MCAS, the Boeing Seven Thirty-Seven MAX Grounding, and the Hidden Automation Failure That Rewrote FAA Certification of Flight Control Software

The Boeing 737 MAX grounding revealed how a single-sensor software system with no pilot disclosure caused two fatal crashes and triggered the most significant FAA certification reform in a generation.

Aviation Technology Analyst

The grounding of every Boeing 737 MAX in the world for 20 months following two fatal accidents was not primarily a story about a faulty sensor or bad software. It was a story about how a series of individually defensible engineering and certification decisions combined into a failure mode the entire oversight framework was not structured to catch - and how 346 people died before that was fixed.

Why MCAS Existed: An Engine Problem That Became a Software Problem

The Boeing 737 has been in continuous production since 1968 and holds the most common commercial jet type rating in the world. That type rating continuity is a central part of the aircraft’s commercial value: airlines that invest in check airmen, simulators, and line pilots already rated on type want that investment to carry forward when a new variant arrives.

When Airbus began offering the A320neo with new CFM International LEAP engines and meaningful fuel efficiency gains, Boeing needed a competitive response. The choice was between a clean-sheet replacement - a decade-plus effort costing north of $15 billion - or re-engining the existing 737. Boeing chose the second path. The result was the 737 MAX.

The LEAP engine has a larger fan diameter than the CFM-56 it replaced. The 737’s airframe sits close to the ground by original design - a deliberate 1960s choice to allow baggage loading without specialized ground equipment. With the larger engines, clearance requirements forced the nacelles to be mounted further forward and higher on the wing than the previous position.

That change had an aerodynamic consequence. At high angles of attack, the new engine nacelles generated lift in a way that created a nose-up pitching tendency the original 737 did not have. Left unaddressed, this would have changed handling qualities enough to require a new type certificate - meaning new training, new ratings, and the loss of the type rating continuity the MAX program was built around.

The Maneuvering Characteristics Augmentation System (MCAS) was Boeing’s engineering solution: a software system that would automatically apply nose-down horizontal stabilizer trim when it detected a high angle of attack condition, counteracting that pitching tendency and preserving the handling qualities 737 pilots expected. When functioning as designed, pilots would feel nothing unusual. MCAS would do its work invisibly.

The Design Decisions That Made MCAS Dangerous

Software-augmented handling is standard in modern commercial aviation. Fly-by-wire aircraft routinely use software to shape handling qualities, and both the 777 and 787 use control laws that modify pilot inputs to maintain stability. The concept of MCAS was not, by itself, the problem.

The problem was a set of specific design decisions that compounded each other in the worst possible way.

Single-sensor input. MCAS was designed to operate on data from a single angle of attack (AOA) sensor. Modern safety-critical aviation systems are built around redundancy because sensors fail - they ice over, take damage, or suffer contact corrosion on the ramp. The engineering standard for systems where failure can mean loss of an aircraft is dual or triple redundancy with cross-checking logic. MCAS used one sensor. If that sensor failed high, registering a falsely elevated angle of attack, the system would interpret that failure as a stall condition and respond accordingly.

Expanded authority. During the certification process, the stabilizer input limit was expanded considerably beyond the original design specification. MCAS could apply substantial nose-down stabilizer trim per activation - and it could reactivate. Each time a pilot pulled back on the control column to counter the nose-down input, if the sensor reading persisted, the system could reset and push nose-down again. The cumulative effect at low altitude in the minutes after departure could make the aircraft extremely difficult to control.

No meaningful pilot disclosure. The 737 MAX Flight Crew Operations Manual did not describe MCAS as a system crews needed to understand and manage. The transition course from the 737 NG to the MAX was brief. MCAS was not part of it. The design philosophy was that the system would be entirely transparent to the crew - it would do its job, and nobody would know it was there.

That philosophy holds until the sensor fails.

Lion Air Flight 610: October 29, 2018

The night before the first crash, the Lion Air aircraft that would become Flight 610 operated a flight from Bali to Surabaya. An erroneous AOA sensor reading triggered anomalies the crew noted and worked through. The issue was documented and addressed by maintenance. The sensor was not replaced.

On October 29, 2018, Lion Air Flight 610 departed Jakarta. Twelve minutes after takeoff, the airplane was in the Java Sea. All 189 people aboard were killed. The flight data recorder documented repeated MCAS activations driven by the erroneous sensor. The crew applied trim corrections; MCAS activated again. They attempted the runaway trim procedure. At low altitude in the minutes after departure, the available margins of time and altitude ran out.

Boeing issued an operations bulletin following the crash. It described the symptoms of anomalous trim behavior and referenced the existing runaway trim procedure. What it did not include was the name MCAS, a description of the system, an explanation of its single-sensor architecture, or any guidance on how its behavior differed from classic runaway trim in terms of authority and persistence. Pilots received a procedure. They did not receive a system description.

Ethiopian Airlines Flight 302: March 10, 2019

On March 10, 2019, Ethiopian Airlines Flight 302 departed Addis Ababa. Six minutes and eighteen seconds after takeoff, the airplane struck a field near Bishoftu. All 157 people aboard were killed.

The crew had received the bulletin issued after Lion Air. They applied the stabilizer trim cutout procedure. The Ethiopian Accident Investigation Bureau’s final report is thorough and unsparing: these were experienced pilots, flying an aircraft they were certified to fly, confronting a failure mode that had not been disclosed to them.

Within two days, China and Europe grounded the MAX. The FAA issued its emergency airworthiness directive on March 13, 2019, bringing down the entire operating MAX fleet worldwide - the most extensive grounding of a commercial aircraft type in the history of the agency.

What the Investigations Found

The combined investigations produced findings that forced a reckoning across the certification community.

The AOA disagree alert - the cockpit warning that the two AOA sensors were giving different readings - existed in the MAX avionics architecture but was only active on aircraft equipped with an optional AOA indicator display. That display was available as a purchasable add-on. Many operators, including Lion Air, had not ordered it. A safety-critical alert that might have given crews actionable information about a sensor disagreement was locked behind an extra-cost configuration.

The authority expansion during certification was processed through Boeing’s Organization Designation Authorization (ODA) system. The FAA’s own safety engineers were not fully informed of the scope of that increase before certification was finalized. That gap - between what Boeing’s ODA representatives approved and what FAA engineers knew - is central to why Congress acted.

Congressional investigators also found internal Boeing communications from the certification period in which engineers expressed concerns about how MCAS worked and how it was being described to operators. The 737 MAX was under significant schedule and commercial pressure - Boeing’s response to what internal communications described as an urgent competitive threat from the A320neo. The investigation found that pressure shaped decisions at multiple stages of the program.

The engineers who designed MCAS were not trying to build a dangerous system. What happened was a series of decisions - single-sensor reliance, expanded authority, minimal pilot disclosure, no required training - each of which seemed defensible in isolation, that combined into a failure mode the entire review framework was not equipped to catch. None of the individual reviews saw the full picture of what happened when all of those conditions were simultaneously true.

FAA Certification Reform: The Aircraft Certification, Safety, and Accountability Act

The Aircraft Certification, Safety, and Accountability Act, passed in December 2020, was the most significant legislative reform to FAA certification processes in decades. Its core provisions:

  • Required direct FAA engineer involvement in key ODA certification decisions
  • Reduced manufacturers’ ability to self-certify critical safety findings
  • Established new requirements for how software changes with flight safety implications are reviewed before service entry
  • Required manufacturers to disclose new and changed systems to flight crews in a way that supports accurate pilot understanding of system behavior

That last provision carries the longest reach. It codifies a principle that should have been self-evident: if a software system can override pilot control inputs, the pilot must know it exists, understand when it activates, and have the information needed to identify a malfunction and correct it. It did not require a law to be true. But it took 346 lives to get it written into one.

The Redesigned MAX: What Changed

The 737 MAX returned to service in the United States in November 2020. The redesigned MCAS uses inputs from both AOA sensors and activates only when both agree. Authority was reduced. The AOA disagree alert was made standard equipment on all aircraft. Full MCAS system training became mandatory for the type rating.

The software was rewritten and recertified under direct FAA oversight. EASA conducted an independent certification review before approving the return to service in January 2021. China’s Civil Aviation Administration (CAAC) completed its own review and returned the MAX to service in January 2023.

Since the redesigned MAX re-entered service, MCAS has not been a factor in any subsequent incident. The engineers who built the redesigned system were not more capable than those who built the original. What was different was the oversight framework, the information requirements, and the authority structure that required the right questions to be asked and answered before the airplane flew passengers again.

Why This Matters Beyond the 737 MAX

New cockpit automation platforms - AI-assisted decision support tools, envelope protection systems being certified for Part 23 aircraft, fly-by-wire architectures in advanced air mobility vehicles and next-generation business jets - all exist in the shadow of the MAX. The certification culture surrounding them is different from what it was in 2017. Whether that difference holds as commercial pressure builds in those new programs is a question the industry will keep answering in real time.

The mental model is not optional. When flying an automated aircraft, situational awareness depends on knowing what the automation is doing - the modes it operates in, its authority limits, when it will take control and when it won’t, and how to remove it from the equation when direct control is needed. That awareness is a primary safety mechanism. The design philosophy behind MCAS deliberately removed it in pursuit of a schedule and a type rating. The two accidents are the documentation of what removing that mechanism costs.


Key Takeaways

  • MCAS was designed to be invisible to pilots - to preserve 737 type rating continuity by masking an aerodynamic consequence of the larger LEAP engines - and that transparency-by-design became lethality-by-design when its single sensor failed.
  • Two accidents, 346 deaths: Lion Air Flight 610 (October 29, 2018, 189 killed) and Ethiopian Airlines Flight 302 (March 10, 2019, 157 killed) resulted from a failure mode that had not been disclosed to the crews who encountered it.
  • The AOA disagree alert was a paid optional feature on the original MAX - a safety-critical sensor disagreement warning locked behind an add-on that many operators, including Lion Air, had not purchased.
  • The Aircraft Certification, Safety, and Accountability Act (December 2020) mandated direct FAA engineer involvement in key certification decisions, reduced manufacturer self-certification authority, and required full crew disclosure for any system capable of overriding pilot inputs.
  • The redesigned MCAS uses dual-sensor input, reduced authority, and is now a required training item for the type rating - demonstrating the fix was always technically achievable; the original design reflected schedule pressure and a flawed disclosure philosophy, not engineering necessity.

Radio Hangar. Aviation talk, built by pilots. Listen live | More articles