The 2016 Pacific typhoon season is considered to have been the fourth-latest start for a Pacific typhoon season since reliable records began. It was an average season, with a total of 26 named storms, 13 typhoons, and six super typhoons. The season ran throughout 2016, though typically most tropical cyclones develop between May and October. The season's first named storm, Nepartak, developed on July 3, while the season's last named storm, Nock-ten, dissipated on December 28.
The development of Nepartak made the second-latest time within a season for the first named storm to develop and ended a 199-day period (from December 17, 2015 – July 3, 2016) during which no named storm was active in the basin. Tropical Storm Mirinae reached peak intensity while making landfall over the Red River Delta, causing very severe damage in Northern Vietnam. By the end of August, three storms had hit the Japanese island of Hokkaidō, the most since 1951. In September, Typhoon Meranti reached peak intensity with a minimum pressure of 890 hPa, becoming one of the most intense tropical cyclones on record. Typhoon Chaba became the strongest typhoon to strike South Korea since 2012. Tropical Storm Aere and a tropical depression brought the worst flooding in Vietnam since 2011. The last storm of the season, Typhoon Nock-ten, became the strongest tropical cyclone ever recorded worldwide on Christmas Day (December 25) since at least 1960, in terms of 1-minute maximum sustained winds.
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] will name 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 the Philippine Area of Responsibility (PAR) located between 135°E and 115°E and between 5°N–25°N regardless of whether or not a tropical cyclone has already been given a name by the JMA. Tropical depressions that are monitored by the United States' Joint Typhoon Warning Center (JTWC)[nb 3][nb 1] 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. Some of the forecasts took into consideration what happened in previous seasons and the El Niño conditions that were observed during the previous year. The first forecast of the year was released by PAGASA during January 2016, within its seasonal climate outlook for the period January – June.[6] The outlook noted that one to two tropical cyclones were expected between January and March, while one to three were expected to develop or enter the Philippine Area of Responsibility between April and June.[6]
During March the Hong Kong Observatory predicted that the typhoon season in Hong Kong would be near-normal, with four to seven tropical cyclones passing within 500 km (310 mi) of the territory compared to an average of six,[10] which was revised to five to eight tropical cyclones in August. On May 7, Tropical Storm Risk issued its first forecast for the season and predicted that it will be a quiet season, with 22 tropical storms, 13 typhoons, and 6 intense typhoons developing during the year, while an ACE Index of 217 was also forecast.[3] Ahead of the Thailand rainy season starting during May, the Thai Meteorological Department predicted that two tropical cyclones would move near Thailand during 2016.[11] They predicted that there was a high chance that the first tropical cyclone would move past northern and north-eastern Thailand during August or September.[11] The second tropical cyclone was predicted to move past Southern Thailand during October and November.[11] On June 28, Taiwan's Central Weather Bureau predicted that between 19 and 23 tropical storms would develop over the basin, while two — four systems were expected to affect Taiwan itself.[7]
On July 6, TSR released their second forecast for the season. They predicted mostly the same numbers as the previous forecast, but raised the number of intense typhoons to 7.[4] PAGASA issued their second and final forecast for the year on July 15, within its seasonal climate outlook for the period July – December.[8] The outlook noted that between five and eleven tropical cyclones were expected between July and September, while four to nine were expected to develop or enter the Philippine Area of Responsibility between October and December.[8] TSR issued their final forecast for the season on August 8, sustaining the tropical cyclone numbers, however its ACE was slightly lowered than the previous forecast.[5]
A trio of storms southeast of Japan on August 20; Lionrock (left), Mindulle (bottom-left) and Kompasu (top)
Despite the season's late start, the 2016 season was a normal and active season with a total of 53 tropical depressions, of which 26 became tropical storms. After five months of inactivity, the first tropical depression developed on May 26, making it the fifth-latest season for a system to form. According to existing records only four other seasons started later—the 1973, 1983, 1984, and 1998 seasons. Tropical activity throughout the basin became marginally favorable for development, and two tropical depressions developed during June. On July 3, Nepartak became the first named tropical storm, making it the second-latest first named storm on record. Nepartak's naming ended a 199-day period (from December 17, 2015, to July 2, 2016) during which no named storm was active within the basin; this period tied the 199-day period from December 22, 1997, to July 8, 1998.[12] Nepartak reached Category 5 super typhoon intensity before making landfall in Taiwan and East China, causing a total of US$1.52 billion of damage. In late July, Tropical Storm Mirinae reached its peak intensity while making landfall over Red River Delta in Northern Vietnam. The storm caused a total of US$334 million of damage[nb 4] in Hainan and Vietnam. Later, Nida reached near typhoon strength; it affected the Philippines, South China and Vietnam, but its damage was lower than that of Mirinae. The season became more active in August, with 7 named storms. Except Dianmu, which affected South China, Indochina, all of the tropical cyclones in August affected Japan and the Russian Far East. By the end of August, three storms (Chanthu, Lionrock and Kompasu) had hit the Japanese island of Hokkaidō, the most since 1951.[13] Lionrock was a large, powerful, long-lived and erratic tropical cyclone which caused significant flooding and casualties in North Korea and Japan in late August.
Three storms active during September 13: Rai (left), Meranti (center) and Malakas (right)
In September, Typhoon Meranti became the strongest typhoon in terms of pressure since Typhoon Megi in 2010, as well as the strongest typhoon in terms of sustained winds since Typhoon Haiyan in 2013, and the second-strongest tropical cyclone worldwide in 2016, only behind Cyclone Winston, in terms of pressure. Typhoon Megi reached its peak intensity as a Category 3 typhoon while making landfall over Taiwan. Both Meranti and Megi made landfall in Fujian, China, and they caused a total of US$3.6 billion of damage. Rai became a weak tropical storm before it made landfall in Vietnam, Laos and Thailand in mid-September, causing flooding and moderate damage. Typhoon Malakas impacted Japan with a total of nearly $740 million of damage as a Category 4 typhoon. In late September and early October, Typhoon Chaba reached Category 5 super typhoon intensity and became the strongest tropical cyclone to make landfall in South Korea since Sanba in 2012. Chaba also caused 7 deaths in the country.[14]A tropical depression formed east of the International Date Line on October 3, and entered the basin before developing into Typhoon Songda. Songda struck the Pacific Northwest region of the United States and Canada as a powerful extratropical cyclone.[15]Severe Tropical Storm Aere affected parts of Southeast Asia in mid-October, including the worst flooding in Vietnam since 2010, causing a total of US$209 million of damage.[16][17] Later, Typhoon Sarika became a powerful typhoon, and affected the Philippines, China and Vietnam, causing severe damage as well as severe flooding in southern China. After Sarika, Typhoon Haima reached Category 5 super typhoon strength before impacting the Philippines and China, causing a total of US$1.93 billion in damages. Haima was the most severe tropical cyclone to affect Hong Kong in October since 1995. In early November, a tropical depression made landfall in Southern Vietnam and caused heavy flooding throughout central and southern Vietnam, causing moderate damage. In late December, Nock-ten became the strongest Christmas tropical cyclone on record anywhere in the world since at least 1960 in terms of 1-minute sustained winds, before impacting the Philippines.[18][19]
The Accumulated Cyclone Energy (ACE) index for the 2016 Pacific typhoon season as calculated by Colorado State University using data from the Joint Typhoon Warning Center was 261.9 units.[20] Broadly speaking, ACE is a measure of the power of a tropical or subtropical storm multiplied by the length of time it existed. It is only calculated for full advisories on specific tropical and subtropical systems reaching or exceeding wind speeds of 39 miles per hour (63 km/h).
During May 25, Tropical Depression 01W developed over the northern South China Sea, about 600 km (375 mi) to the south of Hong Kong, China.[21][22] The system subsequently moved north-westwards and slightly developed further, before it made landfall near Yangjiang in Guangdong, China during the next day.[22] The system subsequently quickly weakened and degenerated into an area of low pressure during May 27.[22]
The system brought squally and heavy rain to the Pearl River Delta, including parts of Hong Kong, Macau and Guangdong province, where a bridge was destroyed by flooding and two people were injured.[22] At the Macau Ferry Terminal, two passengers were injured as a vessel collided with the terminal, while there was no significant damage reported within Hong Kong.[22] Damage in China were at CN¥60 million (US$9.14 million).[23]
Early on June 26, the JMA and PAGASA reported that Tropical Depression Ambo had developed over the Philippine Sea, about 555 km (345 mi) to the east of Manila on the island of Luzon in the Philippines.[24][25] The system was located within an environment that was thought to be favourable for further development, with low vertical wind shear and a fair outflow.[26] However, the depression's broad low level circulation centre was moving north-westwards quickly, which meant that the circulation's southern edge could not close off and was exposed.[26] The system subsequently made landfall on Luzon in Philippines later that day, where according to PAGASA it quickly weakened into a low-pressure area.[27] However, the JMA continued to monitor the system as a tropical depression throughout June 27, as it emerged into an unfavourable environment for further development in the South China Sea.[28][29] The depression subsequently made landfall on China's Guangdong Province, before it was last noted during June 28, as it dissipated over land.[28]
Several sea-trips in the Philippine island province of Catanduanes were cancelled with a total of seven passengers, three rolling cargoes and a sea vessel stranded at the port of Virac.[30]
On July 2, a tropical depression formed 780 km (480 mi) to the southeast of Yap State.[31][32] The following day, the depression became a tropical storm, receiving the name Nepartak.[31] By July 4, organization increased and Nepartak intensified into a severe tropical storm.[31] At that time, PAGASA assigned the local name Butchoy as it entered their area of responsibility.[33] Early on July 5, Nepartak started to undergo rapid intensification, reaching typhoon strength.[31] Nepartak soon reached Category 5 super typhoon intensity.[nb 5][34] During the course of July 6, Nepartak reached its peak intensity with 10-minute sustained winds of 205 km/h (125 mph) and a minimum barometric pressure of 900 mbar.[31][35] Nepartak started weakening during the next day, before making landfall in Taitung City on July 8. Nepartak weakened to a tropical storm[31][36] as it made its second landfall in Shishi, Fujian.[37] Nepartak rapidly deteriorated over land and fully dissipated on July 10.[31][38]
Two people drowned on July 7 after being washed out to sea by strong winds in Taiwan.[39] A total of seven major highways were damaged in Taiwan, too.[40] At least 10 people were killed and 11 others were reported missing across Fujian and Jiangxi.[41] At least 3,144 homes were destroyed and 15,800 hectares (39,000 acres) of crops were damaged; total economic losses reached ¥2.2 billion (US$320 million).[42][43] Overall, Nepartak killed a total of 86 people, mostly from Fujian Province, and caused a total of ¥9.99 billion (US$1.49 billion) of damage.[44][45]
During July 14, a tropical disturbance developed about 400 km (250 mi) to the west-northwest of Guam.[46] At this time atmospheric convection surrounding the system was flaring, over the system's weak but developing low level circulation center.[46] However, as a subtropical ridge of high pressure extended a significant amount of dry air over the disturbance, conditions were assessed to be marginally favorable for further development of the system.[46] Over the next couple of days the system gradually developed further as it moved north-westwards and was classified as a tropical depression by the JMA during July 15.[47][48] After the system had consolidated further, it was classified as Tropical Depression 03W by the JTWC during July 17.[49] However, the system weakened during that day as it moved polewards, along the western edge of the subtropical ridge of high pressure, into an area of increasing vertical wind shear.[49] As a result, the JTWC expected the system to quickly dissipate and issued their final advisory later that day.[50] However, over the next couple of days the system continued to move northwards and impacted the Ryukyu Islands, before it was last noted by the JMA during July 20.[51][52]
During July 21, a subtropical disturbance developed at the tailend of a mid-latitude trough of low pressure, about 775 km (480 mi) to the east of Iwo-To.[53] Over the next day, deep atmospheric convection developed over the system's elongated low level circulation center, before it was classified as a tropical depression by the JMA during July 22.[53][54] Over the next day, as the storm moved north-northeastwards around a subtropical ridge of high pressure, its structure improved as it developed a warm core and consolidated.[55] The hybrid system was subsequently classified as Tropical Storm 04W by the JTWC during July 23, before the JMA named it Lupit later that day.[54][55] Over the next day, Lupit peaked with sustained winds of 75 km/h (47 mph), as it went through an extratropical transition and took on frontal characteristics.[54][56] Lupit subsequently became extratropical during July 24, before it dissipated during July 26, as it moved into the Sea of Okhotsk.[54]
Mirinae was first noted as a tropical depression during July 25, as it moved off the west coast of Luzon into the South China Sea, about 300 km (185 mi) to the east of the Paracel Islands.[57][58] The next day, it was named Mirinae after it became a tropical storm.[57] Mirinae subsequently weakened slightly as it made landfall later that day, near Wanning and crossed Hainan Island. It re-intensified on moving into the Gulf of Tonkin.[57][59] The system reached its peak intensity as a severe tropical storm on July 27, with 10-minute sustained winds of 95 km/h (59 mph).[52] The system made landfall about 110 km (70 mi) to the south of Hanoi in northern Vietnam later that day.[57][60] Mirinae subsequently weakened gradually over northern Vietnam, before it dissipated to the north of Hanoi.[52][57]
In Hainan, economic losses caused by the storm reached 300 million yuan (US$45 million).[61] By July 29, the storm had left five people dead and five others missing in Vietnam. Severe damage to infrastructure was reported in Northern Vietnam, with damage to power lines causing blackouts and power cuts in some areas. Mirinae also sank 12 boats, destroyed the roofs of 1,425 houses and uprooted about 5,000 trees.[62] Damages in Vietnam amounted to ₫7.229 trillion ($323.9 million).[17]
During July 28, a tropical depression developed about 1,020 km (635 mi) to the east-southeast of Manila in the Philippines.[63][64] Over the next day as the system moved north-northwestwards under the influence of a subtropical ridge of high pressure, deep convection started wrapping into the system's low level circulation center.[65] During that day PAGASA assigned the local name Carina.[66]
While it lashes the Northeastern part of the Philippines, the provinces of Isabela, Cagayan, Quirino Province, Abra, Mt. Province, Benguet, Kalinga Province, and Ifugao Province reported that some of their major roads was not passable due to landslides. Despite the local governments of the said areas reported that there are no casualties, they still reported that some of them are injured during the typhoon.[69] Damages in Ilocos Norte were estimated at ₱19.38 million (US$411,000).[70]
During August 2, the JMA started to monitor a tropical depression that had developed within a favourable environment for further development, about 565 km (350 mi) to the northeast of Hagåtña, Guam.[71][72] The system had a broad and weak low level circulation centre, which had atmospheric convection flaring around the system's outer edge.[72] Over the next couple of days the system slowly moved north-eastwards, before it was classified as Tropical Storm 07W by the JTWC and named Omais by the JMA during August 4.[71][73]
A high-pressure system kept Omais to the east of Japan producing hot and steamy conditions across Japan approximately about 1000 people were taken to hospital due to heat stroke as the heat index climbed well into the 40s.[74]
On August 9, Omais transitioned to an extratropical cyclone as it moved over cooler waters of the northwestern Pacific Ocean, Omais fully dissipated on August 10.[75]
On August 7, the JMA started to monitor a tropical depression that had developed about 390 km (240 mi) to the west of Wake Island.[76] Over the next day the system gradually developed further as it moved south-westwards, before the JTWC classified it as Tropical Depression 08W during August 8.[76][77] Later that day, the JMA upgraded 08W to a tropical storm, naming it Conson.[78] Despite some moderate wind shear, Conson slowly intensified and later reached severe tropical storm strength on August 10.[79][80] The JTWC later stated that deep convection was forming near the center of Conson,[81] however shortly thereafter, convection became disorganized.[82]
By August 11, convection once re-intensified again, however its LLCC became exposed, causing the JTWC to lower its intensity to lower-end of tropical storm strength.[83] The JMA also downgraded Conson to a tropical storm.[84] During the next day, satellite image showed that the convective structure of Conson was beginning to deteriorate as it started to interact with drier air, suppressing convection.[85] The center of Conson became much broader and exposed early on August 13.[86] While moving northwestward, Conson became better defined than before, however its convection was more shallow as it started to interact will cooler sea-surface temperatures and drier air.[87] By August 14, the JTWC issued their final warning on Conson as it started to undergo its extratropical transition with a result of a strong wind shear and the interaction of the mid-latitude baroclinic zone.[88][89] The JMA tracked Conson until it fully transitioned into an extratropical cyclone on August 15 and made landfall near Nemuro Peninsula.[76] Its remnants were tracked until midday of August 16.[76]
During August 11, the JMA started to track a tropical depression, whereas the JTWC issued a Tropical Cyclone Formation Alert, as it was located about 695 km (432 mi) west-northwest of Guam.[90][91] After meandering eastwards, the JTWC designated the system as 09W, while the JMA immediately upgraded 09W to a tropical storm and assigned it the name Chanthu on August 13.[92][93] The JTWC followed suit early on August 14.[94] With an improving LLCC, Chanthu rapidly developed into a severe tropical storm from the JMA,[95][96] as it was later located over in an area of favorable environments of strengthening.[97] Despite a high chance of strengthening and a well-defined LLCC, Chanthu stopped generating convection as the JMA downgraded it to a tropical storm.[98][99]
Later that day, flaring convection was associated with its LLCC as it was beginning its extratropical transition while interacting with mid-latitude flow.[100] Therefore, early on August 17, Chanthu once again reached severe tropical storm strength as it attained its peak intensity with a minimal pressure of 980 millibars (28.94 inHg), while east of the Japanese archipelago of Honshu.[101] Shortly thereafter, the JTWC issued its final warning on Chanthu.[102] The JMA issued its final warning a few hours later as it made landfall over Cape Erimo of Hokkaido, Japan, at peak intensity.[103]
Agricultural damage in Japan were at ¥9.49 billion (US$94.7 million).[104]
On August 15, a tropical depression developed about 305 km (190 mi) to the southeast of Hong Kong.[105] During the course of August 17, enhanced satellite imagery showed that Dianmu was rapidly organizing with deep flaring convection surrounding its LLCC.[106] Dianmu made landfall in Haiphong and Thái Bình Province in northern Vietnam.[107][108] While overland, the system gradually weakened into a tropical depression, before it degenerated into an area of low pressure during August 20 while over Myanmar.[105]
In the province of Hainan, China, Dianmu's heavy rains brought the water level at the Longtang Dam on the Nandu River to a ten-year high of 13.35 metres. Hainan's capital, Haikou, experienced flooding in some areas. Over in Quảng Ninh, a total of 11 houses were collapsed and total damages in the city amounted to 3.5 billion VND (US$157,000).[109]
A tropical depression formed northwest of Guam on August 17.[110] On August 19, the system became a tropical storm and was named Mindulle early on August 19.[111] However, an upper-level low to the north and the predecessor of Tropical Storm Kompasu to the northeast were stifling the development of poleward outflow.[112]
Moving on the eastern edge of a relatively high-latitude monsoon gyre and being steered by the southern extension of the subtropical ridge anchored east of Japan, the intensification of Mindulle was limited on August 20, owing to modest dry air entrainment resulting in flaring convection near and surrounding the LLCC.[113] Although Mindulle became a severe tropical storm when it was approximately 380 km (240 mi) northwest of Chichi-jima at around 15:00 JST (06:00 UTC) on August 21, outflow from Tropical Storm Lionrock to the west was inhibiting further development, as the distance between their centers was only about 600 km (370 mi) at that time.[114][115] With warm sea surface temperatures of between 30 and 31 °C (86 and 88 °F), good equatorward and poleward outflow channels, as well as low vertical wind shear, Mindulle became a typhoon at around 03:00 JST on August 22 (18:00 UTC on August 21), when the center was located about 40 km (25 mi) east of Hachijō-jima.[116][117] At around 12:30 JST (03:30 UTC), Mindulle made landfall over the area near Tateyama, Chiba.[118]
The system that was to become Typhoon Lionrock was first noted as a hybrid disturbance on August 15, while it was located about 585 km (365 mi) to the west of Wake Island.[119] It developed into a tropical depression about 690 km (430 mi) northwest of Wake Island on August 16.[120] At this time the disturbance had a broad and poorly organized low level circulation centre, which had some shallow bands of atmospheric convection wrapping loosely around it.[119] Over the next day, the system moved northwards, while a TUTT cell created subsidence and high vertical windshear over the system. The JTWC considered the system to be subtropical at this time, as its structure was asymmetric, with deep convection displaced to the north and east of the system's low level circulation centre.[121] From late August 20 to early August 22, the system had at least somewhat an interaction with Mindulle, taking an erratic and slow path for a bit. Restrengthening begun again quickly, with the system already starting to develop an eye in mid-August 23. In the middle of the 24th of August the system reached an initial peak as a Category 3-equivalent storm.
Lionrock entered the Philippine Area of Responsibility on August 25, 2016, and PAGASA assigned Dindo[122] as the local name, while Lionrock had begun an eyewall replacement cycle early that day, weakening to a Category 2-equivalent storm. After two days, early on August 26, it finally completed the eyewall replacement cycle, but slow restrengthening occurred. Another two days passed until it reached its full peak as a Category 4-equivalent storm, which rapid weakening ensued after. On August 29, Lionrock turned towards the northwest due to a high-pressure system located east of Japan, putting it on an towards the northeastern region of the country.[123] Lionrock made landfall near Ōfunato, a city in Iwate Prefecture, Japan.[124] This made Lionrock the first tropical cyclone to make landfall over the Pacific coast of the Tōhoku region of Japan since the Japan Meteorological Agency began record-keeping in 1951.[125]
On August 18, the JMA started to monitor a tropical depression that had developed, about 1,300 km (810 mi) to the northeast of Guam.[126] The JTWC started issuing advisories by the next day as it was immediately classified as a tropical storm and the identifier of 13W.[127] The JMA followed suit early on August 20, and was named Kompasu.[126] Despite wind shear and an exposed LLCC, tightly curved banding was reported embedded within the northern extent of a very broad "monsoon gyre" circulation.[128] Both agencies reported that Kompasu had reached its peak strength as a minimal tropical storm with a minimum barometric pressure of about 994 mbar.[129] Later that day, deep convection of Kompasu had rapidly decreased as it was located in marginally favorable environments with low wind shear and sea-surface temperatures of about 26 degrees Celsius.[130] On August 21, the JTWC downgraded Kompasu to a tropical depression and issued their final bulletin on the system.[131] The JMA did the same and issued its final advisory on Kompasu as it transitioned into an extratropical system.[126]
Floods in Hokkaidō killed one person when a driver was stranded in his flooded car.[132]
During August 23, Tropical Depression 14W developed about 75 km (45 mi) to the east of Andersen Air Force Base, Guam.[133] Moving northward on the next day, the LLCC of 14W became exposed with a deteriorating convective signature.[134] Flaring deep convection became disorganized into a weakly-defined center due to strong northerly wind shear; the JTWC assessed 14W's winds only at 25 knots.[135] Due to a rapidly decaying LLCC with minor bursts of convection, both the JMA and the JTWC issued its final warning on 14W later that same day.[136][137]
A low-pressure area developed into a tropical depression southeast of Taiwan early on August 31.[138] Later that day, the JTWC began issuing advisories on the system, assigning the designation of 15W.[139] Early the next day, 15W had intensified into a tropical storm by both agencies, with the JMA prompting the name Namtheun.[140][141] The PAGASA however started issuing advisories on Namtheun and considered it as a tropical depression and gave the local name Enteng.[142] Despite the overall structure of the storm being described to be "midget" with a very small but compact LLCC, Namtheun had begun a phase of rapid intensification and a pinhole eye developed; therefore, the JTWC upgraded Namtheun to a Category 1 typhoon.[143] The JMA, though, upgraded Namtheun only to a severe tropical storm at that time.[144] Later that day, PAGASA had declared that the storm had exited its area of responsibility as a severe tropical storm.[145]
By September 2, rapid intensification ensued as it was reported that Namtheun was located over a region of warm sea surface temperatures of 30 degrees Celsius with high ocean heat content,[146] therefore prompting the JMA to classify it to a typhoon.[147] Namtheun developed a pinhole eye 8 nmi (15 km; 9.2 mi) across and reached its peak strength as a Category 3 typhoon with 1-minute sustained winds of 185 km/h (115 mph); the JMA though declared its 10-minute peak strength early on September 3 with a minimum barometric pressure of 955 millibars.[148][149] By that time, Namtheun was depicted with significantly weakened structure and a dissipation of its eye, therefore the JTWC downgraded Namtheun rapidly to a strong Category 1.[150] On September 4, Namtheun had weakened to a tropical storm due to diminishing convection, caused by high southwesterly wind shear.[151] After making landfall over in Nagasaki, Kyushu, both the JMA and JTWC issued its final advisory as a tropical depression early on September 5.[152][153]
On September 5, the JMA started to monitor a tropical depression, that had developed over the Japanese prefecture of Okinawa.[154] The depression was located within a favourable environment for further development, with very warm sea surface temperatures and low vertical wind shear. Over the next day the system moved north-eastwards towards the Japanese Mainland, before it was classified as a tropical storm and named Malou by the JMA during September 6.[155] However, the JTWC classified Malou as a hybrid system, with both subtropical and tropical characteristics.[156] They also noted that the convective development around the system's low level circulation centre was being hindered, as the subtropical westerlies were located over the system. During September 7, the system started to accelerate northwards, before the JMA issued their final advisory on the system as Malou became an extratropical cyclone.[157]
On September 8, a tropical depression formed[158] in a region of low wind shear, steered by ridges to the north and southwest, with warm water temperatures and outflow from the south.[159] The system reached tropical storm strength by 06:00 UTC on September 10, receiving the name Meranti.[160]
Rainbands and a central dense overcast continued to evolve as the wind shear decreased.[161] By early on September 12, Meranti reached typhoon status.[162] A small eye 9 km (5.6 mi) across developed within the spiraling thunderstorms, and Meranti started rapidly intensifying.[163]
Meranti quickly attained estimated 1-minute sustained winds of 285 km/h (180 mph), equivalent to Category 5 on the Saffir–Simpson scale.[164] Meranti gradually reached its peak intensity on September 13 while passing through the Luzon Strait. The JMA estimated peak 10-minute sustained winds of 220 km/h (140 mph) and a minimum barometric pressure of 890 hPa (mbar; 26.28 inHg),[165] while the JTWC estimated peak 1-minute sustained winds of 315 km/h (195 mph). Based on the JMA pressure estimate, Meranti was among the most intense tropical cyclones. The JTWC wind estimate made Meranti the strongest tropical cyclone worldwide in 2016, surpassing Cyclone Winston, which had winds of 285 km/h (180 mph) when it struck Fiji in February.[166]
Late on September 13, the storm made landfall on the 83 km2 (32 sq mi) island of Itbayat in the Philippine province of Batanes while near its peak intensity.[167] At around 03:05 CST on September 15 (19:05 UTC on September 14), Meranti made landfall over Xiang'an District, Xiamen in Fujian, China with measured 2-minute sustained winds of 173 km/h (107 mph),[168] making it the strongest typhoon to ever make landfall in China's Fujian Province.[169]
During September 8, the JTWC started to monitor a tropical disturbance that had developed about 1,210 km (750 mi) to the west of Iwo To.[170] Moving northward in a few days, the JTWC assessed that the system had strengthened into Tropical Depression 17W.[171] Despite its LLCC remaining small, satellite imagery showed that 17W produced persistent convection and some spiral banding.[172] Later, drier air surrounded the depression as it was now firmly embedded with the west-southwesterly flow ahead of the mid-latitude frontal zone.[173] The JTWC issued their final advisory on 17W on September 12, as the system was rapidly deteriorating due to vertical wind shear, and weakened into a remnant low.[174]Its remnants was later absorbed by a front near the International Date Line, late on September 14.[citation needed]
In the JMA's post-analysis, 17W was recognized as a tropical depression, and the system was first noted on September 10.[175]
On September 11, a tropical depression formed within an unfavourable environment for further development, about 860 km (535 mi) to the northeast of Ho Chi Minh City, Vietnam.[176][177] Satellite imagery then showed that the LLCC of 19W was broad and defined with some deep convective banding.[178] Its LLCC became exposed, though its deep convection remained in place.[179] Although the JMA declared that 19W had strengthened into a tropical storm,[180] the JTWC deemed the system to not have reached tropical storm intensity. Rai made landfall over Central Vietnam, about 94 km (58 mi) southeast of the city of Da Nang.[181] Rai degraded to a tropical depression six hours later.[182]
Heavy rains in Central Vietnam and Northern Thailand caused flooding and the bursting of the Bung River 2 hydroelectricity plant in Quảng Nam province of Vietnam, which released 28 million cubic meters of water and washed away 2 workers.[183] Four ships were sunk along central Vietnam's coastline and 2 others were left stranded, while 5 houses were completely destroyed and 275 others had their roofs torn off.[184] Most of the damage occurred in Nghệ An Province due to flooding, amounting to about ₫748 billion (US$33.6 million).[185] In total, Rai caused 12 deaths and damages amounting to ₫825 billion (US$37 million).[186]
On September 11, a tropical depression formed approximately 58 km (36 mi) south of Hagåtña, Guam.[187][188] On becoming a tropical storm, it was named Malakas.[189] By September 13, Malakas had improved in its organization and became a severe tropical storm thereafter.[190] At the same time, Malakas had entered the Philippine area of Responsibility, with PAGASA assigning the local name Gener.[191] Despite hindrance by the outflow of nearby Typhoon Meranti,[192] Malakas intensified into a typhoon.[193]
On September 16, Malakas rapidly intensified into a Category 4 typhoon.[194] Malakas reached its peak intensity with 1-minute sustained winds of 215 km/h (135 mph), 10-minute sustained winds of 175 km/h (110 mph), and a pressure of 930 hPa (27.46 inHg) by the following day.[195] Shortly thereafter, its eye became cloud-filled and ragged, signalling the onset of weakening.[196] After weakening to a Category 2 typhoon,[197] Malakas reintensified to a Category 3 typhoon by September 19.[198] Malakas then resumed weakening due to land interaction with Japan.[199] By the following day, Malakas weakened below typhoon intensity,[200] and became extratropical.[201]
At around 00:00 JST on September 20 (15:00 UTC on September 19), Malakas made landfall over the Ōsumi Peninsula in Japan.[202] It subsequently crossed Cape Muroto at around 11:00 JST (02:00 UTC) and made landfall over Tanabe at around 13:30 JST (04:30 UTC).[203][204]
Megi originated as a tropical depression about 722 km (449 mi) east-southeast of Guam on September 21.[205][206] The depression became a tropical storm by on September 23.[207] On the following day, Megi intensified to a severe tropical storm.[208] On developing an eye, Megi reached typhoon intensity.[209][210] Shortly thereafter, Megi entered PAGASA's area of responsibility, and the local name Helen was assigned.[211]
After a day of slight intensification, Megi started to undergo an eyewall replacement cycle. From then on, Megi rapidly intensified as it neared the coast of Taiwan.[212][213] Megi reached peak intensity as a Category 3 typhoon over Taiwan with 1-minute sustained winds of 205 km/h (125 mph), 10-minute sustained winds of 155 km/h (95 mph), and a minimum barometric pressure of 945 mbar late on September 26.[214] Early on September 27, Megi made landfall over Hualien City,[215] weakening due to land interaction.[216] Megi made landfall over in Hui'an County of Quanzhou the next day.[217] Megi continued deteriorating as it moved inland.[218]
In Taiwan, government officials announced that 814 school campuses across Taiwan were damaged, at an estimated cost of NT$161 million (US$4.17 million).[219] In all, 8 people were killed in Taiwan, and total economic losses were counted to be NT$3.36 billion (US$106.9 million).[220] Meanwhile, 44 people were killed in mainland China, and total damages were amounted to CNY9.7 billion (US$1.45 billion).[221]
On September 24, a weak tropical depression had developed approximately 1,445 km (898 mi) east-northeast of Guam.[222][223] The system reached tropical storm status and was assigned the name Chaba late the next day.[224] By September 30, Chaba had intensified into a severe tropical storm after deep convection had evolved into a banding feature, under very favorable conditions.[225][226] During October 1, Chaba entered the Philippine area of responsibility, with PAGASA giving the local name Igme, as it started to move in a northwestward direction.[227] Chaba became a typhoon after its organization and structure vastly improved.[228][229] During the next day, Chaba began explosive intensification,[230] reaching Category 5 super typhoon intensity with a sharp 5 nmi (9.3 km; 5.8 mi) wide eye.[231] Chaba reached its peak intensity with 10-minute sustained winds of 215 km/h (135 mph), while 1-minute sustained winds were at 280 km/h (175 mph), and the minimum central pressure was 905 mbar.[232] Thereafter, Chaba began to weaken as its core became asymmetric,[233] due to strong wind shear.[234] As it neared the coast of Busan, South Korea, Chaba transitioned into an extratropical cyclone.[235]
The storm left widespread damage across the southern regions of South Korea, killing at least 7 and leaving 4 others missing. Transportation was disrupted, with hundreds of flights canceled, while more than 200,000 households lost electricity. Chaba was the strongest typhoon to strike the country since Typhoon Sanba in 2012.[236]
A tropical disturbance entered the basin from the Central Pacific late on October 3 and on the following day, became a tropical depression approximately 1,333 km (828 mi) east-southeast of Wake Island.[237][238] After moving westward for several days, 23W intensified into a tropical storm, with the JMA giving the name Songda.[239][240] By October 9, an eye feature became apparent in microwave imagery,[241] and Songda reached severe tropical storm intensity.[242] Six hours later, Songda intensified into a typhoon.[243] Songda started to undergo rapid deepening, while forming a ragged eye.[244]
Songda eventually reached its peak intensity as a Category 4 super typhoon, despite 25-30 kt vertical wind shear,[245] with 10-minute sustained winds of 185 km/h (115 mph) and a minimum pressure of 925 mbar.[246] Shortly thereafter, Songda rapidly weakened as the wind shear increased further, and its eye became cloud-filled.[247] The JTWC issued its final advisory, classifying Songda as a rapidly-weakening Category 3-equivalent typhoon. The storm was embedded within the deep mid-latitude westerlies and located over waters cooler than 26 °C (79 °F).[248] The JMA downgraded Songda to a severe tropical storm in its final advisory on October 13, and Songda subsequently transitioned into an extratropical cyclone.[249] The extratropical remnant of Songda went on to affect the west coast of North America with heavy rain and winds.
Shortly after Songda's formation, another tropical depression developed well east to the Babuyan Group of Islands.[250][251] Later that day, PAGASA named the system Julian.[252] Despite Julian's disorganised structure, conditions were favourable for development, with light to moderate wind shear and very warm sea surface temperatures.[253] After a significant increase of convection, the system became a tropical storm, receiving the name Aere.[254] Aere became a severe tropical storm the following day.[255] Shortly thereafter, Aere reached itspeak intensity with 10-minute winds of 110 km/h (70 mph), just shy of typhoon strength.[256] Upwelling induced weakening, and Aere weakened to a tropical storm.[257][258] By October 10, Aere's LLCC became exposed due to southwesterly wind shear, and Aere degenerated to a tropical depression.[259] The JMA tracked its remnants as it moved southwestward until it weakened to a low-pressure area late on October 11.[260]
On October 13, the well-marked low-pressure area of Aere re-generated into a tropical depression,[261] and was tracked by the JMA until it fully dissipated on October 14.[262]
Most of the damage was reported mainly in Vietnam, especially in the central region, where estimated damages for transport works were at 130 billion ₫ (US$5.83 million).[263] A total of 25 houses were destroyed while 949 were damaged. In agriculture, 3.14 ha of rice and 11.5 ha of crops were damaged.[264][265] In total, flooding by the storm caused ₫ 4.6 trillion (US$209 million) of damage.[17]
Sarika was first noted as a tropical depression located about 1,200 km (750 mi) east-southeast of Manila, Philippines.[266][267] When 24W entered their area of responsibility, PAGASA assigned it the local name Karen.[268] By October 13, images depicted a broad LLCC; sea surface temperatures were high, at 31 °C (88 °F).[269] Hours later, the system became a tropical storm, with the JMA naming it as Sarika.[270][271] Sarika continued organizing and reached severe tropical storm intensity.[272] Several hours later, Sarika started to form an eye feature as it became a typhoon.[273][274] The storm eventually reached its peak intensity as a Category 4 typhoon with 1-minute sustained winds of 215 km/h (135 mph) and a minimum barometric pressure of 935 mbar.[275][276] Early on October 16, Sarika made landfall over in Baler, Aurora.[277] Dramatic weakening occurred as Sarika traversed the islands.[278] After moving westward rapidly for two days, Sarika weakened to a severe tropical storm as it made landfall over in Hainan.[279] Sarika continued weakening as it made its final landfall over the border of Vietnam and China, and dissipated later that day.[280][281]
During October 14, the JMA and JTWC reported that a tropical depression had developed about 700 km (435 mi) within the Caroline Islands to the south of Guam.[282][283] During that day the depressions low level circulation center rapidly consolidated, while bands of atmospheric convection built and wrapped into the center.[282] As a result, both warning centers reported that the depression had developed into a tropical storm, early the next day with the JMA naming it as Haima.
Early on October 15, the depression intensified into a tropical storm and was assigned the name Haima.[284] At this point of time, Haima was located in a very favorable environment with very high ocean heat content, very low wind shear and warm SSTs.[285] Three hours later, Haima intensified into a severe tropical storm.[286]With very good radial outflow, and still being situated in an extremely favorable environment, Haima rapidly intensified into a Category 4 super typhoon. By the end of the time, PAGASA announced the Haima had entered their area of responsibility, assigning it the name Lawin. Haima continued to intensify, reaching Category 5 super typhoon status by late on October 18.[citation needed] Super Typhoon Haima (Lawin) intensified further, and PAGASA used the term "super typhoon" on Haima for the first time ever since it was introduced in May 2015 due to Typhoon Haiyan's ravage during 2013. PAGASA also raised Signal #5 on the provinces of Cagayan and Isabela, which made it a very dangerous storm. Due to land interaction, Typhoon Haima weakened into a Category 4 storm, and made landfall in Luzon. Typhoon Haima weakened after making landfall in the Philippines, and made landfall in Hong Kong as a weakened Category 1 storm, in which Signal no. 8 was raised. By October 22, Haima became extratropical, and dissipated on October 26.
Total damages in the Philippines were at ₱3.74 billion (US$77.6 million).[287]
On October 31, the JMA started to track a tropical depression about 287 km (178 mi) south of Guam.[288][289] Late on November 2, organization had increased as the JTWC upgraded the system to a tropical depression with the identifier of 26W.[290] The JMA, however, had upgraded 26W to a tropical storm, giving the name Meari early on the next day.[291] With a rapidly consolidating LLCC, the JTWC followed suit of upgrading to a tropical storm.[292] By November 4, now moving northward, feeder bands were covering its very broad and compact LLCC and therefore Meari intensified into a severe tropical storm.[293][294] Hours later, deep convective banding with a central dense overcast (CDO) seen from satellite imagery prompted the JTWC and the JMA to upgrade Meari to a typhoon.[295][296] On the next day, organization ensued with deep convection wrapping into its center and its CDO feature becoming more symmetric. Meari intensified into a Category 2 typhoon.[297] During the course of November 6, Meari reached peak intensity only as a Category 2 with 10-minute sustained winds of 155 km/h (95 mph) and a minimum barometric pressure of 955 mbar.[298]
Later that day, Meari started to move northeastward rapidly with a strong poleward outflow as it started to interact with high vertical wind shear.[299] The JTWC downgraded Meari to a Category 1.[300] On November 7, the JTWC issued its final advisory on Meari due to the fact that its convective structure had become frontal, therefore it had already transitioned into an extratropical cyclone.[301] The JMA followed suit three hours later.[302]Meari's extratropical remnants was later absorbed by another but larger extratropical cyclone early on November 10.[citation needed]
On November 2, a tropical depression formed west of Sabah, Malaysia.[303] On November 5, it made landfall in southern Vietnam, and moved westwards until it dissipated on November 6.[304]
The depression exacerbated the torrential rains and heavy flooding that had impacted central and southern Vietnam since mid October,[305][306][307] damaging more than 20,000 homes.[308] A total of 15 people were killed and total damage reached ₫1.073 trillion (US$48.1 million) in Vietnam from November 1, though a total of 35 have been killed since the flooding from October.[309] Residents say that the country had their worst flooding since 2011.[310]
On November 8, the JMA started to track a tropical depression that had formed several nautical miles to the east of the Mariana Islands.[311] Later that day, the JTWC had started initiating advisories giving it the designation 27W.[312] During the next day, the JMA upgraded 27W to a tropical storm, naming it Ma-on, due to deep curved convection despite the system's LLCC being exposed.[313][314] The JTWC followed suit, upgrading it to a tropical storm after the system became more symmetrical with deep convection over in an area of low wind shear.[315] Later that day, Ma-on reached its maximum intensity with 10-minute sustained winds of 75 km/h (45 mph) and a minimum pressure of 1002 mbar.[316] Despite additional strengthening being forecast, its LLCC became exposed as favorable conditions started to deteriorate.[317] Both agencies downgraded Ma-on to a tropical depression and issued their final advisories,[318][319] although, the JMA tracked Ma-on until November 13.
During November 9, the JMA reported that a tropical depression had developed, about 455 km (285 mi) to the east-northeast of Kwajalein Atoll in the Marshall Islands.[320] Over the next couple of days, the system moved westwards through the Marshall Islands, where it gradually consolidated further within a favourable environment for further development.[320][321] During November 11, the JTWC initiated advisories and designated the system as Tropical Depression 28W, after atmospheric convection had started to wrap into the weekly defined low level circulation centre.[321] However, as the system was located within an area of low to moderate vertical wind shear, atmospheric convection associated with the system quickly dissipated.[322] The system subsequently degenerated into a tropical wave, before it was last noted by both warning centers during November 12.[320][323]
During November 23, PAGASA started to monitor a tropical depression that had developed about 420 km (260 mi) to the east of Hinatuan, Surigao del Sur.[324] The JMA, however, tracked the depression on November 24.[325] The JTWC would
shortly follow suit, designating it as "29W".[326] Over the rest of the day, the depression was gradually organizing under favorable conditions, before the PAGASA reported that Tropical Depression "Marce" had made landfall over Siargao Island around 12:00 UTC (8:00 p.m. PST) of the same day.[327] The JTWC would also follow suit shortly.[326] On 12:00 UTC of November 25, the JMA reported that "Marce" became a tropical storm while traversing the Visayan Sea, naming it as "Tokage".[325] Around 21:00 UTC of the same day, the PAGASA reported that "Marce" became a tropical storm while nearing Panay Island.[328] Tokage would emerge into the Mindoro Strait while making its second landfall and traverse on the Calamian Islands.[329][330][331] Shortly after emerging into the South China Sea on November 26,[332] JMA reported that Tokage briefly reached its peak intensity of 95 km/h (51 knots) and a pressure of 992 hpa.[325] The JTWC would follow suit, upgrading Tokage to a category 1 typhoon, reaching its peak intensity of 135 km/h (73 knots) and a pressure of 967 hPa, while weakening to a tropical storm at 12:00 UTC the same day.[326] Around 03:00 UTC (11:00 a.m PST) of November 26, PAGASA reported that Tokage slightly intensified while the storm is re-intensifying in the South China Sea.[333] On the next day, the JTWC reported that Tokage has regained its category 1 status, and had made its secondary peak intensity with 145 km/h (78 knots) and a pressure of 963 hPa.[326] Afterwards, Tokage rapidly weakened below typhoon intensity on 12:00 UTC the same day, below tropical storm intensity at 18:00 UTC, and both agencies discontinued advisories on 00:00 UTC of November 28.[325][326] The PAGASA, however, discontinued advisories for Tropical Depression "Marce" 3 hours later, around 11 a.m. PST.[334]
A total of 2,980 families were affected during Tokage's passing, and only 712 families evacuated to their designated evacuation centers and 67 families were served outside. A total of 46 municipalities and 9 cities on the regions Mimaropa, 6, 7, 8, 10, NIR and CAR suspended their classes during the storm, a total of 32 flights were cancelled, a total of 6 transmission lines were affected in Visayas, 2 landslides were reported on Sogod, Southern Leyte and Baybay, Leyte, 8 flooding incidents were reported around Oriental Mindoro, Romblon, and Negros Occidental. A total of 16 houses were destroyed during the storm (totally or partially), 40 hectares of palay to tillering stage and 15 hectares in ripening stage were damaged on some parts of Iloilo, and a total of ₱1,500,000 (US$28,788) as reported damages to infrastructure. In response, the DSWD provided a total of ₱24,9049.57 ($47,79.58 USD) to the affected families on Surigao del Norte and Surigao del Sur.[335]
Nock-ten was first noted as a tropical depression on December 21,[336] and quickly organized into a tropical storm.[337] The system reached severe tropical storm intensity the following day,[338] and then typhoon intensity the day after.[339] Around this time, a well-defined eye formed,[340] and the storm began rapidly intensifying.[341] Nock-ten reached its peak intensity as a Category 5-equivalent super typhoon with 1-minute sustained winds of 260 km/h (160 mph)[342] on December 25, becoming the strongest tropical cyclone recorded on Christmas Day anywhere in the world since at least 1960 in terms of 1-minute sustained winds.[18][19] Shortly thereafter, land interaction imparted weakening, with warming cloud tops,[343] and the typhoon made its first landfall over Catanduanes[344] as a Category 4-equivalent super typhoon with 1-minute sustained winds of 250 km/h (155 mph).[19] Nock-ten emerged into the South China Sea as a minimal typhoon,[345][346] where strong vertical wind shear associated with a cold surge event led to continued weakening,[347] with the low-level circulation center becoming exposed. The JMA issued its final advisory on the system late on December 27,[348] and the JTWC followed suit early on December 28.
Other systems
On June 23, the JMA started to monitor a broad tropical depression that had developed, about 420 km (260 mi) to the southwest of Manila in the Philippines.[349][350] The system was located within a favourable environment for further development, but was not expected to significantly develop any further, as an upper-level low was expected to move over the system.[350] Over the next couple of days the system moved north-westwards, before the system dissipated and became a remnant area of low pressure during June 25.[28] However, the system's remnants were tracked until they made landfall on central Vietnam during June 27.[28] The system was responsible for some heavy rainfall in Central and Southern Vietnam.[351] The JMA upgraded a low-pressure area east of Taiwan to a tropical depression on August 6.[352] The system made landfall over eastern China on August 9.
On August 10, the JMA reported that a tropical depression had developed, about 300 km (185 mi) to the southeast of Ishigaki Island.[353][354] Over the next day the system moved north-westwards, within a marginal environment for further development, before it passed over northern Taiwan and moved into the East China Sea.[354][355][356] The system subsequently continued moved westwards, before it was last noted as it made landfall on southern China later that day.[357] During August 12 a tropical depression developed near the coast of Taiwan, about 160 km (100 mi) to the southeast of Taipei.[358] The system subsequently made landfall on the island, before it was last noted during the next day as it dissipated over Taiwan.[359] A tropical depression briefly appeared over the Gulf of Tonkin early on August 16.[360] A tropical depression persisted east of the Northern Mariana Islands in the afternoon of August 17.[110] The system was last noted early on the next day and led to the formation of Tropical Storm Kompasu.[361] During August 24, two tropical depressions briefly developed; one in the South China Sea, and one over to the northeast of the Mariana Islands.[362]However, the system over the South China Sea briefly developed into a tropical depression twice on August 25 and 27.[citation needed] A tropical depression formed north of Wake Island early on August 30, and it became extratropical on the next day.[363][364]
On September 10, the JMA had briefly monitored a tropical depression to the east of Okinawa.[175] On October 15, the JMA reported that a tropical depression had entered the basin from the Central Pacific.[365] The system moved in a westward direction until dissipating several hours later on the same day.[366] On November 1, the JMA started to track a tropical depression about 704 km (437 mi) east of Andersen Air Force Base, Guam.[367][368] Later that same day, the JMA started issuing advisories on the depression whilst the JTWC had issued a Tropical Cyclone Formation Alert,[369][370] though they canceled it early on November 2.[371] The system moved northward until the JMA issued its final advisory as it interacted with the outer rainbands of the nearby Typhoon Meari and became extratropical on November 5.[372] During December 10, the JMA started to monitor a tropical depression that had developed about 415 km (260 mi) to the southeast of Ho-Chi-Minh City in Southern Vietnam.[373] Over the next couple of days, the system moved slowly westwards without developing any further, before it made landfall on and dissipated over Southern Vietnam during December 13. The depression had caused torrential rains and heavy flooding since mid December in Central and Southern Vietnam, where at least 24 people were killed and total damages had reached to at least ₫1.21 trillion (US$53.4 million) in Vietnam.[374] On December 27, the JMA briefly monitored on a tropical depression located near Chuuk, which dissipated later on the same day.[375]
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.[376] 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).[377] 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.[376] The names of significant tropical cyclones are retired, by both PAGASA and the Typhoon Committee.[377] Should the list of names for the Philippine region be exhausted then names will be taken from an auxiliary list of which the first ten are published each season. Unused names are marked in gray.
During the season 26 tropical storms developed in the Western Pacific and each one was named by the JMA, when the system was judged to have 10-minute sustained windspeeds of 65 km/h (40 mph). The JMA selected the names from a list of 140 names, that had been developed by the 14 members nations and territories of the ESCAP/WMO Typhoon Committee.[378] During the season, the name Rai was used for the first time after it replaced the name Fanapi in the 2010 season.
Nepartak
Lupit
Mirinae
Nida
Omais
Conson
Chanthu
Dianmu
Mindulle
Lionrock
Kompasu
Namtheun
Malou
Meranti
Rai
Malakas
Megi
Chaba
Aere
Songda
Sarika
Haima
Meari
Ma-on
Tokage
Nock-ten
After the season the Typhoon Committee retired the names Meranti, Sarika, Haima and Nock-ten from the naming lists, and in February 2018, the names were subsequently replaced with Nyatoh, Trases, Mulan, and Hinnamnor for future seasons, respectively.[379]
During the season PAGASA used its own naming scheme for the 14 tropical cyclones, that either developed within or moved into their self-defined area of responsibility.[380][381] The names were taken from a list of names, that was last used during 2012 and are scheduled to be used again during 2020.[380] All of the names are the same except for Pepito, which replaced the name Pablo after it was retired.[380] The name Gardo was replaced by Gomer after Gardo was added to PAGASA's main list replacing Glenda, which was retired after the 2014 season.
Retirement
After the season the names Karen, Lawin and Nina were retired by PAGASA, as they had caused over ₱1 billion in damages. They were subsequently replaced on the list with the names Kristine, Leon and Nika.[382] for the 2020 Pacific typhoon season.
Season effects
This table will list all the storms that developed in the northwestern Pacific Ocean west of the International Date Line and north of the equator during 2016. It will include their intensity, duration, name, areas affected, deaths, and damage totals. Classification and intensity values will be based on estimations conducted by the JMA. All damage figures will be in 2016 USD. Damages and deaths from a storm will include when the storm was a precursor wave or an extratropical cyclone.
^ 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).[2]
^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.[1]
^All damage totals are valued as of 2016 and in United States dollars, unless otherwise noted.
^Tropical cyclones reaching Category 3 (111 miles per hour or 179 kilometers per hour) and higher on the five-level Saffir–Simpson wind speed scale are considered major hurricanes.
^Frequently Asked Questions (Report). Joint Typhoon Warning Center. August 13, 2012. Archived from the original on October 4, 2013. Retrieved September 22, 2012.
^ abcdMalano, Vicente B (July 15, 2016). July — December 2016 (Seasonal Climate Outlook). Philippine Atmospheric Geophysical and Astronomical Services Administration. Archived from the original on July 4, 2016.
^ abcdTropical Storm Lupit (RSMC Tropical Cyclone Best Track). Japan Meteorological Agency. August 23, 2016. Archived from the original on August 24, 2016. Retrieved August 24, 2016.
^ abSevere Tropical Storm Lupit (RSMC Tropical Cyclone Best Track). Japan Meteorological Agency. September 15, 2016. Archived from the original on September 15, 2016. Retrieved September 17, 2016.
^ abcdTropical Storm Conson (RSMC Tropical Cyclone Best Track). Japan Meteorological Agency. September 15, 2016. Archived from the original on September 15, 2016. Retrieved September 15, 2016.
^平成２８年 台風第７号に関する情報 第４２号 (in Japanese). Japan Meteorological Agency. August 17, 2016. Archived from the original on August 17, 2016. Retrieved August 17, 2016.
^平成28年台風第7号による被害状況 (in Japanese). Ministry of Agriculture, Forestry and Fisheries. April 14, 2017. Retrieved April 16, 2017.
^ abTropical Storm Dianmu (RSMC Tropical Cyclone Best Track). Japan Meteorological Agency. September 21, 2016. Archived from the original on September 21, 2016. Retrieved September 21, 2016.
^平成２８年 台風第９号に関する情報 第３７号 (in Japanese). Japan Meteorological Agency. August 22, 2016. Archived from the original on August 22, 2016. Retrieved August 22, 2016.
^平成２８年 台風第１０号に関する情報 第１１５号 (in Japanese). Japan Meteorological Agency. August 30, 2016. Archived from the original on August 30, 2016. Retrieved August 30, 2016.
^ abcTropical Storm Kompasu (RSMC Tropical Cyclone Best Track). Japan Meteorological Agency. September 27, 2016. Archived from the original on September 27, 2016. Retrieved September 27, 2016.
^ ab日々の天気図 2016年9月(PDF) (in Japanese). Japan Meteorological Agency. Retrieved December 22, 2016.
^Tropical Storm Rai (RSMC Tropical Cyclone Best Track). Japan Meteorological Agency. October 24, 2016. Archived from the original on October 24, 2016. Retrieved October 30, 2016.
^平成２８年 台風第１６号に関する情報 第８９号 (in Japanese). Japan Meteorological Agency. September 19, 2016. Archived from the original on September 19, 2016. Retrieved September 19, 2016.
^平成２８年 台風第１６号に関する情報 第１０２号 (in Japanese). Japan Meteorological Agency. September 20, 2016. Archived from the original on September 20, 2016. Retrieved September 20, 2016.
^平成２８年 台風第１６号に関する情報 第１０６号 (in Japanese). Japan Meteorological Agency. September 20, 2016. Archived from the original on September 20, 2016. Retrieved September 20, 2016.
.jpg)
