Third Umpire Forgets to Check No-Ball — India vs England 2016

The 2016 India vs England Test series was a landmark in the evolution of officiating technology in cricket. Following years of debate about the reliability and consistency of front-foot no-ball detection — a responsibility that had always fallen to the square-leg or on-field umpire — the ICC began trialling a system of third-umpire checks on front-foot compliance for every wicket-taking delivery.

The premise was straightforward: modern cameras offered frame-by-frame resolution that could detect a bowler's foot crossing the popping crease by millimetres, something a standing umpire simply could not do while simultaneously watching the delivery and the batsman. The technology existed; the question was whether it should be systematically deployed.

The India-England series provided a high-profile, high-stakes testing ground. England's fast bowlers, in particular, tended to land very close to the crease, and the concern was that several deliveries each session might technically overstep without the umpire ever spotting it. The potential for dismissed batsmen to be reprieved — or for the technology to be inconsistently applied — was significant.

Several matches into the series, it became clear that the front-foot no-ball checking protocol was producing results: dismissals were being reviewed and occasionally overturned because technology showed the bowler had overstepped by a fraction. To the naked eye — and certainly to the umpire — the deliveries had looked legal.

The most controversial applications came when wickets fell in tight moments and the subsequent no-ball check seemed to take an eternity, disrupting the natural flow of the game. For batsmen, the experience of being dismissed and then — minutes later — being called back was disorienting. For fielding teams, the reversal of what had felt like a legitimate wicket was infuriating.

Critics began to ask whether the protocol was being applied consistently: were all wickets checked in all matches? Was it only triggered when a review was called? The answers were unclear, which added a layer of frustration to the debate. The technology was there, but the framework for its application was still being refined.

During the second Test between India and England in Visakhapatnam, a wicket was taken and referred to the third umpire. Standard protocol requires the third umpire to check for a front-foot no-ball on every wicket-taking delivery, even if not specifically asked.

In this instance, the third umpire confirmed the wicket without checking the front foot. It was a procedural error that raised questions about the consistency and reliability of the third umpire system.

While there was no evidence that the delivery was actually a no-ball, the failure to follow protocol was concerning. The ICC acknowledged the lapse and reiterated the importance of following standard procedures.

The incident was relatively minor but highlighted a broader concern: as cricket becomes more reliant on technology and the third umpire, any procedural lapses undermine confidence in the system. It contributed to the push for automated front-foot no-ball detection technology.

“If the protocol is there to be followed, it must be followed every single time without exception. One missed check undermines the entire system.”

“Technology is only as good as the process around it. You need a watertight system, not just good cameras.”

“The batsman didn't know whether to come back or not. No one knew what was happening. That cannot happen in an international Test match.”

“We need automated systems. A human checking every ball in real time will eventually miss something. Let the technology do the work.”

The aftermath of the no-ball check controversy was primarily administrative rather than match-defining. The ICC convened discussions about whether the protocol had been applied correctly and consistently throughout the series. Umpires were reminded of their obligations, and the protocol documentation was clarified.

The broader consequence was an acceleration of interest in automated front-foot no-ball detection. If the system relied on a third umpire manually checking every wicket, human error would inevitably occur — as it had in this series. The case for fully automated systems — cameras that would instantly flag a no-ball without requiring a human to review the footage — became significantly stronger.

Several dismissed batsmen and their teams were left in an uncomfortable position: if the protocol had not been followed correctly, they had no way of knowing whether their dismissal had been genuinely legal. This uncertainty was cited as damaging to the integrity of the competition.