Fuel Starvation on Final
Improper tank selection, low-fuel descent, and a non-towered field — the engine quits when you need it most
The scenario
Departing Venice Municipal Airport (KVNC), Venice, FL — Runway 22, on a personal cross-country flight to a field 180 nm north. Elevation 18 ft MSL. The field is non-towered (CTAF 122.8); you will self-announce on the common frequency.
It is a clear, calm Florida morning: OAT 22°C, winds light and variable, visibility 10+ SM. A perfect day to fly. You have filed no flight plan. The Piper Archer is within limits, and you conducted a thorough preflight. Both fuel tanks showed green on the gauges — full or very close to full. You topped off the left tank visually at the pump; the right tank you did not check visually, relying on the gauge.
You are now 2.5 hours into the flight, cruising at 2,500 ft MSL, 100 KIAS. You have been on the left tank for the entire flight — standard practice is to switch tanks every 30–45 minutes to balance fuel burn and detect leaks, but you did not. The left tank gauge is now reading approximately one-quarter full. The right tank gauge reads approximately half full.
You are 15 nm south of your destination. You begin a descent to pattern altitude. You switch the fuel selector from LEFT to RIGHT, intending to use the right tank for the approach and landing. Within 60 seconds of the switch, the engine begins to run rough. Within 90 seconds, the engine loses significant power — you are at 800 ft AGL, descending on a 3° glide path to Runway 22.
Aircraft: Piper PA-28-181 Archer, solo, carbureted Lycoming O-360-A, fixed-pitch prop, fixed gear, steam panel, fuel selector LEFT/RIGHT (no BOTH position). The fuel selector is currently on RIGHT. Nothing was written up; the airplane was airworthy at departure.
Pilot: you — a Private pilot, current, roughly 250 hours total. You have flown this airplane before. You did not visually verify the right tank fuel level before departure. You did not establish a disciplined fuel tank management plan during cruise. You are now descending into an unfamiliar airport with a sick engine.
- {'label': 'Field', 'value': 'KVNC · Venice'}
- {'label': 'Runways', 'value': '4/22 · 13/31'}
- {'label': 'Elevation', 'value': '18 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-181'}
- {'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 Piper Archer? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB NYC08FA020 (2007, FATAL): A Piper PA-28-181 on an instructional flight experienced a total loss of engine power during cruise near Boynton Beach, Florida, and impacted trees and terrain. The probable cause was fuel starvation caused by improper in-flight fuel management by the pilots. The airplane was destroyed; the occupants were fatally injured. The pilots had not switched tanks during cruise, and when they finally switched tanks on descent, the selected tank was empty.
NTSB CEN24LA050 (2023): A Piper PA-28-181 on a personal cross-country flight lost engine power on final approach near Minneapolis after 3.5 hours of flight. The probable cause was fuel starvation caused by a leaking left fuel tank drain with a deformed O-ring seal, compounded by pilot confusion about which tank was selected. The pilot made a forced landing; the airplane was substantially damaged but the pilot survived. The lesson: even a well-maintained airplane can have a fuel system anomaly, and pilot confusion about tank selection is deadly.
NTSB WPR23LA203 (2023): A Piper PA-28-181 lost engine power during initial climb after takeoff and made a forced landing to a soccer field, resulting in landing gear collapse and tree strike. The probable cause was fuel starvation caused by a mechanic's failure to properly secure the fuel system gascolator strainer bowl after maintenance. The airplane was substantially damaged; the pilot survived. The lesson: post-maintenance fuel system integrity is critical.
NTSB CEN21LA383 (2021): A Piper PA-28-181 during local flight with touch-and-go landings experienced engine roughness during a soft-field takeoff attempt, lost power, and the pilot made a forced landing. The probable cause was fuel starvation caused by the pilot's mismanagement of available fuel — the pilot did not switch tanks and ran one tank dry. The airplane was substantially damaged; the pilot survived.
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 in flight, forced landings, spatial disorientation, hard landings), but these specific fuel starvation events happened elsewhere. The scenario is localized to KVNC to make the non-towered environment and the runway-end terrain real and consequential for you as a student here.
The consistent thread across all these events: fuel starvation in the Piper Archer is insidious. It builds gradually — one tank depletes, the pilot does not switch, and when the selected tank runs dry, the engine quits. The fix is simple: visually verify fuel level in each tank before departure, establish a disciplined fuel tank management plan during cruise (switch every 30–45 minutes), and never rely on fuel gauges alone. The failure is always a delay or a failure to plan.
Off Runway 22's departure end at KVNC (heading 225°) is open water. An engine failure on descent to land off that runway end is a ditching, not a field landing. The water is the NLCD ground cover — it is real. This is not hypothetical.
Key lesson — In the Piper Archer, fuel starvation is the result of improper fuel management: not switching tanks during cruise, not visually verifying fuel level before departure, and not establishing a disciplined tank selection plan. The engine quits when you need it most — on descent to land. At KVNC, an engine failure on final approach to Runway 22 off-field is a ditching in open water. The fix is simple: visual fuel check before departure, tank switching every 30–45 minutes during cruise, and disciplined fuel management during approach. The failure is always a delay or a failure to plan.
Debrief — teaching points
Visual fuel verification is mandatory, not optional.
Fuel gauges in older aircraft are notoriously unreliable. A gauge reading 'full' may mean the tank is full, or it may mean the gauge is broken. The ONLY reliable way to know how much fuel is in a tank is to visually verify it — open the fuel filler cap, look inside, and confirm the level. This takes 30 seconds per tank. Before every flight, visually verify both fuel tanks. Do not rely on gauges alone. NTSB DFW05CA087 (Cessna TU206G) explicitly cites 'failure to visually verify fuel quantity before departure' as a contributing factor. This is not a suggestion — it is a lesson written in accident reports.
The Piper Archer has LEFT / RIGHT fuel selector — no BOTH position.
Unlike Cessnas (which have a BOTH position), the Piper Archer requires active fuel tank management. You must select either LEFT or RIGHT. If you forget to switch tanks during cruise, one tank will deplete while the other remains full. The engine will quit when the selected tank runs dry, even if the other tank has fuel. Establish a disciplined fuel tank management plan before flight: switch tanks every 30–45 minutes, monitor fuel consumption, and never rely on 'I'll switch when I remember.' Use a checklist or a timer.
Engine roughness after a tank switch is fuel starvation until proven otherwise.
When you switch tanks and the engine runs rough or loses power, the most likely cause is fuel starvation — the selected tank is empty, contaminated, or has a fuel system anomaly (leak, gascolator blockage, etc.). Carburetor heat will not fix a fuel starvation problem. The correct response is to switch to the other tank immediately. If the engine smooths, the selected tank is the problem. If the engine does not smooth after switching, then consider other causes (carburetor heat, mixture, throttle). But the first action is always to switch tanks.
At KVNC, an engine failure on descent to Runway 22 off-field is a ditching.
The off-field environment off Runway 22's departure end (heading 225°) is open water. There is no alternate landing surface ahead. If the engine quits on descent to land and altitude is insufficient to return to the airport or divert to Runway 13/31, the outcome is a ditching. Best glide is 76 KIAS. Doors unlatched before water contact. Master off just before impact. Flaps for slowest possible touchdown speed — impact energy rises with the square of speed, so the slowest possible speed matters most. Know this before you line up on Runway 22.
Fuel starvation on descent is a critical-time emergency.
When the engine quits on descent to land, you have seconds to make decisions. The altitude is low, the options are limited, and the margin for error is zero. This is why fuel management during cruise is not optional — it is the foundation of a safe descent. If you have managed fuel properly (switched tanks, monitored consumption, verified both tanks have fuel), you will have options on descent. If you have not, you will be forced to land on whatever is below you. The NTSB NYC08FA020 accident (fatal, PA-28-181, fuel starvation) resulted from improper fuel management during cruise and a failure to switch tanks on descent. The pilots had no options left.
Built from the real accident record
Scenario built from NTSB NYC08FA020 (2007 PA-28-181 fuel starvation / improper in-flight fuel management), CEN24LA050 (2023 PA-28-181 fuel starvation on final / leaking tank drain), WPR23LA203 (2023 PA-28-181 fuel starvation / gascolator installation), CEN21LA383 (2021 PA-28-181 fuel starvation / pilot mismanagement), and regional precedents WPR24LA167, GAA19CA534, DFW05CA087, ERA17LA205. Anonymized and localized to KVNC.
NTSB reports: NYC08FA020 · CEN24LA050 · WPR23LA203 · CEN21LA383 · 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.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 Piper Archer scenarios · More scenarios at KVNC