SP Maqsood attacked by own colleagues outside SC in 2012

Accused the provincial prosecutor general Shahadat Awan to have engineered the attack.


Naeem Sahoutara July 12, 2013
Ahmed had accused the provincial prosecutor general, Shahadat Awan, of engineering September 2012’s attack on him for challenging ‘illegal’ promotions of officers, including his brother Farooq Awan. PHOTO: FILE

KARACHI:


Police superintendent Maqsood Ahmed has also come under attack by his colleagues outside the Supreme Court’s Karachi registry on September 3, 2012, after he won the legal battle against out-of-turn promotions illegally awarded by the Sindh government in recognition of, what the officers claimed were their ‘gallantry’ performance.


Aggrieved by these shoulder promotions, Ahmed went to the court and ultimately won the battle when the apex court struck down the controversial law, ordering the government to revert out-of-turn promoted officers, including 66 in the police department.

Ahmed had also accused the provincial prosecutor general, Shahadat Awan, of engineering September 2012’s attack on him for challenging ‘illegal’ promotions of officers, including his brother Farooq Awan.

Last month, he had filed another petition with the SC, seeking a direction for the government to correct his date of birth on official documents so he can remain in service till May 2015. The government had issued notification of his retirement on May 15. When, he approached the subordinate court to fix his date of birth, Shahadat Awan allegedly used his influence to create hurdles in the process, he claimed.

In the plea, Ahmed had stated that he was being victimised for challenging illegal promotions and also raising voice against illegal occupation of government lands at the behest of President Asif Ali Zardari’s sister, Faryal Talpur, and his foster-brother Owais Muzaffar.

Published in The Express Tribune, July 13th, 2013.

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