A communications breakdown left the Marine One crew unable to warn air traffic controllers before the presidential helicopter departed on August 4, the NTSB found, and a passenger jet took off into its path at Reagan National Airport.
The crew tried at least twice to deliver the required three-minute advance notice before lifting off with President Donald Trump aboard, but garbled transmissions and radio failures meant controllers never received the warning. A departing commercial aircraft, identified in federal reporting as an Envoy Air jet, briefly lost safe separation from the helicopter, triggering dual investigations by the NTSB and the FAA.
The finding, released Thursday by the National Transportation Safety Board, confirms what tower audio had already suggested: the system built to keep the president's aircraft and commercial traffic apart failed at every level. Controllers did not know Marine One was preparing to depart until the moment it left the ground. The standard protocol, halt all takeoffs and landings when a helicopter crosses a conflicting route, went unenforced because the people responsible for enforcing it never got the call.
A known problem, a failed fix, and a near-miss
The August 4 incident did not come out of nowhere. Breitbart reported that air traffic controllers and Marine One pilots had met one week before the close call specifically to address the communication failures. They agreed on an alternative notification method. That backup plan also failed on the day it mattered.
Tower audio captured the confusion in real time. One controller, apparently unaware that Marine One was about to depart, radioed: "Uh, Marine One, you said, uh, you're proceeding as briefed?" Seconds later, another transmission followed: "OK, no three minutes, roger, proceed as briefed." The three-minute warning, the entire safety buffer designed to clear commercial traffic before a presidential departure, simply never arrived in readable form.
A separate exchange, reported by WTOP and cited in Just The News coverage, captured a controller asking a support helicopter: "If you hear Marine One, can you let me know?" That a federal air traffic controller had to rely on a secondary aircraft to relay presidential departure information tells you how badly the communications chain had broken down.
The FAA confirmed "a momentary loss of separation" between the two aircraft. Under rules implemented after the deadly January 29, 2025, midair collision at the same airport, a crash that killed sixty-seven people, all takeoffs and landings are supposed to halt when a helicopter passes on a conflicting route. That policy appeared to be violated during the president's departure.
White House construction relocated the helicopter pad and broke the radios
The root cause, as pieced together across federal reporting, traces back to the White House itself. Ongoing construction forced the relocation of Marine One's helicopter pad, and that move disrupted the radio link between the crew and Reagan National's tower. The FAA has since repositioned a radio receiver to the top of the airport's control tower in an attempt to restore reliable communications.
But the problems did not end on August 4. Just The News noted that communication breakdowns between Marine One and controllers continued to occur as recently as the date of its own report, weeks after the near-miss. A relocated radio receiver is a patch, not a permanent fix, and the NTSB's finding does not indicate whether the agency has issued formal safety recommendations to prevent a recurrence.
Presidential travel has repeatedly tested the limits of security coordination in recent months. A prior safety breach at Reagan National involving Marine One already drew federal scrutiny, and the August 4 incident compounds the concern.
AP News reported that both the FAA and NTSB launched separate investigations into the incident. The Washington Examiner noted that Marine One had taken off from the White House lawn shortly after 2:30 p.m. that Tuesday, before standard airport safety procedures could be enacted at Reagan National. FAA regulations require 1.5 miles of horizontal separation and 500 feet of vertical separation between aircraft, thresholds that may have been violated.
Officials insist Trump was never in danger
White House spokesman Kush Desai pushed back on any suggestion the president faced risk. "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," Desai said. Marine Corps spokesperson Capt. Jacob Sugg echoed that message: "There were no close calls with the routine Marine One movement."
Those reassurances sit uneasily alongside the NTSB's own finding. If controllers did not know Marine One was departing, if the three-minute warning never got through, and if a commercial jet took off into a conflicting route, then the system designed to protect the president did not work as intended, regardless of how skilled the pilots are.
The January 2025 midair collision at Reagan National, involving a military helicopter and an American Airlines regional jet, remains fresh in the minds of controllers, pilots, and passengers who use the airport daily. The FAA adopted the halt-all-traffic policy precisely because that disaster exposed how dangerous mixed helicopter and commercial traffic can be in the tight airspace around the capital. Less than seven months later, the policy built to prevent the next catastrophe was not followed during a presidential departure.
Security around presidential movement has been tested in other ways this year. In one episode, the Secret Service evacuated Trump from Turkey in a catering truck after an Iranian missile threat. Separately, Trump's arrival at JFK grounded flights and stranded thousands of travelers across the country. The recurring theme is a security apparatus stretched thin and coordination systems that buckle under pressure.
Unanswered questions the NTSB has not addressed
The NTSB's finding, as Military Times reported, leaves critical gaps. The board has not disclosed how close the two aircraft actually came to each other. It has not identified the passenger jet's flight number. It has not said whether this is a preliminary finding or part of a broader formal investigation. And it has not issued, or at least not publicly released, specific corrective recommendations.
The Transportation Secretary was reported to be working on telecom issues related to the incident as early as August 11, one week after the close call. What specific remediation has been completed, beyond moving a single radio receiver, remains unclear.
Threats to presidential security are not limited to airspace. An armed man arrested at Trump's golf course earlier this year was found carrying 208 pages of sketches, Melania Trump's schedule, and Secret Service operational details, a reminder that the protective infrastructure around the president faces pressure from every direction.
The Marine One crew did what they were supposed to do: they tried to call ahead. Twice. The radios failed. The backup plan failed. The controllers were left guessing. And a passenger jet rolled down the runway into the path of the president's helicopter because nobody on the ground knew he was coming.
When the system built to protect the president and hundreds of airline passengers breaks down because someone moved a helicopter pad and nobody fixed the radios, the question is not whether the pilots are skilled enough to avoid a disaster. The question is why the people in charge of the infrastructure let it stay broken.
