Boeing 787-9 incident near Los Angeles, California, March 2, 2026
On March 2, 2026 at about 7:00 pm local time, a 2018 Boeing 787-9, registered N24972, was involved in an incident during landing near Los Angeles, California (Los Angeles Intl airport). It was flown under scheduled airline rules (Part 121). No one was hurt; 250 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this incident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 2, 2026 · about 7:00 pm local time
- Place
- Los Angeles, California · Los Angeles Intl · map
- Type
- Incident
- Injuries
- No one was hurt; 250 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Boeing 787-9, built 2018 · all 787-9s on the register
- Registration
- N24972 · registry record · serial 40939
- Damage
- Not recorded
- Flight
- Flight · scheduled airline rules (Part 121)
The NTSB's narrative preliminary · quoted from the NTSB record
On March 2, 2026, at 1100 Pacific Standard Time, United Airlines flight 2127, a Boeing 787-9, registration N24972, powered by two General Electric GEnx™-1B76A/P2 turbofan engines, experienced a No. 1 (left) engine surge during climb from Los Angeles International Airport (LAX), Los Angeles, California. There were no injuries to the 2 flight crew, 9 cabin crew, or 239 passengers on board. United Airlines operated the airplane as a Title 14 Code of Federal Regulations Part 121 domestic passenger flight destined for Newark Liberty International Airport (EWR), Newark, New Jersey. According to the flight crew statements, the flight began with an uneventful pre-flight, taxi, and takeoff from runway 25R. The First Officer was the pilot flying and the Captain was the pilot monitoring. While climbing through 17,000 feet, they experienced strong vibrations in the controls and observed decreasing left engine N2 speed. A compressor stall and a L ENGINE FIRE message was displayed on the engine indicating and crew alerting system (EICAS) shortly after. The First Officer transferred controls to the Captain and began executing the engine fire checklist. One fire bottle was discharged and the engine fire warning extinguished after about 30 seconds. The warning returned on the EICAS, and the second fire bottle was discharged. The crew declared an emergency, advised ATC of a suspected engine fire, requested clearance for immediate return to LAX, and asked for airport crash and fire rescue (CFR) assistance. The crew continued receiving intermittent fire warnings during their return to LAX. A single engine, ILS approach and landing on Runway 25L was accomplished without incident. After landing, the L ENGINE FIRE EICAS warning returned and the crew decided to stop taxi and evacuate while still on the taxiway. While the crew was performing the evacuation checklist and informing passengers, a flight attendant told them she saw fire coming from the left engine. Aircraft rescue and fire fighting (ARFF) personnel brought airstairs to right-side door R1 and slides were deployed for the remaining right-side doors R2 and R3. The Captain stayed onboard to assist firefighters sweeping the aircraft while the First Officer went outside to assist passenger evacuation. Figure 1: Airport ARFF response after landing Post-incident examination of the airplane found sooting and thermal damage concentrated around the engine core module’s external surfaces and extending up toward the pylon connection. Both left and right thrust reverser halves showed minimal thermal damage. Borescope inspection found damage in the high-pressure turbine. Figure 2: Right side of No. 1 engine with inboard thrust reverser half opened The NTSB invited qualified parties to participate in the investigation, including the Federal Aviation Administration, the Boeing Company, United Airlines, and General Electric Aerospace. NTSB specialists supporting this investigation include Flight Data Recorders, Materials, and Powerplants. The investigation is ongoing.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Fire/smoke (non-impact) during landing defining event
- Powerplant sys/comp malf/fail during enroute (climb to cruise)
The aircraft
- Maximum gross weight: 477,300 lb
- Seats: 270
- Landing gear: retractable
- Operator: United Airlines INC
The flight
- Destination: EWR Newark NJ
- Flight plan: IFR
- Runway 07R/, 11,095 ft by 200 ft
Weather at the time
- Light: daylight
- Wind: at 4 knots
- Visibility: 6 statute miles
- Sky: broken clouds at 22,000 ft; a few clouds
- Temperature: 61°F (16°C), dew point 57°F (14°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Cabi | 9 | |||
| Flight crew | 2 | |||
| Passengers | 239 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
