Case file
- What happened: On 5 January 2024, an Alaska Airlines 737 MAX 9 lost its mid-cabin door plug at roughly 16,000 feet shortly after departure from Portland. The plug departed the airframe cleanly, causing rapid decompression but no fatalities.
- Scale: One aircraft type grounded globally — 171 MAX 9s in the US fleet alone — for nearly a month. Fleet-wide inspections ordered by the FAA.
- Root cause: NTSB preliminary findings confirmed the door plug had been removed during rework to repair damaged rivets at Spirit AeroSystems and reinstalled without the four retaining bolts. No production record captured the removal or the reinstallation.
- The bill: Alaska's preliminary Q1 2024 impact was reported at roughly $160 million. Boeing's full-year financial and reputational cost is still accumulating.
Four bolts. That is what this case comes down to — not the bolts themselves, but the fact that nobody can prove whether they were ever there. In aerospace quality, if the record does not say it happened, it did not happen. The plug was reworked, the paperwork did not follow, and a pressurised hull left the factory with an open hole held shut by friction and luck. Luck held until 16,000 feet.
The situation
The 737 MAX 9 mid-exit door plug seals what would otherwise be an emergency exit — installed on configurations that do not require the extra exit. It is secured to the airframe with twelve stop pads, four hinge fittings, and four upper and lower guide tracks. Four retaining bolts prevent vertical movement. Remove them and the plug is captive only by its own weight and the stop-fit of the pads.
This particular aircraft was assembled at Spirit AeroSystems in Wichita, where the fuselage is built, then shipped to Boeing's Renton facility for final assembly. NTSB documentation later confirmed that during fuselage production, the door plug area had been opened up — the plug removed — to address damaged rivets on the surrounding skin. That rework was real. The paperwork for it was not.
How it unfolded
The aircraft, N704AL, was delivered to Alaska Airlines in late October 2023 and entered revenue service. It accumulated about 150 flight cycles over the following two months — each one a pressurisation cycle that applied upward force on an unretained plug. On 5 January 2024, operating as ASA 1282 from Portland to Ontario, California, the aircraft reached approximately 16,000 feet and the plug departed. Six minutes earlier it would have been on the ground. Six minutes later it would have been at cruising altitude with a larger pressure differential and potentially a different outcome.
The crew declared an emergency, descended, and returned to Portland without serious injuries. The plug was later recovered in a Portland backyard. The investigation traced the plug's history back through Boeing's final assembly line to Spirit's Wichita plant, where the gap in the build record became visible.
Root-cause anatomy
Technically the failure mode is straightforward: vertical movement of an unretained plug under cyclic pressurisation load, leading to disengagement from the stop pads and separation from the airframe. The four upper retaining bolts were absent. The lower guide track bolts were present but loose. The plug walked upward until it cleared the stops.
Organisationally, this is where it gets uncomfortable. The NTSB's preliminary report indicated that Spirit's records did not reflect the door plug removal. Boeing's records did not flag the discrepancy at receiving inspection or during final assembly. Two quality systems — supplier and OEM — both touched this component and neither captured that it had been opened, reworked, and closed up incomplete. This was not a single-point human error. It was the failure of every verification gate between the rework cell and the delivery certificate.
If your rework is real but your paperwork is fiction, you are not running a quality system — you are running a hope system.
Where the quality system failed
Break this against AS9100 and the cracks are specific. The rivet repair triggered a configuration deviation. Under any functional change-control regime, that deviation generates a nonconformance report and a controlled rework instruction. Here it generated neither. No traveller, no stamp, no electronic record that the plug was removed. Door plug retention is a safety-critical characteristic — the PFMEA knows this — and the control plan should mandate independent verification of fastener torque and presence after any rework in that zone. It did not, or the mandate was not enforced.
Receiving inspection at Boeing failed next. The fuselage arrived at Renton with the plug in place, which is exactly what you would expect whether it was bolted correctly or not. The visual was fine. The verification was absent. And CAPA discipline — if earlier signals existed about rework documentation gaps in that Spirit cell — did not close the loop before this aircraft shipped.
What would have caught it
Any removal of a door plug for downstream repair should automatically generate a mandatory reinstallation check, with torque values recorded against serial numbers. Not optional. Not "if the operator remembers." That is a gate, not a suggestion.
Receiving inspection at Renton should have cross-referenced the as-shipped configuration against the as-built record. A door plug physically present but undocumented in the rework log is a red flag, not a closed item. The hardware looked correct whether it was bolted or not — and that is precisely the problem with a visual-only receiving check on a component that was never supposed to be opened.
QRQC at the rework cell is the layer that matters most. The moment damaged rivets were found adjacent to the door plug, a rapid response should have locked the area, documented the as-found condition, and opened a structured rework ticket with mandatory sign-off at each step — including fastener reinstatement. I have deployed QRQC in exactly this mode in automotive plants: the discipline is not about adding paperwork, it is about making the physical state and the documented state inseparable. Layered process audits that specifically target recently reworked areas — not random floor walks — are the backstop. They catch exactly this type of gap before it leaves the cell.
My take
I have spent enough time in aerospace and automotive plants to know that undocumented rework is not a Boeing problem or a Spirit problem — it is an industry-wide pressure point. I have seen it in tier-one automotive suppliers where a line operator removes a bracket to fix weld spatter and reinstalls it two shifts later with no record because the shift handover was verbal. The mechanism is identical: production pressure meets a rework event that the paperwork was not designed to capture at that level of granularity.
In my own work, the discipline I enforce is simple — no rework without a ticket, and no ticket closure without independent verification of the safety-critical characteristics. QRQC and A3 are not tools for after the fact. They are front-end controls. If a damaged rivet is found near a door plug, the rework instruction should be generated before anyone picks up a tool, not after. Receiving inspection at the OEM should treat undocumented configuration changes as nonconformances, full stop. I have seen 97% reductions in internal lead time by tightening exactly these handoff points — not by adding inspection, but by making the documentation flow impossible to bypass.
What this means on your floor
- Rework that is not documented is a nonconformance, regardless of whether the repair itself was correct.
- Receiving inspection must verify the record, not just the hardware. A part that looks right but has no paper is a defect.
- Safety-critical fastener reinstatement after any rework needs independent verification — not the operator's own stamp.
- Audit your rework cells specifically. That is where the pressure lives and where the gaps hide.
Four bolts did not fall out of an airplane. Four bolts were never confirmed to have gone back in — and nobody knew because nobody's record said otherwise. The quality system did not fail to detect a defect. It failed to know it existed. That is a different failure entirely, and it is the one that should keep quality leaders awake.