17 Nov 2023: LANCAIR IV P

17 Nov 2023: LANCAIR IV P (N37MB) — Unknown operator

No fatalities • Perry, FL, United States

Probable cause

A rapid throttle advancement after a period of idling, which resulted in a flooded engine and total loss of engine power.

— NTSB Determination

Accident narrative

On November 17, 2023, about 1708 eastern standard time, an experimental amateur-built Lancair IV-P, N37MB, was substantially damaged when it was involved in an accident near Perry, Florida. The pilot sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to the pilot, he was in cruise flight at 11,500 ft msl with about 40 minutes of daylight remaining when he noted that a ceiling had developed below him. Accordingly, he decided to descend through a hole in the cloud layer and divert to Perry-Foley Airport (FPY), Perry, Florida. When the airplane levelled off under the cloud layer at 2,000 ft msl, he pushed in the throttle but “nothing happened.” The propeller was windmilling, and he thought the fuel-injected engine was at idle power. After several seconds, he pulled the throttle fully out expecting the engine to slow, but the engine power remained unchanged at the low-power setting. Realizing he had lost engine power, the pilot switched fuel tanks and enrichened the mixture; however, he was unable to restore power to the engine. He chose to execute a forced landing and considered landing on a road but believed that he could not slow the airplane enough to make a safe landing, so he landed straight ahead into sapling pine trees. The airplane nosed over and sustained substantial damage to the wings and fuselage; the pilot exited the airplane unassisted. Postaccident examination of the airframe and engine revealed that the fuel strainer contained fuel with a color and odor consistent with 100LL Avgas. There were no signs of debris or water contamination in the retrieved fuel sample. The fuel strainer bowl was removed, and the fuel strainer screen was clear of any contamination. The throttle, mixture, and propeller controls were secured in the cockpit and at their respective control arms at the engine. The crankshaft was rotated by hand and continuity was established between the crankshaft, camshaft, connecting rods, and associated components. All six cylinders displayed good thumb compression and suction. Examination of the engine and airframe fuel system revealed no anomalies; therefore, a determination was made to ship the engine to the manufacturer for an engine test run. At the manufacturer’s facility, the engine was prepared to run in the test cell. The oil sump was impact damaged and was replaced for testing. A fracture was observed on the No. 2 turbocharger exhaust where it had been previously welded. No determination could be made as to whether this was impact-related damage. The magneto-to-engine timing was confirmed to be within specification. A replacement propeller was installed on the engine. The engine started without hesitation in the test cell and ran at idle for 5 minutes, followed by subsequent 5-minute runs at each of the following rpm settings: 1200,1600, 2100, 2450, and then again at idle. Although the engine ran normally at all rpm settings, the engine test run revealed that the fuel system was set too lean, and the manifold pressure was about 2 inches of mercury lower than that required to produce rated power. Following these static engine runs, the engine was brought to idle and then the throttle was rapidly advanced. This sequence was repeated several times, and when the throttle was advanced quickly, the engine ran very rich with black exhaust smoke, and then would falter. If the throttle was not immediately retarded, the engine lost power completely. If the engine was immediately brought back to idle after it faltered upon rapid throttle advancement, the engine regained power.

Contributing factors

  • Engine fuel and control

Conditions

Weather
VMC, wind 359/06kt

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.