Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Aug 02, 2018, 11:21 AM (IST)
Edited: Aug 02, 2018, 11:21 AM (IST)
Keaton Jennings had batted resolutely on the first morning for his 42 of the first Test between India and England, at Edgbaston, Birmingham. Then, as Mohammed Shami was about to start the 36th over, Jennings spotted a pigeon (not Glenn McGrath) at short mid-wicket, which seemed to affect his concentration. Jennings tried to shoo it away. When that did not work, captain Joe Root caused much hilarity by running towards it, arms flapping (as Aleem Dar stood expressionlessly at square-leg), but even that did not work.
READ 30 instances of cricket’s bitter-sweet affair with animals
Jennings dragged the next ball on to the stumps. However, when questioned by cricket.com.au after the match, Jennings refused to blame the pigeon: “The best players in the world have those lucky breaks go in their favour, but that’s the way it is. I’ve obviously made an error, misjudged the ball and it’s ended up on my stump. That’s the way it is.
READ Virat Kohli’s send-off to Joe Root, R Ashwin’s web, other talking points from day one at Edgbaston
“Thirty overs before, people were standing up behind the bowler’s arm, so you could say that distracted me as well. You refocus, you go through your own process between each ball. I wouldn’t say it distracted me at all. I suppose it just happens to be the ball before I got out that there’s a huge hoo-ha about a pigeon.”
READ Ben Stokes’ dismissal raises questions
Pigeons have invaded cricket grounds for centuries. There are at least two instances of pigeon deaths during live cricket matches. In both instances, by Tom Hearne (intentionally, playing for Middlesex against Nottinghamshire at Lord’s) and by Jacques Rudolph (playing for Yorkshire against Lancashire at Headingley).
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.