NTSB investigations: Piper PA-32-260, 1984
10 cases on aircraft the registry lists as Piper PA-32-260. 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
| 1965 | 4 |
|---|---|
| 1966 | 28 |
| 1967 | 32 |
| 1968 | 38 |
| 1969 | 34 |
| 1970 | 29 |
| 1971 | 37 |
| 1972 | 24 |
| 1973 | 26 |
| 1974 | 32 |
| 1975 | 24 |
| 1976 | 26 |
| 1977 | 27 |
| 1978 | 14 |
| 1979 | 18 |
| 1980 | 14 |
| 1981 | 13 |
| 1982 | 7 |
| 1983 | 17 |
| 1984 | 10 |
| 1985 | 4 |
| 1986 | 7 |
| 1987 | 11 |
| 1988 | 11 |
| 1989 | 12 |
| 1990 | 9 |
| 1991 | 7 |
| 1992 | 9 |
| 1993 | 7 |
| 1994 | 11 |
| 1995 | 9 |
| 1996 | 8 |
| 1997 | 7 |
| 1998 | 5 |
| 1999 | 7 |
| 2000 | 5 |
| 2001 | 6 |
| 2002 | 4 |
| 2003 | 6 |
| 2004 | 6 |
| 2005 | 2 |
| 2006 | 5 |
| 2007 | 4 |
| 2008 | 9 |
| 2009 | 2 |
| 2010 | 1 |
| 2011 | 5 |
| 2012 | 2 |
| 2013 | 2 |
| 2014 | 2 |
| 2015 | 3 |
| 2016 | 1 |
| 2017 | 4 |
| 2018 | 1 |
| 2019 | 10 |
| 2020 | 5 |
| 2021 | 9 |
| 2022 | 5 |
| 2023 | 6 |
| 2024 | 4 |
| 2025 | 3 |
| 2026 | 3 |
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 year(c.\"eventDate\") = 1984
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103206'))
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") = 1984
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103206'))
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 CHI84LA359Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Woodstock, ILThe acft collided with the terrain during a forced landing. The wx was VMC & no flt plan was filed. During the forced landing in a farm field the right main gear was sheared off and the nose gear bent. The left wing was also substantiallydamaged. The engine…NTSB FTW84LA350Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Minden, LADuring a night instructional flt on landing approach, the instructor pilot reported that the student over corrected for a high approach by closing the throttle. The acft hit the ground before he could establish control of the resulting high rate of sink.NTSB DEN84LA249Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Ogden, UTAfter discharging sky divers, plt was concentrating on max rate of descent, eng pwr at idle, when fuel tank in use ran day. Pwr loss not noted until throttle applied for level off. Switch to usable fuel tank and restart attempt initiated with insufficient…NTSB NYC84FNC07Accident · Minor injuriesFinal reportPiper PA-32-260 · Brunswick, METhe acft eng failed without warning at an alt of 2500 ft MSL. During the forced landing at nas Brunswick, the plt executed normal emergency procedures but was not successful in air-starting the acft. He stated that after having the 'abandoned field made' he…NTSB CHI84LA265Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Kankakee, ILThe eng quit shortly after takeoff & the acft landed in a bean field. The fuel selector was found on the empty right main fuel tank. The left main fuel tank & tip tanks were full of fuel.NTSB ANC84LA097Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Igiugig, AKDuring flt, the plt heard a 'loud bang' & then the eng lost power. He transmitted a mayday call & made an emergency landing on rolling tundra. During the landing, the nose & left main gear failed & the wing & prop were damaged. An exam revealed that the eng…NTSB ATL84FA151Accident · 5 fatalField investigationFinal reportPiper PA-32-260 · Maynardville, TNThe acft crashed in an uncontrolled state after the airframe failed in flt. Witnesses observed the acft spinning out of the clouds with parts of the airframe separating as it descended. The weather had been described to the plt in 2 wx briefings. At the time…NTSB CHI84LA171Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Marion, INThe student plt reported that during a landing, he reduced the power too soon & flared the acft too high, then the acft bounced about 8 to 10 ft in the air. The hard landing resulted in spar damage to the right wing.NTSB ATL84FA129Accident · Serious injuriesField investigationFinal reportPiper PA-32-260 · Woodstock, GAShortly after breaking ground during the takeoff, the engine lost power & the acft came back down to the rwy. The engine regained power & the plt continued the takeoff. The engine again lost power. Subsequently, the acft impacted on an uneven, grassy, open…NTSB CHI84LA133Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · St. Ignace, MIThe pilot initiated flight into adverse wx conditions in order to pick up a heart attack victim. The pilot encountered fog & in an attempt to return to his departure point, collided with the frozen lake.