NTSB investigations: Cessna 210A
5 cases on aircraft the registry lists as Cessna 210A, 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
| 1994 | 1 |
|---|---|
| 1996 | 2 |
| 1998 | 1 |
| 1999 | 1 |
Where
Open the mapLatest 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 ('2073408')
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 ('2073408')
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 FTW99LA130Accident · No injuriesLimited investigationFinal reportCessna 210A · Bay City, TXThe pilot's inadequate management of fuel and his failure to follow the pre-landing checklist resulting in the loss of engine power as a result of fuel starvation. Factors were the pilot's physiological condition and the lack of suitable terrain for the…NTSB DEN99LA007Accident · No injuriesLimited investigationFinal reportCessna 210A · Provo, UTThe pilot's abrupt throttle control movement that caused the engine to flood, and his failure to follow emergency procedures contained in the Airplane Flight Manual. Factors were increasing the mixture control to full rich and switching the fuel pump to high…NTSB FTW97LA071Accident · No injuriesLimited investigationFinal reportCessna 210A · Peyton, COthe pilot's improper fuel management by failing to avoid a prolong uncoordinated turn or slip, which resulted in fuel starvation. Factors relating to the accident were: darkness, and the lack of (activated) runway lights.NTSB LAX97LA001Accident · Minor injuriesLimited investigationFinal reportCessna 210A · Truckee, CAa total loss of engine power for undetermined nonmechanical reasons.NTSB CHI95LA022Accident · No injuriesLimited investigationFinal reportCessna 210A · Manhattan, KStotal loss of engine power for reason(s) undetermined. A factor was the dark night.