Cessna 210M
FAA incident reports · 233
Matched to the registry by N-number and event date, newest first.
Query with SQL
duckdb -csv -c "SELECT report_number, event_date, event_type, city, state, aircraft_make, aircraft_model, aircraft_damage, fatal_injuries, n_number
FROM 'https://openairdocs.org/data/latest/faa_incident_report.parquet'
WHERE aircraft_model_code IN ('2073450')
ORDER BY event_date DESC, report_number 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 report_number, event_date, event_type, city, state, aircraft_make, aircraft_model, aircraft_damage, fatal_injuries, n_number
FROM 'https://openairdocs.org/data/latest/faa_incident_report.parquet'
WHERE aircraft_model_code IN ('2073450')
ORDER BY event_date DESC, report_number 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.
Incident 19860320015969ICessna 210M · Port Arthur, TXHeard a loud sound before engine lost power. Off airport landing. Found number 4 rod broken.Accident 19860227036379ACessna 210M · White Lake Town, MIEngine quit, landed on frozen lake, sheared off nose gear. Crankshaft failed by unwarranted movement of bearing.Incident 19860126031269ICessna 210M · Hillsboro, ORForgot to lower gear for landing. Pilots thought gear warning horn was the stall warning horn.Accident 19860117000989ACessna 210M · Tucker, GAFuel exhausted en route. Struck trees during forced landing.Accident 19851118073269ACessna 210M · Ft Lauderdale, FLLost electrical power. Cracked landing gear hydraulic actuator. Unable manual extension. Gear folded on landing.Incident 19850820050089ICessna 210M · Hopewell, VAPilot forgot to extend gear until just before touchdown. Gear unlocked but not extended on touchdown.Incident 19850715040849ICessna 210M · Salina, KSLeft brake locked just before liftoff. Aborted takeoff, veered and wingtip struck runway. Brake malfunction.Accident 19850706029739ACessna 210M · Detroit, MICollided with a tree after engine quit on final. Excessive play in fuel selector. Fuel vent installed backwards.Accident 19850614026539ACessna 210M · Linden, NJLanded in fuel dump due to fuel exhaustion in tank selected. Did not attempt switching tanks. Gauge malfunction.Accident 19850511016489ACessna 210M · Morrisville, NYThe aircraft was seen at low altitude when the engine failed. Suspect clogged fuel line. Suspect airplane stalled.Incident 19850502062309ICessna 210M · Tulsa, OKPilot made steep turn to change landing runway and fuel starvation ensued. No damage on landing. Had unported fuel.Incident 19850325011789ICessna 210M · Oklahoma City, OKForgot to extend gear for landing. Distracted by traffic.Accident 19850225006709ACessna 210M · Jacksonville, FLAircraft struck trees while returning to airport after engine failure. Extensive fire damage, cause undetermined.Incident 19850127005409ICessna 210M · Bennettsville, SCEnriched mixture to lower higher than normal CHT. Vibration, power loss. Safe landing. Severe lead fouled plugs.Accident 19850115061689ACessna 210M · Stuart, FLSudden power loss during dark night cruise flight. Landed in a field. Number 2 cylinder piston pin had failed.Accident 19841210067929ACessna 210M · Columbus, OHRan out of fuel on ILS approach. Landed in parking lot, struck a chain link fence, nosed over and burned.Incident 19841012061949ICessna 210M · Beeville, TXPilot failed to secure oil cap. Windshied covered with oil. Ran off runway damage to prop, wing tip, nose gear.Accident 19840829044479ACessna 210M · Howell, MIFuel flow fluctuated and went to zero. Engine quit. Landed in a lake.Incident 19840602043139ICessna 210M · White Plains, NYMaking a series of touch and go landings. Did not hear gear warning horn. Landed gear up.Accident 19840404012519ACessna 210 · Tucson, AZRight main landing gear door actuator piston popped out allowing the hydraulic system to deplete itself of fluid.Accident 19840329007669ACessna 210M · Marathon, FLLost control while landing in a gusty crosswind and collapsed the nose gear. Crosswind component excessive.Incident 19840119009529ICessna 210M · Denton, TXEngine quit en route. Landed on a freeway. Engine had two holes in the crankcase from broken connecting rods.Accident 19831230065009ACessna 210M · West Palm Beach, FLAircraft crashed into ocean during back course approach.Accident 19831105059279ACessna 210M · Greensburg, KSLost control circling to land at dark night low ceiling and no ground reference lights. Light rain and fog in area.Incident 19831026068559ICessna 210M · Tupelo, MSLanded gear up. No landing gear malfunctions found.Incident 19830717046809ICessna 210M · Rapid City, SDUnable to lower landing gear. Landed gear up. Found a sticking door solenoid and a faulty valve assembly selector.Incident 19830225013469ICessna 210M · Austin, KYEngine quit while en route IFR. Landed in a open field. Engine crankshaft had broken.Accident 19830207002729ACessna 210M · Farmington, NMLoaded with 2 inch ice. Landed hard on approach end of runway. Impact collapsed the gear. Icing forecast not given.Incident 19830115005639ICessna 210M · Laverne, CABounced and porpoised on landing. Snapped nose gear fork and bent propeller.Incident 19830101007342ICessna 210M · Wildwood, NJPilot landing on runway 32 collided with a DHC6, N103AC,taking off. N103AC failed to give right of way.Accident 19821215067039ACessna 210 · Defiance, OHStruck trees while trying to make runway visually after NDB approach. Failed to use proper IFR procedures.Incident 19820910055479ICessna 210M · Okeechobee, FLPilot struck an unmarked tire used to make tie down ropes in tie down area. Grass to high to see tire.Accident 19820821046759ACessna 210M · Holly Springs, MSAircraft crashed during emergency landing after engine quit due to fuel exhaustion.Incident 19820813038269ICessna 210M · Sioux City, IAAll efforts failed to dislodge stuck nose gear. Landed nose gear up. Cause not reported.Accident 19820223005569ACessna 210M · FLEngine quit on over-ocean flight. Ditched south of grand bahama island. Possible vapor lock on tank run out.Incident 19820107003429ICessna 210M · Robstown, TXZa engine failure from lack of fuel. Pilot did not check fuel on board before flight.Incident 19811027069549ICessna 210M · Hattiesburg, MSPilot forced to land after striking electrical wire, severing fuel tank feed line.Incident 19810819065929ICessna 210M · Garden City, KSNo landing gear indications. Landed gear up. Found lower nose gear strut collar broken.Incident 19810729062759ICessna 210M · Longview, TXNose gear collapsed on rotation for takeoff. Skid 750 ft on takeoff. Maintenance found no discrepancies.Incident 19810404023969ICessna 210M · Louisville, KYNose gear failed to extend due to a plugged hydraulic line.Accident 19810308008489ACessna 210M · Ivanhoe, MNEngine quit on final. Crash-landed short of farm strip. Found fuel selector on empty tank. Fuel gauge showed fuel.Incident 19810212003639ICessna 210M · Enderlin, NDPilot forgot to lower the gear prior to landing.Incident 19801231089679ICessna 210M · Marion, INZa pilot flew into forecast icing conditions, iced up, lost instruments was vectored to an airport.Incident 19801231088269ICessna 210M · Toledo, OHLost all electrical power at night on instruments. Landed wheels up in snow covered field. Starter solenoid defect.Accident 19801207072709ACessna 210M · Stuart, FLRough engine over ocean. Engine quit, ditched. Airplane sank. Engine problem unknown. Had troubled history.Incident 19800817081579ICessna 210M · Forrest City, ARNose gear retracted on takeoff roll. Pilot failed to check gear handle position.Incident 19800803084539ICessna 210M · Phoenix, AZPilot landed gear up. Gear up warning horn inoperative when throttle was retarded.Incident 19800717061109ICessna 210M · San Antonio, TXTire seperated from wheel due to faulty main wheel hub.Incident 19800408048099ICessna 210 · Minot, NDAircraft ran out of fuel, resulting in forced landing.Incident 19800220003359ICessna 210M · Austin, TX
Back to Cessna 210M