December 7, 2011
What Really Happened Aboard Air France 447
An analysis of the Air France 447 disaster through the lens of decision-making under pressure, OODA loops, and the tempo of crisis.
6 min read
On June 1, 2009, Air France Flight 447 fell out of the sky over the Atlantic Ocean. All 228 people on board died. The aircraft, an Airbus A330, was technologically sophisticated. The crew was experienced. The weather was bad but not extraordinary - thunderstorms over the intertropical convergence zone, which is a normal hazard on the route between Rio de Janeiro and Paris.
The black boxes were recovered from the ocean floor two years later. The transcript of the cockpit voice recorder reveals something more disturbing than mechanical failure. It reveals a decision-making breakdown so complete that a flyable aircraft was crashed into the sea by pilots who never understood what was happening to them.
The Sequence
Here is what happened, simplified but accurate.
The aircraft entered an area of turbulence. Ice crystals blocked the pitot tubes - the external sensors that measure airspeed. Without reliable airspeed data, the autopilot disconnected. This is by design. When the autopilot cannot trust its inputs, it hands control back to the humans.
At this point, the aircraft was flying normally. It was at cruise altitude, in stable flight. All the pilots needed to do was maintain the current attitude and wait for the pitot tubes to clear, which they did within about a minute.
Instead, the co-pilot at the controls pulled back on the stick. The aircraft's nose rose. It began to climb. As it climbed, it slowed. As it slowed, the angle of attack increased. The wings began to lose lift. The stall warning activated.
For the next three and a half minutes, the aircraft was in a stall. The stall warning sounded repeatedly. The aircraft was descending at nearly 11,000 feet per minute. The nose was pitched up. The solution was simple and every pilot learns it on day one: push the nose down to regain airspeed. The co-pilot never did. He kept pulling back.
The aircraft hit the ocean at high speed. Everyone died.
The OODA Breakdown
From a decision-making perspective, what happened is a textbook case of OODA loop failure. Not a failure of speed - the pilots had three and a half minutes, which is an eternity in aviation terms. A failure of orientation.
When the autopilot disconnected, the pilots' orientation was disrupted. They were accustomed to monitoring the autopilot, not flying manually at altitude. The transition from automated to manual control required a shift in mental models - from "supervise the system" to "fly the airplane" - and the shift did not happen cleanly.
The co-pilot's initial pull-back on the stick suggests he was oriented toward climbing, as if the aircraft were in a dangerous descent. It was not. But without reliable airspeed data, he could not confirm this through instruments. He fell back on instinct, and his instinct was wrong.
Once the stall began, a second orientation failure occurred. The stall warning was sounding, but the co-pilot did not recognize the situation as a stall. How is this possible? Partly because high-altitude stalls are rare in commercial aviation. He had no experiential template for one. His training had covered stalls, but at low altitude and low speed - a very different sensory environment. The situation he was in did not match any pattern in his orientation.
This is the sensemaking cliff in action. The crew's existing mental models stopped working, and they could not build new ones fast enough. The tempo of the crisis outpaced the tempo of their adaptation.
The Tempo of Crisis
Three and a half minutes. That is how long the aircraft was falling. In normal life, three and a half minutes is nothing. You spend more time than that choosing what to order for lunch. But in a crisis, time behaves differently.
The tempo of the cockpit during those minutes was catastrophically wrong. The crew was operating at the tempo of confusion rather than the tempo of action. They were talking past each other. The captain, who had been resting and returned to the cockpit mid-crisis, did not take explicit command. The co-pilot at the controls did not communicate clearly what he was doing with the stick. The other co-pilot called out the stall but did not override his colleague.
In Boyd's terms, the entire crew was stuck in the orient phase. They were trying to figure out what was happening, but they could not, and while they tried to figure it out, the aircraft continued to fall. The decide and act phases were not absent - the co-pilot was acting, pulling back on the stick - but the actions were disconnected from accurate orientation. He was acting on a wrong model.
What Should Have Happened
The correct response was known, practiced, and simple. When the stall warning sounds, push the nose down. Trade altitude for airspeed. Regain lift. Fly the airplane.
The phrase "fly the airplane" is a mantra in aviation. It means: when everything is confusing and nothing makes sense, do the most basic thing. Maintain control of the aircraft. Everything else - diagnosis, communication, troubleshooting - is secondary to the fundamental task of keeping the wings flying.
The Air France crew lost this thread. They got absorbed in trying to understand the instruments, trying to understand each other, trying to understand the situation. And while they were trying to understand, they were not flying the airplane.
The Broader Lesson
This is not just an aviation story. It is a story about what happens when stress failure meets orientation failure. Under extreme stress, people revert to their most practiced responses. If those responses fit the situation, they survive. If those responses do not fit - if the situation is novel enough to fall outside their training - they fail.
The defense against this failure is not more training on specific scenarios. You cannot train for every possible crisis. The defense is training the meta-skill: recognizing when your orientation has broken down and defaulting to the simplest, most robust action available. Fly the airplane. Push the nose down. Do the basic thing.
In everyday decision-making, the equivalent is: when you are confused and the situation is deteriorating, stop trying to develop a complete understanding. Take the simplest action that stabilizes the situation. Then reassess. A partial action based on incomplete understanding is almost always better than no action based on a futile search for complete understanding.
The crew of Air France 447 searched for understanding while the ocean rushed up to meet them. They had enough time. They had enough training. They had enough aircraft. What they did not have was the ability to recognize that their understanding had failed and to fall back on the simplest possible response.
That is what really happened aboard Air France 447. And it is a lesson worth remembering every time you find yourself in a situation where nothing makes sense and the clock is running.
Related
- A Moment of Silence with John Boyd - The OODA framework that explains this failure
- Ready-Fire-Aim with Wild Bill - When acting without full understanding is the right move
- Tempo and OODA - The Backstory - The intellectual framework behind this analysis