NTSB investigations: Piper PA-28-161
32 cases on aircraft the registry lists as Piper PA-28-161, where the first occurrence was “In flight collision with object”. 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
| 1982 | 3 |
|---|---|
| 1983 | 2 |
| 1985 | 2 |
| 1986 | 2 |
| 1987 | 2 |
| 1988 | 1 |
| 1989 | 2 |
| 1990 | 2 |
| 1991 | 1 |
| 1992 | 2 |
| 1993 | 3 |
| 1994 | 3 |
| 1997 | 1 |
| 1998 | 1 |
| 1999 | 1 |
| 2000 | 1 |
| 2003 | 1 |
| 2005 | 1 |
| 2007 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102803', '7102834')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 220))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102803', '7102834')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 220))
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 NYC07CA181Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Winchester, VAThe pilot's inadequate preflight planning.NTSB DFW05LA054Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Decatur, TXThe student pilot's failure to maintain obstacle clearance and the instructor's inadequate supervision. Contributing factors were the prevailing dark night conditions, and the power line.NTSB SEA03LA131Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Stuart Island, WAThe pilot's failure to maintain clearance while maneuvering to land. Contributing factors included the tree and the sunglare condition.NTSB NYC00LA149Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Miamisburg, OHThe CFI's delayed remedial action.NTSB NYC99FA123Accident · 3 fatalField investigationFinal reportPiper PA-28-161 · West Dover, VTWas the failure of the pilot to maintain control of the airplane during an aborted landing. Factors were the pilot's lack of familiarity with the airplane, the variable winds, and night conditions.NTSB MIA99LA059Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-161 · Conyers, GAThe pilot's decision to attempt a touch-and-go landing with insufficient runway remaining, and his failure to maintain adequate clearance from an object (tree).NTSB CHI98LA075Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Boone, IAfailure of the pilot to maintain sufficient altitude/clearance from obstruction(s), while flying low over a river. The obstruction (power line) was a related factor.NTSB SEA95LA024Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Auburn, WAThe pilot-in-command's not maintaining clearance from the power lines. A factor was the pilot-in-command's not maintaining the proper VASI glideslope.NTSB CHI94LA077Accident · No injuriesLimited investigationFinal reportPiper PA-28-160 · Wichita, KSThe pilot's failure to attain the proper touchdown point and delay in aborting the landing. The pilot's inadequate training was a factor.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 BFO94FA015Accident · 4 fatalField investigationFinal reportPiper PA-28-161 · Northampton, MAFailure of the air traffic control (ATC) facility to identify and provide the required traffic information to the jump aircraft before release of the jumper(s). A factor related to the accident was: inadequate visual lookout by the pilot of the jump aircraft.NTSB MIA93LA153Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-161 · Jacksonville, FLFailure of the pilot in command to maintain directional control during the landing. Contributing to the accident was the excessive airspeed while landing and failure of the pilot to recover from the bounced landing.NTSB LAX93FA215Accident · 2 fatalField investigationFinal reportPiper PA-28-161 · Grass Valley, CAThe pilot prematurely raising the airplane's flaps at an airspeed insufficient to maintain flight which resulted in an inadvertent stall mush condition. A factor in this accident was the darkness of the night.NTSB BFO92LA099Accident · Serious injuriesLimited investigationFinal reportPiper PA28-161 · Brentwood, NHA delay by the pilot in aborting the landing which resulted in failure to clear the obstacles.NTSB BFO92LA070Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Morrisville, VTThe pilot's failure to maintain clearance with the terrain. Contributing to the accident was a dark night and the lack of familiarity with the geographic area.NTSB DEN91FA097Accident · Serious injuriesField investigationFinal reportPiper PA-28-161 · Denver, COImproper planning/decision by the pilot. Factors related to the accident were: a tail wind, the high density altitude, the pilot's failure to properly lean the mixture, and his failure to use all available runway.NTSB MIA91FA035Accident · 1 fatalField investigationFinal reportPiper PA-28-161 · Bunnell, FLFailure of the pilot to maintain altitude, while maneuvering at night over an unlighted area, which resulted in a collision with trees. Factors related to the accident were: darkness and possible spatial disorientation of the pilot due to lack of visual ques.NTSB ATL90FA061Accident · 1 fatalField investigationFinal reportPiper PA-28-161 · Norris, TNThe student pilot's misjudged descent which resulted in a collision with trees and the ground. A factor was that the pilot was buzzing when the accident occurred.NTSB LAX90LA023Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · S. Juan Batista, CAThe pilot's intentional buzzing and failure to see and avoid a guy wire.NTSB MKC90FA017Accident · 2 fatalField investigationFinal reportPiper PA-28-161 · Elkader, IAThe pilot's failure to maintain clearance from the runway marker at the departure end of the runway.NTSB LAX88FA306Accident · 1 fatalField investigationFinal reportPiper PA-28-161 · Temecula, CAFailure of the pilot to properly initiate a go-around during an aborted landing. The loss of directional control during the landing, failure to return to the runway for the aborted takeoff, and not establishing the proper rate of climb due to high density…NTSB LAX87LA249Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Auberry, CADuring an approach into a private airstrip, the student pilot touched-down, then decided that there was not enough stopping distance and elected to go-around. On the initial climb-out the aircraft struck an object that made the aircraft yaw right then left.…NTSB MIA87FA080Accident · 3 fatalField investigationFinal reportPiper PA-28-161 · Venice, FLAircraft was seen maneuvering at between 200 and 300 feet in attempts to locate a lost radio controlled model airplane. As the aircraft completed 2 and one half turns it leveled out and began a climb to the north at which time it collided with a 504 foot…NTSB MIA86LA251Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Sanford, FLWhile on approach to runway the pilots vision was restricted by the glare from the rising sun. The pilot failed to see the operating approach light system which is located in the closed first 2000 feet of runway, and collided with the approach light system.…NTSB ATL86FA217Accident · Minor injuriesField investigationFinal reportPiper PA-28-161 · Douglasville, GAThe plt loaded three adults plus herself into the warrior ii and attempted to take off from a grass strip which had a dip and a hill of about 6 feet near the departure end. The acft traveled about 150 ft past the end of the runway before impacting on the side…NTSB MIA86LA050Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Leesburg, FLThe plt stated that while attempting to takeoff from a private airstrip his left main wheel hit a barbed wire fence causing the left wing to strike the ground & separate from the acft.NTSB DEN85FA186Accident · 1 fatalField investigationFinal reportPiper PA-28-161 · Aspen, COCFI and student departed Aspen, Colorado, on a dual x-country flt. The density altitude at the time of departure was calculated to be 9954 feet. The CFI directed student to fly up a canyon in an area of rising terrain. The CFI took control of acft and was…NTSB FTW84FA050Accident · 3 fatalField investigationFinal reportPiper PA-28-161 · Devers, TXThe acft collided with trees while maneuvering at a very low altitude after dark in a popular deer hunting area. The acft was observed rolling into steep bank with the eng 'revved up' then suddenly yawed toward the ground. The acft lights were on.NTSB FTW84FA021Accident · 1 fatalField investigationFinal reportPiper PA-28-161 · Aubrey, TXThe purpose of the flt was to give a bfr to the private rated plt who had not flown for about 1 year. There were no witnesses to the accident. The plt stated that he could recall doing basic airwork during the flt, but could not recall any details of the flt…NTSB ATL83FIJ01Accident · 2 fatalFinal reportPiper PA-28-161 · Man, WVA witness reported that the pilot landed about 2100 ft down the 2750 ft, turf runway, rolled several hundred feet, then attempted to go around. When the aircraft was about 4 or 5 ft in the air, it hit some trees while heading into a river basin near the end…NTSB FTW83LA025Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Mcallen, TXWhile on approach the pilot encountered wind shear and downdrafts and subsequently struck the number 2 approach light stanchion. The gear assembly sheared off and the aircraft touched down on the runway and veered to the right.NTSB FTW82FRD13Accident · 2 fatalFinal reportPiper PA-28-161 · Lake Charles, LAThe plt told the surviving pax he was going to make a short fld takeoff with full (40 deg) flaps. The pax, who is also a plt, disagreed with the plt. The plt said it would be okay & proceeded to take off. During the takeoff roll the pax suggested he change…