Trump Jet’s Radio Blackout Mystery

One week after controllers warned that radios were “spotty,” Marine One’s calls went unheard as a passenger jet lifted off nearby with President Trump onboard.

Story Snapshot

Investigators say both sides knew of weak radio links days before the incident.
Marine One’s first call was not received; a second was unreadable, per the report.
Technicians later found a line-of-sight blind spot tied to the temporary Ellipse site.
The Federal Aviation Administration called it a “momentary loss of separation,” not a collision.

What Investigators Say Happened

The National Transportation Safety Board’s preliminary report says Marine One and Reagan National controllers met on July 30 about weak radio links and agreed on backup contact steps. On the incident day, Marine One twice tried to alert the tower before departure. The first call was not received at all, and the second was broken and unreadable, according to the same reporting. The normal three-minute warning did not reach the tower clearly, which set up the loss of separation that followed.

The Federal Aviation Administration described the event as a “momentary loss of separation,” and said the aircraft then moved apart. That framing confirms a safety lapse but not a near-collision. Officials also said the tower frequency itself had no known outage. That means the problem sat in how Marine One’s transmissions reached the tower from its temporary launch point, not in a dead radio channel for everyone that day.

Why The Ellipse Move Mattered

Marine One launched from a temporary site on the Ellipse because of White House construction. Federal Aviation Administration technicians later ran coverage tests. They found the tower’s transmitter and receiver did not have a clean line-of-sight to the Ellipse location, which can block or weaken radio signals. Reports tied that blind spot to the unreadable calls. In plain terms, the system worked on paper, but the geometry of buildings and antennas failed the users that morning.

Investigators and reporters linked the failed warning to that same line-of-sight gap. The chain looks simple but is common in safety cases: a temporary change, a known weak point, and a backup plan that did not hold up under real pressure. That is why the meeting one week earlier matters. People on both teams saw the risk, talked about it, and tried to set a fallback. Yet when it counted, those steps did not bridge the gap, and an airliner rolled anyway.

What Changed After, And What Still Is Not Known

Federal leaders said fixes are underway. Reports say antennas were moved and procedures adjusted to prevent a repeat near Reagan National Airport. Transportation Secretary Sean Duffy called it a telecommunications issue between teams and said they were working on it. The Federal Aviation Administration chief said he was confident the issue was resolved after changes, according to coverage from the field. Those steps match the findings on signal coverage and sight lines.

Key Highlights

Communication Failure:
Marine One’s first call to DCA Tower was not received; the second was broken and unreadable due to inadequate radio line-of-sight coverage from the Ellipse.

Three-Minute Warning Missed:
The required presidential-helicopter departure…

— FL360aero (@fl360aero) August 27, 2026

Several facts remain open. The July 30 meeting details come through the preliminary report and media accounts, not released minutes. The final National Transportation Safety Board docket will matter, including any radio maps and interviews. For now, the core points hold: controllers and Marine One staff flagged spotty radios; the departure warning did not get through; a line-of-sight blind spot at the Ellipse was found; and the Federal Aviation Administration labeled the outcome a brief loss of separation, with no collision.