Rajasthan Royals vs Delhi Capitals: The no-ball controversy | Explained
- Rajasthan Royals scored 222 in its 20 overs
- Delhi Capitals scored 207
- A last over controversy led to Rishabh Pant being fined
Rajasthan Royals’ match against Delhi Capitals on Friday in the 2022 edition of the Indian Premier League would have been a dead T-20 if not for the dramatic last over. Chasing a steep 222, Delhi Capitals needed an unlikely 36.
If cricket were not a game of surprises, the match would have been written off.
Obed McCoy was with the ball and his fellow Caribbean teammate Rovman Powell was on the other side. The first ball goes for a six, the second, for a six and then the third for another six. 18 runs scored of three balls, and 18 more to go. A hopeless match seemed to turn on its head.
But the third ball changed things. A high full toss that was hit for a six changed the course of the match and let to some of the most bizarre scenes on field.
Delhi Capitals expected the high full toss to be given a no ball. That would give them an extra run, an extra ball and a free hit on the extra ball. However, the umpire disagreed. This upset the Delhi dugout to no end and triggered a reaction that was not only surprising but also changed the momentum of the match.
Flustered that the on-field umpire had not taken the help of the third umpire, an angry Rishabh Pant, captain of Delhi Capitals, signalled his batters to walkout of the field. As they started walking out, the umpires intervened. The umpires attempted to calm tempers when suddenly chaos ensued; Rishabh Pant had sent Pravin Amre, an assistant coach of the team, to speak to the umpires.
An altercation later, Delhi could score just two runs of the remaining three balls and lost a wicket on the last.
Delhi Capitals’ skipper Rishabh Pant has been fined 100% of his match fee for violating the IPL Code of Conduct. Shardul Thakur too has been fined. Pravin Amre, who went to the field to argue with umpires, has been banned for a match.