ERA17LA235 · Cessna T337 D
Cessna T337 D · Accident: fuel exhaustion while maneuvering
From Greenwood County Airport (GRD) to Greenwood County Airport (GRD)
Event
- NTSB case
- ERA17LA235
- 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
- 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
Cessna T337 D
- Aircraft type
- Cessna 337
- 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
- N337J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Greenwood County Airport (GRD), Greenwood, SCTo Greenwood County Airport (GRD), Greenwood, SC
- Aircraft age
- About 49 years (built 1968)
- 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
- 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
The flight instructor and private pilot, who did not have a multiengine rating, were conducting a familiarization flight in the centerline thrust, multiengine airplane. Following the preflight inspection, the instructor and the pilot believed that both fuel tanks were about 1/2 to 3/4 full. After practicing maneuvers uneventfully for about 30 minutes, the front engine lost all power. The instructor told the pilot to return to the departure airport; the rear engine was operating at this time. However, before reaching the airport, the rear engine lost all power. With insufficient altitude remaining to reach a runway, the pilot transferred control to the instructor, who then conducted a forced landing into trees.
Postaccident examination of the accident site revealed no smell of fuel, and only about 6 gallons of fuel (of a possible 131 gallons with all fuel tanks filled to capacity, 3 gallons of which were unusable) were recovered from both wing fuel tanks. Examination of both engines revealed no evidence of any preaccident mechanical malfunctions or failures that would have precluded normal operation. The four fuel quantity sender units (two for each main fuel tank) were removed and tested with an ohm meter. In the empty position, the left outboard fuel sender unit displayed a resistance value equal to an approximate 1/2-tank reading. The left and right inboard fuel sender units displayed a resistance value equal to an approximate full-tank reading. The right outboard fuel sender unit displayed inconsistent resistance readings throughout its range of travel.
The airplane manufacturer published a mandatory service bulletin (SB) about 18 years before the accident, which required inspection of the fuel quantity indicating system to verify that each fuel gauge indicated the accurate fuel amount. The SB also required that an initial inspection of the system be completed within 100 hours of operation and subsequent recurring inspections every 12 months. Examination of the airplane's maintenance logbooks revealed no evidence of compliance with the SB.
Given the lack of fuel found at the accident site and that postaccident examination of the engines revealed no mechanical issues, it is likely that the pilots did not adequately verify the quantity of fuel during the preflight inspection, in part due to erroneous fuel quantity indications provided by the fuel quantity indicating system, which resulted in fuel exhaustion and a subsequent loss of all engine power to both engines. The airplane operator's failure to comply with the SB precluded the pilots from being able to identify the fuel quantity in flight.
Probable cause
The pilots' inadequate preflight inspection, during which they failed to adequately verify the quantity of fuel, which resulted in fuel exhaustion, a subsequent total loss of power to both engines, and a forced landing into trees. Contributing to the accident were the erroneous fuel quantity displayed by the fuel quantity indicating system fuel sender units and the operator's failure to comply with a mandatory service bulletin addressing inaccuracies in the fuel quantity indicating system.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA17LA235
- Event ID
- 20170707X90818
- Case number
- ERA17LA235
- 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: b22f7bbebf6a1eb359703bccf437e4f5bb0f9d23fd01c91c9a33ebd141ad316a; retrieved 2026-09-16T05:31:01.693Z.