NTSB investigations: Lycoming 0-320 series, GA

7 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

19832026
NTSB investigations: Lycoming 0-320 series, GA per year, 1983–2026: 7 cases
19831
19841
19871
19921
19971
20031
20061

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\" = 'GA' 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 ATL06CA065Accident · No injuriesData collectionFinal reportCessna 172 M · Griffin, GAThe pilot's failure to achieve the proper touchdown point, which resulted in an overrun of the runway, collision with an embankment, and subsequent nose over.Apr 16, 2006 · N9970V · Substantial damageNTSB ATL03LA067Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Savannah, GAThe pilot misjudged the landing distance, landed with excessive airspeed, did not attempt a go-around resulting in the airplane going off the overrun, and colliding with trees.Mar 23, 2003 · N13591 · Substantial damageNTSB ATL97LA076Accident · No injuriesLimited investigationFinal reportCessna 172M · Perry, GAthe pilot misjudged his distance/airspeed during the approach to land, and touched down long on the runway.May 28, 1997 · N13375 · Substantial damageNTSB ATL92LA037Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Griffin, GAThe excessive speed used by the pilot to land on the short private airstrip. A factor was unfavorable wind.Jan 12, 1992 · N6101D · Substantial damageNTSB ATL88LA033Accident · No injuriesLimited investigationFinal reportCessna 172K · Cumming, GAThe student plt rptd that the airplane contacted the rwy and bounced twice during the ldg flare. Once he got the airplane on the rwy, he realized that the airspeed was 'too high' for the rwy remaining and attempted to ground loop the airplane to stop it. The…Nov 6, 1987 · N7140G · Substantial damageNTSB ATL84LA194Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Augusta, GAThe student pilot stated that the acft touched down at about midfield at aprx 90 mph. He was unable to stop the acft & it struck a chain link fence near the end of the rwy. The student had only 2 hrs of total flt time in this make & model of acft.Jun 6, 1984 · N44372 · Substantial damageNTSB ATL83LA138Accident · No injuriesLimited investigationFinal reportPiper PA-28 · Stone Mountain, GAThe aircraft overran the departure end of the runway and collided with an embankment during an aborted takeoff. The student pilot did not file a flight plan or check the weather for this flight. The weather was VMC but the pilot startedthe takeoff down wind.…Mar 19, 1983 · N8593N · Destroyed