{"id":155623,"date":"2026-08-26T14:28:51","date_gmt":"2026-08-26T08:58:51","guid":{"rendered":"https:\/\/aviationa2z.com\/?p=155623"},"modified":"2026-08-26T14:28:55","modified_gmt":"2026-08-26T08:58:55","slug":"lufthansa-delhi-flight-makes-emergency-landing-in-baku","status":"publish","type":"post","link":"https:\/\/aviationa2z.com\/index.php\/2026\/08\/26\/lufthansa-delhi-flight-makes-emergency-landing-in-baku\/","title":{"rendered":"Lufthansa New A350 Operating Delhi Flight Makes Emergency Landing in Baku"},"content":{"rendered":"\n

FRANKFURT-<\/strong> Lufthansa (LH)<\/a> flight LH760 from Frankfurt (FRA) to Delhi (DEL) diverted to Baku (GYD) on August 25 after the Boeing 787 encountered a technical malfunction during the flight.<\/p>\n\n\n\n

The aircraft, a Boeing 787-9 registered D-ABPH, landed safely at Heydar Aliyev International Airport at 23:26 Baku time, according to the airport press service. ACARS messages from the aircraft also show Lufthansa operations teams coordinating the diversion and passenger handling in Frankfurt.<\/p>\n\n\n\n

\"Lufthansa
Photo: Lufthansa<\/figcaption><\/figure>\n\n\n\n

Lufthansa LH760 Diverts to Baku After Technical Issue<\/h2>\n\n\n\n

Lufthansa flight LH760 was operating from Frankfurt to Delhi when the crew requested a diversion to Heydar Aliyev International Airport in Baku because of a technical malfunction on board.<\/p>\n\n\n\n

The aircraft involved was D-ABPH, a Boeing 787-9<\/a> powered by Rolls-Royce Trent 1000-K3 engines. Lufthansa’s operational messages identified the aircraft and flight as LH760 during the diversion process.<\/p>\n\n\n\n

The press service of Heydar Aliyev International Airport said the aircraft landed safely at 23:26 Baku time. Airport services then carried out the necessary measures to ensure the safety of passengers and crew.<\/p>\n\n\n\n

The available ACARS traffic provides additional technical and operational context. Earlier messages recorded maintenance items involving the aircraft’s right IRU sensor and left AHRU sensor.<\/p>\n\n\n\n

A subsequent Lufthansa maintenance message specifically listed the right IRU sensor as a deferred maintenance item.<\/p>\n\n\n\n

\"\"
Photo: Lufthansa<\/figcaption><\/figure>\n\n\n\n

ACARS Messages Reveal Diversion Planning<\/h2>\n\n\n\n

The ACARS record shows that Lufthansa operations were actively managing the flight’s diversion. At 21:02 UTC, a flight planning message listed VAAH, the ICAO code for Ahmedabad, as an alternate airport and included a landing performance calculation for Runway 23.<\/p>\n\n\n\n

Earlier flight planning data also listed Baku as an alternate, with a planned route from UBBB to VIDP. The flight plan identified an estimated 3-hour-15-minute flight time from the departure point to Delhi<\/a> and a 1-hour-3-minute alternate flight time to Ahmedabad.<\/p>\n\n\n\n

The ACARS traffic later confirms that Lufthansa’s Frankfurt operations team was preparing for the diversion and coordinating the passenger recovery process. A message sent to LH760 stated that passenger handling for the diversion would be supported by Lufthansa’s Passenger Recovery Control in Frankfurt.<\/p>\n\n\n\n

\"Lufthansa
Photo: Lufthansa<\/figcaption><\/figure>\n\n\n\n

Lufthansa Reported No 787 Technician Available<\/h2>\n\n\n\n

One operational message sent at 21:05 UTC stated that no Boeing 787<\/a> technician was available and provided a contact number for the flight captain.<\/p>\n\n\n\n

This message is significant because it shows that Lufthansa was assessing the technical support requirements after the diversion. The ACARS record does not, however, establish whether the aircraft remained in Baku for an extended period or identify the exact corrective maintenance performed there.<\/p>\n\n\n\n

Lufthansa’s flight planning messages also show that the airline prepared revised operational information after the diversion, including landing performance calculations and a flight plan noting that the aircraft would continue after the diversion.<\/p>\n\n\n\n

Passenger Handling Prepared in Frankfurt<\/h3>\n\n\n\n

Lufthansa’s Passenger Recovery Control in Frankfurt instructed the crew to contact the station and provide its dedicated telephone number for diversion support.<\/p>\n\n\n\n

The message also stated that if passengers had to leave the aircraft during the diversion, Lufthansa would require their names. Importantly, the Frankfurt operations team instructed the crew not to actively offer passengers the option of leaving the aircraft.<\/p>\n\n\n\n

This indicates that Lufthansa had begun preparing contingency arrangements for passengers while the aircraft’s situation was being managed.<\/p>\n\n\n\n

Flight Had Been Cruising at 39,000 Feet<\/h4>\n\n\n\n

Before the diversion, ACARS position reports placed D-ABPH at approximately 39,000 feet over the region. One report recorded the aircraft at latitude 40.0187 and longitude 53.8256 at 39,004 feet.<\/p>\n\n\n\n

Another report shortly afterward placed the aircraft at 39,000 feet at latitude 39.8653 and longitude 54.5662.<\/p>\n\n\n\n

The ACARS record also shows a temporary loss of the aircraft’s HF link, with SATCOM remaining available as the default communication link.<\/p>\n\n\n\n

The available messages do not establish that the HF communication issue caused the diversion. It appears as a separate communications status message in the ACARS record.<\/p>\n\n\n\n

\"\"
Photo: Lufthansa<\/figcaption><\/figure>\n\n\n\n

Safe Landing Reported in Baku<\/h2>\n\n\n\n

Heydar Aliyev International Airport confirmed that the Boeing 787 landed safely at 23:26 Baku time. Airport services subsequently took the necessary measures to safeguard passengers and crew.<\/p>\n\n\n\n

The airport statement does not identify the specific technical malfunction that prompted the emergency landing request. The ACARS messages provide evidence of maintenance issues involving the right IRU sensor and left AHRU sensor, but they do not explicitly state that either component was the sole cause of the diversion.<\/p>\n\n\n\n

The available records therefore establish that LH760 diverted to Baku following a technical problem, while the precise root cause and subsequent maintenance outcome remain unclear from the released information.<\/p>\n\n\n\n

Stay tuned with us. Further, follow us on social media for the latest updates.<\/p>\n\n\n\n

Join us on\u00a0Telegram Group\u00a0<\/a>for the Latest Aviation Updates. Subsequently, follow us on\u00a0Google News<\/a><\/p>\n\n\n\n

\n
Lufthansa Boeing 747 Pilots Operating Chicago Flight Diverts to Glasgow<\/a><\/blockquote>