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

Typhoon Chanchu

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

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

Typhoon Chanchu (Caloy)
Typhoon (JMA scale)
Category 4 (Saffir–Simpson scale)
File:Typhoon Chanchu16-05-06.jpg
Typhoon Chanchu at peak intensity
Formed May 8, 2006
Dissipated May 23, 2006
(Extratropical after May 19, 2006)
Highest winds 10-minute sustained: 175 km/h (110 mph)
1-minute sustained: 230 km/h (145 mph)
Lowest pressure 930 hPa (mbar); 27.46 inHg
Fatalities 309 total
Damage $879 million (2006 USD)
Areas affected Philippines, coastal Vietnam, Taiwan, southeast China, Japan, South Korea
Part of the 2006 Pacific typhoon season

Typhoon Chanchu, known in the Philippines as Typhoon Caloy, was the most intense typhoon in the South China Sea in the month of May according to the Hong Kong Observatory (HKO). The first named storm of the 2006 Pacific typhoon season, Chanchu formed on May 8 in the vicinity of the Federated States of Micronesia and progressed westward. It gradually intensified into a tropical storm and later severe tropical storm before moving through the Philippines. On May 13, Chanchu entered the South China Sea and became a typhoon, according to the Japan Meteorological Agency (JMA). Warm waters and favorable outflow allowed the storm to quickly intensify to peak maximum sustained winds of 175 km/h (110 mph) on May 15. Around that time, the typhoon turned sharply to the north toward southeastern China. Chanchu weakened as it curved to the northeast, making landfall near Shantou, Guangdong on May 17 as a severe tropical storm. The government of China considered Chanchu the earliest typhoon to make landfall in the province. On the next day, the storm emerged into the East China Sea, becoming extratropical on May 19 before dissipating west of Kyushu.

Early in its duration, Chanchu moved through the Philippines, causing power outages and landslides in several islands. Despite a general warning against small boats sailing, a ferry departed Masbate and capsized due to the storm, killing 28 people. Throughout the country, 41 people died, and damage reached ₱117.57 million (PHP, $2.15 million USD).[nb 1] While in the South China Sea, Chanchu caught many Vietnamese fisherman off guard, causing 17 ships to sink and damaging several others. Chinese ships assisted in the search-and-rescue mission, ultimately rescuing 330 fishermen from 22 boats; however, 21 bodies were found, and the remaining 220 missing were presumed killed. In southern China, flooding and strong winds from Chanchu wrecked about 14,000 houses and damaged over 190,000 ha (470,000 acres) of crop fields. Damage was heaviest in Shantou where it moved ashore, with flooding covering roads and entering hundreds of homes. Damage in China totaled ¥7 billion yuan (RMB, $872 million USD), and there were 23 deaths. Rains from the typhoon killed two people in Taiwan after sweeping them up in a river, and crop damage there reached NT$158.88 million (NTD, $5 million USD). Later, high waves killed one person in Okinawa and left another person missing, while rains extended into South Korea.

Meteorological history

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

An area of convection, or thunderstorms, persisted on May 5 southeast of Yap State in the Federated States of Micronesia (FSM). Initially it remained disorganized while tracking to the west, although a circulation became more distinct on May 7, indicative of gradual organization.[1] At 06:00 UTC on May 8, the Japan Meteorological Agency (JMA)[nb 2] declared that a tropical depression had developed about 175 km (110 mi) northeast of Palau.[2] Five hours later, the Joint Typhoon Warning Center (JTWC)[nb 3] issued a tropical cyclone formation alert, and at 18:00 UTC they classified the system as Tropical Depression 02W. The system moved to the west-southwest, influenced by the subtropical ridge to the north. Early on May 9, the JTWC upgraded the depression to tropical storm status, and at 12:00 UTC the JMA followed suit by upgrading the system to Tropical Storm Chanchu. Also on that day, the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) began issuing warnings on the storm as Tropical Storm Caloy.[1]

File:Chanchu06.jpg
Satellite image of Chanchu near Samar on May 11

In its formative stages, Chanchu was located in an environment generally favorable for intensification. Its tracked shifted more to the west-northwest due to a building ridge to the south.[1][4] Late on May 10, the JTWC upgraded Chanchu to typhoon status, estimating 1 minute sustained winds of 140 km/h (85 mph). By contrast, the JMA estimated it intensified only into a severe tropical storm with winds of 95 km/h (60 mph).[2][5] Turning more to the west, Chanchu made landfall on Samar in the eastern Philippines on May 11. Despite moving through the archipelago, Chanchu intensified slightly within the Sibuyan Sea, striking Mindoro on May 12 with 1 minute winds of 160 km/h (100 mph), according to the JTWC.[1][5] On May 13, Chanchu emerged into the South China Sea, and later that day the JMA upgraded it to typhoon status.[2]

Upon reaching the South China Sea, Chanchu encountered an area of warm sea surface temperatures and low wind shear.[6] After an upper-level low to the east provided favorable outflow to the south and the east,[7] Chanchu rapidly intensified on May 14. While the storm was active, the JTWC upgraded Chanchu to a super typhoon with peak 1 minute winds of 250 km/h (155 mph),[1] although the agency later downgraded the peak winds to 230 km/h (145 mph). By contrast, the JMA estimated peak 10 minute winds of 175 km/h (110 mph) at 00:00 UTC on May 15.[5] According to the Hong Kong Observatory, the 10 minute winds reached 185 km/h (115 mph),[5] which made Chanchu the strongest typhoon in the South China Sea in the month of May.[8]

By the time Chanchu attained peak winds, an eastward-moving trough over China broke up the ridge to the north,[7] causing the typhoon to turn sharply to the north into a less favorable environment.[1] With decreased outflow and stronger wind shear, Chanchu began slowly weakening.[9] The eye initially remained small, but the outer eyewall deteriorated on May 16 as the convection decreased in the northern periphery.[10] The trough that previously weakened the ridge steered Chanchu to the north-northeast and forced an extratropical transition.[11] Late on May 17, the JMA downgraded the typhoon to a severe tropical storm.[2] Around that time, Chanchu made landfall near Shantou, Guangdong in southeastern China,[1] about 315 km (195 mi) east of Hong Kong;[12] the JTWC estimated landfall winds of 130 km/h (85 mph),[1] while the JMA estimated them at 110 km/h (70 km/h).[5] Early on May 18, the JTWC discontinued advisories, although the JMA continued tracking Chanchu over southeastern China through eastern Fujian province. Later on May 18, the storm emerged into the East China Sea, becoming fully extratropical at 00:00 UTC on May 19. The remnants continued toward Japan before dissipating at 18:00 UTC that day off the west coast of Kyushu in southern Japan.[1][2][5]

Preparations

File:Affected Philippine provinces by typhoon Chanchu 2006.PNG
Philippine provinces where public storm signals

Officials in southern Leyte recommended that residents evacuate to prevent a repeat of a deadly landslide in February 2006. Officials canceled several flights and ferry lines,[13] stranding 10,000 people.[14] In all, 2,144 people evacuated in the Philippines.[15] PAGASA issued a storm signal number 2 for several provinces along Chanchu's path, as well as storm signal number 1 for other areas, largely forecasting for rainfall and gusty winds.[16]

Vietnamese fishermen in the South China Sea received 24 hours of warning from the National Hydrometerological Forecast Center before Chanchu approached the area, less time than other agencies in the region.[17] At one point, Chanchu was forecast to become a strong typhoon and make landfall near Hong Kong. In response to the threat, officials at the Hong Kong Observatory, as well as in Macau, issued a standby signal to inform the public of the approaching typhoon.[18] The HKO issued a warning signal number 3 on May 17.[8] In the territory, 60 flights were canceled with another 14 delayed,[8] beaches were closed, and ferry service was disrupted.[19] Ahead of the storm, about 1 million people evacuated from coastal Guangdong and Fujian provinces to government warehouses, schools, tents, or the houses of relatives.[20] In the former province, 62,000 fishermen were ordered to return to port, while four flights were canceled at Guangzhou Baiyun International Airport. Residents were advised to remain indoors, and workers reinforced billboards in anticipation of the strong winds. Rail and boat transport was stopped between Guangdong and Hainan across the Qiongzhou Strait due to the typhoon.[19] Schools were closed in Guangdong during the storm's passage, although they remained open in Fujian.[21] In Shanghai, the speed limit of Donghai Bridge was halved because of strong winds.[22]

Ahead of the storm, the Central Weather Bureau in Taiwan issued land and sea warnings.[23] The Tainan city government and three county governments closed for one day. All domestic flights to offshore islands were canceled, and rail service was interrupted.[24] Later, airlines canceled 12 flights in Japan due to the storm.[25]

Impact

The Philippines and Malaysia

File:Chanchu2006rain - 2.png
Rainfall from Chanchu up to May 12

While moving through the Philippines, Chanchu affected several islands with strong winds and heavy rainfall. In Legazpi, Albay, strong waves wrecked 100 homes and left 1,500 people homeless.[13] High winds left widespread power outages, particularly in Mindoro, Batangas, and across the Bicol Region.[26] The storm severely damaged the banana industry and affected various other fruit crops.[27] Near Metro Manila, the winds damaged billboards, knocked over trees, and caused isolated power outages. Rough seas sank a ferry off Masbate, despite a warning against the operation of small craft, having left at sunrise to avoid the police. The Coast Guard rescued 18 passengers,[14] but 28 people died in the wreck.[26] An empty ferry sank at port in Tabaco. A ferry with 700 people aboard went missing, but the Coast Guard found it washed ashore with everyone safe on board. Similarly, an oil tanker washed ashore at Pinamalayan, Oriental Mindoro, and its crew of 13 was rescued.[14] Throughout the country, Chanchu killed 41 people,[19] mostly from the Masabate ferry wreck.[26] The storm damaged 5,630 homes, and destroyed 1,013 others,[15] forcing 53,307 people to leave their homes.[26] Agricultural losses totaled ₱71.57 million (PHP, $1.3 million USD),[nb 4] chiefly to the corn harvest,[26] with an additional ₱46 million (PHP, $850,000 USD)[nb 4] in infrastructure damage.[15]

While stalled over the South China Sea, Chanchu's large circulation caused an increase in rainfall over Malaysia.[29] The typhoon brought the onset of the summer monsoon in the South China Sea after shifting the prevailing winds over the region.[30]

Vietnam

While moving slowly through the South China Sea, Chanchu produced strong waves that struck the east coast of Vietnam. The associated flooding washed away many shrimp from coastal ponds and also entered Thu Bồn River, thus preventing its use as a source for irrigation for about 1,000 ha (2,500 acres) of rice paddy fields.[20] Due to its unexpected change in course and ferocity, Chanchu caught dozens of ships off guard and damaged communications, sinking 17 ships and damaging several others.[31] Initially, there were 400 fishermen missing,[32] although there was conflicting information with regard to the number of ships and people affected,[31] particularly with ships near Hainan or Taiwan.[33] Following a request from the Vietnamese government, the Chinese government deployed rescue ships on May 19, a day after the storm made its final landfall.[31] Offshore Quảng Ngãi Province, 94 fishermen sought refuge on a Chinese island,[34] and 22 boats were found in the Dongsha Islands offshore China.[31] One Chinese ship rescued 97 fishermen, but also found 18 people killed.[32] Chinese ships ultimately rescued 330 fishermen from 22 boats and provided them with food and water; this was the country's largest oceanic rescue at the time. Two Vietnamese boats departed from Quảng Ngãi to assist crews on damaged boats attempting to return to port.[31] Medical teams greeted the ships returning to harbor, while an altar was set up for the deceased.[33] After two weeks, the government of Vietnam ended the search, with 21 bodies found, and the remaining 220 missing fishermen presumed killed.[17]

China

Typhoon Chanchu was the earliest on record to strike Guangdong at the time, having struck the country 44 days earlier than the average date for the first strike. Rainfall in the country spread across Guangdong, Fujian, Jiangxi, and Zhejiang,[35] and Chanchu became the earliest typhoon to affect Shanghai in 80 years.[34] Rainfall totaled over 250 mm (9.8 in) in southeastern Guangdong and southwestern Fujian. In the former province, wind gusts peaked at 170 km/h (106 mph) in Huilai.[35]

Upon striking China, Chanchu produced deadly flooding and landslides along its path,[20] with flooding spreading as far northeast as Zhejiang province.[36] One landslide in Fujian killed eight people and wrecked two houses.[37] In Guangdong and Fujian, Chanchu wrecked 14,000 houses and damaged over 190,000 hectares (470,000 acres) of crop fields.[8] Damage was particularly heavy in Shantou, Guangdong, where Chanchu moved ashore.[34] There were about 200 flooded houses,[37] and many roads covered, after rivers flooded from the heavy rainfall. The storm also caused power outages in Shantou,[38] and damage there totaled ¥2.56 billion yuan (RMB, $320 million USD).[34] In nearby Xiamen, the typhoon forced 43 factories to temporarily close, resulting in a loss of ¥62.2 million yuan (RMB, $7.8 million USD).[nb 5][21] The storm killed eight people in Guangdong, five of them due to traffic accidents, and a further 15 in Fujian.[34] Overall damage was estimated at ¥7 billion yuan (RMB, $872 million USD),[nb 5] roughly evenly split between Guangdong and Fujian.[34] This was less than expected given the winds at landfall.[21]

While passing east of Hong Kong, the outer rainbands of Chanchu dropped 43.5 mm (1.71 in) of rainfall at Sha Tin. Sustained winds in the territory reached 96 km/h (60 mph), while gusts reached 146 km/h (91 mph), both recorded at Tate's Cairn. Chanchu produced a storm surge of 0.77 m (2.5 ft), causing minor flooding, sinking a yacht, and injuring one person who was swept into the sea. The storm downed several trees and damaged some scaffolding. Six people were injured in the territory, including three on a jetfoil bound for Macau.[8]

Taiwan, Japan, and South Korea

High waves in Taiwan washed an oil tanker ashore in Kaohsiung City; all 13 crew members were rescued with helicopters. In Kaohsiung County, the typhoon wrecked several dikes in coastal cities. Chanchu also produced heavy rainfall on the island, causing flooding and landslides, the latter of which covered a highway. Swollen rivers swept away three farmers in Hualien County, who were later rescued, and killed two sisters in Pingtung County underneath the Sandimen Bridge.[24] Crop damage totaled NT$158.88 million (NTD, $5 million USD).[23]

In Nishihara, Okinawa, high waves caused by Chanchu swept away three bathers. The Japan Coast Guard rescued one, another was killed, and the third remained missing as of May 23.[39] The remnants of Chanchu produced 121 mm (4.8 in) of rainfall in Gifu Prefecture in combination with a nearby cold front, causing one landslide.[40] A fallen tree in Nagasaki Prefecture caused a small power outage, and nearby there was a damaged home.[25]

The trough that engulfed Chanchu drew moisture from the typhoon, leading to heavy rainfall in portions of South Korea that reached 144 mm (5.7 in) on Jeju Island. Along with strong winds, the rains caused ferry and flight cancelations.[41]

Aftermath

File:Super Typhoon Chanchu.jpg
Satellite image of Chanchu on May 17

In the days after Chanchu moved through the Philippines, then-President Gloria Macapagal-Arroyo ordered that the country's National Disaster Coordinating Council help all towns affected by the storm. The agency helped coordinate search and rescue missions.[42] Several areas were declared a state of calamity, mostly on Mindoro, Samar, and Batangas.[43] The Tzu Chi Foundation visited islands in eastern Samar, providing money to the families whose houses were destroyed. Towns in the region also assisted by supplying thatch to rebuild homes.[27] In Oriental Mindoro, the Philippine Red Cross provided food and relief items to families in Calapan.[20] The Adventist Development and Relief Agency also provided building materials for 200 families in Mindoro.[44] Ultimately, the government provided storm victims with ₱415.1 million (PHP, $7.6 million USD)[nb 4] worth of relief supplies.[26] Rainfall from the storm caused a red tide in Taal Lake, after dispersing a Ceratium bloom.[45]

Immediate after Chanchu's China landfall, officials began distributing tents, quilts, water purification tablets, and disinfectant.[20] The government of Fujian set up a ¥8.5 million yuan (RMB, $1.06 million) relief fund.[34] In the months after Chanchu, China suffered from several other damaging tropical cyclones, including Tropical Storm Bilis and Typhoon Saomai.[46] Damage from Chanchu forced the China National Offshore Oil Corporation to shut down for a time, which contributed to an annual decrease in its oil output.[47] The Chinese government recognized 50 people who assisted in the South China Sea search and rescue mission, and two vessels were declared "hero ships".[48]

Vietnamese president Trần Đức Lương expressed his thanks to the Chinese government on May 22 for rescuing the Vietnamese on the imperiled ships.[49] Residents and industries in Vietnam raised ₫360 million (VND, $36,000 USD)[nb 6] for the families of the deceased fishermen, as well as providing 1 ton of rice. Trade unions encouraged workers to donate one day's salary to help storm victims.[50] The Vietnamese embassy in India raised about $1,000 (USD)[51] and Vietnamese people living in Greece raised ₫26 million (VND, €1,300 Euros) for storm victims.[52] Ultimately, 43 different organizations and people donated $29,000 (USD) to the Vietnam Red Cross.[53] The country's Ministry of Labour, Invalids and Social Affairs presented an award to the Vietnam News Agency in June 2006 for its charitable donations, which included the distribution of ₫112 million (VND, $11,200 USD)[nb 6] to storm victims.[54] One fisherman claimed to survive for two weeks in the open seas before being rescued, although he later confessed that he was safely on another boat, and wanted his family to retain the disaster compensation; after the man revealed that he had lied, his family was able to retain the relief funds due to their poverty.[55] The head of the Vietnam Institute of Meteorology, Hydrology and Environment resigned two weeks after Chanchu killed many fishermen because of inadequate warnings. Then-Deputy Prime Minister Nguyen Tan Dung ordered a review of the meteorological agency as a result.[17] Within a few years after the typhoon, the meteorological agency began issuing more accurate and timely forecasts.[56] After the many deaths of fishermen from Chanchu, the Vietnam government prevented any fishermen from leaving harbor during the passage of Typhoon Durian in November.[57]

After the season ended, members of the 39th meeting of the Typhoon Committee of the World Meteorological Organization met in Manila in December 2006. They discussed retiring the name "Chanchu", along with four other names from the season.[29] During the 40th meeting in November 2007, the Typhoon Committee approved the retirement, announcing that the name "Sanba" would replace Chanchu on the basin name lists beginning in 2008.[58]

See also

Notes

  1. All damage totals are in 2006 values of their respective currencies.
  2. The Japan Meteorological Agency is the official Regional Specialized Meteorological Center for the western Pacific Ocean.[2]
  3. 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.[3]
  4. 4.0 4.1 4.2 The total was originally reported in Philippine pesos. Total converted via the Oanda Corporation website.[28]
  5. 5.0 5.1 The total was originally reported in Chinese yuan. Total converted via the Oanda Corporation website.[28]
  6. 6.0 6.1 The total was originally reported in Vietnamese dong. Total converted via the Oanda Corporation website.[28]

References

  1. 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 2.2 2.3 2.4 2.5 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 5.3 5.4 5.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. 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 8.2 8.3 8.4 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. 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found.
  14. 14.0 14.1 14.2 Lua error in package.lua at line 80: module 'strict' not found.
  15. 15.0 15.1 15.2 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. – via Lexis Nexis (subscription required)
  17. 17.0 17.1 17.2 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. 19.0 19.1 19.2 Lua error in package.lua at line 80: module 'strict' not found.
  20. 20.0 20.1 20.2 20.3 20.4 Lua error in package.lua at line 80: module 'strict' not found.
  21. 21.0 21.1 21.2 Lua error in package.lua at line 80: module 'strict' not found. – via Lexis Nexis (subscription required)
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. 23.0 23.1 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. 26.0 26.1 26.2 26.3 26.4 26.5 Lua error in package.lua at line 80: module 'strict' not found.
  27. 27.0 27.1 Lua error in package.lua at line 80: module 'strict' not found.
  28. 28.0 28.1 28.2 Lua error in package.lua at line 80: module 'strict' not found. Cite error: Invalid <ref> tag; name "oanda" defined multiple times with different content Cite error: Invalid <ref> tag; name "oanda" defined multiple times with different content
  29. 29.0 29.1 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. 31.0 31.1 31.2 31.3 31.4 Lua error in package.lua at line 80: module 'strict' not found.
  32. 32.0 32.1 Lua error in package.lua at line 80: module 'strict' not found.
  33. 33.0 33.1 Lua error in package.lua at line 80: module 'strict' not found.
  34. 34.0 34.1 34.2 34.3 34.4 34.5 34.6 Lua error in package.lua at line 80: module 'strict' not found.
  35. 35.0 35.1 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. 37.0 37.1 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. 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. – via Lexis Nexis (subscription required)
  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. 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. – via Lexis Nexis (subscription required)
  48. Lua error in package.lua at line 80: module 'strict' not found. – via Lexis Nexis (subscription required)
  49. 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. – via Lexis Nexis (subscription required)
  54. Lua error in package.lua at line 80: module 'strict' not found. – via Lexis Nexis (subscription required)
  55. Lua error in package.lua at line 80: module 'strict' not found. – via Lexis Nexis (subscription required)
  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.

External links