ERA10LA317 · Cessna 401
Global Data Aviation Cessna 401 · Accident: fuel starvation on approach
From Plymouth Municipal Airport (PYM) to Plymouth Municipal Airport (PYM)
Event
- NTSB case
- ERA10LA317
- 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 401
- Aircraft type
- Cessna 401
- 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
- N401TE
- Operator
- Global Data Aviation
- Onboard fatalities
- Unknown
- Route
- From Plymouth Municipal Airport (PYM), Plymouth, MATo Plymouth Municipal Airport (PYM), Plymouth, MA
- 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
- Approach · VFR pattern final
- 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 › Fluids/miscellaneous hardware
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The airplane was returning from a 3-hour aerial mapping mission and was lined up for a straight-in, 5-mile final approach for landing. About 3 miles out on final approach, and prior to performing the before-landing check, both engines stopped producing power in sequence, one almost immediately after the other. The pilot said that by the time he completed his remedial actions the airplane had descended to about 200 feet above the ground and the engines would not restart. The auxiliary fuel tank gauges were bouncing between 2-5 gallons and the main tanks were bouncing around at 25 gallons per side. The pilot then selected a forced landing site between two large trees and landed the airplane in heavily wooded terrain. A detailed examination of the wreckage revealed no evidence of preimpact mechanical anomalies. According to information contained in the aircraft manufacturer’s owner's manual, the auxiliary fuel tanks are designed for cruising flight and are not equipped with pumps; operation near the ground (below 1000 feet) using auxiliary fuel tanks is not recommended. The first step in the before-landing check was to select the main fuel tanks on both the left and right fuel selectors, respectively. The pilot indicated that he should have selected the main tanks sooner and performed the before-landing check earlier in the approach.
Probable cause
A total loss of engine power during final approach due to fuel starvation as a result of the pilot’s delayed configuration of the airplane for landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10LA317
- Event ID
- 20100621X04325
- Case number
- ERA10LA317
- 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: 5abec0b5f80ea7794d1201ef60c101b6e65b5f56741c607844d6102975b25983; retrieved 2026-09-15T14:28:14.366Z.