Fuel Selector Confusion on Descent
Engine power loss from improper fuel tank selection in a high-performance Cirrus — dense development surrounds the field, and the decision window is seconds
The scenario
Departing Clearwater Air Park (KCLW), Clearwater, FL — Runway 34, on a personal cross-country flight. Elevation 71 ft MSL. It is a clear, calm morning: OAT 22°C, altimeter 30.02, light winds from the northeast. VFR conditions throughout. You are returning to KCLW after a 2.5-hour flight to a nearby field and back. Fuel state: left tank 18 gal, right tank 22 gal — total 40 gal usable, well within limits for the return leg.
The Cirrus SR22 is a high-performance, fuel-injected constant-speed airplane. The Continental IO-550-N produces 310 hp. The fuel system has LEFT and RIGHT tanks — no BOTH position. The fuel selector must be actively managed: you switch between tanks, not set it and forget it. The POH recommends switching tanks every 1 hour to maintain lateral balance and to monitor fuel flow from each tank.
You are now on descent into KCLW from 3,500 ft MSL, 8 nm out, heading 155° for Runway 16. The field is non-towered (CTAF 122.775). You are in Class G airspace; the overlying Tampa Class B begins at 3,000 ft MSL. Off-field environment: dense development, low-density development, and medium development surround the field on all sides. There is no open field, no water, no alternate landing surface. The runway is your only option.
Aircraft: Cirrus SR22, solo, within limits. Fuel selector currently on RIGHT (you switched to the right tank 45 minutes ago to balance consumption). Engine instruments are normal. You have not yet briefed the descent or confirmed fuel state on the approach.
Pilot: you — a Private pilot with 180 hours total, 40 hours in the SR22. You are familiar with the fuel selector but have not yet developed a habit of verifying tank selection during phase transitions. You are focused on the descent checklist and have not cross-checked the fuel selector position against your fuel plan.
- {'label': 'Field', 'value': 'KCLW · Clearwater Air Park'}
- {'label': 'Runways', 'value': '16/34'}
- {'label': 'Elevation', 'value': '71 ft'}
- {'label': 'Aircraft', 'value': 'SR22'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
Before we get into the decision tree — what do you know about fuel management in the SR22? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB CEN21LA057 (2020): A Cirrus SR22 on approach experienced erratic high oil temperature indications. The pilot improperly adjusted the engine mixture control in response, resulting in total loss of engine power. The pilot deployed the ballistic parachute for a survivable landing. The accident resulted from the pilot's improper adjustment of the engine mixture control, with a contributing factor being a disconnected oil temperature connector damaged during recent maintenance. The pilot survived because CAPS was deployed.
NTSB ERA20LA064 (2020): A Cirrus SR22 on a personal cross-country flight experienced total engine power loss due to camshaft fatigue failure caused by a manufacturing defect. The pilot deployed CAPS and made a survivable landing in trees. The pilot survived because the ballistic parachute was available and deployed.
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. This airplane did not have CAPS.
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 survived but the aircraft was damaged.
The consistent thread across all these events: fuel tank selection in aircraft with LEFT/RIGHT selectors (no BOTH position) is a critical decision point. The SR22's fuel selector must be actively managed. Switching tanks without verifying the new tank has adequate fuel, or failing to verify selector position during phase transitions, is the mechanism for fuel starvation. The SR22 has CAPS — use it when engine power is lost at low altitude with no safe landing option. The real accidents cited above occurred at other airports and in other aircraft — NOT at KCLW. KCLW's dominant accident pattern includes FORCED_LANDING (22.2%), LOSS_OF_CONTROL_INFLIGHT (18.5%), and GEAR_UP_LANDING (18.5%) — but this scenario is localized to KCLW to make the off-field environment real and consequential for you as a student here.
The off-field environment at KCLW is dense development on all sides. There is no open field, no water, no alternate landing surface. Runway 16/34 is the only option. An engine failure on approach to KCLW with insufficient altitude to reach the runway leaves only one decision: CAPS deployment or an uncontrolled forced landing in trees/buildings. The correct answer is CAPS.
Key lesson — In the SR22, fuel tank selection is a critical decision point. The LEFT/RIGHT selector must be actively managed — verify selector position and fuel quantity in both tanks during every phase transition, especially before descent. At low altitude with a dead engine and no safe landing option, CAPS deployment is the primary recovery tool — not an attempt to stretch the glide to the runway. KCLW is surrounded by dense development; there is no alternate landing surface. Fuel verification during descent is the entire lesson.
Debrief — teaching points
The SR22 fuel selector has LEFT and RIGHT positions — there is no BOTH.
Unlike Cessnas with a BOTH position, the SR22 requires active fuel tank selection. You must choose LEFT or RIGHT at all times. The engine draws fuel from the selected tank only. If you select a tank with insufficient fuel while the other tank has usable fuel, the engine will quit — fuel starvation, not fuel exhaustion. This is a critical difference from other aircraft. Develop a habit of verifying selector position during every phase transition: preflight, takeoff, climb, cruise, descent, approach, landing.
Verify fuel selector position and quantity before every descent.
The POH recommends switching tanks every 1 hour to maintain lateral balance and to verify fuel flow from each tank. Before descent, verify: (1) fuel selector position matches your intended tank, (2) fuel quantity in both tanks, (3) fuel flow is normal on the selected tank. Do not assume the selector is where you think it is. A glance at the glass panel takes 3 seconds. A power loss at 600 ft AGL over dense development takes 30 seconds to resolve — and you may not have 30 seconds.
When you switch tanks, observe the brief fuel flow dip and stabilization.
When you move the fuel selector from one tank to the other, the fuel flow will dip briefly as the selector moves, then stabilize on the new tank. This is normal. If the fuel flow does not stabilize or remains zero, you have a problem: either the selected tank is empty, or there is a fuel system malfunction. Do not ignore a fuel flow anomaly — diagnose it immediately.
Fuel starvation is different from fuel exhaustion — and it is preventable.
Fuel exhaustion means you have run out of fuel entirely. Fuel starvation means the engine quits because the selected tank is empty while the other tank has usable fuel. Starvation is preventable: verify selector position and fuel quantity before descent. Exhaustion is a planning failure: you did not calculate fuel correctly or did not monitor consumption. Both result in a dead engine at low altitude. The SR22's LEFT/RIGHT selector makes starvation a real risk — manage it.
At KCLW, dense development surrounds the field on all sides — there is no alternate landing surface.
Off Runway 16 (climb-out heading 155°): dense development, low-density development, medium development. Off Runway 34 (climb-out heading 335°): low-density development, medium development, open developed (parks/large lots). There is no open field, no water, no road suitable for landing. Runway 16/34 is your only option. An engine failure on approach with insufficient altitude to reach the runway leaves only one decision: CAPS deployment or an uncontrolled forced landing in trees/buildings. CAPS is the correct answer.
CAPS deployment is the primary recovery tool for unrecoverable situations — not a last resort.
The Cirrus CAPS (ballistic recovery parachute) is designed for total engine failure, unrecoverable spin, loss of control, and other unrecoverable situations. At low altitude with a dead engine and no safe landing option, CAPS deployment is the correct decision — not an attempt to stretch the glide to the runway. The parachute brings you down at approximately 17 ft/sec in a controlled descent. Survival rates in CAPS deployments are significantly higher than in uncontrolled forced landings. Know the CAPS deployment procedure and the altitude limitations (Vpd max 133 KIAS, minimum altitude for safe deployment varies by conditions). Deploy early rather than late.
Built from the real accident record
Scenario built from NTSB CEN21LA057 (2020 SR22 improper mixture adjustment / power loss), ERA20LA064 (2020 SR22 engine failure / CAPS deployment), CEN20LA020 (2019 SR22 detonation / power loss), CEN19LA320 (2019 SR22 connecting rod failure), and fuel-mismanagement precedents WPR24LA167, GAA19CA534, WPR12LA023, ERA17LA205. Localized to KCLW.
NTSB reports: CEN21LA057 · ERA20LA064 · CEN20LA020 · CEN19LA320 · WPR24LA167 · GAA19CA534 · WPR12LA023 · ERA17LA205
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.V.A — Preflight Inspection · PA.V.B — Cockpit Management
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 Cirrus SR22 scenarios · More scenarios at KCLW