NTSB investigations: Piper PA-32-300, 1998
11 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
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\") = 1998
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") = 1998
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 FTW99LA032Accident · Minor injuriesLimited investigationFinal reportPiper PA32-300 · New Iberia, LAThe mechanic's failure to properly torque the connecting rod's bolt and nut during engine overhaul. A factor was the lack of suitable terrain for the forced landing.NTSB IAD99LA010Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Dunkirk, NYThe pilot's inadequate fuel management that resulted in fuel starvation. Factors in the accident were the improperly timed magneto and an engine driven fuel pump leak.NTSB MIA98LA257Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Opa Locka, FLThe pilot's improper remedial action in recovering from a bounced landing resulting in a stall, and his incorrect recovery from a pilot induced oscillation (PIO) condition. A factor was the pilot's failure to execute a timely go-around maneuver.NTSB ANC98LA097Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Nenana, AKThe failure of the FAA Flight Service Station specialist to issue an active Notice to Airmen that noted a hazardous condition on the runway. Factors associated with the accident are the rough and uneven runway, and inadequate runway maintenance by airport…NTSB NYC98LA119Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Hanover, PAfailure of the pilot to obtain current information for the divert airfield, and his selection of an unsuitable area for landing. Related factors included: the lower ambient light conditions at dusk, construction on the airfield, and an over-reliance on the…NTSB ATL98LA069Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Panama City, FLThe engine crankshaft fracturing, leading to total powerplant failure. Contributing to the severity of the accident was a utility pole.NTSB NYC98LA102Accident · 1 fatalLimited investigationFinal reportPiper PA-32-300 · New Bedford, MAThe pilot's impairment due to alcohol, which resulted in an inadequate preflight examination and subsequent takeoff with a control lock installed.NTSB IAD98LA040Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Red Hook, NYinadequate compensation for the crosswind by the pilot, and his failure to maintain directional control during the landing. Related factors were: the gusty crosswind condition, and high vegetation that was encountered after departing the runway.NTSB ANC98LA023Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Naknek, AKThe pilot's failure to maintain an adequate visual lookout. Factors in the accident were flat lighting conditions, and inadequate airport facilities.NTSB MIA98LA085Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Holly Springs, MSa total loss of power due to fuel starvation as a result of the pilot's lack of adequate preflight planning and preparation and his failure to adequately refuel his airplane.NTSB FTW98LA109Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Alexandria, LAThe fire in the normal braking system due to an undetermined reason.