The Turn to Final — Sarasota Pattern
Base-to-final stall/spin in a complex aircraft: airspeed management, gear extension, and the margin that saves lives
The scenario
Sarasota Bradenton International Airport (KSRQ), Sarasota, FL — Runway 14 in use. Elevation 30 ft MSL. You are a commercial pilot with roughly 400 hours total time, 80 hours in the Piper Arrow PA-28R. This is a local flight — a currency flight with a safety pilot in the right seat, no passengers. You have flown KSRQ twice before; it is not unfamiliar, but it is not your home field.
Conditions: VFR, scattered clouds at 3,500 ft, visibility 8 SM, wind 160° at 12 gusting to 18 knots. That is a 20–30° crosswind to Runway 14 (heading 134°). Gusts are at the edge of your personal minimums. OAT 26°C, altimeter 29.92. You have been in the air for 1.2 hours; this is the final approach to land.
You are on base leg, 800 ft AGL, descending at 90 KIAS with the landing gear down (Vle 129 KIAS — you are within limits). Flaps are at 10°. The safety pilot is quiet; the tower has cleared you to land. You are turning left toward final approach (heading 314° inbound). The runway is in sight. You are in a normal descent. Everything feels routine.
Aircraft: Piper PA-28R-200, complex aircraft — retractable gear, constant-speed prop, fuel-injected Lycoming IO-360. You lowered the gear on downwind and confirmed three green lights. You have set the prop to high RPM (full forward). Flaps are 10°; you plan to add 20° on short final. Airspeed is 90 KIAS.
Pilot: You — commercial pilot, 400 hours total, 80 hours in the Arrow. Current and proficient. You have not flown a crosswind approach in the Arrow in several weeks. The gusts are noticeable but within your stated minimums. You are not fatigued, but you are focused on the landing — the wind is demanding attention.
- {'label': 'Field', 'value': 'KSRQ · Sarasota Bradenton'}
- {'label': 'Runways', 'value': '4/22 · 14/32'}
- {'label': 'Elevation', 'value': '30 ft'}
- {'label': 'Aircraft', 'value': 'PA-28R'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we enter the scenario — what do you know about stall/spin risk during the base-to-final turn in a crosswind approach? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB ERA21FA189 (2021, fatal): 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 night IMC, with contributing factors including self-induced and external pressures that influenced the decision to initiate and continue the flight.
NTSB ERA15FA299 (2015, fatal): 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 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 teaching angle: recognize when an ATC request (or self-imposed maneuver) on final approach will compromise airspeed safety; request an alternative spacing solution or go around rather than attempt a marginal-speed turn.
NTSB LAX89LA222 (1989, fatal): A Grumman AA-1C on approach to a coastal airport stalled on final approach in gusting crosswind conditions and impacted the ocean short of the runway. The probable cause was the pilot's failure to maintain sufficient airspeed to prevent a stall at an altitude too low for recovery. The teaching angle: maintain adequate airspeed margin during final approach in crosswind conditions; recognize unstable pattern early and go around rather than continue descent at marginal speed.
NTSB ATL83LA356 (1983): A Cessna 172 stalled during short final approach at 200 feet and 67 mph with full flaps in crosswind conditions and struck the ground. The probable cause was the pilot allowing the aircraft to descend below stall speed during approach.
The real accidents cited above occurred at other airports and in other aircraft — NOT at KSRQ. This scenario is localized to KSRQ to make the off-field environment and the crosswind conditions real and consequential for you as a student here. The base-to-final stall/spin is the dominant loss-of-control accident in the pattern, and it is almost always preceded by marginal airspeed management, a steep bank, or both.
The consistent thread across all these events: the base-to-final turn is where pilots lose control. The causes are always the same: inadequate airspeed margin, a steep bank to correct for wind drift, adding flaps or gear during the turn (increasing drag without increasing power), and a failure to recognize the marginal situation early enough to go around. The stall warning horn is a gift — if you hear it, go around. Do not continue descent.
Key lesson — In the Piper Arrow, the base-to-final turn in a crosswind is a high-workload, high-risk phase. You are managing airspeed, bank angle, descent rate, gear extension, flap extension, and wind drift simultaneously. Maintain at least 85–90 KIAS on base and final; add flaps gradually, not during the turn; avoid steep banks (keep it under 20°); and add power if airspeed decays below 85 KIAS. If the stall warning horn sounds, go around immediately — do not continue descent. A go-around from 500 ft AGL is safe and recoverable; a stall/spin at 300 ft AGL is not.
Debrief — teaching points
The base-to-final turn is the highest-risk phase of the pattern.
The NTSB data shows that more stall/spin accidents occur during the base-to-final turn than any other phase of flight. The causes are always the same: inadequate airspeed margin, a steep bank to correct for wind drift, adding flaps or gear during the turn (increasing drag without increasing power), and a failure to recognize the marginal situation early enough to go around. In the Piper Arrow, you are also managing the retractable gear and constant-speed prop — additional workload at a critical time. Maintain at least 85–90 KIAS on base and final; avoid steep banks (keep it under 20°); and add power if airspeed decays.
Flaps and gear increase drag — add them early, not during the turn.
In the Arrow, lowering the gear increases drag and reduces climb performance. Adding flaps also increases drag. If you add either during the base-to-final turn, you increase drag without increasing power, and airspeed decays. The correct procedure is to lower the gear on downwind (before the turn), add flaps gradually on downwind and early base (before the turn), and manage power to maintain airspeed. If you find yourself adding flaps during the turn, you are behind the airplane — reduce flaps, add power, and reset.
Crosswind approaches demand higher airspeed and shallower banks.
In a crosswind, the temptation is to steepen the bank to compensate for wind drift and speed up the turn. Do not do this. A steep bank increases the load factor and raises stall speed. At a 25–30° bank, stall speed can increase from 60 KIAS (clean) to 65–68 KIAS. If you are at 90 KIAS in a steep bank with gear down and flaps 10°, you are still above stall, but the margin is tightening. The correct technique is to maintain a shallow bank (under 20°), use crab angle to stay aligned with the runway, and maintain higher airspeed (90–95 KIAS on base and final).
The stall warning horn is a signal to go around, not to continue.
The Piper Arrow has a stall warning horn that activates 5–10 knots before the stall. If you hear it on short final, do not continue descent. Immediately advance the throttle to full power, reduce flaps to 10°, level the wings, and climb out. A go-around from 300–500 ft AGL is safe and recoverable. A stall/spin at 300 ft AGL is not. The stall warning horn is a gift — use it.
Recognize unstable approaches early and go around.
An unstable approach is one where you are below target airspeed, above target descent rate, or struggling to maintain alignment with the runway. If you recognize an unstable approach at 500 ft AGL or higher, go around. Reset, plan the next approach, and execute it with better energy management. A go-around is not a failure — it is the correct decision when conditions are marginal. The NTSB data shows that pilots who go around when approaches are unstable survive; pilots who press on do not.
Off Runway 14 at KSRQ, the off-field environment is dense development — recognize the landing commitment.
Runway 14 at KSRQ (heading 134°) has dense development off the approach end. Once you are committed to landing on Runway 14, you are committed to the runway — there is no alternate landing surface ahead. This makes airspeed management and a stable approach even more critical. If the approach is unstable or marginal, go around before you are too low to recover. Runway 32 (heading 314°) has medium development off the approach end — also challenging. Know the off-field environment before you depart, and use it to inform your decision to 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 during final-approach turn), ATL83LA356 (stall during short final), and FTW99LA205 (inadvertent stall during evasive maneuver). Localized to KSRQ.
NTSB reports: ERA21FA189 · ERA15FA299 · ERA14FA002 · ERA13FA144 · LAX89LA222 · ERA10CA300 · ATL83LA356 · FTW99LA205
ACS tasks: PA.VI.A — Approach and Landing · PA.VI.B — Forward Slip · PA.VI.C — Go-Around · PA.VIII.A — Loss of Control Inflight · PA.I.H — Human Factors
Relevant FARs: §91.3 · §91.13 · §91.21
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 KSRQ