NTSB investigations: Lycoming 0-235 series, OR

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

19852026
NTSB investigations: Lycoming 0-235 series, OR per year, 1985–2026: 7 cases
19851
19861
19871
19951
19961
20001
20011

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\" = 'OR' 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 ('41505')
      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 SEA02FA005Accident · 2 fatalField investigationFinal reportPiper PA-18 · Sandy, ORThe pilot's failure to maintain clearance from the trees while attempting to land in a field after entering an area of instrument meteorological conditions. Factors include low ceilings, rain, fog, strong winds, mountainous/hilly terrain, the pilot's…Oct 16, 2001 · N7502K · Substantial damageNTSB SEA01FA015Accident · 2 fatalField investigationFinal reportCessna 152 · Corvallis, ORThe pilot's failure to maintain clearance from the terrain. Factors include a dark night, densely forested, hilly terrain near the planned route of flight, and low ceilings in the area of the accident.Nov 6, 2000 · N53301 · DestroyedNTSB SEA96LA111Accident · Minor injuriesLimited investigationFinal reportGrumman American AA-1B · Coquille, ORthe pilot's inadequate evaluation of wind conditions, and his subsequent failure to initiate a go-around in a timely manner, which resulted in his inability to maintain clearance with trees during the go-around. Factors relating to the accident included a…Jun 5, 1996 · N9875L · Substantial damageNTSB SEA95LA053Accident · 2 fatalLimited investigationFinal reportBruce Tifft Varieze · Tiller, ORThe pilot's failure to maintain clearance from trees.Feb 18, 1995 · N115EZ · Substantial damageNTSB SEA88LA025Accident · No injuriesLimited investigationFinal reportPiper PA-22-108 · Cornelius, ORThe pilot was attempting to land in a field near a farmhouse. On final approach the pilot cleared large power lines, but had not seen small power lines ahead and below the aircraft. The aircraft struck the power lines in flight with the nose gear. The…Nov 27, 1987 · N4523Z · Substantial damageNTSB SEA86LA229Accident · Minor injuriesLimited investigationFinal reportBellanca 7ECA · Tygh Valley, ORAn uncertificated plt was flying the acft at a low altitude when the acft struck wires. Due to the damage to the acft a forced landing was made onto a bark dump where additional damage occurred to the acft.Aug 30, 1986 · N5159T · Substantial damageNTSB SEA85LA216Accident · No injuriesLimited investigationFinal reportCessna 152 · Independence, ORThe plt descended to a low alt over a river to look for birds. While over the river the plt spotted pwr lines at an alt of aprx 75 ft AGL. An attempt was made to fly under the lines, but the tail contacted the wires severing aprx 6 inches off the top portion…Aug 18, 1985 · N49282 · Substantial damage