Typhoon Wipha (2013)

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Typhoon Wipha (Tino)
Typhoon (JMA scale)
Category 4 (Saffir–Simpson scale)
Wipha Oct 13 2013 0125Z.jpg
Typhoon Wipha on October 13
Formed October 9, 2013
Dissipated October 22, 2013[1]
(Extratropical after October 16, 2013)
Highest winds 10-minute sustained: 165 km/h (105 mph)
1-minute sustained: 220 km/h (140 mph)
Lowest pressure 930 hPa (mbar); 27.46 inHg
Fatalities 41 total
Damage $100 million (2013 USD)
Areas affected Northern Mariana Islands, Guam, Japan
Part of the 2013 Pacific typhoon season

Typhoon Wipha, known in the Philippines as Typhoon Tino, was a large typhoon that caused extensive damage in Japan in mid-October 2013. The system originated from a tropical depression well to the east of Guam on October 8. Tracking generally westward, development of the depression was initially slow; however, on October 11, favorable atmospheric conditions allowed for rapid intensification. The depression strengthened to a tropical storm that day, receiving the name Wipha at the time, and reached typhoon status on October 12. Now moving northwestward, Wipha grew into a very large system and ultimately attained its peak intensity on October 14 with winds of 165 km/h (105 mph) and an atmospheric pressure of 930 mbar (hPa; 27.46 inHg). Accelerating and turning more northerly, the typhoon weakened as conditions became less conducive for tropical cyclones. Wipha dramatically accelerated northeastward on October 15 as it interacted with a stalled out front over Japan. Simultaneously, the storm began transitioning into an extratropical cyclone, a process which it completed early on October 16. It is said that the storm caused over 100 million dollars of damage.[2]

Meteorological history

Map plotting the track and intensity of the storm according to the Saffir–Simpson hurricane wind scale

Early on October 8, 2013, the United States Joint Typhoon Warning Center (JTWC) reported that a tropical disturbance had developed within an area of low to moderate vertical wind shear, about 670 km (415 mi) to the east-southeast of Anderson Air Force Base on the island of Guam.[3] During that day, atmospheric convection started to wrap around into a consolidating low level circulation center, before the Japan Meteorological Agency (JMA) started to monitor the system as a tropical depression early the next day.[4][5]

During October 10, the JTWC initiated advisories on the system and designated it as Tropical Depression 25W.[6] Afterwards, 25W had intensified and have been declared a tropical storm, while the JMA gave the tropical storm name Wipha (1326). Later on, the JMA classified Wipha as a severe tropical storm when it strengthened on October 11, and later on October 12, 2013, Wipha intensified into a typhoon.[citation needed] As it was slowly moving, Wipha entered an area of warm waters and low wind shear. Due to this, the cyclone rapidly intensified into a minimal category 4 typhoon. As it did, Wipha developed a compact, small, clear eye. On the noon of October 14, the Philippine Atmospheric, Geophysical and Astronomical Services Administration, also known as PAGASA, noticed that Wipha had entered the Philippine area of responsibility. As it did, it received the Philippine name Tino.[7] As it weakened into a category 3 typhoon, then into a category 2 typhoon, Wipha left PAGASA's area of responsibility . Early on October 15, Wipha rapidly enfeebled as the ocean waters surrounding the typhoon began to cool as it approached Japan with category 1 status.[8][9] As it came closer, it dumped very heavy rain in many areas of East Japan, killing 25. Afterwards, it was then reported that an additional 16 people perished due to landslides and flashfloods.[10]The storm reached extratropical status late on October 16. The remnants of Wipha continued to be extratropical as it was located southeast of the Kamchatka Peninsula on October 17.[citation needed] As it continued to speed up, Wipha's extratropical remnant low was last noted by the JMA during October 18, after it had crossed the international dateline and moved out of the JMA's area of responsibility.[5]

Preparations and impact

File:Wipha Oct 15 2013 0425Z.jpg
Typhoon Wipha approaching Japan on October 15

In anticipation of heavy rains at the debilitated Fukushima Daiichi Nuclear Power Plant, the Tokyo Electric Power Company (TEPCO) placed sandbags around a drainage ditch holding back radioactive water.[11] Regarded as a "once in a decade storm" by the JMA, schools throughout Tokyo were closed on October 16. Significant disruptions to transportation took place, with over 60,000 people having their flights canceled and train service in parts of the city was suspended. Cosmo Oil, Fuji Oil, Idemitsu Kosan, and JX Holdings suspended shipments in eastern Japan while Nissan Motor cancelled shipments for the day.[12]

Typhoon Wipha weakened as it skirted Japan's eastern coastline on October 15. Though the storm caused only limited damage on the mainland, it spawned a massive landslide on the island of Izu Ōshima, killing at least 31 and leaving 13 others missing.[13] In addition, a woman was killed in western Tokyo, and the body of one of two schoolchildren who went missing near Kanagawa was later found. A man in Chiba and the other child were still reported missing, in addition to the victims on Oshima.[14][15] At least 350 homes were destroyed throughout Japan, mostly on Izu Ōshima.[16]

At the Fukushima Daiichi plant, 12 water storage tanks overflowed from the typhoon's heavy rains. Beta radiation levels skyrocketed to 400,000 becquerels in the wake of the storm, 6,500 times greater than prior to Wipha. The overflow was blamed on TEPCO's inadequate preparation and not heeding warnings of the storm. In addition, beta radiation was detected in areas beyond the levees designed to hold back contaminated water.[17] On October 24, it was announced that radiation levels in water near the Fukushima nuclear plant reached an all-time high of 140,000 becquerels, greatly surpassing the previous peak of 59,000 becquerels. The spike in radiation is at least partially attributed to torrential rains from Typhoon Wipha.[11]

Izu-Oshima

During October 15, the JMA issued a mudslide warning for the volcanic islands of Izu-Oshima and Miyakejima, which was subsequently relayed to the Tokyo Metropolitan government which sent a fax transmission to the affected local governments.[18] However, while the Miyakejima government got the warning and advised residents to evacuate, the staff in the Izu-Oshima town office had left for the day with only a security guard left on duty.[18] As a result, local officials didn’t see the advisory until around midnight local time, by which time they had decided it was too dangerous, to ask residents to leave their homes and did not issue an evacuation order.[18] During the next day as Wipha moved towards the north-northwest it caused heavy rain in the town of Oshima, where an hourly rainfall total of 100 mm (3.9 in) and a 24-hour total of 824 mm (32.4 in) were recorded.[19] As a result of the rainfall several landslides, debris flows and slope failures were recorded in the thin volcanic ash layer of hillside surfaces, which resulted in at least 41 fatalities.[19]

During the systems aftermath the Government of Japan quickly established a disaster response office in Oshima Town, to support the evacuation of residents and help prevent any secondary disasters.[19] The Government also dispatched the Technical Emergency Control Force (TEC‐FORCE) and the Japan Self-Defense Forces to the island to conduct search and rescue operations, evaluate the extent of the damage and help prevent secondary disasters.[19] The TEC‐FORCE set up a video monitoring system to observe streams affected by debris flow and performed emergency ground surveying at local streams and slopes considered to be at risk of further damage, to clarify the possibility of secondary disasters ahead of Typhoon Francisco impacting the area.[19] The results of the emergency ground surveying to the local prefecture government and municipal office, in order to support decisions relating to resident safety.[19] The Tokyo Metropolitan government was criticized by the media for using a fax machine to relay the warnings despite vastly improved technology.[18] However, the metropolitan government stood by its use of fax machines to disseminate warnings as it enabled them to transmit warnings all at once.[18] During October 17, the mayor of Izu Oshima Island issued a public apology for not issuing an evacuation order and admitted the order could have saved lives.[16]

See also

References

  1. ↑ http://www.vos.noaa.gov/MWL/201408/northpacific.shtml
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ 5.0 5.1 Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ http://www.webcitation.org/6KGfCusJR
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ 11.0 11.1 Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Frogmen join body hunt as Japan typhoon tolls hit 24 (AFP)
  15. ↑ http://www.bbc.co.uk/news/world-asia-24531140
  16. ↑ 16.0 16.1 Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ 18.0 18.1 18.2 18.3 18.4 Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ 19.0 19.1 19.2 19.3 19.4 19.5 Lua error in package.lua at line 80: module 'strict' not found.

External links

Retrieved from "https://infogalactic.com/w/index.php?title=Typhoon_Wipha_(2013)&oldid=691369667"