Fuel Planning Failure on the Descent

Departing Brooksville–Tampa Bay Regional Airport (KBKV), Brooksville, FL — Runway 09, on descent from cruise altitude after a 3.5-hour cross-country flight. Field elevation 76 ft MSL. You are 45 nm out, descending through 4,500 ft MSL, and you have just checked the fuel gauges for the first time since cruise.

The flight plan was filed for 4.5 hours block time. You departed with full tanks (48 gallons usable in a Piper Arrow PA-28R-200) and planned a fuel reserve of 45 minutes. The cruise burn was 11 GPH at 65% power. You did not file an alternate airport or brief a diversion plan — the weather is VFR all the way, and KBKV is your destination.

Now, at 45 nm out and beginning descent, the fuel gauges read: Left tank 8 gallons, Right tank 6 gallons. Total remaining: 14 gallons. At 11 GPH cruise burn, that is 1.3 hours of fuel. At approach and landing power, burn will be higher — roughly 14–16 GPH. You are 45 minutes out at descent speed. The math does not work.

The fuel selector is on RIGHT tank (6 gallons). You have not switched tanks since cruise — a critical oversight in a Piper Arrow, where fuel starvation from tank mismanagement is a signature failure mode. You did not monitor fuel consumption against the flight plan. You did not lean the mixture aggressively in cruise. You did not plan a diversion. You are now in a fuel emergency 45 minutes from the destination.

Aircraft: Piper PA-28R-200, solo, within limits. Lycoming IO-360 fuel-injected engine, constant-speed prop, retractable gear. KBKV tower is active (part-time 0700–2200 local; it is 1430 local, tower is open). Class D airspace, ceiling 1,500 ft MSL. Overlying Tampa Class B 6,000–10,000 ft MSL.

Pilot: you — a Commercial pilot, current, roughly 800 hours total. You are instrument-rated but this is a VFR flight. You have logged 120 hours in the Arrow. You did not brief a fuel emergency scenario before departure. You did not plan an alternate. You are now discovering the fuel situation on descent.

NTSB WPR21FA352 (2021, FATAL): A Piper PA-28R-200 on a personal cross-country flight experienced total engine power loss due to fuel exhaustion during descent to the destination airport. The pilot had not filed an alternate airport, had not monitored fuel consumption against the flight plan, and did not declare an emergency until the engine quit. The airplane impacted terrain in a forced landing; the pilot was fatally injured. The probable cause was the pilot's improper fuel planning for the flight.

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. The pilot was operating in low IMC, did not land at any of the three airports with adequate instrument approaches, and delayed declaring a fuel-related emergency. The airplane impacted terrain in a forced landing; the pilot was fatally injured. The probable cause was the pilot's failure to land at multiple airports equipped with adequate instrument approaches and his delay in declaring a fuel emergency.

NTSB ERA13CA362 (2013): A Piper PA-28R-180 on a night personal cross-country flight without a weather briefing encountered low visibility at the destination, executed a missed ILS approach, diverted to an alternate airport, and exhausted fuel before reaching it. The pilot did not obtain weather briefings at intermediate stops and did not plan an alternate airport. The airplane made a forced landing in rough terrain; the pilot survived. The probable cause was inadequate pre-flight and in-flight planning and failure to obtain weather briefings.

The consistent thread across all these accidents: fuel exhaustion in the Piper Arrow results from a combination of poor fuel planning, inadequate monitoring during cruise, failure to switch tanks regularly, and delay in declaring an emergency. The Piper Arrow's LEFT/RIGHT fuel selector (not BOTH) makes fuel starvation from tank mismanagement a signature failure mode. Early declaration of a fuel emergency, aggressive leaning of the mixture, and early diversion to a nearby airport are the interventions that prevent fatal outcomes.

NTSB DEN07LA166 (2007): A Piper PA-28R-201T experienced an in-flight fire during climb from Taos Regional Airport when an unsecured B-nut fitting on the fuel return line loosened, causing fuel spillage and engine fire. The pilot performed a wheels-up landing in rough terrain. The probable cause was the unsecured B-nut fitting. This accident illustrates a different fuel-system failure mode — post-maintenance fuel-system integrity — but the outcome (forced landing) is the same.

The real accidents cited above occurred at other airports and in other aircraft — NOT at Brooksville–Tampa Bay Regional Airport (KBKV). KBKV has its own accident history (see field dominant patterns: hard landings, forced landings, runway excursions), but these specific fuel-exhaustion events happened elsewhere. The scenario is localized to KBKV to make the off-field environment real and consequential for you as a student here.

Off Runway 09 at KBKV (heading 90°), the off-field environment is mostly open developed (parks/large lots), pasture/hay, and medium development — good forced-landing options. Off Runway 27 (heading 270°), the off-field environment is low-density development, pasture/hay, and grassland — also good. Off Runway 03 (heading 26°), the environment is pasture/hay, open developed, and medium development — good. Off Runway 21 (heading 206°), the environment is evergreen forest, pasture/hay, and medium development — more challenging. The point: KBKV is surrounded by reasonable forced-landing terrain, but you should never need it if you plan fuel correctly.