Fuel Selector Confusion Over Tampa Bay
Fuel starvation on final approach — the Piper Archer's LEFT/RIGHT selector and a preflight oversight collide at 800 ft AGL
The scenario
Departing St. Petersburg Clearwater International Airport (KPIE), Pinellas Park, FL — Runway 18, a local VFR flight in a Piper Archer PA-28-181. Elevation 11 ft MSL. It is a clear, calm Florida morning: OAT 22°C, winds calm to light, altimeter 30.02, visibility 10 SM. A textbook VFR day.
You are a Private pilot with 250 hours total time, 80 hours in Piper Archers. This is a local flight — a 1.5-hour round trip to a nearby airport and back. You preflight the airplane, check the fuel visually in both tanks (left and right), and note 'full' in the logbook. The left tank appears full; the right tank appears full. You do not dip the tanks with a fuel stick — a visual check is your standard practice.
You depart Runway 18 at 0900 local, climb to 2,500 ft MSL, and cruise for 45 minutes to the diversion field. The flight is smooth, the engine runs smoothly, and you log 1.2 hours of flight time. You land, taxi, refuel briefly (you add 5 gallons to the left tank only — the FBO was busy and you were in a hurry), and depart again at 1000 local.
You climb back to 2,500 ft MSL and cruise for 30 minutes back toward KPIE. The engine is running smoothly. You are on a heading of 180° (southbound), and KPIE is 20 nm ahead. You have not switched fuel tanks since departure. The fuel selector is still on LEFT, where it was set at the beginning of the flight. You do not recall switching it during the outbound leg, and you assume the left tank is still feeding the engine.
At 1030 local, 20 nm north of KPIE, you contact KPIE tower and request a straight-in approach to Runway 18. Tower clears you to descend to 1,600 ft MSL (the Class D ceiling) and vectors you to a 5-mile final. You are at 800 ft AGL on final approach when the engine begins to run rough. The tachometer is dropping. You have 4 minutes to the runway.
- {'label': 'Field', 'value': 'KPIE · St. Petersburg Clearwater'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '11 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-181'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
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 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 pilots did not switch fuel tanks during the flight, and one tank ran dry while the other had fuel. The airplane impacted trees and terrain. The probable cause was the pilots' failure to manage fuel properly.
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 before the approach and did not recognize the fuel starvation symptom until it was too late.
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 mechanic had failed to properly secure the fuel system gascolator strainer bowl, allowing fuel to bypass the engine.
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 and did not verify fuel quantity before each takeoff.
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 — 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 but the accident was preventable through disciplined preflight checks.
The real accidents cited above occurred at other airports and in other aircraft — NOT at KPIE. St. Petersburg Clearwater International Airport has its own accident history (see field dominant patterns: LOSS_OF_CONTROL_INFLIGHT 21.2%, LOSS_OF_CONTROL_GROUND 15.2%, STALL_SPIN 12.1%, GEAR_UP_LANDING 9.1%, OBSTACLE_ON_TAKEOFF_LANDING 9.1%), but these specific fuel starvation events happened elsewhere. The scenario is localized to KPIE to make the off-field environment and the approach geometry 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 has no BOTH position — if one tank runs dry and you are on that tank, the engine will quit. The first symptom is engine roughness and a dropping tachometer on approach, when options are most limited. The fix — switching the fuel selector to the other tank — is simple and immediate. The failure is always a delay or a failure to switch tanks during flight.
Off Runway 18 at KPIE (heading 171°), the off-field environment is medium development and parks — a forced landing is marginal but survivable. Off Runway 36 (heading 351°), the environment is open water — a forced landing there is a ditching. Know the off-field environment before you line up on approach.
Key lesson — In the Piper Archer, fuel starvation from improper tank management is a preventable accident. Switch fuel tanks every 30 minutes of flight time. Verify the fuel selector position before each flight leg and after any engine anomaly. Never assume a tank is full based on a visual check alone — use a fuel stick or dip the tanks. On final approach, if the engine runs rough and loses power, fuel starvation is the most likely cause in a LEFT/RIGHT selector airplane. Switch tanks immediately.
Debrief — teaching points
The Piper Archer has a LEFT / RIGHT fuel selector with NO BOTH position.
Unlike a Cessna 172 (which has BOTH), the Archer requires active fuel management. You must switch the fuel selector between LEFT and RIGHT during flight. If one tank runs dry and you are on that tank, the engine will quit. There is no crossfeed valve — you cannot draw from the other tank without switching the selector. This is a critical systems difference. Know it before you fly.
Switch fuel tanks every 30 minutes of flight time.
The standard procedure in a LEFT/RIGHT selector airplane is to switch tanks every 30 minutes to balance fuel consumption and prevent one tank from running dry while the other is full. This is not optional — it is the procedure that prevents fuel starvation. Set a timer. Switch the selector. Check the engine response to confirm the switch was successful. If the engine roughens after a switch, you may have switched to an empty tank — switch back immediately.
Verify the fuel selector position before each flight leg.
Before you depart, confirm which tank the fuel selector is on. After you land, note the position in the logbook. Before you depart again, verify the position matches your plan. Do not assume the selector is where you left it — it may have been moved by a previous pilot or a mechanic. A 10-second visual check of the fuel selector position prevents fuel starvation on approach.
Visual fuel checks are unreliable — use a fuel stick or dip the tanks.
Looking in the filler neck and saying 'looks full' is not a reliable fuel measurement. A tilted airplane, residual fuel clinging to the tank wall, or a partially-full tank can all look full from above. Use a fuel stick (a marked dipstick) to measure fuel quantity accurately. Dip both tanks before each flight. Record the quantity in the logbook. This is the gold standard for fuel measurement.
On approach, if the engine runs rough and loses power, fuel starvation is the most likely cause.
Engine roughness and a dropping tachometer on final approach, especially if you have not switched tanks in a while, point to fuel starvation. Carburetor heat may help if carb ice is the cause, but in a LEFT/RIGHT selector airplane, your first response to unexplained engine roughness on approach is to switch fuel tanks. If the engine smooths after the switch, you have diagnosed and fixed the problem. If it does not, then consider other causes.
Best glide in the PA-28-181 is 76 KIAS — establish this speed immediately if power is lost.
If the engine fails on approach and you cannot restore power by switching tanks, establish 76 KIAS best glide immediately. This speed maximizes glide distance and gives you the best chance of reaching the runway or a suitable off-field landing area. At 800 ft AGL on final approach, 76 KIAS gives you roughly 2 minutes of glide time — enough to reach KPIE if you are within 3 nm.
Built from the real accident record
Scenario built from NTSB NYC08FA020 (2007 PA-28 fuel starvation / improper tank management), CEN24LA050 (2023 PA-28-181 fuel starvation / tank confusion on approach), WPR23LA203 (2023 PA-28 fuel starvation / gascolator failure), CEN21LA383 (2021 PA-28-181 fuel starvation / mismanagement), and regional precedents ERA12FA002, ANC17LA043, LAX97LA278, LAX98LA168. Anonymized and localized to KPIE.
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.II.A — Preflight Assessment · PA.II.B — Engine Starting / Systems Preflight · PA.III.C — Fuel Management · 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 KPIE