ERA13LA410 · Cessna 188B
Cessna 188B · Accident: flight control system malfunction/failure while maneuvering
From Lydia, SC to Woodrow, SC (no airport)
Event
- NTSB case
- ERA13LA410
- 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 188B
- Aircraft type
- Cessna 188
- 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
- N59JK
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lydia, SCTo Woodrow, SC (no airport)
- Aircraft age
- About 40 years (built 1973)
- 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 137: Agricultural
- 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 · low-altitude flying
- 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
- Flight control system 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 handling/service
- Aircraft › Aircraft systems
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While spraying a cotton field, the pilot completed a pass and, at the end of the field, pulled up to turn to the right. During the climb, he applied right rudder, but the right rudder pedal assembly broke off, allowing the pedal full travel to the back of the hopper tank. The pilot was able to return to the airfield and make an uneventful landing, but during the landing roll, the airplane began to turn left, and the pilot had no way to correct since the right rudder, right brake, and right tailwheel steering were not operable. The airplane then exited the left side of the runway and entered a soybean field, causing the right main landing gear to collapse and the right wing to impact the ground and sustain substantial damage.
Postaccident examination of the rudder pedal assembly revealed the right rudder pedal arm had separated from its mounting location on the right rudder bar. Both were constructed of steel tubing. The external surfaces of the right rudder pedal arm exhibited areas with disbonded topcoat paint and exposed steel with minor surface corrosion. Internally, the right rudder pedal arm exhibited heavy rust scaling over all surfaces and rust scale that had sloughed from the surfaces had collected at the base of the right rudder pedal arm, where it attached to the right rudder bar. Although measurements of the tube wall's thickness at the top of the rudder pedal arm appeared to be full thickness, with measurements of 0.054 inch, 0.053 inch, 0.056 inch, and 0.055 inch (measured at 90 degree intervals around the circumference), measurements of the tube wall's thickness at the point of the fracture were only 0.030 inch at the thickest point and 0.013 at the thinnest point.
The airplane was equipped with a liquid dispersal system, including a hopper tank located immediately forward of the cockpit. Remnants of corrosion product had adhered to silicone plugs that were at the top of the rudder pedal arm tubing, indicating that the corrosion product was present before the application of the silicone sealant. The plugs had likely been inserted in an attempt to keep contaminants (chemicals from the hopper tank and water from cleaning) out of the rudder pedal arms.
Review of the Service Manual and Illustrated Parts Catalog revealed that the manufacturer had published inspection criteria for the airplane based on operating usage and operating environment. The criteria provided mandatory inspection intervals for components and airplane structures. The manufacturer also offered a supplemental Corrosion Prevention and Control Program to help prevent or control corrosion in the airplane's primary structure so that it did not cause a risk to continued airworthiness as the airplane aged. A supplemental inspection document also included guidance regarding corrosion inspection and corrosion control of the rudder system. Review of the maintenance records revealed no record of the modifications and no record of an inspection of the rudder system per the supplemental inspection document.
Probable cause
A failure of the right rudder pedal arm due to corrosion as a result of inadequate maintenance and inspection of the rudder pedal assembly.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13LA410
- Event ID
- 20130910X93340
- Case number
- ERA13LA410
- 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, coordinates. 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: f59a16daf0e64580d54a130de45925ed9da3b8587a6417355e6d948ea277e1cb; retrieved 2026-09-15T22:49:21.689Z.