by order of the commander air force instruction 21- … · an/aaq-24a (v), an/aaq-24(v) 13,...

BY ORDER OF THE COMMANDER

CANNON AIR FORCE BASE (AFSOC)

AIR FORCE INSTRUCTION 21-

101_AFSOCSUP

CANNON AIR FORCE BASE

Supplement

15 JANUARY 2019

Maintenance

AIRCRAFT AND EQUIPMENT

MAINTENANCE MANAGEMENT

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

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

www.e-Publishing.af.mil for downloading or ordering.

RELEASABILITY: There are no releasability restrictions on this publication.

OPR: 27 SOMXG

Certified by: 27 SOMXG/CC

(Col Stephen C. Grotjohn)

Pages: 26

This supplement implements AFI21-101_AFSOCSUP, Aircraft and Equipment Maintenance

Management. This supplement is applicable to all 27th Special Operations Wing personnel and

those working on 27th Special Operations Maintenance Group assigned aircraft. Ensure that all

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

accordance with Air Force Manual (AFMAN) 33-363, and disposed of in accordance with Air

Force Records Information Management System (AFRIMS) Records Disposition Schedule

(RDS). Refer recommended changes and questions about this publication to the Office of

Primary Responsibility (OPR) using Air Force Form 847, Recommendation for Change of

Publication; route AF Form 847s from the field through the appropriate functional chain of

command.

1.3.3.1. (Added) The Section responsible for the maintenance being performed will submit all

required information on a QA Form 18A (C-130), QA Form 18B (CV-22), or database generated

through the Production Superintendent/equivalent and Squadron Maintenance Supervision prior

to submittal in AIRCAT and/or VTAMP. Outside of normal duty hours, Squadron Maintenance

Supervision may delegate their approval authority to night shift Production Superintendents. If

unit does not have access to AIRCAT, VTAMP and/or LMS send form to QA for submittal.

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

2 AFI21-101_AFSOCSUP_CANNONAFBSUP 15 JANUARY 2019

1.3.3.1.1. (Added) QA Forms 18A and 18B can be found on SharePoint in the 27 SOMXG/QA/

Local Forms section and must be sent to QA for tracking.

1.6.3. (Added) Inside any hangar bay where aircraft are present is considered flightline.

1.8.1. (Added) HAZMAT Inspection Checklist (27 SOMXG Form 8) will be used to document

inspections and filed in the program binder for a minimum of one year from inspection date.

1.13.3. (Added) Hearing Protection.

1.13.3.1. (Added) All sections must maintain a current BEF workplace evaluation to identify

workers potentially exposed to harmful noise levels.

1.13.3.2. (Added) All personnel with Hazardous Noise Exposure will comply with all

hazardous noise control measures to reduce exposure as advised by Bio-Environmental

Engineering and IAW 6055.12.

1.13.3.3. (Added) All personnel working in or entering designated “hazardous noise areas” will

always carry hearing protectors with them IAW DoDI 6055.12 and work center JSTO. This

includes visitors, temporary or transient personnel, aircrew, and ground based controllers

entering hazardous noise areas.

1.13.3.3.1. (Added) When operating two or more pieces of powered AGE (within 25 feet of

each other at the same time) the use of double hearing protection will be worn.

1.13.3.4. (Added) All personnel working around engine operations are required to follow BES

specific hearing protection or MDS specific technical data, whichever is more stringent will be

followed (single hearing protection 300-1500 ft./double hearing protection < 300 ft.).

1.13.4. (Added) Emergency Equipment Inspection Documentation.

1.13.4.1. (Added) Fire extinguishers, eyewash stations, emergency showers, and portable

defibrillators will be inspected and documented no later than the 10th day of each month.

1.13.4.2. (Added) Inspections will be documented on the AF 2411 Inspection Document or

contractor provided tag. (All fire extinguishers exposed to weather will have an “all weather”

type inspection tag or a sealable document protector for the tag).

1.13.5. (Added) Vehicle Fire Extinguishers.

1.13.5.1. (Added) All assigned 27 SOMXG special purpose vehicles operating on the flight line

will have a fire extinguisher with an approved vehicle modification letter from 27

SOLRS/LGRV, if not installed by the manufacturer. All 27 SOMXG units will submit vehicle

modification request in writing to 27 SOLRS/LGRV for vehicle modification. All 27 SOMXG

units with assigned vehicles will keep on file all approved and disapproved vehicle modification

letters.

1.13.6. (Added) Warning Tag Documentation.

1.13.6.1. (Added) Document the tag number in the tag number blocks on both upper and lower

sections as follows:

1.13.6.1.1. (Added) JCN and a three-digit sequential number, beginning with 001, to show how

many tags are installed for the related maintenance task (i.e., 030015555001, 030015555002

AFI21-101_AFSOCSUP_CANNONAFBSUP 15 JANUARY 2019 3

etc.). Annotate condition on both portions of the tag in the “Condition” block in red. Example:

NOTE:“DO NOT APPLY POWER/RESET CB/OPEN DOOR etc.”

1.13.6.1.2. (Added) Affix the top portion of the tag(s) at the point of control (i.e., circuit

breaker, control lever, on/off switch) to prevent inadvertent operation. Tag(s) will be securely

attached by a string material so they cannot be accidentally detached. The lower portion of the

tag will be affixed to the forms/binder on the page and block coinciding with the write-up of the

warning tags.

1.13.6.1.3. (Added) On RPA, if any switch, circuit breaker or electrical component is removed

that would prevent safe application of external power, attach a warning tag on the external

electrical power receptacle of the aircraft, Ground Control Station (GCS), or Ground Data

Terminal (GDT).

1.13.6.2. (Added) Electronic Circuit Breaks (ECBs).

1.13.6.2.1. (Added) Procedures such as strapping and unstrapping ECBs are the electronic

equivalent of attaching and removing warning tags. Furthermore, if power is not applied to the

aircraft, it is acceptable to remove a component without opening and strapping the applicable

ECB. In these cases, the mechanical circuit breaker controlling the ECB load must be opened

and tagged. Refer to T.O. 1C-130(AHM)J-2-24GS-00-1, Table 5-1 for ECB mechanical circuit

breaker cross reference.”

1.13.6.2.2. (Added) Document ECBs as follows:

1.13.6.2.2.1. (Added) If documenting ECB(s) in the original “DISCREPANCY” block, enter

the ECB number(s) pulled and strapped with an applicable NOTE. For example: NOTE: “Three

each ECBs (plus location) are pulled and strapped. NOTE: DO NOT OPERATE LANDING

GEAR.”

1.13.6.2.2.2. (Added) If documenting ECB(s) as a separate discrepancy, enter the appropriate

symbol and ECB number(s) that are pulled and strapped with location and applicable NOTE.

1.14.7. (Added) Duty Shifts and Rest Periods.

3.3.2. (Added) RPA units will include a GCS maintenance section.

3.7.11.1. (Added) During IMDS down periods or when IMDS is unavailable, units will use

AFSOC Form 25, Manual Debrief Form. Units will provide a copy of the completed AFSOC

Form 25 to Wing Analysis NLT the next duty day after flying. Whenever IMDS is not available

at a deployed site, debrief will complete an AFSOC Form 25 for each sortie and give it to the

deployed analyst or fax the form back to home station analysis. The deployed scheduler will

provide analysis with the completed schedule NLT one hour prior to the first sortie of the day.

3.7.11.2. (Added) Preprinted manual aircraft forms will only be used when IMDS capability

does not exist (i.e., IMDS is down or at forward deployed locations). To ensure AFTO Form

781 series are standardized, each new master form created by a maintenance function will match

the appropriate JST and must be approved by OIC or Maintenance Supervision and forwarded to

QA for final approval and stamp. Preprints with corrective actions will not be used. If an

approved JST exists for a maintenance task (i.e., Preflight, Engine Removal/Install), the

appropriate JST will be used.


3.7.13. (Added) Ensure AFTO Form 781 series are standardized. Each new master form

created by a maintenance function will match the appropriate JST (if applicable) and must be

approved by OIC or Maintenance Supervision and forwarded to QA for final approval. Preprints

with corrective actions will not be used. If an approved JST exists for a maintenance task (i.e.,

Preflight, Engine Removal/Install), then that JST must be used.

3.7.13.1. (Added) Debrief sections will use the 27 SOAMXS and 727 SOAMXS Debriefing

Procedures Guide Book in conjunction with the fault-reporting manual. Debriefing guidebooks

will be developed by the debrief subsystem manager (AMU Lead Debriefer), coordinated

through 27 SOMXG Analysis Section and approved by QA. The format will be standardized as

much as possible across all AMUs.

3.8.1.1.1. (Added) Aircraft servicing will be annotated as an Info Note in the 781A’s. Truck,

equipment or fuel cart identification numbers will be documented.

3.9.3.4. (Added) Electronic Warfare System checks for the AN/ALR-69, AN/AAR-44A,

AN/AAQ-24A (V), AN/AAQ-24(V) 13, AN/ALE-47, ALR-56 and AAR-47 systems’ 90 day

scheduled inspections and generation/pre-deployment checks will be valid for 30 calendar days

after completion. These checks will not require re-accomplishment during this period.

3.13. (Added) GCS/CDCS Maintenance Section. The GCS (Ground Control Station)/CDCS

(Containerized Dual Control Segment) Maintenance Section is the primary work center

responsible for maintaining assigned GCS/CDCS systems. This section performs tasks to include

servicing, scheduled and unscheduled maintenance, pre-flights, thru-flights, basic post-flights,

home station checks, special inspections, corrosion control, cleaning, ground handling,

launch/recovery of aircraft, troubleshooting and adjustment, on-equipment repairs and

component removal/replacement, documenting maintenance actions, and managing aircraft

forms. AMUs with 18 or more GCS/CDCS systems may have two GCS Maintenance Sections.

The GCS Maintenance Section consists of GCS Maintenance Technicians.

3.13.1. (Added) GCS/CDCS Maintenance Expediter will perform duties IAW para 3.6 of this

publication.

3.13.1.1. (Added) Coordinate with the Flight line Expediter/Pro Super regarding aircraft link

support for maintenance actions in the event that no support equipment (e.g. RAMTS, Single

Bays Stations, DALE) are available for use or there is a requirement to expedite maintenance

procedures.

3.13.2. (Added) GCS/CDCS Maintenance Technicians will perform duties IAW para 3.8.1 of

this publication.

3.13.3. (Added) Dedicated Crew Chief (DCC) Program will perform duties IAW para 3.8.2 of

this publication.

3.13.4. (Added) GCS/CDCS Maintenance.

3.13.4.1. (Added) The industrial area for building 2379 (aka “the south pad”) will be defined as

room 101. Also, from the end of the pad to the edge of room 101, not to exceed the width of

building 237. The rest of the pad, will be deemed as storage for GCS maintenance personnel.

3.13.4.2. (Added) FOD inspections will be defined as inside the marked areas of the

maintenance bay and inside the GCS/CDCS shelters.


3.13.4.3. (Added) Open ports connecting to peripherals (e.g. Headset ports, Ethernet ports,

USB ports) on the GCS/CDCS will not be required to be capped/covered. Caps supplied by

original manufacturer that come pre-attached/lanyard to equipment will be used when port is

going to be left open.

4.4.4.1.1.4. (Added) Fuels. See 27 SOMXG OI 21-102 for Fuel System maintenance.

4.5.1.2.1. (Added) Inspect assigned AGE and perform 24-month Special Corrosion Control

Inspection IAW TO 35-1-3.

4.5.1.2.2. (Added) AGE does not dispatch operator driven equipment (e.g., bomb lifts).

4.5.1.5.1. (Added) P&S will provide job master listing, off equipment JST's, and training.

4.5.1.7. (Added) Ensures equipment maintained by the AGE flight is placed on the AGE

Flight/work center equipment account.

4.5.2.13.1. (Added) Users may dispatch non-powered AGE (NPA). When moving NPA from

location to location, the user will notify AGE driver of the movement. Users will not place NPA

back on the ready line after use.

5.2.5.1.9.1. (Added) Individuals requesting background reports will go through the appropriate

subsystem manager via email.

5.2.5.3.5.2.1. (Added) Both primary and alternate monitors will be appointed by the squadron’s

maintenance supervision using the DIT appointment letter.

5.2.5.5.1.1. (Added) Maintenance supervision must contact the Database Management (DBM)

section in writing prior to scheduled deployments/TDYs where access to the Cannon IMDS

system will be required.

5.2.5.5.2. (Added) When IMDS comes back on line, the flying schedule must be input first, any

tail number swaps or spares entered by the MOC, debrief will enter all sortie information and

create the event IDs. These procedures must be followed to ensure the data is correctly linked

together. If the job is not tied to a pilot reported discrepancy, it can be input immediately.

5.2.5.5.3. (Added) Manual job control numbers will consist of nine digits. The first two digits

are the last two digits of the calendar year. The next three digits are the applicable Julian date.

The last four digits are assigned from the appropriate block number as designated in the

authorized job control list. Manual job control numbers will not be used except during red-ball

maintenance unless IMDS unavailable. A current list of authorized manual job control numbers

can be found on Analysis SharePoint.

6.2.10. (Added) Manage the QA Flash Program.

6.2.10.1. (Added) The QA Flash Program is established to provide commanders with a means

to quickly communicate relevant maintenance information and guidance directly to 27 SOMXG

personnel. The information provided will cover topics relating to maintenance practices,

procedures and concerns not specifically addressed in other publications such as TOs,

regulations, instructions, etc. Additionally, recurring maintenance problems and items of high

interest will also be addressed. It will also be used to inform maintainers of changes to

procedures in rewrite and due to the time lag in the publishing process the 27 SOMXG/CC feels

the technician needs to know immediately. QA Flashes will not be created to set policy.


6.2.10.2. (Added) Members will read all QA Flashes applicable to the unit and initial the 27

SOMXG Form 3 within 10 days of publication or in-processing to the unit.

6.2.10.3. (Added) Applicable QA Flashes will be posted in the unit where it is readily available

and posted in high traffic areas for a minimum of 30 days from the published date.

6.2.10.4. (Added) Section supervisors will maintain a 27 SOMXG Form 3, listing each

technician assigned to the work center. All new personnel will be added to the 27 SOMXG

Form 3 within 30 days of work center assignment. All blocks in the form header (self-

explanatory) will be utilized and completed. All applicable QA Flash numbers will be listed on

the form and initialed by the technician to indicate he/she has read the QA Flash. When a QA

Flash has been rescinded, the flash number and member initials will be lined through and the

rescinded QA Flash removed from the binder.

6.2.10.5. (Added) Each section, if applicable, will set up a binder to manage the program. QA

will maintain a master binder for reference. Each binder will contain the following: QA Flash

Book Table of Contents, QA Flash Book Program Appointment Letter, 27 SOMXGOI 21-101

QA Flash Program references in Chapter 6, QA Flash index, copy of each applicable QA Flash

posted in date order (most recent on top), Personnel unable to sign tracker, and a 27 SOMXG

Form 3, which includes each individual assigned to the section.

6.2.10.5.1. (Added) As a minimum, the work center will ensure their binder is updated with a

new index, applicable QA Flashes, and members initials on the applicable 27 SOMXG Form 3

entries NLT than 10 duty days after publishing.

6.2.10.6. (Added) QA Flashes and 27 SOMXG Form 3’s can be found on SharePoint in the 27

SOMXG QA Flashes section.

6.6.10. (Added) QA Inspectors will create accounts in AIRCAT/VTAMP/LMS and verify

status of open 107s on a daily basis at the beginning and end of each shift.

6.7.2.7.2.2.1. (Added) Designated QA Augmentees may perform all KTL’s except PRGB,

MWGB, TAGB, and Phase when aircraft is off station and qualified QA personnel are not

available. Augmentee will update home station QA as soon as possible with all required

information for input into LEAP. (CV-22).

6.7.2.7.4. (Added) Required KTLs will be performed prior to any re-paneling of inspection

area. (ALL MDS).

6.7.2.7.5. (Added) KTLs will be documented as a Red Dash in the AFTO Forms 781A. (ALL

MDS).

6.7.2.8.1.1. (Added) QA Chief Inspector will review unit contracts (RILs) on a quarterly basis

for changes and send to QA Supervision for MXG approval.

6.7.2.8.1.2. (Added) Unit contracts (RIL) can be found in the 27 SOMXG MSEP Handbook

RIL section.

6.11.5.7. (Added) A LEP (commonly called “A” page) will be accomplished annually on all

TOs. This requirement is in addition to “Change/Revision” LEPs that are accomplished through

the life of a TO.

6.11.5.8. (Added) The “Received and Posted” date will be annotated on the “Title Page” of all

TOs and Supplements to ensure it is being posted within five duty days.


6.11.7.3. (Added) Ratings for discrepancies found during TO inspections (i.e.,

Management/Spot) will be covered in the 27 SOMXG MSEP Handbook folder located on

SharePoint.

6.11.10. (Added) TODAs at all levels will establish and manage their TO accounts IAW TO

00-5-1, AFSOC SUP 00-5-1, AFI 21-101_AFSOC SUP, AFI 63-101 and local guidance given in

this instruction.

6.11.11. (Added) All TODAs within the 27 SOMXG will add the Lead TODO as a contact in

ETIMS for their account/sub-accounts for purposes of account monitoring.

6.11.12. (Added) TO management inspections will be accomplished annually on TODA

accounts within the 27 SOMXG by the Lead TODO. TO 00-5-1, Table 4.1 will be used to

conduct the inspection.

6.11.13. (Added) Mandatory/Optional Paper Technical Data Usage.

6.11.13.1. (Added) Enforce adherence to IMIS and ETIMS technical data usage. IMIS and

ETIMS are the preferred technical data source for all Technical Orders except for those TOs

listed in Table 6-11. The TOs listed in Table 6-11 require use of paper technical data or have

optional use of paper technical data for the tasks identified.

Table 6.1. (Added) Mandatory/Optional Paper Technical Data Usage.

Tasks requiring mandatory paper TO use Technical Order

GTC/APU Operation 1C-130E-2-49JG-00-1-1

1C-130(H/M)J-2-49JG-00-1

Engine Runs 1C-130H-2-71JG-00-1

1C-130(H/M)J-2-71JG-00-1

Nonnuclear munitions loading procedures (C-130) 1C-130(…) -33-1-2 (All applicable

checklist)

Nonnuclear munitions loading procedures (CV-22) 1V-22(…) – 33-1-2 (All applicable

checklist)

Nonnuclear munitions loading procedures (MQ-9) 1Q-9(…)-33-2-1 (All applicable checklist)

Tasks requiring paper or electronic TO use Technical Order

Towing 1C-130H-2-09JG-10-1

1C-130(H/M)J-2-09JG-10-1

Fuel Servicing 1C-130H-2-12JG-10-1

LOX Servicing 1C-130H-2-12JG-10-2

6.13.2.1.2. (Added) Ensure a current FCF checklist is properly annotated and all required

checks are identified. NOTE: Use the same checklist until the FCF is completed or the aircraft

commander requests a new checklist. Keep all checklists together and turn them in to the PS&D

section upon the aircraft’s release from FCF.

6.13.2.1.3. (Added) Ensure all requirements of the FCF/OCF have been satisfactorily

completed. Ensure the aircraft forms and the FCF checklist is correctly documented. The

aircraft commander will sign, date and enter the time the FCF/OCF was completed in the AFTO

Form 781A FCF/OCF discrepancy block and on the FCF checklist.


6.13.2.7. (Added) Advise 27 SOMXG/CC, maintenance squadron commander, and flying

squadrons FCF program OICs of any changes affecting FCF program.

6.13.3.4.1. (Added) Accomplish a complete review of all aircraft forms and IMDS entries

associated with the maintenance action creating the FCF/OCF. Ensure currency, accuracy and

adequacy of maintenance actions and documentation of all maintenance performed. Enter an

“Informational Note” in the AFTO Form 781A to state the date and page numbers reviewed.

Retain all transcribed forms pertaining to the FCF until the aircraft is released from FCF.

6.13.4.4. (Added) Unit Production Superintendent will:

6.13.4.4.1. (Added) Ensure all maintenance actions pertaining to the FCF/OCF reflect in forms

and IMDS before calling for a FCF/OCF QA forms review.

6.13.4.4.1.1. (Added) Ensure all transcribed and active forms pertaining to current FCF are

available at time of QA forms review.

6.13.4.4.1.2. (Added) QA will maintain control of transcribed forms until aircraft releases FCF.

6.13.4.4.2. (Added) Allow adequate time for a comprehensive forms review by QA before

briefing the aircrew.

6.13.4.4.3. (Added) Include an IMDS screen 380 printout with option 6 including all

suppressed discrepancies with the aircraft forms during the QA forms review. Ensure the

documentation requiring the FCF/OCF is complete.

6.13.4.4.4. (Added) Ensure system knowledgeable personnel are available during the QA forms

review and aircrew brief for any questions.

6.13.4.4.5. (Added) Accomplish the following steps during a TDY without QA support

available:

6.13.4.4.5.1. (Added) Ensure FCF kits are available and maintained with all required technical

data and checklists to properly perform a FCF brief.

6.13.4.4.5.2. (Added) Retain all FCF checklists and AF Form 2400, Functional Check Flight

Log and return both the log and checklist to the home station QA section.

6.16.5. (Added) W&B update requirements.

6.16.5.1. (Added) W&B update is not required when removing and reinstalling the same

component item prior to aircraft’s next flight.

6.16.5.2. (Added) The following actions will take place if a flyable component or assembly is

removed, installed, canned or when TCTOs affect W&B. A separate "Red X" discrepancy will

be entered in the AFTO Form 781A that reads, “Weight and balance update required” followed

by a brief description of the component removed/installed or TCTO accomplished. W&B “Red

X” discrepancy must be referenced to the original removal/installation discrepancy.

6.16.5.3. (Added-C130 Only) W&B discrepancies for –21 equipment due to configuration

changes, individual shortages, or surpluses of equipment resulting in the removal or installation

of items weighing five pounds or more are to be documented in the AFTO Form 781A. The

discrepancy for configuration changes will state: “Weight and Balance due, aircraft reconfigured

from____to____.” (Example: TAC-1 to RAPID). Modification of a listed AFI 11-2MC-130,

Vol 3, Addenda D or MC-130J Operations Conops Annex C Addenda configuration will be


explained in the discrepancy block detailing the modification. Exemption: W&B documentation

is not required if Flight Crew documents the removed -21 equipment on a DD Form 365-4,

Weight and Balance Clearance Form F Transport, for that sortie.

6.16.5.4. (Added) “On-Aircraft” reconfigurations are defined as a reconfiguration of -21

equipment that is moved from its stowed position on the aircraft to its rigged position on the

aircraft or vice versa. W&B is not required for on-aircraft reconfigurations if no items are

removed from or installed on to the aircraft.

6.16.6. (Added) A QA W&B technician will perform the update, post the change to the primary

and supplemental handbooks, sign-off the W&B discrepancy/IMDS, and inform the production

superintendent of W&B completion.

6.16.7. (Added) Procedures for Isochronal (ISO) and phase inspections, Refurbishment

(REFURB), On-Condition Maintenance (OCM), and Cannibalized (CANN) aircraft. NOTE: An

aircraft is considered to be in CANN status when designated by maintenance supervision

and MOC is notified of the status.

6.16.7.1. (Added) Removed components and assemblies do not require separate W&B entries if

they are reinstalled before the aircraft is released from ISO, phase inspection, REFURB, OCM or

CANN status. A “Red Dash” entry will be made in the AFTO Form 781A stating “Forms review

is required to determine if W&B updates are applicable.”

6.16.7.2. (Added) Before an ISO or phase aircraft is released to the owning unit, the dock chief

will ensure each open discrepancy for removed components/equipment has a separate W&B

discrepancy entered in the AFTO Form 781A. Once this is complete, the dock chief will sign off

the forms review. The corrective action will state: "A forms review was conducted and all W&B

requirements are properly documented."

6.16.7.3. (Added) When an aircraft completes REFURB, OCM or is released from CANN

status, the appropriate production superintendent will be responsible for complying with

necessary W&B requirements as applicable.

6.16.7.4. (Added) Equipment installed and TCTOs completed during ISO, phase inspection,

REFURB, OCM and CANN status will be documented IAW applicable W&B procedures.

6.16.7.5. (Added) Owning units will notify QA when aircraft are reconfigured for flight after a

home station check (HSC), ISO, REFURB, OCM, TCTO or is being released from CANN

status.

6.16.7.6. (Added) Aircraft designated as CANN aircraft will require QA to perform an aircraft

forms QVI and BPO/Preflight QVI prior to the first flight. The forms documentation QVI can be

accomplished at any time between pre-dock and the BPO/Pre QVI.

6.16.8. (Added) Procedures for aircraft being transferred:

6.16.8.1. (Added) An aircraft is considered transferred when aircraft possession code changes.

When an aircraft is to be transferred in or out, the owning unit will enter a single Red dash in the

AFTO Form 781A stating “Aircraft transfer weight and balance inventory required”. QA

inspectors will conduct a Chart A inventory, perform updates, and sign-off the discrepancy.

Equipment removed or installed after the inventory is accomplished will require separate AFTO

Form 781A entries.


6.16.9. (Added) Procedures for updating records of deployed aircraft:

6.16.9.1. (Added) Prior to all aircraft departing for an extended deployment, the production

superintendent of the affected aircraft will notify QA of the estimated duration of the

deployment. QA will determine if W&B records or disk will be sent with the aircraft.

6.16.10. (Added) Deployments with QA W&B personnel.

6.16.10.1. (Added) QA personnel will deploy with a portable computer, printer, W&B forms,

and copy of the Chart A and master W&B data.

6.16.10.2. (Added) Procedures for updating will be the same as above. If the computer fails

while TDY or deployed, manual W&B forms will be used for updates for the remainder of the

trip or until a new computer is obtained.

6.16.10.3. (Added) Upon return to home station, the master W&B computer and primary book

of affected aircraft will be updated immediately.

6.16.11. (Added) Deployments without QA W&B personnel.

6.16.11.1. (Added) Flight crews will use the DD Form 365-4, Weight and Balance Clearance

Form F Transport, to perform W&B updates as required.

6.16.11.2. (Added) Maintenance personnel will enter an “INFO NOTE” in the AFTO Form

781A “Form F entry required” followed by a brief description of the component

removed/installed.

6.16.11.3. (Added) Prior to deployment/transfer and upon return to home station, the applicable

AMU Production Superintendent will notify QA of any aircraft transfer/departure/return. QA

will then conduct an inventory of aircraft and update any W&B requirement.

6.16.12. (Added) Aircraft weighs:

6.16.12.1. (Added) Hangars 109, 133, 194, 195, 196, 197, 199, 204, 208, 4605, 4607, 4606,

4608, 4609 and 4610 have been certified by 27 SOCES/CEN. Hangar 4605, 4606, 4607, 4608,

4609 and 4610 have been certified for C-130 weighs. Hangar 199 bays 2 & 3 can be used for

CV-22 weighs, and Hangar 195 and 196 can be used for MQ-9 weighs as long as the

requirements in TO 1-1B-50, Chapter 6 are met.

6.16.12.2. (Added) Maintenance personnel will complete weigh prep checklist found on

SharePoint in the 27 SOMXG/QA/Local Forms section before each weigh.

6.16.13. (Added) QA weight and balance technician will accomplish a weight and balance

records check/inventory annually. A JST will be loaded by wing P&S for each assigned MDS.

7.3.1.2.4. (Added) Suspected FO in the critical areas of the flight deck. Critical Area is defined

as but not limited to: throttle quadrant, rudder pedals, and any other accessible flight controls.

7.3.1.2.5. (Added) Suspected FO is when an item is discovered missing during an inspection

and it is unknown if the item was there prior to the inspection.

7.3.1.2.5.1. (Added) Known FO is any item dropped in the flight deck and/ or discovered

missing after flight and was known to be there before the flight.

7.3.1.2.5.2. (Added) If the item is not found, the Impoundment Official will determine whether

a reasonable search has been conducted for aircraft impoundment release.


7.3.1.2.5.3. (Added) AFTO Form 781A entries will be made to identify the missing

hardware/item to prevent future impoundments for the same item until the item is replaced. An

“INFO NOTE” will be placed in the 781As stating the areas searched.

7.5.13. (Added) Complete loss of braking system.

7.5.14. (Added) Loss of hydraulic power.

7.5.15. (Added) Contaminated fluids due to unknown causes.

7.5.16. (Added) Loss of commanded flight during C-band/LRE operations. On RPA, all

affected systems.

7.5.17. (Added) Third-time repeat/recurs for code 3 write-ups.

7.5.1.18. (Added) Inadvertent weapons release (Exception: CV-22 aircrew will remove

weapon).

7.6.3.5.1. (Added) Cordon aircraft/equipment IAW applicable 27 SOMXG Form 2A/B/C.

7.6.11. (Added) Impounded aircraft/engine/GCS/equipment forms will not be transcribed until

the Impound Release Authority has cleared the Red X for impound.

7.6.12. (Added) Upon impound of an aircraft, engine or equipment the Impound Authority,

MOC, or production superintendent will notify Quality Assurance at which time the Impound

Official or on-duty production superintendent will be assigned an impound folder with all

applicable checklists, ECP/maintenance log, and references (27 SOMXG Form 2A or 2B).

7.6.13. (Added) The impound folder will remain with the aircraft, engine, equipment forms

until impound is cleared by the Impound Release Authority. Return completed folder to Quality

Assurance with all copies of AFTO Form 781As/AFTO Form 244 applying to the impound.

Impound documents will be filed in Quality Assurance for one year.

7.6.14. (Added) Impound official for contractor maintained aircraft or GCS will be SNCO

equivalent.

7.6.15. (Added) Two Red Dash entries, in addition/reference to the impound Red X, will be

made in the appropriate aircraft/equipment forms for (1) Squadron Supervision forms review due

(MOO, Chief or Superintendent) and (2) QA forms review due. The corrective action blocks

will state; “Records review C/W.” Both reviews will be complied with before the Impound

Release Authority receives the forms.

7.6.16. (Added) When aircraft are off station and require impoundment, the Impoundment

Authority and deployed MOC will notify home station MOC as soon as possible. Production

Superintendent will take applicable electronic copies of the 27 SOMXG Form 2A/B/C/D found

on SharePoint at 27 SOMXG/QA/Local Forms. Exception: Use of 27 SOMXG QA Forms are

not required if AOR Command has published local impound forms. Return all completed forms

and AFTO Form 781A copies to home station MOC or QA within 24 hours of impound released.

7.6.16.1. (Added) MOC will maintain a log or computer program containing the aircraft,

equipment or engine serial number, time and date of impoundment, reason for impoundment,

personnel notified, date released, impound official and releasing authority.

7.6.17. (Added) Items requiring 27 SOMXS bench check, other serviceability checks or

placement in the FOM bin will have a red-bordered AFTO Form 350, Repairable Item


Processing Tag attached with "IMPOUNDED AIRCRAFT" written or stamped in bold red

letters. The discrepancy block will contain a clear description of the malfunction causing the

impoundment, name and phone number of the technician who removed the part and the

impoundment official’s name and phone number.

7.6.18. (Added) 27 SOMXS maintenance supervision will coordinate with the impoundment

official on repairs to unserviceable components and will ensure components tagged as

impounded will be expedited through repair shops to avoid delays in the investigation.

7.6.19. (Added) Serviceable units, where the corrective action was CND, are to be returned to

the impoundment official. The impoundment official will coordinate further troubleshooting

and/or bench checks if the unit continues to malfunction in the aircraft.

7.6.20. (Added) QA will:

7.6.20.1. (Added) Monitor all impounded aircraft, engines, and equipment.

7.6.20.2. (Added) Prior to the impoundment release, perform a review of the aircraft,

equipment, or engine forms.

7.6.20.3. (Added) Review/copy all check sheets and pertinent material used during the

investigation.

7.6.20.4. (Added) File and maintain impound folder in QA office once impound is cleared.

7.6.20.5. (Added) QA will maintain a copy of the current IMDS screen 597 for Impound

Authorities.

7.6.21. (Added-C-130 Only) Flight Control Impoundment/Diagnostic Procedures.

7.6.21.1. (Added) The affected AMU in conjunction with Aero Repair (AR) will establish a

team of highly qualified system experts and AR technicians as a Flight Control Team (FCT).

Only one team will be assigned to a specific problem and team integrity will be maintained until

the impoundment is released.

7.6.21.2. (Added) FCT Composition. The team chief will be a highly qualified 7 or 9-level

technician who reports directly to the impoundment official. Team members will be the most

experienced flight control technicians (2A571) and system experts available at the time of the

malfunction. When required, additional technicians may be appointed to the team.

7.6.21.3. (Added) QA and AFETS personnel may only be used as technical advisors.

7.6.21.4. (Added) FCT warranting conditions. Debrief will notify the AMU OIC/NCOIC when

a flight control malfunction arises. The OIC/NCOIC will determine if flight control diagnostics

are required and if so, notify QA. Chronic, repeat, or recurring flight control/air data

malfunctions merit consideration for FCT formation.

7.6.21.5. (Added) The FCT chief or designated representative will debrief the aircrew.

Additionally, IMDS historical data will be used in developing a troubleshooting strategy.

7.6.21.6. (Added) Routine maintenance, except fuel/oil servicing, will not be performed unless

approved by the impoundment official with FCT chief concurrence.


7.6.21.7. (Added) FCT chief will receive detailed documentation of team findings and actions

before the end of each day’s shift. Before beginning work each day, the FCT will meet to review

findings, work accomplished and plan for further action.

7.6.21.8. (Added) All troubleshooting and maintenance actions will be documented in the

AFTO Form 781A and in IMDS. Additionally, each AMU will document all actions in detail in

a manual log.

7.6.21.9. (Added) When discrepancies cannot be duplicated (CND) on the ground and when

troubleshooting, bench check and diagnostic techniques fail to provide a satisfactory fix, the 27

SOMXG/CC may authorize an OCF/FCF to verify system performance.

8.1.1. (Added) A “Tool Kit” or “CTK” is defined as more than one item in a case, box, bag,

etc. and will only be issued as a whole kit. Removal and issue of a single item from a tool kit or

CTK is not authorized.

8.2.3.1.1. (Added) Warranty tools will be exchanged per the vendor’s warranty.

8.2.3.1.2. (Added) Unserviceable warranty tools will be separate from non-warranty tools,

secured, and accounted for until turned in for replacement.

8.2.3.1.3. (Added) Serviceable warranty spare tools will be stored and accounted for in the

spare tools bin/cabinet and compartments will be marked as ―Warranty Tool.

8.2.4.1. (Added) Support section NCOIC will closely monitor the spare and consumable tool

program. Spare tools will be kept to a minimum and will not exceed 10 of any item (example of

tools: hammers, wrenches, screwdrivers, sockets, etc). The exception is high-use tools and

consumables issued from supply or manufacturer in cases exceeding 10 (example of high-

use/consumables: apex bits, drill bits, clecos, sanding pads, wire brushes, acid brushes, etc). Do

not store broken, corroded or unserviceable tools in spare tool cabinets.

8.2.4.2. (Added) Spare and consumable tools will be accounted for in TCMax and secured with

padlock or drawer locks at all times. TCMax will be updated on a one-for-one swap-out basis

and will reflect the exact quantity in each bin/drawer. Access to spare tools will be limited to

unit/section supervision, support flight chief, support section NCOIC, support shift supervisors

and program managers.

8.2.4.3. (Added) If replacement is not readily available, remove all unserviceable items,

document in TCMax and on the MIL. Replace unserviceable items as soon as a replacement

becomes available.

8.2.9.4. (Added) Rags will be controlled as strictly as tools.

8.2.9.4.1. (Added) Dispatchable cloth rags will be issued as a kit of five rags in a bag. The bag

will be inventoried upon issue and turn-in to Support section. The bag will be marked with a nine

digit EID and the quantity of rags will be listed on the outside of the bag. The rags inside the bag

do not require EID markings. MILs are not required. Support personnel will replace kit rags as

necessary. Back shop support sections may issue single item in-shop rags not be used on

aircraft/engines and do not create a FOD potential on the flight line. Cheesecloth will be issued

on a one-for-one swap.

8.2.9.4.2. (Added) Replacement rags will be treated as spare/consumable tools and accounted

for in TCMax on a one-for-one swap-out basis. Due to high-volume replacement of rags, clean


replacement rags will be accounted at shift turnover. Replenishment containers in the Support

section do not require locks. Excess/bulk rags will be stored in the spare tools cabinet and will

be accounted for. TCMax will match rag quantity at all times.

8.2.9.4.3. (Added) Lost rags or pieces of rags will be handled using the same procedures as a

lost tool.

8.2.9.5. (Added) Lint-free rags bulk ordered in a non-standard size must be cut down to a

uniform size before being issued to user.

8.2.13.1.1. (Added) Mobile CTKs (hard mounted inside vehicles) will be inventoried when

vehicle is checked in/out from support and at the completion of each use.

8.2.15.2. (Added) If no one is available from the Support section, the shift production

superintendent will perform a thorough inspection/inventory of the item before signing it back in.

8.3.5.2. (Added) If tools are permanently removed from a dispatchable CTK, the custom inlay,

shadowed layout or silhouette will be filled in (i.e.; glue down foam that is used to fill in foam

cut-out voids).

8.3.5.3. (Added) Tools/kits/TMDE/oversized items that do not require a foam shadow must

have an obvious designated outlined location and have a TCMax/TAS EID with the name of the

item affixed to the location to reflect the item removed.

8.3.6.3.1. (Added) MILs are not required to be listed as a separate item in TCMax. A lost MIL

is not required to be reported as a lost tool.

8.3.6.4.3. (Added) If a container (ex. film case, pill bottle) has a removable lid, the base and lid

will be connected with a securing device or lanyard.

8.3.6.4.4. (Added) All test equipment electrical connectors, fuel, oil, hydraulic and oxygen

connections exposed to physical or environmental damage, or are in an area where such damage

could occur will have dust caps/plugs installed and caps/plugs must be secured to the unit with a

lanyard (link/ball chains, cables, safety wire or wax string). Refer to TO 00-25-234, General

Shop Practice Requirements for the Repair, Maintenance, and Test of Electrical Equipment.

Permanently attached dust caps do not require etching but will require annotation on the MIL as

with the non-manufacture dust caps. If it is impossible to lanyard fluid caps (due to lack of

attaching points), the caps will be etched and itemized on the MIL.

8.3.6.8. (Added) Dispatchable CTKs used for maintenance on aircraft and flight line will

contain a packaging envelope used to secure the MIL. Envelopes securing the MIL will be

attached to the CTK.

8.3.6.9. (Added) Engine Change Kits, Crash Recovery Trailers and Spill Kit Trailers will

follow all guidance regarding CTK management. The trailer will be set up as one CTK and all

items within or attached to the outside of the trailer will be marked with the nine digit WWID.

All forms associated with CTKs/vehicles are required to be maintained as applicable.

8.3.6.10. (Added) All dispatchable TMDE containing multiple parts will have all pieces listed

on the MIL.

8.3.7.2. (Added) Individual issue bins and workshop/bench CTKs for in shop use will be

inventoried before and after each use.


8.3.10.3. (Added) Flashlights such as Mag-Lites will have the rubber switch cover removed

prior to use unless removal renders the flashlight unserviceable and does not present a FOD

hazard.

8.3.13. (Added) Work sections will establish a program for secure sealing of low-use tools.

Tools only signed out every 45 days or more are considered low use. Inventory the identified

low-use items any time they are returned from a job and seal them in a way preventing opening

without breaking the seal (i.e., computer label sticker, lead seal, plastic zip strip, etc.). Label the

item with the signature of individual performing tool count, date counted and sealed, number of

pieces, tool kit number or item number. The low-use sealed items are only required to be

verified as "present" during daily shift inventories as long as the seal is intact. The seal remains

valid as long as the item is unused and the seal remains secure or until the next 180-day CTK

inspection. Low use items will be identified in TCMax.

8.3.14. (Added) If installed, FOD bags will be marked with the letters "FOD", EID for the

associated CTK and added to the CTKs MIL. If installed, FOD bags will be shadowed in or

attached to the CTK (may be attached to the outside of the CTK). If installed, FOD bags must

secure the FO contents when closed.

8.3.15. (Added) During deployments or off-station operations, production superintendent or the

ranking NCO will complete an inventory of the mobility bin and all unsealed deployed CTKs.

This inventory will be accomplished at the beginning and end of each shift and annotated on the

manual CTK Inventory Log Use this form to dispatch tools from mobility bins if TCMax/TAS is

unavailable at deployed locations.

8.3.16. (Added) If contractor and military are operating the same tool room/support section, the

contractor will coordinate with the Support NCOIC on proper tool procedures and

accountability.

8.5.3.3. (Added) CTK/TMDE will be visually inspected and inventoried prior to turn in, to

identify missing/broken/damaged/wet tools, replacement of consumable items (i.e., safety wire),

cleanliness and removal of FO. TOs, Job Guides, and Check Lists will fall under the same

guidelines and will be inspected for missing/damaged pages, binder rings and serviceability.

The USER will accomplish the inspection before the CTK/TMDE/TO is returned in

TCMax/TAS and will inform the Support custodian of any discrepancies. The USER is

responsible for cleaning and drying tools/tech data soiled or saturated during their ownership of

the tools.

8.5.4.4. (Added) All in-use CTKs and equipment assets will be inspected at least every 180

days. This inspection will include a thorough inspection for accountability (which includes all

required documentation, shadowing, etchings and inventory), serviceability and replenishment of

consumables, FOD and corrosion prevention treatment. The 180 day inspections for a rack or

drawer of tools can be grouped into a single inspection if there is a MIL identifying all items in

the rack or drawer. CTKs in rack or drawers with individual MILs will be inspected as CTKs

and annotated as such. TMDE inspections (if required by individual equipment’s TO) must be

tracked in TCMax separately.

8.6.1.2.1. (Added) See 27 SOMXG Form 22 for a listing of authorized CAFB WWIDs located

on Share point at 27 SOMXG/QA/Local Forms (see note for TELFORD/SNC as applicable, tool


kit etchings and identification). Requests for additional numbers or changes will be coordinated

with and approved by QA.

8.6.6.1. (Added) Unserviceable tools will have identifying markings/etching removed and will

be kept in a secure location until disposed of. Unserviceable warranty tools will be distinctly

separated from other unserviceable tools.

8.6.7. (Added) Soft marking is defined as using paint, permanent ink, pressure sensitive labels,

embossed plastic labels, and bar codes. Hard marking is defined as etching, stamping or

scribing.

8.6.8. (Added) Erroneous etchings/markings must be removed from all tools and equipment.

8.6.8.1. (Added) Double etched or double marked is defined when two or more different

TCMax/TAS/Unit identifiers are present on any item. NOTE: If a clear effort to remove or

obliterate a previous marking is evident, even though that marking can still be read, the tool is

not considered double etched. Every effort will be made to remove previous etchings. If visible

previous etchings result in accountability problems or confusion, tools will be replaced.

8.6.9. (Added) All dispatchable CTK/TMDEs, Engine Change kit/trailer, Crash/Recovery

trailer, Armor boxes will be clearly marked with reflective tape/paint on all four corners of the

box/kit/trailer.

8.6.10. (Added) Vehicle keys will not be etched due to cost of replacing ignition switches and

door locks.

8.6.10.1. (Added) Vehicle keys will be tracked in TCMax and have a streamer with the WWID

number.

8.7.4. (Added) Use 27 SOMXG Form 4 for QA approval of Local Manufactured

Tool/Equipment Request with drawings/pictures attached. This procedure does not apply if the

local manufactured, modified or designed tools are authorized/listed in the specific technical

data. QA Local Manufacture Tool Manager and applicable work center will retain a central file

copy of all required paperwork (electronic or hardcopy) for review. Special tools located in TOs

requiring local manufacture will use supply -6 paperwork to complete the manufacturing

process. Approved locally manufactured tool/equipment letter will be reviewed for applicability

biennially (every two years); if the locally manufactured tool/equipment is still applicable, a new

letter approved by the MXG/CC is required.

8.8.2.1.3. (Added) When the Support section/tool room is unattended, all doors will be locked.

After-hours access will only be granted to essential personnel listed on the authorized entry letter

posted at every entry. Personnel not on this letter will be escorted while in the Support

section/tool room. The authorized entry letter should list all assigned individual needing access

during normal hours and after hours.

8.8.2.2.3. (Added) Locks on dispatchable CTKs will be secured to the CTK by cable or chain

and listed on the MIL. Keys will have a "REMOVE BEFORE FLIGHT" streamer permanently

attached. The streamer will measure at least 6" in length. Streamers will be permanently marked

with CTK WWID and annotated on the MIL.

8.9.3. (Added) Refer to SharePoint in the 27 SOMXG/QA/Local Forms section to download

the Lost Tool/Object Reporting Procedures Checklist and Worksheet (27 SOMXG Form 11).

The 27 SOMXG Form 11 will be initiated after one hour after discovery if not found. The


checklist is all-inclusive and covers incidents to include tools or items that are lost on/around

aircraft, after taxi/take-off and while performing maintenance on/in back shops and support

equipment. Complete the portion of the checklist applying to the incident. The 27 SOMXG

Form 11 will be turned into QA once completed. It can also be emailed to the QA Org box at: 27

SOMXG/QA v3. All contractor and military personnel must immediately notify

production/maintenance superintendents when a tool/object is discovered missing. The

production/maintenance superintendent will stop all maintenance procedures for

launching/taxiing aircraft and use the Lost Tool/Item Reporting Procedures Checklist to initiate

required notifications/actions and the Lost Tool/Item Worksheet to document all pertinent

information and areas searched.

8.9.4. (Added) All available personnel in assigned unit(s) will conduct a thorough search.

Document all areas searched. i.e., aircraft, AGE, ramp, CTKs and buildings on the Lost

Tool/Object Worksheet and return completed form to QA.

8.9.4.1. (Added) After lost item/tool procedures have been completed, personnel should remain

vigilant for lost tools and report recovered tools to Wing FOD monitor and QA for tracking

purposes.

8.9.5. (Added) If it is determined maintenance was performed and the tool/object was lost on

the launching aircraft after engine start/taxi the flight crew will be notified to return to parking

and shutdown engines.

8.9.6. (Added) When a tool/object is discovered lost after an aircraft is airborne, initiate the 27

SOMXG Form 11, and notify the MOC who will in turn notify the AMU OIC/MS, 27

SOMXG/CC, and QA. Wing Command Post, and the 27 SOG/CC, will be notified at the

discretion of the 27 SOMXG/CC.

8.9.6.1. (Added) Depending upon which area of the aircraft the lost tool/object was used the 27

SOMXG/CC will determine the safest way to recover the aircraft. Complete the 27 SOMXG

Form 11 and return to QA.

9.24.4. (Added) All aircraft parts turned in to COSO as NRTS will have an IMDS screen 122

attached showing the completed NRTS action.

9.24.5. (Added) All aircraft parts turned in to COSO for repair action will have IMDS screen

122 and 387 attached showing the repair action and document number loaded.

Table 11.1. (Added) Mandatory Special Certification Roster (SCR) and Prerequisites.

A B

ITEM Mandatory SCR Items Prerequisites

37 C-130 Gear Retract Supervisor SSgt or higher, minimum 7-skill level with AFSC

2A571 & 2A6XX. MXG/CC Approval, may

waive qualified 5-skill level SSgt or higher

38 C-130 Jacking Supervisor SSgt or higher, minimum 7-skill level. MXG/CC

Approval, may waive qualified 5-skill level SSgt

or higher

39 Jacking Manifold Operator SSgt or higher, minimum 7-skill level. MXG/CC

Approval, may waive qualified 5-skill level SSgt

or higher


40 CV-22 Jack Team Supervisor SSgt or higher, minimum 7-skill level (or civilian

equivalent). MXG/CC Approval, may waive

qualified 5-skill level SSgt or higher

41 CV-22 Blade Fold Wing Stow

(BFWS) Supervisor

SSgt or higher, minimum 7-skill level with AFSC

2A3XX, 2A5XX, or 2A6XX (or civilian

equivalent), with 6 months MDS experience. Must

pass BFWS test. MXG/CC Approval, may waive

qualified 5-skill level SSgt or higher

11.6.6. (Added) When an aircraft is within the crew ready window as specified in Para 11.6.7.

and is not ready for flight due to maintenance/Aircrew Flight Equipment related issues or a

problem develops after crew show, the actions necessary to return the aircraft to flyable status

will be given priority. This same priority applies to aircraft called back from scheduled missions

for Higher Headquarters (HHQ) mission generation and aircraft returning mid-mission for

maintenance related issues.

11.6.6.1. (Added) Crew Ready times:

AC-130W: 3.5 hours.

MC-130J: 3.5 hours

CV-22B: 2 hours.

MQ-9: 2 hours.

11.6.7. (Added) Red Ball Notification Process and Job Control Numbers.

11.6.7.1. (Added) In the event that Red Ball occurs, the production superintendent or flight line

expediter will immediately notify MOC of the discrepancy, time of discovery and estimated time

of completion or troubleshooting. MOC will log start and stop times for deviation purposes.

The production superintendent or expediter will call the discrepancy into debrief section for issue

of a manual red ball JCN and IMDS loading. Production superintendent or expediter will notify

MOC with Red Ball completion time. A current list of authorized manual job control numbers

can be found on SharePoint at 27SOMOS/Analysis/DBM/Shared Documents.

11.6.8. (Added) Red Ball Parts Requirements.

11.6.8.1. (Added) If parts are required to repair a Red Ball aircraft, the production

superintendent or flight line expediter will notify COSO who will in turn, check the tail number

bins for the part. If the part is on hand, the COSO will notify the production superintendent,

initiate a mark for change, and reorder to backfill the part.

11.6.8.2. (Added) If the part is not in the tail number bin, the production superintendent will

order the part through COSO. The COSO will give the part requisition priority and relay the Red

Ball document number to the production superintendent.

11.6.8.3. (Added) COSO personnel will notify the production superintendent with part status

within five minutes of request. If the part is available, the COSO will immediately pick up the

asset from Supply. If the part is not available for immediate issue, the production superintendent

may authorize CANN action.

11.6.9. (Added) Support Equipment.


11.6.9.1. (Added) If powered AGE is required, the production superintendent or flight line

expediter will notify the AGE driver of the Red Ball requirement. The AGE driver will

immediately respond to this request ahead of all others.

11.6.9.2. (Added) All other support equipment (i.e., testers, fixtures) will be delivered by the

respective flight line expediter truck.

11.6.10. (Added) Weight and Balance for HHQ regeneration resulting in change of mission

equipment.

11.6.10.1. (Added) In the event mission equipment requirements change due to HHQ

regeneration and a weight and balance is required, the production superintendent will notify QA

for immediate response to the aircraft to verify changes and update the Chart C as required.

11.6.11. (Added) Maintenance Follow-on Actions.

11.6.11.1. (Added) Maintenance actions such as leak checks and operational checks required to

return Red Ball aircraft to flyable condition will be accomplished in accordance with applicable

technical orders and will not be waived.

11.6.12. (Added) Follow-on Documentation.

11.6.12.1. (Added) The AFTO Form 781A will be documented prior to any part being removed

from the aircraft. Any Red X discrepancies discovered during or caused by Red Ball

maintenance will be input and cleared from the forms prior to flight. Every effort will be made

to accomplish all MIS documentation prior to flight. In the event IMDS cannot be cleared prior

to flight it must be accomplished no later than 30 minutes after takeoff. This will be verified by

the production superintendent.

11.7.4. (Added) After receipt of AFSOC Form 9 and/or MRT request, MOC will notify

affected unit and initiate applicable checklist. Affected unit Maintenance Operations Officer

(MOO)/Maintenance Superintendent (MX SUPT) will designate and assign a MRT POC.

11.8.3.23. (Added) Flight deck/Cockpit FOD inspections. The Squadron/AMU production

supervisor is responsible for ensuring the flight deck/cockpit FOD prevention inspections are

accomplished after completion of all maintenance prior to signing the exceptional release.

Completion of the exceptional release signifies this inspection has been accomplished.

11.10.5.3. (Added) Be identified by appointment letter.

11.10.5.4. (Added) Download ASIP inspection into Automated Inspection, Repair, Corrosion,

and Aircraft Tracking (AIRCAT) after NDI/Sheet Metal have input their inspection into

Inspection, Corrosion, and Repair Recording (ICARR).

11.10.5.5. (Added) Maintain a tracking log of all aircraft inspected IAW 1C-130A-6WC-15,

Minor and Major Isochronal Inspection, with all findings positive/negative annotated. (C-130).

11.10.10.1. (Added) Debrief sections will enter all appropriate ASIP data into IMDS.

11.10.13.1. (Added) PS&D schedules and tracks all ASIP inspections for NDI/ Sheet Metal.

11.10.14. (Added) If aircraft Isochronal (ISO) is accomplished at deployed location, the on-site

ASIP Program Manager Representative will forward the ASIP inspection results to home station

for input into ICARR and AIRCAT.


11.11.3. (Added) Responsibilities for IFF checks.

11.11.3.1. (Added) The IFF Mode IV Program Manager will:

11.11.3.1.1. (Added) Assume overall responsibility for compliance of IFF checks.

11.11.3.1.2. (Added) Ensure the status of all IFF transponder test sets and crypto loading

devices are serviceable.

11.11.3.1.3. (Added) Ensure compliance of IFF Mode IV/V checks IAW AFI 21-101 and

aircraft specific technical data.

11.11.3.1.4. (Added) Will validate checks every two months by pulling IMDS data.

11.11.3.1.5. (Added) Keep a logbook for the IFF Mode IV/V program. Program manager will

keep a 12-month history in the IFF Mode IV Program continuity book. This book will also

contain the current month IFF Mode IV/V worksheet.

11.11.3.2. (Added) The Specialist Element Chief will:

11.11.3.2.1. (Added) Appoint a primary and alternate IFF Mode IV/V program monitor.

11.11.3.2.2. (Added) Ensure adequate numbers of personnel are trained and qualified to

perform IFF Mode IV procedures.

11.11.3.2.3. (Added) Ensure failed IFF Mode IV/V checks are annotated into IMDS and the

AFTO Form 781As and corrective actions are taken.

11.11.3.2.4. (Added) Ensure the monthly Pass/Fail worksheet is complete and sent to the 27

SOMXG IFF Mode IV/V program manager, located in QA, by the 10th of each month.

11.13.3.3. (Added) Designated CANN authority list will be reviewed and updated quarterly by

the MXG/CC or equivalent.

11.14.2.1.3. (Added) In addition to a forms review prior to flight, a BPO/Preflight or BPO and

Preflight QVI will be accomplished by QA when documented separately.

11.14.2.1.4. (Added) Make the following Red Dash entry in the AFTO Form 781A documents

when an aircraft is designated as hangar queen. "BPO/PRE or BPO and Preflight QVI due by

QA prior to flight."

11.14.2.1.5. (Added) In the absence of QA during deployments, the forms review and

BPO/PRE or BPO and Preflight (when documented separately), QVI will be accomplished by

the deployed Production Superintendent.

11.17.1.5. (Added) All maintenance personnel qualified to perform C-130/CV-22/MQ-9 engine

runs will be qualified IAW AFI 21-101, AFSOC Sup Aircraft and Equipment Maintenance

Management, AFI 11-218, Aircraft Operations and Movement on the Ground. All units will

utilize AMC Form 64 to request for special certification.

11.17.5.3.9. (Added) Initial engine run certification will be completed within 30 days of Formal

Engine Run Course.

11.17.6.5. (Added) The maintenance engine run test must be accomplished within the same

month of the annual recertification and prior to the due date in MIS.


11.17.6.6. (Added) Overdue Annual Engine Run Recertification requires an Engine Run Test

and Engine Run. Recertification and routing an AMC Form 64 and AF Form 2426 from the

engine run manager to MTF.

11.17.6.7. (Added) First-time failures of the Engine Run test require immediate supervisor

authorization to retest.

11.17.6.8. (Added) Third-time failures require decertification in TBA and MIS, re-accomplish

Phase I and Phase II training with the authorization MXG/CC or MXG/CEM.

11.17.7.1. (Added) Use the AMC Form 64 for initial engine run/APU certification. Engine Run

Certifiers will route the completed AMC Form 64 to UTM. The following courses will apply:

Formal Course (one time) Engine Run.

Initial Certification (one time per base) Engine Run.

120 day Proficiency / Engine Run.

11.17.7.2. (Added) Upon identification of pending engine run overdue, the work center will

begin recertification process, or ensure member completes requirements prior to overdue date.

11.17.7.3. (Added) For the annual recertification the engine run manager will forward the AF

Form 2426 to the UTM.

11.17.8.3.1. (Added) If overdue 120-Day Proficiency, members are required to retake the

Engine Run Test and perform Engine Run Recertification within 30 days of taking test and route

an AMC Form 64 / AF Form 2426 from the engine run certifier to the UTM.

11.17.10.8. (Added) APU/GTC course will be taught in the sections through OJT. APU/GTC

SCR courses will be tracked and will be updated along with the annual engine run certification:

Annual Certification APU/GTC.

Certifier APU/GTC.

11.17.16. (Added) Personnel deploying should accomplish their engine run prior to departure.

If this is not available then the same procedures will be used at the TDY location and then

forwarded back to Cannon AFB for updating in MIS.

11.17.17. (Added) The following crew positions will be filled with personnel current to the

following qualification levels:

11.17.17.1. (Added) The minimum crew for a C-130 engine(s) run at ground idle will be:

Pilot’s seat – C-130 engine run qualified.

Co-pilot’s seat – C-130 must be qualified on brakes, hydraulic panel and communications

operator.

Ground person - must be ground-power equipment and fire extinguisher qualified.

Interphone contact with flight station personnel must be maintained at all times.

11.17.17.2. (Added) The minimum crew for a C-130 engine run above ground idle will be:

Pilot’s seat - engine run qualified.

Co-pilot’s seat - qualified brake, hydraulic panel, and communications operator.

Engineer’s seat - engine run qualified.

Ground person - must be ground-power equipment and fire extinguisher qualified.



11.17.17.3. (Added) The minimum crew for a MC-130J engine run at ground idle will be:


Co-Pilot’s seat - qualified brake operator.

Ground observer - must be ground-power equipment and fire extinguisher qualified.


11.17.17.4. (Added) The minimum crew for a MC-130J engine run above ground idle

including reverse will be:


Co-Pilot’s seat - engine run qualified.

Ground observer – must be ground-power equipment and fire extinguisher qualified.


11.19.3. (Added) Support sections possessing borescope equipment will maintain a listing of

personnel authorized to sign-out engine flexible borescope equipment. The only technicians

authorized and certified to use engine flexible borescope equipment are tracked in IMDS using

the initial flexible borescope certification course code. Use of the FOD borescope does not

require borescope certification. Unit/MS/Superintendent will sign AMC Form 64 to add engine

borescope authorized personnel to SCR. Support personnel will update the restricted

TCMax/TAS items for engine borescope sign-out per IMDS course codes.

11.34.2.2. (Added) Prior to attending Crane or Crane Refresher, member must have a current

and approved Occupational Health Exam (OHE).

11.38. (Added) Forms Documentation.

11.38.1. (Added) Repeat/Recur requirements:

11.38.1.1. (Added) Repeat/recur discrepancies will be clearly marked/stamped in red in the

discrepancy block of the associated write-up. Example: “REPEAT #1” or “RECUR #2”.

11.38.1.2. (Added) For first-time repeat/recur discrepancies, a separate “RED DASH” entry

will be made in the AFTO Form 781A stating “Red X qualified 7-level review required due to

repeat/recur of JCN ‘XXX’”. Clearing the discrepancy requires a 7-level, Red X certified

technician who is qualified on the system to troubleshoot and correct the original discrepancy.

The technician who corrected the original discrepancy will sign the "CORRECTED BY" block

of the original discrepancy. The qualified 7-level, Red X certified technician who troubleshot

and corrected the original discrepancy will sign the “INSPECTED BY” block of the 7-level

review entry created for the repeat/recur.

11.38.1.3. (Added) For second-time or later repeat/recur discrepancies, a separate “RED X”

entry will be made in the AFTO Form 781A stating “Red X qualified 7-level review required due

to ‘X’-time repeat/recur of JCN “XXX”. Clearing the repeat/recur discrepancy requires a 7-level,

Red X certified technician qualified on the system to troubleshoot and correct the original

discrepancy. The 7-level, Red X certified technician qualified on the system who corrected the

original discrepancy will sign the "CORRECTED BY" block of the original job. Another 7-

level, Red X certified technician qualified on the system will review the actions taken to clear the

discrepancy and sign the "INSPECTED BY" block of the original job and the 7-level review

entry created for the repeat/recur. QA or Air Force Engineering and Technician Services


(AFETS) representative may act as advisors. AMU Supervision (MOO/MX Superintendent)

must thoroughly review and track past and present repair actions.

11.38.1.4. (Added) Repeat/recur discrepancies will be closely tracked and reviewed for trends

by unit supervision and DIT program managers/monitors.

11.38.1.5. (Added) Only Red X certified 7-level or higher and/or equivalent civilian personnel

will clear applicable repeat/recur discrepancies.

11.38.2. (Added) CND Discrepancies Documentation:

11.38.2.1. (Added) Personnel will make every effort to duplicate the circumstances creating the

reported discrepancy. The discrepancy may be cleared only after thorough troubleshooting has

been accomplished. CND discrepancies will be cleared in the following manner:

11.38.2.1.1. (Added) CND discrepancies require a review of troubleshooting by a system

qualified 7-level, Red X certified technicians.

11.38.2.1.2. (Added) When a discrepancy cannot be duplicated, the technician will document

"Leak or Ops checked system/component IAW T.O. 00-20-1.

11.38.2.1.3. (Added) If an LRU is removed from an aircraft and I-level CNDs a malfunction,

the supervisor/DIFM monitor will notify the appropriate O-level work center of the CND action.

11.39. (Added) Bird Aircraft Strike Hazard (BASH) Plan.

11.39.1. (Added) AMU responsibilities for reporting and preserving bird strike remains are as

follows:

11.39.1.1. (Added) All AMUs are responsible for ensuring all applicable personnel are aware

of procedures for identifying, reporting, collecting and preserving bird strike evidence.

11.39.1.2. (Added) When a pilot reports a bird strike, they will be directed to report it to the

AMU debriefer. The debrief section will ensure the pilot completes an AF Form 853, Air Force

Bird Strike Report. The debriefer will ensure the production superintendent is notified of the

bird strike so it can be reported up the chain to the appropriate agencies. The production

superintendent will report the incident to the MOC. The completed form will be forwarded from

the debrief section to the Wing Safety office.

11.39.1.3. (Added) When a bird strike is identified on the ground, but not identified by the

pilot, the production superintendent will be notified immediately. The production superintendent

will notify the MOC who will immediately notify the Wing Safety office. The production

superintendent will work with the appropriate flying squadron to identify the affected aircraft’s

last pilot to have the AF Form 853, Air Force Bird Strike Report filled out with as much

information as possible. The completed form will then be forwarded to Wing Safety.

11.39.1.4. (Added) All remains (feathers, beaks, parts) will be collected and placed in zip lock

bags and placed in the bash collection box and raise the flag. Wing Safety will respond to the

incident and collect remains from the aircraft only when there is noticeable damage. The owning

AMU will collect all bird remains when there is no noticeable damage to the aircraft. In the

event Wing Safety cannot respond to the incident in a timely manner or if there is a possibility of

losing remains due to inclement weather, the AMU is responsible for collecting and preserving

the remains for Wing Safety.


11.39.2. (Added) Maintenance Operations Center responsibilities are as follows:

11.39.2.1. (Added) Upon notification of a bird strike from AMU supervision, MOC will

complete the emergency action checklist for bird strike notification. MOC will immediately

notify the Command Post, Wing Safety, 27 SOMXG leadership, QA and the Wing FOD

Manager.

11.39.2.2. (Added) The MOC will coordinate with the Wing Safety office to ensure bird

remains are collected and forwarded to appropriate agencies IAW 27 SOW BASH plan.

11.39.3. (Added) QA responsibilities are as follows:

11.39.3.1. (Added) Upon notification from MOC of a bird strike resulting in aircraft damage,

QA will immediately respond to the affected aircraft and take pictures of the bird remains and

any associated damage. They will file all documentation, to include any reports, on the local QA

drive.

11.40. (Added) Engine Power Run Locations and Notification Procedures.

11.40.1. (Added) Full power run-ups may be performed on any aircraft spot. If there are no

other aircraft or structures within 400 ft to the rear of the propeller for C-130s (One clear aircraft

parking spot for C-130s, two clear spots if aircraft to the rear is on full jacks), 200 ft clearance is

required for MQ-9s.

11.40.1.1. (Added) Engine Run Clearance Procedures:

11.40.1.1.1. (Added) Maintenance personnel must provide MOC with the aircraft tail number,

parking spot, reason for engine run, run operator man number, and power setting prior to

performing engine runs. MOC will pass this information to base operations/control tower and

security police for authorization to perform maintenance engine runs. Additionally during full

power runs, MOC will verify required 400 ft clearance, for C-130, 200 ft required clearance for

MQ-9 aircraft, with requestor and make a radio announcement on all nets informing flight line

personnel of aircraft location and safety precautions. If base operations/control tower is closed,

MOC will contact the Command Post and security forces.

11.40.1.1.2. (Added) The engine run supervisor will contact the air traffic control tower for

clearance prior to engine start. If clearance is given for ground idle settings, the control tower

must be contacted again for power settings. Maintenance personnel must reduce engine power

settings or terminate the engine run if directed by the control tower. When the control tower is

closed, radio contact will be made with the Command Post. Personnel performing engine runs

will monitor the appropriate frequencies at all times.

11.41. (Added) AFTO Form 244 Supervisory.

11.41.1. (Added) Supervisory Reviews will be performed at least every 180 days and after

major maintenance and/or major inspections. During this review, the AFTO Form 244 will be

reviewed to verify proper documentation and compared with MIS for accuracy. Reviewer will

verify equipment is serviceable and all required inspections are documented.

11.41.2. (Added) Lead technician, Flight Scheduler or 7-level equivalent will accomplish

supervisory reviews. Individual will document completion of review on AFTO Form 244 Part

IV IAW TO 00-20-1.

11.42. (Added) CANNONAFB) Hardware Control Procedures.


11.42.1. (Added) Hardware bags (NSN 8150-00-183-6981/6989) or equivalent will be used to

secure all attaching hardware for removed parts and components.

11.42.2. (Added) Bags will be attached to the removed part/component. If bag must be left

with the aircraft/equipment due to in-shop turn-in or higher assembly removal the bag will be

tied to the area from which that part was removed.

11.42.3. (Added) Bag tags will be annotated as follows:

11.42.3.1. (Added) JCN, type, amount of hardware, first name initial, last name and man

number of individual who removed the component. (Example: JCN XXXXXXXXX, 16 screws,

16 washers, 16 nuts, J Doe XXXXX).

11.43. (Added) Aircraft Hangaring.

11.43.1. (Added) Facility managers will ensure towing guidelines and wheel spots are painted

on the floor and a sufficient number of drip pans and snatch cables are available for hangared

aircraft. NOTE: MQ-9 do not require wheel spots when hangared.

11.43.2. (Added) Facility managers are responsible for updating routine inspections of all

associated emergency equipment in maintenance hangars. Users will ensure all emergency

equipment is serviceable before starting any maintenance.

11.43.3. (Added) Tow Supervisor will notify the fire department through MOC if an aircraft is

towed into a hangar lacking an automatic fire suppression system.

11.43.3.1. (Added) Use Hangaring checklist 27 SOMXG Form 19A (C-130), Form 19B (CV-

22), or Form 19C (MQ-9), found on SharePoint in the 27 SOMXG/QA/Local Forms section and

ensure all checks are complete; i.e., munitions downloaded, high frequency radio antennas

disconnected as required per MDS, FO checks during install and removal of aircraft, etc. Tow

Supervisors are ultimately responsible for completing the hangaring checklist and verifying all

steps are complied with.

11.43.3.2. (Added) Display completed checklist at the nose of the aircraft. For CV-22 aircraft,

the tow/hangaring checklist may be displayed in the front windscreen of the aircraft, as long as it

is visible from the outside.

11.44. (Added) 27 SOMXG Local Forms can be found on SharePoint in the 27

SOMXG/QA/Local Forms section.

11.45. (Added) Special Purpose Vehicles/Equipment.

11.45.1. (Added) The following are considered Special Purpose Vehicles and will be chocked

when parked: deicer truck, forklift, MB-2, MB-4, and cranes.

11.45.2. (Added) All trailers or equipment mounted on wheels that do not have brakes

activated when parked will be chocked at all times unless attached to a vehicle.

15.2.3.4.7.1. (Added) AMU PS&D will be the last section to review and sign off a document

review.

15.3.1.5.1. (Added) Units may keep an electronic version of the most recent MIS product as a

back-up plan for when MSAT is unavailable for more than 48 hours. The MSAT administrator

will be assigned to the MXG PS&D.


15.3.1.8. (Added) Wing PS&D serves as the overall OPR for SI, TCI, TCTO and ACM

programs.

15.3.1.8.1. (Added) AMU PS&D and back shops are responsible for validating suspenses for

maintenance performed on their respective aircraft or equipment daily to ensure timely updates

of completed maintenance. Suspense validation for TCIs installed on aircraft, will not be

delegated to performing work centers. The Engine Management Section will validate all

suspenses for engines and engine components.

15.3.1.8.2. (Added) Hazardous materials for TCI and TCTOs will be ordered through the

appropriate Munitions Operations or COSO function. These items will be contained in an

approved HAZMAT/Explosive Sited location until ready for use.

15.3.3.5. (Added) TCTO Management.

15.3.3.5.1. (Added) QA will perform in-process evaluations on the first 10 percent of all

TCTOs/OTIs accomplished (aircraft, engine and commodity) within the 27 SOMXG. As a

minimum, this will include one TCTO/OTI from every affected MDS. The performing flight or

section will not begin the TCTO/OTI until QA is present to monitor and provide guidance for

each step. If new procedures are added to the TCTO/OTI, QA will conduct an additional 10

percent in-process evaluation.

15.3.3.5.2. (Added) When a TCTO is placed into abeyance after the initial TCTO meeting is

conducted, wing PS&D will conduct a subsequent TCTO initiation meeting when the TCTO is

reactivated. All required attendees must be present. Maintenance will not be started until

reactivation meeting is conducted and a new schedule is established.

15.3.3.5.3. (Added) Coordinated T1 and T2 modification instructions will be routed through

QA office and maintained by Wing PS&D until rescinded. AFTO Form 781A, Maintenance

Discrepancy and Work Document, will be used for all modifications on assigned aircraft or GCS.

Form(s) will be placed in the forms binder and will be placed in front of active 781As (see QA

master forms binder). Wing PS&D notifies and coordinates all command modifications through

appropriate maintenance operations functions.

15.3.5.3.4. (Added) All 107 requests will follow TO 00-25-107 requirements.

15.3.5.3.4.1. (Added) AMU PS&D will schedule periodic maintenance engineering

requirements.

STEWART A. HAMMONS, Colonel, USAF

Commander