Float and Overshoot at Tampa North
A Cessna 182's excess approach energy, a short runway, and the decision to go around — or commit to a landing that is already unstable
The scenario
Departing Tampa North Aero Park Airport (X39), Tampa, FL — Runway 14, a 3,541-foot asphalt strip. Elevation 68 ft MSL. You are on a personal flight in a Cessna 182 Skylane, solo, full fuel (82 gallons usable), within weight and balance limits. Aircraft is airworthy; no write-ups. You have logged 350 hours total, 45 hours in the C182 (high-performance endorsement current). This is your second visit to X39; you are not familiar with the field.
It is a warm Florida afternoon in late May: OAT 32°C, dew point 24°C, altimeter 29.89. Density altitude approximately 2,100 ft — the field's 68-foot elevation feels like 2,168 ft. Winds are calm to light (2–4 knots, variable). Visibility 10 SM. VFR all the way. You have been flying for 2.5 hours; you are not fatigued, but you are ready to land.
You are on a 5-mile straight-in approach to Runway 14 (true heading 141°). You have been descending at 500 fpm, power at 1,500 RPM, prop at 2,000 RPM (constant-speed prop management), cowl flaps open for cooling. Approach speed is 60 KIAS (Vref, short-field approach). You are 1,000 ft AGL. The runway is in sight, well-aligned, no traffic. Everything looks normal.
At 500 ft AGL, you notice the descent rate is shallower than expected. You are floating slightly — the airplane is not descending as steeply as the glide path should allow. You are still 60 KIAS, but the airplane is not sinking. You have 2,000 ft of runway ahead of you. You have time.
At 200 ft AGL, the float is more pronounced. You are still 60 KIAS, but you are drifting down the runway, not descending to it. You are now 1,500 ft from the runway threshold. The off-field environment off Runway 14's approach end is medium development, low-density development, and wooded wetland — not a go-around-friendly option, but not immediately catastrophic either. You have a decision to make: commit to landing on the remaining runway, or execute a go-around and come around again.
- {'label': 'Field', 'value': 'X39 · Tampa North Aero Park'}
- {'label': 'Runways', 'value': '14/32'}
- {'label': 'Elevation', 'value': '68 ft'}
- {'label': 'Aircraft', 'value': 'C182'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we enter the decision tree — what do you know about the C182'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, resulting in nose-wheel separation and a nose-over. The pilot's improper recovery from the bounced landing was the probable cause. The airplane was a total loss.
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, resulting in departure from the runway and collision with trees. The probable cause was the pilot's decision to continue an unstable approach and delayed go-around.
NTSB CEN21LA055 (2020, FATAL): A Cessna 182R on approach to Rockwall Municipal Airport landed on the wrong runway despite radio calls from other pilots indicating the correct runway was in use. 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, with contributing factors including inaccurate wind direction reporting from a misaligned weather station.
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 consistent pattern across all these accidents: an unstabilized approach with excess energy, a float or late touchdown, a hard landing or bounce, and a delayed or absent go-around decision. The C182 is heavier and faster than a C172; it carries more energy into the landing and floats more easily if the approach is not stabilized. A float at 200 ft AGL is not a minor issue — it is a sign that the approach is unstabilized and a go-around should be executed immediately.
The real accidents cited above occurred at other airports and in other aircraft types — NOT at Tampa North Aero Park Airport (X39). X39's own accident corpus shows LOSS_OF_CONTROL_INFLIGHT (27.3%), LOSS_OF_CONTROL_GROUND (18.2%), OBSTACLE_ON_TAKEOFF_LANDING (9.1%), HARD_LANDING (9.1%), and STALL_SPIN (9.1%) as the dominant patterns. This scenario is localized to X39 to make the runway length (3,541 ft) and the off-field environment (medium development, low-density development, wooded wetland) real and consequential for you as a student here.
The lesson: a float at 200 ft AGL in the C182 is a go-around. A bounce at 50 ft AGL is a go-around. An unstabilized approach is a go-around. The C182's energy and weight make it unforgiving of late decisions. The go-around is not a failure — it is the correct response to an unstabilized approach.
Key lesson — In the Cessna 182, a float at 200 ft AGL is a sign of an unstabilized approach with excess energy. The correct response is an immediate go-around — not a forward-stick push, not a power reduction, not an early flare, but a go-around. The C182 is heavier and faster than a C172; it carries more energy and floats more easily. A late touchdown or a bounce can lead to a hard landing, nose-gear damage, or a nose-over. The go-around is the safest option and the correct decision.
Debrief — teaching points
The C182 carries more energy than a C172 — it floats more easily.
The Cessna 182 is heavier (2,950 lbs gross vs. 2,450 lbs for a C172), faster (cruise ~140 KIAS vs. ~120 KIAS), and has a higher wing loading. It carries more kinetic energy into the landing. If the approach is not stabilized and the descent rate is shallow, the airplane will float down the runway. A float at 200 ft AGL is not a minor issue — it is a sign that the approach is unstabilized and the airplane will not touch down at the proper point. In a 3,541-foot runway, a late touchdown can quickly consume the available surface.
A stabilized approach in the C182 means a steady descent at Vref (60 KIAS) with the runway in sight and aligned.
Vref for the C182 (short-field approach) is 60 KIAS. A stabilized approach is one in which the airplane is descending at a constant rate (typically 300–500 fpm), the descent path is aligned with the runway, and the speed is stable at Vref. If the descent rate is shallower than expected or the airplane is floating, the approach is unstabilized. The correct response is a go-around — not a forward-stick push, not a power reduction, but a go-around.
A go-around at 200 ft AGL is safe and correct — a go-around at 50 ft AGL after a bounce is also correct.
The FAA and the NTSB both recommend a go-around if the approach is unstabilized at any point. A go-around at 200 ft AGL is safe — you have altitude and runway to execute it. A go-around at 100 ft AGL is also safe. Even a go-around at 50 ft AGL after a bounce is the correct decision if the alternative is a hard landing, a nose-over, or a runway excursion. The go-around is not a failure — it is airmanship.
A bounce in the C182 is a critical moment — the recovery must be smooth and controlled.
If the C182 bounces on landing (main gear lifts off after a hard first touchdown), the recovery is critical. The nose gear must not touch down hard — a hard nose-gear touchdown can cause nose-wheel separation or a nose-over. The correct recovery is to level the pitch attitude and let the airplane settle onto the runway for a second, controlled touchdown. Alternatively, a go-around is the safest option. Applying maximum braking after a bounce is dangerous — it can cause the nose gear to collapse.
High density altitude reduces climb performance and increases landing distance required.
On a warm, humid day like the scenario (OAT 32°C, dew point 24°C), the density altitude at X39 (68 ft elevation) is approximately 2,100 ft. This means the airplane performs as if it is at 2,100 ft elevation, not 68 ft. Climb performance is reduced, and landing distance required is increased. The POH landing distance tables account for density altitude; always use the correct table for the conditions. A late touchdown that would be acceptable at sea level on a cool day may be unacceptable at high density altitude.
The constant-speed prop in the C182 requires RPM management — set prop RPM for the phase of flight.
The C182 has a constant-speed propeller, unlike the C172's fixed-pitch prop. During approach and landing, the prop should be set to 2,000 RPM (high RPM for maximum power if a go-around is needed). The prop will automatically adjust blade pitch to maintain the set RPM. During cruise, the prop can be set to 2,000 RPM or lower for fuel efficiency. Know your prop management for each phase of flight.
Built from the real accident record
Scenario built from NTSB ERA21LA113 (2021 C182 bounced landing / nose-wheel separation), WPR20CA269 (2020 C182 hard landing / delayed go-around / tree strike), CEN21LA055 (2020 C182R wrong-runway landing / power-line strike), CEN26LA122 (2026 C182 unstabilized approach / runway overrun), ERA26LA116 (2026 C182G engine failure / runway overrun), ERA25LA358 (2025 C182 late touchdown / runway overrun), ERA25LA325 (2025 C182 crosswind takeoff excursion), and ERA25LA322 (2025 C182 soft-field abort / runway overrun). Localized to Tampa North Aero Park Airport (X39).
NTSB reports: ERA21LA113 · WPR20CA269 · CEN21LA055 · CEN26LA122 · ERA26LA116 · ERA25LA358 · ERA25LA325 · ERA25LA322
ACS tasks: PA.II.D — Approach and Landing · PA.II.E — 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.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 Cessna 182 Skylane scenarios · More scenarios at X39