Police 10-Codes: APCO Standards, Agency Variations, Plain Language

Police 10-codes are a numerical shorthand system that lets officers and dispatchers exchange common information over the radio in a second or two instead of a full spoken sentence. Each code begins with “10-” followed by a number tied to a specific situation or request, such as 10-4 for “message received” or 10-20 for “advise your location.” The system was developed in 1937 and later standardized by APCO International, though in practice the exact meaning of a given code often depends on which agency is using it.

Where 10-Codes Came From and Why They Start With “Ten”

The system traces back to Charles “Charlie” Hopper, communications director for Illinois State Police District 10 in Pesotum, Illinois. Hopper wasn’t trying to invent a secret language. He was solving a hardware problem.

Police radios in the 1930s ran on vacuum tubes powered by small motor-generators called dynamotors. When an officer keyed the microphone, the dynamotor needed roughly a tenth to a quarter of a second to reach full power. Officers were trained to press the transmit button and pause before speaking, but under pressure they often forgot. Receivers clipped the first syllable of whatever was said, which usually meant the most important part of the message was gone.

Putting “ten” at the start of every transmission created a built-in buffer. The prefix gave the dynamotor time to spin up so the meaningful second number came through clearly, and it also worked as an audio flag to dispatchers that a coded message was incoming. Other agencies ran into the same hardware limits, and within a few years the “10-” prefix had spread across much of American policing.

The APCO Standard 10-Code List

As departments drifted into their own versions through the 1950s and 1960s, APCO tried to pull everyone back to a single reference. Project 2 in 1967 produced a standardized set of 10-signals, and Project 14 in 1974 revised and expanded them after a nationwide survey.1APCO International. Projects APCO’s committee argued a unified list would improve accuracy between systems, speed response times, tighten radio discipline, add a thin layer of privacy, and simplify training.

The codes below reflect that APCO standard. They cover radio operations, officer status, traffic incidents, and emergency alerts.

  • 10-1: Signal weak
  • 10-2: Signal good
  • 10-3: Stop transmitting
  • 10-4: Message received (acknowledged)
  • 10-7: Out of service
  • 10-8: In service
  • 10-9: Repeat last transmission
  • 10-10: Fight in progress
  • 10-15: Civil disturbance
  • 10-16: Domestic problem
  • 10-20: Advise your location
  • 10-22: Disregard
  • 10-23: Arrived at scene
  • 10-24: Assignment complete
  • 10-27: Driver’s license information request
  • 10-28: Vehicle registration information request
  • 10-29: Check records for warrants
  • 10-31: Crime in progress
  • 10-32: Person with gun
  • 10-33: Emergency
  • 10-41: Beginning shift
  • 10-42: End of shift
  • 10-50: Traffic accident (PD: property damage, PI: personal injury)
  • 10-51: Request tow truck
  • 10-52: Request ambulance
  • 10-55: Intoxicated driver
  • 10-70: Fire alarm
  • 10-78: Request assistance
  • 10-80: Pursuit in progress
  • 10-89: Bomb threat
  • 10-95: Subject in custody
  • 10-99: Wanted or stolen

A few of these have crossed into everyday American English. Most people recognize 10-4 as “got it” and 10-20 as a question about location. The rest stay inside law enforcement, and even there, meanings aren’t always consistent.

Why the Same Code Can Mean Different Things

APCO had no enforcement power, and no federal law required departments to adopt the standard list. Agencies kept their homegrown codes, and most still do.2Police1. Police 10 Codes vs. Plain Language: The History and Ongoing Debate The result is a patchwork where the APCO definitions serve as a rough reference rather than a binding standard, and a single code can carry different meanings on different sides of a county line.

10-50 is a good example. Under APCO it means a traffic accident. Some departments use it exactly that way. Others assign 10-50 to a tow truck request, a routine traffic stop, or something else. 10-99 is “wanted or stolen” in the APCO system, but some agencies use the same number to flag an open garage door, and others reserve it for an officer in trouble.

State agencies often maintain code sets that diverge from the municipal departments they work alongside. Smaller departments sometimes borrow a larger neighbor’s codes to simplify shared-frequency communication, which helps locally and adds another variant to the national mix. Academy programs and field training officers teach the local list, not the APCO recommendations, so an officer transferring between departments has to relearn the codes and fight years of muscle memory in the process.

The practical takeaway for anyone looking up a code: a definition pulled from a general list, including the one above, tells you what the code probably means. If the context matters, confirm with the specific agency.

When Officers Must Switch to Plain Language

Communication failures during the September 11, 2001 attacks and Hurricane Katrina in 2005 forced the federal government to confront the 10-code problem directly. Responders from different agencies couldn’t understand each other’s coded transmissions during exactly the kind of large-scale emergency where clear communication matters most. Congressional hearings documented how misunderstood codes delayed rescue efforts and put personnel at risk.3Congress.gov. 109th Congress Senate Event LC10941

The Department of Homeland Security built plain language requirements into the National Incident Management System. A December 2006 NIMS Alert made the rule explicit: plain language is required for multi-agency, multi-jurisdiction, and multi-discipline events such as major disasters and exercises.4FEMA. NIMS Alert: Plain Language The 2017 NIMS doctrine reinforced it, directing personnel to use plain language and clear text in all communications between organizational elements during an incident and to avoid acronyms or jargon unique to any single agency.5FEMA. National Incident Management System

Federal preparedness grant funding was tied to compliance starting in fiscal year 2006, which gave the policy real teeth. The same NIMS Alert drew a clear boundary, though: the plain language requirement does not abolish 10-codes in everyday department communications, and using codes for routine daily operations will not cost an agency its federal funding.4FEMA. NIMS Alert: Plain Language

Most agencies now run in a dual mode. Officers use familiar 10-codes for routine patrol and dispatch, then switch to plain English when an incident scales up to involve outside agencies or federal coordination.

Why Some Departments Still Defend 10-Codes

Resistance to dropping 10-codes isn’t just habit. A three-digit code can convey an urgent situation in under a second, and the plain-language equivalent takes several seconds longer to say. In a foot pursuit or an unfolding violent encounter, officers argue those seconds matter.

There’s also an information security argument. Unencrypted plain-language transmissions are easier for the public to follow through scanner apps and streaming services, which means suspects, media, and bystanders can track tactical operations in real time. Numerical shorthand gives at least a thin layer of obscurity, though anyone willing to spend a few minutes online can find a code translation chart.

The counterargument is simple: a code that means different things to different people is worse than no code at all. During a multi-agency incident, one misunderstood number can send resources to the wrong location or leave an officer without backup. That is the risk the NIMS plain-language rule was written to eliminate.