CEN20CA320 · Cessna A188 B
Woods Flying Service Cessna A188 B · Accident during initial climb
From Memphis, MO to Memphis, MO
Event
- NTSB case
- CEN20CA320
- 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 A188 B
- 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
- N90834
- Operator
- Woods Flying Service
- Onboard fatalities
- Unknown
- Route
- From Memphis, MOTo Memphis, MO
- Aircraft age
- About 41 years (built 1979)
- 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
- Initial climb
- 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
- Miscellaneous/other
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he had just started flying this airplane five days before the accident as a contract pilot. Over the past four days, the operator had the airplane on the "ready pad" with all of the tie-downs and gust locks already removed. On the day of the accident, the airplane was tied down with all of the gust locks still installed. Prior to takeoff, the pilot completed a preflight inspection but did not remove the rudder gust lock. During the takeoff roll, the pilot had to use the brakes to keep the airplane centered on the runway, which made for a much longer takeoff roll. The airplane dragged in the 10 ft high corn off the end of the runway and lost lift, so the pilot made a forced landing in a field. During the landing roll the airplane collided with a tree and sustained substantial damage to the fuselage, both wings, and empennage. The pilot reported that there were no mechanical malfunctions with the airplane. He stated that he should have completed a more thorough preflight inspection.
Probable cause
The pilot did not remove the rudder gust lock during the preflight inspection, which resulted in a forced landing and collision with a tree.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20CA320
- Event ID
- 20200803X22344
- Case number
- CEN20CA320
- 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: 10a1b02c42d3f2e430c8ee92ca0cf648ac7e5f9125ac2022d812db064536b935; retrieved 2026-09-16T12:20:35.066Z.