Former South Africa National Cricket Team player AB de Villiers opened up about Rishabh Pant’s dismissal in the second innings of the third Test against the New Zealand National Cricket Team. He believes that there wasn’t enough proof to overturn the decision and that technology should be used properly.
Rishabh Pant’s dismissal in the second innings of the third Test against the New Zealand National Cricket Team was the major talking point of the day. This was because the keeper-batter was given out controversially and despite no conclusive evidence, the decision was overturned.
Rishabh Pant got out due to a controversial call from the third umpire
Rishabh Pant, who held the key for India, in the chase, came down the track to defend the ball from Ajaz Patel. The keeper-batter didn’t get to the pitch of the ball and the ball popped up off the pad before going into the keeper’s gloves. The umpire didn’t term it out but New Zealand skipper Tom Latham went for the DRS.
The UltraEdge showed a bit of spike when the ball passed the bat but at that time, the bat hit the pad as well. Rishabh Pant, however, didn’t want to leave as he was pretty confident that he hadn’t hit the ball. But the third umpire overturned Richard Illingworth’s call.
Also read: ‘Sack Rohit, Gambhir and retire Kohli’: Furious fans react to India’s shocking ‘Blackwash’ vs NZ
Fact is there must’ve been doubt. Surely you stay with the on-field call – AB de Villiers on Rishabh Pant’s dismissal
With Rishabh Pant at the receiving end of a controversial dismissal, AB de Villiers shared his verdict on the same. He highlighted how the keeper-batter hit the bat on the pad at the same time the ball passed the bat. He feels that the on-field call should’ve stayed when there was a doubt. Taking to his Twitter account, he explained:
“Controversy! Little grey area once again. Did Pant get a bat on that or not? The problem is when the ball passes the bat at the same time a batter hits his pad, snicko will pick up the noise. But how sure are we he hit it? I’ve always worried about this and here it happens at a huge moment in a big Test match. Where’s the hotspot?!
“Fact is there must’ve been doubt. Surely you stay with the on-field call, then? Unless the 3rd Ump clearly saw a deviation? I’m not so sure. And don’t get me wrong, I have no bias here, just pushing for consistent calls and good use of tech.”
Controversy! Little grey area once again. Did Pant get bat on that or not? Problem is when the ball passes the bat at exactly the same time a batter hits his pad snicko will pick up the noise. But how sure are we he hit it? I’ve always worried about this and here it happens at a…
— AB de Villiers (@ABdeVilliers17) November 3, 2024
Fact is there must’ve been doubt. Surely you stay with on-field call then? Unless the 3rd Ump clearly saw a deviation? I’m not so sure.
And don’t get me wrong, I have no bias here, just pushing for consistent calls and good use of tech.
— AB de Villiers (@ABdeVilliers17) November 3, 2024
I don’t think it was conclusive enough to overturn on field not out decision – Wasim Jaffer on Rishabh Pant
Wasim Jaffer also shared his verdict on the same. He feels that there wasn’t conclusive evidence to overturn the decision. He expressed his sympathy with keeper-batter and while taking to his Twitter account, he explained:
“I don’t think it was conclusive enough to overturn on field not out decision. Feel for Rishabh Pant.”
I don’t think it was conclusive enough to overturn on field not out decision. Feel for @RishabhPant17. #INDvNZ pic.twitter.com/ciOZq3V0MI
— Wasim Jaffer (@WasimJaffer14) November 3, 2024
Rishabh Pant’s dismissal completely changed the course of the game for the India National Cricket Team. After he got out, the team lost wickets early and went on to lose the game by the margin of 25 runs. The keeper-batter slammed his second fifty in the game and ended with an inning of 64 runs.
Leave feedback about this