Washington Reagan mid-air collision (2025): visual separation, helicopter route design, and what pilots can learn

Approach changed late. Flight 5342 arrived from Wichita and was initially on visual approach to runway 1. At 20:43:06 EST, the tower asked whether the crew could accept runway 33; at 20:43:39 it instructed them to circle to runway 33 at the Wilson Bridge and cleared the airplane to land. The CRJ crew disconnected the autopilot and continued the circling approach.

The helicopter entered the river route. PAT25, a US Army UH-60L from Davison Army Airfield, was flying a night annual standardization evaluation with NVGs. It transitioned from Route 1 to Route 4 and proceeded southbound along the Potomac.

First traffic call. At 20:46:02, tower advised PAT25 about a CRJ south of the Wilson Bridge. The NTSB found that the helicopter crew likely did not receive the word “circling” due to degraded radio reception, so their recording captured the traffic as a CRJ “for runway three three” instead.

“Traffic in sight” and visual separation. The instructor pilot on PAT25 replied that they had the traffic in sight and requested visual separation. The controller approved it. At that point the aircraft were still about 6.5 NM apart, in darkness, with several other aircraft approaching DCA from the south.

Converging close in. At 20:47:29, the CRJ was turning left onto final for runway 33. At 20:47:39, with a conflict alert audible, the controller asked the helicopter again if they had the CRJ in sight.

Blocked transmission. At 20:47:42, the controller transmitted, “PAT two five pass behind that C-R-J,” but one of the helicopter pilots keyed the microphone for 0.8 seconds and blocked the crucial first part of that instruction. Two seconds later, the instructor pilot again said they had an aircraft in sight and requested visual separation.

Collision. PAT25 continued southbound on Route 4 and the CRJ continued descending on final. The collision occurred over the Potomac at about 278 ft msl, about 2,500 ft from the runway 33 threshold.

Route too close: Route 4 passed very near the runway 33 approach path, with little vertical margin even when flown at the published route altitude. The earlier break in the chain was at system level: route design or procedural deconfliction.

Altitude margin illusion: Many Army pilots interviewed believed that staying at or below the published Route 4 maximum meant they would remain clear of runway 33 traffic. A pilot-level break was understanding that a charted route limit is not the same as guaranteed separation.

Incomplete traffic picture: The helicopter crew likely missed the word “circling” in the first traffic advisory, so their mental model of the CRJ’s path was wrong from the start. A break here was to query ATC immediately when any part of a traffic call is unclear.

Unconfirmed sighting: The NTSB found the instructor pilot reported “traffic in sight” without positively identifying the airplane. The obvious break in the chain was to avoid using that phrase until the exact aircraft is found, tracked, and understood.

Blocked instruction: The “pass behind” instruction was partly blocked by a simultaneous transmission from the helicopter. A break here was readback discipline and immediate clarification when a transmission is stepped on or incomplete.

Combined tower duties: The local controller was also covering helicopter control, with conflict alert audible and multiple other tasks competing for attention. A break at system level was staffing and position management matched to traffic complexity.

See-and-avoid limits: Both crews were working at night, against city lights, with little relative motion to help visual detection. A break in the chain was not to overestimate what visual scanning can do in that environment.

Positive identification first: “Traffic in sight” is not a guess, and it is not shorthand for “I think I know which one you mean.” In this accident, the NTSB found that the helicopter crew reported traffic in sight without positively identifying the correct airplane. In training, build the habit of confirming type, position, direction, and likely path before you accept visual separation.

See-and-avoid has hard limits: Night, bright city lights, several aircraft in the same sector, and little relative motion all work against visual acquisition. The NTSB found both crews were operating in conditions that made it difficult to see the other aircraft, and the airline crew did not detect the helicopter until about 1 second before impact. That is a strong reminder that VMC does not equal easy traffic spotting.

If the call is unclear, ask: The missed word “circling” changed the helicopter crew’s expectation of where the CRJ would go. If part of a traffic advisory is unreadable, stepped on, or does not fit what you see outside, stop and clarify. A quick “say again traffic” can be a safety action, not a nuisance.

Read back the plan, not just the clearance: When ATC says “pass behind” or approves visual separation, your mental picture must match the controller’s. If it does not, say so. This case shows how a blocked transmission or partial readback can leave two sides of the frequency acting on different assumptions.

Altitude limits need margin discipline: The published Route 4 maximum was not generous, and the NTSB found the helicopter was above that limit. In light-aircraft flying, the lesson is broader: a published altitude, route, or circuit pattern only works if you fly it accurately and understand the tolerance in the instruments you are using.

Procedures do not remove pilot responsibility: Several helicopter pilots interviewed by the NTSB assumed the route altitude and ATC structure would keep them clear. A student pilot should learn the opposite habit: even when a route, clearance, or controller involvement suggests order, you still need to challenge assumptions and verify what is actually happening around you.