NTSB investigations: Piper PA-30, 2001

6 cases on aircraft the registry lists as Piper PA-30. 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-30, 2001 per year, 1964–2026: 835 cases
196435
196537
196652
196756
196833
196943
197036
197133
197240
197333
197432
197517
197617
197718
197827
197917
198019
198112
198212
19838
198415
19858
19869
19879
19883
19895
199012
19917
19927
19939
19942
19954
19966
19973
19988
19995
20004
20016
20029
20034
20048
20054
20064
200710
20087
20098
20105
20117
20125
20135
20145
20153
20163
20172
20183
20193
20207
20218
20227
20236
20243
20254
20266

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 ('7103002'))
  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 FTW02LA018Accident · Serious injuriesLimited investigationFinal reportPiper PA-30 · Ozona, TXThe loss of engine power due to fuel exhaustion resulting from the pilot's failure to refuel the airplane. Contributing factors were the lack of suitable terrain for the forced landing and the dark night conditions.Oct 20, 2001 · N8642Y · Substantial damageNTSB MIA02LA003Accident · Minor injuriesLimited investigationFinal reportPiper PA-30B-160 · Clarksville, TNThe failure of the CFI/check pilot to insure Vmc was maintained during a go-around following a simulated failed engine approach, resulting in an in-flight loss of control, uncontrolled descent, and collision with the terrain. A factor in the accident was the…Oct 3, 2001 · N8402Y · Substantial damageNTSB SEA01FA175Accident · 1 fatalField investigationFinal reportPiper PA-30 · McCall, IDThe pilot's failure to maintain adequate airspeed following a loss of power on the left engine, resulting in loss of aircraft control. Factors included a loss of power on the left engine for undetermined reasons, and the pilot's failure to properly configure…Sep 29, 2001 · N954S · Substantial damageNTSB CHI01LA221Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Bowman, NDAltitude/clearance not obtained by the pilot during the initial climb. Factors relating to the accident were attaining the proper climb rate not being possible, the microburst, the dark night, and the tree.Jul 21, 2001 · N7382Y · Substantial damageNTSB CHI01LA096Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Appleton, WIThe misjudged glidepath and the intentional engine shutdown by the pilot. Factors were the false indication of the landing gear down light and the approach light.Feb 27, 2001 · N8196Y · Substantial damageNTSB MIA01FA072Accident · 1 fatalField investigationFinal reportPiper PA-30 · Ponce, PRThe pilot's decision to attempt flight with known deficiencies in the airplanes right engine, his failure to feather the right propeller after the engine failed , his failure to retract the landing gear following the engine failure, and his failure to…Feb 8, 2001 · N181MM · Destroyed