Trump's Helicopter and a Passenger Jet Got Too Close Over DC. Here's What Happened.

The US Federal Aviation Administration (FAA) — the government agency that manages air traffic — is investigating an incident in which Donald Trump's Marine One helicopter flew closer to a commercial passenger jet than safety rules allow. The event took place over Washington DC on 5 August 2026. The FAA said the two aircraft were not on a collision course and that this was not a dangerous near-miss. However, breaking the required distance between aircraft is automatically treated as a safety event that must be formally reviewed. (The Guardian)
Here is how it happened. At about 2:33 pm, Marine One lifted off from the Ellipse, a park near the White House, carrying the president to Joint Base Andrews for a flight to Los Angeles. One minute earlier, at 2:34 pm, American Airlines flight 3742 had taken off from Reagan National Airport, heading to Pensacola, Florida. The plane was an Embraer E170 operated by Envoy Air, a company owned by American Airlines.
The two aircraft ended up in the same airspace at the same time because, according to current reporting, air traffic controllers forgot to stop commercial flights from taking off before Marine One departed. Normally, controllers get at least three minutes' warning before a presidential helicopter takes off so they can pause commercial traffic. (Reuters)
A third plane was also affected. Republic flight 4700, flying from Raleigh-Durham to Washington DC, was three miles from Reagan National when the incident happened. Controllers told it to do a go-around — meaning the pilot abandoned the landing approach, circled back, and tried again. It landed safely at 2:52 pm. Flight 3742 continued to Pensacola without any further problems, landing at 3:33 pm CT after a 2-hour-16-minute flight. No one was injured on any of the aircraft. (THV11)
The FAA plans to bring together a safety review team to investigate, according to anonymous sources cited by Reuters. The agency's early assessment is cautious: it did not look like a dangerous close call, and the aircraft did not appear to be heading toward each other. But any breach of the required minimum distance counts as a reportable safety event, whether or not anyone had to take evasive action.
These distance rules were made stricter after a terrible accident in January 2025. In that crash, a commercial airliner and a US Army Black Hawk helicopter collided in mid-air over Washington DC, killing all 67 people on both aircraft. After the disaster, the FAA put permanent restrictions on helicopter flights near Reagan National Airport and created rules requiring aircraft to stay at least 1.5 miles apart horizontally and 500 feet apart vertically when near airports. The 2025 crash also led Trump to order an immediate nationwide review of aviation safety.
That 2025 collision left a lasting mark on how Washington DC airspace is managed. The National Transportation Safety Board recovered the Black Hawk's flight data recorder intact. Trump publicly said the helicopter had been flying above its allowed altitude on a clear night. Trump and members of his administration also claimed, without providing evidence, that diversity hiring programs at the FAA under the Biden and Obama administrations contributed to the crash. In December 2025, the US government admitted in a lawsuit response that failures by both the FAA and the Army played a role — a formal acknowledgment of institutional fault that came about eight months before this latest incident.
The broader context here is that Washington DC's airspace is unusually crowded. Reagan National Airport has very heavy air traffic, and military helicopter routes serving the White House, the Pentagon, and other federal sites cross right through the same area. Think of it like a busy intersection where cars, buses, and emergency vehicles all share the same road — except in three dimensions and at high speed. After the 2025 crash, experts and officials raised concerns again about how this congestion makes it hard to keep aircraft safely separated even on a normal day. Wednesday's incident, where controllers failed to pause commercial flights before a presidential helicopter took off, fits exactly into that known risk, even though no one was hurt this time.
The fact that this breach happened despite the new rules and restrictions suggests the problem may not be the regulations themselves but how they are carried out on the ground — the moment when routine commercial flights and presidential movements meet in the air traffic control system. A safety review team will likely look at whether the three-minute notification protocol was followed, whether controllers received the notice but did not act on it, or whether something went wrong in the handoff between different controlling authorities. The FAA has not yet released a preliminary report or a timeline for its findings.


