How Taal Volcano looks like a year after its eruption

On this day last year, Taal Volcano erupted. It caused millions-worth of property damage and affected thousands of people nearby. It’s crater, considered as one of the famous destinations in the South Luzon, turned gray, dried, and lifeless. But how does it look like a year after?

Left photo shows Taal Volcano’s main crater is dried after the eruption last January 12, 2020, while the right photo taken December of last year shows the crater is slowly coming back to life.

Through this video shot of Reynante Olitan De Villa last year of December 22 which he uploaded on his facebook page Madam Rutsa today, you can have have a peek at how the main crater of the volcano may look like at present. There is water again inside the crater, but its surroundings are still covered with cinders where trees and plants used to flourish.

Taal Volcano Main Crater

Taal Main Crater Main Crater

Posted by Madam RUTSA on Monday, January 11, 2021

According to Rey, he would love to shoot this morning but it’s windy and the waves on the lake are high. “But sometimes, when it’s not foggy, you can see the volcano emitting some steam,” he said.

Last January 10, he also posted another video of the crater in his YouTube channel, where you can also see updates about the volcano.

As of eight in the morning today, Philippine Institute of Volcanology and Seismology (PHIVOLCS) reported on its bulletin that Taal Volcano recorded four volcanic earthquakes in the past 24-hour period. Also, it has a weak emission of steam-laden plumes from fumarolic activity.

Taal Volcano is still at Alert Level 1 which means “sudden steam-driven or phreatic explosions, volcanic earthquakes, minor ashfall, and lethal accumulations or expulsions of volcanic gas can occur and threaten areas within the Taal Volcano Island.”

Credit belongs to : Manila Bulletin

Check Also

Weekend Travel: Must-visit restaurants in NCR+ with breathtaking views

It has been more than a year since the pandemic placed the entire planet on …

error: Content is protected !!