top of page

CRPF jawan killed 4 jawans of his own battalion in Sukma; CM Baghel called the incident unfortunate

According to the information, there was a dispute between the soldiers of 50th Battalion of CRPF over some issue in Linganapally Camp of Maraiguda. After this the dispute increased so much that a jawan opened fire on the rest of the soldiers present there.


CRPF jawan Ritesh Ranjan opened fire on his own fellow soldiers in the early hours of Monday at Linganapalli camp of Maraiguda in Sukma district of Chhattisgarh. In this incident, four jawans Dhanji, Rajib Mandal, Rajmani Kumar Yadav and Dharmendra Kumar have died on the spot, while 3 jawans Dhananjay Kumar Singh, Dharmatma Kumar and Malay Ranjan Maharana have been seriously injured.


At the same time, Chief Minister Bhupesh Baghel has expressed deep sorrow over the unfortunate incident of death of 4 soldiers in this incident. He has asked the police officers to take all necessary measures to ensure that such incidents do not recur. The CM has expressed condolences to the soldiers who died in the incident. The Chief Minister has given instructions to the officers for better treatment of the injured soldiers in this incident.


Accused jawan in custody

Inspector General of Police of Bastar region of the state ,Sundarraj P has received information that at around 3.15 am today, Jawan Ritesh opened fire on other jawans with his AK-47 rifle after a dispute. Seven jawans have been injured in this incident. He said that other jawans and officers reached there as soon as they got information about the incident.


The officers and jawans caught the accused and the injured jawans were taken to the hospital in Bhadrachalam district of Telangana. He said that the doctors declared four jawans dead while three jawans are being treated. The police officer said that the accused is being questioned. After questioning him, information about the cause of the incident will be available.


Comments

Couldn’t Load Comments
It looks like there was a technical problem. Try reconnecting or refreshing the page.
bottom of page