NTSB investigations: Piper PA-23-250, 2003

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
NTSB investigations: Piper PA-23-250, 2003 per year, 1964–2026: 858 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
198818
19898
19908
199115
19929
199312
199415
199517
199612
19978
19988
19996
20003
20013
20025
20037
20048
200512
200612
20073
20081
20091
20101
20112
20122
20136
20142
20151
20163
20174
20183
20196
20205
20211
20222
20235
20243
20252
20261

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\") = 2003
    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 NYC04LA047Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Buffalo, NYThe pilot's improper procedure with regard to the cabin heater, which resulted in the over temperature of the heater and subsequent fire.Dec 12, 2003 · N40259 · Substantial damageNTSB ATL04FA016Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Cordesville, SCThe pilot's failure to maintain adequate airspeed, which resulted in an inadvertent stall and subsequent uncontrolled descent into trees and the ground. A factor was physical impairment.Oct 13, 2003 · N63942 · Substantial damageNTSB MIA03LA145Accident · Minor injuriesLimited investigationFinal reportPiper PA-23-250 · Fort Pierce, FLThe pilot's failure to maintain directional control of the airplane during landing roll resulting in collision with trees after the airplane departed the runway.Jul 20, 2003 · N5224Y · Substantial damageNTSB NYC03LA097Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Buffalo, NYThe pilot's failure to maintain sufficient airspeed to prevent an inadvertent stall. Factors were the variable and gusty winds.May 5, 2003 · N448VP · Substantial damageNTSB MIA03LA061Accident · 4 fatalLimited investigationFinal reportPiper PA-23-250 · Miami, FLThe non instrument-rated pilot-in-command's improper inflight planning/decision, and continued VFR flight into instrument meteorological conditions, which resulted in a loss of control during descent, and impact with water.Feb 17, 2003 · N54835 · DestroyedNTSB LAX03FA069Accident · 4 fatalField investigationFinal reportPiper PA-23-250 · Flagstaff, AZthe pilot's failure to comply with his instrument clearance route instruction and to maintain his assigned altitude. A factor in the accident was the poor quality of radio communications due to the severance of underground fiber optic voice and data lines for…Jan 8, 2003 · N135LA · DestroyedNTSB CHI03FA047Accident · No injuriesField investigationFinal reportPiper PA-23-250 · Barrington Hill, ILThe pilot's improper fuel management, which resulted in fuel starvation. An inadequate preflight inspection and the trees encountered during the forced landing were contributing factors.Jan 7, 2003 · N74AA · Substantial damage