Gusts on Final to Tampa International
Crosswind landing in gusty conditions, loss of directional control, and a runway excursion — the decision to go around must come early
The scenario
Approaching Tampa International Airport (KTPA), Tampa, FL — Runway 19R, an 11,002-foot concrete runway aligned 182° magnetic. Field elevation 26 ft MSL. You are on a personal flight from a nearby satellite airport, returning to KTPA for fuel and a quick turnaround. Piper Archer PA-28-181, solo, 2,400 lb gross weight, within limits.
The weather is VFR but deteriorating. Surface wind is reported from 180° at 14 knots, gusting to 22 knots. Runway 19R is aligned 182°, so the wind is nearly aligned with the runway — but the gusts are significant and variable. The ATIS also mentions wind shear on approach: 'Windshear reported by departing traffic, 1,500 feet, climb out heading 010°.' The wind is not steady; it is layered and gusty.
You are on a 5-mile final to Runway 19R, 1,200 feet AGL, descending at 76 KIAS (best glide speed, your approach speed). The runway is in sight. The tower has cleared you to land. Off the runway ends, the environment is dense development — buildings, roads, parking lots — with some open developed areas (parks, large lots). There is no grass strip, no water, no alternate landing surface. The runway is your target.
Aircraft: Piper Archer PA-28-181, carbureted Lycoming O-360, 180 hp, fixed-pitch prop, fixed gear, steam panel. Fuel selector is LEFT / RIGHT (no BOTH position). Flaps are at 20°. You are configured for landing.
Pilot: You — a Private pilot, current, roughly 250 hours total. You have landed at KTPA twice before, both times in calm conditions. You have not practiced crosswind landings in conditions this gusty. Your personal minimums are 'demonstrated crosswind capability' — which for the Archer is 12 knots. The gusts are at 22 knots. You have not explicitly decided whether 22-knot gusts exceed your comfort or your airplane's demonstrated capability.
- {'label': 'Field', 'value': 'KTPA · Tampa'}
- {'label': 'Runways', 'value': '10/28 · 19L/01R · 19R/01L'}
- {'label': 'Elevation', 'value': '26 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-181'}
- {'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 Archer and when to go around? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB ERA10CA473 (2010): A Piper PA-28 on approach to a destination airport encountered windshear and stalled during landing, resulting in a hard landing and runway excursion. The probable cause was the pilot's inadequate compensation for crosswind conditions.
NTSB LAX08CA199 (2008): A Piper PA-28-181 student pilot on solo flight landed with excessive airspeed after delaying flap extension. The aircraft bounced on touchdown, veered left during recovery, departed the runway, and struck a ditch, collapsing the nose gear and damaging the firewall. The probable cause was inadequate recovery from the bounced landing and loss of directional control.
NTSB CHI05CA208 (2005): A Piper PA-28-181 overran a grass runway and struck a utility pole during landing at Bird Field Airport, Missouri. The probable cause was the pilot's delayed decision-making, excessive approach airspeed, and failure to execute a go-around. Contributing factors included high density altitude and obstacles near the runway.
NTSB LAX04CA289 (2004): A Piper PA-28-181 on a student instructional flight experienced a hard landing and runway excursion at Scottsdale Airport. The probable cause was the student pilot's misjudged flare, resulting in a stall and hard landing, and failure to maintain directional control during landing rollout.
NTSB ERA10FA020 (2009, FATAL): A Piper PA-28-181 on a personal local flight landed fast and hard on a wet turf runway at Oliver Springs Airport, lost directional control during rollout, and collided with trees. The probable cause was the pilot's loss of directional control while landing on a wet runway.
Regional precedents (GAA17CA105, ERA21LA119, GAA19CA170, GAA17CA021) consistently show the same pattern: loss of directional control during landing in gusty crosswind conditions. The common thread is that pilots either (1) did not recognize when crosswind conditions exceeded their demonstrated capability, (2) continued unstable approaches to low altitude, or (3) lost control authority during landing rollout by reducing airspeed too aggressively.
The real accidents cited above occurred at other airports and in other aircraft — NOT at KTPA. KTPA has its own accident history (see field dominant patterns: 22.2% forced landing, 11.1% loss of control inflight, 8.9% loss of control ground, 6.7% wire strike, 6.7% gear-up landing). 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 gusty crosswind conditions is preventable. The decision to go around must come early — on final approach when the approach becomes unstable, not during the flare or rollout. Maintaining adequate airspeed throughout the landing rollout is critical to keeping the controls effective. The Archer's demonstrated crosswind capability is 12 knots — personal minimums should be well below that, especially for pilots with limited crosswind experience.
Key lesson — Recognize when crosswind conditions exceed your demonstrated capability and your personal minimums. Commit to the go-around decision early — on final approach, not during the flare. Maintain adequate airspeed throughout the landing rollout to keep the controls effective in gusty conditions. The trap is always the same: too low to go around comfortably, too unstable to land safely. The way out is to recognize the instability early and go around while you still have altitude and energy.
Debrief — teaching points
The Piper Archer's demonstrated crosswind capability is 12 knots — know this limit.
The Piper PA-28-181 Archer has a demonstrated crosswind capability of 12 knots. This is the maximum the manufacturer has tested and approved. Your personal minimums should be well below this — 10 knots is reasonable for a pilot with limited crosswind experience. When the wind is gusting, the gust component (peak gust minus mean wind) is what matters. A 22-knot gust on a 14-knot mean wind is an 8-knot gust component — but if the mean wind is from a different direction, the crosswind component can exceed the demonstrated limit. Know the wind direction, the runway heading, and the resulting crosswind component before committing to the approach.
An unstable approach at low altitude is a trap — go around early.
If the approach becomes unstable — wings being buffeted, nose cocked, constant corrections needed — the correct response is to go around immediately. The trap is always the same: at 400 ft AGL or 30 ft AGL, it feels too late to go around, so the pilot tries to force the landing. But forcing an unstable approach into a landing at low altitude is how runway excursions happen. Go around while you still have altitude and energy. Going around is not a failure — it is airmanship.
Maintain adequate airspeed during landing rollout to keep the controls effective.
In gusty conditions, maintain at least 40 KIAS during the landing rollout. At this speed, the rudder and ailerons remain effective to correct for wind gusts. Heavy braking that reduces airspeed below 40 KIAS removes your ability to correct for a gust-induced wing lift or nose swing. Use gentle braking and forward-slip if needed to maintain control authority. A slower rollout in gusty conditions is better than a hard brake application.
Brief yourself on the go-around decision before the approach.
Before you begin the approach, decide in advance: at what point will you go around? If the approach becomes unstable at 2 miles out, will you go around? At 1 mile out? At 400 ft AGL? At 30 ft AGL? Having a pre-briefed decision rule makes it easier to execute the go-around when the moment comes. The rule might be: 'If the approach is unstable at any point, I will go around immediately.' Or: 'If the crosswind component exceeds 10 knots, I will go around.' Having the decision made in advance removes the hesitation and the trap.
Recognize the difference between correctable drift and uncontrollable yaw.
In a crosswind landing, some drift is normal and correctable. The airplane drifts to the right, you correct with left aileron and left rudder, and the airplane comes back into alignment. But if the corrections are sluggish or ineffective — if the airplane is not responding to your control inputs — that is uncontrollable yaw. That is the signal to go around. The Archer at 76 KIAS has good control authority; at 66 KIAS (Vref) or below, the control response is slower. In gusty conditions, maintain 76 KIAS all the way to the flare to keep the controls responsive.
Built from the real accident record
Scenario built from NTSB ERA10CA473 (2010 PA-28-181 windshear/stall/hard landing), LAX08CA199 (2008 PA-28-181 bounced landing/loss of directional control), CHI05CA208 (2005 PA-28-181 runway overrun/excessive airspeed), LAX04CA289 (2004 PA-28-181 misjudged flare/directional control loss), ERA10FA020 (2009 PA-28-181 wet runway/tree strike), CEN23LA345 (2023 PA-28 fuel exhaustion), and regional crosswind precedents GAA17CA105, ERA21LA119, GAA19CA170, GAA17CA021. Localized to KTPA.
NTSB reports: ERA10CA473 · LAX08CA199 · CHI05CA208 · LAX04CA289 · ERA10FA020 · CEN23LA345 · GAA17CA105 · ERA21LA119 · GAA19CA170 · GAA17CA021
ACS tasks: PA.I.F — Weather Information · PA.III.A — Preflight Preparation · PA.III.B — Preflight Procedures · PA.III.C — Takeoff and Departure · PA.III.D — In-Flight Maneuvers · PA.III.E — Navigation · PA.III.F — Slow Flight, Stalls, and Spins · PA.III.G — Emergency Operations · PA.IV.A — Approaches and Landings · PA.IV.B — Go-Around / Rejected Landing
Relevant FARs: §91.3 · §91.13 · §91.103
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 Archer scenarios · More scenarios at KTPA