A surprising moment happened during the T20 Blast League match between Somerset and Northamptonshire on Thursday, September 5. In this match, an unusual incident took place that left both fans and players puzzled. The umpire called a no-ball, even though the bowler’s foot was clearly inside the line, confusing everyone watching. But the reason for this decision lies in one of cricket’s lesser-known rules.
What Happened in the Match?
During the match, the Northamptonshire bowler delivered a legal ball, and the Somerset batsman appeared to be stumped. However, instead of declaring the batsman out, the umpire signaled a no ball. Fans were left wondering what had gone wrong. The answer lies in a rule related to the wicketkeeper.
The issue was not with the bowler but with the wicketkeeper. Before the ball had reached the batsman, the wicketkeeper’s glove had come in front of the stumps for a moment, even though he caught the ball from behind the stumps. This small error led the umpire to call the delivery a no ball.
How Did It Affect the Game?
This decision had a major impact on the game. The ball that could have resulted in a wicket became a game-changer. After the no ball call, the batsman got a free hit. He took full advantage of it and smashed a six. This turn of events frustrated Northamptonshire’s team and left fans fuming on social media. Many questioned the fairness of the rule and recalled similar incidents from the past.
What is This Rule?
According to the International Cricket Council (ICC) rules, the wicketkeeper must remain behind the stumps until the ball has either passed the wicket or the batsman has touched it with his bat. If the wicketkeeper moves forward or brings any part of his glove in front of the stumps before these conditions are met, the umpire can call a no ball or declare it a dead ball. This rule applies even if the batsman is stumped.
This was exactly what happened in the Somerset-Northamptonshire match. The wicketkeeper’s glove moved in front of the wicket too early, leading to the no ball, much to the dismay of the bowler and fans.
This incident has sparked a lot of discussion online, with many fans calling for a re-evaluation of the rule.
