Manual flight is not a single state. Between full autopilot engagement and raw data flying lies a spectrum of partial automation — and operating at that intermediate level is one of the most common and most demanding configurations in line flying. The autopilot is off. The pilot is flying the aircraft with their hands. But the flight director is active, issuing continuous guidance commands. The autothrottle may be managing thrust. Vertical and lateral modes are engaged, and they will transition automatically as conditions are met — capturing the cleared altitude, sequencing a constraint, responding to an energy state the system has evaluated independently.
This configuration is operationally valuable. Flight director guidance substantially reduces the cognitive demand of manual flight — the pilot follows commanded pitch and roll rather than computing the required attitude from first principles. Autothrottle removes the continuous thrust management task. Together, they make hand-flying in busy terminal airspace manageable in a way that raw data flight would not be. The workload is lower than full manual. The situation awareness demand is higher than full automation. And the monitoring task is specifically different from both — because the guidance systems are still active, still making decisions, and still capable of doing something unexpected, while the pilot's hands and primary attention are already committed to flying the aircraft.
What Partial Automation Actually Demands
In fully automated flight, the autopilot is managing the path and the crew is monitoring the automation. The division is clear. In raw data manual flight, there is no automation to monitor — the pilot is computing everything internally, and the instrument scan covers the aircraft's state directly. In the partial automation configuration, both tasks run simultaneously. The pilot is flying the aircraft and monitoring the guidance systems that are assisting them. Neither task can be suspended for the other.
This is the specific challenge this behaviour addresses. The flight director is issuing commands that must be followed for the guidance to be meaningful. The autothrottle is managing thrust that must be cross-checked against the energy state. And the modes governing both are transitioning automatically — altitude capture is the most common example, but vertical speed to path transitions, speed mode changes during configuration, and lateral mode sequencing all occur without a discrete crew input. Each automatic transition is a change in what the system is doing, and each one requires the crew to verify that what the system has decided to do is what the situation actually requires.
In partial automation, the pilot is following the flight director and monitoring what it is doing simultaneously. Neither task is optional. Both require active attention from a crew whose capacity is already reduced by hand-flying.
Action, Mode, Response — When There Was No Action
The Action-Mode-Response discipline that underpins effective guidance system monitoring was designed around discrete crew inputs — a mode selection, a target entry, a system engagement. Action: what was selected. Mode: confirmation that the annunciator reflects the intended mode. Response: verification that the aircraft is actually behaving as the mode should produce. Three steps. Every time.
In partial automation during manual flight, the hardest version of this discipline is when there was no crew action — when the mode transition happened automatically. Altitude capture is the classic case. The crew did not press a button. The system evaluated the aircraft's position relative to the cleared level and initiated the capture sequence autonomously. The pilot flying is managing the pitch response to follow the flight director through the capture. The pilot monitoring needs to be watching the mode annunciator to confirm the capture has engaged, checking the captured target matches the cleared level, and verifying that the aircraft's rate of level-off is consistent with what the mode should produce.
All of that is Response monitoring for a transition that had no Action and no discrete Mode selection moment to anchor it. The discipline has to be habitual and continuous rather than triggered by a crew input — because the trigger was the system's own logic, not the crew's.
The approach to the cleared level in manual flight with the flight director active illustrates the monitoring demand clearly. The FD commands a reducing pitch attitude as the aircraft approaches the target altitude. The pilot follows. The autothrottle adjusts thrust to maintain speed through the level-off. The mode transitions from VS or FPA to ALT — automatically, when the system determines the conditions are met.
The monitoring task during this sequence: is the FD commanding correctly for the energy state? Is the altitude capture engaging at the right point? Is the captured target the correct level? Is the autothrottle mode consistent with level flight at this speed? All of this is happening while the pilot is physically flying the aircraft through a manoeuvre that requires continuous control inputs. The monitoring is not a break from the flying task — it runs alongside it, with the same crew.
Mode Reversion — The Risk That Doesn't Announce Itself
Automatic mode transitions are expected and planned for. Mode reversions are different — they are the system retreating to a lesser capability because the current mode can no longer perform its function. And in partial automation during manual flight, the reversion risk changes character in an important way.
In fully automated flight, a mode reversion changes what the autopilot is doing. The flight path may begin to diverge from the intended profile, and the monitoring crew detects it. In manual flight with the flight director active, a mode reversion changes what the flight director is commanding. The pilot following the FD bars will follow the reversion — potentially without realising the guidance has changed — because the FD continues to issue commands regardless of which mode is driving them. An autothrottle reversion from speed mode to a thrust limit mode will change the thrust management without a discrete annunciation that demands attention. The aircraft's speed will begin to move, and the pilot following the FD may not immediately connect the speed trend to a mode change they did not notice.
This is the specific monitoring hazard of partial automation: the pilot is following guidance that may have changed without their knowledge, and the aircraft is complying with what they are asking it to do, which is now not what they intended. Detecting this requires the PM to hold the mode picture continuously — not just checking the annunciator when something draws attention, but maintaining a running awareness of what mode the system is in and whether that matches the last known state.
Mode Selection — The Increased Stakes
When hand-flying with guidance systems active, mode selection decisions carry higher stakes than in fully automated flight. In full automation, selecting the wrong mode or a mode that is not appropriate for the current situation produces a path deviation that the monitoring crew detects and corrects. In partial automation, selecting the wrong mode produces guidance that the pilot then physically follows — potentially compounding the error through the control inputs made in response to incorrect FD commands.
This makes the pre-selection discipline — knowing what mode is needed, understanding what conditions it requires to capture, and verifying engagement before following the guidance — more critical in partial automation than in full. A mode that will not capture needs to be identified before the pilot begins following bars that are leading the aircraft to the wrong state. A mode selected at the wrong phase of the energy management sequence will issue commands that are correct for the mode but wrong for the situation. The Action-Mode-Response sequence exists precisely to catch these errors at the selection stage rather than after the pilot has followed the guidance into an unintended flight path.
The PM Role — Holding the Mode Picture
In partial automation during manual flight, the division of labour between PF and PM is especially important. The pilot flying is managing the aircraft through the controls and following the flight director. Their primary attention is on the physical task of hand-flying and on the FD command bars. The pilot monitoring holds the mode picture — maintaining continuous awareness of which modes are active, what transitions are expected, and whether the annunciator state matches the crew's intentions.
This is a substantive and active role. It requires the PM to scan the flight mode annunciator regularly, to anticipate automatic transitions and call them when they occur, and to detect reversions that the pilot flying may not have noticed. The PM who is passively watching while the PF hand-flies has left the mode monitoring function unmanned. The PM who actively holds the guidance system picture provides the layer of oversight that makes partial automation safe — the second set of eyes on the system state that the pilot flying cannot consistently provide while their hands are on the controls.
Mode Changes Through the Crew
There is a further dimension to partial automation during manual flight that is easy to overlook: when the pilot flying's hands are on the controls, mode selections migrate to the pilot monitoring. The PF cannot safely release the controls to reprogram the FMS or select a new vertical mode at a critical phase of flight. The request goes to the PM — and that request, and its execution, and its verification, all have to happen through communication.
This adds a layer of workload to both pilots. The PF must formulate and transmit a clear, concise request — the right mode, the right target, at the right moment — while continuing to fly the aircraft. The PM must receive it accurately, execute it correctly, and confirm the result, while maintaining their own monitoring picture. The exchange is brief by necessity. It has to be, because neither pilot has capacity to spare. But it has to be precise, because an ambiguous request or an unconfirmed selection introduces exactly the kind of mode uncertainty that the monitoring discipline exists to prevent.
What this communication exchange earns, despite its workload cost, is a shared mental model. When the PF requests a mode change and the PM reads back the selection and confirms engagement, both pilots know the same thing about the guidance system state. The picture is aligned. Compare that to the alternative — a PM who selects a mode without a clear request and reads back only to themselves — and the value of the exchange becomes clear. The brief, disciplined communication around mode changes is not a procedural nicety. It is the mechanism that keeps both pilots working from the same picture of what the guidance systems are doing, in a configuration where that shared awareness is the primary defence against undetected mode changes going unmanaged.
Across Every Sector
High Performance Pilot structures your development of Effectively Monitors Flight Guidance Systems Including Engagement and Automatic Mode Transitions across Foundation, Proficient, and Mastery levels. Free to start.
Start Free — highperformancepilot.com