NTSB investigations: Piper PA-28-161

728 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, newest first

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'))
  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.

NTSB LAX04CA208Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Tucson, AZthe backhoe driver's failure to maintain visual lookout while maneuvering near a taxiway, which resulted in its collision with a taxiing airplane.May 13, 2004 · N84245 · Substantial damageNTSB LAX04FA190Accident · Serious injuriesField investigationFinal reportPiper PA 28-161 · Holoaloa, HIThe pilot's continued flight into adverse weather conditions that resulted in an in-flight collision with mountainous terrain. Factors in the accident were rising terrain, low clouds and rain, and the pilot's lack of familiarity with the geographic area.Apr 19, 2004 · N8198A · DestroyedNTSB LAX04FA137Accident · 2 fatalField investigationFinal reportPiper PA-28-161 · Jean, NV!!This case was modified January 31, 2006!! the pilot's failure to maintain adequate clearance with the rising terrain, while maneuvering at low altitude in a mountainous area.Feb 16, 2004 · N9199Z · DestroyedNTSB CHI04LA063Accident · No injuriesLimited investigationFinal reportPiper PA 28-161 · Lansing, ILThe improper flare by the pilot due to his diverted attention during landing. Factors were the pilot's failure to execute a go-around, the overload of the right main landing gear, and the snowbank.Feb 8, 2004 · N38988 · Substantial damageNTSB ATL04LA074Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Summerville, SCThe pilot's inadequate start procedure, which resulted in a run-away airplane.Feb 7, 2004 · N21266 · Substantial damageNTSB LAX04CA115Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Placerville, CAthe pilot's failure to attain a proper glide path during the final approach and delayed go-around, resulting in an undershoot of the runway. The inadequate supervision of the flight and flight instructor's delayed remedial action was also causal.Jan 30, 2004 · N28385 · Substantial damageNTSB FTW04LA015Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Henryetta, OKA loss of engine power due to fuel starvation. A contributing factor was the inadequate inflight planning procedures for a cross country flight.Oct 26, 2003 · N8090E · Substantial damageNTSB LAX04LA027Accident · No injuriesLimited investigationFinal reportPiper PA 28-161 · San Diego, CAthe pilot of the other airplane's inadvertent application of the rudder pedals rather than the brakes, which resulted in the collision with the Cessna 172R.Oct 25, 2003 · N39494 · 2 aircraft · Substantial damageNTSB LAX03LA280Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-161 · Sacramento, CAthe pilot's inadequate preflight inspection and the bystander's failure to maintain clearance with the rotating propeller.Sep 7, 2003 · N9141Y · No damageNTSB DEN03LA139Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Crowheart, WYThe pilot's inadequate preflight planning (attempting to exceed aircraft's published certificated performance), the pilot not obtaining sufficient altitude to clear the terrain (not possible), and the pilot's inadequate in flight planning/decision making.…Aug 6, 2003 · N2973T · Substantial damageNTSB LAX03LA238Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Lomita, CAThe partial loss of engine power due to carburetor icing and the pilot's failure to use carburetor heat. Also causal was the pilot's failure to attain and maintain an adequate airspeed during the aborted landing, which resulted in a stall/mush.Jul 20, 2003 · N3091M · DestroyedNTSB 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.Jul 10, 2003 · N125ER · Substantial damageNTSB CHI03LA188Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Brazil, INThe delayed aborted takeoff by the pilot-in-command. A contributing factor was the fence, which the airplane contacted during the aborted takeoff.Jun 29, 2003 · N1660H · Substantial damageNTSB LAX03LA130Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-181 · Baker, CAthe separation of a propeller blade tip due to fatigue cracking that resulted from improper maintenance repair procedures.Apr 6, 2003 · N8465R · Substantial damageNTSB MIA03LA073Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Lake Placid, FLthe pilot-in-command's failure to maintain airspeed during climb, which resulted in the airplane stalling, and impacting with a house.Mar 5, 2003 · N81549 · Substantial damageNTSB LAX03LA047Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Scottsdale, AZThe pilot's inadequate preflight inspection and failure to refuel the airplane resulting in a loss of engine power due to fuel starvation.Dec 9, 2002 · N2588Y · Substantial damageNTSB 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.Dec 3, 2002 · N289HG · Substantial damageNTSB NYC03LA012Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-161 · Lakewood, NJThe pilot's improper use of carburetor heat which resulted in a failure to remove carburetor ice, and loss of engine power. A factor was the carburetor icing conditions.Oct 24, 2002 · N40059 · Substantial damageNTSB LAX03LA015Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Queen Creek, AZa loss of engine power for undetermined reasons.Oct 21, 2002 · N4332W · Substantial damageNTSB SEA02LA186Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Spokane, WAThe flight instructor's delay of the remedial action necessary to correct for the student pilot's error during the landing flare. Factors include the student pilot's misjudgment of the aircraft's height above the runway when he initiated the flare.Sep 28, 2002 · N132ND · Substantial damageNTSB FTW02CA249Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Graham, TXthe pilot's failure to attain the proper touchdown point which resulted in a runway overrun.Sep 4, 2002 · N9855S · Substantial damageNTSB FTW02LA205Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Purcell, OKThe in-flight cabin fire as result of non-compliance with an AD and a Service Bulletin. A contributing factor to the accident was night conditions.Jul 14, 2002 · N96PF · DestroyedNTSB IAD02LA066Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Providence, RIThe student pilot's failure to maintain directional control during the landing.Jul 4, 2002 · N8081G · Substantial damageNTSB CHI02LA114Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Lafayette, INThe pilot's improper fuel management resulting in the total loss of engine power due to fuel starvation and the pilot's failure to use the checklist.Apr 23, 2002 · N563PU · Substantial damageNTSB NYC02LA066Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Atlantic City, NJThe pilot's failure to obtain a proper touchdown point.Feb 23, 2002 · N9182X · Substantial damageNTSB CHI02LA086Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Grand Forks, NDThe student pilot not maintaining clearance from a parked van while taxiing to the parking area. The van was a factor.Feb 21, 2002 · N274ND · Substantial damageNTSB 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.Dec 29, 2001 · N4390S · Substantial damageNTSB 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.Dec 27, 2001 · N3035L · Substantial damageNTSB 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.Dec 3, 2001 · N248ND · Substantial damageNTSB CHI02LA031Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · New Ulm, MNThe student and flight instructor not using all of the available runway, the inadequate supervision by the flight instructor and the unsuccessful remedial action by the flight instructor. The student not attaining the proper touchdown point and the plowed…Nov 6, 2001 · N523PU · Substantial damageNTSB CHI01LA305Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Grand Forks, NDThe student pilot's improper flare, and the flight instructor's delayed remedial action, which resulted in a loss of directional control.Sep 5, 2001 · N240ND · Substantial damageNTSB FTW01LA197Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Ardmore, OKthe student pilot's failure to maintain directional control during takeoff roll.Aug 24, 2001 · N81833 · Substantial damageNTSB DEN01FA111Accident · 4 fatalField investigationFinal reportPiper PA-28-161 · Meeker, COthe pilot's failure to maintain terrain clearance as a result of his drug induced impairment. A factor was his exceeding the airplane's gross weight limits.May 29, 2001 · N5999V · DestroyedNTSB NYC01FA128Accident · 3 fatalField investigationFinal reportPiper PA-28-161 · Danvers, MAThe pilot's failure to maintain aircraft control. Factors in the accident were the dark night, low ceiling, reduced visibility, and the pilot's decision to attempt a visual flight rules flight in marginal weather conditions.May 22, 2001 · N8365M · DestroyedNTSB NYC01LA099Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Winchester, VAThe pilot's inadequate fuel management, which resulted in fuel starvation.Apr 21, 2001 · N286FT · Substantial damageNTSB MIA01LA125Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Chapel Hill, NCThe loss of engine power for undetermined reasons during takeoff, resulting in an inflight collision with trees during the subsequent emergency landing. A factor in the accident was the lack of suitable terrain to conduct an emergency landing.Apr 19, 2001 · N118AW · Substantial damageNTSB CHI01LA116Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Culver, INthe CFI delayed remedial action during the takeoff. Additional factors were the wrong runway was selected, the tailwind, and the trees.Apr 13, 2001 · N3573S · Substantial damageNTSB MIA01LA034Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Melbourne, FLThe student pilot's failure to maintain a visual look out while transitioning from the active runway to a taxiway resulting in an on-ground collision with a taxiway sign.Nov 30, 2000 · N617FT · Substantial damageNTSB NYC01LA042Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Fremont, OHThe pilot's failure to obtain a proper touchdown point while landing. Factors were the pilot's improper weather evaluation, rain, a low ceiling, and a tailwind.Nov 25, 2000 · N1305H · Substantial damageNTSB 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.Oct 18, 2000 · N47881 · Substantial damageNTSB ATL00FA091Accident · 2 fatalField investigationFinal reportPiper PA-28-161 · Ft. Pierce, FLFailure of local controller to provide adequate spacing between two airplanes that resulted in a midair collision. Contributing Factors: the local controller declined receiving a formal brief before relieving the controller on duty. The controller who was…Sep 11, 2000 · N9208N · 2 aircraft · DestroyedNTSB LAX00LA330Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Palo Alto, CAThe failure of maintenance personnel to detect and correct loose attachment fasteners and fretting at the landing gear attachment during maintenance inspections.Sep 4, 2000 · N6462C · Substantial damageNTSB CHI00FA263Accident · 3 fatalField investigationFinal reportPiper PA-28-161 · Watertown, WIAircraft control not being maintained during initial climb resulting in a stall/mush. Factors to the accident were the pilot's inadequate preflight planning/preparation, the pilot operating over the airplane's certified maximum gross weight, and the pilot…Aug 15, 2000 · N8126V · DestroyedNTSB 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.Jun 25, 2000 · N36355 · Substantial damageNTSB 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.Jun 24, 2000 · N8427K · Substantial damageNTSB CHI00LA154Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Minneapolis, MNthe failure of the engine and the unsuitable terrain for landing encountered by the pilot-in-command. Factors to the accident were the fracture of the crankshaft due to fatigue, excessive main bearing wear, and the swampy terrain condition.Jun 8, 2000 · N8189T · Substantial damageNTSB NYC00LA149Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Miamisburg, OHThe CFI's delayed remedial action.Jun 2, 2000 · N8234L · Substantial damageNTSB NYC00LA146Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Williamstown, NJimproper installation of a quick drain plug by the airplane owner/mechanic which resulted in a loss of engine oil and forced landing.May 30, 2000 · N4319U · Substantial damageNTSB MIA00LA171Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Chapel Hill, NCThe failure of the CFI to delay his landing until the approaching line of thunderstorms passed, causing the flight to encounter severely gusting wind conditions resulting in the loss of altitude control and collision with the terrain.May 25, 2000 · N47561 · DestroyedNTSB LAX00LA154Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Palo Alto, CAThe loss of engine power for undetermined reasons during takeoff climb.Apr 14, 2000 · N81019 · Substantial damage