Bounce and Drift at Sarasota Bradenton
A misjudged flare in the Archer, a bounced landing, and the decision to go around — or push it down
The scenario
Departing Sarasota Bradenton International Airport (KSRQ), Sarasota/Bradenton, FL — Runway 14, on a 134° heading. Elevation 30 ft MSL. You are a Private pilot with roughly 250 hours total time, 80 hours in the Piper Archer (PA-28-181). This is a local flight — you know the field, you know the airplane, and the weather is benign.
It is a clear, calm morning in late spring: OAT 24°C, winds 080° at 6 knots, gusting to 10 knots. Runway 14 is aligned 134° true; the wind is a 6–10 knot crosswind from the left (northwest). Visibility is 10 SM. Class C airspace; tower is open and active (0600–0000 local). You are cleared to land Runway 14.
You are on a 2-mile final approach to Runway 14, 800 ft AGL, descending at 500 fpm. Airspeed is 90 KIAS — higher than ideal. You have full flaps extended (40°, Vfe 102 KIAS — you are 12 knots fast). The runway is long (9,500 ft) and straight ahead. You are not uncomfortable, but you are not in a textbook descent either.
Aircraft: Piper Archer PA-28-181, solo, within weight and balance limits. Carbureted Lycoming O-360, 180 hp, fixed-pitch prop, fixed gear, steam panel. The airplane is airworthy; nothing was written up. Best glide is 76 KIAS. Approach speed (Vref) is 66 KIAS. Stall speed in landing configuration is 45 KIAS.
Pilot: you — a Private pilot, current, 250 hours total, 80 hours in the Archer. You have landed at KSRQ a dozen times. You are familiar with the field, the runway, and the airplane. You are not fatigued, not distracted, and the weather is not a factor. This is a routine approach.
- {'label': 'Field', 'value': 'KSRQ · Sarasota Bradenton'}
- {'label': 'Runways', 'value': '4/22 · 14/32'}
- {'label': 'Elevation', 'value': '30 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 Archer in a crosswind and recovering from a bounced landing? (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 remained on the runway, but the landing was hard and the pilot's recovery was marginal.
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.
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 nose gear collapsed, and the firewall was damaged.
The consistent thread across all three accidents: the Archer is a heavier, faster airplane than a Warrior or Tomahawk. It carries more energy into the landing. A misjudged flare, a bounced landing, or an unstable approach can quickly escalate into a hard landing and loss of directional control. The Archer's nose gear is not steerable — directional control on the ground depends entirely on differential braking and rudder input. Once directional control is lost, a runway excursion is likely.
At KSRQ, Runway 14's climb-out environment (heading 134°) is dense development — not a factor on landing. But the runway itself is 9,500 feet long and straight, which can mask approach instability. A pilot who is fast, high, or unstable on final may not feel the urgency to go around because 'the runway is long.' This is a trap. The Archer's landing distance increases significantly with excess airspeed, and a bounced landing can consume runway quickly.
The real accidents cited above occurred at other airports and in other aircraft types — NOT at KSRQ. But the failure modes — misjudged flare, bounced landing, loss of directional control, nose gear collapse — are the dominant accident pattern at KSRQ itself (19.2% LOSS_OF_CONTROL_GROUND, 15.4% FORCED_LANDING, 11.5% RUNWAY_EXCURSION, 11.5% HARD_LANDING). The scenario is localized to KSRQ to make the decision points real and consequential for you as a pilot here.
The lesson: in the Archer, a stabilized approach is non-negotiable. If you are fast, high, or unstable on final, go around. A bounced landing is not a recovery opportunity — it is a signal to go around immediately. Directional control on the ground is fragile; a hard landing can compromise it. The Archer is forgiving in many ways, but the landing phase is not one of them.
Key lesson — In the Piper Archer, a stabilized approach is critical. Excess airspeed, a misjudged flare, or a bounced landing can quickly escalate into a hard landing and loss of directional control. The Archer's nose gear is not steerable — once directional control is lost, a runway excursion is likely. If the approach is unstable, fast, high, or drifting, go around. A go-around is always an option and is always safer than pushing a bad landing.
Debrief — teaching points
The Archer is heavier and faster than a Warrior — it carries more energy into the landing.
The Piper Archer (PA-28-181) is a 180-hp, 2,550-lb airplane. It is faster and heavier than a Warrior or Tomahawk. This means it floats more in the flare, it requires more runway to stop, and a misjudged flare or bounced landing has more serious consequences. A fast approach in the Archer is not a minor issue — it directly increases landing distance and the risk of a hard landing. Approach speed (Vref) is 66 KIAS; landing at 90 KIAS means significantly more float and a longer landing distance.
A stabilized approach is non-negotiable — if you are fast, high, or unstable, go around.
A stabilized approach means: on glide slope, on speed, on heading, and in a steady descent. In the Archer, a stabilized approach is the foundation of a safe landing. If you are fast (above Vref), high (above the glide slope), or unstable (drifting, pitching, or in a steep descent), go around. A go-around at 500 ft AGL is far safer than pushing a bad landing. The runway is not going anywhere — you can always come around again.
Flare timing is critical — too early and the airplane settles hard; too late and the descent rate is not arrested.
The flare in the Archer should begin at roughly 20 ft AGL. At this altitude, you reduce power smoothly, raise the nose to a landing attitude, and the descent rate decreases. The main gear should touch down at or just above stall speed (45 KIAS in landing configuration). A flare that is too early (at 30+ ft AGL) results in the airplane settling hard as it runs out of lift. A flare that is too late (at 10 ft AGL) does not allow enough time to arrest the descent rate, resulting in a hard landing. Practice flare timing in calm conditions; crosswind and turbulence make it harder.
A bounced landing is not a recovery opportunity — it is a signal to go around immediately.
If the main gear touches down and the airplane bounces back into the air, the correct response is to go around immediately. Apply full power, raise the flaps, and climb away. Do not attempt to land it again from a bounced state. The Archer's nose gear is not steerable, and a second or third bounce will compromise directional control. NTSB LAX08CA199 and LAX04CA289 both involved pilots who attempted to recover from a bounced landing and ended up with a runway excursion and nose gear collapse. The go-around is the correct response.
Directional control on the ground depends on differential braking and rudder — the nose gear is not steerable.
The Archer's nose gear is not steerable. On the ground, directional control is maintained by differential braking (left brake to correct left drift, right brake to correct right drift) and rudder input. A hard landing can compromise directional control by damaging the nose gear or the braking system. If you lose directional control during the rollout, a runway excursion is likely. Practice differential braking in calm conditions; crosswind landings require active, coordinated input.
Crosswind technique in the Archer requires active aileron and rudder input — crab-and-slip.
In a crosswind, the Archer requires active aileron input to keep the wing down into the wind (preventing drift) and rudder input to keep the nose aligned with the runway (the crab-and-slip technique). A 6–10 knot crosswind is manageable in the Archer, but it requires active control. If you are not comfortable with the crosswind, go around and wait for a better wind direction or a different runway. A crosswind landing that results in drift during the rollout can lead to a runway excursion.
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 / runway excursion / nose gear collapse), and LAX04CA289 (2004 PA-28-181 misjudged flare / hard landing / directional control loss). Anonymized and localized to KSRQ.
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.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 KSRQ