NTSB investigations: Piper PA-28-151, 1985
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\") = 1985
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") = 1985
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 LAX86FA042Accident · 2 fatalField investigationFinal reportPiper PA 28-151 · Lebec, CAAfter receiving a preflight wx briefing that forecast strong headwinds, over mountainous terrain, severe turbulence and pireps of severe turbulence on the proposed flt route. The instructor plt and his student instrument plt took off for a night IFR training…NTSB LAX86FA007Accident · 2 fatalField investigationFinal reportPiper PA-28-151 · Payson, AZThe passenger had a 10:00 medical appointment at the destination arot on the day of the accident. The non-instrument rated, recently certificated pvt plt, requested and received a weather briefing for a proposed VFR flt at 7500 ft MSL from mesa to holbrook,…NTSB NYC85FNA03Accident · Serious injuriesFinal reportPiper PA-28-151 · Newburyport, MAThe pilot attempted a landing at night with an inoperative landing light and no runway lights. After circling the airport 3 or 4 times he attempted a landing. The aircraft received substantial damage and the pilot received serious injuries. The passenger…NTSB NYC85LA167Accident · Minor injuriesLimited investigationFinal reportPiper PA28-151 · Chatham, MADuring the final approach to runway 24, the aircraft was too high and fast. The pilot decided to land on the runway instead of going around. According to the pilot, the aircraft landed too FAR down the runway and went over the end.NTSB CHI85FA253Accident · 2 fatalField investigationFinal reportPiper PA-28-151 · Reedsburg, WINo known witnesses observed the plt preflt the acft or takeoff. He departed in the evening while the arpt was not attended. At aprx 2012 CDT, his son observed & recognized the acft. At that time, the son was at his own home about 1/2 mi from the plt's home.…