11 May 2023: LOEHLE ACFT CORP 5151 Mustang — Pilot

11 May 2023: LOEHLE ACFT CORP 5151 Mustang (N91026) — Pilot

No fatalities • Hector, MN, United States

Probable cause

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.

— NTSB Determination

Accident narrative

On May 11, 2023, at 1210 central daylight time, an experimental, amateur-built 5151 Mustang, N91026, was substantially damaged when it was involved in an accident near Hector, Minnesota. The commercial pilot was uninjured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 test flight. According to a Federal Aviation Administration (FAA) inspector, the pilot, who was not the builder of the airplane, had recently overhauled the engine carburetors and modified the airplane’s fuel system. The overhaul of the carburetors and the fuel system modification were not recorded in maintenance records. When the pilot purchased the airplane, it was equipped with an airframe ballistic parachute, which he removed, and installed a fuel tank in its place. The pilot calculated that the weight of the parachute was equal to the weight of the fuel tank and 2 gallons of fuel. Before the accident flight, the pilot tied the tailwheel of the airplane to an anchor point and ran the engine at a high power setting for about 28 minutes to test the modifications he had made to the fuel system. He also adjusted the ground-adjustable propeller to obtain 6,200 rpm. After the ground run, he decided to test fly the airplane. During takeoff, with the newly-installed fuel tank selected, the engine only attained 6,100 rpm. He stated that suspected something was wrong. There was another aircraft close to the airport, so he radioed the other aircraft notifying the pilot of engine issues and asked the other aircraft for its position from the airport. The other aircraft responded that it was 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 toward the runway, the engine lost total power and the pilot was unable to glide the airplane to the runway. The airplane touched down in a soft field about 250 feet from the end of the runway. The accident pilot recovered the airplane and placed it in a hangar without the knowledge of or permission from the National Transportation Safety Board (NTSB) or FAA. The airplane sustained substantial damage that included damage to the wing rib and lower spar cap at left main gear attach point. Postaccident examination of the engine by an FAA inspector revealed that the front carburetor was out of its mounting flange and the clamp securing it was loose enough that the carburetor could be placed back in the flange and removed without loosening the clamp. A portion of the left side engine cowl, near the carburetor, was torn outward and aft due to impact forces during landing. There were no other engine anomalies noted during the examination. The pilot stated that he thought the loss of engine power was due to fuel starvation and that there may have been a problem with the vent of the newly installed fuel tank. An NTSB Pilot/Operator Aircraft Accident/Incident Report, form 6120, was not received from the pilot. The previous owner and builder of the airplane did not make the required logbook entry for completing Phase 1 flight testing; therefore, operation of the airplane was limited to the flight test area listed in the operating limitations of the airworthiness certificate (within 25 nautical miles of Bateman Field, Chippewa Falls, Wisconsin, excluding class C airspace). The accident flight occurred outside of the flight test area.

Contributing factors

  • Pilot
  • Pilot
  • Descent/approach/glide path — Not attained/maintained
  • Fuel

Conditions

Weather
VMC, wind 140/05kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.