Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Jan 31, 2016, 07:19 PM (IST)
Edited: Jan 31, 2016, 07:19 PM (IST)
It was probably one of the most thrilling run chase in the history of cricket. At one point it looked difficult for Indian team to chase the total but somehow they managed to do it and pulled off one of the most exciting victory in the series. One thing which went unnoticed was the second ball of the final over bowled by Andrew Tye.
It would have been the big talk of town if India would have lost the match or Yuvraj couldn’t have hit that ball for a six. Prior to that delivery, India needed 13 from last five balls. Tye bowled another length ball on the pads to Yuvraj and he went for a biggie over the fence. But the replay suggested, that it was probably a no ball which was completely ignored by the on-field umpire. As it can be seen in the below picture, the foot of Tye is just over the line.
But still it does not justify whether it was a no ball or not: As fast bowlers tends to slide their foot while releasing the ball. But by having a close look at the video below, especially focusing on the 25th and 26th second, it will give an idea that there was not enough sliding from the bowler while releasing the ball.
Even the former Sri Lankan cricketer Russell Arnold raised this question with his tweet and said, “I am pretty sure that last six by Yuvraj was hit off a no ball.. Front foot !!!”
I am pretty sure that last six by Yuvraj was hit off a no ball.. Front foot !!!
— Russel Arnold (@RusselArnold69) January 31, 2016
But still, looking from one specific angle doesn’t prove that the ball was a no ball neither it denies. Still the big question is why didn’t the on field umpire went to third umpire to check for the same or it was just another human error.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.