NTSB investigations: Piper PA-28R-200, 1997
18 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\") = 1997
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") = 1997
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 NYC98LA045Accident · Serious injuriesLimited investigationFinal reportPiper PA-28R-200 · Fairplain, WVan improper overhaul of the fuel servo by the manufacturer, which resulted in the loss of engine power. Factors in the accident were the dark night conditions and rough forced landing terrain.NTSB CHI98LA004Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Nebraska City, NEthe pilot's improper positioning of the fuel slector to a tank which contained only unusable fuel.NTSB MIA97LA250Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Miami, FLThe failure of the pilot to properly plan his descent and approach for a forced landing following partial loss of engine power resulting in the aircraft landing short of the intended landing runway. A factor in the accident was improper inspection of the…NTSB NYC97LA179Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · West Chester, PAthe pilot's misjudgment of altitude and distance to the runway, which resulted in an undershoot and failure to reach the proper touchdown point. Rising terrain at the approach end of the runway was a related factor.NTSB NYC97LA160Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Ashland, OHThe pilot's improper fuel management which resulted in fuel exhaustion and loss of engine power.NTSB CHI97LA232Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Auburn, INan improper flare by either this pilot or the pilot of a previous flight, which resulted in a hard landing and overload damage to the right main landing gear. The pilot's continued operation with a known deficiency may have been a related factor.NTSB NYC97LA130Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Frankfort, NYThe pilot's misjudgment of distance and speed on final approach, and his failure to attain the proper touchdown point during landing. A factor in the accident was the night light condition.NTSB NYC97LA089Accident · 1 fatalLimited investigationFinal reportPiper PA-28R-200 · Pottstown, PAwas the flight instructor's diverted attention while standing on the wing behind a turning propeller, which resulted in his departure from the wing, forward into the turning propeller.NTSB SEA97FA106Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Tigard, ORThe pilot's failure to properly manage the aircraft fuel supply, which led to fuel exhaustion of the right tank and subsequent fuel starvation/power loss of the engine during the final approach. Factors contributing to the accident were the lack of sufficient…NTSB SEA97FA105Accident · 3 fatalField investigationFinal reportCessna 182 · Clinton, UTInadequate prior arrangements for formation flight by the pilot-in-command of the Cessna 182, N5434B, and his subsequent failure to see-and-avoid the Piper PA-28R, N5270T. Factors were: the Cessna pilot's visibility of the Piper impaired by the sun;…NTSB LAX97LA137Accident · Serious injuriesLimited investigationFinal reportPiper PA-28R-200 · Continental, AZloss of engine power as a result of detonation in the number 2 cylinder for undetermined reasons. A factor in the accident was the unsuitable nature of the forced landing area.NTSB FTW97FA122Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Westminster, TXThe pilot's failure to maintain clearance during an intentional low altitude maneuver. A factor was the transmission line.NTSB FTW97LA113Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Thibodaux, LAThe failure of maintenance personnel to comply with an airworthiness directive which specified the correct type of oil quick drain valve for this airplane, the installation of an incorrect oil quick drain valve by maintenance personnel, and the subsequent…NTSB LAX97WA109Accident · No injuriesForeign investigationPiper PA-28 · Mulege, MexicoNTSB ATL97LA041Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Winston Salem, NCthe pilot's inadequate compensation for wind conditions and failure to maintain directional cntrol of the airplane, which resulted in a ground swerve and collapse of the right main landing gear. The crosswind was a related factor.NTSB FTW97FA100Accident · 3 fatalField investigationFinal reportPiper PA-28-200 · Lone Wolf, OKthe pilot's impairment of judgment and performance due to drugs, his resultant improper planning/decision, and his failure to maintain sufficient altitude (clearance above a lake), while performing aerobatic flight. Factors relating to the accident were: the…NTSB NYC97LA046Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Thorndale, PAInadequate overhaul of the crankshaft that failed to detect fatigue cracks, which resulted in a total loss of engine power when the crankshaft separated in two.NTSB ATL97LA033Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Lebanon, TNThe pilot's improper short, soft field takeof. A factor was the pilot's poor in-flight decision to operate over an overcast until near the airplane's maximum endurance.