2007 Pacific typhoon season

Since the 2000 typhoon season, the Laboratory for Atmospheric Research (LAR), of the City University of Hong Kong have issued forecasts of activity for each upcoming typhoon season.[7] Forecasts were released in April and June predicting how many tropical cyclones, tropical storms, and typhoons there will be during the season.[7] During the season, the LAR is predicting a below average season with fewer than usual tropical cyclones. In its April forecast, the LAR predicted that 28 tropical cyclones, 25 tropical storms, and 14 typhoons before in its June forecast predicting 27 tropical cyclones, 24 tropical storms and 14 typhoons.[7][8]

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 2007, forecasts were released in March, May, June, July and August predicting how many tropical cyclones, tropical storms, typhoons and intense typhoons there will be during a season.[note 1][9] In its March forecast, TSR predicted that the season would be about 15% below average with 24 tropical storms, 15 typhoons and 7 intense typhoons.[1] In its May forecast, TSR predicted that the season would now be near normal with 27 tropical storms, 17 typhoons and 8 intense typhoons forming during the season.[2] Within their June July and August forecasts, TSR forecasted the season would be near normal with 27 tropical storms and 17 typhoons forming.[3][4][5]

The Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA), reported on January 27, 2007, that they were expecting 15–19 tropical cyclones to move through their area of responsibility, during the upcoming typhoon season.[6] They also predicted that due to the weak El Niño event that was occurring the first tropical cyclone wouldn't move through their area of responsibility until May.[6]

Typhoon (JMA)
Category 3 typhoon (SSHWS)
Duration	March 30 – April 6
Peak intensity	150 km/h (90 mph) (10-min)  960 hPa (mbar)

On March 26, the JTWC identified a broad area of low pressure in the Western North Pacific. It moved west-northwestward over the next few days, slowly gaining organization. According to the Japan Meteorological Agency, it became a tropical depression on March 30. The next day, the Joint Typhoon Warning Center issued a Tropical Cyclone Formation Alert due to an increased consolidation of the low-level circulation of the system. The JTWC issued its first warning on Tropical Depression 01W late that evening local time.[10] As it continued to strengthen, the JTWC upgraded it to a tropical storm,[11] the first of the season. The JMA followed suit, and named the system Kong-rey.[12] The name was submitted by Cambodia, and refers to a character in a Khmer legend, which is also the name of a mountain.[13]

Kong-rey continued to organize and intensified into a severe tropical storm early the next morning local time.[14] The JTWC then upgraded it to a typhoon on April 2.[15] As the system took a more poleward track towards the Northern Mariana Islands, the National Weather Service office in Guam noted that damaging winds were now not expected on the island. Elsewhere in the Marianas, preparations were made and flights were cancelled in anticipation of the typhoon. Kong-rey passed through the islands in the early hours of the morning on April 3 local time. The JMA upgraded Kong-rey to a typhoon later that afternoon,[16] as it developed an eye. It strengthened slightly further before encountering wind shear and colder sea surface temperatures and was downgraded back to a severe tropical storm on April 4. As Kong-rey accelerated towards the northeast, it began undergoing extratropical transition early on April 5 and the JTWC issued its final warning.[17] The JMA issued its final warning on the morning of April 6 after it had completed extratropical transition. No casualties or major damage was reported.

Typhoon (JMA)
Category 4 super typhoon (SSHWS)
Duration	May 17 – May 23
Peak intensity	175 km/h (110 mph) (10-min)  935 hPa (mbar)

On May 15, a significant consolidation of organisation in a tropical disturbance located south-southeast of Guam led to Dvorak technique numbers equating to a windspeed of 45 knots (83 km/h) from the Air Force Weather Agency. Later that day, the Japan Meteorological Agency designated the system a tropical depression, and the Joint Typhoon Warning Center issued a Tropical Cyclone Formation Alert.[18] The next day, the JMA began issuing full advisories on the tropical depression. It developed slowly, resulting in a reissuance of the TCFA later that day. In this second TCFA, the JTWC noted "an increasingly well-defined" low-level circulation centre.[19] The JTWC upgraded the system to Tropical Depression 02W at 1200 UTC, based on satellite intensity estimates and QuikSCAT.[20] The JMA designated 02W as Tropical Storm Yutu early on May 17, as the system strengthened further. The name 'Yutu' was contributed by China, and refers to a rabbit in a Chinese fable.[13] The JTWC followed suit 3 hours later, upgrading the system to Tropical Storm 02W as it moved quickly westwards, heading for Yap. Tropical storm warnings and watches were put in place for most of the Yap State, but were later cancelled after Yutu passed through quickly.

It then took a northwesterly turn, entered the PAGASA area of responsibility on May 18 as it reached severe tropical storm strength,[21] and was named "Amang". Later that day, the JTWC upgraded it to a typhoon, and identified a "distinct eye feature",[22] and the JMA upgraded the severe tropical storm to a typhoon at 1800 UTC as it continued to intensify. It began to recurve towards Iwo Jima, undergoing rapid intensification,[23] with "enhanced poleward outflow and low vertical wind shear".[24] It reached its peak on the evening of May 20, as a strong Category 4-equivalent typhoon, just short of becoming a super typhoon. Despite moving into cooler waters, its strong poleward outflow helped it to maintain a high intensity, while carrying a 20 nautical mile-wide eye, on the early morning of May 21.[25] It then began to gradually weaken, passing over Okinotorishima and near Iwo Jima that day as it sped off to the northeast. Maximum winds on Iwo Jima occurred around 1500 UTC that day, with 66 kt (122 km/h, 76 mph) sustained gusting to 104 kt (193 km/h, 120 mph), when a minimum central pressure of 976 hPa was recorded.[26] It then started extratropical transition, and the JTWC issued its final warning on the morning of May 22. The JMA issued its last advisory after extratropical transition completed a day later.

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	July 4 – July 5
Peak intensity	65 km/h (40 mph) (10-min)  994 hPa (mbar)

An area of disturbed weather formed in the South China Sea on July 2 and gradually consolidated over the next two days as it moved west-northwestward. A Tropical Cyclone Formation Alert was issued by the Joint Typhoon Warning Center on the morning of July 4, and later that day the disturbance was upgraded straight to a tropical storm just south-east of Hainan Island. It made landfall on the island shortly after. China claimed that a tropical depression formed in the morning on July 2, made landfall in Hainan later that afternoon with maximum sustained winds of 15 m/s (55 km/h, 35 mph)[27] and deepened to 988hPa[28] before making its second landfall. The Japan Meteorological Agency upgraded the tropical depression to Tropical Storm Toraji on the morning of July 5 while it was in the Gulf of Tonkin, after the centre of the storm had emerged back over water. The name Toraji was contributed by North Korea and refers to the broad bellflower (platycodi radix). Toraji made landfall in Vietnam around 1200 UTC later that evening, having not strengthened much while over the Gulf of Tonkin. The JMA never analysed the storm beyond 994 hPa and minimal tropical storm strength. The JTWC issued its last advisory after landfall, and the JMA followed suit shortly after.

Throughout Guangxi Province, an estimated 1.11 million people were affected by Toraji.[29] Heavy rains produced by the storm inundated an estimated 7,500 hectares of farmland and damaged 1,300 homes. The flooding forced about 147,000 people to evacuate to safer locations. Damages from the storm amounted to ¥73.6 million (US$9.7 million).[30] Several small fishing boats sank off the coast of Vietnam, the fate of the crews are unknown.[31] Several other offshore incidents occurred, including a few collisions resulting in a minor oil spill.[32] Throughout northern areas of the country, an average of 155 mm (6.1 in) of rain fell, leading to flooding and landslides. At least 27 homes were damaged and 13 others were destroyed by the storm, leaving hundreds of millions of Vietnamese đồng in losses. A power station at a military base was damaged during the storm, leaving roughly 40 million (VND; US$2,240).[33]

Typhoon (JMA)
Category 4 super typhoon (SSHWS)
Duration	July 9 – July 16
Peak intensity	185 km/h (115 mph) (10-min)  930 hPa (mbar)

The Joint Typhoon Warning Center began to track an area of disturbed weather just north of the equator on July 4. The circulation centre and surrounding convection started to take shape, although the system was in a "marginal upper-level environment" with moderate vertical wind shear.[34][35] Surface pressure drops of less than 0.5 mb (hPa) were observed on July 6, as the system moved westward.[35] Early on July 7, the Japan Meteorological Agency (JMA) listed the system as a weak tropical depression. Hours later, the Joint Typhoon Warning Center (JTWC) issued a Tropical Cyclone Formation Alert, as the system consolidated further with "deep convective banding" and improving upper-level conditions.[36] The JTWC issued its first warning on Tropical Depression 04W later that day,[37] and forecast a gradual intensification, as weak to moderate wind shear and weak poleward outflow balanced the effect of high ocean heat content.[38] The JMA began issuing full tropical cyclone advisories on the tropical depression at the same time.[39] As the depression gained more organisation, it was upgraded to a tropical storm that night by the JTWC.[40] The JMA finally upgraded it to a tropical storm later that evening as the large system consolidated, naming it Man-yi.[41] The name "Man-yi" was contributed by Hong Kong, and is the Chinese name of a strait turned reservoir (the High Island Reservoir). Man-yi continued to organize and became a severe tropical storm on July 9, when downed electricity lines caused widespread power outages on Guam.[42] Tropical storm warnings and typhoon watches were put in place for most of Yap State at some point during the storm. Strong waves from the typhoon capsized a ship 375 miles (604 km) to the northwest of Guam, killing three and leaving six missing.[43] The JTWC upgraded the storm to a typhoon on the afternoon of July 10, based on Dvorak technique satellite intensity estimates of 65 knots (120 km/h) by both the JMA and the JTWC. Early the next day, the system entered the Philippine Area of Responsibility and was named "Bebeng" by PAGASA. At the same time, the JMA upgraded Man-yi to a typhoon.

Moving over warmer waters, Man-yi underwent rapid deepening late on July 11 and early on July 12 as it churned towards Okinawa in Japan. The United States Military upgraded the Tropical Cyclone Condition of Readiness (TCCOR) levels for Kantō, Yokosuka, Sasebo and Okinawa on the afternoon of July 12 as Man-yi neared the islands.[44] Man-yi was upgraded twice to super-typhoon strength over the next day as it passed through the prefecture, with a 1-minute peak of 155 mph (249 km/h). The passage of Man-yi resulted in 37 injuries and widespread power outages in Okinawa.[45] The TCCOR level for Okinawa was downgraded to 1R (recovery) on July 13 while Kantō, Yokosuka and Sasebo's levels were all upgraded in anticipation of the typhoon.[46] Man-yi made brief landfall in Kagoshima Prefecture on Kyūshū early the next day before turning to the east and making brief landfalls in Kōchi Prefecture on Shikoku and in Wakayama Prefecture on Honshū. As it interacted with land and started to undergo extratropical transition, the typhoon weakened and was downgraded to a tropical storm by the JTWC and a severe tropical storm by the JMA. It became extratropical on July 15 according to the JTWC and hence it issued its final advisory. The JMA issued its final advisory two days later.

Typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	July 27 – August 4
Peak intensity	165 km/h (105 mph) (10-min)  945 hPa (mbar)

On July 26, the Joint Typhoon Warning Center identified an area of disturbed weather east of the Mariana Islands. This area moved westward and increased in organization, and the Joint Typhoon Warning Center issued a Tropical Cyclone Formation Alert on the system on July 27.[47] The Japan Meteorological Agency designated the system a tropical depression later that day.[48] The next day, the JMA began issuing advisories on the depression, and the JTWC followed suit, designating it Tropical Depression 05W.[49]

The system quickly strengthened as it approached the Mariana Islands, and the JTWC upgraded it to a tropical storm six hours later.[50] The JMA did so early on July 29, designating the system as Tropical Storm Usagi.[51] The name Usagi was contributed by Japan, and means "rabbit" in Japanese.[13] The National Weather Service office in Guam issued tropical storm warnings for Pagan Island and Agrihan in the Northern Marianas shortly after the system was upgraded.[52]

Usagi passed between Pagan and Agrihan later on July 29,[53] and began to quickly strengthen. The JTWC upgraded it to a typhoon later that day, citing Dvorak technique numbers indicating an estimate of 65 knots (120 km/h, 75 mph) and a developing eye.[54] The system gradually turned toward the northwest, and the JMA upgraded it to a severe tropical storm early on July 30,[55] and then to a typhoon on July 31 as it passed to the south of Iwo Jima.[56] Usagi moved northwest over warm waters, reaching peak intensity on August 1 before weakening due to cooling sea surface temperatures and increasing wind shear as it approached Kyūshū. Usagi made landfall on August 2 near Nobeoka, Miyazaki as a rapidly weakening typhoon, and it was downgraded to a severe tropical storm shortly after. The system continued weakening rapidly as it moved across Kyūshū and Honshū, and the JMA downgraded it to a tropical storm later that day.[57]

The JTWC downgraded the system to a tropical storm late on August 2 and issued its last advisory early on August 3 as it began to undergo extratropical transition. Usagi then made further landfalls on northern Honshū in Aomori Prefecture before becoming fully extratropical on August 4, leading the JMA to stop advisories. Usagi was responsible for 18 injuries in Kyūshū.[58]

Tropical depression (JMA)
Tropical depression (SSHWS)
Duration	August 2 – August 8
Peak intensity	55 km/h (35 mph) (10-min)  994 hPa (mbar)

An area of disturbed weather developed in the South China Sea on July 31. Despite strong wind shear in the area, the system gradually increased in organization as it remained nearly stationary, and the Joint Typhoon Warning Center issued a Tropical Cyclone Formation Alert on the system on August 2.[59] The JTWC classified the system as Tropical Depression 06W shortly after,[60] with the JMA designating it a tropical depression at the same time.[61] Despite strong wind shear in the area, the system slowly intensified as it meandered along the coast of Vietnam, and the JTWC upgraded it to a tropical storm early on August 4.[62] However, later that day, the JTWC downgraded the storm back to a depression due to the loss of most of the convection.[63]

At least 60 people died in Vietnam due to extensive floods.[64] Total rainfall from 06W in Vietnam throughout the course of the storm was over 24 inches (610 mm). Total rainfall in Hainan during the passage of the tropical storm was 9.1 inches (230 mm).[65] In Thailand, the remnants of the storm lead to two casualties and about 272,757,962 Baht ($7.5 million US$) in damage.[66][67]

Typhoon (JMA)
Category 1 typhoon (SSHWS)
Duration	August 4 – August 14
Peak intensity	120 km/h (75 mph) (10-min)  975 hPa (mbar)

A tropical disturbance developed southeast of Chuuk early on July 31. The system moved west-northwestward over the next several days with little change in organization. On August 4, however, organized convection quickly began to redevelop, and the Japan Meteorological Agency began monitoring it as a tropical depression. The system continued to strengthen, and the Joint Typhoon Warning Center issued a Tropical Cyclone Formation Alert on the system early the next day, noting that its environment was "strongly favorable for development".[68] The Japan Meteorological Agency designated the system Tropical Storm Pabuk shortly after.[69] The name "Pabuk" was submitted by Laos, and refers to a large freshwater fish in the Mekong River.[13] The JTWC designated the system Tropical Storm 07W at about the same time, and on August 5 PAGASA named the system Chedeng. As Pabuk continued to move to the northwest, it gained some organisation as it slowly developed outflow.[70] It was upgraded by the JMA to a severe tropical storm on August 6. Moving westwards towards Taiwan, an area of convection south of Pabuk separated and formed its own low-level circulation. Pabuk's upper-level outflow inhibited this new area of convection. Strengthening slightly, Pabuk was upgraded to a typhoon on the morning of August 7. The JTWC downgraded Pabuk to a tropical storm later that day, with the JMA downgrading Pabuk shortly before landfall. It made landfall in southern Taiwan around 1630 UTC according to Taiwan radar and crossed the southern tip of the Hengchun Peninsula in Pingtung County. The JTWC re-upgraded Pabuk to a typhoon at its next advisory, however, citing a small eye at landfall,[71] before downgrading it to a tropical storm again three hours later.[72]

After passing over Taiwan, Pabuk took aim at Hong Kong.[73] The Hong Kong Observatory and Macau's Meteorological and Geophysical Bureau both hoisted strong wind signal 3 on August 9 as the system passed to the south of Hong Kong. The JMA downgraded the storm to a tropical depression later that day and issued its final public advisory, with the JTWC following suit shortly after. The tropical depression then turned back to the east-northeast on August 10,[74] forcing the HKO to re-issue signal 3. The HKO also warned that winds were expected to strengthen further locally, and that the Hong Kong Education Bureau had suspended all classes for the day.[75] The HKO upgraded Pabuk to a tropical storm[76] and subsequently issued the gale or storm warning signal 8 at 2:30 pm HKT (0630 UTC) later that day as Pabuk moved closer to the territory.[77] This was replaced by signal 3 later that night as Pabuk took another turn in direction and headed west inland into Guangdong. Early next morning, Pabuk resumed a northeasterly track, edging once again closer to the Pearl River Delta[78] before it weakened further and HKO cancelled all signals.[79]

At least 11 people were killed in the Philippines by Pabuk.[80]

Tropical storm (JMA)
Tropical depression (SSHWS)
Duration	August 6 – August 9
Peak intensity	65 km/h (40 mph) (10-min)  990 hPa (mbar)

A tropical disturbance developed to the south of the developing Tropical Storm Pabuk on August 5, and was first mentioned by the Joint Typhoon Warning Center in its Significant Tropical Weather Outlook on August 6.[81] The Japan Meteorological Agency designated it a tropical depression later that night.[82] By the next day, although still attached to Pabuk and being inhibited by shearing from an upper-level outflow anticyclone over Pabuk,[83] the JTWC issued a Tropical Cyclone Formation Alert.[84] As Pabuk moved away, the depression gradually strengthened, and the JMA designated it Tropical Storm Wutip early on August 8.[85] The name Wutip was submitted by Macau, and means butterfly.[13] It struggled against land interaction, however, and did not strengthen considerably, remaining poorly organised. The storm quickly weakened, and the JMA issued its last advisory on Wutip early on August 9, downgrading it to a tropical depression. The JTWC issued its last advisory shortly after. Upon being classified a tropical storm, ships within 450 km (280 mi) of the storm were advised to take precautions and those not within that range were urged to avoid it.[86]

Tens of thousands of residents in the northern Philippines took shelter from the storm as there was a high likelihood over severe flooding due to already saturated grounds.[87] Schools throughout the area were canceled for several days due to the storm. The Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) placed Batanes under storm signal 2 while the Babuyan Islands were under storm signal 1.[88] In Taoyuan County, Taiwan (now Taoyuan City), a level three emergency response warning was put in place as Wutip approached the island.[89] Fourteen flights in and out of Taiwan were canceled due to the approaching storm and all ferry service was canceled.[90]

Previously saturated by Typhoon Pabuk, the outer bands of Wutip produced torrential rains over Luzon, Philippines, triggering numerous landslides and flash flooding. Two people were killed in a landslide in northern Luzon while another was electrocuted in knee-deep flooding in Manila.[87] Widespread street flooding resulted in large traffic jams and numerous road closures.[88] Ten homes were destroyed and another 32 were damaged by Wutip. A total of six people were killed by the storm, three due to electrocution, and seven were injured due to a tornado. A total of 239,292 people were affected by the storm and damages amounted to PHP16.8 million (US$349,000).[91] Following the flooding, the civil defense operations center in the Philippines deployed relief teams supplied with food to assist the affected regions.[87]

Typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	August 12 – August 20
Peak intensity	205 km/h (125 mph) (10-min)  910 hPa (mbar)

An area of disturbed weather developed west of the Northern Mariana Islands on August 11. Early the next day, the JMA began issuing advisories on the depression,[92] and the JTWC followed suit, designating it Tropical Depression 09W.[93] Twelve hours later, the JTWC upgraded the tropical depression to a tropical storm[94] based on Dvorak technique satellite intensity estimates and[95] the storm exhibiting tightly-curved convective bands. An upper-level low helped to reduce wind shear that had been affecting the storm.[95] The JTWC also warned of the possibility of rapid intensification.[95] The JMA upgraded the depression to a tropical storm later that day[96] and named it Sepat, a name contributed by Malaysia referring to a freshwater fish species.[13]

By early on August 13, Sepat had moved into PAGASA's area of responsibility and attained the local name "Egay". The JMA upgraded Sepat to a severe tropical storm shortly after.[97] Late that night, Sepat underwent rapid intensification as expected, and was upgraded by the JTWC to a super typhoon the next morning.[98] Sepat slowed in forward speed and took a turn from a west-southwest motion to a more poleward one.[99] Continuing to intensify,[100] Sepat reached a peak minimum central pressure of 910 hPa on the morning of August 16.[101] High ocean heat content and good equatorward outflow allowed Sepat to maintain its intensity, but an eyewall replacement cycle began later that night, resulting in weakening.[102] It made landfall in eastern Taiwan between Taitung and Hualien on the morning of August 18 local time at around 5 am (2100 UTC August 17)[103] and weakened to a minimal typhoon.[104] After crossing the island, Sepat held on to minimal typhoon intensity before weakening to a severe tropical storm that night.[105] It made a second landfall, in mainland China, about 24 hours after landfall on Taiwan and was downgraded to a tropical storm the next morning. It further weakened inland and the JMA issued its final advisory on the morning of August 20.

On August 15, monsoon rains brought by Typhoon Sepat flooded and paralyzed traffic in Metro Manila.[106] Classes and services in government offices were suspended until August 17.[107]

Typhoon (JMA)
Category 1 typhoon (SSHWS)
Duration	August 29 – September 8
Peak intensity	130 km/h (80 mph) (10-min)  965 hPa (mbar)

On August 28, an area of disturbed weather that had lingered east-northeast of Saipan became better organised. The Joint Typhoon Warning Center initiated warnings on Tropical Depression 10W the next morning,[108] and the JMA initiated advisories on a tropical depression the same day.[109] Under favourable conditions, the system intensified quickly, becoming Tropical Storm Fitow by afternoon[110] and a severe tropical storm by the evening of August 29.[111] The name Fitow was contributed by the Federated States of Micronesia, and is Yapese for a beautiful fragrant flower.[13] Rapid intensification ensued,[112] and Fitow became a typhoon early on August 30.[113] Fitow made landfall near Tokyo, Japan late on September 6[114][115] as a minimal typhoon.[116] The JMA downgraded Fitow to a severe tropical storm early on September 7,[117] and a tropical storm later that day.[118] The cyclone degenerated into a remnant low on September 8.[119]

In Japan, seven people were killed,[120] and at least 50 were injured, as Fitow brought strong winds and heavy rain. Over 80,000 houses experienced a power outage. Transport in and around Tokyo was also affected, with nearly 200 flights cancelled and many commuter trains suspended. In the Tama area west of central Tokyo, flood warnings were issued for the Tama River, and many homeless people who lived along its banks were swept away.[121]

Severe tropical storm (JMA)
Category 1 typhoon (SSHWS)
Duration	September 7 – September 11
Peak intensity	100 km/h (65 mph) (10-min)  990 hPa (mbar)

A disturbed area of weather northwest of Wake Island formed early on September 3 and tracked north then northwest, becoming more organised, and on September 6 was recognised as a full tropical depression by the JMA.[122] A TCFA was issued on the same day.[123] The storm continued northwest-ward toward Japan, becoming Tropical Storm Danas early on September 7.[124] The storm slowed its westward movement and headed north, and then northeast, becoming a severe tropical storm on September 9.[125] By the 11th, cooler waters had weakened the storm down to a tropical storm[126] and the storm degenerated into a remnant low later that day.[127] The name Danas was submitted by the Philippines and is defined in the Filipino language as "to go through an experience"[128] High waves from Danas injured two people in Japan.[129]

Typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	September 11 – September 17
Peak intensity	185 km/h (115 mph) (10-min)  935 hPa (mbar)

An area of disturbed weather developed northwest of Guam on September 10 and moved northwestward, slowly increasing in organisation. The Japan Meteorological Agency began monitoring the system as a tropical depression the next day. The depression continued to organise and strengthen, and the Joint Typhoon Warning Center issued a Tropical Cyclone Formation Alert on it during the afternoon of September 12, and began issuing advisories on Tropical Depression 12W an hour later. The JMA followed suit early on September 13 and initiated advisories on the system; PAGASA named the system Falcon shortly after. The depression continued to intensify, and the JMA upgraded it to Tropical Storm Nari later that morning. The storm then underwent rapid intensification that afternoon and evening, strengthening from a tropical depression to a typhoon in just 18 hours. The JMA upgraded Nari to a severe tropical storm late that afternoon, and by late that evening, Nari was upgraded to a typhoon. Nari reached its peak on September 14, and began weakening soon afterwards. It turned extratropical right after landfall in South Korea at tropical storm strength. At least 20 people have been killed or are missing due to the flooding caused by Nari. Rainfall totals reached a record 590 mm (23.2 in) in Jeju, South Korea. The name Nari was submitted by South Korea, and means lily.[13]

Typhoon (JMA)
Category 4 super typhoon (SSHWS)
Duration	September 15 – September 20
Peak intensity	185 km/h (115 mph) (10-min)  925 hPa (mbar)

An area of disturbed weather formed southeast of Naha, Okinawa early on September 13. This area gradually became better organised, and a TCFA was issued late on September 14.[130] The JMA upgraded the storm to a tropical depression on September 15,[131] and the JTWC soon followed suit with Tropical Depression 13W.[132] PAGASA named the storm "Goring" later that day. On September 16, the storm had gained enough organisation to be designated as a tropical storm.[133] On September 17, the storm underwent rapid intensification and quickly strengthened into a typhoon. It continued to strengthen rapidly and was upgraded by the JTWC to a super typhoon early on September 18. In the early hours, local time, of September 19, Wipha slammed into Fuding, near the Fujian–Zhejiang provincial border in China. However, before the storm made landfall it weakened slightly, becoming a Category 3-equivalent typhoon. Wipha originally threatened to pass over Shanghai, which would have made it the most destructive Chinese typhoon in over a decade. However, it veered to the south, making a direct impact unlikely. Throughout the Shanghai and Fujian-Zhejiang area, nearly 2 million people evacuated, including 1.5 million in Zhejiang and 291 thousand from low-lying areas, due to the threat from Wipha. The Xinhua News Agency considered the evacuations to be the region's most extensive in over a half century.[120]

Boats, ferries, and ships were called back into port to take refuge in harbors. At both airports in Shanghai, at least twenty flights were canceled and fifty postponed.[120] The typhoon also caused FIFA to reschedule four matches in the Women's World Cup.[134] Flooding was severe. In the area, at least 80 streets were flooded and brought water levels in several rivers and reservoirs to dangerous levels.[120] In total, nine people were killed and damage was estimated at over $880 million (US$).[135]

Tropical depression (JMA)
Tropical depression (SSHWS)
Duration	September 20 – September 21
Peak intensity	55 km/h (35 mph) (10-min)  1000 hPa (mbar)

An area of disturbed weather formed about 460 nmi (850 km) west of Guam early on September 19. It was recognised as a minor tropical depression by the JMA later that day. On September 20, the JTWC initiated advisories on Tropical Depression 14W.[136] Initially forecast to become a tropical storm, it was impacted by strong vertical wind shear and degenerated into a remnant low on September 21.[137]

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	September 21 – September 25
Peak intensity	75 km/h (45 mph) (10-min)  990 hPa (mbar)

An area of disturbed weather formed about 190 nmi (350 km) south-southeast of Hong Kong early on September 19. It was recognised as a minor tropical depression by the JMA on the 21st, and upgraded to a full depression on the 23rd.[138] The JTWC recognised Tropical Depression 15W at the same time.[139] Nine hours after being declared a full depression, the JMA and the JTWC upgraded it to Tropical Storm Francisco.[140][141] The storm traveled due west and over Wenchang on Hainan Island on September 24. Land interaction and moderate wind shear caused Francisco to weaken to a tropical depression as warnings were discontinued.[142][143][144] The name 'Francisco' was submitted by the United States and is a common Chamorro man's name.[145] A ship, carrying eight people sank over the South China Sea during the storm. Two of the people on the ship were rescued but the other six were listed as missing.[146]

Severe tropical storm (JMA)
Category 1 typhoon (SSHWS)
Duration	September 28 – October 4
Peak intensity	110 km/h (70 mph) (10-min)  975 hPa (mbar)

A tropical disturbance wave near the Philippines gradually developed. PAGASA was first to upgrade it, declaring it Tropical Depression Hanna on September 27, and upgrading it to a tropical storm the next day. It made landfall in central Luzon early on September 29, and shortly thereafter the JMA declared the system Tropical Storm Lekima. It continued to strengthen and was upgraded to a severe tropical storm on September 30 (the JTWC upgraded it to a typhoon) and remained at such until landfall. It dissipated over land on October 5[147]

Lekima brought heavy rains to Luzon causing a landslide that killed eight people, including three children, in Ifugao province, while another person was found dead in Quezon City.[148] Torrential rains also caused landslides, flooding, infrastructure damage, and disruption of transportation service in other parts of the country.[148] Over 100,000 people were evacuated in southern China as the storm approached, and more than 20,000 fishing boats were recalled back to the harbors.[135] On October 3, Lekima made landfall in Vietnam as a severe tropical storm. About 100,000 houses were destroyed and at least 42 people were reported dead or missing in Vietnam.[149]

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	September 30 – October 7
Peak intensity	75 km/h (45 mph) (10-min)  994 hPa (mbar)

A Tropical Low formed northeast of Wake Island on September 29, and it developed into a tropical depression late on September 30, which was operationally analyzed as an extratropical cyclone by the JMA on the next day.[150][151] On October 2, the JMA classified the system as a subtropical depression,[152] and on the next day, transitioned into a tropical depression at noon on October 3, when deep convection over the system dissipated again.[153] The JTWC analyzed that the system had intensified into a tropical storm early on October 4. Although operationally identified as an extratropical cyclone,[154] the JMA analyzed that Haiyan had intensified into a tropical storm at 00:00, and had organized well enough that it had formed an eye-like feature, as well as deep convection and curved banding. UTC on October 5.[155] Early on October 6, the JMA operationally upgraded the system to a tropical storm, but their post-storm analysis indicated that Haiyan had started to weaken and soon become a tropical depression at 06:00 UTC.[156] The agency downgraded Haiyan to a tropical depression operationally late on the same day, as well as the JTWC downgraded it to a tropical depression at the same time in best track data.[157] On October 7, Haiyan became totally exposed with a clear low-level circulation center, and Severe Tropical Storm Podul began to interact with it early on the same day, prompting Haiyan to accelerate northwards.[158] Soon, the JMA declared that Haiyan had dissipated, and the remnants were later absorbed by the new extratropical cyclone transitioned from Podul. However, the JTWC determined that Haiyan completely dissipated late on October 7. Originally not recognized by JTWC, Haiyan was added to the Best Track database and designated as 27W in their post-season analysis.

Typhoon (JMA)
Category 4 super typhoon (SSHWS)
Duration	October 1 – October 8
Peak intensity	195 km/h (120 mph) (10-min)  925 hPa (mbar)

In late September, a new system formed east of the Philippines. PAGASA declared it a tropical depression (Ineng) early on October 1, and the JMA and JTWC soon followed. It was upgraded to a tropical storm early on October 2, named Krosa. Rapid intensification took place on October 2 and it was upgraded to a typhoon by the JTWC by midday. As it intensified, it gained a wide, ragged eye and began to track to the west, becoming a typhoon by the JMA early on October 3. It continued to rapidly intensify that day before leveling off as a Category 4-equivalent typhoon on October 4. Fluctuations in intensity soon followed as Krosa approached Taiwan, as the JMA upgraded it to 105 knots (194 km/h) and the JTWC to a super typhoon early on October 5. It slowly weakened afterward before making landfall in northeastern Taiwan on October 6. At least 17 people were reported injured there, as the typhoon headed for China. An evacuation of 730,000 people from China's Zhejiang and Fujian provinces was ordered on the evening of October 6.[159] The extratropical remnants of Krosa crossed the International Dateline on October 12.

Severe tropical storm (JMA)
Duration	October 3 – October 7
Peak intensity	100 km/h (65 mph) (10-min)  985 hPa (mbar)

On October 6, a tropical depression east of Japan was upgraded to Tropical Storm Podul while racing northeast. It was short-lived over the northwest Pacific and degenerated into a remnant low early on October 7. One person was killed due to the effects of Podul in Japan.[129]

It was upgraded to severe tropical storm status by JMA in post analysis.[160]

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	October 11 – October 15
Peak intensity	85 km/h (50 mph) (10-min)  994 hPa (mbar)

On October 9, a disturbance from the North Central Pacific crossed the International Date Line, and became a tropical depression in the North Western Pacific, just east of the Date Line on October 11.[161] It was upgraded to Tropical Storm Lingling by the JMA,[162] and to Tropical Storm 18W by the JTWC, early on October 12.[163] Lingling headed northeast, and gradually became weaker. On October 13, the JTWC issued its final advisory,[164] and two days later the JMA did the same.[165]

Typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	October 19 – October 22
Peak intensity	165 km/h (105 mph) (10-min)  940 hPa (mbar)

An area of disturbed weather formed in the open ocean early on October 17, and tracked north-east. The JMA and the JTWC declared this area a tropical depression very early on October 19.[166] Six hours later, it was upgraded to Tropical Storm Kajiki.[167] Rapid intensification continued; another six hours later, it was upgraded to a severe tropical storm.[168][169] Kajiki became a typhoon early on October 20 as it rapidly intensified.[170] The storm reached peak intensity as it hit Iwo Jima and then gradually began weakening. The storm dropped upwards of 233 mm (9.1 in) of rain on the island.[171] The airport on Iwo Jima reported winds gusts up to 140 km/h (85 mph).[172]

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	October 25 – October 27
Peak intensity	100 km/h (65 mph) (10-min)  975 hPa (mbar)

On October 25, an area of disturbed weather was classified as a tropical depression by the JMA;[173] early the next day the JMA named it Tropical Storm Faxai as it moved north-west.[174] The JTWC picked the system up as a tropical depression early on the 26th,[175] but declared it extratropical twelve hours later without strengthening it to a tropical storm.[176] PAGASA declared the system Tropical Storm Juaning around the same time the JTWC picked it up.[177][178] Later on October 26, the JTWC resumed advisories as a tropical storm.[179] The JMA declared Faxai a severe tropical storm as October 27 began;[180] the same day, the JTWC stopped issuing advisories once more due to Faxai having completed its extratropical transition.[181] The JMA also stopped issuing advisories on the same day.[182]

Faxai killed one person and injured three others in Japan. One home, two hectares of farmland, and 2 km (1.2 mi) of roads were damaged by the storm. At the height of the storm, 9,605 residences were without power. Heavy rains trigged seven mudslides throughout the country. One ship sank during the storm. Total damages from Faxai totaled to ¥150 million ($1.5 million US$).[129]

Typhoon (JMA)
Category 1 typhoon (SSHWS)
Duration	November 3 – November 9
Peak intensity	130 km/h (80 mph) (10-min)  970 hPa (mbar)

An area of disturbed weather developed east of the Philippines on November 2. it was designated as Tropical Depression 21W & Tropical Depression Kabayan by PAGASA on November 3.[183][184] It then went on to rapidly develop later that day and was upgraded to Tropical Storm Peipah by the JMA on November 3.[185] Pepiah is a popular pet fish in Macau.[13] Early on November 4 it was upgraded to a severe tropical storm.[186] Later that day, just before landfall in the northern Philippines, the JTWC upgraded it to a typhoon.[187] Upon landfall in Palanan, Isabela Province, it pounded strong winds over Northern Luzon, thus unroofing houses, downing power lines and blocking many roads.[188] Once it emerged in the Philippine Sea, the JMA also upgraded it to a typhoon.[189] The strengthening trend was short-lived, though, as hindered outflow weakened the system on November 7.[190] It dissipated on November 9 before reaching Vietnam.

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	November 11 – November 13
Peak intensity	65 km/h (40 mph) (10-min)  996 hPa (mbar)

Early on November 8, the JTWC reported that an area of convection had persisted about 910 km, (565 miles), to the east of Guam.[191] Quickscat data had revealed that there was weak troughing at the surface but no closed low level circulation center existed. Lying under the edge of an upper level ridge the disturbance was in an area of moderate amount vertical windshear.[191] Over the next couple of days an anticyclone helped to develop the disturbance so that the JMA declared it a Tropical Depression on November 11.[192] Later that morning a TCFA, was issued by the JTWC later that morning as deep convection was now organizing into a partially exposed low level circulation center.[193] Later that day the JTWC designated the depression, as 22W whilst it was located 530 km, (330 miles), to the southwest of Iwo To.[194] The Depression at this stage was beginning to turn towards the north with deep convection consolidating since the TCFA was released, and was strongest along the northern edge of the system which was enhanced by poleward outflow into the midlatitude westerlies.[194] Early on November 12, the depression was upgraded to a Tropical Storm by both the JMA and the JTWC with the name Tapah being assigned whilst located to the southeast of Iwo Jima.[192][195] Both 1-minute and 10-minute peak windspeeds of 65 km/h, (40 mph), were reached as the JMA and the JTWC upgraded the depression to Tapah.[192][195] It remained at this intensity until later that day when both the JMA and the JTWC downgraded it to a Tropical Depression, and issued their final advisories whilst it was going through an extratropical transition before it dissipated early on November 13.[192][195][196]

Typhoon (JMA)
Category 1 typhoon (SSHWS)
Duration	November 18 – November 28
Peak intensity	130 km/h (80 mph) (10-min)  970 hPa (mbar)

On November 18, the Joint Typhoon Warning Center issued a TCFA on a Tropical Disturbance located east of the Philippines. Later that day the disturbance was upgraded to a Tropical Depression 24W by the JTWC. PAGASA also declared it Tropical Depression Lando early on November 19, and also upgraded it to a tropical storm soon after. The JTWC also upgraded it to a tropical storm that day. Early on November 21, the storm strengthened into a severe tropical storm. Later that afternoon, the JTWC upgraded Hagibis to typhoon status, and the JMA followed late that evening. The storm then wobbled off the coast of Vietnam beginning on November 22 where it gradually weakened. By November 24, due to its interaction with Typhoon Mitag, the storm turned back eastward in the South China Sea towards the Philippines once again. The JTWC issued its final advisory on November 27, although it was maintained by the JMA as it made landfall once again over the Philippines. It weakened to a depression east of the Philippines on November 28 and the JMA issued its final advisory.

Hagibis caused the deaths of nine people, all in the Visayas and Mindanao island groups.[197]

Typhoon (JMA)
Category 2 typhoon (SSHWS)
Duration	November 20 – November 27
Peak intensity	150 km/h (90 mph) (10-min)  955 hPa (mbar)

On November 20 an area of disturbed weather east of the Philippines strengthened and was classified as Tropical Storm Mitag by the JMA. The JTWC followed suit not long afterwards. The storm strengthened significantly early on November 21 and became a severe tropical storm. Later that day, the JTWC upgraded Mitag to a typhoon, and the JMA also upgraded it late that evening.

Philippine officials ordered the evacuation of 200,000 people on November 23, mostly from the Bicol Region as Mitag approached the coast. Additionally, the province of Albay declared a state of calamity.[198]

As Mitag remained stationary in the Philippine Sea for a day as a Category 2-equivalent typhoon, it changed its course and instead of hitting Catanduanes and the Bicol Region, it will make a landfall at the Aurora–Isabela area.[199] Nonetheless, PAGASA announced that there was still a possibility for the typhoon to once again change its course. The storm turned northwest towards northern Luzon and made landfall late on November 25. It tracked across the island and was downgraded to a severe tropical storm before emerging back over water on November 26. It turned back to the east before reaching Taiwan, and became extratropical on November 27.

Ten fatalities were attributed to Mina.[200] The remnants of Mitag contributed to heavy rains in Okinawa which damaged 3 km (1.9 mi) of roads and triggered one landslide.[129]

Tropical depression (SSHWS)
Duration	November 25 – November 27
Peak intensity	45 km/h (30 mph) (1-min)  1004 hPa (mbar)

On November 24 an area of disturbed area formed about 400 nmi (740 km) south east of Guam.[201] During the following day the JTWC issued a TCFA on the developing system whilst the JMA designated it as a minor tropical depression.[202][203] On November 26 the JTWC designated the depression as Tropical depression 25W[204] Over the next couple of days it tracked towards the north west maintaining its peak wind speeds of 25 kn (45 km/h 30 mph).[205] The depression then started its extra tropical transition on November 27 as it interacted with the Baroclinic zone, the JTWC then issued its final warning on 25W.[206] This was because the depression would succumb to the increasing vertical sheer and decreasing sea surface temperatures as it completed its extra tropical transition.[207]

Tropical depression (JMA)
Tropical depression (SSHWS)
Duration	November 28 – November 29
Peak intensity	45 km/h (30 mph) (10-min)  998 hPa (mbar)

Possibly from the remnants of 25W, an area of disturbed weather formed south-east of Yap on November 26.[208] The next day the JTWC issued a TCFA on the developing system.[209] On November 28, the JMA declared it as a minor tropical depression, whilst later that day the JTWC followed suit and designated it as a tropical depression, with the JTWC assigning the number 26W to the depression.[210][211] However the Tropical depression quickly became extratropical later that day with the JTWC issuing their final advisory on the storm later that day.[212] However the JMA continued to monitor the Depression until it dissipated the next day.[213]

During the season 24 tropical storms developed in the Western Pacific and each one was named by the JMA, when the system was judged to have 10-minute sustained windspeeds of 65 km/h (40 mph). The JMA selected the names from a list of 140 names, that had been developed by the 14 members nations and territories of the ESCAP/WMO Typhoon Committee. During the season, the name Peipah was used for the first time, after they replaced the name Vamei in 2001 season respectively.

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 2011 season. This is the same list used in the 2003 season, except for the names Bebeng, Goring, Hanna, Lando, Mina, Nonoy, Pedring, Ramon, and Sendong, which replaces Batibot, Gilas, Harurot, Lakay, Manang, Niña, Pogi, Roskas, and Sikat. The names Hanna, Lando and Mina were used for the first time this year; Bebeng was previously used in the 1999 season. Names that were not assigned are marked in gray.[216][217]