Royal Challengers Bengaluru (RCB) took on Rajasthan Royals (RR) in Eliminator of the Indian Premier League (IPL 2024), at the Narendra Modi Stadium in Ahmedabad, on (Wednesday) May 22. RCB struggled to get going as Trent Boult bowled a tight spell upfront in the powerplay giving away just six runs in three overs. RR later on managed to pluck timely wickets and Dinesh Karthik entered the fray.
After getting hit for a six in the previous delivery, Avesh Khan had just made Rajat Patidar hole out to Riyan Parag. Karthik was facing the first delivery and Avesh bowled a fuller length that nipped in back. Karthik rushed to defend the ball crouching forward. The ball seemed to hit the pad plumb and the umpire raised his finger. The veteran decided to challenge the decision and the third umpire entered the scene.
The replays showed a hint of spike when the ball passed the bat before hitting the pads. The third umpire preferred reversing the decision. But for many the point of concern was the spike popping up as the bat hit Karthik’s pad before the ball was closed to the bat. Even Sunil Gavaskar was livid with the decision and termed it game-changing if the wicket-keeper batter banked on it.
Karthik fails to capitalise on the lifeline
As it turned out, Karthik struggled to get going even after he got a lifeline from an unusual source. He scored just 11 runs in 13 deliveries with a lone boundary. He was eventually dismissed by Avesh himself bowling the crucial 19th over of the innings. The Tamil-Nadu batter failed to time the slap off a short ball and Yashasvi Jaiswal did the honours at the extra cover.
Here’s how ‘X’ users reacted to the dismissal fiasco:
We simply need to go back to the on-field umpire taking control of all decisions.
Remove player reviews and use the 3rd umpire to overturn any on-field errors. #RRvRCB
— Tom Moody (@TomMoodyCricket) May 22, 2024
There was no bat. If there was, Dinesh would have taken DRS straight away.
— Irfan Pathan (@IrfanPathan) May 22, 2024
That decision in the live cricket match was absolutely terrible!
Seriously, what was that all about?. It was so obvious that he was out! The qualification of the third umpire is seriously in question here. Are they blind or they have no knowledge about cricket at all?infuriating!
— Sreesanth (@sreesanth36) May 22, 2024
It was a shocker .. these mistakes shouldn’t happen at this level .. https://t.co/lFmzZJ07HT
— Michael Vaughan (@MichaelVaughan) May 22, 2024
Bat hit pad, also DK looked hesitant to review as he knew he was out. Third umpire got it wrong again. #RCBvRR #Eliminator #IPL2024 pic.twitter.com/psudjyMqbv
— Wasim Jaffer (@WasimJaffer14) May 22, 2024
There’s a reason why technology has been introduced in cricket – to make the right call. And I wonder why the third umpire is always in a hurry . That was clearly bat hitting the pad first . Was plumb infront IMO. #RRVSRCB
— Shreevats goswami (@shreevats1) May 22, 2024
The bat hit the pad .. that was OUT .. #IPL .. Shocking decision ..
— Michael Vaughan (@MichaelVaughan) May 22, 2024
THE SOUND WAS OF BAT HITTING THE PAD.
No batter would take review this late if this much thick edge. RR are robbed here.#RCBvsRR #RRvsRCB pic.twitter.com/zINF5iABfR
— Himanshu Pareek (@Sports_Himanshu) May 22, 2024
Well paid rcb👏
Bat was hitting to pad but..🤐#RCBvsRR #RRvsRCB pic.twitter.com/3yCXvj3jL4
— Giriraj Dhaker (@cricket24_) May 22, 2024
Twitter Reactions: West Indies clean sweep South Africa after comprehensive win in 3rd T20I
Twitter Reactions: West Indies dominate South Africa in second T20I to clinch series
Twitter Reactions: Pakistan stumble under pressure, England bag comfortable win at Edgbaston
Twitter Reactions: Bangladesh smash USA in third T20I to regain lost prestige
