GAA18CA263 · Schweizer SGS 1 26 E
New England Soaring Association Schweizer SGS 1 26 E · Accident: collision during takeoff/landing on approach
From Hartness State Airport (VSF) to Hartness State Airport (VSF)
Event
- NTSB case
- GAA18CA263
- 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
Schweizer SGS 1 26 E
- Aircraft type
- Schweizer SGS-1
- 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
- N17909
- Operator
- New England Soaring Association
- Onboard fatalities
- Unknown
- Route
- From Hartness State Airport (VSF), Springfield, VTTo Hartness State Airport (VSF), Springfield, VT
- Aircraft age
- About 46 years (built 1972)
- 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
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Environmental issues › Physical environment
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the glider pilot, the glider remained airborne for about 90 minutes before encountering downdrafts while he was pursuing a cumulous cloud system. He immediately attempted to return to the airport but had to select an off-airport landing site instead. During approach, the glider had "insufficient altitude" to clear trees on the west side of the field and collided with branches before impacting the ground.
The glider sustained substantial damage to the fuselage and left-wing spar.
The pilot reported that there were no mechanical malfunctions or failures with the glider that would have precluded normal operation.
Probable cause
The pilot’s inability to maintain sufficient altitude after the glider encountered downdrafts during the approach, which resulted in the glider striking trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA18CA263
- Event ID
- 20180507X81650
- Case number
- GAA18CA263
- 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: 7304c933215ce0143c44b82efc374991a036cb34a154f8c9dc618a18f0114843; retrieved 2026-09-16T07:03:07.830Z.