Typhoon Soulik (2013)

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Typhoon Soulik (Huaning)
Typhoon (JMA scale)
Category 4 (Saffir–Simpson scale)
Soulik Jul 10 2013 0437Z.png
Typhoon Soulik at peak intensity on July 10
Formed July 7, 2013
Dissipated July 14, 2013
Highest winds 10-minute sustained: 185 km/h (115 mph)
1-minute sustained: 230 km/h (145 mph)
Lowest pressure 925 hPa (mbar); 27.32 inHg
Fatalities 11 total
Damage $557 million (2013 USD)
Areas affected
Part of the 2013 Pacific typhoon season

Typhoon Soulik, known in the Philippines as Typhoon Huaning, was a powerful tropical cyclone that caused widespread damage in Taiwan and East China in July 2013. The storm originated from an upper-level cold-core low well to the northeast of Guam on July 6. Gaining tropical characteristics, the system soon developed a surface low and became a tropical depression early on July 7. Tracking generally westward, a motion it would retain for its entire existence, the depression underwent a period of rapid intensification starting on July 8 that culminated in Soulik attaining its peak strength early on July 10. At that time, the system had sustained winds estimated at 185 km/h (115 mph) and barometric pressure of 925 mbar (hPa; 27.32 inHg). Thereafter, an eyewall replacement cycle and cooler waters weakened the system. Though it passed over the warm waters of the Kuroshio Current the following day, dry air soon impinged upon the typhoon. Soulik later made landfall late on July 12 in northern Taiwan before degrading to a tropical storm. Briefly emerging over the Taiwan Strait, the storm moved onshore for a second time in Fujian on July 13. The system was last noted as a tropical depression early on July 14.

Striking Taiwan as a strong typhoon, Soulik brought gusts up to 220 km/h (140 mph) and torrential rains. Numerous trees and power lines fell, leaving roughly 800,000 without electricity. Severe flooding prompted thousands to evacuate as well. Four people lost their lives on the island while 123 more were injured. Agricultural losses in Taiwan amounted to at least NT$1.27 billion (US$42.55 million). In East China, more than 162 million people were affected by the storm. Heavy rains and typhoon-force winds caused extensive damage and killed three people in Guangdong and two in Jiangxi. More than 2,000 homes collapsed and losses reached ¥2.51 billion (US$408 million).[1]

Meteorological history

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

On July 6, the Joint Typhoon Warning Center (JTWC) began monitoring a mid- to upper-level low associated with an easterly wave roughly 1,390 km (865 mi) northeast of Guam.[nb 1] Though satellite analysis indicated no low-level circulation, atmospheric conditions favoured development over the following days.[3] Early the next day, a broad surface low developed and scatterometer passes revealed strong easterly winds to the northeast of the center, which were expected to wrap into the system as it intensified. Despite still being a mostly cold-core system and considered subtropical by the JTWC,[4][5] the Japan Meteorological Agency (JMA) classified the system as a tropical depression.[6][nb 2] Over the following hours, rapid consolidation of the low took place with deep convective banding features wrapping around the low and a distinct transition into a tropical cyclone. In light of this, the JTWC commenced advisories on Tropical Depression 07W. Situated to the south of a subtropical ridge, the depression tracked steadily west to west-northwest over a region of high sea surface temperatures and low wind shear.[5]

Rapid deepening began on July 8 with an eye-like feature developing over the center. Additionally, the storm's westerly motion mitigated the negative effects of wind shear and its upper-level outflow greatly improved. The rate of strengthening surpassed constraints implemented within the Dvorak Technique, a tool used by meteorologists to estimate a cyclone's intensity based on satellite appearance. Both the JTWC and JMA estimated the system to have attained tropical storm status that morning,[8] with the latter assigning it the name Soulik.[9][nb 3] Throughout the day, the storm's eye became increasingly defined on SSMIS satellite images and the system attained typhoon status within 24 hours of being named.[6][11] Three tropical upper tropospheric troughs, two located to the northwest and one to the east of Soulik, greatly enhanced the typhoon's outflow and allowed for the development of a clear, 85 km (50 mi) wide eye which soon contracted to 40 km (25 mi) in diameter.[12][13] Due to the cyclone's proximity to the Philippines, the Philippine Atmospheric, Geophysical and Astronomical Services Administration also monitored the storm and assigned it the local name Huaning.[14] Soulik ultimately attained its peak intensity early on July 10 with winds of 185 km/h (115 mph) and a barometric pressure of 925 mbar (hPa; 27.32 inHg).[6] At this time, the JTWC estimated the storm to have been a Category 4-equivalent on the Saffir–Simpson hurricane scale with one-minute sustained winds of 230 km/h (145 mph).[15]

File:ISS-36 Typhoon Soulik (2).jpg
Typhoon Soulik seen from the International Space Station on July 11

A substantially larger secondary eye, estimated to be 315 km (195 mi) wide, began forming shortly after Soulik attained its peak on July 10. By this time, the deep convection was no longer symmetrical around the storm and was mostly located over the southern and eastern areas of the circulation.[16] This formation of a secondary eye indicated an eyewall replacement cycle was in progress; however, it coincided with the typhoon passing over a small area of very low oceanic heat content and prompted a weakening trend. Convection around Soulik's core gradually weakened, though it retained a well-defined inner eye.[17] The simultaneous occurrence of these two factors greatly hindered reorganization of the system and the weakening trend continued as the typhoon tracked west-northwest toward Taiwan.[18] On July 11, this trend temporarily abated as Soulik moved over the warm waters of the Kuroshio Current, allowing for structural improvement.[19] Early on July 12, dry air began to entrain into the northwestern portion of the circulation, suppressing thunderstorm development. Along the southeastern side of the storm, a large band of convection maintained itself and wrapped around a poorly defined eye.[20]

File:Soulik 2013-07-12 0505Z.jpg
Typhoon Soulik approaching Taiwan on July 12

Throughout July 12, dry air compromised the structure of Soulik as it worked into the system's center between bands of convection. Despite this, the storm's eye cleared somewhat, though remained ragged.[21] Later that day, the typhoon accelerated on its approach to Taiwan. Interaction with the mountainous terrain of the island soon had adverse effects on the storm and caused its eye to fill.[22] Soulik made landfall near Yilan City northern Taiwan, with estimated winds of 150 km/h (90 mph) between 1800 and 2100 UTC. Once onshore, the system quickly weakened below typhoon intensity;[6] however, the JTWC estimated that it retained typhoon strength during its crossing of the island. A phenomenon known as a lee side jump caused the circulation center to move abruptly west and Soulik emerged over the Taiwan Strait within six hours of landfall.[23] Once back over water, the storm failed to reorganize and its center became devoid of convection.[24] Remaining over water for less than 12 hours, Soulik made its final landfall near Fuzhou, Fujian with winds of 95 km/h (60 mph).[6][25] Once onshore, the storm quickly weakened to a tropical depression before it was last noted by the JMA later that day as it dissipated over land.[6]

Preparations

Philippines

Though the storm was forecast to remain away from the Philippines, it was expected to enhance the southwest monsoon over western areas of the country starting July 10.[26] Later that day, PAGASA issued Public Storm Warning Signal (PSWS) #1 for the Batanes in northern Luzon, indicating expected winds of 45 to 60 km/h (28 to 37 mph).[27] Fishermen along the northern and eastern seaboards of the region were advised to avoid sailing due to rough seas.[28] On July 12, the PSWS for the Batanes was raised to #2 as winds were expected to reach 61 to 100 km/h (38 to 62 mph) as the storm brushed the area. Additionally, the Calayan and Babuyan Islands were placed under PSWS #1.[29] Following the typhoon's landfall in Taiwan, the signal were discontinued for all areas during the morning of July 13.[30]

Japan

Hours after the JMA declared Soulik a tropical storm, the agency noted that the Ryukyu Islands were in the path of the storm.[31] By July 10, the Daitō Islands were expected to experience winds of 55 km/h (35 mph) as the storm passed to the south.[32] Due to the storm's large size, areas as far north as the Amami Islands were expected to see effects from the typhoon.[33] Starting during the evening of July 10 and continuing through July 12, ferry service in across the southern islands was suspended and cargo vessels were advised to take alternate courses.[34] Farmers on Miyako-jima were advised to harvest their mango crop, which was nearing peak time for harvest, before the typhoon struck.[35] As the storm moved closer to the Daitō Islands, the JMA urged residents to be aware of coastal conditions and potential storm surges.[36] On July 12, all flights to and from Ishigaki Airport and Miyako Airport were canceled.[37]

Taiwan

In Taiwan, over 8,000 people were evacuated from mountainous areas because of the threat of landslides from torrential rain. In Taiwan's cities, Kaohsiung had 3,000 residents evacuated while 2,000 were evacuated from Pingtung county.[38] The Taiwan Central Weather Bureau has put "Typhoon News and Typhoon Warning" into effect.[39]

Mainland China

File:Soulik Jul 13 2013 0240Z.jpg
Typhoon Soulik over eastern China on July 13

On July 11, the China Meteorological Administration (CMA) placed much of East China under a yellow alert, the second level of a four-tier warning system.[40] Additionally, Fujian was placed under an orange alert, the second-highest level of warning.[41] A national early disaster warning was also put in place that day, with local authorities across the country asked to be on duty around-the-clock.[40] Residents in Fujian, Jiangxi, and Zhejiang were advised to prepare for heavy rains capable of producing floods and landslides.[42] In Fujian, more than 304,000 people were evacuated prior to Soulik's arrival. Public transportation was brought to a standstill in some areas and 142 flights from Fuzhou Changle International Airport were canceled. The National Marine Environmental Forecasting Center also issued a top-level maritime for areas over the southern East China Sea, with waves expected to reach 6 to 10 m (20 to 33 ft). Additionally, roughly 5,500 soldiers were dispatched to 18 counties in Fujian to assist in possible rescue efforts.[43]

Impact

Japan

Skirting the southern Ryukyu Islands, Soulik brought typhoon-force winds to several areas on July 13, with a peak gust of 217 km/h (135 mph) measured in Yonaguni, Okinawa. The winds downed numerous trees and power lines across the region and left roughly 16,100 households without electricity. Significant crop damage took place as well with losses reaching ¥484 million (US$4.87 million), mostly from damage to sugar cane. A total of 11 people were injured in various incidents, one of whom was seriously injured. Rainfall from the storm peaked at 194 mm (7.6 in) in Ishigaki.,[44]

Taiwan

File:Typhoon Soulik damage Taipei 2013.jpg
Damage caused by Soulik in Taipei

According to the Central Weather Bureau, Soulik struck Taiwan with winds of 190 km/h (120 mph) and gusts as high as 220 km/h (140 mph). Winds up to 120 km/h (75 mph) buffeted Taipei, tearing roofs off buildings, downing power lines, and snapping or uprooting 1,000 trees.[45][46] At the height of the storm, roughly 800,000 residences were without power. Torrential rains, amounting to 900 mm (35 in) in Bailan, accompanied the destructive winds. Taipei 101 had its greatest sway amplitude since its completion, shifting up to 70 cm (28 in) during the storm.[47] Flash flooding and landslides caused widespread damage and forced thousands to evacuate. In Puli, Nantou, nine people had to be rescued from their homes as floods inundated the area. An official in the town stated that the typhoon was "more serious than we predicted." In the coastal city of Keelung, streets were covered in up to 30 cm (0.98 ft) of sea water. Low-lying areas along the Hsintien River in greater Taipei were also flooded and one aboriginal town was forced to evacuate.[45] Across the island, four people were killed by the storm: one from head trauma, another from falling off a roof, one from drowning, and a fourth from unknown causes.[48] Additionally, 123 people were injured in various incidents.[49] Substantial damage took place within the agricultural sector, with losses estimated in excess of NT$1.27 billion (US$42.55 million). Crop losses accounted for NT$1.12 billion (US$37.53 million) of this.[50] Rice, banana, pear, guava, and bamboo crops were the hardest hit across the island.[49] A total of 457 schools were damaged, with losses totaling to NT$46.3 million (US$1.5 million).[51]

Immediately following the typhoon, power companies deployed approximately 1,600 personnel to restore downed or interrupted transmission lines. Electricity was fully restored to the island by July 15.[52] Four days after the storm, a dog and four puppies that went missing in Miaoli County after a flash flood and landslide were found on a cliff side and rescued.[53]

Mainland China

Coastal Fujian was battered by typhoon-force winds and waves up to 10 m (33 ft) high. In Ningde, strong winds destroyed billboards and uprooted trees.[54] Preliminary estimates in the province indicated that 72 million people were affected by the storm, more than half of whom were temporarily displaced. At least 990 homes collapsed and direct economic losses reached ¥1.744 billion (US$284.2 million). Additionally, no casualties took place in the province, with media outlets remarking the storm as the "first won battle."[55] In Wenzhou, Zhejiang alone, 410,000 people were affected and economic losses amounted to ¥212 million (US$34.58 million).[56] Heavy rains from the storm extended into Guangdong where many areas recorded 100 to 250 mm (3.9 to 9.8 in) of rain; accumulations peaked at 292.5 mm (11.52 in) in Minamifuku. These rains triggered flooding in many areas of the province and affected 38.2 million people. Approximately 2 million were forced to evacuate their homes.[57] The Hanjiang River crested at 43.68 m (143.3 ft), 1.68 m (5.5 ft) above flood stage, with a flow rate of 5,230 m3 (18,400 ft3) per second. At least three people were killed in the province and 1,076 homes were destroyed with losses amounting to ¥350 million (US$57 million).[58] In Jiangxi, heavy rains from the storm peaked at 354.3 mm (13.95 in) with a province-wide average of 26.8 mm (1.06 in).[59] Two people were killed while another was listed as missing in the province. Approximately 35.84 million people were directly affected in Jiangxi, of whom 6,159 were displaced, and losses amounted to ¥353 million (US$57.5 million).[60]

Further north in Qingdao, Shandong, large quantities of sea lettuce washed ashore under the typhoon's influence. The city dispatched crews with heavy machinery in order to clear beaches of the lettuce.[61]

See also

Notes

  1. The Joint Typhoon Warning Center is a joint United States Navy – United States Air Force task force that issues tropical cyclone warnings for the western Pacific Ocean and other regions.[2]
  2. The Japan Meteorological Agency is the official Regional Specialized Meteorological Center for the western Pacific Ocean.[7]
  3. The name Soulik was submitted to the World Meteorological Organization by the Federated States of Micronesia and is a traditional Pohnpei chief's title.[10]

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 Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 6.2 6.3 6.4 6.5 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. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  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.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. 40.0 40.1 Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. 45.0 45.1 Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. 49.0 49.1 Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Lua error in package.lua at line 80: module 'strict' not found.
  61. Lua error in package.lua at line 80: module 'strict' not found.

External links