NTSB investigations: Piper PA-28-235, 1999
5 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 | 4 |
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\") = 1999
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") = 1999
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 MIA00LA020Accident · No injuriesLimited investigationFinal reportPiper PA-28-235 · Raleigh, NCThe pilot's failure to maintain directional control on landing rollout for undetermined reasons. This resulted in the airplane veering off the runway and colliding with an airport sign.NTSB LAX99LA290Accident · No injuriesLimited investigationFinal reportPiper PA-28-235 · Boulder City, NVthe student pilot's failure to maintain directional control of the airplane during the takeoff roll.NTSB IAD99LA053Accident · No injuriesLimited investigationFinal reportPiper PA-28-235 · Zanesville, OHThe pilot not maintaining a proper descent rate and an inadequate flare.NTSB FTW99LA136Accident · No injuriesLimited investigationFinal reportPiper PA-28-235 · Sulphur Springs, TXThe delayed aborted takeoff by the pilot-in-command. Factors were the short runway, the tall grass, and the tree.NTSB DEN99LA048Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-235 · Provo, UTThe pilot exercising poor judgment by ignoring proper procedures/directives, his intentional selection of the wrong runway for takeoff, and his failure to maintain an adequate visual lookout. Factors were his ostentatious display, the other airplane moving on…