KevinB
Army.ca Relic
- Reaction score
- 24,747
- Points
- 1,260
As promised from the C7 Modernization thread.
I have decided to make a separate thread for at least my take on the Future Armored Division’s Reconnaissance Brigade.
Some caveats: I see the Division as the smallest viable ‘self contained’ entity. The enablers required for Peer or Near Peer conflict require a breadth of forces that is beyond the Combined Arms forces of the late 20th Century. Not to say a smaller military needs to deploy an entire division, but that Brigade’s will not be able to operate on their own, and need the umbrella from Division (yes arguably that was needed anyway in peer/near peer fighting).
A lot of this is taken from Jack Watling’s The Arms of the Future (highly recommended) as well as various modernization projects across NATO and US specific Cross Functional Teams liking at future force models.
I dislike several of Dr Watlings monikers for forces. What he calls the Maneuver Force, I prefer to call Reconnaissance, and I split that into Light Reconnaissance, Cavalry, and Support (which for this includes a HQ)
Where I differ from a lot of other plans is I have Mixed Companies of Light Recce and Calvary. Basically 1 Light Recce Platoon and 2 Platoons of Calvary (call them troops if you want, I’m agnostic) and a HQ Platoon.
I see the force as a symbiotic entity that needs the mix to work effectively in a Near Peer LSCO therefore mixed formations are the best way to create that synergy.
Light Reconnaissance Detachment on a 12-14 person detachment. You may notice it sort of looks like an Army Special Operations Detachment Alpha.
4 Det’s to a Platoon in the Reconnaissance Company
Light Vehicles are key as this force isn’t designed to be in contact. Each Detachment would have 4 4x4 vehicles. I’m somewhat agnostic to naming vehicles, but I’ll go with the Chevy ISV with some Recce specific alterations. I would also have 4 Electric Bikes that are hung in a bracket on the rear of the vehicle.
All personnel would be at least basic Infantry Recce patrolman qualified.
1) Det Commander
2)Signaler / I believe at this point that it needs to be a much more trained individual than a Recce Patrolman with a radio, my ideal candidate would be an 18E Comms Sgt, but I doubt the CA would send a bunch of folks to Bragg for the SF Comms course. But they need to know how to troubleshoot the various communications assets the team has for voice and data.
3)MFC/FOO Tech:
4-5) Stinger SHORAD Team
6-7) Javelin Team
(I use Stinger and Javelin for a reason as both can use the LWCLU and this give a redundant launcher option if one is damaged, but also gives the small team flexibility to focus towards air or ground should the threat require it, and both a fire and forget as the goal of the teams isn’t to get into prolonged contact).
8) Pioneer/Engineer both for demolitions, but also for bridge and other technical surveys.
9) Combat Medic: not a fully 18D, but more like the Ranger Medic which is a 3 month course that is basically a T3C on steroids.
10-11) Sniper Team
12) UAS Operator
That was 12, then I have two of the nice to have positions, but I could live without them in certain situations.
13) Interpreter (as applicable)
14) HumInt Specialist
I have been trying to be realistic as to the extent of what can expect in a non SOF environment, and I don’t think I’m asking too much, close, but…
The Calvary Platoon (note I am going this by Platoon initially as I have mixed Platoons in the Recce Coy’s as they are necessarily complementary entities that should be employed together in a Near Peer type scenario.
I base the Cav Platoon on a 6 vehicle force. They can split into 2 groups of three for dispersed operations and group back together as a Platoon or Coy- with the Second Platoon as required.
A tracked ‘IFV’ for purposes of discussion I would opt for the GDLS XM-30 MICV submission. All vehicles have mast mounting options, though at this time I can only see a need for three mast vehicles.
2 Surveillance POD (EO/IO active and passive systems)
1 Directional Antenna
2 Cannon vehicles with Mine Plows, 1 with a
The only other differences are the turrets
2 are 40-50mm automatic cannons (I’m more preferential to the 40mm CTA cannon from Ares but.. they also have 4 Javelin NLOS missiles (I wouldn’t kick the Hellfire out of the equation either, but having seen the Hellfire reload on an IFV, I’m more willing to accept a 6km range limit for these systems than the boondoggle that can occur manually reloading Hellfire to gain an extra 6km.
1 is a 35mm Cannon and DE AD/C-UAS turret
1 is a 35mm Cannon and RBS-70 AD/C-UAS turret
2 are 120mm mortar turrets.
Watling has his screening platoon on a 4 vehicle system, but he anticipates that the cannon IFV can conduct counter UAS, where I’m of the opinion a dedicated turret will be needed to take feed data for reliable hard kill.
I also don’t see much of a viability for dismounts in a 4 vehicle packet as the mortar versions will have at most 2 with the ammo load. I’m seeing at most 4 in the other versions , considering one wants to be able to have reach back high bandwidth comms, and reasonable supplies of stores. I also want room in extremis if there is a need to cross load due to vehicle losses, or extraction of the Light Recce Det’s if things go sideways badly.
I mentioned the 3/2 split but when operationing as a formed unit see them operating in a 2-2-2 split with a Cannon system and AD system moving and then supporting the next cannon and AD and the Mortars moving as one and moving ones the other two are set. The Light Recce Det’s will have been looking for any significant enemy, as well as UAS, GeoSpacial assets and EW systems should have any major enemy located. These teams will be operating in contested territory covered by friendly sensors, but also sometimes detected by small unit infiltrators or UAS.
So 18 vehicle crew: and 20 dismounts for LAS, UAS launch and Recovery, maintenance. As well as:
Manpad team
Sniper Team
Medic team
Signallers
Engineer Recce Sgt
Unlike Walting, I didn’t split the Armored Recce and Infantry. But combined them into a Cav force that I see 2 Cav platoons operating in a second echelon to the Light Recce Platoon. The Light Recce is designed to remain hidden, while the Cav will engage (and be engaged) but mobility and camouflage is generally their primary defense.
HQ and Support Platoon.
I’m going to use the AMPV as the primary vehicle for the CP’s, EW Section, AD Vehicle, Engineering assets, Medical Evacuation, Medical Transport and Recovery/Fitter tasks. The Logistics section would be via PALS 10x10 vehicles, fuel, food, ammunition etc being palletized (and while there are some advantages to a dedicated fuel bowser vehicle, it is also a single point of failure.
More to follow but my plane is boarding.
I have decided to make a separate thread for at least my take on the Future Armored Division’s Reconnaissance Brigade.
Some caveats: I see the Division as the smallest viable ‘self contained’ entity. The enablers required for Peer or Near Peer conflict require a breadth of forces that is beyond the Combined Arms forces of the late 20th Century. Not to say a smaller military needs to deploy an entire division, but that Brigade’s will not be able to operate on their own, and need the umbrella from Division (yes arguably that was needed anyway in peer/near peer fighting).
A lot of this is taken from Jack Watling’s The Arms of the Future (highly recommended) as well as various modernization projects across NATO and US specific Cross Functional Teams liking at future force models.
I dislike several of Dr Watlings monikers for forces. What he calls the Maneuver Force, I prefer to call Reconnaissance, and I split that into Light Reconnaissance, Cavalry, and Support (which for this includes a HQ)
Where I differ from a lot of other plans is I have Mixed Companies of Light Recce and Calvary. Basically 1 Light Recce Platoon and 2 Platoons of Calvary (call them troops if you want, I’m agnostic) and a HQ Platoon.
I see the force as a symbiotic entity that needs the mix to work effectively in a Near Peer LSCO therefore mixed formations are the best way to create that synergy.
Light Reconnaissance Detachment on a 12-14 person detachment. You may notice it sort of looks like an Army Special Operations Detachment Alpha.
4 Det’s to a Platoon in the Reconnaissance Company
Light Vehicles are key as this force isn’t designed to be in contact. Each Detachment would have 4 4x4 vehicles. I’m somewhat agnostic to naming vehicles, but I’ll go with the Chevy ISV with some Recce specific alterations. I would also have 4 Electric Bikes that are hung in a bracket on the rear of the vehicle.
All personnel would be at least basic Infantry Recce patrolman qualified.
1) Det Commander
2)Signaler / I believe at this point that it needs to be a much more trained individual than a Recce Patrolman with a radio, my ideal candidate would be an 18E Comms Sgt, but I doubt the CA would send a bunch of folks to Bragg for the SF Comms course. But they need to know how to troubleshoot the various communications assets the team has for voice and data.
3)MFC/FOO Tech:
4-5) Stinger SHORAD Team
6-7) Javelin Team
(I use Stinger and Javelin for a reason as both can use the LWCLU and this give a redundant launcher option if one is damaged, but also gives the small team flexibility to focus towards air or ground should the threat require it, and both a fire and forget as the goal of the teams isn’t to get into prolonged contact).
8) Pioneer/Engineer both for demolitions, but also for bridge and other technical surveys.
9) Combat Medic: not a fully 18D, but more like the Ranger Medic which is a 3 month course that is basically a T3C on steroids.
10-11) Sniper Team
12) UAS Operator
That was 12, then I have two of the nice to have positions, but I could live without them in certain situations.
13) Interpreter (as applicable)
14) HumInt Specialist
I have been trying to be realistic as to the extent of what can expect in a non SOF environment, and I don’t think I’m asking too much, close, but…
The Calvary Platoon (note I am going this by Platoon initially as I have mixed Platoons in the Recce Coy’s as they are necessarily complementary entities that should be employed together in a Near Peer type scenario.
I base the Cav Platoon on a 6 vehicle force. They can split into 2 groups of three for dispersed operations and group back together as a Platoon or Coy- with the Second Platoon as required.
A tracked ‘IFV’ for purposes of discussion I would opt for the GDLS XM-30 MICV submission. All vehicles have mast mounting options, though at this time I can only see a need for three mast vehicles.
2 Surveillance POD (EO/IO active and passive systems)
1 Directional Antenna
2 Cannon vehicles with Mine Plows, 1 with a
The only other differences are the turrets
2 are 40-50mm automatic cannons (I’m more preferential to the 40mm CTA cannon from Ares but.. they also have 4 Javelin NLOS missiles (I wouldn’t kick the Hellfire out of the equation either, but having seen the Hellfire reload on an IFV, I’m more willing to accept a 6km range limit for these systems than the boondoggle that can occur manually reloading Hellfire to gain an extra 6km.
1 is a 35mm Cannon and DE AD/C-UAS turret
1 is a 35mm Cannon and RBS-70 AD/C-UAS turret
2 are 120mm mortar turrets.
Watling has his screening platoon on a 4 vehicle system, but he anticipates that the cannon IFV can conduct counter UAS, where I’m of the opinion a dedicated turret will be needed to take feed data for reliable hard kill.
I also don’t see much of a viability for dismounts in a 4 vehicle packet as the mortar versions will have at most 2 with the ammo load. I’m seeing at most 4 in the other versions , considering one wants to be able to have reach back high bandwidth comms, and reasonable supplies of stores. I also want room in extremis if there is a need to cross load due to vehicle losses, or extraction of the Light Recce Det’s if things go sideways badly.
I mentioned the 3/2 split but when operationing as a formed unit see them operating in a 2-2-2 split with a Cannon system and AD system moving and then supporting the next cannon and AD and the Mortars moving as one and moving ones the other two are set. The Light Recce Det’s will have been looking for any significant enemy, as well as UAS, GeoSpacial assets and EW systems should have any major enemy located. These teams will be operating in contested territory covered by friendly sensors, but also sometimes detected by small unit infiltrators or UAS.
So 18 vehicle crew: and 20 dismounts for LAS, UAS launch and Recovery, maintenance. As well as:
Manpad team
Sniper Team
Medic team
Signallers
Engineer Recce Sgt
Unlike Walting, I didn’t split the Armored Recce and Infantry. But combined them into a Cav force that I see 2 Cav platoons operating in a second echelon to the Light Recce Platoon. The Light Recce is designed to remain hidden, while the Cav will engage (and be engaged) but mobility and camouflage is generally their primary defense.
HQ and Support Platoon.
I’m going to use the AMPV as the primary vehicle for the CP’s, EW Section, AD Vehicle, Engineering assets, Medical Evacuation, Medical Transport and Recovery/Fitter tasks. The Logistics section would be via PALS 10x10 vehicles, fuel, food, ammunition etc being palletized (and while there are some advantages to a dedicated fuel bowser vehicle, it is also a single point of failure.
More to follow but my plane is boarding.
