Water hydrant case: Sindh High Court summons KWSB managing director

Petitioner said that the water utility had allowed his father Abdul Khaliq to run the sub-soil hydrant in July, 2015


Our Correspondent December 08, 2016

KARACHI: The Sindh High Court summoned on Thursday the Karachi Water and Sewerage Board (KWSB) head to file his comments in person over maintainability of a petition seeking restraining orders against him for demolishing a hydrant.

Headed by Justice Nadeem Akhtar, the two-member bench directed KWSB managing director Misbahuddin Farid to submit his reply by December 15 in a case filed by a water supplier, Azam Khaliq, who owns a sub-soil hydrant in Korangi.

According to Khalid, in light of the Supreme Court (SC) orders, only those water hydrants in the city were to be demolished that were unlawfully permitted by the Karachi commissioner. His hydrant, however, was approved by a former KWSB chief, the plaintiff maintained. He said that the apex court’s orders did not mention his hydrant and, therefore, the KWSB should be restrained from demolishing his hydrant.

The bench initially observed that it was convinced if the petition was maintainable despite the plaintiff’s claim that his plea did not hit the SC directions. On the suggestion of state counsel, the bench summoned the KWSB chief to submit his comments and assist the court in deciding the maintainability of the petition.

The petitioner said that the water utility had allowed his father Abdul Khaliq to run the sub-soil hydrant in July, 2015, in order to facilitate the industrial and commercial users in Korangi. He said that all the relevant rules were followed to get the no-objection certificate and he was paying bills and taxes regularly. He sought court orders to restrain the authorities from demolishing his hydrant, plant and machinery.

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