Cessna 337A
FAA incident reports · 66
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 ('2075704')
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 ('2075704')
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 20210329009189ICessna 337A · Byars, OKThe airplane departed pauls valley municipal airport (pvj) for a short flight to test out the new ADS-B system installation and practice maneuvers. After about an hour into flight, both engines started losing power simultaneously. The pilot set the airplane…Incident 20170617020569ICessna 337A · Sparta, TNTwo pilots were onboard, owner and friend, which also owns a CE-337. The registered owner was flying the aircraft. (Signed off for solo flight in CE-337) The only qualified person onboard was the pilot rated passenger and has owned the same type of aircraft…Incident 20090325004439ICessna 337A · Norfolk, VA(-23) Pilot stated landing gear down was selected five miles out on final approach to runway 10, pvg, Hampton Roads Executive Airport, portsmouth, Virginia. A down and locked landing gear indication on the instrument panel was observed and the pilot had a…Accident 20080517837689ACessna 337A · West Creek, NJ(-23)On may 17, 2009, at or about 12:45 easter daylight savings time, a Cessna CE-377A, register as N5382S, owned and piloted by a commercial pilot, was destroyed when it impacted terrain in dense wooded pinelands, approximately 200 meters southeast of runway…Incident 20050513010489ICessna 337A · St James City, FL(-23) On may 13, 2005, at 1715 EST, a Cessna 337A, N6244F, registered to the pilot [privacy data omitted] continued landing at the end of runway 27 and colided with 6 foot high mulch banks at a Private Airport on pine island, st. James city, Florida, while on…Accident 20000228013249ACessna 337A · Prince Frederic, MD(-23) N53HS was observed approaching from the north low level at a high rate of speed. Turned right to where wings were vertical and descended into trees. Witnesses say the a/c was operating normally. There was no fire.Incident 19991107032899ICessna 337A · Olney, TX(-5) The pilot had a flight instructor sign off to fly the aircraft solo. The pilot stated that his before landing check was incomplete due to the attention he was directing to his new garmon global positioning system. When he selected gear down, the handle…Incident 19980504013929ICessna 337A · Lakeville, MNNarrative: pilot landed gear up. Pilot was preoccupied with cross-wind landing. Airman landed with landing gear in the up position. Numerous FAR violations concerning aircraft maintenance records. [privacy data omitted]Incident 19980311007579ICessna 337 · Cahokia, ILNarrative: during landing at Parks airport (cps) 30L Mr. O'toole landed gear up. He stated that he checked the landing gear green light but looked at the auto-pilot on green light instead. He then landed at cps gear up. [privacy data omitted]Incident 19971029038439ICessna 337A · Kramer Jct, CANarrative: a Cessna, serial number 337Z, N75AB departed California city airport for hesperia, CA. Enroute front engine quit, pilot made a precautionary landing on a dirt road by highway 395, 21 miles north of Kramer junction. Upon inspection a fuel line was…Accident 19920731028589ACessna 337A · Ruidoso, NMCrashed into hilly terrain circling. For night landing.Incident 19920704033579ICessna 337A · Juneau, AKNR1 engine running rough. Shut engine down. Landed safely.Incident 19920421015819ICessna 337A · Watertown, NYMaking touch and go landings. Pilot forgot to lower gear. Landed gear up. Distracted by strong crosswinds.Incident 19911229057999ICessna 337A · Forney, TXPilot lost directional control on takeoff roll. Veered off runway. Hit a barbed wire fence.Accident 19911008045469ACessna 337A · Snohomish, WASet crossfeed for simulated engine out practice. Forgot restore normal fuel operations tank dry. Lost both engines.Accident 19910827036819ACessna 337 · Urbana, OHLost rear engine on initial takeoff unknown until climbout. Settled into ground impact. Rear engine on empty tank.Incident 19910115006079ICessna 337A · Palmdale, CAUnable to switch fuel tanks. Precautionary landing. Found fuel selector cable binding.Incident 19900709037969ICessna 337A · Alamosa, COEngine went to idle RPM on spray run. Forced landing in field. Found induction air hose had collapsed.Incident 19890622039889ICessna 337A · Gulfport, MSStruck a kite on descent to final approach. String caught in prop. Shut engine down and landed safely. Minor damageIncident 19890416021489ICessna 337A · Oceanside, CARear engine lost power on takeoff. Aborted. Ground looped to slow aircraft. Cause of engine failure undetermined.Accident 19881124051789ACessna 337A · Weatherford, TXObserved in slow flight at low altitude. Wings wobbled, nose pitched down. Struck ground nose and left wing low.Accident 19881001042459ACessna STC337 · Bellingham, WAStalled in steep climbing downwind turn on takeoff. Near vertical impact. Had robertson stol kit installed.Accident 19871121066519ACessna 337A · Kankakee, ILBounced on landing. Came down on nose gear which collapsed. Skidded off runway. Pilot states a go around was neededIncident 19870321036729ICessna 337A · Granite City, ILThe aircraft landed with the wheels retracted. Report indicates pilot error.Incident 19870209026749ICessna 337A · Lubbock, TXBoth engines quit on final. Aircraft was landed in a field. Fuel remained in 2 tanks to inspect fuel selector.Accident 19860228003959ACessna 337A · Key Biscayne, FLBypassed nassau. Thought he had enough fuel to reach Miami. Ran out of fuel. Ditched 1 mile east of cape, Florida.Accident 19850217008029ACessna 337A · Belen, NMTakeoff and landings on both runways 3 and 21. Forgot to extend landing gear, landed gear up.Accident 19850114008109ACessna 337A · Jacksonville, FLLast reported position was over water with no significant weather. Presumed to be fatally injured.Accident 19840803038149ACessna 337A · Ocean Springs, MSBounced, tried go around, became airborne, spun into hangar, hit airplane in hangar. Both aircraft burned.Accident 19840317006219ACessna 337A · Wales, WIRan out of fuel at night during vectors for an ILS approach. Struck trees on the forced landing.Incident 19830706042539ICessna 337A · Sturgis, MILanded gear up.Accident 19830704030009ACessna 337A · Oxford, ARCrash occurred during emergency landing after both engines quit from fuel exhaustion.Incident 19830228013109ICessna 337A · Atlanta, TXPilot in a hurry neglected to lower landing gear on fast landing.Accident 19820619023289ACessna 337A · Stuart, FLBoth engines malfunctioned over ocean and pilot ditched. Pilot attributed engine failure to fuel contamination.Incident 19820426016899ICessna 337A · Washington, VABoth engines quit at cruise altitude. Pilot switched to main tanks and restarted enginesAccident 19810802046809ACessna 337 · Pembroke, NYEngines quit due to fuel vents being plugged. Aircraft damaged during emergency landing.Incident 19810626061839ICessna 337A · San Diego, CAPilot pulled circuit breaker to silence gear warning during photo flight. Failed to reactivate. Gear stayed down.Accident 19810516026729ACessna 337 · Melvin, TXElected to land on a road due to low clouds and fog. Wing hit a fence post, cartwheeled aircraft.Accident 19810515069399ACessna 337A · Evant, TXAircraft crashed in field. Thunderstorms had been reported at approximate time of accident.Incident 19800715061149ICessna 337A · Greenville, SCNose gear collapsed on landing. Cause undetermined.Accident 19800616022539ACessna 337A · Aledo, TXReported engine problem. Both found feathered. Indicates fuel starvation from mismanagement of fuel selectors.Incident 19800614052919ICessna 337A · Trenton, NJLanded on airport gear up. Had misidentified failing engine and shut down the good one.Incident 19800424046549ICessna 337A · Jekyll Island, GAPilot reported near miss with buzzard about 50 feet above runway on final. Touched down hard, blew tire.Accident 19800401007549ACessna 337A · Madison, MSRear engine quit in pattern. Propeller and belly hit runway, landing with gear up. Tried go around. Hit trees.Accident 19790731023499ACessna 337 · Prewitt, NMBoth engines stopped due to fuel exhaustion. Hit tree on wheels up landing on a road. Narcotics found on boardIncident 19790629017879ICessna 337A · Morrisville, NCNose gear collapsed on roll out. Found weak nose gear structureAccident 19790601028759ACessna 337A · Estacada, ORMade gear-up lndg. Believed gear horn was stall warn horn. Factors; pilot fatigue, careless.Accident 19790514011829ACessna 337 · Kissimmee, FLBoth engines quit while on base leg. Aircraft struck trees. Flipped over, and burned. Cause undetermined.Accident 19770928032959ACessna 337G · Wilmot, WIAccident 19770924027709ACessna 337A · Gonzales, LA
Back to Cessna 337A