Targeting FWO: Security official killed in Turbat bomb attack

FWO vehicles were about to start the construction work at Turbat-Oshab Road in Shapuk when the explosion occurred


Shezad Baloch September 18, 2014
Targeting FWO: Security official killed in Turbat bomb attack

QUETTA: A security official, providing security for workers of Frontier Works Organisation (FWO), was killed when militants detonated a remote-controlled bomb in Shapuk area of Turbat on Thursday.

According to Turbat Levies, FWO vehicles were about to start work on the Turbat-Oshab road in Shapuk when the explosion occurred.

“Militants had planted the IED on the roadside and detonated it through remote control when security personnel escorting the FWO arrived,” Levies official at Turbat Levies police station told The Express Tribune.

The explosion partially damaged a vehicle and killed a security official.

The body was shifted to the Civil Hospital Turbat where he was identified as Irfan Mohammad Raza.

Contingents of security forces and levies reached the spot and began a search operation in the area.

Cop shot dead

A police officer was shot dead by unknown gunmen in Quetta late on Wednesday night.

Assistant Sub-Inspector Najeebullah Tareen was returning home after completing his duty when armed assailants opened fire at him on New Algilani Road, killing him instantly.

The body was shifted to the Sandeman Hospital, Quetta where doctors pronounced him dead.

“He was shot seven times on upper torso which caused his instant death,” medics at the hospital said while describing the cause of death.

While the motive behind the attack is unknown, police have begun an investigation.

At least 22 police officials have been killed in targeted attacks in Quetta and its surrounding areas during 2014.

Quetta police said they have increased security in the city after a rise in targeted killings.

COMMENTS (1)

Moiz Omar | 10 years ago | Reply R.I.P.
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