Karachi blast survivor admits to making bomb for Yaum-e-Ali

Investigations reveal LeJ member was leading the operation.


Web Desk July 21, 2013
Security personnel collect evidence at the site of a bomb blast in a house in Karachi on July 20, 2013. PHOTO: AFP

KARACHI: The lone survivor of an accidental bomb blast in Karachi admitted to making a bomb to be blown on Yaum-e-Ali, Express News reported on Sunday.

On July 20, an explosion in a flat in Karachi’s Patel Para left three dead and one injured. The injured – now in police custody - revealed that he, along with his accomplices, was making a bomb when the explosives detonated.

He said the bomb was intended to be used on Yaum-e-Ali, adding that the target location was not decided though.

Initial interrogation revealed that one of the deceased – Mateenuddin – was leading the operations and had rented the flat six months ago. According to the survivor, Mateenuddin belonged to the sectarian group Lashkar-e-Jhangvi (LeJ).

Background

The high intensity blast took place inside a two-room apartment situated on the top floor a three-storey building under construction in Patel Para.

The explosion left a one-foot deep crater at the site.

Cell phone batteries and SIM cards were recovered from the crime scene.

COMMENTS (26)

Syed A. Mateen | 10 years ago | Reply

How cruel they are.

The law enforcement agencies should make a plan that no untowards scene should occur on 21st of Ramadhan thought out the country.

Such Bolta Hoon | 10 years ago | Reply

Bloggers/Readers, A true Muslim will never do such a thing. Clearly deprivation, brainwashing and exploitation is leading Pakistan into this mess. As a nation we will have to condemn such acts and stand united against such anti-state actors. Up to today as a nation we fell short in condemning the maulivis with weapons in lal masjid and criticise the individuals taking actions against them.

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