Gusts on Short Final at Peter O Knight
Crosswind landing in gusty conditions, loss of directional control, and the decision point between go-around and accepting a veer
The scenario
Departing Peter O Knight Airport (KTPF), Tampa, FL — Runway 22, a 3,583 ft asphalt runway on a 217° magnetic heading. Elevation 8 ft MSL. You are a commercial pilot with 800 hours total, 200 hours in the Piper Arrow PA-28R. This is a local flight — a 45-minute round trip to a nearby airport and back.
The weather is VFR: scattered clouds at 3,500 ft, visibility 10 SM, temperature 26°C, dew point 20°C. The wind is from 240° at 12 gusting to 18 knots — a crosswind from the left on Runway 22 (magnetic heading 217°). The crosswind component is roughly 10 knots steady, with gusts to 16 knots. The Piper Arrow's demonstrated crosswind capability is 12 knots. You are at the edge of your airplane's demonstrated limit, and the gusts exceed it.
You have completed the outbound leg and are now on approach to Runway 22 at KTPF. The field is non-towered (CTAF); you self-announce on 122.95. You are at 1,500 ft MSL (1,492 ft AGL), 3 miles from the runway on a left downwind. The wind is gusting noticeably; you have felt several bumps in the descent. Off the Runway 22 departure end (heading 217°), the off-field environment is open water — Hillsborough Bay. Off the Runway 04 end (heading 37°), the environment is dense development.
Aircraft: Piper Arrow PA-28R-200, solo, 2,400 lb gross weight, within limits. Fuel: 40 gallons usable (plenty). Gear: down and locked (three green lights). Prop: constant-speed, set to high RPM for approach. Flaps: 0° (you plan to extend them on base). The airplane is airworthy; it came out of annual inspection two weeks ago.
Pilot: you — a commercial pilot, current, 800 hours total, 200 hours in the Arrow. You have landed at KTPF twice before, both times in calm conditions. You have crosswind experience, but not in gusts that exceed the demonstrated limit. You are familiar with the Arrow's systems: retractable gear, constant-speed prop, fuel selector LEFT/RIGHT, and the workload that comes with a complex airplane during an approach. You have not flown here in gusty conditions.
- {'label': 'Field', 'value': 'KTPF · Peter O Knight'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '8 ft'}
- {'label': 'Aircraft', 'value': 'PA-28R'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
Before we get into the decision tree — what do you know about crosswind landings in a complex airplane like the Arrow? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB WPR25LA178 (2025): A Piper PA-28R-200 on a test flight following annual inspection experienced brake system failure during landing rollout due to a hydraulic fluid leak. The aircraft exited the runway and collided with a fence. The probable cause was a failure of the brake system during landing, which resulted in a runway excursion. The lesson: post-maintenance flights require a functional brake system check, and loss of braking authority during rollout is an immediate runway-excursion risk.
NTSB CEN24LA288 (2024): A Piper PA-28R-180 on a personal flight landed with the left and nose landing gear not fully locked due to the pilot's failure to extend the gear before landing. The accident resulted from the pilot's failure to conduct the before-landing checklist due to distractions from skydiving operations and difficulty locating an unfamiliar airport. The lesson: the before-landing checklist is not optional, and gear extension must be confirmed before the approach begins — not during it.
NTSB CEN23LA417 (2023): A Piper PA-28RT-201 experienced partial retraction of the right main and nose landing gear during landing rollout, causing the right wing to scrape the runway and the aircraft to exit the runway. The cause of the gear retraction could not be determined despite extensive testing. The lesson: in a complex airplane, gear-related anomalies during landing can cause a runway excursion even when the pilot is not at fault.
NTSB CEN21LA269 (2021): A Piper PA-28R on a personal flight experienced loss of directional control during the takeoff roll and struck runway signs and lights. The accident resulted from the pilot's failure to maintain directional control. The lesson: loss of directional control can happen on takeoff as well as landing — crosswind conditions and gusts are a threat throughout the flight.
NTSB GAA17CA105 (2016): A Piper PA-46 experienced loss of directional control during landing rollout in gusting crosswind conditions that exceeded the aircraft's demonstrated crosswind capability. The accident resulted from the pilot's loss of directional control during the aborted landing in gusting crosswind conditions. The lesson: when crosswind conditions exceed the demonstrated limit, a go-around or diversion is the correct decision — not an attempt to recover during rollout.
NTSB ERA11CA212 (2011): A Mooney M20J on a personal flight landed on runway 18 in a crosswind, veered 90 degrees left, departed the runway, struck a seawall, and came to rest nose-down in salt water. The accident resulted from the pilot's failure to maintain directional control during a crosswind landing. The lesson: at KTPF, off Runway 22 the off-field environment is open water — Hillsborough Bay. A veer into the water is a ditching, not a runway excursion. The margin for error is zero.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Peter O Knight Airport. KTPF has its own accident history (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 off-field environment real and consequential for you as a student here.
The consistent thread across all these events: loss of directional control during landing rollout in gusty crosswind conditions is a runway-excursion accident waiting to happen. The decision points are: (1) recognize when crosswind conditions exceed your demonstrated limit and divert before the approach; (2) if you commit to the approach, maintain control inputs throughout the rollout, not just on short final; (3) if a veer begins, accept it and apply brakes smoothly — fighting a veer with aggressive corrections at low speed is a losing game.
Key lesson — At KTPF, three of the four runway ends (22, 18, 36) have open water as the off-field environment. A loss of directional control during landing rollout in a gusty crosswind is not just a runway excursion — it is a potential ditching. Recognize when crosswind conditions exceed your airplane's demonstrated limit (12 knots for the Piper Arrow) and commit to a diversion or go-around early. If you do veer during rollout, accept it and apply smooth brakes — do not fight it with aggressive control inputs. The margin for error is zero.
Debrief — teaching points
Demonstrated crosswind capability is a limit, not a guideline.
The Piper Arrow's demonstrated crosswind capability is 12 knots. This is the maximum crosswind the airplane was tested to handle safely during landing. When the wind is 240° at 12G18 knots on a 217° runway, the steady crosswind is 10 knots and the gusts exceed 16 knots — you are beyond the demonstrated limit. The FAA and the manufacturer have set this limit based on testing. Exceeding it in gusts is a decision to accept higher risk. A diversion or go-around is the correct response, not an attempt to 'handle it.'
Maintain control inputs throughout the rollout, not just on short final.
A crosswind landing requires continuous aileron and rudder inputs from touchdown through the rollout. The wing-down technique (lower the upwind wing, apply opposite rudder to keep the nose aligned) must be maintained as the airplane decelerates. Relaxing the inputs as the airspeed drops below 60 KIAS invites a gust-induced veer. Keep the inputs in until the airplane is slow enough that a gust cannot lift a wing — typically below 20 KIAS.
If a veer begins, accept it and apply smooth brakes — do not fight it.
If the airplane begins to veer during rollout despite your control inputs, the correct response is to accept the veer and apply smooth brakes. Fighting a veer with aggressive control inputs at low speed (below 40 KIAS) is a losing game — you risk over-correcting and veering in the opposite direction. A smooth brake application will slow the airplane and reduce the veer's severity. An off-centerline stop on the runway is far better than a runway excursion or a veer into the off-field environment.
At KTPF, three runway ends have open water as the off-field environment.
Off Runway 22 (217°), the off-field environment is open water — Hillsborough Bay. Off Runway 18 (173°), the environment is also open water. Off Runway 36 (353°), the environment is open water and low-density development. Only off Runway 04 (37°) is the environment dense development. A loss of directional control during landing rollout on Runways 22, 18, or 36 is not just a runway excursion — it is a potential ditching. The margin for error is zero.
The before-landing checklist is not optional — gear must be down and locked before the approach.
In a Piper Arrow, the landing gear is retractable and must be extended before the approach begins. The before-landing checklist includes: gear down and locked (three green lights), flaps as needed, fuel selector LEFT or RIGHT (not BOTH), prop high RPM, and mixture as needed. This checklist is not optional, and it must be completed before the approach begins — not during it. A gear-up landing or a gear-extension failure during rollout is a serious accident.
Constant-speed prop should be set to high RPM for approach and landing.
The Piper Arrow's constant-speed prop should be set to high RPM (full forward) for approach and landing. This setting provides maximum control authority and reduces workload. Low RPM increases the workload and can reduce control authority when you need it most — during a crosswind landing or an emergency maneuver. High RPM is the standard setting for landing.
Built from the real accident record
Scenario built from NTSB WPR25LA178 (2025 PA-28R brake failure / runway excursion), CEN24LA288 (2024 PA-28R gear-up landing), CEN23LA417 (2023 PA-28RT gear retraction during rollout), CEN21LA269 (2021 PA-28R loss of directional control on takeoff), and regional crosswind-loss-of-control precedents GAA17CA105, CHI02TA149, GAA17CA021, ERA11CA212. Real events occurred at other airports — NOT at KTPF.
NTSB reports: WPR25LA178 · CEN24LA288 · CEN23LA417 · CEN21LA269 · GAA17CA105 · CHI02TA149 · GAA17CA021 · ERA11CA212
ACS tasks: PA.VII.A — Preflight Inspection · PA.VII.B — Airplane Systems · PA.VIII.A — Takeoff and Departure · PA.VIII.B — In-Flight Maneuvers · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors
Relevant FARs: §91.3 · §91.13 · §91.175
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 Arrow scenarios · More scenarios at KTPF