2022 Pacific typhoon season

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. 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.

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. TSR remained constant with their prediction in their second forecast in July. 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.

{{clear}}

{{center|1=

ImageSize = width:1030 height:295

PlotArea = top:10 bottom:80 right:20 left:20

Legend = columns:3 left:30 top:58 columnwidth:270

AlignBars = early

DateFormat = dd/mm/yyyy

Period = from:01/01/2022 till:31/12/2022

TimeAxis = orientation:horizontal

ScaleMinor = grid:black unit:month increment:1 start:01/01/2022

Colors =

id:canvas value:gray(0.88)

id:GP value:red

id:TD value:rgb(0.43,0.76,0.92) legend:Tropical_Depression_=_≤62_km/h_(≤39_mph)

id:TS value:rgb(0.3,1,1) legend:Tropical_Storm_=_62–88_km/h_(39–54_mph)

id:ST value:rgb(0.75,1,0.75) legend:Severe_Tropical_Storm_=_89–117_km/h_(55–72_mph)

id:STY value:rgb(1,0.85,0.55) legend:Typhoon_=_118–156_km/h_(73–96_mph)

id:VSTY value:rgb(1,0.45,0.54) legend:Very_Strong_Typhoon_=_157–193_km/h_(97–119_mph)

id:VITY value:rgb(0.55,0.46,0.9) legend:Violent_Typhoon_=_≥194_km/h_(≥120_mph)

Backgroundcolors = canvas:canvas

BarData =

barset:Hurricane

bar:month

PlotData =

barset:Hurricane width:10 align:left fontsize:S shift:(4,-4) anchor:till

from:27/01/2022 till:28/01/2022 color:TD text:"TD"

from:29/03/2022 till:31/03/2022 color:TD text:"01W"

from:06/04/2022 till:15/04/2022 color:VSTY text:"Malakas"

from:08/04/2022 till:12/04/2022 color:TS text:"Megi"

from:30/05/2022 till:30/05/2022 color:TD text:"TD"

from:28/06/2022 till:05/07/2022 color:STY text:"Chaba"

from:30/06/2022 till:04/07/2022 color:TS text:"Aere"

from:24/07/2022 till:25/07/2022 color:TD text:"TD"

from:26/07/2022 till:01/08/2022 color:TS text:"Songda"

from:29/07/2022 till:01/08/2022 color:TS text:"Trases"

from:03/08/2022 till:04/08/2022 color:TD text:"08W"

from:08/08/2022 till:11/08/2022 color:TS text:"Mulan"

from:08/08/2022 till:14/08/2022 color:TS text:"Meari"

barset:break

from:14/08/2022 till:14/08/2022 color:TD text:"TD"

from:20/08/2022 till:26/08/2022 color:ST text:"Ma-on"

from:21/08/2022 till:25/08/2022 color:STY text:"Tokage"

from:22/08/2022 till:22/08/2022 color:TD text:"TD"

from:27/08/2022 till:06/09/2022 color:VITY text:"Hinnamnor"

from:30/08/2022 till:01/09/2022 color:TD text:"Gardo"

from:03/09/2022 till:15/09/2022 color:VSTY text:"Muifa"

from:10/09/2022 till:15/09/2022 color:STY text:"Merbok"

from:12/09/2022 till:19/09/2022 color:VITY text:"Nanmadol"

from:20/09/2022 till:23/09/2022 color:TS text:"Talas"

from:21/09/2022 till:29/09/2022 color:VSTY text:"Noru"

from:25/09/2022 till:29/09/2022 color:ST text:"Kulap"

from:25/09/2022 till:26/09/2022 color:TD text:"TD"

barset:break

from:28/09/2022 till:01/10/2022 color:STY text:"Roke"

from:11/10/2022 till:12/10/2022 color:TD text:"Maymay"

from:12/10/2022 till:14/10/2022 color:TD text:"21W"

from:13/10/2022 till:15/10/2022 color:TS text:"Sonca"

from:14/10/2022 till:20/10/2022 color:STY text:"Nesat"

from:17/10/2022 till:19/10/2022 color:TS text:"Haitang"

from:18/10/2022 till:23/10/2022 color:TD text:"Obet"

from:26/10/2022 till:03/11/2022 color:ST text:"Nalgae"

from:28/10/2022 till:03/11/2022 color:TS text:"Banyan"

from:11/11/2022 till:14/11/2022 color:TS text:"Yamaneko"

from:10/12/2022 till:12/12/2022 color:TS text:"Pakhar"

bar:Month width:5 align:center fontsize:S shift:(0,-20) anchor:middle color:canvas

from:01/01/2022 till:31/01/2022 text:January

from:01/02/2022 till:28/02/2022 text:February

from:01/03/2022 till:31/03/2022 text:March

from:01/04/2022 till:30/04/2022 text:April

from:01/05/2022 till:31/05/2022 text:May

from:01/06/2022 till:30/06/2022 text:June

from:01/07/2022 till:31/07/2022 text:July

from:01/08/2022 till:31/08/2022 text:August

from:01/09/2022 till:30/09/2022 text:September

from:01/10/2022 till:31/10/2022 text:October

from:01/11/2022 till:30/11/2022 text:November

from:01/12/2022 till:31/12/2022 text:December

}}

File:Malakas and Megi 2022-04-09 1700Z - 2022-04-10 0050Z.gif as Tropical Storm Megi nears the Visayas and later stalls in Leyte Gulf, bringing massive flooding and landslides to the Philippines.]]

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.

File:Chaba and Aere 2022-07-01 0810Z.jpg (left) continuing to intensify in the South China Sea, while Tropical Storm Aere (Domeng) (right) is moving north slowly across the Philippine Sea.]]

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.

File:Hinnamnor ISS067-E-302073 lrg.jpg on August 31.]]

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.

File:Muifa, Nanmadol, and Merbok 2022-09-13 2230Z.jpg

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.

File:2022 CIMSS 18W Noru visible infrared satellite loop.gif

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. With the storm's second landfall, the Sierra Madre mountain range helped it to weaken slightly as it moved westwards. 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.

{{Infobox hurricane small

|Basin=WPac

|Formed=March 29

|Dissipated=March 31

|Image=01W 2022-03-31 0040Z.jpg

|Track=01W 2022 track.png

|10-min winds=30

|1-min winds=35

|Prewinds=<

|Pressure=1006

}}

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.{{cite web |date=29 March 2022 |title=WWJP27 RJTD 291800 |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |url-status=deviated |archive-url=https://archive.today/20220330061757/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220329/180000/A_WWJP27RJTD291800_C_RJTD_20220329202446_94.txt |archive-date=30 March 2022 |access-date=30 March 2022 |publisher=Japan Meteorological Agency}} 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.{{Cite JTWC|date=March 29, 2021|type=tcfa|designation=93W|url=https://www.metoc.navy.mil/jtwc/products/wp9322web.txt|archive-url=https://web.archive.org/web/20210329000000/https://www.metoc.navy.mil/jtwc/products/wp9322web.txt|url-status=deviated |archive-date=March 29, 2021|access-date=March 30, 2021}} [https://wiki.chlod.net/jtwc/text/2022-03-29-2110-wp9322web.txt Alt URL] 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.{{Cite JTWC |date=2022-03-30 |type=warn |category=TD |designation=01W |no=1 |name=One|url=https://www.metoc.navy.mil/jtwc/products/wp0122web.txt|url-status=dead |archive-date=2022-03-30 |archive-url=https://archive.today/20220330153822/https://www.metoc.navy.mil/jtwc/products/wp0122web.txt}}

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.{{cite web |date=2022-04-04 |title=Thời tiết, thiên tai ngày càng dị thường |trans-title=Weather and natural disasters are becoming more and more unusual |url=https://thanhnien.vn/post-1445065.html |access-date=2022-04-14 |website=Báo Thanh Niên |language=vi}} Overall damages reach 3.52 trillion VND (US$148.95 million).[https://phongchongthientai.mard.gov.vn/FileUpload/2024-02/Ps2JMy-VHkuYMKZlThi%e1%bb%87t%20h%e1%ba%a1i%202022%20%c4%91%c4%83ng%20web.pdf 2022 Assessment Report, Vietnamese Disaster Management Department]

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.

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=April 6

|Dissipated=April 15

|Image=Malakas 2022-04-13 0405Z.jpg

|Track=Malakas 2022 track.png

|10-min winds=90

|1-min winds=105

|Pressure=945

}}

The JTWC first noted the existence of a tropical disturbance on April 3.{{Cite JTWC|date=2022-04-03|type=abpw|designation=95W|time=1830Z|url=https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|url-status=live|archive-date=2017-12-21|archive-url=https://web.archive.org/web/20171221082438/http://www.metoc.navy.mil/jtwc/products/abpwweb.txt}} [https://wiki.chlod.net/jtwc/text/2022-04-03-1850-abpwweb.txt Alt URL] Favorable conditions near the system helped it develop, with the JMA recognizing the system as a tropical depression on April 6.{{Cite report |url=https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220406/000000/A_WWJP27RJTD060000_C_RJTD_20220406022718_79.txt |title=WWJP27 RJTD 060000 |date=2022-04-06 |publisher=Japan Meteorological Agency |access-date=2022-04-08 |archive-url=https://archive.today/20220406112637/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220406/000000/A_WWJP27RJTD060000_C_RJTD_20220406022718_79.txt|archive-date=2022-04-06 |url-status=deviated}} Later in the day, the JTWC issued a TCFA for the system.{{Cite JTWC|date=2022-04-03|type=tcfa|designation=95W|url=https://www.metoc.navy.mil/jtwc/products/wp9522web.txt|url-status=dead|archive-date=2022-09-22|archive-url=https://web.archive.org/web/20220922013958/https://www.metoc.navy.mil/jtwc/products/wp9522web.txt}} [https://wiki.chlod.net/jtwc/text/2022-04-06-1500-wp9522web.txt Alt URL] The following day, the JTWC recognized the system as a tropical depression and gave it the designation 02W.{{Cite JTWC|date=2022-04-07|type=warn|category=TD|designation=02W|no=1|name=Two|url=https://www.metoc.navy.mil/jtwc/products/wp0222web.txt|url-status=dead|archive-date=2022-04-08|archive-url=https://web.archive.org/web/20220408060018/https://www.metoc.navy.mil/jtwc/products/wp0222web.txt}} [https://wiki.chlod.net/jtwc/text/2022-04-07-0220-wp0222web.txt Alt URL] At 21:00 UTC, the JTWC then upgraded it to a tropical storm.{{Cite JTWC|date=2022-04-07|type=warn|category=TS|designation=02W|no=4|name=Two|url=https://www.metoc.navy.mil/jtwc/products/wp0222web.txt|url-status=dead|archive-date=2023-08-28|archive-url=https://ghostarchive.org/archive/FnMEW}} On April 8, the system developed into a tropical storm and was named Malakas by the JMA.{{Cite report |url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq20.rjtd..txt |title=RSMC Tropical Cyclone Advisory on Tropical Storm 2201 (Malakas) |last=Japan Meteorological Agency |date=2022-04-08 |author-link=Japan Meteorological Agency |access-date=2022-04-08 |archive-url=https://archive.today/20220408015355/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq20.rjtd..txt |archive-date=April 8, 2022 |url-status=deviated }} 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.{{Cite report |url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt |title=RSMC Tropical Cyclone Advisory on Tropical Storm 2201 (Malakas) |last=Japan Meteorological Agency |date=2022-04-10 |author-link=Japan Meteorological Agency |access-date=2022-04-14 |archive-url=https://archive.today/20220410153227/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt |archive-date=2022-04-10 |url-status=deviated }}{{Cite report |url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt |title=RSMC Tropical Cyclone Advisory on Tropical Storm 2201 (Malakas) |last=Japan Meteorological Agency |date=2022-04-12 |author-link=Japan Meteorological Agency |access-date=2022-04-14 |archive-url=https://archive.today/20220412023750/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt |archive-date=2022-04-12 |url-status=deviated }} 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.{{Cite PAGASA|date=April 12, 2022|name=Basyang|intl-name=Malakas|type=tcb|no=1|category=TY|url=https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin/TCB%231_basyang.pdf}}{{dead link|date=August 2023|bot=medic}}{{cbignore|bot=medic}} [https://archive.org/download/pagasa-22-TC02/PAGASA_22-TC02_Basyang_TCB%2301.pdf Alt URL] Malakas then lingered for a while at the border of the PAR before eventually exiting 5 hours later,{{Cite PAGASA|date=April 12, 2022|name=Basyang|intl-name=Malakas|type=tcb|no=2F|category=TY|url=https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin/TCB%232F_basyang.pdf}}{{dead link|date=August 2023|bot=medic}}{{cbignore|bot=medic}} [https://archive.org/download/pagasa-22-TC02/PAGASA_22-TC02_Basyang_TCB%2302-FINAL.pdf Alt URL] 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 {{cvt|130|mph|km/h|order=flip}} 1-minute sustained winds on April 13, reaching its peak intensity. The following day, Malakas weakened to a Category 3-equivalent typhoon{{cite web |title=bwp022022.dat |url=https://www.ssd.noaa.gov/PS/TROP/DATA/ATCF/JTWC/bwp022022.dat |access-date=June 28, 2022 |publisher=Joint Typhoon Warning Center |via=National Oceanic and Atmospheric Administration}} as its eye structure degraded.{{Cite JTWC|date=April 13, 2022|type=prog|category=TY|designation=02W|no=28|name=Malakas|url=https://tgftp.nws.noaa.gov/data/raw/wd/wdpn31.pgtw..txt|archive-url=https://archive.today/20220414021835/https://tgftp.nws.noaa.gov/data/raw/wd/wdpn31.pgtw..txt|archive-date=April 14, 2022|access-date=June 28, 2022}} It further weakened to Category 1-equivalent status later in the day. 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,{{Cite jtwc|date=April 15, 2022|type=warn|category=TS|designation=02W|no=34|name=Malakas|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpn31.pgtw..txt|archive-url=https://archive.today/20220415093925/https://tgftp.nws.noaa.gov/data/raw/wt/wtpn31.pgtw..txt|archive-date=April 15, 2022|access-date=June 28, 2022}} while the JMA did the same around 18:00 UTC.{{cite web |date=April 15, 2022 |title=RSMC Tropical Cyclone Advisory on Developing Low Former STS 2201 Malakas (2201) |url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt |archive-url=https://archive.today/20220416094645/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt |archive-date=April 16, 2022 |access-date=June 28, 2022 |publisher=Japan Meteorological Agency |via=National Oceanic and Atmospheric Administration}}

Although Malakas did not affect any major land areas, due to its name being nearly homophonous to a vulgar Greek slang term ({{lang|el|μαλάκας}} means "wanker"), the name Malakas was retired and will never be used again for a Pacific typhoon name.{{Cite web |date=2024-02-16 |title=Replacement of Typhoon Names |url=https://www.typhooncommittee.org/56th/docs/item%2013/13.1%20Replacement%20of%20Typhoon%20Names%20-%20feb%2016.pdf |website=ESCAP/WMO Typhoon Committee - 56th Session |publisher=ESCAP/WMO Typhoon Committee}} In 2024, it was the first announced to replaced with Amuyao (a mountain in Mountain Province) for future seasons, but it will subsequently replaced for Aghon in Philippine local names by 2028 season.{{Cite web |title=Report of the Fifty-Sixth Session of Typhoon Committee |url=https://www.typhooncommittee.org/56th/docs/final/TC56_FINAL.pdf |website=ESCAP/WMO Typhoon Committee - 56th Session |publisher=ESCAP/WMO Typhoon Committee |publication-date=2024-03-01}} In 2025, the name was changed to Amuyag, which is a Cordilleran word for "to scatter" or "to spread out".

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=April 8

|Dissipated=April 12

|Image=Megi 2022-04-10 0225Z.jpg

|Track=Megi 2022 track.png

|10-min winds=40

|1-min winds=40

|Pressure=996

}}{{main|Tropical Storm Megi}}

On April 8, the JTWC noted an area of convection persisting around {{convert|359|nmi|km mi}} west-northwest of Palau.{{Cite JTWC|date=2022-04-03|type=abpw|designation=94W|time=0330Z|url=https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|url-status=live|archive-date=2017-12-21|archive-url=https://web.archive.org/web/20171221082438/http://www.metoc.navy.mil/jtwc/products/abpwweb.txt}} [https://wiki.chlod.net/jtwc/text/2022-04-08-0340-abpwweb.txt Alt URL] 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.{{Cite report |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |title=WWJP27 RJTD 081800 |last=Japan Meteorological Agency |date=2022-04-08 |author-link=Japan Meteorological Agency |access-date=2022-04-08 |archive-url=https://archive.today/20220408210901/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-date=April 8, 2022 |url-status=deviated }} 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.{{cite tweet |author=PAGASA-DOST |user=dost_pagasa |number=1512513418808291330 |date=April 8, 2022 |title=At 2:00 AM today, the Low Pressure Area east of Visayas developed into Tropical Depression #AgatonPH. Tropical Cyclone Bulletins will be issued starting at 5AM today. https://t.co/ThQu9J5YrH |language=en |access-date=January 14, 2023 |archive-url=https://web.archive.org/web/20221129113337/https://twitter.com/dost_pagasa/status/1512513418808291330 |archive-date=November 29, 2022 |url-status=live}} PAGASA would begin issuing Tropical Cyclone Bulletins (TCBs) for the storm later that day.{{Cite PAGASA|date=2022-04-08|name=Agaton|type=tcb|no=1|category=TD|url=https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin_agaton.pdf|url-status=live|archive-date=2022-04-08|archive-url=https://web.archive.org/web/20220408230335/https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin_agaton.pdf}} [https://archive.org/download/pagasa-22-TC01/PAGASA_22-TC01_Agaton_TCB%2301.pdf Alt URL] On the next day, the JTWC later issued a TCFA for the system.{{Cite JTWC|date=April 9, 2022 |type=tcfa |designation=94W |title=Foobar1 |url=https://www.metoc.navy.mil/jtwc/products/wp9422web.txt |url-status=dead |archive-date=2022-09-21 |archive-url=https://web.archive.org/web/20220921020721/https://www.metoc.navy.mil/jtwc/products/wp9422web.txt}} [https://wiki.chlod.net/jtwc/text/2022-04-09-0210-wp9422web.txt Alt URL] At 03:00 UTC, the agency upgraded it to a tropical depression and assigned it the identifier 03W.{{Cite JTWC|date=2022-04-09|type=warn|category=TD|designation=03W|no=1|name=Three|url=https://www.metoc.navy.mil/jtwc/products/wp0322web.txt|url-status=dead|archive-date=2022-04-10|archive-url=https://web.archive.org/web/20220410073338/https://www.metoc.navy.mil/jtwc/products/wp0322web.txt}} [https://wiki.chlod.net/jtwc/text/2022-04-09-0350-wp0322web.txt Alt URL] On April 10, the JMA upgraded it to a tropical storm, naming it Megi.{{cite web |date=April 10, 2022 |title=RSMC Tropical Cyclone Advisory Name TS 2202 Megi (2202) Upgraded from TD |url=https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Tropical_cyclone/20220410/000000/A_WTPQ51RJTD100000_C_RJTD_20220410012116_15.txt |archive-url=https://archive.today/20220410083103/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Tropical_cyclone/20220410/000000/A_WTPQ51RJTD100000_C_RJTD_20220410012116_15.txt |archive-date=April 10, 2022 |access-date=April 10, 2022 |publisher=Japan Meteorological Agency}} Megi would make its first landfall in Calicoan Island, Guiuan at 07:30 PHT (23:30 UTC).{{cite web |date=2022-04-10 |title='Agaton' slightly weakens; to make landfall over Leyte's eastern coast, says PAGASA |url=https://news.abs-cbn.com/news/04/11/22/pagasa-agaton-weakens-to-make-landfall-over-leytes-eastern-coast |archive-url=https://archive.today/20220411021848/https://news.abs-cbn.com/news/04/11/22/pagasa-agaton-weakens-to-make-landfall-over-leytes-eastern-coast |archive-date=April 11, 2022 |access-date=2022-04-10 |publisher=ABS-CBN News |url-status=live }} Megi then stalled in the Leyte Gulf for hours before making its second landfall in Basey, Samar.{{cite tweet |author=PAGASA-DOST |user=dost_pagasa |number=1513443939512045568 |date=April 11, 2022 |title=At 4:00 PM today, Tropical Depression "AGATON" made landfall over Basey, Samar. #AgatonPH |language=en |access-date=January 14, 2023 |archive-url=https://web.archive.org/web/20220918073912/https://twitter.com/dost_pagasa/status/1513443939512045568 |archive-date=September 18, 2022 |url-status=live}}

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.{{cite news |last=Sarao |first=Zacarian |date=2022-04-13 |title=Agaton weakens into LPA but will still cause heavy rainfall |url=https://newsinfo.inquirer.net/1582222/agaton-weakens-into-low-pressure-area-to-continue-bringing-heavy-rainfall-pagasa |access-date=2022-04-13 |newspaper=Philippine Daily Inquirer |language=en |archive-date=April 13, 2022 |archive-url=https://web.archive.org/web/20220413032431/https://newsinfo.inquirer.net/1582222/agaton-weakens-into-low-pressure-area-to-continue-bringing-heavy-rainfall-pagasa |url-status=live }}

From April 8 to April 10, the storm meandered along the Eastern Visayas region, dumping heavy rain on the region.{{cite web |last=Arceo |first=Acor |date=2022-04-10 |title=Tropical Storm Agaton slightly weakens before looming second landfall |url=https://www.rappler.com/nation/weather/tropical-storm-agaton-malakas-pagasa-forecast-april-10-2022-11pm/ |archive-url=https://archive.today/20220411020514/https://www.rappler.com/nation/weather/tropical-storm-agaton-malakas-pagasa-forecast-april-10-2022-11pm/ |archive-date=2022-04-11 |access-date=2022-04-10 |website=Rappler |language=en-PH|url-status=live}} PAGASA raised storm signals up to Signal No. 2 during the storm's onslaught.{{Cite PAGASA|date=2022-04-10|name=Agaton|type=tcb|no=9|category=TS|url=https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin/TCB%239_agaton.pdf}}{{dead link|date=August 2023|bot=medic}}{{cbignore|bot=medic}} [https://archive.org/download/pagasa-22-TC01/PAGASA_22-TC01_Agaton_TCB%2309.pdf Alt URL]{{cite web |title=Signal No. 2 up over parts of Eastern Samar, 3 other areas due to Agaton |url=https://www.gmanetwork.com/news/scitech/weather/828115/signal-no-2-up-over-parts-of-eastern-samar-3-other-areas-due-to-agaton/story/ |archive-url=https://ghostarchive.org/archive/20220411020432/https://www.gmanetwork.com/news/scitech/weather/828115/signal-no-2-up-over-parts-of-eastern-samar-3-other-areas-due-to-agaton/story/ |archive-date=April 11, 2022 |access-date=2022-04-10 |website=GMA News Online |language=en |url-status=live }} Cebu City was placed under a state of calamity following the heavy rain.{{cite web |last=Israel |first=Dale |date=2022-04-10 |title=Cebu City placed under state of calamity due to Agaton |url=https://www.cnnphilippines.com/regional/2022/4/10/Cebu-City-state-of-calamity.html |access-date=2022-04-10 |publisher=CNN Philippines |archive-date=April 10, 2022 |archive-url=https://web.archive.org/web/20220410130829/https://www.cnnphilippines.com/regional/2022/4/10/Cebu-City-state-of-calamity.html |url-status=dead }} Megi killed 214 people, which made it the deadliest tropical cyclone in the Philippines to form in May.{{cite news |last1=Alota |first1=Bobbie |last2=Morella |first2=Cecil |date=April 14, 2022 |title='Agaton' death toll from landslides, floods hits 148: official tallies |url=https://news.abs-cbn.com/news/04/14/22/agaton-death-toll-hits-148-official-tallies |access-date=April 14, 2022 |archive-url=https://archive.today/20220414145215/https://news.abs-cbn.com/news/04/14/22/agaton-death-toll-hits-148-official-tallies |archive-date=April 14, 2022 |website=ABS-CBN News |url-status=live }} Megi would also injure eight people, leave 134 people missing,{{cite web |last=Abania |first=Lolet |date=2022-04-11 |title=3 patay, 1 nawawala, 2 nasaktan dahil sa Bagyong Agaton — NDRRMC |trans-title=3 dead, 1 missing, 2 injured due to Typhoon Agaton - NDRRMC |url=https://www.bulgaronline.com/post/3-patay-1-nawawala-2-nasaktan-dahil-sa-bagyong-agaton-ndrrmc |access-date=2022-04-11 |website=Bulgar Online |language=tl |archive-url=https://web.archive.org/web/20220411132702/https://www.bulgaronline.com/amp/3-patay-1-nawawala-2-nasaktan-dahil-sa-bagyong-agaton-ndrrmc |archive-date=April 11, 2022 |url-status=live }} and capsize a cargo boat in Ormoc following strong rains, winds, and flash floods which also displaced over 136,390 individuals.{{cite news |last=Gabieta |first=Joey |date=2022-04-10 |title=Cargo vessel capsizes off Ormoc City amid 'Agaton' onslaught |url=https://newsinfo.inquirer.net/1581147/cargo-vessel-capsizes-off-ormoc-city-amid-agaton-onslaught |access-date=2022-04-10 |newspaper=Philippine Daily Inquirer |language=en |archive-date=April 10, 2022 |archive-url=https://web.archive.org/web/20220410103614/https://newsinfo.inquirer.net/1581147/cargo-vessel-capsizes-off-ormoc-city-amid-agaton-onslaught |url-status=live }} The Department of Agriculture estimated agricultural damage to reach ₱3.27 billion,{{cite news |last=Sarao |first=Zacarian |date=2022-04-25 |title='Agaton' agricultural damage, losses jump to P3.27B |url=https://newsinfo.inquirer.net/1587829/agaton-agricultural-damage-losses-jump-to-p3-27b |access-date=2022-04-26 |newspaper=Philippine Daily Inquirer |language=en |archive-date=April 25, 2022 |archive-url=https://web.archive.org/web/20220425153943/https://newsinfo.inquirer.net/1587829/agaton-agricultural-damage-losses-jump-to-p3-27b |url-status=live }} 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).{{cite news |last=Gonzales |first=Cathrine |date=2022-04-20 |title=DPWH says Agaton left P1.45B in infrastructure damage |url=https://newsinfo.inquirer.net/1585731/fwd-damage-of-agaton-to-infrastructure-reaches-p1-45-b |access-date=2022-04-21 |newspaper=Philippine Daily Inquirer |language=en |archive-date=April 21, 2022 |archive-url=https://web.archive.org/web/20220421042905/https://newsinfo.inquirer.net/1585731/fwd-damage-of-agaton-to-infrastructure-reaches-p1-45-b |url-status=live }}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=June 28

|Dissipated=July 5

|Image=Chaba 2022-07-02 0000Z.jpg

|Track=Chaba 2022 track.png

|10-min winds=70

|1-min winds=75

|Pressure=965

}}

{{main|Typhoon Chaba (2022)}}

A low-pressure area west of Luzon developed into a tropical depression on June 28.{{cite web |title=WWJP27 RJTD 280600 |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |publisher=Japan Meteorological Agency |access-date=28 June 2022 |archive-url=https://archive.today/20220628143452/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220628/060000/A_WWJP27RJTD280600_C_RJTD_20220628082517_38.txt |archive-date=28 June 2022 |date=28 June 2022}}{{cite web |title=WWJP27 RJTD 281200 |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |publisher=Japan Meteorological Agency |access-date=28 June 2022 |archive-url=https://archive.today/20220628143406/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-date=28 June 2022 |date=28 June 2022}} 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.{{Cite PAGASA|date=June 29, 2022|name=Caloy|type=TCB|no=1|category=TD|url=https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin/TCB%231_caloy.pdf|archive-url=https://web.archive.org/web/20220629000000/https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin/TCB%231_caloy.pdf|archive-date=June 29, 2022}} [https://archive.org/download/pagasa-22-TC03/PAGASA_22-TC03_Caloy_TCB%2301.pdf Alt URL] The following day, the JTWC issued a TCFA for the system.{{Cite JTWC|date=June 29, 2022|type=tcfa|designation=97W|url=https://www.metoc.navy.mil/jtwc/products/wp9722web.txt|url-status=dead|archive-date=June 29, 2022|archive-url=https://web.archive.org/web/20220629024509/https://www.metoc.navy.mil/jtwc/products/wp9722web.txt}} Caloy remained almost stationary in the South China Sea before slowly moving northwestwards, eventually leaving the Philippine Area of Responsibility by 15:00 UTC.{{cite web |title=WTPQ50 RJTD 290600 |url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt#selection-9.85-9.97 |publisher=Japan Meteorological Agency |access-date=30 June 2022 |archive-url=https://archive.today/20220629083004/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt#selection-9.85-9.97 |archive-date=29 June 2022 |date=29 June 2022}}{{Cite PAGASA|date=June 29, 2022|name=Caloy|type=TCB|no=3|category=TD|url=https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin/TCB%233_caloy.pdf|archive-url=https://web.archive.org/web/20220629000000/https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin/TCB%233_caloy.pdf|archive-date=June 29, 2022}} [https://archive.org/download/pagasa-22-TC03/PAGASA_22-TC03_Caloy_TCB%2303.pdf Alt URL] 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.{{Cite PAGASA|date=June 29, 2022|name=Caloy|type=TCB|no=6-FINAL|category=TD|url=https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin/TCB%236_caloy.pdf|archive-url=https://web.archive.org/web/20220629000000/https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin/TCB%236_caloy.pdf|archive-date=June 29, 2022}} [https://archive.org/download/pagasa-22-TC03/PAGASA_22-TC03_Caloy_TCB%2306-FINAL.pdf Alt URL]{{Cite JTWC|date=June 29, 2022|type=prog|category=TD|designation=04W|no=1|name=Four|time=21Z|url=https://www.metoc.navy.mil/jtwc/products/wp0422prog.txt|url-status=dead|archive-date=2022-06-29|archive-url=https://web.archive.org/web/20220629223651/https://www.metoc.navy.mil/jtwc/products/wp0422prog.txt}} [https://wiki.chlod.net/jtwc/prog/2022-06-29-2100-wp0422prog.txt Alt URL] Later, the Japan Meteorological Agency upgraded Caloy into a tropical storm, naming it Chaba.{{cite web |date=2022-06-30 |title=WTPQ50 RJTD 300000 |url=https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Tropical_cyclone/20220630/000000/A_WTPQ20RJTD300000_C_RJTD_20220630012816_15.txt |archive-url=https://archive.today/20220630020919/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt |archive-date=2022-06-30 |access-date=2022-06-30 |publisher=Japan Meteorological Agency}} Chaba continued to intensify in the South China Sea, later being upgraded into a severe tropical storm northeast of the Paracel Islands.{{cite web |date=June 30, 2022 |title=RSMC Tropical Cyclone Advisory Name STS 2203 Chaba (2203) Upgraded from TS |url=https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Tropical_cyclone/20220630/180000/A_WTPQ50RJTD301800_C_RJTD_20220630184130_3.txt |archive-url=https://archive.today/20220701015429/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Tropical_cyclone/20220630/180000/A_WTPQ50RJTD301800_C_RJTD_20220630184130_3.txt |archive-date=July 1, 2022 |access-date=July 2, 2022 |publisher=Japan Meteorological Agency}} Typhoon Chaba's outer rainbands produced at least three tornadoes, which impacted Shantou, Chaozhou, and Foshan.{{cite tweet |author=ChinaWXnerds (中国气象爱好者) |user=FansOfStorms |number=1542599467148484608 |date=June 30, 2022 |title=Another urban tornado just occurred in #Foshan, China within the outer rainbands of Tropical Storm #Chaba. The city of #Foshan is prone to tornadoes and interestingly, an analog Typhoon #Prapiroon (2006) also dropped a tornado nearby. https://t.co/bo2HoZwE8I |language=en |access-date=December 26, 2022 |archive-url=https://web.archive.org/web/20221018054012/https://twitter.com/FansOfStorms/status/1542599467148484608 |archive-date=October 18, 2022 |url-status=live}}{{cite tweet |author=ChinaWXnerds (中国气象爱好者) |user=FansOfStorms |number=1543082986647732228 |date=July 2, 2022 |title=More tornadoes reported from the outer rainbands of Typhoon #Chaba. This video is taken in #Chaozhou, over 300 miles away from the storm center, reminding us how widespread these typhoon-related hazards can be! (witness: @LCLCLKLZ on Weibo) https://t.co/4dCWW2vH8q |language=en |access-date=December 26, 2022 |archive-url=https://web.archive.org/web/20221011212535/https://twitter.com/FansOfStorms/status/1543082986647732228 |archive-date=October 11, 2022 |url-status=live}}{{cite tweet |author=ChinaWXnerds (中国气象爱好者) |user=FansOfStorms |number=1543084822502973440 |date=July 2, 2022 |title=Another one! Waterspout moving onshore in #Shantou, within the outer rainbands of Typhoon #Chaba, well over 300 miles away from the storm center! https://t.co/LfdKktdsuL |language=en |access-date=December 26, 2022 |archive-url=https://web.archive.org/web/20221018053908/https://twitter.com/FansOfStorms/status/1543084822502973440 |archive-date=October 18, 2022 |url-status=live}} On July 1 at 21:00 UTC, the JTWC upgraded Chaba to a typhoon,{{Cite JTWC|date=July 1, 2022|type=warn|category=TY|designation=04W|no=9|name=Chaba|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpn32.pgtw..txt|archive-url=https://archive.today/20220702020456/https://tgftp.nws.noaa.gov/data/raw/wt/wtpn32.pgtw..txt|archive-date=July 2, 2022|access-date=July 2, 2022}} with the JMA doing the same 3 hours later on July 2 at 0:00 UTC.{{cite web |date=July 2, 2022 |title=RSMC Tropical Cyclone Advisory Name TY 2203 Chaba (2203) Upgraded from STS |url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt |archive-url=https://archive.today/20220702020533/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt |archive-date=July 2, 2022 |access-date=July 2, 2022 |publisher=Japan Meteorological Agency |via=National Oceanic and Atmospheric Administration}} Later that day at 07:00 UTC, it made landfall on Maoming.{{Cite news |date=July 2, 2022 |title=Typhoon Chaba makes landfall in China's Guangdong |publisher=Xinhua News Agency |url=http://www.chinaview.cn/20220702/d226025ff7ed4fc2811318c8bb1319cf/c.html |access-date=July 2, 2022}} 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.{{cite web |date=July 2, 2022 |title=RSMC Tropical Cyclone Advisory Name STS 2203 Chaba (2203) Downgraded from TY |url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt |archive-url=https://archive.today/20220702144043/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt |archive-date=July 2, 2022 |access-date=July 2, 2022 |publisher=Japan Meteorological Agency}}{{Cite JTWC|date=July 2, 2022|type=warn|category=TS|designation=04W|no=12|name=Chaba|url=https://www.metoc.navy.mil/jtwc/products/wp0422web.txt|archive-url=https://archive.today/20220702144201/https://www.metoc.navy.mil/jtwc/products/wp0422web.txt|archive-date=July 2, 2022|access-date=July 2, 2022}} The JTWC then issued their final warning on Chaba at 15:00 UTC.{{Cite jtwc|date=July 2, 2022|type=warn|category=TS|designation=04W|no=12|name=Chaba|url=https://www.metoc.navy.mil/jtwc/products/wp0422web.txt|archive-url=https://archive.today/20220702144201/https://www.metoc.navy.mil/jtwc/products/wp0422web.txt|archive-date=July 2, 2022|access-date=July 3, 2022}} Shortly after, the JMA downgraded Chaba to a tropical storm;{{cite web |date=July 2, 2022 |title=RSMC Tropical Cyclone Advisory Name TS 2203 Chaba (2203) Downgraded from STS |url=https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Tropical_cyclone/20220702/180000/A_WTPQ20RJTD021800_C_RJTD_20220702190917_28.txt |url-status=live |archive-url=https://web.archive.org/web/20220703073811/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Tropical_cyclone/20220702/180000/A_WTPQ20RJTD021800_C_RJTD_20220702190917_28.txt |archive-date=July 3, 2022 |access-date=July 3, 2022 |publisher=Japan Meteorological Agency}} it was further downgraded to a tropical depression on July 3 at 06:00 UTC.{{cite web |date=July 3, 2022 |title=RSMC Tropical Cyclone Advisory Name TD Downgraded from TS 2203 Chaba (2203) |url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt |url-status=live |archive-url=https://web.archive.org/web/20220703073318/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt |archive-date=July 3, 2022 |access-date=July 3, 2022 |publisher=Japan Meteorological Agency}}

{{convert|160|nmi|km 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.{{Cite news |date=July 2, 2022 |title=Dozens missing in shipwreck off Hong Kong during South China Sea typhoon |publisher=Channel NewsAsia |url=https://www.channelnewsasia.com/asia/hong-kong-shipwreck-south-china-sea-typhoon-chaba-2786556 |access-date=July 2, 2022}}{{Citation needed|date=September 2023}}{{Cite news |date=July 4, 2022 |title=China retrieves dozen bodies after Typhoon Chaba sinks ship |publisher=Reuters |url=https://www.reuters.com/world/china/china-retrieves-dozen-bodies-after-typhoon-chaba-sinks-ship-2022-07-04/ |access-date=July 4, 2022}} Three of the 30 crew members were rescued, seen in a video published online by the Hong Kong Government Flying Service.{{Cite news |date=2 July 2022 |title=Dramatic video shows crew member's rescue from sinking ship near Hong Kong |publisher=Canadian Broadcasting Corporation |url=https://www.cbc.ca/news/world/dramatic-video-shows-crew-member-s-rescue-from-sinking-ship-near-hong-kong-1.6508729?cmp=rss}} Another person was rescued by July 4, bringing the total number of people rescued to four. Twelve bodies from the ship were recovered. More than 400 flights were suspended in Hainan; one person was injured in Macau.{{Cite news |last1=Yan |first1=Zhang |last2=Woo |first2=Ryan |date=July 2, 2022 |title=China lashed by year's first typhoon, record rains forecast |publisher=Reuters |editor-last=Mallard |editor-first=William |url=https://www.reuters.com/world/china/china-lashed-by-years-first-typhoon-record-rains-forecast-2022-07-02/ |access-date=July 2, 2022}}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=June 30

|Dissipated=July 4

|Image=Aere 2022-07-02 0405Z.jpg

|Track=Aere 2022 track.png

|10-min winds=45

|1-min winds=45

|Pressure=994

}}

On June 30, the JTWC began issuing TCFAs for a tropical disturbance in the Philippine Sea, {{convert|530|nmi|km mi}} south-southeast of Kadena Air Base in Japan.{{Cite JTWC|date=2022-06-30|type=tcfa|designation=98W|time=06Z|url=https://www.metoc.navy.mil/jtwc/products/wp9822web.txt|url-status=dead|archive-date=2022-08-30|archive-url=https://web.archive.org/web/20220830074531/https://www.metoc.navy.mil/jtwc/products/wp9822web.txt}} [https://wiki.chlod.net/jtwc/text/2022-06-30-0650-wp9822web.txt Alt URL] 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.{{Cite PAGASA|date=2022-06-30|name=Domeng|type=tcb|no=1|category=TD|url=https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin/TCB%231_domeng.pdf}}{{dead link|date=August 2023|bot=medic}}{{cbignore|bot=medic}} [https://archive.org/download/pagasa-22-TC04/PAGASA_22-TC04_Domeng_TCB%2301.pdf Alt URL] The JMA recognized the storm as a tropical depression at 12:00 UTC on the same day;{{cite web |date=June 30, 2022 |title=WWJP27 RTJD 301200 |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |url-status=deviated |archive-url=https://archive.today/20220630142304/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-date=June 30, 2022 |access-date=June 30, 2022 |publisher=Japan Meteorological Agency}} the JTWC followed shortly after.{{Cite JTWC|date=June 30, 2022|type=warn|category=TD|designation=05W|no=1|name=Five|time=15Z|url=https://www.metoc.navy.mil/jtwc/products/wp0522web.txt|url-status=dead|archive-date=2022-06-30|archive-url=https://web.archive.org/web/20220630144024/https://www.metoc.navy.mil/jtwc/products/wp0522web.txt}} [https://wiki.chlod.net/jtwc/text/2022-06-30-1420-wp0522web.txt Alt URL] On the next day, the Japan Meteorological Agency upgraded Domeng into a tropical storm and named it Aere as it was east of Batanes.{{cite web |date=July 1, 2022 |title=Tropical Cyclone Information |url=https://www.data.jma.go.jp/multi/cyclone/cyclone_detail.html?id=61&lang=en |url-status=deviated |archive-url=https://web.archive.org/web/20220701015447/https://www.data.jma.go.jp/multi/cyclone/cyclone_detail.html?id=61&lang=en |archive-date=July 1, 2022 |access-date=July 1, 2022 |publisher=Japan Meteorological Agency}} 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.{{Cite PAGASA|date=2022-07-02|name=Domeng|intl-name=Aere|type=tcb|no=8F|category=TS|url=https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin/TCB%238F_domeng.pdf}}{{dead link|date=August 2023|bot=medic}}{{cbignore|bot=medic}} [https://archive.org/download/pagasa-22-TC04/PAGASA_22-TC04_Domeng_TCB%2308-FINAL.pdf Alt URL] Later that day, Aere made landfall over Okinawa.{{Cite news |date=July 2, 2022 |title=Japan: Tropical Storm Aere making landfall over northern Okinawa late July 2 |work=Crisis24 |url=https://crisis24.garda.com/alerts/2022/07/japan-tropical-storm-aere-making-landfall-over-northern-okinawa-late-july-2 |access-date=July 4, 2022}} On July 3 at 09:00 UTC, the JTWC downgraded Aere to a tropical depression.{{Cite jtwc|date=July 3, 2022|type=warn|category=TD|designation=05W|no=12|name=Aere|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpn31.pgtw..txt|archive-url=https://archive.today/20220703084058/https://tgftp.nws.noaa.gov/data/raw/wt/wtpn31.pgtw..txt|archive-date=July 3, 2022|access-date=July 4, 2022|language=en}} However, three days later, the JTWC released another unofficial bulletin, reclassifying this disturbance as a subtropical storm, with an estimated pressure of 1000 hPa.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|archive-url=https://ghostarchive.org/archive/WFsZ6|title=Tropical Storm 05W (Aere) Warning #26 Final Warning Issued at 06/2100Z|website=JTWC|date=July 6, 2022|access-date=July 7, 2022|archive-date=July 7, 2022|language=en}}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=July 26

|Dissipated=August 1

|Image=Songda 2022-07-29 0400Z.jpg

|Track=Songda 2022 track.png

|10-min winds=40

|1-min winds=30

|Pressure=996

}}

On July 26, a low-pressure area northwest of the Mariana Islands developed into a tropical depression.{{cite web|title=WWJP27 RJTD 260600|url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|publisher=Japan Meteorological Agency|access-date=26 July 2022|archive-url=https://archive.today/20220726133330/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|archive-date=26 July 2022}}{{cite web|title=WTPQ50 RJTD 261200|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt|publisher=Japan Meteorological Agency|access-date=26 July 2022|archive-url=https://archive.today/20220726133332/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt|archive-date=26 July 2022}} The system tracked northwest along the periphery of a subtropical high, with limited intensification.{{cite web|title=WTPQ30 RJTD 270000|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq30.rjtd..txt|publisher=Japan Meteorological Agency|access-date=27 July 2022|archive-url=https://archive.today/20220727021216/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq30.rjtd..txt|archive-date=27 July 2022}}{{cite web|title=WTPQ30 RJTD 280000|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq30.rjtd..txt|publisher=Japan Meteorological Agency|access-date=28 July 2022|archive-url=https://archive.today/20220728021837/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq30.rjtd..txt|archive-date=28 July 2022}} 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.{{cite web|title=WTPQ30 RJTD 281200|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq30.rjtd..txt|publisher=Japan Meteorological Agency|access-date=28 July 2022|archive-url=https://archive.today/20220728141858/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq30.rjtd..txt#selection-9.0-9.18|archive-date=28 July 2022}} The JTWC recognized the system's formation into a tropical depression on July 29, three days after the JMA.{{Cite JTWC|date=July 29, 2022|type=prog|category=TD|designation=06W|no=1|name=Songda|time=03Z|url=https://www.metoc.navy.mil/jtwc/products/wp0622prog.txt|url-status=dead|archive-date=2022-07-29|archive-url=https://web.archive.org/web/20220729081804/https://www.metoc.navy.mil/jtwc/products/wp0622prog.txt}} [https://wiki.chlod.net/jtwc/prog/2022-07-29-0250-wp0622prog.txt Alt URL] Songda continued tracking northwestwards, passing over the waters of Kagoshima Prefecture on July 30, slowing down over the Yellow Sea.{{cite web|title=WTPQ30 RJTD 280000|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq30.rjtd..txt|publisher=Japan Meteorological Agency|access-date=31 July 2022|archive-url=https://archive.today/20220728021837/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq30.rjtd..txt|archive-date=28 July 2022}} It then recurved towards mainland Korea, losing its strength as it entered unfavorable conditions which sheared its center.{{Cite JTWC|date=July 31, 2022|type=prog|category=TD|designation=06W|no=10|name=Songda|time=09Z|url=https://www.metoc.navy.mil/jtwc/products/wp0622prog.txt|url-status=dead|archive-date=2022-07-29|archive-url=https://web.archive.org/web/20220729081804/https://www.metoc.navy.mil/jtwc/products/wp0622prog.txt}} [https://wiki.chlod.net/jtwc/prog/2022-07-31-0830-wp0622prog.txt Alt URL]{{Cite JTWC|date=July 31, 2022|type=prog|category=TD|designation=06W|no=12|name=Songda|time=09Z|url=https://www.metoc.navy.mil/jtwc/products/wp0622prog.txt|url-status=dead|archive-date=2022-07-29|archive-url=https://web.archive.org/web/20220729081804/https://www.metoc.navy.mil/jtwc/products/wp0622prog.txt}} [https://wiki.chlod.net/jtwc/prog/2022-07-31-2010-wp0622prog.txt Alt URL] Songda dissipated on August 1; its remnants made landfall over North Korea on August 2.{{cite web|title=WWJP27 RJTD 011200|url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|publisher=Japan Meteorological Agency|access-date=31 July 2022|archive-url=https://archive.today/20220801084356/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|archive-date=August 1, 2022}}{{cite web|title=WWJP27 RJTD 011200

|url=https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220801/120000/A_WWJP27RJTD011200_C_RJTD_20220801142817_47.txt|publisher=Japan Meteorological Agency|access-date=31 July 2022|archive-url=https://archive.today/20220802021216/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220801/120000/A_WWJP27RJTD011200_C_RJTD_20220801142817_47.txt|archive-date=August 2, 2022}}{{cite web |date=August 2, 2022 |title=NOAA ATCF Best Track for 06W (Songda) |url=https://www.ssd.noaa.gov/PS/TROP/DATA/ATCF/JTWC/bwp062022.dat |publisher=National Oceanic and Atmospheric Administration}}

Songda caused heavy rainfall over the Kyushu and Shikoku regions of Japan and over Jeju Island in South Korea.{{cite web |title=Weather officials urge caution against Tropical Storm Songda |url=https://www3.nhk.or.jp/nhkworld/en/news/20220730_02/ |access-date=2022-08-04 |website=NHK World |language=en}}{{cite web |title=Unstable air bringing heavy rain to western Japan |url=https://www3.nhk.or.jp/nhkworld/en/news/20220730_08/ |access-date=2022-08-04 |website=NHK World |language=en}}{{cite web |last=김수연 |date=2022-07-30 |title=(Lead) Typhoon Songda brings heavy rains to Jeju Island |url=https://en.yna.co.kr/view/AEN20220730001951320 |access-date=2022-08-04 |publisher=Yonhap News Agency |language=en}} Despite strong winds and around {{convert|206|mm|in}} of rain, no damages were reported on Jeju Island.

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=July 29

|Dissipated=August 1

|Image=Trases 2022-07-31 0500Z.jpg

|Track=Trases 2022 track.png

|10-min winds=35

|1-min winds=35

|Pressure=998

}}

A low-pressure area from a massive monsoon gyre developed into a tropical depression southeast of the Ryukyu Islands on July 29.{{cite web |date=July 29, 2022 |title=WWJP27 RJTD 290000 |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-url=https://archive.today/20220729025718/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-date=July 29, 2022 |access-date=July 29, 2022 |publisher=Japan Meteorological Agency}} The PAGASA followed suit in upgrading it, then named the system Ester.{{Cite PAGASA|date=July 29, 2022|name=Ester|type=tcb|no=1|category=TD|url=https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin/TCB%231_ester.pdf|archive-url=https://web.archive.org/web/20220729000000/https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin/TCB%231_ester.pdf|archive-date=July 29, 2022}} [https://archive.org/download/pagasa-22-TC05/PAGASA_22-TC05_Ester_TCB%2301.pdf Alt URL] 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).{{Cite PAGASA|date=July 31, 2022|name=Ester|type=tcb|no=8F|category=TD|url=https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin/TCB%238_ester.pdf|archive-url=https://web.archive.org/web/20220731000000/https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin/TCB%238_ester.pdf|archive-date=July 31, 2022}} [https://archive.org/download/pagasa-22-TC05/PAGASA_22-TC05_Ester_TCB%2308-FINAL.pdf Alt URL] 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.{{cite web |date=July 31, 2022 |title=WTPQ51 RJTD 310300 |url=https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Tropical_cyclone/20220731/030000/A_WTPQ51RJTD310300_C_RJTD_20220731041717_75.txt |archive-url=https://archive.today/20220731091337/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Tropical_cyclone/20220731/030000/A_WTPQ51RJTD310300_C_RJTD_20220731041717_75.txt |archive-date=July 31, 2022 |access-date=August 4, 2022 |publisher=Japan Meteorological Agency}}

Trases then passed over Okinawa, and later made landfall in Jeju Island.{{Cite web|url=https://www.stripes.com/theaters/asia_pacific/storm_tracker/2022-07-26/93w-invest:-tropical-cyclone-formation-alert-issued-6775977.html|title=Tropical Depression 07W (Trases), # 9 FINAL|website=Stars and Stripes}}{{Failed verification|date=August 2022|reason=Reference does not properly detail Trases passing directly over Okinawa, only forecasts. Same with Jeju Island landfall.}} The JTWC issued a TCFA. Later, they upgraded Trases into a tropical depression, and gave the designation of 07W.{{Cite JTWC|date=July 31, 2022|type=tcfa|designation=95W|time=1730Z|url=https://www.metoc.navy.mil/jtwc/products/wp9522web.txt|url-status=dead|archive-date=2022-09-22|archive-url=https://web.archive.org/web/20220922013958/https://www.metoc.navy.mil/jtwc/products/wp9522web.txt}} [https://wiki.chlod.net/jtwc/text/2022-07-31-1750-wp9522web.txt Alt URL] 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|date=August 2022}} 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.{{cite web |date=August 1, 2022 |title=WTPQ51 RJTD 011200 |url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq51.rjtd..txt |archive-url=https://archive.today/20220801134251/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq51.rjtd..txt |archive-date=August 1, 2022 |access-date=August 1, 2022 |publisher=Japan Meteorological Agency}}{{Cite JTWC|date=August 1, 2022|type=warn|category=TD|designation=07W|no=2|name=Trases|time=09Z|url=https://www.metoc.navy.mil/jtwc/products/wp0722web.txt|url-status=dead|archive-date=2022-08-01|archive-url=https://web.archive.org/web/20220801022408/https://www.metoc.navy.mil/jtwc/products/wp0722web.txt}} [https://wiki.chlod.net/jtwc/text/2022-08-01-0700-wp0722web.txt Alt URL]

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=August 3

|Dissipated=August 4

|Image=08W 2022-08-04 0530Z.jpg

|Track=08W 2022 track.png

|10-min winds=30

|1-min winds=25

|Prewinds=<

|Pressure=1002

}}

On August 2, the JTWC noted an area of disorganized convection in the South China Sea, approximately {{cvt|105|nmi}} to the south-southeast of Kaohsiung, Taiwan.{{cite report|title=Significant Tropical Weather Advisory for the Western and South Pacific Oceans (Reissued)|url=https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|publisher=Joint Typhoon Warning Center|date=August 2, 2022|archive-url=https://web.archive.org/web/20220829003233/https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|archive-date=August 29, 2022}} [https://wiki.chlod.net/jtwc/text/2022-08-02-1230-abpwweb.txt Alt URL] 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.{{cite report|title=Tropical Cyclone Formation Alert (Invest 96W)|url=https://www.metoc.navy.mil/jtwc/products/wp9622web.txt|publisher=Joint Typhoon Warning Center|date=August 3, 2022|archive-url=https://archive.today/20220804015326/https://www.metoc.navy.mil/jtwc/products/wp9622web.txt|archive-date=August 4, 2022}} The JMA then upgraded the system into a tropical depression by 18:00 UTC the same day.{{cite web|title=WWJP27 RJTD 031800|url=https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220803/180000/A_WWJP27RJTD031800_C_RJTD_20220803201418_92.txt|publisher=Japan Meteorological Agency|date=August 3, 2022|archive-url=https://archive.today/20220804015704/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220803/180000/A_WWJP27RJTD031800_C_RJTD_20220803201418_92.txt|archive-date=August 4, 2022}} The JTWC subsequently followed suit, designating the depression as 08W by early August 4.{{cite web|title=Tropical Depression 08W (Eight) Warning Nr 001|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpn31.pgtw..txt|publisher=Joint Typhoon Warning Center|date=August 4, 2022|archive-url=https://archive.today/20220804023329/https://tgftp.nws.noaa.gov/data/raw/wt/wtpn31.pgtw..txt|archive-date=August 4, 2022}} The system then struck Huidong County, Guangdong at 01:40 UTC that same day, according to the China Meteorological Administration,{{Cite web|url=http://www.nmc.cn/publish/typhoon/typhoon_new.html|title=台风海洋_台风快讯与报文_台风快讯|website=nmc.cn}} prompting the JTWC to issue its final advisory eight hours after landfall.{{cite web|title=Tropical Depression 08W (Eight) Warning Nr 002|url=https://www.metoc.navy.mil/jtwc/products/wp0822web.txt|publisher=Joint Typhoon Warning Center|date=August 4, 2022|archive-url=https://archive.today/20220804073433/https://www.metoc.navy.mil/jtwc/products/wp0822web.txt|archive-date=August 4, 2022}}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=August 8

|Dissipated=August 11

|Image=Mulan 2022-08-10 0300Z.jpg

|Track=Mulan 2022 track.png

|10-min winds=35

|1-min winds=35

|Pressure=994

}}

On August 5, the JTWC noticed an area of convection with a consolidating low-level circulation center at approximately {{cvt|7|nmi}} to the south of Manila, Philippines.{{cite report|title=Significant Tropical Weather Advisory for the Western and South Pacific Oceans (Reissued)|url=https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|publisher=Joint Typhoon Warning Center|date=August 5, 2022|archive-url=https://web.archive.org/web/20220829003233/https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|archive-date=August 29, 2022}} [https://wiki.chlod.net/jtwc/text/2022-08-05-1400-abpwweb.txt Alt URL] 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.{{cite report|title=Significant Tropical Weather Advisory for the Western and South Pacific Oceans|url=https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|publisher=Joint Typhoon Warning Center|date=August 7, 2022|archive-url=https://web.archive.org/web/20220829003233/https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|archive-date=August 29, 2022}} [https://wiki.chlod.net/jtwc/text/2022-08-07-0520-abpwweb.txt Alt URL] The JMA then upgraded the system into a tropical depression by 00:00 UTC on August 8.{{cite web |title=WWJP27 RJTD 080000|url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|publisher=Japan Meteorological Agency |access-date=8 August 2022|archive-url=https://archive.today/20220808073748/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-date=8 August 2022|date=8 August 2022}} 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.{{cite report|title=Significant Tropical Weather Advisory for the Western and South Pacific Oceans|url=https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|publisher=Joint Typhoon Warning Center|date=August 8, 2022|archive-url=https://web.archive.org/web/20220829003233/https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|archive-date=August 29, 2022}} [https://wiki.chlod.net/jtwc/text/2022-08-08-0550-abpwweb.txt Alt URL]{{cite report|title=Tropical Cyclone Formation Alert (Corrected)|url=https://www.metoc.navy.mil/jtwc/products/wp9722web.txt|publisher=Joint Typhoon Warning Center|date=August 8, 2022|archive-url=https://archive.today/20220809015210/https://www.metoc.navy.mil/jtwc/products/wp9722web.txt|archive-date=August 9, 2022}} By the next day, the JMA upgraded it into a tropical storm, and it was given the name Mulan.{{cite web|title=RSMC Tropical Cyclone Advisory TS 2207 Mulan (2207) upgraded from TD |url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt|publisher=Japan Meteorological Agency|date=August 9, 2022|archive-url=https://archive.today/20220809082108/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt|archive-date=August 9, 2022}} The JTWC, however, did not recognize Mulan as tropical, due to its huge radius of maximum winds which "are typically present in monsoonal depressions."{{cite report|title=Tropical Cyclone Formation Alert (Reissued)|url=https://www.metoc.navy.mil/jtwc/products/wp9722web.txt|publisher=Joint Typhoon Warning Center|date=August 9, 2022|archive-url=https://archive.today/20220810013549/https://www.metoc.navy.mil/jtwc/products/wp9722web.txt|archive-date=August 10, 2022}} 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.{{cite news|title=Typhoon Mulan makes landfall in South China|url=https://english.news.cn/20220810/b79d7252c23c449c93fd8e60a7b94819/c.html|publisher=Xinhua News Agency|date=August 10, 2022|access-date=August 28, 2022}} The JTWC subsequently canceled the TCFA and downgraded its formation chances to medium.{{cite report|title=Tropical Cyclone Formation Alert Cancellation|url=https://www.metoc.navy.mil/jtwc/products/wp9722web.txt|publisher=Joint Typhoon Warning Center|date=August 10, 2022|archive-url=https://archive.today/20220810140505/https://www.metoc.navy.mil/jtwc/products/wp9722web.txt|archive-date=August 10, 2022}} 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.{{cite web|title=RSMC Tropical Cyclone Advisory TD downgraded from TS 2207 Mulan (2207)|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt|publisher=Japan Meteorological Agency|date=August 11, 2022|archive-url=https://archive.today/20220811021720/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt|archive-date=August 11, 2022}}{{cite web|title=WWJP27 RJTD 110600|url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|publisher=Japan Meteorological Agency|date=August 11, 2022|archive-url=https://archive.today/20220811083255/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|archive-date=August 11, 2022}}

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 {{cvt|20 to 50|mm}}.{{cite web|title=Storm Mulan circulation leaves six dead and missing|url=https://en.baoquocte.vn/storm-mulan-circulation-leaves-six-dead-and-missing-194437.html|date=August 15, 2022|publisher=The World and Vietnam Report}} 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.{{cite web|title=Farmed lobsters die en masse following storm in south-central Vietnam|date=August 13, 2022|publisher=Tuổi Trẻ News|url=https://tuoitrenews.vn/news/society/20220813/farmed-lobsters-die-en-masse-following-storm-in-southcentral-vietnam/68568.html}} In Son La the damaged reached 7 billion dong (US$295,000),{{cite web |url=https://baotainguyenmoitruong.vn/son-la-hoan-luu-bao-so-2-gay-thiet-hai-hon-7-ty-dong-342716.html |title=Sơn la: Hoàn lưu bão số 2 gây thiệt hại hơn 7 tỷ đồng |date=August 13, 2022 }} in Da Bac District is 2.3 billion dong (US$97,000){{Cite web|url=https://baohoabinh.com.vn/28/170122/Huyen-Da-Bac-tap-trung-khac-phuc-thiet-hai-do-thien-tai-gay-ra.htm|title=Huyện Đà Bắc tập trung khắc phục thiệt hại do thiên tai gây ra|website=baohoabinh.com.vn}} and in Cao Phong District in Hoa Binh is 3 billion dong (US$127,000).{{Cite web |last=Vì |first=Duy Long |date=29 August 2022 |title=Huyện Cao Phong: Thiệt hại do cơn bão số 2 hơn 3 tỷ đồng |trans-title=Cao Phong District: Damage by storm No. 2 is over 3 billion dong |url=https://caophong.hoabinh.gov.vn/tin-t-c-s-ki-n/kinh-t/2490-huya-n-cao-phong-thia-t-ha-i-do-c-n-ba-o-sa-2-h-n-3-ta-a-ng |language=Vietnamese}} Total damages caused by Mulan were 33.7 billion VND (US$1.44 million).

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=August 8

|Dissipated=August 14

|Image=Meari 2022-08-13 0145Z.jpg

|Track=Meari 2022 track.png

|10-min winds=40

|1-min winds=35

|Pressure=996

}}

A low-pressure area developed into a tropical depression northwest of Iwo Jima on August 10.{{cite web |title=WWJP27 RJTD 091800 |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |publisher=Japan Meteorological Agency |access-date=10 August 2022 |archive-url=https://archive.today/20220810021938/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220809/180000/A_WWJP27RJTD091800_C_RJTD_20220809202118_86.txt |archive-date=10 August 2022 |date=9 August 2022}}{{cite web |title=WTPQ51 RJTD 100000 |url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq51.rjtd..txt |publisher=Japan Meteorological Agency |access-date=10 August 2022 |archive-url=https://archive.today/20220810021908/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq51.rjtd..txt |archive-date=10 August 2022 |date=10 August 2022}} 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.{{cite web |title=Tropical Storm 09W (Meari) Warning #11Final Warning Issued at 13/2100Z|url=https://www.metoc.navy.mil/jtwc/products/wp0922web.txt|date=13 August 2022|access-date=13 August 2022|website=JTWC|archive-url=https://ghostarchive.org/archive/nlwV8|archive-date=13 August 2022}}

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.{{Cite news|url=https://mainichi.jp/english/articles/20220813/p2g/00m/0na/010000c|title=Typhoon Meari makes landfall on Japan's Pacific coast|newspaper=The Mainichi|date=August 13, 2022 |agency=Kyodo|access-date=August 14, 2022}}{{cite news|url=https://abcnews.go.com/amp/International/wireStory/tropical-storm-meari-hammers-japan-heavy-rainfall-wind-88332896|title=Tropical Storm Meari hammers Japan with heavy rainfall, wind|author=Kageyama, Yuri|agency=Associates Press|publisher=ABC News|access-date=August 14, 2022}}

Homes in Central Japan were destroyed.{{Cite news |title=Homes destroyed in Japan tropical storm |language=en-GB |publisher=BBC News |url=https://www.bbc.co.uk/news/av/world-asia-62544007 |access-date=2022-08-15}}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=August 20

|Dissipated=August 26

|Image=Ma-on 2022-08-24 0550Z.jpg

|Track=Ma-on_2022_track.png

|10-min winds=55

|1-min winds=65

|Pressure=985

}}{{Main|Tropical Storm Ma-on}}

On August 19, the JMA began tracking a low pressure area in the Philippine Sea, around {{convert|500|km|mi}} north of Palau.{{cite web |date=August 19, 2022 |title=WWJP27 RJTD 190000 |url=https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220819/000000/A_WWJP27RJTD190000_C_RJTD_20220819021616_20.txt |archive-url=https://archive.today/20220821024009/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220819/000000/A_WWJP27RJTD190000_C_RJTD_20220819021616_20.txt |archive-date=August 21, 2022 |access-date=August 21, 2022 |publisher=Japan Meteorological Agency}} The low pressure area slowly moved westwards, eventually developing into a tropical depression on August 20.{{cite web |date=August 20, 2022 |title=WWJP27 RJTD 201800 |url=https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220820/180000/A_WWJP27RJTD201800_C_RJTD_20220820202416_32.txt |archive-url=https://archive.today/20220821024016/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220820/180000/A_WWJP27RJTD201800_C_RJTD_20220820202416_32.txt |archive-date=August 21, 2022 |access-date=August 21, 2022 |publisher=Japan Meteorological Agency}} 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.{{Cite PAGASA|date=August 21, 2022|name=Florita|type=tcb|no=1|category=TD|url=https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin_florita.pdf |archive-url=https://web.archive.org/web/20220821000000/https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin_florita.pdf|archive-date=August 21, 2022}} [https://archive.org/download/pagasa-22-TC06/PAGASA_22-TC06_Florita_TCB%2301.pdf Alt URL] Shortly afterwards, the JTWC designated the system as 10W.{{cite web |date=August 21, 2022 |title=WTPN31 PGTW 211500 |url=https://www.metoc.navy.mil/jtwc/products/wp1022web.txt |archive-url=https://web.archive.org/web/20220821154004/https://www.metoc.navy.mil/jtwc/products/wp1022web.txt |archive-date=August 21, 2022 |access-date=August 21, 2022 |publisher=Joint Typhoon Warning Center}} 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.{{cite web |title='Florita' makes landfall in Isabela; to exit PAR Wednesday |url=https://www.pna.gov.ph/articles/1181944 |access-date=2022-08-23 |website=pna.gov.ph |language=en}} Four fatalities occurred;{{cite web|title=Florita exits PH; death toll now 4|url=https://newsinfo.inquirer.net/1652780/florita-exits-ph-death-toll-now-4|date=August 28, 2022|work=Inquirer}} infrastructure damage was estimated to be ₱{{Format price|571100000}} (US${{Format price|{{#expr:10350000}}}}), while agricultural damage was estimated to be ₱{{Format price|1855024611.66}} (US${{Format price|{{#expr:33600000}}}}).{{cite web |title=Situational Report for TC FLORITA (2022) - SitRep No. 10 for Severe Tropical Storm FLORITA (2022) |url=https://monitoring-dashboard.ndrrmc.gov.ph/assets/uploads/situations/SUMMARY_SitRep_No__10_for_Severe_Tropical_Storm_FLORITA_20221.pdf |publisher=National Disaster Risk Reduction and Management Council |archive-url=https://web.archive.org/web/20230220192305/https://monitoring-dashboard.ndrrmc.gov.ph/assets/uploads/situations/SUMMARY_SitRep_No__10_for_Severe_Tropical_Storm_FLORITA_20221.pdf |archive-date=February 20, 2023 |date=September 4, 2022 |url-status=dead}}

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.{{cite web |date=2022-08-25 |title=Bão vào Quảng Ninh, suy yếu thành áp thấp nhiệt đới |url=https://vnexpress.net/bao-vao-quang-ninh-suy-yeu-thanh-ap-thap-nhiet-doi-4503969.html |website=VnExpress}}

The storm caused moderate damage in Vietnam and killed three people.{{cite web |url=https://vnexpress.net/hang-loat-cay-xanh-bat-goc-sau-bao-maon-4504081.html |title=Hàng loạt cây xanh bật gốc sau bão Maon }}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=August 21

|Dissipated=August 25

|Image=Tokage 2022-08-24 0235Z.jpg

|Track=Tokage 2022 track.png

|10-min winds=75

|1-min winds=95

|Pressure=970

}}

On August 21, the JMA noted that a tropical depression had formed to the northeast of Guam.{{cite web|title=WWJP27 RJTD 210600|url=https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220821/060000/A_WWJP27RJTD210600_C_RJTD_20220821081817_44.txt|publisher=Japan Meteorological Agency|date=August 21, 2022|archive-url=https://archive.today/20220821142424/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220821/060000/A_WWJP27RJTD210600_C_RJTD_20220821081817_44.txt|archive-date=August 21, 2022}} 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.{{cite web|title=RSMC Tropical Cyclone Advisory TS 2210 Tokage (2210) upgraded from TD|url=https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Tropical_cyclone/20220822/030000/A_WTPQ51RJTD220300_C_RJTD_20220822042016_55.txt|publisher=Japan Meteorological Agency|date=August 22, 2022|archive-url=https://archive.today/20220822074737/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Tropical_cyclone/20220822/030000/A_WTPQ51RJTD220300_C_RJTD_20220822042016_55.txt|archive-date=August 22, 2022}}{{cite report|title=Prognostic Reasoning for Tropical Storm 11W (Tokage) Warning Nr 001|url=https://www.metoc.navy.mil/jtwc/products/wp1122prog.txt|publisher=Joint Typhoon Warning Center|date=August 22, 2022|archive-url=https://archive.today/20220822080937/https://www.metoc.navy.mil/jtwc/products/wp1122prog.txt|archive-date=August 22, 2022}} Moving north-northwest, Tokage would intensify into a severe tropical storm later by the same day,{{cite report|title=RSMC Tropical Cyclone Prognostic Reasoning No.5 for STS 2210 Tokage (2210)|url=https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Tropical_cyclone/20220822/180000/A_WTPQ31RJTD221800_C_RJTD_20220822201015_1.txt|publisher=Japan Meteorological Agency|date=August 22, 2022|archive-url=https://archive.today/20220823020806/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Tropical_cyclone/20220822/180000/A_WTPQ31RJTD221800_C_RJTD_20220822201015_1.txt|archive-date=August 23, 2022}} and by 09:00 UTC on August 23, the JTWC upgraded Tokage to a typhoon, with the JMA following suit three hours later.{{cite report|title=Prognostic Reasoning for Typhoon 11W (Tokage) Nr 005|url=https://www.metoc.navy.mil/jtwc/products/wp1122prog.txt|publisher=Joint Typhoon Warning Center|date=August 23, 2022|archive-url=https://archive.today/20220823092200/https://www.metoc.navy.mil/jtwc/products/wp1122prog.txt|archive-date=August 23, 2022}}{{cite report|title=RSMC Tropical Cyclone Prognostic Reasoning No.8 for TY 2210 Tokage (2210)|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq31.rjtd..txt|publisher=Japan Meteorological Agency|date=August 23, 2022|archive-url=https://archive.today/20220823142920/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq31.rjtd..txt|archive-date=August 23, 2022}} The storm would peak six hours later according to the JMA, with 10-minute sustained winds of {{cvt|140|km/h}} 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 {{cvt|175|km/h}}, making Tokage a Category 3-equivalent typhoon on the Saffir-Simpson scale.{{cite web|title=RSMC Tropical Cyclone Advisory TY 2210 Tokage (2210)|url=https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Tropical_cyclone/20220823/180000/A_WTPQ51RJTD231800_C_RJTD_20220823190116_11.txt|publisher=Japan Meteorological Agency|date=August 23, 2022|archive-url=https://archive.today/20220824015647/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Tropical_cyclone/20220823/180000/A_WTPQ51RJTD231800_C_RJTD_20220823190116_11.txt|archive-date=August 24, 2022}}{{cite report|title=Prognostic Reasoning for Typhoon 11W (Tokage) Warning Nr 008|url=https://tgftp.nws.noaa.gov/data/raw/wd/wdpn32.pgtw..txt|publisher=Joint Typhoon Warning Center|date=August 24, 2022|archive-url=https://archive.today/20220824025139/https://tgftp.nws.noaa.gov/data/raw/wd/wdpn32.pgtw..txt\|archive-date=August 24, 2022}}{{cite web|title=bwp112022.dat|url=https://www.ssd.noaa.gov/PS/TROP/DATA/ATCF/JTWC/bwp112022.dat|publisher=Joint Typhoon Warning Center, National Oceanic and Atmospheric Administration|date=August 26, 2022|access-date=August 28, 2022}} 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,{{cite report|title=Prognostic Reasoning for Typhoon 11W (Tokage) Warning Nr 010|url=https://tgftp.nws.noaa.gov/data/raw/wd/wdpn32.pgtw..txt|publisher=Joint Typhoon Warning Center|date=August 24, 2022|archive-url=https://archive.today/20220824143622/https://tgftp.nws.noaa.gov/data/raw/wd/wdpn32.pgtw..txt|archive-date=August 24, 2022}} and commenced extratropical transition by 03:00 UTC on August 25.{{cite report|title=Prognostic Reasoning for Typhoon 11W (Tokage) Warning Nr 012|url=https://tgftp.nws.noaa.gov/data/raw/wd/wdpn32.pgtw..txt|publisher=Joint Typhoon Warning Center|date=August 25, 2022|archive-url=https://archive.today/20220825031524/https://tgftp.nws.noaa.gov/data/raw/wd/wdpn32.pgtw..txt|archive-date=August 25, 2022}} The storm would complete its transition 12 hours later, with the JTWC issuing its final advisory, and the JMA following suit three hours later.{{cite web|title=Tropical Storm 11W (Tokage) Warning Nr 014|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpn32.pgtw..txt|publisher=Joint Typhoon Warning Center|date=August 25, 2022|archive-url=https://archive.today/20220825150705/https://tgftp.nws.noaa.gov/data/raw/wt/wtpn32.pgtw..txt|archive-date=August 25, 2022}}{{cite web|title=RSMC Tropical Cyclone Prognostic Reasoning No.17 for Developed Low Former STS 2210 Tokage (2210)|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq31.rjtd..txt|publisher=Japan Meteorological Agency|date=August 25, 2022|archive-url=https://archive.today/20220826015305/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq31.rjtd..txt|archive-date=August 26, 2022}}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=August 27

|Dissipated=September 6

|Image=Hinnamnor 2022-09-01 0000Z.jpg

|Track=Hinnamnor 2022 path.png

|10-min winds=105

|1-min winds=145

|Pressure=920

}}{{main|Typhoon Hinnamnor}}

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.{{cite web |last=JTWC |first=Joint Typhoon Warning Center |date=August 28, 2022 |title=Tropical Cyclone Formation Alert (Invest 90W) |url=https://www.metoc.navy.mil/jtwc/jtwc.html |archive-url=https://archive.today/20220828074833/https://www.metoc.navy.mil/jtwc/products/wp9022web.txt |archive-date=August 28, 2022}} 6 hours later, it intensified into a tropical storm, being named Hinnamnor by the JMA, which replaced the name Nock-ten.{{cite web |last=JMA |first=Japan Meteorological Agency |date=August 29, 2022 |title=RSMC Tropical Cyclone Prognostic Reasoning No. 2 For TS 2211 Hinnamnor (2211) |url=https://www.jma.go.jp/jma/index.html |archive-url=https://archive.today/20220828080014/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq30.rjtd..txt |archive-date=August 28, 2022}} Moving due west, Hinnamnor steadily strengthened, gaining Category 1-equivalent winds of {{cvt|75|knot}} on August 29.{{cite web |last=JTWC |first=Joint Typhoon Warning Center |date=August 29, 2022 |title=Prognpstoc Reasoning For Typhoon 12W (Hinnanmor) Warning NR 005 |url=https://www.metoc.navy.mil/jtwc/jtwc.html |archive-url=https://archive.today/20220829091044/https://tgftp.nws.noaa.gov/data/raw/wd/wdpn31.pgtw..txt |archive-date=August 29, 2022}} At the same time, the JMA upgraded Hinnamnor to a typhoon.{{cite web |last=JMA |first=Japan Meteorological Agency |date=August 29, 2022 |title=Tropical Cyclone Prognostic Reasoning No. 6 For TY 2211 Hinnanmor (2211) |url=https://www.jma.go.jp/jma/index.html |archive-url=https://archive.today/20220829075702/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq30.rjtd..txt |archive-date=August 29, 2022}} The system underwent rapid intensification, and proceeded to gain Category 3-equivalent winds at 12:00 UTC the same day.{{cite web |last=JTWC |first=Joint Typhoon Warning Center |date=August 29, 2022 |title=Typhoon 12W (Hinnanmor) Warning NR 006 |url=https://www.metoc.navy.mil/jtwc/jtwc.html |archive-url=https://archive.today/20220829142101/https://tgftp.nws.noaa.gov/data/raw/wt/wtpn31.pgtw..txt |archive-date=August 29, 2022}} Quickly strengthening overnight, the storm quickly grew with Category 5-equivalent winds of {{cvt|140|knot}}, with a minimum pressure of {{convert|920|hPa|inHg|sigfig=4}} with a pinhole eye.{{cite web |last=JTWC |first=Joint Typhoon Warning Center |date=August 30, 2022 |title=Super Typhoon 12W (Hinnanmor) Warning NR 011 |url=https://www.metoc.navy.mil/jtwc/jtwc.html |archive-url=https://archive.today/20220831020547/https://www.wis-jma.go.jp/d/o/PGTW/Alphanumeric/Warning/Tropical_cyclone/20220830/210000/A_WTPN31PGTW302100_C_RJTD_20220830200231_16.txt |archive-date=August 31, 2022}}{{cite web |last=JTWC |first=Joint Typhoon Warning Center |date=August 30, 2022 |title=Prognostic Reasoning For Super Typhoon 12W (Hinnanmor) Warning NR 011 |url=https://www.metoc.navy.mil/jtwc/jtwc.html |archive-url=https://archive.today/20220831015846/https://tgftp.nws.noaa.gov/data/raw/wd/wdpn31.pgtw..txt |archive-date=August 31, 2022}}{{cite web |last=JMA |first=Japan Meteorological Agency |date=August 30, 2022 |title=Reasoning No. 12 For TY 2211 Hinnanmor (2211) |url=https://www.jma.go.jp/jma/index.html |archive-url=https://archive.today/20220831021221/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Tropical_cyclone/20220830/180000/A_WTPQ30RJTD301800_C_RJTD_20220830194831_15.txt |archive-date=August 31, 2022}} 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.{{cite web |last=JMA |first=Japan Meteorological Agency |date=August 31, 2022 |title=Reasoning No. 15 For TY 2211 Hinnanmor (2211) |url=https://www.jma.go.jp/jma/index.html |archive-url=https://archive.today/20220831153306/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq30.rjtd..txt |archive-date=August 31, 2022}}{{cite web |last=JTWC |first=Joint Typhoon Warning Center |date=August 31, 2022 |title=Typhoon 12W (Hinnanmor) Warning NR 014 |url=https://www.metoc.navy.mil/jtwc/jtwc.html |archive-url=https://archive.today/20220831153506/https://tgftp.nws.noaa.gov/data/raw/wt/wtpn31.pgtw..txt |archive-date=August 31, 2022}}{{cite web |last=JTWC |first=Joint Typhoon Warning Center |date=August 31, 2022 |title=Prognostic Reasoning For Typhoon 12W (Hinnanmor) Warning NR 014 |url=https://www.metoc.navy.mil/jtwc/jtwc.html |archive-url=https://archive.today/20220831153628/https://tgftp.nws.noaa.gov/data/raw/wd/wdpn31.pgtw..txt |archive-date=August 31, 2022}}

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.{{cite news |last=Mendoza |first=John Eric |date=2022-08-31 |title=Super Typhoon Hinnamnor roars into PAR and is now named Henry |url=https://newsinfo.inquirer.net/1656401/super-typhoon-hinnamnor-enters-ph-and-is-now-named-henry |access-date=2022-09-01 |newspaper=Philippine Daily Inquirer |language=en}} 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.{{Cite web |date=September 6, 2022 |title=Typhoon Hinnamnor makes landfall, thousands evacuate to safety |url=https://www.koreatimes.co.kr/www/nation/2022/09/371_335627.html |archive-url=https://web.archive.org/web/20220906051212/https://www.koreatimes.co.kr/www/nation/2022/09/371_335627.html |archive-date=September 6, 2022 |access-date=September 6, 2022 |website=koreatimes |language=en}}{{Cite JTWC|date=September 4, 2022|type=prog|category=TY|designation=12W|no=28|name=Hinnamnor |url=https://www.metoc.navy.mil/jtwc/products/wp1222prog.txt|url-status=dead|archive-date=September 4, 2022|archive-url=https://archive.today/20220904080328/https://www.wis-jma.go.jp/d/o/PGTW/Alphanumeric/Warning/Tropical_cyclone/20220904/030000/A_WDPN31PGTW040300_C_RJTD_20220904023718_89.txt#selection-9.630-9.639}} The JMA issued its last advisory on Hinnamnor, and declared it an extratropical low.{{Cite web |date=September 6, 2022 |title=RSMC Tropical Cyclone Advisory Name Developing Low Former STS Hinnamnor (2011) |url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq30.rjtd..txt |archive-url=https://archive.today/20220906142256/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt|archive-date=September 6, 2022 |access-date=September 6, 2022 |website=Japan Meteorological Agency}} The low moved northward and last noted in Okhotsk, Russia on September 7.{{Cite report |url=https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220412/180000/A_WWJP27RJTD121800_C_RJTD_20220412202517_48.txt |title=WWJP27 RJTD 061200 (Warning and Weather Summary) |last=Japan Meteorological Agency |date=September 6, 2022 |author-link=Japan Meteorological Agency |access-date=September 6, 2022 |archive-url=https://archive.today/20220906143402/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|archive-date=September 6, 2022 |url-status=dead }}{{Cite report |url=https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220412/180000/A_WWJP27RJTD121800_C_RJTD_20220412202517_48.txt |title=WWJP27 RJTD 070600 (Warning and Weather Summary) |last=Japan Meteorological Agency |date=September 6, 2022 |author-link=Japan Meteorological Agency |access-date=September 7, 2022 |archive-url=https://archive.today/20220907131421/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|archive-date=September 7, 2022|url-status=dead }}

In Ifugao, a man was buried in the landslide due to heavy rains caused by the typhoon.{{cite web |url=https://mb.com.ph/2022/09/01/landslide-spawned-by-typhoon-henrys-heavy-rains-catches-farmer-inside-brothers-house-in-ifugao/ |title=Landslide spawned by Typhoon Henry's heavy rains catches farmer inside brother's house in Ifugao |website=Manila Bulletin |date=September 2022 }} Several flights were canceled to and from Okinawa.{{Cite news |date=September 2, 2022 |title=Super typhoon 'Hinnamnor', strongest storm of 2022, batters Japan |work=Mint |url=https://www.livemint.com/news/world/explainer-super-typhoon-hinnamnor-strongest-storm-of-2022-batters-japan-11662078554253.html |access-date=September 2, 2022}} 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.{{cite web |url=https://www.em.com.br/app/noticia/internacional/2022/09/06/interna_internacional,1391556/tufao-hinnamnor-deixa-um-morto-e-nove-desaparecidos-na-coreia-do-sul.shtml |title=Tufão Hinnamnor deixa um morto e nove desaparecidos na Coreia do Sul |date=September 6, 2022 }}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=August 30

|Dissipated=September 1

|Image=Gardo 2022-08-30 0450Z.jpg

|Track=Gardo 2022 track.png

|10-min winds=30

|1-min winds=30

|Pressure=998

}}

On August 30 at 00:00 UTC, the JMA began tracking a westward-moving tropical depression.{{cite web |date=August 30, 2022 |title=WWJP27 RJTD 300000 |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-url=https://archive.today/20220830035433/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-date=August 30, 2022 |access-date=September 2, 2022 |website=Japan Meteorological Agency}}{{cite web |date=August 30, 2022 |title=WTPQ51 RJTD 300600 |url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq51.rjtd..txt |archive-url=https://archive.today/20220830075601/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq51.rjtd..txt |archive-date=August 30, 2022 |access-date=September 2, 2022 |website=Japan Meteorological Agency}} A few hours later, the PAGASA gave it the local name Gardo due to it being inside their area of responsibility.{{Cite news |last=Arceo |first=Acor |date=August 30, 2022 |title=LPA develops into Tropical Depression Gardo; Hinnamnor becomes super typhoon |work=Rappler |url=https://www.rappler.com/nation/weather/tropical-depression-gardo-super-typhoon-hinnamnor-pagasa-forecast-august-30-2022-5pm/ |access-date=September 2, 2022}} The JTWC issued a TCFA for the system,{{Cite JTWC|date=August 30, 2022|type=tcfa|designation=98W|url=https://www.metoc.navy.mil/jtwc/products/wp9822web.txt|archive-url=https://archive.today/20220830075749/https://www.metoc.navy.mil/jtwc/products/wp9822web.txt|url-status=dead|archive-date=August 30, 2022|access-date=September 2, 2022}} and would then upgrade the system to a tropical depression, designating it as 13W. Due to its proximity to Typhoon Hinnamnor,{{Cite JTWC|date=August 30, 2022|type=prog|category=TD|designation=13W|no=1|name=Thirteen|url=https://tgftp.nws.noaa.gov/data/raw/wd/wdpn32.pgtw..txt|archive-url=https://archive.today/20220831015856/https://tgftp.nws.noaa.gov/data/raw/wd/wdpn32.pgtw..txt|archive-date=August 31, 2022|access-date=September 2, 2022}} its outflow fully exposed 13W's circulation.{{Cite jtwc|date=August 31, 2022|type=prog|category=TD|designation=13W|no=3|name=Thirteen|url=https://www.metoc.navy.mil/jtwc/products/wp1322prog.txt|archive-url=https://archive.today/20220831083411/https://www.metoc.navy.mil/jtwc/products/wp1322prog.txt|archive-date=August 31, 2022|access-date=September 2, 2022}} On September 1, the JMA, the JTWC, and the PAGASA issued their final warnings on the system as it was absorbed into Hinnamnor.{{cite web |date=September 1, 2022 |title=RSMC Tropical Cyclone Prognostic Reasoning No. 8 for TD Located at 24.0N 129.0E |url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq31.rjtd..txt |archive-url=https://archive.today/20220901081217/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq31.rjtd..txt |archive-date=September 1, 2022 |access-date=September 2, 2022 |website=Japan Meteorological Agency}}{{Cite jtwc|date=September 1, 2022|type=warn|designation=13W|no=6|name=Thirteen|url=https://www.metoc.navy.mil/jtwc/products/wp1322web.txt|archive-url=https://archive.today/20220901082305/https://www.metoc.navy.mil/jtwc/products/wp1322web.txt|archive-date=September 1, 2022|access-date=September 2, 2022}}{{Cite news |last=Arceo |first=Acor |date=September 1, 2022 |title=Super Typhoon Henry slightly intensifies; Tropical Depression Gardo weakens into LPA |work=Rappler |url=https://www.rappler.com/nation/weather/super-typhoon-henry-tropical-depression-gardo-pagasa-forecast-september-1-2022-11am/ |access-date=September 2, 2022}}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=September 3

|Dissipated=September 15

|Image=Muifa 2022-09-11 0500Z.jpg

|Track=Muifa 2022 track.png

|10-min winds=85

|1-min winds=110

|Pressure=950

}}{{main|Typhoon Muifa (2022)}}

The JTWC detected a disturbance at approximately {{cvt|255|nmi}} from Iwo-To. According to the agency, the cyclone achieved a favorable environment for a more comprehensive intensification because of the warm waters (between {{cvt|30 and 31|°C|disp=sqbr}}) and was designated as Invest 91W.{{cite web |url=https://www.metoc.navy.mil/jtwc/products/abpwweb.txt |archive-url=https://ghostarchive.org/archive/AGSZf|title=Current Significant Tropical Weather Advisories ABPW10 Western/South Pacific Ocean (Invest 91W) |website=JTWC |date=September 6, 2022 |access-date=September 6, 2022|language=en|archive-date=September 6, 2022}} A day later, the cyclone became a tropical storm according to the JTWC, being {{cvt|696|nmi}} SSE of Kadena Air Base. The JMA, however, had not released any bulletin to designate this system until then.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1422web.txt|title=Tropical Storm 14W (Fourteen) Warning #03 Issued at 07/0300Z |archive-url=https://ghostarchive.org/archive/zpIEv|access-date=7 September 2022|date=7 September 2022|archive-date=7 September 2022|website=JTWC|language=en}} 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.{{cite web|url=https://bagong.pagasa.dost.gov.ph/tropical-cyclone/severe-weather-bulletin|date=September 8, 2022|access-date=8 September 2022|archive-date=8 September 2022|archive-url=https://web.archive.org/web/20220908034204/https://bagong.pagasa.dost.gov.ph/tropical-cyclone/severe-weather-bulletin|title=Tropical Cyclone Bulletin #3 Tropical storm "Inday"|website=PAGASA}} Within the PAR, the storm strengthened into a severe tropical storm according to PAGASA.{{cite web|title=Tropical Cyclone Bulletin #10 Severe tropical storm "Inday"

|url=https://bagong.pagasa.dost.gov.ph/tropical-cyclone/severe-weather-bulletin|archive-url=https://ghostarchive.org/archive/XWZot|archive-date=10 September 2022|date=10 September 2022|access-date=10 September 2022|website=PAGASA}} Muifa then intensified into a typhoon according to the JTWC, as it reached {{cvt|120|km/h|mph knot}} in sustained one-minute winds.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1422web.txt|archive-url=https://ghostarchive.org/archive/AD10v|archive-date=10 September 2022|date=9 September 2022|access-date=10 September 2022|website=JTWC|title=Typhoon 14W (Muifa) Warning #14 Issued 09/2100Z}} 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.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1422web.txt|archive-url=https://ghostarchive.org/archive/vgQ0F|date=10 September 2022|access-date=10 September 2022|archive-date=10 September 2022|title=Typhoon 14W (Muifa) Warning #18 Issued 10/2100Z|website=JTWC|language=en}} On September 12, Muifa hit Ishigaki Island;{{cite web|last1=Masters|first1=Jeff|last2=Henson|first2=Bob|title=Typhoon Muifa storms toward Shanghai; all quiet on the Atlantic front|date=September 12, 2022|url=https://yaleclimateconnections.org/2022/09/typhoon-muifa-storms-toward-shanghai-all-quiet-on-the-atlantic-front/|publisher=Yale Climate Connections|location=New Haven, Connecticut|language=en|access-date=September 12, 2022}} it left the PAR the same day in the afternoon.{{cite web|url=https://bagong.pagasa.dost.gov.ph/tropical-cyclone/severe-weather-bulletin|archive-url=https://archive.today/20220912211447/https://bagong.pagasa.dost.gov.ph/tropical-cyclone/severe-weather-bulletin|archive-date=12 September 2022|date=12 September 2022|access-date=12 September 2022|website=PAGASA|title=Tropical Cyclone Bulletin #22 typhoon "Inday" (Final bulletin)}} With winds of {{cvt|155|km/h|mph knot}}, 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.{{cite web |last1=Henson |first1=Bob |last2=Masters |first2=Jeff |title=Typhoon Muifa sweeps into Shanghai; Caribbean eyes new tropical depression |date=September 14, 2022 |url=https://yaleclimateconnections.org/2022/09/typhoon-muifa-sweeps-into-shanghai-caribbean-eyes-new-tropical-depression/ |publisher=Yale Climate Connections |access-date=14 September 2022}}{{Cite news|date=2022-09-16|title=Weather tracker: Typhoon Muifa wreaks havoc in China after summer of records|language=en-GB|work=The Guardian|url=https://www.theguardian.com/environment/2022/sep/16/weather-tracker-typhoon-muifa-wreaks-havoc-in-china-after-summer-of-records|access-date=2023-04-06|issn=0261-3077}} Muifa was downgraded to a tropical storm when it made landfall according to the JTWC.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1422web.txt|archive-url=https://ghostarchive.org/archive/pHtqD|date=15 September 2022|access-date=15 September 2022|archive-date=15 September 2022|title=Tropical storm Muifa (14W) Warning #37 Issued 15/1500Z|website=JTWC|language=en}} Muifa was downgraded to a tropical depression again by the JTWC on its last bulletin for the system.{{cite web |url=https://www.metoc.navy.mil/jtwc/products/wp1422web.txt |archive-url=https://ghostarchive.org/archive/wtepa|date=16 September 2022|access-date=16 September 2022|archive-date=16 September 2022 |title=Tropical depression Muifa (14W) Warning #40 Final bulletin Issued 16/0900Z |website=JTWC |language=en}}

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.{{cite web |date=13 September 2022 |title=Orange warning of typhoon Muifa |url=http://www.cma.gov.cn/en2014/weather/Warnings/ActiveWarnings/202209/t20220913_5083997.html |archive-url=https://archive.today/20220913172234/http://www.cma.gov.cn/en2014/weather/Warnings/ActiveWarnings/202209/t20220913_5083997.html |archive-date=13 September 2022 |access-date=13 September 2022 |website=China Meteorological Administration |language=en}} 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.{{cite news |url=https://www.reuters.com/business/environment/chinas-zhejiang-province-high-alert-ahead-typhoon-muifa-2022-09-14/ |title=Typhoon Muifa pounds eastern China with strong gales, rain |newspaper=Reuters |date=September 14, 2022 }}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Image=Merbok 2022-09-14 0240Z.jpg

|Track=Merbok 2022 track.png

|Formed=September 10

|Dissipated=September 15

|10-min winds=70

|1-min winds=70

|Pressure=965

}}

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.{{cite web|archive-url=https://archive.today/20220909030720/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|date=10 September 2022|access-date=10 September 2022|archive-date=9 September 2022|title=Bulletin released of Typhoon Muifa, tropical depression 15W and tropical depression Issued 10/1800Z|website=Japan Meteorological Agency|language=en}} 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.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1522web.txt|archive-url=https://ghostarchive.org/archive/bGpCn|date=10 September 2022|access-date=10 September 2022|archive-date=10 September 2022|title=Tropical depression 15W (Fifteen) Warning #01 Issued 10/2100Z|website=JTWC|language=en}} In its fifth bulletin, the JTWC stated that 15W turned into a tropical storm when it reached {{cvt|65|km/h|mph knot}} one-minute sustained winds.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1522web.txt|archive-url=https://ghostarchive.org/archive/coBAK|date=11 September 2022|access-date=11 September 2022|archive-date=11 September 2022|title=Tropical storm 15W (Fifteen) Warning #05 Issued 11/2100Z|website=JTWC|language=en}} The JMA named the system Merbok on September 12, due to it having achieved 10-minute sustained winds of {{cvt|35|knot|round=5|order=out}}.{{cite web|url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|archive-url=https://ghostarchive.org/archive/55nL1|date=12 September 2022|access-date=12 September 2022|archive-date=12 September 2022|title=Bulletin released of Typhoon Muifa, tropical storm Merbok and tropical depression Issued 12/0300Z|website=Japan Meteorological Agency|language=en}} Later that day, Merbok reached severe tropical storm status.{{cite web|url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|archive-url=https://ghostarchive.org/archive/rBgvT|date=12 September 2022|access-date=12 September 2022|archive-date=12 September 2022|title=Bulletin released of typhoon Muifa, severe tropical storm Merbok and tropical depression Issued 12/0900Z|website=Japan Meteorological Agency|language=en}} The next day, the JTWC reported that Merbok became a Category 1 typhoon, reaching sustained winds of {{cvt|120|km/h|mph knot}}.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1522web.txt|date=13 September 2022|access-date=13 September 2022|archive-date=13 September 2022|title=Typhoon 15W (Merbok) Warning #13 Issued 13/2100Z|website=JTWC |archive-url=https://ghostarchive.org/archive/P2zTz |language=en}} On September 15, the JTWC gave its final bulletin on Merbok, noting that it had moved away from habitable areas.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1522web.txt|archive-url=https://ghostarchive.org/archive/Ev5Vk|date=15 September 2022|access-date=15 September 2022|archive-date=15 September 2022|title=Typhoon Merbok 15W Warning #18 Final bulletin Issued 15/0300Z|website=JTWC|language=en}}

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.{{cite website |title=Typhoon Merbok, fueled by unusually warm Pacific Ocean, pounded Alaska’s vulnerable coastal communities at a critical time |last1= Thoman |first1= Rick |url= https://theconversation.com/typhoon-merbok-fueled-by-unusually-warm-pacific-ocean-pounded-alaskas-vulnerable-coastal-communities-at-a-critical-time-190898 |publisher= The Conversation}} It crossed the islands, entering the Bering Sea late on {{nowrap|September 15 (HDT)}} as it maintained hurricane-force winds and reached its minimum central barometric pressure of {{convert|937|mbar|inHg|abbr=on|sigfig=4}} 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.{{cite website |title= USGS aids storm response to Extratropical Typhoon Merbok in Alaska |last1= Hayden |first1= Maya |url=https://www.usgs.gov/centers/pcmsc/news/usgs-aids-storm-response-extratropical-typhoon-merbok-alaska |publisher= USGS}} Governor Mike Dunleavy declared a state of emergency in the region before the cyclone hit.{{Cite news |last1=Fernando |first1=Christine |last2=Thornton |first2=Claire |title='Angry sea': Huge storm floods roads, homes in Alaska as governor declares disaster |date=September 17, 2022 |url=https://www.usatoday.com/story/news/nation/2022/09/17/alaska-expects-floods-typhoon-merboks-remnants/10410998002/ |access-date=September 18, 2022 |work=USA Today |language=en-US}} Water levels in Unalakleet peaked at around {{cvt|12.5|ft}}, 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.{{cite report |title=Merbok: A Bering Sea storm & coastal flooding event |last1=Erickson |first1=Caroline |last2= Thoman |first2= Rick |url= https://uaf-accap.org/wp-content/uploads/2024/06/2022-Merbok.pdf |publisher= Alaska Center for Climate Assessment and Policy}} The typhoon also destroyed {{convert|1,000|mi|km|abbr=on}} of coastline, devastating multiple fish camps in western Alaska.[https://greaternw.org/news/alaskan-typhoon-damages-1000-miles-of-coastline-creates-deep-generational-loss-of-culture/ Alaskan typhoon damages 1,000 miles of coastline, creates deep generational loss of culture], Great NW News, October 5, 2022. Retrieved April 27, 2025 Despite the widespread coastal flooding, no injuries were reported.{{cite news|title=Former Typhoon Merbok blasts western Alaska with historic storm surge, 90 mph wind and 50-foot seas |url=https://uk.news.yahoo.com/former-typhoon-merbok-blast-western-125310460.html?guccounter=1&guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&guce_referrer_sig=AQAAAEyIwyKozHcnIRdUC1Svp_eTQnG5JAHEgj2BP2a4ySz-wig4FWrpWtcFe4L8VicOFfNeSY4xWZPFIC397tLE65hYArDb4dOHRvODQK-20R5vszNE4CNDddEr6hE90ULT-DAxPB9dIvXSkVRmEsXdi8827BMgdIA7y4IncJ2EaMit |date=17 September 2022 |publisher=Fox News |access-date=18 September 2022 |via=Yahoo! News}}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Image=Nanmadol 2022-09-16 1700Z (Black Marble Nighttime).jpg

|Track=Nanmadol 2022 track.png

|Formed=September 12

|Dissipated=September 19

|10-min winds=105

|1-min winds=135

|Pressure=910

}}{{Main article|Typhoon Nanmadol (2022)}}

On 06:00 UTC of September 9, the JMA briefly tracked a weak tropical depression to the east of Iwo To, Japan.{{cite web |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-url=https://archive.today/20220909083242/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |url-status=dead |archive-date=2022-09-09 |title=Archive.ph }} 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 {{cvt|262|nmi}} southwest of Iwo-To.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1622web.txt|archive-url=https://ghostarchive.org/archive/6kmDY|date=12 September 2022|access-date=12 September 2022|archive-date=12 September 2022|title=Tropical depression 16W (Sixteen) Warning #01 Issued 12/2100Z|website=JTWC|language=en}} On the same day, the JMA and the JTWC upgraded the system to a tropical storm, with the JMA assigning it the name Nanmadol.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1622web.txt|archive-url=https://ghostarchive.org/archive/hHT69|date=13 September 2022|access-date=13 September 2022|archive-date=13 September 2022|title=Tropical storm 16W (Nanmadol) Warning #05 Issued 13/2100Z|website=JTWC|language=en}}{{cite web|url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|archive-url=https://ghostarchive.org/archive/lVgEp|date=13 September 2022|access-date=13 September 2022|archive-date=13 September 2022|title=Bulletin released of typhoon Muifa, typhoon Merbok and tropical storm Nanmadol Issued 13/2100Z|website=Japan Meteorological Agency|language=en}} The storm then reached typhoon status on September 15.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1622web.txt|archive-url=https://ghostarchive.org/archive/IgNPS|archive-date=15 September 2022|date=15 September 2022|access-date=15 September 2022|title=Typhoon Nanmadol (16W) Warning #12 Issued 15/1500Z|website=JTWC|language=en}} Nanmadol rapidly intensified into a very strong typhoon, according to the JTWC's thirteenth bulletin.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1622web.txt|archive-url=https://ghostarchive.org/archive/jPPaA|date=16 September 2022|access-date=16 September 2022|archive-date=16 September 2022|title=Typhoon Nanmadol (16W) Warning #13 Issued 16/0000Z|website=JTWC|language=en}} Nanmadol then entered the PAGASA's Philippine Area of Responsibility at 09:40 UTC on September 16, and was given the name Josie,{{cite web |title=Watch |url=https://www.facebook.com/watch/?v=604804811281104&ref=sharing |access-date=16 September 2022 |via=Facebook}}{{Cite news |title=Typhoon Josie enters PAR, no landfall seen |url=https://www.rappler.com/nation/weather/typhoon-josie-southwest-monsoon-pagasa-forecast-september-16-2022-2pm/ |website=rappler.com |last=Arceo |first=Acor |date=16 September 2022 |access-date=16 September 2022}} however, it quickly left the PAR, just over four hours later, at 14:00 UTC on the same day.{{cite web |title=Watch |url=https://facebook.com/.watch/fAi3HTtW5V/ |access-date=16 September 2022 |via=Facebook}} A system pressure of 910 hPa (mbar) was then recorded, the lowest so far this season.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1622web.txt|archive-url=https://ghostarchive.org/archive/ROOjQ|date=16 September 2022|access-date=16 September 2022|archive-date=16 September 2022|title=Super typhoon Nanmadol (16W) Warning #17 Issued 16/2100Z|website=JTWC|language=en}}{{Failed verification|date=September 2022|reason=No mention of 910 hPa}} When it made landfall in southern Japan, the typhoon was downgraded to Category 3-equivalent status upon reaching Kyushu Islands.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1622web.txt|archive-url=https://ghostarchive.org/archive/AwN17|date=18 September 2022|access-date=18 September 2022|archive-date=18 September 2022|title=Typhoon Nanmadol (16W) Warning #22 Issued 18/0300Z|website=JTWC|language=en}} Upon directly impacting the country, it was downgraded again to Category 1-equivalent status.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1622web.txt|archive-url=https://ghostarchive.org/archive/AwN17|date=18 September 2022|access-date=18 September 2022|archive-date=18 September 2022|title=Typhoon Nanmadol (16W) Warning #25 Issued 18/2100Z|website=JTWC|language=en}} 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|date=September 2022}}

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.{{cite news |url=https://www.bbc.com/news/world-asia-62938608 |title=Japan storm: Millions told to evacuate as Typhoon Nanmadol makes landfall |publisher=BBC News |date=September 18, 2022 }} 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.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1622web.txt|archive-url=https://ghostarchive.org/archive/uqYPQ|date=19 September 2022|access-date=19 September 2022|archive-date=19 September 2022|title=Tropical storm Nanmadol (16W) Warning #26 Issued 19/0300Z|website=JTWC|language=en}}{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1622prog.txt|archive-url=https://ghostarchive.org/archive/N2iox|date=19 September 2022|access-date=19 September 2022|archive-date=19 September 2022|title=Tropical storm Nanmadol (16W) Prognostic Reasoning Warning #26 Issued 19/0300Z|website=JTWC|language=en}}{{cite web|url=https://www.bloomberg.com/news/articles/2022-09-19/powerful-typhoon-pelts-japan-tokyo-under-flood-advisory?srnd=all|date=19 September 2022|access-date=19 September 2022|title=At Least Two Killed in Japan Typhoon, Tokyo Under Flood Advisory

|website=Bloomberg|language=en}} 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.{{cite web |url=https://m.koreaherald.com/view.php?ud=20220919000125 |title=1 person injured, hundreds evacuated as Typhoon Nanmadol nears |date=September 19, 2022 |access-date=19 September 2022|website=Korea Herald}}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=September 20

|Dissipated=September 23

|Image=Talas 2022-09-23 0430Z.jpg

|Track=Talas 2022 track.png

|10-min winds=35

|1-min winds=35

|Pressure=1000

}}

{{main|Tropical Storm Talas (2022)}}

On September 20, a disturbance turned into a tropical depression according to the JMA.{{cite web|url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|archive-url=https://ghostarchive.org/archive/Z2HrK|title=Bulletin released of Tropical depression (Invest 94W) Issued 20/2100Z|website=Japan Meteorological Agency|language=en|date=20 September 2022|access-date=20 September 2022|archive-date=20 September 2022}} The JTWC reported that the low pressure encountered favorable environments for intensification by warm waters and low wind shear.{{cite web |url=https://www.metoc.navy.mil/jtwc/products/wp9422web.txt |archive-url=https://ghostarchive.org/archive/b289L |date=20 September 2022 |access-date=20 September 2022 |archive-date=20 September 2022 |title=Tropical cyclone formation alert WTPN21 (Invest 94W) Issued at 21/0130Z |website=JTWC |language=en}} The next day, the JTWC designated the system as 17W as it was upgraded into a tropical depression.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1722prog.txt|archive-url=https://ghostarchive.org/archive/pmroQ|date=21 September 2022|access-date=22 September 2022|archive-date=21 September 2022|title=Tropical depression 17W (Seventeen) Warning #01 Issued 21/2100Z|website=JTWC|language=en}} 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.{{cite web|archive-url=https://ghostarchive.org/archive/gcnM7|url=https://www.metoc.navy.mil/jtwc/products/wp1722web.txt|date=23 September 2022|access-date=23 September 2022|archive-date=23 September 2022|title=Tropical storm 17W (Talas) Warning #06 Issued 23/0300Z|website=JTWC|language=en}} When it made landfall in southern Japan, it was downgraded to a tropical depression according to the seventh JTWC bulletin.{{cite web|date=23 September 2022|access-date=23 September 2022|archive-date=23 September 2022|title=Tropical depression 17W (Talas) Warning #07 Issued 21/0900Z|website=JTWC|language=en|url=https://www.metoc.navy.mil/jtwc/products/wp1722web.txt|archive-url=https://ghostarchive.org/archive/JWnV2}}

A {{cvt|10|-|12|cm}} total hourly, total {{cvt|30|-|42|cm}} 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.{{Cite web |date=2022-09-25 |title=Three killed as storm lashes central Japan |url=https://www.japantimes.co.jp/news/2022/09/25/national/storm-talas-approaches-japan/ |access-date=2022-09-27 |website=The Japan Times |language=en-US}}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=September 21

|Dissipated=September 29

|Image=Noru 2022-09-24 2330Z.jpg

|Track=Noru 2022 path.png

|10-min winds=95

|1-min winds=145

|Pressure=940

}}{{Main article|Typhoon Noru}}

On September 21, a disturbance developed into tropical depression near the Philippines, according to the JMA.{{cite web|url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|archive-url=https://ghostarchive.org/archive/zEOrm|date=21 September 2022|access-date=21 September 2022|archive-date=21 September 2022|title=Bulletin released of tropical depressions (94W and 95W) Issued 21/1500Z|website=Japan Meteorological Agency|language=en}} 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.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|archive-url=https://ghostarchive.org/archive/uSGr2|date=21 September 2022|access-date=21 September 2022|archive-date=21 September 2022|title=Current significant tropical weather advisories ABPW10 (Western/South Pacific Ocean) Reissued at 21/1530Z (Invest 95W)|website=JTWC|language=en}} Hours later, the JTWC upgraded the system into a tropical depression, designating it as 18W.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1822web.txt|archive-url=https://ghostarchive.org/archive/8Zfh9|date=22 September 2022|access-date=22 September 2022|archive-date=22 September 2022|title=Tropical depression 18W (Eighteen) Warning #01 Issued 22/0300Z|website=JTWC|language=en}} The PAGASA then followed suit on 00:00 UTC of September 22, and the tropical depression was assigned the name Karding.{{cite tweet |author=ABS-CBN News |author-link=ABS-CBN News |user=ABSCBNNews |number=1572756161996410880 |date=September 22, 2022 |title=JUST IN: The low pressure area east of Central Luzon has developed into Tropical Depression #KardingPH, @dost_pagasa said in its 8 a.m. bulletin Thursday. #WeatherPatrol Story to follow on https://t.co/pCyTuluM8U. https://t.co/Zbobjz1t81 |language=en |access-date=January 14, 2023 |archive-url=https://web.archive.org/web/20220929031546/https://twitter.com/abscbnnews/status/1572756161996410880 |archive-date=September 29, 2022 |url-status=live}} A few hours later, the system reached tropical storm intensity and the JMA assigned it the name Noru (2216).{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1822prog.txt|archive-url=https://ghostarchive.org/archive/9mBFh|date=22 September 2022|access-date=22 September 2022|archive-date=22 September 2022|title=Tropical storm 18W (Eighteen) Warning #04 Issued 22/2100Z|website=JTWC|language=en}} On 24 September, Noru entered the Philippine area of responsibility and reached typhoon intensity.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1822web.txt|archive-url=https://archive.today/20220924144249/https://www.metoc.navy.mil/jtwc/products/wp1822web.txt|date=24 September 2022|access-date=24 September 2022|archive-date=24 September 2022|title=Typhoon 17W (Noru) Warning #11 Issued 24/1500Z|website=JTWC|language=en}} Noru then underwent explosive intensification, during which, according to the JTWC, Noru's 1-minute sustained winds increased by {{convert|165|km/h|mph|abbr=on|round=5}}.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1822prog.txt|archive-url=https://ghostarchive.org/archive/tZXQT|date=24 September 2022|access-date=24 September 2022|archive-date=24 September 2022|title=Super typhoon 17W (Noru) Warning #12 Prognostic Reasoning Issued 24/2100Z|website=JTWC|language=en}} At 00:00 UTC, Noru was classified as a Category-5 super typhoon.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1822web.txt|archive-url=https://ghostarchive.org/archive/BEmLh|date=24 September 2022|access-date=24 September 2022|archive-date=24 September 2022|title=Super typhoon 17W (Noru) Warning #12 Issued 24/2100Z|website=JTWC|language=en}} 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.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1822web.txt|archive-url=https://ghostarchive.org/archive/YQNer|date=25 September 2022|access-date=25 September 2022|archive-date=25 September 2022|title=Typhoon 17W (Noru) Warning #15 Issued 25/1500Z|website=JTWC|language=en}} At 8:20pm PHT, Noru struck Dingalan, Aurora as a typhoon according to PAGASA.{{Cite web |date=2022-09-25 |title=Karding makes first landfall in Quezon, second in Aurora |url=https://www.rappler.com/nation/weather/super-typhoon-karding-pagasa-forecast-september-25-2022-8pm/ |access-date=2022-09-28 |website=RAPPLER |language=en-US}} The terrain of the Sierra Madre mountain range weakened Noru as it passed through Central Luzon.{{Cite news |last=Peña |first=Kurt Dela |date=2022-09-28 |title=Sierra Madre stands up to Karding, but needs protection vs the humans it saves |url=https://newsinfo.inquirer.net/1672040/sierra-madre-stands-up-to-karding-but-needs-protection-vs-the-humans-it-saves |access-date=2022-09-28 |newspaper=Philippine Daily Inquirer |language=en}} Noru then slightly re-intensified in the West Philippine Sea, leaving the PAGASA's area of responsibility on Monday morning.{{Cite web |date=2022-09-26 |title=Typhoon Karding exits PAR after leaving trail of destruction |url=https://www.rappler.com/nation/weather/typhoon-karding-pagasa-forecast-september-26-2022-11pm/ |access-date=2022-09-28 |website=RAPPLER |language=en-US}} 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).

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=September 25

|Dissipated=September 29

|Image=Kulap 2022-09-28 0315Z.jpg

|Track=Kulap 2022 track.png

|10-min winds=60

|1-min winds=75

|Pressure=965

}}

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.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp9622web.txt|archive-url=https://archive.today/20220925030736/https://www.metoc.navy.mil/jtwc/products/wp9622web.txt|date=25 September 2022|access-date=25 September 2022|archive-date=25 September 2022|title=Current Northwest Pacific/North Indian Ocean Tropical Systems Tropical Cyclone Formation Alert WTPN21 Issued at 24/2230Z (Invest 96W)|website=JTWC|language=en}} The next day, JMA classified the system as a tropical depression.{{cite web|url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|archive-url=https://ghostarchive.org/archive/LtbIP|date=21 September 2022|access-date=22 September 2022|archive-date=21 September 2022|title=Bulletin released of typhoon Noru and tropical depression (Seventeen) Issued 25/1500Z|website=Japan Meteorological Agency|language=en}} Hours later, the JTWC followed suit, and designated him 19W.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp1922web.txt|archive-url=https://ghostarchive.org/archive/0r6cP|date=25 September 2022|access-date=29 September 2022|archive-date=25 September 2022|title=Tropical depression 19W (Nineteen) Warning #01 Issued at 25/2100Z|website=JTWC|language=en}}

The next day, the cyclone intensified and the JTWC in its second bulletin, classified it as a "tropical storm".{{cite web |url=https://www.metoc.navy.mil/jtwc/products/wp1922web.txt |archive-url=https://ghostarchive.org/archive/qeHxC |website=JTWC|date=26 September 2022|access-date=26 September 2022|archive-date=26 September 2022|title=Tropical storm Kulap (19W) Warning #02 26/0300Z |language=en}} The JMA followed suit and called it Kulap.{{cite web |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-url=https://ghostarchive.org/archive/avc9L |archive-date=26 September 2022 |website=Japan Meteorological Agency|access-date=26 September 2022|date=26 September 2022|title=Bulletin released of tropical storm Kulap (November 26, 2022)|language=en}} The JMA quickly classified it as a "severe tropical storm" but the JTWC went further and upgraded it to a Category 1 typhoon.{{cite web |url=https://www.metoc.navy.mil/jtwc/products/wp1922web.txt |archive-url=https://archive.today/20220929030926/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq30.rjtd..txt |archive-date=29 September 2022 |website=JTWC|date=28 September 2022|access-date=28 September 2022|title=Typhoon Kulap (19W) Warning #12 Issued 28/1500|language=en}}{{cite web |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-url=https://ghostarchive.org/archive/kq3Ks |archive-date=27 September 2022 |website=Japan Meteorological Agency|date=27 September 2022|access-date=27 September 2022|title=Bulletin released of severe tropical storm Kulap (September 27, 2022)|language=en}} 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.{{cite web |title=Severe tropical storm Kulap (19W) Prognostic Resoaning Warning #16 |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-url=https://ghostarchive.org/archive/iSi6d|archive-date=29 September 2022 |website=JTWC|date=29 September 2022|access-date=29 September 2022|language=en}}{{cite web |title=Bulletin released of severe tropical storm Kulap (September 29, 2022)|url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-url=https://archive.today/20220929031249/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|archive-date=29 September 2022 |website=Japan Meteorological Agency}} 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.{{cite web |url=https://www.metoc.navy.mil/jtwc/products/wp1922web.txt |archive-url=https://ghostarchive.org/archive/udMdq |archive-date=29 September 2022 |website=JTWC|date=29 September 2022|access-date=29 September 2022|title=Current Northwest Pacific/North Indian Ocean Tropical Systems Issued at 29/0600Z (Typhoon Kulap of the tropical storm Roke)|language=en}}{{cite web |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-url=https://archive.today/20220929090631/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|archive-date=29 September 2022 |website=Japan Meteorological Agency|date=29 September 2022|access-date=29 September 2022|title=Bulletin released of developing low (ex-Severe tropical storm Kulap)|language=en}}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=September 28

|Dissipated=October 1

|Image=Roke 2022-09-29 0435Z.jpg

|Track=Roke 2022 track.png

|10-min winds=70

|1-min winds=90

|Pressure=975

}}

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.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp2022web.txt|archive-url=https://ghostarchive.org/archive/h1H2D|title=SIGNIFICANT TROPICAL WEATHER ADVISORY FOR THE WESTERN AND SOUTH PACIFIC OCEANS (Tropical depression 20W) Issued 28/0930Z|website=JTWC|language=en|date=28 September 2022|access-date=3 October 2022|archive-date=28 September 2022}} 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.{{cite web|archive-url=https://ghostarchive.org/archive/ldbtZ|url=https://www.metoc.navy.mil/jtwc/jtwc.html|title=Tropical storm 20W (Roke) Warning #02 Issued 28/1500Z|website=JTWC|language=en|date=28 September 2022|access-date=3 October 2022|archive-date=28 September 2022}} Two days later, the JTWC and JMA classified it as a Category 1 typhoon,{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp2022web.txt|archive-url=https://ghostarchive.org/archive/Maa7q|title=Typhoon 20W (Roke) Warning #07 Issued 29/1500Z|website=JTWC|language=en|date=29 September 2022|access-date=3 October 2022|archive-date=29 September 2022}} The intensification did not last long and Roke was downgraded to a tropical storm.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp2022web.txt|archive-url=https://ghostarchive.org/archive/fZ69g|date=30 September 2022|access-date=3 October 2022|archive-date=30 September 2022|title=Tropical storm 20W (Roke) Warning #11 Issued 30/2100Z|website=JTWC|language=en}} Having the same fate as its predecessor Kulap, the JTWC released a final bulletin in which Roke had been downgraded to an extratropical cyclone.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp2022web.txt|archive-url=https://ghostarchive.org/archive/0VEsc|date=2 October 2022|access-date=3 October 2022|archive-date=2 October 2022|title=Tropical storm 20W (Roke) Warning #16 Final Warning Issued 02/0300Z|website=JTWC|language=en}} However, the cyclone intensified into a subtropical storm according to the JTWC's special bulletin. On October 1, it weakened into a subtropical depression.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|archive-url=https://ghostarchive.org/archive/C59PR|title=Significant Tropical Weather Advisory for the Western and South Pacific Oceasns Reissued/030600Z (Remnants of subtropical storm Roke 20W)|date=3 October 2022|access-date=3 October 2022|archive-date=3 October 2022|website=JTWC|language=en}}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=October 11

|Dissipated=October 12

|Image=Maymay 2022-10-11 0500Z.jpg

|Track=Maymay 2022 track.png

|10-min winds=30

|1-min winds=

|Prewinds=<

|Pressure=1002

}}

On October 9, the JTWC started to monitor a persisting area of convection with a poorly-defined circulation at approximately {{cvt|645|nmi}} to the east of Manila, Philippines.{{cite report|title=Significant Tropical Weather Advisory for the Western and South Pacific Oceans|url=https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|publisher=Joint Typhoon Warning Center|date=October 9, 2022|archive-url=https://web.archive.org/web/20220923070157/https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|archive-date=September 23, 2022}} [https://wiki.chlod.net/jtwc/text/2022-10-09-0650-abpwweb.txt Alt URL] Under a favorable environment of warm sea surface temperatures, low to moderate wind shear, and strong poleward outflow,{{cite report|title=Significant Tropical Weather Advisory for the Western and South Pacific Oceans|url=https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|publisher=Joint Typhoon Warning Center|date=October 10, 2022|archive-url=https://web.archive.org/web/20220923070157/https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|archive-date=September 23, 2022}} [https://wiki.chlod.net/jtwc/text/2022-10-10-0600-abpwweb.txt Alt URL] the system continued to organize before PAGASA upgraded it as a tropical depression, naming it as Maymay, late on October 10.{{cite report|title=Tropical Depression "Maymay" Tropical Cyclone Bulletin No. 1|url=https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin/TCB%231_maymay.pdf|publisher=PAGASA|date=October 10, 2022|archive-url=https://web.archive.org/web/20221011040825/https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin/TCB%231_maymay.pdf|archive-date=October 11, 2022}} [https://archive.org/download/pagasa-22-TC13/PAGASA_22-TC13_Maymay_TCB%2301.pdf Alt URL] The JMA subsequently followed suit by the next day.{{cite web|title=WWJP27 RJTD 110000|url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|publisher=Japan Meteorological Agency|date=October 11, 2022|archive-url=https://archive.today/20221011052529/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|archive-date=October 11, 2022}} 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.{{cite report|title=Tropical Cyclone Formation Alert (Invest 98W)|url=https://www.metoc.navy.mil/jtwc/products/wp9822web.txt|publisher=Joint Typhoon Warning Center|date=October 11, 2022|archive-url=https://archive.today/20221011053227/https://www.metoc.navy.mil/jtwc/products/wp9822web.txt|archive-date=October 11, 2022}} However, the storm's convective structure was detached from the main center due to a TUTT cell to the northeast of it,{{cite report|title=Tropical Cyclone Formation Alert (Invest 98W) Reissued|url=https://www.metoc.navy.mil/jtwc/products/wp9822web.txt|publisher=Joint Typhoon Warning Center|date=October 12, 2022|archive-url=https://archive.today/20221012095717/https://www.metoc.navy.mil/jtwc/products/wp9822web.txt|archive-date=October 12, 2022}} which made the storm weaken as it moved northwestwards, prompting the JMA to downgrade Maymay into a low-pressure area on October 12.{{cite web|title=WWJP27 RJTD 121200|url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|publisher=Japan Meteorological Agency|date=October 12, 2022|archive-url=https://archive.today/20221012151955/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|archive-date=October 12, 2022}} The PAGASA subsequently followed suit late on the same day,{{cite report|title=Low Pressure Area (formerly "Maymay") Tropical Cyclone Bulletin No. 9F|url=https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin/TCB%239_maymay.pdf|publisher=PAGASA|date=October 12, 2022}}{{dead link|date=August 2023|bot=medic}}{{cbignore|bot=medic}} [https://archive.org/download/pagasa-22-TC13/PAGASA_22-TC13_Maymay_TCB%2309-FINAL.pdf Alt URL] and JTWC cancelled their TCFA by October 13.{{cite report|title=Tropical Cyclone Formation Alert (Invest 98W) Cancellation|url=https://www.metoc.navy.mil/jtwc/products/wp9822web.txt|publisher=Joint Typhoon Warning Center|date=October 13, 2022|archive-url=https://archive.today/20221013032717/https://www.metoc.navy.mil/jtwc/products/wp9822web.txt|archive-date=October 13, 2022}}

Though short-lived, Maymay killed two people in Cagayan, Philippines.{{Cite news |date=October 13, 2022 |title='Maymay' leaves 2 dead in Cagayan |last=Recuenco |first=Aaron |url=https://mb.com.ph/2022/10/13/maymay-leaves-2-dead-in-cagayan/ |access-date=October 18, 2022 |newspaper=Manila Bulletin |language=en}} 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.{{Cite news |last=Basa Iñigo |first=Liezle |title=Cagayan sustains P533-M damage from 'Maymay' |url=https://mb.com.ph/2022/10/17/cagayan-sustains-p533-m-damage-from-maymay/ |access-date=2022-10-17 |newspaper=Manila Bulletin |language=en}}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=October 12

|Dissipated=October 14

|Image=21W 2022-10-14 0300Z.jpg

|Track=21W 2022 track.png

|10-min winds=30

|1-min winds=40

|Pressure=1002

}}

On October 12, the JTWC started to monitor an organizing area of convection with a fully obscured low-level center at approximately {{cvt|325|nmi}} to the west of Saipan.{{cite report|title=Significant Tropical Weather Advisory for the Western and South Pacific Oceans (Reissued)|url=https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|publisher=Joint Typhoon Warning Center|date=October 12, 2022|archive-url=https://web.archive.org/web/20220923070157/https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|archive-date=September 23, 2022}} [https://wiki.chlod.net/jtwc/text/2022-10-12-0350-abpwweb.txt Alt URL] 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,{{cite report|title=Tropical Cyclone Formation Alert (Invest 99W)|url=https://www.metoc.navy.mil/jtwc/products/wp9922web.txt|publisher=Joint Typhoon Warning Center|date=October 12, 2022|archive-url=https://archive.today/20221012095726/https://www.metoc.navy.mil/jtwc/products/wp9922web.txt|archive-date=October 12, 2022}} 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.{{cite report|title=Prognostic Reasoning for Tropical Depression 21W (Twentyone) Warning Nr 001|url=https://tgftp.nws.noaa.gov/data/raw/wd/wdpn31.pgtw..txt|publisher=Joint Typhoon Warning Center|date=October 12, 2022|archive-url=https://archive.today/20221012144532/https://tgftp.nws.noaa.gov/data/raw/wd/wdpn31.pgtw..txt|archive-date=October 12, 2022}} The JMA followed suit three hours later.{{cite web|title=WWJP27 RJTD 121800|url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|publisher=Japan Meteorological Agency|date=October 12, 2022|archive-url=https://archive.today/20221012202956/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|archive-date=October 12, 2022}} The system soon became severely sheared by the next day as wind shear increased dramatically while it continued moving eastward,{{cite report|title=Prognostic Reasoning for Tropical Depression 21W (Twentyone) Warning Nr 003|url=https://tgftp.nws.noaa.gov/data/raw/wd/wdpn31.pgtw..txt|publisher=Joint Typhoon Warning Center|date=October 13, 2022|archive-url=https://archive.today/20221013032638/https://tgftp.nws.noaa.gov/data/raw/wd/wdpn31.pgtw..txt|archive-date=October 13, 2022}} before it got embedded into a convergent outer boundary of a deep TUTT cell positioned towards the northwest,{{cite report|title=Prognostic Reasoning for Tropical Depression 21W (Twentyone) Warning Nr 006|url=https://tgftp.nws.noaa.gov/data/raw/wd/wdpn31.pgtw..txt|publisher=Joint Typhoon Warning Center|date=October 13, 2022|archive-url=https://archive.today/20221013204242/https://tgftp.nws.noaa.gov/data/raw/wd/wdpn31.pgtw..txt|archive-date=October 13, 2022}} helping the storm re-organize and intensify into a tropical storm by October 14.{{cite report|title=Prognostic Reasoning for Tropical Storm Twentyone (21W) Warning Nr 007|url=https://www.wis-jma.go.jp/d/o/PGTW/Alphanumeric/Warning/Tropical_cyclone/20221014/030000/A_WDPN31PGTW140300_C_RJTD_20221014023617_38.txt|publisher=Joint Typhoon Warning Center|date=October 14, 2022|archive-url=https://archive.today/20221014081028/https://www.wis-jma.go.jp/d/o/PGTW/Alphanumeric/Warning/Tropical_cyclone/20221014/030000/A_WDPN31PGTW140300_C_RJTD_20221014023617_38.txt|archive-date=October 14, 2022}} 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,{{cite report|title=Prognostic Reasoning for Tropical Storm Twentyone (21W) Warning Nr 009|url=https://tgftp.nws.noaa.gov/data/raw/wd/wdpn31.pgtw..txt|publisher=Joint Typhoon Warning Center|date=October 14, 2022|archive-url=https://archive.today/20221014143730/https://tgftp.nws.noaa.gov/data/raw/wd/wdpn31.pgtw..txt|archive-date=October 14, 2022}} and it soon opened up into a tropical wave later the same day.{{cite report|title=Tropical Storm Twentyone (21W) Warning Nr 010A Corrected|url=https://www.metoc.navy.mil/jtwc/products/wp2122web.txt|publisher=Joint Typhoon Warning Center|date=October 14, 2022|archive-url=https://archive.today/20221015073750/https://www.metoc.navy.mil/jtwc/products/wp2122web.txt|archive-date=October 15, 2022}}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=October 13

|Dissipated=October 15

|Image=Sonca 2022-10-14 0620Z.jpg

|Track=Sonca 2022 track.png

|10-min winds=35

|1-min winds=35

|Pressure=998

}}{{main|Tropical Storm Sonca (2022)}}

Late on October 11, the JTWC started to monitor a scattered area of convection with a poorly-organized broad low-level center at approximately {{cvt|150|nmi}} to the west-southwest of Manila, Philippines.{{cite report|title=Significant Tropical Weather Advisory for the Western and South Pacific Oceans (Reissued)|url=https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|publisher=Joint Typhoon Warning Center|date=October 11, 2022|archive-url=https://web.archive.org/web/20220923070157/https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|archive-date=September 23, 2022}} [https://wiki.chlod.net/jtwc/text/2022-10-11-2020-abpwweb.txt Alt URL] 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.{{cite report|title=Significant Tropical Weather Advisory for the Western and South Pacific Oceans (Reissued)|url=https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|publisher=Joint Typhoon Warning Center|date=October 12, 2022|archive-url=https://web.archive.org/web/20220923070157/https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|archive-date=September 23, 2022}} [https://wiki.chlod.net/jtwc/text/2022-10-12-1520-abpwweb.txt Alt URL] Nonetheless, the JMA upgraded the system into a tropical depression on October 13.{{cite report|title=RSMC Tropical Cyclone Prognostic Reasoning No. 1 for TD located at 12.1N 114.4E|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt|publisher=Japan Meteorological Agency|date=October 13, 2022|archive-url=https://archive.today/20221013032616/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt|archive-date=October 13, 2022}} 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.{{cite report|title=Tropical Cyclone Formation Alert (Invest 90W)|url=https://www.metoc.navy.mil/jtwc/products/wp9022web.txt|publisher=Joint Typhoon Warning Center|date=October 13, 2022|archive-url=https://archive.today/20221013153452/https://www.metoc.navy.mil/jtwc/products/wp9022web.txt|archive-date=October 13, 2022}} By the next day, the JTWC initiated advisories on the storm, designating it as 22W.{{cite report|title=Prognostic Reasoning for Tropical Depression 22W (Twenty-two) Warning Nr 001|url=https://www.wis-jma.go.jp/d/o/PGTW/Alphanumeric/Warning/Tropical_cyclone/20221014/030000/A_WDPN32PGTW140300_C_RJTD_20221014030217_87.txt|publisher=Joint Typhoon Warning Center|date=October 14, 2022|archive-url=https://archive.today/20221014081211/https://www.wis-jma.go.jp/d/o/PGTW/Alphanumeric/Warning/Tropical_cyclone/20221014/030000/A_WDPN32PGTW140300_C_RJTD_20221014030217_87.txt|archive-date=October 14, 2022}} Moving westward, the storm intensified into a tropical storm six hours later, with the JMA naming it as Sonca.{{cite report|title=RSMC Tropical Cyclone Prognostic Reasoning No. 6 for TS 2219 Sonca (2219)|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq30.rjtd..txt|publisher=Japan Meteorological Agency|date=October 14, 2022|archive-url=https://archive.today/20221014081120/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq30.rjtd..txt|archive-date=October 14, 2022}} Sonca failed to intensify further as its center remained exposed, with deep convection displaced to the west due to strong wind shear,{{cite report|title=Prognostic Reasoning for Tropical Storm 22W (Sonca) Warning Nr 003|url=https://tgftp.nws.noaa.gov/data/raw/wd/wdpn32.pgtw..txt|publisher=Joint Typhoon Warning Center|date=October 14, 2022|archive-url=https://archive.today/20221014143202/https://tgftp.nws.noaa.gov/data/raw/wd/wdpn32.pgtw..txt|archive-date=October 14, 2022}} 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.{{cite report|title=Tropical Storm 22W (Sonca) Warning Nr 004|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpn32.pgtw..txt|publisher=Joint Typhoon Warning Center|date=October 14, 2022|archive-url=https://archive.today/20221014205048/https://tgftp.nws.noaa.gov/data/raw/wt/wtpn32.pgtw..txt|archive-date=October 14, 2022}} The JMA followed suit by October 15, as Sonca weakened into a tropical depression.{{cite report|title=RSMC Tropical Cyclone Advisory for TD downgraded from TS 2219 Sonca (2219)|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt|publisher=Japan Meteorological Agency|date=October 15, 2022|archive-url=https://archive.today/20221015072706/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt|archive-date=October 15, 2022}}

As Sonca moved inland, it brought heavy rainfall to central Vietnam, with {{cvt|700|mm}} of rain fell in Da Nang during a 24-hour period on {{nowrap|October 14–15}}; this resulted in major flooding throughout the region, with 10 fatalities reported.{{cite news |title=Central Vietnam flooding death toll rises to 10 |url=https://e.vnexpress.net/news/news/central-vietnam-flooding-death-toll-rises-to-10-4524156.html |date=October 16, 2022 |newspaper=VnExpress |location=Hanoi, Vietnam |access-date=October 18, 2022 |language=en}} Initial estimated economic losses in Da Nang City caused by Sonca's heavy precipitation are around 1.48 trillion VND (US$60.8 million).{{cite news |title=Đà Nẵng bị thiệt hại hơn 1.486 tỷ đồng do trận ngập lụt lịch sử |url=https://baodanang.vn/channel/5399/202210/da-nang-bi-thiet-hai-hon-1486-ty-dong-do-tran-ngap-lut-lich-su-3926577/ |date=October 19, 2022 |newspaper=baodanang.vn |location=Danang, Vietnam |access-date=October 19, 2022 |language=vi}}{{cite news |title=Đà Nẵng thiệt hại gần 1.500 tỷ đồng trong bão số 5 |url=http://daidoanket.vn/da-nang-thiet-hai-gan-1500-ty-dong-trong-bao-so-5-5699838.html |date=October 20, 2022 |newspaper=daidoanket.vn |access-date=October 20, 2022 |language=vi}}{{cite news |title=Đà Nẵng thiệt hại gần 1.500 tỷ đồng do mưa lũ |url=https://vnexpress.net/da-nang-thiet-hai-gan-1-500-ty-dong-do-mua-lu-4525539.html |date=October 19, 2022 |newspaper=VnExpress |access-date=October 20, 2022 |language=vi}} 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.{{cite news |title=Thừa Thiên Huế thiệt hại hơn 337 tỉ đồng do mưa lũ |url=https://tuoitre.vn/thua-thien-hue-thiet-hai-hon-337-ti-dong-do-mua-lu-20221020151045351.htm |date=October 20, 2022 |newspaper=Tuổi Trẻ |access-date=October 23, 2022 |language=vi}} Overall, damages inflicted by Sonca were 2.4 trillion VND (US$101.5 million).

{{clear}}

{{Infobox typhoon small

|Basin=WPac

|Formed=October 14

|Dissipated=October 20

|Image=Nesat 2022-10-17 0540Z.jpg

|Track=Nesat 2022 track.png

|10-min winds=75

|1-min winds=90

|Pressure=965

}}

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.{{Cite web |date=2022-10-13 |title=Tropical Depression Neneng enters PAR, seen to head for extreme Northern Luzon |url=https://www.rappler.com/nation/weather/tropical-depression-neneng-pagasa-forecast-october-13-2022-5pm/ |access-date=2022-10-18 |website=RAPPLER |language=en-US}} 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.{{Cite web |date=2022-10-16 |title='Neneng' intensifies into a severe tropical storm, makes landfall over Calayan Island |url=https://mb.com.ph/2022/10/16/neneng-intensifies-into-a-severe-tropical-storm-makes-landfall-over-calayan-island/ |access-date=2022-10-18 |website=Manila Bulletin |language=en-US}} According to the PAGASA, Nesat underwent "extreme" rapid intensification{{Cite web |date=2022-10-16 |title=MB Daily News Update: 'Extreme rapid intensification' turns 'Neneng' into a typhoon |url=https://mb.com.ph/2022/10/16/mb-daily-news-update-extreme-rapid-intensification-turns-neneng-into-a-typhoon/ |access-date=2022-10-18 |website=Manila Bulletin |language=en-US}} 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.{{Cite news |last=Cabuenas |first=Jon Viktor D. |title=Typhoon Neneng exits PAR; rains still likely in parts of VisMin |url=https://www.gmanetwork.com/news/scitech/weather/848274/typhoon-neneng-exits-par-rains-still-likely-in-parts-of-vismin/story/ |access-date=2022-10-18 |website=GMA News Online |language=en}}

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.{{cite news|title=NDRRMC: 103,662 individuals affected by Typhoon Neneng|first=Jean|last=Mangaluz|url=https://newsinfo.inquirer.net/1681293/ndrrmc-103662-persons-affected-by-typhoon-neneng/|date=October 18, 2022|newspaper=Philippine Daily Inquirer|access-date=October 18, 2022}} A final report by PDRRMO estimated infrastructure and agricultural damage at ₱474.2 million (US$8.15 million).{{cite news|title=2 Storms Leave ₱1 Billion Damage in Cagayan|last1=Michael Mugas|first1=John|last2=Visaya Jr.|first2=Villamor|url=https://newsinfo.inquirer.net/1683440/2-storms-leave-p1-b-damage-in-cagayan|date=October 22, 2022|newspaper=Philippine Daily Inquirer|access-date=October 22, 2022}}

{{clear}}

{{Infobox typhoon small

|Basin=WPac

|Type2=subtropical

|Formed=October 17

|Dissipated=October 19

|Image=24W 2022-10-18 0240Z.jpg

|Track=Haitang 2022 track.png

|10-min winds=35

|1-min winds=40

|type2=subtropical

|Pressure=1004

}}

On October 14, a non-tropical low with subtropical characteristics started to persist north of Minamitorishima and northwest of then-degenerating Tropical Depression 21W.{{cite web |title=WWJP27 RJTD 141800 |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |publisher=Japan Meteorological Agency |access-date=18 October 2022 |archive-url=https://archive.today/20221014203153/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-date=14 October 2022 |date=14 October 2022}}{{cite web |title=Tropical Cyclone Formation Alert (Invest 91W) |url=https://www.metoc.navy.mil/jtwc/products/wp9122web.txt |publisher=Joint Typhoon Warning Center |access-date=18 October 2022 |archive-url=https://archive.today/20221015204203/https://www.metoc.navy.mil/jtwc/products/wp9122web.txt |archive-date=15 October 2022 |date=15 October 2022}} The low remained stationary, slowly weakened and acquired more tropical characteristics next three days,{{cite web |title=Tropical Cyclone Formation Alert (Invest 91W) |url=https://www.metoc.navy.mil/jtwc/products/wp9122web.txt |publisher=Joint Typhoon Warning Center |access-date=18 October 2022 |archive-url=https://archive.today/20221017154802/https://www.metoc.navy.mil/jtwc/products/wp9122web.txt |archive-date=17 October 2022 |date=17 October 2022}} and JTWC eventually declared a tropical depression early on October 18 when the system had been deepening again and became compact.{{cite web |title=Prognostic Reasoning for Tropical Depression 24W (Twentyfour) Warning Nr 001

|url=https://www.metoc.navy.mil/jtwc/products/wp2422prog.txt |publisher=Joint Typhoon Warning Center |access-date=18 October 2022 |archive-url=https://archive.today/20221018032726/https://www.metoc.navy.mil/jtwc/products/wp2422prog.txt |archive-date=18 October 2022 |date=18 October 2022}} Although the JMA reported a gale-force non-tropical low at the same time,{{cite web |title=WWJP27 RJTD 180000 |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |publisher=Japan Meteorological Agency |access-date=18 October 2022 |archive-url=https://archive.today/20221018023450/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-date=18 October 2022 |date=18 October 2022}} the system was soon analyzed as a tropical storm and named Haitang.{{cite web |title=WTPQ50 RJTD 180600 |url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt |publisher=Japan Meteorological Agency |access-date=18 October 2022 |archive-url=https://archive.today/20221018072525/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt |archive-date=18 October 2022 |date=18 October 2022}} The center of the storm soon became weakly-defined as extensive dry air entrained the storm,{{cite report|title=Prognostic Reasoning for Tropical Storm 24W (Haitang) Warning Nr 003|url=https://tgftp.nws.noaa.gov/data/raw/wd/wdpn31.pgtw..txt|publisher=Joint Typhoon Warning Center|access-date=18 October 2022|archive-url=https://archive.today/20221018150640/https://tgftp.nws.noaa.gov/data/raw/wd/wdpn31.pgtw..txt|archive-date=18 October 2022|date=18 October 2022}} prompting the JTWC to downgrade the storm into a tropical depression and issue their final advisory late on the same day.{{cite report|title=Tropical Depression 24W (Haitang) Warning Nr 004|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpn31.pgtw..txt|publisher=Joint Typhoon Warning Center|access-date=18 October 2022|archive-url=https://archive.today/20221019032844/https://tgftp.nws.noaa.gov/data/raw/wt/wtpn31.pgtw..txt|archive-date=19 October 2022|date=18 October 2022}} The JMA, however, continued to issue advisories on the storm as it moved northeastwards,{{cite report|title=RSMC Tropical Cyclone Prognostic Reasoning No. 4 for TS 2221 Haitang (2221)|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq30.rjtd..txt|publisher=Japan Meteorological Agency|access-date=19 October 2022|archive-url=https://archive.today/20221019032732/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq30.rjtd..txt|archive-date=19 October 2022|date=19 October 2022}} and transitioned into an extratropical cyclone on October 19.{{cite web|title=RSMC Tropical Cyclone Advisory for Developed Low former TS 2221 Haitang (2221)|url=https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt|publisher=Japan Meteorological Agency|access-date=19 October 2022|archive-url=https://archive.today/20221019155422/https://tgftp.nws.noaa.gov/data/raw/wt/wtpq50.rjtd..txt|archive-date=19 October 2022|date=19 October 2022}}

{{clear}}

{{Infobox typhoon small

|Basin=WPac

|Formed=October 18

|Dissipated=October 23

|Image=Obet 2022-10-21 0515Z.jpg

|Track=Obet 2022 track.png

|10-min winds=30

|1-min winds=30

|Pressure=1006

}}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,{{Cite web |title=Tropical Depression 'Obet' can still intensify to tropical storm, prompt Signal No. 2 |url=https://www.philstar.com/headlines/2022/10/21/2218312/tropical-depression-obet-can-still-intensify-tropical-storm-prompt-signal-no-2 |access-date=2023-04-03 |website=The Philippine Star}} but the system would not strengthen further.{{Cite web |title=Obet may become tropical storm this weekend: PAGASA |url=https://news.abs-cbn.com/news/10/19/22/obet-may-become-tropical-storm-this-weekend-pagasa |access-date=2023-04-01 |website=PAGASA.dost}} On October 21, 2022, the depression slightly intensified while moving towards the Luzon Strait.{{Cite web |date=2022-10-21 |title=Tropical Depression Obet slightly strengthens while heading for Luzon Strait |url=https://www.rappler.com/nation/weather/tropical-depression-obet-pagasa-forecast-october-21-2022-2pm/ |access-date=2023-04-03 |website=RAPPLER |language=en-US}} 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.{{Cite web |title=DSWD DROMIC Report #6 on Tropical Depression "Obet" as of 24 October 2022, 6PM - Philippines {{!}} ReliefWeb |url=https://reliefweb.int/report/philippines/dswd-dromic-report-6-tropical-depression-obet-24-october-2022-6pm |access-date=2023-03-31 |website=reliefweb.int |date=October 25, 2022 |language=en}} 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.{{Cite web |title=Tropical Cyclone Obet Tracker |url=https://mb.com.ph/2022/10/22/tropical-cyclone-obet-tracker/ |access-date=2023-04-01 |website=Manila Bulletin |language=en}} The next day, the depression exited the Philippine Area of Responsibility (PAR) while moving slowly westward. 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.{{Cite news |date=2022-10-20 |title=LIVE UPDATES: Tropical Depression Obet latest news |url=https://newsinfo.inquirer.net/1682641/live-updates-tropical-depression-obet-latest-news |access-date=2023-03-31 |newspaper=Philippine Daily Inquirer |language=en}} However, later that day, the state weather bureau said that 25W was no longer expected to bring heavy rainfall to the country.{{Cite web |title=Tropical Cyclone Obet Tracker |url=https://mb.com.ph/2022/10/22/tropical-cyclone-obet-tracker/ |access-date=2023-03-31 |website=Manila Bulletin |language=en}} The depression gradually weakened and was classified as a remnant low on October 23.

According to Municipal Disaster Risk Reduction & Management Office (MDRRMO), two deaths, a fisherman and his wife, were reported due to 25W.{{cite news |last=Visaya Jr. |first=Villamor |date=October 22, 2022 |title=Missing Fisherman, Wife Found Dead In Cagayan Coastal Town |newspaper=Philippine Daily Inquirer |url=https://newsinfo.inquirer.net/1683606/missing-fisherman-wife-found-dead-in-cagayan-coastal-town |access-date=October 22, 2022}} According to the DSWD DROMIC Report #6, a total of 7,327 families or 24,245 people were affected in 74 barangays. 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.{{Cite web |title=TROPICAL DEPRESSION OBET SUMMARY |url=https://pubfiles.pagasa.dost.gov.ph/pagasaweb/files/tamss/weather/tcprelimsummary/OBET.pdf}} 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.{{Cite web |date=2022-10-21 |title=Tropical Depression Obet passes close to Batanes; no landfall |url=https://www.rappler.com/nation/weather/tropical-depression-obet-pagasa-forecast-october-21-2022-11pm/ |access-date=2023-04-03 |website=RAPPLER |language=en-US}} The NDRRMC didn't receive any damage related to the depression.{{Cite web |title=SitRep No.3 for TD OBET 2022|url=https://ndrrmc.gov.ph/attachments/article/4209/SitRep_No_3_for_Tropical_Depression_OBET_2022_Report.pdf|date=October 23, 2022|access-date=October 24, 2022|work=NDRRMC}}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=October 26

|Dissipated=November 3

|Image=Nalgae 2022-11-01 0600Z.jpg

|Track=Nalgae 2022 track.png

|10-min winds=60

|1-min winds=75

|Pressure=975

}}{{Main article|Tropical Storm Nalgae}}

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.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp9322web.txt|archive-url=https://ghostarchive.org/archive/AlMzR|date=26 October 2022|title=Current Northwest Pacific/North Indian Ocean Tropical Systems Tropical Cyclone Formation Alert WTPN21 Issued at 26/0200Z|access-date=26 October 2022|website=JTWC|archive-date=26 October 2022|language=en}} The JMA and the PAGASA then classified the disturbance as a tropical depression, with the latter assigning the name Paeng to the system.{{cite web|url=https://bagong.pagasa.dost.gov.ph/weather/weather-advisory|archive-url=https://archive.today/20221026033629/https://bagong.pagasa.dost.gov.ph/weather/weather-advisory|title=Weather advisory No. 3 For: Shearline and tropical depression "Paeng" Issued at: 11:00 AM |date=26 October 2022|access-date=26 October 2022|archive-date=26 October 2022 |website=PAGASA|language=en}}{{cite web|url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|title=Bulletin released of the tropical depression|archive-url=https://ghostarchive.org/archive/dnkh0|archive-date=26 October 2022|date=26 October 2022|access-date=26 October 2022|language=en|website=Japan Meteorological Agency}} 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.{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp2622prog.txt|archive-url=https://archive.today/20221027024540/https://www.metoc.navy.mil/jtwc/products/wp2622web.txt|archive-date=27 October 2022|date=26 October 2022|access-date=26 October 2022|website=JTWC|language=en|title=Tropical Depression 26W (Twentysix) Warning #01 Issued at 27/0300Z}} At the same time, the JMA upgraded the typhoon to a tropical storm, and was named Nalgae.{{cite web|url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|archive-url=https://web.archive.org/web/20221027025836/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt|archive-date=27 October 2022|date=26 October 2022|access-date=26 October 2022|website=Japan Meteorological Agency|language=en|title=WWJP27 RJTD 270000}} 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.{{cite web|url=https://bagong.pagasa.dost.gov.ph/tropical-cyclone/severe-weather-bulletin|archive-url=https://archive.today/20221028193536/https://bagong.pagasa.dost.gov.ph/tropical-cyclone/severe-weather-bulletin|archive-date=28 October 2022|date=28 October 2022|access-date=28 October 2022|website=PAGASA|language=en|title=Tropical cyclone bulletin #14 'Severe tropical storm Paeng' Issued at: 02:00 a. m.}}{{cite web|url=https://www.metoc.navy.mil/jtwc/products/wp2622web.txt|archive-url=https://ghostarchive.org/archive/uM27e|archive-date=28 October 2022|date=28 October 2022|access-date=28 October 2022|website=JTWC|language=en|title=Tropical storm 26W (Nalgae) Warning #07 Issued at 28/1500Z}} 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.{{Cite web |title=Severe Tropical Storm Paeng: Forecast track, weather updates, latest news in the Philippines |url=https://www.rappler.com/nation/weather/forecast-track-impact-relief-efforts-updates-news-paeng-philippines-2022/ |access-date=2022-10-29 |website=RAPPLER |language=en-US}} Nalgae then headed southwestward and struck Mogpog in the island province of Marinduque,{{Cite web |date=2022-10-29 |title=Severe Tropical Storm Paeng makes fourth landfall in Marinduque |url=https://www.rappler.com/nation/weather/severe-tropical-storm-paeng-pagasa-forecast-october-29-2022-11am/ |access-date=2022-11-02 |website=RAPPLER |language=en-US}} 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.{{Cite web |date=2022-10-29 |title=Severe Tropical Storm Paeng crosses Laguna after fifth landfall in Quezon |url=https://www.rappler.com/nation/weather/severe-tropical-storm-paeng-pagasa-forecast-october-29-2022-5pm/ |access-date=2022-11-02 |website=RAPPLER |language=en-US}} Nalgae then passed through Metro Manila and Rizal, heading into Bulacan by evening of October 29.{{Cite web|url=https://pubfiles.pagasa.dost.gov.ph/tamss/weather/bulletin/TCB%2321_paeng.pdf|title="PAENG" HAS PASSED OVER LAGUNA DE BAY AND THE METRO MANILA-RIZAL-BULACAN AREA}} By the next day, Nalgae weakened into a tropical storm in the West Philippine Sea,{{Cite web |date=2022-10-29 |title=Tropical Storm Paeng now over West Philippine Sea |url=https://www.rappler.com/nation/weather/tropical-storm-paeng-pagasa-forecast-october-30-2022-5am/ |access-date=2022-11-02 |website=RAPPLER |language=en-US}} 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.{{Cite news |last1=Mok |first1=Danny |last2=Yeo |first2=Rachel |last3=Ma |first3=Jess |last4=Ng |first4=Kang-chung |date=November 2, 2022 |title=Hong Kong cancels all storm signals 17 hours after issuing historic No 8 alert, as Nalgae departs |work=South China Morning Post |url=https://www.scmp.com/news/hong-kong/health-environment/article/3198069/hong-kong-suspends-classes-no-8-typhoon-signal-looms |access-date=November 3, 2022}}{{Cite news |date=November 2, 2022 |title=T8 to stay in force as HK waits for Nalgae to weaken |work=RTHK |url=https://news.rthk.hk/rthk/en/component/k2/1673950-20221102.htm |access-date=November 3, 2022}}{{Cite news |last=Leung |first=Kanis |date=November 2, 2022 |title=Hong Kong braces for Tropical Storm Nalgae |publisher=ABC News |url=https://abcnews.go.com/International/wireStory/hong-kong-businesses-brace-tropical-storm-nalgae-impact-92526009 |access-date=November 3, 2022}} 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{{Cite news |date=November 2, 2022 |title=Death toll from 'Paeng' hits 121 |work=Philstar.com |publisher=Philstar Global |url=https://www.philstar.com/headlines/2022/11/02/2220988/death-toll-paeng-hits-121 |access-date=November 2, 2022 |quote=The Bangsamoro Autonomous Region in Muslim Mindanao accounted for most of the fatalities with 61 deaths... Fatalities were also reported in the following regions: Western Visayas with 29, Calabarzon with 12, Eastern Visayas with five, Zamboanga Peninsula with four, Soccsksargen with three, Mimaropa and Central Visayas with two each, and Central Luzon, Bicol region and the Cordillera Administrative Region with one each.}}{{Cite news |last=De Leon |first=Dwight |date=November 2, 2022 |title=NDRRMC: Paeng death toll now at 121 |publisher=Rappler |url=https://www.rappler.com/nation/severe-tropical-storm-paeng-death-toll-injuries-damage-missing-persons-november-2-2022/ |access-date=November 2, 2022}} due to continuous flooding and landslides that were partially caused by Nalgae.{{Cite web |date=October 30, 2022 |title=Floods swamp PH, as death toll climbs to 45 |url=https://www.manilatimes.net/2022/10/30/news/floods-swamp-ph-as-death-toll-climbs-to-45/1864336 |access-date=October 30, 2022 |website=The Manila Times}}{{Cite news |last=Morales |first=Neil Jerome |date=October 29, 2022 |title=Philippines president orders urgent aid as storm Nalgae kills 45 |work=Reuters |url=https://www.reuters.com/world/asia-pacific/philippines-death-toll-tropical-storm-nalgae-climbs-72-2022-10-28/ |access-date=October 30, 2022}} 14 individuals were also confirmed to have been missing; 11 from the Maguindanao province, and 3 from the Soccsksargen region.{{Cite web |title=Philippine officials revise 'Paeng' death toll down to 45 |url=https://www.philstar.com/headlines/2022/10/29/2220162/ndrrmc-death-toll-due-paeng-rises-72 |access-date=October 30, 2022 |website=Philstar.com}}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=October 28

|Dissipated=November 3

|Image=Banyan 2022-10-31 0430Z.jpg

|Track=Banyan 2022 track.png

|10-min winds=40

|1-min winds=40

|Pressure=1002

}}

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.{{Cite web|url=https://ghostarchive.org/archive/CEnoA|title=WTPN21 PGTW 281230 MSGID/GENADMIN/JOINT TYPHOON WRNCEN PEARL HARBOR HI// SUBJ/TROPICAL CYCLONE FORMATION ALERT (INVEST 94W)// RMKS/|via=Ghostarchive}}{{Cite web|url=https://ghostarchive.org/archive/Jfpvx|title=WTPN21 PGTW 291230 |via=Ghostarchive}} 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.{{Cite web|url=https://ghostarchive.org/archive/WxnPN |title=Tropical cyclone formation alert WTPN21 (Invest 94W) Issued at 21/0130Z |website=JTWC |via=Ghostarchive}}{{cite web |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-url=https://archive.today/20221030030928/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |url-status=dead |archive-date=2022-10-30 |title=WWJP27 RJTD 300000 |via=Archive.ph }} At 21:00 UTC on October 30, the tropical depression was designated 27W.{{Cite web |url=https://ghostarchive.org/archive/nhj0o |title=WTPN32 PGTW 302100 |via=Ghostarchive}} Upon entering the Philippine Area of Responsibility, it was given the local name Queenie by PAGASA.{{Cite web|url=https://news.abs-cbn.com/news/10/31/22/queenie-enters-par-paeng-set-to-exit|title=Queenie enters PAR, Paeng set to exit}} Banyan intensified into a tropical storm, and was given the international name Banyan by the Japan Meteorological Agency.{{Cite news |last=Boiser |first=Abby |date=2022-11-01 |title=Queenie turns into tropical storm as it enters PH |url=https://newsinfo.inquirer.net/1687703/queenie-turns-into-tropical-storm-as-it-enters-ph |access-date=2022-11-02 |newspaper=Philippine Daily Inquirer |language=en}} 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.{{Cite web |title='Queenie' weakens into tropical depression |url=https://www.philstar.com/headlines/2022/11/01/2220768/queenie-weakens-tropical-depression |access-date=2022-11-02 |website=The Philippine Star}} Later that afternoon, the PAGASA had issued their final advisory on Banyan after it dissipated into a remnant low pressure area.{{Cite web |last=Araja |first=Rio N. |date=2022-11-02 |title=Queenie weakens into mere LPA |url=https://manilastandard.net/news/314274678/queenie-weakens-into-mere-lpa.html |access-date=2022-11-02 |website=Manila Standard |language=en-US}} The depression was last seen 200 km north of Sonsorol, moving west-northwestward at 7 km/h (4 knots) over the past 6 hours.{{Cite web |title=Tropical Cyclone Queenie Tracker |url=https://mb.com.ph/2022/10/31/tropical-cyclone-queenie-tracker/ |access-date=2023-03-30 |website=Manila Bulletin |language=en}} The remnants of Banyan continued to cause some rain in eastern Mindanao.{{Cite web |date=2022-11-01 |title=Tropical Depression Queenie weakens into low pressure area |url=https://www.rappler.com/nation/weather/tropical-depression-queenie-low-pressure-area-pagasa-forecast-november-1-2022-5pm/ |access-date=2022-11-06 |website=RAPPLER |language=en-US}}

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=November 11

|Dissipated=November 14

|Image=Yamaneko 2022-11-13 0210Z.jpg

|Track=Yamaneko 2022 track.png

|10-min winds=35

|1-min winds=40

|Pressure=1004

}}

On November 11, a tropical disturbance was formed in Wake Island, it was designated as 95W by the JTWC on its TCFA.{{cite web |title=WWJP27 RJTD 111200 |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |publisher=Japan Meteorological Agency |access-date=11 November 2022 |archive-url=https://archive.today/20221111155729/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-date=11 November 2022 |date=11 November 2022}} It strengthened into a tropical depression later on the next day, designated as 28W. 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 {{cvt|65|km/h|mph}}. There were no reports of damage or casualties caused by Yamaneko. The storm did not make landfall and dissipated on November 14, 2022.

{{clear}}

{{Infobox hurricane small

|Basin=WPac

|Formed=December 10

|Dissipated=December 12

|Image=Pakhar 2022-12-12 0140Z.jpg

|Track=Pakhar 2022 track.png

|10-min winds=40

|1-min winds=50

|Pressure=998

}}

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.{{cite web |title=WWJP27 RJTD 090000 |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |publisher=Japan Meteorological Agency |access-date=9 December 2022 |archive-url=https://archive.today/20221209083542/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20221209/000000/A_WWJP27RJTD090000_C_RJTD_20221209022317_44.txt |archive-date=9 December 2022 |date=9 December 2022}}{{cite web |title=WWJP27 RJTD 090600 |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |publisher=Japan Meteorological Agency |access-date=9 December 2022 |archive-url=https://archive.today/20221209083410/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-date=9 December 2022 |date=9 December 2022}} 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.{{Cite web |last=Flores |first=Helen |title=Rosal may dissipate while moving away from Philippines |url=https://www.philstar.com/headlines/2022/12/13/2230438/rosal-may-dissipate-while-moving-away-philippines |access-date=2022-12-14 |website=The Philippine Star}}

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.{{Cite web |last=Standard |first=Manila |date=2022-12-11 |title=8 killed as flash floods hit Tanay, Rizal |url=https://manilastandard.net/news/national/314286634/8-killed-as-flash-floods-hit-tanay-rizal.html |access-date=2022-12-15 |website=Manila Standard |language=en-US}}

{{clear}}

• A low-pressure area developed into a tropical depression to the northeast of Mindanao early on May 30,{{cite web |title=WWJP27 RJTD 291800 |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |publisher=Japan Meteorological Agency |access-date=30 May 2022 |archive-url=https://archive.today/20220530023729/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220529/180000/A_WWJP27RJTD291800_C_RJTD_20220529202618_78.txt |archive-date=30 May 2022 |date=29 May 2022}}{{cite web |title=WWJP27 RJTD 300000 |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |publisher=Japan Meteorological Agency |access-date=30 May 2022 |archive-url=https://archive.today/20220530023544/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-date=30 May 2022 |date=30 May 2022}} but quickly dissipated near Mindanao late on the same day.{{cite web |title=WWJP27 RJTD 301800 |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |publisher=Japan Meteorological Agency |access-date=31 May 2022 |archive-url=https://archive.today/20220531022221/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220530/180000/A_WWJP27RJTD301800_C_RJTD_20220530201717_85.txt |archive-date=31 May 2022 |date=30 May 2022}}{{cite web |title=WWJP27 RJTD 310000 |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |publisher=Japan Meteorological Agency |access-date=31 May 2022 |archive-url=https://archive.today/20220531023353/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-date=31 May 2022 |date=31 May 2022}}
• On July 22, the JMA began tracking a low pressure area off south of Japan.{{cite web |date=2022-07-22 |title=WWJP27 RJTD 221800 |url=https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220722/180000/A_WWJP27RJTD221800_C_RJTD_20220722201617_54.txt |archive-url=https://archive.today/20220724072244/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220722/180000/A_WWJP27RJTD221800_C_RJTD_20220722201617_54.txt |archive-date=2022-07-24 |access-date=2022-07-24 |publisher=Japan Meteorological Agency}} The following day, the JTWC also began tracking the system, now {{convert|227|nmi|mi km}} south-southwest of Iwo Jima, Japan.{{Cite JTWC|date=2022-07-23|type=stwa|basin=wpac|designation=92W|name=Invest 92W|time=06Z|url=https://www.metoc.navy.mil/jtwc/products/abpwweb.txt|url-status=live|archive-date=2017-12-21|archive-url=https://web.archive.org/web/20171221082438/http://www.metoc.navy.mil/jtwc/products/abpwweb.txt}} [https://wiki.chlod.net/jtwc/text/2022-07-23-0610-abpwweb.txt Alt URL] On July 24, the JMA upgraded the system to a tropical depression.{{cite web |date=2022-07-24 |title=WWJP27 RJTD 240000 |url=https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220724/000000/A_WWJP27RJTD240000_C_RJTD_20220724022217_31.txt |archive-url=https://archive.today/20220724071533/https://www.wis-jma.go.jp/d/o/RJTD/Alphanumeric/Warning/Warnings_and_weather_summary/20220724/000000/A_WWJP27RJTD240000_C_RJTD_20220724022217_31.txt |archive-date=2022-07-24 |access-date=2022-07-24 |publisher=Japan Meteorological Agency}}
• The JMA started to monitor a weak tropical depression that formed just west of the International Date Line on August 14 and dissipated later that day.{{cite web |title=WWJP27 RJTD 141200 |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |publisher=Japan Meteorological Agency |access-date=14 August 2022 |archive-url=https://archive.today/20220814144403/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-date=14 August 2022 |date=14 August 2022}}
• A tropical depression formed far east of Japan on August 22, and dissipated the same day.{{cite web |title=WWJP27 RJTD 220600 |url=https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |publisher=Japan Meteorological Agency |access-date=22 August 2022 |archive-url=https://archive.today/20220822093555/https://tgftp.nws.noaa.gov/data/raw/ww/wwjp27.rjtd..txt |archive-date=22 August 2022 |date=22 August 2022}}
• On September 25, the JMA tracked a weak tropical depression a few hundred miles off the Japanese coast, but it dissipated on the same day. {{citation needed|date=November 2022}}

{{clear}}

• On November 15, a low-pressure area and the Intertropical Convergence Zone brought flooding and heavy rain to the Philippines due to the combined effects of the weather systems.{{Cite web |title=Philippines: Adverse weather forecast across most of the country through at least Nov. 22 /update 1 |url=https://crisis24.garda.com/alerts/2022/11/philippines-adverse-weather-forecast-across-most-of-the-country-through-at-least-nov-22-update-1 |access-date=2022-11-29 |website=Philippines: Adverse weather forecast across most of the country through at least Nov. 22 /update 1 {{!}} Crisis24 |language=en}} Landslides were said to have occurred in some parts of the Philippines.{{Cite web |title=Philippines, Flooding and Landslides in Davao Occidental and Davao del Sur (Region XI) (16 Nov 2022) - Philippines {{!}} ReliefWeb |url=https://reliefweb.int/report/philippines/philippines-flooding-and-landslides-davao-occidental-and-davao-del-sur-region-xi-16-nov-2022 |access-date=2022-11-29 |website=reliefweb.int |date=November 18, 2022 |language=en}} By November 18, extreme flooding was experienced in some parts of Mindanao.{{Cite news |last=Lalu |first=Gabriel Pabico |date=2022-11-11 |title=Luzon and Visayas to see fair weather; ITCZ to affect Mindanao – Pagasa |url=https://newsinfo.inquirer.net/1692274/luzon-and-visayas-to-see-fair-weather-itcz-to-affect-mindanao-pagasa |access-date=2022-11-29 |newspaper=Philippine Daily Inquirer |language=en}} The Philippine Red Cross served hot meals to 1,691 displaced people due to the effects of the flood.{{Cite web |title=PH Red Cross responds to families displaced by flash floods and heavy rains in Davao del Sur and other parts of Mindanao - Philippines {{!}} ReliefWeb |url=https://reliefweb.int/report/philippines/ph-red-cross-responds-families-displaced-flash-floods-and-heavy-rains-davao-del-sur-and-other-parts-mindanao |access-date=2022-11-29 |website=reliefweb.int |date=November 23, 2022 |language=en}} Localities in Cotabato have also suspended classes.{{Cite web |last=Sarmiento |first=Bong S. |date=2022-11-16 |title=All South Cotabato localities suspend classes due to bad weather |url=https://www.mindanews.com/top-stories/2022/11/all-south-cotabato-localities-suspend-classes-due-to-bad-weather/ |access-date=2022-11-30 |website=MindaNews |language=en-US}} At least five casualties had occurred.{{Cite web |last=Cantos |first=Joy |title=5 patay sa LPA, ITCZ |url=https://www.philstar.com/pilipino-star-ngayon/bansa/2012/11/15/866786/5-patay-sa-lpa-itcz |access-date=2022-11-29 |website=The Philippine Star}}

{{See also|Tropical cyclone naming|History of tropical cyclone naming}}

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.{{cite web|title=Monthly Tropical Cyclone Summary December 1999|access-date=October 1, 2013|last=Padgett |first=Gary|publisher=Australian Severe Weather|url=http://www.australiasevereweather.com/cyclones/2000/summ9912.htm|archive-url=https://web.archive.org/web/20120211074501/http://australiasevereweather.com/cyclones/2000/summ9912.htm|archive-date=February 11, 2012|url-status=live}} 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 {{convert|65|km/h|mph|abbr=on}}.{{cite web|title=Typhoon Committee Operational Manual 2013|url=http://www.wmo.int/pages/prog/www/tcp/documents/TCP-23EDITION2013.pdf|archive-url=https://web.archive.org/web/20130801020116/http://www.wmo.int/pages/prog/www/tcp/documents/TCP-23EDITION2012.pdf|publisher=World Meteorological Organization|archive-date=August 1, 2013|pages=37–38|date=February 21, 2013|author=The Typhoon Committee|access-date=October 1, 2013|url-status=live}} 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. The names of significant tropical cyclones will be retired by both PAGASA and the Typhoon Committee in the spring of 2023.

{{main article|List of retired Pacific typhoon names}}

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.{{cite journal|last1=Zhou |first1= Xiao|last2=Lei |first2= Xiaotu|year=2012|title=Summary of retired typhoons within the Western North Pacific Ocean|volume=1|issue=1|publisher=The Economic and Social Commission for Asia and the Pacific/World Meteorological Organization's Typhoon Committee|journal=Tropical Cyclone Research and Review|pages=23–32|issn=2225-6032|url=http://tcrr.typhoon.gov.cn/EN/article/downloadArticleFile.do?attachType=PDF&id=7|access-date=December 21, 2014|doi=10.6057/2012TCRR01.03|archive-date=August 12, 2017|archive-url=https://web.archive.org/web/20170812172856/http://tcrr.typhoon.gov.cn/EN/article/downloadArticleFile.do?attachType=PDF&id=7|url-status=dead}} 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.

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.{{Cite web |date=April 30, 2023 |title=REPORT OF THE FIFTY-FIFTH SESSION OF TYPHOON COMMITTEE |url=https://typhooncommittee.org/55th/docs/final/TC55Report_FINAL.pdf |access-date=April 30, 2023 |website=Typhoon Committee}} In 2024, they were replaced by Amuyao, Gosari, Tsing-ma, Ong-mang, Hodu and Jamjari respectively.{{cite report |url=https://www.typhooncommittee.org/56th/docs/final/TC56_FINAL.pdf |title=Report of the Fifty-Sixth session of Typhoon Committee|date=March 25, 2024 |publisher=ESCAP/WMO Typhoon Committee |access-date=September 1, 2024}} This surpassed, at that time, the previous record for the number of typhoon names retired after a single season – five, held by the 2006, 2019, and 2020 seasons. However, the record was later broken when the 2024 season recorded nine retired typhoon names in a single season.

{{clear}}

{{main article|List of retired Philippine typhoon names}}

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.{{cite web|title=Philippine Tropical Cyclone Names|access-date=April 18, 2015|publisher=Philippine Atmospheric, Geophysical and Astronomical Services Administration|url=http://www.pagasa.dost.gov.ph/index.php/learning-tools/94-weather/278-philippine-tropical-cyclone-names|archive-date=December 28, 2016|archive-url=https://web.archive.org/web/20161228042559/http://www.pagasa.dost.gov.ph/index.php/learning-tools/94-weather/278-philippine-tropical-cyclone-names|url-status=live}} The names were taken from a list of names, that was last used during 2018 and are scheduled to be used again during 2026. All of the names are the same except Obet, Rosal and Umberto which replaced the names Ompong, Rosita and Usman after they were retired. The names Obet and Rosal were used for the first time this year.

{{clear}}

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.{{Cite web |date=May 6, 2023 |title=Philippine Tropical Cyclone Names |url=https://bagong.pagasa.dost.gov.ph/learning-tools/philippine-tropical-cyclone-names |url-status=deviated |archive-url=https://web.archive.org/web/20230506225938/https://bagong.pagasa.dost.gov.ph/learning-tools/philippine-tropical-cyclone-names |archive-date=May 6, 2023 |access-date=2023-05-06 |website=bagong.pagasa.dost.gov.ph}}

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.

{{Pacific areas affected (Top)|year=2022}}

|-

| TD || {{Sort|220724|January 27–28}} || style="background:#{{storm color|TD}}" |{{Sort|0|Tropical depression}} || style="background:#{{storm color|TD}}" | {{Sort|0|Not specified}} || style="background:#{{storm color|TD}}" |{{convert|1006|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| None || {{ntsh|0||$}} None || {{ntsh|0}} None ||

|-

| 01W || {{Sort|220329|March 29–31}} || style="background:#{{storm color|TD}}" |{{Sort|0|Tropical depression}} || style="background:#{{storm color|TD}}" |{{Sort|0|Not specified}} || style="background:#{{storm color|TD}}" |{{convert|1006|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Vietnam || {{ntsp|148950000||$}} || {{nts|6}} ||

|-

| Malakas (Basyang) || {{Sort|220406|April 6–15}} || style="background:#{{storm color|VSTY}}" |{{Sort|4|Very strong typhoon}} || style="background:#{{storm color|VSTY}}" |{{convert|90|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|VSTY}}" |{{convert|945|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Guam, Caroline Islands, Bonin Islands || {{ntsh|0||$}} None || {{ntsh|0}} None ||

|-

| Megi (Agaton) || {{Sort|220408|April 8–12}} || style="background:#{{storm color|TS}}" |{{Sort|1|Tropical storm}} || style="background:#{{storm color|TS}}" |{{convert|40|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TS}}" |{{convert|996|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Philippines || {{ntsp|200000000||$}} || {{nts|214}} || {{Cite report |url=https://monitoring-dashboard.ndrrmc.gov.ph/assets/uploads/situations/SitRep_No__15_for_TC_AGATON_2022.pdf |title=Situational Report No. 15 for TC AGATON (2022) |date=April 29, 2022 |publisher=National Disaster Risk Reduction and Management Council |access-date=April 29, 2022 |archive-url=https://web.archive.org/web/20220430043432/https://monitoring-dashboard.ndrrmc.gov.ph/assets/uploads/situations/SitRep_No__15_for_TC_AGATON_2022.pdf |archive-date=April 30, 2022 |url-status=live}}

|-

| TD || {{Sort|220530|May 30}} || style="background:#{{storm color|TD}}" |{{Sort|0|Tropical depression}} || style="background:#{{storm color|TD}}" |{{Sort|0|Not specified}} || style="background:#{{storm color|TD}}" |{{convert|1006|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Philippines || {{ntsh|0||$}} None || {{ntsh|0}} None ||

|-

| Chaba (Caloy) || {{Sort|220628|June 28 – July 5}} || style="background:#{{storm color|TY}}" |{{Sort|3|Typhoon}} || style="background:#{{storm color|TY}}" |{{convert|70|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TY}}" |{{convert|965|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Philippines, China, Vietnam || {{ntsp|464000000||$}} || {{nts|12}} || {{cite web |title=Q3 Global Catastrophe Recap |url=https://www.aon.com/reinsurance/getmedia/08b0306f-790c-4f6a-8c0e-883e91ceba04/20221410-if-q3-2022-global-cat-recap.pdf |website=Aon Benfield |access-date=October 21, 2022}}

|-

| Aere (Domeng) || {{Sort|220630|June 30 – July 4}} || style="background:#{{storm color|TS}}" |{{Sort|1|Tropical storm}} || style="background:#{{storm color|TS}}" |{{convert|45|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TS}}" |{{convert|994|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Japan || {{ntsh|0||$}} Unknown || {{ntsh|0}} None ||

|-

| TD || {{Sort|220724|July 24–25}} || style="background:#{{storm color|TD}}" |{{Sort|0|Tropical depression}} || style="background:#{{storm color|TD}}" | {{convert|30|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TD}}" |{{convert|1006|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| None || {{ntsh|0||$}} None || {{ntsh|0}} None ||

|-

| Songda || {{Sort|220726|July 26 – August 1}} || style="background:#{{storm color|TS}}" |{{Sort|1|Tropical storm}} || style="background:#{{storm color|TS}}" | {{convert|40|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TS}}" |{{convert|996|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Japan, South Korea, North Korea || {{ntsh|0||$}} None || {{ntsh|0}} None ||

|-

| Trases (Ester) || {{Sort|220729|July 29 – August 1}} || style="background:#{{storm color|TS}}" |{{Sort|1|Tropical storm}} || style="background:#{{storm color|TS}}" | {{convert|35|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TS}}" |{{convert|998|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Ryukyu Islands, South Korea || {{ntsh|0||$}} None || {{ntsh|0}} None ||

|-

| 08W || {{Sort|220803|August 3–4}} || style="background:#{{storm color|TD}}" |{{Sort|0|Tropical depression}} || style="background:#{{storm color|TD}}" |{{Sort|0|Not specified}} || style="background:#{{storm color|TD}}" |{{convert|1002|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| South China, Vietnam || {{ntsh|0||$}} Unknown || {{ntsh|0}} None ||

|-

| Mulan || {{Sort|220808|August 8–11}} || style="background:#{{storm color|TS}}" |{{Sort|1|Tropical storm}} || style="background:#{{storm color|TS}}" |{{convert|35|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TS}}" |{{convert|994|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| South China, Vietnam, Laos, Thailand, Myanmar || {{ntsp|1426000||$}} || {{nts|7}} || {{cite web |date=14 August 2022|title=9 người chết và mất tích do mưa lũ sau bão số 2 ở miền Bắc |url=https://vov.vn/xa-hoi/9-nguoi-chet-va-mat-tich-do-mua-lu-sau-bao-so-2-o-mien-bac-post963208.vov |work=Voice of Vietnam |access-date=14 August 2022 |language=vi}}

|-

| Meari || {{Sort|220810|August 8–14}} || style="background:#{{storm color|TS}}" |{{Sort|1|Tropical storm}} || style="background:#{{storm color|TS}}" |{{convert|40|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TS}}" |{{convert|996|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Japan || {{ntsh|0||$}} Unknown || {{ntsh|0}} None ||

|-

| TD || {{Sort|220814|August 14}} || style="background:#{{storm color|TD}}" |{{Sort|0|Tropical depression}} || style="background:#{{storm color|TD}}" |{{Sort|0|Not specified}} || style="background:#{{storm color|TD}}" |{{convert|1012|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| None || {{ntsh|0||$}} None || {{ntsh|0}} None ||

|-

| Ma-on (Florita) || {{Sort|220820|August 20–26}} || style="background:#{{storm color|STS}}" |{{Sort|2|Severe tropical storm}} || style="background:#{{storm color|STS}}" |{{convert|55|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|STS}}" |{{convert|985|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Philippines, South China, Vietnam || {{ntsp|66590000||$}} || {{nts|7}} || {{cite news|url=https://ndrrmc.gov.ph/attachments/article/4194/SitRep_No_7_for_STS_Florita_2022_Update.pdf |title=SitRep No. 7 for Severe Tropical Storm Florita (2022) |newspaper=NDRRMC |access-date=August 28, 2022}}{{cite web |date=27 August 2022|title=3 người chết, nhiều tài sản thiệt hại trong mưa lũ sau bão số 3 |url=https://thanhnien.vn/3-nguoi-chet-nhieu-tai-san-thiet-hai-trong-mua-lu-sau-bao-so-3-post1492525.html |work=Thanh Niên |access-date=27 August 2022 |language=vi}}https://www.mem.gov.cn/xw/yjglbgzdt/202209/t20220917_422674.shtml

|-

| Tokage || {{Sort|220821|August 21–25}} || style="background:#{{storm color|TY}}" |{{Sort|3|Typhoon}} || style="background:#{{storm color|TY}}" |{{convert|75|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TY}}" |{{convert|970|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| None || {{ntsh|0||$}} None || {{ntsh|0}} None ||

|-

| TD || {{Sort|220822|August 22}} || style="background:#{{storm color|TD}}" |{{Sort|0|Tropical depression}} || style="background:#{{storm color|TD}}" | {{convert|30|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TD}}" |{{convert|1008|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| None || {{ntsh|0||$}} None || {{ntsh|0}} None ||

|-

| Hinnamnor (Henry) || {{Sort|220827|August 27 –September 6}} || style="background:#{{storm color|VITY}}" |{{Sort|5|Violent typhoon}} || style="background:#{{storm color|VITY}}" | {{convert|105|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|VITY}}" |{{convert|920|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Japan, Philippines, Taiwan, East China, South Korea, North Korea, Russian Far East || {{ntsp|1807000000||$}} || {{nts|20}} || {{Cite news| script-title=ko:[태풍 힌남노] 포항서 9명 사망·1명 실종...재산피해 1조7천억 원 – 연합뉴스 |trans-title=Typhoon Hinnamnor: 9 dead, 1 missing in Pohang; Property damage at KRW 1.7 trillion |publisher=Yonhap News Agency |url=https://m.yna.co.kr/view/AKR20220907155700053 |archive-url=https://web.archive.org/web/20220919001212/https://m.yna.co.kr/view/AKR20220907155700053 |date=September 7, 2022 |archive-date=September 19, 2022 |access-date=September 19, 2022 |website=m.yna.co.kr |language=ko}}

|-

| 13W (Gardo) || {{Sort|220830|August 30 – September 1}} || style="background:#{{storm color|TD}}" |{{Sort|0|Tropical depression}} || style="background:#{{storm color|TD}}" | {{convert|30|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TD}}" |{{convert|998|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| None || {{ntsh|0||$}} None || {{ntsh|0}} None ||

|-

| Muifa (Inday) || {{Sort|220903|September 3–15}} || style="background:#{{storm color|VSTY}}" |{{Sort|4|Very strong typhoon}} || style="background:#{{storm color|VSTY}}" | {{convert|85|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|VSTY}}" |{{convert|950|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Philippines, Taiwan, Yaeyama Islands, East China || {{ntsp|437000000||$}} || {{ntsh|3}} 3 ||

|-

| Merbok || {{Sort|220910|September 10–15}} || style="background:#{{storm color|TY}}" |{{Sort|3|Typhoon}} || style="background:#{{storm color|TY}}" | {{convert|70|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TY}}" |{{convert|965|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| None || {{ntsh|0||$}} None || {{ntsh|0}} None ||

|-

| Nanmadol (Josie) || {{Sort|220912|September 12–19}} || style="background:#{{storm color|VITY}}" |{{Sort|5|Violent typhoon}} || style="background:#{{storm color|VITY}}" |{{convert|105|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|VITY}}" |{{convert|910|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Japan, Korean Peninsula, Russian Far East || {{ntsp|1200000000||$}} || {{nts|4}} ||

|-

| Talas || {{Sort|220920|September 20–23}} || style="background:#{{storm color|TS}}" |{{Sort|1|Tropical storm}} || style="background:#{{storm color|TS}}" |{{convert|35|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TS}}" |{{convert|1000|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Japan || {{ntsh|0||$}} Unknown || {{nts|3}} ||

|-

| Noru (Karding) || {{Sort|220921|September 21–29}} || style="background:#{{storm color|VSTY}}" |{{Sort|4|Very strong typhoon}} || style="background:#{{storm color|VSTY}}" |{{convert|95|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|VSTY}}" |{{convert|940|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Philippines, Vietnam, Laos, Thailand, Cambodia || {{ntsp|312700000||$}} || {{nts|40}} || {{Cite report |url=https://monitoring-dashboard.ndrrmc.gov.ph/assets/uploads/situations/SitRep_No__10_for_STY_KARDING_2022.pdf |title=Situational Report No. 7 for Tropical Storm Karding |date=October 3, 2022 |publisher=National Disaster Risk Reduction and Management Council |archive-url=https://web.archive.org/web/20221003004545/https://monitoring-dashboard.ndrrmc.gov.ph/assets/uploads/situations/SitRep_No__10_for_STY_KARDING_2022.pdf |archive-date=October 3, 2022}}{{Cite web |title=Báo cáo nhanh công tác trực ban PCTT ngày 02/10/2022 |url=https://phongchongthientai.mard.gov.vn/Pages/bao-cao-nhanh-cong-tac-truc-ban-pctt-ngay-02-10-2022.aspx |access-date=October 3, 2022 |website=phongchongthientai.mard.gov.vn}}{{cite web |url=https://phnompenhpost.com/national/typhoon-noru-brings-flash-floods-16-dead | title=Typhoon Noru brings flash floods – 16 dead }}

|-

| Kulap || {{Sort|220925|September 25–29}} || style="background:#{{storm color|STS}}" |{{Sort|2|Severe tropical storm}} || style="background:#{{storm color|STS}}" | {{convert|60|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|STS}}" |{{convert|965|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| None || {{ntsh|0||$}} None || {{ntsh|0}} None ||

|-

| TD || {{Sort|220925|September 25–26}} || style="background:#{{storm color|TD}}" |{{Sort|0|Tropical depression}} || style="background:#{{storm color|TD}}" | {{Sort|0|Not specified}} || style="background:#{{storm color|TD}}" |{{convert|1012|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| None || {{ntsh|0||$}} None || {{ntsh|0}} None ||

|-

| Roke (Luis) || {{Sort|220927|September 28 – October 1}} || style="background:#{{storm color|TY}}" |{{Sort|3|Typhoon}} || style="background:#{{storm color|TY}}" | {{convert|70|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TY}}" |{{convert|975|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Daitō Islands || {{ntsh|0||$}} None || {{ntsh|0}} None ||

|-

| Maymay || {{Sort|221011|October 11–12}} || style="background:#{{storm color|TD}}" |{{Sort|0|Tropical depression}} || style="background:#{{storm color|TD}}" |{{Sort|0|Not specified}} || style="background:#{{storm color|TD}}" |{{convert|1002|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Philippines || {{ntsp|9160000||$}} || {{nts|2}} || {{Cite web|title=Cagayan PDRRMO confirms 2 deaths due to 'Maymay' |url=https://www.cnnphilippines.com/news/2022/10/13/Cagayan-deaths-due-to-Maymay.html|archive-url=https://web.archive.org/web/20221012232123/https://www.cnnphilippines.com/news/2022/10/13/Cagayan-deaths-due-to-Maymay.html|url-status=dead|archive-date=October 12, 2022|access-date=October 13, 2022|website=cnnphilippines.com/news}}

|-

| 21W || {{Sort|221012|October 12–14}} || style="background:#{{storm color|TD}}" |{{Sort|0|Tropical depression}} || style="background:#{{storm color|TD}}" |{{convert|30|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TD}}" |{{convert|1002|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| None || {{ntsh|0||$}} None || {{ntsh|0}} None ||

|-

| Sonca || {{Sort|221013|October 13–15}} || style="background:#{{storm color|TS}}" |{{Sort|1|Tropical storm}} || style="background:#{{storm color|TS}}" |{{convert|35|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TS}}" |{{convert|998|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Vietnam, Laos, Cambodia || {{ntsp|101500000||$}} || {{ntsh|10}} 10 ||

|-

| Nesat (Neneng) || {{Sort|221014|October 14–20}} || style="background:#{{storm color|TY}}" |{{Sort|3|Typhoon}} || style="background:#{{storm color|TY}}" |{{convert|75|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TY}}" |{{convert|965|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Philippines, Taiwan, South China, Vietnam, Cambodia, Laos || {{ntsp|16701471.40||$}} || {{ntsh|0}} None || {{Cite web|title=Over 29K families affected by Neneng, ₱81-M infra damage — NDRRMC |url=https://www.cnnphilippines.com/news/2022/10/18/Over-29K-families-affected-by-Neneng.html|archive-url=https://web.archive.org/web/20221018064530/https://www.cnnphilippines.com/news/2022/10/18/Over-29K-families-affected-by-Neneng.html|url-status=dead|archive-date=October 18, 2022|access-date=October 18, 2022|website=cnnphilippines.com/news}}

|-

| Haitang || {{Sort|221018|October 17–19}} || style="background:#{{storm color|TS}}" |{{Sort|1|Tropical storm}} || style="background:#{{storm color|TS}}" |{{convert|35|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TS}}" |{{convert|1004|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| None || {{ntsh|0||$}} None || {{ntsh|0}} None ||

|-

| 25W (Obet) || {{Sort|221018|October 18–23}} || style="background:#{{storm color|TD}}" |{{Sort|0|Tropical depression}} || style="background:#{{storm color|TD}}" | {{convert|30|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TD}}" |{{convert|1006|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Philippines || {{ntsh|0||$}} Minimal || {{nts|2}} || {{cite news|title=Missing Fisherman, Wife Found Dead In Cagayan Coastal Town|first=Villamor|last=Visaya Jr.|url=https://newsinfo.inquirer.net/1683606/missing-fisherman-wife-found-dead-in-cagayan-coastal-town|date=October 22, 2022|newspaper=Philippine Daily Inquirer|access-date=October 22, 2022}}

|-

| Nalgae (Paeng) || {{Sort|221026|October 26 – November 3}} || style="background:#{{storm color|STS}}" |{{Sort|2|Severe tropical storm}} || style="background:#{{storm color|STS}}" | {{convert|60|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|STS}}" |{{convert|975|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Philippines, Hong Kong, Macau, South China || {{ntsp|321000000||$}} || {{nts|160}} || {{Cite news |title=NDRRMC: 'Paeng' disrupted lives of nearly 4M, left at least 150 dead |url=https://www.philstar.com/headlines/2022/11/03/2221267/ndrrmc-paeng-disrupted-lives-nearly-4m-left-least-150-dead |date=2022-11-03 |access-date=2022-11-03 |website=The Philippine Star}}{{Cite news |quote=As of its 6 a.m. report on Thursday, the National Disaster Risk Reduction and Management Council (NDRRMC) noted 94 of the deaths were confirmed while 56 are for validation. Of those verified, 63 were from the Bangsamoro region, 28 from Western Visayas, and three from Soccsksargen. |url=https://www.cnnphilippines.com/news/2022/11/3/Paeng-150-death-toll.html |archive-url=https://web.archive.org/web/20221103062403/https://www.cnnphilippines.com/news/2022/11/3/Paeng-150-death-toll.html |url-status=dead |archive-date=November 3, 2022 |access-date=2022-11-03 |date=2022-11-03 |publisher=CNN Philippines |title=NDRRMC: Paeng death toll climbs to 150, almost four million people affected}}{{Cite news |title=Reported death toll due to Paeng now 150 —NDRRMC |url=https://www.gmanetwork.com/news/topstories/nation/850181/reported-death-toll-due-to-paeng-now-150-ndrrmc/story/ |publisher=GMA News|date=2022-11-03 |access-date=2022-11-03}}{{Cite report |url=https://ndrrmc.gov.ph/attachments/article/4211/SitRep_No._23_for_STS_PAENG_2022.pdf |title=Situational Report No. 23 for Tropical Storm Paeng |date=November 12, 2022 |publisher=National Disaster Risk Reduction and Management Council}}

|-

| Banyan (Queenie) || {{Sort|2201028|October 28 – November 3}} || style="background:#{{storm color|TS}}" |{{Sort|1|Tropical storm}} || style="background:#{{storm color|TS}}" | {{convert|40|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TS}}" |{{convert|1002|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Caroline Islands, Palau, Mindanao || {{ntsh|0||$}} None || {{ntsh|0}} None ||

|-

| Yamaneko || {{Sort|221111|November 11–14}} || style="background:#{{storm color|TS}}" |{{Sort|1|Tropical storm}} || style="background:#{{storm color|TS}}" | {{convert|35|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TS}}" |{{convert|1004|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| None || {{ntsh|0||$}} None || {{ntsh|0}} None ||

|-

| Pakhar (Rosal) || {{Sort|221210|December 10–12}} || style="background:#{{storm color|TS}}" |{{Sort|1|Tropical storm}} || style="background:#{{storm color|TS}}" | {{convert|40|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}} || style="background:#{{storm color|TS}}" |{{convert|998|hPa|inHg|abbr=on|sigfig=4|comma=off}}|| Philippines || {{ntsh|0||$}} None || {{nts|8}} ||

|-

{{TC Areas affected (Bottom)|TC's=37 systems|dates=January 27 – December 12, 2022|winds={{convert|105|kn|km/h mph|round=5|order=out|abbr=on|sortable=on}}|pres={{convert|910|hPa|inHg|abbr=on|sigfig=4|comma=off}}|damage={{ntsp|{{#expr:149000000+200000000+464000000+1430000+66590000+1807000000+437000000+1200000000+312700000+9160000+101500000+16701471.40+321000000}}||$}}|deaths=498|}}

{{Portal|Tropical cyclones}}

• Weather of 2022
• Tropical cyclones in 2022
• Pacific typhoon season
• 2022 Atlantic hurricane season
• 2022 Pacific hurricane season
• 2022 North Indian Ocean cyclone season
• South-West Indian Ocean cyclone seasons: 2021–22, 2022–23
• Australian region cyclone seasons: 2021–22, 2022–23
• South Pacific cyclone seasons: 2021–22, 2022–23

{{clear}}

{{Reflist|group=nb}}

{{reflist|colwidth=30em}}

{{Commons category}}

{{WPAC EL's}}

{{2022 Pacific typhoon season buttons}}

{{TC Decades|Year=2020|basin=Pacific|type=typhoon}}

Category:Articles which contain graphical timelines

Category:Pacific typhoon seasons

Category:Tropical cyclones in 2022