NTSB investigations: Lycoming O&VO-360 series, 2016

8 cases on aircraft whose registry engine model is Lycoming O&VO-360 series, where the defining event was Loss of control on ground. 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 O&VO-360 series, 2016 per year, 2008–2026: 114 cases
20086
20099
20106
20114
20128
20138
20143
20154
20168
20176
20186
20197
20204
20214
20226
202310
20249
20252
20264

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\") = 2016
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41514')
      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\" = '230'))
  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 GAA17CA096Accident · No injuriesData collectionFinal reportPiper PA28 · Madisonville, TNThe student pilot’s failure to maintain directional control during landing with a gusting crosswind.Dec 15, 2016 · N7646W · Substantial damageNTSB GAA17CA056Accident · No injuriesData collectionFinal reportBeech 76 · Davis, CAThe pilot's failure to maintain directional control during a simulated left engine failure during takeoff. Also causal to the accident was the flight instructor's delayed remedial action to maintain directional control and reduce the right engine mixture…Nov 5, 2016 · N6703L · Substantial damageNTSB GAA16CA494Accident · No injuriesData collectionFinal reportBeech B23 · Raleigh, NCThe pilot’s failure to maintain directional control during the landing roll, which resulted in a runway excursion.Sep 16, 2016 · N4002T · Substantial damageNTSB GAA16CA276Accident · No injuriesData collectionFinal reportMooney M20C · Williamstown, NJThe pilot's landing area overshoot and failure to maintain surface speed and braking capability, which resulted in a runway overrun and a collision with a fence.Jun 4, 2016 · N6453U · Substantial damageNTSB ERA16LA192Accident · No injuriesLimited investigationFinal reportPiper PA 28-180 · Batavia, NYThe student pilot's failure to maintain directional control during takeoff, which resulted in a collision with runway signs.May 19, 2016 · N7781W · Substantial damageNTSB WPR16LA109Accident · No injuriesLimited investigationFinal reportCessna 172RG · Las Vegas, NVThe pilot's loss of directional control during the landing roll, which resulted in a runway excursion.May 13, 2016 · N6281V · Substantial damageNTSB GAA16CA191Accident · No injuriesData collectionFinal reportBeech C23 · Frenchville, METhe pilot's failure to maintain directional control during the takeoff roll on a runway contaminated with ice and snow, which resulted in a runway excursion and an impact with a snowbank.Mar 30, 2016 · N2397E · Substantial damageNTSB GAA16CA147Accident · No injuriesData collectionFinal reportPiper PA 28 · Pearland, TXThe pilot's failure to maintain directional control during the landing roll in gusty wind conditions, which resulted in a runway excursion and a collision with an airport sign.Mar 12, 2016 · N9309J · Substantial damage