The Tightening Turn
Base-to-final stall/spin in a Piper Warrior — airspeed decay, a descending turn, and 300 feet AGL
The scenario
Departing Lakeland Linder International Airport (KLAL), Lakeland, FL — Runway 10, pattern work and touch-and-go practice. Elevation 142 ft MSL. It is a clear, calm afternoon: winds calm to 3 knots, visibility 10 SM, scattered clouds at 3,500 ft. A textbook VFR day for pattern work.
You are a Private pilot with roughly 180 hours total time, about 40 hours in the Piper Warrior (PA-28-161). You are current and proficient on landings, but today you are pushing the envelope slightly: you have completed three touch-and-go landings and are on your fourth approach. You are tired but not fatigued — just the normal fatigue of repetitive pattern work. Your CFI is not on board; you are solo.
You are on base leg, 300 ft AGL, descending toward final approach for Runway 10. Airspeed is 70 KIAS — slightly above Vref (63 KIAS with full flaps), and you have not yet added full flaps. The turn to final is ahead. The off-field environment to the west (left, in the turn) is medium development, evergreen forest, and low-density development — not ideal for a forced landing, but not water or dense urban. The runway is in sight, the approach looks stable, and you are ready to turn.
Aircraft: Piper PA-28-161 Warrior, solo, within limits. Lycoming O-320-D carbureted engine, fixed-pitch prop, fixed gear, LEFT/RIGHT fuel selector (no BOTH position). Fuel selector is on LEFT tank, which has 15 gallons remaining. The airplane is airworthy; nothing was written up.
Pilot: you — Private, 180 hours total, 40 hours Warrior. You have completed three touch-and-go landings this session. You are focused on the approach but not hypervigilant. You have not briefed the go-around procedure or the stall recovery sequence for this session.
- {'label': 'Field', 'value': 'KLAL · Lakeland Linder'}
- {'label': 'Runways', 'value': '5/23 · 10/28'}
- {'label': 'Elevation', 'value': '142 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-161'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
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 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. Fatal.
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. Fatal.
NTSB CHI89DET01 (1988): A Volksplane VP-1 in local traffic pattern at approximately 300 feet AGL stalled while turning downwind with a nose-high attitude and slow airspeed, entered an incipient spin, and struck the ground in an inverted attitude. The accident resulted from a stall with insufficient altitude for recovery. Fatal.
NTSB FTW91DRG06 (1991): A Questair Venture experimental aircraft stalled during a base-to-final turn on a maintenance test flight and nosed over out of control. The accident resulted from the pilot's failure to maintain flying airspeed during the approach. Fatal.
NTSB SEA07CA125 (2007): A Cessna 170B on a full-stop landing approach stalled during the base-to-final turn when the pilot allowed airspeed to become too low. The aircraft impacted a field adjacent to the airport. The accident was attributed to the pilot's failure to maintain adequate airspeed during the turn, resulting in an inadvertent stall and collision with terrain.
The common thread across all these accidents: base-to-final stalls occur when airspeed decays below stall speed during a descending turn at low altitude. The stall develops silently — the stall warning horn may sound, but by then the stall is imminent. The recovery window is measured in feet, not seconds. At 300 ft AGL, there is no recovery altitude. The correct response to an unstable approach at low altitude is a go-around — full power, level wings, climb to pattern altitude, and a fresh approach. The go-around is not a failure; it is airmanship.
None of these accidents occurred at KLAL — they happened at other airports and in other aircraft. But the pattern is identical: a descending turn in the pattern, airspeed decay, a stall at low altitude, and impact with terrain. The off-field environment at KLAL (medium development, evergreen forest, low-density development off Runway 10's departure end) is not ideal for a forced landing, but it is survivable if you execute a go-around before the stall develops.
Key lesson — In the pattern, airspeed is your lifeline. A stable approach means airspeed at or above Vref (63 KIAS with full flaps in the Warrior), descent rate controlled, and runway aligned. If any of these are missing at 300 ft AGL, go around. The go-around is the correct response to an unstable approach — it is not a failure, it is the decision that saves your life. The stall/spin in the pattern is the deadliest accident in general aviation because the altitude is too low for recovery. Do not let it happen to you.
Debrief — teaching points
Stall speed increases with bank angle — a 20° bank adds 6% to stall speed.
In the Warrior, stall speed in landing configuration (full flaps) is 44 KIAS (Vs0) in level flight. In a 15° bank, stall speed is roughly 47 KIAS (3% increase). In a 20° bank, stall speed is roughly 47 KIAS (6% increase). In a 25° bank, stall speed is roughly 49 KIAS (11% increase). A descending turn in the pattern is a high-load maneuver — the bank angle is steep, the descent rate is high, and the airspeed is low. The stall speed in a 25° bank turn at 300 ft AGL is significantly higher than the published Vs0. Monitor the airspeed indicator continuously during the turn to final.
Vref (approach speed) is the minimum safe airspeed on final approach — do not go below it.
Vref for the Warrior with full flaps is 63 KIAS. This is the speed at which the airplane is stable on final approach — descent rate controlled, pitch stable, and stall margin adequate. Anything slower than Vref is a descent into the stall envelope. On base leg, before the turn to final, your airspeed should be at or above Vref. If you are below Vref on base leg, lower the nose to regain airspeed — do not turn to final until you are at Vref.
The stall warning horn is a late warning — recognize the precursors before the horn sounds.
The stall warning horn in the Warrior sounds at roughly 5–10 KIAS above stall speed. By the time the horn sounds, you are at the edge of the stall envelope. The precursors are: airspeed decaying, descent rate increasing, nose attitude high, and control feel mushy. Monitor the airspeed indicator and the attitude indicator continuously. If airspeed is decaying and you are in a turn, lower the nose immediately — do not wait for the stall warning horn.
Stall recovery at low altitude is not possible — prevention is the only option.
Stall recovery requires altitude: nose down to regain airspeed (lose 100–200 ft), level the wings to reduce stall speed (lose 50–100 ft), add power to climb (gain altitude). At 300 ft AGL on base-to-final, there is no altitude to lose. If you stall at 300 ft AGL, you will impact terrain before the recovery is complete. The only option is prevention: maintain airspeed at or above Vref, keep the bank angle shallow, and monitor the descent rate. If the approach is unstable, go around.
A go-around is not a failure — it is the correct response to an unstable approach.
An unstable approach is defined as: airspeed more than 10 KIAS above or below Vref, descent rate more than 700 ft/min, or runway not aligned. If any of these are true at 500 ft AGL or below, execute a go-around: full power, level the wings, retract flaps to 0°, and climb to pattern altitude. The go-around is the safest option — you have the fuel, the daylight, and the runway. A fresh approach is always better than pushing a marginal one.
Fatigue and repetition dull your scan — after multiple touch-and-go landings, your vigilance decreases.
After three or four touch-and-go landings, your attention narrows — you focus on the runway and lose the big picture. Your scan of the airspeed indicator, attitude indicator, and descent rate becomes less frequent. Your decision-making becomes more automatic and less deliberate. If you feel this happening, execute a go-around and take a break. A fresh approach with full attention is always better than a fatigued approach with diminished vigilance.
Built from the real accident record
Scenario built from NTSB NYC08FA237 (2008 PA-28-161 stall on touch-and-go), NYC06FA029 (2005 PA-28-161 stall during go-around), FTW91DRG06 (1991 base-to-final stall/spin), SEA07CA125 (2007 Cessna 170B base-to-final stall), CHI89DET01 (1988 Volksplane stall/spin in pattern), and ERA10CA300 (2010 PA-18-135 stall during climbing turn). Localized to KLAL.
NTSB reports: CEN12FA188 · NYC08FA237 · NYC06FA029 · CHI05LA226 · FTW91DRG06 · SEA07CA125 · CHI89DET01 · ERA10CA300
ACS tasks: PA.II.E — Approach and Landing · PA.II.F — Go-Around / Rejected Landing · PA.VII.A — Stall / Spin Awareness · PA.VIII.A — Slow Flight · 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 KLAL