Bounce and Recover
A misjudged flare in the Piper Archer — energy management, directional control, and the decision to go around
The scenario
Departing Tampa North Aero Park Airport (X39), Tampa, FL — Runway 14, a 3,541-foot asphalt strip at 68 ft MSL. Elevation is negligible; density altitude is roughly field elevation. You are on approach to land after a 45-minute local flight in the Piper Archer PA-28-181.
Weather: VFR, scattered clouds at 3,500 ft, visibility 10 SM. Wind is reported as 160° at 12 knots — a crosswind from the left on Runway 14 (true heading 141°). The ATIS mentions light wind shear on approach. Temperature 26°C, dew point 18°C. No precipitation, no icing.
You are on a 3-mile final approach to Runway 14, descending through 800 ft AGL. Airspeed is 90 KIAS — slightly fast for the Archer's approach speed of 66 KIAS (Vref), but you are planning to bleed off speed on short final. Flaps are at 20°. The runway is in sight, well-aligned. You feel comfortable with the approach.
Aircraft: Piper Archer PA-28-181, solo, within weight and balance limits. Fuel is adequate. The airplane is airworthy; nothing was written up. Lycoming O-360-A carbureted engine, fixed-pitch prop, fixed gear, steam panel.
Pilot: You — a Private pilot, current, roughly 180 hours total. You have about 40 hours in the Archer. This is a routine local flight; you have landed at X39 several times before. You are not fatigued, not distracted. You are on a normal approach.
- {'label': 'Field', 'value': 'X39 · Tampa North Aero Park'}
- {'label': 'Runways', 'value': '14/32'}
- {'label': 'Elevation', 'value': '68 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-181'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we get into the decision tree — what do you already know about landing the Piper Archer in a crosswind? (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 led to loss of directional control during the landing rollout. The airplane departed the runway and came to rest off the pavement. The probable cause was the pilot's inadequate compensation for crosswind conditions which resulted in a hard landing and loss of directional control.
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 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.
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 was the pilot's misjudged flare, resulting in a stall and hard landing, and his failure to maintain directional control. The pilot's improper recovery from a bounced landing is a contributing factor.
The common thread across all three accidents: a fast or unstable approach in a crosswind, followed by a hard landing or bounce, followed by loss of directional control during the rollout. The Piper Archer is heavier and faster than a Cessna 172 — it carries more landing energy, and a misjudged flare will float longer and land harder. The crosswind compounds the problem: directional control is marginal during the rollout, and a hard landing makes it worse.
Tampa North Aero Park Airport (X39) is a non-towered, Class G field with a 3,541-foot runway. The off-field environment off both runway ends is poor: medium development, low-density development, and wooded wetland. A runway excursion at X39 is not a water ditching (as it would be at a coastal field), but it is a collision with terrain, trees, or structures. The accident sequence is the same: hard landing, loss of directional control, departure from the runway.
These real accidents occurred at other airports and in other circumstances — NOT at X39. But the accident pattern (hard landing, crosswind, loss of directional control) is the dominant pattern at X39 itself (27.3% loss of control inflight, 18.2% loss of control ground, 9.1% hard landing). The scenario is localized to X39 to make the field's own accident history real and consequential for you as a student here.
Key lesson — The Piper Archer is heavier and faster than a Cessna 172 — it carries more landing energy. A fast approach (above Vref 66 KIAS) in a crosswind is a setup for a long float, a hard landing, and loss of directional control during the rollout. The correct sequence: (1) Reduce speed to Vref (66 KIAS) before short final. (2) Flare smoothly, not aggressively. (3) Maintain active rudder correction throughout the rollout to keep the nose aligned with the runway. (4) If the approach is unstable or fast at 500 ft AGL, go around — do not try to salvage a bad approach. A bounced landing is not a second chance to land; it is a signal to go around and reset.
Debrief — teaching points
The Archer carries more landing energy than a Cessna 172 — speed management is critical.
The Piper Archer PA-28-181 is heavier (2,550 lbs gross) and faster than a Cessna 172. It carries significantly more kinetic energy on approach. A 10-knot overspeed on approach (76 KIAS instead of 66 KIAS Vref) means the Archer will float much longer down the runway and land much harder. The energy is proportional to the square of velocity — small speed errors produce large energy errors. Reduce speed to Vref (66 KIAS) before short final, not during the flare.
Crosswind landings require active rudder control throughout the flare and rollout.
A 12-knot crosswind is within the Archer's demonstrated capability, but it requires active, continuous rudder input. During the flare, the crosswind wants to push the nose off the runway. You must apply rudder to keep the nose aligned. During the rollout, especially after a hard landing, the nose gear may not be fully aligned, and the crosswind will push the nose further off. Aggressive rudder and braking are required. If directional control is lost, the airplane will leave the runway.
A hard landing or bounce is a signal to go around — not a second chance to land.
If the main gear touches down hard or the airplane bounces, the correct response is to apply full power, raise flaps to 0°, and establish a climb at Vy (76 KIAS). Do not try to land again from the bounce. A bounced landing means the approach was unstable or fast; a second attempt from the bounce will be even worse. Go around, reset the situation, and try again with a stable, slower approach. The NTSB LAX08CA199 and LAX04CA289 accidents both involved improper recovery from a bounced landing — the pilots tried to land again instead of going around.
Flare technique matters: smooth and shallow, not aggressive.
The correct flare in the Archer is smooth and shallow — reduce power gradually, hold the nose up gently, and let the airplane settle onto the runway at the slowest possible speed. An aggressive flare (pulling the nose up hard) will cause the airspeed to bleed off rapidly, and the airplane will sink hard. A shallow flare (keeping the nose lower) will result in a longer float, but the touchdown will be softer. The goal is to touch down at or just above Vs0 (45 KIAS stall speed landing), not at 75+ KIAS.
Go-around decisions must be made early — by 500 ft AGL — before energy state makes recovery impossible.
If the approach is unstable, fast, or poorly aligned at 500 ft AGL, declare a go-around. At 500 ft AGL in the Archer, you have enough altitude and airspeed to climb away safely and return to pattern altitude. Below 300 ft AGL, a go-around becomes marginal — the airplane may not have enough energy to clear obstacles or climb back to pattern altitude. Make the go-around decision early, when you have options. A go-around is not a failure; it is a sign of good judgment.
Built from the real accident record
Scenario built from NTSB ERA10CA473 (2010 PA-28-181 hard landing / windshear), LAX08CA199 (2008 PA-28-181 bounced landing / runway excursion), and LAX04CA289 (2004 PA-28-181 misjudged flare / hard landing). Anonymized and localized to X39 (Tampa North Aero Park Airport).
NTSB reports: ERA10CA473 · LAX08CA199 · LAX04CA289
ACS tasks: PA.II.J — Approach and Landing · PA.II.K — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.II.E — Slow Flight, Stalls, and Spins
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 X39