Table of Contents
Day 4 of the Boxing Day Test at the Melbourne Cricket Ground (MCG) between Australia and India was marred by a controversial run-out involving Yashasvi Jaiswal and Virat Kohli. The incident sparked a heated argument between former Indian cricketers Sanjay Manjrekar and Irfan Pathan during the post-day show on Star Sports, with bo🐭th experts presenting contrasting views on the cause of Jaiswal’s run-out.
Sanjay Manjrekar’s perspective on Yashasvi Jaiswal’s unfortunate run-out
The key moment occurred during India’s first innings when Jaiswal and Kohli found themselves in a mix-up. After Jaiswal played a back-of-a-length delivery to mid-on, a crucial misunderstanding saw Kohli turn down the single, leading to Jaiswal sacrificing his wicket at the non-striker’s end. The call became a talking point as both former cricketers offered differing views on who was at fault.
Manjrekar argued that it was Kohli’s error for not responding to Jaiswal’s call, emphasizing that the non꧂-striker, in this case, Kohli, should have acknowledged the single and not lefཧt Jaiswal stranded. Manjrekar insisted that Kohli made a ‘schoolboy error’ by looking at the ball instead of at his partner, which led to Jaiswal sacrificing his wicket.
“Kohli should’ve taken the single. It was Jaiswal running to the danger end. It’s a primary school rule in cricket – the non-striker must always watch his partner and ensure the call is communicated clearly. It was Kohli’s error, plain and simple,” Manjrekar said, adding that Kohli’s perceived guilt over the run-out could have impacted his concentration when he was dismissed later,” Manjrekar said.
Also READ: AU🧸S vs IND: Fans mercilessly roast Virat Kohli after Yashasvi Jaiswal’s unfortunate run-out on Dꦫay 2 of the Melbourne Test
Irfan Pathan’s counter and support for Virat Kohli
However, Pathan offered a contrasting perspective, defending Kohli and arguing that the rapid pace of the ball and the fielder’s position at mid-on played a significant role. He maintained that Kohli’s hesitation to take the run was justified, citing the hard-hit ball from Jaiswal that was always heading toward Pat Cummins.
“Virat wasn’t confident taking that run. The ball was hit hard, and with Cummins’ speed and positioning, he had to think about his own safety as well. It wasn’t just Jaiswal who was at risk – Kohli also could’ve been run out. He was running toward the striker’s end, and that makes the situation risky,” Pathan explained.
Pathan also argued that a non-str🎉iker can exercise the option o♚f refusing a run if they deem it too risky.
“It’s not just about Jaiswal; the striker also has the right to decide if the run is on or not. Kohli had a view of how fast the ball was traveling, and he decided there wasn’t a run. It’s a two-way call,” the former cricketer added.
Heated exchange between Manjrekar and Pathan
The argument between Manjrekar and Pathan grew heated, with both experts speaking over each other at times, prompting Manjrekar to say, “If you don’t want to let me talk, it’s fine,” Manjrekar further criticized Pathan, sarcastically suggesting that Pathan’s approach to understanding run-outs should be ad🦄ded to the coaching manual.
“Irfan, your interpretation of how runs are called should be included in the coaching manual. Maybe a non-striker should also see if there’s a run, even when the ball is behind him!,” Manjrekar quipped.
While, Pathan insisted on the importance of understanding the scenario rather than solely blaming one player. He argued that cricket involves risk assessments and decisi♒ons are not always black and white. On the other hand, Manjrekar continued to stress 🔜the role of the non-striker in run-out situations, citing Jaiswal’s attempt to reach the non-striker’s end, which left him vulnerable.
Here’s the video:
Kalesh between Irfan and Sanjay Manjrekar 😭
— Pallavi Anand (@PallaviSAnand)
Lafda between Irfan and Sanjay Manjrekar 😭
— Pushkar (@Musafirr_hu_yar)
