United Airlines Flight 2127
Boeing 787-9 · Incident: fire/smoke (non-impact) during landing
From an unrecorded airport to Newark Liberty International Airport (EWR)
Event
- NTSB case
- DCA26LA184
- 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
- Incident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Ongoing
- 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 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
- N24972
- Operator
- United Airlines
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Newark Liberty International Airport (EWR), Newark, NJ
- Aircraft age
- About 8 years (built 2018)
- 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
- Landing
- 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
- Fire/smoke (non-impact)
- 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
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.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record DCA26LA184
- Event ID
- 20260302202579
- Case number
- DCA26LA184
- 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: 1a044fc1feb135bbc76a90b7a475d255519861b856d5e60ad32e9eab669e3adf; retrieved 2026-09-16T20:53:15.122Z.