The DCA midair collision: what the NTSB found and what has changed since

On the night of January 29, 2025, PSA Airlines flight 5342, a CRJ700 flown for American Airlines from Wichita, collided with an Army UH-60L Black Hawk, callsign PAT25, about half a mile southeast of Ronald Reagan Washington National Airport (DCA). All 64 people on the airplane and the 3 soldiers on the helicopter died.

The NTSB adopted its final report in January 2026. This article covers what the Board found, what has changed since, and what it means for crews flying into busy airports with helicopters nearby.

What happened

According to the final report, flight 5342 was inbound from the south for a visual approach to runway 1 when the tower asked whether the crew could take runway 33. The crew checked landing performance, accepted, and circled to runway 33.

PAT25 was flying the pilot's annual standardization evaluation, with the crew on night vision goggles. The controller, working the local and helicopter positions combined, had cleared it down helicopter Routes 1 and 4 along the Potomac. When the controller called the airplane to the helicopter, it was about 6.5 nm south, one set of lights among several airplanes lined up for runway 1. The instructor pilot reported it in sight and asked for visual separation, which was approved.

About 20 seconds before impact, the controller asked PAT25 whether it had the airplane in sight and told it to pass behind. One of the helicopter pilots keyed the microphone for 0.8 seconds during that call, and the "pass behind" portion never reached the crew. The instructor pilot again reported the traffic in sight. The two aircraft collided over the river at about 278 ft msl. The report found that the airplane crew detected the helicopter only about 1 second before impact.

Preliminary findings and the urgent fix

The NTSB released its preliminary report on March 11, 2025, with an urgent safety recommendation report. Preliminary reports assign no cause, but the geometry was already clear. A helicopter at Route 4's 200 ft maximum altitude over the eastern shoreline of the Potomac would have about 75 ft of vertical separation from an airplane approaching runway 33, and less if the helicopter was farther from shore or the airplane was below the PAPI glidepath.

The same report cited FAA data: between October 2021 and December 2024, in 944,179 commercial IFR operations at DCA, there were 15,214 occasions when a commercial airplane and a helicopter were within 1 nm laterally and 400 ft vertically, and 85 within 1,500 ft and 200 ft. Reports and FAA data from 2011 to 2024 showed at least one TCAS RA per month caused by a helicopter, two-thirds of the events at night.

The NTSB asked the FAA to prohibit Route 4 operations between Hains Point and the Wilson Bridge when runways 15 and 33 are in use (A-25-1), and to designate an alternative route (A-25-2). Three days later the FAA removed that segment of Route 4 from the charts and barred runways 15/33 and 4/22 during certain helicopter operations. The NTSB later classified the response as exceeding what it had asked for.

The final report

The Board met on January 27, 2026, and adopted report AIR-26-02. It determined that the probable cause was "the FAA's placement of a helicopter route in close proximity to a runway approach path," the FAA's failure to review routes and act on recommendations and data, and "the air traffic system's overreliance on visual separation." Three more causal factors followed. The first was the helicopter crew's visual separation: degraded radio reception kept the crew from hearing that the airplane was circling to runway 33, and with several points of light ahead, the instructor pilot "likely identified the wrong target." The second was the tower, where high workload on the combined helicopter and local control positions, with no real-time risk assessment, led to misprioritized duties, inadequate traffic advisories and no safety alerts to either crew. The third was the altimeter. The Army had not made its pilots aware of how allowable barometric altimeter tolerances add up, and the NTSB found the crew likely saw an altitude about 100 ft lower than the true one, which put the helicopter above the route's maximum altitude.

Contributing factors included the limits of the traffic alerting systems on both aircraft; an arrival rate the Board called unsustainable (36 per hour that night), along with airline scheduling and a changing fleet mix; the Army's incomplete safety management system; the FAA's failure to act on earlier NTSB recommendations, including ADS-B In; and poor data sharing.

The NTSB found the airline pilots qualified, not fatigued, and flying a properly equipped airplane. It concluded they did not see the helicopter in time because of the high workload of the final phase of the approach and the helicopter's "low conspicuity and lack of apparent motion."

The helicopter's transponder was switched on but, because of installation settings, was not broadcasting ADS-B Out. The airplane had no ADS-B In, so the broadcast alone would not have helped its crew. Its TCAS worked as designed, but the airplane was too low for resolution advisories. The crew got a traffic advisory 19 seconds before impact; a simulated ADS-B In display would have alerted them at 59 seconds. In MIT Lincoln Laboratory simulations of the encounter, ACAS Xa with RAs allowed down to 300 ft cut the risk of a near midair collision by more than 90%.

The Board issued 50 new recommendations: 33 to the FAA, 8 to the Army, 5 to the Pentagon's Policy Board on Federal Aviation, 3 to DOT and its inspector general, and 1 to RTCA. Those that most affect airline crews ask the FAA to:

• Require ADS-B In with a traffic display and audible alerts wherever ADS-B Out is required (A-26-31).
• Require ACAS X on new aircraft and retrofit it on aircraft that must carry TCAS, and evaluate lowering its alerting altitudes (A-26-32 to -35).
• Add clock position, range, relative altitude and vertical trend to aural traffic alerts, and directional traffic symbols to displays (A-26-29, -30).
• Show helicopter routes on instrument and visual approach and departure procedures (A-26-28).
• Implement anti-blocking technology that alerts controllers or crews when simultaneous transmissions block each other (A-26-19).

What has changed since

Sources: FAA statements, the FAA's timeline of actions, its March 2026 announcement, the NTSB report and the Federal Register.

At DCA itself, the interim final rule allows helicopters and powered-lift between the Memorial Bridge, Hains Point and the Wilson Bridge only for essential operations, such as lifesaving medical, law enforcement, national security, or transport of the President or Vice President. Training and proficiency flights do not qualify. When an essential flight enters the area, ATC keeps fixed-wing traffic out, which can mean restricting runways 15/33 or 4/22. The FAA writes that such flights "should be exceedingly rare."

Nationwide, GENOT N JO 7110.801, effective March 18, 2026, amends paragraph 7-2-1 of FAA Order JO 7110.65: visual separation may no longer be used between a helicopter or powered-lift aircraft crossing the path of arriving or departing aircraft in Class B, Class C or TRSA airspace. The GENOT is interim and cancels on December 24, 2026. In May 2026, the FAA said it was still evaluating the other recommendations, some of which would need rulemaking or new technical standards.

In the tower, the NTSB report lists 28 authorized and 28 assigned controllers at DCA at the time of the accident, 25 of them operational. In January 2026 the FAA said DCA was authorized 30, with 22 working, 8 in training and 4 on temporary assignment from other facilities. The FAA cut the arrival rate from 36 to 26 after the accident and later raised it to 30.

Legislation: still not law

Two bills would put many of the recommendations into law. As of late September 2026, neither has been enacted.

The ROTOR Act (S. 2503) passed the Senate by unanimous consent on December 17, 2025. It would require aircraft to carry ADS-B In and would strike section 373(a) of the fiscal 2026 defense authorization act, which, according to the Senate Commerce Committee, would have exempted military helicopters from broadcasting their position in Washington airspace. On February 24, 2026, the House voted on it under suspension of the rules. The tally was 264 to 133, one vote short of the two-thirds needed. AAAE reported that House committee leaders preferred their own bill and that the Defense and Transportation departments objected late.

The ALERT Act (H.R. 7613) passed the House on April 14, 2026, by 396 to 10. It would require ADS-B In with collision prevention technology by December 31, 2031, on almost all aircraft that must carry ADS-B Out. The committee summary of its defense title would make ADS-B Out the default for military helicopters and require each service to verify its ADS-B Out transponders at least every 90 days. The bill has sat in Senate Commerce since April 15.

On September 15, victims' families stood with lawmakers at the Capitol to press for a final bill. NTSB Chair Jennifer Homendy, who spoke there, said the Board had judged the FAA's responses to a third of its 33 recommendations to the agency "unacceptable." Advocates told Gray News they would push again in the lame-duck session after the November elections.

What it means for line pilots

Your company procedures and AFM come first. These points come from the report's findings.

• "Traffic in sight" has to mean the right traffic. The NTSB found the instructor pilot likely picked the wrong light. At night over a city, a helicopter may be one point of light with no apparent motion. If you are not certain, say "looking." A light that holds still on your windscreen is likely on a collision course.
• Expect less visual separation with helicopters. Under the GENOT, controllers must use radar standards between you and a helicopter crossing your arrival or departure path in Class B, Class C and TRSA airspace. Expect more helicopter holds and reroutes, and occasional runway restrictions when medical or police flights get priority.
• Know where the helicopter routes are. The NTSB found fixed-wing charts did not show helicopter routes that could cross DCA's approach and departure paths. Until procedures show them, look at the VFR helicopter route charts for the airports you fly to.
• A late runway change costs attention. The report found that offloading arrivals to runway 33 was a routine way to create spacing at DCA, and that the workload of that final segment was one reason the crew did not see the helicopter. It is fine to take time, or to say unable.
• Know your TCAS limits. The report notes that TCAS II inhibits RAs below 900 ft AGL on descent and silences the aural TA below 400 ft AGL. Flight 5342 got a TA 19 seconds before impact and no RA. Check the numbers for your airplane.
• You may not hear the helicopter. At DCA, helicopters and airplanes were on different frequencies, and a 0.8-second transmission blocked a critical instruction. If a call is stepped on or garbled, ask for it again.
• Report close calls. The Board found the warning signs were in FAA data for years. ASAP, ASRS and TCAS event reports are part of that data.

The 67 people who died that night deserve a system that does not depend on spotting a helicopter's lights against a city. The procedures have changed. The equipment the NTSB called for is still ahead.

Sources

1. Midair Collision over the Potomac River, PSA Airlines Flight 5342 and US Army Priority Air Transport Flight 25, Aviation Investigation Report AIR-26-02, NTSB, January 27, 2026 (reissued February 25, 2026)
2. Deconflict Airplane and Helicopter Traffic in the Vicinity of Ronald Reagan Washington National Airport, Aviation Investigation Report AIR-25-01, NTSB, March 7, 2025 (released March 11, 2025)
3. NTSB Makes Urgent Recommendations on Helicopter Traffic Near Reagan National Airport, NTSB, March 11, 2025
4. Investigation DCA25MA108, NTSB
5. Media Advisory: NTSB Board Meeting on Midair Collision at DCA Scheduled for Jan. 27, NTSB, January 2026
6. FAA Statements on Midair Collision at Reagan Washington National Airport, FAA (updated May 19, 2026)
7. Timeline of Actions Since DCA Midair, FAA, 2026
8. Flight Restrictions in the Vicinity of Ronald Reagan Washington National Airport (DCA), Interim final rule, Federal Register, 91 FR 2840, January 23, 2026
9. Trump's Transportation Secretary Sean P. Duffy and Federal Aviation Administration Announce New Measure to Enhance Safety between Airplanes and Helicopters, FAA, March 18, 2026
10. GENOT N JO 7110.801, Interim Helicopter Separation Procedures, FAA, March 18, 2026
11. Chairman Cruz: Senate Passage of ROTOR Act a Key Step for Aviation Safety, Senate Commerce Committee, December 17, 2025
12. S. 2503, ROTOR Act, All Actions, Congress.gov
13. ROTOR Act Fails in House; Committee Action on ALERT Act Could Come as Soon as Next Week, AAAE, February 24, 2026
14. House Votes Down ROTOR Act, Flying, February 24, 2026
15. House Overwhelmingly Approves ALERT Act to Provide Comprehensive Safety Response to Tragic DCA Crash, House Transportation and Infrastructure Committee, April 14, 2026
16. H.R. 7613, ALERT Act, Title II Section-by-Section, House Armed Services Committee
17. H.R. 7613, ALERT Act, All Actions, Congress.gov
18. Families of victims killed in midair collision over Potomac make emotional appeal to Congress, WTOP, September 15, 2026
19. Families push Congress to pass ROTOR Act after deadly crash, Gray News via WBNG, September 15, 2026