Misplaced Pages

2018 Pacific typhoon season: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 10:59, 1 October 2023 editTherealangelo1177 (talk | contribs)Extended confirmed users7,027 edits Season summary← Previous edit Latest revision as of 07:44, 25 December 2024 edit undoA1Cafel (talk | contribs)Extended confirmed users, Pending changes reviewers, Rollbackers10,511 editsNo edit summary 
(64 intermediate revisions by 44 users not shown)
Line 1: Line 1:
{{Short description|Typhoon season in the Western Pacific Ocean}} {{Short description|none}} <!-- "none" is a legitimate description when the title is already adequate; see ] -->
{{Infobox tropical cyclone season {{Infobox tropical cyclone season
| Basin = WPac | Basin = WPac
Line 15: Line 15:
| Total intense = 7 (unofficial) | Total intense = 7 (unofficial)
| Fatalities = 793 total | Fatalities = 793 total
| Damages = 31540 <!-- 31,537.556 --> | Damages = 30540 <!-- 30,537.556 -->
| Damagespost = Second-costliest Pacific typhoon season on record | Damagespost = Third-costliest Pacific typhoon season on record
| five seasons = ], ], '''2018''', ], ] | five seasons = ], ], '''2018''', ], ]
| Season timeline = Timeline of the 2018 Pacific typhoon season | Season timeline = Timeline of the 2018 Pacific typhoon season
Line 23: Line 23:
| North Indian season = 2018 North Indian Ocean cyclone season | North Indian season = 2018 North Indian Ocean cyclone season
}} }}
The '''2018 Pacific typhoon season''' was at the time, the costliest Pacific typhoon season on record, until the record was beaten by the ]. The season was well above-average, producing 29 storms, 13 typhoons, and 7 super typhoons. It was an event in the annual cycle of ] formation, in which tropical cyclones form in the western Pacific Ocean. The season ran throughout 2018, though most tropical cyclones typically ] between May and October. The season's first named storm, ], developed on January 3, while the season's last named storm, Man-yi, dissipated on November 28. The season's first typhoon, Jelawat, reached typhoon status on March 29, and became the first super typhoon of the year on the next day. The '''2018 Pacific typhoon season''' was at the time, the costliest Pacific typhoon season on record, until the record was beaten by the ]. The season was well above-average, producing twenty-nine storms (including one that crossed over from the Eastern/Central Pacific), thirteen typhoons, seven super typhoons and six ]. The season ran throughout 2018, though most tropical cyclones typically ] between May and October. The season's first named storm, ], developed on January 3, while the season's last named storm, Man-yi, dissipated on November 28. The season's first typhoon, Jelawat, reached typhoon status on March 29, and became the first super typhoon of the year on the next day.


The scope of this article is limited to the Pacific Ocean, to the north of the equator between ] and the ]. Within the northwestern Pacific Ocean, there are two separate agencies that assign names to tropical cyclones, which can often result in a cyclone having two names, one from the JMA and one from PAGASA. The ]&nbsp;<small>(JMA)</small> will name a tropical cyclone should it be judged to have 10-minute ] of at least {{convert|65|km/h|mph|abbr=on}} anywhere in the basin, while the ]&nbsp;<small>(PAGASA)</small> assigns 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 regardless of whether or not a tropical cyclone has already been given a name by the JMA. Tropical depressions that are monitored by the United States' ]&nbsp;<small>(JTWC)</small> are given a number with a "W" suffix. The scope of this article is limited to the Pacific Ocean, to the north of the equator between ] and the ]. Within the northwestern Pacific Ocean, there are two separate agencies that assign names to tropical cyclones, which can often result in a cyclone having two names, one from the JMA and one from PAGASA. The ]&nbsp;<small>(JMA)</small> will name a tropical cyclone should it be judged to have 10-minute ] of at least {{convert|65|km/h|mph|abbr=on}} anywhere in the basin, while the ]&nbsp;<small>(PAGASA)</small> assigns 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 regardless of whether or not a tropical cyclone has already been given a name by the JMA. Tropical depressions that are monitored by the United States' ]&nbsp;<small>(JTWC)</small> are given a number with a "W" suffix.
Line 79: Line 79:
<div class="center"> <div class="center">
<timeline> <timeline>
ImageSize = width:1030 height:340 ImageSize = width:1100 height:300
PlotArea = top:10 bottom:80 right:20 left:20 PlotArea = top:10 bottom:80 right:20 left:20
Legend = columns:2 left:30 top:58 columnwidth:270 Legend = columns:3 left:30 top:58 columnwidth:270
AlignBars = early AlignBars = early
DateFormat = dd/mm/yyyy DateFormat = dd/mm/yyyy
Period = from:01/12/2017 till:01/02/2019 Period = from:23/12/2017 till:08/01/2019
TimeAxis = orientation:horizontal TimeAxis = orientation:horizontal
ScaleMinor = grid:black unit:month increment:1 start:31/12/2017 ScaleMinor = grid:black unit:month increment:1 start:31/12/2017
Line 107: Line 107:
from:10/05/2018 till:15/05/2018 color:TD text:"04W" from:10/05/2018 till:15/05/2018 color:TD text:"04W"
from:02/06/2018 till:09/06/2018 color:TS text:"]" from:02/06/2018 till:09/06/2018 color:TS text:"]"
from:03/06/2018 till:11/06/2018 color:ST text:"Maliksi" from:03/06/2018 till:11/06/2018 color:ST text:"]"
from:04/06/2018 till:05/06/2018 color:TD text:"TD" from:04/06/2018 till:05/06/2018 color:TD text:"TD"
from:13/06/2018 till:15/06/2018 color:TS text:"07W" from:13/06/2018 till:15/06/2018 color:TS text:"07W"
Line 116: Line 116:
from:16/07/2018 till:24/07/2018 color:TS text:"]" from:16/07/2018 till:24/07/2018 color:TS text:"]"
from:16/07/2018 till:17/07/2018 color:TD text:"TD" from:16/07/2018 till:17/07/2018 color:TD text:"TD"
barset:break
from:17/07/2018 till:24/07/2018 color:ST text:"]" from:17/07/2018 till:24/07/2018 color:ST text:"]"
from:20/07/2018 till:23/07/2018 color:TD text:"]" from:20/07/2018 till:23/07/2018 color:TD text:"]"
from:22/07/2018 till:26/07/2018 color:ST text:"Wukong" from:22/07/2018 till:26/07/2018 color:ST text:"Wukong"
from:23/07/2018 till:04/08/2018 color:STY text:"]" from:23/07/2018 till:04/08/2018 color:STY text:"]"
barset:break
from:31/07/2018 till:02/08/2018 color:TD text:"16W" from:31/07/2018 till:02/08/2018 color:TD text:"16W"
from:02/08/2018 till:10/08/2018 color:STY text:"Shanshan" from:02/08/2018 till:10/08/2018 color:STY text:"]"
from:06/08/2018 till:15/08/2018 color:TS text:"]" from:06/08/2018 till:15/08/2018 color:TS text:"]"
from:09/08/2018 till:17/08/2018 color:TS text:"]" from:09/08/2018 till:17/08/2018 color:TS text:"]"
Line 131: Line 131:
from:16/08/2018 till:24/08/2018 color:VSTY text:"]" from:16/08/2018 till:24/08/2018 color:VSTY text:"]"
from:22/08/2018 till:26/08/2018 color:TD text:"Luis" from:22/08/2018 till:26/08/2018 color:TD text:"Luis"
barset:break
from:24/08/2018 till:26/08/2018 color:TD text:"TD" from:24/08/2018 till:26/08/2018 color:TD text:"TD"
from:26/08/2018 till:04/09/2018 color:VITY text:"]" from:26/08/2018 till:04/09/2018 color:VITY text:"]"
from:05/09/2018 till:08/09/2018 color:TD text:"TD" from:05/09/2018 till:08/09/2018 color:TD text:"TD"
from:06/09/2018 till:17/09/2018 color:VITY text:"]" from:06/09/2018 till:17/09/2018 color:VITY text:"]"
from:08/09/2018 till:13/09/2018 color:TS text:"]" from:08/09/2018 till:13/09/2018 color:TS text:"]"
from:20/09/2018 till:30/09/2018 color:VITY text:"]" from:20/09/2018 till:30/09/2018 color:VITY text:"]"
from:21/09/2018 till:23/09/2018 color:TD text:"TD" from:21/09/2018 till:23/09/2018 color:TD text:"TD"
from:25/09/2018 till:27/09/2018 color:TD text:"29W" from:25/09/2018 till:27/09/2018 color:TD text:"29W"
barset:break
from:28/09/2018 till:06/10/2018 color:VITY text:"]" from:28/09/2018 till:06/10/2018 color:VITY text:"]"
from:19/10/2018 till:20/10/2018 color:TD text:"TD" from:19/10/2018 till:20/10/2018 color:TD text:"TD"
Line 146: Line 146:
from:16/11/2018 till:18/11/2018 color:TS text:"]" from:16/11/2018 till:18/11/2018 color:TS text:"]"
from:20/11/2018 till:28/11/2018 color:STY text:"Man-yi" from:20/11/2018 till:28/11/2018 color:STY text:"Man-yi"
barset:break
from:25/12/2018 till:29/12/2018 color:TD text:"]" from:25/12/2018 till:29/12/2018 color:TD text:"]"
from:31/12/2018 till:04/01/2019 color:TS text:"]" from:31/12/2018 till:04/01/2019 color:TS text:"]"


bar:Month width:5 align:center fontsize:S shift:(0,-20) anchor:middle color:canvas bar:Month width:5 align:center fontsize:S shift:(0,-20) anchor:middle color:canvas
from:01/12/2017 till:01/01/2018 text:December '17 from:23/12/2017 till:01/01/2018 text:Dec '17
from:01/01/2018 till:01/02/2018 text:January from:01/01/2018 till:01/02/2018 text:January
from:01/02/2018 till:01/03/2018 text:February from:01/02/2018 till:01/03/2018 text:February
Line 163: Line 164:
from:01/11/2018 till:01/12/2018 text:November from:01/11/2018 till:01/12/2018 text:November
from:01/12/2018 till:01/01/2019 text:December from:01/12/2018 till:01/01/2019 text:December
from:01/01/2019 till:01/02/2019 text:January '19 from:01/01/2019 till:08/01/2019 text:Jan '19


</timeline> </timeline>
Line 172: Line 173:
On August 16, Typhoon Soulik developed and headed north, until a Fujiwhara interaction with Typhoon Cimaron (which formed after Soulik) made it head west towards the ]. It later made landfall on ], making it the first typhoon to make landfall on South Korea since ] in 2016. Cimaron made landfall near ], ] on August 23. As Cimaron was nearing landfall, Tropical Depression Luis formed, which made landfall on China and Taiwan. Later that month, Typhoon Jebi developed over the West Pacific and intensified into the third super typhoon of the season. On August 16, Typhoon Soulik developed and headed north, until a Fujiwhara interaction with Typhoon Cimaron (which formed after Soulik) made it head west towards the ]. It later made landfall on ], making it the first typhoon to make landfall on South Korea since ] in 2016. Cimaron made landfall near ], ] on August 23. As Cimaron was nearing landfall, Tropical Depression Luis formed, which made landfall on China and Taiwan. Later that month, Typhoon Jebi developed over the West Pacific and intensified into the third super typhoon of the season.


In September, ] became the fourth super typhoon of the season and made landfall on the island of ] in the ].<ref>{{cite web |last1=Griffiths |first1=James |title=Philippines lashed by Typhoon Mangkhut, strongest storm this year |date=14 September 2018 |url=https://www.cnn.com/2018/09/14/asia/super-typhoon-mangkhut-ompong-wxc-intl/index.html |publisher=Cable News Network |access-date=22 September 2018 |ref=176 |archive-date=15 September 2018 |archive-url=https://web.archive.org/web/20180915233513/https://www.cnn.com/2018/09/14/asia/super-typhoon-mangkhut-ompong-wxc-intl/index.html |url-status=live }}</ref> On the same day, Tropical Depression Neneng formed, which later became Tropical Storm Barijat and made landfall on Vietnam. By late September, Typhoon Trami (Paeng) formed, becoming the 5th super typhoon of 2018. While ] was in the Western Pacific, nearing ] with winds of {{convert|165|km/h|mph|abbr=on}}, Tropical Depression 30W formed, and was named ''Kong-rey'' by the JMA after strengthening into a tropical storm. It intensified into a super typhoon on October 2, becoming the 5th ] super typhoon. Later on in the month, it was followed by the sixth and final Category 5-equivalent storm of the season, Yutu. In September, ] became the fourth super typhoon of the season and made landfall on the island of ] in the ].<ref>{{cite web |last1=Griffiths |first1=James |title=Philippines lashed by Typhoon Mangkhut, strongest storm this year |date=14 September 2018 |url=https://www.cnn.com/2018/09/14/asia/super-typhoon-mangkhut-ompong-wxc-intl/index.html |publisher=Cable News Network |access-date=22 September 2018 |ref=176 |archive-date=15 September 2018 |archive-url=https://web.archive.org/web/20180915233513/https://www.cnn.com/2018/09/14/asia/super-typhoon-mangkhut-ompong-wxc-intl/index.html |url-status=live }}</ref> On the same day, Tropical Depression Neneng formed, which later became Tropical Storm Barijat and made landfall on Vietnam. By late September, Typhoon Trami (Paeng) formed, becoming the 5th super typhoon of 2018. While ] was in the Western Pacific, nearing ] with winds of {{convert|165|km/h|mph|abbr=on}}, Tropical Depression 30W formed, and was named ''Kong-rey'' by the JMA after strengthening into a tropical storm. It intensified into a super typhoon on October 2, becoming the 5th ] super typhoon. Later on in the month, it was followed by the sixth and final Category 5-equivalent storm of the season, Yutu.


==Systems== ==Systems==
Line 187: Line 188:
}} }}
{{main|Tropical Storm Bolaven (2018)}} {{main|Tropical Storm Bolaven (2018)}}
A low-pressure area developed into a tropical depression northeast of ] on December 29, 2017.<ref>{{Cite web|url=http://www.wis-jma.go.jp/cms/warning/2017/12/30/marine-weather-warning-for-gmdss-metarea-xi-2017-12-30t060000z/|title=Marine Weather Warning for GMDSS Metarea XI 2017-12-30T06:00:00Z|date=December 30, 2017|website=WIS Portal – GISC Tokyo|publisher=Japan Meteorological Agency|access-date=December 30, 2017}}</ref> The system moved generally westward, and on the first day of 2018, the PAGASA began issuing advisories on the system and locally named it ''Agaton''.<ref>{{cite web|title=Storm Signal No. 1 raised in several areas as LPA turns into depression|url=https://newsinfo.inquirer.net/956694/td-agaton-pagasa|date=January 1, 2018|publisher=Inquirer|author=Jhoanna Ballaran|access-date=February 16, 2018|archive-date=January 2, 2018|archive-url=https://web.archive.org/web/20180102073727/https://newsinfo.inquirer.net/956694/td-agaton-pagasa|url-status=live}}</ref> Both the JMA and the JTWC followed suit, with the latter designating the system as ''01W''.<ref>{{cite web|title=Tropical Depression 01W (One) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201801012100.htm|archive-url=https://www.webcitation.org/6wAQehJzZ?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201801012100.htm|url-status=dead|date=January 1, 2018|archive-date=January 2, 2018|publisher=Joint Typhoon Warning Center}}</ref> The depression reached the Philippines on January&nbsp;1, making ] over ] at 17:00&nbsp;UTC, then at ] at 17:15&nbsp;UTC.<ref name="landfalls">{{cite news |title=Tropical Depression Agaton makes 6th landfall in Palawan |url=https://www.rappler.com/nation/special-coverage/weather-alert/192761-20180102-tropical-depression-agaton-pagasa-forecast-11pm |access-date=May 16, 2020 |work=Rappler |date=January 2, 2018}}</ref> The system crossed the ] before making a third landfall near ] at 20:00&nbsp;UTC, a fourth in ] at 21:00&nbsp;UTC, and a final landfall at ] at 23:30&nbsp;UTC.<ref name="landfalls"/> By January 3, the system had intensified into a tropical storm according to the JMA and was named ''Bolaven'', thus becoming the first named storm of the season. However, several hours later, Bolaven started to weaken and rapidly deteriorate.<ref>{{cite web|title=Tropical Depression 01W (Bolaven) Warning Nr 010|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201801040300.htm|archive-url=https://www.webcitation.org/6wDputLB4?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201801040300.htm|url-status=dead|date=January 4, 2018|archive-date=January 4, 2018|publisher=Joint Typhoon Warning Center}}</ref> The system was last tracked by the JMA to the east of ] on January 4. A low-pressure area developed into a tropical depression northeast of ] on December 29, 2017.<ref>{{Cite web|url=http://www.wis-jma.go.jp/cms/warning/2017/12/30/marine-weather-warning-for-gmdss-metarea-xi-2017-12-30t060000z/|title=Marine Weather Warning for GMDSS Metarea XI 2017-12-30T06:00:00Z|date=December 30, 2017|website=WIS Portal – GISC Tokyo|publisher=Japan Meteorological Agency|access-date=December 30, 2017}}</ref> The system moved generally westward, and on the first day of 2018, the PAGASA began issuing advisories on the system and locally named it ''Agaton''.<ref>{{cite web|title=Storm Signal No. 1 raised in several areas as LPA turns into depression|url=https://newsinfo.inquirer.net/956694/td-agaton-pagasa|date=January 1, 2018|publisher=Inquirer|author=Jhoanna Ballaran|access-date=February 16, 2018|archive-date=January 2, 2018|archive-url=https://web.archive.org/web/20180102073727/https://newsinfo.inquirer.net/956694/td-agaton-pagasa|url-status=live}}</ref> Both the JMA and the JTWC followed suit, with the latter designating the system as ''01W''.<ref>{{cite web|title=Tropical Depression 01W (One) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201801012100.htm|archive-url=https://archive.today/20240524021115/https://www.webcitation.org/6wAQehJzZ?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201801012100.htm|url-status=dead|date=January 1, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> The depression reached the Philippines on January&nbsp;1, making ] over ] at 17:00&nbsp;UTC, then at ] at 17:15&nbsp;UTC.<ref name="landfalls">{{cite news |title=Tropical Depression Agaton makes 6th landfall in Palawan |url=https://www.rappler.com/nation/special-coverage/weather-alert/192761-20180102-tropical-depression-agaton-pagasa-forecast-11pm |access-date=May 16, 2020 |work=Rappler |date=January 2, 2018}}</ref> The system crossed the ] before making a third landfall near ] at 20:00&nbsp;UTC, a fourth in ] at 21:00&nbsp;UTC, and a final landfall at ] at 23:30&nbsp;UTC.<ref name="landfalls"/> By January 3, the system had intensified into a tropical storm according to the JMA and was named ''Bolaven'', thus becoming the first named storm of the season. However, several hours later, Bolaven started to weaken and rapidly deteriorate.<ref>{{cite web|title=Tropical Depression 01W (Bolaven) Warning Nr 010|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201801040300.htm|archive-url=https://archive.today/20240524021202/https://www.webcitation.org/6wDputLB4?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201801040300.htm|url-status=dead|date=January 4, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> The system was last tracked by the JMA to the east of ] on January 4.


The impact caused by Bolaven (Agaton) was moderate but not as significant as the previous two systems, ] and ], with about 2,000 passengers stranded in ports in the ].<ref>{{cite web|title=More than 2,000 passengers stranded due to 'Agaton'|url=http://www.sunstar.com.ph/manila/local-news/2018/01/02/more-2000-passengers-stranded-due-agaton-582023|date=January 2, 2018|publisher=Sunstar Philippines|access-date=February 16, 2018|archive-date=January 5, 2018|archive-url=https://web.archive.org/web/20180105011028/http://www.sunstar.com.ph/manila/local-news/2018/01/02/more-2000-passengers-stranded-due-agaton-582023|url-status=live}}</ref> As of January 22, three people have been reported killed by the storm, while total damages were up to ]554.7 million (US$11.1 million).<ref name="Bolaven1">{{cite web|url=http://www.ndrrmc.gov.ph/attachments/article/3276/SitRep_No_13_re_Preparedness_Measures_and_Effects_of_TD_Agaton_as_of_0800H_22Jan2018.pdf|title=SitRep No. 13 re Preparedness Measures and Effects of Tropical Depression "AGATON"|date=January 22, 2018|access-date=January 22, 2018|archive-date=February 9, 2018|archive-url=https://web.archive.org/web/20180209073210/http://www.ndrrmc.gov.ph/attachments/article/3276/SitRep_No_13_re_Preparedness_Measures_and_Effects_of_TD_Agaton_as_of_0800H_22Jan2018.pdf|url-status=live}}</ref> The impact caused by Bolaven (Agaton) was moderate but not as significant as the previous two systems, ] and ], with about 2,000 passengers stranded in ports in the ].<ref>{{cite web|title=More than 2,000 passengers stranded due to 'Agaton'|url=http://www.sunstar.com.ph/manila/local-news/2018/01/02/more-2000-passengers-stranded-due-agaton-582023|date=January 2, 2018|publisher=Sunstar Philippines|access-date=February 16, 2018|archive-date=January 5, 2018|archive-url=https://web.archive.org/web/20180105011028/http://www.sunstar.com.ph/manila/local-news/2018/01/02/more-2000-passengers-stranded-due-agaton-582023|url-status=live}}</ref> As of January 22, three people have been reported killed by the storm, while total damages were up to ]554.7 million (US$11.1 million).<ref name="Bolaven1">{{cite web|url=http://www.ndrrmc.gov.ph/attachments/article/3276/SitRep_No_13_re_Preparedness_Measures_and_Effects_of_TD_Agaton_as_of_0800H_22Jan2018.pdf|title=SitRep No. 13 re Preparedness Measures and Effects of Tropical Depression "AGATON"|date=January 22, 2018|access-date=January 22, 2018|archive-date=February 9, 2018|archive-url=https://web.archive.org/web/20180209073210/http://www.ndrrmc.gov.ph/attachments/article/3276/SitRep_No_13_re_Preparedness_Measures_and_Effects_of_TD_Agaton_as_of_0800H_22Jan2018.pdf|url-status=live}}</ref>
Line 206: Line 207:
A low-pressure system developed into a tropical depression north of ] early on February 8. It developed into a tropical storm on February 11, receiving the international name ''Sanba'' by the JMA. Shortly afterwards, ''Sanba'' entered the Philippine area of responsibility and was assigned the local name ''Basyang'' by the PAGASA.<ref>{{cite web|url=https://www.rappler.com/nation/special-coverage/weather-alert/195897-20180213-tropical-storm-basyang-pagasa-forecast-8am|title=Tropical Storm Basyang makes landfall in Surigao del Sur|date=13 February 2018 |access-date=2018-04-08|archive-date=2018-02-13|archive-url=https://web.archive.org/web/20180213080047/https://www.rappler.com/nation/special-coverage/weather-alert/195897-20180213-tropical-storm-basyang-pagasa-forecast-8am|url-status=live}}</ref> On February 13, ''Sanba'' made landfall on Cortes, Surigao Del Sur,<ref name="PAG 3">{{cite web|url=https://www.garda.com/crisis24/news-alerts/90236/philippines-tropical-storm-sanba-makes-landfall-february-13-update-1|title=Philippines: Tropical Storm Sanba makes landfall February 13 /update 1}}</ref> causing it to weaken to a tropical depression. On the next day, the system weakened into a ] as it made another ] in ].<ref>{{cite web|url=http://news.abs-cbn.com/news/02/13/18/basyang-weakens-after-pounding-surigao|title='Basyang' weakens after pounding Surigao|date=February 13, 2018|access-date=April 8, 2018|archive-date=April 8, 2018|archive-url=https://web.archive.org/web/20180408205757/http://news.abs-cbn.com/news/02/13/18/basyang-weakens-after-pounding-surigao|url-status=live}}</ref> A low-pressure system developed into a tropical depression north of ] early on February 8. It developed into a tropical storm on February 11, receiving the international name ''Sanba'' by the JMA. Shortly afterwards, ''Sanba'' entered the Philippine area of responsibility and was assigned the local name ''Basyang'' by the PAGASA.<ref>{{cite web|url=https://www.rappler.com/nation/special-coverage/weather-alert/195897-20180213-tropical-storm-basyang-pagasa-forecast-8am|title=Tropical Storm Basyang makes landfall in Surigao del Sur|date=13 February 2018 |access-date=2018-04-08|archive-date=2018-02-13|archive-url=https://web.archive.org/web/20180213080047/https://www.rappler.com/nation/special-coverage/weather-alert/195897-20180213-tropical-storm-basyang-pagasa-forecast-8am|url-status=live}}</ref> On February 13, ''Sanba'' made landfall on Cortes, Surigao Del Sur,<ref name="PAG 3">{{cite web|url=https://www.garda.com/crisis24/news-alerts/90236/philippines-tropical-storm-sanba-makes-landfall-february-13-update-1|title=Philippines: Tropical Storm Sanba makes landfall February 13 /update 1}}</ref> causing it to weaken to a tropical depression. On the next day, the system weakened into a ] as it made another ] in ].<ref>{{cite web|url=http://news.abs-cbn.com/news/02/13/18/basyang-weakens-after-pounding-surigao|title='Basyang' weakens after pounding Surigao|date=February 13, 2018|access-date=April 8, 2018|archive-date=April 8, 2018|archive-url=https://web.archive.org/web/20180408205757/http://news.abs-cbn.com/news/02/13/18/basyang-weakens-after-pounding-surigao|url-status=live}}</ref>


A total of 1,660 houses were damaged, of which 429 were completely destroyed; most of the homes damaged were in ]. ] Island, ], ] municipality in ], and the municipalities of ] and ] in ] were affected by power outages from February&nbsp;12 to 13. Twenty-two roads and eight bridges were damaged by floods and landslides.<ref name="SitRep 11">{{cite report|url=http://www.ndrrmc.gov.ph/attachments/article/3317/SitRep_No_11_re_Preparedness_Measures_and_Effect_for_TS_Basyang_SANBA_as_of_23FEB2018_0800H.pdf|title=SitRep No. 11 re Preparedness Measures and Effects for Tropical Storm "BASYANG" (I.N. SANBA)|publisher=National Disaster Risk Reduction and Management Council|date=February 23, 2018|archive-url=https://web.archive.org/web/20181012193123/http://www.ndrrmc.gov.ph/attachments/article/3317/SitRep_No_11_re_Preparedness_Measures_and_Effect_for_TS_Basyang_SANBA_as_of_23FEB2018_0800H.pdf|archive-date=October 12, 2018|url-status=live|access-date=February 26, 2018}}</ref> A total of 1,660 houses were damaged, of which 429 were completely destroyed; most of the homes damaged were in ]. ] Island, ], ] municipality in ], and the municipalities of ] and ] in ] were affected by power outages from February&nbsp;12 to 13. Twenty-two roads and eight bridges were damaged by floods and landslides.<ref name="SitRep 11">{{cite report|url=http://www.ndrrmc.gov.ph/attachments/article/3317/SitRep_No_11_re_Preparedness_Measures_and_Effect_for_TS_Basyang_SANBA_as_of_23FEB2018_0800H.pdf|title=SitRep No. 11 re Preparedness Measures and Effects for Tropical Storm "BASYANG" (I.N. SANBA)|publisher=National Disaster Risk Reduction and Management Council|date=February 23, 2018|archive-url=https://web.archive.org/web/20181012193123/http://www.ndrrmc.gov.ph/attachments/article/3317/SitRep_No_11_re_Preparedness_Measures_and_Effect_for_TS_Basyang_SANBA_as_of_23FEB2018_0800H.pdf|archive-date=October 12, 2018|url-status=live|access-date=February 26, 2018}}</ref> Two boats carrying people capsized: a fishing boat near ], and a passenger vessel en route to ]. All four on board the two boats survived. Approximately 17,000 people were affected by the storm and there were 14 fatalities. Total agricultural damages were at ] 168 million (US$3.23 million), mostly coming from flooded rice fields.<ref name="Sanba2">{{cite web|url=http://www.ndrrmc.gov.ph/attachments/article/3317/SitRep_No_11_re_Preparedness_Measures_and_Effect_for_TS_Basyang_SANBA_as_of_23FEB2018_0800H.pdf|title=SitRep No. 11 re Preparedness Measures and Effects for Tropical Storm "BASYANG"|date=February 23, 2018|access-date=September 10, 2018|archive-date=October 12, 2018|archive-url=https://web.archive.org/web/20181012193123/http://www.ndrrmc.gov.ph/attachments/article/3317/SitRep_No_11_re_Preparedness_Measures_and_Effect_for_TS_Basyang_SANBA_as_of_23FEB2018_0800H.pdf|url-status=live}}</ref>

Two boats carrying people capsized: a fishing boat near ], and a passenger vessel en route to ]. All four on board the two boats survived.

Approximately 17,000 people were affected by the storm and there were 14 fatalities. Total agricultural damages were at ] 168 million (US$3.23 million), mostly coming from flooded rice fields.<ref name="Sanba2">{{cite web|url=http://www.ndrrmc.gov.ph/attachments/article/3317/SitRep_No_11_re_Preparedness_Measures_and_Effect_for_TS_Basyang_SANBA_as_of_23FEB2018_0800H.pdf|title=SitRep No. 11 re Preparedness Measures and Effects for Tropical Storm "BASYANG"|date=February 23, 2018|access-date=September 10, 2018|archive-date=October 12, 2018|archive-url=https://web.archive.org/web/20181012193123/http://www.ndrrmc.gov.ph/attachments/article/3317/SitRep_No_11_re_Preparedness_Measures_and_Effect_for_TS_Basyang_SANBA_as_of_23FEB2018_0800H.pdf|url-status=live}}</ref>
{{clear}} {{clear}}


Line 219: Line 216:
| Dissipated = April 1 | Dissipated = April 1
| Image = Jelawat 2018-03-30 0410Z.jpg | Image = Jelawat 2018-03-30 0410Z.jpg
| Track = Jelawat 2018 track.png | Track = Jelawat 2018 path.png
| 10-min winds = 105 | 10-min winds = 105
| 1-min winds = 130 | 1-min winds = 130
| Pressure = 915 | Pressure = 915
}}{{Main|Typhoon Jelawat (2018)}} }}{{Main|Typhoon Jelawat (2018)}}
On March 24, a tropical depression formed to the south of the ],<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803240000.htm |title=6yAE5Nl2l |access-date=2018-03-24 |archive-url=https://www.webcitation.org/6yAE5Nl2l?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803240000.htm |archive-date=2018-03-24 |url-status=dead }}</ref> and the JTWC assigned it the numerical identifier ''03W''.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201803242100.htm |title=6yBF3lHZz |access-date=2018-03-25 |archive-url=https://www.webcitation.org/6yBF3lHZz?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201803242100.htm |archive-date=2018-03-25 |url-status=dead }}</ref> On March 25, the system intensified into a tropical storm and was named ''Jelawat'' by the JMA, and at the same time it entered ]'s ] (PAR) and was assigned the local name ''Caloy''.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803250600.htm |title=6yBF7pyWZ |access-date=2018-03-25 |archive-url=https://www.webcitation.org/6yBF7pyWZ?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803250600.htm |archive-date=2018-03-25 |url-status=dead }}</ref> Due to strong southwesterly wind shear, the cyclone remained poorly organized, with disorganized convection near an exposed low-level circulation.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201803260300.htm |title=6yCiZiQTo |access-date=2018-03-26 |archive-url=https://www.webcitation.org/6yCiZiQTo?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201803260300.htm |archive-date=2018-03-26 |url-status=dead }}</ref> Conditions gradually became more favorable for further development, resulting in Jelawat steadily strengthening and gaining organization before intensifying into a severe tropical storm at 18:00&nbsp;UTC on March 28.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803281800.htm |title=6yHP5U1lz |access-date=2018-03-29 |archive-url=https://www.webcitation.org/6yHP5U1lz?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803281800.htm |archive-date=2018-03-29 |url-status=dead }}</ref> Later on March 29, an ] began to emerge within a growing ], leading to the JMA classifying it as a typhoon at 00:00&nbsp;UTC on March 29.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803300000.htm |title=6yIu7LyVR |access-date=2018-03-30 |archive-url=https://www.webcitation.org/6yIu7LyVR?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803300000.htm |archive-date=2018-03-30 |url-status=dead }}</ref> ] then ensued over the following 36 hours as the eye became sharply defined, and Jelawat attained its peak intensity later that morning, with estimated 10-minute sustained winds of {{convert|195|km/h|mph|abbr=on}} and a central pressure of {{convert|915|hPa|inHg|abbr=on}}.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803301200.htm |title=6yKn1AxSi |access-date=2018-03-31 |archive-url=https://www.webcitation.org/6yKn1AxSi?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803301200.htm |archive-date=2018-03-31 |url-status=dead }}</ref> At the same time, the JTWC assessed it as peaking with 1-minute sustained winds of {{convert|240|km/h|mph|abbr=on}}, making it a Category 4 super typhoon.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201803301500.htm |title=6yKnKMxc1 |access-date=2018-03-31 |archive-url=https://www.webcitation.org/6yKnKMxc1?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201803301500.htm |archive-date=2018-03-31 |url-status=dead }}</ref> On March 24, a tropical depression formed to the south of the ],<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803240000.htm |title=6yAE5Nl2l |access-date=2018-03-24 |archive-url=https://archive.today/20240524021235/https://www.webcitation.org/6yAE5Nl2l?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803240000.htm |archive-date=2024-05-24 |url-status=dead }}</ref> and the JTWC assigned it the numerical identifier ''03W''.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201803242100.htm |title=6yBF3lHZz |access-date=2018-03-25 |archive-url=https://archive.today/20240524021316/https://www.webcitation.org/6yBF3lHZz?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201803242100.htm |archive-date=2024-05-24 |url-status=dead }}</ref> On March 25, the system intensified into a tropical storm and was named ''Jelawat'' by the JMA, and at the same time it entered ]'s ] (PAR) and was assigned the local name ''Caloy''.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803250600.htm |title=6yBF7pyWZ |access-date=2018-03-25 |archive-url=https://archive.today/20240524021358/https://www.webcitation.org/6yBF7pyWZ?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803250600.htm |archive-date=2024-05-24 |url-status=dead }}</ref> Due to strong southwesterly wind shear, the cyclone remained poorly organized, with disorganized convection near an exposed low-level circulation.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201803260300.htm |title=6yCiZiQTo |access-date=2018-03-26 |archive-url=https://archive.today/20240524021437/https://www.webcitation.org/6yCiZiQTo?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201803260300.htm |archive-date=2024-05-24 |url-status=dead }}</ref> Conditions gradually became more favorable for further development, resulting in Jelawat steadily strengthening and gaining organization before intensifying into a severe tropical storm at 18:00&nbsp;UTC on March 28.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803281800.htm |title=6yHP5U1lz |access-date=2018-03-29 |archive-url=https://archive.today/20240524021516/https://www.webcitation.org/6yHP5U1lz?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803281800.htm |archive-date=2024-05-24 |url-status=dead }}</ref> Later on March 29, an ] began to emerge within a growing ], leading to the JMA classifying it as a typhoon at 00:00&nbsp;UTC on March 29.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803300000.htm |title=6yIu7LyVR |access-date=2018-03-30 |archive-url=https://archive.today/20240524021557/https://www.webcitation.org/6yIu7LyVR?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803300000.htm |archive-date=2024-05-24 |url-status=dead }}</ref> ] then ensued over the following 36 hours as the eye became sharply defined, and Jelawat attained its peak intensity later that morning, with estimated 10-minute sustained winds of {{convert|195|km/h|mph|abbr=on}} and a central pressure of {{convert|915|hPa|inHg|abbr=on}}.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803301200.htm |title=6yKn1AxSi |access-date=2018-03-31 |archive-url=https://archive.today/20240524021636/https://www.webcitation.org/6yKn1AxSi?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201803301200.htm |archive-date=2024-05-24 |url-status=dead }}</ref> At the same time, the JTWC assessed it as peaking with 1-minute sustained winds of {{convert|240|km/h|mph|abbr=on}}, making it a Category 4 super typhoon.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201803301500.htm |title=6yKnKMxc1 |access-date=2018-03-31 |archive-url=https://archive.today/20240524021719/https://www.webcitation.org/6yKnKMxc1?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201803301500.htm |archive-date=2024-05-24 |url-status=dead }}</ref>


Immediately after peaking in intensity, Jelawat began weakening rapidly due to a sharp increase in wind shear and dry air, and the storm fell below typhoon strength late on March 31. During the next couple of days, Jelawat drifted to the northeast and then turned eastward before dissipating on April 1. Immediately after peaking in intensity, Jelawat began weakening rapidly due to a sharp increase in wind shear and dry air, and the storm fell below typhoon strength late on March 31. During the next couple of days, Jelawat drifted to the northeast and then turned eastward before dissipating on April 1.


Jelawat yielded 20 inches of rainfall on parts of the island of ], resulting in flooding and landslides that caused critical damage to infrastructure and one death.<ref>{{Cite web |date=March 20, 2019 |title=Newsletter 1QTR2019 |url=https://www.weather.gov/media/peac/PEU/Newsletter%201QTR2019.pdf |website=www.weather.gov}}</ref><ref>{{Cite web |date=October 20, 2020 |title=FSM and RMI Program Summary |url=https://2017-2020.usaid.gov/sites/default/files/documents/FSM_and_RMI_Program_Summary_Revised_10_20_2020.pdf |website=www.usaid.gov}}</ref> A woman in Guam drowned from the remnants of Jelawat on April 3,<ref>{{Cite web |title=Quarterly Climate Impacts and Outlook |url=https://www.drought.gov/sites/default/files/2020-07/Pacific%20Spring%202018.pdf |access-date=2022-12-20}}</ref> after strong surf and rip currents stranded her in water.<ref>{{Cite web |last=Post |first=Meghan Swartz {{!}} The Guam Daily |title=Don't risk going in rough waters, expert says |url=https://www.postguam.com/news/local/dont-risk-going-in-rough-waters-expert-says/article_9cc6613e-3727-11e8-9f8f-4fb2a004f08c.html |access-date=2022-12-03 |website=The Guam Daily Post |language=en}}</ref> Jelawat yielded 20 inches of rainfall on parts of the island of ], resulting in flooding and landslides that caused critical damage to infrastructure and one death.<ref>{{Cite web |date=March 20, 2019 |title=Newsletter 1QTR2019 |url=https://www.weather.gov/media/peac/PEU/Newsletter%201QTR2019.pdf |website=www.weather.gov}}</ref><ref>{{Cite web |date=October 20, 2020 |title=FSM and RMI Program Summary |url=https://2017-2020.usaid.gov/sites/default/files/documents/FSM_and_RMI_Program_Summary_Revised_10_20_2020.pdf |website=www.usaid.gov}}</ref> A woman in Guam drowned from the remnants of Jelawat on April 3,<ref>{{Cite web |title=Quarterly Climate Impacts and Outlook |url=https://www.drought.gov/sites/default/files/2020-07/Pacific%20Spring%202018.pdf |access-date=2022-12-20}}</ref> after strong surf and rip currents stranded her in water.<ref>{{Cite web |last=Post |first=Meghan Swartz {{!}} The Guam Daily |title=Don't risk going in rough waters, expert says |url=https://www.postguam.com/news/local/dont-risk-going-in-rough-waters-expert-says/article_9cc6613e-3727-11e8-9f8f-4fb2a004f08c.html |access-date=2022-12-03 |website=The Guam Daily Post |date=4 April 2018 |language=en}}</ref>
{{clear}} {{clear}}


Line 242: Line 239:
| Pressure = 1008 | Pressure = 1008
}} }}
A low-pressure area east of ] was upgraded to a tropical depression by the JMA late on May 10 shortly before the JTWC issued a ].<ref>{{Cite web|url=http://www.wis-jma.go.jp/cms/warning/2018/05/10/marine-weather-warning-for-gmdss-metarea-xi-2018-05-10t180000z/|title=Marine Weather Warning for GMDSS Metarea XI 2018-05-10T18:00:00Z|date=May 10, 2018|website=WIS Portal – GISC Tokyo|publisher=Japan Meteorological Agency|access-date=May 11, 2018}}</ref><ref>{{Cite web|url=http://www.metoc.navy.mil/jtwc/products/wp9718web.txt|title=Tropical Cyclone Formation Alert|date=May 10, 2018|publisher=Joint Typhoon Warning Center|archive-url=https://web.archive.org/web/20180511021302/http://www.metoc.navy.mil/jtwc/products/wp9718web.txt|archive-date=May 11, 2018|access-date=May 11, 2018}}</ref> By May 12, deep convection was observed near its center as the JTWC began issuing advisories on the system, giving it the designation ''04W''.<ref>{{cite web|title=Tropical Depression 04W (Four) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201805120300.htm|archive-url=https://www.webcitation.org/6zM45x4Ol?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201805120300.htm|url-status=dead|date=May 12, 2018|archive-date=May 12, 2018|publisher=Joint Typhoon Warning Center}}</ref> Roughly twelve hours later, it was reported that 04W had intensified into a tropical storm by the JTWC after satellite imagery had depicted a well-defined center.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 04W (Four) Warning Nr 03|url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201805121500.htm|archive-url=https://www.webcitation.org/6zNqEVaqh?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201805121500.htm|url-status=dead|date=May 12, 2018|archive-date=May 13, 2018|publisher=Joint Typhoon Warning Center}}</ref> Tracking on a west-northwesterly course, the system began to weaken as it entered an area of unfavorable conditions.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 04W (Four) Warning Nr 05|url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201805130300.htm|archive-url=https://www.webcitation.org/6zNqDiTcO?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201805130300.htm|url-status=dead|date=May 13, 2018|archive-date=May 13, 2018|publisher=Joint Typhoon Warning Center}}</ref> 04W rapidly weakened as the JTWC issued their final advisory on the system early on May 14 as ] affected the system and exposed the elongated low-level circulation.<ref>{{cite web|title=Tropical Depression 04W (Four) Warning Nr 008|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201805132100.htm|archive-url=https://www.webcitation.org/6zPBOifdC?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201805132100.htm|url-status=dead|date=May 14, 2018|archive-date=May 14, 2018|publisher=Joint Typhoon Warning Center}}</ref> The JMA, however, tracked the system until early on May 15, when it dissipated.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201805150000.htm |title=Archived copy |access-date=2018-05-15 |archive-url=https://www.webcitation.org/6zQcRnmgI?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201805150000.htm |archive-date=2018-05-15 |url-status=dead }}</ref> A low-pressure area east of ] was upgraded to a tropical depression by the JMA late on May 10 shortly before the JTWC issued a ].<ref>{{Cite web|url=http://www.wis-jma.go.jp/cms/warning/2018/05/10/marine-weather-warning-for-gmdss-metarea-xi-2018-05-10t180000z/|title=Marine Weather Warning for GMDSS Metarea XI 2018-05-10T18:00:00Z|date=May 10, 2018|website=WIS Portal – GISC Tokyo|publisher=Japan Meteorological Agency|access-date=May 11, 2018}}</ref><ref>{{Cite web|url=http://www.metoc.navy.mil/jtwc/products/wp9718web.txt|title=Tropical Cyclone Formation Alert|date=May 10, 2018|publisher=Joint Typhoon Warning Center|archive-url=https://web.archive.org/web/20180511021302/http://www.metoc.navy.mil/jtwc/products/wp9718web.txt|archive-date=May 11, 2018|access-date=May 11, 2018}}</ref> By May 12, deep convection was observed near its center as the JTWC began issuing advisories on the system, giving it the designation ''04W''.<ref>{{cite web|title=Tropical Depression 04W (Four) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201805120300.htm|archive-url=https://archive.today/20240524021757/https://www.webcitation.org/6zM45x4Ol?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201805120300.htm|url-status=dead|date=May 12, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> Roughly twelve hours later, it was reported that 04W had intensified into a tropical storm by the JTWC after satellite imagery had depicted a well-defined center.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 04W (Four) Warning Nr 03|url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201805121500.htm|archive-url=https://archive.today/20240524021918/https://www.webcitation.org/6zNqEVaqh?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201805121500.htm|url-status=dead|date=May 12, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> Tracking on a west-northwesterly course, the system began to weaken as it entered an area of unfavorable conditions.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 04W (Four) Warning Nr 05|url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201805130300.htm|archive-url=https://archive.today/20240524021837/https://www.webcitation.org/6zNqDiTcO?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201805130300.htm|url-status=dead|date=May 13, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> 04W rapidly weakened as the JTWC issued their final advisory on the system early on May 14 as ] affected the system and exposed the elongated low-level circulation.<ref>{{cite web|title=Tropical Depression 04W (Four) Warning Nr 008|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201805132100.htm|archive-url=https://archive.today/20240524021959/https://www.webcitation.org/6zPBOifdC?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201805132100.htm|url-status=dead|date=May 14, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> The JMA, however, tracked the system until early on May 15, when it dissipated.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201805150000.htm |title=Archived copy |access-date=2018-05-15 |archive-url=https://archive.today/20240524022039/https://www.webcitation.org/6zQcRnmgI?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201805150000.htm |archive-date=2024-05-24 |url-status=dead }}</ref>
{{clear}} {{clear}}


Line 257: Line 254:
}} }}
{{main|Tropical Storm Ewiniar (2018)}} {{main|Tropical Storm Ewiniar (2018)}}
A low-pressure area developed into a tropical depression over the ] on June 2.<ref>{{Cite web|url=http://www.wis-jma.go.jp/cms/warning/2018/06/01/marine-weather-warning-for-gmdss-metarea-xi-2018-06-01t180000z/|title=Marine Weather Warning for GMDSS Metarea XI 2018-06-01T18:00:00Z|date=June 1, 2018|website=WIS Portal – GISC Tokyo|publisher=Japan Meteorological Agency|access-date=June 4, 2018}}</ref><ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wt/wtpq20.rjtd..txt|title=RSMC Tropical Cyclone Advisory|date=June 2, 2018|publisher=Japan Meteorological Agency|archive-url=https://www.webcitation.org/6zry592Lg?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201806020000.htm|archive-date=2018-06-02|access-date=June 4, 2018|url-status=live}}</ref> Later that day, the JTWC followed suit and assigned the designation ''05W'' to the system.<ref>{{cite web|title=Tropical Depression 05W (Five) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806020900.htm|archive-url=https://www.webcitation.org/6ztoVMK3K?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806020900.htm|url-status=dead|date=June 2, 2018|archive-date=June 3, 2018|publisher=Joint Typhoon Warning Center}}</ref> 05W meandered in a westward direction until it curved northward, and after three days, the JTWC upgraded the system to a tropical storm.<ref>{{cite web|title=Tropical Storm 05W (Five) Warning Nr 015|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806052100.htm|archive-url=https://www.webcitation.org/6zyUaYolK?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806052100.htm|url-status=dead|date=June 5, 2018|archive-date=June 6, 2018|publisher=Joint Typhoon Warning Center}}</ref> The JMA did the same three hours later early on June 6, naming it ''Ewiniar''.<ref>{{cite web|title=TS 1804 EWINIAR (1806) UPGRADED FROM TD|url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201806060000.htm|archive-url=https://www.webcitation.org/6zyTyOUOi?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201806060000.htm|url-status=dead|archive-date=June 6, 2018|date=June 6, 2018|agency=Japan Meteorological Agency}}</ref> Shortly thereafter, Ewiniar made landfall over ]. Ewiniar maintained its intensity while over land until the JTWC issued its final advisory late on June 7.<ref>{{cite web|title=Tropical Storm 05W (Five) Warning Nr 023|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806072100.htm|archive-url=https://www.webcitation.org/702zQiImW?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806072100.htm|url-status=dead|date=June 7, 2018|archive-date=June 9, 2018|publisher=Joint Typhoon Warning Center}}</ref> The JMA, however, tracked the system until early on June 9, when Ewiniar had weakened into a tropical depression and degenerated into a remnant low.<ref>{{cite web|title=TD DOWNGRADED FROM TS 1804 EWINIAR (1806)|url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201806090000.htm|archive-url=https://www.webcitation.org/702z6MDY3?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201806090000.htm|url-status=dead|archive-date=June 9, 2018|date=June 9, 2018|agency=Japan Meteorological Agency}}</ref> However, Ewiniar's remnants moved out to sea and continued to persist, before dissipating on June 13. A low-pressure area developed into a tropical depression over the ] on June 2.<ref>{{Cite web|url=http://www.wis-jma.go.jp/cms/warning/2018/06/01/marine-weather-warning-for-gmdss-metarea-xi-2018-06-01t180000z/|title=Marine Weather Warning for GMDSS Metarea XI 2018-06-01T18:00:00Z|date=June 1, 2018|website=WIS Portal – GISC Tokyo|publisher=Japan Meteorological Agency|access-date=June 4, 2018}}</ref><ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wt/wtpq20.rjtd..txt|title=RSMC Tropical Cyclone Advisory|date=June 2, 2018|publisher=Japan Meteorological Agency|archive-url=https://archive.today/20240522091528/https://www.webcitation.org/6zry592Lg?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201806020000.htm|archive-date=2024-05-22|access-date=June 4, 2018|url-status=live}}</ref> Later that day, the JTWC followed suit and assigned the designation ''05W'' to the system.<ref>{{cite web|title=Tropical Depression 05W (Five) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806020900.htm|archive-url=https://archive.today/20240524022118/https://www.webcitation.org/6ztoVMK3K?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806020900.htm|url-status=dead|date=June 2, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> 05W meandered in a westward direction until it curved northward, and after three days, the JTWC upgraded the system to a tropical storm.<ref>{{cite web|title=Tropical Storm 05W (Five) Warning Nr 015|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806052100.htm|archive-url=https://archive.today/20240524022240/https://www.webcitation.org/6zyUaYolK?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806052100.htm|url-status=dead|date=June 5, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> The JMA did the same three hours later early on June 6, naming it ''Ewiniar''.<ref>{{cite web|title=TS 1804 EWINIAR (1806) UPGRADED FROM TD|url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201806060000.htm|archive-url=https://archive.today/20240524022200/https://www.webcitation.org/6zyTyOUOi?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201806060000.htm|url-status=dead|archive-date=May 24, 2024|date=June 6, 2018|agency=Japan Meteorological Agency}}</ref> Shortly thereafter, Ewiniar made landfall over ]. Ewiniar maintained its intensity while over land until the JTWC issued its final advisory late on June 7.<ref>{{cite web|title=Tropical Storm 05W (Five) Warning Nr 023|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806072100.htm|archive-url=https://archive.today/20240522224727/https://www.webcitation.org/702zQiImW?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806072100.htm|url-status=dead|date=June 7, 2018|archive-date=May 22, 2024|publisher=Joint Typhoon Warning Center}}</ref> The JMA, however, tracked the system until early on June 9, when Ewiniar had weakened into a tropical depression and degenerated into a remnant low.<ref>{{cite web|title=TD DOWNGRADED FROM TS 1804 EWINIAR (1806)|url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201806090000.htm|archive-url=https://archive.today/20240524022320/https://www.webcitation.org/702z6MDY3?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201806090000.htm|url-status=dead|archive-date=May 24, 2024|date=June 9, 2018|agency=Japan Meteorological Agency}}</ref> However, Ewiniar's remnants moved out to sea and continued to persist, before dissipating on June 13.


A total of 13 people were killed, while total damages in mainland China were counted to be ]5.19 billion (US$812 million).<ref name="China Member Report">{{cite conference|pages=1–2|conference=ESCAP/WMO Typhoon Committee|title=Member Report: China|author=CMA|publisher=ESCAP/WMO Typhoon Committee|url=http://www.typhooncommittee.org/13IWS/docs/Members%20REport/CHina/Member_report_China_2018.pdf|archive-url=https://web.archive.org/web/20181204010101/http://www.typhooncommittee.org/13IWS/docs/Members%20REport/CHina/Member_report_China_2018.pdf|date=December 4, 2018|access-date=December 4, 2018|conference-url=http://www.typhooncommittee.org/13IWS/index13IWS.html|archive-date=December 4, 2018|url-status=dead}}</ref> A total of 13 people were killed, while total damages in mainland China were counted to be ]5.19 billion (US$812 million).<ref name="China Member Report">{{cite conference|pages=1–2|conference=ESCAP/WMO Typhoon Committee|title=Member Report: China|author=CMA|publisher=ESCAP/WMO Typhoon Committee|url=http://www.typhooncommittee.org/13IWS/docs/Members%20REport/CHina/Member_report_China_2018.pdf|archive-url=https://web.archive.org/web/20181204010101/http://www.typhooncommittee.org/13IWS/docs/Members%20REport/CHina/Member_report_China_2018.pdf|date=December 4, 2018|access-date=December 4, 2018|conference-url=http://www.typhooncommittee.org/13IWS/index13IWS.html|archive-date=December 4, 2018|url-status=dead}}</ref>
Line 274: Line 271:
}} }}
{{main|Tropical Storm Maliksi (2018)}} {{main|Tropical Storm Maliksi (2018)}}
A low-pressure area northwest of ] developed into a tropical depression late on June 3.<ref name="MaliksiBT">{{cite web|title=RSMC Tropical Cyclone Best Track 1805 MALIKSI (1805)|url=http://gwydir.demon.co.uk/advisories/AXPQ20-RJTD_201807180100.htm|archive-url=https://www.webcitation.org/70zie0yqF?url=http://gwydir.demon.co.uk/advisories/AXPQ20-RJTD_201807180100.htm|url-status=dead|date=July 18, 2018|archive-date=July 18, 2018|publisher=Japan Meteorological Agency}}</ref> On the next day, the system received the local name ''Domeng'' from the ] as the JTWC issued a TCFA on the system.<ref name="90W_TCFA">{{Cite web|url=http://www.metoc.navy.mil/jtwc/products/wp9018web.txt|title=Tropical Cyclone Formation Alert|date=June 5, 2018|publisher=Joint Typhoon Warning Center|archive-url=https://web.archive.org/web/20180606014622/http://www.metoc.navy.mil/jtwc/products/wp9018web.txt|archive-date=June 6, 2018|access-date=June 6, 2018}}</ref><ref>{{cite web|title=Tropical depression Domeng enters PAR|url=https://www.philstar.com/headlines/2018/06/06/1822086/tropical-depression-domeng-enters-par|date=June 6, 2018|publisher=Philstar}}</ref> After the system had consolidated further, the JMA upgraded the system to a tropical storm, naming it ''Maliksi'' ('''1805''').<ref name="MaliksiBT"/> The JTWC, however, did not track the system until 03:00 UTC on June 8 when it gave Maliksi the designation of ''06W''.<ref>{{cite web|title=Tropical Storm 06W (Maliksi) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201806080300.htm|archive-url=https://www.webcitation.org/7031YYt8y?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201806080300.htm|url-status=dead|date=June 8, 2018|archive-date=June 9, 2018|publisher=Joint Typhoon Warning Center}}</ref> Moving northward, Maliksi continued to intensify until it reached its peak strength early on June 10 with winds of {{convert|110|km/h|mph|abbr=on}}, just shy of typhoon intensity, and a minimum pressure of 970 hPa.<ref name="MaliksiBT"/><ref>{{cite web|title=Tropical Storm 06W (Maliksi) Warning Nr 010|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201806100300.htm|archive-url=https://www.webcitation.org/704CM4SL0?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201806100300.htm|url-status=dead|date=June 10, 2018|archive-date=June 10, 2018|publisher=Joint Typhoon Warning Center}}</ref> Operationally, the JMA briefly classified Maliksi as a typhoon, but it was downgraded to a severe tropical storm in post-analysis.<ref>{{cite web|title=TY 1805 MALIKSI (1805) UPGRADED FROM STS|url=http://gwydir.demon.co.uk/advisories/WTPQ21-RJTD_201806100000.htm|archive-url=https://www.webcitation.org/704C7x6fo?url=http://gwydir.demon.co.uk/advisories/WTPQ21-RJTD_201806100000.htm|url-status=dead|archive-date=June 10, 2018|date=June 10, 2018|publisher=Japan Meteorological Agency}}</ref> Maliksi began to weaken as it began extratropical transition, and on June 11 as it encountered more unfavorable conditions, both agencies stopped issuing warnings on Maliksi as the system's center became exposed and as it transitioned into an extratropical cyclone.<ref name="MaliksiBT"/><ref>{{cite web|title=Tropical Storm 06W (Maliksi) Warning Nr 015|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201806111500.htm|archive-url=https://www.webcitation.org/707nNaSby?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201806111500.htm|url-status=dead|date=June 11, 2018|archive-date=June 12, 2018|publisher=Joint Typhoon Warning Center}}</ref> The JMA tracked the remnants of Maliksi until 00:00 UTC on June 13.<ref name="MaliksiBT"/> A low-pressure area northwest of ] developed into a tropical depression late on June 3.<ref name="MaliksiBT">{{cite web|title=RSMC Tropical Cyclone Best Track 1805 MALIKSI (1805)|url=http://gwydir.demon.co.uk/advisories/AXPQ20-RJTD_201807180100.htm|archive-url=https://archive.today/20240522101720/https://www.webcitation.org/70zie0yqF?url=http://gwydir.demon.co.uk/advisories/AXPQ20-RJTD_201807180100.htm|url-status=dead|date=July 18, 2018|archive-date=May 22, 2024|publisher=Japan Meteorological Agency}}</ref> On the next day, the system received the local name ''Domeng'' from the ] as the JTWC issued a TCFA on the system.<ref name="90W_TCFA">{{Cite web|url=http://www.metoc.navy.mil/jtwc/products/wp9018web.txt|title=Tropical Cyclone Formation Alert|date=June 5, 2018|publisher=Joint Typhoon Warning Center|archive-url=https://web.archive.org/web/20180606014622/http://www.metoc.navy.mil/jtwc/products/wp9018web.txt|archive-date=June 6, 2018|access-date=June 6, 2018}}</ref><ref>{{cite web|title=Tropical depression Domeng enters PAR|url=https://www.philstar.com/headlines/2018/06/06/1822086/tropical-depression-domeng-enters-par|date=June 6, 2018|publisher=Philstar}}</ref> After the system had consolidated further, the JMA upgraded the system to a tropical storm, naming it ''Maliksi'' ('''1805''').<ref name="MaliksiBT"/> The JTWC, however, did not track the system until 03:00 UTC on June 8 when it gave Maliksi the designation of ''06W''.<ref>{{cite web|title=Tropical Storm 06W (Maliksi) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201806080300.htm|archive-url=https://archive.today/20240524022359/https://www.webcitation.org/7031YYt8y?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201806080300.htm|url-status=dead|date=June 8, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> Moving northward, Maliksi continued to intensify until it reached its peak strength early on June 10 with winds of {{convert|110|km/h|mph|abbr=on}}, just shy of typhoon intensity, and a minimum pressure of 970 hPa.<ref name="MaliksiBT"/><ref>{{cite web|title=Tropical Storm 06W (Maliksi) Warning Nr 010|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201806100300.htm|archive-url=https://archive.today/20240524022520/https://www.webcitation.org/704CM4SL0?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201806100300.htm|url-status=dead|date=June 10, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> Operationally, the JMA briefly classified Maliksi as a typhoon, but it was downgraded to a severe tropical storm in post-analysis.<ref>{{cite web|title=TY 1805 MALIKSI (1805) UPGRADED FROM STS|url=http://gwydir.demon.co.uk/advisories/WTPQ21-RJTD_201806100000.htm|archive-url=https://archive.today/20240524022439/https://www.webcitation.org/704C7x6fo?url=http://gwydir.demon.co.uk/advisories/WTPQ21-RJTD_201806100000.htm|url-status=dead|archive-date=May 24, 2024|date=June 10, 2018|publisher=Japan Meteorological Agency}}</ref> Maliksi began to weaken as it began extratropical transition, and on June 11 as it encountered more unfavorable conditions, both agencies stopped issuing warnings on Maliksi as the system's center became exposed and as it transitioned into an extratropical cyclone.<ref name="MaliksiBT"/><ref>{{cite web|title=Tropical Storm 06W (Maliksi) Warning Nr 015|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201806111500.htm|archive-url=https://archive.today/20240524022600/https://www.webcitation.org/707nNaSby?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201806111500.htm|url-status=dead|date=June 11, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> The JMA tracked the remnants of Maliksi until 00:00 UTC on June 13.<ref name="MaliksiBT"/>


Despite not making landfall on the ], Maliksi prompted the PAGASA to declare the official start of the rainy season on June 8, 2018. Two people were killed by heavy monsoonal rains enhanced by Maliksi in the Philippines.<ref name="Maliksi1">{{cite web|title=2 dead in aftermath of Typhoon Domeng|url=http://cnnphilippines.com/news/2018/06/10/domeng-aftermath.html|date=June 11, 2018|publisher=CNN Philippines|access-date=June 10, 2018|archive-date=June 12, 2018|archive-url=https://web.archive.org/web/20180612213217/http://cnnphilippines.com/news/2018/06/10/domeng-aftermath.html|url-status=live}}</ref> Despite not making landfall on the ], Maliksi prompted the PAGASA to declare the official start of the rainy season on June 8, 2018. Two people were killed by heavy monsoonal rains enhanced by Maliksi in the Philippines.<ref name="Maliksi1">{{cite web|title=2 dead in aftermath of Typhoon Domeng|url=http://cnnphilippines.com/news/2018/06/10/domeng-aftermath.html|date=June 11, 2018|publisher=CNN Philippines|access-date=June 10, 2018|archive-date=June 12, 2018|archive-url=https://web.archive.org/web/20180612213217/http://cnnphilippines.com/news/2018/06/10/domeng-aftermath.html|url-status=dead}}</ref>
{{Clear}} {{Clear}}


Line 290: Line 287:
| Type = subtropical | Type = subtropical
}} }}
A disturbance formed southwest of ] on June 12 just within the ], and the JTWC subsequently indicated the formation of a subtropical depression.<ref name="07WJTWCtrack">{{Cite web|url=http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp072018.dat|title=Tropical Storm 07W running best track|publisher=Joint Typhoon Warning Center|access-date=June 14, 2018|archive-date=June 14, 2018|archive-url=https://web.archive.org/web/20180614094510/http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp072018.dat|url-status=live}}</ref> At 21:00 UTC on June 13, the JTWC issued its first advisory on the system and designated it as ''07W'', classifying it as a tropical depression.<ref>{{cite web|title=Tropical Depression 07W (Seven) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806132100.htm|archive-url=https://www.webcitation.org/70ALHxWfQ?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806132100.htm|url-status=dead|date=June 13, 2018 |archive-date=June 14, 2018|publisher=Joint Typhoon Warning Center}}</ref> Despite being affected by moderate to severe wind shear, the system was located over relatively warm sea-surface temperatures as it produced patches of convection, and this prompted the JTWC to upgrade 07W to a tropical storm.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 07W (Seven) Warning Nr 02|url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201806140300.htm|archive-url=https://www.webcitation.org/70Br5Or8G?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201806140300.htm|url-status=dead|date=June 14, 2018 |archive-date=June 15, 2018|publisher=Joint Typhoon Warning Center}}</ref> The JTWC later issued their fourth but final advisory on 07W at 15:00 UTC on June 14 when the system was rapidly undergoing a phase of extratropical transition and as the system was rapidly losing its structure.<ref>{{cite web|title=Tropical Storm 07W (Seven) Warning Nr 004|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806141500.htm|archive-url=https://www.webcitation.org/70Br20EEl?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806141500.htm|url-status=dead|date=June 14, 2018 |archive-date=June 15, 2018|publisher=Joint Typhoon Warning Center}}</ref> 07W fully became an extratropical cyclone just to the south of mainland ] at 06:00 UTC on June 15, although its remnant was still tracked until June 25, when the system was last located near the coast of ].<ref name="07WJTWCtrack"/> A disturbance formed southwest of ] on June 12 just within the ], and the JTWC subsequently indicated the formation of a subtropical depression.<ref name="07WJTWCtrack">{{Cite web|url=http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp072018.dat|title=Tropical Storm 07W running best track|publisher=Joint Typhoon Warning Center|access-date=June 14, 2018|archive-date=June 14, 2018|archive-url=https://web.archive.org/web/20180614094510/http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp072018.dat|url-status=live}}</ref> At 21:00 UTC on June 13, the JTWC issued its first advisory on the system and designated it as ''07W'', classifying it as a tropical depression.<ref>{{cite web|title=Tropical Depression 07W (Seven) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806132100.htm|archive-url=https://archive.today/20240524022642/https://www.webcitation.org/70ALHxWfQ?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806132100.htm|url-status=dead|date=June 13, 2018 |archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> Despite being affected by moderate to severe wind shear, the system was located over relatively warm sea-surface temperatures as it produced patches of convection, and this prompted the JTWC to upgrade 07W to a tropical storm.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 07W (Seven) Warning Nr 02|url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201806140300.htm|archive-url=https://archive.today/20240524022801/https://www.webcitation.org/70Br5Or8G?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201806140300.htm|url-status=dead|date=June 14, 2018 |archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> The JTWC later issued their fourth but final advisory on 07W at 15:00 UTC on June 14 when the system was rapidly undergoing a phase of extratropical transition and as the system was rapidly losing its structure.<ref>{{cite web|title=Tropical Storm 07W (Seven) Warning Nr 004|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806141500.htm|archive-url=https://archive.today/20240524022722/https://www.webcitation.org/70Br20EEl?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201806141500.htm|url-status=dead|date=June 14, 2018 |archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> 07W fully became an extratropical cyclone just to the south of mainland ] at 06:00 UTC on June 15, although its remnant was still tracked until June 25, when the system was last located near the coast of ].<ref name="07WJTWCtrack"/>
{{clear}} {{clear}}


Line 322: Line 319:
{{main|Typhoon Prapiroon (2018)}} {{main|Typhoon Prapiroon (2018)}}
{{see also|2018 Japan floods}} {{see also|2018 Japan floods}}
A low-pressure area west of ] developed into a tropical depression on June 28. On the next day, the PAGASA began issuing advisories, assigning it the local name ''Florita''. 6 hours later, Florita became a tropical storm, with the JMA assigning it the name ''Prapiroon'' (''1807''). By July 2, Prapiroon intensified into a Category 1 typhoon as it neared Japan and Korea. By July 3, Prapiroon had attained peak intensity. On the same day, Prapiroon made landfall on Japan. After making landfall, Prapiroon briefly weakened to a tropical storm. Prapiroon became a low-pressure area on the next day, though the ] still tracked its remnants until July 10, when it finally dissipated.<ref>{{Cite web|url=http://www.wis-jma.go.jp/cms/warning/2018/06/28/marine-weather-warning-for-gmdss-metarea-xi-2018-06-28t000000z/|title=Marine Weather Warning for GMDSS Metarea XI 2018-06-28T00:00:00Z|date=June 28, 2018|website=WIS Portal – GISC Tokyo|publisher=Japan Meteorological Agency|access-date=June 28, 2018}}</ref><ref>{{Cite web|url=http://www.wis-jma.go.jp/cms/warning/2018/07/04/marine-weather-warning-for-gmdss-metarea-xi-2018-07-04t000000z/|title=Marine Weather Warning for GMDSS Metarea XI 2018-07-04T00:00:00Z|date=July 4, 2018|website=WIS Portal – GISC Tokyo|publisher=Japan Meteorological Agency|access-date=July 4, 2018}}</ref> A low-pressure area west of ] developed into ''Tropical Depression 09W'' on June 28. On the next day, the PAGASA began issuing advisories, assigning it the local name ''Florita''. 6 hours later, Florita became a tropical storm, with the JMA assigning it the name ''Prapiroon'' (''1807''). By July 2, Prapiroon intensified into a Category 1 typhoon as it neared Japan and Korea. By July 3, Prapiroon had attained peak intensity. On the same day, Prapiroon made landfall on Japan. After making landfall, Prapiroon briefly weakened to a tropical storm. Prapiroon became a low-pressure area on the next day, though the ] still tracked its remnants until July 10, when it finally dissipated.<ref>{{Cite web|url=http://www.wis-jma.go.jp/cms/warning/2018/06/28/marine-weather-warning-for-gmdss-metarea-xi-2018-06-28t000000z/|title=Marine Weather Warning for GMDSS Metarea XI 2018-06-28T00:00:00Z|date=June 28, 2018|website=WIS Portal – GISC Tokyo|publisher=Japan Meteorological Agency|access-date=June 28, 2018}}</ref><ref>{{Cite web|url=http://www.wis-jma.go.jp/cms/warning/2018/07/04/marine-weather-warning-for-gmdss-metarea-xi-2018-07-04t000000z/|title=Marine Weather Warning for GMDSS Metarea XI 2018-07-04T00:00:00Z|date=July 4, 2018|website=WIS Portal – GISC Tokyo|publisher=Japan Meteorological Agency|access-date=July 4, 2018}}</ref>


Five people were injured by the winds from the typhoon.<ref>{{Cite web|url=https://ryukyushimpo.jp/news/entry-751661.html|title=台風7号 被害報告、県の災害警戒本部会議|publisher=琉球新報|date=2018-07-05|accessdate=2018-07-09}}</ref> A woman was blown away by the strong winds of the typhoon and died at a hospital she was sent to later.<ref>{{Cite web|url=https://mainichi.jp/articles/20180705/k00/00m/040/020000c|title=台風7号 農作業中の89歳女性転落死 強風にあおられ?|publisher=毎日新聞|date=2018-07-05|accessdate=2018-07-05}}</ref> The typhoon also caused damages on Old Gorin Church, which as designated as heritage site four days prior, and caused damages to the stained glass in Kuroshima Catholic Church.<ref>{{Cite news |url=https://news.infoseek.co.jp/article/mainichi_20180706k0000m040113000c/ |title=台風7号:長崎の「潜伏キリシタン」世界文化遺産で被害 |newspaper=] |publisher=] ] ] |date=2018-07-05 |accessdate=2018-07-07}}</ref> Five people were injured by the winds from the typhoon.<ref>{{Cite web|url=https://ryukyushimpo.jp/news/entry-751661.html|title=台風7号 被害報告、県の災害警戒本部会議|publisher=琉球新報|date=2018-07-05|accessdate=2018-07-09}}</ref> A woman was blown away by the strong winds of the typhoon and died at a hospital she was sent to later.<ref>{{Cite web|url=https://mainichi.jp/articles/20180705/k00/00m/040/020000c|title=台風7号 農作業中の89歳女性転落死 強風にあおられ?|publisher=毎日新聞|date=2018-07-05|accessdate=2018-07-05}}</ref> The typhoon also caused damages on Old Gorin Church, which as designated as heritage site four days prior, and caused damages to the stained glass in Kuroshima Catholic Church.<ref>{{Cite news |url=https://news.infoseek.co.jp/article/mainichi_20180706k0000m040113000c/ |title=台風7号:長崎の「潜伏キリシタン」世界文化遺産で被害 |newspaper=] |publisher=] ] ] |date=2018-07-05 |accessdate=2018-07-07 |archive-date=2018-07-07 |archive-url=https://web.archive.org/web/20180707011524/https://news.infoseek.co.jp/article/mainichi_20180706k0000m040113000c/ |url-status=dead }}</ref> One person from ] was killed by the storm.<ref name="Prapiroon1">{{cite web|title=1 dead, 1 missing as Typhoon Prapiroon approaches Korea|url=http://www.koreaherald.com/view.php?ud=20180702000720|date=July 2, 2018|publisher=Koreaherald|access-date=July 5, 2018|archive-date=July 18, 2018|archive-url=https://web.archive.org/web/20180718001436/http://www.koreaherald.com/view.php?ud=20180702000720|url-status=live}}</ref> Agricultural damage in ] were about ]49.39 million (US$446,000).<ref>{{cite report|url=http://www.ogb.go.jp/-/media/Files/OGB/Soumu/bousai/taifuu/H30/7higai7.pdf|title=平成30年台風第7号に係る被害状況等について(第7報)最終報|language=ja|publisher=沖縄総合事務局|date=July 4, 2018|access-date=July 5, 2018}}</ref>

{{As of|July 2018}}, 1 person from ] was killed by the storm.<ref name="Prapiroon1">{{cite web|title=1 dead, 1 missing as Typhoon Prapiroon approaches Korea|url=http://www.koreaherald.com/view.php?ud=20180702000720|date=July 2, 2018|publisher=Koreaherald|access-date=July 5, 2018|archive-date=July 18, 2018|archive-url=https://web.archive.org/web/20180718001436/http://www.koreaherald.com/view.php?ud=20180702000720|url-status=live}}</ref> Agricultural damage in ] were about ]49.39 million (US$446,000).<ref>{{cite report|url=http://www.ogb.go.jp/-/media/Files/OGB/Soumu/bousai/taifuu/H30/7higai7.pdf|title=平成30年台風第7号に係る被害状況等について(第7報)最終報|language=ja|publisher=沖縄総合事務局|date=July 4, 2018|access-date=July 5, 2018}}</ref>
{{Clear}} {{Clear}}


Line 335: Line 330:
| Dissipated = July 12 | Dissipated = July 12
| Image = Maria 2018-07-08 0630Z.png | Image = Maria 2018-07-08 0630Z.png
| Track = Maria 2018 track.png | Track = Maria 2018 path.png
| 10-min winds = 105 | 10-min winds = 105
| 1-min winds = 145 | 1-min winds = 145
Line 361: Line 356:
{{main|Tropical Storm Son-Tinh (2018)}} {{main|Tropical Storm Son-Tinh (2018)}}
{{see also|2018 Laos dam collapse|2018 Northern Vietnam floods}} {{see also|2018 Laos dam collapse|2018 Northern Vietnam floods}}
An area of low-pressure strengthened into a tropical depression on July 15 to the northwest of ], ].<ref name="11W1">{{cite web|title=Tropical Depression 11W (Eleven) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807151500.htm|archive-url=https://www.webcitation.org/70w2Bc366?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807151500.htm|url-status=dead|date=July 15, 2018|archive-date=July 15, 2018|publisher=Joint Typhoon Warning Center}}</ref> The JTWC designated it as ''11W'' while the PAGASA gave it the local name ''Henry''.<ref name="11W1"/> As the system moved fast in a westward direction towards the Babuyan Islands, the system gradually intensified and was declared a tropical storm on July 17, with the JMA naming it as ''Son-Tinh'' as its convective structure improved.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 11W (Son-Tinh) Warning Nr 07|url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807170300.htm|archive-url=https://www.webcitation.org/70zFNXrpr?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807170300.htm|url-status=dead|date=July 17, 2018|archive-date=July 17, 2018|publisher=Joint Typhoon Warning Center}}</ref> Thereafter, Son-Tinh slightly weakened as it neared ] Island while experiencing moderate shear.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 11W (Son-Tinh) Warning Nr 08|url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807170900.htm|archive-url=https://www.webcitation.org/70zFNA2BH?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807170900.htm|url-status=dead|date=July 17, 2018|archive-date=July 17, 2018|publisher=Joint Typhoon Warning Center}}</ref> During the next day, however, Son-Tinh slightly intensified over the ] due to warm sea-surface temperatures before it made landfall on northern ].<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 11W (Son-Tinh) Warning Nr 12|url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807180900.htm|archive-url=https://www.webcitation.org/710hJRT94?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807180900.htm|url-status=dead|date=July 18, 2018|archive-date=July 18, 2018|publisher=Joint Typhoon Warning Center}}</ref> Both agencies issued their final warnings on Son-Tinh on July 19 as the system had weakened back into an area of low-pressure embedded into the ].<ref>{{cite web|title=Tropical Storm 11W (Son-Tinh) Warning Nr 014|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807182100.htm|archive-url=https://www.webcitation.org/711otPu9f?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807182100.htm|url-status=dead|date=July 19, 2018|archive-date=July 19, 2018|publisher=Joint Typhoon Warning Center}}</ref> However, the JTWC continued to track the system's ] for another two days before it dissipated.<ref name="11Wtrack">{{Cite web |url=http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp112018.dat |title=Archived copy |access-date=2018-07-21 |archive-date=2018-07-22 |archive-url=https://web.archive.org/web/20180722172212/http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp112018.dat |url-status=live }}</ref> An area of low-pressure strengthened into a tropical depression on July 15 to the northwest of ], ].<ref name="11W1">{{cite web|title=Tropical Depression 11W (Eleven) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807151500.htm|archive-url=https://archive.today/20240523013146/https://www.webcitation.org/70w2Bc366?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807151500.htm|url-status=dead|date=July 15, 2018|archive-date=May 23, 2024|publisher=Joint Typhoon Warning Center}}</ref> The JTWC designated it as ''11W'' while the PAGASA gave it the local name ''Henry''.<ref name="11W1"/> As the system moved fast in a westward direction towards the Babuyan Islands, the system gradually intensified and was declared a tropical storm on July 17, with the JMA naming it as ''Son-Tinh'' as its convective structure improved.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 11W (Son-Tinh) Warning Nr 07|url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807170300.htm|archive-url=https://archive.today/20240523013428/https://www.webcitation.org/70zFNXrpr?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807170300.htm|url-status=dead|date=July 17, 2018|archive-date=May 23, 2024|publisher=Joint Typhoon Warning Center}}</ref> Thereafter, Son-Tinh slightly weakened as it neared ] Island while experiencing moderate shear.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 11W (Son-Tinh) Warning Nr 08|url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807170900.htm|archive-url=https://archive.today/20240523013348/https://www.webcitation.org/70zFNA2BH?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807170900.htm|url-status=dead|date=July 17, 2018|archive-date=May 23, 2024|publisher=Joint Typhoon Warning Center}}</ref> During the next day, however, Son-Tinh slightly intensified over the ] due to warm sea-surface temperatures before it made landfall on northern ].<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 11W (Son-Tinh) Warning Nr 12|url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807180900.htm|archive-url=https://archive.today/20240523013549/https://www.webcitation.org/710hJRT94?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807180900.htm|url-status=dead|date=July 18, 2018|archive-date=May 23, 2024|publisher=Joint Typhoon Warning Center}}</ref> Both agencies issued their final warnings on Son-Tinh on July 19 as the system had weakened back into an area of low-pressure embedded into the ].<ref>{{cite web|title=Tropical Storm 11W (Son-Tinh) Warning Nr 014|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807182100.htm|archive-url=https://archive.today/20240523013749/https://www.webcitation.org/711otPu9f?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807182100.htm|url-status=dead|date=July 19, 2018|archive-date=May 23, 2024|publisher=Joint Typhoon Warning Center}}</ref> However, the JTWC continued to track the system's ] for another two days before it dissipated.<ref name="11Wtrack">{{Cite web |url=http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp112018.dat |title=Archived copy |access-date=2018-07-21 |archive-date=2018-07-22 |archive-url=https://web.archive.org/web/20180722172212/http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp112018.dat |url-status=live }}</ref>


In Vietnam, the ] and ] provinces suffered the most damage, especially with the wake of the storm continuing to generate significant rainfall.<ref name=":0">{{Cite news|url=http://www.newindianexpress.com/world/2018/jul/21/at-least-10-dead-in-vietnam-floods-triggered-by-typhoon-son-tinh-1846607.html|title=At least 10 dead in Vietnam floods triggered by Typhoon Son Tinh|date=July 21, 2018|work=The New Indian Express|access-date=July 22, 2018|agency=PTI}}</ref> It caused major flooding in ] and the capital city of ].{{cn|date=July 2023}}<!--<ref name="Reuters" /> --> 35 people were killed, more than 5,000 houses, {{Convert|82,000|hectare|acre}} of crops, and 17,000 farm animals were either swept away, submerged, or otherwise destroyed.{{cn|date=July 2023}}<!--<ref name="Reuters" /> --> The storm has cut off access to several areas in the country and flood water covers several streets in the capital city.<ref name=":0" /> Economic losses were estimated to be ]6.615 trillion (US$287 million).<ref name="tuyenq">{{cite web|title=Tóm tắt các cơn bão trong năm 2018|url=http://www.tuyenquang.gov.vn/n39915_tom-tat-cac-con-bao-trong-nam-2018?AspxAutoDetectCookieSupport=1|language=vi|publisher=Government of Tuyen Quang province|date=January 5, 2019|accessdate=January 20, 2019}}{{Dead link|date=July 2023 |bot=InternetArchiveBot |fix-attempted=yes }}</ref> In Vietnam, the ] and ] provinces suffered the most damage, especially with the wake of the storm continuing to generate significant rainfall.<ref name=":0">{{Cite news|url=https://www.newindianexpress.com/world/2018/jul/21/at-least-10-dead-in-vietnam-floods-triggered-by-typhoon-son-tinh-1846607.html|title=At least 10 dead in Vietnam floods triggered by Typhoon Son Tinh|date=July 21, 2018|work=The New Indian Express|access-date=July 22, 2018|agency=PTI}}</ref> It caused major flooding in ] and the capital city of ].{{cn|date=July 2023}}<!--<ref name="Reuters" /> --> 35 people were killed, more than 5,000 houses, {{Convert|82,000|hectare|acre}} of crops, and 17,000 farm animals were either swept away, submerged, or otherwise destroyed.{{cn|date=July 2023}}<!--<ref name="Reuters" /> --> The storm has cut off access to several areas in the country and flood water covers several streets in the capital city.<ref name=":0" /> Economic losses were estimated to be ]6.615 trillion (US$287 million).<ref name="tuyenq">{{cite web|title=Tóm tắt các cơn bão trong năm 2018|url=http://www.tuyenquang.gov.vn/n39915_tom-tat-cac-con-bao-trong-nam-2018?AspxAutoDetectCookieSupport=1|language=vi|publisher=Government of Tuyen Quang province|date=January 5, 2019|accessdate=January 20, 2019}}{{Dead link|date=July 2023 |bot=InternetArchiveBot |fix-attempted=yes }}</ref>


{{clear}} {{clear}}
Line 378: Line 373:
| Pressure = 985 | Pressure = 985
}} }}
{{main|Tropical Storm Ampil}} {{main|Tropical Storm Ampil (2018)}}
<!--Wait for Ampil BT for JMA sources--> <!--Wait for Ampil BT for JMA sources-->
On July 17, a weak tropical depression developed over the ]. The JTWC upgraded the system to a tropical depression on the same day, designating it as ''12W'' as it was located over a favorable environment.<ref>{{cite web|title=Tropical Depression 12W (Twelve) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201807172100.htm|archive-url=https://www.webcitation.org/710ipDmjp?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201807172100.htm|url-status=dead|date=July 17, 2018|archive-date=July 18, 2018|publisher=Joint Typhoon Warning Center}}</ref> On the next day, the PAGASA followed suit and it was given the local name ''Inday''. By 12:00 UTC on July 18, the JMA upgraded the system to a tropical storm, assigning it the name ''Ampil''.<ref>{{cite web|title=Tropical Storm 12W (Ampil) Warning Nr 005|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201807181500.htm|archive-url=https://www.webcitation.org/710io9dDG?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201807181500.htm|url-status=dead|date=July 18, 2018|archive-date=July 18, 2018|publisher=Joint Typhoon Warning Center}}</ref> As Ampil moved in a northward direction, the system's structure had broadened, being accompanied by sustained deep convection.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 12W (Ampil) Warning Nr 06|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201807190300.htm|archive-url=https://www.webcitation.org/711qxrpVG?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201807190300.htm|url-status=dead|date=July 19, 2018|archive-date=July 19, 2018|publisher=Joint Typhoon Warning Center}}</ref> Despite unfavorable ocean heat content, Ampil still remained over relatively warm sea surface temperatures with the inclusion of extensive deep convection,<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 12W (Ampil) Warning Nr 08|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201807191500.htm|archive-url=https://www.webcitation.org/713PFt7FK?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201807191500.htm|url-status=dead|date=July 19, 2018|archive-date=July 20, 2018|publisher=Joint Typhoon Warning Center}}</ref> therefore Ampil was classified as a severe tropical storm. With an improved convective system, the JTWC assessed that Ampil had reached maximum 1-minute sustained winds of {{convert|95|km/h|mph|abbr=on}}.<ref>{{cite web|title=Tropical Storm 12W (Ampil) Warning Nr 010|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201807200300.htm|archive-url=https://www.webcitation.org/713P2W6Yq?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201807200300.htm|url-status=dead|date=July 20, 2018|archive-date=July 20, 2018|publisher=Joint Typhoon Warning Center}}</ref> Ampil reached its peak intensity with a minimum pressure of 985 hPa and maintained that intensity for the next few days as the track of Ampil changed direction. On July 21, the system's center became exposed as the system slightly weakened.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 12W (Ampil) Warning Nr 15|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201807210900.htm|archive-url=https://www.webcitation.org/714sYZMjo?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201807210900.htm|url-status=dead|date=July 20, 2018|archive-date=July 21, 2018|publisher=Joint Typhoon Warning Center}}</ref> On the next day, the JMA downgraded Ampil back to a tropical storm as it made landfall on China with a lack of convection.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 12W (Ampil) Warning Nr 21|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201807222100.htm|archive-url=https://www.webcitation.org/717tkTHrg?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201807222100.htm|url-status=dead|date=July 22, 2018|archive-date=July 23, 2018|publisher=Joint Typhoon Warning Center}}</ref> Ampil weakened further to a tropical depression on July 23, and both agencies issued their final advisories on the system.<ref>{{cite web|title=Tropical Depression 12W (Ampil) Warning Nr 025|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201807232100.htm|archive-url=https://www.webcitation.org/7199EB2y3?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201807232100.htm|url-status=dead|date=July 23, 2018|archive-date=July 24, 2018|publisher=Joint Typhoon Warning Center}}</ref> The JMA continued tracking the system until it weakened into an area of low pressure at 18:00 UTC on July 24.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201807241800.htm |title=Archived copy |access-date=2018-07-25 |archive-url=https://www.webcitation.org/71B9r2g8v?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201807241800.htm |archive-date=2018-07-25 |url-status=dead }}</ref> On July 17, a weak tropical depression developed over the ]. The JTWC upgraded the system to a tropical depression on the same day, designating it as ''12W'' as it was located over a favorable environment.<ref>{{cite web|title=Tropical Depression 12W (Twelve) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201807172100.htm|archive-url=https://archive.today/20240524022920/https://www.webcitation.org/710ipDmjp?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201807172100.htm|url-status=dead|date=July 17, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> On the next day, the PAGASA followed suit and it was given the local name ''Inday''. By 12:00 UTC on July 18, the JMA upgraded the system to a tropical storm, assigning it the name ''Ampil''.<ref>{{cite web|title=Tropical Storm 12W (Ampil) Warning Nr 005|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201807181500.htm|archive-url=https://archive.today/20240524022841/https://www.webcitation.org/710io9dDG?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201807181500.htm|url-status=dead|date=July 18, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> As Ampil moved in a northward direction, the system's structure had broadened, being accompanied by sustained deep convection.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 12W (Ampil) Warning Nr 06|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201807190300.htm|archive-url=https://archive.today/20240524023001/https://www.webcitation.org/711qxrpVG?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201807190300.htm|url-status=dead|date=July 19, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> Despite unfavorable ocean heat content, Ampil still remained over relatively warm sea surface temperatures with the inclusion of extensive deep convection,<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 12W (Ampil) Warning Nr 08|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201807191500.htm|archive-url=https://archive.today/20240524023121/https://www.webcitation.org/713PFt7FK?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201807191500.htm|url-status=dead|date=July 19, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> therefore Ampil was classified as a severe tropical storm. With an improved convective system, the JTWC assessed that Ampil had reached maximum 1-minute sustained winds of {{convert|95|km/h|mph|abbr=on}}.<ref>{{cite web|title=Tropical Storm 12W (Ampil) Warning Nr 010|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201807200300.htm|archive-url=https://archive.today/20240524023043/https://www.webcitation.org/713P2W6Yq?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201807200300.htm|url-status=dead|date=July 20, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> Ampil reached its peak intensity with a minimum pressure of 985 hPa and maintained that intensity for the next few days as the track of Ampil changed direction. On July 21, the system's center became exposed as the system slightly weakened.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 12W (Ampil) Warning Nr 15|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201807210900.htm|archive-url=https://archive.today/20240524023202/https://www.webcitation.org/714sYZMjo?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201807210900.htm|url-status=dead|date=July 20, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> On the next day, the JMA downgraded Ampil back to a tropical storm as it made landfall on China with a lack of convection.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 12W (Ampil) Warning Nr 21|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201807222100.htm|archive-url=https://archive.today/20240524023404/https://www.webcitation.org/717tkTHrg?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201807222100.htm|url-status=dead|date=July 22, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> Ampil weakened further to a tropical depression on July 23, and both agencies issued their final advisories on the system.<ref>{{cite web|title=Tropical Depression 12W (Ampil) Warning Nr 025|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201807232100.htm|archive-url=https://archive.today/20240524023522/https://www.webcitation.org/7199EB2y3?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201807232100.htm|url-status=dead|date=July 23, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> The JMA continued tracking the system until it weakened into an area of low pressure at 18:00 UTC on July 24.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201807241800.htm |title=Archived copy |access-date=2018-07-25 |archive-url=https://archive.today/20240524023643/https://www.webcitation.org/71B9r2g8v?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201807241800.htm |archive-date=2024-05-24 |url-status=dead }}</ref>


Heavy rain in ]—accumulating to {{convert|237|mm|in|abbr=on}} in ]—caused significant flooding, inundating 31,600&nbsp;hectares of crops and affecting 260,000&nbsp;people. One person was killed in China and total economic losses reached CN¥1.63 billion (US$241 million).<ref name="China Member Report"/> Heavy rain in ]—accumulating to {{convert|237|mm|in|abbr=on}} in ]—caused significant flooding, inundating 31,600&nbsp;hectares of crops and affecting 260,000&nbsp;people. One person was killed in China and total economic losses reached CN¥1.63 billion (US$241 million).<ref name="China Member Report"/>
Line 386: Line 381:


===Tropical Depression 13W (Josie)=== ===Tropical Depression 13W (Josie)===
{{main|Tropical Depression Josie}}
{{Infobox hurricane small {{Infobox hurricane small
| Basin = WPac | Basin = WPac
Line 396: Line 390:
| 1-min winds = 35 | 1-min winds = 35
| Pressure = 996 | Pressure = 996
}}{{main|Tropical Depression Josie}}
}}


{{Citation needed span|text=A tropical depression formed in the South China Sea on July 20 according to the JMA. On July 21, the system entered the Philippine Area of Responsibility and was assigned the local name Josie, making it the 10th named storm to enter the PAR. The JTWC upgraded the system to a tropical storm on the same day. The system missed landfall within kilometers on Saud, Ilocos Norte. It moved north and exited the PAR on the next day. The remnants of 13W dissipated off the coast of China.|date=May 2021}} {{Citation needed span|text=A tropical depression formed in the South China Sea on July 20 according to the JMA. On July 21, the system entered the Philippine Area of Responsibility and was assigned the local name Josie, making it the 10th named storm to enter the PAR. The JTWC upgraded the system to a tropical storm on the same day. The system missed landfall within kilometers on Saud, Ilocos Norte. It moved north and exited the PAR on the next day. The remnants of 13W dissipated off the coast of China.|date=May 2021}}
Line 414: Line 408:
| Pressure = 990 | Pressure = 990
}} }}
Late on July 21, the JTWC began to issue advisories on Tropical Depression 14W as it developed about {{convert|603|km|mi|abbr=on}} east-southeast of the Japanese island of ].<ref>{{cite web|title=Tropical Depression 14W (Fourteen) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN34-PGTW_201807212100.htm|archive-url=https://www.webcitation.org/716EDAbvg?url=http://gwydir.demon.co.uk/advisories/WTPN34-PGTW_201807212100.htm|url-status=dead|date=July 21, 2018|archive-date=July 22, 2018|publisher=Joint Typhoon Warning Center}}</ref> The JMA began tracking the system on the early hours of July 22. Later that day, the JTWC upgraded 14W to a tropical storm, though convection was sheared and the system was located in unfavorable southwesterly shear.<ref>{{cite web|title=Tropical Storm 14W (Fourteen) Warning Nr 003|url=http://gwydir.demon.co.uk/advisories/WTPN34-PGTW_201807220900.htm|archive-url=https://www.webcitation.org/716ECRu7N?url=http://gwydir.demon.co.uk/advisories/WTPN34-PGTW_201807220900.htm|url-status=dead|date=July 22, 2018|archive-date=July 22, 2018|publisher=Joint Typhoon Warning Center}}</ref> Within the next 24 hours, 14W began to organize with deep convection obscuring its LLCC,<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 14W (Fourteen) Warning Nr 07|url=http://gwydir.demon.co.uk/advisories/WDPN34-PGTW_201807230900.htm|archive-url=https://www.webcitation.org/717xOWVlz?url=http://gwydir.demon.co.uk/advisories/WDPN34-PGTW_201807230900.htm|url-status=dead|date=July 23, 2018|archive-date=July 23, 2018|publisher=Joint Typhoon Warning Center}}</ref> and at 12:00 UTC on July 23, the JMA upgraded the system to a tropical storm, naming it ''Wukong''. Moving poleward, Wukong gradually intensified while entering an area of favorable environment with lesser shear, and at 00:00 UTC on July 25, the JMA upgraded Wukong to a severe tropical storm. Nine hours later, the JTWC upgraded Wukong to a Category 1 typhoon after satellite images depicted a 30-nmi ragged ].<ref>{{cite web|title=Prognostic Reasoning for Typhoon 14W (Fourteen) Warning Nr 15|url=http://gwydir.demon.co.uk/advisories/WDPN34-PGTW_201807250900.htm|archive-url=https://www.webcitation.org/71B5greA0?url=http://gwydir.demon.co.uk/advisories/WDPN34-PGTW_201807250900.htm|url-status=dead|date=July 25, 2018|archive-date=July 25, 2018|publisher=Joint Typhoon Warning Center}}</ref> By July 26, both the JMA and the JTWC issued their final advisories on Wukong as the system rapidly transitioned into an extratropical cyclone.<ref>{{cite web|title=Tropical Storm 14W (Wukong) Warning Nr 020|url=http://gwydir.demon.co.uk/advisories/WTPN34-PGTW_201807261500.htm|archive-url=https://www.webcitation.org/71DmJxt7V?url=http://gwydir.demon.co.uk/advisories/WTPN34-PGTW_201807261500.htm|url-status=dead|date=July 26, 2018|archive-date=July 27, 2018|publisher=Joint Typhoon Warning Center}}</ref> Wukong's extratropical remnants were tracked until late on July 27 when it was last noticed off the eastern coast of ].<ref>{{Cite web |url=http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp142018.dat |title=Archived copy |access-date=2018-08-18 |archive-date=2018-08-29 |archive-url=https://web.archive.org/web/20180829010705/http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp142018.dat |url-status=live }}</ref> Late on July 21, the JTWC began to issue advisories on Tropical Depression 14W as it developed about {{convert|603|km|mi|abbr=on}} east-southeast of the Japanese island of ].<ref>{{cite web|title=Tropical Depression 14W (Fourteen) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN34-PGTW_201807212100.htm|archive-url=https://archive.today/20240524023323/https://www.webcitation.org/716EDAbvg?url=http://gwydir.demon.co.uk/advisories/WTPN34-PGTW_201807212100.htm|url-status=dead|date=July 21, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> The JMA began tracking the system on the early hours of July 22. Later that day, the JTWC upgraded 14W to a tropical storm, though convection was sheared and the system was located in unfavorable southwesterly shear.<ref>{{cite web|title=Tropical Storm 14W (Fourteen) Warning Nr 003|url=http://gwydir.demon.co.uk/advisories/WTPN34-PGTW_201807220900.htm|archive-url=https://archive.today/20240524023242/https://www.webcitation.org/716ECRu7N?url=http://gwydir.demon.co.uk/advisories/WTPN34-PGTW_201807220900.htm|url-status=dead|date=July 22, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> Within the next 24 hours, 14W began to organize with deep convection obscuring its LLCC,<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 14W (Fourteen) Warning Nr 07|url=http://gwydir.demon.co.uk/advisories/WDPN34-PGTW_201807230900.htm|archive-url=https://archive.today/20240524023443/https://www.webcitation.org/717xOWVlz?url=http://gwydir.demon.co.uk/advisories/WDPN34-PGTW_201807230900.htm|url-status=dead|date=July 23, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> and at 12:00 UTC on July 23, the JMA upgraded the system to a tropical storm, naming it ''Wukong''. Moving poleward, Wukong gradually intensified while entering an area of favorable environment with lesser shear, and at 00:00 UTC on July 25, the JMA upgraded Wukong to a severe tropical storm. Nine hours later, the JTWC upgraded Wukong to a Category 1 typhoon after satellite images depicted a 30-nmi ragged ].<ref>{{cite web|title=Prognostic Reasoning for Typhoon 14W (Fourteen) Warning Nr 15|url=http://gwydir.demon.co.uk/advisories/WDPN34-PGTW_201807250900.htm|archive-url=https://archive.today/20240524023602/https://www.webcitation.org/71B5greA0?url=http://gwydir.demon.co.uk/advisories/WDPN34-PGTW_201807250900.htm|url-status=dead|date=July 25, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> By July 26, both the JMA and the JTWC issued their final advisories on Wukong as the system rapidly transitioned into an extratropical cyclone.<ref>{{cite web|title=Tropical Storm 14W (Wukong) Warning Nr 020|url=http://gwydir.demon.co.uk/advisories/WTPN34-PGTW_201807261500.htm|archive-url=https://archive.today/20240524023725/https://www.webcitation.org/71DmJxt7V?url=http://gwydir.demon.co.uk/advisories/WTPN34-PGTW_201807261500.htm|url-status=dead|date=July 26, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> Wukong's extratropical remnants were tracked until late on July 27 when it was last noticed off the eastern coast of ].<ref>{{Cite web |url=http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp142018.dat |title=Archived copy |access-date=2018-08-18 |archive-date=2018-08-29 |archive-url=https://web.archive.org/web/20180829010705/http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp142018.dat |url-status=live }}</ref>
{{clear}} {{clear}}


Line 429: Line 423:
}} }}
{{Main|Typhoon Jongdari}} {{Main|Typhoon Jongdari}}
A tropical disturbance formed southeast of ] on July 19 and tracked westward steadily.<ref>{{Cite web|url=http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp152018.dat|title=bwp152018.dat|publisher=Joint Typhoon Warning Center|access-date=July 27, 2018|archive-date=July 26, 2018|archive-url=https://web.archive.org/web/20180726191327/http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp152018.dat|url-status=live}}</ref> After issuing a ] on July 21, the ] (JTWC) upgraded the system to a tropical depression early on July 22, although the location of its low-level circulation center was not clear.<ref>{{Cite web|url=https://www.wis-jma.go.jp/d/o/PGTW/Alphanumeric/Warning/Tropical_cyclone/20180722/030000/A_WDPN35PGTW220300_C_RJTD_20180722030944_21.txt|title=Prognostic Reasoning for Tropical Depression 15W (Fifteen) Warning Nr 01|date=July 22, 2018|archive-url=https://www.webcitation.org/7199oPab0?url=http://gwydir.demon.co.uk/advisories/WDPN35-PGTW_201807220300.htm|archive-date=July 24, 2018|access-date=July 27, 2018|url-status=live|df=mdy-all}}</ref> The ] (JMA), however, kept reporting it as a low-pressure area until it was upgraded to a tropical depression late on July 23.<ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/ww/wwjp25.rjtd..txt|title=WWJP25 RJTD 231800|date=July 23, 2018|publisher=Japan Meteorological Agency|archive-url=https://www.webcitation.org/7198wsnmg?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201807231800.htm|archive-date=July 24, 2018|access-date=July 27, 2018|url-status=live|df=mdy-all}}</ref> After slow consolidation for several days, the system was upgraded to a tropical storm near ] at around 18:00 on July 24 by the JMA and the JTWC, being assigned the international name ''Jongdari''.<ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wt/wtpq20.rjtd..txt|title=RSMC Tropical Cyclone Advisory 241800|date=July 24, 2017|publisher=Japan Meteorological Agency|archive-url=https://www.webcitation.org/71B8lHgeM?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201807241800.htm|archive-date=July 25, 2018|access-date=July 27, 2017|url-status=live|df=mdy-all}}</ref><ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wd/wdpn35.pgtw..txt|title=Prognostic Reasoning for Tropical Storm 15W (Jongdari) Warning Nr 12|date=July 24, 2018|archive-url=https://www.webcitation.org/71B7rKE7u?url=http://gwydir.demon.co.uk/advisories/WDPN35-PGTW_201807242100.htm|archive-date=July 25, 2018|access-date=July 27, 2018|url-status=live|df=mdy-all}}</ref> ] imagery revealed a low-level eyewall forming on the next day, indicating a consolidating system. After the JMA upgraded Jongdari to a severe tropical storm at noon,<ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wt/wtpq20.rjtd..txt|title=RSMC Tropical Cyclone Advisory 251200|date=July 25, 2017|publisher=Japan Meteorological Agency|archive-url=https://www.webcitation.org/71B8aVUiN?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201807251200.htm|archive-date=July 25, 2018|access-date=July 28, 2017|url-status=live|df=mdy-all}}</ref> the system accelerated northeastward under the influence of a near-equatorial ridge to the south.<ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wd/wdpn35.pgtw..txt|title=Prognostic Reasoning for Tropical Storm 15W (Jongdari) Warning Nr 15|date=July 25, 2018|archive-url=https://www.webcitation.org/71B7pwxDJ?url=http://gwydir.demon.co.uk/advisories/WDPN35-PGTW_201807251500.htm|archive-date=July 25, 2018|access-date=July 28, 2018|url-status=live|df=mdy-all}}</ref> A tropical disturbance formed southeast of ] on July 19 and tracked westward steadily.<ref>{{Cite web|url=http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp152018.dat|title=bwp152018.dat|publisher=Joint Typhoon Warning Center|access-date=July 27, 2018|archive-date=July 26, 2018|archive-url=https://web.archive.org/web/20180726191327/http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp152018.dat|url-status=live}}</ref> After issuing a ] on July 21, the ] (JTWC) upgraded the system to a tropical depression early on July 22, although the location of its low-level circulation center was not clear.<ref>{{Cite web|url=https://www.wis-jma.go.jp/d/o/PGTW/Alphanumeric/Warning/Tropical_cyclone/20180722/030000/A_WDPN35PGTW220300_C_RJTD_20180722030944_21.txt|title=Prognostic Reasoning for Tropical Depression 15W (Fifteen) Warning Nr 01|date=July 22, 2018|archive-url=https://archive.today/20240523072050/https://www.webcitation.org/7199oPab0?url=http://gwydir.demon.co.uk/advisories/WDPN35-PGTW_201807220300.htm|archive-date=May 23, 2024|access-date=July 27, 2018|url-status=live|df=mdy-all}}</ref> The ] (JMA), however, kept reporting it as a low-pressure area until it was upgraded to a tropical depression late on July 23.<ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/ww/wwjp25.rjtd..txt|title=WWJP25 RJTD 231800|date=July 23, 2018|publisher=Japan Meteorological Agency|archive-url=https://archive.today/20240523072010/https://www.webcitation.org/7198wsnmg?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201807231800.htm|archive-date=May 23, 2024|access-date=July 27, 2018|url-status=live|df=mdy-all}}</ref> After slow consolidation for several days, the system was upgraded to a tropical storm near ] at around 18:00 on July 24 by the JMA and the JTWC, being assigned the international name ''Jongdari''.<ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wt/wtpq20.rjtd..txt|title=RSMC Tropical Cyclone Advisory 241800|date=July 24, 2017|publisher=Japan Meteorological Agency|archive-url=https://archive.today/20240523072331/https://www.webcitation.org/71B8lHgeM?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201807241800.htm|archive-date=May 23, 2024|access-date=July 27, 2017|url-status=live|df=mdy-all}}</ref><ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wd/wdpn35.pgtw..txt|title=Prognostic Reasoning for Tropical Storm 15W (Jongdari) Warning Nr 12|date=July 24, 2018|archive-url=https://archive.today/20240523072213/https://www.webcitation.org/71B7rKE7u?url=http://gwydir.demon.co.uk/advisories/WDPN35-PGTW_201807242100.htm|archive-date=May 23, 2024|access-date=July 27, 2018|url-status=live|df=mdy-all}}</ref> ] imagery revealed a low-level eyewall forming on the next day, indicating a consolidating system. After the JMA upgraded Jongdari to a severe tropical storm at noon,<ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wt/wtpq20.rjtd..txt|title=RSMC Tropical Cyclone Advisory 251200|date=July 25, 2017|publisher=Japan Meteorological Agency|archive-url=https://archive.today/20240523072251/https://www.webcitation.org/71B8aVUiN?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201807251200.htm|archive-date=May 23, 2024|access-date=July 28, 2017|url-status=live|df=mdy-all}}</ref> the system accelerated northeastward under the influence of a near-equatorial ridge to the south.<ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wd/wdpn35.pgtw..txt|title=Prognostic Reasoning for Tropical Storm 15W (Jongdari) Warning Nr 15|date=July 25, 2018|archive-url=https://archive.today/20240523072131/https://www.webcitation.org/71B7pwxDJ?url=http://gwydir.demon.co.uk/advisories/WDPN35-PGTW_201807251500.htm|archive-date=May 23, 2024|access-date=July 28, 2018|url-status=live|df=mdy-all}}</ref>


On July 26, as Jongdari started to interact with an upper-level ] to the north which significantly enhanced poleward ],<ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wd/wdpn35.pgtw..txt|title=Prognostic Reasoning for Tropical Storm 15W (Jongdari) Warning Nr 19|date=July 26, 2018|archive-url=https://www.webcitation.org/71DlA9HrD?url=http://gwydir.demon.co.uk/advisories/WDPN35-PGTW_201807261500.htm|archive-date=July 27, 2018|access-date=July 28, 2018|url-status=live|df=mdy-all}}</ref> it intensified to a ] in the afternoon despite increasingly unfavorable vertical ].<ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wt/wtpq20.rjtd..txt|title=RSMC Tropical Cyclone Advisory 261200|date=July 26, 2017|publisher=Japan Meteorological Agency|archive-url=https://www.webcitation.org/71Dk7NnSB?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201807261200.htm|archive-date=July 27, 2018|access-date=July 28, 2017|url-status=live|df=mdy-all}}</ref> Over the warm ]s between {{convert|29|and|30|C|F}} near the ], JMA reported that Jongdari had reached peak intensity at 00:00 ] on July 27, with ten-minute ] of {{convert|140|km/h|mph|abbr=on}} and a minimum central pressure of {{convert|965|hPa|inHg|abbr=on}}.<ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wt/wtpq20.rjtd..txt|title=RSMC Tropical Cyclone Advisory 270000|date=July 27, 2017|publisher=Japan Meteorological Agency|archive-url=https://www.webcitation.org/71Dk5qppU?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201807270000.htm|archive-date=July 27, 2018|access-date=July 28, 2017|url-status=live|df=mdy-all}}</ref> Although the JTWC indicated Jongdari reached peak intensity at 12:00 UTC with one-minute maximum sustained winds of {{convert|175|km/h|mph|abbr=on}}, the rugged ] of Jongdari remained periodically visible with an elongated structure due to further interaction of the upper-level low which had moved to the northwest side of the typhoon. As the steering influence transitioned to a ] to the northeast, Jongdari executed a counter-clockwise turn to the southeast of ].<ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wd/wdpn35.pgtw..txt|title=Prognostic Reasoning for Typhoon 15W (Jongdari) Warning Nr 23|date=July 27, 2018|archive-url=https://www.webcitation.org/71FHEn6Pf?url=http://gwydir.demon.co.uk/advisories/WDPN35-PGTW_201807271500.htm|archive-date=July 28, 2018|access-date=July 28, 2018|url-status=live|df=mdy-all}}</ref> On July 26, as Jongdari started to interact with an upper-level ] to the north which significantly enhanced poleward ],<ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wd/wdpn35.pgtw..txt|title=Prognostic Reasoning for Tropical Storm 15W (Jongdari) Warning Nr 19|date=July 26, 2018|archive-url=https://archive.today/20240523072536/https://www.webcitation.org/71DlA9HrD?url=http://gwydir.demon.co.uk/advisories/WDPN35-PGTW_201807261500.htm|archive-date=May 23, 2024|access-date=July 28, 2018|url-status=live|df=mdy-all}}</ref> it intensified to a ] in the afternoon despite increasingly unfavorable vertical ].<ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wt/wtpq20.rjtd..txt|title=RSMC Tropical Cyclone Advisory 261200|date=July 26, 2017|publisher=Japan Meteorological Agency|archive-url=https://archive.today/20240523072452/https://www.webcitation.org/71Dk7NnSB?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201807261200.htm|archive-date=May 23, 2024|access-date=July 28, 2017|url-status=live|df=mdy-all}}</ref> Over the warm ]s between {{convert|29|and|30|C|F}} near the ], JMA reported that Jongdari had reached peak intensity at 00:00 ] on July 27, with ten-minute ] of {{convert|140|km/h|mph|abbr=on}} and a minimum central pressure of {{convert|965|hPa|inHg|abbr=on}}.<ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wt/wtpq20.rjtd..txt|title=RSMC Tropical Cyclone Advisory 270000|date=July 27, 2017|publisher=Japan Meteorological Agency|archive-url=https://archive.today/20240523072413/https://www.webcitation.org/71Dk5qppU?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201807270000.htm|archive-date=May 23, 2024|access-date=July 28, 2017|url-status=live|df=mdy-all}}</ref> Although the JTWC indicated Jongdari reached peak intensity at 12:00 UTC with one-minute maximum sustained winds of {{convert|175|km/h|mph|abbr=on}}, the rugged ] of Jongdari remained periodically visible with an elongated structure due to further interaction of the upper-level low which had moved to the northwest side of the typhoon. As the steering influence transitioned to a ] to the northeast, Jongdari executed a counter-clockwise turn to the southeast of ].<ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wd/wdpn35.pgtw..txt|title=Prognostic Reasoning for Typhoon 15W (Jongdari) Warning Nr 23|date=July 27, 2018|archive-url=https://archive.today/20240523072612/https://www.webcitation.org/71FHEn6Pf?url=http://gwydir.demon.co.uk/advisories/WDPN35-PGTW_201807271500.htm|archive-date=May 23, 2024|access-date=July 28, 2018|url-status=live|df=mdy-all}}</ref>


Jongdari began to be inundated by ] on July 28 as the ] had made the upper-level low move to the west of the typhoon.<ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wd/wdpn35.pgtw..txt|title=Prognostic Reasoning for Typhoon 15W (Jongdari) Warning Nr 25|date=July 28, 2018|archive-url=https://www.webcitation.org/71FHLbwbt?url=http://gwydir.demon.co.uk/advisories/WDPN35-PGTW_201807280300.htm|archive-date=July 28, 2018|access-date=July 28, 2018|url-status=live|df=mdy-all}}</ref> It also initiated a weakening trend while accelerating northwestward and then westward toward the Japanese island of ]. At around 01:00 ] on July 29 (16:00 UTC July 28), Jongdari made ] over ], ] with ten-minute maximum sustained winds of {{convert|120|km/h|mph|abbr=on}} and a central pressure of {{convert|975|hPa|inHg|abbr=on}}.<ref>{{Cite web|url=https://www.jma.go.jp/jp/kishojoho/000_00_662_20180728160345.html|script-title=ja:平成30年 台風第12号に関する情報 第73号|date=July 28, 2018|publisher=Japan Meteorological Agency|language=ja|archive-url=https://web.archive.org/web/20180728161214/https://www.jma.go.jp/jp/kishojoho/000_00_662_20180728160345.html|archive-date=July 28, 2018|access-date=July 28, 2018}}</ref><ref>{{Cite web|url=https://www.jma.go.jp/jp/typh/181224.html|script-title=ja:台風第12号 (ジョンダリ) 平成30年07月29日01時50分 発表|date=July 28, 2018|publisher=Japan Meteorological Agency|language=ja|archive-url=https://web.archive.org/web/20180728170942/https://www.jma.go.jp/jp/typh/181224.html|archive-date=July 28, 2018|access-date=July 28, 2018}}</ref> The storm weakened rapidly inland before making its second landfall over ], ], at around 17:30 JST (08:30 UTC), with ten-minute sustained winds of {{convert|75|km/h|mph|abbr=on}} and a central pressure of {{convert|992|hPa|inHg|abbr=on}}.<ref>{{Cite web|url=https://www.jma.go.jp/jp/kishojoho/000_00_662_20180729083814.html|script-title=ja:平成30年 台風第12号に関する情報 第94号|date=July 29, 2018|publisher=Japan Meteorological Agency|language=ja|archive-url=https://web.archive.org/web/20180729133959/https://www.jma.go.jp/jp/kishojoho/000_00_662_20180729083814.html|archive-date=July 29, 2018|access-date=July 29, 2018}}</ref> At around 10:30 ] (02:30 UTC) on August 3, Jongdari made landfall over ], ] as a tropical storm.<ref>{{Cite web|url=http://www.nmc.cn/publish/typhoon/warning.html|script-title=zh:中央气象台03日10时30分发布台风登陆消息|date=August 3, 2018|publisher=]|language=zh|archive-url=https://web.archive.org/web/20180803023837/http://www.nmc.cn/publish/typhoon/warning.html|archive-date=August 3, 2018|access-date=August 3, 2018}}</ref> Jongdari rapidly weakened after landfall, dissipating on the next day. No fatalities were recorded for this storm. Jongdari began to be inundated by ] on July 28 as the ] had made the upper-level low move to the west of the typhoon.<ref>{{Cite web|url=http://tgftp.nws.noaa.gov/data/raw/wd/wdpn35.pgtw..txt|title=Prognostic Reasoning for Typhoon 15W (Jongdari) Warning Nr 25|date=July 28, 2018|archive-url=https://archive.today/20240523072653/https://www.webcitation.org/71FHLbwbt?url=http://gwydir.demon.co.uk/advisories/WDPN35-PGTW_201807280300.htm|archive-date=May 23, 2024|access-date=July 28, 2018|url-status=live|df=mdy-all}}</ref> It also initiated a weakening trend while accelerating northwestward and then westward toward the Japanese island of ]. At around 01:00 ] on July 29 (16:00 UTC July 28), Jongdari made ] over ], ] with ten-minute maximum sustained winds of {{convert|120|km/h|mph|abbr=on}} and a central pressure of {{convert|975|hPa|inHg|abbr=on}}.<ref>{{Cite web|url=https://www.jma.go.jp/jp/kishojoho/000_00_662_20180728160345.html|script-title=ja:平成30年 台風第12号に関する情報 第73号|date=July 28, 2018|publisher=Japan Meteorological Agency|language=ja|archive-url=https://web.archive.org/web/20180728161214/https://www.jma.go.jp/jp/kishojoho/000_00_662_20180728160345.html|archive-date=July 28, 2018|access-date=July 28, 2018}}</ref><ref>{{Cite web|url=https://www.jma.go.jp/jp/typh/181224.html|script-title=ja:台風第12号 (ジョンダリ) 平成30年07月29日01時50分 発表|date=July 28, 2018|publisher=Japan Meteorological Agency|language=ja|archive-url=https://web.archive.org/web/20180728170942/https://www.jma.go.jp/jp/typh/181224.html|archive-date=July 28, 2018|access-date=July 28, 2018}}</ref> The storm weakened rapidly inland before making its second landfall over ], ], at around 17:30 JST (08:30 UTC), with ten-minute sustained winds of {{convert|75|km/h|mph|abbr=on}} and a central pressure of {{convert|992|hPa|inHg|abbr=on}}.<ref>{{Cite web|url=https://www.jma.go.jp/jp/kishojoho/000_00_662_20180729083814.html|script-title=ja:平成30年 台風第12号に関する情報 第94号|date=July 29, 2018|publisher=Japan Meteorological Agency|language=ja|archive-url=https://web.archive.org/web/20180729133959/https://www.jma.go.jp/jp/kishojoho/000_00_662_20180729083814.html|archive-date=July 29, 2018|access-date=July 29, 2018}}</ref> At around 10:30 ] (02:30 UTC) on August 3, Jongdari made landfall over ], ] as a tropical storm.<ref>{{Cite web|url=http://www.nmc.cn/publish/typhoon/warning.html|script-title=zh:中央气象台03日10时30分发布台风登陆消息|date=August 3, 2018|publisher=]|language=zh|archive-url=https://web.archive.org/web/20180803023837/http://www.nmc.cn/publish/typhoon/warning.html|archive-date=August 3, 2018|access-date=August 3, 2018}}</ref> Jongdari rapidly weakened after landfall, dissipating on the next day. No fatalities were recorded for this storm.
{{clear}} {{clear}}


Line 448: Line 442:
| Pressure = 1002 | Pressure = 1002
}} }}
A tropical disturbance developed about {{convert|807|km|mi|abbr=on}} north-northeast of ] by July 29.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/ABPW10-PGTW_201807290600.htm |title=Archived copy |access-date=2018-07-29 |archive-url=https://www.webcitation.org/71H5VsKfg?url=http://gwydir.demon.co.uk/advisories/ABPW10-PGTW_201807290600.htm |archive-date=2018-07-29 |url-status=dead }}</ref> The JTWC upgraded the system to Tropical Depression 16W during the next day after its convective structure had slightly improved despite the system located in moderate to strong wind shear.<ref>{{cite web|title=Tropical Depression 16W (Sixteen) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807301500.htm|archive-url=https://www.webcitation.org/71KRlxGP2?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807301500.htm|url-status=dead|date=July 30, 2018|archive-date=July 31, 2018|publisher=Joint Typhoon Warning Center}}</ref> By July 31, the JMA followed suit on classifying the system as a tropical depression.<ref name="webcitation.org">{{Cite web |url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201807310000.htm |title=Archived copy |access-date=2018-07-31 |archive-url=https://www.webcitation.org/71KRs7CE9?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201807310000.htm |archive-date=2018-07-31 |url-status=dead }}</ref> 16W's center late became exposed with deep convection displaced due to continued shear.<ref>{{cite web|title=Prognostic Reasoning for Tropical Depression 16W (Sixteen) Warning Nr 02|url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807302100.htm|archive-url=https://www.webcitation.org/71KRg3Mzt?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807302100.htm|url-status=dead|date=July 30, 2018|archive-date=July 31, 2018|publisher=Joint Typhoon Warning Center}}</ref> Originally, the system was forecast to reach tropical storm intensity with only 35 knot winds,<ref>{{cite web|title=Tropical Depression 16W (Sixteen) Warning Nr 004|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807310900.htm|archive-url=https://www.webcitation.org/71KRkl1mn?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807310900.htm|url-status=dead|date=July 31, 2018|archive-date=July 31, 2018|publisher=Joint Typhoon Warning Center}}</ref> but the system's center had become asymmetric with a fully sheared center.<ref>{{cite web|title=Prognostic Reasoning for Tropical Depression 16W (Sixteen) Warning Nr 05|url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807311500.htm|archive-url=https://www.webcitation.org/71KReu3eI?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807311500.htm|url-status=dead|date=July 31, 2018|archive-date=July 31, 2018|publisher=Joint Typhoon Warning Center}}</ref> The JTWC issued their final advisory on 21:00 UTC of the same day, after 16W had fully transitioned into a subtropical cyclone, though both agencies continued to track the system until August 2.<ref>{{cite web|title=Tropical Depression 16W (Sixteen) Warning Nr 006|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807312100.htm|archive-url=https://www.webcitation.org/71LmwAmw0?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807312100.htm|url-status=dead|date=July 31, 2018|archive-date=August 1, 2018|publisher=Joint Typhoon Warning Center}}</ref><ref>{{Cite web |url=http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp162018.dat |title=Archived copy |access-date=2018-08-02 |archive-date=2018-08-02 |archive-url=https://web.archive.org/web/20180802132017/http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp162018.dat |url-status=live }}</ref> A tropical disturbance developed about {{convert|807|km|mi|abbr=on}} north-northeast of ] by July 29.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/ABPW10-PGTW_201807290600.htm |title=Archived copy |access-date=2018-07-29 |archive-url=https://archive.today/20240522234308/https://www.webcitation.org/71H5VsKfg?url=http://gwydir.demon.co.uk/advisories/ABPW10-PGTW_201807290600.htm |archive-date=2024-05-22 |url-status=dead }}</ref> The JTWC upgraded the system to Tropical Depression 16W during the next day after its convective structure had slightly improved despite the system located in moderate to strong wind shear.<ref>{{cite web|title=Tropical Depression 16W (Sixteen) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807301500.htm|archive-url=https://archive.today/20240524024328/https://www.webcitation.org/71KRlxGP2?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807301500.htm|url-status=dead|date=July 30, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> By July 31, the JMA followed suit on classifying the system as a tropical depression.<ref name="webcitation.org">{{Cite web |url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201807310000.htm |title=Archived copy |access-date=2018-07-31 |archive-url=https://archive.today/20240522192611/https://www.webcitation.org/71KRs7CE9?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201807310000.htm |archive-date=2024-05-22 |url-status=dead }}</ref> 16W's center late became exposed with deep convection displaced due to continued shear.<ref>{{cite web|title=Prognostic Reasoning for Tropical Depression 16W (Sixteen) Warning Nr 02|url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807302100.htm|archive-url=https://archive.today/20240524024207/https://www.webcitation.org/71KRg3Mzt?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807302100.htm|url-status=dead|date=July 30, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> Originally, the system was forecast to reach tropical storm intensity with only 35 knot winds,<ref>{{cite web|title=Tropical Depression 16W (Sixteen) Warning Nr 004|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807310900.htm|archive-url=https://archive.today/20240524024248/https://www.webcitation.org/71KRkl1mn?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807310900.htm|url-status=dead|date=July 31, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> but the system's center had become asymmetric with a fully sheared center.<ref>{{cite web|title=Prognostic Reasoning for Tropical Depression 16W (Sixteen) Warning Nr 05|url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807311500.htm|archive-url=https://archive.today/20240524024125/https://www.webcitation.org/71KReu3eI?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201807311500.htm|url-status=dead|date=July 31, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> The JTWC issued their final advisory on 21:00 UTC of the same day, after 16W had fully transitioned into a subtropical cyclone, though both agencies continued to track the system until August 2.<ref>{{cite web|title=Tropical Depression 16W (Sixteen) Warning Nr 006|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807312100.htm|archive-url=https://archive.today/20240524024407/https://www.webcitation.org/71LmwAmw0?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201807312100.htm|url-status=dead|date=July 31, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref><ref>{{Cite web |url=http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp162018.dat |title=Archived copy |access-date=2018-08-02 |archive-date=2018-08-02 |archive-url=https://web.archive.org/web/20180802132017/http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp162018.dat |url-status=live }}</ref>
{{clear}} {{clear}}


===Typhoon Shanshan=== ===Typhoon Shanshan===
{{main|Typhoon Shanshan (2018)}}
{{Infobox hurricane small {{Infobox hurricane small
| Basin = WPac | Basin = WPac
Line 462: Line 455:
| 1-min winds = 85 | 1-min winds = 85
| Pressure = 970 | Pressure = 970
}}{{main|Typhoon Shanshan (2018)}}
}}
A tropical depression developed east-northeast of ] on August 2. At 21:00 UTC on the same day, the JTWC began tracking the system, giving it the identifier ''17W''.<ref>{{cite web|title=Tropical Depression 17W (Seventeen) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201808022100.htm|archive-url=https://www.webcitation.org/71OkfsOzG?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201808022100.htm|url-status=dead|date=August 2, 2018|archive-date=August 3, 2018|publisher=Joint Typhoon Warning Center}}</ref> 17W intensified into a tropical storm on August 3, with the JMA assigning it the name ''Shanshan''.<ref>{{cite web|title=Tropical Storm 17W (Shanshan) Warning Nr 003|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201808030900.htm|archive-url=https://www.webcitation.org/71Okf8Fn4?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201808030900.htm|url-status=dead|date=August 3, 2018|archive-date=August 3, 2018|publisher=Joint Typhoon Warning Center}}</ref> The storm was located over a favorable environment as the system was gradually consolidating,<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 17W (Shanshan) Warning Nr 04|url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201808031500.htm|archive-url=https://www.webcitation.org/71PkKoqiL?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201808031500.htm|url-status=dead|date=August 3, 2018|archive-date=August 4, 2018|publisher=Joint Typhoon Warning Center}}</ref> and it intensified into a severe tropical storm on August 3. During the next day, both the JMA and JTWC upgraded Shanshan to a typhoon after deep convection was seen wrapping into its developing center. The JMA later analysed that the storm had peaked in intensity with 10-minute winds of {{convert|130|km/h|mph|abbr=on}} and a minimum pressure of 970 hPa, remaining that intensity for several days. The JTWC stated that Shanshan had slightly weakened after a strengthening trend by August 6 after its ] became ragged and slightly displaced. On August 7, Shanshan began to re-intensify and reached its peak strength as a Category 2 typhoon with 1-minute winds of {{convert|165|km/h|mph|abbr=on}} while nearing southeastern ]. Thereafter, Shanshan began to change its course towards the east as it rapidly weakened. The JTWC issued their final advisory on August 9, though the JMA tracked the system until it became extratropical at 06:00 UTC on August 10. A tropical depression developed east-northeast of ] on August 2. At 21:00 UTC on the same day, the JTWC began tracking the system, giving it the identifier ''17W''.<ref>{{cite web|title=Tropical Depression 17W (Seventeen) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201808022100.htm|archive-url=https://archive.today/20240523131355/https://www.webcitation.org/71OkfsOzG?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201808022100.htm|url-status=dead|date=August 2, 2018|archive-date=May 23, 2024|publisher=Joint Typhoon Warning Center}}</ref> 17W intensified into a tropical storm on August 3, with the JMA assigning it the name ''Shanshan''.<ref>{{cite web|title=Tropical Storm 17W (Shanshan) Warning Nr 003|url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201808030900.htm|archive-url=https://archive.today/20240523131311/https://www.webcitation.org/71Okf8Fn4?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201808030900.htm|url-status=dead|date=August 3, 2018|archive-date=May 23, 2024|publisher=Joint Typhoon Warning Center}}</ref> The storm was located over a favorable environment as the system was gradually consolidating,<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 17W (Shanshan) Warning Nr 04|url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201808031500.htm|archive-url=https://archive.today/20240523131438/https://www.webcitation.org/71PkKoqiL?url=http://gwydir.demon.co.uk/advisories/WDPN31-PGTW_201808031500.htm|url-status=dead|date=August 3, 2018|archive-date=May 23, 2024|publisher=Joint Typhoon Warning Center}}</ref> and it intensified into a severe tropical storm on August 3. During the next day, both the JMA and JTWC upgraded Shanshan to a typhoon after deep convection was seen wrapping into its developing center. The JMA later analysed that the storm had peaked in intensity with 10-minute winds of {{convert|130|km/h|mph|abbr=on}} and a minimum pressure of 970 hPa, remaining that intensity for several days. The JTWC stated that Shanshan had slightly weakened after a strengthening trend by August 6 after its ] became ragged and slightly displaced. On August 7, Shanshan began to re-intensify and reached its peak strength as a Category 2 typhoon with 1-minute winds of {{convert|165|km/h|mph|abbr=on}} while nearing southeastern ]. Thereafter, Shanshan began to change its course towards the east as it rapidly weakened. The JTWC issued their final advisory on August 9, though the JMA tracked the system until it became extratropical at 06:00 UTC on August 10.


Losses in ] were counted at ]96.2 million (US$866,000).<ref>{{cite report|url=https://www.pref.miyagi.jp/uploaded/attachment/719494.pdf|title=平成30年の災害等の発生状況|language=ja|publisher=Miyagi Prefectural Government|year=2018|access-date=November 11, 2018|archive-date=July 27, 2019|archive-url=https://web.archive.org/web/20190727163611/https://www.pref.miyagi.jp/uploaded/attachment/719494.pdf|url-status=live}}</ref> Losses in ] were counted at ]96.2 million (US$866,000).<ref>{{cite report|url=https://www.pref.miyagi.jp/uploaded/attachment/719494.pdf|title=平成30年の災害等の発生状況|language=ja|publisher=Miyagi Prefectural Government|year=2018|access-date=November 11, 2018|archive-date=July 27, 2019|archive-url=https://web.archive.org/web/20190727163611/https://www.pref.miyagi.jp/uploaded/attachment/719494.pdf|url-status=live}}</ref>
Line 480: Line 473:
}} }}
{{main|Tropical Storm Yagi (2018)}} {{main|Tropical Storm Yagi (2018)}}
A tropical disturbance had persisted towards the southwest of ] on August&nbsp;1.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/ABPW10-PGTW_201808010600.htm |title=Archived copy |access-date=2018-08-01 |archive-url=https://www.webcitation.org/71LmypagG?url=http://gwydir.demon.co.uk/advisories/ABPW10-PGTW_201808010600.htm |archive-date=2018-08-01 |url-status=dead }}</ref> After the course of five days, the system was upgraded into a tropical depression by the JMA, with the JTWC following suit several hours later, designating it as ''18W''.<ref>{{cite web|title=Tropical Depression 18W (Eighteen) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201808062100.htm|archive-url=https://www.webcitation.org/71b6wj8DM?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201808062100.htm|url-status=dead|date=August 6, 2018|archive-date=August 11, 2018|publisher=Joint Typhoon Warning Center}}</ref> The PAGASA also began issuing bulletins on the system, assigning it the local name ''Karding''. Karding maintained its intensity as a tropical depression due to moderate to strong easterly shear despite persistent convection surrounding the system.<ref>{{cite web|title=Prognostic Reasoning for Tropical Depression 18W (Eighteen) Warning Nr 03|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808070900.htm|archive-url=https://www.webcitation.org/71fA7RmYH?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808070900.htm|url-status=dead|date=August 7, 2018|archive-date=August 14, 2018|publisher=Joint Typhoon Warning Center}}</ref> By August&nbsp;8, a METOP-A ASCAT image showed that the system had winds of 35&nbsp;knots, which prompted the JTWC to upgrade it to a tropical storm.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 18W (Yagi) Warning Nr 07|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808080900.htm|archive-url=https://www.webcitation.org/71fA5s8io?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808080900.htm|url-status=dead|date=August 8, 2018|archive-date=August 14, 2018|publisher=Joint Typhoon Warning Center}}</ref> The JMA around the same time did the same, assigning it the name ''Yagi''. Within the next day, Yagi curved towards the northwest, struggling to intensify due to wind shear. At 12:00&nbsp;UTC on August&nbsp;11, the JMA estimated that Yagi reached its peak strength with 10-minute winds of {{convert|75|km/h|mph|abbr=on}} and a minimum pressure of 990&nbsp;hPa. A tropical disturbance had persisted towards the southwest of ] on August&nbsp;1.<ref>{{Cite web |url=http://gwydir.demon.co.uk/advisories/ABPW10-PGTW_201808010600.htm |title=Archived copy |access-date=2018-08-01 |archive-url=https://archive.today/20240523022657/https://www.webcitation.org/71LmypagG?url=http://gwydir.demon.co.uk/advisories/ABPW10-PGTW_201808010600.htm |archive-date=2024-05-23 |url-status=dead }}</ref> After the course of five days, the system was upgraded into a tropical depression by the JMA, with the JTWC following suit several hours later, designating it as ''18W''.<ref>{{cite web|title=Tropical Depression 18W (Eighteen) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201808062100.htm|archive-url=https://archive.today/20240523022334/https://www.webcitation.org/71b6wj8DM?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201808062100.htm|url-status=dead|date=August 6, 2018|archive-date=May 23, 2024|publisher=Joint Typhoon Warning Center}}</ref> The PAGASA also began issuing bulletins on the system, assigning it the local name ''Karding''. Karding maintained its intensity as a tropical depression due to moderate to strong easterly shear despite persistent convection surrounding the system.<ref>{{cite web|title=Prognostic Reasoning for Tropical Depression 18W (Eighteen) Warning Nr 03|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808070900.htm|archive-url=https://archive.today/20240523022614/https://www.webcitation.org/71fA7RmYH?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808070900.htm|url-status=dead|date=August 7, 2018|archive-date=May 23, 2024|publisher=Joint Typhoon Warning Center}}</ref> By August&nbsp;8, a METOP-A ASCAT image showed that the system had winds of 35&nbsp;knots, which prompted the JTWC to upgrade it to a tropical storm.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 18W (Yagi) Warning Nr 07|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808080900.htm|archive-url=https://archive.today/20240523022539/https://www.webcitation.org/71fA5s8io?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808080900.htm|url-status=dead|date=August 8, 2018|archive-date=May 23, 2024|publisher=Joint Typhoon Warning Center}}</ref> The JMA around the same time did the same, assigning it the name ''Yagi''. Within the next day, Yagi curved towards the northwest, struggling to intensify due to wind shear. At 12:00&nbsp;UTC on August&nbsp;11, the JMA estimated that Yagi reached its peak strength with 10-minute winds of {{convert|75|km/h|mph|abbr=on}} and a minimum pressure of 990&nbsp;hPa.


The JTWC declared that Yagi reached winds of {{convert|85|km/h|mph|abbr=on}} at 12:00&nbsp;UTC on August&nbsp;12 after the storm had consolidated further with an improved structure.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 18W (Yagi) Warning Nr 24|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808121500.htm|archive-url=https://www.webcitation.org/71f9zJVkw?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808121500.htm|url-status=dead|date=August 12, 2018|archive-date=August 14, 2018|publisher=Joint Typhoon Warning Center}}</ref> Yagi made landfall shortly thereafter over ], in ] of ], ], at around 23:35&nbsp;CST (15:35&nbsp;UTC) on August&nbsp;12.<ref>{{cite web|script-title=zh:中央气象台12日23时40分发布台风登陆消息|url=http://www.nmc.cn/publish/typhoon/warning.html|publisher=National Meteorological Center of CMA|access-date=August 12, 2018|archive-url=https://web.archive.org/web/20180812155813/http://www.nmc.cn/publish/typhoon/warning.html|archive-date=August 12, 2018|language=zh|date=August 12, 2018}}</ref> By 21:00&nbsp;UTC of that day, the JTWC issued their final advisory on Yagi,<ref>{{cite web|title=Tropical Storm 18W (Yagi) Warning Nr 025|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201808122100.htm|archive-url=https://www.webcitation.org/71ddqLY0g?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201808122100.htm|url-status=dead|date=August 12, 2018|archive-date=August 13, 2018|publisher=Joint Typhoon Warning Center}}</ref> though they continued to track it until it weakened further into a tropical depression early on August&nbsp;13.<ref>{{Cite web |url=http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp182018.dat |title=Archived copy |access-date=2018-08-18 |archive-date=2018-08-17 |archive-url=https://web.archive.org/web/20180817151752/http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp182018.dat |url-status=live }}</ref> The JMA did the same on 06:00&nbsp;UTC of August&nbsp;13. The JMA tracked Yagi until it became an extratropical system on August&nbsp;15. The JTWC declared that Yagi reached winds of {{convert|85|km/h|mph|abbr=on}} at 12:00&nbsp;UTC on August&nbsp;12 after the storm had consolidated further with an improved structure.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 18W (Yagi) Warning Nr 24|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808121500.htm|archive-url=https://archive.today/20240523022455/https://www.webcitation.org/71f9zJVkw?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808121500.htm|url-status=dead|date=August 12, 2018|archive-date=May 23, 2024|publisher=Joint Typhoon Warning Center}}</ref> Yagi made landfall shortly thereafter over ], in ] of ], ], at around 23:35&nbsp;CST (15:35&nbsp;UTC) on August&nbsp;12.<ref>{{cite web|script-title=zh:中央气象台12日23时40分发布台风登陆消息|url=http://www.nmc.cn/publish/typhoon/warning.html|publisher=National Meteorological Center of CMA|access-date=August 12, 2018|archive-url=https://web.archive.org/web/20180812155813/http://www.nmc.cn/publish/typhoon/warning.html|archive-date=August 12, 2018|language=zh|date=August 12, 2018}}</ref> By 21:00&nbsp;UTC of that day, the JTWC issued their final advisory on Yagi,<ref>{{cite web|title=Tropical Storm 18W (Yagi) Warning Nr 025|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201808122100.htm|archive-url=https://archive.today/20240523022414/https://www.webcitation.org/71ddqLY0g?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201808122100.htm|url-status=dead|date=August 12, 2018|archive-date=May 23, 2024|publisher=Joint Typhoon Warning Center}}</ref> though they continued to track it until it weakened further into a tropical depression early on August&nbsp;13.<ref>{{Cite web |url=http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp182018.dat |title=Archived copy |access-date=2018-08-18 |archive-date=2018-08-17 |archive-url=https://web.archive.org/web/20180817151752/http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp182018.dat |url-status=live }}</ref> The JMA did the same on 06:00&nbsp;UTC of August&nbsp;13. The JMA tracked Yagi until it became an extratropical system on August&nbsp;15.


Despite not making landfall on the ], the storm enhanced the ] which brought extreme flooding to many regions within the country. According to the NDRRMC, 5 people died along with ₱996 million (US$19 million) worth of damages.<ref name="Global Catastrophe Recap August 2018"/> In East China, Yagi killed a total of 3 people and total damages were counted to be CN¥2.51 billion (US$367 million).<ref name="China Member Report"/> Despite not making landfall on the ], the storm enhanced the ] which brought extreme flooding to many regions within the country. According to the NDRRMC, 5 people died along with ₱996 million (US$19 million) worth of damages.<ref name="Global Catastrophe Recap August 2018"/> In East China, Yagi killed a total of 3 people and total damages were counted to be CN¥2.51 billion (US$367 million).<ref name="China Member Report"/>
Line 499: Line 492:
}} }}
{{main|Tropical Storm Bebinca (2018)}} {{main|Tropical Storm Bebinca (2018)}}
On August&nbsp;9, a tropical depression formed within the ]. The system remained weak and remained stationary for a few days until the JTWC began tracking the system, giving it the designation ''20W'' on August&nbsp;12.<ref>{{cite web|title=Tropical Depression 20W (Twenty) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN33-PGTW_201808121500.htm|archive-url=https://www.webcitation.org/71dffWzIo?url=http://gwydir.demon.co.uk/advisories/WTPN33-PGTW_201808121500.htm|url-status=dead|date=August 12, 2018|archive-date=August 13, 2018|publisher=Joint Typhoon Warning Center}}</ref> On the next day, the JMA upgraded the system to a tropical storm, naming it ''Bebinca''. The JTWC followed suit nine hours later as deep convection flared near its compact center.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 20W (Bebinca) Warning Nr 04|url=http://gwydir.demon.co.uk/advisories/WDPN33-PGTW_201808130900.htm|archive-url=https://www.webcitation.org/71dfyW93u?url=http://gwydir.demon.co.uk/advisories/WDPN33-PGTW_201808130900.htm|url-status=dead|date=August 13, 2018|archive-date=August 13, 2018|publisher=Joint Typhoon Warning Center}}</ref> Despite consistent convection along with warm sea-surface temperatures, Bebinca remained weak for the next few days due to strong shear.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 20W (Bebinca) Warning Nr 11|url=http://gwydir.demon.co.uk/advisories/WDPN33-PGTW_201808150300.htm|archive-url=https://www.webcitation.org/71hOVDSQt?url=http://gwydir.demon.co.uk/advisories/WDPN33-PGTW_201808150300.htm|url-status=dead|date=August 15, 2018|archive-date=August 15, 2018|publisher=Joint Typhoon Warning Center}}</ref> By August&nbsp;16, however, Bebinca began to undergo a phase of rapid intensification as its center was obscured by a central dense overcast,<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 20W (Bebinca) Warning Nr 15 CORRECTED|url=http://gwydir.demon.co.uk/advisories/WDPN33-PGTW_201808160300.htm|archive-url=https://www.webcitation.org/71i8exOQ1?url=http://gwydir.demon.co.uk/advisories/WDPN33-PGTW_201808160300.htm|url-status=dead|date=August 16, 2018|archive-date=August 16, 2018|publisher=Joint Typhoon Warning Center}}</ref> which resulted in the JMA briefly upgrading Bebinca to a severe tropical storm, though in post-analysis it was downgraded to a tropical storm. The JTWC analysed a few hours later that the system had reached peak intensity with 1-minute winds of {{convert|110|km/h|mph|abbr=on}}. After Bebinca made landfall, the system rapidly weakened and both agencies issued their final warnings on August&nbsp;17, with the system fully dissipating on the same day. On August&nbsp;9, a tropical depression formed within the ]. The system remained weak and remained stationary for a few days until the JTWC began tracking the system, giving it the designation ''20W'' on August&nbsp;12.<ref>{{cite web|title=Tropical Depression 20W (Twenty) Warning Nr 001|url=http://gwydir.demon.co.uk/advisories/WTPN33-PGTW_201808121500.htm|archive-url=https://archive.today/20240522215334/https://www.webcitation.org/71dffWzIo?url=http://gwydir.demon.co.uk/advisories/WTPN33-PGTW_201808121500.htm|url-status=dead|date=August 12, 2018|archive-date=May 22, 2024|publisher=Joint Typhoon Warning Center}}</ref> On the next day, the JMA upgraded the system to a tropical storm, naming it ''Bebinca''. The JTWC followed suit nine hours later as deep convection flared near its compact center.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 20W (Bebinca) Warning Nr 04|url=http://gwydir.demon.co.uk/advisories/WDPN33-PGTW_201808130900.htm|archive-url=https://archive.today/20240522215413/https://www.webcitation.org/71dfyW93u?url=http://gwydir.demon.co.uk/advisories/WDPN33-PGTW_201808130900.htm|url-status=dead|date=August 13, 2018|archive-date=May 22, 2024|publisher=Joint Typhoon Warning Center}}</ref> Despite consistent convection along with warm sea-surface temperatures, Bebinca remained weak for the next few days due to strong shear.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 20W (Bebinca) Warning Nr 11|url=http://gwydir.demon.co.uk/advisories/WDPN33-PGTW_201808150300.htm|archive-url=https://archive.today/20240524024009/https://www.webcitation.org/71hOVDSQt?url=http://gwydir.demon.co.uk/advisories/WDPN33-PGTW_201808150300.htm|url-status=dead|date=August 15, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> By August&nbsp;16, however, Bebinca began to undergo a phase of rapid intensification as its center was obscured by a central dense overcast,<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 20W (Bebinca) Warning Nr 15 CORRECTED|url=http://gwydir.demon.co.uk/advisories/WDPN33-PGTW_201808160300.htm|archive-url=https://archive.today/20240522215457/https://www.webcitation.org/71i8exOQ1?url=http://gwydir.demon.co.uk/advisories/WDPN33-PGTW_201808160300.htm|url-status=dead|date=August 16, 2018|archive-date=May 22, 2024|publisher=Joint Typhoon Warning Center}}</ref> which resulted in the JMA briefly upgrading Bebinca to a severe tropical storm, though in post-analysis it was downgraded to a tropical storm. The JTWC analysed a few hours later that the system had reached peak intensity with 1-minute winds of {{convert|110|km/h|mph|abbr=on}}. After Bebinca made landfall, the system rapidly weakened and both agencies issued their final warnings on August&nbsp;17, with the system fully dissipating on the same day.


Bebinca killed a total of 6&nbsp;people, and total economic losses in South China were counted to be ¥2.31 billion (US$333 million).<ref name="China Member Report"/> 13 people lost their lives in Vietnam and total damages were counted to be ]786.55 billion (US$33.7 million).<ref name="infonet.vn">{{cite web|url=http://infonet.vn/nghe-an-xin-trung-uong-ho-tro-350-ti-dong-khac-phuc-thiet-hai-bao-so-4-post272385.info|title=Nghệ An xin trung ương hỗ trợ 350 tỉ đồng khắc phục thiệt hại bão số 4|date=22 August 2018|access-date=22 August 2018|archive-date=22 August 2018|archive-url=https://web.archive.org/web/20180822214025/http://infonet.vn/nghe-an-xin-trung-uong-ho-tro-350-ti-dong-khac-phuc-thiet-hai-bao-so-4-post272385.info|url-status=live}}</ref><ref name="Global Catastrophe Recap August 2018"/> Bebinca killed a total of 6&nbsp;people, and total economic losses in South China were counted to be ¥2.31 billion (US$333 million).<ref name="China Member Report"/> 13 people lost their lives in Vietnam and total damages were counted to be ]786.55 billion (US$33.7 million).<ref name="infonet.vn">{{cite web|url=http://infonet.vn/nghe-an-xin-trung-uong-ho-tro-350-ti-dong-khac-phuc-thiet-hai-bao-so-4-post272385.info|title=Nghệ An xin trung ương hỗ trợ 350 tỉ đồng khắc phục thiệt hại bão số 4|date=22 August 2018|access-date=22 August 2018|archive-date=22 August 2018|archive-url=https://web.archive.org/web/20180822214025/http://infonet.vn/nghe-an-xin-trung-uong-ho-tro-350-ti-dong-khac-phuc-thiet-hai-bao-so-4-post272385.info|url-status=live}}</ref><ref name="Global Catastrophe Recap August 2018"/>
Line 515: Line 508:
| Pressure = 994 | Pressure = 994
}} }}
On August 10, a tropical depression formed near the Mariana Islands, assigning the depression as 21W and on the next day at 12:00 UTC, the JMA upgraded it to a tropical storm, assigning it the name ''Leepi''. By August 13, Leepi began to threaten Japan, and on August 14, Leepi intensified into a severe tropical storm, with the JTWC upgrading it to a Category 1 equivalent typhoon. Shortly before 03:00 JST (18:00 UTC) on August 15, Leepi made landfall over ], ] in ]. Leepi was downgraded into a tropical depression and dissipated on August 15, though its remnants were still noted near Russia.<ref>{{cite web|script-title=ja:平成30年 台風第15号に関する情報 第38号|url=https://www.jma.go.jp/jp/kishojoho/000_00_662_20180814181316.html|publisher=Japan Meteorological Agency|access-date=August 17, 2018|archive-url=https://web.archive.org/web/20180817021912/https://www.jma.go.jp/jp/kishojoho/000_00_662_20180814181316.html|archive-date=August 17, 2018|language=ja|date=August 14, 2018}}</ref> On August 10, a tropical depression formed near the Mariana Islands, assigning the depression as 19W and on the next day at 12:00 UTC, the JMA upgraded it to a tropical storm, assigning it the name ''Leepi''. By August 13, Leepi began to threaten Japan, and on August 14, Leepi intensified into a severe tropical storm, with the JTWC upgrading it to a Category 1 equivalent typhoon. Shortly before 03:00 JST (18:00 UTC) on August 15, Leepi made landfall over ], ] in ]. Leepi was downgraded into a tropical depression and dissipated on August 15, though its remnants were still noted near Russia.<ref>{{cite web|script-title=ja:平成30年 台風第15号に関する情報 第38号|url=https://www.jma.go.jp/jp/kishojoho/000_00_662_20180814181316.html|publisher=Japan Meteorological Agency|access-date=August 17, 2018|archive-url=https://web.archive.org/web/20180817021912/https://www.jma.go.jp/jp/kishojoho/000_00_662_20180814181316.html|archive-date=August 17, 2018|language=ja|date=August 14, 2018}}</ref>
{{clear}} {{clear}}


Line 531: Line 524:
{{Main|Hurricane Hector (2018)}} {{Main|Hurricane Hector (2018)}}
<!--wait for Hector BT for JMA sources--> <!--wait for Hector BT for JMA sources-->
On August 13 at 18:00 UTC, both the JMA and the JTWC declared that Tropical Storm Hector has crossed the ] and entered the West Pacific basin from the East Pacific basin.<ref>{{cite web|title=Tropical Storm 10E (Hector) Warning Nr 054|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201808132100.htm|archive-url=https://www.webcitation.org/71f867Iaw?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201808132100.htm|url-status=dead|date=August 13, 2018|archive-date=August 14, 2018|publisher=Joint Typhoon Warning Center}}</ref> At this point, Hector was still located in a favorable environment with only moderate shear, though deep convection was limited as it only persisted just near its center.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 10E (Hector) Warning Nr 54|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808132100.htm|archive-url=https://www.webcitation.org/71f88nyEE?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808132100.htm|url-status=dead|date=August 13, 2018|archive-date=August 14, 2018|publisher=Joint Typhoon Warning Center}}</ref> Due to an ] located to the west of Hector, the storm failed to intensify and began to weaken.<ref>{{cite web|title=Prognostic Reasnong for Tropical Storm 10E (Hector) Warning Nr 55|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808140300.htm|archive-url=https://www.webcitation.org/71f88RcK7?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808140300.htm|url-status=dead|date=August 14, 2018|archive-date=August 14, 2018|publisher=Joint Typhoon Warning Center}}</ref> The JTWC downgraded Hector to a tropical depression after the system rapidly entered an area of high vertical wind shear.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 10E (Hector) Warning Nr 58|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808140300.htm|archive-url=https://www.webcitation.org/71f88RcK7?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808140300.htm|url-status=dead|date=August 14, 2018|archive-date=August 14, 2018|publisher=Joint Typhoon Warning Center}}</ref> By the early hours of August 15, both agencies issued their final warnings on Hector, mentioning that Hector's low-level circulation had become elongated and that the storm already transitioned into a subtropical cyclone.<ref>{{cite web|title=Tropical Depression 10E (Hector) Warning Nr 059|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201808150300.htm|archive-url=https://www.webcitation.org/71i8pQewR?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201808150300.htm|url-status=dead|date=August 15, 2018|archive-date=August 16, 2018|publisher=Joint Typhoon Warning Center}}</ref> The JMA, however, continued to monitor the system until 00:00 UTC on August 17. On August 13 at 18:00 UTC, both the JMA and the JTWC declared that Tropical Storm Hector has crossed the ] and entered the West Pacific basin from the East Pacific basin.<ref>{{cite web|title=Tropical Storm 10E (Hector) Warning Nr 054|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201808132100.htm|archive-url=https://archive.today/20240524023803/https://www.webcitation.org/71f867Iaw?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201808132100.htm|url-status=dead|date=August 13, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> At this point, Hector was still located in a favorable environment with only moderate shear, though deep convection was limited as it only persisted just near its center.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 10E (Hector) Warning Nr 54|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808132100.htm|archive-url=https://archive.today/20240524023846/https://www.webcitation.org/71f88nyEE?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808132100.htm|url-status=dead|date=August 13, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> Due to an ] located to the west of Hector, the storm failed to intensify and began to weaken.<ref>{{cite web|title=Prognostic Reasnong for Tropical Storm 10E (Hector) Warning Nr 55|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808140300.htm|archive-url=https://archive.today/20240524023925/https://www.webcitation.org/71f88RcK7?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808140300.htm|url-status=dead|date=August 14, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> The JTWC downgraded Hector to a tropical depression after the system rapidly entered an area of high vertical wind shear.<ref>{{cite web|title=Prognostic Reasoning for Tropical Storm 10E (Hector) Warning Nr 58|url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808140300.htm|archive-url=https://archive.today/20240524023925/https://www.webcitation.org/71f88RcK7?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201808140300.htm|url-status=dead|date=August 14, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> By the early hours of August 15, both agencies issued their final warnings on Hector, mentioning that Hector's low-level circulation had become elongated and that the storm already transitioned into a subtropical cyclone.<ref>{{cite web|title=Tropical Depression 10E (Hector) Warning Nr 059|url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201808150300.htm|archive-url=https://archive.today/20240524024046/https://www.webcitation.org/71i8pQewR?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201808150300.htm|url-status=dead|date=August 15, 2018|archive-date=May 24, 2024|publisher=Joint Typhoon Warning Center}}</ref> The JMA, however, continued to monitor the system until 00:00 UTC on August 17.
{{clear}} {{clear}}


Line 545: Line 538:
| Pressure = 985 | Pressure = 985
}} }}
{{main|Tropical Storm Rumbia (2018)}} {{main|Tropical Storm Rumbia}}
On August 15, a tropical depression in the ] intensified into a tropical storm, being given the name ''Rumbia'' by the JMA. Shortly after reaching peak intensity over the ] on August 16, Rumbia made landfall over ], ], ] at around 04:05 CST on August 17 (20:05 UTC), becoming the third tropical storm to hit ] in 2018.<ref>{{cite web|script-title=zh:"温比亚"已登陆上海浦东 苏浙沪皖鄂豫迎强风雨|url=http://www.nmc.cn/publish/weatherperday/index.htm|publisher=National Meteorological Center of CMA|access-date=August 17, 2018|archive-url=https://web.archive.org/web/20180817020615/http://www.nmc.cn/publish/weatherperday/index.htm|archive-date=August 17, 2018|language=zh|date=August 16, 2018}}</ref> On August 15, a tropical depression in the ] intensified into a tropical storm, being given the name ''Rumbia'' by the JMA. Shortly after reaching peak intensity over the ] on August 16, Rumbia made landfall over ], ], ] at around 04:05 CST on August 17 (20:05 UTC), becoming the third tropical storm to hit ] in 2018.<ref>{{cite web|script-title=zh:"温比亚"已登陆上海浦东 苏浙沪皖鄂豫迎强风雨|url=http://www.nmc.cn/publish/weatherperday/index.htm|publisher=National Meteorological Center of CMA|access-date=August 17, 2018|archive-url=https://web.archive.org/web/20180817020615/http://www.nmc.cn/publish/weatherperday/index.htm|archive-date=August 17, 2018|language=zh|date=August 16, 2018}}</ref>


Line 565: Line 558:
A ] in the ] organized into a tropical depression late on August&nbsp;15. The ] followed suit at 00:00&nbsp;] at August&nbsp;16 and was designated as ''22W''. Later on that day, the ] upgraded 22W to tropical storm and it was given the international name ''Soulik''. On August&nbsp;17, JMA upgraded Soulik to a typhoon, marking the sixth typhoon of the season. Then Soulik rapidly intensified onto a severe typhoon, and on the next day, Soulik reached its peak intensity, with winds of {{convert|165|km/h|mph|abbr=on}}, and remained that intensity for several days. It also began to display some annular characteristics. After passing the Ryukyu Islands early on 22&nbsp;August, the storm gradually weakened due to low sea-surface temperatures. On August&nbsp;23, Soulik made landfall over ], ] of ] at around 23:00&nbsp;] (14:00&nbsp;UTC).<ref>{{cite web |script-title=ko:태풍 현황과 전망 |url=http://www.weather.go.kr/weather/warning/report.jsp?prevStn=108&prevKind=&stn=108&kind=&reportId=ann%3A201808232310%3A34&x=22&y=9 |publisher=Korea Meteorological Administration |access-date=August 23, 2018 |archive-url=https://web.archive.org/web/20180823170031/http://www.weather.go.kr/weather/warning/report.jsp?prevStn=108&prevKind=&stn=108&kind=&reportId=ann%3A201808232310%3A34&x=22&y=9 |archive-date=August 23, 2018 |language=ko |date=August 23, 2018}}</ref> A ] in the ] organized into a tropical depression late on August&nbsp;15. The ] followed suit at 00:00&nbsp;] at August&nbsp;16 and was designated as ''22W''. Later on that day, the ] upgraded 22W to tropical storm and it was given the international name ''Soulik''. On August&nbsp;17, JMA upgraded Soulik to a typhoon, marking the sixth typhoon of the season. Then Soulik rapidly intensified onto a severe typhoon, and on the next day, Soulik reached its peak intensity, with winds of {{convert|165|km/h|mph|abbr=on}}, and remained that intensity for several days. It also began to display some annular characteristics. After passing the Ryukyu Islands early on 22&nbsp;August, the storm gradually weakened due to low sea-surface temperatures. On August&nbsp;23, Soulik made landfall over ], ] of ] at around 23:00&nbsp;] (14:00&nbsp;UTC).<ref>{{cite web |script-title=ko:태풍 현황과 전망 |url=http://www.weather.go.kr/weather/warning/report.jsp?prevStn=108&prevKind=&stn=108&kind=&reportId=ann%3A201808232310%3A34&x=22&y=9 |publisher=Korea Meteorological Administration |access-date=August 23, 2018 |archive-url=https://web.archive.org/web/20180823170031/http://www.weather.go.kr/weather/warning/report.jsp?prevStn=108&prevKind=&stn=108&kind=&reportId=ann%3A201808232310%3A34&x=22&y=9 |archive-date=August 23, 2018 |language=ko |date=August 23, 2018}}</ref>


Total damage in South Korea were at ]50.7 billion (US$45 million).<ref name="Wikitree">{{cite news|url=https://www.wikitree.co.kr/main/news_view.php?id=370835|script-title=ko:태풍 솔릭·호우 피해지역 복구비 1338억 확정|language=ko|publisher=Wikitree|date=September 20, 2018|access-date=October 15, 2018}}</ref> Economic loss in Northeast China were counted to be CN¥550 million (US$79.9 million).<ref name="台风苏力致吉林黑龙江损失5.5亿元">{{cite news|publisher=中华人民共和国减灾部|date=August 27, 2018|access-date=August 27, 2018|title=台风"苏力"致吉林黑龙江损失5.5亿元|url=http://www.jianzai.gov.cn//DRpublish/ywcp/0000000000030671.html|archive-url=https://web.archive.org/web/20180922052610/http://www.jianzai.gov.cn/DRpublish/ywcp/0000000000030671.html|archive-date=September 22, 2018|url-status=dead}}</ref> Flooding in North Korea triggered by Soulik killed 86 people.<ref name="SoulikinNK">{{cite news|author=Hamish Macdonald|url=https://www.nknews.org/2018/09/dozens-dead-tens-of-thousands-displaced-by-flooding-in-north-korea-un/|title=Dozens dead, tens of thousands displaced by flooding in North Korea: UN|publisher=NK News|date=September 3, 2018|access-date=October 3, 2018|archive-date=October 21, 2018|archive-url=https://web.archive.org/web/20181021224406/https://www.nknews.org/2018/09/dozens-dead-tens-of-thousands-displaced-by-flooding-in-north-korea-un/|url-status=live}}</ref> Total damage in South Korea were at ]50.7 billion (US$45 million).{{citation needed|date=November 2024}} Economic loss in Northeast China were counted to be CN¥550 million (US$79.9 million).<ref name="台风苏力致吉林黑龙江损失5.5亿元">{{cite news|publisher=中华人民共和国减灾部|date=August 27, 2018|access-date=August 27, 2018|title=台风"苏力"致吉林黑龙江损失5.5亿元|url=http://www.jianzai.gov.cn//DRpublish/ywcp/0000000000030671.html|archive-url=https://web.archive.org/web/20180922052610/http://www.jianzai.gov.cn/DRpublish/ywcp/0000000000030671.html|archive-date=September 22, 2018|url-status=dead}}</ref> Flooding in North Korea triggered by Soulik killed 86 people.<ref name="SoulikinNK">{{cite news|author=Hamish Macdonald|url=https://www.nknews.org/2018/09/dozens-dead-tens-of-thousands-displaced-by-flooding-in-north-korea-un/|title=Dozens dead, tens of thousands displaced by flooding in North Korea: UN|publisher=NK News|date=September 3, 2018|access-date=October 3, 2018|archive-date=October 21, 2018|archive-url=https://web.archive.org/web/20181021224406/https://www.nknews.org/2018/09/dozens-dead-tens-of-thousands-displaced-by-flooding-in-north-korea-un/|url-status=live}}</ref>
{{Clear}} {{Clear}}


Line 598: Line 591:
| Pressure = 996 | Pressure = 996
}} }}
A tropical depression formed at the South China Sea near ].<ref name="JMA 201808">{{cite report|title=2018年 8月|url=http://www.data.jma.go.jp/fcd/yoho/data/hibiten/2018/201808.pdf|lang=ja|publisher=]|access-date=April 10, 2019}}</ref> Despite entering an area of high ], the system was in a favorable environment, so the ] and the ] followed suit, with the JTWC naming it 24W, and the PAGASA named it Luis. 24W then made landfall over ], ] shortly after 08:00 CST (00:00 ]) on August 25, and degenerated into a low-pressure area on next day.<ref>{{cite web |title=WWJP25 RJTD 250000 |url=http://tgftp.nws.noaa.gov/data/raw/ww/wwjp25.rjtd..txt |publisher=Japan Meteorological Agency |access-date=August 27, 2018 |archive-url=https://www.webcitation.org/71w5g38Bu?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201808250000.htm |archive-date=2018-08-25 |date=August 25, 2018 |url-status=live }}</ref><ref>{{cite web |title=WWJP25 RJTD 261200 |url=http://tgftp.nws.noaa.gov/data/raw/ww/wwjp25.rjtd..txt |publisher=Japan Meteorological Agency |access-date=August 27, 2018 |archive-url=https://www.webcitation.org/71xjX4lqf?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201808261200.htm |archive-date=2018-08-26 |date=August 26, 2018 |url-status=live }}</ref> The JMA would continue monitoring the system until the next day.<ref name="JMA 201808"/> A tropical depression formed at the South China Sea near ].<ref name="JMA 201808">{{cite report|title=2018年 8月|url=http://www.data.jma.go.jp/fcd/yoho/data/hibiten/2018/201808.pdf|lang=ja|publisher=]|access-date=April 10, 2019}}</ref> Despite entering an area of high ], the system was in a favorable environment, so the ] and the ] followed suit, with the JTWC naming it 24W, and the PAGASA named it Luis. 24W then made landfall over ], ] shortly after 08:00 CST (00:00 ]) on August 25, and degenerated into a low-pressure area on next day.<ref>{{cite web |title=WWJP25 RJTD 250000 |url=http://tgftp.nws.noaa.gov/data/raw/ww/wwjp25.rjtd..txt |publisher=Japan Meteorological Agency |access-date=August 27, 2018 |archive-url=https://archive.today/20240522193011/https://www.webcitation.org/71w5g38Bu?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201808250000.htm |archive-date=2024-05-22 |date=August 25, 2018 |url-status=live }}</ref><ref>{{cite web |title=WWJP25 RJTD 261200 |url=http://tgftp.nws.noaa.gov/data/raw/ww/wwjp25.rjtd..txt |publisher=Japan Meteorological Agency |access-date=August 27, 2018 |archive-url=https://archive.today/20240524024448/https://www.webcitation.org/71xjX4lqf?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201808261200.htm |archive-date=2024-05-24 |date=August 26, 2018 |url-status=live }}</ref> The JMA would continue monitoring the system until the next day.<ref name="JMA 201808"/>


Tropical Depression 24W killed 7 people and caused NT$1.022 billion (US$34 million) of damage in ].<ref name="Global Catastrophe Recap August 2018"/> Tropical Depression 24W killed 7 people and caused NT$1.022 billion (US$34 million) of damage in ].<ref name="Global Catastrophe Recap August 2018"/>
Line 609: Line 602:
| Dissipated = September 4 | Dissipated = September 4
| Image = Jebi 2018-08-31 0332Z.jpg | Image = Jebi 2018-08-31 0332Z.jpg
| Track = Jebi 2018 track.png | Track = Jebi 2018 path.png
| 10-min winds = 105 | 10-min winds = 105
| 1-min winds = 155 | 1-min winds = 155
Line 626: Line 619:
| Dissipated = September 17 | Dissipated = September 17
| Image = File:Mangkhut 2018-09-12 0505Z.jpg | Image = File:Mangkhut 2018-09-12 0505Z.jpg
| Track = Mangkhut 2018 track.png | Track = Mangkhut 2018 path.png
| 10-min winds = 110 | 10-min winds = 110
| 1-min winds = 155 | 1-min winds = 155
Line 632: Line 625:
}} }}
{{main|Typhoon Mangkhut}} {{main|Typhoon Mangkhut}}
On September 6, a tropical depression formed near the ].<ref name="JMA BTD">{{cite web|title=bst2018.txt|url=https://www.jma.go.jp/jma/jma-eng/jma-center/rsmc-hp-pub-eg/Besttracks/bst2018.txt|publisher=]|access-date=April 12, 2019|archive-date=April 12, 2019|archive-url=https://web.archive.org/web/20190412150937/https://www.jma.go.jp/jma/jma-eng/jma-center/rsmc-hp-pub-eg/Besttracks/bst2018.txt|url-status=live}}</ref> However, operationally, the Japan Meteorological Agency (JMA) did not initiate advisories on the system until September 7. The ] followed suit at 03:00 ] on September 7, and classified the system as ''26W''. Late on the same day, the system strengthened into a tropical storm, and the JMA named the system ''Mangkhut''. By September 11, Mangkhut became a typhoon, and made landfall on the islands of ], ]. On September 12, at 3 pm ], Mangkhut entered the ] as a ] super typhoon, and accordingly, ] named the storm ''Ompong''. The JTWC noted additional strengthening on September 12, and assessed Mangkhut to have reached its peak intensity at 18:00 ], with maximum one-minute sustained winds of {{convert|285|km/h|mph|abbr=on}}. On September 13, the Philippine Government initiated evacuations for residents in the typhoon's expected path. Late on September 14, Mangkhut made landfall on the Philippines as a Category 5-equivalent super typhoon, with 1-minute sustained winds of {{convert|165|mph|km/h}}.<ref name="Philippines lashed">{{cite web|url=https://www.cnn.com/2018/09/14/asia/super-typhoon-mangkhut-ompong-wxc-intl/index.html|title=Philippines lashed by Typhoon Mangkhut, strongest storm this year|author1=James Griffiths|author2=Steve George|author3=Jo Shelley|publisher=Cable News Network|date=15 September 2018|access-date=22 September 2018|archive-date=15 September 2018|archive-url=https://web.archive.org/web/20180915233513/https://www.cnn.com/2018/09/14/asia/super-typhoon-mangkhut-ompong-wxc-intl/index.html|url-status=live}}</ref> While moving inland, Mangkhut weakened into a strong Category 4-equivalent super typhoon, and soon weakened further into a Category 2 typhoon. A large eye then appeared and the system slowly strengthened into a Category 3 typhoon, as the storm moved over Hong Kong. As Mangkhut made its final landfall, it weakened into a weak Category 1 typhoon and maintained its intensity inland with ], before subsequently weakening further. Late on September 17, Mangkhut dissipated over ], ]. On September 6, a tropical depression formed near the ].<ref name="JMA BTD">{{cite web|title=bst2018.txt|url=https://www.jma.go.jp/jma/jma-eng/jma-center/rsmc-hp-pub-eg/Besttracks/bst2018.txt|publisher=]|access-date=April 12, 2019|archive-date=April 12, 2019|archive-url=https://web.archive.org/web/20190412150937/https://www.jma.go.jp/jma/jma-eng/jma-center/rsmc-hp-pub-eg/Besttracks/bst2018.txt|url-status=live}}</ref> However, operationally, the Japan Meteorological Agency (JMA) did not initiate advisories on the system until September 7. The ] followed suit at 03:00 ] on September 7, and classified the system as ''Tropical Depression 26W''. Late on the same day, the system strengthened into a tropical storm, and the JMA named the system ''Mangkhut''. By September 11, Mangkhut became a typhoon, and made landfall on the islands of ], ]. On September 12, at 3 pm ], Mangkhut entered the ] as a ] super typhoon, and accordingly, ] named the storm ''Ompong''. The JTWC noted additional strengthening on September 12, and assessed Mangkhut to have reached its peak intensity at 18:00 ], with maximum one-minute sustained winds of {{convert|285|km/h|mph|abbr=on}}. On September 13, the Philippine Government initiated evacuations for residents in the typhoon's expected path. Late on September 14, Mangkhut made landfall on the Philippines as a Category 5-equivalent super typhoon, with 1-minute sustained winds of {{convert|165|mph|km/h}}.<ref name="Philippines lashed">{{cite web|url=https://www.cnn.com/2018/09/14/asia/super-typhoon-mangkhut-ompong-wxc-intl/index.html|title=Philippines lashed by Typhoon Mangkhut, strongest storm this year|author1=James Griffiths|author2=Steve George|author3=Jo Shelley|publisher=Cable News Network|date=15 September 2018|access-date=22 September 2018|archive-date=15 September 2018|archive-url=https://web.archive.org/web/20180915233513/https://www.cnn.com/2018/09/14/asia/super-typhoon-mangkhut-ompong-wxc-intl/index.html|url-status=live}}</ref> While moving inland, Mangkhut weakened into a strong Category 4-equivalent super typhoon, and soon weakened further into a Category 2 typhoon. A large eye then appeared and the system slowly strengthened into a Category 3 typhoon, as the storm moved over Hong Kong. As Mangkhut made its final landfall, it weakened into a weak Category 1 typhoon and maintained its intensity inland with ], before subsequently weakening further. Late on September 17, Mangkhut dissipated over ], ].


As of September 23, at least 134 fatalities have been attributed to Mangkhut, including 127 in the Philippines,<ref name="hits 127">{{cite web|url=https://www.perthnow.com.au/news/disaster-and-emergency/typhoon-mangkhut-death-toll-hits-127-ng-s-1893646|title=Typhoon Mangkhut death toll hits 127|author=Girlie Linao|publisher=PerthNow|date=22 September 2018|access-date=8 October 2018|archive-date=14 October 2019|archive-url=https://web.archive.org/web/20191014183838/https://www.perthnow.com.au/news/disaster-and-emergency/typhoon-mangkhut-death-toll-hits-127-ng-s-1893646|url-status=live}}</ref><ref name="rises to 95">{{Cite news|url=https://www.rappler.com/nation/212481-typhoon-ompong-death-toll-september-21-2018|title=At least 95 dead due to Typhoon Ompong|work=Rappler|date=21 September 2018|access-date=21 September 2018|language=en|archive-date=13 May 2019|archive-url=https://web.archive.org/web/20190513020619/https://www.rappler.com/nation/212481-typhoon-ompong-death-toll-september-21-2018|url-status=live}}</ref> 6 in mainland China,<ref>{{cite report|url=http://www.jianzai.gov.cn//DRpublish/jzdt/0000000000031328.html|title=应急管理新机制助力台风"山竹"应对|language=zh-hans|date=September 19, 2018|access-date=September 22, 2018|archive-url=https://web.archive.org/web/20180928022008/http://www.jianzai.gov.cn/DRpublish/jzdt/0000000000031328.html|archive-date=September 28, 2018|url-status=dead}}</ref> and 1 in Taiwan.<ref name="CNN - 09-16-2018">{{cite web |last1=McKenzie |first1=Sheena |title=Typhoon Mangkhut hits mainland China, lashes Hong Kong, dozens dead in Philippines |website=] |date=16 September 2018 |url=https://www.cnn.com/2018/09/16/asia/typhoon-mangkhut-china-hong-kong-intl/index.html |access-date=16 September 2018 |archive-date=18 February 2020 |archive-url=https://web.archive.org/web/20200218014255/https://www.cnn.com/2018/09/16/asia/typhoon-mangkhut-china-hong-kong-intl/index.html |url-status=live }}</ref> As of October 5, the NDRRMC estimated that Mangkhut caused ]33.9 billion (US$627 million) in damages in the Philippines, with assessments continuing.<ref name="OmpongNDRRMC">{{cite web|title=Situational Report No.55 re Preparedness Measures for TY OMPONG (I.N. MANGKHUT)|url=http://ndrrmc.gov.ph/attachments/article/3437/Sitrep_No_55_re_Preparedness_Measures_and_Effects_for_TY_OMPONG_as_of_05OCT2018_0600H.pdf|date=October 5, 2018|publisher=NDRRMC}}</ref> Hong Kong Observatory initiated Hurricane Signal No. 10 around 09:40 HKT (00:40 UTC), the first time since ] of the previous year. As of September 23, at least 134 fatalities have been attributed to Mangkhut, including 127 in the Philippines,<ref name="hits 127">{{cite web|url=https://www.perthnow.com.au/news/disaster-and-emergency/typhoon-mangkhut-death-toll-hits-127-ng-s-1893646|title=Typhoon Mangkhut death toll hits 127|author=Girlie Linao|publisher=PerthNow|date=22 September 2018|access-date=8 October 2018|archive-date=14 October 2019|archive-url=https://web.archive.org/web/20191014183838/https://www.perthnow.com.au/news/disaster-and-emergency/typhoon-mangkhut-death-toll-hits-127-ng-s-1893646|url-status=live}}</ref><ref name="rises to 95">{{Cite news|url=https://www.rappler.com/nation/212481-typhoon-ompong-death-toll-september-21-2018|title=At least 95 dead due to Typhoon Ompong|work=Rappler|date=21 September 2018|access-date=21 September 2018|language=en|archive-date=13 May 2019|archive-url=https://web.archive.org/web/20190513020619/https://www.rappler.com/nation/212481-typhoon-ompong-death-toll-september-21-2018|url-status=live}}</ref> 6 in mainland China,<ref>{{cite report|url=http://www.jianzai.gov.cn//DRpublish/jzdt/0000000000031328.html|title=应急管理新机制助力台风"山竹"应对|language=zh-hans|date=September 19, 2018|access-date=September 22, 2018|archive-url=https://web.archive.org/web/20180928022008/http://www.jianzai.gov.cn/DRpublish/jzdt/0000000000031328.html|archive-date=September 28, 2018|url-status=dead}}</ref> and 1 in Taiwan.<ref name="CNN - 09-16-2018">{{cite web |last1=McKenzie |first1=Sheena |title=Typhoon Mangkhut hits mainland China, lashes Hong Kong, dozens dead in Philippines |website=] |date=16 September 2018 |url=https://www.cnn.com/2018/09/16/asia/typhoon-mangkhut-china-hong-kong-intl/index.html |access-date=16 September 2018 |archive-date=18 February 2020 |archive-url=https://web.archive.org/web/20200218014255/https://www.cnn.com/2018/09/16/asia/typhoon-mangkhut-china-hong-kong-intl/index.html |url-status=live }}</ref> As of October 5, the NDRRMC estimated that Mangkhut caused ]33.9 billion (US$627 million) in damages in the Philippines, with assessments continuing.<ref name="OmpongNDRRMC">{{cite web|title=Situational Report No.55 re Preparedness Measures for TY OMPONG (I.N. MANGKHUT)|url=http://ndrrmc.gov.ph/attachments/article/3437/Sitrep_No_55_re_Preparedness_Measures_and_Effects_for_TY_OMPONG_as_of_05OCT2018_0600H.pdf|date=October 5, 2018|publisher=NDRRMC}}</ref>
{{clear}} {{clear}}


Line 648: Line 641:
| Pressure = 998 | Pressure = 998
}} }}
{{main|Tropical Storm Barijat}} {{main|Tropical Storm Barijat (2018)}}

On September 8, a tropical depression formed near ] in the Philippines. The storm was named Tropical Depression Neneng by PAGASA, with Batanes placed under TCWS #1. By the next day, Neneng exited the PAR and became a tropical storm, with the JMA assigning the name ''Barijat'' to the storm, while TCWS were raised in the absence of the storm. Over the next 2 days, Tropical Storm Barijat moved westward across the South China Sea, reaching its peak intensity with 10-minute maximum sustained wind speeds of 85&nbsp;km/h on the night of September 11.<ref>{{Cite web |url=https://www.weather.gov.hk/informtc/barijat18/report.htm |title=Tropical Storm Barijat(1823) |access-date=2018-11-16 |archive-date=2018-11-16 |archive-url=https://web.archive.org/web/20181116133240/https://www.weather.gov.hk/informtc/barijat18/report.htm |url-status=dead }}</ref> On September 13, Tropical Storm Barijat (Neneng) made landfall on the ], near the area where Tropical Storm Son-tinh (Henry) had made landfall 2 months ago, before making a second landfall on northern Vietnam later on the same day. During the evening of September 13, Barijat became a ], dissipating on the next day. On September 8, a tropical depression formed near ] in the Philippines. The storm was named Tropical Depression Neneng by PAGASA, with Batanes placed under TCWS #1. By the next day, Neneng exited the PAR and became a tropical storm, with the JMA assigning the name ''Barijat'' to the storm, while TCWS were raised in the absence of the storm. Over the next 2 days, Tropical Storm Barijat moved westward across the South China Sea, reaching its peak intensity with 10-minute maximum sustained wind speeds of 85&nbsp;km/h on the night of September 11.<ref>{{Cite web |url=https://www.weather.gov.hk/informtc/barijat18/report.htm |title=Tropical Storm Barijat(1823) |access-date=2018-11-16 |archive-date=2018-11-16 |archive-url=https://web.archive.org/web/20181116133240/https://www.weather.gov.hk/informtc/barijat18/report.htm |url-status=dead }}</ref> On September 13, Tropical Storm Barijat (Neneng) made landfall on the ], near the area where Tropical Storm Son-tinh (Henry) had made landfall 2 months ago, before making a second landfall on northern Vietnam later on the same day. During the evening of September 13, Barijat became a ], dissipating on the next day.


Tropical Storm Barijat made a dozen landslides over Batanes, which increased the risk of major landslides and major flooding in the saturated soil influenced by this storm and later by ]. Damages in China were at ¥50 million (US$7.3 million).<ref name="China Member Report"/> Tropical Storm Barijat made a dozen landslides over Batanes, which increased the risk of major landslides and major flooding in the saturated soil influenced by this storm and later by ]. No deaths were reported throughout its path, however, damages in China were at ¥50 million (US$7.3 million).<ref name="China Member Report"/>
{{clear}} {{clear}}


Line 660: Line 654:
| Dissipated = October 1 | Dissipated = October 1
| Image = Trami 2018-09-25 0050Z.png | Image = Trami 2018-09-25 0050Z.png
| Track = Trami 2018 track.png | Track = Trami 2018 path.png
| 10-min winds = 105 | 10-min winds = 105
| 1-min winds = 140 | 1-min winds = 140
Line 666: Line 660:
}} }}
{{main|Typhoon Trami (2018)}} {{main|Typhoon Trami (2018)}}
On September 19, the ] began to monitor a large tropical disturbance that formed near ] in the ]. The system drifted westwards and strengthened into a tropical depression on September 20 according to the JMA, while the ] issued a ]. Trami managed to find itself in favorable conditions for strengthening and on September 21, it gained tropical storm status and was ] Trami. On September 22, Trami still strengthened and became a Severe Tropical Storm before strengthening to a ] typhoon. On September 23, Trami, yet again in favorable conditions, continued to strengthen and became a Category 3-equivalent typhoon while undergoing an ] at the same time. Early on September 24, Trami strengthened further and attained Category 4 super typhoon status once it finished its eyewall replacement cycle. At 18:00 UTC on September 24, Trami strengthened even further and subsequently became a Category 5 super typhoon. On its route to ], ], Trami slowed down considerably and was almost stationary before moving north-northeastward. During this period of time, another eyewall replacement cycle that eventually failed later on, coupled with decreasing sea surface temperatures, started to slowly weaken Trami, although it still remained an organized storm. On September 30, Trami reached the most organized point of its duration after its peak, but Trami's structure started to deteriorate afterward, and the storm's winds gradually dropped as Trami resumed weakening. The typhoon made ] over ], ] at around 20:00 JST (11:00 UTC) on September 30<ref>{{cite web |script-title=ja:平成30年 台風第24号に関する情報 第101号 |url=https://www.jma.go.jp/jp/kishojoho/000_00_662_20180930110844.html |publisher=Japan Meteorological Agency |access-date=September 30, 2018 |archive-url=https://web.archive.org/web/20180930204605/https://www.jma.go.jp/jp/kishojoho/000_00_662_20180930110844.html |archive-date=September 30, 2018 |language=ja |date=September 30, 2018}}</ref> as a Category 2-equivalent typhoon. The storm's structure deteriorated rapidly after landfall, and the JMA issued their last advisory on Trami on October 1. After Trami impacted ], it completely transitioned into a hurricane-force ] and impacted the Kuril Islands and weakened to a storm-force system. Its extratropical remnants were last tracked in the ], near the ]. On September 19, the ] began to monitor a large tropical disturbance that formed near ] in the ]. The system drifted westwards and strengthened into a tropical depression on September 20 according to the JMA, while the ] issued a ]. Trami managed to find itself in favorable conditions for strengthening and on September 21, it gained tropical storm status and was ] Trami. On September 22, Trami still strengthened and became a Severe Tropical Storm before strengthening to a ] typhoon. On September 23, Trami, yet again in favorable conditions, continued to strengthen and became a Category 3-equivalent typhoon while undergoing an ] at the same time. Early on September 24, Trami strengthened further and attained Category 4 super typhoon status once it finished its eyewall replacement cycle. At 18:00 UTC on September 24, Trami strengthened even further and subsequently became a Category 5 super typhoon. On its route to ], ], Trami slowed down considerably and was almost stationary before moving north-northeastward. During this period of time, another eyewall replacement cycle that eventually failed later on, coupled with decreasing sea surface temperatures, started to slowly weaken Trami, although it still remained an organized storm. On September 30, Trami reached the most organized point of its duration after its peak, but Trami's structure started to deteriorate afterward, and the storm's winds gradually dropped as Trami resumed weakening. The typhoon made ] over ], ] at around 20:00 JST (11:00 UTC) on September 30<ref>{{cite web |script-title=ja:平成30年 台風第24号に関する情報 第101号 |url=https://www.jma.go.jp/jp/kishojoho/000_00_662_20180930110844.html |publisher=Japan Meteorological Agency |access-date=September 30, 2018 |archive-url=https://web.archive.org/web/20180930204605/https://www.jma.go.jp/jp/kishojoho/000_00_662_20180930110844.html |archive-date=September 30, 2018 |language=ja |date=September 30, 2018}}</ref> as a Category 2-equivalent typhoon. The storm's structure deteriorated rapidly after landfall, and the JMA issued their last advisory on Trami on October 1. After Trami impacted ], it completely transitioned into a hurricane-force ] and impacted the Kuril Islands and weakened to a storm-force system. Its extratropical remnants were last tracked in the ], near the ].


Agricultural damage in Japan were at ]61.65 billion (US$542 million).<ref>{{cite news|url=http://www.maff.go.jp/j/saigai/typhoon/20180929.html|script-title=ja:平成30年台風第24号による被害状況|language=ja|publisher=Ministry of Agriculture, Forestry and Fisheries|date=January 9, 2019|access-date=January 16, 2019|archive-date=March 23, 2019|archive-url=https://web.archive.org/web/20190323142219/http://www.maff.go.jp/j/saigai/typhoon/20180929.html|url-status=dead}}</ref> Agricultural damage in Japan were at ]61.65 billion (US$542 million).<ref>{{cite news|url=http://www.maff.go.jp/j/saigai/typhoon/20180929.html|script-title=ja:平成30年台風第24号による被害状況|language=ja|publisher=Ministry of Agriculture, Forestry and Fisheries|date=January 9, 2019|access-date=January 16, 2019|archive-date=March 23, 2019|archive-url=https://web.archive.org/web/20190323142219/http://www.maff.go.jp/j/saigai/typhoon/20180929.html|url-status=dead}}</ref>
Line 682: Line 676:
| Pressure = 1008 | Pressure = 1008
}} }}
On September 25, a tropical depression formed from the remnant energy of ] to the southeast of Japan. The JTWC gave the system the designation ''29W'' on the next day.<ref>{{cite web |title=Prognostic Reasoning for Tropical Depression 29W (Twentynine) Warning Nr 01 |url=http://tgftp.nws.noaa.gov/data/raw/wd/wdpn32.pgtw..txt |publisher=Joint Typhoon Warning Center |access-date=September 28, 2018 |archive-url=https://www.webcitation.org/72j4RW3yV?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201809260900.htm |archive-date=September 26, 2018 |url-status=live |date=September 26, 2018}}</ref> However, Tropical Depression 29W remained a weak system, and developed an exposed low-level circulation center later that day. Afterward, the tropical depression accelerated northward and then north-northeastward, until it was eventually absorbed into a developing ] east of ] on September 27.<ref>{{cite web |title=WWJP25 RJTD 271200 |url=http://tgftp.nws.noaa.gov/data/raw/ww/wwjp25.rjtd..txt |publisher=Japan Meteorological Agency |access-date=September 28, 2018 |archive-url=https://www.webcitation.org/72lCcoFGd?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201809271200.htm |archive-date=September 28, 2018 |url-status=live |date=September 27, 2018}}</ref><ref>{{cite web |title=WWJP25 RJTD 271800 |url=http://tgftp.nws.noaa.gov/data/raw/ww/wwjp25.rjtd..txt |publisher=Japan Meteorological Agency |access-date=September 28, 2018 |archive-url=https://www.webcitation.org/72lCjY2JY?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201809271800.htm |archive-date=September 28, 2018 |url-status=live |date=September 27, 2018}}</ref> On September 25, a tropical depression formed from the remnant energy of ] to the southeast of Japan. The JTWC gave the system the designation ''29W'' on the next day.<ref>{{cite web |title=Prognostic Reasoning for Tropical Depression 29W (Twentynine) Warning Nr 01 |url=http://tgftp.nws.noaa.gov/data/raw/wd/wdpn32.pgtw..txt |publisher=Joint Typhoon Warning Center |access-date=September 28, 2018 |archive-url=https://archive.today/20240524024607/https://www.webcitation.org/72j4RW3yV?url=http://gwydir.demon.co.uk/advisories/WDPN32-PGTW_201809260900.htm |archive-date=May 24, 2024 |url-status=live |date=September 26, 2018}}</ref> However, Tropical Depression 29W remained a weak system, and developed an exposed low-level circulation center later that day. Afterward, the tropical depression accelerated northward and then north-northeastward, until it was eventually absorbed into a developing ] east of ] on September 27.<ref>{{cite web |title=WWJP25 RJTD 271200 |url=http://tgftp.nws.noaa.gov/data/raw/ww/wwjp25.rjtd..txt |publisher=Japan Meteorological Agency |access-date=September 28, 2018 |archive-url=https://archive.today/20240522193614/https://www.webcitation.org/72lCcoFGd?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201809271200.htm |archive-date=May 22, 2024 |url-status=live |date=September 27, 2018}}</ref><ref>{{cite web |title=WWJP25 RJTD 271800 |url=http://tgftp.nws.noaa.gov/data/raw/ww/wwjp25.rjtd..txt |publisher=Japan Meteorological Agency |access-date=September 28, 2018 |archive-url=https://archive.today/20240524024648/https://www.webcitation.org/72lCjY2JY?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201809271800.htm |archive-date=May 24, 2024 |url-status=live |date=September 27, 2018}}</ref>
{{Clear}} {{Clear}}


Line 691: Line 685:
| Dissipated = October 6 | Dissipated = October 6
| Image = Kong-rey 2018-10-02 0440Z.jpg | Image = Kong-rey 2018-10-02 0440Z.jpg
| Track = Kong-rey 2018 track.png | Track = Kong-rey 2018 path.png
| 10-min winds = 115 | 10-min winds = 115
| 1-min winds = 150 | 1-min winds = 150
Line 697: Line 691:
}} }}
{{Main|Typhoon Kong-rey (2018)}} {{Main|Typhoon Kong-rey (2018)}}
In late September, a tropical disturbance formed in the waters near ] in the ]. The ] also gave the storm, Invest 94W, a low chance of development.<ref>{{cite web |title=Prognostic Reasoning for Tropical Disturbance 94W |url=http://gwydir.demon.co.uk/advisories/ABPW10-PGTW_201809250600.htm |archive-url=https://www.webcitation.org/72gw08z2b?url=http://gwydir.demon.co.uk/advisories/ABPW10-PGTW_201809250600.htm |url-status=dead |archive-date=2018-09-25 |ref=173 |date=2018-09-25}}</ref> Over the next couple of days, the system moved westward and organized into a tropical depression on September&nbsp;27, and the ] initiated advisories on the storm, while the ] issued a ]. On September 28, the JTWC designated the system as 30W,<ref>{{cite web |title=熱帶性低氣壓WP302018 #1 |url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201809280300.htm |archive-url=https://www.webcitation.org/72li93bxH?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201809280300.htm |url-status=dead |archive-date=2018-09-28 |ref=174 |date=2018-09-28}}</ref> while the JMA issued a gale warning for the system.<ref>{{cite web |title=日本氣象廳2018年西北太平洋第35號熱帶低氣壓烈風警告 #1 |url=http://gwydir.demon.co.uk/advisories/WTPQ21-RJTD_201809280600.htm |archive-url=https://www.webcitation.org/72li4vVss?url=http://gwydir.demon.co.uk/advisories/WTPQ21-RJTD_201809280600.htm |url-status=dead |archive-date=2018-09-28 |ref=175 |date=2018-09-29}}</ref> As Tropical Depression 30W continued strengthening, the system became a tropical storm and was named ''Kong-rey'' by the JMA. On September 29, the system moved further west, found itself in favorable conditions for strengthening, and became a tropical storm. Later that day, Kong-rey strengthened into a severe tropical storm, and on September 30, the storm attained typhoon status at 03:00 ]. Kong-rey continued strengthening, and at 18:00 UTC on October 1, Kong-rey became a Category 4-equivalent super typhoon. Early on October 2, Kong-rey strengthened into a ] super typhoon. Affected by vertical ], low ] and decreasing sea surface temperatures, the storm gradually weakened to a Category 3 typhoon on October 3 while undergoing an ].<ref>{{cite news|script-title=zh:康芮強度今晚起減弱! 專家:近台時是中颱等級|url=http://news.ltn.com.tw/news/life/breakingnews/2568708|access-date=2018-10-03|date=2018-10-02|location=Taiwan|language=zh|archive-date=2018-10-03|archive-url=https://web.archive.org/web/20181003061759/http://news.ltn.com.tw/news/life/breakingnews/2568708|url-status=live}}</ref> Increased vertical wind shear and lower sea surface temperatures hampered Kong-rey's strength, and Kong-rey was downgraded to a tropical storm on October 4. Early on October 6, Kong-rey made ] in ], ] in ] as a high-end tropical storm,<ref>{{cite news |author1=郭展毓 |script-title=zh:「康芮」登陸南韓慶南 釜山已現強風雨 |url=https://news.tvbs.com.tw/world/1004871 |access-date=2018-10-06 |publisher=TVBS新聞網 |date=2018-10-06 |ref=176 |location=Hong Kong |language=zh}}</ref> and later on the same day, Kong-rey transitioned into an ], while impacting southern ], such as areas near ]. In late September, a tropical disturbance formed in the waters near ] in the ]. The ] also gave the storm, Invest 94W, a low chance of development.<ref>{{cite web |title=Prognostic Reasoning for Tropical Disturbance 94W |url=http://gwydir.demon.co.uk/advisories/ABPW10-PGTW_201809250600.htm |archive-url=https://archive.today/20240524024529/https://www.webcitation.org/72gw08z2b?url=http://gwydir.demon.co.uk/advisories/ABPW10-PGTW_201809250600.htm |url-status=dead |archive-date=2024-05-24 |ref=173 |date=2018-09-25}}</ref> Over the next couple of days, the system moved westward and organized into a tropical depression on September&nbsp;27, and the ] initiated advisories on the storm, while the ] issued a ]. On September 28, the JTWC designated the system as 30W,<ref>{{cite web |title=熱帶性低氣壓WP302018 #1 |url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201809280300.htm |archive-url=https://archive.today/20240524024808/https://www.webcitation.org/72li93bxH?url=http://gwydir.demon.co.uk/advisories/WTPN32-PGTW_201809280300.htm |url-status=dead |archive-date=2024-05-24 |ref=174 |date=2018-09-28}}</ref> while the JMA issued a gale warning for the system.<ref>{{cite web |title=日本氣象廳2018年西北太平洋第35號熱帶低氣壓烈風警告 #1 |url=http://gwydir.demon.co.uk/advisories/WTPQ21-RJTD_201809280600.htm |archive-url=https://archive.today/20240524024729/https://www.webcitation.org/72li4vVss?url=http://gwydir.demon.co.uk/advisories/WTPQ21-RJTD_201809280600.htm |url-status=dead |archive-date=2024-05-24 |ref=175 |date=2018-09-29}}</ref> As Tropical Depression 30W continued strengthening, the system became a tropical storm and was named ''Kong-rey'' by the JMA. On September 29, the system moved further west, found itself in favorable conditions for strengthening, and became a tropical storm. Later that day, Kong-rey strengthened into a severe tropical storm, and on September 30, the storm attained typhoon status at 03:00 ]. Kong-rey continued strengthening, and at 18:00 UTC on October 1, Kong-rey became a Category 4-equivalent super typhoon. Early on October 2, Kong-rey strengthened into a ] super typhoon. Affected by vertical ], low ] and decreasing sea surface temperatures, the storm gradually weakened to a Category 3 typhoon on October 3 while undergoing an ].<ref>{{cite news|script-title=zh:康芮強度今晚起減弱! 專家:近台時是中颱等級|url=http://news.ltn.com.tw/news/life/breakingnews/2568708|access-date=2018-10-03|date=2018-10-02|location=Taiwan|language=zh|archive-date=2018-10-03|archive-url=https://web.archive.org/web/20181003061759/http://news.ltn.com.tw/news/life/breakingnews/2568708|url-status=live}}</ref> Increased vertical wind shear and lower sea surface temperatures hampered Kong-rey's strength, and Kong-rey was downgraded to a tropical storm on October 4. Early on October 6, Kong-rey made ] in ], ] in ] as a high-end tropical storm,<ref>{{cite news |author1=郭展毓 |script-title=zh:「康芮」登陸南韓慶南 釜山已現強風雨 |url=https://news.tvbs.com.tw/world/1004871 |access-date=2018-10-06 |publisher=TVBS新聞網 |date=2018-10-06 |ref=176 |location=Hong Kong |language=zh}}</ref> and later on the same day, Kong-rey transitioned into an ], while impacting southern ], such as areas near ].


As of October 2018, 3 people have been killed by the storm, including 2 people from ].<ref>{{Cite news|url=https://weather.com/news/news/2018-10-06-tropical-storm-kong-rey-south-korea-impacts|title=Tropical Storm Kong-rey Leaves 2 Dead, 1 Missing In South Korea {{!}} The Weather Channel|work=The Weather Channel|access-date=2018-10-09|archive-date=2018-10-09|archive-url=https://web.archive.org/web/20181009172147/https://weather.com/news/news/2018-10-06-tropical-storm-kong-rey-south-korea-impacts|url-status=live}}</ref> Damage nationwide totaled at ]54.9 billion (US$48.5 million).<ref>{{Cite news|url=https://news.joins.com/article/23077620?cloc=rss%7Cnews%7Ctotal_list|script-title=ko:정부, 태풍 콩레이 피해복구비 2360억 지원|publisher=Newsis|date=October 30, 2018|access-date=October 31, 2018|language=ko}}</ref> Although Kong-Rey did not make a direct landfall on ] and ], its outer rainbands affected the two islands. At an area in Shikoku, rain accumulated to 300&nbsp;mm. In ], more than 12,000 families lost power;<ref>{{cite news |script-title=zh:颱風「康妮」周六吹向日本西南部及韓國 長崎縣約1.2萬戶停電 |url=https://www.hk01.com/世界說/243783/颱風-康妮-周六吹向日本西南部及韓國-長崎縣約1-2萬戶停電 |access-date=2018-10-08 |publisher=王海如 |date=2018-10-07 |ref=172 |language=zh |archive-date=2018-11-16 |archive-url=https://web.archive.org/web/20181116110110/https://www.hk01.com/%E4%B8%96%E7%95%8C%E8%AA%AA/243783/%E9%A2%B1%E9%A2%A8-%E5%BA%B7%E5%A6%AE-%E5%91%A8%E5%85%AD%E5%90%B9%E5%90%91%E6%97%A5%E6%9C%AC%E8%A5%BF%E5%8D%97%E9%83%A8%E5%8F%8A%E9%9F%93%E5%9C%8B-%E9%95%B7%E5%B4%8E%E7%B8%A3%E7%B4%841-2%E8%90%AC%E6%88%B6%E5%81%9C%E9%9B%BB |url-status=live }}</ref> in ], a person died because of the rain.<ref name="hk01">{{cite news |script-title=zh:颱風「康妮」吹襲韓國 韓2人死亡1人失蹤 日1人死亡 |url=https://www.hk01.com/即時國際/244019/颱風-康妮-吹襲韓國-韓2人死亡1人失蹤-日1人死亡 |access-date=2018-10-08 |publisher=王燕婷 |date=2018-10-07 |ref=171 |language=zh |archive-date=2018-10-07 |archive-url=https://web.archive.org/web/20181007093206/https://www.hk01.com/%E5%8D%B3%E6%99%82%E5%9C%8B%E9%9A%9B/244019/%E9%A2%B1%E9%A2%A8-%E5%BA%B7%E5%A6%AE-%E5%90%B9%E8%A5%B2%E9%9F%93%E5%9C%8B-%E9%9F%932%E4%BA%BA%E6%AD%BB%E4%BA%A11%E4%BA%BA%E5%A4%B1%E8%B9%A4-%E6%97%A51%E4%BA%BA%E6%AD%BB%E4%BA%A1 |url-status=live }}</ref> Agricultural damage in ] and ] were about ]13.99 billion (US$123 million).<ref>{{cite news|url=https://ryukyushimpo.jp/news/entry-816269.html|script-title=ja:農作物の台風被害拡大 沖縄、24号と25号で20億円|language=ja|publisher=Ryūkyū Shimpō|date=October 10, 2018|access-date=October 31, 2018|archive-date=November 4, 2018|archive-url=https://web.archive.org/web/20181104211207/https://ryukyushimpo.jp/news/entry-816269.html|url-status=dead}}</ref><ref>{{cite news|url=https://this.kiji.is/435825900446811233|script-title=ja:農林水産被害120億円 台風24、25号で県確定|language=ja|publisher=Miyazaki Nichinichi Shinbun|date=November 16, 2018|access-date=November 17, 2018}}</ref> As of October 2018, 3 people have been killed by the storm, including 2 people from ].<ref>{{Cite news|url=https://weather.com/news/news/2018-10-06-tropical-storm-kong-rey-south-korea-impacts|title=Tropical Storm Kong-rey Leaves 2 Dead, 1 Missing In South Korea {{!}} The Weather Channel|work=The Weather Channel|access-date=2018-10-09|archive-date=2018-10-09|archive-url=https://web.archive.org/web/20181009172147/https://weather.com/news/news/2018-10-06-tropical-storm-kong-rey-south-korea-impacts|url-status=live}}</ref> Damage nationwide totaled at ]54.9 billion (US$48.5 million).<ref>{{Cite news|url=https://news.joins.com/article/23077620?cloc=rss%7Cnews%7Ctotal_list|script-title=ko:정부, 태풍 콩레이 피해복구비 2360억 지원|publisher=Newsis|date=October 30, 2018|access-date=October 31, 2018|language=ko}}</ref> Although Kong-Rey did not make a direct landfall on ] and ], its outer rainbands affected the two islands. At an area in Shikoku, rain accumulated to 300&nbsp;mm. In ], more than 12,000 families lost power;<ref>{{cite news |script-title=zh:颱風「康妮」周六吹向日本西南部及韓國 長崎縣約1.2萬戶停電 |url=https://www.hk01.com/世界說/243783/颱風-康妮-周六吹向日本西南部及韓國-長崎縣約1-2萬戶停電 |access-date=2018-10-08 |publisher=王海如 |date=2018-10-07 |ref=172 |language=zh |archive-date=2018-11-16 |archive-url=https://web.archive.org/web/20181116110110/https://www.hk01.com/%E4%B8%96%E7%95%8C%E8%AA%AA/243783/%E9%A2%B1%E9%A2%A8-%E5%BA%B7%E5%A6%AE-%E5%91%A8%E5%85%AD%E5%90%B9%E5%90%91%E6%97%A5%E6%9C%AC%E8%A5%BF%E5%8D%97%E9%83%A8%E5%8F%8A%E9%9F%93%E5%9C%8B-%E9%95%B7%E5%B4%8E%E7%B8%A3%E7%B4%841-2%E8%90%AC%E6%88%B6%E5%81%9C%E9%9B%BB |url-status=live }}</ref> in ], a person died because of the rain.<ref name="hk01">{{cite news |script-title=zh:颱風「康妮」吹襲韓國 韓2人死亡1人失蹤 日1人死亡 |url=https://www.hk01.com/即時國際/244019/颱風-康妮-吹襲韓國-韓2人死亡1人失蹤-日1人死亡 |access-date=2018-10-08 |publisher=王燕婷 |date=2018-10-07 |ref=171 |language=zh |archive-date=2018-10-07 |archive-url=https://web.archive.org/web/20181007093206/https://www.hk01.com/%E5%8D%B3%E6%99%82%E5%9C%8B%E9%9A%9B/244019/%E9%A2%B1%E9%A2%A8-%E5%BA%B7%E5%A6%AE-%E5%90%B9%E8%A5%B2%E9%9F%93%E5%9C%8B-%E9%9F%932%E4%BA%BA%E6%AD%BB%E4%BA%A11%E4%BA%BA%E5%A4%B1%E8%B9%A4-%E6%97%A51%E4%BA%BA%E6%AD%BB%E4%BA%A1 |url-status=live }}</ref> Agricultural damage in ] and ] were about ]13.99 billion (US$123 million).<ref>{{cite news|url=https://ryukyushimpo.jp/news/entry-816269.html|script-title=ja:農作物の台風被害拡大 沖縄、24号と25号で20億円|language=ja|publisher=Ryūkyū Shimpō|date=October 10, 2018|access-date=October 31, 2018|archive-date=November 4, 2018|archive-url=https://web.archive.org/web/20181104211207/https://ryukyushimpo.jp/news/entry-816269.html|url-status=dead}}</ref><ref>{{cite news|url=https://this.kiji.is/435825900446811233|script-title=ja:農林水産被害120億円 台風24、25号で県確定|language=ja|publisher=Miyazaki Nichinichi Shinbun|date=November 16, 2018|access-date=November 17, 2018}}</ref>


Unrelated to Kong-rey, ] was a Category 5 hurricane at the same time Kong-rey intensified to Category 5 super typhoon intensity, marking the first time since 2005 when two tropical cyclones of Category 5 strength existed simultaneously in the Northern Hemisphere.<ref name="two monster">{{cite news|url=https://www.washingtonpost.com/weather/2018/10/02/two-monster-tropical-cyclones-are-raging-pacific-ocean/?noredirect=on|title=Two monster tropical cyclones are raging in the Pacific Ocean|author=Matthew Cappucci|date=October 2, 2018|newspaper=The Washington Post|access-date=October 14, 2018}}</ref> Unrelated to Kong-rey, ] was a Category 5 hurricane at the same time Kong-rey intensified to Category 5 super typhoon intensity, marking the first time since 2005 when two tropical cyclones of Category 5 strength existed simultaneously in the Northern Hemisphere.<ref name="two monster">{{cite news|url=https://www.washingtonpost.com/weather/2018/10/02/two-monster-tropical-cyclones-are-raging-pacific-ocean/?noredirect=on|title=Two monster tropical cyclones are raging in the Pacific Ocean|author=Matthew Cappucci|date=October 2, 2018|newspaper=The Washington Post|access-date=October 14, 2018}}</ref>
Line 710: Line 704:
| Dissipated = November 3 | Dissipated = November 3
| Image = Yutu 2018-10-25 0000Z.jpg | Image = Yutu 2018-10-25 0000Z.jpg
| Track = Yutu 2018 track.png | Track = Yutu 2018 path.png
| 10-min winds = 115 | 10-min winds = 115
| 1-min winds = 150 | 1-min winds = 195
| Pressure = 900 | Pressure = 900
}} }}
Line 740: Line 734:
On November 3, the ] began monitoring a disturbance that had formed in the ].<ref>{{Cite web|url=http://www.prh.noaa.gov/cphc/pages/TWO.php?previous=1811030020&fdays=2|title=Central Pacific Hurricane Center - Honolulu, Hawai'i|last=Service|first=US Department of Commerce, NOAA, National Weather|website=www.prh.noaa.gov|language=EN-US|access-date=2018-11-24|archive-date=2018-11-24|archive-url=https://web.archive.org/web/20181124162234/http://www.prh.noaa.gov/cphc/pages/TWO.php?previous=1811030020&fdays=2|url-status=dead}}</ref> This disturbance soon moved out of the basin and into the West Pacific without further development on November 6.<ref>{{Cite web|url=http://www.prh.noaa.gov/cphc/pages/TWO.php?previous=1811061759&fdays=2|title=Central Pacific Hurricane Center - Honolulu, Hawai'i|last=Service|first=US Department of Commerce, NOAA, National Weather|website=www.prh.noaa.gov|language=EN-US|access-date=2018-11-24|archive-date=2018-11-24|archive-url=https://web.archive.org/web/20181124105814/http://www.prh.noaa.gov/cphc/pages/TWO.php?previous=1811061759&fdays=2|url-status=dead}}</ref> Tracking westward, the system did not organize until late on November 18, when it reached tropical depression status on the ]. The PAGASA named the system Tropical Depression "Samuel" and issued warnings for Mindanao and Visayas. Samuel made landfall on November 20 in the ], crossing the archipelago and weakening slightly. Samuel began to restrengthen over the South China Sea, and was subsequently named "Usagi". Usagi underwent rapid intensification, and became a severe tropical storm on November 21 while moving slowly. By November 22, Usagi (Samuel) intensified into a Category 1 typhoon. On November 24, Usagi weakened back to a severe tropical storm while heading to Vietnam because of the land interaction. On November 3, the ] began monitoring a disturbance that had formed in the ].<ref>{{Cite web|url=http://www.prh.noaa.gov/cphc/pages/TWO.php?previous=1811030020&fdays=2|title=Central Pacific Hurricane Center - Honolulu, Hawai'i|last=Service|first=US Department of Commerce, NOAA, National Weather|website=www.prh.noaa.gov|language=EN-US|access-date=2018-11-24|archive-date=2018-11-24|archive-url=https://web.archive.org/web/20181124162234/http://www.prh.noaa.gov/cphc/pages/TWO.php?previous=1811030020&fdays=2|url-status=dead}}</ref> This disturbance soon moved out of the basin and into the West Pacific without further development on November 6.<ref>{{Cite web|url=http://www.prh.noaa.gov/cphc/pages/TWO.php?previous=1811061759&fdays=2|title=Central Pacific Hurricane Center - Honolulu, Hawai'i|last=Service|first=US Department of Commerce, NOAA, National Weather|website=www.prh.noaa.gov|language=EN-US|access-date=2018-11-24|archive-date=2018-11-24|archive-url=https://web.archive.org/web/20181124105814/http://www.prh.noaa.gov/cphc/pages/TWO.php?previous=1811061759&fdays=2|url-status=dead}}</ref> Tracking westward, the system did not organize until late on November 18, when it reached tropical depression status on the ]. The PAGASA named the system Tropical Depression "Samuel" and issued warnings for Mindanao and Visayas. Samuel made landfall on November 20 in the ], crossing the archipelago and weakening slightly. Samuel began to restrengthen over the South China Sea, and was subsequently named "Usagi". Usagi underwent rapid intensification, and became a severe tropical storm on November 21 while moving slowly. By November 22, Usagi (Samuel) intensified into a Category 1 typhoon. On November 24, Usagi weakened back to a severe tropical storm while heading to Vietnam because of the land interaction.


Usagi caused one death in the Philippines, and the agricultural damage were at ]52.2 million (US$994,000).<ref name="Usagi PHI death">{{cite news|last=Amazona|first=Roel|url=http://www.pna.gov.ph/articles/1054519|title=1 dead, thousands displaced as 'Samuel' cuts through Samar|publisher=Pililppines News Agency|date=November 22, 2018|access-date=November 22, 2018}}</ref><ref>{{cite web|url=http://ndrrmc.gov.ph/attachments/article/3511/SitRep_No_11_re_Preparedness_Measures_and_Effects_of_Tropical_Depression_SAMUEL_as_of_6PM_23_November_2018.pdf|title=Situational Report No.11 for Preparedness Measures and Effects of TD SAMUEL|publisher=NDRRMC|date=November 24, 2018|access-date=November 25, 2018}}</ref> On November 25, Usagi made landfall on ]. The typhoon caused flooding in ] and killed three people.<ref name="Usagi 3 dead">{{Cite news|url=https://baomoi.com/tp-hcm-3-nguoi-chet-do-anh-huong-bao-so-9/c/28744984.epi|title=TP HCM 3 người chết do ảnh hưởng bão số 9|date=November 27, 2018|publisher=Báo Mới|access-date=November 28, 2018}}</ref> Losses in Vietnam were at ]925 billion (US$39.5 million).<ref>{{cite web|title=Tóm tắt các cơn bão trong năm 2018|url=http://www.tuyenquang.gov.vn/n39915_tom-tat-cac-con-bao-trong-nam-2018?AspxAutoDetectCookieSupport=1|language=vi|publisher=Government of Tuyen Quang province|date=January 5, 2019|access-date=January 20, 2019}}{{Dead link|date=August 2020 |bot=InternetArchiveBot |fix-attempted=yes }}</ref> Usagi caused one death in the Philippines, and the agricultural damage were at ]52.2 million (US$994,000).<ref name="Usagi PHI death">{{cite news|last=Amazona|first=Roel|url=http://www.pna.gov.ph/articles/1054519|title=1 dead, thousands displaced as 'Samuel' cuts through Samar|publisher=Pililppines News Agency|date=November 22, 2018|access-date=November 22, 2018}}</ref><ref>{{cite web|url=http://ndrrmc.gov.ph/attachments/article/3511/SitRep_No_11_re_Preparedness_Measures_and_Effects_of_Tropical_Depression_SAMUEL_as_of_6PM_23_November_2018.pdf|title=Situational Report No.11 for Preparedness Measures and Effects of TD SAMUEL|publisher=NDRRMC|date=November 24, 2018|access-date=November 25, 2018}}</ref> On November 25, Usagi made landfall on ]. The typhoon caused flooding in ] and killed three people.<ref name="Usagi 3 dead">{{Cite news|url=https://baomoi.com/tp-hcm-3-nguoi-chet-do-anh-huong-bao-so-9/c/28744984.epi|title=TP HCM 3 người chết do ảnh hưởng bão số 9|date=November 27, 2018|publisher=Báo Mới|access-date=November 28, 2018}}</ref> Losses in Vietnam were at ]925 billion (US$39.5 million).<ref name="Toraji1"/>
{{clear}} {{clear}}


===Tropical Storm Toraji=== ===Tropical Storm Toraji===
{{main|Tropical Storm Toraji (2018)}}
{{Infobox hurricane small {{Infobox hurricane small
| Basin = WPac | Basin = WPac
Line 754: Line 747:
| 1-min winds = 30 | 1-min winds = 30
| Pressure = 1004 | Pressure = 1004
}}{{main|Tropical Storm Toraji (2018)}}
}}
A low pressure system exited the PAR on November 15. Late on November 16, a tropical disturbance formed east of ]. It slowly tracked west-northwest and strengthened into a tropical-depression strength storm early on November 17. Toraji made landfall on November 18 and quickly weakened; the remnants emerged into the ], and the remnants briefly reorganized, regaining tropical-depression strength on November 20. However, as Toraji made a second landfall on the ], it weakened once more and dissipated late on November 21, due to wind shear over the ]. A low pressure system exited the PAR on November 15. Late on November 16, a tropical disturbance formed east of ]. It slowly tracked west-northwest and strengthened into a tropical-depression strength storm early on November 17. Toraji made landfall on November 18 and quickly weakened; the remnants emerged into the ], and the remnants briefly reorganized, regaining tropical-depression strength on November 20. However, as Toraji made a second landfall on the ], it weakened once more and dissipated late on November 21, due to wind shear over the ].


Line 786: Line 779:
}} }}
{{main|Tropical Depression Usman}} {{main|Tropical Depression Usman}}
A tropical depression formed in the ] on Christmas Day, December 25. It entered the PAR later that evening and the PAGASA named the significant tropical depression "Usman". Usman made its first landfall on ], ] on December 28. It passed over ] and other areas in the weekend. Usman did not survive the passage of the Philippines and degenerated into a remnant low. The remnants of 35W were absorbed by an invest on December 30 which would later become ].<ref>{{cite web |title=Tropical Depression 35W (Thirty-five) Warning Nr 023 |url=http://tgftp.nws.noaa.gov/data/raw/wt/wtpn31.pgtw..txt |publisher=Joint Typhoon Warning Center |access-date=1 January 2019 |archive-url=https://www.webcitation.org/756CTgiv8?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201812300300.htm |archive-date=1 January 2019 |date=30 December 2018 |url-status=live |df=dmy-all }}</ref> A tropical depression formed in the ] on Christmas Day, December 25. It entered the PAR later that evening and the PAGASA named the significant tropical depression "Usman". Usman made its first landfall on ], ] on December 28. It passed over ] and other areas in the weekend. Usman did not survive the passage of the Philippines and degenerated into a remnant low. The remnants of 35W were absorbed by an invest on December 30 which would later become ].<ref>{{cite web |title=Tropical Depression 35W (Thirty-five) Warning Nr 023 |url=http://tgftp.nws.noaa.gov/data/raw/wt/wtpn31.pgtw..txt |publisher=Joint Typhoon Warning Center |access-date=1 January 2019 |archive-url=https://archive.today/20240522215655/https://www.webcitation.org/756CTgiv8?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201812300300.htm |archive-date=22 May 2024 |date=30 December 2018 |url-status=live |df=dmy-all }}</ref>


While passing over the Philippines, Usman brought heavy rains that caused several landslides, which killed 156 people, with damages amounting to Php5.41 billion (US$103 million).<ref>{{cite report|url=http://ndrrmc.gov.ph/attachments/article/3540/Update_re_Sitrep_no_26_Preparedness_Measures_and_Effects_of_TD_USMAN_as_of_6AM_Jan_20_2019_with_TABS.pdf|title=Sitrep No.26 re Preparedness Measures and Effects of TD USMAN|publisher=NDRRMC|date=January 20, 2019|access-date=January 20, 2019}}</ref> While passing over the Philippines, Usman brought heavy rains that caused several landslides, which killed 156 people, with damages amounting to Php5.41 billion (US$103 million).<ref>{{cite report|url=http://ndrrmc.gov.ph/attachments/article/3540/Update_re_Sitrep_no_26_Preparedness_Measures_and_Effects_of_TD_USMAN_as_of_6AM_Jan_20_2019_with_TABS.pdf|title=Sitrep No.26 re Preparedness Measures and Effects of TD USMAN|publisher=NDRRMC|date=January 20, 2019|access-date=January 20, 2019}}</ref>
Line 792: Line 785:


===Other systems=== ===Other systems===
On June 4, the JMA began tracking a weak tropical depression that had formed northeast of ].<ref>{{Cite web|url=http://www.wis-jma.go.jp/cms/warning/2018/06/04/marine-weather-warning-for-gmdss-metarea-xi-2018-06-04t060000z/|title=Marine Weather Warning for GMDSS Metarea XI 2018-06-04T06:00:00Z|date=June 4, 2018|website=WIS Portal – GISC Tokyo|publisher=Japan Meteorological Agency|access-date=June 4, 2018}}</ref> However, the system was absorbed by a nearby tropical depression, which would eventually become Severe Tropical Storm Maliksi on the next day.<ref name="90W_TCFA"/> After Gaemi became extratropical, a tropical depression formed south of ] early on June 17, and dissipated over the east coast of ], ] one day later.<ref>{{Cite web|url=http://www.wis-jma.go.jp/cms/warning/2018/06/17/marine-weather-warning-for-gmdss-metarea-xi-2018-06-17t060000z/|title=Marine Weather Warning for GMDSS Metarea XI 2018-06-17T06:00:00Z|date=June 17, 2018|website=WIS Portal – GISC Tokyo|publisher=Japan Meteorological Agency|access-date=June 18, 2018}}</ref><ref>{{Cite web|url=http://www.wis-jma.go.jp/cms/warning/2018/06/18/marine-weather-warning-for-gmdss-metarea-xi-2018-06-18t060000z/|title=Marine Weather Warning for GMDSS Metarea XI 2018-06-18T06:00:00Z|date=June 18, 2018|website=WIS Portal – GISC Tokyo|publisher=Japan Meteorological Agency|access-date=June 18, 2018}}</ref> On July 16, a tropical depression developed over the South China Sea. The system remained weak and moved into Vietnam, before dissipating on the next day. On August 4, the JTWC began to track a ] that had developed just west of the ]; the storm subsequently became extratropical on the next day.<ref>{{Cite web|url=http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp952018.dat|title=bwp952018.dat|date=August 5, 2018|publisher=Joint Typhoon Warning Center|archive-url=https://web.archive.org/web/20180806023828/http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp952018.dat|archive-date=August 6, 2018|access-date=August 6, 2018}}</ref>


* On June 4, the JMA began tracking a weak tropical depression that had formed northeast of ].<ref>{{Cite web|url=http://www.wis-jma.go.jp/cms/warning/2018/06/04/marine-weather-warning-for-gmdss-metarea-xi-2018-06-04t060000z/|title=Marine Weather Warning for GMDSS Metarea XI 2018-06-04T06:00:00Z|date=June 4, 2018|website=WIS Portal – GISC Tokyo|publisher=Japan Meteorological Agency|access-date=June 4, 2018}}</ref> However, the system was absorbed by a nearby tropical depression, which would eventually become Severe Tropical Storm Maliksi on the next day.<ref name="90W_TCFA" />
A tropical depression formed southeast of ] on August 24; two days later, it made landfall over ] and quickly dissipated over ], in East China.<ref>{{cite web |title=WWJP25 RJTD 240600 |url=http://tgftp.nws.noaa.gov/data/raw/ww/wwjp25.rjtd..txt |publisher=Japan Meteorological Agency |access-date=August 26, 2018 |archive-url=https://www.webcitation.org/71ueodlcq?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201808240600.htm |archive-date=2018-08-24 |date=August 24, 2018 |url-status=live }}</ref><ref>{{cite web |title=WWJP25 RJTD 260600 |url=http://tgftp.nws.noaa.gov/data/raw/ww/wwjp25.rjtd..txt |publisher=Japan Meteorological Agency |access-date=August 26, 2018 |archive-url=https://www.webcitation.org/71xc0EjnB?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201808260600.htm |archive-date=2018-08-26 |date=August 26, 2018 |url-status=live }}</ref><ref>{{cite web |title=WWJP25 RJTD 261200 |url=http://tgftp.nws.noaa.gov/data/raw/ww/wwjp25.rjtd..txt |publisher=Japan Meteorological Agency |access-date=August 26, 2018 |archive-url=https://www.webcitation.org/71xjX4lqf?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201808261200.htm |archive-date=2018-08-26 |date=August 26, 2018 |url-status=live }}</ref> The remnants associated with ] entered this basin on September 19,<ref>{{cite web |title=Pacific Surface Analysis 06:00 UTC 19 Sep 2018 |url=https://nomads.ncdc.noaa.gov/ncep-charts/new_charts/201809/20180919/pacw.sfcanal.06.2018091909.gif |publisher=Ocean Prediction Center |access-date=September 28, 2018 |archive-url=https://web.archive.org/web/20180928033345/https://nomads.ncdc.noaa.gov/ncep-charts/new_charts/201809/20180919/pacw.sfcanal.06.2018091909.gif |archive-date=September 28, 2018 |format=GIF |date=September 19, 2018}}</ref><ref>{{cite web |title=Pacific Surface Analysis 12:00 UTC 19 Sep 2018 |url=https://nomads.ncdc.noaa.gov/ncep-charts/new_charts/201809/20180919/pacw.sfcanal.12.2018091914.gif |publisher=Ocean Prediction Center |access-date=September 28, 2018 |archive-url=https://web.archive.org/web/20180928033554/https://nomads.ncdc.noaa.gov/ncep-charts/new_charts/201809/20180919/pacw.sfcanal.12.2018091914.gif |archive-date=September 28, 2018 |format=GIF |date=September 19, 2018}}</ref> and it developed into a tropical depression on September 21, while slowly drifting westward.<ref>{{cite web |title=WWJP25 RJTD 211200 CCA |url=http://tgftp.nws.noaa.gov/data/raw/ww/wwjp25.rjtd..txt |publisher=Japan Meteorological Agency |access-date=September 28, 2018 |archive-url=https://www.webcitation.org/72cZLkrmw?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201809211200.htm |archive-date=September 22, 2018 |url-status=live |date=September 21, 2018}}</ref> Two days later, it degenerated into a remnant low again, as the JMA reported the system's dissipation.<ref>{{cite web |title=Surface Analysis 230000 UTC Sep. 2018 |url=http://www.data.jma.go.jp/fcd/yoho/data/wxchart/quick/201809/ASAS_COLOR_201809230000.pdf |publisher=Japan Meteorological Agency |access-date=September 28, 2018 |archive-url=https://web.archive.org/web/20180928031800/http://www.data.jma.go.jp/fcd/yoho/data/wxchart/quick/201809/ASAS_COLOR_201809230000.pdf |archive-date=September 28, 2018 |date=September 23, 2018}}</ref><ref>{{cite web |title=Surface Analysis 230600 UTC Sep. 2018 |url=http://www.data.jma.go.jp/fcd/yoho/data/wxchart/quick/201809/ASAS_COLOR_201809230600.pdf |publisher=Japan Meteorological Agency |access-date=September 28, 2018 |archive-url=https://web.archive.org/web/20180928031819/http://www.data.jma.go.jp/fcd/yoho/data/wxchart/quick/201809/ASAS_COLOR_201809230600.pdf |archive-date=September 28, 2018 |date=September 23, 2018}}</ref> On September 25, the system's remnant energy developed into Tropical Depression 29W.
*
* After Gaemi became extratropical, a tropical depression formed south of ] early on June 17, and dissipated over the east coast of ], ] one day later.<ref>{{Cite web|url=http://www.wis-jma.go.jp/cms/warning/2018/06/17/marine-weather-warning-for-gmdss-metarea-xi-2018-06-17t060000z/|title=Marine Weather Warning for GMDSS Metarea XI 2018-06-17T06:00:00Z|date=June 17, 2018|website=WIS Portal – GISC Tokyo|publisher=Japan Meteorological Agency|access-date=June 18, 2018}}</ref><ref>{{Cite web|url=http://www.wis-jma.go.jp/cms/warning/2018/06/18/marine-weather-warning-for-gmdss-metarea-xi-2018-06-18t060000z/|title=Marine Weather Warning for GMDSS Metarea XI 2018-06-18T06:00:00Z|date=June 18, 2018|website=WIS Portal – GISC Tokyo|publisher=Japan Meteorological Agency|access-date=June 18, 2018}}</ref>
* On July 16, a tropical depression developed over the South China Sea. The system remained weak and moved into Vietnam, before dissipating on the next day.
* On August 4, the JTWC began to track a ] that had developed just west of the ]; the storm subsequently became extratropical on the next day.<ref>{{Cite web|url=http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp952018.dat|title=bwp952018.dat|date=August 5, 2018|publisher=Joint Typhoon Warning Center|archive-url=https://web.archive.org/web/20180806023828/http://ftp.emc.ncep.noaa.gov/wd20vxt/hwrf-init/decks/bwp952018.dat|archive-date=August 6, 2018|access-date=August 6, 2018}}</ref>


* A tropical depression formed southeast of ] on August 24; two days later, it made landfall over ] and quickly dissipated over ], in East China.<ref>{{cite web |title=WWJP25 RJTD 240600 |url=http://tgftp.nws.noaa.gov/data/raw/ww/wwjp25.rjtd..txt |publisher=Japan Meteorological Agency |access-date=August 26, 2018 |archive-url=https://archive.today/20240522192929/https://www.webcitation.org/71ueodlcq?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201808240600.htm |archive-date=2024-05-22 |date=August 24, 2018 |url-status=live }}</ref><ref>{{cite web |title=WWJP25 RJTD 260600 |url=http://tgftp.nws.noaa.gov/data/raw/ww/wwjp25.rjtd..txt |publisher=Japan Meteorological Agency |access-date=August 26, 2018 |archive-url=https://archive.today/20240522193050/https://www.webcitation.org/71xc0EjnB?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201808260600.htm |archive-date=2024-05-22 |date=August 26, 2018 |url-status=live }}</ref><ref>{{cite web |title=WWJP25 RJTD 261200 |url=http://tgftp.nws.noaa.gov/data/raw/ww/wwjp25.rjtd..txt |publisher=Japan Meteorological Agency |access-date=August 26, 2018 |archive-url=https://archive.today/20240524024448/https://www.webcitation.org/71xjX4lqf?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201808261200.htm |archive-date=2024-05-24 |date=August 26, 2018 |url-status=live }}</ref>
On October 19, the JMA began tracking a tropical depression in the ]. On October 20, the tropical depression made landfall on the ] and weakened into a remnant low, before moving out of the basin.
* The remnants of ] entered the basin on September 19,<ref>{{cite web |title=Pacific Surface Analysis 06:00 UTC 19 Sep 2018 |url=https://nomads.ncdc.noaa.gov/ncep-charts/new_charts/201809/20180919/pacw.sfcanal.06.2018091909.gif |publisher=Ocean Prediction Center |access-date=September 28, 2018 |archive-url=https://web.archive.org/web/20180928033345/https://nomads.ncdc.noaa.gov/ncep-charts/new_charts/201809/20180919/pacw.sfcanal.06.2018091909.gif |archive-date=September 28, 2018 |format=GIF |date=September 19, 2018}}</ref><ref>{{cite web |title=Pacific Surface Analysis 12:00 UTC 19 Sep 2018 |url=https://nomads.ncdc.noaa.gov/ncep-charts/new_charts/201809/20180919/pacw.sfcanal.12.2018091914.gif |publisher=Ocean Prediction Center |access-date=September 28, 2018 |archive-url=https://web.archive.org/web/20180928033554/https://nomads.ncdc.noaa.gov/ncep-charts/new_charts/201809/20180919/pacw.sfcanal.12.2018091914.gif |archive-date=September 28, 2018 |format=GIF |date=September 19, 2018}}</ref> and redeveloped into a tropical depression on September 21, while slowly drifting westward.<ref>{{cite web |title=WWJP25 RJTD 211200 CCA |url=http://tgftp.nws.noaa.gov/data/raw/ww/wwjp25.rjtd..txt |publisher=Japan Meteorological Agency |access-date=September 28, 2018 |archive-url=https://archive.today/20240522193213/https://www.webcitation.org/72cZLkrmw?url=http://gwydir.demon.co.uk/advisories/WWJP25-RJTD_201809211200.htm |archive-date=May 22, 2024 |url-status=live |date=September 21, 2018}}</ref> Two days later, it degenerated into a remnant low again, as the JMA reported the system's dissipation.<ref>{{cite web |title=Surface Analysis 230000 UTC Sep. 2018 |url=http://www.data.jma.go.jp/fcd/yoho/data/wxchart/quick/201809/ASAS_COLOR_201809230000.pdf |publisher=Japan Meteorological Agency |access-date=September 28, 2018 |archive-url=https://web.archive.org/web/20180928031800/http://www.data.jma.go.jp/fcd/yoho/data/wxchart/quick/201809/ASAS_COLOR_201809230000.pdf |archive-date=September 28, 2018 |date=September 23, 2018}}</ref><ref>{{cite web |title=Surface Analysis 230600 UTC Sep. 2018 |url=http://www.data.jma.go.jp/fcd/yoho/data/wxchart/quick/201809/ASAS_COLOR_201809230600.pdf |publisher=Japan Meteorological Agency |access-date=September 28, 2018 |archive-url=https://web.archive.org/web/20180928031819/http://www.data.jma.go.jp/fcd/yoho/data/wxchart/quick/201809/ASAS_COLOR_201809230600.pdf |archive-date=September 28, 2018 |date=September 23, 2018}}</ref> On September 25, the system's remnant energy developed into Tropical Depression 29W.


* On October 19, the JMA began tracking a tropical depression in the ]. On October 20, the tropical depression made landfall on the ] and weakened into a remnant low, before moving out of the basin.
A tropical depression formed over the southern portion of the South China Sea on December 31,<ref>{{cite web |title=WTPQ20 RJTD 310600 RSMC Tropical Cyclone Advisory |url=http://tgftp.nws.noaa.gov/data/raw/wt/wtpq20.rjtd..txt |publisher=Japan Meteorological Agency |access-date=1 January 2019 |archive-url=https://www.webcitation.org/75600KJsX?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201812310600.htm |archive-date=2019-01-01 |date=31 December 2018 |url-status=live }}</ref> with the JTWC designation ''36W''.<ref>{{cite web |title=Tropical Depression 36W (Thirtysix) Warning Nr 001 |url=http://tgftp.nws.noaa.gov/data/raw/wt/wtpn31.pgtw..txt |publisher=Joint Typhoon Warning Center |access-date=1 January 2019 |archive-url=https://www.webcitation.org/7560E3na7?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201812310900.htm |archive-date=1 January 2019 |date=31 December 2018 |url-status=live |df=dmy-all }}</ref> The system intensified into ] on January 1, 2019, becoming the first named storm of the ].<ref>{{cite web |title=WTPQ20 RJTD 010600 RSMC Tropical Cyclone Advisory |url=http://tgftp.nws.noaa.gov/data/raw/wt/wtpq20.rjtd..txt |publisher=Japan Meteorological Agency |access-date=1 January 2019 |archive-url=https://www.webcitation.org/7560995uj?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201901010600.htm |archive-date=2019-01-01 |date=1 January 2019 |url-status=live }}</ref>

* A tropical depression formed over the southern portion of the South China Sea on December 31,<ref>{{cite web |title=WTPQ20 RJTD 310600 RSMC Tropical Cyclone Advisory |url=http://tgftp.nws.noaa.gov/data/raw/wt/wtpq20.rjtd..txt |publisher=Japan Meteorological Agency |access-date=1 January 2019 |archive-url=https://archive.today/20240523002924/https://www.webcitation.org/75600KJsX?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201812310600.htm |archive-date=2024-05-23 |date=31 December 2018 |url-status=live }}</ref> with the JTWC designation ''36W''.<ref>{{cite web |title=Tropical Depression 36W (Thirtysix) Warning Nr 001 |url=http://tgftp.nws.noaa.gov/data/raw/wt/wtpn31.pgtw..txt |publisher=Joint Typhoon Warning Center |access-date=1 January 2019 |archive-url=https://archive.today/20240524024848/https://www.webcitation.org/7560E3na7?url=http://gwydir.demon.co.uk/advisories/WTPN31-PGTW_201812310900.htm |archive-date=24 May 2024 |date=31 December 2018 |url-status=live |df=dmy-all }}</ref> The system intensified into ] on January 1, 2019, becoming the first named storm of the ].<ref>{{cite web |title=WTPQ20 RJTD 010600 RSMC Tropical Cyclone Advisory |url=http://tgftp.nws.noaa.gov/data/raw/wt/wtpq20.rjtd..txt |publisher=Japan Meteorological Agency |access-date=1 January 2019 |archive-url=https://archive.today/20240523003005/https://www.webcitation.org/7560995uj?url=http://gwydir.demon.co.uk/advisories/WTPQ20-RJTD_201901010600.htm |archive-date=2024-05-23 |date=1 January 2019 |url-status=live }}</ref>
{{clear}} {{clear}}


Line 812: Line 811:
{| class="wikitable" {| class="wikitable"
|- |-
| ] || ]|| ] || ]|| ]|| Gaemi|| ]|| ]|| ]|| ]|| Wukong|| ]|| ] ||] | ] || ] || ] || ] || ] || Gaemi || ] || ] || ] || ] || Wukong || ] || ] || ]
|- |-
| Leepi || ]|| ]|| ]|| ]|| ]|| ]|| ]|| ]|| ]|| ]|| ]|| Man-yi | Leepi || ] || ] || ] || ] || ]|| ] || ]|| ] || ] || ] || ] || Man-yi || ]
|]
|} |}


{| width="90%"
If a tropical cyclone enters the Western Pacific basin from the ] (west of 180°E), it will retain the name assigned to it by the ] (NHC) and ] (CPHC). The following storms were named in this manner.
|
*]
* Additionally, ] entered the Western Pacific basin from the Central Pacific basin after crossing the International Date Line (180°E) as a tropical cyclone. As the system crossed between basins intact, it retained the name assigned to it by the ].
|}


====Retirement==== ====Retirement====
After the season, the Typhoon Committee announced that the names '']'', '']'', and '']'' were removed from the naming lists due to the damages and deaths it caused in their respective onslaughts, and they will never be used again for another typhoon name.<ref>{{Cite web|url=http://www.cma.gov.cn/en2014/news/News/201902/t20190228_515957.html|title=CMA|website=www.cma.gov.cn|access-date=2019-03-01}}</ref><ref>{{Cite web|date=2020-06-10|title=WMO 52nd Typhoon Committee|url=http://www.typhooncommittee.org/52nd/docs/final/2nd%20VCTC52Report_FINAL.pdf|website=]}}</ref> In 2020, they will be replaced with ''Pulasan'', ''Krathon'', and ''Yinxing'', respectively. After the season, the Typhoon Committee announced that the names '']'', '']'', and '']'' were removed from the naming lists due to the damages and deaths it caused in their respective onslaughts, and they will never be used again for another typhoon name.<ref>{{Cite web|url=http://www.cma.gov.cn/en2014/news/News/201902/t20190228_515957.html|title=CMA|website=www.cma.gov.cn|access-date=2019-03-01}}</ref><ref>{{Cite web|date=2020-06-10|title=WMO 52nd Typhoon Committee|url=http://www.typhooncommittee.org/52nd/docs/final/2nd%20VCTC52Report_FINAL.pdf|website=]}}</ref> In 2020, they were replaced with ''Pulasan'', ''Krathon'', and ''Yinxing'', respectively.


===Philippines=== ===Philippines===
Line 831: Line 831:
| ]|| ]|| ] || ] || Ester | ]|| ]|| ] || ] || Ester
|- |-
| ]|| ]|| ]|| ]|| ] | ]|| ]|| ]|| ]|| ]
|- |-
| ] || Luis || ]|| ]|| ] | ] || Luis || ]|| ]|| ]
Line 845: Line 845:
| {{tcname unused|Felino}} || {{tcname unused|Gunding}} || {{tcname unused|Harriet}} || {{tcname unused|Indang}} || {{tcname unused|Jessa}} | {{tcname unused|Felino}} || {{tcname unused|Gunding}} || {{tcname unused|Harriet}} || {{tcname unused|Indang}} || {{tcname unused|Jessa}}
|} |}
During the season PAGASA used its own naming scheme for the 21 tropical cyclones, that either developed within or moved into their self-defined area of responsibility. The names were taken from a list of names, that had been last used during ] and are scheduled to be used again during ]. The names Gardo, Josie, Maymay, Rosita, Samuel and Usman were used for the first (and only, in the cases of Rosita and Usman) time during the year after the names Glenda, Jose, Mario, Ruby, and Seniang were retired, as both the names Ruby and Rosita were used only for the first times due its damages in the Philippines. Although Tropical Depression Josie caused a substantial amount of damage, the name ''Josie'' was not retired following the season. During the season PAGASA used its own naming scheme for the 21 tropical cyclones, that either developed within or moved into their self-defined area of responsibility. This is the same list used from the ] season, except for the names ''Gardo'', ''Josie'', ''Maymay'', ''Rosita'', and ''Samuel'', which replaced ''Glenda'', ''Jose'', ''Mario'', ''Ruby'', and ''Seniang''. All five names, as well as ''Usman'', were used for the first time (and only, in the cases of ''Rosita'' and ''Usman'').


====Retirement==== ====Retirement====
After the season, the names '']'', '']'' and '']'' were retired, as they caused ₱1&nbsp;billion in damages. Rosita and Usman were only used for the first and last time. They were replaced with ''Obet'', ''Rosal'' and ''Umberto'' for the ].<ref>{{Cite web|title=Philippine Tropical Cyclone Names|url=http://bagong.pagasa.dost.gov.ph/learning-tools/philippine-tropical-cyclone-names|access-date=November 11, 2020|website=bagong.pagasa.dost.gov.ph}}</ref> After the season, the names '']'', '']'' and '']'' were retired, as they caused at least ₱1 billion in damages. They were replaced with ''Obet'', ''Rosal'' and ''Umberto'' for the ].<ref>{{Cite web|title=Philippine Tropical Cyclone Names|url=http://bagong.pagasa.dost.gov.ph/learning-tools/philippine-tropical-cyclone-names|access-date=November 11, 2020|website=bagong.pagasa.dost.gov.ph}}</ref>
{{clear}} {{clear}}


Line 859: Line 859:
| ] || {{Sort|180208|February 8&nbsp;– 16}} || bgcolor=#{{storm colour|TS}}|{{Sort|1|Tropical storm}} || bgcolor=#{{storm colour|TS}}|{{Sort|065|{{convert|65|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|TS}}|{{Sort|1000|{{convert|1000|hPa|inHg|abbr=on}}}} || ], Philippines || {{ntsp|3190000||$}} || {{nts|15}} || <ref name="Sanba2"/> | ] || {{Sort|180208|February 8&nbsp;– 16}} || bgcolor=#{{storm colour|TS}}|{{Sort|1|Tropical storm}} || bgcolor=#{{storm colour|TS}}|{{Sort|065|{{convert|65|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|TS}}|{{Sort|1000|{{convert|1000|hPa|inHg|abbr=on}}}} || ], Philippines || {{ntsp|3190000||$}} || {{nts|15}} || <ref name="Sanba2"/>
|- |-
| Jelawat (Caloy) || {{Sort|180324|March 24&nbsp;– April 1}} || bgcolor=#{{storm colour|VITY}}|{{Sort|3|Violent typhoon}} || bgcolor=#{{storm colour|VITY}}|{{Sort|195|{{convert|195|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|VITY}}|{{Sort|915|{{convert|915|hPa|inHg|abbr=on}}}} || Caroline Islands || None || {{ntsh|0}} None || | ] || {{Sort|180324|March 24&nbsp;– April 1}} || bgcolor=#{{storm colour|VITY}}|{{Sort|3|Violent typhoon}} || bgcolor=#{{storm colour|VITY}}|{{Sort|195|{{convert|195|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|VITY}}|{{Sort|915|{{convert|915|hPa|inHg|abbr=on}}}} || Caroline Islands, Mariana Islands || Unknown || {{nts|2}} ||
|- |-
| 04W || {{Sort|180510|May 10&nbsp;– 15}} || bgcolor=#{{storm colour|TD}}|{{Sort|0|Tropical depression}} || bgcolor=#{{storm colour|TD}}|{{Sort|045|Not specified}} || bgcolor=#{{storm colour|TD}}|{{Sort|1008|{{convert|1008|hPa|inHg|abbr=on}}}} || None || None || {{ntsh|0}} None || | 04W || {{Sort|180510|May 10&nbsp;– 15}} || bgcolor=#{{storm colour|TD}}|{{Sort|0|Tropical depression}} || bgcolor=#{{storm colour|TD}}|{{Sort|045|Not specified}} || bgcolor=#{{storm colour|TD}}|{{Sort|1008|{{convert|1008|hPa|inHg|abbr=on}}}} || None || None || {{ntsh|0}} None ||
Line 883: Line 883:
| TD || {{Sort|180716|July 16&nbsp;– 17}} || bgcolor=#{{storm colour|TD}}|{{Sort|0|Tropical depression}} || bgcolor=#{{storm colour|TD}}|{{Sort|045|Not specified}} || bgcolor=#{{storm colour|TD}}|{{Sort|0998|{{convert|998|hPa|inHg|abbr=on}}}} || South China, Vietnam, Laos || {{ntsp|14900000||$}} || {{ntsh|0}} None ||<ref>{{cite news|publisher=中华人民共和国减灾部|date=July 27, 2018|access-date=July 27, 2018|title=热带低压致广西海南云南损失1亿元|url=http://www.jianzai.gov.cn//DRpublish/jzdt/0000000000029987.html|archive-url=https://web.archive.org/web/20180729094917/http://www.jianzai.gov.cn/DRpublish/jzdt/0000000000029987.html|archive-date=July 29, 2018|url-status=dead}}</ref> | TD || {{Sort|180716|July 16&nbsp;– 17}} || bgcolor=#{{storm colour|TD}}|{{Sort|0|Tropical depression}} || bgcolor=#{{storm colour|TD}}|{{Sort|045|Not specified}} || bgcolor=#{{storm colour|TD}}|{{Sort|0998|{{convert|998|hPa|inHg|abbr=on}}}} || South China, Vietnam, Laos || {{ntsp|14900000||$}} || {{ntsh|0}} None ||<ref>{{cite news|publisher=中华人民共和国减灾部|date=July 27, 2018|access-date=July 27, 2018|title=热带低压致广西海南云南损失1亿元|url=http://www.jianzai.gov.cn//DRpublish/jzdt/0000000000029987.html|archive-url=https://web.archive.org/web/20180729094917/http://www.jianzai.gov.cn/DRpublish/jzdt/0000000000029987.html|archive-date=July 29, 2018|url-status=dead}}</ref>
|- |-
| ] || {{Sort|180717|July 17&nbsp;– 24}} || bgcolor=#{{storm colour|STS}}|{{Sort|2|Severe tropical storm}} || bgcolor=#{{storm colour|STS}}|{{Sort|095|{{convert|95|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|STS}}|{{Sort|0985|{{convert|985|hPa|inHg|abbr=on}}}} || Ryukyu Islands, China, Russian Far East || {{ntsp|246000000||$}} || {{nts|1}} ||<ref name="China Member Report"/> | ] || {{Sort|180717|July 17&nbsp;– 24}} || bgcolor=#{{storm colour|STS}}|{{Sort|2|Severe tropical storm}} || bgcolor=#{{storm colour|STS}}|{{Sort|095|{{convert|95|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|STS}}|{{Sort|0985|{{convert|985|hPa|inHg|abbr=on}}}} || Ryukyu Islands, China, Russian Far East || {{ntsp|246000000||$}} || {{nts|1}} ||<ref name="China Member Report"/>
|- |-
| ] || {{Sort|180720|July 20&nbsp;– 23}} || bgcolor=#{{storm colour|TD}}|{{Sort|0|Tropical depression}} || bgcolor=#{{storm colour|TD}}|{{Sort|055|{{convert|55|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|TD}}|{{Sort|0996|{{convert|996|hPa|inHg|abbr=on}}}} || Philippines, Taiwan, Ryukyu Islands, East China || {{ntsp|87400000||$}} || {{nts|16}} || <ref name="JosieNDRRMC"/> | ] || {{Sort|180720|July 20&nbsp;– 23}} || bgcolor=#{{storm colour|TD}}|{{Sort|0|Tropical depression}} || bgcolor=#{{storm colour|TD}}|{{Sort|055|{{convert|55|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|TD}}|{{Sort|0996|{{convert|996|hPa|inHg|abbr=on}}}} || Philippines, Taiwan, Ryukyu Islands, East China || {{ntsp|87400000||$}} || {{nts|16}} || <ref name="JosieNDRRMC"/>
Line 905: Line 905:
| ] || {{Sort|180814|August 14&nbsp;– 19}} || bgcolor=#{{storm colour|TS}}|{{Sort|1|Tropical storm}} || bgcolor=#{{storm colour|TS}}|{{Sort|085|{{convert|85|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|TS}}|{{Sort|0985|{{convert|985|hPa|inHg|abbr=on}}}} || Ryukyu Islands, China, Korean Peninsula, ] || {{ntsp|5360000000||$}} || {{nts|53}} || <ref name="China Member Report"/> | ] || {{Sort|180814|August 14&nbsp;– 19}} || bgcolor=#{{storm colour|TS}}|{{Sort|1|Tropical storm}} || bgcolor=#{{storm colour|TS}}|{{Sort|085|{{convert|85|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|TS}}|{{Sort|0985|{{convert|985|hPa|inHg|abbr=on}}}} || Ryukyu Islands, China, Korean Peninsula, ] || {{ntsp|5360000000||$}} || {{nts|53}} || <ref name="China Member Report"/>
|- |-
| ] || {{Sort|180815|August 15&nbsp;– 24}} || bgcolor=#{{storm colour|VSTY}}|{{Sort|3|Very strong typhoon}} || bgcolor=#{{storm colour|VSTY}}|{{Sort|155|{{convert|155|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|VSTY}}|{{Sort|0950|{{convert|950|hPa|inHg|abbr=on}}}} || Caroline Islands, Mariana Islands, Northeast China, Japan, Korean Peninsula, Russian Far East, ] || {{ntsp|125000000||$}} || {{nts|86}} ||<ref name="台风苏力致吉林黑龙江损失5.5亿元"/><ref name="SoulikinNK"/><ref name="Wikitree"/> | ] || {{Sort|180815|August 15&nbsp;– 24}} || bgcolor=#{{storm colour|VSTY}}|{{Sort|3|Very strong typhoon}} || bgcolor=#{{storm colour|VSTY}}|{{Sort|155|{{convert|155|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|VSTY}}|{{Sort|0950|{{convert|950|hPa|inHg|abbr=on}}}} || Caroline Islands, Mariana Islands, Northeast China, Japan, Korean Peninsula, Russian Far East, ] || {{ntsp|125000000||$}} || {{nts|86}} ||<ref name="台风苏力致吉林黑龙江损失5.5亿元"/><ref name="SoulikinNK"/>
|- |-
| ] || {{Sort|180816|August 16&nbsp;– 24}} || bgcolor=#{{storm colour|VSTY}}|{{Sort|3|Very strong typhoon}} || bgcolor=#{{storm colour|VSTY}}|{{Sort|155|{{convert|155|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|VSTY}}|{{Sort|0950|{{convert|950|hPa|inHg|abbr=on}}}} || ], Mariana Islands, Japan, ] || {{ntsp|30600000||$}} || {{nts|3}} || <ref name="Global Catastrophe Recap August 2018"/> | ] || {{Sort|180816|August 16&nbsp;– 24}} || bgcolor=#{{storm colour|VSTY}}|{{Sort|3|Very strong typhoon}} || bgcolor=#{{storm colour|VSTY}}|{{Sort|155|{{convert|155|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|VSTY}}|{{Sort|0950|{{convert|950|hPa|inHg|abbr=on}}}} || ], Mariana Islands, Japan, ] || {{ntsp|30600000||$}} || {{nts|3}} || <ref name="Global Catastrophe Recap August 2018"/>
Line 913: Line 913:
| TD || {{Sort|180824|August 24&nbsp;– 26}} || bgcolor=#{{storm colour|TD}}|{{Sort|0|Tropical depression}} || bgcolor=#{{storm colour|TD}}|{{Sort|045|Not specified}} || bgcolor=#{{storm colour|TD}}|{{Sort|1002|{{convert|1002|hPa|inHg|abbr=on}}}} || Ryukyu Islands, East China || None || {{ntsh|0}} None || | TD || {{Sort|180824|August 24&nbsp;– 26}} || bgcolor=#{{storm colour|TD}}|{{Sort|0|Tropical depression}} || bgcolor=#{{storm colour|TD}}|{{Sort|045|Not specified}} || bgcolor=#{{storm colour|TD}}|{{Sort|1002|{{convert|1002|hPa|inHg|abbr=on}}}} || Ryukyu Islands, East China || None || {{ntsh|0}} None ||
|- |-
| ] || {{Sort|180826|August 26&nbsp;– September 4}} || bgcolor=#{{storm colour|VITY}}|{{Sort|3|Violent typhoon}} || bgcolor=#{{storm colour|VITY}}|{{Sort|195|{{convert|195|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|VITY}}|{{Sort|0915|{{convert|915|hPa|inHg|abbr=on}}}} || Mariana Islands, Taiwan, Japan, Russian Far East, ] || {{ntsp|14000000000||$}} || {{nts|21}} ||<ref>{{cite web |last1=Keoni |first1=Everington |title=Rogue waves claim 6 lives over 2 days in NE Taiwan |url=https://www.taiwannews.com.tw/en/news/3521858 |publisher=Taiwan News |access-date=September 4, 2018 |archive-url=https://web.archive.org/web/20180904101046/https://www.taiwannews.com.tw/en/news/3521858 |archive-date=September 4, 2018 |date=September 4, 2018}}</ref><ref>{{cite web |author1=沈如峰 |script-title=zh:南澳神秘沙灘落海意外已釀4死 尚有1失蹤 |url=http://www.cna.com.tw/news/asoc/201809030295-1.aspx |publisher=] |access-date=September 4, 2018 |archive-url=https://web.archive.org/web/20180904101402/http://www.cna.com.tw/news/asoc/201809030295-1.aspx |archive-date=September 4, 2018 |location=Yilan County, Taiwan |language=zh |date=September 3, 2018}}</ref><ref>{{cite web |title=Japan deals with Jebi aftermath |url=https://www3.nhk.or.jp/nhkworld/en/news/20180905_23/ |publisher=] |access-date=September 5, 2018 |date=September 5, 2018 |archive-url=https://web.archive.org/web/20180905133201/https://www3.nhk.or.jp/nhkworld/en/news/20180905_23/ |archive-date=September 5, 2018 |url-status=dead }}</ref><ref>{{cite web|publisher=Insurance Journal|date=September 14, 2018|access-date=September 17, 2018|title=RMS Estimates Insured Losses from Typhoon Jebi Could Reach $5.5 Billion|url=https://www.insurancejournal.com/news/international/2018/09/14/501390.htm|archive-date=September 14, 2018|archive-url=https://web.archive.org/web/20180914230841/https://www.insurancejournal.com/news/international/2018/09/14/501390.htm|url-status=live}}</ref> | ] || {{Sort|180826|August 26&nbsp;– September 4}} || bgcolor=#{{storm colour|VITY}}|{{Sort|3|Violent typhoon}} || bgcolor=#{{storm colour|VITY}}|{{Sort|195|{{convert|195|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|VITY}}|{{Sort|0915|{{convert|915|hPa|inHg|abbr=on}}}} || Mariana Islands, Taiwan, Japan, Russian Far East, ] || {{ntsp|13000000000||$}} || {{nts|21}} ||<ref>{{cite web |last1=Keoni |first1=Everington |title=Rogue waves claim 6 lives over 2 days in NE Taiwan |url=https://www.taiwannews.com.tw/en/news/3521858 |publisher=Taiwan News |access-date=September 4, 2018 |archive-url=https://web.archive.org/web/20180904101046/https://www.taiwannews.com.tw/en/news/3521858 |archive-date=September 4, 2018 |date=September 4, 2018}}</ref><ref>{{cite web |author1=沈如峰 |script-title=zh:南澳神秘沙灘落海意外已釀4死 尚有1失蹤 |url=http://www.cna.com.tw/news/asoc/201809030295-1.aspx |publisher=] |access-date=September 4, 2018 |archive-url=https://web.archive.org/web/20180904101402/http://www.cna.com.tw/news/asoc/201809030295-1.aspx |archive-date=September 4, 2018 |location=Yilan County, Taiwan |language=zh |date=September 3, 2018}}</ref><ref>{{cite web |title=Japan deals with Jebi aftermath |url=https://www3.nhk.or.jp/nhkworld/en/news/20180905_23/ |publisher=] |access-date=September 5, 2018 |date=September 5, 2018 |archive-url=https://web.archive.org/web/20180905133201/https://www3.nhk.or.jp/nhkworld/en/news/20180905_23/ |archive-date=September 5, 2018 |url-status=dead }}</ref><ref>{{cite web|publisher=Insurance Journal|date=September 14, 2018|access-date=September 17, 2018|title=RMS Estimates Insured Losses from Typhoon Jebi Could Reach $5.5 Billion|url=https://www.insurancejournal.com/news/international/2018/09/14/501390.htm|archive-date=September 14, 2018|archive-url=https://web.archive.org/web/20180914230841/https://www.insurancejournal.com/news/international/2018/09/14/501390.htm|url-status=live}}</ref>
|- |-
| TD || {{Sort|180905|September 5&nbsp;– 8}} || bgcolor=#{{storm colour|TD}}|{{Sort|0|Tropical depression}} || bgcolor=#{{storm colour|TD}}|{{Sort|055|{{convert|55|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|TD}}|{{Sort|1004|{{convert|1004|hPa|inHg|abbr=on}}}} || Ryukyu Islands || None || {{ntsh|0}} None || | TD || {{Sort|180905|September 5&nbsp;– 8}} || bgcolor=#{{storm colour|TD}}|{{Sort|0|Tropical depression}} || bgcolor=#{{storm colour|TD}}|{{Sort|055|{{convert|55|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|TD}}|{{Sort|1004|{{convert|1004|hPa|inHg|abbr=on}}}} || Ryukyu Islands || None || {{ntsh|0}} None ||
Line 919: Line 919:
| ] || {{Sort|180906|September 6&nbsp;– 17}} || bgcolor=#{{storm colour|VITY}}|{{Sort|3|Violent typhoon}} || bgcolor=#{{storm colour|VITY}}|{{Sort|205|{{convert|205|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|VITY}}|{{Sort|0905|{{convert|905|hPa|inHg|abbr=on}}}} || Marshall Islands, Mariana Islands, Taiwan, Philippines, ], ], South China, Vietnam || {{ntsp|3766000000||$}} || {{nts|134}} || <ref name="hits 127"/><ref name="OmpongNDRRMC"/><ref name="Global Catastrophe Recap September 2018">{{cite web|title=Global Catastrophe Recap September 2018|url=http://thoughtleadership.aonbenfield.com/Documents/20181009-ab-analytics-if-sept-global-recap.pdf|access-date=October 12, 2018|archive-date=December 9, 2019|archive-url=https://web.archive.org/web/20191209235952/http://thoughtleadership.aonbenfield.com/Documents/20181009-ab-analytics-if-sept-global-recap.pdf|url-status=live}}</ref><ref name="China Member Report"/><ref>{{cite news |script-title=zh:台风"山竹"致澳门经济损失15.5亿|url=http://news.sina.com.cn/o/2018-11-12/doc-ihmutuea9505964.shtml|access-date=2018-11-12|publisher=sina|date=2018-11-12|ref=172|language=zh}}</ref> | ] || {{Sort|180906|September 6&nbsp;– 17}} || bgcolor=#{{storm colour|VITY}}|{{Sort|3|Violent typhoon}} || bgcolor=#{{storm colour|VITY}}|{{Sort|205|{{convert|205|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|VITY}}|{{Sort|0905|{{convert|905|hPa|inHg|abbr=on}}}} || Marshall Islands, Mariana Islands, Taiwan, Philippines, ], ], South China, Vietnam || {{ntsp|3766000000||$}} || {{nts|134}} || <ref name="hits 127"/><ref name="OmpongNDRRMC"/><ref name="Global Catastrophe Recap September 2018">{{cite web|title=Global Catastrophe Recap September 2018|url=http://thoughtleadership.aonbenfield.com/Documents/20181009-ab-analytics-if-sept-global-recap.pdf|access-date=October 12, 2018|archive-date=December 9, 2019|archive-url=https://web.archive.org/web/20191209235952/http://thoughtleadership.aonbenfield.com/Documents/20181009-ab-analytics-if-sept-global-recap.pdf|url-status=live}}</ref><ref name="China Member Report"/><ref>{{cite news |script-title=zh:台风"山竹"致澳门经济损失15.5亿|url=http://news.sina.com.cn/o/2018-11-12/doc-ihmutuea9505964.shtml|access-date=2018-11-12|publisher=sina|date=2018-11-12|ref=172|language=zh}}</ref>
|- |-
| ] || {{Sort|180908|September 8&nbsp;– 13}} || bgcolor=#{{storm colour|TS}}|{{Sort|1|Tropical storm}} || bgcolor=#{{storm colour|TS}}|{{Sort|075|{{convert|75|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|TS}}|{{Sort|0998|{{convert|998|hPa|inHg|abbr=on}}}} || Philippines, Taiwan, South China, Vietnam || {{ntsp|7300000||$}}|| {{ntsh|0}} None || <ref name="China Member Report"/> | ] || {{Sort|180908|September 8&nbsp;– 13}} || bgcolor=#{{storm colour|TS}}|{{Sort|1|Tropical storm}} || bgcolor=#{{storm colour|TS}}|{{Sort|075|{{convert|75|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|TS}}|{{Sort|0998|{{convert|998|hPa|inHg|abbr=on}}}} || Philippines, Taiwan, South China, Vietnam || {{ntsp|7300000||$}}|| {{ntsh|0}} None || <ref name="China Member Report"/>
|- |-
| ] || {{Sort|180920|September 20&nbsp;– October 1}} || bgcolor=#{{storm colour|VITY}}|{{Sort|3|Violent typhoon}} || bgcolor=#{{storm colour|VITY}}|{{Sort|195|{{convert|195|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|VITY}}|{{Sort|0915|{{convert|915|hPa|inHg|abbr=on}}}} || Mariana Islands, Taiwan, Japan, Russian Far East, Alaska || {{ntsp|2690000000||$}} || {{nts|4}} || <ref>{{cite web|url=https://www.worldbulletin.net/asia-pacific/death-toll-rises-to-4-as-japan-striked-by-strong-typhoon-h206213.html|title=Death toll rises to 4, as Japan struck by strong typhoon|publisher=World Bulletin|date=October 2, 2018|access-date=October 8, 2018}}</ref><ref>{{cite web|title=Global Catastrophe Recap October 2018|url=http://thoughtleadership.aonbenfield.com//Documents/20181107-ab-analytics-if-oct-global-recap.pdf|access-date=November 21, 2018|archive-date=November 16, 2018|archive-url=https://web.archive.org/web/20181116085414/http://thoughtleadership.aonbenfield.com/Documents/20181107-ab-analytics-if-oct-global-recap.pdf|url-status=live}}</ref> | ] || {{Sort|180920|September 20&nbsp;– October 1}} || bgcolor=#{{storm colour|VITY}}|{{Sort|3|Violent typhoon}} || bgcolor=#{{storm colour|VITY}}|{{Sort|195|{{convert|195|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|VITY}}|{{Sort|0915|{{convert|915|hPa|inHg|abbr=on}}}} || Mariana Islands, Taiwan, Japan, Russian Far East, Alaska || {{ntsp|2690000000||$}} || {{nts|4}} || <ref>{{cite web|url=https://www.worldbulletin.net/asia-pacific/death-toll-rises-to-4-as-japan-striked-by-strong-typhoon-h206213.html|title=Death toll rises to 4, as Japan struck by strong typhoon|publisher=World Bulletin|date=October 2, 2018|access-date=October 8, 2018}}</ref><ref>{{cite web|title=Global Catastrophe Recap October 2018|url=http://thoughtleadership.aonbenfield.com//Documents/20181107-ab-analytics-if-oct-global-recap.pdf|access-date=November 21, 2018|archive-date=November 16, 2018|archive-url=https://web.archive.org/web/20181116085414/http://thoughtleadership.aonbenfield.com/Documents/20181107-ab-analytics-if-oct-global-recap.pdf|url-status=live}}</ref>
Line 931: Line 931:
| TD || {{Sort|181019|October 19&nbsp;– 20}} || bgcolor=#{{storm colour|TD}}|{{Sort|0|Tropical depression}} || bgcolor=#{{storm colour|TD}}|{{Sort|045|Not specified}} || bgcolor=#{{storm colour|TD}}|{{Sort|1008|{{convert|1008|hPa|inHg|abbr=on}}}} || Vietnam, ], Thailand, Myanmar || None || {{ntsh|0}} None || | TD || {{Sort|181019|October 19&nbsp;– 20}} || bgcolor=#{{storm colour|TD}}|{{Sort|0|Tropical depression}} || bgcolor=#{{storm colour|TD}}|{{Sort|045|Not specified}} || bgcolor=#{{storm colour|TD}}|{{Sort|1008|{{convert|1008|hPa|inHg|abbr=on}}}} || Vietnam, ], Thailand, Myanmar || None || {{ntsh|0}} None ||
|- |-
| ] || {{Sort|181020|October 21&nbsp;– November 2}} || bgcolor=#{{storm colour|VITY}}|{{Sort|3|Violent typhoon}} || bgcolor=#{{storm colour|VITY}}|{{Sort|215|{{convert|215|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|VITY}}|{{Sort|0900|{{convert|900|hPa|inHg|abbr=on}}}} || Caroline Islands, Mariana Islands, Philippines, South China, Taiwan || {{ntsp|854100000||$}} || {{nts|30}} || <ref>{{cite news|url=https://www.usatoday.com/story/news/2018/10/25/super-typhoon-yutu-leaves-1-dead-crisis-looms-saipan-and-tinian/1771400002/|title=Humanitarian crisis looms after Super Typhoon Yutu flattens parts of Saipan and Tinian|author=Haidee V. Eugenio|publisher=USA Today|date=October 26, 2018|access-date=January 30, 2019}}</ref><ref>{{cite web|title=Global Catastrophe Recap October 2018|url=http://thoughtleadership.aonbenfield.com//Documents/20181107-ab-analytics-if-oct-global-recap.pdf|website=AON|publisher=AON|date=November 7, 2018|access-date=November 21, 2018|archive-date=November 16, 2018|archive-url=https://web.archive.org/web/20181116085414/http://thoughtleadership.aonbenfield.com/Documents/20181107-ab-analytics-if-oct-global-recap.pdf|url-status=live}}</ref> | ] || {{Sort|181020|October 21&nbsp;– November 2}} || bgcolor=#{{storm colour|VITY}}|{{Sort|3|Violent typhoon}} || bgcolor=#{{storm colour|VITY}}|{{Sort|215|{{convert|215|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|VITY}}|{{Sort|0900|{{convert|900|hPa|inHg|abbr=on}}}} || Caroline Islands, Mariana Islands, Philippines, South China, Taiwan || {{ntsp|854100000||$}} || {{nts|30}} || <ref>{{cite news|url=https://www.usatoday.com/story/news/2018/10/25/super-typhoon-yutu-leaves-1-dead-crisis-looms-saipan-and-tinian/1771400002/|title=Humanitarian crisis looms after Super Typhoon Yutu flattens parts of Saipan and Tinian|author=Haidee V. Eugenio|publisher=USA Today|date=October 26, 2018|access-date=January 30, 2019}}</ref><ref>{{cite web|title=Global Catastrophe Recap October 2018|url=http://thoughtleadership.aonbenfield.com//Documents/20181107-ab-analytics-if-oct-global-recap.pdf|website=AON|date=November 7, 2018|access-date=November 21, 2018|archive-date=November 16, 2018|archive-url=https://web.archive.org/web/20181116085414/http://thoughtleadership.aonbenfield.com/Documents/20181107-ab-analytics-if-oct-global-recap.pdf|url-status=live}}</ref>
|- |-
| ] || {{Sort|181113|November 14&nbsp;– 26}} || bgcolor=#{{storm colour|STS}}|{{Sort|2|Severe tropical storm}} || bgcolor=#{{storm colour|STS}}|{{Sort|110|{{convert|110|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|STS}}|{{Sort|0990|{{convert|990|hPa|inHg|abbr=on}}}} || Caroline Islands, Philippines, Vietnam, Cambodia, Laos || {{ntsp|40494000||$}} || {{nts|4}} || <ref name="Usagi PHI death"/><ref name="Usagi 3 dead"/> | ] || {{Sort|181113|November 14&nbsp;– 26}} || bgcolor=#{{storm colour|STS}}|{{Sort|2|Severe tropical storm}} || bgcolor=#{{storm colour|STS}}|{{Sort|110|{{convert|110|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|STS}}|{{Sort|0990|{{convert|990|hPa|inHg|abbr=on}}}} || Caroline Islands, Philippines, Vietnam, Cambodia, Laos || {{ntsp|40494000||$}} || {{nts|4}} || <ref name="Usagi PHI death"/><ref name="Usagi 3 dead"/>
Line 941: Line 941:
| ] || {{Sort|181225|December 25&nbsp;– 29}} || bgcolor=#{{storm colour|TD}}|{{Sort|0|Tropical depression}} || bgcolor=#{{storm colour|TD}}|{{Sort|055|{{convert|55|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|TD}}|{{Sort|1000|{{convert|1000|hPa|inHg|abbr=on}}}} || ], Philippines || {{ntsp|103000000||$}} || {{nts|156}} || | ] || {{Sort|181225|December 25&nbsp;– 29}} || bgcolor=#{{storm colour|TD}}|{{Sort|0|Tropical depression}} || bgcolor=#{{storm colour|TD}}|{{Sort|055|{{convert|55|km/h|mph|abbr=on}}}} || bgcolor=#{{storm colour|TD}}|{{Sort|1000|{{convert|1000|hPa|inHg|abbr=on}}}} || ], Philippines || {{ntsp|103000000||$}} || {{nts|156}} ||
|- |-
{{TC Areas affected (Bottom)|TC's=43&nbsp;systems|dates=December&nbsp;29, 2017 –<br>December&nbsp;29, 2018|winds={{convert|215|km/h|mph|abbr=on}}|pres={{convert|900|hPa|inHg|abbr=on}}|damage={{ntsp|31537556000||$}} <!-- 31,537.556 -->|deaths=793|Refs=}} {{TC Areas affected (Bottom)|TC's=43&nbsp;systems|dates=December&nbsp;29, 2017 –<br>December&nbsp;29, 2018|winds={{convert|215|km/h|mph|abbr=on}}|pres={{convert|900|hPa|inHg|abbr=on}}|damage={{ntsp|30537556000||$}} <!-- 30,537.556 -->|deaths=793|Refs=}}


==See also== ==See also==
Line 963: Line 963:


==External links== ==External links==
{{Commons category|2018 Pacific typhoon season}} {{Commons category}}
{{WPAC EL's}} {{WPAC EL's}}
* *

Latest revision as of 07:44, 25 December 2024

2018 Pacific typhoon season
Season summary map
Seasonal boundaries
First system formedDecember 29, 2017 (2017-12-29)
Last system dissipatedDecember 29, 2018 (2018-12-29)
Strongest storm
NameKong-rey & Yutu
 • Maximum winds215 km/h (130 mph)
(10-minute sustained)
 • Lowest pressure900 hPa (mbar)
Seasonal statistics
Total depressions44, 1 unofficial
Total storms29, 1 unofficial
Typhoons13
Super typhoons7 (unofficial)
Total fatalities793 total
Total damage$30.54 billion (2018 USD)
(Third-costliest Pacific typhoon season on record)
Related articles
Pacific typhoon seasons
2016, 2017, 2018, 2019, 2020

The 2018 Pacific typhoon season was at the time, the costliest Pacific typhoon season on record, until the record was beaten by the following year. The season was well above-average, producing twenty-nine storms (including one that crossed over from the Eastern/Central Pacific), thirteen typhoons, seven super typhoons and six Category 5 tropical cyclones. The season ran throughout 2018, though most tropical cyclones typically develop between May and October. The season's first named storm, Bolaven, developed on January 3, while the season's last named storm, Man-yi, dissipated on November 28. The season's first typhoon, Jelawat, reached typhoon status on March 29, and became the first super typhoon of the year on the next day.

The scope of this article is limited to the Pacific Ocean, to the north of the equator between 100°E and the 180th meridian. Within the northwestern Pacific Ocean, there are two separate agencies that assign names to tropical cyclones, which can often result in a cyclone having two names, one from the JMA and one from PAGASA. The Japan Meteorological Agency (JMA) will name a tropical cyclone should it be judged to have 10-minute sustained wind speeds of at least 65 km/h (40 mph) anywhere in the basin, while the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) assigns 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 regardless of whether or not a tropical cyclone has already been given a name by the JMA. Tropical depressions that are monitored by the United States' Joint Typhoon Warning Center (JTWC) are given a number with a "W" suffix.

Seasonal forecasts

TSR forecasts
Date
Tropical
storms
Total
Typhoons
Intense
TCs
ACE Ref
Average (1965–2017) 26 16 9 294
May 11, 2018 27 17 9 307
July 6, 2018 27 17 10 331
August 7, 2018 27 17 9 319
Other forecasts
Date
Forecast
Center
Period Systems Ref
January 15, 2018 PAGASA January–March 1–3 tropical cyclones
January 15, 2018 PAGASA April–June 2–4 tropical cyclones
March 15, 2018 VNCHMF January–December 12–13 tropical cyclones
March 23, 2018 HKO January–December 5–8 tropical cyclones
July 13, 2018 PAGASA July–September 6–8 tropical cyclones
July 13, 2018 PAGASA October–December 4–6 tropical cyclones
2018 season Forecast
Center
Tropical
cyclones
Tropical
storms
Typhoons Ref
Actual activity: JMA 44 29 13
Actual activity: JTWC 36 30 16
Actual activity: PAGASA 20 15 6

During the year, several national meteorological services and scientific agencies forecast how many tropical cyclones, tropical storms, and typhoons will form during a season and/or how many tropical cyclones will affect a particular country. These agencies included the Tropical Storm Risk (TSR) Consortium of University College London, PAGASA and Taiwan's Central Weather Bureau. The first forecast of the year was released by PAGASA on January 15, within its seasonal climate outlook for the period January–June. The outlook noted that one to three tropical cyclones were expected between January and March, while two to four were expected to develop or enter the Philippine Area of Responsibility between April and June. PAGASA also mentioned that the La Niña would be short-lived, predicting that it would last until February or April.

On March 15, the Vietnamese National Center for Hydro Meteorological forecasts (VNCHMF) predicted that roughly twelve to thirteen tropical cyclones would affect Vietnam during 2018, which is above average. On March 23, the Hong Kong Observatory predicted that five to eight tropical cyclones would come within 500 kilometres of Hong Kong, which is normal to above normal, with the first tropical cyclone affecting Hong Kong in June or earlier. On May 11, the Tropical Storm Risk (TSR) issued their first forecast for the season, predicting that the 2018 season would be a slightly above average season with 27 named storms, 17 typhoons, and nine intense typhoons. The TSR released their second forecast on July 6, still predicting that the season will be above average, with the only changes to their forecast increasing the number of intense typhoons from 9 to 10. The PAGASA issued their second and final outlook on July 13 for the period of July – December, predicting six to eight tropical cyclones were expected to develop or enter their area of responsibility between July and September, while four to six were forecast during October to December. On August 7, TSR released their final forecast, with its only changes decreasing the numbers of intense typhoons from 10 to 9, as well as decreasing its ACE forecast from 331 units to 319 units.

Season summary

This section needs expansion. You can help by adding to it. (November 2020)
Tropical Storm Pabuk (2019)Tropical Depression UsmanTropical Storm Toraji (2018)Tropical Storm Usagi (2018)Typhoon YutuTyphoon Kong-rey (2018)Typhoon TramiTropical Storm Barijat (2018)Typhoon MangkhutTyphoon Jebi (2018)Typhoon Cimaron (2018)Typhoon Soulik (2018)Tropical Storm RumbiaHurricane Hector (2018)Tropical Storm Bebinca (2018)Tropical Storm Yagi (2018)Typhoon Shanshan (2018)Typhoon JongdariTropical Depression JosieTropical Storm Ampil (2018)Tropical Storm Son-Tinh (2018)Typhoon Maria (2018)Typhoon Prapiroon (2018)Tropical Storm Maliksi (2018)Tropical Storm Ewiniar (2018)Typhoon Jelawat (2018)Tropical Storm Sanba (2018)Tropical Storm Bolaven (2018)
Six tropical cyclones active on August 16: Bebinca (bottom left), Yagi (top left, overland), and Rumbia (center-left) affecting China; Soulik (center-right) and a tropical depression (bottom right, precursor to Cimaron) near the Mariana Islands; and a degenerating Hector (top right) located in the far northwest Pacific

2018 opened with Tropical Depression Agaton active to the east of the Philippines. Over the course of two days, the system moved into the South China Sea and intensified into the first named storm, Bolaven. A month later, Tropical Storm Sanba developed and affected the southern Philippines. About another month later, Tropical Depression 03W formed in the open Pacific and was named Jelawat. Jelawat intensified into the season's first typhoon on March 29, and then the season's first super typhoon. Tropical activity fired up by June, when a series of storms developed, with Tropical Storm Ewiniar making landfall over mainland China. Later that month, Typhoon Prapiroon developed and affected the Korean Peninsula, becoming the first to do so since 2013. Thereafter, Typhoon Maria developed and reached its peak intensity as a Category 5 super typhoon, being the first typhoon to reach that intensity since Typhoon Nock-ten in 2016. Hurricane Hector crossed the International Date Line on August 13, the first to do so since Genevieve in 2014. Systems like Tropical Storms Son-Tinh, Ampil, Josie, Wukong, Jongdari, Shanshan, Yagi, Leepi, Bebinca, and Rumbia formed between late July and early August.

Costliest known Pacific typhoon seasons
Rank Total damages Season
1 ≥ $38.96 billion 2019
2 ≥ $37.63 billion 2023
3 ≥ $30.54 billion 2018
4 ≥ $26.8 billion 2024
5 ≥ $26.43 billion 2013
6 ≥ $20.79 billion 2012
7 ≥ $18.77 billion 2004
8 ≥ $18.36 billion 1999
9 ≥ $17.69 billion 2016
10 ≥ $15.1 billion 2017

On August 16, Typhoon Soulik developed and headed north, until a Fujiwhara interaction with Typhoon Cimaron (which formed after Soulik) made it head west towards the East China Sea. It later made landfall on South Korea, making it the first typhoon to make landfall on South Korea since Typhoon Chaba in 2016. Cimaron made landfall near Kyoto, Japan on August 23. As Cimaron was nearing landfall, Tropical Depression Luis formed, which made landfall on China and Taiwan. Later that month, Typhoon Jebi developed over the West Pacific and intensified into the third super typhoon of the season.

In September, Typhoon Mangkhut became the fourth super typhoon of the season and made landfall on the island of Luzon in the Philippines. On the same day, Tropical Depression Neneng formed, which later became Tropical Storm Barijat and made landfall on Vietnam. By late September, Typhoon Trami (Paeng) formed, becoming the 5th super typhoon of 2018. While Typhoon Trami was in the Western Pacific, nearing Okinawa with winds of 165 km/h (103 mph), Tropical Depression 30W formed, and was named Kong-rey by the JMA after strengthening into a tropical storm. It intensified into a super typhoon on October 2, becoming the 5th Category 5 super typhoon. Later on in the month, it was followed by the sixth and final Category 5-equivalent storm of the season, Yutu.

Systems

Tropical Storm Bolaven (Agaton)

Tropical storm (JMA)
Tropical storm (SSHWS)
 
DurationDecember 29, 2017 – January 4, 2018
Peak intensity65 km/h (40 mph) (10-min);
1002 hPa (mbar)
Main article: Tropical Storm Bolaven (2018)

A low-pressure area developed into a tropical depression northeast of Palau on December 29, 2017. The system moved generally westward, and on the first day of 2018, the PAGASA began issuing advisories on the system and locally named it Agaton. Both the JMA and the JTWC followed suit, with the latter designating the system as 01W. The depression reached the Philippines on January 1, making landfall over Bucas Grande at 17:00 UTC, then at Claver, Surigao del Norte at 17:15 UTC. The system crossed the Bohol Sea before making a third landfall near Jagna, Bohol at 20:00 UTC, a fourth in Santander, Cebu at 21:00 UTC, and a final landfall at Bais, Negros Oriental at 23:30 UTC. By January 3, the system had intensified into a tropical storm according to the JMA and was named Bolaven, thus becoming the first named storm of the season. However, several hours later, Bolaven started to weaken and rapidly deteriorate. The system was last tracked by the JMA to the east of Vietnam on January 4.

The impact caused by Bolaven (Agaton) was moderate but not as significant as the previous two systems, Kai-tak and Tembin, with about 2,000 passengers stranded in ports in the Visayas. As of January 22, three people have been reported killed by the storm, while total damages were up to Ph₱554.7 million (US$11.1 million).

Tropical Storm Sanba (Basyang)

Tropical storm (JMA)
Tropical storm (SSHWS)
 
DurationFebruary 8 – February 16
Peak intensity65 km/h (40 mph) (10-min);
1000 hPa (mbar)
Main article: Tropical Storm Sanba (2018)

A low-pressure system developed into a tropical depression north of Chuuk early on February 8. It developed into a tropical storm on February 11, receiving the international name Sanba by the JMA. Shortly afterwards, Sanba entered the Philippine area of responsibility and was assigned the local name Basyang by the PAGASA. On February 13, Sanba made landfall on Cortes, Surigao Del Sur, causing it to weaken to a tropical depression. On the next day, the system weakened into a remnant low as it made another landfall in Surigao del Sur.

A total of 1,660 houses were damaged, of which 429 were completely destroyed; most of the homes damaged were in Caraga. Siargao Island, Silay City, Carmen municipality in Bohol, and the municipalities of Culaba and Kawayan in Biliran were affected by power outages from February 12 to 13. Twenty-two roads and eight bridges were damaged by floods and landslides. Two boats carrying people capsized: a fishing boat near Silago, Southern Leyte, and a passenger vessel en route to Homonhon. All four on board the two boats survived. Approximately 17,000 people were affected by the storm and there were 14 fatalities. Total agricultural damages were at Php 168 million (US$3.23 million), mostly coming from flooded rice fields.

Typhoon Jelawat (Caloy)

Violent typhoon (JMA)
Category 4 super typhoon (SSHWS)
 
DurationMarch 24 – April 1
Peak intensity195 km/h (120 mph) (10-min);
915 hPa (mbar)
Main article: Typhoon Jelawat (2018)

On March 24, a tropical depression formed to the south of the Mariana Islands, and the JTWC assigned it the numerical identifier 03W. On March 25, the system intensified into a tropical storm and was named Jelawat by the JMA, and at the same time it entered PAGASA's Philippine Area of Responsibility (PAR) and was assigned the local name Caloy. Due to strong southwesterly wind shear, the cyclone remained poorly organized, with disorganized convection near an exposed low-level circulation. Conditions gradually became more favorable for further development, resulting in Jelawat steadily strengthening and gaining organization before intensifying into a severe tropical storm at 18:00 UTC on March 28. Later on March 29, an eye began to emerge within a growing central dense overcast, leading to the JMA classifying it as a typhoon at 00:00 UTC on March 29. Explosive intensification then ensued over the following 36 hours as the eye became sharply defined, and Jelawat attained its peak intensity later that morning, with estimated 10-minute sustained winds of 195 km/h (121 mph) and a central pressure of 915 hPa (27.0 inHg). At the same time, the JTWC assessed it as peaking with 1-minute sustained winds of 240 km/h (150 mph), making it a Category 4 super typhoon.

Immediately after peaking in intensity, Jelawat began weakening rapidly due to a sharp increase in wind shear and dry air, and the storm fell below typhoon strength late on March 31. During the next couple of days, Jelawat drifted to the northeast and then turned eastward before dissipating on April 1.

Jelawat yielded 20 inches of rainfall on parts of the island of Pohnpei, resulting in flooding and landslides that caused critical damage to infrastructure and one death. A woman in Guam drowned from the remnants of Jelawat on April 3, after strong surf and rip currents stranded her in water.

Tropical Depression 04W

Tropical depression (JMA)
Tropical storm (SSHWS)
 
DurationMay 10 – May 15
Peak intensity55 km/h (35 mph) (10-min);
1008 hPa (mbar)

A low-pressure area east of Mariana Islands was upgraded to a tropical depression by the JMA late on May 10 shortly before the JTWC issued a TCFA. By May 12, deep convection was observed near its center as the JTWC began issuing advisories on the system, giving it the designation 04W. Roughly twelve hours later, it was reported that 04W had intensified into a tropical storm by the JTWC after satellite imagery had depicted a well-defined center. Tracking on a west-northwesterly course, the system began to weaken as it entered an area of unfavorable conditions. 04W rapidly weakened as the JTWC issued their final advisory on the system early on May 14 as wind shear affected the system and exposed the elongated low-level circulation. The JMA, however, tracked the system until early on May 15, when it dissipated.

Tropical Storm Ewiniar

Tropical storm (JMA)
Tropical storm (SSHWS)
 
DurationJune 2 – June 9
Peak intensity75 km/h (45 mph) (10-min);
998 hPa (mbar)
Main article: Tropical Storm Ewiniar (2018)

A low-pressure area developed into a tropical depression over the South China Sea on June 2. Later that day, the JTWC followed suit and assigned the designation 05W to the system. 05W meandered in a westward direction until it curved northward, and after three days, the JTWC upgraded the system to a tropical storm. The JMA did the same three hours later early on June 6, naming it Ewiniar. Shortly thereafter, Ewiniar made landfall over South China. Ewiniar maintained its intensity while over land until the JTWC issued its final advisory late on June 7. The JMA, however, tracked the system until early on June 9, when Ewiniar had weakened into a tropical depression and degenerated into a remnant low. However, Ewiniar's remnants moved out to sea and continued to persist, before dissipating on June 13.

A total of 13 people were killed, while total damages in mainland China were counted to be ¥5.19 billion (US$812 million).

Severe Tropical Storm Maliksi (Domeng)

Severe tropical storm (JMA)
Tropical storm (SSHWS)
 
DurationJune 3 – June 11
Peak intensity110 km/h (70 mph) (10-min);
970 hPa (mbar)
Main article: Tropical Storm Maliksi (2018)

A low-pressure area northwest of Palau developed into a tropical depression late on June 3. On the next day, the system received the local name Domeng from the PAGASA as the JTWC issued a TCFA on the system. After the system had consolidated further, the JMA upgraded the system to a tropical storm, naming it Maliksi (1805). The JTWC, however, did not track the system until 03:00 UTC on June 8 when it gave Maliksi the designation of 06W. Moving northward, Maliksi continued to intensify until it reached its peak strength early on June 10 with winds of 110 km/h (68 mph), just shy of typhoon intensity, and a minimum pressure of 970 hPa. Operationally, the JMA briefly classified Maliksi as a typhoon, but it was downgraded to a severe tropical storm in post-analysis. Maliksi began to weaken as it began extratropical transition, and on June 11 as it encountered more unfavorable conditions, both agencies stopped issuing warnings on Maliksi as the system's center became exposed and as it transitioned into an extratropical cyclone. The JMA tracked the remnants of Maliksi until 00:00 UTC on June 13.

Despite not making landfall on the Philippines, Maliksi prompted the PAGASA to declare the official start of the rainy season on June 8, 2018. Two people were killed by heavy monsoonal rains enhanced by Maliksi in the Philippines.

Subtropical Storm 07W

Subtropical storm (SSHWS)
 
DurationJune 13 – June 15
Peak intensity65 km/h (40 mph) (1-min);
996 hPa (mbar)

A disturbance formed southwest of Taiwan on June 12 just within the meiyu front, and the JTWC subsequently indicated the formation of a subtropical depression. At 21:00 UTC on June 13, the JTWC issued its first advisory on the system and designated it as 07W, classifying it as a tropical depression. Despite being affected by moderate to severe wind shear, the system was located over relatively warm sea-surface temperatures as it produced patches of convection, and this prompted the JTWC to upgrade 07W to a tropical storm. The JTWC later issued their fourth but final advisory on 07W at 15:00 UTC on June 14 when the system was rapidly undergoing a phase of extratropical transition and as the system was rapidly losing its structure. 07W fully became an extratropical cyclone just to the south of mainland Japan at 06:00 UTC on June 15, although its remnant was still tracked until June 25, when the system was last located near the coast of British Columbia.

Tropical Storm Gaemi (Ester)

Tropical storm (JMA)
Tropical storm (SSHWS)
 
DurationJune 13 – June 17
Peak intensity85 km/h (50 mph) (10-min);
990 hPa (mbar)

On June 13, a tropical depression formed on the South China Sea from the trough of 07W. Tracking east-northeastward on June 14, the PAGASA announced it had entered the Philippine Area of Responsibility at 16:00 UTC, receiving the local name Ester. Tropical Depression Ester (08W) made landfall on Kaohsiung, Taiwan by midnight, and after emerging off the coast, assigned the name Gaemi by the JMA with the international designation of "1806" by the RSMC in Tokyo as it intensified to tropical storm. On June 16, Gaemi transitioned into an extratropical cyclone. The storm sustained the strong southwest monsoon that was previously enhanced by Tropical Storm Maliksi days prior.

On June 19, the NDRRMC reported that 3 people had died from monsoonal rains enhanced by Gaemi. Agricultural damage in Okinawa Prefecture were estimated at ¥84.58 million (US$764,000).

Typhoon Prapiroon (Florita)

Typhoon (JMA)
Category 1 typhoon (SSHWS)
 
DurationJune 28 – July 4
Peak intensity120 km/h (75 mph) (10-min);
960 hPa (mbar)
Main article: Typhoon Prapiroon (2018) See also: 2018 Japan floods

A low-pressure area west of Okinotorishima developed into Tropical Depression 09W on June 28. On the next day, the PAGASA began issuing advisories, assigning it the local name Florita. 6 hours later, Florita became a tropical storm, with the JMA assigning it the name Prapiroon (1807). By July 2, Prapiroon intensified into a Category 1 typhoon as it neared Japan and Korea. By July 3, Prapiroon had attained peak intensity. On the same day, Prapiroon made landfall on Japan. After making landfall, Prapiroon briefly weakened to a tropical storm. Prapiroon became a low-pressure area on the next day, though the JMA still tracked its remnants until July 10, when it finally dissipated.

Five people were injured by the winds from the typhoon. A woman was blown away by the strong winds of the typhoon and died at a hospital she was sent to later. The typhoon also caused damages on Old Gorin Church, which as designated as heritage site four days prior, and caused damages to the stained glass in Kuroshima Catholic Church. One person from South Korea was killed by the storm. Agricultural damage in Okinawa Prefecture were about ¥49.39 million (US$446,000).

Typhoon Maria (Gardo)

Violent typhoon (JMA)
Category 5 super typhoon (SSHWS)
 
DurationJuly 3 – July 12
Peak intensity195 km/h (120 mph) (10-min);
915 hPa (mbar)
Main article: Typhoon Maria (2018)

A tropical disturbance formed over the Marshall Islands late on June 26. After slow development and as it drifted westward for five days, the Joint Typhoon Warning Center (JTWC) issued a Tropical Cyclone Formation Alert early on July 2 and upgraded the system to a tropical depression, designating it 10W late on the same day. Early on July 3, the Japan Meteorological Agency upgraded the low-pressure area into a tropical depression southeast of Guam and subsequently started to issue tropical cyclone warnings. Favorable environmental conditions, including moderate vertical wind shear, poleward outflow enhanced by tropical upper tropospheric trough (TUTT) cells located to the northeast and to the northwest, sea surface temperatures between 30 and 31 °C, were contributing to the development of the system on July 4. As a result, the system continued to organize and the JMA upgraded it to a tropical storm and assigned it the international name Maria at around 12:00 UTC, with the JTWC also upgrading it to a tropical storm. Six hours later, when the storm struck Guam directly, surface observations at Andersen Air Force Base recorded one-minute maximum sustained winds of 50 knots (93 km/h; 58 mph) and a minimum pressure of 984 hPa (29.06 inHg), indicating a rapidly consolidating system.

On July 5, Maria drifted northwestward slowly under the influences of a weak north–south oriented steering ridge and a strong east–west oriented subtropical ridge entrenched to the north. After being upgraded to a severe tropical storm by JMA and a typhoon by JTWC early on the same day, Maria began undergoing extremely rapid intensification due to highly favorable conditions, intensifying from a tropical storm to a Category 5 on the Saffir–Simpson scale in under 24 hours. Microwave imagery revealed an eye and the JMA upgraded Maria to a typhoon in the afternoon. The JTWC upgraded Maria to a super typhoon and reported that it reached its initial peak intensity with one-minute maximum sustained winds of 260 km/h (160 mph) at around 00:00 UTC on July 6, making it the first Category 5-equivalent tropical cyclone in the northern hemisphere since Hurricane Maria in September 2017, and the first in the western Pacific since Typhoon Nock-ten. At around 01:10 UTC on July 11, Maria made landfall over the Huangqi Peninsula of Lianjiang County, Fuzhou in Fujian, China with ten-minute maximum sustained winds of 155 km/h (96 mph) and a central pressure of 955 hPa (28.20 inHg).

When it made landfall in East China on July 10, it soaked Southern Japan and killed 1 person. Total damages in mainland China were estimated to be CN¥4.16 billion (US$623 million).

Tropical Storm Son-Tinh (Henry)

Tropical storm (JMA)
Tropical storm (SSHWS)
 
DurationJuly 16 – July 24
Peak intensity75 km/h (45 mph) (10-min);
994 hPa (mbar)
Main article: Tropical Storm Son-Tinh (2018) See also: 2018 Laos dam collapse and 2018 Northern Vietnam floods

An area of low-pressure strengthened into a tropical depression on July 15 to the northwest of Manila, Philippines. The JTWC designated it as 11W while the PAGASA gave it the local name Henry. As the system moved fast in a westward direction towards the Babuyan Islands, the system gradually intensified and was declared a tropical storm on July 17, with the JMA naming it as Son-Tinh as its convective structure improved. Thereafter, Son-Tinh slightly weakened as it neared Hainan Island while experiencing moderate shear. During the next day, however, Son-Tinh slightly intensified over the Gulf of Tonkin due to warm sea-surface temperatures before it made landfall on northern Vietnam. Both agencies issued their final warnings on Son-Tinh on July 19 as the system had weakened back into an area of low-pressure embedded into the monsoon. However, the JTWC continued to track the system's remnants for another two days before it dissipated.

In Vietnam, the Thanh Hóa and Nghệ An provinces suffered the most damage, especially with the wake of the storm continuing to generate significant rainfall. It caused major flooding in Northern Vietnam and the capital city of Hanoi. 35 people were killed, more than 5,000 houses, 82,000 hectares (200,000 acres) of crops, and 17,000 farm animals were either swept away, submerged, or otherwise destroyed. The storm has cut off access to several areas in the country and flood water covers several streets in the capital city. Economic losses were estimated to be 6.615 trillion (US$287 million).

Severe Tropical Storm Ampil (Inday)

Severe tropical storm (JMA)
Tropical storm (SSHWS)
 
DurationJuly 17 – July 24
Peak intensity95 km/h (60 mph) (10-min);
985 hPa (mbar)
Main article: Tropical Storm Ampil (2018)

On July 17, a weak tropical depression developed over the Philippine Sea. The JTWC upgraded the system to a tropical depression on the same day, designating it as 12W as it was located over a favorable environment. On the next day, the PAGASA followed suit and it was given the local name Inday. By 12:00 UTC on July 18, the JMA upgraded the system to a tropical storm, assigning it the name Ampil. As Ampil moved in a northward direction, the system's structure had broadened, being accompanied by sustained deep convection. Despite unfavorable ocean heat content, Ampil still remained over relatively warm sea surface temperatures with the inclusion of extensive deep convection, therefore Ampil was classified as a severe tropical storm. With an improved convective system, the JTWC assessed that Ampil had reached maximum 1-minute sustained winds of 95 km/h (59 mph). Ampil reached its peak intensity with a minimum pressure of 985 hPa and maintained that intensity for the next few days as the track of Ampil changed direction. On July 21, the system's center became exposed as the system slightly weakened. On the next day, the JMA downgraded Ampil back to a tropical storm as it made landfall on China with a lack of convection. Ampil weakened further to a tropical depression on July 23, and both agencies issued their final advisories on the system. The JMA continued tracking the system until it weakened into an area of low pressure at 18:00 UTC on July 24.

Heavy rain in Shandong Province—accumulating to 237 mm (9.3 in) in Tianjin—caused significant flooding, inundating 31,600 hectares of crops and affecting 260,000 people. One person was killed in China and total economic losses reached CN¥1.63 billion (US$241 million).

Tropical Depression 13W (Josie)

Tropical depression (JMA)
Tropical storm (SSHWS)
 
DurationJuly 20 – July 23
Peak intensity55 km/h (35 mph) (10-min);
996 hPa (mbar)
Main article: Tropical Depression Josie

A tropical depression formed in the South China Sea on July 20 according to the JMA. On July 21, the system entered the Philippine Area of Responsibility and was assigned the local name Josie, making it the 10th named storm to enter the PAR. The JTWC upgraded the system to a tropical storm on the same day. The system missed landfall within kilometers on Saud, Ilocos Norte. It moved north and exited the PAR on the next day. The remnants of 13W dissipated off the coast of China.

After the formation of the previous two systems, the southwest monsoon had been extremely active in the Philippines. By August 1, a total of 16 people had been killed due to extreme flooding, while damages have been recorded at 4.66 billion (US$87.4 million). The southwest monsoon had been active since Typhoon Maria. July had 5 days of class suspensions in Metro Manila, making it the second in history since Typhoon Ketsana struck Metro Manila and caused ocean-high flooding since 2009.

Severe Tropical Storm Wukong

Severe tropical storm (JMA)
Category 1 typhoon (SSHWS)
 
DurationJuly 22 – July 26
Peak intensity95 km/h (60 mph) (10-min);
990 hPa (mbar)

Late on July 21, the JTWC began to issue advisories on Tropical Depression 14W as it developed about 603 km (375 mi) east-southeast of the Japanese island of Minami-Tori-shima. The JMA began tracking the system on the early hours of July 22. Later that day, the JTWC upgraded 14W to a tropical storm, though convection was sheared and the system was located in unfavorable southwesterly shear. Within the next 24 hours, 14W began to organize with deep convection obscuring its LLCC, and at 12:00 UTC on July 23, the JMA upgraded the system to a tropical storm, naming it Wukong. Moving poleward, Wukong gradually intensified while entering an area of favorable environment with lesser shear, and at 00:00 UTC on July 25, the JMA upgraded Wukong to a severe tropical storm. Nine hours later, the JTWC upgraded Wukong to a Category 1 typhoon after satellite images depicted a 30-nmi ragged eye. By July 26, both the JMA and the JTWC issued their final advisories on Wukong as the system rapidly transitioned into an extratropical cyclone. Wukong's extratropical remnants were tracked until late on July 27 when it was last noticed off the eastern coast of Russia Far East.

Typhoon Jongdari

Typhoon (JMA)
Category 2 typhoon (SSHWS)
 
DurationJuly 23 – August 4
Peak intensity140 km/h (85 mph) (10-min);
960 hPa (mbar)
Main article: Typhoon Jongdari

A tropical disturbance formed southeast of Guam on July 19 and tracked westward steadily. After issuing a Tropical Cyclone Formation Alert on July 21, the Joint Typhoon Warning Center (JTWC) upgraded the system to a tropical depression early on July 22, although the location of its low-level circulation center was not clear. The Japan Meteorological Agency (JMA), however, kept reporting it as a low-pressure area until it was upgraded to a tropical depression late on July 23. After slow consolidation for several days, the system was upgraded to a tropical storm near Okinotorishima at around 18:00 on July 24 by the JMA and the JTWC, being assigned the international name Jongdari. Microwave imagery revealed a low-level eyewall forming on the next day, indicating a consolidating system. After the JMA upgraded Jongdari to a severe tropical storm at noon, the system accelerated northeastward under the influence of a near-equatorial ridge to the south.

On July 26, as Jongdari started to interact with an upper-level cold-core low to the north which significantly enhanced poleward outflow, it intensified to a typhoon in the afternoon despite increasingly unfavorable vertical wind shear. Over the warm sea surface temperatures between 29 and 30 °C (84 and 86 °F) near the Ogasawara Islands, JMA reported that Jongdari had reached peak intensity at 00:00 UTC on July 27, with ten-minute maximum sustained winds of 140 km/h (87 mph) and a minimum central pressure of 965 hPa (28.5 inHg). Although the JTWC indicated Jongdari reached peak intensity at 12:00 UTC with one-minute maximum sustained winds of 175 km/h (109 mph), the rugged eye of Jongdari remained periodically visible with an elongated structure due to further interaction of the upper-level low which had moved to the northwest side of the typhoon. As the steering influence transitioned to a subtropical ridge to the northeast, Jongdari executed a counter-clockwise turn to the southeast of Japan.

Jongdari began to be inundated by subsidence on July 28 as the Fujiwhara effect had made the upper-level low move to the west of the typhoon. It also initiated a weakening trend while accelerating northwestward and then westward toward the Japanese island of Honshu. At around 01:00 JST on July 29 (16:00 UTC July 28), Jongdari made landfall over Ise, Mie Prefecture with ten-minute maximum sustained winds of 120 km/h (75 mph) and a central pressure of 975 hPa (28.8 inHg). The storm weakened rapidly inland before making its second landfall over Buzen, Fukuoka Prefecture, at around 17:30 JST (08:30 UTC), with ten-minute sustained winds of 75 km/h (47 mph) and a central pressure of 992 hPa (29.3 inHg). At around 10:30 CST (02:30 UTC) on August 3, Jongdari made landfall over Jinshan District, Shanghai as a tropical storm. Jongdari rapidly weakened after landfall, dissipating on the next day. No fatalities were recorded for this storm.

Tropical Depression 16W

Tropical depression (JMA)
Subtropical storm (SSHWS)
 
DurationJuly 31 – August 1
Peak intensity55 km/h (35 mph) (10-min);
1002 hPa (mbar)

A tropical disturbance developed about 807 km (501 mi) north-northeast of Iwo To by July 29. The JTWC upgraded the system to Tropical Depression 16W during the next day after its convective structure had slightly improved despite the system located in moderate to strong wind shear. By July 31, the JMA followed suit on classifying the system as a tropical depression. 16W's center late became exposed with deep convection displaced due to continued shear. Originally, the system was forecast to reach tropical storm intensity with only 35 knot winds, but the system's center had become asymmetric with a fully sheared center. The JTWC issued their final advisory on 21:00 UTC of the same day, after 16W had fully transitioned into a subtropical cyclone, though both agencies continued to track the system until August 2.

Typhoon Shanshan

Typhoon (JMA)
Category 2 typhoon (SSHWS)
 
DurationAugust 2 – August 10
Peak intensity130 km/h (80 mph) (10-min);
970 hPa (mbar)
Main article: Typhoon Shanshan (2018)

A tropical depression developed east-northeast of Guam on August 2. At 21:00 UTC on the same day, the JTWC began tracking the system, giving it the identifier 17W. 17W intensified into a tropical storm on August 3, with the JMA assigning it the name Shanshan. The storm was located over a favorable environment as the system was gradually consolidating, and it intensified into a severe tropical storm on August 3. During the next day, both the JMA and JTWC upgraded Shanshan to a typhoon after deep convection was seen wrapping into its developing center. The JMA later analysed that the storm had peaked in intensity with 10-minute winds of 130 km/h (81 mph) and a minimum pressure of 970 hPa, remaining that intensity for several days. The JTWC stated that Shanshan had slightly weakened after a strengthening trend by August 6 after its eye became ragged and slightly displaced. On August 7, Shanshan began to re-intensify and reached its peak strength as a Category 2 typhoon with 1-minute winds of 165 km/h (103 mph) while nearing southeastern Japan. Thereafter, Shanshan began to change its course towards the east as it rapidly weakened. The JTWC issued their final advisory on August 9, though the JMA tracked the system until it became extratropical at 06:00 UTC on August 10.

Losses in Miyagi Prefecture were counted at ¥96.2 million (US$866,000).

Tropical Storm Yagi (Karding)

Tropical storm (JMA)
Tropical storm (SSHWS)
 
DurationAugust 6 – August 15
Peak intensity75 km/h (45 mph) (10-min);
990 hPa (mbar)
Main article: Tropical Storm Yagi (2018)

A tropical disturbance had persisted towards the southwest of Iwo To on August 1. After the course of five days, the system was upgraded into a tropical depression by the JMA, with the JTWC following suit several hours later, designating it as 18W. The PAGASA also began issuing bulletins on the system, assigning it the local name Karding. Karding maintained its intensity as a tropical depression due to moderate to strong easterly shear despite persistent convection surrounding the system. By August 8, a METOP-A ASCAT image showed that the system had winds of 35 knots, which prompted the JTWC to upgrade it to a tropical storm. The JMA around the same time did the same, assigning it the name Yagi. Within the next day, Yagi curved towards the northwest, struggling to intensify due to wind shear. At 12:00 UTC on August 11, the JMA estimated that Yagi reached its peak strength with 10-minute winds of 75 km/h (47 mph) and a minimum pressure of 990 hPa.

The JTWC declared that Yagi reached winds of 85 km/h (53 mph) at 12:00 UTC on August 12 after the storm had consolidated further with an improved structure. Yagi made landfall shortly thereafter over Wenling, in Taizhou of Zhejiang, China, at around 23:35 CST (15:35 UTC) on August 12. By 21:00 UTC of that day, the JTWC issued their final advisory on Yagi, though they continued to track it until it weakened further into a tropical depression early on August 13. The JMA did the same on 06:00 UTC of August 13. The JMA tracked Yagi until it became an extratropical system on August 15.

Despite not making landfall on the Philippines, the storm enhanced the southwest monsoon which brought extreme flooding to many regions within the country. According to the NDRRMC, 5 people died along with ₱996 million (US$19 million) worth of damages. In East China, Yagi killed a total of 3 people and total damages were counted to be CN¥2.51 billion (US$367 million).

Tropical Storm Bebinca

Tropical storm (JMA)
Tropical storm (SSHWS)
 
DurationAugust 9 – August 17
Peak intensity85 km/h (50 mph) (10-min);
985 hPa (mbar)
Main article: Tropical Storm Bebinca (2018)

On August 9, a tropical depression formed within the South China Sea. The system remained weak and remained stationary for a few days until the JTWC began tracking the system, giving it the designation 20W on August 12. On the next day, the JMA upgraded the system to a tropical storm, naming it Bebinca. The JTWC followed suit nine hours later as deep convection flared near its compact center. Despite consistent convection along with warm sea-surface temperatures, Bebinca remained weak for the next few days due to strong shear. By August 16, however, Bebinca began to undergo a phase of rapid intensification as its center was obscured by a central dense overcast, which resulted in the JMA briefly upgrading Bebinca to a severe tropical storm, though in post-analysis it was downgraded to a tropical storm. The JTWC analysed a few hours later that the system had reached peak intensity with 1-minute winds of 110 km/h (68 mph). After Bebinca made landfall, the system rapidly weakened and both agencies issued their final warnings on August 17, with the system fully dissipating on the same day.

Bebinca killed a total of 6 people, and total economic losses in South China were counted to be ¥2.31 billion (US$333 million). 13 people lost their lives in Vietnam and total damages were counted to be 786.55 billion (US$33.7 million).

Severe Tropical Storm Leepi

Severe tropical storm (JMA)
Category 1 typhoon (SSHWS)
 
DurationAugust 10 – August 15
Peak intensity95 km/h (60 mph) (10-min);
994 hPa (mbar)

On August 10, a tropical depression formed near the Mariana Islands, assigning the depression as 19W and on the next day at 12:00 UTC, the JMA upgraded it to a tropical storm, assigning it the name Leepi. By August 13, Leepi began to threaten Japan, and on August 14, Leepi intensified into a severe tropical storm, with the JTWC upgrading it to a Category 1 equivalent typhoon. Shortly before 03:00 JST (18:00 UTC) on August 15, Leepi made landfall over Hyūga, Miyazaki in Japan. Leepi was downgraded into a tropical depression and dissipated on August 15, though its remnants were still noted near Russia.

Tropical Storm Hector

Tropical storm (JMA)
Tropical storm (SSHWS)
 
DurationAugust 13 (Entered basin) – August 16
Peak intensity75 km/h (45 mph) (10-min);
998 hPa (mbar)
Main article: Hurricane Hector (2018)

On August 13 at 18:00 UTC, both the JMA and the JTWC declared that Tropical Storm Hector has crossed the International Date Line and entered the West Pacific basin from the East Pacific basin. At this point, Hector was still located in a favorable environment with only moderate shear, though deep convection was limited as it only persisted just near its center. Due to an upper tropospheric trough cell located to the west of Hector, the storm failed to intensify and began to weaken. The JTWC downgraded Hector to a tropical depression after the system rapidly entered an area of high vertical wind shear. By the early hours of August 15, both agencies issued their final warnings on Hector, mentioning that Hector's low-level circulation had become elongated and that the storm already transitioned into a subtropical cyclone. The JMA, however, continued to monitor the system until 00:00 UTC on August 17.

Tropical Storm Rumbia

Tropical storm (JMA)
Tropical storm (SSHWS)
 
DurationAugust 14 – August 18
Peak intensity85 km/h (50 mph) (10-min);
985 hPa (mbar)
Main article: Tropical Storm Rumbia

On August 15, a tropical depression in the East China Sea intensified into a tropical storm, being given the name Rumbia by the JMA. Shortly after reaching peak intensity over the Hangzhou Bay on August 16, Rumbia made landfall over Pudong New Area, Shanghai, China at around 04:05 CST on August 17 (20:05 UTC), becoming the third tropical storm to hit Shanghai in 2018.

Rumbia killed a total of 53 people in East China and total economic losses were counted to be CN¥36.91 billion (US$5.36 billion). Shouguang received 174.7 mm (6.88 in) of rain and was particularly hard-hit, with 10,000 homes destroyed and 13 people killed. The city is regarded as the nation's greatest producer of vegetables and agriculture suffered tremendous losses; 200,000 greenhouses sustained damage. Upstream on the Mi River rainfall reached 241.6 mm (9.51 in) and caused significant flooding. Water levels at three reservoirs rose dangerously high, prompting officials to release excess water to avoid collapse. The resulting increase downstream exacerbated the flooding in Shouguang. The extratropical remnants of Rumbia were last tracked northeast of Hokkaido before dissipating off the coast of the Russian Far East.

Typhoon Soulik

Very strong typhoon (JMA)
Category 3 typhoon (SSHWS)
 
DurationAugust 15 – August 24
Peak intensity155 km/h (100 mph) (10-min);
950 hPa (mbar)
Main article: Typhoon Soulik (2018)

A low-pressure area in the Philippine Sea organized into a tropical depression late on August 15. The JTWC followed suit at 00:00 UTC at August 16 and was designated as 22W. Later on that day, the JMA upgraded 22W to tropical storm and it was given the international name Soulik. On August 17, JMA upgraded Soulik to a typhoon, marking the sixth typhoon of the season. Then Soulik rapidly intensified onto a severe typhoon, and on the next day, Soulik reached its peak intensity, with winds of 165 km/h (103 mph), and remained that intensity for several days. It also began to display some annular characteristics. After passing the Ryukyu Islands early on 22 August, the storm gradually weakened due to low sea-surface temperatures. On August 23, Soulik made landfall over Haenam County, South Jeolla Province of South Korea at around 23:00 KST (14:00 UTC).

Total damage in South Korea were at 50.7 billion (US$45 million). Economic loss in Northeast China were counted to be CN¥550 million (US$79.9 million). Flooding in North Korea triggered by Soulik killed 86 people.

Typhoon Cimaron

Very strong typhoon (JMA)
Category 4 typhoon (SSHWS)
 
DurationAugust 17 – August 24
Peak intensity155 km/h (100 mph) (10-min);
950 hPa (mbar)
Main article: Typhoon Cimaron (2018)

On August 17, a tropical depression formed near the Marshall Islands. It was named Tropical Storm Cimaron a day later. Soon after, it was upgraded to a Severe Tropical Storm. Cimaron gradually intensified over the course from August 20–22. Typhoon Cimaron threatened Southern Japan, at the same time as Typhoon Soulik ravaged the area. Typhoon Cimaron intensified to reach its peak intensity at Category 4 severe typhoon with 130 mph winds before its landfall on Japan on August 23 over the southern part of Tokushima Prefecture, Japan at around 21:00 JST (12:00 UTC). Typhoon Cimaron emerged off the north coast as a weak tropical storm, before becoming extratropical and headed into Northern Japan again. Cimaron was a significant Category 4 storm, and the 12th typhoon to strike Japan in 2018 and was surpassed by Typhoon Jebi a month later. Then, it made landfall over Himeji, Hyōgo Prefecture shortly before 24:00 JST (15:00 UTC).

Agricultural damage in Kyoto, Wakayama and Shiga Prefecture were about JP¥3.41 billion (US$30.6 million).

Tropical Depression 24W (Luis)

Tropical depression (JMA)
Tropical depression (SSHWS)
 
DurationAugust 21 – August 26
Peak intensity55 km/h (35 mph) (10-min);
996 hPa (mbar)

A tropical depression formed at the South China Sea near Taiwan. Despite entering an area of high wind shear, the system was in a favorable environment, so the JTWC and the PAGASA followed suit, with the JTWC naming it 24W, and the PAGASA named it Luis. 24W then made landfall over Fujian, China shortly after 08:00 CST (00:00 UTC) on August 25, and degenerated into a low-pressure area on next day. The JMA would continue monitoring the system until the next day.

Tropical Depression 24W killed 7 people and caused NT$1.022 billion (US$34 million) of damage in Taiwan.

Typhoon Jebi (Maymay)

Violent typhoon (JMA)
Category 5 super typhoon (SSHWS)
 
DurationAugust 26 – September 4
Peak intensity195 km/h (120 mph) (10-min);
915 hPa (mbar)
Main article: Typhoon Jebi (2018)

A low-pressure system formed near the Marshall Islands on early August 25, developing and being upgraded to a tropical depression on August 27 by the Japan Meteorological Agency (JMA). There was a persistent deep convection in the system which lead to the upgrade to a tropical storm by the JMA and was given the name 'Jebi'. On August 29, the storm abruptly underwent rapid intensification and became the third super typhoon and the second category 5 of the season. On September 4, a weakened but still powerful Jebi made landfall over the southern part of Tokushima Prefecture at around 12:00 JST (03:00 UTC) before moving over Osaka Bay and making another landfall at around Kobe, Hyōgo Prefecture at around 14:00 JST (05:00 UTC). Osaka was hit badly with a maximum wind gust of 209 km/h recorded at Kansai International Airport and 171 km/h at Osaka city's weather station, where the minimum sea level pressure (962 mb) was the lowest since 1961's record of 937 mb (Typhoon Nancy) and the fifth lowest on record. A 3.29 metre storm surge led to flooding along the Osaka Bay, including Kansai International Airport, where the runways were flooded and some airport facilities were damaged by wind and water. Osaka's iconic Universal Studios Japan was also closed during the event of the typhoon. Wakayama also recorded a maximum wind gust of 207 km/h. Jebi then moved over Kyoto which wrecked more havoc. Multiple shrines were closed during the duration of the typhoon. Kyoto Station received a lot of damage, the glass above the atrium covering the central exit, shops and hotel, collapsed, narrowly missing a few by centimeters. The typhoon ultimately emerged into the Sea of Japan shortly after 15:00 JST (06:00 UTC). Simultaneously, a cold front formed southwest of the typhoon, initiating the beginning of an extratropical transition on September 4. On September 5, after JTWC issued a final warning at 00:00 JST (15:00 UTC), Jebi was downgraded to a severe tropical storm at 03:00 JST (18:00 UTC) when it was located near the Shakotan Peninsula of Hokkaido. The storm completely transitioned into a storm-force extratropical cyclone off the coast of Primorsky Krai, Russia shortly before 10:00 VLAT (09:00 JST, 00:00 UTC). Later, the extratropical cyclone moved inland. The terrain of Khabarovsk Krai contributed to the steadily weakening trend as the system moved inland northwestward and then northward; extratropical low passed northeast of Ayan early on September 7. Jebi's extratropical remnant continued northward and then turned northeastward, before dissipating early on September 9 over the Arctic Ocean.

Jebi was the strongest storm to hit Japan since Typhoon Yancy of 1993. In total, Jebi killed 17 people and inflicted around US$15 billion. 11 deaths were reported from Japan and 6 deaths were reported from Taiwan.

Typhoon Mangkhut (Ompong)

Violent typhoon (JMA)
Category 5 super typhoon (SSHWS)
 
DurationSeptember 6 – September 17
Peak intensity205 km/h (125 mph) (10-min);
905 hPa (mbar)
Main article: Typhoon Mangkhut

On September 6, a tropical depression formed near the Marshall Islands. However, operationally, the Japan Meteorological Agency (JMA) did not initiate advisories on the system until September 7. The JTWC followed suit at 03:00 UTC on September 7, and classified the system as Tropical Depression 26W. Late on the same day, the system strengthened into a tropical storm, and the JMA named the system Mangkhut. By September 11, Mangkhut became a typhoon, and made landfall on the islands of Rota, Northern Mariana Islands. On September 12, at 3 pm Philippine Standard Time, Mangkhut entered the PAR as a Category 5 super typhoon, and accordingly, PAGASA named the storm Ompong. The JTWC noted additional strengthening on September 12, and assessed Mangkhut to have reached its peak intensity at 18:00 UTC, with maximum one-minute sustained winds of 285 km/h (177 mph). On September 13, the Philippine Government initiated evacuations for residents in the typhoon's expected path. Late on September 14, Mangkhut made landfall on the Philippines as a Category 5-equivalent super typhoon, with 1-minute sustained winds of 165 miles per hour (266 km/h). While moving inland, Mangkhut weakened into a strong Category 4-equivalent super typhoon, and soon weakened further into a Category 2 typhoon. A large eye then appeared and the system slowly strengthened into a Category 3 typhoon, as the storm moved over Hong Kong. As Mangkhut made its final landfall, it weakened into a weak Category 1 typhoon and maintained its intensity inland with deep convection, before subsequently weakening further. Late on September 17, Mangkhut dissipated over Guangxi, China.

Hong Kong Observatory initiated Hurricane Signal No. 10 around 09:40 HKT (00:40 UTC), the first time since Typhoon Hato of the previous year. As of September 23, at least 134 fatalities have been attributed to Mangkhut, including 127 in the Philippines, 6 in mainland China, and 1 in Taiwan. As of October 5, the NDRRMC estimated that Mangkhut caused 33.9 billion (US$627 million) in damages in the Philippines, with assessments continuing.

Tropical Storm Barijat (Neneng)

Tropical storm (JMA)
Tropical storm (SSHWS)
 
DurationSeptember 8 – September 13
Peak intensity75 km/h (45 mph) (10-min);
998 hPa (mbar)
Main article: Tropical Storm Barijat (2018)

On September 8, a tropical depression formed near Batanes in the Philippines. The storm was named Tropical Depression Neneng by PAGASA, with Batanes placed under TCWS #1. By the next day, Neneng exited the PAR and became a tropical storm, with the JMA assigning the name Barijat to the storm, while TCWS were raised in the absence of the storm. Over the next 2 days, Tropical Storm Barijat moved westward across the South China Sea, reaching its peak intensity with 10-minute maximum sustained wind speeds of 85 km/h on the night of September 11. On September 13, Tropical Storm Barijat (Neneng) made landfall on the Leizhou Peninsula, near the area where Tropical Storm Son-tinh (Henry) had made landfall 2 months ago, before making a second landfall on northern Vietnam later on the same day. During the evening of September 13, Barijat became a remnant low, dissipating on the next day.

Tropical Storm Barijat made a dozen landslides over Batanes, which increased the risk of major landslides and major flooding in the saturated soil influenced by this storm and later by Mangkhut (Ompong). No deaths were reported throughout its path, however, damages in China were at ¥50 million (US$7.3 million).

Typhoon Trami (Paeng)

Violent typhoon (JMA)
Category 5 super typhoon (SSHWS)
 
DurationSeptember 20 – October 1
Peak intensity195 km/h (120 mph) (10-min);
915 hPa (mbar)
Main article: Typhoon Trami (2018)

On September 19, the NRL began to monitor a large tropical disturbance that formed near Chuuk in the Federated States of Micronesia. The system drifted westwards and strengthened into a tropical depression on September 20 according to the JMA, while the JTWC issued a TCFA. Trami managed to find itself in favorable conditions for strengthening and on September 21, it gained tropical storm status and was named Trami. On September 22, Trami still strengthened and became a Severe Tropical Storm before strengthening to a Category 1 typhoon. On September 23, Trami, yet again in favorable conditions, continued to strengthen and became a Category 3-equivalent typhoon while undergoing an eyewall replacement cycle at the same time. Early on September 24, Trami strengthened further and attained Category 4 super typhoon status once it finished its eyewall replacement cycle. At 18:00 UTC on September 24, Trami strengthened even further and subsequently became a Category 5 super typhoon. On its route to Okinawa, Japan, Trami slowed down considerably and was almost stationary before moving north-northeastward. During this period of time, another eyewall replacement cycle that eventually failed later on, coupled with decreasing sea surface temperatures, started to slowly weaken Trami, although it still remained an organized storm. On September 30, Trami reached the most organized point of its duration after its peak, but Trami's structure started to deteriorate afterward, and the storm's winds gradually dropped as Trami resumed weakening. The typhoon made landfall over Tanabe, Wakayama Prefecture at around 20:00 JST (11:00 UTC) on September 30 as a Category 2-equivalent typhoon. The storm's structure deteriorated rapidly after landfall, and the JMA issued their last advisory on Trami on October 1. After Trami impacted Honshu, it completely transitioned into a hurricane-force extratropical cyclone and impacted the Kuril Islands and weakened to a storm-force system. Its extratropical remnants were last tracked in the Bering Sea, near the Aleutian Islands.

Agricultural damage in Japan were at ¥61.65 billion (US$542 million).

Tropical Depression 29W

Tropical depression (JMA)
Tropical depression (SSHWS)
 
DurationSeptember 25 – September 27
Peak intensity55 km/h (35 mph) (10-min);
1008 hPa (mbar)

On September 25, a tropical depression formed from the remnant energy of Hurricane Olivia to the southeast of Japan. The JTWC gave the system the designation 29W on the next day. However, Tropical Depression 29W remained a weak system, and developed an exposed low-level circulation center later that day. Afterward, the tropical depression accelerated northward and then north-northeastward, until it was eventually absorbed into a developing extratropical cyclone east of Japan on September 27.

Typhoon Kong-rey (Queenie)

Violent typhoon (JMA)
Category 5 super typhoon (SSHWS)
 
DurationSeptember 28 – October 6
Peak intensity215 km/h (130 mph) (10-min);
900 hPa (mbar)
Main article: Typhoon Kong-rey (2018)

In late September, a tropical disturbance formed in the waters near Pohnpei Island in the Federated States of Micronesia. The Joint Typhoon Warning Center also gave the storm, Invest 94W, a low chance of development. Over the next couple of days, the system moved westward and organized into a tropical depression on September 27, and the JMA initiated advisories on the storm, while the JTWC issued a TCFA. On September 28, the JTWC designated the system as 30W, while the JMA issued a gale warning for the system. As Tropical Depression 30W continued strengthening, the system became a tropical storm and was named Kong-rey by the JMA. On September 29, the system moved further west, found itself in favorable conditions for strengthening, and became a tropical storm. Later that day, Kong-rey strengthened into a severe tropical storm, and on September 30, the storm attained typhoon status at 03:00 UTC. Kong-rey continued strengthening, and at 18:00 UTC on October 1, Kong-rey became a Category 4-equivalent super typhoon. Early on October 2, Kong-rey strengthened into a Category 5 super typhoon. Affected by vertical wind shear, low ocean heat content and decreasing sea surface temperatures, the storm gradually weakened to a Category 3 typhoon on October 3 while undergoing an eyewall replacement cycle. Increased vertical wind shear and lower sea surface temperatures hampered Kong-rey's strength, and Kong-rey was downgraded to a tropical storm on October 4. Early on October 6, Kong-rey made landfall in Tongyeong, South Gyeongsang Province in South Korea as a high-end tropical storm, and later on the same day, Kong-rey transitioned into an extratropical cyclone, while impacting southern Hokkaido, such as areas near Hakodate.

As of October 2018, 3 people have been killed by the storm, including 2 people from South Korea. Damage nationwide totaled at 54.9 billion (US$48.5 million). Although Kong-Rey did not make a direct landfall on Kyushu and Shikoku, its outer rainbands affected the two islands. At an area in Shikoku, rain accumulated to 300 mm. In Nagasaki, more than 12,000 families lost power; in Fukuoka Prefecture, a person died because of the rain. Agricultural damage in Okinawa and Miyazaki Prefecture were about JP¥13.99 billion (US$123 million).

Unrelated to Kong-rey, Hurricane Walaka was a Category 5 hurricane at the same time Kong-rey intensified to Category 5 super typhoon intensity, marking the first time since 2005 when two tropical cyclones of Category 5 strength existed simultaneously in the Northern Hemisphere.

Typhoon Yutu (Rosita)

Violent typhoon (JMA)
Category 5 super typhoon (SSHWS)
 
DurationOctober 21 – November 3
Peak intensity215 km/h (130 mph) (10-min);
900 hPa (mbar)
Main article: Typhoon Yutu

Early on October 21, a tropical depression developed to the east of Guam and the Northern Mariana Islands, with the JMA initiating advisories on the system. Shortly afterward, the JTWC assigned the storm the identifier 31W. The system began to strengthen, becoming a tropical storm several hours later, and the JMA named the system Yutu. Favorable conditions, including low wind shear and high ocean-surface temperatures, allowed Yutu to explosively intensify on the following day, with the storm reaching severe tropical storm strength and then typhoon intensity a few hours later. From October 23 to 24, Yutu continued to organize and explosively intensify, reaching Category 5 super typhoon intensity on October 24. The typhoon continued to strengthen and displayed a healthy convective structure, while moving towards the island of Saipan. Later on the same day, Typhoon Yutu made landfall on the island of Tinian, just south of Saipan, at Category 5 intensity, with 1-minute sustained winds of 285 km/h (177 mph), becoming the most powerful storm on record to impact the northern Mariana Islands.

After making landfall on Tinian, Yutu underwent an eyewall replacement cycle, which it successfully completed on the next day, and the storm strengthened back to Category 5 super typhoon status on October 26, at 15:00 UTC.

On October 27, Yutu's eye became cloud-filled, indicative of weakening, and the storm weakened to a Category 4 super typhoon. On the same day, the storm entered PAGASA's area of responsibility, and Yutu was given the name Rosita by PAGASA. On October 28, Yutu quickly weakened, as the storm moved over ocean waters with significantly lower sea-surface heat content.

After making landfall on October 30, Yutu rapidly weakened, and when it emerged over the South China Sea, low ocean heat content and westerly wind shear caused Yutu to weaken below typhoon status. On November 2, Yutu weakened into a remnant low off the coast of China, before dissipating on the next day.

On October 25, in Saipan, the typhoon killed a woman when it destroyed the building she was staying in, and injured 133 other people, three of whom were severely injured. On Saipan and nearby Tinian, high winds from Yutu knocked down more than 200 power poles. Most of the buildings in southern Saipan lost their roofs or were destroyed, including a high school that was wrecked.

Severe Tropical Storm Usagi (Samuel)

Severe tropical storm (JMA)
Category 2 typhoon (SSHWS)
 
DurationNovember 14 – November 26
Peak intensity110 km/h (70 mph) (10-min);
990 hPa (mbar)
Main article: Tropical Storm Usagi (2018)

On November 3, the Central Pacific Hurricane Center began monitoring a disturbance that had formed in the Central Pacific basin. This disturbance soon moved out of the basin and into the West Pacific without further development on November 6. Tracking westward, the system did not organize until late on November 18, when it reached tropical depression status on the Saffir-Simpson scale. The PAGASA named the system Tropical Depression "Samuel" and issued warnings for Mindanao and Visayas. Samuel made landfall on November 20 in the Philippines, crossing the archipelago and weakening slightly. Samuel began to restrengthen over the South China Sea, and was subsequently named "Usagi". Usagi underwent rapid intensification, and became a severe tropical storm on November 21 while moving slowly. By November 22, Usagi (Samuel) intensified into a Category 1 typhoon. On November 24, Usagi weakened back to a severe tropical storm while heading to Vietnam because of the land interaction.

Usagi caused one death in the Philippines, and the agricultural damage were at 52.2 million (US$994,000). On November 25, Usagi made landfall on Mekong Delta. The typhoon caused flooding in Ho Chi Minh City and killed three people. Losses in Vietnam were at 925 billion (US$39.5 million).

Tropical Storm Toraji

Tropical storm (JMA)
Tropical depression (SSHWS)
 
DurationNovember 16 – November 18
Peak intensity65 km/h (40 mph) (10-min);
1004 hPa (mbar)
Main article: Tropical Storm Toraji (2018)

A low pressure system exited the PAR on November 15. Late on November 16, a tropical disturbance formed east of Vietnam. It slowly tracked west-northwest and strengthened into a tropical-depression strength storm early on November 17. Toraji made landfall on November 18 and quickly weakened; the remnants emerged into the Gulf of Thailand, and the remnants briefly reorganized, regaining tropical-depression strength on November 20. However, as Toraji made a second landfall on the Malay Peninsula, it weakened once more and dissipated late on November 21, due to wind shear over the Strait of Malacca.

Toraji caused flooding in Nha Trang, resulting in 20 dead and 1.24 trillion (US$53.6 million) in damages.

Typhoon Man-yi (Tomas)

Typhoon (JMA)
Category 2 typhoon (SSHWS)
 
DurationNovember 20 – November 28
Peak intensity150 km/h (90 mph) (10-min);
960 hPa (mbar)

On November 19, a tropical depression formed well east of the Philippines and intensified into a tropical storm soon thereafter, receiving the name Man-yi. After reaching typhoon status on November 21, Man-yi entered the Philippine basin and received the name Tomas from PAGASA. Shortly after, Man-yi intensified into a Category 2 typhoon. However, after completing an anticyclonic loop due to the influences of nearby weather systems, entering and exiting the PAR multiple times, Man-yi dipped to Category 1 status and moved into cooler waters. Succumbing to hostile conditions, Man-yi weakened into a tropical storm once more on November 25 and degenerated into a tropical depression by the end of the next day, while tracking northeast, and became an extratropical cyclone.

Tropical Depression 35W (Usman)

Tropical depression (JMA)
Tropical depression (SSHWS)
 
DurationDecember 25 – December 29
Peak intensity55 km/h (35 mph) (10-min);
1000 hPa (mbar)
Main article: Tropical Depression Usman

A tropical depression formed in the Philippine Sea on Christmas Day, December 25. It entered the PAR later that evening and the PAGASA named the significant tropical depression "Usman". Usman made its first landfall on Samar, Eastern Visayas on December 28. It passed over Palawan and other areas in the weekend. Usman did not survive the passage of the Philippines and degenerated into a remnant low. The remnants of 35W were absorbed by an invest on December 30 which would later become Tropical Storm Pabuk.

While passing over the Philippines, Usman brought heavy rains that caused several landslides, which killed 156 people, with damages amounting to Php5.41 billion (US$103 million).

Other systems

  • On June 4, the JMA began tracking a weak tropical depression that had formed northeast of Yap. However, the system was absorbed by a nearby tropical depression, which would eventually become Severe Tropical Storm Maliksi on the next day.
  • After Gaemi became extratropical, a tropical depression formed south of Hong Kong early on June 17, and dissipated over the east coast of Guangdong, China one day later.
  • On July 16, a tropical depression developed over the South China Sea. The system remained weak and moved into Vietnam, before dissipating on the next day.
  • On August 4, the JTWC began to track a subtropical storm that had developed just west of the International Date Line; the storm subsequently became extratropical on the next day.
  • A tropical depression formed southeast of Okinawa on August 24; two days later, it made landfall over Shanghai and quickly dissipated over Jiangsu, in East China.
  • The remnants of Hurricane Olivia entered the basin on September 19, and redeveloped into a tropical depression on September 21, while slowly drifting westward. Two days later, it degenerated into a remnant low again, as the JMA reported the system's dissipation. On September 25, the system's remnant energy developed into Tropical Depression 29W.
  • On October 19, the JMA began tracking a tropical depression in the Gulf of Thailand. On October 20, the tropical depression made landfall on the Malay Peninsula and weakened into a remnant low, before moving out of the basin.
  • A tropical depression formed over the southern portion of the South China Sea on December 31, with the JTWC designation 36W. The system intensified into Tropical Storm Pabuk on January 1, 2019, becoming the first named storm of the 2019 Pacific typhoon season.

Storm names

See also: Tropical cyclone naming, List of historical tropical cyclone names, and 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. The Japan Meteorological Agency's RSMC Tokyo – Typhoon Center assigns international names to tropical cyclones on behalf of the World Meteorological Organization's Typhoon Committee, should they be judged to have 10-minute sustained windspeeds of 65 km/h (40 mph). PAGASA names 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 are retired, by both PAGASA and the Typhoon Committee. Should the list of names for the Philippine region be exhausted then names will be taken from an auxiliary list of which the first ten are published each season. Unused names are marked in gray.

International names

Main article: List of retired Pacific typhoon names

During the season 29 tropical storms developed in the Western Pacific and 28 were named by the JMA, when the system was judged to have 10-minute sustained windspeeds of 65 km/h (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. During the season, the names Ampil, Jongdari and Barijat were used for the first time, after they replaced the names Bopha, Sonamu and Utor which were all retired after the 2012 and 2013 seasons respectively.

Bolaven Sanba Jelawat Ewiniar Maliksi Gaemi Prapiroon Maria Son-Tinh Ampil Wukong Jongdari Shanshan Yagi
Leepi Bebinca Rumbia Soulik Cimaron Jebi Mangkhut Barijat Trami Kong-rey Yutu Toraji Man-yi Usagi
  • Additionally, Hector entered the Western Pacific basin from the Central Pacific basin after crossing the International Date Line (180°E) as a tropical cyclone. As the system crossed between basins intact, it retained the name assigned to it by the National Hurricane Center.

Retirement

After the season, the Typhoon Committee announced that the names Rumbia, Mangkhut, and Yutu were removed from the naming lists due to the damages and deaths it caused in their respective onslaughts, and they will never be used again for another typhoon name. In 2020, they were replaced with Pulasan, Krathon, and Yinxing, respectively.

Philippines

Main article: List of retired Philippine typhoon names
Agaton Basyang Caloy Domeng Ester
Florita Gardo Henry Inday Josie
Karding Luis Maymay Neneng Ompong
Paeng Queenie Rosita Samuel Tomas
Usman Venus (unused) Waldo (unused) Yayang (unused) Zeny (unused)
Auxiliary list
Agila (unused) Bagwis (unused) Chito (unused) Diego (unused) Elena (unused)
Felino (unused) Gunding (unused) Harriet (unused) Indang (unused) Jessa (unused)

During the season PAGASA used its own naming scheme for the 21 tropical cyclones, that either developed within or moved into their self-defined area of responsibility. This is the same list used from the 2014 season, except for the names Gardo, Josie, Maymay, Rosita, and Samuel, which replaced Glenda, Jose, Mario, Ruby, and Seniang. All five names, as well as Usman, were used for the first time (and only, in the cases of Rosita and Usman).

Retirement

After the season, the names Ompong, Rosita and Usman were retired, as they caused at least ₱1 billion in damages. They were replaced with Obet, Rosal and Umberto for the 2022 season.

Season effects

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 2018. The tables also provide an overview of a systems intensity, duration, land areas affected and any deaths or damages associated with the system.

Name Dates Peak intensity Areas affected Damage
(USD)
Deaths Refs
Category Wind speed Pressure
Bolaven (Agaton) December 29, 2017 – January 4, 2018 Tropical storm 65 km/h (40 mph) 1,002 hPa (29.6 inHg) Philippines, Vietnam $10.5 million 4
Sanba (Basyang) February 8 – 16 Tropical storm 65 km/h (40 mph) 1,000 hPa (30 inHg) Caroline Islands, Philippines $3.19 million 15
Jelawat (Caloy) March 24 – April 1 Violent typhoon 195 km/h (121 mph) 915 hPa (27.0 inHg) Caroline Islands, Mariana Islands Unknown 2
04W May 10 – 15 Tropical depression Not specified 1,008 hPa (29.8 inHg) None None None
Ewiniar June 2 – 9 Tropical storm 75 km/h (47 mph) 998 hPa (29.5 inHg) Vietnam, Philippines, South China, Taiwan, Ryukyu Islands $784 million 14
Maliksi (Domeng) June 3 – 11 Severe tropical storm 110 km/h (68 mph) 970 hPa (29 inHg) Ryukyu Islands, Philippines, Honshu None 2
TD June 4 – 5 Tropical depression Not specified 1,006 hPa (29.7 inHg) Guam None None
07W June 13 – 15 Subtropical storm 65 km/h (40 mph) 993 hPa (29.3 inHg) Taiwan, Ryukyu Islands None None
Gaemi (Ester) June 13 – 16 Tropical storm 85 km/h (53 mph) 990 hPa (29 inHg) Taiwan, Ryukyu Islands None 3
TD June 17 – 18 Tropical depression Not specified 998 hPa (29.5 inHg) South China None None
Prapiroon (Florita) June 28 – July 4 Strong typhoon 120 km/h (75 mph) 960 hPa (28 inHg) Japan, Korean Peninsula $10.1 million 4
Maria (Gardo) July 3 – 12 Violent typhoon 195 km/h (121 mph) 915 hPa (27.0 inHg) Mariana Islands, Ryukyu Islands, Taiwan, East China $637 million 2
Son-Tinh (Henry) July 16 – 24 Tropical storm 75 km/h (47 mph) 994 hPa (29.4 inHg) Philippines, South China, Vietnam, Laos, Thailand, Myanmar $323 million 173
TD July 16 – 17 Tropical depression Not specified 998 hPa (29.5 inHg) South China, Vietnam, Laos $14.9 million None
Ampil (Inday) July 17 – 24 Severe tropical storm 95 km/h (59 mph) 985 hPa (29.1 inHg) Ryukyu Islands, China, Russian Far East $246 million 1
13W (Josie) July 20 – 23 Tropical depression 55 km/h (34 mph) 996 hPa (29.4 inHg) Philippines, Taiwan, Ryukyu Islands, East China $87.4 million 16
Wukong July 22 – 26 Severe tropical storm 95 km/h (59 mph) 990 hPa (29 inHg) None None None
Jongdari July 23 – August 4 Strong typhoon 140 km/h (87 mph) 960 hPa (28 inHg) Japan, East China $1.48 billion None
16W July 31 – August 1 Tropical depression 55 km/h (34 mph) 1,002 hPa (29.6 inHg) None None None
Shanshan August 2 – 10 Strong typhoon 130 km/h (81 mph) 970 hPa (29 inHg) Mariana Islands, Japan $866,000 None
Yagi (Karding) August 6 – 15 Tropical storm 75 km/h (47 mph) 990 hPa (29 inHg) Philippines, Taiwan, Ryukyu Islands, China $365 million 7
Bebinca August 9 – 17 Tropical storm 85 km/h (53 mph) 985 hPa (29.1 inHg) South China, Vietnam, Laos, Thailand, Myanmar $391 million 19
Leepi August 10 – 15 Severe tropical storm 95 km/h (59 mph) 994 hPa (29.4 inHg) Japan, South Korea None None
Hector August 13 – 16 Tropical storm 75 km/h (47 mph) 998 hPa (29.5 inHg) None None None
Rumbia August 14 – 19 Tropical storm 85 km/h (53 mph) 985 hPa (29.1 inHg) Ryukyu Islands, China, Korean Peninsula, Russian Far East $5.36 billion 53
Soulik August 15 – 24 Very strong typhoon 155 km/h (96 mph) 950 hPa (28 inHg) Caroline Islands, Mariana Islands, Northeast China, Japan, Korean Peninsula, Russian Far East, Alaska $125 million 86
Cimaron August 16 – 24 Very strong typhoon 155 km/h (96 mph) 950 hPa (28 inHg) Marshall Islands, Mariana Islands, Japan, Aleutian Islands $30.6 million 3
24W (Luis) August 21 – 26 Tropical depression 55 km/h (34 mph) 994 hPa (29.4 inHg) Taiwan, East China $34 million 7
TD August 24 – 26 Tropical depression Not specified 1,002 hPa (29.6 inHg) Ryukyu Islands, East China None None
Jebi (Maymay) August 26 – September 4 Violent typhoon 195 km/h (121 mph) 915 hPa (27.0 inHg) Mariana Islands, Taiwan, Japan, Russian Far East, Arctic $13 billion 21
TD September 5 – 8 Tropical depression 55 km/h (34 mph) 1,004 hPa (29.6 inHg) Ryukyu Islands None None
Mangkhut (Ompong) September 6 – 17 Violent typhoon 205 km/h (127 mph) 905 hPa (26.7 inHg) Marshall Islands, Mariana Islands, Taiwan, Philippines, Hong Kong, Macau, South China, Vietnam $3.77 billion 134
Barijat (Neneng) September 8 – 13 Tropical storm 75 km/h (47 mph) 998 hPa (29.5 inHg) Philippines, Taiwan, South China, Vietnam $7.3 million None
Trami (Paeng) September 20 – October 1 Violent typhoon 195 km/h (121 mph) 915 hPa (27.0 inHg) Mariana Islands, Taiwan, Japan, Russian Far East, Alaska $2.69 billion 4
TD September 21 – 22 Tropical depression Not specified 1,006 hPa (29.7 inHg) None None None
29W September 25 – 27 Tropical depression 55 km/h (34 mph) 1,008 hPa (29.8 inHg) None None None
Kong-rey (Queenie) September 28 – October 6 Violent typhoon 215 km/h (134 mph) 900 hPa (27 inHg) Caroline Islands, Mariana Islands, Japan, Taiwan, Korean Peninsula, Alaska $172 million 3
TD October 19 – 20 Tropical depression Not specified 1,008 hPa (29.8 inHg) Vietnam, Cambodia, Thailand, Myanmar None None
Yutu (Rosita) October 21 – November 2 Violent typhoon 215 km/h (134 mph) 900 hPa (27 inHg) Caroline Islands, Mariana Islands, Philippines, South China, Taiwan $854 million 30
Usagi (Samuel) November 14 – 26 Severe tropical storm 110 km/h (68 mph) 990 hPa (29 inHg) Caroline Islands, Philippines, Vietnam, Cambodia, Laos $40.5 million 4
Toraji November 16 – 18 Tropical storm 65 km/h (40 mph) 1,004 hPa (29.6 inHg) Vietnam, Thailand, Malaysia $53.6 million 32
Man-yi (Tomas) November 20 – 28 Strong typhoon 150 km/h (93 mph) 960 hPa (28 inHg) Caroline Islands, Alaska None None
35W (Usman) December 25 – 29 Tropical depression 55 km/h (34 mph) 1,000 hPa (30 inHg) Palau, Philippines $103 million 156
Season aggregates
43 systems December 29, 2017 –
December 29, 2018
215 km/h (134 mph) 900 hPa (27 inHg) $30.5 billion 793

See also

Notes

References

  1. ^ Saunders, Mark; Lea, Adam (May 11, 2018). Extended Range Forecast for Northwest Pacific Typhoon Activity in 2018 (PDF) (Report). Tropical Storm Risk Consortium. Retrieved May 11, 2018.
  2. ^ Saunders, Mark; Lea, Adam (July 6, 2018). July Forecast Update for Northwest Pacific Typhoon Activity in 2018 (PDF) (Report). Tropical Storm Risk Consortium. Retrieved July 6, 2018.
  3. ^ Saunders, Mark; Lea, Adam (August 7, 2018). August Forecast Update for Northwest Pacific Typhoon Activity in 2018 (PDF) (Report). Tropical Storm Risk Consortium. Retrieved August 7, 2018.
  4. ^ Malano, Vicente B (January 15, 2018). January–June 2018 (Seasonal Climate Outlook). Philippine Atmospheric Geophysical and Astronomical Services Administration. Archived from the original on 2017-01-29. Retrieved January 18, 2017.
  5. ^ "Central region vulnerable to typhoons in 2018". Vietnam News. March 15, 2018.
  6. ^ Chi-ming, Shun (March 23, 2018). "Director of the Hong Kong Observatory highlights Observatory's latest developments". Hong Kong Observatory. Archived from the original on March 26, 2018. Retrieved March 26, 2018.
  7. ^ July–December 2018 Malano, Vicente B (July 13, 2018). July–December 2018 (Seasonal Climate Outlook). Philippine Atmospheric Geophysical and Astronomical Services Administration. Archived from the original on 2017-01-29. Retrieved 2018-01-01.
  8. Griffiths, James (14 September 2018). "Philippines lashed by Typhoon Mangkhut, strongest storm this year". Cable News Network. Archived from the original on 15 September 2018. Retrieved 22 September 2018.
  9. "Marine Weather Warning for GMDSS Metarea XI 2017-12-30T06:00:00Z". WIS Portal – GISC Tokyo. Japan Meteorological Agency. December 30, 2017. Retrieved December 30, 2017.
  10. Jhoanna Ballaran (January 1, 2018). "Storm Signal No. 1 raised in several areas as LPA turns into depression". Inquirer. Archived from the original on January 2, 2018. Retrieved February 16, 2018.
  11. "Tropical Depression 01W (One) Warning Nr 001". Joint Typhoon Warning Center. January 1, 2018. Archived from the original on May 24, 2024.
  12. ^ "Tropical Depression Agaton makes 6th landfall in Palawan". Rappler. January 2, 2018. Retrieved May 16, 2020.
  13. "Tropical Depression 01W (Bolaven) Warning Nr 010". Joint Typhoon Warning Center. January 4, 2018. Archived from the original on May 24, 2024.
  14. "More than 2,000 passengers stranded due to 'Agaton'". Sunstar Philippines. January 2, 2018. Archived from the original on January 5, 2018. Retrieved February 16, 2018.
  15. ^ "SitRep No. 13 re Preparedness Measures and Effects of Tropical Depression "AGATON"" (PDF). January 22, 2018. Archived (PDF) from the original on February 9, 2018. Retrieved January 22, 2018.
  16. "Tropical Storm Basyang makes landfall in Surigao del Sur". 13 February 2018. Archived from the original on 2018-02-13. Retrieved 2018-04-08.
  17. "Philippines: Tropical Storm Sanba makes landfall February 13 /update 1".
  18. "'Basyang' weakens after pounding Surigao". February 13, 2018. Archived from the original on April 8, 2018. Retrieved April 8, 2018.
  19. SitRep No. 11 re Preparedness Measures and Effects for Tropical Storm "BASYANG" (I.N. SANBA) (PDF) (Report). National Disaster Risk Reduction and Management Council. February 23, 2018. Archived (PDF) from the original on October 12, 2018. Retrieved February 26, 2018.
  20. ^ "SitRep No. 11 re Preparedness Measures and Effects for Tropical Storm "BASYANG"" (PDF). February 23, 2018. Archived (PDF) from the original on October 12, 2018. Retrieved September 10, 2018.
  21. "6yAE5Nl2l". Archived from the original on 2024-05-24. Retrieved 2018-03-24.
  22. "6yBF3lHZz". Archived from the original on 2024-05-24. Retrieved 2018-03-25.
  23. "6yBF7pyWZ". Archived from the original on 2024-05-24. Retrieved 2018-03-25.
  24. "6yCiZiQTo". Archived from the original on 2024-05-24. Retrieved 2018-03-26.
  25. "6yHP5U1lz". Archived from the original on 2024-05-24. Retrieved 2018-03-29.
  26. "6yIu7LyVR". Archived from the original on 2024-05-24. Retrieved 2018-03-30.
  27. "6yKn1AxSi". Archived from the original on 2024-05-24. Retrieved 2018-03-31.
  28. "6yKnKMxc1". Archived from the original on 2024-05-24. Retrieved 2018-03-31.
  29. "Newsletter 1QTR2019" (PDF). www.weather.gov. March 20, 2019.
  30. "FSM and RMI Program Summary" (PDF). www.usaid.gov. October 20, 2020.
  31. "Quarterly Climate Impacts and Outlook" (PDF). Retrieved 2022-12-20.
  32. Post, Meghan Swartz | The Guam Daily (4 April 2018). "Don't risk going in rough waters, expert says". The Guam Daily Post. Retrieved 2022-12-03.
  33. "Marine Weather Warning for GMDSS Metarea XI 2018-05-10T18:00:00Z". WIS Portal – GISC Tokyo. Japan Meteorological Agency. May 10, 2018. Retrieved May 11, 2018.
  34. "Tropical Cyclone Formation Alert". Joint Typhoon Warning Center. May 10, 2018. Archived from the original on May 11, 2018. Retrieved May 11, 2018.
  35. "Tropical Depression 04W (Four) Warning Nr 001". Joint Typhoon Warning Center. May 12, 2018. Archived from the original on May 24, 2024.
  36. "Prognostic Reasoning for Tropical Storm 04W (Four) Warning Nr 03". Joint Typhoon Warning Center. May 12, 2018. Archived from the original on May 24, 2024.
  37. "Prognostic Reasoning for Tropical Storm 04W (Four) Warning Nr 05". Joint Typhoon Warning Center. May 13, 2018. Archived from the original on May 24, 2024.
  38. "Tropical Depression 04W (Four) Warning Nr 008". Joint Typhoon Warning Center. May 14, 2018. Archived from the original on May 24, 2024.
  39. "Archived copy". Archived from the original on 2024-05-24. Retrieved 2018-05-15.{{cite web}}: CS1 maint: archived copy as title (link)
  40. "Marine Weather Warning for GMDSS Metarea XI 2018-06-01T18:00:00Z". WIS Portal – GISC Tokyo. Japan Meteorological Agency. June 1, 2018. Retrieved June 4, 2018.
  41. "RSMC Tropical Cyclone Advisory". Japan Meteorological Agency. June 2, 2018. Archived from the original on 2024-05-22. Retrieved June 4, 2018.
  42. "Tropical Depression 05W (Five) Warning Nr 001". Joint Typhoon Warning Center. June 2, 2018. Archived from the original on May 24, 2024.
  43. "Tropical Storm 05W (Five) Warning Nr 015". Joint Typhoon Warning Center. June 5, 2018. Archived from the original on May 24, 2024.
  44. "TS 1804 EWINIAR (1806) UPGRADED FROM TD". Japan Meteorological Agency. June 6, 2018. Archived from the original on May 24, 2024.
  45. "Tropical Storm 05W (Five) Warning Nr 023". Joint Typhoon Warning Center. June 7, 2018. Archived from the original on May 22, 2024.
  46. "TD DOWNGRADED FROM TS 1804 EWINIAR (1806)". Japan Meteorological Agency. June 9, 2018. Archived from the original on May 24, 2024.
  47. ^ CMA (December 4, 2018). Member Report: China (PDF). ESCAP/WMO Typhoon Committee. ESCAP/WMO Typhoon Committee. pp. 1–2. Archived from the original (PDF) on December 4, 2018. Retrieved December 4, 2018.
  48. ^ "RSMC Tropical Cyclone Best Track 1805 MALIKSI (1805)". Japan Meteorological Agency. July 18, 2018. Archived from the original on May 22, 2024.
  49. ^ "Tropical Cyclone Formation Alert". Joint Typhoon Warning Center. June 5, 2018. Archived from the original on June 6, 2018. Retrieved June 6, 2018.
  50. "Tropical depression Domeng enters PAR". Philstar. June 6, 2018.
  51. "Tropical Storm 06W (Maliksi) Warning Nr 001". Joint Typhoon Warning Center. June 8, 2018. Archived from the original on May 24, 2024.
  52. "Tropical Storm 06W (Maliksi) Warning Nr 010". Joint Typhoon Warning Center. June 10, 2018. Archived from the original on May 24, 2024.
  53. "TY 1805 MALIKSI (1805) UPGRADED FROM STS". Japan Meteorological Agency. June 10, 2018. Archived from the original on May 24, 2024.
  54. "Tropical Storm 06W (Maliksi) Warning Nr 015". Joint Typhoon Warning Center. June 11, 2018. Archived from the original on May 24, 2024.
  55. ^ "2 dead in aftermath of Typhoon Domeng". CNN Philippines. June 11, 2018. Archived from the original on June 12, 2018. Retrieved June 10, 2018.
  56. ^ "Tropical Storm 07W running best track". Joint Typhoon Warning Center. Archived from the original on June 14, 2018. Retrieved June 14, 2018.
  57. "Tropical Depression 07W (Seven) Warning Nr 001". Joint Typhoon Warning Center. June 13, 2018. Archived from the original on May 24, 2024.
  58. "Prognostic Reasoning for Tropical Storm 07W (Seven) Warning Nr 02". Joint Typhoon Warning Center. June 14, 2018. Archived from the original on May 24, 2024.
  59. "Tropical Storm 07W (Seven) Warning Nr 004". Joint Typhoon Warning Center. June 14, 2018. Archived from the original on May 24, 2024.
  60. ^ "SitRep No.15 Preparedness Measures&Effects of SW Monsoon by TY Domeng & TD Ester" (PDF). NDRRMC. June 19, 2018.
  61. 台風6号被害8458万 農林水産、大雨で斜面崩壊 (in Japanese). Ryūkyū Shimpō. June 28, 2018. Archived from the original on December 9, 2018. Retrieved June 30, 2018.
  62. "Marine Weather Warning for GMDSS Metarea XI 2018-06-28T00:00:00Z". WIS Portal – GISC Tokyo. Japan Meteorological Agency. June 28, 2018. Retrieved June 28, 2018.
  63. "Marine Weather Warning for GMDSS Metarea XI 2018-07-04T00:00:00Z". WIS Portal – GISC Tokyo. Japan Meteorological Agency. July 4, 2018. Retrieved July 4, 2018.
  64. "台風7号 被害報告、県の災害警戒本部会議". 琉球新報. 2018-07-05. Retrieved 2018-07-09.
  65. "台風7号 農作業中の89歳女性転落死 強風にあおられ?". 毎日新聞. 2018-07-05. Retrieved 2018-07-05.
  66. "台風7号:長崎の「潜伏キリシタン」世界文化遺産で被害". 毎日新聞. 楽天 インフォシーク ニュース. 2018-07-05. Archived from the original on 2018-07-07. Retrieved 2018-07-07.
  67. ^ "1 dead, 1 missing as Typhoon Prapiroon approaches Korea". Koreaherald. July 2, 2018. Archived from the original on July 18, 2018. Retrieved July 5, 2018.
  68. 平成30年台風第7号に係る被害状況等について(第7報)最終報 (PDF) (Report) (in Japanese). 沖縄総合事務局. July 4, 2018. Retrieved July 5, 2018.
  69. "Index of /tcdat/tc18/WPAC/10W.MARIA/ir/geo/1km". United States Naval Research Laboratory. Retrieved July 9, 2018.
  70. "Tropical Cyclone Formation Alert". WIS Portal – GISC Tokyo. Joint Typhoon Warning Center. July 2, 2018. Retrieved July 9, 2018.
  71. "Prognostic Reasoning for Tropical Depression 10W (Ten) Warning Nr 01". Joint Typhoon Warning Center. July 2, 2018. Archived from the original on October 18, 2016. Retrieved July 9, 2018.
  72. "WWJP25 RJTD 030000". Japan Meteorological Agency. July 3, 2018. Archived from the original on August 5, 2016. Retrieved July 9, 2018.
  73. "RSMC Tropical Cyclone Advisory WTPQ21 RJTD 030600". Japan Meteorological Agency. July 3, 2018. Archived from the original on October 13, 2016. Retrieved July 9, 2018.
  74. "RSMC Tropical Cyclone Advisory WTPQ21 RJTD 041200". Japan Meteorological Agency. July 4, 2018. Archived from the original on October 13, 2016. Retrieved July 9, 2018.
  75. "Prognostic Reasoning for Tropical Storm 10W (Maria) Warning Nr 08". Joint Typhoon Warning Center. July 4, 2018. Archived from the original on October 18, 2016. Retrieved July 9, 2018.
  76. "Prognostic Reasoning for Tropical Storm 10W (Maria) Warning Nr 09". Joint Typhoon Warning Center. July 4, 2018. Archived from the original on October 18, 2016. Retrieved July 10, 2018.
  77. "RSMC Tropical Cyclone Advisory WTPQ21 RJTD 050300". Japan Meteorological Agency. July 5, 2018. Archived from the original on October 13, 2016. Retrieved July 10, 2018.
  78. "Prognostic Reasoning for Typhoon 10W (Maria) Warning Nr 11". Joint Typhoon Warning Center. July 5, 2018. Archived from the original on October 18, 2016. Retrieved July 10, 2018.
  79. "RSMC Tropical Cyclone Advisory WTPQ21 RJTD 051500". Japan Meteorological Agency. July 5, 2018. Archived from the original on October 13, 2016. Retrieved July 10, 2018.
  80. "Prognostic Reasoning for Super Typhoon 10W (Maria) Warning Nr 14". Joint Typhoon Warning Center. July 6, 2018. Archived from the original on October 18, 2016. Retrieved July 10, 2018.
  81. "玛莉亚"在福建连江黄岐半岛登陆 (in Chinese). National Meteorological Center of CMA. July 11, 2018. Archived from the original on July 11, 2018. Retrieved July 11, 2018.
  82. ^ "Tropical Depression 11W (Eleven) Warning Nr 001". Joint Typhoon Warning Center. July 15, 2018. Archived from the original on May 23, 2024.
  83. "Prognostic Reasoning for Tropical Storm 11W (Son-Tinh) Warning Nr 07". Joint Typhoon Warning Center. July 17, 2018. Archived from the original on May 23, 2024.
  84. "Prognostic Reasoning for Tropical Storm 11W (Son-Tinh) Warning Nr 08". Joint Typhoon Warning Center. July 17, 2018. Archived from the original on May 23, 2024.
  85. "Prognostic Reasoning for Tropical Storm 11W (Son-Tinh) Warning Nr 12". Joint Typhoon Warning Center. July 18, 2018. Archived from the original on May 23, 2024.
  86. "Tropical Storm 11W (Son-Tinh) Warning Nr 014". Joint Typhoon Warning Center. July 19, 2018. Archived from the original on May 23, 2024.
  87. "Archived copy". Archived from the original on 2018-07-22. Retrieved 2018-07-21.{{cite web}}: CS1 maint: archived copy as title (link)
  88. ^ "At least 10 dead in Vietnam floods triggered by Typhoon Son Tinh". The New Indian Express. PTI. July 21, 2018. Retrieved July 22, 2018.
  89. "Tóm tắt các cơn bão trong năm 2018" (in Vietnamese). Government of Tuyen Quang province. January 5, 2019. Retrieved January 20, 2019.
  90. "Tropical Depression 12W (Twelve) Warning Nr 001". Joint Typhoon Warning Center. July 17, 2018. Archived from the original on May 24, 2024.
  91. "Tropical Storm 12W (Ampil) Warning Nr 005". Joint Typhoon Warning Center. July 18, 2018. Archived from the original on May 24, 2024.
  92. "Prognostic Reasoning for Tropical Storm 12W (Ampil) Warning Nr 06". Joint Typhoon Warning Center. July 19, 2018. Archived from the original on May 24, 2024.
  93. "Prognostic Reasoning for Tropical Storm 12W (Ampil) Warning Nr 08". Joint Typhoon Warning Center. July 19, 2018. Archived from the original on May 24, 2024.
  94. "Tropical Storm 12W (Ampil) Warning Nr 010". Joint Typhoon Warning Center. July 20, 2018. Archived from the original on May 24, 2024.
  95. "Prognostic Reasoning for Tropical Storm 12W (Ampil) Warning Nr 15". Joint Typhoon Warning Center. July 20, 2018. Archived from the original on May 24, 2024.
  96. "Prognostic Reasoning for Tropical Storm 12W (Ampil) Warning Nr 21". Joint Typhoon Warning Center. July 22, 2018. Archived from the original on May 24, 2024.
  97. "Tropical Depression 12W (Ampil) Warning Nr 025". Joint Typhoon Warning Center. July 23, 2018. Archived from the original on May 24, 2024.
  98. "Archived copy". Archived from the original on 2024-05-24. Retrieved 2018-07-25.{{cite web}}: CS1 maint: archived copy as title (link)
  99. ^ "SitRep No.35 SW Monsoon enhanced by TCs Son-Tinh, Ampil and 13W" (PDF). NDRRMC. August 9, 2018. Archived (PDF) from the original on August 9, 2018. Retrieved August 9, 2018.
  100. "Tropical Depression 14W (Fourteen) Warning Nr 001". Joint Typhoon Warning Center. July 21, 2018. Archived from the original on May 24, 2024.
  101. "Tropical Storm 14W (Fourteen) Warning Nr 003". Joint Typhoon Warning Center. July 22, 2018. Archived from the original on May 24, 2024.
  102. "Prognostic Reasoning for Tropical Storm 14W (Fourteen) Warning Nr 07". Joint Typhoon Warning Center. July 23, 2018. Archived from the original on May 24, 2024.
  103. "Prognostic Reasoning for Typhoon 14W (Fourteen) Warning Nr 15". Joint Typhoon Warning Center. July 25, 2018. Archived from the original on May 24, 2024.
  104. "Tropical Storm 14W (Wukong) Warning Nr 020". Joint Typhoon Warning Center. July 26, 2018. Archived from the original on May 24, 2024.
  105. "Archived copy". Archived from the original on 2018-08-29. Retrieved 2018-08-18.{{cite web}}: CS1 maint: archived copy as title (link)
  106. "bwp152018.dat". Joint Typhoon Warning Center. Archived from the original on July 26, 2018. Retrieved July 27, 2018.
  107. "Prognostic Reasoning for Tropical Depression 15W (Fifteen) Warning Nr 01". July 22, 2018. Archived from the original on May 23, 2024. Retrieved July 27, 2018.
  108. "WWJP25 RJTD 231800". Japan Meteorological Agency. July 23, 2018. Archived from the original on May 23, 2024. Retrieved July 27, 2018.
  109. "RSMC Tropical Cyclone Advisory 241800". Japan Meteorological Agency. July 24, 2017. Archived from the original on May 23, 2024. Retrieved July 27, 2017.
  110. "Prognostic Reasoning for Tropical Storm 15W (Jongdari) Warning Nr 12". July 24, 2018. Archived from the original on May 23, 2024. Retrieved July 27, 2018.
  111. "RSMC Tropical Cyclone Advisory 251200". Japan Meteorological Agency. July 25, 2017. Archived from the original on May 23, 2024. Retrieved July 28, 2017.
  112. "Prognostic Reasoning for Tropical Storm 15W (Jongdari) Warning Nr 15". July 25, 2018. Archived from the original on May 23, 2024. Retrieved July 28, 2018.
  113. "Prognostic Reasoning for Tropical Storm 15W (Jongdari) Warning Nr 19". July 26, 2018. Archived from the original on May 23, 2024. Retrieved July 28, 2018.
  114. "RSMC Tropical Cyclone Advisory 261200". Japan Meteorological Agency. July 26, 2017. Archived from the original on May 23, 2024. Retrieved July 28, 2017.
  115. "RSMC Tropical Cyclone Advisory 270000". Japan Meteorological Agency. July 27, 2017. Archived from the original on May 23, 2024. Retrieved July 28, 2017.
  116. "Prognostic Reasoning for Typhoon 15W (Jongdari) Warning Nr 23". July 27, 2018. Archived from the original on May 23, 2024. Retrieved July 28, 2018.
  117. "Prognostic Reasoning for Typhoon 15W (Jongdari) Warning Nr 25". July 28, 2018. Archived from the original on May 23, 2024. Retrieved July 28, 2018.
  118. 平成30年 台風第12号に関する情報 第73号 (in Japanese). Japan Meteorological Agency. July 28, 2018. Archived from the original on July 28, 2018. Retrieved July 28, 2018.
  119. 台風第12号 (ジョンダリ) 平成30年07月29日01時50分 発表 (in Japanese). Japan Meteorological Agency. July 28, 2018. Archived from the original on July 28, 2018. Retrieved July 28, 2018.
  120. 平成30年 台風第12号に関する情報 第94号 (in Japanese). Japan Meteorological Agency. July 29, 2018. Archived from the original on July 29, 2018. Retrieved July 29, 2018.
  121. 中央气象台03日10时30分发布台风登陆消息 (in Chinese). National Meteorological Center of CMA. August 3, 2018. Archived from the original on August 3, 2018. Retrieved August 3, 2018.
  122. "Archived copy". Archived from the original on 2024-05-22. Retrieved 2018-07-29.{{cite web}}: CS1 maint: archived copy as title (link)
  123. "Tropical Depression 16W (Sixteen) Warning Nr 001". Joint Typhoon Warning Center. July 30, 2018. Archived from the original on May 24, 2024.
  124. "Archived copy". Archived from the original on 2024-05-22. Retrieved 2018-07-31.{{cite web}}: CS1 maint: archived copy as title (link)
  125. "Prognostic Reasoning for Tropical Depression 16W (Sixteen) Warning Nr 02". Joint Typhoon Warning Center. July 30, 2018. Archived from the original on May 24, 2024.
  126. "Tropical Depression 16W (Sixteen) Warning Nr 004". Joint Typhoon Warning Center. July 31, 2018. Archived from the original on May 24, 2024.
  127. "Prognostic Reasoning for Tropical Depression 16W (Sixteen) Warning Nr 05". Joint Typhoon Warning Center. July 31, 2018. Archived from the original on May 24, 2024.
  128. "Tropical Depression 16W (Sixteen) Warning Nr 006". Joint Typhoon Warning Center. July 31, 2018. Archived from the original on May 24, 2024.
  129. "Archived copy". Archived from the original on 2018-08-02. Retrieved 2018-08-02.{{cite web}}: CS1 maint: archived copy as title (link)
  130. "Tropical Depression 17W (Seventeen) Warning Nr 001". Joint Typhoon Warning Center. August 2, 2018. Archived from the original on May 23, 2024.
  131. "Tropical Storm 17W (Shanshan) Warning Nr 003". Joint Typhoon Warning Center. August 3, 2018. Archived from the original on May 23, 2024.
  132. "Prognostic Reasoning for Tropical Storm 17W (Shanshan) Warning Nr 04". Joint Typhoon Warning Center. August 3, 2018. Archived from the original on May 23, 2024.
  133. 平成30年の災害等の発生状況 (PDF) (Report) (in Japanese). Miyagi Prefectural Government. 2018. Archived (PDF) from the original on July 27, 2019. Retrieved November 11, 2018.
  134. "Archived copy". Archived from the original on 2024-05-23. Retrieved 2018-08-01.{{cite web}}: CS1 maint: archived copy as title (link)
  135. "Tropical Depression 18W (Eighteen) Warning Nr 001". Joint Typhoon Warning Center. August 6, 2018. Archived from the original on May 23, 2024.
  136. "Prognostic Reasoning for Tropical Depression 18W (Eighteen) Warning Nr 03". Joint Typhoon Warning Center. August 7, 2018. Archived from the original on May 23, 2024.
  137. "Prognostic Reasoning for Tropical Storm 18W (Yagi) Warning Nr 07". Joint Typhoon Warning Center. August 8, 2018. Archived from the original on May 23, 2024.
  138. "Prognostic Reasoning for Tropical Storm 18W (Yagi) Warning Nr 24". Joint Typhoon Warning Center. August 12, 2018. Archived from the original on May 23, 2024.
  139. 中央气象台12日23时40分发布台风登陆消息 (in Chinese). National Meteorological Center of CMA. August 12, 2018. Archived from the original on August 12, 2018. Retrieved August 12, 2018.
  140. "Tropical Storm 18W (Yagi) Warning Nr 025". Joint Typhoon Warning Center. August 12, 2018. Archived from the original on May 23, 2024.
  141. "Archived copy". Archived from the original on 2018-08-17. Retrieved 2018-08-18.{{cite web}}: CS1 maint: archived copy as title (link)
  142. ^ "Global Catastrophe Recap August 2018" (PDF). Archived (PDF) from the original on September 7, 2018. Retrieved September 7, 2018.
  143. "Tropical Depression 20W (Twenty) Warning Nr 001". Joint Typhoon Warning Center. August 12, 2018. Archived from the original on May 22, 2024.
  144. "Prognostic Reasoning for Tropical Storm 20W (Bebinca) Warning Nr 04". Joint Typhoon Warning Center. August 13, 2018. Archived from the original on May 22, 2024.
  145. "Prognostic Reasoning for Tropical Storm 20W (Bebinca) Warning Nr 11". Joint Typhoon Warning Center. August 15, 2018. Archived from the original on May 24, 2024.
  146. "Prognostic Reasoning for Tropical Storm 20W (Bebinca) Warning Nr 15 CORRECTED". Joint Typhoon Warning Center. August 16, 2018. Archived from the original on May 22, 2024.
  147. ^ "Nghệ An xin trung ương hỗ trợ 350 tỉ đồng khắc phục thiệt hại bão số 4". 22 August 2018. Archived from the original on 22 August 2018. Retrieved 22 August 2018.
  148. 平成30年 台風第15号に関する情報 第38号 (in Japanese). Japan Meteorological Agency. August 14, 2018. Archived from the original on August 17, 2018. Retrieved August 17, 2018.
  149. "Tropical Storm 10E (Hector) Warning Nr 054". Joint Typhoon Warning Center. August 13, 2018. Archived from the original on May 24, 2024.
  150. "Prognostic Reasoning for Tropical Storm 10E (Hector) Warning Nr 54". Joint Typhoon Warning Center. August 13, 2018. Archived from the original on May 24, 2024.
  151. "Prognostic Reasnong for Tropical Storm 10E (Hector) Warning Nr 55". Joint Typhoon Warning Center. August 14, 2018. Archived from the original on May 24, 2024.
  152. "Prognostic Reasoning for Tropical Storm 10E (Hector) Warning Nr 58". Joint Typhoon Warning Center. August 14, 2018. Archived from the original on May 24, 2024.
  153. "Tropical Depression 10E (Hector) Warning Nr 059". Joint Typhoon Warning Center. August 15, 2018. Archived from the original on May 24, 2024.
  154. "温比亚"已登陆上海浦东 苏浙沪皖鄂豫迎强风雨 (in Chinese). National Meteorological Center of CMA. August 16, 2018. Archived from the original on August 17, 2018. Retrieved August 17, 2018.
  155. Alice Yan (August 24, 2018). "Floods brought by Typhoon Rumbia devastate China's biggest supplier of vegetables". South China Morning Post. Archived from the original on August 25, 2018. Retrieved August 25, 2018.
  156. 태풍 현황과 전망 (in Korean). Korea Meteorological Administration. August 23, 2018. Archived from the original on August 23, 2018. Retrieved August 23, 2018.
  157. ^ "台风"苏力"致吉林黑龙江损失5.5亿元". 中华人民共和国减灾部. August 27, 2018. Archived from the original on September 22, 2018. Retrieved August 27, 2018.
  158. ^ Hamish Macdonald (September 3, 2018). "Dozens dead, tens of thousands displaced by flooding in North Korea: UN". NK News. Archived from the original on October 21, 2018. Retrieved October 3, 2018.
  159. 平成30年 台風第20号に関する情報 第55号 (in Japanese). Japan Meteorological Agency. August 23, 2018. Archived from the original on August 23, 2018. Retrieved August 23, 2018.
  160. 平成30年 台風第20号に関する情報 第59号 (in Japanese). Japan Meteorological Agency. August 23, 2018. Archived from the original on August 23, 2018. Retrieved August 23, 2018.
  161. 台風20号、和歌山の農林水産被害 計21億9千万円 (in Japanese). Sankei Shimbun. September 29, 2018. Archived from the original on October 23, 2018. Retrieved October 23, 2018.
  162. ^ 2018年 8月 (PDF) (Report) (in Japanese). Japan Meteorological Agency. Retrieved April 10, 2019.
  163. "WWJP25 RJTD 250000". Japan Meteorological Agency. August 25, 2018. Archived from the original on 2024-05-22. Retrieved August 27, 2018.
  164. "WWJP25 RJTD 261200". Japan Meteorological Agency. August 26, 2018. Archived from the original on 2024-05-24. Retrieved August 27, 2018.
  165. "bst2018.txt". Japan Meteorological Agency. Archived from the original on April 12, 2019. Retrieved April 12, 2019.
  166. James Griffiths; Steve George; Jo Shelley (15 September 2018). "Philippines lashed by Typhoon Mangkhut, strongest storm this year". Cable News Network. Archived from the original on 15 September 2018. Retrieved 22 September 2018.
  167. ^ Girlie Linao (22 September 2018). "Typhoon Mangkhut death toll hits 127". PerthNow. Archived from the original on 14 October 2019. Retrieved 8 October 2018.
  168. "At least 95 dead due to Typhoon Ompong". Rappler. 21 September 2018. Archived from the original on 13 May 2019. Retrieved 21 September 2018.
  169. 应急管理新机制助力台风"山竹"应对 (Report) (in Simplified Chinese). September 19, 2018. Archived from the original on September 28, 2018. Retrieved September 22, 2018.
  170. McKenzie, Sheena (16 September 2018). "Typhoon Mangkhut hits mainland China, lashes Hong Kong, dozens dead in Philippines". CNN. Archived from the original on 18 February 2020. Retrieved 16 September 2018.
  171. ^ "Situational Report No.55 re Preparedness Measures for TY OMPONG (I.N. MANGKHUT)" (PDF). NDRRMC. October 5, 2018.
  172. "Tropical Storm Barijat(1823)". Archived from the original on 2018-11-16. Retrieved 2018-11-16.
  173. 平成30年 台風第24号に関する情報 第101号 (in Japanese). Japan Meteorological Agency. September 30, 2018. Archived from the original on September 30, 2018. Retrieved September 30, 2018.
  174. 平成30年台風第24号による被害状況 (in Japanese). Ministry of Agriculture, Forestry and Fisheries. January 9, 2019. Archived from the original on March 23, 2019. Retrieved January 16, 2019.
  175. "Prognostic Reasoning for Tropical Depression 29W (Twentynine) Warning Nr 01". Joint Typhoon Warning Center. September 26, 2018. Archived from the original on May 24, 2024. Retrieved September 28, 2018.
  176. "WWJP25 RJTD 271200". Japan Meteorological Agency. September 27, 2018. Archived from the original on May 22, 2024. Retrieved September 28, 2018.
  177. "WWJP25 RJTD 271800". Japan Meteorological Agency. September 27, 2018. Archived from the original on May 24, 2024. Retrieved September 28, 2018.
  178. "Prognostic Reasoning for Tropical Disturbance 94W". 2018-09-25. Archived from the original on 2024-05-24.
  179. "熱帶性低氣壓WP302018 #1". 2018-09-28. Archived from the original on 2024-05-24.
  180. "日本氣象廳2018年西北太平洋第35號熱帶低氣壓烈風警告 #1". 2018-09-29. Archived from the original on 2024-05-24.
  181. 康芮強度今晚起減弱! 專家:近台時是中颱等級 (in Chinese). Taiwan. 2018-10-02. Archived from the original on 2018-10-03. Retrieved 2018-10-03.
  182. 郭展毓 (2018-10-06). 「康芮」登陸南韓慶南 釜山已現強風雨 (in Chinese). Hong Kong: TVBS新聞網. Retrieved 2018-10-06.
  183. "Tropical Storm Kong-rey Leaves 2 Dead, 1 Missing In South Korea | The Weather Channel". The Weather Channel. Archived from the original on 2018-10-09. Retrieved 2018-10-09.
  184. 정부, 태풍 콩레이 피해복구비 2360억 지원 (in Korean). Newsis. October 30, 2018. Retrieved October 31, 2018.
  185. 颱風「康妮」周六吹向日本西南部及韓國 長崎縣約1.2萬戶停電 (in Chinese). 王海如. 2018-10-07. Archived from the original on 2018-11-16. Retrieved 2018-10-08.
  186. ^ 颱風「康妮」吹襲韓國 韓2人死亡1人失蹤 日1人死亡 (in Chinese). 王燕婷. 2018-10-07. Archived from the original on 2018-10-07. Retrieved 2018-10-08.
  187. 農作物の台風被害拡大 沖縄、24号と25号で20億円 (in Japanese). Ryūkyū Shimpō. October 10, 2018. Archived from the original on November 4, 2018. Retrieved October 31, 2018.
  188. 農林水産被害120億円 台風24、25号で県確定 (in Japanese). Miyazaki Nichinichi Shinbun. November 16, 2018. Retrieved November 17, 2018.
  189. Matthew Cappucci (October 2, 2018). "Two monster tropical cyclones are raging in the Pacific Ocean". The Washington Post. Retrieved October 14, 2018.
  190. Colin Dwyer (October 24, 2018). "Super Typhoon Yutu, 'Strongest Storm Of 2018,' Slams U.S. Pacific Territory". NPR. Archived from the original on October 25, 2018. Retrieved October 25, 2018.
  191. "Category 5 Super Typhoon Yutu Now Moving Away From U.S. Territories of Saipan, Tinian After Devastating Strike". The Weather Company. October 24, 2018. Archived from the original on October 25, 2018. Retrieved October 25, 2018.
  192. "Humanitarian crisis looms after Super Typhoon Yutu flattens parts of Saipan and Tinian". Pacific Daily News. USAToday. October 26, 2018. Retrieved October 26, 2018.
  193. Service, US Department of Commerce, NOAA, National Weather. "Central Pacific Hurricane Center - Honolulu, Hawai'i". www.prh.noaa.gov. Archived from the original on 2018-11-24. Retrieved 2018-11-24.{{cite web}}: CS1 maint: multiple names: authors list (link)
  194. Service, US Department of Commerce, NOAA, National Weather. "Central Pacific Hurricane Center - Honolulu, Hawai'i". www.prh.noaa.gov. Archived from the original on 2018-11-24. Retrieved 2018-11-24.{{cite web}}: CS1 maint: multiple names: authors list (link)
  195. ^ Amazona, Roel (November 22, 2018). "1 dead, thousands displaced as 'Samuel' cuts through Samar". Pililppines News Agency. Retrieved November 22, 2018.
  196. "Situational Report No.11 for Preparedness Measures and Effects of TD SAMUEL" (PDF). NDRRMC. November 24, 2018. Retrieved November 25, 2018.
  197. ^ "TP HCM 3 người chết do ảnh hưởng bão số 9". Báo Mới. November 27, 2018. Retrieved November 28, 2018.
  198. ^ "Tóm tắt các cơn bão trong năm 2018" (in Vietnamese). Government of Tuyen Quang province. January 5, 2019. Retrieved January 20, 2019.
  199. "Tropical Depression 35W (Thirty-five) Warning Nr 023". Joint Typhoon Warning Center. 30 December 2018. Archived from the original on 22 May 2024. Retrieved 1 January 2019.
  200. Sitrep No.26 re Preparedness Measures and Effects of TD USMAN (PDF) (Report). NDRRMC. January 20, 2019. Retrieved January 20, 2019.
  201. "Marine Weather Warning for GMDSS Metarea XI 2018-06-04T06:00:00Z". WIS Portal – GISC Tokyo. Japan Meteorological Agency. June 4, 2018. Retrieved June 4, 2018.
  202. "Marine Weather Warning for GMDSS Metarea XI 2018-06-17T06:00:00Z". WIS Portal – GISC Tokyo. Japan Meteorological Agency. June 17, 2018. Retrieved June 18, 2018.
  203. "Marine Weather Warning for GMDSS Metarea XI 2018-06-18T06:00:00Z". WIS Portal – GISC Tokyo. Japan Meteorological Agency. June 18, 2018. Retrieved June 18, 2018.
  204. "bwp952018.dat". Joint Typhoon Warning Center. August 5, 2018. Archived from the original on August 6, 2018. Retrieved August 6, 2018.
  205. "WWJP25 RJTD 240600". Japan Meteorological Agency. August 24, 2018. Archived from the original on 2024-05-22. Retrieved August 26, 2018.
  206. "WWJP25 RJTD 260600". Japan Meteorological Agency. August 26, 2018. Archived from the original on 2024-05-22. Retrieved August 26, 2018.
  207. "WWJP25 RJTD 261200". Japan Meteorological Agency. August 26, 2018. Archived from the original on 2024-05-24. Retrieved August 26, 2018.
  208. "Pacific Surface Analysis 06:00 UTC 19 Sep 2018". Ocean Prediction Center. September 19, 2018. Archived from the original (GIF) on September 28, 2018. Retrieved September 28, 2018.
  209. "Pacific Surface Analysis 12:00 UTC 19 Sep 2018". Ocean Prediction Center. September 19, 2018. Archived from the original (GIF) on September 28, 2018. Retrieved September 28, 2018.
  210. "WWJP25 RJTD 211200 CCA". Japan Meteorological Agency. September 21, 2018. Archived from the original on May 22, 2024. Retrieved September 28, 2018.
  211. "Surface Analysis 230000 UTC Sep. 2018" (PDF). Japan Meteorological Agency. September 23, 2018. Archived from the original (PDF) on September 28, 2018. Retrieved September 28, 2018.
  212. "Surface Analysis 230600 UTC Sep. 2018" (PDF). Japan Meteorological Agency. September 23, 2018. Archived from the original (PDF) on September 28, 2018. Retrieved September 28, 2018.
  213. "WTPQ20 RJTD 310600 RSMC Tropical Cyclone Advisory". Japan Meteorological Agency. 31 December 2018. Archived from the original on 2024-05-23. Retrieved 1 January 2019.
  214. "Tropical Depression 36W (Thirtysix) Warning Nr 001". Joint Typhoon Warning Center. 31 December 2018. Archived from the original on 24 May 2024. Retrieved 1 January 2019.
  215. "WTPQ20 RJTD 010600 RSMC Tropical Cyclone Advisory". Japan Meteorological Agency. 1 January 2019. Archived from the original on 2024-05-23. Retrieved 1 January 2019.
  216. ^ Padgett, Gary. "Monthly Tropical Cyclone Summary December 1999". Australian Severe Weather. Archived from the original on 2012-02-11. Retrieved October 1, 2013.
  217. ^ The Typhoon Committee (February 21, 2013). "Typhoon Committee Operational Manual 2013" (PDF). World Meteorological Organization. pp. 37–38. Archived (PDF) from the original on 2013-08-01. Retrieved October 1, 2013.
  218. "CMA". www.cma.gov.cn. Retrieved 2019-03-01.
  219. "WMO 52nd Typhoon Committee" (PDF). ESCAP/WMO Typhoon Committee. 2020-06-10.
  220. "Philippine Tropical Cyclone Names". bagong.pagasa.dost.gov.ph. Retrieved November 11, 2020.
  221. ^ "Global Catastrophe Recap July 2018" (PDF). Archived (PDF) from the original on August 9, 2018. Retrieved August 9, 2018.
  222. "热带低压致广西海南云南损失1亿元". 中华人民共和国减灾部. July 27, 2018. Archived from the original on July 29, 2018. Retrieved July 27, 2018.
  223. News Typhoon Jongdari, July 2018 Typhoon Jongdari (PDF) (Report). Credit Suisse. August 2, 2018. Archived (PDF) from the original on October 19, 2018. Retrieved October 12, 2018.
  224. 台風12号:県農林水産被害 総額10億3543万円 /愛知 (in Japanese). Mainichi Shimbun. August 10, 2018. Archived from the original on October 24, 2018. Retrieved October 10, 2018.
  225. 台風12号の影響による農林水産業への被害について(第3報兼最終報) (in Japanese). Chiba Local Government. September 10, 2018. Archived from the original on November 6, 2018. Retrieved October 10, 2018.
  226. 平成30年8月9日大雨(台風第13号)による被害状況について (PDF) (Report) (in Japanese). Miyagi Prefectural Government. August 10, 2018. Archived (PDF) from the original on September 15, 2018. Retrieved August 11, 2018.
  227. Keoni, Everington (September 4, 2018). "Rogue waves claim 6 lives over 2 days in NE Taiwan". Taiwan News. Archived from the original on September 4, 2018. Retrieved September 4, 2018.
  228. 沈如峰 (September 3, 2018). 南澳神秘沙灘落海意外已釀4死 尚有1失蹤 (in Chinese). Yilan County, Taiwan: Central News Agency. Archived from the original on September 4, 2018. Retrieved September 4, 2018.
  229. "Japan deals with Jebi aftermath". NHK. September 5, 2018. Archived from the original on September 5, 2018. Retrieved September 5, 2018.
  230. "RMS Estimates Insured Losses from Typhoon Jebi Could Reach $5.5 Billion". Insurance Journal. September 14, 2018. Archived from the original on September 14, 2018. Retrieved September 17, 2018.
  231. "Global Catastrophe Recap September 2018" (PDF). Archived (PDF) from the original on December 9, 2019. Retrieved October 12, 2018.
  232. 台风"山竹"致澳门经济损失15.5亿 (in Chinese). sina. 2018-11-12. Retrieved 2018-11-12.
  233. "Death toll rises to 4, as Japan struck by strong typhoon". World Bulletin. October 2, 2018. Retrieved October 8, 2018.
  234. "Global Catastrophe Recap October 2018" (PDF). Archived (PDF) from the original on November 16, 2018. Retrieved November 21, 2018.
  235. Haidee V. Eugenio (October 26, 2018). "Humanitarian crisis looms after Super Typhoon Yutu flattens parts of Saipan and Tinian". USA Today. Retrieved January 30, 2019.
  236. "Global Catastrophe Recap October 2018" (PDF). AON. November 7, 2018. Archived (PDF) from the original on November 16, 2018. Retrieved November 21, 2018.

External links

Tropical cyclones of the 2018 Pacific typhoon season
TSBolaven TSSanba VITYJelawat TD04W TSEwiniar STSMaliksi TDTD SS07W TSGaemi TDTD TYPrapiroon VITYMaria TSSon-Tinh TDTD STSAmpil TDJosie STSWukong TYJongdari TD16W TYShanshan TSYagi TSBebinca STSLeepi TSHector TSRumbia VSTYSoulik VSTYCimaron TDLuis TDTD VITYJebi TDTD VITYMangkhut TSBarijat VITYTrami TDTD TD29W VITYKong-rey TDTD TDTD VITYYutu TDTD STSUsagi TSToraji TYMan-yi TDUsman
2010–2019 Pacific typhoon seasons
Tropical cyclones in 2018
Cyclones
Hurricanes
Typhoons
Non-seasonal lists
Categories: