Control Restriction on Short Final
A flight-control cable failure forces a reduced-control approach to landing — recognition, adaptation, and precision are the difference between a safe landing and loss of control.
The scenario
Departing Venice Municipal Airport (KVNC), Venice, FL — Runway 13, a local VFR flight in light winds. Elevation 18 ft MSL. The field is non-towered (CTAF); you will self-announce on 122.8 MHz. Runway 13 is 5,640 ft of asphalt, heading 135° true. Off the runway 13 departure end (northeast), the off-field environment is open water — Charlotte Harbor and the Gulf of Mexico. Off the runway 31 end (southwest), the environment is open field and scattered development.
Weather: clear skies, visibility 10 SM, light winds from 160° at 5 kt, OAT 24°C, altimeter 30.01. A perfect VFR day. You are planning a 30-minute local flight — climb to 1,500 ft AGL, cruise the coast, and return to KVNC for landing on Runway 13.
Aircraft: Cessna 172M, solo, full fuel, within limits. The 172M is the carbureted, 150-hp variant — older and less powerful than the 172N. Climb performance is marginal, especially in heat or at gross weight. The airplane was last flown three days ago; the preflight was clean. Nothing was written up. The airplane is airworthy.
Pilot: you — a Private pilot, current, roughly 250 hours total. You have 40 hours in the 172M. You are familiar with the airplane and the field. Today is a routine local flight.
What you do not know: during the previous flight, the right aileron control cable was subjected to stress during a steep turn. The cable has a hairline crack in the outer jacket near the right wing root — not visible during a standard preflight walk-around. The crack will allow corrosion to begin. The cable is still functional, but it is weakened. Stress during landing approach will cause it to fail.
- {'label': 'Field', 'value': 'KVNC · Venice'}
- {'label': 'Runways', 'value': '4/22 · 13/31'}
- {'label': 'Elevation', 'value': '18 ft'}
- {'label': 'Aircraft', 'value': 'C172M'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we begin — what do you know about flight-control cable failures in the Cessna 172M? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB ERA12FA484 (2012, FATAL): A Cessna 172M on approach to landing experienced in-flight failure of the right aileron control cable due to corrosion. The cable had a hairline crack in the outer jacket, which allowed corrosion to develop. The crack was not visible during a standard preflight walk-around. During landing approach, the stress of control inputs caused the cable to fail completely. The pilot lost roll control and the airplane impacted water. The probable cause was maintenance personnel's improper lubrication of the control cable and failure to detect severe corrosion during inspection. The accident was fatal.
NTSB CEN24LA366 (2024): A Cessna 172M experienced electrical failure and flight control system interference during cruise. The pilot diverted to a nearby airport and attempted a landing. The accident resulted from excessive airspeed during a no-flap landing and failure to attain a proper touchdown point, with contributing factors including instrument panel wiring interference with the flight control system. The airplane overran the runway but the pilot survived.
NTSB WPR13LA035 (2012): A Cessna 172M on an aerial photography mission experienced loss of engine power when the pilot applied full throttle during climb. The accident resulted from failure of the throttle control cable outer jacket, which fragmented and prevented proper throttle control. The pilot made a forced landing.
NTSB NYC08LA228 (2008): A Cessna 172M on an instructional flight experienced a seat failure during takeoff when the CFI's seat rolled backward, causing loss of control and a ground strike. The accident resulted from inadequate inspection of worn seat tracks that exceeded acceptable wear limits.
The common thread in these C172M accidents: control system failures (aileron cable, throttle cable, seat) that were not detected during preflight inspection. A hairline crack in a control cable outer jacket is often invisible during a standard walk-around. It requires close inspection, borescope examination, or a maintenance history review to detect. The failure typically occurs under stress — during takeoff, climb, or landing approach — when control inputs are large and precise.
At Venice Municipal Airport (KVNC), the off-field environment off Runway 13's departure end is open water — Charlotte Harbor and the Gulf of Mexico. An engine failure on the Runway 13 departure at low altitude is a ditching. A flight-control failure on approach to Runway 13 is a ground loop or impact with terrain. The scenario is localized to KVNC to make the off-field environment real and consequential for you as a student here.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Venice Municipal Airport. KVNC has its own accident history (see field dominant patterns: LOSS_OF_CONTROL_INFLIGHT 24.4%, FORCED_LANDING 12.2%, SPATIAL_DISORIENTATION 12.2%, HARD_LANDING 12.2%, LOSS_OF_CONTROL_GROUND 12.2%), but these specific NTSB events happened elsewhere. The scenario is localized to KVNC to make the decision-making and off-field consequences real for you as a student here.
The consistent lesson across all these events: control system failures in the Cessna 172M are rare but catastrophic. They are not detectable by a standard preflight walk-around. They occur under stress. The only defense is a thorough maintenance history review, a detailed preflight inspection (including borescope examination of control cables if there is any history of corrosion or improper maintenance), and immediate recognition and response if control feels wrong during flight. If control feels wrong on approach, go around. Do not attempt to land with compromised flight control.
Key lesson — A hairline crack in a flight-control cable outer jacket is invisible during a standard preflight walk-around. It can fail under the stress of landing approach, resulting in loss of control. If control feels wrong on approach — stiff aileron, sluggish elevator, or unresponsive rudder — go around immediately. Do not attempt to land with compromised flight control. At KVNC, the off-field environment off Runway 13's departure end is open water; a control failure on approach to Runway 13 is a ditching or ground loop. The correct response is to recognize the problem early, go around, diagnose, and make a sound decision — land on a different runway, divert to another airport, or declare an emergency.
Debrief — teaching points
A hairline crack in a control cable is invisible during a standard preflight walk-around.
Control cables in the Cessna 172M are subject to corrosion if they are improperly lubricated or if the protective outer jacket is damaged. A hairline crack in the outer jacket allows moisture and corrosion to develop inside. The crack is often invisible to the naked eye — it requires close inspection, borescope examination, or a maintenance history review to detect. The cable remains functional until it is subjected to stress (takeoff, climb, or landing approach), at which point it can fail suddenly. A standard preflight walk-around does not include borescope inspection of control cables. If there is a history of improper maintenance, corrosion, or control-system work, request a detailed inspection before flight.
Control feel is the first warning sign of a flight-control failure.
If the aileron, elevator, or rudder feels stiff, sluggish, or unresponsive during flight, that is a warning sign of a control-system problem. The problem may be a cable failure, a jam in the control linkage, or a mechanical restriction. Do not ignore it. If you notice control feel degradation on approach, go around immediately. Do not attempt to land with compromised flight control. Trim can help with pitch, but it cannot replace aileron or rudder control. At low altitude on approach, you have seconds to decide — go around or continue. The correct answer is always to go around.
A go-around at 50 ft AGL is the correct response to control degradation.
If you discover a control problem on final approach at 50 ft AGL, the correct response is to go around immediately: advance power to 1,500 RPM, retract flaps to 10°, and climb at 70 KIAS (Vy for the C172M is 78 KIAS, but 70 KIAS is safe for a go-around). Announce the go-around on CTAF. Climb back to pattern altitude. Test the controls in level flight. Diagnose the problem. Make a sound decision: land on a different runway, divert to another airport, or declare an emergency. A go-around at 50 ft AGL is not a failure — it is airmanship. The alternative — continuing the landing with compromised control — is the failure.
At KVNC, the off-field environment off Runway 13's departure end is open water.
The off-field environment off Runway 13's departure end (heading 135°) is open water — Charlotte Harbor and the Gulf of Mexico. There is no alternate landing surface. An engine failure on the Runway 13 departure at low altitude is a ditching. A flight-control failure on approach to Runway 13 is a ground loop or impact with terrain. Runway 31's departure end (heading 315°) is open field and scattered development — a more forgiving off-field environment. If you have a choice of runways and a control problem, choose the runway with the more forgiving off-field environment.
Maintenance history is part of the preflight.
Before you fly the Cessna 172M, review the maintenance log. Look for entries related to control-system work, cable replacement, corrosion, or improper lubrication. If there is a history of control-system issues, request a detailed inspection. If the airplane has been sitting for a long time or has been exposed to moisture, corrosion of control cables is a risk. A standard preflight walk-around does not include borescope inspection of control cables, but a detailed maintenance review can alert you to risk factors. If you are unsure, ask the maintenance team to inspect the control cables before you fly.
Built from the real accident record
Scenario built from NTSB ERA12FA484 (2012, C172M right aileron cable failure / loss of control), CEN24LA366 (2024, C172M flight control interference / runway overrun), WPR13LA035 (2012, C172M throttle cable failure), and NYC08LA228 (2008, C172M seat failure). Localized to Venice Municipal Airport (KVNC), Venice, FL. Regional precedents: CHI91DCJ01, ANC93LA040, FTW89FA151 (VFR-into-IMC spatial disorientation events in Florida/Gulf region).
NTSB reports: ERA12FA484 · CEN24LA366 · WPR13LA035 · NYC08LA228 · CHI91DCJ01 · ANC93LA040 · FTW89FA151
ACS tasks: PA.I.F — Weather Information · PA.VIII.D — Approach and Landing · PA.VIII.E — Go-Around · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors
Relevant FARs: §91.3 · §91.13 · §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 172M scenarios · More scenarios at KVNC