NTSB investigations: Cessna 210-5(205)
4 cases on aircraft the registry lists as Cessna 210-5(205), where the first occurrence was “Loss of engine power(total) - nonmechanical”. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1987 | 1 |
|---|---|
| 1988 | 1 |
| 1996 | 1 |
| 1999 | 1 |
Where
Latest cases
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
WHERE c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073202')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 353))
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073202')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 353))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB IAD99FA043Accident · 6 fatalField investigationFinal reportCessna 205 · Celina, OHwas the pilot's failure to refuel the airplane which resulted in fuel exhaustion and a loss of engine power. Also causal to the accident was the pilot's failure to maintain aircraft control after the power loss. A factor in the accident was a lack of…NTSB FTW96LA345Accident · No injuriesLimited investigationFinal reportCessna 210-5 · Muskogee, OKloss of engine power due to fuel contamination. The lack of suitable terrain for a forced landing was a related factor.NTSB FTW88FA119Accident · 4 fatalField investigationFinal reportCessna 205 · Elgin, TXThe pilot radioed that he was running out of fuel while being vectored for landing. The ceiling was about 900 feet with 5 miles visibility and the accident occurred in a level grass field. Witnesses heard the engine cutting out and a loss of control occurred…NTSB ATL87FA168Accident · 4 fatalField investigationFinal reportCessna 205C · Bowling Green, KYShortly after takeoff from Bowling Green, the pilot reported a problem. He did not report the details of the problem, but witnesses heard the aircraft backfiring as it descended. The aircraft had taken on fuel at Bowling Green. The investigation failed to…