Watch: Shan Masood remains not out despite getting hit wicket and run out on the same ball in T20 Blast 2024; Explained - Cricket Winner

Cricket is a game where luck can dramatically alter the course of events, offering players unexpected lifelines. One such remarkable incident occurred during a T20 Blast 2024 match between Yorkshire and Lancashire, where Pakistani cricketer Shan Masood found himself unexpectedly lucky due to a rare combination of luck and cricket regulations.

The Incident: Yorkshire vs Lancashire T20 Blast 2024

The stage was set for an intense match between Yorkshire and Lancashire. During the 15th over, bowled by Lancashire’s Jack Blatherwick, Shan Masood attempted a scoop shot, leading to a series of unexpected events. The crowd and players were on the edge of their seats, unaware that they were about to witness one of the most unusual lifelines in cricket history.

See Also: Watch: Ravindra Jadeja receives ‘Best Fielder’ medal, honors Dravid with a hug

Shan Masood’s attempted scoop shot

As the ball was delivered, Masood went for a scoop shot. Unfortunately, he failed to make proper contact, and the ball brushed past his bat and onto the stumps. The bails fell, and it seemed like Masood was out hit wicket. The initial reactions from the fielders and commentators were clear – Masood was out.

The hit-wicket scenario

The hit wicket scenario created immediate confusion on the field. As Masood turned to see the fallen bails, he believed his innings had come to an end. Meanwhile, Joe Root, who was at the non-striker’s end, seized the opportunity to take a run. The moment was filled with a mix of disbelief and quick thinking.

Shan Masood steps on his stumps off a no ball, Lancashire take the bails off at the other end – but Masood remained not out under law 31.7 pic.twitter.com/yQG6gP6Rac

— Vitality Blast (@VitalityBlast) June 20, 2024

Joe Root’s Role in the Incident

Joe Root’s actions at the non-striker’s end were crucial. Seeing the ball roll away, Root moved to take a run. His quick thinking added to the confusion as Masood, initially unsure of what had happened, attempted to complete the run. Root’s instinctive move played a pivotal role in the unfolding drama.

The Unexpected Run Out Attempt

As Masood tried to complete the run, Jack Blatherwick, quick on his feet, ran to the non-striker’s end and attempted a run out. Masood, still confused, was run out by the bowler. However, the situation was far from straightforward, as the umpire’s decision hinged on a critical detail.

The No Ball Revelation

Amidst the confusion, the umpire signaled a no ball due to overstepping by Blatherwick. This revelation changed everything. According to cricket rules, a no ball invalidates the delivery and any dismissals that occur from it, meaning Masood was not out hit wicket.

Marylebone Cricket Club (MCC) Rule 31.7

The no ball alone didn’t save Masood. MCC rule 31.7, a lesser-known regulation, played a crucial role. This rule states that if a batter leaves the wicket under the misapprehension of being out, the umpire can call and signal a dead ball. This rule is designed to protect batters from being unfairly dismissed in moments of confusion.

The Rule saved Masood

In Masood’s case, the umpire invoked MCC rule 31.7. As Masood played the shot and the bails fell, he assumed he was out. Upon seeing the umpire signal a no ball, he attempted to run. The rule came into play before Masood could be run out, effectively saving him. The umpire called a dead ball, and Masood was allowed to continue his innings.

Law 31.7 Batter leaving the wicket under a misapprehension

An umpire shall intervene if satisfied that a batter, not having been given out, has left the wicket under a misapprehension of being out.  The umpire intervening shall call and signal Dead ball to prevent any further…

— Vitality Blast (@VitalityBlast) June 20, 2024