Two soldiers martyred in Singi IBO

ISPR says two terrorists were killed in heavy exchange of fire


Our Correspondent April 08, 2022
PHOTO: AFP/FILE

Two soldiers were martyred and an officer injured during an intelligence based operation (IBO) conducted by the security forces in Singi, near Mashkai in Balochistan.

According to a statement issued by the Inter-Services Public Relations (ISPR) on Friday, the security forces conducted an operation in the area between the night of April 7 and 8 on information of the presence of terrorists. “During the operation, two valiant sons of soil, Naik Tajwali and Sepoy Osama embraced Shahadat while one officer got injured,” the military’s media wing said.

It added that once the troops started establishing blocking positions in the area, terrorists tried to escape from their hideout and opened fire at the security forces.

“Two terrorists have been killed in the ensuing heavy exchange of fire. The terrorists were involved in different security incidents in Awaran district and surroundings.”

Read Four FC men martyred in Sibi IED blast

The ISPR said that arms and ammunition were also recovered which were intended to be used by the terrorists for disrupting peace and security in the area.

“Security forces remain determined to thwart attempts at sabotaging peace, stability and progress of Balochistan,” the communique added.

On March 22, at least two soldiers and three civilians were martyred during a terrorist attack in Khyber-Pakhtunkhwa's Bajaur district, the military had said in a statement.

It said the terrorists fired at security forces in Bloro area of the district which initiated a response from the security forces.

"Resultantly, four terrorists were killed. Weapons and ammunition were also recovered from the killed terrorists," it added.

The ISPR said that the militants remained actively involved in terrorist activities against security forces.

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