Department Of The Air Force Police

Understanding the Air Force Police: What It Actually Is

The organization you are referring to has gone through multiple name changes over the years. What most people call the Department Of The Air Force Police is now officially called Security Forces. It used to be Military Police, then Air Force Police, then Security Police, and finally settled on Security Forces when the Air Force and Space Force split into separate departments under the Department of the Air Force. The acronym you will see everywhere is AFSF or just SF. The primary job is base security and law enforcement. This means guarding nuclear weapons, protecting critical infrastructure, conducting criminal investigations through the Office of Special Investigations, and running the installation's law enforcement functions. They also do force protection duties, airfield operations security, and tactical employment of security forces in combat zones. I spent years dealing with the procedural side of this organization when it still went by the old names. The most confusing part for outside people is the jurisdictional overlap. AFSF officers have Law Enforcement Authorization Designations, which give them federal POPO status under 34 U.S.C. 40581. That means they can carry firearms, make arrests, and execute warrants anywhere on a military installation. But their authority outside the gate depends heavily on whether that base has a jurisdictional agreement with local law enforcement, and even then it is complicated.

How It Works in Practice

Security Forces members typically hold the 3D series of AFSCs. The main ones are 3E0X1 for Security Forces enlisted, 31A for Law Enforcement, and 3A0X1 for Force Protection. Investigators fall under the OSI umbrella with their own separate career field. The pay grades and career progression follow the standard Air Force structure, but the duty environment is what sets it apart. Base security checkpoints run 24/7 on most installations. You will see Security Forces officers checking credentials at the main gate, searching vehicles, and maintaining visitor management systems. The day-to-day also involves responding to domestic disturbances, traffic enforcement, and criminal calls. On deployed locations, the work shifts completely toward combat support and base defense. Here is something most people do not realize about the investigation side. OSI handles criminal investigations across the entire Air Force and Space Force, but AFSF still maintains a parallel investigative capability at the unit level for minor incidents. The boundary between what OSI takes and what local Security Forces handles is not always clear cut, and it varies by installation. I learned this the hard way when a unit commander on my end tried to process a theft case internally without realizing the dollar threshold triggered mandatory OSI involvement. The workaround was to get the installation's OSI liaison officer to confirm jurisdictional thresholds in writing before proceeding, which saved us from having to redo three weeks of investigative work. That file review process alone takes about four hours if you know exactly which regulations to reference, or half a day if you are guessing.

Common Pitfalls and What People Get Wrong

The biggest misconception is that Security Forces only do police work on base. In reality, they are the most deployable combat arms branch in the Air Force. When there is a conflict or crisis, SF units go first and stay the longest. The 24th Security Forces Regiment, for example, has been involved in nearly every major deployment since the 1990s. Their training pipeline includes airfield operations, combatives, marksmanship, and tactical squad leader courses. Another thing nobody warns you about is the regulatory maze. The governing directives change frequently, especially after organizational realignments. AFI 31-117 covers Security Forces generally, but AFI 31-121 handles physical security, and AFI 31-122 covers operational security. Then there is Air Force Instruction 31-142 for law enforcement functions, plus countless supplemental instructions from individual bases. Keeping up with which directive applies to which situation is genuinely difficult, and relying on outdated versions can create liability issues. The downsides of this structure are real. Jurisdictional ambiguity between AFSF and local agencies creates friction, especially on installations near urban areas where mutual aid agreements are poorly defined. Base commanders have wide discretion over how much authority they delegate to local police versus keeping it internal, and that leads to inconsistent practices across the force. Additionally, the dual-hat nature of some command relationships between Security Forces and base operations can create conflicts of interest when the commander wants something done quickly and the SF squadron lead knows the proper procedure would take longer.

If you need current official information or want to verify specific policies, the best starting point is the Air Force Security Forces career page on the official .mil site, or you can contact your local installation's Security Forces Squadron public affairs office directly. Those channels will give you the most accurate and up to date guidance available.