Gusts on Final to Runway 19R
Crosswind landing in gusty conditions at a towered Class B airport — the decision to go around must come early
The scenario
Departing Tampa International Airport (KTPA), Tampa, FL — Runway 19R, an 11,002 ft concrete runway on a 182° magnetic heading. Elevation 26 ft MSL. You are on a local instructional flight with your CFI in the right seat, practicing approaches and landings.
The weather is VFR: scattered clouds at 3,500 ft, visibility 10 SM, temperature 24°C, dew point 18°C. Wind is reported from 160° at 12 knots, gusting to 18 knots. Runway 19R's magnetic heading is 182°, so the wind is a crosswind from the left (160° is 22° off the runway heading). The demonstrated crosswind capability of the Piper Warrior is approximately 12 knots; the gusts are at the limit.
You have completed three full-stop landings on Runway 19R this session. The first two were stable, centered, and uneventful. On the third approach, you noticed the airplane drifting slightly left on short final, but you corrected with right rudder and aileron and landed without incident. The CFI said nothing — a sign that the landing was acceptable, if not perfect.
You are now on your fourth approach to Runway 19R. You are on a 3° glide slope, 500 ft AGL, 1.5 nm from the runway threshold. The wind is still from 160°, gusting. The runway is long and wide — plenty of room. You are flying the approach at 70 KIAS (slightly above Vref of 63 KIAS with full flaps, a common practice for gusty conditions). The CFI is monitoring but not flying.
Aircraft: Piper PA-28-161 Warrior, solo plus CFI, within limits. Carbureted Lycoming O-320, fixed-pitch prop, fixed gear, steam panel. Full flaps are available; you are planning to use 40° (full flaps) for landing. Runway 19R is 11,002 ft of concrete — more than enough for a Warrior.
Pilot: you — a Private pilot, current, roughly 180 hours total. You have 15 hours in the Warrior and have landed at KTPA twice before (both times on Runway 01L in calm wind). This is your first time landing on Runway 19R in crosswind conditions. Your personal crosswind limit is 'whatever the airplane can do,' which is not a limit at all.
- {'label': 'Field', 'value': 'KTPA · Tampa'}
- {'label': 'Runways', 'value': '10/28 · 19L/01R · 19R/01L'}
- {'label': 'Elevation', 'value': '26 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-161'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we get into the decision tree — what do you know about crosswind landings in the Piper Warrior? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB IAD04FA033 (2004, FATAL): A Piper PA-28-161 on touch-and-go practice at New Garden Airport veered off the runway during landing in gusty crosswind conditions. The pilot attempted to add power to abort the landing after the airplane had veered off the runway. The added power increased the rate of departure from the runway centerline. The airplane struck parked vehicles and a hangar at high speed. The probable cause was the pilot's decision to add power in an attempt to abort the landing after the airplane had veered off the runway, combined with failure to maintain directional control. The fatal error was adding power instead of reducing power and applying full rudder and aileron to execute a go-around.
NTSB CEN11LA183 (2011): A Piper PA-28-161 on a local personal flight experienced rough engine operation during climbout and returned for a precautionary landing. The accident resulted from loss of directional control during the landing roll in gusty crosswind conditions. The pilot's failure to maintain directional control during the landing roll was the probable cause. Contributing factors included carburetor icing conditions and snow on the runway, which reduced traction and made directional control more difficult.
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 instead of executing a go-around early. The accident was attributed to the pilot's loss of directional control during the aborted landing in gusting crosswind conditions. The lesson: recognize when crosswind conditions exceed aircraft limits and commit to a go-around early rather than attempting recovery during rollout.
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 accident was attributed to the pilot's failure to maintain directional control during landing in a gusting crosswind. The pilot did not recognize that the crosswind conditions exceeded their personal minimums and did not execute a go-around when the approach became unstable.
NTSB GAA19CA170 (2019): A Piper PA-11 tailwheel aircraft lost directional control during landing roll in gusting crosswind conditions, veered off the runway, struck a ditch, and came to rest inverted. The accident was attributed to the pilot's failure to maintain adequate airspeed during landing rollout in gusty conditions. At low airspeed, a gust-induced wing lift cannot be corrected with aileron and rudder — the airplane will weathervane into the wind and lose directional control.
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%, LOSS_OF_CONTROL_GROUND 8.9%, WIRE_STRIKE 6.7%, GEAR_UP_LANDING 6.7%), but these specific 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: loss of directional control in crosswind landings is insidious. It builds gradually — first a small drift, then a larger drift, then a loss of control. The decision to go around must come EARLY, on base leg or early on final, not during the landing rollout when options are gone. Adding power to abort a landing after the airplane has veered off the runway is dangerous — it increases the rate of departure and reduces control authority. The correct response is to reduce power and apply full rudder and aileron to execute a go-around.
Key lesson — In gusty crosswind conditions at the limit of the aircraft's demonstrated capability, the decision to go around must come early — at 300 ft AGL on short final, not at 100 ft AGL during the landing rollout. Recognize when crosswind conditions exceed your skill level and divert to a more favorable runway. If you do lose directional control during landing, reduce power and apply full rudder and aileron to execute a go-around — do NOT add power. At KTPA, the off-field environment off all runway ends is dense development — a loss of directional control during landing can result in a runway excursion into buildings, roads, or parked aircraft.
Debrief — teaching points
The Piper Warrior's demonstrated crosswind capability is approximately 12 knots — that is a reference point, not a hard limit.
The Piper PA-28-161 Warrior's demonstrated crosswind capability is approximately 12 knots. This is the maximum crosswind the manufacturer tested during certification. However, this is NOT a hard limit — it is a reference point. In gusty conditions, the peak gust can exceed the demonstrated capability, and the airplane may not be controllable. Personal minimums for crosswind landings should be LOWER than the demonstrated capability, especially in gusty conditions. A reasonable personal limit for a 180-hour pilot is 10 knots steady crosswind, with no gusts exceeding 15 knots.
A gust that exceeds your crosswind capability will lift a wing and cause weathervaning (yaw) — at low altitude, there is no time to recover.
When a crosswind gust exceeds the airplane's control authority, the upwind wing will lift and the airplane will yaw into the wind (weathervane). At low altitude during landing, there is no time to recover from a loss of directional control. The airplane will drift off the runway and collide with off-field obstacles. The key is to recognize the loss of control EARLY — on short final or during the approach — and execute a go-around before the situation becomes unrecoverable.
The decision to go around must be made EARLY — on base leg or early on final — not during the landing rollout.
An unstable approach in crosswind conditions is a sign that the crosswind is beyond your current skill level. The correct response is a go-around, and the decision must be made EARLY — at 300 ft AGL on short final or earlier. At 100 ft AGL during the landing rollout, a go-around is still possible, but the margin is thin. At 50 ft AGL, a go-around is marginal and risky. The earlier you make the decision, the safer the go-around.
Adding power to abort a landing after the airplane has veered off the runway is dangerous — it increases the rate of departure and reduces control authority.
NTSB IAD04FA033 is a fatal accident caused by a pilot adding power to abort a landing after the airplane had veered off the runway. The added power increased the rate of departure from the runway centerline and reduced the airplane's ability to correct the yaw. The correct response to a loss of directional control during landing is to REDUCE power and apply FULL rudder and aileron to execute a go-around. Do NOT add power — this will make the situation worse.
Increasing airspeed (by reducing flaps or adding power early in the approach) can improve control authority in gusty conditions — but the runway must be long enough.
In gusty crosswind conditions, increasing airspeed can improve control authority and stability. You can reduce flaps from 40° to 20° to increase airspeed to 75 KIAS, or add power early in the approach to maintain a higher descent rate. The increased airspeed gives better control feel and allows you to correct wind gusts more effectively. However, the runway must be long enough to accommodate the increased landing distance. At KTPA, Runway 19R is 11,002 ft — plenty of room for a Warrior with reduced flaps.
Recognize when crosswind conditions exceed your skill level and divert to a more favorable runway — this is good airmanship, not a failure.
At KTPA, you have multiple runway options: Runway 19R (182° heading), Runway 10 (92° heading), and Runway 28 (272° heading). If the wind is from 160°, Runway 19R is a left crosswind, Runway 10 is a headwind, and Runway 28 is a tailwind. If the crosswind on Runway 19R is beyond your skill level, divert to Runway 10 (headwind) or Runway 28 (if the tailwind is acceptable). Recognizing your limits and making a conservative decision is good airmanship.
Built from the real accident record
Scenario built from NTSB IAD04FA033 (2004 PA-28-161 loss of directional control / power-on abort), CEN11LA183 (2011 PA-28-161 loss of directional control landing), and regional precedents GAA17CA105, ERA21LA119, GAA19CA170, GAA17CA021 (crosswind loss-of-control events). Localized to KTPA.
NTSB reports: IAD04FA033 · CEN11LA183 · GAA17CA105 · ERA21LA119 · GAA19CA170 · GAA17CA021
ACS tasks: PA.I.F — Weather Information · PA.VII.A — Approach and Landing · PA.VII.B — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.II.A — Preflight Assessment
Relevant FARs: §91.3 · §91.13 · §91.209
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 Warrior scenarios · More scenarios at KTPA