‘No action, turn tormentors”: Why violence raged in Delhi for 4 days? Delhi Police call logs offer clue

New Delhi: The Delhi Police had received about 13,200 distress calls during the four days when the national capital was hit by clashes, but call records of police stations in the violence hit areas raise serious doubts over the response to those calls.

Over the four days of the violence, from February 23 to 26, the number of distress calls to the police control room rose sharply from 700 on 23rd (Sunday) to 3,500 calls on the 24th, peaking at 7,500 calls on the 25th, before coming down to 1,500 calls on the 26th, matching the rise and dip in the intensity of the rioting on those days.

 

Also read: Delhi riots: In search for their loved ones……in the mortuary

 

In most of the cases, the distress calls made by people showed no action taken on the part of the police or no complaints lodged.

A BJP councilor in Yamuna Vihar, Pramod Gupta said his repeated calls to the Police went unanswered. “Police wasn’t able to control the situation. If police could have controlled, then this would have definitely not happened,” he said.

In Shiv Vihar, Rajdhani Public School, a private school was overrun for over 60 hours by rioters.

 

Also read: Delhi HC issues notice on plea seeking FIR, NIA probe against Swara Bhaskar, others

 

The owner Faisal Farukh, said that he kept making calls to the police but they never came.

“They attacked us on Monday. By 2 pm all the students and staff had left and around 4-5pm all of this happened. We kept calling the police but they just kept saying ‘we are coming’. But they never came,’ he said.

A review logs at the police station show at least two calls being made at around 3:54 pm on Monday, saying that the school was being attack. The action taken column in both these cases says that it is pending.

 

 

 

The post ‘No action, turn tormentors”: Why violence raged in Delhi for 4 days? Delhi Police call logs offer clue appeared first on Prag News.



from Prag News https://ift.tt/2wUXrtb
via IFTTT

Comments