BOEING 737 MAX DEMO CORPUS DOSSIER
Status: RESEARCH / PRE-CAPTURE ONLY
Status: RESEARCH / PRE-CAPTURE ONLY
Subject: Boeing 737 MAX / MCAS crisis, centered on Lion Air JT610 (2018), Ethiopian Airlines ET302 (2019), certification/oversight, grounding, redesign, return to service, and related institutional/legal records
Scope: source inventory, authority/posture, record-contradiction map, provisional five-claim matrix, capture hazards, reverse-source candidates
Explicit non-claims: This dossier creates no CaptureReceipt, SourceEdition, SRS receipt, custody, admission, final standing, article prose, or canonical Counterpedia identity.
A. SUBJECT / DISAMBIGUATION
Common name
Exact event/entity scope
The design, certification, operation, accidents, grounding, redesign, and return to service of the Boeing 737 MAX, with primary focus on:
Lion Air Flight JT610, Boeing 737-8 MAX PK-LQP, October 29, 2018;
Ethiopian Airlines Flight ET302, Boeing 737-8 MAX ET-AVJ, March 10, 2019;
angle-of-attack (AOA) sensing and related flight-deck effects;
flightcrew response assumptions, training, procedures, and workload;
Boeing/FAA certification and delegation processes;
institutional disagreement over how to weight system design, sensor failure, crew performance, maintenance, and organizational factors;
March 2019 grounding and November 2020 U.S. return-to-service requirements;
separate legal proceedings concerning Boeing's disclosures to FAA's Aircraft Evaluation Group.
This is not a general page about all Boeing safety issues or all later 737 MAX production-quality events.
Important identifiers / aliases
KNKT.18.10.35.04
EAIB Report No. AI-01/19
DCA19RA017 / DCA19RA101
JATR — Joint Authorities Technical Review
AOA — angle of attack
Boeing FCOM/OMB issued November 6, 2018
United States v. The Boeing Company, 4:21-cr-00005-O (N.D. Tex.)
Naming / semantic traps
"MCAS caused both crashes" is too compressed. MCAS was central, but accident reports and participating investigators identify different chains and additional contributing factors.
"The AOA sensor failed" is not one identical mechanism across both accidents. Lion Air involved a replacement AOA sensor and maintenance/calibration history; the Ethiopian final report and NTSB/BEA later disagreed over the origin of ET302's erroneous AOA output.
"Pilot error" and "design error" are not mutually exclusive categories. Human performance can be causally relevant even when unsafe design assumptions created the conditions pilots faced.
"Certification failed" can mean different things: regulatory noncompliance, inadequate rules/guidance, insufficient integration analysis, poor communication, delegation/oversight weakness, or a process followed as written that nevertheless failed to reveal a hazard.
"FAA certified MCAS" is too loose. Certification involved Boeing-generated compliance work, FAA retained findings, delegated findings, changing design artifacts, operational-evaluation work, and multiple internal FAA offices.
"The MAX was recertified" is common shorthand. The FAA rescinded its grounding order after mandating specific design, documentation, maintenance, and training actions. The exact regulatory objects matter.
"Boeing admitted causing the crashes" is not an accurate summary of the corporate criminal case. The 2021 DPA concerned conspiracy to defraud FAA AEG about matters relevant to its 737 MAX evaluation; later legal posture changed again.
Accident-investigation findings ≠ criminal liability ≠ civil liability ≠ congressional findings.
The Ethiopian final report ≠ uncontested international consensus. BEA and NTSB submitted material comments under the Annex 13 process.
"Return to service" ≠ proof the original configuration was safe. It concerns the modified configuration and mandatory actions evaluated after grounding.
Temporal bounds
Core technical/certification corpus: 2012–2023.
Legal/procedural posture: through 2026-08-09, because the Boeing criminal case evolved materially after the original 2021 DPA.
Why fertile for Counterpedia
The 737 MAX is the clearest Demo Corpus subject for distributed causation.
The graph has many causally relevant nodes:
aerodynamic characteristic → MCAS design → single-sensor activation architecture → erroneous AOA input → repetitive stabilizer trim → alerts / cockpit workload → pilot recognition and response → training / documentation → maintenance / prior-flight handling → certification assumptions → Boeing–FAA communication → delegation / oversight → accident sequence
Counterpedia should refuse to turn that graph into one slogan.
B. SOURCE INVENTORY
MAX-S01 — Lion Air JT610 Final Accident Investigation Report
Exact title: Final KNKT.18.10.35.04 — Aircraft Accident Investigation Report — PT. Lion Mentari Airlines — Boeing 737-8 (MAX); PK-LQP — Tanjung Karawang, West Java, Republic of Indonesia — 29 October 2018
Issuer: Komite Nasional Keselamatan Transportasi (KNKT), Republic of Indonesia
Report date/publication: October 2019
Historical KNKT origin locator:
https://knkt.dephub.go.id/knkt/ntsc_aviation/baru/2018%20-%20035%20-%20PK-LQP%20Final%20Report.pdf
Current government-preserved discovery/mirror surface: Irish Air Accident Investigation Unit foreign-report page:
https://aaiu.ie/foreign_reports_fr/foreign-report-accident-pt-lion-mentari-airlines-boeing-737-800-pk-lqptanjung-karawang-west-java-republic-of-indonesia-29-october-2018/
Format: PDF, large
Authority / posture: Indonesian Annex 13 final accident investigation. Safety finding, not legal-liability adjudication.
May support
JT610 sequence;
erroneous AOA history and replacement;
MCAS activations;
maintenance/repair/documentation factors;
crew actions across the accident aircraft's preceding and final flights;
certification/design factors;
KNKT's multi-factor causal/contributing-factor account.
Important qualification KNKT's causal structure is deliberately multi-factor. A congressional hearing quoting an Indonesian investigator summarized it as nine factors that had to come together; CAP1 should bind any exact nine-factor enumeration to the report itself, not to the hearing paraphrase.
Captureability: MEDIUM Hazards
historical Indonesian origin may be unstable;
an Irish government-hosted foreign-report copy is a mirror, not KNKT-origin bytes;
capture origin if available and mirror separately if needed;
report contains graphs/tables/FDR plots requiring figure anchoring.
Priority: P0
MAX-S02 — Ethiopian Airlines ET302 Final Accident Investigation Report
Exact title: Aircraft Accident Investigation Report — B737-MAX 8, ET-AVJ — Accident to Ethiopian Airlines Flight 302 — 10 March 2019
Issuer: Ethiopian Aircraft Accident Investigation Bureau (EAIB), Ministry of Transport and Logistics
Report No.: AI-01/19
Publication date: December 23, 2022
Official participating-authority preserved copy:
https://bea.aero/fileadmin/user_upload/ET_302__B737-8MAX_ACCIDENT_FINAL_REPORT.pdf
BEA investigation page:
https://bea.aero/en/investigation-reports/notified-events/detail/accident-to-the-boeing-737-registered-et-avj-and-operated-by-ethiopian-airlines-on-10-03-2019-near-bishoftu-investigation-led-by-eaib-ethiopia/
Format: PDF, ~23 MB / >300 pages
Authority / posture: Ethiopian Annex 13 final accident investigation.
May support
ET302 timeline;
erroneous left AOA data;
repetitive automatic nose-down trim / MCAS sequence;
crew inputs and aircraft state;
EAIB probable-cause and contributing-factor formulation.
Critical qualification The EAIB's final report is not uncontested by participating states. NTSB and BEA agree on MCAS's major role but dispute/criticize important parts of the report.
Captureability: HIGH via BEA-hosted official copy Hazards: large PDF; capture exact report and appendices/comments separately.
Priority: P0
MAX-S03 — BEA comments on the Ethiopian final report
Exact source surface: BEA Accident to the Boeing 737 registered ET-AVJ... investigation page, BEA COMMENTS
Issuer: Bureau d'Enquêtes et d'Analyses pour la sécurité de l'aviation civile (France)
Public posture: Annex 13 participating-state comments requested to be appended to EAIB's report
Exact locator:
https://bea.aero/en/investigation-reports/notified-events/detail/accident-to-the-boeing-737-registered-et-avj-and-operated-by-ethiopian-airlines-on-10-03-2019-near-bishoftu-investigation-led-by-eaib-ethiopia/
Authority / posture: official participating-investigator disagreement/qualification; not the state-of-occurrence final report.
May support
BEA believes operational and crew-performance aspects were insufficiently analyzed;
BEA identifies pre-MCAS actions, autothrottle/autopilot handling, speed/trim/CRM issues as relevant to the chain;
BEA's technical position that foreign-object impact, most likely a bird, caused AOA vane separation.
Cannot establish
that EAIB's final report ceases to be the responsible-state final report;
that crew performance alone caused the crash.
Captureability: HIGH Priority: P0 — essential to the non-binary institutional record.
MAX-S04 — NTSB comments on Ethiopian final report
Exact source 1: NTSB Releases Comments on Ethiopia’s Investigation of the Boeing 737-8 Max Accident
Date: December 27, 2022
Locator:
https://www.ntsb.gov/news/press-releases/Pages/NR20221227.aspx
Exact source 2: NTSB Publishes Additional Comments on Ethiopia’s Final Report on 737 MAX 8 Accident
Date: January 24, 2023
Locator:
https://www.ntsb.gov/news/press-releases/Pages/NR20230124.aspx
Authority / posture: U.S. Annex 13 accredited-representative comments; official disagreement with aspects of EAIB report.
May support
NTSB says final report insufficiently addressed human performance;
NTSB says EAIB's electrical-failure explanation for erroneous AOA was unsupported by evidence;
NTSB's position: AOA vane separation from foreign-object impact, most likely a bird, caused erroneous output;
NTSB objection that the published final report did not include the requested current comments in the expected Annex 13 manner.
Captureability: HIGH Priority: P0
MAX-S05 — NTSB Safety Recommendation Report ASR-19-01
Exact title: Assumptions Used in the Safety Assessment Process and the Effects of Multiple Alerts and Indications on Pilot Performance
Issuer: National Transportation Safety Board
Report: ASR-19-01
Date: September 26, 2019
NTSB investigation surface:
https://www.ntsb.gov/investigations/pages/DCA19RA017-DCA19RA101.aspx
News / recommendation surface:
https://www.ntsb.gov/news/press-releases/Pages/NR20190926.aspx
Authority / posture: NTSB safety recommendation report issued while assisting the foreign accident investigations. It explicitly said it was not analyzing/blaming the specific accident crews in that report.
May support
Boeing/FAA certification analyses assumed pilot recognition/response behavior;
actual crews did not respond as assumed;
multiple simultaneous alerts and indications can affect recognition/response;
certification methods should more robustly validate pilot-response assumptions;
diagnostic/alerting design should support more effective pilot response.
Counterpedia value This is the ideal bridge between human factors and design:
crew action can differ from an assumption without making the design assumption irrelevant or the crew irrelevant.
Captureability: HIGH Priority: P0
MAX-S06 — Joint Authorities Technical Review (JATR)
Exact title: Boeing 737 MAX Flight Control System — Observations, Findings, and Recommendations
Issuer/body: Joint Authorities Technical Review chartered by FAA, chaired by Christopher Hart, with FAA/NASA and nine other civil aviation authorities
Date: October 11, 2019
Exact locator:
https://www.faa.gov/sites/faa.gov/files/2021-08/Final_JATR_Submittal_to_FAA_Oct_2019.pdf
Format: PDF, 71 pages
Authority / posture: multinational technical review of MAX flight-control certification; not an accident probable-cause report and not the FAA return-to-service decision.
Key findings/posture
changed-product process was followed for discrete changes but did not adequately address cumulative effects, system integration, and human factors;
some up-to-date safety/system-integration/human-factor methods were not applied or only partially applied;
certification deliverables were not consistently updated as MCAS evolved;
design assumptions were not adequately reviewed/updated/validated;
potential flight-deck and crew-workload effects were not fully evaluated;
FAA had inadequate awareness of MCAS, limiting independent assessment;
MCAS was not evaluated as a complete integrated function in certification documents submitted to FAA;
certification should minimize reliance on pilot action as the primary hazard-mitigation method.
Important qualification JATR says the certification process had historically produced an exemplary safety record and does not conclude that delegation itself is inherently unsafe.
Captureability: HIGH Priority: P0
MAX-S07 — House Transportation & Infrastructure Committee final investigative report
Exact title: The Design, Development & Certification of the Boeing 737 MAX
Issuer: U.S. House Committee on Transportation and Infrastructure
Date: September 2020
GovInfo preserved locator:
https://www.govinfo.gov/app/details/GOVPUB-Y4_T68_2-PURL-gpo144993
Historical committee PDF locator:
https://transportation.house.gov/imo/media/doc/2020.09.15%20FINAL%20737%20MAX%20Report%20for%20Public%20Release.pdf
Format: PDF, ~3.5 MB
Authority / posture: legislative committee investigation/report. It is not an Annex 13 accident report, FAA technical determination, or judicial finding.
May support
committee's reconstruction of design/development/certification history;
internal Boeing documents and communications incorporated into the investigation;
committee findings concerning production pressure, MCAS design evolution, disclosure, certification, ODA, training and marketing.
Cannot establish alone
accident probable cause;
criminal intent of individuals;
that all lawmakers/investigators agreed with every characterization.
Captureability: HIGH via GovInfo Priority: P1
MAX-S08 — DOT OIG audit of FAA certification/delegation
Exact title: Weaknesses in FAA’s Certification and Delegation Processes Hindered Its Oversight of the 737 MAX 8
Issuer: U.S. Department of Transportation Office of Inspector General
Date: February 23, 2021
Project: AV2021020
Exact locator:
https://services.oig.dot.gov/library-item/38302
Authority / posture: federal inspector-general audit of FAA processes, distinct from accident investigation.
Key findings
FAA and Boeing followed the established certification process;
limitations in FAA guidance/processes led to significant misunderstanding of MCAS;
FAA did not completely understand Boeing's MCAS safety assessments until after JT610;
communication gaps hindered certification;
ODA oversight/independence weaknesses existed;
OIG issued 14 recommendations; FAA concurred.
Counterpedia value This prevents the simplistic sentence:
"Boeing just bypassed the certification process."
The stronger record is:
the established process was followed in important respects and the process/oversight had weaknesses that failed to surface/understand the hazard adequately.
Captureability: HIGH Priority: P0
MAX-S09 — Boeing November 6, 2018 Flight Crew Operations Manual Bulletin
Exact document: Boeing Flight Crew Operations Manual Bulletin, No. TBC-19, issued November 6, 2018, subject concerning uncommanded nose-down stabilizer trim due to erroneous AOA during manual flight.
Primary-origin status: Boeing's historical bulletin should be acquired from Boeing/operator or an authenticated hearing exhibit if possible.
Government-preserved evidentiary surface: House hearing record, October 30, 2019:
https://www.congress.gov/116/chrg/CHRG-116hhrg38282/CHRG-116hhrg38282.htm
Authority / posture: first-party manufacturer operational bulletin. A congressional exhibit remains Boeing-authored content.
May support
what Boeing told operators after JT610;
description of repeated nose-down trim behavior;
reliance on existing runaway-stabilizer procedure.
Important qualification The hearing record highlights that the bulletin described the behavior but did not identify MCAS by name. Boeing witnesses explained the intent as teaching the observable airplane behavior/procedure rather than system diagnosis.
Captureability: MEDIUM Hazards
exact bulletin bytes need an authenticated copy;
"TBC-19" can be ambiguous across Boeing manual families/years; bind title/date/airplane effectivity, not short label alone.
Priority: P1
MAX-S10 — FAA Emergency Airworthiness Directive after JT610
Exact regulatory object: Emergency AD 2018-23-51
Issuer: FAA
Date: November 7, 2018
Official discovery/custody surface: FAA Boeing 737 MAX Reading Room
https://www.faa.gov/foia/electronic_reading_room/boeing_reading_room
Authority / posture: mandatory airworthiness regulation/action after JT610, before ET302.
May support
FAA required AFM revision/runaway-stabilizer procedures in response to erroneous AOA / repeated nose-down trim hazard.
Cannot support
that the mandated procedure was sufficient under every real-world failure condition;
Captureability: HIGH through reading room Priority: P1
MAX-S11 — FAA grounding order and evolving March 2019 position
Source family: FAA 737 MAX updates / Emergency Order of Prohibition
Issuer: FAA
Current official source surface:
https://www.faa.gov/newsroom/faa-updates-boeing-737-max-0
and FAA Reading Room:
https://www.faa.gov/foia/electronic_reading_room/boeing_reading_room
Key temporal record
March 12, 2019: FAA said available review showed no systemic performance issues and no basis to ground.
March 13, 2019: newly developed wreckage/configuration and refined tracking information showed similarities with JT610 warranting investigation of a possible shared cause; FAA grounded the MAX in the U.S.
Authority / posture: regulator's time-indexed operational decision.
Counterpedia value This is a clean temporal-truth specimen:
and
can both be faithful representations of the agency's evidence state at different times.
Captureability: HIGH Priority: P0
MAX-S12 — FAA return-to-service package / AD 2020-24-02
Issuer: FAA
Date: November 18, 2020
Official reading-room locator:
https://www.faa.gov/foia/electronic_reading_room/boeing_reading_room
Related official notice: Boeing 737-8 and 737-9 Airplanes: Return to Service, Notice 8900.570
https://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/documentID/1038501
Pilot-training notice: Notice 8900.569
https://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/documentID/1038500
Authority / posture: FAA regulatory determination for the modified aircraft configuration and mandated return-to-service actions.
May support
grounding rescission;
mandated design/software/AFM/maintenance actions;
new training requirements;
operators had to complete required actions before return to service;
FAA retained airworthiness-certificate authority for newly manufactured aircraft in the post-grounding process.
Cannot support
that every foreign regulator made the identical determination on the identical date.
Captureability: HIGH Priority: P0
MAX-S13 — FAA Flight Standardization Board / training record
Issuer: FAA
Current FSB surface:
https://www.faa.gov/aircraft/air_cert/airworthiness_certification/fsb
Historical return-to-service record: FAA reading room / November 2020 notices.
Authority / posture: operational suitability/training determination, distinct from aircraft type-design engineering certification.
May support
simulator/training requirements added for post-grounding MAX operation;
minimum differences/training expectations.
Counterpedia value Training is not merely a "pilot factor" downstream from design; it is part of the certified/approved operational system.
Captureability: HIGH Priority: P1
MAX-S14 — Boeing public MCAS/software statements
Exact source family: Latest Statements & Videos / 737 MAX updates
Issuer: The Boeing Company
Locator:
https://www.boeing.com/Commercial/737max/737-max-update_bh/737-statements-videos_bh
Authority / posture: first-party manufacturer public statements.
May support
Boeing's own explanation of MCAS purpose;
Boeing's post-accident claims about pilot override/procedures;
announced software changes;
company chronology.
Cannot support
independent validation of Boeing's technical assertions merely because Boeing published them.
Captureability: HIGH Hazards: corporate pages can be reorganized; timestamp individual statements; web page may aggregate multiple dates into one current page.
Priority: P1
MAX-S15 — DOJ 2021 DPA / criminal information
Exact source surface: Boeing Charged with 737 Max Fraud Conspiracy and Agrees to Pay over $2.5 Billion
Issuer: U.S. Department of Justice
Date: January 7, 2021
Archived press-release locator:
https://www.justice.gov/archives/opa/pr/boeing-charged-737-max-fraud-conspiracy-and-agrees-pay-over-25-billion
Current case hub:
https://www.justice.gov/criminal/criminal-fraud/case/united-states-v-boeing-company
Authority / posture: federal criminal information + deferred prosecution agreement. The charge concerned conspiracy to defraud FAA AEG in connection with its evaluation of the 737 MAX; it is not an Annex 13 probable-cause finding.
May support
exact criminal charge;
DPA statement of facts and financial resolution;
information/disclosure conduct within the specified legal case.
Cannot support
"Boeing pleaded guilty to causing 346 deaths" under the 2021 posture.
Captureability: HIGH Priority: P1
MAX-S16 — Boeing criminal case procedural evolution, 2024–2026
Exact case: United States v. The Boeing Company, 4:21-cr-00005-O (N.D. Tex.)
Official DOJ case hub:
https://www.justice.gov/criminal/criminal-fraud/case/united-states-v-boeing-company
Current posture as of 2026-08-09
May 2024: DOJ determined Boeing breached specified DPA obligations.
July 2024: proposed plea agreement reached.
December 5, 2024: district court rejected proposed plea agreement.
May 29, 2025: DOJ and Boeing entered non-prosecution agreement (NPA).
November 6, 2025: court granted DOJ motion to dismiss the criminal Information.
March/May 2026: Fifth Circuit addressed victims' mandamus petitions; amended opinion issued May 22, 2026.
June 18, 2026: mandate issued.
Authority / posture: live procedural history. Each step has its own legal meaning.
Counterpedia value A spectacular procedural-state chain:
criminal information
→ DPA
→ government breach determination
→ proposed plea
→ plea rejected
→ NPA
→ charge dismissed
→ victim-representative appellate challenge
Do not compress this to: "Boeing was convicted" or "Boeing was exonerated."
Captureability: HIGH Priority: P1 / time-sensitive
MAX-S17 — U.S. House Boeing 737 MAX hearing record
Exact title: The Boeing 737 MAX: Examining the Design, Development, and Marketing of the Aircraft
Committee: House Transportation and Infrastructure
Hearing date: October 30, 2019
GovInfo locator:
https://www.govinfo.gov/app/details/CHRG-116hhrg38282
Congress.gov text:
https://www.congress.gov/116/chrg/CHRG-116hhrg38282/CHRG-116hhrg38282.htm
Format: GovInfo PDF ~63.5 MB + text
Authority / posture: legislative hearing/testimony/exhibits. Witness testimony remains testimony; submitted exhibits retain original authorship.
May support
Boeing testimony;
lawmakers' questions;
authenticated/preserved copies or descriptions of Boeing internal/bulletin materials;
contemporaneous disagreement.
Captureability: HIGH Priority: P2 / source-recovery value
MAX-S18 — Wikipedia comparison surface — OPTIONAL
Title: Boeing 737 MAX groundings and/or Boeing 737 MAX
Role: familiar secondary comparison only
Capture rule: pin exact oldid(s) at demo capture time.
Authority / posture: secondary collaborative narrative, no automatic admission.
Priority: OPTIONAL
C. RECORD-CONTRADICTION / QUALIFICATION MAP
C-1 — "MCAS caused the crashes" vs multi-factor accident causation
There is broad institutional agreement that MCAS played a central role in both accidents.
But the actual record does not reduce to one edge.
Lion Air KNKT
The final investigation identifies interacting design, sensor, maintenance, documentation, and flightcrew factors.
NTSB ASR-19-01
Focuses on the gap between certification assumptions about pilot recognition/response and real-world crew response under multiple alerts.
JATR
Finds failures in integrated system evaluation, human-factors consideration, certification-artifact updates, FAA awareness, and oversight.
Ethiopian EAIB
Places repeated uncommanded MCAS activation at the center of its probable-cause formulation.
BEA / NTSB on ET302
Agree that MCAS contributed, but identify additional human-performance issues and dispute aspects of EAIB's AOA-failure explanation.
Counterpedia rule
A causal graph can contain:
initiating sensor fault;
hazardous automation behavior;
inadequate system architecture;
certification assumptions;
alert/workload effects;
crew response;
maintenance/operational factors;
organizational/regulatory factors.
The existence of one does not erase the others.
C-2 — ET302: actual institutional disagreement over the initiating AOA failure
EAIB final report
Attributes the erroneous AOA chain to electrical anomalies/heater-related issues in its final causal account.
NTSB
Says that finding is unsupported by evidence and says the erroneous AOA output resulted from AOA vane separation after foreign-object impact, most likely a bird.
BEA
Also states that testing/modeling supported foreign-object impact, most likely a bird, causing vane separation.
Counterpedia value
This is not manufactured controversy.
It is: responsible-state final report finding versus participating-state technical objection
Both deserve exact attribution.
A composed page should not invent a consensus sentence such as:
"Investigators determined the AOA sensor failed because X"
unless "investigators" is narrowed to the institution actually making X.
C-3 — ET302: agreement on MCAS, disagreement on completeness of human-factor analysis
BEA expressly says it shares EAIB's analysis/conclusions regarding MCAS contribution.
But BEA also says EAIB insufficiently addressed:
crew performance before first MCAS activation;
failure to execute stall/airspeed-unreliable responses;
autopilot/autothrottle management;
speed and trim management;
CRM and training/knowledge acquisition.
NTSB similarly said human-performance aspects were insufficiently addressed.
This is the ideal Counterpedia anti-false-dichotomy:
Design failure can be central and crew performance can still be causally relevant.
Adding the second does not absolve the first.
C-4 — Certification process followed ≠ certification process adequate
DOT OIG says FAA and Boeing followed the established certification process.
JATR/OIG also identify:
weak integration analysis;
outdated/incomplete guidance;
MCAS design evolution not fully reflected in certification deliverables;
FAA misunderstanding/inadequate awareness;
communication gaps;
ODA independence/oversight concerns.
Therefore:
"The normal process was followed"
does not imply:
"the process successfully identified and mitigated the hazard."
And:
"the process had serious weaknesses"
does not automatically imply:
"every certification action was unlawful or skipped."
C-5 — Design compliance ≠ safety
JATR explicitly raises the broader principle that for increasingly complex integrated systems, compliance with every applicable regulation/standard does not necessarily ensure safety if rules do not address every interaction/scenario.
That is a deep Counterpedia distinction:
regulatory compliance proposition ≠ safe-system proposition
These can overlap but are not identical.
C-6 — Pilot response as mitigation vs fail-safe design
Certification analyses relied in part on assumptions about pilots recognizing and countering unintended trim.
real crews faced multiple alerts;
startle/workload can affect response;
certification needs more robust validation of pilot-response assumptions;
design should minimize reliance on pilot action as the primary hazard mitigation.
This supports a nonbinary statement:
A correct pilot action may have been capable of interrupting a hazard under some conditions and a safety architecture can still be defective for relying too heavily on rapid correct pilot action under confusing failure conditions.
C-7 — "Pilots weren't told about MCAS" requires date and document scope
Before JT610, line-pilot documentation/training did not provide the eventual post-accident MCAS detail.
After JT610:
Boeing issued its Nov. 6 operational bulletin describing erroneous-AOA repeated nose-down trim behavior;
FAA issued Emergency AD 2018-23-51;
NTSB later criticized the Ethiopian report for language suggesting lack of MCAS information without adequately reflecting that post-JT610 dissemination.
Therefore:
"pilots were not told about MCAS"
may be true for a particular pre-JT610 manual/training state and overbroad for March 2019 unless document/date/crew-delivery status is specified.
C-8 — FAA March 12 vs March 13, 2019
March 12
FAA publicly said its review showed no systemic performance issues and no basis for grounding.
March 13
New wreckage/configuration and refined tracking information showed similarities between ET302 and JT610 warranting investigation of a shared cause; FAA grounded the fleet.
Counterpedia value Do not retroactively edit March 12's institutional knowledge state.
The page should preserve: evidence at T1 → no grounding basis stated then new evidence at T2 → grounding decision
This is temporal truth, not hypocrisy-by-default.
C-9 — Original MAX configuration vs post-grounding MAX configuration
The FAA's November 2020 return-to-service action concerned an airplane after:
MCAS/control-law changes;
revised sensor comparison behavior;
flight-control-computer/software changes;
AFM/procedure changes;
maintenance actions;
simulator/training requirements.
Therefore:
must be bound to the modified configuration and required actions, not silently projected backward onto the 2017–2019 configuration.
This is a SourceEdition-like problem for engineered systems: same product name, materially changed safety-relevant configuration.
C-10 — Accident cause vs legal fraud case
The DOJ Boeing case concerns disclosure/conspiracy allegations and agreements relating to FAA AEG's evaluation of the MAX.
It is not a substitute for KNKT/EAIB accident causation.
Likewise, accident reports do not establish the legal elements of conspiracy to defraud the United States.
The legal case's changing posture from DPA → breach determination → proposed plea → rejected plea → NPA → dismissal is itself a procedural history that cannot be summarized as either:
"Boeing was convicted," or
"Boeing was cleared."
C-11 — Congressional report vs technical regulator/accident findings
The House final investigative report contains valuable document reconstruction and institutional findings about Boeing/FAA conduct.
But:
committee finding ≠ Annex 13 probable cause;
political/legislative assessment ≠ regulatory technical determination;
testimony/exhibit ≠ committee finding.
Counterpedia should make legislative findings visible without using them to overwrite technical-source posture.
D. FIVE-CLAIM DEMONSTRATION MATRIX — PROVISIONAL ONLY
C1 — Observable / concrete event fact
Provisional wording
Two Boeing 737-8 MAX aircraft—Lion Air JT610 on October 29, 2018 and Ethiopian Airlines ET302 on March 10, 2019—crashed shortly after takeoff, killing all 346 people aboard the two flights; both accident sequences involved erroneous angle-of-attack information and automatic nose-down stabilizer trim associated with MCAS.
Candidate sources
Can establish
accident dates;
aircraft types;
fatalities;
broad common technical features.
Cannot establish
identical initiating failure mechanism;
one identical complete causal chain.
Likely posture
strong cross-investigation event fact with source-specific technical clauses.
Qualification Use separate child propositions for each accident's AOA origin.
Strengthening No need for higher-level event claim; capture exact FDR/accident-report passages for each flight.
C2 — Structural / system-design fact
Provisional wording
In the original 737 MAX certification/configuration, MCAS could command stabilizer movement in response to input from a single active angle-of-attack sensor, while certification safety assessments relied on assumptions about flightcrew recognition and response to unintended trim behavior.
Candidate sources
Can establish
MCAS architecture/safety-assessment structure;
later concern over single-failure/integrated-system behavior.
Cannot establish
that a single sensor was the sole cause of both crashes;
that every certification participant knew every later-evolved MCAS characteristic.
Likely posture
technical/certification fact.
Refusal branch
"FAA deliberately approved a system it knew would crash if one sensor failed."
Current located sources do not establish that subjective proposition.
Strengthening Would require authenticated contemporaneous evidence proving the relevant FAA/Boeing decision-maker's specific knowledge/intent at the time.
C3 — Action / chronology
Provisional wording
After JT610, Boeing issued an operational bulletin and FAA issued an emergency airworthiness directive reinforcing runaway-stabilizer procedures; after ET302 revealed significant similarities to JT610, FAA grounded the U.S. 737 MAX fleet on March 13, 2019, and did not rescind the grounding until November 18, 2020 after mandating design, procedure, maintenance, and training changes.
Candidate sources
Can establish
post-JT610 operational response;
grounding chronology;
return-to-service chronology;
modified-aircraft requirements.
Cannot establish
that post-JT610 measures were sufficient merely because they were mandated;
that return-to-service validates original design.
Likely posture
regulatory/action chronology.
Qualification "FAA grounded the plane after the second crash" should preserve the March 12→13 evidence transition rather than implying an instantaneous/automatic action.
C4 — Carefully bounded causal / explanatory proposition
Provisional wording
The institutional record supports a distributed causal account in which erroneous AOA information triggered hazardous MCAS/stabilizer behavior, while certification/design assumptions, flightdeck alerting and workload, crew recognition and response, training/procedure dissemination, maintenance/operational factors, and oversight/communication failures contributed differently across the two accidents.
Candidate sources
What sources can establish
multiple causal/contributing-factor categories;
cross-institution agreement that MCAS was central;
accident-specific differences;
human-factor/design interaction.
What they cannot establish
one master causal percentage;
that every factor contributed equally;
that a factor present in JT610 was necessarily present in ET302.
Likely posture
synthesis should remain a graph/partitioned causal structure rather than one unattributed sentence.
Refusal branch If Counterpedia cannot retain source-specific attribution and accident scope, refuse the simplified synthesis rather than pretend all institutions made one finding.
C5 — Contested / commonly compressed proposition
Popular formulation
What is documented
erroneous AOA signals occurred;
MCAS/repetitive nose-down trim materially contributed to both accident sequences;
original certification/design had weaknesses;
pilot-response assumptions did not match actual crew experience;
the two crashes had important similarities;
the fleet was grounded and MCAS/system/training design changed.
Why the formulation is still too broad as a complete causal statement
EAIB, BEA, and NTSB do not fully agree on ET302's initiating AOA mechanism or completeness of the causal/contributing-factor analysis;
BEA/NTSB say crew/human-performance issues need more weight in ET302 analysis;
maintenance factors prominent in JT610 are not interchangeable with ET302;
certification/organizational factors operate at a different causal level from the immediate flight-control sequence.
Provisional Counterpedia wording
MCAS was a central causal/contributing mechanism in both accidents, but the official record does not support treating "MCAS" as a complete substitute for the distinct multi-factor causal chains of JT610 and ET302.
Likely posture
qualified multi-source synthesis.
Reopening condition There is no realistic single-source reopening condition for "MCAS completely caused both crashes." To publish a stronger complete-cause formulation, one would need an institutional analysis explicitly excluding the other established contributing factors and resolving the documented inter-authority disagreements—which the current corpus does not provide.
E. BEST "WHY NOT?" SPECIMEN
Popular stronger formulation
"The 737 MAX crashes happened because Boeing's MCAS software malfunctioned."
Why the record does not justify this as the complete explanation
This formulation compresses several different objects:
Software/control logic
MCAS responded to AOA input and commanded stabilizer movement.
Sensor/input
Erroneous AOA data initiated the hazardous chain—but the two accidents did not necessarily share the same sensor-failure origin.
Safety architecture
Single-input reliance and repetitive trim authority matter separately from whether software "malfunctioned" in the colloquial sense.
Certification
JATR/OIG/NTSB identify assumptions and integration/communication/oversight weaknesses.
Human factors
Actual crew response under multiple alerts differed from certification assumptions. BEA/NTSB say ET302's crew-performance analysis matters.
Maintenance/operation
KNKT identifies maintenance, repair, documentation, and prior-flight/crew factors in JT610.
So the stronger "software bug caused everything" version loses the actual lesson.
Reopening condition
A complete-cause statement would require evidence establishing that the other currently documented causal/contributing factors were non-causal or irrelevant to each accident.
The existing official record goes in the opposite direction.
F. SECOND "WHY NOT?" — ET302 INSTITUTIONAL DISAGREEMENT
Strong formulation
"Investigators determined ET302's angle-of-attack sensor failed because of an electrical defect."
Why not
That is EAIB's position.
NTSB says that finding is unsupported by the evidence and attributes the erroneous output to physical AOA-vane separation after a foreign-object impact, most likely a bird. BEA records the same foreign-object-impact analysis.
Therefore the strongest page-level state is:
EAIB attributed the erroneous AOA signal to an electrical/heater-related failure; NTSB and BEA disputed that explanation and attributed it to foreign-object impact/vane separation. All agreed that the erroneous AOA signal fed the later MCAS sequence.
This is a spectacular competing institutional findings demo because disagreement exists inside the official Annex 13 record itself.
G. SOURCE-PAGE / REVERSE-WIKIPEDIA VALUE
1. MAX-S06 — JATR report
Why ideal
The JATR Source Page can reverse-traverse from certification doctrine into:
Changed Product Rule;
certification-document updates;
human factors;
ODA/delegation;
FAA awareness;
training;
specific recommendations.
It can also constrain stronger claims:
process followed for discrete changes;
delegation not condemned categorically;
report is not an accident probable-cause report.
Reverse traversal JATR finding → certification evidence → C2/C4 claims → FAA reforms → later DOT OIG findings → return-to-service requirements
2. MAX-S05 — NTSB ASR-19-01
Why ideal
This source begins with a deceptively simple question:
What did certification assume a pilot would do?
It can traverse into:
human-response assumptions;
alert burden;
startle;
diagnostic design;
training;
accident crew behavior;
post-grounding design requirements.
It is the cleanest bridge between human error and system design without blaming or exonerating either side.
3. MAX-S03 + MAX-S04 — BEA/NTSB comments on EAIB
Why ideal
Counterpedia can show a final accident report and then directly expose accredited-state disagreement:
EAIB final finding → NTSB objection → BEA objection → shared MCAS agreement → disputed AOA mechanism → disputed human-factor completeness
A normal encyclopedia sentence often hides this behind "the report found..." or a footnote.
4. MAX-S11 — FAA March 2019 update stream
Why ideal
A source/history page can show the regulator changing operational posture as evidence changes:
Mar 12 → no basis stated for groundingMar 13 → new similarity evidence → grounding
The reader can inspect what changed, not merely that FAA "reversed itself."
H. 30–60 SECOND DEMO MOMENT
Start with:
Ordinary encyclopedia answer:
MCAS.
Counterpedia opens two accident columns.
LION AIR JT610
erroneous AOA after maintenance/replacement history
MCAS nose-down commands
repeated pilot counter-trim
maintenance/documentation issues
crew/operational factors
certification/design factors
ETHIOPIAN ET302
erroneous AOA immediately after takeoff
MCAS/repetitive nose-down trim
severe alert/workload environment
crew trim/speed/autothrottle/CRM issues identified by BEA/NTSB
EAIB vs NTSB/BEA disagreement on why the AOA signal became erroneous
Then a third column:
SYSTEM / CERTIFICATION
MCAS not evaluated as a complete integrated function in certification documents submitted to FAA
design evolution not consistently fed back into safety artifacts
pilot-response assumptions inadequately validated against multiple-alert scenarios
Then ask:
So was it Boeing or the pilots?
Counterpedia responds:
That is a false binary. The record contains interacting design, sensor, certification, maintenance, operational, and human-performance factors. Different investigators assign different scope and weight to some of those factors.
That's the demo.
I. CAPTURE PRIORITY
P0 — demo does not work without
MAX-S01 KNKT JT610 final report — origin if possible; government mirror separately if needed
MAX-S11 FAA March 2019 grounding chronology
MAX-S12 exact Nov. 2020 return-to-service package / AD 2020-24-02
P1 — important corroboration / contradiction
MAX-S07 House final report
MAX-S09 authenticated Boeing Nov. 6, 2018 bulletin
MAX-S16 2024–2026 Boeing criminal-case procedural chain
P2
MAX-S17 House hearing/transcript/exhibits
specific internal Boeing certification artifacts from FAA Reading Room
exact ODA/certification compliance documents where a narrower claim requires them
OPTIONAL
MAX-S18 Wikipedia comparison editions, pinned by oldid
J. INTEGRITY FLAGS
1. KNKT origin availability / mirror equivalence
The historical Indonesian KNKT locator is known, but current web access is unstable. AAIU/GovInfo/Congressional copies can establish preserved availability, but must not be represented as identical KNKT-origin bytes unless digest comparison proves it.
2. Ethiopian final report has real official dissent
Do not write "the international investigation concluded..." for propositions that EAIB, NTSB, and BEA do not all share.
3. Annex 13 comments are not "minority opinions" in a legislative sense
They are participating-state technical comments with a defined treaty/investigation posture.
4. NTSB/BEA comments agree with EAIB on important points
Do not exaggerate disagreement. They agree MCAS contributed centrally; their objections concern causal completeness and specific technical/human-factor findings.
5. "Most likely bird" is still an attributed technical conclusion
Use:
NTSB/BEA concluded / considered foreign-object impact, most likely a bird.
Do not silently convert "most likely" into a photographed/observed bird strike.
6. Human factors must not become victim-blaming shorthand
Crew actions can be causally analyzed while preserving:
confusing/multiple failure indications;
physical control forces;
certification assumptions;
training/documentation state;
design responsibility.
7. "Pilot could have stopped MCAS" needs condition scope
A procedural capability under some conditions is not proof that the hazard was safely recoverable under every actual flight condition.
8. "Single sensor" should be tied to original configuration
Post-grounding MCAS architecture changed. Product name alone is insufficient.
9. Return-to-service source is configuration-specific
Bind claims to:
design/software version;
required AFM revisions;
training state;
maintenance actions.
10. FAA Reading Room is a discovery surface and custody source
Individual certification artifacts inside it retain:
Boeing authorship;
FAA authorship;
date/version;
compliance-document posture.
11. Boeing public statements are first-party explanations
They are essential for "what Boeing said then" but are not independent accident findings.
12. Congressional report is a legislative investigation
Do not use it as a substitute for KNKT/EAIB probable cause.
13. DOT OIG makes an important both/and finding
"Established process was followed" and "process weaknesses hindered oversight" must both survive.
14. March 2019 FAA position changed with evidence
Preserve March 12 and March 13 as separate observations rather than treating one as an embarrassing superseded byte to hide.
15. Boeing legal case is not static
The 2021 DPA is historically important but no longer describes the whole procedural state as of 2026.
16. DPA ≠ conviction
A criminal Information plus DPA is not a guilty verdict.
17. 2025 dismissal ≠ factual exoneration of original conduct
The later NPA/dismissal has its own procedural meaning. It does not delete the DPA Statement of Facts, accident findings, or other institutional records.
18. Proposed plea ≠ accepted plea
The 2024 proposed plea was rejected by the district court. Do not describe Boeing as convicted under that proposed agreement.
19. Accident-specific factors cannot be copied across flights
JT610 maintenance/sensor-replacement history should not be silently attributed to ET302.
20. Flight-data plots require artifact/figure anchoring
The most intuitive MCAS evidence is graphical. CAP1 must preserve exact pages/figures and not rely only on extracted prose.
K. BOEING 737 MAX CAPTURE DISPATCH SHAPE
For MAX-CAP1, acquire in this order:
MAX-S04 NTSB Dec. 2022 comments + Jan. 2023 additional comments and linked comment documents
attempt historical/current KNKT origin
if unavailable, capture current government-preserved mirror separately
compare digests if an origin copy is later recovered
MAX-S11 FAA March 12 and March 13 update/order artifacts separately
MAX-S12 rescission order + AD 2020-24-02 + return-to-service summary
MAX-S13 FSB Rev. 17 / applicable historical pilot-training report
MAX-S09 authenticated Nov. 6, 2018 Boeing bulletin
MAX-S07 House final report from GovInfo
MAX-S14 individual Boeing dated statements, not only aggregate current page
MAX-S15 criminal Information + DPA + Statement of Facts
2024 DPA breach determination
proposed plea
Dec. 2024 rejection order
May 2025 NPA
Nov. 2025 dismissal
2026 Fifth Circuit amended opinion/mandate
selectively acquire internal certification artifacts from FAA Reading Room only after claims requiring them are identified
CAP1 output remains intentionally boring:
requested locator
final locator
HTTP result
media type
exact bytes/digest
capture observation
authoring institution
source-owned dates
report/case/regulatory identifiers
version/amendment status
artifact lineage
extraction availability
figure/table anchorability
captured / refused / failed
no final standing
no article prose
L. PROVISIONAL 737 MAX THESIS FOR REVIEW
The MAX should not be demoed as:
"Boeing wrote bad software and two planes crashed."
That is too simple to demonstrate Counterpedia.
The stronger thesis is:
A safety failure can be distributed across design, sensor input, automation authority, certification assumptions, cockpit information, training, maintenance, human performance, organizational communication, and regulatory oversight—and the record can disagree about the weight or mechanism of some nodes without making every explanation equally plausible.
The strongest reveal is the Ethiopian record:
EAIB, NTSB, and BEA agree that erroneous AOA data and MCAS were central to ET302. They do not fully agree on what caused the erroneous AOA signal or how much causal weight the final report should give crew-performance factors.
Counterpedia should preserve:
the shared facts;
the shared MCAS finding;
the disputed sensor mechanism;
the disputed causal completeness;
and each institution's exact authority/posture.
The second reveal is systemic:
The certification process can have been followed as designed while still being inadequate to expose the integrated hazard.
That is an unusually important non-binary claim, grounded directly in the JATR and DOT OIG records.
737 MAX therefore exercises:
technical vs organizational causation;
human factors without false pilot/design binaries;
competing institutional technical findings;
source/posture discipline under Annex 13;
certification compliance vs actual safety;
time-indexed regulator decisions;
configuration/version truth;
procedural legal history vs accident causation;
and evidence graphs where no single "root cause" sentence should be allowed to erase the system.