Fatal NTSB investigations: Lycoming 0-540 series, 2002

7 cases on aircraft whose registry engine model is Lycoming 0-540 series. 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
Fatal NTSB investigations: Lycoming 0-540 series, 2002 per year, 1964–2026: 406 cases
19645
19654
19662
19677
19687
19696
197010
19713
19725
19732
19744
19753
19764
19777
19788
19798
198011
19818
198212
19838
19847
198512
19865
19877
19886
19899
19905
19917
19927
19936
19948
19957
19965
19974
19988
19991
20006
20019
20027
200310
200410
20058
200611
20077
20087
200910
20108
201111
20125
20132
20143
20154
20162
20176
20185
20195
20206
202110
20228
20238
20241
20254
20265

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.\"highestInjuryLevel\" = 'Fatal'
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41532'))
  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 LAX03FA051Accident · 2 fatalField investigationFinal reportPiper PA-24-250 · Anaheim Hills, CAthe pilot's encounter with forecast severe turbulence during an inadvertent penetration of an intense weather cell, which resulted in the pilot exceeding the design structural limits of the airplane. A factor in the accident was the pilot's inadequate…Dec 16, 2002 · N6268P · DestroyedNTSB IAD03FA019Accident · 2 fatalField investigationFinal reportPiper PA-32RT-300 · Bastian, VAThe pilot's failure to maintain an adequate altitude above terrain. Factors in the accident were the dark night conditions and the low cloud ceiling.Nov 27, 2002 · N31554 · Substantial damageNTSB SEA02FA175Accident · 3 fatalField investigationFinal reportCessna TR182 · Twin Falls, IDThe pilot's failure to maintain runway alignment and his failure to execute a timely go-around maneuver resutling in the aircraft's impacting a parked fuel truck well clear of the runway safety area. Contributing factors were the strong crosswind/gusty wind…Sep 15, 2002 · N738GX · DestroyedNTSB ANC02FA108Accident · 2 fatalField investigationFinal reportRobinson R-44 · Ketchikan, AKThe pilot's failure to maintain control of the helicopter in-flight due to spatial disorientation, which resulted in an uncontrolled descent and impact with the surface of a lake. Factors contributing to the accident were the high terrain surrounding the…Aug 29, 2002 · N7189T · Substantial damageNTSB CHI02LA121Accident · 2 fatalLimited investigationFinal reportYoder GP-4 · Mount Pleasant, MIThe inadvertent stall/spin by the pilot-in-command.May 5, 2002 · N59JY · DestroyedNTSB FTW02FA118Accident · 2 fatalField investigationFinal reportCessna T182 · Amarillo, TXThe pilot's failure to maintain clearance with the power plant while maneuvering, and his intentional flight into adverse weather conditions. Contributing factors were low clouds, fog, the power plant, and low altitude flight.Apr 12, 2002 · N983HH · DestroyedNTSB ANC02FA025Accident · 1 fatalField investigationFinal reportPiper PA-28-235 · Manokotak, AKThe pilot's continued VFR flight into instrument meteorological conditions, and subsequent collision with terrain during cruise flight. Factors in the accident were low ceilings, snow, and mountainous snow-covered terrain.Mar 23, 2002 · N1220R · Substantial damage