ANC21LA033 · Cessna 140
Cessna 140 · Accident: fuel starvation on approach
From Homer, AK to an unrecorded destination
Event
- NTSB case
- ANC21LA033
- 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
- Event fatalities
- Unknown
- 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 140
- Aircraft type
- Cessna 140
- 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
- N77219
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Homer, AKTo not recorded
- Aircraft age
- About 75 years (built 1946)
- 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
- Substantial
Cause areas
- Aircraft › Aircraft systems
- 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 pilot reported that, after lining up on the final approach to landing and nearing the runway, he was unhappy with the approach, and elected to conduct a go-around. He applied full power, pushed in the carburetor heat, accelerated to 60 knots airspeed, and initiated a climb. When the airplane was about 100 ft above the treetops on the south end of the airport, the engine lost all power. He attempted to restart the engine but was not successful. The airplane touched down in an area of muskeg and bounced several times before it nosed over, sustaining substantial damage to the left lift strut.
The airplane Flight Manual, Power Plant Instrument, stated in part:
Fuel Quantity Gauge – Do not takeoff on a fuel tank less than ¼ full.
Examination of the wreckage by a mechanic found no anomalies to explain the loss of engine power and found the fuel selector placed to the right tank position. Although the right fuel gauge indicated less than 1/4 fuel, and the aircraft flight manual warned not to takeoff on a fuel tank less than 1/4 full, the fuel onboard at the time of the accident could not be determined due to the disposition of the wreckage. The airplane was equipped with 2 -12.5-gallon fuel tanks with left, right, or off, fuel selector positions.
According to a representative from the aircraft manufacturer, the fuel quantity limitation for takeoff was due to the location of the fuel pickup tubes in the fuel tanks. Fuel unporting was possible at takeoff and climb attitudes when the fuel was less than ¼ full. No markings were present on the fuel gauges to indicate a takeoff limitation when the fuel tank was less than ¼ full, which would be about 3.125 gal per fuel tank.
According to the operation manual for the airplane, a cruise power setting between sea level and 10,000 mean seal level would yield a fuel burn of about 4.2 gallons per hour. The pilot indicated that the 1.9-hour flight departed with 15 gallons of fuel and he performed numerous maneuvers during the flight. Flight track data showed the airplane’s altitude varied between 7,400 ft and 100 ft. A 4.2 gph fuel burn over a span of 1.9 hours equates to about 8 gallons of fuel burned, which would have left about 3.5 gal of fuel in each of the two wing fuel tanks if the fuel was used evenly between the two tanks.
Although a postaccident examination found some contaminates within the fuel system, the amount and size were not enough to cause a total loss of engine power. The temperature and dewpoint at the time of the accident placed the airplane on the edge of the regime for carburetor icing at glide power; however, carburetor icing is unlikely to have been an issue since the pilot applied carburetor heat during the approach to land. It is therefore likely that insufficient fuel remained for takeoff which resulted in unporting of the fuel pickups and a total loss of engine power.
Probable cause
The pilot’s mismanagement of fuel which resulted in fuel starvation and total loss of engine power during a go-around. Contributing to the accident was the improperly marked fuel quantity gauges that failed to indicate a fuel quantity takeoff limitation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC21LA033
- Event ID
- 20210427102986
- Case number
- ANC21LA033
- 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: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2021-04-26.
- API snapshot SHA-256: bd0f04bfc0e25ddf8fb8829a62dd6a83e63742528f40525b0ed71a25474fc488; retrieved 2026-09-16T13:59:21.799Z.