Delhi Capitals captain Rishabh Pant made headlines for calling back his batters after the umpires did not check for possible waist-high delivery in the dramatic final over of their IPL 2022 match against Rajasthan Royals on Friday (April 22) at Wankhede Stadium, Mumbai.
Needing 36 runs from the final over, DC batter Rovman Powell hit three successive sixes from the first three deliveries off Obed McCoy. DC needed another 18 more from the final three deliveries.
At this juncture, Kuldeep Yadav, who was at the non-striker’s end, gestured to the umpires demanding that the last delivery be checked for a possible no-ball on height. Powell joined in having a chat with the umpires too. The umpires stood their ground, saying the delivery was legal.
— Nara Akhil Chowdhury (@prabhas_mania17) April 22, 2022
Pant then gestured Powell and Kuldeep to come out though assistant coach Shane Watson tried to reason him out. Another DC coaching staff member Praveen Amre went into the playing arena but was told to go back by the umpires. The match though resumed after a long delay and DC lost by 15 runs.
Royals opener Jos Buttler, who hit a match-winning 116, was also seen having words with Pant near the boundary line.
Meanwhile, netizens were quick to react to Pant’s antics and compared the incident to MS Dhoni’s infamous controversy as the former Chennai Super Kings skipper was also involved in similar drama two years ago and incidentally, it was also during the match against RR in IPL 2020. Notably, Dhoni marched onto the field after a controversial decision by an umpire but even on that day, the on-field decision stood despite the protest.
Here’s how netizens react to Pant’s protest:
First ever declaration in T20 cricket. Captain Rishabh Pant. pic.twitter.com/xgyr8DUt9v
— Manya (@CSKian716) April 22, 2022
Rishabh Pant taking inspiration from MSD pic.twitter.com/HouaN4dOcj
— SG (@RCBSG17) April 22, 2022
Rishabh Pant welcome to Dhoni Academy
— Umesh Darade (@DaradeUmesh) April 22, 2022
Then MS Dhoni
Now Rishabh Pant
— Nilesh G (@oye_nilesh) April 22, 2022
It was a no ball, clear cut no ball.
— (@superking1814) April 22, 2022
So umpires check no balls for front foot every ball, but can’t check a high full toss? Makes sense… pic.twitter.com/RUOX3Yh3YF
— Glenn Maxwell (@Gmaxi_32) April 22, 2022
Asked about the incident at the post-match presentation, Pant said, ”I thought the no ball could have been precious for us. I thought we could have checked that no ball, but it’s not in my control.
”Yes, disappointed, but can’t do much about it. Everyone was frustrated because it was not even close, so I thought it was only a no ball. Everyone in the ground saw that.
”I think third umpire should have intervened in between and said it was a no ball, but I can’t change the rule myself I guess.”
Asked if it was all right to send a team management member onto the field to argue for not calling a no-ball, Pant said, ”Obviously it wasn’t right, but what happened with us was also not right. It was just the heat of the moment, can’t do much about it.
”I think it was the fault of both of the sides, not even only for us because throughout the tournament we have seen some good umpiring.”
Royals captain Sanju Samson said, ”It went for a six, it was a full toss and the umpire gave it a normal ball. But the batsman wanted it as a no ball.
”I think umpire made his decision very clear and sticked to it.”