Cyclones Gulab and Shaheen

While slowly moving westward, the storm turned southwestward, subsequently making an extremely rare landfall in Oman on October 3, as a Category 1-equivalent cyclone.

Shaheen delivered extreme rainfall to Oman, causing flooding across a wide area of the country's northeastern governorates.

On September 24, the JTWC noted a cyclone that was producing tropical storm-force winds located over the east-central Bay of Bengal, 211 nmi (391 km; 243 mi) south of Chittagong, Bangladesh, designating the system as 03B.

[16][17] As it continued westward, the outer rainbands of Cyclone Gulab reached the coastal regions of northern Andhra Pradesh and southern Odisha, which indicated that it had started making landfall, at about 18:00 IST (12:30 UTC) on September 26.

[20] Three hours later, the IMD downgraded it to a deep depression, as it had lost its energy after travelling over rough Indian terrain.

[22] It maintained its intensity as it travelled westward, until at 14:00 IST (08:30 UTC), when it weakened into a well-marked low-pressure area over west Vidarbha.

At this time, the agency analyzed the system's environmental path as being conducive for tropical cyclogenesis, with warm 30–31 °C (86–88 °F) sea surface temperatures, enhanced outflow from an upper-level anticyclone and low wind shear.

[26][27] Later that day, at 18:00 UTC (23:30 IST), the IMD further upgraded the storm to a deep depression, while it was moving away from Gujarat; however, the JTWC continued issuing advisories on the system, referring to it as Gulab, with the agency reissuing advisories three hours later, with the system bearing maximum sustained winds of 40 knots (75 km/h; 45 mph).

[28][29] At 21:00 UTC (03:00 IST, October 1) on that day, the IMD reported that the system had further strengthened to a Cyclonic Storm, with the agency giving it the name Shaheen.

The storm's spiral bands were seen wrapping along its obscured low-level circulation center (LLCC), while its Dvorak rating stood at T2.5 at that time.

[30] At 15:00 UTC (20:30 IST), the IMD further upgraded it to a severe cyclonic storm, as the clouds had become well-organized moving with a defined curved pattern.

[39] After making landfall, Shaheen underwent rapid weakening, due to the dry landmass of the Arabian Desert.

As of September 26, over 30,000 individuals evacuated into safety as a result of the cyclone; this number further increased to 46,075 people as the storm further moved inland.

[44] Due to the brewing storm, which would become Shaheen, the Pakistan Meteorological Department (PMD) issued a tropical cyclone warning for the country on September 30, with the agency predicting heavy rains and strong winds in the Sindh-Makran coastal areas.

The agency also noted that sea conditions were risky for fishermen, advising them to avoid fishing activities until further notice.

[48] 55 emergency shelters in Muscat were also prepared for the evacuees and authorities declared October 3–4 to be a work holiday due to the storm.

The National Committee for Emergency Management (NCEM) also warned individuals within Shaheen's track to evacuate immediately; as of October 3, 2,734 persons were now in government and other safety shelters to ride out the storm.

[51][52] The Dubai Municipality announced temporary closure of Hatta Parks and other community facilities, while schools in the area shifted to distance learning.

[53] The National Centre of Meteorology issued a code red alert off the eastern coast with a warning of 10-foot waves off-shore and wind speeds of 50 km/h (30 mph).

In Al Ain, residents were warned that they may have to briefly work from home, and have schools switch to distance learning temporarily.

A landslide occurred on National Highway 26 near Ralegada, Koraput, causing traffic and disruptions; however, the district's administration quickly restored the road.

[60] An overnight downpour flooded a portion of National Highway 26 near a government hospital, but a team from the Odisha Disaster Rapid Action Force (ODRAF) rescued the people inside.

Vizianagaram was flooded with waterlogging due to a bad subterranean drainage system, with hundreds of trees and signs falling elsewhere.

As a result, 20 teams of National Disaster Response Force (NDRF's) were deployed in the whole state for possible continuous rains.

[76] Nine more small irrigation dams overflowed in Kutch district as a result of three-day rains in the area while boats in the Arabian Sea were asked to return to ports for safety; 363 of them obeyed it while 474 remained in sea and were expected to return to ports by October 4.

The city's Millennium Mall on Rashid Minhas Road also saw heavy traffic due to three electric poles falling on the area.

[7][81] Five fishermen were missing after two fishing vessels sank off the coast of Sistan and Baluchestan Province, local medias in the country reported.

The Royal Oman Police rescued two people stranded in a wadi in Suwaiq on October 4 while the Al-Khoud dam was reported to be overflowed due to heavy rains.

[94] Authorities of the Civil Defence and Ambulance (CDAA) also saved several people who were stuck inside their vehicles.

[105] Due to a widespread lack of home insurance in Oman, many feared that money raised from private funds would not be enough to cover repairs.

Map plotting the storm's track and intensity, according to the Saffir–Simpson scale
Map key
Tropical depression (≤38 mph, ≤62 km/h)
Tropical storm (39–73 mph, 63–118 km/h)
Category 1 (74–95 mph, 119–153 km/h)
Category 2 (96–110 mph, 154–177 km/h)
Category 3 (111–129 mph, 178–208 km/h)
Category 4 (130–156 mph, 209–251 km/h)
Category 5 (≥157 mph, ≥252 km/h)
Unknown
Storm type
triangle Extratropical cyclone , remnant low, tropical disturbance, or monsoon depression
Cyclonic Storm Gulab in the Bay of Bengal on September 26
Gulab over Western India on September 28, as a well-marked low-pressure area.
Severe Cyclonic Storm Shaheen strengthening in the Arabian Sea on October 1