The Blind Spot in Ball-Tracking on Asian Pitches: Where Umpire's Call Stops and Protocol Begins

M Chinnaswamy Stadium, Bengaluru, 9 March 2026. The second Test of the Border-Gavaskar Trophy. A second before he was given out, Steve Smith lifted his head and looked towards the dressing room, searching for a signal on whether to review. That single glance drowned the rest of the series in an argument about cheating versus instinct. Five days later, on 14 March 2026, I launched my weekly referee-review channel from the 2.6m by 2.1m box room above my Didsbury garage, with a £340 microphone and a ring light. The first twelve videos averaged 380 views. What I brought back from Bengaluru was not a view count. It was an unfinished question: nobody that day asked what evidence the ball-tracking system was actually relying on when it claimed the ball would hit the stumps.

Fifty years of watching this game from both ends of the pitch — once as a right-back, once with a whistle in hand, now behind a microphone — have taught me one discipline. Before anything else, separate what each angle proves from what it cannot. On Asian pitches, in the current argument about Umpire's Call, nobody does that.

Context

DRS was first used in a Test match on 23 July 2026, at the Sinhalese Sports Club in Colombo, during the India–Sri Lanka series. The biggest cricket economy in Asia, India, accepted the full system much later — from November 2026, in the home series against England. Those eight years of delay rested on a philosophical objection: that technology inverted the burden of proof against the batter. The umpire's decision stays final; technology intervenes only for the clearly wrong. That principle built the whole architecture.

Inside it sits Umpire's Call. Two reviews per innings is not a convention of the game but a clause in the ICC Test playing conditions. And when ball-tracking shows the ball hitting the stumps but less than half the ball doing so, the final call returns to the on-field umpire. Viewers read that as technological doubt. It is, in fact, a boundary drawn by protocol.

The character of an Asian surface is not visible from the dressing room. It is visible from the pitch. Colombo, Galle, Chattogram, Multan, Sharjah — the common trait is low bounce and high turn. The distance from pitching point to stumps is short, and it is across that short distance that the ball breaks most. Ball-tracking reads the flight from release to pitch and then projects the path after pitching. Its reliability depends on how many frames it has to work with.

The economics of match operations sit inside this too. The host broadcaster supplies the technology, installs the cameras, runs the tracking. The third umpire sees the full array; the crowd sees two or three selected angles. Since umpire reviews were withdrawn, the weight of the decision rests more heavily on the players, and that weight is audited on screen, not on the field. Accuracy of technology and selection of camera angles are two separate questions. To a viewer they arrive as one.

Core Analysis

I have seen this kind of decision from three angles — the front-on camera, the stump camera, and the tracking graphic. Each answers a different question. The truth is still in the replay.

The first angle, front-on, answers two questions: the no-ball line, and whether the batter was in line with the stumps when the ball struck pad. Error margin here is thin, because this is an event, not a projection. It is exactly what the umpire sees from the bowler's end, and that is why technology is on firm ground on the in-line question.

The second angle, the stump camera, shows the height at which the ball struck pad and whether it pitched in line. Again, an event.

The third angle is where the problem lives. Ball-tracking projects the path after pitching. The slower the ball and the sharper the turn, the fewer frames are available for that projection. On an Australian surface the ball reaches the stumps at knee-to-thigh height; there are more frames between pitch and stumps, so the model has more to learn from. On a low-bounce Asian turner the ball often skids in at ankle height across a handful of frames. The error cone widens. When turn increases, lateral error grows with it, because a spinner's delivery breaks differently before and after pitching.

Here is the part that rarely gets said. The error cone does not announce itself, but it produces a large indirect effect. The wider the error cone, the less often the condition of half the ball hitting the stumps is met; the more often Umpire's Call is triggered; the more often the decision returns to the on-field umpire. A system built to reduce the umpire's load quietly hands it back on the surfaces where Asian cricket is mostly played.

This is where process, protocol and correctness must be separated. Process asks whether the camera was in the right place. Protocol asks whether the half-ball rule should have applied to this decision. Correctness asks whether the ball would actually have hit. The three answers can differ, and frequently do. Television collapses them into one.

Watching Asian matches, I look for one signal: how much of the pitch-to-stumps distance the tracking graphic actually shows. If the graphic ends well before the stumps, the system is leaning on projection more than evidence.

On numbers, I hold to my own rule, fixed after 1 December 2026. At the Qatar World Cup, Kaoru Mitoma's cutback for Japan against Spain was ruled in play by 1.88 millimetres, a figure produced by semi-automated offside technology and the ball sensor. Since then my rule has been simple: every figure must trace to a named system with a stated tolerance. So I print no millimetre figure here — the pitch-specific frame count for ball-tracking in Asia is not public. What is not public, I do not fill in with guesswork.

Audio is evidence of the same kind. UltraEdge analyses stump-microphone sound. A spike when ball meets bat and a spike when ball meets pad both register; the distinction rests on latency and playback sync. Across 92 behind-closed-doors matches in June 2026 I worked this problem in a twelve-part series and learned that the more crowd noise masks the evidence, the less the public doubts. With forty-eight thousand people in the ground, nobody sees the UltraEdge spike. They believe it.

Contrarian Angle

Camera, microphone and sensor are all witnesses. None is a judge. Legal reasoning never puts the weight of proof and the weight of decision on one side. Cricket has.

I have seen this match from three angles, and the truth is still in the replay — because the replay reaches the viewer through somebody's hands. The host broadcaster's producer decides which angle goes up and when. So the real lever sits in the pre-series calibration test. Under ICC minimum performance standards, that test is run on the ground itself before each series, with balls delivered at set heights and speeds. The report goes to the match referee. It is shown to nobody.

That is why Asian anger never settles on a target. Some blame the umpire, some the technology, some the ICC. The argument should have been with an invisible file.

The tempting simple fix follows: give three reviews instead of two per innings and decisions improve. Wrong. More reviews reduce only the count of wasted ones. Umpire's Call outcomes do not fall, because the fault lies in protocol design and calibration, not in the quota. Three reviews mean faster decisions, and wrong decisions confirmed with greater confidence.

The second trap is emotional. The roar when a batter is given out is part of the game. Broadcast then uses that roar as proof. A batter-friendly cut, a slow-motion replay, then the graphic — three steps that land the viewer on a verdict while showing them a producer's chosen reality. The anger is genuine. The target is placed. When Piccadilly Radio handed me a Monday slot in August 2026, the lesson was already fixed: what the player felt and what Law 12 says are two different things, and the audience has to be shown both.

Takeaway

Put the error cone on screen beside the tracking graphic — how precise the system is at that ground, at that speed. Publish the calibration annexure with the match referee's report, unless confidentiality can genuinely be defended. Release pitch-specific frame-count data, and researchers, coaches and boards will argue in one language.

Every Asian match will return the same question: is technology telling the truth, or is protocol? Over the next decade the answer depends on what one governing body permits one producer to show. Who opens that screen?