CHI96LA279 · Schleicher ASK-13
Schleicher ASK-13 · Accident: in flight collision with object during takeoff
From Thompsonville Airport (7Y2) to 3D4 · Frankfort, MI
Event
- NTSB case
- CHI96LA279
- 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
Schleicher ASK-13
- Aircraft type
- Schleicher ASK-13
- 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
- N11EK
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Thompsonville Airport (7Y2)To 3D4 · Frankfort, MI
- 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 · rejected 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Pilot in command › Evasive maneuver, performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot said that 'just after the tow plane rotated for takeoff, the pilot (of the tow plane) pulled power. The glider quickly gained on the tow plane.' The pilot did not believe that he could land behind the tow plane. 'I released (the tow cable) and turned to the right over an open field of tall weeds. I leveled off (and) made a course correction which realigned me with the runway. (I) used the altitude we had to gain as much airspeed as possible and flew across the weed field until finally settling into the tall weeds. The horizontal plane surface and the left wing were struck by rotten stumps hidden by the weeds.' The tow plane pilot said that the airplane was not developing full power and he decided to abort the takeoff. Examination of the tow plane revealed no anomalies.
Probable cause
an evasive maneuver necessitated by the tow plane's aborted takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI96LA279
- Event ID
- 20001208X06446
- Case number
- CHI96LA279
- 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: 1493c9dbb9ea794e77d5d2eed02745afa3f13a70cf1329e0f29418b2f4df7310; retrieved 2026-09-22T21:36:54.134Z.