United Airlines Flight 1
Boeing 787 9 · Accident: turbulence encounter en route
From San Francisco International Airport (SFO) to Singapore Changi Airport (WSSS)
Event
- NTSB case
- DCA25LA173
- 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
- 0
- 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
- Instrument Meteorological Cond
Boeing 787 9
- Aircraft type
- Boeing 787
- 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
- N27958
- Operator
- United Airlines
- Onboard fatalities
- Unknown
- Route
- From San Francisco International Airport (SFO), San Francisco, CATo Singapore Changi Airport (WSSS), Singapore
- Aircraft age
- About 10 years (built 2015)
- 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 · 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
United Airlines flight 1 encountered severe convective turbulence during cruise over the Republic of the Philippines, while enroute from San Francisco International Airport (KSFO), San Francisco, California, to Singapore Changi Airport (WSSS), Republic of Singapore. As a result of the turbulence, two flight attendants (FAs) sustained serious injuries, three FAs and one passenger sustained minor injuries. The airplane was not damaged, and the flight continued to its destination without further incident. The Civil Aviation Authority of the Philippines - Accident Investigation and Inquiry Board, delegated the investigation to the NTSB as the State of Operator and State of Registry.
A review of weather records revealed areas of scattered convection were present to the northeast of the accident location. The flight crew reported that prior to the accident the flight was smooth, and they had been deviating around small, scattered returns noted on the cockpit weather radar as they flew southwest toward the intended destination.
Figure 1. The most intense scattered convective activity noted north/northeast of accident site (data fusion satellite imagery provided by United Airlines).
The weather provider noted that there were no significant meteorological information (SIGMETs) or flight plan guidance advisories for turbulence or convective activity for the area, due to the scattered nature of the convection. Fusion satellite and lightning data showed isolated convective cells near the accident location and time, with lightning development and likely updrafts.
The flight crew reported that prior to the accident, the airplane was at flight level 400 in a thin cirrus cloud layer, there was no moonlight and the flight was smooth. The seatbelt sign was off. Immediately before the turbulence encounter, cockpit weather radar displayed no returns ahead of the airplane at any range. There were no messages or alerts about weather from dispatch, nor any indication of weather activity from their 3rd party data sources (Skypath and WSI). The flight crew described the turbulence as a sudden and severe jolt that lasted 3-5 seconds, during which it was difficult to read the instrument panel. Immediately after the turbulence subsided, the flight was smooth.
The FAs working in the aft galley (where the serious injuries occurred) described the turbulence as sudden and brief, the airplane dropped beneath them (or they were lifted off their feet) and they fell to the floor with severe force.
The other cabin crew solicited assistance from passengers with medical experience and rendered aid to those injured. They enlisted a non-revenue FA to replace one of the injured crew, to cover one of the doors during landing.
The captain coordinated with the cabin crew, dispatch and the remote medical advisory service, and the first officer. After considering a diversion to Manila, they chose to continue to WSSS, which was about 80 minutes away. The flight crew declared an emergency, landed uneventfully, and medical personnel met the airplane at the gate. One FA sustained a broken ankle requiring surgery and another was hospitalized for longer than 48 hours with a head injury.
Probable cause
An encounter with convective turbulence during cruise that was not detected in advance by cockpit weather radar or weather information services.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA25LA173
- Event ID
- 20250403199959
- Case number
- DCA25LA173
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas, damage. Values present in the bulk record are kept.
- The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
- API snapshot SHA-256: 17f8683455e9229d2f939aa7e8a67b2d0a1d2a77403104cfa93a8079dbdb1a00; retrieved 2026-09-16T19:47:31.563Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: departure. Narrative names the departure airport as San Francisco International Airport (KSFO), San Francisco, California.