FTW82DA259 · Cessna 310Q
Ansley Paper Cessna 310Q · Accident: total loss of engine power (non-mechanical) while maneuvering
From Graham, TX to Quanah, TX
Event
- NTSB case
- FTW82DA259
- 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
Cessna 310Q
- 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
- N7692Q
- Operator
- Ansley Paper
- Onboard fatalities
- Unknown
- Route
- From Graham, TXTo Quanah, TX
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- Total loss of engine power (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. 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
- Fluid, fuel › Starvation
- Pilot in command › Fuel supply, misjudged
- Pilot in command › Preflight planning/preparation, inadequate
- Pilot in command › Unsuitable terrain or takeoff/landing/taxi area, selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHEN THE PILOT ARRIVED IN THE VICINITY OF HIS DESTINATION, HE LOWERED THE GEAR AND FLAPS AND DLEW OVER AN OIL RIG. HE DID THIS TO ALERT SOMEONE ON THE GROUND TO PICK HIM UP AT THE DESTINATION. AS HE APPLIED POWER TO PROCEED TO THE AIRPORT, THE LEFT ENGINE DID NOT RESPOND. HE REPORTED THAT THE ENGINE ACTED LIKE THE FUEL HAD BEEN CUT OFF. HE SAW A ROAD AHEAD AND ELECTED TO LAND AS HE WAS AFRAID THE OTHER ENGINE WOULD LOOSE POWER. DURING THE LANDING, THE LEFT TIP TANK STRUCK A TREE. THE AIRCRAFT THEN VEERED INTO A DITCH AND THE NOSE GEAR COLLAPSED. THE PILOT STATED THAT HE DID NOT SERVICE THE PLANE BEFORE TAKEOFF. HE ESTIMATED THAT 50 GALLONS WAS ON BOARD DURING DEPARTURE. THE ONE HOUR AND 25 MINUTE FLIGHT WOULD HAVE REQUIRED ABOUT 280 LBS OF FUEL. THE PILOT REPORTED NO MECHANICAL MALFUNCTION OR FAILURE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW82DA259
- Event ID
- 20020917X03336
- Case number
- FTW82DA259
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: a4dffc96e50b3bd4fef9312a7a8f5f6eae0fbb4a7db8d2fa23f8a075679ba2a5; retrieved 2026-09-24T02:42:58.010Z.