CEN19FA211 · Grob G103 TWIN ASTIR
Central MS Soaring Society Grob G103 TWIN ASTIR · Accident: collision during takeoff/landing
From Woodbridge Airport (6MS1) to Harrell Field (MS08)
Event
- NTSB case
- CEN19FA211
- 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
- 1 · 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
Grob G103 TWIN ASTIR
- Aircraft type
- Grob G103
- 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
- N106NS
- Operator
- Central MS Soaring Society
- Onboard fatalities
- Unknown
- Route
- From Woodbridge Airport (6MS1), Brandon, MSTo Harrell Field (MS08), Pisgah, MS
- Aircraft age
- About 41 years (built 1978)
- 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
- 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
- Collision during takeoff/landing
- 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
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot of the accident glider and a pilot of another glider repositioned the two gliders from one airfield to another about 6 miles east of the departure airport. The purpose of the flight was to fly two gliders to a location where they conducted their glider flights. The first glider was towed to 2,000 ft agl, southeast of the departure airport. After the glider was released, the glider pilot flew towards the other airport, and the towpilot returned for the second glider. The accident pilot stated to the towpilot that he planned to release at 3,000 ft agl. When they were about 2,100 agl, the glider pilot released from the towplane. The towpilot stated that this was in same area that the first glider released and didn't see or hear from the glider pilot again. The pilot in the first glider reported that he heard the accident pilot state via radio that he was "getting low and would probably have to land out." The wreckage was located in a fenced field about 2.5 miles southeast of the departure airport and about 6 miles southwest of the destination airport. The glider came to rest inverted about 150 ft beyond an oak tree located at the edge of the field. A piece of the glider's right wing skin was found in a branch of the oak tree about 25 to 30 ft above the ground. Several small branches and leaves were located on the ground beneath the branch. Additionally, there were several impact signatures on parts of the tree branch near the wing skin; the signatures on the branch and ground scars are consistent with the glider's collision with a tree before impact with terrain. Examination of the glider revealed no anomalies. Toxicology of the pilot revealed the presence of metabolites of tetrahydrocannabinol; however, since no active compounds were found in blood, it is unlikely that any effects from his use of marijuana contributed to the accident. The field where the glider came to rest contained several wire fences across and lengthwise to the field. It is likely that these fences were not visible to the pilot until he was committed to the landing. It could not be determined if the pilot tried to avoid the fence during the approach and landing. Given the available evidence, the pilot was attempting to obtain lift in the vicinity of the departure airport but became low and chose to conduct an off-airport landing. During the subsequent off-airport landing, the right wing impacted a tree and the glider subsequently impacted terrain.
Probable cause
The pilot's inadequate clearance from a tree during an attempted off-field landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN19FA211
- Event ID
- 20190706X51649
- Case number
- CEN19FA211
- 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, coordinates. 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: 05b71b91c0556596c17028963cdad865f3168f13249599c832206d75c1792500; retrieved 2026-09-15T07:01:28.544Z.