FlightEdge
Sample scenario-based training
SAMPLE SBTApproach / Landing

The Turn to Final

Base-to-final stall/spin in a complex aircraft — airspeed decay, high workload, and the margin that disappears in a turn

Piper Arrow · Zephyrhills Municipal Airport (KZPH) · Commercial · Approach / Landing

The scenario

Departing Zephyrhills Municipal Airport (KZPH), Zephyrhills, FL — Runway 19, a local VFR training flight. Elevation 90 ft MSL. The afternoon is clear, winds light and variable, visibility 10+ SM. A perfect day to practice approaches and landings in the Piper Arrow.

You are a commercial pilot with roughly 400 hours total time, about 120 hours in the PA-28R. You are current and proficient. The Arrow is familiar — you have flown it regularly for the past three months. Today you are practicing full-stop landings: takeoff, climb out, downwind, base, final, land, taxi back, repeat.

You are on your fourth approach of the afternoon. Downwind for Runway 19, 800 ft AGL, airspeed 90 KIAS, gear down, flaps 10°. The runway is ahead and to the left. You are on a standard left downwind. The wind is light and variable; no crosswind to manage. The approach feels routine.

As you roll out on downwind, you notice the approach is slightly high. You want to descend a bit and tighten the pattern slightly to land closer to the runway threshold. You reduce power, add 10° more flaps (now 20°), and begin a gentle left turn to base. The airspeed is 85 KIAS. The turn feels normal.

Aircraft: Piper Arrow PA-28R, solo, within limits. Constant-speed prop, retractable gear (down and locked), fuel selector LEFT. The airplane is well-maintained and familiar. Nothing was written up; the airplane was airworthy at departure.

Pilot: you — a commercial pilot, current, roughly 400 hours total, 120 hours in type. You have not flown an approach in this exact pattern at KZPH before; it is a new field. You are comfortable with the Arrow's systems and performance, but you are focused on the landing and not actively monitoring airspeed during the turn.

The decision

Before we get into the decision tree — what do you already know about stall/spin risk in the base-to-final turn? (Pick all that apply; this records your baseline.)

What the record shows

What the NTSB files show

NTSB ERA21FA189 (2021, Piper PA-28RT): A commercial pilot on a student solo cross-country flight continued VFR flight into night instrument meteorological conditions despite controller warnings. The accident resulted from spatial disorientation and uncontrolled descent into terrain. The probable cause was the pilot's continued VFR flight into IMC at night, with contributing factors including self-induced and external pressures. The pilot was not instrument-rated.

NTSB ERA15FA299 (2015, Piper PA-28R-200): A pilot on night takeoff from Marathon, Florida experienced spatial disorientation during the initial climb turn, lost positive climb rate, and descended into water. The probable cause was the pilot's failure to maintain a positive climb rate due to spatial disorientation in dark night conditions, with contributing factors including the decision to depart on a night flight over water.

NTSB ERA14FA002 (2013, Piper PA-28R-180): A non-instrument-rated pilot encountered instrument meteorological conditions with precipitation and continued VFR flight into known IMC, resulting in spatial disorientation and loss of control. The probable cause was the improper decision to continue VFR flight into IMC.

NTSB ERA13FA144 (2013, Piper PA-28RT-201): A non-instrument-rated pilot attempted VFR flight in instrument meteorological conditions shortly after takeoff from Tampa North Aero Park. The accident resulted from spatial disorientation and loss of control. Contributing factors included lack of instrument experience and no weather briefing.

NTSB FTW91DRG06 (1991, Questair Venture): A Questair Venture experimental aircraft stalled during a base-to-final turn on a maintenance test flight. The probable cause was the pilot's failure to maintain flying airspeed during the approach.

NTSB SEA07CA125 (2007, Cessna 170B): A Cessna 170B stalled during the base-to-final turn when the pilot allowed airspeed to become too low. 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 adjacent to the airport.

NTSB ERA12CA019 (2011, Aeronca 7AC): An Aeronca 7AC stalled and entered a spin during a left turn to the downwind leg at approximately 400 feet AGL. The probable cause was the pilot's failure to maintain adequate airspeed during the turn, with the pilot unable to recover before ground impact.

NTSB ERA10CA300 (2010, Piper PA-18-135): 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 probable cause was the pilot's failure to maintain adequate airspeed during the climbing turn.

None of these accidents occurred at KZPH. They are cited as precedents for the base-to-final stall/spin mechanism and the consequences of airspeed decay during pattern turns. The KZPH field environment — open developed areas and pasture off Runways 19 and 1, with evergreen forest — means that a stall/spin during the base-to-final turn could result in impact with trees or terrain adjacent to the runway, as shown in the SEA07CA125 and ERA12CA019 cases.

The consistent thread: airspeed decay during a base-to-final turn in a bank angle of 20–30° is the primary cause of stall/spin accidents in the pattern. The stall speed increases with bank angle, and the margin between flying airspeed and stall speed narrows. In a 25° bank, stall speed increases by approximately 6–8%. In a 30° bank, it increases by approximately 15%. At 400 ft AGL, the altitude margin for recovery is measured in seconds. The correct response is to maintain shallow bank angles, monitor airspeed continuously, and go around if the approach becomes unstable.

Key lesson — Base-to-final stall/spin accidents are almost always fatal because the altitude margin for recovery is zero. The prevention is simple: maintain airspeed above the stall speed for the bank angle and flap configuration, keep bank angles shallow (less than 15° on base and final), and go around if the approach becomes unstable. In the PA-28R, the workload of managing gear, constant-speed prop, and fuel selector can distract from airspeed management — prioritize airspeed over all other tasks during the approach.

Debrief — teaching points

Stall speed increases with bank angle — the margin narrows in a turn.

In level flight, the Piper Arrow's stall speed is 55 KIAS (clean) or 55 KIAS (landing configuration). In a 20° bank, stall speed increases by approximately 2% to 56 KIAS. In a 30° bank, it increases by approximately 15% to 63 KIAS. In a 40° bank, it increases by approximately 27% to 70 KIAS. During a base-to-final turn at 400 ft AGL with an airspeed of 80 KIAS and a 25° bank angle, the stall speed is approximately 60 KIAS — a margin of only 20 KIAS. If the airspeed decays to 75 KIAS, the margin is only 15 KIAS. At 70 KIAS, the margin is only 10 KIAS. This is the trap: the turn itself increases the stall speed, and if airspeed is decaying, the margin disappears quickly.

The stall warning horn may not sound in a turn — especially at low altitude.

The stall warning horn in the Piper Arrow is designed to activate at a specific angle of attack in level flight. In a turn, the aerodynamic behavior changes and the stall warning may not activate until the wing is already partially stalled or the stall is imminent. At low altitude with high workload, the pilot may not hear the horn or may not react in time. Do not rely on the stall warning horn as your primary stall-avoidance tool. Monitor the airspeed indicator continuously and maintain a buffer above the stall speed for the bank angle and configuration.

Airspeed decay during base-to-final is the primary cause of stall/spin accidents in the pattern.

The NTSB accident data shows that base-to-final stall/spin accidents are almost always fatal because the altitude margin for recovery is zero. The mechanism is always the same: the pilot reduces power to descend, adds flaps to slow down, and tightens the bank angle to align with the runway. The airspeed decays. The stall speed increases due to the bank angle. The margin between flying airspeed and stall speed narrows. At 300–400 ft AGL, the pilot has no altitude to recover from a stall. The prevention is simple: maintain airspeed above the stall speed for the bank angle and configuration, keep bank angles shallow (less than 15° on base and final), and monitor the airspeed indicator continuously.

The go-around is always an option — it is not a failure, it is airmanship.

If the approach becomes unstable — airspeed decaying, bank angle too steep, descent rate too high — the correct response is to go around. Advance the throttle to full power, reduce flaps to 10°, and climb back to a safe altitude. Announce on CTAF and re-enter the pattern for another approach. A go-around costs a few minutes and a few gallons of fuel. A stall/spin at low altitude costs lives. The go-around is the correct decision.

In the PA-28R, manage workload carefully during the approach — prioritize airspeed.

The Piper Arrow is a complex aircraft: retractable gear, constant-speed prop, and fuel selector (LEFT/RIGHT). During the approach, the pilot must manage gear extension, prop RPM, fuel selector, and flaps while monitoring airspeed, descent rate, and runway alignment. This workload can distract from airspeed management. The solution is to establish a clear approach procedure: gear down and locked before downwind, prop set to climb RPM (or full RPM for approach), fuel selector on the fullest tank, and flaps added incrementally (10° on downwind, 20° on base, 40° on final). This sequence reduces the workload during the critical base-to-final turn and allows the pilot to focus on airspeed and descent rate.

Unfamiliar airports and patterns increase risk — slow down and plan the approach.

KZPH is a non-towered field with two parallel runway pairs. If you are unfamiliar with the field, the pattern, or the runway environment, slow down and plan the approach carefully. Brief the pattern before you enter it: which runway, which direction, what is the off-field environment, where are the obstacles. Fly the approach at a slightly higher altitude and slower airspeed than normal. Do not try to land close to the threshold on an unfamiliar field — land long and taxi back. The extra time and distance are worth the safety margin.

Built from the real accident record

Scenario built from NTSB ERA21FA189, ERA15FA299, ERA14FA002, ERA13FA144 (Piper Arrow spatial disorientation and loss of control in IMC/night), and local base-to-final stall/spin precedents FTW91DRG06 (Questair stall base-to-final), SEA07CA125 (Cessna 170B stall base-to-final), ERA12CA019 (Aeronca spin during pattern turn), ERA10CA300 (Piper PA-18 spin on final approach). Localized to KZPH.

NTSB reports: ERA21FA189 · ERA15FA299 · ERA14FA002 · ERA13FA144 · FTW91DRG06 · SEA07CA125 · ERA12CA019 · ERA10CA300

ACS tasks: PA.IV.A — Normal Approach and Landing · PA.IV.B — Forward Slip to a Landing · PA.IV.C — Go-Around / Rejected Landing · PA.V.A — Stall Recognition and Recovery · PA.V.B — Spin Awareness · PA.I.H — Human Factors

Relevant FARs: §91.3 · §91.13 · §91.103

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 Arrow scenarios · More scenarios at KZPH