2021 Pacific typhoon season

During the year, several national meteorological services and scientific agencies forecast how many tropical cyclones, tropical storms, and typhoons will form during a season and/or how many tropical cyclones will affect a particular country. These agencies included the Tropical Storm Risk (TSR) Consortium of University College London, PAGASA and Taiwan's Central Weather Bureau. The first forecast was released by PAGASA on December 27, 2020, in their monthly seasonal climate outlook predicting the first half of 2021.^[6] The PAGASA predicts that only 0–3 tropical cyclones are expected to form or enter the Philippine Area of Responsibility between January and March, while 1–4 tropical cyclones are expected to form between April and June. PAGASA also predicted that the ongoing La Niña could persist until the end of the first quarter of 2021.^[6] Tropical Storm Risk (TSR) issued their first extended range forecast on May 11, predicting a slightly below-average season with 24 tropical storms, 15 typhoons and 9 intense typhoons.^[3]

On June 23, the PAGASA released their monthly climate outlook for the rest of 2021, predicting 5 to 9 tropical cyclones developing or entering their area of responsibility from July to September, and 5 to 8 tropical cyclones from October to December.^[7] TSR issued an update to their forecast on July 7, reiterating their expectations for slightly below-average activity.^[4] On August 9, TSR issued their final forecast for the season, slightly lowering their numbers to 25 named storms, 13 typhoons and 7 intense typhoons.^[5]

The season began in January with a weak and short-lived tropical depression that brought damages to the Philippines. In mid-February, another tropical depression formed, before being assigned the local name Auring by the PAGASA. The system then strengthened into a tropical storm, being given the name Dujuan by the JMA, making it the first named storm of the year. Another tropical depression formed in March, though it was short-lived, dissipating shortly after forming. On April 12, a tropical depression formed to the south of Woleai. It strengthened into a tropical storm, being given the name Surigae by the JMA. On April 15, it was further upgraded into a severe tropical storm, before being upgraded to a typhoon on the next day, and to a super typhoon on April 17,^{[nb 1]} making it the first of the season and the strongest recorded cyclone to form in the month of April in the Northern Hemisphere, however, it did not hit any landmasses. Then, in mid-May a new tropical depression was named Crising by the PAGASA and made landfall on Baganga, Davao Oriental as a weak tropical storm, bringing minimal damages due to its small size. Two tropical depressions formed on May 29 and 30 respectively, with the first being assigned the local name Dante by the PAGASA. Dante intensified into a tropical storm, being assigned the name Choi-wan, before moving over the Philippines and making landfall eight times, bringing widespread damages to the country. A tropical depression formed behind Choi-wan on May 30; it didn't develop further.

The second typhoon of the season, Champi, briefly threatened the Ogasawara Islands before recurving through the main Japanese islands. Another depression formed at the end of June; it stayed from any landmasses while two tropical depressions formed in early July with both of them affecting land. One of them was named Emong by PAGASA. In mid-July, In-fa formed and became the third typhoon of the season. The storm contributed to rainfall and flooding in eastern China as it made landfall near Shanghai. Meanwhile, Cempaka formed and intensified into a typhoon affecting southern China and northern Vietnam. Another tropical storm, Nepartak, formed as Cempaka made landfall. Nepartak affected Japan in late July, disrupting the 2020 Summer Olympics, before becoming extratropical in the sea of Japan.

By the end of July, activity abruptly increased as eight tropical depressions formed within a week. Half of them were short-lived and dissipated without becoming tropical storms. Another depression and the remaining three were named Lupit, Nida, and Mirinae. Lupit and Mirinae both threatened Japan while Nida stayed out to sea. A system from the Central Pacific traveled a long distance and became Tropical Storm Omais over the Philippine Sea.

After Omais, the tropics stayed quiet for the rest of August until early September, when Conson rapidly intensified to become a typhoon in less than 24 hours before hitting the Philippines and Chanthu becoming the second Category 5-equivalent super typhoon of the season. After Chanthu dissipated, there was a pause in activity until Typhoon Mindulle and Tropical storm Dianmu formed. Dianmu soon made landfall on Vietnam and dissipated, but Mindulle went on to become the third Category 5-equivalent super typhoon of the season.

Soon thereafter in the month of October, four storm named Lionrock, Kompasu, Namtheun, and Malou formed. Lionrock made landfall over Vietnam, causing agricultural damage. Kompasu made landfall in the Philippines and later China, causing severe flooding, infrastructure, and agricultural damage. Tropical Depression Nando also formed in early October but was absorbed by Kompasu. Namtheun initially peaked as a minimal tropical storm while being highly sheared, but unexpectedly conditions became briefly more favorable and peaked as a minimal typhoon. The system transitioned into an extratropical low before explosively intensifying into a bomb cyclone and impacting the Pacific Northwest. In late October, Malou peaked as a Category 2-equivalent typhoon, and only impacted the Bonin Islands. In the South China Sea, tropical depression 26W formed before making landfall in southern Vietnam and causing torrential flooding.

After an unusual four-week break of inactivity, Nyatoh formed on November 29 and later strengthened to a typhoon on December 1. It later turned towards the northeast, became a super typhoon then transitioned into an extratropical cyclone. After Nyatoh, in the early week of December, a disturbance formed east of the Philippines and moved eastward, while dumping rains on parts of Visayas and Mindanao. After that, it merged with another invest (designated 96W by the Joint Typhoon Warning Center) and headed towards the west-northwest. It later strengthened to a tropical depression by December 12, with the JTWC later designating it as 28W. 9 hours later, 28W intensified to Tropical Storm Rai, meaning Yapese stone money. Rai continued intensifying as it headed west and passed south of Ngulu State, and intensified into a severe tropical storm by 14 December. It got battered by wind shear as it neared the small island country of Palau, and by evening, entered the Philippine Area of Responsibility and was given the local name of Odette. Four hours later, Rai (Odette) began showing an eye feature first seen in microwave imaging, with Rai later becoming a Category 1-equivalent typhoon. Steady intensification ensued, and Rai later reached Category 2-equivalent status.

By the evening of December 15, Typhoon Rai underwent unexpected rapid intensification, doubling its wind speeds from a 120 km/h (75 mph) to 260 km/h (160 mph)—Category 5-equivalent winds—by December 16, effectively making it a super typhoon. Rai then began an eyewall replacement cycle shortly after reaching its first peak intensity, weakening below Category 5-equivalent status. It made landfall in General Luna, Surigao del Norte as a 155 mph Category 4-equivalent storm. It made 8 more landfalls, weakening to a Category 2-equivalent typhoon by the time it entered the Sulu Sea. Rai then began to re-intensify, making its 10th landfall in Roxas, Palawan. After this, Rai continued re-intensification, becoming a Category 5-equivalent typhoon once again in the South China Sea, the first in the month of December and the third to do so after Typhoon Pamela (1954) and Typhoon Rammasun. After this, Rai began weakening, eventually dissipating west of the Batanes in December 21. A tropical depression, designated 29W by JTWC, formed in December 14 and affected Malaysia with widespread flooding, and struck around the same time as Rai was pounding through the Visayas. 29W dissipated by December 17, as Rai entered the Sulu Sea.

Rai contributed to the change of PAGASA's Tropical Cyclone Wind Signals and TC classification, which itself was deemed as a super typhoon by the agency when the change was made on March 23, 2022.^[9]

At 06:00 UTC on February 16, the JMA reported that a tropical depression had formed.^[10] Eight hours later, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) for the system.^[11] By February 17, the system moved into the Philippine Area of Responsibility (PAR), and was assigned the local name Auring from the PAGASA.^[12] At 06:00 UTC on the same day, the JTWC upgraded the system to a tropical depression, giving it the designation 01W. The system was later named Dujuan as the first named storm of 2021. The PAGASA later upgraded Dujuan to a severe tropical storm; however, this only lasted for six hours.^[13][14] On February 20, the storm significantly weakened into a tropical depression due to high vertical wind shear. Both JMA and JTWC issued their final advisories moments after.^[15] The storm made landfall over Batag Island in Laoang, Northern Samar at 09:00 PHT (01:00 UTC) on February 22,^[16] dissipating thereafter.

Dujuan briefly moved over Palau on February 16 as a tropical depression, bringing heavy rainfall to parts of the country.^[17][18] Classes and government work were suspended on February 22 in parts of Eastern Visayas and Central Visayas, including Surigao del Sur.^[19][20] A total of 242,194 individuals were affected in Northern Mindanao, Caraga, and in the Davao Region. At least 77,811 of the affected individuals were taken to 344 various evacuation shelters in each region. One person was reported dead with four others reported missing, with total damages to agriculture and infrastructure amounting to ₱159.8 million (US$3.29 million).^[21]

A low-pressure area south of Woleai developed into a tropical depression on April 12.^[22][23] A few hours later, the JTWC issued a TCFA for the developing storm, with the PAGASA beginning to issue advisories for the tropical depression as it remained outside of the PAR.^[24][25] On April 13, the JTWC upgraded the system to a tropical depression and assigned it the designation 02W.^[26] At 18:00 UTC, the JMA upgraded the cyclone to a tropical storm and named it Surigae.^[27] On April 15 at 00:00 UTC, the JMA upgraded Surigae to a severe tropical storm as an eye began forming.^[28] Later that day, the JTWC upgraded the storm to a typhoon, making it the first of the season. Surigae then entered the PAGASA's Philippine Area of Responsibility, getting the local name Bising. Surigae continued to rapidly intensify until it reached Category 5-equivalent super typhoon status, becoming the most intense typhoon ever recorded in the month of April.^[29][30][31] Surigae soon reached its peak intensity, with a minimum central pressure of 895 millibars (26.43 inHg), 10-minute maximum sustained winds of 220 km/h (140 mph), and 1-minute sustained winds of 315 km/h (195 mph).^[32][33] A few days later, on April 22, Surigae began to weaken again, with the storm's structure deteriorating and its large eye dissipating.^[34] Soon afterward, all of the remaining convection was sheared to the east as the storm moved over cooler waters.^[35] Late on April 24, JTWC and JMA declared and issued their final advisory that Surigae had become extratropical.^[36]

Winds of up to 30 mph (50 km/h) were recorded in Yap on that day as Surigae passed from the southwest.^[37] Damage in Palau was estimated at US$4.8 million.^[38] Very strong winds and heavy rains affected the eastern part of the Philippines, with storm surge inundating parts of coastline nearest to the typhoon. Surigae killed a total of 8 people and left another 10 missing.^[39][40] The storm also caused at least ₱272.55 million (US$5.65 million) in damages.^[39]

On May 11, the JTWC noted a persistent area of convection in the Philippine Sea, approximately 184 nmi (341 km) west of Palau.^[41] The JTWC issued a TCFA for the convection on May 12, as it further developed in an environment with low vertical wind shear and warm sea surface temperatures.^[42] Just three hours later, the agency recognized that the area of convection had quickly consolidated into a tropical depression and assigned it with the identifier of 03W.^[43] Around the same time, the JMA had also recognized the storm as a tropical depression while it was to the east of Mindanao.^[44] Since the storm developed within the Philippine Area of Responsibility, the PAGASA immediately named the storm Crising once the agency recognized it as a tropical depression as well, and later raised Signal No. 2 warnings for areas in Mindanao.^[45][46] In the early hours of May 13, the JTWC upgraded the system into a tropical storm, with the PAGASA following suit hours later.^[47][48] Later that day, Crising's low-level circulation center became exposed due to wind shear, and it lost organization. At 8:20 p.m. Philippine Standard Time (12:20 UTC), Crising made landfall in Baganga, Davao Oriental as a weakening tropical storm. It quickly degraded as soon as it made landfall, with both the JTWC and the PAGASA downgrading it to a tropical depression at 15:00 UTC.^[49][50] At 03:00 UTC on that day, the PAGASA reported that the system degenerated to an area of low-pressure in the vicinity of Piagapo in Lanao del Sur, thus lifting all warning signals on Mindanao and issuing their final advisory.^[51] On May 14, the system dissipated over the Sulu Sea, and both the JMA and the JTWC issued their final advisories on the storm.

In preparations for the storm, the local government of Davao Occidental raised a blue alert on May 13, with the authorities in the area preparing rescue equipment in case of emergency.^[52] The PAGASA also warned small vessels near the area to stay away from the rough seas caused by the storm.^[53] Schools were ordered to be suspended for that day in Davao Occidental, including the submission of modules.^[53] When Crising made landfall, it caused widespread rains and flooding across Mindanao and Southern Visayas. Gusty winds were also felt in parts of Mindanao where the storm passed.^[54] In Baganga, some trees were knocked down by strong winds, while strong winds with heavy rainfall were reported in Cateel and Boston, all in the province.^[52] Three men and a carabao were required to be rescued from the rising Kabacan River in the early hours of May 14; they were successfully released safely from the said river.^[55] An evacuation center in South Upi, Maguindanao were reported to be flooded and some crops near the center were submerged in floodwaters, all due to a rising river near the area.^[55] Agricultural damages were estimated at ₱23.2 million (US$486,000).^[56]

On May 27, the JMA and the JTWC noted the persistence of an area of atmospheric convection about 425 nautical miles (787 km; 489 mi) south-southeast of Guam.^[57] The area's nearby environment exhibited low wind shear and warm sea surface temperatures, which were ideal conditions for tropical cyclogenesis.^[58] The JMA assessed the area to have developed into a tropical depression on May 29 at 06:00 UTC.^[59] The PAGASA made a similar assessment in a Tropical Cyclone Advisory issued at 15:00 UTC.^[60] The JTWC later followed with their own assessment, identifying the center of the newly developed tropical depression and assigning the designation 04W.^[61] As the system tracked westward, it entered the Philippine Area of Responsibility at 01:00 PHT (17:00 UTC).^[62] The PAGASA then named the storm Dante in its first Tropical Cyclone Bulletin for the storm.^[63] Dante further organized in the Philippine Sea,^[64] and on May 30 at 15:00 UTC, the JTWC upgraded it to a tropical storm,^[65] with the PAGASA doing the same at 21:00 UTC.^[66] On the next day at 00:00 UTC, the JMA also upgraded Dante into a tropical storm, giving it the international name Choi-wan.^[67] Choi-wan's center was exposed due to a tropical upper tropospheric trough from the northeast, inducing shear on the system.^[68] On June 1 at 12:30 UTC, Choi-wan made landfall on Sulat, Eastern Samar as a minimal tropical storm,^[69] with the JTWC downgrading it to a tropical depression at 15:00 UTC.^[70] It made a second landfall on Cataingan at 17:00 UTC.^[71] Choi-wan made several more landfalls on the Philippines, making its third landfall on Balud, Masbate at 19:30 UTC. It made a fourth landfall on Romblon, Romblon on June 2 at 00:00 UTC, a fifth on San Agustin, Romblon at 00:50 UTC, a sixth on Pola, Oriental Mindoro at 06:00 UTC, a seventh on Tingloy, Batangas at 11:20 UTC, and an eighth and final landfall on the Calatagan Peninsula before moving into the South China Sea.^[72] On June 3 at 03:00 UTC, the JTWC upgraded Choi-wan back to a tropical storm.^[73] At 03:00 UTC, the PAGASA removed all Tropical Cyclone Warning Signals as Choi-wan moved away from the country.^[74] Choi-wan then exited the PAR on June 3 at 18:00 UTC^[75] before weakening into a tropical depression on the next day at 06:00 UTC and re-entering the PAR at 08:00 UTC.^[76] Then, it passed southeast of the island of Taiwan^[77] before moving out near the Okinawa Prefecture and heading towards Japan.^{[citation needed]} On June 5 at 06:00 UTC, the Japan Meteorological Agency issued their final advisory on the system.^[78] 3 hours later at 09:00 UTC, the JTWC upgraded Choi-wan back into a tropical storm,^[79] however at 15:00 UTC, the Joint Typhoon Warning Center downgraded the system to a tropical depression, also issuing their final advisory on the system.^[80]

Heavy rains caused floods in parts of Mindanao;^[81] 11 fatalities were reported, 3 people were injured, and 2 people are missing.^[82] As of June 4, 55,226 people were affected and 16,680 people are inside evacuation centers. A total of ₱307.2 million (US$6.39 million) of damages were incurred throughout the country, of which ₱152.1 million (US$3.17 million) was agricultural damages and ₱155.1 million (US$3.23 million) was related to infrastructure.^[83] On June 1, classes and government work for parts of Davao de Oro, Eastern Samar, Leyte, and Surigao del Sur were suspended for the day.^[84]

On June 10, the JTWC started to monitor an area of low-pressure in the South China Sea, approximately 518 km (322 mi) to the south of Hong Kong, with the agency classifying the system as a monsoon depression.^[85] Tracking west-northwestward, the storm was located in a favorable environment for further development, with warm sea surface temperatures and low wind shear.^[86] At 00:00 UTC on June 11, the JMA upgraded the system into a tropical depression.^[87] Six hours later, the JTWC issued a TCFA for the system as it began to show characteristics of a monsoon depression.^[88] By 18:00 UTC, the JMA upgraded the system to a tropical storm, assigning it the name Koguma.^[87] On June 12 at 00:00 UTC, the JTWC upgraded Koguma to a tropical depression, assigning it the designation 05W.^[89] Later that day, the JTWC also upgraded Koguma to a tropical storm.^[89] By June 12, it had made landfall southeast of Hanoi,^[90] and dissipated the next day.^[87]

1 person died in Yên Bái province as a result of Koguma.^[91]

At 00:00 UTC on June 18, the JTWC started to monitor a broad area of convection nearly 250 km (160 mi) to the south-southwest of Pohnpei.^[92] The system remained weak as it moved northwestwards in a favorable environment for further intensification, characterized by warm sea surface temperatures, low to moderate wind shear and good outflow; the disturbance remained weak as it moved northwestwards.^[92][93] The JTWC issued a TCFA on the system two days later, though the system remained disorganized.^[94][95] The JMA upgraded the system to a tropical depression at 00:00 UTC on June 21.^[96] Meanwhile, the JTWC designated it as 06W in their first advisory on the system, with an exposed LLCC being evident on satellite imagery due to moderate wind shear, being induced by a tropical upper tropospheric trough to its north.^[97][98] By 21:00 on June 21, 06W made its closest passage to the south-southwest of Guam, continuing its northwest track.^[99][100] On June 22, at 06:00 UTC, the JTWC upgraded the system into a tropical storm as it continued to move away from Guam.^[101] The JMA followed and upgraded the system into a tropical storm, in June 23 at 00:00 UTC, and assigned it the name Champi.^[102] At 18:00 UTC, the JMA upgraded the storm to a severe tropical storm as it turned northwestwards.^[103] At this time, a microwave imagery scan of Champi revealed an eye feature emerging in the system; however, this was short lived as dry air continued to impact the storm from the west.^[104] In addition, poleward outflow on the system remained weak on June 24, restricting Champi to significantly develop.^[105] However, on the next day, as a shortwave trough crossed the Ryukyu Islands, the outflow increased on the storm which allowed it to intensify further.^[106] On June 25, at 06:00 UTC, the JMA officially declared the storm a typhoon.^[107] The JTWC soon followed, upgrading it into a Category 1-equivalent typhoon.^[108] At this time, a Champi turned north and north-northwestwards, and subsequently reached its peak intensity of 120 km/h (75 mph) ten-minute maximum sustained winds with a minimum barometric pressure of 980 hPa (28.94 inHg) by 21:00 UTC on June 25, however it was downgraded to a tropical storm a day later.^[109] The storm continued to weaken as it move towards the Japanese islands, until on June 27, the JMA issued its last advisory at 12:00 UTC as the system became an extratropical low.^[110] The JTWC also issued its last warning for Champi at 09:00 UTC, same day.^[111]

In the wake of the tropical depression, the National Weather Service in Guam issued a tropical storm watch for Rota in the Northern Mariana Islands and a tropical storm warning for the whole island of Guam on June 21.^[112][113] Marine and flash flood warnings were also posted on the former and on Saipan, Tinian, and other islands in the east and south, while classes on an elementary and a high school in the latter were suspended the next day due to a reported power outage.^[114][115] Electrical disruptions were also experienced on Chalan Pago, Toto/Canada, and Santa Rita in Guam due to the system's near approach.^[115] As it moved away from the island and the Marianas, the watch and warning in those areas were lifted at 01:00 UTC on June 22.^[116] In the Bonin Islands, residents in the area were advised of rough seas and gusty winds caused by Champi.^[117]

On July 2, the JTWC started to monitor a tropical disturbance to the southwest of Guam.^[118] Moving northwestwards, the disturbance was located in an environment conducive for intensification in the Philippine Sea, with warm sea surface temperatures, and low wind shear, in addition to good poleward outflow, being induced by an upper-level trough to the northwest.^[119][120] The JMA upgraded the broad and weak system to a tropical depression at 18:00 UTC on the next day,^[121] followed by a TCFA being issued by the JTWC an hour and a half later.^[122][123] The PAGASA subsequently upgraded the system to a tropical depression at 02:00 UTC on July 4, naming it Emong.^[124][125] At 21:00 UTC, the JTWC also upgraded the system to a tropical depression, designating it as 07W.^[126] On July 6, PAGASA issued its last advisory on Tropical Depression Emong at 03:00 UTC as it moved outside the PAR and also lift up the warnings which were imposed earlier in the wake of Emong.^[127] Meanwhile, the JMA soon followed and issued its last advisory.^[128] JTWC also issued its last advisory as its convection was significantly sheared and its low level circulation dissipated rapidly over six hours.^[129][130]

In the Philippines, the depression's approach required the raising of Public Storm Warning Signal No. 1 in the provinces of Batanes and the northeastern portion of Cagayan, including the Babuyan Islands, starting on July 4.^[131][132] The Office of Civil Defense of Cagayan were also on blue alert on the next day due to the storm, with the agency conducting a pre-disaster assessment with other government bureaus that day.^[133] The residents in the coastal areas of Palanan, Divilacan, Maconacon and Dinapigue in Isabela were also warned of the storm while fishing activities in the region were prohibited due to Emong.^[133]

At 12:00 UTC on July 3, the PAGASA started to monitor a low-pressure area that developed near Torrijos, Marinduque or 149 kilometers to the south of Manila, followed by the Joint Typhoon Warning Center (JTWC)'s advisory at 01:00 UTC on the next day, citing the system's development as "low".^[134][135] In the latter's analysis on the disturbance, multispectral and microwave image scans on the system showed a weak low-level circulation center over the eastern part of Mindoro with flaring convection in the western periphery.^[135] Traveling northwestwards, the storm was located in an environment conductive for further intensification, with warm sea surface temperatures of 30–31 °C (86–88 °F), low wind shear around the region and good equatorial outflow; however, model forecasts were split regarding the disturbance's strengthening trend.^[135][136] Also that day at 15:00 UTC, the low-pressure area exited the Philippine Area of Responsibility (PAR), which was followed by the Japan Meteorological Agency (JMA) upgrading the storm to a tropical depression roughly three hours later.^[137][138] Eventually, the JTWC upgraded the system's potential intensification trend to "high" and subsequently issued a Tropical Cyclone Formation Alert at 00:30 UTC on June 6 as a circulation became well-defined.^[139] It then changed its motion towards the west along the periphery of a subtropical ridge on the north and northwest as it approached the Hainan Island.^[140] By 06:00 UTC on the next day, the disturbance moved inland on the region near Lingshui Li Autonomous County before emerging on the Gulf of Tonkin, in an area of low to moderate wind shear.^{[141][142][143]} Later, the disturbance began to reorganize; however, strong wind gradient suppressed its intensification, with flaring convection displaced to the west.^[142] Nine hours later, the JTWC upgraded the system to a weak tropical depression with maximum sustained winds of 45 km/h (30 mph); the JMA analysed the storm to be at 55 km/h (35 mph) and a minimum barometric pressure of 1000 hPa (29.53 inHg).^{[144][145][146]} By the night of that day, the depression, with the identifier 08W from the JTWC made landfall on Thanh Hoa, Vietnam on that intensity, before subsequently issuing their final warning as the agency confirmed that the system dissipated inland, with the evidences of radar and satellite imagery.^[147] The JMA continued to monitor the system until it dissipated at 00:00 UTC on July 8 over Laos.^[148]

PAGASA issued rainfall advisories on July 6 as the depression's precursor low tracked near the Philippines.^[149][150] The China Meteorological Administration (CMA), Hong Kong Observatory (HKO), and Macao Meteorological and Geophysical Bureau (SMG) issued tropical cyclone warnings on July 7.^{[151][152][153]} The warnings imposed by the HKO and SMG were later lifted at 06:10 UTC (14:10 HKT) as the system moved away from Hong Kong and Macao.^[151][154] As the depression approached Vietnam, the Vietnamese Ministry of Defense readied 264,272 soldiers and 1,979 vehicles for potential emergencies.^[155][156] Aquaculture activities were also temporarily banned.^[157] A peak rainfall total of 94 mm (3.7 in) was recorded at Sầm Sơn on July 7.^[158] Rough seas and flooding were experienced in Thanh Hóa's Hoằng Hóa District.^[159] About 7 hectares (17 acres) of rice crops and a water pipeline in Minh Luong commune, Van Ban district were both inundated and washed away by floods in Lào Cai.^[160]

At 06:00 UTC on July 14, the JTWC started to monitor an area of low pressure west-northwest of Guam.^[161] Located in an area favorable for intensification with warm sea surface temperatures as its outflow improved, the system struggled to develop under moderate wind shear before gradually intensifying, with the agency issuing a Tropical Cyclone Formation Alert at 20:30 UTC on the next day.^{[161][162][163][164]} On July 16, the PAGASA upgraded the disturbance to a tropical depression as it entered the Philippine Area of Responsibility, assigning it the local name Fabian.^[165] The JMA later recognized the system as a tropical depression at 03:00 UTC on the same day,^[166] with the JTWC doing the same at 09:00 UTC, designating it as 09W.^[167] On July 18 at 00:00 UTC, the JMA upgraded it to a tropical storm assigning it the name In-fa.^[168] The JTWC also upgraded it to a tropical storm at 03:00 UTC. The system had deep flaring convection, however its low-level circulation was broad and elongated.^[169] On July 18, at 00:00 UTC, the JMA upgraded the system to a severe tropical storm.^[170][171] In-fa started moving westwards,^[172] and as it gradually strengthened, In-fa developed a formative eye on July 20, at 03:00 UTC.^[173] At 09:00 UTC, the JTWC declared In-fa to have strengthened into a typhoon as it had deep convection and robust outflow.^[174][175] The JMA also followed suit and upgraded In-fa to a typhoon at 12:00 UTC because of good upper-level outflow and higher sea surface temperatures; however, its central dense overcast was still obscure.^[176][177] On the next day at 03:00 UTC, In-fa strengthened into a Category 2-equivalent typhoon as its central convection continued to deepen. The feeder bands became more compact and the eye of the typhoon became clearer and more defined.^[178] The JTWC assessed that it peaked as a Category 2-equivalent typhoon with maximum wind speeds of 175 km/h (110 mph) at 03:00 UTC the same day.^[179] Because of dry air,^{[citation needed]} the JTWC later downgraded In-fa to a Category 1-equivalent typhoon at 03:00 UTC the next day despite the presence of warm sea surface temperatures and low wind shear.^[180] On July 23 at 21:00 UTC, In-fa got further downgraded to a tropical storm by the JTWC, as its eyewall became fragmented and the deep convection was not continuous over the eye;^[181] it later re-intensified into a Category 1-equivalent typhoon again at 03:00 UTC the next day as it regained convective depths and it managed to maintain a ragged eye.^[182] At 09:00 UTC, PAGASA issued its final advisory as Typhoon In-fa moved northwards and exited the PAR.^[183] On July 24, at 06:00 UTC, In-fa peaked as a typhoon with maximum 10-minute sustained wind speeds of 150 km/h (90 mph) and a minimum pressure of 950 hPa (28.05 inHg), according to the JMA.^[184] On the next day, the China Meteorological Administration (CMA) noted In-fa to have made landfall in Putuo Island at around 04:30 UTC.^[185] After making landfall, the JTWC downgraded it to a tropical storm at 09:00 UTC as it eye structure began to degrade.^[186] JMA later downgraded to a severe tropical storm at 12:00 UTC, because of influence of land and involvement of dry air.^[187]

On July 17, the JMA reported that a tropical depression had formed.^[188][189] The JTWC later issued a TCFA for the system, as the aforementioned area of convection became more organized.^[190] By the following day, the JTWC upgraded the system to a tropical depression and designated it as 10W, with the storm possessing an improved convective structure and a defined low-level circulation.^[191][192] The JTWC upgraded the system to a tropical storm at 21:00 UTC as it had a defined low-level circulation center with improved banding structure.^[193] At 00:00 UTC on July 19, the JMA upgraded the system to a tropical storm, assigning it the name Cempaka.^[194] At 21:00 UTC, the JTWC declared Cempaka to have strengthened into a Category 1-equivalent typhoon as it developed a ragged 15 nmi (28 km; 17 mi) wide eye.^[195][196] The JMA later upgraded it to a severe tropical storm at 00:00 UTC on the next day.^[197] On July 20, at 06:00 UTC, Cempaka peaked as a severe tropical storm with 10-sustained maximum wind speed of 55 kn (100 km/h; 65 mph) with minimum pressure of 990 hPa (29.23 inHg), according to JMA.^[198] JTWC assessed that it peaked as a typhoon with maximum 1-minute sustained wind of 80 kn (150 km/h; 90 mph).^[199] Cempaka made landfall near Jiangcheng District, Yangjiang, Guangdong Province,^[200] and the JTWC downgraded it to a tropical storm at 18:00 UTC the same day as its low-level circulation center became obscure.^[201] The JMA also downgraded Cempaka to a tropical storm at 00:00 UTC the next day as it moved further inland and its central dense overcast disappeared.^[202][203] At 09:00 UTC, the JTWC further downgraded Cempaka to a tropical depression as its deep convection declined; however, it still retained a well-defined wind field.^[204] After moving inland, Cempaka started moving westward at 00:00 UTC on July 21 due to weak steering flow.^[205] Remaining inland, Cempaka maintained tropical storm intensity as it continued westward, but due to unfavorable conditions over land, it weakened into a tropical depression on the next day at 00:00 UTC.^[206] On July 22, at 09:00 UTC, Cempaka then moved southwards towards the Gulf of Tonkin because of the influence of the monsoonal westerlies, while maintaining its tropical depression intensity inland.^[207] Cempaka moved southward, crossed Móng Cái, Quảng Ninh Province in Vietnam and later entered the Gulf of Tonkin at 03:00 UTC.^[208] However, Cempaka further weakened despite the presence of warm sea surface temperatures because of high monsoonal wind shear and land interaction.^[209][210] At 15:00 UTC, the JTWC issued its final warning on the system as it became a weakly defined system with an exposed low-level circulation center over Bạch Long Vĩ Island.^[211] On July 26 at 00:00 UTC, the JMA issued its last advisory.^[212]

In preparation for the tropical depression, the HKO issued a Signal No. 1 warning for Hong Kong at 13:40 UTC on July 18, which was later upgraded to a Signal No. 3 warning as Cempaka neared the Pearl River Delta. However, as it moved away from Hong Kong, the HKO downgraded it to a Signal No. 1 warning, which was later cancelled at 11:40 UTC.^{[213][214][215][216]} The CMA issued an orange alert for the southern provinces of China as Cempaka moved closer to Guangdong, China, though it was later downgraded to a blue alert as it entered the Chinese mainland.^[217][218] It was later lifted by the CMA, as the threat of Cempaka was minimal.^{[citation needed]} As Cempaka made landfall in Guangdong, there were reports of heavy rainfall and rough waves in the region. Over 990 flights were cancelled in Guangzhou, Shenzhen and Zhuhai.^{[citation needed]} The influence of Cempaka caused heavy rainfall in Henan Province, along with In-fa causing devastating floods in the region.^[219]

The JMA has upgraded Cempaka's intensity from Severe Tropical Storm to Typhoon in the post analysis.

At 06:00 UTC on July 22, the Joint Typhoon Warning Center (JTWC) started to monitor a tropical disturbance with subtropical features along the eastern portion of a monsoon trough, located approximately 466 nmi (865 km; 535 mi) to the north of Guam. A weak system, multispectral satellite imageries revealed that the disturbance was disorganized along the said trough, while advanced scaterrometer data showed the same feature with southerly convergent flow over the northern Mariana Islands. Environmental analysis depicted an unfavorable amount of wind shear, although the agency noted that the disturbance could form as a subtropical cyclone along the subtropical trough with the help of baroclinity.^[220] Tracking northeastward, the system slowly organized, with a low-level circulation center developing seen on meteorological satellite imageries. The Japan Meteorological Agency (JMA) designated the disturbance as a tropical depression, seventeen hours later while the JTWC upgraded the system's potential intensification trend from "medium" to "high" and subsequently issued a Tropical Cyclone Formation Alert (TCFA) on the storm at 22:30 UTC that day.^{[221][222][223]} At 12:00 UTC, Dvorak intensity observations and surface wind data from satellite scatterometer confirmed that the depression further intensified to the eighth tropical storm of the season, whereupon the JMA named it as Nepartak.^[224] The JTWC, however only issued its first warning on Nepartak as Tropical Depression 11W, three hours later as its LLCC further became broad and exposed with its center remaining weakly defined while being steered on the continued direction by a north–south oriented subtropical ridge.^[225][226] Nine hours later, the agency further upgraded the system to a subtropical storm as vigorous deep convection further became constant on the east of the still-exposed and elongated circulation center.^[227][228] By July 24, Nepartak was guided north-northeastwards by an upper-level low and a trough. Baroclinic interaction with the latter also led to the development of a large and asymmetric wind field, with the maximum sustained winds of 35 kn (40 mph; 65 km/h) being far from the center.^[228][229] Later, the system's core became ragged as it turned northwards and further northeast before shifting north again while remaining at that intensity. At 09:00 UTC of the next day, the JTWC noted two distinct vorticities, being spaced 350 nmi (650 km; 405 mi) to each other, with each having an elongated circulation from the south-southwest to the north-northeast.^[230][231]

The intensity of Nepartak remained at 65 km/h (40 mph) until 15:00 UTC on July 26, when the system slightly intensified to 40 kn (45 mph; 75 km/h) as it underwent a rapid structural evolution while moving west-northwestwards. At that time, the storm was now almost centered underneath an upper-level low, in which it interacted with for several days prior. Nepartak also began to accelerated as it moved poleward, while subsequently reaching its peak intensity 12 hours later, with winds of 45 kn (50 mph; 85 km/h) and a minimum barometric pressure of 990 hPa (29.23 inHg).^[232][233] As it turned towards the north, the system started to approach the Tōhoku region, and its circulation center became well-defined while located under the cold-core low, which was causing dry air intrusions within the cyclone. The system began to weaken to a low-end tropical storm before making landfall near the town of Minamisanriku in Miyagi Prefecture at 23:00 UTC as a subtropical depression.^{[234][235][236]} As it rapidly crossed far western Honshu, its LLC became disorganized and ragged, with its convective signature collapsing as it crossed the Japanese Alps. At 15:00 UTC on July 28, the JTWC issued its final warning and bulletin on the system as it emerged over the Sea of Japan.^[237][238] Meanwhile, the JMA continued to monitor the remaining remnants on the area until it dissipated at 12:00 UTC on July 31.^[239]

The system was the first tropical cyclone to make landfall in any part of Miyagi Prefecture since reliable records began in 1951.^[240] As Nepartak was anticipated to bring bad weather in the midst of the 2020 Summer Olympics, the rowing competitions were rescheduled.^[241][242]

On August 1, the JTWC issued a TCFA for a disturbance in the open western Pacific as it had an ill-defined low-level circulation center and deep convection.^[243] On the next day, at 00:00 UTC, the JMA recognized it as a tropical depression as it was located near Minami-Tori-shima. It was moving northwards at 10 kn (19 km/h; 12 mph).^[244] A few hours later, the JTWC upgraded the system to a tropical depression, giving it the designation 12W. At that time, the LLC of the storm remained exposed and its strongest convection or thunderstorms were displaced to the west.^[245] A deep-layered subtropical ridge to the east guided the depression to move to the north-northwest while being near from a monsoon gyre.^[245] Despite being located in a favorable environment for additional strengthening, another system to the south slowly interacted with the depression, which weakened the storm's intensity. It reached its peak intensity that day, with winds of 55 km/h (35 mph) in the estimates of the JMA and the JTWC.^[246][247] By August 3, the JTWC downgraded 12W to a disturbance as its structure deteriorated;^[248] the agency upgraded it back to a tropical depression a day later.^[249] The system's LLC then became fully exposed,^[250] and on August 6, both the JTWC and the JMA assessed that 12W had dissipated.^[249][251]

On August 2, the JMA noted a tropical depression near Zhanjiang had formed.^[252] Soon afterwards, the JTWC issued a TCFA on the disturbance situated approximately 153 nm west-southwest of Hong Kong.^[253] On the same day at 21:00 UTC, the JTWC assessed the system as a tropical depression and accordingly designated it as 13W.^[254] Twenty-four hours later, the agency upgraded the system to a tropical storm.^[255] On August 4 at 12:00 UTC, the JMA followed suit and designated the system as a tropical storm, assigning it the name Lupit.^[256] A day later at 03:20 UTC, it made landfall over Nan'ao County in Shantou, Guangdong Province.^{[citation needed]} At 08:50 UTC, it made another landfall over Dongshan County in Zhangzhou, Fujian Province.^[257] On August 7, it headed eastward and briefly entered the PAR, and was named Huaning by PAGASA.^[258] On August 8, at 18:00 UTC, Lupit peaked as a tropical storm with maximum 10-minute sustained winds of 45 kn (85 km/h; 50 mph) and minimum pressure of 985 mb (29.09 inHg).^[259] Maximum 1-minute sustained speed of Lupit was 45 kn (85 km/h; 50 mph).^[260] On August 9, at 00:00 UTC, the JMA issued its final warning, as it completed its extratropical transition.^[261] At 21:00 UTC, the JTWC followed and issued its final warning.^[262]

Four were reported dead and one were missing due to Lupit in Taiwan; two drowned in Ren'ai, Nantou when they were washed away by a stream on August 6, one when a teenager fell into the Zengwen Reservoir on August 11 while getting a phone that he dropped on the area; his body were recovered on the next day by the authorities.^{[263][264][265]} A man whose jogging in Anping Harbor was killed as he was smashed by a large wave into a seawall in the said area on August 7, while his two friends were injured.^[266]

On August 3, at 18:00 UTC, the JMA issued a tropical cyclone advisory for a tropical depression which was located off the east coast of Taiwan and north of the Philippines.^[267] The JMA later issued its first prognostic reasoning at the same time, stating that clusters of convective bursts were scattered around the low-level circulation.^[268] At 22:00 UTC, the same day, the JTWC issued a TCFA for the system, as it had a consolidating low-level circulation, and it was located in a very conductive environment with high sea surface temperatures and low to moderate vertical wind shear.^[269] On the next day, at 03:00 UTC, the PAGASA recognized it as a tropical depression and named it Gorio, as it was located inside the PAR.^[270] At 06:00 UTC, the JTWC did the same and designated it as 14W, as satellite imagery showed a fully exposed mesovortex.^[271][272] On August 5, at 06:00 UTC, the JMA upgraded it to a tropical storm, naming it as Mirinae. Clusters of convective bursts were gathering around the center with a curved manner, with Mirinae having distinct anticyclonic outflow.^[273] At 15:00 UTC, the JTWC followed and upgraded it to a tropical storm, as the storm developed a partially exposed low-level circulation center. Flaring convection was present, though it was affected by moderate westerly wind shear.^[274][275] On August 7, at 18:00 UTC, Mirinae peaked as a tropical storm with maximum 10-sustained wind speed of 50 kn (95 km/h; 60 mph) and minimum barometric pressure of 980 mb (28.94 inHg).^[276] Maximum 1-minute sustained wind speed of Mirinae was 55 kn (100 km/h; 65 mph).^[277] On August 9, at 09:00 UTC, the JTWC issued its final warning for the system.^[278] The JMA later issued its last warning on the next day at 00:00 UTC, as it became an extratropical cyclone.^[279]

On August 3, at 06:00 UTC, the JMA noted a tropical depression north of the Mariana Islands which was moving northwards at 10 kn (19 km/h; 12 mph).^[280] At 03:00 UTC, the next day, the JTWC issued a TCFA for the system. By that time, it had developed a partially obscured low-level circulation center.^[281] At 15:00 UTC, the JTWC recognized it as a tropical depression, designating it as 15W.^[282] On August 5, 03:00 UTC, the JTWC upgraded it to a tropical storm, as its low-level circulation center became more defined.^[283][284] Three hours later, the JMA followed and named it Nida. Satellite imagery showed that convective bursts were organized into a curved band and that the system was exhibiting good anticyclone outflow.^[285] On August 6, at 18:00 UTC, the JMA upgraded it to a severe tropical storm, as it had distinct anticyclonic outflow.^[286] Nida then started moving eastwards at 6:00 UTC the next day, because of a mid-level subtropical high-pressure area along with the westerlies.^[287] On August 7, at 09:00 UTC, the JTWC issued the last advisory for the system, as its low-level circulation center was partly exposed due to the westerlies inflicting shear upon the storm.^[288] However, the JMA continued to publish bulletins for the system. Nida continued its trajectory. On August 7, 12:00 UTC, the JMA downgraded it to a tropical storm due to shear and a generally less conductive environment.^[289] The JMA further downgraded it to an extratropical low at 00:00 UTC the next day as it completed its extratropical transition.^[290]

On August 6, the Central Pacific Hurricane Center (CPHC) first noted an area of disturbed weather positioned around 1,000 mi (1,610 km) south-southwest of Honolulu.^[291] Four days later, the low-pressure area crossed the International Date Line, and on August 10, at 06:00 UTC, the JMA declared it as a tropical depression as it was located northeast of Ratak.^[292][293] By 13:00 UTC, the JTWC issued a TCFA for the system as satellite imagery showed it had developed a well-defined low-level circulation.^[294] At 15:00 UTC, the JTWC recognized it as a tropical depression and designated it as 16W as satellite imagery depicted developing spiral bands and a defined low-level circulation center.^[295][296] The system briefly became a tropical storm;^[297] However, at 21:00 UTC, the JTWC downgraded it to a tropical depression^[298] as its convection struggled to organize itself.^[299] It regained its intensity at 09:00 UTC the next day^[300] as its convection became more organized. Satellite imagery also continued to indicate the presence of a well-defined low-level circulation center.^[301] It was downgraded to a tropical depression again on the next day^[302] as its low-level circulation center became less defined.^[303] On August 16, at 00:00 UTC, the JMA issued its final advisory for the system, losing its tropical cyclone characteristics because of unfavorable conditions.^[304] Later at 00:00 UTC, the next day, the JMA started tracking the system again.^[305] At 09:00 UTC, the JTWC issued its final advisory as the system's convection became further disorganized despite the presence of a marginally favorable environment.^[306] At 19:30 UTC on August 18, the JTWC issued a TCFA for its remnants as its low-level circulation center improved significantly.^[307] On August 19, the system was upgraded by PAGASA to a tropical depression, and a few hours later, it received the local name Isang as it entered the Philippine Area of Responsibility.^[308] At 15:00 UTC, the system was re-upgraded to a tropical depression by the JTWC,^[309] as its deep convection started to become more organized over the low-level center.^[310] On August 20, at 12:00 UTC, the JMA upgraded to a tropical storm, naming it as Omais. Favorable conditions like high sea-surface temperatures, high tropical cyclone heat potential, and low wind shear helped it to develop over the past few hours.^[311] The JTWC did the same thing at 21:00 UTC, the same day.^[312] At 18:00 UTC the next day, the JMA upgraded it to a severe tropical storm as satellite imagery showed convective bursts gathering around the center in a curved manner;^[313] however, shortly after at 06:00 UTC on August 22, it weakened into a tropical storm due to increasing wind shear from the westerlies.^[314] At 03:00 UTC on August 23, the JTWC downgraded it to a tropical depression^[315] as its convection was severely affected by the extremely high westerly wind shear.^[316] On August 24 at 00:00 UTC, the JMA issued its final advisory as the system became an extratropical cyclone over the Sea of Japan.^[317] Nine hours later, the JTWC followed and issued its last warning for Omais.^[318]

As the system neared the islands of Guam, the NWS issued a tropical storm watch at 22:36 UTC on August 14.^[319] At 10:00 UTC on August 15, the NWS issued a tropical storm watch for the island of Rota.^[320] However, all watches were lifted by the NWS at 09:14 UTC the next day as the system further weakened.^[321]

On September 1 on 00:00 UTC, the JMA noticed a tropical depression near Wake Island.^[322] At 06:00 UTC, the JTWC gave a medium chance of formation for the system over the same area, despite being classified as subtropical depression, as it developed a well defined, partially exposed low-level circulation center.^[323] At 20:00 UTC, the JTWC issued a TCFA for the system,^[324] and at 03:00 UTC the next day, it was upgraded to a tropical depression and was designated as 17W,^[325] as its low-level circulation center became more defined but still partially exposed.^[326] The system maintained its defined convective structure,^{[327][328][329][330]} however at 09:00 UTC on September 3, it struggled to consolidate because of presence of dry air causing its convective structure to diminish.^[331][332] At 21:00 UTC, the JTWC issued its final advisory as its remaining convection was sheared by the incoming westerlies.^[333] At 12:00 UTC on September 4, the JMA stopped tracking the system.^[334]

On September 3, a disturbance was noted by the JTWC, approximately 195 nmi (225 mi; 360 km) from Andersen Air Force Base in Yigo, Guam, as it developed a weakly defined low-level circulation center.^[335] The disturbance gradually intensified, and on September 5, the JMA recognized the system as a tropical depression.^[336] Later that day, the JTWC issued a TCFA as its low-level circulation center and its surrounding convection became well organized.^[337] The agency recognized the system as a tropical depression around four hours later.^[338] At 21:00 UTC, the PAGASA recognized the system as a tropical depression, with the agency assigning it the local name Jolina.^[339] The next day on 06:00 UTC, the JMA upgraded the system to a tropical storm, assigning it the international name Conson, with the JTWC following suit three hours later.^[340][341] At 12:00 UTC, the JTWC upgraded it typhoon before downgrading it into a tropical storm at 18:00 UTC.^[342] Three hours later, the JMA upgraded it to a severe tropical storm.^[343] At the same moment, Conson rapidly intensified into a typhoon according to the PAGASA as it made its first landfall on Hernani, Eastern Samar.^[344] Conson then made another landfall at 02:30 PHT (18:30 UTC) in Daram, Samar, and another one at 03:40 PHT (19:40 UTC) in Santo Niño, Samar.^[345] At 06:30 PHT (22:30 UTC), Conson made a fourth landfall in Almagro, Samar. At 00:00 UTC on September 7, the JMA downgraded it to a tropical storm as it was significantly weakened by multiple landfalls.^[346] Conson then made a fifth landfall in Dimasalang, Masbate at 11:00 PHT (03:00 UTC), later weakening into a severe tropical storm, according to PAGASA.^[347][348] Conson then made a sixth landfall over Torrijos, Marinduque.^[349] Conson continued to pummel through more islands, making a seventh landfall over the area in Lobo, Batangas.^[350] After making its eighth landfall at San Juan, Batangas, Conson traversed the Batangas – Cavite area as the PAGASA declared it to have weakened back into a tropical storm.^[351] Conson made its ninth and final landfall in the vicinity of Mariveles, Bataan.^[352] At 12:00 UTC, Conson re-intensified into a severe tropical storm, as it entered the West Philippine Sea.^[353] Three hours later, the PAGASA issued its final bulletin for Conson as it exited the PAR and accelerated westward.^[354]

As Conson moved westward, it came in contact with unfavorable conditions such as increasing vertical wind shear and land interaction with Vietnam. These conditions made Conson weaken, prompting the JMA to downgrade it to a tropical storm at 12:00 UTC on September 11 to further downgrade it to a tropical depression at 18:00 UTC the same day, with the JTWC downgrading it to a tropical depression at 03:00 UTC on September 12.^{[355][356][357]} It stalled off the coast of Vietnam near Quang Nam because of the confluence of three ridges.^{[358][359][360]} At 21:00 UTC, the JTWC issued its final advisory as it made landfall near Da Nang, Vietnam, which caused the system to weaken rapidly. Satellite imagery showed that its low-level circulation center weakened significantly and became less defined.^[361] By 18:00 UTC of September 13, the JMA stopped tracking Conson,^[362] as the agency last noted it at 12:00 UTC.^[363]

According to the NDRRMC, 23 people were killed in the Philippines due to the storm, with combined infrastructural and agricultural damages pegged at ₱5.17 billion (US$88.3 million).^[364] In Vietnam, 2 people were killed by flooding.^[365] Agriculture damages on the offshore island of Lý Sơn was estimated to be about 100 billion ₫ (US$3.9 million).^[366]

At 06:00 UTC on September 5, the JTWC began monitoring an area of convection that had formed 446 nmi (513 mi; 826 km) from Legazpi, Philippines.^[367] At 18:00 UTC the same day, the JMA declared it as a tropical depression.^[368] Five and half hours later, the JTWC issued a TCFA as its circulation and convection had significantly improved.^[369] At 09:00 UTC the next day, the JTWC upgraded the disturbance to a tropical depression, designating it as 19W.^[370] The JTWC later upgraded it to a tropical storm as it was noted that an eye-like feature was forming.^[371] The JMA later did the same at 00:00 UTC on September 7, naming it Chanthu.^[372] At 09:30 UTC, the PAGASA reported that Chanthu entered the PAR, assigning it the name Kiko.^[373] At 12:00 UTC, the JMA upgraded it to a severe tropical storm.^[374] At the same moment, Chanthu started its rapid intensification as it quickly became a minimal typhoon.^[375][376] Several hours later, the typhoon reached Category 4-equivalent status, and by the next day at 09:00 UTC, it reached Category 5-equivalent intensity, developing a 5 nmi (10 km; 5 mi)-wide eye which was surrounded by very compact, intense convection.^[377][378] After reaching its initial peak, Chanthu was downgraded to a Category 4-equivalent super typhoon as its pinhole-shaped eye started to fade.^[379] However, by September 10, Chanthu began to re-intensify as its eye began to clear up.^[380] Chanthu further intensified into a Category 5-equivalent super typhoon once again at 09:00 UTC that day.^[381] On 05:00 PHT on September 11 (21:00 UTC on September 10), the PAGASA reported that Chanthu passed to the east of the Babuyan Islands;^[382] at 08:30 PHT (00:30 UTC), Chanthu made landfall in Ivana, Batanes as the storm began to weaken slightly.^[383][384] On September 11, Chanthu began to weaken as it continued to move northwards with the presence of dry air.^[385] The PAGASA issued its last bulletin for Chanthu since it exited the PAR on the next day.^[386] By September 14, Chanthu was no longer a typhoon as it slowly moved south-eastwards towards Japan.^[387] Due to decreasing wind shear and marginally favorable sea surface temperatures, Chanthu strengthened enough for the JMA to re-classify it as a severe tropical storm on the next day.^[388] On September 17 on 09:00 UTC, Chanthu crossed near the town of Ikitsuki, Nagasaki in Japan.^[389] It continued to move northwards as it moved through the rugged Japanese islands, causing it to weaken significantly.^[390] This caused the JMA to downgrade it to a tropical storm three hours later.^[391] At 21:00 UTC, the JTWC downgraded it to a tropical depression, as it was also undergoing extratropical transition.^[392] On September 18, the JTWC issued its final warning for the system.^[393]

Chanthu caused devastating effects in the islands of Batanes as it was made a direct hit from the typhoon. According to the local residents it was the most ferocious storm even seen.^[394] More than 30,000 residents were affected from Region I, II, III and CAR. Four municipalities went without power and none were restored and one municipality experienced water supply outage and none were restored. There were also reports of landslide and flooding mostly from Region I and III. As of September 15, total damages from the typhoon were up to ₱37.4 million (US$748,000).^[395] On September 12, Chanthu passed east of Taiwan. This caused heavy rainfall over the island including the capital city Taipei. Up to 13 cm (5.1 in) of rainfall was recorded and winds up to 164 km/h (102 mph) were reported.^[396] In China, the storm shut down both Shanghai Port, the world's largest container port, and Ningbo-Zhoushan Port, the world's largest port by cargo throughput, briefly on 12–14 September, with about 86 vessels waiting outside the ports. ^[397] As Chanthu passed near the island of Jeju, it caused winds up to 30 to 40 m/s (110 to 145 km/h; 65 to 90 mph) and 50 mm (2.0 in) of rainfall. There were reports of structural damage and overwhelmed drainage systems on the island. 23 flights were grounded and 48 ferry sailings were cancelled.^[398]

On September 21, the JTWC spotted an area of convection formed approximately 703 nmi (1,302 km; 809 mi) from Guam.^[399] The system rapidly consolidated itself and formed a well-defined LLCC,^[400] and thus, the system strengthened into a tropical depression on 00:00 UTC of September 22.^[401] The JTWC did the same later that day, designating the system as 20W.^[402] At 09:00 UTC of September 23, the JTWC upgraded it to a tropical storm, as its low-level circulation center became partially exposed.^[403] The JMA did the same three hours later, and named it Mindulle.^[404]

At 12:00 UTC of September 24, the JMA upgraded it to a severe tropical storm.^[405] By 03:00 UTC the next day, the JTWC upgraded it to a Category 1-equivalent typhoon, as it developed a small eye. The presence of dry air had slowed its intensification, but it still managed to become a typhoon.^[406][407] Mindulle started to rapidly intensify as it quickly intensified into a Category 2-equivalent typhoon. Its eye expanded but became ragged due to the presence of dry air.^[408] Mindulle continued its rapid intensification, as it further intensified into a Category 4-equivalent typhoon at 15:00 UTC. Its eye became well-defined and at 03:00 UTC the next day, it became a Category 5-equivalent super typhoon, making it the third super typhoon of this season. Satellite imagery showed that the typhoon had developed a well defined 15 nmi (28 km; 17 mi) eye and deepening of the central core.^[409]

At 15:00 UTC, Mindulle weakened into a Category 4-equivalent super typhoon as the eye and the convective structure started to degrade. It also underwent an eyewall replacement cycle, as it developed another eyewall.^[410] At 03:00 UTC of September 27, the JTWC further downgraded the system to a Category 3-equivalent typhoon,^[411] and six hours later, the agency had further downgraded it to a Category 2-equivalent typhoon because of the effects of the eyewall replacement cycle and the increasing presence of dry air.^[412] At 15:00 UTC of September 28, Mindulle re-intensified into a Category 3-equivalent typhoon, as it moved over favorable conditions. Satellite imagery showed that the typhoon continued to struggle to intensify. Its 20 nmi (37 km; 23 mi) eye had steadily shrunk but it remained cloud covered and ragged.^[413] By the next day at 03:00 UTC, the JTWC re-upgraded it to a Category 4-equivalent typhoon as the eye cleared out again.^[414] At 21:00 UTC of September 29, it rapidly weakened and by 15:00 UTC the next day, it weakened from a Category 3-equivalent typhoon to a Category 1-equivalent typhoon. Cool dry air and cool sea-surface temperatures were responsible for the weakening.^{[415][416][417]} At 21:00 UTC of October 1, the JTWC issued its final warning as it downgraded to a tropical storm.^[418] Three hours later, JMA also issued its final warning, as it became extratropical cyclone, off the coast of Hokkaido.^[419]

On September 21 at 18:00 UTC, the JMA noted a westward-moving low-pressure area over the South China Sea near the Philippines.^[420] Three hours later, the JTWC recognized this system.^[421] By 15:00 UTC the next day, the JTWC upgraded it to a tropical depression without issuing a TCFA for the system, as it rapidly improved its convective structure and developed a low-level circulation center;^[422] the JMA did the same three hours later.^[423] On September 23 at 06:00 UTC, the JMA upgraded it to a tropical storm and named it as Dianmu as it continued to move westward and come closer to the Vietnamese coastline.^[424] The JTWC did the same thing, three hours later.^[425] At 15:00 UTC, the JTWC issued its last warning on the system as it made landfall near Da Nang, Vietnam, with its low-level circulation center being hampered following landfall.^[426] At 06:00 UTC on September 24, the JMA downgraded it to a tropical depression as it moved further inland.^[427]

Dianmu caused a total of 8 deaths, of which 6 occurred in Thailand and 2 occurred in Vietnam.^[428][429]

On October 2, the JTWC noted an area of convection located approximately 495 nautical miles (917 km; 570 mi) east of Davao, Philippines^[430] The next day, PAGASA had already classified the system as a tropical depression and named it Lannie.^[431] Lannie made its first landfall on Bucas Grande Island at 04:30 PHT (October 3, 20:00 UTC). It then made an additional seven landfalls: ones in Cagdianao in the Dinagat Islands, Liloan and Padre Burgos in Southern Leyte, Mahanay Island and Getafe in Bohol, San Fernando in Cebu, Guihulngan in Negros Oriental, and its last two landfalls at Iloc Island and El Nido, Palawan.^[432][433] At 14:30 UTC of October 4, the JTWC re-issued a TCFA for the system, as it moved over the South China Sea.^[434] At 06:00 UTC of October 5, the JMA recognized it as a tropical depression.^[435] At 11:00 PHT (03:00 UTC) of October 6, the PAGASA issued its final warning.^[436] At 09:00 UTC of the next day, the JTWC upgraded from a monsoonal depression to a tropical depression. It was designated as 22W. Before landfall in Hainan, the JMA upgraded it to a tropical storm and named it Lionrock at 18:00 UTC.^[437]

Lionrock continued its trajectory, and between 09:00 UTC and 15:00 UTC of October 8, it made its first landfall over the island of Hainan.^[438][439] After making landfall, it briefly intensified a bit before weakening to its original intensity at 21:00 UTC.^[439][440] At 09:00 UTC of the next day, it crossed the island completely and entered the Gulf of Tonkin.^[441] On October 10, at 09:00 UTC, the JTWC downgraded it to a tropical depression and issued its last warning, as it made landfall near Cat Bi International Airport and its convection became disorganized over land.^[442]

On October 6 of 18:00 UTC, the JMA noted that a low-pressure area had formed that was embedded in a large monsoonal circulation to the north of Palau.^[443] The system developed into a tropical depression at 00:00 UTC of the next day.^[444] At 09:00 UTC (17:00 PHT), the PAGASA issued its first bulletin for the first tropical depression and assigned it the name Maring.^[445] The JMA also noted the persistence of another, nearby tropical depression to its northeast, later named Nando.^[446] As it is embedded in the same monsoonal depression and due to its proximity, Nando began to merge with Maring, and therefore formed a rather broad and large circulation. This prompted the JMA to upgrade the overall system to a tropical storm, and was named Kompasu.^[447] However at that time, the JTWC still considered the system as two separate disturbances and issued separate TCFAs later in the day for both depressions, albeit noting the possibility of merging.^[448][449] The JTWC later considered the entire system as merged with their first warning for Kompasu.^[450] At midnight of October 11, the JMA upgraded it to a severe tropical storm, as it attained good cloud characteristics.^[451] At 12:10 UTC (20:10 PHT), Kompasu made its first landfall near Fuga Island of Cagayan Province.^[452] At 05:00 PHT of October 13 (21:00 UTC of October 12), the PAGASA issued its final bulletin as its exited the PAR and continued towards Hainan.^[453] Between 03:00 and 09:00 UTC of October 13, Kompasu had made landfall over the east coast of Hainan.^[454][455] By 18:00 UTC, the JMA downgraded it to a tropical storm, as it crossed the entire island and entered the Gulf of Tonkin, as its convection had rapidly weakened because of the rough terrain of the island.^[456][457] At 09:00 UTC of the next day, the JTWC issued its final warning followed by downgrading to a tropical depression, as its convection had diminished and the low-level circulation center had been weakened significantly because of the increasing vertical wind shear and dry air, despite not making landfall over northern Vietnam.^[458] The JMA issued its final warning after downgrading it to a tropical depression at 18:00 UTC.^[459][460]

As of October 31, the NDRRMC has confirmed a total of 43 deaths, along with 16 people still missing. Total estimated damages of both infrastructure and agriculture is topped to ₱6.39 billion (US$126.5 million).^[461] In Hong Kong, one person was killed and 21 people were injured.^[462]

On 00:00 UTC of October 7, the JMA began monitoring on a tropical depression that had developed to the north of Palau, that was embedded in the same monsoonal circulation as Tropical Depression Maring.^[463] As the circulation moved inside the Philippine Area of Responsibility, the PAGASA began issuing advisories and assigned the local name Nando to the depression.^[464] By the next day, the JMA stopped tracking the system after it began to merge with Maring, which subsequently became Tropical Storm Kompasu.^[465] The PAGASA issued its final bulletin on the system on October 9.^[466] The JTWC issued separate TCFAs for two invests in the monsoonal depression that contained Maring and Nando — Invests 93W and 94W, respectively.^[449] As the two merged, the JTWC cancelled the TCFA for Invest 93W and soon began issuing a single tropical cyclone warning for the overall system.^[467][450]

On October 8, the JTWC noted an area of convection persisted approximately 289 nmi (535 km; 333 mi) from Wake Island, which had a defined low-level circulation with a good outflow.^[468] The JMA later recognized the same area of convection as a tropical depression on October 9.^[469] At 14:00 UTC the same day, the JTWC issued a TCFA for the invest as it developed a flaring convection which was circulating over the obscured LLCC.^[470] By midnight of the next day, the JMA upgraded it to a tropical storm and named it Namtheun.^[471] The JTWC recognized it as a tropical depression, three hours later,^[472] and six hours later, the JTWC upgraded it to a tropical storm.^[473] Namtheun managed to maintain its intensity for two days, until at 09:00 UTC of October 13, it was downgraded to a tropical depression by the JTWC, as it started moving westwards because of the presence of a subtropical ridge towards the southeast of the system. Satellite imagery showed that the deep convection had been displaced towards the northeast and the LLCC of the system had become less defined.^[474] However at 15:00 UTC of the next day, the JTWC re-upgraded it to a tropical storm, as it entered over warm sea-surface temperatures which allowed the system to maintain its intensity despite high wind shear. Satellite imagery also indicated that it developed subtropical characteristics.^[475] Unexpectedly, Namtheun further intensified into a severe tropical storm according to JMA at 06:00 UTC of October 16, and a Category 1-equivalent typhoon according to JTWC at 09:00 UTC of October 16.^[476][477] Satellite imagery depicted that the system had developed a compact core with improved convection structure near its center. It also developed an eye-like feature. The weakening of the vertical wind shear was main reason for the intensification and also the presence of marginally favorable sea-surface temperatures (26–27 °C (79–81 °F)).^[477] A few hours later, both JMA and JTWC downgraded to a tropical storm, as its convection had weakened significantly because of further cooling of sea-surface temperatures and strengthening of the wind shear.^[478][479] Namtheun managed its intensity as it continued north-northwards but since it was interacting with the baroclinic zone, it started its extratropical transition between 00:00 and 15:00 UTC.^[480][481] For the next several days, the system moved eastward across the North Pacific, before undergoing explosive intensification and developing into a bomb cyclone on October 21, reaching an extratropical peak of 951 millibars (28.1 inHg), while situated off the coast of the Pacific Northwest.^[482] Afterward, the system curved northward and then north-northwestward, while gradually weakening, before being absorbed into another approaching extratropical cyclone from the west, late on October 22.^[483] Namtheun's extratropical remnant brought heavy rain and powerful winds to the Pacific Northwest.^[484][485]

On October 20, the JTWC noted an area of convection approximately 574 nmi (1,063 km; 661 mi) east of Guam. Infrared satellite imagery found that it formed a flaring convection which was displaced to the northwest from the actual center,^[486] but at 06:00 UTC the next day, the JTWC discontinued giving advisories to the area of convection, as its convection had completely dissipated.^[487] On the same day at 18:00 UTC, the JMA recognized the same area of convection, as a low pressure area.^[488] At 15:00 UTC of October 22, the JTWC started giving advisories for the area of convection as it developed sufficient convection and a poorly defined low-level circulation.^[489] On the next day at 18:00 UTC, the JMA upgraded it to a tropical depression,^[490] and three and a half hour later, the JTWC issued a TCFA.^[491] At 03:00 UTC of October 24, the JTWC upgraded to a tropical depression and designated as 25W.^[492] Later at 18:00 UTC, the JTWC upgraded it to a tropical storm, as the organization of the convection had increased.^[493] Six hours later, the JMA did the same thing and named it Malou.^[494] At midday of the next day, the JMA upgraded it to a severe tropical storm.^[495] Early on October 27, the JTWC upgraded it to a Category 1-equivalent typhoon, as it developed an eye-like feature wrapped around a ragged spiral bandings.^[496] At 18:00 UTC the same day, the JMA upgraded it to a typhoon.^[497]

At 00:00 UTC of October 22, the JMA noted the formation of a low-pressure area east of Mindanao.^[498] Two days later at 06:00 UTC, the JMA upgraded it to a tropical depression as it was located off the coast of the island of Palawan.^[499] On the same day, the JTWC noted the same low pressure area and gave a low chance of formation,^[500] which was later upgraded to medium.^[501] At 05:30 UTC of October 25, the JTWC issued a TCFA for the system, as its convection had improved and developed a weakly defined LLCC.^[502] On the next day, after re-issuing the TCFA at 05:00 UTC,^[503] the JTWC upgraded it to a tropical depression at 09:00 UTC as it was located off the coast of Vietnam. Satellite imagery found that its LLCC had become defined however the convective structure continued to remain disorganized.^[504] Between 15:00 UTC of October 26 and 03:00 UTC of October 27, the system made landfall near Nha Trang^[505][506] and at 03:00 UTC, the JTWC issued its final advisory as its convection had rapidly disorganized after landfall, as it moved over the mountainous terrain of Vietnam.^[506]

Over 50,000 sea vehicles with over 261,000 people in it were already informed on the brewing system and its path, according to a meeting about the depression on October 25. Over 3,200 officer soldiers and 270 public vehicles were also put on standby. The areas between Thừa Thiên Huế and Khánh Hòa received heavy rainfall from the system.^[507]

Early of November 26, the JTWC noted the formation of an area of convection located 752 nmi (1,393 km; 865 mi) east-southeast of Guam.^[508] On the next day, the JMA recognized the same system as a low pressure area.^[509] At 06:00 UTC of November 28, the JTWC issued a TCFA as it developed a poorly defined center,^[510] and by midnight of November 28, the JMA upgraded the system to a tropical depression.^[511] The JTWC followed suit and designated it as 27W at 15:00 UTC the same day.^[512] Six hours later, the JTWC further upgraded it to a tropical storm.^[513] At midnight of the next day, the JMA followed suit and named it as Nyatoh.^[514] On 00:00 UTC of December 1, the JMA further upgraded it to a severe tropical storm.^[515] Fifteen hours later, the JTWC declared it a typhoon and upgraded it to a Category 1-equivalent status, as Nyatoh developed an eye according to microwave imagery.^[516] The JMA followed suit at 18:00 UTC.^[517] By 03:00 UTC the next day, it further intensified into a Category 2-equivalent typhoon as it briefly formed a ragged eye.^[518] Later that day, Nyatoh unexpectedly rapidly intensified to a Category 4-equivalent super typhoon due to jet interaction. It later reached peak intensity with 10-minute sustained winds of 185 km/h (115 mph) and a pressure of 925 mb (27.32 inHg).^[519] However, this peak was short-lived as strong wind shear, dry air, and cooler sea surface temperatures shredded the system apart and rapidly weakened to a Category 1-equivalent typhoon at 18:00 UTC. On December 4 at 06:35 UTC, the JMA declared Nyatoh a remnant low.^{[citation needed]}

At 00:00 UTC of December 12, the JMA noted the existence of a tropical depression in the vicinity of the Caroline Islands.^[520] Two hours later, the JTWC issued a TCFA for the developing system, noting a "promising" environment for further development.^[521] On the next day, the JMA upgraded the system into a tropical storm and gave it the international name, Rai.^[522]

The PAGASA issued its first tropical cyclone advisory for the developing storm on December 12.^[523] Warnings for Palau and the Federated States of Micronesia were issued by the Guam National Weather Service by December 13.^[524] On the next day, Rai continued intensifying, and the Japan Meteorological Agency upgraded it to a severe tropical storm.^[525]

Rai then entered the Philippine Area of Responsibility on December 14 and was given the name Odette by the PAGASA.^[526] The PAGASA raised Tropical Cyclone Wind Signal #1 over parts of Eastern Visayas and Northern Mindanao.^{[citation needed]} Later that same day, the JMA upgraded Rai to a typhoon.^[525] The PAGASA^{[citation needed]} and the JTWC later followed suit and also upgraded Rai to a typhoon. Rai then rapidly intensified overnight, becoming a Category 5-equivalent super typhoon on the morning of December 16.^[527]

Rai then made its first landfall on General Luna, Surigao del Norte at 1:30PM PHT.^[528] A few minutes later, it struck Cagdianao, Dinagat Island.^[529] It then made a third landfall in Liloan, Southern Leyte.^[530] It continued to cross the islands and later struck Padre Burgos, Southern Leyte and President Carlos P. Garcia, Bohol.^[531][532] It then soon struck Bien Unido, Bohol.^[533] It lost super typhoon intensity and then struck Carcar, Cebu.^[534] It made an eighth landfall on La Libertad, Negros Oriental.^[535] It made a final landfall in Roxas, Palawan. The system then left the PAR by 12:40 PHT (04:40 UTC).^[536] For the first time since Typhoon Rammasun in 2014 and the third after Pamela of 1954 and the aforementioned storm, Rai unexpectedly attained Category 5-equivalent super typhoon status in the South China Sea, due to the favorable environment in that region, at 21:00 UTC on December 18, as it underwent a secondary period of rapid intensification.^[537]

By 03:00 UTC the next day, Rai again weakened below Category 5-equivalent super typhoon intensity, while turning in a west-northwesterly direction. Its eye was cloud-filled by this time, with the storm rapidly weakening afterward.^[538]

As of January 6, 2022, 410 fatalities have been reported,^[539] with 111 alone being located in Bohol.^[540] On March 23, PAGASA revised their tropical cyclone scale. Rai (Odette) was considered as a super typhoon.^[541]

On December 14, the JMA upgraded a westward-moving low-pressure area to a tropical depression.^[542][543] The JTWC began monitoring the system by the next day, noting the presence of a consolidated low-level circulation within the system.^[544] The system's chances of developing into a tropical cyclone slowly increased,^[545] and on December 16 at 17:30 UTC, the JTWC issued a TCFA for the system despite the outflow of Typhoon Rai partially exposing the system's low-level circulation.^[546] By 21:00 UTC, the JTWC upgraded the system to a tropical depression, assigning it the designation 29W as it continued over marginally favorable developmental conditions.^[547] Shortly after, at 23:00 UTC, the depression made landfall north of Kuantan and began to weaken, prompting the JTWC to issue its final advisory on the system by the next day.^[548] The JMA stopped monitoring the system on December 17 at 12:00 UTC.^[549][550]

After passing through Peninsular Malaysia, it reached the Straits of Malacca as a low-pressure system. Persistent and continuous heavy rains for more than 24 hours began on December 17, causing the worst flooding in Central Malaysia since 2014.^[551][552] Floods were also reported in the states of Kelantan, Terengganu, Pahang, Perak, Negeri Sembilan and Malacca.^[552]

• During January 19, the JMA reported that a tropical depression had developed to the east of Luzon, Philippines.^[553] The precursor to the depression brought scattered showers and thunderstorms to Mindanao, Palawan, and Visayas on January 18.^[554] The JMA, however, discontinued advisories for the system on the next day.^[555] The depression also brought stormy weather to Luzon on January 20. The PAGASA warned residents of possible flash flooding and mudslides due to heavy rainfall.^[556][557] The system's precursor was associated with a frontal system, with its combined effects bringing heavy rainfall over much of Visayas, the Bicol Region, and Northern Mindanao, resulting in three deaths and agricultural damages of up to ₱642.5 million (US$13.2 million).^[558]
• On March 9, a low-pressure area entered the Philippine Area of Responsibility, though it was not expected to develop at that time.^[559][560] On March 14, the low-pressure area intensified into a tropical depression over the Sulu Sea before quickly degenerating back into a low-pressure area.^[561][562] The system brought light to moderate rains over parts of the Philippines, with the PAGASA advising residents of the possibility of floods and landslides.^[563]
• On May 29, the JTWC issued a TCFA for a tropical disturbance that was roughly 622 nautical miles (1,152 km; 716 mi) to the southeast of Guam, near the Nomoi Islands. The system gradually developed as it was experiencing warm sea surface temperatures and low vertical wind shear.^[564] On the next day at 00:00 UTC, the JMA recognized the system as a tropical depression.^[565] On the same day, the JTWC cancelled the TCFA for the system as its structure degraded,^[566] with the JMA last recognizing the system as a tropical depression on June 1 at 18:00 UTC.^[567]
• On June 29, an area of convection formed 425 nmi (787 km; 489 mi) from Guam with satellite imagery revealing that the system had a deep convection with a weak low level circulation.^[568] Within a favorable environments with low-to-moderate wind shear, and warm sea surface temperatures, the system gradually became more organized with a more defined low level circulation. On June 30, the JTWC issued a TCFA for the system.^[569][570] On July 1, animated multispectral satellite imagery indicated a very broad and ill-defined low level circulation with convection being sheared to the south-southwest of the disturbance, which prompted the JTWC to cancel the system's TCFA and downgrade its development chances within the next day to low.^[571] The JMA no longer considered it a tropical depression in their tropical disturbance summary advisories on the same day.^[572]
• On July 19, at 00:00 UTC, a tropical depression formed near 29°N 164°E / 29°N 164°E / 29; 164, which was moving northwards at the speed of 10 kn (20 km/h; 10 mph), according to the JMA.^[573] It lasted for two days until July 21, when it became a remnant low at 00:00 UTC.^[574]
• On July 28, at 00:00 UTC, the JMA noted a tropical depression near 29°N 152°E / 29°N 152°E / 29; 152, which was moving northwards slowly.^[575]
• On July 30, at 00:00 UTC, the JMA noted a tropical depression near 28°N 142°E / 28°N 142°E / 28; 142, which was moving northwestward slowly.^[576]
• On July 31, a tropical depression formed over the open Pacific at 18:00 UTC.^[577] By August 1, at 05:30 UTC, the JTWC issued a TCFA for the system as it had an exposed low-level circulation with persistent disorganized convection.^[578] The agency canceled the alert on the next day as it had little remaining convection and it had moved over cooler waters.
• On August 1, at 18:00 UTC, JMA noted a tropical depression near Taiwan.^[579]
• The JMA began tracking a tropical depression that had formed to the east of Hainan on September 7.^[580] The system moved westward towards Vietnam and was last noted the next day.
• On September 27 of 06:00 UTC, the JMA noted the formation of a low-pressure area located to the east of Typhoon Mindulle.^[581] The JMA later upgraded it to a tropical depression, six hours later.^[582] At 01:00 UTC the next day, the JTWC recognized the system and gave a medium chance of formation.^[583]

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

During the season, 22 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 kilometres per hour (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.^[586] During the season, the names Surigae, Koguma, Cempaka and Nyatoh were used for the first time after they replaced Mujigae, Koppu, Melor and Meranti, which were retired following the 2015 and 2016 seasons.

In early 2023, the Typhoon Committee announced that the names Conson, Kompasu, and Rai would be removed from the naming lists and they will never be used again for another typhoon name.^[587] In 2024, they were replaced by Luc-binh, Tokei, and Sarbul respectively.^[588]

During the season, PAGASA used its own naming scheme for the 15 tropical cyclones that either developed within or moved into their self-defined area of responsibility.^[589] This is the same list used during the 2017 season, except for Uwan and Verbena, which replaced Urduja and Vinta, respectively. No names were used for the first time this year.

After the season, on March 21, 2022, PAGASA removed the names Jolina, Maring and Odette from its rotating naming lists due to the number of deaths and amount of damage they caused, and were replaced with Jacinto, Mirasol and Opong for the 2025 season.^[590][591]

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 2021. 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 2021
• Tropical cyclones in 2021
• Pacific typhoon season
• 2021 Atlantic hurricane season
• 2021 Pacific hurricane season
• 2021 North Indian Ocean cyclone season
• South-West Indian Ocean cyclone seasons: 2020–21, 2021–22
• Australian region cyclone seasons: 2020–21, 2021–22
• South Pacific cyclone seasons: 2020–21, 2021–22