The Mode Change
That Came Too Late

There is an important distinction between knowing what the correct automation configuration is and being in it at the right time. The crew that recognises, during the approach, that a selected mode would have served them better than managed mode — and selects it — has done something useful. But if that recognition came after the aircraft had already departed the intended energy profile, the usefulness has a ceiling. The correct selection was made. The timely selection was not.

Timeliness is not a refinement of this behaviour. It is the behaviour. Automation mode management is a forward-looking discipline — one that anticipates what the situation will require before it requires it, rather than responding to what it is requiring now. The crew that is always selecting the mode they need is a crew that is always behind. The crew that is selecting the mode they are about to need is a crew that is ahead of the aircraft.

What Timely Actually Means

Timely does not mean fast. It means early enough that the automation can establish the intended state before it is needed to maintain it. A speed mode selected at the correct moment gives the automation time to capture the target and stabilise before the constraint becomes critical. The same selection made when the constraint is already active asks the automation to recover rather than maintain — a fundamentally different demand, made under fundamentally different conditions.

The window for timely selection is defined by two things: how long the automation takes to capture the intended state, and how long the crew has before that state becomes operationally required. Both vary by situation, aircraft type, and the specific mode being selected. The crew that understands their automation — that has internalised how quickly each mode responds, what it will do in the transition period, and when it will have stabilised — is the crew that can judge the selection window accurately. The crew that does not have that understanding selects reactively, because they cannot anticipate the window they are working within.

Anticipation as the Foundation

Timely mode selection depends on anticipatory situational awareness — the specific dimension of situational awareness that looks ahead rather than at the current state. What is the next constraint? What mode will be needed to meet it? At what point does that mode need to be selected for the automation to be established in time? These are forward-looking questions, and answering them requires that the crew is thinking ahead of the aircraft rather than with it.

The approach is the clearest illustration. The crew that has briefed the energy management strategy for the descent — that has thought through the speed schedule, the configuration points, the likely mode transitions — arrives at each phase with the selection already considered. The mode is changed at the right moment because the right moment was identified during the briefing, not discovered when it arrived. The crew that has not done that preparation makes mode selections reactively, under workload, at precisely the moments when reactive decision-making is most expensive.

The Mode and the Level Together

This behaviour adds mode to the selection discipline. Choosing the appropriate automation level — full managed, selected, or manual — is one decision. Choosing the correct mode within that level is another. LNAV or heading select. VNAV or selected altitude. Speed managed or speed selected. Each of these mode choices has timing implications as well as appropriateness implications.

A heading select engagement at the right moment, in response to a vector that will shortly supersede the programmed routing, keeps the aircraft tracking the clearance and keeps the crew's workload contained. The same engagement made too early abandons the FMS routing before ATC has confirmed the vector — creating an interim configuration that requires active management. Made too late, it means the aircraft is already tracking the programmed route past the point where ATC expected it to turn.

The timing of the mode selection is inseparable from its appropriateness. A mode that is correct in principle but selected at the wrong moment may produce worse outcomes than the mode it replaced. Understanding this — building it into the automation selection discipline — is what separates reactive mode management from genuine automation fluency.

Briefing the Transitions

The highest expression of this behaviour is the automation transition brief — the explicit agreement, before the demanding phase, of which mode changes are anticipated, at what point they will be made, and who will call them. This is not a complex exercise. For a standard approach, it may take a single sentence: at the top of descent we will select managed speed, at the FAF we will confirm approach mode is active, and we will call any mode that does not capture as expected.

That sentence converts three reactive decisions into three prepared ones. The crew is not discovering the transition when it arrives — they have already considered it. The timing has been agreed. The callout has been named. When the moment arrives, the selection is made smoothly and at the right point, because the right point was identified before the workload that surrounds it had arrived.

This is the connection to Communication. The automation transition brief is a communication behaviour — the construction of a shared mental model of the intended mode sequence. Without it, each pilot may have a different picture of when the transitions will happen. With it, both pilots are watching for the same moments and ready to make or confirm the same selections. The timeliness of the individual mode selection is partially a product of the quality of the shared understanding that preceded it.