OpenAirDocs.org

NTSB investigations: Piper PA-23-250

14 cases on aircraft the registry lists as Piper PA-23-250, where the first occurrence was “Airframe/component/system failure/malfunction”. 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

19832026

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 ('7102308')
      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\" = 130))
  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 CHI07LA002Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Marshall, MNThe failure of the nose gear to properly extend for undetermined reasons, which resulted in damage to the forward fuselage during landing.Oct 2, 2006 · N71TA · Substantial damageNTSB NYC06CA080Accident · Serious injuriesData collectionFinal reportPiper PA23-250 · Morristown, NJThe pilot's premature shutdown of both engines, which resulted in a forced landing short of the runway. A factor was a landing gear malfunction indication for undetermined reasons.Mar 20, 2006 · N13878 · Substantial damageNTSB DFW05LA167Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Carizzo Springs, TXThe failure of the stabilator trim control rod due to internal corrosion. A contributing factor was the lack of suitable terrain for the forced landing.Jun 21, 2005 · N2521M · Substantial damageNTSB FTW04LA113Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Sweetwater, TXThe propeller overspeed for undetermined reasons. A contributing factor was the lack of suitable terrain for the forced landing.Apr 20, 2004 · N6257H · Substantial damageNTSB SEA99LA131Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Snohomish, WABrake system failure due to the presence of air bubbles in the hydraulic fluid.Jul 12, 1999 · N65PR · Substantial damageNTSB FTW92LA110Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Denver, COThe loss of hydraulic fluid due to a ruptured hydraulic line in the landing gear system.Apr 3, 1992 · N6460Y · Substantial damageNTSB ATL91LA062Accident · Serious injuriesLimited investigationFinal reportPiper PA-23-250 · Suches, GAThe pilot's failure to maintain altitude during cruise flight after loss of electrical power for an undetermined reason.Mar 1, 1991 · N6546Y · DestroyedNTSB LAX89FA277Accident · 2 fatalField investigationFinal reportPiper PA-23-250 · Lake Tahoe, CADisablement of the stabilator flight control system. A contributing factor was: inadequate maintenance.Aug 14, 1989 · N4838P · DestroyedNTSB DEN86LA239Accident · No injuriesLimited investigationFinal reportPiper PA-23E-250 · Grand Forks, NDThe acft was en route from flin flon airport, manitoba, cd, to mason city, IA, and had stopped at Grand Forks, ND, for fuel and to clear customs. During taxi for takeoff, the acft struck a 1-inch concrete lip on the ramp and the right main landing gear…Aug 26, 1986 · N900TS · Substantial damageNTSB LAX86LA110Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · San Francisco, CAOn feb 9, 1986 at 1717 PST a Piper PA-23, N5300Y, ditched approximately 460 NM sw of sfo, CA. The flt originated from hnl, HI. In flt fuel leak was discovered after 7 hrs of flight. Fuel vapors were seen contrailing off both wings. The plt attempted to…Feb 10, 1986 · N5300Y · DestroyedNTSB CHI85LA079Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · New Philadelphi, OHPlt felt vibration and reduced power on both engines to idle. Plt heard a 'thud' and discovered the left propeller had separated cutting through the nose of the acft as it departed. The propeller was not located. Two of the six propeller bolts remained with…Dec 27, 1984 · N6505Y · Substantial damageNTSB ATL84LA035Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Greer, SCDuring the flt, hydraulic failure of the landing sys occurred & the aircrew were unable to get the gear locked in the down position. After orbiting for over an hour, a landing was made. During touchdown, the gear collapsed. An exam revealed that an aileron…Nov 1, 1983 · N40249 · Substantial damageNTSB FTW83FA415Accident · 2 fatalField investigationFinal reportPiper PA-23-250 · Huffman, TXThe acft collided with the ground in a high speed dive and totally disintegrated. Impact created a 7' crater and material blew out for 100 yards. The engines were recovered at the 14 ft level in the crater. The acft took off at 2215 from baytown TX. At 2334…Sep 3, 1983 · N5551Y · DestroyedNTSB CHI83FA324Accident · No injuriesField investigationFinal reportPiper PA-23-250 · Youngstown, OHDuring an IFR flt, the acft was leveled at 13,000 ft & the power was set at 18 inches manifold pressure & 2300 RPM. Aprx 5 min later, the right eng began to surge to 3000 RPM & almost 'pegged.' The plt attempted to control the right propeller. Finally, the…Jul 19, 1983 · N54072 · Substantial damage