Explore

Lab 06 - Advanced Mission Planning and Simulated Emergency

15 Points

Nathan Tyler Rose

Anestis Athanasios Tsagris

Last edited 28 days ago by Madison Dianne Baker.

Overview

In this lab there are two major tasks. Believer Final Inspection Prep as well as Advanced Mission Planning and Emergencies. The Believer Final Inspection portion should be completed as a group.

The mission planning portion should be completely individual work and should not be completed with the assistance of your peers. We will be planning two separate missions. One will be a mission for the ULTRA on X-Plane and the other mission will be for your believer when operations start. All questions regarding mission planning should be directed immediately to your instructor. Task 0 should be completed before your sign up time.

⁠

Sign up for simulator time here⁠

⁠

Resources and Tools

Tasks - Believer Final Inspection Prep

Task 0 - Review Lab 01

Your classmates provided a quality assessment and punch list for your aircraft as a preliminary check before final inspection. Review this punch list to ensure all items were properly addressed.

Task 1 - Final Power On

Perform one final power check of your Believer. Be sure that the controls, motors, and all peripheral sensors work as expected. This is your final check before passing it off for final inspection next week.

Task 2 - Review Group E-portfolio

Your group e-portfolio will be reviewed as part of your final inspection next week. Be sure that you are happy with it’s condition.

Task 3 - Signoff Form

Complete the final inspection form below, confirming that your group is ready for final review beginning next week.

⁠

Tasks - Simulator

Task 0 - Pre-Briefings

⁠

Using Section D of the ULTRA UAS QRH above, create the following (simplified) briefings before your flight. You will brief your instructor verbally, so you need not write down your briefing; be prepared to lead it.

Airport Briefing

Operational purpose: Depart KLAF rwy 23, remain in left traffic pattern

Facilities and logistics:

Access: Clearance from tower

Speed Limits:

Hours of operation: start time 10:45

Ops point of contact: tower / ATC

Comms with team: radio? Verbal communication

Comms with ATC: 119.6

Area of ops: LAF airport

Circuit direction and height: Left traffic , 1600 ft MSL

Safety pilot position:

BVLOS procedures: Return to home?

Concurrent operations allowed:

Daily Briefing

Activities: we are doing traffic pattern, other manned aircraft may be coming to or leaving airport or doing patterns

Weather: METAR

NOTAMS:

Traffic: Training facility airport, going to be traffic

Aircraft Active: ULTRA

Flight Briefing

Objective and roles: GCS pilot is… Safety pilot is… We are completing this mission…

Air traffic services coordinate: Tower/ATC

Satisfactory air vehicle inspection: Good condition

Route/Time/Fuel: Left traffic for 23 starting at 10:45

DATX and SPAS battery and configuration: Confirmed correct

Radio links deconfliction: ?

Internal/External comms: Tower 119.6

Personal Protective equipment and fire extinguishers : Safety vest

Service Bulletins:

FRAT: Complete and submitted

Threat and error management: Visual observers

Specific recovery procedures: RTH / Loiter

Emergency scenario: review

GCS initial setup and start checklist: Complete

For item 10, use the FRAT below.

⁠

Task 1 - Kidney Bean Mission

Using

Broken link⁠

, other class resources, and the built-in GCS User Manual, recreate the mission below for KLAF RWY 10. Be sure that you achieve/answer the following:

What is the correct loiter direction for the rally point and why?

Why is the takeoff point not on the runway? Consider when the wayboard is achieved.

Which waypoint appears unnecessary for landing on RWY 23 at KLAF? Under what conditions might this waypoint be necessary?

⁠

Kidney bean mission plan for KLAF RWY 23.

Kidney bean mission plan for KLAF RWY 23.

⁠

Task 2 - Auto/stabilize handoff

Control transfer follows a three-step callout:

"you have control," "I have control," "you have control.“

Specific calls between UAV Pilot Instructor and student:

"I have the sticks," "you have the sticks," "I have the sticks"

— confirmed by a nudge.

Alerts:

If callout isn't completed in three steps, current commander retains control.

Instructor must release momentary switch in emergencies to assume control formally.

Refer to the control transfer calls above to transfer command of the aircraft in the following scenarios. Repeat these for all group members:

Tips

Under normal operations, the SP will trigger mode changes.

To abort a landing, SP throttle to 100% or press the abort landing button in GCS.

Auto-takeoff

GCS: State intention, direction of circuit, altitude, rally point location.

SP: Read back and confirm GCS intentions.

Stabilize in downwind, continue circuit (aircraft already in infinite auto circuit)

SP: State intentions. Nudge aircraft.

GCS: Confirm nudge seen. Confirm intentions.

SP: Switch to stabilize after a proper countdown. State control

GCS: Confirm SP has control.

SP: Confirm control.

Auto in downwind, perform an SP-triggered aborted landing (go-around) to return to circuit.

GCS: State intentions. Setup GCS for taking control.

SP: Confirm intentions. Switch to auto after a proper countdown.

GCS: State control

SP: Confirm GCS has control

GCS: Confirm control.

SP: Abort auto landing just before flair. State go-around.

GCS: Confirm go-around. Ask for the reason.

SP: State the reason for the go-around. For example, the aircraft was not aligned with the centerline.

GCS: Update mission as required.

Want to print your doc?
This is not the way.

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.