The Bounce and the Ditch
Misjudged flare, a bounced landing, and directional control loss in a Piper Archer — recovery or excursion?
The scenario
Departing Clearwater Air Park (KCLW), Clearwater, FL — Runway 16, a 4,108 ft asphalt runway. Elevation 71 ft MSL. You are on a local VFR flight in a Piper Archer (PA-28-181), solo, full fuel, within limits. KCLW is non-towered Class G airspace; you are operating on CTAF (122.8). Overlying Class B (Tampa) begins at 3,000 MSL; you are planning to stay below 2,500 ft MSL.
It is a warm Florida afternoon: OAT 27°C, altimeter 29.94, visibility 10 SM. Winds are from 180° at 12 knots, gusting to 18 knots. Runway 16 is aligned 155°; the wind is roughly a 25° crosswind, gusting. Not extreme, but present. You have 200 hours total time, 80 hours in the Archer. You are current and comfortable with crosswind landings.
You have been flying for 1.5 hours. You are returning to KCLW for a full-stop landing. You have been monitoring the CTAF; no other traffic is reported. You are on a 3-mile final approach to Runway 16, descending through 500 ft AGL, airspeed 80 KIAS, flaps 20°. The approach feels stable — you are on glide slope, on speed, on centerline.
Then, at 200 ft AGL, the wind gusts. Your airspeed jumps to 85 KIAS, then drops back to 75 KIAS. The airplane pitches up, then down. You correct with the elevator, but the corrections feel large. The runway is ahead. You are committed to the landing.
Aircraft: Piper Archer PA-28-181, carbureted Lycoming O-360, 180 hp, fixed-pitch prop, fixed gear, LEFT/RIGHT fuel selector (no BOTH position). Steam/vacuum panel. Best glide: 76 KIAS. Vref (approach speed): 66 KIAS. Vs0 (stall, landing): 45 KIAS. Vfe (max flap extended, full 40°): 102 KIAS.
Pilot: you — Private pilot, 200 hours total, 80 hours Archer. Current. You have landed the Archer at KCLW a dozen times. You know the runway. The crosswind is manageable. But the wind shear at 200 ft caught you off-guard, and your approach is now less stable than it was.
- {'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 enter the decision tree — what do you know about landing the Piper Archer in crosswind conditions? (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, veered off the runway, and struck terrain. The pilot was not seriously injured, but the airplane sustained substantial damage.
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 nose gear was destroyed; the firewall was cracked.
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 student pilot's misjudged flare, resulting in a stall and hard landing, and his failure to maintain directional control during the landing rollout. The airplane landed hard, veered off the runway, and struck a ditch. The landing gear was damaged.
The common thread: the Piper Archer is a heavier, faster airplane than a Warrior. It carries more landing energy. A misjudged flare floats the airplane farther down the runway. A bounced landing, if not immediately aborted with a go-around, results in a hard second touchdown and often a directional control loss. The nose gear is particularly vulnerable — hard landings and crabbed touchdowns can collapse it or crack the firewall.
All three real accidents cited above occurred at other airports — NOT at Clearwater Air Park (KCLW). However, KCLW's dominant accident pattern includes HARD_LANDING (11.1%), GEAR_UP_LANDING (18.5%), and LOSS_OF_CONTROL_INFLIGHT (18.5%) — the same failure modes. The scenario is localized to KCLW to make the off-field environment real: Runway 16's climb-out environment is dense development (poor forced-landing options); Runway 34's climb-out environment is low-density development and parks (slightly better but still poor). A forced landing off either runway end is difficult.
The lesson: in the Piper Archer, a stable approach and a smooth flare are not optional. Crosswind gusts at low altitude can destabilize the approach. The correct response to a destabilized approach is a go-around, not a commitment to land. If the airplane bounces, the correct response is an immediate go-around, not an attempt to land from the bounce. Hard landings and bounced landings are the leading cause of nose-gear damage and firewall cracks in the Archer.
Key lesson — The Piper Archer is heavier and faster than a Warrior — it carries more landing energy. A misjudged flare floats the airplane farther down the runway. A bounced landing, if not immediately aborted with a go-around, results in a hard second touchdown and often a directional control loss. Maintain a stable approach at Vref (66 KIAS) with full flaps. If the approach becomes unstable — due to windshear, gusts, or a misjudged flare — go around. Do not attempt to land from a bounce. The nose gear and firewall are vulnerable to hard landings and crabbed touchdowns.
Debrief — teaching points
The Archer carries more landing energy than a Warrior — flare planning must account for this.
The Piper Archer is a 180 hp, low-wing airplane with a gross weight of 2,550 lbs. It is heavier and faster than a Warrior. At landing, this means more kinetic energy. A misjudged flare — too high, too late, or too gentle — results in a longer float and a longer landing distance. An early flare in the Archer floats the airplane 500–1,000 ft farther down the runway than in a Warrior. Plan your flare to begin at 20 ft AGL, not 30 ft. Aim for a touchdown at 45 KIAS (Vs0), not 50 KIAS.
Crosswind gusts at low altitude can destabilize the approach — the correct response is a go-around.
Wind shear and gusts at 200 ft AGL are common in Florida. A gust can jump your airspeed 5–10 KIAS, then drop it back. If the approach becomes unstable — airspeed oscillating, pitch oscillating, or directional control uncertain — go around. Do not commit to a landing from an unstable approach. The cost of a go-around is a few minutes and a few gallons of fuel. The cost of a hard landing is damage to the airplane and risk to you.
A bounced landing must be aborted immediately with a go-around — do NOT attempt to land from a bounce.
If the main gear leaves the runway after touchdown (a bounce), the correct response is immediate: apply full power, retract flaps to 0°, and climb to pattern altitude. Do not reduce power and try to land from the bounce. A second touchdown from a bounce is always harder than the first, and it often results in a directional control loss. The NTSB LAX08CA199 case is the classic example: student bounced, tried to land from the bounce, veered left, struck a ditch, collapsed the nose gear, and cracked the firewall.
Crabbed touchdowns load the landing gear at an angle — manage the crab correction as the main gear touches.
In a crosswind landing, the Archer is crabbed (nose into the wind) until touchdown. As the main gear touches, you must apply aileron and rudder to align the fuselage with the runway. If you hesitate on this correction, the landing gear is loaded at an angle, and the airplane will veer. The landing becomes rough and the directional control is uncertain. Practice the crab-correction timing in calm conditions so it becomes automatic.
The Archer's nose gear is vulnerable to hard landings and firewall cracks — post-landing inspection is mandatory after any hard landing.
Hard landings in the Archer can result in nose-gear collapse or firewall cracks. If you land hard (main gear hits with significant impact, nose-high attitude), do not assume the airplane is fine. Conduct a thorough post-landing inspection: check the nose gear for damage, check the firewall for cracks, and check the landing gear for any signs of bending or twisting. If you see any damage, do not fly the airplane again until a mechanic has inspected it.
Built from the real accident record
Scenario built from NTSB ERA10CA473 (2010 PA-28-181 windshear/stall/hard landing), LAX08CA199 (2008 PA-28-181 bounced landing/directional control loss), and LAX04CA289 (2004 PA-28-181 misjudged flare/hard landing). All real events occurred at other airports — NOT at KCLW. Localized to Clearwater Air Park to reflect its dominant accident pattern (HARD_LANDING 11.1%, GEAR_UP_LANDING 18.5%, LOSS_OF_CONTROL_INFLIGHT 18.5%).
NTSB reports: ERA10CA473 · LAX08CA199 · LAX04CA289
ACS tasks: PA.II.D — Approach and Landing · PA.II.E — Go-Around / Rejected 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 KCLW