NTSB investigations: Piper PA-18, 2002

7 cases on aircraft the registry lists as Piper PA-18. 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-18, 2002 per year, 1964–2026: 477 cases
196447
196531
196621
196720
196818
196914
197023
197115
197215
197311
197419
197513
197611
197710
19788
19797
198010
19817
19829
19834
19845
19859
19867
19874
19883
19896
19909
19917
19923
19934
19946
19955
19965
19972
19984
19996
20006
20011
20027
20034
20042
20054
20062
20074
20084
20093
20102
20114
20124
20131
20142
20152
20162
20171
20181
20193
20204
20213
20224
20234
20252
20263

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\") = 2002
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7101802'))
  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 NYC03LA018Accident · No injuriesLimited investigationFinal reportPiper PA-18 · Turner, METhe pilot's misjudgment of distance which resulted in an overrun.Nov 9, 2002 · N223T · Substantial damageNTSB ANC02LA127Accident · No injuriesLimited investigationFinal reportPiper PA-18 · Ekwok, AKA partial separation of one propeller blade during cruise flight.Sep 30, 2002 · N723C · Substantial damageNTSB NYC02LA181Accident · No injuriesLimited investigationFinal reportPiper PA-18 · Belmar, NJThe improper use of an fuel additive which resulted in a power loss. A factor was the lack of suitable terrain.Sep 3, 2002 · N5428H · Substantial damageNTSB ANC02LA112Accident · No injuriesLimited investigationFinal reportPiper PA-18 · Anchorage, AKThe pilot's failure to attain the proper touchdown point on a remote airstrip, and his failure to perform a go-around that resulted in the airplane overrunning the end of the strip. Factors in the accident were the pilot's inadequate evaluation of a tailwind…Sep 2, 2002 · N6981B · Substantial damageNTSB ANC02LA103Accident · No injuriesLimited investigationFinal reportPiper PA-18 · Chickaloon, AKThe pilot's failure to maintain clearance from ground obstructions while taxiing. A factor contributing to the accident was excessive taxi speed.Aug 24, 2002 · N7489D · Substantial damageNTSB SEA02LA160Accident · No injuriesLimited investigationFinal reportPiper PA-18 · Newberg, ORA warped right brake disc resulting in a veer to the right during the landing roll, and the aircraft's subsequent collision with a fence. A contributing factor was the fence.Aug 19, 2002 · N1277A · Substantial damageNTSB CHI02LA065Accident · No injuriesLimited investigationFinal reportPiper PA-18 · Clear Lake, MNThe loss of engine power for undetermined reasons and the unsuitable terrain for the forced landing. Factors were the low altitude and the fences.Jan 20, 2002 · N7113K · Substantial damage