FlightEdge
Sample scenario-based training
SAMPLE SBTApproach / Landing

The Turn to Final

Base-to-final stall/spin in a complex aircraft — crosswind, low altitude, and the margin between airspeed and stall

Piper Arrow · Tampa Executive Airport (KVDF) · Commercial · Approach / Landing

The scenario

Departing Tampa Executive Airport (KVDF), Tampa, FL — Runway 23 in use. Elevation 22 ft MSL. You are a commercial pilot with 800 hours total, 120 in the Piper Arrow. This is a local pattern flight — currency and proficiency work in the complex aircraft.

Conditions: 1400 local, VFR, winds 210° at 12 gusting 18 knots. Runway 23 is aligned 222° magnetic (true 220°). The crosswind component is roughly 8–10 knots, well within limits. Visibility 5 statute miles in light haze. Scattered clouds at 2,500 ft AGL. Temperature 26°C, dew point 20°C. KVDF is non-towered (CTAF 122.8); you self-announce on downwind, base, and final.

You have completed two touch-and-go landings. This is your third approach. On the second landing, you felt the airplane drift during the flare — the crosswind was more pronounced than you anticipated. You corrected and landed safely, but the approach was not as stable as you would have liked.

Now you are on base leg, 800 ft AGL, 2 nm from the runway. Gear is down (Vle 129 KIAS), flaps are at 20°, airspeed is 90 KIAS. You are turning left from a southbound heading toward the final approach heading of 042° (reciprocal of Runway 23's 222°). The turn to final is a left turn of roughly 180°. The wind is from the southwest, so the turn to final will be a turn into the wind — a left turn with a headwind component.

Aircraft: Piper PA-28R-200 Arrow, solo, within limits. Constant-speed prop (you have set it to high RPM for approach), retractable gear (down and locked), fuel-injected Lycoming IO-360. You have 1.5 hours of fuel remaining.

Pilot: You — commercial pilot, 800 hours total, 120 in type. Current and proficient. You have not flown this airplane in 3 weeks; this is your first flight back after a brief hiatus. You did a thorough preflight and a full run-up. Nothing was written up.

The decision

Before we enter the decision tree — what do you know about stall/spin risk during the base-to-final turn in a complex aircraft like the Arrow? (Pick all that apply.)

What the record shows

What the NTSB files show

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 airplane impacted terrain at an altitude too low for spin recovery.

NTSB LAX89LA222 (1989, fatal): A Grumman AA-1C aborted an approach to Runway 23 and entered a low unstable pattern for Runway 5 in gusting crosswind conditions. The pilot stalled on final approach at 200 feet and 67 mph with full flaps. The accident resulted from the pilot's failure to maintain sufficient airspeed to prevent a stall at an altitude too low for recovery. The airplane impacted the ocean short of the runway.

NTSB ATL83LA356 (1983): A Cessna 172 stalled during short final approach at 200 feet and 67 mph with full flaps in crosswind conditions. The accident resulted from the pilot allowing the aircraft to descend below stall speed during approach.

NTSB ERA21FA189, ERA15FA299, ERA14FA002, ERA13FA144 (2021, 2015, 2013, 2013): Multiple Piper Arrow accidents in night/IMC conditions resulted from spatial disorientation and loss of control. While these accidents occurred in night/IMC environments, the underlying mechanism — loss of airspeed awareness and failure to maintain control in a demanding phase of flight — is the same as the base-to-final stall/spin risk in VFR crosswind conditions.

The real accidents cited above occurred at other airports and in other aircraft — NOT at Tampa Executive Airport (KVDF). KVDF's dominant accident pattern is LOSS_OF_CONTROL_GROUND (18.4%), HARD_LANDING (18.4%), FORCED_LANDING (15.8%), and LOSS_OF_CONTROL_INFLIGHT (13.2%). The base-to-final stall/spin scenario is localized to KVDF to make the crosswind, runway alignment, and off-field environment real and consequential for you as a student here.

The consistent thread across all these events: the base-to-final turn is one of the highest-risk phases of flight. Low altitude, tight turn, crosswind, and the pilot's divided attention (runway alignment vs. airspeed) create a perfect storm for a stall/spin. The fix is simple: maintain 75 KIAS (Vref) throughout the approach, keep the bank angle shallow (less than 15°) during the turn, and if the approach becomes unstable (airspeed low, drift high, bank steep), execute a go-around. A go-around is not a failure — it is airmanship.

Key lesson — The base-to-final turn in a crosswind is the highest-risk phase of flight in a complex aircraft like the Piper Arrow. Maintain 75 KIAS (Vref) and a shallow bank (less than 15°). If the approach becomes unstable — airspeed decaying, drift high, bank steep — execute a go-around. At 650 ft AGL, the margin between stall and recovery is measured in feet, not hundreds of feet. A stall/spin at this altitude is likely fatal. A go-around is always the right call.

Debrief — teaching points

The base-to-final turn is the highest-risk phase of flight in a complex aircraft.

Low altitude (typically 600–800 ft AGL), tight turn (180° in some cases), crosswind, and divided pilot attention (runway alignment vs. airspeed) create a perfect storm for a stall/spin. The Piper Arrow's constant-speed prop and retractable gear add workload. A stall/spin at 650 ft AGL leaves only 10–15 seconds for recovery — often not enough. The NTSB has documented dozens of base-to-final stall/spin accidents across all aircraft types. The lesson is consistent: maintain airspeed margin and a shallow bank. If the approach becomes unstable, go around.

Crosswind increases stall risk by dividing pilot attention.

In a crosswind, the pilot must correct for drift while maintaining airspeed and altitude. This divided attention is a classic accident precursor. The pilot focuses on runway alignment and allows the airspeed to decay. In the Piper Arrow, stall speed with gear down and flaps extended (Vs0) is 55 KIAS. A safe approach speed is 75 KIAS (Vref) — 20 KIAS above stall. But if the pilot is distracted by drift correction and allows the airspeed to decay to 70 KIAS, the margin shrinks to 15 KIAS. In a steep bank (20–25°), the effective stall speed increases to 57–58 KIAS, further reducing the margin. A crosswind gust can push the airspeed below stall speed in seconds.

Bank angle increases stall speed — a steep bank on base-to-final is a stall trap.

In level flight, stall speed is 55 KIAS (Vs0). In a 15° bank, stall speed increases to roughly 56 KIAS. In a 20° bank, it increases to 57 KIAS. In a 25° bank, it increases to 58 KIAS. A shallow bank (less than 15°) during the base-to-final turn minimizes this increase. A steep bank (20–25°) to 'tighten the turn' or 'get aligned quickly' is a stall trap. The pilot's instinct to steepen the bank to make the runway is the exact opposite of what the airplane needs.

Maintain 75 KIAS (Vref) throughout the approach — this is the non-negotiable minimum.

In the Piper Arrow, Vref is 75 KIAS. This speed provides a 20 KIAS margin above stall speed (55 KIAS) in level flight. In a shallow bank (less than 15°), the margin remains adequate. Allowing the airspeed to decay below 75 KIAS — to 70 KIAS, 65 KIAS, or lower — erodes this margin and increases stall risk. If the approach requires you to slow below 75 KIAS to make the runway, the approach is unstable and a go-around is the correct response.

If the approach becomes unstable, go around — do not try to 'fix it' with a correction that deepens the stall risk.

An unstable approach is one where airspeed is low, drift is high, bank is steep, or descent rate is too high. The instinct is to 'fix it' — steepen the bank to align faster, reduce power to descend faster, or pull back to slow the descent. These corrections often deepen the stall risk. The correct response is a go-around: advance the throttle, retract flaps to 10°, and climb to pattern altitude. A go-around costs a few minutes and some fuel. A stall/spin at 650 ft AGL costs lives. The professional pilot's decision is always the go-around.

Built from the real accident record

Scenario built from NTSB ERA21FA189, ERA15FA299, ERA14FA002, ERA13FA144 (Piper Arrow spatial disorientation / loss of control in night/IMC), LAX89LA222 (stall on final in crosswind), ERA10CA300 (stall/spin during climbing turn on final), ATL83LA356 (stall during short final in crosswind), and FTW99LA205 (inadvertent stall during evasive maneuver at low altitude). Localized to Tampa Executive Airport (KVDF).

NTSB reports: ERA21FA189 · ERA15FA299 · ERA14FA002 · ERA13FA144 · LAX89LA222 · ERA10CA300 · ATL83LA356 · FTW99LA205

ACS tasks: PA.IV.C — Approach and Landing · PA.IV.D — 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 KVDF