NTSB investigations: Luscombe 8E

9 cases on aircraft the registry lists as Luscombe 8E, where the sequence of events included Runway excursion. 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

20092026
NTSB investigations: Luscombe 8E per year, 2009–2026: 9 cases
20091
20111
20122
20163
20181
20191

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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('8190112')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.case_mkey = x.case_mkey AND s.aircrafts_position = x.position AND s.\"tier2Number\" = '300' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE \"isDefiningEvent\")))
  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 ERA19TA222Accident · No injuriesClass 3Final reportLuscombe 8 · Sevierville, TNThe pilot's failure to maintain directional control during the landing roll, which resulted in a runway excursion and right main landing gear collapse.Jul 2, 2019 · N2352K · Substantial damageNTSB GAA18CA456Accident · No injuriesData collectionFinal reportLuscombe 8 · Pottsville, PAThe pilot’s failure to maintain directional control during landing.Jul 30, 2018 · N2022K · Substantial damageNTSB GAA17CA066Accident · No injuriesData collectionFinal reportLuscombe 8 · Conway, ARThe pilot’s failure to maintain directional control of the airplane during the landing roll, which resulted in a runway excursion and ground loop.Nov 12, 2016 · N2604K · Substantial damageNTSB GAA17CA038Accident · Minor injuriesData collectionFinal reportLuscombe 8 · Wilmington, OHThe pilot's improper landing flare, which resulted in a bounced landing, and his subsequent failure to maintain directional control, which resulted in a runway excursion.Oct 15, 2016 · N1750K · Substantial damageNTSB GAA16CA476Accident · No injuriesData collectionFinal reportLuscombe 8 · Juneau, WIThe pilot's failure to maintain directional control during the landing roll in gusting crosswind conditions, which resulted in a runway excursion. Contributing to the accident was the foot pad cover slipping off the right rudder pedal during the landing roll.Sep 10, 2016 · N1263K · Substantial damageNTSB ERA12CA403Accident · No injuriesData collectionFinal reportLuscombe 8E · Selinsgrove, PAThe pilot's failure to maintain airplane control during the takeoff.Jun 9, 2012 · N2052K · Substantial damageNTSB WPR12CA159Accident · Minor injuriesData collectionFinal reportLuscombe 8E · Westport, WAThe pilot’s inadequate crosswind compensation, which resulted in a loss of directional control during the landing roll.Apr 7, 2012 · N1183K · Substantial damageNTSB CEN12CA117Accident · No injuriesData collectionFinal reportLuscombe 8E · Atchison, KSThe pilot's inadequate directional control during the landing roll.Dec 17, 2011 · N71911 · Substantial damageNTSB CEN09CA310Accident · No injuriesData collectionFinal reportLuscombe 8E · Ozona, TXThe pilot's failure to maintain directional control of the airplane during landing.May 21, 2009 · N2450K · Substantial damage