Watch- Pat Cummins Argues With Umpire As Taskin-Hazlewood Collision Turns Chaotic

Pat Cummins argues with the umpire after collision [Source: Cricket Australia]

As Bangladesh suffered a definitive collapse against Australia in the second Test at Mackay, the team scripted some horrible and shameful records for themselves after dominating at Darwin. Nevertheless, the collapse was not the only thing that steamed up cricket fans.

In a particular incident during the 28th over of Bangladesh's innings, Taskin Ahmed, the batter, was involved in an incident with Josh Hazlewood, the bowler, which resulted in a missed catch and an agitated Pat Cummins running up to the umpire for an explanation of the incident. 

Taskin Ahmed collides with Josh Hazlewood; Saves his precious wicket

Notably, on the third ball of the 28th over, Hazlewood bowled a short delivery around the middle-stump line at 134 kph. Taskin was on strike, with Taijul Islam at the non-striker's end, and the bowler backed away to make room to play the shot towards the leg side. 

In an attempt to play a pull shot, he got a top edge, sending the ball straight up into the air. As Taskin looked to move forward for a run, he found Josh Hazlewood running straight towards him while attempting to catch the ball. As both Hazlewood and Taskin Ahmed got in each other's way, they collided, and the ball landed in the backward short-leg region, leaving Taskin safe.

Also Read- Mitchell Starc Overtakes Dale Steyn For Most Test Wickets: All Records Made In AUS vs BAN

The incident immediately drew a reaction from Hazlewood, who looked towards the square-leg umpire, while Pat Cummins also approached the umpires for an explanation. 

Pat Cummins argues with the umpire after the collision

Immediately after the collision, Cummins was seen rushing straight towards on-field umpire Nitin Menon to seek an explanation. The Australian captain argued with Menon for quite a few moments as the umpire gestured with his hands while explaining why the batter was not at fault. 

Pat Cummins was clearly appealing for Taskin Ahmed's dismissal, believing Josh Hazlewood had been obstructed while attempting the catch. However, Menon's decision was final on the field, and Cummins was left with no choice but to walk away empty-handed after the appeal was rejected.

Watch the video below:

cricket.com.au

@cricketcomau

Who was in the wrong here? #AUSvBAN WATCH:

Aug 22, 2026, 9:02 AM

Significantly, the ball was not declared dead, and it was recorded as a dot ball for Bangladesh. Play continued with the next delivery of the over, with Ahmed taking strike.

Was anyone at fault for the catch-drop collision?

From the looks of it, it seemed like nobody was at fault for the missed catching opportunity. In the video, it can clearly be seen that Taskin Ahmed, immediately after playing the shot, looked straight up into the air to track the ball. 

While watching the delivery, he unknowingly moved towards the non-striker's side to complete his run with Taijul Islam. However, after a few quick steps, Ahmed realised that Josh Hazlewood had come in his way. 

Hazlewood was also not at fault, given that he was keeping his eyes on the ball and went straight towards it to attempt the catch. 

As soon as Taskin realised that Hazlewood was in front of him, he tried to swerve past him but failed to do so because there was very little time to react. The two subsequently collided, resulting in the ball landing in no-man's land.

What does the ICC rule say about catch obstruction?

As per the cricket laws, the striker can be deemed out if any wilful action or obstruction by either batter prevents a fielder from completing a catch. However, one key aspect of the rule is that the intent of the batter matters, since the obstruction must be wilful. 

Accidental collisions or bumps do not count as an obstruction, and the umpire has to determine whether there was intent. In this case, umpire Nitin Menon decided that there was no such malicious or deliberate intention from the batter, and hence, it was ultimately an accidental collision that did not warrant a dismissal.

Will Hazlewood or Taskin be punished after the match?

The declaration from the umpires came as some relief to Bangladesh, who had already been bundled out for 64 runs in the first innings. Taskin will therefore not face punishment for the accidental collision. Although wilful distraction or obstruction of fielders or bowlers during a catch can lead to a dismissal, an accidental incident does not automatically result in a penalty. 

For example, there is no separate financial penalty, match ban, or suspension simply because a batter is involved in an accidental collision. An immediate dismissal can be given if the umpire deems that the striker wilfully obstructed or distracted the fielder while attempting to take a catch. 

However, in this case, neither Taskin Ahmed nor Josh Hazlewood appeared to be at fault, and therefore, no punishment will be given to either player.

Also Read- "Things Are Back To Normal": Internet Troll Fest Activated As Starc Scripts Bangladesh Collapse