NTSB investigations: Piper PA-32-300, SC
11 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
| 1977 | 1 |
|---|---|
| 1978 | 1 |
| 1980 | 1 |
| 1981 | 1 |
| 1996 | 1 |
| 2003 | 1 |
| 2007 | 1 |
| 2008 | 1 |
| 2018 | 1 |
| 2022 | 2 |
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\" = 'SC' 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" = 'SC' 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 ERA22LA202Accident · No injuriesClass 4 · LimitedFinal reportPiper PA32 · Fountain Inn, SCThe pilot’s failure to obtain the proper touchdown point during landing, which resulted in a runway overrun and collision with a fence.NTSB ERA22LA104Accident · No injuriesClass 3 · LimitedFinal reportPiper PA-32-300 · Edisto Island, SCA loss of engine power due to the fatigue failure of the crankshaft counterweight retaining ring and the No. 6 connecting rod.NTSB GAA18CA368Accident · No injuriesData collectionFinal reportPiper PA 32-300 · Columbia, SCThe pilot's failure to maintain directional control during landing.NTSB NYC08CA272Accident · No injuriesData collectionFinal reportPiper PA32 · Charleston, SCThe pilot's failure to maintain aircraft control while landing. Contributing to the accident was the crosswind condition and a wind gust, as reported by the pilot.NTSB ATL07LA086Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Columbia, SCThe pilot's improper landing flare, resulting in a hard landing.NTSB ATL03LA108Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Fort Mill, SCThe pilot's mismanagement of the fuel supply, which resulted in fuel starvation and the subsequent loss of engine power.NTSB ATL96LA128Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Georgetown, SCfailure of maintenance personnel to comply with an airworthiness directive, requiring periodic magneto inspections; inadequate annual inspection of the airplane by (other) maintenance personnel; and subsequent failure of the impulse coupling in the left…NTSB ATL82FLG04Accident · No injuriesClosedPiper PA-32 · Columbia, SCNTSB MIA80DLG06Accident · No injuriesClosedPiper PA-32 · N Myrtle Beach, SCNTSB MIA78DLG15Accident · No injuriesClosedPiper PA32 · Summerville, SCNTSB MIA77FA046Accident · 1 fatalClosedPiper PA-32 · Charleston, SC