The Path Holds Because
the Pilot Holds It

In automated flight there is a structural separation that makes task management more tractable. The autopilot holds the path. The crew manages the tasks. When something requires attention — an ATC amendment, a checklist, a system query — the crew can give that attention while the path continues to be maintained by the automation. The two demands do not compete for the same resource at the same moment. They are handled by different actors.

In manual flight that separation disappears. The pilot flying is the automation. When an ATC instruction arrives, the pilot handling it is the same pilot who is holding the aircraft on the desired track and altitude. The attention given to the task is attention taken from the path. There is no alternative actor maintaining the path in the background. The path is maintained continuously by the pilot's hands and scan — and the moment those are directed elsewhere, the path begins to drift.

This is the specific challenge this behaviour addresses. Not simply maintaining the path in benign conditions with full attention — that is the baseline. But maintaining it while the tasks that are a normal feature of line flying continue to arrive, and continue to require handling, in a crew configuration where the path cannot look after itself.

The Task That Cannot Be Paused

The instrument scan is the thread that connects the pilot to the aircraft's state. It is how the pilot knows what the aircraft is doing — speed, altitude, heading, rate — and how deviations are detected before they become consequential. In automated flight the scan is essential but operates against a relatively stable background. In manual flight the scan is the primary mechanism by which the path is maintained. It is not a monitoring task running alongside the flying task. It is the flying task.

When another task arrives — an ATC call to copy and read back, a PM query requiring a response, a checklist item requiring attention — the scan competes with it for the pilot's attention. In automated flight, the scan can be briefly interrupted because the automation continues to hold the path through the interruption. In manual flight, the scan interruption is a path management interruption. The aircraft continues moving. The speed trend that was developing continues developing. The altitude that was beginning to drift continues drifting. The interruption has a cost that is directly proportional to its duration and inversely proportional to the margin the pilot had at the moment it occurred.

The PM Role — Absorbing What the PF Cannot

The primary workload management tool when hand-flying through task demands is the pilot monitoring. The PM's role expands substantially in manual flight — not only to hold the monitoring picture that the automation would otherwise provide, but to absorb the tasks that the pilot flying cannot safely handle without interrupting the scan.

ATC communications during manual flight phases are the clearest example. The PF is hand-flying. The PM handles the RT exchange, copies the instruction, reads back, and communicates the relevant information to the PF at a moment when the PF can receive it without breaking their scan. The instruction is not relayed mid-turn, mid-correction, or mid-climb — it is held by the PM until there is a natural pause in the flying task where the PF has capacity to absorb it. This is not passive assistance. It is active workload management of the PF's scan discipline, carried out by the PM as a deliberate function.

Checklists, system queries, and non-urgent communications follow the same pattern. The PM holds them, sequences them to low-workload moments, and ensures the PF is never simultaneously managing a task and a flight path deviation. That sequencing is the PM's craft during a manual flying phase — and it requires the PM to maintain genuine awareness of the PF's current scan load and the aircraft's state, so that the timing of task delivery is informed rather than arbitrary.

Triage — What Can Wait

Not every task that arrives during a manual flying phase requires immediate handling. The skill of task triage — assessing what must be dealt with now, what can be deferred by thirty seconds, and what can wait until the manual flying phase is complete — is the workload management discipline that protects the scan during the tasks that cannot be deferred.

The briefing is where this triage framework is built. A crew that has agreed, before the manual flying phase, which tasks the PM will absorb entirely, which will be handed to the PF at defined moments, and which will be deferred until the aircraft is back on autopilot, enters the phase with an agreed plan rather than an improvised response. The improvised response is always more expensive — it requires decision-making under workload at precisely the moment when workload should be lowest.

What Good Looks Like From the Outside

A crew that manages this well is unremarkable to observe. The pilot flying maintains a stable, accurate flight path throughout. Tasks are handled. Communications are exchanged. Checklists are completed. The aircraft arrives at each phase transition in the intended state. Nothing about the performance signals that managing the path and the tasks simultaneously is difficult — because the upstream planning and role discipline have converted a genuinely demanding situation into a controlled one.

The measure of the behaviour is not whether tasks are handled. Tasks will always be handled one way or another. The measure is whether the flight path is maintained to standard throughout the handling of them. A crew that handles the tasks but allows the path to drift while doing so has not demonstrated this behaviour — they have demonstrated task management at the cost of flight path management. The path and the tasks must both be maintained, simultaneously, without either suffering at the expense of the other. That is the standard the behaviour requires, and it is the standard that distinguishes genuinely capable manual flying from merely adequate handling of the controls.