FirstAlerts
Plane CrashesVersion 6

FAA Investigating Marine One Separation Incident Near Reagan National

The agency says a preliminary review found a momentary loss of separation between the presidential helicopter and an Envoy Air regional jet on Aug. 4, 2026, and that President Trump was never in danger.

By AI ReporterFirst reported Aug 5, 2026, 12:00 a.m. ETUpdated Aug 15, 2026, 10:55 p.m. ET
The Federal Aviation Administration is investigating a safety incident involving Marine One over , on Tuesday, Aug. 4, 2026, according to Forbes, CNBC, KFGO, WKZO, The Jerusalem Post, AeroTime, Newser, Reality Tea, New York magazine and HuffPost; the Daily Express dated the event Aug. 5, 2026. Most of those outlets report the investigation is open, while HuffPost and the Express reported a stage: HuffPost said the FAA cited a safety review finding a momentary loss of separation and that the agency planned to convene a safety review team, and also reported that the National Transportation Safety Board said it would investigate. FAA spokeswoman Cassandra Nolan told the Express that "based on our safety review" there had been a "momentary loss of separation," that the president was "never in danger," and that a review continues. Accounts of the timing differ: Reality Tea, The Jerusalem Post, CNBC, KFGO and WKZO reported , New York magazine , HuffPost EDT, Newser ET, AeroTime , the Express , and Forbes placed it in the afternoon. The outlets reported that Marine One took off from the Ellipse, close to the White House, carrying President Donald Trump to Joint Base Andrews on the first leg of a trip to Los Angeles, and that there was an apparent loss of standard separation with an Envoy Air regional jet bound for Pensacola, Florida, which CNBC, KFGO and WKZO reported departed at Sources disagree on the aircraft involved: CNBC, The Jerusalem Post and WKZO described the airliner as an and HuffPost as an , while AeroTime reported an ; New York magazine reported that a lookalike helicopter serving as a decoy entered Reagan National airspace alongside Marine One. HuffPost, Newser, CNBC, KFGO and WKZO identified the flight as ; Newser wrote . CNBC, HuffPost, AeroTime and WKZO reported the flight was operated by . Both Marine One and the Envoy jet landed without incident, and Reality Tea reported no injuries. The FAA said it did not appear to be a dangerous close call and that the aircraft were not apparently converging, according to CNBC, KFGO, WKZO, The Jerusalem Post and Reality Tea. New York magazine reported that no collision occurred, that the helicopter carrying the president and the Envoy jet came within 0.8 miles laterally and 700 feet vertically of each other, and that at no point was Marine One dangerously close to another aircraft. The outlets reported that FAA rules require at least 1.5 miles horizontally and 500 feet vertically of separation around airports, and that investigators are examining whether that spacing was violated. White House spokesman Kush Desai said the president was at no point in harm's way, and New York magazine reported that the Marine Corps told CNN that "Marine One's flight on Aug. 4 was routine." CNBC, KFGO and WKZO reported that the White House and American Airlines, through its Envoy Air subsidiary, did not immediately comment. Several outlets reported that air-traffic controllers had not halted commercial flights at Reagan National as required by policy when Marine One departed, and that FAA air traffic control is typically given at least three minutes' notice before a Marine One departure. Newser reported that Marine One's pilots informed air traffic control at Reagan at least three times that they were preparing for , with no response. Another regional flight, Republic 4700, an Embraer 175 operating for American from Raleigh-Durham, was 3 miles from Reagan and was sent around out of caution, landing at 2:52 p.m.; New York magazine reported the Reagan tower told an inbound Republic Airways to abort its approach and that it landed 14 minutes later. Weather observations recorded at Reagan National, about 3 miles away and 19 minutes from the reported time, show wind from 60 degrees at 6 knots, visibility 10 statute miles, few clouds at 5,000 feet and a temperature of 87°F. The outlets noted that airspace around Reagan National has been under scrutiny since the midair collision of Jan. 29, 2025, after which the FAA imposed permanent restrictions on helicopter operations around the airport; the outlets reported that collision, between an incoming airliner and an Army Black Hawk helicopter, killed 67 people. No cause has been determined. The FAA and the National Transportation Safety Board are the bodies identified in the reporting, and no findings have been announced.

Was this report accurate and useful?

Reference data

From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.

Terrain elevation
39 ft
Nearest aerodrome
3.0 miles N of Ronald Reagan Washington National Airport (KDCA/DCA)

Sources

Revision history

  1. Version 616 Aug 2026, 02:55current

    Added New York magazine's 0.8-mile/700-foot separation figures and decoy VH-92A detail, FAA spokeswoman Cassandra Nolan's and White House spokesman Kush Desai's statements, the Marine Corps comment to CNN, no-injury report, KDCA weather observation, and the Express's differing Aug. 5 date; dropped the "developing" framing.

  2. Version 57 Aug 2026, 14:47

    No new facts; wording reviewed and left substantively unchanged from v4.

  3. Version 46 Aug 2026, 04:36

    Added HuffPost reporting: NTSB investigation, FAA preliminary safety review and planned safety review team, E170/E175 type conflict, 2:34 p.m. EDT timing, rerouting of Republic 4700, the 67 deaths in the January 2025 collision and the three-minute notice practice; dropped the geographic reference paragraph.

  4. Version 35 Aug 2026, 14:25

    Added Newser's flight number (Envoy Air 3742), its 2:33pm ET timing, the report that Marine One's pilots called Reagan tower at least three times with no response, and that both aircraft landed safely.

  5. Version 25 Aug 2026, 11:10

    Added AeroTime reporting: aircraft identified as an Embraer E175 operated by Envoy Air for American Airlines, a conflicting time of just after 14.30, FAA Class B separation minimums, and the Jan. 29, 2025 midair collision context.

  6. Version 15 Aug 2026, 09:09

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.