The 2015 North Indian Ocean cyclone season was an event in the annual cycle of tropical cyclone formation. The North Indian Ocean cyclone season has no official bounds, but cyclones tend to form between months of April and December, with the peak from May to November. These dates conventionally delimit the period of each year when most tropical cyclones form in the northern Indian Ocean.
The season started rather late compared to the last two years, with the first storm, Ashobaa, not developing until June 7. Ashobaa was followed by 2 depressions, before Komen formed in July. Komen produced torrential rainfall in Bangladesh. September featured no storms, before Chapala formed at the end of October. Chapala rapidly intensified over the Arabian Sea into an Extremely Severe Cyclonic Storm, becoming the strongest in the Arabian Sea since Gonu in 2007. Chapala also became the only hurricane force system to make landfall in Yemen, and the first since 1922 in Socotra. Chapala was followed by Megh, which reached a weaker intensity in the same general area.
Under the influence of an ongoing onset of a southwest monsoon, a low-pressure area formed on June 6. It slowly consolidated, prompting the Joint Typhoon Warning Center (JTWC) to issue a Tropical Cyclone Formation Alert (TCFA) on June 6.[2] The following day, the India Meteorological Department (IMD) issued its first advisory for the system, designating it ARB 01. Later the same day, the JTWC reported the storm had reached tropical cyclone intensity, and on June 8, the IMD upgraded the storm to a cyclonic storm, assigning it the name Ashobaa. The storm continued to track northwestwards for a while, before turning westwards and weakening due to moderate to high wind shear and land interaction.
Due to most of the moisture being drawn into the storm, the onset of the southwest monsoon over the Indian subcontinent was stalled.[3] Torrential rains fell across much of eastern Oman, with Masirah Island receiving 225 mm (8.9 in) of rain in one day and more than 250 mm (9.8 in) overall.[4][5] Significant flooding prompted dozens of evacuations while strong winds caused power outages.[6] Waterlogging was reported in Kalba and Fujairah, in the United Arab Emirates, due to disturbed weather attributed to Ashobaa.[7]
An area of low pressure developed off the east coast of India on June 17, about 135 nmi (250 km; 155 mi) east-southeast of Visakhapatnam.[8] Over the next two days, deep convection developed along the southern and western periphery of the centre of the system, predominantly under the influence of the advancing southwest monsoon.[9] Due to the moderate-to-strong wind shear caused by the monsoon, the disturbance failed to develop any further, and the JTWC had reported that it dissipated on June 20.[10] At the same time, however, the IMD started tracking this system as a depression, reporting gusts of up to 35 kn (65 km/h; 40 mph).[11][12] The depression made landfall over Odisha coast early on June 21, between Gopalpur and Puri.[13] Without any further information, the IMD stopped tracking BOB 01 on June 22.[14]
Rough seas from the depression caught many fishing vessels off-guard, with at least 150 people reported missing offshore on June 21.[15] The vast majority either returned to shore safely or were rescued within a day; however, nine fishermen are feared to have drowned.[16] The entire state of Odisha was put on alert on June 21–23. The system brought heavy rains to most of the state, with Malkangiri receiving the highest, 320 mm (13 in) of rain.[17] Access to many towns in the Malkangiri district was blocked due to flooding.[18] At least six deaths took place from flood-related incidents.[15]
Following the series of monsoonal disturbances, a fresh wave of thunderstorms organized into an area of low pressure on June 21, in the Arabian Sea, off the coast of Gujarat.[19] Deep convection persisted to the west of the system while the circulation continued to develop over the next 24 hours,[20] and the IMD started tracking it as a depression, with the identifier ARB 02.[14] ARB 02 continued to evolve and by the night of June 22, the JTWC issued a TCFA on the system, while it was 285 nmi (528 km; 328 mi) west-northwest of Mumbai.[21]
Torrential rains battered Gujarat, with peak accumulations of 636 mm (25.0 in) in Bagasara, 511 mm (20.1 in) in Dhari, and 400 mm (16 in) in Variyav. Severe flooding ensued across the region, isolating many villages in the Saurashtra region, and prompted mobilization of the National Disaster Response Force and Indian Air Force.[22] Flooding in the Amreli district was reported to be the worst in 90 years; 600 of the district's 838 villages were affected, 400 of which were rendered inaccessible by land.[23] At least 80 people died in the region, with Saurashtra suffering the greatest losses.[24] Ten Asiatic lions, an endangered species with only 523 living individuals documented in May 2015, died during the floods while more than a dozen remain missing.[25][26] The Gujarat government estimated damage at ₹16.5 billion (US$258 million); however, Congress MLA Paresh Dhanani claimed damage to be as high as ₹70 billion (US$1.09 billion).[27]
At 03:00 UTC (08:30 AM IST) on July 10, a depression formed over land over Jharkhand, close to Ranchi. It drifted in a generally northwestward direction and dissipated early on July 12 over the periphery of Uttar Pradesh and adjoining areas of Haryana.
The system produced extremely heavy downpours, breaking the record in the city of Gwalior, Madhya Pradesh for the maximum amount of rainfall in 24 hours. The city received 191 mm (8 in) of rainfall in a day breaking the previous record of 149.9 mm (6 in) which was set around the same period in 1947. The rainfall received was also more than 75% of the average monthly rainfall of 250.7 mm (10 in) in the city.[28] In Odisha, at least 14 villages were inundated by floods directly linked to the depression. The Hirakud Dam authorities had announced that they would be releasing waters on July 13 from the river Mahanadi.[29] The states of Uttar Pradesh and Haryana also received torrential rains from the system.[30]
On July 26 a depression formed inland over the Ganges delta. Early on July 30, the system was upgraded to a cyclonic storm by the IMD and named as Komen while making a U-turn. On August 2, Komen was no longer a tropical cyclone.[31]
Torrential rains impacted much of Myanmar, causing widespread flooding. At least 46 people were killed and more than 200,000 were affected.[32] Additionally, at least 17,000 homes were destroyed.[33][34] Tremendous rains fell across southeastern Bangladesh, with accumulations Komen and the monsoonal system it originated from reaching 1,051.2 mm (41.39 in) in Chittagong.[35] The resulting floods killed at least 23 people and affected more than 130,400.[36][37] A landslide in the Bandarban District killed six people.[38] Flooding in Odisha, India, killed five people and affected at least 480,399.[39] At least 69 people died across West Bengal from various incidents directly and indirectly to the storm, such as electrocution and snake bites. A total of 272,488 homes were destroyed while a further 55,899 sustained damage.[40][41] At least 21 people died in Manipur, 20 of whom perished in a landslide that struck Joumol village.[42]
A trough over Madhya Pradesh drifted westwards into eastern Rajasthan and lead to the formation of an area of low pressure in its vicinity on July 24. Continuing on its westward track, the system became more organised and intensified into a depression on July 27, to the west of Jodhpur. A western disturbance over Pakistan and adjoining areas of Jammu and Kashmir kept the system from moving further north into drier portions of Rajasthan. This allowed it to intensify further into a deep depression, about 110 km (68 mi) southeast of Barmer. However, the system accelerated in a chiefly northward track on July 29, absorbing dry air along its path. It weakened rapidly and dissipated to the north of Bikaner on the following day.[43]
A depression formed in Madhya Pradesh on 4 August and has a maximum winds of 45 km/h (30 mph). One day later it weakened as well marked low-pressure area. It made its impact in Madhya Pradesh.[45]
In early October, a low-pressure area formed over the Arabian Sea. It slowly consolidated, prompting the JTWC to issue a TCFA on October 7. On October 9, the IMD started issuing its advisories for the system, designating it ARB 03. During the late hours of October 9, the JTWC stated the storm had reached gale-force winds, and commenced its advisories. On the following day, the depression intensified into a Deep depression, reaching its peak intensity with sustained wind speeds at 55 km/h (35 mph) and a minimum central pressure estimated near 1,001 mbar (29.56 inHg). On the following days, the storm followed a generally northwestward track, where it encountered areas having low mid-to-upper level moisture in the atmosphere. The system struggled to maintain its intensity and weakened, prompting the JTWC to issue its final warning on ARB 03 in the morning of October 11. On next day, IMD reported that the storm had degenerated into a well-marked low-pressure area.
The storm, being over water during its entire lifespan, did not directly impact any landmass. However, under the influence of the storm's rain bands, heavy Rains lashed the Kanyakumari district of Tamil Nadu, India. The reservoir of Chittar I, a dam near Kanyakumari, recorded 216.4 mm (8.52 in) of rainfall.[46]
A low-pressure area formed over the Arabian Sea on October 26.[47] It slowly consolidated, prompting the IMD to classify it a depression on October 28.[48] Later the same day, the JTWC issued its Tropical Cyclone Formation Alert (TCFA) for the system, and the IMD upgraded the storm to deep depression intensity.[49][50] Further intensification ensued, causing the IMD to upgrade the system to a cyclonic storm, naming it Chapala.[51] Over the following hours, the storm intensified into a severe cyclonic storm and further into a very severe cyclonic storm.[52][53]Rapid intensification commenced and Chapala was upgraded into an extremely severe cyclonic storm on October 30.[54] On November 3, it made landfall in Yemen as a very severe cyclonic storm, making it the first tropical cyclone at hurricane intensity to make landfall in the country on record.[55] Chapala rapidly weakened over the mountainous terrain of mainland Yemen and was last noted as a low-pressure area the following day.
Chapala caused widespread damage in mainland Yemen, Socotra and the Puntland region of Somalia. High winds, strong waves, and heavy rainfall affected the southern Yemen coast, with areas in the region receiving 610 mm (24 in) of rainfall over 48 hours, or 700% of the average yearly precipitation. The storm caused severe flooding along the coast, including in Mukalla, the nation's fifth largest city, where the seafront was destroyed by waves exceeding 9 m (30 ft). While passing north of Socotra, Chapala brought heavy rainfall and high winds while inundating the northeastern part of the island. Large swells produced by Chapala caused extensive coastal damage in eastern Puntland, with multiple structures, boats, and roads destroyed. An Iranian vessel capsized offshore on November 1, killing one person.[citation needed]
A low-pressure area consolidated into a depression on November 5.[56] It intensified further, prompting the JTWC to issue a TCFA and the IMD to upgrade it into a deep depression.[57][58] In the following days, the storm's convection flourished as environmental conditions recuperated. By November 8, Megh rapidly intensified into a marginal Extremely Severe Cyclonic Storm, peaking with winds exceeding 175 km/h (110 mph) and a minimum central pressure of 964 mbar (28.47 inHg). Maintaining intensity, the storm made its first landfall over Socotra and headed west, skirting the northern tip of Somalia. Megh took a west-northwestward turn, and made its second landfall over the coast of Yemen on November 10 and weakened into a well-marked low-pressure area over mainland Yemen.
Megh's landfall over the island of Socotra as a Category 3-equivalent storm caused extensive devastation, killing at least eighteen people and injuring dozens of others.[59] Another six people were left missing on the island. More than 500 houses were completely destroyed and another 3,000 were damaged.[60] In addition, hundreds of fishing boats were damaged and more than 3,000 families were displaced as a result of Megh.[61][62]
A low-pressure area consolidated into a depression on November 8. It slowly intensified, prompting the JTWC to issue a Tropical Cyclone Formation Alert (TCFA) for the system, but was eventually cancelled despite the improving appearance prior to landfall. The IMD later upgraded the system to a deep depression before it crossed the coast of Tamil Nadu near Puducherry the following day with peak wind speeds of 55 km/h (35 mph) and a minimum central pressure of 991 hPa (29.26 inHg). Due to land interaction and high vertical wind shear, the system weakened into a well-marked low-pressure area over north Tamil Nadu on November 10.
The storm brought heavy rainfall over the coastal districts of Tamil Nadu. Neyveli, a mining township southwest of Puducherry, recorded 139 mm (5.5 in) of rainfall on November 9 and 483 mm (19.0 in) of rainfall on November 10[63] of which 450 mm (18 in) fell within a span of 9 hours.[64] At least 71 people were killed in various incidents, predominately related to flooding, across Tamil Nadu.[65][66]
Season effects
This is a table of all storms in the 2015 North Indian Ocean cyclone season. It mentions all of the season's storms and their names, duration, peak intensities (according to the IMD storm scale), damage, and death totals. Damage and death totals include the damage and deaths caused when that storm was a precursor wave or extratropical low, and all of the damage figures are in 2015 USD.
![[icon]](File:Wiki_letter_w_cropped.svg){kind=small}
.jpg)
