Changeflow GovPing Transportation NTSB: Systemic Failures Led to Deadly Potomac R...
Urgent Enforcement Added Final

NTSB: Systemic Failures Led to Deadly Potomac River Midair Collision

Favicon for www.ntsb.gov NTSB Press Releases
Filed January 28th, 2026
Detected March 17th, 2026
Email

Summary

The NTSB has issued 74 findings and 50 recommendations following a year-long investigation into a deadly midair collision over the Potomac River. The report identifies systemic failures by the FAA and U.S. Army, leading to significant safety recommendations for airspace design, ATC procedures, and technology.

What changed

The National Transportation Safety Board (NTSB) has released its final report on the January 29, 2025, midair collision over the Potomac River, which resulted in 67 fatalities. The investigation identified systemic failures by the Federal Aviation Administration (FAA) and the U.S. Army, including inadequate helicopter route design, insufficient safety oversight, and a lack of effective risk management strategies. The NTSB has issued 74 findings and 50 recommendations aimed at preventing future accidents, focusing on improvements to airspace design, air traffic control procedures, safety management systems, data sharing, and collision avoidance technology.

Regulated entities, particularly those involved in aviation operations in congested airspace, should review the NTSB's findings and recommendations. While the NTSB's recommendations are non-binding, they often lead to regulatory changes by the FAA. Companies should proactively assess their safety management systems, data sharing practices, and collision avoidance capabilities, especially in light of the identified deficiencies in airspace design and oversight around major airports. The report highlights the critical need for robust procedural separation, clear guidance, and effective hazard identification and mitigation strategies to prevent similar tragedies.

What to do next

  1. Review NTSB findings and recommendations regarding airspace design and safety oversight.
  2. Assess current safety management systems for potential deficiencies identified in the report.
  3. Evaluate collision avoidance technology and data sharing practices for aviation operations.

Source document (simplified)

Systemic Failures Led to Midair Collision Over Potomac River in Washington

1/28/2026

NTSB recommendations call for changes to helicopter route design, air traffic control procedures, safety management systems, data sharing and collision avoidance technology

​WASHINGTON (January 28, 2026) — Systemic failures in airspace design, safety oversight, and risk management by the Federal Aviation Administration and the U.S. Army contributed to a midair collision a year ago over the Potomac River that killed 67, the National Transportation Safety Board said Tuesday in its final board meeting on the disaster, the nation’s deadliest aviation accident since November 2001.

The collision occurred at 8:48 p.m. Eastern time on January 29, 2025, when a U.S. Army Sikorsky UH-60L Black Hawk helicopter and American Airlines flight 5342, a Mitsubishi Heavy Industries RJ Aviation CRJ700 operated by PSA Airlines, collided over the river about a half mile southeast of Ronald Reagan Washington National Airport. All 64 people on the airplane and all three crewmembers on the helicopter died in the crash.

“This complex and comprehensive one-year investigation identified serious and long-standing safety gaps in the airspace over our nation’s capital,” said Jennifer Homendy, chairwoman of the NTSB. “Sadly, the conditions for this tragedy were in place long before the night of Jan. 29.”

Tuesday, the NTSB in a public meeting voted to approve 74 findings and 50 recommendations to prevent similar accidents in the future.

The investigation found that the FAA’s helicopter route design in the Washington area failed to provide procedural separation between helicopters and fixed-wing aircraft operating on approach and departure paths at Reagan National. Investigators concluded that the route structure allowed helicopters to fly directly beneath an active approach corridor for commercial airliners without sufficient mitigations to manage the risk of a collision.

The investigation also identified deficiencies in FAA guidance regarding helicopter route altitudes and boundaries. Inconsistent and unclear information led some helicopter operators to misinterpret published altitudes as providing separation from fixed-wing traffic, when no such separation existed. Additionally, aeronautical charts for fixed-wing pilots did not depict nearby helicopter routes that intersected approach paths, limiting shared situational awareness.

The NTSB said that the FAA lacked effective strategies to identify, assess, and reduce recurring midair collision hazards in the skies around Reagan National. Despite available safety data showing repeated close encounters between helicopters and airplanes near the airport, the FAA did not conduct sufficient safety analysis or take timely corrective action. The agency also did not act on recommendations from local air traffic control personnel and other helicopter operators who raised concerns about known conflict areas.

The U.S. Army’s safety management processes also failed to identify and address hazards associated with helicopter operations in congested and complicated civilian airspace. The NTSB found that the Army lacked a flight data monitoring program for helicopters operating near major airports and had limited participation in safety reporting systems. As a result, routine excursions above the authorized helicopter route altitudes and close proximity incidents that presented a risk of midair collision went unrecognized by Army safety personnel.

Investigators further determined that neither aircraft was equipped with collision avoidance technology capable of providing effective alerts in the low-altitude environment where the accident occurred. Although the CRJ700 airliner’s traffic alert and collision avoidance system functioned as designed, existing altitude limits prevented higher-level alerts called resolution advisories from being issued, which could have provided the airline flight crew with real-time maneuvering instructions to avoid the collision.

The NTSB found that had the airplane been equipped with an airborne collision avoidance system that used Automatic Dependent Surveillance–Broadcast In, the crew would have had enhanced position information about the helicopter. Such a system could have provided the crew of flight 5342 with the first alert regarding the helicopter 59 seconds before collision.

Air traffic control practices also contributed to the accident. The NTSB found that the high workload during a period of elevated traffic reduced air traffic control’s ability to monitor developing conflicts and provide timely safety alerts. The use of separate radio frequencies for helicopters and airplanes further increased risk, as blocked transmissions prevented critical instructions from being fully received.

As a result of the investigation, the NTSB issued 33 safety recommendations to the FAA, eight to the U.S. Army, and additional recommendations to the Department of Transportation, the Department of War Policy Board on Federal Aviation, and the RTCA (formerly known as the Radio Technical Commission for Aeronautics). These recommendations call for comprehensive reforms to helicopter route design, air traffic control procedures, safety management systems, data sharing, and collision avoidance technology.

“Our work doesn’t end with the issuance of a final report; that's just the first step,” Homendy said. “We will vigorously advocate for the implementation of our safety recommendations — that’s how we prevent a tragedy like this from happening again.”

The findings, probable cause, and safety recommendations, is available on the accident investigation webpage. Additional material, including the preliminary report, previously issued safety recommendations, news releases, the public docket, investigative updates, and links to photos and videos, are also available on that page. The final report will be published in the coming weeks on NTSB.gov.​

To report an incident/accident or if you are a public safety agency, please call 1-844-373-9922 or 202-314-6290 to speak to a Watch Officer at the NTSB Response Operations Center (ROC) in Washington, DC (24/7).

Source

Analysis generated by AI. Source diff and links are from the original.

Classification

Agency
NTSB
Filed
January 28th, 2026
Instrument
Enforcement
Legal weight
Non-binding
Stage
Final
Change scope
Substantive

Who this affects

Applies to
Government agencies Manufacturers
Geographic scope
National (US)

Taxonomy

Primary area
Transportation
Operational domain
Compliance
Topics
Aviation Safety Air Traffic Control Risk Management

Get Transportation alerts

Weekly digest. AI-summarized, no noise.

Free. Unsubscribe anytime.

Get alerts for this source

We'll email you when NTSB Press Releases publishes new changes.

Free. Unsubscribe anytime.