Cessna P337H
NTSB investigations · 16
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 ('2075731')
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 ('2075731')
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 WPR23LA175Accident · Minor injuriesClass 3 · LimitedFinal reportCessna P337H · Laurel, MTA partial loss of engine power to the rear engine resulting from cylinder detonation for undetermined reasons, which resulted in a forced landing and impact with terrain.NTSB ANC23LA023Accident · Minor injuriesClass 3 · LimitedFinal reportCessna P337H · Kona, HIThe failure of the pilot to recognize that the rear engine was not operating during takeoff, which resulted in an attempted single-engine takeoff and the airplane’s subsequent descent and impact with terrain. Contributing to the accident was a loss of rear…NTSB ERA22LA316Accident · No injuriesClass 4 · LimitedFinal reportCessna P337H · Monongahela, PAThe malfunction of the braking system fluid line, which resulted in an overrun of the runway.NTSB WPR13FA289Accident · 1 fatalField investigationFinal reportCessna P337H · San Luis Obispo, CALoss of engine power from the rear engine for reasons that could not be determined because of the postimpact thermal damage to the engine. Contributing to the accident were the pilot's decision to continue flight with a known deficiency, his failure to abort…NTSB WPR12CA240Accident · No injuriesData collectionFinal reportCessna P337H · Jerome, IDThe pilot’s failure to extend the landing gear before landing. Contributing to the accident was the pilot's failure to use the checklist before landing.NTSB NYC08FA215Accident · 2 fatalField investigationFinal reportCessna P337H · Cape Elizabeth, METhe pilot's improper decision to continue the flight in instrument meteorological conditions after experiencing an attitude indicator malfunction.NTSB MIA06FA008Accident · 1 fatalField investigationFinal reportCessna P337H · Port St. Lucie, FLThe pilot's continued flight into an area of known convective weather, resulting in a loss of aircraft control. Contributing factors were the failure of the FAA center controller to provide information on depicted severe weather to the pilot and the…NTSB ATL01LA053Accident · Minor injuriesLimited investigationFinal reportCessna P337H · Fort Lauderdale, FLThe pilot's failure to pre-flight adequate fuel for the flight.NTSB MIA00LA232Accident · Minor injuriesLimited investigationFinal reportCessna P337H · Alabaster, ALa loss of engine power for undetermined reasons resulting in a forced landing and subsequent impact with the ground. A factor in this accident was that the pilot did not obtain the proper touchdown point upon landing and landed long.NTSB FTW94FA090Accident · 1 fatalField investigationFinal reportCessna P337H · N. Little Rock, ARFailure of the pilot to maintain control of the aircraft, while maneuvering to land. Factors related to the accident were: darkness and possible spatial disorientation.NTSB NYC86LA121Accident · Minor injuriesLimited investigationFinal reportCessna T337HPII · Newburg, PAThe Cessna 337P experienced fuel exhaustion and attempted a landing on a road. During the landing the aircraft struck telephone poles and received substantial damage. The pilot did not receive any injuries in the accident which occurred in visual…NTSB MIA85FA128Accident · Serious injuriesField investigationFinal reportCessna P337H · Leesburg, FLOn the morning of 3/22/85, the plt arrived at the Leesburg muni arpt to pick up an acft that had been painted. Aprx 4 weeks earlier, the acft had been ferried there for the paint job. The plt said that during takeoff, both engs lost power at about 300 ft AGL…NTSB FTW83LA103Accident · Minor injuriesLimited investigationFinal reportCessna P337H · La Porte, TXShortly after lift-off, the acft started its initial climb, then entered a slow descent. The flight was continued until the acft collided with a tv cable, suspended below telephone cables on the same poles. The acft contacted the ground, bounced & became…NTSB IAD80AA008Accident · 3 fatalClosedCessna P337H · Benson, NCNTSB SEA79FYP42Accident · No injuriesClosedCessna P337 · Spokane, WANTSB MKC78DER92Accident · No injuriesClosedCessna P337H · Jacobsen, MN
Back to Cessna P337H