OFFSETOFFSET

Anti_Access_Area_Denial

3 min read

Anti-Access / Area Denial (A2/AD)

A2/AD is the term of art for what an adversary builds to make it expensive for the United States to show up and expensive to stay. It is the stated reason the Multi_Domain_Task_Force exists, the organizing threat in Multi_Domain_Operations, and the phrase that appears in the Army’s own definition of what an MDTF is for.

FieldValue
TypeThreat concept and term of art
Anti-accessCapabilities that prevent or slow deployment into a theater
Area denialCapabilities that constrain freedom of action once inside
Principal casesChinese systems in the Western Pacific, Russian systems in Europe
Countering conceptMulti_Domain_Operations

The Distinction

Anti-access targets getting there. Long-range anti-ship ballistic and cruise missiles, submarines, mines, counter-space weapons, and attacks on the ports, airfields, and logistics networks the joint force needs to flow into a theater. Anti-access is about time and distance: it does not have to defeat U.S. forces, only delay their arrival past the point at which they matter.

Area denial targets operating once there. Integrated air defense, shorter-range fires, electronic warfare, and counter-ISR that constrain movement, emission, and basing inside the theater.

The Army’s formulation is layered standoff: a stack of overlapping sensor and shooter systems arrayed at increasing ranges, so that penetrating one layer exposes the force to the next.

Why It Drives Army Force Structure

The Army’s problem with A2/AD is existential in the budget sense. If the fight is about reaching across ocean distances to strike missile batteries and sensors, that is a Navy and Air Force problem. The Army’s answer, articulated in the March 2021 Chief of Staff paper, is that land-based launchers inside the adversary’s range rings are cheaper, more numerous, harder to find, and harder to sink than ships and aircraft, and that a land component can hold contested terrain and chokepoints in ways air and naval forces cannot.

That argument produces specific structure and specific programs:

  • The Multi_Domain_Task_Force, defined in Army doctrine as designed to “synchronize precision effects and precision fires in all domains against adversary anti-access/area denial (A2/AD) networks”
  • Dark_Eagle and Typhon, ground-launched systems that can reach into the layered defense from land
  • The Multi_Domain_Effects_Battalion, because dis-integrating a sensor and command network requires organic ability to find it
  • IFPC_Increment_2 and Counter_UAS, because operating inside area denial means being shot at

Penetrate, Dis-integrate, Exploit

Multi_Domain_Operations frames the counter-A2/AD sequence in three moves. Penetrate the outer standoff layer with long-range fires and non-kinetic effects to create windows. Dis-integrate the adversary’s integrated system by breaking the links between his sensors, command nodes, and shooters rather than attriting each shooter individually. Exploit the resulting freedom of maneuver.

The Kill_Chain implication is that the highest-value targets are not launchers but the things that tell launchers where to shoot. That is why an MDTF carries a space company and an information company alongside its missiles.

Cautions on the Term

A2/AD is contested language. Critics inside the U.S. defense community argue it reifies an adversary capability into a wall, encourages threat inflation, and describes a Chinese or Russian system in terms those militaries do not use for themselves. Some senior U.S. officers have discouraged the phrase for those reasons. It nonetheless remains embedded in Army doctrine, in the formal definition of the Multi_Domain_Task_Force, and in CRS reporting to Congress, which is why it is worth knowing precisely rather than avoiding.

See Also

Graph View

Backlinks