The Washington Midair, the Follow-Up Report, and the Safety Gaps That Still Have Not Been Closed

Nearly two years after the January 2025 Reagan National midair that killed 67, the core safety gaps - ATC staffing, military TCAS, and the Potomac River Exclusion - remain unresolved.

Aviation News Analyst

On January 29, 2025, American Eagle Flight 5342 and a U.S. Army UH-60 Black Hawk collided over the Potomac River near Reagan National Airport, killing all 67 people aboard both aircraft. It was the deadliest aviation accident on U.S. soil in more than two decades. Progress reporting from AeroTime Hub and other outlets now indicates that the systemic failures behind the collision have not been fully corrected - and that the operational urgency following the crash is fading before permanent fixes are in place.

What Happened on January 29, 2025

American Eagle Flight 5342 was a Bombardier CRJ-700 on final approach for Runway 33, inbound from Wichita with 60 passengers and 4 crew. The aircraft was on a standard river approach - routine traffic at a perpetually busy airport.

A U.S. Army Sikorsky UH-60 Black Hawk with three soldiers aboard was operating in the same airspace on a night currency training flight out of Davison Army Airfield. The two aircraft collided over the Potomac. There were no survivors.

The investigation remains open. The NTSB has not yet published its final probable cause report, which typically takes well over a year for a complex multi-vehicle accident. But preliminary findings have already identified the specific gaps that made this collision possible - and the concern is that those gaps remain.

The ATC Staffing Problem at Reagan National

On the night of January 29, a single controller was handling two radar positions simultaneously at Reagan National. This is called a combined position. It is legal. It is common. And it is precisely the problem.

The National Air Traffic Controllers Association (NATCA) has flagged combined position operations as a workload and safety concern for years. The practice is typically associated with lower-traffic periods when a facility cannot staff each position separately - but Reagan National is not a low-complexity facility.

DCA handles some of the most demanding traffic flows in the country: the river approach corridor, the proximity to restricted airspace over the Capitol and the White House, and a constant mix of commercial jets, general aviation, and military operations compressed into a tight geographic box with limited altitude separation. A single controller managing two frequencies simultaneously in that environment creates conditions where a momentary lapse in attention to any one aircraft can close the window the system depends on.

The controller on duty that night was doing a legal, common operation. That is exactly the problem. The system allowed it.

The FAA has publicly acknowledged a shortfall in certified controllers at complex facilities. Full staffing is a multi-year effort - the training pipeline cannot be fast-tracked without compromising the certification standards that make it meaningful. At high-complexity, high-volume facilities, the gap between current certified controller headcount and target staffing has at times been in the double digits. Combined positions, as a result, are not exceptional. They are a daily operational reality at understaffed facilities.

The Potomac River Exclusion and the Altitude Gap

Reagan National sits inside the Washington Special Flight Rules Area, among the most tightly controlled airspace in the country. Within that area, a provision called the Potomac River Exclusion allows certain aircraft - primarily helicopters and small propeller aircraft - to fly along the river corridor under Visual Flight Rules without an IFR clearance. The provision has existed in various forms for decades, primarily to accommodate military, government, and media helicopter operations that cannot practically be run as full IFR operations for every short-hop transit.

The exclusion uses defined routing patterns, each with a required altitude. The Army Black Hawk that night was assigned Pattern Charlie, which requires flight at or below 200 feet above the river surface. That ceiling is not arbitrary. At that altitude, the geometry of the exclusion corridor works - commercial traffic on the Runway 33 final is at a different altitude, and the separation is what makes the exclusion viable.

Radar data indicates the helicopter was significantly higher than 200 feet when the collision occurred. Early analysis placed the aircraft closer to 300 feet. The crew was on a night training profile, managing training objectives and aircraft systems simultaneously in a visually demanding environment. How altitude control was being prioritized during that phase of the flight remains part of the active investigation.

That roughly 100-foot deviation is the gap that killed 67 people.

The Potomac corridor had generated documented near-miss events before the crash. Controllers had raised workload concerns at the facility. Aviation safety publications and advocacy organizations had specifically questioned the Potomac River Exclusion well before January 2025. The NTSB had, in prior reports involving helicopter operations near Class Bravo airports, flagged the need for better collision avoidance technology on rotary-wing aircraft. The warning signs were documented. They were noted. They were not acted on with the urgency the risk deserved.

Why the Military Helicopter Had No Collision Avoidance Technology

Traffic Alert and Collision Avoidance System (TCAS) is mandatory on commercial aircraft above a certain weight threshold. It alerts flight crews when another aircraft is on a collision course and directs them to maneuver. The American Eagle CRJ-700 had TCAS. The Army Black Hawk did not.

Military aircraft operate under a different regulatory framework. The FAA does not regulate military aviation the way it regulates civilian and commercial operations. The Department of Defense (DoD) sets its own airworthiness standards, and across the military helicopter fleet, TCAS installation has been constrained by cost, the weight and power limitations specific to rotary-wing aircraft, and the institutional separation between military and civilian airworthiness programs.

Would TCAS on the Black Hawk have prevented the collision? The geometry of a midair at night, at those closure rates, with the time available to react, is brutal. TCAS advisories require crew action to execute, and the seconds between detection and impact may not have been enough to change the outcome. But the question the safety community is asking is broader than that one night.

The fleet of military helicopters operating in Class Bravo and high-density civilian airspace without collision avoidance technology is large. DCA is not the only airport in the country where military rotary-wing operations bring aircraft into close proximity with commercial approaches. The report recommends the DoD accelerate TCAS installation - or a military equivalent - on rotary-wing aircraft operating in high-density civilian airspace, targeting specifically the aircraft using exclusion corridors where the geometric risk is highest.

How NTSB Recommendations Actually Move Through the System

The NTSB does not have enforcement authority. The agency investigates, analyzes, and issues recommendations. After an investigation, those recommendations go to the FAA, the DoD, airlines, and sometimes directly to Congress. What happens next depends on factors that have nothing to do with the quality of the analysis: budget cycles, agency priorities, competing legislative agendas, and the lobbying weight of various stakeholders.

The NTSB publishes a Most Wanted List of aviation safety improvements - high-priority items that have been identified but not yet implemented. Some entries on that list have been there for a very long time.

The concern expressed in the current follow-up reporting is that the specific gaps from January 29 are tracking toward that same pattern. Some interim measures were put in place. Some procedural adjustments were made. The operational urgency that followed the accident has begun to fade. And the permanent regulatory changes that would formalize the safety improvements are still pending.

What Has Changed - and What Has Not

Since the collision, operational adjustments to helicopter corridor usage near Reagan National were implemented. Some enhanced coordination requirements between military dispatchers and civilian ATC went into effect. The facility received staffing relief. The DoD acknowledged the TCAS recommendation and initiated a review of implementation timelines.

What has not happened: the Potomac River Exclusion has not been permanently restructured to require altitude alerting technology or independent verification. TCAS or an equivalent has not been mandated for military rotary-wing operations in Class Bravo airspace. The ATC staffing shortfall at high-density facilities has not been fully resolved. And the NTSB final probable cause report - which will carry the official weight of the investigation and formally put every recommendation on record - has not been issued.

Why This Is a System Problem, Not an Individual Failure

There is a tendency in post-accident coverage to focus on individual decisions: what the crew did or did not do, what the controller could have done differently. Human performance is always part of the analysis. But it is not the whole analysis, and treating it as such misses the larger lesson aviation safety investigation has taught, repeatedly, over decades.

The combined controller position is a system design decision. The absence of TCAS on military helicopters in Class Bravo is a system gap. The altitude ambiguity that allowed a training profile to put a helicopter 100 feet above its cleared altitude without an alert firing anywhere in the system is a known vulnerability that was not corrected.

Systems fail. The question is not whether humans will make errors - they will. The question is whether the system is designed to catch those errors before they become fatal. Placing accountability solely on individuals is not just unfair. It is analytically wrong, and it lets the system off the hook for the next time.

What This Means for Pilots Operating Near Reagan National

If you fly near DCA, or in any corridor where helicopter and commercial traffic share constrained airspace, the procedural knowledge is on you. Know the exclusions. Understand where the conflict geometry exists in your routing and altitude. Know what traffic is sharing that corridor and what technology - or absence of technology - the other aircraft is carrying.

That awareness does not substitute for the systemic fixes that still need to happen. But it is the protection layer that is entirely within your control right now.


Key Takeaways

  • The January 29, 2025 Reagan National midair killed 67 people - 64 aboard American Eagle Flight 5342 and 3 aboard a U.S. Army UH-60 Black Hawk - making it the deadliest U.S. aviation accident in over two decades.
  • A single controller managing two radar positions simultaneously was legal and routine; the conditions that enabled it are a staffing and system design problem, not an individual failure.
  • The Army helicopter was approximately 100 feet above its cleared Pattern Charlie altitude of 200 feet when the collision occurred; no alerting system flagged the deviation.
  • The military helicopter carried no TCAS; the DoD has acknowledged a recommendation to accelerate installation on rotary-wing aircraft in high-density civilian airspace but has not mandated it.
  • Nearly two years after the collision, the Potomac River Exclusion has not been permanently restructured, military TCAS has not been mandated, ATC staffing gaps persist, and the NTSB final probable cause report has not been issued.

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