Fuel Selector Confusion on Final Approach
A Piper Archer's LEFT/RIGHT fuel selector, fuel starvation, and a non-towered field with water off one runway end — the decision clock is measured in seconds
The scenario
Departing Tampa Executive Airport (KVDF), Tampa, FL — Runway 23, on a 2.5-hour cross-country flight to a nearby airport. Elevation 22 ft MSL. The field is non-towered (CTAF); you self-announce on 118.5.
It is a clear, calm Florida morning: OAT 22°C, wind calm to 3 knots, altimeter 30.01. Visibility 10+ SM. You filed VFR and departed at 0900 local. The flight plan shows a cruise altitude of 3,500 ft MSL, which puts you well below the overlying Tampa Class B (floor 3,000 MSL). You are in Class G airspace — uncontrolled.
You are now on final approach to Runway 23 at KVDF after 2 hours 25 minutes of flight. You are at 800 ft AGL, descending at 66 KIAS (Vref, approach speed), 3 miles from the runway. The field is in sight. The landing is routine — until the engine begins to run rough and lose power at 600 ft AGL on short final.
Aircraft: Piper PA-28-181 Archer, solo, full fuel at departure (48 gallons usable). The left tank was selected during cruise. You have not switched tanks since takeoff. Nothing was written up; the airplane was airworthy at departure. The fuel selector is a LEFT / RIGHT lever — no BOTH position on this airplane.
Pilot: you — a Private pilot, current, roughly 180 hours total. You did not visually verify fuel quantity before departure (you relied on the fuel quantity gauges). You did not brief the fuel selector position or switching plan before takeoff. You are distracted by the approach and have not actively monitored fuel quantity during cruise.
- {'label': 'Field', 'value': 'KVDF · Tampa Executive'}
- {'label': 'Runways', 'value': '5/23 · 18/36'}
- {'label': 'Elevation', 'value': '22 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 with two pilots experienced total loss of engine power during cruise near Boynton Beach, Florida. The accident resulted from fuel starvation caused by improper in-flight fuel management. The pilots did not switch tanks during the flight, and one tank was depleted while the other had fuel remaining. The airplane impacted trees and terrain. Both occupants were killed.
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 accident resulted from 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 switched tanks on final approach and restored power, but the event exposed both a maintenance issue (the leaking drain) and a pilot knowledge gap (not knowing which tank was selected).
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 accident resulted from fuel starvation caused by improper gascolator installation by maintenance personnel. The fuel system gascolator strainer bowl was not properly secured, allowing fuel to bypass the strainer.
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 accident resulted from loss of engine power due to fuel starvation and the pilot's mismanagement of available fuel. The pilot did not actively manage the fuel selector during multiple takeoffs and landings.
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 18.4%, HARD_LANDING 18.4%, FORCED_LANDING 15.8%), but these specific fuel starvation events happened elsewhere. The scenario is localized to KVDF to make the fuel selector reality and the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: the Piper Archer's LEFT / RIGHT fuel selector requires active, deliberate management. There is no BOTH position. Fuel starvation in the Archer is almost always caused by pilot failure to switch tanks during flight, or failure to verify fuel quantity before departure. The fix — visual fuel verification before departure, a written fuel-switching plan, and active fuel management during cruise — is simple. The failure is always a delay or omission.
Key lesson — The Piper Archer PA-28-181 has a LEFT / RIGHT fuel selector with no BOTH position. Fuel starvation is a Piper-class accident. Visually verify fuel quantity before departure (dipstick or sight gauge, not just gauges). Brief a fuel-switching plan before takeoff. Switch tanks every 30–45 minutes during cruise to balance fuel consumption and maintain CG. If the engine runs rough or loses power in flight, check the fuel selector position immediately — switching tanks may restore power. At KVDF, off Runway 36's departure end, the off-field environment includes open water; an engine failure there is a ditching. Know your fuel situation before you need it.
Debrief — teaching points
The Piper Archer has LEFT / RIGHT fuel selector — no BOTH position.
Unlike Cessnas (which have a BOTH position), the Piper Archer PA-28-181 requires active fuel management. You must select LEFT or RIGHT and switch tanks during flight to balance fuel consumption and maintain CG. Failure to switch tanks is the root cause of most Piper fuel starvation accidents. The NTSB NYC08FA020 accident — fatal, with two pilots on board — occurred because neither pilot switched tanks during cruise. One tank was empty; the other had fuel. The engine quit because the selected tank was depleted.
Visual fuel verification before departure is more reliable than fuel quantity gauges.
Fuel quantity gauges in the Archer can be inaccurate, especially if the airplane has been parked for a while or if the gauges have drifted. The only reliable way to know how much fuel is in each tank is to visually verify it: open the fuel caps and look at the sight gauge, or use a dipstick. The NTSB CEN24LA050 accident occurred on final approach because the pilot relied on fuel quantity gauges that were inaccurate. The LEFT tank was nearly empty; the RIGHT tank had fuel. The pilot did not discover this until the engine ran rough on final approach.
Brief a fuel-switching plan before takeoff and execute it during cruise.
Before you line up on the runway, decide when you will switch tanks during the flight. A common plan is to switch tanks every 30–45 minutes, or at specific waypoints during a cross-country flight. Write it down. Execute it. The NTSB CEN21LA383 accident occurred because the pilot did not have a fuel-switching plan and did not actively manage the fuel selector during multiple takeoffs and landings. The fuel became unequally distributed, and the selected tank was depleted.
If the engine runs rough or loses power in flight, check the fuel selector position immediately.
Engine roughness or power loss in the Archer is often caused by fuel starvation from the selected tank being empty or nearly empty. Before you diagnose carburetor ice, mixture issues, or ignition problems, check the fuel selector. Is it on the tank you think it is? Is that tank empty? Switch to the other tank. The NTSB CEN24LA050 pilot switched tanks on final approach and restored power — the correct response. The NTSB NYC08FA020 pilots did not check the fuel selector; the engine quit and they did not recover.
At KVDF, off Runway 36's departure end, the off-field environment includes open water — a ditching, not a field landing.
The off-field environment off Runway 36's climb-out (heading 360°) is mostly medium development, wooded wetland, and open water. An engine failure on the Runway 36 departure at low altitude is a ditching, not a field landing. This is not hypothetical; it is the USGS NLCD ground cover off that runway end. Know your field's off-field environment before you line up on the runway. Off Runway 05 (heading 42°), the environment is good — wooded wetland, medium development, pasture/hay. Off Runway 23 (heading 222°), the environment is good — pasture/hay, open water, medium development. Off Runway 18 (heading 180°), the environment is marginal — low-density development, wooded wetland, open developed. Choose your runway based on the off-field environment and the wind.
Fuel starvation in the Archer is almost always a pilot error — not a mechanical failure.
The NTSB WPR23LA203 accident was caused by improper gascolator installation by maintenance personnel — a rare mechanical failure. The NTSB NYC08FA020, CEN24LA050, and CEN21LA383 accidents were all caused by pilot failure to manage the fuel selector or verify fuel quantity. The fix is preflight discipline: visual fuel verification, a written fuel-switching plan, and active fuel management during cruise. This is not optional; it is the price of flying a Piper Archer.
Built from the real accident record
Scenario built from NTSB NYC08FA020 (2007 PA-28-181 fuel starvation / instructional flight), CEN24LA050 (2023 PA-28-181 fuel starvation on final approach), WPR23LA203 (2023 PA-28-181 fuel starvation / improper gascolator installation), CEN21LA383 (2021 PA-28-181 fuel starvation / mismanagement), and regional precedents ERA12FA002, ANC17LA043, LAX98LA168. Anonymized and localized to KVDF (Tampa Executive Airport).
NTSB reports: NYC08FA020 · CEN24LA050 · WPR23LA203 · CEN21LA383 · ERA12FA002 · ANC17LA043 · LAX98LA168
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.B — Engine Starting / Systems Preflight · PA.II.E — Fuel System and Operation
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 KVDF