NTSB investigations: Lycoming 0-320 series, AR

8 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

19822026
NTSB investigations: Lycoming 0-320 series, AR per year, 1982–2026: 8 cases
19821
19831
19881
19911
19951
19981
20001
20011

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\" = 'AR' 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 FTW01LA138Accident · No injuriesLimited investigationFinal reportCessna 172M · Hot Springs, ARthe student pilot's delayed go-around, which resulted in the airplane impacting trees during the aborted landing.Jun 8, 2001 · N5394H · Substantial damageNTSB FTW00LA090Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Manilla, ARThe pilot's performance of low altitude flight and his failure to maintain clearance with the power lines.Mar 7, 2000 · N20179 · Substantial damageNTSB FTW98FA358Accident · 1 fatalField investigationFinal reportCessna 172N · Cord, ARThe pilot's performance of low altitude flight and his failure to maintain obstacle clearance.Aug 15, 1998 · N6323G · Substantial damageNTSB FTW95FA393Accident · 3 fatalField investigationFinal reportCessna 172M · Witter, ARfailure of the pilot to maintain sufficient altitude/clearance from high/wooded terrain. Factors relating to the accident were: darkness, high terrain, and foggy weather conditions. Also, the pilot's use of Methamphetamine (not approved by the FAA) was a…Sep 13, 1995 · N61899 · DestroyedNTSB FTW91FA060Accident · 2 fatalField investigationFinal reportCessna 172M · Flippin, ARThe pilot's attempted VFR flight in instrument meteorological conditions and his failure to maintain altitude.Apr 4, 1991 · N4416R · DestroyedNTSB MKC88FA120Accident · 1 fatalField investigationFinal reportPiper PA-28-160 · Beedeville, ARIntentional buzzing performed, visual outlook not maintained and over confidence in personal ability by the pilot in command.Jul 2, 1988 · N5517W · Substantial damageNTSB FTW83LA352Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Morrilton, ARThe acft collided with trees on the final approach to land at night. The plt had canceled his IFR clearance. During the approach the plt had the rwy in sight and asked memphis center how FAR he was from the arpt. When he was informed he WAS3 miles south he…Apr 28, 1983 · N54174 · Substantial damageNTSB FTW82FRJ08Accident · 2 fatalFinal reportBellanca 7GCBC · Near Texarkana, ARDuring flight, the aircraft struck a powerline about 70 ft above the red river. The aircraft crashed in the river and drifted about 2 miles before it was recovered. The passenger's body was recovered on 03/21/82 and the pilot's body was recovered on 05/15/83…Feb 21, 1982 · N53731 · Substantial damage