Skip to content
Created a shared OneDrive folder and CODA workspace for collaboration.Ensured every team member and instructor had edit access.Centralized files to maintain consistent document versions and communication.
Evaluated multiple locations before selecting ASREC.Identified major obstacles like water tower, corn height, and high-tension powerlines.Used coordinates and mapping tools to define safe launch, landing, and pattern areas.
Reviewed 14 CFR §107.51(b) to understand altitude restrictions.Determined that an Operational Waiver is required to exceed 400 ft AGL.Evaluated whether Airspace Authorization may also be needed based on Class E boundaries.
Collected full Believer aircraft specifications to show suitability for altitude.Demonstrated RPIC and VO flight competency and simulation-based training.Ensured operational readiness with documented experience.
Identified hazards including towers, crop height, powerlines, roads, and signal interference.Rated likelihood and severity for each hazard.Created mitigation AND contingency actions (what we do if the mitigation fails).
Explained how we will avoid manned aircraft.Demonstrated visibility at ≥3 SM using strobes and VOs.Described real-time altitude/heading monitoring.Defined area boundaries and ATC contact/termination procedures.
Combined all sections into DroneZone application.Verified consistency across narrative, maps, and parameters.Prepared final draft for instructor review.
Lab 10 Altitude Waiver Submission
Step 1 – Establishing Collaboration and Shared Documentation
Summary (Bullet Points):
Paragraph:
The first stage of developing the waiver involved establishing an organized and centralized workspace so that the entire team could collaborate effectively. One member created a OneDrive folder titled “Team## COA Application” and granted editing access to all group members and both instructors. This ensured that everyone was working from the same set of documents at all times. Into this shared folder, we stored all relevant materials including aircraft specification sheets, maps, screenshots, and drafts of the waiver narrative. The shared CODA workspace allowed us to collaboratively edit the waiver in real time, preventing confusion that might arise from multiple versions of the same file. This step also mirrored professional aviation documentation practices, where information management and version control are critical to operational safety planning.
Step 2 – Selecting and Analyzing the Flight Site at ASREC
Summary (Bullet Points):
Paragraph:
After establishing the workspace, we selected a safe and appropriate flight location. We chose the Purdue Animal Sciences Research and Education Center (ASREC) because its wide open fields, low traffic volume, and controlled access areas made it ideal for fixed-wing UAS operations. We recorded the location coordinates (40°30'32.56"N, 87°01'17.06"W) and reviewed satellite imagery to study terrain and identify obstacles. The nearby water tower presented a vertical hazard during climb-out and approach. The high-tension power lines to the east created both obstruction and electromagnetic interference risks, and seasonal crop height (especially corn) posed landing clearance concerns. These observations influenced our takeoff directions, geofenced boundaries, and visual observer assignments.
Step 3 – Interpreting FAA Regulations and Identifying the Required Waiver
Summary (Bullet Points):
Paragraph:
With the flight location defined, we reviewed the applicable FAA regulations to determine what approvals were needed. 14 CFR §107.51(b) states that unmanned aircraft may not exceed 400 feet above ground level unless they are within 400 feet of a structure. Because our training operations involve open-field pattern work, we needed to apply for an Operational Waiver that would allow us to reach 650 ft AGL. We also researched the distinction between an operational waiver and an airspace authorization; waivers modify rules, while authorizations allow flight in controlled airspace. Since ASREC is near Class E airspace, our group prepared documentation for both paths, demonstrating awareness of the regulatory environment and ensuring our operation remains compliant under all seasonal chart conditions.
Step 4 – Documenting Aircraft Performance and Crew Qualifications
Summary (Bullet Points):
Paragraph:
To support the safety justification, we compiled detailed aircraft and personnel data. The MFE Believer V2 specifications, including wingspan, weight, cruise speed, control system, and battery capacity, were included to show that the platform is capable of stable fixed-wing flight at the requested altitude. Additionally, we documented the flight experience of the Remote Pilot in Command (RPIC), who holds a Part 107 certificate and extensive UAS flight hours. All team members participated in fixed-wing simulator training, demonstrating competency in launch, landing, pattern work, and emergency procedures. This training ensured that control inputs and coordination between RPIC and visual observers remained consistent with safety requirements.
Step 5 – Conducting a Formal Risk Assessment (AC 107-2A Appendix A Format)
Summary (Bullet Points):
Paragraph + Table:
Constructing the Safety Risk Assessment required systematic identification of environmental and operational hazards. Using AC 107-2A Appendix A, we assessed each hazard’s likelihood and severity, then developed layered mitigation strategies. We also defined specific contingency actions to be taken if a mitigation fails, demonstrating that our safety strategy is not dependent on any single safeguard.
Table 11
Water Tower
Located near approach path
Collision risk
Unlikely
High
Medium
Select takeoff/landing direction avoiding tower; VO assigned to tower sector
Abort approach and re-enter pattern
Tall Crops
Seasonal height variation
Hard landing
Possible
Low
Low
Pre-select clear landing lane and walk field
Controlled glide-down + immediate motor cut
Power Lines (East)
Obstruction + EMI
Loss of control / strike
Unlikely
High
Medium
Set geofence boundary well west of corridor and assign VO to east
Activate failsafe orbit/RTL; terminate if outbound
Roads
Potential flight drift
Over-people flight
Possible
Moderate
Medium
Pattern routes avoid roads entirely
Immediate lateral repositioning + terminate if needed
Flyaway/Lost Link
Telemetry loss
Uncontrolled aircraft
Unlikely
High
Medium
Pre-program RTL/orbit failsafe and limit radius to ≤3000 ft
Notify ATC and perform emergency termination
There are no rows in this table
Step 6 – Writing the Waiver Safety Explanation Narrative (WSEG 1–5)
Summary (Bullet Points):
Paragraph:
Using the safety data and procedures we developed, we wrote the WSEG narrative, which directly addresses the FAA’s five required safety justification questions. This narrative described how we will detect and avoid non-participating aircraft using visual observers, auditory cues, strobe lighting, and ADS-B-in data. It explained how the RPIC will maintain awareness of aircraft altitude and attitude using telemetry displays and visual confirmation. We described the dimensions and coordinates of the operational area and explained how ATC could contact us through verified on-site cellular phone numbers to terminate flight if needed. This section demonstrated to the FAA that we have both awareness and control over safety mechanisms at all times.
Step 7 – Finalizing and Preparing for DroneZone Submission
Summary (Bullet Points):
Paragraph:
The final stage of the project involved assembling the waiver document inside the FAA DroneZone application portal. We transferred all narrative responses, uploaded the site map boundary images, and entered all operational specifications including altitude, aircraft weight, operational times, and crew information. Before marking the draft ready for instructor review, we performed a full consistency check to ensure that every value, coordinate, safety claim, and procedure matched across the entire application packet. This final review ensured a complete, professionally aligned submission.
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.