Hawk-Eye Ball Tracking in Cricket: LBW Trajectory Prediction, Margin of Error, and Umpire's Call
Hawk-Eye uses six or more high-speed cameras to triangulate a cricket ball's 3D trajectory and predict where it would have gone after hitting the batter's pad, enabling DRS LBW reviews. The system claims a margin of error of approximately 2.5mm. Umpire's Call applies when the ball-tracking model shows the ball clipping the edge of the stumps within a defined marginal zone, meaning the on-field umpire's original decision stands. The technology has been central to DRS since 2009 but continues to attract debate over how accurate predictions beyond the point of pad impact genuinely are.
Hawk-Eye Innovations' ball-tracking system is the primary LBW analysis tool within cricket's Decision Review System (DRS). Using six or more high-speed cameras positioned around the ground at different angles, the system captures the ball's position at up to 300 frames per second and calculates a precise 3D trajectory. When a fielding team or batter triggers a DRS review of an LBW decision, Hawk-Eye models the ball's path from the bowler's hand to the point of contact with the batter's pad, then projects where it would have continued if the pad had not intercepted it.
How the Prediction Model Works
The projection beyond the pad is not a simple linear extrapolation. Hawk-Eye's model incorporates the ball's seam position, spin rate (measured from camera data), pitch declination, and speed decay at impact. These inputs feed into a physics-based trajectory model that generates a probabilistic prediction — not a single certain path, but a cone of possible trajectories, with the central estimate displayed on screen. The displayed path represents the median predicted trajectory. DRS LBW assessments apply three checks: whether the ball pitched in line (or outside off stump — not lbw), whether it struck the batter in line with the stumps (or above knee roll), and whether the ball would have hit the stumps. If all three are satisfied (and not negated by an inside edge or carried outside the stump lines), the ball is deemed to be hitting the stumps and the batter is out.
Umpire's Call and the Margin of Error
ICC regulations specify that Umpire's Call applies when the ball-tracking model shows the ball clipping the edge of the stump zone within a tolerance margin. For the impact point on the stump face (width roughly 9 inches or 22.9cm per stump), the Umpire's Call zone is approximately the outer 2.5cm on each side. Similarly, for height, the ball must be shown to be clearly hitting below the top of the stumps to overturn a not-out — a ball predicted to be clipping the top bail triggers Umpire's Call. The 2.5mm claimed system accuracy applies to the ball-tracking positions up to pad impact; the projection beyond the pad is less precise, with independent analyses suggesting errors of 10–40mm are plausible. Critics argue that Umpire's Call is an admission that Hawk-Eye's predictions at stump edges cannot be trusted without the safety net of the on-field umpire. Defenders argue that the combination of Hawk-Eye plus Umpire's Call is still far more accurate than unaided human judgment across thousands of decisions.
Frequently asked questions
Why does Umpire's Call exist in DRS, and what are the strongest arguments for and against removing it from LBW decisions?
Umpire's Call exists because the ICC and Hawk-Eye's developers acknowledged that ball-tracking predictions beyond the point of pad impact carry a margin of error that is not negligible. The argument for keeping Umpire's Call rests on three pillars. First, the physics of projection: once the ball hits a batter's pad, its subsequent trajectory is no longer directly observed — it is modelled from the known physics of the ball's approach. Variables including the exact angle of impact with the pad, the degree of compression of the pad, and any minor deflection all affect the true path. The Hawk-Eye model cannot observe any of these factors; it projects the pre-impact trajectory forward as if the pad were not there. At the margins — when the ball is predicted to clip the outer edge of the stump — tiny modelling errors become decisive. Second, the cumulative error argument: across a Test series, if Hawk-Eye systematically over- or under-predicts the degree to which the ball would continue to swing or turn after pad contact, the errors favour one batting team or one bowling style. Removing Umpire's Call and trusting marginal predictions entirely would amplify this systematic error. Third, the umpire credibility argument: on-field umpires have become effectively redundant for LBW if their calls can be overturned by a model prediction showing the ball clipping the edge by a fraction of a centimetre. The ICC's position is that umpires remain a central part of the game, and their judgment in marginal cases should stand unless the technology clearly shows they were wrong. The argument for removing Umpire's Call is simpler: it creates anomalies where a batsman given not-out retains the decision even when Hawk-Eye shows the ball would have hit the stump — because it clipped the edge rather than struck the middle. Supporters of removing it argue that if Hawk-Eye shows the ball hitting the stumps, however marginally, the decision should be out, and the system's margin of error is small enough to trust. The practical result of Umpire's Call is that teams must review with higher confidence — reviewing only genuinely in-line deliveries that struck clearly in front of the stumps, rather than speculative DRS reviews of balls that clipped the stumps. This has reduced the total number of successful reviews over the course of DRS history.