Angkrish Raghuvanshi now sits in a tiny, unwanted club. On Sunday night, the Kolkata Knight Riders opener became only the fourth player in 19 IPL seasons to be ruled out for obstructing the field. Lucknow’s appeal felt unusual – it always does when this law is invoked – yet the replays, and the third umpire Rohan Pandit’s reasoning broadcast live, left little room for argument.
First, the bare facts. Raghuvanshi pushed the ball towards mid-off, turned, and sprinted for a tight single. The return from Ayush Badoni was swift and flat. Raghuvanshi was still five or six strides from the non-striker’s crease when he veered left, ending up on the edge of the pitch. As he dived, the ball thudded into him rather than the stumps. Lucknow appealed, on-field umpires sent it upstairs, and Pandit spent nearly two minutes working through the evidence before delivering his verdict: out, obstructing the field.
Pandit’s task, under Law 37, was straightforward in principle yet tricky in practice. He needed to confirm two things:
1. Did the batter “significantly change direction” while running?
2. If so, was there “probable cause” for that change?
If the answers are yes and no respectively, the law says the batter must go – intent does not come into it.
During the broadcast, Pandit said to the on-field officials, “He’s altered his line twice, lads, and there’s no obvious reason – he hasn’t glanced at the crease, only at the fielder.” Crucially, that exchange was audible to viewers, providing a rare, helpful window into the umpire’s thought process. He even paused to check whether Raghuvanshi had been watching the trajectory of the throw (which might have given him a defence). The replays showed Raghuvanshi looking at Badoni rather than the stumps, sealing his fate.
The IPL playing conditions keep an explanatory clause that has disappeared from the current online edition of the Laws of Cricket. It reads: “For the avoidance of doubt, if a batter, in running between the wickets, has significantly changed direction without probable cause and thereby obstructed a fielder’s attempt to effect a run-out, the batter should, on appeal, be given out obstructing the field.” Nothing there about intent, and nothing about whether the run-out would actually have been completed.
From side-on, Raghuvanshi’s last full stride is bang in line with the stumps; his next is almost half a metre wider. By the time he dives, he is practically back on a course towards the stumps, meaning the throw has to travel through him. That double movement – first away, then back – satisfied the “significant change” test beyond doubt.
Inevitably, emotions ran hot. Raghuvanshi looked bemused walking off, and assistant coach Abhishek Nayar was seen in a lengthy conversation with the fourth umpire. The suggestion from the KKR dug-out seemed to be that Badoni’s throw was off line anyway. Pandit’s reply, though not audible, is backed by the wording: the potential outcome of the throw is irrelevant if obstruction occurs.
Former India wicketkeeper Deep Dasgupta, on commentary, put it plainly: “Whether the ball would have hit the stumps is secondary. The law punishes the act, not the result.” That framing helps remove the moral angle that often clouds these decisions. As Dasgupta added, “You might feel hard done by, but the moment you change your path without a clear reason, you’re rolling the dice.”
Is the law too strict? Some players think so. Earlier in the season, Rishabh Pant argued that “there should be room for intent,” while ex-India coach Ravi Shastri believes umpires should first issue a warning. Yet the counter-view, expressed this week by former ICC umpire Simon Taufel, is that introducing subjectivity around intent “opens a can of worms and slows the game”. Taufel told a television panel, “We’ve tried that in the past; trust me, it’s messier.” Those words echo the lawmakers’ stance: cricket prefers bright lines over grey areas where possible.
KKR supporters may point out that batters instinctively look to avoid being hit. That is fair, and no one wants to see players injured. The key phrase, though, is “probable cause”. A slight sidestep to protect the body can be a valid motive, but Raghuvanshi’s initial shift took him wider, not safer, and he was already turning back towards the stumps when the ball struck him. Pandit evidently felt the movement was tactical rather than protective.
Could Raghuvanshi have stayed in his original lane and survived? It is impossible to know, yet most analysts agree that, at worst, he was looking at a tight run-out chance. KKR lost by a comfortable margin in the end, so the dismissal was not decisive, but the incident revived a rarely-used law and provided a mini-lesson in its application.
There is also a small procedural win here: the IPL’s decision to share the third umpire’s dialogue helped viewers understand a nuanced call. “It demystifies the process,” former England captain Nasser Hussain tweeted. “More, please.” Transparency is not a cure-all, yet on nights like this it transforms what could have been a furious talking-point into a teachable moment.
So, where does this leave the batter? Raghuvanshi, 23 and in his first full IPL season, can chalk it up to experience. Coaches will no doubt use the clip in future team meetings: hold your line, slide the bat early, and trust that the law protects the fielder’s right to a clear path. As Pandit’s calm voice reminded everyone, the game’s laws are often blunt instruments – but when applied with consistency, they give both sides a fair shake.
The obstructing-the-field law may feel harsh, especially in a format built on aggressive running, yet it exists to discourage deliberate or careless interference. On Sunday, it did exactly that.
