2015 Pacific typhoon season

2015 Pacific typhoon season

Season summary map
First system formed	January 2, 2015
Last system dissipated	December 23, 2015
Strongest storm1	Soudelor – 900 hPa (mbar), 215 km/h (130 mph) (10-minute sustained)
Total depressions	39
Total storms	27 official, 1 unofficial
Typhoons	18
Super typhoons	9 (unofficial)
Total fatalities	254 total
Total damage	$10.2 billion (2015 USD)
1Strongest storm is determined by lowest pressure
Pacific typhoon seasons 2013, 2014, 2015, 2016, 2017
Related article
Timeline of the 2015 Pacific typhoon season

The 2015 Pacific typhoon season was a slightly above average season that produced 27 tropical storms, 18 typhoons and nine super typhoons. The season ran throughout 2015, though most tropical cyclones typically develop between May and October. The season's first named storm, Mekkhala, developed on January 15, while the season's last named storm, Melor, dissipated on December 17. The season saw at least a named tropical system forming in each of every month, the first time since 1965. Similar to the previous season, this season saw a high number of super typhoons.

The scope of this article is limited to the Pacific Ocean to the north of the equator between 100°E and 180th meridian. Within the northwestern Pacific Ocean, there are two separate agencies that assign names to tropical cyclones which can often result in a cyclone having two names. The Japan Meteorological Agency (JMA) will name a tropical cyclone should it be judged to have 10-minute sustained wind speeds of at least 65 km/h (40 mph) anywhere in the basin, whilst the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) assigns names to tropical cyclones which move into or form as a tropical depression in their area of responsibility located between 135°E and 115°E and between 5°N–25°N regardless of whether or not a tropical cyclone has already been given a name by the JMA. Tropical depressions that are monitored by the United States' Joint Typhoon Warning Center (JTWC) are given a number with a "W" suffix.

Seasonal forecasts

TSR forecasts Date	Tropical storms	Total Typhoons	Intense TCs	ACE	Ref
Average (1965–2014)	26	16	8	294	[1]
May 6, 2015	27	17	11	400	[1]
August 5, 2015	30	20	13	448	[2]
Other forecasts Date	Forecast Center	Period		Systems	Ref
January 8, 2015	PAGASA	January — March		1–2 tropical cyclones	[3]
January 8, 2015	PAGASA	April — June		1–3 tropical cyclones	[3]
June 30, 2015	CWB	January 1 – December 31		28–32 tropical storms	[4]
July 6, 2015	PAGASA	July — September		7–10 tropical cyclones	[5]
July 6, 2015	PAGASA	October — December		3–5 tropical cyclones	[5]
	Forecast Center	Tropical cyclones	Tropical storms	Typhoons	Ref
Actual activity:	JMA	39	27	18
Actual activity:	JTWC	30	28	21
Actual activity:	PAGASA	15	14	10

During the year several national meteorological services and scientific agencies forecast how many tropical cyclones, tropical storms, and typhoons will form during a season and/or how many tropical cyclones will affect a particular country. These agencies included the Tropical Storm Risk (TSR) Consortium of the University College London, Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) and the Taiwan's Central Weather Bureau. Some of the forecasts took into consideration what happened in previous seasons and the El Niño Conditions that were observed during the year. The first forecast of the year was released by PAGASA during January 2015, within its seasonal climate outlook for the period January – June.^[3] The outlook noted that one to two tropical cyclones were expected between January and March while one to three were expected to develop or enter the Philippine Area of Responsibility between April and June.^[3]

During March the Hong Kong Observatory predicted that the typhoon season in Hong Kong, would be near normal with four to seven tropical cyclones passing within 500 km (310 mi) of the territory compared to an average of six.^[6] Within its Pacific ENSO Update for the 2nd quarter of 2015, NOAA's Pacific El Niño-Southern Oscillation Applications Climate Center, noted that the risk of a damaging tropical cyclone in Micronesia was "greatly enhanced" by El Niño.^[7] As a result, they forecasted that the risk of a typhoon severely affecting Micronesia was high, with most islands predicted to have a "1 in 3 chance" of serious effects from some combination of high winds, large waves and extreme rainfall from a typhoon.^[7] They also predicted that there was a near 100% chance of severe effects from a typhoon somewhere within Micronesia.^[7] On May 6, Tropical Storm Risk issued their first forecast for the season and predicted that the season, would be the most active since 2004 with activity forecast to be above average.^[1] Specifically it was forecast that 27 tropical storms, 17 typhoons, and 11 intense typhoons would occur, while an ACE Index of 400 was also forecasted.^[1]

Ahead of the Thailand rainy season starting during May, the Thai Meteorological Department predicted that one or two tropical cyclones would move near Thailand during 2015.^[8] The first of the two tropical storms was predicted to pass near Upper Thailand in either August or September, while the other one was expected to move to the south of Southern Thailand during November.^[8] On June 30, Taiwan's Central Weather Bureau predicted that 28–32 tropical storms would develop over the basin, while two — four systems were expected to affect Taiwan itself.^[4] During July, Paul Stanko of the United States National Weather Service Weather Forecast Office in Tiyan, Guam, called for tropical cyclone activity to be above average.^[9] He also predicted that several records would be set for the number of major typhoons in the western Pacific, tropical storms, typhoons and major typhoons in Micronesia.^[9] PAGASA subsequently predicted within its July — December seasonal climate outlook, that seven to ten tropical cyclones were likely to develop and/or enter the Philippine area of responsibility between July and September, while three to five were predicted for the October–December period.^[5] On July 16, the Guy Carpenter Asia-Pacific Climate Impact Centre (GCACIC) and the City University of Hong Kong's School of Energy, released their seasonal forecast for the period between June 1 – November 30.^[10] They predicted that 19.9 tropical cyclones would develop during the period with 10.3 of these going on and making landfall compared to averages of 23.0 and 17.4 tropical cyclones.^[10] They further predicted that both the Korea — Japan region and that Taiwan and the Eastern Chinese provinces of Jiangsu, Shanghai, Zhejiang, Fujian would see three of these landfalls each.^[10] Vietnam, the Philippines and the Southern Chinese provinces of Guangdong, Guangxi and Hainan were forecasted to see four landfalling tropical cyclones.^[10] On August 5, Tropical Storm Risk issued their final forecast for the season and predicted that 2015 would be a hyperactive season.^[2] Specifically it was forecast that 30 tropical storms, 20 typhoons, 13 intense typhoons would occur, while an ACE Index of 448 was also forecasted.^[2]

Season summary

Most of the 27 tropical cyclones affected Micronesia, because of the strong 2014-16 El Niño event. 2015 opened with Tropical Depression Jangmi (Seniang) active within the Sulu Sea to the north of Malaysia.^[11] The system subsequently moved south-eastwards, made landfall on Malaysia, and dissipated later that day.^[11] However the official first tropical cyclone of the season was a minor tropical depression, in the same place where Jangmi persisted on January 2, but dissipated two days later.^[12] Tropical Storm Mekkhala, in January 13, developed and approached the Philippines where it caused minor damages and also notably interrupted Pope Francis’ visit to the country.^[12] In early-February, Typhoon Higos developed further east of the basin and reached peak strength of a Category 4 typhoon. Higos became the strongest typhoon on record in the month of February when it broke the record of 1970's Typhoon Nancy.^[13] During the opening days of March 2015, a major westerly wind burst occurred, which subsequently contributed to the development of the 2014–16 El Nino event and Tropical Storm Bavi.^[14] Typhoon Maysak developed and became the most intense pre-April tropical cyclone on record, with a peak of 280 km/h (175 mph) 1-minute sustained winds and a minimum pressure of 910 mbar (26.87 inHg).^[15] Only one weak system (Haishen) formed on April and caused little to no damage.^[16]

In May, two storms, Typhoons Noul and Dolphin, both reached Category 5 super typhoon intensity.^[17] Both typhoons affected landmasses and altogether caused about $37.1 million in damages, respectively. Kujira formed in June and made landfall in southeast Asia, bringing flooding.^[18] During the first week of July, the tropics rapidly became active, with a trio typhoons developing simultaneously and affecting three different landmasses. Total damages from Chan-hom, Linfa and Nangka nearly reached US$2 billion. Afterwards, Typhoon Halola entered the basin from the Eastern Pacific.^[19] In August, Typhoon Soudelor made landfall in Taiwan and China, where it killed 38 people and damages totaled up to US$3.7 billion. Typhoon Goni badly affected the Philippines, the Ryukyu Islands and Kyushu as an intense typhoon, causing about US$293 million in damages.^[20]

In September, Tropical Storm Etau brought flooding in much of Japan, with damages at least US$100 million. Tropical Storm Vamco made landfall over in Vietnam and caused moderate impact and damages. Typhoon Dujuan, similar to Soudelor, impacted China and Taiwan with total damages of $660 million as a Category 4 super typhoon.^[21] In early October, Typhoon Mujigae rapidly intensified into a Category 4 typhoon when it made landfall over Zhanjiang, spawning a tornado causing 29 deaths and over US$4 billion in damages. Later, Typhoon Koppu devastated the Philippines as a super typhoon, causing at least $230 million in damages and killing at least 55 people.^[22] Typhoon In-fa became a strong typhoon in November, causing minor impact over in the Caroline Islands.^[23] In December, Typhoon Melor maintained Category 4 intensity as it passed the Philippine Islands with 42 deaths and US$140 million in damages, while a tropical depression, named Onyok by PAGASA, made landfall in southern Philippines. The final tropical cyclone of the year developed near Malaysia on December 20, and dissipated three days later.^[24]

Storms

Severe Tropical Storm Mekkhala (Amang)

Severe tropical storm (JMA)
Category 1 typhoon (SSHWS)
Duration	January 13 – January 21
Peak intensity	110 km/h (70 mph) (10-min)  975 hPa (mbar)

Tropical Depression 01W developed during January 13, to the south of Chuuk State.^[25][26] Despite convection being displaced from its exposed low-level circulation center (LLCC),^[27] the JMA upgraded 01W to a tropical storm with the name Mekkhala, the first of the season.^[28] Later, the PAGASA had stated that Mekkhala had entered the Philippine Area of Responsibility, assigning it the local name Amang.^[29] By January 15, the JTWC upgraded Mekkhala to a tropical storm when spiral banding wrapped into a defined LLCC.^[30][31] Mekkhala intensified to a severe tropical storm when deep convection wrapped into its center during January 16.^[32][33] Satellite imagery revealed that a central dense overcast had obscured its center, therefore Mekkhala strengthened into a Category 1 typhoon by the JTWC.^[34] Operationally the JMA classified Mekkhala's peak as a typhoon on January 17,^[35] however in post-analysis Mekkhala reached its peak as a severe tropical storm.^[36] At the time when Mekkhala made landfall over in Eastern Samar, Visayas,^[37] land reaction persisted and the typhoon weakened to a tropical storm.^[38] By January 18, Mekkhala continued weakening as it started to "unravel and erode" as it passed through the Bicol region in Luzon.^[39] Both the JMA and the JTWC issued their final warning later that day.^[40][41] However, the JMA continued to monitor Mekkhala until it dissipated early on January 21.^[25]

Mekkhala (Amang) had mostly minor impacts in the Philippines. The storm left 3 dead in total in Bicol region and caused about ₱318.7 million (US$7.1 million) in damages.^[42] Moreover, the storm caused agricultural damage of ₱30.3 million (US$680,000) in Samar, where it made landfall.^[43] Mekkhala also interrupted Pope Francis' visit to the Philippines on January 17.^[44]

Typhoon Higos

Typhoon (JMA)
Category 4 super typhoon (SSHWS)
Duration	February 6 – February 12
Peak intensity	165 km/h (105 mph) (10-min)  940 hPa (mbar)

During February 6, the JMA started to monitor a tropical depression that had developed about 190 km (120 mi) to the northwest of Palikir in Pohnpei State.^[45] By January 7, the JTWC started issuing advisories while designating the system as 02W.^[46] Deep convection later deepened over in its LLCC and 02W intensified into a tropical storm, with the JMA naming it as Higos.^[47][45] Higos started to organize as it convection consolidated and its center became well-defined.^[48] The JMA upgraded Higos to a severe tropical storm thereafter.^[45] With multiple curved bands wrapping to its center, Higos strengthened into a Category 1 typhoon.^[49] The JMA upgraded Higos to a typhoon early on February 9.^[50] Higos explosively intensified through the course of 24 hours and on February 10, Higos reached its peak intensity with 1-minute sustained winds of 240 km/h (150 mph), making it the first super typhoon of the season. Later, Higos rapidly weakened; its eye dissipated and convection became less organized, so the JMA downgraded Higos to a severe tropical storm.^[51][45] By February 11, Higos further weakened to a tropical storm as its center became fully exposed.^[45][52] Both agencies issued their final warning later that day and Higos fully dissipated on February 12.^[45][53]

Tropical Storm Bavi (Betty)

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	March 10 – March 21
Peak intensity	85 km/h (50 mph) (10-min)  990 hPa (mbar)

Tropical Storm Bavi was first noted as a tropical disturbance during March 8, while it was located 500 km (310 mi) to the southeast of Kwajalein Atoll in the Marshall Islands.^[54] Over the next few days the system moved north-westwards through the Marshall Islands, and was classified as a tropical depression during March 10.^[55] The system continued to develop over the next day as it moved north-westwards, before it was classified as a tropical storm and named Bavi by the JMA.^[55] The system subsequently continued to gradually intensify as it moved westwards, around the southern periphery of the subtropical ridge of high pressure located to the northwest of the system.^[55][56] During March 14, the system peaked as a tropical storm with the JMA reporting 10-minute sustained winds of 85 km/h (50 mph), while the JTWC reported 1-minute sustained winds of 95 km/h (60 mph).^[55][57] As the system subsequently started to weaken the system's low level circulation passed over Guam during March 15, while convection associated with the system passed over the Northern Mariana islands.^[14][58] Over the next couple of days the system moved westwards and continued to weaken, before it weakened into a tropical depression during March 17, as it moved into the Philippine area of responsibility, where it was named Betty by PAGASA.^[55][59] The JTWC stopped monitoring Bavi during March 19, after the system had weakened into a tropical disturbance, however, the JMA continued to monitor the system as a tropical depression, until it dissipated during March 21.^[55][57]

Bavi and its precursor tropical disturbance impacted eastern Micronesia, with strong to gale force winds of between 45–65 km/h (30–40 mph), reported on various atolls in the Marshall Islands.^[60] Considerable damage was reported on the islet of Ebeye while on the main atoll of Kwajalein, a small amount of tree damage was reported and several old steel structures were made too dangerous to use.^[60] Overall damages in the Marshall Islands were estimated at over US$2 million, while a fishing vessel and its crew of nine were reported missing during March 12.^[60] After impacting Eastern Micronesia, Bavi approached the Mariana Islands, with its circulation passing over Guam during March 15, where it caused the highest waves to be recorded on the island in a decade.^[58] Bavi also impacted the Northern Mariana Islands of Rota, Tinian and Saipan, where power outages were reported and five houses were destroyed.^[58][61] Total property damages within the Mariana Islands, were estimated at around US$150 thousand.^[58]

Typhoon Maysak (Chedeng)

Typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	March 26 – April 7
Peak intensity	195 km/h (120 mph) (10-min)  910 hPa (mbar)

A day after Bavi dissipated, a low-pressure area formed southwest of the Marshall Islands. It slowly drifted northwestward and became more organized over the next two days.^[62] The next day, the JMA started tracking the system as a tropical depression.^[63] On March 27, the JTWC started tracking the system as a tropical depression, and designated it 04W.^[64] Moving west-northwestward, the system's center became more consolidated with convective banding becoming wrapped into it. The JTWC upgraded 04W to a tropical storm the same day.^[65] The JMA followed suit later that day, when it was named Maysak.^[66] On March 28, Maysak developed an eye,^[67] and the JMA further upgraded it to a severe tropical storm.^[68] The eye became more well defined with deep convection persisting along the southern quadrant of the storm. The overcast became more consolidated,^[69] as the JMA upgraded Maysak to a typhoon on the same day.^[70] On March 29, Maysak rapidly intensified over a period of 6 hours, attaining 1-min maximum sustained winds of 230 km/h (145 mph), making it a Category 4 equivalent on the SSHWS.^[71] On the next day, Maysak further intensified into a Category 5-equivalent super typhoon. On April 1, the PAGASA stated tracking on the system, naming it as Chedeng.^[72]

Typhoon Maysak passed directly over Chuuk State in the Federated States of Micronesia on March 29, causing extensive damage. High winds, measured up to 114 km/h (71 mph) at the local National Weather Service office, downed numerous trees, power lines, and tore off roofs. An estimated 80–90 percent of homes in Chuuk sustained damage. Power to most of the island was knocked out and communication was difficult. Early reports indicated that five people had lost their lives.^[73]

Tropical Storm Haishen

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	April 2 – April 6
Peak intensity	65 km/h (40 mph) (10-min)  998 hPa (mbar)

By March 29, the JTWC started to monitor a tropical disturbance over the Marshall Islands, and later upgraded it to a "low chance" of being a cyclone two days later.^[74] Best track indicated that the system developed in to a tropical depression during April 2,^[75] but operationally the JMA did so in April 3.^[76] Shortly thereafter, the JTWC designated the system to 05W, when 1-minute winds stated that it had strengthened into a tropical depression.^[77] 05W started to organize with a slight consolidation of its LLCC and some convective banding; the JTWC upgraded 05W to a tropical storm.^[78] The JMA did the same later, when it was given the name Haishen.^[79] Haishen remained at low-level tropical storm strength until its center became fully exposed with its deepest convection deteriorating due to wind shear.^[80] Both the JMA and JTWC stopped monitoring the system during April 6, as it dissipated over open waters to the southeast of the Mariana Islands.^[75]

In Pohnpei State, 118 mm (4.66 in) worth of rain was recorded on the main island between April 2–3, however, there was no significant damage reported in the state.^[81] During April 4, the system passed to the north of Chuuk and Fananu in Chuuk State, while wind and rain associated with Haishen passed over the area.^[81] There were no direct measurements, of either the wind or rainfall made on Fananu, however, it was estimated that tropical storm force winds of 40–52 mph (64–84 km/h) were experienced on the island.^[81] It was also estimated that 100–150 mm (4–6 in) of rainfall fell on the island, while islanders confirmed that periods of heavy rain did occur.^[81] Haishen knocked down several fruit trees on Fananu, while the heavy rains were considered to be a positive blessing, as they restored water levels on the island, that had been damaged a few days earlier by Maysak.^[81] There were no reports of any other significant damage in the state, while property and crop damage were both estimated at 7005100000000000000♠US$100 thousand.^[81]

Typhoon Noul (Dodong)

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

On April 30, a tropical disturbance developed near Chuuk.^[82] On May 2, the JMA began to track the system as a weak tropical depression.^[83] The following day, the JMA upgraded the depression to a tropical storm and assigned the name Noul.^[84] On May 5, the JMA upgraded the system to a severe tropical storm while the JTWC upgraded it to a minimal typhoon.^[85] The following day, the JMA also upgraded Noul to a typhoon. Early on May 7, Noul entered the Philippine Area of Responsibility and was assigned the name Dodong by PAGASA.^[86] Later that day, the JTWC upgraded Noul to a Category 3 typhoon as a small eye had developed.^[87] At the same time, according to Jeff Masters of Weather Underground, Noul had taken on annular characteristics.^[88] Although Noul weakened to a Category 2 typhoon early on May 9, six hours later, the JTWC upgraded Noul back to a Category 3 typhoon, as its eye became clearer and well-defined. The JTWC upgraded Noul to a Category 4 super typhoon later that day after it began rapid deepening. On May 10, the JTWC further upgraded Noul to a Category 5 super typhoon, and the JMA assessed Noul with 10-minute sustained winds of 205 km/h (125 mph) and a minimum pressure of 920 mbar, its peak intensity.^[89][90] Later that day, Noul made landfall on Pananapan Point, Santa Ana, Cagayan.^[91] After making a direct hit on the northeastern tip of Luzon, the storm began to weaken, and the JTWC downgraded it to a Category 4 super typhoon.^[92] Subsequently, it began rapidly weakening and by May 12, it had weakened to a severe tropical storm.

Typhoon Dolphin

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

On May 3, a tropical disturbance south southeast of Pohnpei began to organize, and the JMA upgraded the disturbance into a tropical depression.^[93] Late on May 6, the JTWC started issuing advisories and designated it as 07W.^[94] On May 9, the JMA upgraded the depression into a tropical storm and named it Dolphin.^[95] The JMA further upgraded Dolphin to a severe tropical storm on May 12,^[96] and on the following day, the JTWC upgraded Dolphin to a typhoon.^[97] Six hours later, the JMA had followed suit.^[98] Over the next few days, Dolphin continued to intensify until it reached Category 5 super typhoon status on May 16. It weakened into a category 4 super typhoon 12 hours later, until it weakened into a category 4 equivalent typhoon after maintaining super typhoon status for 30 hours. Dolphin weakened further into a severe tropical storm on May 19, as the JTWC downgraded Dolphin into a tropical storm and issued their final warning. On May 20, the JMA issued their final warning, and the JTWC and the JMA declared that Dolphin had become an extratropical cyclone.^[99][100]

Tropical Storm Kujira

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	June 19 – June 25
Peak intensity	85 km/h (50 mph) (10-min)  985 hPa (mbar)

During June 19 the JMA started to monitor a tropical depression that had developed within the South China Sea about 940 km (585 mi) to the southeast of Hanoi, Vietnam.^[101] Over the next day the system gradually developed further before the JTWC initiated advisories on the system and designated it as Tropical Depression 08W.^[102] Deep convection obscured its low-level circulation center; however, upper level analysis indicated that 08W was in an area of moderate vertical windshear.^[103] On June 21, the JMA had reported that 08W had intensified into a tropical storm, naming it Kujira.^[104][105] Kujira slightly intensified and the JTWC finally upgraded the system to a tropical storm by June 22.^[106][107] In the same time, Kujira's circulation became exposed but convection remained stable.^[108] Therefore, according to both agencies, Kujira reached its peak intensity with a minimum pressure of 985 mbar later in the same day.^[109] Kujira would've been a severe tropical storm but because of displaced convection and moderate to high windshear, the storm began a weakening trend.^[110] The JTWC downgraded Kujira to a tropical storm as it was located in an area of very unfavorable environments early on June 23;^[111] however, by their next advisory it was reported that Kujira entered an area of warm waters and was upgraded back to tropical storm status.^[112] During June 24, Kujira made landfall on Vietnam to the east of Hanoi and weakened into a tropical depression.^[101] The system was subsequently last noted during the next day, as it dissipated to the north of Hanoi.^[101]

Although outside the Philippine area of responsibility, Kujira's circulation enhanced the southwest monsoon and marked the beginning of the nation's rainy season on June 23, 2015.^[113] Striking Hainan on June 20, Kujira produced torrential rain across the island with an average of 102 mm (4.0 in) falling across the province on June 20; accumulations peaked at 732 mm (28.8 in). The ensuing floods affected 7,400 hectares (18,300 acres) of crops and left ¥88 million (US$14.4 million) in economic losses.^[114] Flooding in northern Vietnam killed at least nine people, including eight in Sơn La Province, and left six others missing.^[115] Across the country, 70 homes were destroyed while a further 382 were damaged.^[116]

Typhoon Chan-hom (Falcon)

Typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	June 29 – July 13
Peak intensity	165 km/h (105 mph) (10-min)  935 hPa (mbar)

On June 25, the JTWC started to monitor a weak tropical disturbance embedded in the active ITCZ.^[117] Convection increased within the system as the JMA and the JTWC upgraded the system to a tropical depression on June 30 while it was located near the island of Kosrae.^[118][119] Later that day, the JMA upgraded the depression to a tropical storm and assigned the name Chan-hom.^[120] Although it was upgraded to a typhoon on July 1,^[121][122] increasing wind shear caused the system to weaken back into a tropical storm as it neared Guam.^[123][124]

On July 5, as it started to move north then northwest, Chan-hom showed good outflow aloft and low vertical windshear was within the area.^[125] Both agencies upgraded the storm to a typhoon again on July 6, as an eye developed.^{[126][127][128]} On July 7, PAGASA had reported that Chan-hom had entered their Area of Responsibility and was assigned the name Falcon.^[129] With a clear and defined eye and an expanding gale-force winds,^{[130][131][132]} both agencies classified Chan-hom as a Category 4 typhoon on July 9,^[133] with a 10-minute wind peak of 165 km/h (105 mph) and a minimum pressure of 935 millibars.^[134] On July 10, Chan-hom further weakened as an eyewall replacement cycle developed with moderate to high vertical windshear as it neared eastern China.^[135][136] Chan-hom made landfall southeast of Shanghai later that day.^[137] Because of cooler waters, Chan-hom weakened below typhoon status.^[138][139] During July 12, Chan-hom briefly transitioned into an extratropical cyclone, before it dissipated over North Korea during the next day.^[140]

Ahead of the typhoon's arrival in East China, officials evacuated over 1.1 million people.^[141] Total economic losses in Zhejiang amounted to ¥5.86 billion (US$944 million).^[142] Even though Chan-hom didn't affect the Philippines, the typhoon enhanced the southwest monsoon which killed about 4 people and damages of about $90 thousand.^[143]

Severe Tropical Storm Linfa (Egay)

Severe tropical storm (JMA)
Category 1 typhoon (SSHWS)
Duration	July 1 – July 10
Peak intensity	95 km/h (60 mph) (10-min)  980 hPa (mbar)

Just as soon as the tropics began to activate, the Intertropical Convergence Zone span four tropical systems across the Western Pacific, and a tropical disturbance had formed about 1015 km (882 mi) east-southeast of Manila during June 30.^[144] By July 1, the JMA started to track the system as it was classified as a tropical depression.^[145] During the next day, the JTWC followed suit and assigned the designation of 10W,^[146] while PAGASA named 10W as Egay.^[147] Few hours later, Egay strengthened into a tropical storm, with the name Linfa given from the JMA.^[148][149] Despite an exposed center, associated convection was being enhanced by its outflow, and Linfa intensified into a severe tropical storm.^[150][151] Late on July 4, Linfa made landfall over in Palanan, Isabela while maintaining its intensity.^[152][153] Linfa crossed the island of Luzon and emerged to the South China Sea while it began moving in a north-northwestward direction.^[154] By July 7, Linfa had become slightly better organized.^[155] PAGASA issued its final bulletin on Linfa (Egay) as it exited their area of responsibility.^[156] Linfa enetered in an area of favorable environments with good banding wrapping into its overall structure,^[157] and Linfa strengthened into a Category 1 typhoon by the JTWC as an eye developed and tightly-curved banding started to wrap its LLCC.^[158] During July 9, Linfa made landfall over in Guangdong province of China.^[159][160] Thereafter, Linfa experienced land interaction and rapidly weakened and both agencies issued their final advisories on July 10.^[161][162]

Across Luzon, Linfa damaged 198 houses and destroyed another seven. The storm damaged ₱34 million ($71,000 USD) worth of crops, and total damage reached ₱214.6 million ($4.8 million USD).^[163] Most of the power outages were repaired within a few days of Linfa's passage. According to preliminary estimates in southern China, economic losses from the storm reached ¥1.7 billion (US$284 million). A total of 288 homes collapsed and 56,000 people were displaced.^[164] A gust of 171 km/h (106 mph) was observed in Jieyang.^[165] A storm surge of 0.48 m (1.6 ft) was also reported along Waglan Island and rainfall reached a total of around 40 mm (1.6 in) in the territory.^[159]

Typhoon Nangka

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

On July 3, the JMA started to monitor a tropical depression over the Marshall Islands.^[166] Later that day, was designated as 11W by the JTWC as it started to intensify.^[167] The JMA followed suit of upgrading it to a tropical storm, naming it Nangka.^[168] After three days of slow strengthening, Nangka was upgraded to a severe tropical storm on July 6, because of favorable environments such as a symmetrical cyclone, an improving outflow and low vertical windshear .^[169][170] Shortly afterwards, rapid intensification ensued and Nangka was upgraded to a Category 2 typhoon 24 hours later.^[171][172] The intensification trend continued, and Nangka reached its first peak as a Category 4 typhoon as an eye developed.^[173][174]

Shortly after its first peak, Nangka slightly weakened and its eye became cloud-filled.^[175] Although some vertical wind shear initially halted the intensification trend, the storm resumed intensifying on July 9, and was upgraded to a Category 4 super typhoon with 1-minute sustained winds of 250 km/h (155 mph). In the same time, Nangka's structure became symmetrical and its eye re-developed clearly.^{[176][177][178]} The JMA also assessed Nangka's peak with 10-minute winds of 185 km/h (115 mph).^[179] Nangka maintained super typhoon strength for 24 hours before weakening to a typhoon on July 10 as it entered an area of some unfavorable environments.^[180] Nangka weakened to a Category 1-equivalent typhoon on July 11, but began strengthening again late on July 12, reaching a secondary peak as a Category 3-equivalent typhoon as its eye became clear once more.^[181][182] An eyewall replacement cycle interrupted the intensification the following day, and Nangka weakened because of drier air from the north.^[183][184] At around 14:00 UTC on July 16, Nangka made landfall over Muroto, Kōchi of Japan.^[185] A few hours later, Nangka made its second landfall over the island of Honshu, as the JMA downgraded Nangka's intensity to a severe tropical storm.^{[185][186][187]} Because of land reaction and cooler waters, Nangka's circulation began to deteriorate and was downgraded to a tropical depression by both agencies late on July 17.^[188][189] On July 18, both agencies issued their final warning on Nangka as it weakened to a remnant low.^[190][191]

On Majuro atoll in the Marshall Islands, high winds from Nangka tore roofs from homes and downed trees and power lines. Nearly half of the nation's capital city of the same name were left without power. Tony deBrum, the Marshall Island's foreign minister, stated "Majuro [is] like a war zone."^[192] At least 25 vessels in the island's lagoon broke loose from or were dragged by their moorings. Some coastal flooding was also noted.^[192]

Typhoon Halola (Goring)

Typhoon (JMA)
Category 2 typhoon (SSHWS)
Duration	July 13 (Entered basin) – July 26
Peak intensity	150 km/h (90 mph) (10-min)  955 hPa (mbar)

During July 13, Tropical Storm Halola moved into the Western Pacific basin from the Central Pacific basin, and was immediately classified as a severe tropical storm by the JMA.^[193] Over the next day the system moved westwards and gradually intensified, before it was classified as a typhoon during the next day.^[193][194] Later that day, both the JMA and JTWC reported that Halola reached peak intensity as a Category 2 typhoon.^[195][196] However weakening convection and moderate vertical windshear caused the typhoon to weaken on July 15.^[197][198] Halola further weakened to a tropical depression as the JMA issued its final advisory on July 18; however, the JTWC continued tracking Halola.^[199][200]

On July 19, the JMA re-issued advisories and Halola showed signs of further intensification.^[201][202] An improved convective signature, expanding moisture field and shallow banding wrapped into the system prompted both agencies to upgrade it to a tropical storm early on July 20.^[203][204] Halola intensified into a typhoon again the next day, as the typhoon became more symmetrical than before.^{[205][206][207]} By July 22, Halola reached its second peak intensity as a Category 2 typhoon, but this time it was a little stronger with 10-minute sustained winds of 150 km/h (90 mph).^{[193][208][209]} PAGASA reported that Halola entered their Area of Responsibility receiving the name Goring early on July 23.^[210][211] On the next day, Halola encountered northeasterly vertical windshear as the system started to weaken.^[212] During July 25 and 26, Halola weakened to tropical storm strength and passed the southwestern Japanese Islands.^[213] At around 09:30 UTC on July 26, Halola made landfall over Saikai, Nagasaki of Japan.^[214] The system was subsequently last noted later that day as it dissipated in the Sea of Japan.^[193]

Throughout the Daitō Islands, sugarcane farms were significantly affected by Typhoon Halola, resulting damage of about 154 million Japanese yen ($1.2 million USD).^[215]

Tropical Depression 12W

Tropical depression (JMA)
Tropical storm (SSHWS)
Duration	July 23 – July 25
Peak intensity	65 km/h (40 mph) (1-min)  1008 hPa (mbar)

During July 23, the JMA and JTWC started monitoring Tropical Depression 12W, that had developed to the northeast of Manila, Philippines.^[216][217] Over the next day the system moved towards the north-northeast along the subtropical ridge, in an environment that was considered marginal for further development.^[218] During the next day, despite Dvorak estimates from various agencies decreasing because of a lack on convection surrounding the system, the JTWC reported that the system had become a tropical storm, with peak 1-minute sustained winds of 65 km/h (40 mph).^[219][220] This was based on an image from the advanced scatterometer, which showed winds of 65–75 km/h (40–45 mph) along the system's western periphery.^[219] The system subsequently directly interacted with Typhoon Halola, before increased vertical wind shear and subsidence from the interaction caused the depression to deteriorate.^[221][222] As a result, the system's low level circulation became weak and fully exposed, with deep convection displaced to the system's western half, before it was last noted during July 25, as it dissipated to the east of Taiwan.^[220][221]

Typhoon Soudelor (Hanna)

Typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	July 29 – August 11
Peak intensity	215 km/h (130 mph) (10-min)  900 hPa (mbar)

During July 29, the JMA reported that a tropical depression had developed, about 1,800 km (1,120 mi) to the east of Hagåtña on the island of Guam.^[223] Over the next day the system moved westwards under the influence of the subtropical ridge of high pressure and quickly consolidated, in an environment that was marginally favorable for further development.^[224] As a result, the JTWC initiated advisories and designated it as Tropical Depression 13W during July 30.^[224] In the same day, Soudelor showed signs of rapid intensification as a central dense overcast obscured its LLCC.^[225] Therefore, the JMA upgraded Soudelor to a severe tropical storm on August 1. Intensification continued, and both agencies upgraded Soudelor to a typhoon the next day. On August 3, Soudelor further deepened into a Category 5 super typhoon with 285 km/h (180 mph) 1-minute sustained winds, and the JMA assessed Soudelor with 10-minute sustained winds of 215 km/h (130 mph) and a minimum central pressure of 900 millibars, making Soudelor the strongest typhoon since Typhoon Vongfong at the time.^[226] The typhoon maintained its peak intensity for 18 hours until it began to weaken gradually on 15:00 UTC on August 4.^[227] The next day, PAGASA noted that Soudelor had entered the Philippine area of responsibility, naming it Hanna.^[228] On August 7, Soudelor re-intensified into a Category 3-equivalent typhoon as it entered an area of favorable conditions.^[229][230]

On August 2, Soudelor made landfall on Saipan as a Category 4 typhoon resulting in severe damage, with early estimates of over $20 million (2015 USD) in damages.^[231] On August 8, at around 4:40 AM, Soudelor made landfall to the north of Hualien as a Category 3 storm.

Tropical Depression 14W

Tropical depression (JMA)
Tropical depression (SSHWS)
Duration	August 1 – August 5
Peak intensity	<55 km/h (35 mph) (10-min)  1008 hPa (mbar)

During August 1, the JMA reported that a tropical depression had developed, about 940 km (585 mi) to the southeast of Tokyo, Japan.^[232] The system had a small low level circulation center, which was partially exposed, with deep atmospheric convection located over the systems southern quadrant.^[233] Overall the disturbance was located within a favourable envioroment for further development, with favourable sea surface temperatures and an anticyclone located over the system.^[233] During the next day, the system was classified as Tropical Depression 14W by the JTWC, while it was located about 740 km (460 mi) to the southeast of Yokosuka, Japan.^[234]

Because of a well-defined but an exposed low-level circulation center with deep flaring convection over the storm's eastern periphery, the JTWC upgraded the system to a tropical depression, designating it as 14W.^[235] The JTWC issued its final warning on the system during August 4, after an image from the advanced scatterometer showed that 14W had a weak circulation that had fallen below their warning criteria.^[236] However, the JMA continued to monitor the system, before it was last noted during the next day while it was affecting Kansai region.

Tropical Storm Molave

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	August 6 – August 14
Peak intensity	85 km/h (50 mph) (10-min)  985 hPa (mbar)

During August 6, the JMA started to monitor a tropical depression that had developed about 680 km (425 mi) to the northeast of Hagåtña, Guam.^[237] The system was located within an area that was considered moderately favorable for further development, with low to moderate vertical windshear and a good outflow.^[238] Over the next day, convection wrapped around the system's low-level circulation and the system gradually consolidated, before a tropical cyclone formation alert was issued by the JTWC later during that day.^[238][239]

Early on August 7, the JTWC upgraded the system to Tropical Depression 15W.^[240] On the same day, 15W gradually intensified, and was named Molave by the JMA.^[241] The JTWC kept Molave's intensity to a weak tropical depression of 25 knots because of poorly and exposed circulation.^[242][243] However the JTWC upgraded Molave to a tropical storm on August 8, as deep convection and tropical storm force winds were reported in the northwestern side of the system.^[244] During the next day, Molave entered in an area of marginally favorable conditions with low to moderate vertical wind shear, with its circulation becoming partially exposed.^[245] Hours later, deep convection rapidly diminished and the JTWC declared it to be a subtropical storm and issued its final advisory.^[246] Despite weakening to a subtropical storm, the JMA still classified Molave at tropical storm strength.^[237]

On August 11, according to the JTWC, strengthened back into a tropical storm and re-issued advisories.^[247][248] Molave's convection weakened due to strong shear as its LLCC became fully exposed.^[249] Later that day, Molave weakened to minimum tropical storm strength.^[250] On August 13, deep convective was fully sheared and Molave drifted deeper into the mid-latitude westerlies.^[251] The JTWC later issued its final warning as environmental analysis revealed that Molave is now a cold-core extratropical system.^[252] Early on August 14, the system degenerated into an extratropical cyclone, before it was last noted by the JMA moving out of the Western Pacific during August 18.^[237]

Typhoon Goni (Ineng)

Typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	August 13 – August 25
Peak intensity	185 km/h (115 mph) (10-min)  930 hPa (mbar)

On August 13, the JMA started to monitor a tropical depression that had developed, about 685 km (425 mi) to the southeast of Hagåtña, Guam.^[253] By the next day, the depression started to organize and was designated as 16W by the JTWC.^[254] Several hours later, deep convection had improved and has covered its LLCC and both agencies upgraded 16W to a tropical storm, naming it Goni.^[255][256] During the night of August 15, the JMA upgraded Goni to a severe tropical storm as windshear started to calm whilst deep convective banding wrapping into its circulation.^[257][258] By the next day, satellite imagery depicted a developing eye with an improved tightly curved banding which upper-level analysis revealed that low shear and an improving environment.^[259] Goni intensified into a typhoon by both agencies a few hours later.^[260][261] Early on August 17, satellite imagery depicted a small-pinhole eye as Goni underwent rapid intensification and was upgraded rapidly to a Category 4 typhoon and reached its first peak intensity.^[262] Slightly thinning convective banding and low to moderate wind shear caused Goni to weaken to a Category 3 typhoon.^[263] Goni maintained that intensity while moving westward and entered the Philippine's area which PAGASA gave the name Ineng,^[264] until on August 19, Goni entered an area of favorable environments. Goni had maintained an overall convective signature with tightly curved banding wrapping into a 28 nautical-mile eye.^[265] The JTWC later re-upgraded Goni back at Category 4 typhoon status early on August 20 as it neared the northeastern Philippine coast.

Typhoon Atsani

Typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	August 14 – August 25
Peak intensity	185 km/h (115 mph) (10-min)  925 hPa (mbar)

Shortly after beginning to track the precursor to Goni, the JTWC started to track another tropical disturbance approximately 157 km (100 mi) north-northwest of Wotje Atoll in the Marshall Islands.^[266] Deep convection with formative bands surrounding the system's circulation caused both the JMA and the JTWC to upgrade it to a tropical depression, also designating it as 17W on August 14.^[267][268] Later that day, both agencies upgraded 17W to a tropical storm, with the JMA naming it Atsani.^[269] On August 16, both agencies upgraded Atsani to a typhoon as it was found in microwave imagery that an eye was developing.^[270][271] Improved convective banding and a ragged eye formed by early the next day.^[272] That night, the typhoon's eye became well-defined and the JTWC assessed Atsani's intensity an equivalent to a Category 3 storm.^[273] Deepening of convection continued until early on August 18, when the JTWC upgraded Atsani to a Category 4 typhoon.^[274] By August 19, very low vertical windshear and excellent radial outflow were in place. A symmetric core and extra feeder bands prompted the JTWC to upgrade it to a super typhoon.^[275] Later that day, satellite imagery showed that Atsani was more symmetric and deep with feeder bands wrapping tighter into an expanded 34 nautical-mile diameter eye. Therefore, the JTWC upgraded Atsani further to a Category 5 super typhoon and it attained its peak intensity of 1-minute sustained winds of 260 km/h (160 mph).^[276]

Atsani moved in a northwestward direction as it was later downgraded to a Category 4 super typhoon intensity on August 20^[277] and at typhoon category later that day as it weakened further.^[278] On August 21, satellite imagery indicated that convection over Atsani was decreasing and an eyewall replacement cycle occurred, therefore, the JTWC downgraded Atsani further to a Category 3 typhoon.^[279][280] Vertical windshear started to intensify to a moderate scale and dry air persisted within the north and western part of Atsani and its eyewall began to erode.^[281][282] By the next day, significant dry air prohibited intensification and multispectural satellite imagery indicated a warming in the typhoon's cloud tops prompted the JTWC to downgrade it to a Category 1 typhoon.^[283] Atsani maintained that intensity as it started to move in a northeastward direction and began to interact with higher vertical wind shear associated by the mid-latitude baroclinic zone late on August 23.^[284] On August 24, both the JMA downgraded Atsani to a severe tropical storm.^[285] A few hours later, the JTWC followed suit of downgrading the typhoon to tropical storm strength.^[286] The JTWC issued its final warning later that day;^[287] During August 25, Atsani became an extra-tropical cyclone, while it was located about 1,650 km (1,025 mi) to the northeast of Tokyo, Japan. The system was subsequently last noted as it dissipated during August 27.^[288]

Typhoon Kilo

Typhoon (JMA)
Category 2 typhoon (SSHWS)
Duration	September 1 (Entered basin) – September 11
Peak intensity	155 km/h (100 mph) (10-min)  945 hPa (mbar)

During September 1, Hurricane Kilo moved into the basin from the Central Pacific and was immediately classified as a typhoon by the JMA and the JTWC.^[289] During the next day, Kilo started to encounter moderate vertical wind shear and started weakening.^[290] Even though Kilo lost its eye structure and its circulation became elongated, the JTWC raised Kilo's intensity on September 3.^[291] Kilo regained strength with deepening and cooling of cloud tops as it was classified at low-end Category 2 strength for a brief time.^[292][293] By September 4, moderate to high southwesterly wind shear prohibited development.^[294][295] Convective band wrapping into a central dense overcast made Kilo to intensify back to a high-end of Category 1 status.^[296] Later that day, Kilo developed an eye again; however, the typhoon maintained its same intensity,^[297] and later became ragged on September 6.^[298]

On September 7, the JTWC estimated 1-minute sustained winds of 165 km/h (105 mph), which again made Category 2 typhoon intensity for a brief time.^[299] Later that day, Kilo started to weaken as its eye became irregular with eroding convection over the southern semi-circle of the typhoon.^[300] Deep convection started to decay, as the JTWC reported a few hours later.^[301] Late on the next day, the Kilo's convective signature began to struggle due to drier air wrapping to its LLCC and the JTWC lowered Kilo's intensity as it was classified with 65 knot winds.^[302] On September 9, the JMA downgraded Kilo to a severe tropical storm.^[303] The JTWC followed suit several hours later as its LLCC became fully exposed as cool dry air enveloped much of the system.^[304] Despite the continuation of banding wrapping to its center, deep convection started to erode and Kilo was located in an area of strong shear.^[305] Thereafter, Kilo began to undergo extratropical transition as the JTWC issued its final warning early on September 11.^[306][307] Hours later, the JMA issued its final warning and reported that Kilo had transitioned into an extratropical cyclone.^[308] The extratropical remnants of Kilo moved as it affected the Kamchatka Peninsula and the Aleutian Islands, absorbing the extratropical remnants of Severe Tropical Storm Etau along the way. The system moved out of the basin on September 13 and was last noted over Alaska roughly two days later.^[289]

Severe Tropical Storm Etau

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

On September 2, a tropical disturbance developed 560 km (350 mi) to the northwest of the island of Guam. The system moved in a northwesterly track until it organised with deep convection,^[309] therefore, it was then classified as a weak tropical depression by the JMA on September 5.^[310] However post-analysis showed that Etau formed early on September 6.^[311] The next day, the JTWC issued a TCFA on the system as in the same time the JMA started issuing advisories on it.^[312][313] Later in the same day, the JMA upgraded the depression to a tropical storm, receiving the name Etau whilst the JTWC designated it as 18W.^[314][315] Formative bands wrapped around its ragged and ill-defined LLCC.^[316] Satellite image revealed that Etau had convection increasing near its center and low vertical wind shear was surrounding the storm,^[317] causing the JTWC to upgrade it to a tropical storm.^[318] A banding eye feature developed on September 8,^[319] and therefore the JMA upgraded Etau to a severe tropical storm.^[320] Upper-level analysis indicated that Etau was over in an environment of very high vertical wind shear due to a mid-latitude trough. However Etau maintained its intensity.^[321] Late on the same day, Etau's convection rapidly flared up briefly as it was beginning to transition to an extratropical cyclone embedded over the baroclinic zone and the JTWC assessed Etau's intensity to 55 knots.^[322] Early on September 9, Etau made landfall over central Honshu and in the same time, Etau weakened to tropical storm strength whilst the JTWC issued its final advisory.^[323][324] The JMA finally issued its final bulletin on Etau and became extratropical later that day.^[325] However the extratropical remnants of Etau moved in a poleward direction while affecting eastern Russia and finally interacted with and was absorbed by another extratropical system that was formerly Typhoon Kilo on September 11.^[311]

When Etau affected Japan, particularly Honshu, during September 8–9, the storm brought widespread flooding. Record rains fell across many areas in eastern Japan, with more than 12 in (300 mm) reported in much of eastern Honshu.^[326] The JMA director, Takuya Deshimaru, called the event "unprecedented".^[327] The heaviest rains fell across Tochigi Prefecture where 668 mm (26.3 in) was observed in Nikkō, including 551 mm (21.7 in) in 24 hours. Kanuma saw 444 mm (17.5 in) during 24 hours, more than double its previous record. Farther north in Sendai, 350 mm (14 in) of rain was observed.^[326] Toba, Mie saw 75.5 mm (2.97 in) in an hour.^[328] Fukushima Prefecture saw its heaviest rains in 50 years, with more than 300 mm (12 in) observed during a 48‑hour span.^[329] Nearly 3 million people were forced to leave their homes. In total, eight people were killed and total damages were amounted to ¥11.7 billion (US$97.8 million).^[330] On September 10, the remnants of Etau brought some rainfall and gusty winds over in the Russian Far East region.^[331]

Tropical Storm Vamco

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	September 13 – September 15
Peak intensity	65 km/h (40 mph) (10-min)  998 hPa (mbar)

On September 10, a tropical disturbance formed within the monsoon 560 km (350 mi) west of Manila, Philippines over the South China Sea and was classified as a low by the JTWC on the next day.^[332] The disturbance meandered for a few days and was later classified as a tropical depression by the JMA on September 13.^[333] With flaring deep convection surrounding its LLCC, the JTWC started issuing bulletins and was assigned the designation 19W.^[334][335] Thereafter, both the JMA and the JTWC upgraded 19W to a tropical storm, naming it Vamco.^[336][337] On September 14, deep convection slightly weakened and became displaced near its center, however environments are still favorable at this moment.^[338] A few hours later, the JTWC reported that according to animations, the center of Vamco became partially exposed and wind shear inhibited further development, which favorable conditions started to fade.^[339] Therefore, the JTWC issued its final warning.^[340] The JMA later downgraded Vamco to a tropical depression and issued their final advisory early on September 15.^[341] The remnants of Vamco continued to move in a westward direction inland and crossed the 100th meridian east on September 16.

Vamco made landfall south of Da Nang, Vietnam, which caused floods across parts of the country.^[342] Flooding in Vietnam killed 11 people.^[343] Losses to fisheries in the Lý Sơn District exceeded ₫1 billion (US$44,500).^[344] Damage to the power grid in Vietnam reached ₫4.9 billion (US$218,000).^[345] In Quảng Nam Province, Vamco caused moderate damage. In Duy Xuyên District, agricultural losses exceeded ₫2 billion (US$89,000) and in Nông Sơn District total damage is ₫1 billion (US$44,500).^[346] Officials in Thanh Hóa Province estimated total damages from the flooding by the storm had reached ₫287 billion (US$12.8 million).^[347] Flooding in Cambodia affected thousands of residents and prompted numerous evacuations.^[348] The remnants of Vamco triggered flooding in 15 provinces across Thailand and killed two people.^[349][350] At least 480 homes were damaged and losses exceeded ฿20 million (US$561,000).^[350] Two fishermen died after their boat sank during the storm off the Ban Laem District while a third remains missing.^[351]

Typhoon Krovanh

Typhoon (JMA)
Category 3 typhoon (SSHWS)
Duration	September 13 – September 21
Peak intensity	155 km/h (100 mph) (10-min)  945 hPa (mbar)

At the same time when 19W intensified into Tropical Storm Vamco, another tropical disturbance was monitored by both the JMA and JTWC about 806 km (500 mi) east of Andersen Air Force Base, Guam.^[352] The JTWC issued a TCFA on the system later that day.^[353] On September 14, the JTWC upgraded the system to a tropical depression, designating it as 20W.^[354] Due to an increase of deep convection obscuring its center, both agencies upgraded 20W to Tropical storm Krovanh by the next day.^[355][356] On September 16, Krovanh showed signs of increasing organization and deep convection wrapping into the storm's center as the JMA upgraded Krovanh to a severe tropical storm.^[357][358] Late on the same day, microwave imagery showed tightly-curved bands wrapping into a well-defined microwave eye and warm sea-surface temperatures within Krovanh's area are conductive for intensification.^[359] With these conditions, both agencies upgraded Krovanh to typhoon status.^[360][361] Krovanh later entered in an area of very favorable environments as wind shear started to decrease.^[362] The JTWC upgraded Krovanh to a Category 2 typhoon on September 17 as an eye developed and the typhoon became more symmetric, later peaking as a Category 3 typhoon.^[363] The convective core started to struggle due to dry air over the western periphery and Krovanh moved in an area of increasing vertical windshear.^[364][365]

Due to deteriorating conditions, Krovanh weakened to a Category 2 typhoon.^[366] Krovanh further weakened to a Category 1 typhoon after its convection diminished.^{[367] [368]} On September 19, Krovanh was in an area of unfavorable environments with strong shear weakening its deepest convection. Both the JMA and the JTWC downgraded Krovanh to a severe tropical storm.^[369][370] On September 20, the LLCC of Krovanh became fully exposed and the JMA later downgraded Krovanh to a tropical storm.^[371][372] The JTWC issued their final warning.^[373] The JMA later issued its final warning on Krovanh on September 21, as it transitioned into an extratropical cyclone.^[374][375] The extratropical remnants of Krovanh lingered to the east of Japan for a few days with a cyclonic loop before turning to the northeast.^[375]

Typhoon Dujuan (Jenny)

Typhoon (JMA)
Category 4 super typhoon (SSHWS)
Duration	September 19 – September 30
Peak intensity	205 km/h (125 mph) (10-min)  925 hPa (mbar)

The JTWC identified a tropical disturbance on September 17 and assessed a low probability of tropical cyclogenesis within 48 hours about 220 km (135 mi) east-southeast of Ujelang Atoll.^[376] On September 20, the JTWC issued the TCFA.^[377] Late the next day, gradual development occurred like persistent deep symmetric convection, and both agencies upgraded the system to a tropical depression also designating it as 21W.^{[378][379][380]} On September 22, wind shear caused the circulation of 21W to become exposed, but flaring deep convection occurred to the west of the circulation.^[381] Despite the wind shear, deep convection continued and the JMA upgraded 21W to a tropical storm, naming it Dujuan.^[382] The JTWC did the same early on September 23.^[383] Dujuan entered the Philippine area of responsibility and was named Jenny.^[384] At the same time, Dujuan slowly intensified, with satellite imagery showing smaller vortices surrounding a larger circulation and shallow banding forming its LLCC.^[385][386] On the next day, Dujuan entered a favorable environment and the JMA upgraded Dujuan to a severe tropical storm.^[387][388] With a convective structure and tightly curved banding wrapping around the eye, both agencies assessed Dujuan's intensity at typhoon strength.^[389][390] On September 26, tightly curved banding wrapping into a large eye caused Dujuan to intensify into a Category 2 typhoon.^[391] Deep convective banding wrapping into an expanding eye occurred later that day.^[392] Despite the JTWC slowly upgrading Dujuan's intensity still at Category 2 strength, satellite imagery showed an improved and intense convective core structure with cooler cloud tops surrounding a large 38-nm wide eye and was therefore upgraded to a Category 3 typhoon.^[393][394]

Dujuan started to undergo explosive intensification and JTWC raised Dujuan's intensity to Category 4 typhoon strength early on September 27.^[395] Later that day, Dujuan rapidly reached peak intensity with 1-minute sustained winds of 240 km/h (150 mph) and a minimum pressure of 925 mbar. The typhoon became more symmetric, taking on annular characteristics, while featuring a 43-nm wide eye.^[396][397] With favorable environments remaining stabled such as excellent radial outflow, deep convective banding and very low shear, Dujuan maintained its intensity with its eye peaking 46-nm wide.^[398][399] However, on September 28, Dujuan's large symmetrical eye began to be cloud-filled as it interacted with the mountainous country of Taiwan, with the JTWC lowering its intensity.^[400] Enhanced infrared satellite imagery later showed Dujuan rapidly eroding as the typhoon weakened to a Category 3 typhoon while making landfall over Nan'ao, Yilan.^[401][402] Dujuan further weakened to a Category 2 typhoon and by the morning of September 29, the JTWC issued their final warning.^[403][404] In the same time, while making its second landfall over Xiuyu District, Putian of Fujian,^[405] the JMA downgraded Dujuan to a severe tropical storm,^[406] then a tropical storm later as it rapidly deteriorate over land.^[407]

Over the next day the system moved northwards before it was last noted during September 30, as it dissipated over the Chinese province of Jiangxi.^[408]

Typhoon Mujigae (Kabayan)

Typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	September 30 – October 5
Peak intensity	155 km/h (100 mph) (10-min)  950 hPa (mbar)

On September 28, a cluster of thunderstorms developed into a tropical disturbance near Palau. With more organization, the JMA classified the system as a tropical depression early on September 30.^[409] On the next day, the PAGASA upgraded it to a tropical depression, assigning it the name Kabayan.^[410] The JTWC designated it as 22W later that day and started issuing warnings.^[411] All three agencies later classified Kabayan as a tropical storm, with the JMA naming it Mujigae.^{[412][413][414]} By October 2, Mujigae made landfall over Aurora province and the JTWC later downgraded the system to a tropical depression.^[415] Later, Mujigae reemerged into the South China Sea, where warm sea-surface temperatures favored development. The JTWC upgraded it back to a tropical storm whilst the JMA upped the intensity to severe tropical storm strength.^[416][417] On the next day, favorable conditions ensued as tightly-curved banding started to wrap into a developing eye, prompting the JMA and the JTWC to classify Mujigae as a typhoon.^[418][419] On October 4, Mujigae intensified into a Category 2 typhoon as it showed a symmetric signature and deep convective banding.^[420] With very favorable environments, Mujigae explosively intensified into a Category 4 typhoon as cooling clouds tops were recorded surrounding its eye feature. At the same time, Mujigae made landfall over Zhanjiang and briefly reached peak intensity at 1-minute sustained winds of 215 km/h (130 mph), however pressure according to the JMA remained rather shallow of 960 mbar.^[421][422] A few hours later, the JTWC issued its final warning as Mujigae rapidly weakened over land.^[423] Later in the same day, the JMA downgraded Mujigae to a severe tropical storm, then a tropical storm.^[424][425] The JMA issued its final advisory on Mujigae as it further weakened to a tropical depression early on October 5.^[426]

In the Philippines, no fatalities were reported; however the cost of damages were reported at PHP1.12 million (US$24.05 thousand).^[427] When Mujigae made landfall over southern China, a tornado struck Foshan and killed three people. However, as of October 7, a total of twenty were reported dead.^[428]

Severe Tropical Storm Choi-wan

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

On October 1, the JMA started to monitor a tropical depression near Wake Island.^[429] By the next day, the system's circulation became expansive as the JMA upgraded the depression to a tropical storm, naming it Choi-wan, however the JTWC still issued a TCFA.^[430][431] The JTWC later started issuing advisories, giving the designation 23W, and then a tropical storm by October 2, due to an improved deep convection banding with a large windfield.^[432][433] Despite favorable conditions, Choi-wan maintained its intensity as a weak system due to a large and very broad circulation; mesovortices were seen rotating cyclonically in its center.^[434] On October 4, Choi-wan consolidated better with an increase of deep convection as the storm gained strength and expanded in size.^[435] With a ragged eye, the JMA upgraded Choi-wan to a severe tropical storm.^[436] On October 6, the JTWC classified and upgraded the storm to a Category 1 typhoon as tightly-curved banding was wrapping to its LLCC.^[437] Later that day, according to 1-minute wind speeds, Choi-wan reached peak intensity 130 km/h (80 mph) with an elongated microwave eye feature.^[438]

On October 7, Choi-wan started to weaken in a slow trend corresponding to southwesterly shear and due to this, Choi-wan's center became cloud-filled.^[439][440] Later that day, the JTWC issued its final warning as Choi-wan moved further northward with increasing and high vertical wind shear and was downgraded to a strong tropical storm.^[441][442] According to the JMA, with Choi-wan becoming extratropical early on October 8, they issued their final warning and stated that Choi-wan reached peak strength with a minimum pressure of 955 hPa still as a severe tropical storm, without reaching typhoon intensity.^[443][444]

Typhoon Koppu (Lando)

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

On October 11, an area of convection persisted approximately 528 km (328 mi) north of Pohnpei and was deemed to have a low chance of tropical cyclone formation within 24 hours by the JTWC.^[445] Hours later, the JMA upgraded the system to a weak tropical depression.^[446] Late the next day, the JTWC issued a TCFA whilst the JMA started issuing warnings.^[447][448] The JTWC later upgraded the system and was classified as Tropical Depression 24W on October 13.^[449] Despite some shear, 24W deepened with formative bands wrapped into a tight circulation already obscured by a central dense overcast.^[450] Therefore, the JMA named the system Koppu as winds were reported at tropical storm strength.^[451][452] Koppu, while moving westward, showed a partially exposed circulation due to continued shear, however intensities were raised slightly.^[453] Later, PAGASA started issuing advisories on Koppu as it entered their area of responsibility and was named Lando.^[454] On October 15, the JMA upgraded Koppu to a severe tropical storm as good cloud banding started to wrap into an obscured LLCC.^[455][456] Koppu later intensified into a typhoon as the system was in a favorable environment with less shear, with convection deepening around an apparent microwave eye.^[457][458] By October 16, the JTWC classified Koppu as a Category 2 typhoon.^[459]

With SSTs over 31 °C over the Philippine Sea, intensification continued and on October 17, Koppu developed an eye and was raised to Category 3 typhoon intensity,^[460] then in their next advisory, a Category 4.^[461] Six hours later, Koppu explosively intensified and reached peak intensity as a Category 4 super typhoon with a 20-nautical-mile sharp eye and a pressure of 925 hPa .^[462][463] Initially, the JTWC forecasted Koppu to reach Category 5 intensity, however the typhoon made landfall earlier than expected in the eastern Philippines.^[464]

Typhoon Champi

Typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	October 13 – October 25
Peak intensity	175 km/h (110 mph) (10-min)  930 hPa (mbar)

During October 13, the JMA and the JTWC reported that Tropical Depression 25W, had developed to the northeast of Pohnpei State in the Marshall Islands.^[465][466] During the early hours of October 14, 25W slightly organized and the JMA upgraded 25W to a tropical storm, naming it Champi.^[465][467] Despite deep convection had not significantly intensified, the JTWC also upgraded the system to a tropical storm.^[468][469] Moving in a west-northwestward direction at that time, Champi was seen moving into favorable environments with low shear, steadily intensifying with deepened convection.^[470] Champi was later deemed as a severe tropical storm by the JMA, while in the same time the storm was impacting the Mariana Islands.^[465]

Early on October 16, Champi intensified to a typhoon as wind shear weakened.^[465][471] Several hours later, Champi formed an eye and significantly intensified into a Category 2 typhoon by the JTWC.^[472][473] The JTWC states that Champi's eye was surrounded with a deep convective core,^[474] and bands wrapped into its center, making Champi to a Category 3 typhoon.^[475] Moving in a northward direction, Champi extremely deepened with an intense convective core.^[476] Therefore, Champi reached peak intensity as a Category 4 super typhoon with 10-minute sustained winds of 165 km/h (105 mph) and a pressure of 930 mbar on October 18.^[477] However its intensity was dropped slightly by the JTWC in post-analysis and considered only a Category 4 typhoon, with a pressure of 935 mbar.^[465] By October 19, Champi started to weaken as a weakening asymmetric convective structure surrounded the eye and dry air started to wrap into the storm's center.^[478][479] After a day of a slow downward trend of intensity, convection deepened again and conditions became favorable for re-development.^[480] Champi peaked once more as a strong typhoon, but as a Category 3 on October 22, until it started to interact with the strong mid-latitude westward flow.^[481] Champi, for the last time, started to weaken due to strengthening shear on October 23.^[482] Convection rapidly decayed over Champi and the JMA downgraded it to a severe tropical storm.^[465] Both the JTWC and the JMA issued their final advisory as Champi became extratropical on October 25.^{[465][483][484]} The extratropical remnants crossed the basin on October 26, and fully dissipated on October 28 south of Alaska.^[465]

Tropical Depression 26W

Tropical depression (JMA)
Subtropical depression (SSHWS)
Duration	October 20 – October 22
Peak intensity	55 km/h (35 mph) (10-min)  1004 hPa (mbar)

On October 20, the JMA started to monitor a tropical depression that had developed within a moderate environment for further development, about 400 km (250 mi) to the southwest of Wake Island.^[485][486] The depression's low level circulation center was fully exposed, while isolated amounts of deep atmospheric convection flared over the systems southwestern quadrant.^[486] Over the next day atmospheric convection over the system increased as it moved north-westwards, which prompted the JTWC to issue a tropical cyclone formation alert.^[487] The JTWC subsequently initiated advisories on the system and classified it as Tropical Depression 26W during October 22, while it was located about 1,430 km (890 mi) to the east of Iwo To, Japan.^[488] At this time the main convection was being sheared to the southwest, which exposed a broad and elongated low level circulation.^[488] During that day the system interacted with the mid-latitude westerly flow and transitioned into an extra tropical cyclone, as it rounded the edge of a subtropical ridge of high pressure.^[489][490] During their post-analysis of the system, the JTWC determined that the system was a subtropical depression rather than a tropical depression.^[491]

Typhoon In-fa (Marilyn)

Typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	November 16 – November 27
Peak intensity	175 km/h (110 mph) (10-min)  935 hPa (mbar)

During November 16, the JMA started to monitor a tropical depression, that had developed about 200 km (125 mi) to the southeast of Kosrae in the Federal States of Micronesia.^[492] Over the next day the system moved north-westwards within a favourable environment for further development, before it was classified as Tropical Depression 27W by the JTWC early on November 17.^[493][494]

Six hours later, deepening of convection occurred and based on the aforementioned satellite imagery, 27W intensified into a tropical storm by the JTWC.^[495] The JMA followed suit shortly after and was named In-fa.^[496] By November 18, gradual strengthening ensued as the JMA upgraded In-fa to a severe tropical storm.^[497] Later, a brief eye developed and the JTWC upgraded In-fa to a Category 1 typhoon.^[498] But despite favorable environments, the eye became cloud-filled and convection weakened as both agencies downgraded In-fa to a tropical storm.^[499][500] The JTWC upgraded In-fa back to a typhoon and the JMA to a severe tropical storm after when satellite imagery showed a consolidating and compact LLCC, obscured beneath a developing central dense overcast.^[501][502]

By November 20, In-fa started to expand and deepen with feeder bands wrapped into the LLCC; the JTWC upgraded In-fa to a Category 3 typhoon.^[503][504] The JTWC assessed In-fa's intensity to a low-end of a Category 4 when its eye became better organized and symmetric early on November 21.^[505] In-fa maintained its peak intensity shortly thereafter when it had 10-minute sustained winds of 175 km/h (110 mph) and a pressure of 935 mbar.^[492][506] Regardless of the expansion of convection banding, its eye became cloud-filled again and weakening became obvious with the lack of organization; In-fa weakened to a Category 3 typhoon.^[507] On November 22, PAGASA has declared that In-fa had entered their area of responsibility, receiving the local name Marilyn.^[508][509] In the same time, In-fa continued to deteriorate and its convective structure and core became elongated,^[510] whereas the typhoon was already a Category 2 typhoon.^[511] Late on November 23, In-fa started to turn northwards while shear started to strengthen.^[512] By the next day, In-fa weakened to a Category 1 typhoon as it moved in an eastward direction with its convection now sheared.^[513] Hours later, In-fa further weakened to severe tropical storm strength.^[492][514] During November 25, the JMA downgraded In-fa to a tropical storm and in the same day, PAGASA issued its final bulletin on the typhoon as it exited their area of responsibility.^[492][515] After located in an area of strong-sheared environments,^[516] During November 26, In-fa started to transition into a hurricane-force extratropical cyclone, before the system dissipated during the next day as it merged with a front.^{[492][517][518]}

Typhoon Melor (Nona)

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

During December 10, the JMA started to monitor a tropical depression, that had developed about 665 km (415 mi) to the south of Guam.^[519] By December 11, the tropical depression rapidly organized as the JMA upgraded it to a tropical storm, naming it Melor,^[520] while the JTWC started issuing advisories, giving the designation 28W.^[521] Moreover, Melor entered the Philippine area of responsibility as PAGASA gave the name Nona.^[522] Due to a rapidly consolidating LLCC, the JTWC assessed Melor's intensity at 45 knots, making it at tropical storm strength.^[523] Melor intensified into a severe tropical storm on the next day when it was located over in extremely favorable environments with very low shear and warm SSTs.^[524][525] On December 13, tightly curved spiral banding wrapping into a 5 nm diameter eye made all agencies upgraded Melor to a typhoon.^[526][527] Rapid intensification occurred and Melor rapidly climbed up to Category 3 typhoon strength.^[528] Hours later, Melor continued to rapidly intensify due to very tight wrapping into a small eye, in which the JTWC upgraded Melor to a Category 4 typhoon.^[529] As from the JMA, Melor peaked with 10-minute sustained winds of 175 km/h (115 mph) and a pressure of 935 mbar.^[519] However, later Melor made its first landfall over in Eastern Samar and due to land interaction, its rapid intensification period had likely ended and the JTWC downgraded Melor to a Category 3 typhoon.^[530][531]

During December 14, despite Melor made several landfalls in the Philippine archipelago of Visayas, the typhoon maintained its intensity, while later Melor briefly strengthened into a Category 4 typhoon again and weakened.^[532][533] By December 15, satellite imagery indicated that Melor once again had undergone rapid intensification and reached its JTWC peak with 1-minute sustained winds of 230 km/h (145 mph).^[534] For the third and final time, Melor started to weaken as it interacted with the island of Mindoro as it was moving stationary.^[535] During the next day, Melor emerged to the South China Sea which it encountered unfavorable environments and the typhoon was further downgraded to a severe tropical storm.^[536][537] All agencies stopped warning on Melor when it fully dissipated early on December 17.^{[519][538][539]}

Due to the severe damage brought about by the typhoon in the provinces of Southern Luzon and the Visayas, Philippine President Benigno Aquino III declared a "State of National Calamity" in the country.^[540] According to NDRRMC, a total of 42 people were killed and ₱6.45 billion (US$136.4 million) were total of infrastructure and agricultural damages caused by Melor (Nona).^[541] Oriental Mindoro was placed under a state of calamity due to the devastation caused by the typhoon.^[542] Pinamalayan in Oriental Mindoro was worst hit, with 15,000 homes destroyed, 24,000 families (108,000 people) in evacuation centers, and property damages amounting to ₱325,025,710.96, including agriculture and infrastructure.^[543]

Tropical Depression 29W (Onyok)

Tropical depression (JMA)
Tropical depression (SSHWS)
Duration	December 14 – December 18
Peak intensity	55 km/h (35 mph) (10-min)  1002 hPa (mbar)

During December 13, a tropical disturbance developed within a favourable environment for further development, about 1,165 km (725 mi) to the southeast of Yap Island.^[544] Over the next day the system gradually moved north-westwards and was classified as a tropical depression by the JMA.^[545] With enough convection, the JTWC started to track the system with the designation of 29W.^[546] Moving westwards, 29W entered the Philippine area of responsibility, with PAGASA naming it as Onyok.^[547] Onyok reached its peak intensity on December 17, when flaring convection near its center had weakened and became exposed.^[548] The system rapidly deteriorated when the JTWC issued its final advisory early the next day.^[549] The system was last noted by the JMA during the same day, as it made landfall over Davao Oriental in Mindanao.^[550][551]

Other storms

On January 1, Tropical Depression Jangmi (Seniang) from the previous season was active within the Sulu Sea to the north of Malaysia.^[11] Over the next day the system moved southwards, before it made landfall on Malaysia and dissipated.^[11] During January 2, a tropical depression developed to the northwest of Brunei, within an area that was marginally favorable for further development.^[552][553] Over the next day the system moved into an area of moderate vertical wind shear, with atmospheric convection becoming displaced to the west of the fully exposed low level circulation center.^[554] The system was subsequently last noted by the JMA during January 4, as it dissipated in the South China Sea near the Malaysian-Indonesian border.^{[555][556][557]}

During July 1, a tropical depression developed, about 700 km (435 mi) to the southeast of Hagåtña, Guam.^[18] Over the next day the system remained near stationary, before it dissipated during July 2.^[18] On July 14, the JMA started to monitor a weak tropical depression several kilometers east-northeast of the Philippines.^[558] The system showed intensification; however, the JMA issued its final warning on the system shortly thereafter.^[559] On July 15, the JMA re-initiated advisories on the depression.^[560] The depression moved in a northward direction as it was absorbed by the outflow of Typhoon Nangka the next day.^[561] Another tropical depression developed on July 18 and dissipated near Japan and south of the Korean Peninsula on July 20.^[562][563] During July 20, the JMA briefly monitored a tropical depression that had developed over the Chinese province of Guangdong.^[563][564] During August 26, the remnants of Hurricane Loke moved into the basin from the Central Pacific and were immediately classified as an extra-tropical cyclone.^[565]

During October 6, the remnants of Tropical Depression 08C moved into the basin from the Central Pacific and were classified as a tropical depression by the JMA.^[566] The system drifted slowly in a westward direction until it started deteriorating,^[567] and the JMA downgraded the depression to a low-pressure area on October 8.^[568] During October 19, the JMA started to monitor a tropical depression that had developed, about 375 km (235 mi) to the south-west of Wake Island.^[569] The system was located within a marginal environment for further development, with moderate vertical wind shear and weak convergence preventing atmospheric convection from developing over the depression.^[570] Over the next couple of days the system moved and near the subsidence side of Typhoon Champi, before it was last noted by the JMA on October 22.^[571][572] The final tropical depression of the system developed on December 20 north of Malaysia.^[573] The system moved in a slow westward direction for a few days until it was last monitored on December 23, ending the season.^[574][575]

Storm names

Within the Northwest Pacific Ocean, both the Japan Meteorological Agency (JMA) and the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) assign names to tropical cyclones that develop in the Western Pacific, which can result in a tropical cyclone having two names.^[576] The Japan Meteorological Agency's RSMC Tokyo — Typhoon Center assigns international names to tropical cyclones on behalf of the World Meteorological Organization's Typhoon Committee, should they be judged to have 10-minute sustained windspeeds of 65 km/h (40 mph).^[577] PAGASA names to tropical cyclones which move into or form as a tropical depression in their area of responsibility located between 135°E and 115°E and between 5°N and 25°N even if the cyclone has had an international name assigned to it.^[576] The names of significant tropical cyclones are retired, by both PAGASA and the Typhoon Committee.^[577] Should the list of names for the Philippine region be exhausted then names will be taken from an auxiliary list of which the first ten are published each season. Unused names are marked in gray.

International names

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).^[578] 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.^[579] During the season the names Atsani, Champi and In-fa were used for the first time, after they had replaced the names Morakot, Ketsana and Parma, which were retired after the 2009 season.^[579] After the season the Typhoon Committee retired the names Soudelor, Mujigae, Koppu and Melor from the naming lists.^[580]

Mekkhala

Higos

Bavi

Maysak

Haishen

Noul

Dolphin

Kujira

Chan-hom

Linfa

Nangka

Soudelor

Molave

Goni

Atsani

Etau

Vamco

Krovanh

Dujuan

Mujigae

Choi-wan

Koppu

Champi

In-fa

Melor

Philippines

Amang	Betty	Chedeng	Dodong	Egay
Falcon	Goring	Hanna	Ineng	Jenny
Kabayan	Lando	Marilyn	Nona	Onyok
Perla (unused)	Quiel (unused)	Ramon (unused)	Sarah (unused)	Tisoy (unused)
Ursula (unused)	Viring (unused)	Weng (unused)	Yoyoy (unused)	Zigzag (unused)
Auxiliary list
Abe (unused)	Berto (unused)	Charo (unused)	Dado (unused)	Estoy (unused)
Felion (unused)	Gening (unused)	Herman (unused)	Irma (unused)	Jaime (unused)

During the season PAGASA used its own naming scheme for the 15 tropical cyclones, that either developed within or moved into their self-defined area of responsibility.^[581][582] The names were taken from a list of names, that had been last used during 2011 and are scheduled to be used again during 2019.^[581] The names Betty, Jenny, Marilyn, and Nona were used for the first time during the year after the names Bebeng, Juaning and Mina were retired.^[581]

The name Nonoy was originally included on the list; however, for political reasons as it sounds like Noynoy, the president of the country, it was redacted and replaced with Nona in mid-December when Tropical Storm Melor entered PAGASA's AoR.^[583][584] After the season the names Lando and Nona were retired by PAGASA, as they had caused over 7009100000000000000♠₱1 billion in damages.^[585] They were subsequently replaced on the list with the names Liwayway and Nimfa.^[585]

Season effects

This table summarizes all the systems that developed within or moved into the North Pacific Ocean, to the west of the International Date Line during 2015. The tables also provide an overview of a systems intensity, duration, land areas affected and any deaths or damages associated with the system.

Name	Dates active	Peak classification	Sustained wind speeds	Pressure	Land areas affected	Damage (USD)	Deaths	Refs
TD	01 !January 2 – 4	0 !Tropical depression	045 !Not specified	1006 !1006 hPa (29.71 inHg)	Borneo	5000000000000000000♠ None	None
Mekkhala (Amang)	02 !January 13 – 21	2 !Severe tropical storm	110 !110 km/h (70 mph)	0975 !975 hPa (28.79 inHg)	Yap State, Philippines	7006780000000000000♠$7.8 million	7000300000000000000♠3	[42][586]
Higos	03 !February 6 – 12	3 !Typhoon	165 !165 km/h (105 mph)	0940 !940 hPa (27.76 inHg)	None	5000000000000000000♠ None	None
Bavi (Betty)	04 !March 10 – 21	1 !Tropical storm	085 !85 km/h (50 mph)	0990 !990 hPa (29.23 inHg)	Marshall Islands, Mariana Islands	7006225000000000000♠$2.25 million	7000900000000000000♠9	[58][60]
Maysak (Chedeng)	05 !March 26 – April 7	3 !Typhoon	195 !195 km/h (120 mph)	0910 !910 hPa (26.87 inHg)	Micronesia, Philippines	7006850000000000000♠$8.5 million	7000500000000000000♠5
Haishen	06 !April 2 – 6	1 !Tropical storm	065 !65 km/h (40 mph)	0998 !998 hPa (29.47 inHg)	Caroline Islands	7005200000000000000♠$200 thousand	None	[81]
Noul (Dodong)	07 !May 2 – 12	3 !Typhoon	205 !205 km/h (125 mph)	0920 !920 hPa (27.17 inHg)	Caroline Islands, Taiwan Philippines, Japan	7007234640000000000♠$23.5 million	7000200000000000000♠2	[587]
Dolphin	08 !May 6 – 20	3 !Typhoon	185 !185 km/h (115 mph)	0925 !925 hPa (27.32 inHg)	Caroline Islands, Mariana Islands	7007100000000000000♠$10 million	None	[588]
Kujira	09 !June 19 – 25	1 !Tropical storm	085 !85 km/h (50 mph)	0985 !985 hPa (29.09 inHg)	Vietnam, China, Laos Thailand, Cambodia	7007166000000000000♠$16.6 million	7000900000000000000♠9	[114][115][589]
Chan-hom (Falcon)	10 !June 29 – July 13	3 !Typhoon	165 !165 km/h (105 mph)	0935 !935 hPa (27.61 inHg)	Mariana Islands, Taiwan, China, Korea, Russia	7009146000000000000♠$1.46 billion	7000600000000000000♠6	[590][591]
Linfa (Egay)	11 !July 1 – 10	2 !Severe tropical storm	095 !95 km/h (60 mph)	0980 !980 hPa (28.94 inHg)	Philippines, Taiwan China, Vietnam	7008217800000000000♠$218 million	5000000000000000000♠ None	[165][592]
TD	12 !July 1 – 2	0 !Tropical depression	045 !Not specified	1000 !1000 hPa (29.53 inHg)	Caroline Islands	5000000000000000000♠ None	None
Nangka	13 !July 2 – 18	3 !Typhoon	185 !185 km/h (115 mph)	0925 !925 hPa (27.31 inHg)	Marshall Islands, Caroline Islands Mariana Islands, Japan	7008150500000000000♠$151 million	7000200000000000000♠2	[593]
Halola (Goring)	14 !July 13 – 26	3 !Typhoon	150 !150 km/h (90 mph)	0955 !955 hPa (28.20 inHg)	Wake Island, Japan, Korea	7006120000000000000♠$1.2 million	None
TD	15 !July 14 – 16	0 !Tropical depression	045 !Not specified	1000 !1000 hPa (29.53 inHg)	None	5000000000000000000♠ None	None
TD	16 !July 18 – 20	0 !Tropical depression	045 !Not specified	1004 !1004 hPa (29.65 inHg)	Japan	5000000000000000000♠ None	None
TD	17 !July 20	0 !Tropical depression	045 !Not specified	1000 !1000 hPa (29.53 inHg)	China	5000000000000000000♠ None	None
12W	18 !July 23 – 25	0 !Tropical depression	045 !Not specified	1008 !1008 hPa (29.77 inHg)	Philippines	5000000000000000000♠ None	None
Soudelor (Hanna)	19 !July 29 – August 11	3 !Typhoon	215 !215 km/h (130 mph)	0900 !900 hPa (26.58 inHg)	Mariana Islands, Philippines Taiwan, Ryukyu Islands China, Korea	7009372000000000000♠$3.72 billion	7001380000000000000♠38	[231][594] [595][596]
14W	20 !August 1 – 5	0 !Tropical depression	045 !Not specified	1008 !1008 hPa (29.77 inHg)	Japan	5000000000000000000♠ None	None
Molave	21 !August 6 – 14	1 !Tropical storm	085 !85 km/h (50 mph)	0985 !985 hPa (29.09 inHg)	None	5000000000000000000♠ None	None
Goni (Ineng)	22 !August 13 – 25	3 !Typhoon	185 !185 km/h (115 mph)	0930 !930 hPa (27.46 inHg)	Mariana Islands, Philippines Taiwan, Japan, Korea China, Russia	7008293300000000000♠$293 million	34	[597][598]
Atsani	23 !August 14 – 25	3 !Typhoon	185 !185 km/h (115 mph)	0925 !925 hPa (27.32 inHg)	Mariana Islands	5000000000000000000♠ None	None
Kilo	24 !September 1 – 11	3 !Typhoon	150 !150 km/h (90 mph)	0950 !950 hPa (28.06 inHg)	Japan, Russia	5000000000000000000♠ None	None
Etau	25 !September 6 – 9	2 !Severe tropical storm	095 !95 km/h (60 mph)	0985 !985 hPa (29.09 inHg)	Japan, Russia	7007978000000000000♠$97.8 million	8	[599]
Vamco	26 !September 13 – 15	1 !Tropical storm	065 !65 km/h (40 mph)	0998 !998 hPa (29.47 inHg)	Vietnam, Laos Cambodia, Thailand	7007137570000000000♠$13.8 million	7001150000000000000♠15	[343][347][349] [350][351]
Krovanh	27 !September 13 – 21	3 !Typhoon	155 !155 km/h (100 mph)	0945 !945 hPa (27.91 inHg)	None	5000000000000000000♠ None	None
Dujuan (Jenny)	28 !September 19 – 30	3 !Typhoon	205 !205 km/h (125 mph)	0925 !925 hPa (27.32 inHg)	Mariana Islands Taiwan, China	7008660600000000000♠$661 million	3	[600]
Mujigae (Kabayan)	29 !September 30 – October 5	3 !Typhoon	155 !155 km/h (100 mph)	0950 !950 hPa (28.05 inHg)	Philippines, China, Vietnam	7009413000000000000♠$4.13 billion	29	[427][428][596][601]
Choi-wan	30 !October 1 – 7	2 !Severe tropical storm	110 !110 km/h (70 mph)	0965 !965 hPa (28.35 inHg)	Wake Island, Japan, Russia	5000000000000000000♠ None	None
08C	31 !October 6 – 8	0 !Tropical depression	045 !Not specified	1002 !1002 hPa (29.59 inHg)	None	5000000000000000000♠ None	None
Koppu (Lando)	32 !October 12 – 21	3 !Typhoon	185 !185 km/h (115 mph)	0925 !925 hPa (27.32 inHg)	Mariana Islands, Philippines Taiwan, Japan	7008235800000000000♠$236 million	58	[602][603]
Champi	33 !October 13 – 25	3 !Typhoon	175 !175 km/h (110 mph)	0930 !930 hPa (27.46 inHg)	Marshall Islands, Mariana Islands	5000000000000000000♠ None	None
TD	34 !October 19 – 21	0 !Tropical depression	045 !Not specified	1006 !1006 hPa (29.71 inHg)	None	5000000000000000000♠ None	None
26W	35 !October 20 – 22	0 !Tropical depression	055 !55 km/h (35 mph)	1004 !1004 hPa (29.65 inHg)	None	5000000000000000000♠ None	None
In-fa (Marilyn)	36 !November 16 – 27	3 !Typhoon	175 !175 km/h (110 mph)	0935 !935 hPa (27.61 inHg)	Micronesia, Guam	5000000000000000000♠ None	None
Melor (Nona)	37 !December 10 – 17	3 !Typhoon	175 !175 km/h (110 mph)	0935 !935 hPa (27.61 inHg)	Caroline Islands, Philippines	7008136400000000000♠$136 million	42	[604]
29W (Onyok)	38 !December 14 – 18	0 !Tropical depression	055 !55 km/h (35 mph)	1002 !1002 hPa (29.59 inHg)	Philippines	5000000000000000000♠ None	None
TD	39 !December 20 – 23	0 !Tropical depression	045 !Not specified	1008 !1008 hPa (29.77 inHg)	Borneo, Malaysia	5000000000000000000♠ None	None
Season Aggregates
39 systems	January 2 – December 23		215 km/h (130 mph)	900 hPa (26.58 inHg)		7010101604470000000♠$10.2 billion	263

See also

• 2015 Atlantic hurricane season
• 2015 Pacific hurricane season
• 2015 North Indian Ocean cyclone season
• South-West Indian Ocean cyclone seasons: 2014–15, 2015–16
• Australian region cyclone seasons: 2014–15, 2015–16
• South Pacific cyclone seasons: 2014–15, 2015–16
• South Atlantic tropical cyclone

References

External links

Wikimedia Commons has media related to 2015 Pacific typhoon season.

• Japan Meteorological Agency
• China Meteorological Agency
• Digital Typhoon
• Hong Kong Observatory
• Joint Typhoon Warning Center
• Korea Meteorological Administration
• National Weather Service Guam
• Malaysian Meteorological Department
• Philippine Atmospheric, Geophysical and Astronomical Services Administration
• Taiwan Central Weather Bureau
• TCWC Jakarta (Indonesian)
• Thai Meteorological Department (Thai)
• Typhoon2000
• Vietnam's National Hydro-Meteorological Service