2024 Pacific typhoon season: Difference between revisions

2024 Pacific typhoon season
Season summary map
Seasonal boundaries
First system formed	May 23, 2024
Last system dissipated	Season ongoing
Strongest storm
Name	Yagi
• Maximum winds	195 km/h (120 mph) (10-minute sustained)
• Lowest pressure	915 hPa (mbar)
Seasonal statistics
Total depressions	24
Total storms	15
Typhoons	6
Super typhoons	1 (unofficial)[nb 1]
Total fatalities	999 total
Total damage	$25.8 billion (2024 USD)
Related articles
Timeline of the 2024 Pacific typhoon season 2024 Atlantic hurricane season 2024 Pacific hurricane season 2024 North Indian Ocean cyclone season
Pacific typhoon seasons 2022, 2023, 2024, 2025, 2026

The 2024 Pacific typhoon season is an ongoing event in the annual cycle of tropical cyclone formation in the western Pacific Ocean. It is the fifth-latest starting Pacific typhoon season on record. The season runs throughout 2024, though most tropical cyclones typically develop between May and October. The season's first named storm, Ewiniar, developed on May 25, and eventually intensified into the first typhoon of the season.

The scope of this article is limited to the Pacific Ocean to the north of the equator between 100°E and 180th meridian. Within the northwestern Pacific Ocean, there are two separate agencies that assign names to tropical cyclones which can often result in a cyclone having two names. The Japan Meteorological Agency (JMA)^{[nb 2]} will name a tropical cyclone if it has 10-minute sustained wind speeds of at least 65 km/h (40 mph) anywhere in the basin. The Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) assigns names to tropical cyclones which move into or form as a tropical depression in the Philippine Area of Responsibility (PAR), located between 135°E and 115°E and between 5°N–25°N, regardless of whether or not a tropical cyclone has already been given a name by the JMA. Tropical depressions that are monitored by the United States' Joint Typhoon Warning Center (JTWC)^{[nb 3][nb 1]} are given a number with a "W" suffix.

TSR forecasts Date	Tropical storms	Total Typhoons	Intense TCs	ACE	Ref.
Average (1991–2020)	25.5	16.0	9.3	301	[3]
May 7, 2024	25	15	7	225	[3]
July 5, 2024	24	14	7	211	[4]
August 7, 2024	24	14	7	177	[5]
Other forecasts Date	Forecast Center	Period	Systems		Ref.
January 15, 2024	PAGASA	January–March	0–2 tropical cyclones		[6]
January 15, 2024	PAGASA	April–June	2–4 tropical cyclones		[6]
June 26, 2024	PAGASA	July–September	6–10 tropical cyclones		[7]
June 26, 2024	PAGASA	October–December	4–7 tropical cyclones		[7]
2024 season	Forecast Center	Tropical cyclones	Tropical storms	Typhoons	Ref.
Actual activity:	JMA	23	15	6
Actual activity:	JTWC	17	12	7
Actual activity:	PAGASA	9	6	2

During the year, several national meteorological services and scientific agencies forecast how many tropical cyclones, tropical storms, and typhoons will form during a season and/or how many tropical cyclones will affect a particular country. These agencies included the Tropical Storm Risk (TSR) Consortium of University College London, PAGASA, Vietnam's National Center for Hydro-Meteorological Forecasting and Taiwan's Central Weather Bureau.

Tropical Storm Risk (TSR) released their first forecast on May 7, predicting below average activity with 25 named storms, 15 typhoons and 7 intense typhoons. This was primarily due to the dominant El Niño event at the time, which was expected to transition into a weak or moderate La Niña by mid-2024.^[3] TSR released their early July forecast on July 5, where they slightly decreased the amount of storms and typhoons, mentioning the same factors as their previous forecast.^[4] On August 7, TSR released their final forecast for the season, retaining the same number of storms. However, they further decreased the predicted ACE index, due to a slow start of the season and decreased tropical activity as of early August.^[5] Moreover, with the Pacific Decadal Oscillation being in a negative phase since the beginning of 2020, they also mentioned how this season could become the lowest five-year activity since 1965.^[5]

Costliest known Pacific typhoon seasons

Rank	Total damages	Season
1	≥ $38.96 billion	2019
2	≥ $37.53 billion	2023
3	≥ $31.54 billion	2018
4	≥ $26.41 billion	2013
5	≥ $25.2 billion	2024
6	≥ $20.79 billion	2012
7	≥ $18.77 billion	2004
8	≥ $18.36 billion	1999
9	≥ $17.69 billion	2016
10	≥ $15.1 billion	2017

The Pacific typhoon season began on May 23, when a tropical storm named Ewiniar formed southeast of Palau, marking it as the fifth-latest start of a Pacific typhoon season since reliable records began.^[8] Ewiniar tracked toward the Philippines, where it made nine landfalls in Homonhon Island; Giporlos, Eastern Samar; Basiao Island; Cagduyong Island; Batuan, Masbate; Masbate City; Torrijos, Marinduque; Lucena, Quezon and Patnanungan. It began to move over the warm tropical waters of Lamon Bay, where the JTWC and the JMA upgraded Ewiniar into a minimal typhoon. Ewiniar began transitioning to an extratropical cyclone while it is 719 km (447 mi) east-northeast of Kadena Air Base in Okinawa, Japan. On June 6, another extratropical cyclone^[which?] would absorb the remnants of Ewiniar, just off the coast of Alaska. On May 30, another tropical depression formed southeast of Haikou, China. The next day, at 03:00 UTC, JTWC designated the disturbance as Tropical Depression 02W. A few hours later, JMA assigned the name Maliksi as they upgraded 02W into a tropical storm. Shortly after being named, on May 31, Maliksi made landfall in Yangjiang, Guangdong. the JMA and JTWC discontinued warnings as Maliksi moved inland and dissipated on June 2. No storms formed in June for the first time since 2010.

After many weeks of inactivity, on July 13, a tropical depression formed east of Vietnam, designated as 03W. Shortly after, it tracked into Vietnam, dissipating soon after. On July 19, two tropical disturbances recognized by the JTWC: one southeast of Manila and another east of Palau. Soon after, both disturbances developed into a depression, being named by PAGASA. The first one, west of Batangas, was named Butchoy while the second, east of Virac, was called Carina. Later that day, the JTWC followed suit, designating them both as depressions, with Butchoy being 04W and Carina as 05W. The next day, the easternmost disturbance, Carina was named Gaemi by the JMA. On July 21, Butchoy also intensified into a tropical storm, assigning the name Prapiroon from the JMA. Prapiroon moved through the South China Sea as a mild tropical storm before landfall over Wanning, Hainan. Prapiroon moved through Gulf of Tonkin, where it further intensified into a severe tropical storm. Early on July 23, Prapiroon made its second and final landfall in Quảng Ninh, Vietnam. Rapid weakening ensued as Prapiroon moved inland and dissipated on the next day.

Being in a favorable environment in the Philippine Sea, Gaemi continues to strengthen into a severe tropical storm as it moves northeastward slowly. Early the next day, JMA upgraded Gaemi into a typhoon, the second to occur this season. JTWC also followed suit and upgraded Gaemi into a Category-1 typhoon. Owing to its warm sea surface temperature and low vertical wind shear, on July 24, Gaemi rapidly intensified into a Category-4 typhoon, with 10-minute sustained winds of 165 km/h (105 mph), equivalent to a very strong typhoon category by the JMA. Gaemi stalled and executed a counterclockwise loop near the coast, slightly weakening into a Category-3 typhoon. Overnight, Gaemi made landfall over Hualien, Taiwan at that intensity. The country's mountain ranges tore apart the storm's structure, causing Gaemi to weaken further into a Category-2 typhoon. The storm accelerated across the island and emerged into the Taiwan Strait, six hours after landfall. The next day, Gaemi made its final landfall at Xiuyu, Putian at Fujian Province as a weakening tropical storm. Moving inland, the storm rapidly weakened until it dissipated on July 27.

Even though Gaemi never made landfall in the Philippines, the storm's moisture would enhance the southwest monsoon. Heavy rainfalls were felt over Luzon and some parts of Visayas, leaving each region flooded. Overall, Gaemi caused 126 fatalities and $266 million worth of damages throughout its track.

On August 3, a low-pressure area developed east of Kadena Air Base. At 00:00 UTC, JMA recognize the disturbance as a depression. However, it downgraded to a remnant low on August 7. The convection later meandered south of Ryukyu Islands for a few days before JMA was reclassified again as a depression on August 11. JMA issued a gale warning the next day, citing that it would intensify in the following days. JTWC later followed suit and upgraded into a tropical depression, 08W. On August 13, the depression became a tropical storm, receiving the name Ampil from the JMA. Ampil gradually intensified in the Pacific Ocean, becoming a severe tropical storm. JMA upgraded Ampil into a typhoon two days later, and the JTWC classified it as a Category 2-equivalent typhoon. The next day, it strengthened into a Category 4-equivalent typhoon. The typhoon passed just south of Greater Tokyo Area before weakening and transitioning to an extratropical cyclone.

On August 5, a low-pressure area was formed in Bonin Islands. The disturbance was in an environment with low to moderate wind shear and warm SSTs. JTWC later classified the disturbance into a depression the next day, giving the designation 06W. Early on August 8, JMA upgraded the depression into a storm, naming it Maria. The storm further strengthened into a severe tropical storm on the same day. At the same time, JTWC reported that Maria had rapidly intensified into a typhoon due to strong equatorward and poleward outflow. However, on August 9, Maria weakened into a tropical storm as it moved northeastwards. On August 10, another area of low pressure formed just southeast of Maria. The JTWC would classify the disturbance as a subtropical depression in their next bulletin. Despite being in a marginal environment and high wind shear, JMA upgraded into a tropical storm, assigning the name Son-Tinh. The next day, JTWC announced that Son-Tinh became tropical, designating it as 07W. Son-Tinh weakened back into a depression before it dissipated on August 14.

On the morning of August 12, Maria made landfall in Iwate Prefecture as a tropical storm, bringing strong winds and dumping heavy rains in northern Japan. Maria then weakened into a depression after moving inland. The storm entered through the Sea of Japan, weakening further the next day. The JTWC issued its final warning after Maria was last noted west-northwest of Misawa, Japan. JMA continued to track as a depression before they issued their final warning at 04:15 UTC.

Activity became more active when an area of convection was formed on August 12 near the southwest of a nearby storm Son-Tinh. JMA would immediately recognize the disturbance as a depression. The next day, JTWC went to give its identifier of the depression, which was Tropical Depression 09W. Just like Ampil, on August 13, 09W intensified into a tropical storm, attaining the name Wukong from the JMA. Wukong was short-lived due to its poorly organized cloud tops. JTWC made its final warning on Wukong as it moved through cooler waters and dissipated on August 15.

On August 17, JMA recognized a tropical depression that formed east of Taiwan. The next day, PAGASA declared the system a tropical depression, assigning the name Dindo. The depression was named Jongdari three hours later upon formation. JTWC later followed suit and upgraded into a tropical storm, with the designation of 10W. However, it did not last long and weakened into a depression as it nears the Korean Peninsula. On August 21, JMA and JTWC reported that Jongdari had dissipated as its low-level circulation center faded when it moved over land, after Jongdari, a low-pressure area formed in the Northern Mariana Islands on the same day. The system intensified into a tropical storm the next day, and the name Shanshan was picked up by the JMA. JTWC gave the designation of 11W to Shanshan.

Shanshan later strengthened into a Category 1-equivalent typhoon. It remained at that intensity as it battled through wind shear. As it nears the Amami Islands, it strengthened into a Category 4-equivalent typhoon. The approach of the typhoon caused the issuance of a special warning system in Kagoshima Prefecture, the first time issued in the area since Nanmadol of 2022. Around 08:00 JST on August 29, Shanshan made landfall near Satsumasendai, making the third tropical cyclone impact mainland Japan this season. Rapid erosion later ensued as it moved eastward over inland. Shanshan heads over Seto Inland Sea before it makes another landfall in Shikoku on the next day. Shanshan's convection began to be disorganized, causing it to weaken into a remnant low. However, it regained back into a depression as it moved east southeastward through open waters. JMA continued to track Shanshan until it dissipated on September 1.

Nearing the end of August, a tropical disturbance formed near Palau. On the same day, JMA started to issue advisories for the system as a depression. As it entered the Philippine Area of Responsibility (PAR), the agency gave it the name Enteng on the first day of September. JTWC followed suit and was classified as a depression, with its designation of 12W. At 21:00 JST (13:00 UTC), JMA developed into a tropical storm, naming the system Yagi. The storm made its first landfall in Casiguran in the province of Aurora. The mountainous terrain of the Cordillera Central had made Yagi weakened as it moved inland. It left PAR on early September 4 as it continues to intensify in the South China Sea.

Yagi later strengthened into a typhoon due to its highly favorable environmental conditions. The following day, it rapidly intensified, developing a distinct eye and briefly reaching Category 5-equivalent super typhoon status as it approached Hainan. The whole cloud system of Yagi covered the entire South China Sea. Although Yagi slightly weakened, it made its second landfall over Wenchang City in Hainan. The storm then moved over Haikou, China, and continued to make another landfall in Xuwen County, Guangdong. Afterward, Yagi entered the open waters of the Gulf of Tonkin.

Yagi became one of only four Category-5 typhoons recorded in the South China Sea, alongside Pamela (1954), Rammasun (2014), and Rai (2021). It also marked the most powerful typhoon to strike Hainan in autumn since Typhoon Rammasun in 2014. On September 7, Yagi underwent a period of reorganization and regained Category 4 status before making a historic landfall between Haiphong and Quang Ninh in Vietnam. Upon landfall, Yagi became the strongest storm to impact Northern Vietnam. The typhoon then weakened rapidly into a remnant low as it moved inland, dissipating on September 8. Even after dissipation, it still wreaked havoc, bringing heavy floods to Myanmar, Laos, and Thailand.

While Yagi was on its way to making landfall in the Philippines, JTWC announced another formation of a tropical disturbance in the open Pacific Ocean on September 2. JMA also started issuing advisories, and it was recognized as a tropical depression in the same location. Two days later, as JTWC upgraded it into a depression, it received its designation as 13W. A day later, JMA reported that 13W developed into a tropical storm, giving the name Leepi as the twelfth named storm of this season. Leepi then accelerated northeastwards before it became an extratropical cyclone on September 6.

On September 9, a tropical depression formed over the Micronesian Islands. The following day, the JTWC designated it as 14W. As it moved over Guam, 14W intensified into a tropical storm and was named Bebinca by the JMA. Despite encountering dry air, Bebinca strengthened as it began its northwestward movement. At 18:00 PHT on September 13, Bebinca entered the Philippine Area of Responsibility and was named Ferdie by PAGASA. Bebinca later strengthened into a minimal typhoon on the next day. On September 16, Bebinca landed in Shanghai, China as a weakening Category-1 typhoon, and became the strongest typhoon to hit Shanghai since Typhoon Gloria of 1949.

As Bebinca moved toward eastern China, two tropical depressions formed in the Pacific on September 15—one near Guam and another within the Philippine Area of Responsibility (PAR). The JTWC designated the depression near Guam as 15W. It soon intensified into a tropical storm and was named Pulasan by the JMA. The PAR tropical depression was given the name Gener by PAGASA. At 02:00 PHT the following day, Gener made landfall over Palanan, Isabela. The storm continued to move westward over Northern Luzon, maintaining its strength as a depression. Meanwhile, Pulasan briefly entered the PAR at 18:30 PHT (10:30 UTC) and was assigned the name Helen. Gener was upgraded by the JTWC into a tropical depression, getting the designation 16W. On September 19, 16W was upgraded to a tropical storm and named Soulik by the JMA. Soulik made landfall over Vĩnh Linh District, Quảng Trị, in Vietnam. Meanwhile, Pulasan also made landfall over Zhoushan, China, similar to where Bebinca had made landfall three days earlier. After that, it made a second landfall over Shanghai, marking the first time since reliable meteorological records exist that two typhoons make landfall over Shanghai with only two days in between.

On September 20, a low-pressure area formed over Northern Luzon. The JTWC later designated the disturbance as Invest 90W upon its formation. Being inside the PAR, PAGASA initiated advisories and named the system Igme. The JTWC soon upgraded it into a tropical depression, designating it as 17W. Igme later curved southwestwards, passing closely to Taiwan. The storm later dissipated on September 22 after topographical interaction and high vertical wind shear had weakened the system significantly.

Typhoon (JMA)
Category 2 typhoon (SSHWS)
Duration	May 23 – May 30
Peak intensity	140 km/h (85 mph) (10-min); 970 hPa (mbar)

On May 21, the Joint Typhoon Warning Center (JTWC) began tracking an area of atmospheric convection 441 km (274 mi) southeast of Palau, noting that the system was moving northwestward towards an environment favorable for tropical cyclogenesis.^[9] In the following day, the disturbance became a tropical depression.^[10] The depression would later enter PAR, assigning the name Aghon, a replacement name for Ambo.^[11] At 18:00 UTC, the JTWC designated the depression as 01W, based on surface observations from Guiuan.^[12] Aghon made landfall over Homonhon Island and subsequently Giporlos, Eastern Samar in the early morning of May 25 (PHT).^[13] It made five more landfalls over Basiao and Cagduyong Islands of Catbalogan; Batuan in Ticao Island; Masbate City; and Torrijos, Marinduque.^[14] At 12:00 UTC, 01W intensified into a tropical storm while it was still in Tayabas Bay, prompted the JMA to name the storm as Ewiniar.^[15] In the morning of May 26 (PHT), the storm made its eighth landfall over Lucena, Quezon in Luzon island.^[14] Ewiniar later intensified into a typhoon over Lamon Bay^[16] The storm made its final landfall over Patnanungan in the Polillo Islands.^[17] The typhoon left the PAR on May 29 and continued to weaken due to subsidence around the mid-latitude.^[18][19] On May 30, Ewiniar transitioned into an extratropical cyclone south-southwest of Yokosuka, Japan^[20] Then at 18:00 UTC on May 31, Ewiniar entered the baroclinic zone and an area of high wind shear.^[21]

Typhoon Ewiniar resulted in ₱1.03 billion (US$20.88 million) in total damages in the Philippines, with ₱85.63 million (US$1.74 million) to agriculture and ₱942.55 million (US$19.14 million) to infrastructure, while also causing six deaths, injuring eight people, and impacting around 152,266 others. In Japan, heavy rainfall was observed in several regions, with a maximum of 52.5 mm (2.07 in) of rain being recorded in Miyake, Tokyo.^[22][23]

Tropical storm (JMA)
Tropical depression (SSHWS)
Duration	May 30 – June 1
Peak intensity	65 km/h (40 mph) (10-min); 998 hPa (mbar)

On May 29, the JTWC began tracking an area of convection located 406 km (252 mi) southeast of Haikou, China. Being in an area of warm waters and low vertical shear and having southerly outflow, the system sustained a weak circulation, inhibited from development by another area of convection near Mainland China.^[24] It was recognized as a low-pressure area by the Japan Meteorological Agency (JMA) early the next day,^[25] before the agency upgraded it to a tropical depression at 06:00 UTC.^[26] Later that day, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the depression since it had rapidly developed.^[27] At 00:00 UTC the next day, the JTWC upgraded the system into a tropical depression, designating it as 02W.^[28] Later, the JMA upgraded it into a tropical storm, and it was given the name Maliksi.^[29] However, the JTWC reported that it did not intensify into a tropical storm as it was disorganized, with the circulation elongating.^[30][31] At 21:00 UTC on May 31, the JTWC discontinued warnings on the system as it made landfall in Yangjiang, Guangdong.^[32] Soon after, the JMA last noted Maliksi as a depression on June 1 before weakening further into a low-pressure area the next day, as it tracked inland.^[33][34][35]

On May 30, the Hong Kong Observatory issued a No. 1 standby signal as the depression neared Hong Kong.^[36] The next day, it upgraded the warnings into a No. 3 Strong Wind signal.^[37] Although it was likely to not directly affect Taiwan, the Central Weather Administration noted that Maliksi's remnants were likely to merge with a frontal system and bring heavy rains to Taiwan over the weekend.^[38] In Macau, the storm caused unstable weather, with the Meteorological and Geophysical Bureau issuing Typhoon Signal No. 3.^[39][40] In China, torrential rainfall occurred, peaking at 272.3 mm (10.72 in) somewhere in the Leizhou Peninsula. Additionally, heavy rain was recorded in Fujian, Zhejiang and Jiangxi.^[41]

Tropical depression (JMA)
Tropical depression (SSHWS)
Duration	July 13 – July 15
Peak intensity	55 km/h (35 mph) (10-min); 1000 hPa (mbar)

On July 13, the JTWC began tracking an area of convection 423 mi (682 km) east-southeast of Da Nang, Vietnam. At the time, the disturbance was in a marginal environment for development, with high vertical wind shear offsetting good divergence aloft alongside warm sea surface temperatures.^[42] At 06:00 UTC of that day, the JMA designated the system as a tropical depression.^[43] The JTWC then issued a TCFA on the system the next day, noting its symmetrical center had improved as it moves northwest, though convection was disorganized.^[44] By 18:00 UTC the next day, the JTWC upgraded the system into a tropical depression, designating it 03W.^[45] However, they issued their last warning on the depression early the next day as it moved over Vietnam and rapidly weakened.^[46] Later that day, the JMA stopped tracking the depression as it dissipated.^[47]

Severe tropical storm (JMA)
Tropical storm (SSHWS)
Duration	July 19 – July 24
Peak intensity	110 km/h (70 mph) (10-min); 980 hPa (mbar)

On July 15, the JTWC started to monitor a persistent area of convection roughly 623 km (385 mi) southeast of Manila, Philippines. At that time, the disturbance was in a favorable environment for development, with warm 29–30 °C (84–86 °F), sea surface temperatures, low wind shear and good equatorial outflow.^[48] At 06:00 UTC the same day, the JMA designated the system as a low-pressure area.^[49] Shortly after, the JMA designated it as a tropical depression.^[50] The PAGASA declared the system a tropical depression a few hours later. Since the storm formed within the Philippine Area of Responsibility, the agency named it Butchoy.^[51] The JTWC began issuing advisories on the system, classifying it as 04W.^[52] It intensified into a tropical storm and was named Prapiroon by the JMA on July 21.^[53][54] A nascent eye feature became visible on microwave satellite imagery.^[55][56] The center of Prapiroon made landfall near Wanning, Hainan, with 1-minute sustained winds of 95 km/h (60 mph) on July 22.^[56] After making landfall, the storm maintained its well-defined eye while moving across central Hainan.^[57] Prapiroon soon encountered high wind shear and a dry environment,^[58] and by 6:30 a.m. local time on July 23, it made its second landfall in Quảng Ninh, Vietnam.^[59][60] After the system moved inland, both the JMA and the JTWC ceased monitoring it on July 24.^[61][62]

Typhoon Gaemi and Prapiroon, along with its precursor, significantly impacted the southwest monsoon over the Philippines, leading to heavy rainfall that caused 23 deaths, 9 people missing, and US$18.9 million in damages across several countries.^[63][64][65]

Very strong typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	July 19 – July 29
Peak intensity	165 km/h (105 mph) (10-min); 940 hPa (mbar)

On July 17, the JMA reported that a low-pressure area had formed east of Palau.^[66] Shortly after, both the JMA and the JTWC followed suit and upgraded the tropical depression,^[50] with the latter designating the system as 05W.^[67] The PAGASA followed suit a few hours later, recognizing the system as a tropical depression and naming it Carina.^[68] Early the next day, the depression intensified into a tropical storm, and was given the name Gaemi by the JMA.^[69] Due to a weak steering environment between the subtropical ridge to the northwest and east, the JTWC upgraded Gaemi to minimal typhoon around 21:00 UTC that day.^[70] On July 24, Gaemi later rapidly intensified and peaked at Category 4-equivalent intensity on the Saffir-Simpson scale at 21:00 UTC on 23 July, with 1-minute sustained winds of 230 km/h (145 mph) by the JTWC, 10-minute sustained winds of 165 km/h (105 mph) by the JMA, and a central pressure of 940 hPa (27.76 inHg).^[71][72] After stalling and executing a tight counter-clockwise loop near the coast,^[73] Gaemi slightly weakened into a below-equivalent typhoon status due to land interaction before it made landfall on the northeastern coast of Taiwan on July 24.^[74] Gaemi accelerated as it moved across the island and emerged into the Taiwan Strait just six hours after making landfall.^[75] Soon after,^[76] the JTWC ceased issuing advisories on the system as it made its final landfall at Xiuyu, Putian in Fujian Province.^[77] Once inland, the JMA downgraded Gaemi into a tropical depression on July 27^[78] and continued tracking the system until it dissipated at 18:00 UTC of July 29.^[79]

The southwest monsoon, combined with Tropical Storm Prapiroon, brought heavy rains to southern and northern Luzon, triggering widespread flash floods that resulted in at least 126 deaths and caused damage estimated at US$304 million across several countries.^[80][81][82]

Very strong typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	August 4 – August 19
Peak intensity	155 km/h (100 mph) (10-min); 950 hPa (mbar)

On August 3, the JTWC began tracking an area of convection 976 km (606 mi) east of Kadena Air Base on August 3.^[83] At 18:00 UTC the same day, the JMA designated the system as a low-pressure area.^[84] However, the following day, the system was upgraded to a tropical depression.^[85] The depression weakened and was last noted by the JMA on August 7.^[86] The disturbance later meandered south of the Ryukyu Islands for a few days before it was re-designated by the JMA as a tropical depression on August 11.^[87] A few hours later, they recognized the system as a tropical depression, designating it as 08W.^[88] Soon after, the JMA noted that it had intensified into a tropical storm and named it Ampil.^[89] The JMA then reported that Ampil had intensified into a typhoon due to warm sea surface temperatures and low vertical wind shear on August 15.^[90] The JMA reported that Ampil reached its peak intensity at 12:00 UTC that day with 10-minute sustained winds of 155 km/h (100 mph) and a central pressure of 950 hPa (28.05 inHg) before making its closest approach to Japan, and transitioned into an extratropical low on August 19.^[91]

Ampil brought strong winds and coastal waves to western Alaska, while Tokyo experienced minimal damage according to NHK, although Kanagawa Prefecture saw several injuries; the remnants of Ampil also contributed to an atmospheric river as its moist core flowed into a low-pressure system, ultimately being absorbed into the Pacific jet stream and anticipated to impact California.^[92]

Severe tropical storm (JMA)
Category 1 typhoon (SSHWS)
Duration	August 5 – August 14
Peak intensity	100 km/h (65 mph) (10-min); 969 hPa (mbar)

On August 5, the JMA stated that a tropical depression had formed.^[93] Later that day, the JTWC began tracking it, noting the depression was in an environment with low to moderate wind shear, warm sea surface temperatures, and good equatorward outflow aloft.^[94] At 09:00 UTC on August 6, the JTWC issued a TCFA on the disturbance, which was located 423 mi (682 km) north-northwest of Iwo Jima, along the eastern periphery of the monsoon gyre,^[95] prior to it being designated as 06W.^[96] The development of a central dense overcast and a ragged eye feature signified its intensification into a tropical storm,^[97] leading the JMA to name it Maria on August 7.^[98] Maria then turned northeastward,^[99] and intensified into a severe tropical storm on August 8 due to a favorable environment for development.^[100] Concurrently, the JTWC then reported that Maria had rapidly intensified into a minimal typhoon due to strong equatorward and poleward outflow.^[101] However, Maria's wind field became more asymmetric, with its associated convection shifting northward,^[102] causing Maria to weaken into a tropical storm on August 9.^[103] Around 00:00 UTC on August 12, the storm made landfall Ōfunato,^[104] a city in Iwate Prefecture, Japan with winds of 85 km/h (50 mph) before traversing northern Honshu and emerging into the Sea of Japan.^[105] The JMA continued to monitor the system until it was last noted at 18:00 UTC on August 14.^[106]

Record-breaking rainfall in Iwate Prefecture, with 19 inches (482.6 mm) in Kuji and 12.6 inches (320.0 mm) in Otsuchi—nearly double the average for August—led to controlled releases from the Taki Dam in Kuji, necessitating the evacuation of 8,300 people and the issuance of the highest evacuation alert level, though no damage or injuries were reported in association with Maria.^[107]

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	August 10 – August 14
Peak intensity	65 km/h (40 mph) (10-min); 992 hPa (mbar)

On August 10, the JMA noted that a tropical depression had formed southeast of Severe Tropical Storm Maria.^[108] A few hours later, the JTWC began tracking the system, noting that it could transition into a tropical cyclone despite intense wind shear.^[109] Early the next day, they noted that the depression had transitioned into a subtropical cyclone.^[110] As a result, a few hours later, the JMA named it Son-Tinh.^[111] The next day, the JTWC noted that it had transitioned into a tropical storm, designating it 07W.^[112] Soon after, the low-level circulation center became fully exposed with no deep convection existing near the center.^[113] On August 13, Son-Tinh turned northwest along the western edge of a subtropical ridge.^[114] Both the JMA and the JTWC stopped monitoring it as a tropical depression that day,^[115] though the JMA continued to track it until it was last noted the following day.^[116]

Tropical storm (JMA)
Tropical depression (SSHWS)
Duration	August 12 – August 15
Peak intensity	65 km/h (40 mph) (10-min); 1002 hPa (mbar)

On 12 August, the JMA noted that a tropical depression formed southwest of Tropical Storm Son-Tinh.^[117] A few hours later, strong convection south of the system's low-level circulation center consolidated, which prompted the JTWC to issue a TCFA for the disturbance.^[118] Soon after, they recognized the system as a tropical depression, designating it as 09W.^[119] Satellite imagery revealed that a central dense overcast obscured the center, leading to the depression strengthening into a tropical storm named Wukong by the JMA,^[120] although moderate vertical wind shear displaced the deep convection to the southeast.^[121][122] Wukong then shifted northwestward, following the eastern edge of a subtropical ridge, while also being affected by the shear and outflow from Typhoon Ampil to the southwest.^[123] On August 15, both the JMA and the JTWC ceased monitoring the system, with the JMA reporting that Wukong had transitioned into an extratropical low due to moderate vertical wind shear and cooler sea surface temperatures.^[124][125]

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	August 17 – August 21
Peak intensity	75 km/h (45 mph) (10-min); 999 hPa (mbar)

On August 17, a low-pressure area east of Taiwan developed into a tropical depression.^[126][127] Soon after the development of a low-level circulation center and deep convection, the JTWC issued a TCFA for the disturbance.^[128] A few hours later, PAGASA declared the system a tropical depression and named it Dindo,^[129] while the JMA reported it had intensified into a tropical storm and named it Jongdari,^[130] and the following day, the JTWC recognized it and designated it as 10W.^[131] Jongdari became devoid of convection as it was displaced from its exposed low-level circulation center and turned north-northeastward along the western edge of a subtropical ridge.^[132] Jongdari then weakened as it moved into the Yellow Sea and made landfall over the Korean Demilitarized Zone on August 20 before emerging into the Sea of Japan.^[133][134] The JTWC assessed the cyclone as having dissipated and ceased issuing advisories on the system,^[135] while the JMA continued to monitor the system until it was last noted on August 21.^[136]

In some parts of the southern islands of Jeju, Jongdari accumulated 60–130 millimetres (2.4–5.1 in) of rain as it moved closer to the coast.^[137]

Very strong typhoon (JMA)
Category 4 typhoon (SSHWS)
Duration	August 21 – September 1
Peak intensity	175 km/h (110 mph) (10-min); 935 hPa (mbar)

On August 20, the JMA reported that a low-pressure area had formed near the Mariana Islands.^[138] At midnight on August 21, both the JMA and the JTWC upgraded the tropical depression, with the latter designating the system as 11W.^[139][140] Shortly after, the depression intensified into a tropical storm and was named Shanshan by the JMA due to low vertical wind shear and warm sea surface temperatures.^[141] A ragged eye-like feature appeared on satellite imagery, and on August 24,^[142] both the JMA and the JTWC upgraded it to a minimal typhoon.^[143] The JMA reported that Shanshan reached its peak intensity at 15:00 UTC on August 27, with 10-minute sustained winds of 175 km/h (110 mph) and a central pressure of 935 hPa (27.61 inHg).^[144] Shanshan then turned northward and made landfall near Satsumasendai in Kagoshima Prefecture on August 29.^[145][146] It then turned eastward along the northern periphery of a subtropical high,^[147] quickly crossed the Seto Inland Sea, and made landfall over the northern tip of Shikoku on August 30.^[148] Shanshan's circulation later diminished as its LLCC became disorganized.^[149] However, convection slightly increased after six hours as Shanshan's circulation moved back over open water and began moving east-southeastward, causing to regenerate back to a depression.^[150][151] The JMA continued to monitor the system until it dissipated at 18:00 UTC that day.^[152]

The JMA issued special weather warnings for Kagoshima Prefecture, marking the first such emergency alert since Typhoon Nanmadol in 2022.^[153] Shanshan caused six fatalities and damaged hundreds of structures throughout Japan.^[154] In response to the severe weather, evacuation orders were issued for 996,299 people in Miyazaki Prefecture and 982,273 people in Kagoshima Prefecture.^[155]

Violent typhoon (JMA)
Category 5 super typhoon (SSHWS)
Duration	August 31 – September 8
Peak intensity	195 km/h (120 mph) (10-min); 915 hPa (mbar)

On August 30, the JMA reported the formation of a low-pressure area approximately 540 km (330 mi) northwest of Palau.^[156][157] This broad low-pressure system began to organize and developed into a tropical depression on August 31.^[158] The following day, PAGASA designated the system as a tropical depression and named it Enteng, as it formed within the Philippine Area of Responsibility.^[159] Shortly after, the system was classified as Tropical Depression 12W.^[160] As it intensified into a tropical storm, the JMA named it Yagi.^[161][162] At 14:00 PHT (06:00 UTC) on September 2, Yagi made landfall in Casiguran, Aurora.^[163] Early the next day, both the JMA and the JTWC upgraded the storm to a typhoon as satellite imagery revealed the formation of an eye. On September 5, Yagi reached peak intensity as a Category 5-equivalent super typhoon, with 1-minute sustained winds of 260 km/h (160 mph) and a central pressure of 915 mbar (27.0 inHg).^[164] It made landfall in Wenchang City, Hainan, and passed directly over Haikou, China, before moving into the open waters of the Gulf of Tonkin.^[165] On September 7, Yagi reorganized and restrengthened into a Category 4-equivalent typhoon before making its final landfall over Haiphong and Quảng Ninh, Vietnam.^[166] It continued to weaken rapidly as it moved southwest along the southeastern edge of a mid-level subtropical high,^[167] becoming a tropical depression on September 8. The JMA monitored Yagi until it was last noted at 18:00 UTC that day.^[168]

Yagi, combined with the effects of the southwest monsoon, resulted in at least 16 deaths, 15 injuries and 21 missing people in the Philippines.^[169] Yagi also caused extensive damages, landslides and floods in Vietnam, Thailand and Myanmar and left more than 500 people dead.^[170]

Tropical depression (JMA)
Subtropical depression (SSHWS)
Duration	September 1 (Entered basin) – September 8
Peak intensity	55 km/h (35 mph) (10-min); 1004 hPa (mbar)

On September 1 at 21:00 UTC, the remnants of Hurricane Hone moved into the basin from the Central Pacific about 280 km (150 nmi; 175 mi) to the southwest of Midway Atoll,^[171][172] where it was classified as a tropical depression by the JMA and as a subtropical depression by the JTWC the next day.^[173] Soon after, Hone began exhibiting a highly asymmetric convective structure, characterized by convective bands encircling a broad center, while being located under a deep subtropical trough with low to moderate vertical wind shear.^[174][175] The JTWC stopped tracking it on September 4, as it had dissipated,^[176] while the JMA continued to monitor the system until it was last noted at 06:00 UTC on September 8.^[177]

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	September 2 – September 6
Peak intensity	65 km/h (40 mph) (10-min); 1002 hPa (mbar)

On September 2, the JMA noted that a tropical depression had formed over the open Pacific.^[172] Two days later, the JTWC designated the system 13W. A day later, JMA reported that it intensified into a tropical storm, assigning the name Leepi. Although the storm was in a high wind shear and unfavorable environment, Leepi continued to maintain that intensity as it accelerated northeastward. JTWC later announced its final warning on September 6 as the system transitioned to an extratropical cyclone. The JMA issued its final advisory on 18:00 UTC of September 6.^{[citation needed]}

Typhoon (JMA)
Category 1 typhoon (SSHWS)
Duration	September 9 – September 18
Peak intensity	140 km/h (85 mph) (10-min); 965 hPa (mbar)

On September 9, a tropical depression formed near the Micronesian Islands. The next day, the JTWC started issuing warnings on the depression, designating it as 14W. As it moved towards Guam, the JMA reported 14W intensified to a tropical storm, naming it Bebinca. As it passes close to Guam, Bebinca further intensified to a severe tropical storm despite of dry air impacting it from the western side. On September 13, the JMA reported that the storm had weakened to a tropical storm due to its near-surface circulation being fully exposed and its banding being fragmented along the northern edge.^[178][179] By 18:00 PHT (10:00 UTC), Bebinca had entered the Philippine Area of Responsibility and PAGASA subsequently assigned it the name Ferdie.^[180] Bebinca then shifted northwestward as JMA reported that the storm had regained back to severe tropical storm status.^[181] On September 14, JMA and JTWC upgraded it to a minimal typhoon as it moved across the Ryukyu Islands.^[182] It made landfall in Shanghai, China, and became the strongest storm to make landfall in Shanghai since Typhoon Gloria of 1949.^[183] Shortly after landfall, the JTWC discontinued warnings on the system.^[184]

Bebinca became the second storm to hit China within a few weeks, following Typhoon Yagi's landfall on Hainan Island in the southern part of the country.^[185] At least 30,000 households lost power.^[186] Four homes were damaged, over 10,000 trees were damaged or uprooted and 53 hectares (132 acres) of farmland were flooded.^[187] In China, two people were killed, while one person was injured.^[188] The storm also left six people dead, eleven others injured and two people missing in the Philippines.^[189]

Tropical storm (JMA)
Tropical depression (SSHWS)
Duration	September 15 – September 20
Peak intensity	65 km/h (40 mph) (10-min); 992 hPa (mbar)

On September 15, a tropical depression formed over the seas east of the Philippines. As it formed inside the Philippine Area of Responsibility, PAGASA assigned it the name Gener at 05:00 PHT (21:00 UTC).^[190][191] The next day, Gener made landfall over Palanan, Isabela.^[192] On the early hours of September 18, Gener exited the PAR. Later in the day, while its circulation remains elongated orienting from the coast of Hainan to inland Vietnam, the JTWC designated Gener as 16W as it consolidates further into one system.^[193][194] On September 19, Gener was upgraded into a tropical storm and assigned the name Soulik by the JMA. Soulik made landfall in Vĩnh Linh District, Quảng Trị, Vietnam, at around 2 p.m. local time that day,^[195] after which the JTWC discontinued warnings for the system.^[196] Soulik quickly weakened to a tropical depression due to land interaction,^[197] and the JMA continued to monitor the system until it dissipated on September 20.^[198]

Soulik strengthened the southwest monsoon, which caused flooding that affected at least 9,000 people in Palawan.^[199] The storm, along with Bebinca and Pulasan, was blamed for a total of 24 deaths, 13 injuries and 12 missing across the Philippines.^[200] The arrival of the storm has led to evacuations in central Vietnam, just days after Typhoon Yagi.^[201] Quảng Bình province has moved nearly 900 households—over 3,000 people—from high-risk areas to safer locations in anticipation of the storm.^[202] Heavy rain and flooding in Central Vietnam caused by Soulik killed 1 person in Nghe An and injured 1 person in Thua Thien Hue.^[203]

Tropical storm (JMA)
Tropical storm (SSHWS)
Duration	September 15 – September 21
Peak intensity	85 km/h (50 mph) (10-min); 992 hPa (mbar)

On September 15, a tropical depression formed from a broad area of convection near Guam. At 12:00 UTC, the JMA upgraded it into a tropical storm, naming it Pulasan, a replacement name for Rumbia. A few hours later, the JTWC issued a TCFA for the system.^[204] The next day, the JTWC classified it as a tropical storm. However, it maintained typical characteristics of a monsoon depression. Pulasan entered the Philippine Area of Responsibility late on September 17 and was designated as Tropical Storm Helen by PAGASA.^[205] Pulasan continued to drift northwestwards until it passed through the Ryukyu Islands and made landfall over Zhoushan, China as a weakening tropical storm.^[206] The terrain interaction with Pulasan made its convection disorganized, causing it to weaken into a tropical depression.^[207] It later turned east-northeast as it heads for South Korea, re-strengthened back into a tropical storm.^[208]

Pulasan strengthened the southwest monsoon affecting the Philippines. The storm, along with Soulik and Bebinca, was blamed for a total of 24 deaths, 13 injuries and 12 missing across the country.^[200] Heavy rains from Pulasan caused major flooding and landslides across the Noto Peninsula in Japan, leaving one missing, destroying many buildings and forcing 60,700 residents to be evacuated. The town of Wajima was especially affected.^[209]

Tropical depression (JMA)
Tropical depression (SSHWS)
Duration	September 20 – September 22
Peak intensity	55 km/h (35 mph) (10-min); 1002 hPa (mbar)

On September 20, a tropical depression formed near northern Luzon. The disturbance was in a marginal environment, with moderate to high wind shear and warm sea surface temperature. Hours later, JMA later recognized the LPA as a depression. At 14:00 PHT of the same day, PAGASA followed suit and named the system as Igme.^[210] JTWC later issued a TCFA warning as the LLCC started to organize. The next day, the JTWC upgraded Igme as a tropical depression and designated it as 17W.^[211] Igme later curved southwestwards, passing closely through Taiwan.^[212] On September 22, the JTWC reported that Igme had strengthened into a tropical storm.^[213] JTWC later discontinued issuing bulletins on Igme after high vertical wind shear and the topographic interaction had caused to weaken significantly and dissipated after.^[214]

Igme strengthened the southwest monsoon affecting the Philippines. The storm, along with Pulasan, Soulik and Bebinca, was blamed for a total of 25 deaths, 13 injuries and eight missing across the country.^[215]

Tropical depression (JMA)
Tropical depression (SSHWS)
Duration	September 24 – Present
Peak intensity	55 km/h (35 mph) (10-min); 1006 hPa (mbar)

On September 24, a tropical depression formed south of Japan, and was designated as 18W by the JTWC later that same day.

• On August 18, the JMA reported the formation of a low-pressure area over the Philippine Sea.^[216] The next day, it was designated as a tropical depression but weakened to a low-pressure area by August 22.^[217] The following day, the JMA re-designated it as a tropical depression as it turned southward.^[218] Over the next few days, the depression gradually moved southwestward while Typhoon Shanshan approached Japan from the west.^[219] The JMA continued to monitor the depression until it dissipated on August 26.^[220]
• A tropical depression briefly formed south of South Korea on August 19 and was last noted by the JMA at 18:00 UTC as it moved northward.^[221][222]
• A tropical depression briefly developed southeast of Japan on August 20.^[223] Thereafter, it was designated as an extratropical low while drifting southeastward.^[224]
• A tropical depression briefly formed southeast of Typhoon Shanshan on August 30 and was last noted by the JMA at 18:00 UTC.^[225][226]
• A tropical depression formed over the Philippine Sea on September 4. Two days later, it degenerated into a low-pressure area as it slowly turned to the west. On September 9, it re-strengthened back into a tropical depression as it moved west-northwest towards Eastern China.

Within the basin, both the Japan Meteorological Agency (JMA) and the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) assign names to tropical cyclones that develop in the Western Pacific, which can result in a tropical cyclone having two names.^[227] The Japan Meteorological Agency's RSMC Tokyo — Typhoon Center assigns international names to tropical cyclones on behalf of the World Meteorological Organization's Typhoon Committee when they have 10-minute sustained winds of 65 km/h (40 mph).^[228]

PAGASA names tropical cyclones which are active in their area of responsibility located between 135°E and 115°E and between 5°N and 25°N even if the cyclone has already been named.^[227] The names of significant tropical cyclones are retired by both PAGASA and the Typhoon Committee.^[228] If the list of names for the Philippine region are exhausted, then names will be taken from an auxiliary list of which the first ten are published each season. Unused names are marked in gray. The names of significant tropical cyclones will be retired by both PAGASA and the Typhoon Committee in the spring of 2025.^[228]

A tropical cyclone is named when it has 10-minute sustained winds of 65 km/h (40 mph).^[229] The JMA selected the names from a list of 140 names, that had been developed by the 14 members nations and territories of the ESCAP/WMO Typhoon Committee.^[230] Retired names, if any, will be announced by the WMO in 2025, though replacement names will be announced in 2026. During the season, the name Pulasan was used for the first time after which replaced Rumbia, which was retired following the 2018 season. The next 28 names on the naming list are listed here along with their international numeric designation, if they are used.

Ewiniar (2401) Maliksi (2402) Gaemi (2403) Prapiroon (2404) Maria (2405) Son-Tinh (2406) Ampil (2407)

Wukong (2408) Jongdari (2409) Shanshan (2410) Yagi (2411) Leepi (2412) Bebinca (2413) Pulasan (2414)

Soulik (2415) Cimaron (unused) Jebi (unused) Krathon (unused) Barijat (unused) Trami (unused) Kong-rey (unused)

Yinxing (unused) Toraji (unused) Man-yi (unused) Usagi (unused) Pabuk (unused) Wutip (unused) Sepat (unused)

If a tropical cyclone enters the Western Pacific basin from the Eastern and Central Pacific basin (west of 180°E), it will retain the name assigned to it by the National Hurricane Center (NHC) and Central Pacific Hurricane Center (CPHC). The following storms were named in this manner.

• Hone

This season, PAGASA will use its own naming scheme for storms that are active in their self-defined area of responsibility.^[231] During this season, PAGASA is using the following list of names that was last used during 2020 and will be used again in 2028, updated with replacements of retired names, if any.^[231] All of the names are the same as in 2020 with the exception of Aghon, Querubin, Romina and Upang, which replaced the names Ambo, Quinta, Rolly and Ulysses after they were retired.^[231] The name Aghon was used for the first time this year.

Aghon (2401) Butchoy (2404) Carina (2403) Dindo (2409) Enteng (2411)

Ferdie (2413) Gener (2415) Helen (2414) Igme Julian (unused)

Kristine (unused) Leon (unused) Marce (unused) Nika (unused) Ofel (unused)

Pepito (unused) Querubin (unused) Romina (unused) Siony (unused) Tonyo (unused)

Upang (unused) Vicky (unused) Warren (unused) Yoyong (unused) Zosimo (unused)

Alakdan (unused) Baldo (unused)

Clara (unused) Dencio (unused)

Estong (unused) Felipe (unused)

Gomer (unused) Heling (unused)

Ismael (unused) Julio (unused)

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

• Weather of 2024
• Tropical cyclones in 2024
• Pacific typhoon season
• 2024 Atlantic hurricane season
• 2024 Pacific hurricane season
• 2024 North Indian Ocean cyclone season
• South-West Indian Ocean cyclone seasons: 2023–24, 2024–25
• Australian region cyclone seasons: 2023–24, 2024–25
• South Pacific cyclone seasons: 2023–24, 2024–25

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