Can you run if bowled on a free hit?

Free Hit Confusion: You’re Safe, But Not That Safe

Cricket’s free hit, designed to penalize illegal bowling, often causes confusion. While it offers batsmen a golden opportunity to swing for the fences without fear of being bowled, caught, LBW, or stumped, it doesn’t grant complete invincibility. One crucial dismissal method remains very much in play: the run out.

The free hit rule states that the batsman cannot be dismissed by any means except for those related to running between the wickets, handling the ball, hitting the ball twice, or obstructing the field. Essentially, if the dismissal requires the ball to be deemed dead after hitting the wickets, the batsman is safe. However, the ball remains live after hitting the wickets on a free hit, opening the door for a run out.

Imagine this scenario: a searing yorker is bowled on a free hit, the batsman digs it out towards mid-off, and attempts a risky single. A sharp fielder swoops in, gathers the ball, and breaks the stumps before the batsman reaches the crease. Despite the free hit, the batsman is out, run out.

This often-misunderstood aspect of the free hit leads to dramatic moments on the field. Batsmen, emboldened by the relative safety of the free hit, may take greater risks with their running, providing the fielding side a chance to capitalize. A smart fielding team will anticipate this and position themselves accordingly, ready to pounce on any hesitation or misjudgment.

So, while the free hit provides a significant advantage to the batting side, it’s not a free pass. Batsmen still need to exercise caution and smart cricket sense between the wickets. The thrill of the free hit can quickly turn to despair if a run out opportunity is presented to a vigilant fielding team. The free hit is a license to thrill, but not a license to be reckless.