NTSB investigations: Piper PA-28-161, 2001
11 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\") = 2001
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") = 2001
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 LAX02LA060Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Long Beach, CAThe student pilot's inadequate compensation for wind, and his failure to maintain directional control of the aircraft during the landing roll.NTSB ATL02LA023Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Kennesaw, GAThe pilot's improper in-flight planning/decision resulting in a total loss of engine power due to fuel exhaustion,which resulted in a forced landing, and subsequent in-flight collision with transmission wires.NTSB CHI02LA045Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Devils Lake, NDThe student pilot's failure to maintain directional control of the airplane during the takeoff phase of a touch and go landing. Factors associated with the accident were the student's lack of total experience and the runway light which the airplane contacted.NTSB CHI02LA031Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · New Ulm, MNThe student and flight instructor not using all of the available runway, the inadequate supervision by the flight instructor and the unsuccessful remedial action by the flight instructor. The student not attaining the proper touchdown point and the plowed…NTSB CHI01LA305Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Grand Forks, NDThe student pilot's improper flare, and the flight instructor's delayed remedial action, which resulted in a loss of directional control.NTSB FTW01LA197Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Ardmore, OKthe student pilot's failure to maintain directional control during takeoff roll.NTSB DEN01FA111Accident · 4 fatalField investigationFinal reportPiper PA-28-161 · Meeker, COthe pilot's failure to maintain terrain clearance as a result of his drug induced impairment. A factor was his exceeding the airplane's gross weight limits.NTSB NYC01FA128Accident · 3 fatalField investigationFinal reportPiper PA-28-161 · Danvers, MAThe pilot's failure to maintain aircraft control. Factors in the accident were the dark night, low ceiling, reduced visibility, and the pilot's decision to attempt a visual flight rules flight in marginal weather conditions.NTSB NYC01LA099Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Winchester, VAThe pilot's inadequate fuel management, which resulted in fuel starvation.NTSB MIA01LA125Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Chapel Hill, NCThe loss of engine power for undetermined reasons during takeoff, resulting in an inflight collision with trees during the subsequent emergency landing. A factor in the accident was the lack of suitable terrain to conduct an emergency landing.NTSB CHI01LA116Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Culver, INthe CFI delayed remedial action during the takeoff. Additional factors were the wrong runway was selected, the tailwind, and the trees.