This is a good article. Click here for more information.

2004 North Indian Ocean cyclone season

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
2004 North Indian Ocean cyclone season
Season summary map
First system formed May 5, 2004
Last system dissipated December 2, 2004
Strongest storm1 BOB 01 – 952 hPa (mbar), 165 km/h (105 mph) (3-minute sustained)
Depressions 10
Deep depressions 7
Cyclonic storms 4
Severe cyclonic storms 3
Very severe cyclonic storms 1
Total fatalities 587 total
Total damage $129.8 million (2004 USD)
1Strongest storm is determined by lowest pressure
North Indian Ocean tropical cyclone seasons
2002, 2003, 2004, 2005, 2006

The 2004 North Indian Ocean cyclone season was the first in which tropical cyclones were officially named in the basin. Cyclone Onil, which struck Pakistan, was named in late September. One other storm, Cyclone Agni, was also named, which crossed into the southern hemisphere during its origins and became one of the storms closest to the equator. The season was fairly active, with ten depressions forming from May to November. The India Meteorological Department designated four of these as cyclonic storms, which have maximum sustained winds of at least 65 km/h (40 mph) averaged over three minutes. The Joint Typhoon Warning Center also issued warnings for five of the storms on an unofficial basis.

In early May, two tropical storms formed on opposite sides of India. The first formed on May 5 and meandered while intensifying, dropping 1,840 mm (72 in) in Aminidivi in the Lakshadweep group offshore western India, which was the highest daily rainfall total in the basin. A week later, a cyclone – the strongest of the season – struck Myanmar, killing 236 people and leaving 25,000 people homeless. Depressions also formed on opposite sides of India in June. A depression in September killed 59 people after dropping torrential rainfall over Bangladesh and adjacent West Bengal. In October, another depression struck the region, killing 273 people. There was also a short-lived cyclonic storm in the Arabian Sea in November.

Season summary

The India Meteorological Department in New Delhi (IMD) was designated a Regional Specialized Meteorological Center by the World Meteorological Organization in July 1988 to monitor and warn on tropical cyclones in the northern Indian Ocean. The basin is defined between 45° and 100° E, and north of the equator. The agency also used geostationary satellites and a network of buoys to track the storms, and utilized various tropical cyclone forecast models to predict future tracks.[1] The American-based Joint Typhoon Warning Center (JTWC) also issued warnings for storms in the basin on an unofficial basis.[2]

The monsoon became active in May as water temperatures became warm.[3] Twin depressions formed during June on opposite sides of India, which helped intensify the monsoon over the country. A notable feature of the season was the Arabian Sea being more active than the Bay of Bengal.[1] The IMD began naming tropical cyclones within the basin in 2004, beginning after the monsoon season. As such, only two cyclonic storms in the latter half of the year were named.[1]

Storms

Cyclonic Storm ARB 01

Severe cyclonic storm (IMD)
Tropical storm (SSHWS)
150px 150px
Duration May 5 – May 10
Peak intensity 100 km/h (65 mph) (3-min)  989 hPa (mbar)

Toward the end of April, an area of convection persisted in the southern Bay of Bengal.[4] It developed into a distinct low pressure area on May 1 over the body of water, but soon moved westward into India without developing. On May 4, the system emerged from Kerala into the Arabian Sea,[1] and soon after convection rapidly increased. Early on May 5, the JTWC classified the system as Tropical Cyclone 01A about 370 km (230 mi) west-southwest of Kochi, India.[4] On the same day, the IMD began classifying it as a depression, but soon after upgraded it to a deep depression and later cyclonic storm after increased organization.[1] The storm meandered off southwest India for three days due to weak steering currents. During that time, the convection pulsed around the circulation,[4] and the IMD upgraded it to a severe cyclonic storm on May 7 with winds of 100 km/h (55 mph).[1] By contrast, the JTWC only estimated peak winds of 85 km/h (50 mph).[2] Increased wind shear, cooler waters, and dry air rapidly weakened the convection, exposing the center and causing the storm to deteriorate quickly into a depression. On May 10, the system degenerated into a remnant low off Gujarat, without any discernible low-level circulation.[1][4]

The precursor to the storm brought heavy rainfall to southern India, reaching 124.8 mm (4.91 in) in Thiruvananthapuram over 48 hours.[4] The remnants also brought upwards of 225 mm (8.9 in) of rainfall in Gujarat.[5] While an active tropical cyclone, the storm dropped torrential rainfall to the Lakshadweep group offshore western India. Aminidivi recorded 1,840 mm (72 in) over three days, including 1,170 mm (46 in) in just 24 hours.[1] This broke the record for the highest daily rainfall total related to a North Indian Ocean cyclone.[6] The high rains cut communications from the island group to the mainland, and damaged 45 houses in conjunction with the winds. High waves sank 15 boats and one cargo ship while also causing erosion in Kerala. The storm killed nine people and caused ₹300 million rupees ($6.7 million USD).[1]

Extremely Severe Cyclonic Storm BOB 01

Extremely severe cyclonic storm (IMD)
Category 1 tropical cyclone (SSHWS)
150px 150px
Duration May 16 – May 19
Peak intensity 165 km/h (105 mph) (3-min)  952 hPa (mbar)

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

The second storm of the season formed as a depression on May 16 in the central Bay of Bengal. With low wind shear and a surge in the monsoon trough, the storm intensified while meandering over open waters. The storm eventually began a steady northeastward motion due to a ridge to the north over India. While approaching land, an eye developed in the center of the storm, indicative of a strong cyclone. On May 19, the cyclone made landfall along northwestern Myanmar near Sittwe, with maximum sustained winds estimated at 165 km/h (105 mph) by the IMD.[1][2][4] The storm rapidly weakened over land, although its remnants spread rainfall into northern Thailand and Yunnan province in China.[4]

Winds from the cyclone reached 157 km/h (98 mph) in Myanmar,[4] occurring in conjunction with heavy rainfall and a high storm surge.[7] Despite the storm's ferocity, the government did not report about the cyclone for ten days, as they usually under report on landfalling storms.[8] The cyclone caused heavy damage throughout Rakhine State, destroying or heavily damaging 4,035 homes and leaving 25,000 people homeless.[9][10] There was widespread crop damage, resulting in food shortages, and damaged roads disrupted subsequent relief efforts.[8][11][12] Damage in Myanmar totaled over K621 million kyat ($99.2 million USD), making it the worst storm in the country since 1968, and there were 236 deaths.[7][13] Although damage was heaviest in Myanmar, the cyclone's effects also spread into neighboring Bangladesh, where strong winds knocked over trees and capsized two ships.[4]

Deep Depression ARB 02

On June 8, a low pressure area formed in the eastern Arabian Sea. A nearby buoy recorded winds of 45 km/h (30 mph), which was the basis for the IMD declaring the system a depression on June 10. While remaining nearly stationary, the depression quickly intensified into a deep depression. The system later began a slow westward movement due to a ridge to the north.[1] On June 11 and again on the following day, the JTWC issued a Tropical Cyclone Formation Alert (TCFA), although the system never strengthened beyond its initial stages.[14] Strong wind shear caused the depression to weaken, and the IMD downgraded it to a remnant low on June 13.[1]

Deep Depression BOB 02

A surge in the monsoon developed an area of convection over the Andaman Sea in early June, spawning a low pressure area and later depression on June 11. Moving to the northwest along a ridge, it strengthened into a deep depression the next day. Early on June 13, the system struck Odisha near Puri, and initially maintained its intensity over land. However, it eventually weakened on June 14, degenerating into a remnant low over Chhattisgarh. The depression dropped heavy rainfall in eastern India, particularly Odisha. There, the peak 24‑hour precipitation total was 320 mm (13 in) in Madanpur Rampur. There were no reports of damage.[1]

Land Depression BOB 03

Depression (IMD)
150px
Duration September 12 – September 15
Peak intensity 45 km/h (30 mph) (3-min)  996 hPa (mbar)

For about ten days in September, a monsoon depression persisted around the northern edge of the Bay of Bengal onto adjacent landmasses, initially associated with a upper-level low.[15] On September 10, a low pressure area developed within the monsoon trough in the extreme northern Bay of Bengal. Moving northwestward, it organized into a depression after it moved ashore, organizing over West Bengal near Kolkata. The system attained peak winds of 45 km/h (30 mph) despite being over land. Located within a col, or weakness between ridges, the depression meandered over eastern India, weakening into a remnant low on September 15.[1] It moved slowly northwestward, reaching Uttar Pradesh by September 22.[15]

The depression dropped heavy rainfall in eastern India, including as a tropical cyclone, a precursor,[1] and its remnant.[15] Notable rainfall totals include 340 mm (13 in) in Chepan on September 9,[1] 480 mm (19 in) on September 21 at a station in Uttar Pradesh,[15] and 341 mm (13.4 in) in Dhaka in neighboring Bangladesh, the heaviest daily total in 50 years.[16] Flash flooding in the Indian state of Tripura killed four people and isolated about 55,000 people. Three people died in West Bengal, where floodwaters left about 650,000 people homeless in hundreds of villages. Flash flooding in Uttar Pradesh killed 33 people overnight on September 21.[15] In nearby Bangladesh, the depression produced additional flooding after a similar disaster occurred in July, temporarily isolating about 1 million people, and killing 19.[16]

Severe Cyclonic Storm Onil

Severe cyclonic storm (IMD)
Tropical storm (SSHWS)
150px
Duration September 30 – October 10
Peak intensity 100 km/h (65 mph) (3-min)  990 hPa (mbar)

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

A depression formed out of an area of convection southwest of India on September 30. The next day, it intensified into Cyclonic Storm Onil.[1] becoming the first tropical cyclone on record to be named in the northern Indian Ocean.[17] Cyclone Onil quickly attained its peak intensity on October 2 with winds of 100 km/h (65 mph) and a barometric pressure of 990 mbar (hPa; 29.23 inHg). However, dry air quickly entered the system, causing it to rapidly weaken to a depression just off the coast of Gujarat, India. Over the following several days, the system took a slow, erratic track towards the south-southeast. After turning northeastward, the system made landfall near Porbandar on October 10 and dissipated shortly thereafter.[1][18]

Throughout southeastern Pakistan and northwestern India, thousands of residents were evacuated prior to the cyclone's arrival. In these areas, the storm produced moderate to heavy rainfall, peaking at 145 mm (5.7 in) in Thatta, Sindh, Pakistan.[18] These rains led to flash flooding in several areas. Nine people died in several incidents related to the storm in Karachi.[19] The drainage system of Hyderabad sustained significant damage, leading to several protests and demonstrations by city residents.[20][21] Offshore, 300 fishermen are believed to have gone missing during the storm.[22]

Depression BOB 04/05

Depression (IMD)
150px
Duration October 2 – October 8
Peak intensity 45 km/h (30 mph) (3-min)  1002 hPa (mbar)

A low pressure area formed in the Bay of Bengal on September 30 and gradually became more organized. It moved northwestward and developed into a depression on October 2. Without intensifying beyond winds of 45 km/h (30 mph), the depression moved ashore Andhra Pradesh near Kalingapatnam on October 4. It rapidly weakened into a remnant low and turned to the northeast. On October 7, the system re-intensified into a depression near Bankura despite being over land, aided by moisture from the Bay of Bengal.[1] After crossing into northern Bangladesh, the system again weakened into a remnant low,[1] which gradually elongated and weakened.[18]

For several days in early October, the depression dropped rainfall across southeastern India, which was heaviest after it re-intensified over land. Alipurduar in northeastern West Bengal recorded 310 mm (12 in) in a 24‑hour period, and Malda reported 430 mm (17 in) in two days.[1] In northern Andhra Pradesh, flooding from the depression affected 40 villages, wrecking 50 houses. The waters also inundated 50,000 acres (20,000 ha) of rice paddies and damaged 200 irrigation water tanks. In West Bengal, the floods killed 3,000 migratory birds and damaged ₹1.1 billion rupees ($23.9 million USD) worth of crops; 51 people also died in the state. In neighboring Odisha, four people were killed, and the floods washed away a bridge and affected several villages.[1]

The third large flood event of the year,[23] the depression caused its most severe impact in northeastern India, where 218 people were killed,[1] including 112 in the city of Goalpara alone.[24] There, the floods struck in the middle of the night, catching residents off guard and washing away hundreds of houses along two whole blocks.[23] Flash flooding caused landslides in Kamrup, while regional and national roads were damaged or submerged. Over 15,000 people were forced to evacuate their homes to emergency shelters.[24] Across the region, 98,721 ha (243,940 acres) of crops were damaged,[1] and 30,000 homes were damaged or destroyed.[23] Rainfall spread into Nepal, where 51.3 mm (2.02 in) was recorded at the airport in Kathmandu. The precipitation led to a snowstorm in Tibet, reaching 60 mm (2.4 in) in one location; this marked the highest daily snowfall for the station in October, and caused a loss of crops and livestock.[18]

Deep Depression ARB 04

Deep depression (IMD)
Tropical storm (SSHWS)
150px 150px
Duration November 2 – November 7
Peak intensity 55 km/h (35 mph) (3-min)  1004 hPa (mbar)

An area of convection formed west of Sri Lanka on October 31, organizing around a circulation center. Low wind shear allowed slow development,[25] and a low pressure area developed on November 1 in the southeastern Arabian Sea. The following day, a depression formed off the southwest coast of India.[1] Moving northward, the system's convection continued to organize around the center, and the JTWC classified it as Tropical Cyclone 04A on November 4.[25] The IMD upgraded it to a deep depression on the next day as the storm began moving westward.[1] Despite good outflow, the convection failed to intensify further and was limited to the eastern portion, and the JTWC did not estimate 1 minute winds higher than 75 km/h (45 mph).[25] The IMD only assessed a peak of 55 km/h (35 mph).[1] Drier air from the north caused the thunderstorms to weaken and expose the circulation.[25] The IMD downgraded the system to a remnant low on November 7,[1] and the remnants continued to the west-southwest, passing near Socotra Island. On November 9, the remnant circulation brushed the coast of Somalia after redeveloping some convection, but there was no redevelopment.[25]

Severe Cyclonic Storm Agni

Severe cyclonic storm (IMD)
Category 1 tropical cyclone (SSHWS)
150px 150px
Duration November 27 – December 4
Peak intensity 100 km/h (65 mph) (3-min)  994 hPa (mbar)

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

A tropical disturbance was observed on November 19 about 800 km (500 mi) southeast of Colombo, Sri Lanka in the Bay of Bengal.[26] The disturbance tracked westward, weakening after passing south of Sri Lanka.[25] It entered the Arabian Sea on November 26, and despite being located unusually close to the equator, the system maintained convection about its circulation, aided by low wind shear.[25] While the system was organizing, the center crossed the equator to reach about 0.5° S, thus becoming an anticyclonic circulation in the southern hemisphere. This was unusual, as the Coriolis effect is nonexistent along the equator—the Coriolis effect refers to planetary vorticity, which provides the spin in a cyclone.[26][27] On November 28, the JTWC classified it as Tropical Cyclone 05A just 78 km (48 mi) from the equator.[25] The IMD classified it as a depression the next day at 1.5° N, noting that "cyclogenesis... at such low latitudes has not occurred in the past."[1] It rivaled Tropical Storm Vamei as one of the closest storms to the equator.[25]

After developing, the system moved northwestward due to a ridge over India.[25] The IMD upgraded the depression to Cyclonic Storm Agni late on November 29 and further to a severe cyclonic storm the next day.[1] The JTWC also upgraded Agni to the equivalent of a minimal hurricane, estimating 120 km/h (75 mph). Wind shear and dry air caused the storm to weaken.[25] After Agni turned westward, the IMD downgraded it to a depression and later remnant low on December 2,[1] although the JTWC tracked it for another day, issuing their final advisory while Agni was about 450 km (275 mi) south-southeast of Cape Guardafui—the easternmost point of the Horn of Africa.[25] The remnants moved ashore on eastern Somalia before turning to the south and dissipating on December 5.[2]

See also

References

  1. 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 1.18 1.19 1.20 1.21 1.22 1.23 1.24 1.25 1.26 1.27 1.28 1.29 1.30 Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 2.2 2.3 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. 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 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 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 15.2 15.3 15.4 Lua error in package.lua at line 80: module 'strict' not found.
  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 Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. 23.0 23.1 23.2 Lua error in package.lua at line 80: module 'strict' not found.
  24. 24.0 24.1 Lua error in package.lua at line 80: module 'strict' not found.
  25. 25.00 25.01 25.02 25.03 25.04 25.05 25.06 25.07 25.08 25.09 25.10 25.11 Lua error in package.lua at line 80: module 'strict' not found.
  26. 26.0 26.1 Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.

External links