FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI99IA144 · Cessna 206H

26 Apr 1999 · Wheeling, IL, United States

Cessna 206H · Incident: airframe, component or system failure while standing

From an unrecorded airport to Naper Aero Club Airport (LL10)

Report a problem

Event

NTSB case
CHI99IA144
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
0
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 206H

Aircraft type
Cessna 206
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
N42122
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo Naper Aero Club Airport (LL10), Naperville, IL
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
Standing · engine(s) operating
First occurrenceThe 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
Airframe, component or system 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

  • Flt control syst, aileron control › Binding(mechanical)
  • Manufacturer › Maintenance, installation, improper

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

During the run-up flight control checks prior to takeoff, the pilot experienced an aileron control failure. He was unable to obtain left aileron up movement. Inspection determined that the aileron had 4 degrees of up travel. Normal travel was 20 degrees +/- 2 degrees. Further inspection revealed that one of the aileron control bellcrank stop bolt/jam nut assemblies was loose allowing the stop bolt to rotate out of the threaded boss. This restricted the aileron movement. The three other stop bolt/jam nut assemblies were also inspected and were found to be loose. The airplane was a 1999 model, s/n 25, which had a total of approximately 11 hours on it at the time of the incident. In response to this incident Cessna Aircraft Company issued Special Service Project SSP99-27-02. On June 21, 1999, the Federal Aviation Administration issued Airworthiness Directive, 99-13-04, effective July 13, 1999. The AD requires '...inspecting the left and right wing aileron control bellcrank stop bolts and lock nuts for flush and tight contact with the surface of the threaded boss on each end of the yoke assemblies, and accomplishing follow-on and corrective actions, as applicable.'

Probable cause

improper installation of the aileron control bellcrank stop bolts and lock nuts during the manufacturing process which resulted in a binding aileron control surface.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI99IA144
Event ID
20001205X00431
Case number
CHI99IA144
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, 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: da527a12556b56868875a4666cd23a8d06d9cac19f3ed5e3e59788017a1ac610; retrieved 2026-09-22T15:24:48.867Z.