TODAY’S PAPER | March 05, 2026 | EPAPER

Gulshan water main leak nears fix after 11 days of dry taps

Officials expect water supply to resume by Friday


Our Correspondent March 05, 2026 1 min read

KARACHI:

After 11 days of parched taps and mounting frustration, residents of Gulshan-e-Iqbal may finally see relief as repair work on the ruptured 33-inch water line resumed on Wednesday, with officials expecting supply to be restored by Friday.

The troubled main, which was damaged during K-IV development works near Nipa Chowrangi, has repeatedly disrupted water supply to several blocks of Gulshan-e-Iqbal. Although repairs were completed last week and supply was briefly restored, the pipeline burst again on Tuesday when water was released at full pressure. Sources alleged that substandard repair work may have caused the repeated rupture.

Water Corporation officials said fresh repair work is now under way and is likely to be completed by Friday, after which water supply will gradually resume in the affected areas. They apologised to residents for the prolonged disruption.

The rupture has severely impacted Blocks 13-B, 13-C, 4, 5, 6, 13-D, 13-D1, 13-D2 and 13-D3, where residents have been forced to purchase expensive water tankers to meet daily needs.

Officials reiterated that the 33-inch line was originally affected during development work for larger K-IV pipelines at Nipa Chowrangi. Following initial repairs, the line failed again, prompting the latest round of maintenance. Authorities say efforts are being made to complete the work on schedule and restore normal supply to the long-suffering neighbourhoods.

Residents say they have been without regular water supply since the first of Ramazan and are being forced to purchase expensive water tankers to meet daily needs. Many have appealed to the Sindh chief minister, the local government minister and the mayor of Karachi to take immediate notice.

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