NTSB investigations: Piper PA-28-180, 2013
10 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\") = 2013
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") = 2013
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 WPR14LA031Accident · Serious injuriesLimited investigationFinal reportPiper PA 28-180 · Big Creek, CAThe loss of engine power due to the improper installation of an oil pressure sending unit by the pilot, who was not a certificated mechanic, which resulted in a forced landing in mountainous terrain.NTSB WPR14CA013Accident · Serious injuriesData collectionFinal reportPiper PA 28-180 · Cody, WYA loss of engine power during climb to cruise for reasons that could not be determined due to no postaccident examination.NTSB CEN14CA041Accident · Minor injuriesData collectionFinal reportPiper PA 28-180 · Benton Harbor, MIThe pilot's failure to maintain aircraft control during engine start.NTSB CEN13LA552Accident · No injuriesLimited investigationFinal reportPiper PA 28-180 · Frankenmuth, MIAn intermittent loss of engine power for reasons that could not be determined because postaccident examinations revealed no anomalies that would have precluded normal operation.NTSB CEN13CA526Accident · No injuriesData collectionFinal reportPiper PA-28-180 · Edgerton, MNThe pilot's delay in aborting the landing which resulted in the airplane contacting the terrain off the departure end of the runway.NTSB WPR13LA384Accident · Serious injuriesLimited investigationFinal reportPiper PA 28 · Sacramento, CAA partial loss of engine power during initial climb for reasons that could not be determined because postaccident examination revealed no evidence of preimpact mechanical malfunction or failure that would have precluded normal operation.NTSB WPR13LA366Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Overgaard, AZThe partial loss of engine power during takeoff due to the separation of the exhaust baffling, which resulted in a partial blockage of airflow. Contributing to the accident was inadequate maintenance of the exhaust system.NTSB CEN13CA475Accident · No injuriesData collectionFinal reportPiper PA-28-180 · Poteau, OKThe pilot’s application of excessive left rudder during the takeoff roll, resulting in a loss of directional control, his failure to correct the excursion with opposite rudder, and his failure to abort the takeoff in a timely manner.NTSB CEN13CA474Accident · No injuriesData collectionFinal reportPiper PA-28-180 · Clare, MIThe flight instructor's failure to adequately monitor the landing approach, his delayed corrective action and his failure to maintain directional control that resulted in the airplane's collision with a ditch adjacent to the runway. The student pilot's…NTSB CEN13CA247Accident · Minor injuriesData collectionFinal reportPiper PA-28-180 · Owatonna, MNThe pilot’s loss of directional control during an aborted landing.