Loading AI tools
From Wikipedia, the free encyclopedia
The 2008 Pacific typhoon season was a below average season which featured 22 named storms, eleven typhoons, and two super typhoons. The season had no official bounds; it ran year-round in 2008, but most tropical cyclones tend to form in the northwestern Pacific Ocean between May and November.[1] These dates conventionally delimit the period of each year when most tropical cyclones form in the northwestern Pacific Ocean.
| 2008 Pacific typhoon season | |
|---|---|
Season summary map | |
| Seasonal boundaries | |
| First system formed | January 13, 2008 |
| Last system dissipated | December 18, 2008 |
| Strongest storm | |
| Name | Jangmi |
| • Maximum winds | 215 km/h (130 mph) (10-minute sustained) |
| • Lowest pressure | 905 hPa (mbar) |
| Seasonal statistics | |
| Total depressions | 40, 1 unofficial |
| Total storms | 22 |
| Typhoons | 11 |
| Super typhoons | 2 (unofficial) |
| Total fatalities | 1,965 total |
| Total damage | $5.97 billion (2008 USD) |
| Related articles | |
The scope of this article is limited to the Pacific Ocean, north of the equator and west of the International Date Line. Storms that form east of the date line and north of the equator are called hurricanes; see 2008 Pacific hurricane season. Tropical storms formed in the entire Western North Pacific basin are assigned a name by the Japan Meteorological Agency. Tropical depressions formed in this basin are given a number with a "W" suffix by the United States' Joint Typhoon Warning Center. In addition, the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) assigns names to tropical cyclones (including tropical depressions) that enter or form in the Philippine area of responsibility. These names, however, are not in common use outside of the Philippines.
| TSR forecasts Date | Tropical storms | Total Typhoons | Intense TCs | ACE | Ref. |
|---|---|---|---|---|---|
| Average (1965–2007) | 26.6 | 16.8 | 8.7 | 303 | [2] |
| March 10, 2008 | – | – | 6.4 | 237 | |
| May 6, 2008 | 28.3 | 18.2 | 7.7 | 274 | [3] |
| July 6, 2008 | 28.3 | 18.2 | 7.5 | 268 | [4] |
| August 5, 2008 | 28.3 | 18.2 | 7.8 | 277 | [5] |
| Other forecasts Date | Forecast Center | TCs | Tropical storms | Typhoons | Ref |
| April 18, 2008 | GCACIC | 33 | 30 | 19 | [6] |
| June 24, 2008 | GCACIC | 33 | 30 | 19 | [7] |
| July 16, 2008 | PAGASA | 22 | – | – | [8] |
| 2008 season | Forecast Center | Tropical cyclones | Tropical storms | Typhoons | Ref. |
| Actual activity: | JMA | 38 | 22 | 11 | |
| Actual activity: | JTWC | 27 | 27 | 12 | |
| Actual activity: | PAGASA | 21 | 16 | 11 | |
Each season several national meteorological services and scientific agencies forecast either the expected amount tropical cyclones, tropical storms, and typhoons forming in a season and/or how many tropical cyclones will affect a country or territory.
Since the 2000 typhoon season, the Laboratory for Atmospheric Research or the Guy Carpenter Asia-Pacific Climate Impact Centre (GCACIC), both of the City University of Hong Kong have issued forecasts of activity for each upcoming typhoon season.[6] Forecasts are issued in April and June of each year and predict how many tropical cyclones, tropical storms, and typhoons there will be in a season.[6] This season, the GCACIC is predicting a slightly more active than usual season. An average season, according to the GCACIC, has 31 tropical cyclones, 27 named storms, and 17 typhoons. In its April forecast, the GCACIC predicted 33 total tropical cyclones, 30 named storms, and 19 typhoons before predicting the same number of systems, tropical storms, and typhoons in its June forecast.[6][7]
Since the 2000 typhoon season, the Tropical Storm Risk Consortium (TSR) of the University College of London have issued forecasts of activity for each upcoming typhoon season. During 2008 forecasts were issued in early March, May, July and August and predict how many tropical storms, typhoons and intense typhoons there will be during a season.[nb 1][9] In its March forecast, TSR Predicted that the season would be about 20% below average with six intense tropical cyclones, however due to conflicting climate signals it was not possible to predict how many tropical storms and typhoons would form.[9] In its May forecast, TSR were now able to predict how many tropical storms and typhoons, would form during the season.[3] They also predicted that the season would be near normal with 28 tropical storms, 18 typhoons and 8 intense typhoons forming during the season.[3] In their July and August forecasts, TSR predicted the same amount of tropical storms and typhoons and intense typhoons as their May forecasts.[4][5]
As the name Frank was retired from PAGASA's naming lists they also released a prediction stating that there would be 16 more Tropical cyclones of any strength to pass through PAGASA'S area of responsibility which added to the six that had already moved through PAGASA's area of responsibility brought a total of 22 cyclones to pass through the PAGASA's area of responsibility during 2008.[8]
The first tropical depression of the season, formed in mid January to the west of the Philippines. As it moved west, the depression did not develop any further and dissipated on January 18. After two more Tropical depressions, the first named storm Typhoon Neoguri formed in April to the east of Mindanao. During May as a result of convection being enhanced within the Philippine sea and the South China Sea four named storms formed which along with 1971 and 1980 was the joint highest incidence in May since 1951. Between June and October, the region was considered to be very quiet by the JMA as they only named 13 tropical cyclones. In November and December, only four tropical cyclones were named by the JMA and all four formed within the Philippine sea and the South China Sea.
Early on January 11, the JTWC reported that an area of convection had persisted about 1,010 km (630 mi) to the southeast of Manila in the Philippines.[10] The disturbance was located near to a developing low level circulation center which was weak and remained displaced from the deep convection whilst located in an area of low to moderate vertical windshear.[10] During the next 24 hours the disturbance developed further with a Tropical Cyclone Formation Alert being issued the next day by the JTWC as the disturbance now had a well defined low level circulation center with convective banding on the northwestern edge.[11] Early on January 13, both the JMA and the JTWC reported that the first depression of the season had developed about 360 km (220 mi) to the west of Manila.[12][13] Later that day the JMA reported that the depression had reached its 10-minute peak windspeeds of 55 km/h (34 mph).[14] However early on January 14 the JTWC reported that the depression had continued to intensify and upgraded the depression to a Tropical storm and then six hours later reported 1-minute peak windspeeds of 65 km/h (40 mph).[13] Later that day it was downgraded to a Tropical depression due to weakening deep convection and a partially exposed low level circulation center.[13][15] Over the next few days the depression moved towards the east until early on January 18 when both the JMA and the JTWC reported that it had dissipated off the Malaysian coastline.[13][16] There were no reports of any damages or casualties associated with the depression.[17]
On April 11, area of convection with an area of low pressure was located between Palau and Yap.[18] Early on April 13, a low-level circulation developed near Mindanao.[19] The JMA designated the system as a minor tropical depression on the same day,[20] and PAGASA began warning on the system, naming it Tropical Depression "Ambo".[citation needed] The low continued to get better organized and early on April 14, the Joint Typhoon Warning Center began issuing advisories on Tropical Depression 02W, which was located about north of Zamboanga City, Philippines.[21] Later that day, the agency upgraded it to tropical storm status, based on satellite intensity estimates.[22] The JMA upgraded the system to a tropical storm, naming it Neoguri, the next day.[23] Early April 16, the system was upgraded to severe tropical storm status,[23] and then reached typhoon status a few hours later.[23] The typhoon continued north, weakening as it did so.[24][25] The cyclone made landfall as a weak tropical storm on Guangdong province in southern China,[23] and the final advisories from both agencies were issued shortly after.[26][27]
As the typhoon approached and passed Hainan Province, about 120,000 people were evacuated from low-lying areas.[28] According to the China Meteorological Administration, it was the earliest in the year a tropical cyclone had ever impacted China (the old record was for Typhoon Wanda on May 3, 1971). [29] 42,000 residents were displaced in the aftermath of Neoguri.[30] 18 Chinese fisherman and 22 Vietnamese fisherman remain missing due to the storm.[31] 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.[32]
Early on May 7, PAGASA designated an area of low pressure which was about 790 km east of Mindanao as Tropical Depression Butchoy.[33] Around the same time the Japan Meteorological Agency (JMA) and the Joint Typhoon Warning Center (JTWC) also designated the area of low pressure as a Tropical depression with the JTWC assigning the number 03W to the depression.[23][34]
Later that day the JMA upgraded the Tropical Depression to Tropical Storm status with RSMC Tokyo assigning the name Rammasun to the storm.[23] It quickly organized, intensifying into a typhoon on May 9.[23] Rapid intensification continued and it strengthened into a Category 4-equivalent typhoon by early on May 10,[35] and a super typhoon by midday.[36]
Rammasun continued on a northerly path, and reached a peak of 105 knots (194 km/h) and 915 hPa on May 10.[23] Soon after, the typhoon began slowly weakening. The JTWC downgraded it to a typhoon on May 11.[37] On May 12, the weakening became more rapid, and the JMA downgraded the system to a severe tropical storm,[23] while the JTWC issued its last advisory, noting that it was extratropical.[38] The JMA, however, held onto Rammasun until early May 13, when it downgraded the cyclone to a low and issued its final advisory.[23] Though it never hit land, it was the second strongest May typhoon in recorded history, behind Typhoon Lola of 1986.[citation needed]
Rammasun brushed the Japanese coastline as it became extratropical on May 13 delivering strong winds and high waves. Along with moderate to heavy rain, winds gusted up to 52 mph (84 km/h) as the storm moved out to sea.[39]
A strong storm from the "tail" of Rammasun struck the Philippines as it passed south of Japan. The winds brought by the storm caused severe damage to some buildings and numerous trees some weighing tonnes were uprooted. The damage may have been due to a possible tornado but there is no clarification for this possibility. At least 40 people were injured and damage totaled to 11 million PHP (US$280,000).[40][41]
On May 13, a tropical disturbance formed about 550 km (340 mi), to the east of Manila in the Philippines.[42] The disturbance was located in an area of low vertical wind shear and had a consolidating low-level circulation center.[42] The JTWC then issued a Tropical Cyclone Formation Alert on the disturbance early the next day, as deep convection was building near to the low-pressure area.[43] Later that day both the JTWC and the JMA upgraded the disturbance to a tropical depression, citing good outflow.[44][45][46] Early on May 15, as the storm was moving towards the northwest, the JMA upgraded the depression to a tropical storm.[47] The Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) then designated the storm as Tropical Depression Dindo.[48] While the storm accelerated to the northwest in response to a mid-latitude trough,[49] the JTWC upped into a tropical storm and had reached its peak intensity with winds of 75 km/h (45 mph).[50] Early on May 16, both PAGASA and the JTWC issued their final advisories on the storm as it approached the edge of PAGASA's Area of responsibility, with the JTWC reporting that Matmo was now extratropical.[51][52] However, data from the JMa suggested that it obtained peak wind speeds of 95 km/h (60 mph) at this time, which made Matmo a severe tropical storm.[47] Though, within their next advisory, the JMA downgraded Matmo to a tropical storm before dissipating the net day.[47][53]
In preparation for Tropical Storm Matmo, the Japan Meteorological Agency issued warnings for the, Naha, Moji and Yokohama areas of Japan,[54] but in the end, there was no impact.[55][56]
Early on May 14 PAGASA upgraded a tropical disturbance west of the Philippines to Tropical Depression Cosme.[57] Later that day the JTWC issued a TCFA,[58] later the first advisory on the system as Tropical Depression 05W.[59] On May 16, the JMA upgraded 05W to Halong.[60] Later that day, it was upgraded to a Severe Tropical Storm by JMA,[60] and a Typhoon by JTWC,[61] and reached its peak of 60 knots (110 km/h) early May 17.[60] It made landfall on western Pangasinan early May 17,[62] and weakened while crossing northern Luzon,[63][64] but after reaching open waters it re-organized while accelerating northeastward. The system intensified to a severe tropical storm again,[60] but never reached its previous peak intensity and began weakening as it moved northeast.[63] The JTWC and the JMA issued their final advisories on May 20.[65][66]
In Luzon, the storm caused 58 deaths and $94 million (USD) in damage. The storm destroyed 43,365 houses and damaged 188,830 more. Most of the damages reported were in Northern Luzon.[67] Meanwhile, Mindoro and Panay islands were also affected as the storm-induced southwest monsoon brought rains and floods to those areas.
A tropical disturbance formed south of Guam on May 25.[68] On May 26, the JMA recognized it as a weak tropical depression,[69] and later that day, the JTWC issued a TCFA on the system.[70]
Early on May 27, the JTWC issued its first advisory on Tropical Depression 06W.[70] Hours after, the JMA designated the system as Tropical Storm Nakri.[23] Early on May 28, the JMA upgraded it to a severe tropical storm.[23] Twelve hours later, the JTWC upgraded 06W to a typhoon. Later that day, Nakri strengthened at a more rapid pace and the rapid intensification continued into May 29, when Nakri strengthened to a Category 4-equivalent typhoon. PAGASA then issued its first advisory on the storm on early on May 30 and named it "Enteng". By May 31 it began to weaken as it moved north.[23] But on the next day, it started to re-intensify slightly.[23] On June 2, it began to undergo transition to an extratropical system.[23] And later, both JTWC and JMA stopped issuing advisories as it already degenerated to an extratropical low.[23][71]
The name Nakri was submitted by Cambodia and refers to a type of flower found in the country.
On June 18, an area of low pressure that the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) had been monitoring for a few days was upgraded to Tropical Depression Frank.[72] Later that day both the Joint Typhoon Warning Center (JTWC) and the Japan Meteorological Agency (JMA) started issuing full advisories on Frank with the JTWC designating it as Tropical Depression 07W.[73][74] Early the next day the JMA upgraded the tropical depression to a tropical storm and assigned the name Fengshen.[23] Tropical Storm Fengshen then rapidly intensified that day by becoming a severe tropical storm and then intensifying into a typhoon later that day.[23] The next day Typhoon Fengshen made landfall in eastern Samar in the central Philippines and travelled northwest over the islands.[75]
Fengshen was initially forecast to go through Bicol Region but later on shifted its course further westward, eventually going towards the direction of Mindoro Province. However, before even reaching Mindoro it again shifted its direction northward towards the direction of Metro Manila, mainly because of the weakening of the High Pressure area system in the northern part of the Philippines.[76]
Typhoon Fengshen, after creating havoc in the Philippines, emerged into the South China Sea on the 22nd of June and moved northwards towards China.[77] After moving into the South China Sea both the JMA and PAGASA downgraded it to a severe tropical storm while the JTWC downgraded Fengshen from a Typhoon to a Tropical Storm.[23][78][79] PAGASA then issued its final advisory on Tropical Storm Fengshen (Frank) due to Fengshen leaving PAGASA's Area of Responsibility.[80] Late in the evening of the 24th June Tropical Storm Fengshen made landfall on Shenzhen, Guangdong, before moving into mainland China.[81] The next day the JTWC downgraded Fengshen to a tropical depression and issued their final warning on the system.[82] The JMA then announced their final warning as they downgraded Fengshen to a tropical depression.[23]
On July 4, PAGASA reported that Tropical Depression Gener formed in the South China Sea to the west of the Philippines.[83][84] The precursor to Gener earlier moved across Luzon, producing 13 mm (0.51 in) of rain in the Ilocos Region.[84][85] The system had deep convection persisting on the western side of its developing low level circulation center,[86] although it was in an area of moderate wind shear,[86] and rapid development was not expected.[86] On July 7, Gener left the PAGASA area of responsibility.[87] The Joint Typhoon Warning Center (JTWC) issued a Tropical Cyclone Formation Alert on July 7 as the circulation strengthened, despite the convection being disorganized due to the shear.[88] Later that day the JMA reported that the system become a minor Tropical Depression, although the Hong Kong Observatory (HKO) did not follow suit.[89][90] The system rapidly weakened as it moved ashore on China to the east of Hong Kong.[91] Early on July 8 the JMA issued their last advisory on the depression.[92] There was no damage reported in China, although the system produced heavy rainfall in Guangdong Province.[90]
Early on July 13, the Japan Meteorological Agency (JMA), began to issue full advisories on a Tropical depression, which was located to the east of the Philippines.[93] Later that day PAGASA allocated the name Helen to the depression, followed the next day by the Joint Typhoon Warning Center (JTWC) designating the number 08W. Early on the 15th July both the JTWC, and the JMA upgraded the depression to Tropical Storm status, with RSMC Tokyo assigning the name "Kalmaegi" to the storm. Early on the 17th, Kalmaegi began rapidly intensifying; both the JTWC and JMA upgraded Kalmaegi to a Typhoon.
In the Philippines, it passed over Northern Luzon (mostly affecting Ilocos and Cagayan Valley), where it killed two people, left more than 31,129 people affected and damaged ₱ 7 million worth of property.[94] The storm also hit 82 villages (all in Northern Luzon) and caused around ₱45,000 worth of damage to farmland and livestock,[95] Typhoon Kalmaegi, which was downgraded to tropical storm status by Taiwan's Central Weather Bureau while still east of the country, made landfall at Ilan County in northeast Taiwan in the evening of July 17 at 19:40 local time (13:40 UTC) and emerged into the Taiwan Strait at 7:20 in the morning local time (01:20 UTC) on July 18.[96] At least nineteen died due to the storm and six are currently reported as missing.[97] Tainan County (now part of Tainan City) in southern Taiwan reported more than 1100 mm of rainfall in some mountain regions.[98] The storm caused NT$ 300 million worth of damage,[99] including an estimated US$16 million in agricultural losses,[97] and the typhoon destroyed about 5,100 hectares of orchards and crops.[99]
From Taiwan, the typhoon, now downgraded to a tropical storm, turned toward southeast China.[99] In Xiapu County of Fujian Province, the tropical storm made landfall at 17:50 local time (0950 UTC), with winds of about 90 miles per hour (140 km/h).[100] In that province and in neighboring Zhejiang Province, 360,000 residents left coastal and low-lying homes to escape the storm.[99] Schools and many businesses remained closed, and the storm was expected to travel northwest.[100] Early on July 19, the JTWC issued its final advisory on Kalmaegi and downgraded it to a tropical depression. However, the JMA continued to issue advisories and maintained Kalmaegi a tropical storm as it moved to Yellow Sea. Late the next day, the JMA downgraded Kalmaegi to a Remnant Low (Extratropical cyclone) as it moved in land over North Korea.
On July 23 the Japan Meteorological Agency (JMA) started to issue WWJP25 warnings on a minor Tropical Depression which was located to the east of the Philippines.[101] Early the next morning PAGASA named the depression as Igme.[102] The Joint Typhoon Warning Center (JTWC) then initiated issuing advisories on the Tropical Depression designating it as Tropical Depression 09W.[103] Later that day the JMA began to issue full advisories on the tropical depression[23] whilst the JTWC upgraded the depression to tropical storm status.[104] The JMA then designated it as Tropical Storm Fung-wong on July 25.[23]
Fung-wong then carried on intensifying and during the morning off July 26 Fung-wong became a severe tropical storm. Later that day both the JTWC and PAGASA upgraded Fung-wong to Typhoon status.[23][105][106] However the JMA did not upgrade Fung-wong to Typhoon Status until early the next morning. Late on July 27 Fung-wong reached its peak wind speeds of 95 kn (109 mph; 176 km/h) which is equivalent to a strong category two Typhoon on the Saffir–Simpson hurricane scale. Later that day Fung-wong made landfall on Taiwan near the border of Hualien County and Taitung County as a Typhoon. PAGASA then released their final advisory on Fung-wong as it had moved out of PAGASA's area of responsibility.
Early on July 28 Fung-wong it then emerged into the Taiwan Strait from Changhua County early the next morning by this time however Fung-wong had weakened into a Severe Tropical Storm whilst the JTWC had downgraded Fung-wong to a Tropical Storm. Fung-wong then made its second landfall later that day over mainland China. The Joint Typhoon Warning Center then released its last warning on Tropical Storm Fung-wong. However the JMA continued to issue advisories on Fung-wong weakening Fung-wong into a tropical storm on July 29. The JMA then terminated issuing full advisories later that day as Fung-wong weakened into a Tropical Depression, However the JMA continued to monitor the Depression within their WWJP25 warnings until later the next day when they issued their last warning on Fung-wong.[citation needed]
On August 3 at 1500 UTC, PAGASA identified a Tropical Disturbance located to the north of Luzon island in the Philippines and designated it as Tropical Depression Julian.[107] Later that day the Japan Meteorological Agency (JMA) designated Julian as a minor Tropical Depression and initiated advisories on the Tropical Depression.[108]
Early the next day the JMA started to issue full advisories on the Tropical Depression with the Joint Typhoon Warning Center (JTWC) starting to issue warnings on the Tropical Depression with the JTWC designating it as Tropical Depression 10W.[109] Furthermore, later that day both PAGASA and the JTWC upgraded the Tropical Depression to a Tropical Storm.[110][111] On August 5 RSMC Tokyo upgraded the depression to a Tropical Storm and named it Kammuri.[23] PAGASA then released their last advisory on Tropical Storm Kammuri (Julian) as it moved out of PAGASA's Area of responsibility and headed towards Mainland China.[112] The Hong Kong Observatory then upgraded Kammuri to a Severe Tropical Storm, with the JMA upgrading it to a severe tropical storm early the next morning.[113][23]
However, Kammuri started to weaken after making landfall along the south coast of China in the Western Guangdong Province at about 12pm UTC on August 6.[114][115] After Kammuri had made landfall the JMA downgraded Kammuri to a Tropical Storm,[23] whilst the JTWC issued their final advisory later that day on Tropical Storm Kammuri.[116] Early the next day Tropical Storm Kammuri emerged into the Gulf of Tonkin, however later that day Kammuri made landfall again in the Guangxi Province of China. After making landfall Kammuri weakened to a tropical depression as the JMA issued its last advisory on August 7.[23] However the JMA continued to monitor the depression in their WWJP25 warnings until early on August 8.[117]
Late on August 9, the Japan Meteorological Agency (JMA) started to issue full advisories on a Tropical Depression which was located southeast of Japan.[23] Early the next day, the depression intensified into a tropical storm and was named Phanfone by the JMA as it moved northwards.[23] Late on August 10, Phanfone reached its maximum wind speeds of 40 knots (74 km/h; 46 mph) as it was becoming extratropical.[118] Early the next day Phanfone became an extratropical low as the JMA issued their final advisory.[23]
Phanfone was upgraded to a severe tropical storm in post-storm analysis.[119]
The name Phanfone was submitted by Laos and is the name of an animal.
Early on August 12 the JMA identified a weak tropical depression which was located to the northwest of the Ryukyu Islands, and initiated warnings on it.[120] Early the next day the Joint Typhoon Warning Center initiated warnings on the depression designating it as Tropical Depression 11W.[121] Early the next day as Tropical Depression 11W approached Korea the depression reached its maximum wind speeds of 30 knots (56 km/h; 35 mph)[122] However, later that day the JTWC issued its final advisory as due to land interaction the depressions wind speeds would weaken to below warning level.[123] The next day the JMA released their final advisory on the depression.[124][125]
Early on August 13, the Joint Typhoon Warning Center, noted that an area of convection had persisted approximately 370 nautical miles (690 km) to the southeast of Okinawa, Japan and designated it as a Tropical Disturbance.[126] The JTWC at this time also assessed the disturbances chances of forming into a significant tropical cyclone within 24 hours as fair.[126] This was due to the tropical disturbance having a broad Low Level Circulation Center however the strongest winds were displaced on the eastern side of the disturbance.[126] Early the next morning the JTWC reassessed the disturbances chances of forming into a significant tropical cyclone within 24 hours as good and issued a Tropical Cyclone Formation Alert on the developing disturbance.[127] This was because the Low Level Circulation Center had become well defined.[127]
Later on August 14, the Japan Meteorological Agency designated the tropical disturbance as a minor tropical depression whilst the JTWC also upgraded the disturbance and designated it as Tropical Depression 12W.[128][129] Early the next day the JMA designated the depression as a full tropical depression, whilst the JTWC upgraded the depression to a tropical storm.[23][130] Later that day the JMA upgraded the depression to a tropical storm, and assigned the name Vongfong to the storm.[23] The Joint Typhoon Warning Center then reported that Vongfong had reached its peak winds of 50 knots (58 mph; 93 km/h)1-Min) whilst it was located approximately 390 nautical miles (720 km) to the southwest of Tokyo, Japan.[131] The JMA also then reported that it Vongfong had reached its operational peak winds of 40 knots (46 mph; 74 km/h) 10-Min) however this was later revised in its best track when the JMA upgraded Vongfong peak winds to 50 knots (58 mph; 93 km/h) 10-Min).[23] Later on August 15, the JTWC reported that Vongfong had started to weaken from its peak.[132] During the next day Vongfong carried on weakening. The JTWC then issued its final warning on Vongfong later that day as it had begun its extratropical transition.[133] whilst the JMA kept issuing warnings on Vongfong until early on August 17 when they downgraded it to an extratropical low.[23] The extratropical low of Vongfong then crossed the International Date Line and moved out of the JMA's area of responsibility and moved into the Central Pacific Hurricane Center's area of responsibility but they did not issue any warnings on Vongfong as it was extratropical.[23]
As Vongfong brushed by Japan, heavy rains triggered flood which killed one person. A total of 523 homes and 39 hectares (96.3 acres) were damaged by the storm and 15,520 people were left without power. The storm also damaged 139 roads and caused 54 landslides.[134]
On August 17 the Joint Typhoon Warning Center identified a tropical depression located to the east of the Philippines and designated it as 13W.[135] Later that day both the JMA and PAGASA identified the tropical depression and started to issue full advisories on the depression with PAGASA naming the depression Karen. Also later that day the JTWC upgraded Karen to a Tropical Storm.[136][137][138]
The next day, both PAGASA and the JMA upgraded the depression to a Tropical Storm with RSMC Tokyo naming it as Nuri.[139][23] It then intensified rather quickly with the JMA designating it as a Severe Tropical Storm[23] with the JMA, PAGASA, and the JTWC upgrading Nuri to a Typhoon later that day.[140][23][141] Late on August 19 Typhoon Nuri made landfall on the Philippines and then over the next day moved across northern Luzon causing 12 deaths and 461.3 million PHP in damage.[142] that day Nuri entered the Babuyan Channel early the next day and started to move northwestwards towards Hong Kong and China. On August 21 PAGASA then issued its final advisory on Nuri as it was moving out of PAGASA's Area of Responsibility.[143] The JMA then downgraded Nuri to a Severe tropical storm with the JTWC also downgrading Nuri to a Tropical Storm later that day as it was approaching Hong Kong. However, the JMA did not downgrade Nuri to a tropical storm until the next morning after Nuri had made a rare direct hit on Hong Kong. The JTWC then issued its final advisory later on tropical storm Nuri and the JMA then downgraded Nuri to a weak tropical depression early the next day and issued its last full advisory on Nuri as it was just moving into the Chinese mainland.
On August 24, a tropical disturbance formed to the east of Luzon in the Philippines.[144] Early the next day PAGASA designated it as Tropical Depression Lawin.[145] However, the JMA did not designate it as a Minor Tropical depression until early on August 26, with the JTWC issuing a Tropical Cyclone Formation Alert at the same time.[146][147] PAGASA then hoisted Public storm Signal number 1 for parts of Luzon which meant that wind speeds of 30–60 km/h were expected within 36 hours in the warning areas.[148] Later that day both the JMA and the JTWC, started to issue full advisories on the tropical depression, with the JTWC designating it as Tropical Depression 14W.[23][149] Early the next day the JTWC upgraded the tropical depression to a tropical storm,[150] Although neither the JMA nor PAGASA upgraded the depression to a tropical storm at this time (or at any time during Lawin's existence),[151][23] the JTWC then weakened the cyclone back into a tropical depression within their next advisory.[152] The JMA then terminated issuing full advisories later that day as it was no longer expected to develop into a tropical storm.[153] On August 28 the JTWC issued its final advisory on the Tropical depression followed by the JMA and PAGASA later that day.[154][155][156] There were no reported casualties from Tropical Depression 14W (Lawin).[157]
On September 8 the JMA and PAGASA started to issue advisories on a tropical depression which was located to the north of Manila with PAGASA designating it as Tropical Depression Marce. During that afternoon the JTWC designated the depression as Tropical Depression 15W. Later that day the depression intensified into a Tropical Storm as was named Sinlaku by the JMA. During the next day Sinlaku firstly rapidly intensified into a Severe Tropical Storm and then into a Typhoon. On September 10 Sinlaku reached its peak 1 minute sustained winds of 125 knots (145 mph). During September 11 Sinlaku, started to weaken as it went under an eyewall replacement cycle. On September 13 Sinlaku made landfall on Taiwan with winds of 90 knots (170 km/h) which made Sinlaku a category two typhoon. As Sinlaku moved through Taiwan Sinlaku turned to the Northeast and moved back into the South China Sea and started moving towards Japan. The next day as Sinlaku moved towards Japan it weakened into a Severe Tropical Storm and exited PAGASA's area of responsibility whilst the JTWC did not downgrade Sinlaku to a tropical storm until late on September 15. By then they were followed by the JMA which downgraded Sinlaku to a tropical storm early the next day. On September 16 the JTWC reported that Sinlaku had restrengthened into a Typhoon whilst the JMA reported that Sinlaku had strengthened into a Severe Tropical Storm. However, the JTWC Quickly downgraded Sinlaku back down into a Tropical Storm whilst the JMA kept Sinlaku at Severe tropical Storm strength. The next day the JTWC reported that Sinlaku had intensified into a typhoon for a third time however later that day the JTWC downgraded Sinlaku to Tropical Storm. On September 17 the JTWC issued its final advisory on Sinlaku as it became extratropical. However, the JMA kept issuing advisories on Sinlaku until early on September 21 when it became an extratropical low.
Late on September 8, a tropical disturbance formed to the southeast of Japan. It then formed into a tropical depression during the next afternoon, with the JMA designating it as a Minor Tropical Depression with wind speeds of 25 knots (46 km/h).[158] However the JTWC did not designate the depression as 16W until the morning of September 10. At that time the JTWC reported the depression had intensified into a Tropical Storm.[159] However, later that day the JTWC lowered the storm back down to a Depression[160] and then re-upgraded the Depression to a tropical storm.[161] However early the next day the storm was downgraded by the JTWC for the last time as it had started its extratropical transition.[162] Later that day as the depression raced into the Baroclinic Zone the JTWC issued its final advisory on Tropical storm 16W.[163][164]
On September 13 the Japan Meteorological Agency started issuing advisories on a tropical depression located to the east of Japan and designated it as a minor tropical depression with wind speeds of 25 knots (46 km/h).[165] The following morning the Joint Typhoon Warning Center assigned the number 17W to the depression.[166] However, as it had already begun its extra tropical transition, this was the only JTWC warning issued on the system.[166][167]
On September 14 a tropical disturbance formed to the northeast of Guam. Over the next few days it slowly developed, with the JMA designating it as a minor tropical depression on September 17. Later that day the Joint Typhoon Warning Center (JTWC) then issued a Tropical Cyclone Formation Alert on the developing tropical depression. Late the next day the JTWC designated the depression as 18W as it began to issue advisories on the depression. Early on September 19 the JMA began to issue full advisories on the depression as it moved into PAGASA's Area of Responsibility and was named Nina by PAGASA. Later that day both the JMA & the JTWC upgraded the depression to a tropical storm. The JMA named the storm as Hagupit, and assigned the international number of 0814. Early the next day Hagupit intensified into a severe tropical storm, and a category 3 typhoon later that day. It reached maximum intensity with 140 mph (230 km/h) winds on September 23, and made landfall at that strength the next day. It then dissipated over land, thus late on September 24 JTWC issued its final advisory on the system followed by JMA early the next day.
Forming south of Guam on September 22. JTWC issued a TCFA and upgraded the low-pressure area to a tropical depression on the next day.[168][169] Both JTWC and JMA upgraded the system to a tropical storm named Jangmi on September 24, as well as it entered the Philippine Area of Responsibility, earning the name Ofel from the PAGASA.[170] On September 25, Jangmi intensified into a typhoon for its developing eye.[171] On September 26, Jangmi formed an cirrus-filled and ambiguous eye, as the typhoon gradually intensified owing to strong radial outflow.[172]
On September 27, JTWC upgraded Jangmi to a super typhoon with a round eye; at noon, the typhoon attained peak intensity by the ten-minute maximum sustained winds reaching 115 knots (213 km/h; 132 mph) and the atmospheric pressure decreasing to 905 hPa (26.7 inHg).[173] On September 28, after JTWC downgraded Jangmi to a typhoon, it made landfall over Yilan, Taiwan at 15:40 TST (07:40 UTC). Jangmi weakened significantly by the mountainous terrain of Taiwan after landfall, and it arrived at the Taiwan Strait from Taoyuan County (now Taoyuan City) at 04:20 TST on September 29 (20:20 UTC on September 28).[174][175]
On September 29, both JMA and JTWC downgraded Jangmi to a tropical storm in the East China Sea.[176] On September 30, Jangmi underwent extratropical transition and became fully extratropical near the Ōsumi Islands on the next day.[177] It ultimately dissipated near Iwo Jima on October 5.
On September 25 a tropical disturbance formed to the south of China, in the Gulf of Tonkin. Over the next few days it gradually intensified and late on September 27 the JMA designated it as a tropical depression. Early the next day the JTWC issued a Tropical Cyclone Formation Alert on the developing depression and then later that day, designated the depression as Tropical Depression 20W. Early on September 28 the JMA reported that the depression had intensified into a tropical storm and named it as Mekkhala. Later that day the JTWC upgraded Mekkhala to a Tropical Storm. However, on the 30th it began to move inland and thus, early that day, JTWC issued its final advisory on Mekkhala as it is expected to dissipate within a short time. Later that day, the JMA downgraded the storm to a tropical depression and issued the final advisory.
At least 21 people have been killed due to Tropical Storm Mekkhala.[178] Damages from the storm totaled to $6.6 million (USD)[179]
On September 27 a tropical disturbance formed in the Philippine Sea to the east of Mindanao, in the Philippines. During the next day the JTWC issued a TCFA on the tropical disturbance. Early on September 29 the JMA designated the disturbance as a tropical depression. Later that day both PAGASA and the JTWC designated the disturbance as a tropical depression, with PAGASA naming the depression as Pablo whilst the JTWC designated it as Tropical Depression 21W. The JTWC upgraded the depression to a tropical storm early in the afternoon. The JMA followed shortly after and upgraded the system to Tropical Storm Higos early on September 30. Higos tracked towards the northwest and made landfall in the eastern Philippines (on Samar island) on October 1. Higos tracked over the Philippines as a tropical storm (but PAGASA downgraded it as a tropical depression) for most of the day before moving out over open waters. Once out over water, the JTWC downgraded Higos to a tropical depression, however, the JMA kept it as a tropical storm. As Higos neared landfall, it suddenly relocated, paralleling the northeastern coast of Hainan, China. The storm later made landfall on October 4 around 2 a.m. (CST) on the northern coastline of the island. JMA then issued its final advisory as Higos weakened to a tropical depression. The JTWC followed 12 hours later.
On October 13 the Japan Meteorological Agency designated a low-pressure area in the Gulf of Tonkin as a minor tropical depression with wind speeds of 25 knots (46 km/h).[180] The China Meteorological Administration and Hong Kong Observatory both declared this system a tropical depression that day as it moved slowly towards northern Vietnam. On October 14, the JMA notes that the depression has strengthened to 30 knots (56 km/h) with little northwestward movement.[181] Joint Typhoon Warning Center begun issuing warnings late morning as a tropical depression and in the evening upgraded it to a tropical storm forecasting it to strengthen even further before making its landfall over northern Vietnam. The system didn't gain anymore strength in the Gulf of Tonkin and on October 15 made landfall over northern Vietnam. The Joint Typhoon Warning Center issued its final advisory on this system expecting it to dissipate near Laos by October 16.
On October 18 an area of low pressure well to the southeast of Japan quickly strengthened to become a Tropical Storm, and the JMA named it Bavi. Bavi strengthened to gain 50 mph (80 km/h) winds, but transitioned into an extra-tropical cyclone on 21 October, while still well to the east of Japan.
On November 5, a tropical disturbance formed in the Philippine Sea to the northeast of Zamboanga, in the Philippines. Later that day the JTWC assessed the disturbance chances of forming into a Significant Tropical cyclone within 24 hours as poor. Early the next day PAGASA designated the disturbance as a Tropical Depression and named it as Quinta, whilst the JTWC still monitored it as a disturbance. Later that day the JTWC upgraded the disturbances chances of forming into a significant tropical cyclone to Good and issued a Tropical Cyclone Formation Alert on the disturbance and then designated the disturbance as Tropical Depression 24W as they issued their first advisory on the Depression. On November 12, PAGASA issued their final warning as it transform into a low-pressure area. PAGASA renamed the system as Siony on November 12 as it redeveloped. Later that day, they issued their final advisory again as it moved out of their area of responsibility.
Early on November 7 a Tropical disturbance formed about 475 nm to the east of Zamboanga in the Philippines.[182] Animated multi-spectral imagery at this time showed that the disturbance had disorganized convection which was located near to a developing low level circulation center and was located within a favorable upper-level environment for development.[182] An anticyclone was providing vertical wind-sheer however the disturbance was already interacting with land as it was rapidly approaching Mindanao.[182] Later that day after it had moved through parts of Mindanao it was named as Tropical Depression Rolly by PAGASA as they placed several parts of Mindanao and Visayas under public storm signal number one.[183] All signals were then canceled the next morning as PAGASA released their final advisory on Rolly as it had weakened into an area of low pressure over Palawan.[184] The JTWC then declared that the low-pressure area had dissipated later that morning.[185] Rough seas produced by the depression capsized a vessel carrying eleven people. The Philippine Coast Guard quickly responded to the incident and rescued all crew members.[186]
On November 14, the JMA reported that tropical depression formed 490 km (300 mi) to the southeast of Iwo To,[47] despite the JTWC noting the tropical cyclone formation was unlikely within the next 24 hours[187] due to lack of deep convection.[188] Later that day, deep convection began to persist near the center, indicating the storm developed a fully warm tropical core.[189][190] Despite increased vertical wind shear, the JTWC issued a Tropical Cyclone Formation Alert on the system.[190] During that evening, the JMA upgraded the depression to a tropical storm while the JTWC designated Haishen as a tropical depression.[23][191] Early on November 16, Haishen attained its peak intensity of 75 km/h (45 mph).[47][192] Traveling along the north portion of a subtropical ridge to the southeast of the system, dry air began to take toll on the system.[192] The JTWC then issued their final warning later that day, as Haishen rapidly transitioned into an extratropical cyclone.[193] The JMA followed suit 24 hours later.[47][187] The extratropical low of Haishen accelerated towards the International Date Line,[187][194] where it briefly reintensified.[187]
On November 12 a tropical disturbance formed to the east of Mindanao in the Philippines. Later that day the JTWC assessed the disturbances' chances of forming into a significant tropical cyclone within 24 hours as Poor. The next day as it moved towards Mindanao, PAGASA designated it as Tropical Depression Tonyo. Early on November 16, the JTWC declared the system Tropical Depression 26W. On November 16, PAGASA issued their final warning as the Depression moved to South China Sea. On November 17 the storm dissipated over Cambodia and both the JMA and JTWC issued their final warnings later that day.
A landslide triggered by Noul killed a schoolteacher as she was heading home in Quảng Ngãi Province. At least 50 rescue workers searched for her through the debris before finding her body several days later. At least 20,000 people were in need of emergency assistance in the form of food, shelter, and water following the storm. Several other people were killed by landslides and flooding.[195] In all, Tropical Storm Noul killed 21 people in southern Vietnam.[196] During the storm, more than 2,000 people were isolated by floodwaters.[197] A total of 200 homes were destroyed, another 13,500 were damaged[198] 8,879 hectares of crops were destroyed and 60 km (37 mi) of roads were submerged.[199] Damages from the storm were estimated at VND143 billion (US$8.4 million).[198] Offshore, a total of 115 boats sank due to the storm.[199]
A small circulation formed over in a developing extratropical cyclone east of Japan on December 2. This type of formation is really rare, as the circulation moved east away from the developing cyclone and moved south on December 5. Dolphin was formerly an area of convection that had formed on the tail end of a shearline on December 7.[200] On December 8, the storm gained more tropical characteristics, thus JMA defined it as a tropical depression. The storm then moved westward during the following days. On December 10, the JTWC upgraded the storm to Tropical Depression 27W when it was east of Guam. On December 12, 27W was upgraded to Tropical Storm Dolphin by the JMA. The name Dolphin was submitted by Hong Kong. Later that day, Dolphin entered the Philippine Area of Responsibility and named Ulysses. On December 15, the JTWC upgraded Dolphin to a typhoon. The JMA also upgraded Dolphin to a typhoon several hours later. On December 16, the JMA downgraded Dolphin to a severe tropical storm. Both agencies issued their final advisories on Dolphin on December 18 as it transitioned into an extratropical cyclone.
Many weak tropical depressions are left unmonitored, or left unnamed.
A tropical depression existed in the central Pacific Ocean from January 22–23. It didn't affect any landmasses.
Another tropical depression existed from March 26–27, affecting Philippines.
On May 27, an unmonitored tropical depression affected the Philippines. It dissipated the next day.
Another tropical depression affected Japan and Ryukyu Islands on June 6.
2 more unmonitored tropical depressions existed from July 6–9 and July 13–15. It didn't affect any landmasses.
2 more unmonitored tropical depressions formed from August 10–12 and August 11–15. The first depression affected China and the latter affected Japan and South Korea.
Shortly after crossing the dateline, the remnants of Tropical Storm Kika entered the western Pacific basin and regenerated into a tropical depression. The depression continued to move towards the west-southwest before dissipating on August 16.[201]
A tropical depression was left unmonitored on November 11–12. It stayed well from land.
The last unmonitored tropical depression existed on December 2. It stayed well from land as it dissipated.
Within the North-western Pacific Ocean, both the Japan Meteorological Agency (JMA) and the Philippine Atmospheric, Geophysical and Astronomical Services Administration assign names to tropical cyclones that develop in the Western Pacific, which can result in a tropical cyclone having two names.[202] The Japan Meteorological Agency's RSMC Tokyo — Typhoon Center assigns international names to tropical cyclones on behalf of the World Meteorological Organization's Typhoon Committee, should they be judged to have 10-minute sustained windspeeds of 65 km/h (40 mph).[203] While the Philippine Atmospheric, Geophysical and Astronomical Services Administration assigns names to tropical cyclones which move into or form as a tropical depression in their area of responsibility located between 135°E and 115°E and between 5°N-25°N even if the cyclone has had an international name assigned to it.[202] The names of significant tropical cyclones are retired, by both PAGASA and the Typhoon Committee.[203] Should the list of names for the Philippine region be exhausted then names will be taken from an auxiliary list of which the first ten are published each season. Unused names are marked in gray.
During the season 22 named tropical cyclones developed in the Western Pacific and were named by the Japan Meteorological Agency, when it was determined that they had become tropical storms. These names were contributed to a list of a 140 names submitted by the fourteen members nations and territories of the ESCAP/WMO Typhoon Committee. The names Matmo, Nuri, Noul and Dolphin were used for the first time as it was replaced from Chataan, Rusa, Pongsona and Yanyan.
| Neoguri | Rammasun | Matmo | Halong | Nakri | Fengshen | Kalmaegi | Fung-wong | Kammuri | Phanfone | Vongfong |
| Nuri | Sinlaku | Hagupit | Jangmi | Mekkhala | Higos | Bavi | Maysak | Haishen | Noul | Dolphin |
| Ambo | Butchoy | Cosme | Dindo | Enteng |
| Frank | Gener | Helen | Igme | Julian |
| Karen | Lawin | Marce | Nina | Ofel |
| Pablo | Quinta | Rolly | Siony | Tonyo |
| Ulysses | Vicky (unused) | Warren (unused) | Yoyong (unused) | Zosimo (unused) |
| Auxiliary list | ||||
|---|---|---|---|---|
| Alakdan (unused) | Baldo (unused) | Clara (unused) | Dencio (unused) | Estong (unused) |
| Felipe (unused) | Gardo (unused) | Heling (unused) | Ismael (unused) | Julio (unused) |
The Philippine Atmospheric, Geophysical and Astronomical Services Administration uses its own naming scheme for tropical cyclones in their area of responsibility. PAGASA assigns names to tropical depressions that form within their area of responsibility and any tropical cyclone that might move into their area of responsibility. Should the list of names for a given year prove to be insufficient, names are taken from an auxiliary list, the first 10 of which are published each year before the season starts. The names not retired from this list will be used again in the 2012 season. This is the same list used in the 2004 season, except for Ulysses, Vicky and Warren, which replaced Unding, Violeta and Winnie respectively. A storm was named Ulysses for the first time. Names that were not assigned are marked in gray.[204]
During this season, PAGASA announced that they were going to retire the names Cosme and Frank due to the extensive damage and loss of life that they caused. In June 2012 the names Carina and Ferdie were chosen to replace these names for future seasons. No international names were retired following the 2008 season.
This table will list all the storms that developed in the northwestern Pacific Ocean west of the International Date Line and north of the equator during 2008. It will include their intensity, duration, name, areas affected, deaths, and damage totals. Classification and intensity values will be based on estimations conducted by the JMA. All damage figures will be in 2008 USD. Damages and deaths from a storm will include when the storm was a precursor wave or an extra tropical low.
| Name | Dates | Peak intensity | Areas affected | Damage (USD) |
Deaths | Refs | ||
|---|---|---|---|---|---|---|---|---|
| Category | Wind speed | Pressure | ||||||
| 01W | January 13–18 | Tropical depression | 55 km/h (34 mph) | 1,004 hPa (29.65 inHg) | Philippines, Malaysia | None | None | |
| TD | January 22–23 | Tropical depression | Not specified | 1,006 hPa (29.71 inHg) | None | None | None | |
| TD | March 26–27 | Tropical depression | Not specified | 1,006 hPa (29.71 inHg) | Philippines | None | None | |
| Neoguri (Ambo) | April 13–20 | Strong typhoon | 150 km/h (93 mph) | 960 hPa (28.35 inHg) | Philippines, China | $65 million | 26 | |
| Rammasun (Butchoy) | May 7–13 | Violent typhoon | 195 km/h (121 mph) | 915 hPa (27.02 inHg) | Philippines, Japan | $9.6 million | 4 | |
| Matmo (Dindo) | May 14–17 | Severe tropical storm | 95 km/h (59 mph) | 992 hPa (29.29 inHg) | Philippines, Japan | None | None | |
| Halong (Cosme) | May 14–20 | Severe tropical storm | 110 km/h (68 mph) | 970 hPa (28.64 inHg) | Philippines, Japan | $100 million | 61 | |
| Nakri (Enteng) | May 26 – June 3 | Very strong typhoon | 185 km/h (115 mph) | 930 hPa (27.46 inHg) | Mariana Islands, Japan | None | None | |
| TD | May 27–28 | Tropical depression | Not specified | 1,006 hPa (29.71 inHg) | Philippines | None | None | |
| TD | June 6 | Tropical depression | Not specified | 1,006 hPa (29.71 inHg) | Taiwan, Ryukyu Islands | None | None | |
| Fengshen (Frank) | June 17–25 | Very strong typhoon | 165 km/h (103 mph) | 945 hPa (27.91 inHg) | Philippines, China | $430 million | 1,371 | |
| Gener | July 4–8 | Tropical depression | 55 km/h (34 mph) | 1,000 hPa (29.53 inHg) | China | None | None | |
| TD | July 6–9 | Tropical depression | Not specified | 1,004 hPa (29.65 inHg) | None | None | None | |
| TD | July 13–15 | Tropical depression | Not specified | 1,006 hPa (29.71 inHg) | None | None | None | |
| Kalmaegi (Helen) | July 13–20 | Strong typhoon | 120 km/h (75 mph) | 970 hPa (28.64 inHg) | Philippines, Taiwan, China, Korea, Japan | $332 million | 25 | |
| Fung-wong (Igme) | July 23–30 | Strong typhoon | 140 km/h (87 mph) | 960 hPa (28.35 inHg) | Taiwan, China | $541 million | 23 | |
| Kammuri (Julian) | July 23–30 | Severe tropical storm | 95 km/h (59 mph) | 975 hPa (28.79 inHg) | Philippines, China, Hong Kong, Taiwan, Vietnam | $200 million | 204 | |
| Phanfone | August 9–11 | Severe tropical storm | 95 km/h (59 mph) | 996 hPa (29.41 inHg) | None | None | None | |
| TD | August 10–12 | Tropical depression | Not specified | 998 hPa (29.47 inHg) | China | None | None | |
| TD | August 11–15 | Tropical depression | Not specified | 1,000 hPa (29.53 inHg) | Japan, South Korea | None | None | |
| 11W | August 12–15 | Tropical depression | 55 km/h (34 mph) | 998 hPa (29.47 inHg) | Japan, South Korea | Minor | None | |
| Vongfong | August 14–17 | Severe tropical storm | 95 km/h (59 mph) | 990 hPa (29.23 inHg) | Japan | Minor | 1 | |
| Nuri (Karen) | August 17–23 | Strong typhoon | 140 km/h (87 mph) | 955 hPa (28.20 inHg) | Caroline Islands, Philippines, China | $85 million | 20 | |
| 14W (Lawin) | August 26–28 | Tropical depression | 55 km/h (34 mph) | 1,002 hPa (29.59 inHg) | Philippines, Taiwan | None | None | |
| Sinlaku (Marce) | September 8–21 | Very strong typhoon | 185 km/h (115 mph) | 935 hPa (27.61 inHg) | Philippines, Taiwan, China, Japan | $1.1 billion | 24 | |
| 16W | September 9–11 | Tropical depression | 55 km/h (34 mph) | 1,002 hPa (29.59 inHg) | Japan | None | None | |
| 17W | September 13–14 | Tropical depression | 45 km/h (28 mph) | 1,010 hPa (29.83 inHg) | None | None | None | |
| Hagupit (Nina) | September 18–25 | Very strong typhoon | 165 km/h (103 mph) | 935 hPa (27.61 inHg) | Philippines, Taiwan, China, Vietnam | $3 billion | 67 | |
| Jangmi (Ofel) | September 23 – October 1 | Violent typhoon | 215 km/h (134 mph) | 905 hPa (26.72 inHg) | Taiwan, Japan | $87.7 million | 8 | |
| Mekkhala | September 27–30 | Tropical storm | 85 km/h (53 mph) | 990 hPa (29.23 inHg) | Vietnam, Laos, Thailand | $6.6 million | 16 | |
| Higos (Pablo) | September 29 – October 6 | Tropical storm | 65 km/h (40 mph) | 998 hPa (29.47 inHg) | Philippines, Taiwan, China | $6.5 million | Unknown | |
| 22W | October 12–15 | Tropical depression | 55 km/h (34 mph) | 1,006 hPa (29.71 inHg) | China, Vietnam | Moderate | None | |
| Bavi | October 18–20 | Tropical storm | 85 km/h (53 mph) | 992 hPa (29.29 inHg) | None | None | None | |
| Maysak (Quinta-Siony) | November 6–14 | Severe tropical storm | 95 km/h (59 mph) | 985 hPa (29.09 inHg) | Philippines, Vietnam | Minor | 30 | |
| Rolly | November 7–9 | Tropical depression | 55 km/h (34 mph) | 1,006 hPa (29.71 inHg) | Philippines | None | None | |
| TD | November 11–12 | Tropical depression | Not specified | 1,004 hPa (29.65 inHg) | None | Minor | None | |
| Haishen | November 14–17 | Tropical storm} | 75 km/h (47 mph) | 1,004 hPa (29.65 inHg) | None | None | None | |
| Noul (Tonyo) | November 14–17 | Tropical storm | 75 km/h (47 mph) | 994 hPa (29.35 inHg) | Philippines, Vietnam, Cambodia | $8.4 million | 21 | |
| TD | December 2 | Tropical depression | Not specified | 1,006 hPa (29.71 inHg) | None | Minor | None | |
| Dolphin (Ulysses) | December 11–18 | Strong typhoon | 120 km/h (75 mph) | 970 hPa (28.64 inHg) | Caroline Islands, Mariana Islands, Philippines | $9,000 | 47 | |
| Season aggregates | ||||||||
| 41 systems | January 13 – December 18 | 215 km/h (134 mph) | 905 hPa (26.72 inHg) | $5.97 billion | 1,936 | |||
Seamless Wikipedia browsing. On steroids.
Every time you click a link to Wikipedia, Wiktionary or Wikiquote in your browser's search results, it will show the modern Wikiwand interface.
Wikiwand extension is a five stars, simple, with minimum permission required to keep your browsing private, safe and transparent.
_2008_track.png)
