NTSB investigations: Cessna T210N

14 cases on aircraft the registry lists as Cessna T210N, 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

20092026
NTSB investigations: Cessna T210N per year, 2009–2026: 14 cases
20091
20104
20131
20151
20161
20172
20182
20191
20231

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 ('2073456')
      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 WPR23LA174Accident · No injuriesClass 4 · LimitedFinal reportCessna T210N · San Luis Obispo, CAThe pilot’s failure to maintain directional control during the landing roll.May 2, 2023 · N29TR · Substantial damageNTSB WPR19LA195Accident · Serious injuriesClass 3 · LimitedFinal reportCessna T210 · Hurricane, UTMaintenance personnel's improper installation of a throttle cable to the throttle body arm, which resulted in a throttle detachment during takeoff and subsequent loss of power. Contributing to the accident was the inadequate inspection of the throttle…Jul 15, 2019 · N6330N · Substantial damageNTSB CEN18LA142Accident · Minor injuriesLimited investigationFinal reportCessna T210N · Colorado Springs, COThe pilot's inadequate in-flight fuel management, which resulted in a total loss of engine power due to fuel starvation.Apr 15, 2018 · N6988N · Substantial damageNTSB ERA18LA103Accident · No injuriesClass 3 · LimitedFinal reportCessna T210 · Orlando, FLThe improper adjustment of the fuel pump by maintenance personnel, which resulted in an overly rich fuel/air mixture and a total loss of engine power.Mar 13, 2018 · N5382A · Substantial damageNTSB WPR17LA090Accident · Minor injuriesLimited investigationFinal reportCessna T210N · Banning, CAThe pilot's improper energy management during an emergency landing approach that was prompted by an engine power loss. The specific reason(s) for the power loss and the improper energy management could not be determined based on available evidence.Apr 24, 2017 · N6218Y · Substantial damageNTSB GAA17CA131Accident · Minor injuriesData collectionFinal reportCessna T210 · Loveland, COThe pilot's exceedance of the airplane’s critical angle of attack during an attempted go-around, which resulted in an aerodynamic stall.Feb 5, 2017 · N4853U · Substantial damageNTSB GAA16CA337Accident · No injuriesData collectionFinal reportCessna T210 · Buena Vista, COThe pilot's failure to maintain directional control during the landing roll in gusty wind conditions, which resulted in a runway excursion and substantial damage to the firewall.Jun 9, 2016 · N9915Y · Substantial damageNTSB GAA16CA065Accident · Minor injuriesData collectionFinal reportCessna T210N · Avalon, CAThe pilot's delay in aborting the landing, resulting in a runway overrun and nose over.Nov 29, 2015 · N99210 · Substantial damageNTSB WPR13CA271Accident · No injuriesData collectionFinal reportCessna T210N · Salmon, IDThe pilot's decision to land on a wet grass airstrip, which resulted in a main landing gear collapse after a collision with rough terrain.Jun 14, 2013 · N6993N · Substantial damageNTSB WPR11LA038Accident · No injuriesLimited investigationFinal reportCessna T210N · Baggs, WYThe failure of a connecting rod cap retaining bolt during cruise flight, which resulted in a loss of engine power.Nov 6, 2010 · N6179Y · Substantial damageNTSB CEN10FA520Accident · 2 fatalField investigationFinal reportCessna T210 · Mountain Home, ARThe pilot’s decision to continue flight into a known area of heavy rain and his subsequent failure to maintain aircraft control.Sep 7, 2010 · N2081U · Substantial damageNTSB ERA10CA274Accident · No injuriesData collectionFinal reportCessna T210N · Fuquay-Varina, NCThe pilot's improper decision to land with a tailwind resulting in an overrun.Apr 28, 2010 · N110KM · Substantial damageNTSB WPR10CA190Accident · No injuriesData collectionFinal reportCessna T210N · Truckee, CAThe pilot's failure to identify the snow-covered runway, which resulted in an off-runway landing and subsequent collision with a berm.Apr 3, 2010 · N4137C · Substantial damageNTSB CEN09FA241Accident · 1 fatalField investigationFinal reportCessna T210N · Edinburg, TXA loss of engine power for undetermined reasons. Contributing to the accident was the pilot's failure to select a suitable alternate landing site.Apr 9, 2009 · N127TC · Destroyed