FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13CA310 · Schleicher Alexander Gmbh & Co ASH 26 E

12 Apr 2013 · Tullahoma, TN, United States

Schleicher Alexander Gmbh & Co ASH 26 E · Accident on approach

From Tullahoma Regional Airport William Northern Field (THA) to Tullahoma Regional Airport William Northern Field (THA)

Report a problem

Event

NTSB case
ERA13CA310
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

Schleicher Alexander Gmbh & Co ASH 26 E

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
N26EL
Onboard fatalities
Unknown
Route
From Tullahoma Regional Airport William Northern Field (THA), Tullahoma, TNTo Tullahoma Regional Airport William Northern Field (THA), Tullahoma, TN
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
Approach · VFR pattern final
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
Miscellaneous/other
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

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft systems
  • Personnel issues › Action/decision

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

NTSB narrative

According to the pilot, he was on a one mile final approach to runway 36 at 800 feet with the glider engine stowed. He noted that the wind was changing and extended the flaps. The airspeed was between 55 and 60 knots when the airbrakes were extended to start a descent. The altitude was high and the glider began to descend at a rapid rate. The pilot closed the airbrakes to arrest the descent rate but realized he was to low and unable to land on the intended runway. The glider collided with a tree, and a post-accident examination revealed that the left wing was substantially damaged. The pilot reported no pre-impact mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot's improper use of wing spoilers during approach resulting in an altitude loss and collision with a tree.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13CA310
Event ID
20130702X20438
Case number
ERA13CA310
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: a3908144491a0021285412bccdd9f0c257baa65bad6127abaedef9ae01460ff1; retrieved 2026-09-15T22:03:10.640Z.