Fuel Selector Confusion on Approach
A single fuel tank, a distracted descent, and the cost of not verifying fuel quantity before flight — power loss on short final at a non-towered field
The scenario
Departing Venice Municipal Airport (KVNC), Venice, FL — Runway 22, a 5,000-ft asphalt runway. Elevation 18 ft MSL. Non-towered field; you are operating on CTAF (122.8). The field is surrounded by open water to the west (Gulf of Mexico, roughly 2 nm), residential and light commercial development to the east and north, and open water and mangrove to the south. Runway 22's departure end (heading 225°) points toward open water and the Gulf.
It is a clear, VFR afternoon in late winter: OAT 22°C, winds light and variable, visibility 10 SM, scattered clouds at 3,500 ft. A routine local flight — you are planning a 1-hour round trip to a nearby field and back. The flight is within the DA20's range and your fuel planning.
You are on descent from 2,500 ft, 8 nm south of KVNC, heading 360° (northbound) toward the field. You are planning to enter a left downwind for Runway 22. The engine is running smoothly at 1,700 RPM. You have not yet switched the fuel selector — it has been in the ON position since preflight. You are distracted: you are reviewing the approach plate on your iPad, managing the descent, and monitoring the CTAF frequency for other traffic.
Aircraft: Diamond DA20-C1, solo, fuel quantity UNKNOWN. You did not visually verify the fuel quantity before departure — you relied on the fuel quantity gauge, which showed 'full' (or close to it). The DA20 has a single fuel tank with an ON/OFF selector. There is no left/right tank management, no crossfeed, no fuel pump. Gravity feed only. The fuel selector is currently ON.
Pilot: you — a Private pilot, current, roughly 250 hours total. You have flown the DA20 for about 40 hours. You are familiar with the fuel system in principle (single tank, ON/OFF selector), but you have not internalized the discipline of verifying fuel quantity by visual inspection before every flight. You have never experienced an engine-out emergency. You are confident, perhaps overconfident, in your ability to manage the flight.
- {'label': 'Field', 'value': 'KVNC · Venice'}
- {'label': 'Runways', 'value': '4/22 · 13/31'}
- {'label': 'Elevation', 'value': '18 ft'}
- {'label': 'Aircraft', 'value': 'DA20'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we get into the decision tree — what do you already know about fuel management in the DA20? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB WPR24LA167 (2024): A Canadian Car & Foundry Harvard MK IV lost all engine power due to fuel starvation when the pilot improperly selected the left fuel tank at low fuel levels. The accident resulted from improper fuel tank selection and a malfunctioning fuel selector. The pilot made a forced landing that struck a dirt berm. The probable cause was fuel starvation from improper tank management in a multi-tank aircraft.
NTSB GAA19CA534 (2019): A Piper PA-28 lost engine power during descent to land after the pilot switched to the left fuel tank and failed to follow the emergency power loss checklist. The accident resulted from improper fuel management and failure to switch to the right tank containing usable fuel. The pilot made a forced landing on a road. The probable cause was fuel starvation from inadequate fuel tank management during the critical descent phase.
NTSB DFW05CA087 (2005): A Cessna TU206G amphibian on a personal flight from Addison to Lancaster lost engine power during approach when the pilot switched fuel tanks. The accident resulted from fuel starvation attributed to the pilot's failure to visually verify fuel quantity before departure and inadequate fuel management during the approach. The pilot made a forced landing short of the runway.
NTSB ERA17LA205 (2017): A Cessna P206 on a post-maintenance break-in flight lost all engine power due to fuel starvation when the pilot mismanaged fuel selection and ran the right tank dry. The pilot made a forced landing in trees short of the runway after the engine quit during approach. The probable cause was inadequate fuel tank management and failure to establish a disciplined fuel management plan before flight.
The DA20-C1 differs from these multi-tank aircraft: it has a SINGLE fuel tank with an ON/OFF selector. There is no left/right tank switching, no crossfeed, no fuel pump — only gravity feed. The fuel starvation risk in the DA20 is purely from exhaustion (running the single tank dry) or selector position (OFF instead of ON). The discipline required is simpler but no less critical: visual fuel verification before every flight and awareness of fuel quantity during flight.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Venice Municipal Airport. KVNC has its own accident history (see field dominant patterns: LOSS_OF_CONTROL_INFLIGHT 24.4%, FORCED_LANDING 12.2%), but these specific fuel starvation events happened elsewhere. The scenario is localized to KVNC to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: fuel starvation is preventable. Visual fuel verification before departure — opening the filler cap and looking at the fuel level — is the only reliable way to confirm fuel quantity. Fuel gauges can be inaccurate. Relying on a gauge reading and skipping the visual check is the first step toward a fuel starvation accident. The DA20 makes this even simpler: one tank, one selector, one discipline. Do it every time.
Key lesson — In the DA20, fuel starvation comes from exhaustion or selector position — there is no tank-switching complexity. Visual fuel verification before every flight is non-negotiable. Open the filler cap and look at the fuel level. Do not rely on the fuel gauge. If fuel is low or uncertain, land and refuel or divert to a field with fuel. Off Runway 22 at KVNC, the departure end points toward open water and the Gulf of Mexico — an engine-out off that end is a ditching, not a field landing. Fuel discipline prevents this scenario entirely.
Debrief — teaching points
Visual fuel verification is the only reliable fuel check.
The DA20's fuel quantity gauge can be inaccurate. The only reliable way to confirm fuel quantity before flight is to open the filler cap and look at the fuel level in the tank. This takes 30 seconds. Skipping this step and relying on a gauge reading is the first step toward a fuel starvation accident. Make visual fuel verification a non-negotiable part of your preflight checklist — every flight, every time.
The DA20 has a single fuel tank with an ON/OFF selector — no tank switching, no crossfeed.
Unlike multi-tank aircraft (Piper PA-28, Cessna 206), the DA20 has one fuel tank and one selector. There is no left/right tank management, no crossfeed, no fuel pump. Fuel is delivered by gravity feed only. The fuel starvation risk is purely from exhaustion (running the tank dry) or selector position (OFF instead of ON). This simplicity is an advantage — but only if you maintain discipline: verify fuel quantity before flight, monitor fuel consumption during flight, and know your fuel reserves.
Fuel starvation on descent and approach is the classic accident pattern.
The NTSB precedents (WPR24LA167, GAA19CA534, DFW05CA087, ERA17LA205) show that fuel starvation accidents cluster in the descent and approach phase. Pilots are distracted by approach planning, descent management, frequency monitoring, and approach plates. They do not notice fuel quantity dropping. They do not verify fuel before the descent. By the time the engine sputters on short final, options are gone. Establish a fuel management discipline: verify fuel before descent, monitor fuel during descent, and be prepared to divert if fuel is marginal.
Best glide speed (73 KIAS) is the immediate response to engine failure.
When engine power is lost, immediately lower the nose to establish 73 KIAS best glide speed. This is the speed that maximizes glide distance and minimizes descent rate — both critical at low altitude. Do not try to climb, do not try to stretch the glide, do not push the throttle. Lower the nose, establish 73 KIAS, and look for the best landing option. At 250 ft AGL with 73 KIAS best glide, you have roughly 45–60 seconds of glide time — enough to make a runway or a field if you execute correctly.
Runway 22's departure end points toward open water — an engine-out off that end is a ditching.
Runway 22's heading is 225° (southwest). The departure end points toward open water and the Gulf of Mexico, roughly 2 nm away. The approach end is over open water and mangrove, but the runway itself is over land. If the engine fails on the Runway 22 departure at low altitude, the off-field environment is water — a ditching, not a field landing. If the engine fails on approach to Runway 22, the approach end is over water and mangrove. Know the off-field environment before you line up on any runway. At KVNC, Runway 13/31 has better off-field options (residential and light commercial development to the east and north) — consider runway selection based on engine-failure risk.
Fuel reserves are not optional — they are the margin between a safe flight and an accident.
If fuel is low or uncertain, land and refuel or divert to a nearby airport with fuel services. KSRQ (Sarasota-Bradenton) is 20.4 nm north of KVNC, a Class C airport with full fuel services. The decision to divert based on fuel uncertainty is conservative and correct. Fuel reserves are not a luxury — they are the margin that allows you to handle headwinds, go-arounds, and unexpected delays. Do not gamble with fuel.
Built from the real accident record
Scenario built from NTSB WPR24LA167 (2024 Harvard fuel starvation / tank selection), GAA19CA534 (2019 PA-28 fuel starvation on descent), DFW05CA087 (2005 Cessna TU206G fuel starvation / approach), and ERA17LA205 (2017 Cessna P206 fuel starvation / forced landing). Anonymized and localized to KVNC.
NTSB reports: WPR24LA167 · GAA19CA534 · DFW05CA087 · ERA17LA205
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.II.A — Preflight Assessment · PA.II.B — Engine Starting / Systems Preflight · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors
Relevant FARs: §91.3 · §91.13 · §91.151 · §91.185
Step through the full decision tree, make the calls, and see where each choice leads — then debrief it with your CFI.
Open the interactive scenario →All sample scenarios · More Diamond DA20-C1 scenarios · More scenarios at KVNC