Fast and Floating at Peter O Knight
Excess approach energy, a short runway, and the Archer's heavy momentum — a decision tree on energy management and go-around discipline
The scenario
Departing Peter O Knight Airport (KTPF), Tampa, FL — Runway 22, a 3,583 ft asphalt runway. Elevation 8 ft MSL. You are on a local VFR flight in a Piper Archer PA-28-181, solo, full fuel, within limits. The airplane is airworthy; nothing was written up.
It is a hot, humid Florida afternoon in late July: OAT 32°C, dew point 24°C, altimeter 29.88. Density altitude is approximately 2,100 ft — the airplane will perform as if it were at 2,100 ft elevation, not 8 ft. Scattered clouds at 3,500 ft, visibility 10 SM. Light and variable winds, but the ATIS reports occasional gusts to 8 knots. The runway is dry.
You have been flying the Archer for about 60 hours total in type. You are current and comfortable with the airplane's handling, but you have not yet internalized how much energy the Archer carries on approach — it is heavier and faster than the Warrior or Skyhawk you trained in. The Archer's fixed-pitch prop and fixed gear mean no drag devices except flaps, and the flaps are limited to 102 KIAS maximum extension speed (Vfe).
You are on a local practice flight. You have completed two uneventful landings on Runway 04 (the reciprocal, over dense development). Now you are planning to practice one more landing on Runway 22 (heading 217°, climb-out over open water). You are inbound on a 5 nm final approach to Runway 22.
Pilot: you — a Private pilot, current, roughly 200 hours total, 60 hours in the Archer. You are comfortable with the airplane but still learning its energy characteristics. You have not yet experienced a bounced landing or a runway excursion in the Archer.
- {'label': 'Field', 'value': 'KTPF · Peter O Knight'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '8 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-181'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
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 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 veered off the runway and struck obstacles.
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 CHI05CA208 (2005): A Piper PA-28-181 on a personal flight overran a grass runway and struck a utility pole during landing at Bird Field Airport, Missouri. 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 and obstacles near the runway.
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.
NTSB ERA10FA020 (2009, FATAL): A Piper PA-28-181 on a personal local flight landed fast and hard on a wet turf runway at Oliver Springs Airport, lost directional control during rollout, and collided with trees. The probable cause was the pilot's loss of directional control while landing on a wet runway.
NTSB CEN23LA345 (2023): A Piper PA-28-181 on a student solo cross-country flight experienced fuel exhaustion during approach to an alternate airport after the student pilot failed to visually verify fuel quantity before departure. The engine lost power during approach, resulting in a forced landing with runway overrun.
The common thread across all these accidents: the Piper Archer's heavier, faster energy characteristics make it unforgiving of approach errors. A fast approach, a delayed flap extension, a bounced landing, or a delayed go-around decision can lead to a runway excursion, a hard landing, or a collision with obstacles. At KTPF, Runway 22's climb-out environment is open water — but on landing, the runway end is the constraint. The Archer needs energy management and go-around discipline to land safely.
The real accidents cited above occurred at other airports — NOT at KTPF. Peter O Knight Airport has its own accident history (see field dominant patterns: FORCED_LANDING 19.4%, LOSS_OF_CONTROL_INFLIGHT 16.7%, LOSS_OF_CONTROL_GROUND 11.1%, DITCHING 11.1%, STALL_SPIN 8.3%), but these specific NTSB events happened elsewhere. The scenario is localized to KTPF to make the runway length and off-field environment real and consequential for you as a student here.
Key lesson — The Piper Archer carries more energy on approach than lighter aircraft. A fast approach floats longer, a delayed flap extension delays slowdown, and a bounced landing can lead to a runway excursion if directional control is lost. The Archer's fixed-pitch prop and fixed gear mean flaps are the only drag device. Vref is 66 KIAS; Vfe is 102 KIAS. Extend full flaps early, maintain a stabilized approach, and execute a go-around if the approach is unstable. At KTPF on Runway 22 (3,583 ft), a late touchdown or a runway excursion is a real risk. Energy management and go-around discipline are the keys to safe landings in the Archer.
Debrief — teaching points
The Archer is heavier and faster than a Warrior or Skyhawk — it carries more kinetic energy on approach.
The Piper Archer PA-28-181 has a 180 hp Lycoming O-360 and a maximum gross weight of 2,550 lbs. It is faster and heavier than the Warrior (150 hp, 2,325 lbs) or Skyhawk (160 hp, 2,450 lbs). On approach, this means the Archer carries more kinetic energy and floats longer if you arrive fast. A 10-knot overspeed on approach in the Archer will result in a longer float and a later touchdown than in a lighter airplane. Be aware of this energy characteristic and plan for it.
Vref is 66 KIAS; Vfe is 102 KIAS. Extend full flaps early and maintain approach speed.
The Archer's approach speed (Vref) is 66 KIAS. Maximum flap extension speed (Vfe) is 102 KIAS. This means you can extend full flaps at any airspeed below 102 KIAS and you should do so early on approach — at 3 nm final, not 1 nm final. Full flaps provide maximum drag and slowest approach speed. Delaying full flap extension is a common error that leads to fast approaches and long floats. Extend full flaps early and maintain Vref ± 5 knots.
A stabilized approach is the foundation of a safe landing.
A stabilized approach means: (1) on a stable descent profile (3° glide slope), (2) at Vref ± 5 knots, (3) with full flaps extended, (4) with the airplane trimmed for the descent, and (5) with no unusual control inputs required. If the approach is not stabilized by 500 ft AGL, go around. If the approach is not stabilized by 1,000 ft AGL, definitely go around. A go-around is not a failure; it is the correct decision when the approach is unstable.
A bounced landing requires immediate go-around decision-making.
If the Archer bounces on landing (touches down, then pitches up and becomes airborne again), the correct response is to go around immediately. Do not attempt to recover from the bounce by landing again — the airplane will likely veer off the runway or collide with the ground hard. Apply climb power, retract flaps, and climb back to pattern altitude. A bounced landing is a sign that the approach was too fast or the flare was too shallow. Go around and try again.
High density altitude reduces climb performance and increases landing distance.
On a hot day (OAT 32°C, dew point 24°C), the density altitude at KTPF (elevation 8 ft) is approximately 2,100 ft. This means the Archer will perform as if it were at 2,100 ft elevation. Climb performance is reduced and landing distance is increased. Plan for longer landing distances and reduced climb performance. At high density altitude, a short runway becomes even shorter.
Off Runway 22 at KTPF, the climb-out environment is open water — but on landing, the runway length is the constraint.
Runway 22 is 3,583 ft long. The climb-out environment (heading 217°) is open water — Hillsborough Bay. However, on landing, you are arriving over the bay and landing on the runway. The runway length is the constraint. A late touchdown or a runway excursion on Runway 22 is a real risk. Plan to touch down in the first 1,500 ft of the runway to have margin for rollout and braking.
Built from the real accident record
Scenario built from NTSB ERA10CA473 (2010 PA-28-181 crosswind / hard landing / excursion), LAX08CA199 (2008 PA-28-181 excessive approach airspeed / bounce / veering), CHI05CA208 (2005 PA-28-181 overrun / delayed go-around decision), LAX04CA289 (2004 PA-28-181 misjudged flare / hard landing / excursion), ERA10FA020 (2009 PA-28-181 wet runway / loss of directional control / tree strike), and CEN23LA345 (2023 PA-28-181 fuel exhaustion / approach overrun). Localized to KTPF.
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.185
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 KTPF