Larry'S Flying Service Cessna 207 accident
Cessna 207 · Accident: total loss of engine power (non-mechanical) en route
From Fort Yukon Airport (FYU) to Fairbanks International Airport (FAI)
Event
- NTSB case
- ANC89FA119
- 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
- Charter & commuter
- 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 207
- Aircraft type
- Cessna 207
- 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
- N91052
- Operator
- Larry'S Flying Service
- Onboard fatalities
- Unknown
- Route
- From Fort Yukon Airport (FYU), Fort Yukon, AKTo Fairbanks International Airport (FAI), Fairbanks, AK
- 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 135: Air Taxi & Commuter
- 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; Tree(s)
- 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 › Planning/decision, improper
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
THE PLT RPRTD THAT BEFORE REACHING HIS DESTN, THE ENG LOST POWER OVER WOODED MOUNTAINOUS TERRAIN. HE TURNED THE ACFT BACK TO LAND DOWNWIND ON A SANDBAR, BUT OVERSHOT & TOUCHED DOWN IN WILLOWS. HE STATED THAT EARLIER, HE HAD FULLY SVCD THE PLANE & FLOWN IT 1 HR. HE CALCULATED THERE WAS 4 HRS OF FUEL REMAINING & THE FLT SHOULD HAVE TAKEN ONLY 2 HRS & 40 MIN. DRAINING OF THE FUEL TANKS AFTER THE ACDNT REVEALED THERE WAS 5 GAL IN THE LEFT WING TANK & LESS THAN 1 PINT IN THE RGT TANK. ACCORDING TO THE FLT MANUAL, THIS LEFT ONLY 1.5 GAL OF USABLE FUEL. THE PLT RPRTD THERE WAS LIGHT TURBC DURING THE FLT. CALCULATIONS REVEALED THE ACFT NEEDED AN ADNL 5.4 GAL OF FUEL TO COMPLETE THE FLT.
Probable cause
IMPROPER PLANNING/DECISION BY THE PILOT, WHICH RESULTED IN FUEL STARVATION. FACTORS RELATED TO THE ACCIDENT WERE: INACCURATE FUEL CONSUMPTION CALCULATIONS, INADEQUATE FUEL SUPPLY, TURBULENCE, TAILWIND, TERRAIN CONDITIONS, AND TREES (WILLOWS) IN THE EMERGENCY LANDING AREA.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC89FA119
- Event ID
- 20001213X28692
- Case number
- ANC89FA119
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1989-07-11.
- API snapshot SHA-256: 1be93026d95cac012266acc696515744b3d43cd42757adb5414024f18fa9a3c6; retrieved 2026-09-18T19:10:22.302Z.