WPR13LA035 · Cessna 172M
Cessna 172M · Accident: powerplant system/component malfunction/failure while maneuvering
From Modesto City Co-Harry Sham Field (KMOD) to Modesto City Co-Harry Sham Field (KMOD)
Event
- NTSB case
- WPR13LA035
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 172M
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N21391
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Modesto City Co-Harry Sham Field (KMOD), Modesto, CATo Modesto City Co-Harry Sham Field (KMOD), Modesto, CA
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Maneuvering
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Powerplant system/component malfunction/failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft power plant
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During a photography mission, the pilot applied full engine power, and the engine speed dropped to idle. After attempting a series of troubleshooting steps, the engine did not respond, and the pilot performed a forced landing into a field. The airplane landed hard and nosed over. Postaccident examination of the engine revealed that the outer jacket of the throttle control cable had fragmented at the carburetor attach point, exposing the inner cable. Subsequent throttle control movement resulted in the cable flexing out of the jacket, rather than moving the throttle control arm at the carburetor. No life limit existed for the cable, which was most likely installed at the time of airframe manufacture, 38 years prior to the accident. Further examination of the engine revealed no additional evidence of a mechanical malfunction or failure that would have precluded normal operation.
Probable cause
Failure of the throttle control cable during maneuvering flight, which resulted in a partial loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13LA035
- Event ID
- 20121108X41006
- Case number
- WPR13LA035
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: fc5ca1eafd8eb7215b116b72adee5669c77ba7d54755dbe22f1ee64ae7d3bc7f; retrieved 2026-09-15T20:22:57.086Z.