An internal U.S. Army investigation made public on October 8, 2026 revealed systemic military breakdowns behind the January 2025 midair collision near Reagan National Airport that killed 67 people. The report cited broken radio transmissions, uncalibrated Black Hawk altimeters, and disabled location-tracking systems as primary factors in the crash with an American Airlines jet. Families of victims are urging Congress to pass mandatory collision avoidance laws and demanding an independent audit into military leadership.
Overview of the Reagan Airport collision
- ▪A U.S. Army internal report made public on October 8, 2026 detailed systemic failures that led to the January 29, 2025 midair collision near Reagan National Airport that killed 67 people
- ▪The January 29, 2025 collision involved an American Airlines regional jet (Flight 5342) and an Army UH-60L Black Hawk helicopter, which both crashed into the Potomac River
Army findings on causes of the crash
- ▪Army investigators noted that the Black Hawk helicopter's barometric altimeter, used in the January 2025 collision, can misread altitude by up to 130 feet, whereas the designated route allowed only 75 feet of vertical separation
- ▪Army investigator Lt. Gen. Michael McCurry concluded that the key factor in the January 2025 Reagan Airport crash was two broken radio transmissions that prevented the Black Hawk helicopter crew from identifying the approaching American Airlines commercial jet
- ▪An Army report on the January 2025 Reagan National Airport collision identified contributing factors including pilot night-vision goggles limiting field of vision amid intense city lights, turbulence, and a pattern of helicopter crews failing to complete required flight hours
- ▪An Army report on the January 2025 Reagan National Airport collision found the Black Hawk helicopter's ADS-B Out location tracking system failed to transmit during the Flight 5342 collision due to an incorrect time Source Reference Code configuration
Army safety recommendations and corrective actions
- ▪The U.S. Army inspected and reconfigured all 3,585 affected helicopters by July 2025 after discovering location-broadcasting transponder errors on the Black Hawk involved in the January 2025 collision
- ▪An Army report on the January 2025 Reagan National Airport collision recommended upgraded night-vision technology and improved training for military pilots operating near commercial airports in Washington and Baltimore
- ▪An Army report on the January 2025 Reagan National Airport collision recommended requiring military aircraft to operate location broadcasting in the Washington area, expanding safety reviews to major cities worldwide, and seeking an FAA data-sharing agreement
Demands and criticism from victims' families
- ▪Victims' families criticized an Army report on the January 2025 Reagan National Airport collision for failing to assign individual leadership accountability and reiterated their call for an independent audit by the Army Inspector General
- ▪The Families of Flight 5342 group and commercial jet captain Tim Lilley called on Congress to pass legislation mandating collision avoidance technology across all aircraft
NTSB findings and evaluations
- ▪The NTSB faulted the Federal Aviation Administration for failing to implement roughly one-third of NTSB-recommended safety reforms and noted that civil-military coordination before the January 2025 Reagan Airport crash lacked discussion of near-misses
- ▪NTSB Chair Jennifer Homendy stated in an October 1, 2026 letter that the U.S. Army made significant progress on seven of eight safety recommendations but needs further work on risk detection
- ▪The NTSB investigation determined that the Black Hawk helicopter was flying nearly 100 feet higher than its altimeter indicated during the fatal approach
Debatable claims
- ▪Broken radio communications were the primary cause of the Reagan Airport collision
- ▪Congress must pass legislation mandating collision avoidance technology on all aircraft
- ▪Systemic military safety reviews are insufficient without individual leadership accountability
Story comments
Loading comments…