Low-Thrust Trajectory Optimization for Cubesat Lunar Mission: HORYU-VI
summary
The gist
This paper presents a low-thrust trajectory optimization strategy to achieve a near-circular lunar orbit for a CubeSat injected into a lunar flyby trajectory The results demonstrate that HORYU-VI…
In short
This paper optimizes a low-thrust trajectory for a CubeSat to achieve lunar capture and a stable science orbit for the HORYU-VI mission. The strategy involves three phases: pre-flyby deceleration, lunar capture, and orbit circularization using finite burns. Results show successful capture within 200 days, reaching a science orbit by 280 days, and near-circular geometry by 450 days.
Key concepts
- Low-Thrust Trajectory Optimization
- This is the process of planning the spacecraft's path using very small engine thrust over long periods. The goal is to find the best way to use minimal fuel to move from Earth toward the Moon and then settle into a desired orbit around it, accounting for complex gravitational forces.
- Trajectory Decomposition
- The overall mission path is broken down into three distinct stages: slowing down before reaching the Moon (pre-flyby), successfully entering lunar gravity (capture), and finally shaping the orbit to be stable and circular for science operations. Each stage requires a different type of maneuver.
- Sequential Quadratic Programming (SQP)
- This is a mathematical tool used to solve complex optimization problems. It helps refine an initial guess for the trajectory by iteratively calculating better thrust directions and burn durations until the spacecraft meets all mission requirements, like achieving capture safely.
- Lunar Gravity Field (GGLP1500D)
- This is a detailed mathematical model used instead of a simple point-mass approximation for the Moon's gravity. It accounts for the Moon's complex shape and gravitational variations near its surface, providing much more accurate calculations for the spacecraft's flight path.
Terminology used across episodes
This episode discusses
The paper
Low-Thrust Trajectory Optimization for Cubesat Lunar Mission: HORYU-VI · Read on arXiv
Omer Burak Iskendera, Keck Voon Lingc, Mengu Chob, Sangkyun Kimb, Necmi Cihan Orgerb
Nanyang Technological University · Kyushu Institute of Technology
Transcript
Introduction to the show: ident: Robotics Radio. Generated commentary on the latest robotics and control papers.
Rosa: We're looking at the paper: "Low-Thrust Trajectory Optimization for Cubesat Lunar Mission".
Dev: Here's the gist of the paper. This paper presents a low-thrust trajectory optimization strategy to achieve a near-circular lunar orbit for a CubeSat injected into a lunar flyby trajectory The results demonstrate that HORYU-VI achieves lunar capture within 200 days, establishes a stable science orbit at 280 days, and can spiral down to a near-circular 100 km orbit by 450 days Mission Context and Objectives The HORYU-VI mission is an international CubeSat initiative to investigate the lunar dust environment through multi-epoch imaging of the Lunar Horizon Glow (LHG) The project is a collaboration among Kyushu Institute of Technology (Japan), Nanyang Technological University (Singapore), Sapienza University of Rome (Italy), California Polytechnic State University (USA), University of Colorado Boulder (USA), and Aliena Pte.
Rosa: Ltd.
Dev: (Singapore) The 12U CubeSat platform carries dedicated imaging instruments for LHG observations from a low-altitude lunar orbit Lunar dust poses hazards to both crewed missions (respiratory risks, contamination, long-term health effects) and robotic systems (optical degradation, thermal property alterations, electrical discharges) Characterizing the near-surface dust population from orbit remains an open challenge in lunar science.
Rosa: Trajectory Decomposition and Modeling The proposed trajectory is decomposed into three phases: (1) pre-flyby deceleration to avoid heliocentric escape, (2) lunar gravitational capture, and (3) orbit circularization to the science orbit For each phase, an impulsive-burn solution is first computed as an initial guess, which is then refined through finite-burn optimization using Sequential Quadratic Programming (SQP).
Paper summary: Rosa: So, this paper, "Low-Thrust Trajectory Optimization for Cubesat Lunar Mission: HORYU-VI," it's basically looking at how to get a small CubeSat into a stable orbit around the Moon using low thrust.
Dev: Right, we're talking about this 12U CubeSat, HORYU-VI, which is set up for some lunar dust imaging by collaborating universities and Aliena <ref:2602.16831#pg1>.
Taro: What's the big claim here? Is it just that they can get it there? I want to know if this low thrust approach is actually feasible for a real mission.
Rosa: The thesis is that they use a three-phase plan: first, you decelerate before you fly by the Moon to avoid escaping into deep space, then you capture gravitationally, and finally you circularize into their science orbit.
Dev: And what makes this approach interesting is that they start with an impulsive-burn guess and then refine it using sequential quadratic programming for the actual thrust direction vectors.
Taro: Refinement sounds good in theory, but how does the math handle all those complex gravitational interactions while you're coasting for months between burns?
Dev: The dynamical model is pretty detailed; it incorporates Earth–Moon–Sun–Jupiter gravity and a high-fidelity lunar gravity field. They are using the GGLP1500D gravity field near the Moon instead of just treating the Moon as a point mass.
Rosa: That's important because it means you can't treat the lunar gravity like something simple; you have to account for that degree and order fifteen hundred gravitational field.
Taro: So, when they look at those optimization variables, what exactly are they tweaking?
Dev: They are optimizing eight design variables in total. These include the three dimensional thrust direction vectors for the transition burn and the capture burn, called d-hat zero and d-hat M in R three space.
Rosa: Plus they have to define two durations: the duration of that transition burn, called delta t burn, and how long you coast between that transition and your capture phase, delta t coast.
Taro: Eight variables sounds like a lot to manage in real time. What about the constraints on those burns? How do they make sure it actually captures?
Paper summary: Dev: The constraints are crucial for safety. They determined their capture constraints through a trade study based on three failure modes they saw in simulations. Specifically, only the C3 minus RMAG formulation, which means a hyperbolic excess velocity less than or equal to negative zero point one one kilometers per second squared and the periapsis radius greater than or equal to six thousand kilometers, simultaneously guarantees gravitational capture and a safe periapsis altitude.
Rosa: So they found this specific mathematical condition that keeps the mission safe during the entire process.
Taro: That sounds like a very tight window for operation, especially when you're dealing with low thrust where small errors add up quickly.
Dev: Exactly, and that ties into the overall performance metrics they achieved. After the initial pre-flyby deceleration burn, the spacecraft coasts for approximately seventy seven point five days through multiple lunar passages.
Rosa: Then comes the capture burn, which switches the thruster reference frame from Earth centered to Moon centered velocity vector based on lunar velocity for maximum deceleration efficiency.
Taro: So that means they are actively aligning their thrust with where they need it most during that critical maneuver phase.
Dev: After capture, the orbit is circularized through a deterministic sequence of four hundred retrograde finite-burn arcs spread over successive perilune passages. They're using these arcs to refine the orbit while still near the Moon.
Rosa: The results show that HORYUVI can establish a stable science orbit within two hundred eighty days and then spiral down to a near-circular one hundred kilometer orbit by four hundred fifty days, using a total delta v of seven hundred ten meters per second.
Taro: Seven hundred ten meters per second is the total effort needed for all those maneuvers, which tells us how much fuel they're actually burning.
Dev: That total delta v figure is pretty low considering the long transfer times they need to account for, which makes this trajectory planning really efficient in terms of propellant usage.
Rosa: It’s interesting because the whole point was to achieve that science orbit by two hundred eighty days so they can start collecting data sooner.
Paper summary: Taro: But what about the risks? The paper mentioned that initial condition uncertainties, especially velocity errors at launch vehicle separation, are the biggest risk factor they found in their sensitivity analysis.
Dev: That's a major caveat. Because their high-eccentricity departure orbit creates a really narrow corridor between lunar capture and heliocentric escape, it makes early autonomous thruster activation within hours of separation mission critical.
Rosa: So, the system has to be very robust against those initial velocity errors right from the start.
Taro: It pushes us to think about how gracefully this system recovers if those errors are larger than expected during operation. What happens when the world misbehaves?
Dev: The paper suggests that future work should adjust their distant retrograde orbit approach to allow a faster spiral-down process and reduce the total thrust duration, which means they're already looking ahead to making the whole sequence quicker.
Rosa: It shows they aren't just stopping at success; they are planning how to make the entire mission profile more efficient over time.
Taro: So, what does this mean for a mission like HORYU-VI in the bigger picture? Is this low thrust strategy something we can apply to other deep space missions easily?
Dev: It shows that decomposing a complex trajectory into distinct phases, like pre-flyby and circularization, is a solid methodology for low thrust transfers.
Rosa: The fact that they can establish science operations at two hundred eighty days means the timeline for lunar science investigations is getting much tighter with this kind of optimization.
Taro: It means we can actually start doing the dust environment research sooner because the trajectory planning itself is handling a lot of complexity right now.
Dev: The main implication is that low thrust isn't just a slow way to travel; it's a well-defined engineering challenge that requires careful, multi-phase optimization for reliable results.
Rosa: It’s about balancing the need for long, efficient transfers with the need to get to science quickly and safely.
Taro: So, we see this paper as a successful demonstration of how advanced optimization techniques can solve real constraints in deep space trajectory design.
Dev: Absolutely, it's a demonstration of how you manage those complex dynamics with the right mathematical tools under tight operational bounds.
Conclusion: Rosa: The title itself tells you everything here—it’s about using low thrust to optimize a mission for a CubeSat going to the Moon.
Dev: It seems like they’ve put together this multi-phase plan, and the key result is that it gets them into orbit within two hundred days.
Taro: I'm looking at the authors now, and it’s an international team with folks from Kyushu Institute of Technology in Japan all the way to California Polytechnic State University in the United States.
Rosa: That collaboration is pretty impressive, especially since they are trying to characterize lunar dust, which is a big challenge for robotics and future crewed missions.
Dev: They used a method called sequential quadratic programming to refine their initial guess from an impulsive burn into these precise thrust direction vectors.
Taro: I want to ask about the constraints they set up; how did they decide what conditions guaranteed a safe gravitational capture?
Rosa: They found that only one specific mathematical formulation, the C3 minus RMAG condition, could simultaneously guarantee both capture and a safe periapsis altitude.
Dev: That’s important because it shows you need to be really careful with those boundaries when designing real-time control loops.
Taro: And what about the performance metrics they actually hit? What were the final numbers for the total delta v required for this whole sequence?
Rosa: They managed a total delta v of seven hundred ten meters per second to get that near-circular orbit by four hundred fifty days.
Dev: Seven hundred ten meters per second over that timeline, it shows how efficiently they managed the propellant usage while meeting those science goals.
Taro: But I want to talk about the risk factor they flagged; what was the biggest danger they saw in their sensitivity analysis?
Rosa: The biggest risk is initial condition uncertainties, specifically errors in velocity at the moment of launch vehicle separation.
Dev: Because that high-eccentricity departure orbit creates a very narrow corridor between getting captured by the Moon and escaping back into deep space.
Taro: That means if those initial velocity errors are too big, the system needs to react very quickly, within hours of separation.
Rosa: So what this means for us outside the lab is that you can't just let a low thrust system coast blindly; it needs early autonomous decision-making capability.
Dev: That’s exactly why their future work is looking at adjusting the distant retrograde orbit approach to speed up that spiral-down process.
Taro: So, they are planning to make the whole sequence faster and use less total thrust duration in future iterations.
Rosa: It shows they aren't just happy with this result; they’re already looking for ways to make the entire mission profile more efficient over time.
More episodes
- 2608.13438-ContactGuard: Pre-Contact Execution Monitoring with Action-Conditioned Latent World Models
- 2610.34593-Future Prediction as Training-Only Video Supervision for Pretrained VLA Policies
- 2610.35385-EmbodiedLab: Beyond Manipulation, Benchmarking Embodied Agents That Act to Know
- 2610.36378-Data-Driven Hamiltonian for Neural Optimal Control
- 2610.37275-A Heuristic for Scheduling Autonomous Vehicles at Intersections
- 2610.37288-Dynamic Coordination of Autonomous Vehicles at Intersections
- 2610.37632-Real-Time Coordination of Autonomous Vehicles at Intersections
- 2611.13779-Softness is something you also need! Why compliance helps control: information metrics of a passive walker with compliant ankle
- 2611.13411-Residual-Corrected Physics-Informed Neural Network KKL Observers with Input-to-State Stability Guarantees
- 2611.14488-Is Your Robot's Memory Just a Clock? Temporal Shortcuts in Memory-Augmented VLA Policies