2018 Pacific typhoon season

Tropical Storm Bolaven (Agaton)

Tropical storm (JMA)
Tropical depression (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.^[8] 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.^[9] Both the JMA and the JTWC followed suit, with the latter designating the system as 01W.^[10] 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.^[11] 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.^[12] As of July 5, three people have been reported killed by the storm, while total damages were up to 554.7 million pesos (US$11.1 million).^[13]

Tropical Storm Sanba (Basyang)

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.^[14] On February 13, Sanba made landfall in Cortes, Philippines,^[15] 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.^[16]

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

Typhoon Jelawat (Caloy)

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,^[18] and the JTWC assigned it the numerical identifier 03W.^[19] On March 25, the system intensified into a tropical storm and was named Jelawat by the JMA.^[20] Due to strong southwesterly wind shear, the cyclone remained poorly organized, with disorganized convection near an exposed low-level circulation.^[21] 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.^[22] 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.^[23] 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).^[24] 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.^[25]

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.

The storm brought minor impacts to Palau, the Caroline Islands, and the Northern Mariana Islands.

Tropical Depression 04W

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,^[26] shortly before the JTWC issued a TCFA.^[27] By May 12, deep convection was observed near its center as the JTWC began issuing advisories on the system giving the designation 04W.^[28] 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.^[29] Tracking in a course of a west-northwesterly direction, the system began to weaken as it started entering in an area of unfavorable conditions.^[30] 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.^[31] The JMA, however, tracked the system until early on May 15, when it finally dissipated.^[32]

Tropical Storm Ewiniar

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.^[33][34] Later that day the JTWC followed suit and designated the system as 05W.^[35] 05W meandered in a westward direction until it curved northward and after three days, the JTWC upgraded the system to a tropical storm.^[36] The JMA did the same three hours later early on June 6, naming it Ewiniar.^[37] 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.^[38] 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.^[39] However, Ewiniar's remnant moved out to sea and continued to persist, before dissipating on June 13.

8 people were killed in China, while total economic losses were estimated at CN￥3.67 billion (US$573 million).^[40]

Severe Tropical Storm Maliksi (Domeng)

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.^[41] On the next day, the system received the name Domeng from PAGASA, while the JTWC issued a TCFA for the system.^[42][43] After the system had consolidated further, the JMA finally upgraded the system to a tropical storm, naming it Maliksi.^[41] The JTWC, however, didn't track the system until 03:00 UTC of June 8 when it also gave the designation 06W.^[44] 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.^[41][45] Operationally, the JMA briefly classified Maliksi to a typhoon, but was downgraded to a severe tropical storm in post-analysis.^[46] 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.^[41][47] The JMA had tracked the remnants of Maliksi until 00:00 UTC of June 13.^[41]

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.^[48]

Tropical Storm 07W

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

A disturbance formed southwest of Taiwan on June 12, just within the meiyu front, and the JTWC indicated a subtropical depression subsequently.^[49] 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.^[50] Despite located in a moderately to a 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.^[51] 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.^[52] 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.^[49]

Tropical Storm Gaemi (Ester)

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	June 13 – June 16
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 by midnight, and after intensifying into a tropical storm 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.^[53]

Typhoon Prapiroon (Florita)

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 advories, 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, Typhoon Prapiroon had 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. ^[54][55]

As of July 2018, only 1 person was killed by the storm, who was from South Korea.^[56]

Typhoon Maria (Gardo)

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 depression formed on July 3. On the next day, the system intensified into Tropical Storm Maria. Early on July 5, Maria intensified into a severe tropical storm, while the JTWC classified the system as a Category 1 typhoon. Explosive intensification ensued, and later that day, Maria became a super typhoon and the first Category 5-equivalent storm of this basin since Nock-ten in 2016. Shortly afterwards, Maria underwent an eyewall replacement cycle, and it weakened below super typhoon status the following day. By July 8, however, Maria had completed the eyewall replacement cycle and regained Category 5-equivalent intensity.

Tropical Storm Son-Tinh (Henry)

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.^[57] The JTWC designated it as 11W while the PAGASA named it Henry.^[57] 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.^[58] Although from thereafter, Son-Tinh slightly weakened as it neared Hainan island while experiencing moderate shear.^[59] 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.^[60] 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.^[61] However, the JTWC continued to track the system's remnant low for another two days, before it finally dissipated.^[62]

Severe Tropical Storm Ampil (Inday)

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.^[63] 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.^[64] As Ampil moved in a northward direction, the system's structure had broadened along with sustained deep convection.^[65] Despite an unfavorable ocean heat content, Ampil still remained over relatively warm sea-surfaces temperatures with the inclusion of an extensive deep convection,^[66] 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).^[67] 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.^[68] 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.^[69] Ampil weakened further to a tropical depression on July 23, and both agencies issued their final advisory on the system.^[70] The JMA continued tracking the system until it weakened into an area of low pressure, at 18:00 UTC on July 24.^[71]

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 ¥1.19 billion (US$175.2 million).^[72]

Tropical Depression 13W (Josie)

Tropical depression (JMA)
Tropical depression (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 2018 Pacific typhoon season. Tropical Depression Josie missed kilometers off of landfall in Saud, Ilocos Norte. Tropical Depression Josie moved north, and exited the PAR by the next day. While approaching China, Josie approached the mainland of China about to become a named tropical storm, but missed Tropical Storm strength and was destroyed by high wind shear near China. The remnants of Josie 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 (Gardo), Tropical Storm Son-Tinh (Henry) and Severe tropical storm Ampil (Inday). July had 5 days of class supensions in Metro Manila, 2nd in history since Typhoon Ketsana (Ondoy) struck Metro Manila and caused ocean-high flooding last 2009 Pacific typhoon season. ^[73]

Severe Tropical Storm Wukong

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.^[74] 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.^[75] Within the next 24 hours, 14W began to organize with deep convection obscuring its LLCC,^[76] 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.^[77] 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.^[78] Wukong's extratropical remnants was tracked until late on July 27 when it was last noticed off the eastern coast of Russia Far East.^[79]

Typhoon Jongdari

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

Typhoon Jongdari was a strong, long-lived and erratic tropical cyclone that impacted Japan and East China in late July and early August 2018. Formed as the twelfth named storm of the 2018 typhoon season near Okinotorishima on July 24, Jongdari gradually intensified and developed into the fourth typhoon of the year on July 26. Influenced by an upper-level low and a subtropical ridge, Jongdari executed a rare counter-clockwise southeast of Japan on the next day. At that time, it also reached peak intensity. The typhoon made landfall in Kii Peninsula, over Mie Prefecture of Japan locally early on July 29.

Tropical Depression 16W

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

A tropical disturbance developed about 807 km (503 mi) north-northeast of Iwo To by July 29.^[80] 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.^[81] By July 31, the JMA followed suit on classifying the system as a tropical depression.^[82] 16W's center late became exposed with deep convection displaced due to continued shear.^[83] Originally, the system was forecast to reach tropical storm intensity with only 35 knot winds,^[84] but the system's center had become asymmetric with a fully sheared center.^[85] 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.^[86][87]

Typhoon Shanshan

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.^[88] 17W intensified into a tropical storm on August 3, with the JMA naming it as Shanshan.^[89] The storm was located over in favorable environments as the system was gradually consolidating,^[90] 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.

Tropical Storm Yagi (Karding)

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.^[91] 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).^[92] 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.^[93] 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.^[94] 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.^[95] Yagi made landfall shortly thereafter over Wenling, in Taizhou of Zhejiang, China, at around 23:35 CST (15:35 UTC) on August 12.^[96] By 21:00 UTC of that day, the JTWC issued their final advisory on Yagi,^[97] but continued to track it until it weakened further into a tropical depression early on August 13.^[98] 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, two people died along with ₱996 million (2018 PHP, US$18.7 million) worth of damages, as of August 26.^[99] In East China, Yagi killed a total of 2 people and total damages were counted to be CN￥380 million (US$55.5 million).^[100]

Tropical Storm Bebinca

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.^[101] 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.^[102] Despite consistent convection along with warm sea-surface temperatures, Bebinca remain weak for the next few days due to strong shear.^[103] Although by August 16, Bebinca began to undergo a phase of rapid intensification as its center was obscured by a central dense overcast,^[104] 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 3 people and total economic losses in South China were counted to be CN￥1.6 billion (US$231 million).^[105]Total damages in Vietnam were counted to be 800 billion ₫ (US$34.4 million).^[106]

Severe Tropical Storm Leepi

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 a extratropical system with no more energy left. Still, its remnants still headed out to mainland Russia. ^[107] Leepi dissipated on August 16, after the system was last tracked east of South Korea as a remnant low.

Tropical Storm Hector

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 Dateline and entered the West Pacific basin.^[108] 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.^[109] Due to an upper tropospheric trough cell located to the west of Hector, the storm failed to intensify and began to weaken.^[110] The JTWC downgraded Hector to a tropical depression after the system rapidly entered an area of high vertical wind shear.^[111] By the early hours of August 15, both agencies issued their final warning on Hector, mentioning that Hector's LLCC had become elongated and that the storm already transitioned into a subtropical cyclone.^[112] The JMA, however, continued to monitor the system until 00:00 UTC on August 17.

Tropical Storm Rumbia

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	August 14 – August 19
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.^[113]

Rumbia killed a total of 22 people in East China and total economic losses were counted to be CN￥9.2 billion (US$1.34 billion).^[114][115] Shouguang where 174.7 mm (6.88 in) of rain fell, 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.^[115]

Typhoon Soulik

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. 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).^[116]

Total economic losses in Northeast China were counted to be CN￥550 million (US$79.9 million).^[117]

Typhoon Cimaron

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

On August 16, a tropical depression formed near the Marshall Islands. It was named Tropical Storm Cimaron a day later. Severe Tropical Storm Cimaron rapidly intensified over the course from August 18-22. Typhoon Cimaron threatened Southern Japan, right after Typhon Soulik ravaged the area. Typhoon Cimaron peaked to a Category 3 major typhoon just right before its intense landfall in Japan. On August 23, Cimaron made landfall over the southern part of Tokushima Prefecture, Japan at around 21:00 JST (12:00 UTC). Typhoon Cimaron became Tropical Depression Cimaron before becoming extratropical and headed to the part of mainland Russia as nothing but just a weak low pressure remnant area that as once the devastating storm, Typhoon Cimaron. Cimaron was a significant Category 3 storm, and the 12th typhoon to strike Japan in 2018 and was surpassed by Typhoon Jebi a month later.^[118] Then, it made landfall over Himeji, Hyōgo Prefecture shortly before 24:00 JST (15:00 UTC).^[119]

Tropical Depression 24W (Luis)

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

A tropical depression formed at the South China Sea near Taiwan. 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 next day.^[120][121]

24W caused damages of 12.1 million and killed 6 people, including floods in Taiwan.

Typhoon Jebi (Maymay)

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

Typhoon Jebi was a strong Category 5 typhoon that killed 17 people. Jebi affected the Mariana Islands, Taiwan, Japan, and the Russian Far East. Jebi first started off as a low-pressure system near the Marshall Islands on early August 25, but was 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 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. Typhoon 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, before the extratropical low eventually dissipated northeast of Ayan early on September 7.

Typhoon Jebi was the strongest storm to hit Japan since Typhoon Yancy of 1993.

Typhoon Mangkhut (Ompong)

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

On September 7, a tropical depression formed near the Marshall Islands, and the Japan Meteorological Agency (JMA) initiated advisories on the system. The JTWC followed suit at 03:00 UTC, and the system was classified 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, Typhoon 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).^[122] 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,^[123][124] 6 in mainland China,^[125] and 1 in Taiwan.^[126] As of October 5, the NDRRMC estimated that Mangkhut caused ₱33.9 billion (US$627 million) in damages in the Philippines, with assessments continuing.^[127]

Tropical Storm Barijat (Neneng)

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. 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 increases the risk of major landslides and major flooding in the saturated soil influenced by this storm and later by Mangkhut (Ompong).

Typhoon Trami (Paeng)

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

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 a 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 began 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,^[128] 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.

Tropical Depression 29W

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, while moving northwestward, a low-pressure area had developed into a tropical depression, associated from the remnant energy from Hurricane Olivia.^[129] The JTWC gave the designation 29W next day.^[130] Remaining weak with an exposed low-level circulation center, 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.^[131][132]

Typhoon Kong-rey (Queenie)

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

In late September 2018, a tropical disturbance formed in the waters near Pohnpei Island in the Federated States of Micronesia. The Joint Typhoon Warning Center also gave the rating to 94W "Low".^[133] 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 28 September, the JTWC designated the system as 30W,^[134] while the JMA issued a gale warning for the system.^[135] As Tropical Depression 30W continued strengthening, the system became a tropical storm and was named Kong-rey by the JMA. On 29 September, 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.^[136] 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,^[137] 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.^[138] Although Kong-Rey did not make a direct impact on Kyushu and Shikoku, its outer rainbands affected the two islands. At an area in Shikoku, rain accumlated to 300 mm. In Nagasaki, more than 12,000 families lost power;^[139] in Fukuoka Prefecture, a person died because of the rain.^[140]

Other systems

On June 4, the JMA began tracking on a weak tropical depression that had formed northeast of Yap.^[141] However, the system was absorbed by a nearby tropical depression, which would eventually become Severe Tropical Storm Maliksi on the next day.^[42] 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.^[142][143] 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.^[144]

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.^{[145][146][147]} The remnants associated with Hurricane Olivia entered this basin on September 19,^[148][149] and it developed into a tropical depression on September 21 when drifting westward slowly.^[150] Two days later, it degenerated into the remnants again, as JMA reported a dissipation.^[151][152] The system's remnant energy developed into Tropical Depression 29W.

International names

A tropical cyclone is named when it is judged to have 10-minute sustained windspeeds of at least 65 km/h (40 mph).^[155] 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.^[156] The next 35 names on the naming list are listed here along with their international numeric designation, if they are used. 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.

The international numeric designation 1817 was applied to Tropical Storm Hector after it crossed the International Date Line; its name was assigned by the National Hurricane Center.

Philippines

PAGASA uses its own naming scheme to name tropical cyclones that either develop within or move into their self-defined area of responsibility.^[157] The list of names for this season was last used during 2014 and are scheduled to be used again during 2022.^[157] All of the names are the same except for Gardo, Josie, Maymay, Rosita and Samuel, which replaced the names Glenda, Jose, Mario, Ruby and Seniang after they were retired.^[157] So far, the names Gardo, Josie and Maymay were used for the first time.