2026 Pacific typhoon season
From Wikipedia, the free encyclopedia
The 2026 Pacific typhoon season is an ongoing event in the annual cycle of tropical cyclone formation in the western Pacific Ocean. The season runs throughout 2026, although most tropical cyclones typically develop between May and October. The first named storm of the season, Nokaen, developed on January 15, marking the first named storm to form in January since Pabuk during the 2019 season, and the earliest start to a Pacific typhoon season since then. The season's first typhoon, Sinlaku, reached typhoon intensity on April 10 and became the season's first super typhoon on April 12. So far, the season has been very active, with 16 named storms having formed by August 9, making it the most active season by this point since 1971.[1]
(10-minute sustained)
| 2026 Pacific typhoon season | |
|---|---|
 Season summary map | |
| Seasonal boundaries | |
| First system formed | January 13, 2026 |
| Last system dissipated | Season ongoing |
| Strongest storm | |
| Name | Sinlaku |
| • Maximum winds | 215 km/h (130 mph) (10-minute sustained) |
| • Lowest pressure | 905 hPa (mbar) |
| Seasonal statistics | |
| Total depressions | 23, 2 unofficial[nb 1][nb 2] |
| Total storms | 16 |
| Typhoons | 5 |
| Super typhoons | 3 (unofficial)[nb 3][nb 4] |
| Total fatalities | 135+ total (+6 indirect) |
| Total damage | > $5.76 billion (2026 USD) |
| Related articles | |
The scope of this article is limited to the Pacific Ocean north of the equator between 100°E and the 180th meridian. Within the northwestern Pacific Ocean, two separate agencies assign names to tropical cyclones, which can result in a system having two names. The Japan Meteorological Agency (JMA)[nb 5] names a tropical cyclone when it is estimated to have 10-minute sustained winds of at least 65 km/h (40 mph) anywhere in the basin. The Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) assigns names to tropical cyclones that move into or form as a tropical depression within the Philippine Area of Responsibility (PAR), defined as the area between 135°E and 115°E and between 5°N and 25°N, regardless of whether the JMA has already named the system. Tropical depressions monitored by the United States Joint Typhoon Warning Center (JTWC)[nb 6] are given a numerical designation with a "W" suffix, which means "west", a reference to the western Pacific region.[nb 3]
Seasonal forecasts
| TSR forecasts Date | Tropical storms | Total typhoons | Intense TCs | ACE | Ref. |
|---|---|---|---|---|---|
| Average (1991–2020) | 25.5 | 16.0 | 9.3 | 301 | [4] |
| May 11, 2026 | 27 | 18 | 11 | 410 | [4] |
| July 9, 2026 | 28 | 19 | 12 | 436 | [5] |
| August 10, 2026 | 28 | 20 | 13 | 500 | [6] |
| Other forecasts Date |
Forecast center |
Period | Systems | Ref. | |
| December 15, 2025 | PAGASA | January–March | 0–3 tropical cyclones | [7] | |
| December 15, 2025 | PAGASA | April–June | 2–5 tropical cyclones | [7] | |
| January 15, 2026 | NCHMF | February–July | 3-4 tropical cyclones | [8] | |
| January 15, 2026 | NCHMF | August–December | 9-10 tropical cyclones | [8] | |
| 2026 season | Forecast Center | Tropical cyclones | Tropical storms | Typhoons | Ref. |
| Actual activity: | JMA | 23 | 16 | 5 | |
| Actual activity: | JTWC | 15 | 13 | 6 | |
| Actual activity: | PAGASA | 13 | 10 | 4 | |
During the year, several national meteorological services and scientific agencies forecast how many tropical cyclones, tropical storms, and typhoons would form during the season and/or how many tropical cyclones would 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 (NCHMF) and Taiwan's Central Weather Administration (CWA).
The first outlook was released by PAGASA on December 15, 2025, in its monthly seasonal climate outlook, covering the first half of 2026. The agency forecast that zero to three tropical cyclones were expected to form or enter the PAR between January and March, while two to five were expected to form or enter the PAR between April and June.[7] PAGASA also mentioned that the short-lived and weak La Niña, which began during the fourth quarter of 2025, would persist for a month or two, with a neutral El Niño–Southern Oscillation (ENSO) transition between January and March.[7]
The year began with a weak La Niña cycle that developed in 2025.[9] According to the National Oceanic and Atmospheric Administration's (NOAA) forecast, the ENSO state was likely to return to neutral by mid-year and potentially transition to an El Niño phase during the second half of the year.
Seasonal summary
Systems
Tropical Storm Nokaen (Ada)
On January 13, the JTWC started monitoring a low-pressure area that developed 170 nautical miles (310 km) south of Palau, with satellite imagery indicating a disorganized low-level circulation center (LLCC).[10] The JMA later followed suit, identifying the same system as a tropical depression.[11] The following day, at 08:00 PHT (00:00 UTC), PAGASA also classified the system, assigning it the name Ada,[12] a replacement name for Agaton. Later that day, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) for Ada as it continued to intensify.[13] At 15:00 UTC, the JTWC upgraded the system to a tropical depression, designating it as 01W.[14] At 06:00 UTC on January 15, the JMA recognized 01W as a tropical storm and named it Nokaen.[15] Despite being in a favorable environment, Nokaen maintained its intensity while remaining stationary along the southern periphery of a subtropical high.[16] It then shifted northeastward slowly as it moved over marginal conditions.[17] On January 19, PAGASA noted that Nokaen weakened into a tropical depression;[18] the system further weakened into a remnant low on January 21[19] and dissipated on January 22.[citation needed]
Nokaen brought torrential rainfall to parts of the Philippines, triggering a landslide that resulted in two fatalities in Matnog, Sorsogon.[20] Another fatality was reported after a maritime incident in the Surigao area.[21] Several areas across Catanduanes, Albay, and Camarines Sur experienced flooding and landslides.[22] A total of 832,986 people were affected, while 60,384 were displaced across Calabarzon, the Bicol Region, Eastern Visayas, Negros Island, and Caraga. The city government of Maasin, Southern Leyte postponed the "Sakay-Sakay Festival" to January 25. Additionally, a barangay in Oras, Eastern Samar experienced a water crisis after flooding damaged the village's water system.[23]
Tropical Storm Penha (Basyang)
On February 2, the JTWC began tracking a low-pressure area that developed 128 nautical miles (237 km) east-northeast of Yap, with satellite imagery indicating a weak and broad low-level circulation center (LLCC).[24] The JMA followed suit the next day, identifying the system as a tropical depression.[25] On February 3, at 17:30 PHT (09:30 UTC), the system entered the PAR, with PAGASA assigning it the name Basyang;[26][27] the JTWC issued a TCFA for the system a few hours later as it showed signs of organization.[28] On February 4, at 03:00 UTC, the JTWC upgraded the system to a tropical depression, designating it as 02W.[29] Later that day, at 21:00 JST (12:00 UTC), the JMA upgraded 02W to a tropical storm and assigned the name Penha.[30] At 23:50 PHT (15:50 UTC), Penha made its first landfall over Bayabas, Surigao del Sur.[31] This was followed by additional landfalls in Jagna and Dauis in Bohol, Alcoy, Cebu, and Ayungon, Negros Oriental on February 6.[32] After making landfall, Penha weakened into a depression as it moved over cooler sea surface temperatures and encountered high wind shear.[33] The system was downgraded to a remnant low the following day and dissipated a few hours later.[34]
Penha produced heavy rainfall, flooding, and landslides across the Philippines, leaving 12 dead, 36 injured,[35] and around 28,000 people displaced. A landslide claimed four lives in Cagayan de Oro,[36] while five people died in Iligan.[37] Two people drowned in Surigao del Sur,[38] while another drowned in Carmen, Agusan del Norte.[39] A state of calamity was subsequently declared in Iligan and Surigao del Sur, where damages reached ₱1.48 billion (US$25.24 million). A total of 1,373 houses were damaged.[40][41]
Tropical Storm Nuri
On March 10, an area of low pressure formed 74 nautical miles (137 km) northeast of Yap, with the JTWC assessing a medium chance of tropical cyclone formation.[42] The JMA also began issuing advisories on the system later that day, classifying it as a tropical depression.[citation needed] Despite being in a marginally favorable environment, the JTWC later upgraded the disturbance's development potential from medium to high as it tracked northeastward.[43] On March 11, the JMA upgraded the system to a tropical storm and assigned it the name Nuri.[44] The JTWC followed suit at 03:00 UTC, designating the system as Tropical Depression 03W.[45] On March 12, Nuri weakened into a tropical depression and subsequently dissipated later that day, with both the JMA and JTWC issuing their final advisories on the system.[46]
Typhoon Sinlaku
On April 8, the Joint Typhoon Warning Center reported that an area of low pressure had formed 234 nautical miles (433 km) west-southwest of Chuuk, assessing a medium chance of development.[47] The Japan Meteorological Agency later followed suit, classifying the system as a tropical depression.[48] At 18:00 UTC on the same day, the JTWC issued a Tropical Cyclone Formation Alert, citing a high chance of formation as the low-level circulation center continued to wrap around the southern semicircle of the system.[49] Early the following day, the JTWC upgraded the system into a depression and designated it Tropical Depression 04W.[50] Later that day, the JMA upgraded 04W into a tropical storm, giving it the name Sinlaku as it moves westwards.[51] With low vertical windshear and high sea surface temperature, Sinlaku was upgraded to a severe tropical storm by the JMA at 12:00 UTC.[citation needed] On April 11, both the JMA and JTWC upgraded Sinlaku to a typhoon, with satellite imagery showing a rapidly consolidating storm and an expanding central dense overcast (CDO).[52][53] The storm would begin rapidly intensifying, and the JMA upgraded Sinlaku to a violent typhoon the following day.[54] By 18:00 UTC the same day, the JTWC upgraded Sinlaku's 1-minute sustained wind speeds to 160 knots (295 km/h) and lowered its pressure to 890 mb (26.28 inHg).[55] By April 14, Sinlaku weakened to a Category 4-equivalent typhoon due to a long-lasting eyewall replacement cycle, losing super typhoon status.[citation needed] Later that day, the still very powerful typhoon made landfall on the northern side of Tinian, with Saipan being located within the now much larger new eye.[citation needed] By the next day, Sinlaku had completed its eyewall replacement cycle, having weakened to a Category 3-equivalent typhoon as it began to turn towards the north.[citation needed] Sinlaku further downgraded into a tropical storm on April 19 before it underwent extratropical transition on the following day, prompting the JTWC to issue its final warning at 21:00 UTC.[56]
Sinlaku left one person dead and another missing in Micronesia.[57] In the Northern Mariana Islands, six people went missing after a cargo vessel overturned.[58]
Tropical Storm Hagupit (Caloy)
On May 4, JTWC marked an area of low-pressure 67 nautical miles (124 km) west-northwest of Chuuk, with a low chance of formation.[59] The following day, JTWC issued a TCFA as the obscured low-level circulation center (LLCC) with deep convection building over the center and increasing formative banding.[60] Later that day, at 21:00 UTC, the JTWC designated the system Tropical Depression 05W.[61] The JTWC further upgraded the system to a tropical storm at 00:00 the following day. At 06:00 UTC, JMA followed suit and assigned the name Hagupit, as the storm passes through environmental conditions marginally favorable for development.[62] At 18:00 UTC, a multispectral satellite imagery (MSI) shows that the storm shows good cloud characteristics of anticyclonic outflow, while a microwave imagery shows active, convective cloud clusters.[63]
On May 9, Hagupit entered the PAR at 18:00 PHT (10:00 UTC), and was assigned the name Caloy.[64] At 03:00 UTC on May 10, Hagupit weakened into a tropical depression as it moves north-northwest over unfavorable conditions.[65] The JTWC issued its final advisory on May 11 as Hagupit further weakened into a remnant low.[66] JMA continued to track Hagupit as a depression before it was downgraded into a low-pressure area on May 15. The remnants of Hagupit tried to redevelop, with the JTWC analyzing the remnants as a separate entity, however they failed to redevelop and later dissipated.[citation needed]
Severe Tropical Storm Jangmi (Domeng)
On May 25, the JTWC began monitoring a disturbance east-southeast of Yap, noting favorable conditions for tropical cyclogenesis.[67] Development chances were raised to medium on May 26,[68] and the Japan Meteorological Agency (JMA) classified it as a tropical depression later that day.[69] The JTWC subsequently issued a TCFA.[70] On May 27, the JMA upgraded the system to Tropical Storm Jangmi,[71] while the JTWC designated it as 06W.[72] After entering the PAR on May 29, PAGASA assigned the name Domeng.[73] Jangmi intensified into a Category 1-equivalent typhoon on May 30 by the JTWC,[74] with the JMA upgrading it to a severe tropical storm.[75] It weakened to a tropical storm on June 1 due to a deteriorating structure and dry air intrusion.[76] Jangmi made landfall in Wakayama Prefecture on June 3[77] before becoming extratropical later that day.[78]
According to the National Disaster Risk Reduction and Management Council (NDRRMC), 85,295 people were displaced in the Bangsamoro Autonomous Region of Muslim Mindanao (BARMM), where infrastructure damage reached ₱3.4 million (US$55,055.42).[79] In Japan, a total of 23 injuries were reported, including 17 in Okinawa and two in Kagoshima Prefecture; 48 houses were also partially damaged in Kagoshima.[80] Flooding occurred in Saiwai-ku, Kawasaki and Ōta, Tokyo, while part of National Route 371 collapsed. Water outages affected 1,800 households in Ōme, Tokyo, and fallen branches disrupted the Hachiko Line between Haijima and Komagawa.[81]
Tropical Depression Ester
On June 3, the JMA began issuing advisories on a tropical depression in the South China Sea.[82] The JTWC also started tracking the system the following day, as it became more broad and well-defined whilst drifting northeastwards towards Taiwan.[citation needed] The depression entered the PAR at 05:00 PHT on June 5 (21:00 UTC on June 4), and PAGASA assigned it the name Ester.[83] That same day, the JTWC analyzed the system as a subtropical depression.[citation needed] On the evening of June 5, the depression's structure was significantly disrupted as it made landfall in Taiwan, due to the island's extremely rugged terrain.[citation needed] This land interaction had caused the broadening of the weak low-level circulation as it began to race towards the northeast.[84] Nonetheless, on June 7, the JTWC upgraded the system to a subtropical storm as it raced just offshore Japan's southern coastline.[85]
Typhoon Mekkhala (Francisco)
On June 15, the JTWC began monitoring a disorganized low-pressure area 940 nautical miles (1,740 km) east-southeast of Guam in a marginal environment for tropical cyclogenesis.[86] On June 18, the JTWC issued a TCFA,[87] while the JMA classified the system as a tropical depression.[88] Later that day, the JTWC designated it as Tropical Depression 07W.[89] On June 19, the JMA upgraded the system to Tropical Storm Mekkhala, with a persistent CDO partially obscuring its LLCC.[90][91] Mekkhala entered the PAR on June 20 and was named Francisco by PAGASA.[92] It strengthened into a severe tropical storm before becoming a Category 1-equivalent typhoon on June 21.[93][94] The storm intensified into a Category 2-equivalent typhoon, with PAGASA also upgrading it to typhoon status.[95][96] On June 22, Mekkhala strengthened into a Category 3-equivalent typhoon before peaking as a Category 4-equivalent typhoon, while PAGASA classified it as a super typhoon.[97][98][99] The storm weakened on June 23 as it encountered cooler waters and 20 to 25 knots (37 to 46 km/h; 23 to 29 mph) north-northeasterly wind shear.[100][101] By June 25, Mekkhala had weakened to a tropical storm, with the JMA downgrading it to a severe tropical storm as it exited the PAR.[102][103][104] Storm warnings were issued for Okinawa as the system approached the islands.[105] Mekkhala later scraped the coast of Japan before becoming extratropical on June 27, prompting the JTWC to discontinue advisories.[citation needed]
Two people died in Taiwan, one in Kaohsiung and another in Hsinchu County. One other person in Hsinchu County went missing.[106] In Japan, the storm produced heavy rainfall which overflowed a reservoir in Hiroshima Prefecture and impacted several residences. Two people were killed and another was injured due to a paddling incident related to the storm in Ehime Prefecture while a landslide caused another death in Yamaguchi Prefecture.[107] Four other injuries occurred across Japan.[106]
Tropical Storm Higos (Gardo)
On June 21, the JTWC marked a poorly organized but consolidating low-pressure area that formed 441 nm (817 km) east of Guam. Although expecting a slow development, the disturbance was located in a favorable environment for tropical cyclogenesis.[108] On the following day, the JMA started issuing advisories on the system, recognizing it as a tropical depression.[109] At 11:00 UTC, JTWC issued a TCFA warning, citing a consolidating LLCC with a persistently building deep convection around the center.[110] JTWC later designated the disturbance as 08W at 15:00 UTC.[111] At 00:00 UTC of June 23, 08W was upgraded into a tropical storm, receiving the name Higos by the JMA.[112] On June 23, Higos weakened back to a tropical depression with winds of 35 mph and a central pressure of 1003 hPa (mbar).[citation needed] However, Higos regained tropical storm status at 21:00 UTC of June 24.[citation needed] At 15:00 PHT (07:00 UTC) of the following day, Higos entered the PAR, assigning the domestic name Gardo by PAGASA, with the system moving towards the north when it entered.[104][113][114] The system then exited the PAR at 09:30 PHT (01:30 UTC).[115][116] Then, Higos made a big turn towards the north and then to the northeast. On June 27 at 5:25 AM JST (19:25 UTC on June 26), Higos made landfall on the Izu Peninsula as it raced towards the northeast, subsequently making landfall on the Boso Peninsula an hour later.[citation needed] Later that evening, Higos completed its extratropical transition, and shortly after, it was absorbed into another extratropical cyclone system to the north.[citation needed]
Typhoon Bavi (Inday)
On June 25, the JTWC began monitoring a low-pressure area 901 nm (1,669 km) east-southeast of Kwajalein, noting favorable conditions for tropical cyclogenesis.[117] On June 30, the agency issued a Tropical Cyclone Formation Alert (TCFA).[118] Early on July 1, the JTWC classified it as Tropical Depression 09W.[119] The JMA upgraded it to Tropical Storm Bavi on July 2.[120] Bavi then underwent rapid intensification, strengthening from 70 kn (80 mph; 130 km/h) to 125 kn (145 mph; 230 km/h) in 18 hours, becoming a Category 4-equivalent typhoon with a well-defined eye.[121][122] On July 4, the JTWC upgraded Bavi to a super typhoon, while the JMA classified it as a violent typhoon.[123] After briefly weakening due to an eyewall replacement cycle, Bavi regained Category 5-equivalent intensity before making landfall on Rota on July 6 as one of the island's strongest typhoons.[124][125] On July 7, PAGASA assigned the local name Inday while the storm remained outside the PAR.[126][127] Bavi turned northwest on July 9 and weakened due to another eyewall replacement cycle.[128] It reintensified on July 11 before making landfall in Zhejiang at 23:20 CST (15:20 UTC) on July 12 with 125 km/h (77 mph) sustained winds.[129][130][131][132]
Bavi triggered heavy rains and landslides that killed 23 people and left 18 others missing across the Philippines.[133]
Severe Tropical Storm Maysak (Henry)
On June 29, an area of convection had developed 591 nm (1,095 km) of Manila, with satellite imagery indicating an elongated LLCC with disorganized convection throughout the northern periphery.[134] At 02:00 UTC of July 1 (18:00 UTC of June 30), PAGASA upgraded the disturbance into a tropical depression, assigning the local name Henry. Meanwhile, at 21:00 UTC, JTWC upgraded its chances to high, prompting to issue a TCFA warning as Henry moved through favorable conditions.[135] On July 1, Henry was designated as 10W by the JTWC as the agency followed suit.[136] As Henry tracked northwards, JMA upgraded it into a tropical storm at 18:00 UTC of the following day, which gained the name Maysak.[137] On July 3 at 10:20 UTC, Maysak made its first landfall near Lingshui, Hainan Province.[138] As Maysak moved through the Gulf of Tonkin, JMA upgraded it into a severe tropical storm[139] before the system made its second and final landfall in Móng Cái, Quảng Ninh province on July 4 at 12:30 UTC.[140] Maysak later moved inland, causing the JMA to downgrade it to a tropical depression.[141]
In Vietnam, strong winds from Maysak uprooted trees and ripped metal roofs off buildings in Móng Cái. Up to 13 in (33 cm) of rainfall was recorded in Fushun on July 4, flooding streets and forcing 3,600 people to evacuate. In Guangxi, China, severe flooding and strong winds killed two people in Nanning,[142] submerged cars and trapped people in Fangchenggang and uprooted trees in Dongxing.[143]
Tropical Storm Haishen (Josie)
On July 7, the JTWC began tracking a disturbance situated over the Marshall Islands.[citation needed] Over the next several days, the disturbance drifted towards the southeast before heading northeastward. On July 12, the disturbance became better organized, prompting the JMA to classify the system as a tropical depression.[citation needed] The following day, it further intensified into a tropical storm, giving it name Haishen by the JMA at 00:00 UTC,[144] with the JTWC issuing a Tropical Cyclone Formation Alert for the system at 03:00 UTC.[145] PAGASA also issued a tropical cyclone advisory the same day at 11:00 PHT (03:00 UTC).[146] At 00:30 PHT (16:30 UTC), Haishen entered the PAR, subsequently assigning the local name Josie by PAGASA.[147] However, the following day, at 03:30 UTC, the JTWC cancelled its TCFA as Haishen dissipated due to moderate to strong easterly wind shear, without giving the system a formal designation.[148] Meanwhile, the JMA continued monitoring Haishen, downgrading into a tropical depression at 00:00 UTC until further downgrading into a low-pressure area at 12:00 UTC.[149]
Haishen is the first tropical storm to be recognized by the Japan Meteorological Agency, but not by the Joint Typhoon Warning Center since Mulan in 2022.[citation needed]
Typhoon Noul (Kiyapo)
On July 21, the JTWC marked an area of low-pressure that formed 253 nm (469 km) north-northwest of Yap, with satellite imagery indicated a broad area of cyclonic low-level rotation associated with weak flaring convection.[150] On July 22, at 20:00 PHT (12:00 UTC), PAGASA upgraded the system into a tropical depression, assigning the domestic name Kiyapo.[151] At 20:30 UTC, the JTWC issued a TCFA, citing a high chance of formation.[152] At 09:00 UTC of the following day, JTWC followed suit, designating Kiyapo as 11W, citing a consolidating and partially exposed LLCC.[153] Later that day, JMA and JTWC upgraded 11W into a tropical storm, [154] with the former agency assigning the name Noul.[citation needed] As it continues to steadily intensify, Noul made landfall over Camiguin Island in Calayan, Cagayan on the following day at 14:10 PHT (06:10 UTC).[155][156] Afterwards, JMA and PAGASA upgraded Noul into a severe tropical storm.[157][158] The storm continued to strengthen while moving west-northwestward as all three agencies[citation needed] upgraded it into a typhoon.[159] Early on July 26 at 03:50 CST (19:50 UTC), Noul made its second and final landfall along the coast of Huidong County, Guangdong as a Category 2-equivalent typhoon on the Saffir–Simpson scale as its intensity peaked at 100 mph (155 km/h) with a minimum pressure of 967 mbar (hPa).[160] After making landfall, Noul started rapidly weakening, going from a strong typhoon to a severe tropical storm in two hours as it moved further inland. Noul was last noted on July 27 as it dissipated.[citation needed]
Typhoon Dolphin
On July 19, the Central Pacific Hurricane Center (CPHC) began monitoring a disturbance south of the Hawaiian Islands. When the disturbance had a high 90% chance of development in the next two days, it was designated Invest 92C.[161] Later on July 26, the disturbance crossed into the Western Pacific, and the JMA classified the system as a tropical depression upon crossover.[citation needed] The following day at midnight, The JTWC upgraded the disturbance to a tropical depression, designating it as 12W.[162] Shortly thereafter, the Japan Meteorological Agency upgraded the system to a tropical storm, naming it Dolphin.[163] Almost immediately after its nomenclature, Dolphin began a period of rapid intensification, the fastest since Typhoon Noru in 2022,[164] quickly becoming a typhoon and reaching a Category 4-equivalent initial peak intensity on the Saffir–Simpson scale on July 28, before its intensification was stunted by an eyewall replacement cycle.[citation needed] After finishing, Dolphin resumed intensifying once again, reaching super typhoon status the following day.[citation needed] Soon after reaching Category 5 strength on the Saffir–Simpson scale, Dolphin started undergoing a second eyewall replacement cycle, temporarily halting further development of the storm.[165] After completing its eyewall replacement cycle, it strengthened back to Category 5-equivalent strength but later started weakening again after started a third eyewall replacement cycle.[166] On August 4, after it completed a fourth eyewall replacement cycle, Dolphin rapidly intensified back into a Category 4-equivalent typhoon,[167] but a few hours later, it once again entered unfavourable conditions and weakened back into a category 2 typhoon.[citation needed] On August 9, Dolphin made landfall over Yuhuan in China's Zhejiang province at 17:30 CST on August 9, followed by a second landfall over Wenzhou an hour later, in almost the exact same spot Bavi made landfall nearly a month prior.[168]
Despite the system remaining outside the PAR, significant rainfall was reported in Metro Manila and 23 provinces as Dolphin enhanced the southwest monsoon.[169]
Tropical Storm Kujira (Luis–Maymay)
On July 29, the JTWC and PAGASA began monitoring a low pressure area outside the PAR, citing an unlikely chance of development.[170] On July 30, the JMA upgraded the disturbance to a tropical depression,[citation needed] and PAGASA followed suit on two days later on August 1, assigning it the name Luis.[171][172] Later that day, at 18:00 UTC, as Luis was situated east-northeast of Legazpi, Albay, the JTWC raised the system's chances of becoming a tropical cyclone to medium, citing a slowly consolidating low-level circulation center (LLCC).[173] At 19:30 UTC, the JTWC raised its chances to high and issued a TCFA for the system but canceled and downgraded the chance of formation to low after 12 hours.[110] At 17:30 PHT (09:30 UTC), Luis made its first landfall over Maconacon, Isabela.[174] PAGASA stated it degenerated into a low pressure area later that day,[175] a part of it split into a second low pressure area in the South China Sea, meanwhile the original system became a remnant low and merged with the second system a few hours later.[176] The JMA also started issuing warnings once again at the same time. The JTWC also upgraded its chances to high and issued a TCFA again after passed over Luzon Island and moved into more favorable conditions.[110] At 20:00 PHT (12:00 UTC), the disturbance redeveloped into a tropical depression and was retrospectively renamed Maymay by PAGASA.[177] At 18:00 UTC, both the JMA and PAGASA upgraded it to a tropical storm and the JTWC upgraded it to a tropical depression, therefore being assigned the name Kujira by the JMA[178] and the designation 13W from the JTWC, respectively.[citation needed] Early on August 6, at 02:00 PHT (18:00 UTC of the previous day), Kujira made its second landfall over Magsingal, Ilocos Sur.[179] Later, the JMA, JTWC and PAGASA all downgraded the system to a tropical depression[180] and JMA later stated it dissipated. The following day, the system weakened into an remnant low over the Philippine sea[181][182] and later it dissipated according to PAGASA.[183] Kujira was later absorbed into Typhoon Dolphin and became a trough.[citation needed]
In the Philippines, flooding was reported in seven areas of Bangsamoro and Zamboanga Peninsula. Several landslides occurred in Dipaculao, Aurora and a downed utility pole blocked a road in the same municipality.[184] A total of 80,633 people were affected by the storm.[185] Upon Kujira's second landfall in the Philippines, torrential rains fell across Luzon. Several roads were closed due to the effect of landslides and flooding. A wooden bridge was also destroyed by floods in Quirino. More than 4,700 households were affected by flooding in Buluan after a river overflowed. At least 13 people died from the effects of the storm, with 9 missing.[186] Agricultural and infrastructural damage in Pangasinan reached ₱105.7 million (US$1.73 million).[187] The Department of Agriculture reported a total of ₱135.3 million worth of agricultural damage from the storm along with the effects of the southwest monsoon.[188]
Severe Tropical Storm Chan-hom
On August 4, the JTWC marked an area of low-pressure that formed 116 nm (215 km) south-southeast of Wake Island, classifying it as a monsoon depression later that evening.[citation needed] The following day, the JMA upgraded the low pressure to a tropical depression.[citation needed] A few hours later, the JMA further upgraded the tropical depression to a tropical storm, assigning it the name Chan-hom.[189] Due to its nature as a monsoon depression, the storm was quite disorganized, consisting of a broad and partially exposed low-level circulation with multiple mesovortices embedded within it.[190] At 19:30 UTC on August 6, the JTWC issued a TCFA for the system, with it expected to consolidate and transition into a warm-core system.[191] Later at midnight, the JTWC upgraded it to a tropical storm, designating it as 14W.[citation needed] Later that day, JTWC downgraded it to a tropical depression.[192] The following day, JTWC once again upgraded it to a tropical storm.[citation needed] The system made landfall as a severe topical storm with winds of 95 km/h (50 mph) in Ibaraki Prefecture in Japan[193] on a rare east-to-west trajectory, making it the first storm to make landfall on the island of Honshu on this trajectory since Typhoon Jongdari in 2018.[citation needed]
Tropical Storm Peilou
On August 8, a trough related to the remnants of Tropical Storm Kujira split from Typhoon Dolphin and the JMA upgraded it to a tropical depression.[194] Later that day, the JTWC followed suit, but its designation was kept the same as that of Kujira, stating that it is a redevelopment of Kujira.[citation needed] PAGASA later followed suit, classifying it as a depression as well.[195] On August 9, both the JMA[citation needed] and PAGASA upgraded the system into a tropical storm, with the system being assigned the name Peilou.[196] The JTWC later followed suit and continued the sequence of bulletins and track forecasts previously issued for Kujira.[197]
Tropical Depression 15W
On August 8, PAGASA reported that a low pressure area outside of the PAR had formed 2,600 kilometers east of northern Luzon. Later that day, the agency stated the low had developed into a tropical depression, while the JMA had only recognized it as a low pressure area.[198][199] Later that day, the JTWC cited that the system had a medium chance of becoming a tropical cyclone within 24 hours.[200] The next day, the JMA upgraded the system to a tropical depression.[201]. At 06:00 UTC, the JTWC issued a TCFA for the system, changing the risk to high.[202] The following day on August 10, the JTWC followed suit, classifying the system as Tropical Depression 15W, with warnings being issued around the same time.[203][204]
Tropical Depression
Other systems
- On March 10, the JMA identified a tropical depression located over 1,300 km (810 mi) east-northeast of Tropical Storm Nuri.[205] The following day, a developing frontal system absorbed the depression.[206]
- On May 8, the JMA noted that a tropical depression formed around 1,900 km (1,200 mi) to the east of Tropical Storm Hagupit.[207] The next day, the depression degenerated into a remnant low-pressure system.[208]
- On June 9, the JMA noted that a tropical depression had formed near the Pearl River Delta.[209] The system was absorbed into a frontal boundary the following day.[210]
- On July 14, PAGASA reported that a tropical depression formed outside the Philippine Area of Responsibility near the Pearl River Delta.[211] The system was downgraded to a remnant low-pressure area six hours later and dissipated completely over land the next day.[citation needed]
- On July 15, the JTWC began tracking a disturbance east-southeast of Micronesia.[citation needed] The following day, the JMA designated it as a tropical depression. However, due to its poorly organized cyclonic circulation, it was downgraded into a remnant low on July 17 despite being in a favorable environment.[212]
- On July 16, the JTWC marked a subtropical depression east of Japan and designated it Invest 91W.[213] However, the JMA only classified the system as a low-pressure area,[citation needed] and it dissipated after two days.
- On August 7, the Vietnamese National Center for Hydro-Meteorological Forecasting reported that a low-pressure area over the Gulf of Tonkin has strengthened into a tropical depression.[214] The Hong Kong Observatory also followed suit the following day. Meanwhile, the JTWC assessed the likelihood of tropical cyclone formation to medium, but downgraded it to low on August 8, while HKO and NCHMF both reported the system was degenerated into a low pressure area in the same day.
Storm names
Within the northwest Pacific Ocean, both the JMA and PAGASA assign names to tropical cyclones that develop in the region, which can result in a tropical cyclone having two names.[215] The JMA's RSMC Tokyo–Typhoon Center assigns international names to tropical cyclones on behalf of the World Meteorological Organization's Typhoon Committee should they be judged to have 10-minute sustained wind speeds of 65 km/h (40 mph).[216] PAGASA names tropical cyclones which move into or form as a tropical depression in their PAR, located between 135°E and 115°E and between 5°N and 25°N, even if the cyclone has had an international name assigned to it.[215] Should the list of names for the region be exhausted, then names will be taken from an auxiliary list, the first ten of which 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 2027.[216]
International names
A tropical cyclone is assigned a name once it reaches 10-minute sustained wind speeds of 65 km/h (40 mph). The JMA selects the names from a list of 140 contributed by the 14 members nations and territories of the ESCAP/WMO Typhoon Committee.[217] Retired names, if any, will be announced by the WMO in 2027, with replacement names to be announced in 2028. The next 28 names on the naming list are shown below, along with their international numeric designations if they are used. All the names in the list are the same, except for Nokaen, Penha, Peilou, Narra, Gaenari, and Bang-Lang, which replaced Phanfone, Vongfong, Linfa, Molave, Goni, and Vamco after the 2019 and 2020 seasons. The names Nokaen, Penha and Peilou were used for the first time this season.
|
|
Philippines
PAGASA uses its own naming scheme for tropical cyclones that develop within or enter their self-defined area of responsibility.[218] During this season, PAGASA uses the following list of names, which was last used during 2022 and is scheduled to be used again in 2030, with replacements for any retired names.[218] All of the names are the same except Ada, Francisco, Kiyapo, and Pilandok, which replaced the names Agaton, Florita, Karding, and Paeng after they were retired.[218] The names Ada, Francisco, and Kiyapo were used for the first time this season.
|
|
|
|
|
|
|
|
Season effects
This table summarizes all official tropical systems that developed within or moved into the Western Pacific basin during 2026, defined as the region west of the 180th meridian. It also provides an overview of each system's intensity, duration, affected land areas, and any associated deaths or damage.
| Name | Dates | Peak intensity | Areas affected | Damage (USD) |
Deaths | Ref(s). | ||
|---|---|---|---|---|---|---|---|---|
| Category | Wind speed | Pressure | ||||||
| Nokaen (Ada) | January 13–22 | Tropical storm | 75 km/h (45 mph) | 996 hPa (29.41 inHg) | Palau, Caroline Islands, Philippines | $24,000 | 2 | [219][220] |
| Penha (Basyang) | February 3–7 | Tropical storm | 65 km/h (40 mph) | 1002 hPa (29.59 inHg) | Caroline Islands, Philippines | $25.5 million | 12 | [221] |
| Nuri | March 9–12 | Tropical storm | 65 km/h (40 mph) | 998 hPa (29.47 inHg) | Mariana Islands, Caroline Islands | None | None | |
| TD | March 10–11 | Tropical depression | Not specified | 1004 hPa (29.65 inHg) | Mariana Islands | None | None | |
| Sinlaku | April 7–19 | Violent typhoon | 215 km/h (130 mph) | 905 hPa (26.72 inHg) | Micronesia, Mariana Islands, Bonin Islands | >$1.55 billion | 17 | [222] |
| Hagupit (Caloy) | May 5–15 | Tropical storm | 75 km/h (45 mph) | 998 hPa (29.47 inHg) | Caroline Islands | Minimal | None | |
| TD | May 8–9 | Tropical depression | Not specified | 1006 hPa (29.71 inHg) | Micronesia | None | None | |
| Jangmi (Domeng) | May 26–June 3 | Severe tropical storm | 110 km/h (70 mph) | 975 hPa (28.79 inHg) | Caroline Islands, Philippines, Japan | >$3.1 million | None | [223] |
| Ester | June 3–6 | Tropical depression | 55 km/h (35 mph) | 1002 hPa (29.59 inHg) | Vietnam, Philippines, Taiwan, Japan | Minimal | None | |
| TD | June 9–10 | Tropical depression | Not specified | 1002 hPa (29.59 inHg) | South China, Taiwan, Japan (particularly Ryukyu Islands) | Minimal | None | |
| Mekkhala (Francisco) | June 18–27 | Very strong typhoon | 185 km/h (115 mph) | 925 hPa (27.32 inHg) | Marshall Islands, Caroline Islands, Mariana Islands, Philippines, Taiwan, Japan, Kuril Islands | >$20.2 million | 10 | [224] |
| Higos (Gardo) | June 22–27 | Tropical storm | 85 km/h (50 mph) | 998 hPa (29.47 inHg) | Mariana Islands, Japan, Kuril Islands | Unknown | None | |
| Bavi (Inday) | June 30–July 15 | Violent typhoon | 205 km/h (125 mph) | 910 hPa (26.87 inHg) | Marshall Islands, Caroline Islands, Mariana Islands, Philippines, Japan (particularly Ryukyu Islands, Hokkaido), Taiwan, Eastern China, Northern China, Korea, Russian Far East | >$141 million | 23 | [225] |
| Maysak (Henry) | July 1–7 | Severe tropical storm | 95 km/h (60 mph) | 990 hPa (29.23 inHg) | Philippines, Vietnam, Laos, Cambodia, Thailand, Southern China, Central China | >$3.35 billion | 50 | [226][227] [228][229] |
| Haishen (Josie) | July 12–14 | Tropical storm | 65 km/h (40 mph) | 1002 hPa (29.59 inHg) | Marshall Islands, Caroline Islands | Minimal | None | |
| TD | July 16–17 | Tropical depression | 55 km/h (35 mph) | 1006 hPa (29.71 inHg) | Micronesia | None | None | |
| Noul (Kiyapo) | July 22–27 | Typhoon | 140 km/h (85 mph) | 960 hPa (28.35 inHg) | Micronesia, Philippines, Taiwan, Southern China | >$639 million | 14+ | |
| Dolphin | July 26–present | Violent typhoon | 205 km/h (125 mph) | 910 hPa (26.87 inHg) | Marshall Islands, Japan (particularly Minamitorishima, Bonin Islands, Daitō Islands, Ryukyu Islands), Taiwan, East China, Central China | Unknown | 6+ | |
| Kujira (Luis–Maymay) | July 31–August 6 | Tropical storm | 75 km/h (45 mph) | 994 hPa (29.35 inHg) | Micronesia, Philippines | >$26.1 million | 7+ | [230][231][232] |
| Chan-hom | August 5–present | Severe tropical storm | 95 km/h (60 mph) | 980 hPa (28.94 inHg) | Wake Island, Japan (particularly Kantō region, Tōhoku region) | Unknown | None | |
| Peilou | August 8–present | Tropical storm | 85 km/h (50 mph) | 992 hPa (29.29 inHg) | Mariana Islands, Japan (particularly Minamitorishima) | Minimal | None | [nb 7] |
| 15W | August 9–11 | Tropical depression | 55 km/h (35 mph) | 996 hPa (29.41 inHg) | None | None | None | |
| TD | August 11–present | Tropical depression | 55 km/h (35 mph) | 998 hPa (29.47 inHg) | Japan (particularly Minamitorishima) | None | None | |
| Season aggregates | ||||||||
| 23 systems | January 13 – Season ongoing | 215 km/h (130 mph) | 905 hPa (26.72 inHg) | >$5.76 billion | 141 | |||
See also
- Weather of 2026
- Tropical cyclones in 2026
- Pacific typhoon season
- 2026 Atlantic hurricane season
- 2026 Pacific hurricane season
- 2026 North Indian Ocean cyclone season
- South-West Indian Ocean cyclone seasons: 2025–26, 2026–27
- Australian region cyclone seasons: 2025–26, 2026–27
- South Pacific cyclone seasons: 2025–26, 2026–27
Notes
Meaning
Information
- On July 14, a tropical depression was designated by PAGASA outside their area of responsibility without being given a name, and was not monitored by the JMA or JTWC as a formal system. Therefore, it is marked as unofficial.
- On August 7, NCMWF spotted a tropical depression in the Gulf of Tonkin, it was also recognised by HKO the following day, and was not monitored by the JMA or JTWC as a formal system. Therefore, it is marked as unofficial.
- The Philippine Atmospheric, Geophysical and Astronomical Services Administration classifies Mekkhala as a super typhoon; however, this statistic follows the super typhoon definition used by the Joint Typhoon Warning Center.
- The Japan Meteorological Agency is the official Regional Specialized Meteorological Centre for the western Pacific Ocean.
- 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.[2]
- The JTWC recognises this system to have regenerated into Peilou as one continuous system, therefore it also has the same designation as Peilou.
- The JTWC recognises this system as a regeneration of Kujira, therefore it also has the same designation as Kujira.
