Fatal NTSB investigations: Piper PA-32-301T
6 cases on aircraft the registry lists as Piper PA-32-301T. 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
| 1983 | 1 |
|---|---|
| 1986 | 1 |
| 1992 | 1 |
| 1997 | 1 |
| 2012 | 1 |
| 2023 | 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 ('7103209'))
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 ('7103209'))
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 CEN23FA079Accident · 2 fatalClass 3 · FieldFinal reportPiper PA-32-301T · Kingfisher, OKAn oil leak of undetermined origin that resulted in an in-flight engine compartment fire and subsequent loss of airplane control.NTSB WPR12FA369Accident · 5 fatalField investigationFinal reportPiper PA-32-301T · South Lake Tahoe, CAA partial loss of engine power for reasons that could not be determined because examinations revealed no evidence of mechanical anomalies with the airframe or engine that would have precluded normal operation and the pilots’ decision to continue the departure…NTSB SEA97FA120Accident · 2 fatalField investigationFinal reportPiper PA-32-301T · Bend, OROverload of the airframe structure. Thunderstorms and turbulence were factors.NTSB DEN92FA085Accident · 3 fatalField investigationFinal reportPiper PA-32-301T · Kit Carson, COThe pilot becoming spatially disoriented and exceeding the design stress limits of the aircraft. Factors were: the pilot's failure to obtain a weather briefing, his attempted VFR flight into a level six thunderstorm, and his lack of instrument time.NTSB SEA86FA098Accident · 2 fatalField investigationFinal reportPiper PA-32-301T · Fort Hall, IDRadar track showed acft made normal climb on course from airport (elev 4488 ft MSL) to 9400 ft. MSL, then executed a left turn of about 90 degrees, climbing to 9700 ft MSL as shown by next-to-last radar tgt. 29 secs later, final radar tgt showed 6900 ft MSL.…NTSB LAX83FA424Accident · 4 fatalField investigationFinal reportPiper PA-32-301T · San Marcos, CAAt aprx 2209 PDT, the plt departed fresno, CA on a night, VFR, x-country flt. He cancelled his VFR flt plan at 0009 PDT & landed at ramona, CA at 0012. After landing, he called his wife to inquire about the wx at palomar, CA. She looked out the window &…