NTSB investigations: Piper PA-24-250, 2001

13 cases on aircraft the registry lists as Piper PA-24-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-24-250, 2001 per year, 1964–2026: 1,523 cases
1964152
1965130
1966124
1967137
196863
196960
197052
197155
197254
197343
197441
197536
197634
197743
197827
197924
198025
198116
198219
198313
198411
198519
19868
198716
198815
198914
199014
199115
19924
199312
199415
19958
199613
199714
19983
199913
20007
200113
200210
20036
20048
20056
20068
20078
20085
20095
20104
20119
20128
20135
20148
20155
20166
20171
201810
20197
20204
20214
20228
20236
20247
20255
20268

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\") = 2001
    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'))
  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 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 LAX02LA036Accident · Minor injuriesLimited investigationFinal reportPiper PA-24-250 · Prescott, AZFuel starvation on final approach due to the pilot's fuel mismanagement, and his inattentiveness in following established prelanding procedures.Dec 2, 2001 · N7213P · Substantial damageNTSB MIA02LA025Accident · Serious injuriesLimited investigationFinal reportPiper PA-24-250 · Evans, GAThe pilot's improper fuel management and failure switch to the other fuel tank which had fuel available prior to the engine ceasing to operate, which resulted in fuel starvation and damage to the airplane during an off-airport landing.Nov 20, 2001 · N6688P · Substantial damageNTSB MIA02LA017Accident · Minor injuriesLimited investigationFinal reportPiper PA-24-250 · Peachtree City, GAThe pilot’s attempted operation of the aircraft with known deficiencies in the engine ignition system resulting in failure of the engine due to ignition system failure and damage to the airplane during the subsequent forced landing.Nov 16, 2001 · N8183P · Substantial damageNTSB SEA01LA148Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Thompson Falls, MTThe pilot's inadequate compensation in gusting wind conditions during the landing flare. A tree was a factor.Aug 9, 2001 · N699WL · Substantial damageNTSB SEA01LA129Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Fragaria, WAThe pilot's failure to maintain adequate directional control. Contributing factors were the embankment and the deer.Jul 7, 2001 · N7994P · Substantial damageNTSB FTW01LA157Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Uvalde, TXThe pilot's failure to verify the landing gear was down and locked, which resulted in a wheels up landing and subsequent ground fire.Jun 28, 2001 · N6474P · Substantial damageNTSB CHI01FA146Accident · 3 fatalField investigationFinal reportPiper PA-24-250 · Osage Beach, MOAircraft control not being maintained by the pilot during the forced landing and inadequate preflight inspection performed by the pilot. Contributing factors to the accident were the fuel system contamination that resulted in the loss of engine power, the…May 28, 2001 · N7331P · Substantial damageNTSB LAX01LA148Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Chino, CAThe pilot's failure to extend the landing gear. A factor was the pilot's failure to use the landing checklist.Apr 9, 2001 · N6240P · Substantial damageNTSB DEN01LA083Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Telluride, COthe pilot's failure to maintain control of the airplane during initial climb. Factors include the gusty wind and high density altitude conditions.Apr 8, 2001 · N7736P · Substantial damageNTSB IAD01FA039Accident · 1 fatalField investigationFinal reportPiper PA-24-250 · Paris, VApilot's continued visual flight into instrument meteorological conditions.Mar 31, 2001 · N5841P · Substantial damageNTSB LAX01LA097Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Petaluma, CAFailure of non-airframe and powerplant mechanic/certificated owners to properly install a new mixture cable that became entangled in the nose landing gear during its extension for landing, resulting in a loss of engine power.Feb 14, 2001 · N8286P · Substantial damageNTSB MIA01LA058Accident · Minor injuriesLimited investigationFinal reportPiper PA-24-250 · Pittsview, ALThe failure of the pilot to conduct proper preflight planning, resulting in loss of engine power while in cruise flight due to fuel exhaustion, and the subsequent emergency descent and landing to an open field.Jan 9, 2001 · N5887P · Substantial damage