Australia captain Aaron Finch ‘not a big fan’ of Mankad dismissals

The dismissal has been a hot-button issue again since India’s Deepti Sharma ran out England’s Charlie Dean at the non-striker’s end in a women’s ODI last month

David Charlesworth
Friday 14 October 2022 16:25 BST
Comments
Finch is ‘not a big fan’ of Mankad dismissals
Finch is ‘not a big fan’ of Mankad dismissals (Getty Images)

Your support helps us to tell the story

From reproductive rights to climate change to Big Tech, The Independent is on the ground when the story is developing. Whether it's investigating the financials of Elon Musk's pro-Trump PAC or producing our latest documentary, 'The A Word', which shines a light on the American women fighting for reproductive rights, we know how important it is to parse out the facts from the messaging.

At such a critical moment in US history, we need reporters on the ground. Your donation allows us to keep sending journalists to speak to both sides of the story.

The Independent is trusted by Americans across the entire political spectrum. And unlike many other quality news outlets, we choose not to lock Americans out of our reporting and analysis with paywalls. We believe quality journalism should be available to everyone, paid for by those who can afford it.

Your support makes all the difference.

Australia captain Aaron Finch says he is “not a big fan” of bowlers running out batters backing up after an apparent flashpoint between Mitchell Starc and England captain Jos Buttler in the third T20.

The dismissal, informally recognised as a ‘Mankad’ after former India all-rounder Vinoo Mankad, has been a hot-button issue again since India’s Deepti Sharma ran out England’s Charlie Dean at the non-striker’s end in a women’s ODI last month.

Before the T20 series between Australia and England came to a soggy end after a rain-enforced abandonment at Canberra’s Manuka Oval, Starc seemed to warn Buttler about being out of his crease while Dawid Malan was batting at the other during the tourists’ innings.

Finch was unaware of what took place but, while he kept his counsel about whether he would give the green light for his bowlers to dismiss batters that way and felt it was fair to offer a warning, he suggested he is generally against it.

“I think if guys get a warning, then it’s fair game after that,” Finch said. “That would go for most teams, I assume, if you give a batter a warning, because you think that they’re gaining a little bit too much ground before the ball is bowled. But I’m not a big fan, personally.”

Buttler has twice been out to this mode of dismissal before, first by Sri Lanka’s Sachithra Senanayake in an ODI in 2014 and then by Ravichandran Ashwin in the Indian Premier League five years later.

While the MCC, the game’s lawmaker, has shifted the dismissal from unfair play to simply a run out in its charter, Buttler said recently he would withdraw the appeal if done by one of his bowlers.

“No one wants to see them in the game because they always create such a talking point when it should be about the battle between bat and ball,” Buttler said.

England seamer Chris Woakes backed up his skipper but felt Australia left-arm paceman Starc was well within his rights to caution Buttler.

“I personally wouldn’t run someone out (like) that but a warning – no issue with that to be honest,” he said. “Happy with giving guys warnings.”

In the first T20 at Perth on Sunday, Matthew Wade appeared to obstruct England quick Mark Wood, who was attempting to take a return catch off the Australia wicketkeeper-batter.

Wade, having top-edged on to his helmet, stuck his arm out and would likely have been given out had England appealed – although Buttler declined to do so, in part because he did not want to incur any opprobrium from the Australian public.

“We’ve only just got to Australia so I thought just carry on in the game,” he said in the aftermath.

Join our commenting forum

Join thought-provoking conversations, follow other Independent readers and see their replies

Comments

Thank you for registering

Please refresh the page or navigate to another page on the site to be automatically logged inPlease refresh your browser to be logged in