The answer to question 1 will come from the chosen trajectory's arrival $V_\inf$ (hyperbolic excess velocity). The answer to question 2 will come from the chosen trajectory's launch $C3$ (characteristic energy). The two are coupled to an individual trajectory dependent on dates and routes (which planets to flyby). Luckily, I have (student) experience in interplanetary trajectory searches.
I chose to maintain the (as flown) mission architecture of a Jupiter gravity assist to try to leverage a lower launch $C3$ (compared to Pluto direct) and a stronger gravity assist at Jupiter. It is also easier to compare with the as flown New Horizons primary mission.
Search Constraint Dates:
- Launch Dates: 2003 - end 2006
- JGA Dates: 2003 - end 2010
- Pluto Arrival Dates: 2008 - End 2030*
- state vector data from JPL Horizons (5 day step size)
*The New Horizons mission design supported arriving at Pluto as late as 2020 in a Pluto direct trajectory (New Horizons Mission Design, Guo et al.)
I used a heavily modified version (mainly the Lambert solver) of this MATLAB file exchange package$^1$ to create the porkchop plots for each leg of the trajectory (Earth-Jupiter, Jupiter-Pluto). Here is the initial leg (launch $C3$) with the New Horizons actual annotated:
The trick comes in finding suitable Jupiter to Pluto trajectories that match the hyperbolic excess velocity, $V_\inf$, approaching and leaving Jupiter, enabling a 'free' flyby/gravity assist. I usually consider a difference of less than 100 m/s to be sufficiently close.
The Pluto arrival hyperbolic excess velocity strongly favours a slower route from Jupiter to Pluto (again, New Horizons actual annotated). Slower is the name of the game here:
A secondary, not immediately evident constraint is how close you are willing to get to Jupiter and its strong radiation during the gravity assist. New Horizons passed at a close approach of about 33 $R_J$, Jovian radii (TRAJECTORY MONITORING AND CONTROL OF THE NEW HORIZONS PLUTO FLYBY, Guo et al.). I have no good knowledge on what is a reasonable close approach distance for a spacecraft flying by Jupiter (in the scope of radiation damage) so for now I will leave this constraint wide open (just don't have the close approach inside of Jupiter).
With these constraints, and a launch $C3$ less than 150 km$ ^2$/s$ ^2$, there are 32,075 viable trajectories, shown here in this nifty plot of the key values we care about:
The red markers show the region of most efficient trajectories (low $C3$ and $V_\inf$). The most efficient trajectory is:
Launch: |
Jupiter Flyby: |
Pluto Arrival: |
$C3$: |
$V_\inf$ @ Pluto: |
Jupiter Close Approach: |
12-Nov-2003 |
22-Oct-2005 |
31-Dec-2020 |
91.9 km$ ^2$/s$ ^2$ |
3.72 km/s |
24 $R_J$ |
It looks like this (with New Horizons actual, left, for comparison):
Observations:
- This trajectory arrives at Pluto on the last day of the time constraint (slower is the name of the game)
- The trajectory remains gravitationally bound to the Sun throughout the entire trajectory (S.M.A. E-J: 3.7 au, S.M.A. J-P: 30.3 au)
Answers:
I am going to ignore Charon in the orbital insertion calculations. I am also going to assume a 'dry mass' (including attitude control propellant) of 500 kg for our New (and improved) Horizons probe to accommodate the increase in propellants. $I_{sp}$ of 220 s as discussed in JanKunis' answer.
- Pluto Orbit Insertion (instantaneous burn at periapsis assumed):
Periapsis Distance: |
Velocity @ Periapsis: |
Capture Velocity @ Periapsis ($C3$=0): |
Circular Orbit Velocity: |
1500 km (~300 km above surface) |
3.872 km/s |
1.078 km/s |
762 m/s |
Capture dV: |
Circular Orbit dV: |
Capture Initial Mass: |
Circular Orbit Initial Mass: |
2793 m/s |
3109 m/s |
1824 kg |
2112 kg |
73% & 76% propellant by mass, respectively.
- Launch Vehicles:
I used a previously developed algorithm of mine to determine how much mass a given launch vehicle + STAR48B combination can throw to a specified $C3$. Basic performance is taken from NASA Launch Services Program Launch Vehicle Performance Website and Northrop Grumman Propulsion Products Catalog. If a reference altitude is assumed you can get velocity from $C3$ and Star48B + spacecraft $\Delta V$ from the public specifications. Get a final velocity and then recompute the $C3$.
The Delta IV Heavy is no longer listed on the NASA Launch Services Program Launch Vehicle Performance Website (it was in April 2020), but I have a a curve fit of the data saved from some old school projects :). I realize that the proposed launch is ~1 year prior to the Delta IV Heavy's maiden flight but the contract could be very juicy to make this possible. I included other launch vehicles for comparison:
For a $C3$ of 91.9 km$ ^2$/s$ ^2$:
Delta IV Heavy: |
Atlas V 551: |
Atlas V 401: |
Falcon Heavy (Expandable): |
Falcon Heavy (Recoverable): |
2215 kg |
1381 kg |
704 kg |
2847 kg |
1249 kg |
A slim margin for sure, but definitely plausible.
1: Bogdan Danciu (2021). Interplanetary Mission Design (https://www.mathworks.com/matlabcentral/fileexchange/66192-interplanetary-mission-design), MATLAB Central File Exchange. Retrieved June 27, 2021.