Fast and High on Final
Excess approach energy in a Piper Archer at a busy Class B airport — the decision to go around comes late
The scenario
Approaching Tampa International Airport (KTPA), Tampa, FL — Runway 19L, a busy Class B field. Elevation 26 ft MSL. You are on a personal flight, solo, in a Piper Archer PA-28-181. Fuel is adequate; weight and balance are within limits.
It is a warm Florida afternoon: OAT 29°C, dew point 21°C, altimeter 29.94 inHg. Scattered clouds at 3,500 ft, visibility 10 SM. Surface wind is reported as 180° at 12 knots, gusting to 18 knots — a crosswind component of roughly 10 knots on Runway 19L (magnetic heading 182°). ATIS reports light windshear on approach.
You are cleared for a straight-in approach to Runway 19L. You are 8 nm out, descending through 2,500 ft MSL, at 110 KIAS. The approach controller vectors you to a 4-nm final. You are on the localizer, on the glideslope. The Archer is a stable, predictable airplane, but it is heavier and faster than a Warrior — it carries more energy, and a fast or high approach floats and consumes runway. Density altitude at KTPA today is roughly 1,200 ft, which erodes climb performance but does not directly affect landing distance on an 8,300-ft runway.
Aircraft: Piper Archer PA-28-181, solo, full fuel, within limits. Lycoming O-360-A, 180 hp, carbureted, fixed-pitch prop, fixed gear, LEFT/RIGHT fuel selector (no BOTH position). Fuel selector is on LEFT tank (you switched from RIGHT on downwind). Vacuum steam panel. Nothing was written up; the airplane is airworthy.
Pilot: you — a Private pilot, current, roughly 250 hours total. You have 15 hours in the Archer. You are current on landings but have not flown into KTPA in six months. The Class B environment, the crosswind, and the windshear report are all present. You are stable on the approach but not yet fully committed to the landing.
- {'label': 'Field', 'value': 'KTPA · Tampa'}
- {'label': 'Runways', 'value': '10/28 · 19L/01R · 19R/01L'}
- {'label': 'Elevation', 'value': '26 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-181'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we enter the decision tree — what do you know about landing the Piper Archer in crosswind and windshear conditions? (Pick all that apply.)
What the record shows
What the NTSB files show
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. This is the exact sequence: high airspeed on final → bounce on touchdown → loss of directional control during recovery → runway excursion.
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 inadequate compensation for crosswind conditions. Windshear on approach, combined with a crosswind, can degrade the Archer's controllability if airspeed is not managed carefully.
NTSB CHI05CA208 (2005): A Piper PA-28-181 overran a grass runway and struck a utility pole during landing. The probable cause was the pilot's delayed decision-making and failure to execute a go-around. Contributing factors included excessive approach airspeed, high density altitude, and obstacles near the runway. The pilot saw the approach was unstable but did not go around — a continuation bias that led to a runway overrun.
NTSB LAX04CA289 (2004): A Piper PA-28-181 on a student instructional flight experienced a hard landing and runway excursion. The probable cause was the student pilot's misjudged flare, resulting in a stall and hard landing, and failure to maintain directional control. The contributing factor was improper recovery from a bounced landing. Again, the sequence: misjudged flare → stall → hard landing → bounce → loss of control → excursion.
NTSB ERA10FA020 (2009, FATAL): A Piper PA-28-181 landed fast and hard on a wet turf runway, lost directional control during rollout, and collided with trees. The probable cause was loss of directional control while landing on a wet runway. This case shows that even on a longer runway, a fast, hard landing can result in loss of directional control and a fatal outcome.
The consistent thread: the Piper Archer is a heavier, faster airplane than a Warrior. It carries more kinetic energy. A fast or high approach floats and consumes runway. A misjudged flare at high airspeed results in a stall and hard landing. A bounced landing at high airspeed can result in loss of directional control and a runway excursion. The fix is early speed reduction, gradual flap extension, and a stable approach by 500 ft AGL. If the approach is unstable at 500 ft AGL, go around. Do not try to salvage it.
These real accidents occurred at other airports and in other aircraft — NOT at Tampa International Airport. KTPA has its own accident history (dominant pattern: FORCED_LANDING 22.2%, LOSS_OF_CONTROL_INFLIGHT 11.1%, LOSS_OF_CONTROL_GROUND 8.9%, WIRE_STRIKE 6.7%, GEAR_UP_LANDING 6.7%), but these specific runway excursion cases happened elsewhere. The scenario is localized to KTPA to make the Class B environment, the crosswind, and the runway length real and consequential for you as a student here.
Key lesson — The Piper Archer is a heavier, faster airplane than a Warrior — it carries more kinetic energy on approach. A fast or high approach floats and consumes runway. Early speed reduction, gradual flap extension, and a stable approach by 500 ft AGL are non-negotiable. If the approach is unstable at 500 ft AGL, go around. A misjudged flare at high airspeed results in a stall, hard landing, bounce, and loss of directional control. At KTPA, with 8,300 ft on Runway 19L and dense development off the runway ends, a runway excursion is not a minor event — it is a serious accident.
Debrief — teaching points
The Archer carries more energy than a Warrior — early speed reduction is essential.
The Piper Archer is 180 hp, 2,550 lb gross weight. It is heavier and faster than a Warrior. On approach, this means it carries more kinetic energy. A fast or high approach will float and consume runway. The fix is early speed reduction: reduce power and extend flaps to 20° by 2 nm final, slow to 90 KIAS. Then extend flaps to 40° at 1 nm final and slow to Vref (66 KIAS) on short final. This gradual energy management is the standard for a safe landing in the Archer.
Vref for the Archer is 66 KIAS — this is the target speed on short final.
Vref (approach speed) for the Piper Archer is 66 KIAS. This is the speed at which the airplane should cross the runway threshold on short final. Landing at higher speeds (80–90 KIAS) increases float distance and landing distance. Landing at lower speeds (below 60 KIAS) risks a stall. Maintain 66 KIAS on short final, flaps 40°, and execute a normal flare.
A misjudged flare at high airspeed results in a stall and hard landing.
If you flare too high (at 40–50 ft AGL instead of 20–30 ft) at high airspeed (80+ KIAS), the Archer will stall. The stall results in a hard landing on the main gear. The hard landing can cause a bounce. If you are not prepared for the bounce and you apply forward pressure to recover, the Archer can drift (especially in a crosswind) and veer off the runway. The NTSB LAX08CA199 case shows this exact sequence: high airspeed → bounce → forward pressure → veering left → runway excursion → nose gear collapse.
An unstable approach at 500 ft AGL is a go-around.
If the approach is high, fast, or drifting by 500 ft AGL, go around. Do not try to salvage it. A go-around at 500 ft AGL is a normal, safe maneuver. Advance the throttle, retract flaps to 20°, and climb. Request another approach. The NTSB CHI05CA208 case shows a pilot who saw the approach was unstable but did not go around — the result was a runway overrun and a utility pole strike. The decision to go around is made at 500 ft AGL, not at 100 ft AGL.
Crosswind and windshear require careful airspeed management.
A 10-knot crosswind on a runway with a 12G18 kt wind report means windshear is likely. Windshear can cause sudden airspeed changes on final approach. The Archer's controllability is degraded at low airspeed in a crosswind. The fix is to maintain a slightly higher approach speed (70–75 KIAS instead of 66 KIAS) to maintain control authority, and to be prepared to go around if the approach becomes unstable. The NTSB ERA10CA473 case shows a PA-28-181 that encountered windshear and stalled during landing — the probable cause was inadequate compensation for crosswind conditions.
The Archer has a LEFT/RIGHT fuel selector with no BOTH position — fuel starvation is a risk.
The Piper Archer has a LEFT/RIGHT fuel selector with no BOTH position. On longer flights, you must switch tanks to balance fuel consumption and prevent fuel starvation. The NTSB CEN23LA345 case shows a PA-28 that experienced fuel exhaustion during approach after the student pilot failed to visually verify fuel quantity before departure and did not switch tanks. Always verify fuel quantity before departure, switch tanks on a schedule (every 15–20 minutes), and visually confirm fuel in both tanks during the approach.
Built from the real accident record
Scenario built from NTSB ERA10CA473 (2010 PA-28-181 windshear/stall/hard landing/excursion), LAX08CA199 (2008 PA-28-181 excessive airspeed/bounce/veering/nose gear collapse), CHI05CA208 (2005 PA-28-181 overrun/utility pole strike), LAX04CA289 (2004 PA-28-181 misjudged flare/hard landing/excursion), ERA10FA020 (2009 PA-28-181 wet runway loss of control/tree strike, fatal), and CEN23LA345 (2023 PA-28 fuel exhaustion approach/overrun). Localized to Tampa International Airport (KTPA).
NTSB reports: ERA10CA473 · LAX08CA199 · CHI05CA208 · LAX04CA289 · ERA10FA020 · CEN23LA345
ACS tasks: PA.VII.A — Approach and Landing · PA.VII.B — Go-Around / Rejected Landing · PA.I.F — Weather Information · 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 Archer scenarios · More scenarios at KTPA