The Roar
The Roar

Advertisement

Mankadded batsman warned by skipper

Roar Guru
23rd February, 2012
5

Sri Lankan batsman Lahiru Thirimanne won’t be backing up quite so far following the Mankad incident against India in Brisbane.

Thirimanne was “Mankadded” by Indian spinner Ravi Ashwin in the 40th over of Sri Lanka’s innings on Tuesday.

A discussion between Indian captain Virender Sehwag, elder statesman Sachin Tendulkar and the umpires resulted in the appeal being withdrawn.

Sri Lanka captain Mahela Jayawardene said he had spoken to his batsman about not taking an unfair advantage by backing up too far.

“There was a bit of fault in him as well, a young lad and I’m sure he’ll learn from that and we’ve spoken, definitely yes,” Jayawardene told reporters at Bellerive ahead of the tri-series match against Australia on Friday.

“He can take a start but just where he’s leaving the crease is probably a bit unfair.

“He can probably hold himself a bit longer and then take a start, I don’t think that’s a problem.

“It’s just him understanding exactly what he can do and can’t do.”

Advertisement

The term Mankad refers to a runout performed by the bowler to dismiss a batsman backing up to take a run.

It was coined after Indian player Vinoo Mankad ran out Australian Bill Brown at the SCG in 1947.

A cricketing gentleman’s agreement has meant bowlers giving a warning to batsmen before running them out.

Australian captain Michael Clarke admitted he doesn’t know how he would react if one of his bowlers “Mankadded” an opponent.

“I’ll find out when I’m in that position. Hopefully I’m not,” he said.

“I hope (Thirimanne) decides to stay in his crease but I’m glad that nothing’s come of it.

“It’s a part of the game that I don’t like.

Advertisement

“But in saying that if somebody’s going to be a long way outside their crease you would hope that by warning them they would understand that the bowler or the fielding captain has asked the batsman to stay in his crease.”

close