Federal investigators want to know why air traffic controllers at Reagan National Airport failed to halt commercial flights when Marine One lifted off with President Trump aboard, a protocol breach that produced a midair near-miss just months after a deadly collision at the same airport.

Marine One departed the Ellipse near the White House at 2:33 p.m. ET on Tuesday, carrying the president to Joint Base Andrews, where he would board Air Force One for Los Angeles. One minute later, at 2:34 p.m., an American Airlines flight operated by Envoy Air took off from Reagan National bound for Pensacola, Florida. The two aircraft came close enough to trigger what the FAA calls a "momentary loss of separation", a breach of the rules that exist to keep planes from colliding.

Reagan National sits fewer than five miles from the White House. Standing safety protocols require controllers to stop all takeoffs and landings whenever the president's helicopter passes on a conflicting route. Those rules were tightened after the January 29, 2025, midair collision at the same airport that killed 67 people. On Tuesday, the New York Post reported, controllers appear to have ignored them.

Tower audio shows controllers missed Marine One's advance warning

Before lifting off, Marine One's crew repeatedly contacted the Reagan National control tower and announced the presidential helicopter was "three minutes to lift." That call should have triggered an immediate ground stop for departing traffic on conflicting routes.

It didn't. AP News reported that tower audio reveals the air traffic controller failed to acknowledge Marine One's initial three-minute warning, a communication breakdown at the most basic level. The tower eventually responded with traffic information, "You've got traffic rotating off Runway One, E-170", alerting the helicopter crew that a regional jet, an Embraer E-170, was already rolling.

Marine One's crew said they would keep a "momentary delay" before proceeding. They lifted off anyway at 2:33 p.m. Sixty seconds later, the Envoy Air flight was airborne.

Tower audio captured what followed. The controller, apparently caught off guard by Marine One's movement, radioed back with a question that underscored the confusion.

As AP News reported, the controller asked:

"Uh, Marine One, you said, uh, you're proceeding as briefed?"

That a controller had to ask the president's helicopter crew whether it was, in fact, doing what it said it would do suggests the tower had not prepared the airspace. The question itself is an admission: the controller did not have the situation under control.

Both the FAA and NTSB opened formal investigations

The FAA confirmed the breach in a statement. It described the event in measured terms but did not dispute the core failure.

"There was momentary loss of separation after which the aircraft continued to move away from one another."

The agency added that "the air traffic controller was in contact with both the commercial pilot and Marine One pilot during the loss of separation." It said it is "continuing to review the incident and will implement any appropriate corrective actions based on our findings."

Fox News reported that both the FAA and the National Transportation Safety Board launched formal investigations into the August 4th loss of separation. FAA rules require aircraft at the same altitude to maintain at least three miles of horizontal distance within 40 miles of an airport surveillance radar antenna, a standard that was momentarily violated. Separate rules require at least 1.5 miles of horizontal separation and 500 feet of vertical separation under other conditions.

The administration has sought to minimize the danger. White House spokesman Kush Desai told reporters that "Marine One flights are piloted by some of the best aviators in the world, and at no point was the president in harm's way." The FAA's own statement echoed that framing, noting that "as the White House has said, the President was never in danger."

The president may not have been in danger of a collision. But the fact that a commercial aircraft full of passengers was allowed to take off into the path of the presidential helicopter, at the same airport where 67 people died in a midair collision seven months ago, is not a reassuring data point about the state of air traffic control at Reagan National.

January's deadly collision already exposed systemic failures at Reagan National

The January 29, 2025, disaster at Reagan National killed all 64 people aboard an American Airlines regional jet and three soldiers in an Army Black Hawk helicopter. That collision prompted the FAA to impose permanent restrictions on helicopter operations around the airport. Among the changes: controllers were required to halt all takeoffs and landings when a helicopter passed on a conflicting route.

Tuesday's incident suggests those post-collision rules were not followed. The Wall Street Journal first reported the investigation. The question now is whether the failure was an isolated lapse by one controller or a symptom of deeper problems in how military and civilian air traffic operations coordinate around the capital's most sensitive airspace.

The administration has been weighing physical infrastructure changes to presidential aviation. Trump has considered building a dedicated White House helipad to accommodate the new Marine One fleet, a project that could alter departure and arrival patterns near the Ellipse.

Tuesday's near-miss also fits a broader pattern of security concerns around the president's travel. Breitbart noted that the loss of separation incident is part of a series of events that includes an Air Force One electrical failure in January and a reported Iranian proxy threat against the president's plane last month. Questions about Iran's ability to threaten U.S. assets despite administration assurances have drawn scrutiny from conservative media figures pressing for clearer answers.

Broader lapses in protective operations have also drawn attention. Secret Service agents guarding the Vance family have faced accusations of leaking private details, raising separate questions about the reliability of the security apparatus surrounding senior officials.

No discipline announced, no names released

The FAA has not said whether any air traffic controllers have been placed on leave or disciplined. It has not identified the controller who failed to acknowledge Marine One's advance call. It has not released the specific flight number of the Envoy Air aircraft involved.

What it has released is a carefully worded statement that concedes the breach, promises corrective action, and avoids assigning blame. That is the bureaucratic default after every failure: acknowledge the problem in language designed to sound responsible, then slow-walk accountability until the news cycle moves on.

The FAA's own post-collision rules existed for exactly this scenario. They were written because 67 people died when airspace coordination failed at this same airport. Seven months later, a controller apparently missed or ignored a direct radio call from the president's helicopter, let a commercial jet take off into its path, and then asked the Marine One crew, after the fact, whether it was "proceeding as briefed."

Rules that exist on paper but fail in practice are not safety protocols. They are paperwork. And paperwork has never kept two aircraft from occupying the same patch of sky.