16.08.2013 Views

ANGI 36-101 - Air Force Link

ANGI 36-101 - Air Force Link

ANGI 36-101 - Air Force Link

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

30 <strong>ANGI</strong><strong>36</strong>-<strong>101</strong> 3 JUNE 2010<br />

7.8.1. AGRs called or ordered to Title 10 federal active duty (OCONUS/CONUS)<br />

supporting Active Duty requirements for operations/missions/exercises/training (Title 10<br />

U.S.C. 12301(d), 12302, 12304, or <strong>101</strong>47) will not be terminated from their Title 32 U.S.C.<br />

Section 502(f) orders.<br />

7.8.2. AGRs Performing Title 10 Duty in Support of <strong>Air</strong> <strong>Force</strong> Active Duty<br />

Requirements. Upon approval and by order of a Federal command authority, AGRs<br />

performing Title 10 duty for 30 or more consecutive days in support of the active <strong>Air</strong> <strong>Force</strong><br />

pursuant to Title 10 Sections 12301(d) , 12302 or 12304 for which reimbursement of AGR<br />

accounts may be required as set forth in paragraph 7.9.4, must have their AGR order<br />

amended to include in the remarks section the following information: Authority in which<br />

they are called to Title 10, inclusive dates of the Title 10 duty, named mission they are<br />

supporting, and active duty MAJCOM they are being tasked to support. An example is as<br />

follows: ―AGR <strong>Air</strong>man will convert to Title 10 U.S.C. Section 12301(d) in support of<br />

OPERATION ENDURING FREEDOM from 15 January 2009 to 26 May 2009,<br />

GMAJCOM: ACC.‖ If the GMAJCOM releases the AGR <strong>Air</strong>man from Title 10 duty<br />

sooner than original expiration day, an AGR amendment must reflect the appropriate end<br />

date of the Title 10 duty.<br />

7.8.2.1. AGRs placed on Title 10 status for less than 30 consecutive days for which<br />

reimbursement of AGR accounts may be required as set forth in paragraph 7.9.4, will have<br />

their Title 10 time documented on AF IMT 1299, Officer’s Certificate of Statement of<br />

Service. This form must be completed by the unit, certified by the AGR’s commander and<br />

provided to the <strong>Force</strong> Support Squadron for update into MiLPDS and to assist in DD Form<br />

214, Certificate of Release or Discharge from Active Duty completion Examples of such<br />

missions that may require an AGR to perform occasional Title 10 duty/day(s) are: <strong>Air</strong><br />

Soverignty Alert (ASA), North East Tanker Task <strong>Force</strong> (NETTF), Unmanned <strong>Air</strong>craft<br />

Systems (UAS)/Remotely Piloted <strong>Air</strong>craft (RPA) (such as Predator, Reaper, Global Hawk),<br />

Distributed Common Ground System (DCGS), State Partnership Program (SPP), etc. A<br />

sample of AF IMT 1299, Officer’s Certificate of Statement of Service can be found in<br />

Attachment 15. The AF IMT 1299 will be entered into the Automated Records Management<br />

System (ARMS) as a source document to an <strong>Air</strong>man’s records or filed in the Unit Personnel<br />

Record Group (UPRG), as applicable. Please note this form is applicable to Officers and<br />

Enlisted <strong>Air</strong>men.<br />

7.8.3. Commanders placed on Title 10 status cannot take Title 32 command action as they<br />

are (Title 32 U.S.C. Section 325) relieved of their State Title 32 status while federally<br />

activated on Title 10.<br />

7.8.4. An AGR while on Title 10 active duty orders must primarily support the active duty<br />

mission and any Title 32 business conducted should be incidental to that primary support of<br />

the Title 10 federal mission.<br />

7.8.5. Title 10 activations (voluntary or involuntary mobilization) of AGRs are normally in<br />

support of AEF rotations for contingency operations. Title 10 activations of <strong>36</strong>5 days are<br />

beyond the intent and purpose of the AGR program.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!