A concertgoer reportedly experienced a seizure after being fly-kicked by a security guard during a Travis Scott concert at Melbourne’s Marvel Stadium on Wednesday, October 23. He was among five fans who were hospitalized after being tackled by security personnel when they forced their way past a barricade.
Travis Scott was scheduled to perform two shows at Melbourne’s Marvel Stadium on October 22 and 23 as part of his Circus Maximus Tour. During the first show, fans allegedly engaged in fights, clashed with police, and broke through security barriers after facing long wait times.
At the second concert, the situation reportedly intensified as two male fans attempted to jump the barricade to approach Travis Scott but were intercepted by security. One fan was quickly apprehended, while the other attempted to escape in a different direction.
Shocked onlookers watched as the fan was fly-kicked by a security guard and then suffered a seizure while being restrained. He was subsequently removed from the stadium and handed over to medical personnel for treatment.
The crowd reportedly remained on the edge of chaos throughout the concert, with many attendees recounting other instances of aggression and disorderly behavior throughout the event.
This incident in Melbourne wasn’t the first Travis Scott concert to result in medical emergencies. At least eight people lost their lives, and hundreds were injured in a stampede at Scott’s Astroworld music festival held at Houston’s NRG Park on November 5, 2021.
During the Astroworld show, over fifty thousand attendees surged toward the stage, leading to a massive stampede and numerous injuries. At one point before the stampede began, Scott paused his performance to instruct security to help manage the crowd.
“Security, somebody help, jump in there real quick. Somebody jump in, come on, come on, security,” Travis Scott could be heard saying in fan-captured video clips from the event.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ