Fatal NTSB investigations: Piper PA-32RT-300T
31 cases on aircraft the registry lists as Piper PA-32RT-300T. 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
| 1980 | 2 |
|---|---|
| 1981 | 2 |
| 1984 | 1 |
| 1985 | 2 |
| 1986 | 1 |
| 1987 | 1 |
| 1988 | 1 |
| 1990 | 2 |
| 1991 | 3 |
| 1992 | 2 |
| 1993 | 2 |
| 1994 | 1 |
| 1997 | 1 |
| 1999 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2005 | 1 |
| 2007 | 1 |
| 2014 | 1 |
| 2015 | 1 |
| 2018 | 1 |
| 2020 | 1 |
| 2021 | 1 |
Where
Open the mapLatest 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 c.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103216'))
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_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."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103216'))
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 ERA21FA133Accident · 2 fatalClass 3 · FieldFinal reportPiper PA32RT · Vinemont, ALA loss of engine power for reasons that could not be determined.NTSB ERA20LA212Accident · 2 fatalClass 3 · LimitedFinal reportPiper PA32RT · Selma, ALThe mechanic’s failure to clean the oil suction screen during the most recent maintenance, which resulted in oil starvation and subsequent total loss of engine power.NTSB CEN18FA368Accident · 1 fatalField investigationFinal reportPiper PA32RT · St Ignace, MIThe pilot's failure to maintain sufficient altitude after takeoff in dark night conditions which resulted in a collision with the water.NTSB WPR16FA041Accident · 5 fatalField investigationFinal reportPiper PA 32RT-300T · Bakersfield, CAThe noninstrument-rated pilot's decision to conduct and continue the flight despite forecast and en route instrument meteorological conditions (IMC), which were not conducive to safe operation under visual flight rules. Also causal to the accident was the…NTSB ERA14FA192Accident · 2 fatalField investigationFinal reportPiper PA-32RT-300T · Hugheston, WVThe pilot's loss of airplane control while operating in instrument flight rules conditions.NTSB ATL07FA069Accident · 2 fatalField investigationFinal reportPiper PA-32RT-300T · Andrews, NCThe pilot's misjudgment of distance and altitude during a night approach for landing, resulting in an in flight collision with wires and the ground.NTSB DFW05RA063Accident · 2 fatalForeign investigationPiper PA-32RT-300 · Guerrero, MexicoNTSB MIA01LA089Accident · 1 fatalLimited investigationFinal reportPiper PA-32RT-300T · Gulfport, MSthe pilot's attempted flight into known adverse weather, resulting in an in flight loss of control, exceedance of design limits of the aircraft, and wing separation prior to collision with water.NTSB ATL01FA008Accident · 1 fatalField investigationFinal reportPiper PA-32RT · Selmer, TNThe pilots inadequate preflight planning and preparation, that resulted in exceeding the designed weight and balance of the airplane. Factors were the pilot's use of inappropriate medications and the collision with trees.NTSB MIA00FA043Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300T · Pelham, ALThe student pilot's decision to continue the visual flight rules flight into deteriorating visibility, and his failure to maintain altitude clearance with the terrain.NTSB FTW97FA171Accident · 3 fatalField investigationFinal reportPiper PA-32RT-300T · Rye, COThe pilot initiating flight into IMC conditions in mountainous terrain. Factors were mountainous terrain, low ceiling, snow, preflight planning, and in-flight planning and decision making.NTSB FTW95FA069Accident · 1 fatalField investigationFinal reportPiper PA-32RT · San Antonio, TXThe loss of engine power for undetermined reasons. A factor related to the accident was: the lack of a suitable area for the forced landing.NTSB ATL94FA011Accident · 5 fatalField investigationFinal reportPiper PA-32RT-300T · Wrens, GAWas the fatique failure of the idler gear which resulted in the complete loss of engine power. A factor was the dark night.NTSB BFO93FA167Accident · 2 fatalField investigationFinal reportPiper PA-32RT-300T · Marshall, VAAn inadequate annual inspection of the airplane and non-compliance with airworthiness directives by company maintenance personnel.NTSB DEN93FA012Accident · 2 fatalField investigationFinal reportPiper PA-32RT-300T · Kersey, COInadvertent stall and loss of control due to structural icing. Factors were: icing conditions, and flight into known adverse weather.NTSB CHI92FA280Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300T · Pullman, MIThe pilot in command's exceeding the design stress limits of the aircraft.NTSB CHI92FA044Accident · 1 fatalField investigationFinal reportPiper PA-32RT/300T · Camdenton, MOThe pilot's disregard for wind conditions, not aborting the takeoff, and inadequate remedial action by the pilot after the airplane became airborne. Factors associated with the accident are an inadequate weather evaluation by the pilot, not maintaining…NTSB SEA91FA235Accident · 1 fatalField investigationFinal reportPiper PA32RT-300T · Mayfield, UTPoor in flight planning/decision. Factors to the accident were: flight into known adverse weather, inadvertent VFR flight into IMC and inadequate clearance.NTSB NYC91FA178Accident · 2 fatalField investigationFinal reportPiper PA-32RT-300T · Yarmouth, MAThe failure of the number one cylinder fuel injector line due to fatigue cracking induced by corrosion and propagated by cyclic loading which resulted in a total loss of engine power. The corrosion was due to the manufacturer's process of brazing the metal…NTSB ANC90LA173Accident · 2 fatalLimited investigationFinal reportPiper PA-32RT-300T · Glacier Island, AKUndetermined mechanical failure(s) that resulted in loss of engine power, smoke in the cockpit, and a subsequent emergency descent for a forced landing (ditching) at sea. The lack of suitable terrain for a forced landing was a related factor.NTSB SEA90FA129Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300T · Prineville, ORThe failure of the left intermediate exhaust pipe, in-flight engine fire and smoke in the cockpit, resulting in impairment of the pilot and his subsequent loss of control.NTSB SEA88FA078Accident · 3 fatalField investigationFinal reportPiper PA-32RT-300T · Port Angeles, WADrg arr, the flt was handed off to whidbey island apch ctl at whidbey island (nuw) naval air stn (nas). Nuw was 35 mi NE of the destn (fairchild intl arpt/clm), at Port Angeles, which had no operg ctl twr. The plt was given the nuw wx, which was 400 scat,…NTSB MKC88FA005Accident · 2 fatalField investigationFinal reportPiper PA-32RT-300T · Lincoln, NEDuring climbout, smoke began filling the cabin and shortly thereafter the eng stopped. Ground witnesses observed smoke coming from the eng compartment just before the acft impacted a large woodpile behind a house located 1/2 mile east of the arpt. Examination…NTSB ATL86FA064Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300T · Milwaukee, NCThe acft was observed to descend and level off at low alt. Witnesses indicated that it leveled off just above the trees, then rolled to the right and dove into wooded terrain. The eng was reported to be running loud and steady until impact. No preimpact part…NTSB BFO86FA002Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300T · Gaithersburg, MDThe plt was clrd for a VOR rwy 14 apch. On apch, he rprtd at the sleet intxn (a fix on the NDB apch). The acft was then seen flying ovr the arpt on an easterly hdg. UNICOM operator said he then heard the plt call "turning final." However, bfr lndg, the acft…NTSB CHI85FA258Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300T · Merom, INThe aircraft was on a visual flight from fairfield Iowa to indianapolis, IN and was about 55 mautical miles south of course when the aircraft broke up in flight. The main wreckage, empennage, and outer wing sections landed within about a quarter of a mile of…NTSB ATL84FA093Accident · 4 fatalField investigationFinal reportPiper PA-32RT-300T · Bluefield, WVThe non-instrument rated plt began his takeoff during the hours of darkness, but in VMC wx. He stated that during the takeoff roll at about 65 to 75 KTS just prior to rotation, the landing light extinguished. Plt stated that 2 to 3 seconds later, he rotated &…NTSB CHI81FA066Accident · 1 fatalClosedPiper PA-32R · Crystal, MNNTSB CHI81FA040Accident · 1 fatalClosedPiper PA-32 · Corunna, MINTSB LAX80FVA03Accident · 2 fatalClosedPiper PA-32 · Merced, CANTSB SEA80FA036Accident · 4 fatalClosedPiper PA32RT · Granite, OR