DSP shot dead in Peshawar

Outlawed Tehreek-e-Taliban Pakistan claims responsibility for the murder


Web Desk May 20, 2015
File photo of Peshawar police.

PESHAWAR: Firing by unidentified assailants in Peshawar's Gulbahar area on Wednesday left Deputy Superintendent Bahadur Khan dead, Express News reported. 

Initial reports revealed that DSP Bahadur Khan had departed from his home near Gulbahar chowk and en route to the office unidentified assailants opened fire on his vehicle, due to which he sustained many injuries.

Read: DSP shot dead in Karachi

According to sources, eye witnesses said that the men had used pistols to fire at the vehicle and immediately fled the scene.

DSP Bahadur was taken to a local hospital but soon succumbed to his injuries and was pronounced dead soon after his arrival at the hospital.


An Express News screengrab


Police have cordoned off the area and a widespread search operation in the area has commenced.

Read: Investigations: 'DSP Zaidi killed over personal enmity'

Reports further revealed that the DSP had received several threats in the past.

Later during the day, the outlawed Tehreek-e-Taliban Pakistan claimed responsibility for his murder.

The TTP Special Task Force targeted the police officer, the group's spokesperson Muhammad Khorasani said.

“The attackers fled after the shooting,” he said in a statement emailed to the media.

Khorasani said the TTP also targeted security official Ehsanullah in Swat.

COMMENTS (2)

US CENTCOM | 9 years ago | Reply Hope the culprits are caught and punished to the fullest extent of the law. My thoughts and prayers are with Deputy Superintendent Bahadur Khan's family during this extremely difficult time. Ali Khan Digital Engagement Team, USCENTCOM
Ahmed | 9 years ago | Reply Inna Lillah-e-Wa Inna ilayh-e-rajiyoon. Very tragic and the scars left on the child forever after winessing this incident. May Allah have mercy on the family. Amen
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