Cyclone Zoe

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Severe Tropical Cyclone Zoe
Category 5 severe tropical cyclone (Aus scale)
Category 5 (Saffir–Simpson scale)
File:Cyclone Zoe 27 dec 2002 2255Z.jpg
Cyclone Zoe near its peak intensity
Formed December 23, 2002 (2002-12-23)
Dissipated January 4, 2003 (2003-01-05)
Highest winds 10-minute sustained: 240 km/h (150 mph)
1-minute sustained: 285 km/h (180 mph)
Gusts: 350 km/h (220 mph)
Lowest pressure 890 hPa (mbar); 26.28 inHg
(Record low in the Southern Hemisphere)
Fatalities None recorded
Areas affected Solomon Islands, Fiji, Vanuatu, Rotuma
Part of the 2002–03 South Pacific cyclone season

Severe Tropical Cyclone Zoe was estimated to be one of the most intense tropical cyclones on record within the Southern Hemisphere. The system was first noted on December 23, 2002 as a tropical depression that had developed, within the South Pacific Convergence Zone to the east of Tuvalu. Over the next couple of days the system moved south-westwards and crossed the International Dateline early on December 25. After this the system became better organized and was declared to be a tropical cyclone and named Zoe later that day. Zoe subsequently rapidly intensified in very favourable conditions as it continued to move west-southwest towards the Solomon Islands. The system subsequently became a Category 5 tropical cyclone on both the Australian tropical cyclone intensity scale and the Saffir-Simpson hurricane wind scale during December 27. The system subsequently affected the Solomon Islands Temotu Province during that day, before it peaked with 10-minute sustained wind speeds of 240 km/h (150 mph). As the system peaked it performed a small clockwise cyclonic loop within the vicinity of Tikopia island, as a result of the steering flow over the cyclone becoming weak and variable. The system subsequently started to move towards the southeast during December 29, in response to a strengthening steering flow, provided by an upper level trough of low pressure and a baroclinic system near New Caledonia. Over the next few days the system weakened and degenerated into a tropical depression during January 1, 2003. The system was subsequently last noted during January 4, while it was located to the southeast of New Caledonia.

Cyclone Zoe severely affected areas of Rotuma, the Solomon Islands, and Vanuatu. Heavy rainfall and strong winds were particularly disastrous to the Solomon Islands, especially on the islands of Anuta and Tikopia. There, numerous crops and fruit–bearing trees were destroyed. Beaches were also heavily eroded due to the high waves generated by the cyclone. Although effects were lesser in Vanuatu, the country's northernmost islands experienced heavy flooding and beaches destroyed by high waves. After this usage of the name Zoe, the name was retired.

Meteorological history

File:Zoe 2002 track.png
Map plotting the track and intensity of the storm according to the Saffir–Simpson hurricane wind scale

During December 23, the Fiji Meteorological Service (FMS) started to monitor Tropical Depression 04F, that had developed within the South Pacific Convergence Zone about 665 km (415 mi) to the east of Funafuti in Tuvalu.[1] Over the next couple of days the system was steered towards the west-southwest, under the influence of a mid-level subtropical ridge of high pressure.[1][2] After the depression had crossed the International Dateline early on December 25, atmospheric convection surrounding 04F increased and the system became better organized.[3][4] At this time vertical wind shear over the system rapidly decreased, while the systems outflow significantly improved.[3][4] As a result, the United States Joint Typhoon Warning Center (JTWC) issued a Tropical Cyclone Formation Alert on the system, before they initiated advisories on the system and designated it as Tropical Cyclone 06P.[5][6] Later that day at 21:00 UTC (08:00 December 26 SIT) the FMS reported that the depression had become a Category 1 tropical cyclone, on the Australian tropical cyclone intensity scale and named it Zoe.[4] At this time the system was located about 220 km (135 mi) to the northwest of the Fijian Dependency; Rotuma and moving westwards at about 18 km/h (11 mph).[1][4]

After being named: Zoe intensified very rapidly in very favourable conditions and became a Category 3 severe tropical cyclone by 12:00 UTC (23:00 SIT) on December 26.[1][7] Zoe's eye subsequently became obvious on both visible and infrared satellite imagery, while the system continued to intensify and became a Category 5 severe tropical cyclone during December 27.[4][7] During December 27, the JTWC reported that Zoe had become equivalent to a category 5 hurricane on the Saffir-Simpson hurricane wind scale as it peaked with 1-minute windspeeds of 285 km/h (180 mph) and passed about 50 km (30 mi) to the southeast of the Solomon Island: Anuta.[2][8] Zoe subsequently turned towards the southwest and passed in between the Solomon Islands of Anuta and Fataka, as the subtropical ridge weakened in response to an upper level trough of low pressure over the Tasman Sea.[2][4] Early on December 28, the FMS estimated that the system had peaked as a Category 5 severe tropical cyclone, with 10-minute sustained wind speeds of 240 km/h (150 mph) and a minimum pressure of Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value)..[4][7] By this time the steering flow over the cyclone had become weak and variable, as the system passed within 30 km (20 mi) of the island of Tikopia.[2] As a result, Zoe virtually stalled and performed a small clockwise cyclonic loop, within the vicinity of Tikopia, however, the eye of the system did not pass over the island.[2]

During December 29, after the system had stalled Zoe started to move towards the southeast in response to the strengthening steering flow, provided by an upper level trough of low pressure and a baroclinic system near New Caledonia.[2][9] Over the next couple of days the system rapidly weakened under the influence of: strengthening vertical wind shear, dry air and cooler sea surface temperatures.[1][4] During December 31, as the system continued its southeastwards movement, it passed about 390 km (240 mi) to the southwest of Nadi, Fiji as a Category 2 tropical cyclone.[1] By this time the system was transitioning into an extra tropical cyclone, while deep convection surrounding the system had significantly diminished.[10] As a result of further weakening, the JTWC issued their final warning on Zoe during January 1, 2003, while the FMS reported that Zoe had weakened into a tropical depression.[4] The system was subsequently recurved and started to move towards the southwest during January 2, before it was declared extratropical as it interacted with an extratropical low which was located over the Tasman Sea.[2][7] Zoe was subsequently last noted by the FMS during January 4, while it was located about 367 km (230 mi) to the southeast of Noumea, New Caledonia.[7]

Intensity

At its peak intensity Zoe was estimated by the FMS to be a Category 5 severe tropical cyclone, with 10-minute sustained wind speeds of 240 km/h (150 mph) and a minimum pressure of Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value)..[7] The United States Joint Typhoon Warning Center reported that the system had peaked with 1-minute sustained wind speeds of 285 km/h (180 mph) and a minimum pressure of Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value)..[8] As a result, both of these estimates would make Zoe, the most intense tropical cyclone on record within the South Pacific Ocean. However, both of these intensity estimates were based on a subjective application of the Dvorak technique, as there were no direct observations of the systems intensity.[2][4]

Preparations, impact and aftermath

File:Cyclone Zoe 31 dec 2002 2230Z.jpg
Cyclone Zoe situated between the Solomon Islands and Fiji on December 31

Severe Tropical Cyclone Zoe primarily affected the Solomon Islands of Anuta, Tikopia, Vanikoro, Utupua and the uninhabited island of Fatutaka between December 27–30, 2002.[11] The system and associated trough of low pressure, subsequently impacted Fiji and the northern islands of Vanuatu.[1][12] However, there were no deaths reported, as a result of Severe Tropical Cyclone Zoe.[13] As a result of the impact of this system, the name Zoe was retired from the South Pacific tropical cyclone naming lists by the World Meteorological Organization.[14]

Early on December 26, both RSMC Nadi and TCWC Brisbane started to issue warnings to support the meteorological services of Vanuatu and the Solomon Islands in tracking the cyclone. TCWC Brisbane cancelled their advisories for the Solomon Islands, late on December 29 while RSMC Nadi continued to issue advisories for Vanuatu until early the next day. Due to a number of problems with the Solomon Islands Weather Service, such as the rent not being paid on the offices they were working out of and the supply of electricity being unreliable, TCWC Brisbane sent the first advisory directly to the Solomon Islands Broadcasting Corporation (SIBC), so they could broadcast them through its network. These were broadcast in English only. After confirmation that the warnings were being received by the SIBC, TCWC Brisbane started to pass warnings to them every 3 hours. The next day Radio Australia was contacted so that arrangements could be made for them to receive and broadcast the warnings. Initial concerns that warning messages had not gotten through arose because there was no two-way radio communication with people on either Tikopia or Anuta, thus authorities had no way of knowing what information people had received and no other way of informing them. However, when communications were restored after the cyclone threat had passed it was discovered that some of the warnings had been received when a shortwave reception was available at various times, until late on December 27 when communications were cut. Those people who could not understand the warnings, were advised by runners who went from hut to hut and to churches to advise people about the oncoming storm, People started preparing straight away cutting Palm fronds and banana trunks in an attempt to support and strengthen roofs and walls. Celebrations to celebrate the new year were cancelled, or moved into communal huts with people sheltering indoors. There were no attempts to evacuate until Zoe had become so intense that dwellings were threatened with imminent inundation or had begun to break up.

Although Zoe never met large land masses, it did affect several inhabited islands which had a total population of around 1700.

The most severe damage wrought by Zoe took place on Tikopia which was completely decimated. Across Tikopia, no home was left standing after 12 m (39 ft) waves along with 320 km/h (200 mph) winds battered the small island. According to press reports, the island was faced with total devastation and all that remained was "just sand and debris."[15] Five days after the storm struck, there were fears of substantial loss of life as no contact had been made with the hardest hit islands. A photographer who took images of the devastation from the air, stated that it would be a miracle if there was not a large loss of life.[16]

On Anuta 90% of houses remained intact, and 70% of crops undamaged. Communication was lost with the island for a week. Vanuatu was inundated with seawater with villagers collecting fish from their village greens. No damage was reported on Fiji with a maximum sustained wind of 33 kn (61 km/h) at Yasawa, and a gust of 40 kn (74 km/h) at Nadi.

Aftermath

Within days of Zoe's passage, the government of the Solomon Islands declared the affected islands disaster zones. Relief supplies were sent from Honiara by January 5 and international aid followed shortly thereafter. Requests for assistance from New Zealand, Australia and France were made by the Solomon Islands.[15] For nearly a week, residents on Tikopia survived without aid by drinking coconut milk and eating what remained of their food stocks. The first relief vessel finally arrived in the island on January 6, bringing medical supplies and food. Although the island's residents had no warning prior to Zoe's arrival, it was found that they took notice of natural warning signs and sought shelter in caves, resulting in no loss of life.[17] Additional supplies were shipped to Anuta on January 6 by a local ship.[17]

Supplies were delayed for days by Solomon Island police as they requested further pay before shipping supplies to the islands. Against the millions of dollars pledged by Australia, only $270,000 had been provided by January 4.[18]

Notes

References

  1. 1.0 1.1 1.2 1.3 1.4 1.5 1.6 Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 2.2 2.3 2.4 2.5 2.6 2.7 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 7.2 7.3 7.4 7.5 Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 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. 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. Lua error in package.lua at line 80: module 'strict' not found.
  15. 15.0 15.1 Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. 17.0 17.1 Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.

See also

External links