JUICE (Jupiter Icy Moons Explorer)

JUICE (Jupiter Icy Moons Explorer) is catalogued in this registry as a mission, held in the frame of Ganymede, from Future missions (curated).

Registry id MISSION_JUICE · source layer missions · provenance PROCESSED — derived deterministically from source catalogues (unit, frame and epoch conversions, cross-source reconciliation) — no value invented

Exists from 2023-01-01 00:00:00 UTC (JD 2459945.5) — no end date is recorded.

Open JUICE (Jupiter Icy Moons Explorer) in the live scene → The scene composes a position for any date and is where a figure becomes a picture. It downloads the whole catalogue first: measured against the built product, an object outside the core resolves after about 16 s over a local network and about 147 s over a 4 Mbit link, having transferred roughly 70 MB. If you cannot wait that long, this page is the answer.

Classification

Kindmission
Originartificial (made by humans)
Planetary protectiontarget Ganymede · contact class surface · COSPAR category IVb under the policy in force at launch (IVb under the 2026 policy) · documentation: undocumented — a DOCUMENTATION fact, never a compliance verdict

The catalogue's own note

ESA → Ganymede (en route). En route to the Jupiter system; Jupiter arrival announced ~2031, a dedicated Ganymede orbit phase announced from ~2034. Studies Ganymede, Callisto and Europa. The flown spacecraft is catalogued separately (COSPAR 2023-053A). Flown spacecraft catalogued separately as COSPAR 2023-053A; this marker is the mission annotation at its target. Cross-referenced to Launch Library 2 launch 4066e51e-93ce-46f7-9806-9d2d712107a6 (The Space Devs) — the matching LL2 upcoming-launch marker is suppressed at bake (one rendering per mission). [ESA JUICE mission (esa.int/juice; launch 2023-04-14); checked 2026-07-21]

Reproduced as the source wrote it. Author-year citations link to their DOI where one is registered.

What this registry does not know about it

These are absences in the catalogues aggregated here, not measurements of zero, and not statements that the quantity is unknown to science:

Where this record comes from

DatabaseFuture missions (curated)
AuthorityPublic mission announcements (NASA/ESA mission pages) · Launch Library 2 cross-refs (The Space Devs) · JPL Horizons predicted ephemerides
LicencePublic record
How it enteredCurated data-as-code (src/ingest/catalogs/missions.ts) — quarterly manual curation
CoverageAnnounced / en-route missions placed as planned-marker annotations on their target bodies (no invented trajectory; existence from the announced window-lo / launch year only when public). Each row carries its cited status/window + the LL2 launch UUID where one exists (the dedup key against the launchlibrary layer — one rendering per mission); a launched mission cross-references its flown COSPAR object. Published PREDICTED trajectories ride the flown object via the horizons-predicted layer, never this marker.

This database remains the property of its owners and is reused under its own licence. If you quote a value from this page, name that database alongside SolarSystemRegistry.org.