Clearance CLR-8497 · AIR186
AIRMAX
Aircraft & EnginesClearance sheet
737 MAX Software Flaw Threatens MAX 10 Certification Timing
A U14 flight management system flaw known to Boeing since 2024 leaves 25 MAX 7s undelivered and puts the MAX 10's expected certification on hold.
Read-back
- Boeing learned of the U14 FMS flaw in 2024 but only now informed the FAA and pilots; it drops vertical navigation guidance after a go-around.
- 25 built MAX 7s remain undelivered; MAX 10 certification, expected within days, may wait on an FAA-mandated safety review panel.
- MAX 8 and MAX 9 operators can revert to earlier software; MAX 7 and MAX 10 cannot, as U14 is their certification standard.

A flaw in the 737 MAX flight management system has stalled deliveries of the MAX 7 and now threatens the certification timeline of the MAX 10, after Boeing waited roughly two years before informing the FAA and line pilots of the problem.
According to a Wall Street Journal report published over the weekend, the issue is tied to the U14 software update for the flight management system. When a crew executes a go-around from a missed instrument approach, the update can shut off vertical navigation guidance. Pilots can reset the function, but the loss of guidance arrives at one of the highest-workload moments in commercial operations — typically in low ceilings and fog, when a landing is aborted and the aircraft must climb away to reposition for another approach or divert to an alternate.
Boeing learned of the flaw in 2024, the report states, and only now has disclosed it to the regulator and to operators. The company did not classify the glitch as a safety-of-flight issue — a determination many pilots dispute. The failure mode bears no resemblance to MCAS, the single-point-of-failure system that killed 346 people in the Lion Air and Ethiopian Airlines crashes. But the disclosure pattern does. In the MCAS case, pilots were never told the system existed or how it behaved before they encountered it in the air. Here again, crews were left to discover unexpected aircraft behavior on their own.
Immediate operational and certification consequences
Operators of the MAX 8 and MAX 9 have a straightforward workaround: revert to an earlier software version that does not exhibit the anomaly. They lose some functional improvements, but the aircraft behaves as intended.
The MAX 7 and MAX 10 have no such option. Both models use U14 as their certification standard, and no earlier software version was ever certified for them. That has forced the FAA to mandate a safety review panel to examine the system and determine whether additional action is required.
The timing is costly. Twenty-five MAX 7 airframes are already built but undelivered. The MAX 10, whose certification was expected within days, may now wait on the outcome of the review — a timeline Boeing does not control. Delayed deliveries weigh directly on cash flow and will color Boeing's third-quarter financial results.
A classification problem, not an engineering problem
The technical fix itself is modest. A bulletin noting that vertical guidance may drop out after a missed approach, plus a checklist item instructing crews to reset the function during the go-around sequence, would likely have resolved the operational risk. By most estimates, such a procedure could have been drafted and approved in a single afternoon.
Instead, Boeing classified the glitch as unrelated to safety and said nothing. A surprise disclosure two years after internal discovery does the opposite of what early transparency would have achieved.
The parallel to 2024 is uncomfortable for the manufacturer. That year began with the Alaska Airlines MAX 9 door-plug blowout and explosive decompression — traced to bolts never reinstalled at the factory — and ended with a CEO change and intensified FAA quality oversight of the 737 and 787 production lines. Kelly Ortberg, who took over in that shakeup, had been making measurable progress on quality metrics and on transparency with the FAA and airline customers. This episode puts that progress at risk.
The FAA now has reason to examine not only the safety implications of the software behavior but also how Boeing classified the risk as low, and why pilots were not informed when the flaw was found rather than two years later.
The core issue is trust
Pilots operate on the assumption that the aircraft will do what it is commanded to do. Doubt about expected aircraft behavior is itself a safety hazard, whatever the engineering assessment says. This is the second time Boeing has failed to communicate clearly with regulators, airline customers, and pilots about how the 737 MAX behaves in flight — the first being MCAS, which was hidden from the FAA and misclassified during the original certification.
Boeing is running out of runway on transparency. Ortberg now faces questions he has yet to answer publicly: why obfuscation on safety issues continues at the company, and when that culture will actually change.
via wsj.com (Original)
More from James Calloway
Show full bio
Staff writer covering industry trends and analytics at Flightdeck Report.
156 articles
Same bay
- FDR160FAA Convenes Review Board Over 737 MAX VNAV Software Fault · September 27, 2026
- FDR369FAA holds 737 MAX 10 certification over flight-guidance software flaw · September 28, 2026
- FDR692FAA Review of Flight Software Threatens New 737 Max 10 Delay · September 27, 2026
- FDR343FAA to Delay 737 MAX 10 Approval Over New Software Glitch · September 30, 2026
- FDR365ATC Failure Disrupts Hundreds of US Flights, Exposing Aging System · September 28, 2026