Build a compact launch service

Epsilon is a Japanese launch program for scientific and small-satellite missions. Its first flight carried SPRINT-A, also called Hisaki, in September 2013. The ascent photograph shows that first vehicle, not the later Epsilon S design. A family name can connect related rockets without making their hardware interchangeable.

Epsilon drew on H-IIA and M-V technology while changing how a launch campaign was organized. Reusing a proven design can reduce development work, but changing its role, interfaces or operating conditions introduces questions that engineers must still answer. Heritage is a starting point for qualification, not an exemption from it.

JAXA describes automated inspections, a compact launch pad and mobile launch control as parts of Epsilon’s approach. Launch cost and preparation effort depend on the ground system as well as the vehicle: personnel must inspect equipment, establish communications and decide whether conditions permit flight.

In an original planning exercise, a team has four independent ten-minute checks. Running them one after another takes forty minutes; running all four simultaneously takes ten minutes if staffing and equipment permit. This is a simplified illustration of scheduling, not a measured Epsilon turnaround time. Shared equipment or a failed check would change the answer.

Epsilon-2 and Epsilon-3 introduced enhancements, while later flights developed multi-satellite delivery. JAXA’s July 2018 user manual describes that era of the launcher. Epsilon S is a subsequent development effort with goals for a more competitive launch service and greater use of H3-related technology.

The project overview still contains an old FY2023 demonstration-flight target. Later dated test reports are needed to interpret what actually happened. Read a document’s edition, the hardware it covers and whether it describes a goal or a result before using it as a current specification.