A curious incident during the third grade match between the Western Districts in Canberra, has captured the attention of cricket fans. A bowler bowled the batsman cleanly, with the ball hitting the wicket, but the bails did not fall, nor did any of the stumps uproot completely, on which the umpires declared the batsman not out.
Despite the ball hitting the wicket, the two bails did not fall and not one of the three stumps could be completely uprooted, on which the umpires did not declare out.
Things you don't see every day…
— Cricket ACT (@CricketACT) December 10, 2023
Explain this one from a Ginninderra-Wests game for us, cricket fans – how was this possible?
Physics? Chewing Gum? Swollen timber in all the rain?" 🤔
📷 Wal Murdoch pic.twitter.com/484qFEt1Wj
According to Marylebone Cricket Club (MCC) Law 29.1, a batsman cannot be declared bowled out unless at least one bail has fallen completely from the top of the stumps or at least one or more stumps have been completely uprooted off the ground.
Social media users have expressed mixed reactions to the unique incident. Here are some reactions;
Stumps too close? Meaning bails rammed against each other to get them into the groove? Add some rain related swelling?
— Tim Fountain (@Tim___F) December 10, 2023
Certainly (un)fortunate, depending which side you're on.
1) Bail is dislodged from stump, so out.
— Brad Rodgers (@Bucksbunnys) December 10, 2023
2) Not every instance can be covered by the laws, that’s where the “spirit of cricket” comes in, any fair minded batsman is walking and not putting the umps in a difficult position.
Bails of Steel !!
— Shrinivas (@shrinivassup) December 11, 2023
Single piece bail. Tricky.
— Nation of Dumbarses (@CricketnBeer) December 10, 2023
