5th Multi-Domain Task Force

The 5th MDTF is the service-retained one. It is planned for Fort_Bragg, North Carolina, tied to the Global_Response_Force and pointed at the USCENTCOM area of responsibility, which means it is the only MDTF designed to go somewhere it is not already assigned. Full operational capability is planned for FY2028, making it the last of the five and the one most exposed to budget and force structure churn.

FieldValue
TypeMulti_Domain_Task_Force, theater-level formation
Planned home stationFort_Bragg, North Carolina
AlignmentService-retained, not assigned to a theater army
Likely combatant command focusUSCENTCOM
Associated formationXVIII_Airborne_Corps and the Global_Response_Force
Status as of Aug 2026Not activated
Full operational capabilityPlanned FY2028

Status

The Army’s February 27, 2024 white paper Army Force Structure Transformation allocated three MDTFs to USARPAC, one to USAREUR-AF, and one that “will be service-retained with a likely focus on the CENTCOM area of responsibility.” CRS describes the 5th MDTF as planned for Fort_Bragg and intended to concentrate on regions as determined, with full operational capability by FY2028. It has not activated.

Lt. Gen. Gregory_Anderson, senior commander at Fort_Bragg and commanding general of the XVIII_Airborne_Corps, publicly stated that the task force is earmarked for Fort_Bragg. The Army’s proposed FY2027 budget request includes funding for MDTF structure. Personnel strength has not been published.

One concrete data point exists in the air defense fielding plan: CRS lists 2-44 ADA at Fort_Bragg as the 5th MDTF’s IFPC_Increment_2 battalion, scheduled for FY2030. That is the only public confirmation of a named subordinate unit and it postdates the FY2028 FOC target by two years, which is a useful indicator of how the Army sequences headquarters activation ahead of full equipping.

What “Service-Retained” Means Here

The first four MDTFs are assigned to theater armies and habitually support one combatant command. The 5th is not. It stays under Army control and deploys where directed, in the same logic as the Global_Response_Force built around the 82nd_Airborne_Division.

That distinction drives design. A theater-assigned MDTF can forward-station launchers, negotiate host nation access years ahead, and build a persistent sensing picture of one adversary. A globally responsive MDTF has to be air-deployable, has to work against whatever Anti_Access_Area_Denial problem it is handed, and has to plug into a joint force it has not exercised with. The tension between those two designs is unresolved in public doctrine.

The USCENTCOM focus is a judgment about where episodic long-range fires and theater sensing would be most useful outside the two pacing-threat theaters: Iranian missile and drone complexes, the Red Sea, and the Levant.

Expected Structure

No published table of organization. The generic MDTF template implies a headquarters battery, a Multi_Domain_Effects_Battalion, a Long_Range_Fires_Battalion with HIMARS, Typhon, and Dark_Eagle batteries, an Indirect_Fire_Protection_Capability_Battalion (2-44 ADA), and a Brigade_Support_Battalion.

Why It Matters

It is the marginal MDTF, and marginal units get cut. With FOC in FY2028 and its air defense battalion not fielded until FY2030, the 5th MDTF is the formation most likely to be deferred, restructured, or converted if the Army’s force structure math changes again. Anyone modeling out-year Long_Range_Precision_Fires demand should treat its fifth battery set as the least certain.

Fort_Bragg is consolidating multi-domain and expeditionary functions. The installation already hosts the XVIII_Airborne_Corps, USASOC, and, since December 2025, USAWHC under the Army_Transformation_Initiative. Adding an MDTF concentrates a large share of the Army’s globally deployable command capacity in one place.

A CENTCOM-focused MDTF would be the first to operate against a theater where the adversary shoots back with mass rather than precision. Iranian and proxy drone and rocket volumes stress the Indirect_Fire_Protection_Capability_Battalion and Counter_UAS side of the task force far more than the Pacific problem does, which is a different requirements pull than the one shaping the Pacific MDTFs.

See Also