CEN18FA262 · Schempp-Hirth Flugzeugbau Gmbh VENTUS 3F
Schempp-Hirth Flugzeugbau Gmbh VENTUS 3F · Accident: loss of control in flight while maneuvering
From Moriarty Municipal Airport (0E0) to Moriarty Municipal Airport (0E0)
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
- CEN18FA262
- 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
Schempp-Hirth Flugzeugbau Gmbh VENTUS 3F
- Aircraft type
- Schempp Hirth VENTUS 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
- N753R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Moriarty Municipal Airport (0E0), Moriarty, NMTo Moriarty Municipal Airport (0E0), Moriarty, NM
- Aircraft age
- About 1 year (built 2017)
- 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
- Maneuvering
- 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
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot was conducting a local flight in his motorglider in day visual meteorological conditions. Another glider pilot in the area reported hearing the accident pilot announce over the radio that he was not getting any lift and was going to stay near the airport. About 2 hours after the pilot departed on the flight, a witness on the ground saw the glider as she was driving near the airport. The glider was in a nose-down attitude very close to the ground; she thought that it might be landing. She subsequently turned her car and lost sight of the glider.
A search was initiated when the glider did not return to the airport as expected, and the wreckage was located about 1/2 mile southeast of the airport. The glider was equipped with a FLARM, which is an onboard collision avoidance system that recorded the glider's flight track, altitude, groundspeed, and engine noise level (ENL). The ENL value increased during the last 4 minutes of flight and then began to fluctuate during the last 13 seconds, both of which are indicative of engine use. FLARM data that were sent to a ground station indicated that, about 11 seconds before impact, the glider entered a left descending turn about 560 ft above ground level; the turn continued until just before impact. The FLARM data could not be correlated with the glider's airspeed, thus the glider's airspeed during the turn could not be determined.
Witness marks on the ground and the structural damage observed at the scene indicated that the glider impacted the ground with the left wingtip immediately followed by the left wing, the engine and propeller, and cockpit. The upward and aft crushing damage was consistent with the glider impacting the terrain in a steep nose down attitude, characteristic of a low-altitude aerodynamic stall. Examination of the airframe and engine revealed no evidence of preimpact anomalies that would have precluded normal operation.
The accident pilot had purchased the glider several months before the accident. Although he had logged over 1,300 hours of flight experience in gliders , the pilot had logged less than 10 hours in the accident glider.
Based on the impact damage, it is likely that during the left descending turn, after the last recorded data from the FLARM, the airplane pitch exceeded the critical angle of attack resulting in an aerodynamic stall causing the glider to descend to the ground in a steep nose down pitch attitude.
Probable cause
The pilot's exceedance of the glider's critical angle of attack during a low-altitude turn, which resulted in an aerodynamic stall and subsequent impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN18FA262
- Event ID
- 20180710X25659
- Case number
- CEN18FA262
- 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: 116e766e15cb1d1200a73897d62eac5a0c9317eed10cb9124dfd8bf81145177f; retrieved 2026-09-15T06:43:54.806Z.