OPERATIONS ORDER
Operation Honeybadger (2001), Night Fighters
TO:
OPERATIONS OFFICER
United Task Force
UNITAF Forces Afghanistan
OPERATIONS OFFICER
United Task Force
UNITAF Forces Afghanistan
FROM:
Lt Gen Chad P. Franks
CMDR CJTF USCENTCOM
MacDill Air Force Base Tampa, U.S.
Lt Gen Chad P. Franks
CMDR CJTF USCENTCOM
MacDill Air Force Base Tampa, U.S.
--- OPERATIONS ORDER ---
Situation
Background InformationIn an attempt to root out the remaining Taliban in the region, a US Army platoon responds to an emergency call for aid in the night from the local village elder of Abbadaez. Meanwhile an SF detachment observes suspected Taliban convoy routes to the town of Bahad.
Friendly Forces
[1x] US Light Rifle Platoon, consisting of: [2x] Rifle Squad [1x] Weapon Squad Supplemented: [1x] Mortar Team [1x] Logistical Support group, CH-47 Chinook [1x] Medical Support group, UH-60 Black Hawk [1x] Special Forces ODA Team
Enemy Forces
Suspected medium levels of Taliban: infantry, technicals, static weapons. Taliban operate guerrilla and ambush tactics.
Mission
TaskingConduct a night-patrol in order to root out remaining Taliban in the region.
End-state
Remaining Taliban presence is neutralised or dispersed with minimum friendly and civilian casualties.
Execution
Commander's IntentHitman Platoon will respond to a distress signal received from a nearby village elder who claims to have intel on the remaining Taliban forces in the region. Once received, they will use this information to conduct attacks on the nearby enemy forces before preparing to sweep the town of Bahad. Bandit's purpose is to conduct recon and disrupt Taliban presence where needed.
Tasks and Sequencing
Detailed by objective. OBJ "Arizona" is the final Hitman-Bandit joint objective.
Staging
HITMAN and BANDIT prepare for departure at FOB Jackson. HITMAN departs on foot west along MSR FATA towards OBJ Alaska. Hitman scheme of manoeuvre is detailed below first. BANDIT departs on their own initiative east towards OBJ OHIO. Bandit scheme of manoeuvre begins sequencing below there.Objective “Alaska”
Hitman first locates the village Elder of Abbadaez. One squad is detached to interview and secure the Elder, who has reportedly collected intel regarding nearby Taliban positions and movements. Hitman remainder maintains security through town. Natural focus points shall be facing N from the town perimeter and S near the road. Using the Elder's information, Hitman will proceed to act upon it accordingly and aggressively.Objective “Florida”
Once Hitman 9 deems suitable, the platoon will continue to their next objective. Hitman sweeps and clears the town of Bahad, expected to be unwillingly harbouring an insurgent threat. The town holds a large civilian population, so weapon discretion is paramount. Best efforts must be taken to root out any Taliban presence. A likely advance will be conducted from the west perimeter of town, enveloping to clear south to north in three sections.Objective “Ohio”
Bandit’s first objective is to capture or kill an insurgent HVT suspected to be hiding in a town close to FOB Jackson. Civilian presence is seemingly light, however little movement has been spotted. Due to previous attacks, a UXO threat is present in the North-East of town that should be avoided unless Bandit is ordered or required to clear it.Objective “Iowa”
Bandit’s second objective is to assist a Northern Alliance reconnaissance squad under heavy assault at a nearby firebase. Whilst the enemy attack has seemingly dwindled, the NA fighters are low on munitions and supplies and require Bandit’s relief. Moreover, the NA squad has reportedly gathered intel on a possible insurgent tunnel network in the region, which they are willing to share.Objective “Utah”
Bandit’s third objective is the execution of an ambush on Bahad’s Northern roadway. This route is highly suspected of being used by the Taliban to reinforce and rearm a hidden insurgent threat within Bahad. Several suspicious convoys have been sighted travelling the path. Bandit must ensure to stay vigilant as, although the mission will be conducted at night, it is not unheard of for civilians to still be travelling between towns – they must choose their target wisely.Objective “Arizona”
Due to the urgency of this mission, little information has been gathered regarding Hitman and Bandit’s combined final objective, We can say with some certainty that this unnamed town contains a heavy and fortified Taliban presence. The town sits directly on a known Taliban supply route so will likely be well-manned and well-armed as it is most likely utilised as an insurgent staging ground or firebase. Both Hitman and Bandit will conduct a coordinated assault on the town in order to destroy or disperse any remaining insurgent threat in the region and further secure the vicinity surrounding FOB Jackson.Administration/Logistics
ResupplyHitman and Bandit depart from FOB Jackson with a light night-appropriate combat load. Sustainment will be executed through proactive and reactive air drops by means of call sign Castle.
Firebase Sustainment
Call sign Archer is responsible for its own supply of munitions, e.g., with a munitions lorry. In the event of embarkation or running dry, Archer and Castle coordinate logistics as per comms plan below.Medical
Medical emergency response is heliborne by means of call sign Guardian. In the event of casualties beyond the capacity of Hitman platoon medic, Guardian conducts a MEDEVAC for safe treatment and subsequent re-insertion. Guardian is on stand-by for treatment and MEDEVAC of civilians.
Rules of Engagement
In accordance with SOP
Fire Support Plan
Fire support by means of 81 mm M252 mortars is available with call sign Archer in accordance with SOP. In addition to destructive fire missions, Archer stands by for continuous battlefield illumination.
Close Air Support
In accordance with SOP
Command/Signal
Communications Plan
Callsign | Primary Frequency | Superior Frequency | ACTUAL |
---|---|---|---|
HITMAN 9 | 40mHz | 37mHz | SFC SkullCollector Platoon Leader |
HITMAN 1 | 250mHz | 40mHz | SP1 Hotspur (Ret.) Squad Leader |
HITMAN 2 | 260mHz | 40mHz | MSP Jari (Ret.) Squad Leader |
HITMAN 3 | 270mHz | 40mHz | MSP Mattjamco Infantry Team Leader |
BANDIT 9 | 361mHz | 37mHz | SSG Kevin SF Commander |
BANDIT 1 | 362mHz | 361mHz | SP1 Tony SF Team Leader |
BANDIT 2 | 290mHz | 361mHz | SPC William (Ret.) SF Team Leader |
CASTLE 4 | 70mHz | 43mHz | SSG Hrusi Logistics Support Chief |
ARCHER 4-1 | 71mHz | 70mHz | SP3 Noah_Hero Fire Support Chief |
WATCHMAN H | 87mHz | 37mHz | 2Lt Zuka Senior Game Master |
Succession of Command
HITMAN 9 >> HITMAN 8 > HITMAN 1 > HITMAN 2 > HITMAN 3 In the event of total collapse of the HITMAN chain of command, BANDIT 9 must attempt communication, reconsolidation and evacuation.COMMS PLAN
LR 40: HITMAN 9 >> HITMAN 1, 2, 3 Close combat net LR 70: HITMAN 8 >> CASTLE 4 LR 80: HITMAN 8 >> GUARDIAN 5 Platoon sergeant logistical net LR 71: HITMAN 7 > ARCHER 4-1 Fire support net LR 72: CASTLE 4 > ARCHER 4-1 Fire base logistical net To be used in the event of either embarkation of the mortar group for close redeployment and / or resupply requests.CONNECTION INSTRUCTIONS
TEAMSPEAK IP: ops.unitedtaskforce.netGAME SERVER IP (Direct Connect): ops.unitedtaskforce.net
GAME SERVER PASSWORD: issued on Discord
TIMINGS
SERVER OPENS: 1630hrs UTCFORM UP: 1700hrs UTC
ANNOUNCEMENTS/BRIEFING: 1715hrs UTC
STEP OFF: 1725hrs UTC
END-EX: 1900-2000hrs UTC APPROX
All are GMT/UTC