Fuel Selector Confusion Over Tampa Bay
A Piper Archer's LEFT/RIGHT fuel selector, a long cross-country, and an engine failure on approach — the decision window is measured in seconds
The scenario
Departing Albert Whitted Airport (KSPG), St. Petersburg, FL — Runway 07, on a cross-country flight to a field 180 nm north. Elevation 7 ft MSL. It is 1400 local, clear skies, light winds from the northeast at 5 kt. You have been airborne for 3 hours and 15 minutes in the Piper Archer (PA-28-181). You are at 2,500 ft MSL, 10 nm south of KSPG, on a direct approach to Runway 07.
Aircraft: Piper Archer PA-28-181, solo, full fuel at departure (48 gallons total: 24 gallons left tank, 24 gallons right tank). You have burned approximately 30 gallons over the 3.25-hour flight. Lycoming O-360-A, 180 hp, carbureted. Fixed-pitch prop, fixed gear, steam panel. Fuel selector: LEFT / RIGHT (no BOTH position). The airplane is within limits.
Pilot: you — a Private pilot, current, roughly 250 hours total. You are familiar with the Archer's fuel management: the LEFT/RIGHT selector must be switched regularly to maintain lateral balance and avoid fuel starvation from a single tank. You did not file IFR; this is a VFR day flight. You did not brief a fuel management plan with yourself before departure — you assumed 'full fuel' meant you could fly the route without thinking about tank selection.
The engine is running smoothly at 2,500 ft. You are on downwind for Runway 07, about 2 nm out. Tower has cleared you to land. You are heads-down on the approach, not monitoring the fuel selector position or the tachometer closely. The fuel quantity indicators show roughly 18 gallons remaining — enough for the landing and a 30-minute reserve, by your rough math.
Then, at 800 ft AGL on final approach, the engine begins to run rough. The tachometer is unwinding. You are over the open water of Tampa Bay, 1.5 nm from the runway.
- {'label': 'Field', 'value': 'KSPG · Albert Whitted'}
- {'label': 'Runways', 'value': '7/25 · 18/36'}
- {'label': 'Elevation', 'value': '7 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 PA-28-181? (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, and impacted trees and terrain. The probable cause was fuel starvation caused by improper in-flight fuel management by the pilots. The Archer's LEFT/RIGHT fuel selector requires active switching to maintain lateral balance and prevent starvation from a single tank. The pilots did not switch tanks during the flight.
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 leak was slow enough that it did not show up in a preflight visual inspection, but over 3.5 hours, it cost enough fuel to cause starvation when the left tank was selected.
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 fuel system was not properly secured after maintenance, allowing air to enter the fuel line.
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 pilot did not switch tanks during the local flight, and one tank ran dry.
The local environment at KSPG makes this scenario particularly unforgiving: Runway 07's departure end (and approach end, depending on direction) is open water — Tampa Bay. An engine failure on approach to Runway 07 at low altitude is a ditching, not a field landing. There is no open field, no road, no park. The water is the off-field environment. This is not hypothetical; it is the NLCD ground cover off that runway end.
NTSB ERA12FA002 (2011, Chesapeake Bay): A Luscombe GC-1B experienced total loss of engine power over the Chesapeake Bay and ditched in the water after a controlled glide. The accident resulted from the pilot's improper fuel management — the pilot did not verify the fuel selector position before flight or after the power loss, resulting in fuel starvation. The pilot survived the ditching.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Albert Whitted Airport. KSPG has its own accident history (see field dominant patterns), but these specific events happened elsewhere. The scenario is localized to KSPG to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: fuel starvation in the Piper Archer is insidious. The LEFT/RIGHT fuel selector requires active management. Fuel starvation from a single tank is a classic failure mode. The fix — switching tanks immediately at the first sign of engine roughness — is simple. The failure is always a delay or a failure to switch tanks at all.
Key lesson — The Piper Archer PA-28-181 has a LEFT/RIGHT fuel selector with no BOTH position. You must switch tanks regularly (every 30–45 minutes) to maintain lateral balance and prevent starvation from a single tank. At low altitude over water, the decision window is measured in seconds — not minutes. Off Runway 07 at KSPG, the off-field environment is Tampa Bay: a delayed response means a ditching, not a field landing. Verify fuel selector position during preflight and immediately after any engine roughness or power loss.
Debrief — teaching points
The Piper Archer's LEFT/RIGHT fuel selector requires active, disciplined management.
Unlike the Cessna 172 (which has a BOTH position), the Archer has only LEFT and RIGHT. There is no BOTH. You must switch tanks every 30–45 minutes to maintain lateral balance and ensure both tanks are feeding the engine. Failure to switch tanks is a classic Archer accident — one tank runs dry while the other has fuel, and the pilot does not realize the selector is on the empty tank. At low altitude, this is fatal. Establish a timer or a checklist item: 'Switch tanks every 30 minutes.' Write it down. Make it automatic.
Fuel starvation in a carbureted engine shows as engine roughness and a dropping tachometer — similar to carburetor ice.
In a carbureted Lycoming O-360, fuel starvation first shows as engine roughness and an unexplained RPM decrease. This is identical to the symptom of carburetor ice. The difference is the fix: carburetor ice is fixed by applying carb heat; fuel starvation is fixed by switching tanks. If carb heat does not fix the roughness, immediately switch the fuel selector to the opposite tank. In the Archer, fuel starvation is more likely than carb ice — the LEFT/RIGHT selector is a constant source of confusion.
Verify fuel selector position during preflight and immediately after any engine anomaly.
Before every flight, physically verify the fuel selector is on the correct tank (usually LEFT for takeoff). Do not assume it is correct. After any engine roughness or power loss, immediately check the fuel selector position and switch tanks if necessary. The NTSB CEN24LA050 pilot was confused about which tank was selected when the engine failed on approach — a simple glance at the selector would have saved the flight. Make it a habit: engine roughness = check fuel selector = switch tanks.
Fuel quantity indicators are unreliable — use a dipstick during preflight.
The Archer's fuel quantity gauges are notoriously inaccurate, especially as fuel is consumed. A gauge showing 18 gallons might actually be 12 gallons, or 25 gallons. The only reliable way to know how much fuel is in the tanks is to use a dipstick during preflight. Measure both tanks. Write down the amounts. Plan your flight based on the dipstick reading, not the gauges. The NTSB ANC17LA043 pilot relied on unreliable fuel quantity indicators and ran out of fuel — a dipstick check would have revealed the discrepancy.
At KSPG Runway 07, an engine failure on approach is a ditching.
The off-field environment off Runway 07's approach end (heading 062°) is open water — Tampa Bay. There is no alternate landing surface. If the engine quits on approach to Runway 07 and altitude is insufficient to return to the airport, 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 touchdown speed. Know this before you line up on Runway 07.
A fuel starvation event at low altitude warrants a precautionary landing and a maintenance inspection.
If the engine runs rough on approach and a tank switch fixes it, do not assume the problem is solved. Land immediately and have the mechanic inspect the fuel system. The NTSB CEN24LA050 pilot experienced fuel starvation on approach, switched tanks, and continued the flight — the engine failed again on final approach. A precautionary landing after the first event would have revealed the leaking tank drain and prevented the second failure. Fuel system anomalies are not minor — they are maintenance issues that require professional inspection.
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 leaking tank / fuel starvation), WPR23LA203 (2023 PA-28-181 gascolator installation failure), CEN21LA383 (2021 PA-28-181 fuel starvation / soft-field takeoff), and regional ditching precedents ERA12FA002, ANC17LA043, LAX97LA278, LAX98LA168. Anonymized and localized to KSPG.
NTSB reports: NYC08FA020 · CEN24LA050 · WPR23LA203 · CEN21LA383 · ERA12FA002 · ANC17LA043 · LAX97LA278 · 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.D — Flight Controls
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 Piper Archer scenarios · More scenarios at KSPG