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

6 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

19822026
NTSB investigations: Lycoming O&VO-360 series, 1983 per year, 1982–2026: 200 cases
19829
19836
19849
198512
19867
198711
19888
19898
19908
19912
19929
19939
19947
19957
19962
19974
19989
19993
20007
20019
20028
20039
20049
200510
20069
20079

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 year(c.\"eventDate\") = 1983
    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 ATL84LA019Accident · No injuriesLimited investigationFinal reportBeech B-23 · Topping, VAThe acft overran the departure end of the rwy and collided with a ditch during landing. The weather was VMC. According to the pilot 2 go-arounds had been made because the acft was high. On the 3rd approach a touchdown was made about 1/2 way down the 2500 ft…Oct 14, 1983 · N5234M · Substantial damageNTSB MKC83LA144Accident · No injuriesLimited investigationFinal reportBeech C-23 · Osage Beach, MOThe acft ran off the side of the runway and continued to overrun the departure end of the runway where collision with a ditch occurred. There was evidence that the brakes were used but were not effective in stopping the acft. An FAA inspector inspected the…Jul 2, 1983 · N9346S · Substantial damageNTSB DEN83LA107Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Erie, CODuring a second touch & go the acft ran off the side of the rwy. The plt last flew on 10/4/82 for about a 1 hr flt.May 2, 1983 · N9088J · Substantial damageNTSB FTW83LA161Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Guthrie, OKThe pilot said he was waiting for an acft to clear the rwy. As he started to turn downfield for takeoff he pushed the throttle in, advancing the power instead of retarding it. The aircraft crossed the runway at an angle, became airborne and hit a tree. The…Mar 18, 1983 · N6501J · Substantial damageNTSB MIA83LA068Accident · No injuriesLimited investigationFinal reportPiper PA-28-180 · Palmetto, FLAccording to the pilot he lost directional control of the aircraft during the landing roll. The aircraft veered to the left and went off the runway colliding with a drainage ditch and fence. No mechanical failure of malfunctions were reported.Jan 29, 1983 · N8923J · Substantial damageNTSB LAX83FVM07Accident · No injuriesFinal reportPitts S1S · San Jose, CAThe pilot made a rolling takeoff and apparently locked the tailwheel while turning. During later landing the aircraft became uncontrollable and ground-looped off the runway into mud where it flipped over. The tailwheel was locked out of detent and was unable…Jan 16, 1983 · N15HR · Substantial damage