The Turn to Final
Base-to-final stall/spin in a Piper Warrior — a low-altitude recovery window that closes in seconds
The scenario
Departing Clearwater Air Park (KCLW), Clearwater, FL — Runway 34, a touch-and-go practice flight. Elevation 71 ft MSL. KCLW is a non-towered field (CTAF 122.8); you self-announce on the common frequency. The field is Class G airspace, overlain by Tampa Class B above 3,000 ft MSL.
It is a clear, calm Florida morning: OAT 22°C, winds calm to 3 knots, visibility 10+ SM. A textbook VFR day. You have completed two touch-and-go landings on Runway 34 (heading 335°). The third approach is stable: you are on a 3-degree glide slope, airspeed 70 KIAS on downwind, descent rate 300 fpm. The runway is made.
You are now turning base — a left turn from downwind (heading roughly 155°) to final (heading 335°). You are at 400 ft AGL. The turn is shallow and coordinated. But as you roll out toward final, you notice the airspeed is dropping: 68 KIAS, 66 KIAS, 64 KIAS. The descent rate is increasing. The control feel is becoming mushy.
Aircraft: Piper PA-28-161 Warrior, solo, within limits. Carbureted Lycoming O-320-D, fixed-pitch prop, fixed gear, steam panel. The airplane is airworthy; nothing was written up. You are a Private pilot, current, roughly 180 hours total. You have done dozens of touch-and-go landings, but never at KCLW before today.
The off-field environment off Runway 34's departure end (heading 335°) is low-density development, medium development, and open developed areas (parks, large lots). Off Runway 16's departure end (heading 155°) is dense development, low-density development, and medium development. There is no open field, no water, no road. The developed area is the off-field reality. A forced landing here is into built-up terrain.
- {'label': 'Field', 'value': 'KCLW · Clearwater Air Park'}
- {'label': 'Runways', 'value': '16/34'}
- {'label': 'Elevation', 'value': '71 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-161'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
Before we get into the decision tree — what do you know about stall recognition and recovery in the Piper Warrior at low altitude? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB NYC08FA237 (2008): A Piper PA-28-161 on an instructional flight stalled during initial climb from a touch-and-go landing at Newport State Airport, Rhode Island. The flight instructor failed to initiate a go-around during a high approach and made inadequate remedial action during the attempted touch-and-go. The airplane impacted trees about 1,000 feet beyond the runway. The probable cause was the instructor's failure to initiate a go-around and inadequate remedial action.
NTSB NYC06FA029 (2005): A Piper PA-28-161 on a touch-and-go practice flight stalled during the go-around after landing at low altitude. The flight instructor failed to maintain adequate airspeed, resulting in an inadvertent stall and impact with trees and terrain. The probable cause was the instructor's failure to maintain airspeed, which resulted in an inadvertent stall and subsequent impact with trees and terrain.
NTSB CEN12FA188 (2012): A Piper PA-28-161 stalled during takeoff from a soft grass airstrip with a quartering tailwind and struck trees at the departure end of the runway. The probable cause was the pilot's failure to maintain airplane control during takeoff, resulting in an aerodynamic stall and collision with trees. Contributing factors included inadequate preflight planning for soft-field conditions and failure to obtain a weather briefing.
NTSB CHI05LA226 (2005): A Piper PA-28-161 lost engine power due to left magneto failure during initial climb after takeoff and subsequently stalled. The probable cause was loss of engine power while maneuvering due to partial failure of the left magneto, with contributing factors including the instructor's failure to maintain sufficient airspeed to avoid a stall.
Regional precedents (FTW91DRG06, SEA07CA125, ERA12CA019, ERA10CA300) show a consistent pattern: base-to-final stalls in light aircraft result in fatalities in the vast majority of cases. The common thread is failure to maintain airspeed during the turn, failure to recognize stall warning signs, and failure to execute an immediate go-around. The recovery window from a stall at 400 ft AGL is measured in seconds — not minutes.
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_INFLIGHT 18.5%, GEAR_UP_LANDING 18.5%), but these specific fatal events happened elsewhere. The scenario is localized to KCLW to make the off-field environment real and consequential for you as a student here.
The consistent lesson across all these events: the base-to-final turn is a high-risk stall environment. The turn increases wing loading (G-forces), requiring higher airspeed to maintain lift. The stall warning signs — mushy control feel, buffeting, loss of control authority — appear BEFORE the stall breaks. The correct decision is an immediate go-around. There is no recovery from a developed spin at 300 ft AGL.
Key lesson — The base-to-final turn is a high-risk stall environment. Maintain airspeed (minimum 70 KIAS on base, 65 KIAS on final in the Piper Warrior). Recognize stall warning signs — mushy control feel, buffeting, loss of control authority. If airspeed is dropping and cannot be recovered, execute an immediate go-around: full power, level wings, climb back to pattern altitude. A go-around is not a failure; it is the correct decision when the approach is unstable. There is no recovery from a developed spin at 300 ft AGL.
Debrief — teaching points
The base-to-final turn is a high-risk stall environment.
During the base-to-final turn, the airplane is in a bank, descending, and often at reduced power. The turn increases wing loading (G-forces), requiring higher airspeed to maintain lift. In a 15-degree bank, the stall speed increases by roughly 2%. In a 20-degree bank, it increases by roughly 6%. At 400 ft AGL in a turn, the margin between flying and stalling is thin. Maintain a minimum of 70 KIAS on downwind and base, and 65 KIAS on final (Vref for the Warrior). Do not allow airspeed to decay below these targets.
Stall warning signs appear BEFORE the stall breaks.
The Piper Warrior will give you warning before it stalls: a mushy control feel (the elevator becomes less responsive), a buffeting or vibration (the wing is approaching stall angle), and a loss of control authority (the airplane no longer responds crisply to control inputs). These signs appear 5–10 knots above the stall speed. If you feel any of these signs on base or final, the correct response is an immediate go-around. Do not attempt to land. Do not try to recover by pitching up — that will make the stall worse. Apply full power, level the wings, and climb back to pattern altitude.
A go-around is not a failure — it is airmanship.
Every pilot will encounter an unstable approach at some point. The correct decision is a go-around. Climbing back to pattern altitude, re-entering the downwind, and setting up another approach is the safe, professional response. The NTSB data shows that pilots who attempt to salvage an unstable approach by stretching the glide or pitching up to slow the descent end up stalling at low altitude. The pilots who execute a go-around live to fly another day. A go-around is not a failure; it is the correct decision.
The recovery window from a stall at 400 ft AGL is measured in seconds.
If the stall breaks at 400 ft AGL, you have roughly 8–10 seconds before ground impact. Stall recovery requires: (1) reduce bank angle to level wings, (2) lower the nose to regain airspeed, (3) apply full power. If you are in a spin, apply opposite rudder to stop the rotation, lower the nose, and apply full power. A fully developed spin from 400 ft AGL is not recoverable. The correct decision is to prevent the stall in the first place — maintain airspeed, recognize the warning signs, and execute a go-around.
The Piper Warrior is a forgiving airplane, but it will stall if you let it.
The Warrior's semi-tapered wing is docile and forgiving. It will not snap-stall or spin easily. But it will stall if you let the airspeed decay below stall speed in a turn. The stall will be gentle — the wing will drop, the nose will pitch down — but at 400 ft AGL, a gentle stall is still fatal. Respect the airplane's limitations. Maintain airspeed. Recognize the warning signs. Execute a go-around if the approach is unstable.
Built from the real accident record
Scenario built from NTSB NYC08FA237 (2008 PA-28-161 stall during touch-and-go, instructor failure to go-around), NYC06FA029 (2005 PA-28-161 stall on go-around, low-altitude recovery failure), and regional base-to-final stall precedents FTW91DRG06, SEA07CA125, ERA12CA019, ERA10CA300. Localized to KCLW.
NTSB reports: CEN12FA188 · NYC08FA237 · NYC06FA029 · CHI05LA226 · FTW91DRG06 · SEA07CA125 · ERA12CA019 · ERA10CA300
ACS tasks: PA.I.F — Weather Information · PA.IV.A — Normal Approach and Landing · PA.IV.B — Forward Slip to a Landing · PA.V.A — Stall Recognition and Recovery · PA.V.B — Spin Awareness · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors
Relevant FARs: §91.3 · §91.13 · §91.119
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 Warrior scenarios · More scenarios at KCLW