Ashes: technological malfunction leads to several no-ball go undetected on second day of Gabba Test
Humans have been too reliant on technology in recent years. It has taken over every field of occupation, and sports is no stranger to it. Hence, whenever there is a glitch in the tech, or it fails to perform its task, major blunders take place.
One example of such blunder comes from the second day of the first Ashes Test played on the 9th of December in Brisbane. It was the 13th over of the game when Ben Stokes’ perfect inswinger that claimed the wicket of David Warner for the score of 17 was checked by the third umpire only for him to find it as an illegal delivery.
According to the footage, Ben Stokes’ front foot was crossing way over the popping crease, which is not allowed. Hence it was called a no-ball. But the problem didn’t end there. Rather it was the starting point of the revelation that even the previous three balls by Stokes that were counted by the umpire were also illegal deliveries.
Since the umpire did not call them, the Pacer could not correct his run-up and ended up bowling a series of no-balls, including the one that took Warner’s wicket.
Ben Stokes was revealed to have overstepped 14 times in opening session, with only two called as a no-ball #Ashes https://t.co/4cim2yFaAa
— cricket.com.au (@cricketcomau) December 9, 2021
Later, according to a report by Zee News, the broadcasters also reported that the equipment used by the third-umpires to detect no-balls had broken. And in such a scenario, according to the rulebook, the decision-making protocol was reversed to the version used before technology. In other words, the on-field Umpires were supposed to make those front foot no-balls which they failed to do.
Now the whole cricketing fraternity is waiting for the ICC to report or comment on the fiasco caused by the on-field umpires present in the game.
