David Miller’s delayed review: South African batsman’s delayed review has created a state of tumult in the cricketing world.
Advertisement
During the third ODI of the ongoing South Africa’s tour of Australia at Hobart, umpire Aleem Dar’s decision of allowing South African middle-order batsman David Miller to review his decision has created a state of tumult and confusion in the cricketing world.
It happened on the fourth delivery of the 34th over when Australian all-rounder Glenn Maxwell pinned Miller (40) in front of the stumps. Once umpire Dar ruled the batsmen out, South Africa’s captain Faf du Plessis, who was at the non-striker’s end, signaled for a review only after significant deliberation with Miller.
Advertisement
The replays confirmed the ball the angle of the bowler would have taken the ball outside the leg stump. Therefore, the decision was reversed.
It is worth mentioning that there was nothing wrong in the final decision which was taken. It was just that the by the time du Plessis signaled for the review, 19 seconds had passed. A batsman is allowed only 15 seconds to signal for the review in such situations.
The ICC playing conditions for ODIs state that only the batsman dismissed can request for a review. “Only the batsman involved in a dismissal may request a Player Review of an Out decision and only the captain (or acting captain) of the fielding team may request a Player Review of a Not-out decision.”
In Miller’s case, it was du Plessis who asked for the review initially, another uncertainty over the decision made by the umpire.
With the decision going in the visitors’ favor, the duo ended up stitching a 252-run stand for the fourth wicket. Recovering from 55-3, the Proteas ended up scoring 320-5 in 50 overs on the back of ODI centuries from Miller (139) and du Plessis (125).
Advertisement
Restricting Australia to 280-9 in 50 overs, South Africa won the match by 40 runs and the series by a 2-1 margin. Miller was adjourned as the ‘Man of the Match’ and ‘Man of the Series’.
Watch the full video below:
Read some of the latest Twitter reactions on the match below: