Английская Википедия:2017 Pacific typhoon season

Материал из Онлайн справочника
Перейти к навигацииПерейти к поиску

Шаблон:Short description Шаблон:Infobox tropical cyclone season

The 2017 Pacific typhoon season was a below-average season in terms of accumulated cyclone energy and the number of typhoons and super typhoons, and the first since the 1977 season to not produce a Category 5-equivalent typhoon on the Saffir–Simpson scale. The season produced a total of 27 named storms, 11 typhoons, and only two super typhoons, making it an average season in terms of storm numbers. It was an event in the annual cycle of tropical cyclone formation, in which tropical cyclones form in the western Pacific Ocean. The season runs throughout 2017, though most tropical cyclones typically develop between May and October. The season's first named storm, Muifa, developed on April 25, while the season's last named storm, Tembin, dissipated on December 26. This season also featured the latest occurrence of the first typhoon of the year since 1998, with Noru reaching this intensity on July 23.

The scope of this article is limited to the Pacific Ocean, to the north of the equator between 100°E and the 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 Шаблон:Convert anywhere in the basin. PAGASA assigns unofficial names to tropical cyclones which move into or form as a tropical depression in their area of responsibility, located between 115°E–135°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 numerical designation with a "W" suffix.

Seasonal forecast

TSR forecasts
Date
Tropical
storms
Total
Typhoons
Intense
TCs
ACE Ref
Average (1965–2016) 26 16 9 297 [1]
May 5, 2017 27 17 10 357 [1]
July 6, 2017 25 15 7 250 [2]
August 8, 2017 26 14 7 255 [3]
Other forecasts
Date
Forecast
Center
Period Systems Ref
January 20, 2017 PAGASA January — March 1–2 tropical cyclones [4]
January 20, 2017 PAGASA April — June 2–4 tropical cyclones [4]
June 26, 2017 CWB January 1 — December 31 21–25 tropical storms [5]
July 6, 2017 PAGASA July — September 6–9 tropical cyclones [6]
July 6, 2017 PAGASA October — December 3–5 tropical cyclones [6]
2017 season Forecast
Center
Tropical
cyclones
Tropical
storms
Typhoons Ref
Actual activity: JMA 41 27 11
Actual activity: JTWC 33 26 13
Actual activity: PAGASA 22 16 4

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 of the year was released by PAGASA during January 20, within its seasonal climate outlook for the period January–June.[4] The outlook noted that one to two tropical cyclones were expected between January and March, while two to four were expected to develop or enter the Philippine Area of Responsibility between April and June.[4] During March 23, the Hong Kong Observatory predicted that the tropical cyclone season in Hong Kong would be near-normal, with four to seven tropical cyclones coming within Шаблон:Convert of the territory, compared to an average of six, which was revised to six to nine tropical cyclones in August.[7]

On May 5, Tropical Storm Risk (TSR) issued their first forecast for the season, anticipating an activity of slightly above normal with 27 named storms, 17 typhoons and 10 intense typhoons, including an accumulated cyclone energy (ACE) of 357.[1] On June 26, Taiwan's Central Weather Bureau (CWB) predicted a normal season with 21–25 tropical storms developing over the basin, while three — five systems were expected to affect Taiwan itself.[5] On the same day, the Thai Meteorological Department (TMD) predicted that 2 tropical cyclones would move towards the northern or northeastern parts of Thailand during August or September.[8] On July 6, TSR released their second forecast for the season, reducing the predicted numbers to 25 named storms, 15 typhoons, and 7 intense typhoons, with an ACE Index of 250.[2] During the same day, the PAGASA issued their second and final outlook for the season for the period of July–December, where six to nine tropical cyclones were expected to develop or entered their area of responsibility between July and September, while three to five were forecast during October to December. During August 8, the TSR released their third and final forecast for the season, slightly raising their forecast named storms to 26, with 14 reaching typhoon intensity and 7 reaching intense typhoon intensity. ACE Indices were slightly raised to 255.[3]

Season summary

Шаблон:Center The first half of the season was relatively inactive, with only seven systems developing, of which only two intensified into tropical storms. The first system of 2017 developed on January 7, and was named Auring by PAGASA. Tropical Depression Bising developed during the first week of February, and was a factor in, and worsened the effects of, the 2017 Visayas and Mindanao floods. This was followed by Crising, the third system unofficially named by PAGASA. Heavy rains from the depression caused flooding that led to the deaths of 10 people in Cebu, Philippines. Shortly after the dissipation of Crising came the formation of the first tropical storm of the season — Muifa. The system was not strong, however, and was located away from all major land areas, so it caused no damage. No systems formed during the month of May, the first such occurrence since 2013. The next cyclone, Merbok, formed during mid-June, and made landfall in Shenzhen in China. The cyclone was short-lived; however, it was relatively strong, producing winds of Шаблон:Convert at its peak. Nanmadol passed over the Ryukyu Islands and progressed to make landfall in Nagasaki on Japan's island of Kyushu during early July. Torrential rainfall and strong winds from the cyclone itself and from the stormy weather that persisted for a number of days were responsible for major damage and 41 fatalities across mainland Japan.

Файл:Sonca, Haitang, Nesat, Noru 2017-07-29.jpg
On July 29, four storms were active simultaneously: the remnants of Sonca (the furthest left and inland), Haitang (center-left), Nesat (center-right), and Noru (top-right).

By the middle of July, tropical activity had increased with simultaneous tropical storms developing after July 14. Severe Tropical Storm Talas formed during mid-July near the Paracel Islands in the South China Sea, and traveled generally westwards. It made landfall in Vietnam after brushing China's Hainan province and, unusually, continued to track far inland to the LaosThailand border before weakening to a depression. At least 14 deaths were attributed to the storm, primarily as a result of flooding. Later, the season was very active with 7 storms in late July-early August. Typhoon Noru reached Category 4 super typhoon in peak intensity and made landfall in Japan, causing $100 million in damage. Tropical Storm Sonca made landfall in Quảng Trị, Vietnam; 2017 was the first year since 1971 where 2 storms made landfall in Central Vietnam in July. Sonca brought heavy rainfall in Northeast Thailand and caused extreme flooding in the region with estimated costs of over US$300 million. Typhoon Nesat and Tropical storm Haitang made landfall in Taiwan and Fujian (a province in China), respectively, 2 days apart. In mid-late August, Typhoon Hato and Tropical Storm Pakhar made landfall in Macau and Guangdong respectively while they were at peak intensity. So far Typhoon Hato is the costliest tropical cyclone in Northwest Pacific in 2017 with damages totalling $6.82 billion.

The season was weaker in September. Typhoon Talim made landfall in Japan as a minimal typhoon and caused US$700 million in damage. Typhoon Doksuri made landfall in Quảng Bình, Vietnam as a Category 3 typhoon; damage was very major as the total was estimated at over US$814 million. In early October a tropical depression made landfall in Northern and North Central Vietnam, which brought very heavy rainfall and was responsible for the worst flooding in Northern and North-Central Vietnam, with 109 deaths and total damages of over US$570 million. Later, Typhoon Khanun made landfall in Southern China. So far Typhoon Lan has been the strongest tropical cyclone in the basin in 2017, and became the second largest tropical cyclone on record.

In November, La Niña was returned and tropical activity had increased with simultaneous tropical storms developing, and most of them moved west and affected Philippines and Vietnam. Typhoon Damrey made landfall in Khánh Hòa, Vietnam and became one of the costliest typhoon in Vietnamese history since 1975; and it is one of the costliest and deadliest typhoon in the basin in 2017 with total damage reached US$1.03 billion and 151 deaths. Later, two weak storms affected Philippines. In December, Tropical storm Kai-tak caused flooding in Central Philippines. Typhoon Tembin was responsible for severe flooding and landslides in South Philippines, it became the deadliest tropical cyclone in 2017 with over 250 deaths. Typhoon Tembin moved South into the China Sea, so 2017 became the most active tropical cyclone season in the South China Sea with 22 Tropical cyclones, and Tembin affected Southern Vietnam.

Systems

Tropical Depression 01W (Auring)

Шаблон:Infobox tropical cyclone small On January 7, both PAGASA and the JMA reported that Tropical Depression Auring developed about Шаблон:Convert to the northeast of Davao City on Mindanao, Philippines.[9][10] During that day, the system moved along the southern periphery of a subtropical ridge of high pressure, before the JTWC initiated advisories on the system and designated it as Tropical Depression 01W.[11] It later made landfall in the Philippines the next day, and was assessed to have degenerated into a remnant low by the JTWC.[12] Шаблон:Cn span By January 15, the JTWC re-issued advisories as it was located to the east of Vietnam.[13] However, convection dissipated due to wind shear and land interaction, the JTWC issued their final warnings on January 16.[14]

Flooding from Auring killed a total of 11 people.[15] Damages from Tropical Depression Auring were totaled at 7.14 million (US$144,000) from agriculture and fishing in Negros Occidental.[16]

Tropical Depression Bising

Шаблон:Infobox tropical cyclone small On February 3, a tropical depression developed near Palau.[17] The PAGASA would later name it as "Bising" as the depression was present at the Philippine Area of Responsibility.[18][19] The storm would meander around the Philippine Sea, until the depression started to weaken when its LLCC became exposed, while moving north-northeast.[20][21] The agency would not notice its weakening until the next day, when they issued their last advisory.[22]

Tropical Depression 02W (Crising)

Шаблон:Infobox tropical cyclone small A tropical depression formed over Palau on April 13.[23] On the next day, the JTWC designated the depression as "02W"; on the best track, the depression was a remnant low at this time.[24] Hours later, the PAGASA would name it "Crising" as the depression was present at the Philippine Area of Responsibility.[25][26] The depression would later shrink its size while approaching the Visayas region.[27] On the following day, the agency reported that "Crising" slightly intensified while moving near the Samar provinces; the intensification of the storm would prove only momentarily and weakened again.[28][29] The JTWC would later discontinue advisories on the storm; on its best track, the system remained as a disturbance.[24] The PAGASA discontinued the advisories on the system as it was nearing landfall on 13:00 UTC (9:00 pm PHST) over Hernani, Eastern Samar.[30] The remnants of the depression crossed the region and into the South China Sea.[31] At 18:00 UTC on April 18, the JTWC would upgrade the disturbance as 02W; operationally, the system was kept as a disturbance.[24] The status would be short-lived, as the JTWC declared 02W as a disturbance.[24] The remnants would later linger around, dissipating on April 20, while in the Luzon Strait.[24]

As of April 17, at least ten people were reported to be killed in Cebu by flooding caused by the system.[32] Total damages throughout the Philippines reached 84.8 million (US$1.7 million), mostly from Danao, Cebu.[33]

Tropical Storm Muifa (Dante)

Шаблон:Infobox tropical cyclone small During April 22, the JMA started to monitor a tropical depression that had developed near Guam.[34] After moving westward for a couple of days, the JTWC began issuing advisories, and designated the storm 03W. By April 25, 03W organized and began consolidating further as the JMA upgraded the depression to a tropical storm, giving it the name Muifa.[34] Muifa entered the Philippine Area of Responsibility the following day, and was named Dante by PAGASA.[35] The storm, however, started moving northwards and immediately tracked out of the area by April 27.[36] Following this, both the JMA and the JTWC downgraded Muifa to a tropical depression. Muifa fully dissipated early on April 29, and the JMA issued their final advisory on the storm.[34]

Severe Tropical Storm Merbok

Шаблон:Infobox tropical cyclone small Шаблон:Main On June 10, the JMA started to track a tropical depression to the west of Manila, Philippines.[34] Шаблон:Cn span A few hours later, 04W had intensified into a tropical storm, receiving the name Merbok as it starts to move in a north-northwestward direction.[34] On June 12, Merbok reached its peak intensity with 10-minute winds of Шаблон:Convert and a minimum pressure of 985 hPa, shortly before making landfall in Eastern Shenzhen.[34][37] On June 13, the JMA issued its final warning on Merbok, as the system dissipated over China.[37][38]

Sustained winds of Шаблон:Convert and a minimum pressure of Шаблон:Convert were recorded in Hong Kong as the eye passed nearby.[37] Across Guangdong Province, 32 homes were destroyed, 122,000 people reported property damage, and 13,000 hectares of crops flooded. Total economic losses in South China were counted to be CN¥600 million (US$88.3 million).[39]

Severe Tropical Storm Nanmadol (Emong)

Шаблон:Infobox tropical cyclone small Шаблон:Main On July 1, the JMA upgraded a low-pressure area it had been monitoring to a tropical depression, located south-southwest of Okinotorishima.[40] Later that day, the JMA began issuing advisories once the depression's sustained winds were estimated at Шаблон:Convert.[41] Shortly thereafter, the PAGASA classified the system as a tropical depression, assigning the local name Emong. On July 2, the JMA classified the system as a tropical storm, and assigned the official name Nanmadol.[40] The JTWC followed suit and gave the internal designation of 05W. The cyclone continued to intensify, and was upgraded by the JMA to a severe tropical storm later that day.[40] Nanmadol reached peak intensity at about 06:00 UTC on July 3,[40] and maintained this strength until making landfall on the western coast of Kyushu several hours later. The cyclone began to accelerate while following a generally eastward course across the south of Japan. After brushing the southern coast of Japan, the JTWC issued its final advisory during the next day. The JMA followed suit late on July 4, when it had become extratropical.[40] Its remnants moved out of the basin three days later.[40]

Evacuation advisories were issued to at least 20,000 residents due to fears of possible flooding and landslides, especially in the prefectures of Niigata, Toyama and Nagano, which had experienced rainfall accumulations of up to Шаблон:Convert in the preceding hours.[42][43] At least three people were injured during the storm—a young boy's hand was injured when a school window broke in the city of Kumamoto, and two adults in Ōita prefecture sustained minor injuries after falling due to the strong winds.[42][43][44] A total of 41 people have been confirmed dead due to torrential rains which caused landslides and flooding, particularly in Kyushu. Total damages from the storm in Japan were amounted to be ¥190 billion (US$1.68 billion).[45]

Severe Tropical Storm Talas

Шаблон:Infobox tropical cyclone small Шаблон:Main Early on July 14, the JMA upgraded a low-pressure area in the South China Sea to a tropical depression after the system began to organize.[46] Late the same day, the JMA began issuing advisories on the depression, and forecast it to develop into a tropical storm within the next 24 hours.[47] The system intensified into a tropical storm, and was then named Talas. A few days later, Talas intensified further to become a severe tropical storm.

Talas made landfall near Vinh of Nghệ An Province in Central Vietnam at 01:00 ICT on July 17 (18:00 UTC on July 16) as a severe tropical storm.[48] In Vietnam, the storm left 14 people dead and damaged around 2,700 houses. A coal ship with 13 crew members sank off the coast of Cửa Lò, leaving 3 dead and another 3 still unaccounted for.[49] Damages in Vietnam were counted to be 993 billion (US$43.7 million).[50] Total economic losses in Hainan Province reached CNY 60 million (US$8.8 million).[39]

Typhoon Noru

Шаблон:Infobox tropical cyclone small Шаблон:Main The JMA reported that a non-tropical low had transitioned into a tropical depression north-northwest of Wake Island early on July 19. Twelve hours later it had strengthened to a tropical storm, and was named Noru.[51] Noru then interacted with Tropical Storm Kulap, its counterpart storm, and began to exhibit a fujiwhara effect with Kulap. Tropical Storm Kulap then weakened enough, and when it dissipated, its remnants started to power Noru, and it became a severe tropical storm after, and continued its long and erratic journey towards Japan.

About halfway through July 22, the system became the first typhoon of the season, and fluctuations in intensity occurred until late on July 29, when it slowed down, and shortly thereafter, explosive intensification ensued, and Noru intensified into a Category 4 super typhoon. After it reached peak intensity, it quickly began to weaken for a short period of time before slowing the rate of weakening. It briefly accelerated, before yet again, it began to stall near Japan for some time before moving north and dissipating in the Sea of Japan. Total economic losses in Japan were counted to be US$100 million.[52]

Tropical Storm Kulap

Шаблон:Infobox tropical cyclone small On July 20, the JMA started to monitor a tropical depression that formed over to the southwest of Midway Atoll, just to the west of the International Date Line.[34] The JTWC classified the system as subtropical, however.[53] By July 21, the subtropical storm started to show tropical characteristics, where it prompted both agencies to start issuing advisories, receiving the designation of 09W and the name Kulap.[54][34] During the next day, Kulap briefly reached its peak intensity with 1-minute sustained winds of Шаблон:Convert after imagery depicted some convection over near its compact center.[55] After moving westward in a marginally favorable environment, the JMA had reported a minimum pressure of 1002 hPa with peak 10-minute winds of Шаблон:Convert during the early hours of July 24. However several hours later, Kulap had entered in a very unfavorable environment such as cooler waters of Шаблон:Convert.[56] Due to strong shear and an interaction with Typhoon Noru to its south, Kulap had rapidly weakened; therefore, both agencies issued their final advisory on July 26.[57] The JMA, however, tracked Kulap's remnants until July 28 when it was absorbed by the outflow of Typhoon Noru.[34]

Tropical Storm Sonca

Шаблон:Infobox tropical cyclone smallШаблон:Main On July 21, both the JMA and the JTWC reported that Tropical Depression 08W had developed approximately Шаблон:Convert to the south of Hong Kong.[34][58] After moving westward for a couple of days, the system strengthened into a tropical storm by both agencies while nearing the island province of Hainan, receiving the name Sonca.[59][34] By July 24, Sonca reached its maximum intensity with a minimum pressure of 994 hPa.[34] Early on July 25, the JTWC issued its final advisory as the system made landfall over in Quảng Trị Province, Vietnam.[60][61] The JMA issued its final advisory a few hours later when it had weakened into a tropical depression,[34] although Sonca maintained its intensity over land until it had fully dissipated on July 29.[34]

Flooding in Northern Cambodia drowned two people, blocked many roads and flooded several hundred houses.[62] Damage across Sakon Nakhon, Thailand exceeded 100 million baht (US$3 million)[63] and killed 23 people across Thailand.[64]

Tropical Storm Roke (Fabian)

Шаблон:Infobox tropical cyclone small The JMA noted the formation of a tropical depression southeast of Taiwan early on July 21.[34] Assigning the numerical designation 10W, the JTWC upgraded the system to a tropical depression at about 18:00 UTC the same day.[65] The system traveled in a generally northwesterly direction, and passed through the Luzon Strait, between Taiwan and the Philippines.[65] Around the same time, the PAGASA began issuing advisories on the depression, and contributed the unofficial name Fabian.[66] Early the next day, after the system had emerged into the South China Sea, both the JMA and the JTWC upgraded the system to a tropical storm, naming it Roke.[65][34] Roke assumed a more westerly course, and tracked obliquely towards China's Guangdong coast.[67] The JTWC downgraded the system to a tropical depression just 12 hours later, at 18:00 UTC,[65] but the JMA maintained the cyclone's category as a tropical storm. Roke made landfall just east of the Hong Kong central business district at about 01:30 UTC on July 23, and passed over Shenzhen one to two hours later.[67] Roke weakened to a depression a few hours later, though the JMA declared that it had dissipated on 18:00 UTC of the same day.[34]

Schools, businesses and government offices were closed in Hong Kong as the Hong Kong Observatory (HKO) raised its typhoon warning signal to 8—the third highest of five levels—in preparation for Tropical Storm Roke.[68] Ferry services in the city were suspended, and more than 50 flights were delayed.[69] However, winds in the city were relatively light and no significant damage was reported.

Typhoon Nesat (Gorio)

Шаблон:Infobox tropical cyclone small Шаблон:Main The JMA upgraded a low-pressure area to a tropical depression east of the Philippines early on July 25. On July 26, it was named Gorio by PAGASA and later intensified into Tropical Storm Nesat. Nesat stalled in the Philippine Sea in the next couple of days and gradually intensified to become a severe tropical storm on July 27. It gradually strengthened until its peak on July 29, as a Category 1 typhoon. It then hit Taiwan, and began to weaken until its dissipation on July 30.[70]

Despite the storm not making landfall in the Philippines, Nesat enhanced the southwest monsoon which brought torrential rainfall over most of the country. As of August 3, the NDRRMC had reported a total of 247.58 million (US$4.9 million) worth of damages.[71] Total damages in Taiwan were counted to be NT$60.19 million (US$2.03 million).[72] Total damages in Mainland China were counted to be CNY 1.83 billion (US$271.6 million).[39] Typhoon Nesat was originally a Category 1, but was upgraded by the Joint Typhoon Warning Center into a minimal Category 2.

Tropical Storm Haitang (Huaning)

Шаблон:Infobox tropical cyclone small A low-pressure area over the northern portion of the South China Sea was upgraded to a tropical depression by the JMA early on July 27.[73] Despite an exposed LLCC with disorganized banding, the JTWC started initiating advisories, assigning the designation of 12W.[74] During the next day, the system had strengthened into a tropical storm, with the JMA naming it as Haitang, after ASCAT image depicted 40 knot winds over in the southern portion of the storm.[75] Due to the nearby Typhoon Nesat and moderate wind shear, Haitang maintained its intensity for several hours,[76] until on July 30 when the system had deepened and reached its peak intensity with 10-minute sustained winds of Шаблон:Convert with a minimum pressure of 985 hPa. Around the same time, Haitang entered the Philippine area of Responsibility, receiving the name Huaning by PAGASA,[77] although the system had left the area during 12:00 UTC of the same day.[78] Three hours later, the JTWC downgraded the system to a tropical depression,[79] though it was re-upgraded into a tropical storm six hours later.[80] By July 31, the JTWC issued their final advisory on Haitang after the system had made landfall over in the Pingtan County in Taiwan.[81] During 06:00 UTC of that day, the JMA issued their final advisory after Haitang weakened into a remnant low.[34]

Tropical Storm Nalgae

Шаблон:Infobox tropical cyclone small During July 31, the JMA started to monitor a tropical depression located about Шаблон:Convert to the northeast of Wake Island.[82] During the next day, the JTWC started issuing advisories and designated it as 13W.[83] By August 2, both agencies upgraded 13W to Tropical Storm Nalgae after imagery showed flaring convection and the storm was located in a region of low to moderate wind shear and warm SSTs.[84][85] Moving in a northward direction, Nalgae slowly intensified for several days. Nalgae reached its peak intensity with 10-minute sustained winds of Шаблон:Convert and a minimum barometric pressure of 988 hPa during August 5 for a brief time, as it was beginning to transition into an extratropical cyclone. The JTWC downgraded Nalgae to a tropical depression later that day and issued their final advisory after the storm was located in very unfavorable environments.[86] Шаблон:Cn span

Typhoon Banyan

Шаблон:Unreferenced section Шаблон:Cleanup rewrite Шаблон:Infobox tropical cyclone small Шаблон:Citation needed span

Typhoon Hato (Isang)

Шаблон:Infobox tropical cyclone small Шаблон:Main A low-pressure area developed into a tropical depression on August 19, while located to the southeast of Taiwan, and was named by PAGASA as Tropical Depression Isang. Over the next few days, Isang became a tropical storm, and was named Hato. Hato then became a severe tropical storm as it passed through the Batanes region of the Philippines, and the PAGASA later issued its final warning as Hato (named Isang) moved out of the Philippine Area of Responsibility.[87]

It gradually intensified and reached typhoon status on the afternoon of August 22 after entering the northeastern part of the South China Sea. On August 23, 07:00 HKT, Hato was approximately 100 km southeast of Hong Kong, bringing rain to the mainland as well as Hainan to the west. At 11:00 HKT the eye was approximately 60 km southwest of Hong Kong with the typhoon heading onto the mainland in a west-northwesterly direction.[88]

Hong Kong Observatory issued Hurricane Signal No. 10 at 09:10 HKT, August 23, the first time since 2012.[89] A total of 11 people were killed while total damage in Mainland China were counted to CN¥28.91 billion (US$4.34 billion).[39] No people were killed in Hong Kong, while estimated damage in Hong Kong amounted to HK$4 billion (US$511 million).[90] In Macau, losses of 12.50 billion patacas (US$1.55 billion) were incurred when high tides exacerbated flooding in most of the low-lying areas, inundating ground floor shops and businesses. There were 12 deaths as a result of the typhoon, including a number of people who drowned in flooded underground car-parks.[91] Despite making landfall in South China, Hato triggered floods in northern Vietnam and killed 1 person. The total damage by heavy rainfall in Bắc Kạn Province was 31 billion₫ (US$1.36 million).[92] In total, there were 24 deaths attributed to the typhoon.

Severe Tropical Storm Pakhar (Jolina)

Шаблон:Infobox tropical cyclone small Шаблон:Main On August 24, a tropical depression formed in the Philippine Sea and was named Jolina by PAGASA. On the next day, Jolina intensified into a tropical storm, and was named Pakhar. On August 26, Pakhar passed over the Philippines heading westward toward mainland China where it gathered strength into a severe tropical storm before making landfall in Tianshan on August 27, where after the previous monster storm Typhoon Hato hit days ago, they raised Signal #8 for Pakhar's arrival and landfall. Pakhar rapidly dissipated the next day.

A total of 83,000 people were affected by the storm, along with 14,000 people in which were evacuated over in the four main affected regions of Guandong, Guangxi, Guizhou and Yunnan.[93] One person died from a traffic incident while 62 were injured, while an additional two were confirmed hours later.[94]

Total economic losses in South China amounted to CN¥760 million (US$114.4 million) while a total of twelve people were killed in relation to the storm.[95] Moreover, damages in the Philippines were recorded at ₱41.27 million (US$808 thousand) and 2 billion (US$88,000) in Vietnam.[96][97]

Typhoon Sanvu

Шаблон:Infobox tropical cyclone small On August 27, the JMA began to monitor a tropical depression that had developed about Шаблон:Convert north-northeast of Saipan, although the system's nature was more of a monsoon depression.[98] The JTWC followed suit on the following day, designating the system as 17W.[99] Around the same time, the system had intensified into Tropical Storm Sanvu. By August 29, Sanvu increased in size, and therefore it prompted the JMA to upgrade it to a severe tropical storm. After moving in a westward direction, Sanvu stalled and entered a region of favorable conditions. As a ragged eye developed, both agencies upgraded Sanvu to a typhoon during August 31.[100] Sanvu reached its peak intensity on September 1 as a Category 2 typhoon.[101] Thereafter, the system steadily weakened as it started to move northwards with JTWC immediately downgrading the system to a tropical storm and issuing their final advisory late on September 2. The JMA still classified Sanvu as a typhoon until they issued their final advisory as the system had transitioned into an extratropical cyclone on September 3.

Sanvu did not cause any significant damage in the Northern Mariana Islands, though a 33-year-old woman drowned at Obyan beach in Saipan due to large waves on August 29.[102]

Severe Tropical Storm Mawar

Шаблон:Infobox tropical cyclone small On August 30, the JMA started to track a tropical depression to the north-northeast of Luzon, Philippines. Given the international designation of 18W by the JTWC,[103] the JMA upgraded the system immediately to Tropical Storm Mawar. Slowly organizing, convection had rapidly developed and Mawar strengthened into a severe tropical storm early on September 2. On September 3, Mawar had weakened to a tropical storm after environments started to become unfavorable due to high wind shear.[104] Later that day, Mawar weakened to a tropical depression and the JTWC issued their final advisory while making landfall over in Southeastern China between the cities of Shanwei and Shantou.[105][106] The JMA followed suit early on September 4 when Mawar had fully dissipated.

The China's National Meteorological Center (NMC) issued a blue alert for the southern parts of Guangdong on September 1.Шаблон:Citation needed During 2:00 a.m. local time on September 2, the Hong Kong Observatory issued a Tropical Cyclone Warning Signal No. 1 over in Hong Kong.[107] Chinese authorities activated a natural disaster alert and response to help local civil affairs departments in areas such as the provinces of Fujian and Guandong to prepare for relief work.[108] By September 3, the NMC had raised their warning signal to a yellow alert.[109] Flooding from Mavar was a major concern with reports of rainfall of up to Шаблон:Convert in some places which were impacted by Hato and Pakhar.[106] Total economic losses in South China were counted to be CNY 10 million (US$1.53 million).[39]

Tropical Storm Guchol (Kiko)

Шаблон:Infobox tropical cyclone small On September 3, the JMA started to track a tropical depression that had developed to the east of Luzon, Philippines. During the next day, the PAGASA initiated advisories and gave the local name Kiko,[110] while the JTWC followed suit by giving it the designation 19W.[111] However, due to increased wind shear along with an exposed circulation, the JTWC issued its final advisory on 03:00 UTC September 5.[112] Several hours later, deep convection was depicted and despite moderate to high shear, the JTWC re-initiated advisories,[113] while the JMA had upgraded the system to a tropical storm, naming it as Guchol early on the next day. On 21:00 UTC of that day, the JTWC stopped issuing warnings on the system after convection significantly weakened.[114] JMA later followed suit early on the next day by declaring it a remnant low as it neared Putian, Fujian on Strait of Taiwan.[34] Шаблон:Cn span

Typhoon Talim (Lannie)

Шаблон:Main Шаблон:Infobox tropical cyclone small A tropical depression formed east of Guam on September 7.[115] By the next day, the JTWC began issuing advisories on Tropical Depression 20W.[116] On September 9, 20W organized into a tropical storm, with the JMA naming the system as Talim.[117] With gradual intensification, the JMA upgraded Talim to a severe tropical storm. Talim further strengthened to a typhoon on September 11 where it simultaneously entered the PAR, with PAGASA naming it as Lannie.[118] The JTWC, however, delayed their upgrade until September 12.[119] Due to an ill-defined eye, Talim maintained its intensity until its eye became much clearer as rapid deepening ensued, as Talim became a Category 4 on September 14, and reached its peak intensity with 1-minute sustained winds of Шаблон:Convert.[120] Talim began to curve eastward as it rapidly weakened to a tropical storm thereafter, making landfall in Kyushu on September 17, with a path of heavy rainfall up to the region east of Tokyo.[121]

In Japan, 5 people were killed, and the agricultural loss were about JP¥32 billion (US$287.9 million).[122] Total damages across the country were counted to be US$750 million.[123]

Typhoon Doksuri (Maring)

Шаблон:Infobox tropical cyclone small Шаблон:Main On September 9, the Joint Typhoon Warning Center (JTWC) began monitoring on a tropical disturbance that had developed about Шаблон:Convert west-northwest of the province of Eastern Samar.[124] During the next day, the Japan Meteorological Agency (JMA) classified the system as a weak tropical depression. As the tropical cyclone is inside PAR, it was assigned the name "Maring".[125] On 21:00 UTC of September 11, the JTWC followed suit, giving the designation of 21W.[126] The JMA upgraded 21W to a tropical storm during September 12, giving the name Doksuri, the 19th named storm of the annual typhoon season.

Laguna was one of the provinces that got hit hard by the storm as the city was placed under a state of calamity after it had "too much rainfall" that produced further flash floods and landslides.[127]

As of September 19, the NDRRMC confirmed a total of 8 dead due to landslides and flooding while total damages were up to ₱267 million (US$5.24 million).[128]

On September 15, Typhoon Doksuri made landfall in Quảng Bình Province, Vietnam as a Category 3 typhoon. Doksuri killed 15 people so far in Vietnam while estimated damages were about ₫16.36 trillion (US$720 million).[129][130][131] Despite making landfall in Indochina, Doksuri affected Hainan and total economic losses were estimated to be CNY 100 million (US$15.3 million).[39]

Tropical Depression 22W (Nando)

Шаблон:Infobox tropical cyclone small Шаблон:Cn span

The China Observatory issued a "yellow" alert over in the eastern and southern regions due to rainstorms. Some areas have warned a possible precipitation of about Шаблон:Convert.[132] Typhoon Signal No. 1 was raised over in Hong Kong during September 24, with expected gusts of up to Шаблон:Convert including rough swells.[133] A voltage dip also occurred, causing 17 people to be trapped in lifts.[134] As the depression approached Vietnam on September 25, the Vietnam National Center for Hydro-Meteorological Forecasting of Vietnam forecast rainfall of about Шаблон:Convert in Hanoi and surrounding provinces, with rough waves up to Шаблон:Convert in Hạ Long Bay.[135]

Tropical Depression 23W

Шаблон:Infobox tropical cyclone small Шаблон:Main Early on October 7, a tropical depression formed to the west of the Philippines.[136]

Шаблон:Cn span

Tropical Depression 23W caused severe flooding over provinces of Northern and Central Vietnam. Roughly more than 700 houses have been destroyed, while rescue efforts have saved 28 people from the danger zone. In total, 100 people were killed, and damages were about 13 trillion₫ (US$572 million).[137][138] During October 10, the Red River was forecast to have waters exceed to the levels of Шаблон:Convert.[139][140] In Hoàng Long river (Ninh Bình Province) flooding was the most severe since 1985.[141]

Typhoon Khanun (Odette)

Шаблон:Infobox tropical cyclone small By October 11, the Japan Meteorological Agency upgraded a disturbance that was organizing in the Philippine Sea.[34] By 06:00 UTC on the following day, the Joint Typhoon Warning Center also upgraded the disturbance to a depression, designating it as "24W".[142] By 12:00 UTC the same day, the JMA officially upgraded the depression, naming it as "Khanun".[34] Two hours later, the PAGASA upgraded the depression, naming it "Odette".[143] Over the rest of the day, Khanun intensified under favorable conditions,[34][142] while approaching the northern parts of Luzon.[144] At 14:00 UTC (10:00 pm PHST), PAGASA upgraded "Odette" to a tropical storm while nearing landfall over Santa Ana, Cagayan.[145] The storm will make landfall on the place,[146] and emerged into the South China Sea, when it started re-intensifying under favorable conditions.[34][142][147] At 06:00 UTC, JMA upgraded Khanun into a severe tropical storm; the PAGASA would later follow suit, as "Odette" is also upgraded into a severe tropical storm.[34][148] At 14:00 UTC (10:00 pm PHST), PAGASA reported that Severe Tropical Storm "Odette" has exited their Philippine Area of Responsibility.[149]

Intensifying in the South China Sea, Khanun was upgraded to a typhoon by the JMA on October 14 at 12:00 UTC.[34] The JTWC would follow suit six hours later, upgrading the storm into a category 1 typhoon.[142] By the next day, JMA reported that Khanun reached its peak intensity with 135 km/h (75 knots) and a pressure of 955 hPa. The JTWC would follow suit three hours later with the winds of 165 km/h (90 knots) and a pressure of 965 hPa.[142] After its peak, Khanun immediately weakened under the influence of the northeast monsoon; at the time the storm made landfall over the Leizhou Peninsula, the system was barely at tropical storm intensity.[34][142][150] Both agencies would issue their last advisories on Khanun, as the storm weakened further while approaching the northern Vietnam.[34][142]

According to the NDRRMC, Khanun killed only one person, with total damages of ₱4.45 million (US$86,600).[151][152] Authorities in Hong Kong and Macau raised the number 8 tropical cyclone warning on October 15 as gale-force winds affected the region. In total, damages from Khanun in South China were counted to be CNY2.46 billion (US$373 million).[150]

Typhoon Lan (Paolo)

Шаблон:Infobox tropical cyclone small Шаблон:Main The United States Naval Research Laboratory (NRL) initially mentioned a tropical disturbance over Chuuk on October 11.[153] After the slow consolidation, the Joint Typhoon Warning Center (JTWC) issued a Tropical Cyclone Formation Alert to the elongated system early on October 14,[154] shortly after the Japan Meteorological Agency (JMA) started to monitor it as a low-pressure area.[155] The agency upgraded it to a tropical depression almost one day later and began to issue tropical cyclone warnings since 06:00 UTC on October 15.[156][157] In the afternoon, the JTWC also upgraded it to a tropical depression assigning the designation 25W, which formative but shallow convective bands had become more organized, and symmetrically wrapped into a defined low-level circulation center.[158] About three hours later, the JMA upgraded it to the twenty-first Northwest Pacific tropical storm in 2017 and assigned the international name Lan, when it was located approximately Шаблон:Convert to the northeast of Palau.[159] Early on October 16, the JTWC upgraded Lan to a tropical storm too, based on T-number 2.5 of the Dvorak technique,[160] shortly before it entered the Philippine Area of Responsibility and received the name Paolo from PAGASA.[161]

In Japan, 17 people were killed in Mainland Japan and the agricultural loss were about JP¥62.19 billion (US$547.9 million).[162] Total economic losses were counted to be US$2 billion.[123]

Tropical Depression 26W

Шаблон:Infobox tropical cyclone small Originating from an enhanced monsoon trough, a tropical disturbance developed just to the northwest of Palawan on October 17.[163] On October 18, the JTWC had issued a TCFA on the system.[164] By 21:00 UTC of that day, the JTWC began issuing advisories as they classified it as a tropical depression, assigning the identifier 26W.[165] This was due to deep convection found near the storm's center with formative banding, along with its location over in a favorable environment.[166] Initially, its forecast stated that 26W would intensify into a weak tropical storm, although due to a disorganized center with strong shear, the JTWC issued their final advisory on October 19 as it was being absorbed by the outflow of nearby Typhoon Lan.[167]

Associated with the rainbands of a nearby typhoon, 26W helped spread scattered rainfall throughout most of Visayas and northern Mindanao. Residents in some areas were alerted against possible flash floods and landslides.[168] 14 people were dead from heavy rainfall from the system and its precursor, and raised a state of calamity in Zamboanga City on October 23.[169][170]

Severe Tropical Storm Saola (Quedan)

Шаблон:Infobox tropical cyclone small A tropical depression formed north of Guam. The next day, the Tropical Depression transitioned into a Tropical Storm and the Japan Meteorological Agency named it Tropical Storm Saola. By evening of that day, Saola entered the Philippine Area of Responsibility (PAR). The PAGASA gave the local name "Quedan" to the storm. [171] On October 26, Saola strengthened into a severe tropical storm at 08:00 UTC as it moved slowly in a northwestward heading. Its intensity did not change, even as high wind shear occurred to the north of Saola and the strengthening northeast monsoon while heading to Japan. It left PAR two days later. The system continued to track northeastward and made several landfalls and close approaches over the islands of Ryukyu Arc.[172] It started weakening while in cold waters and brought rains to Southern Japan but did not make landfall. It later transitioned into an extratropical cyclone before it dissipated near the Chiba Prefecture.

Although Saola didn't make landfall, damages were totaled up to US$250 million.

Tropical Depression 29W

Шаблон:Infobox tropical cyclone small The JMA upgraded a low-pressure area to a tropical depression over the southern portion of the South China Sea, on October 30.[173] The JTWC issued a TCFA during the next day as it gathered strength. Initially forecast to intensify to a tropical storm, the system rapidly deteriorated and degenerated to a remnant low on November 3 as it tracked into the Gulf of Thailand.[174] Over in the course of two days, after re-curving back to the gulf, the JTWC re-issued a TCFA.[175] By November 6, the JTWC classified the system as Tropical Depression 29W.[176] On November 8, 29W made landfall over the Malay Peninsula, before dissipating soon afterward.

Tropical Depression 29W caused unusually heavy rains and flash floods to occur in the state of Penang, killing 7 people.[177] Flood waters in parts of the city reached Шаблон:Convert, submerging entire homes.

Typhoon Damrey (Ramil)

Шаблон:Infobox tropical cyclone small Шаблон:Main The JMA upgraded a low-pressure area to a tropical depression east of Visayas on October 31. PAGASA gave warnings to the system and named it Ramil. The storm brought rainy weather on the All Saints's Day (November 1) to Visayas. The tropical depression made landfall over Busuanga, Palawan at midnight on November 1. On November 2, Ramil strengthened, and the JTWC and JMA upgraded Ramil to a tropical storm, and gave the system the international name Damrey.[178]

Torrential rains caused by the storm resulted in 2.5 ft of deep flooding, damaging agricultural crops. Agricultural damages were totaled to Php1.03 million (US$20,000) over in the city of Aurora Quezon on November 4.[179]

Strong winds, heavy rainfall and severe flooding in Central Vietnam caused by the typhoon. Total damage reached over 22 trillion VND (US$1 billion).[180] Damrey made landfall in central Vietnam as the region hosted the 2017 APEC Summit in Da Nang.

As of November 8, a total of 112 people were confirmed dead due to the storm.[181][182]

Tropical Storm Haikui (Salome)

Шаблон:Infobox tropical cyclone small Шаблон:Main A Tropical Depression formed over Samar on November 9, and PAGASA gave the name Salome to the system. Salome damaged boats in Sorsogon with large waves. On the next day, after Salome made landfall, the system intensified into a tropical storm, and the JMA gave the international name Haikui to the system. Haikui dropped heavy rainfall over Southern Luzon and Visayas.[183] It landfalled in Batangas before midnight and passed the boundary of Batangas and Cavite at 11:00 in that evening. It dissipated on Vietnam on November 13, 2017.

In China, Haikui produced heavy, sustained rain in the island province of Hainan, China. Flooding was recorded in several locations on the east side of the province. In the capital Haikou, flooding caused road closure. [184][185]

No casualties were reported, though damages were totaled up to ₱218.5 million (US$4.26 million). In addition, only five houses were fully damaged in Dipaculao, Aurora.[186]

Tropical Storm Kirogi (Tino)

Шаблон:Infobox tropical cyclone small Шаблон:Main On November 16, a tropical Depression formed on Sulu Sea, with the PAGASA naming it Tino. At midnight on the same day, the system made landfall on Puerto Princesa.[187] At about that time, the system intensified into a tropical storm, receiving the international name Kirogi by the JMA.

Kirogi caused flooding in the Philippines and Vietnam, with trees and power poles toppling in Ho Chi Minh City. Eight people were killed in Vietnam.

Several barangays in Mansalay were affected by floodwaters Шаблон:Convert deep; San Vicente received floods Шаблон:Convert deep. Three houses were damaged in Palawan; ports in Puerto Princesa, Coron, Palawan, Cuyo, Palawan, El Nido, Palawan, and Brooke's Point temporarily suspended operations, stranding 243 passengers. A total of 497 people were affected as a result of the storm.[188]

Total economic losses in Vietnam were amounted to be US$10 million.[189] The remnant energy of Tropical Storm Kirogi eventually contributed to the formation of Very Severe Cyclonic Storm Ockhi in the North Indian Ocean.[190][191]

Tropical Storm Kai-tak (Urduja)

Шаблон:Infobox tropical cyclone small Шаблон:Main A low-pressure area developed into a tropical depression east of Mindanao late on December 11, and the JMA began to issue tropical cyclone warnings early on the next day.[192] It entered the Philippine Area of Responsibility nine hours later, receiving the name Urduja[193] On 21:00 UTC of that same day, the JTWC upgraded the system to a tropical depression and also began issuing advisories, giving the identifier 32W.[194] Despite the system being poorly organized with loose banding, the system also was located in an area of very low wind shear.[195] Three hours later, the JMA upgraded the system to a tropical storm, assigning it the international name Kai-tak.[196]

The city of Tacloban was later placed under a state of calamity as decided by their local council as 80 of the 130 villages were flooded. This resulted in at least 728 families (1,418 individuals) brought to evacuation centers or schools.[197]

The NDRRMC confirmed a total of 83 people dead and calculated a total of ₱3.747 billion (US$74.3 million) worth of infrastructure and agricultural damages.[198][123]

Typhoon Tembin (Vinta)

Шаблон:Main Шаблон:Infobox tropical cyclone small During December 16, the JMA reported that a tropical depression had developed about Шаблон:Convert to the southeast of Guam, before they reclassified it as an area of low pressure during the following day.[199][200][201] Over the next few days, the system moved gradually north-westwards in favourable conditions, before it was reclassified as a tropical depression by the JMA during December 20, while it was located to the northeast of Palau.[34][202] During that day, the JTWC and PAGASA also classified the system as a tropical depression with the latter naming it as Vinta, before the JMA named the system Tembin as it had developed into a tropical storm.[203][204][205]

After the storm, on December 25, two towns in Zamboanga del Norte were under a state of calamity because of the flooding caused by the storm, which also made several roads and bridges impassible as they were covered in mud.[206]

Rough waves caused by Tembin sank a ferry on December 22, killing five people.[207] An additional 261 people were also killed due to flooding in Mindanao, of which 135 were reported in the province of Lanao del Norte.[208] Estimated damages are around ₱2.1 billion (US$42 million).[209]

Other systems

On March 19, a tropical depression formed close to the northeast of Mindanao, Philippines, and dissipated over the Sibuyan Sea two days later.[210][211] Early on June 29, the JMA initiated advisories on a newly formed tropical depression located about Шаблон:Convert south of Okinawa Island.[212] The system re-curved and started moving in a northeastward direction until it dissipated to the southwest of Tokyo on July 1.[213] Early on July 4, the JMA indicated that a tropical depression had formed about Шаблон:Convert south of Okinotorishima.[214] During the next day, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system, although it was canceled several hours later.[215] After moving northward, the depression rapidly weakened as it was absorbed by a stationary front on July 7.[216]

Early on July 13, the JMA reported that a non-tropical low had transitioned into a tropical depression about Шаблон:Convert north-northeast of Iwo Jima.[217] The depression moved in a generally northeasterly direction until weakening to a low-pressure area by 06:00 UTC on July 16.[218] A tropical depression formed about Шаблон:Convert northeast of Wake Island late on July 25, though the JTWC indicated it as a subtropical system with estimated recorded winds of Шаблон:Convert.[219][220] After several days, the system had already transitioned into an extratropical cyclone on July 29, without becoming a tropical storm.[221] Early on August 25 the JMA started to track a tropical depression over in the South China Sea,[222] although it was last monitored during the next day when it was absorbed by the outflow of Tropical Storm Pakhar.[223] On August 28, the JMA started to issue advisories on a tropical depression that had developed about Шаблон:Convert east-northeast of Tuguegarao City.[224] The JMA predicted that the system would become a tropical storm within the next 24 hours, although because the system did not develop further, the JMA issued their final advisory on 03:00 UTC of August 29 when the system had weakened into a low-pressure area.[225] The remnants of the system helped with formation of Tropical Storm Mawar.[226] On December 29, a weak tropical depression formed south-southwest of Palau. The system later strengthened into Tropical Storm Bolaven during the following year.

Storm names

Шаблон:See also Within the Northwest Pacific Ocean, both the Japan Meteorological Agency (JMA) and PAGASA assign names to tropical cyclones that develop in the Western Pacific, which can result in a tropical cyclone having two names.[227] 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 Шаблон:Convert.[228] PAGASA assigns names to tropical cyclones which move into or form as a tropical depression in their area of responsibility located between 135°E–115°E and between 5°N–25°N even if the cyclone has had an international name assigned to it.[227] The names of significant tropical cyclones are retired, by both PAGASA and the Typhoon Committee.[228] 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 Шаблон:Tcname unused.

International names

Шаблон:Main During the season 27 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 Шаблон:Convert. 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.[229] During the season, the names Hato and Lan were used for the first time (only time in the case of Hato), after they had replaced the names Washi and Vicente, which were retired after the 2011 and 2012 seasons, respectively.

Muifa Merbok Nanmadol Talas Noru Kulap Roke Sonca Nesat Haitang Nalgae Banyan Hato Pakhar
Sanvu Mawar Guchol Talim Doksuri Khanun Lan Saola Damrey Haikui Kirogi Kai-tak Tembin

Retirement

After the season the Typhoon Committee retired the names Hato, Kai-tak and Tembin 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 2019, they were replaced with Yamaneko, Yun-yeung and Koinu, respectively.[230]

Philippines

Шаблон:Main

Auring Bising Crising Dante Emong
Fabian Gorio Huaning Isang Jolina
Kiko Lannie Maring Nando Odette
Paolo Quedan Ramil Salome Tino
Urduja Vinta Шаблон:Tcname unused Шаблон:Tcname unused Шаблон:Tcname unused
Auxiliary list
Шаблон:Tcname unused Шаблон:Tcname unused Шаблон:Tcname unused Шаблон:Tcname unused Шаблон:Tcname unused
Шаблон:Tcname unused Шаблон:Tcname unused Шаблон:Tcname unused Шаблон:Tcname unused Шаблон:Tcname 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.[231][232] The names were taken from a list of names, that was last used during the 2013 season and was used again during the 2021 season.[231] All of the names are the same except for Lannie, Salome and Yasmin, which replaced the names Labuyo, Santi and Yolanda after they were retired.[231] The names Lannie and Salome were used for the first time this year.

Retirement

On December 21, PAGASA announced that it would remove the names Urduja and Vinta from their naming lists after they caused over 1 billion in damage.[233] They were replaced with Uwan and Verbena in 2021.[234]

Season effects

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

Шаблон:Pacific areas affected (Top)

|- | 01W (Auring) || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Philippines, Vietnam, Cambodia || Шаблон:Ntsp || Шаблон:Nts || [15][16] |- | Bising || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || None || Шаблон:Ntsh None || None || |- | TD || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Philippines || Шаблон:Ntsh None || None || |- | 02W (Crising) || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Philippines, Taiwan || Шаблон:Ntsp || Шаблон:Nts || [32][33] |- | Muifa (Dante) || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || None || Шаблон:Ntsh None || None || |- | Merbok || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Philippines, South China[nb 1] || Шаблон:Ntsp || None || [39] |- | TD || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Japan || Шаблон:Ntsh None || None || |- | Nanmadol (Emong) || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Japan || Шаблон:Ntsp || Шаблон:Nts || [45] |- | TD || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Taiwan, Ryukyu Islands || Шаблон:Ntsh None || None || |- | TD || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || None || Шаблон:Ntsh None || None || |- | Talas || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Hainan, Indochina[nb 2] || Шаблон:Ntsp || Шаблон:Nts || [235][236]
[50][237][39] |- | Noru || Шаблон:Sort || bgcolor=#Шаблон:Storm colour | Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Japan || Шаблон:Ntsp || 2 || [52] |- | Kulap || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || None || Шаблон:Ntsh None || None || |- | Sonca || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Hainan, Indochina || Шаблон:Ntsp || 37 || [238][239]
[240][241]
[242][243] |- | Roke (Fabian) || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Philippines, Taiwan, South China || Шаблон:Ntsh None || None || |- | Nesat (Gorio) || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Philippines, Ryukyu Islands, Taiwan, East China || Шаблон:Ntsp || 3 || [71][72][244][39] |- | TD || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || None || Шаблон:Ntsh None || None || |- | Haitang (Huaning) || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Taiwan, East China || Шаблон:Ntsp || None || [72][245] |- | Nalgae || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || None || Шаблон:Ntsh None || None || |- | Banyan || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || None || None || None || |- | Hato (Isang) || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Philippines, Taiwan, South China, Vietnam ||Шаблон:Ntsp || 24 || [39][90][91][92] |- | Pakhar (Jolina) || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Philippines, South China, Vietnam, Thailand || Шаблон:Ntsp || 13 || [39][96][97][123] |- | TD || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Vietnam || Шаблон:Ntsh None || None || |- | Sanvu || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Mariana Islands, Ogasawara Islands || Шаблон:Ntsh Unknown || 1 || [102] |- | TD || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Philippines || Шаблон:Ntsh None || None || |- | Mawar || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Philippines, South China || Шаблон:Ntsp || None || [39] |- | Guchol (Kiko) || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Philippines, Taiwan, East China || Шаблон:Ntsh None || None || |- | Talim (Lannie) || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Mariana Islands, Taiwan, East China, Japan || Шаблон:Ntsp || 5 || [123] |- | Doksuri (Maring) || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Philippines, Hainan, Indochina, Bangladesh || Шаблон:Ntsp || 29 ||[128][129][130][131][246][39][237] |- | 22W (Nando) || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Philippines, South China, Vietnam || Шаблон:Ntsh Minimal || None || |- | 23W || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Philippines, Hainan, Indochina || Шаблон:Ntsp || 91 || [247][248][237] |- | Khanun (Odette) || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Philippines, Taiwan, South China, Vietnam || Шаблон:Ntsp || 1 || [39][249] |- | Lan (Paolo) || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Caroline Islands, Philippines, Japan || Шаблон:Ntsp || 17 || [123] |- | 26W || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Philippines || Minimal || 14 || [170] |- | Saola (Quedan)|| Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Caroline Islands, Japan || Шаблон:Ntsp || None || [123] |- | 29W || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Vietnam, Cambodia, Thailand, Malaysia || Minimal || 7 || [177] |- | Damrey (Ramil) || Шаблон:Sort || bgcolor=#Шаблон:Storm color|Шаблон:Sort || bgcolor=#Шаблон:Storm color|Шаблон:Sort || bgcolor=#Шаблон:Storm color|Шаблон:Sort || Philippines, Vietnam, Cambodia || Шаблон:Ntsp || 115 || [180][250][251][237] |- | Haikui (Salome) || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Philippines, South China, Vietnam || Шаблон:Ntsp || None || [186] |- | Kirogi (Tino) || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Philippines, Malaysia, Indochina || Шаблон:Ntsp || 8 || [189] |- | Kai-tak (Urduja) || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Philippines, Malaysia, Vietnam || Шаблон:Ntsp || 83 || [198] |- | Tembin (Vinta) || Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || bgcolor=#Шаблон:Storm colour|Шаблон:Sort || Caroline Islands, Philippines, Malaysia, Vietnam || Шаблон:Ntsp || 266 || [207][208][209] |- Шаблон:TC Areas affected (Bottom)

See also

Шаблон:Portal

Notes

Шаблон:Reflist

References

Шаблон:Reflist

External links

Шаблон:S-start Шаблон:Succession box Шаблон:S-end Шаблон:Commons category Шаблон:WPAC EL's

Шаблон:2017 Pacific typhoon season buttons Шаблон:TC Decades Шаблон:Tropical cyclone season

  1. 1,0 1,1 1,2 Шаблон:Cite report
  2. 2,0 2,1 Шаблон:Cite report
  3. 3,0 3,1 Шаблон:Cite report
  4. 4,0 4,1 4,2 4,3 Шаблон:Cite report
  5. 5,0 5,1 Шаблон:Cite press releaseШаблон:Dead link
  6. 6,0 6,1 Шаблон:CitationШаблон:Cite report
  7. Шаблон:Cite web
  8. Шаблон:Cite web
  9. Шаблон:Cite web
  10. https://www.webcitation.org/6nLHT1u8P?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201701070000.htm Шаблон:Dead link
  11. Шаблон:Cite web
  12. Шаблон:Cite web
  13. Шаблон:Cite web
  14. Шаблон:Cite web
  15. 15,0 15,1 Шаблон:Cite web
  16. 16,0 16,1 Шаблон:Cite web
  17. Шаблон:Cite web
  18. Шаблон:Cite reportШаблон:Dead link
  19. Шаблон:Cite news
  20. Шаблон:Cite report
  21. Шаблон:Cite report
  22. Шаблон:Cite reportШаблон:Dead link
  23. Шаблон:Cite web
  24. 24,0 24,1 24,2 24,3 24,4 Шаблон:Cite web
  25. Шаблон:Cite report
  26. Шаблон:Cite news
  27. Шаблон:Cite reportШаблон:Dead link
  28. Шаблон:Cite reportШаблон:Dead link
  29. Шаблон:Cite reportШаблон:Dead link
  30. Шаблон:Cite reportШаблон:Dead link
  31. Шаблон:Cite web
  32. 32,0 32,1 Шаблон:Cite web
  33. 33,0 33,1 Шаблон:Cite web
  34. 34,00 34,01 34,02 34,03 34,04 34,05 34,06 34,07 34,08 34,09 34,10 34,11 34,12 34,13 34,14 34,15 34,16 34,17 34,18 34,19 34,20 34,21 34,22 34,23 34,24 34,25 34,26 34,27 Шаблон:Cite web
  35. Шаблон:Cite web
  36. Шаблон:Cite web
  37. 37,0 37,1 37,2 Шаблон:Cite web
  38. Шаблон:Cite web
  39. 39,00 39,01 39,02 39,03 39,04 39,05 39,06 39,07 39,08 39,09 39,10 39,11 39,12 39,13 Шаблон:Cite conference
  40. 40,0 40,1 40,2 40,3 40,4 40,5 Шаблон:Cite web
  41. Шаблон:Cite web
  42. 42,0 42,1 Шаблон:Cite news
  43. 43,0 43,1 Шаблон:Cite news
  44. Шаблон:Cite news
  45. 45,0 45,1 Шаблон:Cite web
  46. Шаблон:Cite web
  47. Шаблон:Cite web
  48. Шаблон:Cite web
  49. Шаблон:Cite news
  50. 50,0 50,1 Шаблон:Cite news
  51. Шаблон:Cite web
  52. 52,0 52,1 Шаблон:Cite web
  53. https://www.webcitation.org/6s5rpCQiO?url=http://gwydir.demon.co.uk/advisories/ABPW10-PGTW_201707200600.htm Шаблон:Dead link
  54. Шаблон:Cite web
  55. Шаблон:Cite web
  56. Шаблон:Cite web
  57. Шаблон:Cite web
  58. Шаблон:Cite web
  59. Шаблон:Cite web
  60. Шаблон:Cite web
  61. Шаблон:Cite web
  62. Шаблон:Cite news
  63. Шаблон:Cite web
  64. Шаблон:Cite web
  65. 65,0 65,1 65,2 65,3 Шаблон:Cite web
  66. Шаблон:Cite web
  67. 67,0 67,1 Шаблон:Cite web
  68. Шаблон:Cite news
  69. Шаблон:Cite news
  70. Шаблон:Cite web
  71. 71,0 71,1 Шаблон:Cite webШаблон:Dead link
  72. 72,0 72,1 72,2 Шаблон:Cite web
  73. Шаблон:Cite web
  74. Шаблон:Cite web
  75. Шаблон:Cite web
  76. Шаблон:Cite web
  77. Шаблон:Cite web
  78. Шаблон:Cite webШаблон:Dead link
  79. Шаблон:Cite web
  80. Шаблон:Cite web
  81. Шаблон:Cite web
  82. https://www.webcitation.org/6sNNNO3wi?url=http://gwydir.demon.co.uk/advisories/ABPW10-PGTW_201707311400.htm Шаблон:Dead link
  83. Шаблон:Cite web
  84. Шаблон:Cite web
  85. Шаблон:Cite web
  86. Шаблон:Cite web
  87. Шаблон:Cite web
  88. Шаблон:Cite web
  89. Шаблон:Cite web
  90. 90,0 90,1 Шаблон:Cite news
  91. 91,0 91,1 Шаблон:Cite news
  92. 92,0 92,1 Шаблон:Cite web
  93. Шаблон:Cite web
  94. Шаблон:Cite web
  95. Шаблон:Cite web
  96. 96,0 96,1 Шаблон:Cite web
  97. 97,0 97,1 Шаблон:Cite web
  98. Шаблон:Cite web
  99. Шаблон:Cite web
  100. Шаблон:Cite web
  101. Шаблон:Cite web
  102. 102,0 102,1 Шаблон:Cite web
  103. Шаблон:Cite web
  104. Шаблон:Cite web
  105. Шаблон:Cite web
  106. 106,0 106,1 Шаблон:Cite web
  107. Шаблон:Cite web
  108. Шаблон:Cite web
  109. Шаблон:Cite web
  110. Шаблон:Cite web
  111. Шаблон:Cite web
  112. Шаблон:Cite web
  113. Шаблон:Cite web
  114. Шаблон:Cite web
  115. Шаблон:Cite web
  116. Шаблон:Cite web
  117. Шаблон:Cite web
  118. Шаблон:Cite web
  119. Шаблон:Cite web
  120. Шаблон:Cite web
  121. Шаблон:Cite web
  122. Шаблон:Cite web
  123. 123,0 123,1 123,2 123,3 123,4 123,5 123,6 Шаблон:Cite web
  124. Шаблон:Cite web
  125. https://www.webcitation.org/6tPDwn36b?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201709101800.htm Шаблон:Dead link
  126. Шаблон:Cite web
  127. Шаблон:Cite web
  128. 128,0 128,1 Шаблон:Cite web
  129. 129,0 129,1 Шаблон:Cite web
  130. 130,0 130,1 Шаблон:Cite web
  131. 131,0 131,1 Шаблон:Cite web
  132. Шаблон:Cite web
  133. Шаблон:Cite web
  134. Шаблон:Cite web
  135. Шаблон:Cite web
  136. Шаблон:Cite web
  137. Шаблон:Cite web
  138. Шаблон:Cite web
  139. Шаблон:Cite web
  140. Шаблон:Cite web
  141. Шаблон:Cite web
  142. 142,0 142,1 142,2 142,3 142,4 142,5 142,6 Шаблон:Cite web
  143. Шаблон:Cite report
  144. Шаблон:Cite report
  145. Шаблон:Cite report
  146. Шаблон:Cite report
  147. Шаблон:Cite report
  148. Шаблон:Cite report
  149. Шаблон:Cite report
  150. 150,0 150,1 Шаблон:Cite web
  151. Шаблон:Cite report
  152. Шаблон:Cite news
  153. Шаблон:Cite web
  154. Шаблон:Cite web
  155. Шаблон:Cite web
  156. Шаблон:Cite web
  157. Шаблон:Cite web
  158. Шаблон:Cite web
  159. Шаблон:Cite web
  160. Шаблон:Cite web
  161. Шаблон:Cite web
  162. Шаблон:Cite web
  163. Шаблон:Cite web
  164. https://www.webcitation.org/6uJRdQBON?url=http://gwydir.demon.co.uk/advisories/WTPN21-PGTW_201710180830.htm Шаблон:Dead link
  165. Шаблон:Cite web
  166. Шаблон:Cite web
  167. Шаблон:Cite web
  168. Шаблон:Cite web
  169. Шаблон:Cite web
  170. 170,0 170,1 Шаблон:Cite web
  171. Шаблон:Cite web
  172. Шаблон:Cite web
  173. Шаблон:Cite web
  174. https://www.webcitation.org/6uhDPPetI?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201711030000.htm Шаблон:Dead link
  175. https://www.webcitation.org/6ukQtwtjp?url=http://gwydir.demon.co.uk/advisories/WTPN21-PGTW_201711050730.htm Шаблон:Dead link
  176. Шаблон:Cite web
  177. 177,0 177,1 Шаблон:Cite web
  178. Шаблон:Cite web
  179. Шаблон:Cite web
  180. 180,0 180,1 Шаблон:Cite web
  181. Шаблон:Cite news
  182. Шаблон:Cite news
  183. Шаблон:Cite web
  184. Шаблон:Cite web
  185. Шаблон:Cite web
  186. 186,0 186,1 Шаблон:Cite webШаблон:Cbignore
  187. Шаблон:Cite web
  188. Preparedness, Measures and Effects of Tropical Storm Tinondrrmc.gov.ph Шаблон:Webarchive
  189. 189,0 189,1 Шаблон:Cite web
  190. Шаблон:Cite web
  191. Шаблон:Cite web
  192. Шаблон:Cite web
  193. Шаблон:Cite web
  194. Шаблон:Cite web
  195. Шаблон:Cite web
  196. Шаблон:Cite web
  197. Шаблон:Cite web
  198. 198,0 198,1 Шаблон:Cite web
  199. Шаблон:Cite web
  200. Шаблон:Cite web
  201. Шаблон:Cite web
  202. Шаблон:Cite web
  203. Шаблон:Cite web
  204. Шаблон:Cite web
  205. Шаблон:Cite web
  206. Шаблон:Cite webШаблон:Dead link
  207. 207,0 207,1 Шаблон:Cite web
  208. 208,0 208,1 Шаблон:Cite web
  209. 209,0 209,1 Шаблон:Cite web
  210. Шаблон:Cite web
  211. Шаблон:Cite web
  212. Шаблон:Cite web
  213. https://www.webcitation.org/6rcq7wf0F?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201707010000.htm Шаблон:Dead link
  214. Шаблон:Cite web
  215. https://www.webcitation.org/6rm7A74CM?url=http://gwydir.demon.co.uk/advisories/WTPN21-PGTW_201707051900.htm Шаблон:Dead link
  216. https://www.webcitation.org/6rm7GJy1q?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201707070000.htm Шаблон:Dead link
  217. Шаблон:Cite web
  218. Шаблон:Cite web
  219. Шаблон:Cite web
  220. https://www.webcitation.org/6sIiPiGm6?url=http://gwydir.demon.co.uk/advisories/ABPW10-PGTW_201707261400.htm
  221. Шаблон:Cite web
  222. Шаблон:Cite web
  223. Шаблон:Cite web
  224. Шаблон:Cite web
  225. Шаблон:Cite web
  226. Шаблон:Cite web
  227. 227,0 227,1 Шаблон:Cite web
  228. 228,0 228,1 Шаблон:Cite web
  229. Шаблон:Cite journal
  230. Шаблон:Cite web
  231. 231,0 231,1 231,2 Шаблон:Cite web
  232. Шаблон:Cite news
  233. Шаблон:Cite web
  234. Шаблон:Cite web
  235. Шаблон:Cite web
  236. Шаблон:Cite web
  237. 237,0 237,1 237,2 237,3 Шаблон:Cite web
  238. Шаблон:Cite web
  239. Шаблон:Cite news
  240. Шаблон:Cite web
  241. Шаблон:Cite web
  242. Шаблон:Cite news
  243. Шаблон:Cite webШаблон:Dead link
  244. Шаблон:Cite web
  245. Шаблон:Cite web
  246. Шаблон:Cite web
  247. Шаблон:Cite web
  248. Шаблон:Cite web
  249. Шаблон:Cite web
  250. Шаблон:Cite web
  251. Шаблон:Cite web


Ошибка цитирования Для существующих тегов <ref> группы «nb» не найдено соответствующего тега <references group="nb"/>