FAA Chief Admits Agency Failures Led to Deadly Midair Crash Near DCA

Following a year-long investigation, Federal Aviation Administration (FAA) Administrator Bryan Bedford publicly acknowledged his agency’s role in the tragic midair collision that killed 67 people.

Speaking on February 3, 2026, Administrator Bedford stated that systemic failures within the FAA contributed to the disaster near Ronald Reagan Washington National Airport (DCA) on January 29, 2025. This rare admission of fault follows the release of the National Transportation Safety Board (NTSB) final report. The report detailed deep organizational issues that allowed the fatal accident to occur.

NTSB Finds Preventable Causes

The NTSB determined the accident was “100% preventable,” citing multiple causal factors that lay primarily with the FAA and the U.S. Army. The investigation focused on the collision between a commercial regional jet and a U.S. Army UH-60L Black Hawk helicopter. All 67 people aboard both aircraft died.

The core issue was the FAA’s decision to authorize helicopter flights too close to the airport. Specifically, the NTSB found the agency placed Helicopter Route 4 in close proximity to the final approach path for DCA’s Runway 33. The vertical separation between aircraft on the route and landing planes was found to be only 75 feet. This was deemed an unacceptable level of separation.

Failure to Act on Prior Warnings

Investigators highlighted a critical failure in the FAA's oversight. The agency failed to regularly review and evaluate helicopter routes and available data. Furthermore, the FAA failed to act on recommendations to mitigate the risk of a midair collision near DCA. The NTSB disclosed that a similar near-miss incident in 2013 had already prompted recommendations to relocate or remove Route 4. The FAA ultimately ignored these warnings from both the NTSB and local air traffic controllers.

Systemic Failures in Air Traffic Control

The NTSB report also pointed to systemic failures in air traffic control (ATC) practices. The air traffic system relied too heavily on the visual separation concept. This concept requires pilots to see and avoid other aircraft, which proved insufficient in this congested airspace.

• High Workload: The air traffic controller at DCA faced a loss of situational awareness. This was due to the high workload from combining helicopter and local control positions.
• Risk Assessment: The tower lacked a formal risk assessment process to identify real-time operational risks.
• Communication: The use of separate radio frequencies for helicopters and airplanes increased risk. This practice prevented critical instructions from being fully received.

Industry and Regulatory Impact

In response to the NTSB's urgent recommendations, the FAA immediately restricted helicopter flights from the airport. The agency later published an Interim Final Rule to restrict the use of Runways 15 and 33 when helicopters operate in the area. The NTSB issued 50 new safety recommendations, with most directed toward the FAA.

These recommendations call for comprehensive reforms. They include redesigning helicopter routes and improving controller training. They also focus on enhancing collision avoidance systems.

On the legislative front, the U.S. Senate passed the Rotorcraft Operations Transparency and Oversight Reform (ROTOR) Act. This bill aims to codify NTSB recommendations. It requires all aircraft, including military helicopters, to equip and receive ADS-B broadcasting signals. The ROTOR Act also mandates the FAA to comprehensively evaluate airspace safety around airports nationwide. This is intended to prevent similar risks found at DCA from existing elsewhere. The tragedy has spurred a major push for enhanced aviation safety standards across the National Airspace System.

flying.flights provides comprehensive commercial aviation news covering airlines, aircraft, and airports.

From aircraft production to supply chains, commercial aviation manufacturing news is covered at flying.flights/manufacturing.