Man Killed in Accident While Evading YouTube Vigilante Streaming Drunk Driving Incidents

A South Korean motorist, who was suspected of being intoxicated by a YouTube vigilante, tragically lost his life in a car accident during a livestreamed pursuit.

According to Gwangju Gwangsan Police, at approximately 3:50 AM on September 22 in Gwangsan-gu, Gwangju, a man driving an SUV collided with a parked truck while being chased by a YouTuber famous for exposing drunk drivers.

The 35-year-old driver crashed into a cement transport trailer parked on the roadside near a gas station in Sanwol-dong, Gwangsan-gu. The force of the collision caused his BMW to ignite and burn entirely. He was rushed to a hospital but succumbed to his critical injuries later.

The collision resulted in property damage estimated at around 13 million South Korean won (approximately $9,740).

The content creator, who identifies himself as the “Gwangju Sheriff” and is also known as the “Drunk Drivers Hunter,” frequently uploads videos showcasing car chases with suspected drunk drivers. He has amassed over 70,000 subscribers on his channel.

During the livestream on the day of the incident, the YouTuber confronted the driver, inquiring whether he was intoxicated, to which the driver denied. Nevertheless, the YouTuber reported the individual to the authorities for suspected drunk driving.

His livestream, which attracted around 400 viewers, documented the chase but did not capture the exact moment of the crash, which occurred about two minutes into the pursuit. The video is no longer available on his YouTube channel.

A police spokesperson mentioned, “We will investigate the precise causal link between the YouTuber’s pursuit and the crash.”

Authorities stated that surveillance footage indicated no evidence of the YouTuber following the driver closely before the accident. However, the inquiry is still ongoing to ascertain if the driver was indeed under the influence of alcohol and whether there was any direct correlation between the chase and the crash.

Source

Leave a Reply

Your email address will not be published. Required fields are marked *