The U.S. aircraft register, updated daily
Accidents · NTSB CEN23LA182 · Final report

Loehle Acft CORP 5151 Mustang accident near Hector, Minnesota, May 11, 2023

On May 11, 2023 at about 5:10 pm local time, a 2001 Loehle Acft CORP 5151 Mustang, an amateur-built aircraft,, registered N91026, was substantially damaged in an accident during takeoff near Hector, Minnesota (Hector Municipal Airport). It was a flight test under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A total loss of engine power due to fuel starvation as a result of the pilot’s modifications to the fuel system. Contributing to the accident was the pilot’s decision to continue the takeoff despite observing lower than anticipated propeller rpm, his decision to delay his precautionary landing to allow another airplane to land, and his decision to conduct flight testing of the airplane following multiple modifications.

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

What the record shows

Date
May 11, 2023 · about 5:10 pm local time
Place
Hector, Minnesota · Hector Municipal Airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Loehle Acft CORP 5151 Mustang, built 2001, amateur-built
Registration
N91026 · no longer on the register · serial 5151-4863808
Damage
Substantial damage
Flight
Flight test · general aviation rules (Part 91)

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

The pilot of the experimental, amateur-built airplane overhauled the engine carburetor and modified the airplane’s fuel system with an additional fuel tank after removing the airframe ballistic parachute system. The pilot also adjusted the ground-adjustable propeller to attain an engine rpm of 6,200. The pilot then performed a static ground run of the airplane for about 28 minutes before attempting a test flight. During takeoff, with the newly installed fuel tank selected, the engine only attained 6,100 rpm and the pilot suspected that something was wrong. There was another aircraft close to the airport and the accident pilot radioed the other aircraft and notified the pilot of engine issues and asked for its position from the airport. The pilot of the other aircraft responded that they were about 3 miles from the airport. The accident pilot told the other aircraft to go ahead and land and that he would land behind him. As the accident pilot turned the airplane toward the runway, the engine lost total power and the airplane landed in a soft field about 250 ft short of the runway, resulting in substantial damage. The pilot stated that he thought the loss of engine power was the result of fuel starvation and that there may have been a problem with the vent of the newly installed fuel tank. Postaccident examination of the engine revealed that the front carburetor was not intact within its flange. The carburetor separation was likely due to impact forces during the accident that also damaged the engine cowl around the carburetor. There were no other mechanical anomalies noted during the examination. Though the pilot performed an extended engine runup before flight, the runup did not account for dynamic effects from aircraft velocity that may have been simulated by performing a high-speed taxi test to determine if the anticipated propeller speed could be attained. Also, the pilot attempted a test flight to encompass multiple system modifications and maintenance, contrary to proper flight testing by using a build-up and risk mitigating approach. Additionally, even though the pilot observed a propeller rpm that was lower than anticipated, he chose to continue the takeoff and delay the precautionary landing to allow for another airplane to land. It is possible that the pilot may have been able to land on the runway had he not chose to delay his landing.

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. Aircraft maintenance event during prior to flight
  2. Collision during takeoff/land during landing
  3. Fuel starvation during takeoff defining event

The NTSB's findings

  • Personnel issues › Task performance › Planning/preparation › (general) › Pilot
  • Personnel issues › Action/decision › Action › Delayed action › Pilot
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
  • Aircraft › Fluids/misc hardware › Fluids › Fuel › Not specified

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; single-engine sea; instrument: airplane; rotorcraft: helicopter
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: ctr
  • Injury: no injuries

The aircraft

  • Airframe total time: 117.1 hours
  • Last inspection: condition inspection, April 22, 2023
  • Seats: 1
  • Landing gear: fixed
  • Engine: Rotax 582 (piston); 65 hours total

The flight

  • Flight plan: none
  • Runway 12, 2,776 ft by 50 ft

Weather at the time

  • Light: daylight
  • Wind: from 140° at 5 knots
  • Visibility: 10 statute miles
  • Sky: scat at 1,400 ft
  • Temperature: 66°F (19°C), dew point 59°F (15°C)
  • Altimeter: 29.98 inHg
  • Observation at 11:55 am from OVL, 14 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

6 documents, released by the NTSB on March 28, 2024. 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.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.