NTSB investigations: Piper PA-28-161, 1994
17 cases on aircraft the registry lists as Piper PA-28-161. 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 | 1 |
|---|---|
| 1966 | 1 |
| 1967 | 1 |
| 1969 | 1 |
| 1971 | 1 |
| 1977 | 5 |
| 1978 | 19 |
| 1979 | 30 |
| 1980 | 30 |
| 1981 | 37 |
| 1982 | 31 |
| 1983 | 14 |
| 1984 | 16 |
| 1985 | 20 |
| 1986 | 20 |
| 1987 | 26 |
| 1988 | 19 |
| 1989 | 22 |
| 1990 | 28 |
| 1991 | 22 |
| 1992 | 23 |
| 1993 | 21 |
| 1994 | 17 |
| 1995 | 14 |
| 1996 | 13 |
| 1997 | 15 |
| 1998 | 13 |
| 1999 | 15 |
| 2000 | 16 |
| 2001 | 11 |
| 2002 | 11 |
| 2003 | 9 |
| 2004 | 15 |
| 2005 | 14 |
| 2006 | 17 |
| 2007 | 8 |
| 2008 | 22 |
| 2009 | 8 |
| 2010 | 10 |
| 2011 | 13 |
| 2012 | 8 |
| 2013 | 8 |
| 2014 | 6 |
| 2015 | 7 |
| 2016 | 7 |
| 2017 | 6 |
| 2018 | 11 |
| 2019 | 10 |
| 2020 | 2 |
| 2021 | 9 |
| 2022 | 5 |
| 2023 | 6 |
| 2024 | 7 |
| 2025 | 3 |
| 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\") = 1994
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102803', '7102834'))
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") = 1994
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102803', '7102834'))
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 MIA95LA051Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Lakeland, FLFatigue failure of the engine no.1 valve spring that jammed the intake valve open resulting in partial loss of engine power.NTSB MIA95FAMS1Accident · 1 fatalMissing aircraftFinal reportPiper PA-28-161 · Missing, FLUndetermined.NTSB SEA95LA024Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Auburn, WAThe pilot-in-command's not maintaining clearance from the power lines. A factor was the pilot-in-command's not maintaining the proper VASI glideslope.NTSB ATL95LA024Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · N. Myrtle Beach, SCThe pilot's failure to properly pre-flight the airplane to ensure the left fuel tank cover was properly secured.NTSB CHI95FA012Accident · 1 fatalField investigationFinal reportPiper PA-28-161 · Winfield, ILCollision with the ground for an undetermined reason. The pilot's psychological condition was a probable factor.NTSB CHI94LA335Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · W. Lafayette, INThe pilot's improper level-off and recovery from a bounced landing. A factor in the accident was the pilot's lack of training for recovery from bounced landings and/or aborted takeoffs.NTSB LAX94LA304Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Devore, CAwas the failure of the pilot to follow checklist and emergency procedures, which resulted in an improper decision to land on a dirt road within two miles of an airport.NTSB MIA94LA184Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Naples, FLFailure of the pilot-in-command to maintain wingtip clearance while taxiing resulting in the on-ground collision with a light pole.NTSB FTW94FA242Accident · 3 fatalField investigationFinal reportPiper PA-28-161 · Lakeview, ARThe pilot's failure to maintain minimum required airspeed for flight.NTSB LAX94LA270Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · San Carlos, CAthe student pilot's attempt to exit the runway at an excessive taxi speed which resulted in his loss of control.NTSB LAX94FA243Accident · 3 fatalField investigationFinal reportPiper PA-28-161 · Banning, CAThe failure of both pilots to see and avoid each other. The haze was a factor.NTSB MIA94LA084Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Sanford, FLThe failure of the pilot to maintain airspeed during the forced landing resulting in an inadvertent stall/mush. The total loss of engine power caused by fuel starvation due to inattentiveness by the pilot-in-command (CFI) to the fuel supply was also a cause.NTSB MIA94FA078Accident · 1 fatalField investigationFinal reportPiper PA-28-161 · Inverness, FLThe pilot-in-command's lack of total experience in instrument flight, simulated instrument flight, and night flight resulting in the pilot becoming spatially disoriented, and subsequent in-flight collision with terrain. Contributing to the accident was the…NTSB CHI94LA077Accident · No injuriesLimited investigationFinal reportPiper PA-28-160 · Wichita, KSThe pilot's failure to attain the proper touchdown point and delay in aborting the landing. The pilot's inadequate training was a factor.NTSB BFO94LA037Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Taunton, MAA total loss of engine power for undetermined reasons. A factor in this accident was the lack of suitable terrain to enable the successful completion of the forced landing.NTSB BFO94LA036Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Newburyport, MAThe pilot not maintaining clearance from the snowbank during final approach. A factor in this accident was the proximity of the snowbank to the active runway.NTSB BFO94FA034Accident · 1 fatalField investigationFinal reportPiper PA-28-161 · Bethel, PAthe pilot attempting visual flight rules (VFR) flight into instrument meteorological conditions and the pilot not maintaining clearance from objects/terrain.