BY ORDER OF THE SECRETARY AIR FORCE MANUAL 31-116

Transcription

BY ORDER OF THE SECRETARY
OF THE AIR FORCE
AIR FORCE MANUAL 31-116
9 MAY 2012
TINKER AIR FORCE BASE
Supplement
23 JANUARY 2014
Security
AIR FORCE MOTOR VEHICLE
TRAFFIC SUPERVISION
COMPLIANCE WITH THIS PUBLICATION IS MANDATORY
ACCESSIBILITY: Publications and forms are available for downloading or ordering on the ePublishing website at http://www.e-publishing.af.mil/
RELEASABILITY: There are no releasability restrictions on this publication
OPR: AFSFC/SFOP
Supersedes:
AFI 31-204, 14 July 2000
Certified by: AF/A7S
(Mr. John Fedrigo)
Pages: 35
(TINKERAFB)
OPR: 72 SFS/S5
Supersedes:
TINKERAFBI31-218,
8 Sept 2011
Certified by: 72 MSG/CC
(Col. Todd Vician)
Pages:34
This manual implements AFPD 31-1, Integrated Defense, sets forth AF guidance related to the
Interservice publication AFI 31-218 (I), Motor Vehicle Traffic Supervision, and provides
additional Air Force specific guidance. 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 limited to, granting,
suspending, or revoking the privilege to operate a privately owned vehicle (POV); registration of
POVs; administration of vehicle registration and driver performance records; driver
improvement programs; police traffic supervision; and off-installation traffic activities. This
instruction requires the collection and maintenance of information protected by the Privacy Act
of 1974 authorized by 50 United States Code 797. Refer recommended changes and questions
about this publication to the Office of Primary Responsibility (OPR) using AF Form 847,
Recommendation for Change of Publication; route AF Forms 847 from the field through the
appropriate functional’s chain of command. This publication may be supplemented at any level.
This publication requires the collection and or maintenance of information protected by the
Privacy Act of 1974 authorized by Title 10 United States Code, Section 8013, and DoD
2
AFMAN31-116_TINKERAFBSUP_I 23 JANUARY 2014
Directive 7730.47, Defense Incident-Based Reporting System (DIBRS). The applicable Privacy
Act SORN(s) F031 AF SF B, Security Forces Management Information Service, is available at
http://privacy.defense.gov/notices/usaf/. Records Disposition: Ensure that all records created
as a result of processes prescribed in this publication are maintained in accordance with AFMAN
33-363, Management of Records, and disposed of in accordance with the Air Force Records
Disposition Schedule (RDS) located at https://www.my.af.mil/afrims/afrims/rims.cfm.
(TINKERAFB) This manual implements AFPD 31-1, Integrated Defense, sets forth AF
guidance related to the Interservice publication AFI 31-218 (I), Motor Vehicle Traffic
Supervision, and provides additional Air Force specific guidance. 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
limited to, granting, suspending, or revoking the privilege to operate a privately owned vehicle
(POV); registration of POVs; administration of vehicle registration and driver performance
records; driver improvement programs; police traffic supervision; and off-installation traffic
activities. This instruction requires the collection and maintenance of information protected by
the Privacy Act of 1974 authorized by 50 United States Code 797. Refer recommended changes
and questions about this publication to the Office of Primary Responsibility (OPR) using AF
FORM 847, Recommendation for Change of Publication; route AF Forms 847 from the field
through the appropriate functional’s chain of command. This publication may be supplemented
at any level. This publication requires the collection and or maintenance of information protected
by the Privacy Act of 1974 authorized by Title 10 United States Code, Section 8013, and DoD
Directive 7730.47, Defense Incident-Based Reporting System (DIBRS). The applicable Privacy
Act SORN(s) F031 AF SF B, Security Forces Management Information Service, is available at
http://privacy.defense.gov/notices/usaf/. Records Disposition: Ensure that all records created
as a result of processes prescribed in this publication are maintained in accordance with AFMAN
33-363, Management of Records, and disposed of in accordance with the Air Force Records
Disposition Schedule (RDS) located at https://www.my.af.mil/afrims/afrims/rims.cfm.
SUMMARY OF CHANGES
This document is substantially revised and must be completely reviewed. This manual
incorporates extensive changes from AFI 31-204 which it replaces and must be thoroughly
reviewed by the reader. Among other things, this manual: incorporates current terminology and
standards related to testing for the presence of alcohol and drugs used by the National Highway
Traffic Safety Administration; describes the processes to be used in the collection of evidence
and action on traffic reports; includes guidance on matters ranging from registration of vehicles
to establishment of base traffic management programs; and sets minimum traffic enforcement
goals for Defense Force commanders
(TINKERAFB) This document is substantially revised and must be completely reviewed.
This manual incorporates extensive changes from AFI 31-218 and AFMAN 31-116 which it
supplements and must be thoroughly reviewed by the reader. Among other things, this manual:
incorporates current terminology and standards related to testing for the presence of alcohol and
drugs used by the National Highway Traffic Safety Administration; describes the processes to be
used in the collection of evidence and action on traffic reports; includes guidance on matters
3
ranging from registration of vehicles to establishment of base traffic management programs; and
sets minimum traffic enforcement goals for Defense Force commanders.
Chapter 1—INTRODUCTION
5
1.1.
Program Management. ...........................................................................................
5
1.2.
Responsibilities. .....................................................................................................
5
1.3.
Delegation of Authority. ........................................................................................
5
1.3.
(TINKERAFB) The authority of the Installation commander for the
administration of the base motor vehicle traffic supervision program is delegated
to 72 MSG/CD. ......................................................................................................
5
Chapter 2—DRIVING PRIVILEGES
6
2.1.
Requirements for Driving Privileges. ....................................................................
6
2.1.
(TINKERAFB) A valid state or international driver’s license satisfies driving
privilege requirements on Tinker AFB. .................................................................
6
2.2.
Stopping and Inspecting Personnel or Vehicles. ....................................................
6
2.3.
Implied Consent to Blood, Breath or Urine Tests. .................................................
6
2.4.
Implied Consent to Vehicle Impoundment. ...........................................................
6
2.5.
Suspension or Revocation of Driving Privileges. ..................................................
7
Table 2.1.
(Added-TINKERAFB) Condition/Action Taken ...................................................
8
2.6.
Alcohol and Drug Abuse Programs. ......................................................................
9
Chapter 3—PRIVATELY OWNED VEHICLE OPERATION REQUIREMENTS
10
3.1.
General. ..................................................................................................................
10
3.1.
(TINKERAFB) General. ........................................................................................
10
3.2.
Motorcycles, Motor Scooters and Mopeds. ...........................................................
10
3.3.
AF Form 75, Visitor/Vehicle Pass. ........................................................................
10
3.4.
Handicapped Person Identification. .......................................................................
10
3.5.
Vehicle Registration at non Air Force Installations. ..............................................
10
3.6.
Vehicle Registration at Air Force Installations. .....................................................
10
Chapter 4—TRAFFIC PLANNING AND CODES
11
4.1.
Installation Traffic Codes. .....................................................................................
11
4.2.
Traffic Accident Investigation. ..............................................................................
18
4.3.
Traffic Accident Investigation Reports. .................................................................
19
4.4.
Parking. ..................................................................................................................
20
4.5.
Off-installation Traffic Activities. .........................................................................
27
4
4.5.
(TINKERAFB) Damage to Government property or death/injuries to military or
government civilian personnel must be reported to Security Forces the next duty
day. .........................................................................................................................
27
4.6.
(Added-TINKERAFB) Use of Cellular Phones .....................................................
27
Table 4.1.
(Added-TINKERAFB) Unauthorized Cellular Phone Use/Action Taken Number
of Offenses Action .................................................................................................
28
Chapter 5—DRIVING RECORDS AND THE TRAFFIC POINT SYSTEM
29
5.1.
Driving Records. ....................................................................................................
29
Table 5.1.
Point Assessment for Moving Violations ..............................................................
29
Table 5.2.
Point Assessment for Non-Moving Violations. .....................................................
30
5.2.
Point System Procedures. .......................................................................................
30
5.3.
Disposition of Driving Records. ............................................................................
31
Chapter 6—IMPOUNDING PRIVATELY OWNED VEHICLES
32
6.1.
Standards for Impoundment. ..................................................................................
32
6.2.
Procedures for Impoundment. ................................................................................
32
6.3.
Disposition of Vehicles After Impoundment. ........................................................
32
Attachment 1—GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION
33
5
Chapter 1
INTRODUCTION
1.1. Program Management. This manual implements policy, assigns responsibility and
establishes procedures for motor vehicle traffic supervision on Air Force installations located in
the continental United States (CONUS), outside the continental United States (OCONUS), and
deployed locations, where implemented. This AFMAN provides additional Air Force specific
guidance to complement guidance found in AFI 31-218 (I). The objective of traffic control
programs is the safe and efficient flow of vehicles and pedestrians through reduction of factors
contributing to accidents.
1.2. Responsibilities. Installation Defense Force Commander (DFC). The DFC is the
Installation Commander's principal advisor on issues pertaining to the lawful movement of
personnel and traffic. The DFC exercises staff responsibility for directing, regulating and
controlling traffic, and enforcing installation rules pertaining to traffic control. DFCs assist
traffic engineers by performing traffic control studies to gather information on traffic problems
and use patterns.
1.3. Delegation of Authority. Installation commanders may delegate their responsibilities
under this manual to their vice commanders, mission support commanders or other group
commanders as appropriate and provided the individual does not occupy a position such as law
enforcement which would constitute a conflict of interest. Commanders should coordinate letters
of delegation through their SJAs.
1.3. (TINKERAFB)The authority of the Installation commander for the administration of
the base motor vehicle traffic supervision program is delegated to 72 MSG/CD. The 72
ABW/CC is the final approving authority for any and all amendments to this supplement.
6
Chapter 2
DRIVING PRIVILEGES
2.1. Requirements for Driving Privileges. Each Installation Commander will determine if
international driver’s licenses will be recognized and authorized for use on the installation. Take
into consideration the local (civilian) jurisdiction’s policy on recognition and acceptance of
international driver’s licenses. As a general rule, most CONUS civilian jurisdictions will honor
use of international driver’s licenses for short periods of time by non-resident visitors and
assigned military personnel and dependents. When practical, Installation Commanders should
incorporate local guidance to prevent conflicts and confusion.
2.1. (TINKERAFB)A valid state or international driver’s license satisfies driving privilege
requirements on Tinker AFB. Validity includes any state or federal extensions permissible.
2.2. Stopping and Inspecting Personnel or Vehicles.
2.2.1. AFI 31-101, Integrated Defense, and AFI 10-245, Antiterrorism, require Installation
Commanders to develop instructions and guidance that detail stop, inspection, search and
impoundment of motor vehicles at CONUS installation entry gates, to include Air Force
restricted and controlled areas.
2.2.2. MAJCOMs responsible for overseas military installations must provide their
Installation Commanders 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 combatant commander or those commanding unified forces
may direct guidance 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. This requirement must be outlined as
part of installation newcomers briefings and/or inprocessing of newly assigned personnel. Refer
to AFI 31-218 (I) for specific information.
2.4. Implied Consent to Vehicle Impoundment. In addition to those conditions for
impoundment listed in AFI 31-218(I), paragraph 2-3, local situations may arise that require
impoundment. The determination will be made by the Installation Commander or designee.
Installation and unit commanders must view the abandonment of personal property as a
personnel management issue and be diligent in deterring occurrences. Commanders must include
the consequences when personal property is abandoned during familiarization and indoctrination
training into units. Additionally, measures must be established to ensure personal effects are
cleared prior to personnel departing on permanent change-of-station orders.
2.4.1. (Added-TINKERAFB) Any vehicle on Tinker AFB which displays obvious
disrepair, mechanical defects, expired state registration or is parked for more than 3 days on a
public street, roadway or public parking area without being moved will have a DD Form
2504, Abandoned Vehicle Notice, placed on it. The 72d Security Forces Squadron will
attempt to notify the registered owner, owner’s unit or civilian supervisor after placement of
the notice. The vehicle will be considered abandoned 72 hours after the placement of the
notice and the vehicle will be towed at the owner’s expense if contact cannot be made.
7
2.4.2. (Added-TINKERAFB) In addition to the stated reasons for implied consent to
vehicle impoundment in AFI 31-218, the following violations are considered a threat to
public safety or convenience and may warrant the towing or impounding of a vehicle.
Reasonable efforts will be made to have the owner or other designated person move the
vehicle prior to impoundment. All vehicles impounded on Tinker AFB will be stored at the
impounding agency’s lot and the owner will pay all applicable charges and fees. Impounding
rates and fees will be charged in accordance with the Oklahoma Department of Public Safety
publication Oklahoma Agencies & Commissions (OAC) 595:25. EXCEPTION: Vehicles
seized by 72 SFS, Investigations Section, or other agency authorized by the Chief of Security
Forces (CSF), or which are involved in a crime will be stored in the 72 SFS impound lot.
2.4.2.1. (Added-TINKERAFB) Driving Under Suspension.
2.4.2.2. (Added-TINKERAFB) Driving Under Revocation.
2.4.2.3. (Added-TINKERAFB) Operating a vehicle without physical proof of
insurance verification form in the vehicle (OK Title 47 Ch 7-606).
2.4.2.4. (Added-TINKERAFB) Driving Under the Influence.
2.4.2.5. (Added-TINKERAFB) Mission necessity.
2.4.2.6. (Added-TINKERAFB) Accident where the vehicle is inoperable or the owner
refuses to have it moved.
2.4.2.7. (Added-TINKERAFB) Suspicious vehicles or vehicles presenting a force
protection concern when the owner cannot be contacted.
2.4.3. (Added-TINKERAFB) Repossessing POVs. Any person, company or business
requesting to repossess a vehicle on Tinker AFB will be directed to 72 SFS/S2I. The
requester will furnish legal documents to the 72 SFS for examination. If the agency or
person does not have a court order to repossess the vehicle, the requester will be informed
that repossession will only take place with the mutual consent of the registered owner of the
vehicle. If the registered owner refuses to release the vehicle, the requester will be directed
to leave Tinker AFB until a court order to repossess the vehicle is obtained.
2.4.4. (Added-TINKERAFB) Expired State Registration Tags/License Plates. There is no
grace period for expired vehicle registration tags (state license plates) on Tinker AFB, if the
vehicle state registration tag is more than 90 days the vehicle may be impounded.
EXCEPTION: Personnel returning from deployed status (not more than 2 weeks after
return).
2.5. Suspension or Revocation of Driving Privileges. Installation Commanders must
incorporate procedures governing suspension and revocation in base publications or as a
supplement to this instruction. Make these known to the base population. AF will follow the
administrative due process for suspensions detailed in AFI 31-218(I).
2.5.1. Suspensions.
2.5.1.1. Installation Commanders determine suspension and revocation guidance for nonmoving violations, as well as what constitutes a non-moving violation on their
installation (i.e., performing unauthorized repair; failure to register and insure vehicles;
unauthorized modifications or alterations; failure to maintain safety standards, etc).
8
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. Persons under the age of 21, when in the United States or where legal alcohol
consumption age is 21, operating a motor vehicle with a BAC or BrAC level standard of
.01 or higher is reason for automatic suspension. Refer to AFI 31-218(I) 24.a.(3).(a).(b).(c).(d). for additional guidance.
2.5.1.3. The .08 blood alcohol limit for presumptive intoxication determination may be
reduced to reflect a more stringent local, state or host nation standard.
2.5.1.3. (TINKERAFB) In addition to law enforcement actions taken, additional
administrative action may be taken against persons suspected of operating a motor
vehicle after consuming alcohol. Refer to Table 2 for additional guidance.
Table 2.1. (Added-TINKERAFB) Condition/Action Taken
Condition
SFST – No impairment
SFST – Impairment noted (Without probable
cause to conduct chemical test)
Intoxilizer reports 0.0 – 0.049 BrAC
Intoxilizer reports 0.05 – 0.079 BrAC
Intoxilizer reports 0.08 - .149 BrAC
Intoxilizer reports .15 or higher BrAC
Under 21 years of age: Any traceable amount
Refusal to submit to complete tests to measure
blood, alcohol or drug content:
Action Taken
Follow home or residence
Notify 1st Sergeant or Commander
Give ride or have unit take control of member
First offense: 90-day suspension base driving
Second offense: 6-month suspension base
driving
Third offense: 1-year suspension base driving
First offense: 1-year suspension base driving
Second offense: 2-year suspension base
driving
2-year suspension base driving
6-month base driving suspension
2-year loss of driving privileges
2.5.1.4. (Added-TINKERAFB) Speeding in base housing will result in suspension of
on-base driving privileges of one day for every one mile per hour over the posted speed
limit the individual was cited for. The individual will be assessed points IAW AFI 31218, Air Force Motor Vehicle Traffic Supervision.
2.5.1.5. (Added-TINKERAFB) Subsequent speeding offenses in base housing areas
will result in suspension of on-base driving privileges of one day for every one mile over
the posted speed limit the individual was cited for exceeding the posted speed limit, plus
an additional 30 days. The individual will be assessed points IAW Chapter 5
2.5.1.6. (Added-TINKERAFB) Failure to produce proof of valid compulsory insurance
when requested will result in a 30-day suspension of base driving privileges.
2.5.1.6.1. (Added-TINKERAFB) Obtaining or presenting physical paper proof at a
later date or time does not constitute grounds for dismissal of the suspension.
9
2.5.1.6.2. (Added-TINKERAFB) Displaying a cellular phone app or web page
from any other type of electronic device can constitute proof of compulsory
insurance. Patrolman discretion will be used to determine the validity of such proof
of insurance.
2.5.1.7. (Added-TINKERAFB) Base driving privileges of personnel suspended six
months or less are automatically restored the day after the suspension ends.
2.5.1.8. (Added-TINKERAFB) Those persons whose driving privileges are revoked in
excess of six months must make a request for reinstatement to the 72 SFS/S5R, lesser
suspensions are reinstated automatically upon completion. This request must be made in
writing.
2.5.1.9. (Added-TINKERAFB) Personnel whose base driving privileges are suspended
or revoked may park their vehicles in the parking lot adjacent to the off-base portion of
Gott Gate and the northwest parking lot adjacent to the Defense Reutilization &
Marketing Office (DRMO) compound outside the fence. All other parking areas
controlled by Tinker AFB are off limits.
2.5.2. Revocation.
2.5.2.1. The Installation Commander will immediately revoke driving privileges for a
period of not less than 1 year when a serious incident involving a motor vehicle occurs
and the Installation Commander 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 DFC 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. Installation Commanders may impose multiple suspensions to run consecutively
or concurrently.
2.6. Alcohol and Drug Abuse Programs. After coordination with the SJA, unit commanders
will direct drug and/or alcohol testing within 24 hours of suspected alcohol related motor
vehicle/traffic incidents or misconduct, episodes of aberrant or bizarre behavior or where there is
reasonable suspicion of drug use and the member refuses to provide consent for testing.
Commanders are also encouraged to ensure Blood Alcohol Tests (BAT) are taken as soon after
the incident as possible to determine the level and intensity of alcohol involvement. For
additional information refer to AFI 31-218(I).
10
Chapter 3
PRIVATELY OWNED VEHICLE OPERATION REQUIREMENTS
3.1. General. The Installation Commander will identify requirements to operate a motor
vehicle on the installation.
3.1. (TINKERAFB)General. Requirements for Tinker AFB mirror Oklahoma DMV statutes.
The driver is required to have a valid International or State driver’s license from any state.
3.2. Motorcycles, Motor Scooters and Mopeds. See AFI 91-207, The US Air Force Traffic
Safety Program, for requirements to operate motorcycles, motor scooters and mopeds on AF
installations. Refer to AFI 91-207, para 4.6., for motorcycle training requirements.
3.3. AF Form 75, Visitor/Vehicle Pass. The Security Forces Management Information System
(SFMIS), the Defense Biometric Identification System (DBIDS) generated vehicle/visitor passes
or the AF Form 75 are methods to control and identify personnel and vehicles on a temporary
basis. Specific procedures can be found in AFI 31-201, Security Forces Standards and
Procedures, and AFI 31-113, Installation Perimeter Access Control, when implemented.
3.3.1. (Added-TINKERAFB) Rental vehicles used by military and DoD personnel do not
require an AF Form 75. The vehicle may proceed in the same manner as a marked
government vehicle after showing the proper identification for entry onto the installation.
3.3.2. (Added-TINKERAFB) The Defense Biometric Identification System (DBIDS)
computer registration program will be utilized to record and issue long term and short
term/temporary AF Form 75 Visitor Passes.
3.4. Handicapped Person Identification. Honor local and state-issued handicap decals,
placards, signs, etc, on all Air Force installations. Upon request from a medical practitioner,
Installation Commanders may authorize issue of a locally devised card or form in OCONUS or
deployed locations where decals are not issued. Locally devised decals will contain an issue and
expiration date and be issued and displayed per local procedures.
3.5. Vehicle Registration at non Air Force Installations. Personnel who live or work on a
DoD Installation or who often use the facilities therein, may be required to register and be issued
a DD Form 2220, Vehicle Decal, for their vehicles at those locations.
3.5.1. (Added-TINKERAFB) Tinker AFB no longer issues the DD FM 2220.
3.6. Vehicle Registration at Air Force Installations. Personnel who possess appropriate
credentials to access Air Force Installations do not require a DD Form 2220. Although AFI 31218(I) requires vehicle registration, the Air Force was granted a waiver from this requirement.
Air Force Installations who continue to utilize the DD Form 2220 will use AFI 31-218(I) for
guidance and include any specific requirements for their location in the local traffic plan. The
Air Force will no longer produce DD Form 2220.
11
Chapter 4
TRAFFIC PLANNING AND CODES
4.1. Installation Traffic Codes.
4.1.1. Restraint systems.
4.1.1.1. Require the use of child safety seats consistent with state, territory or host nation
laws. If there is no state, territory or host nation law, all children under 4 years of age
regardless of weight or less than 50 pounds regardless of age shall be properly secured in
an appropriate child restraint system. Children ages 4 through 7, weighing 50 pounds or
more and less than 4 feet 9 inches shall be properly secured in a booster seat or other
appropriate child restraint system. Children ages 8 and above and no less than 4 feet 9
inches in height will be properly secured in a vehicle seat belt or booster seat. The child
safety seat or booster seat will be certified by the manufacturer to meet all applicable
Federal performance standards or host nation requirements and will be installed in
accordance with the manufacturer’s instructions.
4.1.1.2. All drivers and passengers on Air Force installations will wear seat belts, or in
the case of infants, be properly restrained.
4.1.1.2. (TINKERAFB) Children at least 6 years of age who are taller than 4’ 9” may
choose either a child passenger restraint system or a seat belt, as outlined in 49 C.F.R.,
Section 571.213.
4.1.2. Radar Detection Devices. The use of radars or laser detection devices are prohibited
on Air Force Installations.
4.1.2. (TINKERAFB) Safety Belts. All military personnel and civilians operating motor
vehicles on Tinker AFB will wear safety belts. The vehicle operator is responsible for all
passengers to be restrained properly.
4.1.3. Off-road vehicle usage: Installation Commanders or their 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 training and vehicle equipment. Generally, some "on-street" safety practices such
as reflective vests, gloves, headlights 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.1.3. (TINKERAFB) Operators refusing to wear a safety belt after being advised that wear
is mandatory may be denied entry to the installation.
4.1.4. (Added-TINKERAFB) Use of Radar/Laser Detection Devices.
The use of
radar/laser detection devices to indicate the presence of speed recording instruments,
broadcast a jamming signal, or to transmit erroneous speeds, is prohibited. The item must be
unplugged from its power source at the device before entering the military installation.
12
4.1.5. (Added-TINKERAFB) Off-road vehicle usage: Installation commanders or their
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 training and vehicle equipment. Generally, some "onstreet" safety practices such as reflective vests, gloves, headlights 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 offroad vehicle use area.
4.1.5.1. (Added-TINKERAFB) Off-Road Vehicle Usage. Operation of off-road or nonstreet-legal vehicles is prohibited on Tinker AFB except for mission necessity (mobility,
training, exercises, etc) or in identified parking/roadways which may be gravel or similar
material.
4.1.6. (Added-TINKERAFB) Enforcement of the Traffic Code. The Chief, Security Forces
(CSF) is responsible for the enforcement of all traffic laws and regulations, including
applicable state and city laws on TAFB.
4.1.7. (Added-TINKERAFB) Traffic Tickets. Security Forces will issue DD Form 1408,
Armed Forces Traffic Ticket, to military members (active, guard or reserve) in violation of
this traffic code. All other personnel in proprietary jurisdiction on Tinker AFB will also be
cited using DD Form 1408. A DD Form 1805, Federal Violation Notice, will be issued to all
civilian or retired military, Guard and Reserve violators of this traffic code or any other
applicable traffic offenses in exclusive or concurrent jurisdiction.
4.1.7.1. (Added-TINKERAFB) Persons subject to the Uniform Code of Military
Justice (UCMJ) are subject to trial by court-martial, punishment under Article 15/UCMJ,
or other types of disciplinary or administrative action deemed necessary by the unit
commander for violations of the provisions of this instruction, other applicable
regulations, directives, or laws pertaining to traffic.
4.1.7.2. (Added-TINKERAFB) Persons not subject to the UCMJ can be cited in
accordance with this instruction or Oklahoma State Law and may be subject to trial
before a US Magistrate for violations of law pertaining to traffic.
4.1.7.3. (Added-TINKERAFB) Persons not subject to the UCMJ are subject to
administrative action by the installation commander, or designated representative, for
violations of this instruction.
4.1.7.4. (Added-TINKERAFB) For offenses not listed in this instruction, tickets may
be issued in accordance with Oklahoma State Law; a minimum of 3 points will be
assessed in the closest applicable category in Chapter 5.
4.1.8. (Added-TINKERAFB) Exceptions Authorized. The driver of an authorized
emergency vehicle, when responding to a dispatch or security forces vehicle in the pursuit of
a suspected violator of the law, may within reason and with due regard for the safety of all
persons, exercise the following privileges only when using authorized visual and audible
(except when parking or standing) signals:
13
4.1.8.1. (Added-TINKERAFB) Proceed past a red light stop signal or stop sign only
after utilizing all emergency lights and sirens and ensuring the intersection is clear of
traffic. Emergency vehicles must not assume they have the right of way.
4.1.8.2. (Added-TINKERAFB) Exceed the maximum speed limit by 10MPH, as long
as this does not endanger life or property and is limited to actual emergency responses
(potential life or death situations).
4.1.8.3. (Added-TINKERAFB) Disregard regulations governing direction of travel or
turning in specified directions as long as this does not endanger life or property.
4.1.8.4. (Added-TINKERAFB) Emergency equipped vehicles may be left running
unattended when emergency equipment is operating and needed to maintain power for
accessories.
4.1.8.5. (Added-TINKERAFB) Park or stand, irrespective of the provisions of this
traffic code, provided they do not create a traffic hazard and the parking is for official
reasons.
4.1.9. (Added-TINKERAFB) Obedience to Traffic Enforcement Officials or Those
Persons Designated. No person will willfully fail or refuse to comply with any lawful order
or direction of any traffic enforcement officials or persons directed by security forces to
control traffic.
4.1.10. (Added-TINKERAFB) Eluding an Enforcement Official. Any driver of a motor
vehicle who willfully fails or refuses to bring his/her vehicle to a stop or who otherwise is
perceived as fleeing or attempts to elude pursuing security forces vehicles will be
apprehended and charged with a violation of Article 92 of the UCMJ or Oklahoma Statue as
applicable. The signal given by the enforcement official may be by hand, voice, whistle,
emergency light, siren or any combination thereof.
4.1.11. (Added-TINKERAFB) Eluding Traffic Control Devices. It’s unlawful for any
person to drive through parking lots or other areas to elude specific traffic control devices to
include signs, stanchions, and persons controlling traffic.
4.1.12. (Added-TINKERAFB) Crossing Fire Hose. No vehicles will be driven over an
unprotected fire hose laid down on any roadway during an emergency response, unless
directed to cross by security forces or fire department personnel.
4.1.13. (Added-TINKERAFB) Driving in Prohibited Areas. Operators will not drive
vehicles in areas prohibited by this traffic code, or in areas specifically identified in this
section. The driver of a motor vehicle will not drive through an area that is posted, marked,
or barricaded by means of barriers, traffic cones, or signs.
4.1.14. (Added-TINKERAFB) Limitations on Backing. A driver will not back a vehicle
unless such a movement can be made safely. When backing government owned vehicles
(GOV) with limited vision to the rear, a spotter will be used. If no spotter is available, the
operator, prior to backing, will visually check the area in which the vehicle will be backed.
A GOV operator may sound the horn for a short duration for safety.
4.1.15. (Added-TINKERAFB) Quiet Zones. All motor vehicles, including automobiles,
trucks, motorcycles and carryalls are prohibited from being operated in and near on-base
residential areas in such manner as to create a disturbance of the peace.
14
4.1.15.1. (Added-TINKERAFB) Accelerating or braking a vehicle in such a manner as
to cause a loud or unusual noise is prohibited.
4.1.15.2. (Added-TINKERAFB) Sounding a horn is prohibited except brief usage
which does not cause a public disturbance, identify a road hazard, signal bicyclist to your
passing, avoid accidents or when backing a GOV.
4.1.15.3. (Added-TINKERAFB) The designated quiet hours for residential areas are
2200-0600.
4.1.16. (Added-TINKERAFB) Headlights usage and height requirements. Headlights will
be used 30 minutes prior to sunset until 30 minutes after sunrise, and when visibility is
reduced. Headlight height must be between a maximum of 54” and a minimum of 24” from
the ground.
4.1.16.1. (Added-TINKERAFB) Motorcycles will have headlights on whenever in
motion.
4.1.16.2. (Added-TINKERAFB) The use of tinted headlight covers is prohibited when
the use of headlights are required.
4.1.16.3. (Added-TINKERAFB) The use of parking lights, when a vehicle is in motion
during reduced visibility/hours of darkness will only be allowed while vehicles are
entering installation entry control points. When a vehicle is parked off the main traveled
portion of the roadway or a street where parking is not common or prohibited, the driver
will turn on parking lights or emergency flashers.
4.1.17. (Added-TINKERAFB) Speed Limits. No person will drive a vehicle at a speed
greater than the posted speed limit, or at a reduced speed which is reasonable and prudent
under existing weather, road, and traffic conditions with regard for actual and potential
hazards.
4.1.17.1. (Added-TINKERAFB) All personnel are required to observe the following
speed limits:
4.1.17.1.1. (Added-TINKERAFB) 25 MPH on all streets and roads, unless
otherwise posted.
4.1.17.1.2. (Added-TINKERAFB) 15 MPH when entering or exiting all installation
entry points.
4.1.17.1.3. (Added-TINKERAFB) 15 MPH in base housing.
4.1.17.1.4. (Added-TINKERAFB) On the airfield-loading ramp, the speed limit for
special purpose vehicles will be 10 MPH and 15 MPH for general-purpose vehicles.
4.1.17.1.5. (Added-TINKERAFB) 5 MPH in all parking lots, DLA disposal areas
and when passing within 50m of troop formations on a roadway, unless specifically
noted such as between Bldg 460 and Bldg 469, which is 10MPH. NOTE: Military
formations have the right-of-way at all times.
4.1.17.1.6. (Added-TINKERAFB) 5 MPH on Loading/building ramps and inside
buildings, where driving inside is allowed by signage or other markings.
15
4.1.18. (Added-TINKERAFB) Oversized Vehicles. Any tractor, trailer, vehicle or
combination thereof requiring an oversize/overweight load placard, exceeding 102 inches in
width, 25 feet in length or more with 2 or more axles and a separate compartmentalized cargo
area that cannot be visually assessed by looking into the cab, or large recreational vehicles
(RV) (i.e., self propelled or towed vehicle that is equipped to serve as temporary living
quarters for recreation, camping or travel purposes and is used solely as a family or personal
conveyance) must enter and exit the installation utilizing the Truck Gate (Gate 33) just east
of SE 59th Street and Air Depot Blvd. Should an RV enter the gate during base entry control
point checks, the RV will be inspected like any other motor vehicle.
4.1.19. (Added-TINKERAFB) Safe Operation of Motor Vehicles.
4.1.19.1. (Added-TINKERAFB) Operators of motor vehicles will not:
4.1.19.1.1. (Added-TINKERAFB) Park or drive over grass or seeded areas or
where there is no road, unless required for duty or performance of contract
work/repairs.
4.1.19.1.2. (Added-TINKERAFB) Pull or push motor driven cycles on traffic
ways.
4.1.19.1.3. (Added-TINKERAFB) Load or unload passengers in an area that will
interfere with the movement of vehicular or pedestrian traffic, except at bus and
school stops.
4.1.19.1.4. (Added-TINKERAFB) Operate vehicles equipped with catalytic
converters within 5 feet of any aircraft, fuel spill, POL area, explosive area or other
potentially hazardous area when identified or reported.
4.1.19.1.5. (Added-TINKERAFB) Fail to yield the right-of-way to pedestrians
crossing roadways within a crosswalk, from the opposite side of the roadway as to be
in danger. Pedestrians crossing a roadway provided for vehicular traffic at any point
other than within a marked crosswalk or an intersection will yield the right-of-way to
vehicles upon the roadway or traffic lane. Pedestrians are required to use a marked
crosswalk if provided.
4.1.19.1.6. (Added-TINKERAFB) Pass a bus that is stopped to load or unload
passengers on which the red loading signals are in operation.
4.1.19.1.7. (Added-TINKERAFB) Play, operate or permit the playing or operation
of any radio, musical instrument or other machine or device for the producing or
reproducing of sound which can be heard from a distance of 50 feet or more and the
source of such sound is located upon any public right-of-way.
4.1.19.1.8. (Added-TINKERAFB) Leave an inoperable vehicle on base and will be
responsible for the expeditious removal of their vehicles to an off base repair facility
or base automotive shop (if authorized such privileges) when they become
inoperative, damaged or unsafe. In no case will they be left unattended obstructing
the normal flow of vehicular or pedestrian traffic without immediately notifying the
72 SFS BDOC at 734-3737.
4.1.19.1.9. (Added-TINKERAFB) Carry loads unless the load is properly secured.
16
4.1.20. (Added-TINKERAFB) Motorcycles and Motor-Driven Cycles. For the purpose of
this instruction, motorcycles include any motor driven cycle with less than four wheels
touching ground with or without a side car. All motorcycle operators must attend an
approved motorcycle safety course IAW AFI 91-207 para 4.6. When operating a motorcycle
on Tinker AFB drivers must, at all times have in their possession a valid driver’s license with
motorcycle operator’s endorsement and the Motorcycle Safety Form (MSF). However, the
MSF alone is not recognized as a state license and does not fulfill this requirement.
4.1.20.1. (Added-TINKERAFB) No motor driven cycle will be operated or parked on
any grass, (seeded area), sidewalk, jogging path or on any area not designated for the
operation of motor vehicles. Gas or electric powered skateboards, go-carts, mini-bikes
and mini-scooters are not permitted to be operated on or off-road while on Tinker AFB.
4.1.20.2. (Added-TINKERAFB) No operator of a motor driven cycle will carry any
other person on or within such vehicles on Tinker AFB unless the motor driven cycle has
a wheel diameter of 12 inches or greater and has either a double seating device with
double foot rests or a sidecar attachment. The side car attachment must provide a
separate seat space for each person riding therein. In sidecars, the person must be seated
entirely within the body of the sidecar.
4.1.20.3. (Added-TINKERAFB) Personal protective equipment (PPE) required while
operating a motorcycle on Tinker AFB is:
4.1.20.3.1. (Added-TINKERAFB) Head Protection. A helmet designed to meet or
exceed Department of Transportation (DOT) standards, shall be worn and properly
fastened under the chin.
4.1.20.3.2. (Added-TINKERAFB) Eye Protection. Goggles, wrap around glasses,
or a full-face shield (properly attached to helmet) and closed if applicable, designed to
meet or exceed American National Standards Institute (ANSI) Standard Z87.1 for
impact and shatter resistance will be worn. A motorcycle attached windshield does
not constitute proper eye protection regardless of height.
4.1.20.3.3. (Added-TINKERAFB) Protective Clothing. Wear of long sleeved shirt
or jacket, long trousers and full-fingered gloves are required. Gloves should be
sturdy, non-slip type to permit a firm grip on the controls. Wear of a motorcycle
jacket and pants constructed of abrasion resistant materials such as leather, Kevlar®,
and/or Cordurao® containing impact absorbing padding are strongly encouraged.
4.1.20.3.4. (Added-TINKERAFB) Foot Protection. Riders will wear sturdy over
the ankle footwear that affords protection for the feet and ankles (durable athletic
shoes that cover the ankles may be worn). Sandals, low quarter sneakers and similar
footwear will not be used.
4.1.20.3.5. (Added-TINKERAFB) Garment and Motorcycle Visibility. Motorcycle
riders will wear a brightly colored by day and reflective by night outer upper garment.
During hours of darkness/reduced visibility a reflective upper garment will be worn.
Reflective belts (as worn on the flight line) do not constitute an upper ―garment‖.
The outer upper garment shall be visible and not covered. Wearing of a backpack is
authorized if it conforms to colored/reflective properties stated above.
17
4.1.21. (Added-TINKERAFB) Carryall/Segway Operation. All organizations will submit
to 72 LRS a list of all owner/user carryalls, their serial numbers and the name of the
individual in charge of the carryall along with their routing symbol. Carryalls are defined as
mules, gators, Cushman, golf carts and any motorized vehicle that is not required to display
federal or state vehicle registration plate. The base transportation section will issue a
registration number to each carryall vehicle and compile the numbers to a mass listing. The
numbering on the list will be the responsibility of 72 LRS/LRDVQ. The list, once compiled,
will be issued to each organization. A copy will be given to 72 ABW/SE, one to the 72 SFS
and one will be maintained by 72 LRS/LRDVQ.
4.1.21.1. (Added-TINKERAFB) Each owner/user organization will be responsible for
procuring and attaching to each carryall two standard size license plates (white
background with blue lettering), one in front and one in the rear of the carryall vehicle.
The size of the lettering will be the same as the current USAF vehicle plates.
4.1.21.2. (Added-TINKERAFB) Owner/user organizations purchasing new carryall
vehicles will revise their inventory list and send the list through 72 LRS who issues a
number and sends the revised list to 72 ABW/SE, 72 SFS and 72 LRS will maintain one.
4.1.21.3. (Added-TINKERAFB) All organizations that purchase new carryall vehicles
and/or have vehicles that are currently operated on the roads shall ensure that the vehicle
conforms to the current Title 47 of the Oklahoma Motor Vehicle Highway Safety Code.
4.1.21.4. (Added-TINKERAFB) All organizations will write an operating instruction
detailing the care, maintenance and operation of the carryall vehicles using the 72 CEG
Operating Instruction for Low Speed Vehicles.
4.1.21.5. (Added-TINKERAFB) Carryalls must be equipped with headlights, red tail
lamps, turn signals (red or amber), red brake lights, two separate means of applying
brakes (foot pedal and emergency) horn, mirrors with a view to the rear of at least 200 ft,
windshield and wipers, seat belts and a white rear light to illuminate rear registration
plate.
4.1.21.6. (Added-TINKERAFB) Privately owned Segways, those issued by a
Department of Defense office or an associated contractor are permitted on TAFB.
4.1.21.7. (Added-TINKERAFB) Segways should be operated on sidewalks or jogging
trails whenever available. Where not available, segways may be operated on roadways.
While on roadways, operators should stay as far right within the traffic lane as safely
possible. Segways are not authorized for use on flight lines, office areas or hallways.
Exception: During special events, (i.e. air show, open house, etc.) use of segways on the
airfield may be granted by the wing commander. If operated during hours of darkness,
segways must be equipped with headlights, red tail lamps, turn signals (red or amber), red
brake lights, and mirrors with a view to the rear of at least 200 ft. Segways are designed
for a single rider and may not transport passengers.
4.1.21.8. (Added-TINKERAFB) Segway operators shall wear an ANSI, SNELL or
DOT approved whole-head helmet with chin strap fastened while operating the vehicle
regardless of operation location. Stickers will not be affixed to helmets. Wear of music
headphones and use of cellular phones while operating a Segway is prohibited.
18
Appropriate safety equipment (e.g. knee and elbow pads) is highly recommended.
Additionally, operators must wear visible clothing as outlined in 7.3.5 above.
4.1.21.9. (Added-TINKERAFB) Segways will be operated in a controlled, responsible
and courteous fashion. Segway training sessions shall only be conducted by those
individuals who have attended the eight hour Segway training course. Only personnel
completing training can issue an AF Form 483. Government owned Segway operators
will maintain the AF FM 483 in their possession while in operation to be produced on
request.
4.1.22. (Added-TINKERAFB) Use of Roller Skates/Rollerblades and Skateboards.
Rollerblading and skate boarding is not authorized on streets, roadways, parking lots, or in
areas immediately around buildings or in stairways. Permitted areas include sidewalks and
base sponsored skate boarding activity areas. Helmets are required and appropriate safety
equipment (knee/wrist pads, etc.) is highly recommended.
4.1.23. (Added-TINKERAFB) Drivers License Extensions.
4.1.23.1. (Added-TINKERAFB) Automatic extensions for active duty military
personnel:
4.1.23.1.1. (Added-TINKERAFB) Alaska, Arizona, California, Colorado, Florida,
Georgia, Illinois, Indiana, Iowa, Louisiana, Maine, Maryland, Massachusetts,
Michigan, Minnesota, Mississippi, Montana, Nebraska, New Jersey, New Mexico,
New York, North Dakota, Ohio, Oklahoma, Pennsylvania, South Carolina, South
Dakota, Tennessee, Texas, Utah, Vermont, Virginia, Washington, West Virginia,
Wisconsin and Wyoming. NOTE: Some states require an extension card be carried
on your person, check with your state.
4.1.23.2. (Added-TINKERAFB) Any state not listed above does not have an automatic
extension.
4.1.23.3. (Added-TINKERAFB) Automatic extensions for dependent spouses/children
of active duty military personnel:
4.1.23.3.1. (Added-TINKERAFB) Florida, Illinois, Iowa, Maryland, Minnesota,
Nebraska, New Mexico, Ohio, Oklahoma, Pennsylvania, South Carolina, Virginia
and Washington.
4.1.23.4. (Added-TINKERAFB) There are no extensions for any civilian/contractor
personnel.
4.2. Traffic Accident Investigation.
4.2.1. A major traffic accident is any accident involving a fatality, injury or property damage
above the amount established by Installation Commanders. Installation Commanders may set
differing amounts for government versus private vehicle and property damage. Monetary
damage amounts for major accidents are typically $10,000. The investigation of major
accidents should be accomplished by a trained accident investigator. MAJCOMs will
determine the level of training required.
19
4.2.2. Generally, a detailed accident investigation includes, but is not limited to, an AF Form
1315, Accident Report, field sketch, scale diagram (if death or serious bodily harm), and
accident narrative.
4.2.3. (Added-TINKERAFB) All motor vehicle accidents will be reported to the 72 SFS
BDOC, 734-3737 within 24 hours. Failure to report an accident subjects one or both parties
to a possible citation. For the purpose of accident investigations by Security Forces on Tinker
AFB, motor vehicle equipment designated primarily for off-road operations (special purpose
vehicles) will be classified as ground equipment and accidents will be reported as industrial
accidents if they occur off the highway. Industrial accidents will not be recorded on an AF
Form 1315, Accident Report. Accidents involving ground equipment that occur on highways
are traffic accidents and will be recorded on an AF Form 1315. The 72 ABW/SE will be
notified of accidents involving government property or personal injury on Tinker AFB.
4.2.4. (Added-TINKERAFB) A major accident is defined as an accident involving injury,
fatality and/or property damage of $10,000 or more. A Security Forces Accident Investigator
will respond to the scene of the accident and conduct an investigation. A copy of the
Oklahoma Operators Collision and Financial Responsibility Report will be issued to drivers
involved in accidents to comply with Oklahoma law. Security Forces will ensure that all
pertinent information is exchanged between drivers.
4.2.5. (Added-TINKERAFB) All minor accidents involving any vehicles on base will be
reported to the 72 SFS BDOC, at 743-3737, as soon as possible, but no later than 24 hours
after the accident. Fault will not be determined or tickets issued by 72 SFS personnel in
minor accidents. Responding Security Forces personnel will complete AFMC Form 625,
Minor Traffic Accident Work Sheets, for all minor vehicle accidents. An exchange of
information between the parties involved will occur in accordance with Oklahoma law at the
time of the accident.
4.2.6. (Added-TINKERAFB) All accident reports will contain seatbelt use and airbag
deployment.
4.3. Traffic Accident Investigation Reports.
4.3.1. Military members report information to Security Forces if they are on/off base
resulting in accidents involving injuries or damage to military property. Local guidance will
capture procedures to accomplish these notifications and the timeframes to report.
Installation Commanders determine what agencies to notify and for what type of accidents to
notify them. The DFC must develop a local notification matrix or other procedures to ensure
proper notification of appropriate base and civilian agencies are conducted. Develop and
publish these notification procedures locally.
4.3.1. (TINKERAFB) Military members and government civilians must report information
to Security Forces if they are on/off base resulting in accidents involving injuries or damage
to military property not later than the next duty day.
4.3.2. Security Forces will act as the focal point for gathering off-base accident information
of military affiliated personnel. Record the information in the Security Forces blotter, along
with the associated case number from the investigating police agency. When possible,
Security Forces Reports and Analysis (S5R) will obtain copies of major accident reports
20
prepared by investigating civilian police agencies to accompany off-base accident reporting
information.
4.3.3. Security Forces respond to all on-base major vehicle accidents (unless local conditions
or policies prohibit) to accomplish the following:
4.3.3.1. Render first aid and arrange for medical assistance.
4.3.3.2. Protect personal property.
4.3.3.3. Normalize traffic.
4.3.3.4. Identify witnesses and personnel involved.
4.3.3.5. Conduct a formal investigation.
4.3.3.6. The DFC (with Installation Commander approval) will develop local response
and investigative procedures for various types of accidents to include minor vehicle
accidents. S/He may delegate this authority to on-duty Security Forces supervisory
personnel.
4.3.4. Record accident information in the Security Forces 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)/plate. Also, include a brief summary of any damage and circumstances behind or
causing the accident, as well as any traffic citations issued.
4.3.5. Investigation conducted by Security Forces and/or AFOSI of any traffic accident will
take precedence over any other types of investigations relating to the accident. This
precludes the loss of any potential evidence that may later have to be introduced in any
criminal/judicial proceedings. (Example: Any safety related investigation and/or any other
investigation that may hamper accident investigation practices by Security Forces and/or
AFOSI.)
4.4. Parking.
4.4.1. Reserved Parking. When not addressed by MAJCOMs, Installation Commanders
determine reserved parking guidance for their installations. Number of available spaces,
facility design and layout, traffic flow and number of vehicles using facilities will help
determine the number and location of reserved parking spaces. Make guidance and
procedures governing reserved parking a part of the installation supplement to this
instruction, separate traffic control instruction or installation-parking plan. The publication
must address approval, issue, control and review of reserved parking and should give special
consideration to bicycle, motorcycle, visitor and car pool parking. Consideration should also
be given to labor and management contracts when designating parking. Handicap parking is
regulated under the Uniform Federal Accessibility Standards and applies to all Air Force
installations.
4.4.2. Use distinctive emblems, decals, stickers, etc, to control parking space assignments
and to indicate authorized use of the parking slot. MAJCOMs (or Installation Commanders if
not addressed by the MAJCOM) may develop guidance concerning the issue and control of
the identification media discussed above. Designation of parking spaces by name, grade, rank
or title should be avoided due to force protection concerns.
21
4.4.2.1. (Added-TINKERAFB) The 72 ABW Traffic Safety Working Group (TSWG)
is responsible for reviewing safety issues concerning mass parking plans and reserved
parking spaces. The OPR for the TSWG is 72 ABW/SE and is chaired by the 72
MSG/CD.
4.4.2.2. (Added-TINKERAFB) For reserved parking spaces on Staff Drive, Bldg 3001,
coordination must be initially routed through AFSC/DSH then to the TSWG for approval
before any changes can be made.
4.4.2.3. (Added-TINKERAFB) For reserved parking spaces in other areas on Tinker
AFB, coordination with the 72 ABW/CE must be approved before any changes can be
made. The requesting organization must generate an AF Form 332 stating the requested
changes. The AF Form 332s will be reviewed by 72 ABW/CE for approval/disapproval.
72 ABW/CE will limit reserved parking spaces to no more than 10% of available parking
spaces (does not include handicap parking).
4.4.2.4. (Added-TINKERAFB) Community Activity Centers (i.e. Commissary,
AAFES, etc.) if used will be proportionately distributed and designated by title:
4.4.2.4.1. (Added-TINKERAFB) General
4.4.2.4.2. (Added-TINKERAFB) O-6
4.4.2.4.3. (Added-TINKERAFB) CMSgt
4.4.2.4.4. (Added-TINKERAFB) Maternity
4.4.2.4.5. (Added-TINKERAFB) Parents with Small Children
4.4.2.4.6. (Added-TINKERAFB) Honor Guard
4.4.2.4.7. (Added-TINKERAFB) Team Tinker Award Winner
4.4.2.5. (Added-TINKERAFB) Quarterly and Annual Base Award Winners will
receive a parking decal to be placed on their dashboard, when parking in the Team Tinker
Award Winner parking spot at the Exchange or Commissary. The decal must be
prominently displayed at all times when parked in the reserved spot.
4.4.2.6. (Added-TINKERAFB) Sign Manufacturing. 72 ABW/CE is approval authority
for procuring reserved parking signs and will procure all reserved parking signs to ensure
uniformity unless CE expressly approves off-base procurement through local
manufacturers due to workload or time constraints. Either method requires strict
adherence to CE standards.
4.4.2.7. (Added-TINKERAFB) Units must fill out an AF Form 332 and forward to 72
CE.
4.4.2.8. (Added-TINKERAFB) Tinker units will review reserved parking for
compliance with this instruction on the first day of the fiscal year. All signs not in
compliance will be immediately removed by owner/user.
4.4.2.9. (Added-TINKERAFB) Organizations will designate reserved parking by
numerical digits or by unit designator and office symbol or approved posted signs. All
organizations may designate reserved parking spots for personnel assigned to or who
frequent their facility and will include:
22
4.4.2.9.1. (Added-TINKERAFB) General/Senior Executive Service.
4.4.2.9.2. (Added-TINKERAFB) Wing Commander/Vice Commander.
4.4.2.9.3. (Added-TINKERAFB) Group Commander/Deputy Commander.
4.4.2.9.4. (Added-TINKERAFB) Colonel or civilian equivalent.
4.4.2.9.5. (Added-TINKERAFB) Squadron Commander.
4.4.2.9.6. (Added-TINKERAFB) Command CMSgt/Senior Enlisted Manager.
4.4.2.9.7. (Added-TINKERAFB) First Sergeant.
4.4.2.9.8. (Added-TINKERAFB) Government Vehicle.
4.4.2.9.9. (Added-TINKERAFB) Handicap Parking.
4.4.2.9.10. (Added-TINKERAFB) Customer Service (1 hour).
4.4.2.9.11. (Added-TINKERAFB) Car Pool.
4.4.2.9.12. (Added-TINKERAFB) Motorcycle and Loading Zone.
4.4.3. Installations may create a parking wardens program to monitor and cite parking
violators at their facilities.
4.4.3.1. If utilized, installations will develop a local publication to
supplement/implement this instruction addressing the parking warden program. The
supplement will include a requirement for individual unit commanders to delegate a
minimum of one primary and alternate at the grade of E-5 or above, in writing. All
monitors will issue parking tickets on the DD Form 1408, Armed Forces Traffic Ticket.
S5R will obtain a letter with the current monitors and maintain the letter on file.
4.4.3.2. Monitors will be trained by the Security Forces unit on the correct procedures to
complete tickets, including the routing process of issued tickets to S5R. The main
difference between a DD Form 1408 issued by a Security Forces member and one by a
parking monitor is the special instructions on the back of the pink copy that directs the
violator to contact the monitor within 24 hours or next duty day who issued the ticket
instead of Security Forces. Monitors will provide contact information on parking tickets
to enable violators to provide information necessary to complete the citation.
4.4.3.3. (Added-TINKERAFB) Monitors will be trained by the Security Forces unit on
the correct procedures to complete tickets, including the routing process of issued tickets
to S5R. The main difference between a DD Form 1408 issued by a Security Forces
member and one by a parking monitor is the special instructions on the back of the pink
copy that directs the violator to contact the monitor within 24 hours or next duty day who
issued the ticket instead of Security Forces. Monitors will provide contact information on
parking tickets to enable violators to provide information necessary to complete the
ticket. Tickets must be forwarded to 72 SFS/S5R within 72 hours of issue. 72 MSG/CD
reserves the right to remove a parking warden if the individual fails to adequately
perform those duties.
4.4.4. (Added-TINKERAFB) 72 SFS will move or cause to be moved a parked vehicle
when the vehicle:
23
4.4.4.1. (Added-TINKERAFB) Creates a safety or fire hazard.
4.4.4.2. (Added-TINKERAFB) Appears abandoned.
4.4.4.3. (Added-TINKERAFB) Remains parked on a road or the shoulder of the road
for more than 12 hours.
4.4.4.4. (Added-TINKERAFB) Obstructs traffic flow.
4.4.4.5. (Added-TINKERAFB) Is parked on a seeded area.
4.4.4.6. (Added-TINKERAFB) Is blocking an aircraft hangar door or aircraft
movement area.
4.4.4.7. (Added-TINKERAFB) Is being repaired in an unauthorized area.
4.4.4.8. (Added-TINKERAFB) Vehicles parked near aircraft runway take-off and
landing glide paths will be moved immediately.
4.4.5. (Added-TINKERAFB) Parking spaces are designated by white stripes. Areas not
marked specifically for parking are considered no parking. Parking on the grass is
prohibited, unless otherwise posted. Parking in a reserved parking space by any person
whose vehicle does not bear the appropriate parking decal/placard is prohibited.
4.4.5.1. (Added-TINKERAFB) Spaces with a series of narrow white lines at the ends
of parking rows such as present at Bldg 3001, Bldg 820 and others are designated
turning-radius buffers for larger vehicles and are not motorcycle parking spaces marked
by ground paint or elevated signage.
4.4.5.2. (Added-TINKERAFB) Management of Parking Areas. The 72 ABW/CE is
responsible for assigning and authorizing the marking of specific parking areas and
spaces. The establishment of parking areas/spaces will be coordinated with the 72
ABW/CE. Any changes beyond 10 per month in a parking area will be negotiated with
the union.
4.4.5.3. (Added-TINKERAFB) 72 ABW/CE will coordinate with 72 SFS and 72
ABW/SE on construction projects affecting traffic flow and vehicle parking.
4.4.5.4. (Added-TINKERAFB) Handicap parking permits are issued by the respective
state, not Tinker AFB. All requests for handicap parking permits will be made through
the State. Tinker AFB will honor valid handicap parking permits and decals regardless of
the state of issue. The handicap permit must be registered to the person using it. Vehicles
displaying a handicap-parking permit may park in any space designated as such unless
otherwise restricted. A handicap placard does not entitle the user to park in other
reserved spaces such as carpool or reserved, even if all available handicap spaces have
been filled.
4.4.5.5. (Added-TINKERAFB) Government Vehicle Parking. Government vehicles
may be parked in spaces designated for government vehicles or customer service
provided that the size of the parking space will accommodate the vehicle. Time limits
must be observed when using time limit spaces. Temporary parking for government
vehicles may be authorized when mission requirements dictate (to load or unload material
or equipment). Such parking will not be abused.
24
4.4.5.6. (Added-TINKERAFB) Properly marked emergency vehicle parking is
authorized anywhere on Tinker AFB while performing official duties.
4.4.5.7. (Added-TINKERAFB) Contractor Parking. Contractors and construction
management engineers will be permitted on-the-job-site parking for their working
equipment and trucks. Contractor personnel will use authorized unrestricted parking areas
where conditions permit. On sites where use of established parking areas is impractical,
worker parking will be coordinated with 72 SFS and union representatives.
4.4.5.8. (Added-TINKERAFB) Contractor Loading/Unloading Parking Zones.
Designated contractor loading or unloading zones shall not be utilized for (in lieu of)
contractor parking. Usage of loading/unloading zones shall not exceed 2 hours unless
specific authorization is provided. Tinker AFB employees or contractors that fraudulently
utilize these areas for general purpose parking shall be subject to ticketing and towing.
4.4.5.9. (Added-TINKERAFB) Motorcycle/Scooter/Segway
Parking.
All
are
authorized to park in normal parking spaces when motorcycle-only spaces are full or nonexistent. Normally, these parking areas will be assigned in spaces that will not
accommodate larger vehicles. Motorcycles and scooters will not be parked in a
designated bicycle parking area.
4.4.5.10. (Added-TINKERAFB) Deployment/TDY Parking. Each unit is responsible
for identifying a Deployment/TDY parking location for their personnel. 72 SFS will
provide a temporary fall back or over flow parking location in the parking lot West of
Bldg 591 in the event a unit’s primary location is full. Units must notify 72 SFS of their
designated location and a POC within the unit for their parking area to avoid impound.
Overflow parking areas are NOT convenience storage. If investigation reveals the
vehicles’ owner is not deployed/TDY, impound procedures will be initiated. Overflow
parking is limited to one motor vehicle, boats travel trailers and RVs must be stored in
the base RV storage or off base.
4.4.5.11. (Added-TINKERAFB) Organizations may designate special temporary
restricted parking spaces for such purposes as VIPs, IG teams, associate commander’s
meetings and other special needs as required.
4.4.5.12. (Added-TINKERAFB) Handicap and government vehicle spaces are reserved
24 hours a day, 7 days a week. Open parking is allowed in carpool and vendor spaces
between the hours of 1630 to 0600 and on weekends and holidays.
4.4.5.13. (Added-TINKERAFB) Vehicles displaying First Sergeant decals may park in
customer and carpool spaces. First Sergeant decals will be issued only to active duty First
Sergeants assigned to any unit at Tinker AFB.
4.4.5.14. (Added-TINKERAFB) Vehicles displaying General and SES decals may
park in any space except those designated as handicap.
4.4.5.15. (Added-TINKERAFB) Parking decals will be displayed in the upper middle
or lower left corner of the vehicles windshield.
4.4.5.16. (Added-TINKERAFB) Carpool Parking Permits. Carpool permits will be
issued to one participant of each carpool. A carpool is three or more Tinker AFB
employees who ride to work in the same vehicle. Only vehicles designed by the
25
manufacturer to carry three or more passengers may be used for a carpool. All
participants in the carpool must report in person to Pass and Registration to sign an
TINKER AFB Form H-176, Carpool Parking Request. The TINKER AFB Form H-176
will be retained by Pass and Registration. By signing the TINKER AFB Form H-176,
each participant agrees both individually and as a group, to share the responsibility of the
permit and in keeping the carpool valid. One permit will be issued to the group and can
be used by each member. When a carpool drops below three participants, the permit
must be returned to Pass and Registration immediately. When one carpool member is on
leave, the remaining passengers may use the permit. If a member has a shift change for
more than 60 days, and that shift change causes the total number of persons in the carpool
to drop below 3 the permit will be turned in to Pass and Registration. To add or replace
participants of a carpool, the added person must report to Pass and Registration in person
to sign the TINKER AFB Form H-176. Participants must return a faded or mutilated
permit to Pass and Registration for replacement. Lost or stolen permits must be reported
in person to 72 SFS BDOC and a statement completed.
4.4.5.16.1. (Added-TINKERAFB) Misuse of carpool parking permits may result in
the immediate revocation of the permit and suspension or revocation of the offender’s
base driving privileges. The 72 MSG/CD will make the determination to suspend or
revoke driving privileges.
4.4.5.16.2. (Added-TINKERAFB) Carpool parking permits will be displayed from
the rearview mirrors or vehicle dashboards in a position easily visible for inspection
when parked in their authorized spaces or areas. Vehicles must be secured when
permits are displayed.
4.4.5.17. (Added-TINKERAFB) The following violations of parking regulations are
presumed to be infractions of this directive. Multiple infractions will cause loss of base
driving privileges for all persons involved for a minimum of 30 days but not to exceed 6
months as determined by the installation commander:
4.4.5.17.1. (Added-TINKERAFB) Unauthorized use, possession or display of
parking permits, decals and placards. Where applicable, city, state or federal
authorities will be notified for further actions.
4.4.5.17.2. (Added-TINKERAFB) Failure to notify 72 SFS BDOC when a permit
that was previously reported as lost is found.
4.4.5.17.3. (Added-TINKERAFB) Allowing use of a permit by persons other than
those listed on the permit request.
4.4.5.17.4. (Added-TINKERAFB) Use, possession or display of false permits or
permits reported as lost or stolen.
4.4.5.17.5. (Added-TINKERAFB) Falsifying data on TINKER AFB Form H-176.
4.4.5.17.6. (Added-TINKERAFB) Unauthorized
permits.
making
or
reproduction
of
4.4.5.17.7. (Added-TINKERAFB) Unauthorized parking in handicap spaces.
4.4.5.17.8. (Added-TINKERAFB) Unauthorized parking in any space or area
appropriately signed or painted so as to designate a No Parking Area.
26
4.4.5.17.9. (Added-TINKERAFB) Parking in restricted parking spaces except by
persons to whom the spaces are assigned.
4.4.5.17.10. (Added-TINKERAFB) Parking within 8 feet of each side of doorways.
4.4.5.17.11. (Added-TINKERAFB) Parking adjacent to yellow or red bumper
blocks or curbing.
4.4.5.17.12. (Added-TINKERAFB) Parking on pedestrian crosswalks.
4.4.5.17.13. (Added-TINKERAFB) Parking in motor vehicle traffic ways.
4.4.5.17.14. (Added-TINKERAFB) Parking of a vehicle in two or more spaces.
4.4.5.17.15. (Added-TINKERAFB) Parking on any seeded area.
4.4.5.17.16. (Added-TINKERAFB) Backing into spaces where the vehicle will be
facing the flow of traffic when diagonally parked.
4.4.5.17.17. (Added-TINKERAFB) Parking within 25 feet of trash dumpsters.
4.4.5.17.18. (Added-TINKERAFB) Parking in any area not specifically designated
by white lines as a parking space.
4.4.5.17.19. (Added-TINKERAFB) Parking more than 18 inches from the curb
when parallel parked.
4.4.5.17.20. (Added-TINKERAFB) Parking within 15 feet of a fire hydrant.
4.4.5.17.21. (Added-TINKERAFB) Parking within 20 feet of a stop sign or traffic
control device before an intersection.
4.4.5.18. (Added-TINKERAFB) Personnel residing in base housing may park boat
trailers, camping equipment and other large recreational vehicles for no longer than 72
consecutive hours for the purpose of loading, unloading, charging batteries, preparation
for use, or storage. Under no circumstances will recreational vehicles be parked for
longer than 72 hours. Parking is not authorized for any amount of time if a reasonable
officer deems it a safety obstacle to other motorists due to its size. Long term parking is
available with Outdoor Recreation or commercial off-base locations for all vehicles not
authorized in base housing. Violators are subject to towing.
4.4.5.18.1. (Added-TINKERAFB) Only authorized Tinker AFB Family Camping
(Fam Camp) patrons will be allowed to park in designated Fam Camp parking spots
within the Fam Camp compound.
4.4.5.19. (Added-TINKERAFB) Vehicles will not be parked in spaces or areas that
will not accommodate the vehicle. Vehicles must fit within marked white lines properly.
No vehicle or trailer may occupy more than one space at a time.
4.4.5.20. (Added-TINKERAFB) The operation or parking of privately owned vehicles
(except pedaled bicycles, roller blades) on dormitory grounds, not specifically designated
for driving or parking is prohibited for any distance. This includes grassed areas, under
stairways, and sidewalks.
4.4.5.21. (Added-TINKERAFB) Vehicles may be parked with the flow of traffic on the
street parallel to curbs in the Tinker AFB housing area providing the curbing is not
27
painted and parking is not otherwise restricted. Vehicles will not be parked in any
manner that would obstruct the flow of vehicle traffic or hinder the response of
emergency vehicles.
4.4.5.22. (Added-TINKERAFB) Vehicles cannot be parked in ramp areas blocking
hangar doors.
4.4.5.23. (Added-TINKERAFB) Violations will be maintained on the driver’s record
for 12 months from the date of issue for non-moving violations and 24 months from the
date of issue for moving violations. Violations will only be removed after the appropriate
time period has elapsed.
4.4.5.24. (Added-TINKERAFB) The following penalties and guidelines apply to
parking violations on Tinker AFB. Multiple suspensions will be served concurrently, all
violations:
4.4.5.24.1. (Added-TINKERAFB) One handicap parking violation may result in a
30-day suspension of base driving privileges.
4.4.5.24.2. (Added-TINKERAFB) Three tickets within 12 months results in a 30day suspension.
4.4.5.24.3. (Added-TINKERAFB) Four tickets within 12 months results in a 60day suspension.
4.4.5.24.4. (Added-TINKERAFB) Five tickets within 12 months results in a 90day suspension.
4.4.5.24.5. (Added-TINKERAFB) Six tickets within 12 months results in a 6month suspension.
4.4.5.24.6. (Added-TINKERAFB) Seven tickets within 12 months results in a 1year suspension.
4.4.5.25. (Added-TINKERAFB) Parking violations are 2 points each and count toward
suspension actions for 12 months from the date issued. Single tickets or violations may
be counted toward both a total citation volume suspension and a points accumulation
suspension.
4.4.5.26. (Added-TINKERAFB) Individuals who receive parking tickets on vehicles
registered to someone else shall accept responsibility for that citation.
4.5. Off-installation Traffic Activities. The DFC must develop procedures for the sharing and
exchanging of information with civil authorities. Local procedures must cover the receiving,
processing and securing of traffic and related incident reports received from other investigative
agencies. Unit commanders will be notified when personnel under their authority are involved in
serious off-base incidents (i.e., major accidents, DUI, hit and run, etc).
4.5. (TINKERAFB)Damage to Government property or death/injuries to military or
government civilian personnel must be reported to Security Forces the next duty day.
4.6. (Added-TINKERAFB) Use of Cellular Phones
4.6.1. (Added-TINKERAFB) Use of Cellular Phones. Cellular telephone usage while
operating vehicles on Tinker AFB is prohibited, unless the cellular telephone is of such
28
design that it is used in a hands-free mode or has a hands-free option enabled. Placing the
phone in speaker mode then holding it or placing it on your lap does not constitute hands free
operation. Operators of vehicles are to pull safely to the side of the roadway, not interfering
with the normal flow of traffic, to use a cellular telephone not equipped with a hands-free
device. Passengers in vehicles are not prevented from using a cellular telephone in any
configuration not involving the driver. EXCEPTION: The use of a cellular telephone not
equipped with a hands-free device by emergency response forces, responding to a true
emergency, is authorized. The provisions of this paragraph shall not relieve the driver of any
authorized emergency vehicle from the duty to drive with due regard for the safety of all
persons, nor shall such provisions protect the driver from the consequences of his/her
reckless disregard for the safety of others. Violators are subject to enforcement actions listed
in Table 4.
Table 4.1. (Added-TINKERAFB) Unauthorized Cellular Phone Use/Action Taken
Number of Offenses Action
First offense
Second offense
Third offense
Issued DD Form 1408, Armed Forces Traffic
Ticket and Revocation of driving privileges on
the installation for 7 days.
29
Chapter 5
DRIVING RECORDS AND THE TRAFFIC POINT SYSTEM
5.1. Driving Records. Use SFMIS to record vehicle traffic accidents, moving and parking
violations, suspension or revocation actions and traffic point assessments involving military and
DoD civilian personnel, their family members and other personnel operating motor vehicles on a
military installation. Use AF Form 1313, Driver Record, when SFMIS is not available. When
filling out the form, use the following codes in the “accident classification” block:
5.1.1. Identify individuals who are principals in a motor vehicle accident as “Driver 1”
subject or “Driver 2” victim.
5.1.2. Identify accidents appropriately with “MVA” minor vehicle accident; (MJVA) major
vehicle accident; “NLD” no liability determined; “PD” property damage; “PI” personal
injury; “G” government; “P” private; “V” vehicle; and “FO” fixed object.
Table 5.1. Point Assessment for Moving Violations
Violation
Points Assessed
Reference paragraph 4.1.1.1. See note #1.
2
Operating a radar detection device to indicate the presence of
speed recording instruments or to transmit simulated erroneous
speed (prohibited on DoD installations). See note #2.
3
Failure to yield to pedestrians in designated walkway/crosswalk.
See note #2.
3
NOTES:
1. Applies to not using or when child restraint system is improperly installed, i.e., car
seat, infant carrier, booster seat, belt/strap modification (when required by manufacturer),
etc. Assess four points when no restraint system of any kind is used.
2. When violation occurs within an active school zone, add 1 point to point assessment.
30
Table 5.2. Point Assessment for Non-Moving Violations.
Violation
Points Assessed
Unattended Child under 12 years of age left in vehicle. Animals
are included if a danger exists to the animal. See note #4.
6
Improper Registration (fraudulent tags).
4
Misuse of handicap decal. See note #2.
3
Illegally parked in designated handicap area (no decal, license or
placard displayed).
3
Unattended Vehicle (while running).
3
Abandoned Vehicle.
3
Improper Parking. See note #3.
2
Improper Registration (expired or unregistered).
2
NOTES:
1. When two or more violations are committed on a single occasion, points may be
assessed for each violation.
2. When a vehicle has a handicap decal displayed, but the occupant is not the decal or
placard registrant and is not dropping off or picking up the handicapped registrant. Also
includes parking in an area designated for “Van” access only, and handicap registrant has
parked another vehicle class instead.
3. When designated in local parking plan (i.e., double parked, parked in reserved parking,
against the flow of traffic and those areas designated for emergency vehicles).
4. When an AF Form 3545 will also be accomplished. Revocation of driving privileges
for one year will be considered by the commander. Example: If children or animals were
left in dangerous conditions in vehicle, i.e., in hot weather where interior temperatures
may reach dangerous levels, keys left accessible to children or where conditions are
deemed hazardous by a reasonable person.
5. Emergency vehicles are authorized to park in any area deemed necessary to affect a
response.
5.2. Point System Procedures.
5.2.1. Distribute citation copies and process point assessments IAW AFMAN 31-201,
Volume 7, Security Forces Reports and Analysis.
5.2.2. Installation Commanders may suspend or revoke driving privileges as provided by this
instruction regardless of whether the improvement measures identified in AFI 31-218(I) are
accomplished.
31
5.3. Disposition of Driving Records. Follow AFI 33-364, Records Disposition – Procedures
and Responsibilities, to maintain and destroy records of military personnel released from active
duty. Driving records remain active in the case of immediate reenlistment, change of officer
component or military and civilian retirement or when continued access to an installation is
authorized. Retain or destroy according to AFI 33-364 records on civilian personnel who are
terminating on-base employment.
32
Chapter 6
IMPOUNDING PRIVATELY OWNED VEHICLES
6.1. Standards for Impoundment. The on-duty SF Flight Chief, or above, will determine
when the vehicle will be driven or moved without owner’s consent if the owner cannot be
contacted or the owner refuses and conditions in AFI 31-218(I) are present.
6.2. Procedures for Impoundment. At times, civilian law enforcement or civilian government
agencies will request the Air Force impound an on-base vehicle for reasons not related to
military issues. Staff such requests through the SJA and DFC. When appropriate, comply and
support such requests and impound the vehicle for a reasonable period. Release the vehicle if
civil authorities do not take custody of the vehicle within a reasonable period as determined by
Installation Commanders.
6.3. Disposition of Vehicles After Impoundment. Impoundment and disposition of privately
owned vehicles is a high-risk process. It is imperative an installation have a detailed plan to:
Ensure wide publicity of base impoundment rules; have a process to provide reasonable notice of
impoundment and an opportunity to reclaim a vehicle; conduct a review of proposed disposal by
appropriate base offices, to include the SJA, prior to taking action; and a process to obtain retail
records of these actions in the event of litigation or high-level inquiry. Further information on
impoundment can be found in AFI 31-218(I).
JUDITH A. FEDDER, Lieutenant General, USAF
DCS/Logistics, Installations & Mission Support
(TINKERAFB)
CHRISTOPHER P. AZZANO, COLONEL, USAF
COMMANDER
33
Attachment 1
GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION
References
Title 10, U.S.C. § 2575, Disposition of Unclaimed Property
Title 10 U.S.C. §, Section 8013
Title 50, U.S.C. § 797
DoD 4140.1-R, DoD Supply Chain Materiel Management Regulation, 23 May 2003
DoDD 5525.4, Enforcement of State Traffic Laws on DoD Installations, 2 November 1981
DoDD 7730.47, Defense Incident Based Reporting System (DIBRS), 1 December 2003
DoD 4160.21M, Defense Material Disposition Manual, 18 August 1997
AFPD 31-1, Integrated Defense, 7 July 2009
AFI 31-101, The Integrated Defense, 8 October 2009
AFI 31-201, Security Forces Standards and Procedures, 31 March 2009
AFI 31-218(I), Motor Vehicle Traffic Supervision, 22 May 2006
AFI 10-245, Antiterrorism (AT), 30 March 2009
AFI 36-810, Substance Abuse Prevention and Control, 22 July 1994
AFMAN, 32-1017, DoD Transportation Engineering Program, 17 November 2003
AFI 44-102, Medical Care Management, 1 May 2006
AFI 44-121, Alcohol and Drug Abuse Prevention and Treatment (ADAPT) Program, 26
September 2001
AFMAN 33-363, Management of Records, 1 March 2008
AFI 51-905, Use of Magistrate Judges for Trial of Misdemeanors Committed by Civilians, 1
June 1998
AFI 91-207, USAF Traffic Safety Program, 22 May 2007
Forms Prescribed.
AF Form 533, Certificate of Compliance - Private Motor Vehicle Registration, 1 December 1984
Adopted Forms.
AF Form 1313, Driver Record
AF Form 2293, US Air Force Motor Vehicle Operator Identification Card
CVB Form 1805, United States District Court Violation Notice
DD Form 1920, Alcohol Influence Report
DD Form 2220, DoD Registered Vehicle Decal
DD Form 2507, Notice of Vehicle Impoundment
34
DD Form 1408, Armed Forces Traffic Ticket
DD Form 1920, Alcohol Influence Report
DD Form 2507, Notice of Vehicle Impoundment
AF Form 75, Visitor/Vehicle Pass
AF Form 1313, Driver Record
AF Form 2293, US Air Force Motor Vehicle Operator Identification Card
AF Form 3545, Incident Report
AF Form 1315, Accident Report
Abbreviations and Acronyms
BAC—Blood Alcohol Concentration
BAT—Blood Alcohol Test
BrAC—Breath Alcohol Concentration
CE—Civil Engineer
CONUS—Continental United States
DFC—Defense Force Commander
DBIDS—Defense Biometric Identification System
DoD—Department of Defense
DoDD—Department of Defense Directive
DRMO—Defense Reutilization and Marketing Office
FO—Fixed Object
G— —Government
GOV—Government Owned Vehicle
MAJCOM—Major Command
MAJCOM/SF—Major Command Defense Force Commander
MJVA—Major Vehicle Accident
MTMCTEA—Military Traffic Management Command Transportation Engineering Agency
MVA—Motor Vehicle Accident
MWR—Morale, Welfare and Recreation
NAF—Nonappropriated Fund
NHSPS—National Highway Safety Program Standards
NHTSA—National Highway Traffic Safety Administration
NLD—No Liability Determined
OCONUS—Outside Continental United States
ORV—Off Road Vehicle
P——Private
PCS—Permanent Change of Station
PD—Property Damage
PI—Personal Injury
POV—Privately Owned Vehicle
SFMIS—Security Forces Management Information System
SJA—Staff Judge Advocate
S5R—Security Forces Administration and Reports
U.S.C. §——United States Code
V——Vehicle
35

BY ORDER OF THE SECRETARY AIR FORCE MANUAL 31-116

Transcription

Similar documents

Ah-Nab-Awen Park - City of Grand Rapids

Save on Parking Expenses with TransitChek

Scanned Document - Covenant Health

Ref: SB0160 Sun and Mountains Near the Sea, Busot Alicante

Autorama

NI CIHT Venturer 19th October 2015

Parking Parking

LOCK - Plainfield Township

Directions to UCSD Extension K-12 Facility Located at: 6256

BRP Flyer - III_13-ENG.indd