NTSB investigations: Piper PA-32R-301T

119 cases on aircraft the registry lists as Piper PA-32R-301T. 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 ('7103220', '7103221'))
  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 CHI05FA042Accident · 2 fatalField investigationFinal reportPiper PA-32R-301T · Glenwood, MNThe pilot's failure to execute a missed approach and his failure to maintain sufficient altitude and clearance from terrain and obstructions. Contributing factors were the pilot's failure to obtain a preflight weather briefing, his decision to delay descent…Dec 9, 2004 · N587C · Substantial damageNTSB LAX05FA032Accident · 3 fatalField investigationFinal reportPiper PA-32R-301T · Santa Barbara, CAThe pilot's failure to select and maintain an adequate terrain avoidance cruise altitude. Contributing factors were the dark nighttime conditions, the rising mountainous terrain, and the Federal Aviation Administration controller's failure to issue a…Nov 11, 2004 · N803ZG · DestroyedNTSB SEA04LA180Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Picabo, IDThe pilot's failure to set the propeller control for takeoff performance needed to outclimb obstacles. The pilot's failure to use the checklist, trees, and a fence are contributing factors.Sep 5, 2004 · N880SC · Substantial damageNTSB NYC04FA170Accident · 5 fatalField investigationFinal reportPiper PA-32R-301T · Wheeling, WVThe pilot's failure to maintain terrain clearance while executing an instrument approach. A factor was the night instrument meteorological conditions.Jul 19, 2004 · N7710M · DestroyedNTSB LAX04FA177Accident · 1 fatalField investigationFinal reportPiper PA-32R-301T · Ukiah, CAThe non-instrument rated pilot's flight intentional flight into instrument meteorological conditions during takeoff-initial climb, which resulted in spatial disorientation, a subsequent loss of aircraft control, and an uncontrolled descent into terrain. A…Apr 4, 2004 · N4130D · DestroyedNTSB FTW04CA061Accident · No injuriesData collectionFinal reportPiper PA-32R · Poynor, TXThe pilot's failure to maintain aircraft control while on final approach. A factor was the downdraft.Jan 15, 2004 · N4136S · Substantial damageNTSB LAX04FA001Accident · 2 fatalField investigationFinal reportPiper PA-32R-301T · Corona, CAfailure of the turbocharger exhaust clamp due to a pre-existing weld crack, which allowed the release of high temperature exhaust gasses in the engine compartment, causing an in-flight fire.Oct 1, 2003 · N481CA · DestroyedNTSB IAD03CA059Accident · No injuriesData collectionFinal reportPiper Saratoga II TC PA32- · Mansfield, OHThe pilot's inadequate compensation for wind conditions and his failure to maintain directional control during the landing. A factor was the gusty wind conditions.Jun 21, 2003 · N9298D · Substantial damageNTSB ATL03FA114Accident · 2 fatalField investigationFinal reportPiper PA-32R-301T · Scottsboro, ALThe pilot's improper fuel management which resulted in a loss of engine power due to fuel starvation and subsequent impact with trees.Jun 19, 2003 · N270LM · Substantial damageNTSB LAX03LA154Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-301T · Paulden, AZthe pilot's failure to attain and maintain the proper climb airspeed. The high density altitude condition was a factor.May 18, 2003 · N99TX · DestroyedNTSB IAD03FA024Accident · 2 fatalField investigationFinal reportPiper PA-32R-301T · Woodbury, CTAn engine fire for undetermined reasons, which resulted in the pilot's loss of control, and the airplane's subsequent impact with terrain.Dec 21, 2002 · N8168G · DestroyedNTSB MIA02FA173Accident · 2 fatalField investigationFinal reportPiper PA-32R-301T · Yeehaw Junction, FLthe pilot's continued flight into known severe weather, resulting in an in-flight separation of the right wing, vertical stabilizer and the stabilator. Factors in this accident were heavy thunderstorm, and failure of the FAA controllers to provide the pilot…Sep 24, 2002 · N106JG · DestroyedNTSB FTW02LA127Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Bogalusa, LAa deer that ran in front of the airplane during the takeoff phase. A contributing factor was the lack of an airport perimeter fence to prevent deer from entering the runway environment.Apr 23, 2002 · N8108V · Substantial damageNTSB LAX02LA048Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Groveland, CAThe pilot's collision with an unobserved animal that entered the active runway during the dark nighttime when the pilot's visibility was diminished.Dec 14, 2001 · N4328B · Substantial damageNTSB CHI01FA312Accident · Serious injuriesField investigationFinal reportPiper PA-32R-301T · Downers Grove, ILthe improper preflight planning/preparation and the short field take off/procedure not followed by the pilot. Contributing factors were the airplane's forward center of gravity, the variable gusting wind and improper weight and balance calculations by…Sep 7, 2001 · N81557 · DestroyedNTSB LAX01FA290Accident · No injuriesField investigationFinal reportPiper PA-32-301T · Fullerton, CAThe engine lost power for unknown reasons.Aug 26, 2001 · N9288X · Substantial damageNTSB NYC01LA187Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Sandy Hook, NJA total loss of engine power for undetermined reasons.Jul 25, 2001 · N4159V · Substantial damageNTSB FTW01LA068Accident · Serious injuriesLimited investigationFinal reportPiper PA32-R-301T · Haslet, TXthe improper installation of the oil filter bypass valve by an unknown person, which resulted in the loss of engine oil and subsequent loss of total power during a normal descent. A contributing factor to the accident was the lack of suitable terrain for the…Feb 17, 2001 · N8355L · Substantial damageNTSB CHI01LA010Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Tecumseh, MIThe pilot was unable to rotate the aircraft during takeoff for undetermined reasons. A factor associated with the accident was the soft terrain, which the airplane encountered during the aborted takeoff.Oct 15, 2000 · N289JG · Substantial damageNTSB NYC00LA158Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Wauseon, OHThe pilot's failure to maintain airspeed, which resulted in an inadvertent stall.Jun 12, 2000 · N8197W · Substantial damageNTSB LAX00LA112Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Coalinga, CAThe failure of the landing gear for undetermined reasons to go into the locked position after the pilot conducted a manual and emergency gear extension. A factor in the accident was the undetermined failure of the electrical system.Mar 2, 2000 · N8170S · Substantial damageNTSB NYC00LA065Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Harpswell, MEwas the improper decision of the pilot to depart at night, from an unlighted runway with no visual references to obstructions on the sides of the runway. Factors were the dark night conditions, and the lack of runway side lights.Jan 9, 2000 · N8463X · Substantial damageNTSB DEN99FA123Accident · 2 fatalField investigationFinal reportPiper PA-32R-301T · Magdalena, NMThe pilot's inadvertent flight into adverse weather and the subsequent in-flight breakup. Factors were the pilot's lack of experience in high altitude flying and the thunderstorm.Jul 19, 1999 · N22KC · DestroyedNTSB LAX99LA012Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Apple Valley, CAThe pilot's inadvertent use of the aircraft's brakes while using the rudder pedals to maintain directional alignment during the takeoff roll.Oct 12, 1998 · N4316L · Substantial damageNTSB MIA97FA219Accident · 2 fatalField investigationFinal reportPiper PA-32R-301T · Gainesville, GAloss of engine power for undetermined reason(s). Factors relating to the accident were: the lack of suitable terrain for a forced landing, and obstructions (trees and building) that were encountered during the emergency landing.Jul 25, 1997 · N8473P · DestroyedNTSB CHI97LA028Accident · Serious injuriesLimited investigationFinal reportPiper PA-32R-301T · Lansing, ILthe pilot's improper planning/decision, and his failure to go around, while there was still sufficient runway remaining. The unfavorable wind condition was a related factor.Nov 17, 1996 · N8308V · Substantial damageNTSB NYC96LA118Accident · No injuriesLimited investigationFinal reportPiper PA-32R · Williamstown, NJinadequate maintenance, which resulted in a failure of the magneto housing hold-down flange, a disconnect of the magneto from the engine, and loss of engine power. The obstruction (fence post) in the emergency landing area was a related factor.Jun 1, 1996 · N8186G · Substantial damageNTSB CHI96FA049Accident · 1 fatalField investigationFinal reportPiper PA-32R-301T · Parker, KSthe pilot's impairment of judgment and performance due to a drug (cocaine); his improper in-flight decision to continue flight over an overcast condition and then to descend into instrument meteorological conditions (IMC); his failure to maintain control of…Dec 12, 1995 · N14BA · DestroyedNTSB LAX95LA292Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-301T · Truckee, CAA failure in the aircraft electrical system, and the pilot's failure (or inability) to extend the landing gear with the emergency extension system. A factor relating to the accident was: the pilot's decision to continue the flight with a known deficiency.Aug 12, 1995 · N8386H · Substantial damageNTSB LAX95FA105Accident · 2 fatalField investigationFinal reportPiper PA-32R-301T · Ceres, CAthe pilot inadvertently becoming lost/disoriented during a missed approach, his failure to follow the proper missed approach procedure, and his failure to maintain control of the aircraft due to spatial disorientation.Feb 11, 1995 · N560LM · DestroyedNTSB MIA94WA215Accident · No injuriesForeign investigationPiper PA32R-301T · Long Island, BahamasSep 20, 1994 · N8374Y · Substantial damageNTSB LAX94FA198Accident · 1 fatalField investigationFinal reportPiper PA-32R-301T · Santa Monica, CAfuel starvation resulting from the failure of the pilot to select a tank containing fuel, and his failure to maintain adequate airspeed while maneuvering for a forced landing which resulted in an inadvertent stall.Apr 20, 1994 · N8171G · DestroyedNTSB LAX94FA157Accident · 3 fatalField investigationFinal reportPiper PA-32R-301T · Napa, CAthe pilot's selection of an en route descent altitude profile inadequate to clear all terrain along his intended flight path, and, his inadvertent VFR flight into IMC conditions. Factors in the accident were the dark night lighting conditions and the obscured…Mar 11, 1994 · N3562C · DestroyedNTSB MIA94LA046Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-301 · Live Oak, FLThe improper use of the fuel selector by the pilot-in-command by switching to an empty fuel tank. Contributing to the accident was the pilot's failure to switch back to a tank with fuel.Jan 4, 1994 · N8331U · Substantial damageNTSB ATL94FA029Accident · 1 fatalField investigationFinal reportPiper PA-32R-301T · Covington, GASpatial disorientation experienced by the pilot, resulting in his failure to maintain aircraft control. Factors were the total failure of the engine driven vacuum pump, and the night, cloud conditions prevailing at the time of the accident.Dec 10, 1993 · N8340Y · DestroyedNTSB LAX92LA299Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-301T · Shafter, CAThe pic's poor preflight planning and the pic's and flight instructor/passenger's failure to use the emergency checklist. The loss of engine power due to fuel starvation was a factor in the accident.Jul 16, 1992 · N327PL · Substantial damageNTSB FTW92GA111Accident · 1 fatalFinal reportPiper PA-32R-301T · Albuquerque, NMFuel line failure due to vibratory fatigue. Factors were improper maintenance, manufacturer information for fuel line not available, and the pilots' failure to follow emergency procedures.Apr 9, 1992 · N8194X · Substantial damageNTSB ATL92FA019Accident · 1 fatalField investigationFinal reportPiper PA-32R-301T · Darden, TNThe pilot's failure to maintain control of the airplane. The pilot exceeded the design limits of the airframe.Oct 29, 1991 · N3559J · DestroyedNTSB CHI90FA174Accident · 2 fatalField investigationFinal reportPiper PA-32R-301T · Ashton, ILA loss of aircraft control for an unknown reason, while en route in instrument meteorological conditions (IMC) on a dark night, and the pilot exceeding the design stress limits of the aircraft while attempting to recover from uncontrolled flight. Factors…Jul 11, 1990 · N43515 · DestroyedNTSB FTW90LA055Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Liberty, TXLoss of engine power due to failure of the tappet faces. A factor in the accident was the unsuitable terrain in which the forced landing was made.Jan 14, 1990 · N8128B · Substantial damageNTSB FTW89FA137Accident · 2 fatalField investigationFinal reportPiper PA-32R-301T · Celina, TXImproper planning/decision by the pilot. Related factors were: failure of the pilot to use all of the available runway area, the runway/terrain conditions, and obstructions/power lines beyond the departure end of the runway.Jul 16, 1989 · N4360K · DestroyedNTSB LAX89LA088Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Santa Ana, CAPoor preflight planning and preparation by selecting the wrong runway despite NOTAM and ATIS information indicating the runway was closed.Jan 18, 1989 · N6913D · Substantial damageNTSB FTW88LA148Accident · No injuriesLimited investigationFinal reportPiper PA-32RT-300 · Edna, TXA delay in initiation of the go-around during the pilot's second attempt to land in the dark night conditions. Contributing to the accident was the runway closure due to construction, which resulted in no runway lights illuminated, and the fact that the pilot…Aug 8, 1988 · N8355L · Substantial damageNTSB CHI88LA170Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Chicago, ILDuring climbout after takeoff, the pilot experienced an engine fire and diverted to Chicago's midway airport for an emergency landing. The pilot executed emergency procedures, shut down the engine, the fuel supply, and all electrical load. When the pilot knew…Jul 20, 1988 · N8069S · Substantial damageNTSB MIA88LA193Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Lake Wales, FLDuring takeoff from the grass strip, the left main landing gear and wingtip collided with runway lights & a fencepost. The acft was slow to climb. After clearing trees at the departure end of the rwy, the acft descended below treetop level, then continued to…Jun 16, 1988 · N4379A · Substantial damageNTSB ATL88FA136Accident · 7 fatalField investigationFinal reportPiper PA-32R-301T · Middlesboro, KYThe plt received preflt wx briefing that stated VFR flt was not recommended due to low pressure system affecting proposed flt path. Wx forecast included tornadoes, hail, thunderstorms to 42,000', moderate rime icing, moderate turbulence, wind gusts to 70 KTS,…Apr 3, 1988 · N8171P · DestroyedNTSB MKC88FA019Accident · 2 fatalField investigationFinal reportPiper PA-32R · Fayetteville, ARThe airplane was cleared to land while on downwind. Tower saw lights and said airplane appeared to be flying around hill north of airport. Investigation revealed airplane had turned left and impacted trees below the top of the hill.Nov 20, 1987 · N3578G · DestroyedNTSB FTW87FA197Accident · No injuriesField investigationFinal reportPiper PA-32R · Mexia, TXThe plt noticed smoke in the cockpit & started to make a precautionary lndg at Mexia, TX, which was nearby. However, drg the dscnt to lnd, the smoke dissipated, so he elected to cont to the destn. Drg the climb back to alt, smoke reappeared & was followed by…Aug 12, 1987 · N8159S · Substantial damageNTSB NYC87LA226Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Ellenville, NYThe pilot lost directional control during takeoff at Ellenville airport and the aircraft ran off the runway colliding with trees and was demolished. No mechanical or structural problems were found during investigation of acft.Aug 11, 1987 · N8337T · DestroyedNTSB LAX87FA281Accident · 4 fatalField investigationFinal reportPiper PA-32R-301T · Monterey, CALoss of control of the aircraft, by the pilot, while excuting a missed approach.Jul 24, 1987 · N82793 · Destroyed