Mode Awareness | Flight Safety

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

Mode: function, condition and result

A mode defines control logic with inputs, priorities and transition conditions. Knowing its name is insufficient: understand the controlled variable, limitations and expected response at that moment.

Asking “what is VNAV trying to do?” is useful only when grounded in the specific aircraft’s logic. Similar names across manufacturers or variants do not guarantee equivalent behavior.

Intent is not automatic state

Human intent may be to descend, reduce speed or intercept a path. The system executes the actual active state using data and conditions. Intent alone does not modify the logic.

Align intent, clearance, selection and response. If the aircraft holds altitude while the crew expects descent, recognize the mismatch; do not presume its cause before verification.

FMA confirms the indicated state

The FMA presents guidance and autoflight information according to architecture. It may show lateral, vertical and thrust functions, arming and engagement. Read the indications actually available in your aircraft.

Select, verify and monitor summarizes a discipline, not a universal checklist. FMA alone does not confirm route correctness, clearance or terrain separation; compare it with flight path and other references.

Believing it armed

Operating a control and returning to another task without confirming the result allows intent to be confused with state. A selection may not be accepted or may depend on additional conditions.

Verify the prescribed indication and maintain monitoring. Do not assign a universal duration to confirmation: what must be observed and called is defined in the documents and must fit flight priorities.

Armed is not captured

Arming prepares a possible transition. It does not show that capture conditions have been met or that the function already controls the aircraft. Observe what remains active while the system waits.

Follow the capture indication and actual response. If a required transition does not occur, recognize the difference and apply the prescribed intervention without waiting for margin to be consumed.

Transitions require directed attention

Lateral capture, vertical capture, level-off and changes after go-around may alter control priority. Anticipate which function will change, what will remain active and how this will be displayed.

Examples such as HDG to NAV or descent to altitude capture are conceptual. They are not a sequence shared by all aircraft. Know the conditions, annunciations and response of the installation in use.

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

Automation Surprise →Plan Continuation Bias →