NTSB investigations: Piper PA-32-300
5 cases on aircraft the registry lists as Piper PA-32-300, where the sequence of events included Aircraft maintenance event. 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
| 2018 | 2 |
|---|---|
| 2020 | 2 |
| 2024 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103212')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.case_mkey = x.case_mkey AND s.aircrafts_position = x.position AND s.\"tier2Number\" = '040' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE \"isDefiningEvent\")))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103212')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.case_mkey = x.case_mkey AND s.aircrafts_position = x.position AND s."tier2Number" = '040' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE "isDefiningEvent")))
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 ERA24LA211Accident · No injuriesClass 3 · LimitedFinal reportPiper PA32 · Apopka, FLA partial loss of engine power due to sticking exhaust valves. Contributing to the accident was maintenance personnel’s failure to use available engine data while troubleshooting a known engine issue and maintenance personnel’s failure to comply with…NTSB CEN21LA049Accident · No injuriesClass 3 · LimitedFinal reportPiper PA32 · Circleville, OHThe total loss of engine power due to an accessory drive gear that backed out impeding the other gears.NTSB CEN20LA263Accident · Minor injuriesClass 3 · LimitedFinal reportPiper PA32 · Eveleth, MNThe seizure of the airplane’s engine-driven fuel pump due to internal contamination, which led to a total loss of engine power. The source of the contamination could not be determined based on available evidence.NTSB ERA18FA138Accident · 1 fatalField investigationFinal reportPiper PA32 · West Milford, NJAn in-flight fire and total loss of engine power after takeoff due to a loose fuel line. Contributing to the accident was the installation of an unapproved fuel line by unknown personnel.NTSB WPR18LA070Accident · No injuriesLimited investigationFinal reportPiper PA 32-300 · Reno, NVA total loss of engine power due to fuel starvation. Contributing to the accident was the failure of the pilot/owner to ensure that the airplane was airworthy before flight.