Sardar Sanaullah Zehri's convoy attacked, 3 family members killed

The political candidate escaped the attack unhurt.


Web Desk April 16, 2013
File photo of Sardar Sanaullah Zehri. PHOTO: NNI

KHUZDAR: President of the PML-N Balochistan chapter Sardar Sanaullah Zehri’s convoy was targeted by a bomb blast in his area of Zehri as he was returning from an election campaign from a nearby area, reported Express News on Tuesday.

The political candidate escaped the attack unhurt however four others were reported dead.

The dead include Sanaullah Zehri’s son Sikander Zehri, his brother Mir Mehar and nephew Mir Zaid.

At least 25 people were injured as a result of this attack.

Zehri was travelling with personal security along with government provided guards. Balochistan Levies were a part of the security convoy.

“An improvised explosive device went off as Zehri, leading a convoy of more than 20 vehicles, left his home to campaign in Khuzdar,” provincial home secretary Akbar Durrani told AFP.

Local police confirmed the attack.

Candidates of political parties have come under attack as they begin election campaigns, with threats from various elements in the country.

A report compiled by National Crisis Management Cell (NCMC) of the interior ministry claimed that various militant groups are planning terrorist activities, specifically in the Balochistan and Khyber-Pakhtunkhwa provinces and some areas of Punjab in the weeks leading up to the election on May 11.

 

COMMENTS (13)

Ali | 11 years ago | Reply

People who do not have correct knowledge of sardar sanaullah zehri please don't speak .. N dont compare him with ex-cm .. Sanaullah zehri is a sensible and powerful tribal leader.

ali | 11 years ago | Reply

Its war between patriots and rebels, we can say these people died today due to Pakistan, salute to them and God bless our homeland.people in KP and Balochistan are fighting for green flag..

VIEW MORE 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