Table of Contents
The IPL 2026 opener between Royal Challengers Bengaluru (RCB) and Sunrisers Hyderabad (SRH) had everything fans expect from a blockbuster start – big runs, pressure moments, and a thrilling chase. But despite the high-quality cricket on display, it was a controversial umpiring decision that completely dominated post-match discussions. Heinrich Klaasen’s dismissal, following a boundary catch by Phil Salt, quickly became the most debated moment of the game, leaving fans, experts, and players divided.
Klaasen was looking in control during a crucial phase of SRH’s innings. With the team recovering from an early collapse, he had stitched together a strong partnership with skipper Ishan Kishan. However, what seemed like a spectacular fielding effort soon turned into a major talking point, as questions arose over whether the catch was actually clean or not.
Heinrich Klaasen’s dismissal raises eyebrows
The incident unfolded in the 14th over when SRH were 126/3. Klaasen, batting confidently on 31 off 21 balls, attempted an aggressive pull shot off a short delivery from Romario Shepherd. The ball soared towards deep mid-wicket, where Phil Salt was stationed close to the boundary rope.
Salt sprinted to his left and completed a tumbling catch that looked brilliant in real time. But almost instantly, there was uncertainty. Given how close he was to the boundary, the on-field umpires decided to refer the decision upstairs to third umpire Rohan Pandit.
At the heart of the review was a simple yet crucial question: did Salt touch the boundary cushion while in contact with the ball?
According to the Laws of Cricket, a catch is invalid if the fielder touches the boundary rope or the ground beyond it while holding the ball. If such contact is confirmed, the batter is not out, and six runs are awarded instead. This made the third umpire’s role extremely important, as the decision could swing the momentum of the match.
After reviewing the available footage, Rohan Pandit ruled Klaasen out. The reasoning was based on a lack of conclusive evidence. The camera angles shown during the review did not clearly prove that Salt’s foot had touched the boundary cushion while he was completing the catch.
Interestingly, the third umpire was heard saying, “I don’t see any movement of the cushions” before confirming the decision. That statement later became a focal point of the controversy, especially when additional angles were shown after the decision.
Also READ: IPL 2026 – Who is Ananya Birla? Meet the sister of RCB’s new chairman
Why the decision sparked controversy?
The drama didn’t end with the umpire’s call – it only intensified. After a short break, broadcasters aired a top-angle replay that had not been available to the third umpire during his review. This new angle appeared to show the boundary cushion moving as Salt completed the catch, raising serious doubts about the correctness of the decision.
This led to a wave of reactions online. Many fans and analysts argued that the movement of the cushion indicated contact, meaning the catch should have been ruled not out. Others, however, believed the evidence was still not definitive and could have been caused by other factors such as hand contact or even camera perspective.
Cricket experts didn’t hold back either. Former England captain Michael Vaughan was particularly critical, saying, “Looked to me like the foot had touched the boundary sponge to me … that’s a big call for RCB … Not sure how you can give that out and be absolutely sure no part of the foot touched the sponge … and the sponge moved … a bit of a giveaway.” His comments reflected what many viewers were already thinking.
Meanwhile, former India captain Sunil Gavaskar suggested that the third umpire could have taken more time and explored additional angles before making such a crucial call.
Beyond the debate, the impact of Klaasen’s dismissal was significant. At that stage, SRH were rebuilding well, with Klaasen and Kishan guiding them towards a potentially massive total. However, once Klaasen departed, the innings lost momentum. SRH quickly lost a couple more wickets and eventually finished at 201/9.
RCB, on the other hand, capitalized brilliantly. They chased down the target with ease, finishing the game with 26 balls to spare and securing a six-wicket victory. In hindsight, the controversial decision felt even more pivotal, as it shifted the balance of the game at a crucial moment.
Also READ: Fewest overs taken to chase down 200 plus total in IPL ft. RCB
Disclaimer : This story is auto aggregated by a computer programme and has not been created or edited by DOWNTHENEWS. Publisher: crickettimes.com
