NTSB investigations: Luscombe 8E

9 cases on aircraft the registry lists as Luscombe 8E, where the sequence of events included Nose over/nose down. 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: Luscombe 8E per year, 2008–2026: 9 cases
20081
20101
20113
20122
20162

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\" = '096' 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 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 WPR16LA141Accident · Minor injuriesLimited investigationFinal reportLuscombe 8A · Minden, NVThe failure of a main landing gear leg during takeoff due to corrosion, which resulted in a nose-over during the subsequent landing on a grassy area.Jul 17, 2016 · N2759K · 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 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 ERA11CA281Accident · Minor injuriesData collectionFinal reportLuscombe 8E · Apex, NCThe pilot’s excessive application of the brakes, which caused the airplane to nose over.May 3, 2011 · N1902K · Substantial damageNTSB ERA11CA199Accident · No injuriesData collectionFinal reportLuscombe 8E · Taunton, MAThe pilot's inadvertent application of the brakes during recovery from a ground loop which resulted in a nose over.Mar 19, 2011 · N2790K · Substantial damageNTSB WPR10CA334Accident · Minor injuriesData collectionFinal reportLuscombe 8E · Tillamook, ORThe certified flight instructor’s selection of an inappropriate landing surface and the loss of engine power as a result of the improper use carburetor heat. Contributing to the accident was the flight instructor's inadequate supervision.Jul 4, 2010 · N2466K · Substantial damageNTSB LAX08CA051Accident · No injuriesData collectionFinal reportLuscombe 8E · Brigham City, UTThe failure of the landing gear/ski attachment assembly due to inadequate maintenance.Jan 20, 2008 · N71730 · Substantial damage