NTSB investigations: Piper PA-30, 1986
9 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\") = 1986
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") = 1986
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 CHI87LA024Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Minneapolis, MNThe pilot flew for an hour trying to get the gear extended, but was unable. After making a gear up landing, an exam revealed the centering cam on the left side of the nose gear was bent and broken. This could have caused the gear to jam and not extend.NTSB LAX87LA013Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Oceanside, CADuring a x-country flt, the plt stated, that just south of los angeles international arpt, the acft's right engine was running rough. At the same time pwr in the left engine began decreasing, then the prop automatically feathered. The plt attempted a re-start…NTSB LAX87LA002Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Holbrook, AZJust after takeoff, the right engine lost power at an altitude of approximately 450 feet. The right propeller was feathered, but the pilot was unable to maintain altitude. Subsequently, the aircraft collided with terrain about 3 miles south of the airport.…NTSB FTW87LA001Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Sulpher, LAThe pilot landed long at a private grass airstrip and deliberately ground looped the aircraft to avoid overrunning the airstrip into a three foot ditch. The nose gear collapsed during the ground loop and the wings and main gears were damaged when the aircraft…NTSB CHI86MA216Incident · No injuriesMajor investigationFinal reportBoeing 737-222 · Lansing, MIPiedmont flt PI255 (a Boeing 737, N749N) was dscndg in visual conds on an IFR clnc when it & a twin commanche (Piper PA-30, N7399Y) converged & passed within a rprtd 50 to 100 ft of each other. The near collision occurred as the PA-30 was cruising westbound…NTSB BFO86FA042Accident · 3 fatalField investigationFinal reportPiper PA-30 · Bowleys Qrtrs, MDDrg arr, TRACON gave the plt the arpt wx & provided vectors for an ILS rwy 32 apch. The plt inquired about a cell that he understood was over the arpt & was advised to standby while the controller (ctlr) checked on it. The ctlr contacted twr psnl who adzd the…NTSB MKC86LA149Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Arkansas City, KSThe certified flight instructor stated that his intentions for this flight were to simulate an engine power loss during the early stages of the takeoff roll and have the student perform a rejected takeoff procedure. According to the c.f.I., at approximately…NTSB LAX86LA192Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Coolidge, AZThe plt shut down the acft eng when it surged during an encounter with turbulence. The plt initiated a precautionary downwind landing on a nearby airstrip and the acft overran the rwy and collided with a fence.NTSB ATL86LA050Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Charlotte, NCPlt reported loss of power on the right eng at about 20 ft alt on takeoff. The acft veered right, the plt aborted the takeoff and touched down on the right side of rwy. The acft struck a mound of dirt and the ldg gear collapsed. The takeoff was initiated from…