Mankad has been the buzz word in the world of cricket these days. Social media is flooded with people with divided opinions whether is’s correct to Mankad a batsman or not.
It all started when in an IPL game between Rajasthan Royals and Kings XI Punjab in Jaipur, Ravichandran Ashwin ran Jos Buttler out at the non-striker’s end. Buttler was backing out as Ashwin spotted that. He paused in his action and removed the bails before Buttler could come back which meant that the RR batsman was Mankaded.
After that incident, the cricketing fraternity engaged in a battle of opinions. Some believed it was wrong to do that as it’s against the spirit of the game. On the other hand, another argument was that it’s within the laws of the game and so, there is nothing wrong about it.
Krunal Pandya almost mankaded Mayank Agarwal
The Kings XI were on the field against Mumbai Indians in Mohali and the topic of Mankad once again came to the fore. This time, it was against Ashwin’s team. Krunal Pandya was delivering the 10th over of the innings during KXIP’s chase. KL Rahul lined up to face the 4th ball of the over. When he ran in to deliver, Mayank Agarwal backed up too far.
Krunal got distracted and he didn’t deliver. The left-arm spinner stopped and took a sharp turn towards the stumps at the non-striker’s end. He pretended to attack the stumps while Agarwal stretched to get back in the crease. But Krunal didn’t remove the bails nor did he give any warning to the batsman.
His actions could be perceived as a warning though. Agarwal realized he was backing up too far and the bowler knew about it. As Krunal stopped himself from Mankading, he also stopped giving rise to another controversy.