NTSB investigations: Piper PA-28R-200, 2003
11 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\") = 2003
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") = 2003
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 CHI04LA048Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Mountain Grove, MOImproper use of the brakes during landing by the pilot, resulting in failure of the left main landing gear tire and a loss of directional control. Contributing factors were the failure of the main landing gear, as well as the grass and the ditch adjacent to…NTSB LAX04FA061Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Chino Hills, CAthe pilot's inadequate in-flight planning/decision by which he conducted VFR flight into night instrument meteorological conditions. Mountainous terrain, dark night conditions and the pilot's failure to obtain a preflight weather briefing are contributing…NTSB LAX04CA063Accident · No injuriesData collectionFinal reportPiper PA-28R-200 · Morenci, AZthe pilot's excessive landing flare, which resulted in an improper touchdown and hard landing.NTSB ATL04LA039Accident · No injuriesLimited investigationFinal reportPiper PA-28R · Columbia, SCThe pilot's mismanagement of the fuel supply, and his inadequate preflight planning which resulted in fuel exhaustion.NTSB LAX04LA025Accident · Serious injuriesLimited investigationFinal reportPiper PA-28R-200 · Pacoima, CAthe pilot's failure to maintain an adequate glide path on final approach and his failure to ensure adequate clearance from obstacles. The dark night was a factor.NTSB LAX03FA298Accident · Serious injuriesField investigationFinal reportPiper PA-28R-200 · North Las Vegas, NVthe failure of the Federal Aviation Administration Air Traffic Control Tower local controller and local assist controller to effectively monitor the runway operation and ensure proper separation was maintained between aircraft on intersecting runways.NTSB ATL03LA139Accident · Minor injuriesLimited investigationFinal reportPiper PA-28R-200 · Collegedale, TNA loss of engine power due to oil exhaustion as a result of the installation of the incorrect quick-drain valve that opened during flight.NTSB SEA03LA174Accident · No injuriesLimited investigationFinal reportPiper PA-28-200R · Nampa, IDLanding gear collapse for undetermined reasons during the landing roll. On ground collision with a runway light was a factor.NTSB NYC03LA108Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Gaithersburg, MDThe pilot’s failure to maintain airspeed, resulting in an inadvertent stall.NTSB DEN03FA038Accident · 4 fatalField investigationFinal reportPiper PA-28R-200 · La Sal, UTthe loss of engine power (total) due to fuel starvation, the pilot not following procedures/directives (fuel management procedures), and the pilot's inadequate preflight planning/preparation for the flight. Contributing factors were the pilot's inadequately…NTSB FTW03LA207Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Roanoke, TXThe failure of the main landing gear assembly and attach points for undetermined reasons.