NTSB investigations: Piper PA-32-300, 1986
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
| 1967 | 13 |
|---|---|
| 1968 | 13 |
| 1969 | 15 |
| 1970 | 24 |
| 1971 | 23 |
| 1972 | 22 |
| 1973 | 22 |
| 1974 | 29 |
| 1975 | 31 |
| 1976 | 29 |
| 1977 | 23 |
| 1978 | 34 |
| 1979 | 23 |
| 1980 | 28 |
| 1981 | 17 |
| 1982 | 20 |
| 1983 | 15 |
| 1984 | 11 |
| 1985 | 23 |
| 1986 | 10 |
| 1987 | 12 |
| 1988 | 19 |
| 1989 | 25 |
| 1990 | 8 |
| 1991 | 12 |
| 1992 | 13 |
| 1993 | 17 |
| 1994 | 11 |
| 1995 | 10 |
| 1996 | 10 |
| 1997 | 13 |
| 1998 | 11 |
| 1999 | 10 |
| 2000 | 12 |
| 2001 | 12 |
| 2002 | 11 |
| 2003 | 10 |
| 2004 | 5 |
| 2005 | 9 |
| 2006 | 9 |
| 2007 | 5 |
| 2008 | 6 |
| 2009 | 2 |
| 2010 | 2 |
| 2011 | 3 |
| 2012 | 7 |
| 2013 | 2 |
| 2014 | 4 |
| 2015 | 5 |
| 2016 | 4 |
| 2017 | 4 |
| 2018 | 11 |
| 2019 | 4 |
| 2020 | 7 |
| 2021 | 2 |
| 2022 | 12 |
| 2023 | 8 |
| 2024 | 9 |
| 2025 | 3 |
| 2026 | 3 |
Where
Latest 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 year(c.\"eventDate\") = 1986
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 year(c."eventDate") = 1986
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 SEA87LA040Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Gates, ORThe plt was attempting to land the aircraft at night on an unlit grass airstrip. Prior to reaching the airstrip the plt collided with an apple tree. Both wings were severed from the aircraft and it went inverted before striking the ground in a slightly nose…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 LAX86LA343Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Riverside, CAWhile en route to hawthorne airport the aircraft experienced a total loss of power. During a circling descent the pilot attempted to restart the engine without success. The aircraft collided with the terrain 500 ft short of rwy 27 at Riverside airport. The…NTSB ANC86LA124Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Tyonek, AKThe pilot stated that during the initial climb, the aircraft started to settle. The pilot stalled and crashed into a wooded area at the departure end of the runway.NTSB ANC86LA054Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Atmautluak, AKThe air taxi pilot planned six hours of night flying with a five minute fuel reserve at his destination. When he saw that he would be unable to reach the destination, he diverted toward atmautlauk. However, the acft ran out of fuel as the plt was maneuvering…NTSB NYC86LA104Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Doylestown, PAThe pilot made a long landing and ran off the end of the runway. After departing the runway, he ran through a fence and hit a dirt embankment. The pilot said when he realized he was going off the end of the runway, he stayed on the brakes rather than add…NTSB ATL86LA109Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Birmingham, ALAfter takeoff pilot noted loss of engine oil pressure. Engine siezed and pilot landed short of runway. A/c hit ILS antenna during landing roll, severed right wing. Engine oil cooler line burst due to aging. Line was fabricated in the 1st qtr 0F 1972. Oil…NTSB ATL86MA087Accident · 1 fatalMajor investigationFinal reportPiper PA-32-300 · Andalusia, ALThe accident flt was to be the last in a series of flt tests. This flt was for the purpose of determining the landing characteristics of the acft with a combination speed/stol kit installed. When the FAA flt test plt failed to return from the mission a search…NTSB MIA86FA085Accident · 1 fatalField investigationFinal reportPiper PA-32-300 · St. Cloud, FLThe acft was on a VFR flt, the wx was clear with an almost full moon when the acft crashed in a fld. There was no evidence of an airframe, flt control system, eng or propeller malfunction or failure. The autopsy & toxicological studies revealed no pre impact…NTSB MIA86LA065Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Melbourne, FLThe plt stated that on his landing rollout he lost control of the acft & veered off the left side of rwy 9L collapsing the nose gear.