# Going 420 mph In A 30 mph Zone?

### from the you-might-want-to-slow-down-a-bit dept

It's been almost exactly three years since we wrote about a UK driver who received an automated ticket from a speeding camera, clocking his car cruising at a speedy 406 mph. The police chalked it up to a "clerical error." However, apparently those clerical errors are still happening, as a cab driver in the UK has now been issued a ticket for traveling 420 mph in a 30 mph zone. Again, the police chalk it up to "an employee processing error." Unfortunately, despite the driver's claims in the article that he's set a new land speed record, that's not even true in the world of bogus tickets. We've seen other reports clocking people at at least 480 mph. It's probably not such a big deal when the errors are so obvious -- but it makes you wonder how many people get in trouble for similar errors that aren't so extreme? Unless you happen to be good enough at math to disprove a slight exaggeration in your speed, you might just be completely out of luck. You would think that systems like these would (a) not let humans adjust the recorded speed and (b) have some sort of "reality" filter to pick up these extreme errors -- but apparently neither feature is in place. Perhaps that's why we once had that story of a brick wall clocked at 58 mph.

1. Peet McKimmie (profile), 5 Jan 2007 @ 3:43am

### Let's fix this.

OK, from the examples given (admittedly not a statistically significant sample) I would infer that, in the equipment used, the zero key is right next to the "Enter" key. Let's just replace all the keypads so that, say, "." is where zero is at the moment and zero moves to wherever it was. That way, "42" might be mis-entered as "42." and the damn thing will still work; no more stories in Slashdot, minimal costs.

Subscribe to the Techdirt Daily newsletter

Comment Options:

• Use markdown. Use plain text.
• Remember name/email/url (set a cookie)

Special Affiliate Offer