NTSB investigations: Piper PA-28-180, 2007
13 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\") = 2007
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") = 2007
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 NYC08CA066Accident · No injuriesData collectionFinal reportPiper PA28-180 · Blue Bell, PAThe student pilot's failure to maintain directional control while landing.NTSB LAX08CA035Accident · No injuriesData collectionFinal reportPiper PA-28-180 · Fallbrook, CAThe pilot's misjudged distance and altitude that led to an undershoot and a failure to obtain the proper touchdown point.NTSB SEA08CA026Accident · No injuriesData collectionFinal reportPiper PA-28-180 · Sedona, AZThe pilot's inadequate compensation for the wind condition, which resulted in his failure to maintain directional control during takeoff. Factors associated with the accident included the gusty crosswind condition and the taxiway sign.NTSB NYC08CA002Accident · Minor injuriesData collectionFinal reportPiper PA-28-180 · Fairview, TNA loss of engine power due to fuel exhaustion.NTSB NYC07CA240Accident · No injuriesData collectionFinal reportPiper PA-28-180 · Bridgeport, CTThe pilot's failure to maintain directional control of the airplane during the landing. Contributing was the crosswind weather condition.NTSB CHI07CA278Accident · No injuriesData collectionFinal reportPiper PA-28-180 · Hagerstown, INThe pilot's use of an unsuitable runway for takeoff and delayed aborted takeoff. Factors were the wet grass and the fence the airplane impacted and subsequently nosed over.NTSB DFW07CA213Accident · No injuriesData collectionFinal reportPiper PA-28-180 · Tunica, MSThe pilot's failure to compensate for the existing wind conditions during a crosswind landing. A factor was the crosswind.NTSB LAX07CA232Accident · Minor injuriesData collectionFinal reportPiper PA-28-180 · Eagle Point, ORFuel exhaustion due to the pilot's inadequate fuel consumption calculations.NTSB SEA07LA141Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Rosamond, CAThe pilot's failure to abort the takeoff due to lack of airplane climb performance, which resulted in a collision with terrain.NTSB CHI07FA102Accident · 3 fatalField investigationFinal reportPiper PA-28-180 · Viburnum, MOThe pilot's loss of aircraft control during cruise flight in instrument meteorological conditions. Factors contributing to the accident were turbulence and icing conditions.NTSB ATL07CA062Accident · No injuriesData collectionFinal reportPiper PA-28A-180C · Atlanta, GAThe pilot's failure to maintain directional control of the airplane while landing with a flat main tire.NTSB DEN07FA054Accident · 3 fatalField investigationFinal reportPiper PA-28-180 · Centennial, WYthe pilot's inadvertent flight into adverse weather conditions resulting in a loss of aircraft control. Contributing factors include the pilot's improper preflight planning and decision making, the pilot's spatial disorientation, the pilot's lack of night…NTSB LAX07CA070Accident · No injuriesData collectionFinal reportPiper PA-28-180 · Jackpot, NVthe pilot's failure to maintain directional control after encountering loose snow conditions on the runway.