NTSB investigations: Piper PA-32R-300, 1997
7 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
| 1965 | 1 |
|---|---|
| 1975 | 1 |
| 1976 | 9 |
| 1977 | 15 |
| 1978 | 22 |
| 1979 | 13 |
| 1980 | 12 |
| 1981 | 12 |
| 1982 | 7 |
| 1983 | 9 |
| 1984 | 5 |
| 1985 | 4 |
| 1986 | 5 |
| 1987 | 7 |
| 1988 | 6 |
| 1989 | 10 |
| 1990 | 6 |
| 1991 | 7 |
| 1992 | 4 |
| 1993 | 8 |
| 1994 | 10 |
| 1995 | 6 |
| 1996 | 7 |
| 1997 | 7 |
| 1998 | 2 |
| 1999 | 7 |
| 2000 | 3 |
| 2001 | 7 |
| 2002 | 6 |
| 2003 | 2 |
| 2004 | 4 |
| 2005 | 1 |
| 2006 | 6 |
| 2007 | 1 |
| 2008 | 5 |
| 2009 | 6 |
| 2010 | 7 |
| 2011 | 3 |
| 2012 | 4 |
| 2013 | 3 |
| 2014 | 2 |
| 2015 | 3 |
| 2016 | 3 |
| 2017 | 4 |
| 2018 | 4 |
| 2019 | 6 |
| 2020 | 3 |
| 2021 | 3 |
| 2022 | 4 |
| 2023 | 3 |
| 2024 | 1 |
| 2025 | 3 |
| 2026 | 2 |
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\") = 1997
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 year(c."eventDate") = 1997
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 LAX98LA027Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Santa Rosa, CALoss of engine power for undetermined reasons.NTSB CHI97LA294Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Fargo, NDthe pilot's misjudgment of altitude and distance to the runway, while on final approach to land, and failure to attain the proper touchdown point on the runway during the landing. The exposed runway lip was a related factor.NTSB IAD97LA092Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Defiance, OHThe failure of a wheel rim due to overstress separation with no clear evidence initiating event.NTSB LAX97LA181Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Burbank, CAimproperly secured upper cowl fasteners by unknown person(s).NTSB MIA97LA145Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Augusta, GAflight by the pilot into known adverse weather conditions, which resulted in a loss of aircraft control during the landing flare, and collision with the terrain. The adverse weather with nearby thunderstorm activity, crosswind, and gusts was a related factor.NTSB NYC97LA073Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Lumberton, NJThe pilot's delay in initiating remedial action to arrest an excessive descent rate during a go-around. A crosswind condition was a contributing factor.NTSB FTW97LA107Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Salida, COThe airplane's performance being exceeded due to the pilot's inadequate preflight planning. Factors were the uphill runway, high density altitude, and the pilot's lack of experience performing takeoffs from a high altitude airport.