FlightEdge
Sample scenario-based training
SAMPLE SBTLanding / Approach

Bounce and Recover

A hard landing, a bounced recovery, and the decision to go around — the C182's nose-heavy energy and constant-speed prop demand precision on approach

Cessna 182 Skylane · Zephyrhills Municipal Airport (KZPH) · Commercial · Landing / Approach

The scenario

Departing Zephyrhills Municipal Airport (KZPH), Zephyrhills, FL — Runway 19, on a personal flight. Elevation 90 ft MSL. You are a commercial pilot with roughly 800 hours total, 120 hours in the C182 Skylane. This is your second flight in this particular aircraft after a 100-hour inspection and elevator trim rigging maintenance performed by a Part 145 shop three days ago.

It is a clear, calm Florida afternoon: OAT 26°C, winds 180° at 3 kt (nearly calm), altimeter 30.01. Visibility 10 SM. The runway is dry. You have completed a standard preflight and run-up; the airplane is within limits, fuel full, and the elevator trim moved freely through its full range during the preflight check. Nothing was written up. You are solo.

You have completed a 1.2-hour local flight and are now on a 3-mile final approach to Runway 19 at 800 ft AGL. The approach is stable: 70 KIAS (best glide speed, power-off), descent rate 300 ft/min, flaps 20°, prop full forward (2,000 RPM), carburetor heat off (warm air, no icing risk). The runway is made. You are planning a normal landing.

Aircraft: Cessna 182 Skylane, solo, full fuel, within limits. Continental O-470 carbureted, constant-speed prop, cowl flaps, fixed gear, steam panel. The elevator trim was rigged by maintenance three days ago; you did not observe the work or the post-maintenance test flight.

Pilot: You — a commercial pilot, current, 800 hours total, 120 hours in type. You are familiar with the C182's nose-heavy characteristics and the need for precise flare control. You have landed at KZPH twice before, both uneventful. You are not fatigued.

The decision

Before we get into the decision tree — what do you know about the C182's landing characteristics and the go-around decision? (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 bounced, the pilot tried to recover by re-flaring, the airplane bounced again, and the pilot delayed the go-around decision. The runway ran out. The airplane exited the runway, the nose gear separated, and the airplane nosed over. The probable cause was the pilot's improper recovery from the bounced landing and failure to execute a timely go-around.

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 exited 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's failure to recognize the unstable landing and execute a timely go-around was the critical error.

NTSB ERA26LA009 (2025): A Cessna 182H made a hard landing on the nose gear after the pilot, while holding the jump door closed, attempted to add elevator trim for the landing flare. Post-flight investigation revealed that maintenance personnel had improperly rigged the elevator trim system. The probable cause was improper rigging of the elevator trim system by maintenance personnel and failure to perform post-maintenance and preflight inspections that would have detected the defect. The pilot's preflight check of the elevator trim (moving it through its full range) did not detect the rigging defect because the defect was in the mechanical linkage, not the control movement.

The local environment at KZPH makes this scenario consequential: Runway 19's climb-out environment is marginal — open developed area (parks/large lots), evergreen forest, and low-density development. A runway excursion off Runway 19 results in collision with trees or a nose-over in an open area. There is no long overrun area or clear off-field landing surface. The runway is 5,072 ft — adequate for a normal landing, but if the airplane bounces and the go-around decision is delayed, the runway runs out quickly.

The real accidents cited above occurred at other airports — NOT at Zephyrhills Municipal Airport. KZPH has its own accident history dominated by forced landings and loss-of-control events. The scenario is localized to KZPH to make the off-field environment real and consequential for you as a student here.

The consistent thread across all these events: the C182's nose-heavy characteristics and higher approach speed demand precise flare control. A shallow or late flare results in a hard landing. A hard landing can produce a bounce. The bounce is the critical decision point — the pilot must recognize the bounce as a signal to go around, not as a recoverable situation. Continuing to try to recover from multiple bounces until the runway runs out is the trap. The go-around decision must be made early, at the first or second bounce, while sufficient runway and altitude remain.

Key lesson — In the C182, a hard landing or bounce is a signal to go around, not a recoverable situation. The go-around decision must be made immediately, at the first or second bounce, while sufficient runway and altitude remain. Delaying the go-around decision until multiple bounces have occurred and the runway is running out results in a runway excursion. Additionally, elevator trim rigging defects from maintenance can make the airplane difficult to flare properly — post-maintenance test flights and thorough preflight inspections are critical to detect such defects before they cause an accident.

Debrief — teaching points

The C182 is nose-heavy — the flare is critical.

The Cessna 182 is heavier and faster than the C172, and the center of gravity is farther forward. The nose wants to drop in the flare. A shallow flare or a late flare results in the nose dropping and a hard landing on the nose gear. The flare must be smooth and progressive, raising the nose gradually to arrest the descent and achieve a main-gear-first touchdown. Practice the flare technique in the C182 until it is automatic. The nose-heavy characteristics are not a defect — they are a design feature that makes the airplane stable in cruise — but they demand precise flare control.

A hard landing or bounce is a signal to go around.

If the landing is clearly going to be hard, or if the airplane bounces after touchdown, the go-around decision must be made immediately. Do not try to recover from a bounce by re-flaring. Do not try to force the airplane back onto the runway by pushing forward on the yoke. Apply full power, retract flaps to 0°, and climb away. The go-around decision must be made at the first or second bounce, while sufficient runway and altitude remain. Continuing to try to recover from multiple bounces until the runway runs out results in a runway excursion. The NTSB WPR20CA269 case is the precedent: the pilot delayed the go-around decision until the runway ran out, and the airplane exited the runway and collided with trees.

Elevator trim rigging defects can make the airplane difficult to flare.

The C182's elevator trim system is critical for flare control. If the trim is rigged incorrectly by maintenance, the elevator response can be sluggish or delayed, making the airplane difficult to flare properly. A hard landing can result. Post-maintenance test flights are required to verify that the elevator trim system is functioning correctly. Additionally, a thorough preflight inspection — moving the elevator trim through its full range and checking for smooth, responsive movement — is critical. However, a rigging defect in the mechanical linkage (not just the control movement) may not be detected by a simple preflight check. If the elevator response feels wrong during the flare, go around immediately and investigate the trim system on the ground.

The C182's constant-speed prop requires RPM management.

The C182 has a constant-speed prop that requires RPM management during descent and landing. The standard landing configuration is prop full forward (2,000 RPM). This is set during the descent and should not be changed during the approach or landing. Forgetting to set the prop full forward results in lower RPM and reduced engine response if a go-around is needed. Make prop full forward a standard part of your descent checklist.

Cowl flaps and carburetor heat management in the C182.

The C182 has cowl flaps for engine cooling management. During descent and landing, cowl flaps should be open to allow maximum cooling. Carburetor heat should be off during landing (unless conditions warrant it — warm, moist air at reduced power). The C182's Continental O-470 is carbureted, so carburetor ice is a potential issue in conducive conditions. However, during a normal landing approach, carburetor heat is typically off. If the engine runs rough during the approach, apply carburetor heat immediately and diagnose the issue.

Off-field environment at KZPH Runway 19 is marginal.

The off-field environment off Runway 19's climb-out end (heading 180°) is marginal: open developed area (parks/large lots), evergreen forest, and low-density development. A runway excursion off Runway 19 results in collision with trees or a nose-over in an open area. There is no long overrun area or clear off-field landing surface. The runway is 5,072 ft — adequate for a normal landing, but if the airplane bounces and the go-around decision is delayed, the runway runs out quickly. Know the off-field environment before you depart.

Built from the real accident record

Scenario built from NTSB ERA21LA113 (2021 C182 hard landing / nose wheel separation), WPR20CA269 (2020 C182 bounced landing / delayed go-around / runway excursion), and ERA26LA009 (2025 C182H elevator trim rigging defect / hard landing). Anonymized and localized to KZPH.

NTSB reports: ERA21LA113 · WPR20CA269 · ERA26LA009

ACS tasks: PA.II.J — Approach and Landing · PA.II.K — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.II.B — Engine Starting / Systems Preflight · PA.IX.C — Emergency Approach and Landing

Relevant FARs: §91.3 · §91.13 · §135.63

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 KZPH