NOTE #1: IT IS HIGHLY RECOMMENDED TO VIEW THIS PAGE IN "DESKTOP PAGE MODE" IF YOU ARE ON MOBILE AS THE FORMATTING, ESPECIALLY IN THE "SEASON EFFECTS" PART, MAY BREAK IF YOU VIEW THIS AS A DEFAULT MOBILE SITE. NOTE #2: THIS PAGE IS CAREFULLY MONITORED. ANY NONCONSTRUCTIVE EDITS TO THIS ARTICLE WILL BE PROMPTLY REVERTED. NOTE #3: LOTS OF EFFORT USED. PLEASE ENJOY!
The 2066 Pacific typhoon season was an average season in terms of both named storms and accumulated cyclone energy (ACE) index. The season ended a three year streak of above average seasons that started in 2063, and it had a late start for Pacific typhoon seasons, a characteristic typical of years that featured a developing La Niña event after a subsided strong El Niño event. This year saw several intense storms, with Typhoon Shuixian in late October reaching peak intensity with a minimum pressure of 877 hPa (25.90 inHg) and becoming one of the most intense tropical cyclones on record. This also marked the second consecutive year at which the Northwestern Pacific Ocean managed to produce storms with minimum central pressures below 880 hPa (25.99 inHg). The season runs throughout 2066, though most tropical cyclones typically develop between May and October. The season's first named storm, Merbok, developed on May 16, and eventually intensified into the first typhoon of the season, while the last named storm, Sanba, dissipated on December 31. This season was an event in the annual cycle of tropical cyclone formation in the western Pacific Ocean.
The scope of this article is limited to the Pacific Ocean to the north of the equator between 100°E and 180th meridian. Within the northwestern Pacific Ocean, there are two separate agencies that assign names to tropical cyclones which can often result in a cyclone having two names. The Japan Meteorological Agency (JMA) will name a tropical cyclone should it be judged to have 10-minute sustained wind speeds of at least 65 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) are given a number with a "W" suffix; W meaning west, a reference to the western Pacific region.
Seasonal forecasts[]
| TSR forecasts Date |
Tropical storms |
Total Typhoons |
Intense TCs |
ACE |
|---|---|---|---|---|
| Average (1966–2065) | 25.7 | 15.9 | 8.8 | 294 |
| May 7, 2066 | 23 | 13 | 6 | 209 |
| July 6, 2066 | 24 | 14 | 7 | 245 |
| August 8, 2066 | 24 | 14 | 7 | 241 |
| Other forecasts Date |
Forecast Center |
Period | Systems | |
| January 13, 2066 | PAGASA | January — March | 1–2 tropical cyclones | |
| January 13, 2066 | PAGASA | April — June | 1–3 tropical cyclones | |
| June 30, 2066 | PAGASA | July — September | 5-12 tropical cyclones | |
| June 30, 2066 | PAGASA | October — December | 4-8 tropical cyclones | |
| Forecast Center |
Tropical cyclones |
Tropical storms |
Typhoons | |
| Actual activity: | JMA | 45 | 28 | 14 |
| Actual activity: | JTWC | 31 | 26 | 16 |
| Actual activity: | PAGASA | 20 | 17 | 12 |
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, Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA), Vietnam's National Center for Hydro-Meteorological Forecasting and Taiwan's Central Weather Bureau.
The first forecast was released by PAGASA on January 13, 2066, in their monthly seasonal climate outlook predicting the first half of 2066. They predicted that 1-2 tropical cyclones would form or enter the Philippine Area of Responsibility between January and March, while 1-3 tropical cyclones were expected to form between April and June. PAGASA also stated that weakening El Niño conditions could last in the first half of 2066 until La Niña conditions start to develop later in the year.
Tropical Storm Risk (TSR) released their first forecast on May 7, predicting below average activity with 23 named storms, 13 typhoons and 6 intense typhoons. This was primarily due to the dominant El Niño event at the time, which was expected to transition into a weak or moderate La Niña by mid-2066. TSR released their early July forecast on July 6, where they slightly increased the predicted number of tropical storms, typhoons and intense typhoons, mentioning a rather active start compared to previous analog years. On August 8, TSR released their final forecast for the season, retaining the same number of storms, typhoons and intense typhoons. However, they slightly decreased the predicted ACE index compared to their July forecast.
Season summary[]
JMA's seasonal timeline
JTWC's seasonal timeline
Despite the season's late start, the 2066 season was a normal season with a total of 45 tropical depressions, of which 28 became tropical storms according to the JMA. Compared to the 2065 season, the average location of tropical cyclonegenesis were significantly shifted towards the northwest, leading to a lower proportion of long-lived and intense storms but a higher rate of occurrence for storms that impact land.
Early season activity[]
.png){kind=link}
Merbok rapidly intensifying off the coast of the Philippines, on May 19.
Strong trade winds persisted over the Pacific Ocean for much of the first half of 2066. The enhanced trade winds caused the strong El Niño conditions from the 2064-66 El Niño event to gradually subside. As a result of the enhanced trade winds, wind shear over the northwestern Pacific Ocean were higher than normal, contributing to the season's late start. After four months of inactivity, the first tropical depression developed on April 7 in the South China Sea. This depression that was only recognized by the JMA moved northwestward and made a landfall over Vietnam on April 9. The first named storm of the season, Typhoon Merbok, developed on May 16 from a tropical disturbance to the southwest of Guam. The disturbance first moved west-southwestward in the Philippine Sea. Shortly after attaining tropical storm strength, Merbok started to move northwest towards the Philippines. The typhoon reached Category 4 typhoon intensity to the east of Samar on May 19, and it made its first landfall over Siruma, Camarines Sur two days later as a Category 2 typhoon. At the end, Merbok caused a total of ₱5.18 billion (US$89.3 million) of damage in the Philippines.
.png){kind=link}
Aftermath of Hodu, a collapsed billboard in Pingtung County, Taiwan.
The season then went on to have a one-month hiatus in named storms. The second named storm of the season, Tropical Storm Nanmadol, developed on July 3 and went on to affect China's Hainan Province and Vietnam. By mid July, Typhoon Hodu formed at the southeast of Guam and steadily moved northwestwards. The typhoon first brushed past the southern tip of Taiwan, then it made landfall over Zhao'an County of Fujian, China on July 16. Hodu flooded tens of thousands of acres of farmlands and knocked down power poles in the province, causing serious disruption to the economic activities in Fujian and Guangdong. All in all, Hodu caused 38 fatalities and US$6.57 billion of damage in China. By late July, Severe Tropical Storm Kulap made landfall on Hokkaido, Japan. Kulap's torrential rain induced hundreds of landslides across the island, resulting in 7 fatalities. On July 29, Hurricane Wali crossed the International Date Line as a weakening tropical depression. The storm turned extratropical one day later.
Peak season activity[]
.png){kind=link}
Roke approaching Taiwan on August 8.
In early August, a new broad low-pressure area developed into a tropical depression on August 5, over the Philippine Sea, while slowly drifting northwestward. This depression eventually became Typhoon Roke as it gradually intensified. By August 8, before landfall in Taiwan, Roke strengthened into a Category 3 typhoon due to favourable conditions. Roke then made landfall, in Nan'ao, Yilan County, Taiwan later on the same day. The mountain ranges of Taiwan made the storm weakened to a tropical storm as it was moving over the Taiwan Strait. On August 10, Roke made landfall near Xiamen, Fujian as a weakening tropical depression. Roke brought extreme rainfall to both Taiwan and China, and the typhoon became the wettest tropical cyclone for Fujian in 38 years. At the end, Roke killed 34 while bringing US$4.69 billion of damage in total.
.jpg){kind=link}
Jamjari briefly after making landfall over South Korea, on August 26.
On August 12, two areas of disturbed weather were developing in a monsoon trough that spanned from the Philippines to the Caroline Islands. The tropical disturbance on the left would develop into Typhoon Haitang, while the disturbance on the right would eventually become Typhoon Jamjari. The precursor tropical disturbance of Haitang moved west-northwest towards Luzon while gradually strengthening. On August 16, Haitang made landfall over Ilagan, Isabela as a Category 2 typhoon, causing storm surges of over 3.8 m (12.5 ft) to be recorded in Palanan Bay. On the same day, after slowly meandering northwards for a few days, the precursor tropical disturbance of Jamjari strengthened into a Category 1 typhoon as it passed through the Northern Mariana Islands. As a result, off the coast of Guam, a fishing boat was capsized due to the rogue waves generated by Jamjari. 2 fishermen lost their lives in this incident. From August 17 to 18, Jamjari entered an area with highly favourable conditions such as high oceanic heat content and low vertical wind shear. This allowed the typhoon to rapidly intensify until it reached a peak intensity with maximum 1-minute sustained winds of 260 km/h (160 mph). This made Jamjari the first super typhoon as well as the first Category 5 storm of the season. Meanwhile, a few thousands kilometres to the east, Haitang restrengthened into a typhoon in the South China Sea after temporarily weakening to a tropical storm due to its Luzon landfall. The storm eventually slammed into Wuchuan, Guangdong as a Category 1 typhoon in the early hours of August 19. After that, the remnants of Haitang moved inland and brought torrential rains to Guangxi, killing 29 in the province due to severe flooding and landslides. On the other hand, from August 19 to 24, Jamjari fluctuated between Category 2 and 4 due to multiple eyewall replacement cycles (EWRC) and subsequent periods of restrengthening. The typhoon made landfall over Okinawa on August 24 as a weakening Category 3 typhoon, causing a temporary blackout for 221,000 households on the island and numerous collapsed trees. After its Okinawa landfall, Jamjari recurved northwards and brushed past Jeju Island on early August 26 and made landfall near Incheon, South Korea around 17 hours later. Being the strongest storm to impact South Korea since Typhoon Kajiki in 2054, Jamjari caused severe impacts over the Korean Peninsula. 64 fatalities and economic damages of US$2.60 billion were reported in South Korea, while at least 61 deaths were reported in North Korea. After that, Jamjari accelerated east-northeastward and finally turned extratropical on August 27.
While Jamjari was threatening the Korean Peninsula in late August, two tropical disturbances developed in succession. The disturbance to the northeast first developed on August 25 and moved northeastwards. This disturbance would eventually strengthen into Tropical Storm Yamaneko. Meanwhile, the second tropical disturbance would develop 2 days later and become Tropical Storm Pakhar. While Yamaneko generally moved northwards and did not affect any major landmasses, Pakhar moved northwestwards and affected Japan. Pakhar made its first landfall over Taiji, Wakayama on September 2, and its second landfall over Kobe, Hyōgo around six hours later. Pakhar severely disrupted air traffic over central Japan from September 1 to 3, leading to the cancellations of 817 domestic flights 21 international flights. In a campsite near Oishihigashi, Ōtsu in the Shiga Prefecture, 4 people lost their lives from a flash flood of the Yodo River that was induced by Pakhar's enhanced rainfall. At the end, Pakhar resulted in 5 fatalities and US$136 million of damages in Japan. From September 3 onwards, Pakhar underwent extratropical transition and moved towards Russia, where strong winds associated with the Pakhar's extratropical cyclone caused the collapse of a wooden hut in Sakhalin, killing 3.
.jpg){kind=link}
Guchol over the East China Sea during its second peak.
On September 12, a tropical disturbance developed in a monsoon trough to the northeast of Northern Mariana Islands. The tropical disturbance moved northwestward and developed gradually from September 13 to 15, eventually becoming Typhoon Guchol. On September 16, Guchol was exposed to very favourable conditions for development, such as sea surface temperatures (SSTs) of nearly 30 °C (86 °F). This allowed the typhoon to rapidly intensify when it passed between Miyakojima and Okinawa on the next day. On September 18, Guchol attained its peak intensity with maximum 1-minute sustained winds of 230 km/h (145 mph) and a minimum central pressure of 927 mbar (27.37 inHg). Over the next two days, Guchol stalled over the East China Sea and weakened as it underwent an eyewall replacement cycle (EWRC). After the completion of the EWRC, Guchol recurved and strengthened again. The storm passed to the south of the Japanese Mainland as it travelled northwestward from September 21 to 22. When Guchol brushed past Kyūshū on September 21, it brought torrential rain to much of the island. In Nobeoka, Miyazaki, the recorded rainfall on September 21 in a 24-hour-period reached 614.3 mm (24.19 in). On September 23, Guchol underwent extratropical transition over the open Pacific Ocean. The storm finally dissipated 2 days later.
In late September, two tropical disturbances developed simultaneously over the open Pacific waters. The disturbance to the northeast developed first and became a tropical depression by September 29. This system eventually became a tropical storm by October 1, and was named Haebaragi by the JMA. Meanwhile, the disturbance to the southwest strengthened into a tropical depression on September 30 and also became a tropical storm on October 1, hence warranting the name Talim. Over the next few days, as the distance between the two systems decreased to below 1,500 km (932 mi), Haebaragi and Talim interacted with each other in a phenomenon called the Fujiwhara effect. This caused Haebaragi to move southwestward and Talim to move northeastward in the period from October 2 to 5. During this time, both systems reached their maximum intensities; with Haebaragi becoming a minimal Category 1 typhoon, and Talim peaking as a Category 3 typhoon. As the distance between the two storms increased sufficiently after October 5, both Haebaragi and Talim started to recurve predictably. On October 7, Haebaragi made landfall over the Amami Ōshima as a tropical storm. It then made multiple landfalls over the Gotō Islands on the next day as it traversed the Korea Strait. As for Talim, the system made landfall over the northern tip of Okinawa on October 8 as a Category 1 typhoon. It then moved northwards and made another landfall near South Korea's Goseong County, South Gyeongsang by late October 9 as a strong tropical storm. In South Korea, Talim caused 3 deaths and economic damages of US$372 million. While in North Korea, rainfall from Talim exceeded 400 mm (15.74 in) in 24 hours in Kangwon Province. This resulted in flash flooding in Ichon County, killing 39 people in the area. On October 10, both Haebaragi and Talim underwent extratropical transition; then both systems dissipated a few days later.
Late season activity[]
.jpg){kind=link}
Khanun after making landfall over Taiwan.
On October 7, a tropical disturbance developed over the Philippine Sea, to the west of the Northern Mariana Islands. The disturbance moved southwards first, and then it took a more northwesterly track after October 9. The system gradually strengthened and was named Khanun by the JMA on October 11. Three days later, Typhoon Khanun made landfall in Taitung City, Taiwan near peak intensity as a Category 2 typhoon. Khanun brought torrential rain over most of Taiwan; the eastern portions of Hualien and Taitung counties received around 300 mm (11.8 in) of rain from the typhoon. The storm also knocked down power poles, leading to 31,000 houses in Taiwan losing power. After its Taiwan landfall, Khanun crossed the Taiwan Strait and made another landfall over Shishi, Fujian by late October 14. Khanun caused extensive destruction over the provinces of Fujian and Guangdong, leaving ¥22.1 billion (US$3.05 billion) in economic losses and killed 11 in these two provinces. The storm then continued to move inland and weakened. Khanun finally dissipated on October 18 over Northern Vietnam.
.jpg){kind=link}
Trau on October 24, shortly after its peak.
On October 14, when Khanun was about to make landfall in Fujian, a mid-level circulation developed in a tropical upper tropospheric trough (TUTT) to the east of the Philippines. The circulation built toward the surface, and on the next day the system developed a low-level circulation with scattered associated convection. This caused the disturbance to strengthen into a tropical depression and eventually Tropical Storm Trau on October 16. As the TUTT weakened the subtropical ridge to the storm's east, Trau started to move northeastward over the open Pacific Ocean to the south of Japan. Trau strengthened into a typhoon on October 18, and eventually attained its first peak as a strong Category 4 typhoon two days later. However, an eyewall replacement cycle (EWRC) caused it to weaken to a Category 2 typhoon temporarily. After the completion of the EWRC, Trau restrengthened and attained an even stronger second peak on October 23, with maximum 1-minute sustained winds of 240 km/h (150 mph) and a minimum central pressure of 925 mbar (27.32 inHg), making it the second super typhoon of the season. After this point, Trau entered colder waters, leading to its waning convection and weakening. While the typhoon was initially expected to continue its northeast movement, a development of a trough to the storm's East caused Trau to unexpectedly turn due-eastward on October 26. After briefly strengthening back to a Category 2 typhoon, Trau weakened again after October 27 due to increasing wind shear and dry air intrusion. The storm weakened to a tropical storm 3 days later and resumed its northeastward movement due to the weakening of the trough. On October 31, Trau transitioned to an extratropical cyclone as it moved near the Aleutian Islands.
.png){kind=link}
Shuixian making landfall over Luzon at peak intensity, on early October 29.
When Trau first became a typhoon on October 18, two circulations developed within a monsoon trough that extended from the Philippine Sea to the Caroline Islands. Both circulations developed steadily, and the disturbance to the west strengthened to a tropical depression first on October 20 according to the JMA. Meanwhile, the disturbance to the east developed into a tropical depression two days later. On October 23, as the western disturbance moved steadily northwestward and strengthened, the JMA further upgraded the system to a tropical storm and named it Damrey. However, the JTWC never upgraded Damrey to a tropical storm during its lifetime. On the other hand, on October 24, the eastern disturbance continued to deepen, causing both the JMA and JTWC to upgrade it to a tropical storm within the next 24 hours. As a result, the eastern system acquired the name Shuixian. At around the same time, as the distance between Shuixian and Damrey rapidly decreased, wind shear brought by Shuixian's extensive inflow caused Damrey to rapidly weaken. Eventually, by early October 25, Damrey moved towards Shuixian and eventually got absorbed into the outer rainbands of Shuixian. After this, Shuixian continued to steadily develop, until it entered a phase of rapid intensification due to extremely favourable conditions over the Philippine Sea on October 27. In the early hours of October 28, Shuixian reached Category 5 super typhoon status, making it the third super typhoon as well as the second Category 5 storm of the season. The typhoon continued to intensity over the next 24 hours as it approached the Philippines, until it reached a peak with maximum 1-minute sustained winds of 305 km/h (190 mph) and a minimum central pressure of 877 mbar (25.90 inHg) by early October 29. At 02:00 UTC on the same day, Shuixian made landfall over Maconacon, Isabela of Luzon at peak intensity, making it the strongest landfalling cyclone over the Philippines since Typhoon Bang-Lang in 2049. Shuixian brought torrential rain over Luzon, especially in mountainous regions. In the municipality of Bakun, Benguet, the 1,000-millimetre (39-inch) rain gauge overflowed; and in nearby Bokod, the accumulated rainfall recorded reached 1,309 mm (51.5 in) on October 29 alone, making it a one-in-3,611-year event according to statistical models. Apart from severe flooding, Shuixian knocked down trees and power lines, causing 670,000 households to lose power in Luzon. Along its path, the typhoon destroyed 19,650 houses and damaged another 87,903. Overall, Shuixian killed 127 people in the Philippines, mostly caused by landslides, while injuring another 85. Total damage in the country was estimated at ₱150.2 billion (US$2.59 billion). In the late hours of October 29, Shuixian moved off the coast of Luzon and entered the South China Sea as a Category 1 typhoon. Over the next day, the storm slowed down and eventually turned northwards due to a trough at the typhoon's north. On October 31, Shuixian restrengthened to a Category 3 typhoon temporarily due to favourable conditions in the South China Sea, such as low vertical wind shear and sea surface temperatures (SSTs) of 29 °C (84 °F) to 30 °C (86 °F). One day later, on November 1, Shuixian made landfall over Huilai County, Guangdong as a strong Category 1 typhoon. Shuixian brought severe impacts to the Chinese provinces of Guangdong and Fujian; a total of 119,850 hectares of crops and 1,804 houses were destroyed by the storm in these two provinces, with total fatalities and overall economy losses incurred there reaching 41 and CN¥136 billion (US$18.79 billion) respectively. After its China landfall, Shuixian rapidly weakened as it recurved. The storm emerged into the East China Sea as a tropical depression by late November 2, and the system dissipated on November 4 after crossing the Ryukyu Islands.
.jpg){kind=link}
Kirogi at its peak, over the open Pacific Ocean.
Not long after Shuixian made its landfall over Luzon at peak intensity, a weak tropical disturbance entered the West Pacific from the Central Pacific late on October 29. The disturbance was promptly marked as a tropical depression by the JMA within 24 hours of its entrance. However, the system's development was minimal from October 31 to November 1 due to the marginal environment within the subsident region of a tropical upper tropospheric trough (TUTT) cell to the northwest. This brought moderate vertical wind shear to the depression, causing it to often present itself with an exposed low-level circulation center (LLCC). Despite this, after November 2, lessened wind shear allowed the system to organise itself better. As a result, the JMA upgraded the system to a tropical storm and named it Kirogi on November 3, while the JTWC followed suit 12 hours later. From November 3 to 5, Kirogi moved steadily westward as it was moving along the southwest periphery of the deep-layered subtropical ridge positioned to the northeast. During this time, the storm strengthened to a typhoon as environmental conditions continued to improve. In the late hours of November 4, Kirogi entered a phase of explosive intensification due to very low vertical wind shear, decent sea surface temperatures and extremely strong poleward outflow that tapped into the Westerlies. As a result, Kirogi strengthened from a Category 1 typhoon to a Category 5 typhoon with maximum 1-minute sustained winds of 270 km/h (165 mph) and a minimum central pressure of 898 mbar (26.52 inHg) in just 12 hours. Kirogi's 120 km/h (75 mph) increase in 1-minute sustained winds and 65 mbar (1.92 inHg) drop in central pressure in this 12-hour period made it one of the fastest-intensifying tropical cyclones on record. After becoming the fourth super typhoon and the third and final Category 5 storm of the season, Kirogi started to weaken as the system encountered increasing shear when it recurved and accelerated northeastward along the poleward side of the aforementioned subtropical ridge. The storm underwent extratropical transition on November 8, and dissipated five days later near the Alaska Peninsula.
On December 2, the JTWC started to monitor a tropical depression located about 300 km (186 mi) to the east of Samar. The tropical disturbance struggled to develop at first as the warm seas and high mid-level relative humidity were offset by moderate to high vertical wind shear. However, after December 5, the lessening of wind shear allowed the system to strengthen to a tropical depression according to the JTWC. In the late hours on the same day, the JMA upgraded the system to a tropical storm, and named it Bolaven. Over the next day, Bolaven barely moved as it was trapped in an area with weak steering currents between three areas of high pressures; a subtropical ridge over the tropical Pacific to the system's east, another subtropical ridge over the Bay of Bengal to the system's west, and an area of high pressure to the system's south. On December 7, due to high vertical wind shear, Bolaven weakened to a tropical depression, while it managed to finally leave the saddle field in between the three high-pressure areas. The system moved east and made its first landfall over Benarauam Island, off the coast of Samar, as a tropical depression. It then shortly made another landfall over Arteche, Eastern Samar. Bolaven then proceeded to make multiple additional landfalls over numerous islands in Eastern Visayas, Bicol Region, Western Visayas and Mimaropa over the next two days. After leaving the Philippines, the increase of wind shear caused the system's low level circulation to become elongated, and convective activities became minimal. This caused the JTWC to issues its final warning on the system at that time, while the JMA continued to track the storm as a remnant low. From December 9 to 13, the remnants of Bolaven moved southwesterly over the South China Sea, until it strengthened to a tropical depression again shortly after passing near Côn Sơn Island due to the decrease of wind shear. However, on December 16, as wind shear picked up, Bolaven weakened to a remnant low again, and the system dissipated one day later after it made landfall over Marang, Terengganu, Malaysia. Bolaven caused multiple flash floods and landslides over the Philippines, with severe power outages reocrded in the provinces of Romblon and Marinduque. Overall, 69,138 homes were damaged, with 4,042 of them being totally destroyed. 54 people lost their lives in the country, while economic damages amounted to ₱18.12 billion (US$317 million).
.png){kind=link}
Aftermath of Sanba's landfall in Surigao del Sur, Mindanao.
On December 20, the JTWC reported that a tropical disturbance had persisted at about 450 km (280 mi) to the southwest of Satawan Atoll in the Federated States of Micronesia. The broad and poorly organised disturbance struggled to develop at first as it was affected by moderate to high vertical wind shear. However, on December 21, the lessening wind shear allowed the system to cover its low-level circulation centre (LLCC) with deep convection. As a result, both the JTWC and the JMA upgraded the system to a tropical depression that day. A few hours later, by early December 22, both agencies further upgraded the system to a tropical storm, granting it the name Sanba. Over the next two days, Sanba first tracked southwestward and then northwestward along the southern periphery of a deep-layered subtropical ridge. Its intensity fluctuated as a tropical storm during this time due to its low latitude and subsequent lack of Coriolis force. However, on December 25, as Sanba started to form an eye in microwave imagery, the storm strengthened to a Category 1 typhoon on that day when it passed within 80 km (50 mi) to the southwest of Angaur, Palau. 12 hours later, Sanba started a phase of explosive intensification due to very favourable environmental conditions, such as low vertical wind shear, excellent dual-channel outflow, and sea surface temperatures of 29 °C (84 °F) or higher. This allowed the typhoon to attain maximum 1-minute sustained winds of 250 km/h (155 mph) and a minimum central pressure of 920 mbar (27.17 inHg) by December 26, making it the fifth and final super typhoon of the season. On the same day, at 19:00 UTC, Sanba made its first landfall over Madrelino, Cortes, Surigao del Sur on the island of Mindanao as a Category 4 typhoon. It made another landfall over Cantilan, Surigao del Sur around an hour later. From December 27 to 28, Sanba made a series of landfalls in Central Visayas, Negros Island Region and Mimaropa. During this process, the storm gradually weakened to a Category 1 typhoon due to land interaction. On December 29, after passing Palawan, the surge of Northeast Monsoon brought in significant wind shear and dry air, while at the same time causing Sanba to move west-southwestward. This caused the storm to weaken rapidly as its convection was unable to develop over the fully exposed LLCC. Sanba weakened to a tropical depression on December 30, and dissipated over the South China Sea a day later. Sanba caused 245 fatalities in Mindanao alone, making it the deadliest storms to affect the island since Typhoon Barijat in 2062. In a mudslide in the mountainous town of New Bataan, Davao de Oro, 51 people lost their lives as their homes were buried and destroyed by the mud. Overall, At least 298,000 people were evacuated from their homes in the Philippines, with total economic damage and fatalities reaching ₱290.6 billion (US$5.06 billion) and 306 respectively in the nation.
Accumulated cyclone energy (ACE)[]
.png){kind=link}
ACE Progression of the 2066 Pacific typhoon season.
Accumulated cyclone energy (ACE) is a metric used to compare overall activity of tropical cyclones, utilizing the available records of windspeeds at six-hour intervals to synthesize storm duration and strength into a single index value. The ACE index may refer to a single storm or to groups of storms such as those within a particular month, a full season or combined seasons. It is calculated by summing the square of tropical cyclones' maximum sustained winds, as recorded every six hours, but only for windspeeds of at least tropical storm strength (≥ 34 kn; 63 km/h; 39 mph); the resulting figure is divided by 10,000 to place it on a more manageable scale.
According to the Tropical Storm Risk (TSR) Consortium, the 100-year norm of the ACE of Northwest Pacific typhoon season from 1966-2065 is 294, while an ACE above 333, between 246 to 333 and below 246 is defined as "above-average", "near-normal", and "below-average" respectively. The cumulative ACE for the Western Pacific in 2066 fell into the "near-normal" category. This also marked 2066 to be the first average season in terms of ACE since 2062, as the 2063 to 2065 seasons saw above average activity. 2066 was also one of the few seasons in a La Niña event after a strong El Niño that did not feature below average activity. This was likely aided by the positive Pacific decadal oscillation seen throughout the year.
The single storm which had the highest ACE was Typhoon Jamjari (Gardo), which in total accumulated 49.8375 ACE points in its lifetime. It is followed by Typhoon Trau (Neneng) and Typhoon Shuixian (Pilandok), which accumulated 43.335 and 32.035 ACE points respectively.
The following table listed out the ACE points of all the individual named storms this season, in descending order.
| Rank | Storm name | ACE value | Rank | Storm name | ACE value | |
|---|---|---|---|---|---|---|
| 1 | Jamjari (Gardo) | 49.8375 | 15 | Yun-yeung | 6.13 | |
| 2 | Trau (Neneng) | 43.335 | 16 | Talas | 6.085 | |
| 3 | Shuixian (Pilandok) | 32.035 | 17 | Mawar (Henry) | 5.1025 | |
| 4 | Guchol (Josie) | 25.2 | 18 | Nesat (Ester) | 5.0775 | |
| 5 | Talim (Kiyapo) | 19.88 | 19 | Sanvu | 3.9525 | |
| 6 | Sanba (Tomas) | 17.46 | 20 | Sonca | 3.1225 | |
| 7 | Kirogi | 17.07 | 21 | Pakhar | 2.2325 | |
| 8 | Merbok (Ada) | 14.2425 | 22 | Yamaneko | 2.0525 | |
| 9 | Hodu (Caloy) | 11.6 | 23 | Lan | 1.6575 | |
| 10 | Haitang (Francisco) | 8.8975 | 24 | Koinu (Rosal) | 1.2525 | |
| 11 | Roke (Domeng) | 8.42 | 25 | Nanmadol | 1.0175 | |
| 12 | Kulap | 7.5475 | 26 | Bolaven (Samuel) | 0.49 | |
| 13 | Haebaragi (Luis) | 7.0675 | 27 | Banyan* | 0 | |
| 14 | Khanun (Maymay) | 6.4375 | 28 | Damrey (Obet)* | 0 | |
| Sum | 307.2025 | |||||
| *Recognised by the JMA as a tropical storm but not the JTWC. | ||||||
Systems[]
Typhoon Merbok (Ada)[]
| Max 1-min winds: | 120 kt (220 km/h) |
|---|---|
| Max 10-min winds: | 90 kt (165 km/h) |
| Min pressure: | 942 hPa (mbar) |
| ACE accumulated | 14.2425 |
| TD+ days | 8.25 days |
| TS+ days | 6 days |
| C1+ days | 3.25 days |
| C3+ days | 1.5 days |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 5 |
| Damages | $89.3 million (USD) |
| Very Strong Typhoon (JMA) | |
|---|---|
| Category 4 typhoon (SSHWS) | |
  | |
| Duration | May 16 – May 26 |
| Peak intensity | 165 km/h (105 mph) (10-min); 942 hPa (mbar) |
On May 13, an area of disturbed weather developed at around 320 km (199 mi) to the southwest of Guam. The system moved southwestward over the next three days while sustaining a weak circulation. The JMA recognised the system as a tropical depression on May 15 as the storm's convection became better organised. Meanwhile, on the next day, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the depression. On May 16, the JTWC upgraded the storm into a tropical depression, and designating it as 01W. At 00:00 UTC the next day, as 01W entered the Philippine Area of Responsibility, the PAGASA assigned the system with the local name Ada. As the system's convection continued to deepen after that point, with convective bands feeding into the system's centre, the JMA upgraded the storm to Tropical Storm Merbok on May 17, at 12:00 UTC. The JTWC followed suit and upgraded the system to a tropical storm six hours later. By May 18, microwave passes have shown the development of an eye underneath Merbok's deep central convection. This prompted both the JMA and the JTWC to upgrade the storm to a minimal typhoon. Merbok moved northwestward over the next day and rapidly deepened. On the next day, Merbok attained its first and strongest peak as a Category 4 typhoon off the coast of Samar, with 1-minute sustained winds of 220 km/h (140 mph) and a minimum pressure of 942 mbar (27.82 inHg). The storm then underwent a brief eyewall replacement cycle (EWRC) and temporarily weakened to a Category 2 typhoon. However, on May 20, Merbok completed its EWRC and managed to restrengthen into a Category 4 typhoon again, albeit with a slightly lower peak. In the late hours on the same day, Merbok made a westward jolt, and the storm started to move directly towards the Bicol Region of the Philippines. After passing to the north of Catanduanes, Merbok made its first landfall on May 21, at 12:00 UTC, over the northern tip of Daldagon, Siruma, Camarines Sur. Minutes later, the system made another landfall over Butawanan Island. Later on the same day, the typhoon made more landfalls over the Apuao Grande Island and Mambungalon, Mercedes, Camarines Norte. On May 22, Merbok crossed the Calabarzon region, bringing torrential rain and intense winds to the area. During this time, the system weakened to a tropical storm due to land interaction. Merbok then soon moved offshore and entered the South China Sea (SCS). Due to high shear and marginal sea surface temperatures, the storm continued to weaken over the SCS on May 23. On the same day, both the JMA and the JTWC downgraded the storm to a tropical depression. On the next day, the JTWC issued its final warning on the system, while the JMA continued to monitor Merbok until it dissipated on May 26.
While Merbok was crossing the Philippines, it caused serious damage over Calabarzon, Bicol Region, and Eastern Visayas. In these three regions, power outages were reported in 139 cities and municipalities, and at least 33,000 ha (81,500 acres) of farmland suffered damage. At the same time, due to the torrential rain brought by Merbok, the Angat Dam and the Ipo Dam in the province of Bulacan both reached their spilling levels. A total of 11,520 homes were affected in the central Philippines, including 1,339 which were destroyed. Total damages brought by Merbok added up to a total of ₱5.18 billion (US$89.3 million) in the Philippines, while 4 people lost their lives in the country.
Notable stats: None.
Tropical Depression 02W (Basyang)[]
| Max 1-min winds: | 30 kt (55 km/h) |
|---|---|
| Max 10-min winds: | 30 kt (55 km/h) |
| Min pressure: | 1001 hPa (mbar) |
| ACE accumulated | 0 |
| TD+ days | 3 days |
| TS+ days | N/A |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | None |
| Damages | Unknown |
| Tropical depression (JMA) | |
|---|---|
| Tropical depression (SSHWS) | |
  | |
| Duration | June 2 – June 5 |
| Peak intensity | 55 km/h (35 mph) (10-min); 1001 hPa (mbar) |
On June 1, a tropical disturbance formed over the Philippine Sea, at an area around 350 km (217 mi) to the east of Catanduanes. Due to favourable conditions surrounding the system, the disturbance managed to quickly cover its low-level circulation center with deep convection. As a result, both the JMA and the PAGASA designated the system as a tropical depression on the same day, while the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system. At the same time, the PAGASA gave the storm the local name Basyang as the system was in the Philippine Area of Responsibility. On June 2, the JTWC upgraded the system to Tropical Depression 02W when the system was heading towards Luzon to its northwest. On the next day, at 03:00 UTC, 02W made its first landfall over Maligaya, Palanan, Isabela. 02W crossed Luzon quite quickly, and moved offshore eight hours later into the South China Sea. 02W managed to maintain its intensity over the South China Sea as it moved north-northwestwards. Upon reaching the Taiwan Strait on June 4, 02W got exposed to increased wind shear and colder sea surface temperatures. This caused 02W's convection to get displaced, and the depression weakened. As a result, the JTWC issued their final advisories on 02W that day, while the JMA determined 02W to have degraded to a remnant low. 02W's remnants dissipated over the East China Sea on June 5.
Notable stats: None.
Tropical Storm Nanmadol[]
| Max 1-min winds: | 50 kt (95 km/h) |
|---|---|
| Max 10-min winds: | 45 kt (85 km/h) |
| Min pressure: | 986 hPa (mbar) |
| ACE accumulated | 1.0175 |
| TD+ days | 3.25 days |
| TS+ days | 1.5 days |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 3 |
| Damages | $37.2 million (USD) |
| Tropical storm (JMA) | |
|---|---|
| Tropical storm (SSHWS) | |
  | |
| Duration | July 3 – July 6 |
| Peak intensity | 85 km/h (55 mph) (10-min); 986 hPa (mbar) |
In the late hours of July 2, the JTWC designated an area of disturbed weather over the South China Sea as Invest 92W. The tropical disturbance quickly developed as it moved northeastwards slowly. As a result, by early July 3, the JMA upgraded the system to a tropical depression, while the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system. On the same day, at 12:00 UTC, the JTWC upgraded 92W to Tropical Depression 03W. 03W then started to travel northwestward as it approached the Chinese province of Hainan. 03W continued to develop during this time, with its once-exposed center of circulation getting covered by convection. On July 4, at 06:00 UTC, the JMA further upgraded 03W to a tropical storm and named it Nanmadol. The JTWC followed suit and also upgraded Nanmadol to a tropical storm 12 hours later. Nanmadol then made its landfall over Haitang Bay, Sanya, Hainan, at 22:30 UTC as a tropical storm. The system crossed the southern portion of Hainan in four hours, and it moved off-shore into the Gulf of Tonkin by early July 5. Nanmadol a this time was exposed to favourable conditions, such as low vertical wind shear and sea surface temperatures (SSTs) of 28 °C (82 °F) to 29 °C (84 °F). As a result, the storm reached its peak intensity at 18:00 UTC on July 5, with maximum 1-minute sustained winds of 95 km/h (60 mph) and a minimum central pressure of 986 mbar (29.12 inHg). Nanmadol then soon made landfall over Nghi Sơn, Thanh Hóa, Vietnam at peak intensity. This caused the storm to weaken due to land interaction. On July 6, the JTWC issued its final warning on the system, while the JMA stated that the Nanmadol has degraded into a remnant low. The system finally dissipated near the Laos–Thailand border on the same day.
Nanmadol caused considerable damage in Southern China and Vietnam. In Hainan, economic losses caused by the storm reached 158 million yuan (US$21.8 million). In addition, the storm had left three people dead and five others missing in Vietnam, with severe damage to infrastructure being reported in the northern part of the country. Nanmadol also sank four boats, destroyed the roofs of 819 houses and uprooted about 7,300 trees. Damages in Vietnam amounted to ₫386 billion ($15.1 million).
Notable stats: None.
Severe Tropical Storm Talas[]
| Max 1-min winds: | 55 kt (100 km/h) |
|---|---|
| Max 10-min winds: | 55 kt (100 km/h) |
| Min pressure: | 985 hPa (mbar) |
| ACE accumulated | 6.085 |
| TD+ days | 7.25 days |
| TS+ days | 6.75 days |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | None |
| Damages | None |
| Severe tropical storm (JMA) | |
|---|---|
| Tropical storm (SSHWS) | |
  | |
| Duration | July 6 – July 13 (Extratropical) |
| Peak intensity | 100 km/h (60 mph) (10-min); 985 hPa (mbar) |
On July 5, the JMA started to monitor a tropical depression that had developed at about 920 km (575 mi) to the northwest of Hagåtña, Guam. Initially, the system had a broad and weak low level circulation centre (LLCC), and convection only flared up near the storm's edges. However, as the system entered an environment that was favourable for further development after it moved slowly to the northwest, convection started to cover its LLCC. This prompted the JTWC to issue a Tropical Cyclone Formation Alert (TCFA) on the system by early July 6. 18 hours later, the JTWC further upgraded the storm to Tropical Depression 04W. On the next day, both the JMA and the JTWC upgraded 04W to a tropical storm, with the former naming the system Talas. Talas started to slowly move north-eastwards while gradually strengthening. The JMA upgraded the system to a severe tropical storm by late July 8, six hours before Talas attained its peak intensity with maximum 1-minute sustained winds of 100 km/h (65 mph) and a minimum central pressure of 985 mbar (29.12 inHg). At 04:15 UTC, on July 9, Talas made its landfall over Hahajima, Bonin Islands at peak intensity. Fortunately, damages were minimal, and no injuries or fatalities were recorded in the Bonin Islands. Talas continued to move steadily northeastwards over the next few days. After slightly weakening on July 10 due to moderate to high wind shear, the system restrengthened to attain its second peak a day later. Talas then slowly weakened after July 11 due to decreasing sea surface temperatures until it transitioned to an extratropical cyclone in the early hours of July 14. The extratropical cyclone of Talas crossed the International Date Line two days later, and the storm dissipated on July 20, over the Gulf of Alaska.
Notable stats: None.
Typhoon Hodu (Caloy)[]
| Max 1-min winds: | 120 kt (220 km/h) |
|---|---|
| Max 10-min winds: | 95 kt (175 km/h) |
| Min pressure: | 933 hPa (mbar) |
| ACE accumulated | 11.6 |
| TD+ days | 5.75 days |
| TS+ days | 4 days |
| C1+ days | 2.75 days |
| C3+ days | 1.25 days |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 41 |
| Damages | $7.301 billion (USD) |
| Very Strong Typhoon (JMA) | |
|---|---|
| Category 4 typhoon (SSHWS) | |
  | |
| Duration | July 12 – July 19 |
| Peak intensity | 175 km/h (110 mph) (10-min); 933 hPa (mbar) |
On July 8, a broad low-pressure area developed into a tropical depression according to the JMA, at around 490 km (304 mi) to the southeast of Guam. The system slowly drifted westward initially, until it took on a more northwesterly track after July 10. As the storm became more organised, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the depression on July 11. The agency then further upgraded it to Tropical Depression 05W on the next day and initiated advisories on the system. 05W continued to steadily move northwestwards as it eventually entered the Philippine Area of Responsibility in the early hours of July 13. The caused the PAGASA to assign the system with the local name Caloy. As 05W's convective bands started to wrap into the storm’s centre, the JTWC upgraded 05W to a tropical storm on the same day at 12:00 UTC, while the JMA followed suit 6 hour later and named the storm Hodu. Hodu continued to move northwestwards across the Philippine Sea, before finally reaching typhoon status on July 14 according to both the JMA and the JTWC. The typhoon began undergoing rapid intensification on the next day, eventually reaching Category 4 status. Hodu brushed past the southern tip of Taiwan on July 15 and started to weaken due to land interaction. Then it made landfall over Zhao'an County of Fujian, China on July 16, at 20:45 UTC, as a weakening Category 2 typhoon. The JMA then downgraded Hodu back into a severe tropical storm on July 17 as its circulation became degraded after the landfall. Hodu continued to rapidly weaken, and the JTWC issued their final warning on the system that day. However, the JMA continued tracking the remnants of Hodu as it travelled northeastwards after July 18. Hodu finally dissipated on July 19, when it lingered over Nantong, Jiangsu, China.
When Hodu brushed past Taiwan, it unleashed torrential rains and strong gusty winds over the country. Extensive infrastructure damage were recorded in the nation, and More than 129,000 households lost electricity due to the typhoon. In addition, one firefighter lost his life in Pingtung County due to a collapsed tree. Meanwhile, Hodu also flooded tens of thousands of acres of farmlands and knocked down power poles in Fujian and Guangdong, causing serious disruption land and sea transportations in the two provinces. At the end, Hodu caused 38 fatalities and 47.51 billion yuan (US$6.57 billion) of damage in China.
Notable stats: Hodu was the second-costliest storm of the season.
Severe Tropical Storm Kulap[]
| Max 1-min winds: | 70 kt (130 km/h) |
|---|---|
| Max 10-min winds: | 60 kt (110 km/h) |
| Min pressure: | 972 hPa (mbar) |
| ACE accumulated | 7.5475 |
| TD+ days | 8.5 days |
| TS+ days | 8 days |
| C1+ days | 1.25 days |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 9 |
| Damages | $10.1 million (USD) |
| Severe tropical storm (JMA) | |
|---|---|
| Category 1 typhoon (SSHWS) | |
  | |
| Duration | July 22 – July 30 (Extratropical) |
| Peak intensity | 110 km/h (70 mph) (10-min); 972 hPa (mbar) |
On July 20, the JTWC noted on the formation of a tropical depression located at around 900 km (559 mi) to the west of Wake Island. Favourable environment at that time, such as warm sea surface temperatures, low wind shear, and very good poleward outflow, allowed the disturbance to quickly develop. On the next day, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system, while the JMA noted the system has become a tropical depression at around the same time. On July 22, at 06:00 UTC, the JTWC further upgraded the system to Tropical Depression 06W. 06W steadily moved westwards during this time, and it was designated as Tropical Storm Kulap at 12:00 UTC by the JMA on the same day. In the early hours of July 24, Kulap was exposed to more hostile environmental conditions such as high wind shear and dry air intrusion. This caused the storm to weaken to a tropical depression by both agencies on the same day. At this time, Kulap moved to an area with a trough to its north. This caused the system to recurve and move generally northwards. By July 25, as wind shear lessened, Kulap intensified into a tropical storm again by both the JMA and the JTWC. The JMA then further upgraded Kulap to a severe tropical storm on July 26. Meanwhile, as the system started to form a microwave eye, the JTWC upgraded Kulap to a Category 1 typhoon. However, the JMA kept it as a strong severe tropical storm. After peaking, Kulap started to gradually weaken as it moved north-northwestward into colder waters of the North Pacific. The storm made landfall over Onbetsucho Shakubetsu, Kushiro City, Hokkaido as a weak tropical storm on July 30, at 12:40 UTC, and commenced extratropical transition later on the same day. Kulap would complete its transition by July 31, with both the JMA and JTWC issuing their final advisories on the system that day.
Kulap brought considerable impacts to northern Japan, especially in Hokkaido. Over 600 domestic flights in and out of Hokkaido were delayed or cancelled due to the storm, while localised flooding were also recorded along Kushiro River. Off the coast of Cape Kiritappu in Hamanaka, Akkeshi District, a boat sank due to rough seas and strong winds, killing 7 people in the process. Agricultural damage in Hokkaido was at ¥941 million (US$6.3 million).
Notable stats: None.
Tropical Depression Wali[]
| Max 1-min winds: | 30 kt (55 km/h) (in basin) |
|---|---|
| Max 10-min winds: | 30 kt (55 km/h) (in basin) |
| Min pressure: | 1002 hPa (mbar) (in basin) |
| ACE accumulated | 0 (in basin) |
| TD+ days | 1.25 days (in basin) |
| TS+ days | 0 days (in basin) |
| C1+ days | 0 days (in basin) |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | None |
| Damages | None |
| Tropical depression (JMA) | |
|---|---|
| Tropical depression (SSHWS) | |
  | |
| Duration | July 29 (Entered basin) – July 30 (Extratropical) |
| Peak intensity | 55 km/h (35 mph) (10-min); 1002 hPa (mbar) |
On July 28 at 20:00 UTC, the remnants of Hurricane Wali moved into the basin from the Central Pacific about 280 km (174 mi) to the northwest of Midway Atoll. Wali was then classified as a tropical depression by both the JMA and the JTWC on the next day at 00:00 UTC. 12 hours later, the JTWC noted on the subtropical characteristics exhibited by Wali, and the agency reclassified the storm as a subtropical depression at that time. Wali continued to weaken, and its convective structure became highly asymmetric. The system transitioned to an extratropical cyclone by July 30 and recurved northeastwards on the next day. The JTWC stopped tracking Wali on July 30, while the JMA continued to maintain Wali as a depression until it was last noted by the agency at 00:00 UTC on August 1.
Notable stats: The first storm that crossed from the Central Pacific to the West Pacific this season. Formed on July 20 in the Eastern Pacific, got named Wali on July 22 in the Central Pacific, and entered the West Pacific on July 28.
Typhoon Roke (Domeng)[]
| Max 1-min winds: | 105 kt (195 km/h) |
|---|---|
| Max 10-min winds: | 80 kt (150 km/h) |
| Min pressure: | 949 hPa (mbar) |
| ACE accumulated | 8.42 |
| TD+ days | 5.25 days |
| TS+ days | 3.75 days |
| C1+ days | 2.5 days |
| C3+ days | 0.75 days |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 34 |
| Damages | $4.69 billion (USD) |
| Typhoon (JMA) | |
|---|---|
| Category 3 typhoon (SSHWS) | |
  | |
| Duration | August 5 – August 10 |
| Peak intensity | 150 km/h (95 mph) (10-min); 949 hPa (mbar) |
On August 2, the JTWC noted a broad area of low pressure formed at around 400 km (249 mi) to the northwest of Guam. The disturbance developed slowly at first and stalled over the Pacific Ocean. However, the system tightened its circulation over the next two days. As a result, the JMA upgraded the low-pressure area into a tropical depression on August 4, while on the same day, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system. The JTWC then further upgraded the storm to Tropical Depression 07W on August 5, at 06:00 UTC. Six hours later, the JMA assessed 07W to have become a tropical storm, and named the system Roke. At 00:00 UTC on the next day, the JTWC also upgraded Roke to a tropical storm. As Roke moved northwestwards and entered the Philippine Area of Responsibility six hours later, the PAGASA named the storm with its local name Domeng. Roke continued to strengthen during this time. This prompted the JMA to eventually upgrade Roke to a typhoon by late August 6 as a primitive eye started to form in the centre of its central dense overcast (CDO). After this, Roke continued to strengthen as it headed towards Taiwan. On August 8, at 12:00 UTC, Roke attained its peak intensity according to the JTWC as a Category 3 typhoon with maximum 1-minute sustained winds of 195 km/h (120 mph) and a minimum central pressure of 949 mbar (28.02 inHg). Just six hours later, Roke made landfall over Nan'ao, Yilan County, Taiwan as a Category 2 typhoon. The mountain ranges of Taiwan weakened Roke rapidly, and the system moved ashore from Daan District, Taichung ten hours later as a tropical storm. On August 10, at 00:15 UTC, Roke made landfall near Xiamen, Fujian as a weakening tropical depression. The system then dissipated over Guangdong 12 hours later.
Roke brought severe impacts to both Taiwan and China. When the typhoon passed Taiwan, Roke destroyed hundreds of homes near the eastern coast of the country. Numerous traffic signs and billboards were displaced, roads and towns were flooded, and widespread power outages and uprooted trees were reported in New Taipei City, Yilan, Hualien and Taitung. Across the whole Taiwan, About 39,100 houses were destroyed, and another 137,600 were damaged. Fatalities in the island nation reached 15, while damages exceeding NT$104.9 billion (US$3.17 billion) were recorded. Meanwhile, Roke also brought torrential rain to the Chinese provinces of Fujian, Guangdong, Zhejiang and Jiangxi. In Longyan, Fujian, from August 9 to 10, 519.6 mm (20.46 in) of rain were recorded in a 24-hour period, setting a new 38-year record. Widespread flooding across the Fujian resulted in heavy crop and livestock damage, where 29,000 livestock were reported to have been killed, and 5,500 km2 (2,124 sq mi) of fields were inundated. Roke also severely impacted the infrastructure along its path, with 819 km (509 mi) of roads damaged. Across China, damage was estimated at ¥9.51 billion (US$1.31 billion), primarily in Fujian.
Notable stats: None.
Severe Tropical Storm Nesat (Ester)[]
| Max 1-min winds: | 60 kt (110 km/h) |
|---|---|
| Max 10-min winds: | 60 kt (110 km/h) |
| Min pressure: | 978 hPa (mbar) |
| ACE accumulated | 5.0775 |
| TD+ days | 8.5 days |
| TS+ days | 5.75 days |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 9 |
| Damages | $40.07 million (USD) |
| Severe tropical storm (JMA) | |
|---|---|
| Tropical storm (SSHWS) | |
  | |
| Duration | August 9 – August 18 |
| Peak intensity | 110 km/h (70 mph) (10-min); 978 hPa (mbar) |
On August 6, the JMA noted a low-pressure area had formed at around 730 km (454 mi) to the east of Palau. The disturbance moved steadily to the northwest. As the disturbance became more organised, the JMA upgraded the system to a tropical depression on the next day. At around the same time, the JTWC raised the system's chance to develop into a significant tropical cyclone from "low" to "medium". The depression continued to develop, causing the JTWC to issue a Tropical Cyclone Formation Alert (TCFA) on the system on August 8. On the same day, as the system entered the Philippine Area of Responsibility, PAGASA named the depression with its local name Ester. On August 9, at 00:00 UTC, the JTWC designated the depression as Tropical Depression 08W. The agency then further upgraded 08W to a tropical storm on August 11, 06:00 UTC, while the JMA followed suit six hours later and named the storm Nesat. Nesat moved west-northwest over the Philippine Sea, and it made its first landfall over Baler, Aurora on August 12, at 01:00 UTC, as a tropical storm with 1-minute sustained winds of 95 km/h (60 mph). Five hours later, Nesat crossed Luzon and moved offshore from Alacan, San Fabian, Pangasinan and entered the Lingayen Gulf. After making two brief landfalls over Anda, Pangasinan and Bolinao, Pangasinan, Nesat entered the South China Sea at 08:30 UTC on the same day. Nesat fluctuated in strength in the South China Sea, and it interacted with a mid- to high-level trough on August 14. This caused Nesat to start moving towards the north. On August 16, at 11:00 UTC, Nesat made landfall in Dianbai, Maoming, Guangdong, as a strong tropical storm. After landfall, Nesat rapidly weakened. This caused the JTWC to cease issuing advisories on the system on the same day. Once inland, the JMA downgraded Nesat into a tropical depression on August 17 and continued tracking the system until it dissipated at 00:00 UTC on August 18.
Nesat influenced the southwest monsoon over the Philippines, producing heavy rainfall over parts of the archipelago from August 9 through August 16. Flooding induced by the rainfall impacted 118,603 households in Luzon, and four people lost their lives to a landslide in Banaue, Ifugao. Meanwhile, in China, Nesat caused high-speed rail and ferry services on the island of Hainan to be cancelled, while rain squalls associated with the system impacted the Pearl River Delta, where occasional high wind gusts were reported in elevated parts of Hong Kong. Overall, Nesat caused 9 deaths and US$40.07 million of damages across the Philippines, China and Vietnam.
Notable stats: None.
Severe Tropical Storm Sonca[]
| Max 1-min winds: | 55 kt (100 km/h) |
|---|---|
| Max 10-min winds: | 50 kt (95 km/h) |
| Min pressure: | 984 hPa (mbar) |
| ACE accumulated | 3.1225 |
| TD+ days | 4 days |
| TS+ days | 3.5 days |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | None |
| Damages | $6.3 million (USD) |
| Severe tropical storm (JMA) | |
|---|---|
| Tropical storm (SSHWS) | |
  | |
| Duration | August 9 – August 13 (Extratropical) |
| Peak intensity | 95 km/h (60 mph) (10-min); 984 hPa (mbar) |
On August 7, a weak tropical disturbance developed at the tailend of a mid-latitude trough of low pressure, at about 450 km (280 mi) to the southwest of Guam. Over the next two days, deep atmospheric convection developed over the system's elongated low level circulation centre (LLCC). This caused the JMA to classify the tropical disturbance as a tropical depression by early August 9, while the JTWC also followed suit at 12:00 UTC on the same day and gave the system the designation 09W. 09W continued to develop as it moved generally northwards. On August 10, at 00:00 UTC, both the JMA and the JTWC further upgraded 09W to a tropical storm, with the former also giving the system the name Sonca. On the next day, at 18:00 UTC, when Sonca was located at around 600 km (373 mi) to the east-southeast of Aogashima, the storm reached its peak intensity, with maximum 1-minute sustained winds of 100 km/h (65 mph) and a minimum central pressure of 984 mbar (29.06 inHg). After August 12, Sonca started to gradually weaken as it traversed over colder waters. The JTWC noted that Sonca started to take on frontal characteristics on early August 13 as extratropical transitioned commenced. This caused the agency to issues its final warning on Sonca on the same day at 00:00 UTC. Sonca became completely extratropical 12 hours later. Sonca's extratropical remains crossed the International Date Line on August 15, and the storm finally dissipated on August 18 near the Aleutian Islands.
Notable stats: None.
Typhoon Haitang (Francisco)[]
| Max 1-min winds: | 95 kt (175 km/h) |
|---|---|
| Max 10-min winds: | 80 kt (150 km/h) |
| Min pressure: | 953 hPa (mbar) |
| ACE accumulated | 8.8975 |
| TD+ days | 6.5 days |
| TS+ days | 5.5 days |
| C1+ days | 2.75 days |
| C3+ days | N/A days |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 58 |
| Damages | $311.7 million (USD) |
| Typhoon (JMA) | |
|---|---|
| Category 2 typhoon (SSHWS) | |
  | |
| Duration | August 13 – August 20 |
| Peak intensity | 150 km/h (95 mph) (10-min); 953 hPa (mbar) |
On August 12, the JTWC detected a disturbance in a monsoon trough developing at approximately 630 km (391 mi) to the east of Guam. According to the agency, the disturbance was located in a favourable environment conducive for intensification, such as sea surface temperatures (SSTs) of 30 °C (86 °F) to 31 °C (88 °F) and low vertical wind shear. On the next day, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system. The agency then further upgraded the cyclone to Tropical Depression 10W at 18:00 UTC on August 13 as the storm became better organised. On August 14, at 06:00 UTC, both the JMA and the JTWC upgraded the system to a tropical storm, with the former naming the storm Haitang. At the same time, as Haitang entered the Philippine Area of Responsibility (PAR), the PAGASA named the storm with the local name Francisco. Within in PAR, Haitang moved west-northwestward steadily, and it attained typhoon status according to the JMA on August 18. Shortly after peaking as a Category 2 typhoon according to the JTWC, Haitang made landfall over Cabeseria 25 (Santa Lucia), Ilagan, Isabela on August 16, at 12:00 UTC. Haitang rapidly weakened shortly after the landfall, and it fell below typhoon status according to both the JMA and JTWC just six hours after its landfall. The storm crossed Luzon in 12.5 hours, and it moved offshore from Caparacadan, Caoayan, Ilocos Sur on August 17, at 00:30 UTC, to enter the South China Sea (SCS). Over the SCS, Haitang started to reintensify, with the deep convection near its centre starting to wrap around itself to form a large and rugged eye. The JTWC upgraded Haitang to a typhoon again on August 18, at 06:00 UTC. However, the JMA kept the cyclone as a severe tropical storm. Haitang made landfall over Wuchuan, Guangdong as a Category 1 typhoon on the next day, at 03:00 UTC. After that, Haitang moved inland and quickly weakened. The JTWC issued its final advisory on the system on August 19 at 18:00 UTC, while the JMA continued tracking the system till it dissipated near the Guangdong-Guangxi border on August 20, at 06:00 UTC.
Haitang brought severe impacts to the Philippines. Due to the typhoon's arrival, storm surges of over 3.8m were recorded in Palanan Bay. About 43 transmission lines were affected by Haitang, leading to power outages throughout Luzon, though most power was quickly restored by August 17. Meanwhile, torrential rain brought by Haitang caused 12 landslide-related deaths in the country, with most of them occurring in Mountain Province after 9 people died in Natonin when a landslide buried a Department of Public Works and Highways building. Haitang's total damage to agriculture was estimated at ₱7.460 billion (US$130 million), mostly towards rice, while total economic damage reached ₱13.30 billion (US$231.7 million). 19 people lost their lives in the Philippines due to Haitang.
In Guangdong, China, 21 landslides killed two people in Xinxing County and caused another person in Jiangmen to go missing. In Qionghai, Hainan, Haitang spawned a tornado which blew off a market's 600 m2 (6,458 sq ft) roof, damaged four cars and caused three casualties. In Guangxi, persistent rainfall from the remnants of Haitang caused the You River to overflow, which resulted in severe flooding in Baise. In Ceheng County, a landslide caused the collapse of an apartment building, killing 25 people in the process. Overall, the passage of Haitang resulted in 39 fatalities and direct economic losses of ¥534 million (US$73.5 million).
Notable stats: Haitang was the fourth-deadliest storm of the season.
Typhoon Jamjari (Gardo)[]
| Max 1-min winds: | 140 kt (260 km/h) |
|---|---|
| Max 10-min winds: | 105 kt (195 km/h) |
| Min pressure: | 909 hPa (mbar) |
| ACE accumulated | 49.8375 |
| TD+ days | 14 days |
| TS+ days | 13 days |
| C1+ days | 10.5 days |
| C3+ days | 6 days |
| SuperTY days | 1.75 days |
| C5 days | 0.5 days |
| Fatalities | 142 |
| Damages | $6.289 billion (USD) |
| Violent Typhoon (JMA) | |
|---|---|
| Category 5 super typhoon (SSHWS) | |
  | |
| Duration | August 13 – August 27 (Extratropical) |
| Peak intensity | 195 km/h (120 mph) (10-min); 909 hPa (mbar) |
On August 12, the JTWC designated a tropical disturbance developing in a monsoon trough located approximately 180 km (112 mi) to the northeast of Faraulep Atoll. Meanwhile, the JMA noted the system as a tropical depression in the early hours of August 13. As the storm was embedded in an environment favourable for development, the JTWC upgraded the storm to Tropical Depression 11W at 18:00 UTC on the same day, only 12 hours after issuing a Tropical Cyclone Formation Alert (TCFA) on the system. On August 14, at 12:00 UTC, the JMA upgraded 11W to Tropical Storm Jamjari due to rapidly cooling cloudtops near the storm's centre and the development of spiral rainbands. The JTWC followed suit and upgraded Jamjari to a tropical storm six hours later. During this time, Jamjari moved to the southern periphery of a subtropical ridge. This influenced the cyclone to start moving towards the northwest. On August 16, at 00:00 UTC, when Jamjari was located to the east of the Northern Mariana Islands, it strengthened to a typhoon according to the JTWC. At 07:00 UTC, Jamjari passed between Tinian and Rota. Five hours after this passage, the JMA also upgraded Jamjari to a typhoon. From August 17 to 18, Jamjari entered an area with highly favourable conditions such as high oceanic heat content and low vertical wind shear. This allowed the typhoon to rapidly intensify. On August 18, at 06:00 UTC, the JTWC assessed Jamjari have become the first super typhoon of the season, with 1-minute sustained winds of 240 km/h (150 mph). Jamjari continued to strengthen, and the storm became the first Category 5 super typhoon of the season 12 hours later, attaining 1-minute sustained winds of 260 km/h (160 mph) and a minimum central pressure of 909 mbar (26.84 inHg). After this peak, Jamjari weakened due to the onset of an eyewall replacement cycle (EWRC). The typhoon restrengthened to a Category 4 super typhoon again on August 21 due to the completion of the EWRC. However, another EWRC started later on the same day, causing the system to weaken temporarily to a Category 2 typhoon on August 22. During this time, an upper-level low and a trough started to guide Jamjari to move north-northwestward. On August 23, Jamjari attained its third and final peak as a Category 4 typhoon when it approached the Ryukyu Islands.
On the next day, at 15:00 UTC, Jamjari made direct landfall over Teima, Nago, Okinawa as a Category 3 typhoon, with 1-minute sustained winds of 195 km/h (120 mph). Jamjari moved offshore in an hour as it moved northwards and entered the East China Sea. Jamjari gradually weakened in the East China Sea, and it passed within 6 km (4 mi) to the westernmost tip of Jeju Island on August 26, at 01:00 UTC, as a Category 1 typhoon according to the JTWC. At around the same time, the JMA downgraded Jamjari to a severe tropical storm as the system became increasingly affected by shear, and the storm's deep convection waned due to decreasing sea surface temperatures. At 17:30 UTC on the same day, Jamjari made landfall over Yeocha-ri, Hwado-myeon, Incheon. The system then crossed the Korean Peninsula with a northeasterly motion. During this time, on August 27, the JTWC issued their final bulletins on the system as the agency noted on the system's extratropical transition. Jamjari finished extratropical transition in the late hours of August 27, and the extratropical remnants of the system accelerated northeastward over the next few days. After lingering over Alaska from August 31 to September 4 as a strong extratropical cyclone, Jamjari finally dissipated in the early hours of September 5.
When Jamjari passed through the Northern Mariana Islands, its storm surge affected various islands nearby. On August 16, off the coast of Guam, a fishing boat was capsized due to the rogue waves generated by the typhoon. two fishermen lost their lives in this incident as a result. Meanwhile, Jamjari also brought severe impacts to the Ryukyu Islands. In Okinawa, over 221,000 households experienced temporarily blackouts due to the typhoon. In addition, air and sea transport were significantly impacted, with more than 300 flights to and from the island getting cancelled due to Jamjari. The typhoon's strong winds also unroofed buildings. Throughout the Ryukyu Islands, 18 buildings were completely destroyed, with an additional 793 sustaining at least partial damage. Jamjari caused direct economic damage of ¥459 billion (US$3.106 billion) on the island chain, and 14 people were killed.
Being the strongest typhoon since Typhoon Kajiki in 2054 to affect South Korea, Jamjari also brought devastating impacts to the country. On Jeju Island, high winds from the typhoon downed power poles, broke street lamps, and damaged buildings. More than 55,000 households on the island lost power. Furthermore, high amounts of rainfall were recorded in South Korea's southern and eastern coasts, with orographic rain that were resulted from air getting lifted over the Taebaek Mountains being a major contributing factor. Off the coast of South Gyeongsang Province, a 91,063 ton cargo ship ran aground during the storm and broke in half. Out of the 23 people on board the vessel, 3 were injured. Overall in South Korea, Jamjari inflicted ₩3.85 trillion (US$2.60 billion) of economic damage, while 64 fatalities across the nation were recorded. Meanwhile, in North Korea, Kangwon Province was hit hard by the storm. Across the province, 2,405 homes were destroyed and another 1,500 were damaged, while 39 people were killed and another 116 were reported missing. Across the whole North Korea, over 139,000 hectares (343,000 acres) of crop and rice fields were flooded, 29,850 trees were downed, and 339 public and industrial buildings were severely damaged. All in all, at least 61 fatalities were reported across the country, 259 more were reported missing, and more than 13,000 others were left homeless.
Notable stats: Jamjari was the first super typhoon and Category 5 storm of the season; the third-deadliest and third-costliest storm of the season; and the largest ACE producer of the season. Jamjari was the strongest storm to impact South Korea since Typhoon Kajiki in 2054.
Tropical Storm Banyan[]
| Max 1-min winds: | 25 kt (45 km/h) |
|---|---|
| Max 10-min winds: | 35 kt (65 km/h) |
| Min pressure: | 1001 hPa (mbar) |
| ACE accumulated | 0 |
| TD+ days | 1 day |
| TS+ days | N/A |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 2 |
| Damages | $65.5 million (USD) |
| Tropical storm (JMA) | |
|---|---|
| Tropical depression (SSHWS) | |
  | |
| Duration | August 21 – August 25 |
| Peak intensity | 65 km/h (40 mph) (10-min); 1001 hPa (mbar) |
On August 19, the JTWC noted that a small area of low pressure developed within the outflow of Typhoon Haitang, located over the South China Sea, at approximately 410 km (255 mi) to the south of Hong Kong. The system was initially sheared by Haitang. However, as Haitang moved away from the low pressure area and weakened, wind shear surrounding the system decreased. At the same time, warm sea surface temperatures up to 30 °C (86 °F) or 31 °C (88 °F) offset the lack of divergence aloft in the area. These factors allowed the low pressure system to gradually organise itself on August 20. On the same day, the JMA upgraded the system to a tropical depression, while the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system. Over the next day, an anticyclone over China started to move eastward at this time, increasing the divergent flow on the area and allowing the system to further develop. As a result, the JTWC upgraded the cyclone to Tropical Depression 12W at 12:00 UTC on August 21. Six hours later, the JMA upgraded 12W to a tropical storm, and named it Banyan. However, the JTWC never upgraded Banyan to a tropical storm. Banyan moved northwards and made landfall over Taishan, Guangdong at 20:00 UTC. After that, Banyan weakened, with the JTWC issuing their final bulletins on the system on August 22. Meanwhile, the JMA continued tracking the remnants of Banyan until it dissipated over the East China Sea on August 25.
Notable stats: Banyan was the only storm in the season spawned from the outflow of another tropical cyclone. Moreover, Banyan was the first storm this season that was recognised by the JMA as a tropical storm but not the JTWC.
Tropical Storm Yamaneko[]
| Max 1-min winds: | 40 kt (75 km/h) |
|---|---|
| Max 10-min winds: | 40 kt (75 km/h) |
| Min pressure: | 995 hPa (mbar) |
| ACE accumulated | 2.0525 |
| TD+ days | 4.5 days |
| TS+ days | 3.5 days |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | None |
| Damages | None |
| Tropical storm (JMA) | |
|---|---|
| Tropical storm (SSHWS) | |
  | |
| Duration | August 26 – August 30 (Extratropical) |
| Peak intensity | 75 km/h (45 mph) (10-min); 995 hPa (mbar) |
On August 23, the JTWC noted a subtropical disturbance had developed at around 850 km (528 mi) to the southeast of the Bonin Islands. The system drifted over the Pacific Ocean slowly over the next two days. On August 24, the JMA classified the disturbance as a tropical depression. As the storm moved northeastwards around a subtropical ridge of high pressure on the next day, its structure improved with the development of a warm core. This prompted the JTWC to issue a Tropical Cyclone Formation Alert (TCFA) on the system by early August 25. At 00:00 UTC on the next day, the JTWC upgraded the cyclone to Tropical Depression 13W, and the agency also noted the development of tropical characteristics of the system. 13W continued to move northeastward, and it was upgraded to Tropical Storm Yamaneko by the JMA 18 hours later. Six hours after that, the JTWC also upgraded Yamaneko to a tropical storm. Yamaneko achieved a peak with 1-minute sustained winds of 75 km/h (45 mph) over the next few days as it travelled generally northwards. The storm started to undergo extratropical transition on August 29 and took on frontal characteristics. The cyclone then fully became extratropical on the next day as it entered the Sea of Okhotsk. The extratropical cyclone of Yamaneko crossed the International Date Line on September 4 as it travelled over the Aleutian Islands. Yamaneko finally dissipated on September 8 to the south of Kodiak Island.
Notable stats: None.
Tropical Storm Pakhar[]
| Max 1-min winds: | 40 kt (75 km/h) |
|---|---|
| Max 10-min winds: | 45 kt (85 km/h) |
| Min pressure: | 992 hPa (mbar) |
| ACE accumulated | 2.2325 |
| TD+ days | 6.5 days |
| TS+ days | 4.25 days |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 8 |
| Damages | $143.9 million (USD) |
| Tropical storm (JMA) | |
|---|---|
| Tropical storm (SSHWS) | |
  | |
| Duration | August 28 – September 3 (Extratropical) |
| Peak intensity | 85 km/h (55 mph) (10-min); 992 hPa (mbar) |
On August 26, an area of low pressure at 420 km (261 mi) to the northeast of Agrihan in the Northern Mariana Islands was noted by the JMA. The disturbance was upgraded to a tropical depression by the JMA on the next day as it organised itself while moving northeastward. Also on August 27, in light of the deep convections developing over the system's centre, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system. On August 28, the JTWC first upgraded the system to Tropical Depression 14W at 06:00 UTC, then the agency further upgraded 14W to a tropical storm at 18:00 UTC on the same day. Six hours later, the JMA also upgraded 14W to a tropical storm, and named it Pakhar. Over the next two days, Pakhar started to recurve northwestwards as it was influenced by an area of high pressure to its northeast. By late August 30, as Pakhar entered an area of high vertical wind shear, the storm's convection got displaced to its east. As a result, both the JMA and the JTWC downgraded Pakhar to a tropical depression over the next 12 hours. On September 1, located at around 230 km (143 mi) to the southeast of Aogashima, Pakhar exited the area of high wind shear. This allowed the storm to restrengthen to a tropical storm according to both agencies on the same day. On September 2, at 09:00 UTC, Pakhar made its first landfall over Taiji, Wakayama as a tropical storm. At 13:30 UTC on the same day, Pakhar moved offshore from Izumisano, Osaka and entered the Osaka Bay. The storm then crossed the bay in two hours and made landfall over Kobe, Hyōgo at 15:30 UTC. At 22:00 UTC, Pakhar entered the Sea of Japan and started to recurve to the northeast due to interactions with the Westerlies. Pakhar completed its extratropical transition by late September 3, prompting the JTWC to issue its final warning on the system on the same day. The extratropical remains of Pakhar moved over Sakhalin over the next two days. After affecting the Russian Far East for a week, the extratropical remnants of Pakhar dissipated on September 11, near the border between Kamchatka Krai and Chukotka Autonomous Okrug.
Pakhar has caused considerable damage in Japan when the storm passed over the country. Damages in Central Japan were particularly severe, especially in the prefectures of Wakayama, Nara, Hyōgo, Tokushima, Tottori and Okayama. In Wakayama, strong gusts and torrential rainfall caused over 40,000 households to lose electricity temporarily. Moreover, Pakhar severely disrupted air traffic over central Japan from September 1 to 3, leading to the cancellations of 817 domestic flights 21 international flights. In addition, in Tottori City, torrential rainfall of 660 mm (26 in) in 24 hours have caused 810 households to get cut off from access roads that had been damaged. In a campsite near Oishihigashi, Ōtsu in the Shiga Prefecture, 4 people lost their lives from a flash flood of the Yodo River that was induced by Pakhar's enhanced rainfall. Total economic losses from the Pakhar totaled ¥19.4 billion (US$136 million) in Japan, while 5 people lost their lives. Pakhar's extratropical cyclone also caused some damage in Russia, where its strong winds caused the collapse of a wooden hut in Sakhalin, killing 3.
Notable stats: None.
Severe Tropical Storm Sanvu[]
| Max 1-min winds: | 55 kt (100 km/h) |
|---|---|
| Max 10-min winds: | 55 kt (100 km/h) |
| Min pressure: | 986 hPa (mbar) |
| ACE accumulated | 3.9525 |
| TD+ days | 6.25 days |
| TS+ days | 5 days |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | None |
| Damages | $9 million (USD) |
| Severe tropical storm (JMA) | |
|---|---|
| Tropical storm (SSHWS) | |
  | |
| Duration | September 1 – September 8 |
| Peak intensity | 100 km/h (60 mph) (10-min); 986 hPa (mbar) |
The JMA noticed a tropical depression that was designated as 92W by the JTWC developing 20 km (12 mi) to the northeast of Murilo, Hall Islands of the Federated States of Micronesia on August 27. At 00:00 UTC on August 29, when 92W was making a cyclonic loop, the JTWC upgraded the system's chance to develop into a significant tropical cyclone from “medium” to "high" and issued a Tropical Cyclone Formation Alert (TCFA). Over the next day, when 92W was moving towards the west-northwest, it encountered dry air and significant wind shear. This caused its convection to become displaced and shallow. As a result, the JTWC cancelled its TCFA on 92W and lowered the chance for the storm to develop into a significant tropical cyclone back to “medium”. On August 31, due to a break of the subtropical ridge to the north of the system, 92W started moving northwards through a trough. This landed the storm in an area conducive for development. As 92W started to consolidate again, the JTWC issued another TCFA on the storm and once again upgraded the system's chance to develop into a significant tropical cyclone from “medium” to "high". On September 1, at 12:00 UTC, the JTWC upgraded 92W to Tropical Depression 15W. At the same time, the JMA upgraded the system to Tropical Storm Sanvu. Six hours later, the JTWC also upgraded Sanvu to a tropical storm. Sanvu continued to strengthen as it moved north-northwestward over the next few days, and the JMA further upgraded the storm to a severe tropical storm by early September 3. On the same day, Sanvu reached its maximum intensity, with both 1-minute and 10-minute sustained winds of 100 km/h (65 mph) and a minimum central pressure of 986 mbar (29.12 inHg). On September 4, at 23:00 UTC, Sanvu made a brief landfall over Miura, Kanagawa as a tropical storm and quickly entered the Tokyo Bay. At 00:00 UTC on the next day, Sanvu made another landfall over Futtsu, Chiba. The storm then crossed the Bōsō Peninsula in the next few hours, and it moved offshore from Kashima, Ibaraki into the Pacific Ocean at 04:30 UTC. After that, Sanvu slowly weakened as it traversed eastwards. On September 6, the JMA downgraded Sanvu to a tropical depression, while the JTWC issued its last warning on the system early on the next day. Meanwhile, the JMA continued to track the system until it dissipated on September 8, at 06:00 UTC.
Notable stats: None.
Typhoon Mawar (Henry)[]
| Max 1-min winds: | 80 kt (150 km/h) |
|---|---|
| Max 10-min winds: | 70 kt (130 km/h) |
| Min pressure: | 967 hPa (mbar) |
| ACE accumulated | 5.1025 |
| TD+ days | 5.5 days |
| TS+ days | 3.5 days |
| C1+ days | 2 days |
| C3+ days | N/A days |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 7 |
| Damages | $86.85 million (USD) |
| Typhoon (JMA) | |
|---|---|
| Category 1 typhoon (SSHWS) | |
  | |
| Duration | September 6 – September 12 |
| Peak intensity | 130 km/h (80 mph) (10-min); 967 hPa (mbar) |
The JTWC started tracking a tropical disturbance located 420 km (261 mi) to the northeast of Yap on August 31. The disturbance developed slowly at first. However, it consolidated as it moved northwestward over the next few days. On September 2, the JMA upgraded the system from a low-pressure area to a tropical depression. Two days later, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the storm. On September 5, at 06:00 UTC, as the system entered the Philippine Area of Responsibility, the PAGASA named the storm with the local name Henry. On September 6, at 00:00 UTC, the JTWC also upgraded the system to a tropical depression, and designated it as 16W. At 18:00 UTC on that day, the JMA upgraded 16W to Tropical Storm Mawar. 12 hours later, the JTWC also further upgraded Mawar to a tropical storm. At around this time, Mawar took on a more due west track as it interacted with a subtropical high to its north. By late September 7, the JMA upgraded Mawar to a severe tropical storm. Then six hours later, the agency assessed Mawar have become a minimum typhoon. Shortly after, Mawar traversed the strip of the Luzon Strait between the Batanes Islands and Babuyan Islands. Mawar entered the South China Sea on September 8 and peaked as a Category 1 typhoon on the next day, at 06:00 UTC, with maximum 1-minute sustained winds of 150 km/h (90 mph) and a minimum central pressure of 967 mbar (28.56 inHg). After that, Mawar started to slowly weaken. The storm made its first landfall over Wengtian, Wenchang, Hainan as a minimal typhoon on September 9, at 18:30 UTC. Around 45 minutes later, Mawar moved offshore and crossed most of the Qiongzhou Strait from east to west. Mawar weakened to first a severe tropical storm then a tropical storm in the Gulf of Tonkin. Mawar then made its final landfall over Dương Kinh district, Haiphong, Vietnam as a tropical storm on September 10, at 08:45 UTC. The JTWC issued its final bulletin on the system by early September 11. Meanwhile, the JMA continued tracking the system until it dissipated near the China–Myanmar border on early September 12.
Mawar caused widespread floods in Southern China and Vietnam as the storm enhanced the prevailing southwest monsoon. In Guangdong, China, three swimmers in Xuwen County, Zhejiang were swept away by Mawar's storm surge. While one managed to escape alive, two drowned. In Hainan, 60,000 people were evacuated from its east coast prior to the storm's impact. Mawar downed power lines and numerous trees in the province, disrupting the daily life of residents there. In Haikou, schools were ordered to close on September 9 and 10. Overall, Mawar killed a total of 6 people and caused about ¥508 million (US$69.9 million) of damage in China.
Meanwhile, in Vietnam, 429 mm (16.9 in) of rainfall were recorded at Dau Lieu, Hà Tĩnh Province on September 10, while an amount of 233 mm (9.2 in) were reported at Vinh, Nghệ An Province on the same day. Two individuals in Thanh Hóa were reported to be missing due to Mawar. Overall damages in Vietnam reached 325 billion VND (US$12.5 million).
Notable stats: None.
Tropical Depression Inday[]
| Max 1-min winds: | Not specified |
|---|---|
| Max 10-min winds: | <30 kt (55 km/h) |
| Min pressure: | 1004 hPa (mbar) |
| ACE accumulated | 0 |
| TD+ days | N/A |
| TS+ days | N/A |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 1 |
| Damages | $1.95 million (USD) |
| Tropical depression (JMA) | |
|---|---|
  | |
| Duration | September 7 – September 11 |
| Peak intensity | <55 km/h (35 mph) (10-min); 1004 hPa (mbar) |
On September 7, the JMA marked a tropical depression had formed over the Philippine Sea, at around 400 km (249 mi) to the east of Samar. At around the same time, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system, while PAGASA named the storm Inday. However, over the next two days, when Inday crossed the Visayas, it failed to strengthen much due to land interaction and high vertical wind shear. This caused the JTWC to cancel its TCFA on the system September 9. After that, the storm continued to weaken due to wind shear, and its LLCC to became even more elongated. This caused the JTWC to further decrease the chances of the system becoming a significant tropical cyclone from “medium” to “low”. On September 11, both the JMA and JTWC stopped tracking the system as it dissipated over the South China Sea.
Notable stats: Only recognized by the JMA and PAGASA as a tropical depression, but not the JTWC.
Typhoon Guchol (Josie)[]
| Max 1-min winds: | 125 kt (230 km/h) |
|---|---|
| Max 10-min winds: | 95 kt (175 km/h) |
| Min pressure: | 927 hPa (mbar) |
| ACE accumulated | 25.2 |
| TD+ days | 9.25 days |
| TS+ days | 8.25 days |
| C1+ days | 6.5 days |
| C3+ days | 2.75 days |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 2 |
| Damages | $661.6 million (USD) |
| Very Strong Typhoon (JMA) | |
|---|---|
| Category 4 typhoon (SSHWS) | |
  | |
| Duration | September 14 – September 23 (Extratropical) |
| Peak intensity | 175 km/h (110 mph) (10-min); 927 hPa (mbar) |
On September 12, the JMA noted on a tropical depression that formed in a monsoon trough, located 430 km (267 mi) to the east of Anatahan in the Northern Mariana Islands. On early September 14, noting the presence of a consolidated low-level circulation within the system, the JTWC issued a tropical cyclone formation alert (TCFA) on the storm. 12 hours later, at 12:00 UTC on the same day, the JTWC upgraded the system to Tropical Depression 17W. On the next day, at 12:00 UTC, the JTWC further upgraded 17W to a tropical storm. At the same time, as 17W entered the Philippine Area of Responsibility, the PAGASA named the system Josie. Six hours later, due to the system's deepening convection and increasing organisation, the JMA also upgraded 17W to Tropical Storm Guchol. Guchol strengthened significantly at that point, with Vortical Hot Towers (VHTs) being seen developing over the storm's centre. This prompted the JMA to further upgraded Guchol to a severe tropical storm on September 16, at 00:00 UTC. Later on the same day, the JTWC and JMA assessed Guchol to have become a typhoon at 06:00 UTC and 12:00 UTC respectively. During this time, the typhoon was exposed to very favourable conditions for development, such as sea surface temperatures (SSTs) of nearly 30 °C (86 °F) and low vertical wind shear. This allowed Guchol to start rapidly intensify over the Pacific Ocean, with satellite depicting quickly deepening convection and the formation of a well-defined 40 nmi (74 km; 46 mi) eye feature. On September 17, at 09:00 UTC, Guchol passed between Miyakojima and Okinawa in the Ryukyu Islands as a strengthening Category 3 typhoon. On the next day, at 06:00 UTC, Guchol attained its peak intensity, with maximum 1-minute sustained winds of 230 km/h (145 mph) and a minimum central pressure of 927 mbar (27.37 inHg). 12 hours after this peak, Guchol's eye became cloud-filled and ragged, and the system weakened to a Category 3 typhoon due to the start of an eyewall replacement cycle (EWRC). Furthermore, Guchol's slow movement over the East China Sea due to its recurvature to the east-northeast caused upwelling in the underlying ocean water. The decreasing sea surface temperatures also contributed to Guchol's weakening from September 18 to 20. Later on September 20, as Guchol's movement speed increased and its EWRC completed, the typhoon started to restrengthen after getting temporarily weakened to a Category 1 typhoon. On the next day, at 00:00 UTC, Guchol attained its second peak as a Category 3 typhoon. The typhoon then started to gradually weaken again after this point. Guchol made landfall over Nakatane on Tanegashima as a Category 2 typhoon at 16:00 UTC on September 21. After that, Guchol passed by the south of the Japanese Mainland over the next two days. Due to decrease sea surface temperatures and increasing wind shear, Guchol's convection became asymmetrical and its eye waned. This cased the JMA to downgrade the system to a severe tropical storm by September 22. Guchol underwent extratropical transition over the open Pacific Ocean on September 23. This prompted the JTWC to issue its last bulletin on the storm on the same day. However, the JMA continued tracking Guchol's extratropical remnants until it dissipated on September 25.
Guchol dumped heavy rainfall over the Ryukyu Islands and Southern Japan. In Nobeoka, Miyazaki, the recorded rainfall on September 21 in a 24-hour-period reached 614.3 mm (24.19 in). This caused serious flooding in the city. In Satsumasendai, Kagoshima, one person was killed due to a collapsed power pole. Meanwhile, at least eight were hospitalised throughout Kyushu with storm-related injuries. Overall in Japan, agricultural damage were about ¥83.16 billion (US$580 million). Overall damage nationwide were at ¥92.60 billion (US$645.6 million).
Notable stats: None.
Severe Tropical Storm Haebaragi (Luis)[]
| Max 1-min winds: | 65 kt (120 km/h) |
|---|---|
| Max 10-min winds: | 60 kt (110 km/h) |
| Min pressure: | 970 hPa (mbar) |
| ACE accumulated | 7.0675 |
| TD+ days | 10.5 days |
| TS+ days | 6.25 days |
| C1+ days | 1.25 days |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 13 |
| Damages | $3.302 billion (USD) |
| Severe tropical storm (JMA) | |
|---|---|
| Category 1 typhoon (SSHWS) | |
  | |
| Duration | September 29 – October 9 (Extratropical) |
| Peak intensity | 110 km/h (70 mph) (10-min); 970 hPa (mbar) |
On September 24, the JTWC noticed a tropical disturbance developing in a monsoon trough, located 530 km (329 mi) to the east of Pagan in the Northern Mariana Islands. The disturbance was designated 96W by the JTWC, and it moved slowly westward over the next few days. On September 27, the JMA upgraded the system to a tropical depression. On the next day, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on 96W as it got more organised. At 06:00 UTC on 29 September, the agency upgraded the system to a tropical depression, and designated it 18W. 18W continued to gradually strengthen, and was eventually upgraded to Tropical Storm Haebaragi by the JMA on October 1, at 00:00 UTC. Twelve hours later, the JTWC also upgraded Haebaragi to a tropical storm. Over the next day, Haebaragi started to interact with Tropical Storm Talim. As the distance between the two storms decreased, the Fujiwhara effect between the two systems became more apparent. This caused Haebaragi to move westward and eventually southwestward. On October 2, at 18:00 UTC, as Haebaragi entered the Philippine Area of Responsibility, the PAGASA named the system Luis. Haebaragi peaked as a Category 1 typhoon on October 2 and 3. After that, the storm gradually weakened due to increasing wind shear. Haebaragi made a sharp turn to the northeast on October 5 as Talim moved to the southeast of the storm. Around this time, Haebaragi weakened to a tropical depression as it convection became displaced to the northwest due to moderate to high wind shear. Over the next two days, as the distance between the storm and Talim increased, Haebaragi started to move generally northwards and slowly restrengthened. The storm made landfall over Tatsugō on Amami Ōshima on October 7, at 15:00 UTC, as a weak tropical storm. After this landfall, Haebaragi started to recurve to the northeast. The storm attained its second peak as a strong tropical storm over the East China Sea on October 8, at 06:00 UTC. Around seven hours later, Haebaragi made landfall over Tomiemachi Nagamine on Fukue Island of the Gotō Islands. After traversing the Korea Strait, the storm moved into the Sea of Japan on October 9 and accelerated northeastward. Haebaragi brushed past the northern coastline of the Noto Peninsula at 06:00 UTC on the same day. 2.5 hours later, the storm made landfall over Sado Island. Haebaragi then made landfall over Tsuruoka, Yamagata at 10:15 UTC. After moving offshore from Yamada, Iwate at 13:30 UTC, Haebaragi soon transitioned into an extratropical cyclone later that day. Haebaragi dissipated on October 12, over Russia's Kamchatka Peninsula.
When Haebaragi traversed the Korea Strait, it brought severe impacts to both South Korea and Southwestern Japan. In South Korea, a total of 168 flights were cancelled due to Haebaragi. In addition, severe flooding was reported in Changnyeong County and Jinju in South Gyeongsang Province. Over 29,000 power outages were recorded in Busan. The national economic loss totalled at ₩142 billion (US$101.6 million). In Japan, Haebaragi killed nine people and injured over 100. Widespread power outage were reported in Kyushu, with The Kyushu Electric Power Co. stated that at least 138,619 households were without power at one point from October 7 to 9. Meanwhile, a mudslide in Miyazaki Prefecture left two people dead and five people missing. A cargo ship, LKS Morrison, sank near Azuchi-Oshima Island of Nagasaki on October 8 due to rogue waves generated by Haebaragi. Six people were missing due to this incident. All in all, Haebaragi caused ¥464 billion (US$3.20 billion) of damages throughout Japan.
Notable stats: Haebaragi moved erratically due to Fujiwhara with Typhoon Talim.
Typhoon Talim (Kiyapo)[]
| Max 1-min winds: | 110 kt (205 km/h) |
|---|---|
| Max 10-min winds: | 85 kt (155 km/h) |
| Min pressure: | 945 hPa (mbar) |
| ACE accumulated | 19.88 |
| TD+ days | 10 days |
| TS+ days | 9.25 days |
| C1+ days | 6.5 days |
| C3+ days | 0.75 days |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 51 |
| Damages | $904.6 million (USD) |
| Very Strong Typhoon (JMA) | |
|---|---|
| Category 3 typhoon (SSHWS) | |
  | |
| Duration | September 30 – October 10 (Extratropical) |
| Peak intensity | 155 km/h (95 mph) (10-min); 945 hPa (mbar) |
On September 27, the JTWC noticed a tropical disturbance developing in a monsoon trough, located 180 km (112 mi) to the northwest of Alet Island in the Federated States of Micronesia. Two days later, the JMA upgraded the low-pressure area to a tropical depression. In the early hours of September 30, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system, and further upgraded it to Tropical Depression 19W at 12:00 UTC on the same day. Six hours later, the JMA upgraded 19W to Tropical Storm Talim. On October 1, at 00:00 UTC, Talim moved northwestward and entered the Philippine Area of Responsibility, prompting the PAGASA to name the storm with its local name Kiyapo. Six hours after this, the JTWC also upgraded Talim to a tropical storm. Over the two days, Talim started to move closer to Tropical Storm Haebaragi. This triggered a Fujiwhara effect between the two systems. As a result, Talim started to move northeastward from October 2 to 5. The JMA first upgraded Talim to a severe tropical storm on October, then the agency further upgraded the storm to a typhoon a day later. By October 3, Talim entered an area with favourable conditions for development, such as sea surface temperatures of 29 °C (84 °F) to 30 °C (86 °F), low vertical wind shear and excellent poleward outflow. This enabled the typhoon to rapidly develop. Talim reached its peak intensity on October 4, at 00:00 UTC, as a Category 3 typhoon with maximum 1-minute sustained winds of 205 km/h (125 mph) and a minimum central pressure of 945 mbar (27.91 inHg). 12 hours later, the typhoon started to gradually weaken. Talim started to recurve to the northwest due to the lessening influences from Haebaragi as the distance between the two storms increased. This allowed Talim to make landfall as a Category 1 typhoon over Kunigami, Okinawa, at 14:00 UTC on October 8. After this landfall, Talim travered the East China Sea from south to north as it continued to slowly weaken. The JMA downgraded Talim to a severe tropical storm by 00:00 UTC on October 9, while the JTWC downgraded Talim from a typhoon to a tropical storm 12 hours later. Talim made landfall near South Korea's Goseong County, South Gyeongsang on October 9, at 20:30 UTC, as a weakening tropical storm. After that, the system entered the Sea of Japan and turned extratropical on October 10. While the JTWC stopped tracking the system on the same day, the JMA continued tracking it until it dissipated on October 13 over the northern Pacific Ocean.
Talim caused significant disruptions to Okinawa Prefecture during its approach. The typhoon caused over 40 injuries in the prefecture, and about 800 people were evacuated to the shelters. Almost 150 flights in-and-out the prefecture were cancelled, and over 4,000 households suffered from power outage. Total damage in the prefecture reached ¥77.77 billion (US$526 million). Talim also caused severe impacts throughout the Korean Peninsula. In South Korea, Talim caused 3 deaths and economic damages of US$372 million. While in North Korea, rainfall from Talim exceeded 400 mm (15.74 in) in 24 hours in Kangwon Province. This resulted in flash flooding in Ichon County, killing 39 people in the area.
Notable stats: Talim moved erratically due to Fujiwhara with Severe Tropical Storm Haebaragi.
Typhoon Khanun (Maymay)[]
| Max 1-min winds: | 95 kt (175 km/h) |
|---|---|
| Max 10-min winds: | 75 kt (140 km/h) |
| Min pressure: | 946 hPa (mbar) |
| ACE accumulated | 6.4375 |
| TD+ days | 5.25 days |
| TS+ days | 3.5 days |
| C1+ days | 2 days |
| C3+ days | N/A days |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 23 |
| Damages | $3.617 billion (USD) |
| Typhoon (JMA) | |
|---|---|
| Category 2 typhoon (SSHWS) | |
  | |
| Duration | October 11 – October 18 |
| Peak intensity | 140 km/h (85 mph) (10-min); 946 hPa (mbar) |
On October 7, the JMA noted on a developing broad area of low pressure, located 630 km (391 mi) to the west of Rota in the Northern Mariana Islands. The area of disturbance moved southeast then southwest at first. After that, it took on a more typical northwesterly track. On October 9, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system as it became more organised. The JMA upgraded the storm to a tropical depression on the same day. On October 10, at 1800 UTC, the PAGASA gave the storm the local name Maymay as the system entered the Philippine Area of Responsibility. Six hours later, the JTWC upgraded the system to Tropical Depression 20W. On October 11, at 18:00 UTC, both the JMA and the JTWC upgraded 20W to a tropical storm, with the former giving 20W the name Khanun. On October 12, at 12:00 UTC, Khanun strengthened to a typhoon from a severe tropical storm as it approached Taiwan. The typhoon reached its peak intensity as a Category 2 typhoon on October 13, at 18:00 UTC. 7.5 hours later, at 01:30 UTC on October 14, Khanun made landfall in Taitung City near peak intensity. The system crossed the island nation in eight hours, and it rapidly weakened due the rugged terrain of Taiwan's Central Mountain Range, causing the storm to lose its typhoon status. Khanun moved offshore from Taixi, Yunlin at 09:30 UTC on the same day and it entered the Taiwan Strait. At 21:00 UTC, Khanun made landfall over Shishi City, Fujian as a tropical storm. Shortly after this landfall, Khanun weakened to a tropical depression by early October 15. The remnant of Khanun then travelled a few days inland over Southern China. Finally, the system dissipated over Northern Vietnam on October 18.
Khanun brought torrential rain over most of Taiwan, with the eastern portions of Hualien and Taitung counties receiving around 300 mm (11.8 in) of rain from the typhoon. Khanun also knocked down power poles all over the island nation, leading to 31,000 houses losing power. On October 15, a man drowned in Mugua River near Wenlan Village in Xiulin, Hualien after a portion of the river bank collapsed from the flashflood. Over NT$4.83 billion (US$160 million) of damage was recorded in the country. Meanwhile, Khanun also devastated the Chinese provinces of Fujian and Guangdong. In Fujian, 339,000 people were affected by the storm, with 188,000 of them evacuated to safe places. Over 66 passenger ferry routes were suspended due to the system, and 181 port terminals were closed. In Baisha, a town located in Putian, Fujian, a landslide buried 8 houses near a hillside. This caused the death of 6 people and injured 19. Overall in Fujian and Guangdong, 11 fatalities were recorded, and ¥22.1 billion (US$3.05 billion) of economic losses were induced by Khanun.
Notable stats: None.
Tropical Storm Lan[]
| Max 1-min winds: | 40 kt (75 km/h) |
|---|---|
| Max 10-min winds: | 40 kt (75 km/h) |
| Min pressure: | 996 hPa (mbar) |
| ACE accumulated | 1.6575 |
| TD+ days | 5 days |
| TS+ days | 3 days |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 14 |
| Damages | $77.5 million (USD) |
| Tropical storm (JMA) | |
|---|---|
| Tropical storm (SSHWS) | |
  | |
| Duration | October 12 – October 18 |
| Peak intensity | 75 km/h (45 mph) (10-min); 996 hPa (mbar) |
On October 11, the JMA started to track a small low-pressure area that persisted over the South China Sea, near the Macclesfield Bank. The JTWC did not track the system at first. However, by late October 11, an ASCAT (Advanced Scatterometer) over the South China Sea unveiled a midget-sized system with a closed circulation and sustained winds reaching 25 to 30 kts (45 to 55 km/h; 30 to 35 mph). This prompted the JTWC to immediately upgrade the system to Tropical Depression 21W on October 12, at 00:00 UTC. 21W continued to move generally eastward, and it was upgraded to a tropical storm by the JTWC on October 13, at 12:00 UTC. Six hours later, the JMA also upgraded 21W to a tropical storm, and named it Lan. During this time, Lan interacted with the Southwest monsoon. This caused the system's circulation to gradually grow in size. Lan made landfall as a weak tropical storm over Cát Hải, Phù Cát, a district located in the Bình Định Province of Vietnam, on October 15, at 22:15 UTC. After making landfall, Lan rapidly weakened. The JMA downgraded the storm to a tropical depression by October 16, at 06:00 UTC. The system dissipated over Thailand on October 18.
Lan impacted several countries in Southeast Asia, especially Vietnam, Loas, Cambodia and Thailand. In Vietnam's Quảng Nam province, severe flooding occurred, where 5,180 hectares of crops were submerged under water. In Bình Định, more than 800 schools have been closed due to flash floods and strong winds from October 15 to 16. Throughout the whole Vietnam, 22 houses were completely destroyed, while 1,913 more were damaged. Lan was responsible for 2 deaths in the country, as well as economic losses of approximately 727 billion VND (US$28 million). Meanwhile, in Laos, Lan affected 52 villages and caused extensive flooding in provinces such as Attapeu, Saravan and Champasak. In Cambodia, Lan drowned eight people due to flash floods along the Mekong river banks. 6,700 Cambodians were evacuated from flood-prone regions as a result. Finally, in Thailand, 1,820 households were damaged from localised floods caused by Lan's remnants, and economic damages of ฿861 million (US$26 million) were inflicted upon the nation.
Notable stats: Upgraded to a tropical depression directly by the JTWC without the agency issuing a tropical cyclone formation alert (TCFA).
Typhoon Trau (Neneng)[]
| Max 1-min winds: | 130 kt (240 km/h) |
|---|---|
| Max 10-min winds: | 100 kt (185 km/h) |
| Min pressure: | 925 hPa (mbar) |
| ACE accumulated | 43.335 |
| TD+ days | 15.5 days |
| TS+ days | 14.5 days |
| C1+ days | 11.75 days |
| C3+ days | 3.75 days |
| SuperTY days | 0.5 days |
| C5 days | N/A |
| Fatalities | None |
| Damages | None |
| Very Strong Typhoon (JMA) | |
|---|---|
| Category 4 super typhoon (SSHWS) | |
  | |
| Duration | October 15 – October 30 (Extratropical) |
| Peak intensity | 185 km/h (115 mph) (10-min); 925 hPa (mbar) |
On October 13, the JTWC noted on a mid-level circulation developed in a tropical upper tropospheric trough (TUTT), located at 570 km (354 mi) to the east of Catanduanes. On October 14, the circulation built toward the surface, and the system developed a low-level circulation with scattered associated convection. As a result, the JMA started to track the system as a tropical depression. Meanwhile, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the storm. On October 15, at 00:00 UTC, as the storm was located in the Philippine Area of Responsibility and was classified by the PAGASA as a tropical depression, the agency gave the storm the local name Neneng. 12 hours later, at 12:00 UTC, the JTWC upgraded the system to Tropical Depression 22W. On the next day, at 06:00 UTC, deep convection started to cover the centre of 22W. This prompted the JMA to upgrade 22W to Tropical Storm Trau. The JTWC followed suit and also upgraded Trau to a tropical storm six hours later. At around the same time, as the TUTT weakened the subtropical ridge to the storm's east, Trau started to recurve northeastward over the open Pacific Ocean to the south of Japan. The JMA upgraded Trau to a severe tropical storm by October 17, at 18:00 UTC. 12 hours later, the JTWC upgraded Trau to a typhoon, while the JMA followed suit at 18:00 UTC on October 18. On the next day, due to very favourable conditions, such as 0 to 5 kt (9 km/h; 6 mph) of vertical wind shear, and sea surface temperatures of 30 °C (86 °F) to 31 °C (87.8 °F), Trau entered a phase of rapid intensification. At 18:00 UTC on that day, the 1-minute sustained winds of Trau increased by 65 km/h (40 mph) within just six hours. The typhoon reached its first peak as a Category 4 typhoon by October 20, at 00:00 UTC, with 1-minute sustained winds of 230 km/h (145 mph) and a minimum central pressure of 931 mbar (27.49 inHg). Later on the same day, Trau started its first eyewall replacement cycle (EWRC), which caused its eye to become cloud-filled, and the convection over its central dense overcast (CDO) to become warmer and uneven. As a result, by October 21, Trau temporarily weakened to a Category 2 typhoon. However, as Trau's EWRC was completed by early October 22, the typhoon's central deep convections started to build up again, with its eye starting to become apparent on satellite imagery. During this time, a TUTT cell to the storm's northeast also provided excellent polar outflow for the system. This caused Trau to start a second phase of rapid intensification. On October 23, at 12:00 UTC, the 1-minute sustained winds of Trau reached 240 km/h (150 mph). This made the JTWC upgrading the system to the season's second super typhoon. Trau attained its second peak six hours later as a strong Category 4 storm, with 1-minute sustained winds of 240 km/h (150 mph) and a minimum central pressure of 925 mbar (27.32 inHg). After this peak, Trau moved northwards and entered an area of the Pacific Ocean with colder waters. This caused the typhoon to slowly weaken. Trau lost its major typhoon status by October 24 according to the JTWC, an it weakened to a Category 1 typhoon on the next day. At around this time, while Trau was initially expected to continue its northeast movement, a development of a trough to the typhoon's east caused the system to unexpectedly turn due-eastward. This brought Trau to warmer waters and lower vertical wind shear. As a result, Trau managed to strengthen to a Category 2 typhoon by October 27, at 00:00 UTC. However, this window of restrengthening was short-lived, as dry-air started to get wrapped into Trau's core, and wind shear started to make the system's convection displaced. This caused Trau to lose its typhoon status by October 29 according to the JMA. Due to the weakening of the aforementioned TUTT cell, Trau resumed its northeastward movement after October 30. On the next day, the system started its extratropical transition. While the JTWC issued their final bulletin on the storm this day, the JMA continued tracking Trau's extratropical remnants. Trau's extratropical cyclone moved near the Aleutian Islands by late October 31, and it dissipated on November 2 over the northern Pacific Ocean.
Notable stats: Trau was the second super typhoon of the season and the second largest ACE producer of the season.
Tropical Storm Damrey (Obet)[]
| Max 1-min winds: | 30 kt (55 km/h) |
|---|---|
| Max 10-min winds: | 35 kt (65 km/h) |
| Min pressure: | 1000 hPa (mbar) |
| ACE accumulated | 0 |
| TD+ days | 3 days |
| TS+ days | N/A |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | None |
| Damages | None |
| Tropical storm (JMA) | |
|---|---|
| Tropical depression (SSHWS) | |
  | |
| Duration | October 22 – October 25 |
| Peak intensity | 65 km/h (40 mph) (10-min); 1000 hPa (mbar) |
On October 18, two areas of low pressure were developing within a monsoon trough that extended from the Philippine Sea to the Caroline Islands. The western disturbance, located 165 km (103 mi) to the northwest of Eauripik Atoll, developed first and was upgraded to a tropical depression by the JTWC on October 20, at 18:00 UTC. Meanwhile, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system on the next day. On October 22, at 00:00 UTC, the JTWC upgraded the system to a tropical depression, and designated it as 23W. Six hours later, as 23W entered the Philippine Area of Responsibility, the PAGASA gave the system the local name Obet. On October 23, at 00:00 UTC, as the system gradually strengthened, the JMA further upgraded the system to a tropical storm and named it Damrey. However, the JTWC never upgraded Damrey to a tropical storm during its lifetime. Over the next two days, as the distance between Damrey and Tropical Storm Shuixian, which had developed from the eastern tropical disturbance inside the same monsoon trough that Damrey had formed, rapidly decreased, wind shear brought by Shuixian's extensive inflow caused Damrey to rapidly weaken. By late October 24, the JTWC issued its last warning on the system as the agency expected Damrey's soon dissipation. Meanwhile, the JMA tracked Damrey till it got absorbed into the outer rainbands of Shuixian on the October 25, at 06:00 UTC.
Notable stats: Damrey was absorbed into the rainbands of Shuixian. Moreover, Damrey was the second storm this season that was recognised by the JMA as a tropical storm but not the JTWC.
Typhoon Shuixian (Pilandok)[]
| Max 1-min winds: | 165 kt (305 km/h) |
|---|---|
| Max 10-min winds: | 120 kt (220 km/h) |
| Min pressure: | 877 hPa (mbar) |
| ACE accumulated | 32.035 |
| TD+ days | 10.75 days |
| TS+ days | 8.75 days |
| C1+ days | 6.5 days |
| C3+ days | 3 days |
| SuperTY days | 1.5 days |
| C5 days | 1.25 days |
| Fatalities | 175 |
| Damages | $22.576 billion (USD) |
| Violent Typhoon (JMA) | |
|---|---|
| Category 5 super typhoon (SSHWS) | |
  | |
| Duration | October 23 – November 4 |
| Peak intensity | 220 km/h (135 mph) (10-min); 877 hPa (mbar) |
On October 18, two areas of low pressure were developing within a monsoon trough that extended from the Philippine Sea to the Caroline Islands. The low-pressure area to the east, located around 40 km (25 mi) to the north of the Hall Islands in the Federated States of Micronesia. Due to the large size of the disturbance's circulation, the system took several days to tighten its circulation. On October 22, the JMA upgraded the system from a low-pressure area to a tropical depression. On the same day, the JTWC had also raised the system's chance to develop into a significant tropical cyclone from "low" to "medium". On October 23, at 12:00 UTC, the JTWC noted on the closed low-level circulation centre (LLCC) of the storm. As a result, the agency upgraded the system to Tropical Depression 24W at that time. On October 24, as 24W continued to deepen, the JMA upgraded the storm to Tropical Storm Shuixian at 12:00 UTC. 12 hours later, the JTWC also upgraded Shuixian to a tropical storm. On October 25, Tropical Depression Damrey, which was sheared by Shuixian's outflow, was teared apart and absorbed into the latter's spiral bands. At 12:00 UTC on the same day, as Shuixian entered the Philippine Area of Responsibility, the PAGASA named the storm with the local name Pilandok. After this, Shuixian entered a favourable environment for development, with low to moderate vertical wind shear, good divergence aloft, and warm sea surface temperatures. This caused the JMA to upgrade the system to a severe tropical storm on October 26. In the late hours of the same day, the JTWC noted on the development of a microwave eye underneath Shuixian's developing central dense overcast (CDO). The prompted the agency to upgrade Shuixian to a minimal typhoon at 18:00 UTC that day. Meanwhile, the JMA also upgraded Shuixian to a typhoon six hours later. On October 27, Shuixian started to rapidly intensify due to extremely favourable environmental conditions over the Philippine Sea. The JTWC upgraded Shuixian to a Category 5 super typhoon on October 28, at 00:00 UTC, making the storm the second Category 5 storm and the third super typhoon of the season. The typhoon also had an estimate central pressure of 903 mbar (26.67 inHg) at this time. Shuixian continued to strengthen for the next 24 hours, until it reached its peak intensity on October 29, at 00:00 UTC, with maximum 1-minute sustained winds of 305 km/h (190 mph) and a minimum central pressure of 877 mbar (25.90 inHg). Two hours later, at 02:00 UTC, the typhoon made landfall over Maconacon, in the Isabela Province on Luzon, at peak intensity. This made the storm the strongest landfalling cyclone over the Philippines since Typhoon Bang-Lang in 2049. After this landfall, Shuixian rapidly weakened due to the mountainous terrain of Luzon. Shuixian crossed Luzon in 13 hours hours, and it moved offshore from Darapida, Candon City, Ilocos Sur into the South China Sea at 15:00 UTC as a weakening Category 2 typhoon. After bottoming as a strong Category 1 typhoon, warm sea surface temperatures and low to moderate wind shear over the South China Sea allowed Shuixian to start reconstructing its damaged core. This caused the typhoon to start slowly restrengthening. By late October 30, the existence of a trough to the system's north drove Shuixian to start moving northwards towards Southern China. Shuixian reached its secondary peak over the South China Sea on October 31, at 06:00 UTC, as a Category 3 typhoon. After this, increasing wind shear and land interaction with the Asian continent caused Shuixian to start slowly weakening again. On November 1, at 18:15 UTC, Shuixian made landfall over Huilai County, Guangdong, China as a strong Category 1 typhoon. After its China landfall, Shuixian rapidly weakened as it moved over land and recurved. On November 2, at 06:00 UTC, the JMA downgraded Shiuxian to a severe tropical storm. The system then got further downgraded by the agency to a tropical storm and tropical depression at 12:00 UTC and 18:00 UTC on the same day respectively. At the late hours of the same day, Shuixian moved offshore and entered the East China Sea as a weakening tropical depression. While the JTWC stopped issuing warnings on the system at this time, the JMA continued tracking the storm till it dissipated on November 4 after crossing the Ryukyu Islands.
Being the strongest storm to make direct landfall in two decades, Shuixian brought extreme devastation to the Philippines, especially in Luzon. The mountains of Luzon created significant orographic lifting, which caused torrential rain to be observed throughout the island. In the municipality of Bakun, Benguet, the 1,000-millimetre (39-inch) rain gauge overflowed; and in nearby Bokod, the accumulated rainfall recorded reached 1,309 mm (51.5 in) on October 29 alone, making it a one-in-3,611-year event according to statistical models. Apart from severe flooding, Shuixian knocked down trees and power lines, causing 670,000 households to lose power in Luzon. Along its path, the typhoon destroyed 19,650 houses and damaged another 87,903. Overall, Shuixian killed 127 people in the Philippines, mostly caused by landslides, while injuring another 85. Total damage in the country was estimated at ₱150.2 billion (US$2.59 billion). Meanwhile, Shuixian also brought significant impacts to the Chinese provinces of Guangdong and Fujian; a total of 119,850 hectares of crops and 1,804 houses were destroyed by the storm in these two provinces, with total fatalities and overall economy losses incurred there reaching 41 and CN¥136 billion (US$18.79 billion) respectively.
Notable stats: Shuixian was the most intense storm of the season; the third super typhoon and second Category 5 storm of the season; the second-deadliest and the costliest storm of the season; the first and only storm to inflict over US$10 billion of damages this season; and the third largest ACE producer of the season. Shuixian was also the strongest landfalling cyclone over the Philippines since Typhoon Bang-Lang in 2049. Shuixian absorbed Damrey when it moved eastward over the Philippine Sea.
Typhoon Kirogi[]
| Max 1-min winds: | 145 kt (270 km/h) |
|---|---|
| Max 10-min winds: | 105 kt (195 km/h) |
| Min pressure: | 898 hPa (mbar) |
| ACE accumulated | 17.07 |
| TD+ days | 5.75 days |
| TS+ days | 4.5 days |
| C1+ days | 3.25 days |
| C3+ days | 2.25 days |
| SuperTY days | 0.75 days |
| C5 days | 0.25 days |
| Fatalities | None |
| Damages | None |
| Violent Typhoon (JMA) | |
|---|---|
| Category 5 super typhoon (SSHWS) | |
 | |
| Duration | November 2 – November 8 (Extratropical) |
| Peak intensity | 195 km/h (120 mph) (10-min); 898 hPa (mbar) |
A weak tropical disturbance that was designated as 93C by the Central Pacific Hurricane Center (CPHC) crossed the International Date Line and entered the basin from the Central Pacific late on October 29. On the next day, the JMA upgraded the system from a low-pressure area to a tropical depression. Over the next two days, as 93C entered the subsident region of a tropical upper tropospheric trough (TUTT) cell to its northwest, it was faced with a marginal environment for development, with conditions such as moderate to high vertical wind shear and limited upper-level divergence. These conditions caused the system to remain rather disorganised from October 31 to November 1, with its low-level circulation center (LLCC) exposed. However, by late November 1, the system managed to organise itself better due to the lessening of wind shear. This prompted the JTWC to issue a Tropical Cyclone Formation Alert (TCFA) on 93C at 00:00 UTC on November 2. The agency then further upgraded 93C to tropical depression 25W. On the next day, at 06:00 UTC, as the system has developed deep convection that completely covered its LLCC, the JMA upgraded the system to Tropical Storm Kirogi. 12 hours later, the JTWC also followed suit and upgraded Kirogi to a tropical storm. Over the next day, Kirogi moved steadily westward as it was moving along the southwest periphery of the deep-layered subtropical ridge positioned to the northeast while it steadily strengthened. The JMA upgraded Kirogi to a typhoon on November 4, at 12:00 UTC. After this point, Kirogi was provided with favourable conditions for development, such as very low vertical wind shear, decent sea surface temperatures and extremely strong poleward outflow that tapped into the Westerlies. This caused the typhoon to enter a phase of explosive intensification. In the 12-hour period from November 4 18:00 UTC to November 5 06:00 UTC, Kirogi's 1-minute sustained winds increased by 120 km/h (75 mph), while its minimum central pressure fell 65 mbar (1.92 inHg), making the typhoon one of the fastest intensifying tropical cyclones on record. At its peak, at 06:00 UTC on November 5, Kirogi had maximum 1-minute sustained winds of 270 km/h (165 mph) and a minimum central pressure of 898 mbar (26.52 inHg). After maintaining Category 5 strength for six hours, Kirogi started to weaken as the typhoon encountered increasing wind shear. The typhoon lost its Category 4 status on November 6, at 18:00 UTC, and it started to recurve to the northeast. The JMA downgraded Kirogi to a severe tropical storm in the late hours of the next day, while the JTWC issued its final warning on the system by early November 8. On November 8, the JMA noted on the extratropical transition of Kirogi, and the system dissipated near the Alaska Peninsula on November 13.
Notable stats: Kirogi was the fourth super typhoon and the third and final Category 5 storm of the season. It was also one of the fastest intensifying tropical cyclones in record; a 120 km/h (75 mph) increase in 1-minute sustained winds and 65 mbar (1.92 inHg) drop in central pressure in a 12-hour period from November 4 18:00 UTC to November 5 06:00 UTC.
Typhoon Yun-yeung[]
| Max 1-min winds: | 90 kt (165 km/h) |
|---|---|
| Max 10-min winds: | 75 kt (140 km/h) |
| Min pressure: | 959 hPa (mbar) |
| ACE accumulated | 6.13 |
| TD+ days | 4.25 days |
| TS+ days | 3.25 days |
| C1+ days | 2 days |
| C3+ days | N/A days |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | None |
| Damages | None |
| Typhoon (JMA) | |
|---|---|
| Category 2 typhoon (SSHWS) | |
  | |
| Duration | November 7 – November 11 (Extratropical) |
| Peak intensity | 140 km/h (85 mph) (10-min); 959 hPa (mbar) |
On November 4, the JTWC noted a tropical disturbance has formed 640 km (398 mi) to the east-southeast of Guam. The disturbance was designated as 92W by the agency that day. Meanwhile, the JMA upgraded 92W from a low-pressure area to a tropical depression on the next day. After this, 92W organised itself gradually, and the JTWC raised the system's chance to develop into a significant tropical cyclone from "low" to "medium". However, increasing wind shear on November 6 disrupted the storm's development, causing the agency to downgrade 92W's chance to develop into a significant tropical cyclone back to "low". Despite this, wind shear started to decrease soon afterwards, creating another window for 92W reintensify. The disturbance seized this window and reorganised itself. By November 7, the JTWC noted on 92W's closed low-level circulation centre (LLCC) and issued a Tropical Cyclone Formation Alert (TCFA) on the system. Just six hours later, at 18:00 UTC on the same day, the JTWC upgraded 92W to Tropical Depression 26W. On November 8, the storm started to move northeastward due to a trough located to its northeast. 26W continued to strengthen, and the JTWC upgraded the tropical depression to a tropical storm at 18:00 UTC, on November 8. Six hours later, the JMA also upgraded 26W to a tropical storm, and named it Yun-yeung. Yun-yeung then continued to construct its central dense overcast (CDO), and a primitive eye feature could soon be observed on satellite. This prompted both the JMA and the JTWC to upgrade Yun-yeung to a typhoon on November 9. On the next day, at 18:00 UTC, Yun-yeung peaked as a Category 2 typhoon with 1-minute sustained winds of 165 km/h (105 mph) and a minimum pressure of 959 mbar (28.32 inHg). After this, Yun-yeung started to interact with the Westerlies, which caused the typhoon to weaken due to drastically increased wind shear. The JMA downgraded Yun-yeung from a typhoon to a severe tropical storm on November 11, at 12:00 UTC, while the JTWC issued its last warning on the system six hours later as it noted on the storm's extratropical transition. Yun-yeung completed its extratropical transition by November 12, and its extratropical remnant dissipated near the International Date Line on November 15, at 12:00 UTC.
Notable stats: None.
Tropical Depression 27W (Queenie)[]
| Max 1-min winds: | 25 kt (45 km/h) |
|---|---|
| Max 10-min winds: | 30 kt (55 km/h) |
| Min pressure: | 1003 hPa (mbar) |
| ACE accumulated | 0 |
| TD+ days | 2.25 days |
| TS+ days | 0 days |
| C1+ days | 0 days |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 6 |
| Damages | $8.5 million (USD) |
| Tropical depression (JMA) | |
|---|---|
| Tropical depression (SSHWS) | |
  | |
| Duration | November 21 – November 26 |
| Peak intensity | 55 km/h (35 mph) (10-min); 1003 hPa (mbar) |
On November 20, the JMA upgraded a low-pressure area developing 310 km (193 mi) to the east of Baganga, Davao Oriental on Mindanao to a tropical depression. At 12:00 UTC on the same day, the PAGASA recognised the system as a tropical depression, hence granting it the local name Queenie. Six hours later, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system. On November 21, at 06:00 UTC, the JTWC also upgraded the system to a tropical depression, and gave it the designation 27W. 27W traversed the portion of the Philippine Sea to the east of Mindanao over the new few days. On November 22, as 27W was approaching the Dinagat Islands, moderate to strong vertical wind shear displaced the system's convection to its southwest. This caused the JTWC to issue its final warning on the system on the same day as it expected 27W to dissipate. However, the remnants of 27W, which was regarded as a tropical disturbance by the JTWC, managed to persist and it crossed the southern portion of the Visayas and eventually reached Palawan (island) by November 25. On the same day, decreasing vertical wind shear allowed 27W to reorganise its convection again. As a result, the JTWC issued another Tropical Cyclone Formation Alert (TCFA) on the storm and upgraded 27W to a tropical depression again by November 26, at 00:00 UTC. Shortly after this, increased wind shear and cold air from the Northeast monsoon caused the system's convection to become fragmented. This caused the JTWC to issue another final bulletin on the storm only 12 hours its tropical depression upgrade. Meanwhile, the JMA noted on 27W's dissipation over the South China Sea on November 26 at 12:00 UTC.
Despite just being a remnant low when crossing the Philippines, torrential rainfall from 27W brought considerable damage to the regions of the Visayas and Mindanao. Across these two regions, 162,903 people were affected, 16,480 people were displaced, 7,927 people were evacuated, and 3,143 houses were damaged. In addition, over 200 landslides were reported across the islands of Mindanao, Samar, Leyte, Bohol, Cebu and Negros. In Bayugan, Agusan del Sur, flash floods from the Andanan River have claimed the lives of two people. Overall, ₱464 million (US$8.3 million) of economic damages and 6 fatalities were recorded in the Philippines.
Notable stats: None.
Tropical Storm Koinu (Rosal)[]
| Max 1-min winds: | 45 kt (85 km/h) |
|---|---|
| Max 10-min winds: | 45 kt (85 km/h) |
| Min pressure: | 994 hPa (mbar) |
| ACE accumulated | 1.2525 |
| TD+ days | 5.5 days |
| TS+ days | 2 days |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 19 |
| Damages | $41.6 million (USD) |
| Tropical storm (JMA) | |
|---|---|
| Tropical storm (SSHWS) | |
  | |
| Duration | November 30 – December 6 |
| Peak intensity | 85 km/h (55 mph) (10-min); 994 hPa (mbar) |
On November 27, the JMA reported that a low-pressure area had developed within a trough of low pressure, about 390 km (242 mi) to the north-west of Palau. Over the next few days, the storm moved towards the west-northwest along the southern edge of the subtropical ridge of high pressure. By November 29, as the system's low-level circulation centre (LLCC) gradually consolidated further, the JMA upgraded the system to a tropical depression. Meanwhile, on the next day, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the storm. Also on November 30, the PAGASA recognised the system as a tropical depression in their area of responsibility. This prompted the agency to name the storm with the local name Rosal. At 18:00 UTC on the same day, the JTWC upgraded the system to Tropical Depression 28W. An hour after making a brief landfall over the Dinagat Islands, when 28W was located above the Surigao Strait, both the JMA and the JTWC upgraded 28W to a tropical storm at 06:00 UTC on December 1, with the former naming the storm Koinu. After this, Koinu continued to move west-northwestward and passed over or close to several of the Visayan Islands. By 18:00 UTC on the same day, when Koinu was located over the Visayan Sea, the storm reached its peak intensity with maximum 1-minute sustained winds of 85 km/h (50 mph) and a minimum central pressure of 994 mbar (29.35 inHg). The storm then switched to move westward towards Panay. Three hours later, Koinu first made landfall over Calagnaan Island, the shortly after the system made landfall over Estancia, Iloilo on the Island of Panay. This landfall caused Koinu to start weakening, and the system moved offshore from Panay on December 2, at 06:00 UTC. After making its final landfall over Culion Island at 17:00 UTC on the same day, Koinu moved into the South China Sea. By December 3, both the JMA and the JTWC reported that Koinu had become a tropical depression, after its low level circulation center became partially exposed within an area of moderate to strong vertical wind shear. The system slowly recurved towards the northeast over the South China Sea. On December 5, The JTWC issued its final warning on the system as north-easterly cold surge had caused the depression to become fully exposed. Koinu subsequently was last noted during the next day by both the JTWC and the JMA, dissipating about 170 km (106 mi) to the west of Luzon.
Koinu caused significant disruption to the Philippines. As the storm approached the island nation, many ports in Visayas and Mindanao were closed, and domestic flights were disrupted. Across the country, nearly 5,000 people were stranded due to cancellation of flights and ship vessels. In addition, over 63,000 people were evacuated in Iloilo and Leyte in advance of Koinu's approach. In Samar, seven people were killed by the storm: Four were washed away by floodwaters while the three others were hit by downed trees. Many place in Leyte, Samar, Panay and Negros Island were also flooded. Part of a national highway in Kabankalan, Negros Occidental was blocked by flooding, and two villages in Kalibo, Aklan were completely submerged. Overall across the Philippines, 313,099 people were affected by the storm. 19 people were killed, with most of the fatalities occurred in the Eastern Visayas. At the same time, the storm also caused 11 injuries and left 3 others missing. Economic damage across the Philippines reached ₱2.33 billion (US$41.6 million).
Notable stats: None.
Tropical Storm Bolaven (Samuel)[]
| Max 1-min winds: | 35 kt (65 km/h) |
|---|---|
| Max 10-min winds: | 40 kt (75 km/h) |
| Min pressure: | 1000 hPa (mbar) |
| ACE accumulated | 0.49 |
| TD+ days | 6.5 days |
| TS+ days | 1 day |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 54 |
| Damages | $321.9 million (USD) |
| Tropical storm (JMA) | |
|---|---|
| Tropical storm (SSHWS) | |
  | |
| Duration | December 5 – December 17 |
| Peak intensity | 75 km/h (45 mph) (10-min); 1000 hPa (mbar) |
The JMA recognised a low-pressure area has developed into a tropical depression 290 km (180 mi) to the east of Samar late on December 2. As a result, the JMA began to issue tropical cyclone warnings on the system early on the next day. Also on December 3, the PAGASA assessed the system to be a tropical depression inside its Area of Responsibility. This caused the PAGASA to name the storm with its local name Samuel. Over the next few days, the system barely moved due to weak steering currents between a subtropical ridge over the western Pacific and another over the Bay of Bengal. As the system slowly developed, on December 5, at 00:00 UTC, JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the storm. At this time, the system entered area of very low wind shear, which allowed the storm to attain better organisation and banding. As a result, the JMA upgraded the system to Tropical Storm Bolaven on December 5 at 18:00 UTC. The JTWC followed suit six hours later and also upgraded Bolaven to a tropical storm. On December 6, despite Bolaven initially expanded and managed to maintain its convection, medium to high wind shear prevented the storm from developing much. As a result, the system just maintained its intensity as a minimal tropical storm over the next day. During this time, the storm barely moved as it was trapped between two subtropical ridges to its north and northeast. On early December 7, Bolaven started to collapse because of strong wind shear and weak equatorward outflow. This caused both the JMA and JTWC to downgrade Bolaven to a tropical depression on the same day. After moving slowly towards the island of Samar, Bolaven made landfall over Arteche, Eastern Samar on December 7 at 18:00 UTC as a tropical depression. Over the next two days, Bolaven passed through the northern Visayas and remained as a tropical depression due to the marginal environment for development. By December 9, when Bolaven passed to the north of Busuanga Island, strong wind shear have displaced the storm's convection to its southeast significantly, and the system's low-level circulation centre (LLCC) became fragmented. Due to the deeply unfavourable environment surrounding Bolaven, the JTWC noted on the system's imminent dissipation and issued a final warning on the storm by 06:00 UTC that day. Despite that the JTWC downgraded Bolaven to an invest shortly after, the JMA kept tracking the system as a tropical depression. The remnants of Bolaven then moved southwestward over the South China Sea over the next few days. On December 13, when Bolaven approached the area of the South China Sea south of Vietnam's Cà Mau Peninsula, wind shear started to decrease. This allowed the storm's convection to cover up its LLCC again. As a result, the JTWC issued its second TCFA on the system by 06:00 UTC that day. 12 hours later, the JTWC upgraded Bolaven to a tropical depression again. From December 14 to 15, Bolaven stalled over the South China Sea to the east of the Malay Peninsula. During this time, stronger wind shear started to affect the system again. As a result, the JTWC issued its last warning on Bolaven at 18:00 UTC on December 15. While the JTWC marked the dissipation of Bolaven on December 16, the JMA continued tracking the storm's remnant after it made landfall over Marang, Terengganu of Malaysia on December 16, at 09:00 UTC. Finally, the JMA noted on Bolaven's dissipation by early December 17 over Pahang.
Due to its extreme rainfall, Bolaven brought devastating impacts to the Philippines despite it only hitting the island nation as a weak tropical storm. Across the country, over 1,400,000 individuals were affected by the storm. In Luzon and the Visayas, power lines in 41 settlements toppled and bridges collapsed. Moreover, power outages were reported in the provinces of Romblon and Marinduque. The intense rainfall of Bolaven also induced thousands of landslides across the Visayas. In Naval, Biliran, a landslide killed 19 people. Similar landslides have also claimed multiple lives in other areas, such as three in Samar, and nine in Leyte. In Tacloban, the city saw flash floods up to heights of 1.8 m (5.9 ft), which caused the destruction of 3,100 hectares (7,660 acres) of paddy fields, or about 95% of Tacloban's rice. In Eastern Samar, on December 8, 1,139 mm (44.8 in) of rain was recorded in Guiuan, while 1,016 mm (40.0 in) of rain was recorded at Borongan Airport. Overall, 54 people were confirmed dead in the Philippines, and ₱18.12 billion (US$317 million) of damages were recorded in the country. In addition, 69,138 homes across the nation were damaged, with 4,042 of them being totally destroyed.
Notable stats: None.
Typhoon Sanba (Tomas)[]
| Max 1-min winds: | 135 kt (250 km/h) |
|---|---|
| Max 10-min winds: | 100 kt (185 km/h) |
| Min pressure: | 920 hPa (mbar) |
| ACE accumulated | 17.46 |
| TD+ days | 9.5 days |
| TS+ days | 8.5 days |
| C1+ days | 3.75 days |
| C3+ days | 1.25 days |
| SuperTY days | 0.5 days |
| C5 days | N/A |
| Fatalities | 307 |
| Damages | $5.065 billion (USD) |
| Very Strong Typhoon (JMA) | |
|---|---|
| Category 4 super typhoon (SSHWS) | |
  | |
| Duration | December 21 – December 31 |
| Peak intensity | 185 km/h (115 mph) (10-min); 920 hPa (mbar) |
On December 19, the JTWC reported that a tropical disturbance had persisted at about 450 km (280 mi) to the southwest Satawan Atoll in the Federated States of Micronesia. During this time, while the system was slowly moving northwestward, spiral bands were flaring around the system's poorly defined low-level circulation centre (LLCC). As the aforementioned LLCC slowly consolidated over the next two days due to lowering wind shear, the JMA upgraded the system from a low-pressure area to a tropical depression by early December 21. Meanwhile, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system at 06:00 UTC. Just six hours later, the storm's LLCC quickly become closed and organised, and deep convection fed by the spiral bands covered the system's centre. This caused the JTWC to further upgrade the system to Tropical Depression 30W. Six more hours later, the JTWC upgraded 30W to a tropical storm due to its rapid development. During this time, the storm started to move southwestward as it was influenced by a subtropical ridge of high pressure that was located to the south of Japan. On December 22 at 00:00 UTC, the JMA also upgraded the system to a tropical storm, and named it Sanba. After this, Sanba's westward motion increased, and the storm started to move due-westward and eventually west-northwestward. After reaching a temporary peak on December 22, Sanba's slightly weakened, and its circulation became exposed as thunderstorms became limited to its southern periphery due to reduced outflow to the south. The JTWC noted that Sanba has failed to intensify significantly due to the limited Coriolis force caused by its low latitude. However, as Sanba's latitude gradually increased after December 23, and the storm entered an area favourable for development with conditions such as warm waters and low vertical wind shear on the next day, the JMA upgraded Sanba to a severe tropical storm by December 24. On the same day, at 18:00 UTC, as Sanba entered the Philippine Area of Responsibility, the PAGASA named the storm with the local name Tomas. Six hours later, on December 25 at 00:00 UTC, the JTWC upgraded Sanba to a typhoon while it was located at about 160 km (99 mi) to the southwest of Palau. As the storm continued to intensify, organised bands of thunderstorms began to feed into Sanba, which led to an increase of the typhoon's size. Several ot towers up to 17 km (11 mi) high were also observed to have developed over Sanba's central dense overcast (CDO) at around this time. By mid-December 25, a ragged, eye-like feature started to appear in microwave imagery. This eye feature eventually developed into Sanba's pinhole eye. This, together with favourable environmental conditions, such as an anticyclone located to the northeast of the storm that provided the system with ample radial outflow, allowed Sanba to rapidly deepen. In a 24-hour period starting from December 25 at 12:00 UTC, Sanba's 1-minute sustained winds increased by 95 km/h (60 mph), while its minimum central pressure fell 44 mbar (1.30 inHg). On December 26, at 12:00 UTC, the JTWC upgraded Sanba to a super typhoon, the fifth of the season. Six hours later, Sanba reached its peak intensity as a Category 4 super typhoon, with 1-minute sustained winds of 250 km/h (155 mph) and a minimum central pressure of 920 mbar (27.17 inHg). After this peak, land interaction with Mindanao caused Sanba to weaken prior to its landfall. At 20:00 UTC on the same day, Sanba made landfall over Cortes, Surigao del Sur on Mindanao as a Category 4 typhoon. An hour later, Sanba's eye feature dissipated over the mountainous terrain of Mindanao, and its convection on its western side weakened substantially. The typhoon emerged in the Bohol Sea as a weakening Category 3 typhoon, and it continued to weaken as it passed through the various Visayan Islands. On December 27, Sanba entered the Sulu Sea as a Category 1 typhoon. The typhoon then made landfall over Roxas, Palawan at 06:20 UTC on December 28. After crossing Palawan, Sanba entered the South China Sea around 90 minutes later. Over the South China Sea, the surge of Northeast monsoon brought in significant wind shear and dry air, while at the same time causing Sanba to move west-southwestward. This caused Sanba to weaken rapidly as its convection was unable to develop over the fully exposed LLCC. The JMA downgraded Sanba from a typhoon to a severe tropical storm at 12:00 UTC on December 28, while the JTWC downgraded the storm from a typhoon to a tropical storm six hours later. By December 30, Sanba weakened to a tropical depression, and the JTWC issued its final warning over the system. One day later, Sanba dissipated over the South China Sea.
Sanba was the worst storm to affect Mindanao since Typhoon Barijat in 2062. Strong winds and extreme rainfall from the storm have devastated much of the island. The cities of Cagayan de Oro and Iligan were the hardest hit by Sanba's rainfall, where 83 people lost their lives due to flash floods, and residents affected by these flood waters were forced to seek refuge on their roofs amidst typhoon-force winds. At the same time, the heavy rainfall of Sanba triggered multiple landslides over the island nation. In a mudslide in the mountainous town of New Bataan, Davao de Oro, 51 people lost their lives as their homes were buried and destroyed by the mud. 26 others also died in mudslides in other settlements in Mindanao. Overall, At least 298,000 people were evacuated from their homes in the Philippines, with total economic damage and fatalities reaching ₱290.6 billion (US$5.06 billion) and 306 respectively in the nation.
Notable stats: Sanba was the fifth and final super typhoon and the last storm of the season. It was also the deadliest and fourth-costliest storm of the season. Sanba was Mindanao's deadliest storm since 2062's Typhoon Barijat.
Storm names[]
- See also: Tropical cyclone naming and History of tropical cyclone naming
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. 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).
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. The names of significant tropical cyclones are retired, by both PAGASA and the Typhoon Committee. 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. The names of significant tropical cyclones were retired by both PAGASA and the Typhoon Committee in the spring of 2067.
International names[]
- Main article: List of retired Pacific typhoon names
During the season, 28 tropical storms developed in the Western Pacific and all of them were named by the JMA once they had 10-minute sustained winds 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.
| Merbok | Nanmadol | Talas | Hodu | Kulap | Roke | Sonca | Nesat | Haitang |
| Jamjari | Banyan | Yamaneko | Pakhar | Sanvu | Mawar | Guchol | Talim | Haebaragi |
| Khanun | Lan | Trau | Damrey | Shuixian | Kirogi | Yun-yeung | Koinu | Bolaven |
| Sanba |
Other names[]
If a tropical cyclone enters the Western Pacific basin from the Eastern and Central Pacific basin (west of 180°E), it will retain the name assigned to it by the National Hurricane Center (NHC) and Central Pacific Hurricane Center (CPHC). The following storms were named in this manner.
- Wali
Retirement[]
At their 98th Session in February 2067, the Typhoon Committee announced that the names Hodu, Roke, Haitang, Khanun, Shuixian, Bolaven and Sanba would be removed from the naming lists, and they will never be used again to name another typhoon. In 2068, they were replaced by Baechu, Kurihi, Mudan, Makham, Zhuque, Kaipen and Taipa respectively.
Philippines[]
- Main article: List of retired Philippine typhoon names
| Main list | ||||
|---|---|---|---|---|
| Ada | Basyang | Caloy | Domeng | Ester |
| Francisco | Gardo | Henry | Inday | Josie |
| Kiyapo | Luis | Maymay | Neneng | Obet |
| Pilandok | Queenie | Rosal | Samuel | Tomas |
| Umberto (unused) | Venus (unused) | Waldo (unused) | Yayang (unused) | Zeny (unused) |
| Auxiliary list | ||||
| Agila (unused) | Bagwis (unused) | Chito (unused) | Diego (unused) | Elena (unused) |
| Felino (unused) | Gunding (unused) | Harriet (unused) | Indang (unused) | Jessa (unused) |
During the season, PAGASA used its own naming scheme for the 20 tropical cyclones, that either developed within or moved into their self-defined area of responsibility. The names were taken from a list of names, that was last used during 2062 and are scheduled to be used again during 2070.
Retirement[]
On February 3, 2067, PAGASA announced that the names Ada, Francisco, Pilandok, Samuel and Tomas would be retired from the naming list, after they caused over ₱4 billion in damages to the Philippines. They were replaced on the naming list with the names Amparo, Felix, Paquita, Silvino and Tobias respectively. These new names will first appear in the 2070 season.
Season effects[]
This table summarizes all the systems that were active in the North Pacific Ocean, west of the International Date Line, during 2066. It also provides an overview of each system's intensity, duration, land areas affected, and any associated deaths or damages.
| Name | Dates active | Peak classification | Sustained wind speeds |
Pressure | Areas affected | Damage (USD) |
Deaths | Refs |
|---|---|---|---|---|---|---|---|---|
| TD | April 7-11 | Tropical depression | Not specified | 1006 hPa (29.71 inHg) | Vietnam, Cambodia, Laos | None | None | |
| Merbok (Ada) | May 16-26 | Very strong typhoon | 165 km/h (105 mph) | 942 hPa (27.82 inHg) | Palau, Philippines | $89.3 million | 4 | |
| 02W (Basyang) | June 2-5 | Tropical depression | 55 km/h (35 mph) | 1001 hPa (29.56 inHg) | Philippines, South China | Unknown | None | |
| TD | June 28-29 | Tropical depression | Not specified | 1004 hPa (29.65 inHg) | Ryukyu Islands | $450,000 | None | |
| Nanmadol | July 3-6 | Tropical storm | 85 km/h (50 mph) | 986 hPa (29.12 inHg) | South China, Vietnam, Laos, Thailand, Myanmar | $37.2 million | 3 | |
| Talas | July 6-13 | Severe tropical storm | 100 km/h (65 mph) | 985 hPa (29.09 inHg) | Japan, Aleutian Islands, Alaska | None | None | |
| Hodu (Caloy) | July 12-19 | Very strong typhoon | 175 km/h (110 mph) | 933 hPa (27.55 inHg) | Philippines, Taiwan, Hong Kong, Macau, South China, East China | $7.301 billion | 41 | |
| Kulap | July 22-30 | Severe tropical storm | 110 km/h (70 mph) | 972 hPa (28.70 inHg) | Japan, Russian Far East | $10.1 million | 9 | |
| TD | July 23-28 | Tropical depression | Not specified | 998 hPa (29.47 inHg) | None | None | None | |
| TD | July 24-25 | Tropical depression | Not specified | 1008 hPa (29.77 inHg) | None | None | None | |
| Wali | July 29-30 | Tropical depression | 55 km/h (35 mph) | 1002 hPa (29.59 inHg) | None | None | None | |
| Roke (Domeng) | August 5-10 | Typhoon | 150 km/h (90 mph) | 949 hPa (28.02 inHg) | Taiwan, Ryukyu Islands, East China, South China | $4.69 billion | 34 | |
| Nesat (Ester) | August 9-18 | Severe tropical storm | 110 km/h (70 mph) | 978 hPa (28.88 inHg) | Palau, Philippines, South China, Hong Kong, Macau, Vietnam, Laos | $40.07 million | 9 | |
| Sonca | August 9-13 | Severe tropical storm | 95 km/h (60 mph) | 984 hPa (29.06 inHg) | Mariana Islands, Bonin Islands, Japan, Russian Far East | $6.3 million | None | |
| Haitang (Francisco) | August 13-20 | Typhoon | 150 km/h (90 mph) | 953 hPa (28.14 inHg) | Philippines, South China, Hong Kong, Macau, Vietnam | $311.7 million | 58 | |
| Jamjari (Gardo) | August 13-27 | Violent typhoon | 195 km/h (120 mph) | 909 hPa (26.84 inHg) | Mariana Islands, Ryukyu Islands, Northeastern China, South Korea, North Korea, Japan, Alasaka | $6.289 billion | 142 | |
| Banyan | August 21-25 | Tropical storm | 65 km/h (40 mph) | 1001 hPa (29.56 inHg) | South China, Hong Kong, Macau, Taiwan, Ryukyu Islands | $65.5 million | 2 | |
| Yamaneko | August 26-30 | Tropical storm | 75 km/h (45 mph) | 995 hPa (29.38 inHg) | Russian Far East, Aleutian Islands | None | None | |
| TD | August 26-29 | Tropical depression | Not specified | 1008 hPa (29.77 inHg) | Philippines, Vietnam, Laos | $890,000 | 1 | |
| Pakhar | August 28 - September 3 | Tropical storm | 85 km/h (50 mph) | 992 hPa (29.29 inHg) | Japan, Russian Far East | $143.9 million | 8 | |
| TD | August 31 - September 6 | Tropical depression | Not specified | 1000 hPa (29.53 inHg) | Caroline Islands, Mariana Islands | Unknown | None | |
| Sanvu | September 1-8 | Severe tropical storm | 100 km/h (65 mph) | 986 hPa (29.12 inHg) | Caroline Islands, Mariana Islands, Japan | $9 million | None | |
| Mawar (Henry) | September 6-12 | Typhoon | 130 km/h (80 mph) | 967 hPa (28.56 inHg) | Philippines, Taiwan, Hong Kong, Macau, South China, Vietnam, Laos, Thailand, Myanmar | $86.85 million | 7 | |
| Inday | September 7-11 | Tropical depression | Not specified | 1004 hPa (29.65 inHg) | Philippines | $1.95 million | 1 | |
| TD | September 11-12 | Tropical depression | Not specified | 1002 hPa (29.59 inHg) | Ryukyu Islands | None | None | |
| TD | September 12-12 | Tropical depression | Not specified | 1006 hPa (29.71 inHg) | None | None | None | |
| Guchol (Josie) | September 14-23 | Very strong typhoon | 175 km/h (110 mph) | 927 hPa (27.37 inHg) | Ryukyu Islands, Taiwan, East China, Japan | $661.6 million | 2 | |
| Haebaragi (Luis) | September 29 - October 9 | Severe tropical storm | 110 km/h (70 mph) | 970 hPa (28.64 inHg) | Ryukyu Islands, Japan, South Korea, Russian Far East | $3.302 billion | 13 | |
| Talim (Kiyapo) | September 30 - October 10 | Very strong typhoon | 155 km/h (100 mph) | 945 hPa (27.91 inHg) | Ryukyu Islands, Japan, South Korea, North Korea, Northeastern China, Russian Far East | $904.6 million | 51 | |
| Khanun (Maymay) | October 11-18 | Typhoon | 140 km/h (85 mph) | 946 hPa (27.94 inHg) | Philippines, Taiwan, South China, Vietnam, Laos | $3.617 billion | 23 | |
| TD | October 12-13 | Tropical depression | Not specified | 1004 hPa (29.65 inHg) | Vietnam, Southwest China | Unknown | None | |
| Lan | October 12-18 | Tropical storm | 75 km/h (45 mph) | 996 hPa (29.41 inHg) | Vietnam, Laos, Cambodia, Thailand, Myanmar | $77.5 million | 14 | |
| Trau (Neneng) | October 15-30 | Very strong typhoon | 185 km/h (115 mph) | 925 hPa (27.32 inHg) | None | None | None | |
| Damrey (Obet) | October 22-25 | Tropical storm | 65 km/h (40 mph) | 1000 hPa (29.53 inHg) | None | None | None | |
| Shuixian (Pilandok) | October 23 - November 4 | Violent typhoon | 220 km/h (140 mph) | 877 hPa (25.90 inHg) | Philippines, Taiwan, Hong Kong, Macau, South China, Ryukyu Islands | $22.576 billion | 175 | |
| TD | October 27-28 | Tropical depression | Not specified | 1002 hPa (29.59 inHg) | None | None | None | |
| Kirogi | November 2-8 | Violent typhoon | 195 km/h (120 mph) | 898 hPa (26.52 inHg) | None | None | None | |
| Yun-yeung | November 7-11 | Typhoon | 140 km/h (85 mph) | 959 hPa (28.32 inHg) | None | None | None | |
| TD | November 19-22 | Tropical depression | Not specified | 1004 hPa (29.65 inHg) | Vietnam, Cambodia | $2.3 million | None | |
| 27W (Queenie) | November 21-26 | Tropical depression | 55 km/h (35 mph) | 1003 hPa (29.62 inHg) | Philippines, Malaysia | $8.5 million | 6 | |
| TD | November 21-28 | Tropical depression | Not specified | 1000 hPa (29.53 inHg) | Caroline Islands, Mariana Islands | None | None | |
| Koinu (Rosal) | November 30 - December 6 | Tropical storm | 85 km/h (50 mph) | 994 hPa (29.35 inHg) | Philippines | $41.6 million | 19 | |
| Bolaven (Samuel) | December 5-17 | Tropical storm | 75 km/h (45 mph) | 1000 hPa (29.53 inHg) | Philippines, Vietnam, Malaysia | $321.9 million | 54 | |
| TD | December 7-8 | Tropical depression | Not specified | 1010 hPa (29.83 inHg) | Palau | Unknown | None | |
| Sanba (Tomas) | December 21-31 | Very strong typhoon | 185 km/h (115 mph) | 920 hPa (27.17 inHg) | Caroline Islands, Palau, Philippines, Vietnam | $5.065 billion | 307 | |
| Season aggregates | ||||||||
| 45 systems | April 7 – December 31 | 220 km/h (140 mph) | 877 hPa (25.90 inHg) | $55.66 billion | 983 | |||