FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN23FA173 · Cessna 310D

6 May 2023 · Ennis, TX, United States

Cessna 310D · Accident: fuel starvation on approach

From David Wayne Hooks Memorial Airport (KDWH) to Ennis Municipal Airport (F41)

Report a problem

Event

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

Cessna 310D

Aircraft type
Cessna 310
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
N6798T
Operator
Unknown
Onboard fatalities
Unknown
Route
From David Wayne Hooks Memorial Airport (KDWH), Houston, TXTo Ennis Municipal Airport (F41), Ennis, TX
Aircraft age
About 63 years (built 1960)
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
Approach · VFR go-around
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
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft power plant
  • Aircraft › Aircraft systems
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot was conducting a personal flight in a multiengine airplane with two passengers when the accident occurred. According to one of the passengers, the pilot chose to perform a go-around while on final approach; however, the reason for the go-around was not understood. The airplane side-stepped to the right of the runway and immediately rolled to the right. The airplane impacted a field of cedar trees, where a post-impact fire ensued and destroyed the airplane. Debris in the initial impact crater show that the right wing and right engine impacted the ground first. Both the left and right propellers exhibited chordwise/rotational scoring, which was consistent with both propellers rotating at impact; all damage was consistent with high impact forces. The left propeller exhibited damage consistent with rotation at a higher power level when compared to the right; however, the level of engine power could not be determined definitively from either propeller. Both propellers exhibited damage consistent with rotation at a low blade angle and neither was in a feathered position. There were no discrepancies noted that would preclude or degrade normal operation on either propeller. The left engine was examined and there were no preimpact mechanical failures or malfunctions that would have precluded normal operation. The right engine was run and initially ran rough. The fuel plug and screen assembly from the fuel injection control assembly was removed and black debris, small string-like fibers, and metallic particles were observed obstructing the screen. Analysis of the debris revealed polyurethane, and metallic particles of brass (zinc and copper) and aluminum. The brass and aluminum were most likely components of the fuel system. The flexible fluid-carrying hoses had not been replaced since 2001 and were prone to degradation if not replaced after 12 years. The polyurethane and string-like fibers were consistent with a flexible fluid-carrying hose. It is likely that the fuel hose from the fuel system degraded over time and plugged the fuel screen for the right engine which resulted in a partial loss of engine power. A review of the maintenance records did not indicate that the fuel plug and screen from the fuel injection control assembly were cleaned during the August 2022 annual engine inspection as recommended by both the Cessna Model 310D Maintenance Manual and Continental IO-470 Engine Operator’s Manual.

Probable cause

The partial loss of right engine power due to reduced fuel flow as a result of the contamination of the fuel screen.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN23FA173
Event ID
20230506114697
Case number
CEN23FA173
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, 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: a52dcb5b89f059548c41317c9f769ac63482a051aaa611ebf1ec3bd5eeb912e6; retrieved 2026-09-15T07:59:35.779Z.