Float, Bounce, and Recovery
A misjudged flare in the Piper Archer — managing the bounce and directional control on a busy Class D field
The scenario
Departing St. Petersburg Clearwater International Airport (KPIE), Pinellas Park, FL — Runway 18, approaching for landing after a 1.5-hour local flight. Elevation 11 ft MSL. The runway is 9,730 ft of concrete, plenty of room. Class D airspace, tower active (0600–2300 local), current time 1530 local.
Weather: VFR. Wind 180° at 12 knots, gusting to 18 knots — a direct crosswind to Runway 18 (true heading 171°). Visibility 10 SM, scattered clouds at 3,500 ft, temperature 29°C, dew point 21°C. The crosswind is within limits for the Archer (demonstrated crosswind 12 knots, but gusts to 18 are pushing it). Windshear is possible in the approach corridor — typical for Tampa Bay in the afternoon.
Aircraft: Piper PA-28-181 Archer, solo, 2,400 lb (within limits), full fuel, fixed gear, fixed-pitch prop, carbureted Lycoming O-360. Fuel selector is on LEFT tank (you switched from RIGHT on downwind). Flaps are down 40° (full). You are on a 3° glide slope, 500 ft AGL, 1.5 nm from the runway on a left base to Runway 18.
Pilot: you — a Private pilot, current, 180 hours total. You have 12 hours in the Archer (a faster, heavier airplane than the Cessna 172 you trained in). You are familiar with KPIE — you have landed here 8 times. The crosswind is noticeable but manageable. You are focused on the approach.
Tower clears you to land: 'Archer [N-number], cleared to land Runway 18, wind 180 at 12, gusting 18.' You acknowledge and continue the approach.
- {'label': 'Field', 'value': 'KPIE · St. Petersburg Clearwater'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '11 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-181'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we get into the decision tree — what do you know about landing the Piper Archer in crosswind conditions and recovering from a bounced landing? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB LAX08CA199 (2008): A Piper PA-28-181 student pilot on solo flight was vectored to Runway 22R. The student delayed flap extension and landed with excessive airspeed (approximately 75 KIAS instead of the recommended 66 KIAS Vref). The aircraft bounced on touchdown. Instead of executing a go-around, the student attempted to recover from the bounce by adding power and trying to land again. The airplane veered left during the recovery, departed the runway, and struck a ditch. The nose gear collapsed, and the firewall was damaged. The probable cause was the student pilot's inadequate recovery from the bounced landing and failure to maintain directional control. The student was unharmed.
NTSB LAX04CA289 (2004): A Piper PA-28-181 on a student instructional flight experienced a hard landing and runway excursion at Scottsdale Airport. The student pilot misjudged the flare, resulting in a stall and hard landing. The airplane bounced. The student failed to maintain directional control during the landing rollout, and the airplane departed the runway. The probable cause was the pilot's misjudged flare and failure to maintain directional control. Contributing factors included improper recovery from the bounced landing.
NTSB ERA10CA473 (2010): A Piper PA-28 on approach to a destination airport encountered windshear and stalled during landing, resulting in a hard landing and runway excursion. The probable cause was the pilot's inadequate compensation for crosswind conditions. The crosswind was within the airplane's demonstrated limits, but the pilot did not adequately adjust the approach technique.
The common thread: the Piper Archer (PA-28-181) is a heavier, faster airplane than the Cessna 172. It carries more energy into the landing. Excess airspeed on final (landing at 75+ KIAS instead of 66 KIAS Vref) causes floating and a long landing. A misjudged flare results in a hard landing and a bounce. The critical decision point is the bounce: a go-around is the professional recovery. Attempting to land again or trying to salvage the bounce often leads to a loss of directional control and a runway excursion.
At KPIE, the off-field environment off Runway 18's departure end (heading 171°) is marginal — medium development, parks, and dense development. A runway excursion to the left (downwind in a crosswind) puts the airplane into this marginal terrain. A nose-gear collapse in soft ground or a strike on an obstacle is the likely outcome.
The real accidents cited above occurred at other airports (LAX area, Scottsdale) — NOT at KPIE. KPIE has its own accident history (see field dominant patterns: LOSS_OF_CONTROL_GROUND 15.2%, GEAR_UP_LANDING 9.1%), but these specific NTSB events happened elsewhere. The scenario is localized to KPIE to make the off-field environment and the runway configuration real for you as a student here.
The key lesson: in the Piper Archer, manage the approach speed carefully. Land at Vref (66 KIAS), not 75+ KIAS. If the approach is unstable or the flare is misjudged, go around — do not try to salvage a bad landing. A bounce is a signal to go around, not to try again.
Key lesson — The Piper Archer is heavier and faster than the Cessna 172. Excess airspeed on final causes floating and a long landing. A misjudged flare results in a hard landing and a bounce. The bounce is the critical decision point: go around immediately. Attempting to land again or trying to salvage the bounce leads to loss of directional control and a runway excursion. At KPIE Runway 18, the off-field environment is marginal — a runway excursion is serious.
Debrief — teaching points
The Piper Archer is heavier and faster than the Cessna 172 — approach speed discipline is critical.
Vref (approach speed) for the PA-28-181 is 66 KIAS. Landing at 75+ KIAS causes the airplane to float — it does not want to land. The Archer's heavier wing loading and higher inertia mean it carries more energy into the landing. Excess airspeed results in a long landing and often a bounce. Manage the approach speed carefully. If you are above Vref on final, reduce power and increase the descent rate to get back to 66 KIAS before the flare.
The flare is a gradual, progressive maneuver — not an abrupt pitch-up.
A good flare begins around 50 ft AGL and is a smooth, gradual raising of the nose to reduce the descent rate. The goal is to arrive at the runway with a descent rate of 50 ft/min or less — a gentle touchdown. A late flare (starting at 20 ft AGL) or an aggressive flare (raising the nose too steeply) risks a stall and a hard landing. Practice the flare in calm conditions first; crosswind conditions demand even more precision.
A bounce is a signal to go around — not to try to land again.
If the main gear bounces on touchdown, the airplane is still flying (or nearly flying) at low altitude over the runway. The correct response is to apply full power, raise the flaps to 0°, and climb out. Attempting to land again or trying to salvage the bounce by reducing power and trying to settle the airplane often leads to a second, harder bounce or a loss of directional control. A go-around is the professional, safe recovery. The runway will still be there for the next approach.
Crosswind technique: crab or forward slip to maintain the runway centerline.
In a crosswind, use a crab (nose pointed into the wind, wings level) or a forward slip (wing down into the wind, nose aligned with the runway) to maintain the runway centerline during the approach. In the flare, transition to a wings-level, nose-aligned attitude. Use aileron to keep the wings level and rudder to keep the nose aligned with the runway. Differential braking during the rollout helps maintain directional control.
Directional control during rollout is maintained with differential braking and nosewheel steering.
After touchdown, the nosewheel is on the ground and you have directional control via the rudder pedals (nosewheel steering). In a crosswind, apply differential braking (more brake on the downwind side) to counteract the crosswind drift. Use gentle rudder inputs to keep the nose aligned with the runway centerline. Avoid aggressive braking on one side, which can cause a sharp turn or a loss of control.
At KPIE Runway 18, the off-field environment off the departure end is marginal — a runway excursion is serious.
The off-field environment off Runway 18's departure end (heading 171°) is marginal: medium development, parks, and dense development. A runway excursion to the left (downwind in a crosswind) puts the airplane into this terrain. A nose-gear collapse in soft ground, a strike on an obstacle, or a collision with a building is possible. Maintain the runway centerline during rollout. If you are drifting off the runway, apply differential braking and nosewheel steering to correct. If the drift is severe, apply full brakes and accept the hard stop rather than risk an excursion.
Built from the real accident record
Scenario built from NTSB ERA10CA473 (2010 PA-28 windshear/stall hard landing), LAX08CA199 (2008 PA-28-181 bounced landing/runway excursion), and LAX04CA289 (2004 PA-28-181 misjudged flare/hard landing). Anonymized and localized to KPIE.
NTSB reports: ERA10CA473 · LAX08CA199 · LAX04CA289
ACS tasks: PA.II.J — Approach and Landing · PA.II.K — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.II.I — Crosswind Landings · PA.IX.C — Emergency Approach and Landing
Relevant FARs: §91.3 · §91.13 · §91.117
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 Piper Archer scenarios · More scenarios at KPIE