0.82 Miles Apart: How Marine One Went Silent Twice in a Month

0.82 nautical miles. That is the distance the Federal Aviation Administration estimated between Marine One and a departing passenger jet over Washington on August 4 — less than a mile sideways, 700 feet vertically, with the president of the United States aboard the helicopter. ⁹ By the rules of the Class B airspace around Reagan National Airport, which demand 1.5 miles laterally or 500 feet vertically, that was not a near anecdote. It was a loss of separation, about two miles north of the airport. ³⁴⁹

On August 4, 2026, Marine One carrying President Trump lifted off from a temporary pad on the Ellipse at the same time an Envoy Air regional jet, Flight 3742 bound for Pensacola, was cleared for takeoff from Reagan National. ³⁴⁹ The two aircraft converged until they lost required separation. ³⁴⁹ No injuries or damage were reported. ⁵⁸ That clean outcome is the reason this story can be told precisely, and the reason it should unsettle anyone who flies through Washington.

The entire safety system at that moment depended on a single radio call. The Marine helicopter crew is supposed to give the tower a standard three-minute warning call before departing, and controllers never heard it. ⁵⁶⁸ On that warning hinges everything else: the tower freezes departures, and only then does the helicopter leave. Without the call, the local controller had no reason not to release the regional jet.

What the tower missed was not a mumble. The National Transportation Safety Board's preliminary account, released Thursday, August 27, 2026, said the first warning call "was never received at all" and a second was "broken and completely unreadable." ⁶⁷⁸⁹¹⁰ In other words, the failure was total and then partial, but never good enough to do its one job — stop the jets.

The NTSB attributed the failure to radio geometry. ⁷⁹ The temporary Ellipse landing zone sat out of line of sight of the helicopter-control transmitter, and ongoing White House construction contributed to the radio problems. ⁷⁹ A relay attempted through the Joint Base Anacostia Bolling facility also failed. ⁹ This was not a pilot forgetting to key the microphone. It was a presidential operating location that could not reliably be heard by the people charged with keeping aircraft apart.

The most damning detail in the file is that everyone saw this coming. Controllers and pilots from HMX-1 met on July 30 — at the pilots' request, one week before the incident — to discuss communication failures. ⁵⁷¹⁰ Controllers reported not receiving the three-minute warning call, and the two sides agreed on alternative means including an aircraft relay. ⁵⁷¹⁰ HMX-1 itself described communications from the Ellipse as spotty. ⁵⁷ They named the problem, they shook hands on a workaround, and five days later the workaround did not work either.

Transportation Secretary Sean Duffy said that Tuesday that FAA officials were working with the Marine One team to resolve telecom issues after the loss of separation. ⁶ The FAA said it had fixed the issue days before the second failure. ²³ That claim is now the center of the story, because on Thursday afternoon, August 27, 2026, Marine One again could not reach air traffic control before takeoff from the Ellipse — the second failure within a month. ²³⁴¹¹ Both the direct call and the agreed backup failed. ³⁴¹¹ Audio reviewed by ABC News confirmed the communication loss. ⁴

That is how White House spokesman Kush Desai described the president's position, saying the president "was at no point in harm's way." ⁵¹¹ In the narrowest sense, he is right. A loss of separation is not a collision, no one was hurt, and nothing was bent. ⁵⁸⁹ But harm's way is a strange phrase for an event whose whole point is that the system meant to measure harm's way went silent twice.

The radio protocol is a long-standing FAA and military practice typically traced to 2013, predating the January 2025 mid-air collision at the same airport. ¹¹ That lineage matters. Reagan National is the country's most congested and procedurally intricate terminal airspace, where helicopters and airliners are threaded through the same narrow corridors over the Potomac. The practice worked because everyone assumed the call would get through. August proved the assumption, not the discipline, was the system.

None of this turns on whether the August 27 jet traffic came as close as the August 4 traffic did. The sources do not establish a second loss-of-separation figure, and the truncated reporting does not confirm a second set of distances or discipline or a minute-by-minute timeline for that afternoon. ²³⁴ What is established is failure of function: the crew charged with announcing the president's movement could not reliably announce it, and the backup designed after explicit warning could not substitute.

The NTSB investigation remains tied to the preliminary finding that geometry and construction left a presidential helicopter in a radio blind spot, not to any suggestion that the pilots chose silence. ⁷⁹ That distinction should reassure and alarm in equal measure. It clears the crew and indicts the planning that put the commander in chief on a temporary pad whose voice could not reliably reach the tower, then kept him there after the first silence nearly put a regional jet in the same sky at the same time.