Power Loss on Short Final — Fuel Selector Verification
Engine failure from fuel starvation in a single-tank DA20 on approach to Tampa Executive — the decision window is seconds
The scenario
Departing Tampa Executive Airport (KVDF), Tampa, FL — Runway 23, a 5,000 ft asphalt runway. Elevation 22 ft MSL. You are on a local VFR flight in a Diamond DA20-C1, a light, fuel-injected two-seater with a single fuel tank and an ON/OFF selector. The field is non-towered (CTAF); you are in Class G airspace below 3,000 ft MSL. Above 3,000 ft MSL, you are in the overlying Tampa Class B airspace (ceiling 10,000 ft MSL).
It is a clear, calm Florida afternoon: OAT 26°C, altimeter 29.98, winds calm. Visibility 10+ SM. You departed KVDF at 1330 local on a 45-minute local flight — a climb to 2,500 ft MSL, a cruise around the Tampa Bay area, and a return to KVDF. The flight plan was simple: stay below the Class B, remain VFR, and return by 1500.
You are now on short final for Runway 23, 2 nm out, descending through 800 ft AGL. The runway is in sight. You have been in the air for 42 minutes. The fuel quantity indicator on the panel shows approximately 1/4 tank remaining — you expected this; you departed with 3/4 tank and burned roughly 5 gallons per hour in cruise. You are on a stable descent at 55 KIAS (Vref, approach speed), flaps at landing position (78°), and the engine is running smoothly.
Aircraft: Diamond DA20-C1, solo, within limits. Continental IO-240-B fuel-injected engine, fixed-pitch prop, fixed gear, single fuel tank with ON/OFF selector. The fuel selector is currently in the ON position — or so you believe. You did not visually verify the fuel selector position during the preflight walk-around; you assumed it was correct from the previous flight.
Pilot: you — a Private pilot, current, roughly 180 hours total. You have 12 hours in the DA20. This is your second local flight in the airplane. You are familiar with the single-tank fuel system and the ON/OFF selector, but you have not yet internalized the discipline of verifying the selector position on every flight.
- {'label': 'Field', 'value': 'KVDF · Tampa Executive'}
- {'label': 'Runways', 'value': '5/23 · 18/36'}
- {'label': 'Elevation', 'value': '22 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 ERA12FA002 (2011): A Temco GC-1B Swift experienced total loss of engine power over the Chesapeake Bay and ditched in the water. The accident resulted from the pilot's improper fuel management — specifically, the pilot did not verify the fuel selector position before flight or after the power loss, resulting in fuel starvation. The pilot did not survive. The probable cause was fuel starvation due to improper fuel selector positioning.
NTSB ANC17LA043 (2017): A Cessna T207 on a Part 135 scheduled commuter flight lost all engine power during approach due to fuel starvation and made a controlled ditching near Coghlan Island, Alaska. The accident resulted from total loss of engine power due to fuel starvation, with contributing factors including unreliable fuel quantity indicators and a company history of fuel management issues. The crew survived the ditching.
NTSB LAX98LA168 (1998): A Cessna T210M ditched in the Pacific Ocean 2 miles south of Santa Barbara after engine failure on final approach. The accident resulted from the pilot's mismanagement of fuel through improper fuel tank selector positioning. The pilot did not survive.
The common thread: in all three accidents, the fuel selector was not in the correct position, and the pilot either did not verify it during preflight or did not check it immediately after the power loss. In the DA20, with a single fuel tank and an ON/OFF selector, the risk is simpler than in multi-tank airplanes — there is no left/right management — but the discipline is the same: verify the selector position on every flight.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Tampa Executive Airport (KVDF). KVDF has its own accident history (see field dominant patterns: loss of control ground, hard landing, forced landing), but these specific fuel-starvation events happened elsewhere. The scenario is localized to KVDF to make the off-field environment real and consequential for you as a student here.
Off Runway 36's departure end at KVDF, the off-field environment is open water — a forced landing there is a ditching, not a field landing. Off Runway 23's departure end, the environment is pasture/hay and medium development — better options, but still off-field. The runway is always the preferred landing surface. Verify the fuel selector before engine start, and if power is lost, check the selector immediately.
Key lesson — In the DA20, the fuel selector position must be visually verified during every preflight walk-around — you cannot assume it is correct from the previous flight. If an engine failure occurs, the fuel selector is the first thing to check. The fuel quantity indicator is an electrical float gauge and can be unreliable; a visual dipstick check is the gold standard. Fuel starvation from selector mismanagement is the primary fuel-system risk in a single-tank airplane. The decision window on approach is seconds — check the selector before engine start, and if power is lost, check it immediately.
Debrief — teaching points
The fuel selector position must be visually verified during every preflight walk-around.
Do not assume the fuel selector is in the correct position from the previous flight. The DA20 has a single fuel tank with an ON/OFF selector on the left side of the cockpit. During the preflight walk-around, visually inspect the selector and confirm it is in the ON position. Make it a habit: touch the selector, confirm its position, and move on. This takes 5 seconds and prevents fuel starvation.
Fuel starvation in a fuel-injected engine shows as a sudden, complete power loss — not a gradual roughness.
The DA20's Continental IO-240-B is fuel-injected; it has no carburetor. If the fuel selector is OFF or the fuel tank is empty, the engine will lose all power suddenly — no warning, no roughness, just a dead engine. This is different from carburetor ice, which builds gradually. Recognize the symptom: sudden total power loss = fuel starvation until proven otherwise.
If the engine fails, check the fuel selector immediately — it is the most likely cause.
In the DA20, with a single fuel tank and an ON/OFF selector, fuel starvation from selector mismanagement is the primary fuel-system risk. If the engine fails, your first action is to check the fuel selector position. If it is OFF, switch it to ON immediately. The engine will restart. If it is ON and the engine does not restart, then you have a true fuel exhaustion or mechanical failure, and you proceed with the forced landing.
The fuel quantity indicator is unreliable — use a visual dipstick check as the gold standard.
The fuel quantity indicator on the panel is an electrical float gauge. It can be inaccurate, especially at low fuel levels. Before every flight, physically inspect the fuel tank with a dipstick or visual check through the filler cap. Know the actual fuel quantity, not just what the gauge says. This is the gold standard for fuel planning.
Best glide speed in the DA20 is 73 KIAS — establish it immediately if power is lost.
If the engine fails, lower the nose to 73 KIAS best glide immediately. This speed maximizes glide distance and gives you the most time and distance to reach a landing surface. Do not try to stretch the glide by maintaining approach speed (55 KIAS / Vref); the descent angle will be steeper and you will lose altitude faster. 73 KIAS is the speed to fly.
The runway is always the preferred landing surface — off-field landings are a last resort.
If an engine failure occurs on approach and the runway is reachable, aim for the runway. The runway is long, smooth, and designed for landing. An off-field landing in pasture or soft ground is survivable, but the airplane may be damaged. If the runway is reachable, use it.
Off Runway 36 at KVDF, the off-field environment is open water — a forced landing there is a ditching.
The off-field environment off Runway 36's departure end (heading 360°) is open water — Hillsborough Bay. A forced landing there is a ditching, not a field landing. If an engine failure occurs on the Runway 36 departure, establish best glide at 73 KIAS, declare an emergency, and aim for the runway or a safe off-field landing to the east. Know the off-field environment before you depart.
Built from the real accident record
Scenario built from NTSB ERA12FA002 (2011 Luscombe fuel starvation / ditching), ANC17LA043 (2017 Cessna T207 fuel starvation / controlled ditching), and LAX98LA168 (1998 Cessna T210M fuel mismanagement / ditching). Anonymized and localized to KVDF (Tampa Executive Airport).
NTSB reports: ERA12FA002 · ANC17LA043 · LAX98LA168
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.II.B — Engine Starting / Systems Preflight · PA.III.C — Approach and Landing · PA.IX.C — Emergency Approach and Landing
Relevant FARs: §91.3 · §91.13 · §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 KVDF