AUS vs IND | Twitter questions umpiring after Kettleborough misreads Ultraedge to burn India's review
With the rapid advancement of technology in sports, one expects a fair amount of decision-making from the match officials. However, it hasn't been the case in the ensuing Border Gavaskar Trophy with the latest mishap being a TV umpire decision that favoured against the Men in Blue in Adelaide.
Australia's top-order fell prey to Jasprit Bumrah’s heat with the ball in the first hour of the morning session but Travis Head and Marnus Labuschagne came to the rescue against the worn-out ball. The pair orchestrated a 65 runs partnership in between to keep the Indian bowlers at bay before Nitish Kumar Reddy turned out to be the visitors golden arm. With India looking to seize the moment and make further inroads, the TV umpire assisted new batter Mitchell Marsh in the 58th over.
The third ball of the 58th over saw Ashwin spray a fuller one at the stumps that Marsh tried to prod forward and play at it. As the ball spun into the right-hander a tad bit, the batter was thud at the pad followed by the Indian appeal getting overturned by umpire Richard Illingworth. However, the visitors reviewed the decision and to everyone’s surprise TV umpire Richard Kettleborough hurried the decision and gave Not Out on the basis of Snicko. For a twist, the broadcaster replays showed a different angle that suggested that the ball hit the pad first. The Indian contingent seemed bemused by the TV umpire’s process who didn’t follow the protocols and avoided the ball tracking. Eventually, India lost a review due to ‘inconclusive evidence’ and the Twitterverse seemed visibly frustrated.
It was same
"KL's was the same in Perth, two spikes" 🍿 pic.twitter.com/a0FZB0Vk3I
— POTT⁷⁶⁵ (@KlolZone) December 7, 2024
Very hard
Bat or pad first? Hard to say - sticking with the umpire's call #AUSvIND pic.twitter.com/UqsoPvEruJ
— cricket.com.au (@cricketcomau) December 7, 2024
Controversy
Third umpire couldn't recognise whether it's bat or pad first and declared batter as not out
— HXF (@huzaiff_01) December 7, 2024
Virat to Umpire : KL's was the same in Perth, two spikes bat and pad. pic.twitter.com/LMid1Wr1Iy
Pad first
Definitely pad first and Umpire didn't even went for ball tracking. Same old aussies cheating again!!! pic.twitter.com/jzuIqtEC4h
— Div🦁 (@div_yumm) December 7, 2024
Shocker
How is this not pad first !!! What a shocker of a decision this is !! #SteveSmith #Siraj #JaspritBumrah #INDvsAUS #INDvAUS #AUSvIND #AUSvsIND #nitishkumarreddy pic.twitter.com/OrKoPdswmQ
— Cricketism (@MidnightMusinng) December 7, 2024
What was he doing?
No Conclusive evidence - Haven’t going pet protocols - snicko completely saying pad first
— रोहित जुगलान Rohit Juglan (@rohitjuglan) December 7, 2024
What was that Richard Ketel doing there
Hill to die on
This is my hill to die on. When on-field umpire gives not out, he has to say why. If he thought bat first, but ball was hitting the stumps & then technology shows it was pad first - the on-field call should change.
— Saurabh Somani (@saurabh_42) December 7, 2024
Also in this case, India wouldn't have lost a review at least. https://t.co/3X94EN3RWn
Bat first
Haha that review if this was indian player specially kohli it would have been pad first. But if it's an australian player so bat first.
— Archer (@poserarcher) December 7, 2024
True
If it was Virat Kohli, it would’ve been pad first. 😂 pic.twitter.com/KUwrb36Mp9
— Krishna. (@KrishVK_18) December 7, 2024
Definetly pad first
It was definitely pad first… the umpires seem unsure of what they’re doing. No conclusive evidence? But look here… it clearly shows the ball hit the pad first! pic.twitter.com/2lylwjJgX8
— Vipin Tiwari (@Vipintiwari952) December 7, 2024
It's Clear
I'm 100% sure there have been atleast 2 instances with Kohli where his bat pad was much closer at time of contact and both times he was given out
— Pricviz (@Pric_viz_) December 7, 2024
Here it was clearly pad first
Get updates! Follow us on
0
0
0
1
0
0
Comments
Sign up or log in to your account to leave comments and reactions
0 Comments