NTSB investigations: Piper PA-28-180, 2005
19 cases on aircraft the registry lists as Piper PA-28-180. 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 | 47 |
|---|---|
| 1965 | 72 |
| 1966 | 117 |
| 1967 | 131 |
| 1968 | 107 |
| 1969 | 92 |
| 1970 | 98 |
| 1971 | 99 |
| 1972 | 78 |
| 1973 | 85 |
| 1974 | 82 |
| 1975 | 64 |
| 1976 | 76 |
| 1977 | 54 |
| 1978 | 59 |
| 1979 | 37 |
| 1980 | 38 |
| 1981 | 26 |
| 1982 | 21 |
| 1983 | 29 |
| 1984 | 16 |
| 1985 | 24 |
| 1986 | 18 |
| 1987 | 23 |
| 1988 | 21 |
| 1989 | 29 |
| 1990 | 20 |
| 1991 | 12 |
| 1992 | 25 |
| 1993 | 17 |
| 1994 | 18 |
| 1995 | 21 |
| 1996 | 21 |
| 1997 | 16 |
| 1998 | 24 |
| 1999 | 17 |
| 2000 | 17 |
| 2001 | 13 |
| 2002 | 18 |
| 2003 | 17 |
| 2004 | 18 |
| 2005 | 19 |
| 2006 | 9 |
| 2007 | 13 |
| 2008 | 7 |
| 2009 | 15 |
| 2010 | 9 |
| 2011 | 15 |
| 2012 | 12 |
| 2013 | 10 |
| 2014 | 9 |
| 2015 | 10 |
| 2016 | 11 |
| 2017 | 10 |
| 2018 | 11 |
| 2019 | 12 |
| 2020 | 9 |
| 2021 | 11 |
| 2022 | 6 |
| 2023 | 24 |
| 2024 | 9 |
| 2025 | 7 |
| 2026 | 10 |
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\") = 2005
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102808'))
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") = 2005
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102808'))
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 CHI06FA057Accident · 3 fatalField investigationFinal reportPiper PA-28-180 · La Vista, NEThe non-instrument rated pilot not maintaining aircraft control and not maintaining altitude/clearance from terrain during takeoff into instrument meteorological conditions. Contributing factors were the low ceilings, night conditions present, and the pilot's…NTSB LAX06LA068Accident · 1 fatalLimited investigationFinal reportPiper PA-28-180 · Hopland, CAThe non-instrument rated pilot's failure to maintain clearance with terrain, which resulted in a controlled flight into terrain. Contributing factors were the dark night conditions and the low clouds.NTSB CHI06CA040Accident · Minor injuriesData collectionFinal reportPiper PA-28-180 · Marshall, MOAn in-flight loss of engine power in descent due to fuel exhaustion, and the pilot's inaccurate preflight planning. Contributing to the accident was the unsuitable terrain the pilot encountered and the night conditions.NTSB CHI06LA034Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Batavia, OHThe loss of engine power due to fuel starvation and improper fuel management by the pilot while on approach. Contributing factors were the low altitude and unsuitable terrain encountered during an emergency landing.NTSB DFW06CA018Accident · No injuriesData collectionFinal reportPiper PA28A · Lubbock, TXThe pilot's inability to maintain directional control of the airplane while landing due to the separation of the nose landing gear tire assembly.NTSB CHI06CA035Accident · No injuriesData collectionFinal reportPiper PA-28-180 · Imperial, NEThe pilot not maintaining airplane control during the takeoff.NTSB NYC05LA144Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-180 · Millville, NJThe flight instructor's improper in-flight decision to perform a emergency landing to a runway, with a tailwind, and his failure to maintain airspeed after aborting that landing, which resulted in an inadvertent stall and subsequent impact with terrain.…NTSB CHI05CA248Accident · No injuriesData collectionFinal reportPiper PA-28-180 · McConnell, ILThe pilot's inadequate preflight/planning which resulted in the attempted takeoff on the soft airstrip. Factors associated with the accident were the soft terrain, the corn crop, and the inadequate airspeed achieved during the takeoff roll.NTSB NYC05LA134Accident · 3 fatalLimited investigationFinal reportPiper PA-28-180 · Erie, PAThe pilot's inadequate preflight planning, which resulted in fuel exhaustion on approach, and subsequent loss of engine power.NTSB IAD05LA105Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-180 · Copake, NYThe pilot's inadequate preflight planning which resulted in fuel exhaustion and subsequent loss of engine power.NTSB IAD05LA103Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-180 · Denton, MDA loss of engine power for undetermined reasons.NTSB NYC05LA118Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-180 · Elyria, OHA loss of engine power during initial climb, as reported by the pilot, for an undetermined reason which resulted in a collision with trees.NTSB LAX05LA223Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Yuma, AZthe pilot's misjudged distance and altitude, which resulted in an undershoot and collision with a airport boundary fence short of the runway. A factor in the accident was the pilot's lack of familiarity flying the airplane at a high gross weight with a center…NTSB NYC05LA111Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-180 · West Carrollton, OHThe pilot's inadequate preflight inspection that resulted in fuel contamination and a subsequent loss of engine power. A factor related to the accident was the deteriorated fuel cap seals.NTSB CHI05LA158Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Allegan, MIThe inadequate aircraft control by the PA-28-180 pilot while the airplane was stopped.NTSB ATL05CA102Accident · Minor injuriesData collectionFinal reportPiper PA-28-180 · Luka, MSLoss of engine power due to the total failure of the exhaust valve on the number 2 cylinder, and the pilot's misjudgment of speed/distance/altitude which resulted in a overshoot of the runway and subsequent in-flight collision with trees. A factor was the…NTSB NYC05CA077Accident · Minor injuriesData collectionFinal reportPiper PA-28-180 · Portland, MEA loss of engine power due to the pilot's improper decision not to land and refuel resulting in fuel exhaustion.NTSB NYC05CA065Accident · Minor injuriesData collectionFinal reportPiper PA-28-180 · Sussex, NJThe pilot's failure to insure adequate obstacle clearance while conducting a practice forced landing approach, and the flight instructor's failure to take remedial action, which resulted in an in-flight collision with wires.NTSB MIA05LA076Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Bradfordville, FLThe failure of ATC to provide traffic advisories and safety alerts required in class C airspace and the inability of both pilots to see and avoid each other (low wing on top, high wing below), resulting in the midair collision.