Fuel Tank Discipline at Tampa International
A Piper Warrior's LEFT/RIGHT fuel selector, inadequate preflight planning, and the consequences of fuel mismanagement over dense development
The scenario
Departing Tampa International Airport (KTPA), Tampa, FL — Runway 19R, a 4-hour local flight to a nearby airport and back. Elevation 26 ft MSL. Clear skies, light winds, 24°C, altimeter 29.98. VFR all the way. You are a Private pilot, 280 hours total, current and proficient in the Piper Warrior.
Aircraft: Piper PA-28-161 Warrior, solo, full fuel at departure (48 gallons usable). Lycoming O-320-D, carbureted, fixed-pitch prop, fixed gear. Fuel selector: LEFT / RIGHT (no BOTH position). The Warrior burns approximately 7.5 gallons per hour at cruise power.
Preflight: You visually checked both fuel tanks — they looked full. You did not dip the tanks with a fuel stick; you relied on the sight gauges. The left tank appeared to have a small amount of debris in the filler neck, but you did not think it was significant. You did not run the engine long enough to establish a baseline fuel flow. You filed no flight plan and did not brief an alternate airport.
Flight: You climbed out of KTPA on Runway 19R, heading 182°, and leveled off at 3,500 ft MSL. You set cruise power and trimmed the airplane. You did not establish a fuel management plan — no tank-switching intervals, no fuel-burn calculation, no go-or-divert decision point. You have been cruising for 3 hours and 45 minutes. The fuel gauges show approximately 1/4 tank remaining — you estimate you have about 12 gallons left. You are now on descent to return to KTPA.
Current situation: You are 15 nm south of KTPA, descending through 2,500 ft MSL, requesting vectors for approach. ATC has cleared you to descend to 2,000 ft MSL and is vectoring you for a straight-in approach to Runway 19R. The fuel selector is currently on the LEFT tank. You have not switched tanks during the entire flight. The engine is running smoothly. You are 8 nm from the runway.
- {'label': 'Field', 'value': 'KTPA · Tampa'}
- {'label': 'Runways', 'value': '10/28 · 19L/01R · 19R/01L'}
- {'label': 'Elevation', 'value': '26 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-161'}
- {'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 Warrior? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB ERA11CA423 (2011): A Piper PA-28-161 on a local flight experienced total engine failure due to fuel exhaustion during a missed approach after 4 hours 43 minutes of flight. The probable cause was the pilot's inadequate preflight planning and fuel management. The Warrior burns approximately 7.5 gallons per hour; at 4 hours 43 minutes, the pilot needed at least 35 gallons of usable fuel to complete the flight safely. The accident resulted from failure to plan fuel consumption and failure to switch tanks during the flight.
NTSB ERA09LA456 (2009): A Piper PA-28-161 on a local sightseeing flight experienced engine power loss during approach. The probable cause was the pilot's inadequate preflight inspection and failure to ensure an adequate quantity of fuel was available for the flight. The pilot did not verify fuel quantity in each tank before flight and did not manage fuel tank switching during the flight.
NTSB LAX06CA026 (2005): A Piper PA-28-161 on a cross-country flight exhausted its usable fuel after 5.7 hours of flight. The probable cause was the pilot's inadequate preflight and in-flight planning, inadequate fuel consumption calculations, and failure to divert to an alternate airport before the fuel situation became critical. The pilot did not plan fuel tank switching intervals and did not recognize the fuel situation until it was too late.
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 probable cause was improper fuel management and failure to switch to the right tank containing usable fuel. The pilot did not verify fuel quantity in each tank before descent and did not establish a fuel management plan.
The real accidents cited above occurred at other airports and in other aircraft — NOT at KTPA. Tampa International Airport has its own accident history (see field dominant patterns: FORCED_LANDING 22.2%, LOSS_OF_CONTROL_INFLIGHT 11.1%), but these specific fuel exhaustion events happened elsewhere. The scenario is localized to KTPA to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: fuel exhaustion and starvation in the Piper Warrior result from inadequate preflight planning, failure to verify fuel quantity in each tank, and failure to establish a fuel tank switching plan before flight. The Warrior's LEFT / RIGHT fuel selector (no BOTH position) places the burden of fuel management entirely on the pilot. There is no automatic crossfeed; selecting an empty tank causes immediate fuel starvation. The fix is simple: dip the tanks with a fuel stick, establish a fuel tank switching interval (e.g., switch every 45 minutes), and verify fuel quantity in the selected tank before descent. Waiting until the LEFT tank is empty to switch to the RIGHT tank is waiting too long.
Key lesson — The Piper Warrior's LEFT / RIGHT fuel selector (no BOTH position) requires disciplined fuel management. Dip the tanks with a fuel stick before every flight — do not rely on sight gauges. Establish a fuel tank switching interval (e.g., switch every 45 minutes) and stick to it. Before descent, verify fuel quantity in BOTH tanks and confirm you are on the tank with the most fuel. At KTPA, the off-field environment is dense development — parks, buildings, roads. A forced landing due to fuel starvation is survivable if you make the runway; if you do not, you are landing in developed area. Fuel management is not optional; it is the foundation of safe flight.
Debrief — teaching points
The Piper Warrior has LEFT / RIGHT fuel selector — there is NO BOTH position.
Unlike the Cessna 172 (which has a BOTH position), the Piper Warrior's fuel selector offers only LEFT and RIGHT. There is no automatic crossfeed. Fuel flows only from the selected tank. This places the entire burden of fuel management on the pilot. Selecting an empty tank causes immediate fuel starvation — there is no backup. You must know which tank is selected at all times and verify fuel quantity in each tank before flight.
Dip the tanks with a fuel stick — do not rely on sight gauges.
Fuel sight gauges are notoriously inaccurate, especially when the airplane is not level or when fuel has sloshed during flight. The only reliable way to verify fuel quantity is to dip each tank with a fuel stick before every flight. A visual check of the filler neck is not sufficient. The scenario's pilot saw debris in the LEFT tank filler neck but did not dip the tank — that debris may have been a sign of contamination or a stuck float in the gauge. Dipping would have revealed the true fuel quantity.
Establish a fuel tank switching interval before flight — e.g., switch every 45 minutes.
The Warrior burns approximately 7.5 gallons per hour. At 45-minute intervals, you consume about 5.6 gallons per tank. Switching every 45 minutes ensures that you use fuel evenly from both tanks and that you always have a known fuel quantity in the selected tank. Do not wait until one tank is nearly empty to switch — that is waiting too long. Establish the interval before flight and stick to it religiously.
Before descent, verify fuel quantity in BOTH tanks and confirm you are on the tank with the most fuel.
As you approach your destination and begin descent, take 30 seconds to verify fuel quantity in both tanks (using the sight gauges as a rough check, or by memory of your switching intervals) and confirm that the fuel selector is on the tank with the most fuel. This simple check prevents fuel starvation on descent and approach. If one tank is significantly lower, switch to the fuller tank before descent.
Inadequate preflight planning and fuel management is the root cause of fuel exhaustion accidents.
The NTSB accidents cited in this scenario all share a common thread: the pilot did not plan fuel consumption, did not verify fuel quantity in each tank, and did not establish a fuel management plan before flight. The Warrior's 48-gallon total capacity (approximately 44–46 gallons usable) and 7.5 GPH burn rate mean that a 4-hour flight requires at least 30 gallons of usable fuel to be safe. Anything less is marginal. Know your fuel burn rate, calculate fuel required for your flight, and verify you have adequate fuel before departure.
At KTPA, the off-field environment is dense development — a forced landing is survivable only if you make the runway.
The off-field environment around KTPA is dense development, parks, buildings, and roads. There is no open field, no water, no alternate landing surface. A forced landing due to fuel starvation is survivable if you make the runway; if you do not, you are landing in developed area with significant risk of injury or death. This is not hypothetical — it is the NLCD ground cover around KTPA. Fuel management is not optional; it is the foundation of safe flight at this airport.
Built from the real accident record
Scenario built from NTSB CEN22LA324, ERA11CA423, ERA09LA456, LAX06CA026 (PA-28-161 fuel exhaustion/starvation accidents), and regional precedents WPR24LA167, GAA19CA534, WPR12LA023, CEN25LA081. Real accidents occurred at other airports — NOT at KTPA.
NTSB reports: CEN22LA324 · ERA11CA423 · ERA09LA456 · LAX06CA026 · WPR24LA167 · GAA19CA534 · WPR12LA023 · CEN25LA081
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · 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.151 · §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 Warrior scenarios · More scenarios at KTPA