Fatal NTSB investigations: Lycoming IO-360-A1B6D

6 cases on aircraft whose registry engine model is Lycoming IO-360-A1B6D, where the first occurrence was “In flight collision with object”. 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

19862026
Fatal NTSB investigations: Lycoming IO-360-A1B6D per year, 1986–2026: 6 cases
19861
19881
19941
20001
20051
20071

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 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 ('41593')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 220))
  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 LAX07LA122Accident · 1 fatalLimited investigationFinal reportScottish Bulldog 120 · So Lake Tahoe, CAThe pilot's failure to maintain clearance from objects and the mountainous terrain.Apr 8, 2007 · N706X · Substantial damageNTSB LAX06LA058Accident · 1 fatalLimited investigationFinal reportCessna 177RG · Dixon, CAthe pilot's intentional flight at low altitude and failure to maintain obstacle clearance with a high tension static line. The glare from the setting sun was a factor.Dec 15, 2005 · N8040G · Substantial damageNTSB MIA00FA126Accident · 1 fatalField investigationFinal reportCessna 177RG · Chipley, FLThe failure of the pilot to maintain runway alignment during the initial climb from the grass airstrip. Also, the excessive pull-up by the pilot and inadvertent stall. Findings in the investigation were 1) in-flight collision with the tops of trees and 2) the…Apr 3, 2000 · N1997Q · Substantial damageNTSB LAX94FA318Accident · 4 fatalField investigationFinal reportCessna 177RG · So. Lake Tahoe, CAThe pilot's decision to take off from a high density altitude airport at an over allowable gross weight condition. Factors in the accident were the high density altitude, down drafts, and the pilot's lack of familiarity operting from high density altitude…Aug 12, 1994 · N217AF · DestroyedNTSB LAX88FA272Accident · 3 fatalField investigationFinal reportCessna 177RG · Cedar Grove, CAPilots decision to attempt a flight through a mountainous area at an altitude insufficient to ensure terrain clearance.Jul 30, 1988 · N52504 · DestroyedNTSB CHI86FA068Accident · 1 fatalField investigationFinal reportCessna 177RG · Valley View, ILThe plt was conducting a low pass, 40 ft AGL, on a river and struck a power line crossing his flt path. The strike caused loss of control and the acft impacted on the frozen surface of the river.Jan 19, 1986 · N52949 · Destroyed