Gusting Crosswind at Lakeland
A Piper Archer on short final in gusty conditions — recognizing when the wind has won, and committing to the go-around before directional control is lost
The scenario
Departing Lakeland Linder International Airport (KLAL), Lakeland, FL — Runway 10, a 8,500 ft east-west runway. Elevation 142 ft MSL. You are a Private pilot with roughly 180 hours total, 40 hours in the Piper Archer. This is a local VFR flight — a 1-hour round trip to a nearby practice area and back.
Current conditions: winds 120° at 18 gusts 28 knots. Runway 10 is oriented 090° (true). The crosswind component is roughly 15–22 knots — right on the edge of the Archer's demonstrated crosswind capability (15 knots). The gusts are pushing you over. Visibility 10 SM, scattered clouds at 3,500 ft, surface temperature 24°C. KLAL tower is active 24 hours; you are in Class D airspace (ceiling 2,600 MSL).
You are returning from the practice area after 45 minutes of work. Fuel: 28 gallons remaining (roughly 4.5 hours endurance at cruise). The Archer is within weight and balance limits. You have been monitoring the wind on the ground and in the air — it has been steady but gusty all morning. You are familiar with KLAL; you have landed here 15 times.
You are on a 5-mile final for Runway 10, 1,200 ft AGL, descending at 500 fpm. Airspeed is 90 KIAS (you are carrying extra speed to maintain control in the wind). Flaps are at 10°. The tower has cleared you to land. The runway is in sight. The wind is gusting noticeably — you can see the windsock snapping.
Aircraft: Piper PA-28-181 Archer, fixed gear, fixed-pitch prop, carbureted Lycoming O-360-A, 180 hp. Fuel selector is on LEFT tank (you switched from RIGHT 10 minutes ago, confirming fuel flow). Steam gauges, vacuum system, standard six-pack. No glass, no autopilot.
Pilot: you — Private, current, 180 hours total, 40 hours in type. You have landed in crosswinds before, but nothing quite this gusty. Your personal minimums are 12 knots demonstrated crosswind. This is 15–22 knots gusting. You are at the edge of your comfort zone — and the gusts are pushing you over it.
- {'label': 'Field', 'value': 'KLAL · Lakeland Linder'}
- {'label': 'Runways', 'value': '5/23 · 10/28'}
- {'label': 'Elevation', 'value': '142 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? (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 failure to maintain directional control.
NTSB CHI05CA208 (2005): A Piper PA-28-181 overran a grass runway and struck a utility pole during landing. The probable cause was 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 and failure to maintain directional control during rollout.
NTSB ERA10FA020 (2009, FATAL): A Piper PA-28-181 landed fast and hard on a wet turf runway, lost directional control during rollout, and collided with trees. The probable cause was loss of directional control while landing on a wet runway.
NTSB GAA17CA105 (2016): A Piper PA-46 lost directional control during landing rollout in gusting crosswind conditions that exceeded the aircraft's demonstrated crosswind capability. The probable cause was the pilot's loss of directional control in gusting crosswind conditions.
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 consistent thread: Piper Archer and comparable aircraft accidents in crosswind conditions follow a predictable pattern. The pilot recognizes the wind is gusty but continues the approach. The workload increases. The approach becomes unstable. The pilot does not commit to a go-around early. At touchdown or during rollout, directional control is lost. The airplane veers off the runway. The outcome is a runway excursion, impact with obstacles, and structural damage. The critical decision point is always the same: recognizing when the crosswind conditions exceed demonstrated capability and committing to a go-around or diversion BEFORE the approach becomes unstable.
At Lakeland Linder International (KLAL), Runway 10 is oriented 090° (true). The off-field environment to the left (270°) is low-density development, open developed areas, and dense development — buildings, trees, obstacles. A runway excursion to the left ends in impact with structures. The real accidents cited above occurred at other airports — NOT at KLAL. This scenario is localized to KLAL to make the off-field environment real and consequential for you as a student here.
The Piper Archer's demonstrated crosswind capability is 15 knots. The wind in this scenario was 120° at 18 G28 knots — a crosswind component of 15–22 knots gusting. The pilot's personal minimums were 12 knots. The wind exceeded both. The correct decision was a go-around or diversion at the first sign that the approach was unstable — or even earlier, before descending below 1,500 ft AGL.
Key lesson — The Piper Archer's demonstrated crosswind capability is 15 knots. Gusts that push the sustained crosswind above that are a warning sign. Recognize when crosswind conditions exceed your personal minimums and commit to a go-around or diversion BEFORE the approach becomes unstable. An unstable approach in a crosswind is a go-around — not a landing. The decision to continue or go around must be made early, with plenty of altitude and options. At 5 miles final, you still have time. At 1 mile final, you are committed. At 300 ft AGL in the flare, it is too late.
Debrief — teaching points
The Piper Archer's demonstrated crosswind capability is 15 knots — know this number.
The Archer's POH specifies a demonstrated crosswind capability of 15 knots. This is not a suggestion; it is a limit based on testing. Gusts that push the sustained crosswind above 15 knots are beyond the airplane's demonstrated capability. In this scenario, the wind was 120° at 18 G28 knots — a crosswind component of 15–22 knots gusting. The gusts exceeded the limit. The correct response is recognition and a go-around or diversion, not an attempt to manage it.
Personal minimums are lower than demonstrated limits — set them and stick to them.
The pilot in this scenario had personal minimums of 12 knots crosswind. The demonstrated limit is 15 knots. Personal minimums exist because not every pilot is equally skilled in crosswind landings, and because demonstrated limits assume ideal technique and aircraft condition. The wind in this scenario exceeded the pilot's personal minimums. The correct decision was a go-around or diversion, not an attempt to land.
An unstable approach is a go-around — commit early, with altitude and options.
An unstable approach is defined by high workload, inability to maintain the desired descent profile, and loss of control authority. In this scenario, the approach became unstable at 2 miles final — the pilot was hand-flying the crab constantly, workload was high, and the airplane was drifting left and right with each gust. The correct decision was a go-around at that point, with 800 ft AGL and plenty of runway ahead. Instead, the pilot continued, and the situation deteriorated. The decision to go around must be made early, before altitude and options are exhausted.
A bounced landing in a crosswind is dangerous — go around, do not recover.
When an airplane bounces on landing in a crosswind, the recovery is unstable. The airplane is at low airspeed (50–60 KIAS), low altitude (50 ft AGL), and the wind is still gusting. Attempting to recover from the bounce and land again risks directional control loss during rollout. The correct decision is to go around from the bounce — advance power, pitch up to Vy (76 KIAS), and climb out. A go-around from a bounced landing is always the correct call.
Carrying extra airspeed in a crosswind increases float and landing distance.
In this scenario, the pilot was carrying 90 KIAS on final (Vref is 66 KIAS) to maintain control in the wind. Extra airspeed does help with control authority, but it increases float — the airplane does not touch down as soon, and landing distance increases. In a crosswind, the trade-off is real: extra speed for control authority, but longer landing distance and more float. Know the trade-off and plan accordingly.
Off Runway 10 at KLAL, the left edge is low-density development with obstacles — a runway excursion is impact.
The off-field environment to the left of Runway 10 (heading 270°) is low-density development, open developed areas, and dense development — buildings, trees, obstacles. A runway excursion to the left ends in impact with structures. This is not an open field or a grass area; it is an urban environment. A loss of directional control during rollout is a serious accident, not a recoverable event.
Diversion is not failure — it is airmanship.
When crosswind conditions exceed demonstrated capability or personal minimums, the correct decision is a go-around or diversion. Diversion to an airport with a more favorable runway orientation or calmer conditions is a sound, conservative, and correct decision. It is not a failure; it is airmanship. The wind at KLAL was not changing. Holding and trying again was burning fuel without solving the problem. Diversion was the correct call.
Built from the real accident record
Scenario built from NTSB ERA10CA473, LAX08CA199, CHI05CA208, LAX04CA289, ERA10FA020 (Piper PA-28-181 landing accidents involving crosswind loss of control, bounced landings, and runway excursions), and regional precedents GAA17CA105, ERA21LA119, GAA19CA170, ERA10CA448 (crosswind-related directional control loss across aircraft types). Real events occurred at other airports — NOT at Lakeland Linder International (KLAL).
NTSB reports: ERA10CA473 · LAX08CA199 · CHI05CA208 · LAX04CA289 · ERA10FA020 · CEN23LA345 · GAA17CA105 · ERA21LA119 · GAA19CA170 · ERA10CA448
ACS tasks: PA.I.F — Weather Information · PA.III.C — Crosswind Takeoff and Landing · PA.III.D — Soft-Field Takeoff and Landing · PA.III.E — Forward Slip to a Landing · PA.V.A — Approach and Landing · PA.I.H — Human Factors
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 KLAL