The Boeing Seven Thirty-Seven Max VNAV Software Glitch, the FAA Investigation, and What an Automation Failure in the Max Fleet Tells Us About the Systems We Hand Our Descents To

The FAA is actively investigating a software glitch in the Boeing 737 Max family that can inadvertently disengage VNAV (vertical navigation) - the flight management system layer responsible for managing an aircraft’s entire vertical flight profile. Boeing has acknowledged the issue exists. The investigation is focused on determining which variants are affected, under what conditions the glitch triggers, and whether a fix requires a surface-level patch or a deeper review of the flight management software architecture.

What Is VNAV and Why Does It Matter?

VNAV is not the autopilot. The autopilot maintains heading and wings-level flight. VNAV is the flight management system layer that calculates and executes the vertical path - when to begin descent, how steep that descent should be, which altitudes to capture, and how to sequence the entire profile from cruise through a complex arrival procedure.

On a modern airliner, VNAV is active for most of the flight. It drives fuel burn calculations, top-of-descent planning, and compliance with altitude restrictions in complex STAR procedures. It is, functionally, the backbone of how crews manage the vertical dimension of every flight.

What Happens When VNAV Drops Out Unexpectedly?

An unexpected VNAV disengagement does not cause the aircraft to fall out of the sky. The autopilot retains the ability to hold altitude and heading. But vertical profile management reverts to manual, and the crew must simultaneously re-engage or rebuild the vertical path, verify FMS state, troubleshoot the dropout, and stay ahead of the airplane.

That is not an emergency in isolation. But it is a significant workload spike at precisely the moment workload is already high - during a busy arrival into complex airspace, with altitude restrictions to meet and sequencing to manage. The risk is not the dropout itself. The risk is the conditions in which it occurs.

Why the FAA Opened an Investigation Rather Than Waiting

The FAA’s decision to investigate publicly rather than wait for Boeing to self-report a fix reflects a changed regulatory posture. Since the 2018 and 2019 MCAS accidents - which grounded the entire Max fleet for nearly 20 months, the longest grounding of a commercial jet type in FAA history - the agency has moved toward more independent action rather than deferring to Boeing’s internal quality systems.

The 737 Max returned to service in November 2020. The scrutiny did not ease with that return. In 2024, a door plug blew out of an Alaska Airlines Max 9 at 16,000 feet over Portland, Oregon, triggering another round of audits, supplier reviews, and congressional testimony. The FAA imposed additional production limits. The Department of Justice reopened criminal proceedings related to the original MCAS accidents. Boeing replaced its CEO.

Each new anomaly enters a pattern the FAA is actively trying to interpret. A VNAV software glitch in isolation might warrant a service bulletin and a quiet fix. Against this backdrop, it warrants an investigation.

This Is Not MCAS - But the Pattern Still Matters

The VNAV glitch is a different category of problem than MCAS. MCAS was a system pilots were not fully informed about, one capable of overpowering manual control inputs under specific conditions. A VNAV dropout is a known-type failure in a known-type system. Crews are trained for it. The procedure for managing an unexpected VNAV disengagement is practiced in the simulator.

The FAA’s preliminary assessment does not indicate this glitch creates an imminent unsafe condition on its own. This is not a grounding order.

What it does raise is a question about software quality assurance at Boeing at a moment when that question carries exceptional weight. When a manufacturer has had to account for MCAS, a door plug separation, and manufacturing defects across multiple production facilities, another software anomaly in the flagship single-aisle program is not a standalone data point. It is evidence the FAA must weigh against a much larger institutional picture.

What Pilots on Max Operations Should Know Now

As of this reporting, Boeing has not released detailed public information about the specific software versions involved, the exact trigger conditions, or a proposed fix timeline. The investigation is ongoing.

For crew members operating the Max, the relevant technical information will flow through carrier safety departments and chief pilot offices as FAA documentation develops. The immediate operational priority is ensuring automation failure procedures are current and simulator currency is sharp heading into the next recurrent training event.

The Broader Lesson: Automation Dependency Across Every Glass Cockpit

The 737 Max story has a wider application - one that reaches into every glass cockpit aircraft in general aviation. Automation dependency is not a character flaw. It is a natural consequence of flying with systems that perform correctly the overwhelming majority of the time.

The FAA has studied automation complacency for decades. The data consistently shows that as system reliability increases, pilots shift from active monitoring to passive monitoring - from watching the instruments to trusting them. These are not the same posture. Airlines address this through recurrent training, simulator sessions that inject unexpected automation failures, and CRM protocols that keep both pilots cross-checking even when everything is functioning normally.

General aviation does not have a mandatory recurrent training infrastructure equivalent to Part 121 operations. A private pilot flying a Garmin G1000-equipped aircraft can legally fly for years without ever demonstrating to an instructor that they can manage an unexpected autopilot disconnect or FMS anomaly. The FAA and AOPA have both encouraged voluntary engagement with glass cockpit proficiency. But voluntary training is not the same as required training, and that gap matters.

What Every Pilot Should Do With This Information

For crew members on Max operations: stay current on company notices and treat the next simulator event as an opportunity to sharpen automation failure procedures, not merely satisfy a recurrency requirement.

For general aviation pilots: fly without the automation doing everything. Hand-fly a descent. Practice removing automation layers deliberately and periodically - not because the automation is untrustworthy, but because the skill of flying without it requires regular maintenance to remain fluid. Manual flying ability is the backstop behind every layer of automation in the panel.

For student pilots building hours in technically advanced aircraft: ask your instructor to demonstrate what happens when the autopilot disconnects unexpectedly. Ask what the airplane will do when VNAV mode drops. Ask about annunciations, control feedback, and the checklist response. Those questions belong in the practice area, not on a night approach in IMC forty miles from the alternate.

Key Takeaways

• The FAA is actively investigating a VNAV software glitch in the Boeing 737 Max that can cause unexpected disengagement of vertical navigation during flight; Boeing has confirmed the issue exists.
• A VNAV dropout is not an emergency on its own, but it generates a high-workload spike during arrivals when crew capacity is already constrained - which is precisely why it matters.
• This is not MCAS. But it adds to a documented pattern of software and manufacturing anomalies at Boeing that has materially changed how the FAA weighs the company’s internal quality assurances.
• The Max’s history - MCAS accidents in 2018 and 2019, a nearly 20-month grounding, the 2024 Alaska Airlines door plug incident - means each new issue receives scrutiny proportional to that record, not evaluated in isolation.
• Every pilot flying a glass cockpit faces the same underlying challenge: automation that works reliably erodes the manual skills and active monitoring habits that matter when it doesn’t. Practicing without automation is not optional proficiency - it is the safety margin behind the system.