NTSB investigations: Piper PA-28-161
68 cases on aircraft the registry lists as Piper PA-28-161, where the first occurrence was “Loss of control - on ground/water”. 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 | 5 |
|---|---|
| 1983 | 2 |
| 1984 | 2 |
| 1985 | 3 |
| 1986 | 3 |
| 1987 | 4 |
| 1989 | 3 |
| 1990 | 2 |
| 1991 | 4 |
| 1992 | 5 |
| 1993 | 3 |
| 1994 | 1 |
| 1995 | 2 |
| 1996 | 1 |
| 1998 | 2 |
| 1999 | 5 |
| 2000 | 4 |
| 2001 | 3 |
| 2002 | 2 |
| 2004 | 3 |
| 2005 | 5 |
| 2006 | 2 |
| 2007 | 2 |
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.\"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\" = 260))
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" = 260))
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 MIA08CA022Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Orlando, FLThe student pilot's failure to maintain directional control during landing.NTSB CHI08CA002Accident · No injuriesData collectionFinal reportPiper PA28-161 · Grand Forks, NDThe lack of experience and the excessive taxi speed by the pilot. A contributing factors was the airport 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 NYC06CA057Accident · No injuriesData collectionFinal reportPiper PA-28-161 · New Haven, CTThe student pilot's improper flare and inadequate recovery from a bounced landing, which resulted in a loss of aircraft control during landing and subsequent impact with a ditch.NTSB MIA06CA011Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Vero Beach, FLThe failure of the pilot to maintain directional control of the airplane during the landing roll resulting in the on-ground collision with runway signs.NTSB CHI05CA105Accident · No injuriesData collectionFinal reportPiper PA-28-161 · South Bend, INThe student pilot failed to compensate for the crosswind condition and failed to maintain directional control. Factors included the crosswind and the windsock.NTSB LAX05CA098Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Chandler, AZthe students pilot's failure to maintain directional control resulting in a collision with the taxiway sign.NTSB LAX05CA093Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Roosevelt, AZthe pilot's failure to maintain directional control.NTSB LAX05CA067Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Tucson, AZthe pilot's failure to maintain directional control during landing rollout.NTSB LAX05CA047Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Kapolei, HIthe pilot's failure to maintain directional control, which resulted in a collision with an obstacle.NTSB MIA05CA041Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Holly Springs, MSThe failure of the pilot to maintain directional control of the airplane while performing a go-around after a bounced landing, resulting in the on ground collision with trees.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 IAD02LA066Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Providence, RIThe student pilot's failure to maintain directional control during the landing.NTSB NYC02LA066Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Atlantic City, NJThe pilot's failure to obtain a proper touchdown point.NTSB LAX02LA060Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Long Beach, CAThe student pilot's inadequate compensation for wind, and his failure to maintain directional control of the aircraft during the landing roll.NTSB CHI02LA045Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Devils Lake, NDThe student pilot's failure to maintain directional control of the airplane during the takeoff phase of a touch and go landing. Factors associated with the accident were the student's lack of total experience and the runway light which the airplane contacted.NTSB FTW01LA197Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Ardmore, OKthe student pilot's failure to maintain directional control during takeoff roll.NTSB NYC00LA175Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Robbinsville, NJThe pilot's inadequate compensation for wind conditions, which resulted in a loss of aircraft control. A factor was a crosswind.NTSB FTW00LA185Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Mckinney, TXThe flight instructor's inadequate supervision of the landing resulting in the loss of directional control by the student pilot.NTSB NYC00LA089Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · West Milford, NJThe pilot's failure to maintain directional control during landing. A factor in this accident was the gusty crosswind conditions.NTSB LAX00LA094Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Honolulu, HIThe pilot's improper use of the brakes during the landing rollout. The pilot's self induced pressure and the quartering tailwind were factors in the accident.NTSB CHI99LA279Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Schaumburg, ILthe CFI's delay in taking remedial action to maintain directional control of the airplane. A factor associated with the accident was the student's improper use of the brakes.NTSB CHI99LA161Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Mineral Point, WIthe inadequate planning and decision by the pilot and the exceeded crosswind capability of the airplane. Contributing factors were the crosswind and the gusts.NTSB CHI99LA133Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Morris, ILthe directional control not maintained by the pilot. Contributing factors were the wind gusts, crosswind and runway light.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 CHI99LA119Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Ankeny, IAThe student pilot's failure to maintain directional control during landing.NTSB LAX99LA032Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Santa Barbara, CAThe pilot's inadequate compensation for the existing crosswind condition and failure to maintain proper runway alignment during landing flare.NTSB NYC98LA148Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Whitefield, NHThe instructor pilot's failure to maintain control of the aircraft during landing roll. Contributing factors were the instructor pilot's improper in-flight decision, tailwind and gusty conditions, and wet (standing water) runway conditions.NTSB CHI96LA079Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Zionsville, INthe pilot's failure to maintain directional control of the airplane on the ground. A factor relating to this accident is the snowbank.NTSB MIA95LA235Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Melbourne, FLThe failure of the pilot to maintain directional control during landing. Contributing to the accident was the crosswind.NTSB NYC95LA128Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Bluffton, OHan improperly planned approach and touchdown, which resulted in an loss of directional control at touchdown, with the airplane departing the runway, and striking a ravine.NTSB LAX94LA270Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · San Carlos, CAthe student pilot's attempt to exit the runway at an excessive taxi speed which resulted in his loss of control.NTSB ATL94LA008Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Lexington, NCThe pilot's failure to maintain directional control during a crosswind landing. A factor was the crosswind condition.NTSB SEA93LA215Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Tooele, UTThe pilot in command's failure to maintain directional control. A factor contributing to the accident was the fence.NTSB CHI93LA097Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Marshfield, WIThe student pilot's failure to maintain aircraft directional control during the takeoff ground run.NTSB CHI93LA059Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Lake In The Hls, ILThe student pilot's failure to maintain directional control.NTSB NYC93LA014Accident · No injuriesLimited investigationFinal reportPiper PA28-161 · St. Clairsville, OHThe pilot's improper in-flight planning and decision to land on a short grass runway with a tail wind. A factor in this accident was the pilots failure to obtain and evaluate a weather briefing prior to the flight.NTSB LAX92LA249Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · El Monte, CAThe student pilot's failure to maintain directional control and improper use of the brakes.NTSB ATL92LA087Accident · No injuriesLimited investigationFinal reportPiper PA28-161 · Rutherfordton, NCThe pilot's failure to maintain directional control during a landing roll which resulted in a collision with trees.NTSB CHI92LA115Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-161 · Lafayette, INThe student pilot's failure to maintain directional control and his delaying the aborted landing.NTSB MIA92LA043Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Vero Beach, FLFailure of the pilot to maintain directional control during the landing roll. This resulted in the collision with a sign. Contributing to the accident was his lack of total experience.NTSB CHI91LA252Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Mount Pleasant, MIDirectional control was not maintained by the pilot. Factors related to the accident were a wet, grass runway and buildings adjacent the runway.NTSB NYC91LA142Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Vergennes, VTThe pilot's excessive taxi speed, resulted in an on ground loss of control.NTSB MIA91LA105Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Melbourne, FLThe loss of control on the ground by the student pilot due to a lack of total experience and apprehension on his first solo flight.NTSB CHI90LA194Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Pulaski, WIThe pilot's failure to maintain positive control of the airplane while landing. Factors related to the accident were the pilot's lack of total flight experience, and inadequate compensation for crosswind conditions.NTSB DEN90LA062Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Nephi, UTFailure of the pilot to maintain direction control and correct the resultant ground swerve. The snow bank was a related factor.NTSB CHI90LA069Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · West Chicago, ILFailure of the solo student pilot to maintain directional control of the aircraft, which resulted in an inadvertent ground swerve. Factors related to the accident were: the crosswind, the student pilot's lack of total inexperience, and the runway lights.NTSB MIA89IA249Incident · No injuriesIncident investigationFinal reportPiper PA-28-161 · Fort Pierce, FLThe student's failure to maintain directional control of the airplane. Contributing to the accident was the student's lack of experience.NTSB ATL89LA105Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Tiffin, OHThe pilots improper recovery from a bounced landing which led to inadvertent porpoising and loss of directional control.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.