Detecting a deviation from the desired flight path and taking appropriate action sounds like a reactive behaviour. Something goes wrong, you notice, you correct. But that account places the performance entirely at the moment of correction — and by then, the outcome has already been shaped by everything that happened before. How large the deviation grew before it was detected. How much spare capacity was available to maintain the scan. Whether both pilots were working from the same picture of where the aircraft should be. The correction is the visible output. The quality of the behaviour is in everything upstream of it.
In manual flight, that upstream quality matters more than it does in automated flight. When the autopilot is managing the path, a deviation that escapes early detection is absorbed by the system — it continues executing, the crew has time to assess, and the correction is managed at the pace the situation allows. When the aircraft is being hand-flown, a deviation that is not caught early becomes a control problem. The inputs required to recover it are larger, more abrupt, and more demanding — and they arrive into a pilot who is already managing the full cognitive load of flying the aircraft manually.
The Reference You Cannot Do Without
A deviation can only be detected against a reference. Before the deviation can be noticed, the desired state must be known — by both pilots, explicitly, with the same understanding. The approach brief that establishes target speeds, configuration points, stabilisation criteria, and crew responsibilities is the document from which every subsequent deviation will be measured. In manual flight, that shared reference is more critical still, because the monitoring pilot's role expands substantially when the autopilot is off.
With automation engaged, the system is cross-checking the path continuously. In manual flight, the pilot monitoring provides that cross-check. They watch the instruments the pilot flying cannot divide their attention to cover, track the energy state, and call deviations when they appear. That function only works if the monitoring pilot knows precisely what they are monitoring against. A PM who has a different speed target from the one the PF is flying, or who is uncertain of the profile the crew agreed to fly, cannot reliably detect a departure from it. The shared reference built at the briefing is not a procedural nicety — it is the operational precondition for the monitoring function to work at all.
In manual flight the monitoring pilot is the cross-check that automation would otherwise provide. That role only works if both pilots are monitoring against the same reference.
Scan Discipline Under the Pressure of Flying
The second condition for early detection is continuous, disciplined instrument scan. And here is where manual flight creates its specific challenge: the pilot flying is already consuming cognitive bandwidth to fly the aircraft. Attitude management, power adjustments, trim, the physical coordination of inputs — none of that is free. It takes capacity. And the capacity it takes is the same capacity required for the scan that catches deviations early.
This is not a reason to avoid manual flying. It is the reason that scan discipline in manual flight has to be deliberate and habitual rather than incidental. The pilot who hand-flies with a well-established scan pattern — whose instrument cross-check is a practised routine rather than something constructed in the moment — maintains monitoring quality despite the demands of the physical task. The pilot whose scan is less ingrained finds it the first thing to narrow when workload increases. When the scan narrows, deviations grow before they are caught. When deviations grow, the corrections are larger. The diagnostic holds.
The Manual Correction and What It Must Not Do
When a deviation is detected in manual flight, the correction is a physical input — a control deflection, a power adjustment, a pitch change. The discipline of the correction matters as much as its timeliness. An overcorrection in manual flight does not produce a neatly managed outcome; it produces a deviation in the opposite direction, with the same monitoring problem now running in reverse. The aircraft oscillates. The workload increases. The scan that was already managing the demands of hand-flying is now tracking a self-generated disturbance.
Appropriate action in manual flight means proportionate input. The correction should be sized to the deviation — small for a small departure, measured for a larger one — and applied smoothly enough that the aircraft moves towards the desired state without overshooting it. That precision is only available when the deviation was caught early. A small deviation requires a small correction and is correctable smoothly. A large deviation under workload pressure invites the abrupt input that makes things worse before they get better.
The most common pattern in flight path deviations during manual flight is not poor technique — it is distraction. An ATC instruction, a system message, a query from the cabin. The aircraft does not pause while the pilot's attention is elsewhere. The speed trend that began as a minor drift continues uninterrupted. By the time the pilot's attention returns to the instruments, the deviation is larger than it would have been, the correction required is larger, and the workload of applying it competes directly with re-establishing the scan.
The PM's role during any distraction of the PF is to hold the monitoring thread — to track the path and energy state continuously and call the deviation before it compounds. That is not a passive watching brief. It is an active safety function that requires the PM to remain genuinely engaged with the flight path even while the PF is occupied elsewhere.
Calling the Deviation — The Crew Dimension
In a two-crew environment, deviation detection is a shared responsibility with a specific division. The pilot flying is managing the aircraft. The pilot monitoring is providing the cross-check. When the PM detects a deviation — a speed trend, an altitude drift, a path departure — the callout is the behaviour made operational. It must be clear, timely, and specific enough that the PF knows what is happening and what the magnitude is.
That callout requires a crew environment where making it is comfortable and expected. The PM who hesitates, who softens the call to the point where its urgency is unclear, or who does not call at all because the atmosphere does not invite it, has allowed the operational environment to override the safety function. The pilot who detects a deviation in their own flying and acknowledges it openly — rather than quietly correcting and hoping it went unnoticed — builds exactly the culture that makes the next callout easier. The colleague will always know. Transparent correction is not an admission of weakness. It is the professional standard.
Across Every Sector
High Performance Pilot structures your development of Detects Deviations from the Desired Aircraft Trajectory and Takes Appropriate Action across Foundation, Proficient, and Mastery levels. Free to start.
Start Free — highperformancepilot.com