'Absolutely disgusting': Fans fume over Virat Kohli controversy
Cricket fans have taken aim at the standard of umpiring and the Decision Review System (DRS) after a controversial incident involving Royal Challengers Bangalore batsman, Virat Kohli.
Kohli was incensed by a DRS review that denied the bater what looked like it was going to be a classy fifty in RCB's seven wicket victory over the Mumbai Indians.
'HARDEN UP': Proteas fire back over 'deplorable' Test cricket saga
'DID THAT HAPPEN': Pat Cummins goes berserk during record IPL act
'THEIR LOSS': Women's World Cup snub sparks Channel Nine backlash
Kohli was unhappy to be given out lbw for 48 in the closing moments of the match, but his disappointment was nothing like the dismay the Indians will be feeling as they await a first win of the campaign.
Australia's Glenn Maxwell finished the match with successive fours as RCB crushed to 3-152 to secure victory with nine balls to spare.
However, it was the wicket of Kohli that left the former India captain and fans fuming after South African teenager Dewald Brevis slammed a ball into the batter's pads.
Kohli was stunned to see the umpire's finger go up and immediately reviewed the decision, certain that his bat had made contact with the ball.
TV umpire Ulhas Gandhe called on ultraedge to help him decide whether there was a slight edge off bat before the ball struck Kohli's pad.
“Ball is close to the bat as well as pad, it’s simultaneous,” Gandhe said.
Ball-tracking indicated that ball would have gone on to collect the stumps, with Gandhe instructing the umpire to stick with his original decision of 'out'.
Confused fans took to social media in disgust afterwards, insisting that the benefit of doubt should have gone to the batsman in the event of simultaneous contact between bat and pad.
Umpiring 😡😡
Third umpire clearly said that it's hit bat & pad simultaneously but gave out😡😡
(As per rule, if it's "simultaneously",then not out)
Fixer😡 #mivsrcb #rcbvsmi #ViratKohli𓃵 https://t.co/N7wBhsEjj5— Ehtesham khan (@eashm16_10) April 10, 2022
Though I'm not a fan of @imVkohli but in a true gentleman manner it's clear edged. NOT OUT 110%
— Nikhil Akkistani (@NikhilAkkistani) April 10, 2022
Never seen a unlucky player as Virat Kohli.!Even yesterday's out was also unlucky,if we see the law clearly he is not out.! Nevertheless enjoyed that classical knock.!
— Deep Point (@ittzz_spidey) April 10, 2022
Missed a well built fifty due to poor umpiring... it was clearly not out. Once a king, always a king. Never mind. Next matches well deserved fifty is loading. #ViratKohli𓃵 #RCBvMI #ViratKohli #KingKohli #IPL2022 #IPL
— हरा_अर्थशास्त्री 🇮🇳 (@RE_Economix) April 10, 2022
As of my knowledge ball hit bat and pad simultaneously means the decision should favour in batsman side as not out #ViratKohli #RCB pic.twitter.com/tPOKCpvEpm
— Sam Lenin (@SamLenin7) April 9, 2022
Kohli was NOT OUT ..absolute disgusting 3rd umpiring 🤯😭 @imVkohli pic.twitter.com/wQ60ZXPvXe
— Rizwan 🇮🇳 (@rizwanahmed_24) April 9, 2022
Why this picture is so hurting?? Like he is complaining to the God why it's always me?? 🥺
According to the rule book it's not out!!
Why my man is the only one who suffered alot 😒@imVkohli you played very well boii!!! Just keep going well ❤🧿#ViratKohli𓃵 #RCBvsMI pic.twitter.com/OzwZS9zhM3— Bakku❤ (@Bakku_1826_) April 9, 2022
Virat Kohli was clearly not out. If the ball and bat hit simultaneously then according to the rule, the bat should be considered first
Kohli missed 50 by this poor decision, that's done by the 3rd Umpire😲
Thankfully it won't affect the result#RCBvMI #ViratKohli #Kohli #IPL— Vikas Kohli (@imvikaskohli) April 9, 2022
This is literally me after that Decision :-#ViratKohli𓃵 pic.twitter.com/6yhqTju3BT
— Prince Kumar (@maihoonprinx) April 10, 2022
A clearly furious Kohli could be seeing hitting at the ground with his bat as he stormed off back to the pavilion.
“Kohli doesn’t like it and I’ve got to say, question marks around it,” one commentator said.
“Furious. I don’t blame you, VK.”
Suryakumar Yadav heroics in vain for Mumbai
Mumbai began their innings brightly enough as Ishan Kishan and Rohit Sharma put on 50 for the first wicket. But once Rohit fell for 26, caught and bowled by Harshal Patel, it sparked a stunning collapse.
Dewald Brevis made eight, but he went with the score on 60, and it was soon 5-62 when Kishan (26), Tilak Varma (0) and Kieron Pollard (0) headed back to the dressing room.
When Ramandeep Singh was caught behind off Harshal by Dinesh Karthik, Mumbai were 6-79 and looking in all sorts until a vital cameo from the in-form Suryakumar Yadav (68 not out).
He set about carrying the team into three figures before cutting loose late on, taking three sixes off Mohammed Siraj in the 19th over before smashing Harshal for another maximum from the final ball of the innings.
Yadav then took the catch that broke up RCB's opening partnership, showing safe hands at long-on to remove Faf du Plessis for 16 and give Jaydev Unadkat an early wicket.
As with Mumbai, that first wicket fell with the score on 50, but RCB did not crumble as the Indians did.
Rawat impressed, while Kohli was dropped just inside the deep square leg boundary by Brevis off Basil Thampi at the start of the 15th over, the ball squirting away for four.
It was rather academic by then, and although Rawat fell to a smart piece of fielding by Ramandeep, and Kohli was unimpressed at being given out, RCB were soon home and hosed.
with agencies
Click here to sign up to our newsletter for all the latest and breaking stories from Australia and around the world.