Final NTSB investigations: Piper PA-23-250, 2004

7 cases on aircraft the registry lists as Piper PA-23-250. 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

19642026
Final NTSB investigations: Piper PA-23-250, 2004 per year, 1964–2026: 812 cases
196428
196540
196633
196741
196825
196934
197033
197127
197230
197332
197432
197520
197627
197724
197822
197929
198026
198113
198222
198317
198413
198520
198615
198715
198813
19896
19906
199114
19926
199310
199413
199517
199610
19976
19986
19995
20003
20013
20023
20037
20047
200511
200611
20073
20081
20091
20112
20122
20135
20142
20151
20161
20174
20181
20196
20204
20211
20231
20241
20251

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 year(c.\"eventDate\") = 2004
    AND c.\"completionStatus\" = 'Completed'
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102308'))
  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 CHI05FA049Accident · 5 fatalField investigationFinal reportPiper PA-23-250 · Ironwood, MIFatigue fracture of an engine cylinder resulting in a loss of power on the left engine. Additional causes were the pilot's failure to maintain minimum control airspeed (Vmc), the resulting loss of aircraft control, and an inadvertent stall/spin. Contributing…Dec 28, 2004 · N5398M · Substantial damageNTSB CHI05FA024Accident · Serious injuriesField investigationFinal reportPiper PA-23-250 · Detroit, MIThe pilot's failure to feather the propeller and to maintain control of the airplane following the loss of engine power which resulted from undetermined reasons. Factors associated with the accident were the power lines and the house that the airplane…Nov 8, 2004 · N63887 · DestroyedNTSB MIA05LA013Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · San Juan, PRThe pilot-in-command's failure to maintain airspeed while on base to final leg, which resulted in an inadvertent stall/mush and subsequent impact with the runway.Oct 25, 2004 · N62711 · Substantial damageNTSB ATL04LA177Accident · 2 fatalLimited investigationFinal reportPiper PA-23-250 · Lake Wales, FLThe pilot's inadequate preflight planning and preparation, and his inadequate visual lookout, which resulted in a collision with a television tower.Sep 11, 2004 · N962AB · Substantial damageNTSB MIA04FA100Accident · 2 fatalField investigationFinal reportPiper PA-23-250 · Baker, FLThe flight crew's inadvertent flight into thunderstorms resulting in the design limits of the airplane being exceeded, loss of aircraft control and subsequent in-flight breakup. A factor in the accident was the lack of required advisory by ATC about a radar…Jun 21, 2004 · N54134 · DestroyedNTSB 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 NYC04CA066Accident · No injuriesData collectionFinal reportPiper PA-23-250 · Grt. Barrington, MAThe pilot's misjudgment of the airplane's distance/speed and failure to obtain the proper touchdown point, which resulted in an overrun. A factor was the cross wind.Feb 9, 2004 · N6760A · Substantial damage