2018 Pacific typhoon season

2018 Pacific typhoon season
Season summary map
Seasonal boundaries
First system formed	December 29, 2017 (2017-12-29)
Last system dissipated	December 29, 2018 (2018-12-29)
Strongest storm
Name	Kong-rey & Yutu
• Maximum winds	215 km/h (130 mph) (10-minute sustained)
• Lowest pressure	900 hPa (mbar)
Seasonal statistics
Total depressions	44, 1 unofficial
Total storms	29, 1 unofficial
Typhoons	13
Super typhoons	7 (unofficial)
Total fatalities	793 total
Total damage	$30.54 billion (2018 USD) (Third-costliest Pacific typhoon season on record)
Related articles
Timeline of the 2018 Pacific typhoon season 2018 Atlantic hurricane season 2018 Pacific hurricane season 2018 North Indian Ocean cyclone season
Pacific typhoon seasons 2016, 2017, 2018, 2019, 2020

The 2018 Pacific typhoon season was at the time, the costliest Pacific typhoon season on record, until the record was beaten by the

On March 15, the Vietnamese National Center for Hydro Meteorological forecasts (VNCHMF) predicted that roughly twelve to thirteen tropical cyclones would affect Vietnam during 2018, which is above average.^[5] On March 23, the Hong Kong Observatory predicted that five to eight tropical cyclones would come within 500 kilometres of Hong Kong, which is normal to above normal, with the first tropical cyclone affecting Hong Kong in June or earlier.^[6] On May 11, the Tropical Storm Risk (TSR) issued their first forecast for the season, predicting that the 2018 season would be a slightly above average season with 27 named storms, 17 typhoons, and nine intense typhoons.^[1] The TSR released their second forecast on July 6, still predicting that the season will be above average, with the only changes to their forecast increasing the number of intense typhoons from 9 to 10.^[2] The PAGASA issued their second and final outlook on July 13 for the period of July – December, predicting six to eight tropical cyclones were expected to develop or enter their area of responsibility between July and September, while four to six were forecast during October to December. On August 7, TSR released their final forecast, with its only changes decreasing the numbers of intense typhoons from 10 to 9, as well as decreasing its ACE forecast from 331 units to 319 units.^[3]

This section needs expansion. You can help by adding to it. (November 2020)

2018 opened with

On August 16, Typhoon Soulik developed and headed north, until a Fujiwhara interaction with Typhoon Cimaron (which formed after Soulik) made it head west towards the East China Sea. It later made landfall on South Korea, making it the first typhoon to make landfall on South Korea since Typhoon Chaba in 2016. Cimaron made landfall near Kyoto, Japan on August 23. As Cimaron was nearing landfall, Tropical Depression Luis formed, which made landfall on China and Taiwan. Later that month, Typhoon Jebi developed over the West Pacific and intensified into the third super typhoon of the season.

In September,

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

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

Typhoon Jelawat (Caloy)

Violent 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,^[21] and the JTWC assigned it the numerical identifier 03W.^[22] On March 25, the system intensified into a tropical storm and was named Jelawat by the JMA, and at the same time it entered PAGASA's Philippine Area of Responsibility (PAR) and was assigned the local name Caloy.^[23] Due to strong southwesterly wind shear, the cyclone remained poorly organized, with disorganized convection near an exposed low-level circulation.^[24] Conditions gradually became more favorable for further development, resulting in Jelawat steadily strengthening and gaining organization before intensifying into a severe tropical storm at 18:00 UTC on March 28.^[25] 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.^[26] 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 (121 mph) and a central pressure of 915 hPa (27.0 inHg).^[27] 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.^[28]

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.

Jelawat yielded 20 inches of rainfall on parts of the island of Pohnpei, resulting in flooding and landslides that caused critical damage to infrastructure and one death.^[29][30] A woman in Guam drowned from the remnants of Jelawat on April 3,^[31] after strong surf and rip currents stranded her in water.^[32]

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 shortly before the JTWC issued a TCFA.^[33][34] By May 12, deep convection was observed near its center as the JTWC began issuing advisories on the system, giving it the designation 04W.^[35] Roughly twelve hours later, it was reported that 04W had intensified into a tropical storm by the JTWC after satellite imagery had depicted a well-defined center.^[36] Tracking on a west-northwesterly course, the system began to weaken as it entered an area of unfavorable conditions.^[37] 04W rapidly weakened as the JTWC issued their final advisory on the system early on May 14 as wind shear affected the system and exposed the elongated low-level circulation.^[38] The JMA, however, tracked the system until early on May 15, when it dissipated.^[39]

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.^[40][41] Later that day, the JTWC followed suit and assigned the designation 05W to the system.^[42] 05W meandered in a westward direction until it curved northward, and after three days, the JTWC upgraded the system to a tropical storm.^[43] The JMA did the same three hours later early on June 6, naming it Ewiniar.^[44] 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.^[45] 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.^[46] However, Ewiniar's remnants 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).^[47]

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.^[48] On the next day, the system received the local name Domeng from the PAGASA as the JTWC issued a TCFA on the system.^[49][50] After the system had consolidated further, the JMA upgraded the system to a tropical storm, naming it Maliksi (1805).^[48] The JTWC, however, did not track the system until 03:00 UTC on June 8 when it gave Maliksi the designation of 06W.^[51] Moving northward, Maliksi continued to intensify until it reached its peak strength early on June 10 with winds of 110 km/h (68 mph), just shy of typhoon intensity, and a minimum pressure of 970 hPa.^[48][52] Operationally, the JMA briefly classified Maliksi as a typhoon, but it was downgraded to a severe tropical storm in post-analysis.^[53] Maliksi began to weaken as it began extratropical transition, and on June 11 as it encountered more unfavorable conditions, both agencies stopped issuing warnings on Maliksi as the system's center became exposed and as it transitioned into an extratropical cyclone.^[48][54] The JMA tracked the remnants of Maliksi until 00:00 UTC on June 13.^[48]

Despite not making landfall on 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.^[55]

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 subsequently indicated the formation of a subtropical depression.^[56] At 21:00 UTC on June 13, the JTWC issued its first advisory on the system and designated it as 07W, classifying it as a tropical depression.^[57] Despite being affected by moderate to severe wind shear, the system was located over relatively warm sea-surface temperatures as it produced patches of convection, and this prompted the JTWC to upgrade 07W to a tropical storm.^[58] The JTWC later issued their fourth but final advisory on 07W at 15:00 UTC on June 14 when the system was rapidly undergoing a phase of extratropical transition and as the system was rapidly losing its structure.^[59] 07W fully became an extratropical cyclone just to the south of mainland Japan at 06:00 UTC on June 15, although its remnant was still tracked until June 25, when the system was last located near the coast of British Columbia.^[56]

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

On June 19, the NDRRMC reported that 3 people had died from monsoonal rains enhanced by Gaemi.[60] Agricultural damage in Okinawa Prefecture were estimated at ¥84.58 million (US$764,000).^[61]

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 Tropical Depression 09W on June 28. On the next day, the PAGASA began issuing advisories, assigning it the local name Florita. 6 hours later, Florita became a tropical storm, with the JMA assigning it the name Prapiroon (1807). By July 2, Prapiroon intensified into a Category 1 typhoon as it neared Japan and Korea. By July 3, Prapiroon had attained peak intensity. On the same day, Prapiroon made landfall on Japan. After making 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.^[62][63]

Five people were injured by the winds from the typhoon.^[64] A woman was blown away by the strong winds of the typhoon and died at a hospital she was sent to later.^[65] The typhoon also caused damages on Old Gorin Church, which as designated as heritage site four days prior, and caused damages to the stained glass in Kuroshima Catholic Church.^[66] One person from South Korea was killed by the storm.^[67] Agricultural damage in Okinawa Prefecture were about ¥49.39 million (US$446,000).^[68]

Violent 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.^[69] After slow development and as it drifted westward 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, designating it 10W late on the same day.^[70][71] 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.^[72][73] 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 a result, the system continued to organize and the JMA upgraded it to a tropical storm and assigned it the international name Maria at around 12:00 UTC,^[74] with the JTWC also upgrading it to a tropical storm.^[75] Six hours later, when the storm struck Guam directly, surface observations at Andersen Air Force Base recorded one-minute maximum sustained winds of 50 knots (93 km/h; 58 mph) and a minimum pressure of 984 hPa (29.06 inHg), indicating a rapidly consolidating system.^[76]

On July 5, Maria drifted northwestward slowly under the influences of a weak north–south oriented steering ridge and a strong east–west oriented

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

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

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)

Main article:

Tropical Storm Ampil (2018)

On July 17, a weak tropical depression developed over the Philippine Sea. The JTWC upgraded the system to a tropical depression on the same day, designating it as 12W as it was located over a favorable environment.^[90] On the next day, the PAGASA followed suit and it was given the local name Inday. By 12:00 UTC on July 18, the JMA upgraded the system to a tropical storm, assigning it the name Ampil.^[91] As Ampil moved in a northward direction, the system's structure had broadened, being accompanied by sustained deep convection.^[92] Despite unfavorable ocean heat content, Ampil still remained over relatively warm sea surface temperatures with the inclusion of extensive deep convection,^[93] therefore Ampil was classified as a severe tropical storm. With an improved convective system, the JTWC assessed that Ampil had reached maximum 1-minute sustained winds of 95 km/h (59 mph).^[94] Ampil reached its peak intensity with a minimum pressure of 985 hPa and maintained that intensity for the next few days as the track of Ampil changed direction. On July 21, the system's center became exposed as the system slightly weakened.^[95] On the next day, the JMA downgraded Ampil back to a tropical storm as it made landfall on China with a lack of convection.^[96] Ampil weakened further to a tropical depression on July 23, and both agencies issued their final advisories on the system.^[97] The JMA continued tracking the system until it weakened into an area of low pressure at 18:00 UTC on July 24.^[98]

Heavy rain in

Tropical Depression 13W (Josie)

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 in the South China Sea on July 20 according to the JMA. On July 21, the system entered the Philippine Area of Responsibility and was assigned the local name Josie, making it the 10th named storm to enter the PAR. The JTWC upgraded the system to a tropical storm on the same day. The system missed landfall within kilometers on Saud, Ilocos Norte. It moved north and exited the PAR on the next day. The remnants of 13W dissipated off the coast of China.^{[citation needed]}

After the formation of the previous two systems, the

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 as it developed about 603 km (375 mi) east-southeast of the Japanese island of

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)

A tropical disturbance formed southeast of Guam on July 19 and tracked westward steadily.^[106] 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.^[107] 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.^[108] After slow consolidation for several days, the system was upgraded to a tropical storm near Okinotorishima at around 18:00 on July 24 by the JMA and the JTWC, being assigned the international name Jongdari.^[109][110] Microwave imagery revealed a low-level eyewall forming on the next day, indicating a consolidating system. After the JMA upgraded Jongdari to a severe tropical storm at noon,^[111] the system accelerated northeastward under the influence of a near-equatorial ridge to the south.^[112]

On July 26, as Jongdari started to interact with an upper-level

Jongdari rapidly weakened after landfall, dissipating on the next day. No fatalities were recorded for this storm.

Tropical Depression 16W

Tropical depression (JMA)
Subtropical storm (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 (501 mi) north-northeast of

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 developed east-northeast of Guam on August 2. At 21:00 UTC on the same day, the JTWC began tracking the system, giving it the identifier 17W.^[130] 17W intensified into a tropical storm on August 3, with the JMA assigning it the name Shanshan.^[131] The storm was located over a favorable environment as the system was gradually consolidating,^[132] and it intensified into a severe tropical storm on August 3. 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 peaked in intensity with 10-minute winds of 130 km/h (81 mph) and a minimum pressure of 970 hPa, remaining that intensity for several days. The JTWC stated that Shanshan had slightly weakened after a strengthening trend by August 6 after its eye became ragged and slightly displaced. 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 (103 mph) while nearing 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).^[133]

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

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

Despite not making landfall on the

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 the system, giving it the designation 20W on August 12.^[143] On the next day, the JMA upgraded the system to a tropical storm, naming it Bebinca. The JTWC followed suit nine hours later as deep convection flared near its compact center.^[144] Despite consistent convection along with warm sea-surface temperatures, Bebinca remained weak for the next few days due to strong shear.^[145] By August 16, however, Bebinca began to undergo a phase of rapid intensification as its center was obscured by a central dense overcast,^[146] which resulted in the JMA briefly upgrading Bebinca to a severe tropical storm, though in post-analysis it was downgraded to a tropical storm. The JTWC analysed a few hours later that the system had reached peak intensity with 1-minute winds of 110 km/h (68 mph). After Bebinca made landfall, the system rapidly weakened and both agencies issued their final warnings on August 17, with the system fully dissipating on the 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).

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 10, a tropical depression formed near the Mariana Islands, assigning the depression as 19W and on the next day at 12:00 UTC, the JMA upgraded it to a tropical storm, assigning it the name Leepi. By August 13, Leepi began to threaten Japan, and on August 14, Leepi intensified into a severe tropical storm, with the JTWC upgrading it to a Category 1 equivalent typhoon. Shortly before 03:00 JST (18:00 UTC) on August 15, Leepi made landfall over Hyūga, Miyazaki in Japan. Leepi was downgraded into a tropical depression and dissipated on August 15, though its remnants were still noted near Russia.^[148]

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 has crossed the International Date Line and entered the West Pacific basin from the East Pacific basin.^[149] 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.^[150] Due to an upper tropospheric trough cell located to the west of Hector, the storm failed to intensify and began to weaken.^[151] The JTWC downgraded Hector to a tropical depression after the system rapidly entered an area of high vertical wind shear.^[152] By the early hours of August 15, both agencies issued their final warnings on Hector, mentioning that Hector's low-level circulation had become elongated and that the storm already transitioned into a subtropical cyclone.^[153] 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

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).[47] 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 were last tracked northeast of Hokkaido before dissipating off the coast of the Russian Far East.^[155]

Very strong 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).^[156]

Total damage in South Korea were at ₩50.7 billion (US$45 million).^{[citation needed]} Economic loss in Northeast China were counted to be CN¥550 million (US$79.9 million).^[157] Flooding in North Korea triggered by Soulik killed 86 people.^[158]

Very strong 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, at 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 on 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.^[159] Then, it made landfall over Himeji, Hyōgo Prefecture shortly before 24:00 JST (15:00 UTC).^[160]

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

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

Tropical Depression 24W killed 7 people and caused NT$1.022 billion (US$34 million) of damage in Taiwan.^[142]

Violent 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

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.

Violent 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

Hong Kong Observatory initiated Hurricane Signal No. 10 around 09:40 HKT (00:40 UTC), the first time since Typhoon Hato of the previous year. As of September 23, at least 134 fatalities have been attributed to Mangkhut, including 127 in the Philippines,^[167][168] 6 in mainland China,^[169] and 1 in Taiwan.^[170] As of October 5, the NDRRMC estimated that Mangkhut caused ₱33.9 billion (US$627 million) in damages in the Philippines, with assessments continuing.^[171]

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.^[172] 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 on 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). No deaths were reported throughout its path, however, damages in China were at ¥50 million (US$7.3 million).^[47]

Violent 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^[173] 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).^[174]

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 from the remnant energy of Hurricane Olivia to the southeast of Japan. The JTWC gave the system the designation 29W on the next day.^[175] 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.^[176][177]

Violent 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

As of October 2018, 3 people have been killed by the storm, including 2 people from South Korea.^[183] Damage nationwide totaled at ₩54.9 billion (US$48.5 million).^[184] 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;^[185] in Fukuoka Prefecture, a person died because of the rain.^[186] Agricultural damage in Okinawa and Miyazaki Prefecture were about JP¥13.99 billion (US$123 million).^[187][188]

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

Violent 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

After making landfall on 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 the storm moved over ocean waters with significantly lower sea-surface heat content.

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

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

Tropical Storm Toraji

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

Typhoon Man-yi (Tomas)

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

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 35W (Usman)

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 Christmas Day, December 25. It entered the PAR later that evening and the PAGASA named the significant tropical depression "Usman". Usman made its first landfall on 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.^[199]

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

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

• 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.^{[205][206][207]}
• The remnants of Hurricane Olivia entered the basin on September 19,^[208][209] and redeveloped into a tropical depression on September 21, while slowly drifting westward.^[210] Two days later, it degenerated into a remnant low again, as the JMA reported the system's dissipation.^[211][212] 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,^[213] with the JTWC designation 36W.^[214] The system intensified into Tropical Storm Pabuk on January 1, 2019, becoming the first named storm of the 2019 Pacific typhoon season.^[215]

Within the Northwest Pacific Ocean, both the

During the season 29 tropical storms developed in the Western Pacific and 28 were 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

After the season, the Typhoon Committee announced that the names Rumbia, Mangkhut, and Yutu were removed from the naming lists due to the damages and deaths it caused in their respective onslaughts, and they will never be used again for another typhoon name.^[218][219] In 2020, they were replaced with Pulasan , Krathon , and Yinxing , respectively.

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. This is the same list used from the

After the season, the names Ompong, Rosita and Usman were retired, as they caused at least ₱1 billion in damages. They were replaced with Obet, Rosal and Umberto for the 2022 season.^[220]

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

• Weather of 2018
• Tropical cyclones in 2018
• Pacific typhoon season
• 2018 Atlantic hurricane season
• 2018 Pacific hurricane season
• 2018 North Indian Ocean cyclone season
• South-West Indian Ocean cyclone seasons: 2017–18, 2018–19
• Australian region cyclone seasons: 2017–18, 2018–19
• South Pacific cyclone seasons: 2017–18, 2018–19

External links

Wikimedia Commons has media related to 2018 Pacific typhoon season.

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