There is a version of automated flight that looks effortless from the outside. The aircraft tracks the cleared routing, maintains the assigned level, follows the speed constraints. The crew appear to have capacity available. Tasks are being handled. The flight is progressing. But beneath that visible competence, a continuous process is running — one that is easy to interrupt and difficult to resume cleanly once broken. The automation is managing the path. The crew is managing the automation. And that distinction matters enormously when something else requires attention.
The behaviour asks a specific question: can the crew maintain automation management — the active, attentive oversight of what the automation is doing and what it is about to do — whilst simultaneously handling the other demands that a normal flight generates? Not in clean conditions with nothing else happening. In real conditions, where ATC is issuing amendments, checklists are running, and the other pilot needs something at the same moment the FMS requires an input. The automation does not pause for any of this. Neither does its requirement to be monitored.
What Maintaining Means
Maintaining the desired flight path through automation is an active discipline, not a passive one. It requires continuous awareness of what the automation is currently doing, what it is programmed to do next, and whether those two things still match the cleared and intended routing. A mode that was appropriate three miles ago may not be appropriate now. A constraint that was programmed before the amendment may now conflict with the revised clearance. The automation will execute what it has been told — precisely, without interpretation, and without regard for whether the instruction is still correct.
This is the mode awareness connection. The crew that knows at every moment which modes are active, what the automation is targeting, and what transition is next is the crew that will catch the mismatch before it becomes a deviation. The crew whose mode awareness has drifted — whose picture of what the automation is doing no longer matches what it is actually doing — will discover the discrepancy when the aircraft departs from the intended path, not before.
The automation executes what it has been told. The crew's job is to ensure that what it has been told is still what is required — continuously, not just at the point of input.
The Task That Competes
Every task that requires the crew's attention is a task that is competing with automation monitoring. This is not a problem to be eliminated — tasks are a normal and unavoidable feature of line flying. It is a problem to be managed. The crew that treats every task as a potential interruption to monitoring — and plans accordingly — is the crew that maintains automation management through them. The crew that treats tasks as the primary activity and monitoring as what happens in between is the crew that allows the gaps to grow.
The workload management connection is direct. Triage — the discipline of assessing what a task actually requires and when it actually needs to be done — is the mechanism that keeps monitoring continuous. The amendment that needs to be programmed can often wait sixty seconds while the automation captures the current constraint. The checklist that needs to be completed can be started at a point where the automation is stable and the monitoring requirement is lower. These are not delays. They are the sequencing decisions that protect monitoring quality.
The crew that has briefed their sequencing approach for the demanding phases — who handles what, when, and in what order — is the crew that enters those phases with an agreed framework for managing the competition between tasks and monitoring. The crew that has not had that conversation manages it reactively, which is the most cognitively expensive way to do it.
The most demanding version of this behaviour is the ATC amendment that arrives at a critical phase of the flight — a speed restriction during the descent, a re-routing that requires FMS reprogramming while the aircraft is actively managing a constraint. The amendment must be handled. The automation must continue to be monitored. Both are true simultaneously.
The crew that has anticipated this scenario — that has agreed who programs and who monitors, and that cross-checks the programmed amendment against the clearance before executing — manages it as a controlled event. The crew that has not anticipated it manages it as a crisis, with all the workload that implies.
The Monitoring Pilot's Specific Role
In a two-crew environment, automation monitoring is a shared responsibility with a specific division. When the pilot managing the aircraft is occupied with a task — programming an amendment, running a checklist, handling an ATC exchange — the pilot monitoring holds the automation picture. They maintain awareness of the active modes, the programmed targets, and the aircraft's actual behaviour. They are the crew's connection to the automation during the period when the managing pilot's attention is elsewhere.
That responsibility requires the monitoring pilot to remain genuinely engaged with the automation state throughout. A monitoring pilot who is also occupied — who has allowed their own attention to migrate to the same task that is occupying the managing pilot — has left the automation unmonitored. Both pilots are heads-down. The automation is running. Nobody is watching what it is about to do.
This is the point where most automation-related path deviations originate. Not from complexity. Not from system failure. From both crew members being occupied with something else at the same moment, for a period long enough that the automation departs from the intended path without the departure being noticed until it has become consequential.
Cross-Checking Before Executing
Every FMS input made whilst the aircraft is flying has the potential to change what the automation does next. The amendment that looks straightforward on the ground — re-routing around weather, accepting a revised arrival — can produce unexpected automation behaviour in the air when it interacts with existing constraints, active modes, or the aircraft's current energy state. The crew that programmes the amendment and immediately cross-checks that the automation has captured the intended result — that the magenta line goes where it should, that the modes have transitioned as expected, that the constraints are correct — is the crew that catches the unintended consequence before it affects the path.
The crew that programmes and moves on, trusting that the automation has done what was intended, will eventually encounter the case where it has not. The cross-check is not a sign of distrust in the system. It is the verification step that closes the loop between input and outcome — the last line of defence against the gap between what was programmed and what the automation understood.
Across Every Sector
High Performance Pilot structures your development of Maintains the Desired Flight Path During Flight Using Automation Whilst Managing Other Tasks across three levels — Foundation, Proficient, and Mastery. Free to start.
Start Free — highperformancepilot.com