Abhishek Mukherjee
Abhishek Mukherjee is the Chief Editor at CricketCountry. He blogs at ovshake dot blogspot dot com and can be followed on Twitter @ovshake42.
Written by Abhishek Mukherjee
Published: Feb 16, 2018, 10:39 AM (IST)
Edited: Feb 16, 2018, 10:39 AM (IST)
On August 22, 1950, Alec Coxon bowled two consecutive overs in an innings from the same end of a First-Class match with consent from the umpires. Abhishek Mukherjee narrates how.
Bowling consecutive overs is not unheard of. It has happened twice in Tests since 1889 — by Warwick Armstrong at Old Trafford in 1921 and by Alex Moir at Wellington in 1950-51. However, both instances involved umpiring errors, for both men bowled their overs on each side of an interval, and the men in white coats had overlooked the anomaly.
But even they were not the first to do this. Bowling consecutive overs was legal till 1889. Law 14 of the 1884 Code clearly stated “the bowler may not change ends more than twice in the same innings, nor bowl more than two overs in succession.”
Legendary cricket statistician Charles Davis notes that there have been ‘at least two dozen such instances” in Test cricket. This included Allen Hill in the first ever Test and Fred Spofforth in both innings of the 1882 Test that gave birth to the Ashes.
That changed in 1889. As per Law 14: “The bowler shall be allowed to change ends as often as he pleases, provided only that he does not bowl two overs consecutively in one innings.”
However, in all these instances, before 1889 or otherwise, whenever the bowlers had bowled consecutive overs legally, they had bowled from different ends. Even Armstrong did the same, though data for Moir is not available.
However, there was an additional condition, that of incomplete overs: if a bowler could not finish an over (a not-too-rare occurrence) the over would be considered ‘complete’ and a fresh over would begin at the other end.
The match
Let me guide through the contest first, for it was a close one. Sussex secured a 107-run lead before Johnny Wardle and Norman Yardley bowled them out for 151. Then Len Hutton took over and sculpted 71 in a way only he could.
However, a mini-collapse saw Yardley out in the middle at 118 for 4. He helped Willie Watson add 65 for the fifth wicket. Watson carried on, losing Alec Coxon and Wardle, but Eddie Leadbeater stayed put. The pair added an unbeaten 40 for the eighth wicket to seal a win.
Watson remained unbeaten on 96 — but then he knew a thing or two about competitive sport. He had returned from the FIFA World Cup in Brazil the month before.
The incident
Readers must have guessed what had happened by now. Coxon opened bowling in the Sussex second innings with John Whitehead. Then Whitehead injured himself as he ran in to bowl the first ball of an over. It was evident that he would not be able to bowl, at least at that point.
Obviously someone else had to bowl — but from which end? Umpires Bill Ashdown and John Bell conferred before deciding that the ball, despite not being delivered, was “in play” the moment Whitehead had begun his run-up.
That also meant that the over had commenced. And since Whitehead would be unable to finish the over, someone else would have to bowl from the other end.
And Coxon created history.
The amendment
Surprisingly, the law stayed till the 1980 Code. Law 22 of the new code stated: “If, for any reason, a Bowler is incapacitated while running up to bowl the first ball of an over, or is incapacitated or suspended during an over, the Umpire shall call and signal ‘dead ball’ and another Bowler shall be allowed to bowl or complete the over from the same end, provided only that he shall not bowl two overs, or part thereof, consecutively in one innings.”
That is the way things stand now.
Brief scores:
Sussex 290 (George Cox 143; Alec Coxon 3 for 49) and 151 (Norman Yardley 3 for 41, Johnny Wardle 5 for 23) lost to Yorkshire 183 (Vic Wilson 61; Jim Cornford 4 for 49, Charles Oakes 4 for 54) and 262 for 7 (Len Hutton 71, Willie Watson 96*; Ted James 3 for 86) by 3 wickets.
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 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.