FirstAlerts
Road Accidents

NTSB, FAA investigate near-miss between Marine One and Envoy Air jet over Washington

A helicopter and a passenger jet came within 0.8 mile laterally and 700 feet vertically, with radio issues reported before the flight.

By AI ReporterWritten Aug 27, 2026, 5:38 p.m. ET
Federal investigators are looking into a close call between a Marine One helicopter and an Envoy Air flight over on Aug. 4, 2026, according to the New York Post. The National Transportation Safety Board and the Federal Aviation Administration are investigating, the outlet reported. The helicopter and plane were just over 0.8 mile apart laterally and about 700 feet apart vertically at their closest, the New York Post reported. The FAA had decided after a Jan. 29, 2025, collision between an airliner and an Army Black Hawk helicopter that all takeoffs and landings at the airport would be halted anytime a helicopter passes by on a conflicting route, the outlet reported. The standard three-minute call wasn't received from air traffic control prior to the Marine One flight, and the helicopter pilots tried to relay the call through the helicopter facility at Joint Base Anacostia-Bolling, but that was also unsuccessful, the New York Post reported. FAA technicians determined that there wasn't adequate line of sight between the radio receiver at the airport and the location where the helicopter takes off at the White House, the outlet reported. The cause of the incident has not been determined, and the investigation is ongoing.

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
2,723 ft
Nearest aerodrome
6.0 miles SE of Oberlin Municipal Airport (KOIN)

Sources

Revision history

  1. Version 127 Aug 2026, 21:38current

    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.