Float and Overshoot at Venice
A Cessna 182's excess approach energy, a bounced landing, and the decision to go around — or not
The scenario
Departing Venice Municipal Airport (KVNC), Venice, FL — Runway 22, a 5,000-foot asphalt surface. Elevation 18 ft MSL. You are on a personal VFR flight in a Cessna 182 Skylane, a high-performance single with a constant-speed prop and cowl flaps. You have a high-performance endorsement and roughly 400 hours total time, with 80 hours in type. This is your second visit to KVNC; you are not intimately familiar with the field.
It is a warm, humid Florida afternoon in late May: OAT 32°C, dew point 24°C, altimeter 29.89. Scattered clouds at 3,500 ft, visibility 10 SM. The wind is light and variable — roughly 3–5 knots from the northeast. Density altitude is approximately 2,200 ft above field elevation — the runway will perform as if it were 2,200 ft higher. A 5,000-foot runway at sea level is plenty; at a density altitude of 2,200 ft, it is tighter.
You are on a 15-mile straight-in approach to Runway 22 (true heading 225°). You are at 1,500 ft MSL, 8 miles out, descending at a comfortable rate. The runway is in sight. You have already reduced power, extended the flaps to 10°, and trimmed for the descent. The approach feels stable. You are not rushed.
Aircraft: Cessna 182 Skylane, solo, 2,950 lb gross weight, within limits. Constant-speed prop (you have set it to high RPM for descent), cowl flaps open for cooling. Fuel is full. Nothing was written up; the airplane is airworthy.
Pilot: you — a Commercial pilot, current, high-performance endorsed, 400 hours total, 80 hours in the C182. You have landed at KVNC once before, about a year ago. You are familiar with the C182's heavier, faster handling and its tendency to float on approach if energy is not managed carefully. You are not fatigued, not rushed, and the weather is benign.
- {'label': 'Field', 'value': 'KVNC · Venice'}
- {'label': 'Runways', 'value': '4/22 · 13/31'}
- {'label': 'Elevation', 'value': '18 ft'}
- {'label': 'Aircraft', 'value': 'C182'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we get into the decision tree — what do you know about the Cessna 182's approach and landing characteristics? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB ERA21LA113 (2021): A Cessna 182 on a personal flight experienced a hard landing and runway excursion when the pilot failed to properly recover from a bounced landing. The nose wheel separated and the airplane nosed over. The probable cause was the pilot's improper recovery from the bounced landing. The accident occurred at a different airport, not KVNC.
NTSB WPR20CA269 (2020): A Cessna 182 landed hard more than halfway down the runway, bounced, and the pilot delayed the go-around decision until insufficient runway remained. The aircraft departed the runway and collided with trees. The probable cause was the pilot's decision to continue an unstable approach and delayed go-around. The accident occurred at a different airport, not KVNC.
NTSB CEN21LA055 (2020, fatal): A Cessna 182R on approach to Rockwall Municipal Airport landed on the wrong runway despite radio calls from other pilots. The aircraft overran the runway and struck power lines. The probable cause was the pilot's decision to continue an unstabilized approach and delayed go-around decision. Contributing factors included inaccurate wind direction reporting. The accident occurred at Rockwall Municipal Airport, not KVNC.
NTSB CEN26LA122 (2026): A Cessna 182 on a personal touch-and-go landing touched down with insufficient runway remaining due to an unstabilized approach and excessive speed. The pilot applied maximum braking but the aircraft went through a ditch and struck a fence. The probable cause was the pilot's failure to establish a stabilized approach and failure to execute a go-around. The accident occurred at an unspecified location, not KVNC.
NTSB ERA25LA358 (2025): A Cessna 182 overran the runway after landing more than halfway down a 3,100-foot surface in calm winds. The probable cause was the pilot's failure to obtain the proper touchdown point. The accident occurred at a different airport, not KVNC.
The consistent thread across all these events: the C182 is a heavier, faster, nose-heavy airplane than the 172. It carries more approach energy and floats longer if speed is not managed carefully. A float that seems manageable at 1,000 feet becomes a runway excursion at 2,500 feet. A bounce that seems recoverable becomes a porpoise and a hard landing. The decision to go around is not a failure — it is the correct response to an unstable approach or a bounce. KVNC's runway is 5,000 feet, which is adequate for the C182 under normal conditions. At 2,200 ft density altitude, the effective runway is shorter. A late touchdown at KVNC is still on the runway; at a shorter field, it would be an excursion.
The real accidents cited above occurred at other airports — NOT at Venice Municipal Airport (KVNC). KVNC has its own accident history (see field dominant patterns), but these specific events happened elsewhere. The scenario is localized to KVNC to make the runway length and density altitude real and consequential for you as a student here.
Key lesson — The Cessna 182 is a high-performance airplane with more energy and a higher wing loading than a 172. Approach energy management is critical. A stable approach at Vref (60 KIAS), a normal flare, and an early touchdown (1,000–1,200 ft marker) are the standard. A float is a sign of excess energy — either too much speed on approach or a shallow flare. A bounce is a sign of a hard landing or improper flare technique. If the approach is unstable by 500 ft AGL, or if a bounce occurs, go around. Do not try to salvage a bad landing. At KVNC, with 5,000 feet of runway and 2,200 ft density altitude, a late touchdown is still acceptable — but it is a warning sign. At a shorter field, it would be a runway excursion.
Debrief — teaching points
The C182 is heavier and faster than a 172 — approach energy management is critical.
The Cessna 182 Skylane has a higher wing loading and more mass than a 172. It carries more approach energy and floats longer if speed is not managed carefully. Vref (approach speed) is 60 KIAS on short final. Exceeding this speed guarantees a float. The C182's nose-heavy airframe means a float can quickly become a bounce, and a bounce can become a porpoise. Manage speed early in the approach — reduce power and extend flaps gradually to maintain a stable descent at Vref.
A float is a sign of excess energy — either too much speed or a shallow flare.
If the airplane is floating down the runway instead of settling, the cause is almost always one of two things: (1) the approach speed was too high (above 60 KIAS), or (2) the flare was too shallow (the nose was not raised enough to bleed off airspeed). A float that extends beyond the 1,500-foot marker is using runway you may not have. At KVNC with 5,000 feet of runway and 2,200 ft density altitude, a float is still manageable — but it is a warning sign. At a shorter field, it would be a runway excursion.
A bounce is a sign of a hard landing or improper flare technique — go around.
If the nose wheel bounces (lifts off the pavement after touchdown), the airplane is in a porpoise. The nose-heavy C182 will pitch down hard on the second touchdown, and the bounce can quickly become a hard landing or a loss of directional control. If a bounce occurs, the correct response is to go around immediately — advance the throttle, retract flaps to 10°, and climb away. Do not try to salvage the landing by recovering from the bounce. The go-around is the correct decision.
High density altitude reduces runway performance — a 5,000-foot runway at 2,200 ft DA is tighter than it appears.
Density altitude is the altitude at which the airplane performs as if it were at that height. At KVNC on a warm, humid day, the density altitude can be 2,000–2,500 ft above field elevation. A 5,000-foot runway at sea level is plenty for the C182; at 2,200 ft density altitude, it is tighter. Plan for an early touchdown (1,000–1,200 ft marker) and gentle braking. A late touchdown (2,500+ ft marker) leaves little margin for deceleration.
A stable approach by 500 ft AGL is non-negotiable — if the approach is unstable, go around.
By 500 ft AGL, the approach should be stable: on the glide path, at Vref (60 KIAS), with flaps extended, and descending at a normal rate. If the approach is unstable at 500 ft AGL — too fast, too high, too steep, or too shallow — go around. Do not try to salvage an unstable approach. The go-around is not a failure; it is airmanship. A go-around at 500 ft AGL costs a few minutes and some fuel. A runway excursion costs the airplane and possibly your life.
Constant-speed prop and cowl flaps add workload — manage them early in the descent.
The C182 has a constant-speed prop and cowl flaps, which add workload compared to a 172. Set the prop to high RPM (2,000+ RPM) for descent and approach. Open the cowl flaps to manage engine cooling. These tasks should be completed early in the descent, not during the approach. By the time you are on short final, the airplane should be configured and stable, with your attention free to manage the landing.
Built from the real accident record
Scenario built from NTSB ERA21LA113 (2021 C182 bounced landing / runway excursion), WPR20CA269 (2020 C182 hard landing / delayed go-around), CEN21LA055 (2020 fatal C182 unstabilized approach / runway overrun), CEN26LA122 (2026 C182 excessive speed / runway overrun), ERA25LA358 (2025 C182 improper touchdown point), and local-environment precedents ERA25LA325, ERA25LA322. Anonymized and localized to KVNC.
NTSB reports: ERA21LA113 · WPR20CA269 · CEN21LA055 · CEN26LA122 · ERA26LA116 · ERA25LA358 · ERA25LA325 · ERA25LA322
ACS tasks: PA.VIII.A — Normal Landing · PA.VIII.B — Forward Slip to Landing · PA.VIII.C — Short-Field Landing · PA.VIII.D — Soft-Field Landing · PA.VIII.E — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.II.A — Preflight Assessment
Relevant FARs: §91.3 · §91.13 · §61.31
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 182 Skylane scenarios · More scenarios at KVNC