CHI04CA252 · Cessna T310R
Cessna T310R · Accident: total loss of engine power (non-mechanical) en route
From Fitch H Beach Airport (FPK) to Watertown Regional Airport (ATY)
Event
- NTSB case
- CHI04CA252
- 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 T310R
- 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
- N5005J
- Operator
- Maurice H. Dowding · private individual
- Onboard fatalities
- Unknown
- Route
- From Fitch H Beach Airport (FPK), Charlotte, MITo Watertown Regional Airport (ATY), Watertown, SD
- 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
- En route · cruise
- 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 tank selector position, not verified
- Pilot in command › Unsuitable terrain or takeoff/landing/taxi area, encountered
- Pilot passenger › Fuel tank selector position, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane sustained substantial damage during a forced landing following a loss of engine power during cruise flight. The pilot stated in a telephone interview that during the flight, a pilot-rated passenger was handling radio communications and also handling some flying duties. He stated that he believes that the pilot-rated passenger inadvertently switched the fuel selectors so that both engines were using fuel from the right main fuel tank. He said that he believes that this occurred when the pilot-rated passenger was attempting to switch the fuel tanks from the auxiliary fuel tanks back to the main fuel tanks. He stated that later in the flight both engines stopped producing power. The pilot stated that he switched fuel tanks and was able to re-start the left engine, but could not get the right engine to restart. He said that he was unable to maintain altitude and elected to land on a gravel road. The pilot said that the road was narrow and the left landing gear went off of the road. The airplane subsequently went off of the left side of the road and into a bean field. The pilot stated that during the attempts to restart the right engine, the propeller was not placed in the feather position. He stated that he was the pilot in command of the flight and that he was seated in the left seat of the airplane. The pilot did not report any malfunction of the airplane or it's systems.
Probable cause
The pilot rated passenger selecting an improper fuel selector position, and the pilot in command not verifying the fuel selector position which resulted in fuel starvation. Contributing factors were the pilot's failure to feather the right engine propeller during the emergency, the unsuitable terrain encountered during the landing, and the crop.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI04CA252
- Event ID
- 20041012X01613
- Case number
- CHI04CA252
- 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, 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: c1e4756cede4bf5aa3555cdff4bb401a5cc84d682617d82c0b36408308b02a56; retrieved 2026-09-22T06:46:33.890Z.