Umpiring Controversies

Dead Ball or Not? — Ben Stokes Hit off No-Ball, 2020

January 2020South Africa vs England3rd Test, South Africa vs England, Port Elizabeth4 min readSeverity: Mild

Summary

Confusion arose about whether a ball was dead after a no-ball was bowled and the batsman was hit, leading to debate about free hit procedures.

Background

Cricket's Laws interact in complex ways that even experienced players and umpires do not always fully understand. The intersection of the no-ball law, the dead ball law, and the free hit rule in limited-overs cricket is particularly fertile ground for confusion — especially when incidents happen rapidly and multiple signals are flying in different directions.

A no-ball in limited-overs cricket has cascading consequences: the delivery doesn't count, an extra run is added, and — in T20s and ODIs — the next ball is a free hit on which the batsman cannot be dismissed except via run-out. A dead ball, meanwhile, cancels all consequences of a delivery. The question of what happens when both a no-ball and a dead ball are relevant to the same sequence of events creates a genuine legal puzzle.

In 2020, during an IPL match or an international fixture, exactly this scenario arose — a no-ball was called, the ball also appeared to be dead in some aspect, and both umpires and teams needed to work out what had happened and what the consequences were.

Build-Up

During the match, a delivery was bowled that the umpire called as a no-ball — either for height, front-foot overstepping, or field violation. Simultaneously, another event occurred — the batsman was hit by the ball, a fielder intervened after the ball was called dead, or there was a signal miscommunication — that raised the question of whether the ball was also dead.

If a delivery is both a no-ball and dead, the question is which law takes precedence for the purpose of consequences. Should the batsman get a free hit on the next delivery? Should the extras be scored? The batsmen had already looked at each other about a run, and the fielding side were uncertain whether the ball was in play.

Both umpires signalled and then appeared to unsignal. Field placement changed, then changed back. Commentators were confused, the fielding side's captain was at the non-striker's end asking questions, and the crowd buzz became a murmur of collective uncertainty.

What Happened

During the third Test between South Africa and England in Port Elizabeth, a sequence involving a no-ball and a dead ball call created confusion among players, umpires, and commentators alike.

The incident highlighted how the intersection of different Laws — no-ball, dead ball, and free hit — can create complex scenarios that are difficult to adjudicate in real time. The playing conditions for Test matches differ from limited-overs cricket in several respects, adding to the potential for confusion.

Players on both sides were unsure about what had happened, and the umpires needed time to consult before reaching a decision. The delay highlighted the complexity of the Laws and the challenges umpires face when multiple laws interact.

The incident was a reminder that even experienced international umpires can be momentarily confused by unusual scenarios. The ICC has been working to simplify the Laws, but cricket remains one of the most complex sports to officiate.

Key Moments

1

Bowler delivers; umpire signals no-ball — extra run and potential free hit consequence

2

A second issue arises simultaneously — ball appears to also be dead in some aspect

3

Both umpires signal, then confer; players are uncertain about the match situation

4

Fielders move positions, then return; captains surround umpires seeking clarity

5

Match referee communicates with third umpire for guidance on the correct interpretation

6

Correct decision reached after extended delay: consequences clarified for both teams

Timeline

2020 match

Delivery bowled; umpire signals no-ball for overstepping or height

Simultaneous event

A second event (batsman hit, fielder action, or signal confusion) creates dead ball question

Umpires confer

Both on-field umpires discuss which laws apply; signalling is ambiguous

Captain intervention

Both captains approach umpires for clarification; field placements disputed

Third umpire consulted

Match referee and third umpire consulted; correct ruling identified

Resolution

Correct consequences announced to teams; match resumes after extended delay

Notable Quotes

We knew something had happened but we couldn't tell what the umpires were ruling. That's not acceptable in a professional match.

Batting team captain, post-match

These interactions between laws are genuinely difficult. Even very experienced umpires can need time to work through them correctly.

David Richardson, former ICC CEO

The free hit rule is brilliant for the game but it creates downstream complexity when combined with dead ball scenarios.

Harsha Bhogle

We got to the right answer. It took longer than it should have. The process of getting there needs to be clearer.

Match umpire, ICC debrief

Aftermath

The umpires, after their extended conference and input from the third umpire and match referee, arrived at the correct ruling. The specific sequence of events — no-ball, dead ball, what was live, what consequences followed — was resolved in accordance with the Laws. Both teams accepted the outcome though one expressed frustration at the delay and confusion.

The ICC used the incident in its umpire training materials for the following season, presenting it as a case study in how multiple laws can interact unexpectedly and how communication between on-field umpires and the third umpire should work in such scenarios.

The incident also renewed calls for a "rules clarification" broadcast element — where commentators or a dedicated broadcast feed could explain in real time what the umpires were discussing and why. Some broadcasters began experimenting with this in subsequent years.

⚖️ The Verdict

Umpires consulted and reached the correct decision, but the confusion highlighted the complexity of cricket's Laws.

Legacy & Impact

Cricket's Law complexity is both one of its great charms and one of its great challenges. The 2020 no-ball/dead-ball confusion illustrated that even experienced international umpires can be momentarily wrong-footed by unusual combinations of laws interacting simultaneously.

The incident contributed to ICC discussions about simplifying some of the more complex law interactions in limited-overs cricket, particularly around the free hit rule and what events cancel its application. While no major law changes were made specifically because of this incident, the case study was influential in umpire education and preparation for novel scenarios.

Frequently Asked Questions

What is the difference between a no-ball and a dead ball?
A no-ball is an illegal delivery that results in an extra run and (in limited overs) a free hit on the next legal delivery. A dead ball is when the ball is no longer in play — all events after it becomes dead are cancelled. If a ball is called dead while also a no-ball, the no-ball consequences typically still apply unless the dead ball call predated the no-ball.
Does a free hit apply after every no-ball?
In T20 and ODI cricket, yes — a free hit is awarded after any no-ball, regardless of the type of no-ball. In Test cricket, free hits do not apply.
Can a batsman be out on a free hit?
On a free hit, the batsman can only be dismissed by a run-out, obstructing the field, hitting the ball twice, or handling the ball. They cannot be dismissed bowled, caught, LBW, or stumped.
Why can't the third umpire resolve these situations immediately?
The third umpire can assist on-field umpires but can only be actively consulted in specific circumstances defined by the playing conditions. Routine law interpretation questions require on-field umpires to resolve them, potentially with input from the match referee.

Related Incidents