The Turn to Final — Crosswind and Commitment
Base-to-final stall/spin in a complex aircraft: airspeed, crosswind, and the margin between a go-around and a crash
The scenario
Departing Peter O Knight Airport (KTPF), Tampa, FL — Runway 22 in use, landing pattern to Runway 22. Elevation 8 ft MSL. This is a non-towered field; you self-announce on CTAF 122.8.
It is late afternoon, VFR, but the wind is gusting. ATIS reports winds 210° at 14 knots, gusting to 22 knots. Runway 22 is aligned 217° true — nearly aligned with the wind, but the gusts are creating a dynamic crosswind component as the wind direction swings. Visibility is 10 SM, scattered clouds at 3,500 ft, light turbulence in the pattern. The off-field environment off Runway 22's departure end (heading 217°) is open water — Tampa Bay. Off the other runway ends: Runway 04 (climb-out 037°) is dense development; Runway 18 and 36 are also water.
You are a commercial pilot with roughly 800 hours total, 120 hours in the Piper Arrow. You are current and proficient. This is your home field. You have flown the pattern here dozens of times. You are on a local flight — just a couple of laps in the pattern to stay sharp.
Aircraft: Piper Arrow PA-28R, solo, within limits. Retractable gear, constant-speed prop, fuel-injected Lycoming IO-360. Gear is down and locked, prop is in cruise (2000 RPM), flaps are up. You are on downwind for Runway 22 at 800 ft AGL, airspeed 95 KIAS, heading 037° (reciprocal of the runway).
You are about to turn base. The wind is gusting. You have flown this pattern a hundred times. But today the wind is stronger and more variable than usual, and you are tired — a long day of work before the flight. The margin between a normal approach and an unstable one is narrower than you think.
- {'label': 'Field', 'value': 'KTPF · Peter O Knight'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '8 ft'}
- {'label': 'Aircraft', 'value': 'PA-28R'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
Before we enter 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 ERA10CA300 (2010): A Piper PA-18-135 stalled and entered a spin during a climbing right turn on final approach when the pilot attempted to perform a 360-degree turn per ATC spacing request. The pilot was unable to recover from the spin before ground impact. The probable cause was the pilot's failure to maintain adequate airspeed during the climbing turn, which exceeded the airplane's performance limits at low altitude. The lesson: recognize when a maneuver (climbing turn, steep descent, slow approach) exceeds safe margins and request alternative spacing or execute a go-around.
NTSB LAX89LA222 (1989, fatal): A Grumman AA-1C on approach to a coastal airport aborted the initial approach and entered a low unstable pattern in gusting crosswind conditions. The pilot stalled on final approach and impacted the water 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. The lesson: recognize unstable approach conditions (low altitude, gusting winds, steep bank) and commit to a go-around rather than stretching the approach.
NTSB ATL92LA146 (1992): A Cessna 172 stalled 15 feet above ground during short final approach and crashed short of the runway surface. The probable cause was the pilot's failure to maintain flying speed during final approach. The lesson: maintain flying speed throughout final approach; recognize early stall warning signs and execute a go-around before reaching ground effect.
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 was 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. The lesson: maintain adequate airspeed during pattern turns, especially downwind-to-base transitions; recognize stall entry symptoms (wing drop, loss of control) and execute immediate recovery (power, level wings, lower nose).
NTSB ERA21FA189, ERA15FA299, ERA14FA002, ERA13FA144 (PA-28R spatial disorientation and loss of control): These accidents involved Piper Arrow and PA-28R variants in night VFR, IMC, and high-workload situations. The common thread: loss of control due to spatial disorientation, inadequate airspeed management, and failure to recognize unstable flight conditions. The lesson: maintain situational awareness, manage workload, and recognize when the approach is unstable.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Peter O Knight Airport (KTPF). KTPF's own accident corpus shows FORCED_LANDING (19.4%), LOSS_OF_CONTROL_INFLIGHT (16.7%), and STALL_SPIN (8.3%) as dominant patterns. This scenario is localized to KTPF to make the off-field environment real and consequential: Runway 22's departure end is open water (Tampa Bay), and the pattern turns are over a non-towered field with gusting wind. The decision to go around or commit to an unstable approach has real consequences at this field.
The consistent thread across all these events: stall/spin accidents in the pattern are almost always fatal because the altitude is too low for recovery. The defense is recognizing the unstable approach early — low airspeed, steep bank, gusting wind, low altitude — and executing a go-around before the stall occurs. A go-around is not a failure; it is the correct decision when the approach becomes unstable.
Key lesson — In the Piper Arrow, stall/spin accidents in the pattern occur when the pilot commits to an unstable approach at low altitude. The defense is recognizing the unstable approach early and executing a go-around. Maintain adequate airspeed (at least Vref 75 KIAS on final, with a margin above Vs0 55 KIAS), avoid steep banks at low altitude, and recognize when gusting wind or low altitude makes the approach marginal. If the approach becomes unstable — low airspeed, steep bank, high descent rate, low altitude — go around. If a stall does occur at low altitude, recover immediately (power, level wings, lower nose) and land the airplane. At KTPF, the off-field environment off Runway 22 is open water; an uncontrolled descent in the pattern is a ditching, not a field landing.
Debrief — teaching points
Stall speed increases in a turn — the margin above stall shrinks at low altitude.
In the Piper Arrow, stall speed in landing configuration (gear down, flaps 40°) is 55 KIAS (Vs0). But in a turn, the stall speed increases: at 15° bank it is roughly 57 KIAS (1.04 × Vs0), at 20° bank it is roughly 58 KIAS (1.07 × Vs0), and at 30° bank it is roughly 63 KIAS (1.15 × Vs0). On final approach at 75 KIAS (Vref), a 15° bank gives an 18-knot margin above stall. But if you slow to 65 KIAS and increase the bank to 20°, the margin shrinks to 7 knots. At 800 ft AGL, a 7-knot margin is not enough. Maintain Vref (75 KIAS) on final and avoid steep banks at low altitude.
Crosswind gusts can cause sudden airspeed loss — maintain a higher airspeed margin in gusty conditions.
In gusting crosswind conditions, a sudden gust can cause a loss of airspeed or a wing drop during a turn. The defense is maintaining a higher airspeed margin above stall — at least 1.3 × Vs0, which is roughly 72 KIAS in landing configuration. On final approach in gusting wind, consider maintaining 80–85 KIAS instead of the minimum Vref of 75 KIAS. The extra 5–10 knots gives you a buffer against a gust-induced stall.
Recognize unstable approaches early and go around — do not try to salvage a slow, low, steep approach.
An unstable approach is defined by low airspeed, steep bank, high descent rate, and low altitude. If you find yourself on base at 750 ft AGL at 90 KIAS, or on final at 400 ft AGL in a steep descent, the approach is unstable. The correct decision is to go around. Apply full power, retract flaps to 0°, and climb out. In the Piper Arrow, the constant-speed prop is already in cruise (2000 RPM), so you do not need to adjust it; the gear is down and locked, which increases drag but is correct for the go-around. Announce on CTAF and have time to reassess and come back for another approach. A go-around is not a failure — it is the correct decision when the approach becomes unstable.
Fatigue and complacency on a familiar field are major factors in pattern stalls.
The pilot who has flown the pattern at KTPF a hundred times is often the one who does not see the unstable approach developing. Fatigue (a long day of work before the flight) reduces situational awareness and decision-making. Complacency (this is my home field, I have done this a hundred times) leads to overconfidence and reduced vigilance. On a familiar field, especially in gusty conditions, maintain the same discipline and awareness as you would on an unfamiliar field. Scan the airspeed indicator, the altimeter, and the wind indicator continuously. Recognize when the approach is unstable and go around.
Stall recovery at low altitude requires immediate action: power, level wings, lower nose.
If a stall occurs at low altitude (300 ft AGL or lower), the recovery must be immediate and correct. Add full power, level the wings (reduce bank to 0°), and lower the nose to recover airspeed. Do not pitch up — pitching up deepens the stall and can lead to a spin. Do not hold the attitude and wait for the stall to pass — the airplane will continue to descend in a stalled condition. The recovery must be aggressive and immediate. At 300 ft AGL, you have only 2–3 seconds before ground impact; every second counts.
At KTPF, the off-field environment off Runway 22 is open water — an engine failure or uncontrolled descent in the pattern is a ditching.
The off-field environment off Runway 22's departure end (heading 217°) is open water — Tampa Bay. There is no alternate landing surface. If the engine fails or the airplane enters an uncontrolled descent in the pattern, the outcome is a ditching in open water. This is not a worst-case scenario; it is the geographic reality of this field. Know the off-field environment before you depart. If you are uncomfortable with the wind, the pattern, or the approach, go around. A go-around is always an option; a ditching is not.
Built from the real accident record
Scenario built from NTSB ERA10CA300 (2010 PA-18 stall/spin on climbing turn in pattern), LAX89LA222 (1989 AA-1C stall on final in gusting crosswind), ATL92LA146 (1992 C172 stall on short final), and ERA12CA019 (2011 Aeronca stall/spin on downwind turn). Regional precedents: ERA21FA189, ERA15FA299, ERA14FA002, ERA13FA144 (PA-28R spatial disorientation / loss of control in IMC and night). Localized to KTPF with real runway geometry and off-field environment.
NTSB reports: ERA21FA189 · ERA15FA299 · ERA14FA002 · ERA13FA144 · LAX89LA222 · ERA10CA300 · ATL92LA146 · ERA12CA019
ACS tasks: PA.V.A — Approach and Landing · PA.V.B — Go-Around / Rejected Landing · PA.VIII.C — Loss of Control Procedures · PA.I.H — Human Factors · PA.II.D — Approach to Landing
Relevant FARs: §91.3 · §91.13 · §91.121
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 Arrow scenarios · More scenarios at KTPF