unclassified for educational purposes only · unclassified – for educational purposes only 1 ......

UNCLASSIFIED – FOR EDUCATIONAL PURPOSES ONLY

1 UNCLASSIFIED – FOR EDUCATIONAL PURPOSES ONLY

UNITED STATES MEDIATOR COMMAND KRANK NAS, LUNA

Copy Number ____________ HQ USMEDCOM Krank NAS, LUNA 09111 PLANNING DIRECTIVE FOR USMEDCOM CONPLAN 0995-20 REFERENCES: a. ( ) Unified Command Plan (UCP) b. ( ) Guidance for Employment of the Force (GEF) c. ( ) Joint Strategic Capabilities Plan (JSCP) d. ( ) Global Force Management Implementation Guidance (GFMIG)

1. ( ) Purpose. This Planning Directive identifies planning responsibilities for developing USMEDCOM CONPLAN 0995-20. It provides guidance and requirements to the HQ USMEDCOM staff and subordinate commands concerning coordinated planning actions for plan development. Only one course of action (COA) is proposed here. Additional COA(s) will be promulgated for review and assessment in subsequent staff guidance. 2. ( ) Mission a. ( ) Mission Statement ( ) When directed by the SecDef, Joint Task Force (JTF) Mercury will deter Jupiterian aggression in order to maintain regional stability. If deterrence fails, JTF Mercury will gain and maintain air superiority over the JOA; conduct counteroffensive operations in the eastern region of Mercury; and perform maritime surface, sub-surface, and amphibious operations in the Mercurian littorals and Sapphire Ocean international waters in order to provide air defense of all Mercurian territory, eject any Jupiterian force from Mercurian sovereign territory, and secure freedom of navigation in Mercurian territorial waters. b. ( ) End State ( ) The end state for this operation will include maintaining or reestablishing the sovereignty of Mercurian land and maritime borders and the ejection of all Jupiterian forces. Jupiter will no longer have military forces directly threatening Mercurian borders. Mercury will have sufficient military capability and support for proper indications and warning of any future aggression by Jupiter, and the ability to defend against any such aggression. The US military will work in concert with US and Mercurian government agencies and Mercurian military to build an enduring regional stability and balance of power. c. ( ) Military Objectives (1) ( ) Deploy US forces in theater to deter Jupiterian aggression toward Mercury and build forces for potential combat operations. If deterrence fails:



(2) ( ) Gain and maintain air and maritime superiority over the joint operating area (JOA). (3) ( ) Halt Jupiterian military force advance into Mercury short of the Pesca oil terminal. (4) ( ) Secure the eastern Mercurian governorates of Gammon, Minnoway, and Pesca. (5) ( ) Coerce or forcibly eject Jupiterian forces from Mercury. (6) ( ) Reestablish Mercurian territorial integrity and secure its borders. (7) ( ) Render Jupiterian military forces no longer an immediate threat to Mercury.

3. ( ) Commander’s Analysis a. ( ) Commander’s Intent ( ) The purpose of this operation is to deter Jupiter from attacking Mercury and, if deterrence fails, to defend Mercury and eject any Jupiterian forces and reestablish Mercurian sovereignty. The military end state will include secure Mercurian borders and territorial waters, and a Jupiter that no longer directly threatens Mercury. This should ultimately restore regional stability and order, and ensure a safe and secure Mercury. Should deterrence fail, US military forces must execute swiftly and decisively. Due to the limited capability of Mercurian military forces and limited warning of a potential Jupiterian attack, the deployment of immediately combat capable forces into the JOA will be critical. I am willing to accept risk in having limited ground force capability early on to ensure adequate air and maritime support to the Mercurian ground forces to halt the Jupiterian advance. Ensuring open and secure lines of communication for the duration of the operation will be a priority. Close coordination with Mercurian military and government must also be maintained throughout this operation to afford a smooth transition back to Mercurian military and civilian control. Our presence should not be cause for increased internal unrest, so collateral damage and other operational impacts on the Mercurian populace must be minimized. b. ( ) Adversary’s Intent ( ) Jupiter will likely execute one of the following COAs. Most Likely: COA one is to attack the eastern coastal areas in the direction of Gammon, Minnoway, and Pesca with a possible ultimate goal of threatening Salmonville. The second COA is to seize the Beagle Paw oil fields and limited territory further west. Most Dangerous: The most dangerous COA is for Jupiter to use WMD during a campaign of terror and intimidation to force Mercurian leaders to make territory and oil access concessions. Although Jupiter possesses chemical and biological weapons, it is less likely they would use them unless their regime was threatened. See USMEDCOM J-2 Estimate for detailed analysis of enemy capabilities and potential COAs. c. ( ) Mission Type Orders (1) ( ) Joint Force Land Component Commander (JFLCC). Secure lodgment in Mercury for follow-on forces and provide initial base security for Woodpecker airport,



Kingfisher AB, and Sandpiper AB in support of joint air operations. Build forces then continue operations to secure eastern Mercury, and repel and eject Jupiterian ground forces. Conduct stability operations to enable transition to Mercurian area control. (2) ( ) Joint Force Maritime Component Commander (JFMCC). Provide an initial deterrent force and ensure maritime superiority and freedom of navigation in the international waters of the JOA. Provide support to joint air operations--air superiority, air defense, air interdiction, and support the JFLCC scheme of maneuver. Maintain a robust amphibious capability for potential non-combatant evacuation operations (NEO) and/or forcible entry. (3) ( ) Joint Force Air Component Commander (JFACC). Provide an initial deterrent force and gain and maintain air superiority over the JOA. Conduct air operations to halt advancing Jupiterian forces and force a withdrawal from Mercurian territory. Support JFLCC and JFMCC schemes of maneuver and, as directed, support stability operations

and the redeployment of US forces. Also, perform role of Area Air Defense Commander. (4) ( ) Joint Force Special Operations Component Command (JFSOCC). Tasking to be provided under separate cover. 4. ( ) Assumptions a. ( ) Assumptions. The following assumptions are in addition to those in the GEF and JSCP Regional Planning Guidance. (1) ( ) The President will declare a National Emergency and invoke Partial Mobilization authority for call-up of Reserve forces. (2) ( ) Neutral nations will not intervene with direct military force in Mercury. (3) ( ) Mercurian government forces can successfully defend the western governorates from ground attack. (4) ( ) Mercurian civilian populace will support US forces. (5) ( ) The United States will have use of airfields and port facilities as outlined below. (6) ( ) Intelligence will receive at least 10 days of ambiguous warning and 5 days of unambiguous warning (W-day). For planning purposes, W+5 = C+0; C+5 = D+0. 5. ( ) Operational Limitations (Constraints and Restraints) (1) ( ) No offensive actions will be taken outside the Mercurian boundary without Presidential approval. (2) ( ) Freedom of navigation will not be exercised in the Tangy Straits without prior approval. (3) ( ) A buffer zone of 10 nautical miles will be established outside of Jupiter’s international land and sea boundaries.



(4) ( ) No attacks on hostile forces outside Mercurian land, sea, and air boundaries are authorized except in self-defense or with Presidential approval. 6. ( ) Forces a. ( ) Assigned Forces (1) ( ) Army (ARMED) (a) ( ) 1 - Division Headquarters Element, Joint Base Parrot, Pluto (b) ( ) 1 - Infantry Brigade Combat Team (BCT) (Airborne) (c) ( ) 1 - Heavy BCT (d) ( ) 1 - Battalion, Special Forces Group (2) ( ) Navy (NAVMED)

(a) ( ) 1 - Fleet Headquarters Element, Krank NAS, Luna (b) ( ) 1 - Carrier Strike Group (CSG) (c) ( ) 1 - Expeditionary Strike Group (ESG) – including MEU (SOC) (d) ( ) 1 - Patrol Squadron (VP) (e) ( ) 1 - Fleet Air Reconnaissance Squadron (VQ) (3) ( ) Air Forces (AFMED) (a) ( ) 1 - NAF Headquarters Element, Jonas Salk AB, Luna (b) ( ) 2 - Fighter/Attack Squadrons (c) ( ) 2 - Theater Airlift Squadrons (d) ( ) 1 - Rescue Squadron (e) ( ) 1 - Command and Control Squadron (f) ( ) 1 - Refueling Squadron b. ( ) Apportioned Forces. GFMIG apportioned forces.

1) ( ) Apportioned Army Forces (a) ( ) 2 – Infantry Brigade Combat Team (ICBT) (b) ( ) 1 – Combat Aviation Brigade (Heavy) (c) ( ) 2 – ADA Battalion (d) ( ) 1 – Armor Brigade Combat Team (e) ( ) 1 – Cavalry Regiment

2) ( ) Apportioned Navy Forces

(a) ( ) 3 – Attack Submarines (b) ( ) 4 – Frigates (c) ( ) 2 - Destroyers

3) ( ) Apportioned Marine Forces

(a) ( ) 2 – Infantry Regiments (d) ( ) 1 – Tank Battalion (c) ( ) 1 – Expeditionary Force Command Element (d) ( ) 1 – Fighter Attack Squadron (e) ( ) 1 – Light/Attack Helicopter Squadron



4) ( ) Apportioned Air Force Forces (a) ( ) 2 – Command and Control Squadrons (b) ( ) 2 – Bomber Squadrons (c) ( ) 5 – Fighter/Attack Squadrons (d) ( ) 2 – Intelligence, Surveillance, Reconnaissance Squadrons (e) ( ) 4 – Refueling Squadrons (f) ( ) 4 – Theater Airlift Squadrons

7. ( ) Proposed Course of Action a. ( ) Upon order from the SecDef, USMEDCOM ground, naval, and air forces will initiate action to build up air, maritime and land forces in the AOR to present the Jupiterian forces with the possibility of direct confrontation with US forces. Deployment will be made initially to locations outside of Mercury, with in-country redeployment to

follow once the area is secure. On order, air and naval forces will initiate action to provide air superiority over Mercury, protect Mercurian territorial waters, and defend US forces throughout the AOR. Beginning D-day, H-hour, the JTF will launch combined air and maritime operations to halt Jupiterian aggression and, if possible, eject all Jupiterian forces from Mercurian territory. NLT D+16, the JTF will launch a combined airborne and amphibious assault to secure Mercurian ports and airfields in preparation for force build-up and further operations. NLT D+24 ground forces, supported by air and maritime operations, will commence operations to secure the pipeline terminal at Pesca, then move south to eject Jupiterian forces from Mercurian territory and secure the Beagle Paw oil fields. b. ( ) Tentative Phasing. Phasing of the operation should support JSCP tasking, and follow and support the preliminary course of action presented above. (1) ( ) Upon unambiguous warning and when directed by the SecDef, initial build-up of theater forces will begin with air, space and naval forces on C+0 to deter Jupiterian aggression. (2) ( ) JFACC will be responsible for air defense, reconnaissance and surveillance over the JOA, to include the Mercurian landmass beginning C+0. (3) ( ) For planning purposes, D-day = C+5. JFACC and JFMCC will gain and maintain air and maritime superiority. JFACC and JFMCC will be ready to conduct operations to halt Jupiterian incursions, and prepare to assist US and Mercurian ground forces to shape the operational environment and eject Jupiterian forces. (4) ( ) Ground forces will conduct a combined airborne and amphibious assault on C+21 (D+16) to secure lodgment at Salmon Port and Woodpecker airfield by C+22 (D+17), then begin force buildup and preparation to conduct a ground counteroffensive by C+29 (D+24). (5) ( ) Supply buildup objective will be 5 days by C+15 and 30 days by C+30 for all supplies except Class III, which will be 3 days by C+15 and 10 days by C+30. (6) ( ) Anticipated minimum duration of combat operations is 90 days. c. ( ) This COA will be further developed and refined during the planning process.



d. ( ) Additional COA(s) will be promulgated for review and assessment in subsequent staff guidance. 8. ( ) Planning Guidance a. ( ) Nuclear and Chemical Defense Weapons. Nuclear weapons use is not anticipated for this operation; however, adversary use of chemical/biological weapons is unknown. Forces will deploy with appropriate equipment and be prepared to conduct operations in a chemical/biological hazardous environment. b. ( ) Basing Rights (1) ( ) Mercury:

(a) ( ) The only airfields authorized for basing US aviation forces are Kingfisher and Sandpiper. Emergency landings are approved for any Mercurian airfield. (b) ( ) No strategic Aerial Port of Debarkation (APOD) is available in Mercury. Should primary theater Service ports of support (POSs) become unserviceable, exceptions to this limitation will be handled on a case-by-case basis. (c) ( ) Fixed wing aircraft basing (all Services) ceiling in Mercury is 100. Overall US forces manpower ceiling within Mercury is 35,000. This does not include forces afloat. (2) ( ) Pluto: (a) ( ) Pluto will permit the use of the following airfields for logistic support and troop staging only: Cormorant, Egret, Loon NAS, Martin IAP (High Cowton), Joint Base Parrot, and Plover. (3) ( ) Neptune: (a) ( ) Neptune will permit unrestricted use (combat and support forces) of the following airfields on the island of Neptune: Condor, Eagle, Parakeet, Ringneck, and Vulture. (b) ( ) Buzzard NAS, on the island of Neptune, is restricted to logistic support and troop staging only for USAF. US Navy and Neptuni Air Forces (NAF) are authorized unrestricted use of Buzzard NAS. (4) ( ) Luna will permit the unrestricted use of the following airfields: Jonas Salk AB, Krank NAS, and Dogwood AB. (5) ( ) North Neptune, Saturn, and Vulca will not permit overflight or base usage. (6) ( ) Venus will not permit base usage. c. ( ) Mobility Resources



(1) ( ) Strategic lift will be apportioned IAW GEF/JSCP planning priorities and in coordination with USTRANSCOM planners. USMEDCOM is apportioned 2250 short tons of strategic airlift per day for this operation. Service-specific apportionment, along with strategic sealift apportionment will be detailed in subsequent USMEDCOM TPFDD LOI. Activation of CRAF Stage I and use of RRF sealift is to be anticipated. (2) ( ) Theater strategic lift Ports of Debarkation (PODs) will be organized around Service-specific ports of service (POSs). Service PODs will be: Army - Plover, Pluto; Navy - Buzzard NAS, Neptune; Air Force – Jonas Salk AB, Luna. Service logistics assets and theater airlift will be positioned to facilitate effective movement of forces and materiel (JRSO&I) from PODs to final destinations. (3) ( ) Theater airlift will be limited to assigned mobility assets until augmenting mobility forces arrive.

d. ( ) Agency and Coalition Support (1) ( ) US Agencies. All instruments of national power applied in close coordination will be required to effectively resolve this potential crisis. Department of State (DOS): Ambassador to Mercury is senior US authority for actions in country. NEO responsibility resides with DOS, DoD will be supporting. Coordinating basing and overflight rights will be critical to the implementation of this plan for support from coalition partners. USAID will be US lead for working with NGOs, IGOs to support any resulting refugee crisis. Other government agencies must also be integrated into the overall planning to ensure effective coordination and execution. A Joint Interagency Coordination Group (JIACG) will be established to implement this concept. (2) ( ) Except for Mercurian military forces, coalition support for this operation will be primarily in the form of basing, logistics, and administration support. Planners should not anticipate additional coalition combat forces to engage in counteroffensive or offensive operations. Coalition nations hosting US forces can be expected to provide air and missile defense for their sovereign airspace. Liaisons and close coordination will be necessary to ensure air and missile operations are executed safely. Mercurian forces are limited in number, capability, and interoperability compared to US forces. Liaisons will need to be exchanged between forces, but combat operations should be planned to de-conflict rather that integrate Mercurian military forces. e. ( ) Command and Control (1) ( ) CDRUSMEDCOM, at the direction of the SecDef, will establish JTF Mercury with HQ at Buzzard NAS, Neptune. The commander, JTF (CJTF) will be the supported commander for this operation. Forces allocated for execution will be attached to USMEDCOM and placed under operational control (OPCON) (by exception) of the CJTF. USTRANSCOM, USSTRATCOM, USPACOM, USEUCOM, AND USSOCOM are supporting commands. (2) ( ) The CJTF will establish Service component commands, commanded by the senior Service officer eligible for command. Attached/assigned Service forces will be attached and delegated OPCON (or as specified) to the respective Service Component Commander. The following Service components will be established: Army Forces (ARFOR), Navy Forces (NAVFOR), and Air Force Forces (AFFOR). Assigned Marine Corps forces (MEU) will initially be OPCON to the COMNAVFOR while afloat. Once ashore, they



will be delegated tactical control (TACON) to the JFLCC. When augmenting Marine Corps forces arrive, a Marine Corps Forces (MARFOR) component will be established with delegated OPCON of assigned/attached Marine Corps forces. (3) ( ) The CJTF will also establish the following functional component commands to be commanded (dual-hatted) by the indicated Service component commanders: JFLCC - COMARFOR; JFMCC - COMNAVFOR; JFACC - COMAFFOR. Functional component commanders will be delegated TACON of those forces made available for tasking. (4) ( ) Special Operations Forces (SOF) will be organized under a JFSOCC with OPCON of all attached SOF forces. 9. ( ) Planning Tasks a. ( ) All Addressees. Review and provide comments and analysis of taskings,

assumptions, and other planning guidance. b. ( ) USMEDCOM Staff (1) ( ) Prepare functional staff estimates to serve as the basis for evaluation of operational objectives, preliminary course of action and concept of operations. (2) ( ) Provide an overview of respective functional capabilities and requirements to support the plan; known shortfalls, limitations, or problem areas; assessment of apportioned augmentation forces from CONUS; and comparison of courses of action. (3) ( ) Staff Taskings (a) ( ) J-1 will provide functional inputs for the Commander’s Estimate (b) ( ) J-2 will: 1. ( ) Evaluate current intelligence data to assess the threat--enemy order of battle, centers of gravity, and courses of action. Evaluate friendly force order of battle, centers of gravity, and courses of action. 2. ( ) Provide functional inputs for the Commander’s Estimate. (c) ( ) J-3 will: 1. ( ) Define the mission and analyze strategic objectives. 2. ( ) Analyze the situation in relation to forces required and available, operational limitations (constraints/restraints), and rules of engagement. 3. ( ) Develop and coordinate possible courses of action with components and supporting organizations. 4. ( ) Coordinate functional inputs and have overall responsibility for preparation of the Commander’s Estimate. 5. ( ) Identify specific forces for deployment and required delivery dates.



(d) ( ) J-4 will: 1. ( ) Coordinate, with the Service components, the establishment of seaports and airfields for use as Service POSs. 2. ( ) Identify and coordinate the beddown of forces with J-3. 3. ( ) Identify required/desired host nation support. 4. ( ) Establish, with USTRANSCOM support, a Joint Deployment and Distribution Operations Center (JDDOC) to coordinate theater/strategic lift requirements and execution. 5. ( ) Provide functional inputs for the Commander’s Estimate.

6. ( ) Analyze strategic lift requirements and capability. (e) ( ) J-5 will: 1. ( ) Lead the Joint Planning Group (JPG) and provide oversight and review of all staff planning functions 2. ( ) Have overall responsibility for completion/staffing/approval of this plan. (f) ( ) J-6 will provide functional inputs for the Commander’s Estimate. c. ( ) Supporting Component Commands (1) ( ) Functional Components (a) ( ) Provide functional inputs for preparation of the Commander’s Estimate. (b) ( ) At the Intermediate Planning Conference, provide analysis of the proposed concept of operations, to include: 1. ( ) Concepts and input for component achievement of plan objectives/tasks. 2. ( ) Assessment of force requirements and sufficiency of assigned and apportioned forces. 3. ( ) Estimated time phasing of achievement of operational objectives. (c) ( ) Write supporting plans and submit for approval to this headquarters. (2) ( ) Service Components (a) ( ) Provide Service inputs for preparation of the Commander’s Estimate. (b) ( ) At the Intermediate Planning Conference, provide analysis of the proposed concept of operations, to include:



1. ( ) Assessment of Service force capabilities and best employment methods. 2. ( ) The proposed beddown of all Service assigned and augmenting forces and an initial logistics support, transportation and sustainment concept. 3. ( ) Initial estimated time phasing of combat/support forces into the region. (c) ( ) Write Service support plans and submit for approval to this headquarters. d. ( ) Other Supporting Commands, Services and Agencies (1) ( ) Review the proposed concept of operation and provide assessment of resource and capability requirements, any critical shortfalls, and logistics requirements. (2) ( ) Provide ready forces based on final identified and approved requirements;

develop supporting logistics and sustainment concepts to support the COA. (3) ( ) Write supporting plans and submit for approval to this headquarters. 10. ( ) Administration a. ( ) Planning Schedule (1) ( ) Planning Conferences (a) ( ) Initial Planning Conference - USMEDCOM/J-5 (b) ( ) 60 Days - Intermediate Planning Conference, USMEDCOM/J-5 (c) ( ) 180 Days - TPFDD/Logistics Refinement Conference, USMEDCOM/J-4 (d) ( ) 280 Days - Transportation Conference, USTRANSCOM (e) ( ) 300 Days - Final Planning Conference, USMEDCOM/J-5 (2) ( ) Suspenses (a) ( ) Initial Planning Conference - USMEDCOM issue Planning Guidance (b) ( ) 7 Days - All staff agencies identify points of contact to USMEDCOM/J5 (c) ( ) 14 Days - Preliminary Staff Estimates from USMEDCOM J-staff, components and supporting commands, Services and agencies (d) ( ) 21 Days - J-5 provide consolidated Staff Estimates for commander review (e) ( ) 30 Days - USMEDCOM submit Commander’s Estimate to JCS (f) ( ) 60 Days - Intermediate Planning Conference; J-5 issue USMEDCOM Plan Summary and task components for development of supporting/support plans



(g) ( ) 120 Days - Service components submit Service TPFDDs; USMEDCOM staffs (less J-4) submit annexes and appendices for review (h) ( ) 150 Days - Final edited all-Service TPFDD to USMEDCOM/J-4 for movement feasibility analysis (i) ( ) 180 Days - TPFDD/Logistics Refinement Conference (j) ( ) 280 Days - Transportation Conference at USTRANSCOM (k) ( ) 300 Days - Final Planning Conference (l) ( ) 310 Days - USMEDCOM CONPLAN 0995-xx submitted for Joint Staff and JPEC review, and SecDef approval

(m) ( ) 340 Days - SecDef approves plan (n) ( ) 400 Days - Components and supporting commands, Services and agencies submit plans to USMEDCOM for approval b. ( ) Staff Liaison Instructions (1) ( ) USMEDCOM J-5 is lead for overall plan development and coordination. DIRLAUTH is authorized. POC is Lt Col Dewey Hafta, DSN 295-0995. (2) ( ) Forward all coordinated staff instruments to J-5 for review. (3) ( ) NEWSGROUP “CONPLAN 0995” is established for planning coordination. U. R. A. Whyner, Admiral, USN Commander, USMEDCOM

unclassified for educational purposes only · unclassified – for educational purposes only 1 ......

Documents