NTSB Faults FAA, Army Equipment and Tower Culture in Potomac Midair Collision

Lead: On Jan. 29, 2025, the National Transportation Safety Board concluded that a sequence of regulatory, procedural and equipment failures allowed an Army Black Hawk helicopter to collide with American Airlines Flight 5342 over the Potomac River near Ronald Reagan National Airport, producing catastrophic results. The NTSB unanimously found that the Federal Aviation Administration approved flight paths that did not ensure safe separation, that air traffic controllers relied excessively on pilots to see and avoid each other, and that faulty altimeter behavior on the Black Hawks misled their crews. The board tied the crash to longstanding FAA decisions about route design, staffing and oversight, and issued more than 70 findings and dozens of recommendations to prevent recurrence.

• Key Takeaways
• The collision occurred on Jan. 29, 2025, involving an Army Black Hawk and American Airlines Flight 5342 over the Potomac River near Ronald Reagan National Airport.
• The NTSB approved its final determination unanimously and issued over 70 findings plus dozens of safety recommendations.
• Investigators found that FAA-approved routes placed the Black Hawk and Flight 5342 in crisscrossing paths without engineered separation, increasing collision risk.
• The tower routinely diverted traffic to Runway 33 on busy nights, placing arriving airliners in proximity to helicopter routes.
• Air traffic controllers relied heavily on visual separation, a practice the NTSB said introduced unacceptable risk in congested airspace.
• Altimeter idiosyncrasies on the Black Hawks likely led pilots to believe they were about 100 feet lower than they actually were.
• The NTSB said a controller failed to warn either crew explicitly about imminent collision risk, and that ADS-B In could have alerted crews almost a minute earlier.

Background

Reagan National sits under constrained airspace and routinely handles dense traffic patterns for both commercial and military operations. The airport’s proximity to the Potomac River makes river corridor routes attractive for helicopters, while arrival flows for fixed-wing traffic are tightly sequenced. For years controllers and other aviation personnel raised concerns about mixing helicopter river routes and backup runway arrivals, but the NTSB concluded those appeals were not acted on effectively.

The FAA in 2018 downgraded the facility rating for National Airport, a decision that reduced the experience threshold and pay for some controller positions, the board said, and that change made attracting and retaining seasoned staff more difficult in a high cost area. Investigators also described a culture in the tower and within the FAA that discouraged raising safety concerns and noted that a traffic management tool installed at the facility had never been activated, limiting controllers tools to manage surges in demand.

Main Event

On the night of Jan. 29, heavy traffic prompted controllers to route American Airlines Flight 5342 to the backup Runway 33. Simultaneously an Army training flight in a Black Hawk was transiting the river corridor with an instructor pilot evaluating a less experienced pilot. The NTSB found the assigned controller was responsible for both helicopter and airplane traffic, a setup the board said should have been separated.

Investigators determined the helicopter crew requested visual separation early in the approach and likely never had the commercial jet in sight as the two aircraft converged. The jet crew was preparing for landing and, according to the board, had not been warned by the controller about the helicopter’s approach. In animated simulations presented at the board meeting, the instructor pilot lost sight of the jet and regained visual contact only a second or two before impact.

Contributing to the collision, the NTSB concluded, were altimeters on the Black Hawks that exhibited measurement quirks the Army had not documented for aircrews. Investigators said the pilots probably believed they were flying roughly 100 feet lower than their actual altitude. The Army had not been systematically collecting the data that would have highlighted the instrument anomalies and relied on voluntary reports that rarely occurred.

The board also emphasized that had crews been equipped with ADS-B In real-time traffic displays, they might have received an alert nearly a minute before the collision, providing ample time to maneuver and avoid the other aircraft.

Analysis & Implications

Operationally, the report exposes how route design and traffic management choices can create latent hazards that remain dormant until demand and a convergence of small errors produce a catastrophe. The FAA’s historical tolerance for mixing visual separation with closely timed arrivals created a narrow margin for error; once controllers were overloaded, that tolerance became a systemic vulnerability rather than a mitigated risk.

For regulators and lawmakers, the findings will likely prompt calls to mandate separation standards for mixed helicopter and airplane operations near busy terminals, to require activation of traffic management systems, and to accelerate ADS-B In equipage or alternative realtime surveillance in cockpits. The NTSB also highlighted personnel policy effects, noting that the 2018 facility rating change and its compensation impacts may have eroded controller experience at one of the nation’s busiest towers.

From a military safety perspective, the board’s critique of the Army’s data collection and reporting practices could lead to tighter oversight of aircraft equipment tolerances and mandatory dissemination of known instrument behavior to aircrews. The Army may need to institute systematic altimeter performance monitoring, change maintenance or calibration procedures, and update training materials to prevent pilots from developing an undetected false sense of altitude.

Comparison & Data

The table summarizes the core factual elements the NTSB highlighted. In context, investigators told the board that routine diversion to Runway 33 and the airport’s heavy traffic load were immediate operational stressors, while the facility rating downgrade and a nonactivated traffic management system were longer-term organizational contributors.

Reactions & Quotes

The NTSB chair framed the crash as preventable and placed primary responsibility on systemic lapses rather than individual error. Her remarks underscored the board’s unanimous judgment that multiple agencies and practices failed to prevent the collision.

This was 100 percent preventable

Jennifer Homendy, NTSB chair

The FAA emphasized cooperation with the investigation and noted steps already taken. An FAA spokesperson pointed to immediate actions implemented after the crash and said the agency will review the new recommendations carefully as it continues modernization and safety work.

The FAA values and appreciates the NTSB’s expertise and input and will carefully consider the board’s additional recommendations

Hannah Walden, FAA spokeswoman

NTSB investigators also highlighted tactical failures in the tower and the missed opportunity that timely controller intervention would have created. The lead investigator for air traffic control cases summarized the evidence that controllers were not adequately prepared for the workload and that an explicit warning likely would have averted the collision.

They were not adequately prepared to do the jobs they were assigned to do

Brian Soper, NTSB air traffic control investigator

Unconfirmed

• Whether specific FAA internal memos detailed the cumulative risk prior to the crash has not been publicly released and remains under review.
• The precise extent to which Army leadership was aware of widespread altimeter idiosyncrasies across Black Hawk fleets is not fully documented in the public record.
• The timing and final content of any legislative package that would fund FAA modernization and whether it will include the board’s recommendations are unresolved.

Bottom Line

The NTSB’s report attributes the Potomac midair collision to a concatenation of regulatory, cultural and equipment failures rather than to a single human error. Its findings make clear that route design, staffing and information flow matter as much as real-time decisions in preventing midair conflicts, and that technological gaps such as missing ADS-B In equipage and unreported altimeter biases materially worsened risk.

Watch for regulatory changes and military safety directives in the coming months, and for congressional debate over funding to accelerate air traffic modernization. Implementation of the NTSB’s recommendations, whether through FAA rulemaking, Army procedural changes, or new funding for surveillance and staffing, will determine whether the systemic vulnerabilities identified are corrected.

Sources

• The New York Times — news report summarizing the NTSB meeting and findings
• National Transportation Safety Board — official agency investigating the collision
• Federal Aviation Administration — federal aviation regulator, official statements and response
• U.S. Army — military service operating the Black Hawk helicopters