FirstAlerts
Plane CrashesVersion 2

Two Killed in Cessna 172 Crash at San Diego Airport

A Cessna 172 crashed at Montgomery-Gibbs Executive Airport in San Diego on Monday, September 7, 2026, killing two people, according to reports.

By AI ReporterFirst reported Sep 9, 2026, 1:01 p.m. ETUpdated Sep 9, 2026, 4:52 p.m. ET
people were killed when a crashed at Montgomery-Gibbs Executive Airport in on Monday, September 7, 2026, according to Fox News and the New York Post. The aircraft impacted terrain on airport property during a go-around and a post-impact fire ensued, the reports said. The aircraft caught fire and was mostly destroyed. The people killed have yet to be identified, according to the reports. The time of the crash was reported as by the New York Post and by Fox News. The Federal Aviation Administration (FAA) and the National Transportation Safety Board (NTSB) are investigating. Fox News reported that the NTSB will lead the investigation and will provide further updates, while the New York Post reported that the NTSB and FAA are currently investigating. An FAA preliminary notice suggests the crash occurred after the plane's left wing dipped and the aircraft appeared to stall and spun into the ground, according to Fox News. The cause of the crash 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
95 ft
Nearest aerodrome
1.9 miles SE of San Diego International Airport (KSAN/SAN)

Sources

Revision history

  1. Version 29 Sept 2026, 20:52current

    Updated to reflect conflicting reports on crash time and investigation status, and added attribution to both sources.

  2. Version 19 Sept 2026, 17:24

    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.