NTSB investigations: Lycoming 0-320 series, TN

6 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the first occurrence was “In flight collision with object”. 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

19842026
NTSB investigations: Lycoming 0-320 series, TN per year, 1984–2026: 6 cases
19841
19891
19901
19911
19981
19991

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\" = 'TN' 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\" = 220))
  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 MIA99LA148Accident · No injuriesLimited investigationFinal reportCessna 172N · Eagleville, TNThe dual's student failure to maintain adequate altitude/clearance from the wire during takeoff/initial climb. Also causal was the certified flight instructor's inadequate supervision.May 4, 1999 · N739EW · Substantial damageNTSB MIA98LA113Accident · No injuriesLimited investigationFinal reportCessna 172M · Kingsport, TNThe dual student's failure to maintain adequate airspeed which resulted in a stall mush. Contributing to the accident were the flight instructor's inadequate supervision and the night conditions.Mar 31, 1998 · N9233H · DestroyedNTSB ATL91LA146Accident · No injuriesLimited investigationFinal reportCessna C172M · Mc Minnville, TNThe failure of the pilot to maintain cleearance from obstacles during the final approach to landing.Jul 28, 1991 · N64022 · Substantial damageNTSB ATL90FA061Accident · 1 fatalField investigationFinal reportPiper PA-28-161 · Norris, TNThe student pilot's misjudged descent which resulted in a collision with trees and the ground. A factor was that the pilot was buzzing when the accident occurred.Feb 6, 1990 · N4338U · DestroyedNTSB ATL89LA204Accident · Serious injuriesLimited investigationFinal reportBeech A23-19 · Gallatin, TNThe pilot used an unsuitable runway area (terrain) for takeoff. Related factors were: inadequate maintenance of the runway, runway conditions (uneven surface & tall grass), and the fence.Aug 27, 1989 · N5684S · Substantial damageNTSB ATL84FLT02Accident · Serious injuriesFinal reportPiper PA-22-150 · Memphis, TNThe acft struck a powerline and crashed 1.5 mi south of Memphis airport while on a ILS localizer app to rwy 36R. The wx at the time of acc was ceiling 200 ft, visibility 3/4 mile with fog. The acft was equipped with a VOR localizer, but no glide sloop…Jan 25, 1984 · N46RS · Substantial damage