United Airlines Flight 1754
Airbus A320 232 · Accident: turbulence encounter en route
From Louis Armstrong New Orleans International Airport (MSY) to Newark Liberty International Airport (EWR)
Event
- NTSB case
- DCA20CA058
- 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
- Unknown
Airbus A320 232
- Aircraft type
- Airbus A320
- 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
- N1902U
- Operator
- United Airlines
- Onboard fatalities
- Unknown
- Route
- From Louis Armstrong New Orleans International Airport (MSY), New Orleans, LATo Newark Liberty International Airport (EWR), Newark, NJ
- Aircraft age
- About 14 years (built 2006)
- 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 · climb to cruise
- 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
- Environmental issues › Conditions/weather/phenomena
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On January 10, 2020, at about 2245 universal coordinated time, United Airlines flight 1754, an Airbus A320, N1902U, encountered turbulence near the top of climb from New Orleans International Airport (KMSY), New Orleans, Louisiana. Of the 159 passengers and crew onboard, one flight attendant sustained serious injuries. The airplane was not damaged. The flight was operating under the provisions of 14 Code of Federal Regulations Part 121 as a regularly scheduled passenger flight from the KMSY to Newark Liberty International Airport (KEWR), Newark, New Jersey. According to the flight crew, they advised the flight attendants (FA) to expect some light turbulence during the climb out, and stated they would leave the seatbelt sign illuminated for passengers until they had reached smooth air. During the climb to their assigned altitude of flight level (FL) 370, the weather radar was active and air traffic control advised of weather directly in front of the flight. As the flight was climbing through about FL 305 , the flight was in clear air but the crew realized they were not going to stay above the clouds ahead of the airplane and requested, and were approved, to deviate to the right to avoid the buildups. During the turn, the captain made an announcement on the public address (PA) system for the FAs to “take their jumpseats” and subsequently encountered “a couple bumps of light chop.” Almost immediately after, they received a call from the cabin, that the purser had been injured. According to the FAs, they were preparing for cabin service when the turbulence was encountered. The forward FA fell to the floor as she was walking through the first-class cabin. Subsequently, the flight crew’s announcement for the “flight attendants take your jump seats” came over the PA system. The injured FA was assisted by medically qualified passengers and remained in a passenger seat for the remainder of the flight. Paramedics met the airplane at the gate and the FA was transported to the hospital where she was diagnosed with a fractured ankle. Post accident examination of the weather data determined that the turbulence was encountered when the airplane was flying over an area of general thunderstorms. Cloud tops up to FL400 were located within 10 miles of the turbulence encounter but there were no pilot reports (PIREPs) in the vicinity indicating turbulence prior to the event. There was a Center Weather Advisory current for the area for isolated thunderstorms, which was included in the flights weather briefing.
Probable cause
an encounter with convectively induced turbulence while overflying an area of known convective activity.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA20CA058
- Event ID
- 20200125X54545
- Case number
- DCA20CA058
- 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, cause areas, 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: 51b22d189c00beae4216ff3cfe4fb265922c1f4bf1659d86f57deeaf116d7f77; retrieved 2026-09-16T10:59:26.146Z.