LaunchDetect

Launch Watch · Spaceflight

Published

Juno’s orbit changes, reconstructed from 77 perijove dates

Calculate 76 intervals from NASA’s 77 Juno perijove dates, track the moon-encounter steps, and separate historical cadence from the unflown 14-day plan.

Juno’s nominal wait between close Jupiter passes shrank from 53 days to 33 days. That is a 37.7% shorter interval, equivalent to about 60.6% more passes per unit time in a simple reciprocal-period comparison. Both percentages describe the same change, with different denominators.

NASA’s published perijove table makes the intervening steps visible. Taking differences between all 77 dates yields 76 calendar intervals clustered around 53, 43, 38, 35 and 33 days. The historical sequence also explains why the original 14-day science-orbit plan should not be inserted into a chart of the listed encounters.

A date record, from insertion to PJ76

A perijove is a closest approach to Jupiter. The NASA orbit table starts with Jupiter orbit insertion, labeled PJ0, on July 5, 2016. The retained table ends at PJ76 on September 14, 2025. Its dates are explicitly UTC.

We subtracted each date from the next one, without rounding a fitted orbital period or filling gaps between numbered rows. The perijove identifiers run continuously from 0 through 76. Since the first row has no predecessor, 77 rows provide 76 adjacent intervals, not 77.

All 76 successive UTC-date intervals from Juno’s PJ0-PJ76 table form steps near 53, 43, 38, 35 and 33 days. A separate dashed 14-day line marks the original unflown science-orbit plan.
Original LaunchDetect calculation from the complete NASA perijove table. Date-only differences are quantized calendar intervals, not precise orbital periods or science-exposure durations. Open full-size chart

The chart shows every calculated interval. It is a calendar-scale check on the published encounter history, rather than an ephemeris calculation. Its dashed 14-day reference is marked as the unflown original plan and contributes no data points to the interval series.

The five interval groups

All 76 adjacent UTC-date intervals, grouped by encounter stage
StageArrival perijovesIntervalsRange (days)Mean (days)
Before the June 2021 Ganymede changePJ1–PJ343452–5452.91
After Ganymede, before EuropaPJ35–PJ451143–4443.45
After Europa, before the first close Io passPJ46–PJ571238–3938.08
Between the two close Io passesPJ5813535.00
After the second close Io passPJ59–PJ761832–3332.72

“Arrival perijove” identifies the endpoint of an interval. The PJ35 point, for example, is the time between the PJ34 and PJ35 dates. This convention places a changed cadence at the first subsequent interval that exhibits it, rather than assigning the new period backward to the approach before the moon encounter.

The group means are calculations from day-resolution dates. Their two decimal places make the arithmetic auditable; they do not supply hundredth-of-a-day orbital-period measurements. The first group’s 52–54-day spread and the last group’s 32–33-day spread need that context before anyone treats individual differences as anomalies.

Match the steps to encounters without moving their dates

NASA’s mission account attributes the large changes to the Ganymede, Europa and Io encounter sequence. It describes the June 7, 2021 Ganymede flyby reducing the nominal period from 53 to 43 days, followed by the September 2022 Europa encounter reducing it to about 38 days.

The perijove table’s PJ34 date is June 8, 2021, one day after the Ganymede encounter cited in the mission account. A nearby moon flyby and closest approach to Jupiter are different events. The table’s highlight labels should therefore be used as context, rather than silently becoming exact timestamps for the moon encounters.

The Io transition is especially easy to check directly. PJ57 is dated December 30, 2023; PJ58, February 3, 2024; and PJ59, March 7, 2024. The adjacent date differences are 35 and 33 days. A December 2023 JPL announcement described the planned changes from about 38 to 35 and then 33 days, while the later mission account describes the resulting 33-day orbit.

Why 14 days remains a separate line

In its February 17, 2017 decision announcement, NASA said Juno would remain in its 53-day orbit rather than perform the planned burn to reach a 14-day science orbit. Concerns about the propulsion system drove that decision.

Keeping the 14-day plan visible can explain why older mission descriptions differ from later ones. Including it as though it were a flown segment would change the historical claim. The date sequence analyzed here contains no 14-day adjacent interval.

A shorter wait and a faster cadence use different arithmetic

For nominal 53- and 33-day periods, the interval reduction is (53 − 33) ÷ 53 × 100 = 37.7%. Encounter frequency is proportional to one divided by the period. The relative frequency increase is therefore (53 ÷ 33 − 1) × 100 = 60.6%.

The reciprocal calculation compares idealized repeating periods. It does not count a particular year’s scheduled passes and does not measure science return. Instrument choices, geometry, operations and the observations actually obtained would all matter before translating encounter cadence into a science-yield claim.

Method and limits

The complete date-and-interval CSV preserves the source’s identifiers, UTC dates and highlights. For each row after PJ0, we parse both adjacent dates and subtract them in calendar days. Stage boundaries use the arrival-perijove ranges displayed above, and the summaries include every resulting interval exactly once.

Whole dates omit the time of day. Two events separated by a period near 33 days can land 32 or 33 calendar dates apart depending on their times, so a 32-day entry alone is not evidence of unexpected dynamics. Precise periods require precise event times or trajectory data.

This analysis ends at the retained table’s September 2025 endpoint. It makes no claim about Juno’s present health, a next encounter, or whether every listed pass achieved all intended science. The output is a reproducible view of the published historical cadence and the definitions needed to interpret it.

Read all 77 dates and their adjacent intervals
The complete published PJ0–PJ76 date sequence
PerijovePublished date (UTC)Days since previous date
PJ02016-07-05No previous row
PJ12016-08-2753
PJ22016-10-1953
PJ32016-12-1153
PJ42017-02-0253
PJ52017-03-2753
PJ62017-05-1953
PJ72017-07-1153
PJ82017-09-0152
PJ92017-10-2453
PJ102017-12-1653
PJ112018-02-0753
PJ122018-04-0153
PJ132018-05-2453
PJ142018-07-1653
PJ152018-09-0753
PJ162018-10-2952
PJ172018-12-2153
PJ182019-02-1253
PJ192019-04-0653
PJ202019-05-2953
PJ212019-07-2153
PJ222019-09-1253
PJ232019-11-0352
PJ242019-12-2653
PJ252020-02-1753
PJ262020-04-1053
PJ272020-06-0253
PJ282020-07-2553
PJ292020-09-1653
PJ302020-11-0853
PJ312020-12-3052
PJ322021-02-2153
PJ332021-04-1553
PJ342021-06-0854
PJ352021-07-2143
PJ362021-09-0243
PJ372021-10-1644
PJ382021-11-2944
PJ392022-01-1244
PJ402022-02-2544
PJ412022-04-0943
PJ422022-05-2344
PJ432022-07-0543
PJ442022-08-1743
PJ452022-09-2943
PJ462022-11-0638
PJ472022-12-1539
PJ482023-01-2238
PJ492023-03-0138
PJ502023-04-0838
PJ512023-05-1638
PJ522023-06-2338
PJ532023-07-3138
PJ542023-09-0738
PJ552023-10-1538
PJ562023-11-2238
PJ572023-12-3038
PJ582024-02-0335
PJ592024-03-0733
PJ602024-04-0933
PJ612024-05-1233
PJ622024-06-1332
PJ632024-07-1633
PJ642024-08-1833
PJ652024-09-2033
PJ662024-10-2232
PJ672024-11-2433
PJ682024-12-2733
PJ692025-01-2832
PJ702025-03-0233
PJ712025-04-0433
PJ722025-05-0733
PJ732025-06-0832
PJ742025-07-1133
PJ752025-08-1333
PJ762025-09-1432

Sources

  1. NASA: Juno Orbits table. All 77 rows, PJ0-PJ76, 2016-07-05 through 2025-09-14; dates explicitly UTC.
  2. NASA: Juno to remain in its current orbit (February 17, 2017). February 17, 2017; retain 53-day orbit, avoid planned 14-day period-reduction burn following valve concerns.
  3. JPL: Juno’s close Io encounter plan (December 27, 2023). December 27, 2023; planned 38-to-35 then 33-day changes.
  4. NASA: Juno mission overview. Describes Ganymede/Europa/Io sequence and completed February 3, 2024 change to 33 days.

Charts and calculations: LaunchDetect, using the linked factual records. No NASA or JPL endorsement is implied.