Fast and Floating at Tampa North
Excess approach energy, a short runway, and the Archer's momentum — the decision to go around comes late
The scenario
Departing Tampa North Aero Park Airport (X39), Tampa, FL — Runway 14, on a VFR local flight. Elevation 68 ft MSL. You are a Private pilot with roughly 180 hours total time, current and proficient. This is your second visit to X39; you are familiar with the field from a previous dual flight.
It is a warm Florida afternoon in late July: OAT 32°C, dew point 24°C, altimeter 29.89. Scattered clouds at 3,500 ft, visibility 10 SM. The wind is light and variable, roughly 090° at 4 knots — essentially calm. Density altitude at X39 is approximately 2,100 ft, which is moderate for the Archer but not extreme.
You have completed a 45-minute local flight and are returning to X39 for landing on Runway 14 (true heading 141°). You are at 1,500 ft MSL on a straight-in approach, 8 nm from the field. ATC (Tampa Class B approach) has handed you off to the X39 CTAF frequency. X39 is non-towered; you are announcing your position and intentions on CTAF.
Aircraft: Piper PA-28-181 Archer, solo, 38 gallons usable fuel remaining (well above minimums), within weight and balance limits. The airplane is performing normally. Fixed gear, fixed-pitch prop, carbureted Lycoming O-360, steam panel.
Runway 14 is 3,541 ft long — adequate for the Archer under normal conditions. The off-field environment off Runway 14's departure end (climb-out heading 141°) is medium development, low-density development, and wooded wetland — not ideal for a forced landing, but not water. The opposite end (Runway 32, heading 321°) has the same off-field character.
You are planning a standard approach and landing. The wind is light. You have adequate fuel. The weather is VFR. This should be a straightforward return to your home field.
- {'label': 'Field', 'value': 'X39 · Tampa North Aero Park'}
- {'label': 'Runways', 'value': '14/32'}
- {'label': 'Elevation', 'value': '68 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-181'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we get into the decision tree — what do you already know about the 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 Runway 14 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. The excess airspeed on approach — caused by delayed flap extension — led directly to the bounce and the loss of control during rollout.
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. The pilot was aware the approach was unstable but continued rather than going around.
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 failure to maintain directional control during rollout. The pilot's improper recovery from a bounced landing was a contributing factor.
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. The fast landing and wet surface combined to overwhelm the pilot's ability to maintain directional control.
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 stall and hard landing led to loss of directional control.
The consistent thread across all these accidents: the Archer is heavier and faster than a Warrior. It carries more energy and floats longer if the approach is fast or high. A misjudged flare, a bounced landing, or a loss of directional control during rollout can quickly escalate to a runway excursion or collision. The decision to go around — even late in the approach — is always safer than trying to salvage a bad landing. The real accidents cited above occurred at other airports and in other contexts — NOT at Tampa North Aero Park. X39 has its own accident history dominated by loss of control in flight and on the ground; these specific NTSB cases are precedents for how the Archer fails when the approach is unstable.
At X39, Runway 14 is 3,541 ft long — adequate for the Archer under normal conditions. But a fast landing with excess energy can consume 2,500+ ft of that length, leaving little margin for error during rollout. The off-field environment off both runway ends is medium development, low-density development, and wooded wetland — not ideal for a forced landing, but not water. A runway excursion at X39 means departure into that development, not a ditching.
Key lesson — The Piper Archer carries more energy than smaller trainers. A fast or high approach will not forgive a late decision. The correct response to an unstable approach — whether at 4 nm, 2 nm, or 0.5 nm — is a go-around, not a recovery attempt. An unstable approach is not a challenge to overcome; it is a signal to restart. At X39, Runway 14 is 3,541 ft long, but a fast landing can consume most of that length. Know your limits and the runway's limits. A firm landing is survivable; a runway excursion is not.
Debrief — teaching points
The Archer is heavier and faster than a Warrior — it carries more energy and floats longer.
The Piper PA-28-181 Archer has a 180 hp Lycoming O-360 and a gross weight of 2,550 lbs, compared to the Warrior's 150 hp and 2,325 lbs. This extra weight and power mean the Archer carries more kinetic energy into the landing. A fast approach (75+ KIAS instead of 66 KIAS Vref) will result in a longer float and a touchdown farther down the runway. At X39 with a 3,541 ft runway, a fast landing that consumes 2,500+ ft leaves little margin for error during rollout. Know the airplane's energy and plan accordingly.
Vref for the Archer is 66 KIAS on short final — exceeding this speed increases float and reduces stopping distance.
The Piper Archer's approach speed (Vref) is 66 KIAS with full flaps. This is the speed that balances control authority, descent rate, and landing distance. Approaching at 75 KIAS or faster will result in a longer float and a touchdown farther down the runway. At high density altitude (like the 2,100 ft DA at X39 on a warm day), landing distance increases by 20–30%; a fast approach makes this worse. Plan to be at 66 KIAS on short final, not faster.
An unstable approach is not a challenge to overcome — it is a signal to go around.
The NTSB cases LAX08CA199, CHI05CA208, and LAX04CA289 all show pilots who recognized an unstable approach but continued rather than going around. The result was hard landings, bounces, and loss of directional control. The correct decision-making pattern is: if the approach is unstable — too fast, too high, not aligned, or compressed — add power, level off, and go around. A go-around costs a few minutes; a runway excursion or nose gear collapse costs much more. At X39, a runway excursion means departure into development, not a safe field landing.
Delayed flap extension leads to fast approaches and long floats.
The LAX08CA199 accident was caused by the student pilot delaying flap extension until late in the approach. The result was excess airspeed, a long float, a bounce, and a loss of directional control. The correct flap schedule for the Archer is: 10° at 5 nm, 20° at 3 nm, 40° at 1 nm or when the runway is assured. This schedule gives you time to stabilize the airplane at each configuration change and to recognize if the approach is becoming unstable. Delaying flaps compresses the approach and leaves you behind the airplane.
A bounced landing in the Archer can lead to nose gear collapse and firewall damage.
The LAX08CA199 and LAX04CA289 cases both show bounced landings that led to nose gear collapse and structural damage. The Archer's nose gear is not as robust as the main gear; a hard landing or a bounce can overwhelm it. If you touch down fast and the airplane bounces, the correct response is to add power and go around — do not try to land again from a bounced condition. The nose gear cannot take repeated hard impacts.
High density altitude increases landing distance — plan for it.
At X39 on a warm Florida afternoon, density altitude can be 2,000+ ft. This increases the Archer's landing distance by 20–30% compared to sea-level standard conditions. A normal landing distance of 1,500 ft becomes 1,800–2,000 ft at high DA. If you are planning a fast approach or a long float, you are eating into that margin. Know the density altitude for the day and plan your landing distance accordingly.
Built from the real accident record
Scenario built from NTSB ERA10CA473 (2010 PA-28-181 crosswind stall/hard landing), LAX08CA199 (2008 PA-28-181 excessive airspeed/bounced landing/runway excursion), CHI05CA208 (2005 PA-28-181 overrun/utility pole strike), LAX04CA289 (2004 PA-28-181 misjudged flare/hard landing), ERA10FA020 (2009 PA-28-181 wet runway loss of control/tree strike), and CEN23LA345 (2023 PA-28-181 fuel exhaustion/landing overrun). Localized to Tampa North Aero Park Airport (X39).
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.9
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 X39