The 'Plumb LBW': Why Some LBW Dismissals Look Obvious But Are Still Reviewed
Why batsmen sometimes review LBW decisions that appear 'plumb out' to casual viewers — the specific DRS elements that can overturn seemingly obvious LBWs (ball pitching outside leg, bat-before-pad contact, umpire's call on stump impact), why a pitch marker makes all the difference, and the statistics on how often 'obvious' LBWs are overturned by DRS.
What Makes an LBW 'Plumb'?
When cricket commentators call an LBW 'plumb' or 'absolutely stone dead,' they typically mean the ball has clearly hit the pad in front of the stumps, appeared to be on the stumps' line, and there is no obvious bat-before-pad contact. To the human eye watching at full speed, the decision looks open and shut: the ball hit the pads, the pads were in front of the stumps, the ball was going to hit the stumps. But DRS reviews on these 'plumb' LBWs reveal they are overturned more often than casual viewers expect — because the three specific LBW elements that DRS assesses (ball pitching outside leg, bat before pad, stump impact zone) each contain elements invisible to the naked eye.
The three DRS checks for LBW: (1) Did the ball pitch outside leg stump? If yes, not out regardless of all other factors. (2) Was there a bat-before-pad contact? UltraEdge and HotSpot check for any ball-bat contact before the pad impact. If yes, not out — the ball hit the bat first, not the pad. (3) Would the ball have hit the stumps? Hawk-Eye's ball-tracking projects the ball's path from the pad-impact point to the stumps. If less than 50% of the ball would have hit the stumps (the 'umpire's call' zone), the original decision stands.
The Pitch Outside Leg Trap
The 'pitching outside leg' rule (ball pitches to the leg-side of leg stump = not out regardless of everything else) is the most commonly surprising DRS finding for casual viewers on 'plumb' LBWs. A delivery that appears to be pitching on middle-and-leg (directly in line with the stumps) and hitting the batsman's pads directly in front of the stumps can sometimes be found by Hawk-Eye to have pitched marginally outside leg stump — by 5-10cm — which triggers the 'pitching outside leg' not-out verdict. This call can look bizarre when the ball has turned significantly after pitching (common with spin bowling) — the ball turns from outside leg toward the stumps and hits the pads, looking very much like a dismissal.
The rationale for the pitching-outside-leg protection: Law 36.1 protects the batsman against deliveries that pitch outside leg because such deliveries are deemed to have passed the 'line of protection' — it was historically considered unfair to dismiss a batsman for a ball that pitched completely to the leg side and then turned dramatically back. The protection dates from eras before reliable pitch-marking technology, when the only ball genuinely threatening the leg stump from pitching outside leg would have been spinning or seaming dramatically.
Umpire's Call and the Marginal Zone
Even when a ball pitches on the stumps' line and hits the pad on the stumps' line, Hawk-Eye may show the ball striking only a fraction of the stumps — 'clipping' the edge of off stump or the outer edge of leg stump. If Hawk-Eye shows the impact with the stumps as less than 50% of the ball's circumference overlapping the stump's edge, the review is 'umpire's call' — the original on-field decision stands (whether that was out or not out). A batsman given out by the umpire who sees a 'clipping' projection on Hawk-Eye cannot get the umpire's 'out' call reversed if it's umpire's call — the technology confirms the margin was within the umpire's judgment zone. The same applies in reverse for batsmen given not out.
Frequently asked questions
Can a fielding team review a not-out LBW decision?
Yes — the fielding team can use a DRS review to challenge a not-out LBW decision, exactly as the batting team can review an out decision. If the bowler or wicket-keeper believes the on-field umpire missed a clear LBW, the fielding captain (after consultation within the 15-second window) can challenge. The same three checks apply: pitch outside leg, ball-bat contact, and stump impact. Fielding-team LBW reviews have similar overturn rates to batting-team reviews — approximately 35-40% of fielding-team challenges result in the on-field 'not out' being overturned to 'out.'
Does the LBW law apply the same way in T20 as in Tests?
Yes — the LBW law (Law 36) is identical across all formats. The same pitching, bat-before-pad, and stump-impact rules apply in a T20I as in a Test match. DRS is also available in T20 internationals (with the same 2 unsuccessful reviews per innings allocation used in Tests). The only significant difference in practice is the playing conditions context: T20 pitches are often flatter (reducing LBW opportunities from seam movement or turn) and batsmen's footwork is more aggressive (moving down the wicket more frequently, potentially reducing LBW opportunities while potentially increasing the risk of stumping).
Is the umpire's call zone the same size for both 'out' and 'not out' decisions?
Yes — umpire's call works identically regardless of the on-field decision direction. If the on-field umpire gave the batsman not out and the fielding team reviews, umpire's call on a marginal stump impact retains 'not out.' If the on-field umpire gave the batsman out and the batting team reviews, umpire's call retains 'out.' The rule is symmetric: marginal decisions, where the technology shows less than 50% stump contact, are returned to the on-field umpire's original verdict regardless of which team initiated the review. This symmetry was controversial at DRS's introduction because it means a batsman who 'should' be out (the ball clips the outside of off stump) might be retained as not out if that's the original decision — but it's a deliberate design choice to preserve on-field umpire authority in the zone of genuine uncertainty.