Melbourne: The drama continues to intensify in the Border-Gavaskar Trophy, and it reached a fever high at the MCG in Melbourne on Monday, after Yashasvi Jasiwal’s controversial dismissal against Pat Cummins.
After a disastrous beginning to their innings which left them at 33/3 and later on at 130/6, India, who were chasing 340, relied upon young opener Jaiswal to fight through the last session and guide the team to a possible draw.
With the top order failing to fire, Jaiswal took on the burden of carrying India through to the finish line, as the youngster put up a gritty innings of 84 runs, making a stand against the fiery Australian bowlers.
With the match and a potential series lead on the line, AUS skipper Pat Cummins took it upon himself to get rid of the young opener.
With the fifth delivery of the 70th over of the innings, the pacer set up a pestering bouncer that seemingly got the bottom glove of Jaiswal before rifling through to Alex Carey behind the stumps. But, the umpire wouldn’t budge, prompting AUS to take a review, where things took an unforeseen turn.
The replay showed a clear deflection of the ball off Jaiswal’s bottom glove, yet the contact failed to register on the Snickometer, which showed a flat line as it passed through the opener.
But, due to the visual evidence, the umpires decided to overturn their initial call and dismiss Jaiswal, leading to widespread disapproval from the spectators at the MCG.
The controversial decision, whether justified or not, infuriated Indian Cricket fans online, with countless lashing out at the seemingly-deceiving decision from the umpires.
Other fans, including a contingent of Indian fans themselves, agreed with the visual evidence, reinstating that the wicket should righfully stand.
What this decision does call for is introspection regarding the influence that technology can have on decision-making in the sport, but also regarding the Indian batting order which has failed to support their best player more times than less in times of need throughout the series.
Sorry, there was a YouTube error.







