Fast and Floating at Venice
Excess approach energy, a bounced landing, and directional control — the Archer's weight and momentum demand precision on short final
The scenario
Departing Venice Municipal Airport (KVNC), Venice, FL — Runway 22, a 5,000 ft asphalt runway on a hot, humid afternoon. Elevation 18 ft MSL. You are on a local VFR flight in a Piper Archer (PA-28-181), solo, full fuel (48 gallons usable), within weight and balance limits.
It is late July, 1400 local. OAT 32°C, dew point 24°C, altimeter 29.88. Density altitude approximately 1,800 ft — the Archer will perform as if it is 1,800 ft higher than the field elevation. Scattered clouds at 3,500 ft, visibility 10 SM, light and variable winds with a 6-knot crosswind favoring Runway 22. KVNC is non-towered Class G airspace; you are on CTAF (122.8).
You have completed a local area flight and are returning to KVNC for landing. You are on a 3-mile final for Runway 22 (true heading 225°), at 1,200 ft AGL, descending at 500 fpm. The runway is ahead, clearly visible. You have been flying the Archer for 60 hours; you are current and proficient, but this is your first landing in high density altitude conditions.
Aircraft: Piper PA-28-181 Archer. Lycoming O-360-A, 180 hp, carbureted. Fixed-pitch prop, fixed gear, steam panel. Fuel selector on LEFT tank (you switched from RIGHT on downwind). Flaps are at 10°. You are configured for approach.
Pilot: You — a Private pilot, 180 hours total time, 60 hours in the Archer. You are current and have been flying consistently. You have not landed at a high-density-altitude field before. Your CFI is not on board; this is a solo flight.
- {'label': 'Field', 'value': 'KVNC · Venice'}
- {'label': 'Runways', 'value': '4/22 · 13/31'}
- {'label': 'Elevation', 'value': '18 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-181'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we get into the decision tree — what do you know about landing the Archer in high density altitude? (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 at a destination airport. The student delayed flap extension and landed with excessive airspeed. The aircraft bounced on touchdown, veered left during 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 survived.
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.
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.
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.
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 was the pilot's loss of directional control while landing on a wet runway.
The real accidents cited above occurred at other airports — NOT at Venice Municipal Airport (KVNC). KVNC's dominant accident pattern is LOSS_OF_CONTROL_INFLIGHT (24.4%), FORCED_LANDING (12.2%), SPATIAL_DISORIENTATION (12.2%), HARD_LANDING (12.2%), and LOSS_OF_CONTROL_GROUND (12.2%). The scenario is localized to KVNC to make the high-density-altitude environment and the 5,000 ft runway real and consequential for you as a student here.
The consistent thread across all these events: the Piper Archer is heavier and faster than lighter trainers. It carries more energy on approach. A fast approach (even 10–15 knots overspeed) extends landing distance significantly in high density altitude. The Archer floats if the approach is not stabilized at Vref (66 KIAS) by 500 ft AGL. A bounced landing at low altitude is a trap: attempting to recover from a bounce by reducing power and trying to land again often results in a second bounce, a hard landing, and structural damage. The correct response to a bounced landing is a go-around — immediately, without hesitation.
Key lesson — In high density altitude, the Piper Archer demands a stabilized approach at Vref (66 KIAS) by 500 ft AGL, with full flaps extended by that point. Excess airspeed on final approach extends landing distance significantly. A bounced landing is not recoverable at low altitude — go around immediately. The Archer's weight and energy mean that a fast or unstable approach will result in a long float and potential runway excursion. Density altitude erodes climb performance and increases landing distance; plan accordingly.
Debrief — teaching points
High density altitude increases landing distance significantly.
At KVNC on a hot, humid day, density altitude can reach 1,800 ft or higher. This means the Archer performs as if it is 1,800 ft higher than the field elevation. True airspeed is higher for a given indicated airspeed, which means true ground speed on landing is higher. Landing distance increases by 30–50% in high density altitude. A 5,000 ft runway that feels long in standard conditions becomes marginal in high DA. Plan conservatively: assume longer landing distances, aim for a touchdown in the first 1,500 ft of the runway, and be ready to go around if the approach is not stabilized by 500 ft AGL.
The Archer is heavier and faster than lighter trainers — it carries more energy.
The PA-28-181 weighs 2,550 lbs gross and cruises at 125 KIAS (Vno). It is not a Warrior. An overspeed of just 5–10 knots on final approach extends landing distance by 500+ feet because landing distance increases with the square of airspeed. Vref is 66 KIAS; this is not a suggestion. Reaching 66 KIAS by 500 ft AGL is mandatory. If you are 80+ KIAS at 500 ft AGL, go around. Do not try to salvage a fast approach.
Flap extension must be gradual and planned — not rushed or delayed.
Extend flaps to 10° on downwind, 25° on base, and full 40° by 500 ft AGL. This gradual extension allows the airplane to slow down progressively and gives you time to manage the pitch changes. Delaying flap extension to short final (300 ft AGL or lower) compresses the final phase and leaves no margin for error. Extending flaps too quickly can cause a sudden pitch-up that is hard to manage at low altitude. Plan the flap extension; do not improvise it.
A stabilized approach at 500 ft AGL is non-negotiable.
By 500 ft AGL, the approach must be stabilized: airspeed at or below Vref (66 KIAS), descent rate 300–400 fpm, aligned with the runway, and fully configured (flaps 40°). If any of these criteria are not met — too fast, too high, not aligned, or not fully configured — go around. A go-around at 500 ft AGL is safe and correct. Continuing an unstable approach is the path to a hard landing, a bounce, or a runway excursion.
A bounced landing is not recoverable at low altitude — go around immediately.
If the main gear bounces off the runway (the airplane leaves the surface after the initial touchdown), do not attempt to recover by reducing power and trying to land again. This almost always results in a second bounce, a hard landing, and structural damage (nose gear collapse, firewall cracking). The correct response is immediate: advance the throttle, retract flaps to 10°, and climb. A go-around from a bounced landing is the safest outcome. The NTSB LAX08CA199 case (2008 PA-28-181) and LAX04CA289 (2004 PA-28-181) both show the danger of attempting to recover from a bounce.
Crosswind control requires active coordination throughout the approach and landing.
A 6-knot crosswind is within limits for the Archer, but it requires active rudder and aileron coordination. During the approach, maintain alignment with the runway using coordinated aileron and rudder inputs. During the flare and touchdown, use rudder to keep the nose aligned and aileron to keep the wings level. During the rollout, maintain directional control with rudder and differential braking if needed. Crosswind control is not passive; it is active and continuous.
Built from the real accident record
Scenario built from NTSB ERA10CA473 (2010 PA-28-181 windshear/stall/hard landing), LAX08CA199 (2008 PA-28-181 excessive airspeed/bounced landing/runway excursion), CHI05CA208 (2005 PA-28-181 overrun/utility pole), LAX04CA289 (2004 PA-28-181 hard landing/loss of directional control), ERA10FA020 (2009 PA-28-181 wet runway/tree collision), and CEN23LA345 (2023 PA-28-181 fuel exhaustion/landing overrun). Anonymized and localized to KVNC.
NTSB reports: ERA10CA473 · LAX08CA199 · CHI05CA208 · LAX04CA289 · ERA10FA020 · CEN23LA345
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.III.D — Approach and Landing · PA.I.H — Human Factors · PA.III.C — Go-Around / Rejected 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 KVNC