FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN20CA218 · Glasflugel MOSQUITO Undesignat

4 Jun 2020 · Alvarado, TX, United States

Glasflugel MOSQUITO Undesignat · Accident: loss of control on ground during landing

From Tsa Gliderport (TA11) to Tsa Gliderport (TA11)

Report a problem

Event

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

Glasflugel MOSQUITO Undesignat

Aircraft type
Glasflugel MOSQUITO
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
N24HC
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tsa Gliderport (TA11), Midlothian, TXTo Tsa Gliderport (TA11), Midlothian, TX
Aircraft age
About 43 years (built 1977)
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

  • Environmental issues › Operating environment

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

NTSB narrative

The glider pilot reported that due to a weakening of soaring updraft conditions he diverted from his original destination to another airport that he had landed at on previous occasions. While on short final, the pilot noticed the turf runway had not been mowed recently. During the landing rollout, due to long grass blocking his field of view, the pilot was unable to maintain directional control and the glider impacted a fence to the left of the runway, damaging the left wing and fuselage. The pilot reported no preimpact mechanical failures or malfunctions with the glider that would have precluded normal operation. The diversion airport was a private airport that required prior approval for landing.

Probable cause

The pilot's decision to divert to the private airport and his subsequent failure to maintain directional control while landing on a turf runway that contained tall grass.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN20CA218
Event ID
20200608X25926
Case number
CEN20CA218
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: 40d8fbdd201bc7ab15304d3ea333a7a9702e5e1129c76fcdfd6298fded3f0954; retrieved 2026-09-16T11:47:50.280Z.