Two soldiers martyred in Indian ceasefire violation along LoC

Pakistan Army responded effectively, inflicted heavy casualties on the Indian side, says ISPR


Our Correspondent September 23, 2020
Sepoy Waseem Ali (Left) and Sepoy Noor-ul-Hassan (Right). PHOTO: RP

Two Pakistan Army soldiers were martyred due to unprovoked firing along the Line of Control (LoC) in Dewa Sector by the Indian border security forces, a statement issued by Inter-Services Public Relations (ISPR) stated on Wednesday.

According to the ISPR, 29-year-old Sepoy Noor-ul-Hassan and 25-year-old Sepoy Waseem Ali were martyred after Indian forces opened fire with light and heavy weapons.

The Pakistan Army retaliated by targeting Indian check posts, inflicting heavy casualties on the enemy, the military’s media wing added.

Firing and shelling on LoC in Azad Jammu and Kashmir have continued to increase. There have been 2,333 ceasefire violations by Indian troops during the current year. 

On September 9, in yet another incident of unprovoked aggression, Indian border security forces resorted to targeting the LoC resulting in the martyrdom of a Pakistan Army soldier.

The military's media wing said that 39-year-old Havaldar Liaqat, a resident of Chakwal district, embraced martyrdom during the exchange of intense fire.

"Indian Army troops initiated unprovoked ceasefire violation (CFV) in Bedori Sector along the LoC, targeting the Pakistan Army posts and civil population," the ISPR statement said.

Pakistan Army responded effectively to the Indian fire while heavy losses on enemy in terms of men and material were inflicted, it added.

On September 22, a Pakistan Army soldier was martyred on the Pak-Afghan border after terrorists attacked a post in the area. 

The post, located in the Bajur sector of the international border, came under fire from Afghan territory, resulting in the martyrdom of Sepoy Sabir Shah.


Facebook Conversations

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