Pilot Debrief
StudyDatabase
Sign inGet started
← Back to Study Hub

Study Path

Automation and Flight Path Management

When the airplane is doing something you didn't ask for

Overview

This Study Path is about the moment when the autopilot stops doing what the pilot believes it is doing and the pilot does not notice in time. The failure is not the automation. The failure is the assumption that the automation is performing as intended without verifying that assumption. The pattern is built on the gap between selecting a mode and confirming that the mode is tracking. This path trains the ability to monitor automation behavior against intent, and to understand why pilots stop checking once they believe the system is engaged.

Real-World Scenario

A pilot departs on a medical transport flight at night in instrument conditions. The autopilot is engaged after takeoff, and the airplane begins climbing along the published departure procedure. Shortly after, the autopilot disengages and then reengages. The airplane appears to continue tracking normally. The pilot’s attention shifts to managing the flight — communications, climb clearance, weather awareness. Minutes later, the autopilot disengages again. This time it does not reengage. The pilot is now hand-flying in solid instrument conditions at night with no visible horizon. The airplane has been climbing steadily and tracking as expected for several minutes. The pilot’s expectation of what the airplane is doing has been set by that stable behavior. That expectation has not yet been checked against what the airplane is actually doing now.

Lessons

Mode AssumptionWhen selecting a mode replaces confirming it
1

Selecting a mode is not the same as confirming the mode is active

Autopilot systems require the pilot to select a mode and then verify that the mode has captured. A heading selected on the bug is not the same as heading mode engaged. An altitude set in the window is not the same as altitude capture armed. Pilots who select and move on without confirming engagement are flying on an assumption. If the mode did not engage, or engaged a different mode than intended, the airplane will fly a path the pilot did not command. The annunciator panel exists to close this gap, but it only works if the pilot reads it after every mode change.

2

Automation does exactly what it is told, not what the pilot meant

An autopilot does not understand intent. It follows the logic of the mode that is active. If the pilot intended to track a course but the system is in heading mode, the airplane will fly the heading, not the course. If the pilot intended to descend to a selected altitude but the vertical mode is in vertical speed, the airplane will descend at the selected rate regardless of the target altitude. The divergence between intent and behavior grows with time. The longer the pilot assumes the correct mode is active, the further the airplane moves from the intended path.

The Outcome

This is where the option space collapses.

This is where the option space collapses. Without the autopilot maintaining the intended flight path, the airplane begins deviating from its course and its climb profile. The pilot, hand-flying in conditions with no external visual reference, does not recognize the divergence in time. The airplane enters a descending turn that progresses unchecked. The rate of descent accelerates beyond what the airframe can sustain, and the airplane breaks apart before reaching the ground. All five occupants sustain fatal injuries. The outcome was not the product of a single moment. It was the accumulation of a growing gap between what the pilot believed the airplane was doing and what the airplane was actually doing — a gap that widened without detection until recovery was no longer possible.

Reflection Prompts

Use these prompts to rehearse the decision points before you ever face them in flight.

  • After your autopilot engages, how long does it typically take before you shift your attention to something else — and what would bring your attention back to verify it is still tracking as intended?
  • If the autopilot disengaged and then reengaged during a flight, would you treat that as resolved, or would it change how closely you monitored the system for the remainder of the flight?
  • When you are hand-flying in instrument conditions and also managing communications, clearances, or other cockpit tasks, how would you recognize that your awareness of the airplane’s state had started to fall behind?
  • Have you ever looked at the flight instruments and realized the airplane was not where you expected it to be — and how long had the divergence been building before you noticed?
  • When the autopilot is doing what you expect, what keeps you checking — and what makes you stop?

After your next flight with the autopilot engaged, note every mode change you made and whether you confirmed capture each time, then record what you found in Debrief.

AdvancedSIGN IN

Sign in to read this section — free with any account.

InstructorSIGN IN

Sign in to read this section — free with any account.

Close the loop with a debrief

A good debrief turns what you noticed here into a personal trigger you will recognize earlier next time.

Open Debrief Assistant

Real-World Reference

This study path is anchored to a real NTSB investigation: PILATUS PC-12/45 (2023).

Primary AccidentPilatus PC-12/45 — Autopilot disengagement in night IMC during medical transport (2023)
Similar Mishaps
  • Cessna 501 (2020)
  • PILATUS AIRCRAFT LTD PC-12/47E (2022)
  • PILATUS AIRCRAFT LTD PC 12 (2017)
  • RAYTHEON AIRCRAFT COMPANY C90A (2022)
  • Piper PA 31T (2020)

© Pilot Debrief · Built for pilots who take judgment seriously.

Marketing siteLibraryCase StudiesThe Pattern
TermsPrivacyData Sources

Pilot Debrief presents aviation mishap information derived from official National Transportation Safety Board (NTSB) data. Content is provided for educational and safety purposes only. It does not replace official reports or professional judgment.

Browse the mishap database →
Attention DriftWhen reduced workload becomes reduced monitoring
3

Workload reduction is not the same as workload elimination

Pilots engage the autopilot to reduce workload, and it does. But reducing workload does not mean eliminating the need to monitor. The autopilot requires the pilot to verify mode status, cross-check the flight path against the intended route, and confirm that the automation is producing the expected result. When pilots treat the autopilot as a replacement for monitoring instead of a tool that requires monitoring, they create a supervision gap. In that gap, the automation can diverge from intent without detection until the divergence becomes an emergency.

When did you last confirm what the autopilot was actually doing, rather than what you told it to do?
Divergence and ReversionWhen the airplane goes somewhere you never intended
4

The reversion to manual flight after automation divergence is the highest-risk moment

When a pilot discovers that the autopilot is not tracking as intended, the immediate response is to disconnect and fly manually. But the pilot is now taking control of an airplane that may be in an unusual attitude, at an unexpected altitude, or on a heading that makes no sense relative to the route. The pilot must simultaneously assess the current state, determine what went wrong, and fly the airplane in conditions that may require instrument proficiency the pilot has not exercised recently. The transition from passive monitoring to active manual flight is where loss of control most often begins.

5

A regular scan of the mode annunciator is the only defense against mode confusion

Mode confusion does not announce itself. The airplane flies smoothly in the wrong mode just as it does in the right one. The only way to detect the divergence is to read the mode annunciator and compare it to what was intended. This is not a one-time check. It is a recurring scan that must happen after every mode selection, after every altitude or heading change, and at regular intervals during cruise. Pilots who build this scan into their flow catch mode errors early. Pilots who do not build it in discover the error when the airplane is somewhere it should not be.