Explore

Operational Plan

30 Points

Last edited 57 seconds ago by Mason Cole Cramer.

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:

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?

Resources

NSF EAGER Plan

Link

Description

Operational planning website for NSF EAGER trip to Tonopah, NV.

SCALES Flight Week

Link

Description

Large scale coordinated flight in Tulsa, OK to support the WMO UAS Demonstration Campaign.

Lab 05 - Intro to Mission Planning

Link

Description

This lab includes information on mission planning and the believer checklist.

Lab 06 - Advanced Mission Planning

Link

Description

This lab includes an example of a FRAT.

FAA Risk Assessment Video

Link

Description

This video outlines risk and hazard assessments.

FAA AC 107-2

Link

Description

Appendix A includes risk assessment guidance

FAA 107.51(b) Waiver

Link

Description

This is Clayton’s issued waiver.

⁠

Operation ASREC

Objectives

The objective of Operation ASREC is to conduct and operate a series of UAS training missions over a 6–7 week period to become proficient in:

Stabilized and autonomous flight operations

Mission planning using Ground Control Station (GCS) software

Crew coordination and communication between SP, GCS and VO

Emergency procedure and decision making

Risk assessment and mitigation in real scenarios

The goal is to prepare students to operate under Part 107 and waiver conditions while maintaining safe, and consistent flight operations.

Roles and Responsibilities

Safety pilot (SP)

Acts as the final authority on immediate flight safety decisions (can override automation at any time)

Monitors aircraft attitude, position, and performance to ensure stable flight conditions

Takes control if:

The aircraft deviates from the planned mission

There is a loss of GPS, telemetry, or GCS link

A hazard is identified (traffic, people, obstacles, weather)

Maintains situational awareness of the surrounding airspace and environment in coordination with the VO

Confirms the aircraft is in a safe configuration before takeoff (mode, orientation, control response)

Ensures safe takeoff and landing, even during autonomous missions

Visual Observer (VO)

Maintains continuous visual line of sight with the aircraft

Monitors airspace for hazards, like aircraft, obstacles, people etc.

Communicates hazards immediately to SP

Assists with situational awareness

Instructor

Supervises all operations

Provides training feedback and intervention if necessary

Ensures students follow procedures correctly

GCS Operator

Conducts preflight briefings and risk assessments

Ensures compliance with FAA Part 107 and waiver requirements

Maintains control of the aircraft at all times

Programs and monitors mission in Ground Control Station

Oversees telemetry, and mission parameters

Assists SP with system status updates

Operational Area

Location:

40.49568° N, 86.99624° W (ASREC – Purdue University)

Area Description:

Open agricultural research fields with minimal urban interference

Clearly defined flight boundaries

Low population density

Navigation References:

North or US route 52, just past N 425 W, on W 500 N

Identifiable landmarks: white barn, access roads, and research plots, big trailer in middle of farm field

Site Resources:

Limited power availability, need to bring a power bank

No bathrooms

Limited internet access

Vehicle access for staging area, very minimal parking, enough for 4-5 vehicles

⁠

Figure1: Google Maps of Flight Location

Figure1: Google Maps of Flight Location

⁠

Figure 2: Power Lines off in the Distance

Figure 2: Power Lines off in the Distance

⁠

Figure 3: Open Field to the left of Runway 18, No Major Real Hazards

Figure 3: Open Field to the left of Runway 18, No Major Real Hazards

⁠

Figure 4: Trailer to the Left of 18

Figure 4: Trailer to the Left of 18

⁠

Figure 5: Power Lines to the right of 18

Figure 5: Power Lines to the right of 18

⁠

Figure 6: Fence / Electrical next to 18

Figure 6: Fence / Electrical next to 18

⁠

Figure 7: Runway 18

Figure 7: Runway 18

⁠

Figure 8: Runway 27 / 09

Figure 8: Runway 27 / 09

⁠

Figure 9: Ditch Off to the Right of Runway 18

Figure 9: Ditch Off to the Right of Runway 18

⁠

Notes About Flight Area

Flight area is out in the open, there is no power, restrooms, shade etc. Make sure to come prepared

Wind will play a big variable at flight area, it is completely out in the open with nothing to break or stop the wind

Make sure to check metar before departure, and once arriving at flight area

Big fence next to the runway 18 on landing, make sure to move north on the runway before coming in for a landing to stay out of the way.

Checklists

Pre-Departure Checklist

Weather checked (metar, wind, visibility, NOTAMs)

Equipment packed (Believer, controller, batteries, props, cables, power bank)

Firmware and software updated

Mission files loaded into GCS

Airspace authorization verified

Crew assigned and briefed

⁠

Return/Post-Flight Checklist

Aircraft powered down safely

Batteries removed and inspected

Flight logs saved and backed up

Aircraft inspected for damage

Mission debrief completed

Equipment packed and accounted for

Operation Guide

Preflight Operations

Before flight, the GCS operator conducts a full mission briefing covering objectives, roles, airspace, and risks. The GCS Operator ensures the mission is correctly loaded and verifies waypoints, and altitude.

The VO is positioned to maintain clear visual contact with the aircraft and surrounding airspace.

Flight Execution

Takeoff is initiated by the SP after confirming all systems are nominal

The aircraft follows the programmed mission (e.g., kidney bean pattern)

Takeoff in stabilized mode, the switch to autonomous after aircraft is in left hand pattern, nude to confirm

Continuous communication is maintained between PIC and VO

Any hazards are immediately called out

Post-Flight

After landing, the crew conducts a debrief discussing:

Mission success

Any deviations or issues

Lessons learned

Risk Assesment

Risk Assesment

Hazard

Likelihood

Severity

Risk Level

Mitigation

Loss of GPS

Enable RTL, monitor connection

Battery failure

Preflight battery check

Air traffic conflict

VO scanning, communication

Signal loss

RTL after signal loss

High Winds

Check Weather before flight and once at mission site

There are no rows in this table

⁠

Emergency and Contingency Procedures

⁠

This is the WindRacer Ultra emergency procedures, not completely relevant to the believer, but a good starting point for how scenarios like this should be handled, in a calm and fast acting manner to maintain the integrity of the aircraft.

Loss of Link (DATX Disconnect)

Aircraft initiates Return-To-Launch (RTL) after ~3 seconds

SP monitors and prepares for manual takeover

Low Battery

Listen for beeping coming from battery

Prepare flight pattern for landing (reduce altitude)

SP clears landing area

Flyaway

Attempt manual override

Notify instructor immediately

Notify KLAF of aircraft heading and approx. altitude

Crash or Damage