NTSB investigations: Luscombe 8A

18 cases on aircraft the registry lists as Luscombe 8A, 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 8A per year, 2009–2026: 18 cases
20091
20102
20122
20131
20152
20161
20171
20183
20192
20211
20231
20251

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 ('8190104', '8190111')
      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 WPR25LA141Accident · No injuriesClass 4 · LimitedFinal reportLuscombe 8 · Placerville, CAThe pilot’s failure to maintain directional control during the landing roll.Apr 18, 2025 · N1286B · Substantial damageNTSB CEN23LA117Accident · Minor injuriesClass 4 · LimitedFinal reportLuscombe 8A · Guthrie, OKThe student pilot’s failure to maintain directional control during the landing roll.Feb 20, 2023 · N25342 · Substantial damageNTSB ERA21LA231Accident · Minor injuriesClass 4 · LimitedFinal reportLuscombe 8A · Skaneateles, NYThe pilot’s failure to maintain directional control during the takeoff roll which resulted in a runway excursion and nose-over event.May 24, 2021 · N1331K · Substantial damageNTSB CEN20LA029Accident · No injuriesClass 3 · LimitedFinal reportLuscombe 8A · Baldwin City, KSThe pilot's failure to maintain directional control during takeoff, and the flight instructor's delayed remedial action, which resulted in a runway excursion and nose over.Dec 4, 2019 · N45606 · Substantial damageNTSB GAA19CA288Accident · No injuriesData collectionFinal reportLuscombe 8 · Carbondale, ILThe pilot's inadvertent left heel brake application during the landing roll, which resulted in a noseover.May 26, 2019 · N45729 · Substantial damageNTSB GAA18CA524Accident · No injuriesData collectionFinal reportLuscombe 8 · Fulton, MOThe pilot’s failure to maintain directional control during landing in gusting crosswind conditions.Aug 28, 2018 · N1211B · Substantial damageNTSB GAA18CA338Accident · No injuriesData collectionFinal reportLuscombe 8 · Phoenix, AZThe pilot’s improper landing flare and subsequent failure to maintain directional control during landing.Jun 12, 2018 · N2094B · Substantial damageNTSB GAA18CA205Accident · No injuriesData collectionFinal reportLuscombe 8 · Vernon, TXThe pilot’s failure to maintain directional control during landingApr 5, 2018 · N71617 · Substantial damageNTSB GAA17CA498Accident · Minor injuriesData collectionFinal reportLuscombe 8 · Perryville, MOThe pilot’s failure to maintain directional control during takeoff.Aug 21, 2017 · N2861K · Substantial damageNTSB GAA16CA248Accident · No injuriesData collectionFinal reportLuscombe 8 · Blue Bell, PAThe pilot's failure to maintain directional control during the takeoff roll and the flight instructor's delayed remedial action, which resulted in runway excursion, and collision with a ditch.May 19, 2016 · N62925 · Substantial damageNTSB WPR16LA017Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Prescott, AZThe pilot's failure to maintain directional control during landing, and his inability to recover due to a malfunction of the tailwheel.Oct 24, 2015 · N25100 · Substantial damageNTSB GAA15CA193Accident · Minor injuriesData collectionFinal reportLuscombe 8A · Oxford, IAThe pilot's selection of unsuitable terrain for takeoff based on the runway and density altitude conditions, which resulted in a runway excursion and impact with terrain.Jul 19, 2015 · N45508 · Substantial damageNTSB CEN13CA453Accident · No injuriesData collectionFinal reportLuscombe 8A · Ellinwood, KSThe pilot failed to maintain directional control during takeoff.Jul 31, 2013 · N45957 · Substantial damageNTSB ERA12CA269Accident · No injuriesData collectionFinal reportLuscombe 8A · Pittsburgh, PAThe pilot’s loss of directional control during the landing roll, which resulted in a runway excursion.Apr 3, 2012 · N71479 · Substantial damageNTSB ERA12CA140Accident · No injuriesData collectionFinal reportLuscombe 8A · Umatilla, FLA failure of the left main landing gear due to a preexisting crack and corrosion, which resulted in a loss of directional control during landing.Jan 7, 2012 · N77859 · Substantial damageNTSB ERA10CA225Accident · No injuriesData collectionFinal reportLuscombe 8A · Lakeland, FLThe pilot's failure to maintain directional control of the airplane during the landing roll, resulting in a ground loop.Apr 10, 2010 · N1128K · Substantial damageNTSB ERA10LA121Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Madison, GAThe pilot’s failure to maintain directional control while landing with a tailwind.Jan 19, 2010 · N2750K · Substantial damageNTSB ERA09LA520Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Arcadia, FLThe pilot's bounced takeoff roll, which resulted in a collapsed landing gear. Contributing to the accident was the airplane's overweight condition.Aug 27, 2009 · N40VS · Substantial damage