FirstAlerts
Plane CrashesVersion 5

FAA Examining Marine One Safety Incident Over Washington

Outlets report a possible loss of separation between the presidential helicopter and an Envoy Air regional jet during a departure from the Ellipse on Aug. 4, 2026.

By AI ReporterFirst reported Aug 5, 2026, 4:47 a.m. ETUpdated Aug 7, 2026, 10:47 a.m. ET
The Federal Aviation Administration is examining a safety incident involving Marine One over , on Tuesday, Aug. 4, 2026, according to Forbes, AeroTime, Newser and HuffPost. The matter is developing. Forbes, AeroTime and Newser report the investigation is open; HuffPost reported that the FAA cited a safety review finding a momentary loss of separation, and that the agency planned to convene a safety review team. HuffPost also reported that the National Transportation Safety Board said it would investigate. Accounts of the timing differ: Forbes placed it in the afternoon, AeroTime reported , Newser put it at ET and HuffPost at EDT. The outlets reported that Marine One took off from the Ellipse, close to the White House, with President Trump aboard, and that there was a possible "loss of standard separation" with an Envoy Air regional jet bound for Pensacola during the departure. Newser identified the airliner as ; HuffPost referred to it as . Sources disagree on the aircraft type: AeroTime reported an and HuffPost an , in both cases operated by . The FAA said it did not appear to be a dangerous close call and that the aircraft were not apparently converging, according to the reporting, and HuffPost reported the FAA said the loss of separation was momentary and that President Trump was not in danger. Both aircraft landed safely, and Marine One landed at Joint Base Andrews. FAA rules require at least 1.5 nautical miles or 500 feet of separation in Class B airspace, the outlets reported, and investigators are examining whether that spacing was violated. 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; the outlets reported that FAA air traffic control is typically given at least three minutes' notice before Marine One departs. Another regional flight, Republic 4700, was 3 miles from Reagan and was rerouted out of caution, according to the reporting. 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 helicopter restrictions around the airport; the outlets reported that collision killed 67 people. No cause has been determined. The FAA and the NTSB 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 57 Aug 2026, 14:47current

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

  2. 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.

  3. 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.

  4. 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.

  5. 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.