Family protests youth’s ‘custodial death’

.


Imran Asghar July 20, 2024

print-news
RAWALPINDI:

A young man’s death due to alleged police torture in Gujarkhan police custody has sparked protests from the bereaved family and citizens.

Zeeshan Siddique, 24, reportedly died from torture by police officers from two Rawalpindi police stations. According to sources, the police initially attempted to cast doubt on the cause of death, suggesting it was due to some medical condition before any investigation was conducted.

Following the incident, police claimed the deceased’s family did not want legal action and refused to fulfil medico-legal formalities. However, this assertion was proven false as the family of the deceased staged a protest outside the Rawalpindi Press Club, condemning the police's ‘biased behaviour’ and demanding justice from the Chief Justice of Pakistan.

In response to the incident, police sources said eight police officers from Gujarkhan police station have been suspended, and the SHO of Civil Lines police station was removed from his post. This move appeared to be an attempt to show strict action was being taken. Nonetheless, a case was registered at Gujarkhan police station on the police's complaint, incorporating Section 302 for murder but without charging any individual.

Relatives of Zeeshan Siddique alleged that he had been suffering from a respiratory disease. They refuted claims that they refused legal action or a post-mortem. The FIR filed by the police seemingly misrepresented the facts, as evidenced by the family’s protest against police misconduct outside the Rawalpindi Press Club.

Later on Friday, a judicial magistrate initiated an inquiry into the mysterious death of the citizen. Sources said the decision to exhume the body for a postmortem has also been made. The Saddar SP along with police officials and the deceased's family members have been summoned for the inquiry.

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