Rishabh Pant arguing over a No-Ball Call with the Umpires
The tension escalated quickly. Pant, clearly upset, signaled his batters to return to the dugout, effectively halting the match. Assistant coach Pravin Amre even walked onto the field to confront the umpire. Players from both sides got involved, and the scene turned chaotic for a few minutes. Let’s rewind to that fiery evening and uncover what sparked this unforgettable clash.
The clash between Rajasthan Royals and Delhi Capitals on April 22, 2022, turned into a festival of power-hitting and high drama at the Wankhede, with Jos Buttler once again stealing the spotlight. The Royals, powered by Buttler’s sensational hundred, piled on a massive 222 for 2, and despite a spirited effort from the Capitals, held on to win by 15 runs.
Delhi Capitals won the toss and opted to field, perhaps looking to take advantage of the dew factor later in the evening. However, what followed was a brutal display of batting by Rajasthan Royals’ top order, headlined by yet another century from Jos Buttler which was his third of the season.
Opening with Devdutt Padikkal, Buttler launched into Delhi’s bowling attack right from the start. Though the powerplay yielded a moderate 44 for 0, the foundation was set. The duo switched gears quickly, bringing up their 50-run stand in 6.5 overs. Padikkal, often playing the anchor in previous games, looked fluent and aggressive. He reached his fifty in just 31 balls, with 7 fours and 2 sixes.
Buttler, on the other hand, showcased a masterclass in T20 acceleration. He brought up his fifty in 36 balls but exploded in the back half of his innings. His final 66 runs came off just 29 deliveries. The pair added 155 runs for the opening wicket in just 15.1 overs, setting the tone for a mammoth total. Padikkal fell lbw to Khaleel Ahmed for a 35-ball 54, but there was no respite for Delhi. Skipper Sanju Samson came in with intent and lit up the stadium with a fiery 46 not out from just 19 balls, striking 5 fours and 3 sixes. Buttler finally perished in the 19th over, caught by Warner off Mustafizur for a scintillating 116 off 65 deliveries, decorated with 9 fours and 9 sixes.
With just two wickets lost, Rajasthan finished at a towering 222 for 2, the highest total of IPL 2022 at that stage. The Delhi bowlers were taken to the cleaners, with only Prasidh Krishna maintaining some control. Khaleel Ahmed picked up a wicket but went for 47 runs, while Mustafizur conceded 43 from his 4 overs. Kuldeep Yadav and Lalit Yadav also went wicketless and expensive, further highlighting the hammering their attack took.
Chasing 223 for victory, Delhi Capitals came out with aggressive intent. Prithvi Shaw and David Warner gave the team a flying start. Warner smacked a quickfire 28 off 14 balls before falling to Prasidh Krishna. Shaw continued the charge but was dismissed for 37 off 27 deliveries by Ashwin just before the halfway stage. The middle overs saw Delhi losing their way slightly. Sarfaraz Khan managed only a single, and captain Rishabh Pant, after a promising 44 from 24 balls, fell to Krishna at a crucial juncture. Lalit Yadav tried to keep Delhi in the hunt with a 24-ball 37, but the required rate kept climbing.
With the run chase getting bigger and better, Delhi needed a strong finish from their middle order. The target was still within reach, but it heavily relied on the shoulders of Rovman Powell, who had a big job to do for the team. But what eventually happened in the 19th over of the game changed everything for both the teams as this moment came out to remind the fans about MS Dhoni.
With the chase going well, the 19th over became an important moment in one of the most dramatic IPL matches of the season. Delhi Capitals were chasing a huge target of 223 against Rajasthan Royals, and they needed 36 runs from the final six balls. Rovman Powell was on strike, and what followed was a rollercoaster of power-hitting and controversy.
The first ball of the last over was in the slot, and Powell smashed it high over long-off for a six. The next ball went sailing over the cover boundary, and the crowd started roaring. Two deliveries, two sixes. Then came the third, which was a high full toss and Powell sent it into the stands again, but this time, the height of the delivery became the center of debate as the Delhi dugout, led by captain Rishabh Pant, erupted in frustration.
Pant felt the ball should have been called a no-ball for being above waist height. He was seen waving to his batters from the bench and even asked a member of the support staff to go onto the field and talk to the umpires. The umpires, however, stuck to their decision, saying the ball was legal and refused to refer it to the third umpire. It was a rare sight as the captain arguing from the sidelines, players talking to umpires, and Jos Buttler stepping in from long-on to speak to Pant. Tensions were high, and fans watching could feel the pressure on both sides. The long break also affected Powell’s rhythm.
He tried to go big again on the fourth ball but missed, then managed only two runs off the fifth. On the final ball, he went for one last swing but mistimed it and was caught behind by Samson. He ended with a brilliant 36 off 15 balls, including five sixes, but Delhi fell short by 15 runs and at the end, it was the no-ball which made the complete difference between both the teams.
After the match, Pant admitted that sending someone on the field wasn’t right but said it happened in the heat of the moment. He believed the umpires should have used the technology available and called it a no-ball. Ashwin, from Rajasthan Royals, said the break actually helped them calm down, and praised McCoy for staying strong under pressure. Royals captain Sanju Samson also praised the way his team supported the young bowler in the final over. On the incident 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. [When asked if it was okay to send a team management member onto the field to argue the lack of a no ball call] 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.
Jos Buttler deservedly won the Player of the Match award for his third century of the season, pushing him further ahead in the Orange Cap race. His innings was a mix of timing, power, and tactical brilliance, punishing every error in length and line from Delhi’s bowlers. In the end, the match will be remembered not just for Jos Buttler’s century or the six-hitting drama, but for a moment where emotions, rules, and pressure collided on one cricket field.