← Insights
Chandigarh 15 August 2026 · 5 min read · NEER

Chandigarh and the 1% Flood

India's best-drained city — until a cloudburst finds the choes and the low sectors

On 9 July 2023, Chandigarh recorded 290.9 mm of rain in a single day — against a July-day normal of about 4.2 mm — the heaviest 24-hour fall the city had seen in more than two decades, past even the 262 mm of July 2000. Over roughly 50 hours the city took nearly 450 mm. India’s most carefully planned city, the one that is supposed not to flood, did: sectors waterlogged, roads caved in, homes took water, and the floodgates of Sukhna Lake were thrown open to bleed the rising reservoir into the Sukhna Choe and on toward the Ghaggar. For a city built as a model of drainage, the message was blunt — the design is very good, but it is not infinite.

This piece uses the India Flood Atlas — a modeled 1% annual-chance flood layer — to show why Chandigarh is, by exposure share, one of the least flood-prone regions in the atlas, and where the water still gets in.

The scale

The atlas models the 1% annual-chance (100-year) flood — the severe event with a 1% chance of arriving in any given year, mapped consistently across the union territory. Chandigarh is a single planned city, so it can be read as one unit, and the result is a genuine outlier — on the low side.

Across the UT, that event reaches:

That 9.6% is the number to sit with — but read it the right way. Chandigarh floods narrowly and shallowly because Le Corbusier’s plan gave the city something most Indian cities never had: a drainage system designed in from the start.

A note on what this is: these are modeled figures at ~30 m resolution — regional hazard screening, not a parcel-level guarantee, and building footprints, not people. For a dense city, a ~30 m riverine-and-pluvial model under-captures the fine-grained, drainage-driven flooding — the overtopped choe, the choked culvert, the low sector — that causes most of Chandigarh’s real waterlogging. So 9.6% is best read as a floor, not a ceiling.

Why Chandigarh floods

  1. It is drained by seasonal streams — the choes. Chandigarh sits on gently sloping ground between two rivers, drained by seasonal rivulets: the Sukhna Choe and Patiala-ki-Rao on the flanks, and the landscaped N-Choe threading the sectors, with Attawa, Baltana and Faida completing the set. These “stormwater highways” carry the city’s rain toward the Ghaggar. When they run clear, the city drains. When they don’t, they are the flood.
  2. Silted, encroached, garbage-choked channels. The choes lose capacity to silt, debris, wild growth and encroachment — which is why officials call for pre-monsoon desilting of N-Choe and Patiala-ki-Rao almost every year. A choe running at half its section overtops onto the sectors and villages beside it.
  3. Cloudbursts outrun the drains. The system was sized for a rainfall regime that intensifying monsoons now exceed. A 290 mm day delivers water far faster than any stormwater network — however well planned — can move it, so it ponds in the low points before it can leave.
  4. Sukhna Lake floodgate spills. When the lake fills, its floodgates are opened into the Sukhna Choe — a controlled release, but one that raises water along the choe and its downstream residential fringe. In heavy monsoons the gates have been opened repeatedly — a record eight times in a single season — a sign of how often the catchment now overfills.
  5. Low sectors and the choe belts. The exposure is not spread evenly. It concentrates along the Sukhna Choe and Patiala-ki-Rao corridors and in the city’s low-lying sectors and peripheral villages — the bowls where sheet flow collects and the banks the choes overtop first.

A strategic approach

Chandigarh’s problem is small and unusually tractable — a single, well-resourced city with good bones. The work is less about grand engineering than about keeping the design working.

Pillar 1 — Keep the choes clear. The highest-return act is unglamorous: desilt, de-encroach and maintain the choes and N-Choe before every monsoon, and hold their carrying capacity as a permanent budget line rather than an annual scramble. A choe at full section is the flood defence the city already owns.

Pillar 2 — Fix the low points. Target the handful of chronically waterlogged sectors, underpasses and choe-side villages with local drainage upgrades, pumps and monitored culverts — the atlas belt is small enough to fix piece by piece.

Pillar 3 — Operate Sukhna as flood infrastructure. Treat the lake’s catchment and floodgate operation as an integrated flood-management system — sediment control upstream, forecast-linked releases, and protection for the downstream Sukhna Choe fringe.

Pillar 4 — Warn, zone and insure. Nowcasting for cloudburst-scale rain (which gives little lead time), no-build enforcement along the choe corridors, and flood-inclusive home insurance (covered under “STFI” perils in standard Indian cover, yet rarely held).

The honest bottom line: Chandigarh is the counter-example in this atlas — 9.6% exposed, and shallow with it — proof that a city drained by design floods far less than one that isn’t. But “less” is not “never”: the choes silt up, the low sectors pond, and a 290 mm cloudburst still overwhelms the best network in the country. And the modeled floor understates it, because a ~30 m model can’t see the drain-by-drain waterlogging that is Chandigarh’s real flood. The fix isn’t reinvention — it’s maintenance: keep the choes clear, fix the low points, run Sukhna as flood infrastructure. Chandigarh already has the plan. It has to keep it working.

Sources

Exposure figures are modeled estimates (~30 m) for a 1% annual-chance flood, intended for awareness and prioritisation — not parcel-level certainty.

← All insights