Failure Museum.Made with ❤️ by Aniruddh Jangid
Submit a case

EXHIBIT 085 · TRANSPORTATION

737 MAX: automation, certification, and the pilot’s mental model

Two fatal crashes led to worldwide grounding and scrutiny of design and certification.

OrganizationBoeing / FAA
Period2019
LocationGlobal
StatusPartially recovered
ImpactCritical
EvidencePrimary documentation
Compare

Illustrative draft · Source-backed synopsis · Museum analysis marked separately · Updated 5 October 2026

Undelivered Boeing 737 MAX aircraft parked near Boeing Field in Seattle during the April 2019 grounding.
Undelivered Boeing 737 MAX aircraft parked near Boeing Field in Seattle during the April 2019 grounding.SounderBruce / Wikimedia Commons. Resized. Photograph · CC BY-SA 4.0 · Resized for display.
01 / EXECUTIVE SUMMARY

The outcome is only the beginning.

Two fatal crashes led to worldwide grounding and scrutiny of design and certification. [1]

THE PRINCIPLE TO CARRY FORWARD

Test fault scenarios with representative crews and disclose safety-critical automation behavior clearly.

02 / THE PROMISE

What the system was trying to do.

Deliver a fuel-efficient aircraft safely within a familiar operating model.

Museum interpretation

The assumption beneath the promise

Museum hypothesis to examine: People will infer the true physical state and automation mode from the information available under stress. This is an analytical proposition to test against the record, not an attributed statement by the organization.

Success should be assessed against the intended service and its safety, reliability, or integrity constraints. A headline outcome cannot tell us whether those constraints were visible, tested, or owned before the event.

03 / WHAT HAPPENED

A sequence, not a single moment.

The intended system

Deliver a fuel-efficient aircraft safely within a familiar operating model.

Source-backed synopsis

The event or review

Two fatal crashes led to worldwide grounding and scrutiny of design and certification. [1]

Source-backed synopsis

The documented aftermath

Investigations, software changes, and revised training preceded return-to-service approvals. [1]

Source-backed synopsis
Timeline of documented milestones. Gaps are not evidence that nothing happened. Sources: [1]
04 / WARNING SIGNS

What could be seen at the time?

Documented in cited record

The congressional hearing examined MCAS, information provided to pilots, and the certification process. [1]

Who could see it?

See the cited investigation for named teams and the information they held. The synopsis does not infer awareness by every stakeholder.

Why was it not enough?

Signals need interpretation, authority, and a route to action. This is an analytical question, not proof that a warning was deliberately ignored.

05 / KEY DECISIONS

Choices made within constraints.

Museum analysis: Automation design needed to account for sensor failure, repeated activation, and realistic crew response.

Available alternatives

Pause, test, narrow the operating envelope, seek independent review, or build a recovery option. These are proposed analytical alternatives; feasibility at the time is not established.

Information available

The congressional hearing examined MCAS, information provided to pilots, and the certification process. [1]

Incentives & constraints

Delivery pressure, cost, authority, and incomplete knowledge may shape a decision. Their specific weight is not established by this synopsis.

Risk accepted

Ask whether the relevant risk was recognized, who had authority to accept it, and whether affected people understood its implications.

06 / SYSTEM MAP

How conditions connected.

Select a node to inspect its evidence. Links show a proposed analytical relationship, not a measured causal effect.

05 / External context04 / Warning signal03 / Decisions02 / Technical conditions01 / Trigger06 / Consequences
Triggering event

Two fatal crashes led to worldwide grounding and scrutiny of design and certification. [1]

Legend: numbered nodes = analytical categories; dashed arrows = proposed influence or propagation. Museum interpretation informed by the sources below. Feedback and omitted influences require further investigation.
07 / CONSEQUENCES

Beyond the immediate event.

Passengers and crews died; airlines and travelers faced extended disruption. [1]

Technical impactOperational impactHuman impact

Categories identify documented or relevant consequences. Financial, human, and environmental totals are not estimated here when the source base does not support them.

08 / WHAT THE MODELS EXPLAIN

More than one lens.

Analytical lens

Swiss Cheese Model

Harm can pass through gaps in multiple defenses: organizational influences, supervision, preconditions, and active failures.

In this case, use the lens to examine human-system interaction. This application is museum interpretation, not a finding of the original investigation.

Limit: A useful lens, not proof of a universal linear cause. Barriers interact and change over time.

Analytical lens

FMEA

Identify failure modes, their effects, and controls before or during system development.

In this case, use the lens to examine human-system interaction. This application is museum interpretation, not a finding of the original investigation.

Limit: Lists can miss interactions and unanticipated operating conditions; scores are not exact probabilities.

Analytical lens

Systems thinking

Examine relationships, boundaries, feedback, and incentives across a whole system.

In this case, use the lens to examine human-system interaction. This application is museum interpretation, not a finding of the original investigation.

Limit: A broad lens needs explicit boundaries and evidence to avoid explaining everything after the fact.

09 / COUNTERFACTUALS

What could have changed the outcome?

Counterfactuals are hypotheses. They identify possible intervention points without claiming that a different choice would certainly have prevented the event.

INTERVENTION 2 / During early testing

Test the operating envelope

Exercise realistic boundary conditions and shared dependencies rather than validating components only in isolation.

Cost & feasibility

Requires time and independent review before commitment.

Likely effectiveness

May reduce exposure or consequences. Not quantified; feasibility and effect must be assessed against evidence available at the time.

10 / LESSONS

From hindsight to a usable practice.

FOR FOUNDERS

Test fault scenarios with representative crews and disclose safety-critical automation behavior clearly.

Before accelerating hiring or spending, name the assumptions that remain untested and set evidence thresholds for the next commitment.

11 / AFTERWARD

Recovery is another investigation.

Investigations, software changes, and revised training preceded return-to-service approvals. [1]

A corrective action is evidence of a response; it is not, by itself, evidence that the wider pattern has disappeared.

12 / SOURCES & EVIDENCE

Follow the record.

Documented claims are linked to sources. Analytical applications, lessons, and intervention proposals are museum interpretation. This draft does not establish motives or a single complete causal explanation.

  1. 1
    transportation.house.gov — Boeing / FAA case record

    Primary documentation · Accessed 4 October 2026

Editorial history & limits

Version 1 · 4 October 2026 — source-backed illustrative synopsis created. Independent editorial review is pending. No claim of exhaustive investigation. New sources may alter the analysis.