04.10.2015 Views

STRUCTURES OF VIOLENCE

4cONo1kTN

4cONo1kTN

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

495 | Structures of Violence<br />

the alleged rape, but victim no.2stated<br />

that she went for a bath. This was a<br />

contradiction.<br />

- That who typed the medical report,<br />

and why it was signed by only three out of<br />

the four Doctors is unclear. Further, it is<br />

unclear whether it was typed on the date<br />

of examination or thereafter. No reliance<br />

can be placed on the medical report.<br />

Based on the above ndings, the decision of the<br />

SGCM was set aside and the statement of victim no.2<br />

was found unreliable.<br />

Before analyzing the decision of the High Court, the<br />

following preliminary points may be made:<br />

- The IPTK does not have a copy of the<br />

decision of the SGCM. Further, the victims, or<br />

their family members, have not been met by the<br />

IPTK. Therefore, this limits the scope of the<br />

analysis.<br />

- From the reading of the documents it appears<br />

that the conviction of Captain Ravinder Singh<br />

Tewatia was for the rape of victim no.2. But,<br />

technically, as it was allegedly a joint operation,<br />

the charge for both rapes could hold against him.<br />

- The documents available provide very little<br />

information on the rape allegation against SPO<br />

Bharat Bhushan, except the information received<br />

by RTI which may pertain to SPO Bharat Bhushan<br />

as well. Therefore, the analysis will focus on the<br />

allegations against Captain Ravinder Singh<br />

Tewatia.<br />

The submissions and ndings may now be analysed<br />

as follows:<br />

- There appears to be a contradiction on when<br />

Captain Ravinder Singh Tewatia was rst<br />

identied i.e. during the identication parade or<br />

before the SGCM. Further, on one hand he states<br />

that medical examination conrms that victim<br />

no.2 was not injured. On the other hand he<br />

suggests the medical report was a fabricated<br />

document. Further, the medical report does<br />

conrm sexual assault.<br />

- The issue of Captain Ravinder Singh Tewatia<br />

not being named in the FIR appears to be a major<br />

issue. The family of the victim suggest that this<br />

was due to their fear. It would prima facie appear<br />

to be unfortunate that the High Court chose to<br />

dismiss fear as a legitimate reason. Within the<br />

context of Jammu and Kashmir, it would appear to<br />

be a legitimate reason. Further, while victim<br />

no.2states that she informed her parents right<br />

after the incident, and her uncle the following day,<br />

that Captain Ravinder Singh Tewatia was<br />

responsible, the High Court erred by not giving<br />

any weightage to this. Further, while on one hand<br />

the High Court accepts that the uncle was<br />

informed, subsequently the High Court states that<br />

he was not informed. This would once again<br />

appear to be an error on the part of the High Court.<br />

Further, the mere fact that victim no.2, or Sona-<br />

Ullah, did not mention earlier that she was raped<br />

twice, while a contradiction for the High Court,<br />

appears to be very minor.<br />

- The issue of what exactly victim no.2 did<br />

immediately following the rape also appears to be<br />

an issue that the High Court gave weightage to.<br />

Based purely on the records available, the<br />

contradiction is not adequately made out. While<br />

victim no.2 does state that she had a bath, she<br />

does not explicitly state that she was not<br />

unconscious immediately following the rape.<br />

Therefore, based on the record available, it would<br />

appear that the story of victim no.2is consistent with<br />

the other evidence, and that the High Court erred by<br />

overturning the SGCM decision.<br />

The nal point to be considered is the manner in which<br />

the Government of Jammu and Kashmir has<br />

approached the matter. In response to a RTI<br />

application led, the Director of Litigation, Jammu has<br />

stated vide letter dated 17 May 2012 that the<br />

Government of Jammu and Kashmir did not challenge<br />

the High Court judgment as the order was not directed<br />

against the State. Considering that the police within<br />

the State deemed it t to le a chargesheet in the<br />

case, it is unfortunate that the Government did not<br />

deem it t to further litigate the matter. This is<br />

particularly alarming considering that the LPA led by<br />

the Ministry of Defence remains pending from 2003.<br />

Information received by RTI on 27 June 2013, lists the<br />

last activity in this matter as being of 17 March 2003 –<br />

when the LPA was admitted, notices issued and the<br />

High Court order stayed. Further, no information<br />

exists on the effect of the staying of the High Court<br />

nal decision.<br />

Further, in addition to concerns with the court-martial<br />

proceedings in Jammu and Kashmir, it is clear that the<br />

instant case should have been tried before the<br />

criminal courts.<br />

Firstly, in light of section 34 [Common intention] of the<br />

Ranbir Penal Code, 1989 [RPC], Captain Ravinder<br />

Singh Tewatia would be guilty of the rape of both<br />

victims.<br />

Second, by splitting the case between the courtmartial<br />

and the criminal court, the efcacy of the trial is<br />

affected.<br />

Finally, it is concerning that the trial of SPO Bharat<br />

Bhushan does not appear to have reached any logical<br />

conclusion. It is also unfortunate that SPO's<br />

Shailender Singh and Sanjay Kumar, who abetted in<br />

the crime, do not appear to have been proceeded<br />

against.<br />

This case is also an example of the inevitability of the<br />

acquittal of alleged perpetrators as even when a<br />

court-martial nds a person guilty, ultimately the

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!