Fatal NTSB investigations: Lycoming 0-540 series, 2010

8 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, 2010 per year, 1964–2026: 407 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
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\") = 2010
    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 ERA10LA348Accident · 1 fatalLimited investigationFinal reportRobinson Helicopter R44 · Marion, KYThe pilot's failure to maintain clearance from power lines during an aerial application flight.Jul 5, 2010 · N857PM · Substantial damageNTSB WPR10FA239Accident · 1 fatalField investigationFinal reportPiper PA-24-250 · Redmond, ORThe pilot's failure to maintain airspeed, which resulted in a stall and collision with terrain.May 14, 2010 · N6967P · Substantial damageNTSB WPR10FA234Accident · 2 fatalField investigationFinal reportPiper PA-28-235 · Livermore, CAThe pilot's continued visual flight into instrument meteorological conditions, which resulted in a collision with obstacles and terrain.May 9, 2010 · N56626 · Substantial damageNTSB CEN10LA216Accident · 1 fatalLimited investigationFinal reportPiper PA-24-250 · Madison, INThe pilot’s failure to maintain control of the airplane. Contributing to the accident was the pilot’s decision to conduct the flight with known physiological impairment and his use of unapproved sedating medication, both of which likely impaired his ability…Apr 19, 2010 · N5425P · DestroyedNTSB ERA10FA232Accident · 1 fatalField investigationFinal reportMaule M5-235C · Zellwood, FLThe pilot's failure to maintain airspeed while maneuvering after takeoff, which resulted in an aerodynamic stall, loss of aircraft control, and collision with trees.Apr 18, 2010 · N9196E · Substantial damageNTSB CEN10FA164Accident · 1 fatalField investigationFinal reportMaule M-5-235C · Lewisville, TXThe pilot did not retract the landing gear before a water landing. Contributing to the accident was the pilot did not use a checklist.Mar 18, 2010 · N56489 · Substantial damageNTSB CEN10FA115Accident · 3 fatalField investigationFinal reportPiper PA-25-235 · Boulder, COThe failure of both pilots to see and avoid the other resulting in a midair collision. Contributing to the accident was the lack of perceived visual relative motion of the Piper and the Cirrus to the pilot of each airplane, the terrain background, and the…Feb 6, 2010 · N8718L · 3 aircraft · Substantial damageNTSB CEN10FA108Accident · 2 fatalField investigationFinal reportSmith Aerostar 601P · Sugar Grove, ILThe pilot's spatial disorientation and subsequent failure to maintain airplane control.Jan 24, 2010 · N222AQ · Destroyed