Cameras at the Gabba used to check no-balls in real-time by the third umpire have failed, partially explaining how Ben Stokes overstepped five times in his first over.
Stokes bowled David Warner in the first session on day two in Brisbane, putting Australia in trouble at 2/30.
However, the Englishman - in his first over of his first Test match back from a lengthy break – had overstepped and bowled a no-ball, meaning Warner was recalled.
In fact, it was revealed Stokes had overstepped in the previous four balls before the wicket, however none were picked up on.
It was a big moment in the context of the match and had Stokes known he was consistently overstepping, he could have readjusted.
The ICC has recently introduced measures that meant calling no-balls was the responsibility of the third umpire, however only the wicket-ball was picked up on review.
Each of Ben Stokes' first four deliveries to David Warner was a no-ball 👀@copes9 | #Ashes pic.twitter.com/kcyNrYHSYr
— 7Cricket (@7Cricket) December 9, 2021
SEN Test Cricket’s Adam Collins had the answer.
“We have an answer of sorts about what happened with the Ben Stokes’ no-ball and the four that preceded it, according to journalists who have been briefed at the Gabba, the technology monitoring no-balls has been down for the entire match,” he said.
“So they’ve reverted to the old playing conditions leaving no-balls up to the standing umpires who can then refer individual deliveries to the broadcaster upon request.
“Thus, why Paul Reiffel called a no-ball in the next oval.
“A bit more to add on that point, according to reports from the Gabba, and again the journalists have been briefed up there, there’s a four-camera setup from two angles from both ends sent upstairs in real-time to the third umpire.
“But those cameras failed yesterday, so a decision had to be made.
“They can use the broadcast cameras but the delay is too much, thus why the on-field umpire is doing the front-foot no-ball for the rest of this Test.”
Warner went on to pass 50 runs after lunch.