NTSB investigations: Piper PA-28-180, 2000
17 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\") = 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 ('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") = 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 ('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 FTW01FA024Accident · 1 fatalField investigationFinal reportPiper PA-28-180 · Stillwater, OKthe pilot's failure to maintain altitude/clearance from terrain while performing an instrument approach. Contributing factors were the low ceiling, dark night light condition, the pilot's decision to fly in known adverse weather conditions, and his lack of an…NTSB DEN00FA169Accident · Serious injuriesField investigationFinal reportPiper PA-28-180 · Englewood, COthe pilot's failure to maintain aircraft control, which resulted in a collision with terrain. A contributing factor was the high-density altitude weather condition.NTSB LAX00LA333Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Payson, AZThe pilot's failure to maintain directional control during the takeoff roll due to over-rotation, inadequate airspeed, and improper remedial action under the high density altitude condition.NTSB IAD00LA081Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Headwaters, VAPilot's failure to maintain aircraft control during take-off, which resulted in a stall.NTSB CHI00LA272Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Plattsmouth, NEthe pilot's improper preflight planning, improper in-flight planning and decision not to land before exhausting the airplane's fuel. Factors relating to this accident were the power lines, the roadway, and the ditch.NTSB LAX00LA298Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-180 · Grass Valley, CAThe pilot's failure to attain proper alignment with the runway during approach for landing. Contributing factors were the pilot's inadequate and improper preflight planning and in-flight decision.NTSB NYC00LA215Accident · Minor injuriesLimited investigationFinal reportPiper PA28-180 · Taberg, NYThe pilot's improper decision to attempt a second takeoff from the short grass runway at maximum gross weight, which resulted in the inadvertent stall/mush. Factors in this accident were the airplane's high gross weight and the short grass surface runway.NTSB NYC00LA207Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Norwood, MAthe pilot's improper bounced landing recovery. A factor was the pilot's lack of total flight experience.NTSB LAX00LA259Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-180 · Santa Maria, CAThe pilot's failure to ensure that an adequate fuel supply was on board at last departure, which resulted in a loss of engine power due to fuel exhaustion. The pilot's failure to refuel the airplane at the en route stop was also causal.NTSB LAX00LA251Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Tucson, AZThe student pilot's failure to maintain directional control of the airplane during landing.NTSB MIA00LA198Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Ocracoke, NCThe pilot's failure to compensate with rudder control for engine torque and 'p' factor during a go-around resulting in the aircraft drifting to the left, colliding with brush, and spinning around coming to rest in the brush.NTSB LAX00LA235Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Selma, CAThe pilot's inadequate preflight planning that resulted in fuel exhaustion and subsequent collision with grapevines during an off airport forced landing.NTSB DEN00LA112Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Loveland, COThe failure of the pilot to maintain directional control during takeoff roll. A factor was lack of recent experience.NTSB FTW00LA163Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-180 · Tulsa, OKthe loss of engine power for an undetermined reason. A contributing factor was the lack of suitable terrain for the forced landing.NTSB SEA00LA048Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Richland, WAFailure of a connecting rod for undetermined reasons. Factors include unsuitable terrain for the forced landing attempt.NTSB FTW00FA079Accident · 2 fatalField investigationFinal reportPiper PA-28-180 · Frisco, TXThe pilot's failure to maintain clearance with trees during an intentional low altitude flight maneuver.NTSB LAX00LA084Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Santa Barbara, CAThe dual student's loss of directional control and the flight instructor's inadequate supervision of the flight.