Skip to content

Lab 06 - Altitude Waiver

image.png
image.png

Paraphrased Answers to the Questions

We chose the "Beck Agricultural Center" (Google Maps Link to Beck Agricultural Center) as our location. It is located north of US Highway 52, past Sagamore Parkway, and is about a 5–10-minute drive from the Purdue Airport, which is also north of the airport and the campus. There are four people in our group: Kyle Elliott Struck, Minje Kim, Evan Michael Madura, and Alexander Michael Delatorre. After that, below are some facts about the MFE Believer and the aircraft's specifications:

Specs:

Size: 77in wingspan, 7in fuselage height and 42in length
weight: 12lbs.
flight duration: 120 minutes
cruise: 45mph

Operational Waiver vs. Airspace Authorization

A waiver is a legal way for a drone operator to disregard certain Part 107 rules. Some examples are flying without lights at night, flying over people, operating from a moving car, and flying more than one UAS at the same time.
With an Airspace Authorization, you can fly in limited airspace (Class B, C, D, and E near airports). For an Airspace Authorization, you need an operation title, a responsible party, the operation's maximum altitude, its boundaries, a description and explanation, maps, and a way to communicate.

Which One Do We Need

We would need to get both an Operational Waiver and an Airspace Authorization in order to fly our aircraft above 400 feet in the area we chose. This is because we are flying above 400 feet, which requires an Operational Waiver, and we are also flying in a controlled airspace, which requires an Airspace Authorization.

Waives:

The rule we are waiving is 14 CFR §107.51(b) – Operational Limitations for Small Unmanned Aircraft. This rule says that UAS operations can't go above 400 feet above ground level unless they are over a building or object.


Lab 06 - Safety Risk Assessment and Mitigation Steps
Row
Hazard
Cause
Effect
Likelihood1
Severity2
Risk3
Mitigation
Emergency or contingency procedures4
Cross-doc icon
Loss of Control of sUAS
Pilot error, automation failure, strong winds
Crash into property, injure bystanders
Occasional
Hazardous
High
Conduct a preflight checklist, limit operations to <15kt winds, and use the GPS return-to-home feature, maintain VLOS at all times
Activate RTH, land in safe area, notify authorities if UAS crashes
Cross-doc icon
Flyaway Beyond Operational Area
GPS signal loss, lost link, interference
Entry into controlled airspace, potential midair conflict
Remote
Catastrophic
High
Geofencing, lost-link procedures, maintain space from controlled airspace, avoid RF interference zones
Initiate lost-link procedure, notify ATC if entering controlled airspace, terminate flight if unsafe
Cross-doc icon
Collision with Nonparticipants
Low-altitude ops near people
injury to people, damage to property
occasional
hazardous
high
Avoid operations over nonparticipants, establish a perimeter, use visual observers, abort if there is a large crowd
Emergency landing in a safe zone, first aid if injuries occur, contact emergency services
Cross-doc icon
Battery Failure / Fires
Overcharging, aging battery, improper storage
Loss of thrust, fire hazard
Remote
Major
Medium
Inspect batteries preflight, follow charging directions, use approved batteries only, keep a fire extinguisher on site
Land immediately if low power or battery error
Cross-doc icon
Weather-Related hazards
Rain, strong winds, extreme temperature
Reduced control, system failure
Occasional
Major
Medium
Cancel flights in precipitation, check weather data, only operate within limits
Land immediately if the weather deteriorates, or abort the mission if the winds exceed limits
Cross-doc icon
Obstacle Collision
Pilot error, poor site survey
Damage to aircraft or damage to property
Probable
Major
High
Conduct site survey, set altitude ceiling, maintain VLOS, use the obstacle avoidance system
Controlled emergency landing, notify if property damage happens
Cross-doc icon
Loss of Situational Awareness
Pilot distraction, multitasking, fatigue
Delayed response, flight into unsafe area
Occasional
Major
Medium
Have a VO to limit distractions, use checklists
VO assumes control, lands immediately if unsafe, and has a rested crew
There are no rows in this table

Part 107 Waiver Safety Explanation Guidelines and Guiding Operations


Describe how the small unmanned aircraft will not pose a hazard to aircraft, persons on the ground, and others’ property when operating at altitudes other than those prescribed in § 107.51(b).
Our operation will be conducted at the Beck Agricultural Center, a controlled and designated test site located north of Purdue University’s airport (KLAF) and campus. The location is rural, with minimal non-participants and few ground structures. This reduces the risk to both people and property. The PIC will maintain a visual line of sight (VLOS) of the MFE Believer at all times, supported by 3 visual observers (VO). The PIC and VO will monitor for manned aircraft at all times, and operations will be terminated or the aircraft will descend immediately if manned aircraft are approaching and in the vicinity.
Describe the anti-collision lighting used on the sUA, in order for it to be seen by crew members in other aircraft from a distance of at least 1 statute mile (sm) during daytime operations and 3sm if conducting nighttime operations.
The MFE Believer will be equipped with anti-collision lighting visible at a minimum of 3 statute miles. This lighting system provides nighttime compliance and daytime detectability, allowing manned aircraft to detect the aircraft from afar. The lights will remain illuminated throughout flight operations. Additionally, the PIC and VO will position themselves to maintain a clear line of sight, ensuring the Believer is detectable throughout the entirety of the flight.
Describe how the RPIC will be able to accurately determine the sUA altitude and direction of flight.
The MFE Believer’s system provides continuous real-time data, including GPS location, altitude, orientation, and heading. This data is displayed on the controller and can be confirmed with the visual observer (VO). The PIC will maintain VLOS at all times, supported by a VO who is responsible for reporting position and conflicts.
Describe the area of operations using latitude/longitude, street address, identifiable landmarks, or other maps to include the distance from and direction to the nearest airport (e.g., 4.8 miles SE of XYZ Airport).
The operation will take place at the Beck Agricultural Center, located north of US Highway 52 near Sagamore Parkway. The site is approximately 5-10 minutes north of Purdue University Airport (KLAF). Operations will be limited to a defined area over agricultural land, away from populated areas and roadways. Boundaries will be established via GPS geofencing in the ground control system, with altitude limits set in accordance with the waiver. The nearest airport, KLAF, is approximately 5 miles south of the test site. Coordination with Purdue Airport and ATC will be conducted before operations.
In addition to filing a NOTAM, describe how the RPIC will communicate/coordinate with Air Traffic Control (ATC) if required by a Special Provision in your Certificate of Waiver and based on the complexity of your operation.
The PIC will file a NOTAM before all operations above 400 ft. AGL. The PIC will request Airspace Authorization through LAANC using the app ALOFT for operations in KLAF’s controlled airspace. During operations, the PIC will have his phone and maybe a radio in case of an emergency. In the event of a lost link, flyaway, or other emergency, the VO will immediately contact ATC and execute contingency procedures to descend or terminate the flight safely.

Application Draft


Operational Waiver:
image.png
The control station does not give the option to stand at the location. The only other one applicable is “Stationary Vehicle,” which is not accurate for this situation.
image.png
image.png
Responsible Party and Pilot Information will be added later...
image.png
Want to print your doc?
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.