09-004 Automated License Plate Recognition (ALPR) System
AUTOMATED LICENSE PLATE RECOGNITION (ALPR) SYSTEM
PURPOSE
The purpose of this directive is to establish basic procedural guidelines and responsibilities of personnel and units utilizing the Automated License Plate Recognition (ALPR) system. As with any technical system, adherence to standards and procedures is a key element to the success of the system.
BACKGROUND
ALPR technology is a camera-based system that utilizes specially designed cameras to capture license plate and color images of vehicles as they pass by the camera. The ALPR camera is normally “triggered” or “activated” by any vehicle and/or license plate as it passes through its field of view. The captured images from the cameras are processed to provide textual and image data for export to databases. The data may include, a color overview and infrared images, date/time, location data, and/or other data elements. ALPR data can also be automatically compared against hotlist(s) files where users are notified of any wanted licenses plates/vehicles such as Amber Alert, Missing Person, Stolen vehicles, Felony Wanted, Warrants, and others, through various user interfaces.
Currently, LASD is using the following hotlists for ALPR systems to provide alerts:
-
- Stolen Vehicles (SVS);
- Lost or Stolen License Plates (SLR);
- Felony Wanted Vehicles (SFR);
- County Warrants System (CWS) - all “no bail”, misdemeanors over $26,000, and felonies;
- Amber Alerts;
- Missing and Unidentified Persons (MUPS) via NCIC;
- California Sex and Arson Registrants (CSAR); and
- Custom or user defined hotlist(s) or license plate.
All hotlists are updated at specific intervals throughout the day. Due to these intervals and delays in providing “real time” updated hotlist(s), ALPR users should take into account the possibility of being alerted on outdated information.
It is imperative that users of the ALPR system verify and confirm any alerts provided by the ALPR system, either through the Sheriff’s Communication Center (SCC) or via the Mobile Data Computer (MDC), prior to taking any action. Confirmation can be deferred in rare circumstances (i.e., special investigative units) when compelling situations may exist that, if SCC is contacted, could jeopardize the investigation and/or officer safety.
POLICY AND PROCEDURES
Department members and staff will use ALPR in accordance with the procedures and guidelines set forth. All data captured from ALPR systems will be used in accordance with Department policies and directives.
Mobile ALPR unit users receiving an alert that a vehicle is stolen, wanted, or has a warrant associated with it shall immediately confirm the status of the vehicle by running the license plate either manually via the MDC/CAD or over the radio via SCC, unless compelling circumstances are present or officer safety issues make it unsafe to do so. In such cases, deputies shall confirm the status of the wanted vehicle as soon as possible. When requesting SCC to confirm the status of an ALPR alert, the deputy shall advise SCC the request is for an ALPR alert on a vehicle.
In the case of a stolen vehicle alert, personnel may regard the vehicle as a known stolen vehicle while awaiting a secondary confirmation. If the decision is made to initiate a “Code-9” due to an ALPR alert on a stolen vehicle, deputies shall advise SCC they are following a vehicle due to an ALPR stolen vehicle alert (i.e. “212A is Code-9 on a 10-29V ALPR hit”) prior to receiving a secondary confirmation via MDC/SCC.
Deputies shall adhere to the Department’s pursuit policy as described in the Manual of Policy and Procedures, section 5-09/210.00. SCC shall immediately provide secondary confirmation or advise the unit that the vehicle is not reported as stolen.
When desk personnel receive an alert from a fixed ALPR system, which is the result of license plate data taken from a fixed camera, they shall confirm the current status of the vehicle via their CAD terminal or via SCC. While waiting for confirmation, desk personnel will advise field patrol units of the ALPR alert, the location, the vehicle description, request an Aero Bureau unit, and coordinate responding field units.
Any incident associated with the ALPR system shall be documented using a secondary ALPR statistical code. The statistical code shall go on the classification line of the Incident Report (SH-49) and in the MDC clearance. Additionally, any vehicle recovered using the ALPR system shall have “ALPR Recovery” written across the top of the CHP-180 report and the secondary ALPR statistical clearance code will be entered into the MDC clearance log. ALPR statistical codes cannot be used for the issuance of an URN but shall be entered as a secondary statistical clearance code when clearing the TAG.
Please ensure the following stat codes are used:
834 – No ALPR Detection
835 – ALPR-Mobile
836 – ALPR-Fixed
837 – ALPR-CCTV
838 – ALPR-Gunshot Detection
839 – ALPR-Miscellaneous
When recovering a vehicle or boat using statistical code “732” or “733”, the CAD system will not accept the entry without the use of a secondary ALPR statistical code entered.
Examples:
Personnel making an arrest due to an ALPR alert shall enter “835” or “836” as a secondary statistical clearance code in their MDC Log Clearance and on the Classification line of the SH-R-49 report form.
Personnel recovering a stolen vehicle with no suspect in custody shall write “ALPR VEHICLE RECOVERY” on the top of the CHP-180 report as well as use the “835” stat code in the secondary MDC Log Clearance.
Access to ALPR information is restricted to approved personnel. Access to ALPR data is for law enforcement purposes only. Any other use of this data is strictly forbidden. Employees using ALPR data for non-law enforcement purposes may be subject to discipline under Manual of Policy and Procedures as well as all other applicable Department policies, state and federal laws.
Whenever personnel create a manual hotlist/hotplate, they shall include at minimum the reason, file number, and contact information of the investigator.
All ALPR alert(s) provided to personnel shall be verified PRIOR to any detention activity. An ALPR vehicle alert from a hot list does not automatically provide the ALPR users sufficient justification to initiate a traffic stop or detain vehicle occupants. Oftentimes, these hot lists will identify a “vehicle of interest” which is not necessarily wanted for a crime (ex: sex or arson registrant’s vehicle). Personnel must use discretion and have independent information to justify a traffic stop.
Amber Alert hotlist/hotplate are entered/deleted by SCC personnel as needed for the Amber Alert period.
Questions regarding the use of ALPR equipment or accessing ALPR database information should be directed to the Advanced Surveillance and Protection Unit at [REDACTED TEXT]
Questions regarding the content of this Field Operations Directive may be directed to Field Operations Support Services at [REDACTED TEXT]
AFFECTED DIRECTIVES/PUBLICATIONS
Manual of Policy and Procedures (MPP) section 5-09/210.00 Pursuits
Manual of Policy and Procedures (MPP) section 5-09/550.00 Automated License Plate Recognition (ALPR)
Manual of Policy and Procedures (MPP) section 5-09/550.10 General Administration
Manual of Policy and Procedures (MPP) section 5-09/550.30 Field Protocols - Patrol
Manual of Policy and Procedures (MPP) section 5-09/550.40 Audit ProtocolsManual of Policy and Procedures (MPP) section 5-09/550.50 Data