Float and Bounce at Zephyrhills
Excess approach energy in a Piper Archer — the runway is shorter than you think, and the decision to go around comes late
The scenario
Departing Zephyrhills Municipal Airport (KZPH), Zephyrhills, FL — Runway 19, a 5,072 ft asphalt runway. Elevation 90 ft MSL. You are on a local VFR flight in a Piper Archer PA-28-181, solo, full fuel, within limits. The airplane is airworthy; nothing was written up.
It is a warm Florida afternoon in late July: OAT 32°C, dew point 24°C, altimeter 29.91. Scattered clouds at 3,500 ft, visibility 10 SM. The wind is from 180° at 8 knots — a light headwind on Runway 19, but a light crosswind component (roughly 5 knots from the right). Density altitude is approximately 1,800 ft — the Archer will climb and perform as if the field elevation is 1,800 ft, not 90 ft. This is not a high-altitude airport, but the heat erodes performance.
You have been flying the Archer for about 40 hours total in this type. You are a Private pilot, current, with roughly 250 hours total. You are comfortable with the airplane but not deeply experienced. You have not flown into Zephyrhills before — it is a local practice flight, but the field is unfamiliar.
You are on a 3-mile final approach to Runway 19, 1,200 ft AGL, descending at 76 KIAS (Vy, best rate of climb — your approach speed). Flaps are at 20°. The runway is in sight, looks long and clear. You are stable on the glide slope. The wind is light. Everything feels normal.
Pilot: you — a Private pilot, current, roughly 250 hours total, 40 hours in the Archer. This is your first landing at KZPH. You did not brief the runway length or the off-field environment before descent. You did not compute a landing distance or check density altitude. You are flying by feel.
- {'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 know about landing the Piper Archer at a warm, unfamiliar field? (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 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. The excess airspeed on approach led directly to the bounce, and the loss of directional control during recovery led to the excursion.
NTSB CHI05CA208 (2005): A Piper PA-28-181 on a personal flight overran a grass runway and struck a utility pole during landing at Bird Field Airport, Missouri. The accident resulted from the pilot's delayed decision-making, excessive approach airspeed, and failure to execute a go-around. Contributing factors included high density altitude and obstacles near the runway. The pilot continued a fast, unstable approach when a go-around would have been the correct decision.
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 accident was attributed to inadequate compensation for crosswind conditions. The pilot did not maintain directional control during the landing and rollout.
NTSB LAX04CA289 (2004): A Piper PA-28-181 on a student instructional flight experienced a hard landing and runway excursion at Scottsdale Airport. The accident resulted from the student pilot's misjudged landing flare and failure to maintain directional control during the landing rollout. The student did not recognize the float and did not execute a go-around.
NTSB ERA10FA020 (2009, FATAL): A Piper PA-28-181 on a personal local flight landed fast and hard on a wet turf runway at Oliver Springs Airport, lost directional control during rollout, and collided with trees. The accident was attributed to the pilot's loss of directional control while landing on a wet runway. The pilot did not maintain directional control and did not execute a go-around when the approach became unstable.
NTSB CEN23LA345 (2023): A Piper PA-28 on a student solo cross-country flight experienced fuel exhaustion during approach to an alternate airport after the student pilot failed to visually verify fuel quantity before departure. The engine lost power during approach, resulting in a forced landing with runway overrun. This accident highlights the importance of fuel management and the decision to go around when the approach is unstable.
The consistent thread across all these accidents: the Piper Archer is heavier and faster than trainers like the Warrior. Excess approach energy — from flying too fast, delaying flap extension, or failing to reduce speed — leads to floating, late touchdown, and runway excursion. The decision to go around when the approach is unstable at low altitude is the critical intervention. At KZPH, Runway 19 is 5,072 ft — long by general-aviation standards, but not infinite. Density altitude at 1,800 ft erodes the Archer's performance. A late touchdown leaves less runway for rollout and braking. The off-field environment off Runway 19's departure end is marginal — open developed areas, parks, and evergreen forest. A runway excursion into that environment is survivable but damaging.
The real accidents cited above occurred at other airports and in other conditions — NOT at KZPH. The scenario is localized to KZPH to make the runway length, density altitude, and off-field environment real and consequential for you as a student here.
Key lesson — The Piper Archer floats. Excess approach energy — flying above Vref (66 KIAS), delaying flap extension, or failing to reduce speed — means the airplane will float down the runway, consuming runway length and leaving less distance for rollout and braking. At KZPH, with density altitude at 1,800 ft and a 5,072 ft runway, a late touchdown is survivable but marginal. The critical decision is recognizing when the approach is unstable (too fast, too high, floating) at low altitude and executing a go-around. A go-around is not a failure — it is the correct decision when the approach is unstable below 500 ft AGL. Crosswind compensation requires active, smooth rudder and aileron input throughout the landing and rollout. Overcontrol and loss of directional control are the most common causes of runway excursions in the Archer.
Debrief — teaching points
The Archer is heavier and faster than a Warrior — approach energy is higher.
The Piper Archer PA-28-181 has 180 hp and weighs 2,550 lbs at gross. The Warrior PA-28-161 has 160 hp and weighs 2,325 lbs. The Archer carries more energy into the landing. Excess approach airspeed (flying above Vref of 66 KIAS) means the airplane will float — it will not touch down immediately when you flare. The float consumes runway length. At a 5,072 ft runway like Runway 19 at KZPH, a float of 500 ft is manageable. A float of 1,000 ft leaves you marginal. Know the Archer's approach characteristics and respect the energy it carries.
Vref is 66 KIAS — this is the target speed for short final, not 76 KIAS (Vy).
Vy (best rate of climb) is 76 KIAS. Vref (approach speed) is 66 KIAS. These are different speeds for different phases. On approach, reduce to 66 KIAS and configure the airplane with full flaps (40°). This is the correct landing configuration. Flying the approach at 76 KIAS means flying above approach speed — the airplane will float. Reduce to 66 KIAS before the flare.
Density altitude erodes performance — at 32°C OAT, the Archer performs as if the field is 1,800 ft high.
Density altitude is the effective altitude the airplane performs at, given temperature and pressure. At KZPH (90 ft MSL) with OAT 32°C and altimeter 29.91, density altitude is roughly 1,800 ft. The Archer's landing distance increases by roughly 20–30% in these conditions. A landing distance of 1,200 ft in standard conditions becomes 1,500–1,600 ft at density altitude 1,800 ft. Know the density altitude before descent. Compute landing distance using the POH and the actual density altitude. Do not assume the field elevation is the performance altitude.
If the approach is unstable at 500 ft AGL or below, execute a go-around — do not attempt recovery.
An unstable approach is one that is too fast, too high, or floating. If you recognize instability at 500 ft AGL or below, the correct decision is a go-around: reduce power, raise flaps to 20°, climb to 500 ft AGL, and set up another approach. A go-around is not a failure — it is the correct decision when the approach is unstable at low altitude. Attempting to recover from an unstable approach at low altitude is the path to a hard landing, bounce, or runway excursion. The NTSB data is clear: go-around is the intervention that prevents accidents.
Crosswind compensation requires active, smooth rudder and aileron input throughout the landing and rollout.
A 5-knot crosswind on a 100 ft wide runway is manageable, but it requires active control. Use aileron to keep the wings level and rudder to keep the nose aligned with the runway. During rollout, a crosswind gust can lift a wing and cause drift. Correct with smooth, coordinated rudder and aileron — not aggressive overcontrol. Overcontrol leads to veering and loss of directional control. The Archer's fixed gear and low-wing design make crosswind control critical. Practice crosswind landings and develop the muscle memory for smooth, coordinated control.
Runway 19 at KZPH is 5,072 ft — long, but not infinite. Off-field environment is marginal.
Runway 19 at KZPH is 5,072 ft asphalt. This is a long runway by general-aviation standards. However, a late touchdown at 3,200 ft leaves only 1,872 ft for rollout and braking. In density altitude conditions, the Archer's landing distance is 1,500–1,600 ft. A late touchdown leaves minimal margin. Off Runway 19's departure end (heading 180°), the off-field environment is marginal — mostly open developed areas, parks, and evergreen forest. A runway excursion into that environment is survivable but damaging. Land where the airplane wants to land, and use the remaining runway for rollout and braking. Do not stretch the approach to land farther down the runway.
Brief the runway length and off-field environment before descent — do not fly by feel.
Before descent, brief the runway length, the off-field environment, and the landing distance required. Compute density altitude and landing distance using the POH. Know where you are going to land and what is off the runway ends. Do not fly by feel. The scenario brief mentioned that you did not brief the runway length or compute landing distance — you flew by feel. This is the path to a late touchdown and a marginal landing. Brief the runway before descent.
Built from the real accident record
Scenario built from NTSB ERA10CA473 (2010 PA-28-181 crosswind stall/hard landing), LAX08CA199 (2008 PA-28-181 bounced landing / runway excursion), CHI05CA208 (2005 PA-28-181 overrun / obstacle strike), LAX04CA289 (2004 PA-28-181 misjudged flare / loss of control), ERA10FA020 (2009 PA-28-181 wet runway loss of control / tree strike), and CEN23LA345 (2023 PA-28-181 fuel exhaustion / overrun). Localized to KZPH.
NTSB reports: ERA10CA473 · LAX08CA199 · CHI05CA208 · LAX04CA289 · ERA10FA020 · CEN23LA345
ACS tasks: PA.II.F — Landing · PA.II.E — Approach and Landing · PA.I.F — Weather Information · PA.I.H — Human Factors · PA.IX.C — Emergency Approach and Landing
Relevant FARs: §91.3 · §91.13 · §91.121
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