KL Rahul fell to a controversial decision after batting well for his 26 off 74 deliveries in the first innings of the first Border Gavaskar Trophy Test in Perth.
It was the second delivery of the 23rd over of the innings. Mitchell Starc bowled that delivery from over the wicket, and the ball held its line as it passed really close to Rahul’s outside edge. There was a clear noise as the ball went past his bat. However, the on-field umpire, Richard Kettleborough, was unmoved as he felt the noise came from the bat hitting the pad, as both were in close vicinity when the ball went past the outside edge.
Australia and Pat Cummins wasted no time in taking a review for it right after losing one in Starc’s previous over.
TV Umpire Richard Illingworth spotted the bat-pad issue. However, while the outside edge was confirmed on the snicko meter from the side-on view, the broadcaster did not have a front-on snicko view which would have confirmed whether the spike came from the outside edge or the bat hitting the pad.
"His pad and bat are not together at that point in time as the ball passes.
— 7Cricket (@7Cricket) November 22, 2024
"It's (bat hitting pad) after, in fact, the ball passes the edge. Does Snicko pick up the sound of the bat hitting the pad?
"We're assuming (Snicko) may be the outside edge of the bat but that may not… pic.twitter.com/hvG0AF9rdo
With there being no conclusive evidence, then, the third umpire would have been expected to stick with the on-field decision, which was not out, but Illingworth asked the on-field umpire to reverse his decision and adjudge Rahul out. The call from the third umpire not only shocked the batter, but also the commentators, who expected the umpire to stick to the original call.
Rahul visibly showed his dissent against the decision as he returned to the pavilion, shaking his head, indicating that his bat had hit the pad. He was in control in his 74-ball stay at the crease and looked like the best Indian batter on show.
With his dismissal, India were in deep trouble after the first session as they went into lunch four wickets down for just 51 runs.
If you’ve not downloaded the Cricket.com app yet, you’re missing out on our content — big time. Download the App here.