NTSB investigations: Piper PA-32-260

693 cases on aircraft the registry lists as Piper PA-32-260. 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 ('7103206'))
  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 ANC02LA095Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Red Devil, AKA partial loss of engine power for an undetermined reason during the initial climb after takeoff that resulted in a collision with trees. A contributing factor in the accident was rising terrain which was unsuitable for a forced landing.Aug 14, 2002 · N3853W · Substantial damageNTSB DEN02LA090Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-260 · Victor, COthe pilot's failure to refuel, resulting in fuel exhaustion and a subsequent loss of engine power. Contributing factors were the pilot's use of inappropriate medication, and the unsuitable terrain on which to make a forced landing.Aug 11, 2002 · N222SH · Substantial damageNTSB FTW02LA181Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Pecos, TXThe pilot misjudged the landing flare resulting in a hard landing. A contributing factor was the dark night conditions.Jun 17, 2002 · N675MP · Substantial damageNTSB IAD02LA044Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Louisville, KYThe pilot's inadvertent selection of an empty fuel tank, which resulted in fuel starvation of the engine.Apr 23, 2002 · N166PA · Substantial damageNTSB MIA02FA045Accident · 4 fatalField investigationFinal reportPiper PA-32-260 · Jacksonville, FLThe pilot becoming spatially disoriented and losing control of the airplane during a missed approach resulting in the airplane descending uncontrolled and colliding with trees and the ground.Dec 13, 2001 · N7701J · DestroyedNTSB LAX02LA022Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Avalon, CAthe total loss of engine power during departure climb for undetermined reasons.Nov 4, 2001 · N3516W · Substantial damageNTSB ANC02LA004Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-260 · Port Heiden, AKThe pilot's delay in aborting the landing. Factors in the accident were snow and ice on the runway surface, and the pilot's excessive taxi speed.Oct 30, 2001 · N5573J · DestroyedNTSB MIA01LA212Accident · 2 fatalLimited investigationFinal reportPiper PA-32-260 · Key West, FLThe inadvertent disabling of the throttle in the idle position during a cockpit disturbance created when an armed hijacker forcibly attempted to cause the aircraft to fly to Cuba, resulting in a loss of controllability of power for sustainable flight and an…Aug 9, 2001 · N5569J · Substantial damageNTSB SEA01FA145Accident · 6 fatalField investigationFinal reportPiper PA-32-260 · Puyallup, WAThe pilot's failure to maintain adequate airspeed during departure resulting in a stall. Trees were a factor in the accident.Jul 29, 2001 · N3479W · DestroyedNTSB CHI01FA233Accident · 2 fatalField investigationFinal reportPiper PA-32-260 · Chenoa, ILThe inadvertent stall the pilot encountered during his turn with an in-flight loss of engine power due to fuel starvation on initial climbout and the improper in-flight decision he made to continue the turn. Factors were the fuel starvation and the incorrect…Jul 21, 2001 · N27AP · Substantial damageNTSB ATL01LA012Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Florence, SCLoss of engine power due to carburetor icing, which resulted in a emergency landing into rough uneven terrain.Nov 29, 2000 · N6YB · Substantial damageNTSB ANC01LA016Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Lime Village, AKThe pilot's failure to properly utilize carburetor heat. Factors in the accident were the presence of carburetor icing conditions, and unsuitable terrain for a forced landing.Nov 9, 2000 · N4803S · Substantial damageNTSB CHI00LA310Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Petersburg, MIthe pilots failure to abort the takeoff and obtain/maintain clearance from the corn crop. Factors were the tall, wet, grass runway, and the corn crop.Sep 29, 2000 · N33117 · DestroyedNTSB LAX00LA247Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Chester, CAThe loss of engine power for undetermined reasons.Jun 30, 2000 · N933AC · DestroyedNTSB FTW00LA263Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Clinton, OKThe pilot's improper setting of the cockpit fuel selector, which resulted in a total loss of engine power and forced landing.Jun 3, 2000 · N3869W · Substantial damageNTSB NYC99FA220Accident · 3 fatalField investigationFinal reportPiper PA-32-260 · Westerly, RIThe pilot's loss of control of the airplane during a turn.Sep 5, 1999 · N4830S · Substantial damageNTSB DEN99LA146Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Aspen, COThe pilot's inadequate in flight planning. Factors were the high density altitude, the lack of suitable terrain for a forced landing, and the sign post that the right wing impacted.Aug 16, 1999 · N991RC · DestroyedNTSB NYC99FA187Accident · 4 fatalField investigationFinal reportPiper PA-32-260 · North Lima, OHThe pilot's loss of control of the airplane during a turn. Factors include the pilot's failure maintain sufficient airspeed, and his failure to maintain the airplane in proper trim.Aug 1, 1999 · N5526J · DestroyedNTSB MIA99LA099Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Atlantic Ocean (Atlantic Ocean)a loss of engine power for an undetermined reason, resulting in a forced landing in water, and subsequent sinking of the airplane.Mar 3, 1999 · N4802S · DestroyedNTSB MIA99LA073Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-260 · Orlando, FLA loss of engine power due to an engine assembly overload for undetermined reasons. A related factor was the pilot exceeded the airplane's maximum allowable weight.Feb 3, 1999 · N5528J · DestroyedNTSB CHI99LA065Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · St. Charles, ILA loss of engine power due to fuel exhaustion. Also causal was the pilot's inadequate preflight/planning preparation which led to inadvertent flight into instrument meteorological conditions and him becoming lost/disoriented. Contributing to the accident were…Jan 17, 1999 · N40712 · Substantial damageNTSB CHI99LA066Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Creal Springs, ILwas the pilot having the fuel tank selector in the improper position and not following the airplane manufacturer's emergency procedures to restore a loss of power. A factor in this accident was fuel starvation.Jan 16, 1999 · N3689W · DestroyedNTSB FTW99LA056Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Fabens, TXThe pilot's failure to correctly calculate fuel consumption, which resulted in the loss of engine power due to fuel exhaustion. A factor was the lack of suitable terrain for the forced landing.Dec 30, 1998 · N7724J · Substantial damageNTSB IAD99LA014Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Baltimore, MDAn inadvertent collision with a deer on the runway. A contributing factor was night conditions.Nov 9, 1998 · N4808S · Substantial damageNTSB CHI98LA330Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Sault Ste Marie, MIthe pilot's failure to maintain clearance between the airplane and the runway marker. A factor contributing to this accident was the runway marker.Aug 28, 1998 · N4887S · Substantial damageNTSB NYC98WA123Accident · No injuriesForeign investigationPiper PA-32-260 · Nice, FranceMay 31, 1998 · N3995W · Substantial damageNTSB CHI98LA102Accident · 1 fatalLimited investigationFinal reportPiper PA-32-260 · Mc Cordsville, INThe pilot's failure to maintain airspeed and control of the airplane. Factors were his self-induced pressure.Mar 12, 1998 · N55059 · Substantial damageNTSB NYC98FA041Accident · 3 fatalField investigationFinal reportPiper PA-32-260 · Pittsville, MDthe pilot's impairment of judgment and performance due to alcohol, his resultant improper planning/decision and flight in instrument meteorological conditions (IMC), and his failure to maintain sufficient altitude while flying over wooded terrain. Factors…Dec 12, 1997 · N3448W · DestroyedNTSB CHI98LA037Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Lakeville, MNfuel starvation due a deteriorated grommet in an Adel clamp, and a loose mixture control cable.Oct 31, 1997 · N3359W · Substantial damageNTSB MIA98FA007Accident · 3 fatalField investigationFinal reportBeech 35-C33A · Robbins, NCfailure of the pilots in both aircraft to see-and-avoid each other's airplane (inadequate visual lookout), and failure of the Beech pilot to operate his airplane at a correct Visual Flight Rules (VFR) cruising altitude for his route of flight.Oct 7, 1997 · N2050W · 2 aircraft · DestroyedNTSB IAD98FA001Accident · Serious injuriesField investigationFinal reportPiper PA-32-260 · College Park, MDThe pilot failed to maintain control of the airplane during landing rollout and his delayed decision to abort the landing.Oct 4, 1997 · N7730J · DestroyedNTSB MIA97LA109Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Atlantic Ocean (Atlantic Ocean)loss of engine power for undetermined reason(s). A factor relating to the accident was: the pilot's poor in-flight planning/decision by flying at too low of an altitude to glide to shore for a forced landing.Mar 30, 1997 · N576PR · Substantial damageNTSB NYC97LA063Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Lincoln Park, NJThe pilot's failure to maintain adequate obstacle clearance due to his diverted attention in attempting to re-illuminate the runway lights, which resulted in an inflight collision with a tree.Mar 25, 1997 · N3604W · DestroyedNTSB CHI97LA051Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · St. Ignace, MIthe pilot's failure to maintain proper runway alignment during the takeoff roll. A factor associated with the accident was the snowbank which the airplane contacted.Jan 13, 1997 · N33797 · Substantial damageNTSB IAD97LA027Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Claverack, NYloss of engine power for undetermined reasons.Dec 4, 1996 · N3324W · Substantial damageNTSB NYC97FA025Accident · 1 fatalField investigationFinal reportPiper PA-32-260 · Felton, PAThe pilot's inadequate preflight planning and preparation, and his failure to refuel which resulted in fuel exhaustion and the subsequent collision with trees during the forced landing.Dec 3, 1996 · N5538J · DestroyedNTSB CHI97LA012Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Mancelona, MIthe worn fuel system pump (actuator arm). A factor was the unsuitable terrain encountered by the pilot.Oct 20, 1996 · N56155 · Substantial damageNTSB NYC96LA171Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Coatsville, PAloss of engine power for undetermined reason(s). Factors relating to the accident were: darkness, and the lack of suitable landing areas.Aug 23, 1996 · N3868W · DestroyedNTSB IAD96LA130Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Gaithersburg, MDthe unexpected appearance of a deer on the runway.Aug 9, 1996 · N1439T · Substantial damageNTSB MIA96LA202Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Live Oak, FLfailure of the pilot to use carburetor heat during the approach to land, which resulted in loss of engine power due to carburetor ice. The weather (carburetor icing condition) was a related factor.Aug 4, 1996 · N3399W · Substantial damageNTSB CHI96LA174Accident · No injuriesLimited investigationFinal reportPiper PA-32 · Osage Beach, MOa partial loss of power for undetermined reasons.May 25, 1996 · N40933 · Substantial damageNTSB CHI96LA137Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Aitkin, MNthe pilot's improper planning/decision, which resulted in his failure (or inability) to adequately compensation for wind conditions. Factors relating to the accident were: the gusty crosswind condition and the snowbank.Apr 22, 1996 · N4883S · Substantial damageNTSB FTW95LA275Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Farmington, NMThe pilot's failure to verify the fuel tank selector position and the resultant fuel starvation induced power loss.Jul 1, 1995 · N4823T · Substantial damageNTSB MIA95LA158Accident · 1 fatalLimited investigationFinal reportPiper PA-32-260 · Brooksville, FLA loss of engine power after takeoff for undetermined reasons. Contributing to the accident was the lack of suitable terrain for a forced landing.Jun 26, 1995 · N3431W · DestroyedNTSB MIA95FA145Accident · 6 fatalField investigationFinal reportPiper PA-32-260 · Gainesville, FLThe pilot's loss of aircraft control due to spatial disorientation after continuing the VFR flight into instrument meteorological conditions. Factors relating to the accident were: the existing weather conditions and dark night that contributed to the pilot's…Jun 7, 1995 · N41481 · DestroyedNTSB MIA95LA144Accident · 1 fatalLimited investigationFinal reportPiper PA-32-260 · Vieques, PRUndetermined.Jun 2, 1995 · N41528 · Substantial damageNTSB NYC95LA130Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Ashland, VAa loss of engine power due to a subsurface fatigue crack in the crankshaft which led to failure of the crankshaft.May 31, 1995 · N16354 · DestroyedNTSB MIA95LA127Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · N. Miami Beach, FLInadequate annual inspection by maintenance personnel for failure to identify a hardened oil hose from the oil pump to the oil cooler inlet inside a protective fire sleeve. Additionally, unsuitable terrain encountered during the forced landing contributed to…May 5, 1995 · N3482W · Substantial damageNTSB CHI95LA120Accident · 1 fatalLimited investigationFinal reportPiper PA-32-260 · St. Clair, MOthe pilot's impairment of judgment and performance due to drugs which led to his operating the airplane with a known mechanical deficiency.Apr 8, 1995 · N3631W · DestroyedNTSB NYC95FA068Accident · 3 fatalField investigationFinal reportPiper PA-32-260 · Suffolk, VAThe pilot's inadequate preflight and improper in-flight planning/decision, which resulted in fuel exhaustion. Darkness was a factor related to the improper planning/decision-making for the emergency landing.Mar 13, 1995 · N57326 · Destroyed