Sink and Bounce at Venice
A misjudged flare in a Piper Archer on short final — the recovery decision happens in milliseconds
The scenario
Departing Venice Municipal Airport (KVNC), Venice, FL — Runway 22, a 5,000 ft asphalt runway aligned 225° true. Elevation 18 ft MSL. You are on a local VFR flight in a Piper Archer PA-28-181, solo, within limits. The field is non-towered; you are operating on CTAF (122.8). No nearby Class C or Class D airspace is active on your route.
Weather: VFR, scattered clouds at 3,500 ft, visibility 10 SM. Wind is reported from 180° at 12 knots, gusting to 18 knots. Runway 22 is aligned 225° true — the wind is a 45° crosswind from the left, roughly 8–9 knots of crosswind component. This is within the Archer's demonstrated crosswind capability (roughly 12 knots in the POH), but it is a real crosswind, not a calm-wind landing.
You have been flying the Archer for 8 hours dual and 12 hours solo — 20 hours total in type. You are current and proficient in calm-wind landings. Crosswind landings are newer to you; you have done three or four with your CFI. This is your first solo crosswind landing in the Archer.
You are on a 3-mile final to Runway 22, descending through 500 ft AGL. Airspeed is 70 KIAS (slightly above Vref of 66 KIAS — acceptable). Flaps are full (40°). You are configured for landing. The wind is steady from the left. You are holding a slight crab to maintain runway alignment.
At 200 ft AGL, you begin the flare. The Archer is a heavier, faster airplane than the Cessna 172 you trained in — it carries more energy. The flare needs to be smooth and deliberate. The runway is ahead, the crosswind is steady, and you are committed to the landing.
- {'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 crosswind landings 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 pilot's inadequate compensation for crosswind conditions and failure to go around from an unstable approach led to the accident. The airplane veered off the runway and struck terrain.
NTSB LAX08CA199 (2008): A Piper PA-28-181 student pilot on solo flight was vectored to Runway 22R 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 student did not go around after the bounce; instead, tried to salvage the landing.
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 pilot's improper recovery from a bounced landing is a contributing factor. The airplane veered off the runway.
The common thread across all three accidents: the pilot misjudged the flare, landed hard, the airplane bounced, and the pilot tried to salvage the bounce instead of going around. In each case, the bounce led to loss of directional control and a runway excursion. The Piper Archer is a heavier, faster airplane than the Cessna 172 — it carries more energy into the landing. A hard landing in the Archer is not a minor event; it stresses the nose gear, the fuselage, and the landing gear attachment points.
At KVNC, Runway 22 is 5,000 ft long — plenty of runway for a go-around. The off-field environment to the left of Runway 22 (the direction of the crosswind veer) is open grass and scattered trees — not a catastrophic off-field environment, but still a runway excursion. The real accidents cited above occurred at other airports — NOT at KVNC. However, the accident sequence — hard landing, bounce, loss of control, runway excursion — is the dominant pattern at KVNC (12.2% of accidents are hard landings; 12.2% are loss of control on the ground).
The critical decision in all three NTSB cases was at the bounce: go around, or try to salvage the landing? The pilots who tried to salvage the bounce lost directional control. The correct answer is always: go around. A bounced landing in the Archer is a signal that the approach was unstable. The recovery is not to land harder; it is to climb away and try again.
Key lesson — In the Piper Archer, a hard landing or a bounced landing is not a minor event — the airplane carries significant energy and the nose gear is vulnerable. The decision at the bounce is binary: go around (apply full power, climb, re-enter the pattern) or try to salvage the landing (reduce power, land on the second touchdown). The NTSB data is clear: trying to salvage the bounce leads to loss of directional control and runway excursion. Going around is always the safer choice. Runway 22 at KVNC is 5,000 ft long — there is plenty of runway for a go-around.
Debrief — teaching points
The Piper Archer carries more energy than lighter airplanes — the flare must be smooth and deliberate.
The Archer is a 180 hp, low-wing airplane with a gross weight of 2,550 lbs. It is heavier and faster than the Cessna 172 (2,450 lbs) and significantly heavier than a Warrior (2,325 lbs). On approach and landing, this extra weight and speed mean the airplane carries more kinetic energy. A flare that works in a 172 may not work in an Archer. The flare must be smooth, deliberate, and sustained — not abrupt. Pulling back aggressively on the yoke will over-flare the airplane and cause it to balloon (climb back up). A slow, steady back-pressure is the correct technique.
Vref is 66 KIAS — landing above this speed increases float and touchdown distance.
Vref for the PA-28-181 is 66 KIAS. This is the recommended approach speed on short final. Landing above Vref (e.g., at 70 KIAS) means the airplane will float farther down the runway before it settles. In a 5,000 ft runway with a crosswind, floating an extra 200–300 ft is not catastrophic, but it reduces margin. More importantly, landing above Vref means the descent rate at touchdown is higher (the airplane has more energy), which increases the impact force. Aim for Vref on short final; do not land above it.
A bounced landing is a signal that the approach was unstable — go around, do not try to salvage it.
If the main gear bounces on touchdown, the approach was unstable. The descent rate was too high, or the flare was misjudged, or both. The correct recovery is to apply full power, raise the flaps incrementally, and climb back to pattern altitude to try again. Trying to salvage the bounce — reducing power and landing on the second touchdown — leads to a second hard landing, which can damage the nose gear and cause loss of directional control. The NTSB data is clear: bounced-landing accidents are almost always the result of trying to salvage the bounce instead of going around. Go around. There is plenty of runway.
Crosswind landings require active rudder and aileron control — anticipate the drift and correct it smoothly.
In a crosswind, the airplane will drift downwind unless you correct for it. On final approach, use a crab angle (nose into the wind) to maintain runway alignment. As you flare, transition from the crab to a forward slip (into-wind wing down, opposite rudder) to keep the fuselage aligned with the runway while the wind drifts the airplane. This transition must be smooth and coordinated. The Archer's demonstrated crosswind capability is roughly 12 knots; an 8–9 knot crosswind is well within limits, but it requires active control. Do not relax your control inputs in the flare — the crosswind is still there.
A hard landing stresses the nose gear, fuselage, and landing gear attachment points — inspect before flying again.
The Archer's nose gear is not designed to absorb hard landings. A descent rate of 400–500 ft/min on touchdown is hard. The nose gear compresses, the fuselage experiences stress, and the landing gear attachment points are loaded. After a hard landing, the airplane must be inspected by maintenance before it flies again. Do not attempt another approach in a damaged airplane. If you suspect a hard landing, land immediately and have the airplane inspected.
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 KVNC.
NTSB reports: ERA10CA473 · LAX08CA199 · LAX04CA289
ACS tasks: PA.II.J — Slow Flight · PA.II.K — Stall Prevention · PA.III.A — Normal Landing · PA.III.B — Forward Slip · PA.III.C — Go-Around · PA.I.H — Human Factors
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