Typhoon Utor

From Infogalactic: the planetary knowledge core
(Redirected from Typhoon Utor (2013))
Jump to: navigation, search

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

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

Typhoon Utor (Labuyo)
Typhoon (JMA scale)
Category 4 (Saffir–Simpson scale)
Utor 2013-08-11 0515Z.jpg
Typhoon Utor shortly before peak intensity on August 11, 2013
Formed August 8, 2013 (2013-08-08)
Dissipated August 18, 2013 (2013-08-18)
Highest winds 10-minute sustained: 195 km/h (120 mph)
1-minute sustained: 240 km/h (150 mph)
Lowest pressure 925 hPa (mbar); 27.32 inHg
Fatalities 97 total[1]
Damage $2.6 billion (2013 USD)
Areas affected
Part of the 2013 Pacific typhoon season

Typhoon Utor, known in the Philippines as Typhoon Labuyo, was the 15th depression and the 2nd typhoon in the 2013 typhoon season.

It was a powerful tropical cyclone which struck the Philippines and southern China. Developing into a tropical storm on August 9, Utor soon underwent explosive intensification and became a typhoon within a half of day. After making landfall over Luzon late on August 11, the typhoon re-emerged in the South China Sea, and it ultimately made its second landfall over Guangdong, China on August 14.

Meteorological history

Map plotting the track and intensity of the storm according to the Saffir–Simpson hurricane wind scale

Early on August 8, the Joint Typhoon Warning Center (JTWC) reported that a tropical disturbance had developed north of Yap.[2] During that day, the system moved westwards and consolidated within a favourable environment of weak vertical wind shear and strong outflow, which was enhanced by a TUTT Cell located to the northwest of the disturbance.[3][4] As a result, the Japan Meteorological Agency (JMA), JTWC and PAGASA upgraded the system to a tropical depression 11W north of Palau, with the latter naming it Labuyo as it approached the Philippine Area of Responsibility.[5][6][7] During the next day, JTWC and JMA upgraded the system to a tropical storm, with the latter naming it as Utor (1311).[5][8] Shortly thereafter, Utor began undergoing explosive intensification, achieving typhoon status early on August 10, as an eye developed.[9]

On August 11, under the influence of low vertical wind shear, very favourable poleward and westward outflow, and warm sea surface temperature, Utor began to intensify more and formed a clear eye.[10] At 12:00 UTC, Typhoon Utor attained peak intensity by the ten-minute maximum sustained winds reaching 105 knots (195 km/h, 105 mph) and the atmospheric pressure decreasing to 925 hPa (27.3 inHg). The system became exceptionally symmetrical, as the convective bands had further deepened and wrapped tighter around a 13 nautical miles (24 km; 15 mi) pin-hole eye, prompting JTWC upgrading Utor to a super typhoon.[11] Due to land interaction with Luzon, the pin-hole eye filled in quickly; as a result, JTWC downgraded Utor to a typhoon at 18:00 UTC.[12] Tracking along the southern periphery of a subtropical ridge to the north, Utor made landfall over northern Luzon around 19:00 UTC (03:00 PHT on August 12).[13]

File:Utor Aug 14 2013 0545Z.jpg
Typhoon Utor approaching Guangdong, China on August 14

Owing to peaks of western Luzon, Utor significantly weakened as the deep convection became disorganised. Early on August 12, Utor arrived at the South China Sea, where the environment southwest of an anticyclone was favourable with diffluence aloft, light vertical wind shear and excellent radial outflow.[14] Although a ragged eye had formed later that day, the typhoon did not restrengthen further when tracking along the southern periphery of a subtropical ridge.[15] On August 13, the eye of Utor had become well-defined on the visible satellite imagery, but the intensity and structure remained when the system was tracking northwestward.[16] At 07:50 UTC (15:50 CST) on August 14, Utor made landfall over Yangxi County in Yangjiang, Guangdong, China as a minimal typhoon.[17] At 12:00 UTC, JMA downgraded Utor to a severe tropical storm, shortly before JTWC issued a final warning to the rapidly weakening system due to land interaction.[18] Later, Utor weakened into a tropical storm overland, and JMA downgraded the system into a tropical depression at noon on August 15. However, the remnants began tracking very slowly in Guangxi, until the tropical depression finally dissipated on August 18.[5]

Preparations and impact

Philippines

File:Typhoon Utor 2013 making landfall.gif
Animated enhanced infrared satellite loop of Typhoon Utor from peak intensity to landfall in the Philippines

Ahead of Utor affecting the Philippines, PAGASA issued various tropical cyclone signals for Luzon and Visayas, including signal 3 for the provinces of Aurora and Isabela and signal 1 for Metro Manila. [20] As Utor approached Central Luzon, a Malacanang Palace spokesperson called that local government to prepare and evacuate residents living near slopes, mountains and sea.[21] Thirty-two provinces in Luzon and Manila had been placed under signal warnings.[22] In Isabela, 67 families were evacuated before landfall. Under the anticipation of a direct hit, the local Pangasinan government placed the entire province on red alert. On August 11, the governor announced the suspension of classes from pre-school to tertiary level. Government and private offices were also suspended. Rescue equipment and rubber boats had also been placed in the disaster risk area of the province.[23] In the said regions, the government advised all to not engage on water sports or rough seas due to the anticipated rough seas.[24]

Utor made its landfall in Casiguran, Aurora at 3 AM (local time) on August 12. Power lines and telecommunications went down and many houses were destroyed.[25] In Nueva Vizcaya, heavy rainfall had been recorded. Some residents in the said province were forced to evacuate due to flooding. Moreover, the Magat River in the province reached the critical level, resulting in the partial opening of four gates in a dam. Electricity was also out in the province. One man died on Baguio City after he had been buried alive after a mudslide hit his home. In Isabela, more than 100 families had been affected by Utor. About 200 million pesos in agriculture was blamed on Utor in Isabela alone. Around 1,000 residents in the central Bicol region spent the night in shelters, and 23 fishermen who were out at sea failed to return home in four towns in Catanduanes province.[26] Some cars in North Luzon Expressway used hazard signals as roads were nearly impossible to see. Intense rainfall throughout the day had been recorded in Zambales, which created flash flooding in low-lying areas. The major river on the province then overflowed, flooding homes. The flood is expected to get higher as high tide is expected in the morning.[27] At least 700 passengers were stranded in the ports of Albay, Catanduanes, Sorsogon and Samar. Additionally, 10 flights had also been canceled as Utor brought intense rainfall in many parts of Luzon.[28]

Throughout the Philippines, at least ten people were killed while four others were listed as missing. A total of 398,813 people were affected by the typhoon, roughly a third of whom were displaced from their homes. Significant infrastructural damage took place with 2,565 homes destroyed and 18,090 more damaged. Losses from Utor amounted to 1.08 billion (US$24.8 million), the majority resulting from agricultural damage.[29]

China

File:Hong Kong Typhoon Utor.JPG
Typhoon Utor over Hong Kong on 14 August

The Chinese bulk carrier Trans Summer sank some 45 nautical miles (83 km; 52 mi) southwest of Hong Kong after having been caught in the typhoon. Twenty-one members of the crew were saved.[30]

Widespread damage took place in Guangdong Province where at least four people were killed and four others were listed missing. An estimated 109 million people were affected, 16.15 million of whom were temporarily relocated due to the threat of flooding. Typhoon-force winds caused a belt factory in Dongguan to collapse, killing 1 person and injuring 17 others.[31] Losses across the province amounted to ¥13.4 billion (US$2.2 billion).[32] Six people were killed in Guangxi Province while nearly 100 million were affected. Losses in the province reached ¥382 million (US$62.4 million).[33] Prolonged heavy rains in Hunan Province triggered widespread flooding that caused substantial damage. At least five people were killed and five others were listed missing while 96.46 million people were affected by the storm.[34]

Following the storm, prices of vegetables were raised by an average of one percent in Guangzhou, while the price of leafy vegetables were raised by as much as 15 percent.[31]

Retirement

During their 2014 annual session, the ESCAP/WMO Typhoon Committee announced that the name Utor would be retired from the naming lists. The name Barijat was chosen to replace Utor. PAGASA announced that the name Labuyo, would be retired from its naming lists after it had caused over PHP1 billion in damages.[35][36] PAGASA chose the name Lannie to replace Labuyo for the 2017 season.

See also

Notes

  1. Total damages figure includes agriculture, infrastructure, casualties, etc. damages.

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. 5.0 5.1 5.2 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. 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. 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. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. 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.
  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.
  30. Bulk carrier Trans Summer sank off Hong Kong in Typhoon Utor. Maritime Bulletin, 14 August 2013. Retrieved 2013-08-14.
  31. 31.0 31.1 Lua error in package.lua at line 80: module 'strict' not found.
  32. (Chinese) http://news.xinhuanet.com/fortune/2013-08/23/c_125231750.htm
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.

External links