Loading AI tools
From Wikipedia, the free encyclopedia
The 2020 Pacific typhoon season was the first of an series of four below average Pacific typhoon seasons, and became the first with below-average tropical cyclone activity since 2014, with 23 named storms, 10 of which became typhoons and only 2 became super typhoons. This low activity was a consequence of La Niña that persisted from the summer of the year. It had the sixth-latest start in the basin on record, slightly behind 1973, and was the first to start that late since 2016. The first half of the season was unusually inactive, with only four systems, two named storms and one typhoon at the end of July. Additionally, the JTWC recorded no tropical cyclone development in the month of July, the first such occurrence since reliable records began. Despite that, this season featured Super Typhoon Goni, which made the strongest landfall worldwide in terms of 1-minute wind speed. The season's first named tropical cyclone, Vongfong, developed on May 8, while the season's last named tropical cyclone, Krovanh, dissipated on December 24. However, the season's last system was an unnamed tropical depression which dissipated on December 29.
 | This article may need to be rewritten to comply with Wikipedia's quality standards. (July 2020) |
| 2020 Pacific typhoon season | |
|---|---|
Season summary map | |
| Seasonal boundaries | |
| First system formed | May 8, 2020 |
| Last system dissipated | December 29, 2020 |
| Strongest storm | |
| Name | Goni |
| • Maximum winds | 220 km/h (140 mph) (10-minute sustained) |
| • Lowest pressure | 905 hPa (mbar) |
| Seasonal statistics | |
| Total depressions | 32 |
| Total storms | 23 |
| Typhoons | 10 |
| Super typhoons | 2 (unofficial)[nb 1] |
| Total fatalities | 472 total |
| Total damage | $5.35 billion (2020 USD) |
| Related articles | |
The scope of this article is limited to the Pacific Ocean to the north of the equator between 100°E and 180th meridian. Within the northwestern Pacific Ocean, there are two separate agencies that assign names to tropical cyclones which can often result in a cyclone having two names. The Japan Meteorological Agency (JMA) will name a tropical cyclone should it be judged to have 10-minute sustained wind speeds of at least 65 kilometers per hour (40 mph) anywhere in the basin, whilst the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) assigns 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–25°N regardless of whether or not a tropical cyclone has already been given a name by the JMA. Tropical depressions that are monitored by the United States' Joint Typhoon Warning Center (JTWC) are given a number with a "W" suffix.
| TSR forecasts Date | Tropical storms | Total Typhoons | Intense TCs | ACE | Ref. |
|---|---|---|---|---|---|
| Average (1965–2019) | 26 | 16 | 9 | 294 | [1] |
| May 21, 2020 | 26 | 15 | 8 | 258 | [1] |
| July 9, 2020 | 26 | 14 | 7 | 216 | [2] |
| August 6, 2020 | 21 | 13 | 5 | 157 | [3] |
| Other forecasts Date | Forecast Center | Period | Systems | Ref. | |
| January 22, 2020 | PAGASA | January–March | 0–4 tropical cyclones | [4] | |
| January 22, 2020 | PAGASA | April–June | 3–6 tropical cyclones | [4] | |
| June 24, 2020 | PAGASA | July–September | 6–12 tropical cyclones | [5] | |
| June 24, 2020 | PAGASA | October–December | 4–8 tropical cyclones | [5] | |
| 2020 season | Forecast Center | Tropical cyclones | Tropical storms | Typhoons | Ref. |
| Actual activity: | JMA | 32 | 23 | 10 | |
| Actual activity: | JTWC | 26 | 23 | 12 | |
| Actual activity: | PAGASA | 22 | 15 | 7 | |
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 include the Tropical Storm Risk (TSR) Consortium of University College London, PAGASA and Taiwan's Central Weather Bureau. The first forecast for the year was released by PAGASA on January 22 predicting the first half of 2020, within its monthly seasonal climate outlook.[4] The PAGASA predicts that only 0–4 tropical cyclones are expected to form or enter the Philippine Area of Responsibility between January and March, while 3–6 tropical cyclones are expected to form between April and June. This was due to the fact that the El Niño–Southern Oscillation was seeing neutral conditions across the Pacific, and could persist until midyear.[4] On May 21, the TSR issued their extended-range forecast for 2020, forecasting tropical activity below the average normal, with 26 tropical storms, 15 typhoons and 8 intense typhoons.[1] These numbers were supported by the current values from the Indian Ocean Dipole, the Accumulated Cyclone Energy index and the sea-surface temperatures in the Niño 3.75 region, leading to a stronger than normal trade windspeed throughout much of the Western Pacific.[1]
On June 24, the PAGASA issued a climate forecast, predicting the number of tropical cyclones for the second half of the season. They predicted that 6–12 tropical cyclones are expected to form between the months of July and September, while 4–8 tropical cyclones are expected to form between the months of October and December.[5] On July 9, TSR issued their forecast for the season, predicting a well-below average season with 26 named storms, 14 typhoons and only 7 intense typhoons.[2] On August 6, TSR issued their third and final forecast for the season, lowering their numbers to 21 named storms, 13 typhoons and 5 intense typhoons.[3] They mentioned that the 2020 season is expected to be one of the "least active typhoon seasons on record", with a predicted ACE index barely half of the normal and a 96% probability of being a below-average season.[3]
The first few months of 2020 were inactive, with no tropical systems developing until May. On May 8, the season saw its first tropical system with the development of Tropical Depression 01W (Ambo), making it the sixth-latest starting season on record, as well as the latest since 2016. 2 days later, the system strengthened to the first officially named tropical storm of the season, Vongfong. Tropical Storm Vongfong then rapidly intensified into a significant typhoon and struck the central part of the Philippines on May 14, first making its landfall in San Policarpo, Eastern Samar, crossing 4 more islands and then hitting mainland Luzon.
After Vongfong, another month of inactivity ensued, and on June 10, a new tropical depression formed off the coast of Samar, Philippines, and was named Butchoy by the PAGASA a day later. Butchoy made landfall in the Philippines as the JTWC issued a TCFA for it. Once it exited Philippine landmass, Butchoy was upgraded into a tropical depression by the JTWC and all warnings issued by PAGASA were lifted, and Butchoy further intensified into a tropical storm in the South China Sea and was named Nuri by the Japan Meteorological Agency. After Nuri dissipated over mainland China, the basin became quiet again for more than a month with only Tropical Depression Carina forming east of Luzon; this led to the first time that no tropical storms developed within the month of July since reliable records began. The activity in the West Pacific increased somewhat with the formation of Tropical Storm Sinlaku, and the formation and intensification of Hagupit for a typhoon, ending a fast of more than 2 months without any significant typhoon. Hagupit affected China as a mid-Category 1-equivalent storm and caused US$441 million in damage. The storm then transitioned to an Extratropical cyclone and affected North Korea and Russia. A few days later, a new tropical depression formed, and then intensified into Tropical Storm Jangmi. Just southwest of Jangmi, a disorganized low-pressure area formed and would soon become Severe Tropical Storm Mekkhala, reaching China. A few days later, a new tropical depression formed in the South China Sea, and the PAGASA named the system as Helen. Shortly after, Helen intensified into a Severe Tropical Storm Higos, the 7th named storm on the 2020 typhoon season. Higos then went on to hit China. Soon after Higos dissipated, a new system formed in the east of the Philippines, and was named Igme. Igme then went on to become Tropical Storm Bavi and rapidly intensify in the coastal waters of Taiwan. In late August, Typhoon Maysak formed along with Typhoon Haishen, with both systems reaching Korean Peninsula and Japan, respectively.
September started with Maysak weakening on its way to Korea, while a new Haishen threatened the same areas that Maysak and previously Bavi affected. Typhoon Maysak made landfalls in South Korea and North Korea, while Typhoon Haishen intensified into the first super typhoon of the season. In mid-September, Tropical Storm Noul formed in the South China Sea, made landfall in Vietnam, and dissipated soon after. Later in the month, Tropical Storm Dolphin formed off the east coast of Japan and dissipated after a short life. Near the end of the month, Kujira formed and intensified into a severe tropical storm, before weakening and later becoming extratropical.
October was an extremely active month. The season started out with Typhoon Chan-hom, which lasted for 14 days before dissipating. On October 9, Tropical Storm Linfa formed, becoming the first of a train of tropical systems to affect Vietnam. Linfa killed more than 100 people and caused severe flooding in Vietnam and Cambodia. Nangka formed a few days after Linfa, though impacts were much less. A tropical depression, dubbed Ofel by the PAGASA went through the Philippines and then hit Vietnam, affecting the already flooded areas from Linfa.. After a short lull in systems, Typhoon Saudel formed on October 18, causing flooding in the Philippines. Afterwards, two very powerful typhoons formed after Saudel: Molave and Goni. The former killed 41 people throughout The Philippines, Vietnam, and Malaysia, while the latter became a Category 5-equivalent super typhoon.[nb 1] After Goni, Atsani formed and lashed Northern Luzon and Southern Taiwan as a tropical storm. As Atsani dissipated, another depression formed and affected Visayas as a depression, receiving the name Tonyo. The next day, it was upgraded to a tropical storm, earning the name Etau. Etau lasted from November 7 until November 11. On November 8, a depression formed in the Philippine Area of Responsibility and was given the name Ulysses. The next day, it was upgraded to a tropical storm, giving the name Vamco. Vamco strengthened into a Category 2-equivalent typhoon as it brushed the Luzon landmass. It quickly exited the Philippine Area of Responsibility the next day as the PAGASA stated that it restrengthened as a typhoon. It rapidly strengthened and reached its peak intensity as a Category 4-equivalent typhoon. It weakened until it dissipated north of Laos. At last in the month of December, three systems formed with one named as Krovanh which formed at the South China Sea. Then the season concluded on December 29 with a weak depression close to the coast of Vietnam.
After 4 months of lull activity, 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] On May 10, PAGASA later followed suit and named the depression Ambo.[9][10]
The system began to slowly drift westwards throughout the following days,[11] and on the next day, the JTWC upgraded Ambo to a tropical depression, designating it as 01W.[12] The JMA upgraded 01W to a tropical storm and assigned it the first name of the year, Vongfong.[13] Shortly after, the JTWC followed and upgraded the system to tropical storm intensity.[14] A well-defined eye soon emerged on microwave satellite imagery as the storm's structure became further organized [15] The eye became increasingly pronounced and contracted to less than 10 km (6.2 mi) in diameter as the storm's evolution became suggestive of rapid intensification.[16] The JTWC assessed 1-minute sustained winds of 195 km/h (121 mph) at 21:00 UTC on May 13 shortly before the onset of an eyewall replacement cycle;[17] Vongfong made landfall with this intensity over San Policarpo, Eastern Samar, at 04:15 UTC on May 14.[18] Vongfong made six additional landfalls as it traversed the remainder of the Visayas into Luzon: Dalupiri Island; Capul Island; Ticao Island; Burias Island; San Andres, Quezon; and Real, Quezon.[19] The prolonged interaction with land caused Vongfong to weaken, though the storm maintained a compact circulation amid otherwise favorable atmospheric conditions.[20] On May 15, Vongfong downgraded back into a tropical storm and later tropical depression on the following day before dissipated over Bashi Channel on May 17.[21]
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.[22] During the next day, the PAGASA began tracking the system, giving the local name Butchoy.[23][24] 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.[25] Soon after, the JTWC issued a Tropical Cyclone Formation Alert for the storm.[26] Afterwards, the JTWC officially upgraded Butchoy to a tropical depression, and designated it as 02W.[27] With a favorable environment with low vertical wind shear, moderate equatorial outflow and 30–31 °C sea surface temperatures,[27] 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.[28] Then, PAGASA issued their final warning on Nuri as it exited the Philippine Area of Responsibility.[29] 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).[30] Six hours later, the JTWC upgraded Nuri to a tropical storm.[31] 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.[32] The JMA followed suit, downgrading Nuri into a depression.[33] The JTWC issued their final warning on Nuri as the storm subsequently made landfall in Yanjiang, China.[34][35] The JMA followed suit six hours later, issuing their final warning on the system.[36]
The PAGASA issued Tropical Cyclone Signal No. 1 for western Mindanao, southern Luzon, and Visayas on June 11 as Butchoy neared the Philippines.[37] The combination of the system and prevailing southwesterly winds brought showers and thunderstorms across the Philippines.[38] Heavy rainfall in Albay led to the activation of disaster risk management officials and other emergency assets.[37] 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.[39][40] In Hong Kong, Nuri brought heavy rain. One person also drowned due to rough waters.[41]
After about one month of inactivity, on July 11, the JMA designated a low-pressure area near Luzon as a tropical depression.[42] 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.[citation needed] On the following day, the PAGASA upgraded the low-pressure system to a tropical depression and named it Carina.[43]
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.[citation needed] By 12:00 UTC on July 14, Carina rapidly weakened into a low-pressure area, due to an unfavorable environment with strong wind shear.[44] PAGASA then issued their final advisory to Carina, and the remnants dissipated on July 15.[45][46]
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.[47] Heavy rainfall from Carina caused some damage on Ilocos Norte, Abra and Isabela.[48]
On July 31, JMA began monitoring a weak tropical depression that had developed in the Philippine Sea.[49] Later, PAGASA named Dindo to the storm.[50] By the next day, the Joint Typhoon Warning Center designated Dindo as Tropical Depression 03W.[51] With favorable conditions of low vertical wind shear, strong equatorial outflow and 31 °C sea surface temperatures,[51] Dindo intensified into a tropical storm on midday of the same time, and the Japan Meteorological Agency named it as Hagupit.[52] Hagupit then began intensifying in the Philippine Sea, and by August 2, Hagupit was upgraded into a typhoon by the JTWC.[53] The JMA later upgraded Hagupit to a severe tropical storm late on August 2.[54] As Hagupit exited the Philippine Area of Responsibility (PAR), the PAGASA issued its final bulletin on the system.[55] Hagupit was then upgraded into typhoon status by the JMA on August 3,[56] and will later peak in intensity with a pressure of 975 hPa.[57] At around 19:30 UTC, Hagupit made landfall in Wenzhou, China, with winds of 85 mph and pressure of 975 mbar (hPa).[58] After its landfall, Hagupit gradually weakened over China, and by early August 4, the JTWC downgraded the typhoon into a tropical storm.[59] Around midday of the same day, JTWC downgraded Hagupit into a tropical depression and later issued their final advisories on the storm,[60] but the JMA still monitored Hagupit as a tropical storm.[61] 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.[62]
In advance of Hagupit, Chinese officials ordered the evacuation of areas vulnerable to flooding.[63] Hagupit caused torrential rainfall over portions of China peaking at 13.11 inches (333 mm) in the Jingshan district of Wenzhou.[64] 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.[65][66]
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.[citation needed] Environmental conditions became conducive for development, and the JMA declared that a tropical depression had formed in the early hours of July 31.[67] Then early on August 1, the depression intensified into Tropical Storm Sinlaku.[68] The storm failed to intensify much afterward, and during the following day, Sinlaku made landfall on northern Vietnam.[69] Shortly thereafter, both agencies issued final advisories on the storm.[70][71]
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.[72] Damage in the nation was about nearly 5.4 billion đồng (US$232,900).[73] Flash floods across Thailand also killed two people.[74]
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.[75][76]
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.[77] On the next day, the Japan Meteorological Agency designated the low-pressure area as a weak tropical depression.[78] 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.[79]
Early on next day, the PAGASA upgraded it to a depression, naming it Enteng.[80] Later around the same day, the JTWC designated the depression as 05W.[81] But, near end on the same day, the Japan Meteorological Agency upgraded the depression to a tropical storm, receiving the name Jangmi.[82] As such, Jangmi became the fifth named tropical storm of the 2020 typhoon season.[82] On August 9, Jangmi was upgraded into a tropical storm by the JTWC.[83] 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.[83] Around the same time, the PAGASA dropped advisories on Jangmi as it quickly exited the Philippine Area of Responsibility.[84] Moving northward at 23 knots,[83] the JMA reported that Jangmi already peaked at 45 knots (50 mph; 85 km/h).[85] Around 05:50 UTC on August 10, Jangmi made landfall on the southern tip of Geojedo, Gyeongsang Province in South Korea.[86] The JTWC issued their final advisories on Jangmi around 15:00 UTC of the same day,[87] and the JMA issued their final advisory early on the next day, August 11.[88]
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.[89][90]
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.[citation needed]
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.[91] 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.[92]
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.[citation needed]
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.[93][94] At 03:00 UTC on August 13, the JTWC issued its final warning on 06W, ending the monitoring of agency and global agencies.[citation needed]
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.[95] Soon after, at 8:00 pm. PST, the PAGASA followed and upgraded the storm and gave it the name Ferdie.[96] 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.[citation needed] 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.[97]
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.[98] Although remain well offshore Taiwan, the storm still brought heavy rainfall to the island.[99]
In China, local officials suspended ferry services and told ships to return to port, in preparation for Mekkhala.[100] The China Meteorological Administration issued a Level III emergency response, while flood control workers were sent to areas which were hit by Mekkhala.[101] 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.[102] In Zhangzhou, Fujian, damage from the storm reached 1.1 billion yuan (US$159 million).[103]
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.[104][105] 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.[citation needed] 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).[106]
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.[107] The Macao Meteorological and Geophysical Bureau issued the number 10 signal, the highest signal, at 05:00 am local time.[108] 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.[109] Two campers who were unaware of the approaching storm had to be rescued from Tap Mun Island after arriving on August 14.[110] The storm also left 7 deaths and 45 billion đồng (US$2 million) in damages in Vietnam.[111]
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.[112] At 15:00 UTC, the PAGASA named the system Igme and issued a severe weather bulletin for it.[113] By the next day, Igme intensified into a tropical storm, according to the JMA and was given the name Bavi,[114] 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.[115] 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.[116] At around 00:30 UTC on August 27, Bavi made landfall over North Pyongan Province, North Korea.[117] After that, Typhoon Bavi transitioned into an extratropical storm in Manchuria, China.
An area of low pressure was formed in the Northern Mariana Islands.[118] The disturbance then entered PAR on August 27, and a Tropical Cyclone Formation Alert was issued for the system.[119][120] Early on August 28, PAGASA upgraded it to a tropical depression, receiving the local name Julian,[121] JTWC later assigned the disturbance as Tropical Depression 10W, shortly before the JMA upgraded it to a tropical storm and assigned the international name Maysak.[122] The JTWC later followed suit in upgrading into a tropical storm.[123] A few hours later, Maysak later became a severe tropical storm despite its elongated low-level circulation center.[124] The presence of low wind shear and warm sea temperatures allows Maysak for any rapid intensifications. On August 31, it became a Category 4-equivalent typhoon. Maysak held this intensity as it began to move into a less conducive environment for storm development within the East China Sea.[125] Soon, Maysak began to weaken steadily as it passed the East China Sea, slowing back down to Category 3-equivalent winds.[126]
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).[127] equivalent to a Category 2 typhoon. After that, it crossed the Sea of Japan and hitting Hwadae County in North Korea into Jilin, Manchuria in China. Soon after, Typhoon Maysak degenerated into an extratropical low in northeast China.[128]
While Typhoon Maysak is holding its peak intensity, JTWC announced another formation of a very disorganized tropical disturbance situated a couple hundred miles northeast of Guam. By the next day, the disturbance had quickly organized, and the JTWC issued a Tropical Cyclone Formation Alert (TCFA) for the low-pressure area.[129] On the following day, the disturbance later designated as Tropical Depression 11W.[130][failed verification] Traversing generally southwestward, the depression quickly intensified into a tropical storm, with JMA gaining the name Haishen.[131] Under very favorable conditions, Haishen is allowed to do any intensification, which resulted in upgrading into Category 3-typhoon.
PAGASA announced that Haishen entered Philippine Area of Responsibility (PAR), naming the system as Kristine.[132] 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),[133] with a clear, symmetrical eye visible on satellite imagery.[134] Haishen's Haishen's latitude increased, the ocean heat content in the area decreased, resulting of weakening below super typhoon status.[135] Later that day, the system left the PAR and PAGASA issued its last bulletin on the typhoon.[136] 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.[137] Haishen made landfall in Ulsan, South Korea at around 09:00 KST (00:00 UTC) on September 7.[138]
On September 10 at 00:00 UTC, the JMA began tracking a tropical depression.[139] At 15:00 UTC that day, the JTWC issued a Tropical Cyclone Formation Alert on the system.[140] 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.[141] The JMA had stopped tracking the depression by September 13.[142][143]
On September 14 at 12:00 UTC, the JMA began tracking a tropical depression.[144] On the morning of September 15, the JTWC issued a tropical cyclone formation alert for a tropical system forming in the Philippine Sea.[145] 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.[146] 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.[147] At 21:00 on September 16, the storm left the PAR and PAGASA issued its final warning on the system.[148] 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.[149] 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.[150][151][152] Noul damaged homes and knocked down trees and power lines in Hue, Vietnam.[153] Heavy precipitation amounts peaking at 310 mm (12.20 inches) fell in Da Nang.[154] The storm caused 6 deaths and 705 billion đồng (US$30.4 million) in damage.[155][156][157]
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.[158] 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.[159] The JTWC upgraded the system to a tropical storm at 12:00 UTC.[160] On September 21 at 03:00 UTC, the system left the Philippine Area of Responsibility.[161] The system then intensified into a tropical storm south of Japan, and was given the international name Dolphin by the JMA.[162] After the storm transitioned into an extratropical cyclone, the JTWC issued its final warning on the system on September 24 at 03:00 UTC.[163]
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.[citation needed] The storm drifted north-northwestwards before recurving to the northeast while intensifying into a Category 1-equivalent typhoon early on September 29.[164] 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.[165]
On October 2, the JTWC began to monitor a large area of thunderstorms in the open Pacific Ocean.[166] The system gradually organized, and it was classified as a tropical depression on October 4.[167] On the next day, the JMA upgraded the storm to a tropical storm and named it Chan-hom.[168] On October 7, the system was upgraded by the JMA into a typhoon.[169] The JMA issued their final warning on the system on October 12 at 00:45 UTC.[170] The JTWC later followed, issuing their final warning on the system at 09:00 UTC.[171] The JMA, however, still tracked Chan-hom as a tropical depression until it was last noted on October 16.[172]
On October 9, the JTWC began tracking a tropical system east-southeast of Da Nang, Vietnam.[173] On October 10, the system was declared as a tropical depression by the JTWC and the JMA.[174][175] Later that day, the JMA upgraded the system into a tropical storm and named it Linfa.[176] The system continued westward, making landfall on October 11 at 03:00 UTC in Vietnam.[177] The JTWC issued their final warning on the system at 09:00 UTC that day.[178] The JMA later followed, issuing their final warning on the system at 18:00 UTC.[179]
Linfa brought historic amounts of rainfall to Central Vietnam, peaking at 90.16 inches (2,290 mm) in A Lưới (Huế),[180] 59.842 inches (1,520 mm) in Hướng Linh (Quảng Trị).[181] That made it the 12th wettest tropical cyclone in history.[182] At least 370,000 people in Vietnam lost power after the storm.[183] So far the storm and its flood have left 104 people dead and 38 remain missing in Vietnam and Cambodia.[184][185][186] 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.[187]
On October 11, the JMA began tracking a tropical depression off the west coast of Luzon.[188] 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.[189] On the same day at 21:00, the JTWC began issuing warnings on the system.[190] On October 12, the system was declared a tropical storm by the JMA, and was named Nangka.[191] At 09:00 UTC, the system left the PAR and the PAGASA issued its final bulletin on the system.[192] At 19:20 CST (11:20 UTC) on October 13, Nangka made landfall over Qionghai, Hainan.[193]
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.[194] On the same day, both the JMA and JTWC issued their final warnings for the system.[195] The system dissipated on October 14, 2020.[196]
After the passage of Nangka over Hainan Island, 2 people died and 4 are missing as a result of a capsized boat.[197] In Northern Vietnam, the storm killed 2 people in Hòa Bình, another missing in Yên Bái.[198] Over 585 houses were destroyed, while 135,731 others across central Vietnam were flooded.[199]
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.[200] On the same day at 18:30 UTC, Ofel made landfall over Can-avid, Eastern Samar.[201] 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.[202] 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.[203] While Ofel was inside the PAR, the Joint Typhoon Warning Center issued tropical cyclone formation alerts for the system,[204] however it was canceled as the system entered a less favorable environment on October 16.[205] The storm dissipated at 03:00 UTC on that day.[206]
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).[207]
On October 16 UTC, the JTWC began tracking an area of convection approximately 463 nautical miles (857 km) east-southeast of Palau.[208] On October 18 at 21:00 UTC, the PAGASA upgraded the system into a tropical depression, and named the system Pepito.[209] A few hours later, the JMA also recognized the system into a tropical depression,[210] and subsequently issued their first warning on the system.[211] As the system intensified as it approached Northern Luzon, the JMA upgraded the system into a tropical storm and named the system Saudel.[212] The PAGASA also declared the system as a tropical storm, and began issuing Signal #2 tropical cyclone warnings in preparation for its landfall.[213] 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. Saudel made another landfall over Anda, Pangasinan before emerging over the South China Sea hours later.[214][215] 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.[216][217] As it emerged through the South China Sea, Saudel starts to gradually weakened, downgraded into a severe tropical storm status.[218] It moved westwards through the Gulf of Tonkin where increasingly unfavorable conditions made Saudel deteriorate rapidly on October 25. Saudel degenerated into a remnant low Quảng Bình Province in Vietnam.
As of October 24, the NDRRMC reported total damages of about ₱105.8 million (US$2.18 million).[219]
On October 19, both the JMA and the JTWC began tracking a tropical depression, with the JTWC designating it as 20W.[141][220] 20W formed over marginally favorable conditions for development, before turning southwest after originally moving northeastward, encountering strong wind shear.[221][222] 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.[141] The JMA stopped tracking 20W on October 23.[223][224]
On October 23, the JMA began tracking a tropical depression approximately 190 nautical miles (350 km) north of Palau.[225] 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.[226] JTWC followed suit and recognized as Tropical Depression 21W.[227] Now a tropical storm, the system was named Molave by the JMA.[228][229][230] As it nears over the Bicol Region, PAGASA later upgraded Molave into a severe tropical storm on October 25.[231] Before landfall, all agencies were later upgraded to typhoon status, which prompted the warning for the province to Signal #3 in response to the approach of the typhoon.[232] At 18:10 PHT (10:10 UTC), Molave made its first landfall in San Miguel Island in Albay, with another in Malinao just 40 minutes later.[233] Molave made 3 more landfalls in San Andres, Quezon, Torrijos, Marinduque and Pola, Oriental Mindoro before entering the South China Sea on October 26.[234][235] On October 27 at 00:00 UTC, Molave left the PAR, with PAGASA issuing their last bulletin for the system later at 15:00.[236] Molave continue to intensify more and peaked as a Category-3 typhoon. As the system continued westwards, the storm began to slowly weaken as it approached Vietnam. Molave made landfall on Quảng Ngãi province, Central Vietnam at 10:10 UTC+7 (03:10 UTC), October 28 with category 2 typhoon strength.[237] The storm rapidly weakened once inland, with the JTWC issuing their final warning on the system as the storm's convection became increasingly disorganized. The storm dissipated shortly afterward, over Myanmar.
As of November 9, 2020[update], the NDRRMC reported that 27 people were killed, 40 people were injured and four went missing after the typhoon.[238] 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.[238]
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.[239] By the next day, the JTWC had also followed and upgraded the system into a tropical depression.[240] As the system continues to track westward under very favorable conditions, it reached tropical storm strength, naming it as Goni by the JMA.[241] Rapid intensification was ensued and became a typhoon.[242][243] On October 29, at 9:30 UTC, Goni entered the Philippine Area of Responsibility (PAR) and was named Rolly by the PAGASA.[244] At the same day, Goni became the first Category-5 super typhoon with 10-minute winds of 220 kilometers per hour (140 mph) [245] and 225 km/h (140 mph), respectively, marking the second time Tropical Cyclone Wind Signal #5 was raised by PAGASA[246] since Typhoon Haima in 2016. Goni made its first two landfalls at peak intensity over Bato, Catanduanes (20:50 UTC)[246] and Tiwi, Albay (23:20 UTC).[247] 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.[248][249] The capital, Manila, experienced some tropical storm-force winds from Goni.
As of November 11, 2020[update], 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.[250] Goni is estimated to have caused at least ₱48.058 billion (US$1.04 billion) in damages in the Philippines.[251]
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.[252] This disturbance would eventually strengthen into a new tropical depression in the early hours of October 29.[253] Later that day, the JMA upgraded the system into a tropical storm.[254] On November 1, at 00:00 UTC, Atsani entered the PAGASA's Philippine Area of Responsibility (PAR), with the PAGASA naming the system Siony.[255][256] The storm tracked northwest through the Philippine Sea, passing through the Luzon Strait on November 4.[257] The system left the PAR on November 7 at 21:00 UTC.[258] 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.[259] The storm brought heavy rains to Batanes and the Babuyan Islands in the Philippines,[257] causing ₱4.9 million (US$101 thousand) in agricultural damage.[260]
On November 7, the Japan Meteorological Agency (JMA) began tracking a tropical depression 460 nautical miles (850 km; 530 mi) east-southeast of Manila.[261][262][263] 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.[264] The Joint Typhoon Warning Center recognized the system as a tropical depression at 15:00 UTC on November 8.[265] Etau caused rains over Calabarzon, Mimaropa, and the Bicol Region before exiting the Philippine Area of Responsibility on November 9 at 21:00 UTC.[266] 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.[267] 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,[268] with peak at 858 mm in Lake Thủy Yên (Thừa Thiên Huế).[269] 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.[270] Economic losses in Tuy An, Phú Yên were counted as 122 billion VND (US$5.26 million).[271]
On November 8, a tropical depression was formed around 132 nautical miles (245 km; 150 mi) north-northwest of Palau.[272][273] 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.[274] The next day at 7:15 UTC, the system strengthened into a tropical storm, with the JMA giving it the name Vamco,[275] with the Joint Typhoon Warning Center later issuing their first warning on the system designated as Tropical Depression 25W. As the system tracked closer to southern Luzon, Vamco was upgraded into a severe tropical storm.[276] Vamco was then upgraded into typhoon status by the JMA on November 11, followed by the JTWC and later PAGASA, as the PAGASA raised Signal #3 tropical cyclone wind signals in preparation for the storm.[277][278] 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.[279][280] Later at 17:40 UTC, Vamco made its third landfall over General Nakar, Quezon, in the Luzon landmass.[280] At 00:00 UTC, the system emerged over the western seaboard of Zambales and entered the South China Sea.[281] The system left the PAR at 01:30 UTC as the PAGASA redeclared the system as a typhoon.[282] 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.[283] The typhoon then weakened before making another landfall as a Category 1-equivalent typhoon in Vietnam.[284]
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.[285] According to Aon, total economic losses caused by the typhoon were estimated to top ₱50 billion (US$1 billion).[251]
On December 17 at 21:00 UTC, the PAGASA began issuing bulletins for a system 140 nautical miles (260 km) east-southeast of Davao.[286][287] 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.[288] The next day, the JMA followed suit and recognized the system as a tropical depression.[289] At 14:00 PHT (6:00 UTC), the system made landfall in Baganga, Davao Oriental.[290] 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).[291] 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.[292][293] 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.[294] 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.[295] The PAGASA then upgraded Krovanh into a tropical storm, and issued a Signal No. 2 warning for the Kalayaan Islands.[296] 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.[297][298] 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.[299]
Large swaths of Visayas and Mindanao were placed under Signal No. 1 warnings due to Krovanh.[300] 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.[301] 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.[302]
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.[312] 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).[313] PAGASA assigns 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.[312] The names of significant tropical cyclones are retired, by both PAGASA and the Typhoon Committee.[313] 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, 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.
| Vongfong | Nuri | Sinlaku | Hagupit | Jangmi | Mekkhala | Higos | Bavi | Maysak | Haishen | Noul | Dolphin |
| Kujira | Chan-hom | Linfa | Nangka | Saudel | Molave | Goni | Atsani | Etau | Vamco | Krovanh | |
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.[314][315] 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.
| Main list | ||||
|---|---|---|---|---|
| Ambo | Butchoy | Carina | Dindo | Enteng |
| Ferdie | Gener | Helen | Igme | Julian |
| Kristine | Leon | Marce | Nika | Ofel |
| Pepito | Quinta | Rolly | Siony | Tonyo |
| Ulysses | Vicky | Warren (unused) | Yoyong (unused) | Zosimo (unused) |
| Auxiliary list | ||||
| Alakdan (unused) | Baldo (unused) | Clara (unused) | Dencio (unused) | Estong (unused) |
| Felipe (unused) | Gomer (unused) | Heling (unused) | Ismael (unused) | Julio (unused) |
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.[316] This is the same list used during the 2016 season, except for the names Kristine, Leon and Nika, which replaced Karen, Lawin and Nina, respectively. All three names were used for the first time, as well as the names Pepito and Vicky (which replaced Pablo and Violeta in 2012 and 2004 respectively, but went unused 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 were replaced with Aghon, Querubin, Romina and Upang respectively. These new names first appeared in the 2024 season.[317][318][319][320]
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 2020. The tables also provide an overview of a system's intensity, duration, land areas affected and any deaths or damages associated with the system.
| Name | Dates | Peak intensity | Areas affected | Damage (USD) |
Deaths | Refs | ||
|---|---|---|---|---|---|---|---|---|
| Category | Wind speed | Pressure | ||||||
| Vongfong (Ambo) | May 8–18 | Very strong typhoon | 155 km/h (95 mph) | 960 hPa (28.35 inHg) | Palau, Philippines, Taiwan | $50 million | 5 | [321][322][323] |
| Nuri (Butchoy) | June 10–14 | Tropical storm | 75 km/h (45 mph) | 996 hPa (29.41 inHg) | Philippines, South China | Unknown | 1 | [41] |
| Carina | July 11–15 | Tropical depression | Not specified | 1004 hPa (29.65 inHg) | Philippines, Taiwan | Minimal | None | |
| TD | July 27–29 | Tropical depression | Not specified | 1010 hPa (29.83 inHg) | None | None | None | |
| Hagupit (Dindo) | July 30 – August 5 | Typhoon | 130 km/h (80 mph) | 975 hPa (28.79 inHg) | Ryukyu Islands, Taiwan, East China, Korean Peninsula, Kamchatka Peninsula | $1.5 billion | 17 | [324][325][326] |
| Sinlaku | July 31 – August 3 | Tropical storm | 75 km/h (45 mph) | 985 hPa (29.09 inHg) | South China, Vietnam, Laos, Thailand, Myanmar | $12.9 million | 4 | [327][72][74][323] |
| Jangmi (Enteng) | August 6–11 | Tropical storm | 85 km/h (55 mph) | 994 hPa (29.35 inHg) | Philippines, Ryukyu Islands, Korean Peninsula | $1 million | None | [323] |
| 06W (Gener) | August 8–13 | Tropical depression | 55 km/h (35 mph) | 1012 hPa (29.88 inHg) | Bonin Islands, Ryukyu Islands | None | None | |
| Mekkhala (Ferdie) | August 9–11 | Severe tropical storm | 95 km/h (60 mph) | 992 hPa (29.29 inHg) | Philippines, Taiwan, East China | $159 million | None | [103][323] |
| Higos (Helen) | August 16–20 | Severe tropical storm | 100 km/h (60 mph) | 992 hPa (29.29 inHg) | Philippines, South China, Northern Vietnam | $143 million | 7 | [323][111][328] |
| Bavi (Igme) | August 20–27 | Very strong typhoon | 155 km/h (95 mph) | 950 hPa (28.05 inHg) | Philippines, Ryukyu Islands, Taiwan, Korean Peninsula, North China | $11.7 million | 1 | [323][116] |
| Maysak (Julian) | August 27 – September 3 | Very strong typhoon | 175 km/h (110 mph) | 935 hPa (27.61 inHg) | Philippines, Japan, Korean Peninsula, Northeast China | $100 million | 46 | [323] |
| Haishen (Kristine) | August 30 – September 7 | Violent typhoon | 195 km/h (120 mph) | 910 hPa (26.87 inHg) | Mariana Islands, Northeast China, Japan, Korean Peninsula | $100 million | 4 | [329][323] |
| 12W | September 10–12 | Tropical depression | 55 km/h (35 mph) | 1006 hPa (29.71 inHg) | Japan | None | None | |
| Noul (Leon) | September 14–18 | Tropical storm | 85 km/h (55 mph) | 994 hPa (29.35 inHg) | Laos, Thailand, Myanmar, Philippines, Vietnam, Cambodia | $175 million | 18 | [330][323][331] |
| Dolphin (Marce) | September 19–24 | Severe tropical storm | 110 km/h (70 mph) | 975 hPa (28.79 inHg) | None | None | None | |
| Kujira | September 25–30 | Severe tropical storm | 110 km/h (70 mph) | 980 hPa (28.94 inHg) | None | None | None | |
| TD | September 27–29 | Tropical depression | Not specified | 1000 hPa (29.53 inHg) | None | None | None | |
| Chan-hom | October 4–17 | Typhoon | 130 km/h (80 mph) | 965 hPa (28.64 inHg) | Japan | None | None | |
| Linfa | October 6–12 | Tropical storm | 85 km/h (55 mph) | 994 hPa (29.35 inHg) | Philippines, Vietnam, Cambodia, Laos, Thailand, Myanmar | $217 million | 138 | [332][333][251] |
| Nangka (Nika) | October 11–14 | Tropical storm | 85 km/h (55 mph) | 990 hPa (29.23 inHg) | Philippines, South China, Vietnam, Laos, Myanmar | $29.4 million | 4 | [197][334][335] |
| Ofel | October 13–16 | Tropical depression | 45 km/h (30 mph) | 1002 hPa (29.59 inHg) | Philippines, Vietnam, Laos | $187,000 | 10 | [207][336] |
| Saudel (Pepito) | October 18–25 | Typhoon | 120 km/h (75 mph) | 975 hPa (28.79 inHg) | Philippines, South China, Vietnam | $15.2 million | None | [219][335] |
| 20W | October 19–23 | Tropical depression | 55 km/h (35 mph) | 998 hPa (29.47 inHg) | None | None | None | |
| Molave (Quinta) | October 22–29 | Very strong typhoon | 165 km/h (105 mph) | 940 hPa (28.05 inHg) | Philippines, Spratly Island, Vietnam, Laos, Cambodia, Thailand, Malaysia, Myanmar | $742 million | 71 | [332][337][338][328] |
| Goni (Rolly) | October 26 – November 6 | Violent typhoon | 220 km/h (135 mph) | 905 hPa (26.72 inHg) | Philippines, Vietnam, Cambodia, Laos | $1.02 billion | 32 | [339][340][251] |
| Atsani (Siony) | October 30 – November 7 | Severe tropical storm | 95 km/h (60 mph) | 992 hPa (29.29 inHg) | Mariana Islands, Philippines, Taiwan, South China | $101,000 | None | |
| Etau (Tonyo) | November 6–10 | Tropical storm | 85 km/h (55 mph) | 992 hPa (29.29 inHg) | Philippines, Vietnam, Cambodia | $34.8 million | 3 | [341][328] |
| Vamco (Ulysses) | November 8–16 | Very strong typhoon | 155 km/h (95 mph) | 955 hPa (28.05 inHg) | Philippines, Vietnam, Laos, Thailand | $1.06 billion | 102 | [285] |
| TD | December 5–6 | Tropical depression | Not specified | 1010 hPa (29.83 inHg) | None | None | None | |
| Krovanh (Vicky) | December 18–24 | Tropical storm | 65 km/h (40 mph) | 1000 hPa (29.53 inHg) | Philippines, Malaysia, Thailand | $4.48 million | 9 | [342] |
| TD | December 29 | Tropical depression | Not specified | 1004 hPa (29.65 inHg) | None | None | None | |
| Season aggregates | ||||||||
| 32 systems | May 8 – December 29, 2020 | 220 km/h (140 mph) | 905 hPa (26.72 inHg) | $5.35 billion | 472 | |||
Seamless Wikipedia browsing. On steroids.
Every time you click a link to Wikipedia, Wiktionary or Wikiquote in your browser's search results, it will show the modern Wikiwand interface.
Wikiwand extension is a five stars, simple, with minimum permission required to keep your browsing private, safe and transparent.
