
An eruption from Indonesia’s Mount Lewotobi Laki-Laki volcano on Thursday night sent a massive ash cloud more than 8km (5 miles) into the sky, disrupting air travel and raising emergency alerts to their highest level for locals and tourists in the region.
The eruption began at 10:56pm local time (14:56 GMT) on Thursday and was observed to produce a thick grey-to-black ash column.
The eruption, originating in the southeastern part of Flores Island, caused a flight disruption, particularly from Jetstar, Australia’s Qantas Airways’ low-cost subsidiary, which cancelled flights to Bali due to the volcanic ash.
While flights were expected to resume by Friday afternoon, seven international flights and several domestic routes at Bali’s airport had already been cancelled or delayed.
The Indonesian Center for Volcanology and Geological Disaster Mitigation issued a warning for residents and visitors in the southwest and northeast sectors of the eruption’s radius, advising against any activities within 7-8km (4.4-5 miles) of the volcano.
The agency also warned of potential volcanic mudflows in the region due to the heavy rainfall in the area.
Despite the widespread disruptions, there have been no immediate reports of damage to nearby villages. However, the eruption prompted the country’s geological agency to raise the volcano’s alert level to the highest, in a four-tiered system used for such emergencies.
The eruption of Lewotobi Laki-Laki follows a deadly event in November 2024 when the volcano killed at least 10 people and displaced thousands of residents.
After Thursday’s eruption, a tsunami warning was briefly issued by the Japan Meteorological Agency, though it was later lifted as the situation did not result in a tsunami.
The ongoing eruption and the disruption to flights highlight the volatile nature of Indonesia’s numerous active volcanoes, as authorities continue to monitor the situation closely.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ