NTSB investigations: Lycoming O&VO-360 series, UT

8 cases on aircraft whose registry engine model is Lycoming O&VO-360 series, where the first occurrence was “Loss of control - on ground/water”. 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
NTSB investigations: Lycoming O&VO-360 series, UT per year, 1986–2026: 8 cases
19861
19911
19941
19981
20011
20021
20032

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\" = 'UT' 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 ('41514')
      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\" = 260))
  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 DEN03LA141Accident · No injuriesLimited investigationFinal reportRichardson RV-6 · Provo, UTthe pilot's failure to maintain aircraft control. Contributing factors were the resulting ground loop and the collapsed right main landing gear.Aug 7, 2003 · N846E · Substantial damageNTSB DEN03LA046Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-180 · Richfield, UTthe pilot's failure to maintain aircraft control during landing roll resulting in a ground loop/swerve and subsequent nose over. A contributing factor was the gusty wind conditions.Mar 7, 2003 · N8205W · Substantial damageNTSB DEN02LA022Accident · No injuriesLimited investigationFinal reportCessna 175 · St. George, UTThe student pilot's failure to maintain aircraft directional control during take off roll.Jan 20, 2002 · N7693M · Substantial damageNTSB DEN01LA038Accident · No injuriesLimited investigationFinal reportAviat A-1A · Eden, UTthe pilot's failure to maintain aircraft control during a landing attempt. A contributing factor was his failure to check the snow conditions in the field before the flight.Jan 4, 2001 · N26HV · Substantial damageNTSB FTW98LA370Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Hurricane, UTThe pilot inadvertently inducing a porpoise oscillation, and his failure to maintain directional control. A factor was the excessive landing airspeed.Aug 22, 1998 · N4760L · Substantial damageNTSB SEA94LA126Accident · No injuriesLimited investigationFinal reportChristen Industries Husky · Ogden, UTThe pilot's inadequate compensation for wind condiitons. The wind gusts were a factor.May 21, 1994 · N103TB · Substantial damageNTSB SEA91LA113Accident · No injuriesLimited investigationFinal reportBeech B23 · Spanish Fork, UTThe pilot did not adequately recover from a bounced landing. Factors to the accident were: a poorly planned approach, and the pilot's lack of total flight experience.May 19, 1991 · N4019T · Substantial damageNTSB DEN86LA212Accident · No injuriesLimited investigationFinal reportCessna 170B · Ogden, UTThe plt reports that he was making a t&g on the 5400 by 200, asphalt rwy. The wind was light. The plt said he had reconfigured the acft for takeoff and was about to advance the throttle when the acft swerved to the right and ran off the rwy. After leaving the…Jul 27, 1986 · N3056A · Substantial damage