Ignoring orders: PHC seeks LG secretary’s reply in promotions case

NAB restrained from arresting FBR chief


Our Correspondent October 27, 2015
Peshawar High Court. PHOTO: PPI

PESHAWAR: The Peshawar High Court on Monday sought a reply from the local government secretary for failing to promote secretaries of union councils to higher grades.

The division bench of Justices Waqar Ahmad Seth and Irshad Qaiser was hearing a petition filed by Mehmud, Shaheen, Akbar Ali, Muhammad Roedad and Sajid Muhammad through their Advocate Essa Khan. They named Local Government Secretary Adil Siddique and Director Tahira Yasmeen as respondents.

Arguing before the bench, Essa said the petitioners were appointed at a certain grade in different union councils. He pointed out the local government secretary had assured a divisional bench on May 15, 2013 that lists were being prepared and the UC secretaries would be promoted to the next grade within 45 days.

“Two years have passed, but nothing has been done,” said Essa.

He also informed the bench that junior secretaries were promoted, but the petitioners were ignored. He said this was tantamount to contempt of court. The bench, after hearing the arguments, issued notices to the respondents and sought replies.

Hearing a separate petition, the same bench stopped the National Bureau of Accountability (NAB) K-P from arresting Federal Board of Revenue (FBR) chief Akhlaq Ahmad.

Advocate Arshid Ali, representing the petitioner, said NAB started an enquiry into his alleged accumulation of illegal assets. He said his client and spouse were civil servants who served in administrative positions. He requested the court to declare the notice null and void and stop NAB from arresting his client.

The bench, accepting the plea, stopped NAB from arresting Ahmad and asked the petitioner to submit a surety bond of Rs1 million.

Published in The Express Tribune, October 27th, 2015.

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