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

5 cases on aircraft whose registry engine model is Lycoming O&VO-360 series, where the first occurrence was “In flight encounter with weather”. 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

19832026
NTSB investigations: Lycoming O&VO-360 series, TX per year, 1983–2026: 5 cases
19832
19871
19891
19931

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\" = 'TX' 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\" = 240))
  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 FTW94LA048Accident · No injuriesLimited investigationFinal reportAero Commander 100-180 · El Paso, TXThe pilot's inadvertent flight into clear air turbulence.Dec 12, 1993 · N3718X · Substantial damageNTSB FTW89LA050Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-180 · Seminole, TXThe pilot's delay in updating his weather and diverting to an alternate destination, which resulted in fuel exhaustion from lack of fuel. Contributing factors were: the pilot's inadequate preflight planning/preparation at the en route stop, the weather…Feb 14, 1989 · N5258L · Substantial damageNTSB FTW88FA028Accident · 4 fatalField investigationFinal reportPiper PA-28-180 · Lancaster, TXThe pilot received a weather report indicating that IFR conditions prevailed. After takeoff the airplane traveled approximately 1/2 mile before it crashed. Pilot was not instrument rated and had very little total time. He did have three hours of night time…Nov 14, 1987 · N8980J · DestroyedNTSB FTW83FA254Accident · 5 fatalField investigationFinal reportPiper PA-28-180 · Haskell, TXThe acft crashed while on a flt in an area where thunderstorm warnings were in effect. There were no known witnesses to the actual crash, but 2 or 3 local residents heard an acft eng at about the estimated time of the accident. One resident about 1/4 mi from…May 30, 1983 · N5170S · DestroyedNTSB FTW83LA215Accident · 2 fatalLimited investigationFinal reportCessna 177B · Port Aransas, TXDuring a wx briefing, the non-instrument rated plt was told to expect no significant en route wx, but was advised of lower ceilings along the coastline, later that night. There were no records of en route wx briefings. When the acft was about 40 mi northwest…May 2, 1983 · N34581 · Destroyed