FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA22LA200 · Titan T51 D

24 Apr 2022 · Perry, FL, United States

Titan T51 D · Accident: fuel exhaustion en route

From Lakeland Linder International Airport (LAL) to Quincy Municipal Airport (2J9)

Report a problem

Event

NTSB case
ERA22LA200
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Titan T51 D

Aircraft type
Titan T51
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N151CM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lakeland Linder International Airport (LAL), Lakeland, FLTo Quincy Municipal Airport (2J9), Quincy, FL
Aircraft age
About 2 years (built 2020)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Fuel exhaustion
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

According to the pilot, he topped off both wing fuel tanks about 2 weeks prior to the accident flight. The engine was ground run for about 10 minutes on the day after the fueling, after which the airplane was parked until the day of the accident flight. During the preflight inspection for the accident flight, the pilot sampled fuel from the fuel drains, but did not visually inspect the level of fuel in the fuel tanks, and assumed they were both full. About 1 hour into the flight, the engine started to “miss”, and the pilot then activated the fuel boost pump. The engine then ran normally for about 15 to 20 seconds before it began to “miss” again, until a few moments later when it lost all power. The pilot attempted to divert to a nearby airport, however during the approach he determined he would not reach the runway, and he selected a field for a forced landing. During landing the airplane struck trees, and a portion of the left wing separated about 3 ft outboard of the root. The airplane impacted terrain, came to rest inverted, and sustained additional substantial damage to the right wing, forward fuselage, horizontal stabilizer, and elevator. A Federal Aviation Administration inspector observed that both of the left wing fuel tanks were breached and that only a trace amount of fuel was found in the fractured left wing fuel line near the fuselage. The right wing fuel tanks remained intact but were inaccessible. The inspector reported, and the pilot confirmed, that there was no odor of fuel at the accident site.

Following the accident, pilot reported that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation prior to the accident. He concluded that although he believed the fuel tanks were full prior to departure, they likely were not, and he did not confirm the fuel level during the preflight inspection. The pilot further described that the airplane was equipped with fuel quantity gauges, however the gauges were located in the footwell for the rear seat, near but below his hips when seated in the front seat, and they were difficult to see from the front seat position. He added that the fuel quantity gauges were of limited use. Due to the wing dihedral, the gauges would indicate “full” until about 8-12 gallons had been used, and then read empty after using another 3-4 gallons. He had instead used the fuel computer/totalizer indications to reference fuel quantity. He had previously calibrated the totalizer by comparing its indications with fueling records several times and found it to be accurate. Given this information it is likely that the loss of engine power was the result of fuel exhaustion.

Probable cause

The pilot’s inadequate preflight inspection of the fuel quantity, which resulted in fuel exhaustion, a subsequent total loss of engine power, and an off-airport landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA22LA200
Event ID
20220425104991
Case number
ERA22LA200
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: d969b18caec245d8c162ca54235e99e07bf54d39705edc44b26864881fdb84a5; retrieved 2026-09-16T15:10:02.012Z.