The Selection That Has to Be
Early Enough to Matter

Timeliness is not a refinement of mode selection — it is the behaviour. A mode selected correctly but late does not serve the flight in the way a timely selection would. In fully automated flight, a late selection means the automation is catching up to a situation it should have been ahead of. In manual flight with guidance systems active, the consequence is more immediate: the pilot is following flight director commands that are themselves transitioning — bars that are moving toward a state that hasn't been established yet, in an aircraft that the pilot is physically controlling in real time.

This is the specific character of this behaviour in the manual flight context. The guidance system and the pilot are coupled — the pilot follows what the flight director commands, and the flight director commands according to the active mode. A mode that is not yet captured produces guidance that is in transition. Following that guidance faithfully produces a flight path that reflects the transition rather than the intended end state. The selection needed to arrive earlier, so that the guidance was established before the pilot began following it.

The Window and What Compresses It

Every mode selection has a window — the period during which the selection is timely. Too early and the mode is not yet appropriate for the situation; too late and the aircraft is already past the point where the mode can establish the intended state before it is needed. In fully automated flight, identifying that window requires anticipatory situational awareness and knowledge of how the automation responds. In manual flight, it requires the same — but with less spare capacity to exercise it.

Manual flying consumes cognitive bandwidth. The physical demands of hand-flying, the scan discipline required to maintain the flight path, the energy management attention — all of it narrows the window available for the forward-looking assessment that timely mode selection requires. The pilot flying is not free to think several minutes ahead while simultaneously managing the controls in the present. The timeliness discipline therefore needs to be more deeply prepared in advance than in automated flight, because the opportunity to exercise it in real time is more constrained.

Anticipation — Before the Workload Arrives

The crew that briefs the guidance system strategy before the manual flying phase converts reactive decisions into prepared ones. Which mode will be needed at the top of descent, and when does it need to be selected for the guidance to be established before the pilot begins following it? Which vertical mode is appropriate for the approach phase, and at what point in the energy management sequence does it need to be engaged? Where will the autothrottle mode need to change, and what is the trigger?

These questions answered during the brief — in the low-workload environment before the demanding phase — require no capacity during the phase itself. The selection point has been identified. Both pilots know what is coming. When the moment arrives, the request goes to the PM clearly and without deliberation, the selection is made, and the engagement is confirmed before the pilot flying has committed their guidance following to the new mode. That sequence, executed smoothly, is what timely mode selection looks like from the outside — unremarkable, efficient, and always slightly ahead of the situation.

Mode Selection Through the Crew

When the pilot flying is hand-flying the aircraft, FMS reprogramming and guidance mode selection are the pilot monitoring's responsibility. This is not a delegation decision made in the moment — it is standard operating procedure. The manually flying pilot does not reach for the FMS or the mode control panel. The distraction of doing so, and the risk of selecting incorrectly under the divided attention of simultaneously managing the controls, is precisely what the procedure is designed to prevent. The PF flies. The PM manages the systems.

Mode changes therefore happen through a structured exchange: the PF requests, the PM selects, the PM confirms engagement, and the PF acknowledges. This sequence works only if the request is clear, specific, and timely. A vague request produces uncertainty — the PM selecting a mode they are not sure was intended, or hesitating while they seek clarification, at precisely the moment the selection window is closing. A clear request — mode, target, timing — gives the PM everything needed to act without delay. The timeliness of the selection depends partly on the clarity of the communication that precedes it.

There is a sequencing discipline that follows from this. The PF needs to request the mode change early enough that the PM has time to select, confirm engagement, and read back the result before the PF needs to be following the new guidance. That chain — request, select, confirm, readback — takes time. The request that arrives at the moment the mode is needed is already too late. It needs to arrive early enough that the chain completes before the pilot commits to following the new bars.

Choosing the Right Level

This behaviour is about both mode and level — and in manual flight the level decision carries specific weight. The choice between flight director on or off, autothrottle active or disconnected, is a workload and monitoring decision as much as a technical one. Flight director on substantially reduces the cognitive demand of manual flying — the pilot follows commanded guidance rather than computing it. Autothrottle active removes the continuous thrust management task. Both are operationally valuable in the right phase.

But adding a guidance level also adds a monitoring task. Each additional system that is active is a system whose mode must be tracked, whose transitions must be anticipated, and whose potential reversions must be detected. The crew that selects the guidance level appropriate to the phase — enough automation to reduce workload without creating monitoring complexity that exceeds the crew's available capacity — is exercising the level selection discipline. It is not always more guidance. Sometimes, in a low-workload phase where the monitoring overhead of active systems exceeds their workload benefit, the correct level is less.