FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

United Airlines Flight 836

14 Dec 2007 · Chicago, IL, United States

Boeing 777-222 · Accident: airframe, component or system failure on approach

From Shanghai Pudong International Airport (PVG) to Chicago O'Hare International Airport (ORD)

Report a problem

Event

NTSB case
CHI08FA050
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
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 777-222

Aircraft type
Boeing 777
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
N220UA
Onboard fatalities
Unknown
Route
From Shanghai Pudong International Airport (PVG), ShanghaiTo 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
Approach
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
Minor

Cause areas

  • Air cond/heating/pressurization › Contamination
  • Air cond/heating/pressurization › Smoke
  • Engine assembly, bearing › Failure
  • Pilot in command › Evacuation, initiated

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

On approach for landing, about 13 miles from the airport, the flight crew was informed that the cabin was filling with smoke. The cabin crew was unable to determine the source of the smoke. The captain declared an emergency in order to get the airplane on the ground as soon as possible. The first officer performed a normal landing and turned off on the first high-speed taxiway, at which time he noticed a low oil indication on the right engine. The engine was subsequently shut down. The captain elected to initiate an emergency evacuation due to the uncertainty of the situation and the possibility of a fire on-board. During the evacuation, one passenger sustained a fracture of a vertebra. Post accident examinations revealed a low oil quantity in the right engine, with metallic deposits on one of the engine chip detectors. A detailed teardown inspection of the right engine revealed the #2 bearing had failed. The compressor gas path exhibited oil deposits consistent with oil migration into the airplane's environmental system. The cabin pressurization system utilized 8th and 15th stage engine compressor bleed air. No evidence of an engine or cabin fire was observed. The engine manufacturer had released an improved bearing design prior to the accident. At that time, the operator began replacing the bearings on an attrition basis when the original bearings were no longer serviceable. However, the operator has revised that policy and is proactively replacing the original bearings, regardless of the condition, with the improved bearings.

Probable cause

Emergency evacuation due to dense smoke in the cabin and the possibility of an on-board fire, which resulted in a serious injury to one of the 264 passengers and crew. An additional cause was the failure of an engine bearing, allowing oil to migrate into the environmental system, and resulted in the smoke in the cabin.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI08FA050
Event ID
20071231X02013
Case number
CHI08FA050
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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: 0079273c102b3ea80a8dceb2f1432a6485cc881ee56e4b9e0dda8b8d58c8551c; retrieved 2026-09-18T14:39:55.657Z.
  • The NTSB's operator name is blank for N220UA; the operator shown is the name the NTSB's other records give its FAA operator code, UALA.