afi21-101_pacafsup_yokotaabsup.pdf - Air Force

BY ORDER OF THE COMMANDER

YOKOTA AIR BASE

AIR FORCE INSTRUCTION 21-101

PACIFIC AIR FORCE

Supplement

YOKOTA AIR BASE

Supplement

15 JANUARY 2019

Maintenance

AIRCRAFT AND EQUIPMENT

MAINTENANCE MANAGEMENT

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

ACCESSIBILITY: Publications and forms are available for downloading or ordering on the e-

publishing website at www.e-Publishing.af.mil

RELEASABILITY: There are no releasability restrictions on this publication.

OPR: 374 MXG/MXQ

Supersedes: 374MXGOI 21-126, 5 Mar 2011;

374MXGOI 36-2232, 26 Jan 2011

374AWI 20-114, 19 Apr 2012;

374AWI 21-101, 22 May 2012;

374AWI 21-102, 27 Oct 2016;

374AWI 21-106, 10 Dec 2007;

374AWI 21-108, 29 May 2013;

374AWI 21-118, 19 Apr 2012;

374AWI 21-165, 3 Dec 2015;

374AWI 21-201, 17 Dec 2015;

374AWI 91-101, 31 Aug 2009;

YOKOTAABI 21-107, 19 May 2012;

YOKOTAABI 23-125, 13 May 2013;

374MXGOI 21-103, 15 Jun 2010;

374MXGOI 21-108, 15 May 2015;

374MXGOI 21-109, 12 Jun 2010;

374MXGOI 21-110, 01 Mar 2013;

374MXGOI 21-111, 3 Jan 2011;

374MXGOI 21-112, 1 Jul 2010;

74MXGOI 21-114, 30 Jan 2011;

374MXGOI 21-122, 14 Dec 2010; 374MXGOI 21-123, 30 Jan 2011;

374MXGOI 21-124, 31 May 2011;

374MXGOI 21-125, 30 Jan 2011;

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

2 AFI21-101_PACAFSUP_YOKOTAABSUP 15 JANUARY 2019

This supplement implements and extends the guidance of AFI 21-101, Aircraft and Equipment

Maintenance Management, and the PACAF supplement and applies to all Yokota Air Base

aircraft maintenance, trainer maintenance, and support equipment maintenance activities. This

publication is applicable to all units assigned to or a tenant of Yokota Air Base. Supplements to

this publication and the basic AFI are not required to be sent to the OPR for review unless they

have deviations. Ensure 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://afrims.amc.af.mil. 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; route AF Forms 847 from the field through the appropriate functional

chain of command. The use of the name or mark of any specific manufacturer, commercial

product, commodity, or service in this publication does not imply endorsement by the Air Force.

SUMMARY OF CHANGES

This supplement supersedes/consolidates 12 publications listed in above.

1.13.3. (Added-Yokota) Eating and drinking in the maintenance complex:

1.13.3.1. (Added-Yokota) Industrial areas are defined as any area of a facility where

maintenance is performed or industrial chemicals are used/stored.

1.13.3.2. (Added-Yokota) Personnel will take reasonable steps to clean hands of dirt and

industrial chemicals before handling or consuming food in the maintenance complex.

1.13.3.3. (Added-Yokota) Food brought into an industrial area will be in a closed or sealed

container and will be consumed only in a designated break area.

1.13.3.4. (Added-Yokota) All food or beverages brought onto the parking ramp that cannot be

resealed must be consumed in its entirety once opened and the containers disposed of

immediately.

1.13.3.5. (Added-Yokota) Re-sealable beverage containers may be used freely on the parking

ramp, inside aircraft, or in any other industrial area, but must remain sealed when not in use.

1.13.3.6. (Added-Yokota) Case-by-case waivers of these requirements for official functions

(retirements, bazaars, etc.) will be approved in writing by the facility’s Squadron Commander.

1.13.4. (Added-Yokota) Ladder Use. Per AFMAN 91-203, Air Force Consolidated

Occupational Safety Instruction, ladders will be laid down (not left upright) when unattended or

not actively being used. For Yokota AB flight line and maintenance areas, back shop or

otherwise, ladders are considered unattended or not in use when the user is 10 feet or more from

the ladder.

3.7.13. (Added-Yokota) Ensure download, processing, and upload of DTADS data IAW

Chapter 11 of this instruction.

3.10.6. (Added-Yokota) 374 AW Specific Munitions Load Guidance.

3.10.6.1. (Added-Yokota) General Policy and Responsibility.

https://afrims.amc.af.mil/

AFI21-101_PACAFSUP_YOKOTAABSUP 15 JANUARY 2019 3

3.10.6.1.1. (Added-Yokota) The Air Force provides explosives safety guidance in AFMAN 91-

201, Explosives Safety standards. This manual is an extension of DoD 6055.9M, and provides

further guidance for Air Force specific explosive safety issues.

3.10.6.1.2. (Added-Yokota) The 374th Maintenance Group Commander (374 MXG/CC) is

responsible for ensuring all known rules are followed within his/her command. Quality

Assurance assists him/her in these endeavors and must ensure compliance with all known

explosives safety technical orders, directives and standards.

3.10.6.2. (Added-Yokota) Mishap Notification and Emergency Actions.

3.10.6.2.1. (Added-Yokota) When a mishap occurs, involving explosives:

3.10.6.2.2. (Added-Yokota) Immediately notify the 374th Maintenance Operations Center

(MOC), which in turn follows the emergency action checklist.

3.10.6.2.3. (Added-Yokota) All nonessential personnel will be withdrawn to the minimum

distance required for the greatest munitions hazard present.

Table 3.1. (Added-Yokota) ADS Explosive Payload Limits per Aircraft.

Nomenclature Hazard Class/Division Fire Symbol Withdrawal Distance

M-206 Flare 1.3/G 3 600 ft.

MJU-50 Flare 4.2/G 3 600 ft.

M-211/MJU-64B

Flare

4.2/G 3 600 ft.

RR-170 Chaff 1.4/S 4 300 ft.

RR-188 Chaff 1.4/S 4 300 ft.

WARNING: If munitions are involved in a fire, do not use Halon, carbon dioxide or

water fire extinguishers on or near flares. Breathing apparatus is required for

firefighting personnel. These extinguishers may be used on surrounding areas.

Attempt to fight fire only if explosives are not directly involved.

3.10.6.3. (Added-Yokota) Procedures for Chaff/Flare Pre-load Checks.

3.10.6.3.1. (Added-Yokota) Munitions mission requirements will be identified in the weekly

flying schedule using the appropriate configuration code. Changes to the weekly flying schedule

requiring additional munitions support will require coordination using the AF Form 2407,

Weekly/Daily Flying Schedule Coordination.

3.10.6.3.2. (Added-Yokota) The 374 AMXS Production Superintendent will:

3.10.6.3.2.1. (Added-Yokota) Contact the MOC, munitions load team, and MXS Production

Superintendent no later than 1600 hours on the day prior to the mission to confirm the aircraft

tail number, aircraft location, and the required delivery time to the aircraft.

3.10.6.3.2.2. (Added-Yokota) Coordinate with the munitions load team to start the chaff/flare

pre-load checks prior to magazine delivery time.


3.10.6.3.2.3. (Added-Yokota) Coordinate with MXS Production Superintendent to ensure

munitions will be ready for delivery to the aircraft at the appropriate time.

3.10.6.3.3. (Added-Yokota) The load team will notify the AMXS Production Superintendent

when the pre-load checks are completed and the aircraft is ready to be loaded.

3.10.6.4. (Added-Yokota) Procedures for Requesting, Transporting and Uploading/Downloading

Chaff/Flare Modules.

3.10.6.4.1. (Added-Yokota) Authorized upload/download parking locations: The Yokota AB

flight line and all aircraft parking locations are authorized for uploading/downloading chaff/flare

provided that the quantity of munitions being loaded or unloaded is limited to a single aircraft

load. Vehicles parked for loading/unloading of munitions are considered in transit.

3.10.6.4.2. (Added-Yokota) Delivery times for chaff and flare loads will be coordinated

between the load team, AMXS Production Superintendent and MXS Production Superintendent

to assess the risks and hazards associated with seasonal weather patterns when determining chaff

and flare delivery times.

3.10.6.4.3. (Added-Yokota) Aircraft should normally be refueled before

uploading/downloading munitions. Aircraft refueling is authorized after munitions are installed

in aircraft.

3.10.6.4.4. (Added-Yokota) Explosives will be protected IAW AFMAN 91-201 and AFI 24-

301, Vehicle Operations.

3.10.6.4.5. (Added-Yokota) Drivers of vehicles that handle or transport explosives must be

trained using a lesson plan certified by Wing Safety (374 AW/SEW).

3.10.6.4.6. (Added-Yokota) The AMXS Production Superintendent will contact MXS

Production Superintendent and MOC to request delivery/pickup of munitions to/from the

aircraft.

3.10.6.4.7. (Added-Yokota) The Munitions Flight will contact the MOC when transportation of

munitions is started and completed.

3.10.6.4.8. (Added-Yokota) The load team will notify the MOC when munitions loading

operations are started and completed.

3.10.6.4.9. (Added-Yokota) The MOC will notify Base Operations and the Fire Department

(374 CES/CEF) when munitions transport is started/completed.

3.10.6.4.10. (Added-Yokota) The MOC will notify Base Operations, Fire Department, and

Security Forces (374 SFS) when upload/download is started and give the greatest fire symbol

posted. MOC will notify all flight line personnel of munitions upload/download operations,

identifying aircraft parking location and tail number/aircraft call-sign or generation line number

(contingencies).

3.10.6.4.11. (Added-Yokota) The load team, which will consist of a minimum of two qualified

technicians, will “secure” the munitions loading/unloading area with explosive operations signs

or cones. Load team members will remain vigilant throughout upload/download operations to

ensure nonessential personnel do not come within 50 feet of explosives upload/download

operations.


3.10.6.4.11.1. (Added-Yokota) Personnel Limits: One supervisor, four workers and one casual

observer.

3.10.6.4.11.2. (Added-Yokota) Casual observers are persons not normally part of an explosives

operation but who have duties that require their presence, such as quality assurance, medical,

safety or inspection personnel.

3.10.6.4.12. (Added-Yokota) If munitions are unloaded for quick maintenance actions,

exceeding no longer than 8 hours, munitions may be consolidated at the maintenance site. The

chaff/flare team will utilize ammo cans to store non-empty magazines, which will be placed

together at the edge of the work area, away from normal traffic routes. The magazines will be

secured with use of explosives operation cones at a minimum of a 25 foot radius. When re-

uploading the munitions, care will be taken to load magazines into the dispenser that they were

removed from, as recorded in the aircraft’s current AF Form 2434, Munitions Configuration and

Expenditure Document.

3.10.6.4.13. (Added-Yokota) All personnel performing explosives operations must be currently

trained on handling explosives IAW AFI 91-202, The US Air Force Mishap Prevention

Program.

3.10.6.4.14. (Added-Yokota) The following will not be conducted within 100 feet of munitions

uploading/downloading operations: Refueling/defueling, liquid oxygen servicing, aircraft radio

operations, or engine runs (300 feet if engine are run to maximum power).

3.10.6.4.15. (Added-Yokota) The loading team chief will provide a safety briefing before

munitions delivery is accomplished. As a minimum, it will contain:

3.10.6.4.15.1. (Added-Yokota) Firefighting procedures.

3.10.6.4.15.2. (Added-Yokota) Designated evacuation location and procedures.

3.10.6.4.15.3. (Added-Yokota) Steps to take for dropped or damaged explosives.

3.10.6.4.15.4. (Added-Yokota) Withdrawal distances.

3.10.6.4.15.5. (Added-Yokota) Any specific safety requirements for the explosives being

handled.

3.10.6.4.15.6. (Added-Yokota) Direction/briefing to remove watches, rings and all other

jewelry.

3.10.6.4.15.7. (Added-Yokota) Direction to not key radios, or utilize cellular devices, within

25 feet of electrically-primed munitions.

3.10.6.4.15.8. (Added-Yokota) Task assignment/responsibilities of load team members:

3.10.6.4.15.8.1. (Added-Yokota) The load crew supervisor will:

3.10.6.4.15.8.1.1. (Added-Yokota) Ensure applicable operational checks are current.

3.10.6.4.15.8.1.2. (Added-Yokota) Ensure stray voltage is accomplished prior to loading.

3.10.6.4.15.8.1.3. (Added-Yokota) Ensure safety standards are enforced.

3.10.6.4.15.8.1.4. (Added-Yokota) Ensure proper documentation is accomplished.

3.10.6.4.16. (Added-Yokota) The following safety precautions will be strictly adhered to:


3.10.6.4.16.1. (Added-Yokota) Personnel must ground themselves before handling electrically

primed munitions. Frequently re-accomplish this procedure during the uploading/downloading

operations.

3.10.6.4.16.2. (Added-Yokota) The wear of static-producing clothing such as 100% nylon,

rayon, wool or polyester is prohibited as an outer garment. Personnel will not put on or remove

garments while engaged in explosives operations. Gortex garments may be worn during

uploading/downloading operations. Green fleece jackets are prohibited during upload/download

operations.

3.10.6.4.16.3. (Added-Yokota) Explosives must never be carried in pockets, CTKs or tool

pouches.

3.10.6.4.16.4. (Added-Yokota) Personnel should avoid pointing electrically-primed munitions

toward themselves, others, vehicles or aircraft.

3.10.6.4.16.5. (Added-Yokota) Do not tumble, drag, throw or roll explosives or containers.

3.10.6.4.16.5.1. (Added-Yokota) If munitions are dropped 3 feet or less, response is at the

discretion of the load crew supervisor.

3.10.6.4.16.6. (Added-Yokota) Disassembly of any munition modules are prohibited.

3.10.6.4.16.7. (Added-Yokota) No radio frequency transmissions of any kind, including

cellular phones, will be made within 25 feet of the immediate area of explosives.

3.10.6.4.16.8. (Added-Yokota) Ensure adequate area lighting when uploading/downloading

explosives during hours of dusk/darkness.

3.10.6.4.16.9. (Added-Yokota) Discontinue all explosives uploading/downloading operations

when lightning is within 5 nautical miles and/or winds exceed 35 knots.

3.10.6.4.17. (Added-Yokota) Refer to TO 1C-130A-33-1-2 and TO 1C-130A-33-1-2CL-9 (C-

130E/H) or TO 1C-130J-33-1-2CL-1 and TO 1C-130J-33-1-2 (C-130J) for specific step-by-step

uploading and downloading procedures.

3.10.6.4.18. (Added-Yokota) Defensive system will meet the minimum mission requirement as

agreed upon by operations and maintenance personnel. Mispoll data will not exceed 10% of

individual inventories.

3.10.6.4.19. (Added-Yokota) If the number of mispolls exceeds 10% inventory, load crews

will verify proper installation of magazines and/or swap out magazines with 374 MXS Munitions

Flight, if mispolls persist. If mispolls still exceed the standard, the countermeasures dispenser

system (CMDS) will be troubleshot IAW applicable MDS fault isolation technical data. If

proper CMDS operation is assured, then load teams will request replacement munitions from

munitions flight.

3.10.6.4.20. (Added-Yokota) The aircraft armament placard and an AFTO Form 781A,

Maintenance Discrepancy and Work Document, “Info Note” will be used to annotate the type

and quantity of munitions loaded on the aircraft. This “Info Note” will include both the physical

quantity and the quantity reported by the CDU.

3.10.6.4.21. (Added-Yokota) The MOC will notify Base Operations, the Fire Department, and

Security Forces when upload/download is complete.


3.10.6.4.22. (Added-Yokota) The AMXS Expediter will notify MOC when loaded aircraft

depart/arrive parking spot.

3.10.6.4.23. (Added-Yokota) The MOC will notify Base Operations and the Fire Department

of explosives-loaded aircraft arrival to or departure from parking spot.

3.10.6.5. (Added-Yokota) Maintenance Precautions on Explosives-Loaded Aircraft.

3.10.6.5.1. (Added-Yokota) Aircraft are considered explosives-loaded when chaff or flares are

loaded in any part of the weapon system or being transported as cargo, and will be handled IAW

TO 11A-1-33, Handling and Maintenance of Explosives Loaded Aircraft - (ATOS), and AFMAN

91-201.

3.10.6.5.2. (Added-Yokota) Vehicles not directly involved with the explosives

uploading/downloading operation will remain at least 50 feet from explosives.

3.10.6.5.3. (Added-Yokota) Hangaring of chaff/flare loaded aircraft is prohibited IAW TO

11A-1-33.

3.10.6.5.4. (Added-Yokota) Wing Jacking and other maintenance that will affect aircraft

"Weight on Wheels” switch configuration is prohibited (chaff/flare must be downloaded).

3.10.6.5.5. (Added-Yokota) Functional Check Flights (FCF) with explosives are performed

only if the explosives are vital to the FCF.

3.10.6.5.6. (Added-Yokota) Maintenance that requires electrical power to the ADS equipment

will not be performed until the systems are “safed” by a qualified technician.

3.10.6.5.7. (Added-Yokota) Maintenance that will increase the probability of fire, explosives

release, etc., will not be performed. All maintenance actions on munitions loaded aircraft will be

coordinated through the Production Superintendent.

3.10.6.5.8. (Added-Yokota) If an unknown/hazardous condition is encountered, cease all

maintenance, evacuate personnel to the applicable safe distance as outlined in Table 1, and notify

the MOC.

3.10.6.6. (Added-Yokota) Procedures for Recovering and Downloading Explosives-Loaded

Aircraft.

3.10.6.6.1. (Added-Yokota) When an explosives-loaded aircraft is inbound, the MOC will

notify the AMXS Production Office. If a munitions download is required, the MOC will notify

the MXS Production Superintendent. In addition, if the system was armed during flight, the

MOC will coordinate with Command Post (374 AW/CP) to ensure the aircraft is inspected for

partially ejected flares prior to proceeding to normal parking.

3.10.6.6.2. (Added-Yokota) After landing, the aircraft will proceed to the “hammerhead” for

end of runway inspections by aircrew for partially ejected flares. If no partially ejected flares are

found, the aircraft may proceed to normal parking.

3.10.6.6.3. (Added-Yokota) If an uncommanded release of munitions occurs:

3.10.6.6.3.1. (Added-Yokota) Aircrew will perform all applicable partially ejected flare checks

at the hammerhead.


3.10.6.6.3.2. (Added-Yokota) If no partially ejected flare is discovered, the aircraft will taxi to

normal parking when cleared to do so.

3.10.6.6.3.3. (Added-Yokota) Upon arrival at the parking spot, the aircraft will be impounded

IAW Chapter 11 of this instruction. A thorough investigation will be performed by qualified

2A8X1X technician.

3.10.6.6.4. (Added-Yokota) If a partially ejected flare or unknown condition exists:

3.10.6.6.4.1. (Added-Yokota) Aircrew will notify the Command Post. The Command Post

will notify the Wing Safety, the Fire Department, and the MOC to respond to the aircraft. The

Command Post will then notify Yokosuka EOD.

3.10.6.6.4.2. (Added-Yokota) Engines will be shut down immediately and aircraft will be

chocked.

3.10.6.6.4.3. (Added-Yokota) Aircrew personnel will recheck that the ADS system is SAFE.

3.10.6.6.4.4. (Added-Yokota) Aircrew and all nonessential personnel will evacuate to a

minimum safe distance of 600 feet or as directed by the on scene commander.

3.10.6.6.5. (Added-Yokota) Normal operations require chaff/flare downloading after flight.

When the aircraft will fly subsequent missions requiring chaff/flares, the Production

Superintendent will determine if downloading is required.

3.10.6.6.5.1. (Added-Yokota) Load crews will coordinate with the 36th Airlift Squadron (36

AS)/Tactics to determine the maximum expenditures allowed before reconciliation of

chaff/flares is required.

3.10.6.6.6. (Added-Yokota) If downloading is required, the load team will repeat steps in

paragraph 4 of this instruction after the aircraft is recovered at normal parking.

3.10.6.6.6.1. (Added-Yokota) The load team will annotate AF Form 2434, Munitions

Configuration and Expenditure Document, with expenditures and provide a copy to the MXS

Munitions Flight.

3.10.6.6.6.2. (Added-Yokota) Munitions Flight personnel will account for all downloaded

modules prior to departure from the flight line. Discrepancies will be corrected prior to full

acceptance of modules by Munitions Flight. Full counts must match the AF Form 2434.

3.10.6.6.7. (Added-Yokota) Squib/Flare Misfire procedure:

3.10.6.6.7.1. (Added-Yokota) The flight crew or munitions load team will annotate the remarks

block of the AF Form 2434 if there are any misfires detected. The load team personnel will

attach the AF Form 2434 detailing which magazine number and which sequence number stick(s)

misfired.

3.10.6.6.7.2. (Added-Yokota) Munitions Flight personnel will inspect squib/flare misfires and

take appropriate actions deemed necessary by the Munitions Flight Chief and applicable TOs.

3.10.6.7. (Added-Yokota) Munitions Documentation Procedures:

3.10.6.7.1. (Added-Yokota) AFTO Form 781H, Aerospace Vehicle Flight Status and

Maintenance: Document the AFTO Form 781H, IAW TO 00-20-1-WA-1, Web Access -

Aerospace Equipment Maintenance Inspection, Documentation, Policy and Procedures.


3.10.6.7.2. (Added-Yokota) The aircraft armament placard will be used to annotate the

munitions physical count (e.g. 180 = CH, 360 = FL), and the date munitions were uploaded.

3.10.6.7.3. (Added-Yokota) AFTO Form 781A:

3.10.6.7.3.1. (Added-Yokota) Enter the following in the AFTO Form 781A, IAW TO 00-20-1-

:

3.10.6.7.3.1.1. (Added-Yokota) An AFTO Form 781A, Maintenance Discrepancy and Work

Document, “INFO NOTE” will be used to annotate the type and quantity of munitions loaded on

the aircraft. This “Info Note” will include both the physical quantity and the quantity reported by

the CDU, including specific quantity and type of munitions loaded as well as specific dispensers

locations if full load is not accomplished (e.g., “Info Note: 120 M-206 Flares loaded in nose

dispensers only, carry forward until downloaded” or “Info Note: 240 M-206, 240 M-211, 60 RR-

188 Chaff loaded, carry forward until downloaded.”)

3.10.6.7.3.2. (Added-Yokota) Enter the appropriate Red symbol/discrepancy in AFTO Form

781A, IAW TO 00-20-1: “Munitions upload/download required, IAW TO 1C-130A-33-1-2CL-9

or 1C-130J-33-1-2CL-1.”

3.10.6.7.3.3. (Added-Yokota) A qualified Red X munitions load personnel will clear the

discrepancy after munitions upload/download is complete.

3.10.6.7.4. (Added-Yokota) AF Form 2434:

3.10.6.7.4.1. (Added-Yokota) The following blocks will be annotated with applicable

information when the aircraft is loaded with munitions:

3.10.6.7.4.1.1. (Added-Yokota) “Page x of y”

3.10.6.7.4.1.2. (Added-Yokota) “Unit”

3.10.6.7.4.1.3. (Added-Yokota) Enter aircraft tail number in Column 1, “ACFT SERIAL NO.”

3.10.6.7.4.1.4. (Added-Yokota) Enter MSCL configuration code in Column 2,

“CONFIGURATION CODE.”

3.10.6.7.4.1.5. (Added-Yokota) Enter dispenser loaded in Column 3, “ACFT STA.”

3.10.6.7.4.1.6. (Added-Yokota) Enter module serial number (i.e., Y301) in Column 4,

“LAUNCHER / RACK / SSU S/N.”

3.10.6.7.4.1.7. (Added-Yokota) Enter the specific module quantity of munitions loaded in

Column 5, “MUNITIONS, QTY LOADED.”

3.10.6.7.4.1.8. (Added-Yokota) Enter the specific type of munitions loaded in Column 6,

“MUNITIONS, TYPE”, (e.g., M-206).

3.10.6.7.4.1.9. (Added-Yokota) Enter the specific module quantity of installed impulse

cartridges in Column 11, “IMPULSE CARTS, QTY INST.”

3.10.6.7.4.1.10. (Added-Yokota) Enter the type of impulse cartridges installed in Column 12,

“IMPULSE CARTS, TYPE.”

3.10.6.7.4.2. (Added-Yokota) The following blocks will be annotated with applicable

information when munitions are downloaded from the aircraft:


3.10.6.7.4.2.1. (Added-Yokota) Enter the specific quantity of munitions expended from

applicable modules in Column 7, “MUNITIONS, QTY EXPENDED.”

3.10.6.7.4.2.2. (Added-Yokota) Enter the specific quantity of impulse cartridges expended

from applicable modules in Column 13, “IMPULSE CARTS, QTY EXP.”

3.10.6.7.4.2.3. (Added-Yokota) Enter any chaff/flare misfire information in Column 17,

“REMARKS.”

3.10.6.7.4.2.4. (Added-Yokota) Enter the date the munitions were downloaded in “DATE”

block.

3.10.6.7.4.3. (Added-Yokota) An authorized member will sign the AF Form 2434 and send a

copy to Munitions Flight org box: FV5209.

3.10.6.8. (Added-Yokota) Training Requirements and Documentation:

3.10.6.8.1. (Added-Yokota) Load team members will accomplish the following training:

3.10.6.8.1.1. (Added-Yokota) Explosives Safety IAW AFMAN 91-201.

3.10.6.8.1.2. (Added-Yokota) C-130 Munitions Loading Academic and Practical training from

a qualified WTQC/WTQM.

3.10.6.8.2. (Added-Yokota) Load Team Supervisor Prerequisites: 6 months as load team

member, perform at least one aircraft chaff/flare load, and be at least a 5-level 2A8X1X

technician or a 7-level chaff/flare qualified personnel.

4.10.1. (Added-Yokota) Munitions Accountability.

4.10.1.1. (Added-Yokota) General. The procedures in this instruction will be used to account

for countermeasure munitions during day-to-day operations, exercises, contingency operations

and deployments. All flying squadrons (or aircraft maintenance squadrons as applicable) under

374 AW control and Air Mobility Command (AMC) deployed units will follow the procedures

outlined in this instruction if home station accountability procedures are not available.

Accountability of munitions is a coordinated effort between all parties having access to

munitions. All personnel must take an active role to ensure that accurate documentation and

timely processing are achieved.

4.10.2. (Added-Yokota) Responsibilities:

4.10.2.1. (Added-Yokota) The Munitions Accountable Systems Officer (MASO) will:

4.10.2.1.1. (Added-Yokota) Resolve accountability discrepancies that cannot be resolved by

the 374th Aircraft Maintenance Squadron (374 AMXS) and coordinate with AMXS leadership

on corrective actions taken to resolve accountability discrepancies.

4.10.2.1.2. (Added-Yokota) Resolve requests for munitions not identified on the weekly

schedule (e.g., short notice requirements).

4.10.2.1.3. (Added-Yokota) Coordinate all munitions policy changes that impact the 36th

Airlift Squadron (36 AS) operations through the Wing Weapons Officer for review and

distribution to the 36 AS Weapons Officer.

4.10.2.1.4. (Added-Yokota) Routinely coordinate with AMC munitions personnel for

accountability of AMC munitions.


4.10.2.1.5. (Added-Yokota) Ensure receipt of AF Form 2434, Munitions Configuration and

Expenditure Document, from Munitions Load Team personnel for all aircraft loaded with

munitions no later than (NLT) three hours after the last aircraft lands for the flying day or

2400hrs for 24-hr flying operations.

4.10.2.2. (Added-Yokota) The Munitions Flight will:

4.10.2.2.1. (Added-Yokota) Coordinate with the Wing/Squadron Weapons Officers or

Wing/Squadron Electronic Countermeasures Officers (ECOs) to ensure all required munitions

are available for the mission and monitor levels of assembled munitions to support weekly flying

requirements.

4.10.2.2.2. (Added-Yokota) Notify the Wing/Squadron Weapons Officers or Wing/Squadron

ECOs, and 374 MXS/CC if countermeasure munitions are not available or are determined to be

unserviceable and will affect the ability to generate aircraft in support operational taskings.

4.10.2.2.3. (Added-Yokota) Ensure requests for munitions that cannot be fulfilled through

normal scheduling are coordinated through the Munitions Flight Chief and MXS Maintenance

Operations Officer/Chief.

4.10.2.2.4. (Added-Yokota) Ensure an AF Form 2407, Weekly/Daily Flying Schedule

Coordination, is generated for changes to the weekly flying schedule affecting munitions

requirements. The Munitions Flight will not deliver munitions until a completed AF Form 2407

is received. This includes contingency, exercise, and short-notice training mission.

4.10.2.2.5. (Added-Yokota) Ensure all AF Forms 2407 are signed and approved by the

Operations Scheduling Officer and the MXS Production Superintendent or higher.

4.10.2.2.6. (Added-Yokota) Ensure munitions allocations are not exceeded.

4.10.2.2.7. (Added-Yokota) Ensure all countermeasure munitions required to support the

flying schedule are assembled and ready for delivery.

4.10.2.2.8. (Added-Yokota) Assign separate color codes for each Weapon Stock Number

(WSN) assembled to facilitate visual inspection for accountability purposes.

4.10.2.2.9. (Added-Yokota) Document all countermeasure munitions builds on locally devised

build sheets (may be electronic). The build sheets will include build quantity, WSN, color code,

component lot numbers, and shelf/service life date information.

4.10.2.2.10. (Added-Yokota) Store all assembled countermeasure munitions to include in

transit countermeasures.

4.10.2.2.11. (Added-Yokota) Notify Maintenance Operations Center (MOC) and/or Air

Mobility Control Center (AMCC), as applicable, for all munitions movements to and from the

flightline.

4.10.2.2.12. (Added-Yokota) Ensure all munitions delivered to the flightline are signed for by

personnel authorized in writing on the “Authorization to Sign for C-130 Defensive System

Munitions” letter signed by the 374 AMXS/CC.

4.10.2.2.13. (Added-Yokota) Document all munitions movements to and from the flightline on

an AF Form 4331, Munitions Transaction Sheet.

4.10.2.2.14. (Added-Yokota) Be the focal point for munitions reconciliation.


4.10.2.2.15. (Added-Yokota) Chaff/flare magazines will be processed for expenditures upon

return to the munitions processing facility. Munitions Flight personnel will certify chaff/flare as

expended and verify physical quantities against the AF Form 2434 received from Munitions

Load Team personnel.

4.10.2.2.16. (Added-Yokota) Once expenditures have been certified, Munitions Flight

personnel will remove the squibs from expended chaff/flare and place expended squibs in the

appropriate container. Expended chaff/flare sticks will be placed in a separate container.

4.10.2.2.17. (Added-Yokota) Ensure reconciliation of expended countermeasures returned

from aircraft is accomplished as expediently as possible, but must be completed within three

hours of aircraft landing.

4.10.2.2.18. (Added-Yokota) Freeze all countermeasure munitions assets if any

countermeasure munitions are unaccounted for. The Munitions Flight Chief and MXS

Maintenance Operations Officer/Chief will be contacted immediately when any countermeasure

munitions cannot be accounted for. The Munitions Flight Chief will coordinate with the AMXS

Production Superintendent to ensure every effort is made to account for the missing item(s). At

the Munitions Flight Chief’s discretion, the assets will be unfrozen if the items are found or if it

is concluded that the item(s) is/are not recoverable. For accountability purposes, AMXS is

required to provide an incident report to the Munitions Flight as soon as possible, but NLT two

working days after incident.

4.10.2.2.19. (Added-Yokota) Tag unserviceable magazines with an AFTO Form 350,

Repairable Item Processing Tag, and return the magazine to the owning unit for repair or

disposition.

4.10.2.3. (Added-Yokota) Aircraft Maintenance Squadrons as applicable under 374 AW

control will:

4.10.2.3.1. (Added-Yokota) When making any changes to the flying schedule, coordinate

changes using an AF Form 2407 before requesting delivery of any countermeasure munitions.

Accomplish and coordinate the changes as soon as possible to ensure assets are on hand,

assembled and configured properly to support the request.

4.10.2.3.2. (Added-Yokota) Provide the Munitions Flight a copy of the AF Form 2407 with the

aircraft tail number, required quantities, load configurations and date/time required.

4.10.2.3.3. (Added-Yokota) Control their chaff/flare magazines and ALE-47, Counter Measure

Dispenser System (CMDS), series. They are the physical property of the aircraft maintenance

squadrons (flying squadrons in some cases), including AMC intransit aircraft. The maintenance,

repair and replacement are the responsibility of the owning organization. The Munitions Flight

will replace defective breech plates as long as the owning organization provides replacements.

4.10.2.3.4. (Added-Yokota) Notify the Munitions Flight of all munitions deploying on cross-

country missions or diverted aircraft. Ensure all munitions requirements for local training and

deployments are coordinated through the Munitions Flight at least 30 days prior to use.

4.10.2.3.5. (Added-Yokota) Notify the Munitions Flight of all munitions allocation transfers

required for use at TDY locations. Ensure the Munitions Flight is notified at least 90 days prior

to use to ensure proper coordination can be completed in time.


4.10.2.3.6. (Added-Yokota) As required, ensure a Squadron Weapons Officer/ECO or

representative attends the weekly flying scheduling meeting to verify munitions requirements.

4.10.2.4. (Added-Yokota) AMXS Maintenance Supervision (this includes any personnel

assigned chaff/flare load duties) will:

4.10.2.4.1. (Added-Yokota) Ensure all personnel handling countermeasure munitions are

trained and certified in the appropriate tasks they will perform, to include explosive safety,

identification and documentation of expended munitions, munitions accountability and the

handling of loaded countermeasure munitions magazines.

4.10.2.4.2. (Added-Yokota) Ensure only those aircraft identified on the flying schedule are

loaded with countermeasure munitions. Notify the Munitions Flight and MOC prior to

performing any cross loads. AMXS load crews will not cross load countermeasure munitions to

aircraft not on the flying schedule or AF Form 2407.

4.10.2.4.3. (Added-Yokota) Identified AMXS load crew personnel will verify the quantity,

WSN and type of munitions are annotated correctly on the AF Form 4331. Once verified as

correct, they will sign the AF Form 4331 transferring accountability from the Munitions Flight to

load crew personnel.

4.10.2.4.4. (Added-Yokota) Track all munitions loaded on aircraft by tail numbers, type, and

quantity.

4.10.2.4.5. (Added-Yokota) Complete and sign AF Form 2434 detailing aircraft number,

magazine numbers, type of munitions, quantity loaded, and expenditure data at the end of the

flying day. Ensure the Munitions Flight receives all copies of the AF Form 2434 NLT three

hours after the last aircraft land time for the day or midnight for 24-hr flying operations.

4.10.2.4.6. (Added-Yokota) Annotate the remarks block of the AF Form 2434 if there are any

misfires detected. When misfires are detected, AMXS load crew personnel will attach a locally

devised product detailing the magazine to identify which stick(s) misfired.

4.10.2.4.7. (Added-Yokota) Download all chaff/flare magazines with expenditures as required

based on expenditure limits established by the Wing/Squadron Weapons Officer/ECO. Call

MXS Production Superintendent (SUMO 10) for magazine pickup and re-supply by the

Munitions Flight.

4.10.2.4.8. (Added-Yokota) Immediately notify the Munitions Flight of any munitions

determined to be unserviceable. Note: Unsafe munitions will only be handled by qualified

Explosive Ordnance Disposal (EOD) personnel IAW AFMAN 91-201, Explosives Safety

standards.

4.10.2.5. (Added-Yokota) MXS Maintenance Supervision will:

4.10.2.5.1. (Added-Yokota) Attend the weekly flying scheduling meetings to coordinate

countermeasure munitions support requirements.

4.10.2.5.2. (Added-Yokota) Ensure the Munitions Flight has the capability to support changes

to the flying schedule prior to approving AF Form 2407.

4.10.2.6. (Added-Yokota) The MXS Production Superintendent (SUMO 10) will:


4.10.2.6.1. (Added-Yokota) Notify the Munitions Flight when munitions are to be delivered or

picked up. Report aircraft tail number (as permitted), parking location, type of munitions (e.g.,

chaff/flare), configuration (MSCL), and quantity of munitions to be picked up or delivered.

4.10.2.6.2. (Added-Yokota) Ensure the Munitions Flight has the capability to support changes

to the flying schedule prior to approving AF Form 2407.

4.10.2.7. (Added-Yokota) The Squadron Weapons Officer/Squadron ECO will:

4.10.2.7.1. (Added-Yokota) Attend the weekly flying scheduling meeting, as required.

4.10.2.7.2. (Added-Yokota) Coordinate, in writing, all allocation transfer requests through the

Wing Weapons Officer or Wing ECO to the Munitions Flight at least 90 days before the

necessary in place date.

4.10.2.7.3. (Added-Yokota) Work closely with the Munitions Flight to ensure all munitions

requirements are met.

4.10.2.8. (Added-Yokota) The Wing Weapons Officer/Wing ECO will:

4.10.2.8.1. (Added-Yokota) As required, attend the weekly wing flying scheduling

meeting/scheduling meeting or appoint a designated representative to do so.

4.10.2.8.2. (Added-Yokota) Contact the Munitions Flight to ensure munitions allocation is not

exceeded and pass this information to the flying squadrons.

4.10.2.8.3. (Added-Yokota) Be the sole source for resolving all issues concerning aircrew

training munitions allocations.

4.10.2.8.4. (Added-Yokota) Work closely with the Munitions Flight to ensure all munitions

requirements are met.

4.10.3. (Added-Yokota) Procedures. Elements and individuals that work with countermeasure

munitions will use the following procedures:

4.10.3.1. (Added-Yokota) Delivery:

4.10.3.1.1. (Added-Yokota) Munitions Load Team personnel request delivery through SUMO

10. The Munitions Flight will then dispatch the requested countermeasure munitions to the

flightline. Munitions personnel will annotate the munitions delivery on the AF Form 4331 and

ensure only authorized personnel sign for munitions.

4.10.3.2. (Added-Yokota) Return:

4.10.3.2.1. (Added-Yokota) Munitions Load Team personnel will download expenditures as

required based on expenditure levels established by the Wing/Squadron Weapons Officer. When

magazines are downloaded, the Munitions Load Team will complete an AF Form 2434 with

expenditure information as stated in paragraph 3.10.2.6.

4.10.3.2.2. (Added-Yokota) Munitions Load Team personnel will inform SUMO 10 when

assets are ready for pick up. The Munitions Flight will then return all downloaded munitions

from the flightline back to the MSA for processing.

4.10.3.3. (Added-Yokota) Reconciliation:


4.10.3.3.1. (Added-Yokota) Countermeasures will be reconciled when returned to the

munitions processing facility. Reconcile countermeasure munitions using the following

procedures:

4.10.3.3.2. (Added-Yokota) The Munitions Flight will return all downloaded magazines to the

MSA for inspection and verification against the AF Form 2434 received from Munitions Load

Team personnel.

4.10.3.3.3. (Added-Yokota) Upon return to the MSA, the munitions will be 100% inspected for

expenditures by munitions personnel. If a discrepancy between actual expenditures and AF

Form 2434 is discovered, Munitions Flight personnel will contact AMXS Production

Superintendent to rectify the discrepancy.

4.10.3.3.4. (Added-Yokota) Upon completion of reconciliation, the munitions inspector will

clear expenditures from the worktable.

4.10.3.3.5. (Added-Yokota) Chaff/flare will be expended from the CAS database using

procedures outlined in AFI 21-201, Munitions Management.

4.10.3.3.6. (Added-Yokota) During extended downtime of CAS during contingencies, the

Munitions Flight will follow established Post-Post procedures to track munitions transactions.

4.10.4. (Added-Yokota) Operations.

4.10.4.1. (Added-Yokota) General. The following process will be utilized to demonstrate

build, delivery, and load capabilities for generation of C-130 aircraft. This process will allow the

demonstration of the entire process of munitions handling regardless of number of tasked aircraft

during an exercise or inspection scenario, while at the same time maximizing the countermeasure

allocation.

4.10.4.1.1. (Added-Yokota) All aircraft generation MSCL requirements will utilize the training

allocation MSCL 131 to the max extent possible based on current on-hand allocation quantities.

One aircraft load will be utilized for simulated generation of additional aircraft as well as all

required resupply based on ATO requirements.

4.10.4.1.2. (Added-Yokota) During the simulated load actions the countermeasures will be

delivered to the aircraft and transferred to ECM personnel who will wait the allotted time (1

hour) prior to uploading of subsequent aircraft. During this time no other maintenance will be

conducted on the aircraft. Munitions personnel will then be called to transport munitions to next

aircraft for simulated load actions until generation is complete.

4.10.4.1.3. (Added-Yokota) The source document for munitions requirements during

generation will be the 374 MXG Form 2409. The training MSCL will be located in the

configuration block on the 2409 with the real world/exercise MSCL requirement being simulated

in parenthesis. This process will also be followed when documenting ATO requirements via the

AMT or daily schedule.


Figure 4.1. (Added-Yokota) Generation Flow Plan (Exercise and Contingency).

WARORD Received

374 OSS ECO determines threat and appropriate MSCL for acft.

MASO contacts 374 OSS ECO to determine required MSCL.

MASO validates training/operational MSCL is available and in what quantities.

Munitions Flight validates breakout plan.

PTDO Received

374 OSS ECO validates threat and appropriate MCSL for aircraft. MASO contacts 374

OSS ECO to validate MSCL for threat assessment.

MASO validates training/operational MSCL is available and in what quantities.

Munitions Flight begins build-up of required aircraft countermeasures.

DEPORD Received

Aircraft generation begins.

MASO briefs current status of aircraft countermeasures to MXG prescribed meeting.

Ronin 10 request aircraft countermeasures as required based on generation timelines.

Munitions Flight contacts MOC prior to movement from the MSA to the flightline.

Munitions Load Team personnel validates MSCL against AF IMT 4331 provided by

Munitions Flight personnel.

Aircraft countermeasures are loaded on all applicable aircraft based on tasking.

5.2.5.3.5.1.1. (Added-Yokota) Accurate and timely data is essential for monitoring the

reliability and maintainability of weapons systems. Data reported will be accumulated, stored

and used for health of force indicators, special studies, and to help identify which systems and

components consume the most time and money. The data provides historical reference for future

studies and is used for developing and validating command standards and goals. DIT charter is to

ensure the accuracy of maintenance documentation at unit level. Its main objective is to ensure

accuracy, and educate managers and technicians concerning proper documentation practices and

procedures. The group's goal is to maintain an error rate less than three percent before

corrections and zero percent after corrections. Individuals/agencies initiating the maintenance

documentation input(s) into G081 are responsible for its accuracy and completeness.

Maintenance Data Systems Analysis (MDSA) will not correct or enter data into G081.

5.2.5.3.5.1.2. (Added-Yokota) The DIT consists of a Maintenance Data Systems Analysis

representative and representatives from each applicable work center. DIT representatives will be

selected and appointed in writing within each squadron by appropriate supervision. Selected

members should perform their duties within their respective sections for the entire period.

Recommended tenure length of selected members is at least 6 months with a 1-week turnover at

the end of that period for continuity purposes. Representatives will: be at least a 5 skill-level, be

familiar with the unit’s assigned weapon system(s), have a minimum of 6 months concurrent

experience with G081, and have reviewed the DIT Training slides provided by the DIT Manager


assigned to the Maintenance Analysis section. Participation is also required from 374

Maintenance Operations Squadron Plans Scheduling & Documentation, Maintenance Operations

Center, Engine Management Branch, Debrief, and Quality Assurance (QA) on an as needed

basis, as determined by analysis.

5.2.5.3.5.3.1. (Added-Yokota) The Maintenance Group Commander, Maintenance Group

Deputy Commander or a designated representative will chair the monthly DIT meeting.

5.2.5.3.5.6. (Added-Yokota) Responsibilities.

5.2.5.3.5.6.1. (Added-Yokota) Maintenance Data Systems Analysis office will:

5.2.5.3.5.6.1.1. (Added-Yokota) Follow guidance as specified in this instruction and TO 00-

20-2, which gives specific requirements for data integrity and reporting.

5.2.5.3.5.6.1.2. (Added-Yokota) Maintain responsibility for the overall management of the DIT

program. The DIT manager or Analysis section will host the monthly DIT meetings and will be

available to answer or clarify questions.

5.2.5.3.5.6.1.3. (Added-Yokota) Maintain the DIT member roster by work center.

5.2.5.3.5.6.1.4. (Added-Yokota) Work with the DIT members to consolidate reports. Produce

weekly reports for supervision and a monthly briefing/report for the MXG and Mobility Air

Forces identifying any trends as required.

5.2.5.3.5.6.1.5. (Added-Yokota) Run the appropriate G081 products every Tuesday by COB

for distribution/pickup.

5.2.5.3.5.6.1.6. (Added-Yokota) Allow 5 days for work center representatives to correct

identified errors and to return the report to MDSA.

5.2.5.3.5.6.1.7. (Added-Yokota) Review all errors found by the work centers for correction

through applicable G081 screens.

5.2.5.3.5.6.1.8. (Added-Yokota) Periodically spot check Job Data Documentation (JDD)

reviewed by work centers to ensure DIT members are properly documenting and correcting

maintenance.

5.2.5.3.5.6.1.9. (Added-Yokota) Research, identify and recommend corrective actions to

problems involving the DIT process and work center difficulties when completing reviews and

corrections.

5.2.5.3.5.6.1.10. (Added-Yokota) Conduct DIT meetings to educate the units on the

importance of data integrity and on new improvements to the minutes. Record and distribute

minutes.

5.2.5.3.5.6.1.11. (Added-Yokota) Once a week review and compare pulled aircraft forms. A

minimum of one aircraft per week will be checked, ensuring 100 percent coverage of all aircraft

each year.

5.2.5.3.5.6.2. (Added-Yokota) Squadron Data Integrity Team Members will:

5.2.5.3.5.6.2.1. (Added-Yokota) Be appointed in writing and appointment letters forwarded to

the MDSA office.


5.2.5.3.5.6.2.2. (Added-Yokota) Follow guidance as specified by this instruction and TO 00-

20-2, which gives specific requirements for data integrity and reporting.

5.2.5.3.5.6.2.3. (Added-Yokota) Review G081 JDD products run by MDSA. At a minimum,

check for proper documentation.

5.2.5.3.5.6.2.4. (Added-Yokota) Correct any JDD errors discovered during the DIT review.

The work center will complete all corrections within 5 days of the information being published.

The corrections will be completed utilizing G081 screen 9056.

5.2.5.3.5.6.2.5. (Added-Yokota) Ensure DIT representatives from each work center attend DIT

meetings. This will allow for the squadron DIT representative to brief their respective

supervision, prior to briefing 374 MXG/CC.

5.2.5.3.5.6.2.6. (Added-Yokota) During review or correction, notify MDSA within 24 hours if

there are any problems encountered with G081 that are beyond the end user’s capability. Work

centers who fail to notify MDSA prior to the weekly rates being calculated may not be credited

with the correction.

5.2.5.3.5.6.2.7. (Added-Yokota) Ensure AFTO Forms 781A and Maintenance Information

System (MIS) documentation are accurately accomplished; data entry of one should be in the

other unless exemptions to JDD reporting have been established by MAF. If data does not

reflect the same from both source documentations, the responsible work center will be charged

with a JDD error and have it included in the DIT error rate.

5.2.5.3.5.6.2.8. (Added-Yokota) Train and keep the work center alternates informed on all

issues concerning their squadron’s documentation data.

5.2.5.3.5.6.3. (Added-Yokota) Squadron Work Center Supervisors will:

5.2.5.3.5.6.3.1. (Added-Yokota) Designate in writing, work center DIT representatives and

ensure MDSA receives a copy. Each squadron should provide at a minimum, two formal DIT

members, one primary and one alternate.

5.2.5.3.5.6.3.2. (Added-Yokota) Prior to the end of each shift, check G081 screen 8063 to

ensure all closed discrepancies are updated with JDD.

5.2.5.3.5.6.3.3. (Added-Yokota) During JDD reviews, ensure only the most accurate and

specific codes are used to identify and close out discrepancies in G081 (Reference TO 1C-130A-

06 and TO 00-20-2, para 3-4).

5.2.5.3.5.6.3.4. (Added-Yokota) Ensure all ground found aircraft maintenance actions are

documented in G081.

5.2.5.3.5.6.3.5. (Added-Yokota) Ensure errors found in the weekly DIT checks are corrected in

G081 and returned to MDSA within 5 days.

5.2.5.3.5.6.3.6. (Added-Yokota) Report number of forms reviewed and number of jobs not

loaded in G081 to the DIT chairperson.

5.2.5.3.5.6.4. (Added-Yokota) Aircraft Maintenance Squadron and Maintenance Squadron

supervision (as applicable) will:


5.2.5.3.5.6.4.1. (Added-Yokota) Ensure aircraft/equipment status, as reflected in the applicable

maintenance forms, is reported in the MIS and maintenance actions are properly documented

IAW AFI 21-101_AMCSUP, paragraph 3.9.8.

5.2.5.3.5.6.4.2. (Added-Yokota) Ensure AFTO Forms 781A and MIS documentation are

accurately accomplished; data entry of one should be in the other unless exemptions to JDD

reporting have been established by MAF. Examples include: mismatch of write-up in forms

versus G081, signed off in forms but not closed in G081, completed in G081 but not signed off

in forms, no JCN in forms or corrective action in G081 does not match what is in forms.

5.2.5.3.5.6.4.3. (Added-Yokota) Ensure Quality Assurance (QA) 781 findings are corrected

and provide remedial training as needed.

5.2.5.3.5.6.5. (Added-Yokota) Quality Assurance (QA) will:

5.2.5.3.5.6.5.1. (Added-Yokota) Designate a primary and alternate DIT member in writing and

ensure MDSA receives a copy.

5.2.5.3.5.6.5.2. (Added-Yokota) Complete a special inspection of active aircraft forms against

G081 to ensure that AFTO Forms 781A and MIS documentation are complete, accurate and

accomplished. When the two differ, the responsible work center will be charged with an error

and have it included in JDD error rate. Examples include: mismatch of write-up in forms versus

G081, signed off in forms but not closed in G081, completed in G081 but not signed off in

forms, no JCN in forms or corrective action in G081 does not match what is in forms. A 14-day

records check doesn’t cover this requirement. A minimum of one aircraft forms per week should

be checked, ensuring 100 percent coverage of all aircraft each year.

5.2.5.3.5.6.5.3. (Added-Yokota) Ensure monthly aircraft 781A error rates are provided to

MDSA no later than the third workday of each month. These inputs include, but are not limited

to, the number of “Aircraft Forms Reviewed” and “Jobs in Forms but not in G081,” and are

needed for inclusion in the monthly report.

5.2.5.3.5.7. (Added-Yokota) The Maintenance Analysis Section will brief current error rates

and problem areas to the MXG/CC and organizations as required. The MDSA will maintain

historical records of error rates for each maintenance organization in the wing.

5.3.4. (Added-Yokota) 374 AW Specific Maintenance Training guidance:

5.3.4.1. (Added-Yokota) Waivers. Requests to deviate from this instruction will be forwarded

to the 374 MXG/CC. Approved changes will be made by the Maintenance Training Section

(MTS).

5.3.4.2. (Added-Yokota) MTS class cancellation policy.

5.3.4.2.1. (Added-Yokota) MTS class cancellation requests will be routed through the UTM to

be coordinated with the MTS Section Chief, as determined by mission requirements. Final

cancel authority is the MXG/CC. If cancelled, the MTS will notify all scheduled personnel.

5.3.4.2.2. (Added-Yokota) Removing scheduled personnel from a training event in G081 that

causes the class to go below student minimums will require unit commander justification and

approval of the MXG/CC.

5.3.4.3. (Added-Yokota) MTS Testing.


5.3.4.3.1. (Added-Yokota) MTS will administer all tests in the MTS learning center computers

from 0630-0800 and 1500-1630 Monday thru Friday. MTS test sessions must be coordinated

through the unit’s assigned UTM/ADUTM or by calling DSN 225-9130.

5.3.4.3.2. (Added-Yokota) Outside materials will not be allowed inside the testing room.

5.3.4.3.3. (Added-Yokota) Engine Run Test. Upon completion of the initial and/or annual

engine run test, an electronic AF Form 2426, Training Request and Completion, will be sent to

member’s unit by the MTS test proctor. The Form 2426 will identify appropriate course codes

(initial/annual certification). A certifying official must observe the individual performing an

engine run and document pass or fail on the Form 2426. The certifier will sign the Form 2426

and route it to their Unit Training Manager (UTM). Members must pass the certifier evaluation

within 30 days of the test.

5.3.4.3.3.1. (Added-Yokota) Upon the first unsatisfactory score on an engine run test, the MTS

will notify trainee’s flight supervision and UTM of the failure. The member who failed the test

will report to the work center supervisor for additional training IAW AFI 21-101, paragraph

11.17.5.1.7. Members cannot retake the test until 24 hours have passed.

5.3.4.3.3.2. (Added-Yokota) Upon second failure, the MTS will send an email memorandum to

trainee’s flight supervision and UTM. The member will be decertified IAW 21-101, paragraph

11.17.6.3. The SQ/CC (or equivalent) must provide the MTS a MFR authorizing the member to

retest and continue in the program IAW AFI 21-101, paragraph 11.17.5.1.9.

5.3.4.4. (Added-Yokota) G081 training subsystem management.

5.3.4.4.1. (Added-Yokota) G081 will not be used to track ancillary training already tracked by

the Advanced Distributed Learning Service (ADLS).

5.3.4.4.2. (Added-Yokota) The MTS will:

5.3.4.4.2.1. (Added-Yokota) Be the single POC for the G081 training subsystem.

5.3.4.4.2.2. (Added-Yokota) Schedule and update all Aircraft Maintenance Qualification

Program (AMQP) class events and students.

5.3.4.4.3. (Added-Yokota) Unit Training Managers (UTM) will update completed training

accomplished within their squadron using appropriate source documents (completion certificates,

signed AF Form 2426/Form 64).

5.3.4.5. (Added-Yokota) Frequency and distribution of G081 products.

5.3.4.5.1. (Added-Yokota) Training Forecasts are available for download by all personnel at

the Global Reach Logistics website (https://amclg.csd.disa.mil/). The site is refreshed daily.

5.3.4.5.2. (Added-Yokota) MTS/FTD open seat rosters will be provided to UTMs monthly by

the MTS Scheduling section.

5.3.4.5.3. (Added-Yokota) Special Certification Roster (SCR). This roster is the record for

tasks requiring certification and inspector authorizations and will be sent to each squadron

superintendent and Quality Assurance (374 MXG/QA) quarterly. Superintendents will annotate

any SCR addition/deletions required. When a new SCR is generated, superintendents will verify

all the updates are reflected on the new report.

https://amclg.csd.disa.mil/


5.3.4.5.4. (Added-Yokota) Work Center Training Requirements Report. This report shows all

courses identified as mandatory for work center members. It will be refreshed semi-annually and

sent to work center supervisors. Work center supervisors will verify its accuracy and send a

signed copy back to the UTM.

5.3.4.6. (Added-Yokota) Requesting/scheduling training.

5.3.4.6.1. (Added-Yokota) UTMs will build a 120-day training forecast for their unit(s) and

forward it to the MTS Scheduler by the last duty day of the month prior to the 120-day mark

(e.g., November’s forecast is due to the Scheduler by the last duty day in July). Include all

requests for FTD and MTS. Outside training providers (CATM/CBRNE) will be scheduled

approximately 30 days in advance.

5.3.4.6.2. (Added-Yokota) UTMs will use the training forecast to forecast unit requirements

and should project training attendance/completion in the month prior to the actual due date (e.g.,

a member coming due for SABC in December will be identified on the November forecast).

Names of the projected trainees should be identified for every seat forecasted (except

Maintenance Orientation). Training Monitors must ensure trainees are loaded into class rosters

NLT 30 days prior to class date to ensure all requested slots are assigned.

5.3.4.6.3. (Added-Yokota) Out-of-cycle requests will be coordinated through the UTM to the

MTS scheduling section and must be justified by the unit commander.

5.3.4.6.4. (Added-Yokota) The MTS class rosters will be distributed to training providers the

day prior to class start date. FTD rosters are provided to FTD by the 20th day of the month for

all classes starting the following month. The printed roster will be the baseline to identify walk-

ins, non-utilizations and no-shows. Attendees not on the roster will be counted as walk-ins.

Members identified on the roster but not in class will be counted as no-shows. Seat allocations

given to a unit that did not schedule a name in G081 or turn the allocation back in will be

counted as a non-utilization. Members scheduled for a class but do not meet the prerequisites or

have previously completed the class are also non-utilizations.

5.3.4.6.5. (Added-Yokota) If Air Education and Training Command (AETC) funding is not

available for requested off-station TDY training, the requesting unit will be responsible for

funding and preparing the TDY orders for the scheduled member.

5.3.4.7. (Added-Yokota) MTS Process improvement.

5.3.4.7.1. (Added-Yokota) MTS customer service critiques are provided at the end of each

class and available in the MTS office entranceway.

5.3.4.7.2. (Added-Yokota) Monthly QA summaries will be sent to the MTS. The

discrepancies are reviewed and analyzed in coordination with the Development and Instruction

(D & I) section. A trend analysis is then conducted with the results located in the QA summaries

binder located in the D & I section. Repeat discrepancies may lead to course development or

current MTS course updates as needed.

5.3.4.8. (Added-Yokota) Training Manager and Additional Duty Training Manager (ADUTM)

Duties/Responsibilities. Each squadron is allowed two personnel with rights to update

qualifications in G081. Managers are only allowed to update in-house training events. Only

MTS personnel are allowed to update MTS/FTD training completions.


6.7.6.1.3.1. (Added-Yokota) This PE requirement will be tracked in G081 for each individual

and, as with any other training requirement, is the responsibility of the individual and their

squadron to ensure remains current. QA will record PE completion in LEAP and provide

verification upon request.

6.11.5.2.3. (Added-Yokota) 374 MXG/MXQ TODO will provide a weekly TO distribution

listing to Plans, Scheduling, and Documentation (PS&D) NLT Thursday of each week. For

extended weekends, the listing will be sent NLT two days prior to the weekend.

6.11.10. (Added-Yokota) 374 AW specific TODO program guidance:

6.11.10.1. (Added-Yokota) Points of Contact.

6.11.10.1.1. (Added-Yokota) The 374 MXG/MXQ TODO will be the point of contact for all

matters pertaining to TOs.

6.11.10.1.2. (Added-Yokota) The following work centers will serve as TODOs: 374

MXG/MXQ (for MXG account F*121Q), 374 MXS/MXMD (for TMDE account F*13MY) and

373 TRS Det 15 (for FTD account F*10TS). All work centers with T.O. libraries aligned below

these aforementioned TODOs, if any, will be known as Technical Order Distribution Accounts

(TODAs).

6.11.10.1.3. (Added-Yokota) 374 MXG/CC will appoint, in writing, the 374 MXG/MXQ

TODO primary and at least one alternate manager.

6.11.10.1.3.1. (Added-Yokota) Additionally, the 374 MXG/CC will appoint, in writing, the

374 MXG/MXQ TODO as Lead Group TODO overseeing the services of the 374 MXS/MXMD

TODO and 373 TRS FTD Det 15 TODO IAW TO 00-5-1.

6.11.10.1.4. (Added-Yokota) 374 MXS/MXMD Flight Chief will appoint, in writing, the 374

MXS/MXMD TODO primary and at least one alternate manager.

6.11.10.1.5. (Added-Yokota) 373 TRS FTD Det 15 Flight Chief will appoint, in writing, the

373 TRS FTD Det 15 TODO primary and at least one alternate manager.

6.11.10.1.6. (Added-Yokota) Squadron supervision will ensure continual compliance with

TODA program establishment as outlined in TO 00-5-1.

6.11.10.1.7. (Added-Yokota) Each TODA will have a primary account custodian and at least

one alternate custodian. Flight Chiefs will appoint, in writing, any changes of the TODA

assignment or account custodians to the TODO within five calendar days of assignment using

TODA appointment memorandum template available from the TODO.

6.11.10.1.7.1. (Added-Yokota) The TODO will be responsible for managing all sub-accounts

and modifying the ETIMS database to include, but not limited to; order or change quantity of TO

books or TO changes, generate reports, and adding or removing TO users to ETIMS.

6.11.10.1.7.2. (Added-Yokota) Newly appointed TODA custodians will complete, at a

minimum, the one-time online courses within 90 calendar days of assignment (00-5-1 Appendix

C), if not already previously completed.

6.11.10.1.7.3. (Added-Yokota) The TODO will be the point of contact for TO requisitions.

Any TODA or user needing a TO added or removed to/from the TO library will contact the

TODO.


6.11.10.1.7.4. (Added-Yokota) The TODO will add TO users to ETIMS by using their AF

Portal ID when they in-process to the unit and then remove them after they out-processed for

PCS/PCA

6.11.10.1.8. (Added-Yokota) TODOs will initiate an AFTO Form 43, USAF Technical Order

Distribution Office (TODO) Assignment or Change Request, whenever there is a change in

TODO personnel or official mail address. The respective TODO organizational mailbox must be

set-up to receive encrypted e-mails with attachments to complete the AFTO Form 43 approval

process.

6.11.10.1.8.1. (Added-Yokota) A digital copy of the approved AFTO Form 43 will be

maintained in the MXQ/TODO network drive.

6.11.10.1.8.2. (Added-Yokota) The primary TODO will conduct an annual review of the

AFTO Form 43 for accuracy of content.

6.11.10.2. (Added-Yokota) Training Requirements.

6.11.10.2.1. (Added-Yokota) TODOs must complete all training required IAW TO 00-5-1

within 90 calendar days of assignment.

6.11.10.2.1.1. (Added-Yokota) TODAs must successfully complete CBTs “TODA

General/Library Custodian Course” and “TODA Advanced Course” IAW TO 00-5-1 within 90

calendar days of assignment, if not previously completed.

6.11.10.2.1.2. (Added-Yokota) Issue of a course completion certificate will serve as proof of

formal training. The TODA General/Library Custodian Course and TODA Advanced Course

completion certificates will be maintained by the TODO and will keep a copy of all TODA

course completion certificates.

6.11.10.2.1.3. (Added-Yokota) Outgoing TODA custodians or alternate TODA custodians will

provide additional training to incoming TODA custodians. If any training is not provided, the

parent TODO will train them.

6.11.10.3. (Added-Yokota) Distribution and Publication Requirements.

6.11.10.3.1. (Added-Yokota) All technical data will be stamped IAW paragraph 6.11.5.2. prior

to distribution.

6.11.10.3.1.1. (Added-Yokota) For TODAs under the 374 MXG/MXQ TODO account

F*121Q, the TODO will write the TODA’s sub-account number next to the TODO stamp on the

title page. For example, AMXS’ sub-account is F*121Q.003. The TODO will write “.003” next

to the TODO stamp “F*121Q”.

6.11.10.3.2. (Added-Yokota) All 374 MXG governed TODA distribution boxes under TODO

account F*121Q are located in 374 MXG Quality Assurance office (Building 314, Room 210).

6.11.10.3.2.1. (Added-Yokota) The servicing TODO will notify all TODAs of TOs and

supplements in distribution for pick up. TODAs will account for the TO increments received

and then sign for these items in the TODA Distribution Signature Log Book located in the MXG

Quality Assurance office. The TODO will record receipt to show TO increment is on-hand.

6.11.10.3.3. (Added-Yokota) It is the TODA’s responsibility to ensure that the TOs are posted

within five work days of the TODO stamp date.


6.11.10.3.3.1. (Added-Yokota) Check the supercedure notice on the title page of the new TO

change, supplement, or TOPS.

6.11.10.3.3.2. (Added-Yokota) If a TO change is received out of sequence, the TODA or

library custodian will not post the increment. Until all previous increments are received, the

increment will be filed back of the TO and then write legibly on the title page of the TO in black

pencil that TO change is filed back of the book awaiting on previous changes, writing the

specific change numbers.

6.11.10.3.3.3. (Added-Yokota) The TODO will monitor the ETIMS for physical media TO

increments (paper, DVD, CDs) not received. No later than 60 calendar days after the

increment’s EDD (estimated delivery date) according to ETIMS, not its publication date, if the

increment is not received by the TODO through the Official Mail Center, the TODO will notify

the applicable TODAs. The TODA and/or library custodian will then write “Change [#] is

missing in shipment” on the top of the title page in black pencil only.

6.11.10.3.4. (Added-Yokota) Only complete TOs downloaded and printed from a digital

media source by a TODA custodian must be date stamped by the servicing TODO prior to

posting and placed on active TO library, if the following conditions are met:

6.11.10.3.4.1. (Added-Yokota) The TO account already has a subscription in ETIMS for the

paper TO and marked as Global and Active. If they are on subscription for a digital TO,

reproduction of the entire TO is not authorized.

6.11.10.3.4.2. (Added-Yokota) The paper TO is not on a list for zero subscription reduction of

physical media TOs identified by the TOMA, PACAF, group/squadron supervision or TODO.

6.11.10.3.4.3. (Added-Yokota) The reprinted TO is a replacement TO, on a one-for-one swap.

6.11.10.3.4.4. (Added-Yokota) Exception: If a TO page with date stamp (e.g., title page,

supplement) was severely torn or missing, the TODA will reprint the page and bring it to the

TODO to be re- stamped.

6.11.10.3.5. (Added-Yokota) Any TO downloaded to the unit’s shared drive from a digital

media source such as ETOV must be checked for currency using the ETIMS Catalog by

applicable TODA or TODO every seven calendar days and document each digital TO on a

locally generated document (hard copy or electronic copy stored on shared drive) for proof. The

unit will make sure the TO users meet the distribution statement to view the digital TO.

6.11.10.3.5.1. (Added-Yokota) No digital TOs will be re-hosted onto a SharePoint or any other

website due to the accessibility by everyone and restrictions according to the distribution

statement. This includes Local Checklists (LCLs) and Local Page Supplements (LPS) as a digital

file.

6.11.10.3.6. (Added-Yokota) Work centers with CPINS (Computer Program Identification

Numbers) software will have their physical medias (DVDs and CD-ROMs) organized for easier

accountability in the same place, if not part of inventory for a support equipment (i.e., Propeller

Balance Analyzer). These physical media will not be stored with other DVDs or CD-ROMs

where they can be mistaken for anything but a CPIN.

6.11.10.3.6.1. (Added-Yokota) CPIN ordering requests will be submitted by e-mail to the

parent TODO, unless already listed in a TCTO.


6.11.10.3.6.2. (Added-Yokota) TOs and/or CPINs received with new support/test equipment

will be reported to the TODO. TOs and CPINS must be on the account to receive updates.

6.11.10.3.6.3. (Added-Yokota) CPINS (classified and unclassified) will be picked up by

authorized personnel, on a one-for-one swap.

6.11.10.4. (Added-Yokota) Disposition and Handling of Technical Orders.

6.11.10.4.1. (Added-Yokota) The TODA and will notify the TODO for all TO requisitions by

e-mail or phone. The TODO will use ETIMS’ to send transactions to DAPS and JCALS for the

TOMA to approve.

6.11.10.4.1.1. (Added-Yokota) The TODA may keep paper TOs and other physical media TOs

for their account on the active TO library shelf only if both are met: (1) According to ETIMS, the

TO scope is marked Publication Status is marked ‘Active’ and the Media Type is ‘Paper’. (2)

And the paper TO is not on a list for zero subscription reduction of physical media TOs

identified by the TOMA, PACAF, group/squadron supervision or TODO, whichever is first.

6.11.10.4.1.1.1. (Added-Yokota) The TODA will make all efforts to reduce their paper TOs,

DVDs and CD-ROMS once they are on subscription for the ETIMS e-TOs (suffix ending with “-

WA-1”).

6.11.10.4.1.1.2. (Added-Yokota) The TODA custodians will continue to maintain the paper

TOs on active library shelf including LEP checks and TO inventory checks until the paper TOs

are reduced to zero subscriptions.

6.11.10.4.1.2. (Added-Yokota) If the paper TO does not have the same currency as the digital

TO, it must not be checked out for use on Operation & Maintenance (O&M) equipment until all

paper changes are received and caught up with the digital version. The TODA and/or Library

Custodian will identify which ones are affected.

6.11.10.4.1.2.1. (Added-Yokota) The TO user will then follow TO 00-5-1 for TO extractions,

including printing out the title page, all applicable warnings, cautions, illustrations, supplements

affected by the task(s) needed in the TO. The TO user will write on the title page in black

pencil: date printed, date and time checked current, and TO user’s initials and employee man

number. The TO extracts are only good for duration of the day or after completion of the task. It

is the responsibility of the TO user for safe guarding the TO extracts and destroy it when no

longer needed.

6.11.10.4.1.3. (Added-Yokota) All requests for emergency justifications (whether paper or

digital TO) must be in official memorandum format, with justification and signed by the

section/flight chief. The letter will contain, at a minimum, the reason for the request and how

many TOs are needed. Emergency requisitions will be validated by the TODO. The TODO will

then enter the justification in ETIMS immediately for the TOMA to review for approval.

6.11.10.4.1.4. (Added-Yokota) Individual paper TO pages that are missing or torn cannot be

ordered through ETIMS. If only a few pages are needed, the TODAs and library custodians are

authorized to make copies of missing pages to include reprinting pages from current digital TO

source like ETOV; otherwise the entire TO will need to be re-ordered or re-printed (see

Paragraph 6.11.10.3.4.). If the digital TO is more current than paper version, then TODA will

cautiously check the change number on affected pages (both front and back) before reprinting the


needed pages. If unable to reprint, write on title page the discrepant page and wait for updated

paper TO change to be received through mail system by the TODO.

6.11.10.4.1.5. (Added-Yokota) In order to obtain stamped copies of local technical data (e.g.,

LCL, LPS or LWC), the TODA must email a request to TODO. It will be processed into their

distribution box after printing from DAPS with GPC purchase.

6.11.10.4.2. (Added-Yokota) To provide longer lasting TOs, the use of a clear protective

covering (i.e. plastic protective sleeve) for heavily used pages is authorized. The pages will not

be laminated in case the page needs annotation of reference to supplements.

6.11.10.4.3. (Added-Yokota) TOs, checklists and work cards will be treated as tools, and if

lost, must be reported IAW AFI 21-101_PACAFSUP, Aircraft and Equipment Maintenance

Management Pacific Air Forces Supplement, and local instructions.

6.11.10.4.4. (Added-Yokota) Each aircraft T.O. library is a separate sub-account underneath

AMXS’ TODA sub-account F*121Q.003, managed by their custodians.

6.11.10.4.4.1. (Added-Yokota) For aircraft that are deployed, the TODO will mail any paper

T.O. changes for that aircraft to the TODO at the deployed location for posting.

6.11.10.4.5. (Added-Yokota) Documentation of the List of Effective Pages Check (“LOEP” or

“LEP” Check) will be on the last page of the LEP using black pencil only. It will consist of type

of LEP check (revision, annual or change), date accomplished, initials and employee number.

The employee number will be used for QA or TODO to enter the follow up inspection into the

QA database.

6.11.10.4.6. (Added-Yokota) All annotations to the TOs (including references to supplements)

will be legible and be made using black pencil only.

6.11.10.4.7. (Added-Yokota) FOD: Staples and/or other foreign objects will be removed from

TOs used on the flight line, on or around aircraft, and on or near any equipment that could be

affected by the potential FO. Page markers or Post-It Notes will not be used in TO binders.

6.11.10.4.8. (Added-Yokota) TODO will distribute all Safety Supplements immediately upon

receipt and notify TODAs that they have been distributed. TODAs will post the supplements

within 24 hours of received date stamp. TODO will notify squadron supervision of all Safety

Supplements applicable to their units within 24 hours of receipt. If the supplement is for a TO

that is digital viewable through e-Tools (Electronic Tools) in disconnected mode and supplement

is not embedded yet to the e-TO, the TODO will upload the supplement to the master e-Tool and

named to be listed next to the parent TO. Then, inform all applicable TODAs to manually

synchronize all of their e-Tools to receive the supplement update. The TO user will have to open

both parent TO file and supplement file in e-Tools and review them both prior to start of tasks.

The supplement will be kept on the master e-Tool until the supplement is embedded with the

parent TO (viewable through ETOV) or when it has been superseded by updated TO increment,

whichever is first). The TODO will manually remove the supplement from the master e-Tool

only. The supplement on each e-Tool will then be automatically removed during their next

synchronization with the master e-Tool.

6.11.10.4.9. (Added-Yokota) For accounts with paper TOs, the ETIMS listing (or MTOR) will

be printed by the TODA at the beginning of every month during the first week and reviewed for

accuracy NLT fifth day. The current MTOR for the month will be placed in their TODA


Continuity Binder. If the account is too large to print the listing every month, the TODA may

store it electronically on the shared drive and have a DD Form 2861, Cross Reference, showing

the location.

6.11.10.4.9.1. (Added-Yokota) Upon receipt of monthly ETIMS listing, the TODA will

compare the ETIMS listing with the ETIMS Catalog to ensure all information is current. Any

discrepancies noted will be reported to the parent TODO NLT 10th day. At a minimum, they

will check the TOs that now listed as rescinded or renumbered and check for status of their paper

TOs on order.

6.11.10.4.10. (Added-Yokota) Discrepancies found in TOs of a non-technical nature (e.g. LEP

error, misprint) will be submitted in writing or e-mail to the servicing TODO. The TODO will

submit a two-way memo/e-mail to the ALC for clarification. The TODAs will receive a copy of

the two-way memo for their records when disposition instructions are provided by the ALC. All

discrepancies will be noted on the title page of the affected TO.

6.11.10.4.11. (Added-Yokota) TOs will be charged out of their library using TC MAX. If TC

MAX is not utilized, TOs will be charged out using AF Forms 614, Charge out Record, and

614A, Charge Out Record (8 X 5-1/2).

6.11.10.5. (Added-Yokota) Filing Order for AMC Supplements, Messages and Changes to

AMC Supplements.

6.11.10.5.1. (Added-Yokota) TODOs and TODAs will file AMC supplements behind the

applicable TO in ascending order, and will make an annotation concerning the AMC supplement

on the TO title page.

6.11.10.5.2. (Added-Yokota) TODOs and TODAs will file message changes to AMC

supplements on top of the AMC supplements, and will annotate the message on the AMC

supplements title page.

6.11.10.5.3. (Added-Yokota) TODOs and TODAs will file changes to AMC supplements

behind AMC supplements in ascending order, and will annotate the changes on the AMC

supplements title page.

6.11.10.6. (Added-Yokota) Local Checklists (LCL), Local Page Supplements (LPS) and Local

Work Cards (LWC).

6.11.10.6.1. (Added-Yokota) When actions of a technical nature arise that are not covered in

existing technical data, squadron supervision should determine the need for local technical data

(LTD) development. If determination warrants a technical procedure to be written, prepare LTD

IAW TO 00-5-1 and AFI 21-101. All newly proposed LTD draft copies will accompany a

signed AF Form 673, Air Force Publication/Form Action Request, and justification letter signed

by the squadron maintenance supervision. The letter must contain full justification, certifying

that no existing TO will suffice.

6.11.10.6.2. (Added-Yokota) Locally prepared technical data will not be used to circumvent

Air Force Material Command’s (AFMC) inherent responsibility for technical data (see TO 00-5-

1). During validation of LTD, all requests must be reviewed to determine if an AFTO Form 22,

Technical Manual (TM) Change Recommendation and Reply, is necessary for AF wide

implementation. The LTD will be returned to the Office of Primary Responsibility (OPR) for


initiation of an AFTO Form 22 as required. The OPR will initiate the AFTO Form 22 IAW TO

00-5-1. The 374 MXG/MXQ Product Improvement Office will provide assistance as necessary.

6.11.10.6.3. (Added-Yokota) TODOs will submit LCLs, LPSs and LWCs (on locally produced

digital forms 374 MXG Form 8 and 374 MXG Form 8a or equivalents) with a cover letter signed

by the squadron maintenance supervision to Quality Assurance for technical review and

coordination.

6.11.10.6.4. (Added-Yokota) Prior to implementing any LTD, the identifying squadron will

appoint subject matter expert(s) to work in concert with Quality Assurance and the MXG TODO

to properly prepare and validate the LTD. Quality Assurance will verify the safety, adequacy

and quality of each draft copy LCL, LPS and LWC through a technical assessor assigned to the

374 MXG/MXQ section.

6.11.10.6.5. (Added-Yokota) The MXG TODO, with assistance from Quality Assurance, will

ensure a LCL, LPS or LWC number is assigned after completing validation and certification. All

LCL, LPS and LWC numbers will follow standard formats. All LCLs will be numbered LCL-

374MXG-X and LWCs will be numbered LWC- 374MXG-X. (‘X’ indicates number to be

assigned). An LPS will contain the TO number (e.g. LPS-130H-6).

6.11.10.6.6. (Added-Yokota) The MXG TODO will forward the LCL, LPS or LWC and a

cover letter to the 374 MXG/CC for approval/disapproval.

6.11.10.6.7. (Added-Yokota) Upon return of all correspondence, the MXG TODO will notify

each section of current status.

6.11.10.6.8. (Added-Yokota) After approval and signed by MXG/CC on title page of the LTD

and AF Form 673, all locally prepared publications with distribution statement will be submitted

to TODO for tracking and distribution to include: entering in ETIMS database for accountability,

currency tracking, and DAPS processing. LPS will be printed on any other paper (e.g. orange,

blue) except for green while filed in a TO. After the publications are received back from DAPS,

the TODO will update publications in ETIMS as on-hand for applicable TODA accounts, date

stamp the publication and distribute out to applicable TODAs.

6.11.10.6.9. (Added-Yokota) LCLs and LWCs are filed in the same manner as TOs (e.g. date

stamped and filed in alphanumeric order). LPSs are filed in the same manner as TOPS. The title

page of the LPS will be posted in front of the TO title page and behind all other messages,

supplements and TOPS. All LTDs may be filed electronically either in ETIMS, the QA

SharePoint, or another accessible location as appropriate for the particular publication filed

(LCLs, LWCs, or LPS) as determined by the MXG TODO.

6.11.10.6.10. (Added-Yokota) The TODO will conduct routine checks, at least annually, on all

referenced source data affecting each LCL, LPS or LWC. If the source data has changed, the

TODO will contact the OPR in the form of memorandum to review the changed source data to

insure that the information contained in the local technical order is still current. The OPR will

respond NLT 10 calendar days with attached corrections, if any, to the MXG TODO and/or

Quality Assurance Office.

6.11.10.6.11. (Added-Yokota) Each LPS will be maintained efficiently by the 374 MXG/MXQ

TODO to ensure information stays current with the source TO. If the source TO changes, then


the TODO will route the LPS along with the new/changed TO to Quality Assurance subject

matter experts who will determine if the LPS requires revisions/changes.

6.11.10.6.12. (Added-Yokota) LPS requiring revision/changes which deal with safety shall be

updated by the TODO NLT one duty day after source TO changes. Routine revision/changes

will be routed by the TODO NLT five duty days after source TO changes.

6.11.10.7. (Added-Yokota) Management and Maintenance of e-Tools (Electronic Tools).

6.11.10.7.1. (Added-Yokota) The e-Tools are ruggedized laptops/tablets used for its primarily

intended purpose–viewing digital TOs. These are intended to replace physical medial TOs

(paper, CDs, DVDs). In the event that e-Tools cannot be used at the Point of Maintenance

(POMx), the TO user will refer to TO 00-5-1 and this instruction for TO extraction procedures.

Reproduction of an entire TO is not authorized.

6.11.10.7.2. (Added-Yokota) For management of e-Tools refer to: TO 00-5-1, TO 31S5-4-

ETOOL-1, and paragraph 8.5.5 of this instruction. Report cyber security incidents to CTK

Support Section or Lead TODO in accordance with TO 33-1-38.

6.11.10.7.3. (Added-Yokota) The e-Tools have tougher specifications than a normal computer;

they are also designed to be water resistant, but require all case structures and doors to be intact

and serviceable. Damage to the e-Tool limits its acceptable operating environment. Although e-

Tools are tougher than a normal computer, they are not designed to withstand excessive abuse –

they must be treated with care.

6.11.10.7.3.1. (Added-Yokota) It is fully recognized that e-Tools are used in harsh

environment and as a result, normal wear/tear or human mistakes will result in some damage to

e-Tools; however, negligence or willful misconduct must be identified and addressed.

6.11.10.7.4. (Added-Yokota) E-Tool availability will be ensured by work centers keeping e-

Tool assets connected to the network when not in use.

6.11.10.7.4.1. (Added-Yokota) The e-Tools must be connected to only its designated LAN port

(including one in its assigned cabinet drawer) to prevent tripping port security at all times while

stored and not in use.

6.11.10.7.5. (Added-Yokota) The e-Tools must be powered on at all times with power plug

while stored to receive all updates (network, security, patches, and digital TOs). The e-Tool

synchronization will not happen while on ‘battery only’ power.

6.11.10.7.6. (Added-Yokota) Logging into the e-Tool laptop requires the user’s own Common

Access Card (CAC), like any other government computer on the network.

6.11.10.7.7. (Added-Yokota) The following considerations will be observed anytime an e-Tool

is utilized. This is not an all-inclusive list:

6.11.10.7.7.1. (Added-Yokota) Safeguard e-Tools to prevent damage and abuse whether in use,

transport, or storage. This includes ensuring all doors around the laptop are closed to prevent

damage.

6.11.10.7.7.2. (Added-Yokota) For continuity and FOD prevention, all e-Tools of the same

make and model will be configured the same. Any modification/deficiency will be annotated in

TC MAX.


6.11.10.7.7.2.1. (Added-Yokota) All e-Tools will have sealant applied to external screws to

avoid potential FOD hazards. Do not break the seal by loosening these screws.

6.11.10.7.7.2.2. (Added-Yokota) E-Tools equipped with a stylus pen must be secured and

accounted during all inventory checks. If removed, these need to be annotated in TC MAX.

6.11.10.7.7.3. (Added-Yokota) Check out e-Tools IAW AFI 21-101 and local procedures using

TC MAX.

6.11.10.7.7.4. (Added-Yokota) Be familiar with the use of e-Tools in and around hazardous

environments and Electro-Explosive Devices (EED) per TO 00-25-172, TO 1-1-3, and AFMAN

91-201. When around explosives, use IAW guidance contained in EM radiation survey.

6.11.10.7.7.5. (Added-Yokota) Notify the TODO immediately if an e-Tool is broken,

inoperative or damaged.

6.11.10.7.7.6. (Added-Yokota) E-tools are only authorized for government use and on

government networks. Wired or wireless connections to civilian networks are strictly prohibited.

6.11.10.7.7.7. (Added-Yokota) Use e-Tools for official use only.

6.11.10.7.7.8. (Added-Yokota) Notify the TODA of faulty or missing digital TOs.

6.11.10.7.7.9. (Added-Yokota) Do not leave e-Tools unattended.

6.11.10.7.7.10. (Added-Yokota) Do not place e-Tools on operating equipment.

6.11.10.7.7.11. (Added-Yokota) Do not allow fluids to spill or leak on the e-Tools.

6.11.10.7.7.12. (Added-Yokota) Do not set e-Tools in any liquid or fluids.

6.11.10.7.7.13. (Added-Yokota) Do not drop e-Tools.

6.11.10.7.7.14. (Added-Yokota) Do not sit, stand or kneel on the e-Tool or Pelican case (if

utilized).

6.11.10.7.7.15. (Added-Yokota) Do not plug USB devices as this is a DOD violation.

6.11.10.7.7.16. (Added-Yokota) Use care in the placement of e-Tools on objects during high

winds.

6.11.10.7.7.17. (Added-Yokota) In inclement weather (rain, sleet, snow), e-Tools with damage

that can allow water or moisture intrusion cannot be used. It will be documented IAW local

directives if a specific e- Tool cannot be used.

6.11.10.7.7.18. (Added-Yokota) May be held liable for the costs of repair or replacement, if

the damage was caused by neglect, misuse, abuse or alternation on person’s part IAW AFMAN

23-220.

6.11.10.7.8. (Added-Yokota) Prior to checkout of Support Section, the customer (or TO user)

will log on to the e-Tool with user’s own CAC during check out. And before leaving the support

section at Home Station, verify that the downloaded digital TOs are up to date and current within

seven calendar days IAW TO 00-5-1.

6.11.10.7.9. (Added-Yokota) After the user returns the e-Tool laptop to Support Section, the

support personnel will inventory the contents, verify that CAC is removed, the e-tool is restarted,

and no damage noted on the laptop.


6.11.10.7.9.1. (Added-Yokota) Rebooting the e-Tool ensures someone has not left it locked

after turn-in. Left in restart makes it ready for the next user once its batteries are fully recharged.

And, powered on in restart mode places the computer in a generic state (no users logged on) to

receive and apply the updates. If not placed in restart mode while in the cabinet, users will need

to restart at sign out to pull down updates, thereby wasting time before departing support section.

6.11.10.7.10. (Added-Yokota) The Lead TODO(s) will coordinate with other TODOs and

TODAs, and local Client Support Administrators (CSA), Functional Systems Administrators

(FSA), and applicable functional OPRs to ensure eTools are configured with current and only

authorized software to support TO and maintenance documentation. (T-1). Note: Coordination

with the local Communications Squadron to verify network configuration requirements for

eTools are available and sustained to meet the requirements listed in TO 31S5-4-ETOOL-1-WA-

1. Additional user support available through the Air Force Technical Order Functional Support

Team, [email protected] or DSN 872-9300.

6.11.10.7.11. (Added-Yokota) Support personnel will check each e-tool laptop once a week to

ensure there are no logon issues, the laptops have not dropped off the network, and the TO

synchronization is within seven calendar days. If not updated, the support personnel will try to

manually synchronize the e-Tool to the master e-Tool. If any problems or errors arise, follow

local base communications procedures, including contacting unit FSA (Functional System

Administrator) for assistance.

6.11.10.7.12. (Added-Yokota) In the event of an aircraft or equipment mishap, units will lock

down all e-Tools until it is determined which units were used on the affected mishap equipment

and the event log from the e-Tool is downloaded to facilitate the mishap investigation.

6.11.10.7.13. The MXG TODO will:

6.11.10.7.13.1. Maintain a list of Department of Defense Information Technology within the

MXG, identify systems with deficient detection capabilities, actions taken to escalate deficient

detection capabilities, and other locally reported Information Technology deficiencies.

6.11.10.7.13.2. Escalate weapons system and support equipment cyber related deficiencies to the

applicable Program Manager in accordance with T.O. 00-35D-54, USAF Deficiency Reporting,

Investigation, and Resolution.

6.11.10.7.13.3. Escalate a cyber requirement or issue, submit an AF Form 1067, Modification

Proposal, IAW AFI 63-101/20-101, Integrated Life Cycle Management, and/or maintenance

assistance request IAW TO 00-25-107, Maintenance Assistance.

6.11.10.8. (Added-Yokota) Management and Maintenance of Commercial Mobile Devices

(CMD) e-Tools–Apple iPads.

6.11.10.8.1. (Added-Yokota) iPads will be managed and operated in the same manner as e-

Tools per paragraph 6.11.10.7. of this supplement. The following exception applies:

6.11.10.8.1.1. (Added-Yokota) iPads do not conform to AF network standards and will not be

connected to government networks. iPads will only utilize FIPS 140-2 WPA2 encrypted

wireless.

6.11.10.8.2. (Added-Yokota) iPads will be configured IAW TO 31S5-4-ETOOL-1, Chapter 3.

6.11.10.9. (Added-Yokota) E-Tool Cyber Hygiene.

mailto:[email protected]


6.11.10.9.1. (Added-Yokota) All 374 MXG personnel will comply with Cyber Hygiene for

Flightline Computers training prior to check out and use of e-Tools

6.11.10.9.1.1. (Added-Yokota) Training is also required before using iPads.

6.11.10.9.1.2. (Added-Yokota) Annual training required upon assignment to 374 MXG, to be

completed during Maintenance Orientation.

6.11.10.9.1.3. (Added-Yokota) Training will be tracked in G081 as ANCL 000002.

6.11.10.9.2. (Added-Yokota) All e-Tools connected to the AF network will conform to AF

network standards and scanning practices.

6.11.10.9.2.1. (Added-Yokota) Assured Compliance Assessment Solution (ACAS) scanning

conducted on a weekly basis by 374 CS on all networked assets, to include Anti-Virus (AV)

scanning to ensure cyber hygiene.

6.11.10.9.3. (Added-Yokota) CMD e-Tools, specifically iPads, do not conform to AF network

standards and will be managed internally by the owning organization’s TODA.

6.11.10.9.3.1. (Added-Yokota) Per AFMAN 33-282, TODAs with iPads in their inventory

will:

6.11.10.9.3.1.1. (Added-Yokota) Obtain and install antivirus tools and signature files from the

AFCERT site operated by the 33rd Network Warfare Squadron

(https://33ios.lackland.af.mil/virus/sym_sigs.htm) and/or the DoD Patch Repository

(https://patches.csd.disa.mil/Default.aspx).

6.11.10.9.3.1.2. (Added-Yokota) Perform weekly Anti-Virus scans on all assets.

6.11.10.9.3.1.2.1. (Added-Yokota) If viruses are detected, immediately notify proper chain of

command.

6.11.10.9.3.1.3. (Added-Yokota) Check for and apply Signature Updates weekly.

6.11.10.9.4. (Added-Yokota) For Data Transfer and Diagnostic System (DTADS) see

paragraph 11.10.6.3.3.4.

6.11.10.9.5. (Added-Yokota) Quality Assurance will conduct quarterly Cyber Hygiene

Program Compliance Inspections.

6.11.10.10. (Added-Yokota) Inspections.

6.11.10.10.1. (Added-Yokota) Each TODA will be inspected annually by the TODO,

according to the distributed schedule. The schedule is tentative and is designed to serve as a

guide. This includes even if the TO account is 100% digital.

6.11.10.10.2. (Added-Yokota) It is the TODA’s responsibility to ensure their account fulfills

the requirements outlined in the inspection checklist provided in TO 00-5-1. At least one

appointed, trained account custodian will be present for the inspection.

6.11.10.10.3. (Added-Yokota) If the account receives an unsatisfactory rating, the account will

have 30 calendar days to correct all discrepancies and review TOs. During a re-inspection,

verifications will be made to ensure all discrepancies were corrected.

6.13.1.2. (Added-Yokota) Functional Check Flight (FCF). FCFs, Operational Check Flights

(OCF), Acceptance Check Flights (ACF) and High Speed Taxi Checks (HSTC) are performed to

https://33ios.lackland.af.mil/virus/sym_sigs.htm

https://patches.csd.disa.mil/Default.aspx


ensure aircraft are safe for flight and capable of performing assigned missions. FCFs are not

flown when the airworthiness of the aircraft can be determined by maintenance operational

checks prescribed by associated technical directives.

6.13.1.2.1. (Added-Yokota) The C-12 and UH-1 aircraft are maintained by civilian contractors

and are specifically exempted from following this instruction. The contractors are contractually

required to have their own QA and FCF programs and will perform the function of FCF Manager

for their respective contracts. The contractors will follow the guidance of their Performance

Work Statement, applicable technical data and company generated, government accepted FCF

programs to include local operating instructions and checklists.

6.13.5.2. (Added-Yokota) FCF Completion. Upon completion of the FCF, the QA FCF

Manager will meet the FCF aircrew at Maintenance Debrief Section and review the FCF

checklist and aircraft forms to determine if all requirements have been accomplished. The QA

FCF Manager will accomplish the following steps:

6.13.5.2.1. (Added-Yokota) Retrieve the FCF Worksheet, 1C-130J-6CL-1, and the FCF

Information Handbook from the aircrew.

6.13.5.2.2. (Added-Yokota) Deliver the FCF Worksheet, copy of all 781A maintenance

discrepancies/corrective actions pertaining to the check flight, FCF/ACF/OCF/HSTC checklist,

1C-130J-6CL-1 to the 374th Maintenance Operations (374 MO) Plans, Scheduling and

Documentation (PS&D) Section to be included in the aircraft jacket file as a permanent record.

6.13.5.2.3. (Added-Yokota) If the aircraft fails the FCF and is not released, coordinate with the

MOC, 374 AMXS/MOO (or designated representative) and the respective flying squadron

operations desk to schedule the next flight attempt. A non-release is defined as a termination of

the FCF sortie and the FCF aircrew returning to the Maintenance Debrief Section.

6.13.5.2.4. (Added-Yokota) Upon each FCF non-release, a new T.O. 1C-130J-6CL-1 will be

accomplished to account for the number of attempted FCF flights.

6.13.5.2.5. (Added-Yokota) When the FCF aircraft is released, the QA FCF Manager will

complete all documentation in the FCF Log as required. This will serve as a permanent record as

well as show deficiency or trend analysis.

6.13.7. (Added-Yokota) Aircraft Maintenance Unit (AMU) Responsibilities. Upon

notification of a FCF, OCF, ACF or HSTC, the owning aircraft maintenance unit will ensure the

following steps are completed:

6.13.7.1. (Added-Yokota) Place FCF/ACF/OCF/HSTC checklist in the front of the AFTO

Form 781A’s, Maintenance Discrepancy and Work Document, and ensures all applicable items

are completed. Remove the checklist from the forms after the completion of the

FCF/ACF/OCF/HSTC. (See MXG LCL 3, also located on the QA SharePoint site)

6.13.7.2. (Added-Yokota) Ensure all aircraft systems are fully operational or will not affect the

FCF, OCF, ACF or HSTC profile.

6.13.7.3. (Added-Yokota) Refuel the aircraft as required in order to complete the FCF, OCF,

ACF or HSTC profile.


6.13.7.4. (Added-Yokota) Configure the cargo compartment with a CP-1 rig. Only one 2-man

seat at F.S. 267 (left side) needs to be placed down and locked to the cargo compartment floor to

accommodate the loadmaster.

6.13.7.5. (Added-Yokota) Prepare the aircraft AFTO Form 781 Series forms binder for review

by Quality Assurance (QA) FCF Manager. Ensure all AFTO Form 781A pages of the original

grounding discrepancies are included for the review process.

6.13.7.6. (Added-Yokota) The aircraft forms will be transcribed prior to flight, and

maintenance will bring the transcribed forms and the active set of forms to the QA FCF Manager

for the aircrew briefing.

6.13.7.7. (Added-Yokota) The Maintenance Operations Officer (MOO) or Superintendent (or

designated representative) will notify the QA office as soon as possible, but not later than 1100,

the day prior to the FCF mission requirement, and coordinate with the applicable flying squadron

to schedule a FCF-qualified aircrew for the mission.

6.13.8. (Added-Yokota) QA FCF Manager Responsibilities. Upon notification of an FCF,

ACF or OCF, the FCF Manager will ensure the following steps are completed:

6.13.8.1. (Added-Yokota) Prepare a FCF Worksheet (a blue-lined AFTO Form 781A, page

1A) for inclusion in the aircraft forms. If there is more than one FCF on the same day, use the

following job control numbers: 5001-5026.

6.13.8.2. (Added-Yokota) Review the aircraft forms for maintenance accuracy and completed

documentation. Retain the transcribed set of forms until the FCF aircraft is released. Prepare a

concise statement for the reason of the FCF to be entered in Block 1 of the FCF Worksheet.

6.13.8.3. (Added-Yokota) Prepare a T.O. 1C-130J-6CF-1 and annotate the systems to be

checked on Page 1 Block 3, Reason for Check Flight. Consult the applicable maintenance

specialist and highlight those areas on the checklist applicable to the FCF mission.

6.13.8.4. (Added-Yokota) On the day of the FCF; review the aircraft forms and verify status

prior to the AMU calling the Maintenance Operations Center (MOC) and Command Post to alert

the aircrew.

6.13.8.5. (Added-Yokota) Insert the FCF Worksheet page 1A in front of page 1 of the AFTO

Form 781A active forms and have the highlighted T.O. 1C-130J-6CF-1 checklist ready for the

aircrew briefing.

6.13.8.6. (Added-Yokota) When the aircrew arrives for the briefing, inform them of the reason

for the FCF. Ensure the aircrew is aware of any open discrepancies in the AFTO Form 781A

active forms (e.g., in-flight operational checks, in-flight negative torque checks).

6.13.9. (Added-Yokota) Aircrew Responsibilities. The FCF will be accomplished using the

FCF Information File containing: T.O. 1-1-300-WA-1; T.O. 1C-130J-6CF-1; and FCF Area

Map.

6.13.9.1. (Added-Yokota) The aircraft commander (or designee) will sign out the FCF

Information File from the QA office (as required) for guidance in accomplishing the FCF

requirements.

6.13.9.2. (Added-Yokota) Enter FCF-related discrepancies on the FCF Worksheet page 1A.

Discrepancies not related to the FCF are placed in AFTO Form 781A active forms.


6.13.9.3. (Added-Yokota) The aircraft commander will annotate and complete the appropriate

blocks on T.O. 1C-130J-6CF-1, AFTO Form 781A active forms, and FCF Worksheet with the

local time and date the FCF is completed.

6.13.9.4. (Added-Yokota) The aircraft commander (or designee) will complete the highlighted

checklist items, and items marked with an asterisk (*) symbol as required, by using a check mark

for satisfactory, an (X) for unsatisfactory, or an (O) for not checked.

6.16.4.5. (Added-Yokota) Ensure computations are accurate on the DD Form 365 series or

Automated W&B System (AWBS) Data Sheets.

6.16.4.6. (Added-Yokota) Maintain primary W&B handbooks on all assigned aircraft and

provide current DD Form 365-3, W&B Record Chart C Basic, for aircraft supplemental

handbooks located in each aircraft’s Technical Order (T.O.) cabinet.

6.16.4.7. (Added-Yokota) Provide 374 OG Stan/Eval with information identifying baseline C-

130J aircraft to be used for calculation of CANNED Forms F (DD Form 365-4, W&B Flight

Clearance).

6.16.4.8. (Added-Yokota) Provide the owning Aircraft Maintenance Unit (AMU) with a pre-

weigh preparation checklist (MXG Form 9) for guidance in configuring the aircraft to proper

pre-weigh condition IAW applicable T.O.’s. This checklist will remain in the aircraft 781 series

forms binder for final review by Weight and Balance personnel.

6.16.4.9. (Added-Yokota) Set up weighing equipment and monitor each aircraft weighing IAW

TO 1-1B-50, Weight & Balance; 1C-130(C)J-5-1, Sample Basic Weight Checklist, C-130J

(Long) Aircraft, 1C-130(C)J-5-2, Loading Data Manual, C-130J (Long) Aircraft, and T.O. 1C-

130J-2-08JG-00-1, Ground Handling, Weighing and Leveling.

6.16.4.10. (Added-Yokota) Notify Plans, Scheduling and Documentation (PS&D) section of

new W&B due date when aircraft returns from Programmed Depot Maintenance (PDM).

6.16.5. (Added-Yokota) PS&D section will:

6.16.5.1. (Added-Yokota) Notify the QA W&B Manager not later than three duty days prior to

any scheduled aircraft transfer, PDM departure or return, W&B Inspection, Time Compliance

Technical Order modification, equipment upload and download swap outs.

6.16.5.2. (Added-Yokota) Ensure aircraft are scheduled to be weighed. Aircraft will be

weighed as recommended IAW TO 1C-130J-6, Aircraft Scheduled Inspection and Maintenance

Instruction; 1-1B-50, Weight & Balance; and 1C-130(C)J-5-1, Sample Basic Weight Checklist,

C-130J (Long) Aircraft, 1C-130(C)J-5-2, Loading Data Manual, C-130J (Long) Aircraft. The

primary facility for aircraft weighing will be fuel cell (Bldg. 1587) unless other mission

requirements take precedence.

6.16.5.3. (Added-Yokota) Schedule an aircraft wash at least 24 hours prior to being fully

weighed. The aircraft will not be flown between washing and weighing.

6.16.5.4. (Added-Yokota) Schedule a hangar for weighing. Aircraft will not be scheduled for

weighing in a hangar with restricted door operation.

6.16.6. (Added-Yokota) Aircraft Maintenance Squadron Production Superintendents and/or

Expediters will:


6.16.6.1. (Added-Yokota) Notify the QA W&B Manager by any means possible (e.g., G081,

E-mail, fax, telephone) upon completion of a Time Compliance Technical Order (TCTO) that

requires a W&B before next flight.

6.16.6.2. (Added-Yokota) Coordinate all phases of the aircraft weighing with QA and PS&D.

6.16.6.3. (Added-Yokota) Ensure the QA W&B Manager is notified as soon as possible by the

most expeditious means available (e.g., G081, E-mail, fax, telephone) whenever aircraft

equipment weighing 5 pounds or more is removed as a result of either scheduled or unscheduled

maintenance and the aircraft will fly a mission with the resulting configuration. Notify again

upon re-installation of equipment.

6.16.6.4. (Added-Yokota) Notify the QA W&B Manager immediately when a mission change

effecting the W&B of an aircraft occurs (i.e., aircraft swap outs and equipment up/downloads).

6.16.6.5. (Added-Yokota) Complete and insert Aircraft Weighing Preparation and Inventory

Checklist (MXG Form 9) in the front of aircraft AFTO 781 forms binder. DO NOT remove this

checklist prior to weight and balance inspection/inventory. This checklist must be completed in

its entirety and reviewed by the Weight and Balance technician prior to weighing the aircraft.

Note: This checklist is only required for aircraft weighs. Direct any questions to the W&B

manager.

6.16.6.5.1. (Added-Yokota) Verify aircraft fuel tanks are first refueled to capacity then

defueled and drained IAW TO 1C-130J-2-12JG-10-1, Ground Handling Fuel System Servicing

and Concurrent Servicing. NOTE: On aircraft equipped with foam in tanks, draining should be

terminated when the fuel flow decreases to a slow drip or becomes discontinuous. Draining is

required only once and may be accomplished on the flight line or inside the weighing facility

(Bldg. 1587 only).

6.16.6.5.2. (Added-Yokota) Provide fully qualified and dedicated towing/jacking personnel to

position the aircraft before, during and after weighing.

6.16.6.5.3. (Added-Yokota) Assist in the inventory of equipment when requested by QA.

6.16.6.5.4. (Added-Yokota) Coordinate available hangar space for W&B inspection. Include

extra time for inclement weather to ensure aircraft is dry if possible.

6.17. (Added-Yokota) 374 AW Specific Locally Developed Forms guidance:

6.17.1. (Added-Yokota) Terms Explained: The following terms are defined as they apply to

this instruction.

6.17.1.1. (Added-Yokota) Locally Developed Forms/Lists: Forms or lists produced locally to

record maintenance tasks or collect maintenance data and information. Examples may include

access panel sheets and inspection discrepancy sheets used during scheduled inspections, TCTOs

or extensive recurring maintenance.

6.17.1.2. (Added-Yokota) Preprints: Existing aircraft or support equipment forms overprints

used to record recurring maintenance tasks. Automated forms will be used when G081 is

available.

6.17.1.3. (Added-Yokota) Job Flow Packages: Locally developed maintenance packages

developed using the automated management system and loaded or printed when needed. Job


flow packages automate the required documentation of repetitive complex tasks such as engine

change, isochronal inspection, flight control maintenance, etc.


6.17.2.1. (Added-Yokota) The initiator of locally developed preprints, forms/lists and job flow

packages will:

6.17.2.1.1. (Added-Yokota) Submit all proposed locally developed preprints, forms/lists and

job flow packages to the 374 MXG/QA office using locally developed preprints, forms/lists and

job flow package authorization letter for coordination and approval. Proposals must be properly

coordinated with the initiator's squadron and routed through the applicable squadron’s

maintenance supervision.

6.17.2.2. (Added-Yokota) Maintenance supervision will:

6.17.2.2.1. (Added-Yokota) Ensure locally developed preprints, forms/lists and job flow

packages have been reviewed for content, accuracy, necessity and compliance with applicable

directives.

6.17.2.2.2. (Added-Yokota) Ensure locally developed preprints, forms/lists and job flow

packages are used for their intended purpose, documented in accordance with applicable

directives and filed and disposed as required.

6.17.2.2.3. (Added-Yokota) Coordinate with the 374 MXG/QA for review and

addition/deletion of any locally developed preprints, forms/lists and job flow packages.

6.17.2.3. (Added-Yokota) The 374 MXG/QA will:

6.17.2.3.1. (Added-Yokota) Ensure the submitting squadron’s maintenance supervision has

reviewed all submitted proposals.

6.17.2.3.2. (Added-Yokota) Ensure proposed locally developed preprints, forms/lists and job

flow packages do not duplicate existing preprints, forms/lists or job flow packages.

6.17.2.3.3. (Added-Yokota) Ensure locally developed preprints and forms/lists and job flow

packages have a date on each page so the previous version can be easily identified and purged.

6.17.2.3.4. (Added-Yokota) Approve/disapprove and assign control numbers to each approved

locally developed preprint, form/list and job flow package.

6.17.2.3.5. (Added-Yokota) Maintain a file copy of approved locally developed forms/lists and

job flow packages used within the maintenance complex.

6.17.2.3.6. (Added-Yokota) Coordinate annual reviews with maintenance supervision as

required.

6.17.2.4. (Added-Yokota) The 374 MO/PS&D will:

6.17.2.4.1. (Added-Yokota) Ensure QA and initiating squadron supervision review proposed

changes and deletions to job flow packages before they are updated in G081.

6.17.2.4.2. (Added-Yokota) Combine like packages used by both AMXS and MXS whenever

possible.

6.17.2.4.3. (Added-Yokota) As a minimum, coordinate with both AMXS Debrief, applicable

Flight Chief and QA annually for review of all 374 AW preprints and job flow packages.


6.17.2.4.4. (Added-Yokota) Upon completion of the annual review, make updates and changes

as needed in G081.

6.17.2.4.5. (Added-Yokota) Ensure approved changes to job flow Packages are input into

G081 within 7 duty days of receipt of approval.

6.17.2.4.6. (Added-Yokota) Limit access to G081 screen 9004 to schedulers only.

7.3.1.3. (Added-Yokota) Be familiar with and accomplish required tasks outlined in this

Chapter and supplements.

7.3.1.4. (Added-Yokota) The aircraft commander, senior maintenance representative or the

Impoundment Authority will notify the Maintenance Operations Center (MOC) of impoundment

for off station aircraft.

7.4.4. (Added-Yokota) Immediately report to Quality Assurance (QA) to receive an

impoundment brief and initiate the 374 MXG Aircraft/Equipment Impoundment Checklist.

7.4.4.1. (Added-Yokota) Quality Assurance (QA) will:

7.4.4.1.1. (Added-Yokota) Train and brief Impoundment Officials as required and IAW this

chapter.

7.4.4.1.2. (Added-Yokota) Monitor the impoundment to ensure compliance of all applicable

checklists, AFIs and provide technical assistance as required to support the impoundment

process and investigation.

7.4.4.1.3. (Added-Yokota) Review the impoundment report and applicable aircraft/equipment

forms prior to it being released to determine compliance with all directives.

7.4.5. (Added-Yokota) Be familiar with and accomplish requirements listed in this instruction,

all pertinent supplements, and the 374 MXG Aircraft/Equipment Impoundment Checklist.

7.4.6. (Added-Yokota) Brief the status of the aircraft/equipment impoundment investigation at

least once a day to the Impoundment Authority, MXG/CC or designated representative as long as

the aircraft/equipment is impounded.

7.6.2.1. (Added-Yokota) Maintenance Operations Center (MOC) will:

7.6.2.1.1. (Added-Yokota) Run the impoundment quick reaction checklist.

7.6.2.1.2. (Added-Yokota) Notify the transient aircraft’s home station of impoundment details.

7.6.3.1. (Yokota) Place the pre-printed Job Standard (JST) AFTO Form 781A in the aircraft

forms binder for aircraft that use G081. For aircraft that do not use G081 place the Red X

symbols and impoundment statements into the AFTO 781A and MIS. For equipment

impoundments place the Red X symbols and impoundment statements into the applicable AFTO

IMT 244 and the MIS. Maintenance will only be performed when authorized by the

Impoundment Official.

7.6.3.4.1. (Added-Yokota) Ensure the aircraft Cockpit Voice Recorder (CVR) and Digital

Flight Data Recorder (DFDR) are safeguarded by accomplishing the following in the event of a

potential safety-related incident:


7.6.3.4.1.1. (Added-Yokota) Coordinate with the Crashed, Damaged or Disabled Aircraft

Repair (CDDAR) Team Chief, QA and 374 AW/SE prior to the removal of the CVR and DFDR

if the aircraft is crashed, damaged or disabled.

7.6.3.4.1.2. (Added-Yokota) If warranted, direct the removal of the CVR/DFDR immediately

upon aircraft recovery (after aircraft is safe for maintenance/NON-CDDAR only) IAW

Applicable T.O.s. This action is imperative to preclude overwriting of critical data.

7.6.3.4.2. (Added-Yokota) Safeguard both the CVR and DFDR during the entire process until

one of the following occurs (as determined by 374 AW/SE, Safety Investigation Board (SIB)

President or the Impound Release Authority):

7.6.3.4.2.1. (Added-Yokota) The items are deemed Deficiency Report (DR) exhibits.

7.6.3.4.2.2. (Added-Yokota) The items are to be processed by Warner-Robins/ALC.

7.6.3.5. (Yokota) Cordon off the affected aircraft/equipment using cones (mandatory) and rope

(when determined necessary by the Impoundment Official) to prevent unauthorized entry. Place

impoundment sign (kept in QA) at the nose of the aircraft/engine/equipment at or near the Entry

Control Point (ECP).

7.6.4.2. (Yokota) Control all parts removed and tag with an AFTO Form 350 and applicable

serviceability/suspense tags.

7.6.6. (Yokota) Impoundment Release Authority will:

7.6.6.1. (Added-Yokota) Be familiar with and accomplish the required tasks listed in this

chapter.

7.6.6.2. (Added-Yokota) Receive a briefing and report from the Impoundment Official prior to

releasing the impounded aircraft/equipment. This briefing will include the following:

7.6.6.2.1. (Added-Yokota) Condition(s) resulting in impoundment.

7.6.6.2.2. (Added-Yokota) Actions taken to correct condition(s).

7.6.6.2.3. (Added-Yokota) Cost estimate required to correct condition(s).

7.6.6.2.4. (Added-Yokota) Actions taken to prevent recurrences.

7.6.11. (Added-Yokota) Impoundment Release. The Impoundment Official must follow all

procedures outlined in this chapter prior to aircraft/equipment release. If the aircraft is at an off-

station location that has maintenance support, every effort will be made to utilize the production

superintendent and/or QA at that location for forms review prior to requesting release from

impoundment.

8.2.1.2. (Added-Yokota) All units that dispatch tools/equipment to the flight line or aircraft

maintenance areas, or work on equipment destined for use on the flight line or an aircraft, will

follow Tool Management and Control program procedures. The objectives of this program are

to effectively and efficiently manage high-dollar tools and equipment and eliminate foreign

object damage (FOD) to aircraft, engines, training equipment and support equipment. UH-1N

and C-12 tool accountability and control are covered under their specific contracts.

8.2.3.2. (Added-Yokota) Warranty Tool Program:


8.2.3.2.1. (Added-Yokota) The purpose of the warranty/quality tool program is to ensure high

quality, industrial strength warranted tools are available for use in aircraft maintenance activities.

Warranted tools can be obtained through local contracts with warranty tool vendors. Detailed

management procedures are contained in AFH 23-123.

8.2.3.2.2. (Added-Yokota) When preparing background information for base contracting,

ensure all MIL-SPEC and other requirements are identified. Provide as much information as

possible on desired strength, finish (chrome or industrial), insulation, physical dimensions,

magnetic properties, laser etching and size of letters.

8.2.3.2.3. (Added-Yokota) Information covering warranty tools/items (company, POC,

warranty conditions, etc.) will be maintained in the Warranty – Non-Warranty – Spare

Tools/Items continuity binder/folder. All warranty spare tools/items will be controlled and

documented IAW this operating instruction, paragraph 8.3.6.7.5.

8.2.4.1.1. (Added-Yokota) Replacement tools will be purchased after authorization from

squadron tool room managers/CTK section NCOIC.

8.2.4.1.2. (Added-Yokota) Replacement tools will not be issued until all the pieces of a

broken/damaged tool are presented or documentation indicating the tool is lost and reported is

presented. Replacement tools must be marked with the CTK number prior to issue.

8.2.4.1.3. (Added-Yokota) Unserviceable tools removed from a CTK will be de-etched before

being placed in a separate, secure location until turned in for salvage purposes.

Unserviceable/broken tools will be replaced within 60 days or a requisition must be on file in the

Support Section showing the tool(s) is (are) on order. Account for all damaged or broken tools

on MXG Form 10. Items requiring turn in to DRMO or recycling will be secured and tracked

until processed for disposal.

8.2.4.1.4. (Added-Yokota) If one item of a set is unserviceable, the item will be removed and

handled as a broken tool. If the item is not to be replaced, the number of pieces on the tool

listing must be changed and annotated on the list.

8.2.4.1.5. (Added-Yokota) A quarterly inventory of all spare and expendable tools/items will

be accomplished and documented on a general-purpose or automated form. The inventory will

reflect accurate, on-hand amounts at all times. The NCOIC or designated representative will

enter their name, rank, date of inventory, balance on hand and location of tool storage. The

inventory will be kept in the (Warranty - Non-Warranty - Spare Tools/Items) continuity

binder/folder for at least 1 year.

8.2.4.1.6. (Added-Yokota) Expendable hand tools may be placed on bench stock. Examples of

expendable tools include saw blades, acid brushes, wire brushes, disposable gloves, etc.

However, if expendables are placed on bench stock, strict accountability and control procedures

must be established. CTK Custodians will ensure expendable tools are kept secure and

exchanged on a one-for-one basis.

8.2.4.2. (Added-Yokota) HAZMAT materials will be stored and controlled IAW the Yokota

Waste Management Program Guide.

8.2.4.2.1. (Added-Yokota) All HAZMAT materials will be stored/secured in an approved

locker.

8.2.4.2.2. (Added-Yokota) All HAZMAT items will be required to have issued barcode label.


8.2.4.2.3. (Added-Yokota) TCMax will be used to control dispatchable HAZMAT items. If

TCMax is not available, the AF Form 1297 will be used.

8.2.4.2.4. (Added-Yokota) One permanently marked EID per container is required.

8.2.4.2.5. (Added-Yokota) HAZMAT containers will not be leaking. HAZMAT containers

will be clean, and serviceable. If leaking, the user will take appropriate actions to contain the

leaking fluids (i.e., pig mat or absorbent padding) provided the control measures do not present

an additional fire hazard.

8.2.4.2.6. (Added-Yokota) HAZMAT items, individual or part of a kit, that are required to be

closed when not actively being used will have the lids firmly closed when stored in lockers.

8.2.4.2.7. (Added-Yokota) Hazmat that has been used or is in use no longer falls under the

shelf-life program; it is in its “service life”. Service life determines how long a material is usable

once placed in service and is defined by TO, manufacturer data, or AFI guidance (i.e., once

applied to the aircraft, paint has a service life of 6 years).

8.2.4.2.7.1. (Added-Yokota) Service life is not intended to cover items opened and partially

used, then closed and placed back on the shelf for later use (i.e., a two-part sealant kit with only a

portion of the contents mixed and used may be placed back on the shelf for later use but while on

the shelf still must adhere to shelf life guidelines). These items will be disposed of once their

shelf life/expiration date is exceeded.

8.2.4.3. (Added-Yokota) Hazardous Materials/Environmental Impact Analysis Process. CTK

Custodians/NCOICs will be aware of the environmental impact of all hazardous materials issued

from or stored in the CTK and will be aware of the procedures listed in the Yokota AB

Hazardous Waste Management Plan.

8.2.5.2. (Added-Yokota) On-site transfers of CTKs are authorized and the following

procedures are used:

8.2.5.2.1. (Added-Yokota) The CTK will not be swapped from individual to individual on the

next shift unless approved by the Production Superintendent.

8.2.5.2.2. (Added-Yokota) The individual on the incoming shift will obtain a blank AF Form

1297, Temporary Issue.

8.2.5.2.3. (Added-Yokota) The outgoing and incoming individuals will inventory the CTKs.

The incoming individual will annotate the AF Form 1297. The CTK monitor will clear the

outgoing individual and maintain the AF Form 1297 or locally approved form until the CTK has

been turned in or TCMax has been updated to reflect the new user of the CTK.

8.2.5.2.4. (Added-Yokota) If a discrepancy exists (e.g., undocumented missing tool, broken

tools), personnel will immediately notify appropriate supervision. See section 11 of this

instruction (Lost Tool/Object Procedures). Transfer of CTK will not take place under these

circumstances.

8.2.7.1. (Added-Yokota) The 374 MXG QA assigns a prefix to the beginning of CTK numbers

assigned to each section. Every CTK will strictly adhere to alphabetical/identification prefixes

allotted/assigned to it by QA (Table 8.1). The CTK numbers will begin with the assigned prefix

followed by a set of digits consisting of any combination of numbers/letters/symbols that will

ease the use of identification.


Table 8.1. (Added-Yokota) CTK WWID Prefix designators by squadron/section.

Section Yokota AB Squadron Shop WWID

374 MXG/MO

Quality Assurance YM Q Q YMQQ

UH-1 Contractor YM Q D YMQD

Military Training Section YM Q T YMQT

374 AMXS

Support Flight YM A O YMAO

374 MXS

Munitions YM M A YMMA

Aircraft Structural Maintenance (ISO/Letter

Check)

YM M B YMMB

Crash Recovery YM M C YMMC

Transient Alert YM M D YMMD

Repair and Reclamation / Wheel and Tire YM M E YMME

Fuel Systems YM M F YMMF

AGE YM M G YMMG

TMDE YM M H YMMH

Mobility Section YM M M YMMM

Nondestructive Inspection YM M N YMMN

Electro / Environmental YM M O YMMO

Corrosion Control YM M R YMMR

Aircraft Structural Maintenance YM M S YMMS

Aircraft Metals Technology YM M T YMMT

Propulsion Test Cell YM M V YMMV

ISO Support Section / Propulsion ISO YM M X YMMX

Propulsion Material Support YM M Z YMMZ

730 AMS

730th Air Mobility Squadron YM L G YMLG

374 OSS

AFE Main Shop YM O S YMOS

AFE Satellite Shop YM M I YMMI

27 SOMXG (CV-22 DET)

CV-22 Support YM V S YMVS


8.2.7.2. (Added-Yokota) Each CTK will be individually numbered. The CTK identification

must be readable. All dispatchable CTKs will have reflective material on all sides to ensure

maximum visibility.

8.2.7.3. (Added-Yokota) Tools or equipment issued individually from a tool room/support

section must be marked with an equipment identification designators (EID).

8.2.7.3.1. (Added-Yokota) Tools will have only one identifier number. Dual etching (different

numbers) is not authorized. If etched tools need to be re-etched due to CTK re-numbering, there

will be a reasonable attempt made to remove old etchings without rendering the tool

unserviceable.

8.2.7.3.2. (Added-Yokota) Consumable liquids will not be dispatched to the flight line in their

original container until permanently/indelibly marked to identify the CTK agency issuing that

item.

8.2.8.1. (Added-Yokota) Personal Issued Tools/Equipment and Personal Protective Equipment

(PPE):

8.2.8.1.1. (Added-Yokota) Identify personal issue equipment (ear defenders, reflective belts,

and other items purchased and issued by the unit) with minimum first initial, last name, and the

individual’s employee number.

8.2.8.1.2. (Added-Yokota) Personally procured equipment or tools are not authorized on the

flight line or in maintenance work centers unless they are controlled via normal CTK procedures.

Equipment/tools issued by the currently assigned unit are not considered personal tools. If they

are lost, follow the guidelines outlined in paragraph 8.9.

8.2.9.4. (Added-Yokota) Rag Control:

8.2.9.4.1. (Added-Yokota) Positive control of rags must be enforced. Rag control applies to all

374 MXG organizations and personnel. While marking or identifying each rag with a CTK

number is not necessary, issue and receipt procedures will be established to ensure positive

control. Rags of uniform size and colors, such as those available through GSA and commercial

contract suppliers, may be used to facilitate control procedures.

8.2.9.4.2. (Added-Yokota) Rags and containers will be treated like tools and will be controlled

using the same methods as other tools. Lost tool/object procedures will be followed for missing

or lost rags according to paragraph 8.9.

8.2.9.4.3. (Added-Yokota) Authorized methods of positive rag control may include but are not

limited to:

8.2.9.4.3.1. (Added-Yokota) Issuing rags on a one-for-one swap regardless of quantity.

8.2.9.4.3.2. (Added-Yokota) Issuing a predetermined number of rags with CTKs.

8.2.9.4.3.3. (Added-Yokota) Issuing rags in pre-packaged containers with the number of rags

marked on each container.

8.2.9.4.4. (Added-Yokota) The CTK Custodian will establish procedures to ensure how many

rags are on hand (segregate clean and dirty/oily rags).


8.2.12.1. (Added-Yokota) When a depot team, factory representative or contract field team

performs on-equipment maintenance within the 374 MXG, they will follow this instruction for

tool accountability.

8.2.17. (Added-Yokota) When two or more work centers operate a single support section, the

senior maintenance manager will establish CTK procedures for forward operating locations

(TDYs, deployments, exercises, etc.). If no local guidance is available, 374 MXG personnel will

follow the policies/procedures contained in this instruction.

8.3.2.1.1. (Added-Yokota) Flight CC/Chiefs and/or Section NCOICs/Chiefs (or equivalents)

will review, date and sign the Equipment Accountability Listing (EAL)/Master Inventory Listing

(MIL) at least annually or when a new EAL/MIL is required.

8.3.3.1. (Added-Yokota) Tools and toolboxes will be clean, foreign-object-free, dry, oiled if

applicable, and serviceable.

8.3.5.1.1. (Added-Yokota) When an item is in a container with multiple pieces such as a drill

index, fitting kit, etc., the description on the contents listing will include a detailed breakdown to

include a description and quantity of each piece contained inside. Expendable hand tools such as

apexes, files and file cleaners will be etched or installed in an etched/labeled container prior to

issue as replacements. Unserviceable expendable items will be turned in to the tool room/crib

personnel before replacement expendable items are issued.

8.3.5.3. (Added-Yokota) Inlays are the preferred method for maintaining tools inside all CTKs.

Inlays will be cut deeply enough to firmly retain the tool/item. Inlays may be highlighted to

provide increased visibility. Inlays will not be cut to touch or overlay each other. If an item is

deleted, the inlay for that item will be permanently filled with foam or sealant.

8.3.5.3.1. (Added-Yokota) Tools may be shadowed inside CTKs if inlays are not feasible. Use

paint or permanent marker to outline the shape of a tool. Hooks, clips, bungee cords or other

suitable means may be used to mount tools over a shadow.

8.3.6.1.1. (Added-Yokota) All forms will be inserted into a weather-resistant pouch or bag

contained inside the CTK for inventory purposes. When it is not feasible to include the MIL or

AFTO Form 244/245, Industrial Support Equipment Record, (due to size, shape, etc.), a folder

will be maintained in the tool room for conducting inventories or equipment annotations (IAW

00-20-1).

8.3.6.5.2. (Added-Yokota) Consumable Tool Items (CTK/Spare Tools):

8.3.6.5.2.1. (Added-Yokota) Consumable containers will be marked with the CTK Equipment

Identification Designator (EID) number.

8.3.6.5.2.2. (Added-Yokota) Consumable items are inventoried in conjunction with the tool kit

inventory and replenished as necessary. When a consumable is used up, it is immediately

replaced or annotated on the CTK’s consumables list or in TCMax.

8.3.6.5.2.3. (Added-Yokota) Lost consumables and/or their containers will be treated as “lost

item”, see para 8.9 for Lost Tools/Object procedures.

8.3.6.5.2.4. (Added-Yokota) The CTK Custodian will submit requests for additions/deletions

to the authorized consumable list to the CTK NCOIC.


8.3.6.5.2.5. (Added-Yokota) Consumables must be serviceable and meet shelf life

requirements and Hazard Communication Program instructions concerning hazardous chemicals,

if applicable.

8.3.6.7.1.2. (Added-Yokota) Pen will be used for hard copy MIL documentation with CTK

Custodian initials/date

8.3.6.8. (Added-Yokota) A means of containing foreign objects (pouch, can, bag, etc.) will be

maintained in every dispatchable CTK and tool pouch (excluding test equipment) and will be

included on the MIL.

8.3.9.1.1. (Added-Yokota) Engine Blade Blending Tools:

8.3.9.1.1.1. (Added-Yokota) The Maintenance Operations Officer/Superintendent will

designate individuals authorized access to blade blending tools on the Special Certification

Roster (SCR). Individuals will provide certification of training prior to equipment checkout.

8.3.9.1.1.2. (Added-Yokota) Engine blade blending blue permanent markers will be stored in a

secured locker or access controlled area.

8.3.10.1.1. (Added-Yokota) Remove all potential FOD hazards from tools when possible, to

include pocket clips, spare bulbs, etc., prior to placement in CTKs. If items (metal tags, lanyard,

caps, etc.) are attached to tools/equipment, they must be securely attached.

8.3.14. (Added-Yokota) Functional Responsibilities:

8.3.14.1. (Added-Yokota) The 374 MXG Quality Assurance (QA) office is the office of

primary responsibility (OPR) for all changes/waivers to this instruction.

8.3.14.2. (Added-Yokota) Squadron Maintenance Operations Officer/Superintendent:

8.3.14.2.1. (Added-Yokota) Has overall management responsibility of the CTK program

within their area of responsibility.

8.3.14.2.2. (Added-Yokota) Monitors CTK requirements.

8.3.14.3. (Added-Yokota) CTK NCOIC/Custodian will:

8.3.14.3.1. (Added-Yokota) Consider deployment tasking and coordinate CTK content

requirements with the Unit Deployment Manager.

8.3.14.3.2. (Added-Yokota) Ensure strict control of tool room locks and keys.

8.3.14.3.3. (Added-Yokota) Ensure strict control for managing lost/broken tool replacement.

Maintain the original copy of lost tool reports for a minimum of 1 year.

8.3.14.3.4. (Added-Yokota) Develop a continuity folder/book for all tool rooms. The

folder/book will contain, at a minimum, letters of appointment, inspection procedures, policy

letters, and the bench stock shadow board master list (if applicable).

8.3.14.3.5. (Added-Yokota) Inventory all replacement tools quarterly. The quarterly inventory

of all on-hand replacement tools will be documented and kept on file until the next inventory is

completed.

8.3.14.4. (Added-Yokota) CTK Custodian/Tool Crib Representative will:


8.3.14.4.1. (Added-Yokota) Ensure strict control of the CTKs during issue and receipt to

include a 100-percent inventory upon turn-in and checkout.

8.3.14.4.2. (Added-Yokota) Annotate all changes to the CTK contents list in pen with CTK

Custodian initials/date or update changes directly in TCMax and print out a new MIL.

8.3.14.4.3. (Added-Yokota) Ensure annual inventories of all tools and equipment are

accomplished.

8.3.14.4.4. (Added-Yokota) Ensure contents of non-dispatchable CTKs (cabinets) are opened

and inventoried once each shift. The individual performing the inventory ensures all CTKs and

PPE are on-hand and accounted for.

8.3.14.4.5. (Added-Yokota) Ensure tools are serviceable and free of corrosion that exceeds

minor surface rust/oxidation. Document discrepancies if suspect tools cannot be repaired or

replaced.

8.3.14.5. (Added-Yokota) Production Supervision Office will ensure a lost tool report is filed

in the aircraft jacket file when a tool is lost on the aircraft and not recoverable.

8.4.10. (Added-Yokota) Precision Measurement Equipment Laboratory (PMEL) and Test,

Measurement and Diagnostic Equipment (TMDE) calibrated tools may be added to CTKs.

Calibration intervals in TO 00-20-14, Air Force Metrology And Calibration Program, and TO

33K-1-100-2MT-0, Calibration Procedures For TMDE, (kept as a database in PMEL) will be

followed. PMEL and TMDE tools or equipment added to CTKs must be properly identified as

part of that CTK.

8.5.1.2.1.1.1. (Added-Yokota) TCMax will show the current availability/status of the CTK and

all of its contents at all times. TCMax (PMEL Automated Management System for TMDE

section) will also be used to track PMEL requirements and document/track serviceability

inspections.

8.5.1.3.1. (Added-Yokota) AF Form 1297 or a locally developed tracking sheet will be used to

track CTK issued/returned tools/equipment in the event of TCMax failure or in the event TCMax

otherwise becomes unavailable. The locally developed tracking sheet will have as a minimum:

date, time, employee number, and WWID and nomenclature of the item issued. These sheets

will be kept until TCMax is back on line and a full inventory has been accomplished.

8.5.3.3. (Added-Yokota) CTKs designated for use in an off-equipment environment or non-

dispatchable (cabinets) may be left open for use during a shift. Contents of non-dispatchable

CTKs are inventoried at the beginning of each shift and annotated on the applicable form.

8.5.3.4. (Added-Yokota) The same individual that signs out a CTK or a kit cannot sign it back

in. If there are no other personnel on duty, contact MOC to notify AMXS/MXS Production

Superintendent to inspect the CTK.

8.5.3.5. (Added-Yokota) The individual accepting the CTK retains responsibility for it and its

contents until relieved by the next person signing for it or transferred on an AF Form 1297

during a job site transfer (N/A Aircrew).

8.5.3.6. (Added-Yokota) CTKs in use on the flight line or during on-equipment maintenance

will be inventoried at the completion of each task, when moving to another aircraft, at the end of


each shift, prior to aircraft launch, and when leaving the aircraft for an extended period, (e.g.,

during a parts run or break). CTKs will be secured when left unattended.

8.5.4.4. (Added-Yokota) CTK special tools/WRM assets will be inspected annually for

serviceability and inventory IAW AFI 25-101, Air Force War Reserve Materiel (WRM)

Guidance and Procedures.

8.5.8. (Added-Yokota) Mobility/Contingency Kits:

8.5.8.1. (Added-Yokota) CTKs deployed individually or as a package to a forward position

will be collected/controlled by the senior maintenance manager and incorporated into a

temporary Tool Room.

8.5.8.2. (Added-Yokota) If procedures cannot be established to accommodate a tool room at a

forward location, the senior maintenance manager may approve issue of CTKs using a locally

developed tracking tool/form or AF Form 1297, provided inventories are completed in

accordance with paragraph 8.5.3.

8.5.8.3. (Added-Yokota) War Reserve Materiel (WRM): While components are in WRM

status, equipment may not be used to perform maintenance/testing activities without “breaking

the seal.” Custodial personnel may open sealed assets for inspection, servicing or minor

maintenance (cleaning, changing/charging batteries, etc.) that does not affect the operability of

the equipment.

8.7.1.1. (Added-Yokota) All locally manufactured tools and equipment not listed in approved

technical data must be approved by the 374 MXG/CC or CD prior to manufacture of the item

using Attachment 11.

8.7.1.2. (Added-Yokota) The owning section will supply description, justification, and all

relative information, including pictures, to QA prior to the tool being approved or put into use.

8.7.1.3. (Added-Yokota) CTKs will maintain a location and status of all locally manufactured

tools.

8.7.1.4. (Added-Yokota) QA and the respective work center will maintain a copy of all

approval letters.

8.7.2.1. (Added-Yokota) The review is documented in the QA Local Man Tools continuity

binder and the QA SharePoint.

8.8.2.1.3. (Added-Yokota) Tool cribs will be locked when not attended and secured at all

times. Access will be limited to tool room personnel, wing/group/squadron leadership and

production personnel.

8.8.2.2.2.1.1. (Added-Yokota) If dispatchable CTKs are left unattended outside their work area

and not in a controlled/secure area, the CTK will be secured either inside a locked vehicle or

with a cable lanyard to an immobile object. A controlled area is considered to be anything inside

of the airfield restricted area boundaries (Red Lines) or inside a hangar/facility. Tool boxes left

unattended inside the controlled area will be locked, but do not need to be secured to an

immobile object. Note: Do not secure tool boxes in such a way that would impede emergency

situations (e.g., emergency tow, emergency exits).

8.8.2.2.2.1.2. (Added-Yokota) Dispatchable/deployable CTKs will not be fitted with

combination padlocks (exception is ISU-90s loaded on aircraft for transport). Combination


padlocks may be included in the CTK inventory for the purpose of securing toolboxes to

immobile objects or controlling access to aircraft.

8.8.2.2.2.1.3. (Added-Yokota) CTK keys will be etched with the WWID number and will have

a durable streamer/plate securely attached. Snap rings will not be used unless the ends are

welded. CTKs without a built-in lock must use a keyed padlock etched with the CTK’s WWID

identification number.

8.8.2.2.2.1.4. (Added-Yokota) Bolt cutters are considered a security-controlled item and when

not in use they will be secured.

8.9.1.1. (Added-Yokota) Lost Tool/Object Procedures.

8.9.1.1.1. (Added-Yokota) Procedures for tools lost on an aircraft:

8.9.1.1.1.1. (Added-Yokota) If a tool is found missing from a CTK, and was previously used

on an aircraft that has taxied and/or is airborne, the Pro Super will notify the MOC to initiate the

Lost Tool Quick Reaction Checklist (QRC). Aircrew will attempt to locate and secure the lost

tool. If the lost tool is not secured, the Pro Super will notify MOC to recall the aircraft. MOC

will then contact Command Post to initiate recalling the affected aircraft. After this recall, a

thorough search will be conducted.

8.9.1.1.1.2. (Added-Yokota) If a tool is found missing from a CTK, and was previously used

on an aircraft that has not taxied and/or is not airborne, after a 30 minute initial search of the

affected area, the Production Superintendent (Pro Super) will notify the MOC. The individual

who lost the tool will also notify their CTK or tool monitor and initiate a MXG Form 4 (Lost

Tool / Object Report). Operations personnel will follow the same reporting procedures. The

CTK NCOIC will ensure a copy of the completed report is forwarded to the 374 AW FOD

Monitor within 72 hours.

8.9.1.1.1.3. (Added-Yokota) If an item/object is discovered missing while performing an

inspection/maintenance, the individual who discovered this will search the immediate work area

for this missing item and notify his Pro Super. If not found within 30 minutes, the Pro Super will

notify MOC and the individual will initiate a MXG Form 4. The on shift Pro Super or Section

Chief will ensure the user routes a completed report to the 374 AW FOD Monitor within 72

hours.

8.9.1.1.1.4. (Added-Yokota) The MOC will initiate the appropriate QRC. The MXG/CC or

CD will determine if aircraft impoundment is necessary.

8.9.1.1.1.5. (Added-Yokota) If the item is not found, the respective squadron supervision will

determine when the search will be terminated.

8.9.1.1.2. (Added-Yokota) If a tool is discovered missing and it has been positively determined

the tool was not used on an aircraft, after a 30 minute search of the affected area, the individual

with responsibility for the tool (with assistance from the CTK custodian) will initiate an MXG

Form 4, Lost Tool/Object Report, and notify the Production Superintendent. Ensure a copy of

the completed report is forwarded to 374 AW FOD Monitor within 72 hours.

8.10. (Added-Yokota) Support Equipment (SE) Management.


8.10.1. (Added-Yokota) Support equipment (SE) is defined as vehicular SE; Aerospace

Ground Equipment (AGE); Test, Measurement and Diagnostic Equipment (TMDE); munitions

handling and test equipment; test equipment; and special tools requiring scheduled inspections.

8.10.2. (Added-Yokota) Support equipment (other than AGE) will be controlled, maintained

and inspected in the same manner as CTKs.

8.10.3. (Added-Yokota) Dispatchable equipment is defined as SE (other than AGE) that is

dispatched outside CTK.

8.10.3.1. (Added-Yokota) Dispatchable equipment that contains more than one item will have

a MIL (extracted from TCMAX) placed inside the equipment for inventory purposes. The MIL

will contain a breakdown and location of all items in/on the equipment.

8.10.4. (Added-Yokota) Support equipment inspections will be documented on AFTO Form

244/245, TCMax, and MIL as applicable, G081 is optional. (Exception: AGE equipment must

use G081.)

8.10.4.1. (Added-Yokota) Inspection types are as follows and are defined in TO 00-20-1 or the

applicable equipment technical data.

8.10.4.1.1. (Added-Yokota) Servicing Inspections. This inspection is an equipment condition

inspection and is defined in the equipment’s applicable technical data. Powered/Non Powered

AGE support equipment will be service inspected during initial placement on the ready line. At

a minimum, this will consist of a visual inspection of the equipment for defects or irregularities

affecting serviceability and or security. Each inspection will be documented on Part II of the

AFTO Form 244.

8.10.4.1.2. (374 AW-Added) Operator Inspections. To ensure serviceability and safety of the

equipment, the operator’s inspection will consist of a review of the forms for current status and a

visual inspection of the equipment for defects and adequate servicing. If during the inspection a

defect is discovered, the operator will record the defect in Part V of the AFTO Form 244/245 and

contact the equipment’s owning work center.

8.10.4.1.3. (Added-Yokota) All other inspections are defined in TO 00-20-1 or the owner’s

manual and will be adhered to.

8.10.5. (Added-Yokota) Support equipment AFTO Form 244/245 management:

8.10.5.1. (Added-Yokota) An AFTO Form 244 supervisory review will be conducted every

180 days. At a minimum, this will ensure that the AFTO Form 244 matches G081 screens

#8066, #8024 and #9112, in addition to checking for any discrepancies. When a new AFTO

Form 244 is initiated, the initial supervisory review date will match the initial period covered

date in part I.

8.10.5.2. (Added-Yokota) Forms may be maintained in a specific separate file when use or size

of the equipment makes it hazardous or impractical for the forms to accompany the equipment.

These forms will be grouped together by type of equipment and kept in a file or binder in either

the work center having primary responsibility for the end item or in the production

control/support section having scheduling responsibility for the end item.

8.10.5.3. (Added-Yokota) The Standard Reporting Designator (SRD) Code may be used on

AFTO Form 244, Part I, Block 8. The “SUP DOC NO.” block of AFTO Form 244/245, Part V


will be used to enter the base supply document number(s) regardless if using MIS. Uses of

AFTO Form 244/245 to address unique requirements are not authorized without approval from

the 374 MXG/CC.

8.10.6. (Added-Yokota) Use of Locally Developed Oil, Hydraulic and Nitrogen Servicing

Tracking Form management.

8.10.6.1. (Added-Yokota) All Oil, Hydraulic, and Nitrogen servicing carts and Hydraulic test

stands will have a 374 MXG Form 6 included in the rain proof bag along with the AFTO Form

244/245.

8.10.6.1.1. (Added-Yokota) Users must document 374 MXG Form 6 after servicing aircraft

with Oil, Hydraulic, or Nitrogen servicing carts or after using Hydraulic test stands.

8.10.6.1.2. (Added-Yokota) Servicing cart users are responsible for initiating new tracking

forms when the current one becomes full or unusable. Users ensure completed MXG Form 6’s

are forwarded to AGE Flight or Accessories Flight for filing.

8.10.6.2. (Added-Yokota) 374 MXS AGE Flight will maintain the latest complete MXG Form

6, for historical purposes, on oil, hydraulic, and gaseous nitrogen servicing carts.

8.10.6.3. (Added-Yokota) 374 MXS Accessories Flight, Electrical Environmental section will

maintain the latest complete MXG Form 6, for historical purposes, for gaseous nitrogen cylinder

and liquid nitrogen carts.

9.8.1.4.1. (Added-Yokota) Precious metals will be strictly controlled in a secure area. All

precious metals will be issued on a one-for-one basis only.

9.8.1.7. (Added-Yokota) Bench stock items shall be stored one specific item type per bin. Co-

mingling of items is prohibited; however, items of the same specific type but not identical may

be stored together. Example: All batteries of the same capacity (D-cell) may be stored in the

same bin, even if they are made by different manufacturers and have dissimilar appearances.

9.20.1.1. (Added-Yokota) Specific 374 AW instructions for the local manufacture of parts is

included below.


9.20.3.1. (Added-Yokota) The Flight Chief of the fabricating activity has local manufacture

(LM) approval authority for:

9.20.3.1.1. (Added-Yokota) Stock listed items coded for LM (Source of Supply [SOS] JBD or

Illustrated Parts Breakdown Source Maintenance Repair [SMR] Code MF* or AF* with

acquisition advice code [AAC] F).

9.20.3.1.2. (Added-Yokota) Non-stock listed items (items without an assigned stock number)

to be made per technical order (TO)/drawing specification.

9.20.3.2. (Added-Yokota) 374 MXG/CC (or representative designated in writing) has LM

approval authority for:

9.20.3.2.1. (Added-Yokota) Stock listed items not coded for LM (not SOS JBD or SMR Code

Manufactured or fabricated at intermediate level [MF*]).


9.20.3.2.2. (Added-Yokota) Non-stock listed items to be made per other than technical

order/drawing specification. These items, once approved by the MXG/CC, require coordination

through the applicable systems engineer via technical assistance request (TAR) per TO 00-25-

107. See paragraph 9.20.7.4.

9.20.3.3. (Added-Yokota) The section Non-Commissioned Officer In-Charge (NCOIC) has

approval authority for LM requests (other than LM tools) required to facilitate their own

section’s production. Maintenance performed by these sections requires extensive use of custom

made templates, patterns, forming and holding fixtures, hardware extraction/installation tools

and alignment devices on a routine basis. Manufacture of these items is covered in their technical

training, Career Development Course books, general methods and procedural TO and do not

require LM paperwork.

9.20.3.4. (Added-Yokota) LM of munitions related items and equipment must be processed

and approved IAW Chapters 2, 4, and 10 of this instruction.

9.20.3.5. (Added-Yokota) Tools requiring LM will be approved by the 374 MXG Quality

Assurance Office IAW this instruction.

9.20.3.6. (Added-Yokota) MICAP LMs do not follow the procedures listed in this document.

All MICAP requests must be processed IAW AFH 23-123.

9.20.4. (Added-Yokota) Requesting Activity will:

9.20.4.1. (Added-Yokota) Research item requiring LM and ensure it cannot be obtained

through normal supply channels. If item can be ordered, it will be placed on order with

appropriate priority. The supply document number associated with this transaction will be

required when processing LM request. Man hours required to complete the project and

equipment availability will also be considered.

9.20.4.2. (Added-Yokota) Complete a YOKOTA AB Form 36, Local Manufacture Request,

and route as required for the type of part being requested for LM. See paragraphs 9.20.3.1. and

9.20.3.2.

9.20.4.3. (Added-Yokota) Create and load a work order in GO81 or the Integrated

Maintenance Data System (IMDS) for production tracking and documentation against the LM.

If more than one shop is involved in the manufacture process, a work order will be created for

each work center.

9.20.4.4. (Added-Yokota) Provide the following supporting documentation to 374 LRS Flight

Service Center (FSC):

9.20.4.4.1. (Added-Yokota) Approved LM request form (YOKOTA AB 36).

9.20.4.4.2. (Added-Yokota) DD Form 1348-6, Single Line Item Requisition System Document,

AF Form 2005, Issue/Turn-In Request, AF Form 601 (if required), Equipment Action Request.

9.20.4.4.3. (Added-Yokota) Applicable drawings/blueprints/depot guidance/copies of technical

orders or reference specifications for the requested LM. These items may be found in the

Integrated Electronic Technical Manual System (IETMS), the Joint Engineering Data

Management Information and Control System (JEDMICS), or obtained from local Air Force

Engineering Technical Service (AFETS) representatives.


9.20.4.4.4. (Added-Yokota) Supply/purchase order documents for materials needed for the LM

(may include raw materials, hardware, and/or tooling).

9.20.4.4.5. (Added-Yokota) Paper copies of GO81 or IMDS work order(s) for LM.

9.20.4.5. (Added-Yokota) Route supporting documentation to the manufacturing work center

and appropriate approving official(s) as identified in paragraphs 9.20.3.1 and 9.20.3.2.

9.20.5. (Added-Yokota) Manufacturing Activity will:

9.20.5.1. (Added-Yokota) Verify ability to fabricate the requested LM. A fabricating section

7-level will verify ability to manufacture and consult with requester concerning possibilities of

LM and determine material specifications/proper quantities of materials/consumable parts

needed. If the requester already has a LM form (YOKOTA AB 36) available, annotate any

pertinent information and refer to FSC if manufacture is possible. Price of the item will be based

on availability of material and not total cost of item.

9.20.5.2. (Added-Yokota) Execute requested LM. Once paperwork is approved and

materials/consumables received, completion of item will be based upon priority requested. Items

with same priorities, work requests are accomplished in the order received unless instructed

otherwise by fabricating activity’s production supervision.

9.20.5.3. (Added-Yokota) Contact FSC upon completion of LMs and forward property for

receipt processing.

9.20.6. (Added-Yokota) Supply Procedures for Local Manufacture:

9.20.6.1. (Added-Yokota) The normal procedure for requesting a LM item is for the requesting

activity to submit the request through the LRS/Supply activity. However, there are situations

where mission requirements drive expedited processing of the LM. In these cases, the routing of

the LM item request through LRS/Supply activity may be deferred (by the fabricating activity’s

Squadron MOO/Superintendent or higher) while the part is being made but must be routed

immediately after LM completion.

9.20.6.2. (Added-Yokota) 374 LRS (FSC) will appoint, in writing, a primary and alternate

Local Manufacture Manager. The LM Manager will:

9.20.6.2.1. (Added-Yokota) Create a file of all LM requests. Folders should contain the

following:

9.20.6.2.1.1. (Added-Yokota) Approved LM requests (YOKOTA AB 36).

9.20.6.2.1.2. (Added-Yokota) Applicable drawings/blueprints/depot guidance/copies of

technical orders or reference specifications for the requested LMs.

9.20.6.2.1.3. (Added-Yokota) Supply/purchase order documents for materials/consumable

parts.

9.20.6.2.1.4. (Added-Yokota) Paper copies of IMDS work orders for LMs.

9.20.6.2.2. (Added-Yokota) Process documents IAW AFH 23-123 for all LMs submitted.

These will include at a minimum:

9.20.6.2.2.1. (Added-Yokota) Approved LM request (YOKOTA AB 36).

9.20.6.2.2.2. (Added-Yokota) DD Form 1348-6, AF Forms 601 or 2005.


9.20.6.2.2.3. (Added-Yokota) Applicable drawings/blueprints/depot guidance/copies of

technical orders or reference specifications for the requested LM.

9.20.6.2.2.4. (Added-Yokota) Paper copies of IMDS work order(s) for LM.

9.20.6.2.3. (Added-Yokota) If the requested LM item is not stock listed, work with Customer

Service personnel to assign an ERRCD and a locally assigned stock number after the 1348-6

paperwork is completed.

9.20.6.2.4. (Added-Yokota) Assist in verifying parts availability.

9.20.6.2.4.1. (Added-Yokota) If parts are available, bits and pieces along with all paperwork

will be delivered, by the requestor or LRS, along with the required paperwork to the repair

section for manufacture.

9.20.6.2.4.2. (Added-Yokota) If parts are not available and the requirement is MICAP the FSC

local manufacture manager will input the bits and pieces requirements with TEX “7”;

appropriate MICAP UJC; JCN in the work-order field, aircraft tail number (SRD and WUC) in

the mark-for, and notify the AFGLSC who will accomplish MICAP verification and requisition

processes.

9.20.6.2.4.2.1. (Added-Yokota) To complete the MICAP process, when bits and pieces are

received they will be delivered, by the requestor or LRS, along with the required paperwork to

the appropriate repair shop for manufacture of the item.

9.20.6.2.4.2.2. (Added-Yokota) The request for the LM item will remain on order until the

item is complete and received by Supply for REC/DOR processing.

9.20.6.2.4.3. (Added-Yokota) For non-MICAP requirements, the FSC LM manager will back

order the requirements with the appropriate UJC and JCN in the work order field.

9.20.6.2.5. (Added-Yokota) Once all paperwork is completed and all bits and pieces are

received/available they will be delivered, by the requestor or LRS, along with the required

paperwork to the repair section for manufacture.

9.20.6.3. (Added-Yokota) If the requested LM item is beyond base maintenance capability to

manufacture, maintenance personnel will return the work order request with the reason for non-

manufacture to Stock Control.

9.20.6.3.1. (Added-Yokota) Stock Control will cancel the LM due-in detail record and assign

REX code “2”.

9.20.6.4. (Added-Yokota) Upon completion of manufacture the finished product will be

forwarded back to FSC for REC/DOR processing, and then issued to the customer.

9.20.7. (Added-Yokota) Local Manufacture of Aircraft Components and Hardware:

9.20.7.1. (Added-Yokota) Aircraft components, assemblies, and hardware requiring LM fall

into two categories:

9.20.7.1.1. (Added-Yokota) Items coded as LM per applicable TO guidance have automatic

approval and may be locally manufactured without additional authority beyond the TO.

Paperwork shall still be routed as identified in paragraphs 9.20.4. thru 9.20.4.4.5. of this

instruction.


9.20.7.1.2. (Added-Yokota) Items that have other SMR codes may be locally manufactured

providing the following two conditions are met:

9.20.7.1.2.1. (Added-Yokota) The SMR code does not specifically prohibit LM.

9.20.7.1.2.2. (Added-Yokota) Manufacture can be accomplished without deviation from

technical drawings, blueprints, equipment technical directives or covered under applicable

general maintenance practices and within the capabilities of the primary work center.

9.20.7.2. (Added-Yokota) Procurable assets may be approved by the 374 MXG/CC or

designated representative. Procurable assets will only be locally manufactured when normal

procurement will result in unacceptable mission impact as determined by the production

superintendent. Example: Part is SMR-Coded PAA, without a favorable EDD, fabricating

activity has all capabilities to manufacture IAW technical drawings, blueprints, equipment

technical directives or covered under applicable general maintenance practices and within the

capabilities of the primary work center. Approval authority is 374 MXG/CC or designated

representative.

9.20.7.2.1. (Added-Yokota) Requesting activity will contact COSO or MSL to initiate

procedures listed in paragraph 9.20.4.

9.20.7.2.2. (Added-Yokota) Identify and coordinate LM request to 374 MXG/CC or designated

representative for approval.

9.20.7.3. (Added-Yokota) Items identified with a restrictive SMR code will not be

manufactured without approval of Depot Engineering. As per paragraph 9.20.7.4., submit request

for applicable procedures to seek approval following guidance listed in TO 00-25-107.

9.20.7.4. (Added-Yokota) Assets requiring modification or deviation from applicable technical

guidance must be approved by Depot Engineering via TO 00-25-107 request, submitted in

AIRCAT in which case engineering disposition, blueprint or drawing must be made available

prior to establishing a work request. Example: Part is SMR-Coded PAA, without a favorable

EDD, fabricating activity has all capabilities to manufacture IAW technical drawings, blueprints,

equipment technical directives or is covered under applicable general maintenance practices, but

lacks the ability perform a listed procedure (i.e., to shot peen, perform cadmium plating, etc), 00-

25-107 TAR is required to LM the part while deviating from technical data.

9.20.7.4.1. (Added-Yokota) Once the 00-25-107 TAR is approved, follow paragraph 9.20.4 to

complete the request.

9.20.7.5. (Added-Yokota) Aircraft screws, bolts and other externally aircraft threaded

hardware cannot be locally manufactured or repaired in any manner. Replace parts with another

of identical specifications. Clean or repair internal threads by installing inserts IAW applicable

aircraft technical data.


Table 11.1. (Yokota) Mandatory Special Certification Roster (SCR).

A B

Item Mandatory SCR Item Titles Prerequisites

46 Hangar Door Operation Trainer SSgt or higher, minimum 5-skill level or civilian

equivalent. (Note 2)

47 Tow Team Supervisor Certifying

Officials

TSgt or higher, minimum 7-skill level or civilian

equivalent. One year minimum Tow Team

Supervisor experience on applicable MDS.

MXG/CC may waive qualified SSgts. The

MXG/CC may waive qualified SSgts or higher

with 6 months Tow Team Supervisor experience on

applicable MDS. (Note 2)

Notes:

1----Approved by MXG/CC

2----Approved by Operations Officer/MX SUPT

11.6.5.2. (Added-Yokota) MOC will maintain a product to track manually created jobs when

the MIS is down. When necessary, maintainers will create Red Ball jobs in the 781 forms and

contact MOC for a manual JCN. MOC will track each manually created job and, once available,

will enter all jobs into the MIS.

11.6.5.3. (Added-Yokota) Production Superintendents and Expediters will ensure applicable

jobs are opened and closed through MOC to ensure tracking of maintenance while the MIS is

down and that MOC can accurately complete MIS documentation once it is back up. Production

Superintendents must verify with MOC to ensure all Red Xs are closed prior to ER and aircraft

launch.

11.8.1.1. (Added-Yokota) FOD General Procedures:

11.8.1.2. (Added-Yokota) “FOD Elimination” is the standard. Attention to detail, coupled

with a proactive approach at all levels, will result in a zero FOD rate. FOD prevention is

everyone's responsibility. Supervisors at every level will ensure that proper FOD prevention

procedures are strictly enforced.

11.8.1.3. (Added-Yokota) “ZERO TOLERANCE” is the standard for all FOD prevention

measures as well as for 374th Maintenance Group Quality Assurance (374 MXG/MXQ)

assessments on aircraft, work areas directly in or around aircraft, tool boxes, work areas that

support aircraft systems and Aerospace Ground Equipment (AGE).

11.8.1.4. (Added-Yokota) All FOD assessments and spot checks will be objective based on the

“zero tolerance” concept.

11.8.1.5. (Added-Yokota) FOD found within one half hour of a FOD walk or hangar sweep

will constitute a fail against the performing organization. FOD found, including FO discovered

later than one half hour after a FOD walk or hangar sweep, will be subject to investigation by

374 AW FOD Monitor or QA inspectors.


11.8.1.6. (Added-Yokota) The “clean-as-you-go” concept will be strictly followed. On the

flight line and in the hangars, it is important to stress that proactive housekeeping procedures will

be initiated throughout every task. The task is not complete until the area is cleaned up. Strict

use of parts bags will be enforced.

11.8.1.7. (Added-Yokota) Incorporate “clean as you go” into FOD training to enhance the

ability of reducing potential FOD.

11.8.1.8. (Added-Yokota) “Clean as you go” procedures are expressed below:

11.8.1.8.1. (Added-Yokota) Clean the immediate area when work cannot continue.

11.8.1.8.2. (Added-Yokota) Clean the immediate area when work debris has the potential to

migrate to an out of sight or inaccessible area and cause damage and/or give the appearance of

poor workmanship.

11.8.1.8.3. (Added-Yokota) Clean the immediate area after work is completed and prior to

inspection.

11.8.1.8.4. (Added-Yokota) Clean area at the end of each shift.

11.8.1.8.5. (Added-Yokota) If you drop something or hear something drop--pick it up!

11.8.3.1.4. (Added-Yokota) Prevention Policy. FOD and dropped objects are costly and have

a negative impact on mission accomplishment. Every effort will be made by all 374 AW

personnel to ensure FOD and DOP prevention measures are followed. Supervisors at all levels

will ensure everyone within their span of control is trained on, and implements FOD/DOP

prevention procedures at all times.

11.8.3.6.6. (Added-Yokota) Clothing restrictions. Hats will not be worn on the flight line. All

personnel performing ground observer duties for engine start must clear any pockets that cannot

be buttoned, zipped, or otherwise secured of all objects prior to engine operation. Objects that

protrude from the uniform (pens, pencils, etc.) must also be removed.

11.8.3.6.7. (Added-Yokota) Wear of the winter watch cap is authorized and may be worn

during aircraft launch or recovery when using the following procedures:

11.8.3.6.8. (Added-Yokota) Ear defender/communication headset devices should be worn over

the watch cap.

11.8.3.6.9. (Added-Yokota) If ear defender/communication headset is not worn over watch cap

then cap must be firmly set on individual’s head and pulled down over ears to prevent it from

inadvertently coming off.

11.8.3.6.10. (Added-Yokota) For FOD prevention and safety reasons the AF Form 1199, Air

Force Entry Control Card (Restricted Area Badge), will be removed during engine inlet

maintenance and secured. Badge will be secured by placing it in a safe area or having another

member procure it. The badge will be worn upon termination or when not in the immediate area

where the engine inlet maintenance is conducted.

11.8.3.8.1.1. (Added-Yokota) All aircraft hangars, maintenance production areas, and vehicles

that frequent flight line/maintenance areas will have approved area FOD containers readily

accessible to workers. An area FOD container will be a sturdy receptacle. Flight line vehicle

containers must be lidded type containers. Shops may fabricate or procure small portable FO


containers (coffee cans, FOD bags, etc.) for use where area collection points are not feasible such

as on maintenance stands or work benches.

11.8.3.8.2. (Added-Yokota) Containers will be stenciled with the word “FOD” in contrasting

letters. “FOD” stickers may be used on FOD containers and are available from the 374 AW FOD

Monitor’s office.

11.8.3.8.3. (Added-Yokota) All FOD containers will be emptied when full or at the end of each

shift, whichever comes first.

11.8.3.8.4. (Added-Yokota) Approved FOD containers will be installed on all multi or special

purpose vehicles (metros, deicers, tow vehicles, etc.) which frequent flight line/maintenance

areas.

11.8.3.9.1. (Added-Yokota) Practice good housekeeping and hardware accountability at all

times. Parts bags will be used at all times and will be attached to the associated component or

area as applicable. Use attached tag to indicate types and totals of items inside,

aircraft/equipment number and safely secure parts. Plastic “Ziploc” type bags may be used as

parts bags, provided they have a listing included on paper or have the contents annotated on the

package with permanent ink. Locally produced part accountability kits may also be used to

account for component hardware (e.g., engine mount bolt kit).

11.8.3.9.2. (Added-Yokota) Hardware and shop stock control. Hardware and shop stock (acid

brushes, paint pens, razor blades, etc.) will be issued on a one-for-one basis. Bench stock must be

secured in a controlled area. When obtaining these items from the Consolidated Tool Kit (CTK)

or Supply area, turn in one item to receive one like item. For instances where a turn-in part is not

available, CTK or supply personnel will annotate a locally produced log with the following

minimum information: Name, rank, bin number, quantity, date, aircraft tail number, and job

control number. Contracted maintenance operations will follow these guidelines, except in areas

where their statement of work exempts them from it due to contractual FOD prevention

requirements.

11.8.3.11. (Yokota) Base FOD walks. FOD walks are mandatory to remove FO from the flight

line parking ramp, access road, and adjacent areas.

11.8.3.11.2. (Added-Yokota) 374 AW level FOD walks are conducted once a week on Monday

at the times listed in Table 11.2. This time may be adjusted depending on mission requirements

to maximize participation, upon coordination with the Wing FOD Monitor. Squadron personnel

will assemble at designated flight line area spots. Maximum participation is essential for a

successful FOD walk.

11.8.3.11.3. (Added-Yokota) FOD walk areas of responsibility are as follows:


Table 11.3. (Added-Yokota) Responsibility of FOD Walk Areas.

SQUADRON AREA OF RESPONSIBILITY

374 AMXS, 36 AS

Time: 0730 (AMXS) / 0900 (AS)

Parking Spot D-7 to AGE “AMC” Ready Line

374 OG, 374 OSS, 459 AS

Time: 0900

Building 800 to Parking Spot D-7

374 MXS (Fab, Programs &

Accessory Flights)

Time: 0730 (Winter) / 0830 (Summer)

Wash rack to Building 800

374 MXS (AGE)

Time: 0730

Building 610 to AGE yard

374 MXS (MUNS)

Time: 0800

From Hold Line at Kilo Taxiway and Foxtrot

intersection to Building 1504

374 MXS (Fuels) and Aero Club

Time: 0730

Building 1504 to Hold Line at Golf Taxiway Foxtrot

Intersection

374 MXS (ISO, Refurbishment)

Time: 0730

AGE “AMC” Ready Line to Aircraft Parking Spot C-8

730 AMS (FOD Walk on Tuesday)

Time: 1000 (summer)/ 1300 (winter)

Aircraft Parking Spots C-8 to Aircraft Parking Spot

C5-4

11.8.3.11.4. (Added-Yokota) The Wing FOD Monitor may adjust FOD walk days to meet

mission requirements when necessary. FOD walks may be terminated by the Wing FOD

Monitor during inclement weather (e.g., heavy fog, heavy rain, severe temperatures, or when the

Maintenance Operations Center (MOC) announces lightning inside five nautical miles); when

these conditions are present Unit FOD monitors will call the Wing FOD monitor to cancel and

reschedule. FOD walks will be rescheduled accordingly if cancelled.

11.8.3.11.5. (Added-Yokota) Aircraft maintenance units (AMUs) should conduct their own

FOD walks on each duty day when group-level FOD walks are not accomplished. Individuals

will conduct walks around individual aircraft and hangars prior to start and after completion of

any maintenance on that aircraft. The alternative procedure is for units to assemble a structured

line once a day in their area and conduct a FOD walk.

11.8.3.11.6. (Added-Yokota) FOD walk procedures. All participants will assemble prior to

FOD walk for a safety briefing. For safety reasons the FOD walk supervisor has ultimate

authority in controlling procession of the line and personnel will disperse evenly as directed. The

FOD walk supervisor must call MOC to coordinate authorization from Security Forces before

breaking red (crossing the red restricted area lines) when applicable. Movement will be at a slow

pace, paying special attention to equipment, grounding points, expansion joints, and cracks in

pavement. Personnel will disperse evenly as directed and move slowly in an even line. If


hardware (safety wire, rivets, nuts, washers, etc.) is discovered, inform the FOD walk supervisor

of the parking spot where the item was found.

11.3.8.11.7. (Added-Yokota) Aircraft parking spots will be FOD walked prior to parking and

after moving aircraft from the spot. This requirement pertains to both towed and taxied aircraft.

Tow supervisors/expediters will ensure the spot is FOD walked no sooner than 30 minutes prior

to parking on and no later than 30 minutes after moving from the spot.

11.8.3.13. (Yokota) Flight deck FOD inspections. All 374 AW aircraft flight deck FOD

prevention inspections will be accomplished no earlier than 4 hours prior to flight and annotated

in the aircraft AFTO Form 781A, Maintenance Discrepancy and Work Document. Check for

foreign, loose, or missing items (light lenses, covers, bulbs, and hardware) on all instrument,

control, and circuit breaker panels. Pay particular attention to areas around seat tracks, flight

control inputs, and openings in the throttle quadrant and floor.

11.8.3.15.1.1. (Added-Yokota) Streamers. “REMOVE BEFORE FLIGHT” streamers will be

used on ground wires and any external cover applied to the aircraft on the ground.

11.8.3.15.1.2. (Added-Yokota) Equipment Identification. Owning organization will clearly

mark -21 equipment to maintain control and facilitate equipment return if removed off-station

due to mission requirements. Equipment may be marked using black paint, black permanent

marker, etched or monogrammed. If the item is still too small for a marker or engraver, (e.g., tie

down rings), then disregard marking it. Units will stencil their organization identifier (e.g.,

374AW, etc.) on each piece of -21 equipment using black paint, black permanent marker, etched

or monogrammed. Custom engraved and/or monogrammed -21 equipment is authorized as long

as the organizational identifier is standardized. If aircraft tail numbers are stenciled on -21

equipment, do not interchange -21 equipment with multiple tail numbers on a singular aircraft.

11.8.3.16. (Yokota) Vehicles. Vehicles are potential FO/FOD hazards. All vehicles will be

maintained FO-free at all times. Vehicles and FOD bars will be checked for cleanliness prior to

operating the vehicle. Each subsequent operator will ensure the vehicle and magnetic bar are FO

free. All vehicle/equipment tires and magnetic bars will be checked and cleared of debris prior

to entering the flight line. During hours of darkness, a bright flashlight will be used for this

inspection. Vehicles involved in an actual emergency response are exempt from these tire

checks.

11.8.3.16.1. (Added-Yokota) All vehicles prior to entering a flightline gate (with the exception

of the control tower gate, and the dental gate) will come to a complete stop, turn off the engine

and set parking brake. Control tower and dental gate FOD checks will be completed after the

flightline gate but before crossing any taxiway or ramp if no FOD check box is available.

Personnel will shut off the engine, set parking brake, then exit the vehicle and check for

imbedded foreign objects on vehicle tire surfaces, start engine, then pull forward (Roll-Over),

turn off engine, set parking brake, and check any previously unexposed tire surface area for

imbedded foreign objects. Vehicle operators will also check for any loose objects or unsecure

cargo on the vehicle. This check will be accomplished inside or as close to the “FOD Roll-Over

Tire Check Box” as possible, and will be accomplished prior to the FOD check sign.

11.8.3.16.2. (Added-Yokota) Aircraft servicing vehicles, AGE tow vehicles (bobtail), or any

vehicle that requires the engine to idle due to pneumatic air starters or T.O. specific procedures

that call for the vehicle to idle for a specific period of time before the engine is turned off will be


exempt from shutting engines off for vehicle FOD roll over checks. These vehicles will have the

parking brake set, transmission in neutral or park, and chock the rear wheels while performing

FOD Roll-Over checks IAW TC 21-305-20/AFMAN 24-306(I).

11.8.3.16.3. (Added-Yokota) Charlie, Delta, and Echo ramp access road is not a FOD-free

zone and requires a FOD check prior to entering the ramp. The perimeter of this road facing the

flight line is marked with “FOD CHECK ZONE” and any vehicle transitioning to the flight line

will perform a Roll-Over check before entering Charlie, Delta, and Echo ramp.

11.8.3.16.4. (Added-Yokota) Magnetic FOD bars may be installed on all “high use” Transit

Alert/dispatch/expediter vehicles. Vehicles exempt from this requirement are as follows:

Crash/recovery vehicles, mules/golf carts, tow vehicles, cranes, forklifts, other special purpose

vehicles, and any vehicles not operated frequently on the flight line.

11.8.3.16.5. (Added-Yokota) If used, FOD bars will be installed either on the front or back

bumper of the vehicle approximately 3”- 5” off the ground. All FOD bars will be removed prior

to turn in to vehicle maintenance and reinstalled immediately upon return.

11.8.3.24. (Added-Yokota) Incentive Program. Foreign Object Damage (FOD) Poster

Competition/Golden Bolt Award.

11.8.3.24.1. (Added-Yokota) The 374 AW has established the Quarterly FOD Poster

Competition. This competition is open to the entire 374 AW and its tenant units. Posters may be

drawn by hand or developed electronically. Submit completed posters to the 374 AW FOD

Monitor either electronically or in person before the last day of each calendar quarter.

11.8.3.24.1.1. (Added-Yokota) The Wing FOD Monitor/QA office will vote for the best

poster. For quarterly competitions, the winner will receive a certificate and be

authorized/recommended for a 1-day pass. The annual competition winner will receive a

certificate and be authorized/recommended for a 3-day pass.

11.8.3.24.2. (Added-Yokota) Each month the Wing FOD Monitor will hide a Golden Bolt in a

maintenance work area or on the airfield during the weekly FOD walks. Whoever finds the bolt

will be recommended for a 1-day pass and receive a certificate from the 374 AW Vice

Commander (374 AW/CV). These passes must be coordinated with the individual’s work center

supervisor and be taken when workload permits. The bolt will be clearly tracked by the FOD

Monitor to preclude its loss during FOD walk.

11.8.3.25. (Added-Yokota) Towed FOD sweepers and airfield sweeper vehicles will be used

for base FOD prevention efforts.

11.8.3.25.1. (Added-Yokota) Areas requiring airfield sweepers will be coordinated through the

airfield manager by calling the Maintenance Operations Center.

11.8.3.25.2. (Added-Yokota) Towed FOD Sweeper Usage. The FOD sweeper is an effective

tool used to supplement airfield sweepers in removing FOD from large areas of the airfield in an

efficient manner. In order for the FOD sweeper to be effective, units that are assigned a FOD

sweeper must tow it on a regularly scheduled basis. The squadron FOD monitors are responsible

for managing this program at the squadron level.

11.8.3.25.3. (Added-Yokota) Two triplex FOD sweeper are assigned to 374 MXS and one

triplex FOD sweeper is assigned to 374 AMXS. 730 AMS has one triplex FOD boss sweeper.


11.8.3.25.4. (Added-Yokota) Any vehicle can be used to pull the FOD sweeper so long as

good coverage of the ramp is achieved. To prevent damage to the FOD sweeper backing of the

vehicle is prohibited with the FOD sweeper installed, and the FOD sweeper should not be towed

during inclement weather. Vehicles towing a FOD sweeper should focus additional attention on

parking spots recently vacated by aircraft.

11.8.3.25.5. (Added-Yokota) FOD sweeper usage will be tracked and recorded by the CTK of

the assigned workcenter on AF Form 3131, General Purpose Form. The form will track the

following: Name of personnel, squadron/office symbol, date/time, hours driven, area covered,

weight and description of material collected.

11.8.3.25.6. (Added-Yokota) Units will use a FOD sweeper for a minimum of 4 hours a week

and dictate which shift the FOD boss will be utilized. This will be based on mission

requirements and ramp/taxiway condition. After days of inclement weather it is recommended

that the FOD sweeper be pulled to ensure a FOD free ramp.

11.8.3.25.6.1. (Added-Yokota) The unit FOD representative or CTK will notify the 374 AW

FOD prevention office when a sweeper goes down for maintenance. Sweepers will be borrowed

from another unit to sweep required areas, which will be credited to the unit pulling it.

11.8.3.25.6.2. (Added-Yokota) FOD sweeper usage requirements are as follows:

Table 11.4. (Added-Yokota) Requirements of FOD Sweeper Usage.

SQUADRON ASSIGNED AREA OF RESPONSIBILITY

374 AMXS Parking spot D-11 to parking spot C-8

374 MXS Wash rack to parking spot D-11

Golf Ramp/taxiway with Hotel, Juliet, and Kilo taxiway 730 AMS Aircraft Parking Spots C-8 to Aircraft Parking Spot C5-4

11.8.3.26. (Added-Yokota) Airfield inspection and monitoring.

11.8.3.26.1. (Added-Yokota) Representatives from 374 OSS Airfield Operations (374

OSS/OSAA) and the FOD monitor will each conduct random ramp inspections. These

inspections will include the assessment of damaged pavement, flight line construction, and other

FOD hazards in or near aircraft parking ramps, taxiways and access roads. The results will be

passed to 374 OSS/OSAA, Airfield Management, for tracking.

11.8.3.26.2. (Added-Yokota) Results of these inspections will be tracked in the Quality

Assurance database or a locally devised form and briefed quarterly to the 374 AW/CV at the

Wing FOD Prevention committee meeting.

11.8.3.27. (Added-Yokota) Engine/propeller maintenance. Aircraft engine/propeller

maintenance is a FO/FOD critical area. All personnel will exercise caution when performing

maintenance in these areas. Strict tool and hardware control practices will be enforced during

engine/propeller maintenance. All hardware will be accounted for at all times.

11.8.3.27.1. (Added-Yokota) Covers (e.g., engine inlet, pitot tube(s), and protective covers)

will not be removed more than 4 hours prior to flight and will be installed within 30 minutes


following engine shutdown. Engine inlet covers will be installed for any maintenance

accomplished on the engine/propeller forward of the engine firewall. All covers will be

inspected after any severe weather condition to ensure serviceability and inventory.

11.8.3.27.2. (Added-Yokota) All engine inlet maintenance, to include inlet/exhaust inspections

prior to/after each engine operation and blade blending, will be annotated on a Red X symbol in

the AFTO Form 781A. Inlet/exhaust inspections before and after operation or maintenance will

be conducted by a qualified 7-level or red-X qualified 5-level as identified on the unit’s Special

Certification Roster (SCR) for that task.

11.8.3.27.3. (Added-Yokota) Blade damage. Upon discovery of blade damage, annotate AFTO

Form 781A on a red dash and notify the MOC and 374 AW FOD Office prior to any rework of

blades.

11.8.3.27.3.1. (Added-YokotaC-130J/ AE2100D3 only) Upon discovery of blade damage,

annotate AFTO form 781A, Maintenance Discrepancy and Work Document on a red diagonal.

A propulsion 7-Level (2A671H) or field level engineering expert will determine if the blade

damage is outside the limits identified in the applicable job guide or technical data. Blade

blending is not authorized on the AE2100D3 engines.

11.8.3.27.3.2. (Added-Yokota) When damage has been previously blended with no rework

required, the applicable areas will be recoated with blue layout dye and annotated in the AFTO

Form 781A.

11.8.3.27.3.3. (Added-Yokota) When blending is required the damage will be measured using

a borescope. At this time, upgrade the original discrepancy to a Red-X symbol.

11.8.3.27.3.4. (Added-Yokota) Only qualified personnel that have attended a formal blade-

blending course conducted by a qualified blade blending instructor and certified by a blade

blending certifying official will perform blade blending. This qualification will be documented

on the unit’s SCR.

11.8.3.27.3.5. (Added-Yokota) An all systems Red X certified or an Field Training

Detachment (FTD) trained and certified propulsion 7-level, as documented on the unit SCR, will

inspect the blending and clear the Red-X discrepancy from the aircraft forms.

11.8.3.27.3.6. (Added-Yokota) Blade blending (installed engines). Notify Wing FOD Monitor

(730 AMS/QA FOD Monitor for AMC aircraft) prior to any blade blending on installed engines.

Complete a Blade blending worksheet (Attachment 7) and forward by fax or e-mail to applicable

374 AW FOD monitor and the engine management branch (EMB). EMB will document this data

in the AFTO Form 95, Significant Historical Data, IAW TO 00-20-1-WA-1, Aerospace

Equipment Maintenance Inspection, Documentation, Policy and Procedures.

11.8.3.27.3.7. (Added-Yokota) Blade blending (uninstalled engines). Notify Wing FOD

monitor of any blade blending. Complete a Blade blending worksheet (Attachment 7) or

approved work package tracking sheet and forward by fax or e-mail to applicable 374 AW FOD

monitor and the engine management branch (EMB). EMB will document this data in the AFTO

Form 9, IAW TO 00-20-1-WA-1 upon review of the work package.

11.8.3.27.3.8. (Added-Yokota) Non-repairable blade damage. When damage is verified by the

previously mentioned methods and is confirmed as non-repairable, notify the applicable unit


supervision and initiate impoundment procedures IAW Chapter 7 of this instruction. Also,

ensure the MOC and 374 AW FOD monitor are updated with this information.

11.8.3.28. (Added-Yokota) Tool Management. All personnel working in, on, around, or

traveling through areas near aircraft, munitions, AGE, engines or components, will account for

all tools and/or equipment used in performance of their duties. Comply with all requirements in

Chapter 8.

11.8.3.29. (Added-Yokota) Cell phones, pagers, etc. authorized for use on the flight line or in

maintenance work areas by MXG/CC will only be used for official/authorized business. Cell

phones will not be used while actively performing maintenance. During maintenance actions,

cell phones and other electronic devices (e.g., PDAs, pagers) not required in the performance of

maintenance, shall be turned off. Placing cell phones or other electronic devices in the silent or

vibrate mode does not satisfy this requirement. This restriction does not apply to personnel

performing maintenance management duties (e.g., Pro Super, Expediter). Care/prudence should

be exercised when using electronic devices on the flightline so as not to create a FOD hazard.

11.8.3.29.1. (Added-Yokota) Government equipment issued for the performance of official

duties on the flight line must be appropriately marked/identified with squadron and office

symbol, (i.e., 374 MXG/MXQ). Personnel will also comply with restrictions in T.O. 00-25-172,

AFMAN 91-201, AFI 91-207, AFI 31-218 and AFI 21-101.

11.8.4.4. (Added-Yokota) Unit FOD representatives. The following units are required to have

FOD representatives: 374 AMXS, 374 AW/SE, 374 CES, 374 LRS, 374 MXS, 374 OG, 459 AS

(M1), 374 SFS, and 730 AMS.

11.8.4.4.1. (Added-Yokota) Yokota’s weekly FOD walk is the responsibility of the Unit FOD

Monitors and their squadron members. If the Monitors are on leave, TDY or have departed PCS,

the squadron is responsible to arrange for a replacement to take over the Unit FOD Monitor

duties.

11.8.4.4.1.1. (Added-Yokota) Unit FOD Monitors FOD walk duties are to:

11.8.4.4.1.1.1. (Added-Yokota) Perform a safety briefing before each FOD walk.

11.8.4.4.1.1.2. (Added-Yokota) Provide hearing protection.

11.8.4.4.1.1.3. (Added-Yokota) Provide plastic bags or suitable substitute.

11.8.4.4.1.1.4. (Added-Yokota) Make sure everyone is properly spaced out and remains in

straight line for the entire walk.

11.8.4.4.1.1.5. (Added-Yokota) Ensure personnel are actively looking for FOD.

11.8.4.4.1.1.6. (Added-Yokota) Ensure personnel pull grass growing in grounding points.

11.8.4.4.1.1.7. (Added-Yokota) Ensure Airfield management is contacted for grass growing in

areas other than grounding points to be scheduled for Entomology spraying.

11.8.4.4.1.1.8. (Added-Yokota) Turn in anything out of the ordinary to the FOD Monitor (e.g.

pins, bolts, license plates, etc.

11.8.4.5. (Added-Yokota) Unit commanders will appoint primary and alternate FOD/DOP

representatives and forward the name, grade, office symbol, DEROS, and duty telephone of

those individuals in the form of an appointment letter to the 374 AW FOD office. Additional


flight FOD representatives are required for units/flights with geographically separated sections

(Aero Repair (A/R), support section, inspection docks, test cell, fuels maintenance section, wash

rack, corrosion, etc.) and will be appointed in writing by the unit commander. The FOD/DOP

representatives will:

11.8.4.5.1. (Added-Yokota) Inform sections within unit of potential FOD/DOP hazards, trends,

and prevention practices.

11.8.4.5.2. (Added-Yokota) Maintain current FOD/DOP awareness board, subject to spot

inspections.

11.8.4.5.2.1. (Added-Yokota) Required awareness board items:

11.8.4.5.2.1.1. (Added-Yokota) 374 AW FOD/DOP Monitor Flyer.

11.8.4.5.2.1.2. (Added-Yokota) Unit/Flight FOD/DOP Representative.

11.8.4.5.2.1.3. (Added-Yokota) Current Quarterly FOD/DOP Awareness Tips (In color if

available).

11.8.4.5.2.1.4. (Added-Yokota) Current quarterly FOD Awareness Poster.

11.8.4.5.2.1.5. (Added-Yokota) Optional awareness board items include but are not limited to:

11.8.4.5.2.1.5.1. (Added-Yokota) Photos (Wing/Squadron/Flight incentive program award

winners, FOD/DOP incidents).

11.8.4.5.2.1.5.2. (Added-Yokota) FOD Walk collection slides.

11.8.4.5.2.1.5.3. (Added-Yokota) FOD/DOP related news/magazine articles.

11.8.4.5.3. (Added-Yokota) Conduct and document a minimum of one FOD/DOP unit/flight

briefing per quarter on updated or significant information (e.g., FODs, DOs, instruction changes)

located on the 374 AW FOD/DOP SharePoint web page.

11.8.4.5.3.1. (Added-Yokota) FOD/DOP briefings will be documented on an AF Form 3131,

General Purpose Form, and at a minimum contain the following information: Name and rank of

briefer, date accomplished, and briefing subject. This briefing may be accomplished through e-

mail. This form will be kept by the unit FOD/DOP monitor for the current fiscal year and

replaced with a new form at the start of each new fiscal year. This form will be reviewed during

the unit’s annual FOD SAV.

11.8.4.5.4. (Added-Yokota) May develop unit level FOD/DOP prevention and recognition

programs as required.

11.8.4.5.5. (Added-Yokota) Monitor unit FOD sweeper usage (if applicable).

11.8.4.5.6. (Added-Yokota) Assist Wing FOD/DOP Monitor with investigations as requested.

11.8.4.5.7. (Added-Yokota) Conduct and document a minimum of one spot-check per duty

week within the unit/flight. Unit representatives will also be provided a copy of any spot

inspection results conducted by the Wing FOD/DOP Monitor. Unit/flight monitors are

responsible for briefing their squadron/flight supervision.

11.8.4.5.8. (Added-Yokota) Units involved with weekly FOD walks will document them on an

AF Form 3131, General Purpose Form, and at a minimum contain the following information:


Location, date accomplished, time, discrepancies noted, number of participation, and unit FOD

monitor name documenting the FOD walk.

11.8.4.5.9. (Added-Yokota) Attend FOD/DOP Program Committee meetings as required.

11.8.5. (Yokota) The FOD/DOP Program Manager will appoint and assign all duties and

responsibilities to the Wing FOD Monitor. The minimum responsibilities of the Wing

FOD/DOP Monitor are:

11.8.5.7. (Added-Yokota) Ensure personnel accessing the flight line and maintenance areas

comply with program directives and perform spot inspections.

11.8.5.8. (Added-Yokota) Conduct all FOD and dropped object investigations and ensure

sound corrective actions.

11.8.5.9. (Added-Yokota) Inform units of potential FOD/DOP trends and hazards.

11.8.5.10. (Added-Yokota) Perform duties of 374 MXG QA augmentee; conduct and

document spot checks and FOD assessments in/around the flight line and maintenance areas.

11.8.5.10.1. (Added-Yokota) FOD assessments will be determined by the 374 MXG QA

Routine Inspection Listing.

11.8.5.10.2. (Added-Yokota) Spot inspections and assessments will cover, but are not limited

to, the following areas: FOD continuity book/awareness board (content and condition),

prevention (sweeper utilization and condition), housekeeping (shop, aircraft, tool control,

hardware control, etc.), CTK (FOD in tool boxes, support equipment electrical receptacles

capped/plugged, sweeper log (if applicable) and lost tool log), vehicles (FOD bars, cleanliness,

roll-over FOD checks, and FOD containers), and aircraft (use of intake plugs, tubing, and

electrical caps/plugs, pitot tube covers, streamers, flight deck cleanliness and throttle quadrant

covers).

11.8.5.10.3. (Added-Yokota) Spot inspections and assessments will be annotated in the

Logistics Evaluation Assurance Program (LEAP) database and incorporated into the 374 MXG

QA Maintenance Standardization and Evaluation Program (MSEP) briefing.

11.8.5.10.4. (Added-Yokota) All inspection documentation will be kept on file with the

applicable QA office.

11.8.5.11. (Added-Yokota) Organize Wing FOD walks and analyze recovered FO.

11.8.5.12. (Added-Yokota) Develop and monitor FOD/DOP training programs with necessary

changes.

11.8.5.13. (Added-Yokota) Brief the quarterly or monthly FOD/DOP Program Committee

meetings as required.

11.8.5.14. (Added-Yokota) Maintain dropped object historical data.

11.8.5.15. (Added-Yokota) FOD/DOP assistant. A FOD/DOP assistant from the 374 MXG

QA will be assigned in writing to the FOD/DOP monitor. The FOD/DOP assistant will perform

all 374 AW FOD/DOP duties and responsibilities in the absence of the FOD/DOP monitor.

11.8.5.15.1. (Added-Yokota) The FOD/DOP assistant will be approved by the 374 AW/CV.


11.8.6. (Yokota) FOD/DOP reporting and investigations will be accomplished IAW AFI 91-

204, Safety Investigations and Reports, as applicable. Informational copies of the reports will be

sent to the applicable flight safety office as requested. The FOD/DOP monitor will notify 374

AW Public Affairs officials if large objects are lost in-flight or incidents are likely to cause

adverse publicity.

11.8.6.1.1.1. (Added-Yokota) When FOD or a dropped object incident is discovered, unit

supervision will immediately notify the MOC. The MOC will notify the applicable FOD/DOP

Monitor and QA office. Impound aircraft/engine, if required, per Chapter 7 of this instruction.

11.8.6.2.4. (Added-Yokota) Do not perform maintenance in the affected area of the

aircraft/equipment until cleared by the investigator. Save all evidence of the incident for turn-in

to the applicable FOD/DOP office.

11.8.6.2.5. (Added-Yokota) The 374 AW FOD/DOP Monitor or QA offices will accomplish

all FOD investigations with the assistance of the Unit FOD Monitor. The unit responsible for the

incident will complete the FOD investigation worksheets; 374 AW Form 72, Foreign Object

Damage (FOD) Incident Investigation, and 374 AW Form 71, Cost Estimate Worksheet. The

investigation and cost estimate worksheets will be submitted the next duty day to the 374 AW

FOD/DOP monitor or QA office as applicable. Consult the Air Force Safety Center website at

http://afsafety.af.mil/ “Hourly Labor Rates” chart for current rates. When possible,

crewmembers will be interviewed prior to leaving debrief. This time allotment ensures timely

reporting to headquarters.

11.8.6.2.6. (Added-Yokota) The 374 AW FOD/DOP monitor, located in the 374 MXG QA

office, is responsible for any HHQ reporting requirements outlined in various AFI 21-101

supplements.

11.8.6.2.7. (Added-Yokota) When material deficiency is determined to be the cause, or a

suspected cause, the owning unit will submit a material deficiency report IAW TO 00-35D-54,

USAF Deficiency Reporting and Investigation, and Resolution, (even when an exhibit is not

available) within 5 working days to the 374 MXG/MXQ.

11.8.6.2.8. (Added-Yokota) For engine compressor FOD investigations where the impacting

item is not easily identifiable, the forensic metal sampling process from Failure Analysis Service

Technology or “FAST” sampling may be used. This will be at the request of the owning unit or

the applicable FOD monitor; however, the unit is responsible for the cost of this service.

11.8.7.1.1. (Yokota) FOD/DOP Program meetings. FOD/DOP prevention program committee

meetings will be conducted quarterly or as required. The committee chairperson will be the 374

AW/CV.

11.8.7.3. (Added-Yokota) The wing’s FOD Prevention Committee meetings are to ensure the

FOD Prevention Program is sound and meeting base needs. The following personnel and

agencies will attend or have their representative attend the FOD Prevention Committee meeting:

374 AW/CV, 374 AW FOD Monitor, 374 AW/SE, 374 MXG/CC, 374 MXG/MXQ, 374

AMXS/CC, 374 MXS/CC, 374 OG/CC, 374 OSS/OSAA, 374 MSG/CC, 374 LRS/CC, 374

CES/CC, 374 CS/CC, 374 SFS/SFTCA and 730 AMS/SE/MXAQ.

11.8.9. (Added-Yokota) Training.

http://afsafety.af.mil/


11.8.9.1. (Added-Yokota) Initial FOD prevention training for maintenance personnel will be

conducted during maintenance orientation briefing and will include results from previous

FOD/DOP investigations as well as an orientation on this instruction.

11.8.9.2. (Added-Yokota) Recurring FOD/DOP prevention training for maintenance personnel

will be conducted during maintenance block training.

11.8.9.3. (Added-Yokota) Unit and flight FOD/DOP representatives will receive training on

requirements associated with their position from the applicable FOD/DOP monitor.

11.9. (Yokota) The 374 AW FOD/DOP Prevention Program is defined by a combination of

published guidance in Chapter 8 of this instruction and the following section.

11.9.1. (Yokota) DOP is the responsibility of all aircraft operators and maintainers. Prevention

begins when aircraft panels are removed, access doors opened, or when maintenance is

performed on an exterior component.

11.9.2.5. (Added-Yokota) The 374 AW FOD/DOP Monitor or QA offices will accomplish all

dropped object investigations with the assistance of the Unit DOP Monitor. The unit responsible

for the incident will complete the DOP worksheets; 374 AW Form 70, Dropped Object

Investigation Worksheet, 374 AW Form 71, Cost Estimate Worksheet. The DOP investigation

and cost estimate worksheets will be submitted the next duty day to the 374 AW FOD/DOP

monitor or QA office as applicable. Consult the Air Force Safety Center website at

http://afsafety.af.mil/ “Hourly Labor Rates” chart for current rates. When possible,

crewmembers will be interviewed prior to leaving debrief. This time allotment ensures timely

reporting to headquarters.

11.9.4. (Added-Yokota) When installing/operating aircraft panels, doors, and components,

place special emphasis on the condition of latches, fasteners, hinge pins, and hinge lobes.

Preflight inspections must ensure panels, doors, and components fit properly and are attached

securely.

11.10.6. (Added-Yokota) 374 AW specific ASIP and DTADS guidance:

11.10.6.1. (Added-Yokota) The C-130 ASIP is managed by the C-130 System Program Office,

WR-ALC/LBRA. This office analyzes data provided by Operations and Maintenance units

using a web based program called Automated Inspection, Repair, Corrosion and Aircraft

Tracking (AIRCAT). Operations Group (OG) personnel input aircraft usage data using the

Usage Data Input (UDI) segment. Maintenance Group (MXG) personnel utilize the Inspection,

Corrosion and Repair Recording (ICARR) segment for documenting required ASIP inspections,

aircraft structural repairs and reports of damage to aircraft structures as well as submit C-130J

Data Transfer and Diagnostic System (DTADS) downloads to AIRCAT. A major function of

the United States Air Force (USAF)-AIRCAT system is to provide data to generate the ASIP

report. This report is used to make decisions regarding modifications, acquisition, reassignment

and retirement of the Air Force C-130 aircraft.

11.10.6.2. (Added-Yokota) The 374 AW ASIP program is broken into two key elements:

ASIP inspection execution and DTADS data collection and reporting.

11.10.6.2.1. (Added-Yokota) ASIP inspection execution. MXS will be the lead squadron for

ASIP inspection execution and identify a primary and alternate ASIP inspection project officer,

to be appointed by the MXG CC. This project officer will:

http://afsafety.af.mil/


11.10.6.2.1.1. (Added-Yokota) Act as OPR for local ASIP data collection.

11.10.6.2.1.2. (Added-Yokota) Approve and implement procedures for the collection and

submittal of ASIP data.

11.10.6.2.1.3. (Added-Yokota) Appoint, by letter, ASIP monitors to the applicable data

collection work centers (ASM, NDI).

11.10.6.2.2. (Added-Yokota) 374 MXS Non-destruction Inspection (NDI) and ASM section

will:

11.10.6.2.2.1. (Added-Yokota) Maintain an ASIP continuity book with appointment letters,

training plan, procedures, and this instruction.

11.10.6.2.2.2. (Added-Yokota) Develop a training plan specific to their ASIP role and

incorporate it into the section's training program. This plan is to be filed in the section ASIP

continuity book.

11.10.6.2.2.2.1. (Added-Yokota) Individual users of the Inspection Corrosion and Repair

Reporting (ICARR-3D) database will receive cascade training from the individuals qualified to

make inputs into the system. Training will consist of OJT and utilize the power point

presentation available on the AIRCAT website.

11.10.6.2.2.3. (Added-Yokota) Develop procedures for each ASIP inspection or related

function performed by their section. Ensure procedures cover the collection and submittal of

ASIP data as directed in applicable aircraft specific technical data and T.O.s. These procedures

will be approved by the ASIP Project Officer and filed in the section ASIP continuity book.

11.10.6.2.2.4. (Added-Yokota) Section ASIP monitors will collect and report inspections

tracking data for each airframe-specific Individual Aircraft Tracking Program (IATP) required

by appropriate Air Logistics Center and outlined in applicable T.O.s.

11.10.6.2.2.5. (Added-Yokota) For deployment purposes, the ASIP Lead Technician is the

ranking NDI technician deployed. If no NDI technician is deployed, the ranking ASM

technician is the lead technician. The ASIP Lead Technician is responsible for maintaining the

Inspection Corrosion and Repair Reporting (ICARR-3D) tool for any Yokota aircraft within the

deployed AOR. If ASIP inspections are performed and ICARR capability is nonexistent, the

lead technician will forward results to home station for input into ICARR. The home station

ASIP monitor is responsible for ensuring all reports are completed and distributed to appropriate

agencies.

11.10.6.2.2.6. (Added-Yokota) Record all nondestructive inspections directed by TO (positive

or negative findings) in ICARR-3D.

11.10.6.2.2.7. (Added-Yokota) Record all cracks in primary aircraft structure in ICARR-3D.

11.10.6.2.2.8. (Added-Yokota) Record all corrosion or other defects (i.e. gouges, dents) in

primary aircraft structure that exceed repairable limits of -3 series TO in ICARR-3D.

11.10.6.2.2.9. (Added-Yokota) Record all structural repairs for all reported defects in primary

aircraft structure in ICARR-3D.

11.10.6.2.3. (Added-Yokota) C-130 Maintenance Reporting Requirements:


11.10.6.2.3.1. (Added-Yokota) All maintenance actions that require reporting are identified in

the specific work cards, T.O.s and TCTOs. For example: 1C-130A-6, 1C-130A-6WC-5, 1C-

130A-36 and 1C-130A-3.

11.10.6.2.3.2. (Added-Yokota) All ASIP inspections listed in the applicable TOs are required

to be reported in ICARR.

11.10.6.2.3.3. (Added-Yokota) In addition to inspections, if a defect is found that requires a

structural repair of primary structure and skin, 11XXX or landing gear 13XXX, the repair action

must also be reported in ICARR.

11.10.6.2.3.4. (Added-Yokota) The ASIP monitor will accomplish all ASIP and ICARR data

by the close of ISO or within 1 duty day of the completion of the inspection, repair or upon

return from temporary duty location where there is no access to the Automated Inspection,

Repair Corrosion & Tracking System (AIRCAT).

11.10.6.2.4. (Added-Yokota) C-130 Maintenance Responsibilities:

11.10.6.2.4.1. (Added-Yokota) 374 MO (Maintenance Operations Flight/Plans, Scheduling and

Documentation Section) will ensure ASIP special inspections are properly loaded in the

appropriate Maintenance Information System (MIS) and notify the major command in the event

a special ASIP inspection has not been loaded into the MIS.

11.10.6.2.4.2. (Added-Yokota) The aircraft crew chief, or ISO Dock supervisor when the

aircraft is in ISO, will review and coordinate all ASIP inspections with appropriate production

supervisors and the ASM and/or NDI Sections (as required).

11.10.6.2.4.2.1. (Added-Yokota) The ISO Dock supervisor will ensure all ASIP inspections are

complied with prior to closing out the isochronal inspection.

11.10.6.2.4.3. (Added-Yokota) The aircraft crew chief, or ISO Dock supervisor when the

aircraft is in ISO, will ensure locations on their aircraft requiring ASIP inspections are

adequately disassembled and prepared to accommodate inspection equipment. If paints or

coatings are required to be removed from surfaces prior to the inspections being performed, the

crew chief will contact the ASM Section to have them chemically removed.

11.10.6.2.4.4. (Added-Yokota) When required, the ASM Section will prepare surfaces for

inspection and/or remove surface coatings IAW aircraft specific tech data and T.O. 1-1-8.

11.10.6.2.4.5. (Added-Yokota) The NDI Section will perform required ASIP inspections IAW

aircraft specific technical guidance and locally developed procedures. Data collected will be

uploaded to ICARR database within 1 duty day of completion.

11.10.6.2.4.6. (Added-Yokota) Quality Assurance will monitor the ASIP program with

periodic inspections identified in the Maintenance Standardization and Evaluation Program.

11.10.6.3. (Added-Yokota) C-130J Data Transfer and Diagnostic System (DTADS) data

collection and reporting. In addition to the guidance provided in the C-130J DTADS CONOPS

(published by AMC @

https://www.my.af.mil/gcssaf/USAF/AFP40/d/s6925EC1353610FB5E044080020E329A9/ Files/ a4q/a4qa/hello.html), the following guidance applies to the collection of DTADS data on

374 AW C-130Js.

https://www.my.af.mil/gcssaf/USAF/AFP40/d/s6925EC1353610FB5E044080020E329A9/


11.10.6.3.1. (Added-Yokota) Usage reporting from the Operations Group is used to establish

the inspection intervals for the aircraft, determine the service life of major components and the

schedule of aircraft retirements. The replacement of the center and outer wings are predicted

from this data.

11.10.6.3.1.1. (Added-Yokota) The Operations Group will appoint a primary and alternate

DTADS Monitor to work in conjunction with the ASIP and DTADS Project Officers. OG

DTADS Monitor responsibilities:

11.10.6.3.1.1.1. (Added-Yokota) Maintain a continuity binder to include, at a minimum, the

ASIP monitor appointment letters and training documentation.

11.10.6.3.1.1.2. (Added-Yokota) Ensure applicable C-130 flight data worksheets are submitted

into AIRCAT IAW TO 1C-130-101.

11.10.6.3.1.1.3. (Added-Yokota) Archive flight data worksheets for 2 years IAW TO 1C-130-

101.

11.10.6.3.2. (Added-Yokota) Maintenance Group reporting is necessary to determine

frequency of inspections on aircraft. Repairs that are installed on primary structure can change

standard inspection requirements or necessitate new inspections in order to insure the safety of

the aircraft.

11.10.6.3.3. (Added-Yokota) The 374 AMXS will be the lead squadron for DTADS data

collection and identify a DTADS Project Officer and alternate to manage overall data collection

and reporting. These project officers will be appointed by the MXG CC and will:

11.10.6.3.3.1. (Added-Yokota) Act as the main point of contact for MXG DTADS issues and

distribute applicable correspondence received from WR-ALC Robins AFB GA.

11.10.6.3.3.2. (Added-Yokota) Appoint in writing DTADS monitors to applicable workcenters

(Debrief, ISO).

11.10.6.3.3.3. (Added-Yokota) Perform quarterly spot checks on DTADS monitors and

document inspection results.

11.10.6.3.3.4. (Added-Yokota) Ensure cyber hygiene IAW Sections IV and V of the C-130J

DTADS CONOPS.

11.10.6.3.3.4.1. (Added-Yokota) Conduct weekly anti-virus scanning.

11.10.6.3.3.4.2. (Added-Yokota) Check for and apply Signature Updates weekly.

11.10.6.3.3.5. (Added-Yokota) Ensure approved removable media is scanned prior to use on

DTADS laptops.

11.10.6.3.4. (Added-Yokota) MXG DTADS Monitor responsibilities:

11.10.6.3.4.1. (Added-Yokota) Maintain a continuity binder to include, at a minimum, the

ASIP monitor appointment letters and training documentation.

11.10.6.3.4.2. (Added-Yokota) Ensure all required Flight Data Worksheets are available for

Aircrew at debrief locations.

11.10.6.3.4.3. (Added-Yokota) Verify the accuracy of Flight Data Worksheets before Aircrew

leaves debrief.


11.10.6.3.4.4. (Added-Yokota) Submit DTADS flight data download to the “J Model Data”

Graphical User Interface (GUI) found on the AIRCAT Web site not later than the next duty day

after mission completion.

11.10.6.3.5. (Added-Yokota) All documentation requirements for aircraft usage data collection

and submittal contained in TO 1C-130-101 will be adhered to by affected personnel.

11.10.6.3.6. (Added-Yokota) C-130J debrief personnel will follow DTADS usage guidance

contained in TOs 31S5-4-2834-1, 31S5-4-6197-1 and 31S5-4-6198-1.

11.10.6.3.7. (Added-Yokota) All aircraft usage data worksheets will be submitted as soon as

practical but no later than 15 days after mission completion IAW TO 1C-130-101.

11.10.6.3.8. (Added-Yokota) Procedures to collect and submit DTADS aircraft usage data at

deployed locations:

11.10.6.3.8.1. (Added-Yokota) All affected personnel will adhere to the guidance contained in

this instruction when deployed away from home station.

11.10.6.3.8.2. (Added-Yokota) If local instructions are already in place at the deployed

location, personnel will follow the local guidance in addition to the guidance contained within

this instruction to ensure accurate and on-time reporting while temporarily assigned away from

home station.

11.10.6.3.9. (Added-Yokota) Procedures, not listed in applicable TOs, to maintain flight data

recorders on equipped aircraft and the associated downloading equipment or storage media will

be addressed IAW TO 00-5-1.

11.13.1. (Yokota) General. Cannibalizations (CANNs) will be kept to a minimum and will be

done only when an aircraft on the printed flying schedule is Non-Mission Capable and the

mission critical part needed is not readily available from supply. An item will not be

cannibalized solely to improve aircraft availability, attain a Mission Capable (MC) rate, for

maintenance convenience, or to boost any other metric. When a CANN action is required, it is

important that the steps outlined in this section are followed. Compliance with these directions

will ensure the supply system accurately reflects demand for parts and the CANN actions are

properly documented in the aircraft forms and the G081 system.

11.13.8.7. (Added-Yokota) Isochronal (ISO)/Letter Check Aircraft: Coordinate approval for

CANN actions from MXS Production Superintendent. Parts will not be CANN’d from these

aircraft if the CANN of the required parts will adversely affect the flow of ISO/Letter Check

inspection, unless approved by the MXG/CD or higher. Additionally, aircraft possessed by

AFMC for depot maintenance will not be cannibalized without approval from the applicable

ALC Program Manager and in coordination with the MAJCOM functional manager.

11.13.9. (Added-Yokota) Specific Procedures, Individual Responsibilities and Documentation

Requirements for Removal (“T”) Actions.

11.13.9.1. (Added-Yokota) Production Superintendent will:

11.13.9.1.1. (Added-Yokota) Prior to performing a CANN action, verify the required

component cannot be sourced from LRS, TNB or back shop assets. If the component is not

available determine if or when a CANN is required.


11.13.9.1.2. (Added-Yokota) Determine which aircraft will be the donor. All spare

engine/propeller CANNs must be coordinated with the 374 MO Engine Manager and 374 MXG

spare engine CANN authorities.

11.13.9.1.3. (Added-Yokota) Notify DMS, MOC, and PS&D of the pending CANN action

with affected tail numbers and/or engine serial numbers.

11.13.9.2. (Added-Yokota) Decentralized Materiel Support (DMS):

11.13.9.2.1. (Added-Yokota) Document CANN log.

11.13.9.2.2. (Added-Yokota) Notify MOC of supply document number and CANN JCN.

11.13.9.2.3. (Added-Yokota) Update mark-for change in G081 and SBSS after MOC loads

CANN JCN in G081.

11.13.9.3. (Added-Yokota) Maintenance Operations Center (MOC) will:

11.13.9.3.1. (Added-Yokota) Create two maintenance jobs in G081: one for removal “T” and

another for replacement “U” of CANN components for aircraft to aircraft CANNs.

11.13.9.3.2. (Added-Yokota) Open maintenance job in G081 through screen 9111 for engine to

aircraft CANNs.

11.13.9.3.3. (Added-Yokota) Issue a CANN job control number.

11.13.9.4. (Added-Yokota) Flight Line Expediter/MXS Production Superintendent will:

11.13.9.4.1. (Added-Yokota) Notify MOC and Pro Super when CANN action is complete.

11.13.9.4.2. (Added-Yokota) Ensure “T” action is documented in aircraft forms.

11.13.9.5. (Added-Yokota) Maintenance Technician will:

11.13.9.5.1. (Added-Yokota) Remove the part IAW applicable technical order.

11.13.9.5.2. (Added-Yokota) Document in aircraft forms the completed “T” action. For engine

CANNs, document engine CANN log.

11.13.9.5.3. (Added-Yokota) Enter a job in the aircraft forms for the “U” action to be

completed when the part is replaced.

11.13.9.5.4. (Added-Yokota) Document completed “T” action in G081.

11.13.10. (Added-Yokota) Specific Procedures, Individual Responsibilities and

Documentation Requirements for Replacement (“U”) actions.

11.13.10.1. (Added-Yokota) Decentralized Materiel Support (DMS): Notify Production

Superintendent when MICAP parts are delivered.

11.13.10.2. (Added-Yokota) Production Superintendent will:

11.13.10.2.1. (Added-Yokota) Determine the priority for replacing CANN part.

11.13.10.2.2. (Added-Yokota) Notify flight line Expediter or MXS Production Superintendent

of part to install.

11.13.10.2.3. (Added-Yokota) Evaluate “CANN Aircraft” status to determine whether an

FCF/OCF is appropriate before returning aircraft to regular service.


11.13.10.3. (Added-Yokota) Flight Line Expediter/MXS Production Superintendent will:

11.13.10.3.1. (Added-Yokota) Ensure parts are installed on aircraft/engine.

11.13.10.3.2. (Added-Yokota) Ensure documentation is completed.

11.13.10.4. (Added-Yokota) Maintenance Technician will:

11.13.10.4.1. (Added-Yokota) Install part IAW applicable Technical Order.

11.13.10.4.2. (Added-Yokota) Sign off “U” action in aircraft forms or engine work package for

engine CANNs.

11.13.10.4.3. (Added-Yokota) Document “U” action in GO81.

11.13.10.4.4. (Added-Yokota) Ensure faulty component is properly dispositioned through

DMS, placed in aircraft Tail Number Bin, or installed on the CANN aircraft as directed by

Production Superintendent.

11.13.10.4.5. (Added-Yokota) If an operational check of system cannot be accomplished when

part is installed, a job will be generated and an entry put in aircraft forms listing all follow-on

maintenance required.

11.13.10.4.6. (Added-Yokota) For engine CANNs, all CANN parts (installed) will be tagged

using AFTO Form 350, Repairable Item Processing Tag, indicating an operational check due

because of CANN.

11.13.10.5. (Added-Yokota) 374 MO Engine Management Section Chief will update spare

engine AFTO Form 95/G081 when serially controlled items are removed.

11.16.3. (Added-Yokota) 374 MXG does not maintain an Aircraft Inlet/Intake/Exhaust

Certification program due to parent MDS MAJCOM not mandating this requirement for the C-

130. As such placement on the SCR for Engine Inlet/Exhaust Inspection Certification is not

required.

11.16.8. (Added-Yokota) Sections will create a WJQS task in TBA to document C130J

training qualifications as required.

11.17.1.3.1. (Added-Yokota) Maintenance personnel are not authorized to motor or start

installed engines at home station or deployed locations until all provisions, including

documentation of certification and proficiency are complied with. These requirements are

outlined in AFI 11-218 Aircraft Operation and Movement on the Ground, AFI21-101, Aircraft

and Equipment Maintenance Management, AFI36-2650, Maintenance Training, and this

instruction.

11.17.2. (Yokota) Use Aircraft Initial Engine Run Prerequisite Check list (MXG Form 13) of

this instruction to document/certify completion of all prerequisites. Unit training managers will

not request seats for personnel for initial engine run training without this prerequisite letter.

11.17.2.5. (Added-Yokota) Personnel qualified to operate AE 2100D3 engines on C-130J

aircraft at their last assignment must show proof of qualification (e.g. G081 training run,

Integrated Maintenance Data System (IMDS) training run or certificate). In addition, members

must complete requirements outlined in paragraph 11.17.14.5. of this instruction.


11.17.2.6. (Added-Yokota) Personnel must pass a pre-test administered by the MTS prior to

being scheduled for Phase 1 and Phase 2 training. The member must be scheduled for the pre-

test with the MTS by their work center supervisor by contacting one of the MTS Engine Run test

proctors at 225-8963.

11.17.2.6.1. (Added-Yokota) Upon the first unsatisfactory score on the pre-test, the MTS will

notify trainee’s work center supervisor and UTM of the failure. The member who failed the test

will report to their work center supervisor for additional documented technical data review.

Members will not be allowed to retake the test until at least 24 hours have passed. They must be

re-scheduled for the test by their work center supervisor with the MTS.

11.17.2.6.2. (Added-Yokota) Upon a second unsatisfactory score, the MTS will notify the

trainee’s NCOIC/Flight Chief and UTM. More training and tech data review must be conducted

and documented. The MTS will require an additional 24 hours and a signed memorandum by

the trainee’s Squadron Superintendent to be rescheduled for the pre-test.

11.17.5. (Added-Yokota) Phases 1 (academics) and 2 (simulator) of the program are taught by

Lockheed-Martin Technological Services at McChord AFB or a similarly capable facility and

will be scheduled through the MTS Scheduling Element. Squadrons will request Phase 1 and 2

training on the AF Form 898. Phase 3 (certification) is conducted by engine run certifiers within

the 374 MXG and will consist of a practical evaluation (certification run) by performing a

maximum power run with a certifier observing the operation from flight deck. Operational

checks to be accomplished by the engine run student are determined at the certifier’s discretion.

11.17.5.3. (Yokota) Engine run certifiers will use the Aircraft Engine Run Certification

Evaluation Checklist (MXG LCL 9) to evaluate and document the certification run. The certifier

will route a completed AF Form 2426 to UTM for update in G081.

11.17.6. (Added-Yokota) The written test (Part 1 and Part 2) will be administered by the 374

MTS. Members must pass Part 1 (emergency procedures) before being allowed to take Part 2.

Upon successful completion of both tests, engine run certifiers will use the Aircraft Engine Run

Certification Evaluation Checklist (MXG LCL 9) to conduct and document the certification run

and forward completed AF Form 2426 to the UTM for update in G081.

11.17.8.2.1. (Yokota) Decertification will be entered in the individual’s training records and

G081. Engine run personnel will be decertified for any of the following reasons:

11.17.8.2.1.1. (Added-Yokota) Not meeting the minimum prerequisite criteria in this

instruction.

11.17.8.2.1.2. (Added-Yokota) Failure to comply with published safety procedures.

11.17.8.2.1.3. (Added-Yokota) Failure to use applicable technical publications.

11.17.8.2.1.4. (Added-Yokota) Receiving a “FAIL” Quality Assurance assessment during

engine run operation.

11.17.8.2.1.5. (Added-Yokota) Failure to comply with 120-day proficiency requirements.

11.17.8.2.1.6. (Added-Yokota) Failure to complete annual recertification training.

11.17.10.5.1.1. (Added-Yokota) Document approval on an MFR, signed by Sq/CC, and

provide to MTS for rescheduling.



11.17.16.1. (Added-Yokota) 374 MXG Production Superintendents and Expeditors will:

11.17.16.1.1. (Added-Yokota) Contact the MOC for engine run clearance and provide

employee numbers of engine run personnel.

11.17.16.1.2. (Added-Yokota) Contact the MOC upon engine start and shut down.

11.17.16.2. (Added-Yokota) 374 MXG/MXOC will:

11.17.16.2.1. (Added-Yokota) Notify either, Ronin 10, Sumo 10, Ronin 11, or Ronin 15 of any

weather advisories that may prevent engine runs.

11.17.16.2.2. (Added-Yokota) C-130J specific course codes: C130 000541, C130 000626,

C130 000635

11.17.16.2.3. (Added-Yokota) Contact the tower and the Security Forces to coordinate the

maintenance operation then notify the Production Superintendent or Expeditor of clearance to

run engines.

11.17.16.3. (Added-Yokota) 374 MXG/MXOT will:

11.17.16.3.1. (Added-Yokota) Manage the Engine Run Training Plan (ERTP) and required

exams IAW applicable instructions.

11.17.16.3.2. (Added-Yokota) Verify prerequisites using the Aircraft Initial Engine Run

Prerequisite Checklist (MXG Form 13) prior to requesting seats for engine run initial training.

Maintain this form for 1 year or until the individual is scheduled for refresher training

(whichever occurs first).

11.17.16.3.3. (Added-Yokota) Schedule Phases 1, 2, and 3, simulator training and simulator

instructors as applicable.

11.17.16.3.4. (Added-Yokota) Coordinate with applicable Section Chief or equivalent for

decertification for overdue training, test failure, or overdue proficiency.

11.17.16.3.5. (Added-Yokota) Update engine run proficiency in G081.

11.17.16.4. (Added-Yokota) Sq CC, Superintendent and Flight CC/Chiefs will:

11.17.16.4.1. (Added-Yokota) Identify only the most qualified personnel for engine run

qualification.

11.17.16.4.2. (Added-Yokota) Verify all prerequisites are met and coordinate Aircraft Initial

Engine Run Prerequisite Checklist (MXG Form 13) prior to requesting personnel for engine run

training.

11.17.16.4.3. (Added-Yokota) Monitor qualifications and proficiency of all assigned engine-

run qualified personnel to ensure they continue to meet the minimum requirements for run

qualification.

11.17.16.4.4. (Added-Yokota) Schedule personnel for the appropriate phases of engine run

training when required.

11.17.16.4.5. (Added-Yokota) Decertify personnel who fail to meet minimum standards in

paragraph 11.17.8.2.1.


11.28.1. (Yokota) 374 AW CDDAR Policy.

11.28.1.1. (Added-Yokota) The Crashed, Damaged or Disabled Aircraft Repair (CDDAR)

program is established to recover damaged or disabled aircraft in minimum time to return Yokota

AB to operational status as soon as practical after a mishap. The CDDAR program will be

consistent with the following considerations:

11.28.1.1.1. (Added-Yokota) The requirement to reopen the runway for operational use.

11.28.1.1.2. (Added-Yokota) Prevention of secondary damage to the aircraft.

11.28.1.1.3. (Added-Yokota) Preservation of evidence for mishap investigation.

11.28.1.1.4. (Added-Yokota) Safety of personnel involved with recovery operations.

11.28.1.1.5. (Added-Yokota) IAW AFI 91-204, Safety Investigations and Reports, when an

aircraft is under investigation by the Interim Safety Investigation Board, recovery operations will

not proceed until the board president releases the aircraft. Personnel who are not engaged in the

investigation will remain outside of the recovery area. The crash recovery team may be called

upon to perform tasks as required by the investigation team.

11.28.1.2. (Added-Yokota) The CDDAR program instruction is procedural and will not take

precedence over aircraft-specific technical data in recovery of crashed, damaged or disabled

aircraft.

11.28.1.3. (Added-Yokota) Warning: Transient aircraft servicing air logistics center (ALC)

should be contacted to determine composite material risks and requirements for personal

protective equipment (PPE) and special handling instructions. Caution: The aircraft and crash

site will be disturbed only to the extent required to eliminate an imminently dangerous situation

to the aircraft, support equipment and personnel, and will remain in an undisturbed state until the

aircraft is released to maintenance by the incident commander.

11.28.2.8. (Added-Yokota) 374th Maintenance Squadron (374 MXS) Maintenance Flight will:

11.28.2.8.1. (Added-Yokota) Maintain a crash recovery trailer and equipment for home station

and funded/provided unique Air Mobility Command (AMC) aircraft specific CDDAR

equipment. Maintain inventories of specialized crash recovery tools, aircraft tow vehicle, tow

bar, slings, belly bands, snatch cables, air bags, CDDAR kits and current TOs to meet expected

crash recovery operations for home station and AMC supported aircraft. (AMC will

provide/maintain Technical Data for all AMC peculiar aircraft.)

11.28.2.8.2. (Added-Yokota) Provide personnel required to perform CDDAR operations.

11.28.2.8.3. (Added-Yokota) Provide primary and alternate Crash Recovery Team Chiefs

(CRTCs). CRTCs who have completed all training requirements will be identified on the

Special Certification Roster (SCR).

11.28.2.9. (Added-Yokota) 374 MXS Repair & Reclamation (R&R)/Transient Alert (TA)

Section will:

11.28.2.9.1. (374 AW-Added) Manage the CDDAR program and ensure personnel are trained

in recovery operations. Crash recovery team (CRT) composition and member duties are defined

in Attachment 14 of this instruction.


11.28.2.9.2. (Added-Yokota) Conduct CRT member training. Selected personnel will be

trained for emergency and nonstandard towing procedures, standard and nonstandard aircraft

lifting procedures, wear of PPE, and broken and fire-damaged composite material containment,

handling and disposal.

11.28.2.9.3. (Added-Yokota) Establish a crash recovery and composite material handling

training program. CDDAR personnel will accomplish annual training on Yokota AB assigned

mission design series (MDS) and AMC supported aircraft. Actual aircraft emergencies can be

substituted for the required training.

11.28.2.9.4. (Added-Yokota) Maintain equipment assigned to the crash recovery program.

Crash recovery equipment will be maintained in a ready-to-use condition and will receive the

highest priority when maintenance is required.

11.28.2.9.5. (Added-Yokota) Ensure CRT members are respirator fit tested by

Bioenvironmental Engineering and receive annual recertification.

11.28.2.9.6. (Added-Yokota) Maintain a current recall roster of all CRT personnel to include

730 AMS/UH-1/C-12 team members and provide current roster to 374 MO and 374 MXS as

required.

11.28.2.9.7. (Added-Yokota) The CRTC will be the most qualified fully trained CRTC

available. The CRT supervisor will:

11.28.2.9.7.1. (Added-Yokota) Provide the incident commander with a roster of CRT

personnel.

11.28.2.9.7.2. (Added-Yokota) Be responsible for ensuring the aircraft is moved to the

predetermined location, safely and expeditiously, using all resources available.

11.28.2.9.7.3. (Added-Yokota) Maintain complete control of the aircraft and the removal

procedure until it is moved to a predetermined location.

11.28.2.9.7.4. (Added-Yokota) Maintain a continuity binder containing at a minimum, PPE

guidelines, crash recovery checklists, event logs, and trailer equipment and tool inventories.

11.28.2.9.7.5. (Added-Yokota) Perform crash recovery trailer serviceability inspections before

and after each exercise and use. Monthly serviceability inspections will be documented on

AFTO Form 244, Industrial/Support Equipment Record.

11.28.2.9.7.6. (Added-Yokota) Perform inventory of all equipment and expendable items

before and after each exercise and use. At a minimum, the inventory will be documented semi-

annually.

11.28.2.9.7.7. (Added-Yokota) Be prepared to provide equipment and or personnel to perform

emergency tows.

11.28.2.9.7.8. (Added-Yokota) Ensure applicable 374 AW organizations and tenant units

participate in CDDAR exercises and training.

11.28.2.9.8. (Added-Yokota) Respond to in-flight emergencies (IFEs) when assistance is

required with at least two CRT members (CRT members will standby in recovery truck). In the

event manning does not allow for a tow team to be standing by during IFE, the CRT lead will

request production superintendents identify a tow team and the CRT will augment if required.


11.28.2.10. (Added-Yokota) 374 MXS Aerospace Ground Equipment (AGE) Flight will

maintain and deliver serviceable support equipment required to perform CDDAR operations (See

Attachment 15).

11.28.2.11. (Added-Yokota) 374 AW units will provide manpower and/or equipment, as

required, to support the CRT. The following units will provide MDS-specific manpower and/or

equipment for training and crash recovery, as required, by the CRTC.

11.28.2.11.1. (Added-Yokota) 374th Aircraft Maintenance Squadron (374 AMXS) will support

C-130 aircraft crash recovery with personnel as required, at the CRTC’s request.

11.28.2.11.1.1. (Added-Yokota) Provide maintenance representatives and/or manpower (crew

chiefs and/or specialists) to provide technical advice and technical data relative to safety,

operation or environmental hazards, when requested by the CRTC.

11.28.2.11.1.2. (Added-Yokota) Take charge of any emergency tow situations in the event an

aircraft without structural damage requires removal from the active runway, to include IFE

situations, hot brakes, and blown or flat tires.

11.28.2.11.2. (Added-Yokota) 374 MXG/MXQ will coordinate contractor support for incidents

involving assigned C-12 and UH-1N aircraft.

11.28.2.11.3. (Added-Yokota) Yokota Aero Club manager or the lead mechanic, will be

contacted for Yokota Aero Club aircraft recovery.

11.28.2.11.4. (Added-Yokota) 374 MXG Quality Assurance (QA)/730 AMS Quality

Assurance (QA) (as required) will:

11.28.2.11.4.1. (Added-Yokota) Ensure all aircraft AFTO Form 781-series

documentation/historical records, servicing equipment, and personal training records obtained by

374th Maintenance Operations (374 MO) are impounded upon notification of an accident/mishap

IAW 374 AW Mishap Response Plan.

11.28.2.11.4.2. (Added-Yokota) Inform the Maintenance Operations Center (MOC) to lock out

(isolate) the Integrated Maintenance Data System/G081 maintenance information system on the

affected aircraft.

11.28.2.11.4.3. (Added-Yokota) Coordinate with transient aircraft home station QA to ensure

the applicable Maintenance Information System is locked out (isolated) on the affected aircraft.

11.28.2.11.4.4. (Added-Yokota) Assist in calculating weight and balance of aircraft if required.

11.28.2.11.5. (Added-Yokota) 730th Air Mobility Squadron (730 AMS) will:

11.28.2.11.5.1. (Added-Yokota) Provide personnel and equipment as necessary for training

and recovery of AMC aircraft and assist with crash recovery operations with crew chief and

specialist support.

11.28.2.11.5.1.1. (Added-Yokota) Provide AMC aircraft specific equipment authorized in 751

or other applicable allowance standards, and personnel necessary for training and recovery of

AMC aircraft. Augment crash recovery operations manning with crew chief and specialist

support.

11.28.2.11.5.2. (Added-Yokota) Provide tow team and tow vehicle as required per

Memorandum of Agreement FB5209-03282-002 to support the CRT.


11.28.2.11.5.3. (Added-Yokota) Take charge of all AMC emergency tow situations in the

event an aircraft without structural damage requires removal from the active runway, to include

IFE situations, hot brakes, and blown or flat tires.

11.28.2.11.5.4. (Added-Yokota) Provide and maintain C-5, C-17 and KC-10 tow capability,

and coordinate with 618 TACC/XOCL for the rapid deployment of crash recovery equipment

and personnel for AMC aircraft.

11.28.2.11.5.5. (Added-Yokota) The 730 AMS Contract Airlift Administration (730

AMS/CCK), DSN 225-9307, will coordinate with the on-station operations handling agent and

owning airline for recovery assistance of civilian aircraft.

11.28.2.11.6. (Added-Yokota) 374th Civil Engineer Squadron (374 CES) will:

11.28.2.11.6.1. (Added-Yokota) Provide emergency crash and fire response, as well as

hazardous materials and spill containment capability beyond the scope of the unit spill teams.

11.28.2.11.6.2. (Added-Yokota) Provide heavy equipment and operators (e.g., bulldozers,

cranes (25-65 ton) and dump trucks) as required by the CRTC.

11.28.2.11.6.3. (Added-Yokota) Provide rapid runway repair and dunnage (6” x 6” x 8’) as

required by the CRTC. Provide the 374 MXS Repair and Reclamation Section an inventory of

rapid runway repair material and dunnage on hand. (If materials are provided by local vendor

then a signed copy of the contract need to be provided.

11.28.2.11.7. (Added-Yokota) 374th Security Forces Squadron (374 SFS) will provide

Security Forces personnel to secure mishap scene and the wreckage assembly point as directed

by the incident commander.

11.28.2.11.8. (Added-Yokota) 374th Logistics Readiness Squadron (374 LRS) will:

11.28.2.11.8.1. (Added-Yokota) Provide tractor trailers with flatbeds and forklifts, as

necessary, to transport CDDAR support equipment to the mishap site, as well as transport

wreckage to the wreckage assembly point.

11.28.2.11.8.2. (Added-Yokota) Provide maintenance support to heavy equipment

participating in the recovery operation as directed by the incident commander. (If heavy

equipment is provided by local vendor then a signed copy of the contract needs to be provided.)

11.28.2.11.8.2.1. (Added-Yokota) Maintain required minimum essential level (MEL) of

serviceable tow vehicles, and report shortages to PACAF/AMC, and fill shortages with War

Ready Material (WRM) or backfill assets.

11.28.2.11.8.3. (Added-Yokota) Provide on-scene fuel servicing of recovery support

equipment, to include aerospace ground equipment (AGE) and heavy equipment.

11.28.2.11.9. (Added-Yokota) The MOC will:

11.28.2.11.9.1. (Added-Yokota) Notify the R&R Section during IFEs, barrier engagement and

hot brake conditions. If the R&R Section cannot be reached after normal duty hours, the 374

MXS Production Superintendent will be contacted to determine the crash recovery response

actions.

11.28.2.11.9.2. (Added-Yokota) Assist on-scene maintenance representatives by coordinating

with other units and/or agencies as required.


11.28.2.11.9.3. (Added-Yokota) Notify the 374 MO Plans, Scheduling and Documentation

Section (374 MO/MXOOP) to gain possession of crashed aircraft IAW AFI 21-103, Equipment

Inventory, Status and Utilization Reporting.

11.28.2.11.9.4. (Added-Yokota) Notify the appropriate headquarters and owning organization

after initial response by the CRT. In the event a wide-bodied aircraft becomes disabled at

Yokota AB, the MOC will notify the Headquarters Pacific Air Forces Maintenance Engineering

Division (HQ PACAF/A4M) through the PACAF Command Center, DSN 315-948-8500, and

also request assistance through the following points of contact:

11.28.2.11.9.4.1. (Added-Yokota) E-4: 55 MOC, Offutt AFB, Nebraska, DSN 312-271-

5147/48.

11.28.2.11.9.4.2. (Added-Yokota) AMC aircraft: Tanker Airlift Control Center (TACC), Scott

AFB, Illinois, DSN 312-576-1706; 613 AOC/AMD, Hickam AFB, HI, DSN 315-448-8856

11.28.3. (Added-Yokota) Procedures.

11.28.3.1. (Added-Yokota) Upon declaration of a potential or actual major aircraft accident on

the runway or off base, including water recovery, the following sequence of events will occur.

All accident response agencies are notified according to Yokota Comprehensive Emergency

Management Plan 10-2.

11.28.3.1.1. (Added-Yokota) Upon notification of an aircraft mishap requiring recovery of a

damaged or disabled aircraft, the MOC will:

11.28.3.1.1.1. (Added-Yokota) Notify 374 MXS Production Superintendent and if AMC

aircraft, notify 730 AMS Production Superintendent as applicable of the requirement to recall

and assemble the CRT at a designated point.

11.28.3.1.1.2. (Added-Yokota) When responding to a disabled aircraft with hot brakes and

barrier engagement, the CRTC will coordinate with the base fire department and refer to

checklist, LCL “374 MXG-11 Aircraft Hot Brakes Response,” to ensure the aircraft is in a safe

condition before proceeding with removal procedures.

11.28.3.1.1.3. (Added-Yokota) Upon request of the incident commander or CRTC, contact the

transient aircraft home base and request technical order guidance for aircraft recovery operations.

11.28.3.1.1.4. (Added-Yokota) Dispatch the CRT to the accident scene via a designated safe

route as requested by and in coordination with, the incident commander.

11.28.3.1.1.5. (Added-Yokota) In the event an aircraft recovery requires movement of cargo by

normal or alternate means, the MOC will contact the 730 AMS/TR and the Emergency

Operations Center (EOC).

11.28.3.1.2. (Added-Yokota) The 374 MXS Production Superintendent and if AMC aircraft,

730 AMS Production Superintendent as required, will execute the CDDAR team recall

procedures and pass along all known information.

11.28.3.1.3. (Added-Yokota) The CRTC will:

11.28.3.1.3.1. (Added-Yokota) Assemble the CRT at a designated meeting area with the

immediate response trailer.

11.28.3.1.3.2. (Added-Yokota) Notify the EOC and MOC of assembly completion time.


11.28.3.1.3.3. (Added-Yokota) Notify the vehicle management flight dispatch office of a

possible requirement to move the crash recovery trailer and equipment.

11.28.3.1.3.4. (Added-Yokota) Brief the CRT on the situation, possibility of human remains,

and importance of not touching or disturbing the scene, and all known safety hazards.

11.28.3.1.3.5. (Added-Yokota) Monitor the designated crash net, review safety procedures and

aircraft technical data, and stand by until requested by the incident commander to proceed to the

accident scene.

11.28.3.1.3.6. (Added-Yokota) Respond to the accident scene when requested, obtaining

approval from incident commander or safety representative, and confirm with Bioenvironmental

Engineering to ensure the area is safe for entry.

11.28.3.1.3.7. (Added-Yokota) Obtain verification from the incident commander and

Explosive Ordnance Disposal (EOD) representative that all explosive items have been made safe

or removed as applicable.

11.28.3.1.3.8. (Added-Yokota) Assess site with the incident commander, configure the aircraft

and begin recovery actions.

11.28.3.1.3.9. (Added-Yokota) Ensure the first maintenance responders to the aircraft pull the

cockpit voice recorder circuit breakers if the aircraft is deemed safe by the incident commander.

11.28.3.2. (Added-Yokota) Designated individuals from the mishap aircraft organization will

ensure the following ground handling procedures are complied with:

11.28.3.2.1. (Added-Yokota) Disconnect batteries.

11.28.3.2.2. (Added-Yokota) Drain oil and fuel from tanks if required.

11.28.3.2.3. (Added-Yokota) Remove liquid oxygen if required.

11.28.3.3. (Added-Yokota) Crash Recovery operations in difficult to reach areas will be

coordinated through the incident commander and EOC. Several base resources may be needed to

ensure the appropriate equipment and personnel can be taken to the crash site in a timely manner.

11.28.3.3.1. (Added-Yokota) All personnel entering the crash site will wear proper PPE IAW

the site safety and health plan. Units are responsible for providing their personnel with proper

PPE.

11.28.3.3.2. (Added-Yokota) Recovery and removal of aircraft and aircraft parts will be IAW

AFI 91-204 to ensure preservation of evidence for safety and/or accident investigation boards.

11.28.4. (Added-Yokota) Training.

11.28.4.1. (Added-Yokota) All recovery team members must receive initial/annual training

comprised of both academic and hands-on training/exercises. Hands-on training includes aircraft

lifting exercises using a unit owned aircraft or AMC transient aircraft coordinated with 730

AMS.

11.28.4.2. (Added-Yokota) All training events will be conducted by a CRTC and/or an AMC

aircraft subject matter expert (SME) from Yokota AB, Japan. Academic training will be

conducted by Air Education and Training Command (AETC) Training Detachments (TD) at

bases with an assigned TD using an approved Plan of Instruction. It is critical that members


ensure all training is documented in Training Business Area (TBA) and GO81 upon completion.

Operational aircraft will not be used for actual aircraft lifts for training events.

11.28.4.3. (Added-Yokota) Personnel that were previously qualified and actively serving in a

CDDAR capacity are exempt from attending the AETC CDDAR training course. Units are

highly encouraged to schedule these personnel for this training as workload permits.

11.35. (Added-Yokota) Aircraft Wash and Corrosion Prevention Program. In addition to the

guidance provided in AFI 21-105, TO 1-1-691, and associated MAJCOM supplements, the

following directs the implementation of corrosion control and wash rack procedures for 374 AW

personnel.

11.35.1. (Added-Yokota) Philosophy:

11.35.1.1. (Added-Yokota) All maintenance and operations personnel, regardless of Air Force

Specialty Code (AFSC), are responsible to document potentially corroded structures/components

in the proper maintenance forms. The Aircraft Structural Maintenance (ASM) Section evaluates

corrosion discrepancies to determine proper treatment or repair.

11.35.1.2. (Added-Yokota) Clean aircraft metal components with only approved cleansers

IAW the current Qualified Products List (QPL). The current QPL can be obtained from the Wing

Corrosion Manager.

11.35.2. (Added-Yokota) Wing Corrosion Manager Responsibilities:

11.35.2.1. (Added-Yokota) Ensure that only properly trained personnel operate shop corrosion

prevention equipment.

11.35.2.2. (Added-Yokota) Works with the Fabrication Flight Chief to ensure 2A7X3

technicians receive adequate training (formal and on-the-job) to accomplish assigned tasks.

11.35.2.3. (Added-Yokota) Oversees corrosion control maintenance actions at the aircraft wash

facility and corrosion control hangar, or any other location where corrosion control maintenance

actions are taking place in support of the 374 AW mission.

11.35.2.4. (Added-Yokota) Reviews the QPL for approved corrosion control materials at least

every six months as issued by the AF Corrosion Prevention and Control Office (AFCPCO). The

most current document will be kept in the Wing Corrosion Manager’s continuity book.

11.35.2.5. (Added-Yokota) Provides Maintenance Operations Training Section current training

materials for unit-specific Corrosion Awareness Training conducted in Block Training.

11.35.3. (Added-Yokota) Contracted Wash Crew. 374 AW C-130 aircraft Wash Crew

Supervisors and wash crews are a contracted function. The contractor wash crew supervisor

will:

11.35.3.1. (Added-Yokota) Together with an ASM representative, inspect the wash facility

CTK and wash rack before beginning any aircraft wash. The Wash Crew Supervisor will indicate

acceptance of the condition of the wash facility and CTK by signing a locally generated control

log AF Form 1297, Temporary Issue Receipt, maintained by the ASM Support Section. The

ASM representative will sign out the wash facility and CTK in TCMax.


11.35.3.2. (Added-Yokota) Together with an ASM representative, perform a joint inventory of

the wash rack CTK and sign it back in on a locally generated control log or 1297 and in TCMax

before releasing the wash crew at the end of each wash day.

11.35.4. (Added-Yokota) Wash Rack Non-Commissioned Officer in Charge (NCOIC)

responsibilities:

11.35.4.1. (Added-Yokota) Ensures fall protection lifeline cables are installed and serviceable.

11.35.4.2. (Added-Yokota) Ensures cleaners and equipment are authorized, procured, available

and properly used, to include proper mix ratio IAW applicable T.O. or instruction.

11.35.4.3. (Added-Yokota) Ensures wash rack facility and surrounding area are kept clean and

properly maintained.

11.35.4.4. (Added-Yokota) Ensures the facility and equipment are cleaned and properly stored

upon completion of each wash and Foreign Object Debris (FOD) control procedures are

followed IAW paragraph 11.8 of this instruction.

11.35.4.5. (Added-Yokota) Ensures all wash rack equipment is in serviceable condition, and

coordinates maintenance actions as needed.

11.35.4.6. (Added-Yokota) Ensures Composite Tool Kit (CTK) procedures are followed and

scrub pads are controlled in the same manner as rags IAW Chapter 8 of this instruction.

11.35.5. (Added-Yokota) Aircraft Owning Activity Responsibilities:

11.35.5.1. (Added-Yokota) Appoint two Aircraft Wash Monitors and ensure the monitor has a

functioning LMR.

11.35.5.2. (Added-Yokota) Coordinate and schedule use of the wash rack facility through the

374th Maintenance Operations Plans, Scheduling and Documentation (374 MXG/MXOS) for all

aircraft washes to include major inspections. Schedule changes prior to the day of the wash will

be coordinated through 374 MXG/MXOS.

11.35.5.3. (Added-Yokota) In the event a wash schedule change or cancellation on the day of

the wash, the owning activity will inform 374 MXG/MXQ Contracting Officer Representative

(COR) prior to 0515 the morning of the wash. The COR will ensure the contractor, 374

MXG/MXOS, and the Wash Rack Facility Manager are informed of all schedule changes and

cancellations.

11.35.5.4. (Added-Yokota) Notify the COR upon completion of the wash. The COR will

accomplish and document a cleanliness inspection (AMC Form 1018 or equivalent) on the

aircraft prior to release back to the owning activity.

11.35.5.5. (Added-Yokota) The Aircraft Owning Activity will perform a FOD walk before the

aircraft is towed on to the wash rack and no later than 30 minutes after the aircraft is towed out

of the facility.

11.35.5.6. (Added-Yokota) Utilize the approved wash prep sheet for all aircraft washes.

11.35.6. (Added-Yokota) Aircraft Wash Monitors will:


11.35.6.1. (Added-Yokota) Monitor aircraft wash progress, ensure safe operations and provide

contractors escorted access to the restricted area for the duration of contracted aircraft washing

duties.

11.35.6.2. (Added-Yokota) Contact ASM for issues dealing with the wash facility, equipment

or supplies.

11.35.6.3. (Added-Yokota) Immediately contact the MOC in the event of personnel injuries or

damage to aircraft or equipment.

11.35.6.4. (Added-Yokota) Contact the COR for any issues or requirements identified by the

contractors.

11.35.6.5. (Added-Yokota) Contact 374 SFS for security related concerns.

11.35.7. (Added-Yokota) ASM representative will:

11.35.7.1. (Added-Yokota) After the COR has determined that the aircraft wash is complete,

an ASM representative will perform an inspection of the wash rack and equipment inventory to

release the Aircraft Wash Monitor from responsibility of the wash rack.

11.35.8. (Added-Yokota) Contracting Officer Representative (COR):

11.35.8.1. (Added-Yokota) Provide a long range forecast of at least 60 days to the Contractor

of all aircraft scheduled for wash.

11.35.8.2. (Added-Yokota) Verify that the owning organization has completed the wash prep

sheet (MXG Form 12) on the day of the wash prior to 0800.

11.35.8.3. (Added-Yokota) Ensures contractors complete aircraft wash in a satisfactory

condition.

11.35.9. (Added-Yokota) Cleaning and Aircraft Wash Documentation:

11.35.9.1. (Added-Yokota) The Aircraft Owning Activity will load the wash and lubrication

JST against the aircraft in G081 and enter the printed AFTO 781A forms in the aircraft active

781 binder. The COR will verify and sign off 781A entries for tasks performed and completed

by contractors.

11.35.9.2. (Added-Yokota) The Owning Activity will sign the Scheduled Maintenance JCN for

“180 Day Acft Wash” after ensuring all wash package discrepancies have been completed and

signed off

11.35.10. (Added-Yokota) Protective Coating Maintenance:

11.35.10.1. (Added-Yokota) Maintenance painting is defined for field purposes as spot

painting, sectionalized painting, and complete scuff sand and overcoat. Maintenance painting of

aircraft will not be accomplished solely for cosmetics because of environmental and overall

aircraft weight and balance concerns.

11.35.10.2. (Added-Yokota) The 374 MXS ASM Section will determine priority for

maintenance painting by scoring all aircraft coating systems IAW T.O. 1-1-8, Application and

Removal of Organic Coatings, Aerospace and Non-Aerospace Equipment, paragraph 8.2.4. The

374 MXS AGE Flight will score all assigned AGE/Support Equipment.


11.35.10.2.1. (Added-Yokota) At a minimum aircraft protective coating will be scored after

each 180-day aircraft wash. The Wing Corrosion Manager is responsible for retaining a copy of

all paint scores until they are superseded or the equipment is taken out of service.

11.35.10.2.2. (Added-Yokota) Paint scoring of aircraft or AGE/support equipment will only be

accomplished during daylight hours, if outdoors, to ensure thorough assessment of protective

coating conditions.

11.35.10.2.3. (Added-Yokota) Complete over coating of AGE/support equipment will be

scheduled by AGE and Fabrication Flight according to mission requirements and current coating

condition. Maintenance painting of deteriorated areas will be done to prevent or repair corrosion.

11.35.10.3. (Added-Yokota) Non-critical corrosion control tasking (painting of FOD cans,

chocks, signs etc.) will be kept to an absolute minimum. In cases where non-critical items are

painted the local manufacture process will be followed.

11.35.10.4. (Added-Yokota) Use of Fabrication Flight personnel, assets, or materials for

fabrication of non-mission oriented projects, such as gifts, awards, or mementos is strictly

prohibited unless authorized by the Fabrication Flight Chief and MXS Maintenance Operations

Officer or higher, to minimize impact to mission requirements and/or the availability of parts and

assets.

11.35.10.5. (Added-Yokota) All maintenance and operations personnel, regardless of Air

Force Specialty Code (AFSC), are responsible to document potentially corroded

structures/components in the proper maintenance forms. The Aircraft Structural Maintenance

(ASM) Section evaluates corrosion discrepancies to determine proper treatment or repair.

11.35.10.6. (Added-Yokota) Use padded panel racks to store panels/parts for aircraft and

equipment during maintenance. When panels are stored or laid on hangar floors, parking ramp

surfaces, aircraft cargo bay floors, or any other hard surface that could scratch or mar protective

coatings (paints), ensure padding is placed between the panel and hard surface. Use protective

measures to prevent abrasions/scratches resulting from placement of parts from tools, tool boxes,

etc.

11.35.10.7. (Added-Yokota) When large sections are repainted refer to applicable weapon

system TO for potential Weight and Balance (W&B) requirements.

11.35.10.8. (Added-Yokota) When large portions of the aircraft are repainted (i.e. full wing,

large portions of the fuselage, flight controls, etc.) the AFTO Form 95 will be annotated with the

type of paint and exact location.

11.35.10.9. (Added-Yokota) All touch-up painting will be accomplished from seam-to-seam,

and will be masked at the edges. Where a seam is not reasonably accessible, a “simulated” seam

may be created. No unmasked spray touch-up is authorized.

11.35.11. (Added-Yokota) Specific markings guidance:

11.35.11.1. (Added-Yokota) Radomes: C-130 radomes will be painted flat grey, as per

applicable aircraft paint drawings. Every effort will be made to paint radomes to their proper

color prior to install.


11.35.11.2. (Added-Yokota) Crew Chief names: DCC and ADCC names will be applied to the

exterior of the aircraft and centered with the bottom of the ADCC name 6 inches above the crew

entry door. Position the DCC name centered above the ADCC name with a 1-inch space

between the names. The names will be 3-inch block style lettering. Painted or peel and stick

lettering is acceptable; color will match the unit designator color. Names applied must be their

given name only. An individual’s first name can be either the given proper name (William,

Robert, James, etc.) or the more familiar, shorter form of the proper name (Bill, Bob, Jim, etc.).

The title “DCC” or "ADCC" will not precede the crew chief names.

11.35.11.2.1. (Added-Yokota) Crew Chief names are added to aircraft in recognition of the

significant level of responsibility inherent to the Dedicated Crew Chief (DCC) program. Having

their name on their primary aircraft instills pride and a sense of ownership; therefore, DCCs will

apply their names to their aircraft in the approved location upon appointment to their DCC role.

11.35.11.2.2. (Added-Yokota) The 374 MXS Fabrication Flight will provide the names and

materials necessary to facilitate the install.

11.35.11.3. (Added-Yokota) Nose Art. Aircraft nose art will only be applied to flagship aircraft

or aircraft specifically designated by waiver. Decal will be centered on FS 148 and WL 210.

Nose art approval documentation will be maintained with the Wing Corrosion Manager.

11.35.12. (Added-Yokota) AGE Corrosion Requirements:

11.35.12.1. (Added-Yokota) AGE Flight will visually assess equipment paint condition and

overall unit corrosion, at a minimum, during every scheduled periodic inspection. This includes

complying with a 180 day wash cycle (IAW 35-1-3, paragraph 2.1.2., Table 2-1). Also, all AGE

will have a corrosion control inspection scheduled in the MIS and performed every 2 years. This

inspection will be completed and signed off in the MIS by a 5-skill level or above Aircraft

Structural Maintenance (ASM) Specialist as coordinated between AGE and ASM monitors.

ASM will complete the corrosion checklist and provide it to AGE personnel for filing into the

equipment historical records and/or for updating the corrosion tracker. AGE will attend the

monthly shared resources meeting to ensure corrosion control painting requirements are

identified and scheduled as required.

11.35.12.2. (Added-Yokota) AGE will perform the following preparations before the

equipment will be accepted by the Corrosion Control Section for refurbishment:

11.35.12.2.1. (Added-Yokota) Non-powered equipment: Remove bumper pads, tie down

straps, webbing hoses, mobility placards, stickers/stencils, and any other items that would

prevent proper sanding or painting of equipment.

11.35.12.2.2. (Added-Yokota) Powered equipment: Remove batteries, bleed air hoses, power

cables, air conditioner and heater ducts, hydraulic test stand hoses, mobility placards,

stickers/stencils, insulation, and any other items that would prevent proper sanding or painting of

equipment.

11.35.12.3. (Added-Yokota) All support equipment scheduled for paint will be delivered to

Corrosion Control NLT 1500 hrs each Friday prior to the scheduled paint week. Equipment will

be accompanied with a GO81 350 tag and will be logged into the Corrosion Control section’s

parts log by the AGE driver. Failure to prep/deliver all scheduled units on-time with the required

documentation completed will result in a delay or possible refusal of item(s) for that week.


11.35.13. (Added-Yokota) Corrosion Prevention and Control Training:

11.35.13.1. (Added-Yokota) Aircraft Wash Training:

11.35.13.1.1. (Added-Yokota) Personnel assigned as wash supervisors, cleanliness inspectors,

wash personnel, and wash contractor quality assurance evaluators will complete the Aircraft

Washing Procedures (Course C6ANU00TVT0001) video downloadable from

https://a4mxtng.csd.disa.mil (under the heading of “Course List” choose “general” then choose

the course title).

11.35.13.2. (Added-Yokota) Annual Corrosion Prevention and Control Training:

11.35.13.2.1. (Added-Yokota) Maintenance Operations Training Section will conduct unit-

specific Corrosion Awareness Training as a part of Maintenance Block Training. This training is

an annual requirement for all aircraft maintenance personnel (AFSC 2A7X3 is exempt from this

training). Training will include:

11.35.13.2.1.1. (Added-Yokota) The Corrosion Control Familiarization Course 1

downloadable video (https://www.youtube.com/watch?v=EHMW0_iKzPs or

https://www.my.af.mil/gcss-

af/USAF/ep/browse.do?programId=t88B4F00B441D422B014427477A10019B&channelPag

eId=s6925EC133EFE0FB5E044080020E329A9).

11.35.13.2.1.2. (Added-Yokota) Corrosion identification procedures and techniques using the

most current available Air Force aircraft corrosion visual training aids and information.

11.35.13.2.1.3. (Added-Yokota) Identification of corrosion prone areas on unit specific

weapon systems and equipment.

11.35.13.2.1.4. (Added-Yokota) Importance of proper selection and use of sealants, CPC, and

lubricants.

11.35.13.2.1.5. (Added-Yokota) Proper selection and use of all cleaning materials.

11.35.14. (Added-Yokota) Maintenance personnel shall report all corrosion deficiencies

through the applicable MIS IAW 00-20 series technical orders. Accurate documentation of

maintenance actions in support of the corrosion control program is essential to support future

manning, equipment requirements, training and parts/material procurement requirements.

11.35.14.1. (Added-Yokota) ICARR-3D Reporting (C-130 users). NDI, ASM and QA

personnel shall use the Inspection, Crack/Corrosion And Repair Reporting (ICARR-3D)

software to make inputs to the Automated Inspection, Repair, Corrosion, and Aircraft Tracking

(AIRCAT) database for all NDI directed by technical orders; cracks and corrosion exceeding

blending limits of Structural Repair Manual; and structural repairs IAW 1C-130A-6/1C-130J-6.

Corrosion within blending limits of the Structural Repair Manual shall not be documented. This

is an Aircraft Structural Integrity Program (ASIP) requirement. See

https://c130aircat.robins.af.mil/ for program instructions and information on ICARR-3D.report

all C-130 discrepancies in ICARR-3D.

11.36. (Added-Yokota) Local Repeat, Recurring, and Cannot Duplicate (CND) procedures.

11.36.1. (Added-Yokota) Definitions.

https://a4mxtng.csd.disa.mil/

https://www.youtube.com/watch?v=EHMW0_iKzPs

https://www.my.af.mil/gcss-af/USAF/ep/browse.do?programId=t88B4F00B441D422B014427477A10019B&channelPageId=s6925EC133EFE0FB5E044080020E329A9



https://c130aircat.robins.af.mil/


11.36.1.1. (Added-Yokota) Repeat Discrepancy: A discrepancy that occurs on the next sortie

or attempted sortie after corrective action has been taken and the system or subsystem indicates

the same malfunction when operated.

11.36.1.2. (Added-Yokota) Recurring Discrepancy: A discrepancy that occurs on the second

through fourth sortie or attempted sortie after corrective action has been taken and the system or

subsystem indicates the same malfunction when operated.

11.36.1.3. (Added-Yokota) CND discrepancy: Any discrepancy that cannot be duplicated by

maintenance personnel.

11.36.2. (Added-Yokota) Identifying Repeat/Recurring Discrepancies. Repeat/recurring

discrepancies will be identified as follows:

11.36.2.1. (Added-Yokota) The Debrief Section will utilize the MIS to the maximum extent

possible to match the current discrepancy to similar/identical discrepancies.

11.36.2.2. (Added-Yokota) The Debrief Section will enter the discrepancy in G081 and type

“REPEAT” or “RECURRING” and the job control number of the initial write-up in the

discrepancy block, and stamp or write “REPEAT” or “RECURRING” in red in the discrepancy

block of the AFTO Form 781A, Maintenance Discrepancy and Work Document.

11.36.2.3. (Added-Yokota) When entering the discrepancy in G081, the Debrief Section will

also ensure “Repeat” or “Recurring” is selected and the job control number of the initial write-up

is included under “Miscellaneous Data” to aid Maintenance Analysis tracking.

11.36.3. (Added-Yokota) Actions for Clearing Repeat/Recurring Discrepancies.

Repeat/recurring discrepancies will be cleared as follows:

11.36.3.1. (Added-Yokota) First repeat/recurrence: A SCR-qualified 7-skill level or higher

and/or civilian equivalent technician will review the discrepancy and corrective action(s). If all

actions were appropriate, the reviewer will sign the “Inspected By” block and initial over the

symbol.

11.36.3.2. (Added-Yokota) Second repeat/recurrence: A SCR-qualified Production

Superintendent will review the discrepancy and corrective action(s). If all actions were

appropriate, the Production Superintendent will sign the “Inspected By” block and initial over

the symbol.

11.36.3.3. (Added-Yokota) Third repeat/recurrence: The Aircraft Maintenance Unit

OIC/Superintendent will thoroughly review the discrepancy and all corrective actions. Consider

aircraft impoundment and/or the forming of a “Blue Ribbon Team” of highly qualified

technicians to troubleshoot and correct the discrepancy. For mission-essential systems, the

Operations Officer and Maintenance Superintendent will consider impounding the aircraft until

the discrepancy has been corrected. A SCR-qualified Squadron Production Superintendent will

sign the “Inspected By” block of the 781A, Maintenance Discrepancy and Work Document.

11.36.3.4. (Added-Yokota) Actions for clearing CNDs. CNDs will be cleared IAW TO 00-20-

1, AMC SUP 1, Aerospace Equipment Maintenance Inspection, Documentation, Policy and

Procedures Air Mobility Command Supplement.

11.37. (Added-Yokota) Additional Measures Following UH-1N Transmission Change


11.37.1. (Added-Yokota) This instruction is designed to prevent precautionary landings

outside Yokota Air Base (AB) due to chip light illumination after UH-1 transmission

replacement. Due to the increased possibility of a chip light illuminating during break-in of a

new transmission, 374 AW personnel and UH-1 contract maintenance employees will perform

post main gearbox chip light prevention procedures as outlined in this instruction. No additional

training is required.

11.37.2. (Added-Yokota) After transmission replacement, the aircraft will be restricted to the

local Yokota pattern area for at least the first 20 flight hours.

11.37.3. (Added-Yokota) Waiver Request. The 374th Maintenance Group Commander (374

MXG/CC) is the waiver authority to deviate from flight hour inspection criteria. The 374th

Operations Group Commander (374 OG/CC) is the waiver authority to deviate from the local

Yokota pattern.

11.37.4. (Added-Yokota) Responsibilities.

11.37.4.1. (Added-Yokota) UH-1 Maintenance Contractor. The contractor will perform the

following actions before the first flight after changing a main transmission:

11.37.4.1.1. (Added-Yokota) Annotate the following info note in front of the AFTO Form

781A, Maintenance Discrepancy and Work Document: “Due to main transmission change, this

aircraft is restricted to local Yokota pattern area flying during a 20-flight hour break-in period.

Aircraft will not depart local Yokota pattern until AIRCRAFT has reached at least XXXX.X

hours and the 374 MXG/CC has approved release from this restriction. The local Yokota pattern

is defined such that if a precautionary landing is required it can be accomplished within the

controlled movement area.”

11.37.4.1.2. (Added-Yokota) Drain, flush and inspect transmission oil and chip detector upon

completion of the Functional Check Flight (FCF). Conditional Release: During the restriction

period in paragraph 11.37.2., all exceptional releases will be signed off as a conditional release

IAW T.O. 00-20-1.

11.37.4.1.3. (Added-Yokota) Inspect the chip detector and external filter after the completion

of each sortie.

11.37.4.1.3.1. (Added-Yokota) If no debris is found during inspection, the aircraft may be

scheduled to fly again.

11.37.4.1.3.2. (Added-Yokota) If debris is found within limits, clean the detector, drain and

flush oil, and change external filter.

11.37.4.1.3.3. (Added-Yokota) If debris is found outside limits, follow appropriate TO

guidance.

11.37.4.1.4. (Added-Yokota) Inspect the chip detector at 30 and 100 flight hours after the

transmission change following the steps in paragraphs 11.37.4.1.3.1.-11.37.4.1.3.3.

11.37.4.1.5. (Added-Yokota) Send any metal particles found during inspections performed

above to Corpus Christi Army Depot (CCAD) for analysis and report findings to the 580th

Aircraft Sustainment Group at Warner Robins Air Logistics Center (WR-ALC).


11.37.4.1.6. (Added-Yokota) Discuss aircraft limitations during daily/weekly scheduling

meetings to ensure mission profile matches aircraft capability, and affected agencies are aware of

an aircraft restriction before it is flown after a main transmission change.

11.37.4.1.7. (Added-Yokota) Track restriction on their daily UH-1 spreadsheet.

11.37.4.1.8. (Added-Yokota) Upon release by 374 MXG/CC, remove the info note from the

front page of the aircraft AFTO Form 781A.

11.37.4.2. (Added-Yokota) 459th Airlift Squadron (459 AS). The 459 AS will:

11.37.4.2.1. (Added-Yokota) The 459 AS will ensure all UH-1 crew members and schedulers

are aware of the contents of this instruction and the restrictions to mission profiles for aircraft

following a main transmission change to include the definition of “Local Pattern.”

11.37.4.2.2. (Added-Yokota) The 459 AS and scheduler will document the aircraft restriction

on the scheduling board.

11.37.4.2.3. (Added-Yokota) The 459 AS will communicate aircraft limitations during daily

scheduling meetings to ensure mission profiles match aircraft capability.

11.37.4.3. (Added-Yokota) MOCC. The MOCC will:

11.37.4.3.1. (Added-Yokota) Update aircraft status slides to include a “Restricted to Local

Pattern” notation and time to next scheduled transmission inspection.

11.37.4.4. (Added-Yokota) 374 MXG/CC. The 374 MXG/CC will:

11.37.4.4.1. (Added-Yokota) Release the aircraft for normal operations if the chip light has not

illuminated during the first 20 flying hours after transmission change.

11.37.4.4.2. (Added-Yokota) Consider extending this process in 5 flight hour increments if the

chip light illuminates during the first 20 flying hours after the transmission change.

11.37.5. (Added-Yokota) UH-1 Maintenance Contractor Exemptions. The 374 AW will not

hold contractor liable to provide aircraft as outlined in Appendix 1, Table 1.1 and Appendix 1,

paragraph 1.2.4. of the performance work statement contract # FA6800-16-C-0003 during

periods aircraft are restricted due to transmission change.

11.38. (Added-Yokota) Local Hangar Door Safety and Operation Guidance.

11.38.1. (Added-Yokota) This section is designed to prepare personnel to safely and

effectively operate or enter and exit through hangar doors. Hangar Door Operation Qualification

Training is mandatory for all personnel who operate hangar doors or require access through

hangar doors in the performance of routine duties (work in hangar facilities, supply/equipment

deliveries, aircraft cargo loading, 374th Civil Engineer Squadron Fire Emergency Services [374

CES/CEF], 374th Security Forces Squadron [374 SFS], 374 CES Maintenance, etc.).

11.38.2. (Added-Yokota) Following table identifies hangars on Yokota AB and the responsible

agency:


Table 11.5. (Added-Yokota) Hangars on Yokota AB and the Responsible Agency.

Hangar Owning Agency

Bldgs 1, 75, 103, 510, 906, 907, 1503, 1505,

1587

374th Maintenance Squadron

Bldg 95 Det 2, PACAF Air Postal Squadron

Bldg 96 730th Air Mobility Squadron

Bldg 97 374th Security Forces Squadron

Bldg 102 374th Civil Engineer Squadron

Bldgs 400, 800 374th Logistics Readiness Squadron

Bldg 702 459th Airlift Squadron

Bldg 1504 374th Force Support Squadron

11.38.3. (Added-Yokota) Policies. Personnel are not authorized to operate or perform hangar

door procedures until all provisions, including documentation of certification and proficiency

training, have been completed.

11.38.4. (Added-Yokota) Responsibilities.

11.38.4.1. (Added-Yokota) Squadron commanders (through their respective operations

officers, superintendents and supervisors as needed) will:

11.38.4.1.1. (Added-Yokota) Ensure all personnel comply with this instruction.

11.38.4.1.2. (Added-Yokota) Identify personnel who are required to operate hangar doors in

the performance of routine duties, ensure these personnel are properly trained to perform hangar

door operations, and ensure the training is properly documented. This requirement applies to all

organizations and is not limited to the 374th Maintenance Group (374 MXG) or maintenance Air

Force Specialty Codes (AFSC).

11.38.4.1.3. (Added-Yokota) Identify personnel who routinely work in hangars (regardless of

AFSC or duties). Ensure these personnel receive proper hangar door awareness training, and

ensure the training is properly documented.

11.38.4.1.4. (Added-Yokota) Brief their respective group commander on hangar doors

rendered inoperative, repair status, and the expected completion date for corrective actions at

least once a month.

11.38.4.2. (Added-Yokota) Building custodians will:

11.38.4.2.1. (Added-Yokota) Be responsible for ensuring hangar door serviceability in

accordance with AFMAN 91-203, paragraph 24.14.8.7.

11.38.4.2.2. (Added-Yokota) Ensure requirements outlined in AFMAN 91-203 are maintained.

11.38.4.2.3. (Added-Yokota) Ensure a DANGER sign is mounted next to all hangar door

controls. Overall sign dimensions will be 7 inches by 10 inches. “DANGER” must be printed

on top in 1 7/16-inch red lettering. Message below “DANGER” must contain the following


statement using black lettering: “Only authorized personnel may operate hangar doors.” This

sign must be in English and Japanese.

11.38.4.2.4. (Added-Yokota) Maintain luminescent or reflective directional arrows adjacent to

each switch and on horizontal sliding doors to indicate the direction of door travel for each

corresponding switch.

11.38.4.2.5. (Added-Yokota) Ensure all hazards are identified. All areas that pose a potential

pinch point or crush area must be marked with 2 to 3-inch yellow and black hash-mark lines to

ensure no one enters these areas during door operation. Additionally, all hangar door pocket

areas will have a 14-inch by 20-inch “DANGER” sign painted on the floor. “DANGER” must

be in red with 3-inch letters. The message below “DANGER” must contain the following

statement in black with 3-inch letters: “HAZARDOUS AREA-STAND CLEAR DURING

DOOR OPERATION.” The sign will be placed so that it can be read when approaching the

hazard area and must be in English and Japanese.

11.38.4.2.6. (Added-Yokota) Ensure door control panels are marked appropriately.

11.38.4.2.7. (Added-Yokota) At a minimum, conduct a monthly review to identify and

document conditions where hangar doors, signs, or other related items do not conform to

established AFI requirements, and initiate a CE work order (AF Form 332, Base Civil Engineer

Work Request) for any discrepancies requiring 374 CES action to resolve. Document this

inspection in the Facility Manager continuity binder.

11.38.4.2.8. (Added-Yokota) Brief their squadron commander on hangar door discrepancies,

repair status, and the expected completion date for corrective actions at least once a month.

11.38.4.2.9. (Added-Yokota) Maintain hangar door operating checklists for their respective

hangars and post the checklists at each hangar door control panel (electrically controlled) or on

the most entered door for manually operated doors.

11.38.4.3. (Added-Yokota) Hangar door operators will:

11.38.4.3.1. (Added-Yokota) Operate only those hangar doors for which they are trained and

certified.

11.38.4.3.2. (Added-Yokota) Operate powered electrical doors using the Powered Hangar

Door Operation Procedures Checklist. Hangars with manual doors will be operated using the

Manual Hangar Door Operation Procedures Checklist.

11.38.4.3.3. (Added-Yokota) Ensure the hangar door tracks are free of foreign objects and

debris before operating the doors.

11.38.4.3.4. (Added-Yokota) Immediately notify their squadron supervision and CE customer

service after discovering any hangar door discrepancy.

11.38.4.3.5. (Added-Yokota) Report all hangar door discrepancies to the respective facility

manager immediately.

11.38.4.3.6. (Added-Yokota) Not operate any powered hangar doors in manual mode unless

properly trained and authorized.

11.38.5. (Added-Yokota) Hangar Door Training and Certification.


11.38.5.1. (Added-Yokota) Personnel who routinely work in hangars (but are not required to

operate hangar doors) must receive hangar door awareness training. Hangar door awareness

training is provided by the member’s work center and annual training completion will be

documented on the member’s AF Form 55, Employee Safety and Health Record.

11.38.5.2. (Added-Yokota) Personnel who work in hangars or are required to operate hangar

doors in the performance of routine duties must be trained and certified to perform hangar door

operations. Maintenance personnel required to operate hangar doors will have the G081 course

code for hangar door operation loaded as a work center training requirement (manual door course

code - YOKP 0001; electric door course code - YOKP 0005).

11.38.5.3. (Added-Yokota) Hangar door operation trainers in the 374 MXG will be identified

on a special certification roster (SCR) under G081 course code YOKP 0003. Hangar door

operator trainers in other units will be identified in writing by their respective squadron

commander. The minimum rank for hangar door trainer is SSgt.

11.38.5.4. (Added-Yokota) Hangar door operation training will only be accomplished by SCR-

identified hangar door operator trainers. Squadron Commanders will identify highly proficient

hangar door operators as trainers. A completed AMC Form 64, Request for Special

Certification, will be routed to the unit training manager (UTM) upon completion of training to

document the training appointment. Maintenance group UTMs will update completion of

training for MXG personnel in G081. Contractors who are required to operate hangar doors to

fulfill their contractual duties will receive training from the government after award of the

contract and prior to initiating work in hangar facilities. The Quality Assurance Evaluator

(QAE) or Contract Officer Representative (COR) for the awarded contract is responsible for

arranging this training.

11.38.6. (Added-Yokota) Hangar Door Operation.

11.38.6.1. (Added-Yokota) Only personnel identified in writing (either on separate memo or

via G081 course code) as hangar door operators by their respective commanders may operate

hangar doors. Hangar door operators must be listed on the hangar door operators list. This list

will be posted on the hangar door being operated.

11.38.6.2. (Added-Yokota) Hangar doors must be operated IAW the local checklist posted for

the hangar door being operated. Only the checklist identified for that specific hangar door will

be used to operate that respective hangar door.

11.38.6.3. (Added-Yokota) All overhead hangar doors will be fully opened before aircraft are

moved through the door entrance. Horizontal sliding doors will be completely opened for

maximum clearance at each wingtip. Follow additional applicable guidelines in AFMAN 91-

203.

11.38.6.4. (Added-Yokota) Manual hangar doors will be opened a minimum of 10 feet

between adjacent door panels before equipment, vehicles, or personnel move through the

entrance. Under normal conditions, powered hangar or shelter doors will always be opened to a

width of at least 10 feet. For special operations, such as during extreme weather conditions, the

door may be opened less than 10 feet only if the door control switch is locked off or out and

remains locked out until the door can be opened to 10 feet or more or be closed.


11.38.6.5. (Added-Yokota) If a powered hangar door fails to operate properly, the door

operator will inform the respective squadron’s supervision and the Maintenance Operations

Center (MOC) of the problem and await assistance.

11.38.6.6. (Added-Yokota) Powered hangar doors will be operated manually only by qualified

personnel (CE, Fire Department or contractor) during routine maintenance or in the event of a

facility ground emergency.

11.39. (Added-Yokota) Paperless Isochronal Inspection.

11.39.1. (Added-Yokota) Utilizing Paperless Process. If approved by the 374th MXG/CC and

utilized, the 374th Maintenance Squadron, Maintenance Flight will follow guidelines IAW 00-

20-1. The local Paperless Process is as follows:

11.39.1.1. (Added-Yokota) To activate paperless, The Dock Chief must work with the 374

MXG Quality Assurance and Plans and Scheduling offices to ensure a work package

(G081/IMDS screen 9004/86) has been established for each type of paperless inspection. For

every paperless inspection, the call sign on G081 screen 9018 must be set to “ISO” or “HSC”

before dropping a work package. The work package type must start with an "I" for ISO or an

"H" for HSC and must correlate with the call sign being used.

11.39.1.2. (Added-Yokota) For AFSOC aircraft using CAMS/IMDS, the Dock Chief must

work with the 353 SOG Quality Assurance and Plans and Scheduling offices to ensure a work

package has been established for each type of paperless inspection and that the package is loaded

into CAMS/IMDS.

11.39.1.3. (Added-Yokota) During the paperless process, Panel sheets are authorized. Panel

sheets will be filed with 374 MXG Plans and Scheduling office in the aircraft jacket file when

inspection is complete.

11.39.1.4. (Added-Yokota) For AFSOC aircraft, the panel sheet will be given to the Dedicated

Crew Chief after the Post Dock meeting by the Dock Chief. The Crew Chief will be responsible

for ensuring that it is returned back to home station and put into aircraft jacket file.

11.39.1.5. (Added-Yokota) Procedures for starting/operating in the Paperless Documentation

Process.

11.39.1.6. (Added-Yokota) The Dock Chief/Coordinator will:

11.39.1.6.1. (Added-Yokota) Verify all aircraft forms entries are reflected in G081/IMDS.

11.39.1.6.2. (Added-Yokota) Remove the aircraft forms from the binder and process them for

turn in.

11.39.1.7. (Added-Yokota) Forms removed at the beginning of a paperless process will be

considered permanently inactive. The Dock Chief/Coordinator will not follow normal

transcribing procedures and will not be required to close out the aircraft forms dates or document

the transcribing of each discrepancy. Instead, attach the locally developed cover sheet to the

front of the aircraft forms. The cover sheet will include the following information:

11.39.1.7.1. (Added-Yokota) Aircraft tail number.

11.39.1.7.2. (Added-Yokota) Aircraft forms dates, including from date and date inactivated.

11.39.1.7.3. (Added-Yokota) Reason for removal (i.e. paperless ISO, HSC, etc.).


11.39.1.7.4. (Added-Yokota) Number of pages removed from each type of form (i.e., 781A, 16

pages inactivated).

11.39.1.7.5. (Added-Yokota) The statement “I verify that all open entries have been

entered/validated in G081/IMDS.”

11.39.1.8. (Added-Yokota) Printed name and employee number of Dock Chief/Coordinator,

followed by their signature. The permanently inactive forms will then be filed in the aircraft

jacket file.

11.40. (Added-Yokota) Procedures for extended MIS or power outage.

11.40.1. (Added-Yokota) Each oncoming shift Dock Chief/Coordinator will print a new

8035/380 as applicable. This will be used as a source of reference in the event of a MIS or

power outage. The Dock Chief/Coordinator will ensure all personnel working on the aircraft

review the 8035/380, MXG Forms 1s and open work packages prior to conducting maintenance

on the aircraft.

11.40.2. (Added-Yokota) In the event of extended MIS or power outage, personnel will utilize

the attached 374 MXG Form 1, Aircraft Inspection Discrepancy Sheet, to monitor write-ups

during outage. All discrepancies will be entered into MIS once it becomes available.

11.40.3. (Added-Yokota) The Dock Chief/Coordinator will maintain copies of major work

packages, such as engine changes, Strut changes, etc. to be used in the case of extended MIS or

power outage. These packages will be kept with the 8035/380 as applicable and the MXG Form

1s.

11.41. (Added-Yokota) Procedures for completing the Paperless Documentation Process:

11.41.1. (Added-Yokota) Aircraft post dock will not be completed until paper forms are

restored.

11.41.1.1. (Added-Yokota) Forms restoration procedures:

11.41.1.1.1. (Added-Yokota) Print a G081/IMDS flying forms package and transcribe it into

the Aircraft Forms Binder.

11.41.1.1.2. (Added-Yokota) Validate G081/IMDS and the paper forms match.

11.41.1.1.3. (Added-Yokota) Verify existing warning tags Part As are still installed; attach Part

Bs to the binder ring adjacent to the discrepancy.

11.42. (Added-Yokota) Paperless Warning Tag Documentation. When using the paperless

documentation process, all warning tags will be documented IAW paragraph 5.7.3.16.5.3.

11.42.1. (Added-Yokota) Warning tags (Part A and B) will be shown to the Dock Chief/Dock

Coordinator before hanging tags on aircraft and the warning tag board. Once tags are verified by

the Dock Chief/Dock Coordinator, permission is granted to receive the key to the warning tag

board.

11.42.2. (Added-Yokota) Part A’s will be installed (traditional). All individual Part A’s will

be attached to the system (Circuit Breaker (CB)/Handle/Switch) requiring a tag IAW MDS TOs.

11.42.2.1. (Added-Yokota) The Part A will not be removed until all JCN and WES/WCE

references are completed and no longer affect system operation.


11.42.3. (Added-Yokota) Part B documentation requirements:

11.42.3.1. (Added-Yokota) Part B will be kept under lock and key in the warning tag board

outside of the dock box.

11.42.3.2. (Added-Yokota) Complete all blocks with the same information documented in Part

A.

11.42.3.3. (Added-Yokota) Once warning tag board is opened, hang tags under the

corresponding AFSC with the following information: (1) Name of individual hanging tags. (2)

Employee number of individual (3) Date when tags were hung.

11.42.3.4. (Added-Yokota) Individuals will notify the Dock Chief/Dock coordinator before

removing part B.

11.43. (Added-Yokota) Procedures for operating systems that are deactivated during ISO.

11.43.1. (Added-Yokota) The Dock Chief/Coordinator will verify with each workcenter that it

is safe to operate the systems.

11.43.2. (Added-Yokota) The Dock Chief/Coordinator will do a visual safe for maintenance

inspection and call the MXS Production Superintendent to request approval.

11.43.3. (Added-Yokota) Approval may only be given to the 7-level whom will operate the

system. Approval may come from the Maintenance Operations Officer or Squadron

Superintendent, or delegated down to no lower than a SMSgt whom does not work in

Maintenance Flight.

11.43.4. (Added-Yokota) Once approval has been granted, the Dock Chief/Coordinator will

email the 374 MXG QA org box the following information:

11.43.4.1. (Added-Yokota) Date

11.43.4.2. (Added-Yokota) Shop operating system

11.43.4.3. (Added-Yokota) Discrepancy causing the ops check

11.43.4.4. (Added-Yokota) Approving official rank and name

11.43.4.5. (Added-Yokota) 7-level approved to operate systems

11.43.4.6. (Added-Yokota) Warning tag locations still installed

11.43.5. (Added-Yokota) The Dock Chief/Coordinator will conduct a safety brief prior to

operation of systems and will ensure that the approved 7-level is supervising operations and is

aware of any and all safety concerns.

11.43.6. (Added-Yokota) Once the system has been operated, the Dock Chief/Coordinator will

ensure that the technician returned the system back to proper configuration.

11.43.7. (Added-Yokota) The Dock Chief/Coordinator will then sign the attached local form

and email it to the 374 MXG Quality Assurance email address.

14.7. (Added-Yokota) Chemical Warfare Support for Aircraft Maintenance Contractors. This

instruction provides guidance to the 374th Airlift Wing (374 AW) support organizations for

equipping and training aircraft maintenance contractors with chemical warfare protective

equipment. Aircraft maintenance contractors may be required to support real-world


contingencies and participate in command or unit exercises IAW their respective maintenance

contracts. They must be trained and equipped IAW their respective contracts.


14.7.1.1. (Added-Yokota) 374 AMDS Optometry Flight:

14.7.1.1.1. (Added-Yokota) Perform eye examinations on aircraft maintenance contractors to

establish individual requirements for protective mask spectacle inserts.

14.7.1.1.2. (Added-Yokota) Issue protective mask spectacle inserts to aircraft maintenance

contractors.

14.7.1.2. (Added-Yokota) 374 AMDS Bioenvironmental Engineering Flight. Accomplish

NBC mask quantitative fit training (QNFT) for aircraft maintenance contractors, to include

proper wear of protective mask IAW applicable instructions.

14.7.1.3. (Added-Yokota) 374 LRS War Readiness Section. Issue required chemical warfare

defense equipment (CWDE) to emergency essential aircraft maintenance contractors, to include

A-1, C-1, protective mask and training gear IAW applicable instructions.

14.7.1.4. (Added-Yokota) 374 CES Readiness Flight. Train aircraft maintenance contractors

in the proper use and maintenance of CWDE IAW applicable instructions.

14.7.1.5. (Added-Yokota) 374 MXG Quality Assurance Evaluators:

14.7.1.5.1. (Added-Yokota) Ensure currency and accuracy of contract statement of work

(SOW) requirements.

14.7.1.5.2. (Added-Yokota) Ensure contractors establish processes and procedures to ensure all

required personnel are trained and maintain equipment IAW local guidance and the SOW.

15.2.1.2.1. (Added-Yokota) Annotate all significant histories in G081 automated history event

(AHE) NLT 48 hrs after event takes place.

15.2.3.2.2.1. (Added-Yokota) When an ADR comes due during extended deployment and a

2R1 is not present, a Crew Chief will be designated by AMXS AMU Superintendent to perform

the review. The Crew Chief, Production Superintendent, Deployed Engine Manager, and Supply

will verify the accuracy of the AFTO 781 series forms with G081 and complete the ADR

checklist. The completed ADR package will be returned to the PS&D section upon return for

filing.

15.2.3.2.4. (Added-Yokota) Contract maintenance personnel will perform an ADR IAW their

applicable Statement of Work.

15.2.4.3.4.1.2. (Added-Yokota) A PS&D developed part number and serial number

verification sheet will be completed during all HSC/ISO/letter check inspections. The worksheet

is a tool to verify the serial numbers of installed serially controlled items that are accessible

during the inspection and will include MDS specific AFTO Form 95 items identified by the -6

and any other items deemed high interest.

15.2.5.1.2. (Yokota) If CEMS is down for more than 48 hours, EM will document maintenance

actions on an AF Form 1534, CEMS CDB Report.


15.2.5.1.2.1. (Added-Yokota) The completed inspection work package will include the signed

AF Form 2410, completed part number & serial number verification sheet, G081 9188 (Z

transaction) print out, panel sheets, “locked” 781A and 781K forms, applicable Pre/Post-dock

checklist. Note: GIG & panel sheets are automated in G081.

15.2.5.1.3.1. (Added-Yokota) Out-of-configuration items that cannot be verified or corrected

will follow guidance as outlined in 15.3.2.5.

15.2.6.3.1. (Added-Yokota) When aircraft are deployed off-station 30 days or longer for

exercises or contingency operations and parent-unit maintenance is not provided, PS&D will

print an ADR package from Global Reach for inclusion in the aircraft forms binder. This

package will be prepared not earlier than 48 hours prior to aircraft departure.

15.2.6.3.2. (Added-Yokota) Aircraft jacket files will only accompany aircraft in the following

instances: Program Depot Maintenance (PDM), Unscheduled Depot Level Maintenance,

extended loan (over 30 days), or permanent transfer.

15.2.7.2.1. (Added-Yokota) PS&D will notify all agencies with decentralized records to freeze

the applicable aircraft’s records and prepare them for pick-up by a PS&D member to be included

in the aircraft’s jacket file.

15.2.7.4. (Added-Yokota) In the event of a Class A flight mishap, or when requested by an

impoundment official, involving aircraft assigned to the 374 AW, 374 MXG/MOC will notify

374 MXG/MXOA and request applicable aircraft history stored in the database. 374

MXG/MOC will notify 374 MXG/MXOS who will initiate the local Impoundment/Mishap

Checklist, MXG LCL 8, Impound/Mishap Procedure Checklist. See Chapter 7 for additional

impound management requirements.

15.2.7.4.1. (Added-Yokota) Immediately following notification, the G081/IMDS database

manager will place the system in file update (FUD) mode and save the database. After saving,

all initial products will be run and copies will be forwarded to 374 MXG/MXQ.

15.3.1.2.1. (Added-Yokota) Performing work centers will order, manage and dispose of

HAZMAT items for applicable TCIs and TCTOs utilizing the cradle-to-grave methodology. The

requisition number will be forwarded to PS&D as soon as they become available for follow-up

action during the monthly TCI and TCTO reconciliation meeting.

15.3.3.3.2.3.3.1. (Added-Yokota) Prior to deleting TCTOs from the MIS, ensure the TCTO is

marked “Rescinded” in the applicable TO Catalog/Index, and validate the MIS and REMIS

status codes match.

15.3.3.3.2.4.1. (Added-Yokota) If not resolved in a timely manner, notify HQ PACAF

schedulers for assistance.

15.3.4.1.2. (Added-Yokota) AGE Flight will maintain (load, change, delete) the JML for all

AGE inspections.

15.3.4.2.4.1. (Yokota) Original due dates in the MIS will not be changed to reflect the

extension due date.


15.3.4.3.6.1.1. (Added-Yokota) Performing work centers will order, manage and dispose of

HAZMAT items for applicable TCIs utilizing the cradle-to-grave methodology. The requisition

number will be forwarded to PS&D as soon as they become available for follow-up action during

the monthly TCI reconciliation meeting.

15.3.5.1.4. (Added-Yokota) If approved -107 temporary repairs have an associated DD in the

AFTO 781K for a later permanent repair, maintenance personnel will create JCN if required.

15.3.7.1. (Added-Yokota) Units will develop MDS specific acceptance inspection work-

packages. The acceptance inspection will be assigned a JST and scheduled in the MIS.

15.3.8. (Added-Yokota) Quiet Hours Waivers. Operation of aircraft during 374 AW

established quiet hours requires 374 OG/CC approval IAW YOKOTAABI 13-204, Airfield

Operations. For 374 AW missions, waivers should be requested through 374 OSS/OSO. If

approved, 374 OSS/OSO will notify 374 AW/CP, and 374 OSS/OSAA for coordination.

Aircraft maintenance engine runs during 374 AW established quiet hours require 374 MXG/CC

approval.

15.3.9. (Added-Yokota) Requests for Quiet Hours.

15.3.9.1. (Added-Yokota) Requests to instill Quiet Hours will be submitted to the Airfield

Manager (374 OSS/OSAA). A ten working day advance notice is desirable.

15.3.9.2. (Added-Yokota) 374 OSS/OSAA prepares a request, which includes the following:

15.3.9.2.1. (Added-Yokota) Date and minimum time period.

15.3.9.2.2. (Added-Yokota) Event (reason why Quiet Hours are requested).

15.3.9.2.3. (Added-Yokota) Specific location: parking spot, ramp area, or building number.

15.3.9.2.4. (Added-Yokota) Extent of “quiet” options may include:

15.3.9.2.4.1. (Added-Yokota) No activity throughout airfield.

15.3.9.2.4.2. (Added-Yokota) No departures/arrivals.

15.3.9.2.4.3. (Added-Yokota) No engine runs.

15.3.9.2.4.4. (Added-Yokota) No transition.

15.3.9.2.4.5. (Added-Yokota) No Aerospace Ground Equipment (AGE) equipment.

15.3.9.2.4.6. (Added-Yokota) No Auxiliary Power Unit (APUs).

15.3.9.2.4.7. (Added-Yokota) No vehicle traffic.

15.3.9.2.4.8. (Added-Yokota) No contractor activity.

15.3.9.2.4.9. (Added-Yokota) Ramp Freeze – No movement on parking apron or taxiway

(includes vehicle, aircraft, and personnel).

15.3.9.3. (Added-Yokota) 374 OSS/OSAA forwards request to 374 OSS/DO for 374 OG/CC

approval/disapproval. If approved, 374 OSS/DO returns approved request to 374 OSS/OSAA

with final Quiet Hours time and restrictions. 374 OSS/OSAA sends an advisory message to base

agencies (including 374 AW/CP) and issues a NOTAM.


15.3.9.4. (Added-Yokota) 374 MXG/MXOS will include all known and approved Quiet Hour

dates, times and restrictions on the monthly flying and maintenance schedule.

15.3.10. (Added-Yokota) Mission Essential Personnel Letters. MEP letters will be signed

IAW AFI 11-401, Aviation Management, and will be provided to the Operations Squadron

schedulers prior to mission execution. Units with personnel requiring an MEP are responsible

for routing the letter through 374 OG/OGV to the 374 OG/CC for signature. 374 OG/OGV

should provide a template for accomplishing this letter.

15.4.1. (Yokota) EM managers will track & monitor special inspections loaded against all

engines.

15.4.1.2.3.1. (Added-Yokota) Engine maintenance actions will be verified and validated by

EM personnel within two duty days of notification or MIS documentation for home-station, off-

station and deployed assets. All post maintenance part number and serial number verification

sheets will be digitally sent to EM within 24 hours.

15.4.1.2.20.2. (Added-Yokota) CEMS/MIS Downtime and Contingency Plan Procedures for

both Home Station and Deployed Engine Manager (EM).

15.4.1.2.20.2.1. (Added-Yokota) If both CEMS/MIS are down for more than 48 hours, the

following procedures will be executed:

15.4.1.2.20.2.1.1. (Added-Yokota) Propulsion Maintainers will utilize the AFTO Form 349,

Maintenance Data Collection Record, to document all maintenance action in MIS and provide

copies to EM.

15.4.1.2.20.2.1.2. (Added-Yokota) EM will use AF Form 1534, CEMS Central Database

Report to facilitate CEMS reporting.

15.4.1.2.20.2.1.3. (Added-Yokota) EM will retain the AFTO Form 349 and AF Form 1534

until CEMS/MIS database resumes operations.

15.4.1.2.21.3. (Added-Yokota) Local Procedures for Deployed Engine Monitor (DEM): The

purpose of this section is to maintain control of deployed engine assets, time change items and

AFTO Form 95 tracked components, and to ensure prompt documentation and reporting in the

MIS and CEMS database. Deployed engine technicians are responsible for communicating all

status changes to the 374 MXG EM. The following procedures for deployed/off-station aircraft

will be strictly adhered to:

15.4.1.2.21.3.1. (Added-Yokota) 374 AMXS maintenance supervision will appoint a DEM at

least three duty days before departure for deployments and off station operations where no

centralized engine management personnel are assigned. The appointed DEM will report to 374

MXG EM Section for a briefing and training/continuity package at least one duty day before

departure.

15.4.1.2.21.3.2. (Added-Yokota) The DEM will:

15.4.1.2.21.3.2.1. (Added-Yokota) Report pending or completed engine and/or component

changes to the 374 MXG EM.

15.4.1.2.21.3.2.2. (Added-Yokota) Ensure the applicable change sheet is filled out accurately

and completely immediately following engine or component change.


15.4.1.2.21.3.2.2.1. (Added-Yokota) Change sheets are located on 374/MXG/MXOM

SharePoint Site.

15.4.1.2.21.3.2.3. (Added-Yokota) Ensure appropriate MIS entries are accomplished

immediately following engine and/or component change. If MIS is not available at deployment

site/off-station location, provide appropriate data to home station ASAP for input into MIS.

15.4.1.2.21.3.2.4. (Added-Yokota) Fax or e-mail change sheets to [email protected],

Telephone DSN 315-225-8792/8346.

15.4.2. (Added-Yokota) Engine Shipments:

15.4.2.1. (Added-Yokota) Outbound Engines:

15.4.2.1.1. (Added-Yokota) Engines will be shipped with a required delivery

date/transportation priority of“999” IAW AFI 24-203, Preparation and Movement of Air Force

Cargo, paragraph 2.16.1. Cargo movement personnel will ensure to receipt and process the

engine immediately. The Base Engine Manager and/or Engine Schedulers will ensure units

shipping engines are informed that they must properly pack, wrap, drain and purge each engine

for shipment IAW T.O. 00-85-20. Units will be informed to deliver the engine to Outbound

Cargo Section, building 4145, for processing. If commercial vehicles are required to move

aircraft engines, 374 LRS/LGRDDC will ensure the engine is moved on both air ride tractor and

trailer IAW T.O. 00-85-20.

15.4.2.1.2. (Added-Yokota) The Base Engine Manager and/or Engine Schedulers will inform

units of proper shipping documents.DD Form 1348-1A, Issue Release/Receipt Document, and/or

DD Form 1149, Requisition and Invoice/Shipping Document, will be signed only by authorized

individuals appointed by 374 MXG/CC. 374 LRS/LGRDDC will accept either form, DD Form

1348-1A or DD Form 149, to process engines shipments. In addition, units will provide 2 copies

of Caution Tags, AFTO Form 20, Caution and Inspection Record, filled out and signed

certifying that engines have been properly drain and purged.

15.4.2.1.3. (Added-Yokota) EM will provide the engine serial number and TCN to HQ

PACAF/A4MYE for all shipments within 24 hours after the engine has been shipped and will

identify all engine shipments with Special Project Code 449 (nickname “Corral Shannon”) on a

DD Form 1149.

15.4.2.2. (Added-Yokota) Inbound Engines:

15.4.2.2.1. (Added-Yokota) Receiving Elements will in-check/receipt for engines IAW

applicable directives. To limit the safety risk, engines will be downloaded at 730 AMC terminal

by qualified personnel and handed directly over to the Engine Management Section. The Engine

Management Section will forward all documentation to the Receiving Element.

15.4.2.3. (Added-Yokota) EM will maintain/upload shipping documents to CEMS IAW Air

Force Financial Improvement and Audit Readiness (FIAR) instructions as outlined in technical

order 00-25-254-1.

15.4.2.4. (Added-Yokota) The following are commonly used shipping addresses:

mailto:[email protected]


Table 15.2. (Added-Yokota) Shipping Addresses.

Kadena AB Engine Mgt Dowty Props C130J ENGINE (AE2100D3)

SRAN FJ 4441

353 SOMXS/MXMOOP

KADENA AB, JAPAN

APO AP 96368-5246

SRAN EJ 4426

ROLLS ROYCE CORP

CO DOWTY PROPS, CP 703-

421-9321

114 POWERS CT

STERLING VA 20166-9321

SRAN EJ 4028

ROLLS ROYCE CORP

CP: 317-230-4028

450 S. MERIDIAN ST.

INDIANAPOLIS IN 46225

15.5.4.5.1.1. (Added-Yokota) The quarterly scheduling meeting may be held in conjunction

with the monthly scheduling meeting.

15.5.5.5.1.1. (Added-Yokota) Monthly schedules will be published NLT 5 duty days prior to

beginning of the effective month.

15.5.6. (Yokota) Weekly Scheduling. The weekly scheduling meeting takes place every

Tuesday and is chaired by the 374 OG/CD and 374 MXG/CD. At a minimum, the agencies in

attendance will be: 374 OSS/OSO, 36 Airlift Squadron (AS), 459 AS (as needed), 374 Aircraft

Maintenance Squadron (AMXS)/Maintenance Aircraft (MOO or Supt, and Production

Superintendent), 374 Maintenance Squadron (MXS)/MXM (MOO or Supt, and Production

Superintendent), and 374 MXG/MXOS. Following the meeting, the 374 OSS/OSO will compile

the Air Movement Table (AMT) and submit to the 374 MXG/MXOS for final coordination.

15.5.6.1.1.1. (Added-Yokota) Discrepancies will be briefed in the Thursday PM Production

Meeting.

15.5.6.2.13. (Added-Yokota) Unique mission requirements including, but not limited to: tire

wear limits, increased Liquid Oxygen (LOX) requirements, secure voice, chaff & flare,

Frequency Modulation (FM) immunity, extra oxygen bottles, aircrew signs & plaques, special air

show requirements, unimproved runway preparation, diplomatic (DIP) clearance, Flying Crew

Chief (FCC) requirements, Mode IV/IFF checks, unimproved LZ, assault fuel, pet rock, armor.

15.5.6.2.14. (Added-Yokota) Known Quiet Hour dates, times and operation restrictions.

15.5.6.3.1.2. (Added-Yokota) If Daily Scheduling is utilized, aircraft tail numbers will only be

reflected on the daily schedule. Daily tail number assignments will be finalized NLT the

afternoon daily maintenance production meeting the day prior to execution. The finalized tail

numbers will be recorded on an AF Form 2407 for audit and analysis purposes and are non-

chargeable. PS&D will enter the tail number changes in G081 utilizing screen 9074 immediately

following the meeting. The AF Form 2407 will be forwarded to the MOC by 1600 the day prior

to execution.

15.5.6.3.1.3. (Added-Yokota) All weekly scheduling requirements for the following week’s

schedule need to be finalized and sent to PS&D for compilation NLT 1200L each Thursday.

Any changes arising after 1200L on Thursday require an AF Form 2407.

15.5.6.3.9. (Yokota) AF Form 2407 Approval Authority. All other AF Form 2407 changes will

be approved by the AMXS MOO or Superintendent and 36 AS Director of Operations or

Operations Superintendent.


15.5.6.3.9.1. (Yokota) TWCF Missions. Current Operations (374 OSS/OSO) will initiate all AF

Form 2407 changes for AMD-directed schedule changes (prior to crew show).

15.5.6.3.9.1.1. (Added-Yokota) In the MXG/CC’s absence, or upon verbal approval, the

MXG/CD or MXG/CCC may approve AF Form 2407s requiring MXG/CC approval.

15.5.6.3.9.1.2. (Added-Yokota) Daily Scheduling. Daily scheduling allows maintenance to

change tail numbers only. No sorties can be added or subtracted from the original proposed

weekly schedule. AMXS is permitted to substitute aircraft on the next day’s printed daily flying

schedule with aircraft that are not on the printed schedule. All other flying schedule deviations

are recorded against the original printed weekly flying and maintenance schedule. AMXS will

make every effort to change tail numbers at the daily maintenance production meeting the day

prior to the aircraft’s scheduled flight. All tail number changes will be finalized NLT the

afternoon daily maintenance production meeting and will be recorded on an AF Form 2407 for

audit and analysis purposes and are non-chargeable. PS&D will enter the tail number changes in

G081 utilizing screen 9074 immediately following the meeting. The AF Form 2407 will be

forwarded to the MOC by 1600 the day prior to execution.

15.5.6.7.2.1. (Added-Yokota) Once the printed schedule is signed by the WG/GP CC’s all

changes other than those allowed under daily scheduling rules (paragraph 15.5.6.3.9.1.1) will

incur flying scheduling deviations.

15.5.6.8.1.1. (Added-Yokota) PS&D will publish the signed Weekly Flying and Maintenance

Schedule on the MXOS SharePoint site.

15.5.6.9.2.1. (Added-Yokota) 374 MXG/MXOS will calculate maintenance scheduling

effectiveness from the weighted factors outlined in AFI 21-101_PACAFSUP, Table 15.1. All

maintenance actions from the previous day will be verified in G081 NLT 0800 the next morning

after the event was scheduled using screen 9050. Credit will only be awarded for maintenance

events that were completed on or prior to the items scheduled date that is printed in the signed

weekly schedule.

15.5.6.10. (Added-Yokota) Combat/Exercise Sortie Generation.

15.5.6.10.1. (Added-Yokota) In the event a combat/exercise sortie generation is initiated, an

AF Form 2407 will be initiated by Current Operations (374 OSS/OSO) to cancel the remaining

printed weekly flying schedule.

15.5.6.10.2. (Added-Yokota) Combat/exercise sortie generation will include operations using

an Air Tasking Oder (ATO). Operations and Maintenance will meet daily to discuss ATO

scheduling during sortie generation and flying execution. A daily schedule will be finalized on

an AF Form 2407 and confirmed with operations and the MOC NLT 2 hours prior to the first

take-off time. Once the daily schedule has been finalized, normal AF Form 2407 rules apply

with exceptions outlined in paragraph 15.5.6.3.9.

15.5.6.10.2.1. (Added-Yokota) The daily schedule derived from an ATO is applicable to

affected organizations and can contain mission numbers, tail numbers for the first lines and

spares, and configurations.

15.5.6.10.3. (Added-Yokota) Unlike a planned sortie surge, early and late-takeoffs are

recorded on second and subsequent sorties, unless a change due to operational requirements is

made to the ATO. Normal deviations will be recorded against all sorties using the new


published schedule derived from the ATO. Note: All sorties launched under a “Classified

ATO” will be considered flown as scheduled. Classified ATO lines that are missed will be

recorded as cancels in the MIS. Cancellations will be loaded into in the MIS once the sortie is

declared cancelled regardless of actual scheduled take-off time and ground aborts will be

recorded.

OTIS C. JONES, Colonel, USAF

Commander


Attachment 1

GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION

Prescribed Forms

374 AW Form 70, Dropped Object Investigation Worksheet

374 AW Form 71, Cost Estimate Worksheet

374 AW Form 72, Foreign Object Damage (FOD) Incident Investigation

YOKOTA AB Form 36, Local Manufacture Request

Adopted Forms

AF Form 601, Equipment Action Request

AF Form 614, Charge out Record

AF Form 1199, Air Force Entry Control Card

AF Form 1534, CEMS CDB Report

AF Form 2005, Issue/Turn-In Request

AF Form 3131, General Purpose Form

AFTO Form 20, Caution and Inspection Record

AFTO Form 245, Industrial Support Equipment Record

AMC Form 64, Request for Special Certification

DD Form 149, Application for Correction of Military Record Under the Provisions of Title 10,

U.S. Code, Section 1552

DD Form 365-3, W&B Record Chart C Basic

DD Form 1149, Requisition and Invoice/Shipping Document

Terms

Consumable Items (in a CTK) (Added) (Yokota)—Consumables must be limited to the

minimum necessary to support maintenance requirements. Criteria for placing consumables

inside a CTK are based on the impact of not having items immediately available versus the time

required to obtain them from bench stock. Examples of consumable items include safety wire

and electrical insulators. Consumable items placed in a CTK are treated as tools and must be

marked with the worldwide identifier (WWID).

Dispatchable CTK (Added) (Yokota)—CTK designed and/or issued out for use on aircraft or

SE. This includes all components and equipment that are designated individually in GO81/MIS

(i.e., aircraft, AGE, engines) but not parts or pieces of those assets (panels, doors, wheels, etc).

CTKs used on these assets, even when the asset is located inside the work center (i.e.,

AGE/ERRC maintenance floors, Metals Technology welding area), are considered dispatchable.

Deployable CTKs (Added) (Yokota)—Dispatchable CTKs with specific markings and

inventory requirements; used to support off-station missions.


Expendable Items (in a CTK) (Added) (Yokota)—Those items that may be rendered unusable

during use. Examples of expendable items include: apexes, allen wrenches and saw blades.

Tool Crib (Added) (Yokota)—A central location possessing facilities to store and maintain

CTKs, equipment and consumable items; also referred to as “Tool Room.” The tool crib/room

may be co-located with the bench stock section.

afi21-101_pacafsup_yokotaabsup.pdf - Air Force

Documents

Transcript of afi21-101_pacafsup_yokotaabsup.pdf - Air Force