FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

United Airlines Flight 1212

1 Mar 2004 · Janesville, WI, United States

Boeing 757-200 · Accident: uncontrolled altitude deviation en route

From Portland International Airport (PDX) to Chicago O'Hare International Airport (ORD)

Report a problem

Event

NTSB case
CHI04LA084
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 757-200

Aircraft type
Boeing 757
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
N516UA
Onboard fatalities
Unknown
Route
From Portland International Airport (PDX), Portland, ORTo 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
Uncontrolled altitude deviation
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

  • Unsafe/hazardous condition › Not identified
  • Weather condition › Turbulence, convection induced

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

NTSB narrative

A flight attendant suffered a broken ankle and tibia when the airplane encountered turbulence during descent. The captain reported the seat belt sign was turned on as they descended through 18,000 feet. He reported they encountered about 15 seconds of moderate turbulence as they passed through 16,000 feet. He reported there were no weather returns in the area and they were back in smooth air after the encounter. The first officer reported that he informed the flight attendants to take their seats as soon as they began to encounter the turbulence. He reported he was getting ready to call the flight attendants after the turbulence to make sure they were alright, when the cockpit received a call from the back stating that one of the flight attendants injured her ankle. The first officer reported that they requested paramedics meet the flight upon landing. The injured flight attendant reported she was in the aft galley when they encountered the turbulence. She stated she tried to get in the jumpseat, but was unable to because of the turbulence. The injured flight attendant stated she heard another flight attendant tell a passenger who was in the aft galley to sit on the floor, so she decided to do the same. She stated that as she was sitting down, the "plane dropped" and she fell. Once the turbulence subsided, the other flight attendant and a passenger helped her off the floor and into a seat. None of the flight attendants recalled having any advance warning of the turbulence. Rapidly building convective activity was evident along the upper Mississippi Valley at the time of the accident. Convective tops averaging FL250 in the area were moving north-northeast at 60 knots. Severe Weather Advisory 15S, valid from 1731 universal coordinated time (UTC) to 2301 UTC, covered the route of flight from the Mississippi River to ORD. The severe thunderstorm watch included a forecast for hail, surface wind gusts to 60 knots, maximum cloud tops to FL450, and a storm motion vector to 240 degrees at 35 knots. Convective Sigmet 25C was valid until 2255UTC. The Sigmet called for an area of embedded thunderstorms moving from 190 degrees at 20 knots. The thunderstorms had tops to FL300. Data from the digital flight data recorder shows the airplane experienced vertical acceleration fluctuations from a minimum of 0.437 g's, to a maximum of 1.994 g's, and back to 0.576 g's in less then 3 seconds.

Probable cause

The unexpected encounter with convective turbulence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI04LA084
Event ID
20040305X00271
Case number
CHI04LA084
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, 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: 3a43e39ee5df165bd6cd23bcd725ffe5fdb2f6f2a1a75b1b5059abd803ae97d3; retrieved 2026-09-18T15:29:34.761Z.
  • The NTSB's operator name is blank for N516UA; the operator shown is the name the NTSB records it doing business as.