NTSB investigations: Piper PA-32R-300, IN
10 cases on aircraft the registry lists as Piper PA-32R-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
| 1979 | 2 |
|---|---|
| 1980 | 1 |
| 1981 | 1 |
| 1986 | 1 |
| 1989 | 1 |
| 2010 | 1 |
| 2018 | 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\" = '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 ('7103213'))
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 ('7103213'))
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 CEN23LA022Accident · Serious injuriesClass 3 · LimitedFinal reportPiper PA-32R-300 · Evansville, INThe total loss of engine power for reasons that could not be determined based on the available evidence.NTSB CEN22FA080Accident · 1 fatalClass 3 · FieldFinal reportPiper PA-32R-300 · Bloomington, INThe pilot’s failure to follow the instrument landing system (ILS) course guidance, which resulted in the pilot’s loss of airplane control during the instrument approach. Contributing to the accident was the presence of turbulence and low-level wind shear.NTSB WPR19LA011Accident · No injuriesClass 3 · LimitedFinal reportPiper PA32R · Indianapolis, INA total loss of engine power due to displacement of the dual magneto’s internal camshaft, which resulted in the magneto’s inability to produce spark.NTSB CEN11CA015Accident · No injuriesData collectionFinal reportPiper PA-32R-300 · Richmond, INThe pilot's diverted attention to a landing gear indicator light that led to a loss of directional control and subsequent impact with terrain while taxiing.NTSB CHI89LA146Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Nappanee, INThe pilot-in-command's improper preflight calculation of weight and balance and the aircraft's inadequate climb capability due to low compression.NTSB CHI87LA023Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Winamac, INAfter noticing a vague shape off the right side of the aircraft, during takeoff run at night, the pilot continued down the runway until the aircraft collided with a 180 pound deer.NTSB CHI81FA027Accident · 1 fatalClosedPiper PA-32 · Loganspopt, INNTSB CHI80FET26Accident · No injuriesClosedPiper PA-32R · Syracuse, INNTSB CHI79AA082Accident · 5 fatalClosedPiper PA-32R · Indianapolis, INNTSB CHI79FEX19Accident · No injuriesClosedPiper PA-32R · Mooresville, IN