FlightEdge
Sample scenario-based training
SAMPLE SBTApproach / Landing

The Tightening Turn

Base-to-final stall/spin in a complex aircraft — airspeed decay, workload, and the pattern altitude trap

Piper Arrow · Tampa International Airport (KTPA) · Private · Approach / Landing

The scenario

Departing Tampa International Airport (KTPA), Tampa, FL — Runway 19R, a full-length 11,002-ft concrete runway. Elevation 26 ft MSL. You are on a local VFR flight in a Piper Arrow PA-28R-200, solo, within weight and balance, full fuel. The airplane is well-maintained and current.

It is a clear, calm afternoon: OAT 24°C, dew point 16°C, altimeter 30.02, winds light and variable. Visibility 10 SM. A textbook VFR day. KTPA is a towered, Class B airport operating 24 hours. You have filed a local flight plan and are returning to KTPA after 1.5 hours of training maneuvers in the practice area north of the field.

You are on downwind for Runway 19R at 1,200 ft AGL, configured for landing: gear down (Vle 129 KIAS), flaps 20°, power reduced, airspeed 90 KIAS. The runway is in sight. Tower clears you for the approach. You begin the turn to base.

Aircraft: Piper Arrow PA-28R-200, constant-speed prop, retractable gear, fuel-injected Lycoming IO-360 (200 hp). You are current on the airplane but this is your first solo return to KTPA after the practice area. The approach is routine — or it should be.

Pilot: You — a Private pilot with 280 hours total, 45 hours in the Arrow, current and proficient. You have made dozens of approaches to KTPA. Today, however, you are slightly behind the airplane: the practice maneuvers took longer than expected, you are mentally fatigued, and you are eager to get back and close out the flight. You are not distracted by anything specific, but your scan is not as sharp as it should be.

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 ERA21FA189 (2021): A Piper PA-28RT 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 student pilot's continued VFR flight into IMC at night, with contributing factors including self-induced and external pressures that influenced the decision to initiate and continue the flight.

NTSB ERA15FA299 (2015): A Piper PA-28R-200 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 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. The teaching angle: recognize and maintain minimum safe airspeed during base-to-final turn; avoid tightening the turn when airspeed decays.

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 probable cause was the pilot's failure to maintain adequate airspeed during the turn, resulting in an inadvertent stall and collision with terrain.

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.

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 real accidents cited above occurred at other airports and in other aircraft — NOT at Tampa International Airport. KTPA has its own accident history (see field dominant patterns: FORCED_LANDING 22.2%, LOSS_OF_CONTROL_INFLIGHT 11.1%), but these specific stall/spin events happened elsewhere. The scenario is localized to KTPA to make the 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 a high-risk phase. The airplane is slow, configured for landing, at low altitude, and turning — a stall here is unrecoverable. The fix is simple: continuous airspeed scan, maintain Vref (75 KIAS) or higher, and go around if the approach becomes unstable. In a complex aircraft like the Piper Arrow, the workload is higher; fatigue or distraction can lead to airspeed decay. Off Runway 19R's approach end, the off-field environment is dense development — a stall/spin here is a CFIT into buildings or terrain.

Key lesson — The base-to-final turn in the pattern is the highest-risk phase of flight for stall/spin accidents. In a complex aircraft like the Piper Arrow, the workload is higher and the margin for error is smaller. Maintain continuous airspeed scan, keep airspeed above Vref (75 KIAS), and go around immediately if the approach becomes unstable. At KTPA, the off-field environment off Runway 19R's approach end is dense development — a stall/spin here is fatal. Know your V-speeds, scan continuously, and do not hesitate to go around.

Debrief — teaching points

The base-to-final turn is the highest-risk phase for stall/spin accidents.

The airplane is slow, configured for landing, at low altitude, and turning — all risk factors combined. A stall in the pattern at 1,000 ft AGL leaves insufficient altitude for recovery. The NTSB data on pattern stalls is consistent: they are almost always fatal or near-fatal. The base-to-final turn is where most pattern stalls occur because the pilot is focused on runway alignment and not actively monitoring airspeed. Scan the airspeed indicator every 3–5 seconds during the turn.

In the Piper Arrow, Vref is 75 KIAS — maintain this speed or higher on final approach.

Vref (75 KIAS) is the target approach speed for the PA-28R. Stall speed in landing configuration (gear down, flaps 40°) is 55 KIAS, but Vref provides a 20 KIAS safety margin. If airspeed decays below 75 KIAS during the approach turn, you are in the slow-flight stall/spin envelope. Do not attempt to recover by tightening the turn — that increases load factor and makes a stall more likely. Go around instead.

Fatigue and distraction degrade scan discipline — recognize when you are behind the airplane.

In this scenario, you were slightly behind the airplane after the practice maneuvers: mentally fatigued, eager to get back, and not scanning as sharply as usual. This is a common accident precursor. If you notice you are behind the airplane, slow down, take a breath, and reset your scan. A go-around is always an option. Do not let schedule pressure or fatigue push you into an unstable approach.

A go-around is not a failure — it is airmanship.

If the approach becomes unstable, airspeed decays, the turn is not progressing smoothly, or you are not comfortable, go around. Add full throttle, reduce flaps to 20°, and climb back to pattern altitude. Fly another approach. The cost of a go-around is a few minutes and a little fuel. The cost of a stall/spin in the pattern is your life. Go around without hesitation.

In a complex aircraft, workload is higher — manage it deliberately.

The Piper Arrow has retractable gear and a constant-speed prop. Both require attention during the approach. Gear should be down and locked before descending below 1,500 ft AGL. Prop should be set to high RPM (full forward) for the approach. Fuel selector should be on the fullest tank. If you are distracted by any of these tasks, the approach becomes unstable. Plan ahead: get the gear and prop set early, then focus on airspeed and descent.

Built from the real accident record

Scenario built from NTSB ERA21FA189, ERA15FA299, ERA14FA002, ERA13FA144 (Piper Arrow spatial disorientation / loss-of-control accidents), and regional base-to-final stall/spin precedents FTW91DRG06, SEA07CA125, CHI89DET01, ERA10CA300. Anonymized and localized to KTPA.

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

ACS tasks: PA.IV.B — Slow Flight · PA.IV.C — Stall Prevention and Recovery · PA.V.A — Approach and Landing · PA.V.B — Go-Around · PA.I.H — Human Factors

Relevant FARs: §91.3 · §91.13 · §91.119

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 KTPA