FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN15IA079 · Cessna T182T

12 Dec 2014 · Cahokia, IL, United States

CCL Aircraft Cessna T182T · Incident: flight control system malfunction/failure during initial climb

From St Louis Downtown Airport (CPS) to St Louis Downtown Airport (CPS)

Report a problem

Event

NTSB case
CEN15IA079
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
Incident
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 T182T

Aircraft type
Cessna 182
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
N93CL
Operator
CCL Aircraft
Onboard fatalities
Unknown
Route
From St Louis Downtown Airport (CPS), Cahokia, ILTo St Louis Downtown Airport (CPS), Cahokia, IL
Aircraft age
About 7 years (built 2007)
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
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
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
None

Cause areas

  • Aircraft › Aircraft handling/service
  • Aircraft › Aircraft systems
  • Personnel issues › Action/decision
  • 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

The pilot was conducting a postmaintenance test flight. He reported that the airplane was about 900 ft above ground level in the crosswind turn after takeoff when it "began to pitch steeply toward the ground." The airplane lost about 200 to 300 ft of altitude. He pulled hard aft on the yoke to keep the nose level, and he confirmed that the autopilot was not engaged. He called for the pilot-certificated passenger to assist him in pulling aft on the yoke, which required "extreme back pressure." The pilot maneuvered the airplane to land on the longest and widest runway available. During the flight, the pilot incrementally added nose-up elevator trim in an effort to relieve the nose-down pressure; however, this had no effect. The manual elevator trim wheel indicated that the trim was in the full nose-up trim position. The pilot turned the airplane onto the base leg and was still unable to relieve the "extremely strong" nose-down tendency. He remembered that maintenance had been performed on the elevator trim system and thought that there might be some kind of control-reversal problem. While on the base leg of the approach, he decided to apply nose-down trim using the electric trim on the control yoke. The nose-down control forces lessened, and he immediately realized that there was a control reversal. The pilot proceeded to make a normal approach and landed without incident.

The examination of the airplane's elevator trim system revealed that moving the elevator trim wheel to the full nose-down position resulted in the elevator trim tab moving to the down position, which would place the airplane in a nose-up configuration and indicated that the elevator trim control was reversed. The airframe and powerplant mechanic who had performed the maintenance on the airplane, which included replacing the elevator trim actuator, inadvertently misrigged the elevator control cables. The airplane's maintenance manual instructed mechanics to "make sure that the trim tab moves in the correct direction when it is operated by the trim wheel" and contained a note stating that "nose down trim corresponds to the tab UP position." The mechanic did not ensure that the trim tabs moved in the correct direction during his postmaintenance inspection after he installed the elevator trim actuator.

Probable cause

The mechanic’s improper installation of the elevator trim actuator, which resulted in reversed elevator trim control, and his subsequent failure to detect the misrigging of the elevator cables during the postmaintenance inspection.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN15IA079
Event ID
20141217X25544
Case number
CEN15IA079
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, damage. 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: 49008cfdf306bf178d19f7658401562fb728e19874c8ef8023d34445a528abe2; retrieved 2026-09-16T01:59:04.992Z.