NTSB investigations: Cessna 210M
5 cases on aircraft the registry lists as Cessna 210M, where the first occurrence was “In flight collision with terrain/water”. 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
| 1982 | 1 |
|---|---|
| 1983 | 1 |
| 1991 | 1 |
| 2001 | 1 |
| 2003 | 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 ('2073450')
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\" = 230))
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 ('2073450')
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" = 230))
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 CHI03LA175Accident · No injuriesLimited investigationFinal reportCessna 210M · Carlisle, ARThe pilot's improper in-flight decision to descend for landing, at night, without the runway environment insight. Contributing factors were the pilot's disorientation, the embankment and the dark night condition.NTSB FTW01LA050Accident · Serious injuriesLimited investigationFinal reportCessna 210M · Burnet, TXthe pilot's failure to maintain proper glide path during a practice instrument approach, which resulted in an in-flight collision with terrain. Contributory factors to the accident were the dark night light condition and the safety pilot's inadequate…NTSB DEN92FA016Accident · 1 fatalField investigationFinal reportCessna 210M · Albuquerque, NMInsufficient terrain clearance altitude selected by the pilot in command.NTSB MIA84FA053Accident · 3 fatalField investigationFinal reportCessna 210M · West Palm Beach, FLAt 1926 the plt was cleared for the LOC bc arch for rwy 27R. At 1927 the acft acknowledged a clearance to land. 10 secs later the radar target disappeared. The plt was rescued at 2050 from the waters of the atlantic ocean about 1 mioff the Beach at West Palm…NTSB CHI83FA059Accident · 2 fatalField investigationFinal reportCessna T210 · Defiance, OHAircraft crashed during non-precision approach in weather that was below minimums for that type of approach.