Indian T20 League 2022: Rishabh Pant, Pravin Amre and Shardul Thakur penalized for no-ball controversy

The 15th edition of the Indian T20 league saw its first controversy during the game between Rajasthan and Delhi. While the game went right down to the wire. Things were tense towards the end. Thus, a few people from the Delhi camp saw their emotions get the better of them.

This included the likes of their captain Rishabh Pant, their coaching staff member Pravin Amre, as well as their all-rounder Shardul Thakur. They were visibly upset when the umpire decided to call the third ball of the 20th over a legitimate delivery, despite the replays showing it to be a potential no-ball. As a matter of fact, Pant had even called the batters back from the field.

However, they then carried on as the Delhi-based franchise fell short of their target by 15 runs. However, Delhi's members had to face the consequences of their actions. Thus, Pant Amre and Thakur have been fined. The 53-year-old has been banned for a game as well.

“Delhi captain Rishabh Pant has been fined 100 percent of his match-fee for breaching the Code of Conduct during his team’s match against Rajasthan at Wankhede Stadium, Mumbai,” said the Indian T20 league in a release on Saturday. “Mr Pant admitted to the Level 2 offence under Article 2.7 of the Code of Conduct and accepted the sanction. Shardul Thakur has been fined 50 percent of his match-fee, and the assistant coach Pravin Amre has been fined 100 percent of his match-fee for breaching the Code of Conduct. He will also face a one-match ban for the offence," it added.

In the meanwhile, Pant expressed his disappointment over the umpire's decision during the post-match presentation. He stated that the no-ball could have been precious for them. Further on, he felt that the third umpire should have interfered.

"I think they were bowling well throughout the game but in the end Powell gave us a chance, I thought that no-ball could have been precious for us but it is not in my control. Yes, disappointed but can't do much about it. Everyone was frustrated (in the dugout) that it was not even close, everyone in the ground saw that, I think the third umpire should have interfered and said it was a no-ball," said Rishabh Pant.