Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

November 17, 2023 · Lancair IV P · N37MB

Perry, FL

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
November 17, 2023
Injury Outcomes
1 injury (1 minor injury)
Location
Perry, FL
Aircraft
Lancair IV P (1999)
Tail Number
N37MB
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
ERA24LA043

The pilot reported a loss of engine power after descending from 11,500 ft mean sea level (msl) and leveling off under a cloud layer at 2,000 ft msl. The pilot switched fuel tanks and enrichened the mixture; however, he was unable to restore engine power and elected to execute a forced landing during which he impacted trees. Postaccident examination of the airframe and fuel-injected engine revealed no anomalies that would have precluded normal operation. The engine subsequently started without hesitation during a test cell run at the manufacturer’s facility. After running at idle for 5 minutes, the engine was run for 5 minutes at various rpm settings. The engine test run revealed that the fuel system was mal-adjusted and set too lean, and the manifold pressure was about 2 inches of mercury lower than that required to produce rated power. This could have been due to an observed leak of the turbocharger exhaust or the sonic venturis which were open to the atmosphere for the engine test. Following these static engine runs, the engine was brought to idle and then the throttle was rapidly advanced. 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. This was consistent with the engine flooding with rapid throttle advancement after a period of idling. Given that no anomalies were noted in the examination and that the engine repeatedly stopped producing power after rapid throttle advancement after a period of idling in the test cell, it is possible that the speed with which the pilot advanced the throttle after leveling from the descent was too quick. The engine likely then would have flooded with fuel and stopped producing power, similar to the behavior observed during the postaccident test run.

NTSB Probable Cause

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

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

Flight

Event TypeAccident
Event Time17:08 EST
Nearest Airport0nm N
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftLancair IV P
Tail NumberN37MB
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsContinental · TSIO-550-E1B · Reciprocating · 350
Seats4

People & Injuries

Injury Summary1 injury (1 minor injury)
Fatal0
Serious0
Minor1
Uninjured0
Total1
Crew 1Age 45 · Third Class · Minor

Conditions

ConditionsVMC
LightDaylight
Wind359° @ 6 kt
CeilingOvercast 2300 ft
Temperature / Dew Point64 F
Altimeter29.83 inHg
Observation Time17:35
Weather SourceWFAC

Appendix: Source Data