NTSB investigations: Lycoming 0-320 series, MN

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

19832026
NTSB investigations: Lycoming 0-320 series, MN per year, 1983–2026: 5 cases
19831
19941
19981
20011
20041

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\" = 'MN' 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 CHI05CA034Accident · No injuriesData collectionFinal reportCessna 172N · Lakeville, MNThe pilot misjudged his distance and speed which resulted in an overrun.. Factors were the wet runway, the grass and the berm.Nov 20, 2004 · N737CR · Substantial damageNTSB CHI02LA031Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · New Ulm, MNThe student and flight instructor not using all of the available runway, the inadequate supervision by the flight instructor and the unsuccessful remedial action by the flight instructor. The student not attaining the proper touchdown point and the plowed…Nov 6, 2001 · N523PU · Substantial damageNTSB CHI98LA315Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Redwood Falls, MNthe pilot's not following proper short field landing procedures.Aug 15, 1998 · N4576F · Substantial damageNTSB CHI94LA305Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Jackson, MNthe pilot's selection of unsuitable terrain for takeoff and his delay in aborting the takeoff. Factors in the accident were the soft terrain and the ditch.Aug 28, 1994 · N1197X · Substantial damageNTSB CHI83LA409Accident · No injuriesLimited investigationFinal reportCessna 172M · Grand Marais, MNThe plt took off from the departure point after an unexpected 1/2 hr delay. By the time he arrived at his destination, it was dark. No rwy lighting sys was installed, so someone at the arpt drove a car to rwy 27 to light up the approach end with the head…Sep 3, 1983 · N1857V · Substantial damage