FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR24LA127 · Schleicher Alexander Gmbh & Co ASH 26 E

21 Apr 2024 · Heber, UT, United States

Schleicher Alexander Gmbh & Co ASH 26 E · Accident during initial climb

Report a problem

Event

NTSB case
WPR24LA127
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

Schleicher Alexander Gmbh & Co ASH 26 E

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
N644CC
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 24 years (built 2000)
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
Initial climb
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
Unknown or undetermined
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
  • Aircraft › Aircraft power plant

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 stated that the purpose of the flight was to practice takeoffs and landings in the self-launching powered sailplane (motorglider) at his home airport. After one successful takeoff and landing, the pilot prepared for a second takeoff by extending the engine mast and starting the engine. The engine ran rough at first, which the pilot was stated was normal when the engine was started warm, then “smoothed out.” The pilot commenced the takeoff, which was captured by airport security video. He stated that, shortly after takeoff, the motorglider stopped climbing. The pilot believed there was inadequate runway remaining to land straight ahead and began a 180° descending left turn. Upon completion of the turn the motorglider was positioned to the right side of the intended taxiway. The motorglider impacted rough terrain next to the taxiway, resulting in substantial damage to the fuselage, left wing and empennage. Examination of the rotary engine revealed no visible damage. The fuel delivery system and the ignition systems operated normally; however, the engine would not start despite multiple attempts. Postaccident examination of the airframe revealed no mechanical malfunctions or failures that would have precluded normal operation. Review of the security video footage and ADS-B data revealed that, although the engine reached its maximum takeoff rpm during the takeoff, the motor glider’s climb performance was about 50% less than the first takeoff, despite similar conditions. A sound spectrum analysis of the video indicated a slight reduction in engine rpm during the second takeoff; however, that rpm reduction calculated to only a 10% loss in rate of climb. The significant reduction in climb performance while using nearly the same engine performance suggests the configuration of the motor glider had changed during the second takeoff. The airbrake paddles were not visible in the security video and were likely stowed. The motor glider was equipped with trailing edge flaps that had five settings; Flap 1 was a negative setting (-1.0°), Flap setting 4 provided 23° of extension, and the landing flap setting provided 38° extension. The Flight Manual stated that, during self-launch, the pilot should begin the takeoff with the most negative flap setting 1 and select Flap setting 4 at 27 knots for the remainder of the takeoff and climb. The Flight Manual provided a different flap configuration for take-offs on hard surfaces. It is possible that a misconfiguration of the flaps resulted in the motorglider’s poor climb performance during the second takeoff; however, the motorglider’s preaccident flap position could not be determined. .

Probable cause

Reduced takeoff performance for reasons that could not be determined, which resulted in a forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR24LA127
Event ID
20240422194128
Case number
WPR24LA127
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: 3e3ae3682857a8ccd8ff6b4621bfd23754f01c01e31d247fcc40aa6e09d5ed62; retrieved 2026-09-16T18:41:19.738Z.