TODAY’S PAPER | April 24, 2026 | EPAPER

Security guard identified after London crash involving influencer Gabrielle Carrington

Security guard Anoosh Chaichy identified after London crash involving influencer leaves victims seriously injured


Pop Culture & Art April 24, 2026 1 min read
Photo: Instagram

A security guard who sustained serious injuries in a central London vehicle incident has been identified following a crash involving an influencer now facing multiple criminal charges.

According to reports from Metropolitan Police and UK media outlets, 56-year-old Anoosh Chaichy was among those injured when a car struck pedestrians near the Inca nightclub in Soho during the early hours of April 19.

Police said the incident occurred at approximately 4:30 a.m., leaving Chaichy with life-changing injuries. A woman in her 30s, identified as influencer Klaudia Zakrzewska, remains in a life-threatening condition, while another individual sustained minor injuries.

Authorities have charged Gabrielle Carrington, 29, with attempted murder, grievous bodily harm with intent, actual bodily harm, dangerous driving and drink driving in connection with the incident. She appeared before Westminster Magistrates’ Court on April 22 and has been remanded in custody ahead of a further hearing scheduled at the Old Bailey on May 19.

Prosecutors allege that the vehicle mounted the pavement following an altercation outside the venue, striking multiple pedestrians. Chaichy was reportedly attempting to move his e-scooter when he was hit.

Investigators also stated that Carrington was found to have alcohol levels above the legal driving limit at the time of arrest. The case remains under active investigation as authorities continue to review evidence, including CCTV footage.

The incident has drawn significant attention in the UK, raising concerns about public safety and ongoing legal proceedings surrounding the accused.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ