Cricket Country Staff
Editorial team of CricketCountry.
Royal Challengers Bangalore (RCB) player KP Appanna's name has cropped up in the investigations into the molestation case of an American woman allegedly by an Australian cricketer at Delhi last week.
Written by Cricket Country Staff
Published: May 21, 2012, 01:14 PM (IST)
Edited: May 21, 2012, 01:14 PM (IST)
CCTV footages identified KP Appanna with Luke Pomersbach in the corridor of the hotel © AFP
New Delhi: May 21, 2012
Royal Challengers Bangalore (RCB) player KP Appanna’s name has cropped up in the investigations into the molestation case of an American woman allegedly by an Australian cricketer at Delhi last week.
Investigators claimed that Appanna was the person who accompanied Luke Pomersbach when he went to the victim’s room for the second time.
Pomersbach was arrested on Friday after Zohal Hameed alleged that he molested her and hit her fiance Sahil Peerzada when he objected to the cricketer’s behaviour. Peerzada was punched in his ear following which he had to undergo a surgery.
“We have examined the CCTV footages and identified Appanna. We have spoken to him. We are yet to formally question him,” a senior police official said.
Appanna, a leg spinner who plays for Karnataka in Ranji Trophy, could not be contacted for his comments.
He was allegedly seen with Luke at the corridor of the hotel, the official said, adding they were yet to ascertain whether he entered the room where the victim was staying.
Zohal had alleged that some team members of Luke had pressurised her to withdraw the case against Pomersbach.
Peerzada, a model-turned businessman, told police that he has been punched “3-4 times” by the Royal Challengers team member, a senior police official claimed.
Police sources said Peerzada described Hameed as his girlfriend and not as fiancee during the recording of the statement.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.