On a clear January night in 2025, tragedy unfolded over the Potomac River near Ronald Reagan Washington National Airport. PSA Airlines Flight 5342, a Bombardier CRJ700 inbound from Wichita, collided midair with a U.S. Army Sikorsky UH-60L helicopter, callsign PAT25. All 67 people aboard both aircraft perished. What happened was not a mystery of weather, mechanical failure, or sabotage. It was a failure of coordination, communication, and vigilance – failures that violated nearly every principle of High Reliability Organization (HRO) thinking.

High Reliability Organizations, such as aviation systems, military operations, and healthcare, must consistently operate in complex, high-risk environments without catastrophic failure. They do so by embedding five core principles: preoccupation with failure, reluctance to simplify, sensitivity to operations, commitment to resilience, and deference to expertise. In this case, those principles were compromised at nearly every level, from the flight deck to the control tower to interagency systems.

Preoccupation with Failure? Ignored History
This was not the first time helicopters and commercial aircraft had come dangerously close in Washington’s complex airspace. FAA records show more than 15,000 near-miss events between helicopters and airplanes around DCA from 2021 to 2024 – yet those signals were not treated as the leading indicators they were. One TCAS resolution advisory per month near the Potomac was not rare noise; it was a warning. High reliability systems treat near-misses as goldmines of learning. Here, the system treated them as routine.

Reluctance to Simplify? Oversimplified Complexity
Despite the known complexity of night helicopter navigation through tight urban corridors, the ATC protocols assumed flawless adherence to published routes. PAT25 was conducting a night vision goggle training flight – an inherently high-risk operation – yet was routed through Helicopter Route 1, a path with a maximum allowable altitude of just 200 feet through densely trafficked and visually disorienting terrain. That narrow procedural prescription left no room for operational nuance or real-time spatial conflict resolution.

Worse, the communication structure – two aircraft on different radio frequencies, with no direct ability to hear each other’s transmissions – created a blind spot in situational awareness. Even as both flight crews believed they had “visual separation,” they were unknowingly converging. That’s not operational safety – that’s coincidence dressed as coordination.

Sensitivity to Operations? Blunted by Frequency and Workload
The DCA control tower was in a “North Operation” configuration, handling landings and departures on both runway 1 and runway 33, a setup that demands maximum vigilance. Yet the helicopter and local control positions had been combined hours earlier, increasing cognitive load on a single controller handling dissimilar aircraft on intersecting paths.

As the tower issued clearances, its calls were occasionally stepped on or partially lost due to overlapping transmissions. Critical words, like “circling” and “pass behind,” were likely never received by the helicopter crew. Controllers, pilots, and automation each had a sliver of the picture, but no one had the full frame. In a high reliability system, those mismatches are unacceptable.

Commitment to Resilience? Fragile at the Seams
In the final seconds, PSA 5342’s TCAS system issued a “Traffic, Traffic” advisory. But below 400 feet, aural warnings are suppressed by design. It’s a tradeoff prioritizing noise reduction over last-ditch situational cues. The helicopter, meanwhile, lacked TCAS altogether.

While redundancy is a cornerstone of resilience, here both systems failed to reinforce one another. The last viable opportunity for either crew to correct course disappeared into a patchwork of partial data, broken phrases, and equipment design limitations.

Deference to Expertise? Not in Practice
The U.S. Army instructor pilot initially flying PAT25 yielded the controls mid-flight to the less experienced pilot, without clear handoff or confirmation of critical altitude deviations. Despite conflicting readouts – one pilot calling 300 ft, the other 400 ft – no meaningful cross-check followed. This reflects not just a lapse in cockpit discipline, but a failure of hierarchical deference: the senior pilot failed to assert operational authority when confusion mounted.

In the tower, the controllers issued clearances to other jets seconds before the fatal collision, suggesting no one had taken tactical ownership of the emerging threat.

Where Do We Go from Here?
This was not just a tragic accident. It was a predictable – and preventable – failure of high reliability culture. A few critical calls to action:

Integrate Airspace Management: Civil and military aircraft sharing the same congested airspace must have unified, interoperable communications protocols. Segregated frequencies must go.

Equip All Aircraft with TCAS: The military exemption from collision avoidance systems in shared civilian corridors is untenable. Situational awareness must be a baseline requirement.

Reexamine ATC Staffing and Sectorization: Controllers should never be asked to juggle dissimilar air traffic without support. Split high-workload positions, especially during complex night ops.

Reinforce the Value of Near Misses: The FAA and DoD must reframe near-miss reports not as statistical anomalies but as strategic warnings requiring root cause review.

Revise Training for High-Risk Missions: NVG training near major commercial corridors demands simulation or controlled environments, not real-time threading of commercial routes.

This catastrophe should galvanize reform. In systems built for zero-failure tolerance, the margin for error is razor-thin. To honor the lives lost, we must do more than investigate. We must rebuild our aviation culture with the urgency, humility, and systems-thinking that high reliability demands.