NTSB investigations: Piper PA-32-300, 2001

12 cases on aircraft the registry lists as Piper PA-32-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 per year

19672026
NTSB investigations: Piper PA-32-300, 2001 per year, 1967–2026: 767 cases
196713
196813
196915
197024
197123
197222
197322
197429
197531
197629
197723
197834
197923
198028
198117
198220
198315
198411
198523
198610
198712
198819
198925
19908
199112
199213
199317
199411
199510
199610
199713
199811
199910
200012
200112
200211
200310
20045
20059
20069
20075
20086
20092
20102
20113
20127
20132
20144
20155
20164
20174
201811
20194
20207
20212
202212
20238
20249
20253
20263

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 year(c.\"eventDate\") = 2001
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103212'))
  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 CHI02LA056Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Olathe, KSThe pilot's failure to maintain directional control during landing resulting in the overload of the nose gear fork. The overload failure of the nose landing gear fork, the embankment, and the remedial action not possible were contributing factors.Dec 25, 2001 · N666DE · Substantial damageNTSB FTW02LA039Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Galveston, TXthe pilot's failure to set the parking brake before exiting the aircraft to remove the wheel chocks.Nov 15, 2001 · N60TT · Substantial damageNTSB ATL02LA005Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Lake Wales, FLThe pilot's improper decision to land on a wet sod runway which resulted in a loss of directional control during landing. Factors were the wet grass strip which allowed the airplane to hydroplane.Oct 24, 2001 · N4033W · Substantial damageNTSB ATL01LA095Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Homerville, GAThe improper replacement of an accessory drive component with an unapproved part by maintenance personnel, which resulted in a fatigue fracture of the component and loss of engine power. The airplane subsequently collided with power lines and trees during an…Aug 26, 2001 · N2116G · Substantial damageNTSB ANC01FA093Accident · 6 fatalField investigationFinal reportPiper PA-32-300 · Haines, AKThe pilot's continued flight into known adverse weather conditions, and his poor in-flight decision making. Factors associated with the accident were clouds and mountainous terrain. A finding is the pilot's use of FAA prohibited drugs.Jul 30, 2001 · N39586 · DestroyedNTSB NYC01LA154Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Watch Hill, RILoss of engine power for undetermined reason.Jun 26, 2001 · N4063R · Substantial damageNTSB ANC01LA083Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Eek, AKA malfunction of the engine fuel control due to an improper overhaul by other maintenance personnel, and subsequent loss of engine power during cruise flight. A factor in the accident was unsuitable terrain for a forced landing.Jun 20, 2001 · N43551 · Substantial damageNTSB ANC01LA053Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Chefornak, AKThe pilot's inadvertent stall/mush during the final phase of the landing approach. A factor associated with the accident is a crosswind.May 3, 2001 · N4089W · Substantial damageNTSB MIA01FA126Accident · 4 fatalField investigationFinal reportPiper PA-32-300 · Fort Lauderdale, FLThe pilot's exceeding the forward center of gravity (CG) ) limits at the time of engine start, the inability of the pilot to control the airplane due to the exceeded CG limits, the failure of the pilot to abort the takeoff with sufficient runway remaining,…Apr 19, 2001 · N4103R · DestroyedNTSB DEN01LA054Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Angel Fire, NMthe pilot's failure to maintain control of the airplane during landing. Contributing factors were the crosswind, the pilot exceeding the published maximum demonstrated crosswind component, and the snow bank.Feb 18, 2001 · N3051U · Substantial damageNTSB MIA01LA079Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Lakeland, FLThe pilot's failure to disengage the parking brake prior to taxi and his failure to stop and investigate the brakes when they malfunctioned during taxi for takeoff resulting in the wheel brakes heating and starting the tires on fire.Feb 15, 2001 · N15635 · Substantial damageNTSB MIA01GA070Accident · 2 fatalFinal reportPiper PA-32-300 · Marathon, FLThe pilot-in-command's lack of recent experience in instrument flight resulting in the pilot becoming spatially disoriented, and subsequent in-flight collision with water while descending.Feb 2, 2001 · N99WD · Destroyed