Cessna 337F
NTSB investigations · 24
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 ('2075725')
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 ('2075725')
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 WPR20LA245Accident · 1 fatalClass 3 · LimitedFinal reportCessna 337 · Ennis, MTThe pilot-in-command’s failure to maintain sufficient airspeed while attempting an evasive maneuver from a boxed canyon, which resulted in an aerodynamic stall/spin and impact with mountainous terrain. Contributing to the accident was the pilot-in-command’s…NTSB CEN18LA246Accident · No injuriesLimited investigationFinal reportCessna 337 · Baldwin City, KSThe loss of hydraulic accumulator pressure for reasons that could not be determined, which prevented the propeller from unfeathering, and the pilot's improper decision to attempt a go-around, which resulted in an off-airport landing and the airplane impacting…NTSB GAA15CA228Accident · No injuriesData collectionFinal reportCessna 337F · Danbury, CTThe pilot's failure to maintain pitch control during the landing, resulting in a hard landing, nose gear collapse, runway excursion, and collision with terrain.NTSB ERA15LA224Accident · No injuriesLimited investigationFinal reportCessna 337 · Melbourne, FLThe pilot’s failure to maintain directional control while taxiing as a result of his impairment due to alcohol ingestion.NTSB CEN09LA502Accident · Serious injuriesLimited investigationFinal reportCessna 337F · Frankfort, MIThe pilot intentionally attempting to take off with an inoperative engine, which lead to the airplane's inability to maintain airspeed in the initial climb, resulting in a stall and impact with trees.NTSB DEN03LA140Accident · No injuriesLimited investigationFinal reportCessna 337F · Las Cruces, NMLack of adequate power from the rear engine for undetermined reasons and the pilot's failure to maintain aircraft control during take-off. A contributing factor to the accident was the low altitude.NTSB MIA95FA087Accident · 2 fatalField investigationFinal reportCessna 337F · Vero Beach, FLThe pilot's failure to avoid a thunderstorm. The thunderstorm was a factor.NTSB LAX92FA033Accident · 3 fatalField investigationFinal reportCessna 337F · Bullhead City, AZThe pilots failure to maintain a proper descent rate and to adequately judge the above ground altitude of the aircraft during the approach. Factors in the accident were: 1) the dark night conditions, 2) the pilot's degraded visual perceptive ability, and 3)…NTSB NYC90LA091Accident · No injuriesLimited investigationFinal reportCessna O337F · Brant, NYThe pilot's premature rotation and failure to obtain airspeed.NTSB FTW87LA019Accident · Serious injuriesLimited investigationFinal reportCessna 337 · New Orleans, LADuring an instrument approach and the subsequent missed approach, both engines failed due to fuel starvation. It has been determined that as much as six gallons of fuel was contained in the auxillary tanks at the time of the accident but that none was…NTSB ATL86LA191Accident · No injuriesLimited investigationFinal reportCessna 337F · Cherry Point, NCWhen the gear selector handle was placed in the up position the gear unsafe warning horn sounded. The plt reported a stall warning horn to ATC and returned to the airport and landed. Finding nothing wrong with the aircraft the plt. Took-off again. Whenthe…NTSB MIA86LA041Accident · No injuriesLimited investigationFinal reportCessna 337F · Sarasota, FLThe plt stated that all attempts to extend the landing gear were to no avail. He then intentionally landed gear up on the left side of rwy 4.NTSB NYC78FGM44Accident · Serious injuriesClosedCessna 337 · Cutty, PANTSB SEA78FA051Accident · 1 fatalClosedCessna 337F · Ocean Shores, WANTSB MIA78FA057Accident · 1 fatalClosedCessna 337F · No Name Key, FLNTSB OAK78FJY01Accident · 2 fatalClosedCessna 337F · Agana, GUNTSB FTW76FQG80Accident · No injuriesClosedCessna 337 · Adrian, TXNTSB IAD74FIG11Accident · No injuriesClosedCessna 337F · Preston, MDNTSB JAM73AB781Accident · Serious injuriesClosedCessna 337 · Trelawny, JamaicaNTSB MIA73FKW09Accident · No injuriesClosedCessna 337G · Knoxville, TNNTSB MKC73FCJ19Accident · No injuriesClosedCessna 337F · Omaha, NENTSB NYC73AN049Accident · No injuriesClosedCessna 337 · Laconia, NHNTSB MIA72AM031Accident · 2 fatalClosedCessna 337F · Cherrylog, GANTSB MKC71AK027Accident · 2 fatalClosedCessna 337F · Wichita, KS
Back to Cessna 337F