IPL 2019: Why wasn't Deepak Chahar taken off the attack after bowling two beamers?
Did the umpires commit a blunder by not taking Chahar out of the attack?
An interesting incident involving Deepak Chahar took place in the match between the Chennai Super Kings (CSK) and Kings XI Punjab (KXIP). Chasing a target of 161, KXIP slightly lost control over the chase in the middle overs. The Chennai spinners operated brilliantly and left it to the pacers to finish the job for the team.
Scott Kuggeleijn and Deepak Chahar were the two trusted bowlers to do the job. Kuggeleijn bowled a good 18th over and conceded just 7 runs. This brought the equation down to 39 runs needed off 2 overs for KXIP to win the match. While CSK seemed to be the favourites to win the game at this point in time, things turned awry in a matter of just two balls.
Deepak Chahar bowled two beamers off the first two balls. This revived the hopes in the KXIP camp. However, he pulled things back well and also picked the wicket of David Miller in that over. Thus, CSK won the match by 22 runs after the New Zealand pacer bowled a good last over.
Why wasn’t Deepak Chahar taken out of the attack like Siraj?
In the earlier game between RCB and KKR, pacer Mohammed Siraj was taken out of the attack after he bowled two beamers in the same innings. Thus, this has raised many questions as to why Chahar wasn’t pulled out.
According to the rule, a bowler will be pulled out of the attack if he bowls two lethal beamers in the same match. It is left to the sole discretion of the on-field umpire to decide if the ball is dangerous. Both the beamers that Siraj bowled were aimed straight at the batsman’s body. However, in Deepak Chahar’s case, he attempted to bowl slower balls but couldn’t. The ball was at a fair distance from the batsman’s body and thus he was allowed to continue.
Get the latest Cricket News and updates from the Indian Premier League, Match Predictions, Fantasy Cricket Tips and lots more on CricTracker.com.
Download Our App