West Indies keeper suspended for two ODIs

Ramdin was also fined his match fee.


Afp/web Desk June 10, 2013
Ramdin (R) had wrongly claimed to catch Misbah. PHOTO: REUTERS

LONDON: West Indies wicket keeper Denesh Ramdin has been fined his match fee and suspended for two one day internationals after being found guilty of a Level 2 breach of the ICC Code of Conduct during the Champions Trophy 2013 match against Pakistan on Friday, Cricinfo reported.

Ramdin had wrongly claimed to catch a ball edged by Pakistani skipper Misbahul Haq during Friday’s Champions Trophy clash at The Oval.

Match referee Chris Broad charged Ramdin with violating the spirit of the game following a hearing in London after the wicket-keeper had pleaded not guilty to the offence.

"This is regarded as a serious offence as it is the responsibility of all players to act in the spirit of the game," Broad said in a statement released by the International Cricket Council.

"I hope Ramdin has learnt his lesson from this incident and that we will not see such behaviour by him or any player in the future."

Australian umpire Steve Davis gave Misbah out during Friday's match but, following the intervention of English official Nigel Llong at square leg, the decision was referred to third umpire Tony Hill.

Replays showed that while Ramdin had, initially, caught the ball, he had subsequently allowed it to spill out of his grasp.

Eventually it was decided that Ramdin did not have full control over the ball and Misbah was reprieved.

Misbah went on to score 96 runs in the match, but the West Indies managed to win the encounter.

All players found guilty of a Level 2 offence at a hearing have a right to appeal the decision to a Judicial Commissioner, within 24 hours of receipt of that decision. Pending the outcome of the appeal, the sanction imposed will apply.

If the suspension holds, Ramdin will miss matches against India and South Africa.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ