Tropical Depression 01W (Auring)

Tropical depression (JMA)
Tropical depression (SSHWS)
Duration	January 7 – January 16
Peak intensity	55 km/h (35 mph) (10-min); 1000 hPa (mbar)

On January 7, both PAGASA and the JMA reported that Tropical Depression Auring developed about 400 km (250 mi) to the northeast of Davao City on Mindanao, Philippines.^[9][10] During that day, the system moved along the southern periphery of a subtropical ridge of high pressure, before the JTWC initiated advisories on the system and designated it as Tropical Depression 01W.^[11] It later made landfall in the Philippines the next day, and was assessed to have degenerated into a remnant low by the JTWC.^[12] The JMA tracked the system until it emerged into the South China Sea. By January 15, the JTWC re-issued advisories as it was located to the east of Vietnam.^[13] However, convection dissipated due to wind shear and land interaction, the JTWC issued their final warnings on January 16.^[14]

Flooding from Auring killed a total of 11 people.^[15] Damages from Tropical Depression Auring were totaled at ₱7.14 million (US$144,000) from agriculture and fishing in Negros Occidental.^[16]

Tropical Depression Bising

Tropical depression (JMA)
Duration	February 3 – February 7
Peak intensity	55 km/h (35 mph) (10-min); 1000 hPa (mbar)

On February 3, a tropical depression developed near Palau.^[17] The PAGASA would later name it as "Bising" as the depression was present at the Philippine Area of Responsibility.^[18][19] The storm would meander around the Philippine Sea, until the depression started to weaken when its LLCC became exposed, while moving north-northeast.^[20][21] The agency would not notice its weakening until the next day, when they issued their last advisory.^[22]

Tropical Depression 02W (Crising)

Tropical depression (JMA)
Tropical depression (SSHWS)
Duration	April 13 – April 20
Peak intensity	55 km/h (35 mph) (10-min); 1006 hPa (mbar)

A tropical depression formed over Palau on April 13.^[23] On the next day, the JTWC designated the depression as "02W"; on the best track, the depression was a remnant low at this time.^[24] Hours later, the PAGASA would name it "Crising" as the depression was present at the Philippine Area of Responsibility.^[25][26] The depression would later shrink its size while approaching the Visayas region.^[27] On the following day, the agency reported that "Crising" slightly intensified while moving near the Samar provinces; the intensification of the storm would prove only momentarily and weakened again.^[28][29] The JTWC would later discontinue advisories on the storm; on its best track, the system remained as a disturbance.^[24] The PAGASA discontinued the advisories on the system as it was nearing landfall on 13:00 UTC (9:00 pm PHST) over Hernani, Eastern Samar.^[30] The remnants of the depression crossed the region and into the South China Sea.^[31] At 18:00 UTC on April 18, the JTWC would upgrade the disturbance as 02W; operationally, the system was kept as a disturbance.^[24] The status would be short-lived, as the JTWC declared 02W as a disturbance.^[24] The remnants would later linger around, dissipating on April 20, while in the Luzon Strait.^[24]

As of April 17, at least ten people were reported to be killed in Cebu by flooding caused by the system.^[32] Total damages throughout the Philippines reached ₱84.8 million (US$1.7 million), mostly from Danao, Cebu.^[33]

Tropical Storm Muifa (Dante)

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	April 22 – April 29
Peak intensity	65 km/h (40 mph) (10-min); 1002 hPa (mbar)

During April 22, the JMA started to monitor a tropical depression that had developed near Guam.^[34] After moving westward for a couple of days, the JTWC began issuing advisories, and designated the storm 03W. By April 25, 03W organized and began consolidating further as the JMA upgraded the depression to a tropical storm, giving it the name Muifa.^[34] Muifa entered the Philippine Area of Responsibility the following day, and was named Dante by PAGASA.^[35] The storm, however, started moving northwards and immediately tracked out of the area by April 27.^[36] Following this, both the JMA and the JTWC downgraded Muifa to a tropical depression. Muifa fully dissipated early on April 29, and the JMA issued their final advisory on the storm.^[34]

Severe Tropical Storm Merbok

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	June 10 – June 13
Peak intensity	100 km/h (65 mph) (10-min); 985 hPa (mbar)

On June 10, the JMA started to track a tropical depression to the west of Manila, Philippines.^[34] After the system entered a region favorable for further development, the depression rapidly organized, prompting the JTWC to start issuing advisories and give it the designation of 04W. A few hours later, 04W had intensified into a tropical storm, receiving the name Merbok as it starts to move in a north-northwestward direction.^[34] On June 12, Merbok reached its peak intensity with 10-minute winds of 100 km/h (60 mph) and a minimum pressure of 985 hPa, shortly before making landfall in Eastern Shenzhen.^[34][37] On June 13, the JMA issued its final warning on Merbok, as the system dissipated over China.^[37][38]

Sustained winds of 51.3 knots (95.0 km/h; 59.0 mph) and a minimum pressure of 990.3 hPa (29.24 inHg) were recorded in Hong Kong as the eye passed nearby.^[37] Across Guangdong Province, 32 homes were destroyed, 122,000 people reported property damage, and 13,000 hectares of crops flooded. Total economic losses in South China were counted to be CN¥600 million (US$88.3 million).^[39]

Severe Tropical Storm Nanmadol (Emong)

Severe tropical storm (JMA)
Category 1 typhoon (SSHWS)
Duration	July 1 – July 4
Peak intensity	100 km/h (65 mph) (10-min); 985 hPa (mbar)

On July 1, the JMA upgraded a low-pressure area it had been monitoring to a tropical depression, located south-southwest of Okinotorishima.^[40] Later that day, the JMA began issuing advisories once the depression's sustained winds were estimated at 55 km/h (35 mph).^[41] Shortly thereafter, the PAGASA classified the system as a tropical depression, assigning the local name Emong. On July 2, the JMA classified the system as a tropical storm, and assigned the official name Nanmadol.^[40] The JTWC followed suit and gave the internal designation of 05W. The cyclone continued to intensify, and was upgraded by the JMA to a severe tropical storm later that day.^[40] Nanmadol reached peak intensity at about 06:00 UTC on July 3,^[40] and maintained this strength until making landfall on the western coast of Kyushu several hours later. The cyclone began to accelerate while following a generally eastward course across the south of Japan. After brushing the southern coast of Japan, the JTWC issued its final advisory during the next day. The JMA followed suit late on July 4, when it had become extratropical.^[40] Its remnants moved out of the basin three days later.^[40]

Evacuation advisories were issued to at least 20,000 residents due to fears of possible flooding and landslides, especially in the prefectures of Niigata, Toyama and Nagano, which had experienced rainfall accumulations of up to 300 mm (12 in) in the preceding hours.^[42][43] At least three people were injured during the storm—a young boy's hand was injured when a school window broke in the city of Kumamoto, and two adults in Ōita prefecture sustained minor injuries after falling due to the strong winds.^[42][43][44] A total of 41 people have been confirmed dead due to torrential rains which caused landslides and flooding, particularly in Kyushu. Total damages from the storm in Japan were amounted to be ¥190 billion (US$1.68 billion).^[45]

Severe Tropical Storm Talas

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

Early on July 14, the JMA upgraded a low-pressure area in the South China Sea to a tropical depression after the system began to organize.^[46] Late the same day, the JMA began issuing advisories on the depression, and forecast it to develop into a tropical storm within the next 24 hours.^[47] The system intensified into a tropical storm, and was then named Talas. A few days later, Talas intensified further to become a severe tropical storm.

Talas made landfall near Vinh of Nghệ An Province in Central Vietnam at 01:00 ICT on July 17 (18:00 UTC on July 16) as a severe tropical storm.^[48] In Vietnam, the storm left 14 people dead and damaged around 2,700 houses. A coal ship with 13 crew members sank off the coast of Cửa Lò, leaving 3 dead and another 3 still unaccounted for.^[49] Damages in Vietnam were counted to be 993 billion₫ (US$43.7 million).^[50] Total economic losses in Hainan Province reached CNY 60 million (US$8.8 million).^[39]

Typhoon Noru

Very strong typhoon (JMA)
Category 4 super typhoon (SSHWS)
Duration	July 19 – August 8
Peak intensity	175 km/h (110 mph) (10-min); 935 hPa (mbar)

The JMA reported that a non-tropical low had transitioned into a tropical depression north-northwest of Wake Island early on July 19. Twelve hours later it had strengthened to a tropical storm, and was named Noru.^[51] Noru then interacted with Tropical Storm Kulap, its counterpart storm, and began to exhibit a fujiwhara effect with Kulap. Tropical Storm Kulap then weakened enough, and when it dissipated, its remnants started to power Noru, and it became a severe tropical storm after, and continued its long and erratic journey towards Japan.

About halfway through July 22, the system became the first typhoon of the season, and fluctuations in intensity occurred until late on July 29, when it slowed down, and shortly thereafter, explosive intensification ensued, and Noru intensified into a Category 4 super typhoon. After it reached peak intensity, it quickly began to weaken for a short period of time before slowing the rate of weakening. It briefly accelerated, before yet again, it began to stall near Japan for some time before moving north and dissipating in the Sea of Japan. Total economic losses in Japan were counted to be US$100 million.^[52]

Tropical Storm Kulap

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	July 20 – July 28
Peak intensity	75 km/h (45 mph) (10-min); 1002 hPa (mbar)

On July 20, the JMA started to monitor a tropical depression that formed over to the southwest of Midway Atoll, just to the west of the International Date Line.^[34] The JTWC classified the system as subtropical, however.^[53] By July 21, the subtropical storm started to show tropical characteristics, where it prompted both agencies to start issuing advisories, receiving the designation of 09W and the name Kulap.^[54][34] During the next day, Kulap briefly reached its peak intensity with 1-minute sustained winds of 95 km/h (60 mph) after imagery depicted some convection over near its compact center.^[55] After moving westward in a marginally favorable environment, the JMA had reported a minimum pressure of 1002 hPa with peak 10-minute winds of 75 km/h (45 mph) during the early hours of July 24. However several hours later, Kulap had entered in a very unfavorable environment such as cooler waters of 25 °C (77 °F).^[56] Due to strong shear and an interaction with Typhoon Noru to its south, Kulap had rapidly weakened; therefore, both agencies issued their final advisory on July 26.^[57] The JMA, however, tracked Kulap's remnants until July 28 when it was absorbed by the outflow of Typhoon Noru.^[34]

Tropical Storm Sonca

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

On July 21, both the JMA and the JTWC reported that Tropical Depression 08W had developed approximately 582 km (362 mi) to the south of Hong Kong.^[34][58] After moving westward for a couple of days, the system strengthened into a tropical storm by both agencies while nearing the island province of Hainan, receiving the name Sonca.^[59][34] By July 24, Sonca reached its maximum intensity with a minimum pressure of 994 hPa.^[34] Early on July 25, the JTWC issued its final advisory as the system made landfall over in Quảng Trị Province, Vietnam.^[60][61] The JMA issued its final advisory a few hours later when it had weakened into a tropical depression,^[34] although Sonca maintained its intensity over land until it had fully dissipated on July 29.^[34]

Flooding in Northern Cambodia drowned two people, blocked many roads and flooded several hundred houses.^[62] Damage across Sakon Nakhon, Thailand exceeded 100 million baht (US$3 million)^[63] and killed 23 people across Thailand.^[64]

Tropical Storm Roke (Fabian)

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	July 21 – July 23
Peak intensity	65 km/h (40 mph) (10-min); 1002 hPa (mbar)

The JMA noted the formation of a tropical depression southeast of Taiwan early on July 21.^[34] Assigning the numerical designation 10W, the JTWC upgraded the system to a tropical depression at about 18:00 UTC the same day.^[65] The system traveled in a generally northwesterly direction, and passed through the Luzon Strait, between Taiwan and the Philippines.^[65] Around the same time, the PAGASA began issuing advisories on the depression, and contributed the unofficial name Fabian.^[66] Early the next day, after the system had emerged into the South China Sea, both the JMA and the JTWC upgraded the system to a tropical storm, naming it Roke.^[65][34] Roke assumed a more westerly course, and tracked obliquely towards China's Guangdong coast.^[67] The JTWC downgraded the system to a tropical depression just 12 hours later, at 18:00 UTC,^[65] but the JMA maintained the cyclone's category as a tropical storm. Roke made landfall just east of the Hong Kong central business district at about 01:30 UTC on July 23, and passed over Shenzhen one to two hours later.^[67] Roke weakened to a depression a few hours later, though the JMA declared that it had dissipated on 18:00 UTC of the same day.^[34]

Schools, businesses and government offices were closed in Hong Kong as the Hong Kong Observatory (HKO) raised its typhoon warning signal to 8—the third highest of five levels—in preparation for Tropical Storm Roke.^[68] Ferry services in the city were suspended, and more than 50 flights were delayed.^[69] However, winds in the city were relatively light and no significant damage was reported.

Typhoon Nesat (Gorio)

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

The JMA upgraded a low-pressure area to a tropical depression east of the Philippines early on July 25. On July 26, it was named Gorio by PAGASA and later intensified into Tropical Storm Nesat. Nesat stalled in the Philippine Sea in the next couple of days and gradually intensified to become a severe tropical storm on July 27. It gradually strengthened until its peak on July 29, as a Category 1 typhoon. It then hit Taiwan, and began to weaken until its dissipation on July 30.^[70]

Despite the storm not making landfall in the Philippines, Nesat enhanced the southwest monsoon which brought torrential rainfall over most of the country. As of August 3, the NDRRMC had reported a total of ₱ 247.58 million (US$4.9 million) worth of damages.^[71] Total damages in Taiwan were counted to be NT$60.19 million (US$2.03 million).^[72] Total damages in Mainland China were counted to be CNY 1.83 billion (US$271.6 million).^[39] Typhoon Nesat was originally a Category 1, but was upgraded by the Joint Typhoon Warning Center into a minimal Category 2.

Tropical Storm Haitang (Huaning)

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	July 27 – August 2
Peak intensity	85 km/h (50 mph) (10-min); 985 hPa (mbar)

A low-pressure area over the northern portion of the South China Sea was upgraded to a tropical depression by the JMA early on July 27.^[73] Despite an exposed LLCC with disorganized banding, the JTWC started initiating advisories, assigning the designation of 12W.^[74] During the next day, the system had strengthened into a tropical storm, with the JMA naming it as Haitang, after ASCAT image depicted 40 knot winds over in the southern portion of the storm.^[75] Due to the nearby Typhoon Nesat and moderate wind shear, Haitang maintained its intensity for several hours,^[76] until on July 30 when the system had deepened and reached its peak intensity with 10-minute sustained winds of 85 km/h (55 mph) with a minimum pressure of 985 hPa. Around the same time, Haitang entered the Philippine area of Responsibility, receiving the name Huaning by PAGASA,^[77] although the system had left the area during 12:00 UTC of the same day.^[78] Three hours later, the JTWC downgraded the system to a tropical depression,^[79] though it was re-upgraded into a tropical storm six hours later.^[80] By July 31, the JTWC issued their final advisory on Haitang after the system had made landfall over in the Pingtan County in Taiwan.^[81] During 06:00 UTC of that day, the JMA issued their final advisory after Haitang weakened into a remnant low.^[34]

Tropical Storm Nalgae

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	July 31 – August 5
Peak intensity	85 km/h (50 mph) (10-min); 990 hPa (mbar)

During July 31, the JMA started to monitor a tropical depression located about 1,106 km (687 mi) to the northeast of Wake Island.^[82] During the next day, the JTWC started issuing advisories and designated it as 13W.^[83] By August 2, both agencies upgraded 13W to Tropical Storm Nalgae after imagery showed flaring convection and the storm was located in a region of low to moderate wind shear and warm SSTs.^[84][85] Moving in a northward direction, Nalgae slowly intensified for several days. Nalgae reached its peak intensity with 10-minute sustained winds of 85 km/h (55 mph) and a minimum barometric pressure of 988 hPa during August 5 for a brief time, as it was beginning to transition into an extratropical cyclone. The JTWC downgraded Nalgae to a tropical depression later that day and issued their final advisory after the storm was located in very unfavorable environments.^[86] The JMA followed suit early on August 6 when Nalgae fully transitioned into an extratropical cyclone, after which its remnants moved further north and were last noted during August 9.

Typhoon Banyan

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

On August 10, Tropical Depression 14W formed in the North Pacific Ocean. It strengthened into a tropical storm on August 11 at 5 p.m. EDT (2100 UTC), and was named Banyan. Rapid intensification occurred on Banyan, and it intensified into a typhoon on August 12 at 5 p.m. EDT (2100 UTC). Banyan reached its peak strength of 150 km/h (95 mph) on August 13, without harming any land, as a Category 3 equivalent system in a high latitude, like Typhoon Songda (2016). Banyan began to start weakening on August 14, and continue to rapidly weaken as it entered the frigid cold waters of the North Pacific. It weakened into an extratropical depression on August 17.

Typhoon Hato (Isang)

Typhoon (JMA)
Category 3 typhoon (SSHWS)
Duration	August 19 – August 24
Peak intensity	140 km/h (85 mph) (10-min); 965 hPa (mbar)

A low-pressure area developed into a tropical depression on August 19, while located to the southeast of Taiwan, and was named by PAGASA as Tropical Depression Isang. Over the next few days, Isang became a tropical storm, and was named Hato. Hato then became a severe tropical storm as it passed through the Batanes region of the Philippines, and the PAGASA later issued its final warning as Hato (named Isang) moved out of the Philippine Area of Responsibility.^[87]

It gradually intensified and reached typhoon status on the afternoon of August 22 after entering the northeastern part of the South China Sea. On August 23, 07:00 HKT, Hato was approximately 100 km southeast of Hong Kong, bringing rain to the mainland as well as Hainan to the west. At 11:00 HKT the eye was approximately 60 km southwest of Hong Kong with the typhoon heading onto the mainland in a west-northwesterly direction.^[88]

Hong Kong Observatory issued Hurricane Signal No. 10 at 09:10 HKT, August 23, the first time since 2012.^[89] A total of 11 people were killed while total damage in Mainland China were counted to CN¥28.91 billion (US$4.34 billion).^[39] No people were killed in Hong Kong, while estimated damage in Hong Kong amounted to HK$4 billion (US$511 million).^[90] In Macau, losses of 12.50 billion patacas (US$1.55 billion) were incurred when high tides exacerbated flooding in most of the low-lying areas, inundating ground floor shops and businesses. There were 12 deaths as a result of the typhoon, including a number of people who drowned in flooded underground car-parks.^[91] Despite making landfall in South China, Hato triggered floods in northern Vietnam and killed 1 person. The total damage by heavy rainfall in Bắc Kạn Province was 31 billion₫ (US$1.36 million).^[92] In total, there were 24 deaths attributed to the typhoon.

Severe Tropical Storm Pakhar (Jolina)

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	August 24 – August 28
Peak intensity	100 km/h (65 mph) (10-min); 985 hPa (mbar)

On August 24, a tropical depression formed in the Philippine Sea and was named Jolina by PAGASA. On the next day, Jolina intensified into a tropical storm, and was named Pakhar. On August 26, Pakhar passed over the Philippines heading westward toward mainland China where it gathered strength into a severe tropical storm before making landfall in Tianshan on August 27, where after the previous monster storm Typhoon Hato hit days ago, they raised Signal #8 for Pakhar's arrival and landfall. Pakhar rapidly dissipated the next day.

A total of 83,000 people were affected by the storm, along with 14,000 people in which were evacuated over in the four main affected regions of Guandong, Guangxi, Guizhou and Yunnan.^[93] One person died from a traffic incident while 62 were injured, while an additional two were confirmed hours later.^[94]

Total economic losses in South China amounted to CN¥760 million (US$114.4 million) while a total of twelve people were killed in relation to the storm.^[95] Moreover, damages in the Philippines were recorded at ₱41.27 million (US$808 thousand) and 2 billion₫ (US$88,000) in Vietnam.^[96][97]

Typhoon Sanvu

Typhoon (JMA)
Category 2 typhoon (SSHWS)
Duration	August 26 – September 3
Peak intensity	150 km/h (90 mph) (10-min); 955 hPa (mbar)

On August 27, the JMA began to monitor a tropical depression that had developed about 441 km (274 mi) north-northeast of Saipan, although the system's nature was more of a monsoon depression.^[98] The JTWC followed suit on the following day, designating the system as 17W.^[99] Around the same time, the system had intensified into Tropical Storm Sanvu. By August 29, Sanvu increased in size, and therefore it prompted the JMA to upgrade it to a severe tropical storm. After moving in a westward direction, Sanvu stalled and entered a region of favorable conditions. As a ragged eye developed, both agencies upgraded Sanvu to a typhoon during August 31.^[100] Sanvu reached its peak intensity on September 1 as a Category 2 typhoon.^[101] Thereafter, the system steadily weakened as it started to move northwards with JTWC immediately downgrading the system to a tropical storm and issuing their final advisory late on September 2. The JMA still classified Sanvu as a typhoon until they issued their final advisory as the system had transitioned into an extratropical cyclone on September 3.

Sanvu did not cause any significant damage in the Northern Mariana Islands, though a 33-year-old woman drowned at Obyan beach in Saipan due to large waves on August 29.^[102]

Severe Tropical Storm Mawar

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

On August 30, the JMA started to track a tropical depression to the north-northeast of Luzon, Philippines. Given the international designation of 18W by the JTWC,^[103] the JMA upgraded the system immediately to Tropical Storm Mawar. Slowly organizing, convection had rapidly developed and Mawar strengthened into a severe tropical storm early on September 2. On September 3, Mawar had weakened to a tropical storm after environments started to become unfavorable due to high wind shear.^[104] Later that day, Mawar weakened to a tropical depression and the JTWC issued their final advisory while making landfall over in Southeastern China between the cities of Shanwei and Shantou.^[105][106] The JMA followed suit early on September 4 when Mawar had fully dissipated.

The China's National Meteorological Center (NMC) issued a blue alert for the southern parts of Guangdong on September 1. During 2:00 a.m. local time on September 2, the Hong Kong Observatory issued a Tropical Cyclone Warning Signal No. 1 over in Hong Kong.^[107] Chinese authorities activated a natural disaster alert and response to help local civil affairs departments in areas such as the provinces of Fujian and Guandong to prepare for relief work.^[108] By September 3, the NMC had raised their warning signal to a yellow alert.^[109] Flooding from Mavar was a major concern with reports of rainfall of up to 80 millimetres (3.1 in) in some places which were impacted by Hato and Pakhar.^[106] Total economic losses in South China were counted to be CNY 10 million (US$1.53 million).^[39]

Tropical Storm Guchol (Kiko)

Tropical storm (JMA)
Tropical depression (SSHWS)
Duration	September 3 – September 7
Peak intensity	65 km/h (40 mph) (10-min); 1000 hPa (mbar)

On September 3, the JMA started to track a tropical depression that had developed to the east of Luzon, Philippines. During the next day, the PAGASA initiated advisories and gave the local name Kiko,^[110] while the JTWC followed suit by giving it the designation 19W.^[111] However, due to increased wind shear along with an exposed circulation, the JTWC issued its final advisory on 03:00 UTC September 5.^[112] Several hours later, deep convection was depicted and despite moderate to high shear, the JTWC re-initiated advisories,^[113] while the JMA had upgraded the system to a tropical storm, naming it as Guchol early on the next day. On 21:00 UTC of that day, the JTWC stopped issuing warnings on the system after convection significantly weakened.^[114] JMA later followed suit early on the next day by declaring it a remnant low as it neared Putian, Fujian on Strait of Taiwan.^[34] The remnant low would then make landfall over Pingtan County of Fujian in China late on the following day before it transitioned into an extratropical storm near Zhejiang as it merged with the cold front on September 8.

Typhoon Talim (Lannie)

Very strong typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	September 8 – September 17
Peak intensity	175 km/h (110 mph) (10-min); 935 hPa (mbar)

A tropical depression formed east of Guam on September 7.^[115] By the next day, the JTWC began issuing advisories on Tropical Depression 20W.^[116] On September 9, 20W organized into a tropical storm, with the JMA naming the system as Talim.^[117] With gradual intensification, the JMA upgraded Talim to a severe tropical storm. Talim further strengthened to a typhoon on September 11 where it simultaneously entered the PAR, with PAGASA naming it as Lannie.^[118] The JTWC, however, delayed their upgrade until September 12.^[119] Due to an ill-defined eye, Talim maintained its intensity until its eye became much clearer as rapid deepening ensued, as Talim became a Category 4 on September 14, and reached its peak intensity with 1-minute sustained winds of 220 km/h (135 mph).^[120] Talim began to curve eastward as it rapidly weakened to a tropical storm thereafter, making landfall in Kyushu on September 17, with a path of heavy rainfall up to the region east of Tokyo.^[121]

In Japan, 5 people were killed, and the agricultural loss were about JP¥32 billion (US$287.9 million).^[122] Total damages across the country were counted to be US$750 million.^[123]

Typhoon Doksuri (Maring)

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

On September 9, the Joint Typhoon Warning Center (JTWC) began monitoring on a tropical disturbance that had developed about 836 km (519 mi) west-northwest of the province of Eastern Samar.^[124] During the next day, the Japan Meteorological Agency (JMA) classified the system as a weak tropical depression. As the tropical cyclone is inside PAR, it was assigned the name "Maring".^[125] On 21:00 UTC of September 11, the JTWC followed suit, giving the designation of 21W.^[126] The JMA upgraded 21W to a tropical storm during September 12, giving the name Doksuri, the 19th named storm of the annual typhoon season.

Laguna was one of the provinces that got hit hard by the storm as the city was placed under a state of calamity after it had "too much rainfall" that produced further flash floods and landslides.^[127]

As of September 19, the NDRRMC confirmed a total of 8 dead due to landslides and flooding while total damages were up to ₱267 million (US$5.24 million).^[128]

On September 15, Typhoon Doksuri made landfall in Quảng Bình Province, Vietnam as a Category 3 typhoon. Doksuri killed 15 people so far in Vietnam while estimated damages were about ₫16.36 trillion (US$720 million).^{[129][130][131]} Despite making landfall in Indochina, Doksuri affected Hainan and total economic losses were estimated to be CNY 100 million (US$15.3 million).^[39]

Tropical Depression 22W (Nando)

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

A tropical depression formed to the west of Luzon on September 23, and was named "Nando" by PAGASA. The tropical depression quickly moved west-northwest and made landfall in Quảng Ninh, Vietnam, on September 25, before dissipating later on the same day.

The China Observatory issued a "yellow" alert over in the eastern and southern regions due to rainstorms. Some areas have warned a possible precipitation of about 140 millimetres (5.5 in).^[132] Typhoon Signal No. 1 was raised over in Hong Kong during September 24, with expected gusts of up to 70 km/h (45 mph) including rough swells.^[133] A voltage dip also occurred, causing 17 people to be trapped in lifts.^[134] As the depression approached Vietnam on September 25, the Vietnam National Center for Hydro-Meteorological Forecasting of Vietnam forecast rainfall of about 150 millimetres (5.9 in) in Hanoi and surrounding provinces, with rough waves up to 3 m (9.8 ft) in Hạ Long Bay.^[135]

Tropical Depression 23W

Tropical depression (JMA)
Tropical depression (SSHWS)
Duration	October 7 – October 10
Peak intensity	55 km/h (35 mph) (10-min); 1000 hPa (mbar)

Early on October 7, a tropical depression formed to the west of the Philippines.^[136]

Early on October 10, the tropical depression made landfall in Hà Tĩnh Province, Vietnam, and dissipated shortly afterward. Consequently, both the JMA and the JTWC issued their final advisories for the storm.

Tropical Depression 23W caused severe flooding over provinces of Northern and Central Vietnam. Roughly more than 700 houses have been destroyed, while rescue efforts have saved 28 people from the danger zone. In total, 100 people were killed, and damages were about 13 trillion₫ (US$572 million).^[137][138] During October 10, the Red River was forecast to have waters exceed to the levels of 3–50 cm (1.2–19.7 in).^[139][140] In Hoàng Long river (Ninh Bình Province) flooding was the most severe since 1985.^[141]

Typhoon Khanun (Odette)

Typhoon (JMA)
Category 2 typhoon (SSHWS)
Duration	October 11 – October 16
Peak intensity	140 km/h (85 mph) (10-min); 955 hPa (mbar)

By October 11, the Japan Meteorological Agency upgraded a disturbance that was organizing in the Philippine Sea.^[34] By 06:00 UTC on the following day, the Joint Typhoon Warning Center also upgraded the disturbance to a depression, designating it as "24W".^[142] By 12:00 UTC the same day, the JMA officially upgraded the depression, naming it as "Khanun".^[34] Two hours later, the PAGASA upgraded the depression, naming it "Odette".^[143] Over the rest of the day, Khanun intensified under favorable conditions,^[34][142] while approaching the northern parts of Luzon.^[144] At 14:00 UTC (10:00 pm PHST), PAGASA upgraded "Odette" to a tropical storm while nearing landfall over Santa Ana, Cagayan.^[145] The storm will make landfall on the place,^[146] and emerged into the South China Sea, when it started re-intensifying under favorable conditions.^{[34][142][147]} At 06:00 UTC, JMA upgraded Khanun into a severe tropical storm; the PAGASA would later follow suit, as "Odette" is also upgraded into a severe tropical storm.^[34][148] At 14:00 UTC (10:00 pm PHST), PAGASA reported that Severe Tropical Storm "Odette" has exited their Philippine Area of Responsibility.^[149]

Intensifying in the South China Sea, Khanun was upgraded to a typhoon by the JMA on October 14 at 12:00 UTC.^[34] The JTWC would follow suit six hours later, upgrading the storm into a category 1 typhoon.^[142] By the next day, JMA reported that Khanun reached its peak intensity with 135 km/h (75 knots) and a pressure of 955 hPa. The JTWC would follow suit three hours later with the winds of 165 km/h (90 knots) and a pressure of 965 hPa.^[142] After its peak, Khanun immediately weakened under the influence of the northeast monsoon; at the time the storm made landfall over the Leizhou Peninsula, the system was barely at tropical storm intensity.^{[34][142][150]} Both agencies would issue their last advisories on Khanun, as the storm weakened further while approaching the northern Vietnam.^[34][142]

According to the NDRRMC, Khanun killed only one person, with total damages of ₱4.45 million (US$86,600).^[151][152] Authorities in Hong Kong and Macau raised the number 8 tropical cyclone warning on October 15 as gale-force winds affected the region. In total, damages from Khanun in South China were counted to be CNY2.46 billion (US$373 million).^[150]

Typhoon Lan (Paolo)

Very strong typhoon (JMA)
Category 4 super typhoon (SSHWS)
Duration	October 15 – October 23
Peak intensity	185 km/h (115 mph) (10-min); 915 hPa (mbar)

The United States Naval Research Laboratory (NRL) initially mentioned a tropical disturbance over Chuuk on October 11.^[153] After the slow consolidation, the Joint Typhoon Warning Center (JTWC) issued a Tropical Cyclone Formation Alert to the elongated system early on October 14,^[154] shortly after the Japan Meteorological Agency (JMA) started to monitor it as a low-pressure area.^[155] The agency upgraded it to a tropical depression almost one day later and began to issue tropical cyclone warnings since 06:00 UTC on October 15.^[156][157] In the afternoon, the JTWC also upgraded it to a tropical depression assigning the designation 25W, which formative but shallow convective bands had become more organized, and symmetrically wrapped into a defined low-level circulation center.^[158] About three hours later, the JMA upgraded it to the twenty-first Northwest Pacific tropical storm in 2017 and assigned the international name Lan, when it was located approximately 310 km (190 mi) to the northeast of Palau.^[159] Early on October 16, the JTWC upgraded Lan to a tropical storm too, based on T-number 2.5 of the Dvorak technique,^[160] shortly before it entered the Philippine Area of Responsibility and received the name Paolo from PAGASA.^[161]

In Japan, 17 people were killed in Mainland Japan and the agricultural loss were about JP¥62.19 billion (US$547.9 million).^[162] Total economic losses were counted to be US$2 billion.^[123]

Tropical Depression 26W

Tropical depression (SSHWS)
Duration	October 18 – October 19
Peak intensity	45 km/h (30 mph) (1-min); 1002 hPa (mbar)

Originating from an enhanced monsoon trough, a tropical disturbance developed just to the northwest of Palawan on October 17.^[163] On October 18, the JTWC had issued a TCFA on the system.^[164] By 21:00 UTC of that day, the JTWC began issuing advisories as they classified it as a tropical depression, assigning the identifier 26W.^[165] This was due to deep convection found near the storm's center with formative banding, along with its location over in a favorable environment.^[166] Initially, its forecast stated that 26W would intensify into a weak tropical storm, although due to a disorganized center with strong shear, the JTWC issued their final advisory on October 19 as it was being absorbed by the outflow of nearby Typhoon Lan.^[167]

Associated with the rainbands of a nearby typhoon, 26W helped spread scattered rainfall throughout most of Visayas and northern Mindanao. Residents in some areas were alerted against possible flash floods and landslides.^[168] 14 people were dead from heavy rainfall from the system and its precursor, and raised a state of calamity in Zamboanga City on October 23.^[169][170]

Severe Tropical Storm Saola (Quedan)

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

A tropical depression formed north of Guam. The next day, the Tropical Depression transitioned into a Tropical Storm and the Japan Meteorological Agency named it Tropical Storm Saola. By evening of that day, Saola entered the Philippine Area of Responsibility (PAR). The PAGASA gave the local name "Quedan" to the storm. ^[171] On October 26, Saola strengthened into a severe tropical storm at 08:00 UTC as it moved slowly in a northwestward heading. Its intensity did not change, even as high wind shear occurred to the north of Saola and the strengthening northeast monsoon while heading to Japan. It left PAR two days later. The system continued to track northeastward and made several landfalls and close approaches over the islands of Ryukyu Arc.^[172] It started weakening while in cold waters and brought rains to Southern Japan but did not make landfall. It later transitioned into an extratropical cyclone before it dissipated near the Chiba Prefecture.

Although Saola didn't make landfall, damages were totaled up to US$250 million.

Tropical Depression 29W

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

The JMA upgraded a low-pressure area to a tropical depression over the southern portion of the South China Sea, on October 30.^[173] The JTWC issued a TCFA during the next day as it gathered strength. Initially forecast to intensify to a tropical storm, the system rapidly deteriorated and degenerated to a remnant low on November 3 as it tracked into the Gulf of Thailand.^[174] Over in the course of two days, after re-curving back to the gulf, the JTWC re-issued a TCFA.^[175] By November 6, the JTWC classified the system as Tropical Depression 29W.^[176] On November 8, 29W made landfall over the Malay Peninsula, before dissipating soon afterward.

Tropical Depression 29W caused unusually heavy rains and flash floods to occur in the state of Penang, killing 7 people.^[177] Flood waters in parts of the city reached 3.7 m (12 ft), submerging entire homes.

Typhoon Damrey (Ramil)

Typhoon (JMA)
Category 2 typhoon (SSHWS)
Duration	October 31 – November 4
Peak intensity	130 km/h (80 mph) (10-min); 970 hPa (mbar)

The JMA upgraded a low-pressure area to a tropical depression east of Visayas on October 31. PAGASA gave warnings to the system and named it Ramil. The storm brought rainy weather on the All Saints's Day (November 1) to Visayas. The tropical depression made landfall over Busuanga, Palawan at midnight on November 1. On November 2, Ramil strengthened, and the JTWC and JMA upgraded Ramil to a tropical storm, and gave the system the international name Damrey.^[178]

Torrential rains caused by the storm resulted in 2.5 ft of deep flooding, damaging agricultural crops. Agricultural damages were totaled to Php1.03 million (US$20,000) over in the city of Aurora Quezon on November 4.^[179]

Strong winds, heavy rainfall and severe flooding in Central Vietnam caused by the typhoon. Total damage reached over 22 trillion VND (US$1 billion).^[180] Damrey made landfall in central Vietnam as the region hosted the 2017 APEC Summit in Da Nang.

As of November 8, a total of 112 people were confirmed dead due to the storm.^[181][182]

Tropical Storm Haikui (Salome)

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	November 7 – November 13
Peak intensity	75 km/h (45 mph) (10-min); 998 hPa (mbar)

A Tropical Depression formed over Samar on November 9, and PAGASA gave the name Salome to the system. Salome damaged boats in Sorsogon with large waves. On the next day, after Salome made landfall, the system intensified into a tropical storm, and the JMA gave the international name Haikui to the system. Haikui dropped heavy rainfall over Southern Luzon and Visayas.^[183] It landfalled in Batangas before midnight and passed the boundary of Batangas and Cavite at 11:00 in that evening. It dissipated on Vietnam on November 13, 2017.

In China, Haikui produced heavy, sustained rain in the island province of Hainan, China. Flooding was recorded in several locations on the east side of the province. In the capital Haikou, flooding caused road closure. ^[184][185]

No casualties were reported, though damages were totaled up to ₱218.5 million (US$4.26 million). In addition, only five houses were fully damaged in Dipaculao, Aurora.^[186]

Tropical Storm Kirogi (Tino)

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	November 16 – November 19
Peak intensity	65 km/h (40 mph) (10-min); 1000 hPa (mbar)

On November 16, a tropical Depression formed on Sulu Sea, with the PAGASA naming it Tino. At midnight on the same day, the system made landfall on Puerto Princesa.^[187] At about that time, the system intensified into a tropical storm, receiving the international name Kirogi by the JMA.

Kirogi caused flooding in the Philippines and Vietnam, with trees and power poles toppling in Ho Chi Minh City. Eight people were killed in Vietnam.

Several barangays in Mansalay were affected by floodwaters 0.5–1 meter (1.6–3.3 ft) deep; San Vicente received floods 1 metre (3.3 ft) deep. Three houses were damaged in Palawan; ports in Puerto Princesa, Coron, Palawan, Cuyo, Palawan, El Nido, Palawan, and Brooke's Point temporarily suspended operations, stranding 243 passengers. A total of 497 people were affected as a result of the storm.^[188]

Total economic losses in Vietnam were amounted to be US$10 million.^[189] The remnant energy of Tropical Storm Kirogi eventually contributed to the formation of Very Severe Cyclonic Storm Ockhi in the North Indian Ocean.^[190][191]

Tropical Storm Kai-tak (Urduja)

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	December 13 – December 23
Peak intensity	75 km/h (45 mph) (10-min); 994 hPa (mbar)

A low-pressure area developed into a tropical depression east of Mindanao late on December 11, and the JMA began to issue tropical cyclone warnings early on the next day.^[192] It entered the Philippine Area of Responsibility nine hours later, receiving the name Urduja^[193] On 21:00 UTC of that same day, the JTWC upgraded the system to a tropical depression and also began issuing advisories, giving the identifier 32W.^[194] Despite the system being poorly organized with loose banding, the system also was located in an area of very low wind shear.^[195] Three hours later, the JMA upgraded the system to a tropical storm, assigning it the international name Kai-tak.^[196]

The city of Tacloban was later placed under a state of calamity as decided by their local council as 80 of the 130 villages were flooded. This resulted in at least 728 families (1,418 individuals) brought to evacuation centers or schools.^[197]

The NDRRMC confirmed a total of 83 people dead and calculated a total of ₱3.747 billion (US$74.3 million) worth of infrastructure and agricultural damages.^[198][123]

Typhoon Tembin (Vinta)

Typhoon (JMA)
Category 2 typhoon (SSHWS)
Duration	December 20 – December 26
Peak intensity	130 km/h (80 mph) (10-min); 970 hPa (mbar)

During December 16, the JMA reported that a tropical depression had developed about 950 km (590 mi) to the southeast of Guam, before they reclassified it as an area of low pressure during the following day.^{[199][200][201]} Over the next few days, the system moved gradually north-westwards in favourable conditions, before it was reclassified as a tropical depression by the JMA during December 20, while it was located to the northeast of Palau.^[34][202] During that day, the JTWC and PAGASA also classified the system as a tropical depression with the latter naming it as Vinta, before the JMA named the system Tembin as it had developed into a tropical storm.^{[203][204][205]}

After the storm, on December 25, two towns in Zamboanga del Norte were under a state of calamity because of the flooding caused by the storm, which also made several roads and bridges impassible as they were covered in mud.^[206]

Rough waves caused by Tembin sank a ferry on December 22, killing five people.^[207] An additional 261 people were also killed due to flooding in Mindanao, of which 135 were reported in the province of Lanao del Norte.^[208] Estimated damages are around ₱2.1 billion (US$42 million).^[209]

Other systems

On March 19, a tropical depression formed close to the northeast of Mindanao, Philippines, and dissipated over the Sibuyan Sea two days later.^[210][211] Early on June 29, the JMA initiated advisories on a newly formed tropical depression located about 138 km (86 mi) south of Okinawa Island.^[212] The system re-curved and started moving in a northeastward direction until it dissipated to the southwest of Tokyo on July 1.^[213] Early on July 4, the JMA indicated that a tropical depression had formed about 505 km (314 mi) south of Okinotorishima.^[214] During the next day, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system, although it was canceled several hours later.^[215] After moving northward, the depression rapidly weakened as it was absorbed by a stationary front on July 7.^[216]

Early on July 13, the JMA reported that a non-tropical low had transitioned into a tropical depression about 75 km (45 mi) north-northeast of Iwo Jima.^[217] The depression moved in a generally northeasterly direction until weakening to a low-pressure area by 06:00 UTC on July 16.^[218] A tropical depression formed about 700 km (435 mi) northeast of Wake Island late on July 25, though the JTWC indicated it as a subtropical system with estimated recorded winds of 65 km/h (40 mph).^[219][220] After several days, the system had already transitioned into an extratropical cyclone on July 29, without becoming a tropical storm.^[221] Early on August 25 the JMA started to track a tropical depression over in the South China Sea,^[222] although it was last monitored during the next day when it was absorbed by the outflow of Tropical Storm Pakhar.^[223] On August 28, the JMA started to issue advisories on a tropical depression that had developed about 1,217 km (756 mi) east-northeast of Tuguegarao City.^[224] The JMA predicted that the system would become a tropical storm within the next 24 hours, although because the system did not develop further, the JMA issued their final advisory on 03:00 UTC of August 29 when the system had weakened into a low-pressure area.^[225] The remnants of the system helped with formation of Tropical Storm Mawar.^[226] On December 29, a weak tropical depression formed south-southwest of Palau. The system later strengthened into Tropical Storm Bolaven during the following year.

International names

During the season 27 tropical storms developed in the Western Pacific and each one was named by the JMA, when the system was judged to have 10-minute sustained windspeeds of 65 km/h (40 mph). The JMA selected the names from a list of 140 names, that had been developed by the 14 members nations and territories of the ESCAP/WMO Typhoon Committee.^[229] During the season, the names Hato and Lan were used for the first time (only time in the case of Hato), after they had replaced the names Washi and Vicente, which were retired after the 2011 and 2012 seasons, respectively.

Philippines

During the season PAGASA used its own naming scheme for the 22 tropical cyclones, that either developed within or moved into their self-defined area of responsibility.^[231][232] The names were taken from a list of names, that was last used during the 2013 season and was used again during the 2021 season.^[231] All of the names are the same except for Lannie, Salome and Yasmin, which replaced the names Labuyo, Santi and Yolanda after they were retired.^[231] The names Lannie and Salome were used for the first time this year.