FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN18FA030 · Temco GC 1B

10 Nov 2017 · Pineville, LA, United States

Temco GC 1B · Accident: fuel starvation while maneuvering

From Lake Water Wheel Airport (XS99) to Pineville Municipal Airport (2L0)

Report a problem

Event

NTSB case
CEN18FA030
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
1 · all aircraft and ground
Ground fatalities
Unknown
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 GC 1B

Aircraft type
Temco GC-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
N2363B
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lake Water Wheel Airport (XS99), Shepherd, TXTo Pineville Municipal Airport (2L0), Pineville, LA
Aircraft age
About 69 years (built 1948)
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
Maneuvering · low-altitude flying
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 › Aircraft systems
  • Aircraft › Fluids/miscellaneous hardware

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The airline transport pilot departed on a cross-country flight to relocate his newly-purchased airplane to his home state. A fixed-based operator employee at the airport reported that the pilot overflew the airport and requested verification that his landing gear were extended. The employee confirmed that they were down. After overflying the runway the airplane descended and impacted trees and terrain.

Another witness reported that after the low pass, the airplane started to climb and then turned right at an altitude of 250 to 300 ft above ground level. He added that as the airplane turned, its tail "wobbled," which he attributed to a loss of engine power. Then the nose pitched down before it descended below the tree line. The airplane separated into several pieces, and the forward fuselage and engine came to rest inverted behind the empennage.

The signatures on the propeller were consistent with little or no power at the time of the accident. A postaccident examination of the engine, airframe, and flight controls revealed no preimpact anomalies that would have precluded normal operations. Investigators were not able to ascertain why the pilot asked for verification of the landing gear position. The landing gear were found retracted in the airplane wreckage.

The airplane had been equipped with an aftermarket auxiliary fuel tank system; however, the system installed did not match the specifications of the supplemental type certificate (STC) identified in the maintenance logbooks or any other STC approved for the make and model of the airplane. The system had been installed about 9 years before the accident and before the pilot had purchased the airplane. The airplane had only flown about 4.5 hours since the fuel tanks were installed.

The auxiliary fuel tanks were not vented properly which could have resulted in a vacuum preventing fuel flow through the lines and to the engine. In addition, neither auxiliary fuel tank was equipped with a fuel pickup line inside of the tank. During a turn into the selected fuel tank it is possible that the fuel could unport resulting in fuel starvation and a loss of engine power.

The fuel selector valve was selected to the main tank which was empty; however, it is unknown what position change the pilot may have made following the loss of engine power. Evidence of fuel was found in the fuel lines and fuel pump following the accident. Although the amount of fuel onboard the airplane could not be determined, this evidence indicates there was likely sufficient fuel and that fuel exhaustion did not occur.

Given the configuration of the auxiliary fuel tanks, the engine likely lost power due to fuel starvation. This resulted from the unporting of the fuel due to the auxiliary fuel tank's improper configuration and occurred during the right turn the airplane entered after the low pass over the airport.

Probable cause

The loss of engine power due to fuel starvation, which resulted from the unporting of the fuel during a right turn due to the auxiliary fuel tanks' improper configuration.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN18FA030
Event ID
20171110X61056
Case number
CEN18FA030
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. 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: 280bc145797023153a280b8f8ccb5eb2a110c5e7b9ce8759dad41aee73907af6; retrieved 2026-09-15T06:24:45.496Z.