Chapter 14 Wanted

Chapter 14 WACIC Wanted Persons File

WACIC Manual Chapter #14-1

Revised 10/2010

SECTION 01: INTRODUCTION 5

DEFINITIONS 5 A. PURPOSE OF THE WANTED PERSON FILE 5 B. CRITERIA FOR ENTRY 5

SECTION 02: INQUIRIES 11

I. PROCEDURE 11 A. SYNTAX 11 B. OPERATIONAL INQUIRIES 12 C. RESPONSES 20

SECTION 03: FIELDS AND EDITS 24

I. DEFINITIONS 24 A. MESSAGE KEYS 24 B. FIELDS AND EDITS 24 C. DATA FIELD SETS 37

SECTION 04: ENTRY 38

I. PROCEDURE 38 A. ENTRY MASK 38 B. EXAMPLES OF ENTRIES 39 C. ENTRY ACKNOWLEDGMENTS 40 D. REJECTING DUPLICATE RECORDS 40 E. ADDITIONAL GUIDELINES FOR ENTRIES 42 F. GUIDELINES FOR ENTRY OF A JOHN OR JANE DOE WARRANT 42 G. VEHICLE OR LICENSE PLATE DATA 43 H. ADDITIONAL GUIDELINES FOR JUVENILE OFFENDER ENTRIES 44

SECTION 05: SUPPLEMENTAL DATA ENTRY 46

I. PROCEDURE 46 A. SUPPLEMENTAL DATA TRANSACTIONS 46 B. SYNTAX 46 C. WANTED PERSON SUPPLEMENTAL DATA ENTRY FIELD EDITS 47 D. EXAMPLES OF WANTED PERSON SUPPLEMENTAL DATA ENTRIES 47 E. SUPPLEMENTAL DATA ENTRY ACKNOWLEDGMENTS 47 F. ENTRY GUIDELINES FOR SUPPLEMENTAL DATA 48



Revised 10/2010

G. ALIAS (AKA) FIELD IN A SUPPLEMENTAL DATA ENTRY 49 H. OPERATOR'S LICENSE (OLN) FIELD IN A SUPPLEMENTAL DATA ENTRY 50 I. LICENSE PLATE FIELD IN A SUPPLEMENTAL DATA ENTRY 50 J. VEHICLE DATA IN A SUPPLEMENTAL DATA ENTRY 51 K. ADDITIONAL IDENTIFIERS IN A SUPPLEMENTAL DATA ENTRY 51 L. NUMBER OF ADDITIONAL IDENTIFIERS IN A SUPPLEMENTAL DATA ENTRY 51 M. MAXIMUM NUMBER OF ADDITIONAL IDENTIFIERS 52 N. MODIFICATION OF SUPPLEMENTAL IDENTIFIERS 52

SECTION 06: STOLEN/FRAUDULENT IDENTIFIER 53

I. PROCEDURE 53 A. STOLEN OR FRAUDULENT IDENTIFIER DATA ENTRY 53 B. SYNTAX 53 C. WANTED PERSON STOLEN/FRAUDULENT IDENTIFIER ENTRY FIELD EDITS 54 D. EXAMPLE OF STOLEN OR FRAUDULENT IDENTIFIER DATA ENTRIES 54 E. STOLEN OR FRAUDULENT IDENTIFIER DATA ENTRY ACKNOWLEDGMENTS 54 F. ENTRY GUIDELINES FOR STOLEN OR FRAUDULENT IDENTIFIERS 55

SECTION 07: MODIFY TRANSACTIONS 58

I. DEFINITIONS 58 A. MODIFY TRANSACTIONS 58 II. PROCEDURE 58 A. AGENCY MODIFICATION 58 B. SYNTAX 58 C. WANTED PERSON MODIFY FIELD EDITS 59 D. EXAMPLES OF WANTED PERSON RECORD MODIFICATIONS 59 E. MODIFY ACKNOWLEDGMENTS 60 F. ADDITIONAL GUIDELINES FOR RECORD MODIFICATIONS 60 G. MODIFICATION TO REMOVE ALL VEHICLE DATA 61 H. MODIFICATION TO REMOVE PART OF VEHICLE DATA 61

SECTION 08: LOCATE MESSAGES 62

I. DEFINITIONS 62 A. LOCATE MESSAGES 62 B. AGENCY LOCATES 62 C. SYNTAX 63 II. PROCEDURE 64 A. WANTED PERSON LOCATE FIELD EDITS 64 B. EXAMPLES OF WANTED PERSON RECORD LOCATE MESSAGES 65 C. LOCATE ACKNOWLEDGMENTS 66 D. LOCATE GUIDELINES 67



Revised 10/2010

E. USE OF EXTR IN A LOCATE MESSAGE 68 F. USE OF NOEX IN A LOCATE MESSAGE 68 G. USE OF DETN IN A LOCATE MESSAGE 68

SECTION 09: DETAINER 70

I. DEFINITIONS 70 A. DETAINER FILE 70 B. SYNTAX 71 II. PROCEDURE 72 A. WANTED PERSON DETAINER FIELD EDITS 72 B. MESSAGE FIELD CODES AND EDITS 73 C. EXAMPLE OF A DETAINER ENTRY 73 D. MANDATORY FIELDS FOR A DETAINER ENTRY 73 E. DETAINER ACKNOWLEDGMENT 74 F. ADDITIONAL GUIDELINES FOR DETAINER ENTRY 74 G. NOTIFICATIONS OF DETAINER 75 H. MODIFICATION OF DETAINER INFORMATION 78 I. WHEN TO CANCEL DETAINER INFORMATION 78 J. SYNTAX 78 K. WANTED PERSON CANCEL DETAINER FIELD EDITS 78 L. MANDATORY FIELDS FOR A CANCEL DETAINER 79 M. EXAMPLE OF A CANCEL DETAINER TRANSACTION (XDW) 79 N. DETAINER CANCEL ACKNOWLEDGMENTS 79

SECTION 10: CLEAR TRANSACTIONS 80

I. DEFINITIONS 80 A. CLEAR MESSAGES 80 B. WHEN TO USE A CLEAR MESSAGE 80 C. SYNTAX 81 D. WANTED PERSON CLEAR FIELD EDITS 81 E. EXAMPLES OF WANTED PERSON RECORD CLEAR MESSAGES 83 F. CLEAR ACKNOWLEDGMENTS 83

SECTION 11: CANCEL TRANSACTIONS 84

I. PROCEDURE 84 A. CANCEL TRANSACTIONS 84 B. SYNTAX 85 C. WANTED PERSON CANCEL FIELD EDITS 85 D. EXAMPLES OF WANTED PERSON RECORD CANCELLATIONS 85 E. CANCEL ACKNOWLEDGMENTS 86



Revised 10/2010

SECTION 12: SUPPLEMENTAL CANCELLATIONS 87

I. DEFINITIONS 87 A. SUPPLEMENTAL CANCELLATIONS 87 B. SYNTAX 87 II. PROCEDURE 88 A. WANTED PERSON SUPPLEMENTAL DATA CANCEL FIELD EDITS 88 B. EXAMPLE OF WANTED PERSON SUPPLEMENTAL DATA CANCELLATION 88 C. SUPPLEMENTAL DATA CANCEL ACKNOWLEDGMENTS 88 D. CANCELLATION GUIDELINES 89

SECTION 13: STOLEN/FRAUDULENT IDENTIFIER DATA 90

I. PROCEDURE 90 A. STOLEN OR FRAUDULENT IDENTIFIER DATA CANCELLATION 90 B. SYNTAX 90 C. WANTED PERSON STOLEN OR FRAUDULENT IDENTIFIER DATA CANCEL FIELD EDITS 91 D. EXAMPLE OF WANTED PERSON STOLEN/FRAUDULENT IDENTIFIER DATA CANCEL 91 E. CANCEL ACKNOWLEDGMENTS 91

SECTION 14: SUPPLEMENTAL DENTAL 92

I. DEFINITIONS 92 A. SUPPLEMENTAL DENTAL RECORDS 92 B. FIELDS AND EDITS 92 C. DENTAL CHARACTERISTICS 93 D. OCA (ORIGINATING AGENCY CASE NUMBER) 93 E. ORI (ORIGINATING AGENCY IDENTIFIER) 93 F. WAC (WACIC NUMBER) 93 G. ADDITIONAL GUIDELINES FOR A SUPPLEMENTAL DENTAL RECORD 93



Revised 10/2010

CHAPTER 14: WACIC Wanted Persons File SECTION 01: Introduction

Procedure #: 14.01.000 Special Order: Supersedes: WACIC Manual 2003 Edition Applies to: ACCESS Users

Effective Date: August 1, 2006

See Also:

CALEA:

DEFINITIONS

A. Purpose of the Wanted Person File

1. This file assists in the apprehension of wanted persons by providing a

central repository for information contained on outstanding warrants held by criminal justice agencies throughout the state and nation. WACIC/NCIC also provide agencies the ability to retain wanted person records (on line) for subjects incarcerated in another jurisdiction by using the Detainer function.

2. Agencies retain the responsibility of maintaining their records in a current status. Warrant information must be entered, modified, located, cleared, or cancelled as conditions dictate.

B. Criteria for Entry

1. Agencies must enter records into WACIC in a timely manner (72

hours) to ensure maximum system effectiveness. A timely entry is one made immediately after:

a. The decision to arrest or authorize arrest has been made.

b. Extradition is known.



Revised 10/2010

2. Felony Warrant Criteria

a. When a wanted felony or wanted juvenile record is entered where the entering agency will not extradite statewide, the extradition limits must be clearly stated in the Extradition Limits (EXL) or the Miscellaneous field (MIS). An agency receiving a hit on a wanted felony or wanted juvenile record that contains extradition limits, and when the agency is outside of the area specified, need not confirm the hit and must not enter a locate on the record.

3. Misdemeanor Warrant Criteria

a. The entering agency must clearly specify the extradition in the EXL or MIS field.

4. Temporary Felony Warrant

a. A law enforcement agency may enter a temporary felony warrant when it needs to take prompt action to apprehend a person who

has committed, or an officer has probable cause to believe a person has committed, a felony and circumstances prevent the immediate acquisition of the warrant.

5. Juvenile Warrants

a. When a juvenile absconded while on probation or parole;

b. Has escaped from an institution or agency vested with the legal custody or supervision of such juvenile;

c. Has been charged with the commission of an act of delinquency or truancy; or

d. Has been charged with the commission of a delinquent act that would be a crime if committed by an adult and who has fled from the state where the act was committed.

6. NCIC Criteria

a. An individual (including a juvenile who will be tried as an adult) who has a felony or serious misdemeanor warrant outstanding.



Revised 10/2010

b. A juvenile who has been adjudged delinquent and is subject to the jurisdiction of the court making such adjudication who:

(1) Has escaped from an institution or agency vested with the legal custody or supervision of such juvenile.

(2) Has absconded while on probation or parole.

(3) Has been charged with the commission of a delinquent act that

would be a crime if committed by an adult and who has fled from the state where the act was committed (Category 2).

7. Temporary Felony

a. Enter a temporary felony to establish a “want” when a law enforcement agency needs to take prompt action to apprehend a person who has committed or the officer has reasonable grounds to believe has committed a felony. This record must either be cancelled and a permanent record entered or the MKE must be modified to a permanent record.

8. Extradition

a. Before entering a record of a wanted person into WACIC/NCIC, the

entering agency must attempt to determine, to the maximum extent possible, if the extradition will be authorized if/when the individual is found. For NCIC purposes, extradition is the surrender by one state to another of an individual charged with or convicted of an offense outside its own territory and within the territorial jurisdiction of the other.

b. Prior to NCIC 2000, if an agency was absolutely certain the wanted person would not be extradited, they would enter NOEX as the first four characters of the MIS field. At the time of entry, they would note all limitations concerning extradition.



Revised 10/2010

c. With implementation of NCIC 2000, this information must be entered in the EXL field and explained in the MIS field of the record. For example:

EXTR ADJACENT STATES ONLY EXTR WEST OF MISS ONLY EXTR COOP STATES WA-OR-ID-MT ONLY EXTR WITHIN 1000 MILES ONLY NOEX

d. If changes in extradition occur, the entering agency must modify the EXL field to indicate the proper parameters.

9. Retention

a. Felony wanted person records, including juvenile warrants, have

unlimited retention within WACIC/NCIC. These records will remain until action is taken by the entering agency to clear or cancel the entry.

b. Misdemeanor warrants remain on file until cleared or cancelled by

the entering agency or the date entered in the date of expiration (EXD) field.

c. Temporary felony warrants remain on file for 48 hours and then are

automatically purged.

d. Records located once or appended with no extradition (NOEX) will remain until action is taken by the entering agency.

e. Records located twice will purge from NCIC and remain in WACIC

for an additional 14 days.

f. Records located containing EXTR or DETN in the EXT field remain on line in NCIC for 5 days. The same rules apply to a located juvenile (whether emancipated or not). Located records remain in WACIC indefinitely unless a second locate is placed on the record or it is cleared or cancelled.

g. Agencies may retain wanted person records in WACIC/NCIC when

the subject is incarcerated in another jurisdiction. They must append DETAINER information to the record.



Revised 10/2010

h. A DETAINER is an official notice from a law enforcement agency to a correctional facility requesting an individual wanted by the first agency, but subject to the correctional facility’s jurisdiction, not be released or discharged without first notifying the wanting agency and giving proper opportunity to respond. A DETAINER does not place a legal hold on a prisoner.

i. Typical reasons for detainers include:

(1) The individual is wanted for trial. (2) The individual is wanted to serve a sentence in the requesting

jurisidiction.

j. Agencies may only append a wanted person record if the record is in LOCATED status.

k. WACIC retains records for periods set forth below and then purges

from the active file and, if applicable, from NCIC, either as part of the annual purge done on or about January 1st, or on a daily basis.

l. All wanted person records appended with a DETAINER will remain

on file until the date of sentence expiration.

10. Cleared Records

a. When a record is cleared, it remains on file in WACIC for 14 days from the date of clear. NCIC immediately removes cleared records.

11. Automatic Purge

a. A record with MKE/EWW, EWF, or EWJ that has one locate

indicating NOEX will be removed from the file immediately upon receipt of a second locate. The ORI of the record and the CJIS Systems Agency, Washington State Patrol, will be notified the record has been purged.

b. A record with the MKE/EWW, EWF, or EWJ that has one locate

indicating the subject will be extradited (EXTR) or detained (DETN) will remain on line for five days after the date of locate. If a second locate is received within the five days, the record will be immediately removed.



Revised 10/2010

c. After five days, those records that have been suppressed will be purged at the time of the next file realignment.

d. A record with the MKE/EWW, EWF, or EWJ that has been

appended to DETAINER, will remain on file until the date of sentence expiration. Five days prior to the date of sentence expiration, the wanting agency will receive an unsolicited message giving notice of the impending release.

e. A WACIC record containing a date in the EXD field will purge on

that date.



Revised 10/2010

CHAPTER 14: WACIC Wanted Persons File SECTION 02: Inquiries


Effective Date: August 1, 2006 See Also: CALEA:

I. PROCEDURE

A. Syntax

Field Example Header W; Message Key QW Originating Agency Identifier WA0340500 Name DOE, JOHN J Sex M Race W Date of Birth 19500101 Other identifiers SOC/, OLN/, WAC/, etc. Investigation Field INV/INV or ALL Attention Field ATN/SGT. SMITH, JOHN J Related Search Hits RSH/Y Expanded Name Search ENS/Y End of Text (send)

1. Inquiries made with the NAM, SEX, RAC, and DOB can be either MFC

driven or positional. If MFC’s are used (NAM/, SEX/, RAC/, DOB/) those fields immediately follow the ORI in the inquiry. If MFC’s are not used, then the inquiry is “positional” and the fields must be in the order shown above with each field accounted for even if not filled. Inquiries using other numerical identifiers (SOC, OLN, MNU, WAC, NIC, etc.) must have the MFC’s preceding those identifiers.



Revised 10/2010

B. Operational Inquiries

1. WACIC/NCIC Inquiry

a. Message keys W or QW: This type of inquiry is used to check on persons in the WACIC/NCIC files.

Examples: By NAM-SEX-RAC-DOB, no MFC’s W;W..DOE, JON J.M.W.19450101(send)

By NAM-SEX-RAC-DOB with MFC's W;W..NAM/DOE, JOHN J.SEX/M.RAC/W.DOB/19500101(send) By NAM-DOB-SOC with MFC's W;W..NAM/DOE, JOHN J.DOB/19500101.SOC/123456789(send)

By NAM-SEX-RAC-DOB with optional INV field W;W..DOE, JOHN J.M.W.19500101.INV/ALL(send) By NAM-SEX-RAC-DOB with optional ATN field W;W..DOE, JOHN J.M.W.19500101.ATN/SGT SIMS, JOE (send) By NAM-SEX-RAC-DOB with optional INV and ENS fields W;W..DOE, JOHN J.M.W.19500101.INV/ALL.ENS/Y(send) By WAC W;QW..WAC/05W1234567(send)

BY NIC W;QW..NIC/W123456789(send)



Revised 10/2010

2. WACIC Wanted Only Inquiry

b. This inquiry will result in a search of the WACIC Wanted Person Files only and a search of all NCIC Person Files.

By NAM-SEX-RAC-DOB, no MFC's W;QWO..DOE, JOHN J.M.W.19500101(send) By NAM-SEX-RAC-DOB with optional INV field W;QWO..DOE, JOHN J.M.W.19500101. INV/ALL(send) By NAM-SEX-RAC-DOB with optional ATN field W;QWO..DOE, JOHN J.M.W.19500101.ATN/SGT SMITH, JOHN J(send) By NAM-SEX-RAC-DOB with MFC's W;QWO..NAM/DOE, JOHN .SEX/M.RAC/W.DOB/19500101(send)

By NAM-DOB-SOC with MFC's W;QWO..NAM/DOE, JOHN J.DOB//19500101.SOC/123456789 (send)

3. QDD Query Dental Data

a. Message key QDD: This type of inquiry is used to retrieve dental information on persons in the WACIC files.

b. Syntax

Field Example

Header W; Message Key QDD Originating Agency Identifier WA0340500 Name DOE, JOHN J Date of Birth 19500101 Sex M Race W Other identifiers SOC/, OLN/, WAC/, etc.

c. Each field is identified by the appropriate message field code, followed by a forward slash (/), then the data. If the name is present, at least one numeric identifier: DOB, SOC, FBI, MNU, OLN, LIC, LIS, VIN, OCA, WAC, NIC must be in the transaction. SEX and RAC are optional. If LIC is entered, LIS is required.



Revised 10/2010

WAC or NIC must be from a wanted person, missing person, protection order, or person of interest record.

4. WACIC/NCIC and DOL Inquiry

a. Message key DW: This inquiry is used to check WACIC and NCIC for any person records and to obtain a driver’s check from Washington’s driver license file. The ACCESS computer reformats your inquiry and transmits the name and date of birth to the Department of Licensing (DOL) for a driver’s check. Only inquiries that include NAM and DOB are forwarded to DOL. Additional numeric identifiers (SOC, MNU etc.) are not included in the DOL inquiry. Examples:

By NAM-SEX-RAC-DOB, no MFC's W;DW..DOE, JOHN J.M.W.19500101(send) By NAM-SEX-RAC-DOB with optional INV field W;DW..DOE, JOHN J.M.W.19500101.INV/ALL(send) By NAM-SEX-RAC-DOB with optional ATN field W;DW..DOE, JOHN J.M.W.19500101.ATN/SGT SMITH, JOHN J(send) By NAM-SEX-RAC-DOB with MFC's W;DW..NAM/DOE, JOHN J.SEX/M.RAC/W. DOB/19500101(send) By NAM-DOB-SOC with MFC's W;DW..NAM/DOE, JOHN J.DOB/19500101. SOC/1234567893(send)

5. Interpol Inquiries

a. Wanted Person Inquiry (IPQ) Mask

1. Message Key IPQ: This inquiry checks Interpol quires and responses run against the Wanted Person Files.

2. Enter ORI, NAM and DOB. Press Send button. If there is

a possible match, an ID number will be in the IPR message. Use this ID number to run Full Person Detail Query (FPQ).



Revised 10/2010

b. Full Person Detail Inquiry (FPQ) Mask

1. Message Key FPQ: This inquiry further searches for a person detail response based on Entity ID.

2. Enter ORI and Entity ID (EID) number found in IPR

message. Press Send button, an FPR response will be sent with the person detail.

6. Wanted Person/Criminal History

a. Message key QWH: This inquiry checks WACIC and NCIC for person records and obtains a criminal history check from the Washington State criminal history files and the NCIC III criminal history files. These inquiries must be logged in the agency’s criminal history log. W;QWH.WA0340500.ATN/K ANDERSON.NAM/DOE, JOHN J. SEX/M.RAC/W.DOB/19500101.PUR/C(send)

b. The inquiry must contain one of the following combinations of identifiers:

(1) NAM-SEX-RAC-DOB (2) NAM-SEX-RAC-DOB-SOC (3) NAM-SEX-RAC-DOB-MNU (4) NAM-FBI (5) NAM-SOC (6) NAM-MNU (7) NAM-SID

7. Inquiry Using Vehicular Data

a. Message key QV: An inquiry by LIC, LIS, and/or VIN will also identify a wanted person or missing person record that the vehicular and/or license plate data has been entered. It is also possible to make an inquiry of the Wanted person File using message key code QW with LIC, LIS, and/or VIN. An inquiry of this type will also check all persons and vehicle files in both WACIC and NCIC. It is not necessary to include the name in this type of inquiry.



Revised 10/2010

8. NCIC Inquiry

a. NCIC is available for direct inquiries only when WACIC is down. However, since the ACCESS system split’s the inquiries to NCIC, it is not necessary to send a direct NCIC inquiry when WACIC is down. Therefore, the following information on NCIC inquiries is provided for reference only. The NCIC inquiry format requires use of full MKE (QV), ORI, and message field codes. Example: By NAM-SEX-RAC-DOB with MFC’s N;QW..NAM/DOE, JOHN J.SEX/M.RAC/W.DOB/19500101(send) Caution: When the WACIC computer is not available, all entries for WACIC are held by the ACCESS computer until WACIC becomes available. It is possible during WACIC down times that a wanted person entry will be waiting in queue and will not be listed in NCIC.

9. WACIC Search Procedure

a. The WACIC name search is based on the Soundex algorithm. It phonetically converts all the components (first, middle, and last names) of the query name.

b. A weighted score is assigned to each component based on whether

there is an exact or phonetic match. Since all components of the name are scored, it is beneficial to include as much of the name as possible in the query.

c. A weighted score is also applied to the components of the query

DOB (month, day, and year). A sum of the name score and the DOB score is calculated. The top 20 candidates are returned with the highest-scored appearing first. Any matched records with DOB falling outside of plus or minus 10 years from the query DOB will not be included in the candidate list. Exact matches result in a full record response. As implemented, near matches are returned in an abbreviated format containing all necessary identifiers for subsequent searches.

d. In addition, first and middle names are reversed and used in the

search. Common nicknames are converted to full names that are



Revised 10/2010

then searched. Components of hyphenated last names are reversed and searched as well as each component of the hyphenated last name.

e. If the inquiry includes the Expanded Name Search field (ENS/Y)

then additional searches are generated using each input name part as a last name, interchanging the remaining name parts as given names. For example, Bryan Morgan Lee, Lee Morgan; Morgan, Lee Bryan; Morgan, Bryan Lee; Lee, Morgan Bryan; and Lee, Bryan Morgan.

10. NCIC Search Procedure

a. When an inquiry includes both the NAM and the DOB, primary hits

are determined by using a phonetic encoding of the last name and an exact match on the input month and day of birth and a range of plus or minus one year on the input year of birth.

b. If the input last name corresponds to a list of NCIC 2000

nicknames, it is replaced by a corresponding proper name specified in the nickname for search purposes. For example, Bill is replaced with William and Betty is replaced with Elizabeth.

c. If the input last name contains a hyphen, primary hits are

determined by using each hyphenated name part as the last name as well as all combinations of the hyphenated name parts. For example, a surname of Saenz-Parada-Lopez will be searched as Saenz-Parada-Lopez, Saenz- Lopez-Parad, Lopez-Parada-Saenz, Lopez-Saenz-Parada, Parada- Lopez-Saenz, Parada-Saenz-Lopez, Saenz, Parada, and Lopez.

d. Here is a list of the Race Field Codes and the race codes that will

be searched when each is included in an inquiry:

Race Code in Inquiry Race Codes Searched

A (Asian or Pacific Islander) All

I (American Indian or Alaskan Native)

All

B (Black) All except W

W (White) All except B

U (Unknown) All



Revised 10/2010

e. When the inquiry contains a name and an alpha-numeric identifier other than the DOB (SOC, FBI etc.), a name search is not generated. In this situation, only the alpha-numeric identifier is searched.

f. If an alpha-numeric identifier is not available, an alphabetical

search by NAM can be requested. Agencies must contact the FBI/Investigative and Operational Assistance Unit at (304) 625-3000.

g. A juvenile offender (Category 2) positive record response is

restricted to those agencies in states that have signed the Rendition Amendment to the Interstate Compact on Juveniles (ICS). Only those agencies located in Rendition states are allowed access to Category 2 records.

11. Additional Guidelines for Inquiries

a. An inquiry of the Wanted Person File may be made by name and one, more than one, or all of the following alphanumeric identifiers: complete DOB, including month, day, and year; FBI; MNU; SOC; and OLN, with each search element except NAM and DOB preceded by the proper MFC. Additionally, inquiries may be made using vehicle data, NAM and OCA, WAC only, or NIC only with each data element preceded by the proper MFC.

b. If an inquiry to WACIC on a wanted person results in a positive

response (hit) and that record was initially entered with a SID or

PCN, then the descriptor portion (and any alias information) from

WASIS will be appended to the bottom of the WACIC record for

viewing.

c. This descriptor information is not searchable because it was not

part of the base record. The WASIS information is displayed because of the association with a SID or PCN. The WASIS information does not and will not automatically populate the fields in the base record.



Revised 10/2010

d. A name search inquiry on a wanted individual will only search

information entered into the base record. A WACIC inquiry on an

alias name from the WASIS displayed information will not produce

a hit unless the alias name had previously been entered into

another WACIC record.

e. When only one numeric identifier is used in a Wanted Person File

inquiry, the response(s) will include only the record(s) on file containing that specific numeric identifier (e.g., SOC, OLN, FBI, etc.).

f. For example, if an inquiry contains only an FBI, the response(s) will

include the record(s) on file with that FBI number, even though there may be other records on file for the same individual which does not contain an FBI number. However, if an inquiry is made using a numeric identifier other than the FBI number, and the record on file contains an FBI, NCIC will generate a second search using FBI to provide any other matching record(s).

g. This "second" search is only performed when the record produced

contains an FBI and is only performed by NCIC. Therefore, an agency making an inquiry with limited personal descriptors should make a second inquiry using all available identifiers contained in the response record(s) to ensure the receipt of all records on file which could possibly pertain to the person in question.

h. If a positive response (hit) includes vehicle or license plate data in

the wanted person record, the Vehicle File should be queried to ascertain if the vehicle and/or license plate is stolen.

i. NCIC includes caveats as part of a positive response to distinguish

ATF Violent Felon, Foreign Fugitive, Gang and Known or Suspected Terrorists, and Protection Order records from wanted person records. When an agency receives a juvenile offender (EWJ) record(s) from NCIC in response to an inquiry, the following caveat will be furnished:

IMMED CONFIRM RECORD WITH ORI AND FOLLOW

PROCEDURES IN INTERSTATE COMPACT ON JUVENILES



Revised 10/2010

The following caveat will be furnished when the juvenile is emancipated: IMMED CONFIRM RECORD WITH ORI AND FOLLOW

PROCEDURES IN INTERSTATE COMPACT ON JUVENILES.

CAUTION: THIS JUVENILE IS EMANCIPATED.

PLEASE CHECK YOUR STATE LAWS REGARDING APPROPRIATE

ACTION.

C. Responses

1. WACIC/NCIC Responses

a. WACIC No Record Response

WWCIC TIME: 1617 DATE: 042705 TO: ABCPD

QW.WA0340500.NAM/DOE, JOHN J.DOB/19500101

NO WACIC WANTED, MISSING, PROTECTION ORDER,

DOC CUSTODY STATUS, SOR, OR VEHICLE/VEHICLE PART OR

WATCH YOUR CAR RECORDS FOUND

b. WACIC Positive Hit Response


QW.WA0340500.NAM/DOE, JOHN J.DOB/19500101

------ RECORD NUMBER 1 OF 1 ------

FELONY WARRANT (BASED ON DOB,NAM)

MKE/EWF ORI/WA0340500 NAM/DOE, JOHN J

.M.W.WA.01011950

HGT/511 WGT/200 EYE/BRO HAI/BRO

OCA/TEST123

OFF/4809

OFL/UNAUTH COMMUNICATION WITH PRISONER

DOW/04/05/2005 ORC/WA034013J

TOW/FS

MIS/TEST RECORD TEST RECORD

ENT: 04/27/2005 AT 1621 FROM ABCPD BY/PD ANYTOWN

(ABCPD)

UPD: 04/27/2005 AT 1622 FROM WAC/05W0071505



Revised 10/2010

c. NCIC No Record Response

NCIC TIME: 1615 DATE: 042705 TO: ABCPD

WA0340500

NO NCIC WANT NAM/DOE, JOHN J D0B/19500101

d. NCIC Positive Hit Response


WA0340500

MKE/WANTED PERSON

ORI/DSE/20500415 NAM/DOE, JOHN J SEX/M RAC/W POB/WA

DOB/19500101

HGT/511 WGT/200 EYE/BR0 HAI/BRO FBI/123456A SKN/MED

FPC/DIPMPMP013POPOCOPI13 MNU/OA-AB1234512

SOC/555555555

OFF/DAMAGE PROP - PUBLIC-WITH EXPLOSIVE

DOW/20050405 OCA/TEST-TEST

MIS/TEST REC0RD TEST REC0RD

ORI IS SHERIFF’S OFFICE THURSTON COUNTY OLYMPIA 360

555-1212

NIC/W370679163 DTE/20050427 1926 EDT

IMMED CONFIRM WARRANT AND EXTRADITION WITH ORI

e. NCIC Positive Response Containing DETAINER Information

1L01HEADER

WV1100010

WARNING- A DETAINER HAS BEEN FILED FOR THE SUBJECT OF

THIS RECORD.

PLEASE CONTACT ORI TO OBTAIN ADDITIONAL

INFORMATION.

MKE/DETAINED WANTED PERSON – CAUTION SUICIDAL

ORI/WA0130000 NAM/DOE, JOHN J SEX/M RAC/W POB/OH

DOB/19701010 HGT/510 WGT/175 EYE/BRO HAI/BRO FBI/416249J4

SKN/FAR SMT/SC L EAR FPC/121011CO141159TTC113 MNU/AS-

375145249 SOC/375145249 OLN/N222333444 OLS/MD OLY/2002

OFF/HOMICIDE - WILLFUL KILL - FAMILY - GUN

DOW/20051227 OCA/05-4889



Revised 10/2010

ORI IS ANY CITY CORRECTIONS AGENCY 301 555-1234

LOCATED/20050224 PA2020000 A345234 DETN

DOD/20050315 DNO/05-1234567890 IRI/PA202230C DIS/20050315

DSE/20050415

INC/PENNSYLVANIA STATE PEN

NIC/W123456789 DTE 20051228 0830 EDT


f. WACIC Positive Response Containing DETAINER Information

------ RECORD NUMBER 1 OF 1 ------

DETAINED WANTED PERSON (BASED ON WAC)

MKE/EDW ORI/WAWSP0001 NAM/SCHMO, JOE HENRY.

M.W. .02/02/1972

HGT/500 WGT/090 HAI/BLK

OCA/TESTOCA

OFF/0001

DOW/11/11/2005

TOW/MS WAR/WAR1234

MIS/EXTRADITION STATE WIDE

--- L O C A T E D R E C O R D --- ** LOCATED/02/02/2005

WAWSP0000 DETN WARNING- A DETAINER HAS BEEN FILED

FOR THE SUBJECT OF THIS RECORD. PLEASE CONTACT

WAWSP0001 TO OBTAIN ADDITIONAL INFORMATION. AGENCY

NAME/ACCESS OPERATIONS AGENCY TELEPHONE/360-705-5778

ENT: 08/23/2005 AT 1346 FROM ACESS BY/ACCESS OPERATIONS

(ACCSS) UPD: 08/23/2005 AT 1348 FROM ACESS WAC/05W0000046

g. Interpol Response

(1) Wanted Person (IPR Response)

IPR.DCINTER00 13:33 06/01/2009 24029 WAWSP0006 13:33 06/01/2009 39794 TXT Possible Interpol Matches: Subject: NLETS TEST IPQ DOB: 1989-09-09 ID: 2009/15367



Revised 10/2010

Original Query Data Name:IPQ,NLETS DOB:1989-09-09

(2) Full Person Detail (FPR Response)

FPR.DCINTER00 13:59 06/01/2009 41311 13:59 06/01/2009 25070 WAWSP0006 TXT Interpol Record Your query of the Interpol ASF database has resulted in a positive "hit" and an alarm message has been sent to the country that submitted the information and the Interpol-United States National Central Bureau (USNCB) at the U.S. Department of Justice in Washington, D.C. If further investigation of available identification/identifiers of the subject results in a match with the name and date of birth in the Interpol record, you must contact the USNCB immediately at (202) 616-3900 to confirm the validity of the information obtained and coordinate any follow-up action on the information. NOTE: Under U.S. Law, the existence of charges in another Country alone DO NOT authorize the subjects arrest in the United States. However the foreign charges and the present circumstances MAY provide a basis under the laws and regulations applicable to your jurisdiction to detain the subject, at least temporarily, in order to obtain additional information. Subject Information Name: IPQ,NLETS TEST DOB: 1989-09-09 Person Qualification: NOT_CRIMINAL Metadata Original Query Data Entity ID: 2009/15367



Revised 10/2010

CHAPTER 14: WACIC Wanted Persons File SECTION 03: Fields and Edits



I. DEFINITIONS

A. Message Keys

Entry Modify Locate Clear Cancel

Wanted Felony EWF* MWF LWF CWF XWF

Temporary Felony ETF* MTF LTF CTF XTF

Wanted Misdemeanor EWW* MWW LWW CWW XWW

Wanted Juvenile EWJ* MWJ LWJ CWJ XWJ

Supplemental Data EN XN

Stolen/Fraudulent ID ENS XNS

Detainer EDW XDW

1. A caution indicator, “C” can be added to the message key EWW, EWF, ETF, or EWJ when it is known that an individual is armed and dangerous, has suicidal tendencies, has previously escaped custody, is a drug addict, or whatever is appropriate to the particular circumstances of the individual. The reason for the caution must be entered in the Cautions and Medical Conditions (CMC) field.

B. Fields and Edits

Field Name MFC Length Required? Data Type

Header Y

Message Key MKE 4 Y A

Originating Agency Identifier

ORI 9 Y A, N

Name NAM 30 Y A, N, S

Sex SEX 1 Y A



Revised 10/2010


Race RAC 1 Y A

Place of Birth POB 2 N N

Date of Birth DOB 8 C A

Height HGT 3 Y N

Weight WGT 3 Y N

Eye Color EYE 3 N A

Hair Color HAI 3 Y A

FBI Number FBI 9 C A, N

Skin Tone SKN 3 N A

Scars-Marks-Tattoos SMT 10 N A

Fingerprint Classification FPC 20 N A, N

Miscellaneous Number MNU 15 C A, N, S

Social Security Number SOC 9 C N

Operator's License Number OLN 20 C A, N

Operator's License State OLS 2 C A

Operator's License Year OLY 4 C A,N

Date of Warrant DOW 8 Y N

Originating Agency Case number

OCA 20 Y A, N, S

Linkage Agency Identifier LKI 9 N A, N

Linkage Case Number LKA 20 N A, N, S

Miscellaneous MIS 500 C A, N, S

Notify Originating Agency NOA 1 N A

Type of Warrant TOW 2 Y A

Offense Code OFF 24 Y N

Offense Literal OFL 46 N A, N, S

Original Offense Code OOC 4 N N

Amount of Bail AOB 10 N N

Warrant Number WAR 15 N A, N

Originating Court ORI ORC 9 N A, N

License Plate LIC 10 C A, N

License State LIS 2 C A

License Year LIY 4 C N or NX

License Type LIT 2 C A

Vehicle Identification Number

VIN 20 C A, N

Vehicle Year VYR 4 C N

Vehicle Make VMA 24 C A

Vehicle Model VMO 3 C A, N

Vehicle Style VST 2 C A, N Vehicle Color VCO 7 C A, S Caution and Medical Conditions

CMC 2 N N

State Identification Number SID 10 N A, N Process Control Number PCN 9 N A, N Stolen/Fraudulent NAM NAM 30 C A, N, S Stolen/Fraudulent DOB DOB 8 C N Stolen/Fraudulent SOC SOC 9 C N Stolen/Fraudulent MNU MNU 15 C A, N, S



Revised 10/2010


Stolen/Fraudulent OLN OLN 20 C A, N Stolen/Fraudulent OLS OLS 2 C A Stolen/Fraudulent OLY OLY 4 C N or NX DNA Profile Indicator DNA 1 N A DNA Location DLO 250 N A, N, S Extradition Limits EXL 2 N N Expiration Date EXD 8 N N Pack the Record PACK 1 Y A Required: Y – Yes Data Type: A – Alphabetic

N – No N – Numeric

C – Conditional S – Special Characters

1. MKE (Message Key)

a. The MKE must be a valid message key as shown above.

2. ORI (Originating Agency Identifier)

a. The ORI must be a valid NCIC-assigned ORI. The first two

characters must be alphabetic.

3. NAM (Name)

a. The NAM field must contain a minimum of five and a maximum of 30 characters including alphabetic characters, one comma, hyphen(s), and spaces. The comma must follow the last name with no more than one space after the comma. Personal Descriptors of the NCIC Code Manual provides coding instructions.

4. SEX (Sex)

a. The SEX field must contain a valid code as listed in the Personal Descriptors of the NCIC Code Manual.

5. RAC (Race)

a. The RAC field must be a valid code as listed in the Personal

Descriptors of the NCIC Code Manual.



Revised 10/2010

6. POB (Place of Birth)

a. The POB field must contain a two-character alphabetic code from the State and Country Data Codes of the NCIC Code Manual.

7. DOB (Date of Birth)

a. The DOB field must contain eight numbers representing year,

month, and day in that order (YYYYMMDD). Days cannot be more than the maximum for the month. The DOB cannot be a current date or any date one day through 9 years and 364 days prior to the current date. This allows for the entry of age 10 years through 99 years 364 days. If the MKE is EWJ, the DOB must be such that the person is less than 18 years of age. Unless it is a leap year, the date February 29 (XXXX0229) will not be allowed.

8. HGT (Height)

a. The HGT field must contain three numeric characters. The first

character must be 4, 5, 6, or 7. The second character must be zero or one. The first character represents feet and the second and third represent inches. This field may be a minimum of 400 and a maximum of 711.

9. WGT (Weight)

a. The WGT field must contain three numeric characters. It must be

a minimum of 50 (050) pounds and a maximum of 499 pounds.

10. EYE (Eye Color)

a. The EYE field must contain a three character alphabetic code from the Personal Descriptors section of the NCIC Code Manual.

11. HAI (Hair Color)

a. The HAI field must contain a three character alphabetic code from

the Personal Descriptors section of the NCIC Code Manual.



Revised 10/2010

12. FBI (FBI Number)

a. The FBI field must contain one to nine characters. It may be up to seven numeric or one to six numeric followed by an alphabetic character A through H; or one to six numeric followed by an alphabetic character J through Z followed by one or two check digits; or one to six numeric followed by two alphabetic characters followed by one check digit. If the number contains one alphabetic character (J-Z), the check digit will be 1 to 11. If the number contains two alphabetic characters, the first alphabetic cannot be B, G, I, O, Q, S, U, Y, OR Z.

b. The second alphabetic must be A, B, or C, and the check digit will be 0 to 9. The alphabetic characters I and O are always invalid.

13. SKN (Skin Tone)

a. The SKN field must contain a three character alphabetic code from


14. SMT (Scars, Marks, and Tattoos)

a. The SMT field must contain a valid code from the Personal Descriptors section of the NCIC Code Manual.

15. FPC (Fingerprint Classification)

a. The FPC field must contain 20 alphabetic and/or numeric

classification characters from the Personal Descriptors section of the NCIC Code Manual.

16. MNU (Miscellaneous Identifying Number)

a. The MNU field must contain a minimum of four and a maximum of 15 characters. The first two characters must be a valid two- character alphabetic code from the Personal Descriptors section of the NCIC Code Manual. The third character must be a hyphen. Entry of one zero only or a run of zeros only is prohibited in positions 4 through 15. An originating agency police or identification number in MNU cannot be the only numeric identifier in the record.



Revised 10/2010

17. SOC (Social Security Number)

a. The SOC field must contain nine numeric characters not less than 001010001. The SOC cannot have a value of 8 or 9 in the first position or have a value of 00 in the fourth and fifth positions.

b. Entries of invalid and/or non-issued numbers are allowed. With

each entry of this type, a caveat will be generated by NCIC stating the SOC has not been assigned and the agency should check for a possible data entry error.

18. OLN (Operator License Number)

a. The OLN must not be more than 20 alpha-numeric characters.

One zero only or a run of zeros only is not allowed. If the OLN is entered, the OLS and OLY fields must also contain information.

19. OLS (Operator License State)

a. The OLS field must contain a two character alphabetic code from


20. OLY (Operator License Year of Expiration)

a. The OLY field must contain four numeric characters representing the expiration year of the operator license or the alphabetic NX to represent a non-expiring license. The OLY is required when the OLN field is entered.

21. DOW (Date of Warrant)

a. The DOW field must contain eight numeric characters representing

the year, month, and day in that order. It must equal or be less than the current date. Days cannot be more than the maximum for the month. Unless the year is a leap year, the date February 29 will not be allowed. For Wanted Juvenile records, the Date of Violation (DOV) is entered in this field.



Revised 10/2010

22. OCA (Originating Agency Case Number)

a. The OCA field contains a maximum of twenty alphanumeric characters. It must not contain a single zero or a run of zeros only, the word NONE, or the first seven characters of the ORI field. The only valid special character is a hyphen.

23. LKI (Linkage Agency Identifier)

a. The LKI field contains nine alphanumeric characters. It must be a

valid NCIC 2000 assigned ORI. The LKI and LKA cannot be identical to the ORI and the OCA. LKI and LKA are entered as a set.

24. LKA (Linkage Case Number)

a. The LKA field contains a maximum of 20 alphanumeric characters. It must not contain a single zero, a run of zeros only, a single alphabetic only, or the word NONE. The first seven characters of the LKA cannot equal the first seven characters of the LKI. The only valid special character is a hyphen. The LKA must be valid for the LKI (there must be an ORI and matching OCA in the system).

b. The linkage ORI and OCA fields are provided as separate fields to

associate incidents that are handled by multiple departments. An agency entering a record that shares the same incident of a record entered by a different ORI and/or OCA can link the records by entering the associated ORI and OCA in the linkage fields (LKI and LKA). The record will be rejected if the LKI/LKA fields are the same as the first seven characters of the LKI.

c. If an inquiry contains RSH/Y, secondary hit responses will be

returned for all records with the same ORI/OCA contained in the primary hit response and all records linked by the LKI/LKA contained in the primary hit response.

25. MIS (Miscellaneous Field)

a. The MIS field contains a maximum of 500 characters. Extradition

limits must be expressed clearly if the Extradition Limits (EXL) field contains a code that requires further explanation.



Revised 10/2010

b. For the codes VMA/AERO, ATV, COEQ, CYL, FARM, SNOW, SPEC, TRLR, OR TRUK, the MIS field must include the name of the manufacturer. If the OFF code is 0199, 0299, 0399, 4901, 5005, 5011, 5012, 5015, 5099, 7099, 7199, 7299, or 7399, the MIS field must contain an explanation of the offense.

c. SVIN must be the first four characters in the MIS field if the VIN is

a state assigned or non-conforming 17 character VIN.

d. When an agency makes wanted person entries on two or more persons who are known to associate with each other, each record entry should be cross-referenced with the other. To cross- reference, place the name and WAC and/or NIC of each wanted person’s record in the MIS field of the other’s record with an appropriate explanatory notation. An agency receiving the record of one of the fugitives will then have the information needed to obtain additional records. This does not take the place of making appropriate entries in the linkage fields (LKI and LKA).

e. If an ORI has entered a subject and the same ORI obtains a

warrant for that subject on another charge, the second charge and date of warrant should be entered in the MIS field.

26. NOA (Notify Originating Agency)

a. If an entering agency believes notification each time its record is

hit will provide investigative leads, regardless of whether the location of the property or person is known, enter Y in the NOA field. If this field is left blank, it defaults to N for no.

27. TOW (Type of Warrant)

a. The TOW field must contain one of the following:

(1) FN - Felony Warrant WACIC/NCIC (2) FS - Felony Warrant WACIC only (3) MN – Misdemeanor National WACIC/NCIC (4) MS - Misdemeanor Warrant WACIC only



Revised 10/2010

28. OFF (Offense Code)

a. The OFF field must contain a 4-24 character numeric code from Uniform Offense Codes of the NCIC Code Manual. If the first four characters of the OFF are 0199, 0299, 0399, 4901, 5005, 5015, 5099, 7099, 7199, 7299, or 7399, free text or an easily understood abbreviation further explaining or describing the offense must be entered in positions 5 through 24. If the code 0201 or 0299 is used, the ORI must be military or FBI. Any offense code found in the NCIC Code Manual can be used except 4901, 4902, or 4999 when EWJ or EWJC is entered.

29. OFL (Offense Literal)

a. The OFL field contains a maximum of 46 alpha-numeric free text

characters used to further describe the offense entered in the OFF field.

b. The text entered in this field will be appended to the Offense Code

translation shown in the Uniform Offense Codes of the NCIC Code Manual on subsequent WACIC hits. You should not repeat the offense code translation in the OFL field or it will appear twice in a response.

c. Since there is no OFL field in NCIC, the text entered in this field is

added to the end of the MIS field when a qualifying record is forwarded to NCIC. If this causes the MIS field to exceed the maximum allowable characters the text will be truncated.

30. OOC (Original Offense Code)

a. The OOC field must contain a four character numeric code from

the Uniform Offense Codes section of the NCIC Code Manual. Entry of OOC is required (and permitted only) when OFF is 4901, 4999, 5001, 5002, 5011, 5012, 5013, 5014, 5015, 8100, 8101, or 8102. If OOC is 8100, 8101, or 8102, then the FBI field should contain data.



Revised 10/2010

31. AOB (Amount of Bail)

a. The AOB field contains a maximum of 10 numeric characters to represent the amount of bail in dollars or the words NO BAIL. This field must be left blank for temporary felony warrants (MKE/ETF).

32. WAR (Warrant Number)

a. The WAR field contains a maximum of 15 characters. Permissible values are: A-Z, 0-9. Special characters, including the hyphen are not allowed. This field must be left blank for temporary felony warrants.

33. ORC (Originating Court Identifier)

a. The ORC field contains a valid NCIC assigned ORI for the court

issuing the warrant. The first two characters must be alphabetic.

34. LIC (License Plate Number)

a. The LIC field contains a maximum of ten alphanumeric characters. The characters UNK, UNKN, or UNKNOWN are not allowed. If the VMA is AERO, LIS will be US, and the LIT is PP or NP, the first character in the LIC field must be the alphabetic N. If the LIC field is entered, the LIS, LIY, and LIT fields must be entered.

35. LIS (License Plate State)

a. The LIS field must contain a two character alphabetic code from

the State and Country Data Codes of the NCIC Code Manual. It must be entered if the LIC field is filled.

36. LIY (License Plate Year of Expiration)

a. The LIY field must contain four numeric characters representing the current year minus 1; or later than the current year; or the alphabetic NX to represent a non-expiring registration. It must be entered if the LIC field is filled.

37. LIT (License Plate Type)

a. The LIT field must be a valid code from the Vehicle Data Codes of

the NCIC Code Manual. It must be entered if the LIC field is filled.



Revised 10/2010

38. VIN (Vehicle Identification Number)

a. The VIN field cannot contain a single zero, a run of zeros only, a single alphabetic character only, or all alphabetic characters only, indicating the vehicle identification number is unknown.

b. If it is a state-assigned or non-conforming 17 character VIN, SVIN must be entered as the first four characters of the MIS field. If the VIN exceeds 20 characters, only the last 20 characters should be entered in the VIN field. The full VIN must then be shown in the MIS field. If the VIN is entered, the VYR, VMA, VMO, VST, and VCO must also be entered.

39. VYR (Vehicle Year)

a. The VYR field must contain four numeric characters representing

the production (model) year during which the vehicle was manufactured. The year cannot be more than one year beyond the current model year. For entries of model year 1981 or later and when the VIN is 17 characters, the tenth position (vehicle year)of a VIN must be compatible with the VYR. It must be entered if the VIN field is filled.

40. VMA (Vehicle Make)

a. The VMA field contains up to 24 characters. The first four

characters must be alphabetic and a valid NCIC 2000 assigned code as listed in Section 4, Vehicle Data Codes of the NCIC Code Manual. If the VMA code is less than four characters and data is included in positions 5 through 24, positions 3 and/or 4 should be blank. The remaining characters are free text and must contain the name of the manufacturer when the VMA code is AERO, ATV, COEQ, CYL, FARM, SNOW, SPEC, TRLR, or TRUK. If the VMO is TL, the codes must not be ASM, ASMB, ASSE, ASSM, MB, MC, MP, MS, NA, TK, TL, UNK, UNKN, XX, XXX, XXXX, YY, YYY, YYYY, ZZ, ZZZ, or ZZZZ.

41. VMO (Vehicle Model)

a. The VMO field must be entered if the VIN field is filled. VMO edits

are provided in the Vehicle File Section of this manual.



Revised 10/2010

42. VST (Vehicle Style)

a. The VST field must a be a valid code listed in the Vehicle Data Codes of the NCIC Code Manual. It must be entered if the VIN field is filled. Further information reference the VST field may be found in the Vehicle File Section of this manual.

43. VCO (Vehicle Color)

a. The VCO code must be a valid color code from the Vehicle Data

Codes of the NCIC Code Manual. If seven characters, the fourth must be a slash (/). The VCO field must be entered if the VIN field is filled.

44. CMC (Caution and Medical Conditions)

a. The CMC field must be a valid NCIC assigned code as listed in the

Personal Descriptors Section of the NCIC Code Manual. If the caution indicator is added to the entry message key (MKE), this field must contain the reason for the caution.

45. SID (State Identification Number)

a. The SID field contains a maximum of 10 alpha-numeric characters.

If the SID begins with “WA” then:

(1) It must have a length of 10 and, (2) a valid check digit.

b. Otherwise:

(1) The first two characters must be a valid State Code and, (2) have a length of 3-10 characters.

46. PCN (Process Control Number)

a. The PCN field contains nine alpha-numeric characters. WACIC

edits the PCN number assigned to a criminal history record. It carries out a weighted positional check digit routine.



Revised 10/2010

47. EXL (Extradition Limits)

a. The EXL field must be a valid NCIC assigned code as listed in the Personal Descriptors Section of the NCIC Code Manual. If this field is left blank, it will default to 2 (LIMITED EXTRADITION) for felony warrants or B (LIMITED EXTRADITION SEE MIS FIELD) for misdemeanor warrants. Extradition limits must be expressed, in clear language, in the MIS field if this field contains a code that requires further explanation.

48. EXD (Expiration Date)

a. The EXD field must contain eight numeric characters representing

year, month, and day in that order. Days cannot be more than the maximum for the month. Unless the year is a leap year, February 29 will not be allowed. The WACIC record will be purged on the date contained in this field.

49. PACK (Pack the Record)

a. If the PACK flag is set to Y for YES, the record will be packed automatically using the SID, FBI, or PCN entered in the record. For manual packing of the record you may choose N for NO. If left black the record will default to Y for YES.

50. WAC (WACIC Number)

a. The WAC number consists of the year of entry and the letter W,

followed by seven numbers that are automatically assigned by WACIC to each accepted entry. For example: 06W1234567.

51. NIC (NCIC Number)

a. The NIC number consists of an alphabetic character (W in the

Wanted Person File) followed by nine numeric characters, that are automatically assigned by the NCIC system to each accepted felony and serious misdemeanor record. It must have a valid check digit when used to identify a record in a subsequent transaction.



Revised 10/2010

52. DOE (Date of Emancipation)

a. The DOE field will appear only on hits received from NCIC for Wanted Juvenile (EWJ) records. It is automatically calculated by WACIC when an entry for a wanted juvenile is forwarded to NCIC.

53. DNA (DNA Profile Indicator)

a. The DNA field must contain a Y or N. It defaults to N. If an agency enters Y, then the DLO field must be filled.

54. DLO (DNA Location)

a. The DLO field contains a 250 character free text field to explain the

location of the DNA sample and contact information. If the DNA field is N or defaulted to N, the DLO field must be left blank.

C. Data Field Sets

1. Some groups of fields in base or supplemental data records are treated as sets. For the Wanted Person File, these sets are:

a. OLN-OLS-OLY

b. LKI-LKA

c. LIC-LIS-LIY-LIT

d. VIN-VYR-VMA-VMO-VST-VCO

e. DNA-DLO

2. When entering, modifying, or canceling sets of data either in the base record or as supplemental data, the entire set must be entered, modified, or cancelled as a unit. Each set must be identified by its message field code (OLN/, LIC/, VIN/); you cannot preface multiple sets with one message field code. All fields in the set must be accounted for, even if not required.

3. All fields must be included, even if they are not being changed:

OLN/MILLECE515KB.WA.2005

LIC/123ABC.WA.2005.PC

4. Single identifiers can be entered, modified, or cancelled in groups with the message field code required only before the first in the group (e.g. DOB/19490805.19501120).



Revised 10/2010

CHAPTER 14: WACIC Wanted Persons File SECTION 04: Entry



I. PROCEDURE

A. Entry Mask

1. An entry format mask is provided for ACCESS WEBMSS terminals.

To retrieve the mask, enter the following transaction: F:EW(send) MKE/____ ORI/ _________ NAM/______________________________ SEX/_ RAC/_ POB/ __ DOB/________ HGT/___ WGT/___ EYE/ ___ HAI/___ FBI/ _________ SKN/ ___ SMT/ __________ FPC/ ____________________ MNU/ _______________ SOC/ _________ OLN/ ____________________ OLS/ __ OLY/ ____ DOW/________ OCA/____________________ LKI/ _________ LKA/ ____________________ MIS/ ___________________________________________________________________ NOA/ _ TOW/ __ OFF/____ OFL/ _________________ OOC/ ____ AOB/ _________ WAR/ _______________ ORC/ _________ LIC/ ________ LIS/ __ LIY/ ____ LIT/ __ VIN/ ____________________ VYR/ ____ VMA/ ________________________ VMO/ ___ VST/ __ VCO/ _______ CMC/ __ SID/ __________ PCN/ _________DNA/ _ DLO/ _________________________________________________________________ EXL/ __ EXD/ ________ S/F NAM/ ___________________________ S/F DOB/ ________ S/F SOC/ _________ S/F MNU/ ____________________ S/F OLN/ ___________________ S/F OLS/ __ S/F OLY/ ____ PACK/_ ____ REQUIRED FIELD MUST HAVE ONE: DOB,FBI,MNU,SOC OR OLN-OLS-OLY . . . ENTER WANTED PERSON FORMAT . . .



Revised 10/2010

B. Examples of Entries

1. The following examples are entries made without the entry mask.

a. Wanted Felony Entry

W;EWF.WA0340500.DOE, JOHN J.M.W.WA.19590101.511.200. BRO.BRO.123456A.FAR.SC R SHLD.XOPM14AA53DIPOCM07XX. PI-WA13423873.434984784.DOE**JJ12345.WA.2007.20050425. TEST123.WA0340100.05-4321.WA034015J.EXTR STATEWIDE CONFIRM 555-1212 TEST RECORD.Y.FS.5015.FTA BURGLARY. 010000.05-2356.WA034015J.ABC123.WA.2006.PC. 987654321AB987654.1986.TOYT.CST.2D.SIL..WA123456789....1.Y(send)

b. Temporary Felony Entry

W;ETF.WA0340500.DOE, JOHN J.M.W.WA.19500101.511.200. BRO.BRO.123456A.FAR.SC R SHLD.XOPM14AA53DIPOCM07XX. PI-WA13423873.434984784.DOE**JJ12345.WA.2007.20050425. TEST123.WA0340100.05-4321..EXTR STATEWIDE CONFIRM 555-1212 TEST RECORD.Y.FN.4809.UNAUTH COMMUNICATION WITH PRISONER....ABC123.WA.2006.PC.987654321AB987654.1986.TOYT.CST.2D.SIL..WA12345678.Y(send)

c. Misdemeanor Entry

W;EWW.WA0340500.DOE, JOHN J.M.W.WA.19500101.511.200. BRO.BRO.123456A.FAR.SC R SHLD.XOPM14AA53DIPOCM07XX. PI-WA13423873.434984784.DOE**JJ12345.WA.2007.20050425. TEST123...WA034015J.EXTR STATEWIDE CONFIRM 555-1212 TEST RECORD.N.MS.0001.FTA LITTERING.000500.TEST123.WA034015J. ABC123.WA.2006.PC.987654321AB987654.1986.TOYT.CST.2D. SIL.90.....1.20080425.Y(send)



Revised 10/2010

d. Juvenile Entry

W;EWJ.WA0340500.DOE, JOHN J.M.W.WA.19850101.511.200. BRO.BRO.123456A.FAR.SC R SHLD.XOPM14AA53DIPOCM07XX. PI-WA13423873.434984784.DOE**JJ12345.WA.2007.20050425. TEST123...WA034015J.EXTR STATEWIDE CONFIRM 555-1212 TEST RECORD.N.FN.8100.5015.NO BAIL.TEST123.WA034015J. ABC123.WA.2006.PC.987654321AB987654.1986.TOYT.CST.2D. SIL..WA12345678.Y(send)

C. Entry Acknowledgments

1. WACIC Acknowledgment


WA0340500

ENTERED EWF NAM/DOE, JOHN J

WAC/00W1234567 OCA/TEST123

05/25/05 AT 1336

2. WACIC Delayed Inquiry Response

Refer to Chapter 1, Section 2, for further explanation.

3. NCIC Acknowledgment


WA0340500

NAM/DOE, JOHN J NIC/W123456789

D. Rejecting Duplicate Records

1. WACIC Criteria

a. When an entry is made, the WACIC persons files will be searched

for any record matching by record type (wanted, missing, unidentified, etc.) and ORI. Any of the following field combinations shall be returned from the search as duplicate record and the entry will be rejected:

(1) FBI (2) SOC



Revised 10/2010

(3) MNU (4) OLN and OLS (5) NAM and DOB (6) NAM and OCA (for wanted persons and protection orders only) (7) NAM, VIN, and VMA (8) NAM, LIC, LIS, LIY, and LIT (9) NAM and RES (for protection orders only)

b. If no exact duplicate record has been identified, each record that has a different ORI and matches by record type and any of the following field combinations will be returned from the search as a possible duplicate and the record will be accepted: (1) FBI (2) SOC (3) MNU (4) OLN (5) NAM and DOB (6) VIN (7) LIC

2. NCIC Criteria

a. If the following fields of an NCIC wanted person or temporary felony want entry message are the same as those fields of a wanted person or missing person record already on file, the second entry will be rejected with the message REJECT ON FILE: FBI and ORI; MNU and ORI; SOC and ORI; OLN, OLS, and ORI; VIN, VMA, NAM, and ORI; LIC, LIS, LIY, LIT, NAM, and ORI, OCA, NAM, and ORI; and DOB, NAM, and ORI.

b. Whenever the message REJECT ON FILE is sent by NCIC 2000,

the record on file will also be transmitted.

c. A duplicate record will be accepted if the ORI in the second entry is different or the person type is other than wanted or missing, for example, Protection Order File, VGTOF, etc. A duplicate record will also be accepted if there are vehicle data in the wanted person message which match data in the Vehicle File. In those cases, the duplicate record(s) will be furnished with the acknowledgement.



Revised 10/2010

E. Additional Guidelines for Entries

1. When a warrant issued for a subject contains multiple charges, the code for the more serious charge should be entered in the Offense field (OFF) with the additional charge(s) shown in the MIS.

2. Two separate entries by an ORI on the same person should not be made. It is only necessary for an ORI to enter one record on a person, no matter how many separate charges are lodged against him/her.

3. If an ORI has entered a subject and the same ORI obtains a warrant

for that subject on another charge at a later date, the second charge and date of warrant should be entered in the MIS of the original entry. For example:

MIS/ALSO OFF/2404 DOW/120104.

4. A record in the Wanted Person File may contain a minimum number of

personal descriptors, license, and vehicle data because little was known of the individual at the time of entry. This lack of information limits the chance of a hit on the record. One possible source of additional identification data is the Interstate Identification Index (III). An inquiry (using MKE/QH) should be made prior to or soon after making the wanted person entry to determine if the criminal history record of the subject is in III. A positive response to this inquiry may reveal not only physical descriptors, identifying numbers, and aliases not known to the inquirer but also arrest, court, and/or custody supervision data which might provide investigative leads.

5. Inclusion of the FBI number in a WACIC Wanted Person File record

entry will cause the same wanted information to be posted in the subject's arrest fingerprint record maintained by the FBI CJIS Division.

F. Guidelines for Entry of a John or Jane Doe Warrant

1. In jurisdictions authorized to use “John or Jane Doe” warrants, an

agency may enter a Wanted Person File record in the name of “John Doe” or “Jane Doe” using the identifiers from the stolen or fraudulent documents provided this type of warrant has been obtained.



Revised 10/2010

2. If an arrest warrant is issued in the name of “John Doe” or “Jane Doe” the name from the stolen/fraudulent (S/F) documents should be listed as S/F. Any identifiers should be placed in the MIS Field indicating that the documents may be in the possession of “John Doe” or “Jane Doe”. FBI numbers should not be included in these types of entries.

3. If an agency is located within a jurisdiction that does not issue this type

of warrant, only those cases involving a homicide where the Wanted Person is believed to be using the victim’s identification can be entered as “John Doe” or “Jane Doe”. The criteria below list the instructions to enter “John or Jane Doe” records without a warrant. a. To allow specific identification of "John or Jane Doe" entries in

cases involving a homicide, where a warrant could not be secured, OFF/0913 has been added for use in the OFF field.

b. A variation in the DOW field will be required when the OFF/0913 is

used. Because a warrant could not be issued, the date that the investigation was opened should be entered in the DOW. Use of OFF/0913 will generate the following caveat at the end of the NCIC record: NO WARRANT. SUBJECT POSSIBLY IN POSSESSION OF

HOMICIDE VICTIM'S PERSONAL IDENTIFICATION. CONTACT

ORI IMMEDIATELY.

c. OFF/0913 is restricted to open homicide investigations where the

victim's identification was missing at the time the body was located and to agencies unable to obtain a "John or Jane Doe" warrant. The report must indicate that the victim's identification was missing and the report must be available for audit purposes by WACIC and FBI CJIS staff.

G. Vehicle or License Plate Data

1. A vehicle and/or license plate may be entered as part of a wanted

person record (EWW, EWF, EWJ, or ETF), provided the location of the vehicle and/or license plate is unknown and the entering agency has reasonable grounds to believe that the wanted person may be operating the vehicle or a vehicle bearing the license plate.



Revised 10/2010

2. In instances where the vehicle or license plate in a wanted person entry has been stolen, a notation that the vehicle or license plate is stolen should be placed in the MIS. Also, a separate entry of the stolen vehicle, felony vehicle, or license plate should be made in the Vehicle or License Plate Files by the agency possessing the theft report or handling the felony investigation.

3. The wanted person and stolen vehicle or license plate records should

be cross-referenced in the MIS or the linkage fields (LKI and LKA). 4. For example, the MIS of the wanted person record might read SUBJ

STOLE VEH BELOW-SEE WAC/V123456789, and the MIS of the vehicle record might contain SEE WAC/W000069216.

5. Should the wanted person entry contain data about a vehicle or license

plate which has already been entered in the Vehicle or License Plate Files, the agency making the entry will be furnished the vehicle or license plate record already on file at the time the wanted person entry is acknowledged. Receipt of this record should result in some form of communication between the two agencies as valuable lead information may be available.

6. When the vehicle in the record has been recovered, the vehicle data

must be removed from the wanted person record.

H. Additional Guidelines for Juvenile Offender Entries

1. On June 10, 1998, the Warrants and Transport Committee and

ACCESS adopted the following procedures for entering delinquent (Youth at Risk and Truancy) juvenile warrants:

a. All juvenile warrants should be entered using MKE/EWJ.

b. Warrants for "youth at risk" should be entered as follows:

c. Extradition in the EXL field should indicate 1 – Full Extradition.

d. The OFF field should be 5005 (Contempt of Court).

e. Youth at Risk should be indicated in the MIS field.

2. Warrants for "truancy" should be entered as follows:

a. Extradition is determined by the entering agency and should be indicated in the EXL and, if necessary, the MIS field.



Revised 10/2010

b. The OFF should be 7399 (Public Order Crimes).

c. Truancy should be indicated in the MIS field.

3. Adult warrants from juvenile courts should be entered as follows:

a. Warrants issued from the juvenile court for parents should be entered as an adult felony warrant.

b. The OFF Code should be 7399 (Public Order Crimes). c. Dependency should be indicated in the MIS field.



Revised 10/2010

CHAPTER 14: WACIC Wanted Persons File SECTION 05: Supplemental Data Entry



I. PROCEDURE

A. Supplemental Data Transactions

1. The supplemental data entry transaction is used to append additional identifiers to the wanted person entry.

2. To enter information into a supplemental record, that field must first be filled in the base record. That is, if an attempt is made to enter an SOC as a supplemental data entry, a reject will occur if no SOC exists in the base record.

3. Adding supplemental data to a record is restricted to the agency that

entered the record.

B. Syntax

Field Example

Header W; Message Key EN Originating Agency Identifier WA0340500 Record Identifier NAM/DOE, JOHN J Record Identifier OCA/TEST123

Supplemental Field(s) or Set(s) SMT/SC R SHLD. LIC/ACB234.WA.2006.PC

End of Text (send)



Revised 10/2010

1. The supplemental data entry transaction consists of the message key, ORI, two record identifiers, and the supplemental data fields being added. Permissible record identifiers are NAM and OCA, NAM and WAC, or NAM and NIC (except for misdemeanor warrant records). The supplemental data fields being added must be identified by their appropriate message field codes.

C. Wanted Person Supplemental Data Entry Field Edits

Field Edits

MKE The MKE for all wanted person supplemental data entries is EN.

Originating Agency Identifier Must be a valid ORI and match the ORI in the record being supplemented.

1st Record Identifier

The first of two identifiers to identify the record to be supplemented must be NAM.

2nd

Record Identifier The second of two identifiers to identify the record to be supplemented can be OCA, WAC or NIC.

Supplemental Field(s) or Set(s)

The supplemental data field(s) to be added. Each must be identified by its MFC.

D. Examples of Wanted Person Supplemental Data Entries

1. Wanted Person Supplemental Data Entry

W;EN.WA0340500.NAM/DOE JOHN J.OCA/TEST23. DOB/19501010.19490804.VIN/987654321AB987654.1986.TOYT..2D. RED.SOC/123456789(send)

E. Supplemental Data Entry Acknowledgments


WWCIC TIME: 0735 DATE: 050305 TO: ABCPD WA0340500 SUPP RECORD NAM/DOE, JOHN J OCA/TEST123 MODIFIED FIELDS: DOB.VIN.SOC



WA0340500

SUPP NAM/DOE, JOHN J OCA/TEST123



Revised 10/2010

F. Entry Guidelines for Supplemental Data

1. The Alias field and all other additional identifying data fields which may be included in a supplemental record are listed on the following page with their field codes and the maximum number of aliases and/or additional identifiers that may be added to a wanted person record.

FIELD FIELD CODE MAX NUMBER PERMITTED

Alias (includes nicknames) AKA 99

Date of Birth DOB 9

Scars, Marks, Tattoos, etc. SMT 9

Miscellaneous Identifying Number MNU 9

Social Security Number SOC 9

Operator's License Number, State, and Year of Expiration (entered as a set)

OLN 9

License Plate Number, State, Year of Expiration, and Type (entered as a set)

LIC 9

Vehicle Identification Number, Year, Make, Model, Style, and Color (entered as a set; Model and Color not required for entry, but should be entered if known)

VIN 9

Cautions and Medical Conditions CMC 9

Image ID and Type (entered as a set) IID 12

2. After the wanted person record has been identified, each field included

in a supplemental record entry, except those entered in sets of data, must be identified by the appropriate field code followed by a slash and the item(s) of data.

3. The data elements must be separated by a period and each field must

end with a period. Fields that are not a part of sets of data may be entered in any order in a supplemental record entry.

4. The OLN, LIC, VIN and IID fields in the supplemental record format are

multiple element data fields; that is, these fields have more than one data element following the field code and slash and are entered in sets.

5. Each set of data must be preceded by the appropriate field code

followed by a slash. The data elements within a set of data must be entered in sequence after the slash, and each data element must be filled.



Revised 10/2010

6. The DOB, SMT, MNU, SOC, OLN, LIC, and VIN fields in the main record must be filled before any supplemental entry for that same field will be accepted.

7. For example, any attempt to enter a Social Security number in a supplemental record will be rejected as a format error if the main record does not contain a Social Security number in the SOC field.

8. All numeric identifiers, excluding OCA and MNU Fields, are to be

entered omitting spaces, hyphens, and symbols. A hyphen may be used in the OCA, and a hyphen must be used to separate the two alphabetic characters from the number itself in the MNU.

9. When a supplemental record entry contains data on a person, a

vehicle, or a license plate already on file in a Missing Person, Wanted Person, Vehicle, or License Plate File record, the agency making the supplemental record entry will be furnished the record on file at the time the supplemental record entry message is acknowledged.

10. Further guidelines for the coding of personal identifiers are provided in

Personal Descriptors of the NCIC Code Manual.

G. Alias (AKA) Field in a Supplemental Data Entry

1. Field code AKA followed by a slash is used to identify an alias (es). An alias includes any names in which any last, first, or middle name is different from that in the NAM Field (or those previously entered in the AKA Field) for the record, i.e. NAM/Smith, Michael Lee and AKA/Smith, Lee Michael.

2. Aliases are to be listed with the last name, comma (space after comma is optional), first name or initial, space, middle name or initial, if any, space, and suffix indicating seniority, if any. Aliases and/or variations in name spelling must be separated by a period without repeating the MFC AKA.

3. Enter nicknames (monikers) in the AKA Field of the wanted person record. Further guidelines for the coding of aliases are provided in Personal Descriptors of the NCIC Code Manual.

4. It is not necessary to make alias entries for each combination of a

compound or hyphenated surname.



Revised 10/2010

5. Both the WACIC and NCIC systems index each component of compound or hyphenated surnames so an inquiry on any component or combination will produce a hit on the name as entered.

6. For example, a record entered with NAM/SMITH-JONES, JOHN JAY

will be retrieved by an inquiry with NAM/SMITH, JOHN JAY, NAM/JONES, JOHN JAY, or NAM/SMITHJONES, JOHN JAY. If a possibility exists that the surname and given name could be reversed, then an alias entry should be made.

H. Operator's License (OLN) Field in a Supplemental Data Entry

1. Field code OLN followed by a slash is used to identify additional

operator's license data in an entry. The three data elements making up this field are OLN, OLS, and OLY. All three elements must be included in the order listed in the format and must be separated by a period. For example: OLN/L234526677238. VA.2008

2. In the event more than one operator's license is to be entered at the same time, each set of operator's license data must be preceded by MFC OLN/.

I. License Plate Field in a Supplemental Data Entry

1. Field code LIC followed by a slash is used to identify additional license plate data in an entry. This set contains four data elements: LIC, LIS, LIY, and LIT. Elements must be entered in the order listed in the format and must be separated by a period. For example:

LIC/CBA321.MD.2006.TK.

2. In the event more than one set of license plates is to be included in one supplemental message, each set of license plate data must be preceded by MFC LIC/.



Revised 10/2010

J. Vehicle Data in a Supplemental Data Entry

1. Field code VIN followed by a slash is used to identify an additional vehicle in a supplemental entry. This field contains six data elements: VIN, VYR, VMA, VMO, VST, and VCO. The VIN, VYR, VMA, and VST are required for entry. However, the model and color should be entered in proper order when available. Elements must be separated by periods and each element must be filled. For example: VIN/987654321AB987654.1986.TOYT.CST.2D.SIL. or VIN/123456789AB987654. 1976.CHEV..2D

2. In the event data related to other vehicles are entered at the same time, each set of vehicular data must be preceded by MFC VIN/.

K. Additional Identifiers in a Supplemental Data Entry

1. The MFCs followed by a slash are used to identify additional data to be

included in a supplemental record, i.e. DOB/, SMT/, MNU/, and SOC/. Multiples can be entered without repeating the MFC and separated only by periods. For example, an entry might include:

DOB/19500101.19490804.SMT/SC L SHLD.POCKMARKS. MNU/PI-WA12252333.SOC/123456789

2. When identifying data are entered in a supplemental record, the corresponding fields in the corresponding base record must be filled.

L. Number of Additional Identifiers in a Supplemental Data Entry

1. A maximum of 99 AKA's and nine DOB's, SMT's, MNU's, SOC's, OLN's, LIC's, and VIN's may be added to a wanted person record. For example, a record relating to JOHN HARRY DOE might have an appended supplemental record of aliases and other additional identifiers consisting of three other names (AKA's), nine DOB's, five SMT's, two MNU (an Army Serial number and a Mariner's Document number), two sets of data describing operator's licenses known to have been issued in two states, three sets of data describing license plates known to have come into his possession, and one set of data concerning an automobile known to be in his possession.



Revised 10/2010

M. Maximum Number of Additional Identifiers

1. A maximum of nine additional identifiers of various kinds may be entered in one supplemental record entry message. Additional messages are required if more identifiers are to be entered. Each AKA (or variation of name spelling); DOB, SMTs, MNU, or SOC, etc.; is counted as one identifier.

2. Each set of data relating to an operator's license, a license plate, or a

vehicle is likewise counted as one identifier.

N. Modification of Supplemental Identifiers

1. No one-step procedure is available to modify an alias or other identifier in a supplemental record to a wanted person record. To modify (change) an alias or other identifier in a supplemental record, the incorrect alias or other identifier must be cancelled and re-entered.

2. A modify message (F, W, or J) to the base record to delete information in a field will cause the same data in the supplemental record to move up to the base record.



Revised 10/2010

CHAPTER 14: WACIC Wanted Persons File SECTION 06: Stolen/Fraudulent Identifier Data



I. PROCEDURE

A. Stolen or Fraudulent Identifier Data Entry

1. The stolen or fraudulent identifier data entry transaction is used to append additional identifiers to the wanted person entry.

2. Adding stolen or fraudulent identifier data to a record is restricted to the

agency that entered the record.

B. Syntax

Field Example

Header W;

Message Key ENS

Originating Agency Identifier WA0340500

Record Identifier NAM/DOE, JOHN J

Record Identifier OCA/TEST123

Supplemental Field(s) NAM/SMITH, JOHN D. DOB/1950101.19490804

End of Text (send)

1. The stolen or fraudulent identifier data entry transaction consists of the

message key, ORI, two record identifiers, and the supplemental data fields being added.



Revised 10/2010

2. Permissible record identifiers are NAM and OCA, NAM and WAC, or NAM and NIC (except for misdemeanor warrant records). The stolen or fraudulent identifier data fields being added must be identified by their appropriate message field codes.

3. To remove a stolen or fraudulent identifier, use the stolen or fraudulent

identifier data cancellation transaction explained in Section 12.

C. Wanted Person Stolen/Fraudulent Identifier Entry Field Edits

Field Edits

MKE The MKE for all wanted person supplemental data entries is ENS.


Must be a valid ORI and match the ORI in the record being modified.


The first of two identifiers to identify the record to be supplemented. Must be NAM.

2nd

Record Identifier The second of two identifiers to identify the record to be supplemented. Can be OCA, WAC or NIC.

Stolen or Fraudulent Identifier

The stolen or fraudulent identifier data field(s) to be added. Each must be identified by its MFC

D. Example of Stolen or Fraudulent Identifier Data Entries

W;ENS.WA0340500.NAM/DOE, JOHN J.OCA/TEST123. AKA/SMITH, JOHN J.DOB/19500101.19490804.SOC/123456789(send)

E. Stolen or Fraudulent Identifier Data Entry Acknowledgments



WA0340500

S/F SUPP RECORD NAM/DOE, JOHN J OCA/TEST123

MODIFIED FIELDS: AKA, DOB, SOC

12/06/2005 AT 12/13



WA0340500

S/F SUPP NAM/SMITH, JOHN J OCA/TEST12



Revised 10/2010

F. Entry Guidelines for Stolen or Fraudulent Identifiers

1. The general rule for the use of stolen/fraudulent identifier fields is that

they must be used whenever a wanted person is known to be using identification documents that are stolen/fraudulent. If the wanted person is using a made-up name or numerical identifier for which it is not known whether identification documents (Social Security card, operator's license, etc.) exist, these identifiers should be entered in the appropriate base record or supplemental identifier fields, such as the DOB.

2. The base record NAM must be entered for each record. This field

should contain the wanted person's true name, regardless of whether it is the name contained on the arrest warrant. Listed below are guidelines for coding the "true" and S/F NAM Fields and the "true" and S/F DOB Fields.

a. If the name on the arrest warrant is believed to be the wanted

person's real name, the name should be entered in only the base record NAM. If the wanted person's date of birth is available, it should be entered in the base record DOB. Any known S/F identifiers should be entered in the S/F identifier fields.

b. If the name on the arrest warrant is known to be S/F and the

wanted person's true name is known then the S/F name should be entered in the S/F NAM Field. The wanted person's real name must be entered in the base record NAM. The date of birth from the S/F identification, if known, must be entered in the S/F DOB. If the wanted person's real date of birth is known it should be entered in the base record DOB.

c. If an arrest warrant is issued in the name of "John Doe" or “Jane

Doe” when the wanted person's true identity is unknown and the wanted person is known to be using S/F identification documents, entry of a Wanted Person file record is permitted provided that the identifiers from the S/F documents are included in the Wanted Person Record and identified as such. FBI numbers should not be entered in these types of records.



Revised 10/2010

3. This enhancement only serves to highlight information when the record subject is known to use S/F identification documents. It does not alter current policy concerning entry of "John or Jane Doe" records without a warrant which is currently allowed only when the record subject is using a homicide victim's identification.

4. The identifiers which may be included in a supplemental S/F identifier

record entry or cancel message are listed below with their message field codes and the maximum number that may be appended to a base record:

Stolen/Fraudulent ID Field Field Code Max Number Permitted

S/F Name NAM 99

S/F Date of Birth DOB 9

S/F Miscellaneous Identifying Number MNU 9

S/F Social Security Number SOC 9

S/F Operator's License Number, Operator's License State, and Operator's License Year of Expiration

OLN 9

5. The S/F identifiers being entered or cancelled follow the two base

record identifiers. Each type of identifier included in a supplemental S/F record entry or cancel, except an OLS and OLY, must be identified by the proper MFC followed by a slash and the identifier(s). Multiple identifiers may be entered following the MFC. The identifiers must be separated by a period and each field must end with a period. All fields except the operator's license fields may be entered in any order in a supplemental record entry. For example, an entry or cancel containing two SOC's and two DOB's may appear as follows:

a. SOC/123456890.987644321.DOB/19500101.19480804 The OLN

in the supplemental S/F record format is a multiple element data field; there is more than one data element following the field code and slash. Each OLN must be preceded by the MFC OLN and a slash (/). The OLS and OLY must immediately follow the OLN and are entered without an MFC. For example, the entry or cancellation of two OLNs would appear as follows:

OLN/18273645.US.1993.OLN/VA192837465.VA.1992



Revised 10/2010

6. A maximum of nine additional identifiers of various kinds may be entered or cancelled in one supplemental record message. Additional messages are required if more identifiers are to be entered. Each S/F NAM, DOB, SOC, and MNU is counted as one identifier. Each set of data relating to an OLN (i.e., OLN, OLS, and OLY) is counted as one identifier.



Revised 10/2010

CHAPTER 14: WACIC Wanted Persons File SECTION 07: Modify Transactions



I. DEFINITIONS

A. Modify Transactions

1. The modify transaction is used to add, delete, or change information in one or more fields of an existing wanted person record. A modify message to delete information in a field of the base record will cause the same data in the supplemental record to move up to the base record, except for vehicle and license data.

II. PROCEDURE

A. Agency Modification

1. Modification of a record is restricted to the agency that entered the

record. A modification is used to add, delete, or change data in an active base wanted person record.

B. Syntax

Field Example

Header W;

Message Key MWF




Modified Field(s) WGT/200.SMT/SC R SHLD

End of Text (send)



Revised 10/2010

1. The modify transaction consists of the message key, ORI, two record identifiers, and the fields being modified. Permissible record identifiers are NAM and OCA, NAM and WAC, or NAM and NIC (except for misdemeanor warrant records). The fields being modified must be identified by their appropriate MFCs.

2. To delete information from a field, use the MFC followed by a period, (e.g., SMT/.). You cannot delete data from a required field.

C. Wanted Person Modify Field Edits

Field Edits

MKE

Must be a valid message key: MWF – Wanted Felony MTF – Wanted Temporary Felony MWW – Wanted Misdemeanor MWJ – Wanted Juvenile


Must be a valid ORI and match the ORI in the record being modified.


The first of two identifiers to identify the record to be modified. Must be NAM.

2nd

Record Identifier The second of two identifiers to identify the record to be modified. Can be OCA, WAC or NIC.

Modified Field(s) The field(s) in the record to be modified. Each must be identified by its MFC.

D. Examples of Wanted Person Record Modifications

1. Wanted Felony Modify

W;MWF.WA0340500.NAM/DOE, JOHN J.OCA/TEST123. WGT/200(send)

2. Wanted Temporary Felony Modify

W;MTF.WA0340500.NAM/DOE, JOHN J.OCA/TEST123. WGT/200(send)

3. Wanted Misdemeanor Modify

W;MWW.WA0340500.NAM/DOE, JOHN J.OCA/TEST123. HAI/BRO.SOC/123456789(send)



Revised 10/2010

4. Wanted Juvenile Modify

W;MWJ.WA0340500.NAM/DOE, JOHN J.OCA/TEST123. HAI/BRO.SOC/123456789(send)

5. Modify to Remove All Vehicle Data

W;MWF.WA00340500.NAM/DOE, JOHN J.OCA/TEST123. LIC-VCO/(send)

E. Modify Acknowledgments

1. WACIC Modify Acknowledgment


WA0340500

MODIFIED EWF NAM/DOE, JOHN J


MODIFIED FIELDS: WGT

12/06/2000 AT 12/49

2. NCIC Modify Acknowledgment


WA0340500

MODIFY NAM/DOE, JOHN J OCA/TEST123

F. Additional Guidelines for Record Modifications

1. In instances where an ORI will not honor the extradition of an

individual, the ORI must initiate a modify message to include in the MIS of the record information concerning extradition limitations. For example: EXTR WA OR ID MT ONLY.

2. If an entering agency subsequently learns that a person is using one of

the S/F identifiers with one of his "true" identifiers, the record must be modified to add the S/F identifier to the appropriate "true" identifier field.

3. The OLN/. deletes the entire base set and “OLN/OLN.OLS.OLY”,

modifies the entire base set.



Revised 10/2010

G. Modification to Remove All Vehicle Data

1. When a vehicle which was included in a wanted person record is

recovered prior to apprehension/location of the wanted person, a special modification message may be used to remove all vehicular data without identifying each individual field (see example above).

2. The record to be modified must be identified by either the NAM and

WAC in that order or NAM and OCA in that order proceeded by the proper MFC's. The characters LIC-VCO/, follow the two record identifiers. Entry of LIC-VCO/, causes the WACIC system to delete the fields: LIC, LIS, LIY, LIT, VIN, VYR, VMA, VMO, VST, and VCO.

H. Modification to Remove Part of Vehicle Data

1. The special modification message explained above cannot be used to

remove less than all of the vehicular data from a wanted person record. If only the four fields of license plate data (LIC, LIS, LIY, LIT) are to be deleted from the record, the usual modification procedure must be followed, with each field to be deleted explicitly set forth in the modify message. For example:

MWF.WA0340500.NAM/DOE, JOHN J.OCA/98-0141. LIC/.LIS/.LIY/.LIT/.



Revised 10/2010

CHAPTER 14: WACIC Wanted Persons File SECTION 08: Locate Messages



I. DEFINITIONS

A. Locate Messages

1. A locate message is used by an agency other than the entering agency to indicate the wanted person has been apprehended or located. The locate message flags the wanted person record and causes a notice to be sent to the entering agency.

B. Agency Locates

1. Any agency that apprehends a person who is indexed in the WACIC

and/or NCIC Wanted Person Files, except the agency that entered the record, must place a locate message on the wanted person record(s).

2. When the locating agency intends to hold the subject on local charges

and the individual is found within the geographical area of extradition, the locate transaction should include DETN in the EXT Field.

3. When an agency receives a record or multiple records in response to

an inquiry, the inquiring agency must contact the ORI of each record matching the person in question to confirm the hit(s).

4. Following confirmation with the originating agency(s), a locate

message must be transmitted for each record on file for the subject. When an individual is found outside the geographical area of extradition a record should not be located. Locates are placed only when the individual is found within the extradition area.



Revised 10/2010

5. When an agency receives a record(s) in response to an inquiry and no enforcement action is contemplated or possible, because of circumstances, the hit need not be confirmed and the record must not be located. If, for example, local jails are unable to house minor misdemeanor prisoners because of overcrowding, and the subject will be released rather than being booked or posting bail, hit confirmation is not necessary or desirable.

6. The entering ORI has the responsibility of immediately advising an

apprehending/locating agency concerning extradition of the individual when contacted about the apprehension/location.

C. Syntax

Field Example

Header W;

Message Key LWF




Date of Locate 20050228

Locating Agency's Case Number 05-54321

Extradition Indicator EXTR

Reason for Person Record Removal HIT NCIC 20050804

Person Armed 2

Wanted/Missing Person Hit Results 5

Number of Persons Apprehended 2

Number of Missing Persons Found 2

Value of Recovered Property 20000

Value of Other Recovered Property 4000

Value of Recovered Contraband 9000

End of Text (send)

1. The locate transaction consists of the message key, ORI, two record

identifiers, the date of locate, the locating agency's case number, the extradition indicator, and benefits data fields. Permissible record identifiers are NAM and OCA, NAM and WAC, or NAM and NIC (except for misdemeanor warrant records). The name used in identifying the record to receive the locate must be set forth with the exact spelling and spacing as shown in the record on file.

2. Benefits data is not allowed when locating a misdemeanor warrant

record.



Revised 10/2010

II. PROCEDURE

A. Wanted Person Locate Field Edits

Field Edits

MKE

Must be a valid message key:

LWF – Wanted Felony LTF – Wanted Temporary Felony

LWW – Wanted Misdemeanor LWJ – Wanted Juvenile

Originating Agency Identifier Must be a valid ORI and cannot be the same as the ORI in the record being located.


The first of two identifiers to identify the record to be located. Must be NAM.

2nd

Record Identifier The second of two identifiers to identify the record to be located. Can be OCA or WAC.

Date of Locate Must be a valid date in the format YYYYMMDD. Cannot be later than the current date nor earlier than the date of warrant in the record being located.

Locating Agency's Case Number The case number assigned by the locating agency to the recovery. Maximum of 9 characters.

Extradition

Must be either: EXTR – the subject will be extradited; or

NOEX – the subject will not be extradited; or DETN -- the subject will be detained on local charges

Reason for Person Record Removal

Can be 10-21 alpha-numeric characters, possible values are:

HIT LOCAL YYYYMMDD

HIT STATE YYYYMMDD

HIT NCIC YYYYMMDD

OTHER MEANS

PREVIOUSLY LOCATED

Persons Armed

Can contains the Code 1, 2, or 3: 1 = Yes 2 = No 3 = Not Available. Can be entered only if RPS is entered.

Wanted/Missing Person Hit Result

1 or 2 numeric characters. Can be one or two of the following: 1 = Subject arrested on charge in wanted person record 2 = Subject arrested on charge other than charge in hit record 3 = Detainer filed 4 = Held for extradition 5 = Held for another jurisdiction after confirmation of missing status*** 6 = Released - Wanting agency refused to extradite 7 = Released - Agency holding missing person report can provide no follow up in case of adult or where parents refuse



Revised 10/2010

to take custody of missing juvenile*** 8 = Released - Unable to confirm missing status*** 9 = Released - Unable to confirm wanted status Can be entered only if RPS is entered.

Number of Persons Apprehended

1 to 3 numeric characters. Can be entered only if RPP is entered. Must be blank or 0 if RPS is OTHER MEANS or PREVIOUSLY LOCATED.

Number of Missing Persons Found

1 to 20 alphanumeric characters. One or more of the following codes may be entered: nnn represents the number of occurrences: nnnJI: Juvenile indexed in NCIC nnnJN: Juvenile not indexed in NCIC nnnOI: Other missing person indexed in NCIC nnnON: Other missing personnot indexed in NCIC Can be entered only if RPS is entered. Must be blank or 0 if RPS is OTHER MEANS or PREVIOUSLY LOCATED.

Value of Recovered Property

1 to 8 numeric characters. Fair market value (in whole dollars) of the article when it was recovered. Can be entered only if RPS is entered. Must be blank or 0 if RPS is OTHER MEANS or PREVIOUSLY LOCATED

Value of Other Recovered Property

1 to 8 numeric characters. Fair market value (in whole dollars) of the property recovered in addition to the item which is the subject of the record. Can be entered only if RPS is entered. Must be blank or 0 if RPS is OTHER MEANS or PREVIOUSLY LOCATED.

Value of Recovered Contraband

Fair market value (in whole dollars) of any contraband recovered as a result of recovering the item which is the subject of the record. Can be entered only if RPS is entered. Must be blank or 0 if RPS is OTHER MEANS or PREVIOUSLY LOCATED.

B. Examples of Wanted Person Record Locate Messages

1. Wanted Felony Locate (with optional benefits data)

W;LWF.WA0340500.NAM/DOE, JOHN J.OCA/TEST123.20050430.05-54321.EXTR.HIT NCIC 20050804.2.5.2.2.20000.4000.9000(send)

2. Wanted Temporary Felony Locate

W;LTF.WA0340500.NAM/DOE, JOHN J.OCA/TEST123.20000430.05-54321.EXTR(send)



Revised 10/2010

NOTE: It is important that the locating agency enter a locate message upon completion of the hit confirmation process rather than wait for the entering agency to clear their record. Failure to do this prior to a clear message being sent could result in the person being checked at a later date and being shown as an active wanted person when actually in located status.

C. Locate Acknowledgments

1. WACIC Locate Acknowledgment

The following WACIC locate acknowledgment will be sent to the terminal entering the locate:


WA0340500

LOCATED EWF NAM/DOE, JOHN J


The following WACIC locate message will be sent to the agency that entered the record which was located: WWCIC TIME: 1344 DATE: 052505 TO: ABCPD

PD ANYTOWN HAS ENTERED A LOCATE ON YOUR

EWF WARRANT FOR NAM/DOE, JOHN J OCA/TEST123

PLEASE CLEAR THIS RECORD



Revised 10/2010

2. NCIC Locate Acknowledgments

The following NCIC acknowledgment will be sent to the terminal entering the locate:


WA0340500

LOCATED NAM/DOE, JOHN J OCA/TEST123

The following NCIC message will be sent to the agency that entered the record:

NCIC XMIT MSG#: 10527 TIME: 1342 DATE: 052505

RCV MSG#: 86 TIME: 1345 TO: ABCPD

$.L.

WA0340500

LOCATE NOTIFICATION AT 1640 EDT 20000525

1L01ABCPD

.LW.WA0340500.NAM/DOE, JOHN J.0CA/TEST123.20050525.

05-1234

LOCATING ORI IS PD ANYTOWN

MKE/LOCATED WANTED PERSON

ORI/WA340500 NAMDOE, JOHN J SEX/M RAC/W POB/WA

DOB/19500101

HGT/511 WGT/200 EYE/BR0 HAI/BR0

OFF/UNAUTH COMMUNICATION WITH PRISONER

DOW/20050525 OCA/TEST123

MIS/TEST ENTRY 0NLY TEST ENTRY

LOCATED/20050525 WA0340700 05-1234 EXT

NIC/W123456789 DTE/20050525 1636 EDT

D. Locate Guidelines

1. A wanted person record can be placed in locate status regardless of whether EXTR, NOEX or DETN is entered in the extradition (EXT) field.

2. Agencies sending locate messages should make every effort to ensure the proper information is included in the EXT field (example: if the subject is being detained).



Revised 10/2010

E. Use of EXTR in a Locate Message

1. EXTR, an abbreviation for extradition, must be included in the locate

message when:

a. The agency that entered the record advises that the apprehended/located person will be extradited or picked up interstate.

b. The person is wanted by a federal agency and has been apprehended/located by federal or local authorities.

F. Use of NOEX in a Locate Message

1. NOEX, an abbreviation for no extradition, must be included in the

locate message when:

a. The agency that entered the record advises that the apprehended/located person will not be extradited based on circumstances at the time of apprehension/location.

b. The apprehending/locating agency has received no information

concerning an extradition decision after making a concerted effort to obtain such information.

G. Use of DETN in a Locate Message

1. DETN, an abbreviation for “detained”, must be included in the locate message when:

a. The locating agency intends to hold the subject on local charges.

b. The wanted person has been found in a government holding

facility, such as a prison.

2. In a few instances, a wanted person may be apprehended/located more than once without extradition taking place because of the expense, the distance involved, or other reasons. One locate message can be made a permanent part of a WACIC wanted person record. A second locate message will change the record to cleared and then purge after 14 days.



Revised 10/2010

3. Located includes situations when the wanted person has been found,

such as in prison, a mental institution, or deceased, and the agency finding the person contacts the ORI and the ORI advises that the person will or will not be extradited.



Revised 10/2010

CHAPTER 14: WACIC Wanted Persons File SECTION 09: Detainer



I. DEFINITIONS

A. Detainer File

1. A DETAINER is an official notice from a government agency to a correctional agency requesting that an individual wanted by the first agency, but subject to the correctional agency's jurisdiction, not be released or discharged without first notifying the wanting agency and giving it an opportunity to respond. Typical reasons for DETAINERs include the individual is wanted for trial or wanted to serve a sentence in the requesting jurisdiction.

2. DETAINER information may only be appended to wanted person records in located status by the agency of record. At this point, the agency of record has the option of appending DETAINER information to its WACIC and NCIC wanted person records within five days of the locate transaction. This 5 day limitation applies only to those wanted person records in located status in and the locate message indicated EXTR or DETN. Wanted person records in located status which indicate NOEX will remain on file indefinitely unless a second locate is placed upon the record. These records are retired immediately from NCIC upon receipt of a second locate message. Located records in WACIC will remain on file indefinitely unless a second locate is placed upon the record or the record is cleared or canceled. Appending the DETAINER information will allow the record to remain on file until extradition can occur.



Revised 10/2010

3. When an inquiring agency receives a positive response, confirms both that the warrant is outstanding and extradition is valid, it must perform a locate transaction to place the record in located status. If the locating agency intends to hold the individual on local charges, the locate transaction should indicate the detention by placing DETN in the Extradition (EXT) Field. If multiple records are identified and the warrants are confirmed, locate transactions must be sent for each confirmed record if within the extradition limitations.

4. Upon receipt of the locate notification by the ORI of record and the

decision is made to append DETAINER information to the record, direct contact must be made with the incarcerating agency. Pertinent information such as “incarcerating agency ORI, date incarceration starts, date of sentence expiration” must be obtained for the DETAINER transaction.

5. A wanted person record will be placed in locate status regardless of

whether EXTR, NOEX or DETN is entered in the extradition (EXT) field of the locate message. DETAINER information can be appended to a wanted person record as long as it is in located status. Note that NCIC wanted person records in located status (DETN or EXTR) only remain on line for 5 days. Located records in WACIC will remain on file indefinitely unless a second locate is placed upon the record or the record is cleared or canceled.

B. Syntax

Field Example

Header W;

Message Key EDW


Record Identifier NAM/TESTING,DETAINER TEST

Record Identifier OCA/DETAINER4

Date of DETAINER DOD/20050801

DETAINER Case Number DNO/05-004

Incarcerating Agency Identifier IRI/WA008013C

Date Incarceration Starts DIS/20050802

Date of Sentence Expiration DSE/20050903

Place of Incarceration Cowlitz County Jail

End of Text (send)



Revised 10/2010

1. The DETAINER transaction consists of the message key, ORI, two

record identifiers, the date of DETAINER, the DETAINER case number, and the incarcerating agency identifier. Each field in the EDW transaction must be identified by message field code (MFC) with the exception of MKE and ORI. Optional fields, if used, must include MFC. See example below:

II. PROCEDURE

A. Wanted Person DETAINER Field Edits

Field Required? Message Field

Code Field length Data Type

Message Key Yes MKE 3 Alphabetic


Yes ORI 9 Alphabetic, numeric

WACIC Number Conditional* WAC 10 Alphabetic, numeric

Name Conditional* NAM 30 Alphabetic, numeric

Originating Agency Case Number

Conditional* OCA 9 Alphabetic, numeric

Date of DETAINER

Yes DOD 8 Numeric

DETAINER Case Number

Yes DNO 20 Alphabetic, numeric

Incarcerating Agency Identifier

Yes IRI 9 Alphabetic, numeric

Date of Incarceration

Optional DIS 8 Numeric

Date of Sentence Expiration

Optional DSE 8 Numeric

Place of Incarceration

Optional INC 50 Alphabetic, numeric

*Base record identifier



Revised 10/2010

B. MESSAGE FIELD CODES AND EDITS

DIS Date of

Incarceration Must be a valid Gregorian date (YYYYMMDD) equal to or less than current date

DOD Date of Detainer Must be a valid Gregorian date (YYYYMMDD) equal to or less than current date

DNO Detainer Case Number

Must not contain a single zero only, a run of zeros only, the work NONE, or a single alphabetic only. The first seven characters of the DNO cannot equal the first seven characters of the ORI. The only valid special character is the hyphen.

DSE Date of Sentence Expiration

Must be a valid Gregorian date (YYYYMMDD) greater than current date plus 5 days.

INC Place of Incarceration

Free text (alphanumeric and special characters).

IRI Incarcerating Agency Identifier

Must be a valid NCIC-assigned ORI.

C. Example of a DETAINER Entry

1. DETAINER Entry W;EDW.WA0340000.NAM/TESTING,DETAINER TEST.OCA/05-12345.DOD/20050801.DNO/05-004.IRI/WA008013C.DIS/20050801. DSE/20050812.INC/COWLITZ COUNTY JAIL

a. The above enter DETAINER information example contains:

message key (EDW), originating agency identifier (WA0340000), two record identifiers (NAM/ TESTING,DETAINER TEST and OCA/05-12345), date of DETAINER (20050801), DETAINER case number (05-004), incarcerating agency identifier (WA008013C), date incarceration starts (20050801), date of sentence expiration (20050812) and place of incarceration (COWLITZ COUNTY JAIL).

D. Mandatory Fields for a DETAINER Entry

1. The following fields are mandatory to cause acceptance of a DETAINER entry into WACIC: HDR, MKE, ORI, (NAM and OCA) or (WAC and OCA) or (NAM and WAC), DOD, DNO, and IRI.



Revised 10/2010

E. DETAINER Acknowledgment

1. WACIC DETAINER Acknowledgement .

a. The following WACIC DETAINER acknowledgement will be sent to the terminal entering the DETAINER: WACIC ACESS)WA0340000

ENTERED DETAINER NAM/TESTING,DETAINER TEST

WAC/05W0140414 OCA/DETAINER4

07/21/2005 AT 08/31

2. NCIC DETAINER Acknowledgement

a. If DETAINER information is appended to a located wanted person record in NCIC, the following NCIC DETAINER acknowledgement will be sent to the terminal entering the DETAINER: 1L01HEADER

WA0340000

ENTER DETAINER NAM/TESTING,DETAINER TEST

NIC/W123456789

F. Additional Guidelines for DETAINER Entry

1. A Wanted Person record must be in located status before a DETAINER can be appended to the record.

2. The ORI of the Wanted Person Record is the only agency that can

append a DETAINER. 3. A wanted person record can only be appended with one DETAINER. 4. The place of incarceration is the facility that has the individual

detained, whether it be a local, state, federal, or private facility. 5. The incarcerating agency identifier is the NCIC assigned ORI of the

agency who will receive the Incarcerating Agency Notification ($.O.) advising that a DETAINER has been filed. (Prior to trial, this would likely be the arresting agency or holding facility. Post trial, it would probably be a correctional facility).



Revised 10/2010

G. Notifications of Detainer

1. Upon entry of DETAINER information, an unsolicited message, $.O, is sent to the incarcerating agency

a. NCIC Incarcerating Agency Notification ($.O.)

$.O

WA008013C

INCARCERATING AGENCY NOTIFICATION

ORI/WA0340000 HAS REPORTED THE FILING OF A DETAINER ON

NAM/SMITH, JOHN J NIC/W123456789

PLEASE CONTACT ORI/WA0340000 BEFORE SUSPECT IS

RELEASED.

MKE/DETAINED WANTED PERSON-CAUTION SUICIDAL






DOW/20051227 OCA/05-4889

LOCATED/20050324 WA0080200 A345234 DETN

DOD/20050315 DNO/05-1234567890 IRI/ WA008013C DIS/20050315

DSE/20060415

INC/COWLITZ COUNTY JAIL

NIC/W123456789 DTE 2005 0328 0830 EDT




Revised 10/2010

b. WACIC Incarcerating Agency Notification ($.O.) WACIC KELCJ.$.O.

WA008013C

INCARCERATING AGENCY NOTIFICATION

ORI/WA0340000 HAS REPORTED THE FILING OF A DETAINER ON

NAM/TESTING,DETAINER TEST WAC/05W0097691

PLEASE CONTACT WA0340000 BEFORE SUSPECT IS RELEASED.

AGENCY NAME/SO OLYMPIA AGENCY TELEPHONE/360-786-

5500

MKE/DETAINED WANTED PERSON

ORI/WA0340000 NAM/TESTING,DETAINER TEST SEX/M RAC/W

DOB/19651001

HGT/600 WGT/180 EYE/BRO HAI/BLK

OFF/KEEPING HOUSE ILL FAME

DOW/20050715 OCA/DETAINER4

LOCATED/20050801 WA0080000 05-04 NOEX

DOD/08012005 DNO/-00404-0 IRI/WA008013C DIS/20040801

DSE/20040812 INC/COWLITZ COUNTY JAIL

WAC/05W0097691


c. NCIC Sentence Expiration Notification ($.P.)

(1) Five days prior to the date of sentence expiration (date shown in the DSE/), the ORI of record will receive a $.P. message. This unsolicited message is a reminder to the ORI of record of the subject's pending release and the need to contact the incarcerating agency to arrange extradition. The following is an example of the message:



Revised 10/2010

$.P.

WA0340000

SENTENCE EXPIRATION NOTIFICATION

THE FOLLOWING RECORD WILL BE RETIRED IN FIVE DAYS

BASED ON THE SENTENCE EXPIRATION DATE CONTAINED IN

THE DETAINED WANTED PERSON RECORD UNLESS ACTION IS

TAKEN TO INCREASE THE SENTENCE EXPIRATION DATE

MKE/DETAINED WANTED PERSON-CAUTION SUICIDAL






DOW/20051227 OCA/05-4889

LOCATED/20051024 DSE/20050415 A345234 DETN

DOD/20050315 DNO/05-1234567890 IRI/WA008013C DIS/20050315

DSE/20050415


NIC/W123456789 DTE 2005 0328 0830 EDT


d. WACIC Sentence Expiration Notification ($.P.) WACIC OLYSO.$.P.

WA0340000

SENTENCE EXPIRATION NOTIFICATION

THIS RECORD WILL BE RETIRED IN FIVE DAYS BASED ON THE

SENTENCE EXPIRATION DATE CONTAINED IN THE DETAINED

WANTED PERSON RECORD UNLESS ACTION IS TAKEN TO INCREASE

THE SENTENCE EXPIRATION DATE

MKE/DETAINED WANTED PERSON

ORI/WA0340000 NAM/TESTING,DETAINER TEST SEX/M RAC/W

DOB/19651001

HGT/600 WGT/180 EYE/BRO HAI/BLK

OFF/KEEPING HOUSE ILL FAME

DOW/20050715 OCA/DETAINER4

LOCATED/20050801 WA0080000 05-04 NOEX

DOD/20050801 DNO/-00404-0 IRI/WA008013C ISD/20040801 DSE/20050812


WAC/05W0097691




Revised 10/2010

H. Modification of DETAINER Information

1. No one-step procedure is available to modify a DETAINER appended to a Wanted Person record.

2. To modify a DETAINER entry, the incorrect entry must be canceled and re-entered.

I. When to Cancel DETAINER Information

1. This transaction is used to cancel a DETAINER on a Wanted Person record by using MKE XDW. A DETAINER record can be canceled only by agency that made the original entry. This transaction is utilized when the entering agency determines the DETAINER information is incorrect or invalid.

J. Syntax

Field Example

Header W;

Message Key XDW


Record Identifier NAM/ TESTING,DETAINER TEST

Record Identifier OCA/ DETAINER4

End of Text (send)

1. The cancel DETAINER transaction consists of the message key, ORI, and two record identifiers. Permissible record identifiers are NAM and OCA or NAM and WAC.

K. Wanted Person Cancel DETAINER Field Edits

Field Edits

MKE Must be a valid message key: XWD – Cancel DETAINER


Must be a valid ORI and match the ORI in the DETAINER record being cancelled.


The first of two identifiers to identify the DETAINER record to be cancelled. Must be NAM.

2nd

Record Identifier The second of two identifiers to identify the DETAINER record to be cancelled. Can be OCA or WAC.



Revised 10/2010

L. Mandatory Fields for a Cancel DETAINER

1. Transaction

a. The following fields are mandatory to cause acceptance of a DETAINER cancel into WACIC: HDR, MKE, ORI, (NAM and OCA) or (NAM and WAC).

M. Example of a Cancel DETAINER Transaction (XDW)

W;XDW.WA0340000.NAM/TESTING,DETAINER TEST.OCA/ 05-12345

1. The above cancel DETAINER information example contains: message key (XDW), originating agency identifier (WA0340000), two record identifiers (NAM/ TESTING,DETAINER TEST and OCA/05-12345).

N. DETAINER Cancel Acknowledgments

1. WACIC Cancel DETAINER Acknowledgement

WACIC ACESS)WA0340000

CANCELED DETAINER NAM/TESTING,DETAINER TEST

WAC/05W0097691 OCA/DETAINER4

2. NCIC Cancel DETAINER Acknowledgement

1L01HEADER

WA0130000

CANCEL DETAINER NAM/DOE, JOHN J NIC/W123456789



Revised 10/2010

CHAPTER 14: WACIC Wanted Persons File SECTION 10: Clear Transactions



I. DEFINITIONS

A. Clear Messages

1. When a clear message is sent the first character of the message key is changed to "C" and the record is retained in the WACIC system for 14 days from the date of clear. If the record must be re-entered before the end of this 14-day period, it must first be canceled before it can be re-entered or the entry will be rejected as a duplicate record on file. Cleared records are removed entirely from the NCIC system upon receipt of the clear message.

B. When to Use a Clear Message

1. Clearance of a record is restricted to the agency that entered the

record. A clear message is transmitted:

a. When the agency apprehending the wanted person is the agency that entered the record.

b. When the agency that entered the record is officially advised that the wanted person is in custody of another agency.

c. A record to be cleared is identified in the same manner as a "modify" message.



Revised 10/2010

2. If an agency has entered a temporary felony want record, it will automatically be purged from the file after 48 hours.

3. If the subject is apprehended in less than 48 hours, the warrant must

be cleared from the system by the entering ORI.

C. Syntax

Field Example

Header W;

Message Key CWF




Date of Clear 20000228

Locating Agency's ORI WA0340700

Locating Agency's Case Number 05-4321

Reason for Person Record Removal HIT NCIC 20050804

Person Armed 2

Wanted/Missing Person Hit Results 5

Number of Persons Apprehended 2

Number of Missing Persons Found 2

Value of Recovered Property 20000

Value of Other Recovered Property 4000

Value of Recovered Contraband 9000

End of Text (send)

1. The clear transaction consists of the message key, ORI, two record

identifiers, the date of clear, and the locating agency's ORI and case number. Permissible record identifiers are NAM and OCA, NAM and WAC, or NAM and NIC (except for misdemeanor warrant records). Locating agency ORI and case number are optional fields and are not used when the entering agency apprehends the wanted person.

D. Wanted Person Clear Field Edits

Field Edits

MKE

Must be a valid message key: CWF – Wanted Felony CTF – Wanted Temporary Felony CWW – Wanted Misdemeanor CWJ – Wanted Juvenile

Originating Agency Identifier Must be a valid ORI and match the ORI in the record being cleared.

1st Record Identifier The first of two identifiers to identify the record to be cleared.



Revised 10/2010

Field Edits

Must be NAM.

2nd

Record Identifier The second of two identifiers to identify the record to be cleared. Can be OCA, WAC or NIC.

Date of Clear Must be a valid date in the format YYYYMMDD. Cannot be later than the current date nor earlier than the date of warrant in the record being cleared.

Recovering Agency ORI OPTIONAL. If used, the ORI of the agency apprehending the wanted person. Must be a valid ORI and cannot be the same as the ORI in the record.

Recovering Agency Case Number

OPTIONAL. If used, the case number assigned by the agency apprehending the person.



HIT LOCAL YYYYMMDD

HIT STATE YYYYMMDD

HIT NCIC YYYYMMDD

OTHER MEANS

PREVIOUSLY LOCATED

Persons Armed

Can contains the Code 1, 2, or 3: 1 = Yes 2 = No 3 = Not Available. Can be entered only if RPS is entered.

Wanted/Missing Person Hit Result

1 or 2 numeric characters. Can be one or two of the following: 1 = Subject arrested on charge in wanted person record 2 = Subject arrested on charge other than charge in hit record 3 = Detainer filed 4 = Held for extradition 5 = Held for another jurisdiction after confirmation of missing status*** 6 = Released - Wanting agency refused to extradite 7 = Released - Agency holding missing person report can provide no follow up in case of adult or where parents refuse to take custody of missing juvenile*** 8 = Released - Unable to confirm missing status*** 9 = Released - Unable to confirm wanted status Can be entered only if RPS is entered.

Number of Persons Apprehended

1 to 3 numeric characters. Can be entered only if RPP is entered. Must be blank or 0 if RPS is OTHER MEANS or PREVIOUSLY LOCATED.

Number of Missing Persons Found

1 to 20 alphanumeric characters. One or more of the following codes may be entered: nnn represents the number of occurrences: nnnJI: Juvenile indexed in NCIC nnnJN: Juvenile not indexed in NCIC nnnOI: Other missing person indexed in NCIC nnnON: Other missing person not indexed in NCIC Can be entered only if RPS is entered. Must be blank or 0 if RPS is OTHER MEANS or



Revised 10/2010

Field Edits

PREVIOUSLY LOCATED.

Value of Recovered Property

1 to 8 numeric characters. Fair market value (in whole dollars) of the article when it was recovered. Can be entered only if RPS is entered. Must be blank or 0 if RPS is OTHER MEANS or PREVIOUSLY LOCATED

Value of Other Recovered Property

1 to 8 numeric characters. Fair market value (in whole dollars) of the property recovered in addition to the item which is the subject of the record. Can be entered only if RPS is entered. Must be blank or 0 if RPS is OTHER MEANS or PREVIOUSLY LOCATED.

Value of Recovered Contraband

Fair market value (in whole dollars) of any contraband recovered as a result of recovering the item which is the subject of the record. Can be entered only if RPS is entered. Must be blank or 0 if RPS is OTHER MEANS or PREVIOUSLY LOCATED.

E. Examples of Wanted Person Record Clear Messages

1. Wanted Felony Clear (with optional benefits data)

W;CWF.WA0340500.NAM/DOE, JOHN J.OCA/TEST123.20050429. HIT NCIC 20050804.2.5.2.2.20000.4000.9000(send)

2. Wanted Temporary Felony Clear

W;CTF.WA0340500.NAM/DOE, JOHN J.OCA/TEST123.20050429 (send)

F. Clear Acknowledgments


WWCIC TIME: 0837 DATE 050305 TO: ABCPD

WA0340500

CLEARED EWF NAM/DOE, JOHN J




WA0340500

CLEAR NAM/DOE, JOHN J OCA/TEST123



Revised 10/2010

CHAPTER 14: WACIC Wanted Persons File SECTION 11: Cancel Transactions



I. PROCEDURE

A. Cancel Transactions

1. When to Use a Cancellation Message

a. The cancel transaction deletes a record that is incorrect or invalid from the Wanted Person File. A wanted person record can be cancelled only by the agency that made the original entry. A cancellation message is utilized when the entering agency determines that the record is invalid; for example, the warrant, which was the basis for the record, has been dismissed.

b. When a wanted person record is cancelled, the entire record

including all data appended to the record by means of a supplemental record entry is automatically cancelled.



Revised 10/2010

B. Syntax

Field Example

Header W;

Message Key XWF




Date of Cancel 20000228

Reason for Person Record Removal CASE DROPPED

End of Text (send)

1. The cancel transaction consists of the message key, ORI, two record identifiers, and the optional date of cancel. Permissible record identifiers are NAM and OCA, NAM and WAC, or NAM and NIC (except for misdemeanor warrant records). The date of cancel is optional and if not used the record is cancelled as of the current date.

C. Wanted Person Cancel Field Edits

Field Edits

MKE

Must be a valid message key: XWF – Wanted Felony XTF – Wanted Temporary Felony

XWW – Wanted Misdemeanor XWJ – Wanted Juvenile

Originating Agency Identifier Must be a valid ORI and match the ORI in the record being cancelled.


The first of two identifiers to identify the record to be cancelled. Must be NAM.

2nd

Record Identifier The second of two identifiers to identify the record to be cancelled. Can be OCA, WAC or NIC.

Date of Cancel

OPTIONAL. If used must be a valid date in the format YYYYMMDD. Cannot be later than the current date nor earlier than the date of warrant in the record. If not used the record is canceled as of the current date.



CASE DROPPED

WARRANT DISMISSED

NOT WANTED

D. Examples of Wanted Person Record Cancellations



Revised 10/2010

1. Wanted Felony Cancellation

W;XWF.WA0340500.NAM/DOE, JOHN J.OCA/TEST123.. CASE DROPPED(send)

2. Wanted Temporary Felony Cancellation

W;XTF.WA0340500.NAM/DOE, JOHN J.OCA/TEST123(send)

3. Wanted Misdemeanor Cancellation

W;XWW.WA0340500.NAM/DOE, JOHN J.OCA/TEST123(send)

4. Wanted Juvenile Cancellation

W;XWJ.WA0340500.NAM/DOE, JOHN J.OCA/TEST123(send)

E. Cancel Acknowledgments


WWCIC TIME: 0837 DATE 050305 TO: LRKPX WA0340500 CANCELED EWF NAM/DOE, JOHN J WAC/05W0073824 OCA/05-1234


NCIC TIME: 0837 DATE: 050305 TO: ABCPD WA0340500 CANCEL NAM/DOE, JOHN J. OCA/TEST123



Revised 10/2010

CHAPTER 14: WACIC Wanted Persons File SECTION 12: Supplemental Cancellations



I. DEFINITIONS

A. Supplemental Cancellations

1. The supplemental data cancellation is used to remove supplemental data appended to a wanted person base record that is determined to be inaccurate or invalid. Supplemental data cannot be modified; in order to change a supplemental identifier, it must be cancelled and re-entered.

2. Canceling supplemental data appended to a wanted person record is restricted to the agency that entered the record.

B. Syntax

Field Example

Header W;

Message Key XNS




S/F Field(s) AKA/SMITH, JOHN J. DOB/19500101.19490804

End of Text (send)



Revised 10/2010

1. The supplemental data cancel transaction consists of the message key, ORI, two record identifiers, and the supplemental data field(s) or set(s) to be cancelled. Permissible record identifiers are NAM and OCA, NAM and WAC, or NAM and NIC (except for misdemeanor warrant records).

II. PROCEDURE

A. Wanted Person Supplemental Data Cancel Field Edits

Field Edits

MKE The MKE for all wanted person S/F identifier data cancels is XNS.

Originating Agency Identifier Must be a valid ORI and match the ORI in the record from which S/F identifier data is being cancelled.



2nd


Supplemental Field(s) The S/F identifier data field(s) to be canceled. Each must be identified by its MFC.

B. Example of Wanted Person Supplemental Data Cancellation

W;XN.WA0340500.NAM/DOE JOHN J.OCA/TEST123. DOB/19490804.19550101.VIN/987654321AB987654.1986.TOYT.2D. SOC/123456789(send)

C. Supplemental Data Cancel Acknowledgments



WA0340500

CANCELED SUPP NAM/DOE, JOHN J OCA/TEST123

DOB/19500101

VIN/987654321AB987654.1986.TOYT..2D..

SOC/123456789



Revised 10/2010



WA0340500

CANCEL SUPP NAM/DOE, JOHN J OCA/TEST123

DOB/19500101

VIN/987654321AB987654.1986.TOYT..2D.

SOC/123456789

D. Cancellation Guidelines

1. A maximum of nine identifiers of various kinds may be cancelled in one cancel message. Additional messages are required if more than nine identifiers are to be cancelled. Each AKA (or name spelling variation); DOB; SMTs, MNU; or SOC, etc.; is counted as one identifier. Each set of operator's license, license plate, or vehicle data (multiple data element fields) is counted as one identifier.

2. Aliases; dates of birth; scars, marks, tattoos, and other characteristics;

miscellaneous numbers; Social Security numbers; and caution and medical conditions to be cancelled should be set out in the cancel message in the same manner as in a supplemental record entry. That is, more than one identifier of the same type may follow the MFC without repetition of the MFC. However, character for character, each identifier to be canceled must be set out exactly as it appears in the supplemental record on file.

3. Each set of operator's license or license plate data (multiple data

element fields) must be preceded by OLN/ or LIC/, respectively, and all data elements of the set must appear exactly as they appear in the supplemental record on file. When canceling vehicle data, only the VIN and VMA are required following VIN/, with a period to account for the intervening VYR. For example, in Section 8.9, a cancellation of the first vehicle entry example would appear as follows:

VIN/1L69X6J023456..CHEV.

4. When a Wanted Person File record is cancelled, its entire

supplemental record is automatically cancelled.



Revised 10/2010

CHAPTER 14: WACIC Wanted Persons File SECTION 13: Stolen/Fraudulent Identifier Data



I. PROCEDURE

A. Stolen or Fraudulent Identifier Data Cancellation

1. The S/F identifier data cancellation is used to remove S/F identifiers

appended to a wanted person base record that is determined to be inaccurate or invalid. S/F identifiers cannot be modified; in order to change an S/F identifier it must be cancelled and re-entered.

2. Canceling stolen or fraudulent identifier data appended to a wanted

person record is restricted to the agency that entered the record.

B. Syntax


Header Y



ORI 9 Y A, N

WACIC Number WAC 10 Y A, N


OCA 9 Y A, N, S

Dental X-Rays Available DXR 1 C A

Dental Models MOD 1 C A

Photographs of Teeth Available

PHO 1 C A

Dentist's Remarks DRE 50 N A, N, S

Dental Characteristics DCH 221 C A, N, S



Revised 10/2010

1. The stolen or fraudulent identifier data cancel transaction consists of the message key, ORI, two record identifiers, and the stolen or fraudulent identifier data field(s) to be cancelled. Permissible record identifiers are NAM and OCA, NAM and WAC, or NAM and NIC (except for misdemeanor warrant records).

C. Wanted Person Stolen or Fraudulent Identifier Data Cancel Field Edits

Field Edits

MKE The MKE for all wanted person S/F identifier data cancels is XNS.

Originating Agency Identifier Must be a valid ORI and match the ORI in the record from which S/F identifier data is being cancelled.



2nd


Supplemental Field(s) The S/F identifier data field(s) to be canceled. Each must be identified by its MFC.

D. Example of Wanted Person Stolen/Fraudulent Identifier Data Cancel

W;XNS.WA0340500.NAM/DOE JOHN J.OCA/TEST123.

AKA/SMITH, JOHN J.DOB/19490904.19550101.SOC/123456890(send)

E. Cancel Acknowledgments



WA0340500

CANCELED SUPP NAM/DOE, JOHN J OCA/TEST123

AKA/SMITH, JOHN J

SOC/123456789



WA0340500

CANCEL S/F SUPP NAM/DOE, JOHN J OCA/TEST123

S/F NAM/SMITH, JOHN J

S/F NAM/JOHNSON, JOHN J



Revised 10/2010

CHAPTER 14: WACIC Wanted Persons File SECTION 14: Supplemental Dental



I. DEFINITIONS

A. Supplemental Dental Records

1. This section is provided for reference only. All dental information in wanted person records is entered, modified, or removed by the Washington State Patrol Missing and Unidentified Persons Unit.

B. Fields and Edits

1. Shown below in the order in which they appear in an entry transaction are the Wanted Person Dental Record message fields and their respective Message Field Codes (MFC), field lengths, entry requirements (required, optional, conditional), and data type.


Header Y



ORI 9 Y A, N

WACIC Number WAC 10 Y A, N


OCA 9 Y A, N, S

Dental X-Rays Available DXR 1 C A

Dental Models MOD 1 C A

Photographs of Teeth Available

PHO 1 C A

Dentist's Remarks DRE 50 N A, N, S

Dental Characteristics DCH 221 C A, N, S



Revised 10/2010

Data Type: A – Alphabetic

N – Numeric

S – Special Characters

C. Dental Characteristics

1. Refer to the NCIC Missing Persons file for updated dental entry

information (NCIC Missing Persons follows Chapter 5, Missing Persons).

D. OCA (Originating Agency Case Number)

1. The OCA field must be the same as the OCA in the base record.

E. ORI (Originating Agency Identifier)

1. The ORI field must be the same as the ORI listed in the original record.

F. WAC (WACIC Number)

1. The WAC must be the same as the WAC in the original record.

G. Additional Guidelines for a Supplemental Dental Record

1. The entry of a supplemental record to a wanted person record will cause a search of all unidentified person records.

2. If the code ALL is entered in the DCH field, the following will be transmitted after the DRE field in a positive response:

ALL 32 PERMANENT TEETH ARE PRESENT; NO TEETH

ARE DECAYED; NO TEETH HAVE BEEN RESTORED; AND

THERE ARE NO UNUSUAL CHARACTERISTICS.

3. If the code UNK is entered in the DCH field, the following will be transmitted after the DRE field in a positive response:

DENTAL CHARACTERISTICS (DCH) ARE NOT AVAILABLE

Chapter 14 Wanted

Documents

Transcript of Chapter 14 Wanted