by order of the commander aviano air base instruction ... · 6 avianoabi24-302 5 january 2018...

BY ORDER OF THE COMMANDER

AVIANO AIR BASE (USAFE)

Aviano Air Base Instruction

24-302

5 JANUARY 2018

Vehicle Management

VEHICLE MANAGEMENT

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

ACCESSIBILITY: Publications are available on the e-Publishing website at

www.e-publishing.af.mil for downloading.

RELEASABILITY: There are no releasability restrictions on this publication.

OPR: 31 LRS/LGRV

(Vehicle Maintenance Flight)

Supersedes: AVIANO ABI 24-302,

19 November 2004

Certified by: 31 LRS/CC

(Lt Col Sharonda L. Graham)

Pages: 22

This instruction implements AFPD 24-3, Management, Operation and Use Of Transportation

Vehicles, and outlines the definitions, responsibilities and procedures for an effective vehicle

accident and abuse program for Aviano Air Base, and Geographically Separated Units (GSU),

IAW AFI 24-302, Vehicle Management. Visibility and emphasis is placed at the unit level and

under the direct control of the unit commander to foster better operator care and condition of the

31st Fighter Wing (31 FW) vehicle fleet. Additionally, this instruction establishes the policy for

Official Use of Government Motor Vehicles (GOV) assigned to the 31st Fighter Wing, Aviano

Air Base, Italy, including vehicles rented or leased using appropriated funds. This policy reflects

guidance outlined in DoD 4500.36-R, Management, Acquisition, and Use of Motor Vehicles and

AFI 24-301, Vehicle Operations, promoting the safe operation of government vehicles and

includes policy guidance in relation to the vehicle idling, Permissible Operating Range (POR),

Other Government Motor Vehicle Conveyances (OGMCVs), official use of government

vehicles, and stand-by mobile maintenance. It applies to all personnel operating government

vehicles assigned to Aviano Air Base, Italy and any other applicable GSU. Ensure that all

records created as a result of processes prescribed in this publication are maintained IAW

AFMAN 33-363, Management of Records, and disposed of IAW Air Force Records Information

Management System (AFRIMS) Records Disposition Schedule (RDS). Refer recommended

changes and questions about this publication to the Office of Primary Responsibility (OPR)

using the AF Form 847, Recommendation for Change of Publication; using the appropriate

functional chain of command.

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

2 AVIANOABI24-302 5 JANUARY 2018

SUMMARY OF CHANGES

This document has been substantially revised and must be completely reviewed. Major changes

include new references to AFI 24-302, Vehicle Management, dated 26 June 2012, Incorporating

Change 1, 25 July 2016, and certified current, 15 August 2017, as well as AFI 24-301, Vehicle

Operations, dated, 11 May 2017. Also, there are changes affecting the Vehicle Accident/Abuse

Program to include a new requirement for providing proof that the personal insurance company

has been notified. Finally, policy guidance is added regarding the vehicle idling policy,

Permissible Operating Range (POR) for Government Owned Vehicles (GOVs) and vehicular

equipment, official use of government vehicles, and stand-by mobile maintenance.

AVIANOABI24-302 5 JANUARY 2018 3

Chapter 1

ACCIDENT/ABUSE MANAGEMENT

1.1. The purpose of this program is to deter vehicle accident and abuses, which jeopardizes

lives and drains limited resources. Commander emphasis and direct involvement is essential

to the program’s success.

1.1.1. Definitions.

1.1.1.1. Fair Wear and Tear: The deterioration of items attributed to normal usage of a

vehicle or equipment based on its age, usage and life expectancy.

1.1.1.2. Vehicle Accident: A result of a collision, impact, or abrasion against a fixed or

moving object with a motor vehicle, that causes damage, whether immediately noticeable

or not.

1.1.1.3. Vehicle Abuse: Damage caused by willful or negligent acts of improper

operation or care. Vehicle abuse may result in early failure of components or immediately

detectable damage. Some examples of vehicle abuse are listed in Attachment 2 of this

instruction.

1.1.1.4. Vehicle Incident: Damage caused by acts of nature, natural disasters, mechanical

failures or other phenomenon that in no way could have been avoided by safe operation

or adequate vehicle care during non-use. Note: Vehicles involved in an accident/abuse

will not be factored into the equation when determining vehicles in commission in

relation to Mission Essential Levels (MEL).


Chapter 2

ACCIDENT/ABUSE PROGRAM

2.1. All units assigned, attached to, or associated with the 31st Fighter Wing, to include

Geographically Separated Units (GSU), and members/units transitioning not

assigned/associated, will ensure compliance with the information in this instruction.

2.1.1. For transient personnel, if any damage occurs, the 31 LRS/CC will notify the transient

member’s home station organization’s commander for reimbursements.

2.2. The goal of this program is to eliminate or reduce the number of vehicle accidents and

abuses, in order to protect Air Force personnel from injury and/or death and reduce or

eliminate unnecessary expenditure of limited resources at Aviano Air Base.

2.3. The base vehicle maintenance function is funded and staffed to provide scheduled and

unscheduled maintenance in relation to fair wear and tear, but not for accident and abuse

repairs. Using organizations are required to cover the cost of any “at fault” accident or abuse

damage(s).

2.3.1. The key to successfully reducing the number of accidents and abuses relies on unit

commanders maintaining high standards with regard to operator care. In addition, it is

imperative that they have a comprehensive program in place for vehicle operator training.

2.3.2. The 31 LRS/LGRV scheduled maintenance program is vital in preventing premature

failure of vehicle components and maintaining the vehicle fleet in safe and serviceable

condition. These scheduled inspections are time-critical and must be completed at certain

intervals to meet manufacturer and Air Force serviceability criteria. Therefore, overdue

vehicles (e.g. Vehicles not turned in for scheduled maintenance on or before their assigned

appointment date) will be considered vehicle abuse cases and processed accordingly.

2.3.3. The “using” unit commander will utilize their squadron’s Operations and Maintenance

(O&M) funds to pay for repairs attributed to “at fault” accidents and/or vehicle abuse, to

include U-Drive It (UDI) vehicles that their personnel sign out from Vehicle Operations. The

31 LRS/CC (delegated to the 31st Logistic Readiness Squadron, Director of Operations (31

LRS/DO)) will contact the using organization’s commander/resource advisor if timely

payment is not made.

2.3.3.1. The method of payment for accident and/or abuse repairs will be made through

the Government Purchase Card (GPC) program of the using organization and payments

are required upon repair completion. Our policy is to send all accident and/or abuse cases

to off base repair facilities to the maximum extent possible. If payment is not received in

a timely manner then the using organization may incur additional storage charges.


Chapter 3

ACCIDENT/ABUSE PROCEDURES

3.1. All GOVs involved in an accident, or found to have damage not previously reported

(Abuse/Incident), must be turned into the 31 LRS/LGRV as soon as possible, but no later

than the next duty day, so the damage assessment and initial repair cost estimate can be

accomplished.

3.1.1. IAW AFI 24-301, Vehicle Operations, paragraph 3.1.1, and this instruction, a

Standard Form (SF) 91, Motor Vehicle Accident Report, and DD Form 518, Accident

Identification Card, must be completed with all pertinent information. Additionally, for US

Military personnel, proof that the operator’s personal insurance has been notified will be

provided upon vehicle turn-in to 31 LRS/LGRV. For personal insurance notification, an

official email or memorandum from the insurance company will suffice. The vehicle will not

be considered reported to maintenance until the vehicle and all forms are properly submitted.

The reporting party must record the responding Security Forces Squadron individual’s name

and rank in block 89 of the SF 91. Note: Notification of personal insurance after an accident,

regardless of vehicle ownership or who is at fault, is a personal responsibility and

requirement IAW an individual’s insurance contract. In an effort to increase driver care of

GOVs, Vehicle Management requires proof that this personal responsibility has been

accomplished.

3.1.1.1. IAW AABI 31-218, Motor Vehicle Traffic Supervision, paragraph 4.2.3, all

traffic accidents are required to be reported to Security Forces. Anyone involved in an

on-base vehicle accident, major or minor, must immediately report the accident to the

Security Forces Desk Sergeant. For all GOV accidents, you must complete a Standard

Form 91, Operator Report of Motor Vehicle Accident and a DD Form 518, Accident

Identification Card, if damage was caused to private property. For GOV accidents, all

documents must be turned in to Vehicle Management no later than the next duty day.

3.1.1.1.1. If a Privately Owned Vehicle (POV) is involved in an accident with a

GOV, the Standard Form 91, pictures, and police report will be turned in to Vehicle

Management. The civilian will direct their portion of the claim to the base legal

office. Fleet Management & Analysis will draft the case for the GOV and will route

the case to legal. If an accident involves POVs, they must contact their insurance

company as soon as possible. If a POV is involved in an accident with a GOV, direct

the claim through the base legal office. Accidents involving a GOV may result in a

claim against the United States Government. Those found at-fault for an accident may

be liable for damages.

3.1.1.1.2. In the event of an accident, vehicles should not be moved unless police

officials give approval or if in a minor accident, all parties agree to clear the scene.

Drivers are advised to refrain from making any statements, oral or written, to

claimants or their agents regarding liability, cause of an accident, or the possibility of

claims approval.

3.1.1.1.3. Anyone involved in a major accident off base must immediately notify the

Security Forces Desk Sergeant who will assist in notifying Italian authorities. Anyone


involved in a minor accident off base in a POV must report it to Security Forces

within 72 hours.

3.1.1.2. IAW AFI 24-302, Vehicle Management, paragraph 10.4.10.5.3, an operator

surrenders the AF Form 2293, US Air Force Motor Vehicle Operator Identification Card,

with the SF 91 to the Vehicle Control Officer/ Vehicle Control Non-Commissioned

Officer (VCO/VCNCO) after an accident. Unit commanders may reinstate the license at

their discretion.

3.1.2. Any vehicle found to have accident/abuse damage will have a repair estimate work

order accomplished and pictures taken to create an Accident or Abuse Package, and assign it

a case number. The vehicle will then be parked and no corrective actions will be initiated

until the package has been completely routed.

3.1.2.1. Pictures documenting apparent damage will be taken first. Parts may then be

removed as needed to assess overall damage done to the vehicle. Pictures to document

additional damage to the vehicle after part removal may be added at any time.

3.1.3. The Vehicle Accident/Abuse Package will be prepared as soon as the accident/abuse

estimate is complete, and then it will be forwarded to the using organization’s commander

and VCO/VCNCO after being routed through 31 LRS Vehicle Management to the 31

LRS/DO for coordination. Packages will be posted on the SharePoint:

https://portal.usafe.af.mil/sites/Aviano/31MSG/LRS/LGRV/Lists/Abuse/All%20Items.a

spx

3.1.3.1. The Unit Commander, or equivalent, and VCO/VCNCO will be notified via

SharePoint notification email, along with legal, finance, and safety offices upon

completion of the Accident/Abuse Package. In the event of a GOV accident, include a

copy of the Security Forces accident report for the Wing Safety office’s use, if available.

3.1.3.2. The using organization has 10 duty days from notification to either provide a

release notification response via SharePoint, conduct an investigation, direct an Report of

Survey (ROS) including a DD Form 200, Financial Liability Investigation of Loss, or file

an appeal to 31 LRS (see Para 3.1.5.). 31 LRS/LGRV will open an accident/abuse repair

work order and begin repairs upon receipt of the release notification from the

organization or the 11th duty day after notification, unless appealed. An important item to

consider is that any vehicle parked for any extended period of time exposes that vehicle

authorization to the risk of permanent authorization cuts.

3.1.3.3. IAW AFMAN 23-220, Reports of Survey of Air Force Property, paragraph

3.1.19, an ROS must be processed when there is evidence of gross negligence, willful

misconduct, or deliberate unauthorized use pertaining to the loss, damage, or destruction

of a government vehicle or vehicle property records must be adjusted.

3.1.3.4. The investigator cannot hold the position of VCO/VCNCO.

3.1.3.5. If the investigation reveals an operator’s gross negligence was the proximate

cause of damage to a vehicle, commanders may assess pecuniary liability for the repair

cost.

3.1.3.6. Using organizations are responsible for payment of all replacement parts,

regardless of pecuniary liability or reimbursement made by the individual, through the

https://portal.usafe.af.mil/sites/Aviano/31MSG/LRS/LGRV/Lists/Abuse/All%20Items.aspx

https://portal.usafe.af.mil/sites/Aviano/31MSG/LRS/LGRV/Lists/Abuse/All%20Items.aspx


transfer of unit O&M funds. The 31st Logistics Readiness Squadron Resource Advisor

(RA) will coordinate with the using organization’s RA to move money between accounts

via Miscellaneous Obligation Reimbursement Document (MORD), if the using

organization does not use their GPC card to pay for the damage.

3.1.4. If the estimated repair cost exceeds the vehicle’s “one-time repair limit,” the Vehicle

Fleet Manager/Vehicle Management Superintendent (VFM/VMS) will determine if the

vehicle is not economically repairable and/or will not be repaired. Exceptions to the repair

limit may be made based on mission needs. Vehicles that are deemed noneconomically

repairable will have a Limited Time Inspection completed and routed to the 441st Vehicle

Support Chain Operations Squadron (VSCOS) for a disposition decision.

3.1.4.1. After repairs are completed, the actual repair cost is computed as follows:

3.1.4.1.1. To the maximum extent possible, vehicle accident/abuse repairs will be

contracted to local vendors. There may be cases where local vendors cannot

accomplish repairs due to mil-spec design vehicles. If the vehicle is repaired by 31

LRS/LGRV, the using organization is charged with the cost of replacement parts. In

most cases, replacement parts will be charged directly to the using organization’s

GPC program. If for some reason this is not possible, 31 LRS/LGRV will send repair

costs figures to the 31 LRS/RA, who in-turn processes a MORD to transfer funds

from the using organization.

3.1.4.1.2. When a vehicle is repaired by a contractor, the unit is charged with the

repair cost (parts and labor), via the GPC program, at the time the vehicle is picked up

from the vendor.

3.1.4.1.3. With regard to vehicle repairs via contract maintenance, 31 LRS/LGRV

Fleet Management & Analysis (FM&A) will notify the local vendor to begin repairs

on the vehicle once it is released by the applicable unit Commander, in coordination

with their RA. In the event that repairs exceed $5,000, Vehicle Management will

obtain three quotes and provide them to the using organizations so they can process

the necessary paperwork to increase their one-time purchase limit. If the repairs

exceeds $25,000 then the responsible organization will prepare the appropriate AF

Form 9, Request for Purchase, and the necessary fund cite. Once the repairs are

finished, the using organization is responsible for paying the vendor.

3.1.4.2. Accidents and abuse case statistics will be reported/tracked by 31 LRS/LGRV

FM&A on the SharePoint.

3.1.5. Commanders disagreeing with the findings of liability may appeal to the 31 LRS

Commander, delegated to the 31 LRS/DO, within 10 duty days from SharePoint notification.

Additionally, intent to appeal must be coordinated with 31 LRS/LGRV FM&A prior to the

10th duty day. If the 31 LRS/DO does not support the appeal, the appeal package will be

forwarded through the 31st Logistics Readiness Squadron Commander, 31st Mission Support

Group Commander and the 31st Fighter Wing Commander for final determination.

3.1.5.1. In the case of an appeal, the commander of the responsible unit has an additional

30 days from the date the appeal is received at 31 LRS/LGRV. If the appeal is approved,

no transfer of funds will occur.


3.1.5.2. If the appeal is unsuccessful or has not been resolved within 60 days of

notification, 31 LRS will then contact the responsible unit to make sure the required

payment is made.

3.1.6. The organization will pay all bills associated with repairs prior to release of vehicles

from Vehicle Management.

3.1.7. An AF Form 20, Repair Costs and Repairable Value Statement, will be prepared when

requested by the ROS officer and the member is reimbursing the Air Force.


Chapter 4

VEHICLE IDLING

4.1. The following is Wing specific guidance regarding vehicle idling.

4.2. The vehicle operator has the primary responsibility to reduce fuel consumption and

engine wear of Aviano Air Base assigned vehicles while simultaneously promoting

environmental protection, in response to prescribed initiatives outlined in Executive Order

13514, Federal Leadership in Environmental, Energy, and Economic Performance. Operators

of government owned, rented, or leased vehicles are required to adhere to engine idle restrictions

while operating vehicles within or outside the confines of Aviano Air Base, IAW AFI 24-302,

paragraph 11.9.

4.3. Unnecessary engine idling is the single greatest contributing factor to fuel waste by

vehicle fleets and is also the primary cause of premature engine wear/failure. Furthermore,

vehicle exhaust gases from idling vehicles contribute greatly to air pollution. When not in traffic,

operators of GOVs will turn off vehicle engines if the vehicle is stationary for more than five (5)

minutes, unless a waiver or an exemption has been granted by Vehicle Management IAW

paragraph 4.5.

4.4. This policy does not apply when:

4.4.1. Idling to verify that the vehicle is in safe operating condition (operator inspection)

and/or to bring vehicle to operating temperature or build air pressure for air operated vehicle

systems.

4.4.2. Vehicles undergoing maintenance that are difficult to restart or require cool down

procedures prior to shut-off.

4.4.3. Ambient temperatures are below 40 degrees or above 95 degrees Fahrenheit and when

operators are in the vehicle and not reasonably able to wait in a climate-controlled facility

(e.g. Flight line personnel awaiting their next call to service an inbound aircraft).

4.4.4. Idling is allowed during cold weather to aid in the initial clearing of ice and/or snow

from the vehicle.

4.4.5. Idling is necessary for operation of emergency vehicles and equipment engaged in

operational activities, responding to emergency situations, and/or performing any activity

directly related to a public safety.

4.4.6. Vehicles that are required to idle in order to operate auxiliary equipment or are

equipped with temperature sensitive equipment that must be kept at an appropriate

temperature (e.g. SFS K-9 vehicle).

4.4.7. Idling while waiting in line or queuing (e.g. Dump trucks waiting to receive loads

from another vehicle). However, vehicles queuing should not idle while waiting for the

transferring vehicle to retrieve the load.

4.5. Using organizations with unique vehicle operating requirement must submit, in

writing, a list of vehicle(s) requiring exemption from this idling policy, along with a full

justification. All requests for exemption shall be routed through Vehicle Management for

determination.


Chapter 5

OTHER GOVERNMENT MOTOR VEHICLE CONVEYANCE (OGMVCS)/ALL-

TERRAIN VEHICLES (ATVS)/TRAILERS NOT CLASSIFIED AS A VEHICLE

5.1. This section concerns local policies and procedures relating to procurement

coordination, and maintenance related to OGMVCs, ATVs, and trailers not classified as a

vehicle.

5.2. OGMVCs are self-propelled assets providing a basic passenger and/or light cargo

carrying transportation capability (i. e., golf carts, electric stand-up transportation, etc.) that

DO NOT meet specifications of 49 CFR, Part 571, Federal Motor Vehicle Safety Standards, or

have been determined as such, by the appropriate Integrated Product Team (IPT) Program

Manager at Robins AFB Support Equipment and Vehicles (SE&V) Division, to be an OGMVC

by Air Force definition.

5.2.1. Vehicle/Equipment Determination will be conducted by Vehicle Management, in

coordination with the proper agencies. Vehicle Management will review all purchase

requests for non-registered vehicles to ensure the asset is not a registered vehicle.

5.2.2. When needed, Vehicle Management will forward trailer specifications, pictures and/or

appropriate information to the appropriate Robins AFB SE&V IPT Program Manager,

through 441 VSCOS, for determination to ensure the desired asset is not a centrally procured

registered vehicle or trailer. The IPT Program Manager makes the final vehicle/equipment

determination.

5.2.3. Trailers centrally procured by Robins Air Force Base (AFB) SE&V (to include

military design (tactical) trailers) are classified and managed as a registered vehicle IAW AFI

24-302, Paragraph 1.1.3. Any trailers meeting all elements of following criterion will also

be classified and managed as a registered vehicle IAW Air Force standards. Robins AFB

SE&V is the only authorized purchasing agent for Air Force registered vehicles.

5.2.4. Measuring 6’x12’ (width/length) or larger.

5.2.5. Has Department of Transportation (DOT) approved lighting.

5.2.6. Has at least two axles.

5.2.7. Has towing vehicle braking system or surge brakes.

5.2.8. Has a Gross Vehicle Weight Rating of over 6,999 lbs.

5.3. Trailers not meeting all “registered vehicle” criteria established in AFI 24-302, Vehicle

Management, paragraph 1. 1.3, will be identified as an equipment item. Note: With regards to

registered trailers, Vehicle Management is only responsible for the management and

maintenance of the vehicle portion. All equipment on the trailer that has a specific organizational

use is maintained by the using organization. Exception: Trailers classified as Construction,

Mining, Excavating and/or Highway Maintenance Equipment in Federal Stock Class Group 3800

(e.g. Concrete mixer, mounted vacuum cleaner, water distribution tanker, dump trailer,

pneumatic drill, sewer trailers) will be classified as a vehicle.


5.4. The following trailers will not be classified as vehicles regardless of the criteria

established in AFI 24-302, Vehicle Management, paragraph 1. 1.3, (e.g. Horse trailers, travel

trailers or campers, mobile classrooms, mobile bleachers, mobile homes and mobile stages).

5.6. Maintenance and Organizational Responsibility.

5.6.1. Upon written request, and with the approval of the VFM/VMS, Vehicle Management

may provide maintenance support to organizations owning OGMVCs, ATVs and/or trailers

not classified as a vehicle.

5.6.1.1. All maintenance/parts support for these assets will be on a reimbursable basis

only.

5.6.1.2. Any service provided to these assets will be on a “manpower/mission

permitting” basis.

5.6.2. If the VFM/VMS approves maintenance support, the following will be provided by

Vehicle Management. 31 LRS/LGRV FM&A will:

5.6.2.1. Request an “X”-registration number via the Air Force Vehicle Management

Neighborhood’s “X/Z” Registration Request tool.

5.6.2.2. Establish Vehicle Historical Record for each asset.

5.6.2.3. Notify the owning organization of pending maintenance action due dates.

5.6.2.4. Request a “Z”-registration number via the Vehicle Management Neighborhood’s

“X/Z” Registration Request tool, when OGMVCs, ATVs and/or trailers not classified as

a vehicle are not maintained by Vehicle Management.

5.6.3. If the VFM/VMS does not approve maintenance support, organizations owning

OGMVCs, ATVs and/or trailers not classified as a vehicle will:

5.6.3.1. Manage their asset as an equipment item.

5.6.3.2. Fund and manage all aspects of initial procurement, maintenance, and

replacement.

5.6.3.3. Work to secure and fund a local maintenance agreement for asset maintenance

above the operator level. Additionally, owning organizations will ensure assets are

maintained IAW manufacturer recommended intervals and will have a complete safety

and serviceability inspection conducted at least annually.

5.6.3.4. Coordinate purchase of license plate(s) with 31 LRS/LGRV FM&A.

5.6.3.4.1. Owning organizations will fund all license plate purchases.

5.6.3.5. Ensure assets that operate on public roads, off an installation, comply with the

following:

5.6.3.5.1. Affix two license plates per asset, one front and one rear as per United

States General Services Administration Federal Management Regulation 102-34.130,

License Plates. Exception: This does not apply to two-wheeled motor vehicles and

trailers, which require rear license plates only.

5.6.3.6. Owning organizations will process assets for disposal IAW local Defense

Logistics Agency-Disposition Service (DLA-DS) procedures. UNICOR procured license


plates will be turned in to Vehicle Management for disposition as “accountable items”

and returned to UNICOR for destruction.


Chapter 6

STANDBY MOBILE MAINTENANCE

6.1. During off-duty hours, Vehicle Management Stand-By Mechanics will respond to calls

for vehicle repairs such as, emergency response vehicles, units that have vehicle types that

fall below MEL, and vehicles assigned to VIPs.

6.2. Stand-By Mechanics will not be used for routine calls, such as to unlock vehicles.

6.3. General-purpose vehicles blocking a runway, taxi-ways, or impeding traffic should be

safely moved out of the way and reported the following duty day during normal duty

hours. Note: If there is a dispute concerning the validity of a call, the Stand-By Mechanic will

contact the NCOIC of Customer Service Center (CSC) or the VMS for clarification. If either

cannot be contacted, the Stand-By Mechanic will respond to the call and ensure all information is

logged into continuity book.

6.4. Stand-By vehicle maintenance services are available by contacting the Fuel Service

Center via DSN: 632-7043/7064 or COMM: 0343-30-7043/7064. Stand-by duties will be daily,

from 1630 hours through 0900 hours during normal duty days, and 24 hours a day on weekends

and non-duty days. During duty hours, contact VM CSC at 632-8588.


Chapter 7

OFFICIAL USE OF GOVERNMENT OWNED VEHICLES

7.1. All personnel will restrict the use of GOVs for official mission purposes

only. Unauthorized use of GOVs often results in unnecessary expenditures of funds and public

criticism. GOV transportation shall not be provided based solely on reasons of rank, position,

prestige, or personal convenience.

7.2. The POR is established to maximize efficiency of all 31 FW GOVs.

7.2.1. The POR for GOVs assigned to Aviano Air Base is defined as a 30 mile radius around

Aviano Air Base. The following locations are outside the range but have been identified as

frequently traveled areas and will be considered inside the POR.

7.2.1.1. Marco Polo Airport

7.2.1.2. Vicenza

7.2.1.3. Ghedi AB

7.2.2. All units required to operate GOVs outside the POR are responsible for coordination

of all required border clearance letters should GOVs be used to travel outside the borders of

Italy. There is no longer a requirement to formally request to exceed the POR through LRS

Vehicle Dispatch. However, units exceeding the POR should still have a courtesy inspection

conducted by 31st Logistics Readiness Squadron, Vehicle Maintenance Flight, during normal

duty hours, at bldg. 1010, no earlier than 24 hours prior to departure to ensure overall safety

and road worthiness and if needed, to perform scheduled maintenance.

7.2.3. When urgent short notice (less than 24 hours) mission requirements dictate the use of

a GOV or rental to exceed the POR outside of normal duty hours, the user is responsible for

conducting a thorough inspection of the vehicle prior to departure. If there are any

questionable discrepancies, the user should notify the Vehicle Operations Control Center

who will determine if standby maintenance should be called for assistance, if a replacement

vehicle is needed, or if UDI vehicle is authorized.

7.2.4. Units exceeding the boundaries of the established range will be responsible for vehicle

recovery costs incurred should the GOV breakdown outside the POR.

7.3. IAW AFI 24-301, Vehicle Operations, Paragraph 3.7.1.1., Reasonable Proximity for

Temporary Duty (TDY) Sustenance, members TDY to Aviano Air Base and operating

GOVs will not exceed a 5 mile radius from the base in order to obtain sustenance. Transient

Aircrew landing at Aviano requiring meals only, will be taken to on base eating establishments.

For TDY personnel billeted at off base hotels due to non-availability at the Mountain View

Lodge a 5 mile radius of their hotel should be used for sustenance.

7.3.1. All vehicle requests in support of a deployment, command exercises and/or any type

of TDY within or departing Italy must be coordinated through Fleet Management and

Analysis. Requests must be processed 30 days before the proposed travel dates, to allow for

appropriate vehicle sourcing and/or coordination through higher headquarters as needed.

7.4. Mission specific authorizations are approved only for emergency response personnel

for the purpose of securing meals from the on-base military dining facility and


nonappropriated funds, Army and Air Force Exchange Service, and Defense Commissary

Agency, operated eating establishments to include shoppettes. Travel to and from the base

gymnasium when on duty is also allowed. This is predicated on mission requirements and is not

granted for the personal convenience of the members. This is not to be interpreted as authority to

utilize GOVs to participate or attend events/engagements listed in AFI 24-301, Vehicle

Operations, Chapter 3; Section 3K, to include Airmen Leadership School graduations and

sporting events (participation as a player or spectator is not a justification). AMDS is authorized

when providing medical coverage.

7.4.1. The units listed below have been granted mission specific authorization

7.4.1.1. 31 SFS–personnel geared up for response (vest, weapon, on patrol)

7.4.1.2. 31 AMDS–personnel operating ambulances

7.4.1.3. 31 CES–personnel operating fire fighting vehicles

7.4.1.4. 31 MDOS–personnel operating ambulances

7.5. IAW AFI 91-207, Air Force Traffic Safety Program, paragraph 3. 4, Unit Commanders

will establish and enforce duty hour limits for operators of motor vehicles to reduce the potential

for traffic mishaps caused by operator fatigue IAW DoDI 6055.04, DoD Traffic Safety Program.

To reduce the potential for traffic mishaps caused by operator fatigue, commanders and

supervisors will apply a formal risk assessment IAW AFI 90-802, Risk Management. If time

critical, a real time risk assessment will be used to assess the risks, establish operating

procedures, apply supervision and other controls to mitigate risks. This applies to missions

exceeding a singular shift or duty day. Risk assessments include, but not limited to, are time on

duty, operator’s physical condition, driving conditions, duty requirements and length of travel.

7.6. Commercial Terminal Transportation IAW AFI 24-301, Vehicle Operations,

paragraph 3. 8.3, Use of resources to support administrative activities, for which sufficient

public transportation or commercial services exist to fulfill the need, detracts from direct mission

support and should be avoided. To that end and as defined elsewhere in this publication, other,

more cost effective and responsive means of transportation will be utilized to support

administrative activities such as commercial terminal transportation. Terminal transportation will

be addressed in the installation official use policy and include provisions to ensure support is not

based solely on reasons of rank, position, prestige or personal convenience.

7.6.1. Travel to commercial terminals with GOVs will be evaluated on a case by case basis

and authorized when at least one of the conditions below are met:

7.6.1.1. Individual is normally authorized Domicile to Duty transportation. Under 31

U.S.C. §1344 (b)(9), Passenger Carrier Use, the Secretary of the Air Force must approve

all domicile-to-duty authorizations. (There are no approved domicile-to-duty

authorizations at Aviano Air Base.)

7.6.1.2. Necessary because of emergency situations or to meet security requirements.

(Security requirements are defined as increased Force Protection Condition measures or

personnel traveling with government weapons.)

7.6.1.3. Terminals are located in an area where other methods of transportation cannot

meet mission requirements in a responsive manner (e.g. No-notice deployment/TDY, last

minute flight change, public/commercial transportation strike, etc). In order for a request


to be approved for responsive manner, justification must be provided as to why public or

commercial transportation services could not be utilized.

7.6.2. Groups or individuals not meeting the above requirements will not be afforded GOV

support and should utilize public transportation or other commercial transportation services.

7.7. IAW DoD 5105. 53(D), Director of Administration and Management, Special Command

Position (SCP) housing is occupied by a general officer or civilian equivalent and carries public

entertainment responsibilities requiring the incumbent to represent the interests of the United

States in official and social activities involving foreign and domestic dignitaries. Therefore, IAW

AFI 24-301, Vehicle Operations, paragraph 3.18, GOV use by TDY personnel (to include

invitational travel authorization travelers as passengers) to attend these official events is

authorized. SCP housing will be identified in the installation’s official use policy. Installation

Protocol office will be the point of contact for official events. 31 FW/CC residence is considered

SCP housing.

LANCE K. LANDRUM, Brigadier General, USAF

Commander


Attachment 1

GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION

References

31 U.S.C. §1344, Passenger Carrier Use

49 CFR, Part 571, Federal Motor Vehicle Safety Standards,1 October 2011

AABI 31-218, Motor Vehicle Traffic Supervision, 8 October 2015

AFI 23-101, Air Force Material Management, 5 May 2017

AFI 24-301, Vehicle Operations, 11 May 2017

AFI 24-302, Vehicle Management, 15 August 2017

AFI 32-6003, Gerneral Officer Quarters Management, 14 April 2016

AFI 90-802, Risk Management, 15 May 2017

AFI 91-207, Air Force Traffic Safety Program, 16 February 2017

AFMAN 23-220, Reports of Survey of Air Force Property, 1 July 1996

AFMAN 23-220_AVIANOABSUP, Reports of Survey of Air Force Property, 8 March 2017

AFMAN 33-363, Management of Records, 2 June 2017

AFMAN 33-363_USAFESUP, Management of Records, 13 April 2017

AFPAM 91-210, Contract Safety, 14 February 1994

AFPD 24-3, Management, Operation and Use of Transportation Vehicles, 9 October 2013

AFPD 64-1, The Contracting System, 1 May 2015

DoD 4500.36-R, Management, Acquisition, and Use of Motor Vehicles, 19 September 2017

DoD 5105.53(D), Director of Administration and Management, 26 February 2008

DoDI 6055.04, DoD Traffic Safety Program, 20 April 2009, Incorperating Change 2, 23 January

2013

Executive Order 13514, Federal Leadership in Environmental, Energy, and Economic

Performance. 5 October 2009

United States General Services Administration Federal Management Regulation 102-

34.130, License Plates, Last Reviewed 2 March 2015

Adopted Forms

AF Form 9, Request for Purchase

AF Form 20, Repair Costs and Repairable Value Statement

AF Form 2293, US Air Force Motor Vehicle Operator Identification Card

AF Form 847, Recommendation for Change of Publication

DD Form 518, Accident Identification Card


DD Form 200, Financial Liability Investigation of Loss

Standard Form 91, Motor Vehicle Accident Report

Abbreviations and Acronyms

AAFES—Army and Air Force Exchange Service

ATV—All Terrain Vehicle

CSC—Customer Service Center

DeCA—Defense Commissary Agency

DLA-DS—Defense Logistics Agency-Disposition Service

DOT—Department of Transportation

FM&A—Fleet Management and Analysis

GOV—Government Owned Vehicle

GPC—Government Purchase Card

GSU—Geographically Separated Unit

IPT—Integrated Product Team

LRS—Logistics Readiness Squadron

MEL—Minimum Essential List

MORD—Miscellaneous Obligation Reimbursement Document

NAF—Nonappropriated Funds

O&M—Operation and Maintenance

OGMVC—Other Government Motor Vehicle Conveyance

POR—Permissible Operating Range

POV—Privately Owned Vehicle

RA—Resource Advisor

ROS—Report of Survey

SCP—Special Command Position

SE&V—Support Equipment and Vehicles Division

TDY—Temporary Duty

UDI—U-Drive-It

U.S.C—United States Code

VCNCO—Vehicle Control Non-Commissioned Officer

VCO—Vehicle Control Officer

VFM—Vehicle Fleet Manager


VMS—Vehicle Management Superintendent

VSCOS—Vehicle Support Chain Operations Squadron


Attachment 2

EXAMPLES OF VEHICLE ABUSE

A2.1. Vehicle abuse action will be initiated for vehicle or vehicular equipment damage or

failure resulting from:

A2.1.1. Improper cargo distribution, failure to secure loads properly in cargo area of the

vehicle, or by not following established loading or unloading procedures.

A2.1.2. Using a vehicle for other than its intended or designed purpose (i.e., 6K F/L used to

transport a 10,000 pound pallet).

A2.1.3. Tampering with governors, distributors, or pollution control devices.

A2.1.4. Operating vehicles with insufficient oil or coolant, failure to check fluid levels

according to established requirements, failure to monitor dashboard instrumentation, and/or

failure to seek maintenance support for vehicle warning lights/messages.

A2.1.5. Operating vehicle with parking brakes applied.

A2.1.6. Failing to protect the painted surface(s) from corrosion and/or oxidation.

A2.1.7. Failure to clean, wax or maintain the interior or exterior of the vehicle, to meet

corrosion control and appearance requirements.

A2.1.8. Unauthorized wiring, marking, add-ons, or modification of a vehicle (add-ons and

modifications must be processed in writing through the VCO or VCNCO, the Vehicle

Operations Officer (VOO), and Vehicle Management for approval.

A2.1.9. Vehicle being operated by an unqualified or untrained operator without an instructor

present.

A2.1.10. Operating a vehicle with broken tire chains or improperly inflated tires; i.e., not

according to manufacturer recommendations.

A2.1.11. Tire wears beyond minimum acceptable safe tread depth. Tire wear that exposes

the cord renders tires unsuitable to be recapped or re-grooved and is unsafe.

A2.1.12. Intentional destruction or disfigurement of vehicle interior or exterior.

A2.1.13. Operating of a vehicle or equipment in conflict with published safety Department

of Defense (DoD) publication, Air Force Occupational Safety and Health (AFOSH),

Occupational Safety and Health Act (OSHA), Air Force instruction, Air Force Manual,

Technical Order, or Italian laws concerning vehicle safety.

A2.1.14. Allowing water to accumulate in the vehicle interior as a result of washing with a

hose, or the excessive accumulation of water from a storm due to leaving windows open.

A2.1.15. Over-filling the engine crankcase, transmission or hydraulic reservoirs.

A2.1.16. Servicing the vehicle fuel tank or hydraulic reservoir with incorrect fuel or oils.

A2.1.17. Not restraining doors when opening in excessive wind.

A2.1.18. Operating a vehicle in violation of guidance provided in the operator manual or

accepted driving practices.


A2.2. Other situations where vehicle abuse action may be initiated:

A2.2.1. Failure to report malfunctions, defects in, or damage to a vehicle to 31 LRS/LGRV

within 24 hours. A pre-approved delay of this action is authorized to satisfy immediate

mission needs.

A2.2.2. Failure to bring vehicle or equipment to 31 LRS/LGRV for scheduled maintenance

before an overdue condition exists. Prior to becoming overdue, pre-approved rescheduling

due to mission requirements is exempt.

A2.2.3. Failure to accomplish proper operator care and maintenance.

A2.2.4. Any other occurrence when the VFM/VMS, as the fleet management functional

expert, determine that damages caused are a result of abuse.

by order of the commander aviano air base instruction ... · 6 avianoabi24-302 5 january 2018...

Documents