Rohri canal crisis: Phull regulator to become operational by June 19

Repair work gained momentum after farmers started protesting


Our Correspondent June 16, 2016
Water supply to Rohri canal was suspended two weeks ago, after the flank walls of the Phull Fall Regulator collapsed. PHOTO: FILE

SUKKUR: The repair work of Phull Fall Regulator, near Naushero Feroz, is nearly complete and it will be operational by June 19, announced Sukkur Barrage chief engineer Wali Mohammad Naich on Thursday.

Water supply to Rohri canal was suspended two weeks ago, after the flank walls of the regulator collapsed.

Rohri canal is one of the seven off-taking canals of Sukkur Barrage, which originates from barrage's left pocket. It supplies irrigation and drinking water to different districts including Khairpur, Naushero Feroz, Shaheed Benazirabad, Hyderabad, Badin and Sanghar.

Delayed repairs: Closure of Rohri canal affects drinking water supply, crops in lower Sindh

The repair work of the regulator, which was earlier being carried out at a slow speed, gained momentum after the agricultural farmers started a protest movement in different parts of upper and lower Sindh decrying acute shortage of water, which was causing extensive damage to the kharif crops including, cotton and sugarcane.

On Wednesday, 2,200 cusecs water was released in Rohri canal, which passes through the bypass of Phull Fall Regulator, said Sukkur Barrage control room in-charge Abdul Aziz Soomro while talking to The Express Tribune.

The water was increased to 3,500 cusecs by Thursday, he said, adding that only 4,000 cusecs of water could pass through the bypass of the regulator.  The repair work will be completed by June 19, but it will take at least one week for the regulator to dry up after which water will pass through it, said an official of irrigation department, requesting anonymity.

Published in The Express Tribune, June 17th, 2016.

 

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