The satellite is already in the building at Cape Canaveral. On April 7, ViaSat-3 F3 rolled into Launch Complex 39A after a three-week cross-country journey from Boeing's El Segundo, California facility, where it had been assembled and tested. By April 20, when Viasat announced the launch date to investors, the hardware was no longer a concept or a development milestone—it was a physical object sitting on a mobile launch platform with a countdown window that opens April 27 at 10:21 a.m. EDT. For a space tech sector accustomed to slippage, this is notable. This is what a real manifest looks like.
ViaSat is completing a constellation that has taken longer than anyone expected. ViaSat-3 F1 entered commercial service in 2024 after years of delays, integration hiccups, and technical refinements that pushed the program into territory typically reserved for troubled military satellites. F2 is still in the midst of in-orbit testing—the reflector has deployed successfully, but there remain months of validation work before it can hand over capacity to customers. F3, now four weeks from launch, will sit in geostationary transfer orbit for several months under its own electric propulsion before taking its assigned slot over Asia-Pacific. Once it arrives, Viasat will operate the first global three-satellite Ka-band constellation designed to shift capacity dynamically across its footprint in response to real-time demand. The company is betting this completes a financial and strategic recovery that began when the company wrote down nearly $3 billion in satellite program costs five years ago.
The launch vehicle is SpaceX's Falcon Heavy—a manifest swap from an earlier Ariane 64 assignment. Ariane 6 development delays, combined with the post-invasion re-manifestation of Russian-origin payloads to European launchers, freed up Falcon Heavy capacity. The configuration matters: ViaSat-3 F3 will fly on a more favorable transfer orbit than a traditional GTO, reducing the time the satellite spends in dead-weight transit before its electric thrusters take over. The Falcon Heavy side boosters—B1072 on its second flight and B1075 on its 22nd flight—will land back at Cape Canaveral; the core booster will be expended over the Atlantic. That expended core is a deliberate trade-off. Recovering a Falcon Heavy core downrange requires a drone ship stationed in the Atlantic and favorable sea state. For ViaSat, Viasat chose velocity over margin. The cost savings bought speed at the expense of weather sensitivity. If Atlantic conditions deteriorate during the 85-minute launch window, there is no drone ship recovery to sacrifice—the range simply cannot support a launch attempt.
What created the conditions for this moment is a convergent set of pressures that has nothing to do with ViaSat's engineering. Ariane 6 slipped, opening manifest slots. Russia's invasion of Ukraine created a manifest crisis that pushed government-backed payload schedules around the global launch market, which simultaneously opened Falcon Heavy availability for commercial customers. Boeing delivered the satellite ahead of the vehicle assignment window. None of these things individually were predictable; together they created a sequence where ViaSat could announce a concrete launch date four weeks out with genuine confidence. The April 27 window is not a target. It is a manifest.
But here is what the data actually implies: ViaSat is now under the hardest deadline it has faced in this entire program. F3 must launch on schedule. F2 must complete in-orbit testing within the next several weeks—Viasat's own language says "over the next several weeks." F3 must then spend four months traveling to its orbital slot and entering service by late summer 2026. There is no sequential slack. Government customers—defense, international partners, mobility service providers—are waiting on this capacity. ViaSat has contractual commitments tied to F3's service date. If F3 launches on April 27 but F2's testing extends into June, ViaSat is explaining delays to customers who have already waited years. If F3 takes longer than four months to reach its slot and stabilize, the late-summer deadline slips. If in-orbit testing on either satellite reveals anomalies requiring engineering fixes rather than software updates, the timeline compresses further. This is not a roadmap item with flexibility. This is a fixed commitment with low margin for discovery.
Who benefits from an on-schedule F3 arrival? ViaSat's government and defense business, which has been starved of new capacity while waiting for this constellation to reach operational status. The company has positioned F3 as introducing "new functional capabilities including new forms of resilience" for U.S. and international government customers—code for redundancy and sovereign-controlled capacity that LEO constellations do not readily provide. Asia-Pacific commercial mobility operators—airlines, maritime services, enterprise mobility networks—get access to >1 Tbps of new Ka-band capacity in a region historically undersupplied by GEO. ViaSat's stock performance and credit profile benefit from constellation completion after a decade of capital burn. Who does not benefit? Viasat's competitors who were counting on extended ViaSat-3 delays to capture market share. Amazon's Project Kuiper Leo constellation, still in the prototype phase, loses time. Competitors holding spectrum or pre-positioned capacity assumptions get a real operational constellation coming online at exactly the moment their own deployments are accelerating. The competitive calendar just compressed.
Here is the actual read: ViaSat has executed flawlessly on the hardware over the past 18 months—satellite delivery, integration, site arrival all on schedule. The program risk has moved from engineering to operations and schedule. The April 27 launch is real and should happen. The genuine risk is whether the company can hold both F2 and F3 to aggressive in-service timelines simultaneously while managing government customer expectations and executing flawless on-orbit testing that allows no debugging. ViaSat has one path forward: everything lands on the first try. This is possible. It is not probable in a program that has seen years of slippage. Watch what happens in May and June. That will tell you if the late-summer deadline holds or if ViaSat is about to have a different conversation with its government customers.
Three things to watch: First, the April 27 launch window. The 85-minute window opens at 10:21 a.m. EDT from LC-39A. Atlantic weather and range availability are the primary constraints with no core booster recovery downrange. Any scrub pushes to the next available window and compresses already tight margins. Second, B1075's 22nd landing attempt at Landing Zone 1—a successful touchdown becomes a new booster reuse record, which matters as validation that Falcon Heavy side booster logistics can support future commercial cadence. Third, track ViaSat-3 F2's in-orbit testing completion and service-entry announcement. Viasat said it expects reflector deployments to finish "over the next several weeks." If F2 enters service in late May or early June, the constellation can support parallel testing phases. If F2 testing extends into summer, F3's in-orbit validation window compresses and late-summer becomes a genuine deadline risk. The FCC imposes no explicit deadline, but ViaSat's own contracts do.