NTSB investigations: Piper PA-32-301T, CA
5 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 |
|---|---|
| 1992 | 2 |
| 2005 | 1 |
| 2012 | 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.\"eventStateOrRegion\" = 'CA' 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 ('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."eventStateOrRegion" = 'CA' 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 ('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 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 LAX05LA126Accident · No injuriesLimited investigationFinal reportPiper PA-32-301T · Long Beach, CAThe pilot's failure to maintain directional control during the landing rollout.NTSB LAX93LA064Accident · No injuriesLimited investigationFinal reportPiper PA-32-301T · Auburn, CAFailure of the pilot to maintain direction control during the landing touchdown. Contributing to the accident inadequate maintenance of the runway safety area by airport personnel.NTSB LAX92LA309Accident · No injuriesLimited investigationFinal reportPiper PA32-301T · Van Nuys, CAAn on ground collision with terrain subsequent to an engine failure for undetermined reasons.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 &…