NTSB investigations: Piper PA-28-151, 2004
5 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\") = 2004
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") = 2004
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 MIA04CA118Accident · No injuriesData collectionFinal reportPiper PA-28-151 · Sugar Loaf Key, FLThe failure of the pilot to attain the proper touchdown point resulting in a landing overrun and subsequent on-ground collision with trees.NTSB SEA04LA097Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-151 · Easton, WAThe pilot's failure to maintain terrain clearance while maneuvering in mountainous terrain. Mountain terrain was a factor.NTSB FTW04LA094Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Goldwaite, TXThe loss of engine power for undetermined reasons. A contributing factor was the lack of suitable terrain for the forced landing.NTSB DEN04LA046Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Bountiful, UTthe pilot's failure to maintain aircraft control and adequate visual outlook during the landing flare. Contributing factors include the pilot's lack of recent experience, the snow bank, and the snow-covered runway.NTSB NYC04FA056Accident · Serious injuriesField investigationFinal reportPiper PA-28-151 · Danbury, CTThe loss of engine power for undetermined reasons, and the pilot's failure to maintain adequate airspeed.