Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Nov 28, 2015, 01:55 PM (IST)
Edited: Nov 29, 2015, 09:43 AM (IST)
The Decision Review System (DRS) has once again come under scanner as the Australian spinner Nathan Lyon was adjudged not out by the third umpire, even as the Hot Spot technology suggesting he was out.
The incident happened on Day 2 of the historic Day-Night Test between Australia and New Zealand at Adelaide, when Lyon was facing debutant spinner Mitchell Santner shortly after tea. The former attempted to sweep a Santner delivery, which brushed passed the back of his bat and went through to first slip after a slight deflection from his shoulder.
As the New Zealand team started celebrating, the field umpires referred the decision to third umpire Nigel Llong, who viewed the replays again and again, stopping the play for more than five minutes. The Hotspot technology showed a white mark on the back of Lyon’s bat and Lyon started walking off the field, assuming he was set to be given out. He was however held back by the umpires. The replays showed change in the ball’s seam.
Snickometer and Hawkeye were subsequently used, however the replay the Hawkeye technology was used on was in fact being run over the wrong delivery. Eventually, Lyon was ruled not out. The decision fetched boos from a frustrated Adelaide crowd and surprise from captain Brendon McCullum and his side.
Almost immediately, former cricketers like Shane Warne and Matthew Hayden tweeted their frustration at the decision as well as the time consumed. The manner in which the entire episode was been handled has created a controversy and has reignited the debate on the use of technology. Here are few top tweets on the issue:
Hmmm… interesting DRS. I believe that is out, despite being an Aussie supporter. #AUSvNZ
— Lisa Sthalekar (@sthalekar93) November 28, 2015
Daily Ridiculed Shite #DRS what’s your view on DRS #AUSvNZ
— Trent Woodhill (@TrentWoodhill) November 28, 2015
Horrible 5 mins of cricket & a terrible decision by 3rd Umpire Nigel Long, clearly Lyon was out & not to mention the fact Lyon walked off !
— Shane Warne (@ShaneWarne) November 28, 2015
Another example why DRS should be scraped in its current format
— Scott Styris (@scottbstyris) November 28, 2015
3rd ump acted appropriately using process and logic dictated by the icc. good work, crap referral system. boooooooo https://t.co/iIhMJPjbVr
— stu macgill (@scgmacgill) November 28, 2015
What more evidence do you need than batsman walking #WWOS OMG 2 and half minutes the game will never get back https://t.co/TvflNjeQs3
— Matthew Hayden AM (@HaydosTweets) November 28, 2015
Another example of justifying the umpires decision, not getting the decision right. Happens every test https://t.co/e7d6WgAOzI
— Scott Styris (@scottbstyris) November 28, 2015
What is ANYTHING the DRS umpire considered caused the hot spot on the bat of Lyon
— Matthew Hayden AM (@HaydosTweets) November 28, 2015
Do we need more to show that Nathan Lyon actually top edged that.Using technology is one thing,while interpreting ‘IT’ is another. #AusvNZ
— Ashwin Ravichandran (@ashwinravi99) November 28, 2015
How is warner not out at Perth and Williamson out in Brisbane? Protecting umpires is the main job. #everytest https://t.co/uYeDW7rwQM
— Scott Styris (@scottbstyris) November 28, 2015
Now this is why BCCI is not using DRS for their matches we can’t completely trust the system… #AUSvNZ
— Broken Cricket (@BrokenCricket) November 28, 2015
Show me your umpiring license. Now. https://t.co/TMjQCpzSoO
— Jimmy Neesham (@JimmyNeesh) November 28, 2015
TRENDING NOW
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.