Fatal NTSB investigations: Piper PA-24-250

18 cases on aircraft the registry lists as Piper PA-24-250, where the first occurrence was “In flight encounter with weather”. 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
Fatal NTSB investigations: Piper PA-24-250 per year, 1982–2026: 18 cases
19821
19831
19861
19873
19894
19901
19911
19932
19971
20001
20011
20021

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.\"highestInjuryLevel\" = 'Fatal'
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102404')
      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\" = 240))
  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 LAX03FA051Accident · 2 fatalField investigationFinal reportPiper PA-24-250 · Anaheim Hills, CAthe pilot's encounter with forecast severe turbulence during an inadvertent penetration of an intense weather cell, which resulted in the pilot exceeding the design structural limits of the airplane. A factor in the accident was the pilot's inadequate…Dec 16, 2002 · N6268P · DestroyedNTSB LAX02FA038Accident · 4 fatalField investigationFinal reportPiper PA-24-250 · El Dorado, CAthe pilot's intentional flight into adverse weather conditions and his subsequent failure to maintain aircraft control.Dec 3, 2001 · N6946P · DestroyedNTSB DEN01FA021Accident · 2 fatalField investigationFinal reportPiper PA-24-250 · Antimony, UTthe pilot's failure to maintain aircraft control while maneuvering. Contributing factors were the pilot's failure to obtain a preflight weather briefing, his VFR flight into IMC, lack of instrument certification, spatial disorientation, low ceiling, and snow.Dec 8, 2000 · N8245P · DestroyedNTSB SEA97FA070Accident · 3 fatalField investigationFinal reportPiper PA-24-250 · Boise, IDthe accumulation of airframe ice on the aircraft, and the pilot's delayed remedial action after intentionally flying into forecast adverse weather conditions. The adverse weather (icing) conditions were related factors.Mar 7, 1997 · N7583P · DestroyedNTSB CHI94LA056Accident · 1 fatalLimited investigationFinal reportPiper PA-24-250 · Mcintosh, SDwas continued VFR flight into IMC and the failure to maintain clearance with the terrain. Factors associated with this accident were an inaccurate weather evaluation by the pilot, snow and the rising terrain.Dec 22, 1993 · N8003P · DestroyedNTSB LAX93FA185Accident · 2 fatalField investigationFinal reportPiper PA-24-250 · Twin Peaks, CAThe pilot's inadvertent flight into IMC, the radar controller's issuance of incorrect terrain information, the controller's failure to issue a low altitude safety alert, and the controller's failure to provide emergency services.Apr 24, 1993 · N6884P · DestroyedNTSB ATL91FA073Accident · 1 fatalField investigationFinal reportPiper PA-24-250 · Franklin, TNThe pilot's failure to select a proper fuel tank for flight, resulting in fuel starvation to the engine, and subsequent engine stoppage. Factors were the pilot's inadequate evaluation of the weather conditions along his route of flight, and his flight into…Mar 30, 1991 · N7457P · DestroyedNTSB SEA90FA166Accident · 2 fatalField investigationFinal reportPiper PA-24-250 · Salem, ORThe pilot allowed the design stress limits of the aircraft to be exceeded. Factors related to the accident concerned inadvertent flight by the pilot into known adverse weather conditions.Aug 27, 1990 · N8103P · DestroyedNTSB SEA90FA019Accident · 3 fatalField investigationFinal reportPiper PA-24-250 · Vancouver, WAThe pilot in command's inadequate preflight planning, pilot's attempted VFR flight into IMC conditions and the pilot's lack of instrument qualifications. Contributing to the accident was the low ceiling, fog and the pilot's lack of recent experience.Nov 19, 1989 · N8289P · DestroyedNTSB NYC89FA167Accident · 2 fatalField investigationFinal reportPiper PA-24-250 · Hartleton, PAThe pilot allowed the design stress limits of the aircraft to be exceeded after encountering adverse weather conditions. Weather was a related factor.Jul 16, 1989 · N6206P · DestroyedNTSB MKC89FA110Accident · 2 fatalField investigationFinal reportPiper PA-24-250 · Winslow, ARThe pilot flying into adverse weather conditions which resulted in the in-flight separation of a portion of the right wing. Contributing to the accident was the pilot's lack of total experience.May 15, 1989 · N8199P · DestroyedNTSB LAX89FA137Accident · 1 fatalField investigationFinal reportPiper PA-24-250 · Whitmore, CAThe pilot's decision to continue VFR flight with known forecast IMC along his route.Mar 28, 1989 · N7293P · DestroyedNTSB LAX88FA028Accident · 1 fatalField investigationFinal reportPiper PA-24-250 · Buttonwillow, CAA Piper PA-24-250 collided with terrain while on an IFR flight. The pilot received a wx briefing from fss. While en route, radio and radar contact was lost, then regained. The pilot stated to ATC that the acft had been struck by lightning. He elected to…Oct 29, 1987 · N5431P · DestroyedNTSB DEN87FA178Accident · 3 fatalField investigationFinal reportPiper PA-24-250 · Hayden, COThe plt and two pax were participating in the denver, CO to jackpot, NV air classic. The acft departed, destined for rock springs, WY. The plt was believed by a friend to have been navigating with the use of a recently installed RNAV system. The plt radioed a…Jul 11, 1987 · N7858P · DestroyedNTSB LAX87FA149Accident · 4 fatalField investigationFinal reportPiper PA-24-250 · Jamestown, CADuring the night cross country flt, the accident acft, in company with 2 others, was trying to land at the dest airport in hilly terrain. As the 3 acft approached the airport they encountered bkn to ovrcst conditions of about 400 ft AGL and vis of 2 mi in…Mar 18, 1987 · N5393P · DestroyedNTSB DEN86FA098Accident · 1 fatalField investigationFinal reportPiper PA-24-250 · Truth&Consequen, NMThe plt took off on a night IFR flt after being briefed on adverse wx which included severe turbulence and moderate mixed icing conditions. The acft was not equipped for flt in icing conditions. Radio and radar contact with the flt was lost in the vicinity of…Mar 11, 1986 · N7410P · DestroyedNTSB LAX84FA071Accident · 2 fatalField investigationFinal reportPiper PA-24-250 · Oceanside, CABefore takeoff, the plt received a wx briefing & was advised to expect IFR conditions in the vicinity of Oceanside, CA & that moderate turbulence existed below 20,000 ft. after takeoff, he obtained an IFR clearance to climb & cruise at 6000 ft. at about 2005…Nov 25, 1983 · N6295T · DestroyedNTSB DEN82AA132Accident · 1 fatalFinal reportPiper PA-24-250 · Billings, MTPlt decided to land enroute due wx. At 0803 he contacted Billings fss & was advised Billings wx was 5,000 ft broken. At 0809 he called Billings approach control (a/c) & advised he was 20 mi for landing. Enroute to arpt he was unable to locate the arpt due wx…Jul 9, 1982 · N5356P · Substantial damage