Cessna 210G
NTSB investigations · 50
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 ('2073430')
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 ('2073430')
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 CEN17LA352Accident · No injuriesLimited investigationFinal reportCessna 210G · Hallsville, MOThe total loss of engine power due to a fatigue failure of the engine mixture control cable.NTSB CEN12WA040Accident · 2 fatalForeign investigationCessna 210G · Veracruz, MexicoNTSB NYC08CA089Accident · No injuriesData collectionFinal reportCessna 210G · Bessemer, ALThe pilot's failure to properly secure the airplane before attempting to hand-prop the engine.NTSB NYC06CA174Accident · Minor injuriesData collectionFinal reportCessna 210G · Clayton, NYThe pilot's improper fuel tank selection, which resulted in fuel starvation, and subsequent loss of engine power.NTSB DEN04LA013Accident · No injuriesLimited investigationFinal reportCessna 210G · Meeker, COthe pilot's failure to extend the landing gear. Contributing to the accident was the pilots failure to recognize the gear warning horn during the landing flare.NTSB MIA99LA081Accident · Minor injuriesLimited investigationFinal reportCessna 210G · Lake Placid, FLa total loss of engine power due to an in-flight separation of the crankshaft, caused by a fatigue crack that originated from the aft fillet radius of the No. 2 main journal, resulting in a forced landing in a field and impact with a tree.NTSB CHI98LA091Accident · No injuriesLimited investigationFinal reportCessna 210G · Springfield, ILThe failure of left main landing gear saddle resulting in the pilot's inability to extend the left gear. A factor was maintenance personnel's failure to comply with the related airworthiness directive.NTSB FTW93LA007Accident · No injuriesLimited investigationFinal reportCessna 210G · Little Rock, ARThe partial failure of the landing gear retraction/extension assembly from restricted hydraulic fluid movement through a partially failed main landing gear uplock release valve.NTSB LAX92LA139Accident · No injuriesLimited investigationFinal reportCessna 210G · Livermore, CAThe failure of the left main landing gear saddle.NTSB FTW92FA068Accident · 2 fatalField investigationFinal reportCessna 210G · Darrouzett, TXThe pilot's failure to maintain aircraft control for undetermined reasons. A factor was the dark night.NTSB ATL91LA068Accident · No injuriesLimited investigationFinal reportCessna 210G · Metter, GAThe pilot's failure to extend the landing gear when his attention was diverted by radio conversation.NTSB CHI91DEX01Accident · Minor injuriesFinal reportCessna 210G · Indianapolis, INInadequate maintenance and inspection of the airplane resulting in an engine power loss due to water and fuel contamination. A contributing factor was the dark night.NTSB SEA88LA117Accident · Serious injuriesLimited investigationFinal reportCessna 210G · Bend, OROn arrival in area of planned fuel stop, pax did not feel well. Plt determined that adequate fuel remained to continue to final destination. However, exhaustion occurred 8 miles short of destination. Plt diverted from initial forced lndg site (road) due…NTSB FTW85LA075Accident · Serious injuriesLimited investigationFinal reportCessna 210G · Temple, TXDuring the flt in IMC, plt reported low oil pressure to ATC and declared an emergency. Aprx 4 mins later an engine failure was experienced. Plt stated he broke out of the overcast at aprx 250 ft AGL and the acft impacted a power line during the attempted…NTSB ATL83FID04Accident · No injuriesFinal reportCessna 210G · Chesterfield, VAThe acft collided with a snow bank during landing. The student pilot was making touch & go landings on a traffic flight. The snow banks covered 17 feet on each side of the runway. Runway width was 75 feet. The CFI said the acft drifted to the left during a…NTSB SEA82DYK12Accident · No injuriesFinal reportCessna 210 · Rosenburg, ORThe pilot attempted to hand start the aircraft due to a weak battery. The pilot told passenger to hold the brakes and assumed the passenger knew how, because of his many hours of flight time (as a passenger). When the engine started the aircraft began to move…NTSB LAX82FUG08Accident · 2 fatalFinal reportCessna 210G · Etiwanda, CAThe aircraft struck a ridge at an elevation of about 2000 ft MSL. At the impact point, the terrain sloped upward at an angle of about 35 degrees. The aircraft impacted in a near level flight attitude. The weather at the crash site was not determined. However,…NTSB FTW81DQG02Accident · No injuriesClosedCessna 210 · Abernathy, TXNTSB MKC79FA023Accident · Serious injuriesClosedCessna 210 · Liberal, KSNTSB CHI79FEC10Accident · No injuriesClosedCessna 210 · Ypsilanti, MINTSB MIA79DA038Accident · 3 fatalClosedCessna 210G · Gt Inagua, Burkina FasoNTSB SEA78FA028Accident · 1 fatalClosedCessna 210G · Tumwater, WANTSB CHI77FEG24Accident · No injuriesClosedCessna 210 · Cincinnati, OHNTSB CHI77FET17Accident · No injuriesClosedCessna 210 · Fremont, INNTSB MKC77DCD02Accident · No injuriesClosedCessna 210 · Modale, IANTSB CHI76FEC48Accident · No injuriesClosedCessna 210 · Ypsilanti, MINTSB MIA76AM085Accident · 1 fatalClosedCessna 210G · Livingston, ALNTSB IAD76FKM19Accident · No injuriesClosedCessna 210 · Gastonia, NCNTSB MIA75AM068Accident · 2 fatalClosedCessna 210G · Andytown, FLNTSB OAK75DVA33Accident · Minor injuriesClosedCessna 210 · Sanger, CANTSB CHI74FEE49Accident · Serious injuriesClosedCessna 210G · Wheeling, ILNTSB UNK73X0115Accident · No injuriesClosedCessna 210 · Falmouth, JamaicaNTSB CHI73FEA23Accident · Minor injuriesClosedCessna 210G · Chrisney, INNTSB CHI73FEI03Accident · Minor injuriesClosedCessna 210G · Elyria, OHNTSB CHI72FEE75Accident · No injuriesClosedCessna 210G · Wheeling, ILNTSB NYC72DHM30Accident · No injuriesClosedCessna 210G · Wappingers Fls, NYNTSB NYC72FLJ24Accident · No injuriesClosedCessna 210G · Apex, NCNTSB CHI72FEA20Accident · No injuriesClosedCessna 210G · Laconia, INNTSB DEN72AD003Accident · 2 fatalClosedCessna 210G · Torrington, WYNTSB LAX71AL022Accident · No injuriesClosedCessna 210G · Gila Bend, AZNTSB MIA70A0044Accident · 2 fatalClosedCessna 210G · Valdosta, GANTSB MIA70F0255Accident · No injuriesClosedCessna 210G · Oxford, MSNTSB SEA69D0216Accident · No injuriesClosedCessna 210G · Palouse, WANTSB FTW69D0405Accident · No injuriesClosedCessna 210 · Lubbock, TXNTSB FTW69D0340Accident · No injuriesClosedCessna 210G · Abilene, TXNTSB LAX69F0190Accident · Serious injuriesClosedCessna 210G · Winslow, AZNTSB MIA68D0383Accident · No injuriesClosedCessna 210 · Opa Locka, FLNTSB FTW68F0303Accident · No injuriesClosedCessna 210G · Dallas, TXNTSB MIA68D0265Accident · No injuriesClosedCessna 210 · Okeechobee, FLNTSB FTW67F0539Accident · No injuriesClosedCessna 210 · Atlanta, TX
Back to Cessna 210G