Skip to content
Airport BriefingOp Purpose: To flyKLAF airport Access: Granted presumablySpeed Limits: 80 ktsHours of Operation: Open daily from 5 AM to 12 AM. ATC hours of operation 7 AM to 9 PM.POC: Tower phone number is (765) 743-2611Communication method within team: PTT comms between GCS Operator and Safety Pilot.Comms with ATS: 122.95 MHzAO to include runway 28 on both takeoff and landing; AO to include circuitCircuit to commence with takeoff from KLAF RWY 10 @ 606 AGL. First waypoint Safety Pilot will be standing in the grass on the south side of runway 10/28.GCS operator will initiate auto mode and assign aircraft to loop waypoint at Vulcan Building.Daily Briefing
Flight BriefingFRAT:Crew - 0,0,0,0,0Qualification & Currency - 3,3,0,0,3Mission - 0,0,1,1System - 0,0,1Environment - 0,0,0,1,1,0,0Organizational - 0,0
What is the correct loiter direction for the rally point and why?Counterclockwise in order to ensure a smooth transition back in the direction of the circuit. Why is the takeoff point not on the runway? Consider when the wayboard is achieved. It is noting where the aircraft should be (distance and altitude assigned) after actual takeoff.Which waypoint appears unnecessary for landing on RWY 23 at KLAF? Under what conditions might this waypoint be necessary?Waypoint 10. In the event that an aborted landing is necessary, 10 is on the track for landing, but can be configured via GCS to a loiter function or rejoining the circuit instead of landing.
If callout isn't completed in three steps, current commander retains control.Instructor must release momentary switch in emergencies to assume control formally.
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-takeoffGCS: 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 controlGCS: 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 controlSP: Confirm GCS has controlGCS: 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 controlSP: Confirm controlGCS: 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.
What is the target speed for dual engine failure?60ktsWhat is the target speed for single engine failure?52-54ktsWhen should you deploy flaps?To slow down the aircraft when attempting to land (if necessary).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: Go straight to runway, descend, and use flaps if necessary when coming in for landing.Far above ground: Stay close to landing area, descend in circular pattern probably until you reach lower, more manageable altitudes. Then use flaps to reduce airspeed and come in for landing if confident that (safe) landing will certainly be achieved.
Out-BriefingDaily De-Briefings
PDF of this completed page.json file of your X-Plane flight plan.json file of your Believer flight plan
More
Share
Explore
Lab 06 - Advanced Mission Planning and Simulated Emergency
15 Points
Nathan Tyler Rose
|
Anestis Athanasios Tsagris
Last edited 5 days ago by Hunter Hall.
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.
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.
Task 1 - Kidney Bean Mission
Using , 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:
Broken link
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:
Refer to the control transfer calls above to transfer command of the aircraft in the following scenarios. Repeat these for all group members:
Tips
Task 3 - Emergencies
Using section 8 from the ULTRA UAS - SOP above, answer the following questions:
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 above, prepare to deliver a post-briefing to your instructor covering the following sections:
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
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.