NTSB investigations: Lycoming 0-320 series, OH

14 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the first occurrence was “Overrun”. 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, OH per year, 1982–2026: 14 cases
19821
19842
19891
19911
19921
19931
19942
19991
20031
20051
20061
20071

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\" = 'OH' 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\" = 340))
  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 CHI07CA134Accident · Minor injuriesData collectionFinal reportCessna 172I · Shelby, OHThe pilot's failure to properly achieve the correct touch down point which resulted in a runway over run and subsequent nose over into a ditch. Other factors were the pilot's improper decision to land with a tailwind and the ditch.May 9, 2007 · N8469L · Substantial damageNTSB CHI06CA182Accident · No injuriesData collectionFinal reportCessna 172L · Waterford, OHThe pilot's selection of unsuitable terrain for landing. The runway's downhill slope, the wet grass, the fence, and the embankment were factors.Jul 8, 2006 · N7805G · Substantial damageNTSB NYC05CA073Accident · No injuriesData collectionFinal reportCessna 172N · Wellington, OHThe pilot's failure to obtain the proper touchdown point, and his failure to initiate a go-around, which resulted in an overrun during landing. A factor in the accident was the tail wind.Apr 17, 2005 · N1086F · Substantial damageNTSB NYC04CA028Accident · No injuriesData collectionFinal reportCessna 172K · Kilbourne, OHThe pilot's failure to obtain the proper touchdown point which resulted in an overrun and subsequent nose over.Nov 8, 2003 · N78203 · Substantial damageNTSB NYC99LA137Accident · No injuriesLimited investigationFinal reportCessna 172 · Ravenna, OHThe pilot-in-command's failure to maintain aircraft control during landing.Jun 11, 1999 · N62953 · Substantial damageNTSB NYC94LA102Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · New Philadelphi, OHThe pilot's inadequate decision and his delay in aborting the takeoff, which resulted in an overrun of the runway and collision with obstaclesJun 22, 1994 · N5543F · Substantial damageNTSB NYC94LA060Accident · No injuriesLimited investigationFinal reportCessna 172K · Dayton, OHthe pilot's failure to maintain directional control which resulted in a runway overrun. Factors are the pilot's improper recovery from a bounced landing, and his lack of experience.Mar 10, 1994 · N79136 · Substantial damageNTSB BFO93LA182Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Painesville, OHThe pilot's attempt to land with excessive airspeed, his improper use of the brakes, and his delay in performing remedial action.Sep 19, 1993 · N6294J · Substantial damageNTSB NYC92LA084Accident · No injuriesLimited investigationFinal reportCessna 172N · New Madison, OHThe pilot's failure to attain a proper touchdown point. Contributing to the accident was the pilot inadequately planned his approach and his failure to perform a go-around.Apr 23, 1992 · N733XP · Substantial damageNTSB NYC91LA210Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Sandusky, OHThe pilot initiated an emergency landing when the engine RPM went to zero due to a broken tachometer cable. He did not attain the proper touchdown point and overran the end of the runway.Aug 16, 1991 · N64834 · Substantial damageNTSB CHI89LA121Accident · No injuriesLimited investigationFinal reportCessna C172M · Wadsworth, OHPilot's poor planning/decision making during the approach and landing phase of flight, which resulted in a long landing and runway overrun.Jun 26, 1989 · N19950 · Substantial damageNTSB CHI85LA008Accident · No injuriesLimited investigationFinal reportCessna 172N · Youngstown, OHAfter returning to the arpt, the plt entered the pattern for a x-wind landing. He made 3 go-arounds while attempting to land. On the 4th apch, the acft touched down, then became airborne again. The plt decided 'to much time had passed to make another…Oct 6, 1984 · N738CY · Substantial damageNTSB CHI84LA382Accident · No injuriesLimited investigationFinal reportGrumman AA-5 · New Carlisle, OHThe acft collided with trees after overrunning a 2000 ft wet sod airstrip. The plt reported that braking action was poorthe acft went into an evergreen tree nursery before stopping.Sep 5, 1984 · N9596L · Substantial damageNTSB CHI82DA292Accident · No injuriesFinal reportThorp T-18 · Geneva, OHDuring landing, the aircraft touched down about 1/3 of the way down the runway. The pilot reported that after touchdown, he applied the brakes intermittently, but there was little effect on the dry, hard, grassy surface. When it became apparent that he would…Aug 3, 1982 · N693RB · Substantial damage