KWSC officials accused of creating water shortages

Gulshan-e-Iqbal residents bemoan extended cuts in water supply


Our Correspondent January 19, 2025

print-news
KARACHI:

Allegations have surfaced that officials of the Karachi Water and Sewerage Corporation (KWSC) have fabricated a water crisis in Gulshan-e-Iqbal Block 13 D-2, leaving residents without access to water for extended periods. Some areas have faced water cutoffs for two years, while most locations have been affected for over a year.

Residents are forced to rely on unhealthy underground water or purchase water tankers at exorbitant rates. The Sindh government's inadequate policies have resulted in no new water supply projects, and corrupt water board officials have evaded accountability.

Residents affected by the crisis report that Karachi has faced a water shortage for 16 years, and their patience has worn thin. If the issue remains unresolved, conflicts over water may escalate.

A resident of Block 13 D-2 said they have been experiencing severe water shortages for eight years. Until 2016, their area received water for several hours daily without issues. However, the water supply abruptly stopped at the end of the year.

After lodging a complaint, Assistant Executive Engineer Nabil Ahmed inspected the pipeline, claiming it was damaged due to iron corrosion. However, residents alleged that Ahmed deliberately damaged functional pipelines to sell illegal connections.

Despite reporting the matter to senior officials, no action was taken against Ahmed. A new pipeline was installed under Ahmed's supervision in 2017, but it also became nonfunctional over time. Residents accuse Ahmed, under the protection of Executive Engineer Wasif Farooqui, of deliberately damaging pipelines to secure new tenders for pipeline installations. This cycle has repeated multiple times, allowing corrupt officials to demand bribes from residents for water connections.

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