NTSB investigations: Luscombe 8E

7 cases on aircraft the registry lists as Luscombe 8E, where the sequence of events included Collision with terr/obj (non-CFIT). 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

20122026
NTSB investigations: Luscombe 8E per year, 2012–2026: 7 cases
20122
20151
20161
20181
20231
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 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\" = '470' 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 CEN26LA169Accident · No injuriesClass 4 · LimitedFinal reportLuscombe 8E · Meeker, COThe pilot’s inability to maintain climb performance and clearance from terrain due to the airplane’s encounter with windshear during takeoff.Apr 19, 2026 · N1398K · Substantial damageNTSB CEN23LA118Accident · No injuriesClass 3 · LimitedFinal reportLuscombe 8E · Houston, TXThe pilot’s failure to attain/maintain lateral airplane control during landing, which resulted in an impact with the runway surface.Feb 19, 2023 · N2722K · 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 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 ERA15FA103Accident · 1 fatalField investigationFinal reportLuscombe 8 · Fort Valley, GAThe flight instructor’s failure to maintain airspeed during an approach with a simulated engine failure, which resulted in an exceedance of the wing’s critical angle-of-attack and a subsequent aerodynamic stall/spin.Jan 16, 2015 · N1745K · Substantial damageNTSB CEN13CA042Accident · Minor injuriesData collectionFinal reportLuscombe 8E · West Bend, WIThe pilot‘s failure to maintain clearance from power lines at the end of the short runway, which resulted in an aborted takeoff and subsequent nose-over of the airplane.Nov 3, 2012 · N2368K · 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 damage