Satellite fleets: map in-orbit life and backup coverage
A satellite fleet can have abundant headline capacity while lacking a workable replacement for one service region. Orbital location, beam coverage, customer terminals, ground infrastructure and the timing of commercial entry can prevent nominal bandwidth from substituting where it is needed. Fleet research therefore requires a coverage-and-time matrix alongside the satellite count.
The deliverable is a dated asset register and a service continuity worksheet. It connects the expected remaining service of existing spacecraft with replacement milestones and demonstrated backup rights. It does not turn public information into an independent spacecraft engineering assessment or assume that a depreciation schedule reveals undisclosed remaining fuel.
Locate the actual risk and accounting passages
In Viasat’s fiscal 2026 Form 10-K, locate Item 1A, the heading on satellite failures, performance degradation and shortened useful life: printed page 23, PDF page 24. The passage identifies finite useful life, anomalies and potential need for replacement or backup. The launch-risk discussion continues on printed page 24, PDF page 25, including successful orbital placement and testing.
Also locate Critical Accounting Policies, Property, equipment and satellites, printed page 49, PDF page 50. It describes the company’s process for estimating depreciation lives using performance, design life, estimated fuel and operating trends. These are specific inspected passages, not a claim to have reviewed every page of the report.
The passages support two separate research questions: whether service continuity is physically and commercially evidenced, and how the company estimates accounting life. They do not provide a fuel quantity or a universal relation between accounting life and replacement timing for every satellite operator.
Build a service-area register
Record spacecraft, operator, ownership or leased-capacity right, orbit or operating location where disclosed, service footprint, frequency or terminal constraints, stated capacity basis, commercial-entry date and current status. Preserve whether bandwidth is a design figure, an in-service measure or an amount contractually available to the issuer.
For remaining life, record the company’s dated statement and its stated basis. A launch date plus a generic industry life is only a scenario. It must not replace an issuer’s revised estimate after an anomaly. Keep missing engineering details explicitly missing; a public investor generally cannot calculate a particular spacecraft’s propulsion reserve from the age of the fleet.
Next list the proposed replacements with separate dates for manufacturing, launch, orbital placement, in-orbit testing, ground integration and commercial availability. A successful launch closes one milestone. It does not establish that every later milestone has been completed or that customer migration is already possible.
Reproduce an original coverage case
All following assets and capacity units are fictional. Assume service region X needs eighty compatible units. Existing satellite A supplies those eighty and is assumed to retire at Month 24. Satellite B supplies region Y with one hundred units. Spare D has forty nominal units covering region Z, with no demonstrated route to X.
Replacement C has seventy nominal units. Its supported operating plan allocates fifty to X and twenty to Y after testing. Assume launch at Month 18 and six months to complete the remaining milestones. The plan would make C commercially available at Month 24 if every assumption holds.
| Asset | Nominal units | Supported region X units | Timing assumption |
|---|---|---|---|
| Existing A | 80 | 80 | Retires at Month 24 |
| Existing B | 100 | 0 | Region Y |
| Spare D | 40 | 0 | Region Z; no X substitution evidenced |
| Replacement C | 70 | 50 | Commercial entry at Month 24 assumed |
Before A retires, existing nominal capacity totals 220. Including C’s design amount would make a presentation show 290. After A retires and C enters, nominal capacity is 210, yet the evidenced X supply is only fifty against eighty required. The X shortfall is thirty units, or 37.5% of that region’s assumed requirement.
The aggregate total does not resolve the missing thirty. B and D cannot be allocated to X merely because their unused nominal capacity appears in the same fleet slide. Conversely, the shortfall is conditional on the specified regional requirement and replacement capability; it is not a conclusion about Viasat or any real operator.
Now delay C’s commercial entry by three months while A’s retirement date stays fixed. Under these deliberately strict assumptions, X lacks all eighty units during Months 24–27 and still lacks thirty after C enters. Keep the timing gap and the continuing coverage gap separate. Extending A, leasing a compatible substitute or changing customer requirements could alter either, but each remedy needs evidence.
Test the backup claim rather than the spare label
A compatible third-party contract could supply thirty X units for the missing period. Obtain the contract’s region, capacity, priority, activation conditions, duration and terminal requirements. An option to negotiate for capacity is not a reservation, and a reservation with a later start date does not cover the earlier gap.
Commercial control also matters. Capacity on a partner’s satellite can be physically suitable yet unavailable under the issuer’s rights. Record which entity may direct use and whether existing customer commitments have priority. Do not assume group ownership, operating permission and customer access are identical because a satellite name appears on an investor slide.
Customer migration can require a separate timeline. If terminals or gateways need modification, count only the portion evidenced as ready for migration by the relevant date. Fifty compatible units in orbit may not immediately translate into fifty usable service units for the existing customer population.
Counterexample: accounting life changes without new capacity
Suppose a fictional operator revises a satellite’s remaining depreciation life from two years to four after reviewing performance. No new spacecraft is launched and no additional region becomes covered. The accounting expense schedule changes, but nominal physical capacity has not doubled. The research register should record a revised estimate and its explanation, not a new fleet addition.
A different scenario adds a satellite whose coverage overlaps an existing region and improves resilience, while leaving X untouched. Fleet counts and backup totals rise, yet X’s particular replacement gap remains. This is a geographic compatibility mechanism, unlike the accounting-estimate example. Both can make aggregate metrics look better without resolving the operating question.
An anomaly can also reduce capacity without immediate retirement. Preserve partial-service status and the affected footprint. Removing the entire spacecraft from every region can overstate the problem; treating it as fully healthy because some service remains can understate it.
Verify the next decision point
| Evidence object | Obtain | Specific result |
|---|---|---|
| Existing service | Asset and footprint disclosure | Identify dependent customer region |
| Remaining life | Dated issuer estimate and explanation | Preserve uncertainty and revisions |
| New entry | Testing and commercial-entry notices | Distinguish launch from usable service |
| Backup | Executed capacity rights and compatibility | Count only available regional substitution |
| Migration | Terminal and gateway readiness evidence | Bound customers transferable by date |
If reports conflict, compare the capacity denominator and observation date before choosing one. Design throughput, operational throughput and contracted service capacity can legitimately differ. A press release may describe the satellite as a whole, while a later filing discusses only one impaired subsystem or beam population.
Where a PDF lacks a material schedule, record the missing table rather than infer its contents from a map. Keep original and revised service dates. A delay announcement should not erase the earlier deadline that the research model tested.
Update the worksheet after a revised life estimate, anomaly report, testing result, commercial-service notice, backup agreement or customer-migration evidence. State whether the new information changes timing, location compatibility, contractual access or usable capacity. Financial consequences then require their own revenue, customer and settlement evidence; a regional capacity gap is not automatically an equal percentage loss of group revenue.
Turn migration into a measurable completion test
Assume C can support fifty regional units, but only twenty units of customer demand have compatible terminals at Month 24. The remaining thirty need documented upgrades. The in-orbit capacity test is satisfied for fifty, while the customer-readiness test is satisfied for twenty; they should remain separate rows.
Track the original customer population through ordered, installed, tested and migrated stages. An order for terminal equipment is not a completed migration. If a later report says most customers moved, ask for its population and date before comparing it with the earlier footprint. This is particularly important when low-demand customers migrate first. A high customer-count completion rate can coexist with a larger share of remaining traffic, which requires compatible demand evidence rather than a guessed average customer load.
Separate committed backup from priority-dependent capacity. A contract that supplies twenty units only after existing customers release them is a contingent remedy, even if the satellite is already operating. Count the firm portion in the main continuity case and show the contingent portion as a separate scenario with its activation evidence.
FAQ
Does a successful launch prove commercial capacity is available?
No. Orbital placement, testing, ground integration and service entry remain separate evidence milestones.
Can remaining life be read directly from depreciation years?
No. Inspect the estimate’s basis and later revisions without reverse-engineering undisclosed fuel or performance information.