NTSB investigations: Lycoming 0-320 series, IL

7 cases on aircraft whose registry engine model is Lycoming 0-320 series, 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

19822026
NTSB investigations: Lycoming 0-320 series, IL per year, 1982–2026: 7 cases
19821
19861
19891
19911
19971
20011
20021

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.\"eventStateOrRegion\" = 'IL' AND c.\"eventCountry\" = 'USA'
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41508')
      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 CHI03LA040Accident · No injuriesLimited investigationFinal reportCessna 172M · Moline, ILThe pilot's failure to maintain altitude clearance during a base to final turn on approach. Contributing factors to the accident were the night conditions and the trees.Dec 6, 2002 · N80213 · Substantial damageNTSB CHI02LA007Accident · 1 fatalLimited investigationFinal reportWoodrow Stolp-Adams Starduster SA-100 · Millstadt, ILThe pilot not maintaining altitude/clearance from the tree line. Factors to the accident were the pilot attempting the low altitude flight/maneuver and the presence of the tree line.Oct 21, 2001 · N64HW · DestroyedNTSB CHI97LA227Accident · Minor injuriesLimited investigationFinal reportKearns RV-6 · Harrisburg, ILThe pilot's failure to maintain adequate clearance. A factor was the marked transmission wire.Jul 27, 1997 · N35K · Substantial damageNTSB CHI91DEE06Accident · No injuriesFinal reportRobinson R22B · Mineral, ILFailure of the pilot to maintain clearance from the power line.Jun 5, 1991 · N91MG · Substantial damageNTSB CHI90LA022Accident · No injuriesLimited investigationFinal reportCessna 172 · Lansing, ILThe pilot's inadvertent selection of unsuitable terrain (taxiway/construction area). The steel marker poles contributed to the aircraft damage.Oct 29, 1989 · N1316U · Substantial damageNTSB CHI87LA019Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Bethalto, ILThe pilot attempted an ILS approach into an airfield (runway 29) that was reporting a zero foot obscured ceiling with 1/16 mile visibiltiy and fog. He stated that he became confused during the last portion of the approach and was beginning a missed approach…Nov 17, 1986 · N1631E · DestroyedNTSB CHI83LA003Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Seneca, ILWhile landing on a 2300 ft runway, the plane touched down about 1000 to 1200 ft beyond the approach end. The pilot felt that there was insufficient room to stop safely, so she initiated a go-around. The pilot was unable to attain enough altitude to clear…Oct 3, 1982 · N5308D · Substantial damage