The 2021 Pacific typhoon season is an ongoing event in the annual cycle of tropical cycloneformation, in which tropical cyclones form in the western Pacific Ocean. The season runs throughout 2021, with no seasonal boundaries, though most tropical cyclones typically develop between May and October. The season's first named storm, Dujuan, developed on February 16. The season's first typhoon, Surigae, reached typhoon status on April 16. It became the first super typhoon of the year on the next day, also becoming the strongest tropical cyclone in 2021 so far. Surigae was also the most powerful tropical cyclone on record in the Northern Hemisphere for the month of April.[1]
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)[nb 2] names a tropical cyclone should it be judged to have 10-minute sustained wind speeds of at least 65 km/h (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 and 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)[nb 3] are given a number with a "W" suffix.
During the year, several national meteorological services and scientific agencies forecast how many tropical cyclones, tropical storms, and typhoons will form during a season and/or how many tropical cyclones will affect a particular country. These agencies included the Tropical Storm Risk (TSR) Consortium of University College London, PAGASA and Taiwan's Central Weather Bureau. The first forecast was released by PAGASA on December 27, 2020, in their monthly seasonal climate outlook predicting the first half of 2021.[4] The PAGASA predicts that only 0–3 tropical cyclones are expected to form or enter the Philippine Area of Responsibility between January and March, while 1–4 tropical cyclones are expected to form between April and June. PAGASA also predicted that the ongoing La Niña could persist until the end of the first quarter of 2021.[4] Tropical Storm Risk (TSR) issued their first, extended range forecast on May 11. TSR predicts a slightly-below average season with 24 tropical storms, 15 typhoons and 9 intense typhoons to form during the season.[3]
On June 23, the PAGASA released their monthly climate outlook for the rest of 2021, predicting 5 to 9 tropical cyclones developing or entering their area of responsibility from July to September, and 5 to 8 tropical cyclones from October to December.[5]
Seasonal summary
The season began in January with a weak and short-lived tropical depression that brought damages to the Philippines. In mid-February, another tropical depression formed, before being assigned the local name Auring by the PAGASA. The system then strengthened into a tropical storm, being given the name Dujuan by the JMA, making it the first named storm of the year. Another tropical depression formed in March, though it was short-lived, dissipating shortly after forming. On April 12, a tropical depression formed to the south of Woleai. It strengthened into a tropical storm, being given the name Surigae by the JMA. On April 15, it was further upgraded into a severe tropical storm, before being upgraded to a typhoon on the next day, and to a super typhoon on April 17,[nb 1] making it the first of the season and the strongest recorded cyclone to form in the month of April in the Northern Hemisphere, however, it did not hit any landmasses. Then, on mid-May a new tropical depression was named Crising by the PAGASA and made landfall on Baganga, Davao Oriental as a weak tropical storm, bringing minimal damages due to its small size. Two tropical depressions formed on May 29 and May 30 respectively, with the first being assigned the local name Dante by the PAGASA. Dante intensified into a tropical storm, being assigned the name Choi-wan, before moving over the Philippines and making landfall eight times, bringing widespread damages to the country.
On 12:00 UTC of February 16, the JMA reported that a tropical depression had formed.[7] Two hours later, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) for the system.[8] By February 17, the system moved into the Philippine Area of Responsibility (PAR), being assigned the local name Auring from the PAGASA.[9] At 09:00 UTC on the same day, the JTWC upgraded the system to a tropical depression, giving it the designation 01W.[10] On February 18, as it neared the Philippines, both the JTWC and the PAGASA upgraded the system to a tropical storm.[11][12] The JMA followed suit soon after, assigning it the name Dujuan.[13] The PAGASA later upgraded Dujuan to a severe tropical storm; however, this only lasted for six hours.[14][15] On February 20, the storm significantly weakened due to high vertical wind shear, prompting the JTWC to downgrade the system back to a tropical depression,[16] though the JTWC briefly re-classified the system as a tropical storm due to improvements in the storm's structure.[17] By February 22, all agencies had downgraded the system to a tropical depression after the system's center had weakened prior to making landfall.[18][19][20] The JMA and the JTWC issued their final advisories moments after.[18][21] The storm made landfall over Batag Island in Laoang, Northern Samar at 09:00 PHT (01:00 UTC) on February 22,[22] dissipating thereafter.[23]
Dujuan briefly moved over Palau on February 16 as a tropical depression, bringing heavy rainfall to parts of the country.[24][25] In anticipation of the storm, the PAGASA raised Signal #1 warnings for the eastern section of Mindanao and on the eastern provinces of Visayas on February 19.[26][27][28] Signal 2 warnings were also issued for the majority of Samar Island, Southern Leyte, the Dinagat Islands, and Surigao del Norte on February 21, prior to its landfall.[29] Classes and government work were suspended on February 22 in parts of Eastern Visayas and Central Visayas, including Surigao del Sur.[30][31] A total of 242,194 individuals were affected in Northern Mindanao, Caraga, and in the Davao Region. At least 77,811 of the affected individuals were taken to 344 various evacuation shelters in each region. One person was reported dead with four others reported missing, with total damages to agriculture and infrastructure amounting to ₱159.8 million (US$3.29 million).[32]
A low-pressure area south of Woleai developed into a tropical depression on April 12.[33][34] A few hours later, the JTWC issued a TCFA for the developing storm, with the PAGASA beginning to issue advisories for the tropical depression as it remained outside of the PAR.[35][36] On April 13, the JTWC upgraded the storm to a tropical depression and assigned it the designation 02W.[37] At 18:00 UTC, the JMA upgraded the cyclone to a tropical storm and named it Surigae.[38] On April 15 at 00:00 UTC, the JMA upgraded Surigae to a severe tropical storm as an eye began forming.[39] Later that day, the JTWC upgraded the storm to a typhoon, making it the first of the season. Surigae then entered the PAGASA's Philippine Area of Responsibility, getting the local name Bising. The JMA followed suit early on the next day as a central dense overcast developed and filled the original eye. Surigae continued to rapidly intensify, and on April 16, the JTWC upgraded Surigae to a Category 2-equivalent typhoon on the SSHWS.[40] The system continued its rapid intensification until it reached Category 5 super typhoon status, becoming the most intense typhoon ever recorded in the month of April.[41][42] Surigae soon reached its peak intensity, with a minimum central pressure of 895 millibars (26.43 inHg), 10-minute maximum sustained winds of 220 km/h (140 mph), and 1-minute sustained winds of 305 km/h (190 mph).[43][44] After attaining peak intensity, signs of a concentric eyewall indicated that the storm was undergoing an eyewall replacement cycle, with the central dense overcast starting to warm and the eye becoming cloud-filled.[45][46] On April 19, following its eyewall replacement cycle, Surigae became annular.[47] A few days later, on April 22, Surigae began to weaken again, with the storm's structure deteriorating and its large eye dissipating.[48] Soon afterward, all of the remaining convection was sheared to the east as the storm moved over cooler waters.[49] As most of the remaining thunderstorms had dissipated, the JTWC assessed that Surigae transitioned into a subtropical cyclone on April 23.[50] Late on April 24, the JTWC issued their final advisory on the system as it was nearing the completion of its extratropical transition.[51] A few hours later, the JMA declared that Surigae had become extratropical.[52]
After being named, tropical storm watches and warnings were issued for Yap in the Federated States of Micronesia, as well as for Koror and Kayangel in Palau on April 14.[53] Warnings were eventually issued for Ngulu Atoll as well.[54] Winds of up to 30 mph (50 km/h) were recorded in Yap on that day as Surigae passed from the southwest.[55] Damage in Palau was estimated at US$4.8 million.[56] On April 16, as the storm tracked towards the Philippines, the PAGASA issued Signal #1 warnings for areas around the country, also issuing Signal #2 warnings the next day for Catanduanes and Samar.[57][58][59] Very strong winds and heavy rains affected the eastern part of the Philippines, with storm surge inundating parts of coastline nearest to the typhoon. Surigae killed a total of 8 people and left another 10 missing.[60][61] The storm also caused at least ₱272.55 million (US$5.65 million) in damages.[60]
On May 11, the JTWC noted a persistent area of convection in the Philippine Sea, approximately 184 nmi (341 km) west of Palau.[62] The JTWC issued a TCFA for the convection on May 12, as it further developed in an environment with low vertical wind shear and warm sea surface temperatures.[63] Just three hours later, the agency recognised that the area of convection had quickly consolidated into a tropical depression and assigned it with the identifier of 03W.[64] Around the same time, the JMA had also recognised the storm as a tropical depression while it was to the east of Mindanao.[65] Since the storm developed within the Philippine Area of Responsibility, the PAGASA immediately named the storm Crising once the agency recognized it as a tropical depression as well, and later raised Signal No. 2 warnings for areas in Mindanao.[66][67] In the early hours of May 13, the JTWC upgraded the system into a tropical storm, with the PAGASA following suit hours later.[68][69] Later that day, Crising's low-level circulation center became exposed due to wind shear, and it lost organization. At 8:20 p.m. Philippine Standard Time (12:20 UTC), Crising made landfall in Baganga, Davao Oriental as a weakening tropical storm. It quickly degraded as soon as it made landfall, with both the JTWC and the PAGASA downgrading it to a tropical depression at 15:00 UTC.[70][71] At 03:00 UTC on that day, the PAGASA reported that the system degenerated to an area of low-pressure in the vicinity of Piagapo in Lanao del Sur, thus lifting all warning signals on Mindanao and issuing their final advisory.[72] On May 14, the system dissipated over the Sulu Sea, and both the JMA and the JTWC issued their final advisories on the storm.
In preparations for the storm, the local government of Davao Occidental raised a blue alert on May 13, with the authorities in the area preparing rescue equipment in case of emergency.[73] The PAGASA also warned small vessels near the area to stay away from the rough seas caused by the storm.[74] Schools were ordered to be suspended from that day in Davao Occidental, including the submission of modules.[74] When Crising made landfall, it caused widespread rains and flooding across Mindanao and Southern Visayas. Gusty winds were also felt in parts of Mindanao where the storm passed.[75] In Baganga, some trees were knocked down by strong winds, while strong winds with heavy rainfall were reported in Cateel and Boston, all in the province.[73] Three men and a carabao were required to be rescued from the rising Kabacan River in the early hours of May 14; they were successfully released safely from the said river.[75] An evacuation center in South Upi, Maguindanao were reported to be flooded and some crops near the center were submerged in floodwaters, all due to a rising river near the area.[75] Agricultural damages were estimated at ₱23.2 million (US$486,000).[76]
On May 27, the JMA and the JTWC noted the persistence of an area of atmospheric convection about 425 nautical miles (787 km; 489 mi) south-southeast of Guam.[77] The area's nearby environment exhibited low wind shear and warm sea surface temperatures, which were ideal conditions for tropical cyclogenesis.[78] The JMA assessed the area to have developed into a Tropical depression on May 29 at 06:00 UTC.[79] The PAGASA made a similar assessment in a Tropical Cyclone Advisory issued at 15:00 UTC.[80] The JTWC later followed with their own assessment, identifying the center of the newly-developed tropical depression and assigning the designation 04W.[81] As the system tracked westward, it entered the Philippine Area of Responsibility at 01:00 PHT (17:00 UTC).[82] The PAGASA then named the storm Dante in its first Tropical Cyclone Bulletin for the storm.[83] Dante further organized in the Philippine Sea,[84] and on May 30 at 15:00 UTC, the JTWC upgraded it to a tropical storm,[85] with the PAGASA doing the same at 21:00 UTC.[86] On the next day at 00:00 UTC, the JMA also upgraded Dante into a tropical storm, giving it the international name Choi-wan.[87] Choi-wan's center was exposed due to a tropical upper tropospheric trough from the northeast, inducing shear on the system.[88] On June 1 at 12:30 UTC, Choi-wan made landfall on Sulat, Eastern Samar as a minimal tropical storm,[89] with the JTWC downgrading it to a tropical depression at 15:00 UTC.[90] It made a second landfall on Cataingan at 17:00 UTC.[91] Choi-wan made several more landfalls on the Philippines, making its third landfall on Balud, Masbate at 19:30 UTC. It made a fourth landfall on Romblon, Romblon on June 2 at 00:00 UTC, a fifth on San Agustin, Romblon at 00:50 UTC, a sixth on Pola, Oriental Mindoro at 06:00 UTC, a seventh on Tingloy, Batangas at 11:20 UTC, and an eighth and final landfall on the Calatagan Peninsula before moving into the South China Sea.[92] On June 3 at 03:00 UTC, the JTWC upgraded Choi-wan back to a tropical storm.[93] At 03:00 UTC, the PAGASA removed all Tropical Cyclone Warning Signals as Choi-wan moved away from the country.[94] Choi-wan then exited the PAR on June 3 at 18:00 UTC[95] before weakening into a tropical depression on the next day at 06:00 UTC and re-entering the PAR at 08:00 UTC.[96] Then, it passed southeast of the island of Taiwan[97] before moving out near the Okinawa Prefecture and heading towards Japan.[citation needed] On June 5 at 06:00 UTC, the Japan Meteorological Agency issued their final advisory on the system.[98] 3 hours later at 09:00 UTC, the JTWC upgraded Choi-wan back into a tropical storm,[99] however at 15:00 UTC, the Joint Typhoon Warning Center downgraded the system to a tropical depression, also issuing their final advisory on the system.[100]
Heavy rains caused floods in parts of Mindanao;[101] 11 fatalities were reported, 3 people were injured, and 2 people are missing.[102] As of June 4, 55,226 people were affected and 16,680 people are inside evacuation centers. A total of ₱307.2 million (US$6.39 million) of damages were incurred throughout the country, of which ₱152.1 million (US$3.17 million) was agricultural damages and ₱155.1 million (US$3.23 million) was related to infrastructure.[103] On June 1, classes and government work for parts of Davao de Oro, Eastern Samar, Leyte, and Surigao del Sur were suspended for the day.[104]
On June 10, the JTWC started to monitor an area of low-pressure in the South China Sea, approximately 518 km (322 mi) to the south of Hong Kong, with the former classifying the system as a monsoon depression.[105] Tracking west-northwestward, the storm was located in a favourable environment for further development, with warm sea surface temperatures and low wind shear, being offset by lack of divergence aloft.[106] At 06:00 UTC on June 11, the JMA upgraded the system into a tropical depression.[107][108] Six hours later, the JTWC issued a TCFA for the system.[109] On June 12 at 03:00 UTC, the JTWC upgraded the system into a tropical depression, assigning it the designation 05W.[110] Three hours later at 06:00UTC, the JMA upgraded the system to a tropical storm, assigning it the name Koguma.[111] Another three hours later, the JTWC also upgraded the system to a tropical storm. On the next day, the storm made landfall in extreme northern Vietnam and dissipated later that day.
At 00:00 UTC on June 18, the JTWC started to monitor a broad area of convection nearly 250 km (160 mi) to the south-southwest of Pohnpei.[112] The system remained weak as it moved northwestwards in a favorable environment for further intensification, characterized by warm sea surface temperatures, low to moderate wind shear and good outflow, the disturbance remained weak as it moved northwestwards.[112][113] The JTWC issued a TCFA on the system two days later, despite the system remaining disorganised.[114][115] The JMA upgraded the system to a tropical depression at 00:00 UTC on June 21.[116] Meanwhile, the JTWC designated it as 06W in their first advisory on the system, with an exposed LLCC being evident on satellite imagery due to moderate wind shear, being induced by a tropical upper tropospheric trough to its north.[117][118] By 21:00 on June 21, 06W made its closest passage to the south-southwest of Guam, continuing its northwest track.[119][120] On June 22, at 06:00 UTC, JTWC upgraded the system into a tropical storm as it continued to move away from Guam.[121] The JMA followed and upgraded the system into a tropical storm, in June 23 at 00:00 UTC, and assigned it the name Champi.[122] At 18:00 UTC, the JMA upgraded the storm to a severe tropical storm as it turned northwestwards.[123] At this time, a microwave imagery scan of Champi revealed an eye feature emerging on the system; however, this was short lived as dry air continued to impact the storm from the west.[124] In addition, poleward outflow on the system remained weak on June 24, restricting Champi to significantly develop.[125] However, on the next day, as a shortwave trough crossed the Ryukyu Islands, the outflow increased on the storm which allowed it to intensify further.[126] On June 25, at 06:00 UTC, the JMA officially declared the storm a typhoon.[127] The JTWC soon followed upgraded it into a Category 1 typhoon.[128] At this time, a Champi turned north and north-northwestwards, and subsequently reached its peak intensity of 120 km/h (75 mph) ten-minute maximum sustained winds with a minimum barometric pressure of 980 hPa (28.94 inHg) by 21:00 UTC of June 25, however it was downgraded to a tropical storm a day later.[129] The storm continued to weaken as it move towards the Japanese islands, until on June 27, the JMA issued its last advisory at 12:00 UTC as the system became an extratropical low.[130] The JTWC also issued its last warning for Champi at 09:00 UTC, same day.[131]
The approach of Champi as a tropical depression from the west-northwest required a tropical storm watch for Rota in the Northern Mariana Islands and a warning for the whole island of Guam on June 21.[132][133] Marine and flash flood warnings were also posted on the former and on Saipan, Tinian, and other islands in the east and south, while classes on an elementary and a high school in the latter were suspended on the next day due to a reported power outage.[134][135] Electrical disruptions were also experienced on Chalan Pago, Toto/Canada, and Santa Rita in Guam due to the system's near approach.[135] As it moved away from the island and the Marianas, the watch and warning on these areas were lifted at 01:00 UTC on June 22.[136] In the Bonin Islands, residents in the area were advised of rough seas and gusty winds due to Champi.[137]
On July 2, the JTWC started to monitor a tropical disturbance to the southwest of Guam.[138] Moving northwestwards, the disturbance is located in an environment conducive for intensification in the Philippine Sea, with warm sea surface temperatures and low wind shear, in addition to good poleward outflow, being induced by an upper-level trough to the northwest.[139][140] The JMA upgraded the broad and weak system to a tropical depression at 18:00 UTC on the next day,[141] followed by a Tropical Cyclone Formation Alert (TCFA), an hour and a half later.[142][143] The PAGASA subsequently upgraded the system to a tropical depression at 02:00 UTC on July 4, naming it Emong.[144][145] At 21:00 UTC, the JTWC designated as 07W.[146]
In the Philippines, the depression's approach which is locally named Emong required Public Storm Warning Signal No. 1 in the provinces of Batanes and the northeastern portion of Cagayan, including the Babuyan Islands, starting on July 4.[147][148] The Office of Civil Defense (OCD) of Cagayan were also on blue alert on the next day due to the storm, with the agency conducting a pre-disaster assessment with other government bureaus that day.[18] The residents on the coastal areas of Palanan, Divilacan, Maconacon and Dinapigue in Isabela were also warned of the storm while fishing activities in the region were prohibited due to Emong.
Current storm information
As of 18:00 UTC July 5, Tropical Depression 07W (Emong) is located near 21°18′N120°18′E / 21.3°N 120.3°E / 21.3; 120.3 (Emong), about 220 nautical miles (405 km; 255 mi) south-southwest of Taipei, Taiwan. Maximum 10-minute sustained winds are at 30 knots (55 km/h; 35 mph) with gusts up to 45 knots (85 km/h; 50 mph), while maximum 1-minute sustained winds are at 30 knots (55 km/h; 35 mph). The minimum central barometric pressure is 1004 hPa (29.65 inHg), and the system is moving west-northwest at 20 knots (37 km/h; 23 mph).
During January 19, the JMA reported that a tropical depression had developed to the east of Luzon, Philippines.[149] The precursor to the depression brought scattered showers and thunderstorms to Mindanao, Palawan, and Visayas on January 18.[150] The JMA, however, discontinued advisories for the system on the next day.[151] The depression also brought stormy weather to Luzon on January 20. The PAGASA warned residents of possible flash flooding and mudslides due to heavy rainfall.[152] The system's precursor was associated with a frontal system, with its combined effects bringing heavy rainfall over much of Visayas, the Bicol Region, and Northern Mindanao, resulting in three deaths and agricultural damages of up to ₱642.5 million (US$13.2 million).[153]
On March 9, a low-pressure area entered the Philippine Area of Responsibility, though it was not expected to develop at that time.[154][155] On March 14, the low-pressure area intensified into a tropical depression over the Sulu Sea before quickly degenerating back into a low-pressure area.[156][157] The system brought light to moderate rains over parts of the Philippines, with the PAGASA advising residents of the possibility of floods and landslides.[158]
On May 29, the JTWC issued a TCFA for a tropical disturbance that was roughly 622 nautical miles (1,152 km; 716 mi) to the southeast of Guam, near the Nomoi Islands. The system gradually developed as it was experiencing warm sea surface temperatures and low vertical wind shear.[159] On the next day at 00:00 UTC, the JMA recognized the system as a tropical depression.[160] On the same day, the JTWC cancelled the TCFA for the system as its structure degraded,[161] with the JMA last recognizing the system as a tropical depression on June 1 at 18:00 UTC.[162]
On June 29, an area of convection formed 425 nmi (787 km; 489 mi) from Guam with satellite imagery revealing that the system had a deep convection with a weak low level circulation.[163] Within a favorable environments with low-to-moderate wind shear, and warm sea surface temperatures, the system gradually became more organized with a more defined low level circulation. On June 30, the JTWC issued a TCFA for the system.[164][165] On July 1, animated multispectral satellite imagery indicated a very broad and ill-defined low level circulation with convection being sheared to the south southwest of the disturbance, which prompted the JTWC to cancel the system's TCFA and downgrade its development chances within the next day to low.[166] The JMA no longer considered it a tropical depression in their tropical disturbance summary advisories on the same day.[167]
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.[168] 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).[169] PAGASA names to tropical cyclones which move into or form as a tropical depression in their area of responsibility located between 135°E and 115°E and between 5°N and 25°N even if the cyclone has had an international name assigned to it.[168] The names of significant tropical cyclones are retired, by both PAGASA and the Typhoon Committee.[169] 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.
A tropical cyclone is named when it is judged to have 10-minute sustained windspeeds of 65 km/h (40 mph).[170] 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.[171] Retired names, if any, will be announced by the WMO in 2022; though replacement names will be announced in 2023. The next 28 names on the naming list are listed here along with their international numeric designation, if they are used. During the season, the names Surigae and Koguma were used for the first time after they replaced Mujigae and Koppu in the 2015 season.
PAGASA uses its own naming scheme for typhoons that will either develop within or move into their self-defined area of responsibility.[172] The names were taken from a list of names, that was last used during 2017 and are scheduled to be used again during 2025.[172] All of the names are the same except Uwan and Verbena which replaced the names Urduja and Vinta after they were retired.[172]
This table summarizes all the systems that developed within or moved into the North Pacific Ocean, to the west of the International Date Line during 2021. The tables also provide an overview of a systems intensity, duration, land areas affected and any deaths or damages associated with the system.
^ abA super typhoon is an unofficial category used by the Joint Typhoon Warning Center (JTWC) for a typhoon with winds of at least 240 km/h (150 mph).[6]
^The Joint Typhoon Warning Center is a joint United States Navy – United States Air Force task force that issues tropical cyclone warnings for the western Pacific Ocean and other regions.[2]
^"TYPHOON 06W (CHAMPI) WARNING NR 018". www.metoc.navy.mil/jtwc. Pearl Harbor, Hawaii: Joint Typhoon Warning Center. June 25, 2021. Archived from the original on June 25, 2021. Retrieved June 25, 2021.
^ abThe Typhoon Committee (February 21, 2013). "Typhoon Committee Operational Manual 2013"(PDF). World Meteorological Organization. pp. 37–38. Archived(PDF) from the original on August 28, 2012. Retrieved October 1, 2013.
^ abc"Philippine Tropical Cyclone Names". Philippine Atmospheric, Geophysical and Astronomical Services Administration. Archived from the original on January 30, 2021. Retrieved January 30, 2021.
