F-16 Crashes Near Yalova, Turkey, During Training Flight; Pilot Ejected
Turkey's defence ministry said the pilot bailed out safely before the August 12 crash and that the cause will be established after a detailed investigation.
This is a developing story. Details reported early are provisional and are frequently revised. Where sources disagree, both readings are given.
We last searched for new coverage of this at Aug 18, 2026, 6:07 a.m. ET — checked 3h ago.
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
- 1,030 ft
- Nearest aerodrome
- 13 miles SW of Yalova Air Base (LTBP)
Sources
- Pilot ejects safely as F-16 crashes during training - Türkiye Newshurriyetdailynews.com
- F-16 aircraft crashes in Türkiye’s Yalova provinceazernews.az
- Turkish Air Force F-16 crashes near Yalova: videoaerotime.aero
- Turkish F-16 jet crashes during training in NW Türkiye, pilot survivesenglish.news.cn
- Turkish F-16 jet crashes during training in NW Türkiye, pilot survivesenglish.news.cn
- F-16 fighter jet explodes after crashing during training exercisedailymail.com
- Turkish Air Force F-16 crashes during training flight in Yalova | Al Bawabaalbawaba.com
- Turkish Air Force F-16 crashes during training flight in Yalova | Al Bawabaalbawaba.net
- Turkish F-16 flies over car and crashes just a few meters away – New video of fighter jet crash in Yalova (videos) - ProtoThema Englishen.protothema.gr
- Turkish F-16 Fighter Jet Crashes During Training Missionkashmirlife.net
- NATO fighter jet crashes and explodes into massive fireballmirror.co.uk
Revision history
- Version 317 Aug 2026, 11:50current
Added Xinhua and Kashmir Life reporting: defence ministry statement that the pilot safely bailed out, NTV footage of the fire, broader attribution of the investigation statement, and a note that the aircraft has not been identified alongside the operator's registry fleet count.
- Version 212 Aug 2026, 14:28
Added Azernews reporting: conflicting description of the operator, the 18th Air Base location, and preliminary information that the pilot ejected.
- Version 112 Aug 2026, 13:23
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.