Fatal NTSB investigations: Cessna P337H
5 cases on aircraft the registry lists as Cessna P337H. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1979 | 1 |
|---|---|
| 1994 | 1 |
| 2005 | 1 |
| 2008 | 1 |
| 2013 | 1 |
Where
Open the mapLatest cases
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_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
WHERE c.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.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_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE c."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.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 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 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 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 IAD80AA008Accident · 3 fatalClosedCessna P337H · Benson, NC