Flare and Sink at Tampa Executive
A misjudged descent rate and premature power reduction turn a routine landing into a hard impact — structural damage, gear stress, and a critical go-around decision
The scenario
Departing Tampa Executive Airport (KVDF), Tampa, FL — Runway 23, a 5,000-foot asphalt runway. Field elevation 22 ft MSL. You are on a solo cross-country training flight in a Piper Warrior PA-28-161, full fuel, within weight and balance limits. The airplane has been through a 100-hour inspection and was signed off yesterday.
It is late afternoon in late spring: OAT 29°C, altimeter 29.92 inHg, visibility 10 SM. The wind is from the northwest at 12 knots gusting to 18 knots — a crosswind component of roughly 8–10 knots on Runway 23 (magnetic heading 222°). The wind is within the Warrior's demonstrated crosswind limit of 13 knots, but it is gusty and the gusts are noticeable on approach.
You have been flying for 2.5 hours. You are tired but current. You have logged 180 hours total, with 45 hours in the Warrior. This is your first landing at KVDF — you have not flown here before. The approach is stable: you are on a 3° glide path, 500 ft AGL, descending at 300 ft/min, airspeed 70 KIAS (slightly above Vref of 63 KIAS with full flaps), and the runway is made.
KVDF is non-towered (CTAF 122.8). You have announced your position on downwind and base. No other traffic is reported. You are alone on the approach.
Aircraft: Piper Warrior PA-28-161, fixed gear, fixed-pitch prop, carbureted Lycoming O-320-D. Fuel selector is on RIGHT tank (you switched at the halfway point of the flight). Flaps are at 40° (full). Trim is set for approach. The airplane is clean and predictable.
- {'label': 'Field', 'value': 'KVDF · Tampa Executive'}
- {'label': 'Runways', 'value': '5/23 · 18/36'}
- {'label': 'Elevation', 'value': '22 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-161'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we enter the decision tree — what do you know about the Warrior's landing characteristics and go-around procedures? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB ERA12CA407 (2012): A Piper PA-28-161 student pilot on a training flight for short-field landings experienced a hard landing when the student reduced power prematurely and did not advance throttle quickly enough for a go-around. The flight instructor's inadequate supervision of the student's power management resulted in the hard landing. The probable cause was the flight instructor's inadequate supervision and the student's premature power reduction during the landing flare.
NTSB ERA11LA264 (2011): A Piper PA-28-161 student pilot landed hard after encountering vertical wind shear, causing right main landing gear collapse. The accident resulted from inadequate maintenance inspection of the landing gear, which failed to detect a fatigue crack in the torque link lug. The crack was from a previous hard landing that was not properly inspected. Contributing factors included non-compliance with a factory service bulletin addressing landing gear inspections.
NTSB ERA11CA187 (2011): A Piper PA-28-161 on an instructional flight touched down hard on a runway without adequate flare, resulting in nose gear collapse and substantial firewall damage. The probable cause was the student pilot's inadequate landing flare and the certified flight instructor's inadequate remedial action. The hard landing stressed the nose gear beyond its design limits.
NTSB ERA11LA067 (2009): A Piper PA-28-161 on an instructional flight sustained structural damage when the student pilot landed hard with a sideload during crosswind landing practice. The accident resulted from inadequate crosswind landing technique and delayed corrective action by the flight instructor. The hard landing with sideload stressed the landing gear and caused structural damage.
Regional precedents (NTSB GAA17CA105, ERA17CA149, GAA16CA149) show a consistent pattern: pilots who exceed the aircraft's demonstrated crosswind limit or who fail to recognize an unstable approach and commit to a go-around early end up in hard landings, loss of directional control, or gear collapse. The common thread is inadequate decision-making on approach and inadequate go-around execution.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Tampa Executive Airport (KVDF). KVDF has its own accident history (see field dominant patterns: LOSS_OF_CONTROL_GROUND 18.4%, HARD_LANDING 18.4%, FORCED_LANDING 15.8%), but these specific NTSB cases happened elsewhere. The scenario is localized to KVDF to make the off-field environment and the crosswind conditions real and consequential for you as a student here.
The consistent lesson across all these events: a hard landing is not just a rough touchdown — it is structural damage to the landing gear. A fatigue crack in a torque link lug may not be visible after the first hard landing, but it grows with each subsequent landing. On the next hard landing, the gear fails. The NTSB ERA11LA264 case is a real example: a hard landing caused a fatigue crack that was not detected because the airplane was not inspected after the hard landing. On a subsequent hard landing, the gear collapsed. The lesson: hard landings require a thorough inspection by a mechanic, not just a visual walk-around by the pilot.
Key lesson — A hard landing is structural damage. The Piper Warrior's landing gear — especially the nose gear torque links and main gear attach points — is stressed by hard landings and sideloads in crosswind conditions. A fatigue crack from one hard landing may not be visible, but it grows with each subsequent landing. Inspect the landing gear thoroughly after any hard landing. Know the aircraft's demonstrated crosswind limit (13 knots for the Warrior), recognize when the approach is unstable, and commit to a go-around early. A smooth landing is the result of a stable approach, a gradual flare, and smooth power management — not a rushed descent and a hard flare.
Debrief — teaching points
A hard landing is structural damage — not just a rough touchdown.
The Piper Warrior's landing gear is designed to absorb normal landings at descent rates up to roughly 300 ft/min. A hard landing — descent rate of 400+ ft/min — stresses the gear beyond design limits. The nose gear torque links and main gear attach points are particularly vulnerable. A fatigue crack in a torque link lug from one hard landing may not be visible to the naked eye, but it grows with each subsequent landing. On the next hard landing, the gear fails. The NTSB ERA11LA264 case is a real example: a hard landing caused a fatigue crack that was not detected because the airplane was not inspected after the hard landing. On a subsequent hard landing, the gear collapsed. Inspect the landing gear thoroughly after any hard landing — do not assume a visual walk-around is sufficient.
Premature power reduction during the approach causes a sink and a hard landing.
The NTSB ERA12CA407 case involved a student pilot who reduced power to idle at 200 ft AGL, before the flare was complete. The airplane's descent rate increased, and the student was forced to flare hard to arrest the sink. The result was a hard landing. The lesson: power management during the approach is critical. Reduce power smoothly as the flare progresses, not before. In the Warrior, maintain power until the flare is well established, then reduce power smoothly to idle as the main gear approaches the runway. A premature power reduction forces a hard flare and a hard landing.
A hard flare at low altitude is a trap — it leads to a sink and a hard landing.
If you reduce power too early and the descent rate increases, the temptation is to pull back hard on the yoke to arrest the sink. This is a trap. A hard flare at 50 ft AGL or lower can cause a stall or a loss of control. The correct response to an unstable approach at 100 ft AGL or lower is a go-around, not a hard flare. Advance throttle to full power, raise the nose to climb attitude, retract flaps, and climb out. A go-around is always available; a hard landing is not recoverable.
The Warrior's demonstrated crosswind limit is 13 knots — know it and respect it.
The Piper Warrior's demonstrated crosswind limit is 13 knots. Gusts above that limit or poor technique in gusty conditions can cause loss of directional control during landing rollout. The NTSB GAA17CA105 case involved a pilot who exceeded the aircraft's demonstrated crosswind capability in gusting conditions and lost directional control, resulting in a nose-over. The lesson: know the aircraft's limits, recognize when conditions exceed those limits, and commit to a go-around or a diversion early. A 12-knot steady wind with 18-knot gusts is within limits, but the gusts are at the edge. If the approach feels unstable or the wind is particularly gusty, go around or divert.
A stable approach is the foundation of a smooth landing.
A stable approach to the Warrior is: 70 KIAS (Vref + 7 knots), 3° glide path, 300 ft/min descent rate, on centerline, and aligned with the runway. If any of these parameters are off — if the descent rate is too high, the airspeed is too low, or the approach is not aligned — the landing will be hard. The flare is a gradual pitch-up to reduce descent rate; it is not a correction for an unstable approach. If the approach is unstable at 100 ft AGL or lower, go around. A go-around is always the right call.
The flare is a gradual pitch-up — not a hard pull.
The flare in the Warrior is a gradual increase in pitch angle to reduce descent rate. At 50 ft AGL, begin a gentle pitch-up. The descent rate should drop smoothly from 300 ft/min to 150 ft/min, then 75 ft/min, then 0 ft/min as the main gear touches down. The flare should take 10–15 seconds. If you pull back hard on the yoke, you will either stall the airplane or cause a hard landing. A gradual, smooth flare is the key to a soft landing.
Go-around execution is critical — full throttle, pitch up, flaps retract in sequence.
A go-around in the Warrior requires a coordinated sequence: (1) advance throttle to full power, (2) raise the nose to climb attitude (roughly 10° pitch), (3) retract flaps to 20°, (4) retract flaps to 0° as the airplane climbs and accelerates. Do not retract all flaps at once — this can cause a sudden pitch change and loss of control. A go-around is not a last-second maneuver; it is a planned escape from an unstable approach. Recognize the instability early and execute the go-around smoothly.
Built from the real accident record
Scenario built from NTSB ERA12CA407 (2012 PA-28-161 hard landing / power reduction), ERA11LA264 (2011 PA-28-161 gear collapse after hard landing), ERA11CA187 (2011 PA-28-161 nose gear collapse / inadequate flare), ERA11LA067 (2009 PA-28-161 hard landing with sideload in crosswind), and regional precedents GAA17CA105, ERA17CA149, GAA16CA149 (crosswind loss of control / go-around decisions). Localized to Tampa Executive Airport (KVDF).
NTSB reports: ERA12CA407 · ERA11LA264 · ERA11CA187 · ERA11LA067 · GAA17CA105 · ERA17CA149 · GAA16CA149
ACS tasks: PA.VII.A — Normal Landing · PA.VII.B — Forward Slip to a Landing · PA.VII.C — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.II.A — Preflight Assessment
Relevant FARs: §91.3 · §91.13 · §91.103
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 Warrior scenarios · More scenarios at KVDF