NTSB investigations: Piper PA-28-151, 1994
6 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\") = 1994
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") = 1994
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 ATL95FA008Accident · 1 fatalField investigationFinal reportPiper PA-28-151 · Conway, SCThe pilot's failure to maintain a proper altitude during the missed approach, resulting in a collision with trees and terrain. Factors were the weather conditions (low ceiling, fog), and the pilot's diverted attention outside the cockpit.NTSB LAX94LA234Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Simi Valley, CAThe student pilot's failure to properly align the airplane's flightpath over the runway during initial climb. A contributing factor was the student pilot's total lack of recent flying experience.NTSB LAX94LA228Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Sonoma, CAThe pilot's failure to attain the proper touchdown point and his failure to initiate a go-around.NTSB MIA94LA115Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Boca Raton, FLThe failure of the dual student to maintain directional control during landing and the failure of the flight instructor to properly supervise the dual student and take corrective action in a timely manner.NTSB ATL94LA037Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Jasper, ALLoss of engine power for undetermined reasons.NTSB FTW94LA058Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Mckinney, TXThe pilot's improper approach angle.