0
#51
THE FULL INSTRUMENT
An epistle on flying MISSION PLOT at maximum functionality
For the future space travelers — everything the helm's interplanetary instrument can do, and how to do all of it.
1. What you are holding
MISSION PLOT is not a picture of a trajectory. It is a solver. Given any two bodies in the solar system and a departure date and a flight time, it computes where both bodies will actually be — from the JPL Keplerian Elements table, the same approximate fit JPL publishes, good for the years 1800 to 2050 — and then it solves Lambert's problem: the one arc through space that connects them in exactly that time. That is the standard preliminary design stack. JPL elements, Lambert, porkchop. Nothing is assumed and nothing is drawn by hand.
Maximum functionality means using all of it, in order, and filing all of it. Here is the whole flight.
2. Begin with the fix — NAV FIX feeds the plot
Every mission starts with knowing where you stand, and the instrument enforces this: MISSION PLOT reads your GPS fix straight from NAV FIX's cache. Open NAV FIX first. Let it take the fix — latitude, longitude, grid square, altitude. That fix becomes your launch site, shown on the plot as e.g. 21.31N 157.86W GPS, and it feeds the launcher math at the end of the chain: your rotational boost, 0.4651·cos(lat) km/s — 0.43 km/s at Honolulu's 21.3°N — is Earth's free gift, and the instrument counts it.
No fix, no launch site. The plot will tell you so: "NO FIX — open NAV FIX for a fix." A navigator never plots from nowhere.
3. Survey the solar system — don't marry the first planet
The origin and destination selectors hold all eight planets and the Moon, and any pair flies. Maximum functionality starts wide: before you commit to Mars, run FIND WINDOW for Mars, for Venus, for the Moon. Compare the cheapest C3 each destination offers. You are not choosing a favorite; you are reading the sky's price list.
The verified price list, as the instrument reads it today:
Run the survey yourself. The numbers will move as the planets do — that is the point. The instrument is honest about the sky as it is, not as it was in the last chapter.
4. Hunt the window — read the porkchop like a map
FIND WINDOW runs an adaptive scan: a coarse 20×20 grid of departure dates by flight times across roughly two years finds every C3 valley, and a Nelder–Mead optimizer descends each valley to its true local minimum — no dumb sixteen-hundred-cell brute force, the solves go where the windows are. Then it paints the porkchop from the full coarse grid: dark blue valleys where energy is cheap, red ridges where it is ruinous. This is the oldest and truest picture in mission design, and you should learn to read it the way sailors read water.
Look for the valleys, plural. There is usually one deep valley per synodic cycle — the rhythm at which your two planets line up again. A single tap on a dark cell inspects it — departure, flight time, C3, DLA in the status line, a white marker on the cell — without committing anything. Double-tap, or hit LOAD WINDOW, and the optimizer takes over from the inspected point, converging to the true local minimum before it plots. What loads is not a grid square. It is the bottom of the valley.
Tap other dark cells too. Inspecting anywhere on the plot is free. Compare valleys. The cheapest departure is not always the wisest — a slightly costlier window with a shorter flight time, or one whose DLA your pad can reach (see section 5), may be the better mission. The instrument gives you the numbers; the judgment is yours, as it has always been.
And when you want to plan ahead: NEXT 3 WINDOWS runs the adaptive scan three times, each starting one synodic period later, and lists the next three valleys — departure date, flight time, C3, DLA, pad flag — each tappable to load. The windows march to the planets' rhythm, not your calendar.
5. Fly the arc — PLOT and watch
Set your departure and flight days — or load them from a tapped cell — and hit PLOT. The system view draws the transfer arc across the orbits of the planets, departure dot to arrival dot, and animates the ship along it. Watch it. The animation is not decoration; it is the geometry made visible. You will see immediately whether the arc is a clean Hohmann-like half-ellipse or a long looping thing, whether it dives sunward first (Venus) or climbs outward (Mars), whether the arrival meets the planet from ahead or behind.
Then read the readouts, every one of them:
6. Design the return — a mission is a round trip or it is exile
Here is where the instrument earns its keep at maximum functionality: hit ROUND TRIP and it flies the whole mission for you. It takes the best outbound window, waits at the destination at least your MIN STAY D days (default 30), then hunts the best return window home with the same adaptive scan — and files the verdict as one continuous plan: outbound departure, stay duration, return departure, total duration, total Δv (departure + capture + destination-departure), and your Earth-arrival entry speed.
For the 2026 Mars window: out 2026-10-30, a 382-day stay (the return window, not your minimum, sets the schedule — this is the honest part), return departure 2028-09-06, total spacecraft Δv 7.72 km/s, Earth-arrival entry 11.92 km/s. The great expeditions of the future will be designed exactly like this — two valleys, one stay, a single continuous plan.
Run it for Venus too: Earth→Venus→Earth. Run it for the Moon on a lazy afternoon: Earth→Moon→Earth in nine days, the whole round trip for less energy than a Mars departure burns before breakfast.
7. The Moon as proving ground
Fly the Moon the way the instrument insists: geocentrically. Inside Earth's gravity well the Sun-centered Lambert solution is unphysical, so the instrument switches frames on its own — Earth at the center, a parking orbit, the Moon's true position from the lunar algorithm — and reports the TLI-style energy, negative C3, around −2.2 for a four-and-a-half-day hop.
Use it as the training ground it is. Every procedure in this epistle — survey, window hunt, refinement, arc, readouts, verdict, filing — works on the Moon in four days instead of ten months. Learn the instrument where the stakes are a weekend, then take it to Mars.
And never compare the Moon's negative C3 with an interplanetary C3. They are different currencies. The instrument keeps them separate; so must you.
8. From the pad — the full stack, surface to v∞
The last line of the instrument is the first line of the rocket equation: EST. LAUNCHER DELTA-V FROM SURFACE. It takes your C3, adds Earth's escape — √(11.186² + C3) — and subtracts your rotational boost from the GPS fix. For the 2026 Mars window from Honolulu: √(125.13 + 9.14) − 0.43 = 11.15 km/s from the pad.
Read it as what it is: an estimate. It counts no gravity losses, no drag, no steering. The real launcher pays more. But it is the right estimate, built from the right numbers, and it turns the abstract C3 into the one question that matters: can our rocket do this? 11.15 km/s from the surface of the Earth. Now you know the size of the machine you need.
9. File everything — the record is the mission
A solution you don't file is a dream you had. The instrument's chain ends where the TI's chain ends: MISSION VERDICT renders the full findings — bodies, dates, flight time, C3, both v∞ values, phase angle, launch site — and files them through the thread lock into the mission log table, timestamped, permanent, editable. The engineering log notes it too: window found, plot solved, verdict filed.
At maximum functionality, every window you hunt ends in the log. Months later, when someone asks why October 2026 and not December, the answer is not "I remember it was cheaper." The answer is in the table, with the numbers, under a timestamp. That is what separates a navigator from a stargazer.
10. The navigator's cross-checks — trust, then verify
The instrument is honest, and honesty can be checked. Make these three checks a habit, every solution:
11. Know its edges — what maximum functionality does not include
The instrument is a preliminary design tool, and using it at maximum functionality includes knowing exactly where it stops:
None of this diminishes it. Every real mission ever flown began exactly here — with this stack, these numbers, these pictures — and only later graduated to the heavy machinery. The honest limits are what make it an instrument instead of a toy.
12. The whole flight, once, in order
For the traveler who wants it plain:
Do this, all of it, and you have done preliminary mission design the way it is actually done — the way every trajectory team on Earth does it, with darker screens and older coffee. The instrument does not fly the ship. It never will. It gives the navigator true numbers, honestly derived, and gets out of the way.
That is maximum functionality. That is the whole instrument.
— Solid, for the mission record. Written for the future space travelers, who will need no introduction to any of this.
An epistle on flying MISSION PLOT at maximum functionality
For the future space travelers — everything the helm's interplanetary instrument can do, and how to do all of it.
1. What you are holding
MISSION PLOT is not a picture of a trajectory. It is a solver. Given any two bodies in the solar system and a departure date and a flight time, it computes where both bodies will actually be — from the JPL Keplerian Elements table, the same approximate fit JPL publishes, good for the years 1800 to 2050 — and then it solves Lambert's problem: the one arc through space that connects them in exactly that time. That is the standard preliminary design stack. JPL elements, Lambert, porkchop. Nothing is assumed and nothing is drawn by hand.
Maximum functionality means using all of it, in order, and filing all of it. Here is the whole flight.
2. Begin with the fix — NAV FIX feeds the plot
Every mission starts with knowing where you stand, and the instrument enforces this: MISSION PLOT reads your GPS fix straight from NAV FIX's cache. Open NAV FIX first. Let it take the fix — latitude, longitude, grid square, altitude. That fix becomes your launch site, shown on the plot as e.g. 21.31N 157.86W GPS, and it feeds the launcher math at the end of the chain: your rotational boost, 0.4651·cos(lat) km/s — 0.43 km/s at Honolulu's 21.3°N — is Earth's free gift, and the instrument counts it.
No fix, no launch site. The plot will tell you so: "NO FIX — open NAV FIX for a fix." A navigator never plots from nowhere.
3. Survey the solar system — don't marry the first planet
The origin and destination selectors hold all eight planets and the Moon, and any pair flies. Maximum functionality starts wide: before you commit to Mars, run FIND WINDOW for Mars, for Venus, for the Moon. Compare the cheapest C3 each destination offers. You are not choosing a favorite; you are reading the sky's price list.
The verified price list, as the instrument reads it today:
- Mars, October 2026 window: depart 2026-10-30, fly 294.1 days, C3 9.14 — v∞ 3.02 km/s at departure, 2.70 km/s at arrival, phase angle 63.0°.
- Venus, 2028 window: depart 2028-03-26, fly 171.4 days, C3 9.11.
- Moon, any month: about 4.5 days, C3 −2.19 — the negative sign is the cislunar signature, TLI-like energy, not to be compared with interplanetary C3.
Run the survey yourself. The numbers will move as the planets do — that is the point. The instrument is honest about the sky as it is, not as it was in the last chapter.
4. Hunt the window — read the porkchop like a map
FIND WINDOW runs an adaptive scan: a coarse 20×20 grid of departure dates by flight times across roughly two years finds every C3 valley, and a Nelder–Mead optimizer descends each valley to its true local minimum — no dumb sixteen-hundred-cell brute force, the solves go where the windows are. Then it paints the porkchop from the full coarse grid: dark blue valleys where energy is cheap, red ridges where it is ruinous. This is the oldest and truest picture in mission design, and you should learn to read it the way sailors read water.
Look for the valleys, plural. There is usually one deep valley per synodic cycle — the rhythm at which your two planets line up again. A single tap on a dark cell inspects it — departure, flight time, C3, DLA in the status line, a white marker on the cell — without committing anything. Double-tap, or hit LOAD WINDOW, and the optimizer takes over from the inspected point, converging to the true local minimum before it plots. What loads is not a grid square. It is the bottom of the valley.
Tap other dark cells too. Inspecting anywhere on the plot is free. Compare valleys. The cheapest departure is not always the wisest — a slightly costlier window with a shorter flight time, or one whose DLA your pad can reach (see section 5), may be the better mission. The instrument gives you the numbers; the judgment is yours, as it has always been.
And when you want to plan ahead: NEXT 3 WINDOWS runs the adaptive scan three times, each starting one synodic period later, and lists the next three valleys — departure date, flight time, C3, DLA, pad flag — each tappable to load. The windows march to the planets' rhythm, not your calendar.
5. Fly the arc — PLOT and watch
Set your departure and flight days — or load them from a tapped cell — and hit PLOT. The system view draws the transfer arc across the orbits of the planets, departure dot to arrival dot, and animates the ship along it. Watch it. The animation is not decoration; it is the geometry made visible. You will see immediately whether the arc is a clean Hohmann-like half-ellipse or a long looping thing, whether it dives sunward first (Venus) or climbs outward (Mars), whether the arrival meets the planet from ahead or behind.
Then read the readouts, every one of them:
- C3, km²/s² — the launch energy, the single number that prices the mission. Lower is cheaper, always.
- v∞ departure — your hyperbolic excess speed leaving Earth. Square it: it must equal C3, within rounding. 3.02² = 9.14. If it doesn't, something is wrong — check it every time.
- v∞ arrival — your excess speed at the destination. This is the number the next maneuver pays against: capture into orbit, or entry. A mission is not over at arrival; the arrival v∞ is the opening line of the next chapter.
- DLA — declination of the launch asymptote — the latitude the departure asymptote points at, the number launch planners check before anything else. Your pad sits at your GPS latitude; the asymptote is a line in space. If it points at +23.3° and your pad is at 21.3°N (the 2026 Mars window from Honolulu), you fly azimuth 80.4° in a steep direct ascent.
- PAD FLAG — the instrument's verdict on DLA versus your pad. GREEN: the asymptote lies within your latitude, due-east departure, no plane change. YELLOW: it misses by up to 10°, direct ascent can still reach it, steep and costly — the 2026 Mars window from Honolulu is YELLOW. RED: a plane change is required; fly a different window or a different latitude. NO FIX: no GPS fix, so no flag — it will not guess.
- The Δv chain — the mission's actual bill, from the vis-viva chain: DEP DV from your parking orbit (default 400 km, your setting), CAP DV into your capture orbit at the destination (default 300 km), ENTRY V at a 125 km interface if you aerocapture instead of burning. For the 2026 Mars window: 3.59 km/s to leave, 2.12 km/s to capture, 5.63 km/s at entry. The launcher line below is the surface; this chain is the spacecraft.
- Phase angle — the heliocentric longitude of the destination minus that of the origin, on departure day. For Earth→Mars, a Hohmann wants about 44°, Mars ahead of Earth. Longer-than-Hohmann arcs need Mars further ahead — the 2026 window reads 63.0°, which is exactly what a 294-day arc demands. If the phase angle ever reads near zero or near 180° for a Mars departure, be suspicious: near zero means the planets are on the same side (no cheap transfer exists), near 180° is opposition geometry, not departure geometry.
- Distances — where each body sits, in AU, at the moments that matter.
6. Design the return — a mission is a round trip or it is exile
Here is where the instrument earns its keep at maximum functionality: hit ROUND TRIP and it flies the whole mission for you. It takes the best outbound window, waits at the destination at least your MIN STAY D days (default 30), then hunts the best return window home with the same adaptive scan — and files the verdict as one continuous plan: outbound departure, stay duration, return departure, total duration, total Δv (departure + capture + destination-departure), and your Earth-arrival entry speed.
For the 2026 Mars window: out 2026-10-30, a 382-day stay (the return window, not your minimum, sets the schedule — this is the honest part), return departure 2028-09-06, total spacecraft Δv 7.72 km/s, Earth-arrival entry 11.92 km/s. The great expeditions of the future will be designed exactly like this — two valleys, one stay, a single continuous plan.
Run it for Venus too: Earth→Venus→Earth. Run it for the Moon on a lazy afternoon: Earth→Moon→Earth in nine days, the whole round trip for less energy than a Mars departure burns before breakfast.
7. The Moon as proving ground
Fly the Moon the way the instrument insists: geocentrically. Inside Earth's gravity well the Sun-centered Lambert solution is unphysical, so the instrument switches frames on its own — Earth at the center, a parking orbit, the Moon's true position from the lunar algorithm — and reports the TLI-style energy, negative C3, around −2.2 for a four-and-a-half-day hop.
Use it as the training ground it is. Every procedure in this epistle — survey, window hunt, refinement, arc, readouts, verdict, filing — works on the Moon in four days instead of ten months. Learn the instrument where the stakes are a weekend, then take it to Mars.
And never compare the Moon's negative C3 with an interplanetary C3. They are different currencies. The instrument keeps them separate; so must you.
8. From the pad — the full stack, surface to v∞
The last line of the instrument is the first line of the rocket equation: EST. LAUNCHER DELTA-V FROM SURFACE. It takes your C3, adds Earth's escape — √(11.186² + C3) — and subtracts your rotational boost from the GPS fix. For the 2026 Mars window from Honolulu: √(125.13 + 9.14) − 0.43 = 11.15 km/s from the pad.
Read it as what it is: an estimate. It counts no gravity losses, no drag, no steering. The real launcher pays more. But it is the right estimate, built from the right numbers, and it turns the abstract C3 into the one question that matters: can our rocket do this? 11.15 km/s from the surface of the Earth. Now you know the size of the machine you need.
9. File everything — the record is the mission
A solution you don't file is a dream you had. The instrument's chain ends where the TI's chain ends: MISSION VERDICT renders the full findings — bodies, dates, flight time, C3, both v∞ values, phase angle, launch site — and files them through the thread lock into the mission log table, timestamped, permanent, editable. The engineering log notes it too: window found, plot solved, verdict filed.
At maximum functionality, every window you hunt ends in the log. Months later, when someone asks why October 2026 and not December, the answer is not "I remember it was cheaper." The answer is in the table, with the numbers, under a timestamp. That is what separates a navigator from a stargazer.
10. The navigator's cross-checks — trust, then verify
The instrument is honest, and honesty can be checked. Make these three checks a habit, every solution:
- 1. v∞² = C3. Departure v∞ squared must equal C3 within rounding. It is the same energy wearing two hats. If they disagree, stop.
- 2. Phase plausibility. Mars departure near 44° for Hohmann-like arcs, larger for longer arcs. Venus departures want Venus behind Earth at departure (it laps us from the inside). The Moon's geometry changes daily — check the Moon's actual phase in the sky if you can.
- 3. Synodic rhythm. Windows repeat on the synodic cycle — about 26 months for Mars. If the instrument finds a valley, the next one should sit roughly one synodic period later. If it doesn't, ask why before you believe the first one.
11. Know its edges — what maximum functionality does not include
The instrument is a preliminary design tool, and using it at maximum functionality includes knowing exactly where it stops:
- The JPL elements are approximate — fine for hunting windows, not for final navigation. Real navigation uses full numerical ephemerides.
- Two-body Lambert only. No gravity assists, no deep-space maneuvers, no plane-change optimization. A Venus flyby that would cut your Mars C3 in half is invisible to this instrument.
- The launcher number is an estimate — no gravity or drag losses.
- The porkchop is a 20×20 coarse grid with Nelder–Mead valley descent — adaptive, not exhaustive. It finds valleys; it does not prove global optimality.
None of this diminishes it. Every real mission ever flown began exactly here — with this stack, these numbers, these pictures — and only later graduated to the heavy machinery. The honest limits are what make it an instrument instead of a toy.
12. The whole flight, once, in order
For the traveler who wants it plain:
- 1. NAV FIX — take the fix. The plot needs to know where "here" is.
- 2. Survey — FIND WINDOW for every destination on your list. Read the sky's price list.
- 3. Hunt — study the porkchop, inspect the dark valleys with a tap, commit with a double-tap or LOAD WINDOW and let the optimizer converge them.
- 4. Fly — PLOT the chosen arc, watch the system view, read every readout: DLA, pad flag, the Δv chain.
- 5. Plan ahead — NEXT 3 WINDOWS, one synodic period apart, each tappable.
- 6. Return — ROUND TRIP: the best outbound, the stay, the best return, one filed verdict.
- 7. Pad — read the launcher Δv from your GPS fix. Know the size of your machine.
- 8. File — MISSION VERDICT into the mission log, through the thread lock.
- 9. Verify — v∞² = C3, phase plausible, synodic rhythm sane.
Do this, all of it, and you have done preliminary mission design the way it is actually done — the way every trajectory team on Earth does it, with darker screens and older coffee. The instrument does not fly the ship. It never will. It gives the navigator true numbers, honestly derived, and gets out of the way.
That is maximum functionality. That is the whole instrument.
— Solid, for the mission record. Written for the future space travelers, who will need no introduction to any of this.