2016 Pacific typhoon season

2016 Pacific typhoon season

Season summary map
First system formed	May 26, 2016
Last system dissipated	Season ongoing
Strongest storm1	Meranti – 890 hPa (mbar), 220 km/h (140 mph) (10-minute sustained)
Total depressions	46 official, 1 unofficial
Total storms	25
Typhoons	12
Super typhoons	5 (unofficial)
Total fatalities	835
Total damage	$9.49 billion (2016 USD)
1Strongest storm is determined by lowest pressure
Pacific typhoon seasons 2014, 2015, 2016, 2017, 2018

The 2016 Pacific typhoon season is an event in the annual cycle of tropical cyclone formation, in which tropical cyclones form in the western Pacific Ocean. The season has so far produced a total of 25 named storms, 12 typhoons and five intense typhoons. The season runs throughout 2016, though typically most tropical cyclones develop between May and October. 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 65 km/h (40 mph) anywhere in the basin, whilst the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) assigns names to tropical cyclones which move into or form as a tropical depression in their area of responsibility, located between 135°E and 115°E and between 5°N and 25°N, regardless of whether or not a tropical cyclone has already been given a name by the JMA. Tropical depressions that are monitored by the United States' Joint Typhoon Warning Center (JTWC) are given a number with a "W" suffix.

The first system formed on May 26, making it the fifth-latest start for a Pacific typhoon season in the satellite era; only the 1973, 1983, 1984 and 1998 seasons started later. However, the first named tropical storm, Nepartak, did not develop until July 3, making it the second-latest season for a named storm to develop. Nepartak's naming ended a 199-day period (from December 17, 2015 to July 2, 2016) in which no named storm was active within the basin, which equalled the record set in 1997–98.^[1]

Seasonal forecasts

TSR forecasts Date	Tropical storms	Total Typhoons	Intense TCs	ACE	Ref
Average (1965–2015)	26	16	9	298	[2]
May 7, 2016	22	13	6	217	[2]
July 6, 2016	22	13	7	239	[3]
August 8, 2016	22	13	7	231	[4]
Other forecasts Date	Forecast Center	Period		Systems	Ref
January 8, 2016	PAGASA	January — March		1–2 tropical cyclones	[5]
January 8, 2016	PAGASA	April — June		1–3 tropical cyclones	[5]
June 28, 2016	CWB	January 1 — December 31		19–23 tropical storms	[6]
July 15, 2016	PAGASA	July — September		5–11 tropical cyclones	[7]
July 15, 2016	PAGASA	October — December		4–9 tropical cyclones	[7]
	Forecast Center	Tropical cyclones	Tropical storms	Typhoons	Ref
Actual activity:	JMA	46	25	12
Actual activity:	JTWC	29	23	12
Actual activity:	PAGASA	13	12	8

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.^[5] 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.^[5]

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,^[8] 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.^[2] Ahead of the Thailand rainy season starting during May, the Thai Meteorological Department predicted that two tropical cyclones would move near Thailand during 2016.^[9] 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.^[9] The second tropical cyclone was predicted to move past Southern Thailand during October and November.^[9] 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.^[6]

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.^[3] PAGASA issued their second and final forecast for the year on July 15, within its seasonal climate outlook for the period July – December.^[7] 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.^[7] 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.^[4]

Season summary

Despite the season having a late start, the 2016 season was an active season with a total of 47 tropical depressions, of which 25 became tropical storms. After five months of inactivity owing to the strong 2014–16 El Niño event, the first tropical system developed on May 26, making it the fifth-latest season for a system to form. 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 a 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) in which no named storm was active within the basin; this period is of joint-record length with that from December 22, 1997 to July 8, 1998.^[1] 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 when it made landfall over Red River Delta in Northern Vietnam. The storm caused a total of US$334 million of damage 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 storms 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.^[10] 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.

In September, conditions throughout the basin became marginally favorable for typhoons. Typhoon Meranti became the strongest typhoon in terms of pressure since Typhoon Megi in 2010, as well as the strongest typhoon in terms of wind speed since Typhoon Haiyan in 2013, and the strongest tropical cyclone worldwide in 2016. Typhoon Megi reached its peak intensity when it made landfall over Taiwan. Both Meranti and Megi made landfall in Taiwan and 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, causeing 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 and became the strongest tropical cyclone to make landfall in South Korea since Sanba in 2012. Chaba also caused 7 deaths in the country.^[11] A tropical depression formed east of the International Dateline on October 3, and entered the basin before it became Typhoon Songda. Songda struck the Pacific Northwest region of the United States and Canada as a powerful extratropical cyclone.^[12] Severe Tropical Storm Aere affected parts of Southeast Asia in mid-October, and the storm triggered the worst flooding in Vietnam since 2010, causing a total of US$112 million of damage.^[13][14] Later, Typhoon Sarika became a strong and powerful typhoon, which affected the Philippines, China and Vietnam, causing very severe damage. After Sarika, Typhoon Haima reached Category 5 super typhoon strength and it became the second most intense tropical cyclone of the North Pacific Ocean in 2016. Haima affected the Philippines and China, causing a total of US$1.93 billion of damage. In early November, a tropical depression made landfall in Southern Vietnam and caused heavy flooding throughout central and southern Vietnam, causing moderate damage.

Storms

Tropical Depression 01W

Tropical depression (JMA)
Tropical depression (SSHWS)
Duration	May 26 – May 27
Peak intensity	45 km/h (30 mph) (1-min)  998 hPa (mbar)

During May 26, Tropical Depression 01W developed over the northern South China Sea, about 600 km (375 mi) to the south of Hong Kong, China.^[15][16] The system subsequently moved north-westwards and slightly developed further, before it made landfall near Yangjiang in Guangdong, China during the next day.^[16] The system subsequently quickly weakened and degenerated into an area of low pressure during May 27.^[16]

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.^[16][17] 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.^[16]

Tropical Depression Ambo

Tropical depression (JMA)
Duration	June 26 – June 28
Peak intensity	55 km/h (35 mph) (10-min)  1002 hPa (mbar)

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.^[18][19] 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.^[20] 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.^[20] The system subsequently made landfall on Luzon in Philippines later that day, where according to PAGASA it quickly weakened into a low pressure area.^[21] 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.^[22][23] The depression subsequently made landfall on China's Guangdong Province, before it was last noted during June 28, as it dissipated over land.^[22] 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.^[24]

Typhoon Nepartak (Butchoy)

Typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	July 2 – July 10
Peak intensity	205 km/h (125 mph) (10-min)  900 hPa (mbar)

On July 2, the JMA started to track a tropical depression about 780 km (485 mi) to the southeast of Yap State.^[25][26] During the next day, the JTWC started issuing advisories with the designation of 02W, while the JMA had already classified the system as a tropical storm, with the name Nepartak.^[25][27] By July 4, organization ensued and Nepartak intensified into a severe tropical storm.^[25] In the same time, PAGASA had coded Nepartak to its local name Butchoy as it entered their area of responsibility.^[28] Early on July 5, Nepartak started to undergo rapid intensification, and both agencies classified the storm to a typhoon.^[25][29] Later, the JTWC upgraded it further to a Category 4 typhoon after it had entered in area of warm waters and low shear as its eye had became well-defined.^[30] Within their next few advisories, Nepartak reached Category 5 super typhoon intensity.^[31] During the course of July 6, Nepartak sustained its maximum intensity with 10-minute sustained winds of 205 km/h (125 mph) and a minimum barometric pressure of 900 mbar.^[25][32] Though a buoy recorded a minimum pressure of 897 mbar.^[33] Nepartak later started weakening during the next day, until it made landfall in Taitung City on July 8. By July 9, all agencies had already downgraded Nepartak to a tropical storm,^[25][34] as it made its second landfall in Shishi, Fujian.^[35] As it rapidly deteriorated over land, both agencies made their final advisory and it fully dissipated on July 10.^[25][36]

Two people drowned on July 7 after being washed out to sea by strong winds in Taiwan.^[37] A total of seven major highways were damaged in Taiwan, too.^[38] At least 10 people were killed and 11 others were rendered missing across Fujian and Jiangxi.^[39] 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).^[40][41] Overall, Nepartak killed a total of 86 people, mostly from Fujian province, and caused a total of ¥9.98 billion (US$1.52 billion) of damage.^[42][43]

Tropical Depression 03W

Tropical depression (JMA)
Tropical depression (SSHWS)
Duration	July 15 – July 20
Peak intensity	45 km/h (30 mph) (1-min)  1006 hPa (mbar)

During July 14, a tropical disturbance developed about 400 km (250 mi) to the west-northwest of Guam.^[44] At this time atmospheric convection surrounding the system was flaring, over the system's weak but developing low level circulation center.^[44] 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.^[44] 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.^[45][46] After the system had consolidated further, it was classified as Tropical Depression 03W by the JTWC during July 17.^[47] 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 windshear.^[47] As a result, the JTWC expected the system to quickly dissipate and issued their final advisory later that day.^[48] 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.^[49][50]

Tropical Storm Lupit

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	July 22 – July 24
Peak intensity	75 km/h (45 mph) (10-min)  1000 hPa (mbar)

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.^[51] Over the next day, deep atmospheric convection developed over the system's elongated low level circulation, before it was classified as a tropical depression by the JMA during July 22.^[51][52] 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.^[53] 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.^[52][53] 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.^[52][54] Lupit subsequently became extratropical during July 24, before it dissipated during July 26, as it moved into the Sea of Okhotsk.^[52]

Severe Tropical Storm Mirinae

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	July 25 – July 28
Peak intensity	100 km/h (65 mph) (10-min)  980 hPa (mbar)

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.^[55][56] The system's well defined low level circulation centre was located in a very favourable environment for further development, with low vertical windshear and very warm sea surface temperatures.^[56][57] Later that day the JTWC initiated advisories on the system and classified it as Tropical Depression 05W, as it moved north-westwards along the periphery of a subtropical ridge of high pressure.^[57] During the next day, as the system moved west-northwestwards, it continued to intensify was named Mirinae by the JMA after it had become a tropical storm.^[55][58] Mirinae subsequently weakened slightly as it made landfall later that day, near Wanning and crossed Hainan Island, before it re-intensified as it had moved into the Gulf of Tonkin.^[55][59] The system was classified as a severe tropical storm by the JMA during July 27, as it was estimated that Mirinae had peaked with sustained wind-speeds of 95 km/h (59 mph).^[50][60] The system subsequently made landfall about 110 km (70 mi) to the south of Hanoi in northern Vietnam later that day.^[55][61] Mirinae subsequently weakened gradually over northern Vietnam, before it was last noted during July 28, as it dissipated to the north of Hanoi.^[50][55]

In Hainan, economic losses by the storm reached 300 million yuan (US$45 million).^[62] 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.^[63] Damage in Vietnam reached ₫6442 billion ($289 million).^[64]

Severe Tropical Storm Nida (Carina)

Severe tropical storm (JMA)
Category 1 typhoon (SSHWS)
Duration	July 29 – August 3
Peak intensity	110 km/h (70 mph) (10-min)  975 hPa (mbar)

During July 28, the Japan Meteorological Agency started to monitor a tropical depression that had developed about 1,020 km (635 mi) to the east-southeast of Manila in the Philippines.^[65][66] The system had a broad low level circulation center which was consolidating, with atmospheric convection developing to the north and south of the depression.^[66] The system was also located within a favorable environment for further development with low vertical wind shear and very warm sea surface temperatures.^[66] Over the next day as the system moved north-northwestwards under the influence of a subtropical ridge of high pressure, deep atmospheric convection started wrapping into the system's low level circulation center.^[67] The United States Joint Typhoon Warning Center subsequently issued a tropical cyclone formation alert during July 29, as the system rapidly consolidated further, while the global models indicated that tropical cyclogenesis would take place during the next 24 hours.^[67] During that day as the system consolidated further, both PAGASA and the JTWC initiated advisories on the system, with the former naming it Carina, while the latter classified it as 06W.^[68][69]

On July 31, Nida made landfall over the area between Baggao and Gattaran of the Cagayan province in the Philippines at 13:20 PST (05:20 UTC) as a severe tropical storm.^[70] At 03:35 CST on August 2 (19:35 UTC on August 1), Nida made landfall over Dapeng Peninsula of Shenzhen, Guangdong, China as a severe tropical storm.^[71]

Severe Tropical Storm Omais

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	August 2 – August 9
Peak intensity	110 km/h (70 mph) (10-min)  975 hPa (mbar)

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.^[72][73] The system had a broad and weak low level circulation centre, which had atmospheric convection flaring around the system's outer edge.^[73] 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.^[72][74]

Tropical Storm Conson

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	August 7 – August 15
Peak intensity	85 km/h (50 mph) (10-min)  985 hPa (mbar)

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.^[75] 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.^[75][76] Later that day, the JMA upgraded 08W to a tropical storm, naming it Conson.^[77] Despite some moderate wind shear, Conson slowly intensified and later reached severe tropical storm strength on August 10.^[78][79] The JTWC later stated that deep convection was forming near the center of Conson,^[80] however shortly thereafter, convection became disorganized.^[81]

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.^[82] The JMA also downgraded Conson to a tropical storm.^[83] 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.^[84] The center of Conson became much broader and exposed early on August 13.^[85] 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.^[86] 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.^[87][88] The JMA tracked Conson until it fully transitioned into an extratropical cyclone on August 15 and made landfall near Nemuro Peninsula.^[75] Its remnants were tracked until midday of August 16.^[75]

Severe Tropical Storm Chanthu

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	August 12 – August 17
Peak intensity	100 km/h (65 mph) (10-min)  980 hPa (mbar)

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.^[89][90] After meandering eastwards, the JTWC designates the system as 09W, while the JMA immediately upgraded 09W to a tropical storm, with the naming of Chanthu on August 13.^[91][92] The JTWC followed suit early on August 14.^[93] With an improving LLCC, Chanthu rapidly developed into a severe tropical storm from the JMA,^[94][95] as it was later located over in an area of favorable environments of strengthening.^[96] Despite a high chance of strengthening and a well-defined LLCC, Chanthu stopped generating convection as the JMA downgraded it to a tropical storm.^[97][98]

Later that day, flaring convection was associated with its LLCC as it was beginning its extratropical transition while interacting with mid-latitude flow.^[99] Therefore, early on August 17, Chanthu once again reached severe tropical strom 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.^[100] Shortly thereafter, the JTWC issued its final warning on Chanthu.^[101] The JMA issued its final warning a few hours later as it made landfall over Cape Erimo of Hokkaido, Japan, at peak intensity.^[102]

Tropical Storm Dianmu

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	August 15 – August 20
Peak intensity	75 km/h (45 mph) (10-min)  980 hPa (mbar)

During August 15, the JMA reported that a tropical depression, had developed about 305 km (190 mi) to the southeast of Hong Kong.^[103] The system meandered slowly westward until the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on August 17.^[104] By August 18, the JMA upgraded the depression to a tropical storm, prompting to name it as Dianmu.^[105] Shortly thereafter, the JTWC began issuing advisories, classifying it as a tropical depression with the identifier of 11W.^[106] During the course of the day, enhanced satellite imagery showed that Dianmu was rapidly organizing with deep flaring convection surrounding its LLCC.^[107] Due to warm sea-surface temperatures with a compact microwave eye feature seen from satellite imagery, the JTWC upgraded Dianmu to a tropical storm.^[108] However the JTWC issued its final warning on Dianmu as it made landfall over in Haiphong and Thái Bình Province in northern Vietnam.^[109][110] 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.^[103]

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 thousand).^[111]

Typhoon Mindulle

Typhoon (JMA)
Tropical storm (SSHWS)
Duration	August 17 – August 23
Peak intensity	120 km/h (75 mph) (10-min)  975 hPa (mbar)

A tropical depression formed northwest of Guam on August 17.^[112] The Japan Meteorological Agency (JMA) indicated that a tropical depression had formed northwest of Guam at noon on August 17.^[113] A few hours later, the Joint Typhoon Warning Center (JTWC) quickly issued a Tropical Cyclone Formation Alert and also upgraded the system to a tropical depression with the designation 10W on the same day, based on increased symmetric convection associated with a defined but partially exposed low-level circulation center (LLCC) that was embedded within the southwest monsoon surge.^[114][115] One day later, the JTWC upgraded 10W to a tropical storm via the Dvorak technique, with the winds proved by a recent scatterometer pass.^[116] The JMA upgraded the system to a tropical storm and named it Mindulle early on August 19, when central convection had become more organized.^[117] However, an upper-level low to the north and the predecessor of Tropical Storm Kompasu to the northeast were stifling the development of any poleward outflow.^[118]

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.^[119][120] Although the JMA upgraded Mindulle to 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 and causing a partially exposed LLCC with deep convection displaced southward, as the distance between their centers was only about 600 km (370 mi) at that time.^[121][122] With warm sea surface temperatures of between 30 to 31 °C (86 to 88 °F), good equatorward and poleward outflow channels, as well as low vertical wind shear, the JMA upgraded Mindulle to a typhoon at around 03:00 JST on August 22 (18:00 UTC on August 21), when the center was located only about 40 km (25 mi) east of Hachijō-jima.^[123][124] At around 12:30 JST (03:30 UTC), Mindulle made landfall over the area near Tateyama, Chiba.^[125]

Typhoon Lionrock (Dindo)

Typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	August 17 – August 30
Peak intensity	165 km/h (105 mph) (10-min)  940 hPa (mbar)

The JMA upgraded a low-pressure area to a tropical depression about 690 km (430 mi) northwest of Wake Island on August 16.^[126] 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.^[127] 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.^[127] It was located within a marginal environment for further development and was predicted to develop further, in association with a developing upper level low.^[127] Over the next day the system moved northwards, while a TUTT Cell created subsidence and high vertical windshear over the system, before it was classified as a tropical depression by the JMA during August 16.^[128] The depression was subsequently classified as subtropical by the JTWC during August 17, as its structure was asymmetric, with deep convection displaced to the north and east of the system's low level circulation centre.^[129]

Lionrock entered the Philippine Area of Responsibility on August 25, 2016, and PAGASA assigned Dindo ^[130] as the local name for Lionrock. On August 29, Lionrock turned towards the northwest due to a high pressure system located east of Japan, putting it on an unprecedented path towards the northeastern region of the country.^[131] Right before weakening into a severe tropical storm at 18:00 JST (09:00 UTC) on August 30, Lionrock made landfall near Ōfunato, a city in Iwate Prefecture, Japan.^[132] This makes 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.^[133]

Tropical Storm Kompasu

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	August 18 – August 21
Peak intensity	65 km/h (40 mph) (10-min)  994 hPa (mbar)

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.^[134] The JTWC started issuing advisories by the next day as it was immediately classified as a tropical storm and the identifier of 13W.^[135] The JMA followed suit early on August 20, and was named Kompasu.^[134] Despite wind shear and an exposed LLCC, tightly curved banding was reported embedded within the northern extent of a very broad "monsoon gyre" circulation.^[136] Both agencies reported that Kompasu had reached its peak strength as a minimal tropical storm with a minimum barometric pressure of about 994 mbar.^[137] 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.^[138] On August 21, the JTWC downgraded Kompasu to a tropical depression and issued their final bulletin on the system.^[139] The JMA did the same and issued its final advisory on Kompasu as it transitioned into an extratropical system.^[134]

Floods in Hokkaidō killed one person when a driver was stranded in his flooded car.^[140]

Tropical Depression 14W

Tropical depression (JMA)
Tropical depression (SSHWS)
Duration	August 23 – August 24
Peak intensity	55 km/h (35 mph) (10-min)  1000 hPa (mbar)

During August 23, Tropical Depression 14W developed about 75 km (45 mi) to the east of Andersen Air Force Base, Guam.^[141] Moving northward on the next day, the LLCC of 14W became exposed with a deteriorating convective signature.^[142] 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.^[143] 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.^[144][145]

Typhoon Namtheun (Enteng)

Typhoon (JMA)
Category 3 typhoon (SSHWS)
Duration	August 31 – September 5
Peak intensity	140 km/h (85 mph) (10-min)  955 hPa (mbar)

A low-pressure area developed into a tropical depression southeast of Taiwan early on August 31.^[146] Later that day, the JTWC began issuing advisories on the system, assigning the designation of 15W.^[147] Early the next day, 15W had intensified into a tropical storm by both agencies, with the JMA prompting the name Namtheun.^[148][149] The PAGASA however started issuing advisories on Namtheun and considered it as a tropical depression and gave the local name Enteng.^[150] 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.^[151] The JMA, though, upgraded Namtheun only to a severe tropical storm at that time.^[152] Later that day, PAGASA had declared that the storm had exited its area of responsibility as a severe tropical storm.^[153]

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,^[154] therefore prompting the JMA to classify it to a typhoon.^[155] Namtheun developed a pinhole eye 8 NM (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.^[156][157] 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.^[158] On September 4, Namtheun had weakened to a tropical storm due to diminishing convection, caused by high southwesterly wind shear.^[159] After making landfall over in Nagasaki, Kyushu, both the JMA and JTWC issued its final advisory as a tropical depression early on September 5.^[160][161]

Tropical Storm Malou

Tropical storm (JMA)
Duration	September 5 – September 7
Peak intensity	75 km/h (45 mph) (10-min)  1000 hPa (mbar)

On September 5, the JMA started to monitor a tropical depression, that had developed over the Japanese prefecture of Okinawa.^[162] The depression was located within a favourable environment for further development, with very warm sea temperasurface 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.^[163] However, the JTWC classified Malou as a hybrid system, with both subtropical and tropical characteristics.^[164] They also noted that the systems low level circulation centre convective development 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.^[165]

Typhoon Meranti (Ferdie)

Typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	September 9 – September 16
Peak intensity	220 km/h (140 mph) (10-min)  890 hPa (mbar)

On September 8, the Joint Typhoon Warning Center (JTWC)^{[lower-alpha 1]} issued a tropical cyclone formation alert for a closed atmospheric circulation about 155 km (100 mi) west of Guam in the western Pacific Ocean.^[167] At 18:00 UTC that night, the Japan Meteorological Agency (JMA)^{[lower-alpha 2]} classified the system as a depression,^[168] On the next day, the JTWC classified it as Tropical Depression 16W. By that time, the nascent system was moving slowly west-northwestward through a region of low wind shear, steered by ridges to the north and southwest. Increasing and fragmented convection, or thunderstorms, was fueled by warm water temperatures and outflow from the south.^[169] At 06:00 UTC on September 10, the JMA upgraded the depression to Tropical Storm Meranti,^[170] which meandered over its own track while consolidating.^[171]

Northerly wind shear shifted the deepest convection to the south of Meranti's circulation,^[172] although rainbands and a central dense overcast continued to evolve as the wind shear decreased.^[173] By early on September 11, the storm's movement was steady to the west-northwest, south of the ridge.^[174] At 06:00 UTC that day, the JMA upgraded Meranti to typhoon status,^[175] and shortly thereafter the JTWC followed suit.^[176] The structure continued to improve, with increased outflow.^[177] A small eye 9 km (5.6 mi) across developed within the spiraling thunderstorms, signaling that Meranti was rapidly intensifying.^[178] At 06:00 UTC on September 12, the JTWC upgraded Meranti to a super typhoon, with 1-minute maximum sustained winds of 240 km/h (150 mph).^[179]

Six hours later, the JTWC estimated 1-minute sustained winds of 285 km/h (180 mph), equivalent to Category 5 on the Saffir–Simpson scale, while noting "an extremely favorable environment", and that the eye became even more symmetric within intense convection.^[180] Outflow enhanced by a strong anticyclone over Meranti fueled the intensification,^[181] and the typhoon peaked in 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),^[182] while the JTWC estimated peak 1-minute sustained winds of 305 km/h (190 mph).^[183]

Late on September 13, the storm made landfall on the 83 km² (32 sq mi) island of Itbayat in the Philippine province of Batanes while near its peak intensity.^[184] 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 (108 mph),^[185] making it the strongest typhoon to ever make landfall in China's Fujian Province.^[186]

Tropical Depression 17W

Tropical depression (SSHWS)
Duration	September 11 – September 12
Peak intensity	55 km/h (35 mph) (1-min)  1000 hPa (mbar)

On September 8, the JTWC started to monitor a tropical disturbance about 1,211 km (752 mi) west of Iwo To.^[187] Moving northward in a few days, the JTWC assessed that the system had strengthened into Tropical Depression 17W.^[188] Despite its LLCC remaining small, satellite imagery showed that 17W produced persistent convection and some spiral banding.^[189] Later, drier air surrounded the depression as it was now firmly embedded with the west-southwesterly flow ahead of the mid-latitude frontal zone.^[190] The JTWC later issued their final advisory on 17W as the system was rapidly deteriorating due to vertical wind shear as it fully dissipated early on September 12.^[191] Its remnants was later absorbed by a front near the International Dateline early on September 13.

Tropical Storm Rai

Tropical storm (JMA)
Tropical depression (SSHWS)
Duration	September 11 – September 13
Peak intensity	65 km/h (40 mph) (10-min)  996 hPa (mbar)

During September 11, the JMA started to monitor a tropical depression, that had developed within an unfavourable environment for further development, about 860 km (535 mi) to the northeast of Ho Chi Minh City, Vietnam.^[192][193] Later, the JTWC issued a Tropical Cyclone Formation Alert.^[194] By the next day, the JTWC upgraded the system to a tropical depression with the given designation of 19W.^[195] Satellite imagery then showed that the LLCC of 19W was broad and defined with some deep convective banding.^[196] However, its LLCC became exposed, though its deep convection remained in place.^[197] Hours later, the JMA had declared that 19W had strengthened into a tropical storm, with the name Rai.^[198] Although it has strengthened, the JTWC issued its final advisory without upgrading it to a tropical storm, whilst Rai made landfall over Central Vietnam, about 94 km (59 mi) southeast of the city of Da Nang.^[199] According to the JMA, Rai reached its maximum intensity only as a weak tropical storm over land,^[200] however they issued their last advisory and was downgraded into a tropical depression six hours later.^[201]

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.^[202] 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.^[203] Most of the damage occurred in Nghệ An Province due to flooding of about ₫748 billion (US$33.7 million).^[204] In total, Rai caused 12 deaths and damages amounting to ₫825 billion (US$37.3 million).^[205]

Typhoon Malakas (Gener)

Typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	September 11 – September 20
Peak intensity	175 km/h (110 mph) (10-min)  930 hPa (mbar)

During September 11, both the JMA and the JTWC started to monitor Tropical Depression 18W approximately 58 km (36 mi) south of Hagåtña, Guam.^[206][207] Due to decent organization and improved banding, JTWC upgraded 18W to a tropical storm.^[208][209] 18W was fully upgraded to a named tropical storm by the JMA few hours later and was named Malakas.^[210] By September 13, Malakas had improved in its organization and was already strengthening with deep convection wrapping into its LLCC;^[211] the JMA upgraded Malakas to a severe tropical storm thereafter.^[212] In the same time, Malakas had entered the Philippine area of Responsibility, with PAGASA assigning the local name Gener.^[213] Later, it was reported that Malakas was located in marginal conditions for further development due to wind shear caused by the proximity of the outflow of Typhoon Meranti.^[214] However the JMA upgraded Malakas to a typhoon three hours later.^[215] With improving conditions, it was reported that a cold dense overcast was forming and the JTWC upgraded Malakas to a Category 1 typhoon during the next day.^[216]

By September 15, Malakas was in very favorable conditions, with sea surface temperature (SSTs) at nearly 30 °C (86 °F) and was later upgraded to a Category 2 typhoon.^[217][218] After maintaining this intensity for six hours, satellite imagery depicted an improved deep convection and a well-defined 10 nmi (19 km; 12 mi) eye feature, as Malakas rapidly intensified into a Category 4 typhoon.^[219] Malakas reached its peak intensity with 1-minute sustained winds of 215 km/h (130 mph) and a minimum pressure of 930 hPa (27.46 inHg). The JMA had 10-minute sustained winds of 175 km/h (110 mph) on midnight of September 17.^[220] Shortly thereafter, its eye became cloud-filled and ragged and weakened to a Category 3 typhoon.^[221] Later in that same day, Malakas further weakened to a Category 2 as satellite imagery depicted warming cloud tops, decreasing convection and SSTs of only around 28 °C (82 °F).^[222] However, by September 18, Malakas started to re-intensify as it moved east-northeastward.^[223] Malakas reached its secondary peak intensity on September 19, but only as a Category 3 typhoon.^[224] Malakas then started to weaken due to land interaction with Japan.^[225] On September 20, the JTWC downgraded Malakas to a tropical storm,^[226] while the JMA downgraded it to a severe tropical storm.^[227] Both agencies issued their final advisory later that day as it became extratropical.^[228][229]

At around 00:00 JST on September 20 (15:00 UTC on September 19), Malakas made landfall over the Ōsumi Peninsula in Japan.^[230] 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).^[231][232]

Typhoon Megi (Helen)

Typhoon (JMA)
Category 3 typhoon (SSHWS)
Duration	September 22 – September 29
Peak intensity	155 km/h (100 mph) (10-min)  945 hPa (mbar)

During September 21, the JMA started to monitor a tropical depression about 722 km (449 mi) east-southeast of Guam.^[233][234] After steady organization, the system began to intensify, in which the JMA had upgraded the depression to a tropical storm, with the name Megi on September 23.^[235] In the same time, the JTWC started issuing advisories with the designation of 20W,^[236] and later upgrading it to a tropical storm too in their next advisory.^[237] Due to improved banding, the JMA had upgraded Megi to a severe tropical storm.^[238][239] After Megi had developed an eye, both agencies upgraded Megi to a typhoon.^[240][241] Shortly thereafter, PAGASA had stated that Megi had entered their area of responsibility, prompting the local name Helen.^[242] Despite in good and favorable conditions, imagery indicated a slight diurnal weakening on Megi until September 25.^[243]

After a day with only slight intensification, Megi started to undergo an eyewall replacement cycle. From then on, Megi rapidly intensified as it neared the coase of Taiwan.^[244][245] Megi reached peak intensity as a Category 3 typhoon over Taiwan with 10-minute sustained winds of 155 km/h (100 mph) with a minimum barometric pressure of 940 mbar late on September 26.^[246] Early on September 27, Megi made landfall over Hualien City.^[247] Hours later, Megi significantly weakened due to the mountainous terraces of Taiwan, as the typhoon emerged to the Taiwan Strait.^[248] Megi made landfall over in Hui'an County of Quanzhou during the next day.^[249] In the same time, JMA downgraded Megi to a severe tropical storm,^[250] while the JTWC issued its final advisory.^[251] Megi continued its weakening trend until 12 hours later, when the JMA issued its final advisory.^[252] The JMA, however, tracked it until September 29.

Typhoon Chaba (Igme)

Typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	September 24 – October 5
Peak intensity	215 km/h (130 mph) (10-min)  905 hPa (mbar)

On September 24, a weak tropical depression had developed approximately 1,445 km (898 mi) east-northeast of Guam.^[253][254] Despite being located in marginally favorable environments with an exposed LLCC, the JMA had already upgraded the system to a tropical storm and assigned it the name Chaba late the next day.^[255][256] Early on September 28, the JTWC gave the identifier of 21W.^[257] Flaring convection and improved overall convective structure prompted the JTWC to upgrade it to a tropical storm.^[258] By September 30, Chaba had intensified into a severe tropical storm after deep convection had evolved into a banding feature, under very favorable conditions such as very low wind shear and SSTs of about 30 degrees.^[259][260] During October 1, Chaba had entered the Philippine area of responsibility, with PAGASA prompting the local name Igme, as it started to move in a northwestward direction.^[261] Several hours later, both agencies upgraded Chaba to a typhoon after its organization and structure had vastly improved.^[262][263] During the next day, Chaba became more symmetric as feeder bands wrapped into its deep central convection, signalling the onset of explosive intensification.^[264]

Early on October 3, Chaba reached Category 5 super typhoon intensity with a sharp 5 nmi (9.3 km; 5.8 mi) wide eye surrounded by a very intense convective core due to very warm SSTs.^[265] Chaba reached its peak intensity with 10-minute sustained winds of 215 km/h (130 mph), while 1-minute sustained winds were at 270 km/h (165 mph), and the minimum central pressure was 905 mbar.^[266] Thereafter, the JTWC stated that Chaba began to weaken as its core became asymmetric,^[267] and Chaba weakened to a strong Category 4 typhoon by October 4.^[268] Later, significant weakening led the JTWC to downgrade Chaba further to a Category 2 typhoon, due to interaction with strong wind shear.^[269] As it neared the coast of Busan, South Korea, Chaba started to undergo extratropical transition and the JTWC issued its final advisory a few hours later as it was downgraded to a tropical storm.^[270][271] In the same time, the JMA downgraded Chaba to a severe tropical storm.^[272] Six hours later, the JMA issued its final advisory, as Chaba transitioned into an extratropical cyclone.^[273]

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.^[274]

Typhoon Songda

Typhoon (JMA)
Category 4 super typhoon (SSHWS)
Duration	October 4 (Entered basin) – October 13
Peak intensity	185 km/h (115 mph) (10-min)  925 hPa (mbar)

A tropical disturbance entered the basin from the Central Pacific late on October 3. Early the next day, the JMA started to track the system as a tropical depression, as it was located approximately 1,333 km (829 mi) east-southeast of Wake Island.^[275][276] After moving westward for days with little to no strength, the depression finally organized with deep convection, as the JTWC started issuing advisories with the designation of 23W, on October 8.^[277] Few hours later, 23W had intensified into a tropical storm, with the JMA giving the name Songda.^[278][279] By October 9, satellite showed that Songda had a defined center with tightly-curved banding.^[280] Later, Songda entered in an area of very low vertical wind shear and warm SSTs of around 29 °C (84 °F) as animations showed a microwave eye feature.^[281] The JMA upgraded Songda to a severe tropical storm.^[282] Six hours later, satellite imagery depicted that Songda's LLCC was rapidly consolidating with deep convective banding, and Songda intensified into a typhoon.^[283][284] Songda started to undergo rapid deepening with a ragged eye forming as the JTWC upgraded it to a Category 2 typhoon.^[285]

As its eye became clearer, Songda intensified into a Category 3 typhoon.^[286] However the structure of Songda deteriorated with its eye becoming smaller six hours later maintaining its strength due to moderate to high vertical shear.^[287] After a day at the same intensity, and as Songda started to move in a northeastward direction, Songda rapidly intensified into a Category 4 super typhoon, despite 25-30 kt vertical wind shear.^[288] Songda reached its peak intensity early on October 12, with 10-minute sustained winds of 185 km/h (115 mph) and a minimum pressure of 925 mbar.^[289] Shortly thereafter, Songda had rapidly weakened as it started to interact with high shear as its eye became cloud-filled.^[290] The JTWC issued its final advisory as a rapidly-weakening Category 3 storm as it was already embedded with the deep mid-latitude westerlies and located in cooler waters of 26 °C (79 °F).^[291] The JMA downgraded Songda to a severe tropical storm as it issued its final advisory on October 13, and transitioned into an extratropical cyclone.^[292]

Severe Tropical Storm Aere (Julian)

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	October 4 – October 14
Peak intensity	110 km/h (70 mph) (10-min)  975 hPa (mbar)

Shortly after the JMA had started tracking Songda, another tropical depression had developed well east to the Babuyan Group of Islands.^[293][294] Later that day, PAGASA had named the system Julian.^[295] The JTWC started issuing advisories on the system while it moved westward during October 5, with the designation of 22W.^[296] Despite Julian having a disorganised structure while crossing the Luzon Strait, the system was under light to moderate wind shear and very warm sea surface temperatures.^[297] After satellite imagery had depicted a significant increase of convection, all agencies upgraded Julian to a tropical storm, with the JMA naming it as Aere.^[298][299] On October 7, improving convection of the compact system with a well-defined and an intense band of convection wrapping into it caused the JMA to upgrade the system into a tropical storm.^[300][301] Hours later, when Aere had emerged to the extreme northern part of the South China Sea, Aere reached peak intensity with 10-minute winds of 110 km/h (70 mph), just shy of typhoon strength, after it remained nearly stationary between two subtropical ridges.^[302][303] Shortly thereafter, due to remaining in almost the same area for hours, Aere began to weaken and JMA downgraded it to a tropical storm.^[304][305] By October 10, Aere's LLCC became exposed due to southwesterly wind shear and both the JMA and JTWC issued their final advisory three hours later.^[306][307] The JMA tracked its remnants as it moved southwestward until it weakened to a low-pressure area late on October 11.^[308]

On October 13, the well-marked low pressure area of Aere re-generated into a tropical depression.^[309] The JTWC re-issued advisories too.^[310] Now moving westward, Aere had flaring convection with weak banding and was located in an area of high SSTs and low wind shear.^[311] Although the system had failed to re-organize into a weak tropical storm, the JTWC issued its final advisory and shortly thereafter it made landfall several kilometers north of Da Nang, Vietnam.^[312] The remnants of Aere was tracked by the JMA as a weak tropical depression until it fully dissipated on October 14.^[313] Most of the damages were reported mainly in Vietnam, especially in the central region, where estimated damages for transport works were at 130 billion ₫ (US$5.83 million).^[314] 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.^[315][316] In total, flooding by the storm caused ₫ 2.5 trillion (US$111 million) of damage.^[14]

Typhoon Sarika (Karen)

Typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	October 13 – October 19
Peak intensity	175 km/h (110 mph) (10-min)  935 hPa (mbar)

On October 11, the JMA started to issue advisories on a tropical depression located about 1,200 km (750 mi) east-southeast of Manila, Philippines.^[317][318] By the next day, organization continued and the JTWC subsequently upgraded the system to a tropical depression with the designation of 24W.^[319] The PAGASA later declared that 24W had moved into their area of responsibility, giving it the local name Karen.^[320] By October 13, images depicted its LLCC and described it as "broad", and Karen was located in an area of high sea surface temperatures of 31 °C (88 °F).^[321] Hours later, both agencies upgraded Karen to a tropical storm, with the JMA naming it as Sarika.^[322][323] Despite the system having maintained its intensity at that time, deep convection had increased and formative banding started to wrap into its center.^[324] Sarika was upgraded into a severe tropical storm by the JMA three hours later.^[325] Several hours later, Sarika started to form an eye feature, and the JMA upgraded Sarika to a typhoon.^[326][327] After imagery had depicted a significant organisation of convection around the system, the JTWC upgraded Sarika to a Category 1 typhoon.^[328] By October 15, the JTWC stated that Sarika had expanded and deepened with a 15 nmi (28 km; 17 mi) wide ragged eye present, and upgraded it into a Category 2 typhoon.^[329] Within their next advisory, it was reported that Sarika had strengthened into a Category 3 typhoon.^[330] During that time until JTWC issues their next advisory, Sarika briefly reached its peak intensity as a Category 4 typhoon with 1-minute sustained winds of 215 km/h (130 mph) and a minimum barometric pressure of 935 mbar.^[331][332] Early on October 16, PAGASA had stated that Sarika had made landfall over in Baler, Aurora.^[333] Dramatic weakening occurred as Sarika traversed the islands, by the time the storm entered the South China Sea.^[334] After moving westward in a fast pace for two days, Sarika weakened to a severe tropical storm as it made landfall over in Hainan.^[335][336] By October 19, imagery depicted that Sarika was rapidly deteriorating as it made its final landfall over in the coastline and border of Vietnam and China, while the JTWC issued its final advisory.^[337] The JMA followed suit three hours later and dissipated in the same day.^[338][339]

Typhoon Haima (Lawin)

Typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	October 14 – October 21
Peak intensity	215 km/h (130 mph) (10-min)  900 hPa (mbar)

On October 13, the JMA started to track a weak tropical depression about 704 km (437 mi) south-southeast of Guam.^[340] The JTWC followed suite the next day, designating it 25W.^[341] Three hours later, early on October 15, the JMA stated that 25W had intensified into a tropical storm and assigned it the name Haima.^[342] 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.^[343] Three hours later, Haima intensified into a severe tropical storm.^[344] 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.

Typhoon Meari

Typhoon (JMA)
Category 2 typhoon (SSHWS)
Duration	October 31 – November 7
Peak intensity	150 km/h (90 mph) (10-min)  955 hPa (mbar)

On October 31, the JMA started to track a tropical depression about 287 km (178 mi) south of Guam.^[345][346] Late on November 2, organization had increased as the JTWC upgraded the system to a tropical depression with the identifier of 26W.^[347] The JMA, however, had upgraded 26W to a tropical storm, giving the name Meari early on the next day.^[348] With a rapidly consolidating LLCC, the JTWC followed suit of upgrading to a tropical storm.^[349] 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.^[350][351] 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.^[352][353] 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.^[354] During the course of November 6, Meari reached peak intensity only as a Category 2 with 10-minute sustained winds of 155 km/h (100 mph) and a minimum barometric pressure of 955 mbar.^[355]

Later that day, Meari started to move northeastward rapidly with a strong poleward outflow as it started to interact with high vertical wind shear.^[356] The JTWC downgraded Meari to a Category 1.^[357] On November 7, the JTWC issued its final advisory on Meari due to the fact that its convective structure had became frontal, therefore it had already transitioned into an extratropical cyclone.^[358] The JMA followed suit three hours later.^[359] Meari's extratropical remnants was later absorbed by another but larger extratropical cyclone early on November 10.

Vietnam tropical depression

Tropical depression (JMA)
Duration	November 3 – November 6
Peak intensity	55 km/h (35 mph) (10-min)  1004 hPa (mbar)

On November 3, the JMA started to monitor a tropical depression that had formed west of Sabah, Malaysia.^[360] During the next day, the depression was located over in favorable environments such as low to moderate wind shear and warm SSTs.^[361] The JMA declared that the depression reached its maximum strength with a minimum pressure of 1004 mbar,^[362] whilst in the same time the JTWC issued a "TCFA".^[363] However, due to increasing shear and land reaction, the JTWC cancelled it as it made landfall over in Southern Vietnam. The system moved westwards until it dissipated on November 6.^[364]

The depression had caused torrential rains and heavy flooding since mid October in Central and Southern Vietnam,^{[365][366][367]} damaging more than 20,000 homes.^[368] A total of 15 people were killed and total damage reached ₫1.07 trillion (US$48 million) in Vietnam from November 1, though a total of 35 have been killed since the flooding from October.^[369] Residents say that the country had their worst flooding since 2011.^[370]

Tropical Storm Ma-on

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	November 8 – November 13
Peak intensity	75 km/h (45 mph) (10-min)  998 hPa (mbar)

On November 8, the JMA started to track a tropical depression that had formed several nautical miles to the east of the Mariana Islands.^[371] Later that day, the JTWC had started initiating advisories giving it the designation 27W.^[372] 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.^[373][374] 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 shear.^[375] 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 998 mbar.^[376] Despite additional strengthening being forecast, its LLCC already became exposed and favorable conditions started to deteriorate.^[377] Both agencies downgraded Ma-on to a tropical depression and issued their final advisories,^[378][379] although, the JMA tracked Ma-on until November 13.

Tropical Depression 28W

Tropical depression (JMA)
Tropical depression (SSHWS)
Duration	November 9 – November 12
Peak intensity	55 km/h (35 mph) (1-min)  1008 hPa (mbar)

During November 9, a tropical depression had rapidly developed about 454 km (282 mi) east-northeast of Kwajalein.^[380][381] After meandering westwards, the JTWC initiated advisories with the designation of 28W on November 11.^[382] Despite forecasts of strengthening into a typhoon,^[383] the system weakened to a 25 knot system as it was located over in moderate easterly shear.^[384] The JTWC therefore issued its final advisory on November 12,^[385] although the JMA tracked 28W until it fully dissipated six hours later.^[386]

Tropical Storm Tokage (Marce)

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	November 23 – November 28
Peak intensity	85 km/h (50 mph) (10-min)  994 hPa (mbar)

Other storms

On June 23, the JMA started to monitor a broad tropical depression that had developed, about 420 km (260 mi) to the southwest of Manilla in the Philippines.^[387][388] 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.^[388] Over the next couple of days the system moved north-westwards, before the system dissipated and became a remnant area of low presure during June 25.^[389] However, the systems remnants were tracked until they made landfall on central Vietnam during June 27.^[389] The system was responsible for some heavy rainfall in Central and Southern Vietnam.^[390]

Late on July 27, the JMA very briefly monitored a weak tropical depression south of Japan.^[391] The JMA also indicated that a tropical depression had formed southeast of Japan in the afternoon on July 28, however it was downgraded to a low-pressure area early on the next day.^[392][393] The JMA upgraded a low-pressure area east of Taiwan to a tropical depression on August 6.^[394] 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.^[395][396] 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.^{[396][397][398]} The system subsequently continued moved westwards, before it was last noted as it made landfall on southern China later that day.^[399]

During August 12 a tropical depression developed near the coast of Taiwan, about 160 km (100 mi) to the southeast of Taipei.^[400] The system subsequently made landfall on the island, before it was last noted during the next day as it dissipated over Taiwan.^[401] A tropical depression briefly appeared over the Gulf of Tonkin early on August 16.^[402] A tropical depression persisted east of the Northern Mariana Islands in the afternoon of August 17.^[112] The system was last noted early on the next day and led to the formation of Tropical Storm Kompasu.^[403] During August 24, two tropical depressions briefly developed; one in the South China Sea, and one over to the northeast of the Mariana Islands.^[404] However, the system over the South China Sea briefly developed into a tropical depression twice on August 25 and 27. A tropical depression formed north of Wake Island early on August 30, and it became extratropical on the next day.^[405][406] On October 15, the JMA reported that a tropical depression had entered the basin from the Central Pacific.^[407] The system moved in a westward direction until dissipating several hours later on the same day.^[408]

On November 1, the JMA started to track a tropical depression about 704 km (437 mi) east of Andersen Air Force Base, Guam.^[409][410] Later that same day, the JMA started issuing advisories on the depression whilst the JTWC had issued a Tropical Cyclone Formation Alert,^[411][412] though they canceled it early on November 2.^[413] The system moved northward until the JMA issues its final advisory as it interacted with the outer rainbands of the nearby Typhoon Meari and became extratropical on November 4.^[414]

Storm names

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.^[415] 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).^[416] 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.^[415] The names of significant tropical cyclones are retired, by both PAGASA and the Typhoon Committee.^[416] 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.

International names

A tropical cyclone is named when it is judged to have 10-minute sustained windspeeds of 65 km/h (40 mph).^[417] 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.^[418] The next 28 names on the naming list are listed here along with their international numeric designation, if they are used. During the season, the name Rai was used for the first time; it replaced Typhoon Fanapi following the 2010 season.

Nepartak (1601) Lupit (1602) Mirinae (1603) Nida (1604) Omais (1605) Conson (1606) Chanthu (1607)

Dianmu (1608) Mindulle (1609) Lionrock (1610) Kompasu (1611) Namtheun (1612) Malou (1613) Meranti (1614)

Rai (1615) Malakas (1616) Megi (1617) Chaba (1618) Aere (1619) Songda (1620) Sarika (1621)

Haima (1622) Meari (1623) Ma-on (1624) Tokage (1625) Nock-ten (unused) Muifa (unused) Merbok (unused)

Philippines

This season, PAGASA will use its own naming scheme, that will either develop within or move into their self-defined area of responsibility.^[419][420] The names were taken from a list of names, that was last used during 2012 and are scheduled to be used again during 2020.^[419] All of the names are the same except for Pepito, which replaced the name Pablo after it was retired.^[419] 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.

Ambo Butchoy (1601) Carina (1604) Dindo (1610) Enteng (1612)

Ferdie (1614) Gener (1616) Helen (1617) Igme (1618) Julian (1619)

Karen (1621) Lawin (1622) Marce (1625) Nina (unused) Ofel (unused)

Pepito (unused) Quinta (unused) Rolly (unused) Siony (unused) Tonyo (unused)

Ulysses (unused) Vicky (unused) Warren (unused) Yoyong (unused) Zosimo (unused)

Auxiliary list

Alakdan (unused) Baldo (unused)

Clara (unused) Dencio (unused)

Estong (unused) Felipe (unused)

Gomer (unused) Heling (unused)

Ismael (unused) Julio (unused)

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.

Name	Dates active	Peak classification	Sustained wind speeds	Pressure	Land areas affected	Damage (USD)	Deaths	Refs
01W	01 !May 26 – 27	0 !Tropical depression	045 !45 km/h (30 mph)[P 1]	0998 !998 hPa (29.47 inHg)	South China	5000000000000000000♠ Unknown	None
TD	02 !June 23 – 25	0 !Tropical depression	055 !55 km/h (35 mph)	1006 !1006 hPa (29.71 inHg)	Philippines, Vietnam	5000000000000000000♠ None	None
Ambo	03 !June 26 – 28	0 !Tropical depression	055 !55 km/h (35 mph)	1004 !1004 hPa (29.65 inHg)	Philippines, South China	5000000000000000000♠ None	None
Nepartak (Butchoy)	04 !July 2 – 10	3 !Typhoon	205 !205 km/h (125 mph)	0900 !900 hPa (26.58 inHg)	Philippines, Ryukyu Islands, Taiwan, East China	7009151540000000000♠$1.52 billion	86	[421][422][423]
03W	05 !July 15 – 20	0 !Tropical depression	045 !45 km/h (30 mph)[P 1]	1006 !1006 hPa (29.71 inHg)	Ryukyu Islands	5000000000000000000♠ None	None
Lupit	06 !July 22 – 24	1 !Tropical storm	075 !75 km/h (45 mph)	1000 !1000 hPa (29.53 inHg)	None	5000000000000000000♠ None	None
Mirinae	07 !July 25 – 28	2 !Severe tropical storm	100 !100 km/h (65 mph)	0980 !980 hPa (28.94 inHg)	South China, Vietnam, Laos	7008334000000000000♠$334 million	5	[62][64]
TD	08 !July 27	0 !Tropical depression	045 !Not specified	1006 !1006 hPa (29.71 inHg)	None	5000000000000000000♠ None	None
TD	09 !July 28 – 29	0 !Tropical depression	045 !Not specified	1008 !1008 hPa (29.77 inHg)	None	5000000000000000000♠ None	None
Nida (Carina)	10 !July 29 – August 3	2 !Severe tropical storm	110 !110 km/h (70 mph)	0975 !975 hPa (28.79 inHg)	Philippines, Taiwan, South China, Vietnam	7007890000000000000♠$89 million	4	[64][424]
Omais	11 !August 2 – 9	2 !Severe tropical storm	110 !110 km/h (70 mph)	0975 !975 hPa (28.79 inHg)	Mariana Islands, Japan, Russian Far East	5000000000000000000♠ None	None
TD	12 !August 6 – 9	0 !Tropical depression	045 !Not specified	0998 !998 hPa (29.47 inHg)	Ryukyu Islands, East China	5000000000000000000♠ None	None
Conson	13 !August 7 – 15	1 !Tropical storm	085 !85 km/h (50 mph)	0985 !985 hPa (29.09 inHg)	Japan, Russian Far East	5000000000000000000♠ None	None
TD	14 !August 10 – 12	0 !Tropical depression	045 !Not specified	1000 !1000 hPa (29.53 inHg)	Ryukyu Islands, Taiwan, East China	5000000000000000000♠ None	None
Chanthu	15 !August 12 – 17	2 !Severe tropical storm	100 !100 km/h (65 mph)	0980 !980 hPa (28.94 inHg)	Japan, Russian Far East	5000000000000000000♠ None	None
TD	16 !August 12 – 13	0 !Tropical depression	045 !Not specified	1002 !1002 hPa (29.59 inHg)	Taiwan	5000000000000000000♠ None	None
Dianmu	17 !August 15 – 20	1 !Tropical storm	075 !75 km/h (45 mph)	0980 !980 hPa (28.94 inHg)	South China, Vietnam, Laos, Myanmar, Bangladesh, India	7006690000000000000♠$6.9 million	9	[425]
TD	18 !August 16	0 !Tropical depression	045 !Not specified	0996 !996 hPa (29.41 inHg)	South China, Vietnam	5000000000000000000♠ None	None
Mindulle	20 !August 17 – 23	3 !Typhoon	120 !120 km/h (75 mph)	0975 !975 hPa (28.79 inHg)	Mariana Islands, Japan	5000000000000000000♠ Unknown	2	[426]
Lionrock (Dindo)	19 !August 17 – 30	3 !Typhoon	165 !165 km/h (105 mph)	0940 !940 hPa (27.76 inHg)	Japan, Russia, Northeast China, North Korea	7008325000000000000♠$325 million	550+	[427]
TD	21 !August 17 – 18	0 !Tropical depression	045 !Not specified	1000 !1000 hPa (29.53 inHg)	None	5000000000000000000♠ None	None
Kompasu	22 !August 18 – 21	1 !Tropical storm	065 !65 km/h (40 mph)	0994 !994 hPa (29.35 inHg)	Japan, Russian Far East	5000000000000000000♠ None	1
14W	23 !August 23 – 24	0 !Tropical depression	055 !55 km/h (35 mph)	1000 !1000 hPa (29.53 inHg)	Mariana Islands	5000000000000000000♠ None	None
TD	24 !August 24	0 !Tropical depression	045 !Not specified	1002 !1002 hPa (29.59 inHg)	None	5000000000000000000♠ None	None
TD	25 !August 24	0 !Tropical depression	045 !Not specified	1004 !1004 hPa (29.65 inHg)	None	5000000000000000000♠ None	None
TD	26 !August 25	0 !Tropical depression	045 !Not specified	1002 !1002 hPa (29.59 inHg)	None	5000000000000000000♠ None	None
TD	27 !August 27	0 !Tropical depression	045 !Not specified	1006 !1006 hPa (29.71 inHg)	None	5000000000000000000♠ None	None
TD	28 !August 30 – 31	0 !Tropical depression	045 !Not specified	1004 !1004 hPa (29.65 inHg)	None	5000000000000000000♠ None	None
Namtheun (Enteng)	29 !August 31 – September 5	3 !Typhoon	130 !130 km/h (80 mph)	0955 !955 hPa (28.20 inHg)	Japan	5000000000000000000♠ None	None
Malou	30 !September 5 – 7	1 !Tropical storm	075 !75 km/h (45 mph)	1000 !1000 hPa (29.53 inHg)	Japan	5000000000000000000♠ None	None
Meranti (Ferdie)	31 !September 9 – 16	3 !Typhoon	220 !220 km/h (140 mph)	0890 !890 hPa (26.28 inHg)	Mariana Islands, Philippines, Taiwan, China	7009263213000000000♠$2.63 billion	30	[428][429]
17W	32 !September 11 – 12	0 !Tropical depression	045 !55 km/h (35 mph)[P 1]	1000 !1000 hPa (29.53 inHg)	None	5000000000000000000♠ None	None
Rai	33 !September 11 – 13	1 ! Tropical storm	065 !65 km/h (40 mph)	0996 !996 hPa (29.41 inHg)	Vietnam, Cambodia, Laos, Thailand	7007373000000000000♠$37.3 million	12
Malakas (Gener)	34 !September 11 – 20	3 !Typhoon	175 !175 km/h (110 mph)	0930 !930 hPa (27.46 inHg)	Mariana Islands, Taiwan, Japan	7008738900000000000♠$739 million	2	[430][431]
Megi (Helen)	35 !September 22 – 29	3 !Typhoon	155 !155 km/h (100 mph)	0945 !945 hPa (27.91 inHg)	Caroline Islands, Ryukyu Islands, Taiwan, China	7008944700000000000♠$945 million	24	[432][433]
Chaba (Igme)	36 !September 24 – October 5	3 !Typhoon	215 !215 km/h (130 mph)	0905 !905 hPa (26.73 inHg)	Mariana Islands, Japan, South Korea	7007183000000000000♠$18.3 million	7	[274]
Songda	37 !October 4 – 13	3 !Typhoon	185 !185 km/h (115 mph)	0925 !925 hPa (27.32 inHg)	None	5000000000000000000♠ None	None
Aere (Julian)	38 !October 4 – 14	2 !Severe tropical storm	110 !110 km/h (70 mph)	0975 !975 hPa (28.79 inHg)	Philippines, Taiwan, South China, Vietnam, Laos, Cambodia, Thailand	7008112000000000000♠$112 million	35	[14]
Sarika (Karen)	39 !October 13 – 19	3 !Typhoon	175 !175 km/h (110 mph)	0935 !935 hPa (27.61 inHg)	Philippines, South China, Vietnam	7008756700000000000♠$757 million	34	[434][435][436]
Haima (Lawin)	40 !October 14 – 21	3 !Typhoon	215 !215 km/h (130 mph)	900 !900 hPa (26.58 inHg)	Caroline Islands, Philippines, Taiwan, China, Japan	7009192729000000000♠$1.93 billion	7001190000000000000♠19	[436][437][438][439][440][441]
TD	41 !October 15	0 !Tropical depression	045 !Not specified	1008 !1008 hPa (29.77 inHg)	None	5000000000000000000♠ None	None
Meari	42 !October 31 – November 7	3 !Typhoon	150 !150 km/h (90 mph)	0955 !955 hPa (28.20 inHg)	Mariana Islands	5000000000000000000♠ None	None
TD	43 !November 1 – 4	0 !Tropical depression	055 !55 km/h (35 mph)	1000 !1000 hPa (29.53 inHg)	Mariana Islands	5000000000000000000♠ None	None
TD	44 !November 3 – 6	0 !Tropical depression	055 !55 km/h (35 mph)	1004 !1004 hPa (29.65 inHg)	Borneo, Vietnam, Cambodia	7007480000000000000♠$48 million	15	[369][442]
Ma-on	45 !November 8 – 13	1 !Tropical storm	075 !75 km/h (45 mph)	0998 !998 hPa (29.47 inHg)	None	None	None
28W	46 !November 9 – 12	0 !Tropical depression	045 !55 km/h (35 mph)[P 1]	1008 !1008 hPa (29.77 inHg)	Marshall Islands	5000000000000000000♠ None	None
Tokage (Marce)	47 !November 23 – 28	1 !Tropical storm	085 !85 km/h (50 mph)	0994 !994 hPa (29.29 inHg)	Philippines	7004302000000000000♠$30.2 thousand	None	[443]
Season Aggregates
47 systems	May 26 – Season ongoing		220 km/h (140 mph)	890 hPa (26.28 inHg)		7009948565020000000♠$9.49 billion	835

Notes

See also

• 2016 Atlantic hurricane season
• 2016 Pacific hurricane season
• 2016 North Indian Ocean cyclone season
• South-West Indian Ocean cyclone seasons: 2015–16, 2016–17
• Australian region cyclone seasons: 2015–16, 2016–17
• South Pacific cyclone seasons: 2015–16, 2016–17
• South Atlantic tropical cyclone

References

External links

Wikimedia Commons has media related to 2016 Pacific typhoon season.

• Japan Meteorological Agency
• China Meteorological Agency
• Digital Typhoon
• Hong Kong Observatory
• Joint Typhoon Warning Center
• Korea Meteorological Administration
• National Weather Service Guam
• Malaysian Meteorological Department
• Philippine Atmospheric, Geophysical and Astronomical Services Administration
• Taiwan Central Weather Bureau
• TCWC Jakarta (Indonesian)
• Thai Meteorological Department (Thai)
• Typhoon2000
• Vietnam's National Hydro-Meteorological Service