NTSB investigations: Cessna 210-5(205)

6 cases on aircraft the registry lists as Cessna 210-5(205), where the sequence of events included Collision with terr/obj (non-CFIT). 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

20082026
NTSB investigations: Cessna 210-5(205) per year, 2008–2026: 6 cases
20081
20091
20111
20121
20131
20161

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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073202')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.case_mkey = x.case_mkey AND s.aircrafts_position = x.position AND s.\"tier2Number\" = '470' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE \"isDefiningEvent\")))
  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.

NTSB GAA16CA514Accident · No injuriesData collectionFinal reportCessna 205 · Ellington, CTThe pilot's exceedance of the airplane's critical angle-of-attack during the initial climb after an attempted go-around, which resulted in an aerodynamic stall.Sep 26, 2016 · N8433Z · Substantial damageNTSB CEN13LA565Accident · No injuriesLimited investigationFinal reportCessna 210-5(205) · Weatherford, OKThe pilot’s inadequate preflight inspection and fuel planning, which resulted in fuel exhaustion and a total loss of engine power during descent.Sep 25, 2013 · N8472Z · Substantial damageNTSB WPR12CA284Accident · Minor injuriesData collectionFinal reportCessna 210-5 · West Glacier, MTThe pilot elected to abort the takeoff without sufficient runway available to land and stop the airplane. Contributing to the accident was the illusion created by the rising terrain, which influenced the pilot's decision to abort the takeoff.Jul 2, 2012 · N8450Z · Substantial damageNTSB WPR11FA348Accident · Minor injuriesField investigationFinal reportCessna 210-5(205) · Darby, MTThe fatigue failure of the aluminum air intake duct, which resulted in material being ingested into the engine cylinders and a subsequent loss of engine power during cruise flight.Jul 22, 2011 · N8427Z · Substantial damageNTSB ERA09CA366Accident · Minor injuriesData collectionFinal reportCessna 210-5(205) · Porterdale, GAThe loss of engine power due to fuel exhaustion as a result of the pilot's use of improper fuel caps. Contributing to the accident was the pilot’s selection of an unsuitable area for landing.Jun 24, 2009 · N8272Z · Substantial damageNTSB WPR09CA006Accident · No injuriesData collectionFinal reportCessna 210-5(205) · Payson, UTThe total loss of engine power during cruise flight for undetermined reasons. Contributing to the accident were a dark night and a cherry orchard at the location where the pilot executed the forced landing.Oct 9, 2008 · N8374Z · Substantial damage