Your Pilot InterviewATPL EASA

Situational awareness and automation

Connect raw indications to a shared projection of what happens next.

What is missing when a crew sees a warning but misunderstands it?

Seeing information is only the first level of understanding the situation.

Perceive, understand, project

Situational awareness includes perceiving relevant cues, understanding their meaning and projecting the near-term evolution. A crew may see an altitude restriction yet fail to recognise that the active mode will not capture it. More information does not help if its significance is not connected to the plan.

Use cross-checkable statements

State the observation, its implication and the expected next event: “Vertical speed mode; the selected level will require capture; monitoring the mode change.” This creates a prediction another crew member can test. Exact callouts remain operator-specific.

Mechanism and limits

A shared mental model need not mean that everyone holds identical detail. The flying pilot, monitoring pilot and cabin crew have different roles, but they need compatible expectations about the aspects that link their actions. A briefing makes those links explicit; updates keep them current when conditions change. Situational awareness can also be uneven: a crew may understand navigation while missing energy state. Assess it against the relevant task rather than as a single global feeling of confidence. The useful question is which significant cue, meaning or future consequence is currently missing.

Applied case · Build a testable prediction

A synthetic aircraft descends in a mode that maintains a selected vertical speed. The next restriction is approaching. The crew sees the restriction and reads it correctly, but assumes the aircraft will automatically satisfy it without checking the active capture logic. Perception was present; understanding and projection were incomplete. State the current mode, the expected capture or intervention and the point at which the result will be checked. Another crew member can now test that prediction against annunciations and flight path. The example deliberately avoids type-specific mode names because the actual logic must come from approved training.

Why is the selected value not the whole automation state?

Input, active mode and aircraft response can disagree.

Intent is not execution

A pilot can select a target that the active mode does not immediately follow. Armed and active modes have different meanings; automatic reversions can change behaviour. Understanding “what is controlling what” is more reliable than assuming a button press guarantees the intended path.

Monitor the closed loop

Cross-check the input, annunciated mode, actual path and next expected change. Use trained intervention when the aircraft response does not match intent. Automation reduces some manual workload while adding monitoring, mode-awareness and data-integrity tasks; it does not remove crew responsibility.

Mechanism and limits

Automation changes the distribution of work rather than simply removing work. It may stabilise a path and perform calculations while creating demands for data checking, mode interpretation and intervention planning. Long periods of reliable performance can encourage reduced monitoring, leaving the crew less prepared for an uncommon reversion. Conversely, excessive unnecessary mode changes can create new complexity. The appropriate automation level depends on the task and approved training. Whatever level is selected, the crew needs a clear understanding of its current authority, limitations and the method of taking timely control.

Applied case · Verify a command through its result

A synthetic pilot enters a new target but an existing active mode continues its previous behaviour. Watching only the selected number creates the impression that the task is complete. Compare three stages: intended input, annunciated active/armed mode and actual aircraft response. If they do not align, use the trained intervention and resolve the mismatch. The lab changes the active mode while holding the selected target constant, isolating the reason for the different trajectories. A correct entry can coexist with an unexpected path, and a familiar automation interface still requires active monitoring.

Can you explain and apply the mechanism?

Four original questions. Work from the stated facts, then compare your reasoning with the explanation.

Your learning

Progress saved in this browser. Log in to sync across devices.

Learning overview