NTSB investigations: Piper PA-28-181, 2003
10 cases on aircraft the registry lists as Piper PA-28-181. 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
| 1965 | 1 |
|---|---|
| 1966 | 1 |
| 1968 | 1 |
| 1971 | 1 |
| 1972 | 2 |
| 1974 | 1 |
| 1976 | 16 |
| 1977 | 16 |
| 1978 | 29 |
| 1979 | 23 |
| 1980 | 28 |
| 1981 | 36 |
| 1982 | 21 |
| 1983 | 24 |
| 1984 | 10 |
| 1985 | 33 |
| 1986 | 26 |
| 1987 | 23 |
| 1988 | 21 |
| 1989 | 10 |
| 1990 | 20 |
| 1991 | 19 |
| 1992 | 9 |
| 1993 | 19 |
| 1994 | 20 |
| 1995 | 22 |
| 1996 | 12 |
| 1997 | 17 |
| 1998 | 20 |
| 1999 | 16 |
| 2000 | 10 |
| 2001 | 15 |
| 2002 | 10 |
| 2003 | 10 |
| 2004 | 20 |
| 2005 | 15 |
| 2006 | 9 |
| 2007 | 14 |
| 2008 | 8 |
| 2009 | 8 |
| 2010 | 11 |
| 2011 | 7 |
| 2012 | 8 |
| 2013 | 7 |
| 2014 | 12 |
| 2015 | 9 |
| 2016 | 8 |
| 2017 | 8 |
| 2018 | 13 |
| 2019 | 8 |
| 2020 | 6 |
| 2021 | 9 |
| 2022 | 7 |
| 2023 | 19 |
| 2024 | 15 |
| 2025 | 13 |
| 2026 | 11 |
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\") = 2003
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102807', '7102832'))
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") = 2003
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102807', '7102832'))
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 FTW04FA037Accident · 2 fatalField investigationFinal reportPiper PA-28-181 · Sugar Land, TXThe pilots failure to maintain clearance with powerlines during a VFR approach. Contributing factors were the prevailing dark night conditions,and the high winds.NTSB NYC04FA033Accident · 2 fatalField investigationFinal reportCessna 180 · Westerly, RIThe Piper pilot's improper decision to continue a landing on an occupied runway, which resulted in an in-flight collision with the departing Cessna. Factors related to the accident were the departing Cessna pilot's inattentive radio communications, and the…NTSB NYC04LA026Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Montauk, NYThe pilot's loss of control after performing an evasive maneuver to avoid a deer crossing the unlit runway, which resulted in a collision with trees. Factors related to the accident were the nighttime conditions, the inoperative runway lighting system, and…NTSB CHI03FA284Accident · 3 fatalField investigationFinal reportCessna 172S · Lake Elmo, MNBoth pilots failed to maintain adequate visual lookout and did not maintain clearance from the other aircraft.NTSB NYC03LA163Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-181 · Sandusky, OHThe pilot's failure to maintain the engine mixture control during the go-around, which resulted in a loss of power, and in-flight collision with trees.NTSB LAX03LA228Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Phoenix, AZThe disengagement of the left control wheel from the control column, which was due to the attaching screw backing out of the nut plate. Also causal was the manufacturer's inadequate design of the installation and the improper length of the screw.NTSB LAX03LA144Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Bullhead City, AZThe pilot's misjudgment of distance resulting in the inadequate clearance between the wing tip and the fuel truck.NTSB LAX03LA127Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Santa Maria, CAThe pilot's inadequate in-flight planning/decision resulting in fuel exhaustion which resulted in a total loss of engine power during cruise flight, and a subsequent on-ground collision with a pole and a fence during the ensuing emergency landing.NTSB CHI03LA092Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Owatonna, MNThe pilots loss of directional control on landing and subsequent collision with terrain. Contributing factors were the crosswind, the airport lights, and the ditch.NTSB SEA03FA028Accident · 1 fatalField investigationFinal reportPiper PA-28-181 · Eastsound, WAThe pilot's failure to maintain clearance from the water and his failure to reset the altimeter to the local barometric pressure. Contributing factors were fog and night conditions.