FirstAlerts
Plane CrashesVersion 6

FAA Investigating Apparent Loss of Separation Between Marine One and Envoy Air Jet at Reagan National

No collision occurred, and the agency said the August 4 event did not appear to be a dangerous close call; the cause has not been determined.

By AI ReporterFirst reported Aug 5, 2026, 12:00 a.m. ETUpdated Aug 11, 2026, 8:25 p.m. ET
The Federal Aviation Administration is investigating an apparent failure to maintain required separation between Marine One, carrying President Donald Trump, and Flight 3742 near Ronald Reagan Washington National Airport in The event occurred on August 4, 2026, according to realitytea.com, nymag.com, jpost.com, cnbc.com, wkzo.com and kfgo.com, or on August 5, 2026, according to express.co.uk, at as reported by realitytea.com, jpost.com, cnbc.com, wkzo.com and kfgo.com, at as reported by nymag.com, or as reported by express.co.uk, during the phase. The matter is still developing and details may change. No collision occurred. jpost.com, cnbc.com and wkzo.com reported that the aircraft was a regional jet bound for Pensacola, Florida, which departed at 2:34 p.m.; nymag.com reported that the aircraft lifting off from Runway 1, within a mile of Marine One's flight path, was an Embraer E175 operated by , and that the helicopter carrying the president was a , with a lookalike VH-92A Patriot serving as a decoy entering Reagan National airspace alongside it. The aircraft involved have not been identified by registration; registry records list seven aircraft under , which is not an indication of which aircraft was involved. According to express.co.uk, the helicopter and the jet came within 0.8 miles laterally and 700 feet vertically of each other; the FAA defines safe separation near airports as at least 1.5 miles laterally and 500 feet vertically. realitytea.com reported no injuries. Marine One took off from the Ellipse near the White House en route to Joint Base Andrews on the first leg of a trip to Los Angeles, with the president later boarding Air Force One at Andrews. Both Marine One and the Envoy jet landed without incident. Several outlets — cnbc.com, jpost.com, wkzo.com and kfgo.com — reported that air-traffic controllers had not halted commercial flights at Reagan National as required by policy when Marine One departed. nymag.com reported that Reagan tower told an inbound Republic Airways Embraer E175 to abort its approach and that it landed 14 minutes later; cnbc.com and jpost.com reported that Republic 4700, an Embraer 175 from Raleigh-Durham operating for American, was 3 miles from Reagan and was sent around out of caution, landing at 2:52 p.m. realitytea.com reported that Republic Flight 4700 was sent around as a precaution and later landed safely. Accounts of the FAA's posture differ. realitytea.com, kfgo.com, jpost.com, wkzo.com and cnbc.com reported that the agency said it is investigating the safety incident, that it did not appear to be a dangerous close call and the aircraft were not apparently converging, and that two sources said the FAA plans to convene a Safety Review Team. express.co.uk reported that FAA spokeswoman Cassandra Nolan said 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. The cause has not been determined. nymag.com reported that at no point was Marine One dangerously close to another aircraft and that the chance of a midair collision was essentially nonexistent, and that the Marine Corps told CNN that "Marine One's flight on Aug. 4 was routine." White House spokesman Kush Desai said the president was at no point in harm's way, according to express.co.uk; realitytea.com reported that the White House and American Airlines, through its subsidiary, did not immediately comment. Outlets including express.co.uk, realitytea.com, cnbc.com, wkzo.com and jpost.com noted that in January 2025 a collision between an incoming airliner and an Army Black Hawk helicopter in Washington airspace killed 67 people, and that the FAA subsequently imposed permanent restrictions on helicopter operations around Reagan National. Weather observations recorded at Reagan National, three miles away and 19 minutes from the reported time, showed wind from 60 degrees at 6 knots, visibility of 10 statute miles, few clouds at 5,000 feet and a temperature of 87°F. The observation is an instrument reading and is not offered as a factor in what occurred.

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 612 Aug 2026, 00:25current

    Added wkzo.com to the attribution of the date, time, aircraft type, FAA posture and January 2025 collision details.

  2. Version 512 Aug 2026, 00:20

    Added the disputed aircraft type (E170 per jpost/cnbc vs VH-92A per nymag), broadened date and time attribution to all reporting outlets, added the Pensacola-bound 2:34 p.m. departure, the reported failure to halt commercial flights, Republic 4700's Raleigh-Durham origin and 3-mile position, the Ellipse departure point, and a note that the aircraft are unidentified alongside Envoy Air registry fleet size.

  3. Version 48 Aug 2026, 00:18

    Added nymag.com reporting: aircraft identified as a Sikorsky VH-92A Patriot, a decoy lookalike in the airspace, the Envoy Embraer E175 departing Runway 1, the Republic Airways E175 told to abort and landing 14 minutes later, the Marine Corps statement to CNN, and nymag's assessment of collision risk; date attribution updated to include nymag.

  4. Version 37 Aug 2026, 15:20

    No new facts; text reviewed and attribution of the conflicting FAA characterisations and date/time ranges retained unchanged.

  5. Version 26 Aug 2026, 10:41

    Added express.co.uk reporting: FAA spokeswoman Cassandra Nolan's 'momentary loss of separation' statement, the 0.8-mile/700ft figures, White House spokesman Kush Desai's comment, and noted conflicts over the date, time and investigation status.

  6. Version 15 Aug 2026, 23:37

    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.