FlightEdge
Sample scenario-based training
SAMPLE SBTLanding / Approach

Gusts on Final to Runway 19R

Crosswind landing in gusty conditions at a towered Class B airport — directional control and decision-making under pressure

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

The scenario

Departing Tampa International Airport (KTPA), Tampa, FL — Runway 19R, an 11,002 ft concrete runway. Elevation 26 ft MSL. You are a commercial pilot with roughly 800 hours total, 120 hours in the Piper Arrow. This is a personal flight in a rented PA-28R-200 (Lycoming IO-360, fuel-injected, constant-speed prop, retractable gear).

Approach conditions: VFR, visibility 12 SM, scattered clouds 3,500 ft. Wind is from 240° at 18 gusting to 28 knots. Runway 19R is aligned 182° true (roughly south). The crosswind component is roughly 12–16 knots steady, with gusts to 22+ knots. Your personal minimums for crosswind landings are 15 knots demonstrated; the Arrow's demonstrated crosswind capability is 17 knots. You are within limits by the numbers — but the gusts are at the edge.

You are on a 5 nm final approach to Runway 19R, 1,200 ft AGL, 90 KIAS (Vy, best rate of climb speed — appropriate for descent), gear down, flaps 20°. KTPA tower is active and has cleared you to land. The runway is 11,002 ft long; plenty of room. Off the south end of Runway 19R (heading 182°), the off-field environment is dense development, medium development, and pasture — not ideal for a forced landing, but not water or mountains. Off the north end (heading 002°), the environment is also dense development and open developed areas (parks, large lots).

As you descend through 800 ft AGL on short final, a gust lifts the left wing. You correct with right aileron and left rudder. The airplane drifts right of centerline. You correct back left. Another gust hits — this time from the right. The airplane yaws left. You are now 400 ft AGL, 85 KIAS, and the runway is drifting in your windscreen. The crosswind is working you.

Aircraft: Piper PA-28R-200, fuel-injected Lycoming IO-360 (no carburetor heat), constant-speed prop, retractable gear. Vle (max gear extended) is 129 KIAS; you are at 85 KIAS with gear down and flaps 20°. Vref (approach speed) is 75 KIAS. You are flying a stabilized approach at slightly above Vref. The airplane is within limits, but the margin is thin.

Pilot: You — commercial pilot, 800 hours, 120 hours in type. You have landed in crosswind conditions before. You did not brief a go-around decision point before this approach. You are committed to landing.

The decision

Before we enter the decision tree — what do you know about crosswind landings in the Piper Arrow and loss-of-control recovery at low altitude? (Pick all that apply.)

What the record shows

What the NTSB files show

NTSB WPR25LA178 (2025): A Piper PA-28R-200 on a test flight following annual inspection experienced brake system failure during landing rollout due to a hydraulic fluid leak. The aircraft exited the runway and collided with a fence. The probable cause was a failure of the brake system during landing due to a hydraulic fluid leak, which resulted in a runway excursion. This scenario focuses on the loss-of-control phase, not the brake failure — but the outcome is the same: a runway excursion.

NTSB GAA17CA105 (2016): A Piper PA-46 experienced loss of directional control during landing rollout in gusting crosswind conditions that exceeded the aircraft's demonstrated crosswind capability. The pilot attempted to recover during the rollout rather than executing a go-around early. The probable cause was the pilot's loss of directional control during the aborted landing in gusting crosswind conditions.

NTSB ERA21LA119 (2021): A Cessna 172R on a personal flight veered left off the runway during landing in gusting crosswind conditions and struck the ground with the propeller and left wing tip. The pilot failed to maintain directional control during landing in a gusting crosswind and did not execute a go-around when the approach became unstable.

NTSB GAA19CA170 (2019): A Piper PA-11 lost directional control during landing roll in gusting crosswind conditions, veered off the runway, struck a ditch, and came to rest inverted. The pilot failed to maintain adequate airspeed during the landing rollout and was unable to regain control when a gust lifted the wing.

NTSB GAA17CA021 (2016): A Luscombe 8 nosed over during landing roll when a wind gust lifted the left wing and the pilot was unable to regain control due to insufficient airspeed. The pilot had delayed the crosswind correction during the landing roll with a gusting left crosswind, which resulted in the airplane weathervaning and nosing over.

The consistent thread across all these events: pilots continue unstable approaches in gusty crosswind conditions below the point of safe recovery. The decision to go around must be made BEFORE you are too low to execute it safely — typically by 300 ft AGL on short final. Once you are below 150 ft AGL in a loss-of-control situation, a go-around is risky; continuing is riskier. The correct decision is made before the approach begins: brief a go-around decision point, and execute it decisively if the approach is not stable and within limits.

KTPA's dominant accident pattern includes LOSS_OF_CONTROL_GROUND (8.9%) and RUNWAY_EXCURSION (6.7%). The field's towered Class B environment, long runways (11,002 ft on Runway 19R), and proximity to dense development make crosswind loss-of-control accidents particularly consequential. The off-field environment off Runway 19R (heading 182°) is dense development, medium development, and pasture — not ideal for a forced landing, but survivable. The key is recognizing when the approach is unstable and committing to the go-around BEFORE you are too low to execute it safely.

Key lesson — In gusty crosswind conditions at the edge of your demonstrated capability, brief a go-around decision point BEFORE the approach begins. If the approach is not stable and within limits by that point, execute the go-around decisively. Do not continue an unstable approach below 300 ft AGL on short final. Once you are below 150 ft AGL in a loss-of-control situation, your options are gone. The decision is made before the approach begins, not during it.

Debrief — teaching points

Know your demonstrated crosswind capability and your personal minimums.

The Piper Arrow's demonstrated crosswind capability is 17 knots. That is the limit of the manufacturer's testing — not a hard limit, but a boundary beyond which the airplane has not been tested. Your personal minimums should be LOWER than the demonstrated capability, typically 12–15 knots for most pilots. In this scenario, the steady crosswind was 12–16 knots with gusts to 22+ knots. The gusts exceeded the demonstrated capability. Recognize when conditions exceed your demonstrated capability and commit to a go-around or diversion BEFORE the approach begins.

Brief a go-around decision point before the approach begins.

A go-around decision point is a specific altitude or point at which you will abort the approach if it is not stable and within limits. For a crosswind landing, a typical decision point is 300 ft AGL on short final: if the approach is not stable and within 1 dot of the localizer by 300 ft AGL, you will go around. Brief this decision point with ATC before the approach begins. This removes the decision-making from the moment of stress and commits you to a clear action.

Recognize an unstable approach and execute the go-around decisively.

An unstable approach in a crosswind is characterized by repeated corrections for drift, wing-rocking oscillations, and a feeling that you are 'fighting' the airplane. If you find yourself making constant aileron and rudder corrections, the approach is unstable. Do not push through — go around. A go-around below 300 ft AGL is still safe; a go-around below 150 ft AGL is risky; continuing an unstable approach below 150 ft AGL is the highest risk. Make the decision early.

Maintain adequate airspeed throughout the approach to retain control authority.

In gusty crosswind conditions, maintaining adequate airspeed (slightly above Vref, 75 KIAS) gives you control authority to respond to gusts. At Vref or below, your control response is sluggish and you have minimal margin. In this scenario, increasing airspeed to 90–95 KIAS or reducing flaps to 10° both increased control authority. The trade-off is increased landing distance, but the 11,002 ft runway at KTPA was long enough to accommodate it. Know your runway length and your landing distance at various airspeeds and flap configurations.

Understand the tactical adjustments available in a crosswind approach.

If the approach is becoming unstable in a crosswind, you have several tactical options: (1) increase airspeed slightly (trade landing distance for control authority), (2) reduce flaps (trade landing distance for control authority), (3) increase power to maintain airspeed (trade landing distance for control authority), or (4) go around. All of these are valid. The key is recognizing which adjustment is appropriate for the situation and the runway length available. A 11,002 ft runway gives you plenty of room for a faster or longer landing. A 3,000 ft runway does not.

At KTPA, the off-field environment is dense development — not ideal for a forced landing.

Off Runway 19R (heading 182°), the off-field environment is dense development, medium development, and pasture. Off Runway 01L (heading 002°), the environment is also dense development and open developed areas (parks, large lots). Neither is ideal for a forced landing. This makes the decision to go around or divert even more important. If the approach is unstable and you cannot land on the runway, you do not have a good off-field option. Commit to the go-around early.

Built from the real accident record

Scenario built from NTSB WPR25LA178 (2025 PA-28R brake failure / runway excursion), CEN24LA288 (2024 PA-28R gear-up landing), CEN23LA417 (2023 PA-28RT gear retraction), CEN21LA269 (2021 PA-28R loss of directional control on takeoff), and regional crosswind-loss-of-control precedents GAA17CA105, ERA21LA119, GAA19CA170, GAA17CA021. Localized to KTPA.

NTSB reports: WPR25LA178 · CEN24LA288 · CEN23LA417 · CEN21LA269 · GAA17CA105 · ERA21LA119 · GAA19CA170 · GAA17CA021

ACS tasks: PA.V.A — Preflight Inspection · PA.V.B — Cockpit Management · PA.VI.A — Takeoff and Climb · PA.VI.B — Approach and Landing · PA.VII.A — Flight by Reference to Instruments · PA.I.F — Weather Information · PA.I.H — Human Factors

Relevant FARs: §91.3 · §91.13 · §91.175 · §91.205

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