The scope of this article is limited to the Indian Ocean in the Northern Hemisphere, east of the Horn of Africa and west of the Malay Peninsula.

It slowly consolidated, prompting the Joint Typhoon Warning Center (JTWC) to issue a Tropical Cyclone Formation Alert (TCFA) on June 6.

The storm continued to track northwestwards for a while, before turning westwards and weakening due to moderate to high wind shear and land interaction.

[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.

[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.

[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.

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.

[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.

[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.

A western disturbance over Pakistan and adjoining areas of Jammu and Kashmir kept the system from moving further north into drier portions of Rajasthan.

Chief Minister of Gujarat Anandiben Patel ordered rescue teams to carry out relief activities in Kutch, Patan, Banaskantha, and other districts of the state, as a result.

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.

[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.

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.

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).

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.

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.