Indian troops resort to unprovoked firing on LoC in Gultari sector

Previous such violation also occurred on July 20 and 23


Web Desk July 31, 2014
Indian troops resort to unprovoked firing on LoC in Gultari sector

SKARDU: Indian troops resorted to unprovoked firing along the Line of Control (LoC) in Gultari sector, Express News reported on Thursday, quoting the Inter Services Public Relations (ISPR).

A previous such violation occurred on July 23 resulting in one person being killed in Shakargarh sector on the Pakistani side of the Line of Control after India’s Border Security Force (BSF) allegedly opened fire.

According to local sources, the man identified as Iftikhar was shot four times when he accidentally went near the working border between India and Pakistan. He was arrested and handed over to Pakistan Rangers after post-mortem.

Further, on July 20, one person was killed in Mirajke area along the Pakistani side of the LoC after India’s Border Security Force (BSF) allegedly opened fire.

The firing also left three women and a child injured, who were shifted to Combined Military Hospital, Sialkot for medical assistance.

Additionally, on July 26, India said on Saturday that the recent ceasefire violations, alleged by both Pakistan and India, would not impede the upcoming dialogue between the neighbouring countries and would, in fact, become a significant part of the talks.

India’s Defence Minister Arun Jaitley said that they were itself an issue [to be discussed during] the talks.

COMMENTS (9)

Haider | 10 years ago | Reply

@Aditiya It can be said vice versa too good job indian media for hiding cruelties of Indian army be it cross border firings or harassments in kashmir

Aditya | 10 years ago | Reply

Well, Pakistan needs to cover and facilitate infiltration of terrorist into India, and Pakistani media need to cover Pakistani army by shifting blame on India. Good job Tribune!

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