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
Operation ASREC
Objectives
Operation to fulfill fixed wing training requirements for AT219 Maintenance and Operations ll utilizing the MFE Believer builds that were assembled throughout the last and current semester. Operation will take place up to 650 AGL within the approved waiver boundary.
Roles and Responsibilities
Roles, with the exception of the instructors, will be swapped throughout the operation amongst group members, to include myself (Hunter Hall), Lucas Toppe, and Aidan Tottori. Roles will be static between takeoff and landing for each flight.
Instructor(s): Nathan Rose; Anestis Tsagris
PIC: Responsible for the stabilized flight of the Believer during takeoff and landing; responsible for taking over the controls during automated flight of the circuit if necessary
GCS: Responsible for monitoring the operating conditions of the Believer while in flight and switching to different flight modes at the request of the PIC
VO: Ensures that potential obstacles within the flight circuit are communicated to the PIC in order to mitigate safety concerns.
Operational Area
COA_Believer_Boundaries_East_Amendment_032526.pdf
2.1 MB
Operational boundary extends to W 500 N road to the south, N 425 W to the east, and W 600 N to the north. East boundary aligns with the dirt road used to access site and slants to the north east to maintain a 0.07 mile distance from high tension powerlines that obstruct the operational area. Operational boundaries also are tailored to avoid houses and other buildings in the area. There are 9 sides to the irregular polygon that is the operational area. Please refer to the attached file to view the proposed operational boundary.
The site’s address is 4718 W 500 N, West Lafayette, IN 47906. Drive up the dirt road and continue straight north after the dirt road ends and enter the grass. Keep on the east side of the ditch and do not cross the bridge to get on the west side.
Reception in the area is good and obstructions are minimal. There are no public restrooms available, but a deep ditch is handy...so if desperate times arise, there is a solution. The largest concern to operations are the high-tension powerlines to the west of the operations area.
Exact launch and landing site is at 40°29'44.2"N 86°59'46.4"W. Given that the operation is following Part 107 regulations within Class G airspace, the maximum altitude for this flight will be at 400ft AGL.
Checklists
SCALED PLATFORM TRAINING CHECKLIST- DRAFT 2024-08-13 02_32_31.pdf
85.7 KB
The checklist above is to be used for pre-flight checks and to ensure the Believer is operated responsibly. Prior to departure for the operation, team members should ensure possession of:
Completion of the operation should conclude with the return of all equipment to COMP101, with the exception of personal item.
Operation Guide
Well before commencing operations, ensure that weather restrictions won’t impeded the operation. Due to the operation being restricted to Part 107 regulations (with no waiver exceeding the set standards) and the operational area being within Class G airspace, a NOTAM for this operation should not be necessary. It would also be helpful to verify that the Part 107 credentials for each team member is current. Utilize the Flight Risk Assessment Tool (FRAT) to ensure all team members are mentally and physically capable to contribute to the successful conduct of the operation.
When officially on site and going through the pre-flight checklist, it is important to verbally verify instructions and receipt of instructions between the team member reading from the checklist and the team member verifying the status of the Believer from the checklist. Once all of the pre-flight checklist is completed and verified, review the operation with the team members, to include details of the planned circuit, target altitude and speed, and landing procedures. Test communication devices and verify that the communication devices still work across the distance of wherever team members are physically stationed.
Risk Assessment
The above risk assessment is modeled after the U.S. Coast Guard’s PEAACE risk assessment model. Team members should rate what they believe to be the accurate level of risk for each component of the operation and discuss why they gave their respective ratings. The highest number given by a team member should be recorded into the risk assessment matrix. Of course, the gain from an operation should also be discussed. An operation of medium risk and little to gain may be unwise to continue. However, considerable gain could demand partaking in considerable risk. This should be discussed with the team and instructors.
Planning
Ensure everyone feels comfortable with the amount of time and thorough planning conducted in anticipation of the operation (make sure everyone’s on the same page)
Event
Consider the operational complexity. Has there been prior experience with an operation similar to this? A variety of people or entities involved? What are the severity of consequences that may accompany an operational failure?
Asset - Team
Is everyone feeling well enough to be contributing members to the operation? Does everyone possess the competency to successfully function in their role? Are responsibilities articulated and is there adequate supervision?
Asset - Equipment
Is the UAS itself and all related equipment within operational standards of use? Are there any maintenance discrepancies? Do we possess equipment fail safes?
Communication
Does the team have the ability to maintain communication throughout the operation?
Environment
Is the physical environment suitable for operation and will it remain that way during the operation? What obstructions exist inside the flight boundary?
Emergency and Contingency Procedures
Lost Link
Lost link connection between the Believer and DATX will result in the Believer returning to land after 3 seconds of no connection. The same applies if the Believer loses connection with the GCS for 5 seconds. In the event this occurs, team member should clear the landing area and maintain visual of the Believer.
Lost Control
If the PIC, while flying in stabilized flight, loses control of the Believer, the PIC should communicate the situation with the GCS operator. Both should verbally walk through switching the Believer to auto-mode. The GCS operator should update waypoints accordingly and an instructor should be contacted.
Loss of Propulsion
The PIC should immediately communicate the loss of propulsion to team members and an instructor. If the PIC is able to land safely on the predetermined runway, fantastic. If not, the PIC’s primary concern is that the aircraft does not crash into people or property. Ideally, a flat area with no obstructions should be quickly identified for landing. However, given the circumstances and potential danger to other people or equipment on the ground, the best landing area may simply be where there is not people or property to hit, regardless of terrain.
There are more contingencies I want to add, but I’m running out of time.
Compliance and Approvals
Mission Files
In Ground Control build and export the following (attach them here):
Mission (kidney bean for potential “runway” at MOUSETRAP site. Airspace (based on Clayton’s MOUSETRAP waiver boundary) Waiver Quiz
Complete the form below. If it does not load, click the button below to open in a new window. You must be logged into your Purdue account.
Deliverables
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. Upload files from to brightspace. See for file naming requirements. Rubric
Generate with AI