Deliver a satellite and then a service

Anik C3 travelled aboard Columbia on STS-5 in November 1982. The flight also carried SBS-3, a different communications satellite. NASA’s account identifies Joseph P. Allen with the Anik deployment. Keeping the payload identities separate prevents one deployment photograph from silently standing in for every spacecraft on the mission.

The course photograph shows Anik C3 above Columbia’s payload bay. The Shuttle operated in low Earth orbit; it did not carry the satellite all the way to its later geostationary service position. NASA records a Payload Assist Module-D burn after release to place the payload on an elliptical transfer trajectory.

This sequence gives a practical way to read an image: identify what has happened at the photographed moment and which later steps remain outside its evidence. A visible separation can establish deployment without establishing the final orbit, commissioning or customer service.

A transfer orbit connects different orbital conditions. Its purpose is not to reproduce the final operating orbit immediately after release. Later propulsion, navigation and control work must be assessed against the intended destination and spacecraft configuration.

Imagine an original four-stage log: payload released, transfer initiated, operating orbit acquired, service checks passed. If the first two entries are complete, the record supports deployment and transfer initiation. It does not support moving the last two entries to complete just because the launch was successful.

The same distinction applies to hardware condition. A spacecraft can separate correctly yet encounter a later problem. Recording intermediate achievements accurately lets engineers and historians locate where an interruption occurred, rather than collapsing the entire mission into one unqualified success or failure.

From release to a tested service

An operational connection needs terminals configured for the relevant service, a usable path and a way to deliver information locally. These are systems tasks with their own acceptance evidence. A footprint describes a geographic opportunity; an installed and tested endpoint describes a different achievement.

In a fictional rollout, sixteen communities are inside the planned coverage area. Twelve have completed terminal installation and service checks. The verified share is 12 / 16 = 75 percent. Calling all sixteen connected would hide four unfinished endpoints. These values are a planning exercise, not a historical Anik deployment count.

A complete rollout record would retain both the coverage plan and the tested endpoint list. If a local link later fails, that does not mean the spacecraft left orbit. Service availability depends on the whole route, so the status record should identify which part has been checked.