Total Power Loss on Approach to Clearwater Air Park
Engine failure in a fuel-injected Cirrus SR20 over dense development — CAPS deployment and forced-landing decision at low altitude
The scenario
Approaching Clearwater Air Park (KCLW), Clearwater, FL — Runway 34 in use, elevation 71 ft MSL. You are on a local VFR flight, returning from a 1.5-hour cross-country to a nearby field. Fuel state: left tank 12 gallons, right tank 8 gallons — total 20 gallons usable. You burned roughly 10 gallons per hour in cruise at 5,500 ft MSL; the math is tight but legal. The field is non-towered (CTAF 122.8); you will self-announce on downwind and final.
It is a warm, hazy Florida afternoon: OAT 31°C, altimeter 29.91, visibility 8 SM in light haze. Scattered thermals rising off the development around the field. You are descending through 2,000 ft MSL on a southwesterly heading, about 4 nm from KCLW, planning a straight-in approach to Runway 34 (heading 335°). Engine running normally, all systems green on the Avidyne glass panel.
Aircraft: Cirrus SR20, solo, within weight and balance limits. Continental IO-360-ES fuel-injected engine, constant-speed prop, fixed gear, glass panel (Avidyne Perspective). The airplane was last serviced 3 weeks ago; a routine 50-hour inspection was completed, including oil change and fuel system inspection. No squawks were written up.
Pilot: you — a Private pilot, 180 hours total, 40 hours in type (SR20). You are current and have made 6 approaches to KCLW in the past 2 months. You are familiar with the field's non-towered environment and the dense development surrounding it. You did a thorough preflight, including fuel quantity check (visually confirmed both tanks), and you ran the engine-start checklist. Nothing seemed amiss.
At 1,500 ft MSL, 3 nm from the field, you reduce power to 1,500 RPM for descent. The engine is smooth. You are planning a 500 fpm descent to arrive at pattern altitude (1,000 ft MSL) about 2 nm out, then a standard left downwind for Runway 34.
- {'label': 'Field', 'value': 'KCLW · Clearwater Air Park'}
- {'label': 'Runways', 'value': '16/34'}
- {'label': 'Elevation', 'value': '71 ft'}
- {'label': 'Aircraft', 'value': 'SR20'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
Before we get into the decision tree — what do you know about engine failure in the SR20 and CAPS deployment? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB CEN19LA331 (2019): A Cirrus SR20 experienced total engine power loss due to fatigue failure of the fuel line from the fuel manifold to the No. 1 cylinder. The pilot was at 2,500 ft AGL when power was lost. The pilot deployed CAPS and made a controlled descent into a cypress marsh. The pilot survived with minor injuries. The probable cause was the fatigue failure of the fuel line — a mechanical defect that could not have been detected by preflight inspection.
NTSB MIA06LA067 (2006): A Cirrus SR20 experienced total engine power loss on downwind approach due to catastrophic failure from cylinder detonation and excessive blow-by caused by low oil level. The pilot declared an emergency and attempted to land on the runway, but the aircraft overran and struck a ditch. The probable causes were inadequate engine maintenance (low oil level not detected) and inadequate service bulletin guidance for detecting cylinder detonation. The pilot survived, but the accident was preventable through proper preflight inspection.
The regional precedents (WPR24LA167, GAA19CA534, WPR12LA023) all involved fuel starvation from improper fuel tank selection or failure to switch tanks during descent. In the SR20, the fuel selector is LEFT / RIGHT with no BOTH position — fuel starvation from tank selection error is a known failure mode. However, in this scenario, the engine failure is mechanical (fuel-line fatigue or oil starvation), not fuel-selection error.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Clearwater Air Park. KCLW has its own accident history (see field dominant patterns: forced landing 22.2%, loss of control 18.5%, gear-up landing 18.5%), but these specific NTSB events happened elsewhere. The scenario is localized to KCLW to make the off-field environment (dense development) and the non-towered airspace real and consequential for you as a student here.
The consistent thread across all these events: total engine power loss in the SR20 is survivable if you recognize it early, establish best glide (96 KIAS), and either reach an airport or deploy CAPS at adequate altitude. The SR20's CAPS system is the primary response to loss of control, unrecoverable spin, and engine failure with no safe landing site — it is not a last resort, it is the design solution. Preflight inspection (oil level, fuel quantity, fuel line integrity) is the only defense against mechanical failure.
Key lesson — In the SR20, total engine power loss at low altitude over dense development is a CAPS scenario. Deploy CAPS at 1,000–1,500 ft AGL and descend under control into the safest landing area available. If you have sufficient altitude and distance to reach an airport, establish best glide (96 KIAS) and commit to the landing. The SR20's glide ratio (9:1) and constant-speed prop give you significant glide distance — use it. At KCLW, the non-towered environment means you self-announce and control your own approach — no ATC delays or complications. Preflight inspection is your only defense against mechanical failure; if the engine fails despite a thorough preflight, CAPS is your lifeline.
Debrief — teaching points
CAPS is the PRIMARY response to engine failure with no safe landing site, not a last resort.
The SR20's ballistic recovery parachute (CAPS) is certified and designed as the primary response to loss of control, unrecoverable spin, and engine failure when no safe landing site is within glide range. At 1,500 ft AGL over dense development with a dead engine, CAPS deployment is the correct decision — not a panic move, not a failure of airmanship. CAPS requires a minimum deployment altitude of roughly 1,000 ft AGL to provide adequate descent rate and landing distance. Below 1,000 ft AGL, CAPS is no longer a safe option. Know your CAPS deployment altitude window and use it.
Best glide in the SR20 is 96 KIAS — establish it immediately on engine failure.
The SR20's best glide speed is 96 KIAS at 3,000 lb gross weight (87 KIAS at 2,500 lb). This speed maximizes glide distance and gives you the most time and distance to reach an airport or identify a landing site. On engine failure, lower the nose immediately to 96 KIAS and trim for hands-off flight. The SR20's glide ratio is roughly 9:1 — from 1,500 ft AGL you have roughly 13,500 ft of glide distance, enough to reach KCLW from 3 nm out. Know your glide speed and establish it without hesitation.
The SR20's fuel selector is LEFT / RIGHT — no BOTH position. Fuel starvation from improper tank selection is a known failure mode.
Unlike Cessnas (which have BOTH), the SR20 has LEFT / RIGHT fuel selector with no BOTH position. Fuel starvation from switching to an empty or low tank is a documented failure mode in the SR20 and similar aircraft. Plan your fuel tank switches in advance (e.g., at +1 hr, +3 hr intervals) and verify the selector position matches your intended tank before descent. If engine power is lost and you suspect fuel starvation, switch to the opposite tank immediately — do not troubleshoot. In this scenario, the engine failure is mechanical (fuel-line fatigue or oil starvation), not fuel-selection error, but fuel-selector discipline is a critical habit.
Preflight inspection is your only defense against mechanical engine failure.
NTSB CEN19LA331 involved fatigue failure of a fuel line — a defect that could not have been detected by visual preflight inspection. NTSB MIA06LA067 involved low oil level that should have been caught in preflight but was not. The SR20's Continental IO-360-ES is a robust engine, but fuel-line integrity and oil level are critical. Check the oil level with the dipstick (not just the sight glass), visually inspect fuel lines for cracks or corrosion, and confirm fuel quantity by dipping the tanks (not just the glass gauges). If the engine fails despite a thorough preflight, it is a mechanical defect, not pilot error — and CAPS is your lifeline.
KCLW is non-towered (CTAF 122.8) — you self-announce and control your own approach.
Clearwater Air Park is a non-towered field; there is no tower, no ATC clearance, and no approach control. You announce your position and intentions on CTAF 122.8 and listen for other traffic. In an engine-failure scenario, this is an advantage: you do not need to wait for ATC clearance or follow assigned vectors. You can turn directly toward the field, announce your emergency, and execute the approach you choose. Announce early and often: 'Clearwater traffic, Cirrus [N-number], engine failure, descending to pattern altitude, straight-in approach Runway 34.' Other pilots will hear you and stay clear.
Built from the real accident record
Scenario inspired by NTSB CEN19LA331 (2019 SR20 fuel-line fatigue failure, CAPS deployment, forced landing in marsh) and MIA06LA067 (2006 SR20 catastrophic engine failure on approach due to low oil level). Regional precedents: WPR24LA167 (fuel starvation from improper tank selection), GAA19CA534 (fuel starvation on descent), WPR12LA023 (fuel selector error during descent). Real events occurred at other airports — NOT at KCLW.
NTSB reports: CEN19LA331 · MIA06LA067 · WPR24LA167 · GAA19CA534 · WPR12LA023
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.A — Preflight Assessment · PA.II.B — Engine Starting / Systems Preflight
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 SR20 scenarios · More scenarios at KCLW