Gusting Crosswind on Runway 27
Loss of directional control 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 27, landing after a 45-minute local flight. Elevation 76 ft MSL. The tower is active (1400 local, within 0700–2200 operating hours). You are in Class D airspace; Tampa Class B overlies above 6,000 ft MSL.
The weather is VFR but deteriorating: winds are from 310° at 12 knots, gusting to 18 knots. Runway 27 is aligned 270° (true heading). The crosswind component is roughly 8–10 knots steady, with gusts pushing 15–16 knots. The Piper Warrior PA-28-161 has a demonstrated crosswind capability of approximately 12 knots in calm conditions; in gusts, the effective limit is lower. The tower has issued a crosswind warning: 'Caution, gusting crosswind, recommend Runway 09 for landing.'
You have been flying locally for the past 45 minutes, practicing slow flight and steep turns. You are familiar with KBKV. You have logged 180 hours total time, 60 hours in the Warrior. Your last three landings were on Runway 09 (the longer runway, 7,001 ft, aligned 090°). Runway 27 is 4,200 ft, aligned 270°. A landing on Runway 09 would require a 180° turn from your current downwind position and would take you into the wind — a longer, more complex approach. Runway 27 is ahead, downwind is set up, and you are at pattern altitude (1,500 ft MSL, roughly 1,424 ft AGL).
Aircraft: Piper Warrior PA-28-161, solo, within limits. Carbureted Lycoming O-320-D, fixed-pitch prop, fixed gear, steam panel. Fuel selector on LEFT tank (you switched from RIGHT on downwind, per procedure). Nothing was written up; the airplane is airworthy.
Pilot: you — a Private pilot, current, 180 hours total, 60 hours in type. You have landed the Warrior in crosswind before, but not in gusts this strong. The tower's recommendation to use Runway 09 registered, but Runway 27 is set up and available. The decision is yours under 14 CFR §91.3.
- {'label': 'Field', 'value': 'KBKV · Brooksville–Tampa Bay'}
- {'label': 'Runways', 'value': '3/21 · 9/27'}
- {'label': 'Elevation', 'value': '76 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-161'}
- {'label': 'Dominant phase', 'value': 'Landing / Cruise'}
The decision
Before we enter the decision tree — what do you know about crosswind landing technique and limits 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 (a non-towered field in Pennsylvania) veered off the runway during landing rollout and collided with 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 aircraft had veered off the runway, combined with failure to maintain directional control. The pilot was killed. This is the exact fatal decision: adding power during a loss-of-control situation on the ground. The Warrior does not recover from loss of directional control by acceleration — it crashes.
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. Contributing factors included carburetor icing conditions and snow on the runway. The pilot lost directional control during the rollout and the airplane veered off the runway. The lesson: loss of directional control during rollout is a critical phase. Crosswind, snow, or other surface conditions that reduce control authority require immediate corrective action — slip technique, braking, or go-around.
NTSB GAA17CA105 (2016): A Piper PA-46 (a high-performance single) experienced loss of directional control during landing rollout in gusting crosswind conditions that exceeded the aircraft's demonstrated crosswind capability. The accident resulted from the pilot's loss of directional control during the aborted landing in gusting crosswind conditions. The teaching angle: recognize when crosswind conditions exceed aircraft limits and commit to go-around early rather than fighting deteriorating control 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 lesson: technique adjustments (reduced flaps, extra airspeed) have limits. Recognize when wind conditions exceed personal minimums and execute go-around before touchdown.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Brooksville–Tampa Bay Regional Airport (KBKV). However, KBKV's own accident history shows that runway excursion (11.5% of accidents) and loss of control on the ground (7.7%) are dominant patterns at this field. The scenario is localized to KBKV to make the decision consequential: tower's recommendation to use Runway 09 instead of Runway 27 in gusting crosswind is based on safety assessment. Your personal minimums and experience level should align with that recommendation.
The consistent thread across all these events: loss of directional control during landing rollout in crosswind conditions is insidious. It builds gradually as gusts exceed the aircraft's demonstrated capability. The first sign is a wing lifting or the airplane drifting. The fatal mistake is adding power — the correct response is to reduce power, apply slip technique (lower the upwind wing, opposite rudder), and brake. At 180 hours total and 60 hours in type, accepting a go-around to a more favorable runway is the professional, conservative choice.
Key lesson — The Piper Warrior's demonstrated crosswind capability is approximately 12 knots in calm conditions. Gusts reduce the effective limit significantly. When tower recommends a different runway due to wind, that recommendation reflects their assessment of safety. At your experience level, the discipline to go around and use the longer runway with a more favorable wind is the correct decision. Loss of directional control during landing rollout is not recoverable by adding power — it is fatal. The correct response is to reduce power, apply slip technique (lower the upwind wing, opposite rudder), and brake.
Debrief — teaching points
The Warrior's demonstrated crosswind capability is approximately 12 knots in calm conditions.
The Piper Warrior PA-28-161 POH lists a demonstrated crosswind capability of approximately 12 knots. This is measured in calm conditions with a skilled pilot. Gusts reduce the effective limit significantly. A gust that exceeds the demonstrated capability by even 3–4 knots can cause sudden loss of lateral control during rollout. At KBKV, a wind of 310° at 12G18 knots on Runway 27 (aligned 270°) produces a crosswind component of roughly 8–10 knots steady with gusts to 15–16 knots. The gust peak exceeds the demonstrated capability. Tower's recommendation to use Runway 09 (a headwind runway) is based on this assessment.
When tower recommends a different runway due to wind, that recommendation is based on safety assessment.
ATC tower personnel have access to wind data, runway dimensions, and aircraft performance data. Their recommendation to use a different runway due to wind is not a suggestion — it is a safety assessment. At 180 hours total and 60 hours in type, your personal minimums should align with tower's recommendation. The discipline to go around and use the longer runway with a more favorable wind is the professional, conservative choice. The margin between a successful landing and a crash in marginal crosswind conditions is measured in knots of gust and seconds of decision time.
Loss of directional control during landing rollout is not recoverable by adding power.
The fatal mistake in NTSB IAD04FA033 was the pilot's decision to add power during loss of directional control on the ground. The Warrior does not recover from loss of control by acceleration — it crashes. The correct response to loss of directional control during rollout is: (1) reduce power immediately, (2) apply slip technique (lower the upwind wing, apply opposite rudder to keep the nose aligned with the runway), and (3) brake. These actions reduce the control problem and allow the airplane to slow. Do not add power. Do not attempt to take off. Reduce power and slip.
Reduced flaps (20° instead of 40°) in crosswind conditions preserve control authority.
Full flaps (40°) increase the wing's sensitivity to gusts and reduce control authority slightly. In marginal crosswind conditions, reduced flaps (20°) is a sound technique adjustment. It trades a slightly longer landing distance for better control authority and reduced wing-lifting effect. The Warrior's maximum flap-extended speed (Vfe) is 103 KIAS; 20° flaps allow a higher approach speed while maintaining adequate descent rate. This is a valid technique adjustment for crosswind landings.
Slip technique during landing rollout — lower the upwind wing, opposite rudder — is the correct response to crosswind drift.
If the airplane begins to drift during landing rollout due to crosswind, the correct technique is to lower the upwind wing (into the wind) and apply opposite rudder to keep the nose aligned with the runway. This is a forward slip while on the ground. The slip reduces the wing-lifting effect of the crosswind and allows the airplane to align with the runway. Maintain this slip while braking until the airplane is slow enough that wind has minimal effect (roughly 30 KIAS or below). This is the correct technique; it is not a sign of poor landing — it is active management of a crosswind situation.
KBKV's dominant accident pattern includes runway excursion (11.5%) and loss of control on the ground (7.7%).
Brooksville–Tampa Bay Regional Airport's own accident history shows that runway excursion and loss of control on the ground are significant patterns. This is not coincidence — it reflects the field's exposure to crosswind conditions and the challenge of managing directional control in gusts. Know this pattern. When you are landing at KBKV, be aware that the decision to accept a marginal crosswind or go around to a more favorable runway is a decision that has consequences. The field's accident history is the evidence.
Built from the real accident record
Scenario built from NTSB IAD04FA033 (2004 PA-28-161 loss of control during touch-and-go, fatal), CEN11LA183 (2011 PA-28-161 loss of directional control during landing rollout), and regional precedents GAA17CA105 (2016 PA-46 crosswind loss of control), ERA21LA119 (2021 C172R crosswind veering), GAA19CA170 (2019 PA-11 tailwheel crosswind rollout), ERA10CA448 (2010 C182E crosswind nose-over). Localized to Brooksville–Tampa Bay Regional Airport (KBKV).
NTSB reports: IAD04FA033 · CEN11LA183 · GAA17CA105 · ERA21LA119 · GAA19CA170 · ERA10CA448
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.D — 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 Warrior scenarios · More scenarios at KBKV