Marine One's takeoff warnings went unheard by controllers before near-miss

The warning was transmitted. The tower did not receive it.
Tower recordings revealed controllers never heard Marine One's required takeoff warning on August 4th, despite the helicopter making the call.
Mark

So the helicopter made the warning call, but the tower didn't hear it. How is that possible if they're talking on the same radio frequency?

Mimi

The problem was physical. The radio receiver that picks up transmissions from Marine One was positioned in a neighborhood near the airport, but the helicopter had moved to a new takeoff location at the Ellipse because of construction. The signal couldn't reach the receiver from that new spot.

Luke

Wait—so this wasn't a radio failure or a pilot error. It was a known problem that nobody solved before the helicopter started flying from a different location?

Mimi

Exactly. Controllers and pilots met a week before to discuss it. They knew the three-minute warning wasn't getting through. They tried to set up an alternate relay through Joint Base Anacostia-Bolling, but that didn't work either.

Mark

And then on August 4th, the pilot made the call anyway, even though nobody was hearing it?

Mimi

Yes. The pilot transmitted the standard three-minute warning. The tower had no record of it. A few minutes later, a commercial jet took off on a conflicting route, and the two aircraft came within 700 feet of each other vertically.

Luke

But they didn't collide. The Marine One pilots saw the plane and paused. So how close is "close" in this context?

Mimi

Close enough that the jet's collision avoidance system triggered a warning. The crew never saw the helicopter. But Marine One's pilots saw the plane and stopped their departure until it was clear.

Mark

This happened after a midair collision last year that killed 67 people. Didn't that crash lead to new safety procedures?

Mimi

It did. The FAA implemented a rule that all takeoffs and landings at Reagan would be halted when a helicopter is on a conflicting route. But that rule only works if controllers know the helicopter is about to take off.

Luke

So the new safety rule was in place, but the communication system it depends on was broken?

Mimi

Right. The system failed silently. There was no alarm, no obvious problem. The controller just didn't hear the warning.

Mark

What did the FAA do after they found out?

Mimi

They moved the radio receiver to the top of the Reagan tower, which fixed the line-of-sight problem. Tests showed it working properly after that. But it took a near-miss to expose the issue.

  • Marine One and an Envoy Air flight came within 0.8 miles and 700 feet of each other near one of the nation's most congested airspaces, close enough to trigger collision alarms aboard the commercial jet.
  • Air traffic controllers at Reagan tower were operating blind — the helicopter's required three-minute warning was transmitted but never received, leaving the people responsible for separation unaware a departure was imminent.
  • A known communication gap had already prompted a workaround meeting one week earlier, yet the backup relay plan through Joint Base Anacostia-Bolling also failed on the morning of the incident, compounding the breakdown.
  • Marine One's pilots spotted the airliner themselves and paused their departure, preventing a collision through direct observation rather than the coordinated system that was supposed to make such moments unnecessary.
  • The FAA responded by physically relocating radio receivers to the top of Reagan tower, but the incident exposes a deeper pattern: critical safety infrastructure at this airport has repeatedly failed without anyone knowing until something nearly goes wrong.

Near the same airport where 67 people perished in a midair collision just months ago, a presidential helicopter and a commercial airliner drew dangerously close on August 4th — not because warnings went unspoken, but because the infrastructure meant to carry those warnings had quietly failed. Marine One's pilots transmitted the required alert; the tower never heard it. In the space between transmission and reception, a near-miss unfolded, revealing that the safety of those in the sky depends not only on human vigilance but on the silent reliability of the systems beneath it.

On the morning of August 4th, a presidential helicopter and a commercial airliner came within 0.8 miles laterally and 700 feet vertically of each other near Ronald Reagan Washington National Airport. No one was hurt — Marine One's pilots spotted the Envoy Air flight and paused their departure until it climbed safely past. But what federal investigators uncovered in the days that followed was more unsettling than the near-miss itself.

NTSB preliminary findings confirmed that air traffic controllers at Reagan never received Marine One's required three-minute takeoff warning. Separate recordings from aviation monitoring service ATC.com proved the helicopter's pilot had made the call. The warning was transmitted. The tower simply did not receive it. The failure traced back to a logistical shift in mid-July, when Marine One began launching from the Ellipse south of the White House due to construction on a new helipad. The new location created a line-of-sight problem with the radio receiver positioned in a nearby neighborhood, and the signal stopped reaching the tower reliably.

Controllers and Marine One pilots had met just one week before the incident to address the gap. They knew the warnings weren't getting through and agreed on a backup relay through Joint Base Anacostia-Bolling. That plan also failed on August 4th. When the helicopter lifted off, the controller sounded caught off guard, asking Marine One to confirm it was proceeding as briefed — then acknowledging, with no three-minute warning received, that it should continue.

The incident unfolded against a backdrop of institutional friction that had already proven fatal. Last January, an airliner and an Army Black Hawk collided near the same airport, killing 67 people. That crash revealed years of broken communication between the Pentagon and the FAA, including a dedicated military hotline that had been non-functional for more than three years without the FAA's knowledge. A new rule implemented after that collision — halting all Reagan takeoffs and landings when a helicopter crosses on a conflicting route — was in effect on August 4th. It could not work if controllers didn't know a departure was coming.

The FAA moved quickly after the incident, relocating the radio receiver to the top of Reagan tower to restore reliable line-of-sight contact with the Ellipse. Tests confirmed the fix worked. But the episode stands as a reminder that even the most carefully designed safety protocols are only as strong as the infrastructure carrying them — and that infrastructure, as this airport has now shown twice, can fail without a sound.

On August 4th, a presidential helicopter and a commercial airliner occupied the same patch of sky near Ronald Reagan Washington National Airport at nearly the same moment. The two aircraft came within 0.8 miles of each other laterally and 700 feet vertically before pilots saw the danger and adjusted course. No one was hurt. President Trump was aboard Marine One. But the incident exposed something more troubling than the near-miss itself: the people responsible for keeping them apart never heard the warning they were supposed to hear.

Federal investigators from the National Transportation Safety Board released their preliminary findings Thursday, and the core problem was stark. Tower recordings from Reagan showed that air traffic controllers never received Marine One's three-minute takeoff warning on that August morning. Yet separate recordings posted by ATC.com, an aviation monitoring service, captured the helicopter's pilot making exactly that call. The warning was transmitted. The tower did not receive it. This was not a matter of miscommunication or misunderstanding. It was a failure of the basic infrastructure meant to prevent exactly this kind of incident.

The breakdown had roots in recent logistics. Since mid-July, Marine One had been launching from the Ellipse, a park south of the White House, because construction was underway for a new helipad behind the residence. The helicopter's new takeoff location created a line-of-sight problem with the radio receiver that had been positioned in a neighborhood near the airport. When the helicopter moved, the signal no longer reached the tower reliably. Controllers at Reagan had no way to hear what Marine One was saying.

One week before the August 4th incident, controllers and Marine One pilots had met to address the communication gap. They knew the three-minute warning calls were not getting through. They agreed on a workaround: the helicopter would relay its warning through the facility at Joint Base Anacostia-Bolling instead. That alternative plan failed too. On the morning of August 4th, the pilot transmitted the standard call—"three minutes to life," in the language of the protocol—but the controller seemed unaware. When the helicopter lifted off moments later, the controller sounded surprised. "Uh, Marine One, you said, uh, you're proceeding as briefed?" he asked. The controller then acknowledged, "OK, no three minutes, roger, proceed as briefed."

Minutes later, an Envoy Air flight took off on a conflicting route. The crew received a collision avoidance warning from their onboard system immediately after liftoff, but they never saw the helicopter. Marine One's pilots, however, spotted the plane. They paused their departure and waited until the airliner climbed safely above them. The separation was close enough to trigger alarms. It was not close enough to cause a collision.

The incident occurred against a backdrop of longstanding friction between military and civilian air traffic operations in one of the nation's busiest and most congested airspaces. Last year, an airliner collided with an Army Black Hawk helicopter near the same airport, killing 67 people. That crash exposed years of poor communication between the Pentagon and the FAA tower at Reagan. During congressional testimony, it emerged that a dedicated hotline connecting the military to the tower had been broken for more than three years without the FAA even knowing.

After the January 2025 collision, the FAA implemented a new rule: all takeoffs and landings at Reagan would be halted whenever a helicopter passed through on a conflicting route. That rule was in effect on August 4th. It did not prevent the near-miss because the rule depends on controllers knowing when Marine One is about to depart. They did not know.

The FAA moved quickly after August 4th. Technicians relocated the radio receiver from its position in the neighborhood to the top of the Reagan tower itself, improving the line of sight to the Ellipse. Subsequent tests showed the radios working properly after the change. The White House issued a statement saying the president was never in danger and expressing confidence in Marine One's pilots and security personnel. The FAA said it had taken immediate action and reviewed procedures. But the incident stands as evidence that even with the highest-level protocols in place, the systems meant to protect the president depend on infrastructure that can fail silently—and on communication channels that must work the first time, every time.

Marine One flights are piloted by the finest aviators in the world, and the White House maintains the utmost confidence in these patriots and other security officials who are responsible for ensuring the President's safety.
— White House spokesman Kush Desai
OK, no three minutes, roger, proceed as briefed.
— Reagan tower controller, after Marine One took off without the controller having received the three-minute warning
Möchten Sie die ganze Geschichte? Das Original lesen bei CBS News ↗
Kontakt FAQ