Fuel Tank Confusion on Descent to Tampa
Improper fuel selector management, power loss on approach, and dense urban terrain — a forced landing in the city
The scenario
Departing Tampa International Airport (KTPA), Tampa, FL — Runway 19R, on a 3.5-hour cross-country flight to a field 180 nm north. Elevation 26 ft MSL. It is a warm afternoon: OAT 31°C, altimeter 29.92, density altitude approximately 2,200 ft. The Piper Archer is loaded near gross weight — full fuel, two passengers, baggage. You filed VFR and are cruising at 4,500 ft MSL in clear skies.
You took off from KTPA at 1100 local with both fuel tanks full — 36 gallons total (18 per tank). You have been flying for 3 hours and 15 minutes. Your fuel consumption has been approximately 9 gallons per hour. You should have roughly 6–7 gallons remaining — enough for a 45-minute reserve at cruise power. The destination is 45 minutes away. You are on descent to land.
At 2,500 ft MSL, 12 nm south of KTPA on the downwind for Runway 19R, you notice the engine beginning to run rough. The tachometer is steady, but the engine is not smooth. You check the fuel selector — it is on the LEFT tank. You do not recall switching it during the flight. You have been on the left tank for the entire 3 hours and 15 minutes.
Aircraft: Piper PA-28-181 Archer, fixed gear, fixed-pitch prop, carbureted Lycoming O-360-A, 180 hp. Fuel selector: LEFT / RIGHT (no BOTH position). Vacuum steam panel. You are the pilot in command; one passenger is in the right seat, one in the back. The airplane is within weight and balance limits.
Pilot: You are a Private pilot, current, roughly 350 hours total. You have flown the Archer 40 times. You did not review the fuel management section of the POH before this flight. You did not establish a fuel-switching plan during preflight. You have been flying on the left tank since takeoff without consciously thinking about it.
- {'label': 'Field', 'value': 'KTPA · Tampa'}
- {'label': 'Runways', 'value': '10/28 · 19L/01R · 19R/01L'}
- {'label': 'Elevation', 'value': '26 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 on an instructional flight experienced a total loss of engine power during cruise near Boynton Beach, Florida. The accident resulted from fuel starvation caused by improper in-flight fuel management by the pilots. The aircraft impacted trees and terrain. The probable cause was a total loss of engine power due to fuel starvation as a result of the pilots' improper in-flight fuel management.
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 was unable to recover the engine and made a forced landing.
NTSB WPR23LA203 (2023): A Piper PA-28 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 probable cause was a loss of engine power due to fuel starvation as a result of the mechanic's failure to properly secure the fuel system gascolator strainer bowl.
NTSB CEN21LA383 (2021): A Piper PA-28 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 probable cause was a loss of engine power due to fuel starvation and the pilot's mismanagement of the available fuel.
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 consistent thread across all these events: fuel starvation in the Piper Archer is caused by improper fuel tank management — either failing to switch tanks on schedule, leaving an aircraft on one tank for too long, or confusion about which tank is selected. The Archer has LEFT and RIGHT tanks with no BOTH position. Fuel tank switching must be planned before flight and executed on a schedule. Engine roughness and power loss from fuel starvation can occur suddenly, with little warning, especially on descent when fuel flow increases and fuel pressure drops. The remedy is immediate: switch to the other tank. Delay is fatal.
The real accidents cited above occurred at other airports and in other aircraft types — NOT at Tampa International Airport. KTPA has its own accident history (see field dominant patterns), but these specific fuel starvation events happened elsewhere. The scenario is localized to KTPA to make the descent environment and off-field terrain real and consequential for you as a student here.
The lesson for the Piper Archer: establish a fuel tank switching plan before every flight. Switch tanks every 30–45 minutes, or on a schedule that balances the tanks. Know which tank you are on at all times. On descent, when fuel flow increases, fuel starvation is most likely to occur. Engine roughness on descent while on one tank is fuel starvation until proven otherwise. The fix is immediate: switch to the other tank. At 2,500 ft MSL on descent to land, you have minutes to act before the engine fails and you are forced to land in dense urban terrain.
Key lesson — In the Piper Archer, fuel tank management is not optional — it is the difference between a safe landing and a forced landing in dense development. Plan fuel tank switching before flight. Switch tanks every 30–45 minutes. Know which tank you are on at all times. Engine roughness on descent is fuel starvation until proven otherwise. Switch to the other tank immediately. At low altitude on approach, delay is fatal.
Debrief — teaching points
The Archer has LEFT and RIGHT tanks with no BOTH position — fuel tank management is mandatory.
Unlike some aircraft with a BOTH position, the Piper Archer's fuel selector has only LEFT and RIGHT. You must actively manage which tank you are on. Fuel tank switching is not optional; it is a required procedure. Establish a fuel tank switching plan before every flight — typically every 30–45 minutes, or on a schedule that balances the tanks. Write it down. Brief your passengers. Execute it.
Fuel starvation is the leading cause of engine failure in twin-tank aircraft — and it is entirely preventable.
The Archer's left and right tanks may not feed equally. If you stay on one tank too long, you can run it empty or nearly empty while fuel remains in the other tank. The engine will run rough, lose power, and quit — not because of a mechanical failure, but because you selected the wrong tank. The NTSB accident files are full of fuel starvation events in Archers and similar aircraft. Every single one was preventable by proper fuel tank management.
Engine roughness on descent is fuel starvation until proven otherwise.
On descent, fuel flow increases and fuel pressure drops. This is when fuel starvation is most likely to occur. If the engine runs rough on descent, your first action is to switch the fuel selector to the other tank. Do not troubleshoot carb heat, mixture, or engine instruments first. Switch tanks. If the roughness clears, you had a fuel starvation problem. If it does not clear, then troubleshoot other systems. But in the Archer, fuel starvation is the most likely cause of engine roughness on descent.
At low altitude on descent, you have minutes to act — not hours.
At 2,500 ft MSL on descent to land, if the engine fails and you have not switched tanks, you have roughly 2–3 minutes of glide time at 76 KIAS best glide. That is not much time to find a suitable landing area in dense development. The time to act is when you first notice the roughness — at 2,500 ft, not at 1,500 ft. Delay costs you altitude and options.
KTPA is surrounded by dense development — a forced landing is extremely difficult.
The off-field environment around Tampa International Airport is dense development, medium development, and open developed areas (parks, large lots). There is no open field, no clear runway, no road suitable for landing. A forced landing in dense urban terrain is extremely difficult and dangerous. The best you can hope for is a park or large open lot. This makes fuel management even more critical — you cannot afford an engine failure at low altitude over Tampa.
Preflight fuel planning is not a suggestion — it is the foundation of safe fuel management.
Before every flight, calculate your fuel consumption rate, plan your fuel tank switching schedule, and brief yourself on which tank you will use for each leg. Know your fuel quantity in each tank before takeoff. Know your fuel consumption rate in cruise. Know when you need to switch tanks. Know your fuel reserves at each waypoint. This is not busy work; it is the difference between a safe flight and a fuel emergency.
Built from the real accident record
Scenario built from NTSB NYC08FA020 (2007 PA-28-181 fuel starvation / improper fuel management), CEN24LA050 (2023 PA-28-181 fuel starvation on final approach), WPR23LA203 (2023 PA-28-181 fuel starvation on climb after takeoff), CEN21LA383 (2021 PA-28-181 fuel starvation / pilot mismanagement), and regional precedents WPR24LA167, GAA19CA534, WPR12LA023, CEN25LA081. Localized to KTPA.
NTSB reports: NYC08FA020 · CEN24LA050 · WPR23LA203 · CEN21LA383 · WPR24LA167 · GAA19CA534 · WPR12LA023 · CEN25LA081
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 KTPA