SATCOM in contested environments: PTW, protected tactical SATCOM, and pLEO

For most of the last two decades, tactical units treated satellite communications as a utility. A terminal was set up, a link came up, and the main planning worries were bandwidth allocation, look angles, and weather. That assumption no longer holds. Russia's war in Ukraine has shown jamming of commercial satellite links, a destructive cyberattack on a satellite network's ground segment, and the battlefield value of large commercial low Earth orbit (LEO) constellations, all in public view. U.S. defense intelligence reporting describes Chinese and Russian counterspace programs that include jammers aimed specifically at satellite communications.

The U.S. response is spread across several programs that are easy to confuse. The Space Force is fielding a new anti-jam waveform, building ground infrastructure to run it, and buying protected tactical satellites through a family-of-systems approach that was restructured in 2025. The Space Development Agency (SDA) is launching a proliferated LEO data transport layer. Commercial proliferated LEO (pLEO) services are being bought at scale through a contract vehicle whose ceiling grew more than tenfold in roughly a year.

This article lays out what is publicly known about each piece, where program status stands as of early October 2026, and what it means for a unit signal officer writing a primary, alternate, contingency, and emergency (PACE) plan. Everything here comes from open sources. Where a capability's details are not public, the article says so.

The three traditional military SATCOM categories

U.S. military SATCOM has long been organized into three mission categories. Each trades capacity, protection, and terminal size differently, and each has its own constellation, ground segment, and terminal family.

Wideband: WGS

The Wideband Global SATCOM (WGS) system is the high-capacity backbone. According to Air & Space Forces Magazine's WGS profile, ten WGS satellites are on orbit, operating in X-band (designed to augment and then replace the older Defense Satellite Communications System X-band service) and Ka-band (two-way Ka service plus augmentation of the Global Broadcast Service). Each WGS satellite provides roughly ten times the capability of a DSCS satellite. WGS is also an international program: Canada, Denmark, Luxembourg, the Netherlands, and New Zealand are partners, and Poland and Japan signed agreements to join in 2024.

WGS is optimized for throughput, not protection. Its transponded architecture makes it efficient for large data flows, but it was not designed with the anti-jam and low probability of intercept (LPI) features of the protected systems. That gap is exactly what the Protected Tactical Waveform and the Protected Tactical SATCOM satellites are meant to close, and the next WGS satellite is part of that plan. WGS-11 will host a dedicated Protected Tactical SATCOM prototype payload alongside its standard wideband mission. As of a May 2026 Aviation Week report, WGS-11 was manifested on a United Launch Alliance Vulcan and had not yet launched; Breaking Defense reported in March 2026 that a Vulcan grounding was likely to delay it.

Protected: AEHF and Evolved Strategic SATCOM

The Advanced Extremely High Frequency (AEHF) system is the protected, nuclear-survivable layer. Per the Space Force AEHF fact sheet, six AEHF satellites have launched, the last on March 26, 2020. AEHF is the follow-on to Milstar, provides secure, jam-resistant communications for high-priority ground, sea, and air users, supports strategic nuclear operations, and offers data rates from 75 bits per second to roughly 8 megabits per second. International partners also use it.

Those data rates are the important number for tactical planners. AEHF buys protection with bandwidth. It is the right link for the messages that must get through under any condition, not the link for full-motion video or a brigade's data backhaul.

The AEHF successor is Evolved Strategic SATCOM (ESS). In July 2025 the Space Force awarded Boeing a $2.8 billion contract for the first two ESS satellites, with an option for two more and first spacecraft delivery expected in 2031, according to The Defense Post. ESS is described as the primary strategic SATCOM for nuclear command, control, and communications (NC3). Details of its protection features are largely not public, and the reporting notes the design incorporates classified technologies. It is a strategic system first; tactical users should not plan around ESS access in the near term.

Narrowband: MUOS and legacy UHF

The Mobile User Objective System (MUOS) is the narrowband UHF layer that serves dismounted and small-platform users. Air & Space Forces Magazine lists four operational satellites plus one on-orbit spare, launched between 2012 and 2016, with coverage from about 89.5 degrees north to 65 degrees south. MUOS uses a Wideband Code Division Multiple Access (WCDMA) payload that delivers cellular-like voice, chat, and data over military UHF, and the satellites also carry a legacy UHF payload compatible with older UHF Follow-On terminals. The same profile reports that the Space Force plans two additional satellites by 2030 and that Canada reached initial operational capability on MUOS in June 2024.

UHF matters because it works through foliage and weather and requires only small, low-gain antennas. It is also where demand chronically outstrips supply, a point the next section and the terminal section return to.

Category	Primary system	Strength	Main limitation for tactical users
Wideband	WGS (X and Ka-band)	High capacity	Limited inherent anti-jam and LPI protection
Protected	AEHF, then ESS	Jam resistance and nuclear survivability	Low data rates, scarce access, strategic priority
Narrowband	MUOS and legacy UHF	Small terminals, works on the move	Oversubscribed legacy channels and slow terminal fielding

The threat: jamming, cyber, and counterspace

A satellite link has several points of attack: the uplink, the downlink, the spacecraft, the ground segment, and the networks that manage terminals. Public reporting since 2021 includes examples of nearly all of them.

Uplink and downlink jamming

Uplink and downlink jamming are the oldest and cheapest threats, and they behave differently. An uplink jammer transmits toward the satellite. On a transparent, or "bent-pipe," transponder, the satellite amplifies whatever arrives in its passband, so a successful uplink jammer can degrade service for every user sharing that transponder across the beam, not just users near the jammer. Uplink jamming requires the jammer to be within the satellite's receive beam and to have enough power to compete at the satellite, which is a significant engineering task against a geosynchronous spacecraft.

A downlink jammer transmits toward the ground terminals. It only affects terminals within its own footprint, but it can be small, mobile, and cheap because it competes against a weak signal that has traveled tens of thousands of kilometers. For a tactical unit, downlink jamming is the threat most likely to show up on a particular hill on a particular day.

Waveform and payload design are the main electromagnetic protection (EP) answers. Frequency hopping spreads the signal across a wide band so a jammer must cover far more spectrum. Processed payloads, like those on AEHF, demodulate and regenerate signals onboard rather than simply amplifying them, which keeps uplink interference from being passed straight to the downlink. Narrow or nulling antennas reduce gain in the jammer's direction. Each of these has costs in bandwidth, power, or terminal complexity, which is why protection and capacity have historically been traded against each other.

Public examples are no longer hypothetical. The Defense Intelligence Agency's Challenges to Security in Space 2022 report, summarized by U.S. Indo-Pacific Command in April 2022, states that China has deployed jammers to deny satellite communications and GPS. The Secure World Foundation's 2025 Global Counterspace Capabilities assessment, as reported by Breaking Defense in April 2025, describes Russia as the leading practitioner of satellite communications and GPS jamming, including against Ukraine's Starlink access, and reports a Russian system called Kalinka that is claimed to locate devices linked to Starlink terminals within about 15 kilometers. The same report summary notes that the International Telecommunication Union expressed "grave concern" in 2024 about harmful interference from Russian territory affecting French and Swedish satellites, and that the report's overall assessment is that "everyone is jamming."

The Kalinka report deserves attention for a reason beyond jamming. A SATCOM terminal is an emitter. Whatever protects the link does not automatically protect the terminal's location. A unit that has solved its jamming problem can still be found by its emissions.

Cyber attack on the ground segment

The most consequential SATCOM attack of the Ukraine war so far did not touch a satellite. On February 24, 2022, the day of the full-scale invasion, attackers exploited a misconfigured VPN appliance to reach the management segment of Viasat's KA-SAT network, then pushed commands that overwrote flash memory on large numbers of residential modems and rendered them inoperable. The Record reported that Viasat confirmed security firm SentinelOne's analysis identifying the wiper malware, called AcidRain, and that the attack also caused malfunctions in 5,800 Enercon wind turbines in Germany. At the time of that reporting, the U.S. government had not formally attributed the attack.

The lesson is that the network management plane, the terminal software, and the supply chain are part of the attack surface. Anti-jam waveforms do nothing against a command that bricks the modem.

Counterspace weapons

Destructive anti-satellite (ASAT) capability is also public record. On November 15, 2021, Russia destroyed its own Cosmos 1408 satellite with a direct-ascent missile, creating more than 1,500 pieces of trackable debris and forcing crew aboard the International Space Station to shelter, according to Defense News. The Secure World Foundation summary also notes Chinese rendezvous and proximity operations in 2024 involving five satellites at separations of less than a kilometer.

For tactical planning, destructive ASAT is mainly a strategic risk. A handful of high-value geosynchronous satellites concentrate capability, which is the core argument for proliferation, whether through SDA's government constellation or commercial pLEO. Jamming and cyber are the threats a battalion is far more likely to encounter on a given day.

The Protected Tactical Waveform

The Protected Tactical Waveform (PTW) is the centerpiece of the U.S. approach to tactical anti-jam SATCOM. MIT Lincoln Laboratory, which has been central to its development, describes PTW as "a modern, anti-jam, low-probability-of-intercept waveform" intended to let warfighters operate through electromagnetic attack in contested environments (MIT Lincoln Laboratory, 2025).

The important design choice is that PTW is a waveform, not a satellite. It runs on ground terminals and ground hubs, which means it can be used over satellites that were not built for it. PTW's current home is WGS, and public descriptions say it is intended for future use over commercial SATCOM, future U.S. military constellations, and international partner constellations. That decoupling is what lets the Space Force add protection to the large WGS investment and to commercial capacity, instead of waiting for an entirely new protected constellation.

The July 2025 demonstration

Space Systems Command (SSC) reported a PTW demonstration with joint warfighters on July 14 to 16, 2025. According to SSC and Lincoln Laboratory, it included:

Frequency hopping at varying interference levels.
Over-the-air operations through five PTW-enabled terminals.
A secure voice over IP call.
A "ground bounce" through a commercial SATCOM satellite, connecting one constellation to another through the Protected Tactical Enterprise Service joint hub.

Production-representative PTW modems used in the event came from the Protected Tactical Service Field Demonstration effort. Lincoln Laboratory also noted that a prototype PTW key management system received a 2025 R&D 100 Award, and that the lab uses a Multi-Band Test Terminal to test PTW terminals and hubs.

Specific PTW performance figures, such as hop rates, processing gain, or achievable data rates under jamming, have not been published, and they should not be assumed.

Protected Tactical SATCOM as a family of systems

The Space Force acquires protected tactical SATCOM as a family of systems, and the family was restructured in July 2025. Knowing which piece is which avoids a lot of confusion in briefings.

PTES: the ground side

The Protected Tactical Enterprise Service (PTES) is the ground infrastructure that runs PTW. SSC describes a phased approach: Phase 1 broadcasts PTW over WGS, and Phase 2 extends PTW to commercial satellites and to the Protected Tactical SATCOM space segment. SSC also states that the Navy Wideband Anti-Jam Modem System, the Air Force-Army Anti-jam Modem (A3M), and international partners depend on PTES for PTW ground infrastructure. In other words, the service modem programs are the terminal end, and PTES is the hub and management end. Both have to be fielded for PTW to reach a user.

PTS-R: canceled and deferred

Protected Tactical SATCOM-Resilient (PTS-R) was intended to put PTW-capable, jam-resistant payloads into orbit as an operational follow-on to the prototypes. In July 2025, SSC announced that it had terminated the PTS-R competition and that full PTS-R capability would be delivered through a new acquisition strategy in the future. The remaining family elements named by SSC are PTS-Global (PTS-G), PTES, Enterprise Management and Control (EM&C), A3M, and the PTS Prototype (PTS-P) effort. Program executive officer Cordell DeLaPena Jr. said the Space Force had "initiated a new approach to bound cost and technical risk while rapidly delivering incremental capability." Air & Space Forces Magazine reported the cancellation on July 7, 2025, and said the service would focus instead on operationalizing the prototype satellites.

PTS-P: the prototypes

Two prototype efforts exist. Boeing is building prototype payloads hosted on WGS-11 and WGS-12. Northrop Grumman is building a free-flying prototype on an ESPAStar-HP bus. Launch dates have slipped. In January 2025, Air & Space Forces Magazine reported that both prototypes were scheduled to launch in 2025; SSC's July 2025 restructuring statement referred to a launch "next year." By May 2026, Aviation Week reported that both companies' prototypes were scheduled for launch, on-orbit demonstration, and testing no earlier than 2027. The same report said the Space Force had awarded Northrop Grumman a $398 million "Enhanced PTS-P" contract on May 15, 2026, for a second free-flyer on a GEOStar-3 bus, with launch no earlier than 2030.

PTS-G: the global constellation

PTS-G is the effort to buy small, PTW-capable protected satellites in geosynchronous orbit using commercial baseline designs. In July 2025, SSC awarded an initial delivery order worth $37.5 million in total to five companies, Viasat, Northrop Grumman, Astranis, Intelsat General, and Boeing, for design maturation and demonstrations, and projected a first PTS-G launch in 2028 (SmallSat News, July 2025).

In June 2026 the program moved to production. Breaking Defense reported that Viasat and Intelsat received awards worth a combined $437.7 million for two "Swarm 1" satellites operating in X-band and military Ka-band. Viasat's own June 11, 2026 release describes its satellite as a dual-band, maneuverable "mini-GEO," with ground stations and five years of operations support, and states initial operating capability no earlier than 2029. Viasat also cites a PTS-G IDIQ ceiling of $4 billion across awardees. The difference between a 2028 launch target and a 2029 initial operating capability is consistent: launch, checkout, and integration take time. Planners should read both dates as targets, not commitments.

What the restructuring means in practice

The net effect is that, through at least 2027, PTW users will rely on PTW running over WGS (and potentially commercial satellites under PTES Phase 2) rather than on purpose-built protected tactical satellites. That is real protection in the waveform, but the satellites themselves are still conventional transponded spacecraft. The PTS-P prototypes are expected no earlier than 2027, and the first PTS-G production satellites target 2028 or later. Any briefing that implies a fielded protected tactical constellation today is ahead of the public record.

SDA's Proliferated Warfighter Space Architecture transport layer

The Space Development Agency is building the Proliferated Warfighter Space Architecture (PWSA), a LEO constellation organized into layers and deployed in two-year "tranches." The Transport Layer is the communications backbone. SDA describes it as providing "assured, resilient, low-latency military data and communications connectivity worldwide to a full range of warfighter platforms" (SDA).

What the Transport Layer carries

Per the Space Force's September 2025 launch release and Spaceflight Now's coverage, Tranche 1 Transport Layer satellites carry:

Link 16 tactical data link capability, with regional persistence for tactical data channels including Link 16 expected beginning in 2027.
Ka-band radio frequency links.
Optical (laser) communications terminals for satellite-to-satellite mesh networking.

Link 16 from space is the part tactical users should watch most closely. It means aircraft, ships, and ground units already equipped with Link 16 terminals could, in principle, exchange tactical data beyond line of sight through LEO relays without a separate SATCOM terminal. How that will work operationally, including network management and which terminals will be supported first, has not been described in detail publicly.

Status through July 2026

Tranche 0, the demonstration tranche, launched across 2023 and 2024 with 27 satellites, 19 of them Transport Layer. Tranche 1 consists of 126 Transport Layer satellites, 28 Tracking Layer satellites, and four missile defense demonstration spacecraft. The first Tranche 1 launch, 21 York Space Systems Transport Layer satellites, flew on a Falcon 9 on September 10, 2025.

The cadence did not hold. SDA had planned roughly monthly launches, but Air & Space Forces Magazine reported that after the first two launches in fall 2025, a nine-month pause followed technical and operational challenges, with fixes made to ground systems and satellites already in orbit. The third launch, another 21 York-built Transport Layer satellites, flew July 16, 2026. SDA Director Gurpartap Sandhoo said, "The goal here is not to launch on a monthly cadence," emphasizing readiness over schedule. Tranche 1 is expected to begin providing operational capability in 2027.

The laser link question

The GAO has flagged laser communications as the main technical risk. In GAO-25-106838 (February 2025), the GAO found that as of December 2024, Tranche 0 contractors had demonstrated only a small fraction of planned laser communications capabilities. One contractor had demonstrated three of eight planned capabilities, another one of eight, and the remaining two none. GAO recommended that SDA demonstrate laser communications before finalizing Tranche 0 efforts and before making further investments in later tranches, noting that SDA had already awarded roughly $10 billion for Tranches 1 and 2.

For a user, that matters because optical crosslinks are what let the mesh route traffic across the constellation without landing it at a ground station in theater. If crosslinks underperform, the Transport Layer leans more on ground infrastructure, which is both a capacity constraint and a target.

Commercial proliferated LEO and the lessons of Ukraine

Starlink in Ukraine

Starlink's use in Ukraine is the most visible example of commercial pLEO in a war. SpaceX began providing terminals in 2022. In June 2023, the Pentagon confirmed it was buying Starlink services for Ukraine, describing satellite communications as "a vital layer in Ukraine's overall communications network," while declining to disclose cost or duration. By April 2025, Reuters reporting summarized by Silicon UK put the number of Starlink terminals in Ukraine at roughly 50,000.

Three Ukraine lessons stand out from the public record.

Proliferation and software agility blunt jamming. In April 2022, Dave Tremper, then the EW director in the Office of the Secretary of Defense, described how SpaceX countered a Russian jamming attempt with a rapid software change. "How they did that was eye-watering to me," he said, adding that the department needed that same agility (Business Insider via Yahoo News, April 2022). A constellation of thousands of satellites, each in view for minutes, with phased-array terminals and frequent software updates, is a harder target than a single geosynchronous transponder. It is not immune, as the continued Russian effort described in the Secure World Foundation report shows.

The provider controls the network. SpaceX President Gwynne Shotwell said on February 8, 2023, at the FAA's Commercial Space Transportation Conference, that Starlink "was never intended to be weaponized" and that Ukrainians had used it in unintended ways (C4ISRNET, February 2023). In February 2026, Ukraine and SpaceX implemented a whitelist that blocked unregistered terminals, cutting off Russian forces that had been using Starlink, including on attack drones. Ukrainian Defense Minister Mykhailo Fedorov said that whitelisted terminals were working and Russian terminals had been blocked (CNN Newssource via KRDO, February 2026). The same reporting noted that some Ukrainian units also lost connectivity during the transition. The episode cuts both ways: centralized control let the provider deny the enemy, and it also means a military user's access depends on a commercial company's registration system, policy, and decisions.

Diversity has value. Germany has paid for Ukrainian access to Eutelsat OneWeb service. As of April 2025, fewer than 1,000 OneWeb terminals were reported in Ukraine, with plans for 5,000 to 10,000 more, a small fraction of the Starlink fleet. A second pLEO provider is useful precisely because it is a different network, operator, and policy chain, but a provider that is a few percent of the fleet is a backup, not a substitute.

U.S. purchasing: the pLEO IDIQ

The U.S. buys commercial pLEO through an indefinite delivery, indefinite quantity contract now managed by the Space Force's Commercial Satellite Communications Office. The vehicle was awarded in August 2023 with a $900 million ceiling and 16 initial awardees, including OneWeb (Potomac Officers Club, 2023). By late 2024 the ceiling had been raised to $13 billion. Air & Space Forces Magazine reported in April 2025 that about $660 million in task orders had been issued, most of them to SpaceX, among 20 approved vendors. Col. A.J. Ashby, then senior materiel leader for strategic SATCOM, said, "What we don't want to do is find ourselves in a situation where you have a single commercial provider." SpaceX formed its Starshield unit for national security customers in December 2022.

Commercial pLEO brings high throughput, low latency, and small, inexpensive terminals. Its limitations for contested operations are equally specific:

It does not natively carry PTW, and its anti-jam and LPI properties are set by the provider, not the user. Details for Starshield are largely not public.
Terminals are active emitters, and the Kalinka reporting suggests adversaries are working to geolocate them.
Service availability depends on provider policy, licensing, and regional authorization, as the Ukraine whitelist showed.
Ground gateways, network operations centers, and user management systems are cyber targets, as the KA-SAT attack showed for a geosynchronous commercial network.

Terminals and the ground segment: the recurring bottleneck

The single most consistent finding in two decades of GAO work on military SATCOM is that satellites arrive before the terminals and ground systems that users need to exploit them.

GAO's synchronization findings

In October 2009, GAO-10-55, Challenges in Aligning Space System Components, reviewed eight major DoD space systems and found misalignment between satellites and ground or user assets in six of them. For MUOS, user terminals were delayed about seven years, with fewer than 20 percent of the planned terminals expected to be available at initial capability. For AEHF, the Family of Advanced Beyond Line-of-Sight Terminals (FAB-T) was projected to be only 2 percent fielded at initial capability. WGS was flying without functional mission planning software. GAO recommended synchronization standards tied to delivering capability to warfighters, a single oversight authority across segments, and operational testing with production-representative equipment.

The MUOS case shows how long the problem lasts. In September 2021, GAO-21-105283 reported that DoD had invested $7.4 billion in MUOS and that the full constellation had been on orbit for more than four years, yet the services' delayed delivery of compatible radio terminals meant users still relied on the oversubscribed legacy UHF system. MUOS offered a tenfold increase in capacity that was largely going unused. GAO recommended that DoD explore additional near-term narrowband options and update narrowband requirements that had not changed since 2010. GAO later closed both recommendations as implemented, noting that DoD pursued terminal acceleration and completed a requirements update endorsed in October 2023.

Why it keeps happening

The structural reasons are well documented. Satellites, ground control, and terminals are usually managed by different program offices, often in different services, with different budgets and schedules. The Space Force buys the spacecraft; the Army, Navy, Marine Corps, and Air Force buy most terminals and integrate them into vehicles, ships, and aircraft. A satellite program can be on schedule while the terminal program sits behind a platform integration cycle that the satellite office does not control.

The protected tactical effort shows the same pattern in its structure. PTW needs PTES hubs, the service modem programs (A3M and the Navy Wideband Anti-Jam Modem System), key management, and, eventually, PTS-G and PTS-P satellites. Each element is a separate program with its own schedule. The SDA Transport Layer needs Link 16 terminals with the right software and network management, plus Ka-band terminals and ground entry points. Commercial pLEO needs accredited terminals, cyber authorization, and contract vehicles. The publicly available record does not include a single integrated fielding schedule showing when a given unit will hold all of these.

What to ask about terminals

For program offices and units evaluating these capabilities, the useful questions are concrete:

Which terminals in the unit's current inventory can load PTW, and when do the modem upgrades arrive?
Which ground hub or gateway does the link depend on, and where is it?
Who manages the terminal's keys, software updates, and network registration, and how does that work when the unit is disconnected?
Has the terminal been tested against representative jamming in a production configuration, not just a demonstration build?

PACE planning implications for tactical units

A PACE plan lists primary, alternate, contingency, and emergency means of communication for each critical information flow. CISA's guidance on PACE planning, written for the emergency communications community but directly applicable here, makes two points that matter for SATCOM: each level should use a different transmission path than the levels above it, and organizations should define specific trigger points for moving from one level to the next (CISA, Leveraging the PACE Plan into the Emergency Communications Ecosystem). Both are where SATCOM PACE plans most often fail.

Do not count two SATCOM links as independent

A plan that lists commercial pLEO as primary and WGS as alternate looks diverse on paper. In practice, both may share a failure mode. Both rely on a terminal that emits and can be located. Both may run back to the same headquarters network or gateway. A downlink jammer near the unit may affect both if they share bands or if the jammer is wideband. Real independence comes from different orbits, different frequency bands, different operators, different ground entry points, and ideally a non-SATCOM path such as line-of-sight radio, high frequency (HF) radio, or terrestrial networks.

Match the link to the message

Not every information flow needs the same protection. A practical approach is to tier flows by how much they must survive:

Must get through under any condition: command and control, fires coordination, and reporting. Plan these on the most protected path available to the unit, which today may be AEHF access for units that have it, PTW over WGS as modems field, and HF as a non-space backup.
High volume, tolerant of interruption: intelligence products, imagery, logistics data, and administrative traffic. Commercial pLEO and unprotected WGS are well suited here, with an explicit plan for what stops flowing when those links drop.
Tactical data links: as SDA's Link 16 capability becomes available beginning in 2027, it may provide beyond line of sight for Link 16-equipped platforms. Treat it as a capability to exercise and validate before relying on it in a plan.

Write switching triggers in advance

Degradation under jamming is often gradual and ambiguous. Throughput falls, latency rises, and links drop intermittently. Without pre-agreed triggers, units can spend hours troubleshooting a link that is being deliberately attacked. Useful triggers are observable at the terminal: sustained loss of lock, signal-to-noise below a set threshold, or failure of a scheduled communications check. The plan should also state who has authority to shift the unit to a lower PACE level and how the shift is communicated, since the primary path may be the one that just failed.

Plan for emissions control

Because SATCOM terminals are detectable, the PACE plan should include emissions control (EMCON) conditions. That can mean limiting transmit time, moving terminals away from command posts, using remote antennas, preferring directional links, and accepting that some periods will be receive-only. LPI waveforms such as PTW reduce detectability, but published details do not allow anyone outside the program to quantify by how much. Planners should not assume any SATCOM link is undetectable.

Account for provider and cyber dependencies

For commercial service, the plan should identify which provider, which contract or task order, which terminals are registered, and what happens if a provider policy, licensing decision, or registration change interrupts service. For any SATCOM path, it should identify who can push software or configuration changes to the terminal and how a compromised management channel would be detected and isolated.

Train in degraded conditions

The most reliable predictor of PACE performance is whether a unit has practiced it. Exercises should include realistic jamming using electromagnetic attack assets, deliberate loss of the primary SATCOM path, and full transitions through all four PACE levels. Units should also practice the unglamorous parts: re-pointing antennas, loading new keys, and passing critical traffic over HF when every satellite path is unavailable.

What to watch

Several milestones will show whether the protected and proliferated architecture arrives on the timelines currently described in public:

WGS-11 launch. It carries the first Boeing PTS-P payload and adds WGS capacity. As of May 2026 it was manifested on Vulcan and had not launched.
PTS-P on-orbit demonstrations. Both prototypes are publicly described as no earlier than 2027. Results will indicate whether PTW-specific payloads deliver more protection than PTW over a conventional transponder.
PTS-G Swarm 1. Viasat and Intelsat satellites target launch in 2028 and initial operating capability no earlier than 2029.
PTES Phase 2. Extension of PTW over commercial satellites would be the first time protection could be layered onto commercial capacity at scale.
Service modem fielding. A3M and the Navy Wideband Anti-Jam Modem System determine when PTW reaches users. Public schedules for unit-level fielding are limited.
SDA Tranche 1 capability. Launch completion, laser crosslink performance, and the start of Link 16 service in 2027 will show whether the Transport Layer is usable by tactical forces.
pLEO vendor diversity. Whether task orders spread beyond one provider under the $13 billion pLEO vehicle, and whether additional constellations reach operational service.

Bottom line

The U.S. is moving from a SATCOM architecture built around a few large, high-value satellites to one that layers an anti-jam waveform over existing and commercial capacity, adds small protected geosynchronous satellites, and leans on proliferated LEO for resilience and throughput. The direction is sound and is consistent with what the Ukraine war has shown about jamming, cyber, and proliferation.

The timelines are the caution. The PTS-R competition was canceled in July 2025, the PTS-P prototypes have moved to no earlier than 2027, PTS-G production satellites target 2028 or later, and SDA's Tranche 1 paused for nine months before resuming in July 2026. GAO's record on terminal synchronization suggests the user equipment will lag the satellites again unless the services fund and field modems on the same schedule.

For a tactical unit, the near-term answer is not a new satellite. It is a PACE plan built on genuinely independent paths, tiered by message priority, with written switching triggers, emissions discipline, awareness of provider and cyber dependencies, and regular practice under realistic electromagnetic attack. That plan will work regardless of which program milestones slip.