FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW95LA335 · Schempp-Hirth VENTUS A

7 Aug 1995 · Rocksprings, TX, United States

Schempp-Hirth VENTUS A · Accident: airframe, component or system failure en route

From Garner Field (UVA) to an unrecorded destination

Report a problem

Event

NTSB case
FTW95LA335
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
0
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 A

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
N307L
Operator
Unknown
Onboard fatalities
Unknown
Route
From Garner Field (UVA), UVLADE, TXTo not recorded
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
En route · cruise
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
Substantial

Cause areas

  • Flight control, elevator surface › Debonded
  • Flt control syst, elevator control › Inadequate

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

NTSB narrative

ACCORDING TO THE PILOT, AS HE ATTEMPTED TO ACCELERATE TO GLIDE SPEED, HE EXPERIENCED PROBLEMS WITH ELEVATOR CONTROL. HE SAID HE HAD TO APPLY FULL ELEVATOR BEFORE THE GLIDER WOULD RESPOND TO THE CONTROL INPUTS AND THAT IT RESPONDED VERY SLOWLY.' THE PILOT WAS GOING TO LAND ON A RANCH ROAD; HOWEVER, BECAUSE OF THE CONTROL PROBLEM, HE DETERMINED IT WAS SAFER TO BAIL OUT. THE GLIDER IMPACTED THE GROUND IN A LEVEL ATTITUDE, DAMAGING THE FUSELAGE, HORIZONTAL STABILIZER, AND CANOPY. EXAMINATION OF THE GLIDER REVEALED THAT MYLAR TAPE, WHICH WAS USED AS A GAP SEAL FOR THE ELEVATOR, HAD PARTIALLY SEPARATED.

Probable cause

DEBONDING OF MYLAR TAPE THAT WAS USED TO SEAL A GAP ON THE ELEVATOR, WHICH RESULTED IN INADEQUATE ELEVATOR CONTROL AUTHORITY.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW95LA335
Event ID
20001207X04237
Case number
FTW95LA335
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. 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: 02db58b9e07bf5d3a77e82f51e21ccfafdae19f10636799afb3e48f8afab1b61; retrieved 2026-09-21T22:07:14.122Z.