Fuel State Surprise on Descent to Lakeland
Single fuel tank, descent to land, and a power loss that could have been prevented — fuel management discipline under pressure
The scenario
Departing Lakeland Linder International Airport (KLAL), Lakeland, FL — Runway 10, climbing out on a 90° heading. Elevation 142 ft MSL. You are returning from a 2.5-hour cross-country flight to a nearby field; the return leg is 1.2 hours. Fuel consumption in the Diamond DA20-C1 at cruise power is roughly 5.5 gallons per hour. Total usable fuel capacity is 19.5 gallons.
It is a clear, calm afternoon: OAT 24°C, altimeter 30.02, visibility 10+ SM. Light winds from the northeast. Class D airspace, KLAL tower is active 24 hours. You are at 2,500 ft MSL on descent to land, 8 nm northeast of the field, heading 225° inbound on a straight-in approach to Runway 10.
Aircraft: Diamond DA20-C1, solo, with a single fuel tank (ON/OFF selector only — no left/right management). The fuel selector is currently ON. The fuel gauge reads approximately 6 gallons remaining. You did not visually verify fuel quantity at preflight — you relied on the gauge from the previous flight. You did not calculate fuel burn or plan a tank-switching strategy because there is only one tank.
Pilot: you — a Private pilot, current, roughly 180 hours total. You are familiar with the DA20 but have not flown it extensively. You are focused on the approach and landing; fuel state is in the back of your mind. The descent is routine. The field is in sight. Everything feels normal.
At 1,200 ft MSL, 4 nm from the field on a 3° descent, the engine begins to lose power. The tachometer is unwinding. The manifold pressure is dropping. You have roughly 90 seconds of useful decision time before you must commit to a landing option.
- {'label': 'Field', 'value': 'KLAL · Lakeland Linder'}
- {'label': 'Runways', 'value': '5/23 · 10/28'}
- {'label': 'Elevation', 'value': '142 ft'}
- {'label': 'Aircraft', 'value': 'DA20'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we get into the decision tree — what do you 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 aircraft was on descent to land. The pilot had not verified fuel quantity visually before departure and relied on an inaccurate fuel gauge. The forced landing struck a dirt berm. The probable cause was improper fuel tank selection and failure to verify fuel quantity before flight.
NTSB GAA19CA534 (2019): A Piper PA-28-161 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 aircraft was on approach when the engine quit. The pilot did not switch to the right tank (which contained usable fuel) and instead attempted to troubleshoot in descent. The forced landing was on a road. The probable cause was improper fuel management and failure to execute the emergency power loss checklist.
NTSB DFW05CA087 (2005): A Cessna TU206G amphibian on descent to land lost engine power when the pilot switched fuel tanks. The pilot had not visually verified fuel quantity at preflight and relied on the gauge. The aircraft was on approach when the engine quit. The forced landing was short of the runway. The probable cause was fuel starvation attributed to failure to visually verify fuel quantity and inadequate fuel management during approach.
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 aircraft was on approach to land when the engine quit. The pilot made a forced landing in trees short of the runway. The probable cause was failure to establish and maintain fuel tank switching discipline during approach.
The DA20-C1 scenario at KLAL is localized to this field and this aircraft type. The real accidents cited above occurred at other airports and in other aircraft (Harvard, PA-28, Cessna TU206G, Cessna P206) — NOT at KLAL in a DA20. The teaching angle is the same: fuel quantity verification at preflight, fuel management discipline during descent and approach, and early declaration of an emergency when power is lost. The DA20-C1's single fuel tank eliminates the left/right mis-selection risk, but it does NOT eliminate the exhaustion/starvation risk. A fuel gauge that reads 6 gallons may be wrong. Visual verification is the only reliable check.
The consistent thread across all these events: pilots relied on fuel gauges instead of visual verification, delayed declaring emergencies when power was lost, and attempted to troubleshoot or stretch the glide instead of committing to a landing. In the DA20-C1, the single fuel tank simplifies the system, but it does not eliminate the need for fuel discipline. Know your fuel state before descent. Declare an emergency early. Land the airplane.
Key lesson — In the DA20-C1, fuel management is simple (single tank, ON/OFF selector) but critical. Fuel gauges are unreliable — visual verification at preflight is the only reliable check. Plan your fuel burn before flight and monitor fuel state continuously. If power is lost on descent, declare an emergency immediately and commit to a landing (runway or forced landing) rather than delay or troubleshoot. At KLAL, Runway 10 is 8,500 ft long and the off-field environment off the departure end is marginal — a forced landing there is survivable if you commit early and fly a controlled approach.
Debrief — teaching points
Fuel gauges in light aircraft are notoriously unreliable — visual verification is the only reliable check.
The DA20-C1 fuel gauge is mechanical and subject to error. A gauge that reads 6 gallons may be 2 gallons, or 10 gallons. The only reliable fuel quantity check is visual: open the fuel cap, insert a dip-stick or measuring rod, and read the actual fuel level. This must be done at preflight, before every flight. Do not rely on the gauge from the previous flight or the gauge reading at the start of this flight. Verify visually. The NTSB cases DFW05CA087 and ERA17LA205 both cite failure to visually verify fuel quantity as a contributing factor.
Plan your fuel burn before flight and monitor fuel state continuously during descent.
The DA20-C1 burns roughly 5.5 gallons per hour at cruise power. Total usable fuel is 19.5 gallons, giving roughly 3.5 hours of endurance. A 2.5-hour outbound flight plus a 1.2-hour return flight totals 3.7 hours — already above the endurance limit if you account for climb, descent, and taxi. Before flight, calculate: departure fuel + climb burn + cruise burn + descent burn + reserve. If the math does not work, do not depart. During descent and approach, monitor fuel state continuously. If the gauge is reading low, declare an emergency and land immediately rather than delay.
Fuel consumption increases during descent and approach — do not assume cruise burn rates apply.
Cruise power in the DA20-C1 is roughly 5.5 gal/hr. Descent and approach at reduced power may burn less, but the actual consumption depends on power setting and configuration. During descent, monitor fuel state and engine instruments continuously. If power is lost, do not assume it will return — declare an emergency and commit to a landing.
The DA20-C1 has a single fuel tank with an ON/OFF selector — fuel risk is purely quantity planning, not mis-selection.
Unlike Piper PA-28 (left/right/off) or Cessna (both/left/right), the DA20-C1 has only one tank. There is no left/right fuel management, no fuel imbalance, no tank-switching discipline required. The risk is purely exhaustion or starvation from inadequate fuel quantity. Verify fuel quantity visually at preflight. Plan your fuel burn. Monitor fuel state during flight. If power is lost, land immediately.
Declare an emergency early — do not delay or troubleshoot in descent.
If power is lost on descent to land, declare an emergency with ATC immediately. Do not spend time cycling the fuel selector, checking engine instruments, or trying to restart the engine. The runway is in sight, the field is nearby, and ATC can clear you for immediate landing. Declaring early gives you the runway and tower support. Delaying costs altitude and time. NTSB GAA19CA534 cites failure to declare an emergency and failure to execute the emergency power loss checklist as contributing factors.
Best glide speed in the DA20-C1 is 73 KIAS — establish it immediately if power is lost.
If the engine fails or power is lost, lower the nose to 73 KIAS best glide immediately. This speed maximizes glide distance and gives you the most time and distance to reach the runway or a forced landing area. Do not try to stretch the glide by flying slower — that reduces glide distance and increases stall risk. Fly 73 KIAS all the way to the runway or forced landing area.
Built from the real accident record
Scenario built from NTSB WPR24LA167 (2024 Harvard fuel starvation / tank selection), GAA19CA534 (2019 PA-28 fuel mismanagement on descent), DFW05CA087 (2005 Cessna TU206G fuel starvation / approach), and ERA17LA205 (2017 Cessna P206 fuel starvation post-maintenance). Anonymized and localized to KLAL.
NTSB reports: WPR24LA167 · GAA19CA534 · DFW05CA087 · ERA17LA205
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.II.A — Preflight Inspection · 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.185 · §91.207
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 KLAL