It's More Than
Just a Button

The autopilot began as a wing leveller. A basic device that removed the need for constant physical input to keep the aircraft upright — allowing the pilot to take their hands and feet off the controls without the aircraft immediately departing from level flight. From that starting point, automation evolved across decades into something qualitatively different: full flight management systems capable of managing lateral and vertical profiles, executing instrument approaches to minima, protecting the aircraft from exceeding its flight envelope, and integrating with navigation databases to fly precise four-dimensional paths across continents.

That evolution transformed the pilot's relationship with the aircraft. The physical act of flying — the continuous scan, the constant corrections, the hands and feet responding to every deviation — was progressively replaced by the cognitive act of managing the system that does it. Uses automation to manage workload is the behaviour that sits at the centre of that transformation. And it is far more demanding than its name suggests.

The Workload Didn't Disappear

A common misreading of automation is that it reduces workload by transferring work from the crew to the system. That is true of physical workload. The PF is no longer making continuous control inputs to maintain the flight path. The cognitive workload, however, did not transfer — it transformed.

Instead of being consumed with the physical act of flying, the crew is now consumed with monitoring, verification, task completion, efficient management and reviewing. The action-mode-response sequence that governs every interaction with the automation demands knowledge, attention and discipline. Mode awareness — knowing what the automation is doing, what it is about to do, and what it will do when it reaches its programmed limits — is a continuous cognitive task. It does not feel like work in the way that hand-flying does. But it requires the same quality of engaged, directed attention to do well.

The crew that treats automation as a simple workload reducer — that presses the button and disengages cognitively — has not reduced their workload. They have changed its nature while removing the disciplined engagement that makes it safe. The automation is managing the aircraft. Nobody is managing the automation.

The Shared Mental Model Is the Prerequisite

Automation only reduces workload if both crew members have the same picture of what the automation is doing, what it is about to do, and what they will do when it reaches its limits. Without that shared picture, the automation creates ambiguity rather than removing it. Two crew members operating from different understandings of the automation state are not a crew using automation to reduce workload — they are a crew carrying a hidden discrepancy that will surface at the worst possible moment.

Building the shared mental model requires a whole separate set of behaviours. The automation briefing that establishes the planned modes, the transition points, and the crew's response to deviations. The verbalisation of mode selections that confirms the selection and creates the shared expectation. The cross-checks that confirm both crew members are reading the same automation state. The communication that keeps the picture aligned as the automation transitions through phases.

None of that is passive. All of it requires active, deliberate crew behaviour. The automation briefing is not a preamble to using automation effectively. It is part of using it effectively. A crew that skips it — that assumes a shared understanding without building one — is operating with a picture that may or may not be shared, and has no reliable way of knowing which.

Does Automation Always Reduce Workload?

No. And understanding when it does not is as important as knowing how to use it when it does.

There are situations where the dynamics of the operation move faster than the automation can be managed. The final turn on a circling approach in deteriorating visibility. A visual approach with challenging terrain. An unexpected TCAS resolution advisory that requires immediate manual response. In these situations, the time required to programme, manage and verify the automation exceeds the time available for the manoeuvre. The correct response is to fly the aircraft directly — to disengage the automation and use the manual flying skill that the automation has been supplementing.

Making that judgement requires two things. Currency in the automation — knowing what it can and cannot do, and how quickly it can respond. And currency in manual flying — having the skill and confidence to take direct control when the situation demands it. A crew that has defaulted to automation in all conditions has potentially allowed manual flying proficiency to atrophy. When the moment arrives where manual flying is the right choice, they may lack the confidence to make it — or worse, the capability to execute it well when they do.

This is the dependency that over-reliance on automation creates. The automation that makes the routine operation more efficient can, if it becomes a crutch, reduce the capability available for the non-routine one. The crew that uses automation judiciously — that keeps manual flying currency, that knows where the automation's limits are, and that can make the switch when required — is the crew that gets the benefit of automation without incurring the cost.

The PM Is the Biggest Beneficiary

The most significant workload reduction that automation delivers is not to the PF. It is to the PM.

A PM monitoring a crew hand-flying a demanding approach is engaged, active, cross-checking constantly — flight path, energy, instruments, automation state. The monitoring workload is high. The spare capacity available for wider awareness — for thinking ahead, for anticipating threats, for maintaining the picture beyond the immediate — is limited.

A PM on a well-managed automated flight has a genuinely different capacity available. The physical flight path management is being handled by the system. The PM's attention — properly directed — can extend beyond the immediate instruments to the wider operational picture. Fuel state. Traffic. Weather ahead. The approach brief that needs to happen before the descent. The contingency that should be considered before it becomes necessary.

That is the real workload benefit of automation. Not that the PF has their hands free, but that the PM has their mind free — freed from the continuous monitoring of physical flight path management, and available for the higher-order SA and planning functions that keep the crew ahead of the aircraft. A crew that understands this uses automation strategically, not just routinely. They brief it, manage it, and monitor it with the understanding that its primary purpose is not to reduce effort but to create capacity — in the PM especially — for everything that benefits from it.