NTSB investigations: Piper PA-28-161, 1995
14 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\") = 1995
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") = 1995
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 NYC96LA033Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Meriden, CTThe pilot's improper flare and improper recovery from a bounced landing. The unfavorable wind condition was a related factor.NTSB MIA96LA020Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Marco Island, FLA loss of engine power for undetermined reasons. The lack of suitable terrain for the forced landing was a factor.NTSB SEA96LA048Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Salt Lake City, UTa carburetor fire.NTSB NYC95LA230Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Rutland, VTLoss of engine power during takeoff for undetermined reason(s), which resulted in a forced landing and subsequent collision with a tree and barn.NTSB MIA95LA235Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Melbourne, FLThe failure of the pilot to maintain directional control during landing. Contributing to the accident was the crosswind.NTSB CHI95LA331Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Poseyville, INthe pilot's poor judgement in making a night takeoff on an unlit runway and his failure to maintain proper runway alignment. Factors associated with the accident were the hay bale, the night conditions and the unlit runway.NTSB NYC95LA223Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Auburn, MAThe loss of engine power for undetermined reasons. The lack of suitable terrain for a forced landing was a related factor.NTSB SEA95LA157Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-161 · Lakeview, ORthe pilot's failure to maintain clearance with terrain while his attention was directed to reading his map. The pilot's intentional low-altitude operation of the aircraft contributed to the accident.NTSB FTW95LA292Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Van Buren, ARA partial loss of engine power for undetermined reasons, and the pilot's misjudgment of distance and speed during the precautionary landing resulting in an overshoot.NTSB LAX95LA233Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-161 · Carmel Valley, CAfuel starvation due to the pilot's inadequate preflight preparation in that he failed to position the fuel selector to a tank known to contain fuel.NTSB CHI95LA166Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-161 · Valparaiso, INThe pilot's improper execution of the ILS approach. Factors related to the accident were the fog and the pilot's lack of total flight time in actual instrument conditions.NTSB NYC95LA128Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Bluffton, OHan improperly planned approach and touchdown, which resulted in an loss of directional control at touchdown, with the airplane departing the runway, and striking a ravine.NTSB NYC95LA102Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Old Bridge, NJThe pilot misjudged the landing flare and improperly recovered from a bounced landing.NTSB ATL95FA044Accident · 1 fatalField investigationFinal reportPiper PA-28-161 · Spring City, TNThe pilot's inadequate preflight planning, and his continued VFR flight into instrument weather conditions which resulted in the collision with the mountain. A factor was low ceilings.