Boeing Knew About New 737 MAX Software Glitch For Nearly Two Years—United And Southwest Won’t Accept Aircraft With It
The Nature of the Software Glitch
The technical issue centers on the aircraft’s flight management system (FMS), specifically its vertical navigation (VNAV) functionality. During a "go-around" procedure—a critical phase of flight where a pilot aborts a landing and executes a climb-out to attempt another approach—the aircraft’s automation is designed to follow a precise vertical flight path.
According to technical reports, if a pilot modifies the programmed flight path following a missed approach, the flight management software can inadvertently trigger an incorrect switch in the VNAV mode. Instead of maintaining the expected vertical profile, the system may revert to a simpler, less capable automation mode, such as vertical speed or level change. While Boeing maintains that pilots are sufficiently trained to identify and manage this transition—either by reverting to the correct mode manually or by flying the aircraft using standard hand-flying procedures—the unexpected change in automation behavior during a high-workload, low-altitude maneuver presents an additional cognitive burden for flight crews.
Chronology of Disclosure and Delay
The timeline of this discovery has become a focal point of concern for both regulators and the flying public. While the software defect was identified internally by Boeing engineering teams approximately two years ago, it was not formally disclosed to operators until last month. This two-year gap raises significant questions regarding internal reporting protocols and the threshold for what constitutes a "safety-impacting" event under current aerospace reporting standards.
The timing of this disclosure could not be more sensitive for the manufacturer. The Boeing 737 MAX 10, the largest variant of the MAX family, was in the final stages of a protracted certification process. Industry observers expected the FAA to issue a final sign-off within days. However, upon learning of the latent software issue, the FAA halted the process, electing to convene a Corrective Action Review Board (CARB). This regulatory intervention effectively stalls the entry into service for the MAX 10, a cornerstone of Boeing’s competitive strategy against the Airbus A321neo.
Operational Responses: Southwest and United
Major U.S. carriers, which rely heavily on the 737 MAX for their narrowbody operations, have responded with pragmatic caution. Southwest Airlines and United Airlines have indicated that while they remain committed to taking delivery of new MAX aircraft, they are requesting that these jets be equipped with the older, stable software version rather than the updated iteration containing the glitch.
This request highlights a divergence in operational priorities. Airlines are prioritizing fleet growth and capacity management, but they are unwilling to accept aircraft that introduce new variables into their training and standard operating procedures (SOPs). American Airlines and Alaska Airlines, both of which operate significant MAX fleets, are also monitoring the situation closely. To date, none of the U.S. carriers have deployed the affected software version in their active fleets, providing a temporary buffer against immediate operational disruptions.
The Role of the FAA and Regulatory Oversight
The FAA’s decision to launch a formal Corrective Action Review Board marks a return to the rigorous, post-737 MAX grounding oversight model. The CARB process is designed to ensure that any software modifications or procedural updates proposed by the manufacturer are fully vetted for safety before being integrated into the flight control systems.
The agency has stated that it will act "immediately" should it identify any safety concerns that pose an unacceptable risk to flight crews or passengers. This stance is reflective of the heightened scrutiny the FAA has applied to Boeing since the mid-2019 return-to-service efforts. For its part, Boeing has remained firm in its position that the existing flight procedures are robust enough to allow for safe operation even in the event of a VNAV mode switch. The company is currently working on two parallel solutions: a software patch to rectify the logic error and a formal update to the pilot operating procedures to ensure that crews can effectively restore VNAV during a go-around.
Industry Implications and Technical Analysis
The incident serves as a case study in the challenges of modern aircraft automation. As flight decks have become increasingly digitized, the interaction between pilot input and automated systems has become more complex. In the case of the 737 MAX, the VNAV glitch is not necessarily a failure of the hardware, but a manifestation of how legacy flight management logic interacts with modern automation, particularly when pilot intervention—such as changing a flight path—occurs during the high-pressure environment of a go-around.
From a safety engineering perspective, the primary concern is not just the glitch itself, but the "surprise factor." When a pilot expects an aircraft to perform a specific automated function and the system deviates, the split-second reaction time required to troubleshoot the error can be critical. While Boeing is confident in pilot training, the aviation community remains cautious about any automation behavior that deviates from the expected "normal law" of flight deck operations.
Broader Impact on Boeing’s Reputation
The delayed disclosure of the software issue is likely to reignite debates regarding Boeing’s corporate culture and transparency. In the wake of the 737 MAX crisis, Boeing promised a wholesale overhaul of its internal reporting and safety management systems. The discovery that a known issue was held for 24 months before being surfaced to the FAA and operators is being viewed by some industry analysts as a regression in these promised reforms.
For investors, the uncertainty surrounding the MAX 10 certification is a financial headwind. The MAX 10 is essential for Boeing to maintain market share in the transcontinental and short-haul international markets. Every day that the aircraft remains grounded due to software validation processes, the competitive gap with Airbus widens. Furthermore, the need for a software patch and potential pilot training revisions adds costs to the production cycle, which are already strained by supply chain constraints and production rate fluctuations.
Moving Forward: Safety and Compliance
Looking ahead, the next few weeks will be decisive. The FAA’s CARB investigation will dictate the timeline for the MAX 10 certification. If the review board finds that a software patch is sufficient, the delay may be limited to a few months. However, if the FAA requires additional flight testing or extensive simulator verification, the timeline could extend significantly.
For the airlines, the immediate priority is fleet stability. By insisting on the older software, carriers are ensuring that their existing training regimes do not need to be overhauled on short notice. This "software versioning" approach is relatively common in aviation, but it creates a bifurcated fleet management challenge for airlines that must keep track of which aircraft are running which versions of the flight management software.
As the industry awaits the FAA’s findings, the broader takeaway remains clear: the aviation ecosystem is increasingly sensitive to software-driven anomalies. The era of "black box" automation is being replaced by a demand for total transparency, where the logic behind every flight system behavior is scrutinized, documented, and shared across the entire operator community. Boeing’s ability to navigate this period of heightened scrutiny will depend on its capacity to balance the need for rapid certification with the uncompromising requirement for transparent, proactive safety disclosure. The 737 MAX, already the most scrutinized aircraft in history, continues to be a bellwether for the future of aviation safety and regulatory accountability.
