Explore

lab six

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 / speed limits

Hours of operations

Contacts

Areas of operations

Circuit diagnostic

Safety pilot position

BVLOS procedures

Concurrent operations allowed

Daily Briefing

equipment ready

hazard mitigation

notams

weather

traffic area

Flight Briefing

objectives and roles

traffic coordination

inspection, air and ground

route/time/fuel

DATX battery configuration

radio links/comms clear

Threat and Error management

Recovery procedures

Review emergency scenarios

GCS Startup and checklists

use 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?

left because that is the direction of the traffic pattern

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

because you want it to takeoff before that, that point is trying to get the aircraft to that specified height by that location to avoid any hazards on the ground.

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

10 wouldnt always be necessary, if there is a short final that for some reason needs to be planned you wouldnt need multiple points on final, just the land spot and the start of final.

⁠

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.

GCS: State that SP has control.

SP: Confirm control.

GCS: State that SP has control.

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

GCS: State intentions. Set up GCS for taking control.

SP: Confirm intentions. Switch to auto after a proper countdown. State that GCS has control.

GCS: Confirm control

SP: State that GCS has 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.

Full stop stabilized landing.

SP: State intentions.

GCS: Confirm intentions.

SP: Nudge.

CGS: Confirm nudge seen.

SP: Switch to stabilize after a proper countdown.

GCS: State that SP has control.

SP: Confirm control

GCS: State that SP has control. Update current waypoint as needed.

SP: Land, apply brakes, switch to taxi mode.

GCS: Confirm taxi mode seen. Request SP intentions.

SP: State intentions to switch control with another team member. Pass control with proper handoff.

Task 3 - Emergencies

⁠

Using section 8 from the ULTRA UAS - SOP above, answer the following questions:

What is the target speed for dual engine failure?

60KTS

What is the target speed for single engine failure?

52-54KTS

When should you deploy flaps?

when the pilot is confident they can make the field, to get on the ground quicker, otherwise they shouldnt be used

When you recognize that you’ve lost both engines, what should your first move be when you are within a few hundred feet of the ground? Speculate how this changes if you are at a few thousand feet above the ground?

switch to stabilize, pitch for 60 knots and then find a place to land

Near ground:

land straight, if you try to turn around and make the field, you will more than likely stall and spin

Far above ground:

more of a chance of making it back to the ground when turning, it just depends on your height. but you can more than likely land on the opposite runway that you just used, or you could continue on the downwind and make a short base and turn early to make the field.

Simulated Dual Engine Failure

Without warning, you will experience dual engine failure. It is your responsibility to alert your crew in an effective manner and land the ULTRA in a safe location.

Simulated Single-Engine Failure

Without warning, you will experience a single engine failure. It is your responsibility to alert your crew in an effective manner and land the ULTRA in a safe location.

Task 4 - Post-Briefings

Using

Section D of the ULTRA UAS QRH⁠

above, prepare to deliver a post-briefing to your instructor covering the following sections:

Out-Briefing

Daily De-Briefings

Task 5 - Believer Mission as homework

Taking the skills you have learned from this lab and lecture this week, plan an efficient mission. This mission will not be used for X-Plane simulations and should meet the criteria talked about in the lecture for a believer operation. This plan will be used when we operate the believers. We will be conducting operations at this location.

The red pin is on a grass strip used for landings.

⁠

Task 6 - Lab Out Brief

A quick out brief regarding the lab with you instructor

Deliverables

Upload to Brightspace the following

PDF of this completed page

.json file of your X-Plane flight plan

.json file of your Believer flight plan

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

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

CtrlP

) instead.