Fuel Selector Confusion Over Tampa Bay

Departing Peter O Knight Airport (KTPF), Tampa, FL — Runway 22, climbing out on a 217° heading over open water (Tampa Bay and the Gulf). Elevation 8 ft MSL. The runway is essentially at sea level.

It is a hazy Florida afternoon in late spring: OAT 29°C, altimeter 29.92. Scattered clouds at 3,500 ft, visibility 8 SM. A typical Gulf Coast day — warm, humid, and the kind of afternoon when pilots are heads-down on navigation and not thinking about fuel tank selection.

You are 45 minutes into a local flight, cruising at 2,000 ft MSL (1,992 ft AGL) at 110 KIAS, heading 180° (a southbound leg over the water). You have been on the LEFT fuel tank since takeoff. The left tank fuel gauge reads approximately half-full. The right tank gauge is not visible from your seat without leaning over — you have not checked it since preflight.

Suddenly, at 2,000 ft MSL, the engine begins to run rough. The tachometer drops 200 RPM. You are over open water with no visible alternate landing surface. The engine is still turning, but power is noticeably down.

Aircraft: Piper Archer PA-28-181, solo, full fuel at takeoff (48 gallons total: 24 left, 24 right), within limits. Lycoming O-360-A carbureted, fixed-pitch prop, steam panel, fuel selector on LEFT. Nothing was written up; the airplane was airworthy at departure.

Pilot: you — a Private pilot, current, roughly 250 hours total. You are familiar with the Archer's fuel system (LEFT/RIGHT selector, no BOTH position), but you have not flown this airplane in three months. Your last flight in type was a local flight with no fuel tank switching. You did not review the fuel system procedures before this flight.

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 pilots did not verify fuel tank selection or fuel quantity during the flight; they assumed the fuel selector was correct and did not monitor fuel gauges.

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 did not verify the fuel selector position when power was lost, and did not attempt to switch tanks until the engine had already quit.

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, and fuel starvation occurred on the first flight after the work.

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 flight, despite multiple takeoff and landing cycles that should have triggered fuel management checks.

The local environment at KTPF makes this scenario particularly unforgiving: Runway 22's departure end (heading 217°) is open water — Tampa Bay and the Gulf. An engine failure on the Runway 22 departure at low altitude is a ditching, not a field landing. Runways 18 and 36 also have open water as the primary off-field environment. Only Runway 4 (heading 37°) has dense development as the off-field option — still poor, but not water. This is not hypothetical; it is the NLCD ground cover off each runway end at KTPF.

NTSB ERA12FA002 (2011, FATAL): A Temco GC-1B Swift 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 in that he did not verify the fuel selector position before flight or after the power loss, resulting in fuel starvation. The pilot did not check the fuel selector when the engine began to run rough — a critical diagnostic step.

The real accidents cited above occurred at other airports and in other aircraft — NOT at Peter O Knight Airport. KTPF has its own accident history (forced landing 19.4%, loss of control 16.7%, ditching 11.1%), but these specific fuel starvation events happened elsewhere. The scenario is localized to KTPF 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. It builds gradually, the first symptom is engine roughness and a dropping tachometer (identical to carburetor ice), and by the time it is obvious, it may be too late for a comfortable recovery. The fix — verify the fuel selector position immediately when the engine runs rough, and switch tanks if necessary — is simple. The failure is always a delay in diagnosis.