Military reference books and manuals (2009-2023, Volume 2)

FM 6-03.05 / MCWP 3-36.1 / NTTP 3-05.19 / AFTTP 3-2.73 /

USSOCOM Pub 3-33 v.3

17 March 2010

101

d. Tilt Rotor Aircraft. Tilt rotor aircraft offers INFIL, EXFIL, resupply, and C2
capability. The CV-22, Osprey, can self-deploy immediately to the area of
operations eliminating dependence on strategic airlift and additional time to tear
down and build up vertical lift assets. It has a vertical takeoff and landing (VTOL)
capability, the comparable speed of an MC-130, double the unrefueled range of
an MH-53M, and requires less aerial refueling tanker support than existing SOF
helicopters. The CV-22 also has improved survivability, reliability, maintainability,
and reduced weapon system support force structure. The CV-22 is designed for
penetrating denied airspace.

e. Light Nonstandard Aviation Vehicles (NSAVs). AFSOC recently added the
M-28/U-28/PC-12 to their inventory. All three aircraft will perform intra-theater
SOF airlift for the TSOC or designated JSOTF commander. These aircraft have
the unique capability of being able to land and take off from unimproved short
airfields not normally serviced by larger commercial type aircraft. They may be
rapidly configured to perform a range of missions from SOF movement, PR,
MEDEVAC, airdrop, and distinguished visitor support.

AFSOC’s fleet of MH-53J and MH-53M helicopters are phased out. AFSOC is
currently fielding the CV-22 tilt rotor aircraft.

f. Special Tactics (ST) Units. ST units provide combat control, special
operations weather teams, and pararescue personnel to ensure air power is
integrated and operable with special operations and CF. They provide PR to
include planning expertise and program management. Additionally, ST units
operate small UASs for ISR, scouting, and BDA. There are six active and one
reserve ST units.

g. Aviation Foreign Internal Defense (AFID). AFSOF support FID operations by
working by, with, and through a foreign nation’s aviation forces from the
ministerial level to the tactical unit. When required, AFSOF provide persistent
manned and unmanned ISR, mobility, and precision engagement. AFSOF
maintain specially trained combat aviation advisors to assess, train, advise, and
assist a foreign nation with aviation capability, thereby facilitating the availability,
reliability, safety, and interoperability of these forces. Additionally, AFSOF ST
teams enhance air-to-ground interface by synchronizing conventional and special
operations during COIN operations. There is one active AFID squadron.

h. Special Operations Weather Teams (SOWTs). SOWTs collect tactical
forward weather observations in direct support of CF/SOF maneuver and as part
of the air-to-ground interface. They provide high fidelity observations to CF/SOF
assault, MEDEVAC, and ISR platforms. These forward observations are often
the only surface weather intelligence from within an operational area or on an
objective. SOWT conduct environmental reconnaissance in support of CF/SOF
maneuver and OE SA in the form of riverine, avalanche, geographic, and littoral
collection and assessments. These collections and assessments can also be

FM 6-03.05

MCWP 3-36.1

NTTP 3-05.19

AFTTP 3-2.73

USSOCOM Pub 3-33 v.3

102

17 March 2010

used for CA flood threat, humanitarian assistance activities, and engineering
bridge construction. SOWT establish nonstandard weather collection networks
from SOF, indigenous sources, and weather sensors to increase CF/SOF
surface weather data intelligence collections from denied, hostile, or politically
sensitive areas of operation in support of CF/SOF maneuver and OE SA.

i. UAS. AFSOC employs their own MQ-1 Predator and MQ-9 Reaper that are
employed similar to conventional Air Force (CAF) MQ-1s and MQ-9s, the
exception that the AFSOC crews have specialized and focused training for
supporting SOF ground teams. The main function of these two platforms is SOF
ISR. In addition, the Predator and Reaper can provide armed reconnaissance,
CAS, precision strike, and C2 relay. The MQ-9 is designed to carry a larger
payload than the MQ-1, with a variety of weapons.

6. Marine Special Operations Forces Operational Elements

a. Marine Corps special operations forces (MARSOF) include a headquarters,
Marine Special Operations Command (MARSOC), and three subordinate
elements: a Marine special operations regiment with three subordinate Marine
special operations battalions, a Marine special operations support group
(MSOSG), and a Marine special operations school (MSOS). MARSOC’s core
tasks include DA, SR, FID, and CT. Figure 26 outlines the MARSOC command
structure.

FM 6-03.05 / MCWP 3-36.1 / NTTP 3-05.19 / AFTTP 3-2.73 /

USSOCOM Pub 3-33 v.3

17 March 2010

103

Figure 26. MARSOC Command Structure

b. The MSOB is a deployable SOTF-level command with a capability to augment
a JSOTF. Core tasks include SR, DA, and FID and their primary role is to—

(1) Provide C2, basic staff functions, and training for Marine Special

Operations Companies (MSOC) or Marine Special Operations Teams
(MSOT).

(2) Command element provides C2 capacity and special equipment support,

intelligence and fire support.

c. The MSOC is the primary deploying element. Each company has four teams.
The company and teams are augmented with additional specialized personnel in
the fields of intelligence, signal, fire support, EOD, parachute rigger, etc. Figure
27 outlines the MSOC structure.

FM 6-03.05 / MCWP 3-36.1 / NTTP 3-05.19 / AFTTP 3-2.73 /

USSOCOM Pub 3-33 v.3

17 March 2010

105

Appendix B

CF/SOF Unit Coordination Checklist

1. Unit Brief

a. Task organization. Identify key personnel (conventional force/special
operations force counterparts).

b. Unit mission and key tasks.

c. Unique operational capabilities and limitations.

d. C2, communications, computers, and intelligence systems.

(1) Communications methods and contact procedures (PACE).
(2) Conventional force/special operations force C2 systems.
(3) Systems I&I and known shortfalls.

e. Mission coordination process.

(1) Conventional force coordination process.
(2) Special operations force CONOPS coordination/approval process.

f. Status of current operations.

2. Coordination

a. Review initial supporting and supported relationship.

(1) Operations.
(2) Fires.
(3) Logistics.

b. Review ROE.

c. Synchronize battle rhythms.

(1) Battle staff changeover, schedule video teleconferences, communication

checks, rehearsals, etc.

(2) Required reports and formats.
(3) Time, location, and purpose of meetings.

d. Establish liaison requirements and qualifications.

(1) Establish level of special operations forces liaisons (SOCCE, SFLE,

SOLE).

(2) Establish level of CF liaisons.
(3) Roles.

e. Advise and provide real-time information on unit status, capabilities, and
limitations.

(1) Actively participate in planning, briefing, and execution.

FM 6-03.05

MCWP 3-36.1

NTTP 3-05.19

AFTTP 3-2.73

USSOCOM Pub 3-33 v.3

106

17 March 2010

(2) Coordinate current operations and future plans for both CF/SOF.
(3) Monitor the operations.

f. Emergency link-up plan and contact procedures.

g. QRF coordination and POC.

h. CASEVAC.

i. Coordinate chain of custody procedures.

FM 6-03.05 / MCWP 3-36.1 / NTTP 3-05.19 / AFTTP 3-2.73 /

USSOCOM Pub 3-33 v.3

17 March 2010

107

Appendix C

Mission Planning and Execution Checklist

(CF/SOF Integrated Missions)

This checklist is used for CF/SOF integrated missions.

1. Planning

a. Commander’s initial considerations—

(1) OE area evaluation and preparation.

(a) Identify CF/SOF unit locations, boundaries, and receive graphics.
(b) Identify significant current operations.

(2) Synchronize CF/SOF timelines.
(3) CF/SOF coordination, liaison requirements, and resources.
(4) Command relationships. Consider formal supporting and supported

relationships.

(5) End state.

(a) Ensure mutual understanding.
(b) Leverage CF/SOF capabilities.

b. Mission analysis—

(1) Tasks and priorities.

(a) Synchronize CF/SOF plans and actions.
(b) Identify and leverage CF/SOF supporting tasks (specified and implied;

e.g., SOF operating in CF area of responsibility [AOR]).

(2) Intelligence and cyberspace operations.

(a) IPOE/IPB/and Cyber Intelligence Preparation of the Environment

(CIPE).

•

Integrate CF/SOF intelligence information and estimates.

•

Include CF/SOF in targeting meetings.

(b) Intelligence fusion with friendly forces’ unique capabilities.
(c) Fuse CF intelligence with SOF’s unique capabilities.
(d) Integrate counterintelligence and defensive cyber capabilities to protect

friendly networks and information systems from exploitation.

(e) Synchronize offensive cyber operations with lethal and nonlethal

operations.

(3) Command and control.

(a) Command relationships formally defined.
(b) Integrate and disseminate friendly force positions.
(c) Integrate C2 systems requirements.
(d) Synchronize OE geometry (unit locations, boundaries, air space

coordination, radio frequencies, and communication networks
coordination, etc.).

(4) Staff estimates.

(a) Available CF/SOF assets (personnel and equipment).

FM 6-03.05

MCWP 3-36.1

NTTP 3-05.19

AFTTP 3-2.73

USSOCOM Pub 3-33 v.3

108

17 March 2010

(b) Liaison requirements.
(c) CF/SOF restraints and constraints.
(d) Cross-domain CCIRs, requests for information, assumptions.

(5) Synchronize CF/SOF planning and execution timelines.
(6) Risk assessment. Assess CF/SOF risk and effect of subsequent orders.
(7) Mission statement. Consider CF/SOF integration and reference who, what,

where, when, and why, as relates to CF/SOF.

(8) Warning order (WARNORD). Ensure common understanding.

c. COA development and scheme of maneuver—

(1) C2.

(a) Formally define command relationships.
(b) Integrate and disseminate FFT tracks.
(c) Consider C2 systems integration requirements.
(d) Coordinate OE geometry (unit locations, boundaries, air space, radio

frequencies, and communications networks, etc.).

(e) Deconflict CF/SOF planning and execution timelines.
(f) Identify CF/SOF restraints and constraints.
(g) Identify LNO requirements.
(h) Cross check all commanders CCIR, requests for information (RFI), and

assumptions.

(i) Develop initial COAs.

•

Understand CF/SOF capabilities, limitations, and requirements of

available units.

•

Consider joint fire support.

(j) Consider asymmetric and synergistic effects of cyber operations as

independent or enabling function.

(k) Deconflict cyber with lethal and other nonlethal operations.

(2) Array initial forces.

(a) Include CF/SOF in the initial array of forces.

•

Clearly define scope of C2 relationships and ensure that both

CF/SOF understand each other’s roles and responsibilities.

•

Identify the role of the supporting force to the supported commander

(i.e., QRFs, security detachments, etc.).

d. COA analysis, war gaming, and approval—

(1) Conduct COA war-game. Include CF/SOF component liaisons.
(2) Refine staff estimates. Integrate CF/SOF staff estimates.
(3) Refine IPOE/IPB products. Ensure timely CF/SOF intelligence updates.
(4) Define or update task organization. Update CF/SOF tasks, requirements,

command support relationships, and graphics and C2 system
requirements.

FM 6-03.05 / MCWP 3-36.1 / NTTP 3-05.19 / AFTTP 3-2.73 /

USSOCOM Pub 3-33 v.3

17 March 2010

109

e. Orders production (CONOPS or who, what, when, where, and why [5Ws]
development): CF/SOF crosstalk.

(a) Employ SOPs and formatted templates, when applicable.
(b) Include CF/SOF tasks.
(c) Deconflict CF/SOF timeline requirements and battle rhythms.

f. Rehearsal:

(1) Synchronize SOPs, scheme of maneuver, link-up, operations, actions,

contingencies, and emergencies.

(2) Systems compatibility check and communications rehearsal.

(a) Ensure CF/SOF compatibility.
(b) Coordinate redundant systems and methods.

(3) Task organize. Confirm or adjust task organization and unit status for

CF/SOF, as required.

(4) Refine IPOE/IPB products. Ensure timely CF/SOF intelligence updates.

2. Execution

a. Maintain information flow across CF/SOF.

b. Leverage interoperable C2 systems, consider joint fire support, review priority
of fires, etc.

(1) Battle tracking (SITREPs, POSREPs, execution checklists, maneuver).
(2) COP management.

(a) FFT and/or RFT.

•

Update blue and red picture.

•

Update track filters.

•

Redundant and correlated tracking.

(b) FSCMs, MCMs.

(3) Intelligence updates.

(a) BDA.
(b) SITREPs and INTSUMs.
(c) Sensitive site exploitation.

(4) Operational assessment.
(5) Fire support.
(6) Collaboration and coordination.
(7) Follow-on actions and future operations.

c. Conduct AARs.

FM 6-03.05 / MCWP 3-36.1 / NTTP 3-05.19 / AFTTP 3-2.73 /

USSOCOM Pub 3-33 v.3

17 March 2010

111

Appendix D

Joint Fire Support Checklist

This checklist highlights joint fire support considerations. Joint fire support is the
synergistic product of three subsystems: (1) command and control, (2) target
acquisition, and (3) attack resources. These subsystems inevitably cross the
boundaries of CF/SOF, and must be properly planned and executed to prevent
fratricide and duplication, while still supporting operational momentum,
maintaining the initiative, and conducting maneuver.

1. Deliberate Fire Support Planning

a. Establish mission requirements.

(1) Review the commander’s intent as applied to joint fire support planning

(e.g., ROE, timing, effects, risk).

(2) Understand CF/SOF command and/or support relationships with

commander’s intent.

(3) Identify and coordinate CF/SOF capabilities and limitations.

(a) Fire support assets available (air, surface fires, naval).
(b) Target visualization.
(c) Target designation and handoff.
(d) Fire request and target control procedures.
(e) Consider communication requirements (e.g., digital, voice).

(4) Leverage mutually supporting effects.

(a) Lethal.
(b) Nonlethal (e.g., combat assessment, PSYOP, IO).

(5) Coordinate and deconflict targeting priorities.
(6) Determine requirements for input to the joint targeting cycle.
(7) Consider the ATO/integrated tasking order cycle, and clarify processes for

dynamic retasking of air support.

(8) Understand airspace deconfliction procedures.
(9) Standardize map datum.

b. Joint fire support planning.

(1) Review IPOE/IPB.
(2) Develop a common fire support database and ensure that common

software versions are employed on all C2, communications, computers,
and intelligence systems.

(3) Establish OE geometry.

(a) Identify ZORs.
(b) Develop FSCMs.
(c) Airspace deconfliction.

•

Plan within time requirements.

•

Review Service process.

FM 6-03.05

MCWP 3-36.1

NTTP 3-05.19

AFTTP 3-2.73

USSOCOM Pub 3-33 v.3

112

17 March 2010

c. Commander’s guidance for fires.

(1) Availability of joint fire support resources, including field artillery, CAS

(fixed and rotary-wing aircraft), naval surface fire support, SOF, IO,
intelligence, and surveillance assets.

(2) Probable enemy fires plan.
(3) Enemy fires capability.
(4) Consumption factors (type and quantity), positioning requirements, and

priority of logistic support.

(5) Critical decision points.
(6) Attack guidance matrix.
(7) High-payoff target list.
(8) Coordinate and deconflict approval of fires.

d. Targeting.

(1) Review target development process.
(2) Leverage collaboration capabilities.
(3) Review time-sensitive targeting process.
(4) Coordinate immediate requests for fires procedures (quick-fire channels).
(5) Consider constraints and restraints.
(6) Collateral damage assessments (CDAs) and considerations.
(7) Counter-battery analysis. Establish counter-battery attack and

deconfliction procedures.

(8) Review battle rhythm requirements.

(a) Target updates.

•

Target nominations.

•

Restricted targets.

(b) FSCM updates.

(9) Integrate CF/SOF targeting input. Prevent duplication.
(10) Consider sustainment requirements of supporting/supported forces.
(11) Fratricide prevention.

e. CF/SOF systems integration.

(1) Joint fire support C2, communications, computers, and intelligence system

requirements.
(a) Coordinate employment of effects management tool or joint automated

deep operation coordination systems to enhance SA of maneuver and
fires pictures.

(b) Coordinate special operations force input to AFATDS. Voice or digital.
(c) Verify status of FSCMs (permissive and restrictive coordination

measures).

(d) Ensure appropriate command support relationship.
(e) Ensure development of unit OE geometry, overlays, and required

tracks to support scheme of maneuver.

FM 6-03.05 / MCWP 3-36.1 / NTTP 3-05.19 / AFTTP 3-2.73 /

USSOCOM Pub 3-33 v.3

17 March 2010

113

•

Naming conventions (e.g., C2PC overlays, geometries).

•

Target block numbers.

f. Intelligence.

(1) ISR asset availability, coordination, dissemination (organic, theater,

national).

(2) Share intelligence reports and summaries. BDA.

g. Orders production (CF/SOF crosstalk).

2. Immediate Fire Support Planning

a. Primary, alternate, contingency, emergency (PACE) communications plan.

b. Joint fires network communications.

c. Quick-fires channels.

d. Establish pre-planned targets.

e. Pre-cleared fires (kill-boxes, engagement zones, free-fire areas).

f. Clearance of fires process.

3. Execution

a. Battle tracking.

b. PACE communications plan.

c. Clearance of fires process.

d. Blue force SA.

e. Fratricide prevention.

(1) Fusing fires and blue force pictures.
(2) CDE.

f. FSCM management.

(1) Consider the responsible agency for FSCM updates and dissemination.
(2) Establish process to create and manage follow-on FSCMs.

g. BDA sharing.

FM 6-03.05 / MCWP 3-36.1 / NTTP 3-05.19 / AFTTP 3-2.73 /

USSOCOM Pub 3-33 v.3

17 March 2010

115

Appendix E

Liaison Checklist

1. Establish liaison requirements and qualifications.

2. Establish liaison roles.

a. Advise and provide real-time information on unit status, capabilities, and
limitations.

b. Actively participate in planning, briefing, and execution.

c. Coordinate current operations and future plans for both CF/SOF.

d. Monitor operations.

3. Planning.

a. Commander’s initial considerations.

b. Mission analysis.

c. Intelligence.

d. COA development and scheme of maneuver.

e. Conduct COA war-game.

f. Refine staff estimates.

g. Define or update task organization.

h. Issue the WARNORD.

i. Orders production.

j. Rehearsal.

k. Synchronize SOPs and scheme of maneuver.

l. Systems compatibility check and communications rehearsal.

m. Task organize.

4. Execution.

a. Maintain cross-domain information flow and liaison participation.

b. Battle tracking (SITREPs, POSREPs, execution checklists, maneuver). COP
management.

(a) Casualty evacuation.
(b) Quick response force.

FM 6-03.05

MCWP 3-36.1

NTTP 3-05.19

AFTTP 3-2.73

USSOCOM Pub 3-33 v.3

116

17 March 2010

5. Joint Fires.

a. Exchange liaisons and establish contact with other liaison and control
elements from the various CF/SOF headquarters.

b. Liaison responsibilities.

(1) Understand CF/SOF communication requirements for fires.
(2) Understand joint fire support capabilities of CF/SOF.
(3) Understand CF/SOF fire support plans.
(4) Understand CF/SOF joint targeting cycle.
(5) Terminology and SOPs for joint fire support assets.
(6) Synchronize battle rhythms.
(7) Assist in the integration CF/SOF SA requirements.

6. Communications.

a. CF/SOF points of contact.

b. Terminology and SOPs.

c. Understand CF/SOF communication plans.

d. Request communication plan updates and provide feedback based on
CF/SOF requirements.

e. Request communication architecture and topology updates, and provide
feedback.

f. Battle rhythms.

g. Facilitate integration of CF/SOF SA (COP).

(1) Systems support.
(2) FFT (units, platforms, FSCMs, MCMs).

h. Intelligence.

FM 6-03.05 / MCWP 3-36.1 / NTTP 3-05.19 / AFTTP 3-2.73 /

USSOCOM Pub 3-33 v.3

17 March 2010

117

Appendix F

Communications Checklist

1. Review the CEOI.

a. CF/SOF units should review and coordinate assignments and procedures.

b. Frequency and spectrum management (joint restricted frequency listing).

c. Call signs, cryptography, changeovers, and / or compromise.

d. PACE.

2. Communications architecture.

List available CF/SOF systems and the capability of those systems to
communicate with each other.

a. Voice.

(1) Telecommunications.
(2) Radios: ultra high frequency (UHF), very high frequency (VHF), high

frequency (HF), extremely high frequency (EHF), satellite communications
(SATCOM).

(3) Classification (covered, uncovered).
(4) Frequency hopping.

b. Data systems.

(1) Bandwidth (64Kbs, 128Kbs, T1, E1).
(2) Classification: Nonsecure Internet Protocol Router Network (NIPRNET),

SECRET Internet Protocol Network (SIPRNET), Joint Worldwide
Intelligence Communication System (JWICS).

(3) Cryptography.

c. COP architecture.

(1) FFT (units, platforms, FSCMs, MCMs).
(2) Intelligence.

3. Network laydown (topology).

a. Physical location of units and distances.

b. Wired (local area network [LAN]).

c. Wireless (radio, SATCOM).

4. Liaison (see the liaison section of this checklist).

5. Order production (local) and document review.

a. CEOI.

FM 6-03.05

MCWP 3-36.1

NTTP 3-05.19

AFTTP 3-2.73

USSOCOM Pub 3-33 v.3

118

17 March 2010

b. Annex K, Command Information System of the CEOI.

c. SPINS, ATO, ACO.

6. Situational awareness and/or joint operational systems.

a. Environmental impacts (local populace, electronic media, television, radio, cell
phone).

(1) Interference.
(2) Degradation.
(3) Coalition systems.
(4) Other government agencies (OGAs).

b. Interoperability and communications (CF/SOF coordination).

7. Endnotes

a. The CEOI can be obtained from the J-6 communications section.

b. The SPINS can be obtained from the tactical operations center air liaison
officer in the fires and effects coordination center.

FM 6-03.05 / MCWP 3-36.1 / NTTP 3-05.19 / AFTTP 3-2.73 /

USSOCOM Pub 3-33 v.3

17 March 2010

119

Appendix G

SOF Detachment/Platoon Reception and Integration Checklist for CF

This checklist is intended for use by CF when receiving a small SOF unit, (e.g.,
SFODA, SEAL platoon (PLT), MARSOC PLT). Conversely, the SOF unit can
use it as a guide to prepare an indoctrination/information brief to the receiving CF
unit commander and staff.

1. Composition of the SOF element received.

a. Personnel and role of specific personnel.

b. Vehicles.

c. Special equipment.

d. Capabilities.

e. Additions of other government agency personnel to SOF element package.

2. Operations and intelligence brief of new OE.

a. Friendly situation.

b. Enemy situation.

c. Sources and leads.

d. Target folders.

e. Key personalities in OE.

f. Security force partners.

g. Key relationships and spheres of influence.

3. Mission of the SOF.

Under the mission of the SOF element given by the AOB/SOTF/CJSOTF.

4. Operational concerns of the SOF element.

a. Graphics, maps, imagery.

b. COP.

c. Reporting procedures.

d. Information transfer requirements (updates and meetings).

e. Targeting.

FM 6-03.05

MCWP 3-36.1

NTTP 3-05.19

AFTTP 3-2.73

USSOCOM Pub 3-33 v.3

120

17 March 2010

f. Command and support relationship.

g. Directed key tasks from SOF’s higher headquarters.

h. Implied tasks.

i. Desired end state at conclusion of SOF’s deployment.

5. Operational concerns for CF.

a. Graphics, maps, and imagery.

b. COP.

c. Reporting procedures.

d. Information transfer requirements (updates and meetings).

e. Targeting.

f. Directed key tasks from regiment/squadron.

g. Implied tasks.

h. Desired end state at conclusion of squadron/troop deployment.

6. Safe-house operations.

Understand safe-house operations requirements (if not collocated on forward
operating base).

a. Location.

b. Marking method.

c. Logistics supply plan.

d. Force protection plan.

e. QRF.

f. Fires.

g. Ammunition storage and resupply.

7. Define relationships and responsibilities.

Clearly define relationships and responsibilities between military transition team,
border patrol transition team, special police training team, SOF element, CF, and
local indigenous security forces.

a. Training.

FM 6-03.05 / MCWP 3-36.1 / NTTP 3-05.19 / AFTTP 3-2.73 /

USSOCOM Pub 3-33 v.3

17 March 2010

121

b. Personnel.

c. Intelligence.

d. Operations.

e. Logistics.

f. Local security forces staff trainers.

g. C2 of local security forces.

8. Training area requirements (during FID missions).

a. Ranges.

b. Urban warfare training.

c. Maneuver areas (if with mounted or mechanized indigenous forces).

9. Plan for vehicle maintenance and logistics.

a. Plan for maintenance of classes of supply.

b. Squadron or troops must be prepared to enter SOF vehicles into unit level
logistics system-ground and possibly build prescribed load list from these
additions.

10. Operations and employment agreement.

a. CF/SOF must understand that operations necessitate coordination
beforehand.

b. Current partnership guidance for combined or joint operations.

c. C2 relationship during combined or joint operations.

11. Marking methods.

a. Personnel.

b. Vehicle.

12. QRF requirements.

a. CF requirement in order to provide QRF for SOF operations.

b. Size of QRF.

c. Location of QRF.

d. Response time.

FM 6-03.05

MCWP 3-36.1

NTTP 3-05.19

AFTTP 3-2.73

USSOCOM Pub 3-33 v.3

122

17 March 2010

e. Call signs.

13. Signal instructions.

a. Call signs.

b. Net identification.

c. Primary, alternate, contingency, emergency.

14. Additional requirements and concerns.

FM 6-03.05 / MCWP 3-36.1 / NTTP 3-05.19 / AFTTP 3-2.73 /

USSOCOM Pub 3-33 v.3

17 March 2010

123

Appendix H

Quick Reference Checklist

This quick reference checklist (QRC) is organized by the warfighting functions.
The QRC streamlines the military decision-making process (MDMP) and the
rapid decision-making and synchronization process (RDSP). The QRC provides
a reference for deliberate planning when time is a constraint.

1. Intelligence

a. Identify your commander’s/unit’s PIRs for mission support, which should
include, but will not be limited to—

(1) Effects of weather and terrain on the current operation, as required.
(2) Known or template enemy positions within the OE.
(3) Enemy COAs or indications of unexpected enemy action or preparation.
(4) Threats or reactions from within civilian populace, including effect of

refugees on friendly operations.

(5) Structural details of points of interest
(6) HPTs/HVTs located in the AO.
(7) Pattern of life information and relationships of HVIs.

b. Be familiar with units and the AOs lessons learned and use those to amplify
your intelligence requirements.

c. Identify NAIs/TAIs locations to maximize intelligence coverage and avoid
duplication of effort.

d. Coordinate specific information requirements/PIRs encountered or answered
during execution of operation, or modified as appropriate.

e. Report BDA results to OE owner.

f. Fuse data when available and provide or be specific about your fused products
needs.

g. Understand the differences between CF/SOF operational requirements and
build a relationship with counterparts in the different communities to enable
synchronization. Planning considerations will differ between CF/SOF, but to be
successful those differences must be understood and accepted.

h. Understand the difference between CF/SOF site exploitation equipment and
capabilities.

2. Movement and Maneuver.

a. Exchange LNOs.

b. Identify the GFC's intent for the operation.

FM 6-03.05

MCWP 3-36.1

NTTP 3-05.19

AFTTP 3-2.73

USSOCOM Pub 3-33 v.3

124

17 March 2010

c. Complete coordination with OE owner for approval to operate in OE,
availability of a QRF, frequencies and call signs, MEDEVAC procedures (if
different from theater), and who will take detainees/EPWs/interrogation of
prisoners of war (IPW).

d. Identify/disseminate the EXCHECK.

e. Assign tasks, purpose, triggers, and objectives to subordinate units, as
appropriate.

f. Coordinate insertion of manned surveillance teams.

g. Assign priorities of planning for QRF.

h. Coordinate for EPWs or detainees, enemy command posts, or supply points
discovered.

i. Modify ACMs and MCMs.

j. Disseminate applicable friendly force information requirements (FFIRs) to
subordinate units.

k. Consider potential collateral effects to civilian infrastructure affecting friendly
mobility.

l. Refine the ISR plan and asset allocation.

m. Identify cross boundary considerations.

n. Adjust OE geometry (boundaries, restricted operations zones [ROZ], no-fire
areas [NFA], etc.), or addition of joint special operation area (JSOA).

o. Consider emplacement or clearance of obstacles required during mission
execution.

p. Identify PACE routes to and from the AO.

3. Fires.

a. Identify and synchronize desired operational effects (lethal and nonlethal).

b. Identify specified/implied tasks. Translate capabilities, limitations, constraints,
and restrictions of both CF/SOF assets.

c. Review protected target recommendations with fire support coordinator.

d. Review and coordinate HPT/HVT attack guidance matrix.

FM 6-03.05 / MCWP 3-36.1 / NTTP 3-05.19 / AFTTP 3-2.73 /

USSOCOM Pub 3-33 v.3

17 March 2010

125

e. Identify and update available fire (lethal and nonlethal) support for operation,
both organic and nonorganic (from CF/SOF joint fires element [JFE]/fire support
element [FSE]/fires effects coordination cell [FECC]) assets.

f. Identify and coordinate nonlethal fire support requirements.

(1) Psychological operations (PYSOP).
(2) Information operations (IO).
(3) Electronic warfare (EW).
(4) Operations security (OPSEC).
(5) Military deception (MILDEC).
(6) Computer network operations (CNO).
(7) Space control.
(8) Austere weather operations (AWO).

g. Consider civil-military operations (CMO) employment and tasks.

h. Review and coordinate requirements to the ATO cycle. Determine whether
request is immediate (less than 72 hours) or preplanned (more than 72 hours).
Submit air strike request.

i. Identify, coordinate, and modify FSCMs.

j. Ensure proper management of airspace.

k. Identify and coordinate planned fires and counter-battery operations.

(1) Identify and modify radar zones in support of the operation.
(2) Consider repositioning of firing units/systems.

l. Identify and plan for the employment of nonorganic aviation assets or UASs.

m. Synchronize basic battle tracking of friendly units, priority of fires, triggers,
FSCM/ACM, surface to air threats.

n. Identify and coordinate quick fire channels and clearance of fires procedures.

o. Execute and assess fires.

p. Conduct BDA.

4. Sustainment.

a. General.

(1) Establish and distribute resupply procedures (requisition, receive, issue)

and locations.

(2) Establish days of supplies required to accompany troops.
(3) Plan provisions for logistics support of displaced civilians, prisoners of war,

and indigenous personnel.

FM 6-03.05

MCWP 3-36.1

NTTP 3-05.19

AFTTP 3-2.73

USSOCOM Pub 3-33 v.3

126

17 March 2010

b. Special Item Considerations.

(1) Class I (Food and Water).

(a) Ration cycle by phase.
(b) Availability of potable water sources.
(c) Potable ice considerations.

(2) Class II (Expendable Items).

(a) Ensure logistics support element replenish organizational clothing and

individual equipment (OCIE).

(3) Class III (Petroleum, Oils, and Lubricants) [POL]).

(a) Location and capabilities of remote refueling sites or forward arming

and refueling points (FARPs).

(b) Unique package product requirements (POL, oil cans, etc.)

(4) Class IV (Building and Barrier Materials).

(a) Unique requirements for construction, security, and rehearsal

materials.

(b) Basic loads.
(c) Pre-positioned material stocks.

(5) Class V (Ammunition).

(a) Combat load.
(b) EOD support considerations.
(c) SOF peculiar ammunition and CF ammunition for resupply.
(d) Ammunition transfer holding point (ATHP) locations and resupply plan.

(6) Class VII (Major End Items).

(a) SOF peculiar equipment requirements.
(b) Equipment redistribution (cross-leveling) requirements.
(c) Replacement actions for salvage equipment.
(d) Availability of operational readiness floats.

(7) Class VIII (Medical Supplies).

(a) Logistics support plan complements the medical support plan.
(b) Special medical equipment and supply requirements identified.

(8) Class IX (Repair Parts).

(a) SOF peculiar repair parts.
(b) Common repair parts requirements (including repairables).
(c) Cannibalization procedures.

(9) Class X (all others).

(a) Source for Class X materials.
(b) Tailor maintenance contact team to the mission.

(10) Transportation.

(a) Expedited cargo distribution plan.
(b) Materials handling equipment (MHE) requirements.
(c) Weather impact on ports, airfields, and highway nets.
(d) HN support availability.
(e) Planned medical evacuation requirements.

FM 6-03.05 / MCWP 3-36.1 / NTTP 3-05.19 / AFTTP 3-2.73 /

USSOCOM Pub 3-33 v.3

17 March 2010

127

(11) Airfields.

(a) Airfields are available to support military operations.
(b) USAF mobile aero medical staging facilities.
(c) Personnel and cargo reception capabilities of the aerial point of

embarkation (APOE) and aerial point of debarkation (APOD).

(d) Characteristics and capabilities of the roads that access the airfield.
(e) Arrival/departure airfield control group (A/DACG) availability—identify

requirements for aerial port squadron and airlift control element.

(f) Airfield facilities available for military use during A/DACG operations.

(12) Supply Routes.

(a) Road movement and convoy restrictions.
(b) Available routes to support operations.
(c) Dimensions and classifications of tunnels and bridges along the routes.
(d) Segments of the routes heavily used by the civilian populace.
(e) Identify hazards/obstacles to lines of communications (LOC) (weather,

refugees, pilgrims) and contingency plans to mitigate.

(f) Traffic-control measures.
(g) Route security and IED procedures.

(13) Field Services.

(a) Mortuary affairs and graves registration capabilities.
(b) Procedures for salvage collection, evacuation, and disposal.
(c) Fire protection for aviation, ammunition, and bases.
(d) Aerial delivery.
(e) Shower and laundry.

(14) EOD support.

5. Command and Control

a. Identify the command relationships and duties and responsibilities of each
command.

b. Understand supporting and supported relationships.

c. LNOs: placement, duties, and responsibilities.

d. Understand the CONOPS and mission approval process.

e. Know CCIR (commander’s wakeup criteria).

f. Understand participating units’ asset capabilities, limitations, and restrictions.

g. Review all pertinent ROEs, international, and HN caveats.

h. Synchronize battle rhythms.

i. QRF coordination and POC.

j. CASEVAC procedures to lowest level.

FM 6-03.05

MCWP 3-36.1

NTTP 3-05.19

AFTTP 3-2.73

USSOCOM Pub 3-33 v.3

128

17 March 2010

k. Chain of custody procedures.

l. Procedures, rules, and regulations for handling detainees.

m. Determine COP. Determine input requirements and procedures to facilitate
future support.

n. Identify communication plan in accordance with PACE (QRF, OE owner,
medical evacuation quick-fires channels, and immediate CAS).

o. Identify reporting procedures, frequencies, and cryptography requirements.

6. Protection.

a. Identify CF in the area of operations that has capability to destroy, nullify, or
reduce the effectiveness of hostile air and missile threats.

b. Ensure CF/SOFs practice air defense passive measures.

c. Establish physical security measures.

d. Identify indicators of coordinated enemy actions against friendly forces along
required routes.

e. Plan and prepare for potential enemy use of CBRN weapons.

f. Ensure CF/SOF are given shots/meds and issued individual protective
equipment.

g. Ensure actions are taken to protect, monitor, analyze, detect, and respond to
unauthorized activity within DOD information systems and CNO.

h. Establish/review isolated PR contingency plan.

i. Establish antiterrorism measures and activities.

j. Identify high-risk personnel to safeguard.

k. Establish combat identification characterization for but not limited to, “friend,”
“enemy/hostile,” “neutral,” or “unknown.”

l. Ensure constant CF/SOF command information coordination.

m. Identify, assess and report CF/SOF hazardous exposures.

n. Monitor and report battle injury/disease to include combat and operational
stress reaction.

FM 6-03.05 / MCWP 3-36.1 / NTTP 3-05.19 / AFTTP 3-2.73 /

USSOCOM Pub 3-33 v.3

17 March 2010

129

REFERENCES

DEPARTMENT OF DEFENSE ISSUANCES

DODD 5100.3, Support of the Headquarters of Combatant and Subordinate Joint

Commands, 15 November 1999.

DODD 5100.73, The Department of Defense Instruction, 1 December 2007.

Available online at
http://www.dtic.mil/whs/directives/corres/pdf/510073p.pdf.

DODI 4000.19,

Interservice and Intragovernmental Support

, 9 August 1995.

JOINT PUBLICATIONS

CJCSI 3110.06C, (

S) Special Operations Supplemental to the Joint Strategic

Capabilities Play 2006 (U)

, 29 December 2006.

JP 1,

Doctrine for the Armed Forces of the United States

, 14 May 2007.

JP 1-02,

Department of Defense Dictionary of Military and Associated Terms

12 April 2001.

JP 2-0,

Joint Intelligence

, 22 June 2007.

JP 2-01,

Joint and National Intelligence Support to Military Operations

7 October 2004.

JP 3-0,

Joint Operations

, 17 September 2006.

JP 3-05,

Doctrine for Joint Special Operations

, 17 December 2003.

JP 3-05.1,

Joint Special Operations Task Force Operations

, 26 April 2007.

JP 3-09,

Joint Fire Support

, 13 November 2006.

JP 3-09.3,

Close Air Support

, 8 July 2009.

JP 3-13,

Information Operations,

13 February 2006.

JP 3-13.2,

Joint

Doctrine for Psychological Operations,

7 January 2010.

JP 3-14,

Space Operations

, 6 January 2009.

JP 3–30,

Command and Control for Joint Air Operations

, 12 January 2010.

JP 3-33,

Joint Task Force Headquarters

, 16 February 2007.

JP 3-40,

Combating Weapons of Mass Destruction,

10 June 2009.

JP 3-52,

Joint Doctrine for Airspace Control in a Combat Zone

, 30 August 2004.

JP 3-57,

Civil-Military Operations

, 8 July 2008.

JP 3-60,

Joint Targeting,

13 April 2007.

JP 4-0,

Joint Logistics

, 18 July 2008.

JP 5-0,

Joint Operations Planning

, 26 December 2006.

FM 6-03.05

MCWP 3-36.1

NTTP 3-05.19

AFTTP 3-2.73

USSOCOM Pub 3-33 v.3

130

17 March 2010

AIR FORCE PUBLICATIONS

AFDD 2-7,

Special Operations,

16 December 2005

AFI 33-360,

Publications and Forms Management

, 18 May 2006.

ARMY PUBLICATIONS

FM 3-05,

Army Special Operations Forces

, 20 September 2006.

FM 3-05.401,

Civil Affairs Tactics, Techniques, and Procedures,

5 July 2007.

MARINE CORPS PUBLICATIONS

MCWP 3-31.6,

Supporting Arms Coordination in Amphibious Operations

, May

2004.

NAVY PUBLICATIONS

NAVSUP P-409,

MILSTRIP/MILSTRAP Desk Guide

, 9 June 1998.

NWP 3-05,

Naval Special Warfare,

September 2009.

MULTI-SERVICE PUBLICATIONS

FM 3-09.32, MCRP 3-16.6A, NTTP 3-09.2, AFTTP(I) 3-2.6,

Multi-Service Tactics,

Techniques, and Procedures for the Joint Application of Firepower

20 December 2007.

FM 3-09.34, MCRP 3-25H, NTTP 3-09.2.1, AFTTP(I) 3-2.59,

Multi-Service

Tactics, Techniques, and Procedures for Kill Box Employment,

14 June 2005.

FM 3-52.1, AFTTP 3-2.78,

Multi-Service Tactics, Techniques, and Procedures for

Airspace Control,

22 May 2009.

FM 3-60.1, MCRP 3-16D, NTTP 3-60.1, AFTTP(I) 3-2.3,

Multi-Service Tactics,

Techniques, and Procedures for Targeting Time-Sensitive Targets

20 April 2004.

United States Code

Document available online at http://uscode.house.gov/download/title_10.shtml

10 USC Title 10, Armed Forces.

FM 6-03.05 / MCWP 3-36.1 / NTTP 3-05.19 / AFTTP 3-2.73 /

USSOCOM Pub 3-33 v.3

17 March 2010

131

GLOSSARY

PART I — ABBREVIATIONS AND ACRONYMS

A
AAR

after action review

ACCE

air component coordination element

ACM

airspace coordinating measure

ACO

airspace control order

A/DACG

arrival/departure airfield control group

ADC-O

assistant division commander for operations

ADOCS

Automated Deep Operations Coordination System

ADP

automated data processing

AFATDS

Advanced Field Artillery Tactical Data System

AFDD

Air Force Doctrine Document

AFI

Air Force Instruction

AFID

aviation foreign internal defense

AFFOR

Air Force forces

AFSOC

Air Force Special Operations Command

AFSOF

Air Force special operations forces

AFTTP

Air Force tactics, techniques, and procedures

AFTTP(I)

Air Force tactics, techniques, and procedures (interservice)

ALO

air liaison officer

ALSA

Air Land Sea Application (Center)

ANGLICO

air and naval gunfire liaison company

area of operations

AOB

advanced operations base

AOC

air operations center

AOR

area of responsibility

APOD

aerial port of debarkation

APOE

aerial port of embarkation

ARFOR

Army forces

ARSOF

Army special operations forces

ARSOC

Army special operations component

ARSTRAT

Army Forces Strategic Command

ASO

advanced special operations

ATACMS

Army Tactical Missile System

ATHP

ammunition transfer holding point

ATO

air tasking order

AWO

austere weather operations

FM 6-03.05

MCWP 3-36.1

NTTP 3-05.19

AFTTP 3-2.73

USSOCOM Pub 3-33 v.3

132

17 March 2010

B
BCT

brigade combat teams

BCD

battlefield coordination detachment

BDA

battle damage assessment

BFT

blue force tracker

battalion

BOLO

be on the lookout

C
C2

command and control

C4I

command, control, communications, computers, and
intelligence

C4ISR

command, control, communications, computers,
intelligence, surveillance, and reconnaissance

CBRN

chemical, biological, radiological, and nuclear

CDRTSOC

commander TSOC

CHOP

chief of operations

CJCSI

Chairman Joint Chiefs of Staff instruction

CNA

computer network attack

CND

computer network defense

combat support

CSS

combat service support

C2PC

command and control personal computer

civil affairs

CAC

Combined Arms Center

CADD

Combined Arms Doctrine Directorate

CAF

conventional Air Force

CAO

civil affairs operations

CAS

close air support

CASEVAC

casualty evacuation

CBRN

chemical, biological, radiological, and nuclear

CCA

close combat attack

CCIR

commander’s critical information requirement

CDA

collateral damage assessment

CDE

collateral damage estimation

CDRJSOTF

commander, joint special operations task force

CDRUSSOCOM

Commander, United States Special Operations Command

CEOI

communications-electronics operating instructions

conventional forces
[

is used for the term "conventional forces" in the context

of this publication only.]

Military reference books and manuals (2009-2023, Volume 2) - page 14