Virginia House Punts Sneaky VDOT Oversight Bill

January 31, 2009

On Thursday the Virginia House Transportation Committee by a 12-10 vote tabled H.B. 2416, the sneaky attempt by Virginia Beach fraud merchants to eliminate the Virginia Department of Transportation’s ability to stop cities from installing red light cameras in locations where engineering studies do not support their use. In other words the idea is: Virginia Beach and Fairfax want their money now, there’s no time for engineering or safety.

What does “tabled” mean? It means the committee looked at the bill and shoved it in the drawer. In the normal process, the bill is dead as far as the committee is concerned, although it is possible to introduce a motion “To take H.B. 2416 from the table” and pass it. In a part-time legislature, that doesn’t happen. The bigger danger is that this three-word provision gets inserted in the dead of night into a “must pass” piece of legislation like the budget. That’s the way these scam artists do business.

Here’s the vote count. YEA is a vote to dump the bill, but take note that many of those who voted correctly on this are scamera supporters (bold). All of the NAY votes are scamera supporters.

YEAS–May, Oder, Saxman, Carrico, Cosgrove, Gear, Rust, Hugo, Scott, E.T., Fralin, Loupassi, Knight–12.

NAYS–Tata, Ward, Ebbin, BaCote, Marsden, Valentine, Brink, Toscano, Nichols, McQuinn–10.


Deadly Red Light Cameras Rejected in Winchester, VA

January 29, 2009

The Frederick County, Virginia Board of Supervisors said “no” to deadly red light cameras last night. The potential for icy roads kept several of us from making the 90 mile trip to speak, but the Northern Virginia Daily reported that the measure was narrowly defeated:

The proposal elicited mixed reaction from supervisors. Gene E. Fisher said he had researched the issue.

“The statistics I have seen show that this decreases accidents,” he said.

But Supervisor Gary A. Lofton said crash statistics he obtained from the Sheriff’s Office indicated there were few accidents caused by motorists running red lights in the county.

Installing cameras would be a “Draconian fix,” he said. Getting caught by the camera would have cost a motorist $50.

Of course, the only statistics Mr. Fisher bothered to look at were the ones in the sales packet provided by whichever red light camera company happened to drop  by his office. No surprise that this “research” did include the comprehensive 2007 Virginia Department of Transportation study that documented the results at red light camera intersections across the Commonwealth:

  • Rear end accidents increased 42%
  • Angle accidents increased 20%
  • Injury accidents increased 18%
  • The total number of accidents increased 29%

Get a copy of the study

Maryland Speed Camera Program: Scams, Conflicts of Interest Everywhere

January 26, 2009

When he Maryland Legislature authorized Montgomery County to use speed cameras in 2006, the people were given certain assurances. One was that there would be no per-ticket payments to speed camera contractors, which would create a financial incentive for contractors to “cheat” to maximize profits. Another was that they would only be used in “residential and school zones”, not major arterial roads. And finally, that they would not be used as cash cows for local governments by earmarking the revenues for (undefined) “public safety” improvements. All of those promises were given to the driving public – and ALL of those promises have since been broken by the Montgomery County Speed Camera Program.

The no-per-ticket-payment requirement was discussed in local government planning sessions and County Council Sessions prior to bidding on the contract, including a comment by now council president Phil Andrews on the May 8th, 2006 that “contractors are not paid based on the number of citations, that’s built-in” (transcript, pdf). Nonetheless the county signed a contract with ACS State and Local Solutions in 2007 which pays the greater of $3000 per van or $16.25 per citation per fully paid citation. That is in violation of article 21-809(j) which states “If a contractor operates a speed monitoring system on behalf of Montgomery County, the contractor’s fee may not be contingent on the number of citations issued or paid.”

Had the county been open with the public about this after citizens started to take issue, and then promptly renegotiated its contract, this might have been the end of this. But the county had a financial conflict of interest of its own: this contract was also designed to maximize profits for Montgomery County. Instead, they attempted to deceive the public while 2008 legislation authorizing statewide speed cameras was being voted on in March 2008. On March 15th 2008, County Executive Ike Leggett stated in an online town hall session in response to a question about why the county was paying its contractor a 40% cut of the speed camera revenues by stating “Under the contract, we pay a flat fee” (transcript). The 2008 legislation contained a subtle change to the law — changing the definition of a speed monitoring system operator from “an individual who operates” to “A REPRESENTATIVE OF AN AGENCY”. That would have allowed the county to designate anyone they choose as the “operator” of the system, and put into law a “loophole” which the county was trying to use as legal cover. Fortunately, the legislative session ended before the house and senate could reconcile minor differences and make it law.
On May 15th, 2008, County executive Leggett stated that the county would renegotiate its contract. But because of the county’s financial conflict, they instead continued to expand the program. That expansion included the city of Takoma Park signing an agreement to join the contract in September 22, 2008. The resolution appears to require ACS to make a profit for the city:

If the total of the City’s paid citation revenues are less than $2,999.00 per month per mobile unit for two consecutive months or for any two months in a six-month period during the term of the agreement or any renewals, the contract provides for a renegotiation of the per citation rate and/or the monthly minimum compensation payable to the contractor. If the City, in its sole discretion, is not satisfied with the results of such renegotiation or with the revenues derived from the photo speed enforcement program or the City determines that photo speed enforcement is no longer an appropriate enforcement mechanism for the City, then the City may terminate this Agreement for convenience….

Other promises given by the county and state have also proven empty. The requirement that cameras would only be used in “residential and school zones” became meaningless when major 4-6 lane commuter routes such as Connecticut Avenue were used. Other residential zones, have few or no houses nearby, such as the cameras on Montrose road that are located on a bridge at the bottom of a long hill.

Maryland speed trap

Darnestown, Maryland speed trap

The requirements that money be spent on “public safety” were proven meaningless when Chevy Chase village decided that purchasing a new Segway, a locker room, and an office for their police chief constituted “public safety improvements”. Minutes from Chevy Chase village show those items were purchased directly from the safe speed fund.

Finally, promises that they would not be used as cash cows were proven empty when in December 2008 new cameras in Darnestown were placed immediately after the location where the speed limit dropped from 40mph to 30mph. That setup is highly likely to snare any driver who does not react immediately to the changing speed limit.

The Maryland General Assembly is currently in session. Several legislators and Governor O’Malley have pledged to pass legislation which will expand speed cameras to other parts of Maryland. Given the deception Maryland drivers have faced already, it is urgent that you get involved to let them know you will not tolerate more scams, or more scameras!

Virginia Beach Fraud Merchants Try to Pull a Fast One

January 20, 2009

Greedy Virginia Beach city council members talked their state delegates into introducing legislation that would remove the final roadblock to their plan to get rich by trapping drivers with short yellows and badly engineered intersections. Obviously the delegates responsible hoped that nobody would notice their plan. Let them know what you think after reading the article below:

Delegate Robert W. Mathieson
Phone: (757) 470-3000

Delegate Joseph F. Bouchard

Phone: (757) 333-2527


A bill introduced last week in the General Assembly quietly seeks to eliminate a significant motorist protection built into Virginia’s existing red light camera law. The proposal of a pair of Democratic state delegates representing Virginia Beach, Joseph F. Bouchard and Robert W. Mathieson, would delete just three words from that statute, but the change would have wide-ranging effects. Under current law, cities that want to install traffic cameras must first submit a detailed engineering justification to state transportation experts.

“A locality shall submit a list of intersections to the Virginia Department of Transportation for final approval,” Virginia Code Section 15.2-968.1(J) states.

House Bill 2416 would delete the phrase “for final approval,” eliminating oversight by the Virginia Department of Transportation (VDOT) entirely. Many lawmakers reluctantly voted in 2007 to allow the operation of red light cameras only after a handful of provisions were added to ensure municipalities did not simply install automated ticketing machines as a means of obtaining easy revenue. To date, the most powerful of these provisions has been this oversight power which has already been exercised in turning down proposals by the cities of Virginia Beach and Leesburg as unsafe.

VDOT has been careful regarding red light cameras because its own studies in 2005 (view study) and 2007 (view study) showed that accidents increased significantly at the intersections where red light cameras were operational in Virginia. Because VDOT does not share in the revenue generated by a camera, unlike a municipality and its private vendor, lawmakers saw the agency’s participation as an essential third-party check on municipal designs.

VDOT has also been burned in the past by aggressive participation in local red light camera programs. In 1999, the agency shortened the yellow signal duration at a Fairfax County intersection by 1.5 seconds just four days after county officials signed a contract to install red light cameras. Accidents and violations increased dramatically. When VDOT lengthened the signal back to 5.5 seconds a year later, accidents and violations dropped immediately and decisively (view full details).

Shortened yellows are the key to the financial success of red light camera programs. Confidential documents from the private vendor now operating as Affiliated Computer Services (ACS) show that employees were only allowed to install red light cameras at intersections with yellow times of “less than four seconds” and “downhill approaches” (view documents). A Texas Transportation Institute study confirmed that when the yellow light timing was increased one second above the bare minimum amount recommended by the ITE formula, accidents dropped 40 percent (view study).

Bouchard and Mathieson’s proposal would give Virginia Beach and other municipalities the freedom to ignore any engineering improvements — especially lengthened yellow timings — recommended by VDOT.

Winchester, VA Eyes Deadly Red Light Cameras

January 16, 2009

A slim majority on the Frederick County Board of Supervisors wants to bring deadly — but profitable — red light cameras to to the county, which mostly means the city of Winchester, Virginia. Because the proposal only passed by a 4-3 vote, it only will take one changed mind to stop the spread of the red light scam. Do your part to stop this madness:

What: Attend Frederick County, Virginia Board of Supervisors Meeting
When: January 28, 2009 at 7:15pm
Where: 107 North Kent Street, Winchester
Directions:  Here

Scamera agenda document from December

It’s a straight shot on Route 7 all the way to Winchester with little traffic once you get away from the DC suburbs. Just watch out for the speed traps.

On our side: Gary Lofton, Richard C. Shickle Sr. (chairman), Gary Dove.

Fairfax Flouts Law, Adopts Dodgy Deal with Fellow Scofflaws

January 15, 2009

At 1am today, long after the public had left the council chambers and long after those who watch such things on public access cable television had dozed off, Fairfax City Council members approved the dodgy deal with Redflex. Five remained in the audience until the end to point out:

  1. Fairfax cameras increased accidents
  2. The contract is illegal on revenue neutrality and diversion of cash from the literary fund grounds
  3. The city is ignoring superior engineering countermeasures
  4. The tickets are unenforceable
  5. The tickets undermine constitutional protections and privacy

After being threatened with a pair of lawsuits on point #2 above, the council retreated to an hour-long private deliberation away from the public to “consult with the city attorney.” In a cowardly move, members returned for a quick vote that was unanimous in favor of the illegal deal with the lawbreaking Australian company. (Redflex has been fined for violating FCC regulations governing radar and for falsifying documents used in securing speed camera convictions.) No response was offered to the detailed concerns brought by members of the public over the proposal.

There’s still more to do. The Virginia Department of Transportation must approve any proposed camera intersections on engineering grounds, and the council can reconsider its actions at any time. That’s not going to happen unless we let residents know this scam is going on so that they can put pressure on council members:

  • Mayor Robert F. Lederer:
  • Joan W. Cross:
  • Daniel F. Drummond:
  • Jeffrey C. Greenfield:
  • David L. Meyer:
  • Gary J. Rasmussen:
  • Steven C. Stombres:

Literature drops to get the word out in the community would help. Here’s a flyer to pass out. (PDF)

Fairfax City Proposes Illegal Contract with Australian Company

January 9, 2009

On January 13, the Fairfax city council will adopt a contract with Redflex Traffic Systems to install deadly red light cameras at ten intersections in Fairfax, Virginia. How does this work?

Redflex, a company based in Melbourne, Australia, promises to pay the city of Fairfax for the privilege of installing the cameras, reviewing the photographs, creating public relations material promoting the system (i.e. propaganda), repairing any damage, preparing all materials for court hearings, mailing citations and collecting fine payments. It’s all spelled out in Appendix B of the contract (warning: PDF) You might be wondering, if Redflex is doing so much then what role does the city have? The answer is: none. In fact, Fairfax doesn’t even need to go down to the bank and cash its giant monthly check.

Redflex will deposit all of the ticket revenue in the city’s bank account — minus a monthly fee of $4,740 per intersection or a grand total of $568,800  per year. In fact, Redflex guarantees that the city will not, under any circumstances, lose any money on the deal, even if no tickets are ever issued. This so-called “cost neutrality” provision, spelled out in Appendix D, also happens to be illegal.

The contract says:

Cost Neutrality
Cost neutrality is assured to Customer — Customer will never be required to pay Redflex more than actual cash received by Redflex, and such cost neutrality should be reconciled on a monthly basis. This is a material provision of this Agreement and a condition precedent for Customer agreeing to enter into this Agreement.

In other words, despite all the wonderful benefits promised, the city has no interest in paying for its “safety” program. The most important provision in the entire document, the “condition precedent,” is that the city of Fairfax make a profit. We’ll let the reader decide whether that’s a shady motivation or not. Let’s look instead at what the Code of Virginia has to say about it.

A private entity may enter into an agreement with a locality to be compensated for providing the traffic light signal violation monitoring system or equipment, and all related support services, to include consulting, operations and administration….  No locality shall enter into an agreement for compensation based on the number of violations or monetary penalties imposed.

So, let’s think about this. Redflex must be able to keep $4,740 per intersection per month from the cash it collects from motorists. That’s roughly a total of 95 paid tickets. What happens if only half that amount, say 45 tickets, are actually paid? That would mean that Redflex would collect $2,250, but Fairfax would not be required to make up the difference because the contract says: “Customer will never be required to pay Redflex more than actual cash received by Redflex.”

That means if Redflex collects $2,250 in monetary payments, the company — a private entity — will be compensated $2,250. If Redflex collects on one more ticket to $2,300, then Redflex will be compensated $2,300. And so on up to $4,740. There is no getting around the fact that this would be compensation according to the number of violations and the amount of monetary penalties imposed.

An appellate court in California has already considered this issue and struck down a similar contract between the city of Fullerton and a different firm, Nestor Traffic Systems (NTS). The judge ruled:

The possibility that fees could be negotiated ‘down’ if it is determined fees paid to NTS exceed ‘net program revenues being realized,’ indirectly ties fees to NTS to the amount of revenue generated from the program. If insufficient revenue is generated to cover the monthly fee, the fee could be ‘negotiated down.’ As such, NTS has an incentive to ensure sufficient revenues are generated to cover the monthly fee.

So, not only is what Fairfax City proposes to do dangerous, it’s also illegal.