New 737 MAX Software Glitch Raises Certification Risk for Boeing

What happened

Boeing disclosed a new software glitch on the 737 MAX that could disrupt a navigation feature, triggering an FAA investigation and potential delays in certifying new aircraft models. The company is developing a pilot procedure and a software fix, but the issue adds to a list of regulatory hurdles that already include pending certification of the 737-7 and 737-10 variants. This development comes as Boeing attempts to ramp 737 production from 47 to 52 aircraft per month, a milestone contingent on FAA approval of its new North Line. The glitch could prolong FAA scrutiny and push certification timelines further out, jeopardizing Boeing's goal of first MAX 7 and MAX 10 deliveries in 2027. Investors had been cautiously optimistic about Boeing's recovery, but this news reinforces that regulatory risk remains a key overhang.

Implication

The software glitch introduces new uncertainty into an already delicate certification process, which could delay revenue recognition from stored MAX aircraft and backlog conversion. Boeing's valuation at over 30x EV/EBITDA leaves little room for execution missteps, and the stock may re-rate downward if the FAA imposes additional production constraints. Long-term holders should monitor the FAA's response and Boeing's ability to implement the fix quickly, as prolonged disruption would pressure free cash flow and debt reduction plans. Conversely, a swift resolution with minimal operational impact could be a buying opportunity, but that remains to be seen. Until clarity emerges, maintaining a wait-and-see approach aligns with Boeing's still-unproven recovery trajectory.

Thesis delta

The thesis previously assumed a smooth certification path for MAX 7/MAX 10 and a steady ramp in production, but this new glitch weakens that assumption by adding regulatory friction. The probability of certification delays increases, which would push out cash conversion from stored aircraft and backlog. Consequently, the investment case shifts further toward a 'wait' stance, with the attractive entry level potentially needing to be revised lower if the issue escalates.