| |
Introduction:
More than 1 million motor vehicle crashes occur
annually at traffic signals. In contrast to overall
trends in fatal crashes in the United States, the
number of fatal crashes at traffic signals increased
15 percent between 1992 and 1995. Traffic signals,
through use of time separation, are designed to
reduce motor vehicle crashes at intersections involving
potentially conflicting traffic movements. High
compliance with signals is essential for safe and
efficient traffic movement, and noncompliance contributes
substantially to urban motor vehicle crashes.
Motorists are more likely to be injured in crashes
involving red light running than in other types
or urban crashes. A study of police-reported crashes
in four U.S. cities indicates occupant injuries
occurred in 45 percent of the red light running
crashes, compared with 30 percent of other crash
types. This indicates that reductions in red light
running crashes would be especially beneficial
in reducing urban crash losses.
Efforts to promote traffic law compliance are
constrained by limited police enforcement resources,
which have been declining in relation to the number
of vehicles on the road. Enforcing traffic signal
compliance in urban areas is difficult not only
because of limited manpower but because of factors
associated with traditional enforcement methods,
which in many cases require police to follow a
violating vehicle through a red light to stop it.
This action, plus pursuit in areas of high vehicle
density, can endanger motorists, pedestrians and
police officers. Therefore, conventional traffic
enforcement in some communities is being supplemented
with advanced technology.
Red light cameras increasingly are being used
to help communities enforce traffic laws by automatically
photographing vehicles whose drivers deliberately
run red lights. A red light camera system is connected
to the traffic signal system and to sensors buried
in the pavement at the crosswalk or stop line.
The camera system continuously monitors the traffic
signal, and the camera is triggered when any vehicle
passes over the sensors faster than a preset minimum
speed and at a specified elapsed time after the
signal has turned red. A second photograph is taken
that shows the violator in the intersection. The
camera records the date, time of day, time elapsed
since the beginning of the red signal, and the
speed of the vehicle. The use of a flash produces
clear images under a wide range of light and weather
conditions. Upon review of photographic evidence
and depending on state law requirements, tickets
are issued by mail to either vehicle owners or
to drivers at the time of the offenses.
Background:
- After going through a competitive process,
the Sacramento City Council on December 15, 1998
approved a Services Agreement with Lockheed Martin
IMS to install red light running cameras.
- Intersections for this program were selected
based on 1) number of collisions due to red light
running 2) total volumes, and 3) police and community
input.
- To date, eleven (11) intersections have red
light running cameras operations.
- There are:
1) Mack Road & La Mancha / Valley Hi
2) El Camino Avenue & Evergreen Street
3) Howe Avenue & Fair Oaks Boulevard
4) Mack Road & Center Parkway
5) Arden Way / Ethan / Expo
6) 30th Street & Capitol Avenue
7) Alhambra & J Street
8) W Street & 16th Street
9) College Town & Howe Avenue
10) Broadway & 21st Street
11) Power Inn & Folsom
- As required by California Vehicle Code (CVC),
the City of Sacramento began on May 26th, 1999
issuing warning notices for a period of 30 days.
- On June 26th, 1999 the City began issuing red
light running citations.
Problem:
In 1998 the City Police Department
reported more than 5498 collisions. Of those, 714
were due to red light running causing 494 injuries.
Based on California Highway Patrol statistics, the
financial impact to the local economy is more than
$15M.
Goal:
The goal of the program is to enhance
public safety by changing driver behavior.
California
State Auditor/Bureau of State Audits July 2002
Red Light Camera Audit (795 KB)
 
|
|
