NTSB investigations: Piper PA-28R-200, 2016
9 cases on aircraft the registry lists as Piper PA-28R-200. 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
| 1969 | 5 |
|---|---|
| 1970 | 10 |
| 1971 | 11 |
| 1972 | 27 |
| 1973 | 37 |
| 1974 | 39 |
| 1975 | 39 |
| 1976 | 44 |
| 1977 | 50 |
| 1978 | 41 |
| 1979 | 25 |
| 1980 | 27 |
| 1981 | 25 |
| 1982 | 15 |
| 1983 | 20 |
| 1984 | 13 |
| 1985 | 11 |
| 1986 | 15 |
| 1987 | 15 |
| 1988 | 17 |
| 1989 | 15 |
| 1990 | 11 |
| 1991 | 14 |
| 1992 | 17 |
| 1993 | 13 |
| 1994 | 18 |
| 1995 | 8 |
| 1996 | 8 |
| 1997 | 18 |
| 1998 | 12 |
| 1999 | 9 |
| 2000 | 10 |
| 2001 | 6 |
| 2002 | 9 |
| 2003 | 11 |
| 2004 | 6 |
| 2005 | 7 |
| 2006 | 5 |
| 2007 | 7 |
| 2008 | 4 |
| 2009 | 8 |
| 2010 | 7 |
| 2011 | 3 |
| 2012 | 7 |
| 2013 | 5 |
| 2014 | 2 |
| 2015 | 10 |
| 2016 | 9 |
| 2017 | 11 |
| 2018 | 5 |
| 2019 | 8 |
| 2020 | 4 |
| 2021 | 5 |
| 2022 | 2 |
| 2023 | 3 |
| 2024 | 5 |
| 2025 | 5 |
| 2026 | 1 |
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\") = 2016
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102811'))
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") = 2016
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102811'))
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 CEN17FA064Accident · 4 fatalField investigationFinal reportPiper PA 28R-200 · Vienna, ILThe non-instrument rated pilot's decision to descend through an overcast layer of weather during dark night conditions, which resulted in the airplane impacting trees.NTSB CEN17FA063Accident · 3 fatalField investigationFinal reportPiper PA28R · McKinney, TXThe other pilot's use of an alternate traffic pattern entry procedure, which resulted in his inability to see and avoid the airplane, which was flying the preferred traffic pattern, and the subsequent midair collision.NTSB GAA17CA109Accident · No injuriesData collectionFinal reportPiper PA28R · Kewanee, ILThe pilot’s failure to extend the landing gear during the approach to land.NTSB GAA17CA072Accident · No injuriesData collectionFinal reportPiper PA 28R · Payallup, WAThe airport’s failure to issue a NOTAM regarding the deployment of the traffic monitoring camera system before the accident, which resulted in the airplane striking the camera system during a short-field approach and landing.NTSB GAA17LA090Accident · No injuriesLimited investigationFinal reportPiper PA28R · Watertown, WIThe pilot’s failure to attain a proper glidepath on approach for landing, which resulted in impact with trees. Contributing to the accident was a partial, temporary loss of engine power for reasons that could not be determined because postaccident examination…NTSB ERA16LA276Accident · Minor injuriesLimited investigationFinal reportPiper PA28R · Panama City, FLA total loss of engine power during approach for reasons that could not be determined because postaccident examination did not reveal any evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation.NTSB CEN16LA227Accident · No injuriesLimited investigationFinal reportPiper PA 28R-200 · Bowie, TXThe inadequate maintenance and inspection of the throttle control arm, which resulted in its in-flight separation and the subsequent loss of engine power.NTSB GAA16CA236Accident · No injuriesData collectionFinal reportPiper PA 28R · Lee's Summit, MOThe pilot's improper pitch control after the landing flare, resulting in an aerodynamic stall, hard landing, and consequent substantial left wing damage.NTSB WPR16IA100Incident · No injuriesIncident investigationFinal reportPiper PA28 · San Carlos, CAThe failure of maintenance personnel to properly install and secure the input swivel boot on the swivel joint, which resulted in excessive vibration that led to fatigue cracks and failure of the throttle cable.