American Airlines plane, Black Hawk helicopter collide near Washington DC (ATC AUDIO)

For most of the descent into Reagan National, nothing about American Eagle Flight 5342 stood out. It was a regional jet on a route flown dozens of times a day, closing in on one of the most congested pieces of airspace in the country. Then, half a mile short of the runway, it wasn't.

At 8:48 p.m. on 29 January 2025, the jet collided with a US Army Black Hawk helicopter over the Potomac River, and both aircraft went into the water. There were no survivors.

What happened

Flight 5342, operated by PSA Airlines and flown under the American Eagle brand for American Airlines, had come in from Wichita, Kansas, with two pilots, two flight attendants and 60 passengers aboard. On final approach to Runway 33, it collided with a Sikorsky UH-60L Black Hawk flying under the callsign PAT25, a US Army training flight out of Fort Belvoir carrying three soldiers. Both aircraft went down roughly half a mile southeast of the airport. All 67 people aboard the two aircraft were killed, making it the deadliest US aviation accident in more than two decades. Divers and Coast Guard crews worked the river through the following days to recover the wreckage.

Airspace built for a different era

Reagan National sits inside one of the most tightly managed pieces of sky in the country, and it always has. Its runways sit close to the Potomac, close to restricted airspace around the capital, and close to a web of low-altitude helicopter corridors used for medevac flights, law enforcement, and military transport between bases in the area. Aircraft on approach and helicopters following the river have shared that airspace for decades, kept apart mostly by altitude and by the assumption that everyone involved could see everyone else in time.

The final ninety seconds

About five minutes before the collision, the tower switched Flight 5342 from a longer runway to the shorter Runway 33, a change controllers at Reagan National make routinely to manage traffic flow. This time it shifted the jet's final approach path directly across the helicopter's corridor. The switch itself was not unusual. The Black Hawk crew, midway through a training flight and following their assigned route, had no reason to expect that corridor would suddenly cross an active landing path in its final minute.

At 8:47, the tower asked the helicopter crew if they had the jet in sight and instructed them to pass behind it. The recordings later reviewed by investigators showed some uncertainty in how that instruction was understood. At the time, the exchange sounded routine enough that nobody treated it as urgent. A minute later, the two aircraft occupied the same point in the sky.

The route nobody closed

A year later, the National Transportation Safety Board released its final report, running to nearly 400 pages, and it did not settle on one cause. It described a stack of failures that each, on its own, might not have mattered.

The first was the route itself. The Black Hawk was flying a published helicopter corridor that ran directly beneath the approach path to Runway 33, separated from landing traffic by an altitude ceiling and little else. By the board's count, the FAA had logged more than 80 reports of close calls between helicopters and airliners in that same corridor in the years before the crash. The data was sitting inside the agency's own systems. Nobody had reviewed it, and nobody had moved the route.

Two people who didn't know how high they were

The second failure sat inside the helicopter. Investigators found the Black Hawk crew had never been trained on a known limitation of their aircraft's altimeter, and flew above the corridor's altitude ceiling that night without realizing it. A margin of error most crews would assume was covered in training simply hadn't been taught to them. Neither pilot had reason to think they were anywhere they shouldn't have been.

The tower that lost its second set of eyes

The third failure was in the tower. Two controller positions that would normally be staffed separately had been combined that evening, with no formal process for deciding when combining them was safe. The result, the NTSB found, was degraded performance: inadequate traffic advisories, and no safety alert issued to either aircraft before the collision.

The crew of Flight 5342 never saw the helicopter in time to react. The board's findings point to workload, high on a short final approach, and to something more basic: a helicopter closing head-on against a lit city background can appear almost motionless, the same collision geometry that has caught pilots for as long as aircraft have shared sky. NTSB chair Jennifer Homendy said afterward that the crash reflected systemic flaws rather than one crew's mistake, and that it had been entirely preventable.

What the report changed

In the weeks after the crash, the FAA permanently restricted non-essential helicopter operations along the stretch of river closest to the runway, closing the exact gap the NTSB would spend the next year formally documenting. The board's hearing that summer added new detail on the helicopter crew's final minutes, drawn from cockpit recordings and instructor communications, and the final report added dozens of recommendations covering route design, controller staffing levels, and altimeter training across both the military and civilian sides of the investigation.

For the families of the 67 people who died — among them Flight 5342's Captain Jonathan Campos, First Officer Samuel Lilley, and flight attendants Danasia Elder and Ian Epstein, alongside the Black Hawk's three-soldier crew — the report closed the question of how. It left open a harder one: why it took a collision to fix a route the FAA's own data had been warning about for years.