NYC08CA236 · Glasflugel Standard Libelle
Glasflugel Standard Libelle · Accident: loss of control in flight en route
From Front Royal Warren County Airport (FRR) to Front Royal Warren County Airport (FRR)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- NYC08CA236
- 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 Standard Libelle
- Aircraft type
- Glasflugel STANDARD LIBELLE
- 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
- N184W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Front Royal Warren County Airport (FRR), Front Royal, VATo Front Royal Warren County Airport (FRR)
- 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
- En route · cruise
- 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 in flight
- 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 › Task performance
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 pilot, the glider was towed to an altitude of 4,700 feet above mean sea level and released. Shortly after release, the pilot encountered severe turbulence that caused the glider to become inverted. During the turbulence encounter, the pilot's head impacted the canopy several times, and shattered the canopy. While the glider was inverted the pilot heard "cracking in the wings." After recovering from the turbulence upset, the pilot attempted to land in a field. While on the final leg of the approach, the glider impacted some trees, and a hard landing resulted. The tree strikes and hard landing caused substantial damage to the wing and fuselage.
Probable cause
Aircraft control was not maintained during cruise flight. Contributing to the accident was turbulence and inadvertent flight into adverse weather.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC08CA236
- Event ID
- 20080904X01378
- Case number
- NYC08CA236
- 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: 62cdba90f9a475be0784e24fb02746bc7e02f9e6cb0edfb5aef44cdd9b9e9c69; retrieved 2026-09-15T10:09:05.745Z.