Modern transport-category aircraft are managed through sophisticated layers of automation — flight management systems (FMS), autoflight systems, and automated thrust management — that can execute complex trajectories with remarkable precision. Yet this same sophistication introduces a subtle but deadly hazard: mode confusion, the state in which one or more crewmembers hold an incorrect mental model of what the automation is currently doing, or about to do. When the aircraft's behavior diverges from that mental model, the result is an automation surprise — and history shows these surprises can quickly cascade into controlled flight into terrain, unstabilized approaches, or loss of control.
The FAA addressed this problem directly in Advisory Circular 120-71B, Standard Operating Procedures and Checklists for Commercial Operators. While the AC's primary subject is the design and use of SOPs and checklists, it explicitly recognizes that automation integration and mode awareness must be embedded in those procedures. Understanding the accident patterns behind mode confusion, and the procedural disciplines the AC recommends, is essential knowledge for any Airline Transport Pilot candidate and for every crew operating in today's highly automated flight deck.
What Is Mode Confusion?
Every modern autopilot and FMS operates in discrete modes — lateral and vertical guidance states such as LNAV, VNAV PATH, VNAV SPEED, FLCH, HDG SEL, or ALT HOLD, to name only a few examples. Each mode has specific capture logic, engagement conditions, and behaviors that differ from neighboring modes. Mode confusion arises when a pilot believes the system is in one mode when it is actually in another. This can happen because:
- Mode transitions are automatic and sometimes unexpected. The autoflight system can revert, downgrade, or change modes on its own when certain conditions are met — for example, VNAV PATH reverting to VNAV SPEED when the aircraft cannot maintain the computed path, or ALT CAP transitioning to ALT HOLD after level-off.
- The flight mode annunciator (FMA) is small and easy to miss. In high-workload phases of flight, crews may not scan the FMA frequently enough to catch a quiet mode change.
- Control inputs can unexpectedly disengage or modify modes. A manual pitch input, for example, may cause the autopilot to revert to a different vertical mode without an obvious aural alert.
- Different aircraft types have different autoflight logic. A pilot transitioning between fleets may carry over incorrect mental models from the previous type.
The practical result of mode confusion is illustrative rather than a fixed pattern: the crew may, in effect, not be flying the airplane they think they are flying. The aircraft may be descending when the crew expects level flight, may be capturing an incorrect altitude, or may be reducing thrust at a moment when the crew expects thrust to remain constant. These are examples of how an automation surprise can manifest, drawn from the kinds of scenarios discussed in FAA-H-8083-25, Chapter 4 (Automation), rather than a codified FAA definition.
Accident Patterns: What the Record Shows
Several high-profile accidents investigated by the NTSB illustrate how mode confusion progresses from a cognitive error to a fatal outcome. While AC 120-71B does not enumerate specific accidents by name, its SOP guidance is directly informed by the human factors findings these investigations produced.
A common thread is the automation surprise chain: a mode transition occurs, the crew does not immediately notice, the aircraft deviates from the expected flight path, the crew is slow to recognize the deviation because it violates their expectation, and by the time intervention occurs there is insufficient time or altitude to recover. Approach phases — particularly non-precision approaches and arrivals into unfamiliar airports — are disproportionately represented because workload is high, vertical path management is complex, and there is little margin for error near terrain.
A second pattern is complacency-driven passivity: the crew observes an unexpected FMA annunciation but assumes the automation is handling it correctly and does not interrogate the mode change. This is a rational response in most situations — the automation usually is handling it — but it trains a habit of deference that fails catastrophically in the rare cases where the mode change is inappropriate or the data driving it is erroneous.
A third pattern involves input confusion, where a pilot attempts to correct an automation behavior through a control input that inadvertently changes the active mode, creating a new and worse deviation. Attempting to hand-fly a segment while the autopilot is still engaged, for instance, can produce control surface fights and unexpected pitch attitudes.
AC 120-71B: Procedural Disciplines as Defenses
AC 120-71B establishes that well-designed, standardized operating procedures are the primary systemic defense against automation errors. The AC frames SOPs not merely as checklists but as the behavioral infrastructure that keeps crews synchronized with each other and with the automation. Key principles from the AC that bear directly on mode confusion include:
- Mode announcements as part of crew coordination. Effective SOPs require the pilot making an FMS or autopilot mode selection to verbally announce it, and the other pilot to confirm the FMA annunciation. This cross-check converts a silent cockpit action into a shared crew event, making mode awareness a two-person responsibility.
- Automation management callouts. Structured callouts at key flight phases — top of descent, final approach fix, altitude changes — prompt both pilots to verify active modes and armed modes simultaneously. The AC emphasizes that callouts must be meaningful rather than rote; the crew must actually look at the FMA, not simply say the words.
- Understanding before using. AC 120-71B supports the broader FAA guidance that crews must have thorough knowledge of autoflight system logic for their specific aircraft type before operating in revenue service. Procedures should never be a substitute for knowledge; they reinforce it.
- Recognition of automation limitations in SOPs. The AC advises that operators design procedures that explicitly define when automation should not be used or should be disengaged — circumstances where hand-flying or simpler autopilot modes are preferred to reduce the complexity of the automation state and the associated confusion risk.
Why This Matters: Safety and Operational Relevance
Mode confusion is not a hypothetical risk. The FAA, NTSB, and international aviation safety bodies have consistently identified loss of mode awareness as a contributing factor in accidents spanning approach-and-landing, CFIT, and loss-of-control categories. The stakes are especially high in the airline environment because the consequences of error affect dozens to hundreds of passengers, and because the high level of automation sophistication found in transport-category aircraft creates more opportunities for mode transitions than older analog aircraft.
From a crew resource management (CRM) perspective, mode confusion is also a threat to shared situational awareness. If the captain has one mental model of the automation state and the first officer has another, neither pilot is effectively monitoring the actual aircraft trajectory. The two-crew environment, which is designed as a redundancy, becomes a liability when both crew members are confused in the same direction — a phenomenon sometimes called crew-induced mode error.
For ATP candidates, understanding mode confusion matters beyond the knowledge test. The Airman Certification Standards (ACS) and applicable type rating practical test standards require demonstration of automation management, including correct identification of active and armed modes and the ability to recognize and respond to unexpected mode changes. Examiners look for pilots who actively manage the automation rather than passively monitor it.
Key Numbers and Rules
- AC 120-71B is the governing FAA advisory circular for SOP and checklist design for commercial operators; it is not regulatory but represents FAA policy and best practice.
- 14 CFR Part 121 requires air carriers to establish and use approved checklists and procedures; AC 120-71B provides the standard for what those procedures should contain regarding automation management.
- Flight Mode Annunciator (FMA) verification should occur after every autopilot and FMS mode selection — this is a universal best practice endorsed by the AC and by most aircraft manufacturer guidance.
- Sterile cockpit rule (14 CFR 121.542, with the parallel Part 135 rule at 135.100) applies during ground operations, taxi, takeoff, landing, and other flight operations conducted below 10,000 feet MSL, except cruise flight — Part 91 has no general sterile cockpit rule for non-commercial operations, and 91.135 instead addresses ATC authorization for operations in the Flight Levels. This is directly relevant to mode confusion because the reduced non-essential communication required during these phases demands that aviation-essential automation callouts are crisp, standardized, and unambiguous.
- Approach briefings required by Part 121 and Part 135 operator specifications should explicitly include review of expected automation modes at each phase of the approach — an SOP element AC 120-71B supports as essential.
Common Test Traps
- Confusing mode confusion with simple autopilot failure. Mode confusion is a crew cognitive error about what mode the automation is in — it does not require any equipment malfunction. The system is working; the crew's mental model is wrong.
- Assuming annunciations are always obvious. FMA mode changes on modern glass cockpits are sometimes indicated only by text color change or a brief boxed annunciation that fades. Examiners test whether candidates understand that passive monitoring is insufficient.
- Overlooking armed versus active mode distinction. An armed mode (e.g., VNAV or G/S armed) has not yet taken control; an active mode has. Confusion between armed and active is a classic source of automation surprise on approaches.
- Thinking that disengaging the autopilot always solves the problem immediately. If an FMS has been programmed with incorrect data, hand-flying based on FMS guidance simply converts automation error into manual pilot error following bad guidance.
- Treating AC 120-71B as regulatory. It is advisory, but the underlying Part 121 regulations require approved SOPs and checklists. The AC defines what FAA considers best practice for those required documents.