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.
The 2067 Pacific typhoon season was an extremely active, destructive, and deadly season. The season saw 33 tropical storms, one of the highest in record. In addition, the season featured the fourth-highest accumulated cyclone energy (ACE) index in history, only behind 2065, 1997 and 2046. The season is also the deadliest season since 2051, mostly due to Tropical Storm Danas. The season runs throughout 2067, though most tropical cyclones typically develop between May and October. The season's first named storm, Jelawat, developed on January 4. In May, the season's first typhoon, Gaemi, reached typhoon status on May 12, and became the first super typhoon of the year 2 days later. In mid June, after making landfall on the Philippines, Wukong restrengthened over the South China Sea and severely affected the Chinese provinces of Hainan and Yunan, causing 41 deaths in China. By August, Pulasan regenerated after moving over the Gulf of Tonkin and became a severe rain threat to Southeast Asia due to its slow forward speed, resulting in over 100 deaths among the Southeast Asian countries. Two months later, in early October, after becoming the most intense storm of the season, Typhoon Durumi made landfall at Wakayama Prefecture as a large Category 3-equivalent typhoon, causing extensive damages worth over $70 billion. This made the typhoon, at that time, the fourth-costliest Pacific typhoon on record, unadjusted for inflation. In December, Danas claimed the lives of over 2,700 people in the Philippines due to extensive flooding caused by extreme rainfall and lahars formed by the mixing of rain water with volcanic ash from the eruption of Mount Ragang. This made Danas the deadliest storm in the basin since 2051's Typhoon Nuri. The season's last named storm, Nari, dissipated on December 18.
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 (1967–2066) | 25.7 | 15.9 | 8.9 | 295 |
| May 5, 2067 | 26 | 16 | 8 | 288 |
| July 7, 2067 | 28 | 18 | 10 | 336 |
| August 7, 2067 | 29 | 19 | 11 | 360 |
| Other forecasts Date |
Forecast Center |
Period | Systems | |
| January 15, 2067 | PAGASA | January — March | 1–3 tropical cyclones | |
| January 15, 2067 | PAGASA | April — June | 2–4 tropical cyclones | |
| June 27, 2067 | PAGASA | July — September | 6-10 tropical cyclones | |
| June 27, 2067 | PAGASA | October — December | 4-8 tropical cyclones | |
| Forecast Center |
Tropical cyclones |
Tropical storms |
Typhoons | |
| Actual activity: | JMA | 51 | 33 | 19 |
| Actual activity: | JTWC | 37 | 33 | 21 |
| Actual activity: | PAGASA | 23 | 20 | 13 |
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 of the year was released by PAGASA on January 15, within its seasonal climate outlook for the period January–June. The outlook noted that 1-3 tropical cyclones were expected between January and March, while 2-4 were expected to develop or enter the Philippine Area of Responsibility between April and June. Moreover, the agency predicts that while ENSO-neutral conditions may persist in the first half of the year, there is a 60% chance of a weak El Niño presence during the July to December period.
Tropical Storm Risk (TSR) released their first forecast on May 5, predicting 2067 would be an average season with 26 named storms, 16 typhoons and 8 intense typhoons. However, the agency raised their outlook to 28 named storms, 18 typhoons and 10 intense typhoons in their July 7 forecast, citing an active early season and increasing odds for a developing weak El Niño after September. On August 7, TSR released their final forecast for the season, and further raised their outlook to 29 named storms, 19 typhoons and 11 intense typhoons, and an ACE index of 360.
Season summary[]
JMA's seasonal timeline
JTWC's seasonal timeline
| Rank | Total damages | Season |
|---|---|---|
| 1 | ≥ $281.35 billion | 2062 |
| 2 | ≥ $269.60 billion | 2065 |
| 3 | ≥ $215.79 billion | 2059 |
| 4 | ≥ $173.80 billion | 2050 |
| 5 | ≥ $153.11 billion | 2064 |
| 6 | ≥ $128.53 billion | 2057 |
| 7 | ≥ $111.69 billion | 2048 |
| 8 | ≥ $105.95 billion | 2067 |
| 9 | ≥ $98.14 billion | 2051 |
| 10 | ≥ $92.22 billion | 2039 |
2067 was a significantly-above average season. It featured 51 tropical cyclones, 33 named storms, 19 that became typhoons and 8 became super typhoons. Throughout the year, there were at least 3,361 deaths from several storms, making the season the least deadly since 2051. $105.95 billion in damages were recorded throughout the season, making 2067 the eighth costliest Pacific typhoon season on record.
Early season activity[]
The season began on January 4, when a tropical depression formed near the Marshall Islands. The system eventually became the first named storm of the season as it was named Jelawat by the JMA on January 7. Jelawat peaked as a severe tropical storm before it dissipated on January 15. Two months later, Tropical Storm Tepwanu formed near Palau on March 12. The storm impacted the Visayas of the Philippines, bringing moderate damages to the country.
April saw two systems forming, both originated from a westerly wind burst (WWB) that occurred over the open Pacific Ocean early in the month. The tropical disturbance to the west over the Philippine Sea became Tropical Depression 03W on April 8. 03W did not affect any landmasses before its dissipation over the open ocean on April 12. Meanwhile, the disturbance to the east formed near the Marshall Islands on April 9. The system failed to develop in the first few days, until it eventually became Severe Tropical Storm Maliksi by April 17. Maliksi recurved to the north near the Northern Mariana Islands, and its storm surge drowned two fishermen in Rota. The system dissipated on April 22.
Gaemi on May 13, after leaving Guam.
May produced four systems, at which three were named storms. The month started with Typhoon Gaemi forming on May 9 near the Caroline Islands. The storm eventually strengthened to a typhoon by May 12 and peaked as a Category 4-equivalent super typhoon on May 14. This made it the first typhoon and super typhoon of the season. Gaemi approached Guam and the Northern Mariana Islands on May 12 as a Category 1-equivalent typhoon, bringing US$ 142 million of damages and causing 4 fatalities there. Gaemi turned extratropical on May 18 and was absorbed by another extratropical cyclone on the next day, off the coast of Kamchatka Peninsula. On May 15, when Gaemi entered an eyewall replacement cycle after its peak, Typhoon Prapiroon formed in the Philippine Sea. Prapiroon peaked as a Category 1-equivalent typhoon on May 18, and it made landfall over Baler, Aurora at 05:00 UTC on May 20. Prapiroon killed 10 in the Philippines and brought significant damages to the nation, before it dissipated on May 23 over the South China Sea. On May 26, a tropical depression formed over the Philippine Sea. The system recurved and did not bring any major impacts to land. Tropical Storm Maria formed on May 29 over the South China Sea. It made landfall over Guangdong on May 30, causing minimal damages.
Ampil on June 17, after making landfall over Japan
June saw five systems forming, at which three were named storms. Severe Tropical Storm Son-Tinh formed on June 4 and passed near the southern tip of Taiwan on June 7. The storm made landfall over Zhangzhou, Fujian, at 06:00 UTC on June 8, killing four and causing CN¥1.251 billion (US$176 million) of economic losses across China. Ampil formed on June 7 to the east of Mindanao. The system recurved and became a Category 1-equivalent typhoon according to the JTWC on June 13, but the JMA never upgraded it to a typhoon. Ampil made direct landfall over the northern tip of Okinawa Island on early June 14, before it approached Honshu. and made its second landfall over Aichi Prefecture two days later. Ampil dissipated on June 18 over Shimane Prefecture. On June 10, a tropical depression formed near the Caroline Islands. It dissipated without causing any major impacts. On June 16, a low-pressure area formed east of Palau. It eventually became the precursor depression of Typhoon Wukong a day later. Wukong made its first landfall over the northern tip of Catanduanes, on June 21, as a Category 2-equivalent typhoon. It then made its second landfall on Real, Quezon, Quezon later on the same day. Wukong passed directly above Manila early in the morning on June 22, and it emerged over the South China Sea. On June 23, favourable conditions over the South China Sea allowed Wukong to reach its second peak as a Category 2-equivalent typhoon just before its landfall over Hainan, China on June 24, at 01:30 UTC. The system made its final landfall over Nam Định province, Vietnam at 18:45 UTC on the same day, before it dissipated on June 26 over Yunan. Wukong caused significant impacts to the Philippines, China and Vietnam, killing at least 57 people and causing US$ 7.3966 billion of damages. Tropical Depression Gavino formed on June 30, before it made its landfall over Surigao del Sur, Mindanao on July 3. The system dissipated on July 4 without causing major impacts.
.png){kind=link}
Jongdari to the east of Jeju, approaching South Korea, on July 15
July was an active month, with eight systems forming, at which five were named storms. The month started with a minor subtropical depression that developed over the East China Sea on July 1. The system performed a loop over the ocean before it transitioned into a tropical invest according to the JTWC by late July 2. It did not affect any landmasses before it dissipated on the next day. On July 3, a tropical disturbance developed in a monsoon trough, located 280 km (174 mi) to the north-northwest of Pohnpei. The disturbance eventually became Typhoon Jongdari, which peaked as a Category 4-equivalent on July 11 over the Philippine Sea. The typhoon recurved and made landfall over Yeosu, South Korea on July 15, and it transitioned into an extratropical cyclone a day later. The typhoon resulted in 30 fatalities and US$ 4.51 billion of damages, at which 25 deaths and US$ 4.28 billion of damages were recorded in South Korea. Tropical Storm Shanshan originated from a broad tropical disturbance on July 13, located to the east of Aurora, the Philippines. On July 15, Shanshan crossed the Luzon Strait and entered the South China Sea as a tropical depression, before it consolidated into a tropical storm on the following day. From July 18 to 19, Shanshan made landfalls over Hainan and Vietnam, before it dissipated on July 20 over Yunnan. On July 19, two tropical depressions formed over the Pacific Ocean, one near Guam, and another to the east of Japan. Both did not affect land before dissipating. Severe Tropical Storm Sasori developed on July 20, and it recurved to the northeast on July 26, turning extratropical two days later. Meanwhile, a tropical disturbance crossed the International Date Line and entered the basin from the Central Pacific on July 21. It became the precursor depression of Typhoon Leepi on July 23. After failing to develop significantly for a few days, the storm managed to attain typhoon status by July 28. On the next day, Leepi passed through the Northern Mariana Islands as a strong Category 1-equivalent typhoon. On July 30, Leepi peaked as a Category 4-equivalent super typhoon over the open ocean, and it recurved offshore from the south of Japan by August 1. The system passed between the Izu Islands and Bonin Islands on August 4, and it turned extratropical three days later. Typhoon Bebinca formed on July 24. After peaking as a Category 2-equivalent typhoon on July 28, the typhoon made landfall over Taiwan and Zhejiang, China on the next day. It then passed through the Chinese provinces of Jiangsu and Shandong as a tropical storm, and through North Korea as an extratropical remnant, brining severe impacts to these places. Total economic losses in Taiwan reached NT$70.51 billion, and 13 deaths were recorded in North Korea.
Peak season activity[]
.jpg){kind=link}
Lamyai making landfall over northern Vietnam on September 7
August was the most active month of the season, and was slightly more active than July. The month saw nine systems forming, at which six were named storms. Tropical Storm Pulasan formed over the South China Sea on August 1. The storm moved slowly and brushed the coasts of Southern China. It temporarily weakened to a remnant low on August 12 after its landfall over Vietnam. However, when it moved over the Gulf of Tonkin on August 14, it managed to regenerate and attain a new peak. Pulasan made its final landfall over Guangxi, China, and dissipated on August 17 over the same province. Pulasan became the second-deadliest storm of the season, killing 174 people, mostly in Vietnam and Loas. On August 4, Tropical Depression Henriette from the Eastern Pacific entered the basin. After two near-dissipation and regenerations due to high vertical wind shear, the system managed to peak as a Category 4-equivalent typhoon on August 18. The typhoon then moved northwards and moved along the Korea Strait to enter the Sea of Japan. The system transitioned into an extratropical cyclone on August 27, ending its 39-day-long life as the longest-living tropical cyclone ever recorded. Severe Tropical Storm Soulik originated as a tropical disturbance near the Wake Island on August 2. It became a tropical depression on August 7 and moved northwards to the east of Japan before undergoing extratropical transition on August 11. Tropical Depression 18W formed over the open Pacific Ocean on August 7 and made landfall over Kamo District, Shizuoka on August 10. It then interacted with Soulik and was absorbed by the latter on the next day. On August 13, a tropical depression formed near the Marshall Islands. It dissipated on August 17 without affecting any major landmasses. On August 14, a broad area of low pressure developed inside an eastward-extended monsoon trough in the Central Pacific. The disturbance crossed into the basin on August 16 and was named Cimaron on the next day. Cimaron steadily intensified into a typhoon before stalling in intensity as a Category 2-equivalent typhoon from August 19 to 22. The typhoon then managed to enter a phase of rapid intensification due to the decrease of vertical wind shear. It attained its peak as a Category 4-equivalent super typhoon on August 23, before starting a round of eyewall replacement cycle. Cimaron then slowly weakened over the next few days, and it made landfall over Higashiusuki, Miyazaki on August 30. Cimaron dissipated over the Sea of Japan on September 1. On August 18, Tropical Depression 20W formed over the area of the Pacific Ocean to the east of Japan. It then recurved and transitioned into an extratropical cyclone three days later without affecting land. On August 23, the precursor disturbance of Typhoon Horangi formed to the east of the International Date Line. The disturbance crossed the date line on August 24 and was named Horangi by the JMA on August 27. Horangi rapidly intensified on August 30, and it became a Category 5-equivalent super typhoon on September 1, the first of the season. Horangi then slowly weakened as it continued to travel north-northeastward for the next few days. The system transitioned into an extratropical cyclone on September 10. On August 25, the precursor disturbance of Typhoon Lamyai formed within a monsoon trough, located near Kosrae, in the Federated States of Micronesia. Lamyai moved northwestward and gradually intensified into a Category 2-equivalent typhoon before its landfall over General Nakar, Quezon, Luzon on September 4. Lamyai weakened after its Luzon landfall, and it managed to restrengthen over the South China Sea to attain a new, higher peak as a Category 3-equivelent typhoon on September 6. Lamyai then entered the Gulf of Tonkin and made landfall over Quỳnh Lưu, Nghệ An, Vietnam as a Category 2-equivalent typhoon on September 7. Lamyai rapidly weakened after that, and the system dissipated over Myanmar on September 9. Lamyai brought severe impacts to the Philippines and Vietnam. 21 people lost their lives in the Philippines, where economic damages amassed to ₱1.97 billion (US$33.7 million). Meanwhile, in Vietnam, 25 people were killed and 186 were injured. Damage in the nation was estimated at 1.63 trillion VND (US$62 million).
Late season activity[]
Accumulated cyclone energy (ACE)[]
| Rank | Seasons | ACE value |
|---|---|---|
| 1 | 2065 | 753.1 |
| 2 | 1997 | 570.4 |
| 3 | 2046 | 522.5 |
| 4 | 2067 | 498.4 |
| 5 | 2004 | 480.6 |
| 6 | 1992 | 470.1 |
| 7 | 2061 | 467.9 |
| 8 | 2015 | 462.9 |
| 9 | 2040 | 455.2 |
| 10 | 1994 | 454.6 |
| 11 | 2038 | 451.3 |
| 12 | 2059 | 446.0 |
.png){kind=link}
ACE Progression of the 2067 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 1967-2066 is 295, while an ACE above 335, between 246 to 335 and below 246 is defined as "above-average", "near-normal", and "below-average" respectively. The cumulative ACE for the Western Pacific in 2067 fell into the "above-average" category. This also marked 2067 to be the first of the three consecutive above-average seasons in terms of ACE from 2067 to 2069. This season's above-average activity was driven by an ENSO index that ranged from a warm-neutral to a weak El Niño, as well as a persistent positive Pacific decadal oscillation.
The single storm which had the highest ACE was Typhoon Wutip (Sarah), which in total accumulated 50.9875 ACE points in its lifetime. It is followed by Typhoon Cimaron and Typhoon Barijat (Marilyn), which accumulated 44.585 and 42.1575 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 | Wutip (Sarah) | 50.9875 | 18 | Prapiroon (Chedeng) | 7.3075 | |
| 2 | Cimaron | 44.585 | 19 | Kujaku (Quiel) | 6.525 | |
| 3 | Barijat (Marilyn) | 42.1575 | 20 | Yinxing (Nimfa) | 6.415 | |
| 4 | Henriette (Kabayan) | 39.9725 | 21 | Pulasan | 5.2425 | |
| 5 | Horangi | 37.6975 | 22 | Fo-lung (Onyok) | 5.175 | |
| 6 | Durumi (Perla) | 32.7175 | 23 | Jelawat | 5.0875 | |
| 7 | Leepi | 32.4425 | 24 | Sepat (Tamaraw) | 4.4725 | |
| 8 | Jongdari (Hanna) | 26.73 | 25 | Sasori | 3.5525 | |
| 9 | Nari (Weng) | 24.445 | 26 | Danas (Ugong) | 3.39 | |
| 10 | Gaemi | 21.795 | 27 | Son-Tinh (Dodong) | 3.1975 | |
| 11 | Lamyai (Liwayway) | 17.5925 | 28 | Lang-biang | 2.3 | |
| 12 | Romduol | 16.8175 | 29 | Soulik | 2.295 | |
| 13 | Pabuk (Ramon) | 13.0625 | 30 | Shanshan (Ineng) | 1.78 | |
| 14 | Wukong (Falcon) | 11.7825 | 31 | Maliksi | 1.2825 | |
| 15 | Mun | 9.6925 | 32 | Tepwanu (Amang) | 0.565 | |
| 16 | Bebinca (Jenny) | 8.64 | 33 | 18W# | 0.4425 | |
| 17 | Ampil (Emil) | 8.235 | 34 | Maria* | 0 | |
| Sum | 498.3825 | |||||
| #Recognised by the JTWC as a tropical storm but not the JMA.
*Recognised by the JMA as a tropical storm but not the JTWC. | ||||||
Systems[]
Severe Tropical Storm Jelawat[]
| Max 1-min winds: | 55 kt (100 km/h) |
|---|---|
| Max 10-min winds: | 50 kt (95 km/h) |
| Min pressure: | 985 hPa (mbar) |
| ACE accumulated | 5.0875 |
| TD+ days | 10.5 days |
| TS+ days | 6.25 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 | January 4 – January 15 |
| Peak intensity | 95 km/h (60 mph) (10-min); 985 hPa (mbar) |
On January 1, the JTWC started tracking a tropical disturbance that formed at 160 km (99 mi) to the east-northeast of Makin Island, Kiribati. The disturbance remained disorganised for the first few days and moved erratically due to the lack of steering currents. However, the system's convection became more centralised and better organised on January 3 due to the lessening of wind shear. This caused the JMA to upgrade the system from a low-pressure area to a tropical depression on the same day. The JTWC then issued a Tropical Cyclone Formation Alert (TCFA) on the system a few hours later. By 18:00 UTC on January 4, the JTWC designated the system as Tropical Depression 01W, making it the first tropical cyclone of the season according to the agency. O1W then slowly strengthened, and it was upgraded to a tropical storm by the JTWC on January 7, at 00:00 UTC. The JMA then followed suit and also upgraded 01W to a tropical storm 12 hours later, and named it Jelawat. Guided by a subtropical ridge, Jelawat started to steadily move towards the northwest after January 8. By early January 9, the JMA further upgraded Jelawat to a severe tropical storm as the system continued to strengthen. Jelawat reached its peak intensity at 18:00 UTC on the same day according to the JTWC, reaching maximum 1-minute sustained winds of 100 km/h (65 mph) and a minimum central pressure of 985 mbar (29.09 inHg). After that, the system slowly weakened due to increased wind shear and dry air intrusion. The JMA downgraded Jelawat to a tropical storm on January 11, then the agency further downgraded the system to a tropical depression 2 days later. Meanwhile, the JTWC issued its last warning on the system on January 14. The JMA continued to track the storm till January 15, before the system dissipated at 1,140 km (708 mi) to the east of Hagåtña, Guam.
Notable stats: None.
Tropical Storm Tepwanu (Amang)[]
| Max 1-min winds: | 40 kt (75 km/h) |
|---|---|
| Max 10-min winds: | 40 kt (75 km/h) |
| Min pressure: | 994 hPa (mbar) |
| ACE accumulated | 0.565 |
| TD+ days | 6 days |
| TS+ days | 1 day |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | None |
| Damages | $2.12 million (USD) |
| Tropical storm (JMA) | |
|---|---|
| Tropical storm (SSHWS) | |
  | |
| Duration | March 12 – March 18 |
| Peak intensity | 75 km/h (45 mph) (10-min); 994 hPa (mbar) |
The JMA noted a tropical depression has formed on March 11, located 210 km (130 mi) to the west-southwest of Angaur, Palau. Meanwhile, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) hours later. At 18:00 UTC on the same day, the PAGASA recognised the system as a tropical depression inside the Philippine Area of Responsibility. This prompted the agency to give the system the local name Amang. Six hours later, at 00:00 UTC on March 12, the JTWC upgraded Amang from a tropical disturbance to a tropical depression, hence designating it as 02W. 02W moved northwestwards towards the Philippines for the next day. At 18:00 UTC on March 12, when the system was located to the west of Surigao del Norte, Mindanao, the JMA upgraded 02W to a tropical storm and named it Tepwanu. The JTWC also upgraded Tepwanu to a tropical storm 12 hours later. The system failed to strengthen much after this, and it made its first landfall over Siargao Island on March 13, at 14:00 UTC, as a minimal tropical storm. Tepwanu then made its second landfall over Dinagat Island two hours later. Over the next day, the storm made multiple more landfall as it crossed the Visayas. Land interaction caused Tepwanu to weaken in the process, and the JMA downgraded the system to a tropical depression on March 14. Tepwanu entered the South China Sea by early March 15. Over the next two days, northeast monsoon brought significant dry air and wind shear to Tepwanu, which caused the storm to further weaken and move southwestward. The JTWC issued its final warning on Tepwanu on March 17, while the JMA continued to track the system till it dissipated a day later over the South China Sea.
Tepwanu brought significant rainfall to southern Philippines from March 13 to 15, which inundated roads, farmlands, and damaged infrastructure. ₱121 million (US$2.12 million) in total damages were recorded in the Philippines, mostly due to agricultural losses.
Notable stats: None.
Tropical Depression 03W (Betty)[]
| Max 1-min winds: | 30 kt (55 km/h) |
|---|---|
| Max 10-min winds: | 30 kt (55 km/h) |
| Min pressure: | 1002 hPa (mbar) |
| ACE accumulated | 0 |
| TD+ days | 3.5 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 depression (JMA) | |
|---|---|
| Tropical depression (SSHWS) | |
  | |
| Duration | April 8 – April 12 |
| Peak intensity | 55 km/h (35 mph) (10-min); 1002 hPa (mbar) |
By early April, a westerly wind burst (WWB) occurred over the open Pacific Ocean. The WWB spawned two tropical disturbances in the Northern Hemisphere. The western tropical disturbance located over the Philippine Sea developed on April 6 at 430 km (267 mi) to the east of Siargao Island, Surigao del Norte. The disturbance's convection slowly deepened and the system's structure began to consolidate. By April 7, the the JMA upgraded the system to a tropical depression. At around the same time, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system, noting on the elongated but developing centre of the storm. At 18:00 UTC on the same day, the PAGASA recognised the system as a tropical depression, and named it Betty. On April 8, at 12:00 UTC, the JTWC also upgraded the system to a tropical depression, and designated it 03W. 03W slowly moved northwards, and entered an area with unfavourable wind shear by April 10. This caused the 03W's centre to become partially exposed, and the system deteriorated. The JTWC issued its final advisory on 03W at 18:00 UTC on April 10, while both the JMA and PAGASA still tracked the system until April 12.
Notable stats: None.
Severe Tropical Storm Maliksi[]
| Max 1-min winds: | 55 kt (100 km/h) |
|---|---|
| Max 10-min winds: | 55 kt (100 km/h) |
| Min pressure: | 981 hPa (mbar) |
| ACE accumulated | 1.2825 |
| TD+ days | 6.25 days |
| TS+ days | 1.75 days |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 2 |
| Damages | $800,000 (USD) |
| Severe tropical storm (JMA) | |
|---|---|
| Tropical storm (SSHWS) | |
  | |
| Duration | April 14 – April 22 |
| Peak intensity | 100 km/h (60 mph) (10-min); 981 hPa (mbar) |
On April 9, the JTWC identified an area of convection located. The system was spawned from a westerly wind burst in early April. Environmental analysis indicated favourable conditions for tropical cyclogenesis, including low vertical wind shear, improved equatorward outflow, and warm sea surface temperatures. The JMA began issuing advisories the following day, classifying the disturbance as a tropical depression. On April 10, at 19:30 UTC, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system, citing a high chance of further development. The disturbance moved northwestwards, and encountered a significant mass of dry air to its north by April 11, which caused its convection to wane. The JTWC noted on a worsening environment for the system, and cancelled its TCFA by 11:00 UTC on the same day. An hour later, the JMA downgraded the system back to a low-pressure area. By April 13, as the system managed to escape the dry air and enter an area with more favourable conditions, its convection deepened again and its poleward outflow improved. The caused the JTWC to reissue a TCFA on the system on the same day. Meanwhile, the JMA also re-upgrade the system to a tropical depression. On April 14, at 18:00 UTC, the JTWC upgraded the storm to Tropical Depression 04W. The agency then further upgraded 04W to a tropical storm on April 17, at 12:00 UTC, as satellite imagery showed improved convective banding wrapped around the storm's compact LLCC. The JMA followed suit six hours later and also upgraded 04W to a tropical storm, and named it Maliksi. After passing to the south of Guam, Maliksi started to recurve towards the north-northeast. The environment surrounding the storm further improved, and this enabled Maliksi to rapidly intensify on April 18. The storm reached its peak intensity at 12:00 UTC that day, with maximum 1-minute sustained winds of 100 km/h (65 mph) and a minimum central pressure of 981 mbar (28.97 inHg). Shortly after this peak, Maliksi encountered strong easterly flow and high wind shear of 35–45 km/h (20–25 knots) from the northeast. This quickly displaced the storm's convection and weakened the system. By early April 19, both the JTWC and the JMA downgraded Maliksi to a tropical depression. The JTWC issued its final advisory on the system on April 20, at 06:00 UTC, while the JTWC continued tracking the system till it dissipated by late April 22.
Notable stats: None.
Typhoon Gaemi[]
| Max 1-min winds: | 130 kt (240 km/h) |
|---|---|
| Max 10-min winds: | 100 kt (185 km/h) |
| Min pressure: | 923 hPa (mbar) |
| ACE accumulated | 21.795 |
| TD+ days | 9 days |
| TS+ days | 7.5 days |
| C1+ days | 5.25 days |
| C3+ days | 2.25 days |
| SuperTY days | 0.5 days |
| C5 days | N/A |
| Fatalities | 4 |
| Damages | $151 million (USD) |
| Very Strong Typhoon (JMA) | |
|---|---|
| Category 4 super typhoon (SSHWS) | |
  | |
| Duration | May 9 – May 18 (Extratropical) |
| Peak intensity | 185 km/h (115 mph) (10-min); 923 hPa (mbar) |
On May 7, a tropical disturbance formed 630 km (391 mi) to the north-northeast of Pohnpei of the Federated States of Micronesia. The disturbance moved steadily west-northwest as it was located at the southern periphery of a subtropical ridge. The system managed to quickly construct its low-level circulation centre (LLCC) as it was embedded in an environment conducive for tropical cyclone genesis. As a result, by late May 7, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system. On the next day, at 02:00 UTC, the JMA upgraded the system to a tropical depression, while the JTWC followed suit at 12:00 UTC on the same day. The JTWC hence designated the system as 05W. By early May 11, as the deep convection in the central dense overcast (CDO) of 05W completely obscured its LLCC, both the JMA and the JTWC upgraded the system to a tropical storm, with JMA naming the storm Gaemi. Gaemi continued to move westward towards Guam and the Northern Mariana Islands. During this time, low vertical wind shear and warm sea surface temperatures helped the system to attain severe tropical status by early May 12 according to the JMA. At 12:00 UTC on the same day, the JTWC upgraded Gaemi to a typhoon, while the JMA followed suit six hours later. At 18:30 UTC, Gaemi passed only 10 km (6 mi) to the northern tip of Guam as a Category 1-equivalent typhoon, with maximum 1-minute sustained winds of 130 km/h (80 mph). After moving away from Guam, Gaemi's equatorward outflow further improved, with good poleward outflow aloft. This allowed the typhoon to rapidly intensify on May 13. The JTWC upgraded Gaemi to a super typhoon by May 14, at 06:00 UTC, making the system the first super typhoon of the season. Gaemi attained its peak six hours later, with maximum 1-minute sustained winds of 240 km/h (150 mph) and a minimum central pressure of 923 mbar (27.26 inHg). After this, Gaemi entered an eyewall replacement cycle and started to weaken. By May 15, Gaemi started to recurve towards the northeast due to a trough to its northeast. The lower sea surface temperatures and increased wind shear caused Gaemi to further weaken over the next few days. The JMA downgraded Gaemi to a severe tropical storm on May 17. On the next day, Gaemi began its extratropical transition while it was 1,960 km (1,217 mi) to the east of Tokyo, Japan. At around the same time, the JTWC issued its final warning on the system. However, the JMA continued tracking the extratropical remnants of Gaemi, until it was absorbed by another extratropical cyclone on May 19, off the coast of Kamchatka Peninsula.
Gaemi brought severe winds and significant rainfall for Guam and the Northern Mariana Islands. In Guam, from May 12 to 13, Gaemi dropped torrential rainfall that exceeded 400 mm (15.75 in) over multiple spots on the island. Meanwhile, at the Guam International Airport, gusts up to 108 miles per hour (174 km/h) were recorded. Strong winds and severe flooding had caused 513 houses to be damaged. The lost of electricity and damages to the road system were also recorded. Overall, damages totalled US$23 million, 4 people were injured and 1 was dead in the island nation. On neighboring Rota, Gaemi damaged 139 houses and destroyed 15, causing an additional $119 million in damage and 3 fatalities.
Notable stats: Gaemi was the first super typhoon of the season.
Typhoon Prapiroon (Chedeng)[]
| 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 | 7.3075 |
| TD+ days | 7 days |
| TS+ days | 5 days |
| C1+ days | 2.5 days |
| C3+ days | N/A days |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 11 |
| Damages | $60.38 million (USD) |
| Typhoon (JMA) | |
|---|---|
| Category 1 typhoon (SSHWS) | |
  | |
| Duration | May 15 – May 23 |
| Peak intensity | 130 km/h (80 mph) (10-min); 967 hPa (mbar) |
On May 13, at 06:00 UTC, the JMA reported that a low-pressure area had formed 80 km (50 mi) to the west of Peleliu, Palau. While the system was disorganised at first, it slowly tightened its circulation, and deep convection soon started to burst near its centre. As a result, the JMA upgraded the system to a tropical depression by the JMA on May 15, at 02:00 UTC. An hour later, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system. The agency then upgraded the system to a tropical depression and designated it as 06W at 12:00 UTC on the same day. At the same time, the PAGASA recognised the storm as a tropical depression inside its area of responsibility and namied it Chedeng. On May 16, at 12:00 UTC, the JMA upgraded 06W to a tropical storm and named it Prapiroon, while the JTWC followed suit six hours later. Over the Philippine Sea, favourable conditions such as low vertical wind shear and good equatorial outflow allowed Prapiroon to continue to strengthen. On May 17, at 12:00 UTC, Prapiroon was upgraded to a severe tropical storm by the JMA. 12 hours later, the JTWC upgraded system to a minimal typhoon. By May 18, Prapiroon made a drastic turn towards the southwest due to the unexpected strengthening of the subtropical ridge to the typhoon's north. On May 19, at 12:00 UTC, Prapiroon reached its peak intensity, with maximum 1-minute sustained winds of 150 km/h (90 mph) and a minimum central pressure of 967 mbar (28.56 inHg). After this peak, Prapiroon slowly weakened and moved towards Luzon. The typhoon made landfall over Baler, Aurora at 05:00 UTC on May 20 as a Category-1 equivalent typhoon. After that, the mountains over Luzon quickly weakened the storm, and the system entered the South China Sea as a tropical storm six hours after its landfall. As Prapiroon continued to move westward and became embedded in the low-level northeasterly flow associated with the northeast monsoon, its low-level circular convection weakened over the centre due to strong southerly vertical wind shear. As a result, both the JMA and the JTWC downgraded the storm to a tropical depression on May 21. During this time, satellite imagery later showed a weakening of deep convection at Prapiroon's centre, with low-level cloud banding visible around the center and along the southern edge of the circulation. As a result of convective decapitation that left the low-level circulation fully exposed, the JTWC issued its final advisory by early May 22. Meanwhile, the JMA continued monitoring the system until it was last noted at 06:00 UTC on May 23.
In the Philippines, Prapiroon and the southwest monsoon caused extensive flooding and wind damage, affecting over 23,000 people, with ₱3.51 billion (US$60.38 million) in damages, mostly concentrated in Luzon. According to the National Disaster Risk Reduction and Management Council (NDRRMC), at least 11 people died and 139,000 were displaced. The provinces of Aurora, Isabela, Quirino, Nueva Vizcaya and Nueva Ecija were the most affected by the storm. Across the country, 681 houses were damaged, 3 were destroyed, and 19 areas of Central Luzon reported flooding. At the same time, at least 185 cities and municipalities suspended classes, while 29 suspended work.
Meanwhile, in Hainan, China, a man drowned after Prapiroon's storm surge dragged him into the ocean.
Notable stats: None.
Tropical Storm Maria[]
| Max 1-min winds: | 30 kt (55 km/h) |
|---|---|
| Max 10-min winds: | 35 kt (65 km/h) |
| Min pressure: | 999 hPa (mbar) |
| ACE accumulated | 0 |
| TD+ days | 2 day |
| 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 storm (JMA) | |
|---|---|
| Tropical depression (SSHWS) | |
  | |
| Duration | May 29 – June 1 |
| Peak intensity | 65 km/h (40 mph) (10-min); 999 hPa (mbar) |
On May 27, the JMA noted on a low pressure area forming over the South China Sea, located 70 km (43 mi) to the northwest of Laoag, Ilocos Norte. The system steadily organised, and the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system at 15:30 UTC on May 28. Later on the same day, the JMA upgraded the storm to a tropical depression, noting on the deepening convection of the system and the formation of a clear low-level circulation centre (LLCC) on satellite. Meanwhile, the JTWC upgraded the system to a tropical storm on May 29, at 12:00 UTC, and designated it as 07W. On May 30, at 00:00 UTC, satellite imagery showed that despite having an exposed center, a weak banding feature began to develop around 07W. This prompted the JMA to upgrade the storm to a minimal tropical storm, and named it Maria. However, the JTWC kept the system a tropical depression. Maria then gradually approached the southern coasts of China. The storm made landfall at Dianbai, Maoming, Guangdong on May 30, at 18:00 UTC. Maria gradually weakened after that due to land interaction. The JMA downgraded the storm to a tropical depression by early May 31, while the JTWC issued its last warning on the system later on the same day. However, the JMA continued tracking the system till it dissipated near Ningde, Fujian on June 1.
Notable stats: Maria was the first and only storm this season that was recognised by the JMA as a tropical storm but not the JTWC.
Severe Tropical Storm Son-Tinh (Dodong)[]
| Max 1-min winds: | 60 kt (110 km/h) |
|---|---|
| Max 10-min winds: | 60 kt (110 km/h) |
| Min pressure: | 974 hPa (mbar) |
| ACE accumulated | 3.1975 |
| TD+ days | 4.75 days |
| TS+ days | 3.25 days |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 5 |
| Damages | $1.521 billion (USD) |
| Severe tropical storm (JMA) | |
|---|---|
| Tropical storm (SSHWS) | |
  | |
| Duration | June 4 – June 11 |
| Peak intensity | 110 km/h (70 mph) (10-min); 974 hPa (mbar) |
On May 29, at 18:00 UTC, the JTWC noted on a tropical disturbance developing at 250 km (155 mi) to the southwest of Chuuk Lagoon, Federated States of Micronesia. The disturbance steadily moved northwestward for the next few days, where marginal wind shear and poor high-level divergence prohibited the system from significantly developing. By June 2, at 00:00 UTC, as the disturbance entered the Philippine Area of Responsibility and was recognised as a tropical depression by PAGASA, the agency named the storm Dodong. A day later, wind shear over the system lessened, and the disturbance's deep convection completely covered its centre. This prompted the JMA to also upgrade the system to a tropical depression. On the same day, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the storm, and it assessed the probability for a significant tropical cyclone to form from the system in the next 24 hours was "high". The agency then upgraded the system to Tropical Depression 08W on June 4 at 18:00 UTC. When 08W reached the Luzon Strait, the JTWC further upgraded it to a tropical storm on June 5, at 12:00 UTC, while the JMA also did the same six hours later and named 08W Son-Tinh. Son-Tinh reached its peak as a severe tropical storm on June 7, at 06:00 UTC, with maximum 1-minute sustained winds of 110 km/h (70 mph) and a minimum central pressure of 974 mbar (28.76 inHg). Shortly after reaching its peak, Son-Tinh passed near the southern tip of Taiwan on later on the same day. The storm made landfall over Zhangpu County, Zhangzhou, Fujian, at 06:00 UTC on June 8. Son-Tinh weakened to a tropical depression later on the same day. The JTWC issued its last warning on the system on June 8, at 18:00 UTC, while the JMA continued tracking the storm's remnant until it dissipated near the Guangxi-Yunnan border on June 11.
In China, Son-Tinh left four people dead, two people missing, 139 injured, and displaced over 15,000 residents. A man in Longyan, Fujian, was killed after falling while repairing a storm-damaged roof. In Guangxi, heavy rainfall from the remnant of Son-Tinh caused over 600 recorded landslides in the province, with one of them near Dahua, Dahua Yao Autonomous County, burying three houses. Across China, Son-Tinh caused CN¥1.251 billion (US$176 million) of economic losses. In the Philippines, Son-Tinh and its associated southwest monsoon affected more than 20,000 people across the nation. Extensive flooding was recorded in Metro Manila.
Notable stats: None.
Severe Tropical Storm Ampil (Emil)[]
| Max 1-min winds: | 70 kt (130 km/h) |
|---|---|
| Max 10-min winds: | 60 kt (110 km/h) |
| Min pressure: | 973 hPa (mbar) |
| ACE accumulated | 8.235 |
| TD+ days | 10.25 days |
| TS+ days | 7.25 days |
| C1+ days | 2.25 days |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | None |
| Damages | $1.0996 billion (USD) |
| Severe tropical storm (JMA) | |
|---|---|
| Category 1 typhoon (SSHWS) | |
  | |
| Duration | June 7 – June 18 |
| Peak intensity | 110 km/h (70 mph) (10-min); 973 hPa (mbar) |
On June 4, the JMA noted a low-pressure area has formed 250 km (155 mi) to the southeast of Ifalik Atoll in the Federated States of Micronesia. The disturbance remained disorganised in the first two days, with its convection displaced to the southwest due to wind shear. However, on June 6, the system became more symmetrical due to the lessening of wind shear. This prompted the JMA to upgrade the system to a tropical depression that day. The system then moved northwest, and it passed within 6 km (4 mi) to the northern tip of Babeldaob, Palau on June 7, at 05:45 UTC. At around the same time, the PAGASA recognised the storm as a tropical depression, hence naming it Emil. At 07:00 UTC, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system. A few hour later, at 18:00 UTC, the JTWC upgraded the system to a tropical depression, and designated it as 09W. Over the next day, 09W took on a more north-northwesterly track due to a break in the subtropical ridge to the system's north. By June 9, at 11:00 UTC, the JMA upgraded 09W to a tropical storm, and named it Ampil. Meanwhile, the JTWC followed suit at 06:00 UTC on the next day. Over the next few days, Ampil gradually recurved as it passed by the east of the Philippines and Taiwan. On June 13, as Ampil entered a stretch of the ocean with high oceanic heat content (OHC), provided by the Kuroshio Current, and low wind shear, the JMA upgraded the system to a severe tropical storm early that day. The JTWC, on the other hand, upgraded Ampil to a typhoon at 18:00 UTC on the same day. However, the JMA never upgraded Ampil to a typhoon. On June 14, at 01:00 UTC, Ampil made landfall over Kunigami, Okinawa near peak intensity. After that, the storm continued moving towards the east. On June 15, at 18:00 UTC, Ampil lost its typhoon status according to the JTWC due to warning cloud tops driven by decreasing sea surface temperatures. After that, Ampil started to recurve towards the west and approached Honshu. On June 16, at 23:15 UTC, Ampil made a landfall over Tahara, Aichi Prefecture as a tropical storm. It then passed over Mikawa Bay, made a brief landfall on Minamichita, and entered the Ise Bay. Ampil made its next landfall over Tsu, Mie Prefecture at 04:00 UTC on June 17. The storm quickly weakened after that, and it was downgraded to a tropical depression by both the JMA and the JTWC later on the same day. Ampil dissipated by early June 18 over Shimane Prefecture.
Throughout its path, Ampil caused ¥162 billion (US$1.099 billion) of damages throughout Japan, with most concentrated in the Prefectures of Shizuoka, Aichi and Nagano. Throughout the country, a total of 330,000 people were forced to evacuate, and about 130 flights were cancelled.
Notable stats: None.
Typhoon Wukong (Falcon)[]
| Max 1-min winds: | 95 kt (175 km/h) |
|---|---|
| Max 10-min winds: | 85 kt (160 km/h) |
| Min pressure: | 954 hPa (mbar) |
| ACE accumulated | 11.7825 |
| TD+ days | 8.25 days |
| TS+ days | 6.5 days |
| C1+ days | 3.75 days |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 57 |
| Damages | $7.3966 billion (USD) |
| Very Strong Typhoon (JMA) | |
|---|---|
| Category 2 typhoon (SSHWS) | |
  | |
| Duration | June 17 – June 26 |
| Peak intensity | 160 km/h (100 mph) (10-min); 954 hPa (mbar) |
On June 16, the JMA noted on the formation of a tropical depression 340 km (211 mi) to the southeast of Yap. The system organised quickly, and the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system at 01:00 UTC On June 17. The agency then upgraded the storm to Tropical Depression 10W at 12:00 UTC on the same day. Six hours later, as the depression entered the Philippine Area of Responsibility, the PAGASA named it Falcon. Located in a favorable environment with warm 30 °C (86 °F) sea surface temperatures, low 10–15 knots (19–28 km/h; 12–17 mph) wind shear, and moderate outflow, the system's low-level circulation centre (LLCC) quickly consolidated and was obscured by deep convection. This prompted both the JMA and the JTWC to upgrade the system to a tropical storm by 18:00 UTC on June 18, with the former naming it Wukong. Wukong was upgraded to a severe tropical storm by the JMA on the next day, at 06:00 UTC. The JTWC then upgraded Wukong to a typhoon 12 hours later, with the JMA following suit by early June 20. At 18:00 UTC on the same day, Wukong attained its peak intensity, with maximum 1-minute sustained winds of 175 km/h (110 mph) and a minimum central pressure of 954 mbar (28.17 inHg). After that, the start of an eyewall replacement cycle and land interaction caused Wukong to slowly weaken. The typhoon made its first landfall over Pandan, at the northern tip of Catanduanes, on June 21, at 03:00 UTC, as a Category 2-equivalent typhoon. It then entered Lamon Bay a day later. Wukong made its second landfall on Real, Quezon, on June 21, at 22:00 UTC. At 01:30 UTC on the next day, Wukong passed directly above Manila, still as a Category 1-equivalent typhoon. It entered the Manila Bay 15 minutes later, and made its final landfall in the Philippines on Pilar, Bataan, at 04:00 UTC. At around the same time, the mountaineous terrain of Luzon caused Wukong to lose its typhoon status according to both the JMA and the JTWC, and it entered the South China Sea from Morong, Bataan, at 06:00 UTC. On June 23, favourable conditions over the South China Sea allowed Wukong to reattain typhoon status. The typhoon reached its second peak as a Category 2-equivalent typhoon just before its landfall over Hainan, China. Wukong made a landfall at the Lingshui Li Autonomous County of Hainan, on June 24, at 01:30 UTC. The system weakened over Hainan, and it entered the Gulf of Tonkin at 08:30 UTC as a severe tropical storm on the same day. Wukong made its next landfall over Giao Thủy district, Nam Định province, Vietnam at 18:45 UTC. The storm weakened rapidly after that. The JMA downgraded Wukong to a tropical depression on June 25, and the JTWC issued its last warning on the system on the same day. Wukong dissipated on June 26, over China's Yunan province.
In the Philippines, at least 9 deaths and 4 missing persons were attributed to Wukong. The system left 129 homes destroyed, 5,812 damaged, and caused damage to 190 road sections and 23 bridges. Across the country, around 400,000 people were evacuated. In the province of Quezon, more than half the province lost electricity after 300 electric poles were toppled. In Catanduanes, the collapse of a church ceiling caused 18 people to be injured. Overall, damages nationwide were estimated at ₱9.65 billion (US$166.6 million), at which agricultural losses reached ₱1.81 billion (US$31.2 million) and infrastructure damage reached ₱4.57 billion (US$79.0 million). In China, 23 people were killed in Hainan as heavy rain and strong winds battered the island. More than 50,000 people were evacuated from hazardous areas while 19,613 fishing vessels were also docked ahead of the storm. Severe flooding due to storm surge was recorded in the major city of Haikou. Meanwhile, in Yunan, torrential rain from the remnant's of Wukong caused hundreds of landslides across the province. This, together with flash floods, claimed 18 lives in Yunan. In total, economic damages were estimated at ¥51.45 billion (US$7.217 billion) across China. In Vietnam, 7 people were killed, 19 others were reported missing and 88 were injured by Wukong. Around 60 houses were destroyed, while more than 33,000 houses were damaged and 2,000 homes submerged. In addition, more than 33,900 ha (13,350 acres) of crops, 28,000 livestock, and nearly 170,000 poultry were lost. Over 3,800 roads were rendered impassable by flooding and landslides. Damages in the country were valued at 343 billion VND (US$13 million).
Notable stats: Wukong was the third-costliest storm of the season. It was also the first storm of the season to make direct landfall over Hainan's Lingshui Li Autonomous County, followed by Tropical Storm Shanshan.
Tropical Depression Gavino[]
| Max 1-min winds: | Not specified |
|---|---|
| Max 10-min winds: | <30 kt (55 km/h) |
| Min pressure: | 1002 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 | None |
| Damages | None |
| Tropical depression (JMA) | |
|---|---|
  | |
| Duration | June 30 – July 4 |
| Peak intensity | <55 km/h (35 mph) (10-min); 1002 hPa (mbar) |
On June 30, at 18:00 UTC, the JMA noted on the development of a low-pressure area located 60 km (37 mi) to the northwest of Ngulu Atoll, Yap State of the Federated States of Micronesia. The system slowly developed, and the JTWC raised its probabilities of developing into a significant tropical cyclone in the next 24 hours from "low" to "medium" on July 1. At around the same time, the PAGASA recognised the system as a tropical depression inside the Philippine Area of Responsibility. This caused the agency to name it Gavino. Gavino continued to move westwards, and it made landfall over Cagwait, Surigao del Sur, Mindanao on July 3 at 06:00 UTC. Land interaction caused Gavino's convection to quickly vaporise, and the JTWC subsequently cancelled any bulletin on the storm's potential for tropical cyclone development. Gavino was last noted by the JMA on July 4, over Pangantucan, Bukidnon.
Notable stats: Only recognized by the JMA and PAGASA as a tropical depression, but not the JTWC.
Typhoon Jongdari (Hanna)[]
| Max 1-min winds: | 125 kt (230 km/h) |
|---|---|
| Max 10-min winds: | 95 kt (175 km/h) |
| Min pressure: | 925 hPa (mbar) |
| ACE accumulated | 26.73 |
| TD+ days | 11.25 days |
| TS+ days | 10 days |
| C1+ days | 6.75 days |
| C3+ days | 2.5 days |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 30 |
| Damages | $4.5146 billion (USD) |
| Very Strong Typhoon (JMA) | |
|---|---|
| Category 4 typhoon (SSHWS) | |
  | |
| Duration | July 5 – July 16 (Extratropical) |
| Peak intensity | 175 km/h (110 mph) (10-min); 925 hPa (mbar) |
On July 3, the JTWC noted on a tropical disturbance embedded in a monsoon trough developing 280 km (174 mi) to the north-northwest of Pohnpei in the Federated States of Micronesia. The disturbance moved northwestwards and slowly organised. On July 4, at 12:00 UTC, the JMA upgraded the system from a low-pressure area to a tropical depression. Six hours later, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system. The agency then upgraded the system to Tropical Depression 11W on July 5, at 06:00 UTC. As 11W's convective structure continued to become more organised, the JMA upgraded it to a tropical storm on July 6, at 00:00 UTC, and named it Jongdari. Meanwhile, the JTWC followed suit and also upgraded Jongdari to a tropical storm 12 hours later. By early July 7, moderate northwesterly shear have hindered the storm's development, and its convection became displaced while its low-level circulation center became exposed. However, the decrease of wind shear after July 8 allowed it to strengthen to a severe tropical storm that day, according to the JMA. On July 9, as a nascent eye feature developed over the centre of Jongdari, the JTWC upgraded the system to a typhoon. The JMA did the same six hours later. At 12:00 UTC on the same day, as Jongdari entered the Philippine Area of Responsibility, the PAGASA named the typhoon Hanna. In the next 36 hours, Jongdari was embedded in a favourable environment of development, with warm 30 °C (86 °F) sea surface temperatures, low 10–15 knots (19–28 km/h; 12–17 mph) wind shear, and excellent outflow. This allowed the typhoon to rapidly deepen. On July 11, at 06:00 UTC, Jongdari attained its peak as a Category 4-equivalent typhoon, with maximum 1-minute sustained winds of 230 km/h (145 mph) and a minimum central pressure of 925 mbar (27.32 inHg). On early July 12, Jongdari started to weaken due to the onset of an eyewall replacement cycle, where its eye became cloud-filled. By July 13, Jongdari started to recurve and moved towards the Wikipedia:Ryukyu Islands. The typhoon passed within 30 km (19 mi) to the east of Miyako-jima at 07:00 UTC on July 14, as a Category 2-equivalent typhoon. The system entered the East China Sea after that. Jongdari continued to slowly weaken and moved northwards. The storm passed at around 20 km (12 mi) to the east of Jeju Island on July 15, at 13:00 UTC, and it made its first landfall over Nam-myeon, Yeosu as a Category 1-equivalent typhoon three hours later. Land interaction with the Korean Peninsula further weakened Jongdari, causing the JMA to downgrade the system to a severe tropical storm at 18:00 UTC. Jongdari then moved over the Sea of Japan at 22:00 UTC on the same day. Two hours later, the JTWC issued its final warning on the system due to the latter's extratropical transition and diminishing deep convection. Jongdari accelerated northeastward and became completely extratropical by late July 16. On early July 18, the extratropical cyclone of Jongdari passed the southern tip of the Kamchatka Peninsula. From July 19 to 20, the extratropical cyclone brushed passed the Aleutian Islands, where it interacted with the unusually powerful North Pacific jet stream and underwent explosive cyclogenesis. After reaching an estimated minimum central pressure of 951 mbar (28.08 inHg) on July 21, at 00:00 UTC, the hurricane-forced extratropical cyclone gradually weakened. The extratropical remnants of Jongdari was last noted on July 24, over Alaska.
The July 14 passage of Jongdari near the Ryukyu Islands brought torrential rain and severe winds to the island chain. Throughout the islands, 3 deaths and 40 injuries were confirmed. In Okinawa Prefecture, 8,800 power failures have been recorded, and 14 buildings were reported to have been completely destroyed. Total economic losses in the prefecture reached ¥19.51 billion (US$128 million). Meanwhile, in South Korea, Jongdari dropped near record-breaking rains over the southern part of the country, especially on Jeju Island which received more than 1,300 mm (51.2 in) of rainfall from July 13 to 14. On July 14 alone, 880 mm (34.7 in) fell on the island. These rains triggered widespread flooding across the nation. In Cheongdo County, North Gyeongsang Province, three died in a flood-related accident in Cheongdo Valley when their vehicle was swept away. Violent winds were recorded across the country as well, which downed trees, power lines, and damaged buildings. In Jeju, winds gusts peaking at 217 km/h (135 mph) were recorded. Power loss were recorded on the island as approximately 2,400 residences briefly lost power on July 14. At the same time, portions of a baseball stadium's roof in Gwangju, South Jeolla Province was torn off and scattered across a nearby highway. Total fatalities in South Korea reached 25, while economic damages of ₩6.121 trillion (US$4.282 billion) were recorded. The extratropical remnants of Jongdari affected Alaska and the Russian Far East, damaging buildings there with hurricane-forced winds.
Notable stats: Jongdari was the fourth-costliest storm of the season and the strongest storm to impact South Korea since Typhoon Kajiki in 2054, slightly beating out Typhoon Jamjari from 2066.
Tropical Storm Shanshan (Ineng)[]
| Max 1-min winds: | 40 kt (75 km/h) |
|---|---|
| Max 10-min winds: | 40 kt (75 km/h) |
| Min pressure: | 998 hPa (mbar) |
| ACE accumulated | 1.78 |
| TD+ days | 4.5 days |
| TS+ days | 3.25 day |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 7 |
| Damages | $45.79 million (USD) |
| Tropical storm (JMA) | |
|---|---|
| Tropical storm (SSHWS) | |
  | |
| Duration | July 15 – July 20 |
| Peak intensity | 75 km/h (45 mph) (10-min); 998 hPa (mbar) |
On July 13, the JTWC began monitoring a convective area in a monsoon trough located 760 km (472 mi) to the east of Casiguran, Aurora. Due to its broad initial circulation, the system organised itself slowly. By late July 14, the JMA upgraded it from a low-pressure area to a tropical depression over the Philippine Sea. At 00:00 UTC on the next day, the PAGASA also recognised the storm as a tropical depression inside the Philippine Area of Responsibility, hence naming it Ineng. Ineng managed to construct its low-level circulation centre (LLCC) on the same day, which caused the JTWC to issue a Tropical Cyclone Formation Alert (TCFA) on the system at 02:00 UTC. Ten hours later, the JTWC upgraded Ineng to Tropical Depression 12W while it was passing close to the northern part of Luzon, over the Luzon Strait. Over the South China Sea, 12W slowly strengthened over warm sea surface temperatures but marginal wind shear. It was upgraded to a tropical storm by the JTWC on July 16 at 06:00 UTC, while the JMA followed suit 12 hours later and named the storm Shanshan. Shanshan made its first landfall over Lingshui Li Autonomous County, Hainan at 12:20 UTC on July 18. It then entered the Gulf of Tonkin at 22:00 UTC on the same day. Shanshan then made a series of brief landfalls over the numerous islands of Quảng Ninh province by early July 19. It made its final landfall on Tiên Yên district, Quảng Ninh province, at 09:00 UTC on the same day. The JMA downgraded Shanshan to a tropical depression three hours later due to land interaction, and the JTWC issued its final warning on the system later on the same day. Shanshan was last noted by the JMA on July 20, when its remnants dissipated near the southern borders of the Jinping Miao, Yao, and Dai Autonomous County of Yunnan
When Shanshan crossed the Luzon Strait, swells generated by the storm drowned two beachgoers at Xuhai beach, Mudan, Pingtung County in Taiwan. In Hainan, Shanshan brought damaging floods to the province. Authorities evacuated 12,180 people from flood-prone homes. Coastal waves reached 2-4 m (6.6-13.1 ft), damaging some fishing vessels. Eight sailors in Sanya were rescued after their cargo ship was battered by 3.0 m (10 ft) waves. Shanshan also brought rain and wind to Leizhou Peninsula and parts of Guangxi. A rain-induced landslide in Luchuan County, Guangxi, claimed four lives. In total, 5 people lost their lives in China, and direct economic losses totaled CN¥306.86 million (US$43.13 million).
Notable stats: The second storm of the season to make direct landfall over Hainan's Lingshui Li Autonomous County, after Typhoon Wukong.
Severe Tropical Storm Sasori[]
| Max 1-min winds: | 50 kt (95 km/h) |
|---|---|
| Max 10-min winds: | 50 kt (95 km/h) |
| Min pressure: | 986 hPa (mbar) |
| ACE accumulated | 3.5525 |
| TD+ days | 8 days |
| TS+ days | 4.5 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 20 – July 28 (Extratropical) |
| Peak intensity | 95 km/h (60 mph) (10-min); 986 hPa (mbar) |
On July 18, the JTWC noted on a developing tropical disturbance located 230 km (143 mi) to the east of Talo'fo'fo, Guam. The disturbance moved slowly and erratically at first. On July 19, at 04:00 UTC, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system, while the JMA upgraded the system to a tropical depression two hours later. The JTWC upgraded the storm to Tropical Depression 13W at 06:00 UTC on the next day, when it passed through the Northern Mariana Islands. On July 26, 13W started to recurve to the northeast due to a break of the subtropical ridge to the system's north. At 06:00 UTC on July 27, 13W was upgraded to Tropical Storm Sasori by the JMA, while the JTWC also upgraded Sasori to a tropical storm 12 hours later. Sasori was embedded in a marginally favourable environment by July 24, which allowed it to slowly intensify. The JMA upgraded the storm to a severe tropical storm on early July 25. Sasori reached its peak at 12:00 UTC that day, with maximum 1-minute sustained winds of 95 km/h (65 mph) and a minimum central pressure of 986 mbar (29.12 inHg). On July 26, Sasori structure slightly degraded due to increased wind shear, but it managed to recover in the late hours of the same day as wind shear decreased again. After a brief second peak, decreasing sea surface temperatures and dry air intrusion caused Sarori to enter a sustained trend of weakening. On early July 28, Sasori started its extratropical transition, and the JTWC issued its last warning on the system. At 06:00 UTC, Sasori turned fully extratropical as it accelerated towards the northeast. The storm's extratropical remnant was last noted near the Aleutian Islands on July 29, by the JMA.
Notable stats: None.
Typhoon Leepi[]
| Max 1-min winds: | 135 kt (250 km/h) |
|---|---|
| Max 10-min winds: | 100 kt (185 km/h) |
| Min pressure: | 913 hPa (mbar) |
| ACE accumulated | 32.4425 |
| TD+ days | 14.75 days |
| TS+ days | 12.75 days |
| C1+ days | 7 days |
| C3+ days | 4 days |
| SuperTY days | 1.25 days |
| C5 days | N/A |
| Fatalities | None |
| Damages | $1.2 million (USD) |
| Very Strong Typhoon (JMA) | |
|---|---|
| Category 4 super typhoon (SSHWS) | |
  | |
| Duration | July 23 – August 7 (Extratropical) |
| Peak intensity | 185 km/h (115 mph) (10-min); 913 hPa (mbar) |
On early July 21, a tropical disturbance entered the basin from the Central Pacific. The disturbance switched to a more northwestward movement shortly after passing the International Date Line. On July 22, the storm was in a marginally favorable environment with 15–20 knots (28–37 km/h; 17–23 mph) wind shear, 29–30 °C (84–86 °F) sea surface temperatures, and moderate outflow aloft. At that time, multispectral imagery showed the system has developed an ill-defined low-level circulation center (LLCC) with flaring convection along its western side. As a result, the JMA upgraded the system to a tropical depression at 12:00 UTC. 12 hours later, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system. On the next day, at 18:00 UTC, the JTWC upgraded the system to Tropical Depression 14W. On July 24, at 12:00 UTC, the JMA upgraded 14W to a tropical storm, and named it Leepi. After becoming a minimal tropical storm, Leepi was faced with moderate to high vertical wind shear starting from late July 25. By the next day, Leepi's LLCC became fragmented and completed exposed, while its convection was displaced to the southwest. This caused both the JMA and the JTWC to downgrade Leepi to a tropical depression by mid-July 26. On July 27, wind shear lessened surrounding Leepi, and this allowed the system's deep convection to cover its LLCC again. As a result, both the JMA and the JTWC re-upgraded Leepi to a tropical storm later on the same day. Favourable environmental conditions allowed Leepi to quickly develop. The JTWC upgraded Leepi to a minimal typhoon on July 28, at 06:00 UTC. The JMA followed suit six hours later. On July 29, at 11:00 UTC, Leepi passed between Anatahan and Asuncion Island in the Northern Mariana Islands as a strong Category 1-equivalent typhoon. The typhoon soon entered a phase of rapid intensification. The JTWC upgraded Leepi to a super typhoon on July 30, at 06:00 UTC. 12 hours later, Leepi peaked as a strong Category 4-equivalent super typhoon, with maximum 1-minute sustained winds of 250 km/h (155 mph) and a minimum central pressure of 913 mbar (26.96 inHg). Leepi held on to super typhoon status for 30 hours, before the onset of an eyewall replacement cycle on July 31 started to weaken it and caused its convection to become uneven and its eye to become cloud-filled. By August 1, the slowdown of Leepi's movement when it recurved offshore from the south of Japan caused upwelling and further decreased sea surface temperatures beneath itself. This caused Leepi to further weaken. The storm lost its typhoon status according to both the JMA and the JTWC on August 4 when it passed between the Izu Islands and Bonin Islands. On August 7, Leepi stated to accelerate towards the northeast as it interacted with the westerlies and started its extratropical transition. The JTWC issued its final advisory on the same day while the JMA continued monitoring the system until declaring it extratropical at 13:00 UTC. The extratropical remnants of Leepi continued to move northeastward quickly, and it was last noted near the Aleutian Islands on August 9, at 00:00 UTC.
Notable stats: Leepi was the second super typhoon of the season.
Typhoon Bebinca (Jenny)[]
| Max 1-min winds: | 90 kt (165 km/h) |
|---|---|
| Max 10-min winds: | 75 kt (140 km/h) |
| Min pressure: | 954 hPa (mbar) |
| ACE accumulated | 8.64 |
| TD+ days | 6.75 days |
| TS+ days | 6 days |
| C1+ days | 2.25 days |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 35 |
| Damages | $3.6612 billion (USD) |
| Typhoon (JMA) | |
|---|---|
| Category 2 typhoon (SSHWS) | |
  | |
| Duration | July 24 – July 31 (Extratropical) |
| Peak intensity | 140 km/h (85 mph) (10-min); 954 hPa (mbar) |
On July 23, the JMA noted a broad low-pressure area had developed into a tropical depression 280 km (174 mi) to the west of Angaur, Palau. The system moved northwards over the next day. By early July 24, as the storm become more organised, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system. At 12:00 UTC on the same day, the JTWC upgraded the system to Tropical Depression 15W. At the same time, as the PAGASA recognised 15W as a tropical depression that was located in the Philippine Area of Responsibility, the agency name it Jenny. At 18:00 UTC, the JMA upgraded 15W into a tropical storm, naming it as Bebinca. Six hours later, the JTWC followed suit and also upgraded Bebinca to a tropical storm. Over the next two days, favourable conditions over the Philippine Sea allowed Bebinca to steadily strengthen. On July 26, the JMA upgraded Bebinca to a severe tropical storm. The storm switched to move northwestward, as it became a minimal typhoon according to the JTWC on the next day, at 00:00 UTC. Six hours later, the Bebinca also reached typhoon status according to the JMA. On July 28, at 06:00 UTC, Bebinca reached its peak intensity as a Category 2-equivalent typhoon, with maximum 1-minute sustained winds of 165 km/h (105 mph) and a minimum central pressure of 954 mbar (28.17 inHg). Over the next day, as the storm moved towards Taiwan, land interaction caused the typhoon to slowly weaken and moved erratically hours before its landfall. Bebinca made landfall over Suao Township, County at 00:00 UTC on July 29 as a Category 1-equivalent typhoon. Four hours later, the typhoon directly passed over Taoyuan, and it entered the Taiwan Strait at 05:00 UTC. An hour later, both the JMA and the JTWC have assessed that Bebinca lost its typhoon status due to its previous Taiwan landfall. Over the Taiwan Strait, Bebinca started moving northwards due to a weakness in a subtropical ridge south of Japan and the presence of a surface front across the east coast of Asia. At 17:00 UTC on the same day, Bebinca made landfall on Cangnan County, Wenzhou, Zhejiang as a tropical storm. The storm then continued moving northwards over the next 36 hours, through the Chinese provinces of Zhejiang, Jiangsu and Shandong. When Bebinca just entered the Yellow Sea, on July 30 at 18:00 UTC, the JTWC issued its final warning on the storm, while the JMA downgraded the system to a tropical depression six hours later. Bebinca underwent extratropical transition on July 31, and its extratropical cyclone passed through Shandong Peninsula and North Korea from July 31 to August 1. The JMA stopped tracking Bebinca's extratropical remnants when it dissipated over the Sea of Japan, on August 5, at 06:00 UTC.
Bebinca brought significant disruptions to Taiwan. Many trees fell down on roads and damaged infrastructure. A landslide occurred on the Central Cross-Island Highway, near Guguan in Heping District, Taichung, which forced vehicles to drive on the same lane. Three people in the country lost their lives as a mudslide buried a remote mountain village in Nantou County. Total economic losses in Taiwan reached NT$70.51 billion (US$2.30 billion). In Mainland China, Fujian and Zhejiang were the two provinces that were hardest hit by Bebinca. In Fujian, the storm damaged or demolished more than 150 fishing boats, wiped out 10 bridges, snapped 28 power lines, and flooded six reservoirs. Two were killed in the tens of tornadoes spawned by Bebinca. Total damages reached ¥7.63 billion (US$1.07 billion) there. In Zhejiang, torrential rainfall was recorded across much of the province, with as much as 530 mm (20.87 in) of rain recorded falling in a 24-hour period in Wenzhou. In Jiaxing, a minimum of 88,900 ha (219,700 acres) of farmland were flooded, and 250 homes were damaged due to the system. Overall in Mainland China, 17 lost there lives, and economic damages amassed to at least ¥9.62 billion (US$1.35 billion). In North Korea, Bebinca's extratropical remnants brought violent winds and heavy rainfall to the country. Authorities announced that 13 fatalities have been recorded in the country.
Notable stats: None.
Tropical Storm Pulasan[]
| Max 1-min winds: | 55 kt (100 km/h) |
|---|---|
| Max 10-min winds: | 45 kt (85 km/h) |
| Min pressure: | 981 hPa (mbar) |
| ACE accumulated | 5.2425 |
| TD+ days | 13.5 days |
| TS+ days | 7.75 days |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 174 |
| Damages | $1.8444 billion (USD) |
| Tropical storm (JMA) | |
|---|---|
| Tropical storm (SSHWS) | |
  | |
| Duration | August 1 – August 17 |
| Peak intensity | 85 km/h (55 mph) (10-min); 981 hPa (mbar) |
On July 31, the JTWC identified an area of convection about 240 km (149 mi) to the southeast of Paracel Islands over the South China Sea. The disturbance initially showed a weak low-level circulation centre (LLCC) with flaring convection. On August 1, the disturbance consolidated, causing the JMA to classify the system as a tropical depression. At 08:00 UTC on the same day, the JTWC issued Tropical Cyclone Formation Alert (TCFA) on the system. The agency then further upgraded the storm to Tropical Depression 16W ten hours later. The depression moved slowly northeastward, with satellite imagery showing an exposed LLCC over the next three days. By mid-August 4, as vertical wind shear lessened, the system's convection managed to completely cover its centre. This prompted the JTWC to upgrade the system to a tropical storm on August 5, at 00:00 UTC. The JMA followed suit 18 hours later, and named it Pulasan. On August 6, as Pulasan interacted with a subtropical ridge to its north, it started moving northwestward, towards China's Guangdong Province. On August 8, at 00:00 UTC, Pulasan made a very close approach to Hong Kong as a tropical storm, passing only 20 km (12 mi) to the south of the special administrative region. The storm then passed over the numerous islands of Wanshan Archipelago, and made landfall over Taipa, Macau at 07:00 UTC on the same day. Pulasan passed through Zhuhai, Guangdong, and it moved back out at sea at 15:00 UTC, slightly weakened due to land interaction. On the next day, the storm made a small loop over the South China Sea and started to move westward. The system restrengthened due to favourable conditions at this point. On August 10, at 13:30 UTC, Pulasan made landfall over Wuchuan, Guangdong. It then passed directly above the city of Zhanjiang 90 minutes later. Despite land interaction, the system continued to maintain its overall convective organization. Pulasan exited Leizhou Peninsula and entered the Gulf of Tonkin at 19:00 UTC on the same day. Due to moderate to high wind shear, the convection of Pulasan slowly displaced and decayed, and it made landfall over Vân Đồn special administrative region, Quảng Ninh, Vietnam at 06:00 UTC on August 11. Pulasan quickly weakened after that, and both the JMA and the JTWC soon issued their final warnings on the storm later on the same day. Pulasan degenerated into an area of low pressure embedded in a monsoon trough on August 12 according to the JMA. The JTWC, however, continued to track the system's remnants for the next two days. Through August 12 and 13, Pulasan's remnants curved southwards and then eastwards over Northern Vietnam, before moving back over the Gulf of Tonkin by early August 14. Persistent convection developed over the system, aided by a tropical upper tropospheric trough (TUTT) to the northeast. As a result, JTWC to begin issuing advisories on Pulasan once again one the same day. Simultaneously, the JMA reported that Pulasan had regenerated into a tropical depression. With low vertical wind shear and sea surface temperatures remaining high near 30 °C (86 °F), Pulasan quickly organised itself, and both the JMA and the JTWC assessed the system was back to tropical storm strength by late August 14. Pulasan reached its peak according to the JTWC at 06:00 UTC on August 15, with maximum 1-minute sustained winds of 100 km/h (65 mph) and a minimum central pressure of 981 mbar (28.97 inHg). However, the JMA did not assess the system to have reached a new peak, and kept it at 10-minute sustained winds of 85 km/h (50 mph). Pulasan moved northeastward over the Gulf of Tonkin, and it made its last landfall over Beihai, Guangxi at 08:30 UTC on the same day. Pulasan's convection quickly dissipated after that, and the system was downgraded to a tropical depression by both the JMA and the JTWC at 18:00 UTC. Early on August 16, the JTWC issued its final warning on the system, while the JMA continued to track the system until it dissipated over Jingxi, Guangxi on August 17.
Pulasan affected southern China twice, first between August 7 to 11, second from August 15 to 17. Both times the storm caused severe flooding in the country due to heavy rainfall. In Hainan, rainfall in parts of the island peaked at 400 mm (16 in) in a 24-hour period. In Guangdong, 55 thousand residents were evacuated in the cities of Zhanjiang and Maoming, with passenger and train services being halted due to safety concerns. 13 thousand fishermen, 49 thousand offshore workers, and 38 thousand boats were brought back to land. Damages in China were estimated at CN¥1.66 billion (US$233.6 million), with 20 fatalities recorded there. In Vietnam, the provinces of Thanh Hóa, Ninh Bình and Nghệ An suffered the most damage, mostly due to flooding. Numerous instances of major flooding occurred in Northern Vietnam, including the capital city of Hanoi. Major agriculture losses were also recorded in the country, with 119,000 hectares (294,000 acres) of crops and 21,000 farm animals swept away or died. Throughout the nation, 17,000 houses were submerged or damaged, while 800 of them were completely destroyed. Economic losses were estimated to be ₫30.65 trillion (US$287 million), while 59 people lost their lives.
Notable stats: Pulasan was the second-deadliest storm of the season.
Typhoon Henriette (Kabayan)[]
| Max 1-min winds: | 125 kt (230 km/h) |
|---|---|
| Max 10-min winds: | 95 kt (175 km/h) |
| Min pressure: | 937 hPa (mbar) |
| ACE accumulated | 39.9725 (in basin) |
| TD+ days | 20.75 days (in basin) |
| TS+ days | 15.5 days (in basin) |
| C1+ days | 10.25 days |
| C3+ days | 3 days |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 6 |
| Damages | $39.85 million (USD) |
| Very Strong Typhoon (JMA) | |
|---|---|
| Category 4 typhoon (SSHWS) | |
  | |
| Duration | August 4 (Entered basin) – August 27 (Extratropical) |
| Peak intensity | 175 km/h (110 mph) (10-min); 937 hPa (mbar) |
On August 4, at 06:00 UTC, Tropical Depression Henriette moved into the basin from the Central Pacific basin. Both the JMA and the JTWC declared that the depression had just crossed the International Date Line, and the two agencies started initiating advisories on Henriette as a tropical depression. As wind shear slightly decreased to the west of the International Date Line, Henriette's cloud tops cooled, and its convection became less displaced. This prompted the JTWC to upgrade the system to a tropical storm at 18:00 UTC on the same day. The JMA followed suit six hours later. Due to favourable conditions, Henriette continued to steadily strengthen over the next two days. The JMA granted severe tropical status to the system by late August 5, before classifying it as a typhoon on the next day. The JTWC agreed and assessed Henriette to have reached a temporary peak as a Category 1-equivalent typhoon, at 18:00 UTC on August 6. However, by early August 7, the increase of vertical wind shear caused Henriette's nascent eye to vanish, and it cloud tops to warm. During this time, the system showed significant deterioration along its northern flank and severe disorganisation of its deep convection. This caused both the JTWC and JMA to downgrade the system to a tropical storm on the same day. Henriette's weakening continued as its low-level circulation centre (LLCC) further became broad and exposed, and the system lost its status as a tropical cyclone for a third time on August 9, at 18:00 UTC. Henriette's remnant low travelled eastward on August 10 under consistently high vertical wind shear of 35 km/h (20 mph). The JTWC noted that Henriette has briefly regenerated into a tropical depression on August 11, before it degenerated back into a remnant low on the next day. However, the JMA kept Henriette as a low-pressure area from August 9 to 14. By August 14, the lessening of windshear allowed Henriette to once again regenerate to a tropical depression at around 06:00 UTC on the same day. Both the JMA and the JTWC initiated warnings again on the system. As Henriette entered an area of the ocean with favourable conditions, such as 5–10 knots (9-19 km/h; 6-12 mph) of wind shear, 29–30 °C (84–86 °F) sea surface temperatures, excellent equatorward outflow and moderate poleward outflow aloft, the storm started to rapidly consolidate itself. Both agencies upgraded Henriette back to a tropical storm again on August 15, and subsequently a typhoon on the next day. Henriette entered a phase of rapid intensification from August 16 to 17. The system reached its peak intensity as a Category 4-equivalent typhoon on August 18 at 12:00 UTC, with maximum 1-minute sustained winds of 230 km/h (145 mph) and a minimum central pressure of 937 mbar (27.67 inHg). 12 hours later, as the typhoon entered the Philippine Area of Responsibility, the PAGASA named it Kabayan. By late August 19, Henriette started an eyewall replacement cycle, which caused its eye to become cloud-filled, and its cloud tops to warm. On the next day, Henriette stalled over the open ocean and started to move north-northwest due to a trough embedded in a subtropical ridge to its northwest. Over the next five days, the typhoon's strength fluctuated between a Category 1-equivalent typhoon and a Category 2-equivalent typhoon. On August 23, at 10:00 UTC, Henriette passed 15 km (9 mi) to the eastern tip of Okinawa as a strong Category 1-equivalent typhoon. 75 minutes later, it made a brief landfall over Yoronjima, before continuing its journey north-northwest. On August 25, due to decreasing sea surface temperatures, Henriette's convection waned, which caused the JMA to downgrade the system from a typhoon to a severe tropical storm. During this time, the storm started to move northeast as it brushed past Fukue Island at 09:00 UTC on the same day. Henriette then moved along the Korea Strait as a weakening tropical storm over the next 24 hours, becoming increasingly sheared. The system initiated its extratropical transition late on August 27, and as a result, the JTWC discontinued all advisories on Henriette. Over the next three days, Henreitte's extratropical remnants moved over the Sea of Japan, Sakhalin, Sea of Okhotsk and Kamchatka Peninsula. After passing the Kamchatka Peninsula, on August 31, Henriette's extratropical cyclone underwent explosive cyclogenesis and reached an estimated minimum central pressure of 962 mbar (28.41 inHg) on September 1, at 00:00 UTC. After that, the hurricane-forced extratropical cyclone weakened, until it was last noted on the next day, located at the south of the Aleutian Islands.
Throughout its long life, Henriette brought moderate impact to several places, mostly concentrated at Japan's Ryukyu Islands. In Okinawa, at least 18 people have been injured and two deaths were reported. Power outage was also observed on the island. According to the Okinawa Electric Power Company, the typhoon knocked off power to approximately 108,000 residences. Damage across the whole Ryukyu island chain exceeded ¥2.97 billion (US$19 million).
Notable stats: Henriette is the longest-lived tropical cyclone ever recorded. Formed on July 19 in the Eastern Pacific, entered the Western Pacific on August 4, and transitioned into an extratropical cyclone on August 27, it lasted 39 days between its first and last tropical depression phase, beating out the record of 38 days by Cyclone Freddy in 2023. It is also the farthest-traveling tropical cyclone ever observed, travelling a distance of 14,090 km (8,760 mi) as a tropical system, surpassing the record of 13,180 km (8,190 mi) set by Hurricane John in 1994. Henriette was the first storm designated in the Eastern Pacific to cross the International Date Line and reach the West Pacific since Hurricane/Typhoon Miriam in 2042. It is also the only Eastern Pacific-originated tropical cyclone to have ever received a local name by the PAGASA. Henriette had 4 regenerations, at which 2 were in the Western Pacific.
Severe Tropical Storm Soulik[]
| Max 1-min winds: | 50 kt (95 km/h) |
|---|---|
| Max 10-min winds: | 50 kt (95 km/h) |
| Min pressure: | 984 hPa (mbar) |
| ACE accumulated | 2.295 |
| TD+ days | 4.5 days |
| TS+ days | 3 days |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | None |
| Damages | $1.1 million (USD) |
| Severe tropical storm (JMA) | |
|---|---|
| Tropical storm (SSHWS) | |
  | |
| Duration | August 7 – August 11 (Extratropical) |
| Peak intensity | 95 km/h (60 mph) (10-min); 984 hPa (mbar) |
On August 3, the JMA announced that a new tropical depression had developed 680 km (423 mi) to the west of Wake Island. The system slowly meandered southeastwards before gradually turning to the west while slowly consolidating itself. On August 6, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the storm, before designating it as 17W on the next day. 17W's circulation was initially exposed due to wind shear and moderate dry air disruption. However, the improvements of environmental conditions by late August 7 allowed 17W to build deep convections over its core. As a result, the JMA upgraded 17W to Tropical Storm Soulik on August 8, at 00:00 UTC. As Soulik moved generally northwards, it continued to build its core. By August 10, the JMA upgraded the system to a severe tropical storm. Meanwhile, the JTWC assessed Soulik to have reached its peak at 12:00 UTC on the same day, with maximum 1-minute sustained winds of 95 km/h (60 mph) and a minimum central pressure of 984 mbar (29.06 inHg). At the same time, Soulik accelerated towards the northwest as it interacted with Tropical Depression 18W, which was located less than 1,000 km (621 mi) to its west. The distance between the two systems rapidly decreased in the following hours, and by early August 11, 18W was completed sheared apart by Soulik and was absorbed into the outer rainbands of the latter. Soulik's convection then collapsed as it traversed colder waters and weakened. Both the JMA and the JTWC stopped issuing warnings on the system by late August 11 as Soulik was noted to undergo an extratropical transition. The system became a full-fledged extratropical cyclone on August 12 as it moved northwards over the Sea of Okhotsk. Soulik's extratropical remnants was last noted over Oymyakonsky District, Sakha Republic, Russia, on August 13, at 18:00 UTC.
Notable stats: Soulik absorbed 18W when they were located to the east of Japan.
Tropical Depression 18W[]
| Max 1-min winds: | 40 kt (75 km/h) |
|---|---|
| Max 10-min winds: | 30 kt (55 km/h) |
| Min pressure: | 1000 hPa (mbar) |
| ACE accumulated | 0.4425 |
| TD+ days | 3.5 days |
| TS+ days | 0.75 days |
| C1+ days | N/A |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | None |
| Damages | None |
| Tropical depression (JMA) | |
|---|---|
| Tropical storm (SSHWS) | |
  | |
| Duration | August 7 – August 11 |
| Peak intensity | 55 km/h (35 mph) (10-min); 1000 hPa (mbar) |
On August 5, the JTWC noted on a tropical disturbance that formed within a monsoon trough, located 600 km (373 mi) to the northwest of Guam. The disturbance moved northwestward, and was recognised by the JMA as a tropical depression on August 6. On the next day, at 03:00 UTC, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system, noting on its increasing organisation. The agency then upgraded the storm to Tropical Depression 18W nine hours later. 18W slowed down and meandered northwards as it interacted with a trough to its northeast. From August 8 to 9, marginal environmental conditions prevented the system from significantly strengthening. However, wind shear affecting the system lessened after August 9. This allowed 18W to strengthen to a brief minimal tropical storm on August 10 according to the JTWC. Despite this, the JMA kept 18W as a tropical depression the whole time. On August 10, at 14:00 UTC, 18W made landfall over Minamiizu, Kamo District, Shizuoka, located at the southern tip of Izu Peninsula. The system then accelerated towards the northeast as it interacted with Severe Tropical Storm Soulik. 18W quickly closed its distance with Soulik and became increasingly sheared by the latter's outflow. By early August 11, both the JMA and JTWC issued their last warning on the storm as 18W was absorbed into the outer rainbands of Soulik.
Notable stats: 18W was absorbed by Soulik when they were located to the east of Japan. 18W was also the first and only storm this season classified by the JTWC as a tropical storm but not the JMA.
Typhoon Cimaron[]
| Max 1-min winds: | 130 kt (240 km/h) |
|---|---|
| Max 10-min winds: | 100 kt (185 km/h) |
| Min pressure: | 919 hPa (mbar) |
| ACE accumulated | 44.585 |
| TD+ days | 15.75 days |
| TS+ days | 13.25 days |
| C1+ days | 11 days |
| C3+ days | 4.25 days |
| SuperTY days | 0.75 days |
| C5 days | N/A |
| Fatalities | 1 |
| Damages | $181 million (USD) |
| Very Strong Typhoon (JMA) | |
|---|---|
| Category 4 super typhoon (SSHWS) | |
  | |
| Duration | August 16 – September 1 |
| Peak intensity | 185 km/h (115 mph) (10-min); 919 hPa (mbar) |
On August 14, a broad area of low pressure developed inside an eastward-extended monsoon trough in the Central Pacific. The disturbance moved northwestward over the next two days. At August 16, at 00:00 UTC, the system crossed the International Date Line and crossed entered the Western Pacific. The JTWC then promptly issued a Tropical Cyclone Formation Alert (TCFA) on the system, while the JMA assessed the storm to be a tropical depression. At 06:00 UTC on the same day, the JTWC also upgraded the system to a tropical depression and designated it 19W. 19W tracked generally northwestward and gradually developed. The improvements in banding and convection caused the JMA to upgraded the system to Tropical Storm Cimaron on August 17, at 18:00 UTC. Cimaron continue to steadily intensify, and the JMA upgraded it to a severe tropical storm on August 18 at 18:00 UTC. 12 hours later, the JTWC upgraded Cimaron to a typhoon as the storm was noted to have a nascent eye embedded in a developing central dense overcast (CDO). At 12:00 UTC, the JMA also upgraded Cimaron to a typhoon. Later on August 19, vertical wind shear increased due to the passage of a mid-level trough to the north of the typhoon. This caused some erosion to the storm's CDO and halted the system's intensification on August 20, causing it to stay as a Category 2-equivalent typhoon. During this time, Cimaron's small core of persistent central convection remained. After August 22, the passage of the trough caused vertical wind shear to decrease. This allowed Cimaron to enter a phase of rapid intensification. On August 23, at 06:00 UTC, Cimaron reached its first peak as a Category 4-equivalent typhoon, with maximum 1-minute sustained winds reaching 230 km/h (145 mph) and a minimum central pressure of 928 mbar (27.40 inHg). Shortly after this peak, an increase in wind shear caused the system's coldest cloud tops to warm, and its CDO to become asymmetric. As a result, Cimaron slightly weakened by late August 23 and early August 24. However, as wind shear weakened again after that, Cimaron managed to restrengthened and attain its stronger second peak as a Category 4 super typhoon on August 25, at 00:00 UTC, with maximum 1-minute sustained winds reaching 240 km/h (150 mph) and a minimum central pressure of 919 mbar (27.14 inHg). Later on the same day, concentric eyewalls were observed in Cimaron, and the typhoon started an eyewall replacement cycle (EWRC). At the same time, as a shortwave trough moved across Honshu on August 25, Cimaron slowed down and turned towards the north in response to the weakness in the subtropical ridge. Then, as the trough passed by, Cimaron, which was by this time slowly weakening due to the ongoing EWRC and increased wind shear, resumed its northwestern trajectory and veered towards Japan. On August 28, aided by the warm water brought by the Kuroshio Current, Cimaron managed to burst new deep convection around its core. The JTWC at that time assessed the system to have restrengthened to a Category 2-equivalent typhoon. On August 30, at 02:30 UTC, Cimaron made its first landfall over Kadogawa, Higashiusuki, Miyazaki Prefecture, as a weakening typhoon. Shortly after this landfall, interaction with the mountainous terrain of Kyushu, along with increased wind shear aloft, quickly weakened Cimaron. Later on August 30, the JMA downgraded the system to a severe tropical storm, while the JTWC also assessed the storm to have lost typhoon status. Cimaron continued to weaken and gradually recurved towards the northeast over Kyushu. By late August 30, Cimaron entered the Sea of Japan as a tropical storm. By August 31, both the JMA and the JTWC downgraded Cimaron to a tropical depression as its centre had become exposed from the deep convection. At the same time, the JTWC issued its last warning on the system. Cimaron was last noted over the Sea of Japan as a remnant low on September 1.
Cimaron's damage over Japan was mostly concentrated in Kyushu. In Kagoshima Prefecture, one person died as he was swept away from the seaside by Cimaron's storm surge. Throughout Kyushu, a total of 1,609 houses were destroyed while 226 others were flooded. In addition, 200 homes lost power on August 30. Economic damage in Japan totaled at ¥28.3 billion (US$181 million), while 13 people were injured.
Notable stats: Cimaron was the third super typhoon of the season. It was also the second-largest ACE producer of the season.
Tropical Depression 20W[]
| 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 | 2.75 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 depression (JMA) | |
|---|---|
| Tropical depression (SSHWS) | |
  | |
| Duration | August 18 – August 21 (Extratropical) |
| Peak intensity | 55 km/h (35 mph) (10-min); 1001 hPa (mbar) |
On August 17, the JMA noted a low-pressure area was developing 940 km (584 mi) to the northwest of Wake Island. The JTWC also noted on the tropical disturbance and issued a tropical cyclone formation alert (TCFA) on the system by early August 18. Meanwhile, the JMA upgraded the system to a tropical depression by mid-August 18. At 18:00 UTC on the same day, the JTWC followed suit, and also upgraded the disturbance to a tropical depression, with the designation 20W. 20W moved northwestward at first. However, as the depression interacted with the westerlies, the system gradually recurved towards the northeast. By August 20, high vertical wind shear brought by the jet stream caused its core to become elongated, and is convection to become displaced. By early August 21, both the JMA and the JTWC stopped issuing warnings on the system as they noted the depression's extratropical transition. 20W became completely extratropical later on the same day.
Notable stats: None.
Typhoon Horangi[]
| Max 1-min winds: | 140 kt (260 km/h) |
|---|---|
| Max 10-min winds: | 105 kt (195 km/h) |
| Min pressure: | 910 hPa (mbar) |
| ACE accumulated | 37.6975 |
| TD+ days | 15 days |
| TS+ days | 13.75 days |
| C1+ days | 7.75 days |
| C3+ days | 5 days |
| SuperTY days | 1.75 days |
| C5 days | 0.5 days |
| Fatalities | None |
| Damages | None |
| Violent Typhoon (JMA) | |
|---|---|
| Category 5 super typhoon (SSHWS) | |
  | |
| Duration | August 27 – September 10 (Extratropical) |
| Peak intensity | 195 km/h (120 mph) (10-min); 910 hPa (mbar) |
On August 23, a tropical disturbance formed to the east of the International Date Line. It crossed the Date Line at 00:00 UTC on the next day and entered the Western Pacific basin. The system moved west-northwest steadily over the next two days. On August 25, as shower and thunderstorm activity was observed at the centre, the JMA upgraded the system to a tropical depression from a low-pressure area, while the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the disturbance. On August 27, at 00:00 UTC, the JTWC also upgraded the system to a tropical depression, with the designation 21W. 21W continued to steadily intensify due to low vertical wind shear. On August 27, at 12:00 UTC, the JMA upgraded 21W to a tropical storm, and named it Horangi. The JTWC followed suit 18 hours later and also upgraded Horangi to a tropical storm. As Horangi started to construct its central dense overcast (CDO), the JMA upgraded it to a severe tropical storm on August 29, at 00:00 UTC. At 12:00 UTC, a nascent eye could be observed in microwave imagery under the system's cold cloud tops. As a result, the JTWC upgraded Horangi to a typhoon, with the JMA doing the same six hours later. Due to a weakness in the subtropical ridge, Horangi started to move north-northwesterly, and eventually due north over the next few days. During this time, the typhoon was exposed to favourable conditions, such as low vertical wind shear and sea surface temperatures (SSTs) of over 30 °C (86 °F). This allowed the storm to rapidly intensify from August 30 to 31. On August 31, at 12:00 UTC, the JTWC assessed Horangi had become a Category 4-quivalent super typhoon. Soon after that, cold -75 °C (-103 °F) cloud tops formed a uniform ring around the typhoon's warm 20 °C (68 °F) medium-sized eye. This caused the JTWC to upgrade Horangi to a Category 5-equivalent super typhoon, and the JMA to assess Horangi to be a violent typhoon, on September 1, at 00:00 UTC. This made Horangi the first Category 5-equivalent typhoon and violent typhoon of the season. At this time, Horangi peaked with maximum 1-minute sustained winds of 260 km/h (160 mph) and a minimum central pressure of 910 mbar (26.87 inHg). In the late hours on the same day, concentric eyewalls were observed in microwave imagery, signifying the start of an eyewall replacement cycle (EWRC). This caused Horangi to start weakening, with warming cloud tops and its eye getting more irregular and cloud-filled. The typhoon lost its super typhoon status on September 2, at 06:00 UTC, according to the JTWC. As Horangi moved northwards and entered colder waters, it failed to significantly restrengthen after the completion of the EWRC by September 3. Horangi, with its new ragged and large eye, lost its major typhoon status on September 3, at 18:00 UTC. On the next day, Horangi encountered moderate to strong shear, which caused the system to eventually lost its typhoon status according to both agencies on September 5. As the storm's convection became displaced and asymmetric, the JMA then further downgraded Horangi from a severe tropical storm to a tropical storm on September 6. From September 6 to 9, Horangi's movement slowed down and stalled, and it performed a tight cyclonic loop due to it being stuck in a col temporarily. Both the JMA and the JTWC issued their final warnings on the system on September 10, before the system briefly turned extratropical and dissipated on the next day.
Notable stats: Horangi was the fourth super typhoon and the first Category 5-equivalent typhoon of the season.
Typhoon Lamyai (Liwayway)[]
| Max 1-min winds: | 105 kt (195 km/h) |
|---|---|
| Max 10-min winds: | 85 kt (160 km/h) |
| Min pressure: | 952 hPa (mbar) |
| ACE accumulated | 17.5925 |
| TD+ days | 11 days |
| TS+ days | 7.25 days |
| C1+ days | 5.75 days |
| C3+ days | 0.75 days |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | 71 |
| Damages | $252.5 million (USD) |
| Very Strong Typhoon (JMA) | |
|---|---|
| Category 3 typhoon (SSHWS) | |
  | |
| Duration | August 29 – September 9 |
| Peak intensity | 160 km/h (100 mph) (10-min); 952 hPa (mbar) |
On August 25, the JTWC started tracking a tropical disturbance developing within a monsoon trough, located 90 km (56 mi) to the northeast of Kosrae, Federated States of Micronesia. The disturbance moved west-northwest slowly. On August 26, as the disturbance was embedded in favourable conditions for development, the JTWC upgraded its probability of developing into a tropical cyclone within 24 hours from "low" to "medium". However, on the next day, the centre of the system suddenly weakened due to unexpected wind shear. The caused the agency to lower the disturbance's probability of developing into a tropical cyclone within 24 hours back to "low". Environmental conditions improved again on August 28. As a result, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) at 09:00 UTC that day, while the JMA upgraded the system from a low-pressure area to a tropical depression two hours later. At 18:00 UTC, the JTWC also upgraded the system to a tropical depression, with the designation 22W. 22W stagnated in its development over the next four days as it meandered over the open ocean. On September 1, at 00:00 UTC, both the JMA and the JTWC upgraded 22W to a tropical storm, with the former naming it Lamyai. Lamyai quickly strengthened due to favourable conditions, and it started constructing its central dense overcast (CDO). At 06:00 UTC, the storm passed 110 km (68 mi) to the southwest of Guam as an organising tropical storm. Six hours later, Lamyai was upgraded to a severe tropical storm by the JMA. By late September 1, Lamyai developed a nascent eye under microwave imagery. This prompted the JTWC to upgrade Lamyai to a typhoon at 00:00 UTC on the same day, while the JMA followed suit six hours later. Over the next two days, Lamyai moved generally westward steadily. The typhoon struggled to significantly intensify due to mild dry air intrusion and medium vertical wind shear. On September 3, at 00:00 UTC, as Lamyai entered the Philippine Area of Responsibility, the PAGASA named the storm Liwayway. Shortly after this, Lamyai attained its first peak over the Philippine Sea at 18:00 UTC on the same day, as a Category 2-equivalent typhoon, with maximum 1-minute sustained winds of 155 km/h (100 mph) and a minimum central pressure of 962 mbar (28.41 inHg). Lamyai then maintained its intensity up till its landfall over General Nakar, Quezon, Luzon on September 4 at 13:45 UTC. The mountainous terrain of Luzon weakened the system to a Category 1-equivalent typhoon. Four hours after its landfall, Lamyai emerged into the South China Sea, where it was exposed to highly favourable conditions for development, such as 5 to 15 knots of vertical wind shear, and sea surface temperatures of 30 °C (86 °F) to 31 °C (87.8 °F). This allowed the typhoon to rapidly develop on September 5 and 6. On September 6, at 12:00 UTC, Lamyai reached its second and highest peak as a Category 3-equivalent typhoon, with maximum 1-minute sustained winds of 195 km/h (120 mph) and a minimum central pressure of 952 mbar (28.11 inHg). During this time, Lamyai passed 80 km (50 mi) to the southwest of Hainan and entered the Gulf of Tonkin. The typhoon briefly weakened due to land interaction before it made landfall over Quỳnh Lưu, Nghệ An, Vietnam as a Category 2-equivalent typhoon on September 7, at 09:00 UTC. Lamyai rapidly weakened after its landfall, and it lost its typhoon status by late September 7 according to both agencies. The system weakened to a tropical depression on the next day, and the JTWC issued its last warning on the system by early September 8, when the storm was over Loas. Meanwhile, the JMA continued tracking the system till it dissipated on September 9, over Myanmar.
Lamyai brought severe impacts to both the Philippines and Vietnam. In the Philippines, approximately 2 million people in 18 provinces were affected by Lamyai, with most damage being attributed to the violent winds and torrential rain brought by the typhoon. Flooding was the most severe in the provinces of Laguna, Cavite, and Quezon, and over 20,000 hectares (49,400 acres) of farmland were inundated in these places. Overall, 21 people lost their lives in the Philippines, and economic damages amassed to ₱1.97 billion (US$33.7 million). Meanwhile, in Vietnam, Lamyai demolished houses, downed power lines, and caused flooding that forced large-scale evacuations in northern Vietnam. In the hard-hit Nghệ An, Thanh Hóa and Ninh Bình provinces, 309 homes were destroyed, and 2,316 more were damaged. Throughout the country, six hospitals and 250 dispensaries were damaged, while 76,135 dwellings were damaged. Throughout Vietnam, 25 people were killed, 19 were reported missing, 186 were injured, and at least 60,000 others were rendered homeless. Damage in the nation was estimated at 1.63 trillion VND (US$62 million).
Notable stats: Lamyai was the fourth-deadliest storm of the season.
Typhoon Barijat (Marilyn)[]
| Max 1-min winds: | 155 kt (285 km/h) |
|---|---|
| Max 10-min winds: | 115 kt (215 km/h) |
| Min pressure: | 892 hPa (mbar) |
| ACE accumulated | 42.1575 |
| TD+ days | 13.25 days |
| TS+ days | 12 days |
| C1+ days | 9.5 days |
| C3+ days | 3.75 days |
| SuperTY days | 2.25 days |
| C5 days | 1.5 days |
| Fatalities | 26 |
| Damages | $11.1727 billion (USD) |
| Violent Typhoon (JMA) | |
|---|---|
| Category 5 super typhoon (SSHWS) | |
  | |
| Duration | September 4 – September 17 |
| Peak intensity | 215 km/h (135 mph) (10-min); 892 hPa (mbar) |
On September 2, a broad area of low-pressure embedded in a monsoon trough that extended from the Caroline Islands to the International Date Line was designated by the JMA. The disturbance was located 140 km (87 mi) to the east-northeast of Kaginen in the Namu Atoll of the Marshall Islands. The disturbance then moved due west quickly and organised itself. On September 3, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the system, denoting a "high" chance for the system to develop into a tropical cyclone within 24 hours. On the same day, the JMA upgraded the storm low-pressure area to a tropical depression. On September 4, at 00:00 UTC, the JTWC also upgraded the system to a tropical depression, with the designation 23W. Six hours later, 23W was upgraded to Tropical Storm Barijat by the JMA. The JTWC also upgraded Barijat to a tropical storm at 18:00 UTC on the same day. On September 5, Barijat's development has temporarily halted as the system took considerable time to organise its broad and messy convection. The system managed to tighten its circulation on its next day, which resulted in a faster pace of intensification. The JMA upgraded Barijat to a severe tropical storm at 06:00 UTC on September 6. Meanwhile, the JTWC upgraded the system to a typhoon at 18:00 UTC. Three hours later, the JMA followed suit. At 22:00 UTC, Barijat made direct over Kagman, Saipan of the Northern Mariana Islands as a Category 1-equivalent typhoon. Barijat crossed the island in 15 minutes, and it continued its west-northwest trajectory after leaving the Northern Mariana Islands. On September 7, Barijat started to rapidly intensify due to favourable conditions. On September 8, at 00:00 UTC, the JTWC upgraded Barijat to a super typhoon, the fifth of the season. The agency then further upgraded the system to a Category 5-equivalent super typhoon six hours later. At the same time, the JMA assessed Barijat to have become a violent typhoon, the second of the season. Barijat's convection over its central dense overcast (CDO) continued to cool, and its eye maintained temperatures over 20 °C (68 °F). On September 9, at 00:00 UTC, the JTWC has assessed Barijat to have reached its peak intensity, with maximum 1-minute sustained winds of 285 km/h (180 mph) and a minimum central pressure of 892 mbar (26.87 inHg). Shortly after this peak, Barijat started to slowly weaken as it tracked westward and started an eyewall replacement cycle (EWRC). At 06:00 UTC on the same day, upon entering the Philippine Area of Responsibility, the PAGASA quickly named the typhoon Marilyn, and assessed the system to be a super typhoon. At 18:00 UTC, Barijat was no longer a Category 5-equivalent typhoon according to the JTWC, and it lost its super typhoon status 12 hours later. The typhoon continued to move west-northwest and slowly deteriorate due to dry air intrusion during the aforementioned EWRC. On September 11, Barijat entered the Luzon Strait, and it crossed the Babuyan Islands as a Category 2-equivalent typhoon at 18:00 UTC. Barijat then proceeded to stall over the South China Sea from September 12 to 14. The typhoon resumed its westward movement after that as it approached the coasts of Southern China. On September 15, at 17:00 UTC, Barijat passed within 80 km (50 mi) to the south of Hong Kong. It then made landfall over Jinwan, Zhuhai, Guangdong at 22:00 UTC on the same day, as a Category 1-equivalent typhoon. Barijat rapidly weakened over land, and it was downgraded to a tropical depression according to both the JMA and the JTWC on September 16, at 18:00 UTC. The JTWC issued its final warning on the system at that time, while the JMA continued tracking Barijat's remnants till it dissipated over Tuyên Quang, Vietnam on the next day.
Barijat brought severe impacts to Southern China, Hong Kong and Macau. In Hong Kong, the Hong Kong Observatory initiated Hurricane Signal No. 10 around 15:50 HKT (07:50 UTC), the first time since Typhoon Gosari in 2065. Serious flooding was reported in many seaside residential areas due to storm surge of up to 2.78 metres (9.1 ft), including Heng Fa Chuen, Tseung Kwan O South, Shek O and Lei Yue Mun. Total damages across the territory reached HK$6.38 billion (US$820 million). Meanwhile, in Macau, widespread power failure was recorded as about 12,000 homes lost power temporarily. In Coloane, a men lost his life after he was swept away by a rogue wave generated by Barijat. Total damage in Macau was estimated to be 1.64 billion patacas (US$205 million). Across the special administrative region, 18 injuries were reported and more than 2,300 people were evacuated. In Mainland China, Barijat caused the evacuation of over 1.37 million people across Guangdong. In Zhuhai, markets, schools and public transport were closed or limited from September 15 to 16. Near Yangchun, Guangdong, a landslide has buried parts of a mountain-side village, killing four in the process. In Shenzhen, the typhoon toppled 196 trees and caused the power to fail in nine locations. Across the whole China, 14 people lost their lives, and total economic losses were estimated to be CN¥70.14 billion (US$9.98 billion).
Notable stats: Barijat was the fifth super typhoon and the second Category 5-equivalent typhoon of the season. It is also the second-costliest storm and the third-largest ACE producer this season.
Severe Tropical Storm Lang-biang[]
| Max 1-min winds: | 65 kt (120 km/h) |
|---|---|
| Max 10-min winds: | 60 kt (110 km/h) |
| Min pressure: | 978 hPa (mbar) |
| ACE accumulated | 2.3 |
| TD+ days | 4.5 days |
| TS+ days | 2.5 days |
| C1+ days | 0.25 days |
| C3+ days | N/A |
| SuperTY days | N/A |
| C5 days | N/A |
| Fatalities | None |
| Damages | $700,000 (USD) |
| Severe tropical storm (JMA) | |
|---|---|
| Category 1 typhoon (SSHWS) | |
  | |
| Duration | September 8 – September 12 (Extratropical) |
| Peak intensity | 110 km/h (70 mph) (10-min); 978 hPa (mbar) |
On September 7, the JTWC noted on a developing subtropical disturbance located 390 km (242 mi) to the east of Chichijima in the Bonin Islands. The disturbance steadily developed, and the JMA designated it as a tropical depression at 20:00 UTC on the same day. An hour later, the JTWC initiated a Tropical Cyclone Formation Alert (TCFA) on the system. The agency then upgraded it to a subtropical depression, with the designation 24W, at 06:00 UTC on the next day. 24W first slowly moved to the north, then eventually to the northwest. On September 9, at 18:00 UTC, the JTWC upgraded 24W to a subtropical storm. Six hours later, the JMA upgraded 24W to a tropical storm instead, and named the system Lang-biang. On September 10, at 06:00 UTC, the JTWC noted on the tropical characteristics Lang-biang has acquired. This caused the agency to reclassify the system as a tropical storm. 12 hours later, the JMA upgraded Lang-biang to a severe tropical storm. Lang-biang continued to steadily intensify after that as it constructed its central dense overcast (CDO). The JTWC further upgraded it to a minimal Category 1-equivalent typhoon on September 11, at 06:00 UTC. Six hours later, the JTWC downgraded Lang-biang back to a tropical storm as the system's convection started to deteriorate due to wind shear. On the other hand, the JMA never upgraded Lang-biang to a typhoon. Lang-biang then recurved away from Japan over the next two days and rapidly weakened due to very high vertical wind shear bought by the westerlies. The system lost its tropical storm status on September 12 according to both agencies, and it underwent extratropical transition later on the same day.
Notable stats: Lang-biang is the only storm of the season to have a subtropical origin.