NTSB investigations: Piper PA-28-151, 1988
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\") = 1988
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") = 1988
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 MKC89LA036Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Lakeview, ARDuring a personal cross country flight, the newly certificated private pilot said he was attempting to land on a 3200 foot grass strip with an existing gusting crosswind. He lost directional control during the landing, hit a runway light, tearing off the left…NTSB LAX89LA041Accident · Minor injuriesLimited investigationFinal reportPiper PA-28 · Modesto, CADuring an ILS approach in night instrument meteorological conditions, the pilot allowed the airspeed to diminish resulting in the airplane stalling. Before the pilot could regain control, the airplane collided with the terrain short of the runway. There were…NTSB MIA89LA029Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Lajas, PRThe plt filled the fuel tanks, made three touch-&-go landings, then departed on a x-country flt. After aprx 1.5 hrs of flt, he elected to reverse course & land at an alternate arpt since he had inadequate fuel to reach his destn. Realizing the fuel supply was…NTSB CHI89LA010Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Fairview Hts., ILFuel exhaustion due inaccurate fuel consumption calculations.NTSB MKC89LA005Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Cedar Rapids, IAWhile conducting a part 135 air taxi operation, the pilot said his engine began running rough about 7 miles from his destination apt. Emergency procedures were initiated and a call to the control tower declaring an emergency was made. Unable to reach the apt,…NTSB NYC88LA245Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Carlton Center, NYPlt stated he was landing to the west and touched down about half way down a 2,000 ft grass strip. The plt also said the grass was wet and the wheel braking was ineffective. The plt elected to keep the airplane on the ground due to obstacles at the end of the…NTSB CHI88LA238Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Kenosha, WIWhile on a VFR approach to the airport, at night, the pilot misidentified the street lights in a mobile home park as the runway lights and descended into wires. Afterward the pilot was able to continue to the intended runway and made a successful landing.…NTSB ATL88FA220Accident · No injuriesField investigationFinal reportPiper PA-28-151 · La Grange, GAThe PIC stated he had a hardover in the single axis autopilot which resulted in the acft constantly turning right. Therefore due to the continous bank he elected to make a precautionary landing in a lake versus on land. The acft impacted in a lake left of the…NTSB LAX88LA142Accident · 1 fatalLimited investigationFinal reportPiper PA-28-151 · Valley Center, CAWitnesses observed the acft rotate to a high pitch attitude during the initial climb after takeoff. They said the acft then entered a left turn & descended to the ground. Impact occurred on rising terrain, beyond a gully, about 200 ft east of the departure…NTSB MIA88LA129Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Terra Ceia, FLWhile on a cross country flt, the plt elected to return to the departure point due to 'bad weather.' He later advised tower personnel when the flt was 10 miles south, inbound for landing. The plt was given landing information after which he reported a loss of…