Why Was Yashasvi Jaiswal Controversially Declared Out Despite No Spike In Ultra-Edge?

Jaiswal was given out despite no spike [Source: @gavaskar_theman/X]

India's swashbuckling opener Yashasvi Jaiswal witnessed an unfortunate end to his fighting innings, as he was controversially declared caught behind despite no spike in the ultra-edge. Jaiswal batted exceptionally in the second innings, slamming a valiant fifty and keeping India's hopes for a draw alive during his stay. 

However, the southpaw was eventually dismissed by Pat Cummins, who got rid of him through a sharp bumper. From over the wicket, Cummins bowler a short ball around the right shoulder of Jaiswal, who failed to nail the hook shot over the leg side field. 

However, as soon as Australian wicketkeeper Alex Carey caught the ball, the hosts appealed for a caught behind, with the on-field umpire Joel Wilson deciding in Jaiswal's favour. Nevertheless, the TV umpire overturned the on-field decision and declared Jaiswal out despite no spike in the ultra-edge. This event sparked controversy, leading to Jaiswal's heated argument with the on-field umpires. 

Was Yashasvi Jaiswal Actually Out In MCG Test?

Although the ultra-edge technology didn't detect any spike, the TV umpire found a clear deflection when the ball passed through Yashasvi Jaiswal's bat. The deflection was sufficient enough for him to overturn the on-field call. The ball suddenly changed its direction after travelling past his bat, convincing the third umpire to decide in the bowling team's favour. 

It's worth mentioning that the ultra-edge technology is not foolproof, so the TV umpire has the right to reverse the on-field decision if the replay visual is sufficient enough to convince him. As there was a clear deflection off Jaiswal's bat, the third umpire found it reasonable to ignore the ultra-edge and declare him out. 

---

ALSO READ

'Jaldi...'- Pant Leaks India's Game Plan To Jaiswal After Kohli, Rohit And KL Fail At MCG

---