Physical Address
23,24,25 & 26, 2nd Floor, Software Technology Park India, Opp: Garware Stadium,MIDC, Chikalthana, Aurangabad, Maharashtra – 431001 India
Physical Address
23,24,25 & 26, 2nd Floor, Software Technology Park India, Opp: Garware Stadium,MIDC, Chikalthana, Aurangabad, Maharashtra – 431001 India

The Bay of Bengal witnessed a rapidly evolving weather system this week as Cyclone Akvan kept meteorologists guessing over its movement, intensity and potential landfall. Initially projected to strike the Andhra Pradesh coast as a very severe cyclonic storm, the system changed its course and weakened before making landfall near Gopalpur in Odisha on November 20. Its changing trajectory and varying intensity forecasts highlighted the challenges of predicting tropical cyclones, particularly when atmospheric conditions are constantly shifting.
The India Meteorological Department (IMD) had initially forecast that Akvan would cross the Andhra Pradesh coast between Nellore and Tuni around November 20. However, subsequent forecasts shifted the expected landfall zone northwards, towards the stretch between Narsapur in Andhra Pradesh and Puri in Odisha, close to Gopalpur. The changing projections brought different parts of India’s eastern coastline under heightened surveillance.
A slow-moving cyclone with a shifting trajectory
According to the IMD’s November 18 update, Cyclone Akvan was located approximately 540 kilometres southeast of Narsapur in Andhra Pradesh and 570 kilometres east of Chennai at 11.30 am. The agency projected that the storm could cross the coast between Narsapur in Andhra Pradesh and Puri in Odisha around noon on November 20. At the time, sustained wind speeds were estimated at 90–100 kilometres per hour, with gusts reaching 110 kmph.
This represented a notable shift from an earlier forecast issued just hours before, which had placed the likely landfall between Nellore and Visakhapatnam in Andhra Pradesh. That forecast had also indicated higher wind speeds of 100–110 kmph, with gusts of up to 120 kmph. The cyclone’s movement has been another source of concern. During the night of November 17–18, Akvan moved at a remarkably slow speed of around 3 kmph. Its forward speed subsequently increased to approximately 7–8 kmph on the morning of November 18.
Explaining this sluggish movement, the IMD pointed to the system’s position within a region between two anticyclones, known as a Col region. The cyclone was also moving through an environment of moderate vertical wind shear, which contributed to its slow intensification. Vertical wind shear refers to changes in wind speed or direction at different atmospheric heights. When these conditions are unfavourable, they can disrupt a cyclone’s structure and limit its development. The IMD indicated that a ridge to the east of the system was likely to influence its movement from November 18 onwards, steering it towards the northwest or north-northwest at a faster pace.
What actually happened? Akvan weakens before landfall
The latest developments on November 20 brought greater clarity. According to the Indian Express’s live updates and the IMD’s hourly bulletin, Cyclone Akvan weakened from a severe cyclonic storm into a cyclonic storm before crossing the coast. The landfall process began near Gopalpur, along the south Odisha and north Andhra Pradesh coastline, between 7.30 am and 8.30 am on November 20. At the time of crossing, the system was packing sustained wind speeds of 70–80 kmph, with gusts reaching 90 kmph.
The IMD’s 10.20 am bulletin placed the cyclone near latitude 19.30°N and longitude 84.90°E, close to Gopalpur. It had moved north-northwestwards at approximately 24 kmph during the preceding six hours. The department expected the system to continue moving north-northeastwards and gradually weaken into a deep depression within three hours, followed by a depression over the subsequent six hours. Although its wind intensity had reduced, the cyclone brought substantial rainfall to the affected regions. IMD observations for the 24 hours ending 8.30 am on November 20 recorded 209 mm of rainfall at Patrapur, 207 mm at Hinjili, 199 mm at Chikiti and 190 mm at Gopalpur in Odisha. In Andhra Pradesh, Ichchapuram recorded 168.75 mm during the same period.
The department also warned of a storm surge of approximately 0.3 metres above astronomical tide, with the possibility of inundation in low-lying areas of Ganjam and Puri districts. Preparations had intensified even before the cyclone made landfall. The IMD issued a red alert for six Andhra Pradesh districts, including Eluru, East Godavari, West Godavari, Kakinada, Krishna and Bapatla, warning of very heavy to extremely heavy rainfall. Several districts in Odisha and West Bengal were also placed under weather alerts.
Cyclone Akvan’s journey demonstrates why cyclone forecasting is not simply about predicting a storm’s destination. Its initial projected landfall, changing trajectory, weakening intensity and eventual crossing near Gopalpur illustrate how atmospheric conditions can alter a cyclone’s behaviour within a short period. While differences between weather models initially complicated the forecast, continuous satellite observations, meteorological assessments and updated warnings helped track its changing course. The episode also highlights an important distinction: a weakening cyclone does not necessarily mean diminishing rainfall-related risks. Flooding, waterlogging, storm surges and damage to vulnerable infrastructure can continue even after wind speeds fall.
As Akvan moves inland and weakens, its impact offers another reminder that effective disaster preparedness depends not only on anticipating a cyclone’s intensity but also on responding quickly as forecasts evolve.
https://pmc.ncbi.nlm.nih.gov/articles/PMC9925922
Banner Image: AI generated
Sections of this article may have been developed with the assistance of artificial intelligence tools to support research, drafting, and language refinement. All information has been reviewed, edited, and verified by the author/editor to ensure accuracy, context, and editorial integrity. The responsibility for the final content, interpretations, and conclusions rests solely with the publisher.