Deprecated (16384): The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead. - /home/brlfuser/public_html/src/Controller/ArtileDetailController.php, line: 150
 You can disable deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED` in your config/app.php. [CORE/src/Core/functions.php, line 311]
Deprecated (16384): The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead. - /home/brlfuser/public_html/src/Controller/ArtileDetailController.php, line: 151
 You can disable deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED` in your config/app.php. [CORE/src/Core/functions.php, line 311]
Warning (512): Unable to emit headers. Headers sent in file=/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php line=853 [CORE/src/Http/ResponseEmitter.php, line 48]
Warning (2): Cannot modify header information - headers already sent by (output started at /home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php:853) [CORE/src/Http/ResponseEmitter.php, line 148]
Warning (2): Cannot modify header information - headers already sent by (output started at /home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php:853) [CORE/src/Http/ResponseEmitter.php, line 181]
LATEST NEWS UPDATES | Valley’s first, RTI seeks details behind Sopore custodial killing by Peerzada Ashiq

Valley’s first, RTI seeks details behind Sopore custodial killing by Peerzada Ashiq

Share this article Share this article
published Published on Aug 3, 2011   modified Modified on Aug 3, 2011

Right to Information Act might be a tool to fight corruption in rest of the country but in Kashmir, for the first time, it will seek unraveling of the mystery behind the custodial killing.

Kashmir RTI Movement chairman Dr Raja Muzaffar Bhat on Monday filed an RTI in the Sopore custodial killing where 28-year-old Nazim Rashid died immediately after being arrested by the police.

“There were 117 killings last year. Nobody knows what happened to the cases. We want to seek facts behind the Sopore killing to know why and how he was killed. The case will also stretch the RTI Act realm to go beyond sadak, bijli and pani issues,” Bhat told the Hindustan Times.

Nazim Rashid (28) was killed in police custody in Sopore, 55 north of Srinagar.

The RTI seeks answers to on why was Nazim Rashid arrested and what were the charges leveled against him. “Was any FIR filed against him for which he was arrested, if yes provide a copy of FIR?” asks the RTI.

Bhat said the RTI seeks information on the date and time of his arrest. “Who were the police officials and the Army personnel who arrested him?” asked Bhat in the RTI.

The RTI application speed posted on Monday to the authorities, also seeks details on the total time for which the victim was under custody of the army and the police.

“Who were the police/Army officials who interrogated him? What was the official and preliminary cause of his death? Had the deceased complained of any illness or discomfort before his death in custody and was any first aid given or was he treated for the same by any medical officers. If yes please provide details of the treatment given. If no please provide why any medical help was not given?” says the RTI.

The RTI also seeks to know if the parents were informed officially about the death of their son and was it recorded officially. “Please provide copy of the same,” said Bhat.

The RTI sought to know if a written consent obtained from his parents before conducting postmortem of Rashid. “Was the post mortem process video recorded as per Supreme Court guidelines?,” asks the RTI.

It also wants to know the names of medical officers, magistrates who conducted the post mortem.

The Hindustan Times, 1 August, 2011, http://www.hindustantimes.com/Valley-s-first-RTI-seeks-details-behind-Sopore-custodial-killing/Article1-728152.aspx


Related Articles

 

Write Comments

Your email address will not be published. Required fields are marked *

*

Video Archives

Archives

share on Facebook
Twitter
RSS
Feedback
Read Later

Contact Form

Please enter security code
      Close