Five policemen injured in Quetta IED blast

No group has claimed responsibility of attack but such attacks on security forces are not rare in the region


Mohammad Zafar May 03, 2016
File photo of police in Quetta. PHOTO: AFP/ FILE

QUETTA: At least five Rapid Response Group (RRG) personnel, including an officer, were injured on Tuesday morning as their vehicle came under attack by a roadside bomb in Eastern Bypass area of Quetta.

The RRG vehicle was on its way for duty when it was hit by a roadside improvised explosive device (IED) in the provincial capital, SSP Operation Quetta said while speaking to The Express Tribune.

“Five RRG police, including an officer, were injured in the blast,” the SSP said, adding around two kilogramme of explosive material was used in the blast.

Three of a family die in Khuzdar blast

Following the attack, a large contingent of security personnel rushed to the scene and cordoned off the area. The injured were taken to the Combined Military Hospital Quetta for medical treatment where three personnel were said to be in a critical condition.

No group has claimed responsibility for the attack but such attacks on security forces are not rare in the region.

The outlawed Tehreek-e-Taliban Pakistan (TTP) and Baloch insurgents frequently carry out attacks on security forces and government installations in the province which is home to a raging insurgency that has claimed the lives of hundreds of soldiers and militants since it re-ignited in 2004.

Landmine blast kills father, son in Sibi

The province’s roughly seven million inhabitants have long complained they do not receive a fair share of its gas and mineral wealth.

Last week, a father and his son were killed in a landmine blast in the Lehri area of Sibi. The incident occurred when a motorbike ran over a landmine in the Goth Abdul Ghafoor neighbourhood, resulting in a huge blast, the Levies forces said in a statement.

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