NTSB investigations: Piper PA-28-180, 1984
16 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 | 11 |
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 ('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") = 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 ('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 MKC85LA041Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-180 · Stuttgart, ARPlt stated he had attempted an NDB approach to rwy 18 but executed a missed approach when he could not see the rwy when the acft was at 800 ft. the plt pitched the acft to a climb attitude and added full throttle. He continued to state that the acft felt…NTSB ATL85LA038Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Luray Caverns, VAThe acft was landed on a inadequate field during a simulated forced landing that became a real emergency because the fltinstructor cut the mixture to off. The CFI took over the landing at the last part of the approach and told the student to restart the…NTSB SEA84LA236Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Darrington, WAThe acft went off the rwys end into a tree stump and brush during landing. The plt said he landed with excess speed and was unable to stop. The plt recommended that a go-around should have been performed.NTSB SEA84LA200Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-180 · Boulder City, NVPlt executed a forced landing in a field following a loss of power during initial takeoff climb. Post accidnet investigation revealed a large quantity of water in the fuel system. The acft had been parked at an arpt with 1/2 full fuel tanks. The tie down area…NTSB SEA84FA215Accident · 6 fatalField investigationFinal reportPiper PA-28-180 · The Dalles, ORN6499J departed The Dalles municipal arpt shortly after 0930 PDT on a flt to vancouver, WA. N4622T departed chenoweth airfield ( aprx 4 NM west of The Dalles) at about 0930 PDT on a flt to The Dalles municipal arpt. A witness who observed both acft before the…NTSB LAX84FA463Accident · No injuriesField investigationFinal reportPiper PA-28-180 · Bakersfield, CAThe student plt landed long on an intended touch and go landing and therefore, rolled out to a full stop on rwy 31. A 180 deg turn was made at the end in order to takeoff on rwy 13. Prior to initiating the takeoff, according to the student plt, he placed the…NTSB MIA84LA239Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Gainesville, FLThe nose gear tire blew out on landing. Directional control was lost and the acft traveled off the left side of the rwy.NTSB FTW84LA357Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Fort Worth, TXDue to acft parked in close proximity to the right side of the narrow (25 ft) runway and a crosswind from the left, the plt favored the left side of the runway on landing line-up. During the landing roll, he was unable to arrest a left drift before the acft…NTSB NYC84LA281Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-180 · White Marsh, MDThe acft was descended for aprx 7 miles at low power & slow rate for the landing at White Marsh arpt. The descent started at 2800 ft & continued straight in to rwy 27. At about 200 yds from the rwy & at 200 ft AGL the plt decided he needed power to land…NTSB MIA84LA198Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-180 · Port St. Joe, FLWhile on final apch to land at a private arpt, the acft collided with power lines near the apch end of the rwy. The plt stated that he did not see the power lines until just prior to impact. He attempted to fly under the lines, but the vertical stabilizer of…NTSB NYC84FA224Accident · 4 fatalField investigationFinal reportPiper PA-28-180 · Lincoln Park, NJThe acft collided with the ground shortly after takeoff. A following acft plt said the acft was slow and long on takeoffroll and stayed low after takeoff. The acft made a 90 degree right turn and then a 270 degree left turn and was about lined up to land…NTSB DEN84LA198Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Albuquerque, NMWhile en route, the acft's ELT suddenly activated. The plt made an unplanned landing at laguna, NM to correct the ELT problem, then he continued on to coronado arpt at Albuquerque, NM. He said this incident made him tense. After receiving radar vectors to the…NTSB NYC84LA182Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Marlboro, NJThe pilot aborted his takeoff when he noted insufficient acceleration, but lost control of the aircraft, ran off the end of the runwaym thru a ditch and onto railroad tracks.NTSB CHI84LA178Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · La Porte, INThe pilot stated that he initiated the landing flare 'too late,' and the acft landed hard. There was subst damage to theto the landing gear and left wing.NTSB ATL84FA147Accident · Serious injuriesField investigationFinal reportPiper PA-28-180 · Athens, GABefore starting an apch, the plt was advised the wx was: 300 ft obscured, visibility 3/4 mi with light rain & fog. The minimums for a straight-in VOR apch to rwy 2 were 400 ft mda & 1 mi visibility; for a circling apch, the minimums were 433 ft & 1 mi. The…NTSB NYC84LA097Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-180 · Elmira, NYThe acft was descending to land when the engine quit. The pilot attempted to restart the engine with negative results and made a forced landing into a plowed field. The weather conditions were conducive to carburetor ice.