Connect with us

Regulations & Safety

NTSB Attributes Flight 1632 Runway Excursion to Maintenance Errors

NTSB finds maintenance errors caused American Airlines Flight 1632’s brake failure, prompting safety protocol updates in aviation.

Published

on

Anatomy of a Runway Excursion: The NTSB’s Final Word on Flight 1632

On February 10, 2024, American Airlines Flight 1632, a Boeing 737-823, completed its journey from Washington, D.C., to Dallas-Fort Worth International Airport (DFW). The landing, however, was anything but routine. After touching down, the aircraft was unable to stop on the runway, ultimately coming to a rest in the paved overrun area. While the 104 passengers and crew deplaned safely with no injuries reported, the incident triggered a thorough investigation by the National Transportation Safety Board (NTSB).

When an aircraft experiences a runway excursion, initial speculation often turns to pilot action, weather conditions, or a fundamental design flaw. However, the NTSB’s final report, released on November 10, 2025, steers the narrative in a different direction. The findings bypass the cockpit and the weather, focusing instead on the meticulous, high-stakes world of aircraft maintenance. The report provides a critical look at how a procedural oversight on the ground can have significant consequences in the air, offering valuable lessons for the entire aviation industry.

This breakdown will dissect the NTSB’s official findings. We will explore the sequence of events during the landing, delve into the specific maintenance errors that led to the brake failure, and examine the subsequent safety recommendations issued to prevent a similar event from happening again. The story of Flight 1632 is a stark reminder that aviation Safety is a chain of countless links, and every single one matters.

The Incident Unpacked: A Routine Landing Turns Critical

Flight 1632’s approach to DFW was, by all accounts, normal. The crew prepared for landing on runway 17L under standard conditions. The aircraft touched down as expected, but the first sign of trouble appeared almost immediately. An “AUTOBRAKE DISARM” light illuminated in the cockpit, signaling a malfunction in the automated braking system designed to slow the aircraft smoothly and efficiently after landing.

A Sudden Failure

The flight crew’s training and experience kicked in instantly. The cockpit voice recorder captured the tense moments as the situation unfolded. The first officer was recorded stating, “The brakes will not… you got it?” The captain’s response was immediate and clear: “I got it. Brakes aren’t working.” This exchange highlights the crew’s swift recognition of a complete loss of braking effectiveness. The pilots were now manually trying to control an aircraft that was not responding as it should.

With conventional braking gone, the captain took manual control and deployed maximum reverse thrust, a procedure used to rapidly decelerate the aircraft by redirecting the engines’ power forward. Despite these efforts, the Boeing 737’s momentum carried it beyond the end of the runway. The aircraft finally came to a stop in the paved overrun area approximately 30 seconds after the crew first realized the brakes had failed. Thanks to the crew’s handling of the emergency and the presence of a safety overrun area, a potentially dangerous situation was contained without injury.

The passengers and crew deplaned onto the tarmac using airstairs, and while the event was undoubtedly alarming, the immediate outcome was safe. The focus then shifted from emergency response to Investigation. The NTSB was tasked with answering a critical question: Why did a modern aircraft’s braking system, one of its most critical safety features, fail so completely upon landing?

NTSB Findings: Tracing the Failure to a Maintenance Error

The NTSB’s investigation moved away from the flight deck and into the maintenance hangar. Their final report concluded that the probable cause of the runway excursion was not a design flaw or pilot error, but improper maintenance due to human error during a braking system modification.

The Root of the Problem

Investigators discovered that just four days before the incident, the aircraft had undergone scheduled maintenance at an American Airlines facility in Tulsa. The work involved a significant modification: replacing the aircraft’s steel brakes with newer carbon brakes. This complex task was performed by a team of six mechanics, each with over three decades of experience. Yet, despite this wealth of expertise, critical connection errors were made.

The NTSB found two specific and crucial mistakes. First, the flexible hydraulic hoses for the right main landing gear brakes were swapped, meaning the lines that deliver hydraulic pressure to the brakes were improperly reconnected. Second, the wiring harnesses for the left main landing gear’s wheel speed transducers were cross-connected. These transducers are essential sensors that tell the aircraft’s systems how fast each wheel is spinning.

These seemingly small errors had a cascading effect on the aircraft’s sophisticated braking systems. The misconnections directly impacted the antiskid system, which functions much like an anti-lock braking system (ABS) in a car. Its job is to prevent the wheels from locking up during heavy braking by modulating brake pressure, ensuring maximum braking efficiency without skidding.

The NTSB report cited a key contributing factor as “the lack of a functional check to verify the flexible hydraulic hoses and transducer wiring were connected correctly after the braking system modification.”

How the Errors Caused the Failure

With the hydraulic lines and sensor wiring crossed, the antiskid system received incorrect information and sent commands to the wrong places. Instead of releasing pressure on wheels that were about to lock up, the system was unable to perform its function correctly. This led to tire failure and a severe, sudden reduction in the aircraft’s ability to slow down, precisely what the flight crew experienced upon touchdown.

Crucially, the NTSB pointed out that the maintenance procedure lacked a final, critical step: a functional check to confirm that all connections were correct before returning the aircraft to service. This oversight allowed the hidden errors to go undetected until the system was needed most, during landing. The incident became a powerful case study in the importance of not just performing maintenance correctly, but also verifying that the work was done right.

The findings underscore that in a system as complex as modern aviation, safety relies on robust processes that include checks and balances. Even the most experienced technicians can make mistakes, which is why verification protocols are not just a formality, but a fundamental layer of safety.

Moving Forward: Industry Responses and Safety Enhancements

In the wake of the NTSB’s findings, the focus has shifted to implementing measures that will prevent a recurrence. The investigation into Flight 1632 provided a clear, actionable lesson for the aviation maintenance industry. In response, The Boeing Company has issued a list of best practices aimed directly at addressing the procedural gaps identified in the report.

These recommendations are not about redesigning the aircraft but about strengthening the human processes involved in maintaining it. The new guidelines are designed to be straightforward and effective, adding layers of protection against simple human error. They serve as an industry-wide update to maintenance protocols, ensuring that the lessons from this incident are applied broadly.

The core of the recommendations involves simple yet effective verification steps. Boeing now advises maintenance teams to temporarily label flexible hydraulic hoses to ensure they are reconnected to the correct brake positions. Similarly, wiring harnesses for wheel speed transducers should be labeled when disconnected. Most importantly, the new best practices call for the implementation of functional checks to verify that all hydraulic and electrical connections are correct after any braking system modification is performed. This final step provides a critical opportunity to catch any errors before an aircraft is cleared for flight.

Conclusion: A Stark Reminder of Procedural Importance

The runway excursion of American Airlines Flight 1632 at DFW was a serious event that, fortunately, concluded without injury. The NTSB’s investigation provides a clear and sobering conclusion: this was not a failure of design or a misjudgment in the cockpit, but a consequence of a procedural lapse on the maintenance floor. It serves as a powerful case study on the absolute necessity of meticulous, verified procedures in every aspect of aviation.

The incident highlights that safety is not just about advanced technology or skilled pilots; it is equally dependent on the disciplined, process-driven work of maintenance technicians. The subsequent recommendations from Boeing aim to reinforce this discipline by closing the procedural gap that allowed this error to occur. The story of Flight 1632 is ultimately one of continuous improvement, demonstrating how the aviation industry learns from every incident to build an even safer system for the future.

FAQ

Question: What was the official cause of the American Airlines Flight 1632 runway excursion?
Answer: The NTSB determined the probable cause was improper maintenance. During a brake system modification, hydraulic hoses and wheel speed transducer wires were incorrectly connected. This led to a malfunction of the antiskid system and a subsequent loss of braking effectiveness upon landing.

Question: Were any passengers or crew injured in the incident?
Answer: No. All 104 occupants on board deplaned safely via airstairs, and no injuries were reported.

Question: What changes have been made in the industry following this event?
Answer: In response to the findings, The Boeing Company issued a list of best practices for maintenance crews. These include better labeling of hoses and wires during maintenance and, most importantly, implementing mandatory functional checks to verify all connections are correct after any work on the braking system.

NTSB Final Report

Photo Credit: NTSB

Continue Reading
Click to comment

Leave a Reply

Regulations & Safety

FAA Opens $40M ATC Manufacturing Facility in Maryland

The FAA opened a $40M Rohde & Schwarz USA plant in Frederick, MD to produce VoIP switches for national ATC modernization by 2028.

Published

on

On August 25, 2026, the Federal Aviation Administration (FAA) and the U.S. Department of Transportation (USDOT) inaugurated a new $40 million manufacturing facility in Frederick, Maryland, dedicated to producing digital Voice over IP (VoIP) switches for the nation’s air traffic control network.

The 87,000-square-foot plant, operated by Rohde & Schwarz USA, represents a critical node in the FAA’s aggressive timeline to complete a nationwide air traffic control modernization overhaul by the end of 2028. According to an agency press release, the facility will build the CERTIUM Voice Communication System (VCS) to facilitate communication between air traffic controllers, pilots, and other control facilities.

Accelerating Air Traffic Control Modernization

The modernization effort is backed by a $12.5 billion down payment from the Working Families Tax Cut. U.S. Transportation Secretary Sean P. Duffy and FAA Administrator Bryan Bedford attended the opening to highlight the administration’s focus on domestic Manufacturing for critical aviation Infrastructure.

“Under President Trump, we aren’t just modernizing our skies at record speed—we’re putting American workers, American manufacturing, and American innovation first,” Duffy stated. “We’re making sure our air traffic control system is American made.”

Bedford emphasized the strict timeline driving the agency’s current procurement Strategy. He noted that the new facility supports the aggressive schedule to complete the new system by the end of 2028 while strengthening domestic production capabilities and creating high-quality jobs. Bedford described the equipment as a critical part of the landmark modernization effort.

Infrastructure Overhaul and Deployment Milestones

The opening of the Frederick plant follows a year of rapid infrastructure deployment by the FAA. The agency recently completed Wave 1 of its nationwide CERTIUM VCS deployment ahead of schedule. This milestone was marked by the installation of the 140th system at the Rapid City Regional Airport (RAP) control tower in South Dakota.

Beyond voice communication systems, the FAA has executed a massive infrastructure overhaul over the past year. The agency reports that 63 percent of legacy copper wires in air traffic control facilities nationwide have been replaced with high-speed fiber, 5G wireless, or Low Earth Orbit (LEO) capabilities.

Additional upgrades completed over the past year include the conversion of 388 radio sites and the installation of 176 IP voice switches. The FAA also deployed Surface Awareness Initiative technology at 96 towers, transitioned 21 towers to electronic flight strips, installed SMR4 Surface Movement Radars at five Airports, and added nine new Tower Simulation systems for controller Training.

AirPro News analysis

The opening of the Rohde & Schwarz USA facility in Maryland underscores a strategic shift toward localizing the supply chain for critical aviation infrastructure. By anchoring the production of digital VoIP switches domestically, the FAA mitigates supply chain risks that have historically delayed large-scale aerospace and infrastructure projects. We view the $12.5 billion funding injection as a substantial catalyst, though the 2028 completion target remains highly ambitious given the historical complexities of integrating new technologies into the national airspace system without disrupting active operations.

Sources: Federal Aviation Administration

Photo Credit: Federal Aviation Administration

Continue Reading

Regulations & Safety

Global Aerospace Issues Hangar Foam Suppression Safety Guidelines

Global Aerospace updates hangar fire suppression guidelines, citing 200+ accidental foam discharges and the shift to PFAS-free alternatives.

Published

on

Global Aerospace has issued updated safety and risk mitigation guidelines for aviation hangar fire suppression systems, highlighting the severe financial and environmental toll of accidental foam discharges. The aviation insurer published the comprehensive best practices on August 24, 2026, detailing the industry transition toward alternative fire protection technologies.

The guidance arrives alongside the introduction of the 2026 edition of National Fire Protection Association (NFPA) 409. This updated standard governs hangar fire protection and introduces critical changes to align requirements with modern aircraft design and growing environmental concerns regarding chemical suppressants.

The financial and human cost of accidental discharges

Fire suppression standards established in the mid-1970s heavily prioritized foam systems to combat large fuel-spill fires. However, Global Aerospace reports that these systems frequently cause more damage than the fires they are designed to prevent. Over the last two decades, more than 200 unnecessary foam discharges have occurred in aviation facilities.

These accidental activations have resulted in tens of millions of dollars in total damages, with the average per-incident cost reaching hundreds of thousands of dollars. Beyond property damage to aircraft and hangar infrastructure, accidental discharges pose severe life-safety risks to personnel.

The insurer cited a fatal 2014 incident at Eglin Air Force Base as a primary example of these hazards. Following a broken sprinkler pipe, the hangar filled with approximately 17 feet of foam in minutes, resulting in the death of one contractor.

Shifting standards and environmental-impact liabilities

Aviation insurers are increasingly processing claims that extend beyond immediate property damage to include long-term health risks and environmental restoration. This liability shift is largely driven by the presence of perfluoroalkyl substances (PFAS) in older aqueous film-forming foams (AFFF).

To mitigate these chemical risks, the aviation industry is actively transitioning toward fluorine-free foams and alternative fire suppression technologies. Global Aerospace highlighted the growing adoption of ignitable liquid drainage floor assemblies and optical flame detection systems, such as multi-spectrum infrared detectors. These alternatives eliminate hazardous chemicals and significantly reduce the likelihood of false alarms.

While the 2026 edition of NFPA 409 provides the framework for these modern systems, the updated standards must be adopted by local fire marshals before facilities can implement the changes.

Operational risk mitigation strategies

For facilities still operating legacy high-expansion foam (HEF) or AFFF systems, Global Aerospace recommends strict operational protocols to minimize the risk and impact of an accidental discharge. The insurer advises operators to protect all aircraft openings and secure sensitive electronics during maintenance operations.

In the event of a discharge, the guidelines stress the importance of keeping hangar doors closed to contain the foam and prevent environmental contamination outside the facility. Additionally, Global Aerospace recommends conducting all system testing and maintenance during off-hours to limit personnel exposure and operational disruption.

AirPro News analysis

The publication of these guidelines by a major aviation insurer underscores a broader industry reality: insurance providers are often the primary catalyst for operational safety upgrades. While regulatory bodies like the NFPA set the baseline standards, the financial pressure of uninsurable environmental liabilities tied to PFAS contamination is forcing hangar operators to modernize. We expect the transition to optical flame detection and drainage floor assemblies to accelerate rapidly as insurers begin pricing the risk of legacy foam systems out of the market.

Sources: Global Aerospace

Photo Credit: Global Aerospace

Continue Reading

Regulations & Safety

NTSB Preliminary Report: Ryanair 737-800 Engine Failure

NTSB confirms fan-blade-out on Ryanair 737-800 shattered cabin window, partially ejecting a passenger during climb from Thessaloniki.

Published

on

This is a developing story. Information may change as official details are released.

This is original reporting and analysis by AirPro News.

On August 13, 2026, the National Transportation Safety Board (NTSB) issued its preliminary report on a July 10 uncontained engine failure aboard a Ryanair Boeing 737-800, confirming that a fan-blade-out event shattered a cabin window and caused a rapid decompression. The incident resulted in a 61-year-old male passenger being partially pulled through the shattered window before being secured by fellow passengers.

The event occurred during climb out from Thessaloniki International Airport (SKG) in Greece. The flight, operated by Ryanair subsidiary Malta Air, was bound for Memmingen, Germany (FMM). The NTSB is currently investigating potential similarities between this event and a fatal 2018 engine failure, while the agency has also publicly addressed premature speculation regarding the cause by Ryanair leadership.

Flight 1879 rapid decompression

According to the NTSB preliminary report, the Boeing 737-800 was climbing when the right-hand CFM56-7B engine experienced a fan-blade-out event. Debris from the engine struck the fuselage and shattered a window at row 11. The resulting rapid decompression pulled a passenger partially outside the aircraft. The passenger sustained neck and shoulder injuries as well as friction burns, but no fatalities occurred.

Reporting by The Air Current indicates the failure happened at an altitude of approximately 15,000 feet. Passengers described a sudden and violent disruption to the flight. A passenger told AP News that the cabin was quiet before a loud noise resembling a bursting tire occurred, adding that they knew immediately the aircraft had lost pressure due to the sudden loss of altitude.

Initial reports following the July 10 incident suggested the failure occurred in the airspace of the Republic of North Macedonia. However, flight path analysis confirmed the event took place in Greek airspace. The Hellenic Air and Rail Safety Investigation Authority officially delegated the investigation to the NTSB on July 16, 2026.

Maintenance history and preliminary findings

The NTSB preliminary report notes that bird remains were found inside the damaged engine. Flight crews had reported four suspected bird strikes to the aircraft’s number two engine in the 12 months preceding the accident. The report states that bird remains were found in two of those previous cases.

Maintenance records indicate that the fan blades on the failed right engine underwent ultrasonic inspections in November 2025 and May 2026. No damage was found during either inspection. The official cause of the July 10 failure remains under investigation by the NTSB, with participation from the Federal Aviation Administration (FAA), Boeing, and CFM International, a joint venture between GE Aerospace and Safran.

Regulatory protocols and historical precedent

The investigation has generated friction between the NTSB and Ryanair regarding public communications. On August 7, 2026, NTSB Chair Jennifer Homendy issued a letter to Ryanair CEO Michael O’Leary after he told investors the investigation was focused on foreign object damage rather than aircraft age or maintenance. Homendy stated that the NTSB had made no such determination and noted that O’Leary’s comments violated International Civil Aviation Organization (ICAO) Annex 13 protocols governing accident investigations.

The aviation industry is closely monitoring the investigation due to the aircraft and engine types involved. The Air Current reported that the event closely mirrors the April 2018 Southwest Airlines flight 1380 uncontained engine failure, which also involved a Boeing 737-700 and a CFM56-7B engine. That incident resulted in one passenger fatality after a shattered window caused partial ejection, leading the FAA to mandate engine inlet redesigns by July 2028.

The NTSB addressed the historical context directly in its preliminary report:

The investigative team is aware of previous … events with similar engine models that resulted in damage to engine inlets or cowlings and fuselage structures. Determination of any relevant similarities or details between this accident and previous events remains under investigation.

AirPro News analysis

We observe that the public rebuke of a major airline CEO by the NTSB is a rare and significant enforcement of ICAO Annex 13 communication protocols. Operators typically defer entirely to the investigating authority to avoid compromising the integrity of an active probe. The NTSB’s swift correction underscores the agency’s zero-tolerance policy for operator speculation, particularly when an event involves high-profile safety concerns like uncontained engine failures.

The CFM56-7B is one of the most widely used commercial aviation engines in the world. Any investigation involving a fan-blade-out event on this powerplant will naturally draw intense regulatory scrutiny, especially given the precedent set by the 2018 Southwest Airlines accident. While the discovery of bird remains introduces foreign object damage as a variable, we expect investigators will rigorously examine the efficacy of the ultrasonic inspections conducted in November 2025 and May 2026 to understand how the blade failure propagated.

Sources: National Transportation Safety Board

Photo Credit: NTSB

Continue Reading
Every coffee directly supports the work behind the headlines.

Support AirPro News!

Advertisement

Follow Us

newsletter

Latest

Categories

Tags

Every coffee directly supports the work behind the headlines.

Support AirPro News!

Popular News