NTSB investigations: Piper PA-32RT-300, NC
8 cases on aircraft the registry lists as Piper PA-32RT-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
| 1981 | 1 |
|---|---|
| 1987 | 1 |
| 1997 | 1 |
| 2001 | 1 |
| 2015 | 1 |
| 2019 | 1 |
| 2021 | 1 |
| 2022 | 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\" = 'NC' 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 ('7103215'))
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" = 'NC' 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 ('7103215'))
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 ERA22LA366Accident · Minor injuriesClass 3 · LimitedFinal reportPiper PA-32RT · Wilmington, NCA partial loss of engine power during initial climb for reasons that could not be determined.NTSB ERA21LA153Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-32RT-300 · Brevard, NCThe pilot’s improper landing flare, which resulted in a hard landing, overstress fracture of components of the left main landing gear, and subsequent runway excursion.NTSB ERA20LA062Accident · No injuriesClass 3 · LimitedFinal reportPiper PA32RT · Fletcher, NCA failure of two of the oil pump drive gear’s teeth, which resulted in a loss of engine oil lubrication, and a total loss of engine power.NTSB ERA16CA011Accident · No injuriesData collectionFinal reportPiper PA-32RT-300T · Salisbury, NCThe pilot's inadvertent switching of the fuel selector to the "off" position on final approach, which resulted in a total loss of engine power due to fuel starvation.NTSB MIA01FA107Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300 · Concord, NCAn in-flight collision with terrain for undetermined reasons.NTSB MIA97LA243Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300 · Oxford, NCfatigue failure of the No.4 connecting rod in an area where galling had occurred, which resulted in loss of engine power and a forced landing. Related factors were: the pilot's lack of communication by failing to select the proper UNICOM frequency; and his…NTSB ATL87LA202Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300 · Liberty, NCBfr departing on a ngt flt, the acft was loaded until it was at or near its max gross wt limit. The plt stated that as he was taking off on a 3000' rwy, the eng 'coughed' after the acft had accelerated to about the rotation speed & was aprx 3/4 of the way…NTSB ATL82FA030Accident · 2 fatalClosedPiper PA-32R · Wallace, NC