OpenAirDocs.org

NTSB investigations: Piper PA-31-350

18 cases on aircraft the registry lists as Piper PA-31-350, where the first occurrence was “In flight collision with terrain/water”. 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

19822026

Where

Open the map

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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103110', '7103125')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 230))
  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 LAX00FA014Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · North Las Vegas, NVThe failure of the pilot-in-command to maintain separation from terrain while operating under visual flight rules. Contributing factors were the improper issuance of a suggested heading by air traffic control personnel, inadequate flight progress monitoring…Oct 15, 1999 · N1024B · DestroyedNTSB DCA99MA088Accident · 10 fatalMajor investigationFinal reportPiper PA-31-350 · Volcano, HIthe pilot's decision to continue visual flight into instrument meteorological conditions (IMC) in an area of cloud-covered mountainous terrain. Contributing to the accident were the pilot's failure to properly navigate and his disregard for standard operating…Sep 26, 1999 · N411WL · DestroyedNTSB DEN99FA016Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · Hayden, COThe pilot not following instrument procedures and subsequently descended to minimums prematurely. Factors were the mountainous terrain and the falling snow.Oct 28, 1998 · N35533 · DestroyedNTSB 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…Mar 6, 1998 · N257NW · DestroyedNTSB 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…Dec 23, 1995 · N27954 · DestroyedNTSB ANC95LA050Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Dillingham, AKThe pilot's inadequate preflight planning and preparation. Factors associated with the accident are: the dispatcher's decision to dispatch a multi-engined airplane to a short, soft airstrip, and inadequate company management oversight/surveillance.May 8, 1995 · N3588Z · Substantial damageNTSB 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.Mar 4, 1994 · N78DE · DestroyedNTSB LAX92FA058Accident · 5 fatalField investigationFinal reportPiper PA31-350 · Temple Bar, AZThe pilot-in-command's poor inflight decision by not electing to proceed to an alternate airport and to continue to the flight under visual flight rules into instrument meteorological conditions. The low ceilings and visibilities across the flight route and…Dec 10, 1991 · N350MR · DestroyedNTSB ATL91FA052Accident · 4 fatalField investigationFinal reportPiper PA-31-350 · Munford, ALThe pilot attempting visual flight in instrument meteorological conditions below the minimum safe altitude for terrain clearance. Contributing factors were the low ceiling and mountainous terrain.Feb 7, 1991 · N27818 · DestroyedNTSB ANC91FA017Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · Evanston, WYThe pilot's premature descent. Contributing to the accident was the pilot's fatigue and poor weather.Dec 18, 1990 · N4082H · DestroyedNTSB NYC90FA039Accident · 6 fatalField investigationFinal reportPiper PA-31-350 · Cairo Township, NYThe pilot's decision to fly into the known adverse weather and his failure to select an altitude that would provide terrain clearance. Factors were: the adverse weather and the pilot's disregard for the forecasted conditions.Dec 15, 1989 · N45CH · DestroyedNTSB ANC87IA032Incident · No injuriesIncident investigationFinal reportPiper PA-31-350 · Barter Island, AKThe pilot flew into rising terrain during a night VFR flight. After shutting down the right engine and achieving only partial propeller feather he elected to make a gear up landing. The plt was flying at 500 ft AGL when he wandered from over water to on-shore…Feb 4, 1987 · N35232 · Minor damageNTSB MIA87LA024Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Homestead, FLThe plt stated that he thought he had put the gear handle down but on touchdown the gear was up and the aircraft slid to a stop on the runway. Post crash examination of the landing gear system revealed that the landing gear was up when it contacted the runway…Nov 5, 1986 · N27418 · Substantial damageNTSB ANC86IA069Incident · No injuriesIncident investigationFinal reportPiper PA-31-350 · Nulato, AKA witness on the ground watched the airplane fly the landing pattern for landing and at no time did he see the landing gear extend. He watched the airplane until it passed below the tree line. Testing of the hydro-mechanical and electrical systems did not…Jun 10, 1986 · N41078 · Minor damageNTSB 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…Jun 2, 1984 · N6GW · DestroyedNTSB MKC84LA031Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Waterloo, IAAfter takeoff for an FAA part 135 check ride, the aircrew were unable to get a positive up indication for the landing gear. The gear was recycled & then the left main gear would not get a down & locked indication. Repeated attempts to extend the left main…Nov 28, 1983 · N600TS · Substantial damageNTSB MKC83FA045Accident · 2 fatalField investigationFinal reportPiper PA-31-350 · Dubuque, IAAt 2015 the flt contacted ARTCC & requested Dubuque wx. They were advised that Dubuque was 500 ft indefinite ceiling, sky obscured, visibility 1/2 mi fog & they would be vectored for a back course rwy 13 apch. The flt then requested the front course apch to…Dec 25, 1982 · N4091U · DestroyedNTSB ATL83AA029Accident · 1 fatalFinal reportPiper PA-31-350 · Brevard, NCAfter a missed approach at asheville the flt was cleared to the greenville-spartanburg arpt at greer,SC. Enroute to greer radar contact was lost. In response to a query from atlanta ARTCC the plt verified his position as being on the 235 deg radial of…Nov 12, 1982 · N59771 · Destroyed