FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

United Airlines Flight 1734

1 Jun 2023 · Chicago, IL, United States

Boeing 737-924ER · Accident: turbulence encounter en route

From San Francisco International Airport (KSFO) to Chicago O'Hare International Airport (KORD)

Report a problem

Event

NTSB case
DCA23LA305
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
Event fatalities
Unknown
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-924ER

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
N28457
Onboard fatalities
Unknown
Route
From San Francisco International Airport (KSFO), San Francisco, CATo Chicago O'Hare International Airport (KORD), Chicago, IL
Aircraft age
About 11 years (built 2012)
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
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
Turbulence encounter
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

No findings designated as a cause are recorded in the NTSB data yet.

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 was seriously injured when United Airlines flight 1734 encountered convectively-induced turbulence during the descent into the Chicago O'Hare International Airport (ORD), Chicago, Illinois.

Flight 1734 originated from the San Francisco International Airport (SFO) and the captain was the pilot monitoring and the first officer was the pilot flying.

The flight crewmembers reported that they were not aware of any adverse reports of turbulence from either air traffic control (ATC), or other aircraft and they found the route along the arrival path to be generally smooth. Their weather radar was on and showed some cells located to the west of ORD, but none were along either their arrival route, the airport itself, or the area east of ORD where they conducted their approach to landing. When they first checked in with the Chicago approach controller, they were assigned runway 27R. However, they preferred a longer runway due to their landing weight and were therefore assigned runway 28C which they had to load into the flight management computer and re-brief.

The captain indicated that the seat belt sign had been turned on early in the descent during the “arrival” passenger announcement. About 13,000 ft, the captain gave the cabin crew the “double chime” indicating that they should prepare the cabin for landing and then take their seats.

The flight crewmembers reported that as the aircraft was descending through an isolated overcast layer, they observed a small cloud buildup with the top of the buildup slightly above their altitude. They contacted ATC and requested and were approved to make a left turn to avoid the cloud build-up. Although they attempted to avoid the cloud, the aircraft penetrated the left outermost area of the cloud buildup at an altitude of approximately 12,100 ft. The flight crewmembers indicated that as they went through this area, they experienced about 5 seconds of light to borderline moderate turbulence. As soon as they exited the area, the air was once again smooth.

Shortly after the encounter, the flight crewmembers received a call from the cabin crew informing them that one of the flight attendants had fallen in the rear galley and had injured her foot. According to the cabin crew, shortly after they heard the double chime, there was a big bump of turbulence, and a flight attendant lost her balance, twisted her ankle, and hit her back on the corner of her jump seat. A physician who was onboard the airplane assisted her and helped move her to a passenger seat for the remainder of the flight. Emergency medical personnel met the airplane at the gate and a post-flight medical evaluation revealed that the flight attendant had a fracture injury to her metatarsal bone in the left foot.

Based on a review of WSR-88Dweather radar (KMKX), satellite (GOES-16), and upper air model (HRRR) data, the turbulence encounter appeared generally coincident in time and location with a convective updraft that reached heights above 12,100 ft.

Probable cause

An encounter with convectively-induced turbulence (CIT).

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA23LA305
Event ID
20230602192293
Case number
DCA23LA305
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: 6259fa74ea73bbcd18cc8deb4dcfa82a40b707a305ab974adcddc6abf6125b95; retrieved 2026-09-16T17:40:55.024Z.