NTSB investigations: Piper PA-28R-200, 1993
13 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\") = 1993
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") = 1993
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 CHI94LA054Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Lacon, ILThe pilot misjudged the landing flare. Factors related to the accident were: the dark night, the pilot's lack of recent night experience, and the failure of the airplane's electrical system.NTSB NYC94FA033Accident · 4 fatalField investigationFinal reportPiper PA-28R-200 · New Haven, CTThe pilot's failure to maintain control of the airplane during a night approach in adverse weather conditions. Factors which contributed to the accident were the weather conditions and dark night. In addition, the radar controller's vectoring of the pilot to…NTSB CHI93LA311Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Millard, NEImproper maintenance/inspection of the aircraft by (other) maintenance personnel, and subsequent blockage of the induction air system by an object (alternate air door) that was not removed during previous maintenance.NTSB CHI93FA302Accident · 5 fatalField investigationFinal reportRockwell 690-A · Norfolk, NEThe failure of the pilots of the Rockwell 690-A, N707BP, and the Piper PA-28R, N33056, to see and avoid each other. A factor which contributed to the accident was the failure of both pilot's to follow recommended communication procedures contained in the…NTSB CHI93LA277Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Flushing, MIThe pilot's inadequate preflight planning for determining the proper takeoff profile. A factor in the accident was the high density altitude.NTSB LAX93LA229Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Hesperia, CAFatigue failure of the exhaust valve due to inadequate maintenance and inspection.NTSB LAX93LA182Accident · Serious injuriesLimited investigationFinal reportPiper PA-28R-200 · Avalon, CAThe loss of engine power for undetermined reasons.NTSB CHI93FA135Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Kinsley, KSThe pilot initiated VFR flight into instrument meteorological conditions which resulted in a loss of aircraft control due to spatial disorientation. The adverse weather conditions were factors which contributed to the accident.NTSB FTW93LA120Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Midlothian, TXFailure of the engine cowling latch resulting in deteriorating airplane performance and a forced landing.NTSB MIA93LA092Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Walls, MSThe pilot-in-command's delay in aborting the landing.NTSB BFO93LA054Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Babylon, NYThe loss of engine power due to the intake valve failure.NTSB CHI93FAMS2Accident · 1 fatalMissing aircraftFinal reportPiper PA-28R-200 · Grand Haven, MIundetermined.NTSB CHI93LA089Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Lincoln, NEThe pilot's failure to attain the proper touchdown point and failure to abort the landing. The wet, grass landing area was a factor.