NTSB investigations: Piper PA-30, 1984
15 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\") = 1984
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") = 1984
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 ATL85LA073Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Sparta, TNDual engine stoppage. Fuel tanks topped before takeoff. Plt had filed IFR en route but the wind had shifted to a 30 kt headwind. Plt became concerned about fuel remaining and made an instrument apch which was missed because of low clouds. During course to an…NTSB LAX85LA061Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Garberville, CAThe plt reported that on his first attempt to land he was 'too high' so he made a go-around. On the second apch to the 3050 ft rwy, he was flying at 110 mph. He landed long, applied brakes & skidded off the dept end of the rwy. The lt tire blew-out,…NTSB DEN85FA043Accident · 3 fatalField investigationFinal reportPiper PA-30-160 · Albuquerque, NMThe flt was en route from forth worth, TX, to santa fe, new Mexico, when the plt decided to divert to Albuquerque. The a/c crashed while being vectored for an ILS approach to rwy 8. The plt received his instrument rating slightly more than 6 mos before the…NTSB MIA85LA060Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Jacksonville, FLElectrical malfunctions caused the loss of air to ground communications and acft navigational equipment. The plt became lost about 70 mi east of Jacksonville, FL. With the help of another acft the plt located the arpt and radio communications were temporarily…NTSB MIA85FA022Accident · Serious injuriesField investigationFinal reportPiper PA-30 · Jasper, FLDue to a low fuel state the plt elected to make a precautionary landing on a road. Power lines and poles forced the plt to land in unimproved terrain next to the road. During touch down the left wing struck a dirt bank. Exam of the wreckage revealed that 3…NTSB FTW85FA015Accident · 2 fatalField investigationFinal reportPiper PA-30 · Port Mansfield, TXAcft crashed in a marsh area during a night recurrency training flt. Acft appeared to have contacted the terrain in an uncontrolled 90 deg left bank. PIC received his last medical certificate on 5/7/70. Investigation disclosed PIC was under medication for…NTSB FTW85LA007Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Amarillo, TXDuring the lndg roll, all 3 lndg gear collapsed. The plt stated that on short final he inadvertantly retracted the gear instead of the flaps. He immediately cycled it back down butthe gear collapsed shortly after touchdown.NTSB NYC84LA245Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Manahawkin, NJThe acft descended out of control into trees and slid down an embankment. The plt said everything seemed normal on takeoff until the acft was put into a climb at about 93 mph at 50 ft AGL the acft began vibrating and veered about 90 degrees to the right. An…NTSB MIA84LA189Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Clewiston, FLThe plt stated that before the flt, he visually checked the main tanks & the fuel gages indicated 1/4 full on each side. Before reaching the destination, an eng lost power, & shortly after that, the other eng lost power, both from fuel exhaustion. The plt had…NTSB CHI84LA219Accident · Minor injuriesLimited investigationFinal reportPiper PA-30 · Berrien Springs, MIThe acft crashed shortly after takeoff near the end of the rwy. The sequence began when the plt noticied that acft acceleration was 'a bit slow' on the rwy. Then a noticable drop in RPM on the right engine occurred at about halfway down the 3100 ft rwy. The…NTSB ATL84FA187Accident · Serious injuriesField investigationFinal reportPiper PA-30 · Charlotte, NCPlt departed rwy 18L and shortly thereafter reported to the tower that he had a stuck trim. The plt was cleared to land on rwy 18R. Witnesses observed the acft descend rapidly on downwind to approx 300 to 500 ft AGL and make a steep (90 to 120 degree) right…NTSB ATL84FA118Accident · No injuriesField investigationFinal reportPiper PA 31-350 · Atlanta, GAThe aircrews of a Piper PA-31, N62849, & a Piper PA-30, N7047Y, proceeded to taxi at dawn from a cargo ramp to rwy 26. Their taxi route was down a parallel taxiway. The PA-31 plt stopped at a glide slope hold line which was located near the end of the…NTSB MIA84FA092Accident · 3 fatalField investigationFinal reportPiper PA-30 · Sarasota, FLShortly after takeoff the acft entered a descending left turn, struck a wire, a car, and a tree before contacting a building and exploding. A passenger reported that the stall warning horn had activated at least twice during the initial takeoff climb prior to…NTSB ATL84FA099Accident · 1 fatalField investigationFinal reportPiper PA-30-160 · Massies Mill, VAWhile en route, the plt was progressing northbound when he contacted the Washington fss at 2134 EST for updated wx info. At that time, he described his position as north of lynchburg, VA. The fss briefer noted that his voice was normal, his manner was calm &…NTSB FTW84FA126Accident · 1 fatalField investigationFinal reportPiper PA-30B · Hugo, OKAccording to witnesses, the acft was having some kind of problem after takeoff. It entered a nose high attitude, went to the right & crashed. An exam revealed that it had impacted in a nose down attitude. The landing gear was found in a down & locked…