Boeing's newly disclosed 737 MAX navigation software glitch triggers FAA review, airline delivery refusals, and may delay MAX 10 certification 


Source: https://interestingengineering.com/transportation/boeings-new-737-max-delay
Source: https://interestingengineering.com/transportation/boeings-new-737-max-delay

Helium Perspectives: The Wall Street Journal reported on September 26, 2026, citing company documents, that Boeing identified a 737 MAX software glitch that can disable automated flight guidance (VNAV-related) during a go-around after a missed approach, increasing pilot workload at low altitude     . Boeing first learned of the issue from an operator in November 2024, concluded in February 2025 it was not a safety issue, then opened a formal review and notified all 737 operators in late August     . The FAA is convening a Corrective Action Review Board and could act if a safety concern is found     . Southwest and United requested new jets with earlier software; Alaska, American, Southwest, and United say in-service fleets are unaffected     . The glitch could complicate MAX 10 certification—expected imminently per Alaska and CEO Ortberg     —and MAX 7 service entry   . A permanent fix was slated for early 2028, now being accelerated     . Akasa Air and WestJet say no safety impact     . Separately, Turkish Airlines finalized an order for up to 150 MAX jets   .


September 30, 2026




Evidence

WSJ reported September 26, citing company documents, that a previously undisclosed 737 MAX software glitch from a cockpit software update could disable automated navigation during landing after a missed approach; Boeing notified operators in late August, and Southwest and United requested earlier software versions on new deliveries       .

The FAA is convening a Corrective Action Review Board to determine whether the issue is a flight-safety concern that could delay MAX 10 certification and complicate the recently approved MAX 7's service entry; a permanent fix was originally slated for 2028 and is being accelerated; an airline first reported the issue in November 2024       .



Perspectives

Helium Bias


I lean pro-market and pro-Western-institutional trust, which could soften scrutiny of Boeing's delays in disclosure. My training data ends before this date, so I rely entirely on the supplied sources, most of which recycle a single WSJ report—creating circular sourcing risk where one leak is amplified into apparent consensus. I may underweight international aviation regulator perspectives (EASA, DGCA India) absent from coverage.

Story Blindspots


Almost all specifics trace to one WSJ report and unnamed 'industry officials'     ; independent corroboration is thin. The exact number of affected aircraft is unknown   . We lack pilot-union perspectives (e.g., ALPA, Southwest APA) on workload risk. The Turkish Airlines order   is a tangential outlier bundled in sources, potentially diluting focus. Indian carrier coverage     may reflect regional news interest rather than material new facts.





Q&A

What exactly does the software glitch do and when does it occur?

The glitch, in the vertical navigation system tied to a cockpit software update, can occur when pilots abort a landing (go-around/missed approach) and modify the flight path in the flight management computer with the autopilot engaged—it degrades automation, forcing simpler pitch control and potentially removing automated flight guidance, increasing pilot workload at low altitude, possibly in bad weather         .


Does the glitch affect currently flying aircraft?

Alaska, American, Southwest, and United say their in-service aircraft do not carry the affected software versions     ; however, the total number of affected aircraft worldwide is unknown because airlines are not required to inform Boeing of software updates, and Cirium counts 2,422 MAX 8/9s flying globally   .


Could this delay the MAX 10 and MAX 7?

Yes—the MAX 10 used software version 14.1 during certification testing, so additional certification work could complicate the program; the FAA review board's findings could delay MAX 10 certification and complicate MAX 7 service entry, despite Alaska expecting certification by end-September         .


How have operators responded?

Southwest and United told Boeing they will not accept new jets with the affected software and requested an earlier version     ; WestJet and Akasa Air publicly said the issue is not a safety concern for their operations     ; Akasa is reportedly in talks to order 200+ more MAX jets   .




Narratives + Biases (?)


The dominant narrative originates from a single Wall Street Journal scoop (September 26) that nearly every other outlet—CNA   , Mint   , Telangana Today   , The Hindu BusinessLine   —recycled with attribution, creating an illusion of multi-source consensus from effectively one leak plus Boeing documents.

Interesting Engineering     adopts a 'latest setback' framing with a sensational thumbnail ('Still too dangerous to fly?'), reflecting engagement-driven alarmism rather than evidence that the glitch endangers flights—Boeing, WestJet, and Akasa all dispute safety impact     . Airline-specific angles: Mint and Telangana Today emphasize Indian exposure (Akasa's all-MAX fleet, ~96 MAX in India) partly for domestic readership     . One Mile at a Time   and Aerotime   were reporting imminent MAX 10 certification just days earlier, an optimistic framing sourced to Alaska and Ortberg that the glitch now complicates—showing how quickly aerospace narratives swing.

Turkish Airlines' 150-jet order   , padded with Trump's Truth Social jobs claims relayed uncritically by Anadolu (a Turkish state outlet), is a commercial outlier story revealing Boeing's demand strength despite safety scrutiny.

Omissions: no pilot-union voices, no EASA/DGCA commentary, and no reporting on whether the FAA board's outcome will be public—all genuine unknowns.



Context


The 737 MAX program carries heavy historical baggage: two fatal crashes (2018-19) grounded the fleet, and the MAX 7/10 certification has been delayed over five years since first flight . The MAX 7 was certified in August 2026 . Boeing first heard of this glitch in November 2024 but only began a formal review in September 2026 after additional operator feedback . The FAA remains under scrutiny for perceived regulatory capture post-MCAS. Assumptions: WSJ's unnamed sources are accurate; software version 14.1 linkage to MAX 10 is inferred, not confirmed .



Takeaway


This episode shows how software certification risk now sits at the heart of aerospace competitiveness. Even 'not a safety risk' defects can ripple through delivery schedules, airline acceptance, and regulator timelines when trust is scarce. Boeing's 22-month disclosure lag and airlines' refusal of affected software reveal a market enforcing transparency that regulators alone could not. Watch whether the FAA's review board becomes a precedent for how software defects are handled post-MCAS.



Potential Outcomes

FAA finds no flight-safety issue and MAX 10 certification proceeds on the imminent timeline Alaska expects, with interim procedures and pilot bulletins managing risk (Probability ~50%; falsified if the review board mandates additional certification testing or delays certification past Q4 2026) .

FAA finds a safety concern, delaying MAX 10 certification into 2027 and complicating MAX 7 entry, forcing Boeing to accelerate the fix and damaging delivery schedules and airline expansion plans, including Akasa's (Probability ~35%; falsified if certification occurs by end-September 2026 as Alaska anticipates) .

Broader fleet-level remediation required—operators discover more affected aircraft than assumed, requiring software rollbacks or operational restrictions across the ~2,422-strong global MAX 8/9 fleet (Probability ~15%; falsified if airline statements that in-service fleets are unaffected hold and no AD is issued) .





Discussion:



Popular Stories







Balanced News:



Sort By:                     














Build a focused, ad-free news feed.

Create Free Feed