Cricket world left baffled following Ashes technology glitch

Ben Stokes

It was heartbreak for Australia early in the second day of the Ashes, losing David Warner to a ball from Ben Stokes. 

Until they didn’t. 

The call was reversed, with Stokes shown to have bowled a no-ball, stepping outside of his crease to deliver the ball. 

Following this call, a review of the previous balls found that Stokes had overstepped not once, but on all of his first four deliveries to Warner. This number was then extended to 14 balls across the morning session.

From here, it was then revealed that technological issues were plaguing the Ashes, meaning the usual way that no balls are detected was not operational. 

In recent years, the third umpire has called no balls with the aid of technology for officially sanctioned ICC matches. Unfortunately, that technology is not working in this match and is unavailable.

The technology involves dedicated cameras at each end of the pitch that are calibrated and ingested into a device which generates a signal for the third umpire.

With that technology unavailable, the officials have reverted back to using the old protocols/playing conditions whereby the on-field umpires will call no balls when identified, and the third umpire can check no balls but only at the fall of a wicket.

Officials are working to have the no ball technology available again as soon as possible.

Warner went on to make the most of his second opportunity, not out for 94 as tea was taken.

Somewhat surprising is the batsman’s prolific success following no-balls - should he reach 100, it will have been the fifth test century posted by Warner following a no-ball dismissal.

Author(s)
LATEST VIDEOS