Indian television has found a perfect strategic soundbite: Pakistan cannot strike upstream Indian dams because the released water would race downstream and drown Pakistan. Dramatic. Conditionally plausible. Still incomplete. A catastrophic breach of a sufficiently large and sufficiently full reservoir can certainly generate a destructive flood wave, but whether that wave devastates Pakistan, loses force before reaching it, or first tears through Indian-administered valleys depends on stored volume, reservoir elevation, breach dimensions, river gradient, downstream topography, season, existing river discharge and the distance separating the structure from populated areas. Turning this conditional engineering reality into a universal law is not hydrological analysis; it is narrative warfare dressed in the language of expertise.
That distinction matters because ANI’s discussion with Tilak Devasher and Uttam Kumar Sinha does not exist inside an academic vacuum. It lands inside an Indian political environment where sections of the audience are openly demanding “not a drop of water” for Pakistan, celebrating the possibility of flooding Pakistani civilians, proposing attacks on food stocks and treating water deprivation as a bloodless substitute for conventional war. Other viewers correctly warn that legitimising upstream coercion would also expose India to similar arguments involving China and transboundary rivers. The comment section is not expert evidence, but it is unmistakable evidence of how a technical treaty dispute is being converted into mass-market fantasies of collective punishment.
The central verdict: Devasher’s claim is possible in some scenarios, not true in every scenario
Saying that “striking India’s dams will flood Pakistan” compresses several radically different structures into one convenient word: dam. A large storage reservoir near maximum operating level is not equivalent to a run-of-river hydroelectric project with limited pondage. A breach during a heavy monsoon is not equivalent to damage during a low-flow winter period. A structure immediately upstream of densely populated Pakistani territory is not equivalent to one located deep inside a complex mountain valley where the surge would strike settlements, roads, bridges and power infrastructure on the Indian side before travelling farther downstream.
Dam-break science treats inundation as a modelling problem, not a slogan. Flood depth, velocity, arrival time and attenuation depend on the assumed breach, the volume released and the geometry and roughness of the downstream channel. The destructive wave can continue far downstream, but its behaviour cannot be predicted merely by drawing an arrow from Kashmir toward Pakistan.
There is also a practical fact missing from the television theatre: some Indian projects on the western rivers possess nowhere near the strategic storage imagined by online warriors. An official 2026 NHPC tender concerning the Salal project recorded an original gross storage capacity of 284.08 million cubic metres but reported only 13.95 million cubic metres remaining in a 2024 survey because of sedimentation. That does not make the structure harmless, nor does it justify attacking it, but it demonstrates why every project must be assessed individually rather than mythologised as a giant upstream water bomb.
Pakistan should therefore reject two equally irresponsible claims. The first is the Indian fantasy that every upstream dam can be converted at will into an apocalyptic weapon against Pakistan. The second is the Pakistani fantasy that dams can be attacked without imposing potentially grave downstream consequences on Pakistani communities. Water infrastructure is inherently civilian infrastructure. Once states normalise attacks on reservoirs, barrages, canal controls and flood-warning systems, the river itself becomes an uncontrolled combatant.
What the Indus Waters Treaty actually divided
The most repeated Indian political slogan is that Jawaharlal Nehru “gave 80 percent of India’s water to Pakistan.” That formulation is emotionally effective and legally crude. The 1960 Indus Waters Treaty did not calculate every litre available across India and then donate four-fifths of it to Pakistan. It divided the six-river system into two principal groups. The Ravi, Beas and Sutlej were designated the Eastern Rivers, whose waters were generally made available for India’s unrestricted use after a transition period. The Indus, Jhelum and Chenab were designated the Western Rivers, whose waters Pakistan was entitled to receive, while India retained specified rights for domestic use, non-consumptive use, limited agriculture and hydroelectric generation subject to technical restrictions.
Pakistan’s allocation reflected geography, existing irrigation dependence and the brutal hydraulic disruption caused by Partition. Canal networks had been designed as one connected system under British rule; political borders then left important headworks in India while millions of irrigated acres and dependent communities lay in Pakistan. This was not an act of Indian charity toward an unrelated neighbour. It was a settlement addressing a basin that had been administratively severed without regard for the way water moved through it.
India also agreed to contribute £62.06 million toward replacement works that enabled Pakistan to transfer water from the western rivers into areas previously supplied by eastern-river canals. That financial arrangement further demonstrates that the treaty was an engineered transition between interdependent systems, not a ceremonial gift handed over because one prime minister wanted international applause.
| Popular claim | What the evidence shows | Assessment |
|---|---|---|
| “Pakistan received 80 percent of India’s water.” | The treaty primarily allocated three eastern rivers to India and three western rivers to Pakistan, while preserving limited Indian uses on the western rivers. | Misleading political shorthand |
| “India may not build anything on the western rivers.” | India may undertake specified domestic, agricultural, non-consumptive and hydroelectric uses, subject to treaty limitations and design conditions. | False |
| “Pakistan may treat every Indian hydroelectric project as illegal.” | The treaty permits qualifying projects, but Pakistan may question whether designs comply with the specified restrictions. | False |
| “India can unilaterally terminate the treaty whenever it chooses.” | Article XII states that modification or termination requires a duly ratified treaty between both governments. | Unsupported by the treaty’s express text |
| “Pakistan’s poor water management cancels its treaty rights.” | Internal efficiency and international legal entitlement are separate questions. | False |
The deeper historical meaning of this basin can be explored in The Indus Is Not Just Water: Pakistan’s Civilizational Spine, Legal Shield and Red Line, while the longer historical relationship between the Indus region, Taxila and the political imagination of South Asia is examined in Taxila, Chanakya and the Indus: Pakistan Did Not Begin in 1947.
Why treaty negotiations took nine years
The World Bank records that the treaty emerged after nine years of negotiations. The delay was not caused merely by personal rivalry between Ayub Khan and Nehru, nor by diplomats arguing over abstract percentages. Negotiators had to resolve control of rivers, canal dependence, replacement infrastructure, engineering feasibility, financing, transition periods, data exchange, future hydroelectric construction and a dispute-resolution mechanism capable of surviving recurring hostility.
The resulting agreement created the Permanent Indus Commission and a graduated process under which a technical “question” could become a “difference” for a Neutral Expert or, in qualifying circumstances, a legal “dispute” before a Court of Arbitration. The World Bank’s role is limited and procedural; it is not the basin’s permanent ruler and does not possess an unlimited mandate to rewrite the treaty whenever one state becomes dissatisfied.
The negotiations lasted because the treaty was doing more than dividing water. It was rebuilding a hydraulic system after the political amputation of 1947. Any podcast that reduces those nine years to Nehru’s alleged sentimentality or Pakistan’s diplomatic cleverness removes the engineering heart of the settlement.
Why India placed the treaty “in abeyance”
On April 23, 2025, India announced that the Indus Waters Treaty would be held in abeyance “with immediate effect” until Pakistan credibly and irrevocably abandoned what India described as support for cross-border terrorism. India has continued to defend that political position, including in 2026.
Pakistan rejected the move, arguing that the treaty is binding and contains no provision permitting one party to suspend it unilaterally. Article XII supports a central part of Pakistan’s legal argument: the treaty says it may be modified by a duly ratified treaty between the two governments and shall continue until terminated by another duly ratified bilateral treaty. It does not expressly create a unilateral “abeyance” mechanism.
A Court of Arbitration operating under the treaty subsequently maintained that its competence was unaffected by India’s position. India rejects the legitimacy of that proceeding and has described the court as improperly constituted, leaving the basin inside a dangerous split reality: India asserts a political suspension; Pakistan and the arbitral process maintain that the treaty and its adjudicatory machinery continue.
This is where the phrase “abeyance” performs political work. It sounds temporary enough to avoid the blunt admission of termination, yet expansive enough to justify withholding cooperation. Legally, however, a carefully chosen political word cannot automatically manufacture a power absent from the treaty.
What nobody is telling the audience: data can be weaponised before water is stopped
India does not presently possess the infrastructure required to permanently halt the western rivers flowing into Pakistan. The scale is enormous: the western system carries well over 170 cubic kilometres in an average year, while India’s treaty-permitted storage is only a small fraction of that volume. Building the dams, tunnels and diversion systems required to substantially alter long-term flows would take years and involve major financial, engineering, environmental and political constraints.
That does not mean “abeyance” is harmless. The immediate strategic danger is less cinematic and more credible: reduced data exchange, weakened advance warnings, disrupted inspections, delayed dispute resolution and greater uncertainty about reservoir operations. Article VI requires regular exchange of river-flow, reservoir and canal data, while Article IV addresses cooperation intended to avoid material damage and includes communication concerning extraordinary discharges and flood flows. Predictability is itself a security asset. Removing it can increase agricultural losses, complicate reservoir planning and leave downstream authorities with less time to prepare for extreme events.
During severe monsoon flooding in August 2025, India opened dam gates and transmitted warnings concerning potentially heavy flows entering Pakistan. The episode illustrated two realities simultaneously: rainfall and natural inflows were central drivers of the emergency, but reservoir releases and timely notification could still materially affect downstream preparedness.
This is the leverage that deserves more attention than television fantasies about completely turning off the Chenab. Flow timing, operational opacity and warning delays can damage trust and increase risk long before anyone constructs an impossible tap across an entire mountain river.
AI Music Generator
July 17, 2026 at 5:01 pm
One point that often gets overlooked in discussions about the Indus system is that river basins don’t follow political narratives—they follow geography and interconnected hydrology. If the article’s argument is that simplistic flood scenarios ignore how reservoirs, river flow, and downstream impacts actually work, then that’s a useful reminder that technical water management should be separated from political messaging.