Five most controversial dismissals in modern-day cricket
Over the years, the gentleman’s game has evolved a lot with new technologies and rules coming into the play. However, there are still times when the decisions related to an individual’s dismissal by the on-field umpire and third umpire have stirred controversy. Here’s a list of top 5 controversial dismissals in modern-day cricket
Jason Roy’s dismissal for obstructing the field against South Africa (2017)
Playing in the second T20I of the three-match series in 2017, England’s opening batsman Jason Roy was involved in an embarrassing dismissal against South Africa as the third umpire found him guilty of obstructing the field while trying to save his wicket. In the 16th over, Liam Livingstone pushed the ball towards the point and Roy tried to take a single. However, after Liam denied the same, Jason took a u-turn and tried to cross the line before the stumps were uprooted. In the replay, the batsman was seen trying to deliberately run inside the line of throw and was adjudged out.
WICKET Roy out obstructing the field for 67 off 45 balls.
133-3 in the 16th #ENGvSA
Follow: https://t.co/JxdwNtG5cv pic.twitter.com/3yF7vRayDe
— England Cricket (@englandcricket) June 23, 2017
Ben Stokes’ dismissal for obstructing the field against Australia (2015)
England’s Ben Stokes was dismissed in the same fashion in a game against Australia in 2015. While facing Mitchell Starc, Stokes hit the ball towards the bowler by coming out of his crease. As soon as Starc collected the ball he decided to throw it back towards Stokes’s side. However, the all-rounder had stuck out his hand to block the return at his stumps which made Australians appeal for obstructing the field dismissal. After seeing the replay a number of times, the umpire gave the decision in the favour of the bowler.
Think what went against Stokes was that he moved his hand to bring it in line. Umpire had to decide if deliberate or in defence. Tough call
— Harsha Bhogle (@bhogleharsha) September 5, 2015
David Warner’s dismissal against RCB in IPL 2020
David Warner was caught in a controversial dismissal during the 13th edition of the Indian Premier League while playing for his franchise Sunrisers Hyderabad in the Eliminator against Royal Challengers Bangalore. A delivery by Mohammed Siraj had slightly touched Warner’s gloves or trouser as there was a spike and was collected by the wicketkeeper AB de Villiers. Upon review, the third umpire didn’t have conclusive evidence of the ball touching Warner’s bat or gloves but he decided to turn the decision in the favour of the bowler.
WATCH – VK gets the DRS right
Big wicket at stake, close call, @imVkohli opts for the DRS in the nick of time and the third umpire rules Warner out. Superb review from the RCB captain.
??https://t.co/4Brs8hh3f5 #Dream11IPL #Eliminator
— IndianPremierLeague (@IPL) November 6, 2020
R Ashwin Mankads Jos Buttler (IPL 2019)
The incident of Ravi Ashwin mankading Jos Buttler in a game during IPL 2019 had garnered a lot of headlines and had stirred a debate in the cricket fraternity regarding its credibility. As Ashwin was preparing to bowl the next ball, Buttler left the crease and the bowler stopped his run-way in the middle to uproot the stumps and sent the RR batsman back to the pavilion.
“No real argument and it’s pretty instinctive. I actually didn’t load and he left the crease. That’s always been my take on it because it’s my half of the crease. He wasn’t even looking at me and he just left the place” – Ashwin on the Buttler mankad
— Broken Cricket (@BrokenCricket) March 25, 2019
Usman Khawaja’s caught behind dismissal during 2013 Ashes
The Australian team was left fuming when the umpires had given their batsman Usman Khawaja out even when there was no visible contact between the bat and the ball. On the delivery by Graeme Swann, Khawaja missed the shot and the ball was caught by the wicketkeeper. However, the on-field umpire came up with the decision in favour of the bowling team after England appealed for a nick. Upon checking, the third umpire also decided the same though there was nothing on the hotspot.
