Dispelling controversy: SHO Ijaz Khan was victim of fire exchange: SSP

Two FIRs registered in Urmar Payan firing case


Our Correspondent September 04, 2015
A police damaged in Peshawar raid on September 2, 2015. PHOTO: PPI

PESHAWAR: Although Urmar SHO Ijaz Khan had been suspended by IGP Nasir Durrani on Tuesday, the notification took time in issuance and the actual suspension took place on Wednesday.

This was said by SSP Operations Dr Mian Saeed during a press conference at Gulbahar police station.

“Some people in the media are confused about the entire case as Ijaz had been suspended in an earlier case in Badhaber police station,” he said. “A police team is investigating the matter thoroughly.”

According to the SSP, Aslam was killed by the SHO after he gunned down three police constables.

“The SHO then entered Aslam’s house, took shelter there and opened fire in retaliation which killed Aslam on the spot,” he said. “Aslam’s relatives gathered and started firing at police. As a result, six policemen were injured.”

He added that Ijaz opened fire on Aslam in the Urmar case, only after the villagers began the shoot-out.

After his involvement in the Urmar case, a judicial enquiry has been announced by MPA Ishtiaq Urmar.

Cases registered

Two FIRs have been registered in Urmar Payan firing incident which left three people dead and six others injured.

The first FIR was sealed immediately after the registration. The second one was registered on the complaint of Abbas Khan, the father of the deceased Aslam Khan, resident of Urmar Payan village.

“We were present in the house when the police raid was conducted and my son was murdered in cold blood by the SHO,” Abbas said. “I was too shocked after Aslam’s death to see what was happening between the police and villagers.”

Published in The Express Tribune, September 4th,  2015.

COMMENTS (1)

JSM | 8 years ago | Reply Hindus- a marginalized community in Paksitan.
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