NTSB investigations: Piper PA-28-235, 2000
7 cases on aircraft the registry lists as Piper PA-28-235. 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
| 1964 | 27 |
|---|---|
| 1965 | 40 |
| 1966 | 30 |
| 1967 | 32 |
| 1968 | 34 |
| 1969 | 16 |
| 1970 | 24 |
| 1971 | 13 |
| 1972 | 30 |
| 1973 | 14 |
| 1974 | 16 |
| 1975 | 14 |
| 1976 | 18 |
| 1977 | 14 |
| 1978 | 15 |
| 1979 | 8 |
| 1980 | 10 |
| 1981 | 11 |
| 1982 | 9 |
| 1983 | 3 |
| 1984 | 4 |
| 1985 | 7 |
| 1986 | 7 |
| 1987 | 7 |
| 1988 | 5 |
| 1989 | 8 |
| 1990 | 7 |
| 1991 | 1 |
| 1992 | 4 |
| 1993 | 4 |
| 1994 | 9 |
| 1995 | 6 |
| 1996 | 5 |
| 1997 | 6 |
| 1998 | 5 |
| 1999 | 5 |
| 2000 | 7 |
| 2001 | 6 |
| 2002 | 8 |
| 2003 | 4 |
| 2004 | 2 |
| 2005 | 6 |
| 2006 | 4 |
| 2007 | 2 |
| 2008 | 7 |
| 2009 | 4 |
| 2010 | 5 |
| 2011 | 7 |
| 2012 | 2 |
| 2013 | 3 |
| 2014 | 4 |
| 2015 | 3 |
| 2016 | 2 |
| 2017 | 3 |
| 2018 | 1 |
| 2019 | 5 |
| 2020 | 6 |
| 2021 | 2 |
| 2022 | 5 |
| 2023 | 5 |
| 2024 | 1 |
| 2025 | 4 |
| 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\") = 2000
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102810'))
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") = 2000
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102810'))
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 FTW01LA018Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-235 · Almyra, ARthe loss of engine power due to the crankshaft idler gear's loose lower retaining screw, which resulted in the fatigue failure of the crankshaft idler gear's upper retaining screw.NTSB DEN00LA178Accident · No injuriesLimited investigationFinal reportPiper PA-28-235 · Broomfield, COThe pilot's failure to maintain adequate clearance from a vehicle parked beside the ramp while he was taxiing the aircraft from landing.NTSB ATL00LA093Accident · No injuriesLimited investigationFinal reportPiper PA-28-235 · Adel, GAThe pilot's selection of a closed runway for landing. Contributing factors were his inadequate inflight planning/decision and the wood block on the runway..NTSB CHI00LA264Accident · No injuriesLimited investigationFinal reportPiper PA-28-235 · Mackinac Island, MIthe pilot not maintaining aircraft control in response to the uncommanded roll, and the excessive descent to the runway resulting in the hard landing. Factors relating to the accident were the pilot's attempted recovery from the uncommanded roll, the high…NTSB NYC00LA221Accident · Minor injuriesLimited investigationFinal reportPiper PA28-235 · Chester, CTThe CFI's delayed remedial action.NTSB CHI00LA164Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-235 · Sully, IAThe pilot inadvertently applied full flaps during the aborted landing and was not able to gain enough altitude to clear a fence post at the end of the airstrip. Factors associated with the accident were the trees at the approach end of the airstrip, the pilot…NTSB FTW00LA202Accident · No injuriesLimited investigationFinal reportPiper PA-28-235 · Sugar Land, TXThe pilot's improper fuel tank selection, which resulted in fuel starvation. A factor was the lack of suitable terrain for the forced landing.