AT A GLANCE
Cyclone Arnab formed over the Bay of Bengal, rapidly intensified into a Very Severe Cyclonic Storm (VSCS), and made landfall on the Andhra Pradesh coast near Narsapur around 1:20 a.m. IST on 28 October 2026 with maximum sustained winds of 125–135 km/h, gusting to 150 km/h and a forecast storm surge of 1–2 metres. Tens of thousands were evacuated from Andhra Pradesh and Odisha, 64 train services and 38 Visakhapatnam flights were cancelled, roughly 6,000 electric poles were uprooted in Konaseema alone, and a red alert remained in force for 28–29 October. The name "Arnab" was contributed by Bangladesh to the UN-backed North Indian Ocean naming list and is pronounced "Ornab".
📑 Quick Navigation Index
- 1. Cyclone Arnab Explained: What Happened
- 2. Kya Log Search Kar Rahe Hain: Train, Flight & School Alerts
- 3. Formation Timeline: 23 October to 28 October
- 4. Landfall Data: Winds, Storm Surge & Path
- 5. Where It Hit: Affected Districts & States
- 6. Ground Impact: Evacuations, Trains, Flights, Power
- 7. Rescue & Government Response
- 8. Comparison Matrix: Arnab vs Dana vs Fani vs Amphan
- 9. How Cyclones Form, Naming & the Climate Question
- 10. Safety Checklist: IMD Do's and Don'ts
- 11. Frequently Asked Questions (Dropdown FAQ)
1. Cyclone Arnab Explained: What Happened
Cyclone Arnab is a tropical cyclone that developed in the Bay of Bengal during the last week of October 2026 and crossed the east coast of India — specifically the Andhra Pradesh coast near Narsapur — in the early morning of 28 October 2026. At the time of landfall the India Meteorological Department (IMD) classified it as a Very Severe Cyclonic Storm, the third-highest category the IMD uses for North Indian Ocean storms.
In practical terms, that means a storm with sustained winds between 118 and 166 km/h — strong enough to uproot trees, bring down electricity poles, blow off rooftops, flood low-lying coastal blocks and make sea conditions impossible for fishing vessels. Arnab did all of those things across Andhra Pradesh, parts of Odisha, the Puducherry enclave of Yanam and southern Bengal.
The storm became national news within hours of forming because it followed a textbook rapid intensification pattern: a fairly ordinary low-pressure area on 23 October turned into a named storm by 26 October and into a "very severe" system by 27–28 October. Forecasters had days of warning, evacuations began well before landfall, and the tracking accuracy of the last decade is a large part of why casualty numbers from cyclones in India have fallen so sharply compared with the 1970s and 1990s.
💡 One-line summary: Arnab = Bay of Bengal cyclone, landfall near Narsapur (Andhra Pradesh) at 1:20 a.m. on 28 Oct 2026, winds 125–135 km/h (gusts 150), surge 1–2 m, tens of thousands evacuated, name given by Bangladesh.
2. Kya Log Search Kar Rahe Hain: Train, Flight & School Alerts
- Immediate practical need: people in coastal Andhra, Odisha and Bengal are searching for train status, flight status, school closures and "cyclone kab tak aayega". Emergency search behaviour always spikes faster than news consumption.
- Landfall timing: the storm crossed the coast overnight (1:20 a.m.), so the morning search wave was people waking up to alerts, missed messages and flooded streets.
- National news coverage: live trackers from The Hindu, Times of India, News18, Hindustan Times and Indian Express all ran continuous updates, each one feeding related searches.
- A second system in the same basin: reports of another potential storm forming behind Arnab (covered as "double trouble in the Bay of Bengal") kept the topic alive past landfall.
3. Formation Timeline: 23 October to 28 October
Tropical cyclones in the North Indian Ocean are monitored by the IMD's Regional Specialised Meteorological Centre (RSMC) in New Delhi, which is the officially designated body for naming and tracking storms in the Bay of Bengal and Arabian Sea. Arnab's life cycle unfolded over five days:
- 23 October — Seed: a low-pressure area forms over the southwest Bay of Bengal. Too early for a name, too early for panic, but already on the IMD's chart.
- 24 October — Depression: the system organises into a depression, the first stage where rain bands and a circulation centre become distinct.
- 25 October — Deep depression: winds strengthen further; coastal advisories begin going out to fishing communities.
- 26 October — Named: it crosses the threshold to Cyclonic Storm "Arnab" and receives its name from the pre-approved North Indian Ocean list.
- 27 October — Rapid intensification: the IMD upgrades it to a Very Severe Cyclonic Storm and issues a red alert for 28–29 October covering parts of Andhra Pradesh and Odisha. National Bulletin No. 18 (27 October, 11:30 IST) forecasts landfall intensity of 125–135 kmph gusting to 150 kmph by the forenoon of 28 October.
- 28 October, 1:20 a.m. — Landfall begins: the storm starts crossing the Andhra Pradesh–Yanam coast near Narsapur. By 8:30 a.m., having spent its energy over land, it weakens from a Very Severe Cyclonic Storm to a Severe Cyclonic Storm.
Why the five-day warning matters: this progression is why evacuation orders could start days in advance. Modern cyclone forecasting in the North Indian Ocean gives a track position accuracy of roughly 100–150 km at 24 hours out — imperfect, but easily good enough to move an entire coastal district before the storm arrives.
4. Landfall Data: Winds, Storm Surge & Path
The technical details of the crossing explain why this stretch of coast was targeted with evacuation orders:
- Landfall window: began approximately 1:20 a.m. IST on 28 October 2026, with the crossing completed during the early morning hours.
- Exact crossing point: about 20 km east-northeast of Narsapur, 40 km southwest of Yanam and 60 km southwest of Kakinada — essentially the East Godavari–West Godavari coastline, with the Puducherry enclave of Yanam sitting right in the impact zone.
- Wind at landfall: 125–135 km/h sustained, gusting to 150 km/h (IMD). For reference, that is inside the range of a Category 1 hurricane on the Saffir–Simpson scale — enough to snap trees and power lines but not enough to level a well-built concrete structure.
- Storm surge: forecast at roughly 1–2 metres above astronomical tide in low-lying areas, with IMD leadership quoting 1–1.5 m for the most exposed sections. East Godavari was identified as the most vulnerable stretch.
- Weakening after landfall: cut off from the warm ocean water that fuels it, Arnab dropped from Very Severe to Severe Cyclonic Storm intensity by 8:30 a.m. the same morning — but continued to dump heavy rain inland.
- Rainfall reach: heavy to very heavy rain was reported across coastal Andhra, with the remnant system pushing rain towards Odisha, inland Andhra and parts of the northeast — which is how a coastal cyclone turns into a flood story hundreds of kilometres from the coast.
5. Where It Hit: Affected Districts & States
The impact zone stretched across three states and one union territory. Here is how the alerts and damage were distributed:
- Andhra Pradesh (worst affected): East Godavari, West Godavari, Dr. B.R. Ambedkar Konaseema, Eluru, Krishna, Bapatla, Anakapalli, Visakhapatnam, Vizianagaram, Kakinada and Srikakulam reported falling trees, flooded streets, damaged rooftops and disrupted power. Konaseema alone reported around 6,000 electric poles uprooted.
- Yanam (Puducherry): the small enclave sat within a few dozen kilometres of the crossing point and was treated as part of the core impact area by both IMD and the administration.
- Odisha: southern districts — Ganjam, Gajapati, Rayagada, Nabarangpur, Koraput and Malkangiri — were put on alert for heavy rain. Schools were closed in vulnerable blocks, fishing was restricted and more than 30,000 people were moved from low-lying areas.
- West Bengal: south Bengal districts including South 24 Parganas, Purba and Paschim Medinipur, Jhargram, Howrah and Kolkata received warnings for heavy rain as the system moved west-northwest.
- Remnant rain: the weakening system's moisture feed raised flood concerns further inland and in neighbouring regions; local irrigation departments were put on alert as river levels rose. Treat district-level flood reports as fast-changing — check your district administration's own bulletins.
6. Ground Impact: Evacuations, Trains, Flights, Power
These are the numbers reported by major outlets and official briefings in the hours around landfall. Live events move fast — figures below were still being revised when published, so treat them as reported snapshots rather than final statistics.
| Metric | Reported Figure | Source / Note |
|---|---|---|
| Evacuations (AP) | ~50,000 by Monday night; later reported above 84,000–89,000 | Reuters/Al Jazeera, The Hindu — rising counts as relief camps filled |
| Evacuations (Odisha) | 30,000+ moved; earlier planning target 48,000 | State minister to Times of India |
| Train cancellations | 64 services cancelled for 27–28 October | The Hindu live updates; other counts vary with cutoff time |
| Flight cancellations | 38 flights at Visakhapatnam airport by 6:15 p.m. | The Hindu, 28 October; other AP airports also affected |
| Electric poles down | ~6,000 in Konaseema district alone | District Collector via The South First |
| Relief fund released | ₹27 crore across 20 districts | Andhra Pradesh government |
| Casualties | Conflicting early reports (electrocution deaths reported; state leadership cited no confirmed toll that morning) | Live-blog snapshots differ — await the official consolidated figure |
⚠️ Accuracy note: casualty totals, evacuation counts and cancellation numbers in the first 24 hours of any cyclone are almost always revised upward as relief teams reach cut-off villages. If you are quoting this post, quote the date with it — and for anything safety-critical, rely on IMD and your district authority, not a screenshot or an old figure.
Beyond the headline numbers, the recurring pattern of damage was: uprooted trees blocking state highways, roofs and hoardings torn off, power and telecom interruptions, salt-water and freshwater flooding in low-lying agricultural land, and standing water in coastal towns. For a farming district, standing water after a cyclone is often the bigger loss — waterlogged paddy and horticulture crops can be ruined within days even when the wind damage looks modest in photographs.
7. Rescue & Government Response
India's cyclone response machinery has been rebuilt since the 1999 Odisha super cyclone killed more than 10,000 people. The current playbook — early warning, mass evacuation, dedicated rescue forces — was on full display:
- National Disaster Response Force (NDRF): 15 teams deployed in Andhra Pradesh, with four additional teams airlifted into position before landfall. NDRF teams carry chainsaws, cutting equipment, stretchers and medical kits precisely for post-cyclone clearing.
- Odisha Disaster Rapid Action Force (ODRAF): around 60 teams placed on alert and deployment in the southern districts — Odisha runs its own parallel force because it faces Bay of Bengal storms so often.
- State administration: Andhra Pradesh released ₹27 crore for relief across 20 districts, opened shelters with food, water and medical support, and restricted coastal activity. Odisha closed schools in vulnerable blocks and suspended fishing operations.
- Post-landfall orders: Chief Minister N. Chandrababu Naidu set a two-hour deadline for road clearance and ordered power restoration as soon as it was safe, along with immediate crop-loss assessment and continued shelter support.
- Warnings issued: IMD red alerts covering 28–29 October for parts of Andhra Pradesh and Odisha, with district-level warnings communicated through the usual chain of collectors, police and local announcements.
- Transport shutdown: preemptive cancellation of trains and flights is deliberate policy — a moving train in a cyclone-crossed corridor is a greater risk than a cancelled journey.
🛰️ Connectivity angle: when towers and power go down, restoring communication is treated as a rescue task, not a convenience — this is also why satellite-based internet keeps coming up in disaster planning. Our deep-dive on satellite internet real-world performance and challenges explains where it works, where it doesn't, and why ground infrastructure still has to be rebuilt first.
8. Comparison Matrix: Arnab vs Dana vs Fani vs Amphan
Numbers only make sense in comparison. Here is how Arnab stacks up against recent Bay of Bengal landfalls, based on reported landfall wind speeds:
| Cyclone | Landfall Area | Reported Landfall Winds | Peak Classification |
|---|---|---|---|
| Arnab (2026) | Narsapur, Andhra Pradesh | 125–135 km/h (gusts 150) | Very Severe Cyclonic Storm |
| Dana (2024) | Odisha coast | ~100–110 km/h | Severe Cyclonic Storm |
| Michaung (2023) | Andhra Pradesh coast | ~90–100 km/h | Severe Cyclonic Storm |
| Amphan (2020) | West Bengal / Bangladesh | ~155–165 km/h | Super Cyclonic Storm (over sea) |
| Fani (2019) | Puri, Odisha | ~185 km/h | Extremely Severe Cyclonic Storm |
Read the table carefully: Arnab was stronger at landfall than Dana (2024) and Michaung (2023), but clearly weaker than Fani (2019) and Amphan (2020). Amphan is the tricky comparison — it reached super-cyclone intensity over the open ocean and weakened before crossing land, so landfall winds alone understate its peak. Landfall wind speed is also not the whole story: surge height, forward speed, rainfall totals and how densely populated the impact zone is all decide how bad the event becomes.
9. How Cyclones Form, Naming & the Climate Question
Tropical cyclones are heat engines. Three ingredients have to come together:
- Warm ocean water (roughly 26.5°C or warmer) extending a few tens of metres deep — this is the fuel. Evaporation from the surface releases latent heat when it condenses into cloud, and that heat drives the storm.
- Atmospheric instability and low wind shear — if winds at different altitudes pull the developing storm apart, it never organises. Low shear lets the vortex stack vertically and tighten.
- Enough distance from the equator for the Earth's rotation to impart spin (the Coriolis effect), which is why cyclones do not form exactly on the equator.
- Rapid intensification — when a storm passes over an unusually warm, deep pool of water with low shear, its winds can jump by 55 km/h or more within 24 hours. That is the pattern forecasters watched with Arnab.
Why is it called "Arnab"? Cyclone names in the North Indian Ocean come from a coordinated list maintained by the ESCAP/WMO Panel on Tropical Cyclones. Member countries — India, Pakistan, Bangladesh, Sri Lanka, Thailand, Myanmar, Oman, Maldives and others — each contribute a set of names, used sequentially. Arnab was contributed by Bangladesh. When a system reaches the naming threshold, RSMC New Delhi assigns the next available name from the list; names are not reused once used. The WMO materials give the pronunciation as "Ornab", and the word is widely reported to mean "ocean/sea" — though the official WMO list itself does not publish a meaning, so treat that translation as an explanation rather than a formal definition.
💡 The naming rule that surprises people: names are assigned country by country, in order, and are never repeated. That is why Indian readers recognisable names like Fani, Amphan, Michaung and Dana — each came from a different member's contribution list.
Does climate change make storms like Arnab worse? Be precise here, because two separate claims get mixed up constantly:
- What the science supports: a warmer ocean holds more energy, and studies of the North Indian Ocean have linked warmer sea surface temperatures to a higher potential for rapid intensification. Warmer air also holds more moisture, which means more rainfall from a given storm.
- What science has not established: that any single cyclone — Arnab included — was caused by climate change, or that the Bay of Bengal is definitively producing more storms overall. Attribution of individual events, and trends in storm frequency, require dedicated analysis and remain active research questions.
- The honest framing: the risk profile is shifting — storms may bring more rain and can intensify faster near coast, even if the total number of cyclones does not clearly rise. That is an argument for stronger warnings and buildings, not for fatalism.
One more practical detail: reporting around Arnab also flagged a second system developing in the same basin behind it. Back-to-back systems are not unusual in the post-monsoon cyclone season (October–December), which is one of the two peak windows for Bay of Bengal storms — the other being pre-monsoon April–June.
10. Safety Checklist: IMD Do's and Don'ts
If a cyclone warning is issued for your district, the advice from IMD and disaster authorities is consistent and boring — which is exactly why it works:
✅ Do:
- Follow official IMD bulletins and your district administration's alerts — use the IMD Mausam app or the official cyclone information page rather than forwarded screenshots.
- Evacuate when told to, and stay in the shelter until authorities declare it safe to return.
- Stock drinking water, ready-to-eat food, essential medicines, a torch, spare batteries, charged phones and power banks, and keep identity/insurance documents in a waterproof cover.
- Secure loose objects on rooftops and balconies — most cyclone injuries come from flying debris, not wind itself.
- Check train and flight status directly with the operator before travelling; preemptive cancellations are normal during a landfall window.
- Keep cash in small denominations — power and UPI connectivity can both go down together.
❌ Don't:
- Do not go to the beach or watch the storm from the shore — storm surge is the deadliest part of a cyclone and it arrives as a rising wall of water, not a wave you can outrun.
- Do not touch or approach fallen power lines or submerged electrical fittings; electrocution after cyclones is a leading cause of death, and several reported incidents around Arnab involved live wires.
- Do not step outside during a lull. The calm centre of a storm is followed by winds from the opposite direction, often stronger than before.
- Do not drive through flooded roads — depth and current are impossible to judge, and vehicles can be swept away in a metre of moving water.
- Do not believe or forward unverified casualty counts and "warning" messages; misinformation spreads fastest exactly when people are making safety decisions.
Official Portals & Action Buttons
Check live warnings, bulletins and radar imagery directly from the primary sources:
11. Frequently Asked Questions (FAQ)
Where and when did Cyclone Arnab make landfall?
The landfall process began at around 1:20 a.m. IST on 28 October 2026 and the storm crossed the Andhra Pradesh–Yanam coast near Narsapur — roughly 20 km east-northeast of Narsapur, 40 km southwest of Yanam and 60 km southwest of Kakinada — as a Very Severe Cyclonic Storm.
How strong was Cyclone Arnab?
At landfall IMD reported maximum sustained winds of 125–135 km/h with gusts up to 150 km/h, plus a forecast storm surge of about 1–2 metres in low-lying areas. It had intensified to "Very Severe" just before crossing and weakened to a Severe Cyclonic Storm by 8:30 a.m. the same morning.
Who named this cyclone and what does "Arnab" mean?
The name comes from the ESCAP/WMO panel's agreed North Indian Ocean list, contributed by Bangladesh and pronounced "Ornab" by the WMO materials. It is assigned by IMD's RSMC New Delhi when a system reaches naming intensity. The word is widely reported to mean "ocean" or "sea", though the official list does not publish meanings.
Was Arnab stronger or weaker than recent cyclones?
Stronger at landfall than Dana (2024, ~100–110 km/h) and Michaung (2023, ~90–100 km/h), but weaker than Fani (2019, ~185 km/h at Puri) and Amphan (2020, ~155–165 km/h). Amphan reached super-cyclone intensity over the open sea before weakening, so a landfall-only comparison understates it.
How do I check whether my area is under a cyclone warning?
Use the official IMD cyclone information page and the Mausam app for bulletins, warnings and radar, and follow your district collector's communications for local evacuation orders. Avoid relying on social media forwards — they are frequently outdated even when they were once accurate.
Is another cyclone forming after Arnab?
Multiple outlets reported a follow-up system developing in the Bay of Bengal behind Arnab during the same week. October–December is one of the two cyclone peak seasons for the basin, so new systems are expected — but a developing low is not a forecast of landfall. Track only official IMD bulletins for any successor system.
Final Verdict
Cyclone Arnab is a serious storm, not a catastrophic one — and that distinction is earned by preparation rather than luck. A Very Severe Cyclonic System crossing a populated coast at 1:20 in the morning could have been far worse; instead, days of accurate tracking, roughly two lakh people moved into shelters across two states, preemptive transport shutdowns and dedicated rescue forces held the damage to infrastructure, crops and localised tragedy. Compare that with the 1999 Odisha super cyclone, where the same basin produced more than ten thousand deaths, and the improvement in India's disaster machinery is not subtle.
What remains genuinely unsettled is the direction of travel: warmer oceans that can intensify storms quickly, a second system following close behind, and coastal districts that rebuild in the same flood paths every season. For readers outside the impact zone, the useful takeaway is a habit rather than a statistic — bookmark the IMD portal, install Mausam, and know your district's evacuation route before the next red alert, because the next name on the list has already been assigned and will be used when its turn comes.
📚 Related Reading on Utility Vaults
- Major Earthquakes Hit Indonesia & Iran — Disaster Explained
- Starlink Deep Dive Part 2: Real-World Performance & Challenges
- Cloudflare Outage & the Security Risk of Centralized Infrastructure
- Google Search Pro Tricks & Operators (Catch Trends Early)
Updated daily — current affairs, weather impact, AI guides, tech trends 2026, cybersecurity, crypto analysis and online-earning strategies.
To leave a comment, click the button below to sign in with Blogger.