NTSB investigations: Piper PA-32-300, UT
8 cases on aircraft the registry lists as Piper PA-32-300. 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
| 1970 | 1 |
|---|---|
| 1971 | 1 |
| 1976 | 1 |
| 1977 | 2 |
| 1981 | 1 |
| 2006 | 2 |
Where
Latest 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.\"eventStateOrRegion\" = 'UT' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103212'))
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."eventStateOrRegion" = 'UT' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103212'))
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 SEA06CA179Accident · No injuriesData collectionFinal reportPiper PA-32-300 · Kanab, UTThe pilot's failure to maintain aircraft control during the takeoff roll. Contributing factors were the rough/uneven conditions of the dirt runway, the wind gusts, and the berms and ditches on both sides of the runway.NTSB SEA06LA141Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Grantsville, UTA lack of lubrication for undetermined reasons, which resulted in the failure of the Nos. 2, 3, 4, 5 and 6 connecting rods, a subsequent total loss of engine power during descent, which resulted in a forced landing. A factor in the accident was the soft sand.NTSB DEN81FA033Accident · 6 fatalClosedPiper PA-32 · Escalante, UTNTSB DEN78FA002Accident · 7 fatalClosedPiper PA-32 · Cedar Fort, UTNTSB DEN77FTM28Accident · Serious injuriesClosedPiper PA-32R · Heber City, UTNTSB DEN76FTM21Accident · No injuriesClosedPiper PA-32 · Logan, UTNTSB DEN71FXT23Accident · No injuriesClosedPiper PA-32 · Provo, UTNTSB DEN70FXT08Accident · No injuriesClosedPiper PA-32 · Woods Cross, UT