Google Street View images of certain Indiana streets may be a bit blurry. Police clocked one of the tech company’s drivers doing 120 mph in the recognizable 360-degree camera car. I’ve never seen a Google Street View car with a “How’s my driving?” number. But it might only be a matter of time.

Not-so-incognito mode

Police officers in Middletown, Indiana, must have done a double-take. They were monitoring traffic near a high school and witnessed a vehicle blow by at more than twice the 55 mph speed limit. It passed two other cars while they watched. What’s more, it was a work vehicle. Decked out in cameras.

The department’s report said the vehicle “was Google wrapped and had a large 360 camera on top of the vehicle.”

The officers understandably flipped on their lights and sirens. Then the driver—presumably on the clock—floored it. As he accelerated, he swerved in and out of traffic, then blew through a red light.

What finally stopped him? He hit a dead end where a bridge was closed for repair. He tried to turn but instead went “airborne for several feet” before landing in a creek.

Wait: Recalculating…

The driver was 37-year-old Google employee, Coleman Ferguson. He first told police he was “scared,” and that’s why he fled. Since the 2023 chase, he’s pleaded guilty and offered the fuzz $3,200 in restitution. Authorities reduced his felony to a misdemeanor and suspended his one-year jail sentence.

I have so many questions. Among them: Were the cameras recording? Did Ferguson think Google wasn’t tracking its car? How does the employer normally deal with speeding in Google Street View cars?

120 mph isn’t “Uh-oh, I’m late for work.” It’s “let’s see if I can hit NASCAR speeds with a camera strapped to the roof.”

Also, doesn’t Google have the best data on road closures? So was this guy not running Google Maps during the incident? Probably not. If he had been, it might have warned him of the speed trap ahead of time.