NTSB investigations: Piper PA-28-180, 1983
29 cases on aircraft the registry lists as Piper PA-28-180. 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 | 47 |
|---|---|
| 1965 | 72 |
| 1966 | 117 |
| 1967 | 131 |
| 1968 | 107 |
| 1969 | 92 |
| 1970 | 98 |
| 1971 | 99 |
| 1972 | 78 |
| 1973 | 85 |
| 1974 | 82 |
| 1975 | 64 |
| 1976 | 76 |
| 1977 | 54 |
| 1978 | 59 |
| 1979 | 37 |
| 1980 | 38 |
| 1981 | 26 |
| 1982 | 21 |
| 1983 | 29 |
| 1984 | 16 |
| 1985 | 24 |
| 1986 | 18 |
| 1987 | 23 |
| 1988 | 21 |
| 1989 | 29 |
| 1990 | 20 |
| 1991 | 12 |
| 1992 | 25 |
| 1993 | 17 |
| 1994 | 18 |
| 1995 | 21 |
| 1996 | 21 |
| 1997 | 16 |
| 1998 | 24 |
| 1999 | 17 |
| 2000 | 17 |
| 2001 | 13 |
| 2002 | 18 |
| 2003 | 17 |
| 2004 | 18 |
| 2005 | 19 |
| 2006 | 9 |
| 2007 | 13 |
| 2008 | 7 |
| 2009 | 15 |
| 2010 | 9 |
| 2011 | 15 |
| 2012 | 12 |
| 2013 | 10 |
| 2014 | 9 |
| 2015 | 10 |
| 2016 | 11 |
| 2017 | 10 |
| 2018 | 11 |
| 2019 | 12 |
| 2020 | 9 |
| 2021 | 11 |
| 2022 | 6 |
| 2023 | 24 |
| 2024 | 9 |
| 2025 | 7 |
| 2026 | 10 |
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\") = 1983
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102808'))
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") = 1983
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102808'))
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 MKC84LA044Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Manhattan, KSThe plt stated that during her arrival at Manhattan, KS, the rwy had patches of snow & was surrounded by snow covered terrain. Just prior to landing, she became aware of a snowbank at the apch end of the rwy. She took evasive action, but the right main gear…NTSB ATL84FA054Accident · 2 fatalField investigationFinal reportPiper PA-28-180 · Lexington, TNThe acft collided with the ground in a vertical descent during IMC weather on a x-country flt. The plt had filed an IFR flt plan but he was a student with limited experience and was not instrument rated. Also he was carrying a passenger. The controller who…NTSB NYC84LA026Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Hackettstown, NJAccording to the plt, he made an extended pattern to keep spacing on a slower acft that was landing. He stated that he went thru the landing checklist & everything seemed normal. On final apch, the acft got a little low, but when the throttle was advanced,…NTSB DEN84LA014Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Englewood, COThe plt reported that during arrival, he was receiving vectors for an ILS when he entered a descent from 9000 to 8500 ft MSL. He entered clouds during the descent & applied carburetor (carb) heat immediately before entering the clouds. He said that the acft…NTSB LAX84LA016Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Yuma, AZThe plt stated that prior to departing lake havasu city he visually inspected the fuel tanks & observed that both tanks were slightly less than 1/2 full. Based on this observation he thought the acft had 20-30 gals of fuel which would be sufficient for the…NTSB MIA83IA237Incident · No injuriesIncident investigationFinal reportPiper PA 28-180 · Verna, FLAcft made an emergency due to powerplant failure. Access to the wreckage was never gained.NTSB CHI83FA410Accident · 2 fatalField investigationFinal reportPiper PA-28-180 · Forestville, WIThe acft was observed making low passes, 150-200 ft AGL, over a wooded area & then strike a radio antenna at the 207-FT level. The acft rolled inverted & impacted the ground. Members of the plt's aero club stated that the plt & pax were probably spotting for…NTSB DEN83FTK05Accident · Serious injuriesFinal reportPiper PA28-180C · Sturgis Muni., SDThe acft crashed on the approach end to runway 11 during an aborted landing. The plt stated the acft was high so he applied full power and retracted the flaps. He said he retracted the flaps too fast and lost control of the acft. The nose gear was broken off,…NTSB ATL83LA331Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Mt. Airy, NCA loss of engine power during takeoff for undetermined reasons. A contributing factor was unsuitable terrain for a forced landing.NTSB NYC83LA201Accident · No injuriesLimited investigationFinal reportPiper PA-28-180G · Linden, PAThe acft collided with powerlines during a night forced landing after fuel exhaustion.NTSB ATL83LA314Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Normantown, WVThe plt noticed smoke in the cockpit, & soon thereafter observed the oil press gage reading zero. The plt was given radar vectors to the nearest arpt but he was unable to reach it. The acft collided with trees & a powerline during the forced landing.…NTSB CHI83LA337Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-180 · Youngstown, OHWhile on a x-country flt, the eng lost power before the acft arrived at the destination arpt. The plt switched fuel tanks, turned on the boost pump & restarted the eng, but aprx 1 min later power was lost again. There was insufficient altitude to glide to the…NTSB MIA83LA185Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Brandon, FLThe plt stated that he aborted the takeoff after lift-off from rwy 09. During the sequence, the main gear contacted a barbed wire fence, then the acft was landed in a field & subsequently nosed over in a pond. The plt reported that he was using soft field…NTSB LAX83LA343Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Auburn, CAWitnesses observed the acft make two approaches to rwy 25. During the second approach the acft got close to the rwy and drifted to the right. Power was applied and the acft collided with a tree. The wind was gusting to 30 KTS.NTSB LAX83LA318Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Clearlake, CAThe acft crashed in a flat area covered with 6 ft bushes after the engine quit during a go-around. The engine had quit on the downwind and started again after the plt switched tanks. The acft was high on final and after go-around was initiated the engine quit…NTSB ATL83LA214Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Westminster, MDThe plt stated that he intended to fly to a 1600 ft private strip with trees on both ends. During the approach, he had planned to make a full stop landing. However, after touchdown, he decided to make it a touch-and-go landing. After lift-off, he felt the…NTSB FTW83FA254Accident · 5 fatalField investigationFinal reportPiper PA-28-180 · Haskell, TXThe acft crashed while on a flt in an area where thunderstorm warnings were in effect. There were no known witnesses to the actual crash, but 2 or 3 local residents heard an acft eng at about the estimated time of the accident. One resident about 1/4 mi from…NTSB CHI83LA234Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Delphi, INDuring a local flt, the plt noticed clouds that looked like smoke approaching the arpt from the west. He stated that he decided to land to keep from losing visibility. The plt stated that while approaching rwy 18 with a x-wind from 270 deg, he had to crab to…NTSB LAX83LA251Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Aguanga, CAThe acft collided with an abandoned auto during an aborted takeoff. The pilot said he applied full power during takeoff and accelerated to about 85 mph and rotated. At about 15 ft AGL the engine seemed to lose power. The pilot said the engine did not sputter…NTSB ANC83LA082Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Kenai, AKThe pilot stated that on a short final approach he encountered a windshear. The pilot only had 5 hours in this type acftand had little experience landing at the location of the accident. This field has no facilities except a windsock. It isbordered by trees…NTSB DEN83FA108Accident · 1 fatalField investigationFinal reportPiper 28-180 · Alpine, WYThe acft collided with mountainous terrain in IMC weather. The pilot had been briefed on the weather. Part of the observation called for mountain obscuration by clouds or precipitation. A person who resides in Alpine, WY said the mountain tops were obscured…NTSB DEN83LA107Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Erie, CODuring a second touch & go the acft ran off the side of the rwy. The plt last flew on 10/4/82 for about a 1 hr flt.NTSB ANC83FAA06Accident · 1 fatalFinal reportPiper PA-28-180 · Nome, AKAt 1205 bdt, the plt reported departing rwy 20 on an IFR flt. At that time, the bases of the clouds were reported to be at aprx 600 to 700 ft with the tops at 3500 ft & another cloud layer was above that. At aprx 1207, the acft crashed on the arpt boundry,…NTSB CHI83LA170Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-180 · Rice Lake, WIThe acft hit a ditch and nosed over during a forced landing after the engine quit. The plt was on a cross country and had landed enroute 3 times without refueling. With the assistance of eau claire fss he overflew Rice Lake arpt but could not find it. The…NTSB FTW83LA161Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Guthrie, OKThe pilot said he was waiting for an acft to clear the rwy. As he started to turn downfield for takeoff he pushed the throttle in, advancing the power instead of retarding it. The aircraft crossed the runway at an angle, became airborne and hit a tree. The…NTSB ATL83LA115Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-180 · Pulaski, VAThe aircraft collided with trees during a forced landing after fuel exhaustion on the final leg of a cross-country. The pilot made 5 enroute stops and no refueling was performed at any point during those stops. Departing the last stop the pilot estimated 45…NTSB CHI83LA106Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Vernon, ILThe aircraft ran off the end of a runway and collided with a ditch. The student pilot on his first solo cross country had become disoriented and landed 95 miles off course. He had been flying 2 hours and 30 minutes. He was supposed to reach enroute stop after…NTSB CHI83LA100Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Chicago, ILThe acft collided with a parked acft on the ramp. The student pilot started the acft on a snow covered icy ramp at nightthe parking brakes were set but when the engine started the acft taxied into another acft. After the accident the brakesof the acft were…NTSB MIA83LA068Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Palmetto, FLAccording to the pilot he lost directional control of the aircraft during the landing roll. The aircraft veered to the left and went off the runway colliding with a drainage ditch and fence. No mechanical failure of malfunctions were reported.