Sialkot lynching: Former DPO released on bail

Chauhan had been charged with negligence with regard to the brutal killing of two teenagers in Sialkot.


Express September 25, 2010
Sialkot lynching: Former DPO released on bail

SIALKOT:


Former DPO Sialkot, Waqar Chauhan was released on bail by the Gujranwala Anti Terrorism Court on Saturday.

Chauhan had been charged with negligence in his duties with regard to the brutal killing of two teenagers in Sialkot.

The Gujranwala ATC accepted the bail of Chauhan in the Sialkot lynching Case, and directed the former DPO to submit Rs100,000 bail bonds.

During the hearing of the bail plea, Chauhan’s counsel Zarar Shah said the former DPO was not directly involved in the brothers killing and nothing had been proven against him. He requested the court to accept Chauhan's bail plea.

Meanwhile, Special Public Prosecutor said the Court should not approve Waqar Chauhan's bail as investigations were still underway.

COMMENTS (22)

SA | 14 years ago | Reply The comment above reflects hypocricy to the extreme.. DPO could do nothing, oops I forgot he was not there, ok DPO wasnt there, Police was enjoying a live "hell in a cell" match and rescue officials were collecting ropes to tie the poor kids, and who knows were collection fire wood too. What could a poor reporter do??? And if the DPO isnt the son in law of a politician then I guess he's the son-in-law of RPO Rawalpindi, yeah??? Oh come on that's not a political post!!
anonymous | 14 years ago | Reply he was not standing there. if you have the courage go get the unedited video and watch it... dont believe the fabricated footage by news anchor who is himself involved. did not stop the culprits, instead continued with the video.. WHY he is free? because the media says so. he should be punished first because a human life was less important for him than gaining fame through that media.
VIEW MORE 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