2020 Pacific typhoon season

Very strong typhoon (JMA)
Category 3 typhoon (SSHWS)
Duration	May 8 – May 18
Peak intensity	155 km/h (100 mph) (10-min); 960 hPa (mbar)

A low-pressure area was first noted on May 9 by the JTWC near Micronesia and was given a medium chance of developing into a tropical cyclone.[7] The following day, the JMA declared that it had developed into a tropical depression to the east of Mindanao, Philippines and was expected to slowly move west.[8] The JTWC then issued a Tropical Cyclone Formation Alert (TCFA) for the system just hours later while convection began to gradually obscure the center.[9] Later that day, the PAGASA followed suit and upgraded the system to a tropical depression, assigning it the name Ambo, as it became the first tropical cyclone to enter their area of responsibility for 2020.[10][11]

The system began to slowly drift westwards throughout the following days,[12] and on the next day, the JTWC upgraded Ambo to a tropical depression, designating it as 01W.[13] The storm gradually intensified throughout the day and began to turn north. At this time, the JMA upgraded 01W to a tropical storm and assigned it the first name of the year, Vongfong.[14] Shortly after, the JTWC followed and upgraded the system to tropical storm intensity.[15] Vongfong began to rapidly intensify due to favorable conditions by early May 13,[16] With the JMA upgrading the system to a severe tropical storm and the JTWC upgrading the storm to a Category 1-equivalent typhoon with 1-minute sustained winds of 130 kilometers per hour (81 mph) as the structure quickly improved. The PAGASA and JMA would then upgrade the system to a typhoon later in the day,[16] with the JTWC quickly upgrading the system to a Category 2-equivalent typhoon as the eye became clearer. A few hours later, Vongfong intensified to a Category 3-equivalent typhoon.[17] Then, the storm later went an eyewall replacement cycle, quickly finishing the cycle while fluctuating in intensity.[18] At 12:15 pm PST on May 14, Vongfong made its first landfall in San Policarpo, Eastern Samar.[19] Vongfong gradually weakened shortly after, crossing over the Ticao Pass as it moved further inland.[20] By the succeeding day, PAGASA recorded five more landfalls: hitting the islands of Dalupiri Island, Capul Island, Ticao Island, Burias Island, and San Andres, Quezon in Luzon Island's Bondoc Peninsula.[21] Ambo weakened into a Category 1-equivalent typhoon following the landfalls.[22] The system further weakened on May 15, and was downgraded by both the JMA and PAGASA to a severe tropical storm,[23][24] with the JTWC downgrading it to a tropical storm as well. Vongfong made its seventh landfall on Real, Quezon,[25][26] further weakening and being downgraded by the JMA and the PAGASA into a tropical storm.[27][28] The weakening trend continued, and by May 16, Vongfong emerged into the Luzon Strait as a low-end tropical storm.[29][18] 6 hours later, the JTWC downgraded Vongfong to a tropical depression, and issued their final warning.[30] Soon after, PAGASA[31] and the JMA followed suit as well.[32] The remnants of the storm fully dissipated by May 17, with PAGASA downgrading the storm's remains into a low-pressure area.[33][18]

In preparation for the incoming typhoon, Tropical Cyclone Wind Signal (TCWS) #3 warnings were issued for Northern Samar and the northern portion of Eastern Samar.[34] According to the NDRRMC, Typhoon Vongfong (Ambo) left ₱1.57 billion (US$31.1 million) worth of damages in agriculture, and left 5 dead, as of May 27.[35][36] The international name Vongfong and Philippine name Ambo were retired from use by the Typhoon Committee and PAGASA, being replaced with Penha and Aghon respectively.[37][38][39]

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	June 10 – June 14
Peak intensity	75 km/h (45 mph) (10-min); 996 hPa (mbar)

On June 10, the JMA began monitoring on a weak tropical depression that had developed to the east of the Philippine island of Samar in Visayas.[40] During the next day, the PAGASA began tracking the system, giving the local name Butchoy.[41][42] The storm then made its first landfall in Polillo Island in Quezon at 5:30 pm PHT, and making its second landfall in Infanta, Quezon shortly thereafter.[43] Soon after, the JTWC issued a Tropical Cyclone Formation Alert for the storm.[44] Afterwards, the JTWC officially upgraded Butchoy to a tropical depression, and designated it as 02W.[45] With a favorable environment with low vertical wind shear, moderate equatorial outflow and 30–31 °C sea surface temperatures,[45] Butchoy started to intensify in the South China Sea, becoming a tropical storm and receiving the name Nuri from the JMA later on the same day.[46] Then, PAGASA issued their final warning on Nuri as it exited the Philippine Area of Responsibility.[47] By the next day, Nuri intensified further and subsequently peaked in intensity, with the JMA analyzing the storm's peak winds of 75 kilometers per hour (47 mph).[48] Six hours later, the JTWC upgraded Nuri to a tropical storm.[49] However, later in the same day, the JTWC downgraded Nuri into a tropical depression, citing that the storm has drifted into high vertical wind shear.[50] The JMA followed suit, downgrading Nuri into a depression.[51] The JTWC issued their final warning on Nuri as the storm subsequently made landfall in Yanjiang, China.[52][53] The JMA followed suit six hours later, issuing their final warning on the system.[54]

The PAGASA issued Tropical Cyclone Signal No. 1 for western Mindanao, southern Luzon, and Visayas on June 11 as Butchoy neared the Philippines.[55] The combination of the system and prevailing southwesterly winds brought showers and thunderstorms across the Philippines.[56] Heavy rainfall in Albay led to the activation of disaster risk management officials and other emergency assets.[55] The rains from the tropical depression prompted PAGASA to declare the start of the rainy season in the Philippines on June 12, 2020, which was also during the country's Independence Day.[57][58] In Hong Kong, Nuri brought heavy rain. One person also drowned due to rough waters.[59]

Tropical depression (JMA)
Duration	July 11 – July 15
Peak intensity	<55 km/h (35 mph) (10-min); 1004 hPa (mbar)

After about one month of inactivity, on July 11, the JMA designated a low-pressure area near Luzon as a tropical depression.[60] The next day, the JTWC designated the depression as an invest and was given a low chance of developing, and later upgraded to a medium chance. On the following day, the PAGASA upgraded the low-pressure system to a tropical depression and named it Carina.[61]

Carina moved north-northwest over an environment favorable for further development, with low vertical wind shear, established equatorial outflow and 28–29 °C sea surface temperatures. By 12:00 UTC on July 14, Carina rapidly weakened into a low-pressure area, due to an unfavorable environment with strong wind shear.[62] PAGASA then issued their final advisory to Carina, and the remnants dissipated on July 15.[63][64]

As the low-pressure system was named Carina, PAGASA immediately hoisted Signal #1, the lowest of their storm warning signals, to Batanes, Babuyan Islands and the northeastern portion of Cagayan.[65] Heavy rainfall from Carina caused some damage on Ilocos Norte, Abra and Isabela.[66]

Typhoon (JMA)
Category 1 typhoon (SSHWS)
Duration	July 30 – August 5
Peak intensity	130 km/h (80 mph) (10-min); 975 hPa (mbar)

On July 31, JMA began monitoring a weak tropical depression that had developed in the Philippine Sea.[67] Later, PAGASA named Dindo to the storm.[68] By the next day, the Joint Typhoon Warning Center designated Dindo as 03W.[69] With favorable conditions of low vertical wind shear, strong equatorial outflow and 31 °C sea surface temperatures,[69] Dindo intensified into a tropical storm on midday of the same time, and the Japan Meteorological Agency named it as Hagupit.[70] Hagupit then began intensifying in the Philippine Sea, and by August 2, Hagupit was upgraded into a typhoon by the JTWC.[71] The JMA later upgraded Hagupit to a severe tropical storm late on August 2.[72] As Hagupit exited the Philippine Area of Responsibility (PAR), the PAGASA issued its final bulletin on the system.[73] Hagupit was then upgraded into typhoon status by the JMA on August 3,[74] and will later peak in intensity with a pressure of 975 hPa.[75] At around 19:30 UTC, Hagupit made landfall in Wenzhou, China, with winds of 85 mph and pressure of 975 mbar (hPa).[76] After its landfall, Hagupit gradually weakened over China, and by early August 4, the JTWC downgraded the typhoon into a tropical storm.[77] Around midday of the same day, JTWC downgraded Hagupit into a tropical depression and later issued their final advisories on the storm,[78] but the JMA still monitored Hagupit as a tropical storm.[79] The system later would undergo an extratropical transition, a process which got completed on August 6, and the JMA issued their final advisory on the extratropical Hagupit.[80]

In advance of Hagupit, Chinese officials ordered the evacuation of areas vulnerable to flooding.[81] Hagupit caused torrential rainfall over portions of China peaking at 13.11 inches (333 mm) in the Jingshan district of Wenzhou.[82] 15 people were reported dead across South Korea, 6 of them following a landslide in South Chungcheong Province, 11 people were reported missing, and 7 people were injured.[83][84]

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	July 31 – August 3
Peak intensity	75 km/h (45 mph) (10-min); 985 hPa (mbar)

On July 29, a tropical disturbance formed and was situated a couple hundred miles east of Manila, Philippines. Struggling to consolidate, the disturbance crossed Luzon with little to no organization and began organizing in the South China Sea. Environmental conditions became conducive for development, and the JMA declared that a tropical depression had formed in the early hours of July 31.[85] Then early on August 1, the depression intensified into Tropical Storm Sinlaku.[86] The storm failed to intensify much afterward, and during the following day, Sinlaku made landfall on northern Vietnam.[87] Shortly thereafter, both agencies issued final advisories on the storm.[88][89]

Sinlaku produced heavy rain across central and northern Vietnam, resulting in significant flooding. Two people died, one from a collapsed embankment and the other from flash flooding. Thousands of homes were inundated and crops suffered extensive damage.[90] Damage in the nation was about nearly 5.4 billion đồng (US$232,900).[91] Flash floods across Thailand also killed two people.[92]

The remnants of Sinlaku emerged in the Indian Ocean and intensified into a well marked low-pressure area between August 5–8, recreating a lot of torrential rain in portions of India.[93][94]

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	August 6 – August 11
Peak intensity	85 km/h (50 mph) (10-min); 994 hPa (mbar)

On August 6, the Philippine Atmospheric, Geophysical and Astronomical Services Administration started to monitor a low-pressure area that developed well east of Virac, Catanduanes.[95] On the next day, the Japan Meteorological Agency designated the low-pressure area as a weak tropical depression.[96] Despite a broad and elongated low-level circulation center, it gradually organized, prompting the Joint Typhoon Warning Center to issue a Tropical Cyclone Formation Alert on the depression.[97]

Early on next day, the PAGASA upgraded it to a depression, naming it Enteng.[98] Later around the same day, the JTWC designated the depression as 05W.[99] But, near end on the same day, the Japan Meteorological Agency upgraded the depression to a tropical storm, receiving the name Jangmi.[100] As such, Jangmi became the fifth named tropical storm of the 2020 typhoon season.[100] On August 9, Jangmi was upgraded into a tropical storm by the JTWC.[101] Despite being at favorable conditions of low vertical shear and 29–30 °C sea surface temperatures, an upper-level low present to the west of the system prohibited the broad Jangmi to organize further.[101] Around the same time, the PAGASA dropped advisories on Jangmi as it quickly exited the Philippine Area of Responsibility.[102] Moving northward at 23 knots,[101] the JMA reported that Jangmi already peaked at 45 knots (50 mph; 85 km/h).[103] Around 05:50 UTC on August 10, Jangmi made landfall on the southern tip of Geojedo, Gyeongsang Province in South Korea.[104] The JTWC issued their final advisories on Jangmi around 15:00 UTC of the same day,[105] and the JMA issued their final advisory early on the next day, August 11.[106]

Jangmi dropped drenching rainfall through the Ryukyu Islands of Japan, with a peak amount of 2.2 inches (55.8 mm) recorded on the island of Kumejima. In South Korea, Jangmi dropped up to 2.6 inches (66.04 mm) of precipitation, in an area already hard hit by flooding in the months previous to Jangmi.[107][108]

Tropical depression (JMA)
Tropical storm (SSHWS)
Duration	August 8 – August 13
Peak intensity	55 km/h (35 mph) (10-min); 1012 hPa (mbar)

A hybrid system formed on August 7, to the south of Japan. It slowly moved westwards, and on August 9, it transitioned into a tropical cyclone.

Due to the fact that the disturbance already had tropical-storm-force winds, it was immediately declared a tropical storm by the JTWC on August 9.[109] The next day, the tropical depression reached its peak intensity of 35 mph with an unusually high pressure of 1012 mbar. Soon afterwards 06W began to gradually weaken, and at 15:00 UTC on August 10, the JTWC downgraded 06W to a tropical depression.[110]

Tropical Depression 06W then ceased to be monitored by the JMA on August 12 due to collapses in the convective activity, dry upper-level air intake, and other factors and ending its official monitoring, yet the JTWC still continued to issue updates normally for 06W even though the system had little signs of activity.

After moving generally westward, the system began to move to the southwest and, at 20:00 UTC (4:00 am, August 13 PST), it entered the Philippine's area of responsibility and was given the name Gener by PAGASA.[111][112] At 03:00 UTC on August 13, the JTWC issued its final warning on 06W, ending the monitoring of agency and global agencies.

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

Another area of persistent convection formed within the proximity of the trough that would also spawn Tropical Storm Jangmi On August 7, west of Luzon. As Jangmi became the dominant system in the area, this low-pressure area remained disorganized. However, on the next day, as Jangmi moved away from the area, the system began to organize, and on August 9, the JTWC upgraded the storm to a Tropical Depression.[113] Soon after, at 8:00 pm. PST, the PAGASA followed and upgraded the storm and gave it the name Ferdie.[114] By the next day, the JTWC upgraded Ferdie into a tropical storm. The PAGASA then issued its last warning as Ferdie exited the Philippine Area of Responsibility. Then soon, the JMA followed suit and upgraded Ferdie to a tropical storm, giving it the international name Mekkhala. At 07:30 CST on August 11 (23:30 UTC on August 10), Mekkhala made landfall at Zhangpu County in Fujian, China shortly after peak intensity.[115]

Mekkhala forced a Signal No. 1 warning to be placed for the Ilocos region in the Philippines. Mekkhala brought monsoonal conditions to portions of Luzon, shortly after its formation.[116] Although remain well offshore Taiwan, the storm still brought heavy rainfall to the island.[117]

In China, local officials suspended ferry services and told ships to return to port, in preparation for Mekkhala.[118] The China Meteorological Administration issued a Level III emergency response, while flood control workers were sent to areas which were hit by Mekkhala.[119] Mekkhala dropped torrential rainfall over China with amounts of up to 7.874 inches (200 mm) reported in some areas. Train services were halted and flights were canceled at local airports as Mekkhala moved onshore.[120] In Zhangzhou, Fujian, damage from the storm reached 1.1 billion yuan (US$159 million).[121]

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

A new tropical depression formed from the Intertropical Convergence Zone east of Luzon on August 16. At 15:00 UTC, the PAGASA named the system Helen and began issuing severe weather bulletins for the tropical depression, but dropped the alerts as Helen left the Philippine area of responsibility after 4 hours.[122][123] By the next day, Helen intensified into a tropical storm, being given the name Higos by the JMA. Later in the day, the Joint Typhoon Warning Center also upgraded Higos into a tropical storm. JMA eventually upgraded the system to a severe tropical storm by evening that day. The Hong Kong Observatory and Macau Meteorological and Geophysical Bureau upgraded Higos into a marginal typhoon prior to landfall, with sustained hurricane-force winds in Macau indicating such an intensity. Higos made landfall over Zhuhai, Guangdong at peak intensity at around 06:00 CST on August 19 (22:00 UTC on August 18).[124]

In preparation for Higos, the Hong Kong Observatory raised the number 9 tropical cyclone warning signal in Hong Kong to warn of the possibility of hurricane-force winds. Winds generally reached gale to storm force over the southern part of Hong Kong under the influence of Higos' small circulation.[125] The Macao Meteorological and Geophysical Bureau issued the number 10 signal, the highest signal, at 05:00 am local time.[126] Over 65,000 people evacuated and schools were closed across these areas. Although heavily populated areas of China were directly hit by Higos, damage was mostly limited to downed trees and power outages.[127] Two campers who were unaware of the approaching storm had to be rescued from Tap Mun Island after arriving on August 14.[128] The storm also left 7 deaths and 45 billion đồng (US$2 million) in damages in Vietnam.[129]

Very strong typhoon (JMA)
Category 3 typhoon (SSHWS)
Duration	August 20 – August 27
Peak intensity	155 km/h (100 mph) (10-min); 950 hPa (mbar)

On August 19, the JTWC began monitoring a broad area of low pressure situated a couple hundred miles northeast of the Philippine archipelago. By the next day, the system rapidly organized, and the JTWC subsequently issued a Tropical Cyclone Formation Alert (TCFA). On August 21, the area of low pressure became Tropical Depression 09W.[130] At 15:00 UTC, the PAGASA named the system Igme and issued a severe weather bulletin for it.[131] By the next day, Igme intensified into a tropical storm, according to the JMA and was given the name Bavi,[132] subsequently prompting the JTWC to follow suit and upgrade 09W from a tropical depression to a tropical storm. Favorable conditions allowed Bavi to rapidly intensify, and by 12:00 UTC on August 22, the system became a severe tropical storm. As the system left the Philippine Area of Responsibility, the PAGASA stopped issuing weather bulletins for the severe tropical storm.[133] Bavi's period of rapid intensification was brief, and it began a slow intensification phase on August 23.

On August 24, Bavi slowly intensified, and it was later upgraded by the JMA into a typhoon. Later on that day, it became a Category 2-equivalent typhoon. By the next day, Bavi intensified even more to become a Category 3-equivalent typhoon. As Bavi moved closer to the Korean peninsula, one person died in Jeju island on August 25.[134] At around 00:30 UTC on August 27, Bavi made landfall over North Pyongan Province, North Korea.[135] After that, Typhoon Bavi transitioned into an extratropical storm in Manchuria, China.

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

A low-pressure area east of the Philippines consolidated into a tropical depression on August 27, and simultaneously, a Tropical Cyclone Formation Alert was issued for the system.[136][137] Early on August 28, PAGASA upgraded it to a tropical depression with the local name Julian,[138] shortly before the JMA upgraded it to a tropical storm and assigned the international name Maysak.[139] Subsequently, the JTWC upgraded Maysak to a tropical storm too,[140] and then the JMA upgraded it to a severe tropical storm despite its elongated low-level circulation center.[141][142] At 19:00 UTC August 29, the system was upgraded to a typhoon by the JMA and two hours later, PAGASA followed and also upgraded the system to typhoon status.[143] Later on that day, it became a Category 2-equivalent typhoon. By the next day, Maysak intensified even more to become a Category 3-equivalent typhoon. Then later on afternoon, it was upgraded to a Category 4-equivalent typhoon. Soon, Maysak began to weaken bit-by-bit as it passed the East China Sea, 1-minute winds slowing back down to Category 3-equivalent speeds.[144]

Typhoon Maysak then made landfall near Busan, South Korea at 02:20 KST on September 3 (17:20 UTC on September 2), with 10-minute maximum sustained winds at 155 kilometers per hour (96 mph) and the central pressure at 950 hPa (28.05 inHg).[145] equivalent to a Category 2 typhoon. After that, it crossed the Sea of Japan and hitting North Korea into Jilin, Manchuria in China. Soon after, Typhoon Maysak degenerated into an extratropical low in northeast China.[146]

On September 2, the Panamanian-registered animal transport ship Gulf Livestock 1 transmitted a Mayday and launched lifeboats, at least one of which was found. The ship was west of Japan's Amami Ōshima Island. The Japan Coast Guard has said that the freighter was carrying a crew including 39 Filipinos, 2 Australians, and 2 New Zealanders when it disappeared. The cargo was 5,867 cattle, loaded in Napier, New Zealand, and bound for the port of Jingtang in Tangshan, China.[147] Two fatalities occurred in South Korea where also 120,000 households lost power.[148] In North Korea, Maysak dropped 15.157 inches (385 mm) of precipitation in Wonsan.[149]

Violent typhoon (JMA)
Category 4 super typhoon (SSHWS)
Duration	August 30 – September 7
Peak intensity	195 km/h (120 mph) (10-min); 910 hPa (mbar)

On August 29, the JTWC began tracking a very disorganized tropical disturbance situated a couple hundred miles northeast of Guam, noting that no major models but the European Center for Medium-range Weather Forecasting's ECMWF model had forecasted for any significant development. By the next day, the disturbance had quickly organized, and the JTWC issued a Tropical Cyclone Formation Alert (TCFA) for the low-pressure area,[150] and by the next day, it intensified into Tropical Depression 11W.[151] Traversing generally southwestward, the depression quickly intensified into a tropical storm.[152] The JMA soon followed and upgraded the system into a tropical storm as well, and gave the storm the international name Haishen. Later that day, Haishen became a severe tropical storm as it headed southwest into the Philippine Sea. Intensification on September 3 was significant, with Typhoon Haishen acquiring a pinhole eye early in the day, but underwent a merger eyewall replacement cycle/MERC due to the eyewall being inertially unstable. This allowed the eyewall to be more robust and stable, and continual rapid intensification continued throughout the day.

Upon entering the Philippine Area of Responsibility (PAR), the Philippine Atmospheric, Geological and Atmospheric Services Administration (PAGASA) named the system Kristine.[153][154] Early on September 4, the JTWC assessed that Haishen became a Category 4-equivalent super typhoon – with 1-minute sustained wind speeds of 135 kt (155 mph; 250 km/h),[155] with a clear, symmetrical eye visible on satellite imagery.[156] On September 5, as Haishen's latitude increased, the ocean heat content in the area decreased,[157] which disrupted the system's core and caused its eye to appear ragged on satellite imagery, subsequently indicating weakening, and dropping below super typhoon status.[158] Later that day, the system left the PAR and PAGASA issued its last bulletin on the typhoon.[159]

As the system continued its northward track toward the Japanese archipelago, it continued to weaken and became a Category 3-equivalent typhoon, and not too long after it weakened to a Category 2-equivalent typhoon as it neared the Southern Ryukyu Islands of Japan. A mandatory evacuation order was issued for western Japan as millions of people evacuated accordingly.[160] Haishen made landfall in Ulsan, South Korea at around 09:00 KST (00:00 UTC) on September 7,[161] with 10-minute maximum sustained winds at 140 kilometers per hour (87 mph) and the central pressure at 955 hPa (28.20 inHg).

Haishen caused two fatalities in Japan, while four others went missing after a mudslide occurred in Miyazaki Prefecture.[162] Two more fatalities occurred in South Korea and widespread flooding occurred in neighboring North Korea.[163]

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

On September 10 at 00:00 UTC, the JMA began tracking a tropical depression.[164] At 15:00 UTC that day, the JTWC issued a Tropical Cyclone Formation Alert on the system.[165] On September 11 at 18:00 UTC, the JTWC upgraded the disturbance to a tropical depression, designating it as 12W; it was downgraded back to a tropical disturbance six hours later.[166] The JMA had stopped tracking the depression by September 13th.[167][168]

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	September 15 – September 18
Peak intensity	85 km/h (50 mph) (10-min); 992 hPa (mbar)

On September 14 at 12:00 UTC, the JMA began tracking a tropical depression.[169] On the morning of September 15, the JTWC issued a tropical cyclone formation alert for a tropical system forming in the Philippine Sea.[170] The JTWC later upgraded it to a tropical depression at 15:00 UTC as they issued their first warning on the system as Tropical Depression 13W.[171] Since the depression formed inside of the Philippine Area of Responsibility (PAR), the PAGASA immediately issued a severe weather bulletin on the storm and named the system Leon.[172] At 21:00 on September 16, the storm left the PAR and PAGASA issued its final warning on the system.[173] At 03:00 UTC September 18, Noul made landfall between Quảng Trị and Thừa Thiên-Huế provinces. At 09:00 UTC, the JTWC issued its final warning on the system.[174] After being downgraded to a low-pressure area (LPA), Noul followed a westward path and emerged in the Indian Ocean.

A few days before the storm hit Vietnam, the Vietnamese government closed three airports and evacuated more than one million people in the affected areas.[175][176][177] Noul damaged homes and knocked down trees and power lines in Hue, Vietnam.[178] Heavy precipitation amounts peaking at 310 mm (12.20 inches) fell in Da Nang.[179] The storm caused 6 deaths and 705 billion đồng (US$30.4 million) in damage.[180][181][182]

The remnants of Noul left the western Pacific after the landfall and reached the waters of the northern Indian Ocean. The remnants created several areas of convection and caused heavy rains, landslides, floods, causing some damages in Bangladesh, northeast of India and Myanmar. No death was reported.

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	September 19 – September 24
Peak intensity	110 km/h (70 mph) (10-min); 975 hPa (mbar)

On September 20 at 06:00 UTC, as a tropical disturbance strengthened in the extreme northeast corner of the Philippine Area of Responsibility, PAGASA upgraded the system to a tropical depression, giving it the local name Marce.[183] At the time, the JTWC only recognized the system as an area of convection and only issued a medium level of warning for the system.[184] The JTWC upgraded the system to a tropical storm at 12:00 UTC.[185] On September 21 at 03:00 UTC, the system left the Philippine Area of Responsibility.[186] The system then intensified into a tropical storm south of Japan, and was given the international name Dolphin by the JMA.[187] After the storm transitioned into an extratropical cyclone, the JTWC issued its final warning on the system on September 24 at 03:00 UTC.[188]

Severe tropical storm (JMA)
Category 1 typhoon (SSHWS)
Duration	September 25 – September 30
Peak intensity	110 km/h (70 mph) (10-min); 980 hPa (mbar)

On September 25, The JTWC first noted the possibility of tropical cyclone formation from an area of convection northeast of the Northern Mariana Islands. Over the next few days, the system organized and on September 27, both the JMA and the JTWC upgraded the system to a tropical storm, with the JMA assigning the name Kujira. The storm drifted north-northwestwards before recurving to the northeast while intensifying into a Category 1-equivalent typhoon early on September 29.[189] Kujira weakened to a tropical storm 12 hours after it intensified into a typhoon due to very high wind shear and cool waters. At 21:00 UTC, the JTWC issued the last advisory for the system.[190]

Typhoon (JMA)
Category 1 typhoon (SSHWS)
Duration	October 4 – October 17
Peak intensity	130 km/h (80 mph) (10-min); 965 hPa (mbar)

On October 2, the JTWC began to monitor a large area of thunderstorms in the open Pacific Ocean.[191] The system gradually organized, and it was classified as a tropical depression on October 4.[192] On the next day, the JMA upgraded the storm to a tropical storm and named it Chan-hom.[193] On October 7, the system was upgraded by the JMA into a typhoon.[194] The JMA issued their final warning on the system on October 12 at 00:45 UTC.[195] The JTWC later followed, issuing their final warning on the system at 09:00 UTC.[196] The JMA, however, still tracked Chan-hom as a tropical depression until it was last noted on October 16.[197]

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	October 6 – October 12
Peak intensity	85 km/h (50 mph) (10-min); 994 hPa (mbar)

On October 9, the JTWC began tracking a tropical system east-southeast of Da Nang, Vietnam.[198] On October 10, the system was declared as a tropical depression by the JTWC and the JMA.[199][200] Later that day, the JMA upgraded the system into a tropical storm and named it Linfa.[201] The system continued westward, making landfall on October 11 at 03:00 UTC in Vietnam.[202] The JTWC issued their final warning on the system at 09:00 UTC that day.[203] The JMA later followed, issuing their final warning on the system at 18:00 UTC.[204]

Linfa brought historic amounts of rainfall to Central Vietnam, peaking at 90.16 inches (2,290 mm) in A Lưới (Huế),[205] 59.842 inches (1,520 mm) in Hướng Linh (Quảng Trị).[206] That made it the 12th wettest tropical cyclone in history.[207] At least 370,000 people in Vietnam lost power after the storm.[208] So far the storm and its flood have left 104 people dead and 38 remain missing in Vietnam and Cambodia.[209][210][211] In Cambodia, severe flooding affected 16 provinces including Phnom Penh, killed at least 21 people, damaged over 25,000 homes over and over 180,000 hectares of farmland.[212]

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	October 11 – October 14
Peak intensity	85 km/h (50 mph) (10-min); 990 hPa (mbar)

On October 11, the JMA began tracking a tropical depression off the west coast of Luzon.[213] The PAGASA declared the system as a tropical depression at 12:00 UTC, and since the storm formed inside of the Philippine Area of Responsibility (PAR) the agency named the system Nika.[214] On the same day at 21:00, the JTWC began issuing warnings on the system.[215] On October 12, the system was declared a tropical storm by the JMA, and was named Nangka.[216] At 09:00 UTC, the system left the PAR and the PAGASA issued its final bulletin on the system.[217] At 19:20 CST (11:20 UTC) on October 13, Nangka made landfall over Qionghai, Hainan.[218]

On October 13, the storm crossed the Gulf of Tonkin and made landfall in the Nam Định, Ninh Bình, and Thanh Hóa provinces in Northern Vietnam on October 14.[219] On the same day, both the JMA and JTWC issued their final warnings for the system.[220] The system dissipated on October 14, 2020.[221]

After the passage of Nangka over Hainan Island, 2 people died and 4 are missing as a result of a capsized boat.[222] In Northern Vietnam, the storm killed 2 people in Hòa Bình, another missing in Yên Bái.[223] Over 585 houses were destroyed, while 135,731 others across central Vietnam were flooded.[224]

Tropical depression (JMA)
Duration	October 13 – October 16
Peak intensity	<55 km/h (35 mph) (10-min); 1002 hPa (mbar)

A low-pressure area formed in the Philippine Sea, east of Leyte, on October 13. Soon, the PAGASA declared the newly formed system as a tropical depression and assigned it the name Ofel. The PAGASA immediately raised warning signals for the province of Sorsogon and for parts of the Samar province.[225] On the same day at 18:30 UTC, Ofel made landfall over Can-avid, Eastern Samar.[226] As the system entered the South China Sea in the early hours of October 15 UTC, the PAGASA lifted all tropical cyclone warning signals for Ofel.[227] On the same day at 20:00 UTC, Ofel left the Philippine Area of Responsibility (PAR) and PAGASA issued their final bulletin for the system.[228] While Ofel was inside the PAR, the Joint Typhoon Warning Center issued tropical cyclone formation alerts for the system,[229] however it was canceled as the system entered a less favorable environment on October 16.[230] The storm dissipated at 03:00 UTC on that day.[231]

Flooding was reported due to moderate to heavy rains. According to the Department of Agriculture Regional Office 5, total damages have topped to an estimated ₱9.1 million (US$187,000).[232]

Typhoon (JMA)
Category 1 typhoon (SSHWS)
Duration	October 18 – October 25
Peak intensity	120 km/h (75 mph) (10-min); 975 hPa (mbar)

On October 16 UTC, the JTWC began tracking an area of convection approximately 463 nautical miles (857 km) east-southeast of Palau.[233] On October 18 at 21:00 UTC, the PAGASA upgraded the system into a tropical depression, and named the system Pepito.[234] A few hours later, the JMA also recognized the system into a tropical depression,[235] and subsequently issued their first warning on the system.[236] As the system intensified as it approached Northern Luzon, the JMA upgraded the system into a tropical storm and named the system Saudel.[237] The PAGASA also declared the system as a tropical storm, and began issuing Signal #2 tropical cyclone warnings in preparation for its landfall.[238] Saudel made landfall over the San Ildefonso Peninsula in Casiguran, Aurora on October 20 at 13:00 UTC (21:00 PHT) and began crossing the Luzon Island, emerging over the South China Sea hours later.[239][240] As the storm left the Philippine Area of Responsibility, the developing severe tropical storm was upgraded into a typhoon by the JMA, the JTWC, and by the PAGASA in their final bulletin for the system.[241][242][243]

As of October 24, the NDRRMC reported total damages of about ₱105.8 million (US$2.18 million).[244]

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

On October 19, both the JMA and the JTWC began tracking a tropical depression, with the JTWC designating it as 20W.[166][245] 20W formed over marginally favorable conditions for development, before turning southwest after originally moving northeastward, encountering strong wind shear.[246][247] On October 21, the JTWC assessed that 20W was no longer a tropical depression, also assessing that it had transitioned into an extratropical cyclone the next day.[166] The JMA stopped tracking 20W on October 23.[248][249]

Very strong typhoon (JMA)
Category 3 typhoon (SSHWS)
Duration	October 22 – October 29
Peak intensity	165 km/h (105 mph) (10-min); 940 hPa (mbar)

On October 23, the JMA began tracking a tropical depression approximately 190 nautical miles (350 km) north of Palau.[250][251] On the same day, PAGASA followed suit as the system formed inside of the Philippine Area of Responsibility (PAR), east of Mindanao, and named the system Quinta.[252] On October 24, the JTWC also recognized the system as a tropical depression.[253] At 15:00 of the same day, the JTWC upgraded the system into a tropical storm, with the JMA and PAGASA doing the same a few hours apart from each other. Now a tropical storm, the system was named Molave by the JMA.[254][255][256] On October 25, PAGASA upgraded the system into a severe tropical storm as it tracked closer to the Bicol Region.[257] Later that day, the PAGASA then upgraded Molave into a typhoon as it headed for Albay and Camarines Sur, prompting the raising of Signal #3 tropical cyclone warnings for both and adjacent provinces.[258] Moments later, the JMA also upgraded the system to a typhoon and the JTWC followed a few hours later.[259][260] At 18:10 PHT (10:10 UTC), Molave made its first landfall on the San Miguel Island in Albay, with another in Malinao just 40 minutes later.[261] Molave made a total of 5 landfalls in the Luzon area before entering the South China Sea on October 26.[262][263] On October 27 at 00:00 UTC, Molave left the PAR, with PAGASA issuing their last bulletin for the system later at 15:00.[264][265] After that, Typhoon Molave intensified even more and peaked as a Category 3-equivalent typhoon in the South China Sea. After that, colder sea surface temperatures caused the storm to weaken a bit, and by the next day Molave made landfall in Vietnam as a weakening Category 2-equivalent storm.

As of November 9, 2020, the NDRRMC reported that 27 people were killed, 40 people were injured and four went missing after the typhoon.[266] Damage from infrastructure and agriculture counted to be ₱1.56 billion (US$32.2 million) and ₱2.66 billion (US$54.9 million) respectively, with a total damage of ₱4.22 billion (US$87.1 million) nationwide.[266] In Vietnam, Molave left 41 dead, 143 were injured and 42 people missing. Economic losses were estimated to be 12.92 trillion dong (US$558 million).

Violent typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	October 26 – November 6
Peak intensity	220 km/h (140 mph) (10-min); 905 hPa (mbar)

After Typhoon Molave devastated the Philippines, the JMA announced the formation of a new tropical depression in the Pacific Ocean, west of the Mariana Islands, on October 27.[267] By the next day, the JTWC had also followed and upgraded the system into a tropical depression.[268] As the system continued tracking westward under favorable conditions in the Pacific Ocean, the JMA and JTWC upgraded the system into a tropical storm, with the JMA assigning the name Goni to the intensifying storm.[269][270][271] Due to the warm waters surrounding the storm, the system underwent rapid intensification and became a typhoon.[272][273] On October 29, at 9:30 UTC, Goni entered the Philippine Area of Responsibility (PAR) and was named Rolly by the PAGASA.[274] By 18:00 UTC, Goni had intensified into a Category 4-equivalent typhoon, with 1-minute sustained winds at 120 knots (220 km/h; 140 mph), and eventually the first Category 5-equivalent typhoon of the season a few hours later.[275][276] Warm sea surface temperatures, low vertical wind shear and high ocean heat content continually supported Goni as it edged closer to the Philippines, and it maintained its intensity into the next day.[277] At 18:00 UTC October 31 (2:00 PST November 1), PAGASA upgraded Goni to a super typhoon on the agency's tropical cyclone intensity scale[278] at which time the JMA and PAGASA both reported 10-minute sustained winds of 220 kilometers per hour (140 mph)[279] and 225 km/h (140 mph), respectively, marking the second time Tropical Cyclone Wind Signal #5 was raised by PAGASA[280] since Typhoon Haima in 2016 and Typhoon Megi in 2010. Goni made its first two landfalls at peak intensity over Bato, Catanduanes (20:50 UTC)[280] and Tiwi, Albay (23:20 UTC).[281] After that, it weakened into a strong typhoon and made a third landfall in San Narciso, Quezon. Due to three landfalls and land interaction, Goni lost its immense strength and weakened into a minimal typhoon as it made a fourth landfall in San Juan, Batangas. Before exiting the PAR, Goni slightly intensified, but further development was hampered by unfavorable conditions.[282][283] The capital, Manila, experienced some tropical storm-force winds from Goni.

As of November 11, 2020, the NDRRMC has reported ₱12.9 billion (US$266 million) of infrastructure damages, along with ₱5 billion (US$103 million) of agricultural damage, with a combined total of ₱17.9 billion (US$369 million), and at least 25 deaths, 399 injured and 6 missing.[284] Goni is estimated to have caused at least ₱48.058 billion (US$1.04 billion) in damages in the Philippines.[285]

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	October 30 – November 7
Peak intensity	95 km/h (60 mph) (10-min); 992 hPa (mbar)

On October 28, the JTWC began tracking another tropical disturbance 95 nautical miles (110 mi) south-southwest of Chuuk in the Federated States of Micronesia.[286] This disturbance would eventually strengthen into a new tropical depression in the early hours of October 29.[287] Later that day, the JMA upgraded the system into a tropical storm.[288] On November 1, at 00:00 UTC, Atsani entered the PAGASA's Philippine Area of Responsibility (PAR), with the PAGASA naming the system Siony.[289][290] The storm tracked northwest through the Philippine Sea, passing through the Luzon Strait on November 4.[291] The system left the PAR on November 7 at 21:00 UTC.[292] Shortly afterwards, the system rapidly weakened and dissipated thereafter.

Atsani downed trees, caused landslides, and damaged street lights in parts of Taiwan. Rockfalls caused some roads to close in Taitung County. 3 minor injuries were reported within Taitung County in the townships of Haiduan and Jinfeng.[293] The storm brought heavy rains to Batanes and the Babuyan Islands in the Philippines,[291] causing ₱4.9 million (US$101 thousand) in agricultural damage.[294]

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	November 6 – November 10
Peak intensity	85 km/h (50 mph) (10-min); 992 hPa (mbar)

On November 7, the Japan Meteorological Agency (JMA) began tracking a tropical depression 460 nautical miles (850 km; 530 mi) east-southeast of Manila.[295][296][297] At 12:00 UTC on the same day, the PAGASA declared the system as a tropical depression and assigned it the name Tonyo as it formed directly over Burias Island.[298] The Joint Typhoon Warning Center recognized the system as a tropical depression at 15:00 UTC on November 8.[299] Etau caused rains over Calabarzon, Mimaropa, and the Bicol Region before exiting the Philippine Area of Responsibility on November 9 at 21:00 UTC.[300] It continued its way towards Vietnam, after crossing Philippines.

Etau killed two people in Quảng Nam and Bình Định and damaged 400 houses when it made landfall in central Vietnam on November 10.[301] The storm produced over 250 mm (10 in) of rain in the provinces of Bình Định, Khánh Hòa, and Phú Yên,[302] with peak at 858 mm in Lake Thủy Yên (Thừa Thiên Huế).[303] The storm also caused gusty winds which uprooted trees and ripped roofs of buildings, many of which were still recovering from the adverse impacts of Typhoon Molave and the weakened Tropical Storm Goni. In addition, power outages locally affected the city of Tuy Hòa.[304] Economic losses in Tuy An, Phú Yên were counted as 122 billion VND (US$5.26 million).[305]

Very strong typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	November 8 – November 16
Peak intensity	155 km/h (100 mph) (10-min); 955 hPa (mbar)

On November 8, the JMA began tracking a new tropical depression 132 nautical miles (245 km; 150 mi) north-northwest of Palau.[306][307] At 12:00 UTC on the same day, the PAGASA declared the system as a tropical depression inside of the Philippine Area of Responsibility and named it Ulysses.[308] The next day at 7:15 UTC, the system strengthened into a tropical storm, with the JMA giving it the name Vamco,[309] with the Joint Typhoon Warning Center later issuing their first warning on the system as a tropical depression. As the system tracked closer to southern Luzon, both the PAGASA and the JMA upgraded Vamco into a severe tropical storm.[310] Vamco was then upgraded into typhoon status by the JMA on November 11, followed by the JTWC and the PAGASA shortly after, as the PAGASA raised Signal #3 tropical cyclone wind signals in preparation for the storm.[311][312] At 14:30 UTC and 15:20 UTC, Vamco made its first two landfalls over the island towns of Patnanungan and Burdeos, respectively, both in Quezon Province.[313][314] Later at 17:40 UTC, Vamco made its third landfall over General Nakar, Quezon, in the Luzon landmass.[314] At 00:00 UTC, the system emerged over the western seaboard of Zambales and entered the South China Sea.[315] The system left the PAR at 01:30 UTC as the PAGASA redeclared the system as a typhoon.[316] Vamco rapidly re-strengthened in the South China Sea and peaked as a Category 4-equivalent typhoon briefly before weakening back into a Category 3-equivalent storm heading for Vietnam.[317] The typhoon then weakened before making another landfall as a Category 1-equivalent typhoon in Vietnam.[318]

As of January 13, 2021, the NDRRMC reported a total of 196 casualties (Including 101 validated deaths, 85 injuries and 10 missing) caused by the typhoon, along with ₱7.32 billion (US$151 million) worth of agriculture damages and ₱12.9 billion (US$267 million) worth of infrastructural damages. The Cagayan Valley experienced the highest total amount of damage. At least 5,184,824 individuals were affected by the typhoon's onslaught.[319] The Armed Forces of the Philippines and Philippine National Police reportedly rescued 265,339 and 104,850 individuals, respectively.[320][321] According to Aon, total economic losses caused by the typhoon were estimated to top ₱50 billion (US$1 billion).[285]

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

On December 17 at 21:00 UTC, the PAGASA began issuing bulletins for a system 140 nautical miles (260 km) east-southeast of Davao.[322][323] The PAGASA had already recognized the system as a tropical depression and named it Vicky, however at the time, the Japan Meteorological Agency (JMA) only recognized the system as a low-pressure area.[324] The next day, the JMA followed suit and recognized the system as a tropical depression.[325] At 14:00 PHT (6:00 UTC), the system made landfall in Baganga, Davao Oriental.[326] 9 hours later, it emerged off the coast of Misamis Oriental and entered the Bohol Sea, later entering the Sulu Sea on the next day at 5:00 PHT (23:00 UTC).[327] On December 19 at 23:00 PHT (15:00 UTC), Krovanh made its second landfall over central Palawan, emerging into the South China Sea shortly after.[328][329] As the storm traversed the South China Sea, the system had strengthed into a tropical storm according to the JMA as it emerged into a region of relatively favorable atmospheric conditions, thus given the name Krovanh.[330] On December 20 at 14:00 PHT (6:00 UTC), Krovanh left the Philippine Area of Responsibility, although storm signals were still raised for the Kalayaan Islands.[331] The PAGASA then upgraded Krovanh into a tropical storm, and issued a Signal No. 2 warning for the Kalayaan Islands.[332] The next day, December 21, Krovanh was downgraded into a tropical depression by both the JMA and by the PAGASA in their final advisories for the storm.[333][334] The JTWC then issued their final warning on Krovanh the next day shortly after most of its central convection had dissipated due to increasingly hostile wind shear.[335]

Large swaths of Visayas and Mindanao were placed under Signal No. 1 warnings due to Krovanh.[336] Floods and landslides were triggered in Cebu, Agusan del Sur, Davao de Oro, and in Leyte, where two senior citizens were killed in a landslide. In Lapu-Lapu City, 300 residents were forced to evacuate after 76 houses near the shore were swept into sea.[337] Around 6,702 individuals were affected by the storm in the Philippines, with 5,646 in evacuation centers. Damages have been estimated to total up to ₱213.2 million (US$4.48 million). At least eight people were killed by the effects of Krovanh.[338]

The precursor to the Vietnam tropical depression on October 5

Late on July 27, the JMA began to track a weak tropical depression in the open Western Pacific.[339] Later on the following day, the system was unofficially classified as a subtropical depression by the JTWC, having been given a low chance of transitioning to a tropical cyclone. In a marginal environment with cyclonic easterly flow, moderate to strong wind shear and 28–30 °C sea surface temperatures, the system was expected to recurve poleward and be absorbed by a larger extratropical low. The depression, however, dissipated on July 30.[340]

The JMA began monitoring on another tropical depression to the south of Japan on September 27.[341] The system moved in a general northeastward direction until it was last noted on 18:00 UTC on September 29.[342]

On October 7, the Vietnam Center for Hydro-Meteorological Forecasting (VNCHF) monitored a tropical depression that had made landfall in the Khánh Hòa province.[343] Enhanced by the seasonal northeast monsoon, the system caused many provinces nearby to experience heavy rainfall with average accumulations of 200–300 mm. In Sa Huỳnh (Quảng Ngãi), rainfalls peaked at 360 mm. By October 11, heavy floods killed 9 people.[344]

On December 5, a tropical depression formed to the south of Japan.[345] The depression was short-lived, however, as it dissipated the next day after being embedded into a frontal zone.[346]

On December 29, the JMA started to track a weak tropical depression to the east of Vietnam.[347]

During the season, 23 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 kilometers 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. During the season, the name Saudel was used for the first time after it replaced Soudelor, which was retired following the 2015 season.

After the season, the Typhoon Committee announced that the names Vongfong, Linfa, Molave, Goni, and Vamco would be 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. In 2022, they were replaced by Penha, Peilou, Narra, Gaenari and Bang-Lang respectively.[350][351] With five names retired, this season was tied with the 2006 and 2019 seasons for the highest number of retired storm names after a single typhoon season, a record it jointly held until it was surpassed by the 2022 season which had six retired names.

During the season PAGASA used its own naming scheme for the 22 tropical cyclones, that either developed within or moved into their self-defined area of responsibility.[352] The names were taken from a list of names, that had been last used during 2016 and are scheduled to be used again during 2024.[352] The names Kristine, Leon and Nika were used for the first time after the names Karen, Lawin and Nina. Aside from those names, Pepito and Vicky were also used for the first time this year. The name Pepito replaced Pablo after 2012, while the name Vicky replaced Violeta after 2004 but not used in previous seasons.

After the season, PAGASA announced that the names Ambo, Quinta, Rolly and Ulysses will be removed from its rotating naming lists due to the number of deaths and amount of damage they caused, and they will not be used again. On January 21, 2021, they will be replaced with Aghon, Querubin, Romina and Upang for the 2024 season.[353][354][355][356]