NTSB investigations: Piper PA-28-161, 2000
16 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\") = 2000
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") = 2000
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 MIA01LA034Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Melbourne, FLThe student pilot's failure to maintain a visual look out while transitioning from the active runway to a taxiway resulting in an on-ground collision with a taxiway sign.NTSB NYC01LA042Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Fremont, OHThe pilot's failure to obtain a proper touchdown point while landing. Factors were the pilot's improper weather evaluation, rain, a low ceiling, and a tailwind.NTSB MIA01LA009Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Jesup, GAA total failure of the wheel braking system due to the pilot's improper use of braking in downwind, downhill conditions, resulting in overheated brakes, and subsequent encounter with a downslope and terrain collision.NTSB ATL00FA091Accident · 2 fatalField investigationFinal reportPiper PA-28-161 · Ft. Pierce, FLFailure of local controller to provide adequate spacing between two airplanes that resulted in a midair collision. Contributing Factors: the local controller declined receiving a formal brief before relieving the controller on duty. The controller who was…NTSB LAX00LA330Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Palo Alto, CAThe failure of maintenance personnel to detect and correct loose attachment fasteners and fretting at the landing gear attachment during maintenance inspections.NTSB CHI00FA263Accident · 3 fatalField investigationFinal reportPiper PA-28-161 · Watertown, WIAircraft control not being maintained during initial climb resulting in a stall/mush. Factors to the accident were the pilot's inadequate preflight planning/preparation, the pilot operating over the airplane's certified maximum gross weight, and the pilot…NTSB NYC00LA175Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Robbinsville, NJThe pilot's inadequate compensation for wind conditions, which resulted in a loss of aircraft control. A factor was a crosswind.NTSB FTW00LA185Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Mckinney, TXThe flight instructor's inadequate supervision of the landing resulting in the loss of directional control by the student pilot.NTSB CHI00LA154Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Minneapolis, MNthe failure of the engine and the unsuitable terrain for landing encountered by the pilot-in-command. Factors to the accident were the fracture of the crankshaft due to fatigue, excessive main bearing wear, and the swampy terrain condition.NTSB NYC00LA149Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Miamisburg, OHThe CFI's delayed remedial action.NTSB NYC00LA146Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Williamstown, NJimproper installation of a quick drain plug by the airplane owner/mechanic which resulted in a loss of engine oil and forced landing.NTSB MIA00LA171Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Chapel Hill, NCThe failure of the CFI to delay his landing until the approaching line of thunderstorms passed, causing the flight to encounter severely gusting wind conditions resulting in the loss of altitude control and collision with the terrain.NTSB LAX00LA154Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Palo Alto, CAThe loss of engine power for undetermined reasons during takeoff climb.NTSB NYC00LA089Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · West Milford, NJThe pilot's failure to maintain directional control during landing. A factor in this accident was the gusty crosswind conditions.NTSB ATL00FA026Accident · 1 fatalField investigationFinal reportPiper PA-28-161 · Chamblee, GAThe S76 helicopter pilot's failure to follow ATC landing sequence clearance, which resulted in the PA-28's encounter with the helicopters wake turbulence. A factor was the air traffic controllers clearance procedure.NTSB LAX00LA094Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Honolulu, HIThe pilot's improper use of the brakes during the landing rollout. The pilot's self induced pressure and the quartering tailwind were factors in the accident.