Cessna 210F
NTSB investigations · 45
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 ('2073418')
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 ('2073418')
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 CEN17LA212Accident · No injuriesLimited investigationFinal reportCessna 210F · Anoka, MNThe failure of the landing gear to fully extend due to insufficient hydraulic fluid in the hydraulic system as a result of inadequate maintenance by the airplane owner.NTSB ERA16FA189Accident · 1 fatalField investigationFinal reportCessna 210 · Wantage, NJA collision with terrain for reasons that could not be determined as the investigation did not reveal any postaccident anomalies with the airplane or pilot.NTSB WPR15FA166Accident · 1 fatalField investigationFinal reportCessna 210F · Pleasanton, CAThe pilot’s continued visual flight into instrument flight rules conditions, which resulted in his failure to maintain sufficient clearance from rising terrain.NTSB CEN12CA064Accident · No injuriesData collectionFinal reportCessna 210F · Phillipsburg, KSThe pilot’s improper recovery from a bounced landing.NTSB WPR10LA248Accident · Minor injuriesLimited investigationFinal reportCessna 210 · Arbuckle, CAInsufficient clamping force to the connecting rod bolt, which resulted in looseness in the connecting rod bearing area that led to the fatigue fracture of the connecting rod and a subsequent loss of engine power.NTSB LAX07CA183Accident · No injuriesData collectionFinal reportCessna 210F · Denton, MTThe pilot's decision to abort the landing with insufficient runway available to gurantee obstruction clearance.NTSB DFW06LA104Accident · Minor injuriesLimited investigationFinal reportCessna 210F · Lubbock, TXAn in-flight electrical fire for undetermined reasons. A contributing factor was the lack of suitable terrain for the forced landing.NTSB ATL02WA109Accident · 1 fatalForeign investigationCessna 210F · Grand Cayman, Cayman IslandsNTSB ATL02LA070Accident · No injuriesLimited investigationFinal reportCessna 210 · Naples, FLTotal loss of engine power due to improper maintenance by company maintenance personnel which allowed the mixture control linkage to disconnect in flight which resulted in an emergency descent to landing into unsuitable terrain.NTSB ANC01WA043Accident · 1 fatalForeign investigationCessna 210F · Teslin, CanadaNTSB LAX00LA339Accident · No injuriesLimited investigationFinal reportCessna 210E · Holbrook, AZThe lack of elevator control during final approach, for undetermined reasons, that resulted in a hard landing.NTSB MIA97LA182Accident · Minor injuriesLimited investigationFinal reportCessna 210F · Waycross, GAthe private pilot's failure to maintain airspeed, while maneuvering in an attempt to reverse direction, which resulted in an inadvertent stall, and subsequent in-flight collision with terrain.NTSB FTW95LA385Accident · No injuriesLimited investigationFinal reportCessna 210F · Montrose, COThe pilot's inattentiveness to the low fuel supply and his failure to switch fuel tanks in a timely manner. A factor was the lack of suitable terrain for the forced landing.NTSB LAX93LA357Accident · No injuriesLimited investigationFinal reportCessna 210F · Chino, CAthe pilot's inadequate compensation for the downdraft and his failure to maintain the proper glidepath.NTSB LAX93LA009Accident · No injuriesLimited investigationFinal reportCessna 210F · Buena Park, CAFailure of the pilot to adequately detect water contamination in the airplane's fuel system during preflight.NTSB ATL92LA112Accident · No injuriesLimited investigationFinal reportCessna 210F · Manteo, NCThe pilot's inadequate emergency procedures, in that he failed to note the discharge of electrical power on the ammeter, and his loss of directional control during the off airport landing. Factors were the disabled alternator and a low cloud ceiling.NTSB MKC90LA086Accident · Minor injuriesLimited investigationFinal reportCessna 210 · Eden Prairie, MNDirectional control was not maintained by the pilot in command.NTSB SEA86LA201Accident · Minor injuriesLimited investigationFinal reportCessna 210F · Lages, NVThe plt was unable to divert around numerous thunderstorms along in his flight path. Subsequently, he made a precautionary landing on a soft, dry lake bed were the aircraft nosed over.NTSB NYC85FHD02Accident · Serious injuriesFinal reportCessna 210F · Princeton, NJThe acft collided with trees & crashed after overflying mercer cty arpt on a special VFR clearance. The acft had descended to 900 ft to overfly mercer and was attempting to proceed VFR to Princeton arpt to land when it contacted trees and crashed. The wx was…NTSB LAX80FUM03Accident · Serious injuriesClosedCessna T210F · El Cajon, CANTSB MIA78FLA31Accident · No injuriesClosedCessna 210 · St.Augustine, FLNTSB DEN77FTM08Accident · Minor injuriesClosedCessna 210 · Brigham City, UTNTSB SEA75FTA19Accident · Minor injuriesClosedCessna 210F · Pompeys Pillar, MTNTSB CHI75FEC36Accident · No injuriesClosedCessna 210F · Howell, MINTSB SEA75FTA11Accident · No injuriesClosedCessna 210F · Ballatine, MTNTSB MIA75FLD13Accident · No injuriesClosedCessna 210F · Orlando, FLNTSB MIA74FKG79Accident · Minor injuriesClosedCessna 210T · Albany, GANTSB IAD74FID28Accident · No injuriesClosedCessna 210F · Williamsburg, VANTSB DEN74FTM11Accident · Serious injuriesClosedCessna 210F · Cedar City, UTNTSB IAD73FKW26Accident · No injuriesClosedCessna 210 · Athens, TNNTSB MKC73AK054Accident · Serious injuriesClosedCessna 210F · Manhattan, KSNTSB FTW73FPM05Accident · No injuriesClosedCessna 210F · Mannford, OKNTSB MKC72FCG14Accident · Serious injuriesClosedCessna 210F · Bolivar, MONTSB FTW70D0175Accident · Minor injuriesClosedCessna 210F · Dequeen, ARNTSB FTW69D0048Accident · Minor injuriesClosedCessna 210 · Mountain Home, ARNTSB CHI68A0083Accident · 1 fatalClosedCessna 210F · Bellville, OHNTSB DEN68A0039Accident · 3 fatalClosedCessna 210 · Eureka, UTNTSB NYC68D0366Accident · No injuriesClosedCessna 210F · Slocum, RINTSB MIA68D0338Accident · No injuriesClosedCessna 210F · Opa Locka, FLNTSB MKC68A0033Accident · No injuriesClosedCessna 210 · Iola, KSNTSB LAX68A0012Accident · 2 fatalClosedCessna 210F · Tujunga, CANTSB LAX67D0338Accident · No injuriesClosedCessna 210 · Parker, AZNTSB CHI67F0535Accident · No injuriesClosedCessna 210F · Romeo, MINTSB MIA67A0074Accident · 1 fatalClosedCessna 210F · Muscle Shoals, ALNTSB MKC67D0349Accident · Minor injuriesClosedCessna 210F · Fort Dodge, IA
Back to Cessna 210F