Summer Sale! Get unlimited digital access for 13 weeks for $13.
News Opinion Editorial

Restoring trust in speed cameras

If there is a general theme that runs through The Sun's investigation of speed camera programs on the state and local level in the Baltimore area, it is this: Governments have found ways to follow the letter of the law that maximize the number of citations issued while flouting the spirit of the law that protects the public from erroneous tickets.

The law is designed to prevent the camera operator from being paid on a per ticket basis, but Baltimore City, Baltimore County and, to an extent, Howard County found a way around that. The law requires the cameras to take two, time-stamped photos of each alleged violation to serve as evidence of speeding, but the state, Baltimore County and Howard County render that requirement meaningless. State guidelines define what a "school" is for the purposes of speed camera location, but the law itself does not, and the city has chosen a broad interpretation. It recently shut down some questionable cameras, but it has not conceded the point — nor, of course, has it refunded any of the tickets those cameras produced.

Del. Jon Cardin today proposed creating penalties for camera operators when they issue erroneous tickets. That certainly might provide more incentive for them to be careful, but it would not solve all the problems with the program. State legislators need to take a comprehensive look at the speed camera law to make sure the way it has been implemented conforms with their intent and provides sufficient protection for motorists.

The state's speed camera law says, "If a contractor operates a speed monitoring system on behalf of a local jurisdiction, the contractor's fee may not be contingent on the number of citations issued or paid." But local governments have used self-serving definitions of the word "operates" to justify systems in which contractors are paid on a per-ticket basis.

Since the inception of its speed camera program, Baltimore City has had a contract with a subsidiary of Xerox that pays the company a set amount per ticket issued, generally a little less than half of each $40 fine. Baltimore County initially paid a flat fee to Xerox, but it recently switched to a per-ticket contract. Howard County has a blended arrangement that includes both flat fees and per-ticket payments. The services the contractor performs differ somewhat in each jurisdiction, but in the city, for example, Xerox maintains the cameras and vets possible violations, which are then forwarded to the police for final review before going to motorists.

What the law needs to make clear is that any contractor who has a hand in determining whether tickets are issued should not have an incentive to issue more of them.

The law also says that cameras need to provide two separate, time-stamped images of each violation that both include the same stationary object. Baltimore City's citations round the time to the thousandth of the second, which makes it possible to calculate, with some precision, the speed of the vehicle based on the distance it traveled in the half-second interval between photos. Cameras used by the State Highway Administration and Baltimore and Howard counties round to the nearest second, which makes such calculations impossible. The General Assembly needs to change the law to require the same standard used in Baltimore City.

State law says that cameras may operate in school zones, which it defines as anywhere within half a mile of a school. Subsequently adopted guidelines are more precise, specifying that the cameras must be within 500 feet of a K-12 school, but those restrictions do not have the force of law. The legislature should adopt them as statute.

Several recent cases documented by The Sun's Scott Calvert and Luke Broadwater in which time-stamped photos from Baltimore cameras showed wildly inaccurate speed data call for a separate response. Xerox has attempted and failed to replicate the problems reported at two cameras on Cold Spring Lane and has stopped issuing tickets from those locations while it tries to sort out the source of the problem. The company has suggested, among other things, that the city paint markings on the pavement to make it easier to calculate the speed of supposed violators. That's an excellent idea and should be required by law wherever speed cameras are used so motorists and judges can more easily determine whether the tickets are valid.

Speed cameras can be a valuable tool to increase public safety, but they have to be accurate, and they have to be used in such a way that motorists can effectively challenge them if they are somehow in error. It's clear that Maryland's speed camera program is currently failing that test, and the General Assembly needs to step in to fix it.

Copyright © 2015, The Baltimore Sun
Related Content
  • Speed cameras save lives? Prove it

    Speed cameras save lives? Prove it

    I read the article about money machines (speed cameras) in Baltimore County, and there certainly are a number of different numbers associated with these money grabbers ("Is Baltimore County doubling its speed camera budget?" May 30). I use these term because I believe most people think speed cameras...

  • Annapolis and speed cameras

    Annapolis and speed cameras

    Isn't it amazing how the courts have found that speed cameras are a safety feature and not an un-mandated nuisance tax, yet The Sun finds the news in the loss of revenue instead of the great job they are doing in slowing down traffic and clogging up the streets of Annapolis with bumper to bumper...

  • Cameras and corruption

    Cameras and corruption

    I have followed The Sun's investigation of Baltimore's speed and red light cameras from the beginning and believe a desire for a back door tax is what is driving Baltimore's concern and not protecting the poor innocent school children they claim when defending the constitutionality of such laws...

  • Smaller is better

    Smaller is better

    A Baltimore City Council investigative committee looking into the city's problem-plagued speed- and red light-camera program has discovered what should have been obvious all along: That the now suspended system was far too big to be managed efficiently, that it was set up too quickly by the companies...

  • Speed cameras don't save lives

    Speed cameras don't save lives

    A recent editorial claimed "speed cameras are a powerful tool for saving lives" ("Safety first," June 3) but the supporting evidence, "a reduction in speed-related crashes — 29 percent from 2009 to 2012" is about crashes, not lives.

  • Get a move on: Local speed limits are too low [Letter]

    Get a move on: Local speed limits are too low [Letter]

    Congratulations to Howard County for trying to figure out sensible speed limits ("Are Howard County's speed limits too low?" Aug. 5).

  • Safety or revenue?

    Safety or revenue?

    Before it was shut down over reports of widespread errors, Baltimore ran by far the largest speed camera program in the state and one of the largest in the nation. It generated a lot of tickets and a lot of revenue for the city — so much so that officials were fighting over what to do with the...

  • Speed cameras didn't make streets any safer

    Speed cameras didn't make streets any safer

    I enjoyed your recent article on the statistics regarding pedestrian accidents during and after the use of speed cameras ("Even with speed cameras off, no pedestrians injured in school zones," Dec. 19).