AFI31-204.pdf

BY ORDER OF THE

SECRETARY OF THE AIR FORCE

AIR FORCE INSTRUCTION 31-204

14 JULY 2000

Incorporating Change 1, 20 July 2007

Security

AIR FORCE MOTOR VEHICLE

TRAFFIC SUPERVISION

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

ACCESSIBILITY: Publications and forms are available on the e-Publishing website at www.e-publishing.af.mil for downloading or ordering.

RELEASABILITY: There are no releasability restrictions on this publication.

OPR: HQ AFSPA/SPO Certified by: AF/SF (Brig Gen R. A. Coleman) Supersedes AFI 31-204, 1August 1997. Pages: 40

This instruction implements Air Force Policy Directive (AFPD) 31-2, Law Enforcement. It assigns responsibilities and establishes procedures for motor vehicle traffic supervision on Air Force installations in the continental United States (CONUS) and overseas (OCONUS) areas. This includes, but is not lim-ited to, granting, suspending, or revoking the privilege to operate a privately owned vehicle (POV); regis-tration of POVs; administration of vehicle registration and driver performance records; driver improvement programs; police traffic supervision; and off-installation traffic activities.

SUMMARY OF CHANGES

This interim change eliminates the requirement for privately owed vehicles to be registered with the Air Force or other DoD agency to be operated on an Air Force installation. The IC re-titles Chapter 3 from “Motor Vehicle Registration” to “Privately Owned Vehicle Operation Requirements.” A bar ( | ) indicates a revision from the previous edition.

Chapter 3, REPLACED. This chapter has been substantially revised and must be completely reviewed.

Chapter 1— INTRODUCTION 4

1.1. Program Management

1.2. Responsibilities

1.3. Delegation Of Authority

Chapter 2— DRIVING PRIVILEGES 6

2.1. Requirements for Driving Privileges

2.2. Stopping and Inspecting Personnel or Vehicles

2.3. Implied Consent to Blood, Breath, or Urine Tests

http://www.e-publishing.af.mil

2 AFI31-204 14 JULY 2000

2.4. Implied Consent to Vehicle Impoundment

2.5. Suspension or Revocation of Driving Privileges

2.6. Reciprocal Procedures

2.7. Administrative Due Process for Suspensions and Revocations

2.8. Alcohol and Drug Abuse Programs

2.9. Restoration of Driving Privileges on Acquittal

2.10. Restricted Driving Privileges or Probation

2.11. Extensions of Suspensions and Revocations

2.12. Reciprocal State-Military Action

Chapter 3— PRIVATELY OWNED VEHICLE OPERATION REQUIREMENTS 13

3.1. General

3.2. Driver and Vehicle Requirements

3.3. Motorcycles, Motor Scooters, and Mopeds

3.4. Rental Vehicles

3.5. AF Form 75, Visitor/Vehicle Pass

3.6. Handicapped Person Identification

Chapter 4— TRAFFIC PLANNING AND CODES 14

4.1. Traffic Planning

4.2. Installation Traffic Codes

4.3. Traffic Law Enforcement Principles

4.4. Speed-measuring Devices

4.5. Traffic Accident Investigation

4.6. Traffic Accident Investigation Reports

4.7. Use of Traffic Accident Investigation Report Data

4.8. Parking

4.9. Traffic Violation Reports

4.10. Standards and Procedures for Processing Intoxicated Drivers

4.11. Blood Alcohol Concentration Standards

4.12. Chemical Testing Policies and Procedures

4.13. Detection, Apprehension, and Testing of Intoxicated Drivers

4.14. Voluntary Breath and Bodily Fluid Testing Based on Implied Consent

4.15. Involuntary Extraction of Bodily Fluids in Traffic Cases

AFI31-204 14 JULY 2000 3

4.16. Testing at the Request of the Apprehended Person

4.17. Off-installation Traffic Activities

4.18. Compliance With Local and State Laws

4.19. Civil-Military Cooperative Programs

Chapter 5— DRIVING RECORDS AND THE TRAFFIC POINT SYSTEM 28

5.1. Driving Records

Table 5.1. Suspension/Revocation of Driving Privileges (See Notes 1 and 2)

5.2. The Traffic Point System

5.3. Point System Application

Table 5.2. Point Assessment for Moving Violations (See Note 1)

5.4. Point System Procedures

5.5. Disposition of Driving Records

Chapter 6— IMPOUNDING PRIVATELY OWNED VEHICLES 34

6.1. General

6.2. Standards for Impoundment

6.3. Towing and Storage

6.4. Procedures for Impoundment

6.5. Search Incident to Impoundment Based On Criminal Activity

6.6. Disposition Of Vehicles After Impoundment

6.7. Forms Prescribed

Attachment 1— GLOSSARY OF REFERENCES, ABBREVIATIONS, AND ACRONYMS 38

Attachment 2— IC 2000-1, TO AFI 31-204, AIR FORCE MOTOR VEHICLE TRAFFIC

SUPERVISION 40

4 AFI31-204 14 JULY 2000

Chapter 1

INTRODUCTION

1.1. Program Management. This instruction implements policy, assigns responsibility, and establishes procedures for motor vehicle traffic supervision on Air Force installations located in the continental United States (CONUS) and overseas (OCONUS) areas.

1.1.1. This includes, but is not limited to:

1.1.1.1. Granting, suspending, or revoking the privilege to operate a POV.

1.1.1.2. Registration of POVs.

1.1.1.3. Administration of vehicle registration and driver performance records.

1.1.1.4. Driver improvement programs.

1.1.1.5. Police traffic supervision.

1.1.1.6. Off-installation traffic activities.

1.1.2. Commanders can modify these policies and procedures in the following instances:

1.1.2.1. When dictated by host nation relationships, treaties, and agreements.

1.1.2.2. When traffic operations under military supervision necessitate special measures to meet mission unique requirements or to protect public safety.

1.1.3. Safe and efficient movement of personnel and vehicles is the objective of every traffic control program. Program goals should focus on ways to reduce traffic-related deaths, injuries, and property damage.

1.2. Responsibilities.

1.2.1. Air Force Chief of Security Police (HQ USAF/SP). Establishes policy to assist installation commanders in the administration of local traffic supervision and enforcement programs.

1.2.2. Air Force Security Police Agency (HQ AFSPA). Provides guidance to MAJCOMs and field units on implementing traffic safety and supervision programs.

1.2.3. Major Command Chief of Security Police (MAJCOM/SP). Each MAJCOM/SP manages com-mand unique traffic supervision and enforcement programs. They provide key staff support to instal-lation commanders and their assigned security police units.

1.2.4. Installation Commander. Establishes and manages the local installation traffic supervision pro-gram. They have broad authority to regulate the movement of traffic and personnel on their installa-tions. Each must develop local procedures to ensure safe pedestrian and vehicle traffic. To meet goals and objectives, installation commanders integrate safety, engineering, legal, and law enforcement resources into their traffic review and planning processes.

1.2.5. Chief of Security Police. The CSP is the installation commander's principal advisor on issues pertaining to the safe movement of personnel and traffic. The CSP exercises staff responsibility for directing, regulating, and controlling traffic, and enforcing installation rules pertaining to traffic con-

AFI31-204 14 JULY 2000 5

trol. CSPs assist traffic engineers by performing traffic control studies to gather information on traffic problems and usage patterns.

1.2.6. Installation Safety Officer. The safety officer develops traffic accident prevention initiatives in support of the installation traffic safety program. They also help the CSP and other agencies with accident and incident investigation.

1.2.7. Installation Civil Engineer (CE). The CE plans, designs, constructs, and maintains streets, highways, and abutting lands. CEs select, determine appropriate design, procure, construct, install, and maintain permanent traffic and parking control devices in coordination with the CSP and installa-tion safety officer. They ensure traffic signs, signals, and pavement markings conform to the stan-dards in the current Manual on Uniform Traffic Control Devices for Streets and Highways. They also ensure planning, design, construction, and maintenance of streets and highways conform to National Highway Safety Program Standards, and where applicable, host nation requirements.

1.2.8. Installation Traffic Engineer. Traffic engineers conduct formal traffic engineering studies.

They apply traffic engineering measures and control devices to reduce the number and severity of traf-fic accidents. If there is no installation traffic engineer, the installation commander may request sup-port services by contacting the Commander, Military Traffic Management Command, 5611 Columbia Pike, Falls Church VA 22041-5050.

1.2.9. Mental Health Office. The mental health substance abuse control program provides alcohol/ drug education, treatment, and rehabilitation to personnel identified with alcohol and/or drug abuse problems.

1.3. Delegation Of Authority. Installation commanders can delegate their authority under this instruc-tion to their vice commander, support group commander, or other appropriate official. Those selected for delegation must not occupy a law enforcement, investigative, or other position which might lead to a con-flict of interest or the appearance of such conflict during their administration of the motor vehicle traffic supervision program. Installation commanders must coordinate their letters of delegation through their installation staff judge advocate

6 AFI31-204 14 JULY 2000

Chapter 2

DRIVING PRIVILEGES

2.1. Requirements for Driving Privileges.

2.1.1. Driving a government owned vehicle (GOV) or POV on an Air Force installation is a privilege granted by the installation commander. If you accept that privilege, you must comply with the laws and instructions governing motor vehicle operation and registration on the installation. Consequently, everyone operating a motor vehicle on a military installation must produce, upon request from the security police, the following:

2.1.1.1. Proof of vehicle ownership or registration if required by the issuing authority.

2.1.1.2. A valid state, overseas command, host nation, or international driver’s license and/or AF Form 2293, US Air Force Motor Vehicle Operator’s Identification Card, supported by a DD Form 2, US Armed Forces Identification Card. Locally determine acceptable identification media for civilian personnel and base contractors. Note: Each installation commander must deter-mine if international drivers licenses are recognized and accepted by the local (civilian) jurisdic-tion, and if so, will their use be authorized on the installation. As a general rule, most CONUS civilian jurisdictions will honor use of international drivers licenses for short periods of time by non-resident visitors and assigned military personnel. When practical, installation commanders should assimilate local policy to preclude conflicting policy.

2.1.1.3. If required by the jurisdiction in which the vehicle is operated, a valid record of motor vehicle safety inspection, emission control test, or any other test, evaluation, safety inspection, or other documents required by local, state, or host nation law or agreement. Note: In some instances, a state or other governing jurisdiction in which a vehicle is registered may require, as a condition for keeping registration/plates issued by that state or jurisdiction, a safety or other inspection even when the vehicle is operated in another state or jurisdiction. Though not enforce-able (in another state), failure to comply may invalidate the vehicle registration leaving the owner/ operator in a precarious legal position. In such cases, it becomes the owner's responsibility to comply with their "home state" or other issuing jurisdiction requirements in addition to host state requirements. Owners should secure host registration when unable to comply with licensing and/ or registration requirements issued by their home state or other jurisdiction.

2.1.1.4. Proof of current vehicle insurance when required by state, host nation, or the installation commander.

2.2. Stopping and Inspecting Personnel or Vehicles.

2.2.1. The security police may stop vehicles on military installations based on the installation com-mander's authority. The following principles govern the stopping of motor vehicles:

2.2.1.1. In overseas areas, security police may stop, search, and detain vehicles on or off base as determined by host nation agreements and local command policy.

2.2.1.2. AFI 31-209, The Air Force Resource Protection Program, local command instructions, and policies established by the installation commander will detail stop, inspection, search, and impoundment of motor vehicles at CONUS installation entry gates and in Air Force restricted areas.

AFI31-204 14 JULY 2000 7

2.2.1.3. On-base traffic stops and inspections (other than at entry gates and restricted areas) of POVs is authorized when there is a reasonable basis to believe it’s necessary to enforce a traffic regulation or when there is suspicion of criminal activity.

2.2.2. MAJCOMs responsible for overseas military installations must provide their installation com-manders with written guidelines governing stop, inspection, search, and impoundment of vehicles.

This guidance must reflect host nation agreements and pass appropriate legal review. Note: A theater commander or those commanding unified forces may direct policy covering all installations under their command. In this case, MAJCOMs must review those policies before issuing their guidance.

2.3. Implied Consent to Blood, Breath, or Urine Tests. Drivers give consent to evidential tests for alcohol or other drug content of their blood, breath, and/or urine as a condition to accepting installation driving privileges. This consent applies when lawfully detained, apprehended, or cited for any impaired driving offense committed while driving or in physical control of a motor vehicle on an Air Force instal-lation.

2.4. Implied Consent to Vehicle Impoundment. As a condition to accepting installation driving privi-leges, drivers must give their consent for the removal and temporary impoundment of their POV if their POV is: 1) Illegally parked for unreasonable periods; 2) Interferes with traffic operations; 3) Creates a safety hazard; 4) Disabled by accident or incident; 5) Left unattended in, or adjacent to, a restricted, con-trolled, or off-limits area; and 6) Abandoned. Drivers also agree to reimburse an authorized agency or contractor for the cost of towing, storage, and disposal should a need arise to remove or impound their motor vehicle because of a situation described above.

2.4.1. Installation commanders define in local procedures or supplement to this instruction, the defi-nitions for "unreasonable periods," "abandoned," and other terms relevant to enforcement action under paragraph 2.4. Incorporate those instructions, procedures, and definitions into the local instal-lation traffic code and make them known to the general public.

2.5. Suspension or Revocation of Driving Privileges . Installation commanders may suspend or revoke installation driving privileges and POV registration for lawful reasons both related and unrelated to traffic violations or safe vehicle operations. Installation commanders must incorporate procedures gov-erning suspension and revocation in local publications or supplement to this instruction. Make these known to the general public.

2.5.1. Suspensions.

2.5.1.1. Installation commanders can suspend driving privileges for serious violations or when lesser measures fail to improve a driver's performance. The commander may also suspend or revoke licenses for up to 12 months if a driver continually violates installation parking standards, or habitually violates other standards considered non-moving in nature. Installation commanders determine suspension and revocation policy for non-moving violations, as well as what constitutes a non-moving violation on their installation (i.e., performing unauthorized repair; failure to regis-ter; unauthorized modifications or alterations; failure to maintain safety standards, etc.). Make these standards part of the local installation traffic code and take reasonable steps to make them known to the general public.

2.5.1.2. The installation commander has discretionary authority and may withdraw anyone's authorization to operate a government or privately owned motor vehicle on the installation.

8 AFI31-204 14 JULY 2000

2.5.1.3. Installation commanders will immediately suspend installation GOV or POV driving privileges pending resolution of an intoxicated driving incident which involves active duty mili-tary personnel, their family members, retired members of the military service, and DoD civilian personnel. This applies regardless of the geographic location of an intoxicated driving incident.

Installation commanders can only suspend privileges of non-DoD affiliated civilians for incidents occurring on the installation or in the areas subject to their military traffic jurisdiction. After a review of available evidence as specified in paragraph 2.6., suspend driver’s privileges pending resolution of the intoxicated driving incident under the circumstances outlined below:

2.5.1.3.1. Refusal to take or complete a lawfully requested chemical test to determine blood alcohol content BAC) or breath alcohol content (BrAC) for alcohol or other drugs.

2.5.1.3.2. Operating a motor vehicle with BAC or BrAC of 0.10 percent by volume or higher.

2.5.1.3.3. Operating a motor vehicle with a BAC or BrAC below 0.10 percent blood alcohol by volume if the jurisdiction in which the vehicle is operated imposes a suspension for a BAC or BrAC level below 0.10.

2.5.1.3.4. On an arrest report or other official document reasonably showing an intoxicated driving incident occurred.

2.5.2. Revocation.

2.5.2.1. The installation commander will immediately revoke driving privileges for a period of not less than one year in the following circumstances:

2.5.2.1.1. A person is lawfully detained for intoxicated driving and refuses to submit to or complete tests to measure blood alcohol or drug content as required by the law of the jurisdic-tion, installation traffic code, or this instruction.

2.5.2.1.2. A conviction, nonjudicial punishment, or a military or civilian administrative action resulting in the suspension or revocation of a driver’s license for intoxicated driving. Official documentation is required as the basis for this type of revocation action.

2.5.2.1.3. When a serious incident involving a motor vehicle occurs and the installation com-mander determines immediate revocation of driving privileges is required to preserve public safety or the good order and discipline of military personnel.

2.5.2.2. The CSP develops plans and procedures to forward revocation, suspension, and driving records to gaining commanders and to initiate appropriate staff action when receiving similar records from losing commanders of inbound personnel.

2.5.2.3. When temporary suspensions are followed by revocations, compute the revocation period from the original suspension date, exclusive of any period during which full driving privileges were restored pending resolution of charges.

2.5.2.4. Installation commanders may impose multiple suspensions to run consecutively or con-currently.

2.6. Reciprocal Procedures.

2.6.1. Air Force installation commanders will honor revocations issued by other installation com-manders regardless of service component affiliation. Revocations remain in effect during reassign-

AFI31-204 14 JULY 2000 9

ment unless the issuing authority terminates the revocation before reassignment. Installation commander may honor suspensions as determined on a case by case basis. Anyone with suspended or revocated privileges may petition an installation commander for partial or limited driving privileges.

2.7. Administrative Due Process for Suspensions and Revocations.

2.7.1. When considering suspending or revoking someone’s driving privileges, notify that person in writing and tell them what action you are taking and the reason for it. Coordinate this notice with the base legal office.

2.7.2. Except for incidents outlined in para 2.5.1.3. and 2.5.2.1., do not suspend or revoke a person's driving privileges until they are notified (or reasonable attempts made) and offered an administrative hearing. Installation commanders determine when a suspension or revocation takes effect once mak-ing or attempting this written notice. Only in unusual circumstances should you make verbal notifica-tions. Unless an application for a hearing is made within the prescribed period, suspension or revocation takes place on the prescribed date and time. Installation commanders determine the time period for staying a suspension or revocation action after receiving a request for a administrative hear-ing. For offenses outlined in para 2.5.1.3. and 2.5.2.1., an installation commander will authorize an immediate preliminary suspension based on reliable evidence. Such evidence can include witness statements, a military or civilian police report, chemical test results, a refusal to complete chemical testing, video tapes, written statements, field sobriety test results, or other evidence.

2.7.2.1. Installation commanders or their designee must conduct evidence reviews as soon as pos-sible, but no later than three duty days following final assembly of evidence.

2.7.2.2. For active duty military personnel, send a written notice of preliminary suspension for intoxicated driving to their commander or reasonable equivalent. For non-installation, non-DoD affiliated civilians, present the written notice of preliminary suspension for intoxicated driving either in person (preferred) or by certified mail. If the person is employed on the installation, send the notice to their commander or reasonable equivalent.

2.7.2.3. Advise the individual of the following in the preliminary suspension notification for intoxicated driving:

2.7.2.3.1. Suspension can be made a revocation under the authority of paragraph 2.5.2. of this

AFI.

2.7.2.3.2. The right to request restoration of driving privileges pending investigation or reso-lution of the incident (direct request letters to the installation commander or designee).

2.7.2.3.3. The right of military personnel to present evidence and witnesses and be repre-sented by a civilian counsel (at their own expense) or assigned military counsel. Commanders determine the availability of specific (by name) military counsel requests.

2.7.2.3.4. The right of DoD civilian employees to have a personal representative present at the administrative hearing in accordance with applicable laws and instructions.

2.7.2.3.5. Amount of time the individual has to respond and request the administrative hearing before the preliminary suspension or revocation becomes permanent.

2.7.2.3.6. Direction to sign the acknowledgment of receipt and to return the signed letter to the address shown in the letter.

10 AFI31-204 14 JULY 2000

2.7.2.3.7. Requested hearings must take place within a reasonable period which is determined by the installation commander. A preliminary suspension for intoxicated driving remains in effect until the installation commander makes a final decision. However, if no decision is made within 30 days of the preliminary suspension or revocation, restore full driving privi-leges until the accused is notified of the final hearing results.

2.7.3. Hearings for intoxicated driving will cover only the pertinent issues of whether: 1) The law enforcement official had reasonable grounds to believe the person was driving or was in physical con-trol of a motor vehicle while under the influence of alcohol or other drugs; 2) The person was lawfully cited or apprehended for an intoxicated driving offense; 3) The person was asked to submit to a test for alcohol or other drug content of blood, breath, or urine and was informed of the consequences for refusing to take or complete such a test; 4) The person refused to submit to the test for alcohol, breath, or urine; failed to complete the test; submitted to the test and the result exceeded the amount of allowed blood alcohol content; results indicate the presence of other drugs for an on-installation apprehension or in violation of state laws for an off-installation apprehension; and 5) The testing methods used were valid and reliable, and the results accurately recorded and evaluated.

2.7.3.1. For revocation actions under paragraph 2.5.2.1. for intoxicated driving, the revocation is mandatory on conviction or other findings that confirm the charge.

2.7.3.1.1. The date of conviction or other findings that confirm the charge is the effective date of the revocation.

2.7.3.1.2. You may place the notice that revocation is automatic in the suspension letter, or send a separate letter. Revocation is not effective until receipt of the written notice, or the showing that you made reasonable attempts to notify the individual.

2.7.3.1.3. Revocations cancel any partial or restricted driving privileges previously granted.

Once revocation is acknowledged, a person may petition for the restoration of all or partial driving privileges.

2.8. Alcohol and Drug Abuse Programs.

2.8.1. Refer military personnel involved in any intoxicated (drug or alcohol) motor vehicle incident to Substance Abuse Office, Drug and Alcohol Control for evaluation.

2.9. Restoration of Driving Privileges on Acquittal. When an official report or finding determines lack of guilt (not guilty) or when charges are dismissed or reduced to an offense not amounting to intoxi-cated driving, vacate the suspension of driving privileges except when:

2.9.1. The preliminary suspension was based on refusal to take a BAC test.

2.9.2. Operating a motor vehicle with a BAC of 0.10 percent by volume or higher or in violation of the law of the jurisdiction that is bring assimilated on the military installation.

2.9.3. The person was driving or in physical control of a motor vehicle while under another prelimi-nary suspension or revocation.

2.9.4. The state or host nation authorities made an administrative determination to suspend or revoke driving privileges based on local law or pertinent regulations.

AFI31-204 14 JULY 2000 11

2.9.5. The individual failed to complete a formally directed substance abuse or driver’s training pro-gram.

2.10. Restricted Driving Privileges or Probation.

2.10.1. Unless prohibited by higher authority, host nation authority, or other publication, installation commanders may authorize partial or restricted driving privileges to those whose authority to drive on military installations was suspended or revocated by a military service authority. Ensure the individ-ual’s driving credentials (civilian state, international, host nation, etc.) are still valid.

2.10.2. Without due cause, do not grant restricted driving privileges, probation, or reinstatement to any person whose civilian driver’s license is under suspension or revocation by a state, federal, or host nation licensing authority. If absolutely necessary to do so (and for on base privileges only), coordi-nate with the installation staff judge advocate. Note: This option applies only to installations exercis-ing exclusive military jurisdiction. Outline procedures for applying for partial or restricted privileges in the base supplement to this AFI or in another appropriate publication. Only consider requests in which there is extreme hardship and there are no other workable alternatives. Do not consider the granting of limited privileges as an alternative to administrative discharge action when discharge is the more appropriate action. Installation commanders must weigh heavily the potential liability inherent when an individual with a suspended or revoked state, host nation, or other license is allowed to operate a motor vehicle on the installation. Administrative separation may be appropri-ate when the loss of driving privileges renders someone ineffective and incapable of performing their military duties, and a change in duty position is not reasonable.

2.11. Extensions of Suspensions and Revocations.

2.11.1. Increase by two years the suspension or revocation period when someone is discovered driv-ing in violation of their original suspension or revocation. The unit or installation commander may also take administrative or disciplinary action.

2.11.2. Extend the suspension or revocation of installation driving privileges until the offender com-pletes an approved remedial driver training course, drug or alcohol program, or other program deemed necessary by the installation commander or local authorities.

2.12. Reciprocal State-Military Action.

2.12.1. Statutory authority may exist within some host nations or states for reciprocal suspension and revocation of driving privileges. If so, the installation commander should honor the reciprocal agree-ments with the state or host nation driver licensing authorities. On receipt of written notice, the receiving party may suspend or revoke driving privileges as if the violations or incidents occurred within its own jurisdiction.

2.12.1.1. Use the following procedures if statutory authority does not provide for formal military reciprocity:

2.12.1.1.1. When such authority suspends or revokes a license, automatically terminate the individual’s installation GOV and POV driving privileges. Take only comparable military administrative actions (suspensions, revocation, or point assessment) for those off-base viola-tions reported by local, state, or host nation authorities.

12 AFI31-204 14 JULY 2000

2.12.1.1.2. In the CONUS, notify the licensing authority of the state where a license is issued when revoking a person’s installation driving privileges (for a period of one year or more only) following final adjudication of an intoxicated driving offense or for refusal to submit to a BAC/BrAC test. Include in the notification the basis for the revocation and the BAC/BrAC level.

2.12.2. Provisions of the applicable status of forces agreement (SOFA) and the law of the host nation concerning reciprocal suspension and revocation can affect OCONUS installation commanders.

When permitted at a particular overseas installation and to the extent an agreement concerning reci-procity exists, the installation commander must have prior authorization to negotiate and conclude such an international agreement in accordance with applicable directives.

AFI31-204 14 JULY 2000 13

Chapter 3

PRIVATELY OWNED VEHICLE OPERATION REQUIREMENTS

3.1. General. The installation commander is responsible for ensuring all vehicles entering their installa-tion are controlled. Installation commanders may extend or deny the privilege of operating a motor vehi-cle on the installation to anyone they deem appropriate.

3.2. Driver and Vehicle Requirements. All operators of privately owned vehicles on Air Force installa-tions will possess the following:

3.2.1. A valid state, overseas command, host nation or international driver’s license (within appropri-ate classification), supported by identification authorizing base entry.

3.2.2. A certificate of state registration as required by the state in which the vehicle is registered.

3.2.3. Proof of compliance with the minimum requirements of the automobile insurance laws or reg-ulations of the state, host nation, or command.

3.2.4. Proof of compliance with safety and emissions inspection for the state or local jurisdiction in which the vehicle is licensed.

3.2.5. Proof of compliance with local vehicle emission inspection if required by the State, and main-tenance requirements.

3.3. Motorcycles, Motor Scooters, and Mopeds. See AFI 91-207, The US Air Force Traffic Safety Pro-gram, for safety course requirements to operate motorcycles, motor scooters, and mopeds on AF installa-tions.

3.4. Rental Vehicles. Rental vehicles will be treated as government vehicles when being used for official business by military or DOD personnel. For base entry, driver identification will be checked and if all is in order, the vehicle may proceed in the same manner as a marked government vehicle.

3.5. AF Form 75, Visitor/Vehicle Pass. The AF Form 75 is one method to control and identify person-nel and vehicles on a temporary basis. It is issued to installation visitors who do not have the authorized credentials needed for unescorted or unchecked entry to the base. Installation commanders determine the use of AF Forms 75 on their installation and, if used, to what degree and to whom issued. Issue other access credentials when a pass is needed for longer than one year. Installation commanders determine if and how to retrieve passes once the visit is finished.

3.6. Handicapped Person Identification. Honor local and state-issued handicap decals, placards, signs, etc. on all Air Force installations. The installation commander may authorize issue of a locally devised card or form, which should contain an issue and expiration date. Issue and display per local procedure.

14 AFI31-204 14 JULY 2000

Chapter 4

TRAFFIC PLANNING AND CODES

4.1. Traffic Planning

4.1.1. Safe and efficient movement of traffic on an installation requires traffic supervision. A strong traffic supervision program includes sound traffic circulation planning, supervision, and control of motor vehicle traffic. Proactive publication and enforcement of traffic laws and regulations together with timely and professional investigation of motor vehicle accidents are also important. Finally, every successful program must include meaningful interaction, education, and communication with the general public.

4.1.2. Installation commanders develop traffic circulation plans that provide for the safest and most efficient use of primary and secondary roads. A major focus of installation traffic planning is circula-tion control. The base traffic engineer, CSP, safety officer, and other concerned staff agencies develop the traffic circulation plan. Consult with highway engineering representatives from adjacent civilian communities to ensure the installation plan is compatible with plans developed by the state and sur-rounding local communities. As a minimum, your base traffic plan should consider the following:

4.1.2.1. Normal and peak load routing based on traffic control studies.

4.1.2.2. Effective control of traffic, using planned traffic flow patterns which include measures for special events and adverse road conditions.

4.1.2.3. Point control at congested locations by law enforcement personnel or designated traffic directors or wardens, including trained school-crossing guards.

4.1.2.4. Use of traffic control signs and devices.

4.1.2.5. Efficient use of available parking facilities.

4.1.2.6. Efficient use of mass transportation.

4.1.2.7. Every installation commander should appoint a primary and alternate base traffic engi-neer. The engineer directs, develops, and staffs the base traffic circulation plan. This is normally a civil engineering responsibility and those considered for the position should have an infrastruc-ture planning and engineering background.

4.1.3. Traffic control studies provide factual data on existing roads, traffic density and flow patterns, and points of congestion. The CSP and traffic engineer usually conduct coordinated traffic control studies to obtain the data. Accurate data helps determine major and minor routes, locations for traffic control devices, and special conditions requiring engineering or enforcement services.

4.1.4. The Military Traffic Management Command Transportation Engineering Agency (MTMC- TEA) will help installation commanders solve complex highway traffic engineering problems. MTM- CTEA traffic engineering team services include:

4.1.4.1. Traffic studies of lifted areas and other special situations.

4.1.4.2. Complete studies of traffic operations of entire installations.

4.1.4.3. Assistance in complying with established traffic engineering standards.

AFI31-204 14 JULY 2000 15

4.1.5. Installation commanders submit requests for MTMCTEA assistance in accordance with AFR 75-88, Highways for National Defense.

4.2. Installation Traffic Codes.

4.2.1. Installation commanders must establish a traffic code for operation of motor vehicles on the installation. Commanders in overseas areas establish a traffic code to the extent military authority is empowered to regulate traffic under applicable treaties or agreements. Installation traffic codes must contain the base rules of the road and will, to the degree possible, conform to the code of the state or host nation in which the installation is located. The CSP is responsible for developing the traffic code and for ensuring it meets all local and legal requirements, this AFI, and the standards published in the following:

4.2.1.1. The National Highway Safety Program Standards, as published in 23, CFR 1230.

4.2.1.2. Applicable portions of the Uniform Vehicle Code and Model Traffic Ordinance published by the National Committee on Uniform Traffic Laws and Ordinances, which is contained in 23, CFR 1204.

4.2.1.3. DoDI 6055.4, DoD Traffic Safety Program.

4.2.2. The installation traffic code must contain policy and procedures for the towing, searching, impounding, and inventorying of vehicles. Publish these provisions and ensure they contain the fol-lowing:

4.2.2.1. Violations and conditions to tow or impound a vehicle.

4.2.2.2. Procedures to notify the vehicle owner.

4.2.2.3. Procedures for towing, storing, and protecting impounded vehicles.

4.2.2.4. Procedures for disposing of vehicles after lawful impoundment.

4.2.3. Where applicable, installation traffic codes must supplement the various basic provisions con-tained in the subparagraphs below:

4.2.3.1. Motorcycles and mopeds. Operators must comply with special requirements when driv-ing motorcycles, mopeds, or other open two-, three-, and four-wheel vehicles powered by a motor-cycle-type engine. See paragraph 4.2.6. for information concerning off-road vehicle use.

Installations should adopt local, state, or host nation guidance concerning the legal definition, operation, use, and control of mopeds, motorized bicycles, and other such devices on installation roadways. Such guidelines will be modified or restricted as necessary to ensure personal safety or the safe and orderly flow of installation traffic. Refer to AFI 91-207 for helmet, eye, and clothing safety requirements.

4.2.3.2. Restraint systems.

4.2.3.2.1. Operators and passengers of all vehicles operated on Air Force installations must wear restraint systems. In addition, operators and passengers of GOVs must wear restraint systems when driving or riding off the installation as well.

4.2.3.2.2. All Air Force active duty and reserve component members on active duty must wear restraint systems while driving or riding in a POV whether on or off the installation.

16 AFI31-204 14 JULY 2000

4.2.3.2.3. US Department of Transportation requires approved infant/child restraint devices in POVs for children 4 years old or under and not exceeding 50 pounds in weight.

4.2.3.2.4. Cars manufactured after model year 1966 require a manufacturer-approved restraint system meeting federal traffic safety standards.

4.2.3.2.5. Operators using vehicles equipped with air bags must still wear the manufacturer's primary restraint system (seat belts).

4.2.3.3. Headphones and earphones. The wearing of headphones and earphones is prohibited while driving a motor vehicle on base. This does not negate wearing of hearing protection when conditions and good judgment dictate its use such as when driving in noise hazard areas. This restriction does not apply to intercom systems worn by motorcycle operators and their passengers.

4.2.4. Take only administrative actions (reprimand, assessment of points, loss of installation driving privileges, etc.) for off-installation violations of the installation traffic code.

4.2.5. At bases with concurrent or exclusive federal jurisdiction, make violations of state traffic codes applicable to base driving records when those violations are included in that state’s criminal offense code. This provision is covered under the authority of Title 18 United States Code 13 (USC).

4.2.5.1. DoDD 5525.4, Enforcement of State Traffic Laws on DoD Installations, adopts the vehic-ular and pedestrian traffic laws of states where traffic law violations are not considered criminal offenses and cannot be assimilated under 18 USC. It makes these laws applicable to military installations having concurrent or exclusive federal jurisdiction. It also delegates authority to installation commanders to establish additional vehicular and pedestrian traffic rules and regula-tions for their installations. Those found guilty of violating traffic laws made applicable on instal-lations under provisions of DoDD 5525.4 are subject to a fine of not more than $50 or imprisonment for not more than 30 days or both for each violation. In those states where you can-not assimilate traffic laws, post an extracted copy of this paragraph and a copy of DoDD 5525.4 in a prominent place accessible to persons assigned, living, or working on the installation.

4.2.5.1.1. Take only administrative actions in states where you cannot assimilate violations of traffic laws under either Title 18 USC 13 or DoDD 5525.4. Generally, this applies to installa-tions under part or full proprietary jurisdiction.

4.2.6. Off-road vehicles usage: The installation commander or his or her designee determines if, when, and where off-road vehicles may be operated on base. In many areas, the operation of off-road vehicles is unregulated while other jurisdictions have strict requirements concerning age, safety train-ing, and vehicle equipment. Generally, some "on-street" safety practices such as reflective vests, gloves, headlight on, and goggles may not apply when operating off road in a recreational capacity.

However, ensure full compliance with local, state, or host nation requirements. When necessary, develop additional procedures and guidance locally and publish in the installation traffic safety plan or supplement to this instruction. Ensure environmental considerations are reviewed prior to designating any off-road vehicle use area.

4.3. Traffic Law Enforcement Principles.

4.3.1. Traffic law enforcement should motivate drivers to operate vehicles safely within traffic laws and regulations and maintain an effective and efficient flow of traffic. Effective enforcement should

AFI31-204 14 JULY 2000 17

emphasize selective enforcement and voluntary compliance by drivers. You can reach these goals by developing effective programs in the following areas.

4.3.1.1. Publishing a realistic traffic code well known by all personnel.

4.3.1.2. Adopting standard signs, markings, and signals in accordance with National Highway Safety Program Standards (NHSPS) and the Manual on Uniform Traffic Control Devices for Streets and Highways.

4.3.1.3. Ensuring enforcement personnel establish courteous, personal contact with drivers, and act promptly when driving behavior is improper or when observing a defective vehicle in opera-tion.

4.3.1.4. Maintain an aggressive program to detect and apprehend those who drive with suspended or revoked privileges.

4.3.1.5. Use sound discretion and judgment in deciding when to apprehend, issue a citation, or warn the offender.

4.3.2. Enforcement activities against intoxicated driving will include:

4.3.2.1. Detecting, apprehending, and testing persons suspected of driving under the influence of alcohol or drugs.

4.3.2.2. Training law enforcement personnel in special enforcement standards, detection tech-niques, and equipment standards unique to your location and jurisdiction.

4.3.2.3. Enforcing blood-alcohol concentration standards (see paragraph 4.11.).

4.3.2.4. Denying installation driving privileges to those whose use of alcohol or drugs prevents their safe operation of a motor vehicle.

4.4. Speed-measuring Devices. Use speed-measuring devices in traffic control studies and enforce-ment programs. Post signs to indicate the use of speed-measuring devices.

4.4.1. Equipment purchases. Installations located in states having a formal civilian police training and certification program for speed measurement should consider purchasing the same brand and model of equipment used by their civilian counterparts. Where possible, attend the same or similar certification courses used by local authorities.

4.4.2. Training and certification standards.

4.4.2.1. The CSP should strive to ensure operators of speed-measuring devices meet training and certification requirements prescribed by the state or jurisdiction where the installation is located.

Obtain specific information on course dates, costs, and prerequisites for attending by contacting the state agency responsible for police traffic radar training. Notwithstanding the above informa-tion, the CSP may establish other local training and certification programs for operators of speed-measuring devices. If exercising this option, you must ensure your qualification and train-ing standards are admissible as evidence and considered reliable by both military and civil author-ities. This requirement applies to courts-martial, nonjudicial proceedings, and civilian courts used to prosecute civilian offenders. Coordination between the military staff judge advocate and attor-ney general (or equivalent) is necessary.

18 AFI31-204 14 JULY 2000

4.4.2.2. Develop local training programs or attend a civilian institution or manufacturer's training program if security police are unable to attend local or state-sponsored radar certification courses.

4.4.2.3. The objective of civilian or manufacturer-sponsored courses is to improve the effective-ness of speed enforcement through the proper and efficient use of speed-measurement radar. On successful completion, the course graduate must know how to:

4.4.2.3.1. Describe the association between excessive speed and accidents, deaths, and inju-ries, and describe the traffic safety benefits of effective speed control.

4.4.2.3.2. Describe the basic principles of radar speed measurement.

4.4.2.3.3. Identify and describe Air Force speed measurement and speed enforcement policy and procedure.

4.4.2.3.4. Identify the specific radar instrument used and describe the instrument’s major com-ponents and functions.

4.4.2.3.5. Demonstrate basic skills in calibrating and operating the specific radar instru-ment(s).

4.4.2.3.6. Demonstrate basic skills in preparing and presenting records and courtroom testi-mony relating to radar speed measurement and enforcement.

4.4.3. Recertification. Certify operators every three years or more frequently when required by the state or governing jurisdiction. The CSP must document and maintain certification and training stan-dards in the unit training section. Forward records to gaining unit commanders when personnel PCS.

4.4.4. Use the following sources in local training and certification programs:

4.4.4.1. State or local training guides, plans, and procedures.

4.4.4.2. Publish techniques for radar speed detection and legal aspects of speed-measuring devices by the National Highway Traffic Safety Administration and the International Association of Directors of Law Enforcement Standards and Training.

4.5. Traffic Accident Investigation.

4.5.1. Conduct detailed investigations of the following:

4.5.1.1. All accidents involving a fatality or personal injury.

4.5.1.2. Vehicle and private property damage over the amount specified by the installation com-mander. This applies to government as well as private vehicles and property damage; however, the installation commander may establish different damage amounts for each category.

4.5.2. Conduct investigations of off-installation accidents involving military personnel according to local policy developed by the CSP and local police leaders.

NOTE: Generally, a detailed accident investigation includes, but is not limited to, an accident report form, field sketch, scale diagram, and accident narrative.

4.6. Traffic Accident Investigation Reports.

4.6.1. Anyone involved in an on-base vehicle accident must immediately report the incident to the security police. Report off-base accidents to the security police if they involve injuries to military per-

AFI31-204 14 JULY 2000 19

sonnel or damage to military property. The installation commander determines what agencies to notify and for what type of accidents to notify them. The CSP must develop a local notification matrix or other procedures that will ensure notification of appropriate base and civilian agencies. Develop and publish these notification procedures locally.

4.6.2. The security police will act as the focal point for gathering off-base accident information.

Record the information in the security police desk blotter. When possible, obtain copies of major accident reports prepared by investigating civilian police agencies.

4.6.3. Security police respond to all on-base major vehicle accidents (unless local conditions or poli-cies prohibit) to accomplish the following:

4.6.3.1. Render first aid and arrange for medical assistance.

4.6.3.2. Protect personal property.

4.6.3.3. Normalize traffic.

4.6.3.4. Identify witnesses and personnel involved.

4.6.3.5. Conduct a formal investigation.

4.6.3.6. The CSP determines (with installation commander approval) when and/or if minor vehi-cle accidents require investigation or a police response. He or she may delegate this authority to on-duty security police supervisory personnel. Develop policy in this area locally.

4.6.4. Report minor accidents not involving a security police response to the security police within 72 hours. Record accident information in the security police blotter. This information should include the accident type, time and date, location, name(s) of vehicle operator(s), unit (or address when civilian not affiliated with military), vehicle description, and license number(s). You should also include a brief summary of any damage and circumstances behind or causing the accident. A minor accident is any accident in which there are no fatalities/injuries or vehicle/property damage above the amount established by the installation commander. Consequently, a major accident is any accident involving a fatality, injury, or property damage above the amount established by the installation commander.

The installation commander may set differing amounts for government versus private vehicle and property damage.