NTSB: Controller-Helicopter Miscommunication Caused DCA Near-Miss

On May 1st, an Army UH-60 Blackhawk helicopter and a commercial airliner came within a fraction of a mile of each other in the skies above Washington, D.C. The helicopter, flying under the call sign Priority Air Transport 23, was descending toward the Pentagon. A Republic Airways Embraer 170, flight 5825, was on its final approach into Reagan National Airport. At their closest point, the two aircraft were separated by just 0.4 miles horizontally and 200 feet vertically—a margin that, in aviation terms, is measured in seconds of reaction time.

The National Transportation Safety Board released its preliminary findings this week, and the culprit was neither mechanical failure nor weather. It was a breakdown in the most fundamental requirement of aviation safety: one controller telling another controller what is happening in their airspace. The DCA tower controller never instructed the Blackhawk crew to switch frequencies and contact the Pentagon's air traffic control. This omission set off a chain of confusion. When the Pentagon controller saw the helicopter on radar, he asked the crew who had cleared them to land. The helicopter pilot, uncertain of his clearance status, reported "landing assured"—a statement that would prove misleading, because moments later the aircraft was observed climbing back above the Pentagon building and beginning a second orbit around it.

Robert Katz, a commercial pilot and flight instructor with 43 years in the cockpit, reviewed the NTSB report and found something troubling in every layer. Both the DCA controller and the helicopter pilot, he said, were operating outside established procedures. The controller should have made a handoff. The pilot should have sought explicit clearance before attempting to land. But what struck Katz most was the geography of the mistake. The helicopter, circling east of the Pentagon, had positioned itself directly in the approach corridor for Reagan National. An airliner descending toward the runway was losing altitude at a steady rate, potentially passing through the same airspace the helicopter occupied.

The question Katz posed was simple but unsettling: why was the helicopter circling east of the Pentagon at all? Flying that route brought it closer to the DCA approach path than necessary. The Blackhawk was operating at or below 200 feet. The Republic Airways flight was descending through 200 feet. The horizontal separation of 0.4 miles meant they were close enough that a slight deviation by either aircraft could have turned a near-miss into a collision.

This incident arrives with particular weight because the same Army helicopter unit—Priority Air Transport—was involved in a catastrophic mid-air collision over the Potomac River on January 29, 2025, that killed 67 people. That disaster prompted a national conversation about how military and civilian air traffic are coordinated in one of the nation's most congested airspace. The May 1st near-miss suggests that conversation has not yet yielded systemic change. The NTSB report documents not a single point of failure but a cascade of procedural violations and communication gaps, each one manageable in isolation, but together creating the conditions for tragedy. What happens next—whether controllers and pilots adjust their practices, whether the Pentagon and DCA coordinate more tightly, whether the Army's helicopter operations are restructured—will determine whether this near-miss becomes a warning heeded or a prologue.