FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

United Airlines Boeing 737-322 incident

13 Dec 2001 · Chicago, IL, United States

Boeing 737-322 · Incident: loss of control in flight en route

From St. Louis Lambert International Airport (STL) to Chicago O'Hare International Airport (ORD)

Report a problem

Event

NTSB case
CHI02IA050
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
Airline
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

Boeing 737-322

Aircraft type
Boeing 737
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
N359UA
Onboard fatalities
Unknown
Route
From St. Louis Lambert International Airport (STL), St. Louis, MOTo Chicago O'Hare International Airport (ORD), Chicago, 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 121: Air Carrier
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
En route · descent
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
Loss of control in flight
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

  • Reason for occurrence undetermined

Approximate · Estimated position: the centre of Chicago, IL, the place the record names. Not the accident site.

NTSB narrative

The scheduled domestic passenger carrying flight of a Boeing 737-322 achieved a maximum altitude of about 27,000 feet with an outside air temperature of about -36 degrees Celsius. About 30 minutes after departure and while on a visual descent to the destination airport, the flight encountered wake turbulence while descending through 9,300 feet mean sea level for visual approach to the destination airport. The airplane began a correction back to the right while continuing to bounce. The airplane rapidly banked 10 degrees when the captain said that he was disengaging the autopilot and autothrottles. The captain applied left aileron and left rudder to oppose the roll and eventually the first officer began to assist the captain in his control inputs.

The digital flight data recorder showed that the airplane achieved a right 26-degree roll; a left 45-degree control wheel deflection followed by right control wheel deflections. The rudder pedal deflection achieved a maximum value of left 6.5 degrees which was followed by a right 1.5 degree deflection with corresponding aileron deflections ranging from left 6.0 degrees to right 1.0 degrees. The pedal then remained deflected to the left over a range from 2.0-0.25 degrees with corresponding left rudder deflections ranging from 2.0-0.25 degrees until the airplane landed. The first officer reported that A and B hydraulic quantity and pressure gauge indications were normal and there was no change in hydraulic pressure and quantity indication upon completion of each uncommanded rudder checklist item. The captain stated that during landing roll, about 100 knots indicated airspeed, they heard a banging noise and got a full right deflection of the rudder pedals. The cockpit voice recorder recording of the flight was not retained by the operator following the incident.

Inspection of the cockpit nose area forward of the main landing gear revealed a wood-handled wire brush. The first officer's pedal arms contained scuff marks on the paint surface and gouge marks which penetrated the paint surface and metal. Further inspection with the aid of a borescope revealed the presence of displaced white paint on the structure aft of the pedal arms. No dents were noted in the vertical structure surrounding the pedal arm. The UAL party representative stated that work relating to an airworthiness directive was performed weeks prior to the incident. The brush along with a new brush and the first officer's pedal arms were sent to the National Transportation Safety Board's Materials Laboratory for further examination. Examination of the first officer's rudder pedal arms and brush revealed that in the vicinity of the bolt heads revealed only light score marks scattered around the edge of the boss, consistent with tool usage. The right pedal arm contained one score mark on the rear edge of the boss. The score mark was circumferential for approximately 90 degrees of arc, centered at the horizontal line. It was more significant above the horizontal and tapered to nothing below it. Examination of the left, right , top, and bottom faces of the brush handle revealed no indications of any crush damage. Functional testing and macroscopic visual examination of the rudder power control unit revealed no anomalies. One estimate of the maximum rudder forces that can be exerted for various positions of rudder pedal range from 246 - 424 lbs depending upon rudder pedal position and distance from back of seat. Several like brushes were loaded in the lengthwise direction and also placed in various obstructive positions within the pedal arms. Brushes placed in obstructive positions with a pilot applying rudder pressure estimated that force he applied to the rudder pedals to fracture the brushes was 15-20 pounds. Brushes loaded in the lengthwise directions broke at loadings from a maximum of 80 pounds and below. A flight training simulator was back driven at UAL's Flight Training Facility using FDR data from the incident flight with both flight crew members aboard. The simulator structure at the rudder pedals had the same platform/shelf structure as the incident airplane. The rudder pedals set to the same adjustment as reported by the first officer, and the brush was inserted with the application of left rudder pedal pressure to hold the brush in place due to the resting platform being shorter than the actual airplane. The brush position for the best strength and holding power was noted when the brush was orientated such that the wire bristles were facing downward and towards the rudder control arms and the convex portion of the brush handle facing upwards with the other end against the vertical wall of the pedal box. Further pressure on the rudder pedals was not added due to a concern of causing damage to the simulator.

A search of the Federal Aviation Administration’s service difficulty reporting system relating to "Boeing Rudder Controls" was performed for a time period from January 1, 1997 to February 1, 2002. One occurrence shows that maintenance could not find any fault with the airplane and that the rudder hydraulic system components were replaced. A second occurrence shows that after the accomplishment of engineering callouts relating to rudder hydraulic system components, no defects were noted. A third occurrence noted the replacement of the PCU.

Probable cause

Reason for occurrence is undetermined.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI02IA050
Event ID
20020115X00074
Case number
CHI02IA050
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: d244be08f1123ce3990db047f005c01eea4c6e321e861b74516920d1456bcb2d; retrieved 2026-09-18T16:07:30.603Z.