FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC07FA051 · Cessna 206

19 Jun 2007 · Homer, AK, United States

Cessna 206 · Accident: loss of engine power en route

From Seldovia Airport (PASO) to Homer Airport (PAHO)

Report a problem

Event

NTSB case
ANC07FA051
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
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 206

Aircraft type
Cessna 206
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
N72067
Operator
Unknown
Onboard fatalities
Unknown
Route
From Seldovia Airport (PASO), Seldovia, AKTo Homer Airport (PAHO), Homer, 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
Loss of engine power
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; Stall
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 › Airspeed(vs), not maintained
  • Pilot in command › 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 commercial pilot began her duty day by making three flights in another company airplane. Six minutes after parking the first airplane, she switched to the accident airplane, and departed on a round-robin flight that included 4 takeoffs and 3 landings. About 8 minutes after the last takeoff, she declared an emergency, and reported a loss of engine power. Ground witnesses, and the front seat passenger, heard the engine stop, restart for a moment, and stop again. The pilot made an emergency landing approach to a remote island beach. While maneuvering for landing, she banked sharply to the right, and the airplane stalled at low level, colliding with the ground in a right wing and nose low attitude. Examination of the airplane at the crash site by an FAA inspector revealed that the fuel selector was on the left fuel tank. The right wing fuel tank system appeared to have been breached. The left fuel tank system appeared to be intact, and contained about 1/2 gallon of fuel. The engine fuel manifold contained about a drop of fuel. The engine was placed on an engine test stand, where it produced full rated rpm. The accident airplane had been flown the previous day by another company pilot for about 72 to 90 minutes and then parked. The amount of fuel remaining in the airplane when it was parked is unknown. A company ramp employee said he saw the pilot with a fuel hose at the accident airplane, but the amount of fuel, if any, that the pilot put in the airplane is unknown. Also, that observation was 23 minutes before the pilot's time sheet indicated she landed in the first airplane. Consequently, the amount of fuel in the accident airplane when the pilot departed is unknown. The pilot flew the accident airplane about 41 minutes before her crash landing on the beach. The company does not require pilots to log the amount of fuel placed in each airplane before each flight. The airplane's owner's manual description of the procedure for engine restart, after running a fuel tank dry, states, in part: "To ensure a prompt engine restart in flight after running a fuel tank dry, switch to the tank containing fuel, and place the auxiliary fuel pump switch in the "HI" position momentarily (3 to 5 seconds) with the throttle at least 1/2 open. Excessive use of the "HI" position of the auxiliary pump can cause flooding of the engine as indicated by a short (1 to 2 second) period of power, followed by a loss of power. This can be detected by a fuel flow indication, accompanied by a lack of power. If flooding does occur, turn off the auxiliary fuel pump switch, and normal propeller windmilling should start the engine in 1 to 2 seconds." Due to the lack of fuel found in the left wing tank, the position of the fuel selector, and the absence of any mechanical problems with the engine, it is probable that the pilot inadvertently allowed the left tank to run dry, and was unable to restart the engine prior to the emergency landing. During the emergency landing, she allowed the airspeed to decay and stalled the airplane, adding to the severity of the crash.

Probable cause

A loss of engine power due to fuel starvation from the pilot's improper fuel selector positioning, and her failure to maintain adequate airspeed to preclude a stall. Contributing to the accident was an inadvertent stall.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC07FA051
Event ID
20070626X00811
Case number
ANC07FA051
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: fdb0820f7c88ca28d635e9dad9cd5bc02b5578851e771ca5be12431803815721; retrieved 2026-09-18T14:43:41.759Z.