Cessna T210R
NTSB investigations · 18
Matched to the registry by N-number and event date, newest first.
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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c.\"mKey\" = a.case_mkey
WHERE a.aircraft_model_code IN ('2073459')
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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c."mKey" = a.case_mkey
WHERE a.aircraft_model_code IN ('2073459')
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 GAA25WA122Accident · No injuriesClass 5 · ForeignCessna T210R · El Perico, MexicoNTSB WPR25LA094Accident · No injuriesClass 3 · LimitedPreliminary reportCessna T210R · Flagstaff, AZOn February 16, 2025, about 1445 mountain standard time, a Cessna T210R, N105DF, was substantially damaged when it was involved in an accident near Flagstaff, Arizona. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of…NTSB WPR22LA248Accident · No injuriesClass 3 · LimitedFinal reportCessna T210R · Stanley, IDThe pilot’s failure to provide adequate braking during a tailwind landing, which resulted in a runway excursion.NTSB ERA22FA076Accident · 2 fatalClass 3 · FieldFinal reportCessna T210R · Grove City, PAA catastrophic engine failure due to oil starvation after the pilot’s failure to secure the oil filler cap before flight. Contributing to the accident was the pilots’ decision to continue the flight following the oil loss event and precautionary landing.NTSB CEN11CA675Accident · No injuriesData collectionFinal reportCessna T210R · Lamar, MOThe pilot's inadequate compensation for the wind condition, resulting in a runway excursion.NTSB DFW07LA082Accident · No injuriesLimited investigationFinal reportCessna T210R · Boerne, TXThe pilot of the other airplane's failure to maintain proper spacing during approach to landing and subsequent go-around, which resulted in a midair collision.NTSB SEA07FA061Accident · 1 fatalField investigationFinal reportCessna T210R · Rexburg, IDThe loss of engine power due to the contamination of the fuel manifold valve, and the pilot's continued operation of the airplane with known maintenance discrepancies.NTSB LAX98LA291Accident · Minor injuriesLimited investigationFinal reportCessna T210R · Buckeye, AZthe pilot's delayed response in recovering from a bounced landing combined with his delayed decision to abort the landing. The pilot's inadequate compensation for tailwind conditions and inadvertently raising the flaps to 10 degrees were factors in this…NTSB CHI95FA337Accident · 1 fatalField investigationFinal reportCessna T210R · Iowa City, IAfuel exhaustion as a result of the pilot's inadequate preflight and lack of familiarity with the airplane. Factors involved were the bright night, trees and transmission wires.NTSB NYC94LA175Accident · No injuriesLimited investigationFinal reportCessna T210R · Tunkhannock, PAUse of improper procedures during a short field landing which resulted in an overrun and noseover.NTSB ATL94LA053Accident · No injuriesLimited investigationFinal reportCessna T210R · Baxley, GADamage to the crankshaft internal oil tube by other maintenance persons during the engine overhaul that resulted in oil starvation.NTSB SEA93FA020Accident · 1 fatalField investigationFinal reportCessna T210R · Boise, IDProper altitude was not maintained. Factors to the accident were: fog, dark night conditions, and improper IFR procedures.NTSB FTW92GA011Accident · No injuriesFinal reportCessna T21OR · Lordsburg, NMThe pilot's improper recovery from a bounced landing. Factors were the pilot's excessive airspeed and improper flare technique.NTSB MKC90FA026Accident · Serious injuriesField investigationFinal reportCessna T210 · Columbia, MOAn engine compartment fire due to a missing turbocharger exhaust duct and tailpipe assembly. The clamp used to retain the tailpipe assembly to the turbocharger was also missing, contributing factor(s) was: the soft terrain.NTSB BFO88IA065Incident · No injuriesIncident investigationFinal reportCessna T210R · Washington, DCImproper maintenance resulting in the routing of wire which caused an electrical short and inflight smoke.NTSB MIA88LA188Accident · Minor injuriesLimited investigationFinal reportCessna T210R · Tampa, FLThe plt stated that on final apch to Tampa international airport, he reduced power, put the gear down and, as he tried to add power, none was available. During an attempted forced landing, he hit the top of an office trailer and a guy wire before coming to…NTSB DEN88LA038Accident · No injuriesLimited investigationFinal reportCessna T210R · Bismarck, NDThe plt was attempting to takeoff at dusk on a gravel road. The acft veered off of road and hit a ditch.NTSB MKC85FA070Accident · 2 fatalField investigationFinal reportCessna T210R · Eli, NEThere were no witnesses to the takeoff or the accident. A flt plan was not filed and no radar data on the flt was found. The owner of N6101U estimated the takeoff time to be 2130 CST, mar. 12 and the plt told the owner he was going to Utah. The wreckage of…
Back to Cessna T210R