Gusting Crosswind on Short Final
Loss of directional control in a Piper Archer during landing in marginal crosswind conditions — the decision to go around must come early
The scenario
Approaching Brooksville–Tampa Bay Regional Airport (KBKV), Brooksville, FL — Runway 09, a 7,001-foot concrete runway aligned 090° magnetic. Elevation 76 ft MSL. You are inbound from the north on a personal flight, solo, 2.2 hours of fuel remaining. The flight has been smooth; you are current and proficient.
Weather at KBKV: VFR, scattered clouds at 3,500 ft, visibility 10 SM. Wind is reported as 120° at 12 knots gusting to 18 knots. Runway 09 is aligned 090° magnetic — that means the wind is a direct crosswind, roughly 30° off the runway heading. The demonstrated crosswind capability of the Piper Archer is 12 knots. The gusts are at or slightly above that limit.
You are 8 nm north of the field, descending through 2,000 ft MSL, cleared for a straight-in approach to Runway 09. The tower is active (part-time, 0700–2200 local; it is 1530 local). You have been flying this approach many times — KBKV is your home field. The off-field environment off Runway 09's departure end (heading 090°) is open developed areas, pasture, and medium development — good forced-landing options if needed. Off Runway 09's approach end (heading 270°) is the same. No water, no mountains, no obstacles.
Aircraft: Piper Archer PA-28-181, solo, 2,200 lb gross weight, within limits. Lycoming O-360-A carbureted engine, fixed-pitch prop, fixed gear, steam panel. Fuel selector on LEFT tank (you switched from RIGHT on descent). Flaps are currently up.
Pilot: you — a Private pilot, 450 hours total, 120 hours in Archers. You have landed in crosswinds before, but never in gusts this close to the demonstrated limit. Your personal crosswind minimum is 10 knots steady; you have not explicitly set a gust limit. The wind is marginal.
- {'label': 'Field', 'value': 'KBKV · Brooksville–Tampa Bay'}
- {'label': 'Runways', 'value': '3/21 · 9/27'}
- {'label': 'Elevation', 'value': '76 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-181'}
- {'label': 'Dominant phase', 'value': 'Landing / Cruise'}
The decision
Before we get into the decision tree — what do you already know about crosswind landings in the Piper Archer? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB ERA10CA473 (2010): A Piper PA-28-181 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. The airplane veered off the runway and struck terrain.
NTSB LAX08CA199 (2008): A Piper PA-28-181 student pilot on solo flight was vectored to a runway and 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 the student pilot's inadequate recovery from the bounced landing and failure to maintain directional control.
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 his failure to maintain directional control during the 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 turf runway, which resulted in a runway excursion and collision with a tree.
The consistent thread: the Piper Archer is a heavier, faster airplane than the Warrior. It carries more landing energy, floats longer in ground effect, and has less aileron authority in full-flap configuration. A fast approach, a bounced landing, or a loss of directional control during rollout in a crosswind can quickly escalate to a runway excursion or nose-gear collapse. The real accidents cited above occurred at other airports — NOT at KBKV. KBKV's own dominant accident pattern is HARD_LANDING (26.9%), FORCED_LANDING (11.5%), and RUNWAY_EXCURSION (11.5%) — the same pattern as the NTSB cases.
The critical decision point is EARLY — on base leg or short final, before you are committed to the landing. If the wind is marginal, the approach is unstable, or you are carrying excess energy, the go-around decision must be made then, not during the flare or rollout. Once you are below 100 ft AGL in a marginal crosswind, your options are limited. The NTSB data show that pilots who delay the go-around decision and try to salvage a marginal approach often end up off the runway.
At KBKV, the off-field environment off all runway ends is good — open developed areas, pasture, and medium development. A forced landing off any runway end is survivable. But a runway excursion or nose-gear collapse during landing is not. The lesson: recognize marginal crosswind conditions early, set a personal gust limit (not just a steady-wind limit), and execute a go-around or diversion before you are committed to the landing.
Key lesson — The Piper Archer's demonstrated crosswind capability is 12 knots steady. Gusts above that are outside the tested envelope. In marginal crosswind conditions (12G18 knots), the go-around decision must be made early — on base leg or short final — not during the flare or rollout. A bounced landing or loss of directional control during rollout in a crosswind can result in a runway excursion or nose-gear collapse. Diverting to an alternate with calmer wind is not a failure; it is airmanship. Set a personal gust limit (e.g., 10 knots steady, 15 knots gust) and stick to it.
Debrief — teaching points
The Piper Archer's demonstrated crosswind capability is 12 knots steady — gusts above that are outside the tested envelope.
The Archer's POH specifies a demonstrated crosswind capability of 12 knots. This is a steady-wind limit, tested by the manufacturer. Gusts above 12 knots are outside the tested envelope. A wind of 120° at 12G18 knots is at or above the limit. Your personal minimums should account for gusts separately — for example, 10 knots steady, 15 knots gust. If the gusts exceed your personal limit, the correct response is a go-around or diversion, not a commitment to land.
The Archer is heavier and faster than a Warrior — it carries more landing energy and floats longer in ground effect.
The Archer weighs 2,550 lb gross; a Warrior weighs 2,450 lb. The Archer is also faster and has more wing loading. In landing, this means the Archer carries more kinetic energy, floats longer in ground effect, and is harder to stop. A fast approach in an Archer is more forgiving than in a Warrior, but it also means a bounced landing is more likely and harder to recover from. Approach speed (66 KIAS) is the target; carrying excess airspeed (80 KIAS) is a setup for a float and bounce.
Full flaps reduce aileron authority — in a crosswind, reduced flaps (20°) may be the better trade-off.
Full flaps (40°) increase drag and reduce landing distance, but they also reduce aileron authority and control response. In a crosswind, the loss of control authority can be a liability. Reduced flaps (20°) trade landing distance for better aileron authority and crisper control response. At KBKV, with 7,001 feet of runway on Runway 09, the extra landing distance is acceptable. The better control authority in a crosswind is worth the trade.
The go-around decision must be made early — on base leg or short final, not during the flare or rollout.
Once you are below 100 ft AGL in a marginal crosswind, your options are limited. If the wind is too strong, the approach is unstable, or you are carrying excess energy, the go-around decision must be made on base leg or short final, when you have altitude and airspeed to climb away safely. The NTSB data show that pilots who delay the go-around decision and try to salvage a marginal approach often end up off the runway. Recognize the problem early and act.
A bounced landing in a crosswind is a setup for loss of directional control and runway excursion.
If the Archer bounces on touchdown (due to excess airspeed or a hard landing), the airplane is airborne again at low altitude with reduced control authority. A gust during the bounce can cause a loss of directional control. The correct response to a bounced landing is either a smooth recovery and second landing, or a go-around. Do not try to salvage a bounced landing in a crosswind by fighting the airplane — go around and reset.
Directional control during rollout is critical — apply brakes early to slow the airplane and regain control.
During rollout in a crosswind, the wind gusts are most effective at high speed. As the airplane slows, the wind gusts become less effective and rudder authority becomes more effective. If you are drifting or fighting the wind during rollout, apply brakes early to slow the airplane and regain directional control. At 30 KIAS, you have full directional control and the wind is no longer a threat.
Built from the real accident record
Scenario built from NTSB ERA10CA473 (2010 PA-28-181 crosswind stall/hard landing), LAX08CA199 (2008 PA-28-181 bounced landing/loss of control), CHI05CA208 (2005 PA-28-181 runway overrun/excessive airspeed), LAX04CA289 (2004 PA-28-181 hard landing/directional control loss), ERA10FA020 (2009 PA-28-181 wet runway loss of control, fatal), CEN23LA345 (2023 PA-28 fuel exhaustion/landing overrun), and regional crosswind-loss-of-control precedents GAA17CA105, ERA21LA119, GAA19CA170, ERA10CA448. Localized to KBKV.
NTSB reports: ERA10CA473 · LAX08CA199 · CHI05CA208 · LAX04CA289 · ERA10FA020 · CEN23LA345 · GAA17CA105 · ERA21LA119 · GAA19CA170 · ERA10CA448
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.III.A — Preflight Preparation · PA.III.B — Preflight Procedures · PA.IV.J — Approach and Landing · PA.IV.K — Go-Around / Rejected Landing · PA.I.H — Human Factors
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 Archer scenarios · More scenarios at KBKV