Fuel Selector Oversight on Descent
A single fuel tank, a descent to land, and the moment you realize the tank you selected is empty — decision-making under pressure in a light, slippery airframe
The scenario
Departing Zephyrhills Municipal Airport (KZPH), Zephyrhills, FL — Runway 19, a 50-minute local flight in the Diamond DA20-C1. Elevation 90 ft MSL. The day is clear, winds light, visibility unlimited. A textbook VFR afternoon.
You are a Private pilot with roughly 180 hours total time, 40 hours in the DA20. You completed the preflight this morning: fuel quantity visually verified in the single fuel tank — the fuel selector is ON, and the tank appeared full (or very close). You did not top off because the previous flight was short and you assumed the fuel level was adequate for today's local flight.
You are now on descent from 2,500 ft MSL, 8 nm northeast of KZPH, heading 180° toward Runway 19. The descent is routine. You are at 1,500 ft MSL, 5 nm out, planning a standard left downwind for Runway 19. The engine is running smoothly. Fuel quantity is not on your mind — you have been flying for 50 minutes and have not been monitoring fuel burn closely.
Aircraft: Diamond DA20-C1, solo, single fuel tank with ON/OFF selector (no left/right tank management). Continental IO-240-B, fuel-injected, fixed-pitch prop, fixed gear, steam panel. The DA20 is a light, slippery airframe — it floats in ground effect and is sensitive to gusts. The castering nosewheel requires differential braking for directional control on rollout.
Pilot: you — current, 180 hours total, 40 hours DA20. You did not visually verify fuel quantity before descent. You did not calculate fuel burn or estimate remaining fuel. You are focused on the approach.
- {'label': 'Field', 'value': 'KZPH · Zephyrhills'}
- {'label': 'Runways', 'value': '19/1 · 5/23'}
- {'label': 'Elevation', 'value': '90 ft'}
- {'label': 'Aircraft', 'value': 'DA20'}
- {'label': 'Dominant phase', 'value': 'Landing / Cruise'}
The decision
Before we get into the decision tree — what do you already know about fuel management in the DA20-C1? (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, requiring a forced landing that struck a dirt berm. The probable cause was inadequate fuel management and failure to verify fuel quantity before flight.
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, leading to fuel starvation and a forced landing on a road. The pilot did not visually verify fuel quantity before departure.
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 did not calculate fuel burn or monitor fuel status.
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 monitoring and failure to switch tanks proactively before starvation symptoms appeared.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Zephyrhills Municipal Airport. KZPH has its own accident history (forced landing and loss-of-control incidents are the dominant patterns), but these specific fuel-starvation events happened elsewhere. The scenario is localized to KZPH 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. It requires three steps: (1) visual verification of fuel quantity during preflight, not reliance on gauges; (2) calculation of fuel burn and remaining fuel before descent; (3) continuous monitoring of fuel status during flight. The DA20's single fuel tank with ON/OFF selector eliminates the risk of mis-selection (left/right tank confusion), but it does not eliminate the risk of exhaustion. Knowing how much fuel you have is the entire lesson.
Key lesson — In the DA20-C1, fuel starvation is a total-power-loss event with no warning. The single fuel tank and ON/OFF selector eliminate mis-selection risk, but they do not eliminate exhaustion risk. Always visually verify fuel quantity during preflight — do not rely on the fuel gauge. Calculate fuel burn before descent and monitor fuel status continuously. At 1,500 ft on approach, a fuel starvation event leaves you 8–10 minutes of glide time at best glide (73 KIAS) — enough to reach the airport if you act immediately. Delay diagnosis or poor glide management will cost you the runway.
Debrief — teaching points
Fuel starvation in a fuel-injected engine is a sudden, total power loss — not a gradual roughness.
The DA20's Continental IO-240-B is fuel-injected; it has no carburetor and no carb-ice risk. Fuel starvation in a fuel-injected engine shows as a sudden drop to idle, not engine roughness or a gradual power loss. There is no warning. The first symptom is the power loss itself. This is why preflight fuel verification and continuous fuel monitoring are non-negotiable — you cannot rely on an engine symptom to warn you.
Visual verification of fuel quantity during preflight is mandatory — fuel gauges are unreliable.
The DA20 has a single fuel tank with a fuel gauge. Fuel gauges are notoriously inaccurate, especially at low fuel levels. The only reliable method is to visually verify the fuel level in the tank during preflight. Open the filler cap, look at the fuel level, and confirm it is where you expect it to be. Do not assume the previous flight left adequate fuel. Do not rely on the gauge. See the fuel with your eyes.
Calculate fuel burn before descent — know how much fuel you have remaining.
The DA20's Continental IO-240 burns roughly 5–6 gallons per hour at cruise. Before you begin descent, calculate how much fuel you have burned and how much remains. If you departed with a full tank (roughly 20 gallons usable) and have been flying for 50 minutes, you have burned roughly 4–5 gallons and have 15–16 gallons remaining. That is adequate for a local flight. But if you did not top off and the tank was not full at departure, your remaining fuel is lower. Know the number before you descend.
Best glide speed in the DA20 is 73 KIAS — establish it immediately on engine failure.
If the engine fails at altitude, establish 73 KIAS best glide immediately. This speed maximizes glide distance and gives you the most time and distance to reach an airport or suitable landing site. At 1,500 ft MSL with a dead engine, 73 KIAS best glide gives you roughly 8–10 minutes of glide time — enough to cover 5+ nm and reach KZPH. Deviating from best glide (climbing, descending steeply, or flying too fast) reduces your glide distance and options.
The DA20 is a light, slippery airframe — it floats in ground effect and is sensitive to gusts.
The DA20 is a composite, low-wing trainer with a bubble canopy. It is light and slippery, which means it floats in ground effect and is sensitive to wind gusts. On approach, maintain Vref (55 KIAS) and be prepared for the airplane to float down the runway. The castering nosewheel requires differential braking for directional control on rollout — do not rely on nosewheel steering alone. Understand the airplane's handling characteristics before you need them in an emergency.
Off Runway 19 at KZPH, the off-field environment is marginal — open developed areas, parks, and evergreen forest.
The off-field environment off Runway 19's departure end (heading 180°) is marginal — mostly open developed areas, parks, and evergreen forest. If you undershoot on approach, you will impact in that environment. It is survivable, but it is not ideal. Runway 01 (heading 360°) has a better off-field environment (pasture/hay, open developed areas). If you have a choice of runways and are in doubt, choose the one with the better off-field environment.
Built from the real accident record
Scenario inspired by NTSB WPR24LA167 (2024 Harvard fuel starvation / tank selection), GAA19CA534 (2019 PA-28 fuel tank mismanagement / forced landing), DFW05CA087 (2005 Cessna fuel starvation / approach power loss), and ERA17LA205 (2017 Cessna post-maintenance fuel mismanagement). Localized to KZPH.
NTSB reports: WPR24LA167 · GAA19CA534 · DFW05CA087 · ERA17LA205
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors · PA.II.A — Preflight Assessment
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 KZPH