The automation delivers what you ask of it. That sentence contains a significant assumption — that you know what you are asking for. Managing the flight path to achieve optimum operational performance is not primarily a technical behaviour. It is a planning behaviour. The technical execution, when the planning is done well, follows with relatively little effort. When the planning has not been done, the execution becomes an improvisation: a series of reactive adjustments to a situation that was never clearly defined.
The word optimum is doing real work here, and it is worth examining what it means in practice. On any given flight, optimum is the intersection of several competing constraints: the fuel plan, noise abatement requirements, passenger comfort, track miles, continuous descent arrival procedures, airspace restrictions, and the performance capabilities of the specific aircraft on that day. None of these is fixed. Each of them varies by flight. And the crew that has not thought through that intersection before the demanding phases arrive will be thinking through it during them — which is the least efficient time to do so.
Optimum Is a Decision, Not a Default
The default is whatever the FMS produces when you load the flight plan. For many flights, on many sectors, that default is also the optimum — and flying it with precision is the entirety of the task. But treating the default as the optimum without examining whether it actually is, on this flight, in these conditions, is not a plan. It is an assumption. And assumptions about the desired flight path are exactly the kind of assumption that produces the most avoidable deviations.
The crew that defines optimum explicitly — that asks, during the briefing, what the priority is for this descent: track miles, fuel, noise, or schedule — has created a shared reference point. Both pilots know what the aircraft should be doing and why. Deviations from that plan are recognisable because the plan is explicit. Adjustments to the plan, as conditions evolve, can be evaluated against a known baseline. The crew is not improvising. They are adapting a plan.
The automation does exactly what it is asked. The behaviour is in knowing what to ask — and asking it precisely enough that the answer is the right one for this flight.
Understanding How the Aircraft Will Respond
Optimum performance is not simply a target. It is an outcome produced by the interaction between the planned profile and the aircraft's actual performance on the day. Temperature, weight, wind, the specific thrust characteristics of the engines — all of these affect where the aircraft will be at any given point in the profile, and whether the plan as briefed will produce the outcome as intended.
This is where Application of Knowledge does its practical work. The crew that understands how the automation will manage the descent — how the FMS calculates the top of descent, how it responds to speed constraints, at what point it will transition between managed modes — is the crew that can anticipate where the profile may need active management rather than passive monitoring. They know which constraints are tight on this sector. They know where the energy state will be most sensitive. They have briefed the points where they expect to intervene, and what that intervention will look like.
The crew that does not have that understanding flies the descent reactively — responding to what the automation does rather than managing what it should do. Both crews may arrive at the same point. But one of them was in control of the outcome; the other was following it.
The continuous descent arrival is the clearest expression of this behaviour. It is a procedure designed to deliver specific performance outcomes — noise reduction, fuel efficiency, track mile compression — and it does so only if the energy management is precise from the top of descent. The crew that has planned the descent with the CDA constraints explicitly in mind, that has briefed the speed schedule and the likely intervention points, and that monitors the profile against the plan rather than the FMS against itself, is the crew for whom the CDA delivers its intended benefits.
The crew that loads the CDA and monitors passively discovers at the FAF that the energy state is not where it needs to be — and that the efficiency the procedure was designed to deliver has already been lost in the management of it.
Briefing the Strategy
The planning work becomes operational through the briefing. This is where the defined optimum, the anticipated aircraft response, and the agreed crew strategy are converted into a shared mental model that both pilots hold. A briefing that is specific about the intended profile — the target speeds, the configuration points, the energy management gates, the likely automation interventions, and the crew's agreed response to each — produces a crew that is genuinely aligned. Both pilots are managing the same flight.
A briefing that is vague about these elements produces a crew that is each managing the flight they individually expect, which may or may not be the same flight. The divergence between two mental models that were never explicitly aligned is not visible until execution reveals it — usually during the most demanding phase of the sector.
The briefing is also where the performance margins are established. The approach brief is not simply a recitation of limits. It is a plan: this is what optimum looks like on this approach, these are the energy gates we are targeting, this is the point at which we will assess whether the profile is sustainable. That plan is what makes the execution of the approach a managed process rather than a reactive one.
Execution as Active Management
With the planning done and the briefing complete, execution is the ongoing comparison of actual against planned — and the adjustment that keeps the two aligned. This is where the monitoring discipline that underpins all of Flight Path Management is most directly expressed. The crew that continuously cross-checks the actual energy state against the planned profile — that does not assume the automation is delivering the intended outcome simply because it has not alarmed — is the crew whose execution is genuinely managed.
The adjustments that optimum performance requires are almost always small when the monitoring is continuous. A speed target adjusted slightly earlier. An automation mode selected to prevent an energy shortfall developing. A rate of descent modified at a gate where the profile is running slightly high. These are the corrections of a crew in front of the aircraft — managing the profile rather than following it.
When the monitoring is intermittent, the adjustments become larger. The energy shortfall that was a small trend ten miles back is now a meaningful deficit. The correction required is more significant, the workload higher, and the optimum outcome that was achievable with small adjustments may now require a compromise. This is the execution cost of planning that was not followed by active management — and it is entirely predictable from the quality of the monitoring that preceded it.
On the Line
High Performance Pilot structures your development of Manages the Flight Path to Achieve Optimum Operational Performance across three levels — Foundation, Proficient, and Mastery. Each session takes minutes. The development happens on every flight. Free to start.
Start Free — highperformancepilot.com