NTSB investigations: Piper PA-31-350, CA
14 cases on aircraft the registry lists as Piper PA-31-350. 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 | 1 |
|---|---|
| 1982 | 1 |
| 1984 | 2 |
| 1988 | 1 |
| 1989 | 4 |
| 1994 | 1 |
| 1995 | 1 |
| 1996 | 1 |
| 1998 | 1 |
| 2008 | 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.\"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 ('7103110', '7103125'))
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 ('7103110', '7103125'))
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 WPR09LA014Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Fresno, CAThe pilot misjudged the flare resulting in a hard landing.NTSB LAX98FA106Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · Novato, CAthe pilot's failure to maintain adequate terrain clearance after initiating a descent over mountainous terrain at night and under marginal VFR conditions. The pilot's self-induced pressure to arrive at class with enough time remaining to take the final…NTSB LAX96LA289Accident · Minor injuriesLimited investigationFinal reportPiper PA-31-350 · Kneeland, CAthe pilot's misjudgment of distance and speed, during the landing, and his failure to execute a go-around, when a proper touchdown point was not attained.NTSB LAX96FA078Accident · 2 fatalField investigationFinal reportPiper PA-31-350 · San Jose, CAThe failure of the air traffic controller to comply with instructions contained in the Air Traffic Control Handbook, FAA Order 7110.65, which resulted in the flight being vectored at an altitude below the minimum vectoring altitude (MVA) and failure to issue…NTSB LAX94FA149Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · Frazier Park, CAthe pilot's failure to select a cruise altitude which would ensure adequate terrain clearance. Contributing factors related to the dark, nighttime condition and to the pilot's lack of attentiveness.NTSB LAX90LA036Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Ontario, CAImproper use of the brakes by the pilot of the Piper PA-31.NTSB LAX89FA314Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · Ontario, CAFailure of the right propeller hub due to metal fatigue which resulted in catastrophic separation of the propeller. Contributing to the accident was damage done to the aircraft airframe in flight by the separating propeller making the aircraft uncontrollable.NTSB LAX89LA199Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Arcata, CAThe pilots inaccurate fuel consumption calculations and improper fuel tank selector position. These resulted in fuel starvation to both engines when the aux tanks ran dry and the mains had fuel remaining in them. A factor in this accident was the rough…NTSB LAX89LA147Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Salinas, CAThe pilot's failure to maintain proper taxiway alignment, when he diverted his attention, while taxiing. The location of the parked aircraft was a related factor.NTSB LAX88FA169Accident · Serious injuriesField investigationFinal reportPiper PA-31-350 · Hayward, CAPilot's failure to detect an uncommanded propeller feathering procedures established in the pilot's operating handbook.NTSB LAX84FA328Accident · 2 fatalField investigationFinal reportPiper PA-31-350 · Baker, CAThe acft was found where it had crashed & burned on a rough lava bed. The crash site was about 1 mi northeast of a road where drug smuggling acft had been known to land in the past. There was evidence that cocaine had been removed from the accident site. The…NTSB LAX84IA147Incident · No injuriesIncident investigationFinal reportPiper PA-31-350 · Redding, CAWhile taxiing to takeoff, smoke was noted in the cockpit area, shortly after the plt activated the heater ignition switch. The plt immediately stopped & secured the acft & assisted the passengers in deplaning. An exam of the janitrol heater, model B4050,…NTSB LAX83LA032Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Alturas, CAThe aircraft was landed long on a wet runway, and after overrunning the departure end, it collided with a fence and a dirt bank.NTSB LAX80FVD06Accident · No injuriesClosedPiper PA-31 · Oakland, CA