2012 Pacific typhoon season

Tropical depression (JMA)
Tropical depression (SSHWS)
Duration	February 17 – February 21
Peak intensity	55 km/h (35 mph) (10-min); 1004 hPa (mbar)

Early on February 17, the JMA reported that a tropical depression had developed, about 800 km (495 mi) to the southeast of Manila on the Philippine island of Luzon.[10] During that day the depression moved westwards, before the Joint Typhoon Warning Center initiated advisories at 1500 UTC and designated the system as Tropical Depression 01W.[11] However, six hours later the JTWC issued its final advisory as vertical windshear had started to increase, and after it had found no deep convection near the systems low level circulation centre during a reassessment of the depressions low level structure.[12] Over the next few days the JMA continued to monitor the depression before it was last noted during February 20.[13]

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	March 26 – April 2
Peak intensity	75 km/h (45 mph) (10-min); 986 hPa (mbar)

On March 17, a tropical disturbance formed northwest of Palau, and was located in an area of moderate vertical wind shear with unfavorable sea surface temperatures. Due to a high-pressure system extending into Vietnam, building up to the northeast of the system, the tropical disturbance slowly crossed the Visayas region and Palawan, during the next couple of days. On March 24, the JMA upgraded the system to a tropical depression, but downgraded it back to a tropical disturbance, on March 25, due to the collapsing outer rainbands, and the exposed low-level circulation center. Early on March 26, the JMA upgraded the tropical disturbance to a tropical depression again, because of low vertical wind shear and favorable sea surface temperatures, in the South China Sea, allowing the system to reorganize.

On March 28, the JTWC issued a TCFA on the tropical depression, as its LLCC began to consolidate more. Early on March 29, the JMA upgraded the tropical depression to a tropical storm, and named it Pakhar, because the storm's convection had completely wrapped around the circulation center. Early on March 30, the JTWC upgraded Pakhar to a Category 1 typhoon, as a banding eye formed. Because of land interaction and colder sea surface temperatures, the JTWC downgraded Pakhar to a severe tropical storm, early on March 31. On April 1, Pakhar made landfall near Vũng Tàu, Vietnam with gusting 132 km/h, and began to weaken. Early on April 2, the JMA reported that Pakhar had weakened into a tropical depression, before they reported later that day that the system had dissipated over Cambodia.[14]

Although Pakhar did not affect the Philippines as a tropical cyclone, its precursor produced heavy rains across part of the nation. Flooding occurred in different parts of central and southern Luzon, and the northern Visayas region.[15] In Basud, Camarines Norte, 128 families had to be evacuated due to flash flooding. A few landslides resulted from the rains, damaging or destroying a few homes. Throughout the affected region, five people were killed and three others were listed as missing.[16] In Vietnam, ten people were killed and several others were injured due to flash flooding and high winds. The hardest hit area was Khánh Hòa Province where the storm made landfall. About 4,400 homes were damaged in the region by the storm and thousands of acres of rice paddy were flooded.[17] In Ho Chi Minh City, officials reported that 600 homes and schools were destroyed.[18] Total damage were finalized at ₫1.12 trillion (US$53.9 million).[19] The remnants of the system brought rains to parts of Cambodia, Laos, and Thailand.[17]

Severe tropical storm (JMA)
Category 1 typhoon (SSHWS)
Duration	May 20 – May 27
Peak intensity	110 km/h (70 mph) (10-min); 975 hPa (mbar)

On May 20, the JMA reported that a tropical depression had developed about 525 km (325 mi) to the southeast of Guam.[20] During May 21, the JTWC also upgraded the system to a tropical depression later. Early on May 22, the JMA upgraded the system to a tropical storm and named it Sanvu. Late on May 23, the JTWC upgraded Sanvu to a category 1 typhoon, for the system became compact and more organized as an eye was forming. After being upgraded to a severe tropical storm by the JMA late on May 24, Sanvu's eye directly passed over Iwo Jima late on May 25. On May 26, strong vertical wind shear and cool sea surface temperature caused weaker convection around Sanvu, and the eye began to dissipate. The JTWC downgraded Sanvu to a tropical storm late on May 26, followed by the JMA early on May 27, as the system's low level circulation center started to become exposed. Late on May 27, the JMA reported that Sanvu had degenerated into an extratropical low, before the remnants dissipated during May 30.[20]

Sanvu brought tropical storm force wind gusts and rainfall between 38–51 mm (1.5–2 in) to parts of Guam and the Northern Mariana Islands.[21] However the only damage reported was on Guam where falling tree limbs caused an estimated $20,000 of damage to power lines.[21]

Typhoon (JMA)
Category 3 typhoon (SSHWS)
Duration	May 31 – June 6
Peak intensity	140 km/h (85 mph) (10-min); 960 hPa (mbar)

On May 29, a tropical disturbance formed northwest of Palau. On May 30, the disturbance began moving northwestwards, as it slowly strengthened. On May 31, the system's convection became significantly organized near Samar prompting the JTWC to issue a TCFA. Later that day, the PAGASA upgraded the low-pressure area to a tropical depression and assigned its local name Ambo, and the JTWC upgraded the disturbance into a tropical depression. On June 1, the JMA upgraded the system to a tropical storm and named it Mawar. On June 2, the JMA upgraded Mawar to a severe tropical storm, and the JTWC upgraded it to a category 1 typhoon as the convection began to wrap up and organize. On June 3, the JMA upgraded Mawar to a typhoon after the JTWC upgraded it to a category 2 typhoon. Early on June 4, the JTWC upgraded Mawar to a category 3 typhoon but downgraded it to a category 2 typhoon only six hours later, due to increasing wind shear coming from a subtropical jet stream located over Japan. On June 5, Mawar started its extratropical transition, and the JMA downgraded Mawar to a severe tropical storm. On June 6, Mawar fully became extratropical cyclone and dissipated east of the Kamchatka Peninsula on June 13.[22]

Mawar brought torrential rain to parts of the Philippines including the Bicol Region while enhancing the southwest monsoon which triggered delays and cancelled of air flights. In Bicol region, more than 332 passengers were stranded at ports due to Mawar.[23] Different domestic and international flights were forced to divert at Clark Air Base rather than NAIA due to bad weather. Some other flights were also cancelled.[24][25] At least three were reported dead due to rains brought by Mawar.[26]

Very strong typhoon (JMA)
Category 4 super typhoon (SSHWS)
Duration	June 10 – June 19
Peak intensity	185 km/h (115 mph) (10-min); 930 hPa (mbar)

Late on June 7, a tropical disturbance formed south-southeast of Pohnpei. Late on June 8, the Joint Typhoon Warning Center (JTWC) issued a Tropical Cyclone Formation Alert on that system but canceled it late on June 9. The Japan Meteorological Agency (JMA) upgraded the low-pressure area to a tropical depression on June 10, so did the JTWC early on June 11. Early on the next day, the JTWC upgraded the system to a tropical storm, and later the JMA also upgraded it to a tropical storm and named it Guchol. Early on June 14, the JMA upgraded Guchol to a severe tropical storm, and the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) assigned the local name Butchoy on it as the system entered the Philippine Area of Responsibility. Later that day, the JTWC upgraded Guchol to a category 1 typhoon, as convection started to organize. It continued to intensify into a category 2 typhoon on June 15, as it became better organized and started to develop more convection.

As Guchol went through rapid intensification with a well defined eye on June 16, the JMA upgraded it to a typhoon early that day, and the JTWC upgraded it further to a category 3 typhoon, and later a category 4 super typhoon. Guchol reached peak intensity late on June 17 before it began to undergo an eyewall replacement cycle as the storm began to weaken under moderate vertical wind shear on June 18, and later started its extratropical transition. The JTWC downgraded Guchol to a tropical storm on June 19, as it made landfall over Kii Peninsula in Japan. Later that day, the JMA downgraded Guchol to a severe tropical storm, as it moves over Japan. On June 20, the JMA issued their last advisories on Guchol, as it fully transitioned into an extratropical cyclone north east of Japan.

Between June 14 and 18, Guchol enhanced the southwestern monsoon over the Philippines, resulting in widespread rains. However, the effects of these rains were limited and only one fatality took place.[27] In Japan, airlines cancelled 420 domestic and international flights because of the strong winds, affecting 32,600 passengers. The town of Nachikatsuura, some 400 kilometres southwest of Tokyo, ordered nearly 1,600 residents to evacuate, warning of the danger of landslides brought on by heavy rain, media reports said. At least two people were killed and eighty others were injured across the country. Total economic losses were estimated in excess of ¥8 billion (US$100 million).[28]

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	June 16 – June 20
Peak intensity	95 km/h (60 mph) (10-min); 985 hPa (mbar)

On June 14, a low-pressure area within the monsoonal trough formed east of Hainan, China. On June 16, the low-pressure area started to absorb the surrounding convection from the dissipating monsoonal trough and started to organize, promoting the JMA and the HKO to upgrading the system to a tropical depression later that day. On June 17, the HKO raised the Standby signal, No. 1 as the tropical depression was centered about 470 kilometers from Hong Kong, and the JTWC issued a TCFA on the system. Late on the same day, the JMA upgraded the system to a tropical storm and named it Talim, and the JTWC upgraded Talim to a tropical depression. On June 18, the JTWC upgraded Talim to a tropical storm. On June 19, as the HKO raised the Strong Wind signal, No. 3, moderate vertical wind shear from the north pushed Talim's convection to the south. Later that day, the JMA upgraded Talim to a severe tropical storm, but the JMA downgraded it to a tropical storm early on June 20 as the LLCC fully exposed. Yet, Talim's convection soon wrapped around the center, as it began to merge with a monsoon trough. Later, the PAGASA assigned the local name Carina on the system as it briefly entered the Philippine Area of Responsibility. Late on June 20, both the JMA and the JTWC downgraded Talim to a tropical depression, as the system weakened in the Taiwan Strait. Shortly thereafter, the tropical depression was absorbed into the same monsoon trough which gave birth to Talim. Throughout China, 1 people were killed and total economic losses were counted to be CNY2.25 billion (US$354 million).[29]

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	June 25 – June 30
Peak intensity	75 km/h (45 mph) (10-min); 992 hPa (mbar)

On June 25, the JMA started to monitor a tropical depression that had developed, within the monsoon trough about 1,585 km (985 mi) to the southeast of Manila, Philippines.[30][31] During that day the depression moved north-westwards and consolidated further before during the next day, PAGASA started to monitor it as Tropical Depression Dindo.[32][33] Later that day, the JMA upgraded the system to a tropical storm and named it Doksuri,[34] and the JTWC upgraded Doksuri to a tropical depression.[35] Late on the same day, the JTWC upgraded Doksuri to a tropical storm.[36] On June 27, Doksuri's low-level circulation center became exposed due to moderate easterly wind shear.[37] On June 28, the JTWC downgraded Doksuri to a tropical depression, as the system's exposed circulation center began to undergo an unusual circulation center replacement cycle, which involves a circulation center to be replaced by another new circulation center.[38] Late on June 29, Doksuri made landfall over Nanshui, Zhuhai, Guangdong, China.[39] During June 30, the JMA reported that Doksuri had weakened into a tropical depression, before reporting that the depression had dissipated later that day.[40] In Macau, the storm caused minor roof damage.[41]

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	July 14 – July 19
Peak intensity	95 km/h (60 mph) (10-min); 985 hPa (mbar)

Late on July 12, a large cluster of thunderstorms associated with an Upper Level Low formed a weak low pressure area northwest of Guam. On July 13, the cold-core low separated with lower, warm-core low, and the warm-core low's convection started to organize, prompting the JMA to upgrade the system to a tropical depression late on July 14. Early on July 15, the JTWC issued a TCFA on the system, and it upgraded the system to a tropical depression later that day. On July 16, the JMA upgraded the system to a tropical storm and named it Khanun. Later on the same day, the JTWC upgraded Khanun to a tropical storm; also, the PAGASA named it Enteng as the system briefly passed the corner of the Philippine Area of Responsibility. Late on July 17, the JMA upgraded Khanun to a severe tropical storm, as Khanun's center passed over Okinoerabujima. On July 18, the JMA downgraded Khanun to a tropical storm, before the system passed over Jeju. Khanun weakened into a tropical depression near the Korean Demilitarized Zone early on July 19, and it became post-tropical late on the same day.

The storm killed at least one person in South Korea, while in North Korea, state-run media reported that at least seven people were killed in Kangwon Province, with an eighth fatality reported elsewhere. It said the storm caused significant damage, destroying 650 dwelling houses, 30 public buildings, railways, roads, bridges, and various systems. The flooding also inundated nearly 3,870 homes, leaving more than 16,250 people homeless.[42]

On July 29 the North Korean government dramatically raised the death toll in the country to 88, with an additional 134 injured. The biggest loss of human life was in two counties of South Pyongan Province. At least 63,000 were made homeless by the flooding, while more than 30,000 hectares of land for growing crops were submerged and will add to growing fears of another looming famine in the country. Three hundred public buildings and 60 factories were damaged during the storm.[43]

Typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	July 18 – July 25
Peak intensity	150 km/h (90 mph) (10-min); 950 hPa (mbar)

Originally Khanun's large area of convention on July 16, the JMA upgraded the system to a tropical depression on July 18.[44] On July 20, the JTWC issued a TCFA on the system;[45] soon, the PAGASA upgraded it to a tropical depression and named it Ferdie.[46] The JTWC also upgraded the system to a tropical depression late on the same day.[47] After the system moved into the South China Sea on July 21, the JMA upgraded the system to a tropical storm and named it Vicente,[48] so did the JTWC.[49]

On July 23, due to weak vertical wind shear and high sea surface temperature, Vicente started to undergo an explosive intensification prompting the JMA to upgrade Vicente to a typhoon, and the JTWC upgraded Vicente to a category 4 typhoon later.[50] At 16:45 UTC, the HKO issued the Hurricane Signal, No. 10, the first since Typhoon York in 1999.[51] Later, Typhoon Vicente made landfall over Taishan in Guangdong, China.[52] Due to land interaction, the JMA downgraded Vicente to a severe tropical storm early on July 24, and the JTWC downgraded Vicente to a category 3 typhoon.[53][54] Late on the same day, the JMA downgraded Vicente to a tropical depression.[55]

Typhoon (JMA)
Category 2 typhoon (SSHWS)
Duration	July 26 – August 5
Peak intensity	130 km/h (80 mph) (10-min); 960 hPa (mbar)

On July 26, the JMA reported that a tropical depression had developed within an area of strong vertical windshear in the monsoon trough about 1,000 kilometres (620 mi) to the southeast of Manila in the Philippines.

Early on July 28, the JTWC upgraded the system to a tropical depression, whilst the JMA upgraded it to a tropical storm and named it Saola. Soon, the PAGASA upgraded the system to a tropical depression and named it Gener. Later that day, the JTWC upgraded Saola to a tropical storm. Early on July 29, the JMA upgraded Saola to a severe tropical storm. On July 30, the JTWC upgraded Saola to a category 1 typhoon, as it started to develop an eye-like feature, but soon downgraded it to a tropical storm late on the same day. Late on July 31, the JMA upgraded Saola to a typhoon. It continued to intensify the next day, reaching its peak intensity as a Category 2 typhoon.

Most forecast models predicts Saola to pass very near on the northern coastline of Taiwan, but this is defied on August 1, when Saola had made landfall on Taiwan as a Category 2 typhoon. It moved slowly inland, making a counter-clockwise loop. It made out to sea, now downgraded as a severe tropical storm. Just then did Saola passed very close to the northern coastline of Taiwan, then it headed straight for China. On August 3 it made landfall near Fuding, Fujian Province as a tropical storm, then headed straight inland until on the next day when Saola dissipated near Jiangxi.

Typhoon (JMA)
Category 1 typhoon (SSHWS)
Duration	July 27 – August 4
Peak intensity	130 km/h (80 mph) (10-min); 965 hPa (mbar)

Originally a cold-core low, the system became a tropical disturbance southwest of Minamitorishima late on July 26. Early on July 27, the Japan Meteorological Agency (JMA) upgraded it to a tropical depression.[56] On July 28, the Joint Typhoon Warning Center (JTWC) issued a Tropical Cyclone Formation Alert on the system, before the JMA upgraded it to a tropical storm and named it Damrey.[57][58] Late on the same day, the JTWC upgraded Damrey to a tropical depression, and even upgraded it to a tropical storm on the next day.[59][60] After Damrey had drifted slowly for two days, the JMA upgraded it to a severe tropical storm northeast of Chichi-jima late on July 30, when the storm began to accelerate moving west-northwest and form a banding eye.[61] On August 1, the JTWC upgraded Damrey to a category 1 typhoon, while the system passed through the Ōsumi Islands in Japan, as it started to develop a well defined eye.[62] When Damrey drifted towards Yellow Sea on August 2, the JMA upgraded it to a typhoon. Soon, Typhoon Damrey made landfall over Xiangshui County in Jiangsu, China at 13:30 UTC (21:30 CST).[63] Late on August 2, the JTWC downgraded Damrey to a tropical storm with a final warning, before the JMA downgraded it to a severe tropical storm early on the next day. On August 3, the JMA downgraded Damrey to a tropical depression when it was located in Shandong. The system then dissipated near Hebei on August 4.[64]

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

Late on July 31, a tropical disturbance formed within a large monsoon trough. On August 1, the Japan Meteorological Agency (JMA) mentioned the system as a tropical depression southeast of Iwo Jima, and the Joint Typhoon Warning Center (JTWC) issued a Tropical Cyclone Formation Alert late on the same day.[65][66] Late on August 2, the JTWC upgraded it to a tropical depression, before the JMA upgraded the system to a tropical storm and named it Haikui early on the next day.[67][68] Early on August 4, the JTWC upgraded Haikui to a tropical storm.[69] On August 5, the JMA upgraded Haikui to a severe tropical storm when it was located north-northeast of Kume Island.[70] The JTWC upgraded Haikui to a category 1 typhoon Late on August 6, as it developed an eye. At 12Z on August 7, the JMA upgraded Haikui to a typhoon, but the JTWC downgraded it to a tropical storm simultaneously. Later, Typhoon Haikui made landfall over Xiangshan County in Zhejiang, China at 19:20 UTC (03:20 CST on August 8).[71] Early on August 8, the JMA downgraded Haikui to a severe tropical storm, when the JTWC issued the final warning. Soon, the JMA downgraded Haikui to a tropical storm.

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	August 3 – August 10
Peak intensity	95 km/h (60 mph) (10-min); 990 hPa (mbar)

During August 3, the JMA reported that a tropical depression had developed, about 720 km (445 mi) to the northwest of Wake Island.[72] Over the next day the system gradually developed further, before the JTWC started to monitor the system as Tropical Depression 13W, late on August 4.[73][74]

On August 5, the JTWC upgraded the system to a tropical storm.[75] Early on August 6, the JMA reported that the system had become extratropical.[76] However, the JMA designated it as a tropical storm with the name Kirogi early on August 8.[77] Early on August 9, the JTWC downgraded Kirogi to a tropical depression.[78] Later, the JMA upgraded Kirogi to a severe tropical storm, it reached its peak intensity,[79] while the JTWC upgraded it to a tropical storm again.[80] Later that day, the JTWC issued its final warning on Kirogi as it transitioned from a warm cored tropical system to a cold cored extratropical system.[81] The remnants of the system then entered the Sea of Okhotsk.

Typhoon (JMA)
Category 1 typhoon (SSHWS)
Duration	August 12 – August 18
Peak intensity	120 km/h (75 mph) (10-min); 970 hPa (mbar)

The monsoonal trough spawned a tropical disturbance early on August 10,[82] which had organizing convection and a weak circulation.[83] Early on August 12, the Japan Meteorological Agency (JMA) started tracking the system as a weak Tropical Depression with winds under 30 knots.[84] Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) started issuing advisories on the system, naming it Helen.[85] That day, the JTWC also initiated advisories on Tropical Depression 14W.[86] Early on August 13, the JMA upgraded the depression to Tropical Storm Kai-tak (1213).[87] and 9 hours later the JTWC followed suit.[88] Later the same day, the JMA upgraded it to a Severe Tropical Storm.[89] On August 15, the convection increased as outflow improved, and the JTWC upgraded Kai-tak to a typhoon.[90] The storm continued towards China, with deepening convection due to decreasing wind shear.[91] However, it was only at 0000 UTC on August 16 when the JMA officially declared Kai-tak a typhoon.[92] At the same time, the PAGASA issued their last warning on Kai-tak, otherwise known as Helen, locally, as it left the Philippine area of Responsibility.[93]

On the morning of August 17, Kai-tak made landfall over the Leizhou peninsula in southern China as a typhoon.[94] Within 6 hours, Kai-tak made a second landfall over the northeast coast of Vietnam and weakened slightly to a tropical storm.[95] Later that night, the JTWC issued their final warning on the system as it weakened further and sped up inland.[96] The JMA stopped tracking the storm early the next morning, no longer considering it a tropical cyclone.[97]

Typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	August 17 – August 30
Peak intensity	150 km/h (90 mph) (10-min); 950 hPa (mbar)

On August 16, a tropical disturbance formed southeast of Taiwan.[98] On August 17, the JMA mentioned it as a tropical depression, as a subtropical ridge pushed the system southwards.[99] The JTWC issued a TCFA on the system late on August 18;[100] early on the next day, the JMA upgraded it to a tropical storm and named it Tembin, and the JTWC upgraded it to a tropical depression.[101][102] Soon, the PAGASA also upgraded it to a tropical depression and named it Igme.[103] On August 20, Tembin entered a period of explosive intensification by excellent dual outflow, prompting both the JMA and the JTWC upgrading it to a typhoon.[104][105]

On August 22, Tembin began to undergo an eyewall replacement cycle, as it further weakened to a category 1 typhoon.[106] On August 23, Tembin re-intensified into a category 3 typhoon, before it made landfall over Pingtung, Taiwan later on the same day.[107] Due to minor land interaction, the JMA downgraded Tembin to a severe tropical storm early on August 24, and the JTWC downgraded it to a tropical storm later.[108] Soon, the JTWC upgraded Tembin to a typhoon when it moved into the South China Sea. Late on August 25, the JMA upgraded Tembin to a typhoon again, and the system intensified into a category 2 typhoon early on the next day. Afterward, Typhoon Tembin interacted with the nearby Typhoon Bolaven (Julian). Over the next few days, Tembin made a counterclockwise loop westward, moving back into the Philippine Area of Responsibility (PAR) in the process, causing more rainfall over in the Philippines. Afterward, Tembin weakened into a tropical storm on August 28 and turned north-northeastward. On August 30, Tembin made landfall on South Korea and transitioned into an extratropical storm, before dissipating two days later.

Very strong typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	August 19 – August 29
Peak intensity	185 km/h (115 mph) (10-min); 910 hPa (mbar)

Forming as a tropical depression on August 19 to the southwest of the Mariana Islands,[109] Bolaven steadily intensified as it slowly moved west-northwestward in a region favoring tropical development. The system was soon upgraded to a tropical storm less than a day after formation and further to a typhoon by August 21.[110][111] Strengthening became more gradual thereafter as Bolaven grew in size.[112] On August 24, the system attained its peak intensity with winds of 185 km/h (115 mph) and a barometric pressure of 910 mbar (hPa; 26.87 inHg). Weakening only slightly, the storm passed directly over Okinawa on August 26 as it began accelerating toward the north.[113][114][115] Steady weakening continued as Bolaven approached the Korean Peninsula and it eventually made landfall in North Korea late on August 28 before transitioning into an extratropical cyclone.[116] The remnants rapidly tracked northeastward and was last noted over the Russian Far East.[117]

Although Bolaven struck the Ryukyu Islands as a powerful typhoon, damage was less than expected. Relatively few buildings were damaged or destroyed across the region.[118] The most significant effects stemmed from heavy rains, amounting to 551.5 mm (21.71 in), that caused flash flooding and landslides.[119] One person drowned on Amami Ōshima after being swept away by a swollen river.[120] In mainland Japan, two people drowned after being swept away by rough seas.[121][122] In South Korea, 19 people were killed by the storm. Many buildings were damaged and approximately 1.9 million homes were left without power.[123][124] Losses in the country reached ₩420 billion (US$374.3 million), the majority of which was due to destroyed apple orchards.[125] Significant damage also took place in North Korea where at least 59 people were killed and 50 others were reported missing.[126] Additionally, 6,700 homes were destroyed. Offshore, nine people drowned after two Chinese vessels sank.[127] Total economic losses in China were counted to be CNY 19.82 billion (US$3.126 billion).[29]

Violent typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	September 10 – September 18
Peak intensity	205 km/h (125 mph) (10-min); 900 hPa (mbar)

A low-pressure area formed east of Palau on September 9.[128] On September 10, both the JMA and the JTWC upgraded it to a tropical depression.[129][130][131] As the system entered the PAR early on September 11, the PAGASA named it Karen.[132] At the same time, the JMA upgraded the system to a tropical storm and named it Sanba, and the JTWC also upgraded it to a tropical storm later.[133] Late on September 12, Sanba began explosive intensification, prompting the JMA upgrading it to a severe tropical storm and even a typhoon later. On September 13, the JTWC reported that Sanba strengthened into a category 5 super typhoon, and had intensified into the strongest typhoon since Megi in 2010. On September 15, as the system started to weaken into a category 3 typhoon, the well defined eye wall dissipated, and started to undergo an eyewall replacement cycle, and soon ended up with a 70 kilometer wide eye. On September 17, at 01:00 (UTC) Sanba made landfall over Korea.

In Kōchi Prefecture, Japan, 222 hectares (548 acres) of agricultural land was damaged by the storm, with losses reaching ¥50 million (US$640 thousand).[134] Throughout Okinawa, damage to agriculture, forestry, and fisheries amounted to ¥900 million (US$11.5 million).[135]

Violent typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	September 20 – October 1
Peak intensity	205 km/h (125 mph) (10-min); 905 hPa (mbar)

Late on September 17, a tropical disturbance formed east of Guam. Early on September 20, the JMA upgraded the low-pressure area to a tropical depression, just after the JTWC issued a TCFA on the system. Eight hours later, the PAGASA also upgraded the system to a tropical depression named Lawin, before the JTWC also upgraded it to a tropical depression. Late on the same day, the JMA upgraded the system to a tropical storm and named it Jelawat, and so did the JTWC. Half a day later, the JMA upgraded Jelawat to a severe tropical storm on September 21. Early on September 23, both the JMA and the JTWC upgraded Jelawat to a typhoon as it started to undergo explosive intensification, from a category 1 typhoon, to a category 4 typhoon in 12 hours, as it developed a small eye. Early on September 25, as Jelawat developed a 50-kilometre-wide (31 mi) eye after a few minor eye wall replacement cycles, the JTWC upgraded the system to a Category 5 Super Typhoon. On September 26, the JTWC downgraded the system to a Category 4 super typhoon, and it soon started to undergo its fourth eye wall replacement cycle, which lasted 15 hours. The eye ended up at 70 kilometers across. On September 28, it struck Taiwan in typhoon strength. 12 hours later, it weakened to a category 3 typhoon and category 2 on the next day due to cool sea surface temperatures, then to a category 1 typhoon. On September 30, it made landfall on Japan, then on October 1 the system became an extratropical cyclone.[136]

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	September 23 – September 30
Peak intensity	95 km/h (60 mph) (10-min); 985 hPa (mbar)

Early on September 22, a tropical disturbance formed west of Guam, out of the Intertropical Convergence Zone, and the JMA upgraded it to a tropical depression on the next day. On September 24, the JTWC upgraded the system to a tropical depression, as it became better organized, however the low level circulation center remained exposed, due to outflow wind shear from Jelawat, which pushed the convection to the east of the system, and prevented it from strengthening more quickly. On September 24, the JTWC further upgraded the system to a minimal tropical storm and named it Ewiniar, as the system started moving away from Jelawat, which allowed it to strengthen. On September 27, with the system far from Jelawat's outflow, the exposed low level circulation center was wrapped with convection, and the JMA upgraded the system to a Severe tropical Storm. A small eye-like feature showed up in the satellite image of Ewiniar. On September 29, the system became totally exposed, with the convection being blown away by strong vertical wind shear. It became extratropical the next day.[137]

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	September 29 – October 4
Peak intensity	95 km/h (60 mph) (10-min); 985 hPa (mbar)

On September 27, a large tropical disturbance formed near Chuuk. On September 29, the JMA upgraded the system to a tropical depression. On October 1, the system was upgraded into a tropical storm and named Maliksi. The large storm developed a mid-level circulation center, with microwave satellite imagery showing that the storm had become less organized during the morning hours of October 2 because it had become slightly elongated and on October 3, the JMA upgraded it to Severe Tropical Storm, and the storm's center soon passed over Iwo To. High wind shear and unfavorable conditions made it weaken as it started transitioning to an extratropical system. On October 4, it became fully extratropical, with wind shear from the southwest, which pushed most of the showers and thunderstorms northeast of the center of circulation.[138]

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	September 29 – October 7
Peak intensity	95 km/h (60 mph) (10-min); 990 hPa (mbar)

On September 29, the JMA reported that a tropical depression that had developed within the monsoon trough, about 745 km (465 mi) to the northwest of Ho Chi Minh City in Southern Vietnam.[139][140] As the tropical depression organized, large, powerful thunderstorms with very cold cloud top temperatures (colder than -63F/-52 C) surrounded the center of circulation, hinting that the storm was organizing and strengthening. The system remained quasi-stationary over the next 12 hours, due to weak steering environment. On October 1, the system strengthened into a tropical storm,[141]and was named "Gaemi" by the JMA, and soon strengthened into a Severe Tropical Storm on October 3. The PAGASA assigned the local name Marce as it entered the Philippine Area of Responsibility (PAR) on October 3, with the outer rainbands of the storm dropped rains all over Luzon, causing floods and prompting class suspensions. The JTWC originally anticipated the storm to strengthen into a category 1 typhoon, however on October 4, moderate vertical wind shear coming from the east blown the system's convection away, its low level circulation center became totally exposed. Gaemi made a large cyclonic loop during its lifetime, and on October 6, at 1100 (UTC), Gaemi made landfall over southern Tuy Hòa, Vietnam as a tropical storm. The remnants brought heavy rain over Thailand, and spawned an area of convection that developed into Deep Depression BOB 01 in the Bay of Bengal.

Very strong typhoon (JMA)
Category 3 typhoon (SSHWS)
Duration	October 5 – October 19
Peak intensity	165 km/h (105 mph) (10-min); 940 hPa (mbar)

On October 5, the JMA started to monitor a tropical depression that had developed about 115 km (70 mi) to the northeast of Hagåtña, Guam.[142] On October 7, the JMA upgraded the tropical depression to a tropical storm, and named it Prapiroon. The PAGASA also assigned the local name Nina as the system entered the Philippine Area of Responsibility (PAR). As the JMA upgraded the storm to a Severe Tropical Storm on October 8, rapid convection produced a tightly wrapped system with multiple deep convective bands wrapping into a well-defined low level circulation center.[143] On October 9, the JTWC, and the JMA upgraded the system to a typhoon. On October 11, as the system developed a ragged eye, the JTWC upgraded Prapiroon further, to a category 2 typhoon. The ragged eye soon became well defined as seen in Microwave imagery later that day, and was soon upgraded further to a category 3 typhoon. On October 15, as the system was pushed south, by an anticyclone ridging in from the north, and caused it to make a small cyclonic loop. On October 16, an Anticyclone located on the north west of Prapiroon became slightly displaced to the southeast, which brought wind shear to Prapiroon's northern periphery's convection to be pushed to the south, and caused a strong southern outflow. On October 19, Prapiroon transitioned into an extratropical cyclone, as it became bombarded by strong vertical wind shear. The remnants of Prapiroon's center fully dissipated early on October 23.[144]

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	October 12 – October 20
Peak intensity	95 km/h (60 mph) (10-min); 990 hPa (mbar)

Late on October 12, the JMA started to monitor a tropical depression that had developed near the Northern Mariana Islands, about 400 km (250 mi) to the northeast of Guam.[145][146]

As it moved westward it strengthened to become Tropical Storm Maria on October 14.[147] Early the next day, the JMA upgraded the Maria into a severe tropical storm.[148] On October 19, the system's low level circulation center became totally exposed, with strong wind shear eroding the entire system into an exposed vortex, almost devoid of convection, as it slowed down on movement. Early on October 20, the JMA reported that Maria had dissipated.[145]

Very strong typhoon (JMA)
Category 3 typhoon (SSHWS)
Duration	October 21 – October 29
Peak intensity	155 km/h (100 mph) (10-min); 945 hPa (mbar)

On October 19, a tropical disturbance formed southeast of Yap, and the JMA mentioned the system as a tropical depression on October 21.[149] On October 22, the PAGASA started to monitor the tropical depression and named it Ofel. On October 24, the storm made landfall over Leyte and capsized 6 boats in Tacloban City.[150] The storm caused heavy rains and strong winds over the Visayas. At the night of October 24, the storm hardly hit Cebu with rain and winds. Classes in Cebu City were suspended the next day.[151]

Authorities in the Philippines confirmed at least four deaths – an 8-year-old boy who drowned, two men crushed by falling trees, and an elderly man who died from hypothermia. Six fishermen were reported missing, and more than 13,000 passengers were stranded at ferry terminals and ports. Widespread flooding was reported as rivers burst their banks, in some instances rising as much as 12.8 meters in 24 hours. A cargo ship, called the ML Lady RP II, sank with around 1,200 sacks of copra near Zamboanga City at the height of the storm. Strong winds derailed a train in Quezon.[152]

Son-Tinh reached typhoon strength on October 27.[153]

Tropical depression (JMA)
Tropical depression (SSHWS)
Duration	November 12 – November 15
Peak intensity	55 km/h (35 mph) (10-min); 1004 hPa (mbar)

Early on November 12, the JTWC reported that a tropical disturbance had developed within an area of weak to moderate vertical windshear, about 315 km (195 mi) to the southeast of Manila in the Philippines.[154][155] Later that day as the system moved towards the north-northwest, the JTWC reported that the disturbance had become a tropical depression before the JMA followed suit early on November 13.[154][156]

Very strong typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	November 25 – December 9
Peak intensity	185 km/h (115 mph) (10-min); 930 hPa (mbar)

On November 23, the JTWC reported that a large area of convection persisted approximately 0.6°N of the equator, or 350 nm south of Pohnpei in the Caroline Islands, and dubbed the system as Invest 90W.[157] Its organization steadily improved over the next few days under a favorable conditions with warm sea surface temperatures.[158] and on November 25 both JTWC and JMA upgraded its status to a Tropical Depression, while the JTWC designated it with 26W.[159][160] During the early hours of November 26, an upper-level anticyclone formed over the center with near-radial outflow and weak vertical wind shear.[161] Under its influence, 26W strengthened gradually and acquired tropical storm status by that evening. As a result, the JMA officially named the storm Bopha.[162] On November 27, a deep centralized convective cover developed over the LLCC and the JTWC too upgraded Bopha into a tropical storm.[163] By the evening of December 2, the storm entered the Philippine Area of Responsibility and was named Pablo. Late on December 3, as the system continued to strengthen, the system unexpectedly rapidly intensified into a category 5 super typhoon, as the eye started to become well defined at 27 kilometers across. Bopha made landfall as a Category 5 Super Typhoon.[164] After landfall in Visayas and Mindanao, Bopha weakened to tropical storm as it passed through Palawan island. On December 7 Bopha rapidly re-intensified, going from a Category 1 to a Category 4 in less than 6 hours. The next day it weakened rapidly from a Typhoon to a Tropical Storm due to moderate vertical wind shear. On December 9, the Joint Typhoon Warning Center issued its final advisory. Later that day Bopha weakened into tropical depression and dissipated completely 70 kilometers north of Binabalian, Philippines.

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	December 24 – December 29
Peak intensity	75 km/h (45 mph) (10-min); 1000 hPa (mbar)

Early on December 24, the JMA reported that a tropical depression had developed within a trough of low pressure, about 220 km (135 mi) to the north-east of Palau.[165][166] During that day the depressions low level circulation gradually consolidated further, as it moved towards the west-northwest along the southern edge of the subtropical ridge of high pressure.[167] The JTWC and PAGASA subsequently initiated advisories on the system with the latter naming it Quinta.[168][169] Early on Christmas Day 2012, the JMA reported that the depression had become a tropical storm and named it as Wukong, before reporting that the system had attained its peak 10-minute sustained windspeeds of 75 km/h (45 mph).[166] Later that day, the system passed over or close to several of the Visayan Islands, before the JTWC reported that the system had reached its peak 1-minute sustained windspeeds of 65 km/h (35 mph).[170][171]

During December 26, Wukong continued to move through the Philippine islands, before the JTWC reported that the system had become a tropical depression, after its low level circulation center became fully exposed within an area of moderate to strong vertical windshear.[171][172] However, throughout December 27, as the system moved through the South China Sea and deep convection redeveloped over the systems center, the JMA continued to report that Wukong was a tropical storm.[166][173] During the next day, the JMA reported that the system had weakened into a tropical depression, before the JTWC issued their final warning on Wukong as a north-easterly cold surge along the coast of south-east Asia had caused the depression to become fully exposed.[166][174] The depression subsequently was last noted during the next day by both the JTWC and the JMA, dissipating about 190 km (120 mi) to the south of Vietnam.[166][171]

Within the Philippines, 20 people were killed, while 4 others were left missing.[175][176]

On January 13, the JMA started monitoring a tropical depression that was located within an area of moderate to strong vertical windshear about 625 km (390 mi) to the east of Kuala Lumpur in Malaysia.[177][178] During that day the depression remained near stationary, before the JMA issued their final advisory on the system during the next day as the system dissipated.[179][180][181] On April 8, the JMA started to monitor a tropical depression, that had developed about 2,000 km (1,245 mi) to the northeast of Tarawa island in Kiribati.[182] Over the next few days the JMA continued to monitor the depression, before it was last noted by the JMA during April 11 about 450 km (280 mi) to the northwest of Wake Island.[183] Late on April 28, the JMA reported that a tropical depression had developed about 460 km (285 mi) to the southeast of Davao City on the Philippine island of Mindanao.[184] Over the next day, the depression moved towards the west-northwest, before it was last noted early on April 30, as it dissipated near Mindanao.[185][186][187][188]

On August 5, the Central Pacific Hurricane Center started to monitor a TUTT cell that had developed into a subtropical low, while located about 400 km (250 mi) to the southeast of Midway Atoll.[189][190] Over the next few days the low moved westwards towards the Western Pacific, before it moved into the basin during August 7. As it continued to move towards the west the JMA reported on August 9, that the low had developed into a tropical depression.[191] The system re-entered the Central Pacific Ocean early on August 11.[192] On August 23, the JMA reported that a tropical depression had developed about 441 km (275 mi) to the northeast of Shanghai in China.[193] Over the next few days, the depression moved northwards, before it was last noted by the JMA during August 25 moving into North Korea.[194][195] During September 10, the JMA started to monitor a tropical depression, that had developed in an area of moderate vertical windshear between two upper tropospheric trough cells about 945 km (585 mi) to the southeast of Tokyo, Japan.[196][197] During that day the depression remained near stationary, before it started during September 11 to move northwards as it directly interacted with another area of low pressure, located about 405 km (250 mi) to the northwest of the depression.[198][199][200] Over the next couple of days, as the depression moved towards the northwest, the system transitioned into a subtropical cyclone, before it was last noted by the JMA during September 13.[201][202]

During the season 25 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 names Pakhar, Doksuri, Haikui, Sanba, Maliksi and Son-Tinh were used for the first time, after they had replaced the names Matsa, Nabi, Longwang, Chanchu, Bilis and Saomai, which were retired after the 2005 and 2006 seasons.

After the season the Typhoon Committee retired the names Vicente and Bopha from its naming lists, and in 2014 and 2015, the names were subsequently replaced with Lan and Ampil for future seasons.[205]

During the season PAGASA used its own naming scheme for the 17 tropical cyclones, that either developed within or moved into their self-defined area of responsibility.[206] The names were taken from a list of names, that had been last used during 2008 and are scheduled to be used again during 2016.[206] The names Carina and Ferdie were used for the first time during the year after the names Cosme, and Frank were retired.[206]

After the season the name Pablo was retired by PAGASA, as it was responsible for over 300 deaths and Php1 billion in damages. It was subsequently replaced on the list with Pepito.[207]