Stay up to date with notifications from The Independent

Notifications can be managed in browser preferences.

Ferguson riots: 'I didn't foresee an evening like this': Why was jury decision announced at 8pm?

Speculation ranges from police wanting to let people get home from work - to maximising their own overtime pay

Adam Withnall
Tuesday 25 November 2014 09:42 GMT
Comments
A car burns on the street after a grand jury returned no indictment in the shooting of Michael Brown
A car burns on the street after a grand jury returned no indictment in the shooting of Michael Brown (REUTERS)

The decision not to indict the police officer who killed Michael Brown has resulted in an almost immediate flare-up of violent protests, prompting the question – why was it announced at 8pm?

The grand jury in Clayton, Missouri had reached a decision some hours earlier, but Prosecutor Bob McCulloch called a press conference to announce the verdict only once night had fallen.

Early guidance from McCulloch’s office suggested the decision would be revealed “after rush hour”, and many have suggested that 8pm was chosen to give people time to get home safely.

Belmar said the riots were “probably much worse than the worst night we ever had in August” after Brown was killed, adding: “I didn’t foresee an evening like this.”

Many will accuse him and McCulloch of being shortsighted – and searched for ulterior motives for the 8pm announcement timing. Some suggested police “wanted civil unrest to occur”.

Perhaps even more cynically, Miami Herald writer Joseph Goodman asked: “I wonder how much more overtime the cops make in St Louis for an announcement at night compared to during the day?”

Meanwhile, the riots continue and the National Guard in Ferguson have deployed tear gas and rubber bullets.

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