|
Post by tons4fun on May 28, 2012 14:37:20 GMT
A fast bowler normally off a long run up (15 paces at least) picked up a ball off his own bowling, walked back towards his bowling mark, turned early and bowled off 3 paces.
All ok so far, BUT batsmen wasn't ready. I called dead ball as bowler was in delivery stride to try to prevent ball being bowled and unprepared bat from possibly being injured.
Batsmen only slightly aware of what was happening and took stride from square back to crease and cross batted ball in defence, clearly unprepared.
Bowler very unhappy with me. I asked the bat to ensure he was ready to recieve all future balls. No effect on game other than unhappy bowler for next two balls. Bowler did have a minor tirade but apologised prior to his next over - no problem and no action.
How should this have been handled?
|
|
|
Post by Reggie Duff on May 28, 2012 23:14:04 GMT
I usually stand with my arm extended until the batsman is ready. If he is regularly not ready I remind him that he should be ready when the bowler turns. When Jason Arnburger bowls off 2 paces though, he intentionally tries to rush the batsman, so on the occasions I've stood at his end I would actually stand in his way until the batsman was ready. For your situation though, the laws actually state Law 23.4(b) Either umpire shall call and signal Dead ball when ...(v) 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. In the case you mention, according to the laws you did the right thing - by calling dead ball before it was delivered, you didn't need to worry about whether a shot was played or not. Had you called it after delivery, then you would have been wrong because the batsman brought himself into it by playing the ball. Had he left it and say it bowled him, you could then have called dead ball.
|
|