RR vs RCB: Fans Outraged As Umpire Declares Dinesh Karthik Not Out In Controversial LBW Decision
RR vs RCB IPL 2024 Eliminator: Initially, Karthik appeared convinced he was out, and it took some persuasion from his partner, Mahipal Lomror, to review the LBW call made by the on-field umpire.
RR vs RCB: In a dramatic turn of events during the IPL 2024 Eliminator between Royal Challengers Bangalore and Rajasthan Royals at the Narendra Modi Stadium in Ahmedabad on Wednesday, May 22, Dinesh Karthik received a significant reprieve. Karthik, who was given out LBW on the very first delivery he faced in the 15th over of the RCB innings, saw the decision overturned after a review, denying Avesh Khan a double strike.
IANS
The decision from the third umpire, Anil Chaudhary, left many, including on-air commentators Sunil Gavaskar and Ravi Shastri, surprised and shocked. Initially, Karthik appeared convinced he was out, and it took some persuasion from his partner, Mahipal Lomror, to review the LBW call made by the on-field umpire. Avesh Khan, riding high on confidence after dismissing Rajat Patidar with the previous delivery, bowled a sharp inswinger that hit Karthik flush on the pads.
Upon reviewing the delivery, the third umpire examined replays. While the decision looked straightforward to the naked eye, the Ultra-Edge technology indicated a spike as the ball passed the bat. Simultaneously, Karthik's bat was also hitting his pad. However, the third umpire quickly overturned the on-field decision without reviewing additional replays, concluding that there was an inside edge.
No way this is Notout?
¡ª ABC (@Naruto___777) May 22, 2024
Standard of umpiring at IPL is so bad.#viratkohli #ipl #RcbvsRR pic.twitter.com/iszlc8tQq8
The decision was contentious because, at one point, there appeared to be a gap between the bat and ball. Typically, such spikes are observed when the ball hits the pad or body, and those from the bat tend to be smaller. The third umpire's declaration of an inside edge from the Ultra-Edge spike drew criticism, as he did not consider the possibility of the spike arising from the bat striking Karthik's pad.
The RR dugout expressed their displeasure, with Kumar Sangakkara even approaching the umpire to discuss the decision. The incident prompted strong reactions from commentators. Ravi Shastri, on-air during the game, did not hold back, calling the decision "an absolute shocker."
"If there's one word for it, it's an absolute shocker," Shastri remarked.
Legendary cricketer Sunil Gavaskar also voiced his disagreement, stating he clearly saw the bat hitting the pad rather than the ball.
"It looks to me that the bat has hit the pads. The ball is in front of the bat (when the spike was seen). The ball did not hit the bat, the pad hit the bat," Gavaskar commented during the broadcast.
Also Read: Virat Kohli Left Heartbroken As Chahal Outfoxes Him In Dramatic RR vs RCB IPL Eliminator
Social media was abuzz with fans questioning Anil Chaudhary's decision. Many took to X (formerly Twitter) to express their dissatisfaction with the third umpire's call, believing the wicket should have been given.
That was clear out. Even Dinesh Karthik knew it. Another umpiring blunder in this IPL. pic.twitter.com/S16lWFUxAG
¡ª R A T N I S H (@LoyalSachinFan) May 22, 2024
Dinesh Karthik was out LBW first ball. It was a plumb. The TV umpire gave a shockingly wrong decision.
¡ª Abhishek Mukherjee (@ovshake42) May 22, 2024
Happens. There is little option but to move on. :)
The umpire is an impact player for RCB. Dinesh Karthik was clear Out.
¡ª AJ (@iam_bakshi) May 22, 2024
But the umpire ???#RCBvsRR pic.twitter.com/MOA2CVLBoM
At this point, RCB head coach might get angry for not giving Dinesh Karthik out.
¡ª Silly Point (@FarziCricketer) May 22, 2024
The incident has sparked widespread debate about the accuracy and reliability of the decision-making process, especially in crucial matches such as the IPL Eliminator. As the dust settles, the discussion around the third umpire's role and the use of technology in cricket continues to gain momentum.
In their allotted 20 overs, RCB scored 172 runs while losing eight wickets. At the time of writing, Rajasthan Royals had reached 53 runs for the loss of one wicket in 6.1 overs in the second innings.
For more news and current affairs from around the world, please visit Indiatimes News.
We keep you updated with the latest happenings from India and across the globe. Whether it's something quirky, emotional, inspiring, or informative ¨C we've got you covered.
