Float and Overshoot at Venice
Excess approach energy, a short runway, and the decision to go around — a C172R runway-excursion scenario
The scenario
Departing Venice Municipal Airport (KVNC), Venice, FL — Runway 22, a 5,000 ft asphalt runway. Elevation 18 ft MSL. You are inbound on a solo cross-country flight, VFR, and have requested a full-stop landing.
It is a breezy afternoon in late spring: OAT 26°C, wind from 240° at 12 gusting to 18 knots. Runway 22's magnetic heading is 225° (true 225°), so the wind is roughly 15° off the nose with a slight right crosswind component. Visibility 10 SM, scattered clouds at 3,500 ft. KVNC is non-towered (Class G); you are on CTAF 122.775 MHz. No other traffic reported.
You are on a 3° glide slope to Runway 22, 500 ft AGL, descending at 65 KIAS (best glide / approach speed). You have full flaps (30°) extended; the flap limit at this speed is 85 KIAS for full flaps, so you are within limits. The runway is made; it looks long and stable. You are planning a normal landing.
Aircraft: Cessna 172R, solo, 1,950 lb (well within limits), fuel 30 gal usable remaining. Fuel-injected Lycoming IO-360-L2A, 160 hp. Fixed gear, fixed-pitch prop, steam panel (vacuum-driven instruments). You are current and have 180 hours total time, with 45 hours in the C172R.
Pilot: You — a Private pilot, current, 180 hours total. This is your third solo cross-country. You have practiced power-off 180° approaches in training but have not flown one in actual wind. You are focused on the landing and have not briefed an alternate plan if the approach becomes unstable.
- {'label': 'Field', 'value': 'KVNC · Venice'}
- {'label': 'Runways', 'value': '4/22 · 13/31'}
- {'label': 'Elevation', 'value': '18 ft'}
- {'label': 'Aircraft', 'value': 'C172R'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before the decision tree — what do you know about go-around decisions and runway excursion prevention in the C172R? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB CEN24LA263 (2024): A Cessna 172R performing a power-off 180° maneuver landed too high on the runway and was unable to stop within the remaining distance. The aircraft overran the runway end, breached the perimeter fence, and came to rest upright. The probable cause was the pilot's decision to continue the landing attempt with insufficient runway remaining.
NTSB CEN24LA233 (2024): A Cessna 172R on an instructional flight veered left of the runway centerline during landing; the pilot's correction attempts resulted in a right veer, causing the aircraft to exit the left side of the runway and strike a distance marker. The accident was attributed to the pilot's failure to maintain directional control during landing.
NTSB ERA22LA280 (2022): A Cessna 172 flown by a student pilot during touch-and-go landings experienced a porpoising landing after an improper flare. The student's attempt to recover by pulling back caused a skid, and subsequent overcompensation with rudder input resulted in a runway excursion and collision with a taxiway sign.
NTSB ERA21LA249 (2021): A Cessna 172R on a solo cross-country instructional flight experienced loss of directional control during landing when the nose gear contacted the runway. The accident resulted from the student pilot's failure to maintain directional control, resulting in a runway excursion and collision with an airport sign.
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 real accidents cited above occurred at other airports — NOT at Venice Municipal Airport (KVNC). KVNC has its own accident history dominated by loss-of-control inflight (24.4%), forced landing (12.2%), spatial disorientation (12.2%), hard landing (12.2%), and loss-of-control ground (12.2%). The runway-excursion scenario is localized to KVNC to make the runway geometry and off-field environment real for you as a student here.
The consistent thread across all these events: a floating or unstable approach, combined with a pilot's reluctance to go around, results in a long landing with excess energy. Loss of directional control during the rollout — especially in gusting crosswind conditions — then leads to a runway excursion. The C172R's fixed gear and fixed-pitch prop mean you have no gear-extension or prop-pitch tools to increase drag; your only tools are flaps (already extended), aerodynamic drag, and wheel brakes. Directional control on landing is maintained by active rudder input and a willingness to abort the landing if the approach becomes unstable.
Key lesson — At KVNC Runway 22 (5,000 ft), a long landing (landing at 40% or more of the runway) combined with gusting crosswind conditions (240° at 12G18 knots) leaves minimal margin for directional control errors. The decision to go around — made early, when the approach is unstable or the float is obvious — is always the correct decision. A go-around is not a failure; it is airmanship. Once committed to a landing, maintain directional control with active rudder input, use aerodynamic drag and light braking to slow, and be prepared to release brakes if directional control is lost. The C172R's Lycoming IO-360 fuel-injected engine and steam-panel vacuum system are reliable, but the landing is where the pilot's decision-making matters most.
Debrief — teaching points
A floating approach is a sign of excess energy — go around if the float is obvious.
In the C172R, a power-off approach should descend at a steady 3° glide slope. If the descent rate shallows and the airplane floats above the glide slope, the approach has excess energy. This excess energy will result in a long landing. At 300 ft AGL, if the float is obvious, a go-around is the correct decision. At 200 ft AGL, a go-around is still the correct decision. At 100 ft AGL, a go-around is marginal but still possible. Waiting until 50 ft AGL to decide the approach is unstable leaves no room for error. Early recognition and early action are the keys to preventing a runway excursion.
An improper flare can worsen a float — aggressive back pressure can cause the airplane to balloon.
A common error in landing is to flare too aggressively or too early. In the C172R, a normal flare begins at 50 ft AGL with gentle back pressure to reduce the descent rate. If you flare too early (at 100 ft AGL) or too aggressively, the airplane can balloon (climb) instead of settle. This worsens the float and results in an even longer landing. A proper flare is gentle and late — not aggressive and early. Practice the flare in training with your CFI; it is a skill that requires precision.
Gusting crosswind conditions reduce directional control authority — especially during braking.
At KVNC Runway 22, the wind is 240° at 12G18 knots — a slight right crosswind with gusts. During the landing rollout, a gust from the right can push the airplane left of centerline. If you are applying aggressive wheel brakes at the same time, your directional control authority is reduced because the brakes are slowing the airplane and reducing the effectiveness of the rudder. The solution is to use light braking and active rudder input to maintain centerline. If the airplane begins to drift off centerline, reduce braking pressure and increase rudder input to regain control.
The C172R has no constant-speed prop or retractable gear — your only drag tools are flaps and aerodynamic drag.
The C172R has a fixed-pitch prop and fixed gear. Unlike higher-performance airplanes, you cannot extend the gear or increase prop pitch to increase drag. Your only tools for slowing the airplane are full flaps (already extended on landing), aerodynamic drag (back pressure on the yoke), and wheel brakes. This means you must plan the landing to arrive at the runway with minimal excess energy. A long landing (landing at 40% or more of the runway) leaves minimal margin for error. Land short and use the full runway length to stop — do not land long and hope to stop in time.
A go-around is always an option — it is not a failure, it is airmanship.
Many pilots feel pressure to 'make' the landing, especially on a solo cross-country flight. This pressure can lead to poor decisions: continuing an unstable approach, landing long, and then losing directional control during the rollout. The correct decision is to go around if the approach is unstable or the landing is not assured. A go-around costs a few minutes and a small amount of fuel. A runway excursion costs damage to the airplane and a potential accident. The go-around is always the correct decision when the approach is unstable.
Built from the real accident record
Scenario built from NTSB CEN24LA263 (2024 C172R power-off 180 overshoot), CEN24LA233 (2024 C172R directional control loss on landing), ERA22LA280 (2022 C172R porpoising/excursion), ERA21LA249 (2021 C172R solo cross-country directional loss), and ERA21LA119 (2021 C172R gusting crosswind excursion). Localized to KVNC.
NTSB reports: CEN24LA263 · CEN24LA233 · ERA22LA280 · ERA21LA249 · ERA21LA119
ACS tasks: PA.II.J — Approach and Landing · PA.II.K — Go-Around / Rejected Landing · PA.I.F — Weather Information · 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 Cessna 172R scenarios · More scenarios at KVNC