DEN06CA086 · Rolladen-Schneider Gmbh LS-3
Rolladen-Schneider Gmbh LS-3 · Accident: in flight encounter with weather on approach
From 7V1 · Buena Vista, CO to 7V1 · Buena Vista, CO
Event
- NTSB case
- DEN06CA086
- 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
Rolladen-Schneider Gmbh LS-3
- Aircraft type
- Rolladen Schneider LS-3
- 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
- N48CW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 7V1 · Buena Vista, COTo 7V1 · Buena Vista, CO
- 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
- First occurrenceThe 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
- In flight encounter with weather
- 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
- Stall/mush
- 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
- Pilot in command › Stall/mush, inadvertent
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 had been soaring for about 4 hours when he decided to return to the airport. The AWOS (automated weather observation system) had been indicating that the wind was generally from the south-southeast at 10 to 18 knots. As the pilot got closer to the airport, AWOS indicated the wind was from 240 degrees and greater than 20 knots, then 250 degrees at 20 knots. When the pilot had descended to 700 feet agl (above ground level), he encountered a "strong sink." He said that he lost 400 feet in 12 seconds (2,000 fpm descent) and there was a barn, aircraft, and vehicles in his flight path. He decided to make a 180-degree turn in an attempt to land in a field west of the airport. The pilot rolled out of the turn at 30 feet agl. At 15 feet agl, the glider stalled and landed hard on rough, uneven terrain. The landing gear was torn off and the fuselage was buckled.
Probable cause
the pilot's failure to maintain aircraft control resulting in an inadvertent stall/mush. Contributing to the accident was the downdraft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN06CA086
- Event ID
- 20060627X00824
- Case number
- DEN06CA086
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 3f893b2e6216f22c4b073aefa14b97c685d344a9b07e18e2ae93ca993fb1a1b7; retrieved 2026-09-21T08:57:13.195Z.