FlightEdge
Sample scenario-based training
SAMPLE SBTLanding / Approach

Gusty Crosswind at Venice

A C172R on landing approach encounters wind gusts that challenge directional control — the decision to go around or land comes down to airspeed, crosswind technique, and recognizing the limits of the airplane and pilot

Cessna 172R · Venice Municipal Airport (KVNC) · Private · Landing / Approach

The scenario

Departing Venice Municipal Airport (KVNC), Venice, FL — Runway 13, a 5,640 ft asphalt runway aligned 135° true. Field elevation 18 ft MSL. You are on a solo instructional flight, practicing crosswind landings and go-arounds in preparation for your commercial rating.

KVNC is non-towered (CTAF 122.8). You are in Class G airspace. The nearest controlled airspace is Sarasota Class C, 20.4 nm to the north. Weather: VFR, wind 160° at 18 gusts 26 knots. That is a 45° crosswind from the right, roughly 12–14 knots of crosswind component on Runway 13. The maximum demonstrated crosswind for the C172R is 15 knots. You are at the edge of the envelope — not beyond it, but close.

You are on a 3 nm final approach to Runway 13, descending through 500 ft AGL at 65 KIAS (best glide / approach speed). The runway is in sight. The wind is gusty; you can see the windsock dancing. Your CFI is on the ground, observing. You have made three landings already this morning — all acceptable, but none in wind this strong. This will be your fourth.

Aircraft: Cessna 172R, solo, within weight and balance limits, full fuel. Fuel-injected Lycoming IO-360-L2A, fixed-pitch prop, fixed gear, steam panel. You have 1,200 hours total time, 180 hours in type. You are a competent pilot, but crosswind landings in gusts above 20 knots are not routine for you.

As you descend through 300 ft AGL on final, a gust hits from the right. The airplane drifts left. You correct with right aileron and right rudder. The descent is stable. You are committed to the landing.

The decision

Before we enter the decision tree — what do you know about crosswind landings in the C172R? (Pick all that apply; this records your baseline.)

What the record shows

What the NTSB files show

NTSB WPR11FA242 (2011, fatal): A Cessna 172R on a solo instructional flight at Wendover Airport, Nevada, executed a go-around from a landing attempt. During the downwind turn of the go-around, the pilot failed to maintain adequate airspeed. The airplane stalled and entered an unrecoverable spin. Contributing factors included inadequate preflight planning and an out-of-limits weight and balance envelope. The pilot did not survive. The probable cause was the pilot's failure to maintain adequate airspeed during the downwind turn, resulting in an aerodynamic stall and loss of control.

NTSB ERA23LA339 (2023): A Cessna 172R on a solo instructional flight encountered an unexpected wind gust during a soft-field takeoff. The pilot did not adequately compensate for the prevailing wind conditions. The airplane lost directional control and collided with trees. The probable cause was the pilot's inadequate compensation for the prevailing wind conditions during takeoff, resulting in loss of control.

NTSB CEN22LA014 (2021): A Cessna 172R on a personal flight encountered gusting winds during landing approach. The pilot failed to maintain control in the gusting wind conditions, resulting in a hard, bounced landing. The nose landing gear collapsed. The probable cause was the pilot's failure to maintain control of the airplane while landing in gusting wind conditions.

NTSB NYC05FA075 (2005, fatal): A Cessna 172R on an IFR training flight from Albany to Westchester County Airport descended below the decision height of 200 feet AGL during an ILS approach in low visibility, fog, and gusty winds. The airplane struck trees. The probable cause was the flight instructor's failure to maintain proper altitude clearance during the approach. Contributing factors included low ceilings, fog, and gusty wind conditions.

The consistent thread across all these events: crosswind and gust-related accidents in the C172R occur when pilots either (1) fail to recognize the limits of the demonstrated crosswind (15 knots), (2) fail to maintain adequate airspeed during a go-around or maneuver in gusty conditions, or (3) attempt to land in conditions that are unstable and then fail to go around when the approach deteriorates. The real accidents cited above occurred at other airports — NOT at Venice Municipal. KVNC has its own dominant accident pattern (loss of control inflight, forced landing, spatial disorientation, hard landing, loss of control ground — 24.4%, 12.2%, 12.2%, 12.2%, 12.2% respectively). The scenario is localized to KVNC to make the crosswind challenge real and consequential for you as a student here.

The key lesson: recognize when an approach is unstable (loss of directional control, excessive drift, bouncing, increasing workload) and commit to a go-around before the situation becomes unrecoverable. A go-around from 300 ft AGL is safe; a go-around from 20 ft AGL is marginal. A hard landing is survivable; a stall/spin at low altitude is not.

Key lesson — In gusty crosswind conditions at or near the demonstrated crosswind limit (15 knots for the C172R), maintain a low-workload approach technique (crab or slip, consistently applied), monitor airspeed (65 KIAS on final), and commit to a go-around if the approach becomes unstable. An unstable approach at low altitude — characterized by loss of directional control, excessive drift, or increasing control inputs — is a setup for a hard landing or loss of control. Go around early, while you have altitude and time.

Debrief — teaching points

The maximum demonstrated crosswind for the C172R is 15 knots — beyond that, control authority is not guaranteed.

The C172R POH specifies a maximum demonstrated crosswind of 15 knots. At KVNC with a wind of 160° at 18 gusts 26 knots, the crosswind component on Runway 13 (135° true) is roughly 12–14 knots — at the edge of the envelope. The gust factor (26 – 18 = 8 knots) means the wind can vary from 10 to 26 knots. When the gust peaks at 26 knots, the crosswind component approaches or exceeds 15 knots. You are operating at the demonstrated limit. Recognize this before you commit to the approach.

An unstable approach at low altitude is a setup for a hard landing or loss of control.

An unstable approach is characterized by loss of directional control, excessive drift, bouncing, or increasing control inputs. If you are fighting the airplane to keep it aligned with the runway, the approach is unstable. At 300 ft AGL, you have time and altitude to go around safely. At 150 ft AGL, a go-around is still safe. At 50 ft AGL, a go-around is marginal. At 20 ft AGL, a go-around is a last resort. Commit to the go-around early, while you have options.

Crosswind technique: crab or slip, applied consistently from the beginning of the approach.

Two valid techniques exist: (1) crabbed approach (nose into the wind, fuselage aligned with runway), then transition to a slip at low altitude to align the fuselage for touchdown; (2) slip from the beginning (wing low into the wind, opposite rudder). Either technique is valid. The key is consistency — choose one and apply it throughout the approach. Mixing techniques or switching mid-approach increases workload and reduces control authority. A forward slip (wing low into the wind) is particularly effective in gusty conditions because it increases descent rate and reduces the time in the gusty lower altitude.

During a go-around from low altitude, maintain Vy (79 KIAS) and avoid a steep turn that could result in a stall.

NTSB WPR11FA242 is a fatal reminder: during a go-around from a landing attempt, the pilot failed to maintain adequate airspeed during the downwind turn and stalled. The C172R's stall speed in landing configuration (flaps extended) is 33 KIAS; Vy is 79 KIAS. A go-around requires a positive rate of climb and adequate airspeed. Retract flaps to 10° immediately, push the throttle to full power, and establish a climb at Vy. Avoid a steep turn that could bleed airspeed. If you are at 20 ft AGL and need to go around, you have seconds to establish a positive rate of climb before the terrain becomes a factor. This is why early go-around decisions are critical.

Proper trim before the approach reduces workload and improves control authority.

A properly trimmed airplane requires less control input to maintain a stable descent. In gusty conditions, a poorly trimmed airplane is harder to control — you are fighting the trim as well as the wind. Before you begin the descent on final, trim the airplane for 65 KIAS descent. This reduces workload and leaves you more control authority to handle gusts. In the C172R, trim is a wheel on the control column; adjust it smoothly and confirm the airplane is trimmed before you descend.

A crabbed touchdown (nose pointed into the wind while the fuselage is drifting) results in side loads on the landing gear and a hard landing.

If you touch down in a crab — nose pointed right while the fuselage is drifting left — the right main gear touches first and bears the side load. The airplane bounces. The nose gear then touches hard. This is a setup for nose gear collapse (NTSB CEN22LA014). Always transition from a crab to a slip before touchdown — lower the upwind wing and apply opposite rudder to align the fuselage with the runway. This ensures the nose gear and main gears touch down aligned with the runway, minimizing side loads.

Built from the real accident record

Scenario built from NTSB WPR11FA242 (2011 C172R stall during go-around), NYC05FA075 (2005 C172R loss of control in low-visibility approach), ERA23LA339 (2023 C172R loss of control in wind gust during takeoff), and CEN22LA014 (2021 C172R hard landing in gusting winds). Regional precedents CHI91DCJ01, ANC93LA040, FTW89FA151 inform the spatial-disorientation and decision-making teaching angles. Anonymized and localized to KVNC.

NTSB reports: WPR11FA242 · NYC05FA075 · ERA23LA339 · CEN22LA014 · CHI91DCJ01 · ANC93LA040 · FTW89FA151

ACS tasks: PA.I.F — Weather Information · PA.II.D — Takeoff and Departure · PA.II.E — Inflight Maneuvers · PA.III.A — Normal Approach and Landing · PA.III.B — Forward Slip to a Landing · PA.III.C — Go-Around / Rejected Landing · PA.I.H — Human Factors

Relevant FARs: §91.3 · §91.13 · §91.103

Run this scenario yourself

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 Cessna 172R scenarios · More scenarios at KVNC