VIDEO: Steve O’Keefe caught in absurd run out during Sheffield Shield match
VIDEO: Steve O’Keefe caught in absurd run out during Sheffield Shield match
O'Keefe, who had injured his hamstring during the match, was the last man to bat and entered the field with a runner.
Written by Cricket Country Staff Published: Mar 13, 2019, 04:14 PM (IST) Edited: Mar 13, 2019, 04:14 PM (IST)
O’Keefe forgot he had a runner and played his first ball from Scott Boland towards mid-on and went for the run after calling Peter Nevill – at the non-striker’s end – for a single.
During a Sheffield Shield match between Victoria and New South Wales on Wednesday, Steve O’Keefe became the latest victim of a dramatic dismissal. The NSW spinner, who had injured his hamstring during the match, was the last man to bat and entered the field with a runner.
O’Keefe forgot he had a runner and played his first ball from Scott Boland towards mid-on and went for the run after calling Peter Nevill – at the non-striker’s end – for a single. Nevill obliged, but O’ Keefe and his runner Nick Larkin both ran to complete the single.
When Jon Holland, the fielder, stopped the ball, Nevill had safely made his ground, but Larkin and O’Keefe were ball watching.
In a dramatic sequence of events, both Larkin and O’ Keefe ran for the single and ended up at the bowler’s end. Realising his mistake, O’Keefe immediately made a dash to the striker’s end, but it was too late as Holland threw the ball to wicketkeeper Seb Gotch, who dislodged the bails with O’Keefe stranded.
“His hamstring can’t be that bad as well,” the commentator said. “Because if it was that bad you’d know as soon as you took off that you shouldn’t be running.”
TRENDING NOW
Neville’s unbeaten 33 helped NSW move past Victoria’s first-innings total of 106.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.