Latest previewNew Zealand v India · 3rd ODI · 10 Nov 2026Read the preview
History

From Unfair Play to Run Out: How Cricket Rewrote the Law on the Non-Striker Leaving Early

Vinoo Mankad's run-out of Bill Brown on India's 1947-48 tour of Australia gave the dismissal a name. It took until 2022 for the Laws to treat it as a plain run-out, and until 2023 to say exactly when the bowler's chance ends.

By Jozaf · 18 Nov 2026 · 5 min read

Few dismissals in cricket start as many arguments as the run-out at the non-striker's end. The bowler stops in the delivery stride, the batter at the bowler's end has already set off, and the bails come off. For most of its history this way of getting out sat in the part of the Laws headed Unfair Play. Since 1 October 2022 it has been part of the ordinary run-out Law, and since 19 January 2023 the Law has said exactly when the bowler's chance ends. This piece traces how it got there, from Sydney in the 1947-48 season to the Big Bash League in January 2023.

Sydney, 1947-48: the dismissal gets a name

India toured Australia in 1947-48, and their all-rounder Vinoo Mankad twice ran out Australia’s Bill Brown for backing up too far. The first time was in a tour match against an Australian XI, and Mankad warned Brown before doing it. The second was in the second Test of the tour, at the Sydney Cricket Ground. Brown was backing up and had left his ground; Mankad stopped in his delivery stride, kept the ball and broke the wicket at his own end.

The Australian press reacted angrily and accused Mankad of poor sportsmanship. Don Bradman took the other side. In his autobiography he defended Mankad, arguing that a non-striker who backs up too far or too early is the one gaining an unfair advantage. The name stuck anyway: a batter dismissed this way came to be described as having been "Mankaded", and the word has followed the dismissal ever since.

The courtesy of the warning

For decades the dismissal was governed less by the Laws than by an unwritten custom: a bowler was expected to warn a batter who kept leaving early before actually running them out. The most famous act of restraint came in a group match of the 1987 World Cup between Pakistan and West Indies. Pakistan needed two runs from the last ball, and the non-striker, Saleem Jaffar, was out of his ground as Courtney Walsh came in to bowl. Walsh stopped and did not run him out. Pakistan went on to win, and West Indies did not reach the semi-finals. Walsh was widely praised for his sportsmanship.

The custom has never been part of the Law. A bowler may warn a non-striker, but neither the Laws nor guidance from the Marylebone Cricket Club (MCC), which writes them, requires it.

Jaipur, 2019: the timing question

The argument moved to the Indian Premier League on 25 March 2019. In Jaipur, Kings XI Punjab made 184 for four, and Rajasthan Royals were chasing 185 when Ravichandran Ashwin, Kings XI's captain, ran out Jos Buttler at the non-striker's end. Buttler had made 69 from 43 balls. The third umpire gave him out, Rajasthan's chase fell away, and Kings XI won by 14 runs. It was not Buttler's first dismissal of this kind: Sri Lanka's Sachithra Senanayake had run him out the same way in a 2014 one-day international.

Ashwin said the act was "very instinctive" and within the rules. Rajasthan's mentor Shane Warne was among many who criticised it. The MCC's own response turned on timing rather than on the dismissal itself. The Law at the time allowed the run-out only up to "the instant when the bowler would normally have been expected to release the ball", and the question was whether Ashwin had paused beyond that instant. The MCC called the dismissal legitimate but said it was not in the spirit of the game because of that timing. The incident showed that the problem was not just whether the dismissal was fair, but where exactly the line fell.

2022: out of Unfair Play

In March 2022 the MCC announced a new edition of the Laws. Among the changes, the clause on running out the non-striker, until then Law 41.16 under Unfair Play, was moved into Law 38, Run Out. The wording itself stayed the same. The same Code also permanently banned the use of saliva to shine the ball. The new Code took effect on 1 October 2022, and the International Cricket Council (ICC) brought its playing conditions for international matches into line from the start of that month.

Before that date arrived, the dismissal produced its most watched case. On 24 September 2022, at Lord’s, India played England in the third women’s one-day international, the last international match of Jhulan Goswami, who had made her India debut in 2002. England were nine wickets down and needed 17 more to win when Deepti Sharma, in her delivery stride, ran out the non-striker Charlie Dean. That was the last wicket. India won by 16 runs and took the series 3-0.

The MCC responded that the match had been properly officiated and should not be considered as anything more. Its advice to non-strikers was simple: remain in their ground until they have seen the ball leave the bowler’s hand. The dismissal took place a week before the Law moved out of the Unfair Play section, which gave the debate an odd timing: a decision that was about to stop being filed under unfair play was argued over in exactly those terms.

Melbourne, 2023: fixing the moment

The last gap in the Law was the one that had surfaced in 2019: what does “normally have been expected to release the ball” mean in practice? It came up again in a Big Bash League match between Melbourne Stars and Melbourne Renegades in January 2023. Adam Zampa, bowling for the Stars, broke the wicket at the bowler’s end with the Renegades’ Tom Rogers out of his ground. The TV umpire, Shawn Craig, gave Rogers not out, because Zampa’s bowling arm had already passed the point at which he would normally have released the ball. The MCC said the umpires had been correct.

On 19 January 2023 the MCC changed the wording with immediate effect. The Law now defines the expected moment of release as the moment the bowler’s arm reaches the highest point of their normal bowling action. Once the bowler has reached that point, the non-striker can no longer be run out in this way, even if they have already left their ground. The Zampa decision did not change; what changed was that the reasoning behind it was written into the Law instead of left to interpretation.

What the rewrites settled, and what they did not

Taken together, the changes of 2022 and 2023 answer the two questions that kept the dismissal controversial. First, is it fair? The Laws now say plainly that it is a run-out, nothing more. Second, when is it allowed? From the moment the ball comes into play until the bowler’s arm reaches the top of the normal action, and not after.

What the Laws have not settled, and arguably cannot, is the custom. Nothing obliges a bowler to warn a batter. Our reading is that the wording now leaves less room for argument over the dismissal itself, and moves the argument to whether a warning was given. The simplest protection remains the one the MCC keeps repeating: a non-striker who stays in the crease until the ball has left the bowler’s hand cannot be run out this way.

Laws of CricketMCCVinoo MankadBill BrownRavichandran AshwinJos ButtlerDeepti SharmaCharlie DeanAdam ZampaCourtney Walsh

Frequently asked questions

Is running out the non-striker before the ball is bowled legal?

Yes. Under Law 38 (Run Out) a non-striker who is out of their ground can be run out from the moment the ball comes into play until the bowler's arm reaches the highest point of the normal bowling action.

Does the bowler have to warn the batter first?

No. A bowler may give a warning, and some do by custom, but neither the Laws nor MCC guidance require one.

Why was Adam Zampa's attempt in January 2023 given not out?

His bowling arm had already passed the point at which he would normally have released the ball, so the window for the run-out had closed. The MCC said the umpires were correct and then clarified the wording of the Law on 19 January 2023.

Share

More History posts

All History posts
History The 1983 World Cup Final: How India Shocked the Champions at Lord’s

How Kapil Dev's India defended 183 against the mighty West Indies at Lord's in 1983, and how that win changed cricket in India for ever.

7 min read
History The Tied Test of Brisbane: A Match Played in the Right Spirit

The first tied Test, Australia v West Indies at the Gabba in 1960: a final-over thriller and a contest that helped redefine how cricket should be…

7 min read
History Headingley 1981: The Test That Made Botham’s Ashes

England followed on 227 behind, then won by 18 runs. How Botham, Dilley and Willis turned Headingley 1981 into the most famous comeback in Ashes history.

7 min read

Related guides

All guides
Laws Mankad Run-Outs and the Laws of Cricket

What a Mankad run-out is, where the name comes from, how the Laws treat running out the non-striker, and why the change in 2022…

Laws The Final Over of the Day Explained: The Rule Change in the 2026 Laws

Since 1 October 2026, a wicket in the last over of a day's play in multi-day cricket no longer ends the day early. The…

Laws Overthrows and Misfields Explained: The Definitions in the 2026 Laws

The 2026 edition of the Laws gives cricket a formal definition of an overthrow and separates it from a misfield. Here is what each…