A highly dramatic and confusing moment took place during the ACC Men’s Asia Cup Rising Stars 2025 match between India A and Pakistan A at the West End Park Stadium, Doha. What should have been a simple on-field decision turned into chaos, heated arguments, and complete disbelief after the third umpire ruled a catch as ‘NOT OUT’ and also NOT a SIX — instead awarding a dot ball.
This unexpected call left Indian players stunned and fans questioning the rulebook.
Why the Confusion? – The Entire Incident Explained
The moment happened during the 9th over, bowled by India A’s Suyash Sharma, when Pakistan A batter Maaz Sadaqat mistimed a big shot towards deep mid-wicket.
What unfolded:
- Fielder Nehal Wadhera caught the ball near the boundary.
- Realizing his momentum would take him over the rope, he flicked the ball mid-air back into the field.
- Ramandeep Singh completed the catch at long-on.
- The on-field umpires sent it upstairs.
- The third umpire checked multiple angles.
- Everyone expected either:
- OUT (if fielder released the ball before touching rope), or
- SIX (if fielder touched rope while catching it).
But the final verdict shocked everyone:
It was all happening in Qatar 👀 And things got pretty heated in the middle…
— Sony LIV (@SonyLIV) November 16, 2025
Watch India A take on Pakistan A in #AsiaCupRisingStars2025 – LIVE NOW on #SonyLIV and #SonySportsNetwork TV channels 📺 pic.twitter.com/OZ56KQYxf0
“NOT OUT… and NOT SIX… the ball is declared a DOT BALL.”
This is extremely unusual and almost never seen at the professional level.
What the Rules Normally Say
To understand why this decision caused such an uproar, here’s what cricket laws state:
| Situation | Correct Decision (as per rules) |
|---|---|
| Fielder catches ball cleanly inside field | OUT |
| Fielder catches ball, touches rope before release | SIX |
| Fielder lobs ball in air before touching rope, second fielder catches | OUT |
| Ball touches ground/rope before catch | SIX |
| Fielder steps on rope while touching ball | SIX |
| No catch and no boundary | Runs scored (0,1,2…) |
But what happened here?
The third umpire decided:
- It was not out
- It was not six
- It was simply a dot ball
This combination is almost impossible under standard rules, which is why Indian players were visibly upset.
Indian Players’ Reaction – Shock, Anger, and Arguments
After the decision flashed on the big screen:
- Indian fielders surrounded the umpire asking for clarification.
- Many players were seen arguing and pointing towards the boundary.
- Even the batters were confused — the next batter had already walked in, assuming Sadaqat was out.
- Crowd noise increased as confusion spread across the stadium.
Despite the chaos, the match resumed with Maaz Sadaqat returning to bat.
Why This Decision Was Controversial
1. No clarity from the third umpire
There was no explanation visible on the big screen or shared with the fielding team.
2. Either OUT or SIX was expected
Based on replay visuals:
- The ball was fielded extremely close to the rope.
- If the fielder touched the rope → SIX.
- If he didn’t → OUT.
- There is no scenario in the rulebook that justifies a DOT BALL.
3. Pakistan A gained momentum
After the controversial survival:
- Sadaqat continued batting confidently.
- Pakistan A’s chase stayed strong at 94/2 (9.3 overs) requiring only 43 off 63 balls.
Read more: India vs Pakistan Upcoming Matches
Match Situation at the Time of Controversy
Pakistan A Chase Summary
| Stage | Score | Details |
|---|---|---|
| After Powerplay | 57/1 (6 overs) | Sadaqat 35(25) dominating |
| At time of confusion | 93/1 (after 9 overs) | Pakistan cruising |
| Moment of decision | 9.1 over | Catch overturned |
| Next ball wicket | Yasir Khan out on 11(9) | 94/2 |
Was It a Third-Umpire Error?
Based on available data from commentary:
- The umpire seemed unsure whether the ball touched the rope or not.
- A decision of “NOT OUT but ALSO not signaling a SIX” suggests:
- Either miscommunication
- Or a technical error in interpreting the footage
- Or an unusual reading of the boundary rule
Even commentators labelled it:
“Shocking decision.”
Impact on the Match
This moment shifted the momentum sharply:
- Pakistan A batters gained confidence
- Indian bowlers became frustrated
- The match atmosphere turned tense and emotional
- Fans on both sides started reacting strongly online and inside the stadium
Such decisions can completely change the course of a match, especially in an aggressive T20-style chase.
Final Thoughts – A Decision That Will Be Discussed for Long
The India A vs Pakistan A match delivered:
- High drama
- Intense cricket
- A rulebook controversy
- And one of the strangest third-umpire calls seen in recent games
While cricket often brings thrilling moments, this incident will likely be remembered as a rare case where technology, rules, and interpretation clashed badly.
It raises key questions:
- Should third-umpire decisions be better explained?
- Should boundary catches have stricter clarity?
- Should teams be allowed more transparency in reviews?
One thing is certain — the debate will continue long after the match.
