(If you’re reading at Bay12 as opposed to one of the other places this runs, you can skip ahead to the last two paragraphs of the introduction, which reproduces stuff I’ve posted during the week there.)
Readers familiar with the BattleTech lore will have put May 1, 3052 and Tukayyid together already.
For everyone else, the Battle of Tukayyid is one of the seminal events in the history of the Inner Sphere. ComStar, up until now believed to be merely the people who run the hyperpulse generator interstellar communications network, reveal themselves to be guardians of enormous caches of Star League technology and an army as large as any of the Great Houses of the Inner Sphere. They challenge the Clans to a Trial of Possession, a throwdown for the fate of the known galaxy. Seven miniature battles are set for Tukayyid, seven Clans against seven units of the Com Guards. If ComStar wins, the Clans advance no further than Tukayyid for the next fifteen years. If the Clans win, ComStar forfeits Terra itself. I won’t spoil the ending.
What I will do, since the Opinionated Bastards are on the sidelines for this month, is replicate one of the official Battle of Tukayyid scenarios and play that, with the Bastards replacing the Com Guards for fun.
The scenario is #3 from the BattleTech Tukayyid sourcebook: Battle in the Suburbs. Clan Nova Cat’s forces, battered somewhat by ComStar aerospace fighters while landing, nevertheless marched on the city of Joje in moderate force. In the real timeline, two veteran Com Guard divisions stood ready to meet them. The Nova Cat commander who won the batchall for the attack bid a single Cluster, which matched the Com Guard strength mech for mech, but ignored the Com Guards’ penchant for combined arms tactics. An engagement in the northern suburbs between the 9th Division and the leading elements of the Second Nova Cat Guards saw the Clanners stopped in their tracks. The Nova Cat forces, heavily dependent on ammunition supplies, made no further progress into Joje.
In our hypothetical timeline, it isn’t the Com Guards who meet the Nova Cat forces in Joje, it’s the Opinionated Bastards. In particular, it’s Drake’s Destroyers, Second Lance, and Reserve Lance. Facing off against them are two stars of Clan mechs, one medium, one light. The light star is down one mech, for a total of 9 Clanners. All are elite pilots.
Poland’s Rak 120mm self propelled mortar is the sort of turreted system that Russia has had for years but never really caught on in the west. It’s built on the Rosomak chassis, which is a Polish-made variant of Patria’s 8×8 AMV.
In the turret is a 120mm breach-loading mortar. It has an automatic loading system with a capacity for 20 ready rounds. 26 additional rounds are stowed in the hull. The autoloader and mortar has a rate of fire of 6-8 rounds per minute. The mortar has the expected computerized fire control system that is integrated with the GPS/INS navigation system. This fire control system also allows for direct fire with a laser rangefinder and a day/night sight. A coaxial 7.62mm UKM-2000D machine gun is also provided.
Chief among the advantages of a turreted mortar carrier is the ability to provide protection for the crew. The Rak has STANAG Level 1 armor protection all-around, which means it’s rated to resist 7.62mm M80 rounds and 5.56mm M855 and M193 rounds fired from a distance of 30 meters. It’s also proof against fragments from a 155mm artillery shell detonated at 100 meters. That’s pretty good, but I’d prefer a bit more protection. More specifically, I’d be concerned about DPICM-type submunitions hitting the roof, and I don’t expect the Rak to be protected from these.
The Rak has a crew of three, which is notably less than the simpler mortar carriers. That’s good for life-cycle costs. Overall, I like the Rak a lot.
I’ve spoken before about CAS-specialist aircraft. I’ve spent a lot of time with the virtual A-10 in DCS, and I’m a big fan of the aircraft. In my heart, I love that gun. But the heart can make us do stupid things. We can’t always trust it. Similarly, the A-10 has saved the bacon of a great many American soldiers in combat. They adore the Warthog, and rightfully so. But they would adore any aircraft that saved them.
We want to know whether or not the Dedicated CAS aircraft is a good buy. Keeping it simple, we’ll compare it to buying more multirole aircraft instead. In USAF terms, A-10s or F-16s. Given that this is 2017, and we have combat data on both, is it worth it to put money towards maintaining the A-10 fleet, or should that money be switched over to the F-16s and F-35s?
The close air support mission is a peculiar one, and one full of contradictory requirements. The A-10 seems tailor-made for the mission, with plenty of armor and a massively powerful gun. It’s optimized for flying low and slow, and this kind of flight profile maximizes the utility of the gun and the ability of the pilot to see things.
That sort of flight profile make a number of assumptions:
Local air superiority has been achieved and can be assumed
Enemy air defense is extremely limited in number
Enemy air defense is gun based or nonexistent
In a conventional shooting war, or even a low-intensity conflict with a sophisticated adversary, we don’t get to assume these are true.1 In a COIN conflict, we get (1) and (2) but we may not have (3). The enemy may have access to MANPADS like Stinger or Igla. As seen in the Soviet experience in Afghanistan, this forces aircraft to medium altitudes, i.e. out of the gun envelope.
Let’s look at the combat record. The A-10 has seen combat in Gulf War I as well as providing close air support as part of US military operations in Iraq and Afghanistan. The first Gulf War is as close as we get to seeing the A-10 in a conventional war. The A-10 was not sent in against the Iraqi SAM systems. But it did see plenty of use against troops of both the Iraqi Army as well as against those of the Republican Guard. The Republican Guard was better equipped and better disciplined than the conscript regular army. The Republican Guard did not have much in the way of MANPADS or other short-range SAM systems, but they fought back with guns. Many A-10s sustained combat damage, and two were lost on February 15, which caused A-10s to be tasked to other targets. While the A-10’s armor usually allowed it to make it back to base, the A-10’s lack of speed was identified as a deficiency that made it more vulnerable to gun hits.
The primary tank-killer for the A-10 in the Persian Gulf was the IR-guided Maverick, not the GAU-8/A. Of course, other aircraft can also carry these Mavericks, and these other aircraft also racked up a respectable tally of destroyed tanks with the AGM-65s. The A-10A had very little provision for precision-guided ordnance2, and so did not use laser guided bombs to “plink” tanks, unlike the F-111. Again it doesn’t take a purpose-built aircraft to carry precision ordnance, and these can be delivered from medium altitude, away from AAA and MANPADS.
Lots of aircraft have done CAS duty in Afghanistan, including of course, the A-10. Again, the big star weapon hasn’t been the gun. It’s the JDAM, which are GPS guided. Also using the JDAM to excellent close air support effect are the B-1B and the B-52H. And many others too, but I’m highlighting heavy bombers because they’re big, high-altitude behemoths that aren’t really “designed” with CAS in mind. But they can do it with modern weapons. As can F-16s, F-15Es, F/A-18C/Ds, F/A-18E/Fs, and just about every other multirole tactical aircraft you care to name. Tactical aircraft give up the giant gun and the armor plate. But there’s a net gain in survivability from more speed because they can evade missiles better, and they can perform the vast majority of modern CAS missions just as well as a purpose built type.
For COIN, one might be tempted to look for savings in aircraft types. These can be provided from UCAVs like the MQ-9 Reaper or from something like a Super Tucano. Both of these will provide more sorties per dollar than the sort of big armored CAS-optimized plane. And if there’s negligible threat, they’ll drop precision guided munitions just as well.
Against a hypothetical, sophisticated opponent with modern integrated air defense systems, all of the above will all require large strike packages to approach any kind of reasonable survivability level, and those aren’t feasible for CAS. Maximum survivability is provided by aircraft with low-observability characteristics, such as the F-35 or F-22. In Desert Storm, coalition air commanders had faith only in the stealthy F-117 to penetrate the formidable air defenses around Baghdad. The alternative to stealth is a big, Rolling Thunder-style strike package with ECM and SEAD escorts, plus fighter escorts. Which isn’t going to be generated for an aircraft to loiter in support of ground forces.
Let’s look at a more modern example: recent events in the Ukraine. Here’s a radar map of the Ukraine. That’s a map of all of the air search radars in the region. Have fun with that. And remember, lots of these SAM systems are going to be reasonably modern units that can move. Everyone saw the success the Serbians had by shutting off their radars and moving their air defense systems around to frustrate NATO SEAD strikes. And you can’t sortie your A-10s until you get air superiority and deeply reduce that SAM umbrella.
The gun on the A-10 is a fantastic weapon, but it’s a trifle outmoded these days. If a gun and armor were the sine qua non of CAS, we’d sortie Hs 129 B-3s. With modern precision munitions, the role can be filled by multirole or low-observable-multirole types with no loss of effectiveness. And in hostile airspace where the opponent has some actual air defenses, the A-10 and its ilk are the least survivable types. A mess like the Donbass is begging for low-observability if you want to actually survive to deliver ordnance and live to strike again tomorrow.
While we're committed to keeping our long-form posts free for all, short ones like this are exclusive to our patrons. To read it, please consider supporting our work!
To view this content, you must be a member of Many's Patreon at $5 or more
Drake looks over the plans for the Awesome’s refit and deems them good. It’s Kepano Endo again who takes on the task. Between reconditioning all the damaged internals, coming up with a way to fit Clan technology in, and changing the engine heat sinks out, it’s going to take…
Five months. Well, when it’s ready, it’ll be a sight to behold.
The Action of April 10, 3052
There are rumblings amongst the Rasalhague garrison that something big is going to happen soon: a truce, an Inner Sphere counterattack, something.
That’s a long way off, though, and we have more immediate concerns. A Rasalhague officer appears in the Bastards’ command post—a little more makeshift and a little more tumbledown than in the past; moving world to world at this pace is hard—and lets us know that a full Star of Clan mechs has been spotted marching toward the city of Spanac. There’s a Rasalhague force moving to intercept, but they’ll need reinforcements. Second Lance and Bear’s Bruisers drew patrol duty today. Drake redirects them there. It’ll be a race against time.
Since it’s been a while since these two lances deployed, here are their dispositions. The Ryoken still has a damaged arm, but will have to get by. The Ultra AC/20 is its main punch anyway.
The Opinionated Bastards are arriving a little late to the party. We’ll deploy as we arrive. To get full credit for the mission, we’ll have to keep at least some of the extant Rasalhague forces alive.
Round 1
None of our forces arrive until before Round 4.
The Rasalhague forces deploy around the city in the middle of the map, while the Clanners appear all along the northern border. They advance, exchanging LRM and PPC fire to no effect.
Round 2
The Rasalhague forces remain entrenched in the city, while the Clanners close from all angles. The lightest Rasalhague mech, an Ostscout, takes heavy damage and loses a leg.
Round 3
The Clan mechs, rushing into combat and toward glory, slip on the pavement. A Fenris trips, sliding into an approaching Ryoken and nearly tripping. The Rasalhague mechs, whose pilots are largely green, fail to take advantage. The Clanners, however, remain focused on the ailing Ostscout.
Round 4
Severe is the first to arrive on the scene. (The minimap shot up under round 1 has her position highlighted.) Her sensors paint a confused picture. Firing continues in the city. Severe is going to move closer, but attempt to stay out of the way until reinforcements arrive. Teddy Bear‘s Vulcan arrives before Round 5, and Simona in the Ryoken appears before Round 6.
Round 5
The Rasalhague Ostscout finally falls. A full company of mechs now battles in the city, although two of the Rasalhague mechs are hanging back. Teddy Bear arrives, and he and Severe link up on the road south of the city.
The heaviest Rasalhague mech, a Thunderbolt, falls. Chatter on the Rasalhague radio net turns panicky; that must have been their commander.
Teddy Bear quickly switches his radio over to the right channel, and calls for the Rasalhague forces to retreat and regroup south of the city, falling back on the Bastards.
Round 6
The six remaining Rasalhague mechs are a little slow to respond, and a little out of position to boot. Happily, most of them have jump jets, and the command to turn and run seems to be a pretty welcome one. Milspec in the Crab, plus the ever-dependable Wizard and Hanzoku in their Guillotines, arrive soon. With the Rasalhague forces rallying to us, we may be able to turn this around on the Clanners.
The allied Lancelot appears to be trapped; unable to jump and deployed on the wrong side of the buildings, it’s facing down the enemy Ryoken and Man o’ War. We’ll see if we can extricate it.
We can’t support it with weapons fire yet. Its pilot aims, not for the Fenris shooting at it, but at the building underneath it.
Round 7
The gambit doesn’t work; the building survives. The Lancelot is likely to take a serious beating.
South of the city, the Bastards and the Rasalhague forces are consolidating. Soon they’ll be in position to make a push.
The allied Ostroc actually has a shot on one of the enemy Fenrises, and takes it gleefully. So does the Cicada. Severe joins in, firing the Bastards’ first shots in anger from a Clan mech.
Round 8
Double Dog hits the field. Only Rook remains to join the fray.
We don’t have a lot of LRMs, but we also don’t want to charge around the corner until we can bring more mechs to bear at once. The allied Cicada, perched atop a building but out of sight of most of the enemy mechs, will do some spotting, as will the Lancelot, which is probably doomed this turn.
Round 9
The allied Lancelot does indeed eat it, and the Cicada takes a hit from one of the Fenrises which knocks out one of its legs. Fully half of the allied mechs have been either destroyed or rendered combat-ineffective. Happily, we’re now in a position to begin our own attack, swinging around to the left to engage the Clanners.
Simona finds himself a good position with the Ryoken, switching his Ultra AC/20 over to burst mode and targeting the rear of the enemy Ryoken. Rook, too, takes her first shot of the day, a low-percentage LRM-10 salvo against the enemy Ryoken. The allied commander, who survived the destruction of his Thunderbolt and managed to eject, is directing fire.
For his trouble, he immediately takes a hit from the Man o’ War’s large pulse laser.
Simona hits with one of his two AC/20 shells, shearing off the enemy Ryoken’s right arm and cutting deep into its right torso armor: a successful sneak attack. He’ll get down from the building now, to avoid taking any return fire.
Round 10
The allied Cicada is still clinging to life, but not for very long. Rook, who took command when she took the field, encourages its pilot to eject. The Rasalhague pilot does so.
At present, our forces are still jockeying for position.
Round 11
The next round sees the Bastards moving into attack range of the enemy. Severe takes a shot at a Fenris caught a bit out of position, joined by Wizard and the Rasalhague medium mech drivers. Simona is itching to bring his AC/20 to bear, but is just out of range behind a building.
The Fenris unloads at point-blank range with four medium pulse lasers, knocking the Rasalhague Wolverine over and readying a kick. Severe misses with everything, though Wizard scores with her PPC. The Rasalhague Griffin readies a kick itself.
Though the Wolverine absorbs a kick, the Griffin’s kick knocks the Fenris down.
Round 12
A pillar of dust around to the west comes as a surprise to the Bastards on the field. Sensor records later indicate that it was an enemy Fenris, attempting to flank, which skidded into a building.
The Rasalhague Wolverine loses an arm to fire from the Fenris, but beyond that, not much happens.
Severe is on the hunt for the enemy Fenris to the north, while Simona and Milspec aim to put some fire on the enemy Ryoken. Simona, unfortunately, is under fire from the enemy Man o’ War, too. Hopefully he’ll weather it well.
It seems he does: he takes a few hits, and fire from the Ryoken facing him eats into his left leg and strikes the myomers in the shin. Otherwise, his armor holds, and with a devastating AC/20 shot to the chest, he knocks the enemy Ryoken out. We’ll have to see about salvaging it later.
Round 13-14
The Clan Wolf Man o’ War moves up, and the battle is well and truly joined. Teddy Bear, Severe, Hanzoku, and Milspec have clear shots at it, while Simona has managed to move just out of its path. He exchanges fire with the flanking Fenris, now back on its feet, instead. Double Dog shoots at the back of the Fenris from up north, hoping to bring it down in concert with the friendly Wolverine.
As might have been expected, Simona loses the Ryoken’s right arm and its attendant medium lasers. Hopefully we can salvage those. The Man o’ War takes a good bit of damage, but Milspec‘s cockpit flashes with alarms: his right torso armor is gone.
Round 15
The Man o’ War lays heavy fire on the Koshi, which I stupidly put a little too close to its arc of fire. Severe does what she can to stay on her feet, but bolts shear apart and her mech’s left leg detaches at the hip.
Hanzoku, however, scores a kill on the Fenris hassling Rook, while Simona blows a leg off of the other one.
Round 16
Simona is out of danger now, and Rook is in LRM and large laser range of the Mad Cat perched on a building over to the east. The enemy Man o’ War, though still evidently in good shape, has nearly been cored; its center torso is all but gone.
Wizard scores the kill on the Man o’ War, shooting through its tattered rear armor, and knocking out its engine.
Round 17
Milspec is left to deal with the downed Fenris, while the rest of our little force advances on the Mad Cat, the only enemy still in fighting shape. Its pilot jumps down from the building, taking it out of the arc of fire of most of our mechs.
Trading fire with the Ostroc, the Mad Cat neither deals nor takes serious damage. Milspec gets the kill, kicking through the Fenris’ chest.
Round 18
For once, initiative goes our way. The Mad Cat moves first, and we’re able to bring a lot more firepower to bear; six or seven mechs take shots at the Mad Cat. Not many hit, however; we’re shooting from a bad position. Hanzoku and Wizard are going to try to get closer; their mechs are well-armored and have legs fit for kicking.
Simona takes a few hits, and his poorly-repaired Ryoken doesn’t behave quite like he expects. It tips over and falls, and as he recovers his senses, he realizes his left leg is out of action.
Round 19
It looks like the end for the Mad Cat, and indeed it turns out to be. Wizard‘s barrage of medium laser fire chews through its engine and brings it down.
Damage, Injuries, Salvage
In the Crab, Milspec took heavy damage, while both Simona in the Ryoken and Severe in the Koshi lost legs. Despite that, injuries are light, and salvage is good. We take the Mad Cat and the Ryoken.
Both end up yielding good salvage. Unfortunately, we don’t manage to pull any intact ER PPCs out of the Mad Cat, but we do secure a Clan 375 XL engine, which we could probably trade for an Inner Sphere assault mech without too much difficulty.
The Ryoken ends up being an even better haul than expected. Its engine survived, too, and now we have a spare for Simona’s Ryoken. We also take an ER Large Laser from the wreckage.
Otherwise, the Mad Cat yields a brace of Streak SRM-6 launchers plus some ammo. We also strip a good deal of Clan Ferro-Fibrous armor off of the two mechs, which is important for our long-term capability to field the Koshi and the Ryoken.
Kill Board(s)
Last Battle
Wizard continues her charge up the leaderboard with another two kills this month. She’s tied for second in mech kills, and has a dominating lead when it comes to bringing down Clanners.
All-Time Leaders
“Rook” Ishikawa (26, 7 mechs, 2 Clan kills)
“Drake” Halit (14, 6 mechs, 2 Clan kills)
“Woad” Kohler (13, 5 mechs, 1 Clan kill)
“Carcer” Ngo (11, 5 mechs, 2 Clan kills)
“Wizard” Que (7, 6 mechs, 6 Clan kills)
“Teddy Bear” Jamil (5, 3 mechs, 2 Clan kills)
“Double Dog” Dare (5, 2 mechs, 1 Clan kill)
“Linebuster” Atkinson (5)
“Severe” Payne (4, 4 mechs)
“Milspec” Ortega (4, 1 mech, 1 Clan kill)
“Ker-Ker” Ec (3, 2 mechs)
“Hanzoku” Yuksel (3, 3 mechs, 2 Clan kill)
“Euchre” Kojic (2, 2 mechs)
Gwenael Hernandez (1, 1 mech, 1 Clan kill)
Simona (1, 1 mech, 1 Clan kill)
“Wojtek” Frajtov (1, 1 mech)
Status
As the Bastards scramble, as usual, to repair and refit before the next fight, something strange happens. On April 15th, the Clan Wolf forces raiding Tukayyid pull back to orbit. Soon after, our little backwater is suddenly the center of a tremendous amount of activity. Ships from six other Clans appear in orbit, along with a vast fleet of vessels with the ComStar insignia.
Our Rasalhague liaison bandies about terms like ‘batchall’ and ‘Trial of Possession’, which Hanzoku explains, and other terms like ‘the fate of Terra’ and ‘utter ruin if they lose’, which the rest of the Bastards understand just fine.
ComStar has taken over all defense arrangements against the Clans, and shunted the Rasalhague Republican forces off to provide security for civilians evacuated from the combat zones to come. We’re more than happy to babysit refugee convoys and sit out of the action for a bit. After all, we still get paid.
It is now May 1, 3052.
Contract Status
Our contract has been extended, but there’s a reasonable possibility it might be cut short early, unless ComStar loses.
Finances
We have 42.046 million C-bills on hand.
Repairs and Refits
With the obvious exception of the Awesome, which is still four months away from completion, the Bastards are at full strength. With the Clan heat sinks we salvaged from the Mad Cat and downed Ryoken, we were able to bring Simona’s Ryoken back to a full complement, and we even have five to spare.
As far as negatives go, several of the ER Medium Lasers in our Ryoken’s arm were total losses. At present, it has four instead of the design six, and we have no spares.
Training and Promotions
Teddy Bear acquitted himself well in combat, rapidly taking stock of the state of things when he arrived on the field. By taking command of the Rasalhague mechs, he managed to keep a full lance of them alive in the face of overwhelming Clan firepower. As such, he’s been promoted to Sergeant.
Mechwarrior Claims and Assignments
For the record, the following mechwarriors are claimed.
Yes, that’s right. Do you like the content you read here at Many Words and the Soapbox? Now you have a way to support it on an ongoing basis, and we’ve even cooked up some extras as a reward for your patronage.
Before we get to those, though, there’s the matter of the implied contract: if you’re to be our patrons, we owe you content. In the parvusimperator era, the Soapbox has been pretty good about that. Many Words hasn’t been. No more! As part of the Patreon launch, I’m aiming for 48 weeks of writing content per year.
Now, about those rewards.
First off, all patrons, no matter the amount, get access to the patron channel at the Many Words Press Discord server. There, you can rub elbows with us, in addition to your fellow patrons. All patrons also get exclusive access to the originally-posted drafts of since-published stories at Many Words Main.
Next up, the $5 tier. In addition to the above, you get access to special patron-only posts at Many Words and the Soapbox (which we’ll also put on the Patreon feed). At the Soapbox, you’ll get Deep Thoughts with Parvusimperator and sometimes Fishbreath: interesting facts which we can’t expand to a proper post. At Many Words, you’ll get a monthly exclusive piece of writing: either a vignette or a bit of setting or backstory I can’t fit into a story. Also, whenever I release an e-book while you’re a patron, you’ll get a free copy. Sign up before June 9th and I’ll send you the two I’ve released already.
Lastly, the $20 tier. You get all of the above, a special thank you on the website, and a podcast mention when you sign up. You also get a free copy of any print books I release while you’re a patron, as well as access to the full Many Words Press e-book catalog. Lastly, if there’s something you’d like us to write about at the Soapbox or talk about on the podcast, well, I can’t guarantee that we’ll actually do so, but we’ll certainly listen. We’re only human. Money talks.
What do we intend to do with your patronage? Good question.
First and foremost, we’ll pay for our web hosting expenses. $20 per month would cover it all—server, domain name, image hosting. (We consider the latter especially important for the Soapbox. A lot of the pictures parvusimperator posts are rare or hard to find, and by mirroring them we can pretty much guarantee they’ll be available for at least as long as we’re doing this.)
Once this has turned from a revenue-sink hobby into a revenue-neutral one, we have a few things in mind. At Many Words, we’ll be able to continue to hire cover designers for e-books and spend a bit on marketing, and hopefully make the fiction arm of Many Words Press self-supporting. At the Soapbox, our plans are a little more up in the air. We’d like to pay parvusimperator at some point, and we also have a few podcast studio items on the shopping list. Otherwise, what we can do depends on what we end up making, and we’ll have that discussion, both internally and with our patrons, when it becomes relevant.
Thanks for reading this far. If you like the sound of joining us as we go forward, click here and take a look at our Patreon.
Mortars are awesome, and a bigger mortar means more range and explosive power per shell. But a bigger mortar is a lot harder for troops to carry. The biggest commonly in use today are the 120 mm mortars like the Soltam K6. This weighs 319 lbs, and breaks down into the following components:
M298 cannon assembly (110 lbs)
M190 bipod assembly (70 pounds)
M9 baseplate (136 pounds)
That’s not going to be easy for infantry to haul. And it’s pretty natural, especially for motorized or mechanized infantry, to want to put mortars in a carrier vehicle. Let’s look at a couple American options. The basic idea here is pretty straightforward: take an APC, fit a retractable roof, and mount the mortar in the back. Surprisingly simple for units in the US Army inventory.
Our first example is the M1064. It’s based on the classic M113 APC. While the M113, even with the A3 improvements, is pretty vulnerable to modern battlefield threats these days, in the artillery role it’s perfectly adequate. The mortar is the 120mm M121, an American licensed copy of the K6. The M1064 also has a ring mount for a machine gun, and usually has an M2 mounted. Ammunition capacity is 69 mortar shells and 600 rounds for the M2.
The Israelis operate a similar system to the M1064, the Keshet. The key difference is that it’s equipped with the CARDOM mortar system, which automates the aiming of the mortar using a computerized fire control system. I would expect the number of stowed shells carried to be similar to the M1064.
Next we have the M1129, based on the Stryker APC. Again, there’s a retractable roof exposing a 120 mm M121 mortar. Some versions are also equipped with an additional, smaller mortar for dismounted use. This may be a 60mm or an 81mm mortar. If the M1129 is only equipped with a 120mm mortar, it will carry 60 120mm mortar shells. If a dismountable mortar is also carried, the supply of 120mm shells is reduced to 48. If a 60mm mortar is carried, 77 shells for it will be carried as well. On the other hand, if an 81mm mortar is carried, a supply of 35 shells will be provided for it. Note that if a dismount mortar is provided, this mortar cannot replace the 120mm for mounted use, and the vehicle crew is sufficient to use only one of the two provided mortars.
Here’s a handy chart of ammo capacities. The designations M1129-60 and M1129-81 are my own, used here for convenience. What dismount mortar, if any, is carried on an M1129 is based on its tasking in the organization table (i.e. whether it belongs to a rifle company, rifle battalion, or RSTA1 squadron) and is not indicated in its designation.
Vehicle
M1064
M1129
M1129-60
M1129-81
120mm shells
69
60
48
48
81mm shells
–
–
–
35
60mm shells
–
–
77
–
In terms of deployment, each company in a Striker Brigade Combat Team has two M1129-60s and each battalion has four M1129-81s as an organic component. An RSTA squadron gets six M1129s. A mechanized infantry battalion will get 6 M1064s. In the future, an AMPV-based mortar carrier will replace the M1064.
Reconnaissance, Surveillance, and Target Acquisition. They’re organized in the cavalry model (hence “squadron” instead of “battalion”). One RSTA squadron functions as the recon element for a brigade. ↩
Anytime I hear the words “milspec AR-10” my teeth get set on edge. There’s no such thing. I’m gonna repeat that.
There is no such thing as a “milspec AR-10”.
Got it? It should be pretty clear. No. Such. Thing.
Let’s start with what exactly is “milspec.” You may have guessed it’s short for “military specification,” and you’d be correct. For the US Army (and some others), they like to take ownership of certain products. Sometimes there are competitive bids. For the M4, there’s a specification of what exactly an M4 is, and then the US Army can have companies bid on how much it will cost to make a certain number of rifles to that spec. The milspec is owned by the military (in general).
So there’s no “milspec AR-10” because no major military adopted the AR-10 and cemented the design that way. Emphasis on the and. Merely adopting the rifle is insufficient. The AR-10 was used by the Sudanese, Cubans, and the Portugese, but none of those made a spec. All of those arms were built by Artillerie Inrichtigen, which wasn’t able to get more contracts and stopped making AR-10s ages ago. Still no spec.
Things got confusing in the 1990s. By that time, Eugene Stoner was working for Knights Armament, and they made the SR-25, a modern take on the AR-10 design for use as a semiautomatic marksman’s rifle. This used the gas system improvements worked out on the AR-15 and had a number of parts shared with the then-issue M16A2. The magazine design is also used in DPMS’ AR-10-pattern rifles, among others, and you can find these magazines as “DPMS/SR-25” pattern.
There’s another pattern of magazines currently in use for AR-10-pattern rifles. This one is made, confusingly enough, by Armalite. The original Armalite company ceased operations in the early 1980s. The rights to the name were bought, and Armalite was relaunched in 1996, with a new AR-10 pattern rifle (among other things). At that time the 1994 Assault Weapons Ban was in effect in the United States. This bill prohibited the sale of new magazines with a capacity of more than 10 rounds, but older magazines that held more than 10 rounds could still be bought and sold. So (new) Armalite made magazines that had a common design with M-14 magazines, so buyers of their rifle could use existing, common M-14 magazines with a couple easy modifications. These are “Armalite” pattern magazines, and they’re not compatible with DPMS/SR-25 pattern magazines.
And no, neither DPMS nor Knights nor Armalite are responsible for any current milspec “AR-10-pattern” rifle.
