NTSB investigations: Piper PA-28-161, GA
15 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
| 1979 | 1 |
|---|---|
| 1985 | 1 |
| 1986 | 1 |
| 1992 | 1 |
| 1997 | 1 |
| 1998 | 1 |
| 1999 | 1 |
| 2000 | 2 |
| 2001 | 1 |
| 2002 | 1 |
| 2004 | 1 |
| 2006 | 1 |
| 2011 | 1 |
| 2024 | 1 |
Where
Latest 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\" = 'GA' 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" = 'GA' 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 ERA24LA392Accident · Minor injuriesClass 3 · LimitedFinal reportPiper PA28 · LaGrange, GAImproper manufacture of a cylinder exhaust valve guide by the engine manufacturer, which resulted in a stuck exhaust valve and a partial loss of engine power during initial climb.NTSB ERA11CA131Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Atlanta, GAThe pilot's wrong turn while taxiing resulting in a collision with a sign.NTSB ATL06CA105Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Griffin, GAThe pilot's failure to maintain direction control of the airplane during the landing roll.NTSB ATL04LA124Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · St. Marys, GAThe pilot failure to use carburetor heat when weather condition were favorable for the for the formation of carburetor ice. .NTSB ATL03LA022Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Eastman, GAThe pilots failure to maintain a visual lookout resulting in the subsequent on ground collision with a hangar.NTSB ATL02LA023Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Kennesaw, GAThe pilot's improper in-flight planning/decision resulting in a total loss of engine power due to fuel exhaustion,which resulted in a forced landing, and subsequent in-flight collision with transmission wires.NTSB MIA01LA009Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Jesup, GAA total failure of the wheel braking system due to the pilot's improper use of braking in downwind, downhill conditions, resulting in overheated brakes, and subsequent encounter with a downslope and terrain collision.NTSB ATL00FA026Accident · 1 fatalField investigationFinal reportPiper PA-28-161 · Chamblee, GAThe S76 helicopter pilot's failure to follow ATC landing sequence clearance, which resulted in the PA-28's encounter with the helicopters wake turbulence. A factor was the air traffic controllers clearance procedure.NTSB MIA99LA264Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Covington, GAthe pilot's decision to take off from unsuitable terrain, which resulted in a collision with trees.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 ATL98LA015Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Lawrenceville, GAfailure of the student pilot to maintain directional control of the airplane, during the landing roll.NTSB ATL92LA115Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Bainbridge, GAThe pilot's misjudged distance of runway remaining, resulting in a delayed decision to abort the takeoff, and subsequent collision with trees. Factors were the high obstructions (trees) at the departure end of the runway.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 ATL85FA165Accident · Serious injuriesField investigationFinal reportPiper PA-28-161 · Milledgeville, GAAcft left home airport at 0400. Flt plan left with FBO indicated 6 hours to destination, no en route stops, and 4+30 hours fuel on board. Fuel consumption calculated, 4+36 hours endurance available. Acft flew 4+47 hours. The pilot told approach control acft…NTSB MIA80FKG07Accident · Serious injuriesClosedPiper PA-28 · Jonesboro, GA