Ben Stokes: Police reveal man in Bristol street fight suffered fractured eye socket as case passed to prosecutors

The case has been referred to the Crown Prosecution Service who will advise whether any charges should be brought against the cricketer over the incident

Lawrence Ostlere
Wednesday 29 November 2017 16:25 GMT
Comments
Ben Stokes touched down at Christchurch Airport on Wednesday morning
Ben Stokes touched down at Christchurch Airport on Wednesday morning (Getty)

Police have revealed that a man involved in the street fight which has kept Ben Stokes out of contention for England's Ashes series suffered a fractured eye socket as they passed the case on to the Crown Prosecution Service.

The investigation into the brawl in Bristol in September has now been concluded and referred to the CPS, leaving Stokes closer to finding out if he will be charged.

Stokes is currently in New Zealand where he is expected to begin playing for Canterbury in an effort to regain match sharpness and acclimatise, so he will be ready should he be called upon to play by England in any of the remaining four Tests.

For that to happen he would need exonerating by police, and by the England and Wales Cricket Board who are likely to carry out a subsequent internal investigation.

"We're now in a position to provide an update on our investigation," read a statement from Avon & Somerset Police. "A 27-year-old man suffered a fractured eye socket in the incident on Queens Road, Clifton.

"A 26-year-old man was arrested on suspicion of causing actual bodily harm and was later released under investigation. Three other men, aged 26, 27, and 28 have all voluntarily attended police stations for interview.

"Today (29/11) we have passed a file to the Crown Prosecution Service and are now seeking charging advice."

Join our commenting forum

Join thought-provoking conversations, follow other Independent readers and see their replies

Comments

Thank you for registering

Please refresh the page or navigate to another page on the site to be automatically logged inPlease refresh your browser to be logged in