NTSB investigations: Lycoming 0-320 series, 2015

7 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the defining event was Abnormal runway contact. 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

20082026
NTSB investigations: Lycoming 0-320 series, 2015 per year, 2008–2026: 81 cases
20085
20092
20109
20113
20122
20134
20144
20157
20168
20175
20188
20192
20205
20215
20225
20231
20243
20252
20261

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 year(c.\"eventDate\") = 2015
    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_events.parquet' e WHERE e.case_mkey = x.case_mkey AND e.aircrafts_position = x.position AND e.\"isDefiningEvent\" AND e.\"tier2Number\" = '090'))
  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 GAA16CA083Accident · No injuriesData collectionFinal reportGrumman American Avn. AA-5A · Friendswood, TXThe student pilot's loss of directional control during an aborted landing, which resulted in a collision with a tree and impact with the ground.Dec 17, 2015 · N9860U · Substantial damageNTSB GAA15CA274Accident · No injuriesData collectionFinal reportCessna 172N · Herington, KSThe pilot's failure to maintain pitch control during the landing roll, which resulted in a porpoise.Sep 16, 2015 · N909HC · Substantial damageNTSB GAA15CA214Accident · No injuriesData collectionFinal reportCessna 172N · Miami, FLThe student pilot's failure to maintain pitch control resulting in a hard landing and damage to the airplane firewall.Aug 3, 2015 · N6223D · Substantial damageNTSB ANC15CA054Accident · No injuriesData collectionFinal reportPiper PA 18-150 · Talkeetna, AKThe pilot's inadequate compensation for wind conditions, and improper recovery from a bounced landing resulting in a loss of control and collision with terrain.Jul 22, 2015 · N323DH · Substantial damageNTSB GAA15CA162Accident · No injuriesData collectionFinal reportCessna 172N · Lubbock, TXThe student pilot's improper flare during landing which resulted in abnormal runway contact and damage to the firewall.Jul 3, 2015 · N6326J · Substantial damageNTSB ERA15CA222Accident · No injuriesData collectionFinal reportCessna 172P · Mitchellville, MDThe pilot’s improper landing flare, which resulted in a bounced landing and damage to the airplane.May 25, 2015 · N6155K · Substantial damageNTSB GAA15CA049Accident · No injuriesData collectionFinal reportCessna 172M · Clearwater, FLThe pilot's excessive airspeed during landing, which resulted in abnormal runway contact, a runway excursion, and substantial damage to the airplane.Apr 24, 2015 · N1576V · Substantial damage