The Turn to Final
Base-to-final stall/spin in a Piper Warrior — low altitude, crosswind, and the decision to go around
The scenario
Departing Peter O Knight Airport (KTPF), Tampa, FL — Runway 22, landing pattern in progress. Field elevation 8 ft MSL. You are a Private pilot with roughly 180 hours total, 45 hours in the Piper Warrior. This is a solo flight; you are current and within your personal minimums for VFR.
Conditions: 1400 local, VFR, scattered clouds 3,500 ft AGL, visibility 8 SM. Wind is reported from 260° at 12 knots gusting to 18 knots. Runway 22 is aligned 217° magnetic (true heading 217°). The wind is a crosswind from the left — roughly 30° off the runway heading. Gusts are present. This is workable, but the pattern will be active and the crosswind will require attention.
You have completed two touch-and-go landings on Runway 22. The first was stable and smooth. The second was a bit high on short final, but you corrected and landed safely. You are now on your third approach. You are on downwind, 500 ft AGL, airspeed 90 KIAS, flaps up, heading roughly 037° (reciprocal of runway). The base turn is coming up.
Aircraft: Piper PA-28-161 Warrior, solo, 1,800 lb gross weight, within limits. Carbureted Lycoming O-320, fixed-pitch prop, fixed gear, steam panel. Fuel selector on RIGHT tank (you switched after the second landing). Nothing was written up; the airplane is airworthy.
Pilot: you — current, 180 hours total, 45 hours Warrior time. You have practiced stalls in the Warrior with your CFI, but pattern work and crosswind landings are still building skills. You are comfortable with the airplane, but the gusts and the crosswind are at the edge of your comfort zone.
- {'label': 'Field', 'value': 'KTPF · Peter O Knight'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '8 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/spin accidents in the pattern? (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 did not provide adequate remedial action during the attempted touch-and-go. The airplane impacted trees about 1,000 feet beyond the runway. The probable cause was the flight instructor's failure to initiate a go-around during a high approach and inadequate remedial action during an attempted touch-and-go.
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 flight instructor's failure to maintain airspeed, which resulted in an inadvertent stall and subsequent impact with trees and terrain.
NTSB ERA12CA019 (2011): An Aeronca 7AC stalled and entered a spin during a left turn to the downwind leg of the traffic pattern at approximately 400 feet AGL. The pilot failed to maintain adequate airspeed during the turn, with the pilot unable to recover from the resulting dive before ground impact. The probable cause was the pilot's failure to maintain adequate airspeed during the turn.
NTSB LAX89LA222 (1989): A Grumman AA-1C aborted an approach to Runway 36 and entered a low unstable pattern in gusting crosswind conditions. The airplane stalled on final approach and impacted the ocean short of the runway. The probable cause was the pilot's failure to maintain sufficient airspeed to prevent a stall at an altitude too low for recovery.
These real accidents occurred at other airports and in other aircraft — NOT at Peter O Knight Airport (KTPF). KTPF has its own accident history dominated by forced landings and loss-of-control events. The scenario is localized to KTPF to make the off-field environment real and consequential for you as a student here. Off Runway 22 at KTPF (climb-out heading 217°), the off-field environment is mostly open water — Tampa Bay and surrounding waterways. An engine-out or stall at low altitude on the Runway 22 departure is a ditching, not a field landing.
The consistent thread across all these events: stall/spin in the pattern is a low-altitude trap. The stall develops in a turn (base, downwind, or final) when airspeed decays below the stall speed for that bank angle. At 300 ft AGL or below, there is no altitude to recover. The recovery maneuver — lower the nose and level the wings — requires 500+ feet of altitude. The decision to go around and try again is not a failure; it is the correct response to an unstable approach.
Key lesson — In the Piper Warrior, stall speed clean is 50 KIAS; in landing configuration (full flaps) it is 44 KIAS. In a turn, the stall speed increases due to load factor — in a 20° bank, stall speed is roughly 52 KIAS. At KTPF, a stall in the pattern (especially on base or final) is a low-altitude trap. The correct airspeed on final approach is 70 KIAS initial approach, reducing to 63 KIAS (Vref) on short final. Maintain this airspeed throughout the approach. If the approach becomes unstable (high, fast, slow, or in gusty conditions), go around and try again. Do not try to salvage an unstable approach at low altitude. Off Runway 22, the off-field environment is open water — a stall at low altitude is a ditching.
Debrief — teaching points
Stall speed increases in a turn due to load factor.
In level flight, the Piper Warrior stalls at 50 KIAS (clean) or 44 KIAS (full flaps). In a turn, the stall speed increases. In a 10° bank, stall speed is roughly 51 KIAS; in a 20° bank, roughly 52 KIAS; in a 30° bank, roughly 54 KIAS. The load factor (G-loading) increases with bank angle, and the stall speed increases with the square root of the load factor. At 300 ft AGL in a 20° bank at 70 KIAS, you are only 18 KIAS above stall. A gust or a further increase in bank angle will push you into the stall. Know these numbers.
Crosswind final approaches are a known risk factor for stall/spin accidents.
Crosswind final approaches require wind correction (crabbing or slipping), which distracts the pilot from airspeed management. The pilot is focused on keeping the airplane aligned with the runway and may not notice the airspeed decaying. At KTPF, Runway 22 is aligned 217° magnetic; a wind from 260° is a left crosswind. In gusty conditions, the crosswind can be challenging. Maintain airspeed as the primary focus; wind correction is secondary. If the approach becomes unstable, go around.
Maintain 70 KIAS initial approach, reducing to 63 KIAS (Vref) on short final.
In the Piper Warrior, Vref (approach speed, full flaps) is 63 KIAS. Initial approach is 70 KIAS. These speeds are in the POH for a reason — they provide adequate margin above stall speed (44 KIAS in landing configuration) while allowing a normal descent rate and landing distance. At 70 KIAS, you are 26 KIAS above stall in level flight; in a 20° bank, you are still 18 KIAS above stall. Slower than 70 KIAS on approach is asking for trouble.
An unstable approach at low altitude is a trap — go around and try again.
An unstable approach is one that is high, fast, slow, or in gusty conditions where the pilot is not confident of a safe landing. At KTPF, if you are high on short final, if the airspeed is below 70 KIAS, or if the descent rate is excessive, the correct decision is to add power, level the wings, retract flaps, and go around. The go-around is not a failure; it is airmanship. The NTSB data show that pilots who try to salvage unstable approaches at low altitude often stall and crash. Pilots who go around and try again land safely.
Stall recovery requires 500+ feet of altitude.
If a stall develops in a turn at low altitude, the recovery maneuver is to lower the nose and level the wings. This maneuver requires altitude — typically 500+ feet depending on the airplane and the severity of the stall. At 300 ft AGL or below, there is no altitude to recover. The stall/spin is unrecoverable. The only way to avoid this is to maintain adequate airspeed throughout the approach and pattern. Do not allow the airspeed to decay below 70 KIAS on approach.
Off Runway 22 at KTPF, the off-field environment is open water — a stall at low altitude is a ditching.
The off-field environment off Runway 22's departure end (heading 217°) is mostly open water — Tampa Bay and surrounding waterways. An engine-out or stall at low altitude on the Runway 22 departure is a ditching, not a field landing. This is the geographic reality of KTPF. Runway 22 is the longer runway (3,583 ft vs. 2,687 ft for Runway 18/36), but the off-field environment is water. Runway 4 (reciprocal of 22) has a climb-out over dense development — also challenging. Know the off-field environment for each runway before you depart.
Built from the real accident record
Scenario built from NTSB NYC08FA237 (2008 PA-28-161 stall during go-around), NYC06FA029 (2005 PA-28-161 stall during touch-and-go), ERA12CA019 (2011 Aeronca stall/spin in pattern turn), and LAX89LA222 (1989 low-altitude stall on final). Anonymized and localized to KTPF.
NTSB reports: CEN12FA188 · NYC08FA237 · NYC06FA029 · CHI05LA226 · LAX89LA222 · ERA10CA300 · ATL92LA146 · ERA12CA019
ACS tasks: PA.I.F — Weather Information · PA.III.A — Steep Turns · PA.III.B — Slow Flight and Stalls · PA.IV.C — Approach and Landing · PA.I.H — Human Factors
Relevant FARs: §91.3 · §91.13 · §91.303
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 KTPF