NTSB investigations: Piper PA-32-300, CA

78 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, CA per year, 1967–2026: 78 cases
19671
19683
19692
19704
19712
19732
19743
19753
19762
19774
19783
19795
19804
19811
19835
19843
19856
19861
19871
19881
19892
19902
19911
19922
19932
19951
19991
20001
20091
20121
20151
20181
20211
20221
20231
20242
20251

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 c.\"eventStateOrRegion\" = 'CA' AND c.\"eventCountry\" = 'USA'
    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 ANC25LA032Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-32-300 · Redding, CAThe pilot's failure to maintain a stabilized approach and his delayed action to perform a go-around, resulting in a collision with the runway surface.Mar 8, 2025 · N32371 · Substantial damageNTSB WPR25LA039Accident · Serious injuriesClass 3 · LimitedFinal reportPiper PA32-300 · Pomona, CAA total loss of engine power during final approach for reasons that could not be determined.Nov 17, 2024 · N617ET · Substantial damageNTSB WPR24LA283Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-32-300 · Fallbrook, CAThe pilot’s failure to maintain clearance from an obstacle during taxi operations.Aug 9, 2024 · N56631 · Substantial damageNTSB WPR23LA363Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-32-300 · Needles, CAAn encounter with windshear during the initial climb after takeoff, resulting in a loss of control and a subsequent hard landing.Aug 13, 2023 · N2957N · Substantial damageNTSB WPR22LA296Accident · No injuriesClass 3 · LimitedFinal reportPiper PA-32-300 · Corona, CAThe airplane’s partial loss of engine power during the landing for reasons that could not be determined based on the available evidence, which resulted in an off airport landing and subsequent fire.Aug 9, 2022 · N841AD · Substantial damageNTSB WPR21LA326Accident · No injuriesClass 3 · LimitedFinal reportPiper PA-32-300 · Del Mar, CAThe partial loss of engine power for reasons that could not be determined, which resulted in a forced landing on an interstate highway and subsequent collision with vehicles.Aug 24, 2021 · N2843T · Substantial damageNTSB WPR18LA203Accident · Serious injuriesClass 3 · LimitedFinal reportPiper PA32 · Avalon, CAThe pilot's delayed decision to conduct a go-around following an unstable landing approach and long landing.Jul 25, 2018 · N4747H · Substantial damageNTSB WPR15LA157Accident · No injuriesLimited investigationFinal reportPiper PA 32-300 · Redlands, CAThe partial loss of engine power during takeoff due to oil starvation.May 9, 2015 · N4124R · Substantial damageNTSB WPR12CA400Accident · No injuriesData collectionFinal reportPiper PA-32-300 · Lancaster, CAThe student pilot’s inadvertent selection of an empty fuel tank.Sep 4, 2012 · N308DF · Substantial damageNTSB WPR09FA158Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Corona, CAThe pilot did not maintain airplane control during climb due to spatial disorientation while flying in instrument meteorological conditions. Contributing to the accident was the pilot's lack of recent instrument flying experience.Mar 20, 2009 · N55962 · Substantial damageNTSB LAX00LA088Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Ukiah, CAfailure of the pilot to comply with the checklists in the Owner's Handbook, resulting in a total loss of engine power due to fuel exhaustion.Feb 16, 2000 · N1452T · Substantial damageNTSB LAX00LA065Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Fallbrook, CAthe pilot's misjudged altitude and distance during a night landing approach, which resulted in an undershoot.Dec 31, 1999 · N1412T · Substantial damageNTSB LAX96FA050Accident · 3 fatalField investigationFinal reportPiper PA-32-300 · Fullerton, CAthe pilot-in-command's failure to follow IFR procedures in that he descended below the minimum descent altitude and failed to execute a missed approach. Contributing to the accident was the pilot-in-command's self-induced pressure to get to work.Nov 20, 1995 · N888JK · DestroyedNTSB LAX94FA005Accident · 3 fatalField investigationFinal reportPiper PA-32-300 · Kernville, CAthe pilot's inadvertent flight into a box canyon and his failure to attain a safe altitude. A factor in the accident was the pilot's lack of familiarity with the geographic area.Oct 3, 1993 · N4018W · DestroyedNTSB LAX93FA119Accident · 4 fatalField investigationFinal reportPiper PA-32-300 · Truckee, CAThe pilot's continued VFR flight into instrument meteorological conditions. The adverse weather conditions contributed to the accident.Feb 15, 1993 · N15267 · DestroyedNTSB LAX92LA402Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Gasquet, CAThe pilot failed to receive available wind information and selected the wrong landing runway. A contributing factor related to his expecting the local wind to be coming from the same direction as it had been reported at a neighboring airport.Sep 25, 1992 · N3410M · Substantial damageNTSB LAX92LA266Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Coalinga, CAThe failure of the pilot to maintain the proper glide path during the night VFR approach which resulted in a landing undershoot and a subsequent collision with the raised asphalt lip of the runway edge.Jun 29, 1992 · N4065R · Substantial damageNTSB LAX91LA315Accident · 2 fatalLimited investigationFinal reportPiper PA32-300 · Corona, CAThe pilot's failure to maintain an airspeed above the aircraft's stall speed after the engine failed. Factors contributing to the accident were: the failure of the engine, magneto and accessory drive gear, the rough terrain conditions over which the engine…Jul 17, 1991 · N5233S · Substantial damageNTSB LAX90FA213Accident · 3 fatalField investigationFinal reportPiper PA-32-300 · Havasu Landing, CAFailure of the pilot to properly secure an oil supply line b-nut fitting after an oil change, which allowed the oil line to become disconnected and led to oil exhaustion and subsequent engine failure. A factor related to the accident was: unsuitable terrain…Jun 10, 1990 · N3AH · DestroyedNTSB LAX90LA085Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Mammoth Lakes, CAThe pilot's inadequate removal of ice from the fuselage, wings, and horizontal stabilizer prior to takeoff.Feb 5, 1990 · N8620N · Substantial damageNTSB LAX90LA056Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-300 · Big Bear, CAThe pilot's improper level-off and improper recovery from a bounced landing.Dec 23, 1989 · N4111W · Substantial damageNTSB LAX89LA100Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Gualala, CAPilot misjudged the altitude and distance to the runway and subsequently did not attain the proper touchdown point.Jan 27, 1989 · N4235R · Substantial damageNTSB LAX89FA013Accident · 3 fatalField investigationFinal reportPiper PA-32-300 · Santa Maria, CAThe pilot failed to follow the correct I.f.r. procedures whereas he descended below the final approach fix altitude.Oct 12, 1988 · N6198H · DestroyedNTSB LAX87LA182Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Lincoln, CAThe aircraft collided with a ditch after a loss of pwr during t/o climb at aprx 350 to 400 ft AGL. The plt described the loss of pwr as 'like taking the throttle and pulling off in a rapid motion.' He noticed during his preflt check that the fuel in the right…Apr 19, 1987 · N15259 · Substantial damageNTSB LAX86LA343Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Riverside, CAWhile en route to hawthorne airport the aircraft experienced a total loss of power. During a circling descent the pilot attempted to restart the engine without success. The aircraft collided with the terrain 500 ft short of rwy 27 at Riverside airport. The…Aug 25, 1986 · N4083R · Substantial damageNTSB LAX86LA055Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Santa Maria, CAAfter completing a nighttime business flight, the plt landed and taxied to parking. Enroute the plt attempted to taxi between two hangars and around a wash rack. The acft collided with an unmarked curb adjacent to the wash rack and the gear collapsed bending…Nov 28, 1985 · N32998 · Substantial damageNTSB LAX86LA001Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Van Nuys, CAThe plt stated that after takeoff he climbed to 1800 ft MSL (aprx 1000 ft above ground level) and entered a left turn. The eng failed in the turn an he selected a dry flood control basin on which to land. The acft's airspeed was slow on landing and the…Oct 2, 1985 · N9AZ · Substantial damageNTSB LAX85LA248Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Baker, CAPlt became lost on a daylight VFR flt and was unable, because of her low altitude, to receive any nav radio aids or establish radio communications. Because of apch darkness and a low fuel state she elected to perform a precautionary landing on a dirt strip.…May 5, 1985 · N15259 · Substantial damageNTSB LAX85LA226Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Oroville, CAAfter overflying the arpt to evaluate local conditions, the PIC elected to land on rwy 01. The wind was estimated from 330 degs at 15 KTS with gusts to 20 KTS. The PIC reported that on final apch with the acft's flaps fully extended, she observed that the…Apr 27, 1985 · N15420 · Substantial damageNTSB LAX85LA143Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Hayward, CAWhile the instructor plt (CFI) & student were practicing landings, the eng lost power during the initial climb of the 4th touch-&-go at aprx 30 to 40 ft AGL. The CFI took control of the acft & attempted to land on the remaining rwy. However, the acft…Feb 16, 1985 · N4186W · Substantial damageNTSB LAX85LA133Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Big Bear, CAAfter spending the day skiing, the plt & passengers planned to depart on a return flt to san diego. The wind was from 210 to 220 deg at about 10 mph. The plt elected to takeoff on rwy 7 since low clouds were approaching from the west & the visibility was near…Feb 4, 1985 · N30069 · Substantial damageNTSB LAX84FA407Accident · 3 fatalField investigationFinal reportPiper PA-32-300 · Goleta, CAThe plt radioed to the santa barbara tower that he was 'without power' & was going to attempt to land in an open field. However, during the forced landing, the acft collided with trees aprx 50 ft short of the field. An exam of the eng revealed that the fuel…Jul 21, 1984 · N8632N · DestroyedNTSB LAX84IA353Incident · No injuriesIncident investigationFinal reportPiper PA-32-300 · Chowchilla, CAThe acft collided with VASI lights during an unscheduled landing when plt became ill & according to the passengers became unconscious. The passenger, a non-plt, landed the acft. The plt was transported by ambulence to a nearby hospitalwhere doctors stated…Jun 15, 1984 · N32139 · Minor damageNTSB LAX84FA144Accident · Serious injuriesField investigationFinal reportPiper PA-32-300 · Oxnard, CAThe acft made a forced landing and collided with irrigation pipes which criss-crossed a freshly plowed field after the engine lost power during a night cruise. After the accident the fuel selector valve was found in the off position and nofuel was in the…Jan 19, 1984 · N4012R · DestroyedNTSB LAX83LA401Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Bermuda Dunes, CAThe acft encountered a downdraft during short final & touched down in sandy terrain a few feet short of the rwy. The right main landing gear failed as the acft struck the end of the asphalt rwy. The plt had been advised over UNICOM of a possible wind shear…Aug 22, 1983 · N3957X · Substantial damageNTSB LAX83FA185Accident · 6 fatalField investigationFinal reportPiper PA32-300 · Weaverville, CAThe acft was being flown to a uni-directional arpt with an instructor plt (CFI) in the right front seat & a student plt/prospective buyer in the left front seat. The rwy elevation was 2230 ft MSL at the south end & 2350 ft at the north end. North of the rwy,…Apr 9, 1983 · N15351 · DestroyedNTSB LAX83LA165Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Gorman, CAEncountering clouds enroute the plt descended to fly through the teton pass. After confirming a VFR check point, he commenced a climb. Shortly thereafter the acft struck a powerline.Mar 28, 1983 · N4235R · Substantial damageNTSB LAX83LA094Accident · No injuriesLimited investigationFinal reportPiper PA-32 · So. Lake Tahoe, CAThe takeoff was initiated downwind on runway 36, which was 8544 ft long and was wet. The field elevation was 6264 ft. the aircraft was observed by tower personnel to rotate about 3000 ft down the runway, then climb to about 50 ft AGL. The pilot elected to…Feb 7, 1983 · N4069R · Substantial damageNTSB LAX83FUG13Accident · 3 fatalFinal reportPiper PA-32-300 · Palm Springs, CAThe acft crashed during takeoff at the end of the runway after the engine lost power. After he was cleared for takeoff the pilot started down the runway. At the runways end according to a surviving passenger the pilot said we are in trouble. He called the…Jan 18, 1983 · N5208S · DestroyedNTSB LAX81DUG13Accident · No injuriesClosedPiper PA-32 · Salton Sea, CAFeb 14, 1981 · N47831 · Substantial damageNTSB LAX81DUG02Accident · No injuriesClosedPiper PA-32 · Rialto, CAOct 28, 1980 · N29172 · Substantial damageNTSB LAX80FVG21Accident · Serious injuriesClosedPiper PA-32 · Angwin, CAMar 22, 1980 · N2906V · DestroyedNTSB LAX80DXQ21Accident · No injuriesClosedPiper PA-32 · Mammoth Lakes, CAMar 20, 1980 · N102YT · DestroyedNTSB LAX80FA041Accident · 1 fatalClosedPiper PA-32 · Catalina Is, CAJan 26, 1980 · N2781M · DestroyedNTSB LAX79FA060Accident · 1 fatalClosedPiper PA-32 · Burmuda Dunes, CAJul 11, 1979 · N15325 · DestroyedNTSB LAX79FUQ37Accident · No injuriesClosedPiper PA-32 · Burbank, CAJun 22, 1979 · N4106R · Substantial damageNTSB LAX79DUG48Accident · Minor injuriesClosedPiper PA-32 · Hesperia, CAJun 17, 1979 · N4085W · Substantial damageNTSB OAK79FA030Accident · 1 fatalClosedPiper PA-32 · Groveland, CAMay 11, 1979 · N44698 · DestroyedNTSB LAX79FA050Accident · 1 fatalClosedPiper PA-32 · La Posta, CAMay 8, 1979 · N47534 · DestroyedNTSB LAX78FUQ35Accident · Minor injuriesClosedPiper PA-32 · Van Nuys, CAJul 6, 1978 · N4247R · Destroyed