Mardan police shoot deaf man dead for ignoring spoken order to stop

The man did not stop at judicial complex check post despite multiple police warnings, DSP said

Our Correspondent March 02, 2017
A file photo of police personnel in Peshawar. PHOTO: AFP

MARDAN: Police shot dead a vendor it had mistaken for a suicide bomber in Khyber-Pakhtunkhwa's (K-P) Mardan district on Thursday.

The vendor riding a cycle did not respond to police calls to stop at judicial complex check post, Deputy Superintendent Police (DSP) Mumtaz Khan told journalists.

The deceased, identified as Olas Khan was taken to Mardan medical complex where he succumbed to his injuries.

For killing suspect: Three police razakars jailed for life

According to local people, the vendor was deaf and had been selling clothes in the area for the last 15 years to run his household. He was shifted to Sheeran Khota where he will be buried.

Locals protested outside the Mardan Press Club and raised slogans against, what they called, police brutality, demanding that a case of murder be registered against the responsible personnel.

When the bomb disposal squad officials checked the bike's carrier, they found nothing except bundles of clothes that the vendor was selling in the district, the DSP added.

Man shot to death by Islamabad police for not stopping car at checkpost

On February 3, a 27-year-old man was shot dead by police firing in Islamabad after he allegedly did not stop when a police official signaled him to.

Police and other law enforcement agencies have been on high alert since the recent wave of terrorism in the country that claimed more than 100 lives.


Junaid | 7 years ago | Reply The guys bicycle was rammed by police vehicle but he kept on running away on foot. So this deaf excuse is a bit lame. If he couldn't hear, at least he saw a police vehicle hitting him in order to stop him
Shafqat | 7 years ago | Reply Very Sad
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