FlightEdge
Sample scenario-based training
SAMPLE SBTLanding / Approach

Float and Overshoot at Brooksville

A Cessna 182's excess approach energy, a bounced landing, and the critical decision to go around — or push it

Cessna 182 Skylane · Brooksville–Tampa Bay Regional Airport (KBKV) · Commercial · Landing / Approach

The scenario

Departing Brooksville–Tampa Bay Regional Airport (KBKV), Brooksville, FL — Runway 09, a 7,001-foot concrete surface. Elevation 76 ft MSL. You are a commercial pilot with a high-performance endorsement, currently 850 hours total time, 120 hours in the Cessna 182 Skylane. This is a personal flight; you are solo.

It is a hot, humid Florida afternoon in early August: OAT 32°C, dew point 26°C, altimeter 29.89. Scattered clouds at 3,500 ft. Visibility 10 SM. The wind is reported from 110° at 8 knots — a light crosswind from the right on Runway 09. Density altitude is approximately 2,200 ft, which erodes the 182's climb performance noticeably.

You have completed a 1.5-hour flight from a nearby field and are returning to KBKV for a full-stop landing. The approach is stable until about 500 ft AGL, where you realize you are slightly high and fast. You are at 75 KIAS on short final — 15 knots above Vref (60 KIAS for a power-off short-field approach). The runway is long (7,001 ft), and you have been flying the 182 for a few months. The tower is active (it is 1400 local; tower operates 0700–2200).

Aircraft: Cessna 182 Skylane, solo, 45 gallons usable fuel (full), within CG and weight limits. Continental O-470 carbureted engine, constant-speed prop, cowl flaps (currently open for cooling), fixed landing gear, steam/vacuum panel. You have not flown a high-performance retractable-gear airplane before; the 182's fixed gear and constant-speed prop represent a step up in systems management.

Pilot: You — commercial pilot, high-performance endorsement current, 850 hours total, 120 hours in type. You completed the 182 transition training 3 months ago. This is your fourth solo flight in the airplane. You have not experienced a bounced landing in the 182 before. Your recent landings have been consistently firm — you attribute this to the 182's heavier nose and faster approach energy compared to the 172 you trained in.

The decision

Before we get into the decision tree — what do you know about the Cessna 182's approach and landing characteristics compared to a 172? (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 bounce led to a porpoise, and the pilot's improper recovery (likely excessive back-pressure) worsened the oscillations. The nose wheel separated, and the airplane nosed over. The probable cause was the pilot's improper recovery from the bounced landing.

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 airplane departed the runway and collided with trees. The probable cause was the pilot's decision to continue an unstable approach and the delayed go-around.

NTSB CEN21LA055 (2020, fatal): A Cessna 182R on approach to Rockwall Municipal Airport (a different field) landed on the wrong runway despite radio calls 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.

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.

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 airplane floated too far down the runway.

The real accidents cited above occurred at other airports and in other aircraft — NOT at Brooksville–Tampa Bay Regional Airport (KBKV). KBKV has its own accident history dominated by hard landings (26.9%), forced landings (11.5%), and runway excursions (11.5%). The scenario is localized to KBKV to make the runway length and off-field environment real and consequential for you as a student here. Runway 09 is 7,001 ft long — a long runway — but the NTSB data shows that long runways do not prevent excursions when the approach is unstable and the pilot delays the go-around decision.

The consistent thread across all these events: the Cessna 182's heavier nose, higher approach energy, and constant-speed prop require precise flare timing and smooth control inputs. A high or fast approach that floats down the runway, followed by a bounce and a delayed go-around decision, is the pathway to a runway excursion. The fix is simple: if the approach is unstable below 500 ft AGL, go around. The second approach, flown with discipline, is the safe one.

Key lesson — The Cessna 182 Skylane carries more approach energy than a 172 — the heavier nose and higher wing loading mean a high or fast approach will float, and a bounce can lead to a porpoise if the flare is not perfectly timed. At KBKV, Runway 09 is 7,001 ft long, but the NTSB data shows that long runways do not prevent excursions when the approach is unstable. The decision rule is simple: if the approach is unstable below 500 ft AGL, go around. A go-around at 500 ft AGL is a safe, defensible decision. Pushing a bad approach to the runway is how runway excursions happen.

Debrief — teaching points

The Cessna 182 carries more approach energy than a 172 — plan accordingly.

The 182 is heavier (2,950 lb gross vs. 2,450 lb for a 172) and has a higher wing loading. This means a high or fast approach will float longer, and the flare requires more back-pressure. At KBKV's elevation (76 ft MSL) with a density altitude of 2,200 ft on a hot day, the 182's climb performance is noticeably reduced. Plan the approach carefully: reduce power early, extend the downwind to allow time for descent, and plan to be at Vref (60 KIAS) on short final — not 75 KIAS. The extra 15 knots means a longer float and a touchdown point farther down the runway.

Vref for the Cessna 182 is 60 KIAS (power-off short-field approach) — not 65 or 70.

The POH is clear: Vref (approach speed, power-off) for the 182 is 60 KIAS. This is the speed that gives the slowest possible touchdown speed and the shortest landing distance. If you are at 75 KIAS on short final, you are 15 knots fast — that is a significant energy penalty. The airplane will float, and the touchdown point will move down the runway. Discipline on approach speed is non-negotiable in the 182.

A bounced landing in the 182 can lead to a porpoise — know the recovery.

If the main gear touches down and rebounds (a bounce), the airplane can enter a porpoise — a series of pitch oscillations. The 182's heavier nose makes this more likely than in a 172. The correct recovery is to hold the pitch attitude steady and let the oscillations dampen naturally, or apply gentle forward pressure to lower the nose and increase airspeed. Do NOT apply back-pressure — this increases the angle of attack and worsens the porpoise. If the porpoise becomes violent and the nose pitches up sharply, apply firm forward pressure immediately to prevent a stall.

If the approach is unstable below 500 ft AGL, go around — do not push it to the runway.

The NTSB data is clear: pilots who continue unstable approaches and delay the go-around decision end up in runway excursions. At KBKV, Runway 09 is 7,001 ft long — a long runway — but that does not prevent excursions when the approach is unstable. The decision rule is simple: if the approach is unstable below 500 ft AGL (high, fast, not aligned with the runway, or not descending at the planned rate), go around. A go-around at 500 ft AGL is a safe, defensible decision. The second approach, flown with discipline, is the safe one.

The 182's constant-speed prop requires RPM management — keep it at high RPM during approach.

The 182's constant-speed prop is different from the 172's fixed-pitch prop. During approach, the prop should be set to high RPM (full forward on the prop control) for maximum responsiveness and engine power if you need to go around. If the prop is at low RPM and you need to go around, the engine will be sluggish. Keep the prop at high RPM throughout the approach and landing.

Cowl flaps management affects engine cooling — open them during descent and landing.

The 182 has cowl flaps for engine cooling management. During descent and landing, the cowl flaps should be open to allow adequate cooling. If the cowl flaps are closed during approach, the engine may overheat, especially on a hot day. Open the cowl flaps during the descent and keep them open until after landing.

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), CEN21LA055 (2020 C182 unstabilized approach / runway overrun), CEN26LA122 (2026 C182 insufficient runway / fence strike), ERA25LA358 (2025 C182 improper touchdown point), and local-environment precedents ERA25LA325, ERA25LA322. Anonymized and localized to KBKV.

NTSB reports: ERA21LA113 · WPR20CA269 · CEN21LA055 · CEN26LA122 · ERA25LA358 · ERA25LA325 · ERA25LA322

ACS tasks: PA.I.F — Weather Information · PA.II.F — Approach and Landing · PA.II.G — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.IX.C — Emergency Approach and Landing

Relevant FARs: §91.3 · §91.13 · §61.31

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 182 Skylane scenarios · More scenarios at KBKV