Crosswind Surprise at Lakeland
A gusting crosswind during landing flare tests directional control in the Piper Arrow — and your decision to go around or commit
The scenario
Departing Lakeland Linder International Airport (KLAL), Lakeland, FL — Runway 10, a 8,500 ft concrete strip. Elevation 142 ft MSL. You are a commercial pilot with roughly 800 hours total, 200 hours in the Piper Arrow (PA-28R). This is a local instructional flight with a student pilot in the right seat — your job is to demonstrate a crosswind landing and then let the student fly the approach and landing on the return.
It is a warm, humid Florida afternoon in late spring. Surface wind is reported as 120° at 12 knots, gusting to 18 knots. Runway 10 is aligned 090° true (magnetic 090°). The crosswind component is roughly 10–12 knots steady, with gusts pushing 15–16 knots — right at or slightly above the Piper Arrow's demonstrated crosswind capability of 15 knots. The tower has issued a crosswind landing advisory. Visibility is 10 SM, scattered clouds at 3,500 ft. Class D airspace, ceiling 2,600 ft MSL.
You have completed a normal approach to Runway 10 at 79 KIAS best glide speed (gear down, prop full forward, flaps 20°). The runway is made. You are on short final, 200 ft AGL, lined up on the runway centerline with a 10° crab angle to the left to compensate for the crosswind. The tower clears you to land.
Aircraft: Piper Arrow PA-28R, full fuel, within limits. Lycoming IO-360 fuel-injected, constant-speed prop, retractable gear. Landing gear is down and locked. Flaps are at 20°. You are configured for landing.
Pilot: You — a commercial pilot, current, 800 hours total, 200 hours in type. You have crosswind experience but have not landed in conditions this gusty in the Arrow. Your personal minimums are 12 knots demonstrated crosswind; the current conditions are at the edge of that envelope. The student is watching and expecting to learn.
- {'label': 'Field', 'value': 'KLAL · Lakeland Linder'}
- {'label': 'Runways', 'value': '5/23 · 10/28'}
- {'label': 'Elevation', 'value': '142 ft'}
- {'label': 'Aircraft', 'value': 'PA-28R'}
- {'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 Arrow? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB CEN12LA189 (2012): A Piper PA-28R-200 on an instructional flight drifted off the runway during landing flare in a crosswind gust. The student pilot did not relinquish controls and the flight instructor delayed remedial action. The airplane struck a ditch and was substantially damaged. The probable cause was the student pilot's failure to maintain adequate crosswind correction during the landing flare and the flight instructor's delayed remedial action.
NTSB CEN10CA318 (2010): A Piper PA-28R-200 encountered a downdraft during final approach to a wet grass strip and drifted left during landing rollout. The left main landing gear struck concrete driveways and separated. The probable cause was the pilot's failure to maintain directional control during the landing roll. The airplane was substantially damaged.
NTSB CHI08LA137 (2008): A Piper PA-28R-180 lost control during takeoff when a wind gust forced the nose up. The pilot's corrective input resulted in impact with bushes alongside the runway. The probable cause was the pilot's failure to maintain control during takeoff, with contributing factors including gusty wind conditions.
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 lost directional control during the aborted landing in gusting crosswind conditions. The lesson: recognize when crosswind conditions exceed aircraft limits and commit to go-around early rather than fighting uncontrollable drift during rollout.
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 lesson: understand that technique adjustments (reduced flaps, extra airspeed) have limits; recognize when wind conditions exceed personal minimums and when to divert or go-around.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Lakeland Linder International Airport. KLAL has its own accident history (see field dominant patterns: 19.4% LOSS_OF_CONTROL_GROUND), but these specific events happened elsewhere. The scenario is localized to KLAL to make the crosswind challenge real and consequential for you as a pilot here.
The consistent thread across all these events: crosswind loss of control happens in the flare and landing roll, not on approach. The pilot recognizes the drift too late, tries to correct with rudder alone (creating a skid), or levels the wings early to reduce landing impact (removing the slip correction). By the time the pilot realizes the airplane is not under control, it is too low to recover. The fix — early recognition of drift, immediate slip correction, and commitment to a go-around if control is marginal — is simple. The failure is always a delay or a commitment to land when the conditions exceed the pilot's ability to maintain control.
At Lakeland Linder International, the off-field environment off Runway 10's departure end (heading 090°) is marginal: low-density development, open developed areas (parks/large lots), and dense development. A loss of directional control during takeoff could result in impact with structures or terrain. The off-field environment off Runway 10's arrival end is also marginal. The runway is 8,500 ft long — plenty of runway for a crosswind landing if directional control is maintained. But if the airplane drifts off the runway, the consequences are real.
Key lesson — In the Piper Arrow, crosswind loss of control happens in the flare and landing roll. The demonstrated crosswind capability is 15 knots — that is the limit of what the airplane has been tested to handle. When gusts push the crosswind component above that limit, or when your personal minimums are exceeded, the correct response is a go-around, not a commitment to land. If you do land in a crosswind, maintain the forward slip (wing low into the wind, opposite rudder) all the way to touchdown. Do not level the wings early to reduce landing impact — the slip is your only tool for maintaining directional control. If the airplane begins to drift or the wing begins to lift, apply slip correction immediately. If control is lost, the airplane will ground loop, and the retractable gear is not designed for the side loads of a ground loop.
Debrief — teaching points
The Piper Arrow's demonstrated crosswind capability is 15 knots — that is the limit.
The POH states that the Piper Arrow has been demonstrated to handle a 15-knot crosswind. That is the maximum crosswind component the airplane has been tested to handle. When the tower reports wind gusting to 18 knots from 120° on a 090° runway, the peak crosswind component can exceed 15 knots. Gusts add 3–5 knots to the steady-state crosswind component. If your personal minimums are 12 knots (a common conservative limit), and the conditions are gusting to 15–16 knots, you are exceeding your minimums. The correct response is a go-around or a diversion to a runway with a more favorable wind direction.
Crosswind loss of control happens in the flare and landing roll, not on approach.
The NTSB data on crosswind accidents shows a consistent pattern: the pilot flies a stable approach, but in the flare or landing roll, a gust lifts the wing. The pilot tries to correct with rudder alone (creating a skid), or levels the wings early to reduce landing impact (removing the slip correction). By the time the pilot realizes the airplane is not under control, it is too low to recover. The solution: recognize the drift early, enter a forward slip (wing low into the wind, opposite rudder), and maintain the slip all the way to touchdown. Do not level the wings until the airplane is on the ground and slowing.
A forward slip is the correct crosswind landing technique — not a crab angle.
On approach, a crab angle (nose pointed into the wind) is used to track the runway. But in the flare and landing roll, the crab must be converted to a slip (wing low into the wind, opposite rudder). The slip corrects for the crosswind while keeping the fuselage aligned with the runway. A crab angle during landing will result in a side load on the landing gear when the airplane touches down. A slip distributes the side load more evenly and keeps the airplane aligned with the runway. Practice the slip technique in calm conditions before attempting it in gusty crosswinds.
Do not level the wings early to reduce landing impact.
In a crosswind, the temptation is to level the wings before touchdown to reduce the landing impact. This removes your only tool for maintaining directional control — the slip. The moment you level the wings, the crosswind reasserts itself and the airplane drifts. If you are at 30 ft AGL or lower when you level the wings, you are too low to recover with another slip. Maintain the slip all the way to touchdown. The landing will be firm, but the airplane will remain under control. A firm landing is better than a ground loop.
If directional control is marginal, go around — do not commit to land.
The NTSB data on crosswind accidents shows that pilots who commit to landing in marginal conditions lose directional control. Pilots who go around live to fly another day. If you are in the flare and the airplane is drifting, or the wing is lifting, and you are not confident you can maintain directional control with a slip, apply full power, retract flaps, raise gear, and go around. A go-around from 150 ft AGL is safe and well within the Piper Arrow's performance. A ground loop at 20 ft AGL is not.
The Piper Arrow's retractable gear is not designed for the side loads of a ground loop.
If the airplane ground loops, the retractable gear struts are not designed to handle the side loads. The left main gear strut could collapse, or the gear could separate. The airplane will come to rest off the runway, damaged. A ground loop is not just a loss of directional control — it is structural damage to the airplane. Maintain directional control all the way to a complete stop. If the airplane begins to drift or the wing begins to lift, apply slip correction immediately.
At KLAL, the off-field environment off Runway 10 is marginal — recognize the consequences.
The off-field environment off Runway 10's departure end (heading 090°) is marginal: low-density development, open developed areas (parks/large lots), and dense development. A loss of directional control during takeoff could result in impact with structures or terrain. The off-field environment off Runway 10's arrival end is also marginal. The runway is 8,500 ft long — plenty of runway for a crosswind landing if directional control is maintained. But if the airplane drifts off the runway, the consequences are real. Recognize the geography and the stakes.
Built from the real accident record
Scenario built from NTSB CEN12LA189 (2012 PA-28R-200 crosswind loss of control during landing flare), CEN10CA318 (2010 PA-28R-200 directional control failure during rollout), CHI08LA137 (2008 PA-28R-180 loss of control during takeoff in gusty wind), and regional precedents GAA17CA105, ERA21LA119, GAA19CA170 (all crosswind/directional control events). Anonymized and localized to KLAL.
NTSB reports: CEN12LA189 · WPR11CA107 · CEN10CA318 · CHI08LA137 · GAA17CA105 · ERA21LA119 · GAA19CA170
ACS tasks: PA.VII.A — Preflight Inspection · PA.VII.B — Powerplant and Systems Management · PA.VIII.A — Takeoff and Climb · PA.VIII.B — Approach and Landing · PA.I.H — Human Factors · PA.IX.C — Emergency Approach and Landing
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 Arrow scenarios · More scenarios at KLAL