NTSB investigations: Lycoming 0-320 series, AR

6 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

19842026
NTSB investigations: Lycoming 0-320 series, AR per year, 1984–2026: 6 cases
19841
19911
19921
19961
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\" = '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\" = 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 DFW05CA203Accident · No injuriesData collectionFinal reportCessna 172M · El Dorado, ARThe student pilot's improper landing flare resulting in a hard landing and his improper recovery procedures for a bounced landing.Aug 2, 2005 · N80735 · Substantial damageNTSB FTW00LA014Accident · No injuriesLimited investigationFinal reportRobinson R22 Beta · Jonesboro, ARThe flight instructor's delay in taking remedial action to recover from a low rotor rpm situation. A factor was the student's failure to maintain adequate rotor rpm.Oct 21, 1999 · N2301C · Substantial damageNTSB FTW96LA245Accident · No injuriesLimited investigationFinal reportBeech 23 · Weiner, ARan improper flare by the pilot, which resulted in a hard landing.Jun 11, 1996 · N2398L · Substantial damageNTSB FTW92LA091Accident · No injuriesLimited investigationFinal reportCessna 172P · West Helena, ARPilot's improper flarea ND improper recovery from a bounced landing.Mar 16, 1992 · N96493 · Substantial damageNTSB FTW91LA116Accident · No injuriesLimited investigationFinal reportCessna 172P · Lakeview, AR(1) The pilot's failure to properly flare the airplane for landing and (2) his subsequent improper recovery from a bounced landing.Jul 4, 1991 · N64344 · Substantial damageNTSB MKC84LA233Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · No Little Rock, ARThe pilot-in-command was hired by the student pilot/aircraft owner to perform the passenger flight. No experience or currency records are available on the PIC as he had not held an airman's medical certificate for the last four years. On landing at…Jul 1, 1984 · N44213 · Substantial damage