Cricket's Most Controversial Umpire Decisions Explained
Cricket's most controversial umpiring decisions — Frank Chester's 1948 Bradman dismissal, the Gatting-Shakoor Rana confrontation (1987), the Ian Botham 'caught behind' in 1981 Headingley, the Headingley 2019 Stokes no-ball that wasn't called, and how DRS changed the landscape of disputed decisions.
Cricket has generated some of sport's most celebrated and disputed umpire decisions — partly because the game has so many forms of dismissal (LBW, caught behind, run out) where marginal outcomes have significant consequences, and partly because cricket's etiquette traditions ('walk' — voluntarily accepting a catch on your own bat before the umpire raises a finger) create a complex relationship between players and officials. The introduction of DRS in 2009 fundamentally changed how controversial decisions are managed — but it also created new controversies (Umpire's Call, technology limitations) that replaced the old ones.
Gatting vs Shakoor Rana (1987): The Test That Stopped
The 1987 England tour of Pakistan produced cricket's most celebrated player-umpire confrontation. In the Second Test at Faisalabad, England's Mike Gatting (captain) and Pakistani umpire Shakoor Rana had a heated on-field argument over a field-placing dispute. Gatting alleged Shakoor Rana had called 'stop' while England bowler Eddie Hemmings was about to bowl and had moved fielders — an allegation that Shakoor disputed. The argument escalated; Shakoor Rana pointed his finger at Gatting; Gatting pointed back. Play was suspended for a full day. Shakoor Rana refused to resume until Gatting issued a written apology; Gatting (under TCCB instruction) issued the apology but the damage to England-Pakistan cricket relations was significant. The tour was completed; England won the match. The incident led to neutral umpires being introduced at Test matches — no longer could a home team provide both umpires.
The 2019 Headingley Stokes No-Ball
During Ben Stokes' celebrated 135* Headingley chase (discussed in a separate article), Australia's Josh Hazlewood bowled a delivery that replays showed was a front-foot no-ball — but which on-field umpire Joel Wilson did not call. At the time, Australia had taken the wicket of Jack Leach off the same delivery — but because no-ball was not called (and DRS cannot be used to check no-ball foot positions in Tests at that time), the delivery stood as a legal wicket attempt. Leach survived only because the ball deflected off Stokes' bat and was missed. The no-ball call, if made, would have given Leach a 'free hit' under the T20 rule — but free hits do not apply in Test cricket. The incident raised questions about whether DRS should extend to checking bowler front-foot positions during real-time play.
How DRS Changed the Controversy Landscape
Before DRS (pre-2009), wrong decisions stood as official results — there was no mechanism for review. Historically significant wrong decisions include Bradman's final dismissal (bowled for a duck vs England, 1948 — he needed 4 runs to average 100; the delivery is generally agreed to have been a genuine chance but not one involving an umpire error specifically). DRS eliminated many categories of wrong decision (particularly LBW where Hawk-Eye clearly shows the ball missing) but created new categories of controversy: 'Umpire's Call' (ball on the edge of the stumps decided by original umpire) remains contested; technology error margins (UltraEdge not detecting fine edges) generate 'Not Out' decisions that replay suggests were genuine edges. The controversy in cricket has not disappeared with DRS — it has changed form.
Frequently asked questions
What was the Gatting vs Shakoor Rana incident?
In the 1987 England tour of Pakistan's Second Test at Faisalabad, England captain Mike Gatting and Pakistani umpire Shakoor Rana had a heated on-field confrontation over a fielding dispute. Shakoor Rana refused to resume play until Gatting issued a written apology. Play was suspended for a full day. The incident led directly to the introduction of neutral umpires at Test matches — ending the practice of both umpires being provided by the host nation.
Can DRS be used to review no-ball calls in Tests?
As of 2024: teams cannot use their DRS reviews to challenge no-ball calls in Tests (wides and no-balls have a separate TV umpire check process for flagrant cases). The umpire at the bowler's end must judge the front-foot line in real time. In limited-overs cricket, there is a third umpire check system for front-foot no-balls on every delivery that has been trialled in some tournaments. The 2019 Headingley no-ball (Josh Hazlewood's delivery that was not called) highlighted the gap in DRS coverage for front-foot no-ball decisions.
What is 'walking' in cricket?
'Walking' in cricket means a batsman voluntarily accepts that they have been legitimately dismissed — typically a caught behind (the ball nicked the edge) — before the on-field umpire raises their finger, walking back to the pavilion without waiting for the decision. It was a common practice in the 1950s-1970s and is associated with 'fair play' and the 'spirit of cricket.' Modern professional cricketers rarely walk, instead waiting for the umpire's decision or using DRS to review. The ethics of walking — whether it should be expected — is periodically debated in cricket culture.