NTSB investigations: Lycoming 0-320 series, IA

5 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, IA per year, 1982–2026: 5 cases
19821
19861
19911
19991
20051

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\" = 'IA' 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 CHI05CA224Accident · Minor injuriesData collectionFinal reportPiper PA-28-140 · Mount Ayr, IAThe pilot's selection of a wrong runway, and the misjudged distance/speed which resulted in an overrun. Contributing factors were the tailwind, and the ditch.Sep 21, 2005 · N6266W · Substantial damageNTSB CHI99LA237Accident · No injuriesLimited investigationFinal reportCessna 172L · Montezuma, IAthe pilot inadvertently landed on the wrong runway and exceeded the proper touchdown point on the runway. Factors associated with the accident were the gusty tailwind, the fence, and the ditch.Jul 14, 1999 · N19752 · Substantial damageNTSB CHI91LA010Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Manning, IAAirspeed was not attained and aborted takeoff was delayed by the pilot. Factors related to the accident were: over confidence in aircraft's ability to takeoff on the short, grass runway and a dirt embankment on the departure end of the strip.Jun 11, 1991 · N44300 · Substantial damageNTSB MKC86LA158Accident · No injuriesLimited investigationFinal reportGrumman AA-5A · Audubon, IAThe pilot stated that the engine was developing full power during the brake release and takeoff roll but that the aircraft would not accelerate to lift-off speed as fast as expected. Upon reaching 70 m.p.h.(61 KTS.), and after a takeoff roll of 2,000 feet,…Jul 27, 1986 · N9835U · Substantial damageNTSB MKC82DA103Accident · No injuriesFinal reportCessna 172N · Marion, IAThe pilot reported that he took off, stayed in the traffic pattern, and made a normal approach with one notch of flaps at about 75 mph. He stated that on final approach, the wind shifted from 350 to almost 180 degrees. He landed long and was unable to stop on…Jun 13, 1982 · N5158E · Substantial damage