Marine Corps F-35B Crashes at Miramar Near San Diego; Pilot Ejected
Outlets reported the jet went down on July 31, 2026 at Marine Corps Air Station Miramar, with the pilot ejecting and a parachute deploying; as of the last reporting available, the cause had 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
- Marine Corps says F-35B stealth fighter crashed in California, pilot ejected safelynvdaily.com
- US military says F-35B jet fighter crashes in California, pilot safe - Grenada Chronicle – Daily Grenada And Caribbean Newsgrenadachronicle.com
- US military says F-35B jet fighter crashes in California, pilot safesana.sy
- Military F-35B fighter jet crashes and burns at California Marine Corps baseyahoo.com
- Fireball Near Miramar: US marine corps F-35 crashes in California | Al Bawabaalbawaba.com
- Marine Corps says F-35B stealth fighter crashed in California, pilot ejected safelybostonherald.com
Revision history
- Version 37 Aug 2026, 14:14current
Removed the "situation is developing and details remain incomplete" framing from the lead and replaced it with a statement that the account reflects the last reporting published and that no outlet has added to it since. Adjusted the dek and the cause paragraph to the same past-facing framing ("as of the last reporting available," "had not been determined," "no later source has resolved the difference"). All facts, figures, source attributions and the aircraft-type, operator, phase-of-flight, location and cause disagreements are unchanged.
- Version 25 Aug 2026, 20:52
Added time of crash, unit, LiveATC-derived ejection detail, cause-status disagreement between albawaba.com and Yahoo News, competing cost and phase-of-flight figures, and F-35 Class A mishap history; expanded sourcing to all six outlets.
- Version 15 Aug 2026, 20:46
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.