Shan Masood got a hit wicket and a run out off a no-ball.© X (Twitter)
Pakistan batsman Shan Masood, playing in Yorkshire’s Vitality T20 Blast, was at the centre of a bizarre incident in which he was run out off a no-ball yet remained not out. It all happened when Masood was batting on 58 and facing Lancashire’s Jack Blatherwick in the 15th over. Masood hit the stumps while trying to hit the ball off his backfoot and stepped outside the crease thinking he was out. The Lancashire players also missed a bail on the other side of the pitch, causing a run out.
However, Masood thought he had already been out after hitting the leg stump and didn’t even make a real effort to reach the other end of the pitch, but events took a dramatic turn when it turned out the bowler had overstepped and delivered a no-ball.
In such a case, rule 31.7 would apply and Masood was deemed not out even though he was a hit wicket and a run out on that delivery.
The umpires thoroughly discussed the situation and ultimately decided to adjudgment Masood as a run-out dismissal and not out under MCC Cricket Law 31.7 “Batter leaves wicket due to misunderstanding”. Masood was dismissed on a no-ball and therefore could not be out on a hit wicket.
Why was Shan Masood not out?
Unaware of the no-ball, Masood left the crease thinking he was out on a hit wicket and therefore could not be run out at the other end of the pitch.
According to rule 31.7, “If an umpire is convinced that a batsman who is not out has left the wicket in the mistaken belief that he is out, he must intervene. The intervening umpire must call a dead ball to prevent any further action by the fielding team and recall the batsman.”
Masood added three more runs to take his total to 61 before being dismissed.
Topics mentioned in this article
