Boeing made a clean-sheet-versus-derivative call under competitive pressure.
It never priced the execution environment that call was landing into.

NAVETRA does not replace Boeing's engineering, finance, audit, or compliance systems. It prices what those systems already hold. Boeing collected and reported the leading-indicator data behind both decisions in this casebook. What its board increasingly needed, and never had, was that data expressed as one dollar figure the audit committee could challenge before the commitment hardened, instead of reading it as a charge afterward.

What this casebook is, and is not

This is not a legal finding or an investment recommendation. It is a capital-allocation read built entirely from public reporting, government investigations, regulatory releases, and Boeing's own disclosures.

NAVETRA was never engaged by Boeing. Nothing here attributes any Boeing outcome to a NAVETRA-led decision, and no Operating Profit at Risk figure is assigned to Boeing. Inventing one would be the exact overclaim this casebook exists to refuse. The claim is narrow and deliberate: on two capital-allocation decisions, the leading-indicator data existed, Boeing reported it, and it was never priced into one board-readable range before the irreversible commitment moved.

Where the seat boundary sits

The 737 MAX crashes and the Alaska Airlines door plug were operational-safety failures. Those belong to the quality and operational-risk owner, a seat NAVETRA sits upstream of, not in. This casebook does not price them. It treats them as the converted lagging cost of two upstream capital decisions, and it draws that line explicitly so the read is not mistaken for a safety-governance review.

The decision NAVETRA prices is the one a CEO and board own jointly: under competitive pressure from Airbus's A320neo, commit to a derivative airframe with MCAS to avoid pilot-retraining cost, or take the clean-sheet capital and schedule. And separately: how long to carry an escalating 777X programme commitment as a strategic narrative before pricing it as a board decision.

The split that protects the read

A casebook that claimed a priced read would have prevented Boeing's loss cycle would be dismissed by any director who has run a capital plan, and rightly so. The discipline is to separate the two halves of this loss and only claim the half that was endogenous.

The MCAS decision: a capital call, not a safety story

Under pressure to answer the A320neo without the cost of pilot retraining, Boeing chose the derivative path and the system that came with it. Treated as a safety story, that belongs to the operational-risk owner. Treated as what it was at the decision point, a trade between retraining economics and the exposure of a derivative whose value depended on one design assumption holding, it is a board capital decision.

That exposure was in Boeing's own engineering and programme data at the decision point. It was carried as competitive necessity. It was never priced as the dollar value of a derivative bet that fails on its central assumption.

The 777X: a commitment carried as narrative

The 777X is the cleaner endogenous example because it has no exogenous excuse. The widebody was expected in service years before its current timeline. Public reporting through late 2025 described substantial cumulative charges and continued schedule extension. The trajectory was visible in programme data the whole way. It was carried as a narrative of difficulty, aerospace is hard, rather than priced as a recurring board decision about whether the commitment still cleared its own bar.

The artifact

NAVETRA assigns Boeing no Operating Profit at Risk figure here. What the artifact shows instead is structure: which client-facing domains carried the endogenous exposure on these two decisions, expressed as the actuarially weighted, sector-validated range a board reads on one page before the commitment hardens, not the charge it reads after.

Connect it to the data Boeing already collected

Every input above was already inside Boeing. The retraining-versus-clean-sheet economics sat with finance and programme management. The derivative-architecture assumption sat in engineering. The 777X slippage trajectory sat in programme schedules and charge forecasts. Boeing collected all of it and reported most of it.

What Boeing did not have was the dollar layer that data represented before it converted, expressed as one actuarially weighted, sector-validated range aligned to ISO 31000 and the company's existing enterprise-risk framework. Not a new metric to adopt. The price tag on the data already on the table. That alignment is the difference between a page a board chair finds persuasive and one a board chair can forward to procurement without having to defend it.

How much was external, and how much was organisational

Not every dollar of Boeing's loss cycle was preventable. The pandemic was exogenous. Competitive pressure from Airbus is structural. Treating the full arc as organisational failure would be inaccurate, and this casebook does not.

But treating it as external misfortune would be equally inaccurate. The derivative-versus-clean-sheet call and the duration of the 777X commitment were endogenous decisions Boeing's own data described in advance. The split is analytical, not accounting-based, and it can be debated. The harder point survives the debate: a meaningful share of this loss was carried as narrative when it could have been read as a number.