United Airlines Boeing 757-200 accident
Boeing 757-200 · Accident: in flight encounter with weather en route
From John F. Kennedy International Airport (KJFK) to Los Angeles International Airport (KLAX)
Event
- NTSB case
- LAX07LA127
- 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
- N525UA
- Operator
- United Airlines
- Onboard fatalities
- Unknown
- Route
- From John F. Kennedy International Airport (KJFK), New York, NYTo Los Angeles International Airport (KLAX), Los Angeles, CA
- 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
- In flight encounter with weather
- 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
- Weather condition › Turbulence
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While at flight level FL400 (40,000 feet) the flight deck received information about turbulence below 12,000 feet. The captain advised the flight attendants to have the cabin secured and be in their seats within 15 minutes. The first officer gave the 'prepare for landing' announcement in the descent around flight level FL250 (25,000 feet), which was after the captain had notified the flight attendants to prepare the cabin, but before the end of the stated 15 minutes. While descending through 15,500 feet, the airplane experienced a moderate 'jolt' lasting 1-2 seconds. By this time it had been more than 15 minutes since the captain gave the flight attendants the secure cabin instructions. The cabin crew reported injuries to all flight attendants and no injuries to passengers. All six flight attendants received medical attention after landing. One flight attendant was seriously injured with a closed fibular fracture; the five other flight attendants had minor injuries. The first officer said that turbulence during their departure had been very bad, therefore, in order to mitigate any passenger anxiety, when he made the 'prepare for landing' announcement, he added that the turbulence would not be as bad as it was on departure. He understood the captain's instructions to the flight attendants, and this announcement was aimed solely at the passengers. The flight attendants confirmed that they understood the captain's instructions to have the cabin cleaned up and be seated within 15 minutes. As they were finishing the cabin clean up, the first officer's 'prepare for landing' announcement indicated that the turbulence would not be as bad as they had been told to expect. The flight attendants may have interpreted this added information concerning turbulence as a relaxation of the captain's earlier instructions. The Digital Flight Data Recorder (DFDR) indicated the turbulence occurred as the aircraft was coming out of a 12-degree right bank and descending through 15,400 pressure altitude. The event lasted approximately 10-11 seconds. The bank angle of the aircraft was between 8 and 1 degrees right wing down during the event. Vertical acceleration fluctuated between .5 and 2.06 G's. Longitudinal acceleration spiked up to .2 G's about the same time as the 2 G vertical spike. Lateral acceleration fluctuated between .1 G left and .05 G's to the right during the incident. The data showed that the autopilot was engaged and in control of the aircraft during the incident.
Probable cause
The flight's encounter with a turbulence event that occurred while the flight attendants were unseated. Contributing to the accident was the apparent conflicting information provided by the flight deck to the flight attendants and the flight attendants' interpretation of that information.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX07LA127
- Event ID
- 20070418X00436
- Case number
- LAX07LA127
- 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, 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: 59a9c81e36e5ab41671e39e8e04d1214f9f7d5f38080e135c6c2fb9367e9185c; retrieved 2026-09-18T14:45:34.507Z.