Float and Overshoot at Clearwater Air Park
Excess approach energy in a Piper Archer, a short runway, and dense development off both ends — the decision to go around must come early
The scenario
Departing Clearwater Air Park (KCLW), Clearwater, FL — Runway 16, a 4,108 ft asphalt strip. Elevation 71 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 August: OAT 32°C, dew point 24°C, altimeter 29.91. Scattered clouds at 3,500 ft, visibility 10 SM. Density altitude at KCLW is approximately 2,100 ft — the Archer will climb and land as if the field were 2,100 ft higher than its true elevation of 71 ft. The runway is 4,108 ft; in high-DA conditions, that is workable but not generous.
You have been flying the Archer for 45 hours. You are current and proficient in the airplane, but you have not logged many landings in high-density-altitude conditions. You are familiar with KCLW — it is your home field.
You are on downwind for Runway 16, 1,200 ft AGL, 90 KIAS, flaps 10°. The wind is 160° at 8 kt — roughly aligned with Runway 16 (true heading 155°), a slight crosswind from the left. The tower is not active; KCLW is Class G, non-towered. You are monitoring CTAF (122.8).
Off Runway 16's departure end (heading 155°), the off-field environment is dense development — low-density residential, medium development, and scattered commercial. There is no open field, no water, no alternate landing surface. Off Runway 34's opposite end, the environment is similar: low-density development, medium development, and open developed areas (parks and large parking lots). A runway excursion off either end at KCLW ends in developed terrain.
You are cleared to land (self-clearing on CTAF). You turn base.
- {'label': 'Field', 'value': 'KCLW · Clearwater Air Park'}
- {'label': 'Runways', 'value': '16/34'}
- {'label': 'Elevation', 'value': '71 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-181'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
Before we get into the decision tree — what do you already know about landing the Piper Archer in high-density-altitude conditions? (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 scenario: excess airspeed on approach → float → bounce → loss of directional control → runway 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 probable cause: the pilot did not go around when the approach was unstable; instead, he continued and overran the runway into obstacles.
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 probable cause: a misjudged flare (late flare) resulted in a hard landing and a bounce; the student then failed to maintain directional control during recovery.
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 probable cause: the pilot's loss of directional control while landing on a wet runway, which resulted in a runway excursion and collision with a tree. The scenario: fast approach → hard landing → loss of directional control → collision with obstacles.
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: the pilot's inadequate compensation for crosswind conditions, which resulted in a hard landing and loss of directional control.
NTSB CEN23LA345 (2023): A Piper PA-28-181 on a student solo cross-country flight experienced fuel exhaustion during approach to an alternate airport. The engine lost power during approach, resulting in a forced landing with runway overrun. The probable cause: the student pilot's improper fuel management and failure to visually verify fuel quantity before departure.
The consistent thread across these accidents: the Piper Archer is a heavier, faster airplane than a Warrior. It carries more energy on approach. An unstable approach at 500 ft AGL — high, fast, or both — is not a salvage situation; it is a go-around. A late touchdown in high-DA conditions consumes runway. A bounce after a hard landing can result in loss of directional control. The off-field environment at KCLW is dense development off both runway ends — no alternate landing surface. A runway excursion off either end results in a collision with obstacles.
Real accidents cited above occurred at other airports and in other conditions — NOT at KCLW. KCLW has its own accident history (FORCED_LANDING 22.2%, LOSS_OF_CONTROL_INFLIGHT 18.5%, GEAR_UP_LANDING 18.5%, HARD_LANDING 11.1%, FUEL_STARVATION 11.1%), but these specific NTSB cases happened elsewhere. The scenario is localized to KCLW to make the runway length and off-field environment real and consequential for you as a student here.
Key lesson — The Piper Archer is a heavier, faster airplane than a Warrior. It carries more energy on approach and floats more readily. In high-density-altitude conditions at a 4,108 ft runway, an unstable approach at 500 ft AGL — high, fast, or both — is a go-around, not a salvage attempt. A late touchdown consumes runway. A bounce after a hard landing can result in loss of directional control. Off Runway 16 at KCLW, the off-field environment is dense development — no alternate landing surface. The correct decision is made at 500 ft AGL: stable and on profile, continue; unstable, go around.
Debrief — teaching points
Density altitude erodes runway performance in the Piper Archer.
At KCLW on a warm Florida afternoon, density altitude is approximately 2,100 ft. The Archer will land as if the field were 2,100 ft higher than its true elevation of 71 ft. A 4,108 ft runway is adequate in standard conditions but becomes marginal in high DA. A long float or a bounced landing can consume the entire runway. Know the density altitude before you depart. Plan for a longer landing distance. If the approach is unstable, go around — do not attempt to salvage it.
Approach speed (Vref) for the Archer is 66 KIAS — exceeding this speed increases landing distance significantly.
The Piper Archer's approach speed (Vref) is 66 KIAS. Exceeding this speed on final approach increases landing distance. At 75 KIAS instead of 66 KIAS, the airplane will float — it will not touch down until airspeed decays, eating runway. In high-DA conditions, every knot of excess airspeed matters. Plan to cross the threshold at 66 KIAS. If you are faster, go around.
Stability at 500 ft AGL is the decision point.
At 500 ft AGL, assess your approach: altitude, airspeed, descent rate, and directional control. If the approach is stable — on speed, on glide path, and in control — continue. If the approach is unstable — high, fast, low, slow, or drifting — go around. A go-around at 500 ft AGL is safe and correct. A go-around at 200 ft AGL is marginal. Do not wait. The decision is made at 500 ft AGL.
A hard landing or a bounce after touchdown is a runway excursion risk.
A hard landing in the Archer can result in a bounce — the nose gear compresses and the airplane lifts off again. If you bounce, do not attempt to land again; go around. A bounced landing followed by a second touchdown late in the runway, combined with excess float, can result in a runway excursion. The NTSB cases (LAX08CA199, LAX04CA289) show the sequence: excess airspeed → float → bounce → loss of directional control → runway excursion. The correct response to a bounce is a go-around.
Off-field environment at KCLW is dense development — no alternate landing surface.
Off Runway 16's departure end (heading 155°), the off-field environment is dense development — low-density residential, medium development, and scattered commercial. Off Runway 34's opposite end, the environment is similar: low-density development, medium development, and open developed areas. There is no open field, no water, no alternate landing surface. A runway excursion off either end results in a collision with obstacles. The runway is your only landing surface. Land on it, or go around.
Crosswind compensation must be active throughout the approach and rollout.
The wind at KCLW is 160° at 8 kt — a slight crosswind from the left for Runway 16 (true heading 155°). Crosswind compensation must be active throughout the approach and rollout. The Archer is susceptible to loss of directional control in crosswind conditions, especially on landing. Maintain a crab or slip as needed to keep the airplane aligned with the runway. During rollout, use gentle rudder input to maintain directional control. The NTSB cases (ERA10CA473, ERA10FA020) show the consequence of inadequate crosswind compensation: loss of directional control and runway excursion.
A forward slip is a tool for losing altitude and drag without increasing airspeed.
If you are floating down the runway at excess airspeed, a forward slip — dropping a wing and applying opposite rudder — increases drag and loses altitude without increasing airspeed. This is a valid technique in the Archer to manage a float and land earlier on the runway. However, a forward slip should be planned and executed deliberately, not as a last-minute salvage attempt. The better decision is a go-around at 500 ft AGL when the approach is unstable.
Built from the real accident record
Scenario built from NTSB ERA10CA473 (2010 PA-28-181 windshear / hard landing / excursion), LAX08CA199 (2008 PA-28-181 excessive airspeed / bounced landing / runway excursion), CHI05CA208 (2005 PA-28-181 delayed go-around decision / runway overrun), LAX04CA289 (2004 PA-28-181 misjudged flare / hard landing / excursion), ERA10FA020 (2009 PA-28-181 loss of directional control / wet runway / tree strike), and CEN23LA345 (2023 PA-28-181 fuel exhaustion / forced landing / overrun). Localized to KCLW.
NTSB reports: ERA10CA473 · LAX08CA199 · CHI05CA208 · LAX04CA289 · ERA10FA020 · CEN23LA345
ACS tasks: PA.I.F — Weather Information · PA.III.A — Preflight Preparation · PA.III.B — Preflight Procedures · PA.IV.A — Normal Takeoff and Climb · PA.V.A — Normal Approach and Landing · PA.V.B — Forward Slip to a Landing · PA.V.C — Go-Around / Rejected Landing · PA.IX.C — Emergency Approach and Landing
Relevant FARs: §91.3 · §91.13 · §91.103
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 KCLW