Controversial Decision in IPL 2026 Final: Washington Sundar's Not Out Call Sparks Debate
Washington Sundar's Controversial Moment
The IPL 2026 final witnessed a heated discussion regarding officiating consistency, particularly surrounding Washington Sundar's contentious 'not out' decision during the match against Royal Challengers Bengaluru (RCB).
Batting first after being put in by RCB captain Rajat Patidar at Ahmedabad's Narendra Modi Stadium, the Gujarat Titans faced a challenging start, losing several key players including opener Sai Sudharsan (8), captain Shubman Gill (10), Nishant Sindhu (20), and Jos Buttler (19), leaving them at a precarious 73/4 in just 12.1 overs.
Sundar's Key Partnership
Following this, Washington Sundar and Arshad Khan (15) managed to form a brief partnership of 20 runs for the fifth wicket before Khan's dismissal at 99/5, further complicating the Titans' recovery efforts in this crucial match.
The Catch Controversy
A pivotal moment arose when a low catch attempt by Jordon Cox on Sundar's flick off Jocab Duffy's delivery became a focal point of controversy. The incident occurred during the tenth over, with the ball heading towards fine leg where Cox was positioned.
Initially, the on-field umpire ruled Sundar out after Cox appeared to take a clean catch. However, as Sundar began to leave the field, he was asked to wait for a third-umpire review. The slow-motion replays indicated that the ball had made contact with the ground before Cox could secure it fully.
Third Umpire's Decision
The third umpire ultimately overturned the initial out decision, leading to visible frustration from RCB's captain Rajat Patidar, who engaged in a discussion with the on-field umpires regarding the inconsistency of the ruling.
Gone... gone... DROPPED! Big moment in the match as #WashingtonSundar is dropped in the deep by #JordanCox. #TATAIPL 2026 FINAL | #RCBvGT | LIVE NOW https://t.co/nTKb3Qmpst
At the time of the incident, Sundar was on 4 runs from 7 balls. The third umpire's reversal was based on the inconclusive nature of the catch, as replays confirmed the ball had touched the ground.
Debate on Officiating Consistency
This decision ignited a significant debate on social media platforms, particularly X (formerly Twitter), where fans and cricket analysts highlighted discrepancies in umpiring decisions throughout the tournament. Many compared this incident to a similar catch taken by Jason Holder earlier in the series that was ruled out.
Opinions were divided; while some believed Sundar was fortunate to remain not out, others argued that the replay justified the third umpire's decision, emphasizing the challenges of making calls on 'soft signals' and low catches in high-pressure situations.
Final Match Summary
Despite the controversy, Washington Sundar went on to score an unbeaten 50 off 37 balls, helping the Gujarat Titans set a total of 155/8 in their 20 overs, creating a target of 156 runs for RCB.
Rasikh Salam Dar led the bowling attack for RCB with impressive figures of 3/27, while Bhuvneshwar Kumar (2/29) and Josh Hazlewood (2/37) also contributed significantly to restricting the Titans.