Which Race Codes Should Be Used in an NLETS Inquiry
If you're a law enforcement officer, dispatcher, or records technician running queries through NLETS, you've probably stared at that race code field and wondered: "Am I using the right code?" It's a small field, but using the correct code matters — it affects whether you find the right person, avoid false hits, and keep your database accurate.
So here's the deal: the race codes used in NLETS inquiries come from the FBI's standard set, the same ones used in NCIC and the Uniform Crime Reporting program. Let me walk you through exactly which codes to use and why it matters.
What Is NLETS and Why Race Codes Matter
NLETS — the National Law Enforcement Telecommunications System — is the backbone that connects local, state, and federal agencies for criminal justice information sharing. When you run a query for a wanted person, a stolen vehicle, or a license plate check, NLETS is often the pipeline that carries that request to NCIC and brings the response back to your terminal.
The race code field is part of that identification package. It's not there to profile anyone — it's there to help narrow down hits when you're searching for a specific person. A good race code, combined with other descriptors like height, weight, age, and eye color, helps the system return relevant results instead of flooding you with unrelated records.
Here's what most people don't realize: the codes aren't just suggestions. They're standardized for a reason. On the flip side, when every agency uses the same code set, the system works. When officers improvise or guess, you get bad data, missed hits, and records that can't be matched across jurisdictions.
The Standard Race Codes for NLETS Inquiries
The codes used in NLETS come from the FBI's NCIC standards. Here's what you need to know:
Primary Race Codes
- W — White
- B — Black
- I — American Indian or Alaska Native
- A — Asian or Pacific Islander
- U — Unknown
These five codes cover the standard categories used in the National Crime Information Center database. You'll use one of these when entering a person into the Wanted Persons File, the Missing Persons File, or any other NLETS-supported query that asks for race.
Short version: it depends. Long version — keep reading.
What About Hispanic?
This is where things get tricky, and it's the question I hear most often. And hispanic is treated as an ethnicity, not a race, in NCIC and NLETS. There's no separate "H" race code in the main race field.
Instead, Hispanic is captured in a separate field — the ethnic field. So if you know someone is Hispanic, you enter the appropriate race code (W, B, A, I) in the race field, and you enter "H" in the ethnicity field. That's the correct way to document it.
Some older systems or legacy records might show "H" in the race field, but that's not the current standard. If you're entering new data, use the ethnicity field for Hispanic Surprisingly effective..
When to Use "Unknown"
The "U" code exists for a reason. If you genuinely don't know the person's race — maybe you only have a partial description, or the witness isn't sure — use U. Practically speaking, don't guess. Guessing introduces bad data into the system, and it can actually create more problems than it solves. A wrong race code can cause you to miss a legitimate hit or flag the wrong person.
The official docs gloss over this. That's a mistake.
How to Use These Codes Correctly in Practice
Running an NLETS inquiry isn't complicated, but a few practical things will help you get it right every time.
Enter the most specific code you can. If you know the person is Asian, use A. Don't default to "Unknown" just because you're not sure which type of Asian — A covers all Asian and Pacific Islander categories Most people skip this — try not to..
Use the ethnicity field for Hispanic. Remember: race and ethnicity are separate. Enter the race code based on physical appearance or race as perceived by the reporting party, then use the ethnicity field to note Hispanic origin if applicable.
When in doubt, use U. It's better to admit you don't know than to guess wrong. The system is designed to work with Unknown as a valid entry Not complicated — just consistent..
Be consistent with your agency. Your department may have specific policies or training on when to use each code. If you're new or unsure, ask your records unit or supervisor. Consistency across your agency's entries makes your local data cleaner and plays nicer with state and federal databases.
Common Mistakes People Make
After years of working with law enforcement databases, I've seen the same mistakes pop up over and over. Here's what to avoid:
Guessing instead of using Unknown. Officers sometimes pick a race code because they feel like they should have an answer. But a wrong code can actually hurt an investigation. If you guess White when the person is Black, and another agency is searching with the correct code, your entry won't come up in their results. The system matches on race — if the codes don't align, the hit gets missed.
Putting Hispanic in the race field. As I mentioned, this is an ethnicity, not a race. Using H in the race field is outdated and can cause matching issues. Use the ethnicity field.
Using outdated or agency-specific codes. Some agencies developed their own internal codes years ago. Those might work locally, but they won't translate to NLETS or NCIC. Stick to the federal standard.
Not updating records when new information comes in. If you initially entered "Unknown" but later learn the person's race, update the record. Keeping data current helps everyone.
Practical Tips for Officers and Dispatchers
A few things that will make your life easier:
- Double-check before you submit. It's a quick step, but it matters. A second glance at that race code field can save time later.
- Document your source. If you're entering information from a witness, note that in your records. The race code is only as good as the information it came from.
- Know your system. Different RMS (Records Management Systems) might label fields differently or handle ethnicity differently. Learn how your specific software handles the race and ethnicity fields.
- Ask if you're unsure. Records personnel deal with this stuff every day. They're a resource, not an afterthought.
FAQ
What if the person appears to be more than one race?
Use the code that best describes the person based on the information you have. In practice, if you're uncertain, use "Unknown. " The system is designed to work with limited information.
Can I leave the race field blank?
In most NLETS queries, you can — but it's not ideal. Leaving it blank reduces the search's effectiveness. If you have any information, use it That's the part that actually makes a difference..
Do these codes apply to all NLETS queries?
Yes. NLETS uses the NCIC standard codes across all person-related files — Wanted Persons, Missing Persons, Identity Theft, and others No workaround needed..
What about Native Hawaiian or Pacific Islander?
Those fall under "A" — Asian or Pacific Islander. You don't need to separate them.
Does the race code affect the priority or urgency of a query?
No. That's why the race code is purely for identification purposes. It doesn't affect BOLO priority, want status, or any other operational designation Nothing fancy..
The Bottom Line
Using the correct race codes in NLETS inquiries isn't glamorous, but it matters. It helps your agency find the right person, it keeps the national database clean, and it makes it easier for agencies across the country to work together.
The short version: use W, B, I, A, or U for race. Use the ethnicity field for Hispanic. And when you don't know, don't guess — use Unknown Most people skip this — try not to..
It's a small step that makes a big difference in getting the job done right.
