NTSB investigations: Luscombe 8A

7 cases on aircraft the registry lists as Luscombe 8A, where the first occurrence was “In flight collision with object”. 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

19832026
NTSB investigations: Luscombe 8A per year, 1983–2026: 7 cases
19831
19841
19851
19881
19911
19971
19991

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_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 220))
  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 CHI00LA051Accident · 1 fatalLimited investigationFinal reportLuscombe 8A · Orleans, NEthe pilot's failure to maintain adequate clearance from the power line. The power line was a factor.Dec 25, 1999 · N1363K · Substantial damageNTSB CHI97LA304Accident · 1 fatalLimited investigationFinal reportLuscombe 8A · Brooklyn, MIfailure of the pilot to see-and-avoid the transmission wires (inadequate visual lookout, and failing to maintain sufficient altitude and clearance from the obstruction).Sep 27, 1997 · N1269K · DestroyedNTSB SEA91LA088Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Clark Fork, IDThe pilot-in-command's failure to maintain proper altitude in cruise light resulting in an in flight collision with a wire and subsequent forced landing in a river.Apr 19, 1991 · N45656 · DestroyedNTSB ATL88FA199Accident · 1 fatalField investigationFinal reportLuscombe 8A · Horse Shoe, NCA witness reported that he was irrigating a newly cultivated corn field with a spray irrigation machine. He heard and then observed the accident airplane fly through or just over a gap in the trees at the northeast end of the field. The airplane proceeded to…Jun 22, 1988 · N1144B · DestroyedNTSB ATL85LA104Accident · Minor injuriesLimited investigationFinal reportLuscombe 8A · Suches, GAAfter takeoff in mountainous terrain pilot used shallow climb on course. Pilot stated he failed to climb to a suitable altitude. When first ridge was cleared a downdraft was encountered. Pilot made 180 degree turn but was unable to climb above terrain.Feb 28, 1985 · N71877 · Substantial damageNTSB CHI84LA230Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Center Village, OHThe plt stated that during the takeoff, the acft prematurely became airborne, then settled back onto the rwy & lifted off again. During the second lift-off, he raised the left w ing. Subsequently, the left x-wind blew the acft into a tree line beside the rwy.Jun 12, 1984 · N1244K · DestroyedNTSB SEA83LA106Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Cle Elum, WAThe acft collided with a power line while flying low over a river. Reportedly the student pilot was buzzing some rafterson the yakima river when the acft collided with a power line about 25 feet AGL. The powerline was downed by the impact and the acft right…May 21, 1983 · N71836 · Substantial damage