Overview
The focus of this assignment is to draft and submit an operational waiver to the FAA in preparation for practice flights with the MFE Believer, our fixed-wing training aircraft. While flying within 400 feet AGL is feasible, maintaining that altitude ceiling becomes challenging during training maneuvers. Securing this waiver will enable us to conduct more complex training operations with the Believer, enhancing our instructional capabilities. We are going to waiver CFR 107.51b. We will be requesting an altitude of 650ft with a planned max flight altitude of 625ft.
Resources/Reading (from website)
Operational Waivers: Before you apply for a waiver, review the resources below.
Target Location
Our location for the altitude waiver is Purdue ACRE. We picked this location due to its vicinity to Purdue and because of how open the place is. There are lots of places to land and not that many obstacles. Here is a picture of the area we are going to request for our altitude waiver
Team Members
Joseph Salcik
Mason Cramer
Erik Krellner
Hongsik Kim
Trigg Strawhorn
Ryan Shurtleff
Believer Specs
The following are the specs of the sUAS that we are going to be using for this operation
Size: Wingspan: 1960mm
Fuselage Length: 1070mm
Fuselage Height: 180mm
Approx. Weight: 5.5 Pounds
Flight Duration: 2 hours
Cruise Speed: 20 m/s
Part 107 Template Guiding questons
Below are some questions recommended by the FAA to answer for our waiver
Question 1: Describe how the small unmanned aircraft (sUA) 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).
1. Visual boundaries will be displayed on the GCS to aid in avoiding structures or flying outside of designated flight area
2. The altitude limit on the drone will be 675ft AGL which allows for a 25ft buffer for telemetry glitches or inconsistencies.
3. There will be at least 4 visual observers monitoring the area to help avoid collisions with ground structures. They will also be monitoring the airspace for other non participating aircraft. If an aircraft is detected and is approaching the area the PIC will descend the aircraft to 400ft AGL. One of the visual observers will be monitoring aircraft through ADSB out
4. The UAS will have 2 different colored strobing lights (one for each wing) to help make it more identifiable for other non participating aircraft
5. Prior to the flight a NOTAM will be posted to let other manned aircraft know that a UAS operation is happening at higher than normal altitudes.
6. In the event of the possibility of an immediate mid air collision the PIC will make the decision to either maintain altitude or perform a quick descent. The UAS will not make a descent in the event that an aircraft is at a lower altitude.
Question 1a. How will the Remote Pilot in Command (RPIC) and Visual Observer(s) (VO), if used, see and avoid other aircraft when flying over 400 feet above ground level (AGL)?
1. The UAS will have strobing lights on each wing of the aircraft to help make it more noticeable in the air
2. The UAS will have a neon pink markings (tape) painted on the bottom to make it more identifiable to the people on the ground.
Question 2: Describe the anti-collision lighting used on the sUA, in order for it to be seen by crewmembers in other aircraft from a distance of at least 1 statute mile (sm) during daytime operations and 3sm if conducting nighttime operations. a. Will the sUA be sufficiently visible by crewmembers in other aircraft in the location where the RPIC will operate? 1) If yes, how will you accomplish this? 2) If no, why do crewmembers in other aircraft not need to be able to see your sUA?
NA as the answers for this question are found in question 1 and 1a
Question 3: Describe how the RPIC will be able to accurately determine the sUA altitude and direction of flight. a. How will the RPIC know, while keeping eyes on the sUA, the current real-time: 1) Geographic location, 2) Altitude (AGL), and 3) Direction of flight of the sUA b. How will the RPIC maintain visual line of sight with the sUA (i.e., meet the requirements of § 107.31) at the maximum altitude and distance requested in the waiver application?
The RPIC will be in constant communication with the ground station operator regarding altitude, heading, and ground position. The GCS operator will give periodic callouts, as well as when the RPIC requests a position update. The RPIC will use sunglasses and or other methods of environmental protection to help them see the sUA better without needing the aid of assistive viewing devices.
Question 4: 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 area of operation is located at 40°28'36"N 87°00'28"W. it is located 4.5 miles north west of the KLAF airport, just off of US 52. It will be a seven-hundred-foot radius circle. The entire area of operation is an open crop field, except in the southwest half of the operation area is a patch of trees, the
Question 5: 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.
In the event that the operation needs to be stopped for any reason, the visual observer will have their phone connected through LAANC, also 907-390-0579. Additionally, we will be outside of the class Delta airspace, however, we will continuously monitor and power this phone to ensure that if ATC contacts us, someone will answer. We will also include a secondary phone number: 317-908-1061. We will also be monitoring 119.6, the nearest airport tower frequency.
Lab 06 - Safety Risk Assessment and Mitigation Steps
Application Draft
Waiver Safety Explanation
This operation takes place approximately 5.7 nautical miles away from an KLAF airport. The operation is outside of the Class D airspace and since our altitude will be below 700ft we will be outside of the Class E airspace as well. Because of our vicinity to an airport extra precautions are taken to ensure that manned aircraft are identified and proper action is taken if they can pose a hazard to the operation. Also, 3 out of the 4 IFR flight paths for KLAF (the airport closest to the operation) are at least 3NM away from the operation and will not pose a hazard. 1 is close to the flight area but it has a minimum altitude of 1300ft AGL so it will not pose a hazard to our operations. Also, manned aircraft will not fly lower than 1600ft AGL outside of a 3NM radium of KLAF for VFR patterns. Our operation takes places more than 4NM away from the airport. Due to this there should not be interference with manned traffic. However precautions are still in place to watch for lower flying aircraft. The following are done to ensure that the sUAS will not pose a hazard to manned aircraft as well as other people/objects on the ground.
1. Visual boundaries will be displayed on the GCS to aid in avoiding structures or flying outside of designated flight area.
2. There will be at least 2 visual observers monitoring the area to help avoid collisions with ground structures. They will also be monitoring the airspace for other non participating manned and unmanned aircraft. Another one of the crew members will also be monitoring aircraft through an ADSB service. If an aircraft is detected and is approaching the area at an altitude lower than 750ft ALG the PIC will descend the aircraft to 400ft AGL.
3. The UAS will have 2 different colored lights (one for each wing) to help make it more identifiable for other non participating aircraft. The lights being used will have a daylight visibility of at least 3 statute miles.
4. Prior to the flight a NOTAM will be posted to let other manned aircraft know that a UAS operation is happening at higher than normal altitudes.
The Following will be done so the crew on the ground can maintain accurate orientation, location, and altitude of the aircraft to ensure that the sUAS does not fly outside the designated area.
1. The altitude limit on the drone will be 625ft AGL which allows for a 25ft buffer for telemetry glitches or inconsistencies.
2. The UAS will have a neon pink markings (tape) painted on the bottom to make it more identifiable to operation crew on the ground.
3. There will be 2 different colored lights on each wing to help make to aircraft more identifiable in the air and also make it easier for the PIC to maintain correct orientation of the aircraft. The PIC will also use his/her natural eyesight and depth perception to maintain proper orientation of the aircraft.
4. The GCS operator will give periodic callouts to the PIC if they are nearing a flight boundary and every time the aircrafts altitude raises or lowers 50ft when flying above 400ft AGL. In the event that the PIC loses orientation of the sUAS the GCS operator will relay the aircrafts heading and altitude. In the event the sUAS gets within 50ft of a flight boundary or the PIC loses control of the aircraft the GCS operator will make the sUAS automatically return to a rally point closer within the flight area.
The following are mitigations and contingencies for possible hazards that could occur when flying above 400ft AGL.
1. Mid air collision with other manned aircraft
Mitigation: The main mitigation for this hazard is having multiple VO’s scanning the skyline for other aircraft entering the flight area and having one of the operation members monitoring ATSB out. If there is an aircraft entering the flight area the PIC will lower the altitude to 400ft AGL. The remote PIC must brief all involved personnel of how to alert them and report possible collisions.
Contingency: In the event that an aircraft enters the flight area at a lower altitude than expected and could cause an immediate mid air collision the PIC will make the decision to either maintain altitude or perform a quick descent. The UAS will not make a descent in the event that an aircraft is at a lower altitude. If there is a collision, cut throttle, notify personnel and ensure area is safe for ground individuals, provide aid if an injury occurred, and notify local authorities if needed based on the severity of collision.
2. Flyaway
Mitigation: Thorough checklist making sure we have steady connection to aircraft
Contingency: In case of lost link/flyaway, the aircraft will be programmed to fly to a predetermined rally point within our operations area. If control is not able to be regained within a certain period of time, the aircraft will be given the order to initiate a spin. The spin will allow for the aircraft to have a controlled crash without straying too far from the operations area in order to prevent undue damage to foreign persons or property.
3. Low Voltage Cutoff
Mitigation: Have GCS operator be monitoring voltage from real time telemetry information of the aircraft. Notify the PIC if voltage levels are getting low and initiate a landing.
Contingency: Use the servo control to perform a quick descent and emergency landing.
4. Airframe Failure/Crash into ground and other structures
Mitigation: Set bank and speed limits on the sUAS so it does not exceed its hardware limitations. Also, before takeoff, check the sUAS for damages and ensure every part of the aircraft is secure
Contingency: Perform a controlled descent and landing if possible. If control is lost and not able to be regained the GCS operator/PIC will disarm the aircrafts motors. Also the crew will maintain visual observation and note the impact location of the crash, ensure the area is safe, report any injuries or damage to authorities, and preserve wreckage for inspection. File an incident report and review inspection procedures before future operations.
Proposed Location of Operation
This operation will be taking place at the Purdue Agronomy Center for Research & Education (ACRE). The requested flight area is a box approximately 0.43 miles in height by 0.6 miles in length. The coordinates for each corner of the box are:
N 40.499337, W -86.999280
N 40.493003, W -86.999280
N 40.499337, W -86.986722
N 40.493003, W -86.986722
Pictures of Proposed flight area:
Proof of submission: