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.
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.
Photo Credit: NTSB
Regulations & Safety
Thales to Upgrade Slovenian Airspace with New Radar System by 2027
Thales partners with Slovenia Control to install advanced co-mounted radar system enhancing air traffic surveillance and cybersecurity by mid-2027.
This article is based on an official press release from Thales Group.
On May 27, 2026, French aerospace and defense technology company Thales announced a major contracts with Slovenia Control, the national Air Navigation Services Provider (ANSP) for Slovenia. According to the official press release, the agreement covers the delivery and installation of a co-mounted primary and secondary surveillance radar system designed to modernize the country’s air traffic management capabilities.
The new infrastructure, slated for deployment by mid-2027, aims to provide continuous, redundant 24/7 surveillance of Slovenian airspace. As European flight volumes continue to climb past pre-pandemic levels, ANSPs are increasingly tasked with upgrading legacy systems to handle denser, more complex traffic flows safely.
We note that this upgrade aligns with the latest EUROCONTROL and International Civil Aviation Organization (ICAO) recommendations, ensuring Slovenia remains fully compliant with European Mode S Station (EMS) standards while bolstering its defenses against modern cyber threats.
Upgrading Slovenia’s Airspace Infrastructure
Building on a 30-Year Partnership
Thales and Slovenia Control have collaborated for nearly three decades. The press release highlights that Thales has previously supplied the ANSP with various Air Traffic Management (ATM) solutions, including Automatic Dependent Surveillance–Broadcast (ADS-B) systems, Instrument Landing Systems (ILS), and an upgraded Air Traffic Services Message Handling System (AMHS). Additionally, Thales previously won a tender to deliver and install a wide area multilateration (WAM) system at Ljubljana Joze Pucnik Airport.
For this latest project, the new radar system will be mounted on a newly constructed 30-meter tower. To ensure uninterrupted and reliable operation during severe weather conditions, the equipment will be enclosed within a protective radome.
Next-Generation Radar-Systems
STAR NG and RSM NG Capabilities
The contract specifies a “co-mounted” configuration, integrating two distinct but complementary radar technologies on the same physical structure to track both cooperative (transponder-equipped) and non-cooperative aircraft.
The primary surveillance radar, the STAR NG, is an S-Band system tailored for Approach Control. It offers a surveillance range of up to 80 nautical miles and detects physical objects without relying on aircraft transponders. Notably, the STAR NG features advanced clutter reduction technology to filter out interference from wind farms and 4G mobile communication networks. It is also capable of detecting small, slow-moving targets such as Unmanned Aerial Vehicles (UAVs) and Drones.
Operating alongside it is the RSM NG, a digital secondary surveillance radar described by Thales as a “Meta Sensor.” This system communicates with aircraft transponders to gather identity, altitude, and speed data. It combines Monopulse Secondary Surveillance Radar (MSSR) architecture with fully integrated, redundant ADS-B. According to the provided technical specifications, the RSM NG can track up to 2,000 aircraft per scan and conduct simultaneous Mode S interrogations.
Cybersecurity at the Forefront
With critical aviation infrastructure increasingly targeted by digital threats, both radar systems are engineered to be “cybersecure by design.” The RSM NG utilizes a cybersecurity framework based on National Institute of Standards and Technology (NIST) standards. It incorporates a virtual machine designed to preserve the radar’s operational behavior while actively protecting the system against jamming, spoofing, and unauthorized cyber intrusions.
“We are honoured that Slovenia Control has once again placed its trust in Thales with the order of this new co-mounted air traffic control radar. This contract reflects not only our commitment to delivering advanced radar surveillance solutions, but also the strength of our long-standing Partnerships in ensuring safe and efficient air operations across Europe.”
, Lionel de Castellane, Vice President of Thales’ Air Traffic Control radars segment, via company press release.
“We are pleased to take this important step forward together with our partner Thales, with whom we share a common goal: safe, efficient and modern air traffic management. This cooperation further strengthens our commitment to continuously enhancing the safety and performance of air navigation services in Slovenia and beyond.”
, Rok Marolt, CEO of Slovenia Control, Ltd., via company press release.
Industry Context: The Pressure on European Skies
The necessity of this infrastructure upgrade is underscored by current European air traffic trends. According to EUROCONTROL’s Spring 2026 forecast cited in the provided research data, European air traffic fully recovered to pre-pandemic levels in 2025, recording 11.05 million flights.
Despite geopolitical disruptions, traffic within the European Civil Aviation Conference (ECAC) area is projected to grow by an additional 2.7% in 2026, reaching approximately 11.3 million flights. This rising volume places immense strain on the European airspace network. In May 2026, EUROCONTROL reported that Air Traffic Control (ATC) capacity and staffing issues accounted for 44% of all en-route delays across Europe.
AirPro News analysis
As the skies become more crowded, structural capacity limits are being severely tested. ANSPs like Slovenia Control are effectively forced to invest in high-precision, automated, and redundant surveillance technologies. Systems like the STAR NG and RSM NG combination are critical for safely reducing aircraft separation distances and managing complex traffic flows efficiently. Furthermore, the specific capability to filter out modern airspace “noise”, such as drone proliferation, wind farms, and 4G interference, demonstrates how technological leaps are required just to maintain baseline safety in an increasingly congested and digitized airspace.
Frequently Asked Questions
What is a co-mounted radar system?
A co-mounted radar system integrates two different types of radar, typically a primary radar (which bounces radio waves off physical objects) and a secondary radar (which communicates with aircraft transponders), onto the same physical tower or structure. This provides comprehensive tracking of both cooperative and non-cooperative aircraft.
When will the new radar system in Slovenia be operational?
According to the Thales press release, the new radar system is scheduled to be delivered and installed by mid-2027.
Why is cybersecurity important for air traffic control radars?
Modern air traffic control relies heavily on digital data and automated systems. Protecting these systems from jamming, spoofing (broadcasting fake aircraft signals), and cyber intrusions is critical to preventing airspace disruptions and ensuring passenger safety.
Sources: Thales Group Press Release
Photo Credit: Thales Group
Regulations & Safety
FAA Proposes $336,000 Fine Against Planet Nine Private Air
The FAA alleges Planet Nine Private Air misclassified 21 international commercial charter flights, proposing a $336,000 civil penalty.
This article is based on an official press release from the Federal Aviation Administration (FAA).
The Federal Aviation Administration (FAA) has proposed a $336,000 civil penalty against Planet Nine Private Air, a luxury private jets operator based in Van Nuys, California. The agency alleges that the company intentionally misclassified a series of international commercial charter flights to bypass strict regulatory requirements.
According to the FAA’s May 28, 2026, press release, the enforcement action targets operations conducted between November 2023 and August 2024. The agency claims that Planet Nine filed inaccurate flight plans for 21 passenger flights, labeling them as general aviation rather than commercial charter operations.
This alleged misclassification allowed the operator to circumvent the need for specific overflight and landing permits from foreign aviation authorities. The FAA’s enforcement letter emphasizes the severity of these actions, noting that the company failed to follow its own internal procedures during these international routes.
Details of the FAA Allegations
The core of the FAA’s allegations revolves around the strict regulatory boundaries that separate private flying from paid passenger transport. By filing the 21 flights in question as general aviation, Planet Nine allegedly avoided the rigorous oversight and international permitting processes required for commercial operators.
The FAA alleges that the luxury private jet operator violated international aviation regulations by intentionally misclassifying commercial charter flights… and operating in a “careless and reckless manner.”
In addition to the misclassification, the FAA states that Planet Nine failed to adhere to its own Oceanic and International Procedures Manual. The agency views the circumvention of these established safety and operational protocols as a serious breach of aviation regulations.
International Scope and Procedural Failures
The 21 flights cited in the FAA’s enforcement letter highlight a broad international scope. According to the provided research report, the operations took place between the United States and eight foreign nations: Canada, Costa Rica, the Czech Republic, France, Germany, Ireland, Sweden, and the United Kingdom.
Operating commercial charters in these jurisdictions typically requires extensive documentation, costly fees, and significant lead times for approval. The FAA alleges that by misidentifying the flights, Planet Nine bypassed these international bureaucratic requirements entirely.
Industry Context and Company Background
Planet Nine Private Air, often branded as Planet 9, is a boutique charter and aircraft management company. Co-founded in 2018 by CEO Matt Walter and Director of Operations James Seagrim, the company operates a “floating fleet” of ultra-long-range business jets, including Dassault Falcon 7Xs, Bombardier Global series, and Gulfstream G550/G650s.
Historically, the operator has touted high safety standards, holding an FAA Part 135 operating certificate alongside Wyvern Wingman and ARGUS Platinum safety ratings. The company maintains a presence in London and New York, in addition to its California headquarters.
The Regulatory Divide: Part 91 vs. Part 135
Understanding the FAA’s proposed penalty requires distinguishing between Part 91 and Part 135 regulations. General aviation (Part 91) governs private, non-commercial flights, which generally face fewer regulatory hurdles and faster approval times for international routing.
Conversely, commercial charter operations (Part 135) involve paying passengers and are subject to much stricter safety, maintenance, and crew rest regulations. Foreign governments mandate that Part 135 operators secure specific permits, which demand rigorous oversight. The FAA’s categorization of Planet Nine’s actions as “careless and reckless” stems from the alleged intentional evasion of these commercial safety standards.
Next Steps for Planet Nine
Following the receipt of the FAA’s enforcement letter, Planet Nine Private Air has a 30-day window to formally respond to the agency. The company has several legal avenues available to address the proposed civil penalty.
The operator can choose to pay the $336,000 fine, attempt to negotiate a settlement with the FAA, or formally contest the allegations and the penalty amount through an administrative legal process.
AirPro News analysis
We note that this proposed $336,000 fine underscores the FAA’s ongoing commitment to strictly enforcing the boundaries between Part 91 and Part 135 operations, particularly in complex international airspace. While Planet Nine Private Air is a well-established operator with premium safety ratings, these allegations highlight the immense logistical pressures and costs associated with global commercial charters.
If the FAA successfully levies this penalty, it will likely serve as a strong deterrent to other boutique charter operators. The enforcement action sends a clear message that the agency is actively monitoring international flight plan accuracy and will penalize attempts to bypass the bureaucratic and financial requirements of commercial aviation.
Frequently Asked Questions
What is the proposed fine against Planet Nine Private Air?
The FAA has proposed a civil penalty of $336,000.
How many flights are involved in the allegations?
The FAA alleges that 21 international flights were misclassified between November 2023 and August 2024.
What is the difference between Part 91 and Part 135?
Part 91 regulations govern private, general aviation flights with fewer regulatory hurdles. Part 135 regulations govern commercial charter flights, requiring stricter safety oversight, maintenance standards, and specific international permits.
Sources
Photo Credit: Planet Nine Private Air
Regulations & Safety
TSB Reports Fatal 2023 Helicopter Accident During Maintenance Run
TSB Canada details a fatal 2023 helicopter accident at Smithers Airport caused by skipped checklists and pilot distraction. Mustang Helicopters updates safety policies.
This article is based on an official press release from the Transportation Safety Board of Canada.
On May 27, 2026, the Transportation Safety Board of Canada (TSB) released its final investigation report (A23P0040) detailing the circumstances surrounding a fatal incident that occurred three years prior. The incident, which took place on May 6, 2023, at Smithers Airport (CYYD) in British Columbia, involved an Airbus Helicopters AS 350 B3 operated by Mustang Helicopters Inc.
According to the official TSB press release and accompanying report, the accident occurred during a maintenance ground run, resulting in the death of one ground worker and serious injuries to another. The investigation highlights critical safety issues, specifically the severe dangers of procedural complacency and digital distraction in the cockpit during ground operations.
The Incident at Smithers Airport
Maintenance Ground Run Turns Fatal
The TSB report outlines that on the day of the accident, the Airbus AS 350 B3 helicopter (registration C-GUXR) was undergoing maintenance ground run operations. The specific procedure was designed to balance the tail rotor drive shaft, a highly technical task that requires the helicopter’s rotor system to be operated at nearly full RPM.
During the third maintenance ground run of the day, the aircraft suddenly entered an uncommanded and rapid rotation. At the time, two maintenance staff members were positioned on the ground near the helicopter’s left cargo door to monitor the balancing equipment. As the helicopter spun out of control, both workers attempted to evade the aircraft but were struck multiple times by the tail rotor. Tragically, one worker was fatally injured at the scene, while the other sustained serious injuries and was airlifted to a local hospital.
The TSB investigation notes that the pilot eventually managed to move the engine control to IDLE, shut off the fuel supply, and apply the rotor brake. The helicopter came to a rest after rotating approximately 540 degrees. The aircraft remained upright throughout the event, and no post-impact fire occurred.
Investigation Findings and Human Factors
Skipped Checklists and Unseen Hazards
In its analysis of the events leading up to the uncommanded rotation, the TSB identified several critical human factors and procedural deviations. Following the first maintenance run of the day, the pilot abbreviated the operator’s official checklist to expedite the process.
The pilot abbreviated the operator’s official checklist to expedite the process, viewing the task as “routine and repetitive.”
According to the TSB, this deviation meant that crucial safety steps were missed. Specifically, pressure was left in the hydraulic system, and the right anti-torque pedal remained engaged in a fully forward position. Because the checklist was skipped, this critical hazard went completely undetected prior to the third engine start.
The Role of Digital Distraction
A central finding of the TSB report is the role of digital distraction in the cockpit. Investigators found that the pilot’s attention was split between the highly sensitive maintenance operation and a cellphone, which was connected to a Bluetooth earpiece.
Because the pilot was looking down when the rapid rotation began, he was not expecting the sudden movement. The TSB concluded that his delayed response to the rotational yaw force was insufficient to stop the helicopter from spinning quickly. Investigators emphasized that the minimal time saved by skipping the official checklist was negligible and ultimately contributed to the fatal outcome.
Industry Implications and Safety Actions
Regulatory Blind Spots
The TSB report highlights a significant regulatory gap within the Canadian aviation framework. Currently, there are no Transport Canada regulations that explicitly prohibit the use of cellphones or personal electronic devices in the cockpit during operations.
The safety board has previously identified the severe risks associated with cellphone use in aviation accidents, noting that electronic devices can fatally divert a pilot’s attention from activities necessary for safe operations. The TSB presents this incident as a grim case study on the dangers of complacency during ground operations, which are often falsely perceived by crews as lower-risk than active flight.
Operator Corrective Measures
Following the tragic occurrence, Mustang Helicopters Inc. implemented several corrective safety measures aimed at preventing future incidents. According to the TSB report, the company introduced a strict new distraction policy that explicitly requires the stowing of all electronic devices during operations.
Additionally, Mustang Helicopters added a new standard operating procedure (SOP) specifically tailored for maintenance ground runs to its operations manual. The company also thoroughly revised and strengthened its hazard assessments and safety briefings for both maintenance personnel and pilots.
AirPro News analysis
We note that this tragic event underscores a critical vulnerability in modern aviation operations: the intrusion of personal electronics into safety-critical environments. While active flight operations often command a pilot’s full attention, ground operations, such as maintenance runs, can falsely appear lower-risk, inviting a dangerous level of complacency. The TSB’s findings suggest that regulatory bodies like Transport Canada may need to urgently modernize their frameworks to explicitly address digital distractions. Ensuring that the cockpit remains a sterile, focused environment, even when the aircraft is firmly on the ground, is paramount to preventing similar tragedies in the future.
Frequently Asked Questions (FAQ)
What caused the helicopter to spin during the maintenance run?
According to the TSB, the pilot skipped portions of the checklist, leaving hydraulic pressure in the system and the right anti-torque pedal in a fully forward position. When the engine was started for the third run, this caused an uncommanded and rapid rotation of the aircraft.
Why didn’t the pilot stop the rotation immediately?
The TSB investigation found that the pilot was distracted by a cellphone connected to a Bluetooth earpiece and was looking down when the rotation began. This distraction led to a delayed and insufficient reaction to the sudden yaw force.
Are pilots allowed to use cellphones in the cockpit in Canada?
The TSB report highlights that there are currently no Transport Canada regulations explicitly prohibiting the use of cellphones or personal electronic devices in the cockpit during operations, identifying this as a significant regulatory blind spot.
Sources
Photo Credit: TSB
-
Regulations & Safety6 days agoNTSB Urges FAA to Update Runway Condition Assessment Matrix for Heavy Rain
-
Space & Satellites5 days agoUS Space Force Awards SpaceX $2.29B Contract for Military Satellite Network
-
Space & Satellites5 days agoFAA Orders SpaceX Investigation After Starship Flight 12 Booster Mishap
-
Space & Satellites3 days agoBlue Origin’s New Glenn Rocket Explodes During Test at Cape Canaveral
-
Route Development5 days agoHong Kong International Airport Opens Expanded Terminal 2 for Departures