WATCH- Ajinkya Rahane recalled from pavilion by umpires after no-ball drama during Mumbai v J&K Ranji match

The incident happened during Mumbai v J&K Ranji Trophy 2024-25 match in BKC, Mumbai.

Ajinkya Rahane | X

Mumbai captain Ajinkya Rahane was involved in a dubious debate during his team’s ongoing Ranji Trophy 2024-25 match against Jammu and Kashmir (J&K). The match is being played at the Sharad Pawar Cricket Academy in BKC, Mumbai.

Mumbai was bowled out for 120 runs in the first innings after winning the toss and choosing to bat first. In response, J&K slammed 206 runs in their first innings.

Despite a good start to Mumbai's second innings, with Rohit Sharma (28) and Yashasvi Jaiswal (26) adding 54 runs for the first wicket, the hosts struggled against disciplined bowling. They were soon reduced to 101/7 in no time, taking a slender lead in the process.

The umpiring standards in Indian cricket were once again called into question after Mumbai skipper Ajinkya Rahane was called back by the on-field umpires nearly five minutes after being dismissed and entered the changing room as the third umpire informed him that the bowler had overstepped.

The incident occurred in the 25th over of Mumbai's second innings on day two. Umar Nazir, the J&K pacer, bowled a short ball and caught Rahane off guard. He was restricted for space while playing the pull shot and could only glove it to the wicketkeeper.

The drama, however, started after that. Rahane quickly went back to the dressing room, and the next batter, Shardul Thakur, stepped in to bat, while the umpires were still checking the no-ball.

The replays took some time to load, and when the third umpire agreed that Nazir had overstepped, the on-field umpires directed Thakur to go back and Rahane to return to the middle.

When Rahane returned to the crease, the umpires informed him that they had requested him to wait due to the no-ball check, but the Mumbai skipper was unable to hear.

See Here:

JioCinema, the game's official broadcaster, never showed the so-called no-ball during its live transmission. When contacted, the television production staff at the BKC ground stated that they did not have access to the tape but that the third umpire did.

Nitin Goel, the third umpire and match referee, explained that the misunderstanding and delay were caused by a lack of communication.

"When I tried reaching out to the umpire on the walkie-talkie, the umpire was on a different channel. So, it took some time to communicate to the on-field umpire. Rahane himself appeared on the screen, indicating that he did not hear the umpires asking him to wait. It was a clear no-ball and there was no doubt about it. I will send the relevant footage to the BCCI,” Goel was quoted by Cricbuzz.

According to the laws of the game, "An umpire shall intervene if satisfied that a batter, not having been given out, has left the wicket under a misapprehension of being out. The umpire intervening shall call and signal the Dead ball to prevent any further action by the fielding side and shall recall the batter.

A batter may be recalled at any time up to the instant when the ball comes into play for the next delivery unless it is the final wicket of the innings, in which case it should be up to the instant when the umpires leave the field."

Rahane was dismissed by Nazir in his next over, as he was out thanks to an outstanding diving catch by J&K captain Paras Dogra.

Even before Rahane’s incident, the umpiring standards in domestic cricket came for scrutiny as Shreyas Iyer was given out when it appeared that he had clearly nicked the ball to the keeper, but the batter was given out, despite his complaints. Rahane, who was at the non-striker's end, was also seen having a chat with the umpires.

 
 

By Jatin Sharma - 24 Jan, 2025

    Share Via