Mu: improve a scientific launcher across generations

Japan’s Mu, or M-series, launch vehicles developed through several generations to serve scientific missions. They followed the Lambda rocket that launched Ohsumi in 1970. M-4S, M-3C, M-3H, M-3S, M-3SII and M-V identify different designs within this history. A shared family name does not mean that every flight used identical stages, guidance or payload capability.

The early M-4S relied on aerodynamic stabilization and spinning, while later designs introduced improved thrust-vector control — open definition. Changing the direction of thrust changes the force acting on the vehicle and helps control its trajectory. Guidance development therefore mattered alongside stronger motors: delivering a satellite requires an appropriate position and velocity, rather than simply reaching a high altitude.

M-3SII retained the first stage of its predecessor but changed other stages to improve capability. With an additional kick stage — open definition it launched Sakigake and Suisei in 1985 toward their Halley-comet investigations. A kick stage adds another propulsion step for a particular trajectory; it should not be assumed to appear in every flight of a family.

M-V subsequently launched observatories and planetary explorers, including Hayabusa. Its final flight carried Hinode in September 2006. The photograph in this lesson depicts that particular M-V launch, not an earlier Mu configuration. Launching an explorer onto its planned departure path and completing its later scientific mission are separate achievements, with different systems and teams responsible for the next phases.

Imagine selecting between two fictional launch configurations for a scientific payload. One can carry more mass to low Earth orbit; the other includes an upper stage for a higher-energy departure. Those figures answer different questions. Specify the target orbit or trajectory, payload mass, volume and environmental limits before deciding which vehicle is suitable.

M-V also suffered a failed launch carrying ASTRO-E. A balanced program history includes both successful deliveries and losses, rather than inferring perfect performance from a selection of famous spacecraft. Later development can reuse knowledge from the family while changing the operational design. Preserving these distinctions makes the sequence of names a useful engineering history instead of a simple list of rockets.