21.09.2015 Views

Command

AFDD 1 - GlobalSecurity.org

AFDD 1 - GlobalSecurity.org

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

America-based ANG units participating in homeland air defense within Operation<br />

NOBLE EAGLE, need not adopt expeditionary nomenclature since they are not truly<br />

expeditionary. The overall operation, however, should still be modeled as an AETF to<br />

delineate clear chains of operational and administrative authority. Other deployed<br />

wings, groups, and squadrons that are not assigned or attached to the AETF, but<br />

provide significant support (such as airlift and tanker units in the intertheater air bridge<br />

or space and special operations units in direct support), may be designated<br />

“expeditionary” at the discretion of their owning MAJCOM or Service component<br />

commander. Normally, these “expeditionary” forces provide their support through their<br />

functional chains of command.<br />

EXAMPLES OF AETFs<br />

This section presents three recent usages of AETFs. AETFs may be attached to<br />

a joint force as an Air Force Service component; provided in direct support of a joint<br />

force in lieu of attachment; or temporarily established to address an internal operational<br />

Service requirement.<br />

Component AETF. When directed, an AETF may be formally attached to a joint<br />

force at the combatant command, subunified combatant command, or JTF level,<br />

usually with specification of OPCON, forming Service component commands. In<br />

these cases, the AETF commander is a COMAFFOR, and a separate AOC and A-<br />

staff are normally required to employ and support the AETF. Examples of these<br />

components are found in the form of component major commands (MAJCOMs) and<br />

component numbered Air Forces (NAFs) established to support the CCDRs.<br />

Component AETFs may also be attached to JTFs. These have historically been the<br />

most usual manifestation of the AETF.<br />

“Subordinate AETF.” During some operations, especially when there may be<br />

multiple JOAs with multiple JTFs, it may not be feasible to attach AETFs to each JTF<br />

due to C2 resource constraints. In such cases, subordinate AETFs may be<br />

established and placed in support of JTFs. Examples of this structure occurred in<br />

the later phases of Operations ENDURING FREEDOM and IRAQI FREEDOM<br />

(redesignated Operation NEW DAWN), USAFCENT established subordinate task<br />

forces to directly support sub-theater-level JTFs operating in separate JOAs within<br />

US Central <strong>Command</strong> (USCENTCOM). With the approval of <strong>Command</strong>er,<br />

USCENTCOM (CDRUSCENTCOM), these subordinate task forces were not<br />

attached as separate Air Force components to those JTFs, but were established as<br />

supporting forces with OPCON retained by the CCDR-level COMAFFOR<br />

(<strong>Command</strong>er, USAFCENT). In this case, the USAFCENT commander delegated<br />

specified elements of OPCON and ADCON over forces to the subordinate task force<br />

commanders. These task forces were then provided in direct support of their<br />

respective JTF commanders. The USAFCENT commander, as the theater<br />

COMAFFOR/CFACC to CDRUSCENTCOM, maintained a theater-wide perspective<br />

and the ability to re-apportion airpower across the USCENTCOM AOR IAW CCDR<br />

priorities.<br />

68

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

Saved successfully!

Ooh no, something went wrong!