Pitch Control Anomaly on Short Final
Elevator trim runaway and a non-towered field — managing a degraded control situation to a safe landing
The scenario
Departing Tampa North Aero Park Airport (X39), Tampa, FL — Runway 14, a 3,541 ft asphalt strip. Elevation 68 ft MSL. Non-towered field; you will self-announce on CTAF 122.8. This is a local practice flight, 0.8 nm northeast of the field, 20 minutes of pattern work.
Conditions: VFR, clear skies, visibility 10 SM, wind 140° at 5 kt (nearly aligned with Runway 14). OAT 24°C, altimeter 30.01. A textbook Florida morning for pattern work.
Aircraft: Cessna 172R, solo, 1,800 lbs (well within limits), full fuel. Fuel-injected Lycoming IO-360-L2A, 160 hp. Fixed gear, fixed-pitch prop, steam panel with vacuum-driven attitude indicator and heading indicator. You completed a standard preflight inspection — no squawks noted. The airplane has been in regular service; the last 100-hour inspection was 8 hours ago.
Pilot: you — a Private pilot, current, 280 hours total, 120 hours in the C172R. You have 15 landings at X39 in the past two months. This is a routine practice flight.
Plan: Depart Runway 14, climb to 1,500 ft AGL, enter left downwind, and execute three full-stop landings. The off-field environment off Runway 14 (climb-out heading 141°) is medium development, low-density development, and wooded wetland — not ideal for an engine-out forced landing, but not open water. Off Runway 32 (reciprocal, heading 321°) is the same: developed and wooded. This field is surrounded by urban/suburban terrain.
- {'label': 'Field', 'value': 'X39 · Tampa North Aero Park'}
- {'label': 'Runways', 'value': '14/32'}
- {'label': 'Elevation', 'value': '68 ft'}
- {'label': 'Aircraft', 'value': 'C172R'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we begin — what do you know about elevator trim runaway and flight-control malfunctions in the C172R? (Pick all that apply.)
What the record shows
What the NTSB files show
NTSB MIA06LA091 (2006): A Cessna 172R experienced loss of pitch 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 in the stall.
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 was able to manage the partial power loss and land safely, but the incident highlighted the vulnerability of single-point mechanical failures in flight control systems.
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 control malfunction was not discovered until after the flight.
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 structural damage during the preflight walk-around.
The common thread in these accidents: control malfunctions in the C172R are often subtle at first — heavy pitch control, sluggish response, or a trim system that does not behave as expected. Pilots who recognize these anomalies early and go around have time to diagnose and manage the problem. Pilots who continue the approach or landing with a known control malfunction risk a hard landing, loss of control, or structural damage.
Tampa North Aero Park Airport (X39) is a non-towered field in the Tampa Class B environment. The off-field environment off both Runway 14 and Runway 32 is medium development, low-density development, and wooded wetland — not ideal for a forced landing. A control malfunction at low altitude over this terrain is a serious situation. Early recognition, a go-around, and a controlled approach with the malfunction managed is the correct response.
The real accidents cited above occurred at other airports and in other aircraft — NOT at X39. This scenario is localized to X39 to make the non-towered environment and the off-field terrain real and consequential for you as a student here.
Key lesson — Elevator trim runaway and other flight-control malfunctions in the C172R are rare but catastrophic if not managed correctly. The first sign is often heavy pitch control or a trim system that does not respond as expected. At low altitude on approach, the correct response is to go around immediately — climb away, diagnose the problem, and attempt a controlled approach with the malfunction managed. Continuing an approach with a known control malfunction risks a hard landing, loss of control, or structural damage. A preflight check of the elevator trim system — cycling the trim wheel through its full range and confirming smooth, responsive movement — can catch some malfunctions before flight. But some malfunctions develop in flight and are only detected during the approach. When they do, go around.
Debrief — teaching points
Elevator trim runaway is rare but catastrophic — recognize it early.
In the C172R, the elevator trim is electric, driven by a motor controlled by a trim wheel on the yoke. A runaway trim system will drive the elevator to an extreme pitch attitude, making pitch control difficult or impossible. The first sign is often heavy pitch control or a trim wheel that moves without your input. If you notice the trim wheel moving on its own or pitch control becoming progressively heavier, this is a red flag. At low altitude on approach, the correct response is to go around immediately — climb away, diagnose, and attempt a controlled landing with the malfunction managed.
A preflight check of the elevator trim system can catch some malfunctions.
Before each flight, cycle the elevator trim wheel through its full range and confirm the elevator responds smoothly. The trim wheel should move freely, and the elevator should follow the trim input without lag or resistance. If the trim wheel feels stiff, moves in jerks, or the elevator does not respond smoothly, do not fly the airplane — report it to maintenance. Some malfunctions will not be detected in a preflight check, but a thorough check can catch obvious problems.
Manual pitch control can manage a trim malfunction — but the control forces will be heavy.
If the elevator trim runs away nose-up, you can still control pitch manually by applying forward pressure on the yoke. However, the control forces will be heavy, and the longer the trim runs away, the heavier the forces become. At low altitude on approach, heavy pitch control is a distraction you do not need. The correct response is to go around and either disable the trim system (pull the trim circuit breaker) or manage the pitch control manually with the trim disabled.
The C172R trim circuit breaker is your emergency tool for trim runaway.
If the elevator trim runs away, you can disable the trim system by pulling the trim circuit breaker on the panel. This will stop the trim motor and prevent further trim input. The nose-up (or nose-down) trim that has already been applied will remain, but no more trim will be added. You can then control pitch manually with forward (or back) pressure on the yoke. Knowing where the trim circuit breaker is located and being willing to pull it is essential for managing a trim runaway.
At X39, a control malfunction on approach is a serious situation.
X39 is a non-towered field in the Tampa Class B environment. The off-field environment off both Runway 14 and Runway 32 is medium development, low-density development, and wooded wetland — not ideal for a forced landing. A control malfunction at low altitude over this terrain leaves little margin for error. Early recognition, a go-around, and a controlled approach with the malfunction managed is the correct response. Do not attempt to land with a known control malfunction.
A go-around is not a failure — it is airmanship.
If you detect a control anomaly on approach — heavy pitch control, sluggish response, trim runaway, or any other malfunction — go around. Climb away, diagnose the problem, and attempt a controlled approach with the malfunction managed. A go-around costs time and fuel, but it gives you altitude, distance, and time to think. Continuing an approach with a known control malfunction risks a hard landing, loss of control, or structural damage. A go-around is always the correct decision when the airplane is not behaving as expected.
Built from the real accident record
Scenario built from NTSB MIA06LA091 (2006 C172R elevator control malfunction / trim runaway), CEN09IA456 (2009 C172R throttle cable detachment), WPR23LA216 (2023 C172R nose wheel torque link failure), and DEN07CA154 (2007 C172R rudder control loss). Localized to Tampa North Aero Park Airport (X39), a non-towered field in the Tampa Class B environment.
NTSB reports: WPR23LA216 · CEN09IA456 · DEN07CA154 · MIA06LA091 · CHI91DCJ01 · ANC93LA040 · FTW89FA151
ACS tasks: PA.I.F — Weather Information · PA.III.A — Normal Takeoff and Climb · PA.III.B — Normal Approach and Landing · PA.IX.C — Emergency Approach and Landing · PA.IX.D — Systems and Equipment Malfunctions · PA.I.H — Human Factors
Relevant FARs: §91.3 · §91.13 · §91.185 · §91.407
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 X39