Loading AI tools
From Wikipedia, the free encyclopedia
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.[1] 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.
| 2022 Pacific typhoon season | |
|---|---|
Season summary map | |
| Seasonal boundaries | |
| First system formed | January 27, 2022 |
| Last system dissipated | December 12, 2022 |
| Strongest storm | |
| Name | Nanmadol |
| • Maximum winds | 195 km/h (120 mph) (10-minute sustained) |
| • Lowest pressure | 910 hPa (mbar) |
| Seasonal statistics | |
| Total depressions | 37 |
| Total storms | 25 |
| Typhoons | 10 |
| Super typhoons | 3 (unofficial)[nb 1] |
| Total fatalities | 498 total |
| Total damage | $5.07 billion (2022 USD) |
| Related articles | |
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] named tropical cyclones that were judged to have 10-minute sustained wind speeds of at least 65 km/h (40 mph) anywhere in the basin, whilst the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) assigned names to tropical cyclones which moved into or formed as a tropical depression in the Philippine Area of Responsibility (PAR) located between 135°E and 115°E and between 5°N and 25°N regardless of whether or not a tropical cyclone has already been given a name by the JMA. Tropical depressions that were monitored by the United States' Joint Typhoon Warning Center (JTWC)[nb 3][nb 1] were given a number with a "W" suffix.
| TSR forecasts Date | Tropical storms | Total Typhoons | Intense TCs | ACE | Ref. |
|---|---|---|---|---|---|
| Average (1965–2021) | 25.9 | 16.2 | 8.8 | 293 | [4] |
| May 5, 2022 | 23 | 13 | 7 | 293 | [4] |
| July 6, 2022 | 23 | 13 | 7 | 217 | [5] |
| August 9, 2022 | 23 | 14 | 6 | 166 | [6] |
| Other forecasts Date | Forecast Center | Period | Systems | Ref. | |
| December 22, 2021 | PAGASA | January–March | 0–3 tropical cyclones | [7] | |
| December 22, 2021 | PAGASA | April–June | 1–4 tropical cyclones | [7] | |
| June 29, 2022 | PAGASA | July–September | 3–6 tropical cyclones | [8] | |
| June 29, 2022 | PAGASA | October–December | 5–9 tropical cyclones | [8] | |
| 2022 season | Forecast Center | Tropical cyclones | Tropical storms | Typhoons | Ref. |
| Actual activity: | JMA | 37 | 25 | 10 | |
| Actual activity: | JTWC | 29 | 25 | 13 | |
| Actual activity: | PAGASA | 18 | 14 | 6 | |
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 and Taiwan's Central Weather Bureau. The first forecast was released by PAGASA on December 22, 2021, in their monthly seasonal climate outlook predicting the first half of 2022.[7] They predicted that only 0–3 tropical cyclones were expected to form or enter the Philippine Area of Responsibility between January and March, while 1–4 tropical cyclones are expected to form between April and June. PAGASA also stated that ongoing La Niña conditions could last until it transitions back into ENSO-neutral conditions by the second quarter of 2022.[7]
On May 5, Tropical Storm Risk (TSR) issued its first forecast for the 2022 season with ongoing La Niña still anticipated until roughly the third quarter of the year, TSR predicted that tropical activity for 2022 will be slightly below average predicting 23 named storms, 13 typhoons and 7 intense typhoons.[4] TSR remained constant with their prediction in their second forecast in July.[5] On August 9, TSR released their third and final forecast for the season, with the only changes is increasing their typhoon numbers by 14, and decreasing the intense typhoon numbers down to 6. The ACE Index forecast was significantly lowered to 166, and was based on the then-current index as of early August and the reduction of cyclonic activity in the month of June.[6]
The first system, a minor tropical depression, formed in the South China Sea on January 27 and dissipated shortly after. In the final week of March, a tropical depression formed west of Palawan and headed for Vietnam, and received the designation of 01W from the Joint Typhoon Warning Center, but the system did not last long and dissipated the next day. In early April, the systems designated as 02W and 03W formed. 02W went on to become Tropical Storm Malakas, which later intensified into the first tropical storm, and later the first typhoon of the season. It also received the name Basyang from PAGASA, but only lasted 5 hours inside the Philippine Area of Responsibility.
03W received the name Agaton from PAGASA and first struck Guiuan in Eastern Visayas before eventually moving westward, and later intensifying into Tropical Storm Megi. Megi stalled through the Leyte Gulf before it made its second landfall over Basey, Samar. Throughout its track, Megi brought catastrophic flooding and landslides to the country as it remained almost stationary in Leyte Gulf before making landfall, which effectively made it the deadliest tropical cyclone ever recorded in the month of April in the Philippines. Megi later dissipated on April 13, as Malakas developed into a Category 4-equivalent typhoon. Malakas then began to rapidly weaken as it headed northeast and became extratropical, and the basin quieted down for the rest of April. No named storms formed during the entirety of May, with a minor tropical depression forming east of Mindanao on May 30, and later dissipated on that day.
Nearing the end of June, a tropical depression formed west of Luzon where it received the name Caloy by the PAGASA. Caloy then intensified into a tropical storm a day later, gaining the international name Chaba. Around the same time, a new Low Pressure Area (LPA) east of Northern Luzon was given a Tropical Cyclone Formation Alert by JTWC, and was named by PAGASA as Domeng. The system eventually strengthened into a tropical storm where the JMA named the system Aere.
Chaba continued to intensify until it reached Severe Tropical Storm status as Aere moved poleward and threatened the Japanese Ryukyu Islands. Chaba became a Category 1 typhoon and struck Maoming, China, and also sunk a crane ship passing nearby Hong Kong. Aere passed through Naha, Japan and weakened into a tropical depression. After crossing Japan, Aere (Domeng) was reupgraded by the Joint Typhoon Warning Center into a subtropical storm.
During the last week of July, Songda formed west of the Mariana Islands, which was joined by Trases (Ester) in the Philippine Sea three days later. Songda traveled northwestwards, passing over the waters of Kagoshima Prefecture on July 30. Songda dissipated on August 1 as its remnants made landfall over North Korea. Songda additionally brought heavy rainfall over Kyushu and Shikoku regions of Japan as well as Jeju Island in South Korea. Trases on the other hand passed over Okinawa, Trases made landfall on Jeju Island before weakening into a tropical depression until it dissipated on August 1.
In early August, a low pressure area formed southwest of Taiwan on August 1. Two days later, the disturbance strengthened into a tropical depression according to the JMA, and the JTWC designated the depression as Tropical Depression 08W. 08W dissipated on August 4, as it made landfall on Huidong County in Guangdong. On August 8, a tropical depression formed east of Vietnam. The JMA classified the system as a tropical storm and was given the name Mulan. The JTWC classified Mulan as a monsoon depression. Mulan travelled across the South China Sea and passed the Qiongzhou Strait before making landfall on Northern Vietnam and dissipating on August 11.
On August 10, another low pressure area formed northwest of Iwo Jima. The JMA named the system as Meari as it reached tropical storm status. Meari made landfall near Shizuoka Prefecture before it transitioned into an extratropical cyclone by August 14. The storm disturbed multiple events held in Japan, and caused some transportation to be suspended, and caused minor damages to houses. On August 14, the JMA began tracking a weak tropical depression that formed west of the International Date Line. The depression only lasted until the next day.
On August 19, the JMA began tracking a low pressure area north of Palau. Being inside PAR, PAGASA named the system Florita as it intensified into a tropical depression. The system was then named Ma-on by the JMA as it reached tropical storm status on August 22. The storm further strengthened into a severe tropical storm on the same day. Ma-on first made landfall over Maconacon in the province of Isabela before exiting the Philippine Area of Responsibility on August 24. Ma-on then made its second landfall near Yangjiang, China the next day and its final landfall in Northern Vietnam before it was last noted on August 26. Ma-on killed seven people in the Philippines and Vietnam and caused moderate damage to infrastructures in both countries.
On August 21 after Ma-on formed, another tropical depression formed northeast of Guam. Due to favorable conditions, the depression rapidly intensified into a tropical storm and was named Tokage by the JMA. Three days later, the JTWC upgraded Tokage into a typhoon, with the JMA following suit 3 hours later. Tokage reached its peak intensity as a Category 3 before entering hostile environments east of Japan. Tokage became an extratropical storm on August 25 before it was last noted south of Alaska. Additionally, on August 22, a tropical depression formed north of Typhoon Tokage. It dissipated on the same day. Nearing the end of August on the 28th, a tropical depression formed southeast of Japan. The depression was named Hinnamnor by the JMA 6 hours later upon formation. Hinnamnor later strengthened into the basin's first Category 5-equivalent typhoon.
Hinnamnor headed west towards the Ryuku Islands and stalled south of the prefecture while maintaining its strength. On August 30, another tropical depression formed south of intensifying Typhoon Hinnamnor. The depression was named Gardo by the PAGASA. Gardo was short lived and its structure was absorbed by Typhoon Hinnamnor near Taiwan. Hinnamnor later headed north in the East China Sea and restrengthened into a Category 3-equivalent typhoon. The typhoon then made landfall near Busan in South Korea and the JMA declared Hinnamnor as an extratropical low as it was located in the Sea of Japan. Hinnamnor killed at least 12 people and caused widespread damage across South Korea and Japan. Additionally, Hinnamnor's outer bands brought heavy rain across Taiwan and the Philippines causing moderate damage.
On September 5, a tropical depression formed near the Japanese island of Iwo-To. The JTWC designated the system as Invest 91W upon formation. The depression later intensified into a tropical storm and was named Muifa by the JMA. Muifa then intensified further into a Category 1 typhoon as it was located south of Okinawa. The typhoon reached its peak intensity as a Category 4 typhoon and passed the Yaeyama Islands on September 12 as it headed north very slowly while weakening. Muifa then slightly regained its strength in the East China Sea and made landfall near Shanghai in China two days later.
The typhoon suspended several flights and port activities within the city. Muifa also became the strongest typhoon to strike Shanghai, beating the previous record set by Typhoon Gloria in 1949. Muifa then degenerated into a remnant low over the Chinese mainland until it was last noted on September 16. On September 9, a tropical depression formed west of Wake Island. The JTWC later designated the depression as 15W. It was then named Merbok as it strengthened into a tropical storm on September 12.
Merbok then further intensified into a Category 1 typhoon before it headed north and transitioned into an extratropical cyclone by September 15. Merbok's remnants later brought gale force winds along Alaska. It then entered the Bering Sea, generating a dangerous storm surge which inundated several coastal villages and towns. Despite the impact, no injuries were reported. On September 11, the JMA began tracking a weak tropical depression which formed east of Iwo-To. The JTWC followed suit and designated the system as 16W on the next day.
The depression later strengthened into a tropical storm and was named Nanmadol by the JMA. Nanmadol then intensified into a Category 1 typhoon on the same day. It further reached its peak intensity as a Category 4 typhoon as it approached Japan. The approaching typhoon prompted the JMA to issue a special warning which advised at least 4 million people to evacuate. Nanmadol then made landfall on the island of Kyushu. The typhoon then turned east before weakening further on September 19. Nanmadol killed at least 2 people and left more than 70 people injured. Additionally, the typhoon left more than 200,000 people without electricity.
After Nanmadol, the monsoon trough east of the Philippines set up, and a tropical disturbance embedded in it got upgraded by the Japan Meteorological Agency into a tropical depression. On the following day, the Joint Typhoon Warning Center designed the depression as 17W. Two days later, as it was approaching Japan, it intensified into a tropical storm, and was given the international name of Talas. However, soon after, Talas weakened back into a tropical depression and dissipated as it made its approach towards Southern Japan. Despite this short duration, Talas killed at least three people and caused a power outage across Japan's Shizuoka Prefecture.
Another system in the monsoon trough formed in the Philippine Sea after Talas, and the JMA began tracking the system as a tropical depression. The depression was in a favorable environment for development and made the JTWC to classify the system as 18W on the next day. As the system formed within the Philippine Area of Responsibility (PAR), it was given the name Karding by the agency. On September 23, the depression intensified into a tropical storm, and was named Noru. After being initially sheared, Noru began a period of explosive intensification, developing a pinhole eye and intensifying briefly into a Category 5-equivalent super typhoon as it approached Luzon, Philippines.
Noru weakened due to increasing shear, and made its first landfall over the Polillo Islands in the municipality of Burdeos, Quezon. Shortly after, Noru rapidly weakened back into a Category 2-equivalent typhoon shortly before its second landfall over Dingalan, Aurora. Noru then entered the South China Sea where the typhoon re-intensified back into a Category 3-equivalent typhoon. Noru then re-developed a pinhole eye and reintensified into a Category 4 in the South China Sea, before getting sheared and striking Vietnam as a strong Category 2 before heading inland the Indochina Peninsula. Shortly after Noru's formation the JMA began tracking another tropical depression southeast of Japan. The depression was then named Kulap shortly after.
Kulap gradually intensified in the open Pacific Ocean, becoming a typhoon as per the Joint Typhoon Warning Center by September 28. As the Philippines was still reeling from the effects of Super Typhoon Noru, PAGASA named Tropical Depression Luis in the Philippine Sea, with JTWC later designating Luis as 20W. Luis left the PAR shortly after without affecting the country. Outside the PAR, the storm began intensifying and was classified as a tropical storm which was then named Roke by the JMA. It quickly reached Category 1 strength and hours later on September 29, as a Category 2 typhoon. The intensification didn't last long and like Kulap, it didn't impact any areas. Roke eventually became an extratropical cyclone. Roke's remnants later developed into a subtropical storm.
On October 11, a depression named Maymay by the PAGASA, formed off the coast of the Philippines. Maymay was rather short lived and dissipated the next day. Despite the depression being short-lived, two people were killed from the storm and the storm caused infrastructure and agricultural damage. On the next day, another tropical depression classified as 21W formed east of the Mariana Islands. 21W was also short lived and never made landfall. On October 13, another tropical depression formed west of the Philippines in the South China Sea. The depression reached tropical storm status and was named Sonca by the JMA.
Sonca made landfall in Quang Ngai Province, Vietnam and dissipated shortly after. 10 fatalities were reported in the region due to the heavy precipitation from the storm. On the same day Sonca formed, another tropical depression formed in the Philippine Sea. The storm was named Nesat on October 15, as the storm passed just north of the island of Luzon. Nesat then entered the South China Sea where it intensified further into a typhoon. Nesat reached its peak intensity as a Category 2 typhoon and began losing its strength as it approached Vietnam. Nesat dissipated on October 20, off the coast of Hainan Island. During its lifespan, Nesat caused minor damage across the Philippines, Taiwan, Vietnam, and Hong Kong. No fatalities were reported.
On October 18, Tropical Storm Haitang formed after interacting with a non-tropical low and degenerating Tropical Depression 21W since October 14. Haitang was also short lived and became extratropical the next day. On the same day Haitang formed, another tropical depression formed south of Okinawa. The depression was classified as 25W as it headed west before it dissipated in the South China Sea without intensifying further. However, two reported deaths were reported from 25W in the Philippines. On October 26, a tropical depression formed in the Philippine Sea. As the system approached the Philippines, the JMA classified the low as a tropical storm where it named it Nalgae.
Nalgae (Paeng) intensified into a severe tropical storm hours before striking the island of Catanduanes and the rest of the Bicol Region. Nalgae traveled across the Philippine archipelago, making 5 landfalls according to the PAGASA before emerging into the South China Sea where it further strengthened into a Category 1 typhoon, as per the Joint Typhoon Warning Center. As the typhoon approached the coast of China, Nalgae weakened back into a tropical storm due to hostile conditions and made landfall over Xiangzhou District, Zhuhai.
Nalgae became the first tropical cyclone to make landfall in November over the country since Nepartak in 2003. Nalgae also caused heavy damage and flooding across the Philippines and killed at least 154 people in the country alone. On October 28, as Nalgae ravaged Southern Luzon, a tropical depression formed southeast of the Philippines, passing near Palau, with the PAGASA naming it as Queenie.
On November 1, the JMA classified the system as a tropical storm and named it Banyan. Banyan however weakened back into a tropical depression the next day due to strong wind shear and dissipated before reaching the Philippines, only delivering some rainshowers as a remnant low. On November 11, a tropical depression formed near Wake Island. The JMA later named the system Yamaneko as it reached tropical storm status. Yamaneko was a short lived system and dissipated three days later. Yamaneko was an out to sea storm, harming no land area near it, and a relatively weak system in terms of intensity.
On December 9, a tropical depression formed east of the Philippines. The system continued to drift towards the Philippines and began to turn eastwards, where the system was named Pakhar by the JMA and Rosal by the PAGASA, as it reached tropical storm status. Pakhar's close approach to the Bicol Region and Polillo, Quezon prompted the PAGASA to raise Tropical Cyclone Warning Signal (TCWS) #1 in some areas in Southern Luzon. Pakhar killed 8 people indirectly from a flood that swept away a jeep in Rizal as it was making its close approach to the archipelago. Pakhar then intensified further, but later rapidly weakening and dissipating by December 12 from high vertical wind shear and dry air sent by the northeast monsoon, making its circulation exposed.
A tropical disturbance formed after crossing Palawan on late March. The disturbance would develop into a low-pressure area southeast of Da Nang, Vietnam, where it would intensify into the first tropical depression of the season, at 18:00 UTC on March 29.[9] At 21:00 UTC at the same day, the JTWC issued a Tropical Cyclone Formation Alert (TCFA) for the system after its development of a tropical depression.[10] On the next day, the agency upgraded to a tropical depression, assigning it the designation 01W. Shortly after, the agency issued their final advisory on the system after it made landfall in the southeastern part of Vietnam on March 30, shortly after dissipating.[11]
In Vietnam, floods caused by the storm have killed six people. The storm left one missing and eight injured. Flooding also caused two houses to collapse.[12] Overall damages reach 3.52 trillion VND (US$148.95 million).[13]
In real-time, the JTWC assessed that the system had peaked as a tropical depression, however in the JTWC's post-analysis of 2023, 01W would be recognized as a tropical storm.
The JTWC first noted the existence of a tropical disturbance on April 3.[14] Favorable conditions near the system helped it develop, with the JMA recognizing the system as a tropical depression on April 6.[15] Later in the day, the JTWC issued a TCFA for the system.[16] The following day, the JTWC recognized the system as a tropical depression and gave it the designation 02W.[17] At 21:00 UTC, the JTWC then upgraded it to a tropical storm.[18] On April 8, the system developed into a tropical storm and was named Malakas by the JMA.[19] Malakas continued traveling over the Pacific Ocean, and began to slowly intensify, becoming a severe tropical storm on the April 11, then a typhoon by April 12.[20][21] At around the same time, it entered the Philippine Area of Responsibility (PAR), receiving the local name of Basyang from the PAGASA at 03:00 UTC.[22] Malakas then lingered for a while at the border of the PAR before eventually exiting 5 hours later,[23] while intensifying into a Category 2-equivalent typhoon. Malakas then continued its intensification, reaching Category 3-equivalent status later that day, and into a Category 4-equivalent typhoon with 210 km/h (130 mph) 1-minute sustained winds on April 13, reaching its peak intensity. The following day, Malakas weakened to a Category 3-equivalent typhoon[24] as its eye structure degraded.[25] It further weakened to Category 1-equivalent status later in the day.[24] By April 15, it began its transition into an extratropical cyclone, with its structure rapidly deteriorating. The JTWC gave their final warning on the system at 09:00 UTC of the same day,[26] while the JMA did the same around 18:00 UTC.[27]
Although Malakas did not affect any major lands, due to its name being nearly homophonous to a vulgar Greek slang term (μαλάκας means "wanker"), the name Malakas was retired and will never be used again for a Pacific typhoon name.[28] In 2024, it was replaced with Amuyao (a mountain in Mountain Province) for future seasons.[29]
On April 8, the JTWC noted an area of convection persisting around 359 nautical miles (665 km; 413 mi) west-northwest of Palau.[30] Since the disturbance was in an environment favorable for development, the JMA recognized the system as a tropical depression east of Visayas later that day.[30][31] Around the same time, the PAGASA announced that the system had developed into a tropical depression, resulting in it being named Agaton by the agency.[32] PAGASA would begin issuing Tropical Cyclone Bulletins (TCBs) for the storm later that day.[33] On the next day, the JTWC later issued a TCFA for the system.[34] At 03:00 UTC, the agency upgraded it to a tropical depression and assigned it the identifier 03W.[35] On April 10, the JMA upgraded it to a tropical storm, naming it Megi.[36] Megi would make its first landfall in Calicoan Island, Guiuan at 07:30 PHT (23:30 UTC).[37] Megi then stalled in the Leyte Gulf for hours before making its second landfall in Basey, Samar.[38] Megi then weakened into a tropical depression after lingering over the islands of Samar and Leyte, resulting in PAGASA removing all warning signals for the system before it dissipated into a remnant low on the midnight of April 13.[39]
From April 8 to April 10, the storm meandered along the Eastern Visayas region, dumping heavy rain on the region.[40] PAGASA raised storm signals up to Signal No. 2 during the storm's onslaught.[41][42] Cebu City was placed under a state of calamity following the heavy rain.[43] Megi killed 214 people, which made it the deadliest tropical cyclone in the Philippines to form in May.[44][45] Megi would also injure eight people, leave 134 people missing,[46] and capsize a cargo boat in Ormoc following strong rains, winds, and flash floods which also displaced over 136,390 individuals.[47] The Department of Agriculture estimated agricultural damage to reach ₱3.27 billion,[48] while the Department of Public Works and Highways estimated infrastructural damage at ₱1.45 billion. Total damage from the storm was valued at ₱4.72 billion (US$90.8 million).[49]
A low-pressure area west of Luzon developed into a tropical depression on June 28.[50][51] At 20:00 PHT (12:00 UTC), the PAGASA had recognized the storm's development into a tropical depression, began issuing advisories, and named the system Caloy.[52] The following day, the JTWC issued a TCFA for the system.[53] Caloy remained almost stationary in the South China Sea before slowly moving northwestwards, eventually leaving the Philippine Area of Responsibility by 15:00 UTC.[54][55] As the PAGASA issued its last bulletin on the tropical depression, the JTWC began issuing warnings for the storm and was given the designation 04W.[56][57] Later, the Japan Meteorological Agency upgraded Caloy into a tropical storm, naming it Chaba.[58] Chaba continued to intensify in the South China Sea, later being upgraded into a severe tropical storm east of Hainan.[59] Typhoon Chaba's outer rainbands produced at least three tornadoes, which impacted Shantou, Chaozhou, and Foshan.[60][61][62] On July 1 at 21:00 UTC, the JTWC upgraded Chaba to a typhoon,[63] with the JMA doing the same 3 hours later on July 2 at 0:00 UTC.[64] Later that day at 07:00 UTC, it made landfall on Maoming.[65] Shortly after its landfall, both the JMA and the JTWC assessed that Chaba lost typhoon status, downgrading Chaba to a severe tropical storm and to a tropical storm respectively.[66][67] The JTWC then issued their final warning on Chaba at 15:00 UTC.[68] Shortly after, the JMA downgraded Chaba to a tropical storm;[69] it was further downgraded to a tropical depression on July 3 at 06:00 UTC.[70]
160 nautical miles (300 km; 180 mi) southwest of Hong Kong, the Fujing 001, a crane vessel tasked in assisting with the construction of an offshore wind farm, split in half and quickly sunk—leaving 26 crew members missing.[71][citation needed][72] Three of the 30 crew members were rescued, seen in a video published online by the Hong Kong Government Flying Service.[73] Another person was rescued by July 4, bringing the total number of people rescued to four. Twelve bodies from the ship were recovered.[72] More than 400 flights were suspended in Hainan; one person was injured in Macau.[74]
On June 30, the JTWC began issuing TCFAs for a tropical disturbance in the Philippine Sea, 530 nautical miles (980 km; 610 mi) south-southeast of Kadena Air Base in Japan.[75] At 14:00 PHT (06:00 UTC), the PAGASA recognized the disturbance's formation into a tropical depression, began issuing tropical cyclone bulletins, and named the system Domeng.[76] The JMA recognized the storm as a tropical depression at 12:00 UTC on the same day;[77] the JTWC followed shortly after.[78] On the next day, the Japan Meteorological Agency upgraded Domeng into a tropical storm and named it Aere as it was east of Batanes.[79] Aere then continued to track north and at 03:00 UTC on July 2, Aere left the Philippine Area of Responsibility; the PAGASA released its final bulletin on the storm shortly after.[80] Later that day, Aere made landfall over Okinawa.[81] On July 3 at 09:00 UTC, the JTWC downgraded Aere to a tropical depression.[82] However, three days later, the JTWC released another unofficial bulletin, reclassifying this disturbance as a subtropical storm, with an estimated pressure of 1000 hPa.[83]
On July 26, a low-pressure area northwest of the Mariana Islands developed into a tropical depression.[84][85] The system tracked northwest along the periphery of a subtropical high, with limited intensification.[86][87] After some development while over the Philippine Sea on July 28, the JMA upgraded the system to a tropical storm, giving it the name Songda.[88] The JTWC recognized the system's formation into a tropical depression on July 29, three days after the JMA.[89] Songda continued tracking northwestwards, passing over the waters of Kagoshima Prefecture on July 30, slowing down over the Yellow Sea.[90][91] It then recurved towards mainland Korea, losing its strength as it entered unfavorable conditions which sheared its center.[92][93] Songda dissipated on August 1; its remnants made landfall over North Korea on August 2.[94][95][96]
Songda caused heavy rainfall over the Kyushu and Shikoku regions of Japan and over Jeju Island in South Korea.[90][97][98] Despite strong winds and around 206 millimetres (8.1 in) of rain, no damages were reported on Jeju Island.[98]
A low-pressure area from a massive monsoon gyre developed into a tropical depression southeast of the Ryukyu Islands on July 29.[99] The PAGASA followed suit in upgrading it, then named the system Ester.[100] Trases moved generally northward over the Philippine Sea, maintaining its strength as it did so. Trases exited the Philippine Area of Responsibility at 05:00 PHT (21:00 UTC) on July 31; the PAGASA issued their last bulletin on the storm at 11:00 PHT (03:00 UTC).[101] As Trases neared the Okinawa Islands, the JMA upgraded it into a tropical storm, and it was given the name Trases, which replaced the name Sarika.[102]
Trases then passed over Okinawa, and later made landfall in Jeju Island.[103][failed verification] The JTWC issued a TCFA. Later, they upgraded Trases into a tropical depression, and gave the designation of 07W.[104] Trases then interacted with the nearby Tropical Depression Songda, and made a second landfall on the mainland of South Korea on August 1.[citation needed] Not long after, the JMA downgraded Trases into a tropical depression, and the JTWC issued their last advisory on it as it lingered near the western coast of South Korea.[105][106]
On August 2, the JTWC noted an area of disorganized convection in the South China Sea, approximately 105 nmi (194 km; 121 mi) to the south-southeast of Kaohsiung, Taiwan.[107] Under a favorable environment of warm sea surface temperatures, low wind shear, and moderate equatorial outflow, the convection rapidly consolidated a low-level circulation center which led the JTWC to issue a Tropical Cyclone Formation Alert by the next day.[108] The JMA then upgraded the system into a tropical depression by 18:00 UTC the same day.[109] The JTWC subsequently followed suit, designating the depression as 08W by early August 4.[110] The system then struck Huidong County, Guangdong at 01:40 UTC that same day, according to the China Meteorological Administration,[111] prompting the JTWC to issue its final advisory eight hours after landfall.[112]
On August 5, the JTWC noticed an area of convection with a consolidating low-level circulation center at approximately 7 nmi (13 km; 8.1 mi) to the south of Manila, Philippines.[113] The system then subsequently moved over Luzon and emerged into the South China Sea, where it organized but its circulation remained broad, having two distinct vortices present in satellite imagery.[114] The JMA then upgraded the system into a tropical depression by 00:00 UTC on August 8.[115] The JTWC designated the system as a "monsoon depression" six hours later due to many centers present in the system, before issuing a TCFA as it was steadily organizing with its radius of maximum winds shrinking.[116][117] By the next day, the JMA upgraded it into a tropical storm, and it was given the name Mulan.[118] The JTWC, however, did not recognize Mulan as tropical, due to its huge radius of maximum winds which "are typically present in monsoonal depressions."[119] The storm did not intensify further, according to the JMA, and by 02:50 UTC on August 10, Mulan made landfall on the coastal areas of Xuwen County in Zhanjiang, Guangdong.[120] The JTWC subsequently canceled the TCFA and downgraded its formation chances to medium.[121] The JMA then downgraded the storm into a tropical depression as it moved inland in Vietnam by the next day, and was last noted six hours later the same day.[122][123]
Heavy rainfall in Vietnam caused flash flooding which resulted in the deaths of six people. The northern region of the country experienced torrential rainfall of about 20 to 50 mm (0.79 to 1.97 in).[124] The storm also caused agricultural damages of an estimated ₫2.5 billion (US$107,000) after about 30,000 lobsters have died due to the effects of the storm.[125] In Son La the damaged reached 7 billion dong (US$295,000),[126] in Da Bac District is 2.3 billion dong (US$97,000)[127] and in Cao Phong District in Hoa Binh is 3 billion dong (US$127,000).[128] Total damages caused by Mulan were 33.7 billion VND (US$1.4 million).[13]
A low-pressure area developed into a tropical depression northwest of Iwo Jima on August 10.[129][130] After JMA named the system Meari, the JTWC followed suit in an unofficial bulletin, classifying this system as a tropical storm. However, according to the agency, because of colder waters, the storm returned to the Pacific Ocean after threatening the southern coast of Japan without causing major impacts.[131]
In preparation for Meari, government officials in Tokyo warned of heavy rains and strong winds. The final day of the Rock in Japan Festival was cancelled and ticket refunds were distributed. Three J1 League games in Tokyo and Kanagawa Prefecture were also cancelled. About 72,000 residents were evacuated in Shizuoka; two landslides were reported which isolated five houses. Power outages affected 1,200 homes in Shimizu and another 2,200 were affected in Kakegawa. Parts of the Shin-Tōmei Expressway, connecting Tokyo to Nagoya, were closed as a result of heavy rains, while tunnel speed limits were lowered. Rainfall also affected flights and bullet train services, the latter of which affecting 92,000 people. An elderly man in Hamamatsu sustained forehead injuries after being knocked down by strong winds.[132][133]
Homes in Central Japan were destroyed.[134]
On August 19, the JMA began tracking a low pressure area in the Philippine Sea, around 500 kilometres (310 mi) north of Palau.[135] The low pressure area slowly moved westwards, eventually developing into a tropical depression on August 20.[136] The following day, the PAGASA also announced the system's formation into a tropical depression, and as a result of its position within the PAR, assigned it the name Florita.[137] Shortly afterwards, the JTWC designated the system as 10W.[138] Florita remained relatively weak, having an exposed circulation. By August 22, it was upgraded to tropical storm, being designated Ma-on by the Japan Meteorological Agency, with the JTWC later following suit.
On the evening of August 22, the exposed low-level circulation center was obscured by a convection burst, which later turned into a central dense overcast, which prompted the JMA to upgrade Ma-on into a severe tropical storm. At 10 a.m. PHT, Ma-on made landfall at Maconacon, Isabela as a high-end severe tropical storm, just short of typhoon intensity, according to the PAGASA.[139] Four fatalities occurred;[140] infrastructure damage was estimated to be ₱571 million (US$10.4 million), while agricultural damage was estimated to be ₱1.86 billion (US$33.6 million).[141]
On the morning of August 25, Ma-on made landfall in Guangdong, China. Shortly after, the system moved westward to the Gulf of Tonkin. Later, the storm made its final landfall in Móng Cái, Quảng Ninh Province in Vietnam.[142]
The storm caused moderate damage in Vietnam and killed three people.[143]
On August 21, the JMA noted that a tropical depression had formed to the northeast of Guam.[144] Under a favorable environment of warm sea surface temperatures, low wind shear, and very good poleward outflow, the system rapidly intensified to become Tropical Storm Tokage by early next day.[145][146] Moving north-northwest, Tokage would intensify into a severe tropical storm later by the same day,[147] and by 09:00 UTC on August 23, the JTWC upgraded Tokage to a typhoon, with the JMA following suit three hours later.[148][149] The storm would peak six hours later according to the JMA, with 10-minute sustained winds of 140 km/h (87 mph) and a pressure of 970 hPa, while the JTWC estimated Tokage to have peaked at 00:00 UTC the next day, with 1-minute sustained winds of 175 km/h (109 mph), making Tokage a Category 3-equivalent typhoon on the Saffir-Simpson scale.[150][151][152] After peaking, Tokage rapidly weakened under high wind shear as it curved northeastwards due to a deep-layered subtropical ridge positioned to the east of the storm,[153] and commenced extratropical transition by 03:00 UTC on August 25.[154] The storm would complete its transition 12 hours later, with the JTWC issuing its final advisory, and the JMA following suit three hours later.[155][156]
On August 27, the JTWC began monitoring a disturbance located 461 nautical miles off Iwo Jima, which they labeled Invest 90W. Following organization, the agency issued a Tropical Cyclone Formation Alert (TCFA) at 04:10 UTC the next day.[157] 6 hours later, it intensified into a tropical storm, being named Hinnamnor by the JMA, which replaced the name Nock-ten.[158] Moving due west, Hinnamnor steadily strengthened, gaining Category 1-equivalent winds of 75 kn (139 km/h; 86 mph) on August 29.[159] At the same time, the JMA upgraded Hinnamnor to a typhoon.[160] The system underwent rapid intensification, and proceeded to gain Category 3-equivalent winds at 12:00 UTC the same day.[161] Quickly strengthening overnight, the storm quickly grew with Category 5-equivalent winds of 140 kn (260 km/h; 160 mph), with a minimum pressure of 920 hectopascals (27.17 inHg) with a pinhole eye.[162][163][164] Hinnamnor then weakened following an eyewall replacement cycle, slowing down as it neared Okinawa. As it stalled south of the Prefecture, the storm re-intensified, with an intense central dense overcast forming along with a larger eye.[165][166][167] On August 31, at 5:30 p.m. PHT (09:30 UTC), Hinnamnor entered the PAGASA's Philippine Area of Responsibility and was named Henry.[168] Hinnamnor later weakened into a Category-1 typhoon as it turns back north-northwest in the East China Sea. The system later re-strengthen into Category-3 typhoon, with deep convection becoming more symmetric on September 4. It later weakened back into Category-2 and made landfall over Geoje, South Gyeongsang Province, South Korea.[169][170] The JMA issued its last advisory on Hinnamnor, and declared it an extratropical low.[171] The low moved northward and last noted in Okhotsk, Russia on September 7.[172][173]
In Ifugao, a man was buried in the landslide due to heavy rains caused by the typhoon.[174] Several flights were canceled to and from Okinawa.[175] When the typhoon made landfall in South Korea, it brought severe impacts. 60,000 homes were left without electricity and an elderly woman died due to currents. Another 9 people are missing. In the city of Pohang, South Korea, seven people were killed in the flooding of an underground parking garage. Hinnamnor caused >$1 billion in damages.[176]
On August 30 at 00:00 UTC, the JMA began tracking a westward-moving tropical depression.[177][178] A few hours later, the PAGASA gave it the local name Gardo due to it being inside their area of responsibility.[179] The JTWC issued a TCFA for the system,[180] and would then upgrade the system to a tropical depression, designating it as 13W. Due to its proximity to Typhoon Hinnamnor,[181] its outflow fully exposed 13W's circulation.[182] On September 1, the JMA, the JTWC, and the PAGASA issued their final warnings on the system as it was absorbed into Hinnamnor.[183][184][185]
The JTWC detected a disturbance at approximately 255 nmi (472 km; 293 mi) from Iwo-To. According to the agency, the cyclone achieved a favorable environment for a more comprehensive intensification because of the warm waters (between 30 and 31 °C [86 and 88 °F]) and was designated as Invest 91W.[186] A day later, the cyclone became a tropical storm according to the JTWC, being 696 nmi (1,289 km; 801 mi) SSE of Kadena Air Base. The JMA, however, had not released any bulletin to designate this system until then.[187] When the storm entered PAGASA's area of responsibility, it was named Inday; in its first bulletin, the agency stated that the storm was unlikely to impact the Philippines.[188] Within the PAR, the storm strengthened into a severe tropical storm according to PAGASA.[189] Muifa then intensified into a typhoon according to the JTWC, as it reached 120 km/h (75 mph; 65 kn) in sustained one-minute winds.[190] Muifa continued intensifying, with the JTWC then assessing that Muifa reached Category 3-equivalent status on September 10. Then strengthening a bit more to a Category 4-equivalent typhoon.[191] On September 12, Muifa hit Ishigaki Island;[192] it left the PAR the same day in the afternoon.[193] With winds of 155 km/h (96 mph; 84 kn), the typhoon made landfall in Zhoushan around 20:30 local time, making a second landfall shortly after in Shanghai. It is the most powerful typhoon to strike Shanghai on record.[194][195] Muifa was downgraded to a tropical storm when it made landfall according to the JTWC.[196] Muifa was downgraded to a tropical depression again by the JTWC on its last bulletin for the system.[197]
On September 13, China issued an orange alert (Signal #2) on Muifa, warning that it could impact the Taiwan Strait, in addition to the provinces of Jiangsu, northern Zhejiang, and Shanghai.[198] Several flights departing from the airports in Zhoushan, Ningbo and Shanghai were suspended due to Muifa. Activities in the Port of Shanghai were also suspended.[199]
On 00:00 UTC of September 9, the JMA began tracking a weak tropical depression that had developed west of Wake Island. The JMA downgraded the system to a low-pressure area shortly thereafter.[200] However, on the next day, the JMA re-upgraded the system to a tropical depression. The JTWC followed suit and began issuing advisories, assigning it the designation 15W.[201] In its fifth bulletin, the JTWC stated that 15W turned into a tropical storm when it reached 65 km/h (40 mph; 35 kn) one-minute sustained winds.[202] The JMA named the system Merbok on September 12, due to it having achieved 10-minute sustained winds of 65 km/h (40 mph).[203] Later that day, Merbok reached severe tropical storm status.[204] The next day, the JTWC reported that Merbok became a Category 1 typhoon, reaching sustained winds of 120 km/h (75 mph; 65 kn).[205] On September 15, the JTWC gave its final bulletin on Merbok, noting that it had moved away from habitable areas.[206]
After transitioning into an extratropical cyclone, the system tracked generally northeastward and continued to deepen as it encountered record warm waters near the western Aleutian Islands.[207] It crossed the islands, entering the Bering Sea late on September 15 (HDT) as it maintained hurricane-force winds and reached its minimum central barometric pressure of 937 mbar (27.67 inHg) early the next day. The storm track generated a large dynamic fetch across the Bering Sea, which contributed to a dangerous storm surge that inundated at least 35 communities across 1,300 miles of coastline in western Alaska.[208] Governor Mike Dunleavy declared a state of emergency in the region before the cyclone hit.[209] Water levels in Unalakleet peaked at around 12.5 ft (3.8 m), which was among its largest peaks on record. In Golovin, the 1913 record of flooding was broken. Significant flooding and gale force winds were widely reported across the west coast of Alaska. Homes floated off their foundations, major erosion, subsistence infrastructure damage, and power outages were reported in Hooper Bay, Nome, Shaktoolik, Newtok, and Kotlik among others.[210] Despite the widespread coastal flooding, no injuries were reported.[211]
On 06:00 UTC of September 9, the JMA briefly tracked a weak tropical depression to the east of Iwo To, Japan.[212] The JMA re-upgraded the system to a tropical depression two days later. On September 12, the JTWC designated the system 16W and it was located approximately 262 nmi (485 km; 302 mi) southwest of Iwo-To.[213] On the same day, the JMA and the JTWC upgraded the system to a tropical storm, with the JMA assigning it the name Nanmadol.[214][215] The storm then reached typhoon status on September 15.[216] Nanmadol rapidly intensified into a very strong typhoon, according to the JTWC's thirteenth bulletin.[217] Nanmadol then entered the PAGASA's Philippine Area of Responsibility at 09:40 UTC on September 16, and was given the name Josie,[218][219] however, it quickly left the PAR, just over four hours later, at 14:00 UTC on the same day.[220] A system pressure of 910 hPa (mbar) was then recorded, the lowest so far this season.[221][failed verification] When it made landfall in southern Japan, the typhoon was downgraded to Category 3-equivalent status upon reaching Kyushu Islands.[222] Upon directly impacting the country, it was downgraded again to Category 1-equivalent status.[223] On its way to northeast Japan post-landfall, the cyclone was downgraded to a tropical storm by the JTWC. The JMA also followed suit and downgraded it to a severe tropical storm. In its twenty-ninth bulletin, the JTWC reported that Nanmadol was weakening as it moved over land in Japan and would be downgraded to an extratropical cyclone.[citation needed]
Before the cyclone hit the country, the JMA issued a special warning that Nanmadol could cause severe damage, and at least 4 million people have been advised to leave their homes.[224] Exceptionally high volumes of precipitation were recorded and resulted in flooding in streets, destruction of building walls. and destroyed power poles. At least 2 people died and another 70 people were injured. More than 200,000 people were left without electricity.[225][226][227] In South Korea, the winds and rain caused by the typhoon also caused inconvenience. One person was injured, more than 700 people were evacuated from their homes, fallen trees were reported, and some locations in the southeast portion of the country were left without electricity.[228]
On September 20, a disturbance turned into a tropical depression according to the JMA.[229] The JTWC reported that the low pressure encountered favorable environments for intensification by warm waters and low wind shear.[230] The next day, the JTWC designated the system as 17W as it was upgraded into a tropical depression.[231] On September 23, the cyclone was upgraded to a tropical storm according to the JTWC's sixth bulletin. The storm was named Talas by the JMA.[232] When it made landfall in southern Japan, it was downgraded to a tropical depression according to the seventh JTWC bulletin.[233]
A 10–12 cm (3.9–4.7 in) total hourly, total 30–42 cm (12–17 in) in twelve hours precipitation hit in Hamamatsu, Shizuoka City and other areas of Shizuoka Prefecture. A landslide hit Ōigawa Railway in Kawane, two transmission towers collapsed in Aoi-ku, Shizuoka, and 119,200 customers were affected by power outages in Shizuoka Prefecture, according to Heita Kawakatsu, Governor of Shizuoka. According to the Japan Fire and Disaster Management Agency official report, Talas killed three people and injured six others.[234]
On September 21, a disturbance developed into tropical depression near the Philippines, according to the JMA.[235] The JTWC designated this disturbance as Invest 95W and issued a bulletin noting that the low pressure system could have reasonable intensification due to low wind shear and warmer water.[236] Hours later, the JTWC upgraded the system into a tropical depression, designating it as 18W.[237] The PAGASA then followed suit on 00:00 UTC of September 22, and the tropical depression was assigned the name Karding.[238] A few hours later, the system reached tropical storm intensity and the JMA assigned it the name Noru (2216).[239] On 24 September, Noru entered the Philippine area of responsibility and reached typhoon intensity.[240] Noru then underwent explosive intensification, during which, according to the JTWC, Noru's 1-minute sustained winds increased by 165 km/h (105 mph).[241] At 00:00 UTC, Noru was classified as a Category-5 super typhoon.[242] At 5:30 p.m. Philippine Standard Time, according to the PAGASA, Noru struck Burdeos, Polillo Islands, Quezon Province. When it made landfall in the northern Philippines, the cyclone was downgraded to Category 4 according to the JTWC.[243] At 8:20pm PHT, Noru struck Dingalan, Aurora as a typhoon according to PAGASA.[244] The terrain of the Sierra Madre mountain range weakened Noru as it passed through Central Luzon.[245] Noru then slightly re-intensified in the West Philippine Sea, leaving the PAGASA's area of responsibility on Monday morning.[246] It made landfall near Da Nang, Vietnam on September 28 before JTWC released its final warning on the storm shortly after.
The National Disaster Risk Reduction and Management Council (NDRRMC) of the Philippines reported at least ₱304 million (US$6.18 million) in infrastructural damages and ₱3.08 billion (US$62.5 million) in agricultural damages, totalling to ₱3.38 billion (US$68.7 million). 40 people have been reported dead following the typhoon, another 5 remain missing. In Vietnam, Noru killed 9 people and caused an economic loss of 5.776 trillion VND (US$244.41 million).[13]
On September 24, the JTWC released a first report on a low pressure system and because it entered warmer waters and low wind shear, the agency named it Invest 96W.[247] The next day, JMA classified the system as a tropical depression.[248] Hours later, the JTWC followed suit, and designated him 19W.[249] The next day, the cyclone intensified and the JTWC in its second bulletin, classified it as a "tropical storm".[250] The JMA followed suit and called it Kulap.[251] The JMA quickly classified it as a "severe tropical storm" but the JTWC went further and upgraded it to a Category 1 typhoon.[252][253] Upon threatening the Japanese coast, the cyclone continued its course until it was downgraded to a tropical storm, according to bulletins released by the two agencies.[254][255] By moving to cooler areas and without threatening any habitable areas, the system transitioned into an extratropical cyclone, prompting the agencies to issue their final advisories on the system.[256][257]
On September 27, the JMA began to monitor a weak tropical depression that had developed in the Philippine Sea and had been designated as Invest 98W by the JTWC. The agency said in a TCFA bulletin that because it was in warmer waters and low shear, there was scope for broader intensification. The prediction was confirmed, and a few hours later, it was classified as a tropical depression, being called 20W.[258] The following day, the storm entered the PAGASA's area of responsibility and was called Luis, but it did not directly threaten the Philippines and left the PAGASA's area of responsibility a few hours later. Subsequently, the cyclone gained strength and reached a "tropical storm" according to the second JTWC bulletin. The JMA named the system Roke.[259] Two days later, the JTWC and JMA classified it as a Category 1 typhoon,[260] The intensification did not last long and Roke was downgraded to a tropical storm.[261] Having the same fate as its predecessor Kulap, the JTWC released a final bulletin in which Roke had been downgraded to an extratropical cyclone.[262] However, the cyclone intensified into a subtropical storm according to the JTWC's special bulletin. On October 1, it weakened into a subtropical depression.[263]
On October 9, the JTWC started to monitor a persisting area of convection with a poorly-defined circulation at approximately 645 nmi (1,195 km; 742 mi) to the east of Manila, Philippines.[264] Under a favorable environment of warm sea surface temperatures, low to moderate wind shear, and strong poleward outflow,[265] the system continued to organize before PAGASA upgraded it as a tropical depression, naming it as Maymay, late on October 10.[266] The JMA subsequently followed suit by the next day.[267] Later that same day, the JTWC issued a TCFA on Maymay, noting that the storm's center was tucked beneath the southeast side of an intense but disorganized convection.[268] However, the storm's convective structure was detached from the main center due to a TUTT cell to the northeast of it,[269] which made the storm weaken as it moved northwestwards, prompting the JMA to downgrade Maymay into a low-pressure area on October 12.[270] The PAGASA subsequently followed suit late on the same day,[271] and JTWC cancelled their TCFA by October 13.[272]
Though short-lived, Maymay killed two people in Cagayan, Philippines.[273] The Provincial Disaster Risk Reduction Management Office (PDDRMO) in Cagayan estimated infrastructure and agricultural damage at ₱533 million (US$9.16 million) and 33,432 individuals were impacted by Maymay.[274]
On October 12, the JTWC started to monitor an organizing area of convection with a fully obscured low-level center at approximately 325 nmi (602 km; 374 mi) to the west of Saipan.[275] Within a favorable environment of low wind shear, warm sea surface temperatures, and fair equatorial outflow, the agency would later issue a TCFA for the system four hours later,[276] and initiate advisories on Tropical Depression 21W at 15:00 UTC the same day, noting the convection of the system became compact and symmetrical, and was displaced slightly from the center.[277] The JMA followed suit three hours later.[278] The system soon became severely sheared by the next day as wind shear increased dramatically while it continued moving eastward,[279] before it got embedded into a convergent outer boundary of a deep TUTT cell positioned towards the northwest,[280] helping the storm re-organize and intensify into a tropical storm by October 14.[281] The storm, however, accelerated north-northeastwards at that point, as it got embedded under strong southerly flow within the eastern periphery of a broad subtropical upper-level low that would later become Tropical Storm Haitang,[282] and it soon opened up into a tropical wave later the same day.[283]
Late on October 11, the JTWC started to monitor a scattered area of convection with a poorly-organized broad low-level center at approximately 150 nmi (280 km; 170 mi) to the west-southwest of Manila, Philippines.[284] Within a marginally favorable environment of no distinct outflow established, low to moderate wind shear, and warm sea surface temperatures, the system slightly organized by the next day, with flaring convection and its center remaining exposed.[285] Nonetheless, the JMA upgraded the system into a tropical depression on October 13.[286] The JTWC later issued a TCFA on the system on the same day, noting fragmented deep convection was wrapping into its broad low-level center.[287] By the next day, the JTWC initiated advisories on the storm, designating it as 22W.[288] Moving westward, the storm intensified into a tropical storm six hours later, with the JMA naming it as Sonca.[289] Sonca failed to intensify further as its center remained exposed, with deep convection displaced to the west due to strong wind shear,[290] and it soon made landfall on Da Nang, Vietnam late on the same day, prompting the JTWC to issue their final advisory on the system.[291] The JMA followed suit by October 15, as Sonca weakened into a tropical depression.[292]
As Sonca moved inland, it brought heavy rainfall to central Vietnam, with 700 mm (28 in) of rain fell in Da Nang during a 24-hour period on October 14–15; this resulted in major flooding throughout the region, with 10 fatalities reported.[293] Initial estimated economic losses in Da Nang City caused by Sonca's heavy precipitation are around 1.48 trillion VND (US$60.8 million).[294][295][296] Infrastructure losses in Thừa Thiên Huế province reached 337 billion VND (US$13.5 million). 2 people were killed and 4 injured in the province.[297] Overall, damages inflicted by Sonca were 2.4 trillion VND (US$101.5 million).[13]
Nesat formed from an area of disturbed weather east of the Philippines, and on October 13, entered the PAGASA's Philippine Area of Responsibility and was named Neneng by the agency.[298] Neneng continued to intensify in the Philippine Sea and was given the international name of Nesat by the Japan Meteorological Agency. On October 16, at 3:50 a.m. Philippine Standard Time, the PAGASA noted that Nesat (Neneng) made its first landfall in the island of Calayan in the province of Cagayan as a severe tropical storm.[299] According to the PAGASA, Nesat underwent "extreme" rapid intensification[300] and became a typhoon after it passed through the Luzon Strait. A day after, Nesat exited the PAR, and the PAGASA stopped issuing advisories on the system.[301]
Flooding in northern Luzon caused damage to buildings and infrastructure. According to NDRRMC, 103,662 people were impacted when Nesat moved through, with 4,459 displaced; there were no fatalities.[302] A final report by PDRRMO estimated infrastructure and agricultural damage at ₱474.2 million (US$8.15 million).[303]
On October 14, a non-tropical low with subtropical characteristics started to persist north of Minamitorishima and northwest of then-degenerating Tropical Depression 21W.[304][305] The low remained stationary, slowly weakened and acquired more tropical characteristics next three days,[306] and JTWC eventually declared a tropical depression early on October 18 when the system had been deepening again and became compact.[307] Although the JMA reported a gale-force non-tropical low at the same time,[308] the system was soon analyzed as a tropical storm and named Haitang.[309] The center of the storm soon became weakly-defined as extensive dry air entrained the storm,[310] prompting the JTWC to downgrade the storm into a tropical depression and issue their final advisory late on the same day.[311] The JMA, however, continued to issue advisories on the storm as it moved northeastwards,[312] and transitioned into an extratropical cyclone on October 19.[313]
On October 19, a low-pressure area over the Philippine Sea east of northeastern Luzon developed into a tropical depression and was given the name Obet by PAGASA. The following day, the JTWC upgraded it to a tropical depression, designating it as 25W. The PAGASA initially expected the depression to be a tropical storm,[314] but the system would not strengthen further.[315] On October 21, 2022, the depression slightly intensified while moving towards the Luzon Strait.[316] The depression decelerated while moving west southwestward over the Philippine Sea and continued to move westward while maintaining its strength as it threatened Batanes on October 21.[317] Later that day, PAGASA would hoist Tropical Cyclone Wind Signal No. 1 for Batanes, Babuyan Islands, and the northeastern portion of mainland Cagayan due to the expected strong winds from 25W.[318] The next day, the depression exited the Philippine Area of Responsibility (PAR) while moving slowly westward.[317] The depression was located approximately 432 km east-southeast of Hong Kong and moved westward at 19 km/h (10 knots), before it dissipated. PAGASA forecasted that 25W would generate heavy rainfall over parts of northern Luzon by October 22, 2022.[319] However, later that day, the state weather bureau said that 25W was no longer expected to bring heavy rainfall to the country.[320] The depression gradually weakened and was classified as a remnant low on October 23.[321] According to Municipal Disaster Risk Reduction & Management Office (MDRRMO), two deaths, a fisherman and his wife, were reported due to 25W.[322] According to the DSWD DROMIC Report #6, a total of 7,327 families or 24,245 people were affected in 74 Barangays.[317] Tropical Depression 25W did not have a direct impact on the Philippines but would pass winds and heavy rains in some areas such as Batanes and Babuyan Islands.[321] Despite the fact that the depression did not make landfall in the Philippine, it would pass very close to the province of Batanes on evening of October 21, causing rain and strong winds in Northern Luzon.[316][323] According to the NDDRMC, the depression has caused at least ₱136,700 PHP (US$2519.14) in agricultural damages.[324]
On October 26, the JTWC reported in its TCFA (Tropical Cyclone Formation Alert) that a low pressure area near the Philippines was able to develop because of warm waters and low wind shear. The agency designated it as Invest 93W.[325] The JMA and the PAGASA then classified the disturbance as a tropical depression, with the latter assigning the name Paeng to the system.[326][327] The JTWC upgraded the system to a tropical depression a day later, at 00:00 UTC on October 27, and it was given the designation 26W.[328] At the same time, the JMA upgraded the typhoon to a tropical storm, and was named Nalgae.[329] The following day, PAGASA and JTWC classified it as a severe tropical storm approaching the northeast of the Philippines. PAGASA issued danger alerts (Signal No. 3), informing that damage could be registered as Paeng approached the archipelago.[330][331] On 17:10 UTC on October 28, Nalgae made its first landfall at Virac, Catanduanes, followed by another landfall at Caramoan, Camarines Sur just thirty minutes later. It crossed the Bicol Region and exited into the Sibuyan Sea, and later made its third landfall in Buenavista, Quezon, maintaining its strength as it did so.[332] Nalgae then headed southwestward and struck Mogpog in the island province of Marinduque,[333] then later crossed the Sibuyan Sea again and made its fifth landfall in Sariaya, once again in the province of Quezon, later passing into Laguna.[334] Nalgae then passed through Metro Manila and Rizal, heading into Bulacan by evening of October 29.[335] By the next day, Nalgae weakened into a tropical storm in the West Philippine Sea,[336] but re-intensified into a severe tropical storm a few hours later, and exited the Philippine Area of Responsibility a day later. Upon its exit from Philippine jurisdiction, Nalgae then intensified into a Category 1-equivalent typhoon on JTWC; however, the JMA maintained its severe tropical storm classification for the system. It then approached the Pearl River Delta, prompting officials in Hong Kong and Macau to raise Signal No. 8 from November 1 to 2.[337][338][339] At around 04:50 CST on November 3, 2022, Nalgae made its final landfall at Xiangzhou District, Zhuhai as a tropical depression, making it the first tropical cyclone since Nepartak in 2003 to make landfall in China in November.
On the island of Mindanao, at least 68 people died[340][341] due to continuous flooding and landslides that were partially caused by Nalgae.[342][343] 14 individuals were also confirmed to have been missing; 11 from the Maguindanao province, and 3 from the Soccsksargen region.[342][344]
On October 29, the JTWC released a first TCFA, reporting that a tropical disturbance, designated as Invest 94W, had formed far from the Philippine Sea. However, hours later, the agency canceled the TCFA over this low-pressure area after it had lost strength.[345][346] However, the agency released a second TCFA, reporting that the disturbance had re-intensified, and classified the possibility of tropical depression as "high". The JMA went further in a bulletin, and already classified it as a depression.[347][348] At 21:00 UTC on October 30, the tropical depression was designated 27W.[349] Upon entering the Philippine Area of Responsibility, it was given the local name Queenie by PAGASA.[350] Banyan intensified into a tropical storm, and was given the international name Banyan by the Japan Meteorological Agency.[351] As of November 1, 2022, Banyan then weakened due to strong wind shear, and then weakened into a tropical depression the next day after weakening.[352] Later that afternoon, the PAGASA had issued their final advisory on Banyan after it dissipated into a remnant low pressure area.[353] The depression was last seen 200 km north of Sonsorol, moving west-northwestward at 7 km/h (4 knots) over the past 6 hours.[354] The remnants of Banyan continued to cause some rain in eastern Mindanao.[355]
On November 11, a tropical disturbance was formed in Wake Island, it was designated as 95W by the JTWC on its TCFA.[356] It strengthened into a tropical depression later on the next day, designated as 24W. The system then strengthened to a tropical storm, gaining the name Yamaneko from the JMA. The system was short-lived and weakened due to cooler sea temperatures. The system dissipated on the morning of November 14. It was a relatively weak storm with maximum sustained winds of 65 km/h (40 mph). There were no reports of damage or casualties caused by Yamaneko. The storm did not make landfall and dissipated on November 14, 2022.
An area of low pressure formed east of Mindanao within the Philippine Sea which would later be designated as an invest which would move generally northwest towards the island of Samar and east of the Visayas region. On December 9, the Low Pressure Area (LPA) was upgraded into a Tropical Depression by the Japan Meteorological Agency and be designated as 29W by the JTWC later on.[357][358] As it was inside the Philippine Area of Responsibility, it was assigned the name Rosal after it was designated as a tropical depression by the Philippine Atmospheric Geophysical Astronomical Services Administration (PAGASA). Rosal's close approach to the archipelago would then prompt the raising of tropical cyclone warning signals across some parts of Bicol Region. The storm would later intensify into a tropical storm and be named "Pakhar" by the JMA. By the morning of December 12, Pakhar reached its peak intensity east of the Babuyan Islands and later weaken rapidly by wind shear in the Philippine Sea east of Extreme Northern Luzon. During the early morning hours of December 13, PAGASA would downgrade Pakhar to a remnant low east of northeastern Cagayan, dissipating due to dry air from the northeast monsoon surge, which tore apart Pakhar's circulation.[359]
Pakhar's trough resulted in heavy rain, which indirectly resulted in 8 deaths in the province of Tanay, Rizal after a jeep was swept away by flash flooding.[360]
Within the Northwest Pacific Ocean, both the Japan Meteorological Agency (JMA) and the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) assign names to tropical cyclones that develop in the Western Pacific, which can result in a tropical cyclone having two names.[376] The Japan Meteorological Agency's RSMC Tokyo — Typhoon Center assigns international names to tropical cyclones on behalf of the World Meteorological Organization's Typhoon Committee, should they be judged to have 10-minute sustained windspeeds of 65 km/h (40 mph).[377] PAGASA names to tropical cyclones which move into or form as a tropical depression in their area of responsibility 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.[376] The names of significant tropical cyclones will be retired by both PAGASA and the Typhoon Committee in the spring of 2023.[377]
During the season, 25 tropical storms developed in the Western Pacific and each one was named by the JMA, when the system was judged to have 10-minute sustained windspeeds of 65 kilometres per hour (40 mph). 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.[378] During the season, the names Trases, Mulan, Hinnamnor, and Yamaneko were used for the first (and only, in the case of Hinnamnor) time after they replaced Sarika, Haima, Nock-ten and Hato, which were retired following the 2016 and 2017 seasons.
| Malakas | Megi | Chaba | Aere | Songda | Trases | Mulan | Meari | Ma-on | Tokage | Hinnamnor | Muifa | Merbok |
| Nanmadol | Talas | Noru | Kulap | Roke | Sonca | Nesat | Haitang | Nalgae | Banyan | Yamaneko | Pakhar | |
After the season, the Typhoon Committee announced that the names Malakas, Megi, Ma-on, Hinnamnor, Noru and Nalgae would be removed from the naming lists, and they will never be used again to name another typhoon.[379] In 2024, they were replaced by Amuyao, Gosari, Tsing-ma, Ong-mang, Hodu and Jamjari respectively.[380] This surpassed the previous record for the number of typhoon names retired after a single season – five, held by the 2006, 2019, and 2020 seasons.
| Main list | ||||
|---|---|---|---|---|
| Agaton | Basyang | Caloy | Domeng | Ester |
| Florita | Gardo | Henry | Inday | Josie |
| Karding | Luis | Maymay | Neneng | Obet |
| Paeng | Queenie | Rosal | Samuel (unused) | Tomas (unused) |
| Umberto (unused) | Venus (unused) | Waldo (unused) | Yayang (unused) | Zeny (unused) |
| Auxiliary list | ||||
| Agila (unused) | Bagwis (unused) | Chito (unused) | Diego (unused) | Elena (unused) |
| Felino (unused) | Gunding (unused) | Harriet (unused) | Indang (unused) | Jessa (unused) |
During the season, PAGASA used its own naming scheme for the 18 tropical cyclones, that either developed within or moved into their self-defined area of responsibility.[381] The names were taken from a list of names, that was last used during 2018 and are scheduled to be used again during 2026.[381] All of the names are the same except Obet, Rosal and Umberto which replaced the names Ompong, Rosita and Usman after they were retired.[381] The names Obet and Rosal were used for the first time this year.
After the season, PAGASA announced that they removed the names Agaton, Florita, Karding and Paeng from its rotating naming lists due to the number of deaths and amount of damage they caused, and they will never be used again for another typhoon name within the Philippine Area of Responsibility (PAR). On May 5, 2023, they were replaced with Ada, Francisco, Kiyapo and Pilandok respectively for the 2026 season.[382]
This table summarizes all the systems that developed within or moved into the North Pacific Ocean, to the west of the International Date Line during 2022. The tables also provide an overview of a system's intensity, duration, land areas affected, and any deaths or damages associated with the system.
| Name | Dates | Peak intensity | Areas affected | Damage (USD) |
Deaths | Refs | ||
|---|---|---|---|---|---|---|---|---|
| Category | Wind speed | Pressure | ||||||
| TD | January 27–28 | Tropical depression | Not specified | 1006 hPa (29.71 inHg) | None | None | None | |
| 01W | March 29–31 | Tropical depression | Not specified | 1006 hPa (29.71 inHg) | Vietnam | $149 million | 6 | [13][12] |
| Malakas (Basyang) | April 6–15 | Very strong typhoon | 165 km/h (105 mph) | 945 hPa (27.91 inHg) | Guam, Caroline Islands, Bonin Islands | None | None | |
| Megi (Agaton) | April 8–12 | Tropical storm | 75 km/h (45 mph) | 996 hPa (29.41 inHg) | Philippines | $200 million | 214 | [44] |
| TD | May 30 | Tropical depression | Not specified | 1006 hPa (29.71 inHg) | Philippines | None | None | |
| Chaba (Caloy) | June 28 – July 5 | Typhoon | 130 km/h (80 mph) | 965 hPa (28.50 inHg) | Philippines, China, Vietnam | $464 million | 12 | [72][383] |
| Aere (Domeng) | June 30 – July 4 | Tropical storm | 85 km/h (50 mph) | 994 hPa (29.35 inHg) | Japan | Unknown | None | |
| TD | July 24–25 | Tropical depression | 55 km/h (35 mph) | 1006 hPa (29.71 inHg) | None | None | None | |
| Songda | July 26 – August 1 | Tropical storm | 75 km/h (45 mph) | 996 hPa (29.41 inHg) | Japan, South Korea, North Korea | None | None | |
| Trases (Ester) | July 29 – August 1 | Tropical storm | 65 km/h (40 mph) | 998 hPa (29.47 inHg) | Ryukyu Islands, South Korea | None | None | |
| 08W | August 3–4 | Tropical depression | Not specified | 1002 hPa (29.59 inHg) | South China, Vietnam | Unknown | None | |
| Mulan | August 8–11 | Tropical storm | 65 km/h (40 mph) | 994 hPa (29.35 inHg) | South China, Vietnam, Laos, Thailand, Myanmar | $1.43 million | 7 | [13][124][125][384] |
| Meari | August 8–14 | Tropical storm | 75 km/h (45 mph) | 996 hPa (29.41 inHg) | Japan | Unknown | None | |
| TD | August 14 | Tropical depression | Not specified | 1012 hPa (29.88 inHg) | None | None | None | |
| Ma-on (Florita) | August 20–26 | Severe tropical storm | 100 km/h (65 mph) | 985 hPa (29.09 inHg) | Philippines, South China, Vietnam | $46.2 million | 7 | [140][385][386] |
| Tokage | August 21–25 | Typhoon | 140 km/h (85 mph) | 970 hPa (28.64 inHg) | None | None | None | |
| TD | August 22 | Tropical depression | 55 km/h (35 mph) | 1008 hPa (29.77 inHg) | None | None | None | |
| Hinnamnor (Henry) | August 27 –September 6 | Violent typhoon | 195 km/h (120 mph) | 920 hPa (27.17 inHg) | Japan, Philippines, Taiwan, East China, South Korea, North Korea, Russian Far East | $1.81 billion | 20 | [174][387] |
| 13W (Gardo) | August 30 – September 1 | Tropical depression | 55 km/h (35 mph) | 998 hPa (29.47 inHg) | None | None | None | |
| Muifa (Inday) | September 3–15 | Very strong typhoon | 155 km/h (100 mph) | 950 hPa (28.05 inHg) | Philippines, Taiwan, Yaeyama Islands, East China | $437 million | 3 | |
| Merbok | September 10–15 | Typhoon | 130 km/h (80 mph) | 965 hPa (28.50 inHg) | None | None | None | |
| Nanmadol (Josie) | September 12–19 | Violent typhoon | 195 km/h (120 mph) | 910 hPa (26.87 inHg) | Japan, Korean Peninsula, Russian Far East | $1.2 billion | 4 | [227] |
| Talas | September 20–23 | Tropical storm | 65 km/h (40 mph) | 1000 hPa (29.53 inHg) | Japan | Unknown | 3 | [234] |
| Noru (Karding) | September 21–29 | Very strong typhoon | 175 km/h (110 mph) | 940 hPa (27.76 inHg) | Philippines, Vietnam, Laos, Thailand, Cambodia | $313 million | 40 | [388][389][390][13] |
| Kulap | September 25–29 | Severe tropical storm | 110 km/h (70 mph) | 965 hPa (28.50 inHg) | None | None | None | |
| TD | September 25–26 | Tropical depression | Not specified | 1012 hPa (29.88 inHg) | None | None | None | |
| Roke (Luis) | September 28 – October 1 | Typhoon | 130 km/h (80 mph) | 975 hPa (28.79 inHg) | Daitō Islands | None | None | |
| Maymay | October 11–12 | Tropical depression | Not specified | 1002 hPa (29.59 inHg) | Philippines | $9.16 million | 2 | [274][391] |
| 21W | October 12–14 | Tropical depression | 55 km/h (35 mph) | 1002 hPa (29.59 inHg) | None | None | None | |
| Sonca | October 13–15 | Tropical storm | 65 km/h (40 mph) | 998 hPa (29.47 inHg) | Vietnam, Laos, Cambodia | $102 million | 10 | [13][293][296][297] |
| Nesat (Neneng) | October 14–20 | Typhoon | 140 km/h (85 mph) | 965 hPa (28.50 inHg) | Philippines, Taiwan, South China, Vietnam, Cambodia, Laos | $16.7 million | None | [302][392][303] |
| Haitang | October 17–19 | Tropical storm | 65 km/h (40 mph) | 1004 hPa (29.65 inHg) | None | None | None | |
| 25W (Obet) | October 18–23 | Tropical depression | 55 km/h (35 mph) | 1006 hPa (29.71 inHg) | Philippines | Minimal | 2 | [393] |
| Nalgae (Paeng) | October 26 – November 3 | Severe tropical storm | 110 km/h (70 mph) | 975 hPa (28.79 inHg) | Philippines, Hong Kong, Macau, South China | $321 million | 160 | [394][395][396][397] |
| Banyan (Queenie) | October 28 – November 3 | Tropical storm | 75 km/h (45 mph) | 1002 hPa (29.59 inHg) | Caroline Islands, Palau, Mindanao | None | None | |
| Yamaneko | November 11–14 | Tropical storm | 65 km/h (40 mph) | 1004 hPa (29.65 inHg) | None | None | None | |
| Pakhar (Rosal) | December 10–12 | Tropical storm | 75 km/h (45 mph) | 998 hPa (29.47 inHg) | Philippines | None | 8 | [360] |
| Season aggregates | ||||||||
| 37 systems | January 27 – December 12, 2022 | 195 km/h (120 mph) | 910 hPa (26.87 inHg) | $5.07 billion | 498 | |||
Seamless Wikipedia browsing. On steroids.
Every time you click a link to Wikipedia, Wiktionary or Wikiquote in your browser's search results, it will show the modern Wikiwand interface.
Wikiwand extension is a five stars, simple, with minimum permission required to keep your browsing private, safe and transparent.
.jpg)
