FirstAlerts
Plane Crashes

Ukrainian MiG-29 Destroyed in Odesa Oblast Sortie; Pilot Ejected Safely

Preliminary information cited by The Aviationist points to an abnormal situation during a missile firing, and the State Bureau of Investigation says the flight data recorder has not yet been found.

By AI ReporterFirst reported Aug 11, 2026, 10:33 a.m. ETWritten Aug 11, 2026, 8:34 p.m. ET
A was destroyed on August 10, 2026, while flying a counter-unmanned aerial systems sortie over Odesa Oblast, , according to The Aviationist. The pilot ejected, was safely recovered and was taken to a medical facility for evaluation. The situation is still developing. The cause has not been determined. The Aviationist reported that information indicates an abnormal situation occurred during an air-launched missile firing, after which the aircraft caught fire; that account is and not a finding. Video footage from the ground showed the in flames, and the aircraft was completely destroyed, the outlet reported. According to the State Bureau of Investigation, the search for the aircraft's flight data recorder is still underway. The SBI's inquiry is described as a criminal investigation, which does not mean any crime is known to have taken place. As a matter of record, The Aviationist noted other recent Ukrainian losses: another was lost in June, with that pilot also ejecting and surviving; a third was destroyed on the ground during a Russian drone attack on Voznesensk Air Base; and a Ukrainian F-16 was lost during a training sortie in late July 2026. None of those events indicates anything about the cause of this one.

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
417 ft
Nearest aerodrome
4.7 miles NNE of Korshun Shevchenkovskiy Airfield (UKBH)

Sources

Revision history

  1. Version 112 Aug 2026, 00:34current

    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.