Stay up to date with notifications from The Independent

Notifications can be managed in browser preferences.

Astroworld: Event staff told to refer to dead concertgoers as ‘Smurfs’

Festival’s emergency response plan told staff to ‘never use the term dead or deceased over the radio’

Bevan Hurley
Tuesday 09 November 2021 15:53 EST
Comments
Who is to blame for Astroworld tragedy?

Your support helps us to tell the story

From reproductive rights to climate change to Big Tech, The Independent is on the ground when the story is developing. Whether it's investigating the financials of Elon Musk's pro-Trump PAC or producing our latest documentary, 'The A Word', which shines a light on the American women fighting for reproductive rights, we know how important it is to parse out the facts from the messaging.

At such a critical moment in US history, we need reporters on the ground. Your donation allows us to keep sending journalists to speak to both sides of the story.

The Independent is trusted by Americans across the entire political spectrum. And unlike many other quality news outlets, we choose not to lock Americans out of our reporting and analysis with paywalls. We believe quality journalism should be available to everyone, paid for by those who can afford it.

Your support makes all the difference.

Astroworld Festival staff were instructed to refer to dead concertgoers as ‘Smurfs’ in the event of a fatality, according to a leaked safety and emergency response plan.

The 55-page document, obtained by CNN, informs staff how to respond to robberies, active shooters, extreme weather, terror threats and other hazardous scenarios.

Under a section headed ‘traumatic injury resulting in death’, the event plan instructed staff to notify supervisors of a fatality using the codeword ‘Smurf’.

“Never use the term “dead” or “deceased” over the radio,” the manual states.

Eight people died and hundreds more were injured when a deadly crowd surge occurred as festival founder and headline act Travis Scott performed just after 9pm on Friday night.

Concertgoers were trampled on and crushed during the surge, while others passed out and only survived after being lifted over the crowd.

Staff hired to work security at the festival have spoken of a chaotic and dysfunctional event, with many turning up on the morning of the festival without receiving any training.

The document, titled Astroworld’s 2021 Event Operations Plan and written by Texas concert promoter Scoremore, contains detailed advice for severe weather events such as tornadoes, high heat and winds.

It contains separate sections on how to handle wind speeds of 25mph, 30mph, 35mph, and 40mph, as well as what to do in the event of an earthquake, or lightning storm.

However, information on what to do in case of “multiple casualty incidents” is limited to just one page.

It doesn’t directly address what festival staff should do in the event of a crowd surge like the one seen on Friday night.

The stage at Astroworld on Friday
The stage at Astroworld on Friday (Amy Harris/Invision/AP)

The security plan underscores the importance of being prepared for a mass casualty event.

“Based on the site’s layout and numerous past experiences, the potential for multiple alcohol/drug related incidents, posible evacuation needs, and the ever-present threat of a mass casualty situation are identified as key concerns.”

It’s unclear if the advice to use the word Smurf to describe a fatality was followed during Friday’s deadly crowd surge.

In the case of a death, the operations guide said staff should also request additional support, create a perimeter around the scene and take try to take witness statements.

Dozens of lawsuits have been filed against Scott and the promoters Live Nation alleging that insufficient safety measures were put in place.

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