Float and Overshoot at Peter O Knight
A fast, unstable approach in a high-performance Cessna 182 — energy management and the go-around decision at a tight field
The scenario
Departing Peter O Knight Airport (KTPF), Tampa, FL — Runway 22, a 3,583-foot asphalt strip at 8 ft MSL. You are a Commercial pilot with a high-performance endorsement, roughly 800 hours total, current in the Cessna 182 Skylane. This is a personal flight; you are solo.
It is a hot, humid Tampa afternoon in late July: OAT 32°C, dew point 26°C, altimeter 29.89. Density altitude is approximately 2,800 ft — the runway will perform as if it were 2,800 ft high. Winds are calm to light, with occasional gusts to 8 knots. Visibility is 10 SM. KTPF is non-towered (CTAF 118.2); you are in Class G airspace, but the overlying Tampa Class B (1,200 MSL ceiling) is 5.7 nm to the north.
You are on a 5-mile final approach to Runway 22 (heading 217°). The runway is in sight. You have been flying the approach at 90 KIAS — slightly above the recommended Vref of 60 KIAS for a short-field approach. The descent is stable, but the airplane is carrying energy. You are configured: flaps 20°, prop full RPM (2,700), cowl flaps open for cooling, carb heat on (warm, humid conditions), mixture leaned for density altitude.
Aircraft: Cessna 182 Skylane, solo, 2,400 lb (within limits), fuel 40 gallons (sufficient). The 182 is a high-performance single: Continental O-470 (230 hp), constant-speed prop, fixed gear, fuel selector BOTH. It is faster and heavier than a 172, with more nose-down trim and more energy on approach. A fast or shallow approach floats the runway, and the nose drops into a porpoise or hard landing.
Pilot: you — Commercial, high-performance endorsement, current. You have 800 hours, but only 12 hours in the 182. You are familiar with the airplane's systems but not deeply experienced with its approach characteristics. You have not landed at KTPF before. The runway is 3,583 feet — adequate for a 182 in calm conditions, but tight if you float or land long.
- {'label': 'Field', 'value': 'KTPF · Peter O Knight'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '8 ft'}
- {'label': 'Aircraft', 'value': 'C182'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
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 airplane's nose wheel separated and the aircraft nosed over. The probable cause was the pilot's improper recovery from the bounced landing — the pilot did not execute a go-around when the bounce occurred, and instead tried to recover and land the airplane. The runway was adequate, but the landing technique was not.
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 delayed go-around. The pilot had the opportunity to go around after the bounce but chose to continue landing instead.
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. Contributing to the accident was inaccurate wind direction reporting from a misaligned weather station.
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 achieve the proper touchdown point. The pilot landed long and did not have sufficient runway remaining to stop.
The consistent thread across all these accidents: the Cessna 182 is a high-performance, nose-heavy airplane that carries energy on approach. Pilots who maintain approach speeds above Vref (60 KIAS), who land long, or who attempt to recover from a bounce instead of going around, end up in runway excursions. The 182 is not forgiving of sloppy approaches — it will float, it will bounce, and if you land long, the runway will run out.
At KTPF, Runway 22 is 3,583 feet. At 2,800 ft density altitude, that is tight. Off Runway 22's departure end (heading 217°), the off-field environment is open water — Tampa Bay. A runway overrun off that end is a ditching, not a field landing. The geographic reality makes the landing decision even more critical: a stabilized approach at Vref, a short-field landing technique, and a go-around if unstable are not optional. They are the difference between a safe landing and a ditching.
The real accidents cited above occurred at other airports and in other conditions — NOT at KTPF. KTPF has its own accident history (dominated by forced landings and loss-of-control events), but these specific runway-excursion accidents happened elsewhere. The scenario is localized to KTPF to make the runway length and off-field environment real and consequential for you as a pilot here.
Key lesson — The Cessna 182 is a fast, heavy, nose-down airplane that carries energy on approach. Vref for short-field landing is 60 KIAS; exceeding this speed by 10–30 knots adds significant float distance and touchdown point uncertainty. At a tight field like KTPF (3,583 feet at 2,800 ft density altitude), a fast or unstable approach will result in a long landing and a marginal go-around decision. The correct response to an unstable approach at 2 miles final is a go-around — not a recovery attempt. Off Runway 22 at KTPF, the off-field environment is open water: a runway overrun is a ditching.
Debrief — teaching points
The Cessna 182 is not a 172 — it carries more energy and requires different approach management.
The 182 is 600+ pounds heavier than a 172, with a 230 hp Continental O-470 (vs. 160 hp in a 172), a constant-speed prop, and cowl flaps. It is faster, nose-heavy, and carries more energy on approach. A 172 can tolerate a 90 KIAS approach to a 3,500-foot runway; a 182 cannot. Vref for short-field landing is 60 KIAS — not 70, not 80. Exceeding Vref by 10 knots adds 200+ feet of float distance. At 2,800 ft density altitude, that float distance is not recoverable.
Density altitude erodes runway performance — a 3,583-foot runway at 2,800 ft DA is tight.
Density altitude is the effective altitude at which the airplane performs. At 2,800 ft DA, a 3,583-foot runway performs as if it were 2,800 ft high. For a 182, the minimum runway length for a normal landing is approximately 2,500 feet (sea level, standard conditions). At 2,800 ft DA, that effective length is reduced by 10–15%. A short-field landing technique (full flaps, 60 KIAS, steep descent) is not optional — it is the correct procedure. A normal landing at 70–80 KIAS will land long and leave insufficient margin.
An unstable approach at 2 miles final is a go-around, not a recovery.
An unstable approach is defined as one that is not stabilized in pitch, roll, heading, or airspeed by the 2-mile point (or 500 ft AGL, whichever is lower). If your approach is 30 knots fast, if the descent is too shallow, or if the touchdown point is uncertain, the correct decision is a go-around. The go-around is not a failure — it is airmanship. The NTSB data shows that pilots who attempt to recover from an unstable approach at low altitude end up in runway excursions or accidents. Pilots who go around and reset end up landing safely.
A bounce at touchdown is a signal to go around — not to recover and land.
If the 182 bounces at touchdown, the correct response is to immediately advance power, lower the nose to maintain 80 KIAS (Vy), retract flaps to 10°, and climb out. Do not attempt to land the airplane again by applying forward pressure and braking. A bounce at 1,500–2,000 feet down the runway means you landed long; you do not have runway remaining for a safe recovery. The NTSB ERA21LA113 accident was caused by a pilot who tried to recover from a bounce instead of going around. The result was a hard landing, nose-wheel separation, and a nose-over.
Off Runway 22 at KTPF, the off-field environment is open water — a runway overrun is a ditching.
The off-field environment off Runway 22's departure end (heading 217°) is open water — Tampa Bay. There is no alternate landing surface. A runway overrun off that end is a ditching, not a field landing. This geographic reality makes the landing decision even more critical. A stabilized approach at Vref, a short-field landing technique, and a go-around if unstable are not optional — they are the difference between a safe landing and a ditching. Know the off-field environment before you line up on final.
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 / power-line strike), CEN26LA122 (2026 C182 insufficient runway / fence strike), ERA25LA358 (2025 C182 improper touchdown point / overrun), and local-environment precedents. Anonymized and localized to KTPF.
NTSB reports: ERA21LA113 · WPR20CA269 · CEN21LA055 · CEN26LA122 · ERA25LA358 · ERA25LA325 · ERA25LA322
ACS tasks: PA.V.A — Approach and Landing · PA.V.B — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.II.D — Approach and Landing · PA.III.A — Preflight Inspection
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 KTPF