Typhoon Neoguri (2008)
<templatestyles src="Module:Hatnote/styles.css"></templatestyles>
Typhoon (JMA scale) | |
---|---|
Category 3 (Saffir–Simpson scale) | |
File:Neoguri 17 apr 2008 0550Z.jpg
Typhoon Neoguri on April 17
|
|
Formed | April 13, 2008 |
Dissipated | April 21, 2008 |
(Extratropical after April 20, 2008) | |
Highest winds | 10-minute sustained: 150 km/h (90 mph) 1-minute sustained: 185 km/h (115 mph) |
Lowest pressure | 960 hPa (mbar); 28.35 inHg |
Fatalities | 26 total |
Damage | $65 million (2008 USD) |
Areas affected | Philippines, China |
Part of the 2008 Pacific typhoon season |
Typhoon Neoguri, known in the Philippines as Typhoon Ambo, was the earliest tropical cyclone on record to strike The People's Republic of China. The first named storm in the 2008 Pacific typhoon season, named after the Korean word for raccoon dog, it formed from a low pressure area on April 13 to the east of the Philippine island of Mindanao, and after crossing the island it intensified into a tropical storm in the South China Sea. Environmental conditions allowed for quick strengthening, with Neoguri attaining typhoon status on April 16. The typhoon reached its peak intensity on April 18 as it approached the island of Hainan, and subsequently it turned northward. Due to increased wind shear and cooler waters, Neoguri rapidly weakened and made landfall as a minimal tropical storm in southern China on April 19.
In the southern Philippines, the storm brought heavy rainfall, which left a person missing when a boat capsized. The typhoon left 40 fishermen missing in the South China Sea. Neoguri brought heavy rainfall as it made its final landfall on China, causing moderate damage totaling over ¥296 million (2008 RMB, $42 million 2008 USD). Three deaths occurred in China.
Contents
Meteorological history
An area of disorganized convection persisted east-northeast of Palau on April 11 in association with a sharp easterly wave, and within the system, a low pressure area was evident between Palau and Yap. Located beneath a developing anticyclone, with limited wind shear and enhanced diffluence, the system encountered favorable conditions for development.[1] By April 13, a low-level circulation had formed and started consolidating about 260 km (160 mi) southeast of Bislig City on Mindanao island in the Philippines. At around the same time, weak rainbands began wrapping into the center.[2] At 1200 UTC on April 13, the JMA classified it as a weak tropical depression.[3] Its development was impeded somewhat as it crossed Mindanao and Negros island, though the circulation consolidated while convective banding features increased.[4] Later that day, the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) classified the system as Tropical Depression Ambo,[5] and early on April 14 the Joint Typhoon Warning Center (JTWC) classified it as Tropical Depression 02W about 300 km (185 mi north of the Zamboanga Peninsula).[6] Also, PAGASA declared "Ambo" at 0300 UTC April 14 to be within Dumaguete City.[7]
The depression continued westward, along the southern periphery of a strong subtropical ridge extending from southeastern Asia to north of Luzon. After it entered the Sulu Sea, the convection and circulation continued to consolidate, while its anticyclone aloft provided excellent outflow. Based on satellite intensity estimates using the Dvorak technique, the JTWC upgraded the depression to Tropical Storm 02W midday on April 14.[8] At 0000 UTC on April 15, the JMA classified the system as a full tropical depression,[9] and six hours later the agency upgraded it to Tropical Storm Neoguri after it crossed Palawan island into the South China Sea.[10] Shortly thereafter, the PAGASA issued its last advisory on the cyclone as the storm moved out of their area of warning responsibility.[11]
After attaining tropical storm status, significant intensification was limited due to a slight increase in wind shear as well as impeded outflow.[12] The slowing of the strengthening trend was temporary, and by early on April 16 the organization had rapidly improved.[13] As a result, the JMA upgraded Neoguri to a severe tropical storm.[14] Warm water temperatures contributed to further intensification, and an eye formed in the center of the convection.[15] At 1200 UTC on April 16, the JMA classified Neoguri as a typhoon about 350 km (220 mi) east of Qui Nhon, Vietnam.[16] An approaching mid-level trough turned the typhoon northwestward,[15] which enhanced outflow and contributed to further intensification.[17] Late on April 17, the JTWC assessed Neoguri as attaining peak winds of 175 km/h (110 mph), averaged over a duration of one minute, near the Paracel Islands.[18] Early the next day, the JMA estimated Neoguri reached its peak intensity with ten-minute sustained winds of 150 km/h (90 mph), about 190 km (120 mi) east of Sanya on the southern tip of Hainan.[19]
Typhoon Neoguri underwent an eyewall replacement cycle around the time it reached peak intensity; the inner eyewall collapsed, and the outer eyewall contracted to a diameter of 65 km (40 mi). Upon attaining peak winds, the typhoon had turned northward,[20] and the China Meteorological Administration assessed Neoguri as moving ashore along Hainan island near Wenchang.[21] However, other agencies assessed the typhoon as tracking parallel to the eastern coastline just offshore. Land interaction and wind shear weakened the typhoon,[22] and by April 19 it had weakened to a tropical storm. Cooler waters contributed to further weakening, causing its convection to diminish significantly and for its circulation to become elongated.[23] After turning to the north-northeast, Neoguri made landfall on Guangdong province in southern China, a short distance west of Macau as a weak tropical storm.[24] Neoguri made landfall on China earlier than any other tropical cyclone on record, about two weeks prior to the previous record set by Typhoon Wanda in 1971.[25] Shortly after moving ashore, the JTWC issued its final warning as the cyclone began dissipating.[26]
Preparations and impact
As Ambo (Neoguri) passed directly through many parts Visayas and Mindanao, PAGASA issued Public Storm Warning Signals for these areas. Signal number one was issued for southern Negros, Siquijor and Camiguin.[27] This storm signal was later scaled back up until the storm reached Palawan and the South China Sea.[28]
As a tropical depression, Neoguri (Ambo) brought heavy rainfall to many portions of the Philippines, including even Metro Manila.[29] In Cebu City, the precipitation caused flooding, which forced 62 people to evacuate their houses.[30] In the Camotes Islands, rough waves capsized a motorboat with six passengers; five were rescued, with the other reported missing.[31] But the storm at least alleviated for a few days the heat that has been experienced over Luzon from the past weeks.[32] However, the storm did not stop the Palarong Pambansa (National Games in the Philippines) which was held in Puerto Princesa City in Palawan, one of the areas said by PAGASA to see stormy weather.[33]
In preparation for the storm, about 21,800 fishing boats in the Chinese province of Hainan returned to port,[34] and about 120,000 people evacuated from fish farms and low-lying areas on the island. Officials halted ferry service between Hainan and the Leizhou Peninsula in Guangdong province.[35] Offshore, 56 fishermen rode out the storm in a shelter on the Paracel Islands; 38 people were rescued shortly after the storm, and initially eighteen people were reported missing.[36] The eighteen missing fishermen were found thirty hours after Neoguri struck. The ship they were on had sunk, and the crew clung to debris and made makeshift rafts to survive in the waters. However, another 18 Chinese fisherman and 22 Vietnamese fisherman remain missing.[37] On Hainan island, the storm left the city of Wenchang without power.[36]
Along the mainland, ferry service was temporarily stopped between Hong Kong and Macau. At the Hong Kong International Airport, over 200 flights were delayed due to the threat of the storm; additionally, around 30 were canceled, and 66 others were deviated elsewhere.[38] The Hong Kong Observatory issued a standby warning signal on April 17, which was the second earliest standby signal on record.[39] One day later, the No. 3 strong wind signal was issued, the earliest in record.[40] As it moved ashore, the storm brought heavy rainfall, with one station reporting 237 mm (9.35 in) in one day.[41] Strong winds downed coconut and banana trees, with agricultural damage totaling over ¥200 million (2008 RMB, $28 million 2008 USD).[42] Structural damage amounted to ¥96 million (2008 RMB, $14 million 2008 USD). Three fatalities were confirmed in China, two due to a road being covered in a mud flow, and another due to winds blowing a sheet of aluminum into a person, throwing them off the roof of a stadium.[43]
See also
References
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ http://i28.tinypic.com/20szxnl.jpg
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 15.0 15.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ http://i31.tinypic.com/fut0m0.jpg
- ↑ http://i26.tinypic.com/124hg0i.png
- ↑ http://www.gmanews.tv/story/89236/Ambo-brings-early-morning-rains-to-Metro
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ http://www.gmanews.tv/story/89365/Ambo-tames-fiery-days-in-parts-of-Luzon
- ↑ http://www.gmanews.tv/story/89520/Athletes-arrive-in-Palawan-for-Palarong-Pambansa-despite-Ambo
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 36.0 36.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
External links
![]() |
Wikimedia Commons has media related to [[commons:Lua error in Module:WikidataIB at line 506: attempt to index field 'wikibase' (a nil value).|Lua error in Module:WikidataIB at line 506: attempt to index field 'wikibase' (a nil value).]]. |
- The JMA's Best Track Data on Typhoon Neoguri (0801) (Japanese)
- The JMA's RSMC Best Track Data (Graphics) on Typhoon Neoguri (0801)
- The JMA's RSMC Best Track Data (Text)
- The JTWC's Best Track Data on Typhoon 02W (Neoguri)