NTSB investigations: Piper PA-28-140, 2001
21 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\") = 2001
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") = 2001
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 LAX02LA057Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Show Low, AZThe pilot's inadequate compensation for wind conditions and his failure to maintain directional control. Contributing factors were a crosswind and wind gusts.NTSB FTW02LA023Accident · Minor injuriesLimited investigationFinal reportPiper PA28-140 · Wilton, ARthe pilot's failure to obtain a proper touchdown point and his excessive approach speed during a forced landing. A contributing factor was the total loss of engine power for undetermined reasons.NTSB LAX02FA004Accident · No injuriesField investigationFinal reportPiper PA-28-140 · Van Nuys, CAThe failure of the air traffic controller to provide effective separation on the runway surface as specified in FAA Order 7110.65, Paragraph 3-9-6.NTSB MIA01LA219Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Wilgrove, NCThe failure of maintenance personal to properly reconnect the throttle-cable-to carburetor attachment, resulting in a throttle cable disconnection while in the landing pattern, and collision with trees. A factor in the accident was the failure of the pilot to…NTSB IAD01LA094Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Odenton, MDImproper maintenance inspections, which resulted in a blocked carburetor.NTSB DEN01LA127Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Calhan, COthe loss of engine power due to fuel contamination (water). A contributing factor was the lack of suitable terrain on which to perform a forced landing.NTSB NYC01LA173Accident · Minor injuriesLimited investigationFinal reportPiper PA28-140 · Schuyler, NYThe pilot's delayed go-around, which resulted in an in-flight collision with trees. A factor in this accident was the crosswind conditions.NTSB CHI01LA197Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-140 · Mecosta, MIthe inadequate preflight planning/preparation by the pilot and fuel starvation. Additional causes were the aircraft control not maintained, and the inadvertent stall by the pilot.NTSB CHI01LA199Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Albion, ILthe maintenance performed on the airplane by the unqualified pilot The unsuitable takeoff area selected by the pilot was an additional cause. The ditch was a contributing factor.NTSB NYC01LA153Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-140 · Rochester, NYFuel exhaustion, due to the student pilot's failure to monitor his fuel supply.NTSB ANC01LA073Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Haines, AKThe pilot's selection of unsuitable terrain for takeoff. Factors in the accident were soft terrain, and the pilot's delay in aborting the takeoff.NTSB LAX01FA208Accident · 1 fatalField investigationFinal reportPiper PA-28-140 · Lanai City, HIthe CFI's inadequate in-flight planning/decision making, inadequate supervision, and his delayed remedial action, which resulted in controlled flight into terrain.NTSB MIA01LA159Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-140 · Dahlonega, GAThe failure of the No. 3 exhaust valve due to fatigue cracking for undetermined reasons, which resulted in a partial loss of engine power and an in-flight collision with a building during an attempted forced landing to unsuitable terrain..NTSB NYC01LA124Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-140 · Elizabethtown, KYThe pilot's failure to maintain directional control during the takeoff roll.NTSB SEA01LA068Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Scapoose, ORthe pilot's failure to maintain a speed above minimum in-flight stall speed (Vs). Factors include gusty winds at the time of the attempted landing.NTSB IAD01LA044Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Hammonton, NJpilot's failure to maintain directional control during the landing roll-out. A factor was the crosswind.NTSB SEA01FA064Accident · 2 fatalField investigationFinal reportPiper PA-28-140 · Greenwater, WAFailure to maintain clearance from mountainous terrain.NTSB CHI01LA103Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Port Huron, MIThe pilot not maintaing a proper glide path during the simulated forced landing. Factors were flight instructor's inadequate supervision and the wind gusts.NTSB CHI01LA143Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Detroit Lakes, MNAltitude/clearance not maintained from the transmission wires during a low altitude flight/maneuver performed by the pilot. A factor to the accident was the transmission wires.NTSB FTW01LA066Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-140 · Owasso, OKthe pilot's delay in switching the fuel selector, which resulted in fuel starvation in cruise flight.NTSB MIA01LA065Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-140 · Tifton, GAThe pilot's failure to properly judge his altitude (too high) during a forced landing to a runway. The pilot made a 270-degree turn in an attempt to lose altitude resulting in a forced landing in a swampy/marshy area short of the runway. Contributing to the…