Flare and Sink at Tampa Executive
A misjudged landing flare in a Piper Archer — the heavier airplane's energy and the runway's limits collide
The scenario
Departing Tampa Executive Airport (KVDF), Tampa, FL — Runway 23, a 5,000 ft asphalt runway on a 222° magnetic heading. Elevation 22 ft MSL. You are on approach to land after a local flight in the Piper Archer PA-28-181.
It is a warm Florida afternoon: OAT 29°C, wind 190° at 12 knots gusting to 18 knots. Runway 23 is oriented 222° — the wind is roughly 30° off the runway heading, a moderate crosswind. Visibility is 10 SM, scattered clouds at 2,500 ft. KVDF is non-towered (CTAF); you are in Class G airspace below 3,000 ft MSL. Above 3,000 ft, the overlying Tampa Class B airspace begins.
You are on a 3° glide slope, 2 nm from the runway, descending through 1,200 ft MSL. The runway is in sight. You have been flying this route for months; the approach feels routine. You have 180 hours total time, 40 hours in the Archer. You are current and proficient — or so you feel.
Aircraft: Piper PA-28-181 Archer, solo, 2,400 lbs (within limits). Lycoming O-360-A, 180 hp, carbureted, fixed-pitch prop, fixed gear. Fuel selector on RIGHT tank (you switched from LEFT on downwind). Flaps are at 10° — you plan to add full 40° flaps on short final.
The wind is gusty. On base leg, you felt a brief gust push the left wing up; you corrected with right aileron. The approach has been stable since then. You are not thinking much about the crosswind — the Archer is a solid airplane, and you have landed in crosswinds before.
- {'label': 'Field', 'value': 'KVDF · Tampa Executive'}
- {'label': 'Runways', 'value': '5/23 · 18/36'}
- {'label': 'Elevation', 'value': '22 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 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 probable cause was the pilot's inadequate compensation for crosswind conditions. The accident demonstrates the critical importance of maintaining proper airspeed and control authority in a crosswind landing.
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. 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 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 improper recovery from a bounced landing was a contributing factor.
The real accidents cited above occurred at other airports — NOT at Tampa Executive Airport (KVDF). KVDF has its own accident history dominated by loss-of-control-ground, hard landings, and forced landings. The scenario is localized to KVDF to make the runway environment and the crosswind conditions real and consequential for you as a student here.
The consistent thread across all these events: the Piper 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 a loss of directional control in a crosswind can quickly escalate into a runway excursion or structural damage. The Archer demands precision in the landing flare and immediate, decisive action if the landing becomes unstable.
Off Runway 23 at KVDF, the climb-out environment is pasture/hay, open water, and medium development — good off-field options if an engine failure occurs on departure. But on landing, the runway is your only option. A runway excursion off Runway 23 could result in impact with obstacles or terrain off the runway end. The runway is 5,000 ft long — there is always room for a go-around if the approach becomes unstable.
Key lesson — The Piper Archer's weight and energy demand precision in the landing flare. A misjudged flare (too high, too late) results in a stall and hard landing. A bounced landing at low altitude is unstable — the correct response is an immediate go-around, not an attempt to salvage the landing. In a crosswind, maintain proper crab angle through the flare, then straighten the wings at touchdown with coordinated aileron and rudder. If the approach becomes unstable at any point, execute a go-around. The runway is 5,000 ft long; there is always room to try again.
Debrief — teaching points
The Piper Archer is heavier and faster than a Warrior — it carries more energy into the landing.
The Archer's Lycoming O-360-A produces 180 hp, and the airplane weighs up to 2,550 lbs at gross. It is faster and heavier than a Warrior or Tomahawk. This means it carries more kinetic energy into the landing. A misjudged flare or a fast approach will float longer and require more runway. The Archer demands a precise, shallow flare and strict adherence to Vref (66 KIAS) on short final. A fast approach or a late flare is unforgiving.
Vref is 66 KIAS — maintain it through the flare.
The Archer's approach speed (Vref) is 66 KIAS. This is the target speed on short final and through the flare. Maintaining Vref ensures the airplane has the right energy for a smooth touchdown and the right control authority to handle crosswinds. Landing faster than Vref increases float, reduces control authority, and increases impact energy. Landing slower than Vref risks a stall. Maintain 66 KIAS.
The flare is where precision matters most — a misjudged flare results in a stall or hard landing.
The flare is the transition from descent to level flight. In the Archer, the flare must be shallow and gradual. A flare that is too aggressive (nose pitched up too steeply) will bleed off airspeed and risk a stall. A flare that is too shallow (nose not pitched up enough) will result in a hard landing. The correct flare is a gradual, coordinated pitch-up that reduces the descent rate to near-zero at the instant of touchdown. Practice the flare in calm conditions until it becomes smooth and automatic.
In a crosswind, maintain crab angle through the flare, then straighten at touchdown.
In a crosswind, you must crab the airplane to maintain runway alignment during the approach and flare. The crab angle is maintained by the pilot's heading control — the airplane's nose is pointed into the wind, but the fuselage is not aligned with the runway. At the instant of touchdown, the pilot must straighten the wings with coordinated aileron and rudder to align the fuselage with the runway. If the airplane touches down in a crab (fuselage not aligned with the runway), the landing will be hard and asymmetrical — one main gear will touch first, and the airplane may veer or bounce. Practice crosswind landings until straightening at touchdown becomes automatic.
A bounced landing at low altitude is unstable — the correct response is an immediate go-around.
If the Archer bounces on touchdown (the main gears leave the runway), the situation is unstable and deteriorating. Trying to salvage a bounced landing by reducing power and lowering the nose will result in a second, harder bounce. The correct response is an immediate go-around: advance the throttle to full power, retract the flaps, and climb away. The runway is 5,000 ft long; there is always room to go around. A go-around is not a failure — it is airmanship. Do not try to salvage an unstable landing.
Full flaps (40°) are limited to 102 KIAS — do not extend flaps above this speed.
The Archer's full flaps (40°) are limited to 102 KIAS (Vfe). Landing with full flaps above this speed risks structural damage to the flap system. On approach, ensure the airspeed is below 102 KIAS before extending full flaps. If the approach is fast, extend flaps gradually (10° at a time) and reduce airspeed before extending further. Never extend full flaps at high airspeed.
Built from the real accident record
Scenario built from NTSB ERA10CA473 (2010 PA-28-181 windshear / hard landing / loss of directional control), LAX08CA199 (2008 PA-28-181 bounced landing / runway excursion), and LAX04CA289 (2004 PA-28-181 misjudged flare / hard landing / loss of directional control). Anonymized and localized to KVDF (Tampa Executive Airport).
NTSB reports: ERA10CA473 · LAX08CA199 · LAX04CA289
ACS tasks: PA.II.D — Approach and Landing · PA.II.E — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.IX.C — Emergency Approach and Landing
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 KVDF