The Physics of Cricket Sixes: How Six Distance Is Calculated

A cricket six is a solved physics problem once you know the exit velocity and launch angle. Every broadcast graphic showing a distance in metres is the output of one equation applied to sensor data.

The Range Formula: The Equation Behind Every Broadcast Graphic

When a batsman hits the ball, it follows projectile motion. Ignoring air drag (a reasonable first approximation for a powerfully struck ball over a short flight), the horizontal distance is:

R = v² sin(2θ) / g

• R = horizontal range in metres
• v = exit speed off the bat in metres per second
• θ = launch angle above the horizontal
• g = gravitational acceleration, 9.8 m/s²

The derivation is straightforward. Horizontally, the ball travels at constant speed v cos(θ). Vertically, it decelerates at g. Setting vertical displacement to zero gives time of flight T = 2v sin(θ) / g. Multiply T by the horizontal speed and the double-angle identity sin(2θ) = 2 sin(θ) cos(θ) collapses everything to R = v² sin(2θ) / g.

The sin(2θ) term is maximised when 2θ = 90°, meaning θ = 45°. At 45°, sin(90°) = 1 and the formula reduces to:

R = v² / g

One less obvious consequence: a ball hit at 30° travels the same horizontal distance as one hit at 60°, because sin(60°) = sin(120°) = 0.866. A batsman who swings too flat loses exactly as much range as one who hits too steep. The 45° sweet spot is not a coaching cliche. It is the geometry of projectile motion.

This formula assumes flat ground and no air drag. Neither holds perfectly in a real match, but the combined error is small enough that the formula produces estimates within a few metres of what Hawk-Eye measures directly from camera data.

Worked Examples: Exit Velocity to Metres

All calculations use R = v² sin(2θ) / g with g = 9.8 m/s².

• 100m six at 45°: v = √(100 × 9.8) = √980 = 31.3 m/s (≈ 113 km/h exit speed). Check: R = (31.3)² / 9.8 = 979.7 / 9.8 = 99.97m ≈ 100m. Time of flight: T = 2 × 31.3 × 0.7071 / 9.8 = 4.52 seconds. Peak height: y_max = (v sin θ)² / (2g) = (31.3 × 0.7071)² / 19.6 = 489.7 / 19.6 = 25.0m — roughly eight storeys above the pitch.

• Required speed for a 120m six at 45°: R = v² / g → v² = 120 × 9.8 = 1,176 → v = 34.3 m/s (≈ 123 km/h). That is the exit-speed bracket for the biggest IPL maximums on record in the Statsguru database.

• Angle effect at fixed speed (v = 31.3 m/s):

  • At 30°: R = 979.7 × sin(60°) / 9.8 = 979.7 × 0.866 / 9.8 = 86.5m
  • At 45°: R = 979.7 × 1.000 / 9.8 = 100.0m
  • At 60°: R = 979.7 × sin(120°) / 9.8 = 86.5m (same as 30°, confirming the symmetry)

• Minimum exit speed to clear a 70m boundary at 45°: v = √(70 × 9.8) = √686 = 26.2 m/s (≈ 94 km/h).

ICC playing conditions set the boundary distance between 59.4m and 82.9m from the stumps, so a well-timed shot at around 26–28 m/s exit speed is enough to clear a boundary at the shorter end of the permitted range.

How Hawk-Eye Measures a Six in Real Time

The projectile formula is the classroom tool. Broadcasters use Hawk-Eye, a multi-camera tracking system installed at every international and IPL venue.

Standard setup per ground:

• Six high-speed vision-processing cameras positioned at fixed, calibrated locations around the boundary
• Two additional broadcast cameras feeding the main production feed
• On-site processing hardware running the tracking software in real time

When the ball is bowled, all eight cameras track it frame by frame. Hawk-Eye’s software combines the per-camera positions to compute a continuous 3D coordinate for the ball throughout the delivery. The technique is called stereophotogrammetry: using overlapping camera views from known positions to triangulate the exact location of a moving object in three dimensions.

The system divides each delivery into two segments:

1. Delivery to bounce — from the bowler’s release point to where the ball pitches on the surface
2. Bounce to impact — from the pitch point to the bat, pad, or stumps

For a six, the relevant arc begins at bat contact. Hawk-Eye extrapolates the outbound trajectory and calculates the distance from the stumps to wherever the ball lands.

What Hawk-Eye Records and Where It Stops

Here is the detail that broadcast commentary rarely explains. Hawk-Eye measures to the landing point inside the stadium, not to where the ball would land on theoretical flat ground.

If a ball is hit steeply and lands high in the upper deck of a stand 85 metres from the stumps, the graphic shows 85 metres. That same force applied at 45° on flat ground might carry 105 metres by the formula. This is why flat, low sixes often measure longer than steeply struck balls that disappear into tall stands. Trajectory angle determines both the theoretical flat-ground distance and the altitude at which the ball intersects the stadium structure.

Hawk-Eye’s design choice is defensible: the physical landing point is what actually happened, not a counterfactual about infinite flat ground. The trade-off is that distance comparisons across stadiums with stands of different heights are not fully like-for-like.

ESPNcricinfo’s Statsguru records these Hawk-Eye outputs alongside ball-by-ball data. The database enables analysts to rank six-distance across IPL seasons, compare venues, and identify peak-hitting performances for specific batsmen.

Wagon Wheels, Pitch Maps, and the Statsguru Data Layer

Hawk-Eye outputs more than a single distance number. Its analytics products feed the full broadcast data layer:

• Wagon Wheel — a polar plot of every shot’s direction and distance, showing whether a batsman targets long-on, extra cover, or square leg; MS Dhoni’s Wagon Wheel in a final-over chase looks different from a standard innings because of the deliberate targeting of specific fielding gaps
• Pitch Map — a top-down view of every delivery’s landing point on the surface, revealing a bowler’s line-and-length consistency over a spell or a match
• RailCam — an overlay comparing bounce height and speed variation between deliveries from the same or different bowlers, useful for spotting disguised slower balls
• Ball Speed — instantaneous velocity tracked at release, pitch, and impact, enabling broadcasters to compute swing, deceleration, and pace variation within a delivery

All of this feeds into Statsguru’s historical record. The raw pipeline from cameras to derived statistics to searchable database is a real-time data engineering system. During IPL season it processes data from multiple simultaneous matches, with sub-second latency from ball contact to broadcast overlay.

From Ball Tracking to AI Engineering

The worked example above shows that “a 100m six” is just R = v² / g applied to a measured exit velocity of 31.3 m/s. The physics is four lines of algebra. The challenge is the surrounding infrastructure: six calibrated cameras, stereophotogrammetry in real time, a trajectory model operating under broadcast latency, and a database large enough to hold every ball bowled in every IPL match since 2008.

That broadcast graphic traces back to a specific engineering stack: sensor fusion, real-time computation, trajectory modelling, and data pipeline design. It is the same skill cluster that AI and data-engineering roles at sports technology firms and analytics companies in Bengaluru and Hyderabad hire for. The same quantitative reasoning that appears in campus placement aptitude rounds is the mathematical foundation those engineers build on.

TinkerLLM is the ₹299 entry point for building that kind of pipeline from scratch. Its projects involve wiring up real data sources, deploying models, and connecting the pipeline that converts raw sensor input to a human-readable output: the same logic chain as converting Hawk-Eye’s triangulated ball position into the distance graphic on your IPL broadcast, applied to language models and live data feeds instead of cameras and cricket balls.