NTSB investigations: Piper PA-28-161, PA
29 cases on aircraft the registry lists as Piper PA-28-161. 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
| 1967 | 1 |
|---|---|
| 1979 | 1 |
| 1982 | 1 |
| 1983 | 1 |
| 1984 | 1 |
| 1985 | 2 |
| 1986 | 1 |
| 1987 | 2 |
| 1989 | 1 |
| 1990 | 3 |
| 1991 | 1 |
| 1993 | 2 |
| 1994 | 1 |
| 1997 | 3 |
| 1999 | 1 |
| 2004 | 1 |
| 2006 | 1 |
| 2011 | 1 |
| 2015 | 1 |
| 2016 | 2 |
| 2019 | 1 |
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 c.\"eventStateOrRegion\" = 'PA' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102803', '7102834'))
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 c."eventStateOrRegion" = 'PA' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102803', '7102834'))
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 GAA20CA079Accident · No injuriesData collectionFinal reportPiper PA28 · Quakertown, PAThe student pilot's improper landing flare, which resulted in a hard, bounced landing, and his subsequent failure to maintain directional control, which resulted in a runway excursion and collision with a drainage culvert.NTSB GAA17CA026Accident · Serious injuriesData collectionFinal reportPiper PA 28 · Latrobe, PAThe pilot’s unstabilized approach, which resulted in the airplane’s wing striking the ground while the pilot was maneuvering to realign with the runway.NTSB ERA16CA237Accident · No injuriesData collectionFinal reportPiper PA 28-161 · Honesdale, PAThe pilot's inadequate preflight planning, which resulted in his attempt to take off near the airplane’s maximum gross weight in high-density altitude conditions that degraded the airplane’s takeoff and climb performance and resulted in an aborted takeoff and…NTSB ERA15LA369Accident · No injuriesLimited investigationFinal reportPiper PA 28-161 · Pittsburg, PAAn engine fire, which resulted from the overpriming of a hot engine.NTSB ERA11LA104Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-161 · Benton, PAThe pilot's failure to maintain clearance from terrain during the night flight.NTSB NYC06LA064Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-161 · Smoketown, PAThe pilot's improper pre-flight planning and improper fuel consumption calculations, which resulted in fuel exhaustion and a subsequent loss of engine power.NTSB IAD04FA033Accident · 4 fatalField investigationFinal reportPiper PA-28-161 · Toughkenamon, PAThe pilot's decision to add power, in an attempt to abort the landing after the airplane had veered off the runway. A factor was the pilot's failure to maintain directional control after the landing.NTSB IAD99LA037Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Zelienople, PAThe pilot's inadequate preflight planning to practice crosswind landings in wind that exceeded the airplane's demonstrated capability and his failure to maintain directional control. A factor in the accident was the high wind.NTSB NYC98LA046Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Philadelphia, PAThe pilot's failure to maintain proper distance and altitude during approach which resulted in an undershoot and collision with a fence.NTSB NYC97LA168Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Blairsville, PAthe pilot's inaccurate fuel consumption calculations and improper in-flight planning/decision, which led to fuel exhaustion, loss of engine power, and a forced landing.NTSB NYC97LA075Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Butler, PAthe pilot's misjudgment of distance and speed on final approach; his failure to attain the proper touchdown point; and his failure to perform a go-around, while there was still sufficient airspeed and runway remaining, which resulted in an overrun and…NTSB BFO94FA034Accident · 1 fatalField investigationFinal reportPiper PA-28-161 · Bethel, PAthe pilot attempting visual flight rules (VFR) flight into instrument meteorological conditions and the pilot not maintaining clearance from objects/terrain.NTSB BFO93LA154Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Centre Hall, PAThe pilot misjudged his airspeed and altitude which resulted in the pilot's failure to attain the proper touchdown point resultng in the airplane exiting the runway and colliding with the berm. A related factor was the location of the berm.NTSB NYC93LA179Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · West Mifflin, PAThe pilot's misjudgement of speed and distance, which resulted in a landing overrun of the runway. Factors were an embankment and the pilot not being able to abort the landing.NTSB NYC91LA079Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-161 · Philadelphia, PADue to failure of the induction air control/air filter/screen, which blocked airflow through the carburetor throat.NTSB NYC91LA047Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Easton, PAThe flight instructor allowed the airplane to get too low on final approach during the demonstration of a power off landing.NTSB NYC91LA026Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Saxton, PAAn engine failure due to fuel starvation and the subsequent forced landing in unsuitable terrain. Factors related to the accident were the cfi's inadequate execution of emergency procedures.NTSB NYC90LA111Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Fraconia, PAThe pilot failed to maintain sufficient airspeed to flare for landing. Factors related to the accident were: a power loss due to oil exhaustion, the failure of the pilot to conduct an adequate pre-flight and departing with the oil dip stick loose.NTSB NYC89LA124Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Dushore, PACollision with trees during a rejected takeoff from a private turf strip due to the pilots failure to take advantage of the existing wind.NTSB NYC88DGM03Accident · 1 fatalFinal reportPiper PA-28-161 · Spartansburg, PAThe pilot landed at the franklin, PA airport after encountering fog. After making several phone calls and remaining on the ground for about 37 minutes he departed. About 30 minutes later the aircraft was seen circling at a low altitude, flying in and out of…NTSB NYC88LA024Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Erwinna, PAThe pilot was landing the aircraft on runway 25 at vansant airport. At about 100 feet down the runway, the aircraft veered to the left, off of the runway and slid down an embankment and came to rest after colliding with a tree.NTSB NYC87FA038Accident · 1 fatalField investigationFinal reportPiper PA-28-161 · Glen Mawr, PADrg arrival, the acft was vectored to intercept the ILS rwy 27 localizer (LOC) bfr reaching the munci initial apch fix (iaf), which was 21.5 mi fm the rwy. The ATC controller (ctlr) told the plt to maint 4000' until on the LOC, then clrd him for the apch.…NTSB NYC85LA212Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Doylestown, PAAccording to the plt, on touchdown the acft braking was ineffective due to morning dew on the grass rwy. The acft slid off the end of the rwy and collided with bushes.NTSB NYC85LA069Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Beaver Falls, PAThe student plt was on a supervised solo flt. While landing with an 8 kt rgt x-wind, the acft veered left, went off the rwy & hit a 1 ft deep snowbank, then nosed over. No pre-impact part failure or malfunction was found.NTSB NYC85LA020Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Farmington, PAAccording to the plt, during the landing flare the wind shifted causing the acft to drift off the left side of the rwy striking rwy lights and a pole. Winds were from 230 deg at 10 KTS gusting to 15.NTSB NYC84FGM01Accident · Minor injuriesFinal reportPiper PA-28-161 · Marshburg, PAAfter refueling at ithaca, NY, the plts of two Piper PA-28 acft departed as a flt of two. They had planned to continue their flt back to cincinnati, oh with another en route stop at columbus, OH. The non-instrument rated plt of N8163P was following the lead…NTSB NYC82DA196Accident · No injuriesFinal reportPiper PA-28-161 · Wilkes Barre, PAThe student pilot stated that as he began to taxi, he proceeded about 35 ft and then the aircraft suddenly veered to the left as if the wheel had locked. He applied right rudder, then right brake. However, the aircraft struck a building and an automobile.NTSB NYC80FA014Accident · 1 fatalClosedPiper PA-28 · Watsontown, PANTSB NYC68D0121Accident · No injuriesClosedPiper PA-22 · Somerset, PA