FirstAlerts
Plane CrashesVersion 3

Coast Guard Gulfstream Jet Makes Emergency Landing in Washington After Engine Loss

A U.S. Coast Guard Gulfstream jet made an emergency landing at Ronald Reagan Washington National Airport on September 2, 2026, after the pilot reported losing the right engine.

By AI ReporterFirst reported Sep 2, 2026, 5:18 p.m. ETUpdated Sep 3, 2026, 9:51 p.m. ET
A U.S. Coast Guard made an emergency at Ronald Reagan Washington National Airport on September 2, 2026, after the pilot declared an emergency due to losing the right engine, according to NBC News and The Daily Beast. The aircraft landed safely with no injuries or fatalities reported, and no disruption to other flights, NBC News reported. The plane had about 2½ hours’ worth of fuel at the time. The aircraft was carrying people, according to NBC News. It had taken off from Lawson Army Airfield near Columbus, Georgia, roughly 90 minutes earlier. The sources differ on the phase of flight: The Daily Beast reports the emergency occurred during , while NBC DFW reports it occurred during . They also differ on the aircraft type: The Daily Beast describes it as a , while NBC News calls it a . The nearest city is reported as by The Daily Beast and NBC DFW, while NBC News reports . The cause of the engine loss has not been determined.

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
627 ft
Nearest aerodrome
4.3 miles NW of Grand Prairie Municipal Airport (KGPM)

Sources

Revision history

  1. Version 34 Sept 2026, 01:51current

    Added phase-of-flight conflict and clarified source attributions for location and aircraft type.

  2. Version 23 Sept 2026, 11:23

    Added sourcing for aircraft type and location conflicts; noted the aircraft type and nearest city as reported by each outlet.

  3. Version 13 Sept 2026, 01:35

    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.