
I want to walk you through a set of important human-performance pitfalls that come with advanced automation in the cockpit. These are traps that professional pilots must recognise and actively guard against.
First, there is the problem of greater delays between the performance of the crew and its ultimate effect. What does that mean? In a traditional aircraft, if you move the controls, the aircraft responds immediately — you see the result right away. But with automated systems, an action you take now might not show its consequence until much later. For example, an incorrect entry of a waypoint into the flight management computer may not become apparent until hours later. The book gives a classic example: the Air New Zealand DC-10 crash into Mount Erebus. In that case, ground personnel entered an incorrect waypoint into the computer, and the crew had no immediate indication of the error. The consequence only became obvious when the aircraft flew into terrain. So the delay between the action and its effect can be very long, and that makes it harder for the crew to detect and correct mistakes in real time.
Next, we have automation complacency. This is defined as an over-reliance on automation, and the classic symptom of it is passive monitoring. That means the crew stops actively watching and thinking about what the automation is doing. They tend to "leave it up to the computer to sort out" and accept, in blind belief, that the automation is more capable of monitoring the flight path and of finding solutions. The book is very clear here: continued, active, and deliberate monitoring of the systems is an absolute necessity. You cannot just sit back and trust the computer to handle everything.
There is a danger that the pilot may come to regard the aircraft as infallible — as if it can cope with impossible situations. The book gives a vivid example: it is no use flying an unstallable aircraft if the pilot has placed it at low level and low airspeed, with no energy available to fly away from the problem. The automation does not absolve the pilot from operating in a way that complies with the basic requirements for safe flight. In other words, the pilot remains responsible for the fundamental aerodynamic and energy-state safety of the aircraft, regardless of how sophisticated the automation is.
Finally, there is blinkered concentration. This is the possibility of becoming so involved in a single readout that you lose situational awareness. You fixate on one instrument or one piece of data, and you stop seeing the big picture. The book gives a practical piece of advice: always remember that a readout that causes consternation can, in 99% of cases, be cross-checked with alternate instruments. So if something on one display alarms you, don't stare at it — look at other instruments to verify or disprove what you think you're seeing.
Let me bring in a diagram that illustrates these concepts. That figure shows "Protected and vulnerable systems" — it helps you visualise how the automated systems are meant to protect the flight, but also where the vulnerabilities lie when the crew falls into these traps. The key takeaway is that automation is a tool, not a replacement for the pilot's active, deliberate, and continuous monitoring and decision-making.
This is one saved preview. Continue from this exact book or paper with BlueFlash voice AI.
Continue in BlueFlash