Sindh CM vows to resolve water distribution issue

Murad Ali Shah has assured Capt (retd) Fazeel Asghar of full cooperation in resolving the water distribution issue


​ Our Correspondent December 14, 2019
Sindh CM Murad Ali Shah. PHOTO: PPP

QUETTA: The Balochistan chief secretary has apprised the Sindh chief minister of the problems being faced by the province in receiving its share of water from Pat Feeder and Kirthar canals.

According to a statement issued by the information department of the Balochistan government on Friday, Murad Ali Shah has assured Capt (retd) Fazeel Asghar of full cooperation in resolving the water distribution issue.

“The Sindh government will cooperate with Balochistan and [its] due share will be considered,” said the chief minister while chairing a meeting at the CM Secretariat in Karachi on Friday.

Both the chief secretaries of Balochistan and Sindh, irrigation minister for Sindh and other officers were in attendance.

A three-point agenda was discussed: inequitable distribution of Hub Dam water, encroachment on Pat Feeder Canal and short supply of water from Pat Feeder and Kirthar canals.

Murad directed the Sindh technical departments with devising a viable water distribution plan to address the reservations of Balochistan.

CM Murad was apprised by Chief Secretary Asghar that Balochistan was not receiving its share of water from Sindh.

“Since 1991, Balochistan has not gotten its due share of water from Pat Feeder, Kirthar, Uch and Manuthi canals,” informed the chief secretary.

He raised the issue of inequitable distribution of Hub Dam storage water between the two provinces, saying 71% of the dam’s catchment area falls in Balochistan, whereas only 29% in Sindh but still the apportionment of water has not been made accordingly. “Balochistan has been allocated 36% while Sindh is getting 63.44%,” he added.

Published in The Express Tribune, December 14th, 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