The fourth Test of the Border-Gavaskar Trophy series has been filled with intense drama, but one incident stood out above all—the dismissal of Indian batter Yashasvi Jaiswal. The young cricketer’s controversial departure during the final innings at the Melbourne Cricket Ground (MCG) on Day 5 sparked debates, with the decision being questioned by fans and experts alike. Here’s a detailed breakdown of the incident and the reasons behind the controversy.
The Match Context
India was chasing a formidable target of 340 runs in the final innings. Jaiswal, in sublime form throughout the series, had already scored consecutive half-centuries and was pivotal to India’s chances. His partnership with Rishabh Pant appeared to be steering India towards a historic victory. With a century within sight, Jaiswal’s dismissal proved to be a turning point in the game.
The Incident: A Disputed Dismissal
The controversy unfolded during the 71st over of the innings when Pat Cummins bowled a short delivery down the leg side. Jaiswal attempted a pull shot but seemingly gloved the ball to wicketkeeper Alex Carey, who dived forward and claimed the catch just above the ground.
The Australians immediately appealed, but on-field umpire Joel Wilson signaled it not out. However, Cummins opted for a review. Third umpire Sharfuddoula Ibne Shahid Saikat analyzed the replay and observed a visible deflection off the bat. Despite this, Snicko technology showed no spike, a tool often relied upon for confirmation in such instances.
Why Was Jaiswal Given Out?
Unlike typical cases where the absence of a spike on Snicko could lead to a “not out” decision, the third umpire relied on visual evidence. The visible deflection of the ball off the bat was deemed conclusive enough to overturn the on-field decision, and Jaiswal was declared out.
The batter was visibly frustrated and argued with the umpires before reluctantly walking back to the pavilion.
Why Did Snicko Fail to Detect a Spike?
Warren Brennan, the operator of Snicko technology through BBG Sports, explained the absence of a spike despite the clear deflection. Speaking to Code Sports, he clarified:
“That was one of those shots where no significant sound was made, resulting in Snicko only registering ambient noise. I checked with the audio director, and they confirmed there was no detectable sound. In such cases, Hot Spot technology might have provided clarity, but it wasn’t used here.”
Experts Weigh In
Former Test umpire Simon Taufel supported the third umpire’s decision, emphasizing the protocols followed. He explained on Channel 7:
“In my opinion, the decision to declare Jaiswal out was correct. The visible deflection off the bat provided conclusive evidence. When such visual evidence is clear, there’s no need to rely further on other technologies. In this case, Snicko didn’t provide corroborative audio, but the umpire correctly prioritized the deflection seen on replay.”
Conclusion
The dismissal of Yashasvi Jaiswal has ignited discussions about the limitations of technology in cricket and the importance of human judgment. While some questioned the decision, experts and former umpires largely backed the third umpire’s call. Regardless, the incident will likely remain a talking point for cricket fans for years to come, given its impact on the thrilling Test series.
