NTSB investigations: Piper PA-32-301T
27 cases on aircraft the registry lists as Piper PA-32-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 per year
| 1981 | 2 |
|---|---|
| 1982 | 3 |
| 1983 | 1 |
| 1984 | 1 |
| 1986 | 2 |
| 1987 | 1 |
| 1989 | 2 |
| 1992 | 3 |
| 1997 | 1 |
| 1998 | 1 |
| 2001 | 1 |
| 2005 | 2 |
| 2007 | 1 |
| 2009 | 1 |
| 2012 | 1 |
| 2013 | 1 |
| 2017 | 1 |
| 2023 | 1 |
| 2024 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103209'))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103209'))
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 ERA24LA111Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-32-301T · Palm Beach Gardens, FLThe pilot’s failure to maintain directional control of the airplane during the landing roll in a gusting crosswind.NTSB CEN23FA079Accident · 2 fatalClass 3 · FieldFinal reportPiper PA-32-301T · Kingfisher, OKAn oil leak of undetermined origin that resulted in an in-flight engine compartment fire and subsequent loss of airplane control.NTSB GAA18CA094Accident · No injuriesData collectionFinal reportPiper PA32 · Spearfish, SDThe pilot’s inadvertent landing in snow adjacent to the snow-covered runway resulting in a collision with runway signs.NTSB CEN13LA365Accident · No injuriesLimited investigationFinal reportPiper PA-32-301T · Lansing, MIThe pilot’s failure to follow the airplane checklist, which resulted in the parking brake not being released before taxi and a subsequent brake fire.NTSB WPR12FA369Accident · 5 fatalField investigationFinal reportPiper PA-32-301T · South Lake Tahoe, CAA partial loss of engine power for reasons that could not be determined because examinations revealed no evidence of mechanical anomalies with the airframe or engine that would have precluded normal operation and the pilots’ decision to continue the departure…NTSB ERA09CA213Accident · No injuriesData collectionFinal reportPiper PA32 · Merritt Island, FLThe pilot's failure to maintain directional control during the landing roll.NTSB DEN07CA105Accident · Minor injuriesData collectionFinal reportPiper PA-32-301T · Santa Fe, NMThe pilot's inadequate preflight planning and preparation, and improper in-flight decisions resulting in fuel exhaustion. A factor was the unsuitable terrain for landing.NTSB LAX05LA126Accident · No injuriesLimited investigationFinal reportPiper PA-32-301T · Long Beach, CAThe pilot's failure to maintain directional control during the landing rollout.NTSB MIA05LA070Accident · No injuriesLimited investigationFinal reportPiper PA-32-301T · Destin, FLThe pilot's inadequate compensation for wind during a crosswind takeoff resulting in a loss of directional control and subsequent collision with terrain.NTSB CHI02LA019Accident · No injuriesLimited investigationFinal reportPiper PA-32-301T · Phillips, WIThe fuel starvation encountered on takeoff and unsuitable terrain the pilot encountered during the forced landing. A factor was the fuel selector valve malfunction.NTSB FTW98LA415Accident · No injuriesLimited investigationFinal reportPiper PA-32-301T · Austin, TXThe collision with deer during the landing roll. Factors were the dark night light condition and the separation of the lower strut assembly from the right main landing gear, on the subsequent flight.NTSB SEA97FA120Accident · 2 fatalField investigationFinal reportPiper PA-32-301T · Bend, OROverload of the airframe structure. Thunderstorms and turbulence were factors.NTSB LAX93LA064Accident · No injuriesLimited investigationFinal reportPiper PA-32-301T · Auburn, CAFailure of the pilot to maintain direction control during the landing touchdown. Contributing to the accident inadequate maintenance of the runway safety area by airport personnel.NTSB DEN92FA085Accident · 3 fatalField investigationFinal reportPiper PA-32-301T · Kit Carson, COThe pilot becoming spatially disoriented and exceeding the design stress limits of the aircraft. Factors were: the pilot's failure to obtain a weather briefing, his attempted VFR flight into a level six thunderstorm, and his lack of instrument time.NTSB LAX92LA309Accident · No injuriesLimited investigationFinal reportPiper PA32-301T · Van Nuys, CAAn on ground collision with terrain subsequent to an engine failure for undetermined reasons.NTSB MIA89LA258Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-301T · Kissimmee, FLInadequate preflight by the pilot, which resulted in fuel exhaustion, due to an inadequate supply of fuel. Factors related to the accident were: false fuel gage indications and trees in the emergency landing area.NTSB DEN89LA164Accident · No injuriesLimited investigationFinal reportPiper PA-32R-301T · Telluride, COThe pilot's failure to maintain aircraft control during an encounter with turbulence. Contributing to the accident was the turbulence.NTSB ANC87LA090Accident · No injuriesLimited investigationFinal reportPiper PA-32-301T · Becharof Lake, AKThe pilot stated he was rolling out for takeoff when the nose wheel struck a soft area causing the aircraft to go up on its nose.NTSB DEN87FA017Accident · Serious injuriesField investigationFinal reportPiper PA-32-301T · Cheyenne, WYThe plt and his two pax were on a VFR x-country to scottsbluff, NE, when IMC was encountered near grand junction, CO. The plt then called ATC and obtained an IFR clearance. The plt elected to land at Cheyenne, WY. Wx was reported to be 500 overcast, 1/4 mi…NTSB SEA86FA098Accident · 2 fatalField investigationFinal reportPiper PA-32-301T · Fort Hall, IDRadar track showed acft made normal climb on course from airport (elev 4488 ft MSL) to 9400 ft. MSL, then executed a left turn of about 90 degrees, climbing to 9700 ft MSL as shown by next-to-last radar tgt. 29 secs later, final radar tgt showed 6900 ft MSL.…NTSB FTW84LA178Accident · No injuriesLimited investigationFinal reportPiper PA-32-301T · Haskell, TXThe plt received a wx briefing and said, 'today was not the day to go', but later went. En route weather encouraged him to land at an arpt with a 1600 ft rwy with winds of 30 KTS gusting to 50 KTS, according to a witness. The plt landedwith no flaps and…NTSB LAX83FA424Accident · 4 fatalField investigationFinal reportPiper PA-32-301T · San Marcos, CAAt aprx 2209 PDT, the plt departed fresno, CA on a night, VFR, x-country flt. He cancelled his VFR flt plan at 0009 PDT & landed at ramona, CA at 0012. After landing, he called his wife to inquire about the wx at palomar, CA. She looked out the window &…NTSB ATL82DA094Accident · No injuriesFinal reportPiper PA-32-301T · Lexington Park, MDThe pilot stated that while decelerating through approximately 50 knots on landing rollout he lowered the nose. The nose gear collapsed after encountering a soft spot on the runway.NTSB SEA82DA036Accident · No injuriesFinal reportPiper PA-32-301T · Hailey, IDAfter an engine run-up with the parking brake set, the first attempt to takeoff was aborted when the plane failed to accelerate satisfactorily. The brakes operated satisfactorily during the abort and a second run-up revealed no unusual engine indications.…NTSB DEN82DA028Accident · Serious injuriesFinal reportPiper PA-32 · Rock Springs, WYThe aircraft departed vernal,ut at 1810 MST after refueling. During the VFR flight the pilot reported to Rock Springs fss that he was 20 miles south and was given current weather and runway in use. No other transmissions were received. The aircraft struck a…NTSB FTW81DQD33Accident · No injuriesClosedPiper PA-32 · Timberon, NMNTSB LAX81FVW15Accident · No injuriesClosedPiper PA-32 · Henderson, NV