The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB WPR24LA127 · Final report

Schleicher Alexander GMBH & CO ASH 26 E accident near Heber, Utah, April 21, 2024

On April 21, 2024 at about 9:30 pm local time, a 2000 Schleicher Alexander GMBH & CO ASH 26 E (glider), registered N644CC, was substantially damaged in an accident during initial climb near Heber, Utah (Heber Valley Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

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

Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.

What the record shows

Date
April 21, 2024 · about 9:30 pm local time
Place
Heber, Utah · Heber Valley Airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Schleicher Alexander GMBH & CO ASH 26 E, built 2000 · all ASH 26 Es on the register
Registration
N644CC · registry record · serial 26170
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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. .

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Unknown or undetermined during initial climb defining event
  2. Off-field or emergency landing during initial climb

The NTSB's findings

  • Aircraft › Aircraft power plant › Power plant › (general) › Unknown/Not determined
  • Environmental issues › Physical environment › Terrain › Rough terrain › Contributed to outcome
  • Aircraft › Aircraft oper/perf/capability › Aircraft capability › Climb capability › Attain/maintain not possible

Pilot

  • Certificate: private
  • Ratings: rotorcraft: glider
  • Flight time: 1,833 hours in all; 860 in this make and model; 3 in the last 90 days; 1 in the last 30 days; 1,793 as pilot in command
  • Last flight review: September 4, 2022
  • Medical certificate: None
  • Seat: sngl
  • Injury: no injuries

The aircraft

  • Airframe total time: 879.3 hours
  • Last inspection: annual inspection, April 13, 2024
  • Maximum gross weight: 1,158 lb
  • Seats: 1
  • Landing gear: retractable
  • Engine: Austro AE50 (type not recorded); 76 hours total

The flight

  • Flight plan: none
  • Runway 22, 6,898 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 210° at 7 knots, gusting 15
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 70°F (21°C), dew point 27°F (-3°C)
  • Altimeter: 30.11 inHg
  • Observation at 3:30 pm from KHCR, 1 miles away

Weather report (METAR): METAR KHCR 212135Z AUTO 21007G15KT 10SM SCT230 21/M03 A3011 RMK AO2 T02081030 $=

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

10 documents, released by the NTSB on March 12, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The documents and photographs are the NTSB's docket, the folder of records gathered during the investigation, shown as the NTSB released them (the NTSB redacts some personal details first) and listed under the NTSB's own titles. This site's own text never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number WPR24LA127.