Tropical Storm Nanmadol (2017)

Severe Tropical Storm Nanmadol, known in the Philippines as Severe Tropical Storm Emong, was a tropical cyclone that impacted southern Japan during July 2017. Nanmadol developed over in the Philippine Sea as a tropical depression on July 1, and strengthened into the third named storm of the 2017 typhoon season on July 3. After gaining organization, the system rapidly developed and intensified into a severe tropical storm and reached its peak intensity with a 10-minute maximum sustained winds of 100 km/h (65 mph) and a minimum barometric pressure of 985 hPa (29.09 inHg). On July 4, Nanmadol turned eastwards and made landfall near Nagasaki, Kyushu, just before it transitioned into an extratropical cyclone.

Severe Tropical Storm Nanmadol (Emong)
Severe tropical storm (JMA scale)
Category 1 typhoon (SSHWS)
Severe Tropical Storm Nanmadol near peak intensity on July 3
FormedJuly 1, 2017
DissipatedJuly 8, 2017
(Extratropical after July 4)
Highest winds10-minute sustained: 100 km/h (65 mph)
1-minute sustained: 120 km/h (75 mph)
Lowest pressure985 hPa (mbar); 29.09 inHg
Fatalities42 total
Damage$1.68 billion (2017 USD)
Areas affectedJapan
Part of the 2017 Pacific typhoon season

Nanmadol dropped torrential rainfall across Kyushu, resulting in landslides, although the Fukuoka and Ōita Prefectures were the hardest hit. The city of Asakura, Fukuoka experienced a one-day rainfall surpassing the city's average total for July by 50%, with a rainfall of 500 mm (20 in) recorded within a 12-hour period on July 5. Landslides were recorded in 44 different locations and flooding in 38 locations, and from this, more than 2,600 homes were destroyed. In total, 42 people died from Nanmadol due to drowning from flash flooding or due to landslides. Total damages was estimated to have toppled to ¥190 billion (US$1.68 billion).


Meteorological history
Map plotting the track and the intensity of the storm, according to the Saffir–Simpson scale

During June 30, a tropical disturbance developed about 463 km (288 mi) to the north-northeast of Palau.[1] Noting some organization within the system, the Joint Typhoon Warning Center (JTWC) issued a Tropical Cyclone Formation Alert (TCFA) early on July 1.[2] Six hours later, the Japan Meteorological Agency (JMA) classified it as a tropical depression.[3][4] Later that day, the JMA began to issue advisories, predicting that the system could intensify into a tropical storm within the next 24 hours.[5] Shortly after, the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) upgraded the system to a tropical depression, assigning the local name Emong.[6]

Early on July 2, the JMA upgraded the system to a tropical storm, and assigned the official name Nanmadol.[7] The PAGASA also upgraded the system to a tropical storm.[8] Soon after, the JTWC gave the system the internal designation of 05W.[9] Satellite imagery depicted convective banding wrapping tightly into Nanmadol's low-level circulation center (LLCC), prompting the JTWC to upgrade it to a tropical storm in their next advisory.[10] Nanmadol later entered a favorable environment with low vertical wind shear and high sea surface temperatures (SSTs) of 30–31 °C (86–88 °F), allowing it to develop a deep and symmetric core surrounded by deep convection.[11] At this time, the JMA stated that Nanmadol had intensified into a severe tropical storm.[12] The PAGASA also upgraded Nanmadol to a severe tropical storm in their final advisory on the system as it exited the Philippine Area of Responsibility.[13]

Nanmadol continued to intensify while moving northward just to the east of Taiwan, with satellite imagery capturing a small, developing eye.[14] At 06:00 UTC on July 3, Nanmadol reached its peak intensity with the JTWC assessing the cyclone to have 1-minute sustained winds of 110 km/h (70 mph);[15] the JMA estimated 10-minute sustained winds of 100 km/h (65 mph) and a minimum barometric pressure of 985 hPa (29.09 inHg).[16] However, the JTWC assessed that Nanmadol reached its peak intensity as a Category 1-equivalent typhoon with 1-minute sustained winds of 120 km/h (75 mph) six hours later in a post-analysis report.[17] Nanmadol maintained its peak intensity for several hours until just before July 4, when the system began curving eastwards and its satellite presentation deteriorated.[18] Around that time, Nanmadol made landfall approximately 40 km (25 mi) to the east of Nagasaki in Kyushu.[19] Despite the system still displaying a well-defined center, cloud tops began to warm, in line with the rapid weakening trend of the system.[20] After several hours, Nanmadol began to interact with the mid-latitude westerlies; the JTWC downgraded the system further to a low-end of tropical storm intensity, though the JMA still maintained it at severe tropical storm intensity.[21] By 21:00 UTC on the same day, the JTWC issued its final advisory on Nanmadol, mentioning that the system was embedded within the cold baroclinic zone, and had thus lost its tropical characteristics and transitioned into a cold-core low.[22] The JMA soon followed suit with their final warning, declaring that Nanmadol had fully become an extratropical cyclone at 00:00 UTC on July 5.[23] Its extratropical remnants later left the basin on July 8.[24]

Preparations, impact, and aftermath
Nanmadol affecting southern Japan on July 4

The JMA issued a heavy rain warning for Shimane Prefecture and neighboring areas, in which the government had urged 20,000 residents to evacuate.[25] On July 3, the Sasebo City Emergency Management Bureau activated a total of 30 emergency shelters.[26] The government dispatched a total of 12,000 rescuers, including police officers, firefighters and the Self-Defense Forces troops, in preparation for post-storm relief.[27] On July 10, the Kyushu Railway Company began a bus service to aid residents trapped in some areas along the currently suspended Kyudai Main Line; this included areas between Ukiha Station in Fukuoka Prefecture and Hita Station, Ōita Prefecture, where an iron bridge spanning a river was washed away by floodwaters. Due to the threat of further landslides, the West Nippon Expressway Company extended a closure of the Ōita Expressway.[28] Trees with trunks of 50–60 cm (19.7–23.6 in) were washed away, blocking the water stream further and exacerbating floods. Therefore, on July 11, Forestry Minister Yuji Yamamoto pledged to set up a task force to remove driftwood. Meanwhile, an official at the University of Hyogo warned other municipalities of potential damage caused by fallen trees.[29]

Map of satellite-estimated rains across Japan after the passage of Nanmadol

Peak windspeeds of 150 km/h (93 mph) were recorded in Nagasaki upon landfall, including a 162 km/h (101 mph) wind gust in the Shikoku town of Muroto just after 05:30 UTC.[30][31] Strong winds overturned vehicles, collapsed scaffolding, and left 68,500 homes without power in Nagasaki and Kumamoto prefectures; other blackouts occurred in the prefectures of Ōita, Miyazaki and Kagoshima.[31][32] Around 3,000 airline passengers were affected by the grounding and cancellation of at least 47 flights. Heavy rains and strong winds disrupted numerous train services including the iconic Shinkansen, between Hakata and Kagoshima-Chuo in Kyushu.[31][32] Evacuation advisories were issued to at least 20,000 residents due to fears of possible flooding and landslides, especially in the Niigata, Toyama and Nagano prefectures that had experienced rainfall accumulations of up to 300 mm (12 in) in the preceding hours.[32] In Hamada, Shimane, over 80 mm (3.1 in) fell in an hour.[33][25]

At least three people were injured during the storm—a young boy's hand was injured when a school window broke in the city of Kumamoto, and two adults in Ōita prefecture sustained injuries from falls as a result of the strong winds.[32][34] About 180 people took shelter at a junior high school gymnasium in Asakura.[27] Within the prefecture, 130 mm (5.1 in) of rain fell in an hour, greatly contributing to a 24-hour rainfall total of 545 mm (21.5 in).[35] A later report showed that the prefecture experienced a total accumulated rainfall of 632.5 mm (24.90 in).[36] The city of Hita, Ōita also experienced extreme rainfall, with accumulations of 400 mm (16 in).[37] However the prefecture of Fukuoka experienced an incredible amount of 774 mm (30.5 in) of rain within the course of nine hours on July 5.[38] Due to the risk of landslides, an evacuation order which covered 316 people from 115 households was issued in the Haki District of Asakura, due to high risk of landslides. Throughout the Fukuoka and Ōita Prefectures, 1,724 people evacuated.[28] More than 2,600 homes were destroyed by Nanmadol around the Fukuoka, Oita, and the Hiroshima prefectures,[39] but a later report showed a total of 4,458 buildings damaged.[40] Nearly a week after the flooding had begun, some roads were already reopened over in some communities in the Fukuoka Prefecture.[29] During July 12, the Japanese Prime Minister Shinzō Abe canceled a trip to Estonia for a European tour and instead visited devastated places over in the Kyushu region to view the damage and console residents. He also promised that the government would take action and do everything possible to help rebuild.[41][42]

A total of 42 people have been confirmed dead due to torrential rains which caused landslides and flooding, particularly in Kyushu,[39][43] where two still remained missing and leaving 39 people injured.[40][36] Total damages in Japan were amounted to be ¥190 billion (US$1.68 billion).[40]

gollark: I'm also relatively confident the government doesn't have my *exact* internet history and whatnot, as that's spread over a bunch of sites and details like exactly which site I'm connecting to and which page on it are encrypted now.
gollark: For the few people I can actually convince to use Signal, my communication with them is up to "probably private".
gollark: dis.cool was a great demonstration of that.
gollark: I treat Discord messages and reddit posts as "basically public" anyway.
gollark: Connections to websites themselves run over HTTPS, which I'm mostly trusting of (MITM attacks are a thing and the government does realistically have access to a cert I'll trust, but that's detectable), and my DNS resolution also runs over HTTPS.

See also

References
  1. "ABPW10 PGTW 300130". Joint Typhoon Warning Center. Archived from the original on July 1, 2017. Retrieved June 30, 2017.
  2. "WTPN21 PGTW 010600". Joint Typhoon Warning Center. July 1, 2017. Archived from the original on July 1, 2017.CS1 maint: BOT: original-url status unknown (link)
  3. "Marine Weather Warning for GMDSS Metarea XI 2017-07-01T06:00:00Z". WIS Portal – GISC Tokyo. Japan Meteorological Agency. July 1, 2017. Retrieved July 1, 2017.
  4. "Tropical Cyclone Formation Alert". Joint Typhoon Warning Center. July 1, 2017. Archived from the original on July 1, 2017. Retrieved July 1, 2017.
  5. "TD". Japan Meteorological Agency. Archived from the original on July 3, 2017. Retrieved July 1, 2017.CS1 maint: BOT: original-url status unknown (link)
  6. "LPA now Tropical Depression Emong". Philippines: Rappler. PAGASA. Retrieved July 2, 2017.
  7. "RSMC Tropical Cyclone Advisory TS 1703 NANMADOL (1703) UPGRADED FROM TD". Japan Meteorological Agency. July 2, 2017. Archived from the original on July 3, 2017.CS1 maint: BOT: original-url status unknown (link)
  8. "Tropical depression Emong now a tropical storm". CNN Philippines. July 2, 2017.
  9. "Tropical Depression 05W (Nanmadol) Warning Nr 001". Joint Typhoon Warning Center. July 2, 2017. Archived from the original on July 3, 2017.CS1 maint: BOT: original-url status unknown (link)
  10. "Prognostic Reasoning for Tropical Storm 05W (Nanmadol) Warning Nr 02". Joint Typhoon Warning Center. July 2, 2017. Archived from the original on July 3, 2017.
  11. "Prognostic Reasoning for Tropical Storm 05W (Nanmadol) Warning Nr 03". Joint Typhoon Warning Center. July 2, 2017. Archived from the original on July 3, 2017.CS1 maint: BOT: original-url status unknown (link)
  12. "RSMC Tropical Cyclone Advisory STS 1703 NANMADOL (1703) UPGRADED FROM TS". Japan Meteorological Agency. July 2, 2017. Archived from the original on July 3, 2017.CS1 maint: BOT: original-url status unknown (link)
  13. "'Emong' exits PAR". Philippines: Philstar. July 3, 2017.
  14. "Prognostic Reasoning for Tropical Storm 05W (Nanmadol) Warning Nr 06". Joint Typhoon Warning Center. July 3, 2017. Archived from the original on July 3, 2017.
  15. "Tropical Storm 05W (Nanmadol) Warning Nr 006". Joint Typhoon Warning Center. July 3, 2017. Archived from the original on July 3, 2017.CS1 maint: BOT: original-url status unknown (link)
  16. "RSMC Tropical Cyclone Advisory STS 1703 NANMADOL (1703)". Japan Meteorological Agency. July 2, 2017. Archived from the original on July 3, 2017.CS1 maint: BOT: original-url status unknown (link)
  17. "JTWC Annual Tropical Cyclone Report 2017" (PDF). Joint Typhoon Warning Center.
  18. "Prognostic Reasoning for Tropical Storm 05W (Nanmadol) Warning Nr 08". Joint Typhoon Warning Center. July 3, 2017. Archived from the original on July 7, 2017.CS1 maint: BOT: original-url status unknown (link)
  19. h"Tropical Cyclone Nanmadol Update (GDACS, JTWC, Media) (ECHO Daily Flash of 4 July 2017)". ReliefWeb. July 4, 2017.
  20. "Prognostic Reasoning for Tropical Storm 05W (Nanmadol) Warning Nr 09". Joint Typhoon Warning Center. July 4, 2017. Archived from the original on July 7, 2017.CS1 maint: BOT: original-url status unknown (link)
  21. "Prognostic Reasoning for Tropical Storm 05W (Nanmadol) Warning Nr 10". Joint Typhoon Warning Center. July 4, 2017. Archived from the original on July 7, 2017.CS1 maint: BOT: original-url status unknown (link)
  22. "Tropical Depression 05W (Nanmadol) Warning Nr 012". Joint Typhoon Warning Center. July 4, 2017. Archived from the original on July 7, 2017.
  23. "RSMC Tropical Cyclone Advisory DEVELOPING LOW FORMER STS 1703 NANMADOL (1703)". Japan Meteorological Agency. July 5, 2017. Archived from the original on July 7, 2017.CS1 maint: BOT: original-url status unknown (link)
  24. "Marine Weather Warning for GMDSS Metarea XI 2017-07-08T06:00:00Z". Japan Meteorological Agency. Retrieved July 8, 2017.
  25. "One dead, 20,000 evacuated as tropical storm Nanmadol batters western Japan". Japan: Sun Daily. July 5, 2017.
  26. "Tropical Storm 05W (Nanmadol), #9 FINAL: Sasebo all clear". Dave Ornauer. June 30, 2017. Retrieved July 3, 2017.
  27. "Rescuers race against time as flood death toll hits 18". Japan Times. July 8, 2017. Retrieved July 8, 2017.
  28. "Death toll from Kyushu rains hits 22 as searches, evacuations continue". Japan: The Mainichi. July 9, 2017. Retrieved July 10, 2017.
  29. "In Kyushu floods, destruction was magnified by fast-flowing driftwood". The Japan Times. July 12, 2017.
  30. "Typhoon hits Nagasaki, torrential rain expected across Japan". Mainichi Daily News. 2017-07-04. Retrieved 2017-07-05.
  31. Faith Eherts. "Tropical Storm Nanmadol to batter Japan with wind, rain through midweek". AccuWeather. Retrieved 2017-07-05.
  32. "Japan typhoon grounds flights, injures 3". The Straits Times. 2017-07-04. Retrieved 2017-07-05.
  33. "High temperatures and extreme weather continue". World Meteorological Organization. July 7, 2017. Retrieved July 7, 2017.
  34. "Typhoon causes mudslides, blackouts". Japan Today. Retrieved 2017-07-05.
  35. "Disaster-hit Kyushu region needs all the help it can get". The Asahi Shimbun. July 8, 2017.
  36. "Digital Typhoon: Typhoon 201703 (NANMADOL) – Disaster Information". Digital Typhoon.
  37. "Death toll rises to 18 as rescue operations continue in rain-pummeled southwestern Japan". Xinhua. July 8, 2017.
  38. "Southern Japan areas devastated by floods". Aljazeera. July 6, 2017.
  39. "Tremendous July Flooding Costs Asia Over $10 Billion in Damages". Chief Investment Officer. August 9, 2017.
  40. 平成 29 年の水害被害額（確報値）を公表 (PDF). Ministry of Land, Infrastructure, Transport and Tourism (in Japanese). April 19, 2019. Retrieved May 2, 2019.
  41. "Japanese PM Abe Promises to Help Victims of Floods; Death Toll up to 25". US News. July 12, 2017.
  42. "Japan Abe sees devastation in flood-hit area". Times live. July 12, 2016.
  43. "Companion Volume to Weather, Climate & Catastrophe Insight" (PDF). Aon Benfield. Retrieved 30 January 2018.

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.