NTSB investigations: Piper PA-32-300, IN
10 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 | 2 |
|---|---|
| 1971 | 1 |
| 1978 | 1 |
| 1980 | 1 |
| 1983 | 1 |
| 2005 | 2 |
| 2014 | 1 |
| 2017 | 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\" = 'IN' 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" = 'IN' 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 CEN17LA271Accident · No injuriesLimited investigationFinal reportPiper PA 32-300 · Rushville, INThe pilot’s inability to properly control engine power because of an improperly installed throttle control arm, which resulted in a partial loss of engine power and led to a forced landing.NTSB CEN14CA422Accident · No injuriesData collectionFinal reportPiper PA 32-300 · Warsaw, INThe pilot failed to maintain directional control during landing.NTSB CHI05FA260Accident · 4 fatalField investigationFinal reportPiper PA-32-300 · Wabash, INThe pilot's spatial disorientation that resulted in his failure to maintain clearance from terrain. Factors to the accident were the pilot's lack of recent night experience and the hazy night conditions.NTSB CHI05CA087Accident · No injuriesData collectionFinal reportPiper PA-32-300 · Jeffersonville, INThe pilot's inadequate preflight of the aircraft by his failure to detect an open fuel drain which resulted in fuel starvation and the loss of engine power. Contributing factors were the pilot's failure to follow emergency procedures, low ceiling, fog and…NTSB CHI83LA356Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Ligonier, INThe plt report that when he landed on a wet, grass rwy, the acft slid off the wet sod & hit a ditch while on the landing roll. No mechanical malfunctions were reported.NTSB CHI80FA026Accident · 4 fatalClosedPiper PA-32 · Ft Wayne, INNTSB CHI78FA048Accident · No injuriesClosedPiper PA-32 · Goshen, INNTSB CHI72DEA16Accident · No injuriesClosedPiper PA-32 · Anderson, INNTSB CHI71FBM10Accident · Minor injuriesClosedPiper PA-32 · South Bend, INNTSB CHI71DBA20Accident · No injuriesClosedPiper PA-32 · Indianapolis, IN