Gusting Crosswind on Final — Brooksville
Loss of directional control in a DA20 during landing rollout in marginal crosswind conditions — the decision to go-around comes too late
The scenario
Departing Brooksville–Tampa Bay Regional Airport (KBKV), Brooksville, FL — Runway 09, a 7,001-foot concrete runway aligned 090° true. Field elevation 76 ft MSL. You are on a local VFR training flight in a Diamond DA20-C1, solo, full fuel (approximately 38 gallons usable), within weight and balance limits.
It is mid-afternoon on a breezy Florida day. Surface wind is reported by KBKV tower as 080° at 12 knots, gusting to 18 knots. Runway 09 is aligned 090° true — that is a direct crosswind from the left (080° wind on a 090° runway = roughly 10° left quartering headwind, with gusts adding a dynamic crosswind component). The DA20's demonstrated crosswind capability is approximately 12 knots in calm air; in gusts to 18, you are at the edge of demonstrated limits.
You have completed your training flight and are returning to KBKV for landing. You are at 2,000 ft MSL on a 10-mile final approach to Runway 09. The tower has cleared you to land. You are configured for landing: flaps set to landing position (full flap, 78°), airspeed 55 KIAS (Vref — approach speed), descent rate stable at 300 fpm. The runway is in sight, straight ahead.
Aircraft: Diamond DA20-C1, solo, full fuel. Continental IO-240-B fuel-injected engine, fixed-pitch prop, fixed landing gear, castering nosewheel. The DA20 is a light, slippery composite trainer — it floats in ground effect and is sensitive to gusts. Directional control on the ground depends on differential braking and nosewheel steering; there is no nose-wheel shimmy damper.
Pilot: you — a Private pilot, current, roughly 150 hours total. You have 8 hours in the DA20. You have landed in crosswind before, but not in gusts this strong. You are not sure if this is beyond your personal minimums, but you are committed to the approach and the tower has cleared you to land.
- {'label': 'Field', 'value': 'KBKV · Brooksville–Tampa Bay'}
- {'label': 'Runways', 'value': '3/21 · 9/27'}
- {'label': 'Elevation', 'value': '76 ft'}
- {'label': 'Aircraft', 'value': 'DA20'}
- {'label': 'Dominant phase', 'value': 'Landing / Cruise'}
The decision
Before we get into the decision tree — what do you know about crosswind landings in the DA20 and loss-of-control risk on the ground? (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. The student pilot failed to maintain directional control during rollout, resulting in a ground loop. The landing gear collapsed and the airframe was damaged. The probable cause was the student pilot's failure to maintain directional control in crosswind conditions that were at or near the aircraft's demonstrated crosswind 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 land despite marginal conditions and lost control during rollout. The probable cause was the pilot's failure to recognize when crosswind conditions exceeded aircraft limits and commit to a go-around early.
NTSB ERA21LA119 (2021): A Cessna 172R veered left off the runway during landing in gusting crosswind conditions and struck the ground with the propeller and left wing tip. The probable cause was the pilot's failure to maintain directional control during landing in a gusting crosswind. The pilot did not recognize that technique adjustments (reduced flaps, extra airspeed) have limits; the wind conditions exceeded personal minimums.
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 probable cause was the pilot's failure to maintain directional control during the landing roll. In a tailwheel aircraft, an abrupt wing lift in a gust is a loss-of-control warning; the pilot should have committed to power reduction and a controlled exit rather than fighting uncontrollable yaw.
NTSB ERA10CA448 (2010): A Cessna 182E landed on a runway with a direct crosswind and veered left during landing rollout, causing the aircraft to nose over. The probable cause was inadequate compensation for crosswind conditions. The pilot did not make an independent crosswind assessment and did not recognize when wind conditions exceeded personal minimums.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Brooksville–Tampa Bay Regional Airport (KBKV). KBKV's dominant accident pattern is hard landings (26.9%), forced landings (11.5%), and runway excursions (11.5%) — the field's own accident history. This scenario is localized to KBKV to make the runway geometry and off-field environment real for you as a student here.
The consistent thread across all these events: loss of directional control during landing in crosswind conditions is a trap that catches experienced and inexperienced pilots alike. The decision point is NOT during rollout — it is on final approach or in the flare. If conditions are marginal, a go-around or a runway change is the correct decision. Once you are on the ground and losing control, the options are limited and the outcome is often a ground loop or runway excursion.
Key lesson — In the DA20, demonstrated crosswind capability is approximately 12 knots in calm air. Gusts above that are beyond demonstrated limits. If you are marginal on control during approach or flare, go-around or request a headwind runway. The decision to land must be made before the flare — once you are in the flare at 200 ft AGL, a go-around is risky and difficult. If you do lose directional control during rollout, reduce power and apply gentle corrective inputs (differential braking, nosewheel steering) — aggressive corrections will escalate the situation into a ground loop. The safest option when crosswind conditions are marginal is a runway change to a headwind runway or a go-around to reassess.
Debrief — teaching points
Demonstrated crosswind capability is a limit, not a target.
The DA20's demonstrated crosswind capability is approximately 12 knots in calm air. This is the maximum crosswind the aircraft has been tested to handle — not the maximum you should attempt, especially in gusty conditions or with limited experience in type. Gusts are dynamic events; a 12-knot gust on top of a 12-knot mean wind can exceed demonstrated limits. Personal minimums should be lower than demonstrated capability, especially in gusty conditions and with fewer than 50 hours in type.
The decision to land is made on final approach, not during rollout.
Once you are in the flare at 200 ft AGL, a go-around is difficult and risky — the airplane is committed to landing. The decision to land or go-around must be made on short final or during the approach, when you still have altitude and control authority. If directional control is marginal on short final, go-around. If you are uncertain about crosswind conditions, request a runway change to a headwind runway.
The DA20's castering nosewheel requires active directional control during rollout.
The DA20 has a castering nosewheel (not a steerable nose gear like larger aircraft) and no nose-wheel shimmy damper. Directional control during rollout depends on differential braking and nosewheel steering. In a crosswind or gust, you must actively manage the nose with brake inputs. Ignoring a drift or applying aggressive corrective braking can escalate into a ground loop. Gentle, coordinated inputs are the key.
A runway change is a valid and often superior option to fighting marginal crosswind conditions.
If crosswind conditions are marginal for your experience level, request a runway change to a headwind runway. A headwind landing eliminates the crosswind risk, reduces your groundspeed, and gives you more control authority during rollout. The NTSB precedents show that pilots who committed to marginal crosswind landings and lost control had worse outcomes than pilots who requested runway changes or go-arounds. There is no shame in requesting a headwind runway — it is the correct decision.
If you lose directional control during rollout, reduce power and apply gentle corrective inputs.
If the nose drifts during rollout, reduce throttle to idle immediately and apply gentle differential braking and nosewheel steering to correct. Do not apply aggressive braking — this will dig in the main gear and escalate the situation into a ground loop. Gentle, coordinated inputs will slow the airplane and give you control authority to correct the drift. The goal is to regain directional control and come to a smooth stop on the runway.
Runway 09 at KBKV is a crosswind runway in this wind direction; Runway 27 is a headwind runway.
At KBKV, Runway 09 is aligned 090° true and Runway 27 is aligned 270° true. With a wind of 080° at 12 gusting 18, Runway 09 is a direct crosswind from the left, and Runway 27 is a direct headwind. If crosswind conditions are marginal, request Runway 27. The headwind will slow your groundspeed, eliminate the crosswind component, and give you more control authority during landing and rollout.
Built from the real accident record
Scenario built from NTSB GAA18CA474 (2018 DA20 loss of directional control / ground loop in crosswind landing), GAA17CA105 (2016 Piper PA-46 crosswind loss of control), ERA21LA119 (2021 Cessna 172R crosswind landing excursion), GAA19CA170 (2019 Piper PA-11 tailwheel crosswind ground loop), and ERA10CA448 (2010 Cessna 182E crosswind nose-over). Real events occurred at other airports — NOT at Brooksville–Tampa Bay Regional (KBKV).
NTSB reports: GAA18CA474 · GAA17CA105 · ERA21LA119 · GAA19CA170 · ERA10CA448
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.II.F — Approach and Landing · PA.I.H — Human Factors · PA.II.E — Go-Around / Rejected Landing
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 KBKV