FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DFW06CA111 · Schempp-Hirth Ventus-2C

22 Apr 2006 · Midlothian, TX, United States

Schempp-Hirth Ventus-2C · Accident: airframe, component or system failure during takeoff

From Midlothian, TX to Midlothian, TX

Report a problem

Event

NTSB case
DFW06CA111
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
0 · 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

Schempp-Hirth Ventus-2C

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
N340TW
Operator
Unknown
Onboard fatalities
Unknown
Route
From Midlothian, TXTo Midlothian, TX
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
Takeoff
First occurrenceThe 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
Airframe, component or system failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Flt control syst, wing spoiler system › Deployed inadvertently

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The 630-hour glider commercial pilot reported that prior to departure from the 4,200-feet by 400-feet wide grass-turf gliderport, he followed his checklist items which included; checking and closing the spoilers, checking the seat belts and shoulder harnesses. During the aero tow takeoff, the pilot noticed the uncommanded opening of the spoilers and he elected to release from the aero tow. During the landing on the grass runway, the glider touched down hard. The glider received minor damage to its landing gear and the pilot was seriously injured. The reason for the uncommanded extension of the spoilers could not be determined.

Probable cause

The inadvertent deployment of the spoilers during the aero tow takeoff for undetermined reasons, resulting in a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DFW06CA111
Event ID
20060516X00580
Case number
DFW06CA111
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: b7c6bba2fe21563e48eab20f61199fba0e568f410cf92f4592100317659be635; retrieved 2026-09-21T08:58:47.874Z.