NTSB investigations: Piper PA-28-151, 1984
10 cases on aircraft the registry lists as Piper PA-28-151. 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
| 1974 | 12 |
|---|---|
| 1975 | 22 |
| 1976 | 25 |
| 1977 | 29 |
| 1978 | 38 |
| 1979 | 22 |
| 1980 | 18 |
| 1981 | 14 |
| 1982 | 9 |
| 1983 | 10 |
| 1984 | 10 |
| 1985 | 5 |
| 1986 | 5 |
| 1987 | 7 |
| 1988 | 10 |
| 1989 | 4 |
| 1990 | 11 |
| 1991 | 9 |
| 1992 | 4 |
| 1993 | 9 |
| 1994 | 6 |
| 1995 | 11 |
| 1996 | 7 |
| 1997 | 8 |
| 1998 | 6 |
| 1999 | 4 |
| 2000 | 2 |
| 2001 | 4 |
| 2002 | 6 |
| 2003 | 4 |
| 2004 | 5 |
| 2005 | 8 |
| 2006 | 3 |
| 2007 | 7 |
| 2008 | 1 |
| 2009 | 7 |
| 2010 | 4 |
| 2012 | 3 |
| 2013 | 3 |
| 2014 | 3 |
| 2015 | 3 |
| 2016 | 1 |
| 2017 | 2 |
| 2018 | 3 |
| 2019 | 2 |
| 2020 | 5 |
| 2021 | 3 |
| 2022 | 4 |
| 2023 | 2 |
| 2024 | 4 |
| 2025 | 2 |
| 2026 | 3 |
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\") = 1984
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102805', '7104223'))
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") = 1984
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102805', '7104223'))
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 MIA85LA054Accident · No injuriesLimited investigationFinal reportPiper PA28-151 · Daytona Beach, FLPlt stated that he was unfamiliar with the arpt and requested assistance to taxi to the ramp. The pilot was told to take the first left turn to ramp, he turned onto an access road to the fire station and collided with a sign that stated 'no taxiway.'NTSB MKC85LA013Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Springfield, MOThe acft collided with trees during a forced landing, while on a dual instructional flt. The CFI said after the climb tocruise the eng began to slow dwn. The CFI took control of the acft to return to arpt of departure. He said the vibrationwas excessive as…NTSB CHI85LA024Accident · Minor injuriesLimited investigationFinal reportPiper PA28-151 · Lake Village, INThe plt reported that he was on final apch to land on a wet, sod rwy when he noticed a flock of geese over the apch end. He added power to fly over the geese then proceeded to touchdown further down the rwy than what he had planned. Due to his speed & the wet…NTSB ATL85FA007Accident · 2 fatalField investigationFinal reportPiper PA-28-151 · Morgantown, NCN2553A was in traffic pattern conducting touch and go landings. N32828 was maneuvering below the traffic pattern and was seen climbing in direction of N2553A. N32828 was flying westerly into the sun. N2553A was seen in a shallow left turn from crosswind to…NTSB SEA84LA234Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Shady Cove, ORThe pilot stated after the accident that he stalled the aircraft at an altitude of 50 ft AGL during takeoff and the acftdescended in a nose low attitude into trees and the ground.NTSB SEA84LA181Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-151 · Creswell, ORThe acft was on a night VFR flt from san carlos, CA, to eugene, OR, when the plt asked apch control how for away the arpt was. ATC informed the plt that the arpt was 16 miles further. About 3 minutes later, the left fuel tank was emptied. The plt switched to…NTSB LAX84LA362Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Sacramento, CAThe plt stated he landed a little long on the 2800 foot dirt road and was unable to stop. The acft traveled off the end of the road and collided with a river bank.NTSB LAX84FA300Accident · Serious injuriesField investigationFinal reportPiper PA-28-151 · Corona, CAThe acft experienced an eng power failure during takeoff & collided with the ground while maneuvering to return to the airport. The plt stated that he 'turned right trying to return to the runway,' & at the same time, 'maintain 80 (KTS IAS), but it (the acft)…NTSB NYC84LA146Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Westerly, RIOn final approach to runway 32, the aircraft contacted trees located approximately 600 yard short of the approach end of the runway. The passenger stated after the accident that as the aircraft approached the runway, he noticed the acft was 'a bit too close…NTSB NYC84FNE01Accident · Minor injuriesFinal reportPiper PA-28-151 · Southwick, MAThe acft lost power & made an emergency forced landing in a school yard. Investigation revealed that only a few drops offuel remained in the powerplant & 1QT plus 1PT remained in the wing tanks with none in the gasolator. There was no evidence of fuel leakage…