NTSB investigations: Piper PA-32R-300, CA
23 cases on aircraft the registry lists as Piper PA-32R-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
| 1976 | 1 |
|---|---|
| 1977 | 1 |
| 1978 | 3 |
| 1980 | 1 |
| 1981 | 1 |
| 1982 | 1 |
| 1986 | 1 |
| 1987 | 2 |
| 1989 | 1 |
| 1990 | 1 |
| 1991 | 2 |
| 1996 | 1 |
| 1997 | 2 |
| 1999 | 2 |
| 2001 | 1 |
| 2004 | 2 |
Where
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 ('7103213'))
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."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 ('7103213'))
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 LAX04FA102Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Big Pine, CAfailure of the pilot to maintain clearance with mountainous terrain for undetermined reasons.NTSB LAX04LA084Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Riverside, CAengine oil exhaustion due to the extrusion of an oil filter converter plate gasket and the failure of the aircraft owner to comply with a mandatory Service Bulletin and a Federal Aviation Administration emergency Airworthiness Directive.NTSB LAX01FA113Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Essex, CARupture of the fuel injection flow divider diaphragm due to improper manufacture of the raw material stock from which the diaphragm was fabricated. The diaphragm tear resulted in complete engine power loss, which required the pilot to descend into an…NTSB LAX99LA254Accident · No injuriesLimited investigationFinal reportPiper PA32R-300 · Mammoth Lakes, CAThe pilot's failure to attain and maintain an adequate airspeed for the prevailing density altitude. The pilot's failure to abort the takeoff is also causal.NTSB LAX99LA201Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Valley Springs, CAThe fatigue failure and separation of the No. 6 connecting rod end cap, which led to a catastrophic failure of the engine. The fatigue crack initiation was due to galling on the rod end cap, which was most likely caused by an undetermined factory…NTSB LAX98LA027Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Santa Rosa, CALoss of engine power for undetermined reasons.NTSB LAX97LA181Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Burbank, CAimproperly secured upper cowl fasteners by unknown person(s).NTSB LAX96FA226Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Goleta, CAfailure of the flying pilot to maintain control of the airplane, due to spatial disorientation, which resulted in an uncontrolled descent and collision with the water. Factors relating to the accident were: the lack of recent instrument experience by the…NTSB LAX91FA124Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Palm Springs, CAIncapacitation of the pilot due to inadequate sleep.NTSB LAX91LA085Accident · Minor injuriesLimited investigationFinal reportPiper PA 32-300 · Anaheim, CAMaintenance personnel in that they improperly adjusted the left magneto which resulted in the complete erosion of the electrodes from six of the twelve installed spark plugs. The installation of spark plugs with colder heat ranges than specified by the…NTSB LAX90LA108Accident · No injuriesLimited investigationFinal reportPiper PA-32-R-300 · Sacramento, CAAn inadvertent collision with a large bird during the hours of darkness while in the landing pattern.NTSB LAX89LA313Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Mammoth Lakes, CAThe pilot's improper compensation for the existing wind condition and his failure to maintain airspeed. Factors that related to the accident were: the gusty & cross-winds and high density altitude.NTSB LAX88LA074Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Los Angeles, CAWhile taxiing after landing, N911E was instructed to taxi to a position and hold, en route to that position, the acft collided with N75397 that was also holding in the same position. The plt of N911E stated that he did not see the acft due to moisture that…NTSB SEA88FA031Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Lakeport, CAAlthough weather conditions were marginally VFR at his departure point, and the pilot had access to a vehicle which could have been used to drive to his dest, he departed novato, CA, enroute to Lakeport, CA, without obtaining a wx briefing nor filing a flt…NTSB LAX87LA048Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · San Jose, CAA Piper pa 32R-300 landed short of the rwy after a loss of power. The plt reported during the climb that he turned on the heater and the windshield turned black obscuring outside vision. The plt also indicated that there was a 'pungent odor' at the same time.…NTSB LAX82DVG19Accident · No injuriesFinal reportPiper PA-32R · Brownsville, CAThe pilot stated that the aircraft did not touchdown until halfway down the runway and he then applied too much left brake resulting in the aircraft running off the left side of the runway. Before coming to a stop the left landing gear collapsed.NTSB LAX81FVD16Accident · No injuriesClosedPiper PA-32R · Petaluma, CANTSB LAX80FUJ52Accident · 2 fatalClosedPiper PA-32R · Needles, CANTSB LAX79FA018Accident · Serious injuriesClosedPiper PA-32 · Los Angeles, CANTSB LAX79FA010Accident · 2 fatalClosedPiper PA-32 · Mojave, CANTSB LAX78DUG27Accident · No injuriesClosedPiper PA-32R · Yucca Valley, CANTSB OAK77FA044Accident · 2 fatalClosedPiper PA-32R · Tahoe Paradise, CANTSB OAK76AP069Accident · 4 fatalClosedPiper PA-32R · North Fork, CA