RPO, CPO removed in the wake of Rawalpindi violence

Death toll from riots rises to 11.


Web Desk November 19, 2013
The mob during Rawalpindi clashes. PHOTO: AFP

RAWALPINDI: The government decided to remove Rawalpindi City Police Officer (CPO) Bilal Siddique Kamyana and Regional Police Officer (RPO) Zaeem Iqbal Sheikh from their posts, Express News reported on Tuesday.

Akhtar Hayat Laleka is likely to replace the CPO, according to reports.

The decision comes after sectarian clashes during an Ashura procession on Muharram 10 left 11 dead and over 80 injured. The body of another victim was recovered today.

When violence broke out in Rawalpindi on Friday - the day of Youm-e-Ashura - the army was called in to control the law and order situation, thereby sidelining the police who had been unable to control the crowds.

“We will make an inquiry to provide some relief to the affected people,” said Justice Mamoonur Rasheed, speaking about the Rawalpindi clashes.

He added that the investigation has not formally started yet, and it is too soon to make a comment regarding the incident.

According to sources, the government is under pressure from people affected by the sectarian clash.

Clash and protest

On November 15, sectarian clashes had erupted at an Ashura procession near Fawara Chowk, that left at least 11 people dead and over 80 injured. Unidentified people had also set a portion of the cloth market in Raja Bazaar on fire.

A weekend long curfew was imposed in the city after Friday's violence to control the sectarian tension.

On November 18, after the curfew was lifted, around seven to eight hundred people had staged a protest against the administration, demanding compensation for losses borne by traders as a result of the Rawalpindi riots.

The army and police had arrived at the bazaar shortly after the protest started and had temporarily closed of all routes leading to Raja Bazaar.

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