Mankad Dismissal

The Mankad dismissal is named after Indian cricketer Vinoo Mankad, but it actually predates him by over a century — Thomas Barker first recorded it in 1835. It's a run-out where the bowler dismisses a non-striker who leaves their crease too early. Cricket's governing body reclassified it in 2022, removing its "unfair play" label entirely. There's plenty more to this controversial dismissal that'll change how you see the game.

Key Takeaways

• The Mankad dismissal predates Vinoo Mankad by over a century, first recorded in 1835 when Thomas Barker dismissed George Baigent of Sussex.
• It was renamed after Indian cricketer Vinoo Mankad following his 1947 dismissal of Australian Bill Brown, which generated widespread negative media coverage.
• In 2022, the dismissal was reclassified from Law 41 (unfair play) to Law 38, officially recognizing it as a standard run-out.
• Don Bradman defended Mankad's actions as entirely within the rules, contradicting the widespread narrative that the dismissal was unsportsmanlike.
• Non-strikers can depart their crease early up to 72 times per innings, highlighting a frequently exploited yet overlooked batting advantage.

Where Did the Mankad Dismissal Actually Come From?

The Mankad dismissal didn't actually originate with Vinoo Mankad. The first recorded first-class cricket instance dates back to 1835, when Thomas Barker dismissed George Baigent of Sussex at the non-striker's end. That's over a century before Mankad's name became attached to the dismissal.

To understand the historical context, you need to recognize that Mankad's 1947 dismissal of Bill Brown during Australia's tour simply grabbed headlines at the right moment. The cultural significance of the incident grew because it occurred during India's first post-independence series, making Mankad a prominent figure. The press coined "Mankading," unfairly portraying him negatively despite the act being completely legal. Fundamentally, timing and media coverage cemented Mankad's name to a practice that existed long before him. Some historians argue this negative portrayal reflects how colonial mentality shaped English cricket's perception of the dismissal as unsportsmanlike.

Interestingly, Australian captain Don Bradman defended Mankad's actions as completely within the rules, even as some newspapers were quick to label the dismissal unsporting. In 2022, the MCC reinforced the legitimacy of the Mankad dismissal by moving it from Law 41 on unfair play to Law 38, categorizing it as a standard run-out rather than an act of misconduct.

How Does the Mankad Dismissal Actually Work?

Understanding how the Mankad dismissal actually works starts with its legal foundation: a non-striker is out of their ground from the moment the ball comes into play until the bowler would normally release it. The legality of execution process is straightforward — if you're the non-striker and you leave your crease early, the bowler can stop mid-action and remove the bails. You're dismissed if you're out of your ground at that moment, and the TV umpire confirms it.

The controversy surrounding time window stems from bowlers deliberately faking their delivery stride to expose early movement. Since 2022, MCC reclassified this as a run out under Law 38, removing any prior warning requirement and eliminating debate about its legitimacy. The simplest way for a non-striker to avoid this dismissal is to stay in the crease until the moment the bowler would normally be expected to release the ball.

The dismissal is named after former India player Vinoo Mankad, who became associated with this method of running out a non-striker leaving their crease early.

When Did Cricket Finally Make the Mankad Legal?

Although cricket's laws long permitted the Mankad dismissal, it carried an uncomfortable stigma — sitting under Law 41 as a form of unfair play. That changed on October 1, 2022, when the MCC relocated the rule to Law 38, classifying it as a standard run-out.

This reclassification wasn't just administrative. It marked a genuine shift in cultural attitudes toward a dismissal that had divided fans, players, and officials for decades. By removing the "unfair play" label, the MCC validated what many already argued — that non-strikers bear responsibility for staying in their crease.

You'll now notice the rise of tactical usage, particularly in T20 cricket, where every run counts. Coaches actively teach non-striker awareness, and official boards recognize the dismissal as fully legitimate. Ravichandran Ashwin has been one of the most prominent voices emphasizing that the dismissal places responsibility squarely on the batsman at the non-striker's end.

The dismissal has not been without controversy, as Jos Buttler was run out by Ashwin in an IPL match, reigniting fierce debate about where the line sits between playing within the laws and upholding the spirit of cricket.

Which Mankad Incidents Caused the Most Controversy?

Few dismissals in cricket history have sparked as much debate as the Mankad, and five incidents stand out for the controversy they generated. The 1947-48 Bill Brown incident saw Australian media label the dismissal unfair, though Mankad had warned Brown beforehand. The media eventually pushed to rename it "Browned" rather than "Mankaded." Notably, Bradman defended Mankad's actions, citing the laws of cricket as justification for the dismissal.

The 2012 Ravichandran Ashwin-Lahiru Thirimanne dispute exposed a captain disagreement, as Jayawardene denied Thirimanne had received any warning. In 2023, Shami dismissed Shanaka at 98 runs before Rohit withdrew the appeal. Walsh famously refused to mankad Jaffar in the 1987 World Cup, costing West Indies a semi-final spot.

The earliest recorded instance of this dismissal dates back to 1835, when Thomas Barker dismissed George Baigent of Sussex in a first-class cricket match, making it one of the oldest forms of controversial dismissal in the sport's history.

Most recently, the 2025 IPL Rathi controversy hinged on whether his delivery stride was technically complete.

Why Does the Mankad Keep Catching Non-Strikers Off Guard?

The Mankad keeps catching non-strikers off guard for 5 core reasons, and most stem from a fundamental misunderstanding of where the law's onus actually lies. You assume warnings are mandatory, but bowlers aren't obligated to issue any.

You treat early crease departure as a strategic opportunity rather than a rule violation, especially in T20s and ODIs where gaining that head start enormously boosts scoring potential. You expect spirit-of-the-game protection to override written law, but the MCC confirms responsibility falls entirely on you to stay grounded until the ball leaves the bowler's hand.

That responsibility neglect — sometimes reaching 72 early departures in a single innings — goes unchecked until a critical moment exposes it. The dismissal isn't a surprise; it's the consequence of ignoring a clear, enforceable rule.

When a Mankad dismissal does occur, it often sparks fierce debate beyond the boundary, with captains publicly contesting the legitimacy of the decision and the claims surrounding it on personal social media platforms.

The very name attached to this dismissal carries its own injustice, as Vinoo Mankad's legacy remains unfairly defined by a mode of dismissal that was entirely within the laws of the game.

Will This Dismissal Ever Stop Dividing Cricket Fans?

You'll notice that fair play concerns dominate every discussion, yet the dismissal remains perfectly legal. Ethical considerations pull fans in opposite directions — some see it as legitimate strategy, others call it "craftiness not cricket."

Media outlets amplify this divide by labeling bowlers "cowardly," while captains like Sehwag and Rohit Sharma withdrew appeals, signaling internal uncertainty.

Authorities face a clear choice: modify the laws or keep relying on spirit-of-the-game arguments that satisfy nobody. Without legislative clarity, each new Mankad incident will reignite the same controversy, keeping cricket fans permanently split on this uniquely polarizing dismissal. The term itself dates back to 1947 in Sydney, when Indian player Vinoo Mankad controversially ran out Australia's Bill Brown during a Test match.

Broadcaster Piers Morgan condemned the Indian team's actions following a Mankad dismissal that sealed a 3-0 series victory for India over England, saying the whole team should be ashamed.