This is a good article. Click here for more information.

Tropical Storm Mekkhala (2015)

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Severe Tropical Storm Mekkhala (Amang)
Severe tropical storm (JMA scale)
Category 1 (Saffir–Simpson scale)
File:Mekkhala 2015-01-17 0414Z.jpg
Severe Tropical Storm Mekkhala making landfall over the Philippines on January 17
Formed January 13, 2015
Dissipated January 21, 2015
Highest winds 10-minute sustained: 110 km/h (70 mph)
1-minute sustained: 130 km/h (80 mph)
Lowest pressure 975 hPa (mbar); 28.79 inHg
Fatalities 3 total
Damage $7.8 million (2015 USD)
Areas affected Caroline Islands, Philippines
Part of the 2015 Pacific typhoon season

Severe Tropical Storm Mekkhala,[nb 1] known in the Philippines as Tropical Storm Amang, was an early-season tropical cyclone that made landfall over the Philippines in January 2015. Mekkhala killed three people in the Bicol Region and caused light crop damage. Notably, the storm disturbed Pope Francis’ visit to the country After The Victims of Typhoon Haiyan on November 8,2013. Although the storm also caused an airplane crash in Tacloban, nobody was hurt in the incident.

The system developed on January 13 between the Philippines and Guam. Moving west-northwest for its duration, Mekkhala passed north of Yap State on January 14 while slowly intensifying due to moderate wind shear. Conditions became more favorable on January 16, when the storm quickly strengthened to peak winds of at least 110 km/h (70 mph); a ragged eye prompted the American-based Joint Typhoon Warning Center (JTWC) to upgrade it to a typhoon. The storm weakened slightly and made landfall on the Philippine island of Samar on January 17. Mekkhala weakened further over land, dissipating on January 21 east of Luzon.

Meteorological history

File:Mekkhala 2015 track.png
Map plotting the track and intensity of the storm according to the Saffir–Simpson hurricane wind scale

A tropical disturbance formed approximately 390 km (240 miles) south-southwest of Pohnpei early on January 9.[2] The system remained disorganized until the Joint Typhoon Warning Center (JTWC) issued a Tropical Cyclone Formation Alert to it late on January 12, when deepened convection with formative started to wrap into a slowly-consolidating low-level circulation center (LLCC).[3][nb 2] Afterwards, the Japan Meteorological Agency (JMA) upgraded the low-pressure area to a tropical depression early on January 13,[nb 3] as did the JTWC with the designation 01W[6] Although deep convection was displaced to the northwest of an exposed LLCC early on January 14, the JMA still upgraded the system to a tropical storm and named it Mekkhala, under moderate vertical wind shear offset by excellent poleward outflow.[7][8] In post-season analysis, the agency upgraded the storm at 12:00 UTC on the previous day.[9] Late on January 14, the PAGASA named the storm Amang right after it entered the Philippine Area of Responsibility.[10]

File:Mekkhala 2015 landfall.gif
Severe Tropical Storm Mekkhala making landfall over the Samar

Tracking west-northwestward and then westward along the southern periphery of a subtropical ridge, Mekkhala was upgraded to a tropical storm by the JTWC early on January 15, due to its slightly improved structure.[11] Mekkhala quickly intensified on the next day due to improved conditions; the wind shear became in-phase with the storm's motion while the robust divergent outflow persisted.[12] Therefore, the JMA upgraded the system to a severe tropical storm at 06:00 UTC on January 16,[9] and later that day the JTWC upgraded it to a typhoon, when a central dense overcast has significantly deepened and totally obscured the LLCC.[12] Later, a microwave imagery revealed that Mekkhala formed a ragged eyewall structure.[13] The system reached peak intensity at 00:00 UTC on January 17 with ten-minute maximum sustained winds of 110 km/h (70 mph),[9] although operationally the JMA estimated typhoon-force winds of 130 km/h (80 mph).[14]

After slightly weakening, Mekkhala tracked northwestward and made landfall over Dolores, Eastern Samar of the Philippines at around 15:00 Philippine Standard Time (07:00 UTC), where Typhoon Hagupit also made landfall the month before.[15] Both the JMA and the JTWC downgraded Mekkhala to a tropical storm on January 17, due to land interaction weakening the storm significantly.[16][17][18] Mekkhala eroded further while crossing the Bicol Region on January 18, leading the JTWC to downgrade it to a tropical depression when it turned northward and emerged into the Philippine Sea.[19] Late on the same day, the JMA downgraded Mekkhala to a tropical depression, and shortly after the JTWC issued the final warning as strong wind shear exposed the LLCC.[20] The tropical depression drifted northeastward and maintained its exposed low-level circulation east of Luzon, until the system was completely absorbed by a stationary front early on January 21.[21][22]

Impact

File:Pope Francis Tacloban 18.jpg
The site of the Papal Mass in Tacloban on January 17

During January 14, Mekkhala passed about 95 km (60 mi) to the north of Yap State and less than 45 km (30 mi) to the south of the atoll Ulithi.[23] A peak wind gust of 58 km/h (36 mph) was recorded in Yap State, along with a rainfall total of around 13 mm (0.5 in).[23] On Ulithi a rainfall total of 100 mm (4 in) was recorded, while there were no reports of any deaths or significant damage on either Ulithi or in Yap State.[23]

Severe Tropical Storm Mekkhala, also known as Tropical Storm Amang, killed three people in the Bicol Region of the Philippines. Damage in the region amounted to 318.7 million (US$7.1 million), stemming mostly from agriculture.[24] In addition, the storm caused agricultural damage of ₱30.3 million (US$680,000) in Samar.[25] The crop damage and a subsequent drought caused rice shortages in the country, prompting the government to import the grain in May 2015.[26] Throughout the country, 48 homes were destroyed while a further 490 sustained damage.[25] Infrastructural losses reached ₱49.7 million (US$1.1 million); repairs to roadways was quick and completed by January 21.[24] A volunteer from the Bicol Region, who worked for a Catholic Relief Services station in Salcedo, Eastern Samar, was hit by a soundbox due to a collapsed scaffolding caused by heavy winds during a papal Mass held in Daniel Z. Romualdez Airport in Tacloban, Leyte.[27]

To comfort Tacloban people who suffered from the devastating disaster caused by Typhoon Haiyan in 2013, and Typhoon Hagupit a month prior, Pope Francis visited the storm-ravaged city on January 17. However, the schedule is significantly impacted by Severe Tropical Storm Mekkhala, making thousands of pilgrims and even Pope himself have to wear a raincoat during the rain-soaked Mass in the airport.[28] Only several minutes after Pope Francis’ own aircraft left the airport, a private jet was veered off the runway by strong winds of Mekkhala and eventually crashed. The 15 passengers on the plane were all safe, including many officials from the Cabinet of the Philippines.[29]

See also

Notes

  1. The name Mekkhala was submitted to the World Meteorological Organization by Thailand and comes from the Thai angel of thunder Manimekhala (Thai: มณีเมขลา).[1]
  2. The Joint Typhoon Warning Center is a joint United States NavyUnited States Air Force task force that issues tropical cyclone warnings for the western Pacific Ocean and other regions.[4]
  3. The Japan Meteorological Agency is the official Regional Specialized Meteorological Center for the western Pacific Ocean.[5]

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 9.2 Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. 12.0 12.1 Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. 23.0 23.1 23.2 Lua error in package.lua at line 80: module 'strict' not found.
  24. 24.0 24.1 Lua error in package.lua at line 80: module 'strict' not found.
  25. 25.0 25.1 Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found. – via Lexis Nexis (subscription required)
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.

External links