NTSB investigations: Lycoming 0-320 series, MN

8 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the first occurrence was “Hard landing”. 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, MN per year, 1982–2026: 8 cases
19821
19872
19951
20031
20052
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\" = '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\" = 200))
  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 CHI07CA006Accident · No injuriesData collectionFinal reportCessna 172N · Grand Rapids, MNThe student pilot's misjudged landing flare and improper recovery from the bounced landing which led to the failure of the nose landing gear. The overload failure of the nose landing gear was a factor.Oct 9, 2006 · N739XK · Substantial damageNTSB CHI05CA174Accident · No injuriesData collectionFinal reportPiper PA-28-151 · Willmar, MNThe pilot's improper flare which resulted in a hard landing.Jun 26, 2005 · N9027F · Substantial damageNTSB CHI05CA152Accident · No injuriesData collectionFinal reportCessna 172M · Rochester, MNThe pilot flared improperly and failed to recover from a bounced landing.Jun 18, 2005 · N73328 · Substantial damageNTSB CHI03LA137Accident · Minor injuriesLimited investigationFinal reportLongjev RV-6A · Backus, MNThe pilot's inadequate flare and recovery from a bounced landing.May 27, 2003 · N72159 · Substantial damageNTSB CHI95FA307Accident · 1 fatalField investigationFinal reportCessna 172M · Orr, MNthe pilot misjudged the landing flare. Factors associated with the accident were the visual illusion caused by the glassy smooth water condition and the forward center of gravity.Sep 3, 1995 · N828MB · DestroyedNTSB CHI87LA224Accident · No injuriesLimited investigationFinal reportCessna 172L · Lakeville, MNAircraft landed hard, nose wheel first, and collapsed the nose landing gear tire. PIC was concerned about a sharp knocking noise in the rear of the aircraft that he heard after liftoff. The reason for the noise was not determined. He acknowledged that he…Sep 26, 1987 · N3599F · Substantial damageNTSB CHI87LA178Accident · No injuriesLimited investigationFinal reportRobinson 22 · Minnetonka, MNWhile attempting to land on a flat spot on top of a hill the tail rotor hit the ground and the tail boom broke off. One witness reports that when the helicopter touched down it bounced up about 10 feet. No mechanical malfunctions were reported.Jul 29, 1987 · N8383F · Substantial damageNTSB CHI82DA296Accident · No injuriesFinal reportBeech B19 · Le Suer, MNThe aircraft landed short of the runway collapsing the nose gear and damaging the propeller.Aug 5, 1982 · N9309S · Substantial damage