NTSB investigations: Lycoming 0-320 series, 2010

8 cases on aircraft whose registry engine model is Lycoming 0-320 series, where the defining event was Collision during takeoff/land. 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, 2010 per year, 2008–2026: 107 cases
20087
20096
20108
20119
20129
20132
20142
20153
20165
20172
20184
20199
202010
20216
20225
20235
20244
20255
20266

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\") = 2010
    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\" = '490'))
  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 CEN10LA575Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Basehor, KSThe pilot's improper touchdown point during landing and his delayed decision to execute a go-around. Contributing to the accident was the pilot's vision being obscured by the rain.Sep 25, 2010 · N6484R · DestroyedNTSB CEN10LA227Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Glenwood, NMThe pilot's decision to attempt a takeoff from an unimproved airstrip with a high density altitude.Aug 7, 2010 · N4372J · Substantial damageNTSB WPR10FA384Accident · Minor injuriesField investigationFinal reportCessna 172 · Roche Harbor, WAThe pilot’s failure to attain an adequate climb airspeed due to his use of flaps for takeoff, and his selection of a runway, which resulted in an uphill, and possibly downwind, takeoff and subsequent collision with a known obstacle. Contributing to the…Aug 6, 2010 · N9730H · Substantial damageNTSB ERA10CA392Accident · No injuriesData collectionFinal reportCessna 172N · Elk Creek, VAThe student pilot’s continued visual flight into instrument meteorological conditions, which resulted in an off-airport landing.Jul 31, 2010 · N172FL · Substantial damageNTSB ANC10CA063Accident · No injuriesData collectionFinal reportCessna 172P · New Stuyahok, AKThe pilot's selection of unsuitable terrain for takeoff, resulting in a collision with trees.Jul 18, 2010 · N63022 · Substantial damageNTSB ANC10CA047Accident · No injuriesData collectionFinal reportPiper PA-22-160 · Port Alsworth, AKThe pilot's selection of unsuitable terrain for takeoff and inability to abort the takeoff, resulting in an overrun into the water.Jun 1, 2010 · N9217D · Substantial damageNTSB ANC10CA042Accident · No injuriesData collectionFinal reportPiper PA-12 · Chugiak, AKThe pilot's failure to maintain a proper glide path while landing, which resulted in an in-flight collision with a tree, and the collapse of the main landing gear during touchdown.May 22, 2010 · N2581M · Substantial damageNTSB WPR10CA167Accident · No injuriesData collectionFinal reportPiper PA-18-150 · Okanogan, WAThe pilot's failure to maintain clearance from a fence at the end of the runway.Mar 17, 2010 · N4425Z · Substantial damage