Pitch Control Degradation on Short Final
Elevator trim runaway and restricted pitch authority force a non-standard approach and landing — decision-making under control constraint
The scenario
Departing St. Petersburg Clearwater International Airport (KPIE), Pinellas Park, FL — Runway 18, a local VFR flight in the Cessna 172R. Elevation 11 ft MSL. You are a Private pilot with roughly 250 hours total, current and proficient. The airplane is based at KPIE; you know the field well.
Weather: VFR throughout. OAT 24°C, dew point 18°C, altimeter 29.98. Scattered clouds at 3,500 ft, visibility 10 SM. Light winds from 180° at 6 kt — a light crosswind for Runway 18 (true heading 171°). Conditions are benign.
You depart Runway 18 at 0900 local, climb to 2,500 ft MSL, and fly a local practice area east of the field for 45 minutes: slow flight, stalls, and steep turns. The airplane handles normally throughout. You return to KPIE and request a straight-in approach to Runway 18. Tower clears you for the approach.
On downwind at 1,500 ft MSL, 3 nm from the runway, you begin the descent. You reduce power to 1,500 RPM, trim for the descent, and configure: 10° flaps, airspeed 90 KIAS. The approach is stable. At 2 nm, you add full flaps (30°) and slow to 70 KIAS — just above Vref (62 KIAS for short-field landing). The runway is in sight.
At 1 nm on final, 500 ft AGL, you notice the pitch trim wheel feels stiff — stiffer than normal. You apply gentle forward pressure on the yoke to maintain descent. The trim wheel does not respond smoothly; it feels like it is binding or stuck. You can still control pitch with the yoke, but the trim is not cooperating. You are 0.5 nm from the runway, 300 ft AGL, committed to the approach.
Aircraft: Cessna 172R, solo, full fuel, within limits. Fuel-injected Lycoming IO-360-L2A, fixed-pitch prop, fixed gear, steam panel. The airplane was airworthy at preflight — you checked the flight controls, trim wheel moved freely on the ground. Something has changed in flight.
Pilot: you — a Private pilot, current, 250 hours. You have 80 hours in the C172R. You are familiar with KPIE and Runway 18. You are not in an emergency yet, but the pitch trim is not normal and you are on short final.
- {'label': 'Field', 'value': 'KPIE · St. Petersburg Clearwater'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '11 ft'}
- {'label': 'Aircraft', 'value': 'C172R'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we get into the decision tree — what do you know about pitch trim malfunctions in the C172R? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB MIA06LA091 (2006): A Cessna 172R lost control during initial climb when excessive pitch attitude developed and nose-down trim proved ineffective. The flight instructor declared an emergency and attempted to return to the airport, but the aircraft stalled. The probable cause was the flight instructor's failure to maintain airspeed while maneuvering, with a contributing factor of an undetermined elevator control malfunction that required excessive forward pressure on the yoke to maintain pitch control. The malfunction was never fully diagnosed — the aircraft was destroyed and the investigation could not isolate the cause.
NTSB CEN09IA456 (2009): A Cessna 172R experienced loss of throttle control during a practice instrument approach when the throttle cable became unscrewed from the rod end of the throttle assembly. The incident resulted from detachment of the throttle control cable, with a contributing factor of lack of redundant means to preclude cable detachment. The pilot recovered by declaring an emergency and returning to the airport.
NTSB DEN07CA154 (2007): A Cessna 172R bounced twice during landing and the student pilot executed a go-around. After a successful second landing, the student discovered the left rudder pedal was inoperative. The accident resulted from the student pilot's improper flare and recovery from the bounced landing, which buckled and bent the firewall — the damage rendered the rudder control ineffective. This case shows how hard landings can damage the airframe in ways that are not immediately obvious.
NTSB WPR23LA216 (2023): A Cessna 172R nosed over during landing when the upper nose wheel torque link bolt failed due to fractures sustained during a prior collision with a fuel truck. The failure resulted from maintenance personnel's failure to replace the damaged bolt and the pilot's inadequate preflight inspection. The pilot did not detect the damage during the preflight walk-around.
The regional precedent NTSB LAX89LA222 (1989, fatal, Grumman AA-1C) shows the danger of continuing a descent with degraded control authority: the pilot stalled on final approach in crosswind conditions and impacted the ocean short of the runway. The lesson is consistent: on short final with control uncertainty, a go-around is the safest option.
The real accidents cited above occurred at other airports and in other aircraft — NOT at KPIE. However, KPIE's own accident corpus shows LOSS_OF_CONTROL_INFLIGHT (21.2%), LOSS_OF_CONTROL_GROUND (15.2%), and STALL_SPIN (12.1%) as the dominant patterns. This scenario reflects those patterns: a flight control malfunction on approach, the decision to continue or go around, and the consequences of each choice.
The consistent thread: flight control malfunctions in the C172R are rare but serious. They can result from maintenance errors (cable detachment, rigging issues, post-collision damage), mechanical binding, or undetermined causes. The correct response is always the same: if pitch control is uncertain or degraded on short final, go around. Land at the nearest suitable airport and have maintenance inspect. Do not attempt to land with compromised control authority.
Key lesson — A stiff or unresponsive pitch trim wheel on short final is a warning sign of a flight control malfunction. You can still control pitch with the yoke — the elevator is independent of the trim system — but the malfunction itself is a maintenance issue. At 0.5 nm and 300 ft AGL, a go-around is the safest option. Climb to a safe altitude, troubleshoot if possible, and either attempt another approach or divert to a nearby airport for maintenance inspection. Hard landings resulting from continued approaches with degraded control authority can damage the airframe (firewall, nose gear, rudder linkage) in ways that are not immediately obvious. Airmanship means recognizing the limits of your control authority and making the conservative choice.
Debrief — teaching points
Pitch trim is a control aid, not a control necessity.
The elevator control and the pitch trim system are independent. If the trim wheel is stiff, binding, or unresponsive, you can still control pitch with the yoke alone. The elevator control surfaces will respond to yoke input. However, a stiff or unresponsive trim wheel is a sign of a mechanical problem — a cable tension issue, a rigging error, or a post-maintenance mistake. It is not something to ignore or troubleshoot in flight on short final. Recognize it, go around, climb to a safe altitude, and have maintenance inspect.
On short final with control uncertainty, a go-around is the safest option.
At 0.5 nm and 300 ft AGL, you are committed to landing in terms of proximity to the runway, but you are NOT committed in terms of safety. If you notice anything unusual about pitch control — stiffness, binding, unresponsiveness, or excessive force required — a go-around is the correct decision. Climb to 1,500 ft, re-enter the pattern, and either attempt another approach or divert to a nearby airport. The cost of a go-around is a few minutes and some fuel. The cost of continuing a descent with degraded control authority is a hard landing, airframe damage, or a stall.
Hard landings from continued approaches with degraded control can damage the airframe in non-obvious ways.
NTSB DEN07CA154 shows a Cessna 172R that bounced during landing and the student executed a go-around. On the second landing, the student discovered the left rudder pedal was inoperative — the hard landing had buckled and bent the firewall, rendering the rudder control ineffective. The damage was not visible during the preflight walk-around; it only became apparent after the second landing. A hard landing is not just an embarrassment — it is a potential source of hidden airframe damage. If you land hard, have maintenance inspect the firewall, nose gear, and control linkages.
Preflight inspection of flight controls is essential — move the yoke and trim wheel through their full range.
During the preflight walk-around, physically move the yoke (pitch, roll, yaw) through its full range and confirm smooth, responsive movement. Move the trim wheel through its full range and confirm smooth, responsive movement. Check for any binding, stiffness, or unusual resistance. A trim wheel that is stiff on the ground will be stiff in the air. A cable that is loose or mis-rigged will show up in the preflight. NTSB WPR23LA216 shows a pilot who did not detect a damaged nose wheel torque link bolt during the preflight — the damage was there, but the pilot did not look carefully enough. Thorough preflight inspection is your first line of defense against flight control malfunctions.
Vref and airspeed margin are critical on any approach with control uncertainty.
Vref for the C172R with full flaps is 62 KIAS. Maintaining a 5–10 kt margin above Vref (65–72 KIAS) is standard practice. On an approach with pitch control uncertainty, maintain that margin or increase it. Do not slow to Vref or below. The slower you fly, the less control authority you have and the more susceptible you are to a stall. If you are flying an approach with a stiff trim wheel, maintain 70–75 KIAS (8–13 kt above Vref) to ensure adequate control authority and stall margin.
Trim binding can be transient — cycling the trim wheel at altitude may free it up.
A trim wheel that is stiff or binding on short final may be a transient mechanical issue — a cable tension problem, a pulley misalignment, or a rigging error that can be cleared by cycling the trim wheel through its full range. If you go around and have time at altitude, try cycling the trim wheel forward and aft several times. If it frees up, you can attempt another approach with full control authority. If it remains stiff, divert to a nearby airport for maintenance inspection.
Built from the real accident record
Scenario built from NTSB MIA06LA091 (2006 C172R elevator control malfunction / excessive pitch trim), CEN09IA456 (2009 C172R throttle cable detachment / loss of control), DEN07CA154 (2007 C172R rudder control loss from firewall damage), WPR23LA216 (2023 C172R nose wheel steering loss / inadequate preflight), and regional precedents LAX89LA222 (1989 stall on final approach), ERA10CA300 (2010 stall during climbing turn), ATL83LA356 (1983 stall during short final). Anonymized and localized to KPIE.
NTSB reports: WPR23LA216 · CEN09IA456 · DEN07CA154 · MIA06LA091 · LAX89LA222 · ERA10CA300 · ATL83LA356
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors · PA.II.A — Preflight Assessment · PA.III.C — Approach and Landing
Relevant FARs: §91.3 · §91.7 · §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 Cessna 172R scenarios · More scenarios at KPIE