Fatal NTSB investigations: Cessna 210M
13 cases on aircraft the registry lists as Cessna 210M. 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
| 1979 | 1 |
|---|---|
| 1982 | 1 |
| 1983 | 2 |
| 1985 | 2 |
| 1987 | 1 |
| 1991 | 2 |
| 1996 | 1 |
| 1997 | 1 |
| 1998 | 1 |
| 2001 | 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.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073450'))
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."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073450'))
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 IAD02FA002Accident · 2 fatalField investigationFinal reportCessna 210M · Pittsfield, PAThe pilot's loss of control in flight due to spatial disorientation, and his subsequent overstress of the airplane during a recovery attempt. A factor in the accident was the pilot's use of inappropriate medications.NTSB FTW98FA338Accident · 3 fatalField investigationFinal reportCessna 210M · Leesville, LAThe pilot's failure to establish a climb during a night go-around. Factors were the lack of visual cues available to the pilot and the dark night illumination.NTSB NYC97FA103Accident · 3 fatalField investigationFinal reportCessna 210M · Elliston, VAfailure of the PIC to maintain control of the airplane, due to spatial disorientation.NTSB LAX96FA284Accident · 1 fatalField investigationFinal reportCessna 210M · Corning, CAimproper installation of an electrical component, during an alteration of the aircraft electrical system; and subsequent electrical insulation failure, which resulted in electrical shorting, arcing, and an electrical fire. Factors relating to the accident…NTSB DEN92FA016Accident · 1 fatalField investigationFinal reportCessna 210M · Albuquerque, NMInsufficient terrain clearance altitude selected by the pilot in command.NTSB DEN91FA079Accident · 2 fatalField investigationFinal reportCessna 210M · Colorado City, TXThe pilot continuing flight into known adverse weather conditions and exceeding the design stress limits of the aircraft. Factors were: thunderstorm, updrafts and the pilot's disregard of the weather briefing.NTSB BFO87FA026Accident · 4 fatalField investigationFinal reportCessna 210M · Charleston, WVThe aircraft bounced after landing touchdown. Witnesses observed the aircraft assume a nose high attitude and heard some power applied to the engine as the aircraft veered to the right. It was not determined whether the pilot was attempting to abort the…NTSB NYC85FA120Accident · 2 fatalField investigationFinal reportCessna 210M · Morrisville, NYShortly after t/o the pilot experienced a rough running engine, continued maneuvering at a low altitude and the engine quit due to undetermined cause. The pilot attempted to stretch the glide to an open field and stalled the aircraft, which mushed into the…NTSB MIA85FA105Accident · 1 fatalField investigationFinal reportCessna 210 · Jacksonville, FLThe acft crashed & burned while attempting to return to the arpt after the pilot reported a power loss shortly after takeoff. A post crash exam of the engine did not reveal any evidence to suggest any failure or malfunction prior to impact.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 MKC84FA014Accident · 5 fatalField investigationFinal reportCessna 210M · Greensburg, KSAt 1619 CST, the non-instrument rated plt called the dodge city fss & requested the current dodge city wx. He was given the current & forcasted wx. He took off at 1825 & at 1846, he called the la junta radio & requested an update on the dodge city wx as well…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.NTSB MIA79FA102Accident · 1 fatalClosedCessna 210M · Milton, FL