The Turn to Final
Base-to-final stall in the pattern — recognizing the trap and executing the go-around
The scenario
Departing St. Petersburg Clearwater International Airport (KPIE), Pinellas Park, FL — Runway 18, a 9,730 ft concrete runway. Elevation 11 ft MSL. You are a Private pilot with 180 hours total time, current and proficient. This is a local VFR flight — a practice approach and landing in the pattern.
Conditions: 1400 local, VFR, scattered clouds at 3,500 ft, visibility 8 SM. Wind is 180° at 12 knots, gusting to 18 knots — a direct headwind on Runway 18, but with crosswind component from the south. The tower is active (part-time 0600–2300). You are in Class D airspace, ceiling 1,600 ft MSL. Above 1,200 ft MSL, you are in the overlying Tampa Class B airspace.
Aircraft: Cessna 172S, solo, within limits. Fuel-injected Lycoming IO-360-L2A, 180 hp. Glass panel (G1000). Fixed gear, fixed-pitch prop. You completed a normal run-up; the airplane is airworthy.
You have completed a full stop landing on Runway 18 and are now in the pattern for a second approach. You are on base leg, 800 ft AGL, descending toward the final approach course. The wind is gusting. You are concentrating on the descent and the turn to final.
The off-field environment on base leg (heading roughly 090° from Runway 18) is medium development — houses, small commercial buildings, roads. Off the runway ends: Runway 18 departure (heading 171°) is marginal — medium development, parks, some dense development. Runway 36 departure (heading 351°) is open water — a ditching environment. If you lose control on base and descend into the developed area, impact is likely. If you somehow end up over the water off Runway 36, a ditching is the outcome.
- {'label': 'Field', 'value': 'KPIE · St. Petersburg Clearwater'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '11 ft'}
- {'label': 'Aircraft', 'value': 'C172S'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we enter the decision tree — what do you know about stall/spin accidents on base-to-final in the pattern? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB CEN17FA111 (2017, fatal): A Cessna 172S conducting spin-training maneuvers failed to recover from an intentional aerodynamic spin. The pilots did not apply prompt and correct flight control inputs to recover. The accident occurred at an altitude where recovery was not possible. The lesson: stall/spin recovery requires immediate, correct action — and at low altitude, there is no margin for error or delay.
NTSB ERA14FA283 (2014, fatal): A Cessna 172S on an instructional night flight experienced a partial loss of engine power during initial climb after a touch-and-go landing at Daytona Beach. The pilots decided to turn back to the airport. During the turn, the airplane exceeded its critical angle of attack and stalled. The probable cause was the pilots' decision to turn back — a maneuver that increased angle of attack and stall risk at low altitude — rather than accepting a forced landing ahead.
NTSB WPR12FA230 (2012, fatal): A Cessna 172S stalled during an aggressive pitch-up maneuver shortly after takeoff from St. George Municipal Airport. The pilot failed to maintain adequate airspeed during the maneuver. Contributing factors included alcohol impairment and an over-gross-weight aircraft. The lesson: aggressive pitch-up maneuvers at low altitude are stall traps, especially with reduced performance margins.
NTSB LAX08LA191 (2008, fatal): A Cessna 172S with a newly certificated pilot (72 hours total time) and passengers aboard intentionally performed a second stall/spin maneuver at low altitude and failed to recover. The accident resulted from failure to regain airplane control during the spin. The lesson: stall/spin maneuvers at low altitude with passengers are prohibited for good reason — there is no recovery margin.
NTSB LAX89LA222 (1989, fatal): A Grumman AA-1C aborted an approach to Runway 18 and entered a low unstable pattern for Runway 36 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. This regional precedent demonstrates the stall-on-final trap in crosswind conditions at coastal airports.
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 accident was attributed to the pilot's failure to maintain adequate airspeed during the climbing turn. The lesson: prioritize airspeed and aircraft performance over ATC requests; recognize when a maneuver exceeds aircraft capability.
NTSB ATL83LA356 (1983): A Cessna 172 stalled during short final approach at 200 feet and 67 mph (58 KIAS) with full flaps in crosswind conditions. The probable cause was the pilot allowing the aircraft to descend below stall speed during approach. The lesson: maintain minimum safe airspeed above stall speed during final approach; recognize stall warning and execute go-around immediately.
NTSB FTW99LA205 (1999): A Cessna 150L lost engine power during touch-and-go landing practice. During the subsequent climb-out, the flight instructor performed an abrupt pull-up to avoid powerlines, resulting in an inadvertent stall and spin. The lesson: plan approach and climb-out to avoid obstacles; when faced with unexpected hazard, maintain controlled flight and adequate airspeed rather than abrupt evasive maneuvers that induce stall.
The consistent thread across all these accidents: stalls and spins in the pattern, especially on base-to-final, are almost always fatal because there is insufficient altitude for recovery. The prevention is disciplined airspeed and angle-of-attack management during the approach phase. The C172S's G1000 glass panel includes an angle-of-attack indicator — a tool that, if monitored, makes stall prevention straightforward. The stall warning horn is a backup, not the primary defense. The primary defense is continuous monitoring of airspeed and AOA, and the immediate go-around if either drifts into the yellow arc or the stall warning activates.
At KPIE, the off-field environment on base leg (medium development, houses, roads) and off the runway ends (marginal development on Runway 18 departure, open water on Runway 36 departure) makes a stall/spin in the pattern particularly unforgiving. There is no open field to land in. The outcome is impact with terrain or buildings, or a ditching in open water. This is not hypothetical; it is the NLCD ground cover off those runway ends.
Key lesson — The base-to-final turn is a high-risk phase because the airplane is low, slow, and turning. Stall risk is highest when airspeed is below Vref (65 KIAS), angle of attack is in the yellow arc or above, or the airplane is in a steep bank or slip. The C172S's stall warning horn activates before the aerodynamic stall, but it is a backup — the primary defense is continuous monitoring of airspeed and the G1000's angle-of-attack indicator. If the stall warning activates or the approach becomes unstable, the correct response is an immediate go-around, not a correction attempt at low altitude. At KPIE, a stall/spin in the pattern means impact with developed terrain or a ditching in open water — there is no recovery margin.
Debrief — teaching points
The base-to-final turn is a stall trap.
The base-to-final turn combines three stall-risk factors: low altitude (typically 500–800 ft AGL), low airspeed (approaching Vref, 65 KIAS), and a turn (which increases load factor and stall speed). In a 20° bank, the stall speed increases by roughly 10%. In a 30° bank, it increases by roughly 20%. A steep turn to final at low altitude is a classic stall setup. The NTSB data (ERA10CA300, ATL83LA356, LAX89LA222) shows that stalls initiated on base-to-final are almost always fatal because there is insufficient altitude for recovery. Prevention is disciplined airspeed and bank-angle management during the turn.
Crosswind conditions increase stall risk on base-to-final.
Crosswind conditions tempt pilots to slip the wing down (increasing angle of attack) or roll into a steeper bank to correct drift. Both of these increase stall risk. The correct response to crosswind on base-to-final is to maintain a shallow bank (15–20°), monitor airspeed and AOA continuously, and accept a longer turn to final if necessary. If the approach becomes unstable due to crosswind, the correct response is a go-around, not a correction attempt at low altitude. NTSB LAX89LA222 shows a fatal stall on final in gusting crosswind conditions — the pilot did not recognize the unstable approach and did not go around.
The C172S's angle-of-attack indicator is your primary stall-prevention tool.
The G1000 glass panel includes an angle-of-attack indicator that displays how close you are to stall. The green arc is safe; the yellow arc is caution; the red line is stall. Monitoring the AOA indicator during approach is more reliable than relying on airspeed alone, because AOA accounts for bank angle, load factor, and weight. If the AOA drifts into the yellow arc, add power and/or shallow the descent immediately. The stall warning horn is a backup — it activates before the aerodynamic stall, but it is not the primary defense. The primary defense is continuous AOA monitoring.
Maintain Vref (65 KIAS) or faster on final approach.
Vref for the C172S is 65 KIAS. This is the recommended approach speed in landing configuration (full flaps, gear down if applicable). Maintaining Vref or faster provides a margin above Vs0 (stall speed in landing configuration, 40 KIAS) and accounts for wind gusts and load factor changes during the turn. If a gust causes the airspeed to drop below Vref, add power to recover it — do not pitch up, which increases angle of attack and stall risk. If the approach becomes slow and unstable, go around.
The stall warning horn is a backup, not the primary defense.
The C172S's stall warning horn activates before the aerodynamic stall — typically at an angle of attack about 5–10° before the stall. This gives you a few seconds to respond. However, relying on the stall warning horn as your primary defense is dangerous, because those few seconds at low altitude may not be enough to recover. The primary defense is continuous monitoring of airspeed and AOA during the approach. If the stall warning activates, execute an immediate go-around — do not attempt to correct the approach at low altitude.
When in doubt, go around.
If the approach is unstable, the stall warning activates, airspeed drops below Vref, or the AOA drifts into the yellow arc, the correct response is an immediate go-around. A go-around is not a failure — it is airmanship. The NTSB data shows that pilots who attempt to salvage unstable approaches at low altitude often stall and crash. Pilots who recognize the unstable approach early and go around live to fly another day. The go-around procedure is simple: push the nose down to regain airspeed, add full power, and climb back to pattern altitude. Practice it until it is automatic.
Built from the real accident record
Scenario built from NTSB CEN17FA111 (2017 C172S spin recovery failure), ERA14FA283 (2014 C172S stall on base-to-final turn), WPR12FA230 (2012 C172S low-altitude stall), LAX08LA191 (2008 C172S spin at low altitude), and regional precedents LAX89LA222 (1989 AA-1C stall on final), ERA10CA300 (2010 PA-18 stall during climbing turn), ATL83LA356 (1983 C172 stall on short final), FTW99LA205 (1999 C150 stall during evasive maneuver). Localized to KPIE.
NTSB reports: CEN17FA111 · ERA14FA283 · WPR12FA230 · LAX08LA191 · LAX89LA222 · ERA10CA300 · ATL83LA356 · FTW99LA205
ACS tasks: PA.II.F — Approach and Landing · PA.II.G — Go-Around / Rejected Landing · PA.IV.C — Stall Prevention · PA.IV.D — Spin Awareness · 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 Cessna 172S scenarios · More scenarios at KPIE