Automation Surprise | Flight Safety

Selected passages from the existing NFA article. This public introduction offers an operational overview; the complete study is in the member library.

Automation requires supervision

The crew establishes operational intent; systems execute inputs and logic within their capabilities. Autopilot, flight directors, automatic thrust control and FMS have related but different functions. Being automated does not mean that all are active or that the flight path is correct.

Supervision means continually comparing intent, system state and actual aircraft motion. Responsibility for flightpath management remains with the crew at every level of automation.

The gap between expectation and response

The pilot expects descent, capture, a turn or deceleration. The aircraft does something different. The mismatch may result from selection, data, capture conditions, an automatic transition or a failure. Do not conclude the cause merely because the behavior was surprising.

First recognize the mismatch and its consequence for flight. Then investigate its origin with the flight path protected. A plausible explanation does not replace control of the deviation.

Mode awareness: state and functions

Mode awareness includes knowing what is selected, armed and active, which functions are being controlled and which conditions permit the next transition. Terminology and indications vary between aircraft.

Recognizing a mode name is only the beginning. Understand its priority and limitations: is it controlling speed through pitch, vertical path, thrust or another variable? This distinction informs expectations about energy and flight path.

FMA: confirmation, not a guarantee of flight path

The FMA is a central source of guidance and automatic-control state in aircraft that use it. Panel selection does not guarantee activation. Verify the corresponding indication and compare it with actual response.

Select, verify and monitor summarizes a study discipline; it does not replace callouts and procedures. The FMA alone does not confirm position, ATC clearance, data integrity or terrain clearance. Verification must integrate other indications.

What did I command?

Before making a selection, be clear about intent and the command that will implement it. Changing selected altitude, programming a constraint and selecting a vertical mode are different actions; none should be treated as a synonym for the others.

Verbalize changes according to SOP and confirm values and units. Intent must match the clearance, safe flight path and limitations, and be understood by the other pilot.

What did the system accept?

Compare the input with targets, modes and engagement indications. A correctly entered value may be present without producing the imagined action. Armed is not active; a mode may await specific conditions before capture.

Also verify that the aircraft has begun responding coherently. The less margin there is for a deviation, the more important it is to recognize the absence of the required response promptly and apply the prescribed intervention.

OPERATIONAL DOCUMENTATION TAKES PRECEDENCE

Educational material. Current aircraft and operator manuals, SOPs, mandatory criteria and required actions take precedence. These passages do not introduce new procedures or authorize exceptions.

Technical sources from the original article

NFA PROFESSIONAL

Explore the complete study

Continue with the complete existing article, its operational analysis, examples and references in the member library.

Access the complete study in the member area →The professional plan is in preparation. Paid subscriptions are not yet open.

CONTINUE THE COLLECTION

Runway Excursion →Mode Awareness →