close
close

Pakistan batsman Shan Masood is dismissed without a ball but is still not out. Incident explained. Watch

Shan Masood got hit-wicket and run-out on a no-ball© X (Twitter)




Pakistan international Shan Masood, who plays for Yorkshire in the Vitality T20 Blast, was at the centre of the strange incident in which he was not out despite facing a no-ball. It all happened when Masood was batting at 58 in the 15th over, facing Lancashire’s Jack Blatherwick. Masood hit the stumps while attempting to hit the ball on his back foot and walked off the pitch thinking it was out. The Lancashire players also dislodged the bails at the other end of the pitch, causing a run-out.

Masood, however, did not even make any real effort to reach the other end of the pitch, thinking he was already out as his foot had struck the stumps. However, the incident took a dramatic turn when it was revealed that the bowler had bowled a no-ball by over-stepping.

In such a case, Law 31.7 came into play and Masood was declared not out even though he had both a hit-wicket and a run-out on that delivery.

The umpires discussed the situation at length and finally decided to count Masood not out due to run-out displacement under MCC Law of Cricket 31.7 as the batsman had left the wicket due to a misunderstanding. Masood could not be counted out for the hit wicket as it was a no-ball.

Why wasn’t Shan Masood out?

Masood had not noticed the no-ball and had left his field thinking he was out by hit-wicket. Hence, he could not be run out at the other end of the field.

Law 31.7 states: “An umpire shall intervene if he is satisfied that a striker who has not been adjudged to be out has left the wicket in the mistaken belief that he is out. The intervening umpire shall call and signal ‘Dead Ball’ to prevent further action by the fielding side and recall the striker.”

Masood added three more runs to his total, reaching 61 runs before retiring.

Topics covered in this article