FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA11FA401 · Slingsby CAPSTAN TYPE 49B

15 Jul 2011 · Hollywood, MD, United States

Slingsby CAPSTAN TYPE 49B · Accident: glider tow event during initial climb

From St. Mary's County Regional Airport (2W6) to St. Mary's County Regional Airport (2W6)

Report a problem

Event

NTSB case
ERA11FA401
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Slingsby CAPSTAN TYPE 49B

Category
Glider
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N7475
Operator
Unknown
Onboard fatalities
Unknown
Route
From St. Mary's County Regional Airport (2W6), Leonardtown, MDTo St. Mary's County Regional Airport (2W6), Leonardtown, MD
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Initial climb
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Glider tow event
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

According to the glider pilot/owner, he purchased the glider 1 week before the accident and flew it with the previous owner for about 1 hour at the time of purchase. He assembled the glider with the assistance of the tow plane pilot and completed all post-assembly checks before they were joined by his copilot. The pilot and copilot then performed the before-takeoff checks outside the aircraft, confirmed operation of the tow release mechanism, and verified that the spoilers were closed. During the initial climb, the glider pilot noticed that the glider was not climbing, and he and his copilot, a more experienced glider pilot, discussed relative position to the tow plane in order to avoid wake turbulence and improve climb performance. About 200 feet above ground level and over the trees beyond the departure end of the runway, the glider pilot observed the tow plane's rudder "waggle" back and forth, and his copilot shouted, "Release! Release! Release!" The glider pilot released the glider from the tow plane and entered a left turn to the north for a forced landing on the divided highway east of the airport. The copilot joined him on the flight controls before the glider overshot the highway and collided with trees on the east side of the roadway.

The tow plane pilot provided a similar recounting of the events. He explained that, before the flight, the proper signals for “too fast” or “too slow” were discussed but no others. He added that he had discussed signaling with the glider’s copilot many times previously but that they had not recently discussed the rudder-wag signal, which means “check spoilers.” After takeoff, he noted that the tow plane’s performance was as expected, but the climb rate was not. He checked the glider in his rearview mirror and noted that the spoilers were deployed. The tow plane pilot provided the internationally recognized (in the glider community) rudder-wag signal, and, instead of stowing the spoilers, the glider released from the tow.

Postaccident examination of the glider revealed no mechanical deficiencies. The pilot/owner stated that he knew the meaning of the rudder-wag signal, but responded to the callout from his copilot. He further stated that he believed the spoilers were stowed during preflight and before-takeoff checks, but he did not confirm that the control was locked in its detent prior to takeoff.

Probable cause

The glider pilot’s improper response to the “check spoilers” signal from the tow pilot. Contributing to the accident was the glider pilot’s failure to confirm that the spoilers were closed and locked before takeoff, and the glider copilot’s improper crew coordination response to the “check spoilers” signal from the tow pilot.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA11FA401
Event ID
20110715X11650
Case number
ERA11FA401
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: b314ea534311417e6e048ad06c42b6e7c24b65e0feeb5577a1140082c161e1ed; retrieved 2026-09-13T21:34:52.043Z.