England cricketers vent frustration over Hales’ dismissal

Opening batsman was furious when he was given out to Yasir's low catch off Amir’s delivery


Sports Desk August 12, 2016
Alex Hales (L) and Alastair Cook await a decision by the third umpire at The Oval in London on August 11, 2016. PHOTO: AFP

England duo Alex Hales and Stuart Broad took to Twitter to express their frustration over a controversial catch in their fourth Test’s day one against Pakistan..

Opening batsman Hales was furious when he was given out to a low catch off Mohammad Amir’s delivery early on in England’s first innings. Yasir Shah had claimed a diving catch and didn’t hesitate to celebrate, but the batsman stood his ground. He walked off the field only after third umpire Joel Wilson confirmed standing umpire Bruce Oxenford’s initial decision.



Good teams do not make mistakes like dropping catches: Mushtaq Ahmed

However, Broad vented his displeasure on Twitter in a reply English newspaper The Daily Mirror’s cricket correspondent’s tweet.



While replays failed to get a closer view of the catch, Hales also chose to voice his opinion in response to Broad, indicating the ball had touched the ground before Yasir could get his hands on it.

https://twitter.com/AlexHales1/status/763796262365884420

England 328 all out against Pakistan

Even though disciplinary action on cricketers as a result of social media posts is far from uncommon, it remains to be seen whether either player will be reprimanded by the International Cricket Council (ICC). The tweets could be a violation of Article 2.1.3 of the ICC Code of Conduct, which relates to ‘public criticism of the umpire’s performance’.

This article initially appeared on cricket.com.au

COMMENTS (2)

Pakistan | 7 years ago | Reply Sir Ian Botham made an apt comment when this Hale dropped a sitter from his tormenter Yasir Shah. Sir Ian said " this one did carry Hale".
Unknown | 7 years ago | Reply English are crying babies
Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ