Bounce and Drift at Zephyrhills
A misjudged flare in a Piper Archer, a bounced landing, and the decision to go around — or push it down
The scenario
Departing Zephyrhills Municipal Airport (KZPH), Zephyrhills, FL — Runway 19, on a local VFR flight. Elevation 90 ft MSL. You are a Private pilot with roughly 180 hours total, 40 hours in the Piper Archer. This is a familiar field; you have landed here a dozen times.
It is a warm afternoon in late spring: OAT 26°C, winds reported 180° at 12 gusting to 18 knots. Runway 19 is aligned 180° true — a direct headwind with gusts. Visibility 10 SM, scattered clouds at 3,500 ft. A typical Florida afternoon: warm, gusty, and workable.
You have been flying for 1.5 hours. The approach is stable: you are on a 3° glide slope, 2 nm from the runway, descending at 500 fpm, airspeed 90 KIAS. Flaps are at 20°. Trim is set. The runway is in sight. Everything feels normal.
Aircraft: Piper PA-28-181 Archer, solo, 2,400 lb (within limits). Carbureted Lycoming O-360, fixed-pitch prop, fixed gear, steam panel. The airplane has been flown all morning; no write-ups. You are current and proficient.
Pilot: you — a Private pilot, current, roughly 180 hours total, 40 hours in type. You have landed at KZPH before. You did not brief the crosswind component or the gust factor. You are confident in your ability to handle the approach.
- {'label': 'Field', 'value': 'KZPH · Zephyrhills'}
- {'label': 'Runways', 'value': '19/1 · 5/23'}
- {'label': 'Elevation', 'value': '90 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-181'}
- {'label': 'Dominant phase', 'value': 'Landing / Cruise'}
The decision
Before we get into the decision tree — what do you already know about crosswind landings and go-around decisions in the Piper Archer? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB ERA10CA473 (2010): A Piper PA-28-181 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 airplane landed hard, bounced, and the pilot lost directional control during the landing rollout. The nose gear collapsed and the airplane came to rest off the runway.
NTSB LAX08CA199 (2008): A Piper PA-28-181 student pilot on solo flight was vectored to a runway and landed with excessive airspeed after delaying flap extension. The aircraft bounced on touchdown, veered left during recovery, departed the runway, and struck a ditch, collapsing the nose gear and damaging the firewall. The probable cause was the student pilot's inadequate recovery from the bounced landing and failure to maintain directional control.
NTSB LAX04CA289 (2004): A Piper PA-28-181 on a student instructional flight experienced a hard landing and runway excursion at Scottsdale Airport. The probable cause was the pilot's misjudged flare, resulting in a stall and hard landing, and his failure to maintain directional control during the landing rollout. The pilot's improper recovery from a bounced landing was a contributing factor.
The common thread across all three accidents: a hard landing or bounce, followed by loss of directional control, followed by an attempt to salvage the landing instead of going around. In each case, the pilot had the altitude and airspeed to execute a go-around, but chose instead to try to recover from the bounced landing. The result was a runway excursion and significant damage.
At KZPH, the off-field environment off Runway 19 is marginal — mostly open developed (parks/large lots), evergreen forest, and low-density development. A runway excursion off Runway 19 would likely result in a collision with trees or structures. The runway is 5,072 ft long, which is adequate for a normal landing, but a hard landing that consumes 2,000 ft of runway leaves only 3,000 ft for recovery. The decision to go around must be made early — at 50 ft AGL, not at 200 ft.
The real accidents cited above occurred at other airports and in other aircraft types — NOT at KZPH. The scenario is localized to KZPH to make the runway environment and off-field options real and consequential for you as a student here. The lesson is universal: in gusty or crosswind conditions, brief the approach, plan the flare, and set a low threshold for go-around. If the landing is unstable, bounces, or results in directional control loss, go around immediately. Do not try to salvage it.
Key lesson — In the Piper Archer, a hard landing or bounce on final approach is a signal to go around, not to salvage the landing. The Archer is heavier and faster than a Warrior; it carries more energy into the flare and floats longer if the flare is shallow. A progressive flare, briefed in advance, is the key to a smooth landing. If the landing is unstable, bounces, or results in directional control loss, go around immediately — you have the altitude and airspeed to do so safely. A runway excursion is the outcome of trying to salvage a bad landing.
Debrief — teaching points
The Piper Archer floats longer than a Warrior — plan for it.
The Archer is heavier and faster than a Warrior. It carries more energy into the flare and floats longer if the flare is shallow or delayed. The approach speed is 66 KIAS (Vref); the landing stall speed is 45 KIAS (Vs0). The flare must be progressive: shallow at 50 ft AGL, deepening as the airplane slows. A shallow, extended flare in gusty conditions can result in a float that consumes 1,000+ ft of runway. Plan the flare in advance and execute it progressively.
Crosswind gusts can create a crosswind component even in a headwind approach.
A wind reported as 12 gusting to 18 knots means the instantaneous wind can swing ±3 knots from the reported value. A 12-knot headwind at 180° can become a 6-knot crosswind gust from the right or left. The Archer's demonstrated crosswind component is roughly 12 knots; beyond that, directional control authority on the ground becomes marginal. Brief the gust factor and plan for a crosswind correction, even in a headwind approach.
A bounced landing is a signal to go around, not to salvage.
If the airplane bounces on touchdown, the correct response is to go around immediately — add power, raise the flaps, and climb away. Do not attempt to push the airplane back down or salvage the landing. A bounce indicates the landing was unstable; trying to recover from it on the runway risks a loss of directional control and a runway excursion. The NTSB LAX08CA199 and LAX04CA289 cases both involved bounces that the pilots tried to salvage, resulting in runway excursions and nose gear collapse. Go around. It is the correct decision.
Directional control loss on the runway is a runway excursion waiting to happen.
If the airplane is weaving or drifting on the runway after a hard landing or bounce, directional control is compromised. Heavy braking will worsen the problem by loading the nose gear further. Light brakes and relaxed rudder inputs are the correct response. If directional control cannot be recovered, the airplane will drift off the runway. The off-field environment at KZPH off Runway 19 is marginal — trees and structures are nearby. A runway excursion is a serious accident.
A formal approach brief is not optional — it is the foundation of a safe landing.
Before beginning the approach, brief the runway, the wind (mean and gust), the crosswind component, the approach speed (66 KIAS Vref), the flare plan (progressive, shallow at 50 ft, deepen as the airplane slows), the landing stall speed (45 KIAS Vs0), and the go-around threshold (low — if the landing is unstable, go around). This brief takes 30 seconds and is the foundation of a safe landing. Skipping the brief and flying by feel is how accidents happen.
Built from the real accident record
Scenario built from NTSB ERA10CA473 (2010 PA-28-181 hard landing / windshear / crosswind loss of control), LAX08CA199 (2008 PA-28-181 bounced landing / directional control loss), and LAX04CA289 (2004 PA-28-181 misjudged flare / hard landing / runway excursion). Anonymized and localized to KZPH.
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.IX.C — Emergency Approach and Landing
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 KZPH