WASA fails to repair broken tube-wells in Rawalpindi

Leaving the adjoining areas parched


​ Our Correspondent August 26, 2019
Water gushes from a tube well. PHOTO: EXPRESS

RAWALPINDI: The Water and Sanitation Agency (WASA) in Rawalpindi has failed to repair a tube-well which has been in a state of disrepair since Eidul Azha, leaving the adjoining areas parched.

Tube-well 31-A, located near the Kurri Road graveyard has not been repaired while the authority has declared a second tube-well, number 30, in the same area as ‘out-of-order.’

WASA opens bids for water metres 

As a result, residents of the Rasool Nagar neighbourhood and its adjoining areas say they are facing an extreme shortage of water as the tube-wells are the only source of water in the area.

They said that they had raised the matter with WASA officials but the issue has received scant attention for the past 10 days.

They demanded that WASA repair the tube-well at the earliest so that residents could be relieved.

At the moment, they said that they were compelled to pay for the expensive private water tankers to meet their water needs.

Meanwhile, residents of Union Council (UC)-42 Dhoke Elahi Bukush have been facing a shortage of water for the past few days with no substitute arrangements made by the Water and Sanitation Agency (WASA) to ensure a regular supply of water.

Residents expressed their grievances and threatened to protest against WASA for failing to provide them with water.

Repairs start on breach in Khanpur water channel

A complainant from Dhoke Elahi Bukush called Muhammad Atif said, "We have to fetch water from far-flung areas just to meet our daily needs.

We cannot afford a water tanker as it costs Rs1,000 for a single charge which is unaffordable,” he said, adding that their repeated complaints to WASA’s area in-charge Amir Shah had fallen on deaf ears. APP

Published in The Express Tribune, August 26th, 2019.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ