Aakash Chopra labels IPL umpire the villain in the Rajat Patidar–Jason Holder catch controversy ...Middle East

cricketaddictor - News
Aakash Chopra labels IPL umpire the villain in the Rajat Patidar–Jason Holder catch controversy

The IPL 2026 match between Royal Challengers Bengaluru (RCB) and Gujarat Titans (GT) may be over, with the win by four wickets in Ahmedabad, but the debate over Rajat Patidar’s controversial dismissal, courtesy of Jason Holder’s brilliant catch, is far from ending.

Fans and cricket experts are sharing their views on the umpiring call, and now the former Indian batter and well-known commentator, Aakash Chopra, has shared his views on the drama.

    The controversy unfolded when Arshad Khan bowled a short ball and Rajat Patidar mistimed his shot. The ball went towards fine leg, where Jason Holder ran in and took a diving catch. At the first glance, the catch looked clean, but the replay confused one and all.

    Read Also: Kevin Pietersen takes fresh aim at Alastair Cook, brings Jos Buttler into Jacob Bethell controversy

    It looked like the ball touched the ground while Holder was sliding. Still, the third umpire gave it out to Patidar, and Aakash Chopra feels the decision was wrong. He explained that a catch is only complete when the player has full control, and the ball should not touch the ground at all.

    Aakash Chopra questions umpire's decision

    Since Holder was still moving and sliding, the cricket pundit believes that the catch was not properly completed, and he openly said that the umpire made a “mistake” in his judgment.

    Aakash Chopra said in a video on his YouTube channel, “In my opinion, it wasn't a catch. Law 33.3 has a clear distinction: once the ball comes into your hand, you need to have full control of the ball and your body, and until then, the ball shouldn't touch the ground. Your hand can touch the ground, but the ball can't.”

    The commentator added, “Jason Holder took the catch and slid. When you are sliding, your body is still in motion, and it is not in complete control. When he was sliding, the ball had touched the ground, and the ball wasn't dead by then. The catch had not been completed. I felt the umpire made a mistake there. It should have been given out, not in.”

    Read Also: Ajit Agarkar receives orders from Virender Sehwag to give Bhuvneshwar Kumar a T20I recall

    Aakash Chopra orders RCB to continue their aggressive style

    Despite having an explosive batting unit, the RCB bowled out for just 155 runs in 19.2 overs, with Arshad Khan starring with the three-wicket haul at the Narendra Modi Stadium. In reply, Gujarat Titans chased down the target inside 16 overs to win the match by 4 wickets on April 30.

    This batting collapse surprised many, but Chopra wants RCB to continue with the same aggressive template going forward in the ongoing IPL 2026. He explained, “Was getting all out a concern for RCB? I would say it isn't a concern. If you bat at such a pace, it will happen once in a while.”

    He signed off by saying, “This might happen with the SunRisers Hyderabad someday, where you are scoring 250 runs, and a 125-run match might come someday. That is a possibility. When you take so much risk, this could be a side effect at times. They will have to forget this game and just continue in their own merry way, because they are playing well. I actually liked Devdutt Padikkal's inning.”

    Hence then, the article about aakash chopra labels ipl umpire the villain in the rajat patidar jason holder catch controversy was published today ( ) and is available on cricketaddictor ( Middle East ) The editorial team at PressBee has edited and verified it, and it may have been modified, fully republished, or quoted. You can read and follow the updates of this news or article from its original source.

    Read More Details
    Finally We wish PressBee provided you with enough information of ( Aakash Chopra labels IPL umpire the villain in the Rajat Patidar–Jason Holder catch controversy )

    Apple Storegoogle play

    Last updated :

    Also on site :