Trim Runaway on Short Final
Elevator trim malfunction during approach to Lakeland Linder — reduced control authority and a decision window measured in seconds
The scenario
Departing Lakeland Linder International Airport (KLAL), Lakeland, FL — Runway 10, a 30-minute local flight in a Cessna 172R to practice instrument approaches. Elevation 142 ft MSL. The field is towered, Class D airspace, ceiling 2,600 ft MSL.
Weather is VFR: scattered clouds at 3,500 ft, visibility 10 SM, wind 120° at 14 gusting to 22 knots. Runway 10's magnetic heading is 090°; the wind is a 30° crosswind gust, right on the limit of the C172R's demonstrated crosswind capability (15 knots). The tower has advised that Runway 28 is available (heading 270°) and would be a direct downwind with a lighter crosswind component, but you have briefed Runway 10 and the approach is set up.
You are on a practice instrument approach to Runway 10, descending through 1,200 ft AGL on a 5-mile final. The autopilot is off; you are hand-flying. The approach is stable: 62 KIAS (Vref short-field), 10° flaps, descent rate 300 fpm, glide slope centered. The tower has cleared you to land.
Aircraft: Cessna 172R, solo, 1,800 lb (within limits). Fuel-injected Lycoming IO-360-L2A, 160 hp. Fixed gear, fixed-pitch prop, fuel selector BOTH. Steam panel (vacuum-driven gyro, turn coordinator, attitude indicator). The airplane was released from maintenance yesterday after a 100-hour inspection and an elevator trim cable replacement. You did a thorough preflight; nothing was written up.
Pilot: you — a Private pilot, current, roughly 250 hours total. You have 15 hours in the C172R and are comfortable with the type. You have not landed in gusting crosswind conditions above 12 knots before. This is a learning flight.
- {'label': 'Field', 'value': 'KLAL · Lakeland Linder'}
- {'label': 'Runways', 'value': '5/23 · 10/28'}
- {'label': 'Elevation', 'value': '142 ft'}
- {'label': 'Aircraft', 'value': 'C172R'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before the decision tree — what do you know about elevator trim malfunctions and flight-control restrictions 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 on a training flight experienced loss of 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 accident was fatal.
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 recover and land safely.
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 probable cause was the failure of the nose wheel upper torque link bolt, with contributing factors of maintenance personnel's failure to inspect and replace the fractured bolt and the pilot's oversight during preflight.
NTSB ERA21LA119 (2021): A Cessna 172R on a personal flight veered left off the runway during landing in gusting crosswind conditions and struck the ground with the propeller and left wing tip. The accident was attributed to the pilot's failure to maintain directional control during landing in a gusting crosswind. The crosswind conditions exceeded the pilot's experience level.
The scenario at KLAL is localized to Lakeland Linder International Airport, a towered Class D field with four runways (05/23 and 10/28). The off-field environment off Runway 10's departure end (heading 090°) is marginal — mostly low-density development, open developed areas (parks/large lots), and dense development. An engine failure on the Runway 10 departure would be a forced landing in a developed area, not a ditching. The crosswind environment at KLAL is real: gusting winds from the southeast (120°) create a 30° crosswind on Runway 10 and a lighter crosswind on Runway 28 (heading 270°). The real accidents cited above occurred at other airports and in other aircraft — NOT at KLAL. The scenario is localized to KLAL to make the field environment and the control-system risk real for you as a student here.
The consistent thread across all these events: flight-control malfunctions in the C172R are insidious. They can develop gradually (a loose trim cable fitting from maintenance) or suddenly (a throttle cable detachment). The first sign is often subtle — a trim change, a control force imbalance, or an inability to maintain pitch. By the time the malfunction is obvious, the pilot may be committed to landing in a degraded control state. The fix — recognizing the malfunction early and executing a go-around — is simple. The failure is always a delay or a decision to continue landing with a questionable control system.
Key lesson — In the C172R, an uncommanded trim change on short final is a red flag for a control system problem. The trim cable replacement you just had done is a high-risk maintenance item — a loose fitting or improper torque can cause a trim malfunction. Recognize the malfunction early (a pitch change without your input, a change in control force), declare a go-around immediately, and do not land with a degraded control system. At KLAL, the crosswind environment is also real: gusting winds can exceed the demonstrated crosswind capability. Recognize when conditions exceed your personal minimums and request a different runway or divert. An unstable approach with a degraded control system should never be continued to landing.
Debrief — teaching points
Flight-control malfunctions in the C172R are often subtle and develop gradually.
The NTSB MIA06LA091 case shows a C172R with an undetermined elevator control malfunction that required excessive forward pressure on the yoke to maintain pitch control. The malfunction was not obvious until the pilot was in a critical phase of flight (initial climb). The CEN09IA456 case shows a throttle cable detachment that happened during an approach. The WPR23LA216 case shows a nose wheel steering failure that resulted from a loose bolt left over from a prior collision. All of these malfunctions could have been caught with a thorough preflight inspection or a careful control check after maintenance. After any flight-control maintenance (trim cable replacement, control surface work, etc.), the first flight should include a careful control check and a low-altitude go-around practice before committing to a full-stop landing.
Recognize an uncommanded trim change as a red flag for a control system problem.
An uncommanded pitch change during a stable approach — especially on short final — is a sign that something is wrong with the flight-control system. It could be a loose trim cable fitting, a trim motor malfunction, or a control surface restriction. Do not assume it is a one-time event. Do not assume you can correct it and continue landing. An uncommanded trim change on short final warrants an immediate go-around. Declare the go-around, climb to a safe altitude, and assess the control system. If the trim behaves normally on the second approach, you can land. If it moves again, do not land — divert to a nearby airport and have the airplane inspected.
Preflight inspection of flight controls is non-negotiable.
The C172R preflight should include a trim check: set the trim to neutral, move the yoke full forward and aft, and confirm smooth, full travel without binding or stiffness. Check the trim wheel (or switch) for smooth operation. After any flight-control maintenance, this check is critical. The WPR23LA216 pilot's 'adequate preflight' missed a loose nose wheel bolt that had been fractured in a prior collision. The lesson: a preflight is only as good as the attention you give it. If something feels wrong — a stiff control, an unusual trim position, a binding — do not fly the airplane. Have it inspected.
The C172R's demonstrated crosswind capability is 15 knots; gusts above that are outside the tested envelope.
The ERA21LA119 case shows a C172R that veered off the runway during landing in gusting crosswind conditions. The crosswind component exceeded the pilot's experience and the aircraft's demonstrated capability. The GAA17CA105 and GAA19CA170 cases show similar accidents in other aircraft — loss of directional control during landing in gusting crosswinds. At KLAL, a wind of 120° at 14 gusting to 22 knots creates a 30° crosswind on Runway 10 with a steady component of ~12 knots and gusts to ~20 knots. This is at or exceeding the demonstrated limit. Runway 28 (heading 270°) would be a direct downwind with a lighter crosswind component. Recognize when crosswind conditions exceed the demonstrated capability and request a different runway or divert.
An unstable approach with a degraded control system should never be continued to landing.
If the approach becomes unstable — drift, loss of alignment, high descent rate, high airspeed — and the control system is questionable (trim malfunction, heavy control forces, stiff controls), a go-around is the correct decision. The runway will still be there after you climb to a safe altitude, assess the control system, and set up a second approach. Landing with a degraded control system is not acceptable. The MIA06LA091 pilot attempted to return to the airport after recognizing a control malfunction during climb; the aircraft stalled. The lesson: recognize the malfunction early, when you have altitude and options. A go-around on short final is not a failure — it is airmanship.
After maintenance, the first flight should include a careful control check and a low-altitude go-around practice.
The scenario assumes the C172R had an elevator trim cable replacement during a 100-hour inspection. This is a high-risk maintenance item — a loose fitting or improper torque can cause a trim malfunction. The first flight after this maintenance should include a careful control check (full forward and aft yoke travel, smooth trim operation) and a low-altitude go-around practice before committing to a full-stop landing. If anything feels wrong — stiff controls, unusual trim behavior, binding — do not land. Have the airplane inspected. The mechanic in the scenario later found a loose trim cable fitting that was not fully torqued — exactly the kind of maintenance error that can cause a malfunction.
Built from the real accident record
Scenario built from NTSB MIA06LA091 (2006 C172R elevator control malfunction / trim runaway on climb), CEN09IA456 (2009 C172R throttle cable detachment / loss of power control), WPR23LA216 (2023 C172R nose wheel steering failure / inadequate preflight), and regional precedents ERA21LA119 (2021 C172R crosswind loss of control), GAA17CA105 (2016 Piper crosswind excursion), GAA19CA170 (2019 Piper tailwheel crosswind loss of directional control). Anonymized and localized to KLAL.
NTSB reports: WPR23LA216 · CEN09IA456 · DEN07CA154 · MIA06LA091 · GAA17CA105 · ERA21LA119 · GAA19CA170
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.B — Engine Starting / Systems Preflight · PA.V.A — Preflight Inspection · PA.VII.A — Normal Approach and Landing
Relevant FARs: §91.3 · §91.7 · §91.13 · §91.405
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 KLAL