NTSB investigations: Piper PA-32R-300

301 cases on aircraft the registry lists as Piper PA-32R-300. 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 ('7103213'))
  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 ANC99FA130Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Bettles, AKThe pilot's continued flight into known adverse weather conditions. Factors in the accident were low ceilings and snow.Sep 3, 1999 · N9166K · DestroyedNTSB LAX99LA254Accident · No injuriesLimited investigationFinal reportPiper PA32R-300 · Mammoth Lakes, CAThe pilot's failure to attain and maintain an adequate airspeed for the prevailing density altitude. The pilot's failure to abort the takeoff is also causal.Jul 17, 1999 · N1692H · Substantial damageNTSB LAX99LA201Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Valley Springs, CAThe fatigue failure and separation of the No. 6 connecting rod end cap, which led to a catastrophic failure of the engine. The fatigue crack initiation was due to galling on the rod end cap, which was most likely caused by an undetermined factory…May 28, 1999 · N38908 · Substantial damageNTSB ANC99LA043Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R · Fairbanks, AKThe loss of engine power due to the failure of maintenance personnel to properly torque a connecting rod bolt during an engine overhaul, and the subsequent disconnection of the connecting rod bolt and connecting rod.Apr 5, 1999 · N1942H · Substantial damageNTSB NYC99LA073Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Richmond, VAThe pilot's inadequate preflight planning/preparation which resulted in flight into icing weather conditions. A factor related to the accident was restricted visibility through the icy windshield during landing.Mar 9, 1999 · N5454F · Substantial damageNTSB FTW99FA060Accident · 1 fatalField investigationFinal reportPiper PA-32-300R · Smackover, ARThe pilot's spatial disorientation resulting in a loss of control of the airplane and the ensuing stall/spin. Factors were the low ceilings and the night condition.Jan 2, 1999 · N7676C · DestroyedNTSB ATL99FA011Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Roswell, GAA loss of engine power due to the failure of the number five connecting rod assembly as a result of fatigue cracks that were initiated in areas of galling. A factor was the lack of suitable terrain for a forced landing.Oct 28, 1998 · N8554C · DestroyedNTSB MIA98WA131Accident · No injuriesForeign investigationPiper PA-32R-300 · Dolo Odo, EthiopiaApr 12, 1998 · N2SX · Substantial damageNTSB LAX98LA027Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Santa Rosa, CALoss of engine power for undetermined reasons.Oct 31, 1997 · N1655H · Substantial damageNTSB CHI97LA294Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Fargo, NDthe pilot's misjudgment of altitude and distance to the runway, while on final approach to land, and failure to attain the proper touchdown point on the runway during the landing. The exposed runway lip was a related factor.Sep 17, 1997 · N2680Q · Substantial damageNTSB IAD97LA092Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Defiance, OHThe failure of a wheel rim due to overstress separation with no clear evidence initiating event.Jun 21, 1997 · N5716F · Substantial damageNTSB LAX97LA181Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Burbank, CAimproperly secured upper cowl fasteners by unknown person(s).May 12, 1997 · N3609Q · Substantial damageNTSB MIA97LA145Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Augusta, GAflight by the pilot into known adverse weather conditions, which resulted in a loss of aircraft control during the landing flare, and collision with the terrain. The adverse weather with nearby thunderstorm activity, crosswind, and gusts was a related factor.Apr 23, 1997 · N1321H · Substantial damageNTSB NYC97LA073Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Lumberton, NJThe pilot's delay in initiating remedial action to arrest an excessive descent rate during a go-around. A crosswind condition was a contributing factor.Apr 14, 1997 · N29M · Substantial damageNTSB FTW97LA107Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Salida, COThe airplane's performance being exceeded due to the pilot's inadequate preflight planning. Factors were the uphill runway, high density altitude, and the pilot's lack of experience performing takeoffs from a high altitude airport.Feb 18, 1997 · N4477F · Substantial damageNTSB CHI97LA042Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Garnett, KSthe pilot's improper in-flight planning/decision, including a delay in proceeding to an alternate airport after encountering fog during a night approach, which resulted in loss of engine power due to fuel exhaustion.Dec 13, 1996 · N31SW · Substantial damageNTSB FTW96LA369Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Salida, COtotal failure of the induction air control linkage (bolt), which allowed the alternate air door to close and starve the engine of air.Sep 2, 1996 · N7640F · Substantial damageNTSB CHI96FA314Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Medford, MNfailure of the pilot to maintain control of the airplane, due to spatial disorientation. Factors relating to the accident were: failure of the (primary) vacuum system and a restriction in the (standby) vacuum system.Aug 26, 1996 · N7133C · DestroyedNTSB LAX96FA226Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Goleta, CAfailure of the flying pilot to maintain control of the airplane, due to spatial disorientation, which resulted in an uncontrolled descent and collision with the water. Factors relating to the accident were: the lack of recent instrument experience by the…Jun 7, 1996 · N4303X · DestroyedNTSB CHI96LA118Accident · No injuriesLimited investigationFinal reportCessna 310R · Marshfield, WIthe failure of the pilot of the PA-32R, N1030Q, to obtain identification of the Cessna 310R, N1835E, visually, and his inadequate visual outlook. A factor was the failure of both pilots to hear communications from each other.Mar 20, 1996 · N1835E · 2 aircraft · Substantial damageNTSB MIA96LA066Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-300 · Smithville, TNThe pilot's improper in-flight planning/decision, which resulted in a heavy load of airframe ice, an inability to maintain altitude, and a subsequent emergency landing. Factors relating to the accident were: the adverse weather (icing) condition, which was…Jan 19, 1996 · N4457X · Substantial damageNTSB CHI96FA113Accident · 1 fatalField investigationFinal reportPiper PA-32 · Milwaukee, WIInadequate maintenance and inspection in that the Airworthiness Directive which applied to the fuel pump had not been complied with. A factor was the pilot was unable to reach land.Jan 17, 1996 · N3326Q · DestroyedNTSB FTW95FA363Accident · Serious injuriesField investigationFinal reportPiper PA-32R-300 · Wichita Falls, TXthe pilot's failure to maintain airspeed while diverting attention to an open cargo door. A factor was the pilot's inadequate preflight inspection.Aug 26, 1995 · N9296K · DestroyedNTSB FTW95LA355Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Fayetteville, ARThe pilot's inability to extend the landing gear due to the failure of an emergency gear extension valve.Aug 19, 1995 · N47423 · Substantial damageNTSB MIA95FA183Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Hilton Head Isl, SCloss of engine power for undetermined reasons, and the unsuitable terrain encountered during the emergency landing. A factor in the accident was the pilot's extension of the downwind leg which prevented landing on the intended runway following loss of engine…Jul 13, 1995 · N38188 · DestroyedNTSB ANC95FA101Accident · 6 fatalField investigationFinal reportPiper PA-32R-300 · Haines, AKThe pilot's failure to maintain an adequate altitude above and clearance from the surrounding terrain. A factor related to the accident was the pilot's improper decision to conduct the maneuver in such close proximity to the rising terrain.Jul 7, 1995 · N6281J · DestroyedNTSB FTW95FA112Accident · 5 fatalField investigationFinal reportPiper PA-32R-300 · Conroe, TXThe pilot's failure to follow published IFR procedures. Factors were the weather conditions, the dark night, and the pilot's failure to activate the approach lighting system.Feb 10, 1995 · N5373F · DestroyedNTSB ATL95LA045Accident · Serious injuriesLimited investigationFinal reportPiper PA-32R-300 · Burnsville, NCThe pilot's failure to complete the before-landing checklist to ensure that the landing gear was extended.Jan 25, 1995 · N1999H · Substantial damageNTSB SEA95FA031Accident · 4 fatalField investigationFinal reportPiper PA-32R-300 · Grantsville, UTThe VFR pilot's attempt to continue the flight into instrument meteorological conditions, and his failure to maintain altitude/clearance with mountainous terrain.Dec 19, 1994 · N175MC · DestroyedNTSB ATL94FA171Accident · 3 fatalField investigationFinal reportPiper PA-32R-300 · Glenville, NCThe fatigue failure of #4 intake valve. A factor was hilly terrain.Sep 13, 1994 · N73AW · DestroyedNTSB BFO94FA140Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Roanoke, VAThe disconnection of the throttle cable from the throttle arm on the fuel injector servo.Aug 19, 1994 · N4316X · DestroyedNTSB NYC94LA105Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Put-In-Bay, OHThe pilot's inadequate control and failure to maintain directional control which resulted in collision with a sign.Jul 2, 1994 · N5716F · Substantial damageNTSB BFO94LA113Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-300 · Seven Springs, PAThe pilot's failure to attain adequate airspeed and his premature liftoff which resulted in a stall mush and collision with trees.Jun 23, 1994 · N40051 · Substantial damageNTSB BFO94LA070Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Bedford, PAThe pilot's failure to maintain the proper descent rate which resulted in an undershoot of the runway.Apr 18, 1994 · N4445X · Substantial damageNTSB BFO94FA066Accident · 3 fatalField investigationFinal reportPiper PA-32R-300 · Salem, OHVFR flight by the pilot into instrument meteorological conditions (IMC), his loss of aircraft control due to spatial disorientation, and exceeding the design stress limits of the aircraft. Factors related to the accident were: darkness, the adverse weather…Apr 16, 1994 · N8685C · DestroyedNTSB BFO94LA046Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Berlin, NJThe pilot not maintaining clearance from obstacles (trees) during final approach which resulted in a collision with a tree and a subsequent uncontrolled descent until colliding with the ground.Feb 22, 1994 · N23AL · Substantial damageNTSB MIA94FA069Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Vicksburg, MSFailure of the pilot-in-command to maintain the proper glidepath while on a straight in approach resulting in the inflight collision with trees short of the runway. Contributing to the accident was the dark night condition.Feb 9, 1994 · N1645H · Substantial damageNTSB BFO94LA038Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Norfolk, VAFatigue failure of the engine mounting bolt which resulted in loss of engine power and subsequent on ground collision with the terrain.Feb 7, 1994 · N38780 · Substantial damageNTSB SEA94FA040Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Spokane, WAThe pilot's failure to maintain proper alignment with the instrument landing system approach course. The pilot's failure to perform a missed approach was a factor.Dec 15, 1993 · N999VP · DestroyedNTSB CHI94FA048Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Antigo, WIthe failure of the pilot in command to maintain proper altitude.Dec 10, 1993 · N550BC · Substantial damageNTSB LAX94WA053Accident · Serious injuriesForeign investigationPiper PA-32R-300 · Mulege, MexicoNov 13, 1993 · N6879J · Substantial damageNTSB CHI94FA018Accident · 5 fatalField investigationFinal reportPiper PA-32R-300 · Atkinson, NEthe instrument rated commercial pilot's failure to maintain adequate clearance from terrain/obstructions during the initial climb after takeoff. Related factors are the weather conditions (fog) and the pilot's failure to maintain the proper rate of climb.Oct 16, 1993 · N4147Q · DestroyedNTSB ATL93FA151Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Laurinburg, NCThe pilot's VFR flight into instrument meteorological conditions (IMC), failure to maintain control of the aircraft after becoming spatially disoriented, and inadvertently exceeding the design stress limits of the aircraft. Factors related to the accident…Sep 5, 1993 · N5339F · DestroyedNTSB ANC93FA134Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Atigun Pass, AKThe pilot-in-command's intentional VFR flight into instrument meteorological conditions and his unfamiliarity with the geographical area. Factors were the rain and fog.Aug 4, 1993 · N477JC · DestroyedNTSB MIA93WA115Accident · No injuriesForeign investigationPiper PA-32R-300 · West End, BahamasMay 4, 1993 · N96RJ · DestroyedNTSB FTW93LA073Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · El Dorado, ARThe pilot's failure to maintain clearance. A factor was the dark night.Jan 23, 1993 · N7676C · Substantial damageNTSB SEA92LA173Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-300 · Farmington, UTThe pilot's poor inflight decision. Factors include downdrafts and a box canyon.Aug 4, 1992 · N7091C · DestroyedNTSB MIA92WA146Accident · No injuriesForeign investigationPiper PA32R-300 · Andros Island, BahamasJul 4, 1992 · N5606V · Substantial damageNTSB NYC92LA107Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Denton, MDThe failure of the pilot to detect the automobile gasoline in the tanks prior to departure, and intentional refueling with improper fuel by the pilot's brother which resulted in a lose of engine power due to detonation and loss of oil pressure.Jun 10, 1992 · N4552X · Substantial damageNTSB CHI92LA160Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-300 · Round Lake, ILThe pilot-in-command's failure to follow emergency procedures, and the fire in the electrical system for reasons undetermined.Jun 1, 1992 · N812PC · Destroyed