Explore

Lab 06 - Advanced Mission Planning and Simulated Emergency

15 Points

Nathan Tyler Rose

Anestis Athanasios Tsagris

Last edited 25 days ago by Nico Jaeckle.

Lab 06 Sign Up

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

1. Operational purpose

Training flight 2. Facilities and Logistics

Inside of NISW 116, flying in Xplane 3. Access

Access has been given for simulator and room 116 4. Speed limits

80 knots 5. Hours of operations

1:30pm to 2:30pm 6. Operations point of contact

Anesti 7. Facilities point of contact

Rose 8. Communication method within team

Within vocal range, group chat 9. Communication frequency with ATS

127.75 10. Areas of operations

Klaf airport 11. Circuit directions and height

Left hand pattern at 1000 ft AGL 12. Safety pilot position

Standing on the side of the runway. 13. BVLOS procedures

Auto mode allow aircraft to fly preplanned flight, should maintain VLOS 14. Concurrent operations allowed

Daily Briefing

1. Activities

Flight training on ULTRA 2. Weather current and forecast (Wind, direction, visibility, precipitation, temperature, dew point)

Overcast, light rain, wind at 5kts 100 degrees, 1500ft ceiling, temp 3C, 2.5 miles of visibility, dewpoint 2.8C 3. NOTAMS

None 4. Traffic

None 5. Fleet/Aircraft active

Windracer Ultra

Flight Briefing

For item 10, use the FRAT below.

1. Objective and roles

Perform successful training flight and understand emergency procedures 2. Air traffic services coordinated

ATC knows that we will be flying 3. Satisfactory air vehicle inspection

Has ULTRA been inspected? YES 4. Route/Time/Fuel

30 minute flight left hand kidney bean pattern around klaf, full fuel 5. DATX and SPAS battery and configuration

DATX is charged and normally configured, SPAS is fully charged 6. Radio links deconfliction

Only one aircraft will be flying. 7. Internal/ External comms – frequencies and numbers

ATC: 119.6, phone number: 765-743-9687, walkie talkies 8. Personal Protective Equipment and fire extinguishers

All PPE and fire extinguishers are accounted for. 9. Service bulletins

Check for any service bulletins. 10. FRAT – Start, complete & submit

FRAT looks good, all marks are flow severity 11. Threat and Error management

Whiteboard scenarios 12. Specific recovery procedures

Will go into loiter if link is lost and link will try to be recovered. 13. Emergency scenario - review

birdstrike - Kill engine if damaged, perform a stabilized landing, hand over control to more experienced pilot if possible, flaps clean 14. GCS initial Setup and Start Checklists

GCS has been setup correctly and checklists will be started

⁠

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?

The direction of the flight pattern so that it allows for a smooth entry back into the pattern

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

The takeoff point is set after the runway because once the aircraft reaches that point in either altitude or xy, it will go to the next point.

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

Point 10 is unnecessary but it could be used if there was high terrain near the runway.

⁠

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.

Full stop stabilized landing.

SP: State intentions.

GCS: Confirm intentions.

SP: Nudge.

CGS: Confirm nudge seen.

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

GCS: Confirm SP has control

SP: Confirm control

GCS: 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.

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?

60 knots

What is the target speed for single engine failure?

52 knots

When should you deploy flaps?

During a single engine failure half flaps are recommended or when the UAV pilot is confident that they can make it to the runway.

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?

Near ground: Shorten the usual flight circuit and try to land on the runway as soon as possible.

Far above ground: Shorten the usual flight circuit and try to land on the runway as soon as possible, if there is extra speed deploy flaps.

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.