Banakacherla Project Explained: AP-Telangana Water Dispute

Banakacherla Project Explained: AP-Telangana Water Dispute upsc

From Current Affairs Notes for UPSC » Editorials & In-depths » This topic

Andhra Pradesh and Telangana are once again embroiled in a water dispute, this time over the Banakacherla project. This new irrigation proposal, championed by AP’s Chief Minister Chandrababu Naidu, aims to link the Godavari and Krishna river basins to supply water to drought-prone Rayalaseema. Telangana has objected, saying it violates the 2014 State Reorganisation Act and could threaten its share of Godavari waters. Below is a detailed breakdown of the Banakacherla scheme – what it is, why it was proposed, how it would work, who it involves, and its broader significance and challenges.

What is the Banakacherla project and where is it planned?

  • Definition: The Banakacherla project is a proposed river-link irrigation scheme in Andhra Pradesh that intends to divert surplus monsoon flow from the Godavari River into the Krishna River network and ultimately into the Penna basin (Rayalaseema region). It includes new reservoirs, canal expansions, and lift irrigation systems to transfer water from the Godavari (via the Polavaram dam) to the Banakacherla Regulator on the Srisailam Right Main Canal (Penna basin).
  • Location and Components: The scheme spans multiple districts in AP: starting at the Polavaram Dam (West Godavari district, Godavari basin), it upgrades the Polavaram Right Main Canal (RMC) in East Godavari to 38,000 cusecs, increases the Thatipudi lift canal (Visakhapatnam district) to 10,000 cusecs, and builds a large reservoir at Bollapalli in Palnadu (West) district. From Bollapalli (with ~4,899 million m³ live storage, about 173 TMC), water will be pumped through a network of lift stations (at Harischandrapuram, Lingapuram, Gangireddypalem, etc.) and a 19.5 km tunnel under the Nallamala hills into the Banakacherla Regulator in Nandyal district (Rayalaseema/Penna basin). The Banakacherla Regulator (15°50′N, 78°31′E) serves as the “gateway” for most of Rayalaseema’s irrigation projects (like SRBC, GNSS, KC canal, Telugu Ganga).
  • Design Features: At full tilt, the plan is to divert about 5663 million m³ (MCM) annually (≈200 TMC) – roughly 2 TMC per day during ~105 flood days. Key infrastructure includes ~376 km of new/expanded canals, 6.6 km of tunnels (twinned), and nine pumping stations with nearly 400 MW of pumped-storage hydropower. The net effect is to move Godavari floodwaters hundreds of kilometers southwards.

Why is the Banakacherla project being pursued in Andhra Pradesh?

  • Drought Mitigation: Rayalaseema (Kadapa, Anantapur, Kurnool, Chittoor districts) is notoriously rain-shadow territory with yearly rainfall roughly 500–700 mm, far below Coastal Andhra. Traditional sources (Srisailam, Nagarjunasagar) only supply a fraction of needs. For example, in 2015, Srisailam reservoir delivered less than 1 TMC to its canals, and AP had to transport water by rail. The Banakacherla scheme would “drought-proof” this region by adding up to 12.14 lakh hectares of irrigation (3.00 lakh new + 9.14 lakh stabilized) and supplying drinking water to about 80 lakh people. Industries would gain ~20 TMC for operations.
  • Utilizing Surplus Water: Andhra leaders claim the Godavari has huge “surplus” flows during monsoons – on the order of 90–120 flood days yielding tens of TMC each. Studies suggest about 3,000 TMC of Godavari water currently flows unused into the Bay of Bengal every year. By capturing just a part of this as floodwater, AP argues it’s tapping a renewable resource. CM Naidu has repeatedly said only excess floodwater (2 TMC/day for 100+ days ≈200 TMC/year) would be used, which would otherwise drain to sea.
  • Political and Economic Goals: The project is a pet project of CM Naidu (TDP) and has political overtones. Rayalaseema is a stronghold of rival YSR Congress, so delivering water here could yield electoral gains. Economically, bringing irrigation to backward districts could stimulate agriculture and rural livelihoods. It aligns with India’s broader river-linking vision to balance water distribution across regions.
  • Part of a Network: This linkage builds on Polavaram (a multipurpose dam on Godavari) and the existing Krishna canals. The idea is to augment Andhra’s overall water portfolio by tying together Godavari, Krishna, and Penna systems. It is also reminiscent of past AP–TN agreements (Telugu Ganga) where Krishna water was sent to Chennai, showing Andhra’s history of inter-basin projects.

Who are the key stakeholders and what roles do they play in the Banakacherla project?

  • Andhra Pradesh Government: Led by CM N. Chandrababu Naidu (TDP), the AP Water Resources Department is the main proponent. They prepared the project plan, submitted a Pre-Feasibility Report (PFR) to the Centre, and are seeking central approvals. Key figures include AP’s Water Minister (Nimmala Rama Naidu) and irrigation officials. Andhra’s justification is based on surplus flood water use.
  • Telangana Government: CM A. Revanth Reddy (Congress) and his Irrigation Minister U. Kumar Reddy are the principal opponents. They claim the project threatens Telangana’s water share and violates law. Telangana has petitioned Union Ministers (Finance and Jal Shakti) and even plans to raise the issue in Parliament or courts. BRS leaders (former Telangana CM KCR) initially had floated similar ideas, but TS now resists this AP plan.
  • Central Government: The Union Jal Shakti Ministry (with Minister C.R. Patil) oversees river boards. Its Expert Appraisal Committee (EAC) on river projects recently deferred a clearance request, instructing AP to consult the Central Water Commission (CWC) first. The CWC has asked for detailed data on all projects (floodwater, dependability, calculations). Union Coal Minister and BJP leader G. Kishan Reddy has noted that the Union has only asked for more info (DPR) and not approved the PFR yet.
  • River Management Boards: The Krishna River Management Board (KRMB) and Godavari River Management Board (GRMB), set up under the AP Reorganisation Act, must clear any new project affecting shared rivers. Telangana insists Banakacherla needs their approval. The Krishna Water Disputes Tribunal (KWDT-II) is also mentioned, since it is re-examining Krishna shares (TS has demanded 66% vs AP 34%). Under the Reorganisation Act, an Apex Council (council of ministers) can adjudicate disputes – Telangana has urged its use.
  • Local Communities and NGOs: Farmers in Rayalaseema stand to benefit from water security, so they generally favor the project. Conversely, communities in the Nallamala forests or Bollapalli area might face displacement or ecological impact, potentially opposing on environmental/social grounds. NGOs and activists concerned with deforestation, wildlife (tiger, forest) and tribal rights could also become stakeholders. Their voices may emerge during EIA (Environmental Impact Assessment).
  • Other Political Parties: In AP, ruling YSR Congress may have mixed views (its MP K. Chiranjeevi resigned citing water issues, as TS claims). In Telangana, the BJP and Congress unite in opposition. Nationally, cooperative federalism advocates (e.g. within Inter-State Council) are watching.

When was the Banakacherla project first conceived and what is its current status?

  • Initial Conception: The idea traces back to 2014, soon after Andhra Pradesh’s bifurcation. Water sharing was a central issue in the Telangana movement, so linking rivers was part of Andhra’s response. CM Naidu first talked about a Godavari-Penna link around 2018 when his TDP government drafted the “Godavari-Penna River Linking Scheme”. 
  • Developments: In 2019, when Y.S. Jagan Mohan Reddy (YSR Congress) became CM, the project was renamed “Palnadu Drought Mitigation Project” and tenders were invited. However, inter-state concerns stalled progress. After TDP returned to power (2024), Naidu revived the plan.
  • Recent Timeline:
    • June 2024–2025: Andhra submitted a PFR to the CWC; Telangana raised objections.
    • June 17, 2025: The MoEF’s EAC meeting returned the proposal to AP, asking it to consult CWC about interstate issues (possible violation of Godavari Tribunal Award) before moving to environmental ToR.
    • Late June 2025: Telangana CM Reddy held an all-party meeting (June 18) and went to Delhi to press the case with Union ministers.
    • July 5, 2025: News reports indicated the CWC sought detailed data on the Polavaram-Banakacherla link and asked for dependability analysis, maps, formulas. As of mid-2025, no construction has begun; the project remains in the planning/approval stage.
  • Legal Status: Under the Andhra Pradesh Reorganisation Act, 2014, new water projects affecting common rivers require approval by the Apex Council (an inter-state body). Telangana argues Banakacherla lacks these clearances (KRMB, GRMB, CWC) and thus must be kept in abeyance. AP says it will comply, but is impatient due to local pressures.

How will the Banakacherla project function to interlink river basins?

  • Water Transfer Process: The scheme systematically uses canal augmentation and lift irrigation to move water southwards:
    • Godavari (Polavaram Dam): During floods, water is released into the Polavaram Right Main Canal. AP plans to nearly double this canal’s capacity from 17,500 cusecs (≈500 m³/s) to 38,000 cusecs (≈1076 m³/s). This canal currently feeds Krishna basin projects.
    • Thatipudi Lift: The existing lift canal at Thatipudi (draws Godavari water towards coastal Andhra) will be upgraded from 1,400 to 10,000 cusecs (≈283 m³/s), further diverting water into the Krishna system.
    • Bollapalli Reservoir (Palnadu): Water is collected in a new reservoir at Bollapalli (capacity ~173 TMC). From here, large pumps (each ~300–800 cumec) lift water in stages.
    • Lift Conveyance: A series of pump houses will raise water (~28,000 cusecs in total flow capacity) from Bollapalli up through the Nallamala range.
    • Tunnel Passage: A 19.5 km tunnel (and smaller 6.6 km auxiliary tunnels) will carry the water beneath the forest hills to emerge in the Krishna basin (near Srisailam canals).
    • Banakacherla Regulator (Penna Basin): The lifted water is stored at the Banakacherla complex, which is essentially on the Srisailam Right Main Canal but considered part of the Penna basin. From Banakacherla, water can be distributed via existing canal networks (e.g., Telugu Ganga, SRBC, KC Canal) into Rayalaseema’s farms and towns.
  • Engineering Specs: AP’s DPR envisions moving about 656 m³/s (2 TMC/day) during peak operation. With 105 flood days assumed, about 200 TMC/year (5663 MCM) could be transferred. To maintain flows year-round, the huge Bollapalli storage acts as a balancing reservoir, since Rayalaseema’s cropping extends into the dry season. Pumped-storage turbines (~400 MW total) are included, enabling energy recovery when releasing water.
  • Dependability: The plan is built on the idea that after upstream states take their share (per the Godavari tribunal), 90–120 days of flood water remains surplus. By capturing this, AP argues it isn’t impinging on Telangana. However, actual flows depend on monsoon variability and upstream usage; less than designed discharge could reduce yield. The CWC wants AP to compute dependability at 75% (a standard viability threshold) before proceeding.
  • Integration with Other Schemes: The project leverages existing infrastructure: water from Polavaram (Godavari) is fed into Srisailam canals (Krishna basin) via the Right Main Canal. Essentially, it would use Polavaram as a source and Banakacherla as a terminal, knitting Godavari, Krishna, and Penna basins in one chain. It resembles how Telugu Ganga currently channels Krishna water to Chennai (Penna basin) – similarly an inter-basin lift scheme.

What is the significance of the Banakacherla project for Andhra’s water security and development?

  • Alleviating Water Scarcity: Rayalaseema is one of India’s driest agricultural zones. By potentially irrigating over 12 lakh hectares and supplying drinking water to ~80 lakh people, the project could transform its economy. Cropping intensity and yields would rise, enabling farmers to grow water-intensive crops (sugarcane, paddy) currently untenable at scale. The region has poor groundwater levels; surface water from Banakacherla could stabilize supplies and reduce dependence on tankers or borewells (as happened in 2015).
  • Surplus Water Utilization: It exemplifies an efficient use of river floodwaters. Official reports suggest that after allocations to Maharashtra, Chhattisgarh, Odisha, Telangana, and AP as per the Godavari tribunal, large volumes of monsoon flow (millions of acre-feet) still reach the sea. Harnessing even a fraction (200 TMC ≈5.66 billion m³) can have major impact. For context, AP’s own Srisailam reservoir has an active capacity of ~10 TMC; Banakacherla alone involves 20 times that volume in diversion.
  • Economic Growth and Power: The project’s pumps and two 200 MW hydropower units (pumped-storage mode) would provide peaking power and stabilize the grid. The anticipated IRR (internal rate of return) could be significant if full irrigation is realized (economists estimate multipliers of 2–3 in farm income). This could reduce regional migration and unemployment.
  • Strategic Importance: Banakacherla is the largest canal-based link proposed in AP after Polavaram. It underscores AP’s pursuit of integrated water management, aligning with the National Perspective Plan (which envisages 30 river links). If successful, Andhra might claim precedence in water budgeting (e.g. allowing it to use full Godavari entitlement plus surplus). It could also indirectly benefit Telangana: by taking Godavari flood off the table, more Krishna water might be available downstream (a point Telangana disputes).
  • Political Symbolism: The dispute has become a major political flashpoint. For Andhra’s ruling party, it demonstrates a proactive approach to statehood-era grievances. For Telangana, resisting it resonates with the historical demand that Hyderabad State’s lands (Telangana) should not be drained of water for Seemandhra (Coastal Andhra) benefit. The strong emotions show how interlinking schemes are about more than engineering – they reflect identity, federal trust, and resource justice.

What limitations and challenges does the Banakacherla project face?

  • Inter-State Legal Hurdles: Telangana contends the plan violates the AP Reorganisation Act, 2014, which requires any new water project to get clearance from the Apex Council (an inter-state body under the Act). No such approval has been sought yet. The project also needs clearances from the Krishna and Godavari River Management Boards, which Telangana argues were bypassed. Even if Andhra insists on “surplus” water use, the Godavari Water Disputes Tribunal (GWDT) award of 1980 allocated 1,486 TMC (AP 518, TS 968) but did not define “surplus”. Telangana fears Banakacherla would encroach on its tribunal-sanctioned share. This legal ambiguity could lead to a Supreme Court battle or demand federal intervention, delaying the project indefinitely.
  • Data and Dependability Concerns: The CWC has asked AP for transparent computations (floodwater definitions, dependence on 200 TMC diversion). Critics point out that if upstream states use more Godavari (e.g. via Polavaram itself), less “surplus” may remain. Andhra’s own planners say success hinges on capturing 150–200 TMC and storing it to meet crops in January. But climate change makes monsoon patterns erratic. If the assumed 105 flood-days fall short, actual diversion could be far below 200 TMC, affecting benefits. This technical risk is a limitation.
  • Environmental and Social Impact: The project requires submergence of ~24,064 hectares (mostly Palnadu, Prakasam, and Nandyal districts), of which ~7,179 ha is forest land (including part of Nallamala wildlife sanctuary). Building large dams/tanks and cutting tunnels through biodiverse forests could damage ecosystems and displace tribal and rural communities. Resettlement and Rehabilitation (R&R) costs and conflicts (compensation disputes, loss of livelihoods) will be massive. If not managed well, this could spark local protests or litigation under the Forest Conservation and Wildlife Acts. The envisaged pumped-storage also raises questions of sedimentation and leakage.
  • Financial Viability: At an estimated ₹81,900 crore (2025-26 prices), the project is extremely expensive. Critics may question the cost per unit water delivered and whether funds might yield more benefit if spent on local water conservation or decentralized irrigation. Any cost overrun or interest burden will add to AP’s fiscal stress. Moreover, since the scheme’s benefit-cost ratio depends on near-perfect monsoon yields, financial returns are not guaranteed.
  • Political Resistance: Telangana’s government has vowed to “stall” the project at every level (legislative assembly resolutions, writing to central ministries, even threatening court). Such resistance may make official clearances and construction politically difficult. MPs from Telangana have already walked out of a joint meeting to protest misleading claims. Andhra cannot simply bypass TS’s concerns without risking constitutional conflict and eroding cooperative federalism.
  • Implementation Complexities: Technically, lifting 200 TMC over long distances is a massive engineering task. It involves high-energy pumping over several stages and maintenance of a huge canal network. Any breakdowns or silting could interrupt supply. Coordination of multiple canal systems (Polavaram RMC, Srisailam RMC) also means complex operations. Delays in one component would ripple through the chain.
  • Opportunity Cost: With limited funds and time, focusing on Banakacherla might divert attention from other needs (e.g., urban water supply, local lift schemes). If Banakacherla moves slowly, some argue AP should concurrently invest in alternate measures: more efficient irrigation (drip, laser leveling), recharge of local reservoirs, or improvements to existing tanks rather than banking everything on one mega-link.

How does the Banakacherla project compare with other major river-linking initiatives?

Feature / ProjectBanakacherla (AP)Ken–Betwa (MP/UP)Telugu Ganga (AP/TN)
Rivers LinkedGodavari → Krishna → PennaKen → BetwaKrishna → Penna (Tamil Nadu)
Link Length~376 km of new/expanded canals + tunnels221 km canal (+2 km tunnel)~406 km canals
Proposed Annual Transfer~200 TMC (5,663 MCM) of floodwater~64 TMC (1,830 MCM)~12 TMC (340 MCM) supply
Main BenefitsIrrigation (~12.14 lakh ha), drinking water to ~80 lakh people, 20 TMC for industries, 400 MW hydroIrrigation ~1.45 lakh ha (MP), 3.36 MLD drinking (UP); ~1.83 BCM/yearDrinking water to Chennai (~4 million people); irrigation in Rayalaseema
Estimated Cost (INR)~₹81,900 crores (2025-26)~₹16,000 crores (approx.)(Completed earlier; original cost data adjusted)
Status (as of 2025)DPR/PFR stage; facing legal-clearance delaysDPR approved (environment clearance granted Feb 2023); construction to startCompleted and operational (final stage in 2004, delivering smaller flows than envisaged)
  • Key Insight: Compared to Ken–Betwa, Banakacherla is much larger in scale (over three times the water volume and more than five times the area irrigated). Telugu Ganga, linking Krishna to Chennai, was built in the 1980s–2000s to supply about 12 TMC (though actual supply averaged ~3-4 TMC), showing that even smaller interlinks can be contentious. Unlike Ken–Betwa (which required combining two states’ interests) or Telugu Ganga (also inter-state), Banakacherla is currently an intra-state scheme, yet it triggers inter-state issues because it involves a river (Godavari) shared with Telangana.
  • Regional Context: All these projects aim to bring water to water-deficient regions. Banakacherla targets drought-prone Rayalaseema (AP), Ken–Betwa targets drought-hit Bundelkhand (MP/UP), and Telugu Ganga targeted Chennai’s water needs. Differences lie in governance: Ken–Betwa had environmental controversies but went ahead with Centre’s backing; Telugu Ganga faced some disputes but was ultimately completed through multi-party agreement. Banakacherla’s fate may hinge on whether federal coordination improves.
  • Planning and Outcomes: Notably, Telugu Ganga’s actual yield has been lower than planned, highlighting risks in inter-basin projects. If Banakacherla is built, engineers will have to ensure canals are lined (as was done later in TG) and loss minimization is achieved. In terms of governance, Banakacherla is unique because the riparian states (AP and TS) share a recent history of mistrust; any success here would require unprecedented cooperation, perhaps learned from how Telugu Ganga eventually succeeded after data-sharing and canal upgradation.
  • Comparison Insights: The table shows Banakacherla is by far the most ambitious in water volume and coverage. However, its challenges are equally magnified: a very high cost and the hurdle of inter-state legal clearance. Lessons from the Telugu Ganga and Ken–Betwa projects (like phased implementation, trust-building, and transparent data on water availability) may guide Andhra and Telangana if they choose a cooperative approach.

What are the possible ways forward in resolving the Banakacherla dispute?

  • Technical Review and Data Sharing: The CWC’s request for detailed analysis suggests an objective way forward. Andhra should provide clear hydrological data (rainfall-runoff, dependability) and involve Telangana in joint studies to define “surplus” water scientifically. Shared use of real-time flow gauges and a transparent data platform (as envisioned in the River Boards Act) could build trust.
  • Institutional Mechanisms: Invoke the Apex Council or Supreme Court under the Inter-State River Water Disputes Act if negotiations stall. However, both states might first exhaust political dialogue. The ongoing Parliamentary push (Inter-State River Water Disputes Amendment) for stronger dispute resolution bodies could help if operationalized.
  • Mutual Concessions: Politicians could explore quid pro quos. For example, AP might agree to provide Telangana enhanced share (beyond legal minimum) of Godavari water left after Banakacherla withdrawals, or invest in Telangana’s water projects (like support for Kaleshwaram or Rangampally schemes). Conversely, Telangana could prioritize quicker clearances for Banakacherla in return for AP support on Krishna share issues.
  • Phased or Modified Implementation: Andhra may consider advancing less contentious parts (canal lining, small storages) while pausing the reservoir lift aspect until clearances. The scheme could be downsized: initially divert fewer TMC of water, meeting perhaps one-third of the target, to demonstrate viability without immediately raising Telangana’s alarm.
  • Alternate Measures: Simultaneously, both states should ramp up water use efficiency. Rayalaseema needs on-demand irrigation (drip, sprinklers) and watershed management to reduce Banakacherla’s burden. Telangana can expand its existing Godavari projects (e.g., lift from Kaleshwaram) to meet its needs rather than fight AP. Engaging farming communities to switch from paddy to millets or pulses could also mitigate demand pressures.
  • Political Dialogue and Public Communication: A joint panel of AP–TS engineers and officials (or using the Union Water Ministry as mediator) could hold structured talks. Public messaging is key: Andhra must convince its people that Telangana’s concerns about “theft” are unfounded, while Telangana must be assured its own irrigation projects won’t suffer. Emphasizing cooperative federalism (as noted in policy reviews) and regional equity may ease emotions.
  • Environmental Safeguards: To move ahead, AP could agree to independent environmental impact assessments, with strict conditions (e.g., no tunneling during animal mating seasons, compensatory afforestation for submergence areas). Demonstrating genuine environmental stewardship might sway neutral observers and build pressure on Telangana to negotiate. In sum, the way forward likely lies in stepwise diplomacy: technical collaboration, phased construction, and reciprocal agreements. Both states must balance Rayalaseema’s development needs with Telangana’s water security. The Centre can facilitate by enforcing rules (CWC guidelines, EAC recommendations) impartially. If both sides cling to extreme positions (AP: “It’s our water”; TS: “We got the lion’s share”), the stand-off may persist. But if they embrace the spirit of constitutional river-sharing, a mutually acceptable compromise could be found.

Conclusion: What is the future outlook of the Banakacherla project and the AP-Telangana water dispute?

The Banakacherla project encapsulates the tug-of-war over water resources in post-bifurcation Andhra Pradesh and Telangana. On paper, it offers transformative benefits for Andhra’s thirsty south, promising to irrigate over 12 lakh hectares and serve 80 lakh people. Yet in practice, it runs into the complex realities of federal water governance. Telangana’s resistance highlights that water is not just a resource but a political claim as well. Going forward, the project’s fate will depend on whether data-driven negotiation and institutional mechanisms can override zero-sum politics. Strong technical studies (on surplus water availability), transparent dialogues under the Inter-State Council, and perhaps conditional approvals (like phased implementation) may pave a path. Alternatively, the dispute could drag on, reflecting broader national challenges in river sharing. For UPSC aspirants, Banakacherla is a case study in cooperative federalism: it underscores that ambitious development projects must heed not only engineering but also laws (like the Reorganisation Act), tribunal awards, and inter-state trust. Ultimately, the outlook will hinge on both states finding a compromise that aligns Andhra’s development goals with Telangana’s water entitlements – a delicate balancing act emblematic of India’s river politics.

Q. How can Andhra Pradesh and Telangana use institutional mechanisms to resolve the Banakacherla dispute cooperatively? (250 words)

Related Posts

If you like this post, please share your feedback in the comments section below so that we will upload more posts like this.

Responses

🖍️ Highlight
HomeCoursesPlansAccount