NTSB investigations: Piper PA-30, 1988
3 cases on aircraft the registry lists as Piper PA-30. 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
| 1964 | 35 |
|---|---|
| 1965 | 37 |
| 1966 | 52 |
| 1967 | 56 |
| 1968 | 33 |
| 1969 | 43 |
| 1970 | 36 |
| 1971 | 33 |
| 1972 | 40 |
| 1973 | 33 |
| 1974 | 32 |
| 1975 | 17 |
| 1976 | 17 |
| 1977 | 18 |
| 1978 | 27 |
| 1979 | 17 |
| 1980 | 19 |
| 1981 | 12 |
| 1982 | 12 |
| 1983 | 8 |
| 1984 | 15 |
| 1985 | 8 |
| 1986 | 9 |
| 1987 | 9 |
| 1988 | 3 |
| 1989 | 5 |
| 1990 | 12 |
| 1991 | 7 |
| 1992 | 7 |
| 1993 | 9 |
| 1994 | 2 |
| 1995 | 4 |
| 1996 | 6 |
| 1997 | 3 |
| 1998 | 8 |
| 1999 | 5 |
| 2000 | 4 |
| 2001 | 6 |
| 2002 | 9 |
| 2003 | 4 |
| 2004 | 8 |
| 2005 | 4 |
| 2006 | 4 |
| 2007 | 10 |
| 2008 | 7 |
| 2009 | 8 |
| 2010 | 5 |
| 2011 | 7 |
| 2012 | 5 |
| 2013 | 5 |
| 2014 | 5 |
| 2015 | 3 |
| 2016 | 3 |
| 2017 | 2 |
| 2018 | 3 |
| 2019 | 3 |
| 2020 | 7 |
| 2021 | 8 |
| 2022 | 7 |
| 2023 | 6 |
| 2024 | 3 |
| 2025 | 4 |
| 2026 | 6 |
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 ('7103002'))
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 ('7103002'))
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 ATL89FA004Accident · 1 fatalField investigationFinal reportPiper PA-30 · La Follette, TNThe pilot reported an autopilot problem and was not able to maintain control of the airplane. The airframe components were scattered in a circular pattern. All fractures displayed overload failures. The wreckage examination failed to disclose any system or…NTSB BFO88LA072Accident · No injuriesLimited investigationFinal reportPiper PA-30-160R · Chantilly, VAThe instr & stu plt were doing a practice landing on rwy 27 at the front royal airport when the acft landed hard and bounced about 20 ft high. A go around was made, however, the landing gear would not retract. After two flyovers of the arpt it was confirmed…NTSB MIA88LA113Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Jupiter, FLThe plt stated that he had completed a ldg away from his home base without the gear down & locked lights being illuminated. He stated that he had assumed the lights were 'burned out'. Upon departure, he retracted the gear & flew to his home airport. Upon…