NTSB investigations: Cessna 210M
5 cases on aircraft the registry lists as Cessna 210M, where the first occurrence was “Loss of engine power”. 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 |
|---|---|
| 1984 | 1 |
| 1996 | 1 |
| 1997 | 1 |
| 1998 | 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\" = 350))
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" = 350))
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 FTW98LA349Accident · No injuriesLimited investigationFinal reportCessna 210M · Albuquerque, NMA power loss for reasons undetermined. A factor was unsuitable terrain on which to make a forced landing.NTSB MIA97LA118Accident · No injuriesLimited investigationFinal reportCessna 210M · Troy, ALThe pilot's failure to obtain the proper touchdown point during an emergency landing resulting in an overrun and subsequent nose over. A factor in the accident was a reported partial loss of engine power for undetermined reasons.NTSB MIA96LA215Accident · No injuriesLimited investigationFinal reportCessna 210M · Opa Locka, FLthe pilot's improper fuel management, which resulted in a loss of engine power due to fuel starvation, a forced landing, and subsequent in flight collision with terrain. The lack of suitable terrain for a forced landing was a related factor.NTSB CHI84LA371Accident · No injuriesLimited investigationFinal reportCessna 210M · Howell, MIThe plt stated that about 10 min after takeoff, the fuel flow fluctuated & slowly went to zero. He turned the aux fuel pump on, increased the mixture to rich & repositioned the fuel selector to another tank, but to no avail. The plt made a forced landing in a…NTSB MIA82DA077Accident · Serious injuriesFinal reportCessna 210 · Atlantic Ocean (Atlantic Ocean)The pilot reported departing valkaria, Florida on a VFR round robin flight to great abaco island, Bahamas and return. While on the return leg of the flight, the engine lost power. The pilot was unable to restore power or glide to land; therefore, he ditched…