NTSB investigations: Piper PA-28-140, 2012
17 cases on aircraft the registry lists as Piper PA-28-140. 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 | 35 |
|---|---|
| 1965 | 102 |
| 1966 | 177 |
| 1967 | 263 |
| 1968 | 182 |
| 1969 | 227 |
| 1970 | 220 |
| 1971 | 230 |
| 1972 | 189 |
| 1973 | 183 |
| 1974 | 169 |
| 1975 | 141 |
| 1976 | 129 |
| 1977 | 123 |
| 1978 | 118 |
| 1979 | 83 |
| 1980 | 66 |
| 1981 | 76 |
| 1982 | 63 |
| 1983 | 40 |
| 1984 | 48 |
| 1985 | 35 |
| 1986 | 40 |
| 1987 | 42 |
| 1988 | 46 |
| 1989 | 30 |
| 1990 | 45 |
| 1991 | 46 |
| 1992 | 30 |
| 1993 | 31 |
| 1994 | 45 |
| 1995 | 29 |
| 1996 | 25 |
| 1997 | 30 |
| 1998 | 27 |
| 1999 | 21 |
| 2000 | 30 |
| 2001 | 21 |
| 2002 | 24 |
| 2003 | 19 |
| 2004 | 17 |
| 2005 | 21 |
| 2006 | 20 |
| 2007 | 23 |
| 2008 | 16 |
| 2009 | 12 |
| 2010 | 16 |
| 2011 | 8 |
| 2012 | 17 |
| 2013 | 20 |
| 2014 | 15 |
| 2015 | 18 |
| 2016 | 16 |
| 2017 | 15 |
| 2018 | 21 |
| 2019 | 17 |
| 2020 | 16 |
| 2021 | 20 |
| 2022 | 17 |
| 2023 | 18 |
| 2024 | 13 |
| 2025 | 9 |
| 2026 | 12 |
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\") = 2012
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102802'))
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") = 2012
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102802'))
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 CEN13FA051Accident · 1 fatalField investigationFinal reportPiper PA-28-140 · Anadarko, OKThe pilot’s use of excessive bank angle while maneuvering in the airport traffic pattern, which resulted in an accelerated stall.NTSB CEN13FA030Accident · 2 fatalField investigationFinal reportPiper PA-28-140 · Maryland Heights, MOThe pilot’s failure to activate the carburetor heat while operating in conditions conducive to carburetor icing, which resulted in a loss of engine power due to carburetor ice.NTSB ERA13LA025Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Allentown, PAThe operator's failure to perform magneto inspections per the manufacturer's recommendations and failure to comply with the engine manufacturer's recommended time interval for engine overhaul, which resulted in defects in the magnetos going undetected and the…NTSB ERA13CA011Accident · No injuriesData collectionFinal reportPiper PA-28-140 · Beltzville, PAThe flight instructor’s improper fuel management, which resulted in a loss of engine power due to fuel starvation.NTSB ERA12CA585Accident · No injuriesData collectionFinal reportPiper PA-28-140 · Maryville, TNThe pilot’s failure to plan and execute a takeoff that assured obstacle clearance at the departure end of the runway, which resulted in a collision with trees.NTSB CEN12LA651Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Boonville, INA total loss of engine power during initial climb due to fuel starvation for reasons that could not be determined because postaccident examination could not verify whether the fuel selector was properly positioned before takeoff.NTSB WPR12CA368Accident · No injuriesData collectionFinal reportPiper PA-28-140 · McMinnville, ORThe pilot’s loss of directional control during the takeoff roll, which resulted in a runway excursion.NTSB CEN12LA569Accident · No injuriesLimited investigationFinal reportPiper PA28 · Leesburg, OHThe pilot's improper preflight planning and decision to attempt a takeoff from a runway that was too short for conditions, which resulted in the airplane settling into terrain.NTSB ERA12LA442Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-140 · Pensacola, FLA partial loss of engine power during initial climb for reasons that could not be determined because examination of the engine did not reveal any anomalies that would have precluded normal operation.NTSB ERA12LA425Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Lakewood, NJThe loss of engine power during climb for reasons that could not be determined during postaccident examination of the engine and engine systems or during postaccident operational testing of the engine.NTSB WPR12CA209Accident · Minor injuriesData collectionFinal reportPiper PA-28-140 · Sula, MTThe pilot's inability to maintain clearance from terrain while operating in a downdraft over mountainous terrain.NTSB ERA12RA367Accident · 2 fatalForeign investigationBeech V35B · Sumerduck, VAOn May 28, 2012, about 1604 eastern daylight time, a Beech V35B, N6658R, and a Piper PA-28-140, N23SC, collided in flight in the vicinity of Sumerduck, Virginia. The Beech was destroyed, and the pilot and flight instructor were fatally injured; the Piper was…NTSB WPR12LA165Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-140 · San Manuel, AZThe pilot’s failure to maintain directional control during the takeoff, which resulted in a runway excursion.NTSB WPR12CA142Accident · No injuriesData collectionFinal reportPiper PA-28-140 · Jean, NVThe student pilot did not maintain directional control during the landing roll.NTSB CEN12LA195Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Indianapolis, INThe student pilot did not maintain directional control while practicing a soft-field takeoff.NTSB ERA12CA172Accident · No injuriesData collectionFinal reportPiper PA-28-140 · Greenville, SCThe pilot’s loss of directional control during the landing roll, which resulted in a runway excursion.NTSB WPR12LA087Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Chehalis, WAThe pilot did not correctly manage his glide profile during a simulated engine-out forced landing. Contributing to the accident was the pilot's decision not to add additional engine power, which resulted in a runway undershoot.