The Elusive 500: Ashwin’s Milestone Blemished by Umpiring Controversy

In a high-stakes clash between India and England during the second Test series, the cricketing world anticipated the historic moment when Ravichandran Ashwin would notch up his 500th Test wicket. However, what unfolded on the fourth day in Visakhapatnam was not a celebration but a saga of confusion and controversy.

Ashwin, in the 63rd over, bowled a delivery that saw Tom Hartley attempting a reverse sweep. Rohit Sharma claimed the catch, and the on-field umpire signaled the dismissal. Yet, the cricketing narrative took an unexpected twist when Hartley opted for a review.

Replays exposed the ball’s contact with the batsman’s hand, not the bat.The third umpire, adhering to protocol, rubbished the lbw aspects. The impact and ball hitting the wickets was both umpire’s call. In a normal situation it would stand out but the nuances of cricket get the better of everyone in most cases.

Here lies the crux of the controversy — a catch declared by the on-field umpire, disputed by the batsman eventually declared not out. If you go upstairs for a catch referal, you can simultaneously not appeal for an LBW. Where two points are umpire’s call and ball is hitting a moving object, for example Hartley’s hand.

The ensuing confusion triggered protests from Indian captain Rohit Sharma and Ashwin, challenging the umpire’s call. The umpire, in a perplexing turn, stuck to the initial decision of the catch, leaving the batsman unbeaten.

This unexpected turn of events extended Ashwin’s wait for the 500th Test wicket, overshadowing the milestone moment with lingering controversy. The cricketing fraternity now debates the intricacies of umpiring decisions, questioning the impact on the game’s spirit and Ashwin’s pursuit of this historic achievement.