ERA14CA088 · LET L 23 SUPER BLANIK
Seminole Flying & Soaring LET L 23 SUPER BLANIK · Accident: loss of control on ground during landing
From Seminole Lake Gliderport (6FL0) to Seminole Lake Gliderport (6FL0)
Event
- NTSB case
- ERA14CA088
- 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
LET L 23 SUPER BLANIK
- Aircraft type
- Let L-23
- 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
- N321BA
- Operator
- Seminole Flying & Soaring
- Onboard fatalities
- Unknown
- Route
- From Seminole Lake Gliderport (6FL0), Clermont, FLTo Seminole Lake Gliderport (6FL0), Clermont, FL
- Aircraft age
- About 15 years (built 1998)
- 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
- Landing · landing roll
- 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
- Loss of control on ground
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot was landing the glider on runway 36, a 3,000-foot-long, 200-foot-wide, turf runway. During the landing roll, the glider veered off the right side of the runway and struck a gazebo, which resulted in substantial damage to glider's right wing and fuselage. The student pilot did not reside in the United States and subsequently returned to his country of residence. The accident was reported to the NTSB by a Federal Aviation Administration (FAA) inspector about 4 months later. Efforts to contact the student pilot were unsuccessful. The student pilot's total flight experience, and flight experience in the airplane make and model, could not be determined. According to an FAA inspector, there were no known or reported mechanical malfunctions with the glider that would have precluded normal operation. Winds reported at an airport located about 21 miles south of the accident site, around the time of the accident, were from 110 degrees at 10 knots.
Probable cause
The student pilot's failure to maintain directional control during the landing roll.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14CA088
- Event ID
- 20140107X93850
- Case number
- ERA14CA088
- 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: 0f89d40ed55cb02ce21e34c2dffc9e7eeda426046487bb2c57e8145150453a7c; retrieved 2026-09-15T23:14:23.172Z.