Key Takeaways
- The incident occurred on October 31, the fifth day of the third Test between South Africa and Australia.
- One of cricket’s most memorable LBW controversies involved Sachin Tendulkar during India’s 1999 Test against Australia at Adelaide Oval.
- The first Ashes Test of 2013 at Trent Bridge provides a particularly relevant precedent.
- The 2019 World Cup final between England and New Zealand offers another important example, although it involved a conventional LBW decision rather than the no-shot exception.
MELBOURNE, Australia, November 1, 2026: Marnus Labuschagne’s controversial-looking LBW dismissal against Kagiso Rabada in the deciding South Africa-Australia Test at Newlands has revived one of cricket’s most misunderstood laws. The Australian batter offered no shot to a delivery outside off stump, watched it jag sharply inward and strike his back pad, and was given out by umpire Richard Kettleborough. Although the impact appeared outside the line of the stumps to the naked eye, Labuschagne’s review failed because ball-tracking showed the delivery would have clipped off stump, preserving the on-field decision under the ICC’s Umpire’s Call protocol.
The dismissal reduced Australia to 5/2 in the opening over of their pursuit of 288, helping trigger a collapse to 111 all out and a 176-run South African victory that secured the series 2-1. But was the decision legally correct, and why can a batter be out when the ball strikes outside off stump? The answer lies in a specific exception within cricket’s LBW law: when a batter makes no genuine attempt to play the ball with the bat, impact outside off stump does not automatically protect them. The incident also raises broader questions about ball-tracking technology, the authority of on-field umpires and how one marginal decision can influence an entire match.
What Happened to Marnus Labuschagne in the Cape Town Test?
The incident occurred on October 31, the fifth day of the third Test between South Africa and Australia.
Story at a glance
What Happened to Marnus Labuschagne in the Cape Town Test?
The incident occurred on October 31, the fifth day of the third Test between South Africa and Australia.
Cricket Law 36 Explained: When Is a Batter Out LBW?
The Laws of Cricket do not say that every delivery striking a batter in front of the stumps results in an LBW dismissal.
The Crucial Difference: Playing a Shot vs Offering No Shot
This is where the law becomes especially important.
What Counts as a Genuine Attempt to Play the Ball?
The umpire must decide whether the batter genuinely attempted to play the delivery with the bat.
What Does Umpire’s Call Mean in an LBW Review?
The Decision Review System separates an LBW decision into several questions.
Australia needed 288 to win the match and take the three-Test series.
Rabada opened the bowling with the new ball on a surface that had already produced substantial seam and spin movement.
Matt Renshaw was dismissed for a duck from the third delivery of the innings, caught behind by Ryan Rickelton.
Labuschagne arrived at No. 3 with Australia already under pressure.
He scored four from his first delivery, an attempted leg-side stroke that resulted in a leading edge passing through the gully region.
He then left the next delivery outside off stump.
At 0.6, Labuschagne again raised his bat and offered no shot.
This time, Rabada’s delivery moved sharply inward from outside off stump and struck his back pad.
Kettleborough upheld South Africa’s appeal.
Labuschagne immediately reviewed the decision.
The review confirmed that the ball would have made marginal contact with off stump, and the original decision remained out.
Australia were 5/2 after one over.
Labuschagne had made four from three balls.
Why Did the Decision Look Questionable?
From the conventional television angle, the delivery appeared to strike the pad outside the line of off stump.
That impression is understandable.
Batters are normally protected against LBW when they play a genuine shot and the ball strikes outside off stump.
But Labuschagne had not attempted a shot.
That changes the relevant legal test.
The television review showed enough projected contact with off stump for the on-field decision to remain in force.
Importantly, the available commentary describes Umpire’s Call on the ball’s projected contact with the wicket. It does not establish that the point of impact on the pad was fully between the stumps.
The distinction is essential to understanding why the decision stood.
Cricket Law 36 Explained: When Is a Batter Out LBW?
The Laws of Cricket do not say that every delivery striking a batter in front of the stumps results in an LBW dismissal.
Several conditions must be satisfied.
Law 36 requires the delivery to be legal, the relevant pitching conditions to be met, the ball to strike the batter’s person without previously touching the bat, the impact to satisfy the applicable rule, and the ball to have been on course to hit the wicket.
The impact condition changes depending on whether the batter made a genuine attempt to play the ball with the bat.
The ICC’s official explanation of Law 36 establishes this distinction.
The Five Main LBW Conditions
| Condition | Legal Requirement | Application at Cape Town |
|---|---|---|
| Fair delivery | The ball must not be a no-ball | No no-ball issue was reported |
| Pitching | If it pitches, the ball must land in line with the stumps or outside off stump | The delivery came from outside off |
| Bat first | The ball must not touch the bat before striking the person | Labuschagne did not make contact with the bat |
| Point of impact | In line, or outside off if no genuine shot was attempted | Labuschagne deliberately left the ball |
| Projected path | The ball must have been on course to hit the wicket | DRS showed marginal contact with off stump |
The pitching requirement still applies when no shot is offered.
A delivery that pitches outside leg stump cannot produce an LBW dismissal under the normal law, even when a batter deliberately leaves it.
Similarly, the no-shot exception does not allow the umpire to dismiss a batter if the ball would have missed the stumps.
The Crucial Difference: Playing a Shot vs Offering No Shot
This is where the law becomes especially important.
Consider two deliveries that strike a right-handed batter outside off stump.
In the first case, the batter attempts a forward defensive stroke, misses the ball and is struck on the pad outside off.
If the umpire considers that a genuine attempt to play the ball was made, the batter is not out LBW because the impact was outside off stump.
In the second case, the batter raises the bat and deliberately allows the delivery to pass.
The ball moves inward and strikes the pad outside off stump.
If the ball otherwise meets the LBW conditions and would have hit the wicket, the batter can be given out.
The difference is the attempt to play the ball.
| Situation | Impact Outside Off | LBW Possible? |
|---|---|---|
| Genuine defensive stroke | Yes | No, if impact is outside off |
| Genuine attacking stroke | Yes | No, if impact is outside off |
| Deliberate leave | Yes | Yes, if all remaining LBW conditions are met |
| No genuine attempt to play | Yes | Yes, subject to the other conditions |
| Ball pitches outside leg | Any | No |
| Ball projected to miss stumps | Any | No |
| Bat makes contact before pad | Any | No LBW |
Why Does the No-Shot Exception Exist?
The provision prevents batters from deliberately using their pads as protection against deliveries that threaten the wicket.
Without it, a batter could repeatedly leave balls moving toward off stump while relying on the point of impact outside the stump line.
That would weaken the balance between batting and bowling.
The exception preserves the bowler’s opportunity to earn an LBW dismissal when a batter chooses not to attempt a stroke.
However, it does not make leaving the ball an offense.
Batters are perfectly entitled to leave deliveries.
The risk arises only when the ball strikes their person and satisfies the remaining conditions of Law 36.
What Counts as a Genuine Attempt to Play the Ball?
The umpire must decide whether the batter genuinely attempted to play the delivery with the bat.
This is not necessarily determined by whether the bat moved.
For example, a batter might make a late movement that appears defensive but does not genuinely attempt to contact the ball.
Conversely, an awkward or unsuccessful defensive movement may still constitute a genuine attempt.
The assessment depends on the actual action rather than a batter’s claim about their intention.
In Labuschagne’s case, the situation was relatively clear.
He raised the bat and shouldered arms.
There was no meaningful attempt to strike or defend the delivery.
That allowed the no-shot provision to apply.
What Does Umpire’s Call Mean in an LBW Review?
The Decision Review System separates an LBW decision into several questions.
Was the delivery legal?
Did the ball touch the bat?
Where did the ball pitch?
Where did it first strike the batter?
And would it have hit the wicket?
Ball-tracking technology estimates the trajectory of the ball using available camera information.
But the review protocol recognizes marginal cases in which the technology does not provide grounds to reverse the on-field umpire.
That is the purpose of Umpire’s Call.
The ICC’s official DRS protocol explains the treatment of marginal decisions involving impact and projected contact with the wicket.
Why Does an On-Field Out Decision Sometimes Stay Out?
When a delivery is projected to make marginal contact with the stumps, the technology can return Umpire’s Call.
If the original decision was out, it remains out.
If the original decision was not out, the same marginal projected contact may allow that decision to remain not out.
That does not mean the laws are different for different batters.
It means the review system preserves the on-field decision when the available evidence falls within a defined marginal category.
Only sufficiently conclusive evidence permits the technology to overturn the original decision.
Why Labuschagne’s Review Failed
Labuschagne was originally given out.
The review established that the delivery would have clipped off stump.
The projected wicket contact fell within the Umpire’s Call threshold.
Consequently, the third umpire did not reverse Kettleborough’s decision.
The replay did not need to demonstrate that the ball would have crashed into the middle of off stump.
Marginal contact was enough to preserve the original out decision.
DRS and the Naked Eye: Why Can They Appear to Disagree?
Television viewers usually observe an LBW appeal from one or two camera angles before ball-tracking appears.
Those angles are useful but do not reproduce the umpire’s exact viewpoint or the three-dimensional movement of the delivery.
A ball can appear outside the line of the stumps when viewed from a camera positioned away from the precise wicket-to-wicket axis.
Seam movement, swing and the angle of the batter’s body can complicate the visual impression.
Ball-tracking attempts to reconstruct the delivery’s path.
However, a projection is not the same thing as observing the ball physically strike the stumps.
The technology estimates what would have happened if the pad had not intercepted the delivery.
That is why the ICC maintains defined review categories for marginal contact.
| Review Element | What It Establishes | Important Limitation |
|---|---|---|
| Front-foot replay | Whether the bowler delivered a legal ball | Camera interpretation may be necessary |
| Edge-detection technology | Evidence of contact involving bat and ball | Must be interpreted with images and timing |
| Pitching projection | Where the delivery pitched | Subject to the defined review protocol |
| Impact tracking | Where the ball first struck the batter | Marginal boundary cases are treated separately |
| Wicket projection | Whether the ball would have hit the wicket | It is a calculated continuation of the trajectory |
| Umpire’s Call | Preserves the original decision in defined marginal cases | Does not imply absolute certainty |
How Labuschagne’s Dismissal Helped Decide the Cape Town Test
The broader match situation made the dismissal especially damaging.
Australia entered the final day needing 288 to win the Test and claim the series.
South Africa had already recovered from a 100-run first-innings deficit, thanks largely to centuries from Ryan Rickelton and Wiaan Mulder.
The Sports Encounter examined that extraordinary recovery in its report on the decisive fourth day at Newlands.
Australia needed a solid start to the chase.
Instead, Rabada dismissed Renshaw and Labuschagne in the opening over.
Travis Head subsequently fell, leaving Australia 22/3.
Josh Inglis was run out for four.
Simon Harmer then removed Alex Carey and Cooper Connolly, and Australia collapsed to 42/6.
The innings eventually ended at 111.
South Africa won by 176 runs and claimed the three-Test series 2-1.
Was Labuschagne’s Dismissal the Single Decisive Moment?
It was an important early blow, but it would be misleading to present it as the sole reason Australia lost.
The tourists also lost nine other wickets.
Rabada’s three early breakthroughs created the collapse, while Harmer completed the destruction with six wickets for only 16 runs.
Australia’s batting problems had also appeared during the previous Test in Gqeberha.
Nevertheless, Labuschagne’s dismissal materially intensified the pressure.
At 5/2, Australia had lost two established top-order batters before completing the opening over.
The remaining players were forced to rebuild rather than construct a planned chase.
The dismissal therefore changed the competitive situation even though the result cannot be attributed to that delivery alone.
What Former Cricketers and Analysts Said About Australia’s Collapse
Former Australia opener David Warner delivered a severe assessment of the team’s batting after the final-innings collapse.
Speaking during post-match coverage, Warner described aspects of Australia’s performance as deplorable and criticized the manner in which the batters were getting dismissed.
His frustration was directed at the wider batting failure rather than presented as a formal allegation that Labuschagne had been incorrectly given out.
That distinction is important.
The available reporting does not establish that Warner publicly disputed the legal application of the no-shot LBW provision in this specific incident.
Graeme Smith Questions Australia’s Decision-Making
Former South Africa captain Graeme Smith criticized Cameron Green’s calling after Josh Inglis was run out.
Smith’s assessment reflected the broader problems with Australia’s decision-making under pressure.
Although his comments concerned a run-out rather than Labuschagne’s LBW, they reinforced the conclusion that Australia contributed to its own collapse through poor judgments.
How Match Analysts Viewed the Labuschagne Leave
Contemporary reporting described the dismissal as a serious error of judgment by a batter already under considerable selection pressure.
Commentators noted that Rabada’s delivery moved sharply back after pitching outside off stump.
Labuschagne had committed to the leave and could not recover when the ball struck his pad.
The review then confirmed marginal projected contact with off stump.
The available evidence therefore supports criticism of the batting judgment more strongly than claims of an obvious umpiring error.
Pat Cummins Acknowledges Australia Lost the Key Moments
Australia captain Pat Cummins accepted after the Test that South Africa had performed better during the decisive passages.
His assessment was broader than one LBW decision.
Australia had taken a 100-run first-innings lead but could not prevent South Africa’s second-innings recovery.
The tourists then failed to build meaningful partnerships during the chase.
The captain’s response highlights why responsible match analysis must distinguish between one marginal decision and the full sequence that determines a Test result.
Historic Example 1: Sachin Tendulkar’s Controversial LBW Against Glenn McGrath, Adelaide 1999
One of cricket’s most memorable LBW controversies involved Sachin Tendulkar during India’s 1999 Test against Australia at Adelaide Oval.
Tendulkar attempted to duck beneath a short delivery from Glenn McGrath.
Instead, the ball stayed relatively low and struck him high on the body.
Umpire Daryl Harper gave him out LBW.
The decision caused enormous controversy because Tendulkar appeared to be avoiding the delivery rather than attempting a conventional batting stroke.
The central questions concerned the ball’s projected height and whether it would have struck the wicket.
This was not identical to Labuschagne’s conventional shoulder-arms leave.
It did, however, illustrate how the absence of a batting stroke can coincide with a difficult LBW judgment.
Did the Decision Affect the Result?
India were chasing 396.
Tendulkar’s dismissal contributed to a fourth-day collapse that left India at 76/5.
Australia eventually won by 285 runs.
The decision was consequential because it removed India’s captain during a demanding chase.
However, the final margin was substantial, and it cannot be established that India would have won if Tendulkar had survived.
The defensible conclusion is that a controversial LBW contributed to a decisive batting collapse, not that the decision alone determined the result.
Historic Example 2: Stuart Broad’s No-Shot LBW Appeal in the 2013 Ashes
The first Ashes Test of 2013 at Trent Bridge provides a particularly relevant precedent.
England won the match by just 14 runs.
The contest featured several contentious umpiring decisions and intense debate about the use of DRS.
Among the incidents subsequently assessed by the ICC was an LBW appeal against Stuart Broad when he offered no shot.
Australia could not challenge that decision because its reviews had already been exhausted.
The ICC later acknowledged that the Trent Bridge Test included decisions that could not be corrected because reviews were unavailable.
That observation is important because the review system cannot eliminate an error if the affected team has no reviews remaining.
Why the 14-Run Margin Matters
England’s 14-run victory made every disputed decision potentially consequential.
A different ruling could have changed the number of deliveries remaining, the batting partnership and the runs available to the lower order.
But it would still be inappropriate to claim that overturning one decision would automatically have produced an Australian victory.
The match included numerous pivotal moments.
The case is best understood as an example of how review availability and umpiring decisions can interact in an exceptionally close result.
The ICC’s published assessment of umpiring in the Trent Bridge Test remains an unusually valuable primary-source record of the debate.
Historic Example 3: Ross Taylor’s LBW in the 2019 Cricket World Cup Final
The 2019 World Cup final between England and New Zealand offers another important example, although it involved a conventional LBW decision rather than the no-shot exception.
Ross Taylor was given out LBW to Mark Wood for 15.
New Zealand had already exhausted its review and could not challenge the decision.
Television replays subsequently raised questions about whether the delivery would have passed over the stumps.
Taylor’s dismissal left New Zealand 141/4 during its innings.
The team eventually reached 241/8.
England also scored 241, and the Super Over was tied before England secured the championship under the boundary-count regulation then in force.
Why This Decision Was Particularly Significant
Unlike the 1999 Adelaide Test, the 2019 final finished level on runs after both the regulation match and Super Over.
Any additional run at various stages could have changed the championship outcome.
That gives the Taylor decision exceptional counterfactual importance.
However, it does not establish how many runs he would have scored had the decision been reversed.
Nor does it establish that New Zealand would necessarily have won.
The value of the example lies in illustrating how a marginal decision involving an established batter can become magnified when a major final is decided by the smallest possible margin.
For broader historical context on close ODI results and controversial turning points, explore The Sports Encounter’s A Celebration of 5000 ODIs series.
Historic Example 4: Shane Watson’s Repeated LBW Reviews in the Ashes
Former Australia all-rounder Shane Watson became closely associated with unsuccessful LBW reviews during his Test career.
The issue received particular attention during Ashes contests against England.
At Trent Bridge in 2013, Watson was dismissed LBW to Stuart Broad for 46.
Ball-tracking showed the delivery making marginal contact with leg stump, so the original decision remained in place.
Watson’s repeated unsuccessful reviews became a recurring talking point.
But his experiences also demonstrate a genuine difficulty in cricket.
Batters do not have access to real-time ball-tracking information when deciding whether to review.
They must assess pitching, impact, bat contact and projected trajectory from their own viewpoint, often under considerable pressure.
Even an experienced international batter can misjudge one of those elements.
Four Historical Cases: What Was Actually at Stake?
| Match | Incident | Final Result | What Can Be Concluded? |
|---|---|---|---|
| Australia vs India, Adelaide 1999 | Tendulkar’s high-impact LBW while ducking McGrath | Australia won by 285 runs | Controversial dismissal contributed to a collapse |
| England vs Australia, Trent Bridge 2013 | Broad no-shot LBW appeal among disputed decisions | England won by 14 runs | Unreviewable decisions mattered in an extremely close match |
| England vs New Zealand, Lord’s 2019 | Ross Taylor LBW without a review available | Scores tied; England won on boundary count | A decision acquired exceptional significance in a tied final |
| South Africa vs Australia, Cape Town 2026 | Labuschagne no-shot LBW upheld on Umpire’s Call | South Africa won by 176 runs | Early wicket intensified a decisive batting collapse |
These cases are not legally identical.
They cover different LBW circumstances and different eras of review technology.
What connects them is the importance of umpiring judgment when a delivery produces uncertainty and the consequences can extend far beyond a single wicket.
Does Umpire’s Call Protect Bad Decisions?
This question has been debated repeatedly since ball-tracking became central to international cricket.
Critics argue that once technology is available, it should determine the decision without preserving the original judgment.
Supporters argue that a projected trajectory is not perfectly certain and that marginal cases should not be treated as conclusive grounds to overturn the umpire.
Both perspectives address a legitimate concern.
One prioritizes consistency in applying available data.
The other prioritizes caution when technology indicates only marginal contact.
The Case for Retaining Umpire’s Call
Supporters argue that the system preserves a meaningful role for on-field umpires.
It also recognizes that ball-tracking relies on reconstruction and prediction rather than direct observation of the ball hitting the stumps.
Under this interpretation, a review should correct sufficiently clear errors rather than replace every close judgment.
The Case for Removing Umpire’s Call
Critics question why the same projected trajectory can allow different original decisions to remain in force.
They argue that using a consistent technological threshold could make decisions easier for supporters to understand.
However, removing Umpire’s Call would not automatically eliminate uncertainty.
It would require governing bodies to choose a new definitive boundary for what counts as out.
Marginal cases would then be judged against that new threshold.
The underlying problem of how to handle uncertain evidence would remain.
Should the No-Shot LBW Rule Be Changed?
Labuschagne’s dismissal may encourage debate about whether batters should be protected when the ball strikes outside off stump, regardless of whether they play a shot.
However, removing the no-shot exception would create a different competitive imbalance.
Batters could deliberately use their pads against deliveries moving toward the wicket while avoiding the risk associated with playing the ball.
That would reduce the bowler’s opportunities and could encourage defensive tactics based on deliberate pad interception.
The present law therefore has a clear cricketing purpose.
The stronger subject for debate is not necessarily the existence of the no-shot provision but how the review system evaluates its application.
The two issues should not be confused.
Why Good Batters Still Misjudge the Leave
Leaving the ball is one of Test cricket’s most important defensive skills.
On surfaces offering movement, batters must repeatedly decide whether a delivery threatens the stumps.
The decision is made in a fraction of a second.
A batter studies the bowler’s release position, seam alignment, length and initial trajectory.
But the ball can move after pitching in ways that defeat the initial judgment.
Rabada’s delivery to Labuschagne demonstrated that problem.
The ball appeared sufficiently wide for a leave, but its inward movement transformed the situation.
Labuschagne had already committed to not playing.
Once struck on the pad, he could no longer rely on the normal outside-off impact protection.
How a Bowler Can Use the No-Shot Rule Tactically
A skilled fast bowler can exploit a batter’s established leaving pattern.
Deliveries outside off stump encourage the batter to identify balls that can safely pass.
However, if the bowler can produce late inward movement from a similar initial line, the batter’s judgment becomes more difficult.
Rabada’s delivery was effective precisely because it challenged that judgment.
The dismissal therefore involved both high-quality bowling and a costly batting decision.
It should not be reduced to a discussion of technology alone.
How South Africa Used Pressure to Dismantle Australia
Labuschagne’s dismissal formed part of a broader pattern throughout the series.
Australia had begun the tour strongly in Durban, where Matt Renshaw’s batting played an essential role in the opening victory.
The Sports Encounter documented those innings in its report on Australia’s first-Test triumph.
At Gqeberha, the momentum changed dramatically.
South Africa recovered through Temba Bavuma’s 179 and a series of important lower-order partnerships.
The hosts then dismissed Australia for 99 in its first innings.
That collapse was examined in our detailed analysis of Marco Jansen’s five-wicket performance.
South Africa completed an innings victory to level the series.
At Cape Town, Australia again appeared to have a strong position after establishing a 100-run first-innings lead.
But Rickelton and Mulder added 154 for the sixth wicket during South Africa’s second innings.
The target increased to 288.
Rabada then exploited the new ball, and Harmer dominated the final innings.
The Proteas’ repeated ability to recover from difficult positions was an important characteristic of the series.
The Psychological Importance of an Early LBW Decision
An early wicket changes more than the scoreboard.
It alters the responsibilities of the incoming batter.
It can interrupt the batting team’s planned approach and strengthen the bowling side’s confidence.
In Cape Town, Australia’s opening over provided an extreme example.
Renshaw was dismissed before scoring.
Labuschagne survived only three balls.
Australia were two down before completing the first over of a difficult chase.
The remaining batters entered knowing that South Africa had already established a major advantage.
But psychological impact is difficult to measure directly.
It should be described as an analytical interpretation rather than an independently proven numerical effect.
In this case, the subsequent scoreboard provides strong evidence that Australia failed to recover.
How the Same Decision Could Affect a Close Test or a World Cup Final
Consider a hypothetical Test match in which a team needs 20 runs to win with two wickets remaining.
An LBW dismissal upheld by Umpire’s Call could end the chase immediately.
If the same marginal delivery had originally been given not out, the batter might have survived the review.
The result would then depend on subsequent deliveries.
That demonstrates why the original on-field judgment can be especially significant in close contests.
However, the hypothetical example does not establish that either decision would be legally incorrect.
It illustrates the operation of the current review protocol.
Actual historical matches such as the 2013 Trent Bridge Test and 2019 World Cup final show why close finishes intensify scrutiny of marginal decisions.
Five Questions Every Viewer Should Ask Before Criticizing an LBW Decision
| Question | Why It Matters | Common Misunderstanding |
|---|---|---|
| Did the batter attempt a genuine shot? | Determines the outside-off impact exception | Assuming impact outside off always means not out |
| Where did the ball pitch? | Outside-leg pitching prevents LBW | Confusing pitching with pad impact |
| Did the ball touch the bat first? | Prior bat contact prevents LBW | Judging only from the pad impact |
| Would the ball have hit the stumps? | Required for every LBW dismissal | Assuming a no-shot leave automatically means out |
| What was the original decision? | Determines what happens in marginal Umpire’s Call cases | Assuming technology always replaces the umpire |
Continue the Cricket Story
Frequently Asked Questions About the No-Shot LBW Rule
Can a Batter Be Out LBW if the Ball Hits Outside Off Stump?
Yes, if the batter made no genuine attempt to play the delivery with the bat and all the remaining LBW conditions are satisfied.
Can a Batter Be Out LBW if the Ball Pitches Outside Leg Stump?
No. A delivery pitching outside leg stump cannot result in LBW under the normal law, regardless of whether the batter plays a shot.
Why Was Marnus Labuschagne Given Out?
He offered no shot to a Rabada delivery that moved inward and struck his pad. The umpire gave him out, and DRS showed marginal projected contact with off stump, preserving the original ruling.
Was Labuschagne’s LBW Decision Incorrect?
The available review evidence does not establish an incorrect application of the law. The no-shot exception applied, and the projected wicket contact was sufficient for the original decision to stand under Umpire’s Call.
What Does Umpire’s Call Mean?
It is a defined DRS outcome for certain marginal impact or wicket-contact projections, in which the original on-field decision remains unchanged.
Can the Same Ball Be Out or Not Out Depending on the On-Field Decision?
Under the current review protocol, the same marginal projected contact can allow either original decision to stand, provided the remaining conditions are satisfied.
Does No Shot Mean Automatic LBW?
No. The ball must still meet the other requirements, including legal delivery, permitted pitching and projected contact with the wicket.
Who Dismissed Labuschagne at Cape Town?
Kagiso Rabada dismissed him LBW for four during Australia’s second innings.
Who Was the On-Field Umpire?
Richard Kettleborough gave the original out decision.
What Was Australia’s Score After the Dismissal?
Australia were 5/2 after the opening over.
Who Won the Cape Town Test?
South Africa defeated Australia by 176 runs and won the three-match series 2-1.
Did the LBW Decision Alone Cause Australia’s Defeat?
No. The dismissal contributed to an early collapse, but South Africa’s other nine wickets, Rabada’s opening spell and Harmer’s six-wicket performance were also decisive.
The Sports Encounter Verdict: The Law Was Clear, but the Debate Is Bigger Than One Wicket
Marnus Labuschagne’s dismissal at Cape Town looked controversial because of the distance between what viewers appeared to see and what the review ultimately showed.
The ball struck him after he had shouldered arms outside off stump.
That was the defining decision he made.
By choosing not to play, Labuschagne surrendered the ordinary protection available to a batter whose genuine stroke is beaten outside off stump.
The delivery still needed to be on course to hit the wicket.
The review showed marginal contact with off stump, which was enough to preserve the original out decision.
There is therefore no sound basis for describing the dismissal as a clear violation of Law 36.
But the incident opens a legitimate broader discussion.
How much authority should the on-field umpire retain when technology indicates a marginal result?
Should projected contact with the stumps always be judged by a single technological threshold?
And how should cricket communicate the difference between impact outside off stump and the projected path of the ball?
These questions deserve informed debate rather than instant accusations of bias or incompetence.
History demonstrates why the stakes can be enormous.
Controversial dismissals have occurred during Test collapses, closely contested Ashes matches and World Cup finals.
Yet responsible analysis must distinguish between a decision that contributed to a result and a claim that reversing it would necessarily have changed the winner.
At Newlands, Australia’s problems were far larger than one LBW.
The tourists had taken a 100-run first-innings lead but failed to protect it.
They then lost their top order almost immediately and collapsed to 111.
South Africa’s bowlers deserved credit for creating and exploiting that pressure.
Labuschagne’s dismissal was one important moment in the sequence.
It also offered an exceptionally clear example of a rule that many cricket followers misunderstand.
The lesson is straightforward.
Impact outside off stump does not always save the batter.
No genuine shot removes that particular protection, while the requirement that the delivery would hit the wicket remains.
And when a review produces Umpire’s Call, the original judgment can become one of the most influential decisions in the match.
For a wider understanding of the South Africa-Australia rivalry, revisit our analysis of aggression and competitive discipline in the series, Bavuma’s remarkable Gqeberha century, and the full second-Test victory report.
The transformation of the series was also documented in our opening-day Durban report, Renshaw’s extraordinary first-Test innings, and Jansen’s decisive bowling at Gqeberha.
