“How Is This Out?”: Twitter Slams Shocking Caught-Behind Decision In BBL


Sydney Sixers registered a six-wicket win over Melbourne Stars in their Big Bash League (BBL) game on Friday. However, there was a controversial moment in the match when an umpiring error cost Sixers’ Jordan Silk his wicket in the final over of the match. With Sixers needing two runs to win off three deliveries, Silk missed a cut shot that went through to the keeper, but James Vince called him for a single. However, the bowler and the wicketkeeper combined to hit the stumps at the non-striker’s end.

While Silk seemed to have fallen short at the non-striker’s end, Stars’ captain Adam Zampa took a review for a caught behind.

Silk was ultimately given out caught behind, despite the replays showing a clear gap between the bat and ball when a spike on ‘snicko’ appeared.

A disappointed Silk protested and asked for a review himself, but he eventually had to walk back to the dugout after he was denied the review.

The decision went down poorly with cricket experts and fans on Twitter. Here are some reactions:

“I definitely heard a noise as it went past my bat and I saw up there that there was a spike on snicko as it was going past (my bat). But then the front-on camera showed I was about that far away from it, so I’m not sure how they’ve come up with that,” Silk was quoted as saying by Fox Sports Australia after the match.

“That’s what I saw on the screen, so that what was I was going off (when I tried to review). But I reckon I was run out at the other end anyway. It’s following me at the moment, controversy. I don’ know, it was a bizarre moment. I went from thinking I was out on the snicko and then I saw a gap on the other camera. It could’ve blown up, no doubt,” he added.

Featured Video Of The Day

Sourav Ganguly Set To Rejoin Delhi Capitals As Director Of Cricket: Report

Topics mentioned in this article

#Twitter #Slams #Shocking #CaughtBehind #Decision #BBL



Please enter your comment!
Please enter your name here