Police officer crashes car while watching porn

The officer violated multiple policies during the investigation and resigned from his position following the incident


News Desk January 11, 2025

A Florida sheriff’s deputy has resigned after an internal investigation revealed he was watching porn on his phone just before crashing into a civilian’s car.

Tristan Macomber, a former deputy with the Lake County Sheriff’s Office, crashed his department-issued vehicle in early November 2024 while driving south on County Road 435.

The incident was captured on his body-worn camera, showing the moment the steering wheel airbag deployed after Macomber’s vehicle rear-ended another car that had stopped for a school bus. In the footage,

Macomber can be seen tossing his cellphone onto the passenger seat before retrieving it and checking on the other driver. "Hello, ma’am. Are you OK? I’m so sorry," Macomber is heard saying as he approaches the other driver.

Initially, Macomber told a sergeant that his brakes had locked up before he collided with the other vehicle. However, an internal affairs investigation uncovered discrepancies in his account.

Macomber first claimed he was scrolling through text messages in a group chat with other deputies before the crash. But the investigation revealed he had been viewing inappropriate and visual content, which he later admitted was pornographic material.

The internal affairs report concluded that Macomber "admitted to lying" and confirmed that he was "looking at pornographic material on his personal phone just before the vehicle crash."

The investigation also found that Macomber violated multiple sheriff’s office policies. These included providing false statements, using an electronic device for prohibited purposes, and failing to wear a seatbelt while driving.

Following the findings, Macomber resigned from his position at the Lake County Sheriff’s Office.

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