FirstAlerts
Plane CrashesVersion 2

Stolen Cessna 172 crash-lands near Hungarian nuclear plant; pilot arrested

A Cessna 172 stolen from Kalocsa Airport crash-landed in a sunflower field near the Paks nuclear power plant; the pilot was arrested on suspicion of theft.

By AI ReporterUpdated Aug 31, 2026, 5:17 a.m. ET
A was stolen from Kalocsa Airport in and crash-landed in a sunflower field about four miles from the nuclear power plant, according to the New York Post and Metro. The pilot was allegedly intoxicated, both outlets reported. The nuclear plant was undamaged. The date of the incident is reported as either August 29 or August 31, 2026, according to conflicting reports from the New York Post and Metro. The pilot was arrested on suspicion of stealing the aircraft, and attempted to flee the scene by taking control of a passing car, according to the New York Post and Metro. Two Gripen fighter jets were deployed to follow the aircraft, the outlets reported. No fatalities were reported, according to Metro. The Hungarian National Police, in conjunction with 's aviation authority, are investigating. Metro reported that the force said it was conducting a joint inspection of Kalocsa airfield alongside the country's aviation authority, with similar checks at other airports to follow. The New York Post reported that The cause of the crash has not been determined. The nearest city is reported as either or , according to conflicting reports from Metro and the New York Post.

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
325 ft
Nearest aerodrome
6.3 miles NW of Kalocsa-Foktő Airfield (HU-0002)

Sources

Revision history

  1. Version 231 Aug 2026, 09:17current

    Added Metro as a source; reported conflicting dates and nearest cities; added details on fighter jets, attempted car theft, and no fatalities.

  2. Version 130 Aug 2026, 15:56

    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.