Uttarakhand Floods of June 2013: Curtain Raiser on the Events at NHPC’s 280 MW Dhauliganga HEP

Days after walking down the Gori, we go to the Sub-Divisional Magistrate of Dharchula sub-division, Pramod Kumar, who is busy coordinating rescue and relief on a war-footing, but still has the courtesy to meet. On being asked by me regarding the sudden release of water by the 280 MW National Hydro-Power Corporation (NHPC) Dhauliganga Hydro-Electric Project (HEP, see below the layout of the project given on NHPC website) at Chirkila and the ensuing damage downstream, he confirms that he received an emergency call on the night of 16^th June, 2013 from the NHPC, asking that they be permitted to release the impounded water in their reservoir, because it was in danger of breaching. Under normal circumstances they do not need his permission. He also confirms that he had refused, because the water level in the Mahakali main-stem was already flowing at danger-mark. NHPC went right ahead and opened their gates at full on the night of 16^th June, without authorization or any prior warning to anybody[1] but their own office-residence complex 20 km downstream, at Dobat.

Was this really an emergency, or was this purely opportunistic on the part of NHPC to take this opportunity early in the season to flush their reservoir that had been filled almost to half with bed-load and silt? We went looking for clues and information. I went to the NHPC office complex at Dobat, and met Bhuvan Chand Joshi, their Public Relations Officer. After giving me the spiel on how safe, and how green this so called run-of-the-river (ROR) project was, constructed by no less than the Japanese, the Germans and the Koreans put together[2], he admitted that their underground power-station was entirely flooded. Housed in a gigantic underground cavern about 100 meters long, four-storeys high at 40 meters and about 16 meters wide, river water had filled it right upto the control-room on the fourth floor. I had already been told by Kesar Singh Dhami, taxi owner of Dharchula, that on the 16^th June itself, when he was ferrying the first batch of Kailash yatris to the road-head on their way up to Tibet, he had noticed the reservoir was filled high already with flood-waters, with large uprooted trees and other woody debris floating at the damsite. He confirms that water was being released, but only a small release, despite the dam being fuller than he had ever seen it.

I was also told by another employee of NHPC (who did not wish to be named) that what had gone wrong was that despite the high flows on the 15^th and 16^th June, the power-station continued with production of electricity as usual. In what seems to be an unbelievably short-sighted and poor design, the Tail-race Tunnel, from where water is released back into the river after having turned the turbines, is flushed into a tributary stream, the Ellagad. It was when Ellagad also pulsed, that it sent a train of bed-load debris down its lower reaches, effectively blocking the exit of the Tail-race Tunnel coming out of the powerhouse. The power house continued to take in water from the Head-race Tunnel intake to work their turbines, unaware that the exit for water had been blocked. It is only when the water blocked in the Tail-race Tunnel surged back up, burst through the turbine units and began flooding the powerhouse, that NHPC even know that something was wrong. It was then that the massive curved steel gates of the intake were slid shut, and the powerhouse evacuated. This was further confirmed by Joshi, PRO, who also said that the ‘matter was under investigation’ by their own team for organizational detail. The General Manager and the Chief Engineer of the Dhauliganga HEP had meanwhile been transferred out. It is not clear yet how soon after the powerhouse was flooded, that they opened the sluice gates at the bottom of the reservoir. Draining it was clearly beneficial for NHPC, but catastrophic for roads, bridges and habitations downstream, both in India and Nepal.

If you look closely enough, there are two separate events here. The flooding of the powerhouse, and the ’emergency’ release of reservoir water. The powerhouse was not flooded because of too much water in the reservoir, but because it was in operation when its tail-race exit seven km downstream, is blocked-off because of poor short-sighted design[3]. They are then forced to close the gates of the intake, and abandon the powerhouse where water has reached the control-room on the fourth floor. The intake gates are now shut, but the flood waters continue to fill the reservoir further. They have already allowed the dam fill to a very high level, and here is the other curious factor.

The design of the Dhauliganga dam, is such that the dam has no provision for water to ‘overflow’ the dam safely, should undesired (even if foreseeable) levels be reached as they did this year. Or say if giant boulders block the narrow sluice gates at the bottom of the reservoir. Or in the real-time situation of what actually happened this year, the blocking of the tail-race tunnel leading to flooding of the powerhouse, hence requiring the shutting off of the intake, and losing the option of reducing reservoir levels more gradually and safely through two simultaneous releases. They then open the flood-gates. Clearly, one of two things have led to this decision:

One, letting the reservoir fill to a very high level is not out of the ordinary for NHPC; they do it every monsoon, as they had done on 16^th June as well. It is not for many months in the year that they have enough water to run all four turbines. Despite the run-of-the-river label, Joshi confirmed that they were unable to let any water to continue to flow un-diverted in the river-channel during the winter-spring months (we have photographic evidence of this as well), or they would not have water to turn even one turbine! The mandatory requirement that every hydro-power dam in Uttarakhand be required to release at least 10% of the river’s minimum flows at all times (as greatly insufficient as such a small flow is for downstream life), it seems neither a consideration while justifying the economics of such projects, and neither is it complied to here. The use of the term run-of-the-river here, is plain deception.

Their regular annual schedule for flushing the reservoir of bed-load and sediment is normally the 15^th of July and the 31st of July every year. Here again, when the reservoir is full, and there is enough water to provide the pressure for increased and accelerated flow to flush the reservoir on a twice-annual basis. Both flushing schedules follow each other closely at peak-flow season, so that the flushing is as complete as possible, and there is enough of a monsoon season ahead to fill the reservoir up again before the winter-lean. The probable reason for preponing the flushing could be the chance of flushing some of the unusually high accumulation of bed-load debris that had come down in this years flood. What this meant to the efficiency of the power-station is one thing, but what it means to all life in and along the river, is quite another.

Two, that the faulty design of the dam, both in location of its tail-race exit as well as no provision for over-topping, in combination with the carelessness of allowing the reservoir to fill to such levels at the start of the monsoon, was responsible for the ’emergency’ catastrophic release.

The Dhauliganga HEP is located on the Darma–yangti river, re-christened the Dhauliganga  river, just a couple of kilometers upstream of the confluence with the Mahakali at Tawaghat. In these two kilometers, the rivers flows (twice a year when it is allowed to, for a few hours) down steeply to the confluence which it meets at right-angles. With the Mahakali already in spate, coupled with the sudden release of more than 6 million cubic meters of stored water (Gross Storage Capacity), plus the flow of the river in flood (steadily increasing from 398 cubic meters a second on 15^th June), as well as millions of tonnes of bed-load boulders and sediment, the damage downstream is clear to see. If you look at the fresh scour-level on the banks downstream of the dam, it is in places more than 15 meters higher than the flood-level flow of the DhauliRiver. The river added thousands of tonnes of even more debris when, because of the flood level it reached, it tore through, plucking high at the talus-cones on either bank, and at every turn. At the confluence at Tawaghat, there must have been something of a back-flood for some time (a common flood phenomenon where the high-flowing main-stem creates a temporary water-dam), because the water-level seems to have risen very high, taking away the bridge that connects the entire Kuti valley and the trade route to Tibet,   tearing away almost the entire village-market complex at Tawaghat, and destroying the road as well. The flood waters had clearly reached the top of the road because of the deposition of river-sand on it. When I walked this section days later, the river was only less than a meter below danger mark. Even so, it was flowing about 12 meters below the road! Further downstream, the destruction was more serious.

In order to understand the magnitude of this flood event, I ask Joshi of NHPC for flow-data of the Dhauli river between the 12^th and the 18^th of June. He goes off for some time and returns with a sheet of paper that has hand-scrawled 6 hourly flow volumes from 12^th June, but stops short at 15^th June. All the flow volumes between the 12^th and the 15^th were below 150 cubic meters a second (cumecs), and at 12 am, on the night of the 15^th June it jumps up to 389.92 cumecs. This is just the start of the flood. Joshi seems to balk right here, and says that they have not received data for the 16^th June yet (the day I speak to him was the 8^th of July), and that he may get it after a week or so. And anyway, he says, the powerhouse was abandoned from the night of the 16^thJune, so getting data beyond that would be out of question. It is clear that Joshi was unwilling to give me flow-data for the duration of the flood-pulse. He had only minutes before informed me of how automated the whole operation was, and that it was possible for them to even operate the power-house sitting in their Dobat office-complex itself. The real scenario will be clear when we get flow data for the 16^th and 17^th of June.

According to NHPC, the Peak Flood Design for the Dhauliganga HEP is 3,210 cumecs, at a return interval of 100 years. That is the flow volumes that the dam is designed to be able to take without damage, at flood levels expected at least every hundred years. It is unlikely that flow volumes had reached almost 10 times the flow volumes of the flood on the 15^th June at the damsite (389.92 cumecs). NHPC gets its flow data from an automated level-gauge at the reservoir, so it did not require anyone to take readings manually, even prior to abandoning the station. If unprecedented levels had indeed been reached, then why had they held on to water in the reservoir right till the night of the 16^th June?  Please see the accompanying photographs, of the dam reservoir, empty of water. You can see at least two levels of cut-away terraces. The lower ones are alluvial terraces, consisting clearly of coarser gravels and cobbles deposited by the flowing river. The higher terraces, more visible high on the upper true-left bank in the photo, are remnant lacustrine (lake-bed) terraces, consisting of finer silts and sand, deposited by the stilled waters in the reservoir when it was full. This was the highest point of sediment accumulation in the reservoir prior to being flushed out. Clearly, at least 45% the reservoir was full of debris and sediment before NHPC flushed it. And if you look at the brown line on the concrete face of the dam, you see the level that the reservoir was allowed to fill upto, marked by the ‘bath-tub ring’ of floating bark and woody debris stuck there after draining.

Joshi tells me that when a delegation of people from Nepal came to NHPC to talk about the possible role that NHPC’s sudden release of water might have had on the flood that devastated Khalanga bazar at Darchula, he had told them that to the contrary, the dam had saved Nepal from great damage. “See how much debris is still behind our reservoir!” This was bare-faced misinformation. There are two aspects being denied here. One, that great masses of debris were actually flushed out from the lower-end of the reservoir on the night of 16^th June, leading to greatly increased flood levels as well as erosive potential downstream, especially on the Nepal bank at Darchula, which bore the brunt of flushed debris centrifuged on the curve. As is evident from the photo of the dam-site above, most of the debris that has been flushed, is from the front-end of the reservoir only. And two, that all dams and reservoirs, despite some being able to flush out debris from a section of the reservoir, do actually hold back a great deal of bed-load as well as suspended sediment in the upper end of the reservoir. They impede the very essential flow of sediment down to the oceans. Look now at the geometry of bed-load debris in the stitched photo. Distortions from the wide-angle lens apart, it clearly shows a gradual slope, and a filling up of the bed-rock channel to form a wide, sloping flood-plain. Had it not been for the dam, the bed-load would have continued to fill up the bed-rock channel downstream at about the same angle, slowing the entire flow of water and entrained debris. It would not have been washed down catastrophically all the way down to Darchula, without the force of an additional 6 million m³ of stored water released suddenly.

Emmanuel Theophilus (etheophilus@gmail.com)