NTSB investigations: Piper PA-28-161, 1993
21 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\") = 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 ('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") = 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 ('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 BFO94FA015Accident · 4 fatalField investigationFinal reportPiper PA-28-161 · Northampton, MAFailure of the air traffic control (ATC) facility to identify and provide the required traffic information to the jump aircraft before release of the jumper(s). A factor related to the accident was: inadequate visual lookout by the pilot of the jump aircraft.NTSB NYC94FA027Accident · 1 fatalField investigationFinal reportPiper PA-28-161 · Kinnelon, NJThe loss of engine power for undetermined reasons.NTSB BFO94LA004Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Manassas, VAThe loss of total engine power for undetermined reasons. A factor in the accident was the lack of suitable terrain to enable the completion of a power-off forced landing.NTSB ATL94LA008Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Lexington, NCThe pilot's failure to maintain directional control during a crosswind landing. A factor was the crosswind condition.NTSB SEA93LA215Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Tooele, UTThe pilot in command's failure to maintain directional control. A factor contributing to the accident was the fence.NTSB BFO93LA163Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Stowe, VTThe pilot's improper in-flight planning/decision. A related factor in the accident was: the partial loss of engine power for an undetermined reason.NTSB BFO93LA154Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Centre Hall, PAThe pilot misjudged his airspeed and altitude which resulted in the pilot's failure to attain the proper touchdown point resultng in the airplane exiting the runway and colliding with the berm. A related factor was the location of the berm.NTSB NYC93LA179Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · West Mifflin, PAThe pilot's misjudgement of speed and distance, which resulted in a landing overrun of the runway. Factors were an embankment and the pilot not being able to abort the landing.NTSB CHI93LA290Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Troy, MIIs the pilot not attaining the proper touchdown point, not flying a proper glidepath, and not performing a go around.NTSB FTW93LA218Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-161 · League City, TXVisual lookout not maintained by the driver of the vehicle. A factor was the driver of the vehicle becoming inadvertently lost.NTSB MIA93LA153Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-161 · Jacksonville, FLFailure of the pilot in command to maintain directional control during the landing. Contributing to the accident was the excessive airspeed while landing and failure of the pilot to recover from the bounced landing.NTSB CHI93LA190Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Indianapolis, INa misjudged flare and subsequent hard landing by the student pilot. A factor in the accident was the student pilot's failure to perform a go-around.NTSB LAX93FA215Accident · 2 fatalField investigationFinal reportPiper PA-28-161 · Grass Valley, CAThe pilot prematurely raising the airplane's flaps at an airspeed insufficient to maintain flight which resulted in an inadvertent stall mush condition. A factor in this accident was the darkness of the night.NTSB NYC93LA085Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Lakewood, NJThe pilot's inadequate compensation for wind conditions, and his failure to maintain directional control of the airplane, which resulted in a ground swerve and a collision with trees. The adverse wind was a related factor.NTSB DEN93LA039Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Llano, TXThe pilot's continued VFR flight into IMC. Factors were: low ceiling, dark night, and the pilot's lack of total instrument time.NTSB CHI93LA131Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Northwood, NDThe flight instructor's inadequate supervision of the flight.NTSB LAX93LA152Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-161 · Vacaville, CAa loss of engine power for undetermined reason(s).NTSB LAX93LA138Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Chandler, AZLoss of engine power for an undetermined reason.NTSB CHI93LA097Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Marshfield, WIThe student pilot's failure to maintain aircraft directional control during the takeoff ground run.NTSB LAX93LA127Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Bakersfield, CAThe overload failure of the right main landing gear strut attach bolts due to a hard landing. The hard landing was the result of the student misjudging the landing flare, and, the inadequate supervision of the flight by the flight instructor.NTSB NYC93LA060Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Danbury, CTThe pilot's improper emergency procedures for an engine fire during starting which resulted in the substantial damage. Factors related to the accident were the pilot's improper starting procedure and his lack of total experience.