NTSB investigations: Cessna 210, CO
20 cases on aircraft the registry lists as Cessna 210. 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
| 1964 | 2 |
|---|---|
| 1965 | 1 |
| 1966 | 1 |
| 1971 | 1 |
| 1975 | 1 |
| 1976 | 1 |
| 1984 | 1 |
| 1987 | 2 |
| 1990 | 1 |
| 1992 | 1 |
| 1993 | 1 |
| 1996 | 1 |
| 1997 | 2 |
| 2007 | 1 |
| 2008 | 1 |
| 2009 | 1 |
| 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\" = 'CO' 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 ('2073402'))
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" = 'CO' 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 ('2073402'))
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 CEN17LA162Accident · No injuriesLimited investigationFinal reportCessna 210 · Salida, COThe pilot’s inadequate fuel management, which resulted in a total loss of engine power due to fuel starvation.NTSB CEN10LA032Accident · Minor injuriesLimited investigationFinal reportCessna 210 · Walsh, COA partial loss of engine power due to failure of the No. 2 cylinder as a result of the failure of the repair facility to properly torque the lower four nuts on the cylinder.NTSB DEN08LA153Accident · No injuriesLimited investigationFinal reportCessna 210 · Pagosa Springs, COThe failure of the landing gear to extend for undetermined reasons.NTSB DEN08LA014Accident · No injuriesLimited investigationFinal reportCessna 210 · Canon City, COThe failure of the engine throttle cable resulting in a lack of engine power when commanded.NTSB FTW97LA307Accident · Serious injuriesLimited investigationFinal reportCessna T210 · Eagle, COwater contamination of the fuel, which led to a total loss of engine power and a forced landing. Factors relating to the accident were: the delay in refueling the aircraft by the FBO, which allowed condensation to form in the fuel tanks, and inadequate…NTSB FTW97LA239Accident · No injuriesLimited investigationFinal reportCessna 210 · Peyton, COFailure of both pilots to assure the landing gear was down and locked.NTSB FTW96LA334Accident · No injuriesLimited investigationFinal reportCessna 210 · Pueblo, COimproper routing of the nose landing gear hydraulic line by unknown maintenance personnel, allowing it to chafe on the nose wheel and develop a leak, which resulted in an inability to obtain a down-and-locked condition of the landing gear.NTSB FTW94LA029Accident · No injuriesLimited investigationFinal reportCessna 210 · Monte Vista, COFailure by the pilot in command to follow procedures and directives to lower the landing gear prior to landing.NTSB DEN93FA021Accident · 3 fatalField investigationFinal reportCessna 210 · Aurora, COCollision with terrain when the pilot inadvertently flew into fog while conducting a visual approach. Factors were: inaccurate weather evaluation by the pilot and lack of familiarity with the geographic area.NTSB DEN91LA014Accident · Minor injuriesLimited investigationFinal reportCessna T-210-M · Buena Vista, COThe pilot misjudged the fuel supply resulting in fuel exhaustion.NTSB DEN88LA018Accident · No injuriesLimited investigationFinal reportCessna 210 · Greeley, COThe CFI was instructing the private rated plt in simulated forced landings. The plt reported that after a full stop landing, the aircraft would not turn properly to the right, and she suspected brake system failure. The CFI took control and attempted to taxi…NTSB DEN87FA188Accident · 1 fatalField investigationFinal reportCessna 210 · Coaldale, COThe ATP rated pilot was an airline captain on a Boeing 727 aircraft. However, the pilot had accumulated a total of only 140 hours in single engine aircraft with 20 hours in the Cessna 210. Moderate to severe turbulence had been forecast and reported in the…NTSB DEN84LA067Accident · No injuriesLimited investigationFinal reportCessna 210 · Grand Junction, COThe plt stated he touched down too hard, bounced & that he over-corrected causing the acft to land hard again collapsingthe nose gear.NTSB DEN76FTE64Accident · No injuriesClosedCessna 210 · Loveland, CONTSB DEN76DTE44Accident · No injuriesClosedCessna 210 · Blanca, CONTSB DEN71FXD48Accident · Minor injuriesClosedCessna 210 · Boulder, CONTSB DEN67D0184Accident · No injuriesClosedCessna 210 · Seibert, CONTSB DEN65D0102Accident · No injuriesClosedCessna 210 · Sterling, CONTSB UNK65X0284Accident · No injuriesClosedCessna 210 · Denver, CONTSB UNK64X1627Accident · No injuriesClosedCessna 210 · Lamar, CO