Category Modeling, Simulation & Wargaming

Presentations from HAAC – Fitting Lanchester Equations

The third presentation of the first day was given by Dr. Tom Lucas of the Naval Post-Graduate School (49 slides):  Fitting Lanchester equations to time-phased battle data

The two of the databases used for this work were the Ardennes Campaign Simulation Data Base (ACSDB) and the Kursk Data Base (KDB). I was the program manager for both of these efforts.

———-

We had a total of 30 presentations given at the first Historical Analysis Annual Conference (HAAC). We have the briefing slides from most of these presentations. Over the next few weeks, we are going to present the briefing slides on this blog, maybe twice a week (Tuesdays and Thursday). In all cases, this is done with the permission of the briefer. We may later also post the videos of the presentations, but these are clearly going to have to go to another medium (Youtube.com). We will announce when and if these are posted.

The briefings will be posted in the order given at the conference. The conference schedule is here: Schedule for the Historical Analysis Annual Conference (HAAC), 27-29 September 2022 – update 16 | Mystics & Statistics (dupuyinstitute.org)

The conference opened with a brief set of introductory remarks by me. The seven supporting slides are here: Opening Presentation

It was then followed by a briefing by Dr. Shawn Woodford on Studying Combat; The “Base of Sand” Problem: 20220927 HAAC-Studying Combat

The second presentation of the first day was given by me. It is here (45 slides): Data for Wargames (Summary) – 2

Presentations from HAAC – Data for Wargames

The second presentation of the first day was given by me. It is here (45 slides): Data for Wargames (Summary) – 2. This presentation was originally prepared for a conference in Norway in December 2021. It was based upon my books America’s Modern Wars and  War by Numbers.

—————

We had a total of 30 presentations given at the first Historical Analysis Annual Conference (HAAC). We have the briefing slides from most of these presentations. Over the next few weeks, we are going to present the briefing slides on this blog, maybe twice a week (Tuesdays and Thursday). In all cases, this is done with the permission of the briefer. We may later also post the videos of the presentations, but these are clearly going to have to go to another medium (Youtube.com). We will announce when and if these are posted.

The briefings will be posted in the order given at the conference. The conference schedule is here: Schedule for the Historical Analysis Annual Conference (HAAC), 27-29 September 2022 – update 16 | Mystics & Statistics (dupuyinstitute.org)

The conference opened with a brief set of introductory remarks by me. The seven supporting slides are here: Opening Presentation

It was then followed by a briefing by Dr. Shawn Woodford on Studying Combat; The “Base of Sand” Problem: 20220927 HAAC-Studying Combat

Presentations from the first Historical Analysis Annual Conference (HAAC) – Studying Combat

We had a total of 30 presentations given at the first Historical Analysis Annual Conference (HAAC). We have the briefing slides from most of these presentations. Over the next few weeks, we are going to present the briefing slides on this blog, maybe twice a week (Tuesdays and Thursday). In all cases, this is done with the permission of the briefer. We may later also post the videos of the presentations, but these are clearly going to have to go to another medium (Youtube.com). We will announce when and if these are posted.

The briefings will be posted in the order given at the conference. The conference schedule is here: Schedule for the Historical Analysis Annual Conference (HAAC), 27-29 September 2022 – update 16 | Mystics & Statistics (dupuyinstitute.org)

The conference did open with a brief set of introductory remarks by me. The seven supporting slides are here:

Opening Presentation

It was then followed by a briefing by Dr. Shawn Woodford on Studying Combat; The “Base of Sand” Problem:

20220927 HAAC-Studying Combat

 

The Defensive Value of Urban Terrain According to the QJM

According to the Trevor Dupuy’s Quantified Judgment Model (QJM), as described in the book Numbers, Predictions and War (1985 edition), the value of defending is urban terrain is between 1.82 to 2.24. This is a multiplier to the combat value of the defender.

This consists of the value of a defense posture (Table 5, page 230)…

                         Force Strength

Attack:                        1.0

Defense (hasty)          1.3

Defense (prepared)    1.5

Defense (fortified)      1.6

Withdrawal                  1.15

Delay                            1.2

 

…Multiplied by the value of terrain (Table 1, page 228):

Terrain Characteristics

Rugged-Mixed          1.5

Rolling-Mixed           1.3

Urban                        1.4

 

Now, the entire terrain table is not included here, there are 14 terrain types in the table. I just included the three that were discussed in the previous post: The Defensive Value of Urban Terrain | Mystics & Statistics (dupuyinstitute.org). As can be seen, there is not a lot of difference between Rolling-mixed to Urban to Rugged-Mixed. Clearly there is an advantage to defending in urban terrain, but no more so than other good defensive non-urban terrain.

Keep in mind that with the QJM, it only requires superior combat value to move forward. So, if a force is doing a prepared defense (1.5) on urban terrain (1.4), which equals 2.1; then a force with more than 2.1 times more combat power will be able to advance against them. 

Now, this is a game construct, not a piece of analytical work. It really has no other validity than any other game construct. For example, in “classic” Avalon Hill (AH) games the urban terrain multiplies the defense by 2. But their Combat Result Tables (CRT) are still based upon a three-to-one rule, so attacking urban terrain with twice the force on the AH 1-to-1 combat results table was a truly risky proposition. The attack still has a 50% chance of losing. The AH CRT is here: Force Ratios and CRTs | Mystics & Statistics (dupuyinstitute.org). Whereas with the QJM, the attack is going to go forward and with roughly equal casualties.

Still, the QJM is a model that has been extensively validated three times, so there are some reasons to believe that some parts of it may be close to reality. But we have not validated the model to a large collection of urban engagements. This would be useful to do but it does take a little effort.

Common Use, Lineage, and Lethality

Below is an article from the UC Davis Law Review that references Trevor Dupuy 75 times, references me 9 times and references Susan Rich 8 times. The article is Common Use, Lineage, and Lethality by Darrell A. H. Miller & Jennifer Tucker: Microsoft Word – 55-5_Miller_Tucker.docx (ucdavis.edu).

It still seems strange to me that a group of legal scholars are actually paying attention to the Theoretical Lethality Index (TLI) that Trevor Dupuy came up with in 1964, but we are flattered by the mention. This has been discussed before: Opinion: Now that guns can kill hundreds in minutes, Supreme Court should rethink the rights question | CNN. And then there is this: The Left’s Shark-Jumping Conclusions On NY Carry Case – Bearing Arms. These are all linked to this blog post: What Is The Relationship Between Rate of Fire and Military Effectiveness? | Mystics & Statistics (dupuyinstitute.org).

I will be speaking at the Center for the Study of Guns and Society at Wesleyan University in Middleton, Conn. on 14-15 October 2022. The link to it is here: Center for the Study of Guns and Society – Wesleyan University-based center dedicated to interdisciplinary humanities study and teaching on the social and cultural history of firearms (gunsandsocietycenter.com). Click on this: Quantifying Arms Lethality in Historical Perspective – Center for the Study of Guns and Society (gunsandsocietycenter.com). Should be interesting. I have never actually attended an academic conference.

I gather the conference is open invitation:  Conference – Center for the Study of Guns and Society (gunsandsocietycenter.com).

Drone Survivability

On 30 June, we posted a guest post from William (Chip) Sayers on Scoring the KF51 Panther and the Future of the MBT | Mystics & Statistics (dupuyinstitute.org). The article generated some discussion on the blog which he partially responded to, but he felt the need to assemble a proper response. This is included below:

KF51 Panther. Image Credit: Industry Handout.

——–William (Chip) Sayers———————-

After submitting my post last week, we had a little internal debate among ourselves concerning the viability of drones and their ability to displace the MBT as the apex predator of the battlespace. What follows is a rather lengthy expansion of my reply to my colleagues.

I have written quite a bit on other fora about our over estimation of what drones – particularly of the Medium Altitude/Long Endurance (MALE) and High-Altitude/Long-Endurance (HALE) varieties – are capable of doing in the battlespace. I believe them to be virtually unsurvivable in a modern air defense environment — though I may have to up their chances a bit, given that they Russians have not, so far, swept them from the skies of Ukraine.  

The Turkish TB-2 is almost an exact analog of our MQ-1 Predator, and our experience with that system has been very instructive.  Iranians and Saddam-era Iraqis have been able to shoot them down, despite their general incompetence. The target drones we use to train fighter pilots and air defense crews in live-fire weapons employment exercises are far more challenging targets. This is because the Predator and other similar drones have an exceedingly limited ability to see the world around them. The pilot flies using a fixed nose camera with what is commonly referred to as a “soda-straw” view forward. The enemy interceptor (be it a fighter or a SAM) has to literally fly directly in front of the drone for the pilot to see it. The weapon systems operator is a bit better off as his camera is mounted in a turret, but again, it has to be pointed to within a few degrees of the interceptor, and coordination between the two “aircrew” in such a scenario is problematic, at best. In practice, however, they rarely even perceive when they are under attack and can’t do anything about it if they do: large, light-structured, straight-wing drones are not designed for maneuverability and have very little chance of survival, once targeted. Watching drone footage of an armed fighter-interceptor flashing by, and then, after a few seconds, seeing the video feed turn to static gives one a supreme feeling of helplessness.

Worse, drone accident rates are high and often due to things a pilot could avoid, if he were on board. Flying from a remote ground station just does not give a pilot the feel and visual scan that he would otherwise have. In the 1990s, we lost the entire Predator fleet over former-Yugoslavia, mostly to icing that could easily have been avoided if the aircraft were manned. An onboard pilot might have picked up the subtle clues through his controls and might have seen the ice beginning to form. With such information, he might have been able to simply change his altitude and continue the mission, or abort and save a valuable platform. While drone accident rates have come down from the disastrous levels of the 1990s, they remain at least twice those of the worst of USAF fighters.

Taken together, these drones are less survivable in a combat situation and succumb to accidents at a high rate making them much less effective and much more expensive than people generally believe. 
 
On the other hand, the Switchblade and the HERO-120 are in a completely different category. They are both significantly smaller than a MALE (length 4.25 vs 21 feet, wingspan of ~4 vs 39 feet and a weight of 50 vs 1,500lbs) and they use electric motors, making them acoustically undetectable and difficult to find with IR sensors. Shooting down one of these things flying just above the treetops isn’t impossible – if you see it – but it will be significantly more difficult than shooting down a MALE flying fat, dumb and happy at 15,000 feet. 

Nevertheless, these small drones are not without their vulnerabilities. They are already threatened by Counter-Rocket and Mortar (C-RAM) systems, designed to shoot down individual indirect fire rounds fired at fixed targets. These systems already acquire and track small-signature targets, so kamikaze drones won’t present the challenge they do to more traditional air defense systems. The main drawback that will keep C-RAM systems in check is their expense and limited mobility. More menacing in the not-too-distant future will be ground-based Laser air defense weapons when they come into operational use. A larger aircraft can take a hit in the fuselage or wing, and as long as it doesn’t contain a vital system at that point, it may be able to shrug off the hit. Not so with mini-drones where their small size will work against them as a hit anywhere will not require much dwell time to do catastrophic damage. Virtually any part of the drone’s volume will contain vital systems. So, look for kamikaze drones as the first target of air defense Lasers when they finally come online.

Some have talked of an anti-drone role for systems such as the Switchblade 300. Presumably, this would involve acquiring the target drone, flying a collision course and detonating the warhead within lethal range of the enemy craft. This is no easy feat with no dedicated acquisition and tracking means and working in three dimensions. This might work better against a less maneuverable, large target like a HALE or MALE UAS, but altitude and airspeed limitations work against the mini-drones here. Generally speaking, the smaller the drone, the less power and thus speed and altitude capability are available.

The final threat to the kamikaze drone is the most readily available and, perhaps, the most effective: jamming. These drones use radio signals to communicate with their operators and have little capability to operate autonomously, other than to cruise to a designated waypoint. If the link between drone and operator is broken, the drone is effectively neutralized. It is possible to give these drones an autonomous target recognition capability, but this takes sensors, computing capacity and electrical power, all of which require space in an already packed airframe. It is also has somewhat less than ideal reliability and represents a tangible threat to friendly forces.

Historically, whenever electro-magnetic jamming has come into play, it has always become a game of measure vs. countermeasure. Once started, the cycle cannot be relied on to stabilize in favor of one side or the other for very long. The implication is that kamikaze drones will have their moments of relative effectiveness, but they are unlikely to be swept from the sky by any single solution and thus will be an endemic feature of the battlespace for the foreseeable future.

 

Scoring the KF51 Panther and the Future of the MBT

KF51 Panther. Image Credit: Industry Handout.

Another William (Chip) Sayers post. This is his fifth post here. He will be presenting at our Historical Analysis conference: Who’s Who at HAAC – part 1 | Mystics & Statistics (dupuyinstitute.org).

———————–William (Chip) Sayers——————

Scoring the KF51 Panther and the Future of the MBT


The German arms manufacturer Rheinmetall recently announced the rollout of their newest Main Battle Tank, the KF51 Panther. The new tank has captured the attention of the world largely because its main armament represents the first major improvement in that area in over 40 years, but also because — let’s be honest — the prospect of a new German Panther prowling the battlefields of Europe just sounds incredibly sexy.

Panther Ausf D number 435 of the 51st Panzer Battalion Kursk (source: World War Photos 2013-2022, contact: info(at)worldwarphptos.info).

While the Panther is not yet approved for large-scale production by the Bundeswehr — it is, in fact, an alternative to an ongoing Franco-German Leopard II/AMX-40 Le Clerc replacement program — the buzz created by the name alone may propel it to top of the list. Rheinmetall’s announcement make it clear that the major selling features center around its new 130mm gun and autoloader (reducing the crew size to three), integral HERO-120 reconnaissance/weapon UAS, a new, more powerful diesel power plant, an active protection system and integrated vehicle electronics.

When a major new weapons system like the Panther enters the scene, I immediately reach for my TNDM Operational Lethality Index (OLI) creation spreadsheet and see how it scores. First, because it may come in handy in future modeling, but also because going through the process and examining the outcome has a tendency to cut through my preconceptions and replace them with a more balanced perspective. So, I thought I was share my insights with this post.

In creating a score for a tank, the first thing one must do is define and score the weapons systems. This presents a couple of challenges in the case of the KF51. First, there is little publicly available data on the Rh-130 gun. It will obviously be more powerful than the Rh-120 on the Leopard II, but we need more specificity to create a reasonable score. By scouring everything available on the web, I found claims of an effective range of 4,000 meters. I could not find an exact number for muzzle velocity, but 2,000 m/sec seems to be within the range of most speculation and seems, if anything, comfortably conservative. These are the really important numbers, so the main gun looks reasonably accounted for.

However, another aspect of the Rh-130 is its autoloader. Rheinmetall apparently believes that handling 130mm rounds inside a turret is too difficult to be done efficiently by a human loader and has substituted a mechanical device that can load the gun more quickly and without tiring over time. The downside of the autoloader is its small “ready use” capacity of 20 rounds. The OLI of a gun is based on its hourly rate of fire, which means that barrel heating and wear, and human fatigue need to be accounted for — and, it must be said, such numbers are not easily found. Fortunately, graphs for rate of fire based on shell-size are provided if reliable information is unavailable. On the other hand, magazine capacity is not the primary determinator of rate of fire. The rules for building a gun score state that one should not consider logistics as a limitation. In other words, it is as though the gun is on the range with an unlimited amount of ammunition available. Thus, while limited magazine capacity may yield a negative modifier, it isn’t an absolute limiter.

More difficult to calculate is the HERO-120. Not only are hard numbers difficult to come by, the TNDM has difficulty coming to grips with this system. The HERO-120 can serve as a basic reconnaissance UAS, but the TNDM has no explicit reconnaissance function — the model assumes that a given force has its doctrinal recon means operating in a competent manner. If this isn’t the case for some reason, the penalty would be assessed as a decrement in that side’s Combat Effectiveness Value (troop quality) or a
CEV bonus to the opposing side.

There are several ways we can score the HERO-120: as an infantry weapon, an ATGM, an artillery weapon, or as an aircraft. There is no clear-cut answer to how its score it. The HERO-120 can be used as an anti-personnel/light-materiel weapon that could be considered a long-range mortar within the confines of the model. Scoring it this way, the HERO-120 has an impressive Operational Lethality Index (combat power score) of 792. This compares to an AKM assault rifle at .16, an M-2HB .50 cal heavy machinegun at 1.2, or an M-43 120mm mortar at an OLI of 145.

Scoring it as an ATGM yields an OLI of 257. This compares well with the Russian Konkurs (113), Kornet-E (175), US TOW-2B (136) and Javelin-C (246). This is primarily due to the HERO-120’s much greater range. Scored as an artillery system — much like an MRL rocket or SSM — the HERO-120 has an OLI of 782. This compares to the 227mm HIMARS MLRS at 338, or a Russian 9K720 Iskander SSM at 184. Compared to the basic HIMARS, HERO-120 has better range and is much more accurate. Its major advantages over the Iskander are its guidance system and its much smaller size that makes it handier to reload, giving it a higher volume of firepower.

The obvious course is to score it as a fixed-wing aircraft, but this is a bit trickier than it appears at first blush. The warhead must be scored as if it is a bomb or missile, then the UAS has to be scored as an aircraft carrying a single “bomb.” Both the “weapon” and the “aircraft” must have a range (in the case of the weapon) or a radius (in the case of the aircraft). For the weapon range, I estimated the range at which the UAS would lock-on to the target and begin to make its terminal dive. For the radius of the aircraft, I simply used the Line-of-Sight distance, which is approximately 40km. The UAS’ loiter time is one of its defining characteristics, but there’s no satisfactory way to handle it directly in the TNDM model. This will bear some exploration for the future. In the meantime, the Operational Lethality Index came to only 2.8 for the HERO-120 (approximately half the score of an under-rifle grenade launcher). By comparison, the MQ-1 Predator UAS has an OLI of 161, while a MQ-4 Reaper scores a 933 OLI. Clearly, this does not adequately reflect the contribution of this unique and versatile weapon. As the intent (aside from its reconnaissance function) is clearly as an antiarmor weapon, I decided to use the ATGM value for the HERO-120.

The TNDM makes provision for advanced composite or reactive armor, giving AFVs with these characteristics a 10% bump up compared to those with simple rolled homogenous armor. Active Protection Systems (APS) that actually intercept an incoming round before it hits the vehicle were not in widespread use. They should probably give a tank with RHA at least a 10% increase in value, but it is probably insufficient when coupled with advanced composite armor as used on the KF51. It is possible that the correct solution is to add 10% for each one of these characteristics, but this hasn’t been validated (to my knowledge) and therefore I give a maximum of 10% for advanced armor. It remains to be seen how well APS systems will hold up under actual combat conditions and given their complexity, they could underperform considerably. Therefore, I’m not overly concerned that we’re lowballing the Panther’s score by essentially ignoring this characteristic. If we get a large test case where APS work reliably, are not overwhelmed by multiple incoming shots and don’t prove to be far more danger than they are worth to their accompanying infantry, then we will have to revisit the subject.

Within the model, the Panther’s new power pack is measured by the speed it gives the vehicle and the fuel efficiency expressed in terms of combat radius. The numbers currently available turn out to be rather average for the type. It has been described as having a high power to weight ratio and this is generally a good thing. However, in the model vehicle weight translates directly to protection, thus a light-weight engine that doesn’t improve the speed or fuel efficiency of the vehicle is actually considered detrimental to protection. Given that many armored vehicles — the Israeli Merkava MBT being the outstanding example — incorporate the engine positioning as part of the protective package, it’s not too much of a stretch to justify the model’s view.

Advanced Vehicle Electronics (commonly known as “Vectronics”) are another unknown. Vectronics that merely provide the vehicle with, for example, improved night vision or allow the crew to be grouped into the hull for better protection is probably beneath the field of regard for the TNDM. However, networking vehicles with information-sharing technology must be addressed by the model, though it is probably best done as a modification to CEV.

In the 1970s, navies got into peer-to-peer information sharing, followed by air forces in the 1980s. This was a natural progression given the technical challenges involved. Land armies didn’t stick their toes in the water until the early 2000s, but the potential, if it can be made to reliably work under combat conditions, is profound. For thousands of years, the biggest fear and determinate of a commander’s actions was the necessity that he guess what was over the next hill. Just knowing with certainty where one’s own troops are, is a revolution in land warfare. Adding the enemy into this picture allows small, maneuverable forces to operate freely in enemy territory without fear of being caught and destroyed while maneuvering directly against enemy Centers of Gravity. In the September 1999 issue of Marine Corps Gazette, I wrote an article detailing how this kind of information could enable the USMC’s doctrine of Ship To Objective Maneuver could enable small, agile amphibious raids to execute their doctrine unencumbered by a large logistics tail.

With this in mind, it’s not so much the individual vehicle, but the entire force that exploits the information available. Therefore, it seems more fitting to adjust the unit’s CEV than to give a higher score to a vehicle whose crew might, or might not, be able to properly exploit the possibilities resident in the enhanced C3I equipment carried aboard the tank. A crew might not be properly trained or the force might be depleted to the point that the big picture information either doesn’t exist, or cannot be exploited effectively by an insufficient force. Thus, CEV enhancement is the best way to handle this capability.

All told then, what do we have? The KF51 Panther scores in at an OLI of 836. Not bad, but compared to the Leopard 2A6 at 800, the M-1A2 at 712, the Challenger II at 685, or the T-14 Armata at 963, it is not particularly impressive — hardly a game-changer. So, what does it take to build a game-changer?

My first attempt to answer this question was simple: Let’s put a really big gun on the Panther and see what that does. I replaced the 130mm gun with the Russian 152mm 2A83, a possibility for arming a future T-14 Armata II. After adding a couple of MT of weight and degrading top speed by 2 km/hr, the “Tiger” scored out at an OLI of 1015 — an increase of nearly 20%. However, even this massive upgrade in firepower did not yield a score that would dominate the battlefield. It would merely make a four-tank platoon the equivalent of an older five-tank platoon in firepower. Useful, but hardly a game-changer.

Next, I popped the turret off the Panther to create a “Jagdpanther,” armed with long-range loitering munitions scored essentially as ATGMs. I posited an 8-cell box launcher for the Switchblade 600 with two sets of reloads aboard and dual controls for the weapons for the tank commander and gunner. The engagement sequence would go something like this: Off-board recon and intelligence would be fed to the vehicle via information sharing networks and targets for individual vehicles would be assigned. The gunner would launch up to 8 loitering munitions and send them to their respective engagement areas via GPS guidance. As the UAS approach the target area some 25 minutes and 80km away, the gunner launches a second salvo of 8 and he and the commander divide up final guidance of the UAS as they attack their assigned targets. By the end of an hour, 24 UAS have been launched with perhaps as many as 20 enemy targets hit per firing vehicle. With this kind of potential, the “Jagdpanther” has an OLI of 1196, some 30% higher than the Panther, but still not earth-shattering.

Finally, as raw firepower alone did not appear to have the potential to revolutionize the armored fighting vehicle, I decided to explore advantages in operational and strategic mobility. Taking the US Army’s Stryker ICV as a base vehicle, I created the “Puma” wheeled tank destroyer, using the Switchblade loitering munition as the primary weapon and the 40mm automatic grenade launcher as the secondary. While it is not possible to armor a wheeled vehicle to MBT standards, the creation of Active Protection Systems might substitute for a brute-force approach of hanging tons of extra steel and laminates on the sides. If APS are as good as their manufacturers suggest, a light-weight vehicle may be able to stand in the line of battle as well as a much heavier MBT. All that might be needed is armor to defeat heavy machineguns and artillery fragments, saving tons of weight and considerable volume within the hull. In the early 2000s, the US Army was developing a family of combat vehicles that used alternate, high-tech armor packages to allow for a much lighter vehicle. Unfortunately, the Army couldn’t think past a 120mm gun, which incurred certain weight penalties of its own. When the Army retreated from its gamble on high-tech armor, the entire program collapsed. However, the time may have come to try this evolutionary stream, again.

With two 8-box launchers, a full set of reloads carried inside and stations for four gunners, the “Puma” scores out at a 1483 OLI. Finally, we have a vehicle that doubles the score of many extant MBTs. Not exactly groundbreaking in itself, but in a deployable package that can move great distances quickly on their own wheels? This just might be the revolution we’re looking for.

Clearly, the “Puma’s” score is the TNDM talking according to what the model values. But it does bring up interesting questions. How much is operational mobility worth? Being able to rush from one battlefield to the next is obviously a valuable asset. What about strategic mobility? It does no good to have heavy tanks at home if it takes six months for them to get to the hot-spot of the week. And if Bell/Boeing delivers on the idea of a VTOL C-130 (an advanced, four rotor development of the MV-22 Osprey)? The combination could be devastating. In my Marine Corps Gazette article, I posited that the Marines should drop their M-1s and substitute a much more supportable vehicle somewhat like the “Puma.” 23 years later, the Marine Corps is restructuring, a move that will divest them of their M-1 tank battalions. The Corps’ reasoning is that they need to radically lighten up their forces to play hit and run in a potential conflict with China in the Pacific islands. Losing the tanks (along with some of their tube-artillery and other items) not only reduces the sheer weight of these massive vehicles, but more importantly, the huge weight of ammunition and fuel these gas-guzzlers consume.

All of which begs the question: is the TNDM declaring the era of the tank over? Is the dinosaur of the lumbering MBT going to sprout wings and evolve into something new and different?

Maybe. Much of the push back against the idea in the post-Operation DESERT STORM 1990s was the theory that MBTs are intimidating to potential troublemakers in peace operations. But in an era where anything appearing on CNN with a turret is called a tank, are 70 tons worth of armored behemoth truly necessary for intimidation purposes? It seemed a poor argument then, and even less convincing now. In 2003’s Operation IRAQI FREEDOM, Republican Guard armored formations were broken up by air and artillery before they came into contact with US ground units such that we never ran into an RG unit larger than a company. So, for the last 3 decades, major force-on-force actions featuring MBTs seemed to be a thing of the past. Then Russia invaded Ukraine.

The ambiguity brought by this latest conflict presents a challenge to those who would make easy pronouncements about the future of warfare. On the one hand, tanks and other armored vehicles are in widespread use across Ukraine. On the other, tanks are meeting wholesale destruction by a wide variety of means, including those wielded by individual infantrymen. Regardless of the long-term utility of the MBT, it is clear that it no longer owns the battlespace like it did four decades ago, and isn’t likely to reclaim that position by hanging more armor on its sides or mounting a larger gun.

Traditionally, armored vehicles have been judged on their balance between three factors: firepower, protection and mobility. With a range of around 4km, the 130mm Rh-130 allows the Panther to dominate an area of 158km2 though its penetrative power vs other tanks is only evolutionary and is threatened by the active protection capability the Panther, itself employs. By contrast, the “Puma’s” reach is over 63,000km2 [km squared] ! As a top-attack system, the Switchblade will overmatch any top armor currently conceivable and is far less vulnerable to reactive armor and active protection systems as it adds the third dimension to the problem. The Panther carries 20 rounds in its autoloader, while the “Puma” has 32 rounds of ready ammo. It’s difficult to see how the traditional MBT wins the point for firepower.

While the Panther’s base armor greatly outperforms the “Puma’s,” it is, like all MBTs, vulnerable from the top, sides and rear where its armor is substantially thinner. Therefore, both vehicles would be significantly dependent on their APS, which does not necessarily depend on base armor to work. Perhaps more important, if it comes down to evading high-velocity gunfire from opposing MBTs, the “Puma” has significantly higher speed on the battlefield and potentially a lower profile for the enemy to shoot at. All things being equal, the combination of thick base armor and an APS is superior to thin base armor and an APS. Except, of course, for cost and the waste of resources if the APS is sufficient to defeat enemy attacks by itself. In the meantime, it carries a huge penalty to mobility at every level. The points for protection are then ambiguous.

As for mobility, a US Army Cold War era study estimated that tracks increase the terrain a vehicle can negotiate by only (if I recall correctly) about 5%. In the meantime, wheeled vehicles are far superior in operational and strategic mobility. Add to that the weight of an MBT vs. that of what is essentially an armored personnel carrier and there is no scenario where the Panther has an advantage at the operational or strategic level, and precious few where it may outperform the conceptual “Puma” on the tactical battlefield.

With one point clearly going to the wheeled vehicle, another strongly leaning that way, and the third a question mark, there is only one question left to us: Why are we playing with expensive and sluggish dinosaurs when we could be flooding the battlefield with ferocious stalking cats?

The Severskii Donets River Crossing Operation

This is another piece of TNDM analysis from William (Chip) Sayers. He will be doing a presentation at our Historical Analysis conference: Who’s Who at HAAC – part 1 | Mystics & Statistics (dupuyinstitute.org). Now, I have questioned the Ukrainian estimates of overall casualties: The Ukrainian casualty claims are inflated – part 1 | Mystics & Statistics (dupuyinstitute.org). This post by Chip Sayers makes the point that the estimates of 400+ Russian casualties in this river crossing operation is believable. 

The William (Chip) Sayers piece:


The objective of this set of model runs was to explore the failed Russian river crossing operation of the Siverskiy Donets.  Ukrainian photos of the battlefield aftermath showed vividly the carnage wrought by modern defenses when properly warned and deployed. 

Ukrainian reconnaissance detected the Russian preparations to cross the Siverskiy Donets at least 3 days prior to the river crossing operation, which gave them time to bring up reinforcements and prepare a defense.  According to uawardata.com, The 79th Ukrainian Air Assault Brigade was defending the sector, while one or two Battalion Tactical Groups from the 35th and 74th Mechanized Brigades of the 41st Combined Arms Army were in the area of the attack.  The Institute for the Study of War reports that it was a BTG from the 74th Mech Brigade that conducted the attack.

The vulnerability of attacking forces in a river crossing operation is such that surprise and support are necessary to preclude catastrophic losses.  Clearly, the Russian BTG failed to achieve surprise — it is unknown how well supported they were, but the scale of their losses indicates that whatever support they had was probably inadequate.

I set up the battle with the following forces:

Russian: one mechanized BTG from the 74th Mech Brigade with support from half the guns of the 120th Artillery Brigade (the 41st CAA’s sole artillery brigade) and 30 Mi-24 attack helicopter sorties.

Ukrainian: one battalion from the 79th Air Assault Brigade plus a battalion slice of brigade assets (the brigade apparently was covering a large frontage and probably couldn’t afford to devote more to the battle).  Assuming the Ukrainian Army productively used the warning time they had to bring up supporting fires, I gave the defenders an Urgan MRL battalion from the 27th Rocket Artillery Brigade.  Just for fun, I also gave them ~10% of the Switchblade “kamikaze” UAS that the United States has sent (100 x Switchblade 300 anti-personnel drones and 20 x Switchblade 600 anti-tank drones). 

The Siverskiy Donets is only about 50m wide at the crossing point, and the ground is heavily forested, though relatively flat.  As best as can be determined from aerial video imagery, the battlefield is actually too small to support an attacking battalion.  Soviet motorized rifle battalions attacked on a minimum frontage of 1 kilometer, while a Russian BTG is somewhat beefier organization.  The Siverskiy Donets makes a partial loop at the point of attack and a kilometer attack zone would have taken the entire frontage of the loop such that Russian troops on one side might have been firing into the faces of their compatriots attacking at the other end of the line.  This suggests that they probably attacked on no more than a single company frontage (400m), with four companies in echelon.  This is not a formula for success in an opposed river crossing.

For the base case, I did not give the Ukrainian side a CEV advantage, nor surprise to either side.

Results:

After a full day of battle on 11 May, the Russians were decisively repulsed, having lost 27% of their personnel, 80% of their armored fighting vehicles, 50% of their attack helicopters and 38% of their overall combat power.  This compares favorably to the ISW’s estimate of 458 casualties (the TNDM predicted 521) and 80 pieces of equipment, compared to the TNDM report of 89.  50% losses to the attack helicopter force is probably a bit overstated and could bear closer examination.

In contrast, the Ukrainians lost 6% of personnel (85 men), 2 AFVs and 6% of their combat power. 

This disparity in the loss of combat power to the two sides would have undoubtedly made another attempt to cross the river on the 12th a non-starter, even though some sources have reported it as a two-day battle.  If these losses are indeed indicative of what really happened, the second day’s attack could only have been carried out by the 35th Brigade’s BTG.  This would imply that not one, but two BTGs may have been wrecked in the Siverskiy Donets operation.

Run #2: While the force-to-space ratios don’t really support at two-BTG attack, it is possible that when the 74th Mech’s BTG was rendered combat-ineffective, the 35th’s BTG was passed through the 74th to renew the attack.  By including both BTG’s in the Russian Order of Battle and throwing in the balance of the 120th Artillery Brigade, we can see the impact of a rough 2:1 numerical advantage for the attacker’s side.

As it happens, even this reinforcement only yielded a combat power ratio of 1:1, which did not allow for a successful crossing of the river.  Russian casualties were somewhat lower, but still higher than the defender’s losses.  Both sides took about 7% personnel losses, but the Russian units had roughly double the personnel, so took 271 casualties as opposed to only 110 by the Ukrainians.  The Russians lost 29 AFVs to the Ukrainians’ 3, but this is deceptive as the defenders had only a small number of tanks to lose — their 3 AFV losses represented 45% of their starting force.  The bigger story is that the Russian’s lost 15% of their combat power, while the Ukrainians lost just 8%, thus ensuring the attackers would never make it across the river without significant reinforcement.

Run #3: Some sites have reported that the operation continued into a second day, so the third run was essentially the first run with a second day’s extension where the 35th Brigade’s BTG took over the fight.  I also postulated that it would be too expensive for the Ukrainians to devote a second package of Switchblade drones to battle.  Therefore, the defenders’ combat power was weakened in comparison to the first day’s battle, despite their low losses.

After extracting the losses to the defenders and not adding the Switchblade package back in, the fresh 35th Bde BTG replaced the broken 74th’s BTG with exactly the same combat power.  Thus, we have a fresh second echelon committed to battle against a moderately depleted defender. 

Results:

Without their Switchblade drones, the 79th Air Assault Brigade defenders were unable to repulse the second echelon, though the attack was only able to make 350 meters beyond the river’s edge.  In doing so, the Russians lost another 323 men, a third of their AFVs and 14% of their combat power.  The defenders lost 130 men, 2 AFVs and 1% of their combat power.  All told, in the two-day battle the Russians lost nearly 850 men, 45 AFVs, had one BTG rendered combat ineffective and barely gained a toehold on the south side of the Siverskiy Donets. 

Run #4: Clearly, a CEV advantage to the Ukrainian side would merely make the Russian defeats in Runs #1 and #2 worse, so they needn’t be explored further.  Run number 4 was run as run #3, but with a Ukrainian CEV of 1.2.

Results:

On day 1, the Russians lost 57% of their combat power and 124% of their AFVs, indicating they their armored vehicles wouldn’t have survived to the end of the day, thus the battle would have likely ceased less than 16 hours in.  After such a slaughter, it is questionable if the Russians would have tried it again the next day with the second BTG.

On day 2, the Russian second echelon managed to take the crossing site to the same depth as run #3, but lost 50% of their AFVs and 20% of their combat power in doing so.  The casualty list after two days would have totaled over a thousand Russian soldiers.  Technically, this might be called a Russian “victory,” but without a substantial exploitation force behind them, it would surely be a pyrrhic one.

Run #5: The next few runs explored the idea that the Russians not only failed to achieve the needed surprise, but were, in fact, surprised by the resistance they ran into.  Again, runs #1 & #2 were sufficiently adverse to the attacker that they needn’t be explored further.  This is a re-run of run #3 with minor surprise by the defenders.

Results:

While the 74th’s BTG was thoroughly destroyed (41% personnel losses, 161% of AFVs and 71% of its combat power lost), interestingly, the 35th’s BTG made the same gains and losses were almost exactly what they were in run #4.  This surprising result is because surprise degrades over time, and the second day of minor surprise essentially equates to the Ukrainian CEV of 1.2 from run #4.

Run #6: Given this, run #6 was done with substantial surprise.  Not surprisingly, the 74th BTG was obliterated in short order, losing over 54% of its personnel, 271% of its AFVs and 115% of its combat power.  It could be scratched out of the Russian OOB after half a day’s fight.  The 35th BTG, however, still made it across the river, albeit at some cost.

Run #7: Run 7 was done with complete surprise — not a likely situation, but one explored for completeness.  The results were much the same, with the 74th annihilated after just a few hours, while the 35th persisted in gaining the far bank of the Siverskiy Donets.  However, at a cost of 1/3rd of its personnel, all of its AFVs and 35% of its combat power, the BTG would have been hors de combat until a rest and refit period were accomplished.

At this point, I ran several sensitivity exercises without using the Switchblade package from the first day of the battle, but including variations of surprise and CEV.  No amount of surprise was capable of repulsing the attack and only a Ukrainian CEV of 1.5 proved sufficient to keep the Russians on their side of the river without the use of the kamikaze UAVs.  As a large influx of combat power in some form was needed to rebuff the attack, I made a final run with the entire 79th Air Assault Brigade in place of the Switchblades.  This did, indeed, defeat the single BTG on day 1 of the battle with losses comparable to those estimated to have actually been incurred by the Russian force.  In other words, it took a force three times the size of our estimate to successfully defeat the river crossing without extraordinary support.  This would, of course, have been advantageous for defending a day 2 attack by the 35th BTG had it occurred, since the entire brigade would remain in place, as opposed to the Switchblade package that we posited would be too expensive to recreate for the second day’s battle.

Conclusions:

Once again, the TNDM has demonstrated that the reported results of this battle are entirely consistent with historical outcomes — nothing too unusual or particularly remarkable happened here.

Also, Russian tactical incompetence is once again the key to interpreting the results of this battle.  Had the Russians achieved the prerequisite surprise, things would have gone very differently.  A final model run with the shoe on the other foot confirms this.

Finally, the impact of a single weapon system — in this case the Switchblade kamikaze UAS — proved pivotal.  Essentially a round of ammunition, these killer drones significantly boosted the combat power of the defenders.  However, once expended, the defending units went back to their organic firepower, which was insufficient to hold the line.  This underscores the importance of a steady, sustainable supply of weapons and logistical support from NATO and other countries sympathetic to the Ukrainian cause.

A Strategy Page Article and Trevor Dupuy and Validation

An article appeared this week in the Strategy Page, which while a little rambling and unfocused, does hit on a few points of importance to us. The article is here: Murphy’s Law: What is Real on the Battlefield. Not sure of the author. But let me make a few rambling and unfocused comments on the article.

First they name-checked Trevor Dupuy. As they note: “Some post World War II historians had noted and measured the qualitative differences but their results were not widely recognized. One notable practitioner of this was military historian and World War II artillery officer Trevor Dupuy.”

“Not widely recognized” is kind of an understatement. In many cases, his work was actively resisted, with considerable criticism (some of it outright false), and often arrogantly and out-of-hand dismissed by people who apparently knew better. This is the reason why four chapters of my book War by Numbers focuses on measuring human factors.

I never understood the arguments from combat analysts and modelers who did not want to measure the qualitative differences between military forces. I would welcome someone who does not think this is useful to make the argument on this blog or maybe at our historical analysis conference. Fact of the matter was that Trevor Dupuy’s work was underfunded and under-resourced throughout the 33 years he pursued this research. His companies were always on the verge of extinction, kept going only by his force of will. 

Second, they discussed validation and the failure of the U.S. DOD to take it into account. Their statement was that “But, in general, validation was not a high priority and avoided as much as possible during peacetime.”  They discuss this as the case in the 1970s, but it was also true in the 1980s, the 1990s and into the current century. In my first meeting at CAA in early 1987, a group of analysts showed up for the purpose of getting the Ardennes Campaign Simulation Data Base (ACSDB) cancelled. There was open hostility at that time to even assembling the data to conduct a validation among the analytical community. We have discussed the need for validation a few times before here:  Summation of our Validation Posts | Mystics & Statistics (dupuyinstitute.org) and here: TDI Friday Read: Engaging The Phalanx | Mystics & Statistics (dupuyinstitute.org) and here: TDI Friday Read: Battalion-Level Combat Model Validation | Mystics & Statistics (dupuyinstitute.org) and here: No Action on Validation In the 2020 National Defense Act Authorization | Mystics & Statistics (dupuyinstitute.org) and in Chapters 18 and 19 of War by Numbers.

Nominally, I am somewhat of a validation expert. I have created four+ large validation databases: the Ardennes Campaign Simulation Data Base, the Kursk Data Base, and Battle of Britian Data Base (primarily done by Richard Anderson) and the expansion of the various DuWar databases. I have actually conducted three validations also. This is the fully documented battalion-level validation done for the TNDM (see International TNDM Newsletters Volume I, numbers 2 – 6 at http://www.dupuyinstitute.org/tdipub4.htm), the fully documented test of various models done in our report CE-1 Casualty Estimation Methodologies Study (May 2005) at http://www.dupuyinstitute.org/tdipub3.htm and the fully documented test of division and corps level combat at Kursk using the TNDM (see Chapter 19 of War by Numbers and reports FCS-1 and FCS-2 here: http://www.dupuyinstitute.org/tdipub3.htm). That said, no one in DOD has ever invited me to discuss validation. I don’t think they would really agree with what I had to say. On the other hand, if there have been some solid documented validations conducted recently by DOD, then I certainly would invite them to post about it to our blog or present them at our Historical Analysis conference. There has been a tendency for certain agencies to claim they have done VVA and sensitivity tests, but one never seems to find a detailed description of the validation they have conducted.

I will not be specifically discussing these databases or validation at the Historical Analysis conference, but my discussion on the subject in War by Numbers and in over 40 blog posts on this blog.