Gusts on Short Final at Peter O Knight
Crosswind landing in gusty conditions — the C150's light wing loading and marginal control authority make this a decision-critical scenario
The scenario
Departing Peter O Knight Airport (KTPF), Tampa, FL — Runway 22, landing in gusty crosswind conditions. Elevation 8 ft MSL. This is a non-towered field; you are self-announcing on CTAF 122.8.
It is a breezy late afternoon in early spring: wind 220° at 12 knots, gusting to 18 knots. Runway 22's magnetic heading is 217°. The crosswind component is roughly 8–10 knots steady, with gusts pushing 14–16 knots — right at or slightly exceeding the C150's demonstrated crosswind capability of 12 knots. Visibility 10 SM, scattered clouds at 3,000 ft, light turbulence in the pattern.
You are on short final to Runway 22, 400 ft AGL, descending at 60 KIAS (Vref, flaps down). The runway is made; you are committed to the landing. Off Runway 22's landing end (heading 217°), the off-field environment is open water — Tampa Bay and the Hillsborough River. An engine failure or loss of control off that end is a ditching, not a field landing.
Aircraft: Cessna 150M, solo, within limits. Continental O-200-A, 100 hp, fixed-pitch prop, fixed gear, steam panel. The airplane is airworthy; nothing was written up.
Pilot: you — a Private pilot, roughly 150 hours total, current. You have landed in crosswinds before, but not in gusts this strong. Your personal minimums are 10 knots crosswind; this flight is at the edge of them. You did not brief a go-around decision point before entering the pattern.
- {'label': 'Field', 'value': 'KTPF · Peter O Knight'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '8 ft'}
- {'label': 'Aircraft', 'value': 'C150'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
Before we get into the decision tree — what do you know about crosswind landings in the C150? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB CEN23FA352 (2023, FATAL): A Van's RV-8 tailwheel aircraft nosed over during landing roll after a wind gust pushed the nose left. The pilot was unable to maintain directional control in crosswind conditions. The probable cause was the pilot's failure to maintain directional control during the landing roll with crosswind conditions.
NTSB ERA24LA063 (2023): A Cessna 150L on a personal flight struck bushes alongside a narrow turf runway during takeoff, causing the aircraft to yaw right. The pilot lost directional control and the aircraft impacted the ground and nosed over. The probable cause was the pilot's failure to maintain adequate clearance from obstacles, which resulted in a loss of directional control during takeoff.
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.
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 consistent thread: a crosswind landing in gusty conditions, an unstable approach that the pilot continued rather than aborted, a loss of directional control during rollout, and a ground loop or off-runway excursion. The C150's light wing loading and marginal control authority (100 hp, fixed-pitch prop) make it particularly vulnerable to gusts lifting a wing during rollout. At KTPF, Runway 22's landing-end environment is open water — a loss of control off that end is a ditching, not a field landing.
The real accidents cited above occurred at other airports and in other aircraft — NOT at KTPF. KTPF has its own accident history (see field dominant patterns), but these specific 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 critical decision point is BEFORE short final: establish a go-around decision point (e.g., 'if the airplane is more than 100 ft off centerline or if a gust lifts a wing significantly at 400 ft AGL, I will go around'). Once you are at 400 ft AGL committed to landing, the window to abort safely is closing. The C150's marginal climb performance (roughly 300 fpm on go-around) means you have altitude to work with, but not much. Commit to the go-around decision BEFORE you are in the position of having to make it.
Key lesson — The C150's demonstrated crosswind capability is 12 knots — a limit, not a target. Gusts that exceed that limit can overwhelm directional control during rollout, especially if airspeed is marginal. Establish a go-around decision point BEFORE short final. If the approach is unstable (off-centerline, wing lifted, or airspeed low), abort and go around. Maintaining airspeed above Vs0 (42 KIAS) through the rollout is critical — it preserves control authority to recover from a gust. At KTPF Runway 22, the landing-end environment is open water; a loss of control off that end is a ditching.
Debrief — teaching points
The C150's demonstrated crosswind capability is 12 knots — a tested limit, not a hard ceiling.
The C150M's demonstrated crosswind capability of 12 knots means the airplane was tested and found controllable in that crosswind. It does not mean the airplane is uncontrollable beyond 12 knots, nor does it mean 12 knots is safe for every pilot in every condition. Gusts that exceed the demonstrated capability can overwhelm directional control, especially during rollout when airspeed is low. Your personal crosswind limit should be lower than the demonstrated limit — typically 8–10 knots for a Private pilot in a C150. Know your limit and your aircraft's limit before you enter the pattern.
The C150's light wing loading makes it gust-sensitive during rollout.
The C150 weighs roughly 1,600 lbs at gross and has a wing area of 149 sq ft — a light wing loading. This makes the airplane responsive to gusts, especially during rollout when airspeed is low and control authority is marginal. A gust that lifts a wing 15–20° during rollout can be difficult to recover from if you are slow. Maintain airspeed above 50 KIAS through the rollout — do not rush to slow down. Vs0 (stall speed in landing configuration) is 42 KIAS; you need a margin above that to preserve control authority.
Establish a go-around decision point BEFORE short final.
A go-around decision should be made before you are committed to landing — typically at 500–600 ft AGL on final approach. Decide in advance: 'If the airplane is more than 100 ft off centerline, or if a gust lifts a wing significantly, or if airspeed is below 55 KIAS at 400 ft AGL, I will go around.' Once you are at 400 ft AGL, the window to abort safely is closing. The C150's climb performance on go-around is roughly 300 fpm — you have altitude to work with, but not much. Commit to the decision BEFORE you are in the position of having to make it.
Crosswind correction: crab on approach, wing-down on flare.
On approach, use the crab method — nose into the wind — to maintain alignment with the runway. As you flare, transition to the wing-down (forward-slip) method: lower the upwind wing and apply opposite rudder to correct drift. This keeps the fuselage aligned with the runway and prevents a side-load on the landing gear. The C150's fixed gear and light structure are not designed for side-loads; a landing with the fuselage crabbed can damage the gear.
At KTPF Runway 22, the landing-end environment is open water — a loss of control is a ditching.
Off Runway 22's landing end (heading 217°), the off-field environment is open water — Tampa Bay and the Hillsborough River. An engine failure or loss of directional control off that end is a ditching, not a field landing. There is no alternate landing surface. This is not hypothetical; it is the NLCD ground cover off that runway end. If you lose directional control during rollout and veer off the runway to the right, you are heading toward water. Recognize this risk and make your go-around decision accordingly.
Recognize when conditions exceed your personal minimums and commit to diversion.
Your personal crosswind limit is a decision, not a regulation. If the wind is at the edge of your limit and gusting, or if you are not comfortable with the approach, divert to a nearby airport with a more favorable wind direction. Diversion is not failure — it is airmanship. The NTSB precedents show that pilots who press on in marginal crosswind conditions often end up in ground loops or off-runway excursions. Recognize the limit and respect it.
Built from the real accident record
Scenario built from NTSB CEN23FA352 (2023 tailwheel loss of control in crosswind gust), ERA24LA063 (2023 C150L directional control loss on takeoff), GAA17CA105 (2016 PA-46 crosswind landing loss of control), CHI02TA149 (2002 Cessna A185F crosswind rollout veer), GAA17CA021 (2016 Mooney crosswind landing veer into water), and ERA11CA212 (2011 Mooney crosswind landing loss of control). Localized to KTPF.
NTSB reports: CEN23FA352 · WPR26LA042 · ERA24LA347 · ERA24LA063 · GAA17CA105 · CHI02TA149 · GAA17CA021 · ERA11CA212
ACS tasks: PA.II.E — Crosswind Takeoff and Landing · PA.II.F — Slip to a Landing · PA.IX.C — Emergency Approach and Landing · 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 Cessna 150M scenarios · More scenarios at KTPF