Boeing flags a 737 MAX software glitch after missed approaches

The brief in 6 cards

1. Context1 / 6

   Boeing has informed 737 operators about a software issue affecting some 737 MAX aircraft. It can occur after a missed approach, also called a go-around: the pilot stops a landing and climbs away to try again or divert. If the crew then changes the route stored in the flight computer, the computer may switch off vertical navigation (VNAV), which helps manage the aircraft's planned climb and descent. The pilots keep control of the aircraft, but lose that layer of computer guidance. Boeing says it has strengthened existing procedures and is developing a software update. The FAA is reviewing the issue. The Hindu reported the story on 28 September 2026; Reuters and other outlets reported it earlier that week.

2. Key highlights2 / 6

   When it can happen: Reports describe a narrow sequence involving a precision approach, the autopilot, a go-around and a later change to the programmed route. This is not a claim that the autopilot shuts down during ordinary flight.

   What changes: The flight computer may drop VNAV and move to a simpler pitch-control mode, such as vertical speed. Think of a car's cruise control switching off when a driver changes route: the car still works, but the driver has to do more.

   Aircraft and software: Reports identify some in-service MAX 8 and MAX 9 aircraft and refer to software version U.14. The exact affected models and version designation remain unconfirmed against a public Boeing or FAA document.

   Boeing and FAA: Boeing says existing pilot procedures address the situation and that it is working on an update. The FAA says it is assessing the issue, will convene a Corrective Action Review Board and will review the proposed fix.

   India: PTI reporting dated 27 September gives a total of about 96 MAX aircraft operated by Air India Express and Akasa Air. That is the total fleet estimate, not a count of aircraft with the affected software. Akasa said there was no impact on its operations; the supplied reporting says no immediate DGCA comment had been made as of 27–28 September.

   Disclosure timeline: A report says Boeing first identified the issue in November 2024 and informed operators in August 2026. The November 2024 date has not been confirmed by Boeing or the FAA in a public statement and remains a high-priority fact check.

3. Key concepts3 / 6

   1. A go-around is a normal safety manoeuvre

   A missed approach is a planned procedure: the aircraft stops trying to land, climbs away and either makes another attempt or goes to another airport. Poor visibility, an occupied runway or an unstable approach can prompt it. It is like choosing not to squeeze into a parking space and driving around the block to try again.

   At a decision altitude or height, the pilot either has the required view of the runway and continues, or follows the missed-approach procedure. The manoeuvre is practised; it does not by itself mean an emergency or mechanical failure.

   2. The flight computer and VNAV

   The Flight Management System (FMS) stores the planned route, waypoints, altitudes and speeds. It works with the autopilot to help fly that plan. A navigation-app analogy helps: the app stores the route and gives directions, but in an aircraft the system can also guide the controls.

   LNAV handles the route across the map—left, right and straight. VNAV handles the up-and-down plan—when to climb, level off or descend, and what altitude to reach. If VNAV drops out, a simpler mode may hold a chosen climb or descent rate without tracking all the upcoming altitude targets. Pilots then have to manage more of that plan themselves.

   3. Automation can step down without the aircraft becoming uncontrollable

   Automation degradation is when a system loses some capability but continues in a simpler mode. Mode confusion can happen if a person thinks the system is still doing one job when it has changed modes. Imagine a rice cooker expected to switch itself off: if its mode changes quietly, the user may not notice until later. In an aircraft, alerts need to make a change clear and timely. The FAA review will help assess the issue; the draft does not establish whether crews would fail to notice this particular change.

   4. Safety-critical software and disclosure

   Safety-critical software is software whose failure could cause serious harm. Aviation software is developed, reviewed and tested against standards such as DO-178C. The level of review depends on how serious the consequences could be. The classification of this reported issue, and the timeline for telling operators, are contested; the November 2024 discovery date is not confirmed in a public primary source.

   5. Certification and airworthiness

   A type certificate approves an aircraft design. An airworthiness directive is a legally binding instruction requiring action to correct an unsafe condition. They are different: one approves a design, while the other directs a safety fix. The supplied sources do not identify a new airworthiness directive for this software issue.

4. Way forward4 / 6

   For Boeing: Complete the software update under FAA oversight and give operators a clear, formal interim procedure. Revisit how and when software issues are classified for disclosure.

   For regulators: The FAA review should assess both the proposed fix and the decision process around the issue. The DGCA should clarify whether it is examining the matter and, if needed, tell Indian operators what action to take. Avoid treating the lack of a public comment as proof of inaction.

   For airlines: Include the specific sequence—go-around, route change and possible VNAV dropout—in simulator training if the manufacturer and regulators confirm it is appropriate. Do not rely on unverified reset instructions.

   For system design: When automation steps down, the change should be clear and early enough for the person using it to respond. As more transport and medical systems rely on software, safety depends on people understanding what the system is doing at that moment.

5. Note5 / 6

   Why this matters for India

   PTI reporting on 27 September put the combined Indian 737 MAX fleet at about 96 aircraft—roughly 53 with Air India Express and 43 with Akasa Air. These are reported fleet estimates that can change with deliveries. They do not show how many aircraft carry the affected software; that number was not publicly known in the supplied reporting.

   Air India Express and Akasa Air use the MAX as part of their narrow-body operations. Using one aircraft type can lower training and maintenance complexity. The trade-off is that a common fleet issue may affect many aircraft at once, much like a household relying on one vehicle: it is efficient until that vehicle needs attention.

   The FAA certifies aircraft designs in the United States; the DGCA regulates civil aviation in India and aircraft on the Indian register. India relies on international certification expertise, but should still assess foreign safety information and clearly communicate any action for Indian operators. The 2019 grounding of the MAX in India is a reminder that local regulators make their own operational decisions.

   The story also raises an ethics question: when a manufacturer believes trained crews can manage a problem, who decides whether that is enough reason to delay telling operators? The commercial timing of certification and deliveries is relevant context, but the supplied record does not establish that it influenced any safety decision.

6. Note6 / 6

   What remains contested

   The disclosure dispute depends heavily on the reported November 2024 discovery date. That date comes from secondary coverage of Wall Street Journal reporting based on company documents; it has not been confirmed by Boeing or the FAA in a public statement. Do not present it as established fact.

   Reports describe U.14 as the affected software version and say a related 14.1 version was used in MAX 7 certification testing. Confirm both details against Boeing or FAA documentation.

   Reports mention resetting the system after a go-around, while Aviation Week describes work to formalise a way to restore VNAV. Those are not necessarily the same procedure. Do not publish operational reset instructions until a bulletin is located.

   The Indian fleet estimate is not the affected-aircraft count. Carrier statements about their own operations should not be generalized to the other carrier or to every aircraft. Reports that US airlines requested earlier software versions should remain attributed to those reports unless confirmed by the airlines themselves.

   The broader question is whether an issue that pilots may be trained to manage still requires earlier disclosure so that airlines and regulators can assess it for themselves. The available reporting records the positions and questions; it does not settle them.

Swipe or use ← → to move between cards.