Piper PA-36-300
NTSB investigations · 57
Matched to the registry by N-number and event date, 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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c.\"mKey\" = a.case_mkey
WHERE a.aircraft_model_code IN ('7103612')
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.
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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c."mKey" = a.case_mkey
WHERE a.aircraft_model_code IN ('7103612')
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB WPR26FA216Accident · 1 fatalClass 3 · FieldPreliminary reportPiper PA-36-300 · Henderson, NEOn June 11, 2026, at 2103 central daylight time, a Piper PA-36-300, N57846, was substantially damaged when it impacted a rotating beacon tower and terrain near Henderson, Nebraska. The pilot was fatally injured. The airplane was operated as a Title 14 Code of…NTSB CEN17LA202Accident · Serious injuriesLimited investigationFinal reportPiper PA36 · El Campo, TXFoam contamination in the fuel injector nozzles from deteriorated foam baffles and water in the fuel flow divider, the combination of which resulted in the loss of engine power.NTSB CEN13LA464Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Santa Teresa, NMThe pilot’s failure to maintain clearance from a tree at the completion of an agricultural spray run. Contributing to the accident was the pilot’s decision to accept a high level of risk to spray a small field bordered by multiple obstacles and his fatigue…NTSB ERA12LA195Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Americus, GAThe failure of maintenance personnel to properly secure a portion of the right wing leading edge, which resulted in the separation of the associated section of the leading edge during takeoff and the loss of directional control during the subsequent landing.NTSB CEN11LA399Accident · 1 fatalLimited investigationFinal reportPiper PA-36-300 · Highmore, SDThe pilot did not maintain control of the airplane while maneuvering at low altitude.NTSB DFW08CA136Accident · No injuriesData collectionFinal reportPiper PA-36 · Thomas, OKThe disconnected throttle linkage resulting in the loss of engine power during takeoff-initial climb. A factor contributing to the accident was the muddy forced landing site.NTSB FTW03LA181Accident · Minor injuriesLimited investigationFinal reportPiper PA-36-300 · Gruver, TXThe loss of engine power for undetermined reasons. A contributing factor was the lack of suitable terrain for the forced landing.NTSB MIA02FAMS3Accident · 1 fatalMissing aircraftFinal reportPiper PA-36-300 · MissingThe falure of the pilot to arrive at the intended destination for undetermined reasons. A finding in the investigation was the fact that clouds with tops to 44,000 feet were noted 38 miles south of the airplane's last position.NTSB CHI01LA214Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Langdon, NDthe pilot stalled the airplane while manuevering to avoid the power lines. A factor was the power lines.NTSB CHI00LA149Accident · No injuriesLimited investigationFinal reportPiper PA-36-200 · Oakley, KSthe directional control not maintained by the pilot. The thunderstorm, quartering tailwind/crosswind and the weather evaluation by the pilot were contributing factors.NTSB SEA00LA078Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Lexington, ORThe pilot's failure to adequately compensate for wind conditions upon encountering a wind shift on takeoff. A factor was variable winds.NTSB CHI98LA219Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Mobridge, SDThe pilot's failure to maintain clearance from the power lines. Factors associated with the accident were the power lines, and the separation of the vertical stabilizer and rudder which resulted in the pilot's inability to maintain directional control of the…NTSB SEA97LA010Accident · 1 fatalLimited investigationFinal reportPiper PA-36-300 · Prosser, WAfailure of the pilot to maintain clearance from the terrain, while en route to an apple orchard that he intended to spray. A factor relating to the accident was: the turbulent wind condition over the hills.NTSB FTW97LA029Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Stanton, TXPilot's failure to maintain clearance with a wire resulting in the separation of the rudder and a loss of aircraft control.NTSB FTW96LA353Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Hale Center, TXthe pilot's inadequate preflight planning/preparation and failure to obtain and/or maintain adequate airspeed after takeoff, which resulted in an inadvertent stall/mush. The overweight condition of the airplane and high density altitude were related factors.NTSB FTW96LA264Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Littlefield, TXThe total loss of engine power due to the failure of the number 5 and 6 connecting rods. A factor was the lack of suitable terrain for the forced landing.NTSB FTW96LA126Accident · Minor injuriesLimited investigationFinal reportPiper PA-36-300 · Andrews, TXthe mechanic's improper overhaul of the engine. Factors were: the pilot in command's inability to maintain visual lookout due to oil on the windscreen and unsuitable terrain for the forced landing.NTSB MIA95LA156Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Atlantic Ocean (Atlantic Ocean)Loss of engine power for an undetermined reason(s).NTSB CHI94LA126Accident · Serious injuriesLimited investigationFinal reportPiper PA-36-300 · Beloit, KSthe pilot's failure to maintain sufficient airspeed during the initial takeoff climb.NTSB CHI93LA185Accident · Minor injuriesLimited investigationFinal reportPiper PA-36-400 · Elbow Lake, MNthe pilot's failure to maintain an adequate visual outlook during aerial application manuevers.NTSB LAX92TL#08Accident · No injuriesClass 3Final reportPiper PA36-300 · Madera, CANTSB CHI91DCQ06Accident · No injuriesFinal reportPiper PA-36-300 · Oakley, KSA loss of engine power for an undetermined reason(s).NTSB CHI90DCQ01Accident · Minor injuriesFinal reportPiper PA 36-300 · Mingo, KSInadequate airspeed resulting in a stall/mush being encountered by the PIC. Contributing factors were a tailwind and a load jettison not performed.NTSB MIA90LA119Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Shelby, MSThe pilot's inadequate preflight planning and attempted flight with insufficient fuel on board to complete the flight.NTSB DEN89DTK01Accident · 1 fatalFinal reportPiper PA-36-300 · Agar, SDThe pilot's failure to maintain an adequate clearance with the powerlines. The powerline is considered to be a contributing factor to the accident.NTSB CHI88DEP12Accident · 1 fatalFinal reportPiper PA-36-300 · Pulaski, WIThe aircraft descended at a high rate of speed, 75 degrees nosedown, into the terrain. His widow stated that the pilot had left home at approximately 2100 CST on the accident night, in an inebriated condition. After a discussion about his drinking, he…NTSB MKC87LA155Accident · Serious injuriesLimited investigationFinal reportPiper PA-36-300 · Swea City, IAThe acft was engaged in ag spray operations near Swea City, Iowa. The PIC stated that he was making a procedure turn after a swath run. The PIC further stated that the acft stalled in the turn and the acft descended into the fld he had been spraying. The PIC…NTSB SEA86LA146Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Moore, IDDuring an aerial application turn a rapid rate of descent developed. The pilot released the chemical load at about 100 feet AGL and the aircraft continued to descend to the ground even though the pilot leveled the wings and initially lowered the nose. The…NTSB FTW86LQG12Accident · No injuriesFinal reportPiper PA-36-300 · Muleshoe, TXThe ag acft was climbing after a pass to clear power lines at the north end of the field. The main lndg gear contacted the top wire as the acft started leveling off. The wire did not break and the acft descended to ground impact. The lndg gear snapped off and…NTSB FTW86LQG01Accident · No injuriesFinal reportPiper PA-36-300 · Fluvanna, TXThe acft contacted a cattle guard during an attempted takeoff for an aerial application flt. The plt reported the acft was overloaded for the length of rwy being used for the takeoff. He continued to report he was too late in dumping the chemical load. The…NTSB CHI85LA336Accident · Minor injuriesLimited investigationFinal reportPiper PA-36-300 · Red Lake Falls, MNThe acft contacted wires during an aerial application flt. The plt stated he was maintaining extra alt to avoid tall weeds and the clearance below the wires was misjudged. The wires severed the vertical fin and rudder.NTSB MIA85FA038Accident · Serious injuriesField investigationFinal reportPiper PA-36-300 · Fellsmere, FLPlt was completing downwind turn when acft began to settle. Plt failed to use full power or jettison the chemical load. As airspeed fell below minimum steady state control spd, acft mushed into grnd.NTSB FTW84LA365Accident · Serious injuriesLimited investigationFinal reportPiper PA-36-300 · Lorenzo, TXAfter completion of a swath run the acft turned right and then left before it descended to the ground in a left bank and nose down attitude. Plt stated that the acft would not recover from the left turn when full right stick travel was applied. The acft was…NTSB CHI84LA238Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Leroy, WIThe acft collided with trees while turning during an aerial application mission. The plt said that the acft started losing altitude in the turn and despite application of full power it continued to settle until trees were hit. The plt reported that during…NTSB FTW81FQG58Accident · Serious injuriesClosedPiper PA-36 · Gruver, TXNTSB FTW81DQG55Accident · No injuriesClosedPiper PA-36 · Clovis, NMNTSB ATL81FKG39Accident · No injuriesClosedPiper PA-36 · Kildare, GANTSB LAX81DVA48Accident · No injuriesClosedPiper PA-36 · Hanford, CANTSB FTW81FQG26Accident · Serious injuriesClosedPiper PA-36 · Lazbuddie, TXNTSB FTW81FQG15Accident · No injuriesClosedPiper PA-36 · Goodland, TXNTSB FTW80FQG39Accident · No injuriesClosedPiper PA-36 · Clovis, NMNTSB LAX80DUJ94Accident · No injuriesClosedPiper PA-36 · Tacna, AZNTSB CHI80FEV26Accident · No injuriesClosedPiper PA-36 · Mc Lean, ILNTSB MIA80FLD57Accident · No injuriesClosedPiper PA-36 · Gardner, FLNTSB DEN79DQG05Accident · Minor injuriesClosedPiper PA-36 · Arch, NMNTSB DEN79FTE70Accident · No injuriesClosedPiper PA-36 · Pueblo, CONTSB MIA79DKG56Accident · No injuriesClosedPiper PA-36 · Denton, GANTSB FTW79FPG51Accident · 1 fatalClosedPiper PA-36 · Tupelo, ARNTSB MIA79DLD66Accident · No injuriesClosedPiper PA-36 · Astatulo, FLNTSB MIA78FKG71Accident · Minor injuriesClosedPiper PA-36 · Cordele, GA
Back to Piper PA-36-300