Released tow rope brushes a Discus 2b after the tug misses the disconnect

Federispitz, Switzerland Schempp-Hirth Discus-2B FFA AS 202/32 Turbo Bravo

After a Discus 2b released from aerotow at about 2,200 m near Schänis, its freed rope brushed the glider; both crews were unhurt and the Discus was left with light scratches and a bent gear-door hinge. The tug — a high-powered Turbo Bravo — was flying on reduced power at the glider pilot's radioed request to ease rope tension for release. Because the rope was slightly slack, the tug pilot never felt the disconnect and climbed on some 10 to 20 m above the glider; on spotting it low behind him in his mirror, he banked steeply left with airbrakes out, and the trailing rope struck the Discus. The glider handled normally and landed at Schänis.

  1. Aerotow to release height: A Discus 2b was aerotowed near Schänis behind a high-powered AS 202 Turbo Bravo and reached release height at about 2,200 m.
  2. Low-power release procedure: To keep the strong tug from snapping the rope forward on release, the glider pilot radioed his intent so the tug pilot could reduce power and ease the rope tension.
  3. Slack rope hides the release: The rope was slightly slack, so the tug pilot never felt the disconnect and kept climbing on reduced power, ending some 10 to 20 m above the glider.
  4. Tug turns steeply into the rope: On spotting the glider low behind him in his mirror, the tug pilot banked steeply left with airbrakes out, and the trailing rope swung into the Discus.
  5. Rope brushes the Discus; lands safe: The rope scraped the glider's nose and bent a gear-door hinge but did not affect its handling; the Discus landed at Schänis, both crews unhurt.
Loading incidents...
Select Incident
Select Report
Filter
0/0
Incident year
1997 2024
Sort By
Search
0/0
Preferences
Save preferences
Enable map view
Show analysis
Language
Theme
About

gliderincidents.com gathers and lists soaring incident reports from official sources. The sources are indicated and linked. These reports are amended by summaries, metadata and translations, some of which have been generated utilizing machine learning (AI). You shouldn't trust the information provided here blindly, and consider reading the official incident report as a fact-check.

OR AND
0/0
Flight Phase
Circumstance
Decision pattern
Mitigation
0/0
Severity Levels
0/0
Countries

Please describe what information is incorrect or needs review:

Bookmarked