Energy Management on Short Final
Excess approach airspeed, float, and a narrowing runway — the Archer's weight and inertia demand early decisions
The scenario
Departing Brooksville–Tampa Bay Regional Airport (KBKV), Brooksville, FL — Runway 09, a 7,001 ft concrete runway. Elevation 76 ft MSL. You are on a local VFR flight, solo, full fuel, within limits.
It is a hot, humid Florida afternoon in August: OAT 32°C, dew point 24°C, altimeter 29.89. Density altitude is approximately 2,200 ft — the airplane will perform as if it is 2,200 ft higher than the field elevation. Scattered clouds at 3,500 ft, visibility 10 SM. Light crosswind from the left (roughly 040° at 6 knots). KBKV's tower is active (0700–2200 local); you are in Class D airspace.
You have been flying for 1.2 hours. The approach is stable: you are on a 3° glide slope, 2 nm from the runway, descending through 1,200 ft MSL. Airspeed is 85 KIAS — 19 knots above Vref (66 KIAS). You have not yet extended full flaps; you are at 20° flap. The runway is ahead, clearly visible. Tower clears you to land.
Aircraft: Piper PA-28-181 Archer, solo, full fuel (48 gallons usable), within CG and weight limits. Carbureted Lycoming O-360-A, 180 hp, fixed-pitch prop, fixed gear, LEFT/RIGHT fuel selector (no BOTH position). Steam/vacuum panel. Best glide 76 KIAS.
Pilot: you — a Private pilot, current, roughly 180 hours total. You have 12 hours in the Archer. You are comfortable with the airplane but have not yet internalized how much energy it carries on approach — the Archer is heavier and faster than a Warrior or Skyhawk. You are on a stable approach, but you are not thinking about the energy budget.
- {'label': 'Field', 'value': 'KBKV · Brooksville–Tampa Bay'}
- {'label': 'Runways', 'value': '3/21 · 9/27'}
- {'label': 'Elevation', 'value': '76 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-181'}
- {'label': 'Dominant phase', 'value': 'Landing / Cruise'}
The decision
Before we get into the decision tree — what do you already know about the Piper Archer's approach and landing characteristics? (Pick all that apply; this records your baseline.)
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 approach and delayed flap extension. The aircraft landed with excessive airspeed, 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 accident happened at a different airport — NOT at KBKV — but the sequence is identical to what you just experienced: excess airspeed on approach, bounce, loss of directional control, runway excursion.
NTSB CHI05CA208 (2005): A Piper PA-28-181 on a personal flight overran a grass runway and struck a utility pole during landing. The accident resulted from the pilot's delayed decision-making, excessive approach airspeed, and failure to execute a go-around. Contributing factors included high density altitude (the airplane performed as if it were 2,000+ ft higher) and obstacles near the runway. The pilot had the opportunity to go around but chose to continue the landing. This accident also occurred at a different airport — NOT at KBKV.
NTSB ERA10CA473 (2010): A Piper PA-28-181 on approach 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 Archer, with its fixed gear and fixed-pitch prop, is particularly sensitive to crosswind during landing — the weight and inertia make directional control critical.
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 accident was fatal. The sequence — fast landing, loss of control, collision — is the worst-case outcome of the scenario you just flew.
The consistent thread across all these accidents: the Piper Archer is heavier and faster than a Warrior or Skyhawk. It carries more energy on approach, floats longer if airspeed is high, and is less forgiving of poor energy management. The accidents happen when pilots (1) delay reducing airspeed on approach, (2) extend flaps too late or at high airspeed, (3) try to salvage an unstable approach instead of going around, or (4) lose directional control during rollout after a firm landing. All of these are preventable with early energy management and a willingness to go around.
At KBKV, the off-field environment off Runway 09 is open developed (parks/large lots), pasture/hay, and medium development — good forced-landing terrain if needed. But a runway excursion into that terrain is still an accident. The goal is to land on the runway, not off it.
Key lesson — The Piper Archer is a heavier, faster airplane than a Warrior or Skyhawk. On approach, it carries more energy and floats longer if airspeed is high. Energy management must start early — reduce airspeed to Vref (66 KIAS) before extending full flaps, and be willing to go around if the approach is unstable. A firm landing or a runway excursion is the result of excess airspeed on approach. At KBKV, Runway 09 is 7,001 ft — plenty of runway — but only if you land in the first third. Land above Vref and you will float past the midpoint. Manage energy early, or go around.
Debrief — teaching points
The Archer is heavier and faster than a Warrior or Skyhawk — energy management is critical.
The Piper PA-28-181 Archer weighs 2,550 lbs gross and cruises at 125 KIAS (Vno). The Warrior weighs 2,325 lbs and cruises at 111 KIAS. The Skyhawk weighs 2,450 lbs and cruises at 122 KIAS. The Archer's extra weight and speed mean it carries more energy on approach and floats longer if airspeed is high. A 10-knot excess on approach in an Archer is more consequential than in a Warrior. Internalize this: the Archer demands earlier, more aggressive energy management.
Vref is 66 KIAS — that is the target speed on short final, not a speed to exceed.
Vref (approach speed) for the Archer is 66 KIAS. This is the speed at which the airplane is stable, the descent rate is predictable, and the flare and landing are smooth. If you are above Vref on short final, the airplane will float — the excess airspeed keeps it in the air. You will touch down farther down the runway than planned. In a 7,001 ft runway like Runway 09 at KBKV, this is usually not a problem — you have plenty of runway. But in a shorter runway, a float can lead to a runway excursion. The solution: reduce airspeed to Vref before extending full flaps, and maintain Vref on short final.
Extend full flaps at or below Vfe (102 KIAS) — extending flaps at high airspeed can damage the wing.
Vfe (maximum flap extended speed) for the Archer is 102 KIAS. You can extend full flaps (40°) at any airspeed up to 102 KIAS without risk of structural damage. However, extending full flaps at high airspeed (e.g., 85 KIAS) creates a sudden pitch-up moment — the wing's lift coefficient increases, and the airplane pitches up. If you are not prepared for this pitch-up, you may instinctively pitch down to maintain glide slope, and the descent rate increases. The solution: reduce airspeed to approximately 70 KIAS, then extend full flaps. The pitch-up moment will be smaller, and the descent rate will be more predictable.
A bounced landing is a critical moment — go around instead of trying to salvage it.
If the airplane bounces on touchdown, you are now 20–30 ft AGL, airborne again, above Vref, and the runway is passing beneath you. You have two options: (1) go around — apply power, pitch up to Vy (76 KIAS), retract flaps, and climb out; or (2) try to land again. The NTSB data is clear: pilots who try to salvage a bounced landing have a significantly higher accident rate than those who go around. A bounced landing is a sign that energy management was not optimal. The correct response is to go around, circle, and set up for another approach. Do not try to catch the second landing.
Loss of directional control during rollout is often the result of a firm landing combined with a crosswind.
The Archer's weight and inertia make directional control critical during rollout, especially after a firm landing. A light crosswind (6 knots) is usually not a problem — but after a firm landing, the airplane is moving fast and the crosswind can push the nose off the centerline. The solution: (1) land smoothly at Vref to minimize the landing impact and the speed during rollout, (2) maintain directional control with rudder input, and (3) apply braking smoothly. If you lose directional control, do not apply maximum braking — this can cause the nose to pitch down and make the situation worse. Instead, apply moderate braking and use rudder to maintain centerline.
High density altitude reduces climb performance and increases landing distance — the airplane needs more runway.
On a hot, humid day like the one in this scenario (OAT 32°C, dew point 24°C), the density altitude is approximately 2,200 ft. This means the airplane performs as if it is 2,200 ft higher than the field elevation (76 ft MSL). The Archer's climb performance is reduced, and the landing distance is increased. At KBKV, Runway 09 is 7,001 ft — plenty of runway even with high density altitude. But on a shorter runway, high density altitude can be a limiting factor. Always calculate the landing distance required and compare it to the runway available, accounting for density altitude.
Built from the real accident record
Scenario built from NTSB ERA10CA473 (2010 PA-28-181 windshear/stall/hard landing), LAX08CA199 (2008 PA-28-181 delayed flaps/bounce/excursion), CHI05CA208 (2005 PA-28-181 excessive airspeed/overrun), LAX04CA289 (2004 PA-28-181 misjudged flare/excursion), ERA10FA020 (2009 PA-28-181 wet runway loss of control, fatal), and CEN23LA345 (2023 PA-28-181 fuel exhaustion approach). Anonymized and localized to KBKV.
NTSB reports: ERA10CA473 · LAX08CA199 · CHI05CA208 · LAX04CA289 · ERA10FA020 · CEN23LA345
ACS tasks: PA.II.E — Approach and Landing · PA.II.F — Go-Around / Rejected Landing · PA.I.F — Weather Information · PA.I.H — Human Factors · PA.IX.C — Emergency Approach and Landing
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 KBKV