Ball-Tracking Technology Explained: How Hawk-Eye Works in Cricket, Ball Trajectory Prediction, and DRS LBW Reviews

Hawk-Eye is the ball-tracking technology used in cricket's Decision Review System (DRS) to assess LBW decisions. Developed by Paul Hawkins (UK) and first used in cricket in 2001 (Channel 4 broadcast, England vs Pakistan), Hawk-Eye uses multiple high-speed cameras to track the cricket ball in three dimensions, reconstructing its trajectory and predicting where it would have gone had it not hit the batsman's pad. Its use in DRS has been official in international cricket since 2008, fundamentally changing how LBW decisions are reviewed.

How Hawk-Eye Works

Hawk-Eye technical mechanics: (1) Camera setup: Hawk-Eye uses 6-12 high-speed cameras positioned around the ground. In cricket, typically 6 cameras are used, positioned at different angles (both ends of the ground, from the stands, from behind the bowler's arm). Each camera captures 340 frames per second — far faster than broadcast cameras (typically 25-60 fps); (2) Triangulation: by combining the ball position data from all cameras simultaneously, Hawk-Eye triangulates the ball's exact 3D position at each frame — 340 times per second. This produces a highly accurate ball-position sequence from the moment of release to the moment of impact (with the pad or bat); (3) Trajectory reconstruction: from the 340 fps position data, Hawk-Eye reconstructs the exact trajectory of the ball before impact. This reconstructed trajectory shows: the ball's flight path, seam position, whether it bounced before hitting the pad (if it hit the pad below the knee roll — 'pitched outside leg'), and the point of impact relative to the stumps; (4) Trajectory prediction (the extension): for LBW DRS reviews, Hawk-Eye predicts what the ball would have done had it not hit the pad. This prediction extends the ball's trajectory beyond the point of impact using physics modelling — factoring in air resistance, ball speed decay, and gravity. The prediction extends up to 2.5 metres beyond the point of impact; (5) The 2.5-metre limit: Hawk-Eye's predictions beyond 2.5 metres from the point of impact are considered too uncertain to overturn umpire decisions. If the predicted trajectory shows the ball hitting the stumps at a point more than 2.5 metres from the impact, the umpire's call stands.

DRS LBW Review Process

How Hawk-Eye is used in DRS LBW reviews: (1) The captain's review: when a batsman is given out LBW by the on-field umpire, the batting team may review the decision using DRS. The captain signals the review (T signal). Similarly, if not out, the bowling team may review; (2) Three checks: the third umpire checks three things sequentially — (a) ball-tracking for pitch of the ball (did it pitch in line between wicket and wicket, or outside leg stump?), (b) impact (did it hit pad in line with the stumps?), (c) trajectory prediction (would it have hit the stumps?); (3) Pitching outside leg: if Hawk-Eye shows the ball pitched outside leg stump (behind the batsman's left leg for a right-hander), the batsman is not out regardless of where it hit. 'Pitched outside leg stump' = not out automatically; (4) Impact outside off stump: if the ball hit the pad outside off stump and the batsman was playing a shot, it is not out. But if the batsman was not playing a shot (pad hit with no attempt to play), it can still be out; (5) The umpire's call zone: if the trajectory prediction shows the ball clipping the edge of the stumps (in or out marginally), the system may show 'umpire's call' — meaning the prediction is uncertain enough that the umpire's original decision (out or not out) stands. This is displayed as a different coloured ball in the Hawk-Eye graphic.

Other Hawk-Eye Uses in Cricket

Non-DRS uses of Hawk-Eye: (1) Broadcast graphics: Hawk-Eye has been used in cricket broadcasting since 2001 — long before DRS. The 3D ball-tracking graphics (showing ball trajectory from above, side-on, from behind the wicket) are now a standard broadcast feature. The 'wagon wheel' (a top-down map of where every scoring shot went) uses Hawk-Eye data; (2) Pitch map: the pitch map (a visualisation of where each ball landed during a bowler's spell) is produced by Hawk-Eye and broadcast as a tactical analysis tool. It shows whether a bowler is consistently hitting a good length or varying short and full; (3) Edge detection: some DRS systems use a separate technology (Snicko or UltraEdge) for detecting whether the ball nicked the bat before hitting the pad or keeper's gloves. Hawk-Eye alone does not detect edges; (4) Worm chart (ODIs): the run-rate comparison graph (worm chart) used in broadcast for ODI matches compares two team's run rates over time — this is a data visualisation using scoring data rather than Hawk-Eye tracking, though it's often grouped with Hawk-Eye in broadcast graphics packages.