back icon

News

Why didn't Josh Inglis walk despite being bowled by Mark Watt?

article_imageEXPLAINER
Last updated on 04 Sep 2024 | 04:22 PM
Google News IconFollow Us
Why didn't Josh Inglis walk despite being bowled by Mark Watt?

The Australia wicketkeeper-batter eventually remained unbeaten on 27 off just 13 deliveries

An interesting incident took place during the first T20 International (T20I) between Scotland and Australia in Edinburgh on September 4 (Wednesday). Scotland spinner Mark Watt bowled to Australia's Josh Inglis and knocked over the bails. But Inglis held his ground and did not walk back to the pavilion. It was not a no-ball, either. 

However, the umpire signalled dead ball as Inglis had pulled out. By the time Inglis took strike and looked up, the ball was already out of Watt's hands, and he immediately pulled out, saying he was not ready.

Is that really allowed?

Yes, the batter has every right to do that. In fact, Watt bowled 25 yards out and released the ball from well behind the umpire, as he has done on many occasions. 

Here, Alex Hales fell victim to such a delivery:

According to the MCC laws section 20.4, an umpire can signal a dead ball when "the striker is not ready for the delivery of the ball and, if the ball is delivered, makes no attempt to play it. Provided the umpire is satisfied that the striker had adequate reason for not being ready, the ball shall not count as one of the over."

According to the laws laid out, it is clear that Inglis was well within his right to pull out of facing the ball. Even in the recently concluded T20 World Cup 2024, Khalid Kail of Oman pulled out on a couple of occasions while facing Watt. 

The incident forced the bowler, Scotland captain and the umpire to come together for a chat. However, on every occasion, the umpire declared it a dead ball, which was once again the right call.

If you’ve not downloaded the Cricket.com app yet, you’re missing out — big time. Play Fantasy on Cricket.com NOW! Download the App here.

Related Article

Loader