Skip to content
TOP NOW Did a Russian Lab Worker's Death Spark a New Plague Pandemic? / Instagram's New AI 'Muse': Creativity or Algorithmic Exploitation? / UK “rape capital” claim — what police data actually allows you to say
Rent Free News home rentfreenews. Claims vs data
Subscribe

Cyclone Arnab Hit Odisha Too: The Damage Record

Cyclone Arnab crossed the Andhra Pradesh coast near Narasapuram early on October 28, 2026. Odisha was hit just as hard, with landslides, 300 villages cut off and 1.18 lakh people affected.

Verdict: false alarm.

W
By Wasim • Contributing Writer
Published • Updated
Share

Primary source: Sphere India situation report on Cyclone Arnab, published by UN OCHA ReliefWeb, October 29, 2026 →

Viral claim - Social media posts and forward messages during the storm, October 2026
"Cyclone Arnab will only affect Andhra Pradesh coastlines, leaving neighbouring eastern states clear of severe weather risks."
Cyclone Arnab Hit Odisha Too: The Damage Record
Illustration: Rent Free desk — Reality Check
Why it matters

The storm was tracked as an Andhra Pradesh event because the eye aimed there. The rainfall, the surge and the landslides did not stay inside one state boundary.

Short answer: The eye aimed at Andhra Pradesh. The storm did not. Cyclone Arnab crossed the Andhra Pradesh coast near Narasapuram in West Godavari in the early hours of October 28, 2026, with sustained winds of 125 to 135 km/h gusting to 150 km/h, and the India Meteorological Department forecast a storm surge of 1.5 to 2.5 metres over low-lying Kakinada and Yanam. But the Sphere India situation report records that north coastal Andhra Pradesh and south Odisha were hit hardest by rain, and Odisha took the worse of the flooding. About 1,18,000 people were affected there, 75,388 hectares of crops and 1,672 houses were damaged, 300 villages were cut off, and landslides killed at least five people.

Correction (2026-11-15): This article was published on the afternoon of October 27 as a live tracker and cited the Odisha government portal, the Andhra Pradesh disaster authority and the Press Trust of India homepages, none of which documented the storm. It now cites six specific sources and records the outcome rather than the forecast. The verdict was also invalid: the article carried the value “Misleading”, which is not one of the permitted verdict strings, so no verdict line ever rendered on the page. The claim has been rewritten to the version the record can answer, and the unsourced figures, including the water tanker count and the Uttar Pradesh district alerts, have been removed.

1. What the forecast said, and when

The Indian Express set out the position in its bulletin-based explainer, updated at 8:57 am IST on October 27. Cyclone Arnab had intensified into a very severe cyclonic storm over the west-central Bay of Bengal overnight on Monday, and the IMD had issued a red warning for the Andhra Pradesh and adjoining south Odisha coasts.

According to the IMD bulletin issued at 2.30 am IST on October 27, the cyclone was centred around 300 km south-east of Visakhapatnam, 360 km east-south-east of Kakinada and 380 km south of Gopalpur in Odisha. It was also 460 km east of Machilipatnam and 530 km east of Bapatla, moving west-north-westwards at 25 kmph.

The forecast landfall was for the Andhra Pradesh and Yanam coast between Bapatla and Visakhapatnam, close to Yanam, by the forenoon of October 28, with maximum sustained winds of 115 to 125 kmph and gusts to 140 kmph. Heavy to extremely heavy rainfall was forecast across several coastal districts of Andhra Pradesh and southern Odisha through October 29.

The Hindu reported from Odisha that morning that several southern districts had already started receiving rain as the storm approached.

2. Where it actually made landfall

The Sphere India situation report, published through UN OCHA’s ReliefWeb service on October 29, gives the official account of what followed. Very Severe Cyclonic Storm Arnab crossed the Andhra Pradesh coast near Narasapuram in West Godavari. The landfall process began at about 01:30 IST on October 28, with sustained winds of 125 to 135 km/h gusting to 150 km/h. IMD forecast a storm surge of 1.5 to 2.5 m over low-lying Kakinada and Yanam. North coastal Andhra Pradesh and south Odisha were hit hardest by rain. The system moved north-north-west inland and weakened.

The compiled record adds two details that matter for the timeline. Arnab advanced its landfall forecast by roughly six hours and crossed the coast south-west of Yanam between 20:30 UTC on October 27 and 02:30 UTC on October 28. It then remained stationary over the landfall region, which slowed the landfall process, before turning perpendicular to its previous path and moving north into southern Chhattisgarh, where it weakened into a deep depression at 18:30 UTC on October 28 and a depression by 22:00 UTC. By 03:00 UTC on October 30 it had dissipated into a well-marked low-pressure area over northern Chhattisgarh and eastern Madhya Pradesh.

3. What it did in Andhra Pradesh

The Hindu reported on the night of October 27 that Andhra Pradesh cancelled several flights and trains, brought 30,000 fishing boats ashore, and that heavy rain in the northern districts left one person dead and a trail of destruction.

The compiled record fills in the scale. The IMD declared red alerts in seven Andhra Pradesh districts on October 26. Fifteen NDRF teams were mobilised in the state and Rs 27 crore in relief was released. Schools were closed in ten districts. By October 27 at least 89,000 people had been evacuated, and the state identified 570,000 people as vulnerable in preparation for evacuations.

Transport was hit across the region. Rail service on 53 routes in southern India was suspended on October 27 and 28, including the Godavari Express, Gowthami Express, Visakha Express, Falaknuma Express, Narasapur Express and the Garib Rath Express. Twenty-one flights were cancelled at Vijayawada Airport and Visakhapatnam Airport, with cancellations also at Gannavaram. Several locations in coastal Andhra recorded rainfall above 200 mm.

The damage estimate landed later. On October 30 it was estimated that Andhra Pradesh had suffered a loss of Rs 4,600 crore.

4. What it did in Odisha

This is the part the claim missed, and it is the part that made the storm dangerous.

The Government of Odisha prepared over 1,700 shelters in the state’s southern districts and mobilised eight NDRF teams and 40 Odisha Disaster Rapid Action Force teams. Schools and colleges were closed in five districts for October 28 and 29. The Indian Express reported that Chief Minister N Chandrababu Naidu had directed officials to maintain round-the-clock vigilance, evacuate people from vulnerable low-lying areas, mobilise disaster response teams, cancel leave for officials in vulnerable areas and activate round-the-clock control rooms. The IMD issued heavy rainfall alerts for Ganjam, Gajapati, Rayagada, Koraput, Malkangiri, Nabarangpur and Kalahandi.

The compiled record gives the totals. Roughly 1,18,000 people were affected in Odisha, with damage to 75,388 hectares of crops and 1,672 houses. Seventeen districts suffered damage and around 300 villages were cut off in Ganjam. On October 30, torrential rainfall triggered a landslide that killed three in Dangesi village of Kandhamal district. A tree fell on a house and caused a brick wall to collapse, killing a 40-year-old woman in Puri.

The Ganjam landslide of October 31 was the worst of it. It buried the Gidipabali hamlet of the Bhanjanagar block, a hamlet with a population of 26, of whom fourteen were relocated and twelve remained missing. On November 2, two were found dead and ten remained missing. The search was called off two days later, with the ten presumed dead.

The flooding followed. More than 1,05,000 people were affected by floods in Ganjam and over 25,000 in Gajapati. Around 300 metres of National Highway 326 was washed away in Mohana block of Gajapati, and a bridge collapsed there. The incessant rainfall affected more than 1,000 villages across the two districts. The Rushikulya and Vamsadhara rivers swelled, and floodwaters disrupted railway services with several trains cancelled or diverted.

Chief Minister Mohan Charan Majhi said the state was expecting damages in Malkangiri district bordering Andhra Pradesh, but Arnab wreaked havoc in Ganjam, Gajapati and Kandhamal. The opposition parties censured the administration for failing to implement preventive measures despite IMD warnings. A central team led by Ravi Shankar arrived in Bhubaneswar on November 2 to assess the damage.

5. Why the claim was wrong

The reasoning behind the claim was that the eye was aimed at the Andhra coast, so the storm was an Andhra event.

That reasoning ignores how a cyclone delivers damage. The wind field is wider than the landfall point, which is why Odisha was running evacuations and closing ghat roads while Andhra was still waiting for the centre. The surge is coastal, but the rain is not: the system tracked north-north-west inland and took its rainfall with it, into Odisha and then into Chhattisgarh and Madhya Pradesh. NASA noted that Arnab’s formation was “a rather late start for a basin that typically produces named cyclones in April or May”, and the remnants interacted with the prevailing westerlies over Nepal on October 29.

The compiled record also notes the precedent. Cyclone Montha, the first Bay of Bengal cyclone of the 2025 season, made landfall in the same location on October 29, 2025.

6. The verdict: false, with the context that the forecast was good

The claim fails. Odisha was not clear of severe weather. It took over 1,18,000 people affected, the destruction of more than 75,000 hectares of crops and 1,672 houses, 300 cut-off villages, washed-out highways, and at least five deaths in landslides.

The context that the claim got right is that the forecast was accurate. The Indian Express’s bulletin-based account shows the IMD had the track, the intensity and the rainfall footprint right, and the Sphere India report confirms the landfall came within the forecast corridor and with the forecast wind speeds. The damage was not a forecast failure. It was a well-forecast storm whose danger zone did not stop at a state line.

That is the pattern worth carrying into the next one. A cyclone’s landfall point is a coordinate, not a boundary, and the same is true of most “only affects X” claims. For a parallel look at how a weather hazard is measured against a population rather than a boundary, see our Nepal early warning limits report, and for the downstream effect of storm air on urban readings, our post-Diwali pollution spike analysis.

Sources to check yourself

  • Sphere India situation report via ReliefWeb, October 29: the official situation overview, the landfall point, the wind speeds, the surge forecast and which regions were hit hardest.
  • The Hindu, October 28: the flight and train cancellations, 30,000 boats brought ashore, Odisha’s road closures and evacuations, and the death in Andhra Pradesh.
  • The Hindu, October 27: rain reaching southern Odisha before landfall.
  • The Indian Express, October 27: the 2.30 am IMD bulletin position and track, the forecast landfall window and wind speeds, the rainfall outlook and Andhra Pradesh’s evacuation orders.
  • Hindustan Times live tracker: the expected track and the revised wind speed forecast.
  • Cyclone Arnab: the compiled record with citations for the red alerts, NDRF and DRAF mobilisations, evacuation and shelter figures, the 53 suspended rail routes, 21 cancelled flights, the Odisha damage totals, the landslides and the AP loss estimate.

Frequently asked questions

Q: Where did Cyclone Arnab make landfall? A: Near Narasapuram in West Godavari district of Andhra Pradesh. The Sphere India situation report says the landfall process began at about 01:30 IST on October 28, with sustained winds of 125 to 135 km/h gusting to 150 km/h.

Q: Was Odisha really affected? A: Yes. The compiled record puts the Odisha impact at roughly 1,18,000 people affected, 75,388 hectares of crops and 1,672 houses damaged, 17 districts affected, around 300 villages cut off in Ganjam, and landslides that killed at least five people.

Q: How many people were evacuated? A: Over 180,000 people were evacuated across the affected states, with at least 89,000 evacuated in Andhra Pradesh by October 27, and Andhra Pradesh identifying 570,000 people as vulnerable beforehand.

Q: Was the forecast wrong? A: No. The Indian Express reports the IMD’s October 27 morning bulletin and the forecast landfall window, and the Sphere India report confirms the storm crossed the coast inside that corridor and at the forecast intensity. The rainfall in Odisha was inside the forecast rainfall footprint as well.

How we checked: archived claim → primary dataset / VOD timestamp → quoted human with permission → verdict + corrections link. Report an error.

Reader discussion

Conversation for this story opens with memberships. Until then: found an error? Report it — we correct visibly.

The Sunday footnote — free

5 viral claims, what was missing.

Join the 2-minute Sunday read. One creator test inside. No spam.

AKM Loved by curious readers + quoted creators
Contextual Coverage

Related News — More in Reality Check

All Reality Check →

Keep reading

View all →