West Indies vs Sri Lanka: Former Cricketers Question Contentious Run Out Of Sri Lankan Batsman | Cricket News





West Indies defeated Sri Lanka in the first One-day International (ODI) on Wednesday to take 1-0 lead in the three-match series. While it was a clinical performance from the West Indies, there was an incident that took away all the spotlight — the run out of Sri Lanka opening batsman Danushka Gunathilaka. In the 21st over, Gunathilaka, batting on 55, defended a ball from Kieron Pollard and took off for a single but changed his mind midway and as he was trying to get back in his crease, the Sri Lankan batsman pushed the ball away from the West Indies skipper. Pollard was left frustrated and he appealed against Gunathilaka for obstructing the field. 

The on-field umpire went upstairs to check with TV umpire and after looking at few replays, he gave the decision in favour of the fielding side. 

Watch the video of the contentious run out here: 

Former cricketers took to social media to express their thoughts on the contentious run out call with veteran India off-spinner Harbhajan Singh questioning the International Cricket Council. 

Promoted

“How this is out?”, Harbhajan tagged ICC while asking the about the run-out decision. 

“Jeez .. just saw this …. NOT OUT 8 days of the week . He only looks down when he feels something hit his boot in my opinion #WIvSL,” former Sri Lanka cricketer Russel Arnold tweeted. 

Tom Moody termed the decision as a shocker while Michael Vaughan reacted by saying that cricket has officially gone bonkers. 

In the match, the hosts managed to bowl out Sri Lanka for 232 in 49 overs as Jason Mohammed and Jason Holder picked up two wickets apiece. 

In reply, Shai Hope slammed his 10th ODI century as the West Indies successfully chased down the 233-run target with eight wickets in hand.

Topics mentioned in this article





Source link

Leave a Reply

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

Releated

Error – NDTV Sports

You may not be able to visit this page because of: 4 You have no access to this page 5 The requested resource was not found 6 An error has occurred while processing you request Source link

%d bloggers like this: