How should Boeing respond to re-engined narrowbody competition while protecting long-run aircraft safety, customer value, program economics, and financial flexibility?
Authorize only the reversible work needed to establish a credible derivative business case. Before final schedule and production commitments, require an independent aircraft-level safety assessment of all changed and interacting systems, validation of crew and maintenance assumptions under combined failures and alerts, current certification documents, supplier and production readiness, and a downside cash-and-return case. Maintain a funded clean-sheet technology path so short-term customer urgency does not become permanent architecture lock-in.
Confidence
Moderate
What happened
On August 30, 2011, Boeing announced board approval to launch a new-engine 737 variant based on commitments for 496 aircraft from five airlines.
The frozen Part A packet recommended bounded derivative work subject to independent, aircraft-level safety, certification, training, supplier, and downside-return gates. Later official records identify omissions in integrated evaluation, design-change documentation, oversight, and human-response assumptions that those gates were designed to test. This directional alignment does not prove that the proposed process would have prevented either accident, that the derivative launch alone caused the accidents, or that the alternative would have maximized owner value.
Require an independent aircraft-level safety gate before binding schedule and production commitments; keep every material design change synchronized with hazard analyses, certification artifacts, combined-failure tests, warnings, procedures, maintenance, training, and regulator communication.
Integrated review exposes adverse interactions, stale assumptions, fragmented evidence, and reliance on idealized operator response before commercial commitments make redesign harder.
Candidatemoderate confidence
rule.separate-program-costs-from-portfolio-shocks
Preserve directly labeled program amounts, build a deterministic reconciled bridge for any broader attribution, and abstain from assigning aggregate financial changes to the program until identified confounders are controlled.
Separating reported program amounts from multi-causal portfolio outcomes prevents salient-event bias and double counting while retaining the financial consequences that are directly evidenced.