Fuel Tank Discipline at a Busy Class B
Engine failure from fuel mismanagement on approach to Tampa International — dense development below, limited off-field options, and a towered emergency
The scenario
Departing Tampa International Airport (KTPA), Tampa, FL — Runway 19R, descending on approach to land after a 2.5-hour flight from the north. Field elevation 26 ft MSL. You are a commercial pilot with 450 hours total time, 120 hours in the Piper Arrow, and current in type. The Arrow is a complex single: retractable gear, constant-speed prop, fuel-injected Lycoming IO-360, and a critical fuel-management discipline — LEFT / RIGHT fuel selector, no crossfeed.
It is a clear afternoon in late spring: OAT 26°C, altimeter 29.92, scattered clouds at 3,500 ft. Visibility 10 SM. You are in the Tampa Class B (ceiling 10,000 MSL), under radar vectors from approach control. KTPA is towered 24/7 and busy — you are one of many aircraft in the pattern.
Fuel status: You departed with 40 gallons total (20 left, 20 right). The flight burned approximately 12 gallons per hour at cruise power. You have been airborne 2 hours 30 minutes. Calculation: 40 gal − (12 gal/hr × 2.5 hr) = 10 gallons remaining. You did not lean the mixture aggressively during cruise — you flew at a higher power setting to make good time. You did not verify fuel quantity by visual inspection before descent.
Current status: You are at 2,000 ft MSL, 8 nm from KTPA, descending on a 180° heading (southbound) toward Runway 19R. The fuel selector is on the LEFT tank. You have not switched tanks since departure. The left tank has been feeding the engine for the entire 2.5-hour flight. You are now on approach, gear down (Vle 129 KIAS), flaps 10°, descending at 90 KIAS. Approach control has cleared you to descend to 1,500 ft MSL and expects to hand you off to tower in 2 minutes.
The off-field environment below you is dense urban development — Tampa's commercial and residential zones. There are no open fields, no water suitable for ditching, no roads wide enough for a safe forced landing. The forced-landing environment is marginal at best: parks, parking lots, and developed land. An engine failure on approach to Runway 19R means a forced landing into that development.
- {'label': 'Field', 'value': 'KTPA · Tampa'}
- {'label': 'Runways', 'value': '10/28 · 19L/01R · 19R/01L'}
- {'label': 'Elevation', 'value': '26 ft'}
- {'label': 'Aircraft', 'value': 'PA-28R'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we enter the decision tree — what do you know about fuel management in the Piper Arrow? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB ERA13LA111 (2013, fatal): A Piper PA-28R on an IFR flight from Georgia to Delaware experienced total loss of engine power due to fuel exhaustion after the pilot attempted multiple missed approaches at three different airports in low IMC. The probable cause was the pilot's failure to land at multiple airports equipped with adequate instrument approach procedures while operating in low instrument meteorological conditions and his delay in declaring a fuel-related emergency. The pilot did not switch tanks, did not verify fuel quantity, and did not plan fuel management before descent. The result was fatal.
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 pilot did not verify fuel quantity before descent and did not plan tank switching intervals.
NTSB WPR24LA167 (2024): A Canadian Car & Foundry Harvard MK IV lost all engine power due to fuel starvation when the pilot improperly selected the left fuel tank at low fuel levels. The accident resulted from improper fuel tank selection and a malfunctioning fuel selector, requiring a forced landing that struck a dirt berm. The pilot did not verify fuel quantity and did not understand fuel tank capacity limits.
NTSB CEN22FA419 (2022, fatal): A Piper PA-28R-201 on a personal flight from Myrtle Beach, South Carolina experienced total engine failure during initial climb after departure. The accident resulted from a missing vacuum pump drive pad gasket installed during avionics maintenance, which caused oil exhaustion and catastrophic engine failure. While this accident was a maintenance defect, not fuel mismanagement, it demonstrates the critical importance of preflight inspection — the pilot did not detect the maintenance error before flight.
NTSB ERA22FA261 (2022, fatal): A Piper PA-28RT on a personal flight lost engine power due to oil starvation caused by high-cycle fatigue failure of an oil pressure sensor line that was improperly installed with a rigid line instead of flexible hose. The pilot did not perform an adequate preflight inspection and did not detect the maintenance error. The lesson: preflight inspection is not optional, and fuel/oil system integrity must be verified before every flight.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Tampa International Airport. KTPA has its own accident history (dominant pattern: FORCED_LANDING 22.2%, LOSS_OF_CONTROL_INFLIGHT 11.1%, GEAR_UP_LANDING 6.7%), but these specific fuel-starvation events happened elsewhere. The scenario is localized to KTPA to make the Class B complexity, the towered environment, and the dense urban off-field environment real and consequential for you as a commercial pilot here.
The consistent thread across all these events: fuel mismanagement in the Piper Arrow is insidious. It builds gradually — a pilot forgets to switch tanks, does not verify fuel quantity, does not plan descent fuel management — and by the time the engine fails, it is too late for a comfortable recovery. The fix is simple and non-negotiable: verify fuel quantity before descent, plan tank switching intervals during cruise, and switch tanks before entering the critical phases (descent, approach, landing). The failure is always a delay or an oversight.
Key lesson — In the Piper Arrow, fuel tank discipline is non-negotiable. The LEFT / RIGHT fuel selector has no crossfeed — each engine feeds from one tank only. Before descent, verify fuel quantity in each tank, plan which tank you will use for approach and landing, and switch tanks before entering the descent. Do not fly the pattern or final approach on a marginal fuel tank. At KTPA, the off-field environment is dense urban development — a forced landing is marginal at best. An engine failure on approach to Runway 19R means a forced landing into that development, not a safe field landing. Fuel tank switching is the entire lesson.
Debrief — teaching points
The Piper Arrow has a LEFT / RIGHT fuel selector with no crossfeed — each tank is independent.
Unlike some aircraft with a crossfeed system, the Arrow's fuel selector is binary: LEFT feeds from the left tank only, RIGHT feeds from the right tank only. There is no BOTH position. This means fuel tank switching is not optional — it is a critical part of flight planning and descent management. If you fly the entire flight on one tank and that tank runs dry, the engine quits. There is no backup. Verify fuel quantity in each tank before flight and plan tank switching intervals during cruise.
Fuel tank switching should be planned and executed at regular intervals during cruise, not left to chance.
A common practice is to switch tanks every 30 minutes or every 50 gallons burned, whichever comes first. This ensures balanced fuel consumption and prevents one tank from running dry while the other still has fuel. Document your tank switches in your flight log or on a notepad. Before descent, verify fuel quantity in each tank and plan which tank you will use for approach and landing. Do not enter the pattern without a clear fuel plan.
Before descent, verify fuel quantity by checking the fuel gauges and, if possible, visually confirming the sight gauge.
Fuel gauges in general aviation aircraft are notoriously unreliable — they can read high, read low, or read nothing at all. The only reliable way to verify fuel on board is a visual inspection using the sight gauge (if equipped) or a dip stick. Before descent, take 30 seconds to verify fuel quantity. If the gauges read 10 gallons but the sight gauge shows 5 gallons, trust the sight gauge. This simple check can prevent fuel starvation.
Lean the mixture aggressively during cruise to reduce fuel burn and extend range.
The Piper Arrow's Lycoming IO-360 is fuel-injected and responds well to mixture leaning. At altitude (above 3,000 ft MSL), lean the mixture to the point where the engine begins to run rough, then enrich slightly. This reduces fuel burn from 12 gal/hr to 8–10 gal/hr, extending your range and giving you more fuel margin. Leaning is not optional at altitude — it is a critical part of fuel management.
Before entering the pattern, switch to the tank with the most fuel and verify the switch.
Before beginning descent, identify which tank has the most fuel and plan to use that tank for approach and landing. Switch to that tank before entering the descent. Verify the switch by observing the fuel flow indicator or engine response. Do not fly the pattern or final approach on a marginal fuel tank. If the engine fails on final approach at 400 ft AGL, there is no time to troubleshoot or switch tanks — you will land in whatever is below you.
At KTPA, the off-field environment is dense urban development — a forced landing is marginal at best.
KTPA is surrounded by dense residential and commercial development. The off-field environment off Runway 19R's departure end (heading 182°) is mostly dense development, medium development, and pasture/hay — marginal at best for a forced landing. An engine failure on approach to Runway 19R means a forced landing into that development, not a safe field landing. Fuel tank discipline is not a luxury — it is a survival issue.
The Arrow's retractable gear and constant-speed prop add workload in an emergency — prioritize engine troubleshooting.
The Arrow is a complex aircraft: retractable gear, constant-speed prop, and fuel-injected engine. In an emergency, you have multiple systems to manage. If the engine fails on approach, your priorities are: (1) maintain airspeed (79 KIAS best glide), (2) extend the landing gear (if not already down), (3) troubleshoot the engine (fuel selector, mixture, fuel pump), and (4) plan the forced landing. Do not get distracted by the prop or other systems — focus on the engine and the landing.
Built from the real accident record
Scenario built from NTSB ERA13LA111 (2013 PA-28R fuel exhaustion / missed approaches), WPR24LA167 (2024 fuel tank mismanagement / starvation), GAA19CA534 (2019 PA-28 fuel selector error / forced landing), WPR12LA023 (2011 Cessna 185 fuel selector discipline), and CEN25LA081 (2025 PA-24 fuel mismanagement on approach). Post-maintenance engine-failure precedents: CEN22FA419, ERA22FA261 (PA-28R oil starvation / maintenance defects). Real events occurred at other airports — NOT at KTPA.
NTSB reports: CEN22FA419 · ERA22FA261 · ERA13LA111 · WPR12FA058 · WPR24LA167 · GAA19CA534 · WPR12LA023 · CEN25LA081
ACS tasks: PA.V.A — Preflight Inspection · PA.V.B — Cockpit Management / Automation · PA.VI.A — Engine Starting / Systems Preflight · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors · PA.II.F — 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 Arrow scenarios · More scenarios at KTPA