FlightEdge
Sample scenario-based training
SAMPLE SBTApproach / Landing

The Turn to Final

Base-to-final stall/spin in the pattern — recognizing decay and committing to recovery before altitude runs out

Piper Warrior · Brooksville–Tampa Bay Regional Airport (KBKV) · Private · Approach / Landing

The scenario

Departing Brooksville–Tampa Bay Regional Airport (KBKV), Brooksville, FL — Runway 09, a clear VFR afternoon. Elevation 76 ft MSL. Wind 080° at 6 knots — nearly aligned with Runway 09, a light quartering headwind. Visibility 10 SM, scattered clouds at 3,500 ft. A textbook day for pattern work.

You are a Private pilot with roughly 120 hours total time, about 40 hours in the Piper Warrior. You are on a solo practice flight, working touch-and-go landings. This is your fourth landing of the session. The first three were stable, normal approaches. You landed, taxied back, and lined up again.

You are now on downwind for Runway 09, 800 ft AGL, airspeed 80 KIAS, power 1,500 RPM, flaps up. The tower has cleared you to land. The runway is ahead and to your right. You begin the turn to base.

Aircraft: Piper PA-28-161 Warrior, solo, 1,800 lb gross weight, within limits. Lycoming O-320-D carbureted engine, fixed-pitch prop, fixed gear, steam panel. All systems normal. The airplane has been flown all morning with no write-ups.

Pilot: you — Private, current, 120 hours total, 40 hours Warrior. You have been flying pattern work for 45 minutes. You are comfortable in the airplane and the pattern is routine. You have not flown a stall recovery in the Warrior since your checkride. You have never practiced a stall recovery in the pattern.

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, FATAL): 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 take adequate remedial action during the attempted touch-and-go. The airplane stalled at low altitude and 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 his inadequate remedial action during the attempted touch-and-go.

NTSB NYC06FA029 (2005, FATAL): 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 CEN12FA188 (2012, FATAL): A Piper PA-28-161 stalled during takeoff from a soft grass airstrip with a quartering tailwind and struck trees at the departure end of the runway. The probable cause was the pilot's failure to maintain airplane control during takeoff, which resulted in an aerodynamic stall and subsequent collision with trees. Contributing to the accident was the pilot's inadequate preflight performance planning before departing on the soft, grass field with a quartering tailwind.

NTSB FTW91DRG06 (1991, FATAL): 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.

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 pilot attempted recovery but 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.

NTSB CHI89DET01 (1988, FATAL): 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.

The real accidents cited above occurred at other airports and in other aircraft types — NOT at Brooksville–Tampa Bay Regional Airport (KBKV). KBKV's own dominant accident pattern is HARD_LANDING (26.9%), FORCED_LANDING (11.5%), and RUNWAY_EXCURSION (11.5%) — not stall/spin accidents. However, the stall/spin mechanism is universal: any pattern turn at low altitude with decaying airspeed is a stall/spin risk, regardless of field. The scenario is localized to KBKV to make the pattern and off-field environment real for you as a student here.

The consistent thread across all these events: the stall in the pattern is not a surprise mechanical failure or a weather event. It is a failure to maintain flying airspeed during a turn at low altitude. The Piper Warrior's Vs0 (stall speed in landing configuration) is 44 KIAS. Vref (approach speed) is 63 KIAS. The margin between them is 19 knots. In a turn, the stall speed increases — a 15° bank increases stall speed by about 5%. At 20° bank, stall speed is roughly 50 KIAS. At 25° bank, it is 52 KIAS. A pilot who allows airspeed to decay to 60 KIAS in a 20° bank is already at stall speed. The recovery — lower the nose, add power, level the wings — is simple. But it must happen before the stall, not after. Once the wing stalls at 300 ft AGL in a banked turn, recovery altitude is gone.

Key lesson — The base-to-final turn is the most dangerous turn in the pattern. Airspeed is low, altitude is low, and the turn is tight. Maintain Vref (63 KIAS) or higher throughout the turn. Recognize stall-warning signs — mushy controls, sluggish pitch response, buffeting — and respond immediately by reducing bank angle and adding power. At 300 ft AGL, a stall followed by a spin entry is fatal. The stall is prevented by maintaining flying airspeed, not by hoping for a recovery at low altitude.

Debrief — teaching points

Stall speed increases in a turn — the bank angle matters.

In level flight, the Piper Warrior's stall speed in landing configuration (full flaps) is 44 KIAS (Vs0). In a 15° bank, stall speed increases to roughly 47 KIAS. In a 20° bank, it is 50 KIAS. In a 25° bank, it is 52 KIAS. The relationship is: Vs_banked = Vs0 / √(cos bank angle). A pilot who allows airspeed to decay to 60 KIAS in a 20° bank is already at stall speed. The margin is gone. Maintain Vref (63 KIAS) or higher throughout the base-to-final turn to ensure a safety margin above stall speed in any bank angle.

Stall-warning signs are subtle — mushy controls, sluggish pitch response, buffeting.

The Piper Warrior has no stall-warning horn or stick shaker. You must recognize stall-warning signs: the controls become mushy and unresponsive, pitch changes are sluggish, and there may be a slight buffeting or vibration. These signs appear 5–10 knots above stall speed. If you feel mushy controls in the pattern, the stall is imminent. Respond immediately: reduce bank angle, lower the nose slightly, and add power. Do not wait for the stall to occur.

Stall recovery at low altitude requires immediate action and sufficient altitude.

Stall recovery in the Piper Warrior requires 500–1,000 ft of altitude, depending on the depth of the stall and the bank angle. At 300 ft AGL in the pattern, a stall followed by a spin entry leaves no recovery altitude. The recovery procedure is: reduce power (to minimize the nose-down pitch moment), apply full opposite rudder (to stop the rotation), lower the nose (to break the stall and restore airspeed), and level the wings (to stop the roll). But all of this takes altitude. The stall must be prevented, not recovered from at low altitude.

Maintain airspeed throughout the base-to-final turn — monitor the airspeed indicator continuously.

The base-to-final turn is the most dangerous turn in the pattern. Airspeed is low, altitude is low, and the turn is tight. Maintain Vref (63 KIAS) or higher throughout the turn. Monitor the airspeed indicator as part of your scan — do not focus on the runway and neglect the airspeed. If airspeed decays below 65 KIAS, reduce bank angle and add power immediately. The runway will still be there; the stall will not wait.

A go-around is not a failure — it is the correct decision when the approach is unstable.

If the approach is high, fast, unstable, or if airspeed is decaying, go around. Advance power to 1,700 RPM, lower the nose to maintain 79 KIAS (Vy, best rate of climb), and climb to 1,000 ft AGL. Re-enter the pattern and try again. A go-around costs a few minutes. A stall in the pattern costs your life. The NTSB data shows that many stall/spin accidents in the pattern occurred on approaches that were unstable — the pilot tried to salvage the approach instead of going around.

Built from the real accident record

Scenario built from NTSB NYC08FA237 (2008 PA-28-161 stall during touch-and-go), NYC06FA029 (2005 PA-28-161 stall during go-around), CEN12FA188 (2012 PA-28-161 takeoff stall), CHI05LA226 (2005 PA-28-161 magneto failure / stall), and local-environment precedents FTW91DRG06 (1991 base-to-final stall/spin), SEA07CA125 (2007 base-to-final stall), CHI89DET01 (1988 stall/spin in pattern). Anonymized and localized to KBKV.

NTSB reports: CEN12FA188 · NYC08FA237 · NYC06FA029 · CHI05LA226 · FTW91DRG06 · SEA07CA125 · CHI89DET01

ACS tasks: PA.VII.A — Steep Turns · PA.VIII.A — Slow Flight · PA.VIII.B — Stall Recognition and Recovery · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors

Relevant FARs: §91.3 · §91.13 · §91.303

Run this scenario yourself

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 KBKV