Part of the launch-sim epic #412 (PRD-031 / RFC-033), surfaced by the data-hygiene pass (commit 58530549).
What this is
Five mission launch vehicles have no matching static/data/fleet/launcher/*.json entry at all — so their missions can't link a canonical launcher and can't get a vehicle-accurate flagship launch profile. They currently fall back to the generic representative-tier ascent.
| Vehicle |
Missions blocked |
Notes |
| Delta IV Heavy (+ Star 48BV) |
parker-solar-probe |
low-TWR cryo upper stage → also needs coast+restart (Track 2) |
| Titan IIIE / Centaur |
voyager-1, voyager-2, viking1 |
iconic; Centaur upper → coast+restart; core+2 UA1205 solids → parallel-boost (Track 3) |
| Titan IVB / Centaur |
cassini |
Centaur upper → coast+restart; 2 SRMU solids → parallel-boost |
| M-V (Mu-V) |
hayabusa1 |
Japanese 3-stage solid |
| Athena II |
lunar-prospector |
US small solid launcher |
Decision needed (later)
For each family, decide whether to:
- Author a full fleet entry + flagship profile (real stage data + provenance, like proton-k/titan-ii-glv/saturn-ib), or
- Leave on the generic fallback (mission still launches, just not vehicle-accurate).
Most of these depend on the integrator tracks in #412 anyway — Delta IV / Titan III / Titan IV all need coast+restart and/or parallel-boost before their real profiles would fly a genuine orbit rather than a suborbital lob. So this is naturally after the closed-loop-guidance + coast/restart + parallel-boost work lands.
Not in scope here
The near-miss bucket (vehicle string maps to a variant of an existing fleet entry — Atlas SLV-3C vs -3D, Long March 3A vs 3B, Titan II G vs GLV, Molniya-M / Soyuz 11A511 vs the R-7 family) is a separate call: link-with-a-caveat vs new entry. Tracked separately if we decide to close it.
Part of the launch-sim epic #412 (PRD-031 / RFC-033), surfaced by the data-hygiene pass (commit 58530549).
What this is
Five mission launch vehicles have no matching
static/data/fleet/launcher/*.jsonentry at all — so their missions can't link a canonical launcher and can't get a vehicle-accurate flagship launch profile. They currently fall back to the generic representative-tier ascent.Decision needed (later)
For each family, decide whether to:
Most of these depend on the integrator tracks in #412 anyway — Delta IV / Titan III / Titan IV all need coast+restart and/or parallel-boost before their real profiles would fly a genuine orbit rather than a suborbital lob. So this is naturally after the closed-loop-guidance + coast/restart + parallel-boost work lands.
Not in scope here
The near-miss bucket (vehicle string maps to a variant of an existing fleet entry — Atlas SLV-3C vs -3D, Long March 3A vs 3B, Titan II G vs GLV, Molniya-M / Soyuz 11A511 vs the R-7 family) is a separate call: link-with-a-caveat vs new entry. Tracked separately if we decide to close it.