The 737 MAX Showed Us What Documents Can Hide

The Crash That Took 346 Lives

On March 10, 2019, Ethiopian Airlines Flight 302 crashed six minutes after takeoff from Addis Ababa. Everyone on board died. It was the second catastrophe involving the Boeing 737 MAX in just five months. The first, Lion Air Flight 610, had gone down in the Java Sea that October, killing all 189 people on board. Together, 346 lives were lost.

The immediate culprit was a software system called the Maneuvering Characteristics Augmentation System, or MCAS. It was designed to automatically push the plane's nose down to prevent a stall. But a faulty angle-of-attack sensor caused it to trigger repeatedly, putting the pilots in a fight they couldn't win. They didn't know the system existed. It wasn't in their flight manuals. It wasn't in their training. That's not an engineering failure, it's a document analysis failure.

And it wasn't just the pilots who were kept in the dark. The airlines that bought the MAX didn't fully understand the system either. According to the final report from Indonesia's National Transportation Safety Committee, the Lion Air flight crew was struggling with conflicting sensor readings, and neither the manual nor the pre-flight checklist gave them any insight into what MCAS was doing. The Ethiopian Airlines crew got a few seconds' warning from an automated message before the plane pitched down violently. They followed the standard recovery procedure, but their training didn't cover the possibility of a system that would re-trigger on its own. That's not a pilot problem. That's a systemic information failure.

You might be asking: what does this have to do with a boring contract you have to sign at work? More than you'd think. Because the same pattern, incomplete summaries, hidden changes, and a reliance on outdated descriptions, plays out in boardrooms and law firms every day. The most critical documents in your career will never cause a global tragedy. But they can cause a lot of damage if you don't ask the right questions.

That's why I want to walk you through exactly how Boeing's document trail failed, and then give you a field guide for protecting yourself. Because the next time you accept a one-page summary, you might be accepting a hidden MCAS.

How Boeing's Documents Misled Everyone

MCAS didn't appear out of nowhere. It was a workaround for the larger, heavier engines on the MAX, which changed the plane's aerodynamics. In certain flight conditions, the nose would rise too much, reducing airflow over the wings. MCAS would automatically push the nose down. That sounds like something you'd want to document thoroughly, right? Instead, the original flight manual described MCAS as a "speed augmentation" system.

"Augmentation" is a comforting word. It suggests a minor enhancement, not a system that could override the pilot. According to reporting from Reuters and other outlets, the official manual text gave MCAS only a few sentences. Pilots had no reason to suspect that this system could dive-bomb the plane. And it wasn't just the flight crew. Boeing's own safety analysis underestimated the risk of MCAS activation, and the FAA based its certification on that analysis.

In fact, the safety analysis was flawed in a fundamental way. Boeing assumed that a single point of failure, that one sensor sending bad data, was only a "hazardous" event, not "catastrophic." That distinction affected how much redundancy was required. If the analysis had classified it as catastrophic, the FAA likely would have demanded a second sensor and more training. But the paperwork chose the lower category. That's not just a miscalculation; it's an intentional framing that minimized the system's danger.

The result was a cascade of incomplete information that doomed the planes before they left the ground. Here's the part that should scare you: the people who wrote those documents believed they were telling the truth. They just didn't see the whole picture. They checked their boxes. They submitted the right forms. And a system that could kill people was approved.

This happens in business all the time. A contract writer might leave out a clause they consider boilerplate. A policy summary might ignore an exception that turns out to be the entire point. An engineer might update a spec without telling anyone. The MAX case shows the difference between a document that describes a system and a document that reveals how the system actually behaves. One is enough to look compliant. The other is what keeps people safe.

You see the same dynamic in due diligence. If you're reviewing an acquisition target, you read their contracts. But you're reading what they chose to share. The most important risks might be in the documents they didn't hand over, or in the missing version history. When you read with the attitude of "checking the boxes," you miss the depth. Document due diligence isn't about reading the words. It's about understanding the story behind them.

And the story here is that the documents were optimized for approval, not for transparency. Boeing needed the MAX to compete quickly. The FAA wanted to help. So the documentation became a checklist to pass, not a manual to protect. That's a lesson for anyone who signs a non-disclosure agreement, a lease, or a partnership agreement: ask yourself if the document you were given was created to inform you or to authorize something.

The One-Page Summary That Killed 189 People

Let's get specific about how pilots were trained. Going from an older 737 to the MAX required a short iPad-based course, not a full-flight simulator. Boeing and the FAA agreed that the differences were small enough that a one-page summary of changes would be enough. That summary didn't list MCAS as a functional system that could actively push the nose down. The exact number of pages varies by report, some say one, some say a few, but the core fact is consistent: the training omitted a dangerous system.

This should be a wake-up call for anyone who relies on summaries. When you condense a complex document, you make choices. Those choices are based on assumptions. The assumption here was that the MAX was basically a 737 with better fuel economy. So the summary was dangerously incomplete.

That's the summary trap. You read the executive brief of a contract, the TL;DR of a policy, or a third-party recap of a technical spec. But you never read the original. If the summary misses a key detail, you might be accepting a hidden MCAS.