Over the last year, there has been a significant rise in aggression from both sides, and Islamabad and New Delhi need to work together to bring it to an end.. PHOTO: REUTERS
The Rawalpindi corps commander visited the Line of Control (LoC) in Kashmir on Tuesday where firing from the Indian side resulted in the death of a teenage girl recently.
Lt Gen Qamar Javed Bajwa visited troops stationed on forward locations along the LoC in Rawalakot and Nezpair sectors, where he exchanged Eid greetings with soldiers.
According to the military’s media wing, the Inter-Services Public Relations, Lt Gen Bajwa appreciated the high morale of troops and their dedication in defending the motherland.
The visit comes in the backdrop of unprovoked firing by Indian forces at the LoC in Kashmir and the working boundary in Sialkot.
Both sides have exchanged gunfire in the last week with four people killed on the Pakistani side by the Indian border security force. Five more have been left injured by the attacks from across the border.
On Pakistan’s invitation, the UN Military Observers Group for India and Pakistan visited the affected towns on Monday to evaluate the damages caused by the Indian firing.
The clashes have thrown the fate of upcoming peace talks between the two countries in the doldrums with New Delhi reluctant to fix a date for the meeting.
Amid the rising tension on the borders, the Indian army has also warned Pakistan to be ready for “unexpected damages”, accusing it of violating the ceasefire along the disputed border in Kashmir.
Lt Gen KH Singh, who commands the 16 Corps, alleged that Pakistan initiated shelling and firing on villages in the Poonch sector in Jammu, injuring five civilians in the area.
“There are certain elements across the border who want to create trouble on the LoC... we have to give them certain unexpected damage so that they don’t repeat it in future,” he said.
Published in The Express Tribune, July 22nd, 2015.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ