Skip to content
How to format a checklist?Am I missing anything in my risk assessment?I have this number of emergency and contingency plans. What else can I add?My operational waiver states that I need duplex communication between the PIC and the VO. What does that mean?
List of pilots by name and remote pilot certificate number used under this waiver Altitude Waiver Evidence that all participants have taken a quiz to prove they are informed on the altitude waiverPart 107 licenseDrivers licenseList of UAS eligible for use under the waiverincluding make, model, date added, and name of person who affirms complianceLog of maintenance performed for each aircraft operated under waiverdescription, date, name, signatureDocumentation of test flights prior to operations under waivercalendar date, sUA registration number, RPIC, duration, resultWiring DiagramVoltimeterBatteries x2 - charged Fire Extinguisher Charged laptop with GroundControl Radios - charged; number varies with personnel Phones - with appropriate phone numbers savedCrew’s phone numbers911ATC phone numberSPASOther required checklistsSafety VestSunglassesSunscreen Water SnacksHatWater
The RPIC will take immediate control and ensure the safety of people and property.If operating under a waiver or in shared airspace, the appropriate Air Traffic Control (ATC) facility (e.g., Grissom Air Reserve Base RAPCON or Chicago Air Route Traffic Control Center) will be notified with details including last known position, altitude, direction, and nature of the emergency.Local emergency services (911) will be contacted if there is risk to people, property, or fire.The Responsible Person and instructor/supervisor will be notified immediately.If required, the Federal Aviation Administration will be notified in accordance with Part 107 accident reporting requirements.
Maximum altitude of 650 ft AGLClass G Airspace, must stay within defined coordinatesValid from Jan 20,2026 to June 30, 2027No flights at night or civil twilightNo ADS-B Out transmission from the droneCannot combine with other waivers/authorizationsNot an Airspace AuthorizationATOMS must be filed 24-72 hours before operations VOs requiredmonitor at least 2-mile radiusCommunication must be hands-free, full duplex, and have backup methodsResponsible Person has full accountability Must use approved UAS modelsrequires real-time telemetry, alerts for system failures, emergency automation, and anti-collision lights visible for 1 mileMust follow manufacturer maintenance procedureslog work done, date, technician, and signaturemust before test flight under normal Part 107Operational Requirementswaiver on-site during operationsMust yield to aircraftFAA can stop operations at any time
Mission (kidney bean for potential “runway” at ASRECRally pointAirspace (based on Clayton’s waiver boundary)
Upload a completed copy of this document (as a PDF) to brightspace by the due date listed in the . See to add this page to your own doc.See to create a PDF of your doc for submission.See for file naming requirements.
Operational Plan
30 Points
Nathan Tyler Rose
Last edited 23 days ago by Isabella Riley Avedician.
Overview
Using the resources below and your experience performing flight operations, complete an operational plan for the flight training missions that we will complete throughout the next 6-7 weeks. The objective is to build a comprehensive operational plan document outlining the training exercise. You may use AI to help you complete this assignment, but you may not copy-paste text directly.
How AI might help:
Resources
Operation ASREC
Objectives
The objective of this operation is to safely conduct fixed-wing UAS training flights using the twin-engine UAV, The Believer, under an FAA-approved altitude waiver authorizing operations up to 650 feet AGL in Class G airspace. These training operations are designed to enhance pilot proficiency and operational readiness through the execution of standard and advanced flight maneuvers, including takeoffs, landings, go-arounds, low passes, traffic pattern work, and simulated emergency procedures. All activities will be conducted in strict compliance with FAA regulations and waiver provisions, with an emphasis on maintaining the highest level of safety, situational awareness, and coordination among the remote pilot in command, visual observers, and support personnel.
Roles and Responsibilities .
During flight operations, all personnel will have clearly defined roles and responsibilities to ensure safe and effective execution of the mission. The Remote Pilot in Command (RPIC) holds ultimate authority and responsibility for the operation, ensuring compliance with FAA regulations, waiver provisions, and overall flight safety while making final decisions regarding the continuation, modification, or termination of the flight. The SPAS is responsible for maintaining continuous awareness of surrounding airspace and ground hazards, assisting the RPIC in identifying potential conflicts and ensuring separation from other aircraft and obstacles. They will also observe the aircrafts airspeed and altitude to ensure operations are safe and will communicate with the RPIC of any changes. Visual Observers (VOs) support the operation by maintaining unaided visual line of sight with the aircraft, scanning for air and ground risks, and communicating timely information to the RPIC using established procedures. The Ground Control Station (GCS) Operator manages the technical operation of the aircraft systems, including monitoring telemetry, navigation, and system health, and executing control inputs as directed by the RPIC. The Instructor oversees all training activities, ensuring that procedures are properly followed, providing real-time guidance and evaluation, and intervening when necessary to maintain safety and achieve training objectives.
Operational Area
The planned operation will utilize a fixed-wing twin-motor unmanned aircraft system, the Believer UAV, at the Animal Sciences Research and Education Center (ASREC). The primary operational area is centered at coordinates 40.49797553798778, -87.01496958741554. The operational boundaries are defined by a polygon formed from the listed coordinates, encompassing agricultural fields and associated research land. Vertical operations will be conducted at or below 650 feet above ground level (AGL). All operations will take place in Class G airspace at or below 650 feet AGL, and no air traffic control (ATC) authorization is required.
Boundary Coordinates:
40°30'17.33"N, 87° 01'47.26"W
40°30'17.22"N, 87° 01'00.34"W
40°30'11.62"N, 87° 01'00.45"W
40°29'55.84"N, 87° 00'52.27"W
40°29'42.74"N, 87° 01'13.86"W
40°30'11.70"N, 87° 00'52.55"W
40°29'53.41"N, 87° 01'13.77"W
40°29'42.74"N, 87° 01'46.88"W
Boundary Map:
Figure 1. Boundary Coordinates and Visual Map
The operational site is located approximately 9.4 miles north-northwest of Purdue University Airport (KLAF), which is under the jurisdiction of GUS RAPCON and ZAU ARTCC. The remote pilot will remain vigilant for low-altitude manned aircraft, particularly those on approach to land in the surrounding area. However, communication with ATC is not required. The CTAF/tower frequency for KLAF is 119.6, and situational awareness will be maintained through visual scanning and, if necessary, monitoring of local traffic.
Ground hazards within the operational area include power lines, buildings, towers, and nearby roadways. These obstacles present potential collision risks and will be accounted for during mission planning and execution. Flight paths will be designed to maintain safe separation from all obstacles, and visual observers will assist the remote pilot in maintaining awareness of these hazards. Additionally, as crops grow throughout the season, they may create visual and physical obstacles that could affect takeoff, landing, and low-altitude maneuvering, requiring continuous reassessment of the environment.
The area is characterized by low population density, consisting primarily of agricultural fields, farms, and a small number of dispersed residential structures. Only authorized participants will be present during flight operations, and all personnel will be briefed on safety procedures and required to remain in designated safe zones. Cones or other markers will be used to establish boundaries and ensure non-participants remain clear of the operational area.
Weather conditions will be evaluated prior to and during all operations using official aviation weather sources, including METAR reports from Purdue University Airport. For example, a typical observation such as “METAR KLAF 241554Z VRB04KT 10SM CLR 06/M04 A3039” indicates favorable conditions; however, an on-site weather assessment will always be conducted to confirm safe operating conditions, including wind, visibility, and any localized environmental factors.
The designated takeoff and landing zone is located at 40°29'43.99"N, 86°59'47.29"W and consists of a grass surface suitable for fixed-wing operations. The site provides adequate space for safe launch and recovery, with clear approach and departure paths. Access to the operational area is unrestricted via W 500N, where personnel can enter via a gravel road and park near the site. Communication among crew members will be maintained through verbal callouts, mobile phones, and radios as needed.
Map of takeoff and landing site:
Figure 2. Takeoff and landing coordinates
Operational security will be maintained by establishing a clearly defined flight line and spectator boundary using cones or similar visual markers. All personnel will be required to remain behind these markers unless directly involved in flight operations, ensuring a controlled and safe environment throughout the mission.
Pre-Departure Checklist
Name
Column 2
NOTAM
Reviewed and put out 24 to 72 hours in advance
Mission
Planned and reviewed
Crew Roles
Assigned and briefed
Emergency Procedures
Briefed
Weather
In limits
Documentation
Everyone has required documentation and it is packed
Batteries
Charged and have a spare
Aircraft frame Inspection
Ensure it is operational and safe to fly
Avionics System
Correct and plugged in
Aircraft Items
Packed
Personal Items
Packed
Center of Gravity and Hand-Launch Grip Points
Confirmed
There are no rows in this table
Before departing for the mission the team, more specifically the RPIC, needs to ensure the table above is complete and all individuals are briefed and prepped. A NOTAM needs to be released 24 to 72 hours in advance to mission operation. The entire crew needs to be briefed on the mission, specific roles and responsibilities, and emergency procedures before leaving dispatch. The crew needs to check the weather at the operational site to ensure it is safe for operations. The RPIC is responsible for ensuring all individuals have the appropriate documentation on hand and all required documentation is present at the mission site. The following documentation is required:
Before departing, the aircraft needs to be inspected for any damage and that it is safe for mission operation. In addition, the avionics system needs to be checked and reviewed with the wiring diagram. If any part of the aircraft is damaged or deemed unsafe to fly, then the mission will automatically be terminated until proper maintenance, inspection, and test flights are completed. All personnel should bring any personal items they might deem they need. Finally, the Center of Gravity and Hand-Launching grip points needs to be checked and confirmed. The following items need to be brought for flight operations and recommended for personal safety:
Flight Operations:
Personal Safety:
Pre-Flight
Name
Column 2
Airframe
No damage
Wings
Secure and locked
Propellers
Intact, tight, no nicks
Battery
Charged
Voltimeter
Reading and set
SPAS and GC
Open and Set
Flight Plan in GC
Set
Systems Check
GPS, Compass, Firmware, Telemetry, RC, Failsafe
Control Surfaces
Free and Control
Weather
Go/No Go
Identify Wind Direction
-
There are no rows in this table
At the mission site the aircraft needs to be checked again for any structural damage. The wings need to be physical checked for security. Propellers needs to be checked for any damage or nicks. The battery needs to be plugged in with the voltimeter set on it. The SPAS and GroundControl need to be open and ready for the mission. The health of the aircraft, including all systems, needs to be checked for a heartbeat in GroundControl. All control systems need to be free and control. The weather needs to be checked once again for a final Go/No Go decision. Finally, the wind direction needs to be identified. If the wind direction alters the flight plan and takeoff direction, the flight plan in GroundControl needs to be altered.
Landings
Name
Column 2
Aircaft
Recovered
Motor
Disarmed
Battery
Disconnected
Airframe
Inspected
Flight Logs
Saved
Battery Temperature and Voltage
Checked and Recorded
Any damage
Document
Flight Data
Downloaded
Mission
Debriefed
There are no rows in this table
After landing, the aircraft must be recovered, motors disarmed, and battery disconnected. The airframe needs to be inspected for any damage, and if any is present, all damage needs to be documented in detail. The flight logs and flight data need to be saved and downloaded. The battery temperature and voltage need to be checked and recorded. Finally, the mission needs to be debriefed. The site of operations needs to be left as it was when crew arrived. The crew will not leave any materials at the site.
Risk Assessment
Using guidance from the Federal Aviation Administration and FAA AC 107-2 and the Certificate of Waiver. The following risk assessment was made. The waiver permits small UAS operations above 400 feet AGL, up to a maximum of 650 feet AGL, within defined Class G airspace near West Lafayette, Indiana, provided all mitigation measures and special provisions are strictly followed. The Remote Pilot in Command (PIC) and Responsible Person are directly accountable for operational safety, and that all crew members—including visual observers (VOs)—must be trained, informed, and compliant with both Part 107 and waiver-specific procedures. Additionally, operations must remain within the defined geographic boundaries, cannot occur at night or during civil twilight, and require a filed NOTAM 24–72 hours prior to flight
Operational risks associated with takeoff and landing are highly dependent on direction. When departing to the south, hazards include nearby residential structures, power lines, and trees that may interfere with base and final turns, increasing the risk of collision. When departing to the north, trees pose hazards during upwind and crosswind legs, while power lines remain a concern on base and final. These risks are mitigated through strict traffic pattern control (left-hand traffic for south departures, right-hand for north), maintaining visual line of sight, and the use of a Ground Control Station (GCS) capable of real-time telemetry, system alerts, and pre-programmed emergency actions such as return-to-launch or altitude adjustments. . The waiver further requires sufficient VOs to monitor at least a two-mile radius of airspace, ensuring early detection of aircraft, vehicles, or people and enabling timely avoidance actions.
Figure 3. Trees to the North
Figure 4. Power lines to the West
Environmental and site-specific hazards also play a significant role in the risk assessment. Seasonal crop growth near the takeoff and landing zone can reduce visibility and increase collision risk, while farm equipment and non-participants introduce ground hazards. Previous rainfall may create unsafe muddy conditions on the grass/dirt runway, requiring a no-go decision. Additional terrain risks include a ditch or creek bank to the west, which presents both ground hazards for personnel and flight risks if the aircraft drifts. Nearby residential, industrial, and agricultural areas require maintaining safe separation and avoiding overflight of non-participants, as defined in the waiver.
Figure 5. Farm Fields near runway
Human factors and operational readiness are also critical components of the risk matrix. Hand-launching the Believer UAS introduces risks such as improper release technique or loss of control, which are mitigated through repetitive training with foam and weighted rollers. Crew fatigue and dehydration are concerns due to limited shade and facilities at the site, requiring proper hydration, nutrition, and weather-appropriate clothing. In-flight risks are mitigated through simulator training, buddy-box systems for instructor override, and continuous monitoring of telemetry data such as battery health, signal strength, and aircraft position, as required by the waiver’s GCS provisions.
Finally, operational compliance and emergency preparedness are essential to maintaining an acceptable level of safety. The waiver requires anti-collision lighting visible for at least one statute mile, prohibits ADS-B transmission from the UAS, and mandates detailed maintenance logs and functional test flights after any repairs. A copy of the waiver must be accessible during operations, and the FAA retains authority to cancel operations if safety is compromised. Emergency preparedness measures include configuring automated failsafe behaviors in the GCS and carrying a fire extinguisher in case of battery or electrical fires. Together, these layered mitigations ensure that risks associated with high-altitude UAS operations are systematically identified, assessed, and reduced to an acceptable level in accordance with FAA standards.
Emergency and Contingency Procedures
Loss of Datalink / DATX Disconnect (Lost Link):
A lost link occurs when command and control (C2) communication between the aircraft and Ground Control Station is interrupted. In this operation, if DATX disconnects, the aircraft will automatically initiate a Return-To-Launch (RTL) after approximately 3 seconds, following pre-programmed fail-safe logic. The RPIC will attempt to re-establish connection while maintaining visual line of sight. If the link is not restored, the aircraft will continue its RTL profile and land at the designated recovery point. The crew will note last known position, altitude, and heading for situational awareness and potential recovery.
Loss of GPS:
If GPS signal is degraded or lost, the RPIC will immediately transition to manual flight (if available) and safely land the aircraft within the operational area. If both GPS and datalink are lost simultaneously, the aircraft will execute an automatic landing at its current position or follow pre-programmed contingency behavior
Ground Control Station (GCS) Failure:
In the event of GCS malfunction, backup control methods (if available) will be used. If control cannot be regained, the aircraft will follow its automated emergency profile (RTL or controlled descent). The RPIC will ensure the aircraft remains clear of people and obstacles during the event.
Flyaway / Loss of Control:
If the aircraft deviates from commanded flight or exhibits uncontrolled behavior, the RPIC will initiate emergency procedures such as RTL, loiter, or flight termination depending on severity. If the aircraft cannot be recovered, the crew will document last known telemetry and initiate recovery procedures while ensuring ground safety.
Low Battery / Power Failure:
If the aircraft reaches a critical battery threshold, it will automatically initiate RTL or auto-land depending on configuration. The RPIC will prioritize a safe landing area and ensure the aircraft does not overfly people or structures.
Engine or Propulsion Failure:
In the event of partial or total propulsion failure, the RPIC will execute an immediate controlled descent and land in the safest available area within the operational boundary.
Intruding Aircraft (Manned or Unmanned):
If another aircraft enters the operational area, the RPIC must immediately yield right-of-way and take evasive action (descend, climb, or maneuver laterally as appropriate). Visual Observers play a critical role in early detection and communication to prevent midair collision.
Loss of Visual Line of Sight (VLOS):
If the VO or RPIC loses sight of the aircraft, the operation must be terminated immediately unless visual contact is quickly re-established. The RPIC will command the aircraft to return and land safely.
Obstacle or Terrain Avoidance (Trees, Powerlines, Crops):
If the aircraft is at risk of collision with obstacles, the RPIC will manually maneuver away or initiate RTL. Pre-programmed waypoints and geofencing through the GCS serve as preventative mitigation.
Weather-Related Emergency (Wind, Rain, Visibility):
If weather conditions deteriorate (e.g., high winds, precipitation, or reduced visibility), the RPIC will immediately terminate the mission and land the aircraft. Flights will not be conducted in unsafe weather conditions.
Battery Fire / Electrical Fire:
In the event of a battery or onboard fire, the aircraft will be landed immediately if possible. A fire extinguisher on-site will be used to contain any fire hazard after landing.
Crash / Hard Landing:
If the aircraft crashes, the crew will secure the area, assess for injuries or property damage, and attempt recovery only if safe to do so. Damaged batteries will be treated as fire hazards.
Human Factors (Fatigue, Dehydration, Injury): If any crew member becomes unfit to perform duties, operations will be paused or terminated. Proper hydration, rest, and crew rotation are required to mitigate these risks.
Who to Contact in an Emergency:
In the event of a significant incident or emergency:
Compliance and Approvals
Part 107 Credentials and Currency:
Figure 6. Part 107 License
Copy of Waiver:
Important Information from Waiver
Mission Files
In Ground Control build and export the following (attach them here):
Deliverables
Broken link
Rubric
Generate with AI
Section
Max Points
Criteria summary
1. Objectives
3
Clear, specific training objectives tied to the upcoming missions; not generic.
2. Roles and responsibilities
3
All key roles defined (PIC, VO, instructor, GCS operator) with clear responsibilities.
3. Operational area
4
Map, coordinates, and navigational cues; description of site features and constraints.
4. Checklists
4
Believer checklist included; tailored pre‑departure and return checklists that are complete and usable.
5. Operation guide
4
Expands checklist into a readable, step‑by‑step “how‑to” narrative aligned with course practices.
6. Risk assessment
5
Uses FAA‑style risk matrix (e.g., AC 107‑2 / risk video); clear hazards, mitigations, and residual risk.
7. Emergency and contingency procedures
5
Comprehensive list of emergencies with concrete, safe responses and communication steps.
8. Compliance and approvals
2
Correctly references Part 107, currency, and 107.51(b) waiver; shows how plan complies.
There are no rows in this table
30
Sum
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.