Basin: | WPac |
Year: | 2024 |
First Storm Formed: | May 22, 2024 |
Last Storm Dissipated: | Season ongoing |
Track: | 2024 Pacific typhoon season summary.png |
Strongest Storm Name: | Gaemi |
Strongest Storm Pressure: | 940 |
Strongest Storm Winds: | 90 |
Average Wind Speed: | 10 |
Total Depressions: | 14 |
Total Storms: | 10 |
Total Hurricanes: | 3 |
Total Super: | 0 (unofficial) |
Fatalities: | 155 total |
Damages: | 344 |
Five Seasons: | 2022, 2023, 2024, 2025, 2026 |
Atlantic Season: | 2024 Atlantic hurricane season |
East Pacific Season: | 2024 Pacific hurricane season |
North Indian Season: | 2024 North Indian Ocean cyclone season |
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) will name a tropical cyclone if it has 10-minute sustained wind speeds of at least 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) are given a number with a "W" suffix. __TOC__
TSR forecasts Date | Tropical storms | Total Typhoons | Intense TCs | |||
---|---|---|---|---|---|---|
Average (1991–2020) | 25.5 | 16.0 | 9.3 | 301 | [1] | |
May 7, 2024 | 25 | 15 | 7 | 225 | ||
July 5, 2024 | 24 | 14 | 7 | 211 | [2] | |
Other forecastsDate | ForecastCenter | Period | Systems | |||
January 15, 2024 | PAGASA | January–March | 0–2 tropical cyclones | [3] | ||
January 15, 2024 | PAGASA | April–June | 2–4 tropical cyclones | |||
June 26, 2024 | PAGASA | July–September | 6–10 tropical cyclones | [4] | ||
June 26, 2024 | PAGASA | October–December | 4–7 tropical cyclones | |||
Other forecasts Date | Forecast Center | Period | Systems | |||
January 13, 2023 | PAGASA | January–March | 0–2 tropical cyclones | |||
January 13, 2023 | PAGASA | April–June | 2–4 tropical cyclones | |||
June 27, 2023 | PAGASA | July–September | 7–10 tropical cyclones | |||
June 27, 2023 | PAGASA | October–December | tropical cyclones | |||
2024 season | Forecast Center | Tropical cyclones | Tropical storms | Typhoons | ||
Actual activity: | JMA | 14 | 10 | 3 | ||
Actual activity: | JTWC | 11 | 7 | 4 | ||
Actual activity: | PAGASA | 4 | 3 | 2 |
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.[1] In their July forecast, they slightly decreased the amount of storms and typhoons.
The Pacific typhoon season began on May 22, 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.[5] 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, the remnants of Ewiniar would be absorbed by another extratropical cyclone, 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 Southern China. 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. 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. The next day, the easternmost disturbance 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. 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, with JTWC further recognized as a Category-2 typhoon. The next day, it strengthened into a Category-4 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. However, it did not last long and weakened into a depression as it nears the Korean Peninsula. On August 21, Both JMA and JTWC reported that Jongdari had dissipated as its low-level circulation center had 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 on the next day and got the name Shanshan from the JMA.
Basin: | WPac |
Formed: | May 22 |
Dissipated: | May 30 |
Track: | Ewiniar 2024 path.png |
10-Min Winds: | 70 |
1-Min Winds: | 95 |
Pressure: | 980 |
See main article: Typhoon Ewiniar (2024). On May 21, the Joint Typhoon Warning Center (JTWC) began tracking an area of atmospheric convection 238order=outNaNorder=out southeast of Palau, noting that the system was moving northwestward towards an environment favorable for tropical cyclogenesis.[6] The JTWC subsequently issued a TCFA on the following day as the disturbance developed rainbands wrapping from the southwest.[7] At 18:00, the disturbance became a tropical depression.[8] The depression would later enter PAR, assigning the name Aghon, a replacement name for Ambo.[9] At 18:00 UTC, the JTWC designated the depression as 01W, based on surface observations from Guiuan.[10] Aghon made landfall over Homonhon Island and subsequently Giporlos, Eastern Samar in the early morning of May 25 (PHT).[11] It made five more landfalls over Basiao and Cagduyong Islands of Catbalogan; Batuan in Ticao Island; Masbate City; and Torrijos, Marinduque. 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.[12] In the morning of May 26 (PHT), the storm made its eighth landfall over Lucena, Quezon in Luzon island.[13] Ewiniar later intensified into a typhoon over Lamon Bay[14] The storm made its final landfall over Patnanungan in the Polillo Islands.[15] The typhoon left the PAR on May 29 and continued to weaken due to subsidence around the mid-latitude.[16] [17] On May 30, Ewiniar transitioned into an extratropical cyclone south-southwest of Yokosuka, Japan[18] Then at 18:00 UTC on May 31, Ewiniar entered the baroclinic zone and an area of high wind shear.[19]
Agricultural damage in the Philippines totalled . Damage to infrastructure was valued a for a total of . Overall, Typhoon Ewiniar killed six people and left eight injured, and around 152,266 others were directly impacted by Ewiniar in the Philippines.[20]
Basin: | WPac |
Formed: | May 30 |
Dissipated: | June 2 |
Track: | Maliksi 2024 path.png |
10-Min Winds: | 35 |
1-Min Winds: | 30 |
Pressure: | 998 |
On May 29, the JTWC began tracking an area of convection located 219order=outNaNorder=out 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.[21] It was recognized as a low-pressure area by the JMA early the next day,[22] before the agency upgraded it to a tropical depression at 06:00 UTC.[23] Later that day, the JTWC issued a TCFA on the depression since it had rapidly developed.[24] At 00:00 UTC the next day, the JTWC upgraded the system into a tropical depression, designating it as 02W.[25] Later, the JMA upgraded it into a tropical storm, and it was given the name Maliksi.[26] However, the JTWC reported that it did not intensify into a tropical storm as it was disorganized, with the circulation elongating.[27] [28] At 21:00 UTC on May 31, the JTWC discontinued warnings on the system as it made landfall in Southern China.[29] Soon after, the JMA downgraded Maliksi into a depression before being further downgraded by the agency as a low-pressure area as it tracked inland on June 2.[30] [31]
On May 30, the Hong Kong Observatory issued a No. 1 standby signal as the depression neared Hong Kong.[32] The next day, it upgraded the warnings into a No. 3 Strong Wind signal.[33] 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.[34] In Macau, the storm caused unstable weather, with the Meteorological and Geophysical Bureau issuing Typhoon Signal No. 3[35] [36] In China, torrential rainfall occurred, peaking at 272.3mm somewhere in the Leizhou Peninsula. Additionally, heavy rain was recorded in Fujian, Zhejiang and Jiangxi.[37]
Basin: | WPac |
Formed: | July 13 |
Dissipated: | July 15 |
Track: | 03W 2024 path.png |
10-Min Winds: | 30 |
1-Min Winds: | 25 |
Pressure: | 1000 |
On July 13, the JTWC began tracking an area of convection 368abbr=onNaNabbr=on 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.[38] At 06:00 UTC of that day, the JMA designated the system as a tropical depression.[39] 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.[40] By 18:00 UTC the next day, the JTWC upgraded the system into a tropical depression, designating it 03W.[41] However, they issued their last warning on the depression early the next day as it moved over Vietnam and rapidly weakened.[42] Later that day, the JMA stopped tracking the depression as it dissipated.[43]
Basin: | WPac |
Formed: | July 19 |
Dissipated: | July 24 |
Track: | Prapiroon 2024 path.png |
10-Min Winds: | 60 |
1-Min Winds: | 60 |
Pressure: | 980 |
See main article: Tropical Storm Prapiroon (2024). On July 15, the JTWC started to monitor a persistent area of convection roughly 623abbr=onNaNabbr=on southeast of Manila, Philippines. At that time, the disturbance was in a favorable environment for development, with warm NaNC, sea surface temperatures, low wind shear and good equatorial outflow.[44] At 06:00 UTC the same day, the JMA designated the system as a low-pressure area.[45] Shortly after, the JMA designated it as a tropical depression.[46] 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.[47] It intensified into a tropical storm and was named Prapiroon by the JMA on June 21.[48] [49] A nascent eye feature became visible on microwave satellite imagery.[50] [51] The center of Prapiroon made landfall near Wanning, Hainan, with 1-minute sustained winds of 50kn on July 22. After making landfall, the storm maintained its well-defined eye while moving across central Hainan.[52] Prapiroon soon encountered high wind shear and a dry environment,[53] and by 6:30 a.m. local time on July 23, it made its second landfall in Quảng Ninh, Vietnam, becoming the first tropical cyclone to strike Vietnam in 640 days.[54] [55] After the system moved inland,[56] both the JMA and the JTWC ceased monitoring it on July 24.[57]
Along with 2024's Typhoon Gaemi, Prapiroon and its precursor affected the southwest monsoon over the Philippines,[58] leading to significant rainfall across parts of the archipelago as Prapiroon began to move away.[59] Overall, the tropical storm was responsible for 23 deaths, 9 missing and US in damage.[60]
Basin: | WPac |
Formed: | July 19 |
Dissipated: | July 27 |
Track: | Gaemi 2024 path.png |
10-Min Winds: | 90 |
1-Min Winds: | 125 |
Pressure: | 940 |
See main article: Typhoon Gaemi. On July 17, the JMA reported that a low-pressure area had formed east of Palau.[61] Shortly after, both the JMA and the JTWC followed suit and upgraded the tropical depression, with the latter designating the system as 05W.[62] The PAGASA followed suit a few hours later, recognizing the system as a tropical depression and naming it Carina.[63] Early the next day, the depression intensified into a tropical storm, and was given the name Gaemi by the JMA.[64] 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.[65] 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 125kn by the JTWC, 10-minute sustained winds of 90kn by the JMA, and a central pressure of 940abbr=onNaNabbr=on.[66] [67] After stalling and executing a tight counter-clockwise loop near the coast,[68] 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.[69] Gaemi accelerated as it moved across the island and emerged into the Taiwan Strait just six hours after making landfall.[70] Soon after,[71] the JTWC ceased issuing advisories on the system as it made its final landfall at Xiuyu, Putian in Fujian Province.[72] Once inland, the JMA continued tracking Gaemi until it weakened into a tropical depression on July 27.[73]
Together with the southwest monsoon and nearby 2024's Tropical Storm Prapiroon, heavy rains were reported over southern and northern Luzon, triggering widespread flash floods in various areas of the region.[74] In all, the typhoon killed at least 126 people and caused US$266 million.[75] [76]
Basin: | WPac |
Formed: | August 3 |
Dissipated: | August 19 |
Track: | Ampil 2024 path.png |
10-Min Winds: | 85 |
1-Min Winds: | 115 |
Pressure: | 950 |
See main article: Typhoon Ampil (2024). On August 3, the JTWC began tracking an area of convection 527abbr=onNaNabbr=on east of Kadena Air Base on August 3.[77] At 18:00 UTC the same day, the JMA designated the system as a low-pressure area.[78] However, just six hours later, they upgraded the system as a tropical depression.[79] The depression weakened and was last noted by the JMA on August 7.[80] 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.[81] Soon after, the JTWC began to re-monitoring it, noting that it was in a marginal favorable environment for development.[82] At 07:00 UTC on August 12, the agency issued a TCFA on the disturbance.[83] A few hours later, they recognized the system as a tropical depression, designating it as 08W.[84] Soon after, the JMA noted that it had intensified into a tropical storm, with convective bands wrapping around a well-defined low-level circulation center,[85] and named it Ampil.[86]
The JMA upgraded the system to a severe tropical storm on August 13.[87] Around 15:00 UTC on August 14, the JTWC reported that Ampil had intensified into a minimal typhoon, as animated infrared imagery indicated the development of a pinhole eye feature.[88] 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.[89] The JMA reported that Ampil reached its peak intensity at 12:00 UTC that day with 10-minute sustained winds of 85kn and a central pressure of 950abbr=onNaNabbr=on before making its closest approach to Japan.[90] [91] The JMA reported that Ampil had transitioned into an extratropical low on August 19.[92] The NHK reported that Tokyo suffered minimal damage, while several people were injured in Kanagawa Prefecture.[93]
Basin: | WPac |
Formed: | August 5 |
Dissipated: | August 14 |
Track: | Maria 2024 path.png |
10-Min Winds: | 55 |
1-Min Winds: | 70 |
Pressure: | 980 |
See main article: Tropical Storm Maria (2024). On August 5, the JMA stated that a tropical depression had formed.[94] 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.[95] At 09:00 UTC on August 6, the JTWC issued a TCFA on the disturbance, which was located 368abbr=onNaNabbr=on north-northwest of Iwo Jima, along the eastern periphery of the monsoon gyre,[96] prior to it being designated as 06W.[97] The development of a central dense overcast and a ragged eye feature signified its intensification into a tropical storm,[98] leading the JMA to name it Maria on August 7.[99] Maria then turned northeastward,[100] and intensified into a severe tropical storm on August 8 due to a favorable environment for development.[101] Concurrently, the JTWC then reported that Maria had rapidly intensified into a minimal typhoon due to strong equatorward and poleward outflow.[102] However, Maria's wind field became more asymmetric, with its associated convection shifting northward,[103] causing Maria to weaken into a tropical storm on August 9.[104] Around 00:00 UTC on August 12, the storm made landfall Ōfunato,[105] a city in Iwate Prefecture, Japan with winds of 45kn before traversing northern Honshu and emerging into the Sea of Japan.[106] The JMA continued to monitor the system until it was last noted at 18:00 UTC on August 14.[107]
Record-breaking rainfall totals were observed in Iwate Prefecture, reaching 191NaN1 in Kuji and 12.61NaN1 in Otsuchi,[108] nearly double the average rainfall amount for August.[109] Controlled releases of the Taki Dam in Kuji forced the evacuation of 8,300 people as the highest evacuation alert level was issued. Several homes were flooded in Iwaizumi, Kamaishi, and Miyako.[109] No damage and injuries were reported in association with Maria.[110]
Basin: | WPac |
Formed: | August 10 |
Dissipated: | August 14 |
Track: | Son-Tinh 2024 path.png |
10-Min Winds: | 35 |
1-Min Winds: | 40 |
Pressure: | 994 |
On August 10, the JMA noted that a tropical depression had formed southeast of Severe Tropical Storm Maria.[111] A few hours later, the JTWC began tracking the system, noting that it could transition into a tropical cyclone despite intense wind shear.[112] Early the next day, they noted that the depression had transitioned into a subtropical cyclone.[113] As a result, a few hours later, the JMA named it Son-Tinh.[114] The next day, the JTWC noted that it had transitioned into a tropical storm, designating it 07W.[115] Soon after, the low-level circulation center became fully exposed with no deep convection existing near the center.[116] Son-Tinh then turned northwestward, along the western periphery of a subtropical ridge.[117]
Basin: | WPac |
Formed: | August 12 |
Dissipated: | August 15 |
Track: | Wukong 2024 path.png |
10-Min Winds: | 35 |
1-Min Winds: | 30 |
Pressure: | 1002 |
On 12 August, the JMA noted that a tropical depression formed southwest of Tropical Storm Son-Tinh.[118] Later that day, the JTWC issued a TCFA on the depression as it starts to move northeastward. The next day, the agency designated it as 09W with the JMA following suit, upgrading the system to a tropical storm and naming it Wukong. While JTWC still referred to Wukong as a depression, it continued to track northwestwards. It then curved east, losing its tropical characteristics as it moved into high wind shear and unfavorable conditions. JTWC continued to track Wukong until it dissipated on August 15.
Basin: | WPac |
Formed: | August 17 |
Dissipated: | August 21 |
Track: | Jongdari 2024 path.png |
10-Min Winds: | 40 |
1-Min Winds: | 35 |
Pressure: | 998 |
On August 17, the JMA noted that a tropical depression formed east of Taiwan. The next day, at 12:00 UTC, PAGASA declared the system as a tropical depression and named it Dindo. At 15:00 UTC, the JTWC issued a TCFA for what was then-Invest 98W. Three hours later, the JMA declared it as a tropical storm, naming it Jongdari, with PAGASA following suit after that.[119] JTWC also followed suit and designated the depression as 10W.[120] At 09:00 PHT (17:00 UTC), Jongdari left PAR as it heads for the Yellow Sea.[121] Being a well-defined low-level circulation center (LLCC), JTWC upgraded the storm into a tropical storm status. However, it did not last long, causing Jongdari to weaken back to a tropical depression.[122] On August 21, JTWC reported that Jongdari had been dissipated as the LLCC had vanished when it moved through the Korean Peninsula.[123]
In some parts of the southern islands of Jeju, Jongdari accumulated 60 to 100 mm (2.3 to 5.1 in) of rain as it moved closer to the coast.[124]
Basin: | WPac |
Formed: | August 19 |
Dissipated: | present |
Track: | JMA TD 11 2024 path.png |
10-Min Winds: | 30 |
Prewinds: | < |
Pressure: | 1006 |
A tropical depression formed in the Philippine Sea on August 19.
Basin: | WPac |
Formed: | August 21 |
Dissipated: | present |
Track: | Shanshan 2024 path.png |
10-Min Winds: | 35 |
1-Min Winds: | 40 |
Pressure: | 1002 |
A tropical depression formed west of the Northern Mariana Islands on August 21.
See also: Tropical cyclone naming and History of tropical cyclone naming. 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.[125] 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 65km/h.[126]
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.[125] The names of significant tropical cyclones are retired by both PAGASA and the Typhoon Committee. 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 . The names of significant tropical cyclones will be retired by both PAGASA and the Typhoon Committee in the spring of 2025.
See main article: article and List of retired Pacific typhoon names. A tropical cyclone is named when it has 10-minute sustained winds of 65km/h.[127] 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.[128] Retired names, if any, will be announced by the WMO in 2025, though replacement names will be announced in 2026. The next 28 names on the naming list are listed here along with their international numeric designation, if they are used.
|
See main article: List of retired Philippine typhoon names. This season, PAGASA will use its own naming scheme for storms that are active in their self-defined area of responsibility.[129] 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.[129] 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.[129] The name Aghon was used for the first time this year.
Auxiliary list
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.|-| Ewiniar (Aghon) || || style="background:#" | || style="background:#" | 70kn || style="background:#" |980hPa || Philippines, Japan, Alaska || $20.88 million || || |-| Maliksi || || style="background:#" | || style="background:#" | 35kn || style="background:#" |998hPa || South China, Taiwan || Unknown || None ||[130] |-| 03W || || style="background:#" | || style="background:#" | 30kn || style="background:#" |1000hPa || Vietnam, Laos, Thailand || None || None |||-| Prapiroon (Butchoy) || || style="background:#" | || style="background:#" | 60kn || style="background:#" |980hPa || Philippines, Vietnam, South China, Laos, Thailand, Cambodia|| > || 23 ||[131] |-| Gaemi (Carina) || || style="background:#" | || style="background:#" | 90kn || style="background:#" |940hPa || Philippines, Taiwan, Yaeyama Islands, East China, Indonesia, Cambodia, Singapore, North Korea || $304 million || 126 ||[132] [133] [134] |-| Ampil || || style="background:#" | || style="background:#" | 85kn || style="background:#" |950hPa || Bonin Islands, Japan, Alaska || Minimal|| None |||-| Maria || || style="background:#" | || style="background:#" | 55kn || style="background:#"|980hPa || Bonin Islands, Japan || None || None ||[135] |-| Son-Tinh || || style="background:#" | || style="background:#" | 35kn || style="background:#"|994hPa || Alaska || None || None |||-| Wukong || || style="background:#" | || style="background:#" | 35kn || style="background:#"|1002hPa || None || None || None |||-| Jongdari (Dindo) || || style="background:#" | || style="background:#" | 40kn || style="background:#"|998hPa || Taiwan, Miyako Islands, Yaeyama Islands, Korean Peninsula || None || None |||-| TD || || style="background:#" | || style="background:#" | Not specified || style="background:#" |1008hPa || None || None || None |||-| TD || || style="background:#" | || style="background:#" | 30kn || style="background:#" |1006hPa || None || None || None |||-| TD || || style="background:#" | || style="background:#" | Not specified || style="background:#" |1012hPa || None || None || None |||-| Shanshan || || style="background:#" | || style="background:#" | 35kn || style="background:#" |1002hPa || Guam, Northern Mariana Islands || None || None |||-