NTSB investigations: Cessna T210M
19 cases on aircraft the registry lists as Cessna T210M, 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
| 1983 | 1 |
|---|---|
| 1985 | 1 |
| 1986 | 1 |
| 1988 | 1 |
| 1989 | 1 |
| 1990 | 1 |
| 1991 | 2 |
| 1992 | 1 |
| 1994 | 2 |
| 1996 | 1 |
| 1997 | 2 |
| 2000 | 1 |
| 2001 | 1 |
| 2002 | 1 |
| 2003 | 1 |
| 2005 | 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 ('2073451', '2073452')
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 ('2073451', '2073452')
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 LAX05LA136Accident · Serious injuriesLimited investigationFinal reportCessna T210M · Phoenix, AZa loss of power for undetermined reasons.NTSB MIA03LA160Accident · No injuriesLimited investigationFinal reportCessna T210M · Hialeah, FLSpinning of the crankshaft No. 2 main bearing for undetermined reasons resulting in damage to the aft cheek of the No. 2 main bearing journal, fatigue failure of the crankshaft cheek, failure of the engine in cruise flight, and damage to the airplane during…NTSB LAX02FA163Accident · 2 fatalField investigationFinal reportCessna T210M · Groveland, CAa catastrophic engine failure due to the fatigue fracture and failure of the crankshaft. A factor contributing to the accident was the unsuitable nature of the mountainous terrain for a successful forced landing. The precipitating cause of the fatigue…NTSB FTW02FA054Accident · 2 fatalField investigationFinal reportCessna T210-M · Monticello, ARThe separation of the #2 connecting rod and subsequent catastrophic failure of the engine. A factor was the in-flight collision with a vehicle while maneuvering to a emergency landing area.NTSB LAX00GA102Accident · No injuriesFinal reportCessna T210M · Elfrida, AZThe company mechanic's failure to correctly install one or more of the crankshaft counterweight pin retaining plate snap rings, specifically ensuring that the snap rings were fully seated in their grooves. This led to the complete separation of the No. 2…NTSB LAX97LA307Accident · No injuriesLimited investigationFinal reportCessna T210M · San Martin, CAInstallation of improper connecting hardware by maintenance personnel, and, the inadequate inspection of the installed hardware by inspection personnel resulting in separation of the engine throttle linkage.NTSB CHI97IA127Incident · No injuriesIncident investigationFinal reportCessna T210 · Winona, MNLoss of engine power due to improper maintenance installation.NTSB NYC97LA035Accident · Minor injuriesLimited investigationFinal reportCessna T210M · Lexington, KYfailure of #5 exhaust valve and/or #5 exhaust valve guide, which resulted in a progressive engine failure (debris puncturing the #5 piston crown, exhaust gasses entering the crankcase, loss of oil through the breather system, oil exhaustion, and subsequent…NTSB SEA94LA196Accident · No injuriesLimited investigationFinal reportCessna T210M · Rathdrum, IDThe fatigue failure of the crankshaft and a slipped bearing.NTSB MIA94FA064Accident · 2 fatalField investigationFinal reportCessna T210M · Prentiss, MSA total loss of engine power due to the number five piston crown structure sustaining detonation/pre-ignition damage for undetermined reasons. The number two connecting rod and rod bolts failed due to an oil distress event. This resulted in a subsequent…NTSB CHI92LA094Accident · No injuriesLimited investigationFinal reportCessna T210M · Washington, INThe total loss of engine power due to a fatigue-fractured crankshaft.NTSB DEN92IA013Incident · No injuriesIncident investigationFinal reportCessna T210M · La Veta, COFailure of the no 1 connecting rod due to lack of lubrication from blocked oil ports.NTSB DEN91FA061Accident · Serious injuriesField investigationFinal reportCessna T210M · Littleton, COImproper reassembly of the overhauled turbocharger by maintenance personnel, and the pilot's improper use of the mixture control and boost pump. Factors related to the accident were: the adverse weather conditions and unsuitable terrain in the emergency…NTSB DEN91LA006Accident · No injuriesLimited investigationFinal reportCessna T210M · Englewood, COEngine failiure resulting from maintenance discrepancies.NTSB DEN89LA206Accident · No injuriesLimited investigationFinal reportCessna T210M · Rangely, COForced landing in unsuitable terrain as a result of an engine crankshaft failure.NTSB FTW88IA078Incident · No injuriesIncident investigationFinal reportCessna T210M · Grosebeck, TXThe pilot made a forced landing following engine failure. Teardown examination showed the no. 4 exhaust valve head had separated from the stem. Metal debris was found in the oil sump. The no. 1 connecting rod was separated from the crankshaft. There was…NTSB MKC86LA193Accident · No injuriesLimited investigationFinal reportCessna T210M · Old Monroe, MOThe PIC had initiated his descent ot his destination arpt when he rptd experiencing eng pblms. The rough running eng finally quit and the PIC made a forced lndg to an open fld. The subsequent lndg encountered a ditch and the nose gear collapsed. Exam of the…NTSB CHI86FA038Accident · Minor injuriesField investigationFinal reportCessna T210M · Highland, MIFifteen minutes after takeoff an eng failure occurred. The plt force landed the acft in a fld but the roughness of the landing surface resulted in the nose and right main gear collapsed. Examination disclosed the exhaust vavle had failed in the #4 cylinder.…NTSB SEA84LA003Accident · No injuriesLimited investigationFinal reportCessna T210M · Seattle, WAAfter takeoff while on a right turnout from rwy 31L, & at about 1000 ft AGL, the eng quit. The plt returned to the arpt & elected to lower the gear when he knew rwy 13L could be reached. However the left main gear failed to lock prior to touchdown & the…