FAA Delays 737 Max 10 Cert After Software Bug; BA Drops 6%

For legal and regulatory counsel, the FAA's decision to delay 737 Max 10 certification is not an engineering story—it is a compliance and liability event. Boeing knew of the vertical-navigation bug in August but publicly disclosed it only Saturday, and the 6% single-day stock drop after Administrator Bryan Bedford's remarks raises immediate questions about the company's disclosure controls and potential securities exposure.

On September 28, 2026, Federal Aviation Administration Administrator Bryan Bedford publicly confirmed that certification of Boeing's 737 Max 10 will be delayed while the agency determines whether a recently identified software defect constitutes a safety-of-flight issue. The announcement landed during a press conference on air traffic modernization in Washington, D.C., and immediately extended losses in Boeing shares, which fell more than 6% in afternoon trading. Boeing had only days earlier signaled that approval could come "very soon," according to CEO Kelly Ortberg, making the reversal a significant regulatory and financial setback.

“

The announcement landed during a press conference on air traffic modernization in Washington, D.C., and immediately extended losses in Boeing shares, which fell more than 6% in afternoon trading.

The software problem involves the aircraft's vertical navigation system during a missed approach and subsequent go-around, particularly when pilots must line up to land again after an obstruction on the runway. Boeing said Saturday that it had first flagged the glitch to the FAA in August. The disclosure timeline matters as much as the technical issue: the company's public acknowledgment came roughly a month after it reportedly knew of the defect, and only after the agency's administrator discussed the delay. For a manufacturer still operating under heightened scrutiny from the 2018 and 2019 737 Max crashes, any gap between internal knowledge and public disclosure can carry legal and regulatory consequences, including questions about disclosure controls, potential securities claims, and customer notification obligations.

Bedford added that the FAA approved the Max 7 last month, the smallest member of the family, and that Boeing had fixed a previous bug in the same system but "unexpectedly ... introduced a new bug." That pattern—resolving one software issue only to introduce another—suggests deeper quality-assurance and change-management problems that will likely extend the certification runway and could prompt additional FAA oversight or conditions once approval is granted. U.S. airlines stated they have no Max aircraft with the bug and have reverted to older software where needed, which limits immediate operational exposure but may not eliminate contractual or reputational damage.

The certification delay is not occurring in a vacuum. Congress overhauled FAA certification processes through the Aircraft Certification, Safety, and Accountability Act after the 2018 Lion Air and 2019 Ethiopian Airlines crashes, which together killed 346 people and grounded the 737 Max for nearly two years. Under those reforms, manufacturers face stricter reporting obligations and the FAA has greater authority to oversee safety-critical systems. Boeing's experience with the Max 7—approved only after fixing one bug and then revealing another—illustrates how the new regime creates iterative, and often unpredictable, certification cycles. Each cycle not only delays revenue but also generates a paper trail that could become central in future administrative proceedings or litigation.