NTSB investigations: Piper PA-28-151, 1993
9 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\") = 1993
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") = 1993
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 MIA94FA030Accident · 1 fatalField investigationFinal reportPiper PA-28-151 · Daytona Beach, FLLoss of aircraft control for an undetermined reason.NTSB BFO94LA007Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-151 · Greentown, PAThe pilot's selection of the wrong runway, and his delay in attempting a go-around which resulted in an inflight collision with the trees. A related factor was the unfavorable wind.NTSB CHI94LA019Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Allendale, MIImproper in-flight planning/decision by the pilot, after encountering unfavorable winds and a low fuel level, which resulted in fuel exhaustion. The unfavorable wind was a related factor.NTSB BFO93LA182Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Painesville, OHThe pilot's attempt to land with excessive airspeed, his improper use of the brakes, and his delay in performing remedial action.NTSB FTW93LA248Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Tulsa, OKThe loss of engine power and engine fire for undetermined reasons.NTSB ATL93LA080Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Lafayette, GAThe failure of the pilot to maintain control of the aircraft.NTSB NYC93LA081Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Farmingdale, NYThe pilot's inadequate compensation for wind conditions and failure to maintain control of the airplane. The crosswind was a related factor.NTSB BFO93LA055Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Monticello, MEA disconnection of the fuel line, which resulted in fuel starvation and loss of engine power. A related factor was the lack of suitable terrain for an emergency landing.NTSB NYC93LA062Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · New Cumberland, PAThe loss of engine power for undetermined reasons, resulting in a forced landing in the river.