The Turn to Final
Base-to-final stall/spin in a Piper Warrior — airspeed decay, a tightening turn, and 300 feet AGL
The scenario
Departing Venice Municipal Airport (KVNC), Venice, FL — Runway 13, a local VFR flight in the pattern. Elevation 18 ft MSL. The field is non-towered (CTAF 122.775). You are on an instructional flight with your CFI; this is a touch-and-go practice session.
Conditions: VFR, clear skies, light winds from 160° at 4 knots. Visibility 10+ SM. OAT 26°C. A perfect day to practice landings — the kind of day where complacency is the biggest risk.
You have completed two touch-and-goes on Runway 13 without incident. On the third approach, you are turning base at 500 ft AGL, airspeed 75 KIAS, descending at a shallow rate. The runway is ahead and to the right. Your CFI is quiet in the right seat — letting you fly the approach.
Aircraft: Piper PA-28-161 Warrior, solo with CFI, within weight and balance limits. Carbureted Lycoming O-320-D, fixed-pitch prop, fixed gear, LEFT/RIGHT fuel selector (currently LEFT tank, adequate fuel). Steam panel, vacuum-driven instruments. Nothing was written up; the airplane is airworthy.
Pilot: you — a Private pilot, current, roughly 150 hours total. You have 12 hours in the Warrior. You are comfortable in the pattern and have made a dozen landings in the past month. You are not rushing, but you are also not being meticulous about every instrument scan.
- {'label': 'Field', 'value': 'KVNC · Venice'}
- {'label': 'Runways', 'value': '4/22 · 13/31'}
- {'label': 'Elevation', 'value': '18 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-161'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we get into the decision tree — what do you already 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 was in the right seat. The approach was high and unstable; the instructor did not initiate a go-around. Instead, the pilot (a student) attempted to salvage the approach with a tighter turn. The airplane stalled at low altitude, entered a spin, and impacted trees about 1,000 feet beyond the runway. The accident was fatal. The probable cause: the flight instructor's failure to initiate a go-around during a high approach, and inadequate remedial action during the 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 was in the right seat. The instructor failed to maintain adequate airspeed during the go-around climb. The airplane stalled, entered a spin, and impacted trees and terrain. The accident was fatal. The probable cause: the flight 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. The airplane struck trees at the departure end of the runway. The accident was fatal. The probable cause: the pilot's failure to maintain airplane control during takeoff, which resulted in an aerodynamic stall. Contributing factors: inadequate preflight planning for soft-field conditions and failure to obtain a weather briefing.
The regional precedent NTSB FTW91DRG06 (1991, Questair Venture) and SEA07CA125 (2007, Cessna 170B) both document base-to-final stalls in which the pilot allowed airspeed to decay during the turn and did not recover before impact. The common thread: the pilot was focused on the runway alignment, not the airspeed. The stall-warning horn sounded, but the pilot did not respond immediately. At 300–400 ft AGL, there is no time to recover from a stall that develops into a spin.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Venice Municipal Airport (KVNC). However, KVNC's own accident history shows that loss of control in flight and stall/spin events are the dominant patterns at this field. The scenario is localized to KVNC to make the pattern environment real and consequential for you as a student here.
The consistent thread across all these events: base-to-final stall/spin is the most common stall accident in the pattern. It happens when airspeed decays, the pilot tightens the turn to stay aligned with the runway, the stall-warning horn sounds, and the pilot does not respond immediately. At 300 ft AGL, there is no altitude for recovery. The fix is simple: maintain airspeed, monitor the instruments continuously, and do not hesitate to execute a go-around if the approach is unstable.
Key lesson — In the Piper Warrior, the turn to final is the most critical moment in the pattern. Airspeed must be maintained at or above Vref (63 KIAS) with a margin for the turn. If airspeed decays, the correct action is to reduce the bank angle and add power — NOT to tighten the turn. The stall-warning horn is the last warning before the stall. If you hear it, lower the nose, level the wings, and add power immediately. At 300 ft AGL, there is no time to recover from a stall that develops into a spin. If the approach is unstable at any point, execute a go-around.
Debrief — teaching points
Base-to-final stall/spin is the most common stall accident in the pattern.
The NTSB data show that stall/spin accidents in the pattern are concentrated on the turn from base to final. The mechanism is always the same: airspeed decays, the pilot tightens the turn to stay aligned with the runway, the stall-warning horn sounds, and the pilot does not respond immediately. At 300–500 ft AGL, there is no altitude for recovery. The Piper Warrior's stall speed in level flight is 44 KIAS (Vs0 with full flaps), but in a 30° bank turn, the effective stall speed is roughly 50 KIAS. If your airspeed is 63 KIAS (Vref) and you are in a 30° bank, your margin above the stall is only 13 knots — a margin that can evaporate in seconds if you are not actively monitoring the airspeed.
Maintain airspeed as the priority — not runway alignment.
The instinct to stay aligned with the runway is strong, especially when the runway is in sight and you are close to landing. But at 300 ft AGL, maintaining airspeed is more important than maintaining a tight turn. If airspeed is decaying, the correct action is to reduce the bank angle and add power. The turn will take a few more seconds, but you will arrive at the runway safely. A tight turn with decaying airspeed will kill you.
The stall-warning horn is the last warning — respond immediately.
The Piper Warrior has a stall-warning horn that activates at roughly 5 knots above the stall speed. If you hear it, you are in the stall-warning envelope and must immediately lower the nose (reduce angle of attack), reduce the bank angle, and add power. Do not hesitate. Do not try to salvage the approach. The stall-warning horn is not a suggestion — it is the last warning before the stall.
At low altitude, the go-around is your best option.
If the approach is unstable at any point — high, fast, with decaying airspeed, or if you hear the stall-warning horn — the correct action is a go-around. A go-around is not a failure; it is airmanship. You add full power, lower the nose slightly to maintain airspeed, and climb out. You climb back to pattern altitude and set up for another approach. The go-around removes all doubt and gives you another chance to get it right.
Monitor the airspeed indicator continuously in the pattern.
The visual picture can be deceiving. The runway can look good, the descent angle can look right, but the airspeed can be decaying. You must scan the airspeed indicator as part of your regular instrument scan, especially during the turn to final. At 500 ft AGL on base, confirm your airspeed is at or above Vref (63 KIAS) with a margin. If it is below Vref, add power immediately. Do not turn final until you have confirmed the airspeed.
Built from the real accident record
Scenario built from NTSB CEN12FA188 (2012 PA-28-161 stall on takeoff, soft field), NYC08FA237 (2008 PA-28-161 stall during go-around, high approach), NYC06FA029 (2005 PA-28-161 stall on go-around, low altitude), CHI05LA226 (2005 PA-28-161 partial magneto failure and stall), and regional precedents FTW91DRG06 (1991 base-to-final stall), SEA07CA125 (2007 base-to-final stall, airspeed decay), CHI89DET01 (1988 stall in climbing turn), ERA10CA300 (2010 stall during spacing turn). Anonymized and localized to KVNC.
NTSB reports: CEN12FA188 · NYC08FA237 · NYC06FA029 · CHI05LA226 · FTW91DRG06 · SEA07CA125 · CHI89DET01 · ERA10CA300
ACS tasks: PA.I.F — Weather Information · PA.V.A — Approach and Landing · PA.V.B — Go-Around / Rejected Landing · PA.VIII.A — Stall Recognition and Recovery · PA.VIII.B — Spin Awareness · 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 KVNC