Why third umpire gave Ben Duckett not out? Where did Starc miss in catching the catch, MCC told a big mistake
The second Test match of the Ashes series is being played at Lord’s. On the fourth day of the Test, there was a lot of uproar over the catch caught by Mitchell Starc. Actually, Stark took a wonderful catch while diving Ben Duckett on the boundary line, but the third umpire declared the batsman not out. There is a lot of discussion in the cricket world about this decision of the umpire and the former Kangaroo player is very upset with the not out being given to Duckett. Seeing this controversy growing, now the statement of Marylebone Cricket Club (MCC) has come to the fore.
Why was Ben Ducken given not out?
In fact, the MCC has issued a statement saying that due to Rule 33.3, Ben Duckett was adjudged not out. Now understand what this rule says. According to Law 33.3, no catch shall be considered complete unless the fielder is in complete control of himself and the ball. That is, according to the rules, Stark did not catch the catch cleanly and even after catching the ball, the Kangaroo player was seen slipping. For this reason, Ben Duckett was declared not out by the third umpire.
What happened after all?
Ben Duckett had completed his half-century and looked set at the crease. Duckett tried to bat on a rising ball from Cameron Green’s over and the ball stood in the air. Fielding at fine-leg, Stark took an excellent catch while running.
The Australian players celebrated and walked towards the Duckett pavilion. However, it was seen in the replays that while completing the catch, Starc’s hands were touching the ground and the ball was clearly visible on the ground. Duckett was called back to the field after watching the replays.
