Gusts on Short Final — Tampa International
Crosswind landing in gusty conditions at a towered Class B field; directional control and go-around decision under pressure
The scenario
Departing Tampa International Airport (KTPA), Tampa, FL — Runway 10 for landing, elevation 26 ft MSL. You are a Private pilot with roughly 180 hours total time, 45 hours in the Diamond DA20-C1. This is a local training flight; you departed 45 minutes ago and are now on approach to land.
The weather is VFR but deteriorating: winds are reported from 080° at 12 knots, gusting to 18 knots. Runway 10 is aligned 092° true. The wind is a left quartering headwind — roughly 30° off the runway heading — with gusts that are unpredictable and strong. The crosswind component is approximately 10–12 knots steady, with gusts adding another 4–6 knots. The DA20's demonstrated crosswind capability is 12 knots. You are at the edge of your airplane's limit, and the gusts are pushing you over it.
You are cleared for a straight-in approach to Runway 10. You are at 1,200 ft MSL (roughly 1,170 ft AGL), 8 nm from the field, descending at 500 fpm. The runway is in sight. You have been flying the DA20 for 45 hours; you have landed in crosswinds before, but not in gusts this strong. Your CFI is not on board — this is a solo flight.
Aircraft: Diamond DA20-C1, solo, 1,400 lbs (well within limits). Fuel is adequate. The airplane is airworthy. The DA20 is a light, slippery trainer with a fixed nosewheel and fixed gear — it is sensitive to wind and requires active directional control, especially during landing rollout. The castering nosewheel needs differential braking for directional control; there is no nose-wheel steering.
Pilot: you — Private pilot, 180 hours total, 45 hours DA20. You have not flown in gusts this strong before. You did not brief a personal crosswind minimum before departure. You are focused on landing; you have not yet considered whether the conditions exceed your capability or the airplane's demonstrated limit.
- {'label': 'Field', 'value': 'KTPA · Tampa'}
- {'label': 'Runways', 'value': '10/28 · 19L/01R · 19R/01L'}
- {'label': 'Elevation', 'value': '26 ft'}
- {'label': 'Aircraft', 'value': 'DA20'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we get into the decision tree — what do you already know about crosswind landings in the DA20? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB GAA18CA474 (2018): A Diamond DA20 student training flight experienced loss of directional control during landing in a left quartering headwind at a non-towered airport. The student pilot failed to maintain directional control during landing rollout, resulting in a ground loop and landing gear collapse. The probable cause was the student pilot's failure to maintain directional control during landing in crosswind conditions. The wind was reported at 12 knots, within the DA20's demonstrated limit — but the gusts and the student's lack of experience made the actual crosswind component exceed the pilot's capability.
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 rollout instead of going around early. The accident resulted from the pilot's loss of directional control in a gusting crosswind.
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. The probable cause was the pilot's failure to recognize when tactical adjustments (flap reduction, airspeed increase) were insufficient and when to go around.
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 pilot failed to maintain adequate airspeed during landing rollout to retain control authority in gusty conditions.
NTSB GAA17CA021 (2016): A Luscombe 8 tailwheel-equipped aircraft 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 delayed 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: loss of directional control during landing in crosswind conditions is a function of three factors: (1) wind strength relative to the aircraft's demonstrated limit, (2) gust intensity and unpredictability, and (3) pilot experience and control authority margin. The DA20, like all light aircraft, is sensitive to wind. The castering nosewheel requires active differential braking for directional control — there is no nose-wheel steering. At landing speed (55 KIAS, Vref), rudder authority is marginal. A gust-induced drift at 30 ft AGL with marginal control authority is a trap: you are too low to go around safely, but you do not have the control authority to correct the drift.
The real accidents cited above occurred at other airports — NOT at KTPA. KTPA has its own accident history (see field dominant patterns), but these specific events happened elsewhere. The scenario is localized to KTPA to make the runway environment and airspace real for you as a student here.
The correct defenses against this accident are: (1) set personal crosswind minimums before the flight (typically 8–10 knots for a Private pilot in a DA20), (2) recognize when steady wind + gusts exceed your limit and request a runway change early, (3) if you continue the approach, increase airspeed (reduce flaps) to maintain control authority, and (4) commit to a go-around on short final if control is marginal — do not attempt recovery during rollout at low altitude.
Key lesson — The DA20's demonstrated crosswind capability is 12 knots — but that is a limit tested by the manufacturer, not a personal minimum. Gusts add to the steady crosswind component. At landing speed (55 KIAS, Vref), rudder authority is marginal. If you are uncomfortable with the wind on approach, request a runway change or go around early — not on short final. If you continue the approach, increase airspeed (reduce flaps to T/O setting) to maintain control authority all the way to touchdown. Off-center landings and ground loops happen when pilots commit to landings they cannot control.
Debrief — teaching points
The DA20's demonstrated crosswind capability is 12 knots — but gusts add to the steady component.
The DA20 POH lists a demonstrated crosswind capability of 12 knots. This is the limit tested by the manufacturer in controlled conditions — typically with a steady wind, not gusts. When the wind is reported as 080° at 12G18 knots, the steady component is 12 knots, but the gusts add another 6 knots, bringing the peak crosswind to 18 knots. This exceeds the demonstrated limit. Personal minimums should be lower than the demonstrated limit — typically 8–10 knots for a Private pilot with moderate experience. Set your personal minimum before the flight, not on short final.
At landing speed (55 KIAS, Vref), rudder authority is marginal in the DA20.
The DA20 has a castering nosewheel with no steering — directional control during landing rollout depends entirely on differential braking and rudder authority at low speed. At 55 KIAS (Vref, landing flap), rudder authority is minimal. A gust-induced drift at 30 ft AGL with 55 KIAS airspeed is a trap: you cannot correct the drift with rudder alone, and you are too low to go around safely. The defense is to maintain higher airspeed (65 KIAS or more) all the way to touchdown by reducing flaps to T/O setting. This keeps control authority throughout the approach.
Increase airspeed (reduce flaps) early if crosswind conditions are marginal.
If you recognize on approach that the crosswind is stronger than expected, reduce flaps to T/O setting to increase airspeed to 65 KIAS. This gives you better control authority for the remaining descent and landing. The trade-off is a longer landing distance, but Runway 10 at KTPA is 6,999 ft — plenty of room. The key is to make this decision early (on downwind or base), not on short final. If you add landing flap on short final after reducing it, you are back to marginal control authority at low altitude.
Request a runway change early if the wind is not aligned with your initial runway.
KTPA has three parallel runways (10/28, 19L/01R, 19R/01L). If the wind is a strong crosswind for Runway 10, Runway 28 may have a more favorable wind alignment. Request the change on downwind or base, not on short final. The NTSB precedents (GAA17CA105, ERA21LA119) emphasize the importance of this decision: recognize when conditions exceed your limits and commit to a runway change early.
Go around on short final if control is marginal — do not attempt recovery during rollout.
If you are on short final and a gust causes a drift that you cannot correct with available control authority, go around. You have altitude, you have power, and you have time. A go-around is not a failure — it is airmanship. The NTSB GAA18CA474 DA20 accident happened because the pilot committed to a landing at 30 ft AGL with marginal directional control. By the time the pilot realized control was lost, it was too late to go around. The correct decision was to go around on short final when the first gust showed that control was marginal.
The forward slip is a valid recovery technique for drift on short final — but only if you have altitude.
If you are on short final and a gust causes a drift, you can execute a forward slip (cross-control: right rudder, left aileron) to correct the drift and align with the runway. This is advanced technique, but it is the correct recovery if you have 50+ feet of altitude and the runway is close. Below 50 feet, a slip is risky — if the slip does not recover quickly, you do not have altitude to recover. In that case, go around instead.
Built from the real accident record
Scenario built from NTSB GAA18CA474 (2018 DA20 loss of directional control during landing in crosswind), GAA17CA105 (2016 PA-46 crosswind loss of control), ERA21LA119 (2021 C172R crosswind landing veering), GAA19CA170 (2019 PA-11 crosswind ground loop), and GAA17CA021 (2016 Luscombe 8 gust-induced nose-over). Real events occurred at other airports — NOT at KTPA.
NTSB reports: GAA18CA474 · GAA17CA105 · ERA21LA119 · GAA19CA170 · GAA17CA021
ACS tasks: PA.II.E — Crosswind Takeoff and Landing · PA.II.F — Slip to a Landing · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors · PA.II.A — Preflight Inspection
Relevant FARs: §91.3 · §91.13 · §91.175
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 Diamond DA20-C1 scenarios · More scenarios at KTPA