ERA10CA419 · Schweizer SGS 1-34
Seminole Flying & Soaring Schweizer SGS 1-34 · Accident: collision with terrain/object (non-CFIT) on approach
From Seminole Lake Gliderport (6FL0) to Seminole Lake Gliderport (6FL0)
Event
- NTSB case
- ERA10CA419
- 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-34
- 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
- N65916
- Operator
- Seminole Flying & Soaring
- Onboard fatalities
- Unknown
- Route
- From Seminole Lake Gliderport (6FL0), Groveland, FLTo Seminole Lake Gliderport (6FL0), Groveland, FL
- 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
- 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 with terrain/object (non-CFIT)
- 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 glider pilot reported that he was in the traffic pattern adjoining the downwind leg for the runway. He turned onto the base leg at 650 feet above ground level (agl) and then turned onto final approach at 450 feet agl. The glider was high and he could not attain a normal glide slope using the dive brakes. He closed the dive brakes and performed a 360-degree turn in an effort to lose altitude. At mid-field, with the glider about 100 feet agl, he decided to circle right and attempt a landing on a perpendicular runway. The glider was too low and impacted a tree short of the runway. A witness reported that the dive brakes remained full open during the accident sequence. The Federal Aviation Administration inspector who examined the wreckage reported that the dive brakes were in the deployed, or up, position when he arrived at the accident site.
Probable cause
The pilot’s failure to attain the proper approach path to the runway, resulting in landing short of the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10CA419
- Event ID
- 20100813X72205
- Case number
- ERA10CA419
- 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: 770daa7dd32c762163015c6915764244eefd30993e4c4f071e83139f4afedfe8; retrieved 2026-09-15T14:50:30.172Z.