NTSB investigations: Cessna T210N, IL
14 cases on aircraft the registry lists as Cessna T210N. 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 |
|---|---|
| 1986 | 1 |
| 1987 | 1 |
| 1988 | 1 |
| 1989 | 1 |
| 1990 | 1 |
| 1993 | 1 |
| 1995 | 1 |
| 1997 | 1 |
| 2000 | 2 |
| 2002 | 2 |
| 2017 | 1 |
Where
Latest 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.\"eventStateOrRegion\" = 'IL' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073456'))
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."eventStateOrRegion" = 'IL' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073456'))
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 CEN18LA031Accident · No injuriesLimited investigationFinal reportCessna T210N · Grayslake, ILThe failure of the No. 4 connecting rod due to inadequate oil lubrication for reasons that could not be determined because the postaccident engine examination did not reveal any anomalies that would have caused a lack of lubrication.NTSB CHI02LA136Accident · Minor injuriesLimited investigationFinal reportCessna T210N · Lake in Hills, ILIt was not possible for the pilot to land the airplane at a proper touchdown point during the aborted takeoff and unsuitable terrain was encountered off the end of the runway. Factors associated with the accident were a proper climb rate was not achieved…NTSB CHI02LA066Accident · No injuriesLimited investigationFinal reportCessna T210N · Chicago, ILthe pilot's failure to maintain aircraft control after takeoff. Factors relating to the accident were the pilot excessive rotation during takeoff and the crosswind.NTSB CHI01LA037Accident · Serious injuriesLimited investigationFinal reportCessna T210N · Kankakee, ILThe unsuitable terrain encountered by the pilot during the emergency landing. Factors to the accident were the loss of engine power due to the failure of the crankshaft, the pilot misjudging the descent glide path, and the presence of the highway embankment…NTSB CHI01LA005Accident · No injuriesLimited investigationFinal reportCessna T210N · Cahokia, ILaircraft control not being maintained by the inattentive pilot during the taxi. A factor to the accident was the soft terrain condition.NTSB CHI97FAMS1Accident · 2 fatalMissing aircraftFinal reportCessna T210N · Chicago, ILUndetermined.NTSB CHI95LA096Accident · No injuriesLimited investigationFinal reportCessna T210N · Rockford, ILA disconnect of the alternator belt, and failure of the pilot to attain a down and locked condition of the gear with the emergency extension system.NTSB CHI93LA343Accident · No injuriesLimited investigationFinal reportCessna T210N · Lake In The Hil, ILChafing of a fuel system line.NTSB CHI90LA151Accident · No injuriesLimited investigationFinal reportCessna T210N · Wheeling, ILPilot-in-command's failure to obtain a proper flare attitude in the aircraft prior to touchdown.NTSB CHI89FA038Accident · 2 fatalField investigationFinal reportCessna T210N · Springfield, ILThe pilot's improper IFR procedure during an ILS approach in below minimum conditions, and the pilot's failure to proceed to an alternate destination. Contributing factors were the adverse weather conditions.NTSB CHI88FA039Accident · 1 fatalField investigationFinal reportCessna T210N · Bedford Park, ILDrg an arrival to chicago midway arpt on a cold night, the plt rprtd he was having trouble with a sticky throttle. Subsequently, he made an emergency transmission & said he was 'going in.' Witnesses saw the acft in a descent before it crashed. One witness…NTSB CHI88LA017Accident · No injuriesLimited investigationFinal reportCessna T210N · Sugar Grove, ILWhile descending for landing the aircraft experienced total power failure due to fuel exhaustion. An emergency landing was made on a road and on short final, the aircraft collided with power lines which ran along the south side of the road. According to the…NTSB CHI87LA027Accident · No injuriesLimited investigationFinal reportCessna T210N · Kankakee, ILThe plt overran rwy 22 after landing downwind during intrument weather conditions. Fss had advised the plt of a NOTAM that rwy 4 ILS was out of service due to construction. However, another acft which landed on rwy 4 about 15 minutes prior to the accident…NTSB CHI83LA053Accident · No injuriesLimited investigationFinal reportCessna T210 · Frankfort, ILAfter touchdown the right wing of the aircraft suddenly lifted, directional control was lost and the aircraft struck a row of trees.