Billingham pub closed as man charged with rape
Summarised from 2 outlets · Updated 11 Nov, 17:01 · Archive
A man has been charged with rape following an arrest at a Billingham pub, which has been temporarily closed.
A Billingham pub has been temporarily closed following a rape allegation. Zack Briggs, 25, of Throston Grange Lane, Hartlepool, was arrested at The Swan on Wolviston Road on Friday, 6 November, after police were called to the premises. He was charged with rape and appeared before Teesside Magistrates' Court on Monday, 9 November.
Briggs was remanded in custody. His case has been sent to Teesside Crown Court, where he is due to appear on 12 November. A plea and trial preparation hearing has been scheduled for 9 December. The court will consider a bail application on 12 November.
A second man, aged 24, was arrested on Tuesday, 10 November, on suspicion of sexual assault in connection with a separate reported incident. He has been released on police bail while investigations continue. Stonegate Pub Partners, which operates The Swan, said the pub would remain closed while investigations continue and confirmed it is cooperating with the relevant authorities. Anyone with information is asked to call 101 quoting reference 222160.
How it is being reported
- North East pub temporarily closed in rape probe as man appears in courtA Billingham pub has been temporarily shut down amid an investigation into an alleged rape.The Northern Echo · 11 Nov, 16:24
- Rape allegation 'temporarily closes' Billingham pub as police launch probe and charge suspectPolice arrested a man at The Swan, in Wolviston Road, Billingham :: He was charged with rape and appeared before Teesside Magistrates' CourtTeessideLive · 11 Nov, 13:43
In this story: Zack Briggs · The Swan · Billingham · Teesside Magistrates' Court · Teesside Crown Court · Hartlepool · Cleveland Police · Stonegate Pub Partners
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)