2018 Pacific typhoon season

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	December 29, 2017 – January 4, 2018
Peak intensity	65 km/h (40 mph) (10-min)  1002 hPa (mbar)

A low-pressure area developed into a tropical depression northeast of Palau on December 29, 2017.[9] The system moved generally westward and on the first day of 2018, the PAGASA began issuing advisories on the system and locally named it Agaton.[10] Both the JMA and the JTWC followed suit, with the latter designating the system as 01W.[11] By January 3, the system had intensified into a tropical storm according to the JMA and was named Bolaven, thus becoming the first named storm of the season. However, several hours later, Bolaven started to weaken and rapidly deteriorate.[12] The system was last tracked by the JMA to the east of Vietnam on January 4.

The impact caused by Bolaven (Agaton) was moderate but not as significant as the previous two systems, Kai-tak and Tembin, with about 2,000 passengers stranded in ports in the Visayas.[13] As of January 22, three people have been reported killed by the storm, while total damages were up to Ph₱554.7 million (US$11.1 million).[14]

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

A low-pressure system developed into a tropical depression north of Chuuk early on February 8. It developed into a tropical storm on February 11, receiving the international name Sanba by the JMA. Shortly afterwards, Sanba entered the Philippine area of responsibility and received the name Basyang by PAGASA.[15] On February 13, Sanba made landfall in Cortes, Philippines,[16] causing it to weaken to a tropical depression. The next day, the system weakened into a remnant low as it made another landfall in Surigao del Sur.[17]

Approximately 17,000 people were affected by the storm and there were 14 fatalities. Total agricultural damages were at Php 168 million (US$3.23 million).[18]

Typhoon (JMA)
Category 4 super typhoon (SSHWS)
Duration	March 24 – April 1
Peak intensity	195 km/h (120 mph) (10-min)  915 hPa (mbar)

On March 24, a tropical depression formed to the south of the Mariana Islands,[19] and the JTWC assigned it the numerical identifier 03W.[20] On March 25, the system intensified into a tropical storm and was named Jelawat by the JMA, and at the sane time it entered PAGASA's Philippine Area of Responsibility (PAR) and was named Caloy.[21] Due to strong southwesterly wind shear, the cyclone remained poorly organized, with disorganized convection near an exposed low-level circulation.[22] Conditions gradually became more favorable for further development, resulting in Jelawat steadily strengthening and organization to a severe tropical storm at 18:00 UTC on March 28.[23] Later on March 29, an eye began to emerge within a growing central dense overcast, leading to the JMA classifying it as a typhoon at 00:00 UTC on March 29.[24] Explosive intensification then ensued over the following 36 hours as the eye became sharply defined, and Jelawat attained its peak intensity later that morning, with estimated 10-minute sustained winds of 195 km/h (120 mph) and a central pressure of 915 hPa (27.02 inHg).[25] At the same time, the JTWC assessed it as peaking with 1-minute sustained winds of 240 km/h (150 mph), making it a Category 4 super typhoon.[26]

Immediately after peaking in intensity, Jelawat began weakening rapidly, due to a sharp increase in wind shear and dry air, and the storm fell below typhoon strength late on March 31. During the next couple of days, Jelawat drifted to the northeast, and then turned eastward, before dissipating on April 1.

Tropical depression (JMA)
Tropical storm (SSHWS)
Duration	May 10 – May 15
Peak intensity	55 km/h (35 mph) (10-min)  1008 hPa (mbar)

A low-pressure area east of Mariana Islands was upgraded to a tropical depression by the JMA late on May 10,[27] shortly before the JTWC issued a TCFA.[28] By May 12, deep convection was observed near its center as the JTWC began issuing advisories on the system giving the designation 04W.[29] Roughly twelve hours later, it was reported that 04W had intensified into a tropical storm by the JTWC after satellite imagery had depicted on a well-defined center.[30] Tracking in a course of a west-northwesterly direction, the system began to weaken as it started entering in an area of unfavorable conditions.[31] Therefore, 04W rapidly weakened as the JTWC issued their final advisory on the system early on May 14, as the system showed a very elongated and exposed center, due to very strong wind shear.[32] The JMA, however, tracked the system until early on May 15, when it finally dissipated.[33]

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	June 2 – June 9
Peak intensity	75 km/h (45 mph) (10-min)  998 hPa (mbar)

A low-pressure area developed into a tropical depression over the South China Sea on June 2.[34][35] Later that day the JTWC followed suit and designated the system as 05W.[36] 05W meandered in a westward direction until it curved northward and after three days, the JTWC upgraded the system to a tropical storm.[37] The JMA did the same three hours later early on June 6, naming it Ewiniar.[38] Shortly thereafter, Ewiniar made landfall over South China. Ewiniar maintained its intensity while over land until the JTWC issued its final advisory late on June 7.[39] The JMA, however, tracked the system until early on June 9, when Ewiniar had weakened into a tropical depression and degenerated into a remnant low.[40] However, Ewiniar's remnant moved out to sea and continued to persist, before dissipating on June 13.

A total of 13 people were killed, while total damages in Mainland China were counted to be ¥5.19 billion (US$812 million).[41]

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	June 3 – June 11
Peak intensity	110 km/h (70 mph) (10-min)  970 hPa (mbar)

A low-pressure area northwest of Palau developed into a tropical depression late on June 3.[42] On the next day, the system received the name Domeng from PAGASA, while the JTWC issued a TCFA for the system.[43][44] After the system had consolidated further, the JMA finally upgraded the system to a tropical storm, naming it Maliksi.[42] The JTWC, however, didn't track the system until 03:00 UTC of June 8 when it also gave the designation 06W.[45] Moving northward, Maliksi continued to intensify until it reached its peak strength early on June 10 with winds of 110 km/h (70 mph), just shy of typhoon intensity, and a minimum pressure of 970 hPa.[42][46] Operationally, the JMA briefly classified Maliksi to a typhoon, but was downgraded to a severe tropical storm in post-analysis.[47] Afterwards, Maliksi began to weaken as it begins its extratropical transition. Encounting unfavorable environments by June 11, both agencies immediately stopped warning on the system as the system's center became exposed as the system was declared as an extratropical cyclone.[42][48] The JMA had tracked the remnants of Maliksi until 00:00 UTC of June 13.[42]

Despite not making landfall in the Philippines, Maliksi prompted the PAGASA to declare the official start of the rainy season on June 8, 2018. Two people were killed by heavy monsoonal rains, enhanced by Maliksi, in the Philippines.[49]

Subtropical storm (SSHWS)
Duration	June 13 – June 15
Peak intensity	65 km/h (40 mph) (1-min)  996 hPa (mbar)

A disturbance formed southwest of Taiwan on June 12, just within the meiyu front, and the JTWC indicated a subtropical depression subsequently.[50] By 21:00 UTC of June 13, the JTWC issued its first advisory on the system, designating it as 07W, and was classified as a tropical depression.[51] Despite located in a moderately to severely sheared environment, the system was located over in relatively warm sea-surface temperatures with patches of convection, and this prompted the JTWC to upgrade 07W to a tropical storm.[52] The JTWC later issued their fourth but final advisory on 07W on 15:00 UTC of June 14, when the system was rapidly undergoing a phase of extratropical transition as the system was losing its structure rapidly.[53] 07W fully became an extratropical cyclone just to the south of mainland Japan on 06:00 UTC of June 15, although its remnant was still tracked until June 25, when the system was last located near the coast of British Columbia.[50]

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

On June 13, a tropical depression formed on the South China Sea, from Tropical Storm 07W's trough. On June 14, the PAGASA announced it had entered the Philippine Area of Responsibility, assigning the name Ester. Tropical Depression Ester (08W) made landfall on Taiwan by midnight, and after emerging off the coast and intensifying into a tropical storm, it had been assigned the name Gaemi by the JMA. On June 16, Gaemi became extratropical. On June 19, the NDRRMC reported that 3 people had died from monsoonal rains enhanced by Gaemi.[54] Agricultural damage in Okinawa Prefecture were about ¥84.58 million (US$764,000).[55]

Typhoon (JMA)
Category 1 typhoon (SSHWS)
Duration	June 28 – July 4
Peak intensity	120 km/h (75 mph) (10-min)  960 hPa (mbar)

A low-pressure area west of Okinotorishima developed into a tropical depression on June 28. On the next day, PAGASA began issuing advisories, giving the name Florita. 6 hours later, Florita became a tropical storm, with JMA assigning Prapiroon for the international name. On June 30, Prapiroon began to intensify into a tropical storm. By July 2, Prapiroon became a Category 1 typhoon, nearing Japan and Korea. By July 3, Prapiroon had attained peak intensity. On the same day, Prapiroon made landfall on Japan. After landfall, Prapiroon briefly weakened to a tropical storm. Prapiroon became a low-pressure area on the next day, though the JMA still tracked its remnants until July 10, when it finally dissipated.[56][57]

As of July 2018, 1 person from South Korea was killed by the storm.[58] Agricultural damage in Okinawa Prefecture were about ¥49.39 million (US$446,000).[59]

Typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	July 3 – July 12
Peak intensity	195 km/h (120 mph) (10-min)  915 hPa (mbar)

A tropical disturbance formed over the Marshall Islands late on June 26.[60] After the slow development and westward drift for five days, the Joint Typhoon Warning Center (JTWC) issued a Tropical Cyclone Formation Alert early on July 2 and upgraded the system to a tropical depression with the designation 10W late on the same day.[61][62] Early on July 3, the Japan Meteorological Agency upgraded the low-pressure area into a tropical depression southeast of Guam and subsequently started to issue tropical cyclone warnings.[63][64] Favorable environmental conditions, including moderate vertical wind shear, poleward outflow enhanced by tropical upper tropospheric trough (TUTT) cells located to the northeast and to the northwest, sea surface temperatures between 30 and 31 °C, were contributing to the development of the system on July 4. As the result, JMA upgraded it to a tropical storm and assigned the international name Maria at around 12:00 UTC,[65] and JTWC also upgraded it to a tropical storm.[66] Six hours later, when the storm struck Guam directly, surface observations at Andersen Air Force Base recorded one-minute maximum sustained winds at 50 knots (93 km/h; 58 mph) and a minimum pressure at 984 hPa (29.06 inHg), indicating a rapidly consolidating system.[67]

On July 5, Maria drifted northwestward slowly under the influences of a weak north-south oriented steering ridge and a strong east-west oriented subtropical ridge entrenched to the north. After being upgraded to a severe tropical storm by JMA and a typhoon by JTWC early on the same day,[68] Maria started extremely rapid intensification due to highly favorable conditions, going from a tropical storm to a Category 5 on the Saffir–Simpson scale in under 24 hours.[69] Microwave imagery revealed an eye and the JMA upgraded Maria to a typhoon in the afternoon.[70] The JTWC upgraded Maria to a super typhoon and reported that it reached its initial peak intensity with one-minute maximum sustained winds of 260 km/h (160 mph) at around 00:00 UTC on July 6,[71] making it the first Category 5-equivalent tropical cyclone in the northern hemisphere since a homonymous Atlantic hurricane in September 2017, and the first in the western Pacific since Typhoon Nock-ten. At around 01:10 UTC on July 11, Maria made landfall over the Huangqi Peninsula of Lianjiang County, Fuzhou in Fujian, China, with ten-minute maximum sustained winds at 155 km/h (100 mph) and a central pressure of 955 hPa (28.20 inHg).[72]

When it made landfall in East China on July 10, it soaked Southern Japan and killed 1 person. Total damages in Mainland China were counted to be CN¥4.16 billion (US$623 million).[41]

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	July 16 – July 24
Peak intensity	75 km/h (45 mph) (10-min)  994 hPa (mbar)

An area of low-pressure strengthened into a tropical depression on July 15, to the northwest of Manila, Philippines.[73] The JTWC designated it as 11W while the PAGASA named it Henry.[73] As the system moved in a fast westward direction, the system gradually intensified and was declared a tropical storm by July 17, with the JMA naming it as Son-Tinh as its convective structure improved.[74] Although from thereafter, Son-Tinh slightly weakened as it neared Hainan island while experiencing moderate shear.[75] During the next day, however, Son-Tinh slightly intensified over in the Gulf of Tonkin due to warm sea-surface temperatures before it made landfall in northern Vietnam.[76] Both agencies issued their final warning on Son-Tinh on July 19 as the system had weakened back into an area of low-pressure embedded by the monsoon.[77] However, the JTWC continued to track the system's remnant low for another two days, before it finally dissipated.[78]

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

On July 17, a weak tropical depression had developed over in the Philippine Sea. With some deep convection and the system located in favorable environments, the JTWC began tracking on the system, designating it as 12W.[79] By the next day, the PAGASA followed suit and was locally named as Inday. By 12:00 UTC of July 18, the system had intensified into a tropical storm and was named Ampil.[80] As Ampil moved in a northward direction, the system's structure had broadened along with sustained deep convection.[81] Despite an unfavorable ocean heat content, Ampil still remained over relatively warm sea-surfaces temperatures with the inclusion of an extensive deep convection,[82] therefore Ampil was classified as a severe tropical storm. With an improved convective system, the JTWC assessed that Ampil had reached 1-minute peak winds of 95 km/h (60 mph).[83] Ampil reached its peak intensity with a minimum pressure of 985 hPa and maintained that intensity for the next few days, despite with the change of direction. On July 21, the system's center became exposed as the system slightly weakened.[84] By the next day, the JMA downgraded Ampil back to a tropical storm, as the system made landfall over China with a lack of convection.[85] Ampil weakened further to a tropical depression on July 23, and both agencies issued their final advisory on the system.[86] The JMA continued tracking the system until it weakened into an area of low pressure, at 18:00 UTC on July 24.[87]

Heavy rain in Shandong Province—accumulating to 237 mm (9.3 in) in Tianjin—caused significant flooding, inundating 31,600 hectares of crops and affecting 260,000 people. One person was killed in China and total economic losses reached CN¥1.63 billion (US$241 million).[41]

Tropical depression (JMA)
Tropical storm (SSHWS)
Duration	July 20 – July 23
Peak intensity	55 km/h (35 mph) (10-min)  996 hPa (mbar)

A tropical depression formed on the South China Sea on July 20, according to the JMA. On July 21, the system entered the PAGASA's Philippine Area of Responsibility or PAR, and was named Tropical Depression Josie, the 10th named storm to enter the PAR this season. Tropical Depression Josie (13W) missed kilometers off of landfall in Saud, Ilocos Norte. It moved north, and exited the PAR by the next day. While approaching China, 13W is about to become a named tropical storm, but missed tropical storm strength and was destroyed by high wind shear near China. The remnants of 13W headed inland to mainland China, where it fully dissipated.

Since the formation of the previous two systems, the southwest monsoon had been extremely active in the Philippines. By August 1, a total of 16 people had been killed due to extreme flooding, while damages have been recorded at ₱4.66 billion (US$87.4 million). The southwest monsoon had been active since Typhoon Maria. July had 5 days of class suspensions in Metro Manila, second in history since Typhoon Ketsana struck Metro Manila and caused ocean-high flooding since 2009.[88]

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

Late on July 21, the JTWC began to issue advisories on Tropical Depression 14W that had developed about 603 km (381 mi) east-southeast of the Japanese island of Minami-Tori-shima.[89] The JMA, however, began tracking the system until the early hours of July 22. Later that day, the JTWC upgraded 14W to a tropical storm, despite the fact that convection had been sheared and the system was located in unfavorable southwesterly shear.[90] Within the next 24 hours, 14W began to organize with deep convection obscuring its LLCC,[91] and on 12:00 UTC of July 23, the JMA upgraded the system to a tropical storm, naming it Wukong. Moving poleward, Wukong gradually intensified while entering in an area of favorable environment with lesser shear and on 00:00 UTC of July 25, the JMA upgraded Wukong to a severe tropical storm. Nine hours later, the JTWC upgraded Wukong to a Category 1 typhoon after satellite images depicted a 30-nmi ragged eye.[92] Though by July 26, both the JMA and the JTWC issued their final advisory on Wukong as the system had rapidly transitioned into an extratropical cyclone.[93] Wukong's extratropical remnants was tracked until late on July 27 when it was last noticed off the eastern coast of Russia Far East.[94]

Typhoon (JMA)
Category 2 typhoon (SSHWS)
Duration	July 23 – August 4
Peak intensity	140 km/h (85 mph) (10-min)  960 hPa (mbar)

A tropical disturbance formed southeast of Guam on July 19 and tracked westward steadily.[95] After issuing a Tropical Cyclone Formation Alert on July 21, the Joint Typhoon Warning Center (JTWC) upgraded the system to a tropical depression early on July 22, although the location of its low-level circulation center was not clear.[96] The Japan Meteorological Agency (JMA), however, kept reporting it as a low-pressure area until it was upgraded to a tropical depression late on July 23.[97] After the slow consolidation for several days, the system was upgraded to a tropical storm near Okinotorishima at around 18:00 on July 24 by agencies such as JMA and JTWC, with an international name Jongdari.[98][99] A microwave imagery revealed a low-level forming eyewall next day, indicating a consolidating system. After JMA upgraded Jongdari to a severe tropical storm at noon,[100] the system accelerated northeastward under the influence of a near-equatorial ridge to the south.[101]

On July 26, as Jongdari started to interact with an upper-level cold-core low to the north which significantly enhanced poleward outflow,[102] it intensified to a typhoon in the afternoon despite increasingly unfavorable vertical wind shear.[103] Over the warm sea surface temperatures between 29 to 30 °C (84 to 86 °F) near the Ogasawara Islands, JMA reported that Jongdari had reached peak intensity at 00:00 UTC on July 27, with ten-minute maximum sustained winds of 140 km/h (85 mph), and a minimum central pressure of 965 hPa (28.50 inHg).[104] Although JTWC indicated Jongdari reached peak intensity at 12:00 UTC with one-minute maximum sustained winds of 175 km/h (110 mph), the rugged eye of Jongdari kept periodically visible with an elongated structure due to the further interaction of the upper-level low which had moved to the northwest side of the typhoon. As the steering influence transitioned to a subtropical ridge to the northeast, Jongdari executed a counter-clockwise turn to the southeast of Japan.[105]

Jongdari began to be inundated by subsidence on July 28, as the Fujiwhara effect had made the upper-level low move to the west of the typhoon.[106] It also initiated a weakening trend while accelerating northwestward and then westward toward the Japanese island of Honshu. At around 01:00 JST on July 29 (16:00 UTC July 28), Jongdari made landfall over Ise, Mie Prefecture with ten-minute maximum sustained winds at 120 km/h (75 mph) and the central pressure at 975 hPa (28.79 inHg).[107][108] The storm weakened rapidly inland and made its second landfall over Buzen, Fukuoka Prefecture, at around 17:30 JST (08:30 UTC), with ten-minute sustained winds of 75 km/h (45 mph) and a central pressure of 992 hPa (29.29 inHg).[109] At around 10:30 CST (02:30 UTC) on August 3, Jongdari made landfall over Jinshan District, Shanghai as a tropical storm.[110] Jongdari rapidly weakened after landfall, dissipating on the next day. No fatalities were recorded for this storm.

Tropical depression (JMA)
Tropical depression (SSHWS)
Duration	July 31 – August 1
Peak intensity	55 km/h (35 mph) (10-min)  1002 hPa (mbar)

A tropical disturbance developed about 807 km (503 mi) north-northeast of Iwo To by July 29.[111] The JTWC upgraded the system to Tropical Depression 16W during the next day after its convective structure had slightly improved despite the system located in moderate to strong wind shear.[112] By July 31, the JMA followed suit on classifying the system as a tropical depression.[113] 16W's center late became exposed with deep convection displaced due to continued shear.[114] Originally, the system was forecast to reach tropical storm intensity with only 35 knot winds,[115] but the system's center had become asymmetric with a fully sheared center.[116] The JTWC issued their final advisory on 21:00 UTC of the same day, after 16W had fully transitioned into a subtropical cyclone, though both agencies continued to track the system until August 2.[117][118]

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

A tropical depression had developed to the east-northeast of Guam on August 2. On 21:00 UTC of the same day, the JTWC began tracking the system, giving the identifier 17W.[119] 17W intensified into a tropical storm on August 3, with the JMA naming it as Shanshan.[120] The storm was located over in favorable environments as the system was gradually consolidating,[121] therefore Shanshan intensified into a severe tropical storm. During the next day, both the JMA and JTWC upgraded Shanshan to a typhoon after deep convection was seen wrapping into its developing center. The JMA later analysed that the storm had reached 10-minute winds of 130 km/h (80 mph) and a minimum pressure of 970 hPa, and remain that intensity for several days. Though the JTWC stated that Shanshan had slightly weakened after a strengthening trend by August 6 after its eye became ragged and slightly displaced. However, on August 7, Shanshan began to re-intensify and reached its peak strength as a Category 2 typhoon with 1-minute winds of 165 km/h (105 mph) while nearing the coast of southeastern Japan. Thereafter, Shanshan began to change its course towards the east as it rapidly weakened. The JTWC issued their final advisory on August 9, though the JMA tracked the system until it became extratropical at 06:00 UTC on August 10.

Losses in Miyagi Prefecture were counted at ¥96.2 million (US$866,000).[122]

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	August 6 – August 15
Peak intensity	75 km/h (45 mph) (10-min)  990 hPa (mbar)

A tropical disturbance had persisted towards the southwest of Iwo To on August 1.[123] After the course of five days, the system finally strengthened into a tropical depression by the JMA, with the JTWC following suit several hours later (designating it as 18W).[124] The PAGASA also began issuing bulletins to the system, locally assigning the name Karding. Karding maintained its intensity as a tropical depression due to moderate to strong easterly shear, despite persistent convection surrounding the system.[125] By August 8, a METOP-A ASCAT image showed that the system had winds of 35 knots, hence the JTWC upgrading it to a tropical storm.[126] The JMA around the same time did the same, naming it Yagi. Within the next day, Yagi curved towards the northwest while continuously battling shear as it struggled to intensify. Though by 12:00 UTC of August 11, the JMA considered that Yagi reached its peak strength with 10-minute winds of 75 km/h (45 mph) and a minimum pressure of 990 hPa.

The JTWC declared that Yagi reached winds of 85 km/h (50 mph) on 12:00 UTC of August 12 after the storm had consolidated further with an improved structure.[127] Yagi made landfall shortly thereafter over Wenling, in Taizhou of Zhejiang, China, at around 23:35 CST (15:35 UTC) on August 12.[128] By 21:00 UTC of that day, the JTWC issued their final advisory on Yagi,[129] but continued to track it until it weakened further into a tropical depression early on August 13.[130] The JMA did the same on 06:00 UTC of August 13, but continued to tracked it until it became an extratropical system on August 15.

Although Yagi (Karding) didn't make landfall in the Philippines, the storm enhanced the southwest monsoon which brought extreme flooding towards many regions within the country. According to the NDRRMC, 5 people died along with ₱996 million (US$19 million) worth of damages.[131] In East China, Yagi killed a total of 3 people and total damages were counted to be CN¥2.51 billion (US$367 million).[41]

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

On August 9, a tropical depression formed within the South China Sea. The system remained weak and remained stationary for a few days until the JTWC began tracking on the system, designating it as 20W on August 12.[132] By August 13, the JMA finally upgraded the system to a tropical storm, naming it Bebinca. The JTWC followed suit nine hours later when they found flaring deep convection near its compact center.[133] Despite consistent convection along with warm sea-surface temperatures, Bebinca remain weak for the next few days due to strong shear.[134] Although by August 16, Bebinca began to undergo a phase of rapid intensification as its center was obscured by a central dense overcast,[135] and thus, the JMA briefly upgraded Bebinca to a severe tropical storm. The JTWC analysed a few hours later that the system had reached peak intensity with 1-minute winds of 110 km/h (70 mph). After Bebinca made landfall, the system rapidly weakened and both agencies issued their final warning on August 17, and fully dissipated that same day.

Bebinca killed a total of 6 people and total economic losses in South China were counted to be ¥2.31 billion (US$333 million).[41] 13 people lost their lives in Vietnam and total damages were counted to be ₫786.55 billion (US$33.7 million).[136][131]

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

On August 11, a tropical depression became Tropical Storm Leepi the next day. By August 13, Tropical Storm Leepi threatened Japan. By August 14, Leepi became a severe tropical storm or a Category 1 typhoon for JTWC. Shortly before 03:00 JST (18:00 UTC) on August 15, Leepi made landfall over Hyūga, Miyazaki in Japan. It finally dissipated on August 15 as an extratropical system with no more energy left. Still, its remnants still headed out to mainland Russia.[137] Leepi dissipated on August 16, after the system was last tracked east of South Korea as a remnant low.

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	August 13 (Entered basin) – August 16
Peak intensity	75 km/h (45 mph) (10-min)  998 hPa (mbar)

On August 13 at 18:00 UTC, both the JMA and the JTWC declared that Tropical Storm Hector from the East Pacific basin had crossed the International Date Line and entered the West Pacific basin.[138] At this point, Hector was still located in a favorable environment with only moderate shear, though deep convection was limited as it only persisted just near its center.[139] Due to an upper tropospheric trough cell located to the west of Hector, the storm failed to intensify and began to weaken.[140] The JTWC downgraded Hector to a tropical depression after the system rapidly entered an area of high vertical wind shear.[141] By the early hours of August 15, both agencies issued their final warning on Hector, mentioning that Hector's low-level circulation had become elongated and that the storm already transitioned into a subtropical cyclone.[142] The JMA, however, continued to monitor the system until 00:00 UTC on August 17.

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

On August 15, a tropical depression in the East China Sea strengthened into Tropical Storm Rumbia. Shortly after reaching peak intensity over the Hangzhou Bay on August 16, Rumbia made landfall over Pudong New Area, Shanghai, China at around 04:05 CST on August 17 (20:05 UTC), becoming the third tropical storm to hit Shanghai in 2018.[143]

Rumbia killed a total of 53 people in East China and total economic losses were counted to be CN¥36.91 billion (US$5.36 billion).[41] Shouguang received 174.7 mm (6.88 in) of rain and was particularly hard-hit, with 10,000 homes destroyed and 13 people killed. The city is regarded as the nation's greatest producer of vegetables and agriculture suffered tremendous losses; 200,000 greenhouses sustained damage. Upstream on the Mi River rainfall reached 241.6 mm (9.51 in) and caused significant flooding. Water levels at three reservoirs rose dangerously high, prompting officials to release excess water to avoid collapse. The resulting increase downstream exacerbated the flooding in Shouguang. The extratropical remnants of Rumbia was last tracked northeast of Hokkaido before finally dissipating off the coast of the Russian Far East.[144]

Typhoon (JMA)
Category 3 typhoon (SSHWS)
Duration	August 15 – August 24
Peak intensity	155 km/h (100 mph) (10-min)  950 hPa (mbar)

A low-pressure area in the Philippine Sea organized into a tropical depression late on August 15. The JTWC followed suit at 00:00 UTC at August 16 and was designated as 22W. Later on that day, the JMA upgraded 22W to tropical storm and it was given the international name Soulik. On August 17, JMA upgraded Soulik to a typhoon, marking the sixth typhoon of the season. Then Soulik rapidly intensified onto a severe typhoon, and on the next day, Soulik reached its peak intensity, with winds of 165 km/h (103 mph), and remained that intensity for several days. It also began to display some annular characteristics. After passing the Ryukyu Islands early on 22 August, the storm gradually weakened due to low sea-surface temperatures. On August 23, Soulik made landfall over Haenam County, South Jeolla Province of South Korea at around 23:00 KST (14:00 UTC).[145]

Total damage in South Korea were at ₩50.7 billion (US$45 million).[146] Economic loss in Northeast China were counted to be CN￥550 million (US$79.9 million).[147] Flooding in North Korea triggered by Soulik killed 86 people.[148]

Typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	August 17 – August 24
Peak intensity	155 km/h (100 mph) (10-min)  950 hPa (mbar)

On August 17, a tropical depression formed near the Marshall Islands. It was named Tropical Storm Cimaron a day later. Soon after, it was upgraded to a Severe Tropical Storm. Cimaron gradually intensified over the course from August 20–22. Typhoon Cimaron threatened Southern Japan, as the same time as Typhoon Soulik ravaged the area. Typhoon Cimaron intensified to reach its peak intensity at Category 4 severe typhoon with 130 mph winds before its landfall in Japan on August 23 over the southern part of Tokushima Prefecture, Japan at around 21:00 JST (12:00 UTC). Typhoon Cimaron emerged off the north coast as a weak tropical storm, before becoming extratropical and headed into Northern Japan again. Cimaron was a significant Category 4 storm, and the 12th typhoon to strike Japan in 2018 and was surpassed by Typhoon Jebi a month later.[149] Then, it made landfall over Himeji, Hyōgo Prefecture shortly before 24:00 JST (15:00 UTC).[150]

Agricultural damage in Kyoto, Wakayama and Shiga Prefecture were about JP¥3.41 billion (US$30.6 million).[151]

Tropical depression (JMA)
Tropical depression (SSHWS)
Duration	August 21 – August 26
Peak intensity	55 km/h (35 mph) (10-min)  996 hPa (mbar)

A tropical depression formed at the South China Sea near Taiwan.[152] Despite entering an area of high wind shear, the system was in a favorable environment, so the JTWC and the PAGASA followed suit, with the JTWC naming it 24W, and the PAGASA named it Luis. 24W then made landfall over Fujian, China shortly after 08:00 CST (00:00 UTC) on August 25, and degenerated into a low-pressure area on next day.[153][154] The JMA would continue monitoring the system until the next day.[152]

Tropical Depression 24W killed 7 people and damages of NT$1.022 billion (US$34 million)in Taiwan.[131]

Typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	August 26 – September 4
Peak intensity	195 km/h (120 mph) (10-min)  915 hPa (mbar)

A low-pressure system formed near the Marshall Islands on early August 25, developing and being upgraded to a tropical depression on August 27 by the Japan Meteorological Agency (JMA). There was a persistent deep convection in the system which lead to the upgrade to a tropical storm by the JMA and was given the name 'Jebi'. On August 29, the storm abruptly underwent rapid intensification and became the third super typhoon and the second category 5 of the season. On September 4, a weakened but still powerful Jebi made landfall over the southern part of Tokushima Prefecture at around 12:00 JST (03:00 UTC) before moving over Osaka Bay and making another landfall at around Kobe, Hyōgo Prefecture at around 14:00 JST (05:00 UTC). Osaka was hit badly with a maximum wind gust of 209 km/h recorded at Kansai International Airport and 171 km/h at Osaka city's weather station, where the minimum sea level pressure (962 mb) was the lowest since 1961's record of 937 mb (Typhoon Nancy) and the fifth lowest on record. A 3.29 metre storm surge led to flooding along the Osaka Bay, including Kansai International Airport, where the runways were flooded and some airport facilities were damaged by wind and water. Osaka's iconic Universal Studios Japan was also closed during the event of the typhoon. Wakayama also recorded a maximum wind gust of 207 km/h. Jebi then moved over Kyoto which wrecked more havoc. Multiple shrines were closed during the duration of the typhoon. Kyoto Station received a lot of damage, the glass above the atrium covering the central exit, shops and hotel, collapsed, narrowly missing a few by centimeters. The typhoon ultimately emerged into the Sea of Japan shortly after 15:00 JST (06:00 UTC). Simultaneously, a cold front formed southwest of the typhoon, initiating the beginning of an extratropical transition on September 4. On September 5, after JTWC issued a final warning at 00:00 JST (15:00 UTC), Jebi was downgraded to a severe tropical storm at 03:00 JST (18:00 UTC) when it was located near the Shakotan Peninsula of Hokkaido. The storm completely transitioned into a storm-force extratropical cyclone off the coast of Primorsky Krai, Russia shortly before 10:00 VLAT (09:00 JST, 00:00 UTC). Later, the extratropical cyclone moved inland. The terrain of Khabarovsk Krai contributed to the steadily weakening trend as the system moved inland northwestward and then northward; extratropical low passed northeast of Ayan early on September 7. Jebi's extratropical remnant continued northward and then turned northeastward, before dissipating early on September 9 over the Arctic Ocean.

Jebi was the strongest storm to hit Japan since Typhoon Yancy of 1993. In total, Jebi killed 17 people and inflicted around US$15 billion. 11 deaths were reported from Japan and 6 deaths were reported from Taiwan.

Typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	September 6 – September 17
Peak intensity	205 km/h (125 mph) (10-min)  905 hPa (mbar)

On September 6, a tropical depression formed near the Marshall Islands.[155] However, operationally, the Japan Meteorological Agency (JMA) did not initiate advisories on the system until September 7. The JTWC followed suit at 03:00 UTC on September 7, and classified the system as 26W. Late on the same day, the system strengthened into a tropical storm, and the JMA named the system Mangkhut. By September 11, Mangkhut became a typhoon, and made landfall on the islands of Rota, Northern Mariana Islands. On September 12, at 3 pm Philippine Standard Time, Mangkhut entered the PAR as a Category 5 super typhoon, and accordingly, PAGASA named the storm Ompong. The JTWC noted additional strengthening on September 12, and assessed Mangkhut to have reached its peak intensity at 18:00 UTC, with maximum one-minute sustained winds of 285 km/h (180 mph). On September 13, the Philippine Government initiated evacuations for residents in the typhoon's expected path. Late on September 14, Mangkhut made landfall on the Philippines as a Category 5-equivalent super typhoon, with 1-minute sustained winds of 165 miles per hour (266 km/h).[156] While moving inland, Mangkhut weakened into a strong Category 4-equivalent super typhoon, and soon weakened further into a Category 2 typhoon. A large eye then appeared and the system slowly strengthened into a Category 3 typhoon, as the storm moved over Hong Kong. As Mangkhut made its final landfall, it weakened into a weak Category 1 typhoon and maintained its intensity inland with deep convection, before subsequently weakening further. Late on September 17, Mangkhut dissipated over Guangxi, China.

As of September 23, at least 134 fatalities have been attributed to Mangkhut, including 127 in the Philippines,[157][158] 6 in mainland China,[159] and 1 in Taiwan.[160] As of October 5, the NDRRMC estimated that Mangkhut caused ₱33.9 billion (US$627 million) in damages in the Philippines, with assessments continuing.[161]

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

On September 8, a tropical depression formed near Batanes in the Philippines. The storm was named Tropical Depression Neneng by PAGASA, with Batanes placed under TCWS #1. By the next day, Neneng exited the PAR and became a tropical storm, with the JMA assigning the name Barijat to the storm, while TCWS were raised in the absence of the storm. Over the next 2 days, Tropical Storm Barijat moved westward across the South China Sea, reaching its peak intensity with 10-minute maximum sustained wind speeds of 85 km/h on the night of September 11.[162] On September 13, Tropical Storm Barijat (Neneng) made landfall on the Leizhou Peninsula, near the area where Tropical Storm Son-tinh (Henry) had made landfall 2 months ago, before making a second landfall in northern Vietnam later on the same day. During the evening of September 13, Barijat became a remnant low, dissipating on the next day.

Tropical Storm Barijat made a dozen landslides over Batanes, which increased the risk of major landslides and major flooding in the saturated soil influenced by this storm and later by Mangkhut (Ompong). Damages in China were at ¥50 million (US$7.3 million).[41]

Typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	September 20 – October 1
Peak intensity	195 km/h (120 mph) (10-min)  915 hPa (mbar)

On September 19, the NRL began to monitor a large tropical disturbance that formed near Chuuk in the Federated States of Micronesia. The system drifted westwards and strengthened into a tropical depression on September 20 according to the JMA, while the JTWC issued a TCFA. Trami managed to find itself in favorable conditions for strengthening and on September 21, it gained tropical storm status and was named Trami. On September 22, Trami still strengthened and became a Severe Tropical Storm before strengthening to a Category 1 typhoon. On September 23, Trami, yet again in favorable conditions, continued to strengthen and became a Category 3-equivalent typhoon while undergoing an eyewall replacement cycle at the same time. Early on September 24, Trami strengthened further and attained Category 4 super typhoon status once it finished its eyewall replacement cycle. At 18:00 UTC on September 24, Trami strengthened even further and subsequently became a Category 5 super typhoon. On its route to Okinawa, Japan, Trami slowed down considerably and was almost stationary before moving north-northeastward. During this period of time, another eyewall replacement cycle that eventually failed later on, coupled with decreasing sea surface temperatures, started to slowly weaken Trami, although it still remained an organized storm. On September 30, Trami reached the most organized point of its duration after its peak, but Trami's structure started to deteriorate afterward, and the storm's winds gradually dropped as Trami resumed weakening. The typhoon made landfall over Tanabe, Wakayama Prefecture at around 20:00 JST (11:00 UTC) on September 30[163] as a Category 2-equivalent typhoon. The storm's structure deteriorated rapidly after landfall, and the JMA issued their last advisory on Trami on October 1. After Trami impacted Honshu, it completely transitioned into a hurricane-force extratropical cyclone and impacted the Kuril Islands and weakened to a storm-force system. Its extratropical remnants were last tracked in the Bering Sea, near the Aleutian Islands.

Agricultural damage in Japan were at ¥61.65 billion (US$542 million).[164]

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

On September 25, a tropical depression formed to the southeast of Japan. The JTWC gave the system the designation 29W on next day.[165] However, Tropical Depression 29W remained a weak system, and developed an exposed low-level circulation center later that day. Afterward, the tropical depression accelerated northward and then north-northeastward, until it was eventually absorbed into a developing extratropical cyclone east of Japan on September 27.[166][167]

Typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	September 28 – October 6
Peak intensity	215 km/h (130 mph) (10-min)  900 hPa (mbar)

In late September, a tropical disturbance formed in the waters near Pohnpei Island in the Federated States of Micronesia. The Joint Typhoon Warning Center also gave the storm, Invest 94W, a low chance of development.[168] Over the next couple of days, the system moved westward and organized into a tropical depression on September 27, and the JMA initiated advisories on the storm, while the JTWC issued a TCFA. On September 28, the JTWC designated the system as 30W,[169] while the JMA issued a gale warning for the system.[170] As Tropical Depression 30W continued strengthening, the system became a tropical storm and was named Kong-rey by the JMA. On September 29, the system moved further west, found itself in favorable conditions for strengthening, and became a tropical storm. Later that day, Kong-rey strengthened into a severe tropical storm, and on September 30, the storm attained typhoon status at 03:00 UTC. Kong-rey continued strengthening, and at 18:00 UTC on October 1, Kong-rey became a Category 4-equivalent super typhoon. Early on October 2, Kong-rey strengthened into a Category 5 super typhoon. Affected by vertical wind shear, low ocean heat content and decreasing sea surface temperatures, the storm gradually weakened to a Category 3 typhoon on October 3 while undergoing an eyewall replacement cycle.[171] Increased vertical wind shear and lower sea surface temperatures hampered Kong-rey's strength, and Kong-rey was downgraded to a tropical storm on October 4. Early on October 6, Kong-rey made landfall in Tongyeong, South Gyeongsang Province in South Korea as a high-end tropical storm,[172] and later on the same day, Kong-rey transitioned into an extratropical cyclone, while impacting southern Hokkaido, such as areas near Hakodate.

As of October 2018, 3 people have been killed by the storm, including 2 people from South Korea.[173] Damage nationwide totaled at ₩54.9 billion (US$48.5 million).[174] Although Kong-Rey did not make a direct landfall on Kyushu and Shikoku, its outer rainbands affected the two islands. At an area in Shikoku, rain accumulated to 300 mm. In Nagasaki, more than 12,000 families lost power;[175] in Fukuoka Prefecture, a person died because of the rain.[176] Agricultural damage in Okinawa and Miyazaki Prefecture were about JP¥13.99 billion (US$123 million).[177][178]

Unrelated to Kong-rey, Hurricane Walaka was a Category 5 hurricane at the same time Kong-rey intensified to Category 5 super typhoon intensity, marking the first time since 2005 when two tropical cyclones of Category 5 strength existed simultaneously in the Northern Hemisphere.[179]

Typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	October 21 – November 3
Peak intensity	215 km/h (130 mph) (10-min)  900 hPa (mbar)

Early on October 21, a tropical depression developed to the east of Guam and the Northern Mariana Islands, with the JMA initiating advisories on the system. Shortly afterward, the JTWC assigned the storm the identifier 31W. The system began to strengthen, becoming a tropical storm several hours later, and the JMA named the system Yutu. Favorable conditions, including low wind shear and high ocean-surface temperatures, allowed Yutu to explosively intensify on the following day, with the storm reaching severe tropical storm strength and then typhoon intensity a few hours later. From October 23 to 24, Yutu continued to organize and explosively intensify, reaching Category 5 super typhoon intensity on October 24. The typhoon continued to strengthen and displayed a healthy convective structure, while moving towards the island of Saipan. Later on the same day, Typhoon Yutu made landfall on the island of Tinian, just south of Saipan, at Category 5 intensity, with 1-minute sustained winds of 285 km/h (175 mph), becoming the most powerful storm on record to impact the northern Mariana Islands.[180][181]

After making landfall in Tinian, Yutu underwent an eyewall replacement cycle, which it successfully completed on the next day, and the storm strengthened back to Category 5 super typhoon status on October 26, at 15:00 UTC.

On October 27, Yutu's eye became cloud-filled, indicative of weakening, and the storm weakened to a Category 4 super typhoon. On the same day, the storm entered PAGASA's area of responsibility, and Yutu was given the name Rosita by PAGASA. On October 28, Yutu quickly weakened, as ocean sea-surface heat content significantly declined.

After making landfall on October 30, Yutu rapidly weakened, and when it emerged over the South China Sea, low ocean heat content and westerly wind shear caused Yutu to weaken below typhoon status. On November 2, Yutu weakened into a remnant low off the coast of China, before dissipating on the next day.

On October 25, in Saipan, the typhoon killed a woman when it destroyed the building she was staying in, and injured 133 other people, three of whom were severely injured. On Saipan and nearby Tinian, high winds from Yutu knocked down more than 200 power poles. Most of the buildings in southern Saipan lost their roofs or were destroyed, including a high school that was wrecked.[182]

Severe tropical storm (JMA)
Category 2 typhoon (SSHWS)
Duration	November 14 – November 26
Peak intensity	110 km/h (70 mph) (10-min)  990 hPa (mbar)

On November 3, the Central Pacific Hurricane Center began monitoring a disturbance that had formed in the Central Pacific basin.[183] This disturbance soon moved out of the basin and into the West Pacific without further development on November 6.[184] Tracking westward, the system did not organize until late on November 18, when it reached tropical depression status on the Saffir-Simpson scale. The PAGASA named the system Tropical Depression "Samuel" and issued warnings for Mindanao and Visayas. Samuel made landfall on November 20 in the Philippines, crossing the archipelago and weakening slightly. Samuel began to restrengthen over the South China Sea, and was subsequently named "Usagi". Usagi underwent rapid intensification, and became a severe tropical storm on November 21 while moving slowly. By November 22, Usagi (Samuel) intensified into a Category 1 typhoon. On November 24, Usagi weakened back to a severe tropical storm while heading to Vietnam because of the land interaction.

Usagi caused one death in the Philippines, and the agricultural damage were at Php 52.2 million (US$994,000).[185][186] On November 25, Usagi made landfall in Mekong Delta. The typhoon caused flooding in Ho Chi Minh City and killed three people.[187] Losses in Vietnam were at ₫925 billion (US$39.5 million).[188]

Tropical storm (JMA)
Tropical depression (SSHWS)
Duration	November 16 – November 18
Peak intensity	65 km/h (40 mph) (10-min)  1004 hPa (mbar)

A low pressure system exited the PAR on November 15. Late on November 16, a tropical disturbance formed east of Vietnam. It slowly tracked west-northwest and strengthened into a tropical-depression strength storm early on November 17. Toraji made landfall on November 18 and quickly weakened; the remnants emerged into the Gulf of Thailand, and the remnants briefly reorganized, regaining tropical-depression strength on November 20. However, as Toraji made a second landfall on the Malay Peninsula, it weakened once more and dissipated late on November 21, due to wind shear over the Strait of Malacca.

Toraji caused flooding in Nha Trang, resulting in 20 dead and ₫1.24 trillion (US$53.6 million) in damages.[189]

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

On November 19, a tropical depression formed well east of the Philippines and intensified into a tropical storm soon thereafter, receiving the name Man-yi. After reaching typhoon status on November 21, Man-yi entered the Philippine basin and received the name Tomas from PAGASA. Shortly after, Man-yi intensified into a Category 2 typhoon. However, after completing an anticyclonic loop due to the influences of nearby weather systems, entering and exiting the PAR multiple times, Man-yi dipped to Category 1 status and moved into cooler waters. Succumbing to hostile conditions, Man-yi weakened into a tropical storm once more on November 25 and degenerated into a tropical depression by the end of the next day, while tracking northeast, and became an extratropical cyclone.

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

A tropical depression formed in the Philippine Sea on December 25. It entered the PAR later that evening and the PAGASA named the significant tropical depression "Usman". Usman made its first landfall in Samar, Eastern Visayas on December 28. It passed over Palawan and other areas in the weekend. Usman did not survive the passage of the Philippines and degenerated into a remnant low. The remnants of 35W were absorbed by an invest on December 30 which would later become Tropical Storm Pabuk.[190]

While passing over the Philippines, Usman brought heavy rains that caused several landslides, which killed 156 people, with damages amounting to Php5.41 billion (US$103 million).[191]

On June 4, the JMA began tracking on a weak tropical depression that had formed northeast of Yap.[192] However, the system was absorbed by a nearby tropical depression, which would eventually become Severe Tropical Storm Maliksi on the next day.[43] After Gaemi became extratropical, a tropical depression formed south of Hong Kong early on June 17, and dissipated over the east coast of Guangdong, China one day later.[193][194] On July 16, a tropical depression developed over the South China Sea. The system remained weak and moved into Vietnam, before dissipating on the next day. On August 4, the JTWC began to track a subtropical storm that had developed just west of the International Date Line; the storm subsequently became extratropical on the next day.[195]

A tropical depression formed southeast of Okinawa on August 24; two days later, it made landfall over Shanghai and quickly dissipated over Jiangsu, in East China.[196][197][198] The remnants associated with Hurricane Olivia entered this basin on September 19,[199][200] and it developed into a tropical depression on September 21, while slowly drifting westward.[201] Two days later, it degenerated into a remnant low again, as the JMA reported the system's dissipation.[202][203] On September 25, the system's remnant energy developed into Tropical Depression 29W.

On October 19, the JMA began tracking a tropical depression in the Gulf of Thailand. On October 20, the tropical depression made landfall on the Malay Peninsula and weakened into a remnant low, before moving out of the basin.

A tropical depression formed over the southern portion of the South China Sea on December 31,[204] with the JTWC designation 36W.[205] The system intensified into Tropical Storm Pabuk on January 1, 2019, becoming the first named storm of the 2019 Pacific typhoon season.[206]

During the season 28 tropical storms developed in the Western Pacific and each one was named by the JMA, when the system was judged to have 10-minute sustained windspeeds of 65 km/h (40 mph). The JMA selected the names from a list of 140 names, that had been developed by the 14 members nations and territories of the ESCAP/WMO Typhoon Committee. During the season, the names Ampil, Jongdari and Barijat were used for the first time, after they replaced the names Bopha, Sonamu and Utor which were all retired after the 2012 and 2013 seasons respectively.

After the season, the Typhoon Committee announced that the names Rumbia, Mangkhut, and Yutu were removed from the naming lists.[209][210] They were replaced with Pulasan and Krathon, respectively, while the replacement name for Yutu will be announced in 2021.

During the season PAGASA used its own naming scheme for the 21 tropical cyclones, that either developed within or moved into their self-defined area of responsibility. The names were taken from a list of names, that had been last used during 2014 and are scheduled to be used again during 2022. The names Gardo, Josie, Maymay, Rosita, Samuel and Usman were used for the first (and only, in the cases of Rosita and Usman) time during the year after the names Glenda, Jose, Mario, Ruby, and Seniang were retired, as both the names Ruby and Rosita were used only for the first times due its damages in the Philippines.

After the season, the names Ompong, Rosita and Usman were retired, as they caused ₱1 billion in damages. Rosita and Usman were only used for the first and last time. They were replaced with Obet, Rosal and Umberto for the 2022 season.[211]