Stay up to date with notifications from The Independent

Notifications can be managed in browser preferences.

Bugzy Malone crash: Rapper ‘lucky to be alive’ as he shares footage of horror accident

Rapper said he couldn’t remember much of incident, which saw his bike collide with a vehicle

Adam White
Monday 30 March 2020 07:35 BST
Comments
Bugzy Malone recovers in hospital following horror crash

Bugzy Malone has said he is “lucky to be alive” after his involvement in a serious quad bike accident in Manchester.

The rapper was hospitalised on 25 March after his bike collided with a car, with footage circulating on social media showing the star covered in wounds and being loaded into an ambulance.

Writing from his hospital bed, the 29-year-old rapper expressed his gratitude for the “well-wishes and prayers” sent his way.

“They tell me I’m lucky to be alive but although I sustained serious injuries at the time I lost consciousness so I don’t remember much,” he wrote.

“What I do remember is the non-stop love, and just want to say thanks for all the well wishes and prayers, you lot caught me off guard with all the support!”

He continued: “Lock down ain’t easy because boredom causes the craziest problems, but be safe regardless…”

Bugzy also shared a number of photographs of his wrecked bike, along with apparent CCTV footage of the incident.

The footage shows him being thrown from his bike after colliding with a vehicle.

In a statement, a spokesperson for Greater Manchester Police said that they arrived on a street in Bury following “reports of a collision involving an Audi car and a quad bike.”

They added: “Emergency services attended and the driver of the quadbike – a 29-year-old man – was seriously injured and taken to hospital for treatment. His injuries are not believed to be life-threatening.

“No arrests have been made and enquiries are ongoing.”

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