NTSB investigations: Piper PA-32-300, AR
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
| 1973 | 1 |
|---|---|
| 1980 | 1 |
| 1986 | 1 |
| 1989 | 1 |
| 1990 | 1 |
| 1993 | 2 |
| 1997 | 1 |
| 2004 | 1 |
| 2006 | 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\" = 'AR' 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" = 'AR' 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 DFW07FA020Accident · 3 fatalField investigationFinal reportPiper PA-32-300 · Danville, ARFailure of the number 5 cylinder which resulted in oil starvation and the subsequent loss of engine power, and the pilot's inability to see the transmission line during the forced landing. Factors Contributing to the accident were the dark night and the…NTSB FTW04FA172Accident · 1 fatalField investigationFinal reportPiper PA-32-300 · Hot Springs, ARThe pilot's failure to fly a stabilized, published instrument approach procedure, which resulted in a collision with mountainous terrain. Factors were the clouds and the air traffic controllers' failure to provide known information that may have assisted the…NTSB FTW97LA284Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Pine Bluff, ARloss of engine power for undetermined reason(s). The lack of suitable terrain for a forced landing was a related factor.NTSB DEN93FA099Accident · 6 fatalField investigationFinal reportPiper PA-32-300 · Delight, ARThe failure of the vacuum pump, and an inoperative turn coordinator. Factors which contributed to the accident were: the pilot's loss of control of the airplane as a result of spatial disorientation, the pilot exceeding the design stress limits of the…NTSB FTW93LA127Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Danville, ARPilot's improper crosswind correction, his loss of directional control, and improper supervision by the instructor pilot. A factor was the crosswindNTSB MKC90LA112Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Little Rock, ARThe failure of the powerplant due to a sheared timing gear. Contributing factors were unsuitable terrain and restricted vision due to fog.NTSB MKC89FA196Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Bentonville, ARA loose oil line that became disconnected, when maintenance/inspection of the aircraft had not been completed, which resulted in loss of engine oil and subsequent failure of the connecting rod from lack of lubrication. A factor related to the accident was:…NTSB MKC87LA026Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Harrison, ARThe routine business flt had progressed normally until approaching bentonville, Arkansas. The PIC rptd his eng ran rough for a very brief period and quit. Emerg procedures were conducted but a restart was impossible. Only 1.5 hrs of flt had transpired since…NTSB FTW80FA080Accident · 2 fatalClosedPiper PA-32 · Lakeview, ARNTSB FTW74DPG41Accident · No injuriesClosedPiper PA-32 · Mena, AR