FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24LA235 · Temco/Lazier TT-1

31 May 2024 · Laurel Hill, FL, United States

Temco/Lazier TT-1 · Accident: fuel starvation en route

From Tuscaloosa National Airport (TCL) to Bob Sikes Airport (CEW)

Report a problem

Event

NTSB case
ERA24LA235
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

Temco/Lazier TT-1

Aircraft type
Temco/lazier TT-1
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
N4486L
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tuscaloosa National Airport (TCL), Tuscaloosa, ALTo Bob Sikes Airport (CEW), Crestview, FL
Aircraft age
About 67 years (built 1957)
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 · descent
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 starvation
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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot of the vintage jet trainer airplane reported that he departed on a cross-country positioning flight with a reported full fuel load of 224 gallons. After uneventful ground operations, takeoff, and departure, he climbed to a cruise altitude of 12,500 ft. About 33 minutes into the flight, he began his descent to the destination airport. About 6 minutes after he began his descent, the pilot observed the “FUEL PRESSURE LOW” annunciator illuminate in the cockpit. He stated that he immediately verified the electric fuel boost pump was On and the switches for fuel transfer from the tip tanks to the main tanks were both in the On position. The engine subsequently flamed out, and his attempts to restart it were unsuccessful. Unable to glide to his destination, the pilot performed a forced landing in a field. The airplane contacted a barbed wire fence and uneven terrain during the landing, resulting in substantial damage to the airframe.

Examination of the engine after the accident revealed no evidence of case rupture or fluid leakage. The engine was twice rotated using the battery-powered starter, for about 10 seconds; the spool-up sounded normal, and no unusual engine noises were noted. About 33 gallons of fuel was found in the left tip tank and about 40 gallons in the right tip tank, although some fuel leakage was possible after ground impact. About 30 gallons of fuel was recovered from the main tanks after the accident.

The airplane’s fuel system was designed such that fuel transferred from the tip tanks to the main fuel tanks in the wings. The examination also revealed that the fuel transfer switches in the cockpit were found in the On positions. Pilots were advised to burn 60 gallons from the main tanks before turning the transfer pumps on. However, there were no fuel quantity indicators installed for the main tanks, so fuel burn had to be estimated based on power demand. The average fuel burn during the accident flight was estimated to be about 222 gallons per hour based on data recovered from a fuel flow indicator installed in the airplane. Based on the 224 gallons of fuel in the main tanks at the start of the flight, the time spent in flight (including taxi, takeoff, and climb), the airplane’s average fuel burn rate during the flight of 222 gallons per hour, and the 80-gallon-per-hour fuel transfer rate from the tip tanks to the main tanks, the pilot likely delayed turning the fuel transfer switches on after takeoff, which allowed fuel to burn from the main tanks faster than it could be transferred from the tip tanks to the main tanks. The engine then flamed out due to an inadequate supply of fuel in the main tanks. The reason that fuel was found in the main tanks after the accident was because the battery-powered fuel transfer pumps continued to operate after the engine flamed out.

Probable cause

The pilot’s delay in turning on the fuel tip tank transfer pumps after departure, resulting in fuel starvation to the engine, engine flameout, and a subsequent forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24LA235
Event ID
20240601194358
Case number
ERA24LA235
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: local date, investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2024-06-01.
  • API snapshot SHA-256: db27d4422c863b600f8d75ed9026a0f1b4afe00e3428951cb6abf1bac976063f; retrieved 2026-09-16T18:49:32.934Z.