Air Force Seeks Industry Input on Universal Mobile Communications for Special Warfare
The Air Force is using an RFI to shape a vehicle-agnostic communications and command-and-control system for Special Warfare teams, with responses due December 11, 2026. A draft requirements document and draft RFP are tentatively planned for FY2027, but acquisition approval, funding, and contracting strategy remain unresolved.
Key Signals
- Air Force seeks MCS-U industry feedback by December 11, 2026
- Vehicle-agnostic mobile C2 capability targets Special Warfare and TACP teams
- RFI requests input on mesh networking, mounting, antennas, weatherproofing, and power
- FY2027 draft requirements and RFP are tentative pending approvals and funding
- Contracting strategy remains open and may be informed by industry responses
The U.S. Air Force is seeking industry input for the Mobile Communication System-Universal (MCS-U), a planned mobile communications and command-and-control capability for Air Force Special Warfare teams. The RFI describes a mobile C2 node able to pass “critical voice, data, and video communications” between Tactical Air Control Party (TACP) operators while they are driving or parked. Responses are due December 11, 2026. This is market research intended to inform requirements—not a solicitation, contract award, or confirmation that the program will proceed on a set schedule.
MCS-U is described as an evolution of mobile communications capabilities already used in Air Force Special Warfare vehicles. The RFI says previous systems were designed and customized for specific vehicles; the new objective is to make systems “mix and match” across platforms “as much as possible.” That vehicle-agnostic goal could favor adaptable equipment, interfaces, mounting approaches, and integration designs over solutions tied to a single vehicle configuration. The system is also expected to connect with the Advanced Battle Management System (ABMS), which builds the Department of the Air Force Battle Network and supports the Pentagon’s Joint All-Domain Command and Control effort.
The operational use case matters to prospective suppliers. TACP operators call in airstrikes from forward positions and are typically embedded with Army soldiers and Marines, according to the Air Force webpage cited in the source. The communications suite therefore needs to support operators across changing mobility conditions and vehicle types. The TACP-Modernization program office is asking companies to describe available capabilities and components, including weatherproof kits, vehicle-agnostic mounting, mesh network connectivity, antenna auto-tracking, and power-supply integration alternatives. These topics offer industry a direct opportunity to inform how the Air Force frames technical requirements.
The potential platform range is broad, extending from Joint Light Tactical Vehicles and Infantry Squad Vehicles to MRZRs, Special Operations Craft-Riverine, Amphibious Combat Vehicle families, other Marine vehicles, and commercial trucks and SUVs. However, the acquisition pathway remains uncertain. The RFI states that the program is pending formal acquisition and funding approval, and the Air Force has not selected a contracting strategy; that approach is expected to take shape based on industry responses. Draft system requirements and a draft request for proposals are tentatively planned for FY2027, but the notice says requirements are not yet fully developed and would appear in an RFP “if issued.” Contractors should use the response period to provide practical, platform-spanning input while treating later milestones as tentative.
- RFI response deadline: Submit industry feedback by December 11, 2026; the request is for market research, not a contract solicitation.
- Program objective: Develop MCS-U as a vehicle-agnostic mobile C2 node for Air Force Special Warfare teams.
- Communications: The envisioned system passes critical voice, data, and video between TACP operators while driving or parked.
- Interoperability: The system is expected to connect with ABMS, the Department of the Air Force Battle Network, and the broader Joint All-Domain Command and Control effort.
- Potential platforms: The RFI identifies Joint Light Tactical Vehicles, Infantry Squad Vehicles, MRZRs, SOC-R craft, ACV Family of Vehicles, Marine vehicles, and commercial trucks and SUVs.
- Technical feedback sought: Address weatherproofing, vehicle-agnostic mounting, mesh networking, antenna auto-tracking, and power integration.
- Operational context: TACP operators work from forward positions and are typically embedded with Army soldiers and Marines.
- Tentative next step: Draft requirements and a draft RFP are planned for FY2027, subject to change.
- Acquisition uncertainty: Formal acquisition approval, funding approval, and a contracting strategy remain unsettled; the Air Force may shape its approach using RFI responses.
Agencies
- U.S. Air Force
- Department of the Air Force
- U.S. Department of Defense
- TACP-Modernization program office