Share a platform, not a timeline

Japan’s Multi-functional Transport Satellite program combined meteorological work for the Japan Meteorological Agency with aviation services for the Civil Aviation Bureau. Weather observations and aircraft communications could benefit from a broadly fixed regional view from geostationary orbit. They still required different payloads, ground systems and users. A cloud image and an aircraft message were different products even when their signals passed through the same spacecraft.

Think of an original design exercise: two services need a high-altitude relay platform. Sharing the spacecraft can avoid some duplicated support hardware, but also connects both services to common power, pointing and communications resources. Separate payload managers do not make the spacecraft physically independent. Evaluating that choice requires tracing what each service shares and what it manages separately.

The first MTSAT was lost in the H-II Flight 8 launch failure on November 15, 1999. MTSAT-1R, also called Himawari-6, launched on February 26, 2005. Its replacement role does not mean the failed original reached orbit later. MTSAT-2, also called Himawari-7, followed on February 18, 2006. Each name belongs to a particular spacecraft and launch history.

The same spacecraft can have a program designation and a weather-service name. Himawari-6 and MTSAT-1R refer to one spacecraft, while Himawari-7 and MTSAT-2 refer to another. By contrast, the broader Himawari weather history includes other satellite generations. An archive should connect these relationships without merging every spacecraft into one record or counting a renamed spacecraft twice.

One spacecraft, separate service responsibilities

MTSAT-1R began its main weather operation on June 28, 2005. MTSAT-2 first served as a weather backup before taking the principal role on July 1, 2010. Launch, initial observations, backup readiness and primary service therefore identify different stages. A successful launch does not show that every receiver, ground link and operational procedure is already ready.

Imagine a project report saying only that a satellite became operational in 2006. Before using that statement, ask which payload, which service and which role it describes. A backup spacecraft may be functioning while another supplies the routine product. Useful histories attach the service and role to each date, so the reader can distinguish available hardware from a service actually delivered.