FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR25LA015 · Glasflugel STANDARD LIBELLE

11 Oct 2024 · Moriarty, NM, United States

Glasflugel STANDARD LIBELLE · Accident: landing area undershoot

From Moriarty Municipal Airport (0E0) to an unrecorded destination

Report a problem

Event

NTSB case
WPR25LA015
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
Event fatalities
Unknown
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

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
N41FL
Operator
Unknown
Onboard fatalities
Unknown
Route
From Moriarty Municipal Airport (0E0), Moriarty, NMTo not recorded
Aircraft age
About 52 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
Landing
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
Landing area undershoot
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 › 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

The pilot of the glider reported that, while on the downwind leg of the airport traffic pattern, he partially deployed the flight spoilers and extended his downwind leg as the glider was too high. He misjudged his distance to the runway during this time and the glider lost more altitude than the pilot had anticipated. The pilot flared during final; however, the glider impacted rough terrain short of the runway threshold. The glider sustained substantial damage to the fuselage and empennage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the glider that would have precluded normal operation.

Probable cause

The pilot’s failure to maintain an adequate glidepath, which resulted in the glider landing on rough terrain short of the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR25LA015
Event ID
20241015195318
Case number
WPR25LA015
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, cause areas. 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: 376512446143f8b6c7a74155b4aadb911b8e03c604c223bd9a6fde71a9fb965c; retrieved 2026-09-16T19:23:01.397Z.