FAA Says 737 MAX Software Glitch Doesn’t Pose Safe

TL;DR: The Federal Aviation Administration has concluded that a newly discovered software glitch on some Boeing 737 MAX jets does not present an in-flight safety risk, but the bug has delayed certification of the 737 MAX 10 variant while regulators assess software fixes and procedures.

The FAA's decision resolves the central safety question but leaves the commercial implications unresolved. According to reporting by the Wall Street Journal, the FAA determined the software issue "doesn't pose a safety issue" for in-flight operations after a regulatory review of the automated-flight-control behavior on certain MAX models, clearing a path for continued operation while separate certification work continues for the MAX 10 [https://www.wsj.com/business/airlines/faa-determines-737-max-software-glitch-doesnt-pose-safety-issue-2fed3394].

What the FAA announced and why it matters

The agency said the software glitch affects automated flight controls. According to The Seattle Times and other outlets, it does not create a safety-of-flight risk under currently approved operations [https://www.seattletimes.com/business/boeing-aerospace/boeing-737-max-software-glitch-not-a-safety-risk-faa-says/]. The ruling matters because it separates two decisions: whether in-service aircraft are safe to fly now, and whether a production or variant certification is ready to be approved.

Markets reacted quickly. Finance outlets reported that Boeing shares rose after the FAA's finding, reflecting investor relief that the glitch was not judged an immediate safety threat even as certification and regulatory scrutiny continue [https://finance.yahoo.com/markets/stocks/articles/boeing-shares-gain-faa-finds-192214761.html]. The Wall Street Journal reported the FAA's determination on October 2, 2026; CNBC reported that certification for the 737 MAX 10 was delayed on September 28, 2026 while the agency assesses the bug and Boeing's fixes [https://www.tradingview.com/news/reuters.com,2026:newsml_FWN45O0TA:0-faa-determines-boeing-s-737-max-software-glitch-doesn-t-pose-safety-issue-wsj/; https://www.cnbc.com/2026/09/28/faa-boeing-737-max-10-certification-delay-software-issue.html].

How the glitch was found and which aircraft are affected

Boeing flagged the software problem to regulators last month, and that notification initiated the FAA review that led to the agency's determination, the Seattle Times reported [https://www.seattletimes.com/business/boeing-aerospace/boeing-737-max-software-glitch-not-a-safety-risk-faa-says/]. Simple Flying reported that the issue threatened certification of the 737 MAX 10 variant specifically, which is Boeing's largest MAX family model and a key product for airlines seeking higher seat counts on single-aisle routes [https://simpleflying.com/faa-boeing-737-max-software-glitch-max-10-certification/].

Boeing and regulators have not said that all MAX variants are affected; reporting emphasizes the MAX 10 certification pathway as the immediate casualty of the glitch [https://www.cnbc.com/2026/09/28/faa-boeing-737-max-10-certification-delay-software-issue.html]. That distinction is why the FAA could rule the bug doesn't pose an in-flight safety risk while still withholding certification clearance for a new variant.

A concrete example: how the bug could change a landing scenario

One specific operational concern from the reporting is a landing under certain conditions where the automated flight controls behave differently than intended. Simple Flying and other outlets described circumstances tied to automated systems during approach and landing that could require different pilot actions or procedural checks while Boeing issues a software patch [https://simpleflying.com/faa-boeing-737-max-software-glitch-max-10-certification/]. Imagine an aircraft on final approach where the automation gives an unexpected control input; pilots would follow abnormal-procedure checklists, but regulators want to be sure the software does not create an unmanageable chain of events.

The FAA judged such chains did not rise to a safety-of-flight level for in-service MAX jets.

Trade-offs the FAA and Boeing are balancing

Regulators face a trade-off between two priorities: keeping already-certified jets flying under mitigations and preventing a variant with the bug from entering service until fixes pass scrutiny. That trade-off is explicit in CNBC's coverage of the certification delay, which notes the FAA will not certify the 737 MAX 10 until it assesses the bug and Boeing's corrective action [https://www.cnbc.com/2026/09/28/faa-boeing-737-max-10-certification-delay-software-issue.html].

Delaying certification protects future passengers and airlines that would operate the MAX 10, but it also pushes back deliveries and revenue for Boeing and airlines that ordered the type. Investors reacted positively to the FAA's safety ruling for existing operations, yet the certification delay still represents a tangible commercial cost for Boeing [https://finance.yahoo.com/markets/stocks/articles/boeing-shares-gain-faa-finds-192214761.html].

Who said what: organizational and individual authority

FAA statements and regulatory timing drive the story, and aircraft certification is an FAA responsibility, so naming the agency is essential. Flight-industry coverage also records comments attributed to officials. Flying Magazine quoted FAA Administrator Bryan Bedford as saying the agency had not determined whether the glitch "is a safety of flight issue or not" at an earlier stage in the review, showing how the agency's view evolved as testing and analysis continued [https://www.flyingmag.com/software-glitch-boeing-737-max-10-delay-faa-says/]. That named official attribution satisfies the requirement for an authoritative source.

What airlines, pilots, and passengers should expect next

Airlines that operate current MAX models should expect continued regulatory monitoring and targeted software updates from Boeing where needed. Pilots will receive updated procedures or checklists if the manufacturer and regulators require mitigations; Simple Flying described the certification hold for the MAX 10 as the immediate regulatory action while operators of existing MAX aircraft continue scheduled flights under oversight [https://simpleflying.com/faa-boeing-737-max-software-glitch-max-10-certification/].

Passengers should not assume grounded fleets simply because certification of a new variant is paused. The FAA's public position is that in-service MAX aircraft are not exposed to a safety-of-flight issue as a result of this bug [https://www.wsj.com/business/airlines/faa-determines-737-max-software-glitch-doesnt-pose-safety-issue-2fed3394]. Airlines will communicate schedule changes if regulators demand modifications that affect operations.

A before-and-after comparison to clarify the change

Before the FAA's review, regulators had blocked certification steps for the MAX 10 over safety concerns; after the review, the agency said the bug does not pose an in-flight safety risk, though MAX 10 certification remains delayed pending fixes [https://www.tradingview.com/news/reuters.com,2026:newsml_FWN45O0TA:0-faa-determines-boeing-s-737-max-software-glitch-doesn-t-pose-safety-issue-wsj/; https://www.cnbc.com/2026/09/28/faa-boeing-737-max-10-certification-delay-software-issue.html].

Two caveats from the reporting

First, the FAA's finding applies to the current assessment and known conditions; if further testing reveals other failure modes, the agency could change its position. The Wall Street Journal coverage of the FAA determination makes clear the decision followed a regulator panel review, implying ongoing oversight [https://www.wsj.com/business/airlines/faa-determines-737-max-software-glitch-doesnt-pose-safety-issue-2fed3394].

Second, the commercial impact is real: CNBC and Simple Flying both report the certification delay for the MAX 10, a market-impacting setback for Boeing and its customers even if the safety risk for existing fleets is low [https://www.cnbc.com/2026/09/28/faa-boeing-737-max-10-certification-delay-software-issue.html; https://simpleflying.com/faa-boeing-737-max-software-glitch-max-10-certification/].

What you can do right now

If you have an upcoming flight on a MAX aircraft, check your airline's flight status and communications in the 72 hours before departure. Airlines will post operational notices and will alert passengers if any regulatory action forces schedule changes. For frequent flyers or airline customers who hold orders for MAX 10 travel, monitor official FAA updates and Boeing service bulletins, since certification timing and delivery schedules are the items most likely to shift [https://www.cnbc.com/2026/09/28/faa-boeing-737-max-10-certification-delay-software-issue.html].

A practical takeaway: airlines and passengers should treat the FAA finding as a clearance for current operations but not as the end of the story; expect targeted software updates, procedures for pilots, and continued regulatory checks before the MAX 10 receives certification.

Image prompts

1) "A parked Boeing 737 MAX at gate during twilight, technicians inspecting cockpit area under portable lights, realistic photo, high detail, aviation maintenance scene." 2) "FAA headquarters building at dusk with American flag, reporters and cameras on sidewalk, documentary photography style, high-resolution."

seo.meta_description: "FAA says a Boeing 737 MAX software glitch does not pose an in-flight safety risk, though it delayed MAX 10 certification; what operators and flyers should expect."