NTSB investigations: Cessna 210
10 cases on aircraft the registry lists as Cessna 210, where the first occurrence was “Loss of engine power(total) - mech failure/malf”. 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 |
| 1991 | 1 |
| 1992 | 1 |
| 1996 | 1 |
| 1998 | 1 |
| 2000 | 1 |
| 2003 | 2 |
| 2006 | 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 ('2073402')
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\" = 351))
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 ('2073402')
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" = 351))
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 ATL06LA050Accident · Minor injuriesLimited investigationFinal reportCessna 210 · Jesup, GAThe loss of engine power due to the fatigue failure of the crankshaft, which resulted in a forced landing, and an in-flight collision with trees. A factor associated with the accident was the failure of other maintenance personnel to comply with the engine…NTSB FTW04LA042Accident · Serious injuriesLimited investigationFinal reportCessna 210 · Clarendon, TXthe loss of engine power due the separation of the number six cylinder as a result of a fatigue failure from the loosening of the cylinder attachment hardware.NTSB CHI03LA059Accident · No injuriesLimited investigationFinal reportCessna 210 · Clarence, IAA failure of the crankshaft for undetermined reasons. Factors associated with the accident were the rough terrain on which the forced landing was made and the night conditions.NTSB CHI00LA085Accident · Minor injuriesLimited investigationFinal reportCessna 210 · Macomb, ILthe inadequate maintenance inspection prior to the ferry flight by the pilot/mechanic rated passenger who endorsed the airplane as airworthy, the shift in the number two main bearing left half, and the fractured crankshaft. A factor was the rough/uneven…NTSB LAX98LA067Accident · Minor injuriesLimited investigationFinal reportCessna 210 · Compton, CAThe failure of maintenance personnel to adequately inspect the aircraft during an annual inspection to detect a chafed and leaking engine fuel supply line.NTSB NYC96LA141Accident · Minor injuriesLimited investigationFinal reportCessna 210 · Boston, MAa fracture failure of the crankcase, which resulted in separation of the number five cylinder, loss of engine power, and a ditched landing.NTSB ATL92LA073Accident · No injuriesLimited investigationFinal reportCessna 210 · Florence, SCThe improper installation of the engine counterweight retention rings which resulted in the separation of the retention pin, allowing the leading edge of the counterweight to strike the crankcase. Factors in the accident were the subseqent loss of power and…NTSB CHI91FA160Accident · 1 fatalField investigationFinal reportCessna 210 · Belleville, MIFailure of the engine driven fuel pump, the failure of the pilot to activate the electric auxiliary fuel pump, poor inflight decision, and poor execution of emergency procedures. A factor relating to the accident is the pilot's lack of experience in this…NTSB LAX85FA019Accident · No injuriesField investigationFinal reportCessna 210 · San Pedro, CAThe acft was on a 3.5 mile final approach to torrence arpt when the pilot experienced an engine failure. The plt landed the acft the los angeles, west basin harbor. Examination of the engine and associated fuel lines after the accident revealed no evidence of…NTSB MIA83LA024Accident · No injuriesLimited investigationFinal reportCessna 210 · Near Miami, FLAbout 15 minutes after takeoff the aircraft engine quit. All attempts to restart the engine were unsuccessful and the pilot landed in the everglades swamp. Examination of the aircraft revealed that the fuel manifold valve, PN-631427-A15 was stuck in the…