Shan Masood's No-Ball Mishap: Not-Out Despite Hit-Wicket and Run-Out

Shan Masood's Bizarre Not-Out: A Tale of Misapprehension and No-Balls

Pakistan international batter Shan Masood found himself at the heart of a peculiar incident during a Vitality T20 Blast match between Yorkshire and Lancashire. Masood, batting on 58, became involved in a bizarre sequence of events that resulted in him remaining not-out despite being both hit-wicket and run-out.

The incident unfolded in the 15th over when Masood attempted to play a backfoot shot off Lancashire's Jack Blatherwick. However, he inadvertently hit the stumps with his foot and wandered out of his crease, assuming he was out. The Lancashire players, unaware of the no-ball, dislodged the bails at the other end, attempting to run Masood out.

Masood, unaware of the no-ball, made no attempt to reach the other end, believing he was already out. However, the situation took a dramatic turn when it was discovered that Blatherwick had overstepped, resulting in a no-ball.

In such cases, rule 31.7 of the MCC Laws of Cricket comes into play. This rule states that if a batter leaves the wicket under a misapprehension of being out, the umpire shall intervene and call "Dead ball." The batter is then recalled to the crease.

After extensive discussions, the umpires deemed Masood not-out for the run-out dismissal under Law 31.7. While Masood could not be given out hit-wicket due to the no-ball, he was also not out for the run-out because he had left the crease under the misapprehension of being out.

Masood added three more runs to his total before being dismissed, finishing on 61. The incident highlights the importance of umpires being vigilant and ensuring that the correct decisions are made, even in unusual circumstances.

Tags: #ShanMasood, #Yorkshire, #Lancashire, #VitalityT20Blast, #NoBall