Mankad Dismissal (Run Out at Non-Striker End) Explained

Few moments in cricket generate more moral debate than a Mankad dismissal. A bowler runs in, approaches the crease — and instead of delivering the ball, removes the bails at the non-striker's end, running out the non-striker who has backed up too far. It is entirely legal. It is clearly within the Laws of Cricket. Yet for decades it was treated as an affront to cricket's "spirit."

That debate has now largely been resolved. In 2022, the MCC made a historic change to the Laws: what was formerly known as "Mankading" — and was buried in the obstructing the field section — was reclassified as a legitimate run out under Law 38.3. The moral stigma that surrounded the dismissal was officially, if not entirely, lifted.

This guide explains the Mankad dismissal completely — what it is, why it is named after an Indian player, what the Laws actually say, how the 2022 change affected cricket's culture, and when it represents smart strategy versus poor sportsmanship.

---

What is the Mankad Dismissal?

The Mankad dismissal occurs when a bowler, in their delivery stride, removes the bails at the non-striker's end with the ball before the non-striker's bat or body has grounded behind the popping crease. The non-striker — the batsman at the bowler's end — is out run out.

The mechanism: when a bowler runs in to bowl, the non-striker typically starts to walk forward, anticipating the ball being released and wanting to gain ground for a potential run. If the non-striker "backs up" — moves their bat and feet forward, past the popping crease — before the bowler releases the ball, they are technically out of their ground. A bowler who notices this and removes the bails (by breaking the wicket with the ball in hand) before completing the delivery has legally run out the non-striker.

The dismissal is distinct from a standard run-out in two ways: first, the ball has not yet been delivered; second, it is the bowler — not a fielder — who effects the dismissal. In every other respect, it is treated identically to a run out in the scorecard and in the Laws.

---

Origin of the Name

The dismissal is named after Vinoo Mankad, one of India's greatest early cricketers — a classical all-rounder who bowled left-arm spin and batted in the top order with distinction across the 1940s and 1950s.

In December 1947, Mankad was playing for India against an Australian tour match. He ran out Australian batsman Bill Brown at the non-striker's end without delivering the ball — not once, but twice across two matches. The first time, in a tour match, Mankad had warned Brown about backing up too far before running him out; Brown reportedly ignored the warning. In the Test match that followed, Mankad did it again without warning.

The Australian public and press were outraged. Don Bradman, characteristically, took a different view — he reportedly said the blame lay entirely with Brown for backing up too far after having been warned. Nevertheless, the dismissal became known as "Mankading" with a pejorative undertone in English cricket discourse, particularly in Australia and England, for the next seven decades.

The irony is that Vinoo Mankad was a colossus of early Indian cricket — he took 162 Test wickets and scored over 2,000 Test runs — yet his primary legacy in many casual fan discussions has been attached to this one dismissal that he did not invent and that is entirely legal.

---

What the Laws Say (Law 38.3)

Following the October 2022 revision, the non-striker run-out is addressed in Law 38.3 of the Laws of Cricket, under the general heading of "Run Out."

Law 38.3 states: the non-striker is out run out if, at any time while the ball is in play, they are out of their ground and their wicket is put down by the bowler before they have completed their delivery stride.

The critical elements:

"At any time while the ball is in play" — this includes the bowler's entire delivery stride, from when they begin their run-up to when they release the ball. If the non-striker is out of their ground (bat and feet beyond the popping crease) at any point during this process, and the bowler chooses to break the wicket, the non-striker is out.

"Before they have completed their delivery stride" — this is the line that distinguishes a Mankad run-out from a standard run-out. Once the bowler has completed their delivery stride (released the ball), any run-out at the non-striker's end becomes a normal run-out effected by a fielder (or the wicketkeeper receiving the ball). The Mankad specifically refers to the bowler's action before ball release.

No warning required: Since the 2022 revision, the Laws do not require a bowler to warn the non-striker before effecting a Mankad. Previous playing conditions in some formats included a "spirit of cricket" advisory suggesting warnings, but these were guidelines, not Laws. Under current Laws, a bowler can run out the non-striker without any warning, and the dismissal is fully legal.

---

Why Was It Reclassified as Run Out in 2022?

Before the October 2022 revision, the non-striker backing-up dismissal was technically housed in the "Unfair Play" section of the Laws — Law 41.16. This placement implied the dismissal was somehow unsporting, even if legal. The MCC's decision to move it squarely into the Run Out laws (Law 38) was deliberate and carried a clear message: this is not unfair play. It is cricket.

The MCC's stated reasoning: the non-striker gains an unfair advantage by backing up early. By leaving their ground before the ball is released, they shorten the distance needed to complete a run, giving the batting team an unfair head start. The bowler is entitled to prevent this by running out the non-striker. There is nothing unsporting about enforcing a rule that exists to prevent the batting team from gaining an unfair advantage.

The reclassification was welcomed by those who had long argued that calling the dismissal "unfair play" was itself unfair — it stigmatised a bowler for enforcing a legitimate Law of Cricket. Critics of the change argued that removing the "unfair play" classification would make the dismissal more common and more contentious, and that the spirit of cricket counselled warning the non-striker first.

---

Is Mankad Considered Unsporting?

This is the central question, and the answer in 2026 is: no, not by the Laws, and increasingly not by mainstream cricket opinion — though strong pockets of dissent remain.

The "spirit of cricket" preamble to the Laws of Cricket notes that cricket is a game that owes much to those who observe the spirit of the game as well as its Laws. Critics of Mankad have historically cited this preamble, arguing that running out a non-striker without warning violates the spirit even if it is technically legal.

The counterargument — which has gained significant ground since 2022 — is that the non-striker who backs up early is themselves violating the spirit of the game. They are gaining a physical advantage by leaving their ground before the ball is bowled. A bowler who runs them out is merely enforcing a Law designed to prevent that precise advantage. The moral logic of warning a non-striker before enforcing a rule against their cheating is, at minimum, questionable.

In 2026, the cricket community is broadly split as follows: ICC, MCC, and most governing bodies take the position that a Mankad is legitimate and does not require a warning. Many older players and commentators, particularly in England and Australia, still feel a warning should precede the first Mankad attempt. Most younger players, analysts, and T20-era fans treat it as straightforwardly legal and strategically sensible.

---

Famous Mankad Incidents

Vinoo Mankad vs Bill Brown, 1947: The original. Two dismissals across tour match and Test that named the dismissal forever. Mankad had warned Brown the first time; the second time he did not. Both times, entirely legal.

Ravichandran Ashwin vs Jos Buttler, IPL 2019 (Rajasthan Royals vs Kings XI Punjab): Ashwin, captaining Kings XI Punjab, ran out Buttler at the non-striker's end in a league match. Buttler was well out of his crease. The dismissal was entirely legal. The post-match reaction was a storm — pundits and former players from England were vocal in their criticism of Ashwin, while Indian cricket largely supported the decision. Ashwin was unapologetic and remains so.

Deepti Sharma vs Charlotte Dean, 2022 (England vs India Women, Lord's): This is the most significant Mankad incident in recent history, and the one that most directly preceded the MCC's reclassification. In the third and deciding ODI of the India Women vs England Women series, India needed a win. England were chasing and needed 17 from 17 balls with the final wicket pair together. Non-striker Charlotte Dean had been backing up early. Indian spinner Deepti Sharma ran her out without warning.

India won the match. The reaction in England was intense — anger, disappointment, accusations of poor sportsmanship. Dean handled the dismissal with grace in her post-match comments, but several England players and commentators were less measured. Deepti Sharma, for her part, was calm and unapologetic — she pointed out that Dean had been warned during the innings to stay in her ground, and that the dismissal was legal.

The incident accelerated the MCC's review of the Laws and directly contributed to the reclassification of the dismissal as run out (rather than unfair play) just two months later, in October 2022. In many ways, Deepti Sharma vs Charlotte Dean at Lord's was the moment that finally settled the moral question: the Laws agreed with Deepti.

Ravi Ashwin continued advocacy: Post-2022, Ashwin has been cricket's most prominent public advocate for treating Mankad as routine. He argues that non-strikers who back up early are breaking the rules, and that bowlers who enforce them are playing correctly. His consistency on this point has shifted public discourse, particularly in India.

---

ICC Position on Mankad

The ICC's position in 2026 is clear: the run-out at the non-striker's end is a legitimate dismissal. The reclassification from "unfair play" to "run out" in the Laws was consistent with the ICC's playing conditions, and those conditions do not require a warning before the dismissal is attempted.

The ICC has not issued guidance recommending warnings as a matter of best practice since the 2022 revision. Individual tournament or series playing conditions may include their own guidance, but at the international level, the dismissal is treated identically to any other run-out.

Match officials do not intervene to prevent a Mankad. The bowler is entitled to attempt the dismissal, and if the non-striker is out of their ground, they are out. The on-field umpire's role is simply to confirm whether the non-striker was in or out of their ground at the moment the wicket was broken.

---

When is Mankad Legitimate Strategy?

Given the legal clarity, when should a bowling side consider a Mankad?

When a non-striker is consistently backing up early: A non-striker who leaves their crease early on multiple deliveries in an innings is gaining a cumulative advantage across dozens of runs. If the batting team is close in a run chase and every half-metre of backing up translates to saved runs across 50 or 60 deliveries, the advantage is meaningful. The bowling team is entitled to remove that advantage.

When the match situation is tight: A run-out in the final stages of a close match — particularly in limited-overs cricket where every run matters — is obviously more valuable than a run-out with 40 overs remaining and 200 runs to get. The tactical value of a Mankad is highest in close, low-scoring finishes.

As a deterrent: In some cases, simply noticing the non-striker's habit and making them aware the fielding team has noticed it can be enough to stop the backing-up. The bowler does not need to actually attempt the dismissal — they can glance pointedly at the non-striker's position to communicate awareness. This deterrent effect may be as valuable as the actual dismissal.

When the bowler is confident of the crease position: A Mankad attempt that fails — because the non-striker was actually behind the crease — interrupts the bowler's action and concedes the ball. Bowlers should only attempt a Mankad when they are confident the non-striker is genuinely out of their ground.

---

Quick Reference Table

Rule	Detail
Governing Law	Law 38.3 (Run Out)
Named after	Vinoo Mankad (India)
Original incident	1947 — Mankad ran out Bill Brown (Australia)
Pre-2022 classification	Law 41.16 — Unfair Play
Post-2022 classification	Law 38.3 — Run Out
Warning required?	No — not required under current Laws
Who effects the dismissal	The bowler, before completing their delivery stride
Non-striker condition	Must be out of their ground (bat and body past popping crease)
Deepti Sharma incident	September 2022 — England Women vs India Women, Lord's
ICC position (2026)	Fully legitimate run out; no warning required
Scoring	Recorded as run out (non-striker) in scorecard
DRS applicable?	Yes — on-field umpire can refer to TV umpire if there is doubt about whether the non-striker was in their ground

---

Frequently Asked Questions

Does the bowler have to break the stumps with the ball or can they knock the bails off? The wicket can be broken in any of the ways specified in the Laws — the bowler can pull up and remove the bails with their hand while holding the ball, or they can break the wicket with the ball itself. The ball must be live and in the bowler's hand at the moment the wicket is broken.

Can a Mankad be reviewed via DRS? Yes. If the on-field umpire is uncertain whether the non-striker was in or out of their ground at the moment the wicket was broken, they can refer the decision to the TV umpire, who has access to camera angles showing the non-striker's crease position. The TV umpire will check whether the bat or any part of the batsman's body was grounded behind the popping crease.

What if the non-striker dives back and makes their ground just as the bowler breaks the wicket? If the non-striker regains their ground (grounds their bat or body behind the popping crease) before the bowler breaks the wicket, they are not out. The bowler's action must result in the wicket being broken while the non-striker is still outside the crease. A very close call here would go to the TV umpire for review.

Is there any format where Mankad is still treated as unfair play or requires a warning? Some domestic competitions and junior cricket organisations still have playing conditions that require a warning before a Mankad attempt. However, at the international level and in major franchise tournaments including the IPL, no warning is required and the dismissal is treated identically to any other run-out.

Has a Mankad ever been withdrawn — that is, the bowling team offered the batsman back after effecting the dismissal? Yes, historically. Several instances exist where fielding teams "withdrew" the Mankad appeal as a gesture of goodwill, allowing the dismissed non-striker to continue batting. This was more common before the 2022 reclassification when the dismissal carried stronger moral stigma. In modern cricket, withdrawing the appeal after a legal Mankad is rare, though not unprecedented — it remains at the fielding captain's discretion.

---

The Mankad dismissal is now exactly what the Laws say it is: a run out. Not unfair play, not a breach of the spirit of the game, not something requiring a warning — a legitimate way to dismiss a non-striker who leaves their ground early. Deepti Sharma vs Charlotte Dean at Lord's in 2022 was the moment that crystallised the debate, and the MCC's subsequent revision of the Laws confirmed what had always been true: the batsman out of their ground is the one who violated the rules first. For more cricket rules explained clearly, explore the full series, and read our detailed guide on DRS and technology in cricket.