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, as well as the deadliest since 2013, and the fifth-costliest Pacific typhoon season on record, mostly due to Yagi. This season also saw the most active November on record, with 4 storms active at the same time. 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 65km/h (40mph) 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; W meaning west, a reference to the western Pacific region.
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 Administration.
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]
Seasonal summary
Background
Officially, the 2024 Pacific typhoon season so far has thirty-seven tropical depressions form; twenty-five became named storms. Twelve became typhoons, six of which intensified into a super typhoon. This season's ACE index, as of November16, is approximately 204units.[8] This number represents sum of the squares of the maximum sustained wind speed (knots) for all named storms while they are at least tropical storm intensity, divided by 10,000. Therefore, tropical depressions are not included.
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.[9] 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 719km (447mi) 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.
Satellite loop of Typhoon Gaemi skirting the coast before making landfall in the northeastern coast of Taiwan on July 24
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, receiving 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. R
Being in a favorable environment in the Philippine Sea, Gaemi continued to strengthen and became a typhoon, the second to occur this season. Gaemi rapidly intensified into a very strong typhoon, with 10-minute sustained winds of 165km/h (105mph). Gaemi stalled and executed a counterclockwise loop near the coast, slightly weakening before making landfall over Hualien, Taiwan. Weakened by the landfalls, 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 $2.31 billion worth of damages throughout its track.
Peak season activity
Four systems active on August 13: Tropical Depression Maria (top left); Tropical Storm Ampil (bottom left); Tropical Depression Son-Tinh (center right); and Tropical Depression 09W (bottom right; precursor to Wukong).
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 reclassified it 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 Category2-equivalent typhoon. The next day, it strengthened into a Category4-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 Category1-equivalent typhoon. It remained at that intensity as it battled through wind shear. As it nears the Amami Islands, it strengthened into a Category4-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.
Typhoon Yagi making landfall over Wenchang City in Hainan on September 6
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 made landfall in Lingang New City 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 landed 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. On September 18, two disturbances in the South China Sea near 98W and 99W were expected to merge and strengthen at 98W, closer to Vietnam. Shortly after, 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.
Following, on September 24, a tropical depression formed in the Pacific south of Japan. That day, JTWC designated the system as 18W. The following day, the JMA upgraded the depression into a tropical storm, earning the name Cimaron. The storm moved southwestwards, maintaining its intensity. As it moved westwards, Cimaron weakened into a tropical depression as an unfavorable environment hindered any intensification. Cimaron later dissipated on September 27. Shortly later the same day, another low-pressure area formed near the Northern Mariana Islands. Despite being in a marginal environment, the disturbance managed to be organized and designated as 19W by the JTWC. On September 27, the JMA upgraded 19W into a tropical storm, naming it Jebi. At first, Jebi struggled to organize due to the presence of moderate low-level windshear, causing to downgrade Jebi as a depression. However, Jebi redeveloped back into a tropical storm after. The storm continued to organize until it further intensified into a Category-1 typhoon by the JTWC, while JMA only reached the intensity of a severe tropical storm. Jebi later transitioned to an extratropical cyclone, causing both agencies to issue their final warning on October 2.
Shortly after Cimaron weakened into a depression, an area of low pressure formed in the Philippine Sea near extreme Northern Luzon on September 26, PAGASA shortly issued bulletins regarding the disturbance and was named Julian as it developed into a depression. The following day, the JTWC designated Julian as 20W, upgrading it into a tropical depression. On September 28, the JMA upgraded 20W into a tropical storm, naming it Krathon, a replacement name for Mangkhut. It then intensified into a Category-1 typhoon, heading towards Sabtang, Batanes. Shortly after, the typhoon began its rapid intensification and in two days, the system reached its peak intensity equivalent to a Category-4 super typhoon. On October 3, Krathon made landfall over Siaogang District in Kaohsiung, Taiwan. The typhoon became the first storm to make landfall in Taiwan's densely populated western plains since Typhoon Thelma in 1977. The storm weakened while moving inland, marking the first time it had happened in Taiwan since Tropical Storm Trami in 2001. The JMA continued to track the system to the South China Sea before it dissipated on October 4.
Late season activity
On October 5, a tropical depression formed near Guam. The following day, the JTWC designated it as 21W. Despite moving through warm waters, high wind shear hindered any further development, causing it to weaken back into a depression. On October 8, the JTWC issued its final warning, with dissipation expected in the next 12 hours. The next day, 21W intensified into a tropical storm, receiving the name Barijat from the JMA. Later in the day, JTWC reissued advisories on Barijat and strengthened into a tropical storm. However, both agencies later made their final warning for the last time as the storm dissipated on October 11.
Flooded rice fields in Camarines Sur after the onslaught of Trami.
On October 19, a tropical depression formed nearby Yap. The next day, it was assigned as 22W by the JTWC, acknowledged as a tropical depression. Then, it moved into the PAR and was named Kristine by PAGASA. Soon after, the JMA upgraded it to tropical storm status and was given the name Trami. Many parts of the Philippines were issued wind storm signals prior to its approach to the country. On October 23, Trami later strengthened into a severe tropical storm, causing some northern and central Luzon areas to upgrade to Tropical Cyclone Wind Signal No. 3. At 04:30 UTC the next day, Trami made landfall over the province of Divilacan, Isabela. The following day, Trami emerged above the coastal waters of southern Ilocos Sur, leaving the remnants of a circulation center over Northern Luzon. This caused a lot of areas in the country to bring torrential rains with gusty winds throughout the day.
Trami continued crossing the South China Sea, maintaining severe tropical storm strength. Trami later encountered strong easterly vertical wind shear as it approached the coast of Vietnam. The storm later made another landfall in Da Nang at 10 AM local time on October 27. Trami then moved southwestwards due to weak steering flow before making a U-turn over the coastal regions of Vietnam. Trami later weakened into a low-pressure area before the agencies made its last warning on October 29.
As Trami crossed through the Cordilleras, another tropical disturbance was formed southeast of Guam on October 24. JMA began to track the system thereafter as a tropical depression, with a gale warning also being issued. The next day, JMA upgraded the disturbance into a tropical storm, assigning the name Kong-rey. Since another disturbance was formed as Invest 99W on the northern side, the JTWC canceled warnings on the southern side, designated as 98W and issued Kong-rey at 99W, located in the north side. Kong-rey was later designated as Tropical Depression 23W by the JTWC. The storm entered PAR, receiving the local name Leon. On October 29, Kong-rey started undergoing rapid intensification and became a Category-4 super typhoon the following day. With that, Kong-rey achieved a peak intensify of 1-minute sustained winds of 240km/h (150mph) and a central pressure of 925 hPa (27.32 inHg).
Shortly after reaching its peak intensity, Kong-rey started to slightly weaken as it went through eyewall replacement cycle moving northwestwards. The storm later made a historic landfall over Chenggong, Taitung in Taiwan, marking the first major typhoon to make landfall in the country after mid-October, and the largest typhoon to hit since Typhoon Herb of 1996. Kong-rey later reemerged through the Taiwan Strait with a weakened convective structure around the center. Kong-rey weakened and transitioned to an extratropical cyclone over Sasebo, Japan, causing both agencies to cease advisories on November 1.
Four tropical systems active on November 11: Tropical Storm Yinxing [MARCE] (bottom left); Severe Tropical Storm Toraji [NIKA] (upper left); Tropical Storm Usagi [OFEL] (center right); and Tropical Storm Man-yi [PEPITO] (very right).
Just after Kong-rey transitioned to a post-tropical cyclone, an area of low pressure was formed near Palau on November 1. However, JTWC discontinued issuing advisories as unfavorable conditions hindered the development. Two days later, JTWC reissued advisories as signs of organization of the disturbance continued to form. At 14:00 UTC, the JTWC along with JMA upgraded the system to a tropical depression, assigning it the designation Tropical Depression 24W. Later at 18:00 UTC of November 3, 24W intensified into a tropical storm, gaining the name Yinxing by the JMA. Yinxing would enter the Philippine Area of Responsibility, receiving the name Marce by PAGASA. The storm would continue to intensify over the Philippine Sea until the agencies were prompted to classify as a typhoon on the following day. It then reached its peak intensity of a Category-4 typhoon, with 1-minute sustained winds of 230km/h (145mph) and a central pressure of 940 hPa (27.76 inHg). Around 3:40 PM PHT (07:40 UTC) of November 7, Yinxing made landfall over Santa Ana, Cagayan. After crossing through Babuyan Channel, the storm made its second landfall over Sanchez Mira, Cagayan. Yinxing slightly weakened into a Category-2 typhoon after making landfall, but eventually regained as a Category-3 typhoon as it reemerged through South China Sea.
On November 8, a tropical disturbance formed east of Southern Luzon. The disturbance was moving westward as it continues to organize itself in a favorable environment. At 8:00 AM PHT (00:30 UTC) of the following day, it entered the Philippine Area of Responsibility (PAR), where it attained the name Nika by PAGASA. Not long after Nika formed, another area of low pressure formed near Marshall Islands on the following day, designated as Invest 93W. The low pressure was also located in a favorable development and low vertical wind shear, causing to issue of a TCFA regarding the disturbance. Hours later, 93W became a tropical depression, giving the identifier 25W. The JTWC also upgraded Nika into a depression, designated as 26W.
Typhoon Man-yi making landfall in Panganiban, Catanduanes on November 16
Later that day, both depressions strengthened into tropical storms and were named Toraji for 26W and Man-yi for 25W by the JMA. On November 10, Toraji further intensified into a severe tropical storm by the JMA, while JTWC automatically upgraded the system into a Category-1 typhoon as the outer bands of the system continues to tighten up. JMA later followed suit and granted Toraji to intensify into a minimal typhoon before it struck the province of Dilasag, Aurora. It later emerged over South China Sea, just off the coast of Magsingal, Ilocos Sur, with satellite imagery showing a tightly wrapped low-level circulation. As it moved northwestwards, a small patch of deep convection developed over the northern portion of a partially exposed low-level circulation, resulting in the system weakening into a tropical storm on November 11.
Meanwhile, on November 9, a tropical depression formed near Micronesia. The following day the JMA issued a warning on the system. On November 11, the JTWC upgraded it into a tropical depression, designating it as 27W. In early morning the next day, 27W strengthened into a tropical storm, prompting the JMA to name it Usagi. This marks the first time in this basin since reliable meteorological records that four active systems existed simultaneously in November.[10] Meanwhile, Usagi entered Philippine Area of Responsibility (PAR), getting the name Ofel from PAGASA. Usagi continued to strengthen until it underwent rapid intensification, prompting it to upgrade into a Category-4 super typhoon on November 14. At 1:30 PM PHT (05:30 UTC) of the same day, the storm made landfall over Baggao, Cagayan. Usagi later weakened as the eye began to disappear after having land interaction with the mountains.
Upon giving the name Usagi as 27W, the Northwest Pacific witnessed a historical rarity on November 12, witnessing double typhoons in the South China Sea for the first time since 1992 by Angela and four storms simultaneously active in November since records began in 1951 and the basin for the first time since 1970.
Meanwhile, after Man-yi maintained tropical storm strength for five days, JMA upgraded it into a severe tropical storm as it moved into a more favorable environment. At 20:00 PHT (12:00 UTC) on November 14, Man-yi briefly entered PAR, gaining the name Pepito by PAGASA. Early November 16, Man-yi peaked as a super typhoon, with estimated 1-minute maximum sustained winds of 260km/h (160mph) and a central pressure of 920 hPa (27.17 inHg). At 9:40 PM PHT (05:40 UTC) of the same day, Man-yi made its first landfall over the province of Panganiban, Catanduanes, packing strong winds and heavy rains all over the area. The following day, Man-yi made its second landfall in Dipaculao, Aurora, on Luzon Island at around 3:20 PM PHT (07:20 UTC).[11] The Sierra Madre mountain range caused the eye of the typhoon to close as it rapidly moved inland. Man-yi later accelerated northwestward over the South China Sea, weakening into a severe tropical storm. It then continued to deteriorate as it moved through increased vertical wind shear. JTWC issued its final warning on Man-yi on November 19 as the system weakened to a tropical depression, while the JMA continued to monitor it until it was last noted at 06:00 UTC on the following day.
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.5mm (2.07in) of rain being recorded in Miyake, Tokyo.[25][26]
On May 29, the JTWC began tracking an area of convection located 406km (252mi) 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.[27] It was recognized as a low-pressure area by the Japan Meteorological Agency (JMA) early the next day,[28] before the agency upgraded it to a tropical depression at 06:00 UTC.[29] Later that day, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) on the depression since it had rapidly developed.[30] At 00:00 UTC the next day, the JTWC upgraded the system into a tropical depression, designating it as 02W.[31] Later, the JMA upgraded it into a tropical storm, and it was given the name Maliksi.[32] However, the JTWC reported that it did not intensify into a tropical storm as it was disorganized, with the circulation elongating.[33][34] At 21:00 UTC on May 31, the JTWC discontinued warnings on the system as it made landfall in Yangjiang, Guangdong.[35] 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.[36][37][38]
On July 13, the JTWC began tracking an area of convection 423mi (682km) 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.[45] At 06:00UTC of that day, the JMA designated the system as a tropical depression.[46] 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.[47] By 18:00UTC the next day, the JTWC upgraded the system into a tropical depression, designating it 03W.[48] However, they issued their last warning on the depression early the next day as it moved over Vietnam and rapidly weakened.[49] Later that day, the JMA stopped tracking the depression as it dissipated.[50]
On July 17, the JMA reported that a low-pressure area had formed east of Palau.[51] Shortly after, both the JMA and the JTWC followed suit and upgraded the tropical depression,[52] with the latter designating the system as 05W.[53] The PAGASA followed suit a few hours later, recognizing the system as a tropical depression and naming it Carina.[54] Early the next day, the depression intensified into a tropical storm, and was given the name Gaemi by the JMA.[55] 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.[56] 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 230km/h (145mph) by the JTWC, 10-minute sustained winds of 165km/h (105mph) by the JMA, and a central pressure of 935hPa (27.61inHg).[57][58] After stalling and executing a tight counter-clockwise loop near the coast,[59] 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.[60] Gaemi accelerated as it moved across the island and emerged into the Taiwan Strait just six hours after making landfall.[61] Soon after,[62] the JTWC ceased issuing advisories on the system as it made its final landfall at Xiuyu, Putian in Fujian Province.[63] Once inland, the JMA downgraded Gaemi into a tropical depression on July 26[64] and continued tracking the system until it dissipated at 18:00UTC of July 29.[65]
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$2.31 billion across several countries.[66][67][68]
On July 15, the JTWC started to monitor a persistent area of convection roughly 623km (385mi) 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.[69] At 06:00UTC the same day, the JMA designated the system as a low-pressure area.[70] Shortly after, the JMA designated it as a tropical depression.[52] 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.[71] The JTWC began issuing advisories on the system, classifying it as 04W.[72] It intensified into a tropical storm and was named Prapiroon by the JMA on July 21.[73][74] The center of Prapiroon made landfall near Wanning, Hainan, with 1-minute sustained winds of 95km/h (60mph) on July 22.[75] After making landfall, the storm maintained its well-defined eye while moving across central Hainan.[76] Prapiroon soon encountered high wind shear and a dry environment,[77] and by 6:30a.m. local time on July 23, it made its second landfall in Quảng Ninh, Vietnam.[78][79] After the system moved inland, both the JMA and the JTWC ceased monitoring it on July 24.[80][81]
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$32.9million in damages across several countries.[82][83][84]
On August 5, the JMA stated that a tropical depression had formed.[85] 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.[86] At 09:00UTC on August 6, the JTWC issued a TCFA on the disturbance, which was located 423mi (682km) north-northwest of Iwo Jima, along the eastern periphery of the monsoon gyre,[87] prior to it being designated as 06W.[88] The development of a central dense overcast and a ragged eye feature signified its intensification into a tropical storm,[89] leading the JMA to name it Maria on August 7.[90] Maria then turned northeastward,[91] and intensified into a severe tropical storm on August 8 due to a favorable environment for development.[92] Concurrently, the JTWC then reported that Maria had rapidly intensified into a minimal typhoon due to strong equatorward and poleward outflow.[93] However, Maria's wind field became more asymmetric, with its associated convection shifting northward,[94] causing Maria to weaken into a tropical storm on August 9.[95] Around 00:00 UTC on August 12, the storm made landfall Ōfunato,[96] a city in Iwate Prefecture, Japan with winds of 85km/h (50mph) before traversing northern Honshu and emerging into the Sea of Japan.[97] The JMA continued to monitor the system until it was last noted at 18:00 UTC on August 14.[98]
Record-breaking rainfall in Iwate Prefecture, with 19 inches (482.6mm) in Kuji and 12.6 inches (320.0mm) 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.[99]
On August 10, the JMA noted that a tropical depression had formed southeast of Severe Tropical Storm Maria.[100] A few hours later, the JTWC began tracking the system, noting that it could transition into a tropical cyclone despite intense wind shear.[101] Early the next day, they noted that the depression had transitioned into a subtropical cyclone.[102] As a result, a few hours later, the JMA named it Son-Tinh.[103] The next day, the JTWC noted that it had transitioned into a tropical storm, designating it 07W.[104] Soon after, the low-level circulation center became fully exposed with no deep convection existing near the center.[105] On August 13, Son-Tinh turned northwest along the western edge of a subtropical ridge.[106] Both the JMA and the JTWC stopped monitoring it as a tropical depression that day,[107] though the JMA continued to track it until it was last noted the following day.[108]
On August 3, the JTWC began tracking an area of convection 976km (606mi) east of Kadena Air Base on August 3.[109] At 18:00UTC the same day, the JMA designated the system as a low-pressure area.[110] However, the following day, the system was upgraded to a tropical depression.[111] The depression weakened and was last noted by the JMA on August 7.[112] 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.[113] A few hours later, they recognized the system as a tropical depression, designating it as 08W.[114] Soon after, the JMA noted that it had intensified into a tropical storm and named it Ampil.[115] 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.[116] The JMA reported that Ampil reached its peak intensity at 12:00 UTC that day with 10-minute sustained winds of 155km/h (100mph) and a central pressure of 950hPa (28.05inHg) before making its closest approach to Japan, and transitioned into an extratropical low on August 19.[117]
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.[118]
On 12 August, the JMA noted that a tropical depression formed southwest of Tropical Storm Son-Tinh.[119] 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.[120] Soon after, they recognized the system as a tropical depression, designating it as 09W.[121] 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,[122] although moderate vertical wind shear displaced the deep convection to the southeast.[123][124] 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.[125] 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.[126][127]
On August 17, a low-pressure area east of Taiwan developed into a tropical depression.[128][129] Soon after the development of a low-level circulation center and deep convection, the JTWC issued a TCFA for the disturbance.[130] A few hours later, PAGASA declared the system a tropical depression and named it Dindo,[131] while the JMA reported it had intensified into a tropical storm and named it Jongdari,[132] and the following day, the JTWC recognized it and designated it as 10W.[133] 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.[134] 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.[135][136] The JTWC assessed the cyclone as having dissipated and ceased issuing advisories on the system,[137] while the JMA continued to monitor the system until it was last noted on August 21.[138]
In some parts of the southern islands of Jeju, Jongdari accumulated 60–130 millimetres (2.4–5.1in) of rain as it moved closer to the coast.[139]
One person was killed as a result of Jongdari, when a 60-year-old man drowned in a port located on Heuksando, Sinan County. He was a crew member of a 43-ton fishing boat that docked in the port to seek refuge from the storm.[140]
On August 20, the JMA reported that a low-pressure area had formed near the Mariana Islands.[141] At midnight on August 21, both the JMA and the JTWC upgraded the tropical depression, with the latter designating the system as 11W.[142][143] 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.[144] A ragged eye-like feature appeared on satellite imagery, and on August 24,[145] both the JMA and the JTWC upgraded it to a minimal typhoon.[146] The JMA reported that Shanshan reached its peak intensity at 15:00 UTC on August 27, with 10-minute sustained winds of 175km/h (110mph) and a central pressure of 935hPa (27.61inHg).[147] Shanshan then turned northward and made landfall near Satsumasendai in Kagoshima Prefecture on August 29.[148][149] It then turned eastward along the northern periphery of a subtropical high,[150] quickly crossed the Seto Inland Sea, and made landfall over the northern tip of Shikoku on August 30.[151] Shanshan's circulation later diminished as its LLCC became disorganized.[152] 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.[153][154] The JMA continued to monitor the system until it dissipated at 18:00 UTC that day.[155]
The JMA issued special weather warnings for Kagoshima Prefecture, marking the first such emergency alert since Typhoon Nanmadol in 2022.[156] Shanshan caused six fatalities and damaged hundreds of structures throughout Japan.[157] In response to the severe weather, evacuation orders were issued for 996,299 people in Miyazaki Prefecture and 982,273 people in Kagoshima Prefecture.[158]
On August 30, the JMA reported the formation of a low-pressure area approximately 540km (330mi) northwest of Palau.[159][160] This broad low-pressure system began to organize and developed into a tropical depression on August 31.[161] The following day, PAGASA designated the system as a tropical depression and named it Enteng, as it formed within the Philippine Area of Responsibility.[162] Shortly after, the system was classified as Tropical Depression 12W.[163] As it intensified into a tropical storm, the JMA named it Yagi.[163][164] At 14:00 PHT (06:00 UTC) on September 2, Yagi made landfall in Casiguran, Aurora.[165] 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 260km/h (160mph) and a central pressure of 915 mbar (27.0 inHg).[166] It made landfall in Wenchang City, Hainan, and passed directly over Haikou, China, before moving into the open waters of the Gulf of Tonkin and making landfall over Xuwen County in Guangdong.[167] 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.[168] It continued to weaken rapidly as it moved southwest along the southeastern edge of a mid-level subtropical high,[169] becoming a tropical depression on September 8. The JMA monitored Yagi until it was last noted at 18:00 UTC that day.[170]
Yagi, combined with the effects of the southwest monsoon, resulted in at least 21 deaths, 22 injuries and 26 missing people in the Philippines.[171] Yagi also caused extensive damages, landslides and floods in Vietnam, Laos, Thailand and Myanmar and left 815 people dead.[172]
On September 1 at 21:00UTC, the remnants of Hurricane Hone moved into the basin from the Central Pacific about 280km (150nmi; 175mi) to the southwest of Midway Atoll,[173][174] where it was classified as a tropical depression by the JMA and as a subtropical depression by the JTWC the next day.[175] 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.[176][177] The JTWC stopped tracking it on September 4, determining the system had dissipated,[178] while the JMA continued to maintain Hone as a depression until it was last noted by the agency at 06:00 UTC on September 8.[179]
On September 2, the Japan Meteorological Agency noted that a tropical depression had formed over the open Pacific.[174] Despite unfavorable conditions, JTWC later issued a TCFA warning, citing that it will intensify in the upcoming days. Two days later, the JTWC designated the system as Tropical Depression 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. Satellite imagery depicted that the low-level circulation center (LLCC) of Leepi passed under strong upper-level southwesterly flow, indicated by a broad region of cirrus streamers. The storm did not last long, and JTWC later announced its final warning on September 6 as the system transitioned to an extratropical cyclone. The JMA later followed suit and issued its final advisory on 18:00 UTC of September 6.[citation needed]
On September 5, the JTWC noted an area of atmospheric convection 385km (239mi) east-northeast of Kosrae.[180] At 02:30 UTC on September 9, the JTWC issued a TCFA, noting that the system had become well-defined with formative banding in the eastern quadrants.[181] A few hours later, both the JMA and the JTWC followed suit and upgraded the tropical depression, with the latter designating the system as 14W.[182][183] On September 10, the depression intensified into a tropical storm and was named Bebinca by the JMA.[184] By 06:00 PHT (10:00 UTC) on September 13, Bebinca had entered the PAR and was subsequently named Ferdie by the PAGASA,[185] but just a few hours later, it exited the PAR.[186] The JMA reported that Bebinca reached its peak intensity at 00:00 UTC on September 15 with 10-minute sustained winds of 140km/h (85mph) and a central pressure of 965hPa (28.50inHg),[187] before eventually peaking at Category 1-equivalent intensity on the Saffir-Simpson scale with 1-minute sustained winds of 140km/h (85mph).[188] On September 16, at around 07:30 CST,[189] Bebinca made landfall in Lingang New City, Shanghai, China.[190] Shortly after landfall, the JTWC discontinued warnings on the system.[191] Inland, Bebinca quickly diminished to a severe tropical storm due to land interaction,[192] with the JMA tracking the system until it was last noted on September 18.[193]
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.[194] At least 30,000 households lost power.[195] Four homes were damaged, over 10,000 trees were damaged or uprooted and 53 hectares (132 acres) of farmland were flooded.[196] In China, two people were killed, while one person was injured.[197] The storm also left six people dead, eleven others injured and two people missing in the Philippines.[198]
On September 14, the JMA reported that a low-pressure area had formed approximately 596km (371mi) east-northeast of Manila, Philippines.[199][200] At 00:00 UTC on September 15, the JMA identified the system as a tropical depression.[201] On September 16, the PAGASA announced that the system had developed into a tropical depression and named Gener, as it formed within the PAR.[202] At 23:00 PHT (15:00 UTC) of the same day, the storm made landfall in Palanan, Isabela.[203][204] As it emerged over the South China Sea at 14:00 PHT (06:00 UTC) on the next day, the system displayed a broad disorganized low-level circulation.[205][206] On September 18, the JTWC canceled their TCFA due to an obscured low-level circulation with flaring convection, while the depression had drifted into an area of moderate vertical wind shear.[207] Earlier, two disturbances in the South China Sea near 98W and 99W were expected to merge and strengthen at 98W, closer to Vietnam, and shortly after, the system was classified as tropical depression 16W[208] Early the following day, the depression intensified into a tropical storm named Soulik, according to the JMA, while heading towards the northern coast of Vietnam, though it was gradually weakening.[209][210] Soulik made landfall in Vĩnh Linh District, Quảng Trị, Vietnam, at around 2 p.m. local time that day,[211] Soulik quickly weakened to a tropical depression due to land interaction,[212] and the JMA continued to monitor the system until it dissipated on September 20.[213]
On September 14, the JTWC noted an area of atmospheric convection196km (122mi) west-southwest of Andersen Air Force Base, Guam.[215] At 00:00 UTC on September 15, the JMA designated the system as a low-pressure area, having previously identified it as a tropical depression.[201][216] Shortly after, the depression intensified into a tropical storm and was namedPulasan by the JMA.[217] Pulasan was characterized by a large cyclonic circulation exceeding 690 miles (1,111km) and extensive gale-force winds, leading the JTWC to classify it as a monsoon depression at 06:00 UTC on September 16,[218] before later upgrading it to a tropical storm and designating it as 15W.[219] By 11:00 PHT (03:00 UTC) on September 17, Pulasan had entered the PAR and was subsequently named Helen by the PAGASA.[220] Pulasan exited the PAR on September 18 while traversing Okinawa Island in Japan's Ryukyu Archipelago as its circulation center strengthened with persistent convection.[221] On September 19, Pulasan made landfall in Zhoushan, Zhejiang, followed by a second landfall in Shanghai, just days after Typhoon Bebinca affected the Shanghai area.[222][223] Pulasan reemerged over the East China Sea, just off the coast of Jiangsu, China, showcasing a large, near-symmetric area of deep convection to the southeast on September 20.[224] By 06:00 UTC on September 21, the JMA reported that Pulasan had transitioned into an extratropical low as it moved east-northeastward and became embedded within the polar front jet to the north.[225][226]
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.[227]
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.[228] 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.[229] Igme later curved southwestwards, passing closely through Taiwan with the JMA last noting it as it became embedded in a front.[229] On September 22, the JTWC reported that Igme had strengthened into a tropical storm as it nears China, though reanalysis showed that it remained as a depression throughout its track.[229] JTWC later discontinued issuing bulletins on Igme after high vertical wind shear and the topographic interaction had caused to weaken significantly and dissipated after.[230]
On September 24, a tropical depression formed south of Japan, designated as 18W by the JTWC later that same day. The following day, 18W was upgraded by the JMA to become a tropical storm, thereby earning the name Cimaron. JTWC later followed suit and upgraded into a storm as it moved westward. Cimaron later moved northeastward, with the presence of moderate and high shear, which caused a weakening of a tropical depression. The environmental analysis also depicted that Cimaron is in an unfavorable environment, characterized by moderate poleward outflow and the presence of dry air.[231] At the latter part of September 27, JTWC reported that Cimaron became a remnant low due to its increasing vertical wind shear, resulted of eroding of the low-level circulation center (LLCC). The agency made its final warning as it absorbed within the frontal boundary.[232] The JMA downgraded the system to a low-pressure area on 18:00 UTC of the same day.
On September 25, a tropical depression formed near the Northern Mariana Islands. Later that day, JTWC started issuing advisories, stating that it would gradually intensify in the upcoming days. On September 26, it was classified as 19W by the JTWC as it was in a marginally favorable environment.[233] 19W developed into a tropical storm, thus gaining the name Jebi by the JMA. Satellite imagery shows that Jebi struggled to organize as moderate low-level wind shear was present.[234] The storm was downgraded back into a depression on September 28. However, Jebi regained tropical storm status for the second time as it moved northeastwards. On October 1, Jebi further strengthened into a Category 1-equivalent typhoon according to the JTWC, while JMA retained severe tropical storm status. Both agencies later issued their final warning the next day, as Jebi became an extratropical cyclone.
On September 26, the JMA reported a tropical depression 250km (155mi) south-southwest of Kadena Air Base, Japan,[235] characterised by a partially exposed low-level circulation centre with persistent deep convection in the southern semicircle and formative banding to the north.[236] On the next day, the PAGASA announced that the system had developed into a tropical depression, naming it Julian.[237] At 09:00 UTC, the JTWC upgraded the tropical depression, designating the system as 20W.[238] On September 28, the depression intensified into a tropical storm named Krathon by the JMA as it moves southwestward along the southeastern periphery of a mid-level subtropical high.[239] Early the next day, both the JMA and the JTWC upgraded it to a minimal typhoon after it had opened a broad, raggedly-defined eye.[240] which had since become cloud-filled,[241] Early on October 1, the JMA upgraded Krathon to a violent typhoon, estimating its peak intensity with a minimum central pressure of 915hPa (27.02inHg) and 10-minute maximum sustained winds of 195km/h (120mph).[242] On October 3 at 12:40p.m. local time, Krathon made landfall near Siaogang District in Kaohsiung, Taiwan as a weakening Category-1 typhoon.[243] After making landfall, the system rapidly slowed down and deteriorated, weakening rapidly to a depression.[244] The JMA continued to monitor the system as it emerged into the South China Sea before dissipating on October 4.[245][246]
Krathon caused landslides and flooding in parts of the Philippines, leaving five people dead and another missing. Eight others were injured.[247] Four deaths, 714 injuries and one missing person was also reported in Taiwan.[248]
A tropical depression formed near Guam on October 5. The following day, the JTWC issued a TCFA on the system and later upgraded it to Tropical Depression 21W. With convection flaring and persisting to the east of a partial low-level circulation center, the JTWC upgraded it to a tropical storm on October 7. Despite moving over warm waters, high wind shear further displaced the convection, weakening 21W to a tropical depression a few hours later. On October 8, the JTWC issued its last warning on 21W as it further weakened, with the agency expecting it to dissipate within the next 12 hours. The next day, the JMA upgraded 21W to a tropical storm, naming it Barijat. After a few hours, the JTWC reissued warnings for it. However, Barijat would begin its extratropical transition, prompting the said weather agency to issue its last warning the following day, at 09:00 UTC.
On October 19, the JMA upgraded a low-pressure area to a tropical depression north of Yap. Later, the JTWC issued a TCFA on the depression, having an elongated but consolidating low-level circulation center with convective banding wrapping around the northern and southern quadrants. The next day, JTWC upgraded it to Tropical Depression 22W. Soon after, it entered the PAR and was assigned the name Kristine by PAGASA. At 18:00 UTC October 21, the JMA upgraded the system to a tropical storm and named it Trami.[249] On October 23, the JMA upgraded it to a severe tropical storm as it was moving west-northwestwards through South China Sea.[250] At 12:30 AM PHT (16:30 UTC) of the next day, Trami made landfall over Divilacan, Isabela.[251] The following day, Trami emerged above the coastal waters of southern Ilocos Sur, leaving the remnants of a circulation center over Northern Luzon.[252] After traversing the South China Sea, Trami made landfall between Thua Thien-Hue and Da Nang in Central Vietnam at around 10 AM local time on October 27.[253] It then moved southwestward due to weak steering flow before making a U-turn and gradually moving toward the coastal regions of Vietnam.[254] The storm weakened into a low-pressure area before it formally dissipated on October 29.[255]
Trami caused extensive flooding and landslides across the Philippines and left at least 150 people dead and 30 others missing.[256] In Vietnam, Trami's strong winds caused trees and billboards to fall in Da Nang,[257][258] while heavy rainfall in Quang Tri province resulted in severe flooding of several bridges and left 18,000 people without power.[259]
On October 22, a low-pressure area formed southeast of Guam. Two days later, the JMA issued warnings as the disturbance became a tropical depression despite being in a marginal environment characterized by low wind shear, moderate equatorward outflow, and warm sea surface temperatures. At 03:00 UTC, the JTWC issued a TCFA for the system, with a weakly defined low-level circulation center wrapping around. Following this, the JTWC designated another area of convection as Invest 99W north of the system, with a low chance of forming. Early the next day, the JMA upgraded the depression to a tropical storm, gaining the name Kong-rey while the JTWC canceled the TCFA for the southern system and started to issue warnings for the northern system as a depression and designated it as 23W. At 07:30 PM PHT (11:30 UTC) on October 26, Kong-rey entered PAR and was assigned the name Leon by PAGASA. On October 29, Kong-rey rapidly intensified and became a Category-4 super typhoon the next day, according to the JTWC. At 1:40 PM PHT on October 31, it made landfall over Chenggong, Taitung.[260] Kong-rey later reemerged over the Taiwan Strait with a weakened convective structure.[261] Both agencies discontinued their warnings as Kong-rey transitioned into an extratropical cyclone on November 1.[262][263]
Kong-rey triggered strong winds and storm surges that flooded several houses in Gonzaga, Cagayan and Batanes,[264] and destroyed the historic Itbayat Church, the oldest church in Itbayat, Batanes.[265] In Taiwan, typhoon warnings were issued all around the country.[266] Multiple large wave warnings and a singular surge warnings were issued, all in the eastern coast of Taiwan.[267] At least three people were killed and 690 others were injured in Taiwan.[268]
On November 3, a tropical depression formed near Palau. That same day, the JTWC issued a TCFA for the system, indicating that the system is in a favorable environment for development. Later that, JTWC upgraded it to a Tropical Depression 24W. On November 4 early midnight, it entered the Philippine Area of Responsibility (PAR) and was given the domestic name Marce.[269] Shortly afterwards, it intensified into a tropical storm, gaining the name Yinxing by the JMA.[270] On November 5, the storm strengthened into a typhoon as it continues to organize in the Philippine Sea.[271] On November 7, the JTWC reported that the system had peaked as a Category4-equivalent super typhoon after Yinxing attained 1-minute sustained winds of 240km/h (150mph),[272] and a central pressure of 940hPa (27.76inHg).[273] Later that day, Yinxing made landfall on Santa Ana, Cagayan, around 3:40 PM PHT (07:40 UTC).[274] After crossing the Babuyan Channel, Yinxing made its second landfall in Sanchez Mira, Cagayan at 9:00 PM PHT (13:00 UTC).[275] The storm reemerged over the South China Sea on November 8, with minimal weakening due to mountainous terrain interaction.[276] Yinxing would later restrengthen, featuring a 22 miles (35km) oblong eye and an eye temperature of 11.8°C (53.2°F). As a result, the JTWC assessed the storm's winds to have reached 205km/h (125mph) on November 9.[277] However, Yinxing later weakened again for the second time, downgrading into a tropical storm on November 11.[278]
Yinxing caused extensive damage across northern Luzon[279] and left one person dead and another missing.[280]
A low pressure area formed east of the Philippines on November 8.[281] At 8 AM PHT (00:00 UTC) November 9, the tropical depression was named Nika as it is inside the Philippine Area of Responsibility (PAR).[282] The same day, the JTWC issued a TCFA for the system, indicating that the system is in a favorable environment for development. Soon, the JTWC designated the system Tropical Depression 26W. At 18:00 UTC on the same day, the JMA classified the system as a tropical depression,[283] and it moved into the Philippine Area of Responsibility, where PAGASA named it Nika the following day.[284] At 06:00 UTC the same day, the JMA upgraded the system to a tropical storm named Toraji as it moves westwards.[285] On November 10, the JMA upgraded the system to a typhoon,[286] and the following day, Toraji made landfall on Dilasag, Aurora, on Luzon Island at around 8:10 AM PHT (00:10 UTC),[287] before moving inland over mountainous terrain, which caused significant weakening.[288] Toraji emerged over the South China Sea off the coast of Magsingal, Ilocos Sur later that evening.[289] The JTWC issued its final warning on November 14 as it weakened to a tropical depression.[290] While the JMA continued to monitor the system until it was last noted at 06:00 UTC on November 15.[291]
Toraji caused extensive damage across northern Luzon and left two people dead and two others missing in the Philippines.[292][293]
A tropical depression formed near Marshall Islands on November 9. Soon, the JTWC designated the system Tropical Depression 25W, then later in the afternoon JMA upgraded it into a tropical storm and named it Man-yi, with the JTWC following suit after.[294] On November 14, at 20:00 PHT (12:00 UTC), Man-yi entered the Philippine Area of Responsibility and was assigned the name Pepito.[295] Later the same day, the JMA upgraded the storm to a minimal typhoon before the JTWC followed suit.[296] Still on the same day, it subsequently peaked as a Category5-equivalent super typhoon on the Saffir-Simpson scale, with one-minute sustained winds of 260km/h (160mph) and a central pressure of 920 hPa (27.17 inHg). As it moved west-northwestward, Man-yi made landfall in Panganiban, Catanduanes, at around 9:40 PM PHT (13:40 UTC) on November 16.[297] The following day, Man-yi made its second landfall in Dipaculao, Aurora, on Luzon Island at around 3:20 PM PHT (07:20 UTC) as a Category-4 super typhoon.[11] Man-yi later accelerated northwestward over the South China Sea where it started to weaken into a severe tropical storm. It then continued to deteriorate as it moved through increased vertical wind shear.[298] JTWC issued its final warning on Man-yi on November 19 as the system weakened to a tropical depression, while the JMA continued to monitor it until it was last noted at 06:00 UTC on the following day.[299]
Man-yi caused extensive damage in Catanduanes[300] and left eight people dead in the Philippines.[301][302]
A tropical depression formed east of Micronesia on November 9. The next day, the JMA issued a warning in anticipation of the tropical cyclone developing into a tropical storm and potentially a typhoon. On November 11, the JTWC upgraded the system to a tropical depression, designating it as 27W. Early the next day, the depression intensified into a tropical storm and received the name Usagi from the JMA. Meanwhile, the system entered the Philippine Area of Responsibility, and PAGASA named it Ofel.[303] On November 13, Usagi rapidly intensified into a Category 4-equivalent typhoon.[304] On November 14, it made landfall in Baggao, Cagayan, on Luzon Island at around 1:30 PM PHT (05:30 UTC).[305] After crossing northern Luzon, Usagi emerged into the Babuyan Channel, moving northwestwards and then passing close to Babuyan Islands and northern Cagayan,[306] causing to downgrade into a severe tropical storm.[307]
Usagi left two people missing in the Philippines.[308]
On August 18, the JMA reported the formation of a low-pressure area over the Philippine Sea.[309] The next day, it was designated as a tropical depression but weakened to a low-pressure area by August 22.[310] The following day, the JMA re-designated it as a tropical depression as it turned southward.[311] Over the next few days, the depression gradually moved southwestward while Typhoon Shanshan approached Japan from the west.[312] The JMA continued to monitor the depression until it dissipated on August 26.[313]
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.[314][315]
A tropical depression briefly developed southeast of Japan on August 20.[316] Thereafter, it was designated as an extratropical low while drifting southeastward.[317]
A tropical depression briefly formed southeast of Typhoon Shanshan on August 30 and was last noted by the JMA at 18:00 UTC.[318][159]
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 where it made landfall before dissipating.
On September 25, the JTWC marked a subtropical storm near Tokyo and designated it with an invest tag 96W, stating the system has a low chance of transitioning to a tropical system. The next day, the agency last noted the system as it merged with a frontal boundary while moving to the east. The JMA did not recognize the system.
A tropical depression formed west of Guam on September 26. The depression did not last long, dissipating the next day, with its remnants moving northwards across the Philippine Sea.
Another tropical depression formed west of Guam on October 6. The depression moved eastwards as it interacted with a nearby Tropical Depression that would later become Tropical Storm Barijat. The JMA last noted it the next day as the depression became embedded in the latter's circulation.
A tropical depression formed in northeast of Mukojima on October 12. JTWC classified it as a subtropical depression on October 13. JTWC upgraded it into a subtropical storm on October 14. At the same time, JMA declared the system had transitioned to a developing extratropical low.
A tropical depression formed north of Micronesia on October 16. The depression did not last long, and JMA downgraded the system into a low pressure area the next day.
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.[319] The names of significant tropical cyclones are retired by both PAGASA and the Typhoon Committee.[320] 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.[320]
A tropical cyclone is named when it has 10-minute sustained winds of 65km/h (40mph).[321] 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.[322] Retired names, if any, will be announced by the WMO in 2025, though replacement names will be announced in 2026. During the season, the names Pulasan, Krathon and Yinxing were used for the first time after they replaced Rumbia, Mangkhut and Yutu, which were retired following the 2018 season. The next 28names on the naming list are listed here along with their international numeric designation, if they are used.
This season, PAGASA will use its own naming scheme for storms that are active in their self-defined area of responsibility.[323] 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.[323] 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.[323] The name Aghon was used for the first time this year.
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.
1 2 A super typhoon is an unofficial category used by the Joint Typhoon Warning Center (JTWC) for a typhoon with winds of at least 240km/h (150mph).[2]
↑ The Joint Typhoon Warning Center is a joint United States Navy– United States Air Force task force that issues tropical cyclone warnings for the western Pacific Ocean and other regions.[1]
Related Research Articles
The 2008 Pacific typhoon season was a below average season which featured 22 named storms, eleven typhoons, and two super typhoons. The season had no official bounds; it ran year-round in 2008, but most tropical cyclones tend to form in the northwestern Pacific Ocean between May and November. These dates conventionally delimit the period of each year when most tropical cyclones form in the northwestern Pacific Ocean.
The 2012 Pacific typhoon season was a slightly above average season that produced 25 named storms, fourteen typhoons, and four intense typhoons. It was a destructive and the second consecutive year to be the deadliest season, primarily due to Typhoon Bopha which killed 1,901 people in the Philippines. It was an event in the annual cycle of tropical cyclone formation, in which tropical cyclones form in the western Pacific Ocean. The season ran throughout 2012, though most tropical cyclones typically develop between May and October. The season's first named storm, Pakhar, developed on March 28, while the season's last named storm, Wukong, dissipated on December 29. The season's first typhoon, Guchol, reached typhoon status on June 15, and became the first super typhoon of the year on June 17.
The 2013 Pacific typhoon season was a devastating and catastrophic season that was the most active since 2004, and the deadliest since 1975. It featured Typhoon Haiyan, one of the most powerful storms in history, as well as one of the strongest to make landfall on record. It featured 31 named storms, 13 typhoons, and five super typhoons. The season's first named storm, Sonamu, developed on January 4 while the season's last named storm, Podul, dissipated on November 15. Collectively, the storms caused 6,829 fatalities, while total damage amounted to at least $26.41 billion (USD), making it, at the time, the costliest Pacific typhoon season on record, until it was surpassed five years later. As of 2024, it is currently ranked as the fifth-costliest typhoon season.
The 2015 Pacific typhoon season was a slightly above average season that produced twenty-seven tropical storms, eighteen typhoons, and nine super typhoons. The season ran throughout 2015, though most tropical cyclones typically develop between May and November. The season's first named storm, Mekkhala, developed on January 15, while the season's last named storm, Melor, dissipated on December 17. The season saw at least one named tropical system forming in each of every month, the first time since 1965. Similar to the previous season, this season saw a high number of super typhoons. Accumulated cyclone energy (ACE) during 2015 was extremely high, the third highest since 1970, and the 2015 ACE has been attributed in part to anthropogenic warming, and also the 2014-16 El Niño event, that led to similarly high ACE values in the East Pacific.
The 2016 Pacific typhoon season is considered to have been the fourth-latest start for a Pacific typhoon season since reliable records began. It was an average season, with a total of 26 named storms, 13 typhoons, and six super typhoons. The season ran throughout 2016, though typically most tropical cyclones develop between May and October. The season's first named storm, Nepartak, developed on July 3, while the season's last named storm, Nock-ten, dissipated on December 28.
The 2017 Pacific typhoon season was a below-average season in terms of accumulated cyclone energy and the number of typhoons and super typhoons, and the first since the 1977 season to not produce a Category 5-equivalent typhoon on the Saffir–Simpson scale. The season produced a total of 27 named storms, 11 typhoons, and only two super typhoons, making it an average season in terms of storm numbers. It was an event in the annual cycle of tropical cyclone formation, in which tropical cyclones form in the western Pacific Ocean. The season runs throughout 2017, though most tropical cyclones typically develop between May and October. The season's first named storm, Muifa, developed on April 25, while the season's last named storm, Tembin, dissipated on December 26. This season also featured the latest occurrence of the first typhoon of the year since 1998, with Noru reaching this intensity on July 23.
The 2018 Pacific typhoon season was at the time, the costliest Pacific typhoon season on record, until the record was beaten by the following year. The season was well above-average, producing twenty-nine storms, thirteen typhoons, seven super typhoons and six Category 5 tropical cyclones. The season ran throughout 2018, though most tropical cyclones typically develop between May and October. The season's first named storm, Bolaven, developed on January 3, while the season's last named storm, Man-yi, dissipated on November 28. The season's first typhoon, Jelawat, reached typhoon status on March 29, and became the first super typhoon of the year on the next day.
The 2020 Pacific typhoon season was the first of a series of four below average Pacific typhoon seasons, and became the first with below-average tropical cyclone activity since 2014, with 23 named storms, 10 of which became typhoons and only 2 became super typhoons. This low activity was a consequence of La Niña that persisted from the summer of the year. It had the sixth-latest start in the basin on record, slightly behind 1973, and was the first to start that late since 2016. The first half of the season was unusually inactive, with only four systems, two named storms and one typhoon at the end of July. Additionally, the JTWC recorded no tropical cyclone development in the month of July, the first such occurrence since reliable records began. Despite that, this season featured Super Typhoon Goni, which made the strongest landfall worldwide in terms of 1-minute wind speed. The season's first named tropical cyclone, Vongfong, developed on May 8, while the season's last named tropical cyclone, Krovanh, dissipated on December 24. However, the season's last system was an unnamed tropical depression which dissipated on December 29.
Severe Tropical Storm Rumbia, known in the Philippines as Tropical Storm Gorio, was a tropical cyclone that brought widespread flooding in areas of the Philippines and China late June and early July 2013. The sixth internationally named storm of the season, Rumbia formed from a broad area of low pressure situated in the southern Philippine Sea on June 27. Steadily organizing, the initial tropical depression moved towards the northwest as the result of a nearby subtropical ridge. On June 28, the disturbance strengthened to tropical storm strength, and subsequently made its first landfall on Eastern Samar in the Philippines early the following day. Rumbia spent roughly a day moving across the archipelago before emerging into the South China Sea. Over open waters, Rumbia resumed strengthening, and reached its peak intensity with winds of 95 km/h (50 mph) on July 1, ranking it as a severe tropical storm. The tropical cyclone weakened slightly before moving ashore the Leizhou Peninsula late that day. Due to land interaction, Rumbia quickly weakened into a low pressure area on July 2 and eventually dissipated soon afterwards.
Most of the tropical cyclones of the 2013 Pacific typhoon season formed between May and November of that year. The scope of this article is the Pacific Ocean north of the equator, between 100°E and the International Date Line. Tropical storms which form in the Western Pacific basin are assigned a name by the Japan Meteorological Agency (JMA). Tropical depressions forming in this basin are given a number with a "W" suffix by the United States' Joint Typhoon Warning Center (JTWC). The Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) assigns names to tropical cyclones that enter or form in the Philippine area of responsibility, but these names are not in common use outside the Philippines.
This timeline documents all of the events of the 2014 Pacific typhoon season. Most of the tropical cyclones forming between May and November. The scope of this article is limited to the Pacific Ocean, north of the equator between 100°E and the International Date Line. Tropical storms that form in the entire Western Pacific basin are assigned a name by the Japan Meteorological Agency. Tropical depressions that form in this basin are given a number with a "W" suffix by the United States' Joint Typhoon Warning Center. In addition, the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) assigns names to tropical cyclones that enter or form in the Philippine area of responsibility. These names, however, are not in common use outside of the Philippines.
This timeline documents all of the events of the 2012 Pacific typhoon season. The scope of this article is limited to the Pacific Ocean, north of the equator between 100°E and the International Date Line. During the season, 34 systems were designated as tropical depressions by either the Japan Meteorological Agency (JMA), the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA), the Joint Typhoon Warning Center (JTWC), or other National Meteorological and Hydrological Services such as the China Meteorological Administration and the Hong Kong Observatory. Since the JMA runs the Regional Specialized Meteorological Centre (RSMC) for the Western Pacific, they assigned names to tropical depressions which developed into tropical storms in the basin. PAGASA also assigned local names to systems which are active in their area of responsibility; however, these names are not in common use outside of the Philippines.
Typhoon Hagupit known in the Philippines as Super Typhoon Ruby, was the second most intense tropical cyclone in 2014. Hagupit particularly impacted the Philippines in early December while gradually weakening, killing 18 people and causing $114 million of damage in the country. Prior to making landfall, Hagupit was considered the worst threat to the Philippines in 2014, but it was significantly smaller than 2013's Typhoon Haiyan.
This timeline documents all of the events of the 2015 Pacific typhoon season. Most of the tropical cyclones formed between May and November. The scope of this article is limited to the Pacific Ocean, north of the equator between 100°E and the International Date Line. This area, called the Western Pacific basin, is the responsibility of the Japanese Meteorological Agency (JMA). They host and operate the Regional Specialized Meteorological Center (RSMC), located in Tokyo. The Japanese Meteorological Agency (JMA) is also responsible for assigning names to all tropical storms that are formed within the basin. However, any storm that enters or forms in the Philippine Area of Responsibility (PAR) will be named by the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) using a local name. Also of note - the Western Pacific basin is monitored by the United States' Joint Typhoon Warning Center (JTWC), which gives all Tropical depressions a number with a "W" suffix.
Typhoon Nock-ten, known in the Philippines as Super Typhoon Nina, was the strongest Christmas Day tropical cyclone worldwide in terms of 1-minute sustained winds. Forming as a tropical depression southeast of Yap and strengthening into the twenty-sixth tropical storm of the annual typhoon season on December 21, 2016, Nock-ten intensified into the thirteenth typhoon of the season on December 23. Soon afterwards, the system underwent explosive intensification and became a Category 5-equivalent super typhoon early on December 25. Nock-ten weakened shortly afterwards before making eight landfalls over the Philippines. The typhoon weakened rapidly due to the landfalls as it entered the South China Sea on December 26, turned southwest, and ultimately dissipated on December 28 due to the winter monsoon.
The 2021 Pacific typhoon season was the second consecutive season to have below average tropical cyclone activity, with twenty-two named storms, and was the least active since 2011. Nine became typhoons, and five of those intensified into super typhoons. This low activity was caused by a strong La Niña that had persisted from the previous year. The season's first named storm, Dujuan, developed on February 16, while the last named storm, Rai, dissipated on December 21. The season's first typhoon, Surigae, reached typhoon status on April 16. It became the first super typhoon of the year on the next day, also becoming the strongest tropical cyclone in 2021. Surigae was also the most powerful tropical cyclone on record in the Northern Hemisphere for the month of April. Typhoons In-fa and Rai are responsible for more than half of the total damage this season, adding up to a combined total of $2.02 billion.
The 2022 Pacific typhoon season was the third consecutive season to have below average tropical cyclone activity, with twenty-five named storms forming. Of the tropical storms, ten became typhoons, and three would intensify into super typhoons. The season saw near-average activity by named storm count, although many of the storms were weak and short-lived, particularly towards the end of the season. This low activity was caused by an unusually strong La Niña that had persisted from 2020. The season's first named storm, Malakas, developed on April 6, while the last named storm, Pakhar, dissipated on December 12. The season's first typhoon, Malakas, reached typhoon status on April 12. The season ran throughout 2022, though most tropical cyclones typically develop between May and October. Tropical storms Megi and Nalgae were responsible for more than half of the casualties, while typhoons Hinnamnor and Nanmadol both caused $1 billion in damages.
The 2023 Pacific typhoon season was the fourth and final consecutive below-average season and became the third-most inactive typhoon season on record in terms of named storms, with just 17 named storms developing, only ahead of 2010 and 1998. Despite the season occurring during an El Niño event, which typically favors activity in the basin, activity was abnormally low. This was primarily due to a consistent period of negative PDO, which typically discourages tropical storm formation in this basin. The season was less active than the 2023 Atlantic hurricane season in terms of named storms, the fourth such season on record, after 2005, 2010 and 2020. The season's number of storms also did not exceed that of the 2023 Pacific hurricane season. Only ten became typhoons, with four strengthening further into super typhoons. However, it was very destructive, primarily due to Typhoon Doksuri which devastated the northern Philippines, Taiwan, and China in July, becoming the costliest typhoon on record as well as the costliest typhoon to hit mainland China, and Typhoon Haikui in September, which devastated China, Taiwan, and Hong Kong. The season was less active in Southeast Asia, with no tropical storm making landfall in mainland Vietnam.
Typhoon Chanthu, known in the Philippines as Super Typhoon Kiko, was the second most intense tropical cyclone worldwide in 2021 after Typhoon Surigae in April. It impacted the Cagayan Valley region of the Philippines and became the strongest typhoon to affect the Batanes province since Typhoon Meranti in 2016. The twenty-ninth tropical depression, fourteenth named storm and fourth typhoon of the 2021 Pacific typhoon season, Chanthu originated from a disturbance well east of the Philippine islands on September 5 which organized into a tropical depression later that day. By the next day, the depression had formed into a mature tropical storm which began to explosively intensify by September 7, featuring a pinhole eye on satellite, characteristic of rapidly intensifying storms. Chanthu became a Category 5-equivalent super typhoon by September 8, the highest category on the Saffir–Simpson scale. Subsequent eyewall replacement cycles caused intensity fluctuations, but on September 10, Chanthu peaked with 1-minute sustained winds of 285 km/h (180 mph) just northeast of extreme northeastern Luzon. The typhoon passed very near the Babuyan Islands before passing directly over Ivana, Batanes as a weakening but still powerful Category 5-equivalent super typhoon. Chanthu continued steadily weakening as it passed just east of Taiwan and eventually stalled just east of Shanghai, China. The storm eventually made its second and final landfall near Ikitsuki, Nagasaki in Japan, before crossing the country's mountainous terrain and becoming an extratropical cyclone on September 18. Chanthu then continued eastward and curved southward, before dissipating on September 20. According to Aon Benfield, economic losses totaled US$30 million.
Severe Tropical Storm Kompasu, known in the Philippines as Severe Tropical Storm Maring was a very large and deadly tropical cyclone that affected the Philippines, Taiwan, and southeast China. Part of the 2021 Pacific typhoon season, Kompasu originated from an area of low pressure east of the Philippines on 6 October 2021. The Japan Meteorological Agency (JMA) classified it as a tropical depression that day. A day later, the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) classified it as a tropical depression, naming it Maring. The cyclone was initially heavily disorganised, competing with another vortex, Tropical Depression Nando. Eventually, Maring became dominant, and the JMA reclassified it as a tropical storm, naming it Kompasu. Kompasu made landfall in Cagayan, Philippines, on 11 October 2021, and two days later, the storm made landfall in Hainan, China. The cyclone dissipated on 14 October 2021 while located over Vietnam.
↑ Frequently Asked Questions (Report). Joint Typhoon Warning Center. August 13, 2012. Archived from the original on October 4, 2013. Retrieved September 22, 2012.
1 2 Seasonal Climate Outlook January – June 2024(PDF) (Report). Philippine Atmospheric Geophysical and Astronomical Services Administration. January 15, 2024. Archived(PDF) from the original on June 10, 2024. Retrieved July 19, 2024.
1 2 161th Climate Forum July–December 2024(PDF) (Seasonal Climate Outlook). Philippine Atmospheric Geophysical and Astronomical Services Administration. June 26, 2024. Archived(PDF) from the original on July 19, 2024. Retrieved July 19, 2024.
↑ Warning and Summary 221800 (Report). Tokyo, Japan: Japan Meteorological Agency. May 22, 2024. Archived from the original on May 22, 2024. Retrieved May 22, 2024.
↑ Warning and Summary 300000 (Report). Tokyo, Japan: Japan Meteorological Agency. May 30, 2024. Archived from the original on May 30, 2024. Retrieved May 31, 2024.
↑ Warning and Summary 300600 (Report). Tokyo, Japan: Japan Meteorological Agency. May 30, 2024. Archived from the original on May 31, 2024. Retrieved May 31, 2024.
↑ Warning and Summary 130600 (Report). Tokyo, Japan: Japan Meteorological Agency. May 30, 2024. Archived from the original on July 13, 2024. Retrieved July 13, 2024.
↑ Warning and Summary 151800 (Report). Tokyo, Japan: Japan Meteorological Agency. July 15, 2024. Archived from the original on July 15, 2024. Retrieved July 15, 2024.
↑ Warning and Summary 170600 (Report). Tokyo, Japan: Japan Meteorological Agency. July 17, 2024. Archived from the original on July 17, 2024. Retrieved July 17, 2024.
1 2 Warning and Summary 190600 (Report). Tokyo, Japan: Japan Meteorological Agency. July 19, 2024. Archived from the original on July 19, 2024. Retrieved June 19, 2024.
↑ Warning and Summary 150600 (Report). Tokyo, Japan: Japan Meteorological Agency. July 15, 2024. Archived from the original on July 15, 2024. Retrieved July 15, 2024.
↑ Warning and Summary 241800 (Report). Tokyo, Japan: Japan Meteorological Agency. July 15, 2024. Archived from the original on July 25, 2024. Retrieved July 15, 2024.
↑ Warning and Summary 050600 (Report). Tokyo, Japan: Japan Meteorological Agency. August 5, 2024. Archived from the original on August 5, 2024. Retrieved August 5, 2024.
↑ Warning and Summary 141800 (Report). Tokyo, Japan: Japan Meteorological Agency. August 14, 2024. Archived from the original on August 15, 2024. Retrieved August 14, 2024.
↑ Warning and Summary 141800 (Report). Tokyo, Japan: Japan Meteorological Agency. August 14, 2024. Archived from the original on August 15, 2024. Retrieved August 12, 2024.
↑ Warning and Summary 031800 (Report). Tokyo, Japan: Japan Meteorological Agency. August 3, 2024. Archived from the original on August 3, 2024. Retrieved August 3, 2024.
↑ Warning and Summary 040000 (Report). Tokyo, Japan: Japan Meteorological Agency. August 4, 2024. Archived from the original on August 4, 2024. Retrieved August 4, 2024.
↑ Warning and Summary 071800 (Report). Tokyo, Japan: Japan Meteorological Agency. August 10, 2024. Archived from the original on August 8, 2024. Retrieved August 7, 2024.
↑ Warning and Summary 110600 (Report). Tokyo, Japan: Japan Meteorological Agency. August 11, 2024. Archived from the original on August 11, 2024. Retrieved August 11, 2024.
↑ Warning and Summary 120000 (Report). Tokyo, Japan: Japan Meteorological Agency. August 12, 2024. Archived from the original on August 12, 2024. Retrieved August 12, 2024.
↑ Warning and Summary 170000 (Report). Tokyo, Japan: Japan Meteorological Agency. August 17, 2024. Archived from the original on August 17, 2024. Retrieved August 17, 2024.
↑ Warning and Summary 170600 (Report). Tokyo, Japan: Japan Meteorological Agency. August 17, 2024. Archived from the original on August 17, 2024. Retrieved August 17, 2024.
↑ Warning and Summary 211200 (Report). Tokyo, Japan: Japan Meteorological Agency. August 21, 2024. Archived from the original on August 21, 2024. Retrieved August 21, 2024.
↑ Warning and Summary 211800 (Report). Tokyo, Japan: Japan Meteorological Agency. August 21, 2024. Archived from the original on August 22, 2024. Retrieved August 21, 2024.
↑ Warning and Summary 011800 (Report). Tokyo, Japan: Japan Meteorological Agency. September 1, 2024. Archived from the original on September 1, 2024. Retrieved September 1, 2024.
1 2 Warning and Summary 301800 (Report). Tokyo, Japan: Japan Meteorological Agency. August 30, 2024. Archived from the original on August 31, 2024. Retrieved August 30, 2024.
↑ Warning and Summary 310000 (Report). Tokyo, Japan: Japan Meteorological Agency. August 31, 2024. Archived from the original on August 31, 2024. Retrieved August 31, 2024.
↑ Warning and Summary 081800 (Report). Tokyo, Japan: Japan Meteorological Agency. September 8, 2024. Archived from the original on September 8, 2024. Retrieved September 8, 2024.
↑ Warning and Summary 086000 (Report). Tokyo, Japan: Japan Meteorological Agency. September 8, 2024. Archived from the original on September 8, 2024. Retrieved September 8, 2024.
↑ Warning and Summary 091200 (Report). Tokyo, Japan: Japan Meteorological Agency. September 9, 2024. Archived from the original on September 9, 2024. Retrieved September 9, 2024.
↑ Tianchi, Zhang. "暴风雨圈直击！"贝碧嘉"或为1949年以来登陆上海最强台风"[Storm circle hits! "Bebejia" may be the strongest typhoon to land in Shanghai since 1949]. MSN. Retrieved September 16, 2024.
↑ Warning and Summary 180000 (Report). Tokyo, Japan: Japan Meteorological Agency. September 18, 2024. Archived from the original on September 20, 2024. Retrieved September 18, 2024.
↑ Warning and Summary 141800 (Report). Tokyo, Japan: Japan Meteorological Agency. September 14, 2024. Archived from the original on September 15, 2024. Retrieved September 14, 2024.
1 2 Warning and Summary 150000 (Report). Tokyo, Japan: Japan Meteorological Agency. September 15, 2024. Archived from the original on September 15, 2024. Retrieved September 15, 2024.
↑ Warning and Summary 200600 (Report). Tokyo, Japan: Japan Meteorological Agency. September 20, 2024. Archived from the original on September 20, 2024. Retrieved September 20, 2024.
↑ Warning and Summary 260600 (Report). Tokyo, Japan: Japan Meteorological Agency. September 26, 2024. Archived from the original on September 26, 2024. Retrieved September 26, 2024.
↑ Warning and Summary 041200 (Report). Tokyo, Japan: Japan Meteorological Agency. October 4, 2024. Archived from the original on October 4, 2024. Retrieved October 4, 2024.
↑ Warning and Summary 291800 (Report). Tokyo, Japan: Japan Meteorological Agency. October 29, 2024. Archived from the original on October 30, 2024. Retrieved October 29, 2024.
↑ Warning and Summary 080000 (Report). Tokyo, Japan: Japan Meteorological Agency. November 8, 2024. Archived from the original on November 9, 2024. Retrieved November 8, 2024.
↑ Warning and Summary 081800 (Report). Tokyo, Japan: Japan Meteorological Agency. November 8, 2024. Archived from the original on November 9, 2024. Retrieved November 8, 2024.
↑ Warning and Summary 150600 (Report). Tokyo, Japan: Japan Meteorological Agency. November 15, 2024. Archived from the original on November 15, 2024. Retrieved November 15, 2024.
↑ Warning and Summary 200600 (Report). Tokyo, Japan: Japan Meteorological Agency. November 20, 2024. Archived from the original on November 20, 2024. Retrieved November 20, 2024.
↑ Warning and Summary 181800 (Report). Tokyo, Japan: Japan Meteorological Agency. August 18, 2024. Archived from the original on August 19, 2024. Retrieved August 18, 2024.
↑ Warning and Summary 190000 (Report). Tokyo, Japan: Japan Meteorological Agency. August 19, 2024. Archived from the original on August 19, 2024. Retrieved August 19, 2024.
↑ Warning and Summary 230000 (Report). Tokyo, Japan: Japan Meteorological Agency. August 23, 2024. Archived from the original on August 23, 2024. Retrieved August 23, 2024.
↑ Warning and Summary 241200 (Report). Tokyo, Japan: Japan Meteorological Agency. August 24, 2024. Archived from the original on August 24, 2024. Retrieved August 24, 2024.
↑ Warning and Summary 260600 (Report). Tokyo, Japan: Japan Meteorological Agency. August 26, 2024. Archived from the original on August 26, 2024. Retrieved August 26, 2024.
↑ Warning and Summary 190600 (Report). Tokyo, Japan: Japan Meteorological Agency. August 19, 2024. Archived from the original on August 19, 2024. Retrieved August 19, 2024.
↑ Warning and Summary 191800 (Report). Tokyo, Japan: Japan Meteorological Agency. August 19, 2024. Archived from the original on August 20, 2024. Retrieved August 19, 2024.
↑ Warning and Summary 201800 (Report). Tokyo, Japan: Japan Meteorological Agency. August 20, 2024. Archived from the original on August 21, 2024. Retrieved August 20, 2024.
↑ Warning and Summary 210000 (Report). Tokyo, Japan: Japan Meteorological Agency. August 21, 2024. Archived from the original on August 21, 2024. Retrieved August 21, 2024.
↑ Warning and Summary 300000 (Report). Tokyo, Japan: Japan Meteorological Agency. August 30, 2024. Archived from the original on August 30, 2024. Retrieved August 30, 2024.
↑ "2024年7月全國自然災害狀況". Ministry of Emergency Management (MEM) (China) (in Chinese). August 8, 2024. Archived from the original on November 18, 2024. Retrieved December 10, 2024.
↑ Situational Report No. 11 for TCs Marce (2024)(PDF) (Report). Quezon City, Philippines: National Disaster Risk Reduction and Management Council. November 13, 2024. Retrieved November 13, 2024.
This page is based on this Wikipedia article Text is available under the CC BY-SA 4.0 license; additional terms may apply. Images, videos and audio are available under their respective licenses.
![Four tropical systems active on November 11: Tropical Storm Yinxing [MARCE] (bottom left); Severe Tropical Storm Toraji [NIKA] (upper left); Tropical Storm Usagi [OFEL] (center right); and Tropical Storm Man-yi [PEPITO] (very right). Yinxing, Toraji, 27W and Man-yi on 11 November, 2024.jpg](http://upload.wikimedia.org/wikipedia/commons/thumb/8/86/Yinxing%2C_Toraji%2C_27W_and_Man-yi_on_11_November%2C_2024.jpg/400px-Yinxing%2C_Toraji%2C_27W_and_Man-yi_on_11_November%2C_2024.jpg)
