Cassine MissionPlan - RevN

1 of 217
J
Jet Propulsion Laboratory California Institute of Technology PD 699-100, Rev N JPL D-5564, Rev N
Posted Courtesy of the NASA FOIA program
FOIA 10-JPL-F-00451
2 of 217
CASSINI PROJECT DOCUMENT CHANGE NOTICE

TITLE: Changes to the Cassini Mission Plan DOCUMENT TITLE: Cassini Mission Plan, PD 699-100, Rev. N JPL D-NUMBER: JPL D-5564, Rev. N DESCRIPTION OF CHANGE:
This revised document reflects changes since revision M. All changes based on the latest knowledge of mission activities and spacecraft capabilities have been documented. Changes have been made to reflect the re-desgned Probe Mission, which has affected the SOI burn, Probe release activities, and initial tour orbits. In addition, more detail has been added to descriptions of cruise science, SOI activities, Probe mission, and Tour activities.
DOCUMENT CHANGE ID: Revision N PAGE 1 OF 1 DATE: 10 May 2002
DISTRIBUTION
Document Distribution List:
APPROVED BY:
[Include document approval authorities and document custodian]
list maintained by Mission Planning
Dave Seal, Mission Planning Lead Custodian: Jim Frautnick
Date
FOIA 10-JPL-F-00451
3 of 217
MISSION PLAN TABLE OF CONTENTS SECTION 1 INTRODUCTION.................................................................................................. 1-1 1.1 Relationship to Other Documents ................................................................................ 1-1 1.2 Schedule for Document Updates .................................................................................. 1-1 SECTION 2 MISSION OVERVIEW ......................................................................................... 2-1 2.1 Mission Synopsis............................................................................................................. 2-1 2.2 Interplanetary Trajectory ............................................................................................... 2-7 2.3 Tour Overview ................................................................................................................ 2-7 2.4 Reference tables............................................................................................................. 2-23 SECTION 3 SCIENCE OBJECTIVES ....................................................................................... 3-1 3.1 General Objectives .......................................................................................................... 3-1 3.2 Specific Objectives Before Saturn ................................................................................. 3-1 3.3 Specific Objectives at Saturn.......................................................................................... 3-2 3.4 Specific Objectives at Titan ............................................................................................ 3-2 3.5 Specific Objectives at the Rings..................................................................................... 3-2 3.6 Specific Objectives at the Icy Satellites......................................................................... 3-2 3.7 Specific Objectives at the Saturn Magnetosphere ...................................................... 3-2 3.8 Orbiter Science Instruments .......................................................................................... 3-3 3.8.1 Cassini Plasma Spectrometer (CAPS) .................................................................. 3-3 3.8.2 Cosmic Dust Analyzer (CDA)............................................................................... 3-3 3.8.3 Composite Infrared Spectrometer (CIRS)............................................................ 3-4 3.8.4 Ion and Neutral Mass Spectrometer (INMS) ...................................................... 3-5 3.8.5 Imaging science subsystem (ISS) .......................................................................... 3-5 3.8.5 Magnetometer (MAG)............................................................................................ 3-5 3.8.6 Radio Science Subsystem (RSS) ............................................................................ 3-6 3.8.7 Ultraviolet Imaging Spectrograph (UVIS)........................................................... 3-7 3.8.8 Visible and Infrared Mapping Spectrometer (VIMS) ........................................ 3-8 3.8.10 RADAR..................................................................................................................... 3-8 3.8.11 Radio and Plasma Wave Spectrometer (RPWS) ................................................. 3-8 3.8.12 Magnetospheric Imaging Instrument (MIMI) .................................................... 3-9 3.9 Huygens Probe Instruments.......................................................................................... 3-9 3.9.1 Aerosol Collector Pyrolyzer (ACP) ...................................................................... 3-9 3.9.2 Gas Chromatograph and Mass Spectrometer (GCMS) ..................................... 3-9 3.9.3 Descent Imager and Spectral Radiometer (DISR) ............................................ 3-10 3.9.4 Doppler Wind Experiment (DWE) ..................................................................... 3-10 3.9.5 Huygens Atmospheric Structure Instrument (HASI)...................................... 3-10 3.9.6 Surface Science Package (SSP)............................................................................. 3-11 SECTION 4 FLIGHT SYSTEM DESCRIPTIONS .................................................................. 4-1 4.1 Launch Vehicle Description .......................................................................................... 4-1 4.2 Orbiter Description ......................................................................................................... 4-2 4.2.1 S/C Attitude Definition ......................................................................................... 4-3 4.2.2 Attitude Commanding ........................................................................................... 4-4 4.2.3 Inertial Vector Propagation ................................................................................... 4-5 4.2.4 Structure Subsystem ............................................................................................... 4-7 4.2.5 Radio Frequency Subsystem ................................................................................. 4-7 4.2.6 Power and Pyrotechnics Subsystem..................................................................... 4-7 4.2.7 Command and Data Subsystem ........................................................................... 4-7 4.2.8 Attitude and Articulation Control Subsystem.................................................... 4-9 i
Posted Courtesy of the NASA FOIA program FOIA 10-JPL-F-00451
4 of 217
4.2.9 Cabling Subsystem................................................................................................ 4-12 4.2.10 Propulsion Module Subsystem ........................................................................... 4-12 4.2.11 Temperature Control Subsystem........................................................................ 4-15 4.2.12 Mechanical Devices Subsystem .......................................................................... 4-16 4.2.13 Electronic Packaging Subsystem ........................................................................ 4-16 4.2.14 Solid State Recorder Subsystem.......................................................................... 4-16 4.2.15 Antenna Subsystem .............................................................................................. 4-16 4.2.16 Science Instruments .............................................................................................. 4-17 4.2.17 Orbiter Consumable Budgets.............................................................................. 4-17 4.3 The Huygens Probe System......................................................................................... 4-17 4.3.1 Entry Subsystem.................................................................................................... 4-17 4.3.2 Inner Structure Subsystem................................................................................... 4-21 4.3.3 Thermal Control Subsystem................................................................................ 4-21 4-4.3.4 Electrical Power Subsystem................................................................................. 4-21 4.3.5 Command and Data Management Subsystem ................................................. 4-23 4.3.6 Probe Data Relay Subsystem............................................................................... 4-23 4.3.7 Huygens science Instrumentation ...................................................................... 4-23 SECTION 5 OPERATIONS STRATEGIES ............................................................................. 5-1 5.1 Operations Concepts ...................................................................................................... 5-1 5.1.1 ON-BOARD operations.......................................................................................... 5-1 5.1.2 Ground planning & operations............................................................................. 5-2 5.1.3 Data distribution ..................................................................................................... 5-3 5.1.4 Activity Overview................................................................................................... 5-4 5.2 Telecommunications....................................................................................................... 5-4 5.2.1 Antenna Switches.................................................................................................... 5-5 5.2.2 Uplink ....................................................................................................................... 5-5 5.2.3 Bits to ground .......................................................................................................... 5-5 5.3 data storage...................................................................................................................... 5-8 5.3.1 Partitioning .............................................................................................................. 5-8 5.3.2 Data policing.......................................................................................................... 5-13 5.3.3 Carryover ............................................................................................................... 5-14 5.3.4 DSN lockup............................................................................................................ 5-14 5.4 attitude control .............................................................................................................. 5-14 5.4.1 Spacecraft articulation .......................................................................................... 5-18 5.4.2 Target Motion Compensation ............................................................................. 5-18 5.4.3 Titan atmospheric model ..................................................................................... 5-19 5.4.4 Minimum Flyby Altitudes ................................................................................... 5-19 5.5 Navigation...................................................................................................................... 5-20 5.5.1 Tracking requirements ......................................................................................... 5-20 5.5.2 Maneuvers.............................................................................................................. 5-22 5.5.3 Encounter redesign ............................................................................................... 5-23 5.6 Environmental hazards & control .............................................................................. 5-24 5.6.1 Radiation ................................................................................................................ 5-24 5.6.2 Thermal control and sun Exposure .................................................................... 5-24 5.6.3 Debris...................................................................................................................... 5-26 5.7 periodic activities .......................................................................................................... 5-26 5.7.1 Engineering Maintenance .................................................................................... 5-27 5.7.2 Huygens Probe Checkouts .................................................................................. 5-27 5.7.3 Periodic Instrument Maintenance ...................................................................... 5-30 SECTION 6: LAUNCH AND CRUISE ACTIVITIES.............................................................. 6-1 6.1 Launch Phase................................................................................................................... 6-1 ii
5 of 217
6.1.1 Launch Sequence subphase ................................................................................... 6-1 6.1.2 TCM 1 Subphase ..................................................................................................... 6-4 6.2 Inner Cruise Phase .......................................................................................................... 6-6 6.2.1 Venus 1 Flyby Subphase ........................................................................................ 6-9 6.2.2 Instrument Checkout Subphase............................................................................ 6-9 6.2.3 Venus 2 - Earth Subphase .................................................................................... 6-10 6.3 Outer Cruise Phase ...................................................................................................... 6-20 6.3.1 Spacecraft HGA Checkout subphase ................................................................ 6-22 6.3.2 Instrument Checkout-2 Subphase ...................................................................... 6-22 6.3.3 Jupiter Subphase ................................................................................................... 6-23 6.3.4 Quiet Cruise Subphase......................................................................................... 6-26 6.4 Science Cruise Phase..................................................................................................... 6-27 6.4.1 Space Science Subphase ....................................................................................... 6-27 6.4.2 Approach Science Subphase............................................................................... 6-28 SECTION 7: SATURN AND TOUR ACTIVITIES.................................................................. 7-1 7.1 Saturn approach and phoebe ........................................................................................ 7-1 7.2 Saturn Orbit Insertion..................................................................................................... 7-2 7.2.1 Overview .................................................................................................................. 7-2 7.2.2 SOI Trajectory .......................................................................................................... 7-4 7.2.3 SOI Critical Sequence Overview........................................................................... 7-8 7.2.4 SOI Burn ................................................................................................................... 7-9 7.2.5 Attitude Control Strategy .................................................................................... 7-10 7.2.6 SSR Strategy ........................................................................................................... 7-11 7.2.7 Telecom Strategy ................................................................................................... 7-11 7.2.8 Science Strategy..................................................................................................... 7-12 7.3 Initial Orbit..................................................................................................................... 7-13 7.4 The Huygens Probe Mission ....................................................................................... 7-13 7.4.1 Probe Separation ................................................................................................... 7-15 7.4.2 Probe Relay ............................................................................................................ 7-19 7.5 Optical Remote Sensing Encounters .......................................................................... 7-25 7.6 RADAR encounters ...................................................................................................... 7-26 7.7 Radio Science encounters............................................................................................. 7-29 SECTION 8: OPERATIONAL MODES, GUIDELINES AND CONSTRAINTS, AND CONTROLLED SCENARIO TIMELINES................................................................................ 8-1 8.1 Mission Planning Framework ....................................................................................... 8-1 8.1.1 Operational Mode Definition ................................................................................ 8-1 8.1.2 Sequence Constructs Definition............................................................................ 8-1 8.1.3 Requirements on the Design of Operational Modes.......................................... 8-2 8.1.4 Requirements on the Design of Modules ............................................................ 8-3 8.2 Mission Design Guidelines & Constraints Definition ............................................. 8-10 8.3 Mission Design Guidelines and Constraints............................................................. 8-10 8.3.1 Operational Modes and Sequence Constructs.................................................. 8-10 8.3.2 Sequence Development........................................................................................ 8-11 8.3.3 Spacecraft Pointing ............................................................................................... 8-14 8.3.4 Telecommunications............................................................................................. 8-14 8.3.5 Management of On-Board Data.......................................................................... 8-16 8.3.6 Pre-Saturn Science Activities............................................................................... 8-17 8.3.7 Saturn Tour & SOI ................................................................................................ 8-17 8.3.8 Miscellaneous ........................................................................................................ 8-18 8.4 Controlled Scenario Timelines .................................................................................... 8-19 iii
6 of 217
ECR CHANGE LOG GUIDELINES & CONSTRAINTS HISTORY APPENDICIES REQUIREMENTS COMPLIANCE A B SATURNIAN SYSTEM DESCRIPTION K SATURN MYTHOLOGY L CASSINI AND HUYGENS, THE SCIENTISTS ACRONYM LIST
iv
7 of 217
SECTION 1 INTRODUCTION The Mission Plan is the principal reference for high level descriptions of the Cassini mission. It documents the interplanetary cruise and Saturn tour trajectories; high level spacecraft and activity designs; operational strategies and options; and guidelines and constraints for mission operations. It is not within the scope of the Mission Plan to illustrate any one sequence to the granularity of seconds or minutes, or describe individual states of spacecraft components. Neither is it to describe high level project policy. The Mission Plan is the intermediary between the project requirements -- and their associated documents -- and the detailed mission sequences, along with their associated documents. This plan serves to guide the development of detailed event timelines from before launch through end of mission and will evolve throughout the mission as a living document. Section 2 provides a brief overview of the Cassini mission, including the spacecraft trajectory during cruise and tour, and a summary of the main events during the flight. Section 3 describes the science objectives of the mission. Section 4 describes the spacecraft, probe, instrument, and launch vehicle systems. Section 5 illustrates the primary operational strategies developed or led by the mission planners to operate the spacecraft and solve some of the more difficult problems which cross systems. Section 6 describes the details of activities during launch and interplanetary cruise, whereas section 7 covers the tour phase. Section 8 documents missionlevel guidelines and constraints, operational modes, and timelines for crucial periods, and is under project level change control. Changes to Section 8 require engineering change requests (ECRs) and the approval of the project change control board, whereas changes to the remaining sections require approval of the Mission Planning office. Appendices are included as reference material. 1.1 RELATIONSHIP TO OTHER DOCUMENTS
The Mission Plan implements project policy documented in the Project Policies and Requirements Document (699-004). Other resources listed below are relevant to many sections of the Mission Plan and are referred to where possible so as not to duplicate information or require parallel updates should information change. Resource Document Number Project Policies and Requirements 699-004 Orbiter Functional Requirements 699-205 Navigation Plan 699-101 Consumables Report 699-523 Post-Jupiter Scoping Package (Internal memorandum) Risk Management Plan 699-015 1.2 SCHEDULE FOR DOCUMENT UPDATES Version J K L M N Release Jul 1999 Jan 2000 Jul 2000 Jun 2001 May 2002
Past Mission Plan releases have been as follows: Version Release Version Release Jul 1988 F Apr 1995 Initial G Feb 1997 A May 1990 G.1 Jun 1997 B Mar 1993 G.2 Feb 1998 C Aug 1993 H Mar 1998 D Feb 1994 I Dec 1998 E Sep 1994
This version documents the state of the mission as understood as of the release date. Due to space limitations, discussion of unused mission options and past operational strategies have been removed where they are no longer relevant, and replaced with as-flown descriptions. Refer to previous versions of the Mission Plan for reconstruction of these options. 1-1
8 of 217
SECTION 2 MISSION OVERVIEW 2.1 MISSION SYNOPSIS The Cassini spacecraft is a combined Saturn orbiter and Titan atmospheric probe (to be delivered on the first or second flyby of Titan). It is a three-axis stabilized spacecraft equipped for 27 diverse science investigations with 12 orbiter and 6 Huygens probe instruments, one high gain and two low gain antennas, three Radioisotope Thermal Generators (RTGs) for power, main engines, attitude thrusters, and reaction wheels. Cassini was successfully launched on 15 October 1997 using the Titan IV/Centaur launch vehicle with Solid Rocket Motor Upgrade (SRMU) strap-ons and a Centaur upper stage. The spacecraft is flying a 6.7-year Venus-Venus-Earth-Jupiter Gravity Assist (VVEJGA) trajectory to Saturn, during which cruise science is planned to checkout, calibrate, and maintain the instruments as well as characterize the instruments and perform limited science observations. Cruise science is limited by flight software available on the spacecraft as well as cost, scheduling and workforce constraints. Limited science data collection occurred during the Venus flybys and science and calibration occurred during the Earth flyby. As the spacecraft approached Jupiter, science activities picked up as Jupiter observations served as preparation for the four-year tour of the Saturnian system. During most of the early portion of cruise, the High Gain Antenna (HGA) was required to shield most of the spacecraft from the Sun and only low-rate communications via the spacecrafts Low Gain Antennas (LGAs) was possible. Six months after the Earth flyby, the spacecraft was far enough from the Sun to orient the High Gain Antenna (HGA) to Earth enabling much faster communications. Following the Jupiter flyby, the spacecraft attempts to detect gravitational waves using its Ka-band and X-band radio equipment. Instrument calibrations, checkout, and other tour preparations are also conducted during the cruise between Jupiter and Saturn. In the six months preceding its arrival at Saturn, the spacecraft will conduct more intensive science activities, including observations of Phoebe immediately before arrival on 11 June 2004. During Saturn Orbit Insertion (SOI) on 1 July 2004, the spacecraft makes its closest approach to the planets surface during the entire mission at an altitude of only 0.3 Saturn radii (18,000 km). Due to this unique opportunity, the approximately 100-minute SOI burn required to place Cassini in orbit around Saturn executes sooner than its optimal point centered around periapsis, and instead ends at periapsis, allowing science observations immediately after closest approach. At the third targeted Titan flyby, the ESA Huygens probe descends through the atmosphere of Titan to its surface. This probe is released from the orbiter 21 to 22 days before the first Titan flyby. Eleven days after probe release, the orbiter performs a deflection maneuver to place itself on the proper trajectory for the encounter. The probe flies directly into Titan's atmosphere, where it relays data to the orbiter for up to 2.5 hours during its descent to the surface. The orbiter then continues on a tour of the Saturnian system, including multiple close Titan flybys for gravity assist and science acquisition. The Titan flybys and Saturn orbits have been designed to maximize science coverage while meeting resource and operations limitations. Targeted and non-targeted flybys of selected icy satellites have also been included to determine icy satellite surface compositions and geologic histories. Cassinis orbital inclination varies widely to investigate the field, particle, and wave environment at high latitudes, including the hypothesized source of the unique Saturn kilometric radiation. High inclinations also permit high-latitude Saturn radio occultations, viewing of Saturn polar regions, and more nearly vertical viewing of Saturn's rings. The baseline mission ends in mid-2008, for a total mission duration of 10.7 years. 2-1
9 of 217
CASSINI MISSION EVENT SUMMARY Name Epoch Launch 1997-Oct-15 APHELION 1997-Nov-06 TCM-1 1997-Nov-09 o Conjunction 1998-Feb-09 TCM-2 1998-Feb-25 PERIHELION 1998-Mar-27 (TCM-3) 1998-Apr-08 Venus flyby 1998-Apr-26 (TCM-4) 1998-May-14 DSM 1998-Dec-03 DSM-5 1998-Dec-03 APHELION 1998-Dec-07 HGA 1998-Dec-28 o Opposition 1999-Jan-09 LGA 1999-Jan-21 TCM-6 1999-Feb-04 TCM-7 1999-May-18 (TCM-8) 1999-Jun-03 Venus flyby 1999-Jun-24 PERIHELION 1999-Jun-29 TCM-9 1999-Jul-06 TCM-10 1999-Jul-19 TCM-11 1999-Aug-02 TCM-12 1999-Aug-11 o Conjunction 1999-Aug-17 Earth flyby 1999-Aug-18 TCM-13 1999-Aug-31 o Opposition 1999-Sep-13 Enter Asteroid Belt 1999-Dec-11 HGA 2000-Feb-01 Exit Asteroid Belt 2000-Apr-12 o Conjunction 2000-May-13 TCM-14 2000-Jun-14 TCM-15 2000-Sep-14 o Opposition 2000-Nov-28 (TCM-16) 2000-Dec-07 2000-Dec-30 Jupiter flyby TCM-17 2001-Feb-28 o Conjunction 2001-Jun-07 o Opposition 2001-Dec-16 TCM-18 2002-Apr-03 o Conjunction 2002-Jun-21 o Opposition 2002-Dec-27 TCM-19 2003-May-01 o Conjunction 2003-Jul-01 o Opposition 2004-Jan-04 TCM-20 2004-May-27 2004-Jun-11 Phoebe flyby TCM-21 2004-Jun-16 TCM-22 2004-Jun-21 SOI 2004-Jul-01 o Conjunction 2004-Jul-08 PRM 2004-Aug-23 Titan A 2004-Oct-26 Titan B 2004-Dec-13 2004-Dec-24 Probe Separation ODM 2004-Dec-29 2005-Jan-14 Titan C / Huygens o Opposition 2005-Jan-13 EOM 2008-Jun-30
DOY 288 310 313 040 056 086 098 116 134 337 337 341 362 009 021 035 138 154 175 180 187 200 214 223 229 230 243 256 345 032 103 134 166 258 333 342 365 059 158 350 093 172 361 121 182 004 148 163 168 173 183 190 236 300 348 359 364 014 013 182
DOW Wed Thu Sun Mon Wed Fri Wed Sun Thu Thu Thu Mon Mon Sat Thu Thu Tue Thu Thu Tue Tue Mon Mon Wed Tue Wed Tue Mon Sat Tue Wed Sat Wed Thu Tue Thu Sat Wed Thu Sun Wed Fri Fri Thu Tue Sun Thu Fri Wed Mon Thu Thu Mon Tue Mon Fri Wed Fri Thu Mon
Comment C3 = 16.6 km2/sec2 Sun range = 1.01 AU V = 2.7 m/sec on ME Inferior conjunction V = 0.2 m/sec on RCS Sun range = 0.67 AU Canceled Altitude = 284 km; Speed = 11.8 km/sec Canceled V = 450 m/sec V = 450.2 m/sec on ME Sun range = 1.58 AU 25 day checkout period Probe thermal constraints restrict HGA usage V = 11.6 m/sec on ME V = 0.2 m/sec on RCS Canceled Altitude = 603 km; Speed = 13.6 km/sec Sun range = 0.72 AU V = 43.5 m/sec on ME V = 5.1 m/sec on ME V = 36.3 m/sec on ME V = 12.3 m/sec on ME Inferior conjunction Altitude = 1175 km; Speed = 19.0 km/sec V = 6.7 m/sec on ME Sun range = 2.2 AU HGA is Earth-pointed; use after this date Sun range = 3.3 AU Superior Conjunction V = 0.6 m/sec on ME V = 0.2 m/sec on RCS Gravity Wave Opportunity Cancelled Altitude = 9,723,890 km; Speed = 11.6 km/sec V = 1.0 m/sec on ME Superior Conjunction Gravity Wave Experiment - opp20 days V = 1.2 m/sec on ME Conjunction Experiment - conj15 days Gravity Wave Experiment - opp20 days V = 0.5 m/sec on RCS Conjunction Experiment - conj15 days Early Gravity Wave Experiment - Oct-Nov 2003 V = 35 m/sec on ME Altitude = 2000 km; Speed = 6.4 km/sec V = 5.5 m/sec on ME Emergency TCM window if needed V = 633 m/sec V = 391 m/sec Altitude = 1200 km; Speed = 6.1 km/sec Altitude = 2346 km; Speed = 6.1 km/sec V = 21 m/sec Altitude = 60,000 km; Speed = 5.4 km/sec End of 4-year tour
FOIA 10-JPL-F-00451
10 of 217
1997 PHASES SUBPHASES

u La
Launch
1998
Inner Cruise
1999
2000
2001
Outer Cruise
2002
2003
Science Cruise
2004
Initial Orbit
O N D J F M A M J J A S O N D J F M AM J J A S ON D J F M AM J J A S O N D J FM A M J J A S ON D J FM A M J J A S ON D J FM A M J J A S ON D J FM A M J J A
Launch Sequence TCM1 Venus 1
ICO #1
Venus 2 - Earth
HGA Transition
ICO #2
Jupiter
Quiet Cruise
Space Science
Approach Science
nc
h n Ve
us
2 us th en Ear V
Ju
pi
r te
e nc ie n Sc O
Phoebe flyby
SO
EVENTS MANEUVERS PERIHELION/ APHELION

CONJUNCTION OPPOSITION
c
A P A 1.58 AU
DSM
SOI
P 0.72 AU
1.02 AU 0.68 AU
GWE opp
GWE
c
Conj. Experiment
GWE
Conj. Experiment
GWE
c
c
EARTH# SUN HGA#
Inf
Inf
SUN
Sup
EARTH HGA
Sup
Sup
Sup
EARTH EARTH/SCIENCE TARGET
Sup
POINTING ANTENNA
bps
DOWNLINK DATA RATE CAPABILITY

(Ranging ON)
(log scale) 248 k 142 k 82 k 35 k 22 k
high rates
LGA
LGA
HGA
HGA
LGA
HGA
948 200 40
21
DSN COVERAGE REQUESTED (passes/week)
14 7 0 0 200 400 600 800 1000 1200 1400 1600 1800 2000 2200 2400
DAYS FROM LAUNCH
* Refer to Appendix J for more information about data rate capability.

Superior Conjunction causes degradation of telemetry and radiometric tracking data.
#
Indicates actual instrument checkout window.
Figure 2.1: Cassini Cruise Segment Timeline
FOIA 10-JPL-F-00451
11 of 217
FOIA 10-JPL-F-00451
12 of 217
CASSINI PHASES, SUBPHASES AND LOAD BOUNDARIES (CRUISE) Length Start End Phase Subphase Name DOW Date DOW (days) Date C0 2 1997-288T00:00 Wed 1997-290T00:00 Fri Launch C1 7 1997-290T00:00 Fri 1997-297T00:00 Fri C2 7 1997-297T00:00 Fri 1997-304T00:00 Fri Launch TCM 1 C3 7 1997-304T00:00 Fri 1997-311T00:00 Fri C4 7 1997-311T00:00 Fri 1997-318T00:00 Fri C5 66 1997-318T00:00 Fri 1998-019T00:00 Mon C6 56 1998-019T00:00 Mon 1998-075T00:00 Mon C7 56 1998-075T00:00 Mon 1998-131T00:00 Mon Venus 1 C8 63 1998-131T00:00 Mon 1998-194T00:00 Mon C9 63 1998-194T00:00 Mon 1998-257T00:00 Mon C10 1998-257T00:00 Mon 1998-320T00:00 Mon 63 Inner Cruise C11 1998-320T00:00 Mon 1999-025T00:00 Mon 70 ICO-1 C12 1999-025T00:00 Mon 1999-074T00:00 Mon 49 C13 1999-074T00:00 Mon 1999-130T00:00 Mon 56 C14 1999-130T00:00 Mon 1999-193T00:00 Mon 63 Venus2-Earth C15 1999-193T00:00 Mon 1999-249T00:00 Mon 56 C16 1999-249T00:00 Mon 1999-312T00:00 Mon 63 C17 1999-312T00:00 Mon 2000-017T00:00 Mon 70 C18 2000-017T00:00 Mon 2000-066T00:00 Mon 49 HGA transition C19 2000-066T00:00 Mon 2000-127T00:00 Sat 61 C20 2000-127T00:00 Sat 2000-192T00:00 Mon 65 C21 2000-192T00:00 Mon 2000-255T00:00 Mon 63 ICO-2 C22 2000-255T00:00 Mon 2000-310T05:25 Sun 55 C23 2000-310T05:25 Sun 2001-014T11:00 Sun 70 C24 2001-014T11:00 Sun 2001-071T09:55 Mon 57 Jupiter Outer Cruise C25 2001-071T09:55 Mon 2001-120T00:00 Mon 49 C26 2001-120T00:00 Mon 2001-190T00:00 Mon 70 C27 2001-190T00:00 Mon 2001-252T00:00 Sun 62 C28 2001-252T00:00 Sun 2001-309T00:00 Mon 57 C29 2001-309T00:00 Mon 2002-014T00:00 Mon 70 Quiet Cruise C30 2002-014T00:00 Mon 2002-070T00:00 Mon 56 C31 2002-070T00:00 Mon 2002-126T00:00 Mon 56 C32 2002-126T00:00 Mon 2002-189T00:00 Mon 63 C33 2002-189T00:00 Mon 2002-266T00:00 Mon 77 C34 2002-266T00:00 Mon 2002-336T00:00 Mon 70 C35 2002-336T00:00 Mon 2003-048T00:00 Mon 77 C36 2003-048T00:00 Mon 2003-104T00:00 Mon 56 C37 2003-104T00:00 Mon 2003-167T00:00 Mon 63 Space Science C38 2003-167T00:00 Mon 2003-223T00:00 Mon 56 Science Cruise C39 2003-223T00:00 Mon 2003-293T00:00 Mon 70 C40 2003-293T00:00 Mon 2004-010T00:00 Sat 82 C41 was merged with C40 for GWE. C42 2004-010T00:00 Sat 2004-052T00:00 Sat 42 C43 2004-052T00:00 Sat 2004-094T00:00 Sat 42 Approach Science C44 2004-094T00:00 Sat 2004-136T00:00 Sat 42
FOIA 10-JPL-F-00451
13 of 217
CASSINI PHASES AND LOAD BOUNDARIES (TOUR)* Start End date DOW date Phase Name Tour S1 2004-136T00:00 Sat 2004-171T01:38 S2 2004-171T01:38 Sat 2004-212T23:05 S3 2004-212T23:05 Fri 2004-255T19:10 S4 2004-255T19:10 Sat 2004-290T18:40 S5 2004-290T18:40 Sat 2004-318T16:59 S6 2004-318T16:59 Sat 2004-351T15:03 S7 2004-351T15:03 Thu 2005-022T10:38 S8 2005-022T10:38 Sat 2005-058T00:36 S9 2005-058T00:36 Sun 2005-099T05:15 S10 2005-099T05:15 Sat 2005-134T02:50 S11 2005-134T02:50 Sat 2005-169T01:34 S12 2005-169T01:34 Sat 2005-210T22:36 S13 2005-210T22:36 Fri 2005-242T21:53 S14 2005-242T21:53 Tue 2005-281T15:57 S15 2005-281T15:57 Sat 2005-316T17:01 S16 2005-316T17:01 Sat 2005-351T14:21 S17 2005-351T14:21 Sat 2006-028T11:23 S18 2006-028T11:23 Sat 2006-070T00:35 S19 2006-070T00:35 Sat 2006-112T05:15 S20 2006-112T05:15 Sat 2006-154T02:39 S21 2006-154T02:39 Sat 2006-196T00:06 S22 2006-196T00:06 Sat 2006-230T22:06 S23 2006-230T22:06 Fri 2006-269T19:53 S24 2006-269T19:53 Tue 2006-295T18:26 S25 2006-295T18:26 Sun 2006-328T16:30 S26 2006-328T16:30 Fri 2007-005T13:50 S27 2007-005T13:50 Fri 2007-048T10:52 S28 2007-048T10:52 Sat 2007-088T08:04 S29 2007-088T08:04 Thu 2007-124T22:00 S30 2007-124T22:00 Fri 2007-162T03:10 S31 2007-162T03:10 Mon 2007-195T01:06 S32 2007-195T01:06 Sat 2007-223T23:20 S33 2007-223T23:20 Sat 2007-265T20:51 S34 2007-265T20:51 Sat 2007-305T18:40 S35 2007-305T18:40 Thu 2007-347T16:15 S36 2007-347T16:15 Thu 2008-021T13:35 S37 2008-021T13:35 Mon 2008-047T11:51 S38 2008-047T11:51 Sat 2008-083T01:50 S39 2008-083T01:50 Sun 2008-110T07:18 S40 2008-110T07:18 Sat 2008-152T04:27 S41 2008-152T04:27 Sat 2008-187T00:00
DOW Sat Fri Sat Sat Sat Thu Sat Sun Sat Sat Sat Fri Tue Sat Sat Sat Sat Sat Sat Sat Sat Fri Tue Sun Fri Fri Sat Thu Fri Mon Sat Sat Sat Thu Thu Mon Sat Sun Sat Sat Sat
Length (days) 35 42 43 35 28 33 37 36 41 35 35 42 32 39 35 35 42 42 42 42 42 35 39 26 33 42 43 40 37 37 33 29 42 40 42 39 26 36 27 42 35
*Note that S1 begins before the "official" start of tour at SOI on July 1, 2004. This was done to include the Phoebe flyby in the first tour sequence.
FOIA 10-JPL-F-00451
14 of 217
2.2
INTERPLANETARY TRAJECTORY
Cassini's baseline trajectory is a VVEJGA (flybys of Venus twice, Earth and Jupiter) trajectory. This multiple gravity-assist trajectory is necessary because no existing launch vehicle/upper stage combination can place a spacecraft of Cassini's mass on a direct trajectory to Saturn. The minimum C3 (or launch energy) required for a direct trajectory in 1997 is 108 km2 /s2 . A JGA trajectory, with a single gravity-assist at Jupiter, would require a C3 of 83 km2 /s2 . The maximum C3 achievable by the Titan IV (SRMU)/Centaur for the launch mass of Cassini was 34 km2 /sec2 . This trajectory starts the spacecraft inward from the Earths orbit, toward Venus, where the first Venus gravity assist places the spacecraft on a nearly resonant Venus-to-Venus transfer. A maneuver at aphelion of this loop lowers perihelion, allowing the trajectory to intersect Venus earlier, and with a greater flight path angle. The second flyby at Venus targets the spacecraft for a very quick transfer (approximately eight weeks) to Earth. This extremely fortuitous planetary phasing eliminates the need for an additional trajectory loop in the inner solar system. The spacecraft grazes Mars orbit on the Venus 1 - Venus 2 leg, and passes through the asteroid belt on the Earth - Jupiter leg of the trajectory. No asteroid flyby is included in the baseline due to a combination of ground system resource constraints and the high V cost to target to even the closest asteroid encounter. The Jupiter flyby imparts the remaining velocity required to reach Saturn, where arrival occurs on 1 July 2004. Figures 2.3 and 2.4 show the spacecraft interplanetary trajectory. 2.3 TOUR OVERVIEW The reference tour consists of 75 orbits of Saturn with various orientations, orbital periods ranging from 7 to 118 days, and Saturn-centered periapsis radii ranging from about 2.7 to 15.6 RS (Saturn radii). Orbital inclination with respect to Saturn's equator ranges from 0 75.6 , providing opportunities for ring imaging, magnetospheric coverage, and radio (Earth), solar, and stellar occultations of Saturn, Titan, and the ring system. A total of 45 targeted Titan flybys occur during the reference tour. Of these, 41 have flyby altitudes less than 2800 km and two have flyby altitudes greater than 10,000 km. Titan flybys are used to control the spacecraft's orbit about Saturn as well as for Titan science acquisition. The tour also contains 7 close flybys of icy satellites, and 30 additional distant flybys of icy satellites within 100,000 km. Close Titan flybys are capable of making large changes in the orbiters trajectory. A single close flyby of Titan can change the orbiters Saturn-relative velocity by more than 800 m/s. However, Titan is the only satellite of Saturn which is massive enough to use for orbit control during a tour. The masses of the others are so small that even close flybys (within several hundred km) only change the orbiters trajectory slightly. Consequently, the Cassini tour consists mostly of Titan flybys. This places a restriction that each Titan flyby must place the orbiter on a trajectory leading back to Titan. The orbiter cannot be targeted to a flyby of a satellite other than Titan unless the flyby lies almost along a return path to Titan. The large number of Titan flybys does result in extensive coverage of Titan (Figure 2.7). Figure 2.5 shows a view from above Saturn's north pole of all tour orbits in a rotating coordinate system in which the Sun direction is fixed. This type of figure is often referred to as a "petal plot" due to the resemblance of the orbits to petals of a flower. The broad range of orbit orientations allows detailed survey of the magnetosphere and atmosphere of Saturn. Figure 2.6 shows a "side view", from a direction perpendicular to the plane formed by the Saturn-Sun line and Saturns north pole, in which the inclination of the orbits is apparent. The tour is described in detail in the following subsections.
2-7
15 of 217
VENUS 2 FLYBY 24 JUN 1999
DEEP-SPACE MANEUVER DEC 1998 VENUS 1 FLYBY 26 APR 1998
EARTH FLYBY 18 AUG 1999
LAUNCH 15 OCT 1997 TO JUPITER PERIHELIA 27 MAR 1998 0.67 AU 29 JUN 1999 0.72 AU
TICKS EVERY 30 DAYS
Figure 2.3 Cassini Cruise Trajectory

16 of 217
VENUS 1 SWINGBY 26 APR 1998 VENUS 2 SWINGBY 24 JUN 1999
SATURN ARRIVAL 1 JUL 2004
DEEP SPACE MANEUVER 3 DEC 1998 JUPITER FLYBY 30 DEC 2000
LAUNCH 15 OCT 1997 EARTH SWINGBY 18 AUG 1999
PERIHELIA 27 MAR 1998 0.67 AU 29 JUN 1999 0.72 AU
Figure 2.4 CASSINI CRUISE TRAJECTORY

17 of 217
Figure 2.5 Tour Petal Plot-North Pole View (+X parallel to Saturn to Sun direction, +Z Saturn N. Pole)
Figure 2.6 Tour Petal Plot - Side View 2-10

18 of 217
Figure 2.7 Titan Ground Tracks
FOIA 10-JPL-F-00451
19 of 217
Each orbit about Saturn is assigned a rev number from 1 to N incrementing at apoapsis (where one orbit ends, and the next begins). The partial orbit from SOI to the first apoapsis is orbit 0. Each satellite encounter is assigned a unique satellite encounter label consisting of a three digit rev number on which the encounter occurs followed by a two character body indicator. For the major nine satellites (Mimas, Enceladus, Tethys, Dione, Rhea, Titan, Hyperion, Iapetus, and Phoebe), the first two letters are unique and are used as the body indicator. Encounters of satellites occur either inbound (before Saturn periapsis) or outbound (after Saturn periapsis). Orbit orientation defines the location of apoapsis of the Saturn centered orbit with respect to the Sun direction which is an important consideration for observations of Saturns magnetosphere and atmosphere. Orbit orientation may be defined by an angle or a local true solar time (LTST) as depicted in Figure 2.8. The orbit orientation angle is measured clockwise in the Saturn equatorial plane from the projection of the SaturnSun line in the equatorial plane to the projection of the Saturn-apoapsis line. The local true solar time (LTST), measured in hours (or hh:mm:ss), is obtained by scaling the orbit orientation angle by (24 hours/360).
SUN NOON LTST = 12:00 = 12 PM Projection of Saturn-Sun Direction in Saturn Equatorial Plane Orbit Orientation Angle = 90 , Local True Solar Time (LTST) = 6 AM
DUSK LTST =18:00 = 6 PM
Saturn
DAWN LTST = 06:00 = 6 AM S/C Orbit Projection of SaturnApoapsis Direction in Saturn Equatorial Plane
View From Saturn North Pole MIDNIGHT / TAIL LTST = 0:00 = 12 AM
Figure 2.8 Definition of Orbit Orientation
The time available for observations of Saturns lit side decreases as the orbit rotates toward the anti-sun direction. Arrival conditions at Saturn fix the initial orientation at about 90 which is equivalent to 6 AM LTST. Due to the motion of Saturn around the Sun, the orbit orientation increases with time, at a rate of orientation of about 1/month, which over the four-year tour results in a total rotation of about 48 (3.2 hours) in the clockwise direction (as seen from above 2-12
20 of 217
Saturns north pole). Period-changing targeted flybys that rotate the line of apsides may be used to add to or subtract from this drift in orbit orientation. The petal plot of Figure 2.5 shows how targeted flybys combine with orbit drift to rotate the orbit from the initial orientation clockwise most of the way around Saturn to near the Sun line. In the coordinate system used in this figure, the direction to the Sun is fixed. A targeted flyby is one where the orbiters trajectory has been designed to pass through a specified aimpoint (latitude, longitude, and altitude) at closest approach. At Titan, the aimpoint is selected to produce a desired change in the trajectory using the satellites gravitational influence. Flybys within a few thousand km of Titan must be targeted due to the large V imparted by Titan. At targeted flybys of icy satellites, the aimpoint is generally selected to optimize the opportunities for scientific observations, since the gravitational influence of those satellites is small. However, in some cases the satellites gravitational influence is great enough to cause unacceptably large V penalties for some aimpoints, which makes it necessary to constrain the range of allowable aimpoints to avoid this penalty. If the closest approach aimpoint during a flyby is not controlled, the flyby is referred to as a non-targeted flyby. Flybys of Titan at distances greater than 11,000 km (with the notable exception of the Probe Titan flyby 003Tc) are non-targeted flybys. Flybys of satellites other than Titan at distances greater than a few thousand kilometers are usually non-targeted flybys. If the closest approach point is far from the satellite, or if the satellites mass is small, the gravitational effect of the flyby can be small enough that the aimpoint at the flyby need not be tightly controlled in order to ensure a return path to Titan. However, the gravitational influence of the flyby is not the sole criteria for distinguishing between targeted and nontargeted flybys. Operations constraints on satellite encounter frequency may force some close icy satellite flybys(usually within a few days of a Titan flyby) to be non-targeted. Opportunities to achieve non-targeted flybys of smaller satellites occur frequently during the tour. These are important for global imaging. If the transfer angle between two Titan flybys is an integer multiple of 360 (i.e., the two flybys encounter Titan at the same place in its orbit), the orbit connecting the two flybys is called a resonant orbit (Figure 2.9). The period of a Titan-resonant orbit is an integer multiple of Titan's 16 d orbital period. The plane of the transfer orbit between any two flybys is formed by the position vectors of the flybys with respect to Saturn. In this case, an infinite number of orbital planes connect the flybys; therefore, for resonant orbits, the plane of the transfer orbit can be inclined significantly to Saturns equator. The Titan flyby altitude for resonant transfers is often the minimum permitted value of 950 km since maximum inclination change per flyby is usually desired. If two successive flybys encounter Titan at a different place in its orbit, the orbit connecting the two flybys called a non-resonant orbit (Figure 2.10). Non-resonant orbits have orbital periods which are not integer multiples of Titan's period. Non-resonant transfer orbits connect inbound Titan flybys to outbound Titan flybys, or visa versa. Except for the special case of a 180 transfer, the Titan position vectors at successive encounters are not parallel (i.e., Titan is encountered at different locations in its orbit), and therefore the orbital plane formed by the position vectors of the two flybys is unique and lies close to Titans orbital plane (which lies close to Saturns equatorial plane). Nonresonant transfers therefore have near zero orbit inclination. The Titan flyby altitude for nonresonant transfers is usually much greater than the minimum flyby altitude value of 950 km since inclination is constrained to be near zero and thus the Titan gravity assist must be used solely to obtain a return trajectory to Titan. A 180 transfer (Figure 2.10) is a very special case of a Titan nonresonant transfer. In a 180 transfer, the transfer angle between two Titan flybys is an odd multiple of 180. In this case, successive Titan encounters occur first at the ascending node of Titans orbit and then the descending node, or visa versa. Only one 180 transfer occurs in the tour. Significant 2-13
21 of 217
inclination and orbit orientation change are accomplished during a sequence of flybys which includes a 180 transfer.
RESONANT TRANSFER
DEFINITION: Next Titan encounter occurs at SAME place in Titan's orbit as current encounter, i.e. s/c orbit is in resonance with Titan orbit. Used primarily for changing s/c orbit inclination or when already in an inclined orbit, changing s/c orbit period.
Titan Orbit
S/C Orbit Saturn
n complete Titan revs per m complete s/c revs where n, m = 1, 2, 3, ...
Line of Nodes
Titan at current encounter Titan at next encounter
Figure 2.9 Definition of Resonant Transfer
NONRESONANT TRANSFER
DEFINITION: Next Titan encounter occurs at a DIFFERENT place in Titan's orbit as current encounter, i.e. s/c orbit is NOT in resonance with Titan orbit. Used primarily for changing s/c orbit orientation (local solar time of s/c orbit apoapsis).
Titan at next encounter .8 revs later S/C Orbit Inbound Saturn Outbound Titan at current encounter Line of S/C Nodes = Saturn to Titan Direction Inbound Saturn Outbound Titan Orbit S/C Orbit
Titan Orbit
Titan at current encounter Sample Low Inclination Transfer
Titan at next encounter 1.1 revs later Sample Inclined 180 deg. Transfer
Transfers are from Titan outbound from Saturn to Titan inbound to Saturn or visa versa. S/C orbit plane must contain Titan at current encounter, Titan at next encounter, and Saturn. Therefore, s/c orbit inclination must be near zero unless Titan encountered at opposite sides of its orbit (i.e., 180 deg. transfer). Figure 2.10 Definition of Nonresonant and 180 Transfer
Table 2.3 shows a breakdown of the tour into segments and shows the main characteristics of each segment. Segments are delineated by Titan encounters since only at Titan encounters is the orbital geometry significantly altered. An expanded description of each segment follows. Recall that the first 3 digits of the encounter label are the rev number and that encounter labels in parentheses use the old encounter numbering scheme. Tables of satellite encounter conditions as well as an integrated rev by rev summary of key tour geometries can be found in Section 2.4.
2-14
22 of 217
Table 2.3 Tour Segment Characteristics

Figure Comments Encounte Dates rs SOI-Tc Jul 2004 2.11, SOI, PRM, target for Probe mission at Tc, reduce period & inclination (SOI-Tc) Jan 2005 2.12 Tc-14TI Jan 2005 2.13, Reduce inclination to enable nonresonant transfer to establish optimal occultation (Tc-T7) Sep 2005 2.14 geometry, raise inclination for Saturn/ring occultations and lower again to equator. Two targeted Enceladus flybys. Rotate clockwise toward anti-sun direction to establish optimal magnetotail 14TI-26TI Sep 2005 2.15 geometry. Targeted Hyperion, Dione, and Rhea flybys. (T7-T16) Jul 2006 26TI-47TI Jul 2006 2.16, Deep magnetotail passage initiating 180-deg. transfer sequence (including (T16-T33) Jun 2007 2.17 several revs for ring observations) Rotate clockwise to optimize atmospheric observation and Saturn/ring occultation 47TI-49TI Jun 2007 2.18 geometries (T33-T35) Oct 2007 49TI-End Oct 2007 2.19, Increase inclination to 75.6 (maximum value in tour). Targeted Iapetus and Enceladus flyby. Last Titan flyby is 69TI (T44). (T35-T44) Jul 2008 2.20
SOI-Tc (Figures 2.11 and 2.12) This tour segment has been significantly redesigned since the last Mission Plan release due Probe mission considerations. The remaining tour segments only contain a few tweaks to the latest T18-5 reference tour and will be described in subsequent segments. The spacecraft approaches Saturn from below the ring plane on a trajectory inclined about 17 with respect to Saturns equator [ Saturns equatorial plane is inclined 26.7 with respect to its orbit around the Sun. Saturns orbit is itself inclined 2.49 with respect to the ecliptic.]. The first Titan flyby is inbound due to Probe delivery considerations. In February 2000, it was discovered that the bit synchronizer of the Huygens receiver on the orbiter has a bandwidth that is too small to accommodate the Doppler shift of the relay signal. In order to recover the Probe mission, the redesign reduces the Doppler shift between the Probe and orbiter. To reduce the relay Doppler shift, the closest approach altitude of the orbiter at the Probe relay encounter (Tc) was raised to 60000 km which reduces the radial component of the orbiters velocity relative to the Probe and hence the Doppler shift of the relay signal Three new Titan encounters: Ta, Tb, and Tc have been designed with a distant flyby during Probe delivery on Tc. These three initial Titan encounters replace the first two Titan encounters of the T18-5 tour. The new tour therefore contains an additional Titan flyby albeit at very high altitude. Following Tc, the trajectory rejoins the T18-5 tour at the 3TI (T3) encounter. After the 3TI encounter, the encounter times differ from those in T18-5 by less than 4 hours and the geometry of the encounters and occultations remain essentially the same. The orbiters inclination is gradually reduced to enable a nonresonant transfer in the next tour segment needed to establish optimum Saturn/ring occultation geometry. Therefore, the initial series of Titan flybys must all take place at the same place in Titans orbit (i.e. they all must be resonant, inbound flybys). The initial flybys quickly reduce period, as well as inclination, to maximize the number of Titan flybys in the tour. These three inbound, period-reducing flybys rotate the line of apsides counterclockwise (Figure 2.11). This moves the apoapse toward the Sun line which provides time for observations of Saturns atmosphere and helps establish the geometry needed for near equatorial Saturn/ring occultations later in the tour. If the Probe cannot be delivered at the Tc flyby, a contingency trajectory exists that allows a second chance to deliver the Probe. This contingency retargets Tc to a lower altitude and introduces a new distant flyby, Td, for Probe delivery. However, this contingency causes Cassini to fall off of the tour and it doesn't return to the T18-5 tour until the 13TI (T6) flyby. In this case, the first two targeted Enceladus flybys will be lost as well as 3 of the 7 diametric Saturn/ring occultations. Due to the severe science impact of this contingency, every effort will be made to deliver the Probe on the nominal Tc encounter. 2-15
23 of 217
Tc-14TI (Tc-T7) (Figures 2.13 and 2.14) The 3TI (T3) flyby initiates a nonresonant inbound to outbound transfer that orients the line of nodes nearly normal to the Saturn-Earth line. This orientation minimizes the inclination required to achieve an occultation of Saturn and results in Saturn/ring occultations which are characterized by ingress and egress close to Saturns equatorial plane (i.e., near-equatorial). The use of outbound flybys for the early tour dawn orbit orientation minimizes the Saturnspacecraft distance during these occultations which improves science return since the footprint" projected on the rings is minimized, improving the spatial resolution of the "scattered" radio signal observations. This is an important influence on the design of the tour. A targeted Enceladus (4EN, (E1)) flyby is obtained during the 3TI-5TI (T3-T4) nonresonant tranfer. Note that targeted flybys of the icy satellites such as 4EN are usually obtained on orbits which are also used to establish desired Saturn-relative geometries. The resonant outbound flybys 5TI (T4) and 6TI (T5) increase inclination to ~22 to set up the Saturn/ring equatorial occultations. During the 6TI (T5) to 13TI (T6) segment, seven nearequatorial occultations of Earth and Sun by Saturn and its rings (one on each 18.2 d period orbit) occur. During these seven orbits, the orbiter crosses Saturns equator near Enceladus orbit; on the fourth orbit, Enceladus and the spacecraft both arrive at nearly the same point in Enceladus orbit at the same time, and the second targeted flyby of Enceladus (11EN, (E2)) occurs. Enceladus gravity is too weak to displace inclination significantly from the value required to achieve occultations. The 13TI (T6) flyby decreases inclination once again to near Saturn's equator to enable a nonresonant transfer in order to begin the next tour segment. Unlike the last officially released tour, the 13TI (T6) flyby altitude was raised from 950 to ~4000 km in order to avoid a G ring crossing but the 14TI (T7) altitude was lowered from ~4000 to 950 km. These two Titan flybys therefore do not change the distribution of Titan flyby altitudes. 14TI-26TI (T7-T16) (Figure 2.15) The 14TI-17TI (T7-T8) nonresonant transfer initiates a series of alternating outbound/periodreducing and inbound/period-increasing flybys lasting about 10 months. These flybys are used to rotate the orbit apoapsis clockwise toward the magnetotail to establish the geometry required for a deep magnetotail passage. The period typically alternates between 23 d (outbound) and 39 d (inbound) with .8 to 1.1 revs between flybys since this sequence results in the most rapid change in orbit orientation. The only exceptions to this pattern were orbits used to obtain targeted icy satellites during these nonresonant transfers. Following the 14TI (T7) flyby, a 19 d period, 2.8 rev nonresonant transfer is used in order to achieve the first targeted flybys of Hyperion (15HY, (H1)) and Dione (16DI, (D1)) along the way. Compared to the last officially released tour, the Dione flyby aimpoint has been lowered in altitude (to 500 km) and changed in B-plane angle per PSG request. Similarly, following the 17TI (T8) flyby, a 28 d, 2.1 rev nonresonant transfer is utilized to obtain the first targeted Rhea (18RH, R1) flyby. 26TI-47TI (T16-T33) (Figures 2.16, 2.17) The 26TI (T16) flyby places apoapsis near the anti-Sun line at an inclination of ~15 to achieve passage through the current sheet in the magnetotail region. Apoapsis distance is about 49 R S, exceeding the 40 RS MAPS requirement associated with magnetotail passage. At distances this far from Saturn, the current sheet is assumed to be swept away from Saturns equatorial plane by the solar wind. This flyby also initiates the 180 transfer sequence. A series of 17 Titan flybys comprise the 180 transfer sequence. A series of 9 resonant transfers, usually with period of 16 d, increases inclination and decreases orbit eccentricity to a point at which both the ascending and descending nodes of the spacecraft orbit are at Titans 2-16
24 of 217
orbital radius. At an inclination of ~59, a nonresonant 180 transfer is then performed (the orbit shown in bold in Figures 2.16 and 2.17), i.e., the true anomaly of Titan in its orbit at which it is encountered by the spacecraft on successive flybys differs by 180 (actually 540). A series of 8 16 day period orbits then decreases inclination back to near zero and increases eccentricity back to its original value. Orbit orientation is changed by ~135 to ~8 PM LTST over the 11 month sequence duration. Most Titan flyby altitudes are at the minimum permitted value of 950 km in order to maximize the inclination and eccentricity change at each flyby. Such low altitude Titan flybys are preferred for many science observations. The 31TI (T20) flyby reduces period to 12 days resulting in 4 revs over an interval of 48 d between Titan flybys in order to provide additional ORS observations of the rings at a time of favorable observational geometry. This 48-day interval also serves to reduce operational stress on the ground system. 47TI-49TI (T33-T35) (Figure 2.18) The 47TI (T33) and 48TI (T34) nonresonant transfers rotate the orbit petal further clockwise (toward noon) to enable Saturn atmospheric observations at both great distance (> 40 Rs) and low phase angle. This tour segment provides much of the long integration time daytime atmospheric observation opportunities. The nonresonant transfers also move the line of nodes closer to the Sun line in order to establish the geometry needed for near polar Saturn/ring occultations in the next tour segment. 49TI-End Baseline Mission (post 69TI) on Rev 74 (T35-post T44) (Figures 2.19 and 2.20) This segment is comprised solely of resonant transfers which gradually raise inclination to the maximum value attained in the tour. The first targeted Iapetus encounter (49IA (I1)) is obtained on the 49TI-50TI (T35-T36) resonant transfer at an inclination of ~6. Note that the ascending node on which this targeted Iapetus encounter is obtained differs ~180 from the ascending node desired for the maximum inclination sequence. The desired ascending node for the maximum inclination segment places periapsis below the ring plane such that the spacecraft can view the illuminated side of the rings at Saturn periapsis (note Solar declination is negative during this time period). The third targeted Enceladus (61EN, (E3)) encounter is obtained on the 59TI-62TI (T41-T42) transfer. Note that this Enceladus flyby is occulted from the Sun at closest approach. Following the targeted 49IA (I1) Iapetus flyby, starting at 50TI (T36), a series of 10 outbound Titan resonant transfers are used increase inclination as much as possible for ring observations and in-situ fields and particles measurements. These resonant transfers continue until the end of the baseline tour on July 1, 2008 (rev 74) four years after insertion into orbit about Saturn. The LTST of these orbits is near noon to enable near polar Saturn/ring occultations at close distances. The maximum inclination possible is dictated primarily by the Titan-relative V-infinity (fixed), orbital period (free), and the number of Titan flybys (constrained by time left in tour) devoted to increasing inclination. The closest approach altitudes during this segment are kept at the minimum allowed value of 950 km to maximize inclination change at each flyby. The orbital period must be gradually reduced in order to further increase inclination which decreases the descending node crossing distance to the point where ring hazard avoidance becomes a limiting constraint. The orbital characteristics after the last Titan flyby in the tour, 69TI (T44), are a period of 7.1 d, inclination of 75.6, and descending node distance of 2.7 Rs. Five periapses are completed at this maximum inclination before the end of the baseline tour. The aimpoint at the last Titan flyby is chosen to target the orbiter to a Titan flyby on 7/31/08 (64 days and 9 revs after the 69TI (T44) flyby), providing the opportunity to proceed with more flybys during an extended mission, if resources allow. Nothing in the design of the tour precludes an extended mission. 2-17
25 of 217
26 of 217
Figure 2.12 Tour Segment SOI-Tc Side View
Figure 2.13 Tour Segment Tc-14TI (Tc-T7) (+X parallel to Saturn to Sun direction, +Z Saturn N. Pole) 2-19
27 of 217
Figure 2.14 Tour Segment Tc-14TI (Tc-T7) Side View
Figure 2.15 Tour Segment 14TI-26TI (T7-T16) [~Zero Inclination] (+X parallel to Saturn to Sun direction, +Z Saturn N. Pole) 2-20
28 of 217
SUN i=2 , period=16 d Titan location last 8 outbound flybys 180 Transfer Orbit i=59 Dusk Titan Orbit Orbit Orientation Change
Titan location first 9 inbound flybys i=25 , period=16 d i=15 , period= 24 d
Midnight
Figure 2.16 Tour Segment 26TI-47TI (T16-T33) (+X parallel to Saturn to Sun direction, +Z Saturn N. Pole)
180 Transfer Orb i=59

Figure 2.17 Tour Segment 26TI-47TI (T16-T33) Side View 2-21
29 of 217
Figure 2.18 Tour Segment 47TI-49TI (T33-T35) [~Zero Inclination] (+X parallel to Saturn to Sun direction, +Z Saturn N. Pole)
Figure 2.19 Tour Segment 49TI-End Baseline Mission (post 69TI) on Rev 74 (T35-post T44) (+X parallel to Saturn to Sun direction, +Z Saturn N. Pole) 2-22
30 of 217
Figure 2.20 Tour Segment 49TI-End Baseline Mission (post 69TI) on Rev 74 (T35-post T44) Side View 2.4 REFERENCE TABLES The following tables provide reference data for the Cassini mission. Encounters during the nominal tour and all events during the tour are given. Finally, a utility table translates between calendar date, weekday and day of year for planning purposes.
2-23
31 of 217
CASSINI TOUR ENCOUNTER SUMMARY Old Event Epoch (SCET) Rev Name Name 0PH (t) P1 Phoebe 2004-Jun-11 19:33 0 0MI (nt) Mimas 2004-Jul-01 00:30 0 0TI (nt) Titan 2004-Jul-02 09:30 0 aTI (t) N/A Titan 2004-Oct-26 15:30 a bTI (t) N/A Titan 2004-Dec-13 11:37 b bDI (nt) Dione 2004-Dec-15 02:11 b cIA (nt) Iapetus 2005-Jan-01 01:28 c cTI (t) N/A Titan 2005-Jan-14 11:04 c 3TI (t) T3 Titan 2005-Feb-15 06:54 3 3EN (nt) Enceladus 2005-Feb-17 03:24 3 4EN (t) E1 Enceladus 2005-Mar-09 09:06 4 4TE (nt) Tethys 2005-Mar-09 11:42 4 5EN (nt) Enceladus 2005-Mar-29 20:20 5 5TI (t) T4 Titan 2005-Mar-31 19:55 5 6MI (nt) Mimas 2005-Apr-15 01:20 6 6TI (t) T5 Titan 2005-Apr-16 19:05 6 7TE (nt) Tethys 2005-May-02 21:04 7 7TI (nt) Titan 2005-May-04 05:10 7 8EN (nt) Enceladus 2005-May-21 07:19 8 9TI (nt) Titan 2005-Jun-06 18:50 9 Titan 2005-Jun-22 12:27 10 10TI (nt) 11 11EN (t) E2 Enceladus 2005-Jul-14 19:57 Mimas 2005-Aug-02 03:52 12 12MI (nt) Titan 2005-Aug-06 12:33 12 12TI (nt) 2005-Aug-22 08:39 13 13TI (t) T6 Titan 2005-Sep-07 07:50 14 14TI (t) T7 Titan Tethys 2005-Sep-24 01:29 15 15TE (nt) Titan 2005-Sep-24 22:01 15 15TI (nt) 2005-Sep-26 01:41 15 15HY (t) H1 Hyperion Titan 2005-Oct-10 22:20 16 16TI (nt) 2005-Oct-11 17:58 16 16DI (t) D1 Dione Enceladus 2005-Oct-12 03:29 16 16EN (nt) 2005-Oct-28 03:58 17 17TI (t) T8 Titan 2005-Nov-26 22:35 18 18RH (t) R1 Rhea Enceladus 2005-Dec-24 20:23 19 19EN (nt) 2005-Dec-26 18:54 19 19TI (t) T9 Titan 2006-Jan-15 11:36 20 20TI (t) T10 Titan 2006-Feb-27 08:20 21 21TI (t) T11 Titan 2006-Mar-18 23:58 22 22TI (t) T12 Titan Rhea 2006-Mar-21 07:01 22 22RH (nt) 2006-Apr-30 20:53 23 23TI (t) T13 Titan 2006-May-20 12:13 24 24TI (t) T14 Titan 2006-Jul-02 09:12 25 25TI (t) T15 Titan 2006-Jul-22 00:25 26 26TI (t) T16 Titan Titan 2006-Aug-18 17:48 27 27TI (nt) 2006-Sep-07 20:12 28 28TI (t) T17 Titan Enceladus 2006-Sep-09 20:00 28 28EN (nt) 2006-Sep-23 18:52 29 29TI (t) T18 Titan 2006-Oct-09 17:23 30 30TI (t) T19 Titan 2006-Oct-25 15:51 31 31TI (t) T20 Titan Enceladus 2006-Nov-09 01:48 32 32EN (nt) Dione 2006-Nov-21 02:32 33 33DI (nt) Titan 2006-Nov-25 13:57 33 33TI (nt) 2006-Dec-12 11:35 35 35TI (t) T21 Titan 2006-Dec-28 10:00 36 36TI (t) T22 Titan 2007-Jan-13 08:34 37 37TI (t) T23 Titan 2007-Jan-29 07:12 38 38TI (t) T24 Titan
DOY 163 183 184 300 348 350 001 014 046 048 068 068 088 090 105 106 122 124 141 157 173 195 214 218 234 250 267 267 269 283 284 285 301 330 358 360 015 058 077 080 120 140 183 203 230 250 252 266 282 298 313 325 329 346 362 013 029
DOW Altitude km Fri 1,997 Thu 76,424 Fri 338,958 Tue 1,200 Mon 2,358 Wed 81,592 Sat 64,907 Fri 60,000 Tue 950 Thu 1,179 Wed 499 Wed 82,975 Tue 63,785 Thu 2,523 Fri 77,233 Sat 950 Mon 64,990 Wed 860,004 Sat 92,997 Mon 425,973 Wed 920,423 Thu 1,000 Tue 45,112 Sat 841,452 Mon 4,015 Wed 950 Sat 33,295 Sat 910,272 Mon 990 Mon 777,198 Tue 500 Wed 42,635 Fri 1,446 Sat 500 Sat 97,169 Mon 10,429 Sun 2,042 Mon 1,812 Sat 1,947 Tue 85,935 Sun 1,853 Sat 1,879 Sun 1,911 Sat 950 Fri 339,190 Thu 950 Sat 39,842 Sat 950 Mon 950 Wed 950 Thu 94,410 Tue 72,293 Sat 930,525 Tue 950 Thu 1,500 Sat 950 Mon 2,776
Inbound/ outbound inbound inbound outbound inbound inbound inbound inbound inbound inbound outbound inbound outbound inbound outbound outbound outbound inbound outbound outbound inbound inbound inbound inbound outbound outbound outbound outbound outbound outbound inbound inbound outbound inbound inbound inbound outbound inbound outbound inbound outbound outbound inbound outbound inbound outbound inbound outbound inbound inbound inbound outbound outbound outbound inbound inbound inbound inbound
Speed Phase To Next km/s deg Targ 6.4 25 22.3 80 8.3 67 6.1 91 48 6.0 98 32 5.3 93 2.1 106 5.4 93 32 6.0 102 22 6.6 98 6.6 43 22 6.9 64 10.1 134 5.9 65 16 13.6 94 6.1 127 89 10.0 118 10.2 153 8.1 81 5.8 82 3.7 65 8.1 43 39 6.5 83 3.8 62 5.8 42 16 6.1 84 19 7.7 76 10.7 148 5.6 45 16 9.7 65 9.0 66 16 6.6 75 5.9 105 30 7.3 87 30 6.9 133 5.6 67 20 5.8 121 43 5.9 93 20 5.8 148 43 5.3 136 5.8 121 20 5.8 163 43 5.8 148 20 6.0 105 48 4.8 121 6.0 45 16 10.3 116 6.0 90 16 6.0 81 16 6.0 25 48 14.1 27 12.3 144 4.5 114 6.0 124 16 5.9 62 16 6.0 53 16 5.8 73 24
This list only includes flybys of Titan < 1,000,000 km and icy satellites < 100,000 km
FOIA 10-JPL-F-00451
32 of 217
CASSINI TOUR ENCOUNTER SUMMARY Old Event Epoch (SCET) Rev Name Name 2007-Feb-22 03:10 39 39TI (t) T25 Titan 2007-Mar-10 01:47 40 40TI (t) T26 Titan 2007-Mar-26 00:21 41 41TI (t) T27 Titan 2007-Apr-10 22:57 42 42TI (t) T28 Titan 2007-Apr-26 21:32 43 43TI (t) T29 Titan 2007-May-12 20:08 44 44TI (t) T30 Titan Tethys 2007-May-26 20:57 45 45TE (nt) 2007-May-28 18:51 45 45TI (t) T31 Titan 2007-Jun-13 17:46 46 46TI (t) T32 Titan Tethys 2007-Jun-27 19:53 47 47TE (nt) Mimas 2007-Jun-27 22:56 47 47MI (nt) Enceladus 2007-Jun-28 01:15 47 47EN (nt) 2007-Jun-29 17:05 47 47TI (t) T33 Titan 2007-Jul-19 00:39 48 48TI (t) T34 Titan Tethys 2007-Aug-29 11:21 49 49TE (nt) Rhea 2007-Aug-30 01:26 49 49RH (nt) 2007-Aug-31 06:34 49 49TI (t) T35 Titan 2007-Sep-10 12:33 49 49IA (t) I1 Iapetus Dione 2007-Sep-30 06:27 50 50DI (nt) Enceladus 2007-Sep-30 10:53 50 50EN (nt) 2007-Oct-02 04:48 50 50TI (t) T36 Titan Titan 2007-Oct-22 00:47 51 51TI (nt) Rhea 2007-Nov-16 19:52 52 52RH (nt) 2007-Nov-19 00:52 52 52TI (t) T37 Titan Mimas 2007-Dec-03 05:28 53 53MI (nt) 2007-Dec-05 00:06 53 53TI (t) T38 Titan 2007-Dec-20 22:56 54 54TI (t) T39 Titan 2008-Jan-05 21:26 55 55TI (t) T40 Titan Titan 2008-Jan-22 21:06 57 57TI (nt) 2008-Feb-22 17:39 59 59TI (t) T41 Titan Titan 2008-Mar-10 19:15 61 61TI (nt) 61 61EN (t) E3 Enceladus 2008-Mar-12 19:05 2008-Mar-25 14:35 62 62TI (t) T42 Titan Mimas 2008-Apr-11 09:38 64 64MI (nt) Titan 2008-Apr-26 18:22 66 66TI (nt) 2008-May-12 10:09 67 67TI (t) T43 Titan 2008-May-28 08:33 69 69TI (t) T44 Titan Titan 2008-Jun-13 04:17 72 72TI (nt) Enceladus 2008-Jun-30 08:07 74 74EN (nt)
DOY 053 069 085 100 116 132 146 148 164 178 178 179 180 200 241 242 243 253 273 273 275 295 320 323 337 339 354 005 022 053 070 072 085 102 117 133 149 165 182
DOW Altitude km Thu 953 Sat 956 Mon 953 Tue 951 Thu 951 Sat 950 Sat 97,131 Mon 2,425 Wed 950 Wed 16,166 Wed 89,730 Thu 90,769 Fri 1,942 Thu 1,302 Wed 48,324 Thu 5,098 Fri 3,227 Mon 1,000 Sun 56,523 Sun 88,174 Tue 950 Mon 455,697 Fri 78,360 Mon 950 Mon 79,272 Wed 1,300 Thu 953 Sat 949 Tue 860,776 Fri 959 Mon 922,539 Wed 995 Tue 950 Fri 95,428 Sat 780,589 Mon 950 Wed 1,316 Fri 372,240 Mon 99,092
Inbound/ outbound outbound outbound outbound outbound outbound outbound inbound outbound outbound inbound inbound outbound outbound inbound inbound outbound outbound outbound inbound inbound outbound inbound inbound outbound inbound outbound outbound outbound inbound outbound inbound inbound outbound inbound inbound outbound outbound inbound inbound
Speed Phase To Next km/s deg Targ 6.3 161 16 6.3 149 16 6.3 144 16 6.3 137 16 6.3 130 16 6.3 121 16 11.7 75 6.1 114 16 6.3 107 16 10.1 90 16.2 110 9.4 55 6.2 96 19 6.2 34 43 4.7 104 6.7 46 6.1 87 10 2.4 65 22 5.6 47 6.1 99 6.3 67 48 4.1 29 9.1 148 6.3 51 16 14.8 138 6.3 70 16 6.3 61 16 6.3 37 48 4.5 70 6.4 30 19 6.3 123 14.6 56 13 6.4 21 48 16.9 137 5.5 94 6.4 35 16 6.3 23 5.9 89 21.6 66
This list only includes flybys of Titan < 1,000,000 km and icy satellites < 100,000 km
FOIA 10-JPL-F-00451
33 of 217
CASSINI Seq Rev S1 0 S1 0 S1 0 S1 0 S2 0 S2 0 S2 0 S2 0 S2 0 S2 0 S2 0 S2 0 S2 0 S2 0 S2 0 S2 0 S2 0 S2 0 S2 0 S2 0 S2 0 S2 0 S2 0 S2 0 S2 0 S3 0 S3 0 S3 S3 S4 S5 S5 S5 S5 S5 S5 S5 S6 S6 S6 S6 S6 S6 S6 S6 S6 S7 S7 S7 S7 S7 S7 S7 S7 S7 S7 S7 S7 S7 S8 S8 S8 S8 S8 S8 S8 S8 S8 S8 S8 S8 a a a a a a a a a a a b b b b b b b b b b b b b c c c c c c c c c c 3 3 3 3 3 3 3 3 3 3
TOUR EVENT SUMMARY All times are in SCET. For events with nonzero duration, epoch given is start. Name Event Epoch (SCET) Date DOW Comment S1 Begins 2004-136T00:00 May15 Sat Duration = 35 days TCM-20 2004-148T23:45 May27 Thu Phoebe targeting 0PH (t) Phoebe 2004-163T19:33 Jun11 Fri Was P1; inbound 1,997 km, v= 6.4 km/s, Phase=25 deg TCM-21 2004-168T22:40 Jun16 Wed SOI targeting S2 Begins 2004-171T01:38 Jun19 Sat Duration = 42 days TCM-22 2004-173T22:15 Jun21 Mon Backup SOI targeting (contingency) 0MI (nt) Mimas 2004-183T00:30 Jul01 Thu inbound 76,424 km, v= 22.3 km/s, Phase=80 deg Ring CRX Ascending 2004-183T00:47 Jul01 Thu r=2.6 Rs SOI Start 2004-183T01:12 Jul01 Thu SOI burn start, V= 632 m/s, ~102 min. duration Earth OCC Ring 2004-183T01:35 Jul01 Thu Duration = 166 min. Sun OCC Ring 2004-183T01:36 Jul01 Thu Duration = 166 min. Periapse 2004-183T02:38 Jul01 Thu r=1.3 Rs, Phase=94 deg SOI End 2004-183T02:54 Jul01 Thu SOI burn end Earth OCC Saturn 2004-183T03:33 Jul01 Thu Duration = 36 min. Sun OCC Saturn 2004-183T03:36 Jul01 Thu Duration = 32 min. Ring CRX Descending 2004-183T04:34 Jul01 Thu r=2.6 Rs 0TI (nt) Titan 2004-184T09:30 Jul02 Fri Was T0; outbound 338,958 km, v= 8.3 km/s, Phase=67 deg OTM-001 SOI c/u 2004-185T21:40 Jul03 Sat SOI cleanup SEP=3 deg Conjunction 2004-187T04:20 Jul05 Mon SEP Decreasing, successful commanding not req. SEP=2 deg Conjunction 2004-188T10:12 Jul06 Tue SEP Decreasing, plan for RTE-1896, no SSR playback SEP=1 deg Conjunction 2004-189T16:27 Jul07 Wed SEP Decreasing, schedule no DSN passes SEP=1 deg Conjunction 2004-192T01:04 Jul10 Sat SEP Increasing, plan for RTE-1896, no SSR playback SEP=2 deg Conjunction 2004-193T07:11 Jul11 Sun SEP Increasing, successful commanding not req. SEP=3 deg Conjunction 2004-194T12:51 Jul12 Mon SEP Increasing OTM-001A SOI c/u 2004-199T21:00 Jul17 Sat SOI cleanup S3 Begins 2004-212T23:05 Jul30 Fri Duration = 43 days OTM-002 PRM 2004-236T17:00 Aug23 Mon Periapsis raise V= 392 m/s Apoapse OTM-003 S4 Begins S5 Begins OTM-004 aTI (t) Ring CRX Periapse Ring CRX OTM-005 S6 Begins 2004-240T12:38 2004-251T18:00 2004-255T19:10 2004-290T18:40 2004-297T07:30 2004-300T15:30 2004-300T16:53 2004-302T10:19 2004-302T19:58 2004-303T13:30 2004-318T16:59 2004-326T08:41 2004-326T05:00 2004-345T04:00 2004-348T11:37 2004-348T13:29 2004-350T02:11 2004-350T05:58 2004-350T11:14 2004-351T15:03 2004-353T03:45 2004-357T03:30 2004-359T09:00 2004-364T03:00 2004-366T07:17 2005-001T01:28 2005-014T09:00 2005-014T11:04 2005-014T14:55 2005-016T06:27 2005-016T09:30 2005-016T11:57 2005-022T10:38 2005-028T15:13 2005-032T03:25 2005-043T07:15 2005-046T06:54 2005-046T07:01 2005-046T07:05 2005-047T23:38 2005-048T00:54 2005-048T03:24 2005-048T07:16 2005-051T13:40 Aug27 Sep07 Sep11 Oct16 Oct23 Oct26 Oct26 Oct28 Oct28 Oct29 Nov13 Nov21 Nov21 Dec10 Dec13 Dec13 Dec15 Dec15 Dec15 Dec16 Dec18 Dec22 Dec24 Dec29 Dec31 Jan01 Jan14 Jan14 Jan14 Jan16 Jan16 Jan16 Jan22 Jan28 Feb01 Feb12 Feb15 Feb15 Feb15 Feb16 Feb17 Feb17 Feb17 Feb20 Fri Tue Sat Sat Sat Tue Tue Thu Thu Fri Sat Sun Sun Fri Mon Mon Wed Wed Wed Thu Sat Wed Fri Wed Fri Sat Fri Fri Fri Sun Sun Sun Sat Fri Tue Sat Tue Tue Tue Wed Thu Thu Thu Sun P=123.8 d, i=17.6, r=150.5 Rs, Phase=87 deg, LTST=5:47 Periapsis raise clean up Duration = 35 days Duration = 28 days Was T N/A; inbound 1,200 km, v= 6.1 km/s, Phase=91 deg r=19.5 Rs r=6.2 Rs, Phase=104 deg r=8.1 Rs Duration = 33 days P=47.9 d, i=13.8, r=78.1 Rs, Phase=77 deg, LTST=5:09
PRM c/u
ATI-3 Titan Ascending Descending ATI+3
Apoapse OTM-006 APO OTM-007 BTI-3 bTI (t) Titan Ring CRX Ascending bDI (nt) Dione Periapse Ring CRX Descending S7 Begins OTM-008 PTM OTM-009 PTM c/u Probe Release OTM-010 ODM Apoapse cIA (nt) Iapetus Probe Entry cTI (t) Titan Ring CRX Ascending Periapse OTM-011 CTI+2 Ring CRX Descending S8 Begins OTM-012 ~APO Apoapse OTM-013 3TI (t) Earth OCC Sun OCC Ring CRX Periapse 3EN (nt) OTM-014 Ring CRX
Was T N/A; inbound 2,358 km, v= 6.0 km/s, Phase=98 deg r=19.3 Rs inbound 81,592 km, v= 5.3 km/s, Phase=93 deg r=4.8 Rs, Phase=109 deg r=5.8 Rs Duration = 37 days Probe targeting Probe targeting cleanup At entry interface - 21 d Orbit deflection V= 26 m/s P=31.9 d, i=8.6, r=59.5 Rs, Phase=71 deg, LTST=4:45 inbound 64,907 km, v= 2.1 km/s, Phase=106 deg Entry interface alt=1270 km, Tc-2.1 h Was T N/A; inbound 60,000 km, v= 5.4 km/s, Phase=93 deg r=19.1 Rs r=4.9 Rs, Phase=107 deg r=5.9 Rs Duration = 36 days
P=31.8 d, i=8.5, r=59.2 Rs, Phase=73 deg, LTST=4:53 Was T3; inbound 950 km, v= 6.0 km/s, Phase=102 deg Duration = 25 min Duration = 16 min r=3.6 Rs r=3.5 Rs, Phase=115 deg outbound 1,179 km, v= 6.6 km/s, Phase=98 deg r=30.4 Rs
3TI-3 Titan Titan Titan Ascending Enceladus 3TI+3 Descending
This list only includes flybys of Titan < 1,000,000 km and icy satellites < 100,000 km. Saturn occultation times computed using 100 mbar pressure surface (Appendix B). 1 Rs = 60330 km.
FOIA 10-JPL-F-00451
34 of 217
CASSINI TOUR EVENT SUMMARY Name Event Seq Rev S9 Begins S9 3 S9 S9 S9 S9 S9 S9 S9 S9 S9 S9 S9 S9 S9 S9 S9 S9 S9 S9 S9 S10 S10 S10 S10 S10 S10 S10 S10 S10 S10 S10 S10 S10 S10 S10 S10 S10 S10 S10 S10 S10 S10 S10 S10 S10 S10 S10 S11 S11 S11 S11 S11 S11 S11 S11 S11 S11 S11 S11 S11 S11 S11 S11 S11 S11 S11 S11 S11 S11 4 4 4 4 4 4 4 4 4 5 5 5 5 5 5 5 5 5 6 6 6 6 6 6 6 6 6 6 6 6 6 6 7 7 7 7 7 7 7 7 7 7 7 7 7 8 8 8 8 8 8 8 8 8 8 8 8 9 9 9 9 9 9 9 9 9 9 9 Apoapse OTM-015 OTM-016 4EN (t) Ring CRX Periapse 4TE (nt) OTM-017 Ring CRX Apoapse OTM-018 OTM-019 5EN (nt) Ring CRX Periapse 5TI (t) Ring CRX OTM-020 Apoapse S10 Begins OTM-021 OTM-022 Ring CRX Periapse Earth OCC Sun OCC 6MI (nt) Earth OCC 6TI (t) Sun OCC Ring CRX OTM-023 Apoapse OTM-024 7TE (nt) Ring CRX Periapse Earth OCC Sun OCC Earth OCC Sun OCC Earth OCC Sun OCC 7TI (nt) Ring CRX Apoapse S11 Begins Ring CRX Periapse Earth OCC 8EN (nt) Sun OCC Earth OCC Sun OCC Earth OCC Sun OCC Ring CRX Apoapse 9TI (nt) Ring CRX Periapse Earth OCC Sun OCC Earth OCC Sun OCC Earth OCC Sun OCC Ring CRX
All times are in SCET. For events with nonzero duration, epoch given is start. Epoch (SCET) Date DOW Comment 2005-058T00:36 Feb27 Sun Duration = 41 days 2005-058T06:20 2005-061T04:50 2005-065T04:35 2005-068T09:06 2005-068T10:18 2005-068T11:38 2005-068T11:42 2005-071T03:20 2005-071T22:13 2005-078T17:25 2005-078T18:19 2005-087T02:00 2005-088T20:20 2005-088T22:22 2005-088T23:26 2005-090T19:55 2005-090T21:58 2005-094T02:22 2005-096T23:23 2005-099T05:15 2005-100T02:00 2005-104T02:40 2005-104T22:11 2005-104T23:10 2005-104T23:47 2005-104T23:56 2005-105T01:20 2005-106T19:05 2005-106T19:05 2005-106T19:06 2005-106T19:51 2005-110T00:00 2005-113T23:10 2005-118T23:45 2005-122T21:04 2005-122T23:02 2005-123T01:08 2005-123T02:23 2005-123T02:51 2005-123T04:07 2005-123T04:38 2005-123T06:33 2005-123T07:18 2005-124T05:10 2005-125T01:50 2005-132T03:22 2005-134T02:50 2005-141T03:29 2005-141T05:37 2005-141T06:57 2005-141T07:19 2005-141T07:23 2005-141T08:42 2005-141T09:09 2005-141T11:12 2005-141T11:51 2005-143T05:37 2005-150T08:00 2005-157T18:50 2005-159T08:09 2005-159T10:20 2005-159T11:48 2005-159T12:09 2005-159T13:34 2005-159T13:56 2005-159T16:08 2005-159T16:38 2005-161T09:09 Feb27 Mar02 Mar06 Mar09 Mar09 Mar09 Mar09 Mar12 Mar12 Mar19 Mar19 Mar28 Mar29 Mar29 Mar29 Mar31 Mar31 Apr04 Apr06 Apr09 Apr10 Apr14 Apr14 Apr14 Apr14 Apr14 Apr15 Apr16 Apr16 Apr16 Apr16 Apr20 Apr23 Apr28 May02 May02 May03 May03 May03 May03 May03 May03 May03 May04 May05 May12 May14 May21 May21 May21 May21 May21 May21 May21 May21 May21 May23 May30 Jun06 Jun08 Jun08 Jun08 Jun08 Jun08 Jun08 Jun08 Jun08 Jun10 Sun Wed Sun Wed Wed Wed Wed Sat Sat Sat Sat Mon Tue Tue Tue Thu Thu Mon Wed Sat Sun Thu Thu Thu Thu Thu Fri Sat Sat Sat Sat Wed Sat Thu Mon Mon Tue Tue Tue Tue Tue Tue Tue Wed Thu Thu Sat Sat Sat Sat Sat Sat Sat Sat Sat Sat Mon Mon Mon Wed Wed Wed Wed Wed Wed Wed Wed Fri P=20.5 d, i=.3, r=44.3 Rs, Phase=65 deg, LTST=4:20
~APO 4EN-3 Enceladus Ascending Tethys 4EN+3 Descending
was E1; inbound 499 km, v= 6.6 km/s, Phase=43 deg r=3.6 Rs r=3.5 Rs, Phase=115 deg outbound 82,975 km, v= 6.9 km/s, Phase=64 deg r=30.0 Rs P=20.5 d, i=.4, r=44.4 Rs, Phase=66 deg, LTST=4:22
~APO 5TI-3 Enceladus Ascending Titan Descending 5TI+3
inbound 63,785 km, v= 10.1 km/s, Phase=134 deg r=3.6 Rs r=3.5 Rs, Phase=114 deg Was T4; outbound 2,523 km, v= 5.9 km/s, Phase=65 deg r=21.3 Rs
P=16.0 d, i=7.0, r=38.0 Rs, Phase=72 deg, LTST=4:50 Duration = 35 days
~APO 6TI-3 Ascending Ring Ring Mimas Titan Titan Titan Descending 6TI+3
r=2.7 Rs r=2.6 Rs, Phase=108 deg Duration = 101 min. Duration = 105 min. outbound 77,233 km, v= 13.6 km/s, Phase=94 deg Duration = 7 min Was T5; outbound 950 km, v= 6.1 km/s, Phase=127 deg Duration = 8 min r=20.9 Rs
P=18.2 d, i=21.7, r=40.6 Rs, Phase=65 deg, LTST=4:19 inbound 64,990 km, v= 10.0 km/s, Phase=118 deg r=3.9 Rs r=3.6 Rs, Phase=115 deg Duration = 97 min. Duration = 99 min. Duration = 144 min. Duration = 154 min. Duration = 93 min. Duration = 94 min. outbound 860,004 km, v= 10.2 km/s, Phase=153 deg r=21.5 Rs P=18.2 d, i=21.9, r=40.6 Rs, Phase=66 deg, LTST=4:22 Duration = 35 days r=3.9 Rs r=3.6 Rs, Phase=114 deg Duration = 97 min. outbound 92,997 km, v= 8.1 km/s, Phase=81 deg Duration = 99 min. Duration = 146 min. Duration = 154 min. Duration = 93 min. Duration = 95 min. r=21.3 Rs P=18.2 d, i=21.9, r=40.6 Rs, Phase=66 deg, LTST=4:25 inbound 425,973 km, v= 5.8 km/s, Phase=82 deg r=3.9 Rs r=3.6 Rs, Phase=114 deg Duration = 98 min. Duration = 99 min. Duration = 149 min. Duration = 155 min. Duration = 93 min. Duration = 95 min. r=21.0 Rs
~APO Tethys Ascending Ring Ring Saturn Saturn Ring Ring Titan Descending
Ascending Ring Enceladus Ring Saturn Saturn Ring Ring Descending
Titan Ascending Ring Ring Saturn Saturn Ring Ring Descending
FOIA 10-JPL-F-00451
35 of 217
CASSINI TOUR EVENT SUMMARY Name Event Seq Rev S11 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S12 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S13 S14 S14 S14 S14 S14 S14 S14 S14 S14 S14 10 10 10 10 10 10 10 10 10 10 10 10 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 13 13 13 13 13 13 13 13 13 13 13 13 13 14 14 14 14 14 14 14 14 14 14 14 14 Apoapse S12 Begins 10TI (nt) Ring CRX Periapse Earth OCC Sun OCC Earth OCC Sun OCC Earth OCC Sun OCC Ring CRX Apoapse OTM-025 Ring CRX 11EN (t) Periapse Earth OCC Sun OCC Earth OCC Sun OCC Earth OCC Sun OCC Ring CRX SEP=3 deg SEP=2 deg SEP=1 deg Apoapse SEP=1 deg SEP=2 deg SEP=3 deg S13 Begins Ring CRX 12MI (nt) Periapse Sun OCC Earth OCC Sun OCC Earth OCC Sun OCC Earth OCC OTM-026 Ring CRX 12TI (nt) OTM-027 Apoapse OTM-028 Ring CRX Periapse Sun OCC Earth OCC Sun OCC Earth OCC Sun OCC Earth OCC Ring CRX 13TI (t) OTM-029 Apoapse OTM-030 S14 Begins OTM-031 Ring CRX Periapse Sun OCC Earth OCC Sun OCC Earth OCC Sun OCC Earth OCC
All times are in SCET. For events with nonzero duration, epoch given is start. Epoch (SCET) Date DOW Comment 2005-168T13:00 2005-169T01:34 2005-173T12:27 2005-177T13:22 2005-177T15:34 2005-177T17:15 2005-177T17:29 2005-177T19:01 2005-177T19:15 2005-177T21:39 2005-177T21:58 2005-179T13:54 Jun17 Jun18 Jun22 Jun26 Jun26 Jun26 Jun26 Jun26 Jun26 Jun26 Jun26 Jun28 Jul05 Jul08 Jul14 Jul14 Jul14 Jul15 Jul15 Jul15 Jul15 Jul15 Jul15 Jul16 Jul20 Jul21 Jul22 Fri Sat Wed Sun Sun Sun Sun Sun Sun Sun Sun Tue Tue Fri Thu Thu Thu Fri Fri Fri Fri Fri Fri Sat Wed Thu Fri P=18.2 d, i=21.8, r=40.7 Rs, Phase=67 deg, LTST=4:27 Duration = 42 days inbound 920,423 km, v= 3.7 km/s, Phase=65 deg r=3.9 Rs r=3.6 Rs, Phase=113 deg Duration = 98 min. Duration = 100 min. Duration = 152 min. Duration = 156 min. Duration = 94 min. Duration = 95 min. r=20.8 Rs P=18.3 d, i=21.8, r=40.7 Rs, Phase=67 deg, LTST=4:28 r=4.0 Rs was E2; inbound 1,000 km, v= 8.1 km/s, Phase=43 deg r=3.6 Rs, Phase=113 deg Duration = 99 min. Duration = 100 min. Duration = 156 min. Duration = 157 min. Duration = 95 min. Duration = 95 min. r=20.7 Rs SEP Decreasing, successful commanding not req. SEP Decreasing, plan for RTE-1896, no SSR playback SEP Decreasing, schedule no DSN passes P=18.3 d, i=21.8, r=40.8 Rs, Phase=68 deg, LTST=4:30 SEP Increasing, plan for RTE-1896, no SSR playback SEP Increasing, successful commanding not req. SEP Increasing Duration = 32 days r=4.0 Rs inbound 45,112 km, v= 6.5 km/s, Phase=83 deg r=3.6 Rs, Phase=112 deg Duration = 100 min. Duration = 100 min. Duration = 158 min. Duration = 159 min. Duration = 95 min. Duration = 96 min. r=20.5 Rs outbound 841,452 km, v= 3.8 km/s, Phase=62 deg
Titan Ascending Ring Ring Saturn Saturn Ring Ring Descending
2005-186T18:54 2005-189T20:37 2005-195T19:56 2005-195T19:57 2005-195T22:10 Ring 2005-196T00:04 Ring 2005-196T00:09 Saturn 2005-196T01:50 Saturn 2005-196T01:54 Ring 2005-196T04:32 Ring 2005-196T04:38 Descending 2005-197T19:56 Conjunction 2005-201T04:30 Conjunction 2005-202T09:57 Conjunction 2005-203T15:48 11EN-6 Ascending Enceladus
2005-205T01:41 Jul24 Sun Conjunction 2005-205T23:07 Jul24 Sun Conjunction 2005-207T04:44 Jul26 Tue Conjunction 2005-208T09:47 Jul27 Wed 2005-210T22:36 Jul29 Fri Ascending 2005-214T02:59 Aug02 Tue Mimas 2005-214T03:52 Aug02 Tue 2005-214T05:15 Aug02 Tue Ring 2005-214T07:16 Aug02 Tue Ring 2005-214T07:23 Aug02 Tue Saturn 2005-214T09:01 Aug02 Tue Saturn 2005-214T09:07 Aug02 Tue Ring 2005-214T11:46 Aug02 Tue Ring 2005-214T11:54 Aug02 Tue NEARP 2005-215T11:35 Aug03 Wed Descending 2005-216T02:18 Aug04 Thu Titan 2005-218T12:33 Aug06 Sat ~APO 2005-222T15:07 Aug10 Wed 2005-223T08:04 2005-230T11:00 2005-232T08:42 2005-232T10:58 2005-232T13:02 2005-232T13:22 2005-232T14:46 2005-232T15:02 2005-232T17:32 2005-232T17:53 2005-234T07:15 2005-234T08:39 2005-237T18:08 2005-240T11:38 2005-242T17:38 2005-242T21:53 2005-246T17:30 2005-248T10:07 2005-248T11:22 2005-248T12:13 2005-248T12:28 2005-248T14:12 2005-248T14:28 2005-248T15:45 2005-248T16:20 Aug11 Aug18 Aug20 Aug20 Aug20 Aug20 Aug20 Aug20 Aug20 Aug20 Aug22 Aug22 Aug25 Aug28 Aug30 Aug30 Sep03 Sep05 Sep05 Sep05 Sep05 Sep05 Sep05 Sep05 Sep05 Thu Thu Sat Sat Sat Sat Sat Sat Sat Sat Mon Mon Thu Sun Tue Tue Sat Mon Mon Mon Mon Mon Mon Mon Mon
P=18.3 d, i=21.8, r=40.7 Rs, Phase=68 deg, LTST=4:33 r=3.9 Rs r=3.6 Rs, Phase=112 deg Duration = 100 min. Duration = 103 min. Duration = 158 min. Duration = 161 min. Duration = 95 min. Duration = 98 min. r=20.3 Rs Was T6; outbound 4,015 km, v= 5.8 km/s, Phase=42 deg
13TI-3 Ascending Ring Ring Saturn Saturn Ring Ring Descending Titan 13TI+3
P=16.0 d, i=16.1, r=37.8 Rs, Phase=75 deg, LTST=4:60 Duration = 39 days r=3.0 Rs r=2.8 Rs, Phase=105 deg Duration = 122 min. Duration = 116 min. Duration = 139 min. Duration = 149 min. Duration = 110 min. Duration = 105 min.
~APO 14TI-3 Ascending Ring Ring Saturn Saturn Ring Ring
FOIA 10-JPL-F-00451
36 of 217
CASSINI Seq Rev S14 14 S14 14 S14 14 S14 S14 S14 S14 S14 S14 S14 S14 S14 S14 S14 S14 S14 S15 S15 S15 S15 S15 S15 S15 S15 S15 S15 S15 S15 S15 S15 S15 S15 S15 S16 S16 S16 S16 S16 S16 S16 S16 S16 S16 S16 S17 S17 S17 S17 S17 S17 S17 S17 S17 S17 S17 S17 S17 S17 S17 S17 S17 S18 S18 S18 S18 S18 S18 S18 15 15 15 15 15 15 15 15 15 15 15 16 16 16 16 16 16 16 16 16 16 17 17 17 17 17 17 17 17 17 17 18 18 18 18 18 18 18 18 19 19 19 19 19 19 19 19 19 19 19 20 20 20 20 20 20 20 20 20 20 20 21 21 21 21
TOUR EVENT SUMMARY All times are in SCET. For events with nonzero duration, epoch given is start. Name Event Epoch (SCET) Date DOW Comment Ring CRX Descending 2005-250T06:30 Sep07 Wed r=20.3 Rs 14TI (t) Titan 2005-250T07:50 Sep07 Wed Was T7; outbound 950 km, v= 6.1 km/s, Phase=84 deg OTM-032 14TI+3 2005-253T17:09 Sep10 Sat Apoapse OTM-033 OTM-034 Ring CRX Periapse 15TE (nt) Ring CRX 15TI (nt) 15HY (t) OTM-035 OTM-036 Apoapse OTM-037 S15 Begins 16TI (nt) 16DI (t) Ring CRX Periapse 16EN (nt) Ring CRX OTM-038 Apoapse OTM-039 OTM-040 17TI (t) Earth OCC Ring CRX Periapse OTM-041 Ring CRX S16 Begins Apoapse OTM-042 OTM-043 18RH (t) Ring CRX Periapse OTM-044 Ring CRX Apoapse OTM-045 S17 Begins OTM-046 Ring CRX 19EN (nt) Periapse 19TI (t) Ring CRX OTM-047 OTM-048 Apoapse OTM-049 20TI (t) Earth OCC Sun OCC Ring CRX Periapse OTM-050 S18 Begins OTM-051 Ring CRX Apoapse OTM-052 Ring CRX Periapse 2005-257T16:02 2005-262T16:40 2005-266T07:45 2005-266T16:26 2005-266T20:37 2005-267T01:29 2005-267T07:22 2005-267T22:01 2005-269T01:41 2005-271T16:11 2005-274T13:31 2005-275T23:07 2005-281T12:42 2005-281T15:57 2005-283T22:20 2005-284T17:58 2005-284T20:51 2005-285T01:37 2005-285T03:29 2005-285T10:50 2005-285T16:45 2005-293T23:57 2005-294T14:58 2005-298T07:14 2005-301T03:58 2005-301T04:07 2005-302T21:22 2005-302T22:45 2005-304T13:59 2005-310T01:12 2005-316T17:01 2005-317T04:59 2005-317T14:02 2005-327T13:03 2005-330T22:35 2005-331T09:16 2005-331T11:19 2005-332T04:15 2005-336T05:36 2005-345T04:23 2005-345T11:35 2005-351T14:21 2005-357T12:00 2005-358T19:14 2005-358T20:23 2005-358T21:18 2005-360T18:54 2005-363T22:59 2005-364T02:37 2006-003T02:22 2006-005T14:04 2006-012T09:23 2006-015T11:36 2006-015T11:44 2006-015T11:45 2006-017T06:21 2006-017T06:53 2006-018T12:01 2006-028T11:23 2006-033T07:53 2006-033T14:59 2006-036T20:51 2006-055T06:21 2006-056T10:18 2006-056T10:51 Sep14 Sep19 Sep23 Sep23 Sep23 Sep24 Sep24 Sep24 Sep26 Sep28 Oct01 Oct02 Oct08 Oct08 Oct10 Oct11 Oct11 Oct12 Oct12 Oct12 Oct12 Oct20 Oct21 Oct25 Oct28 Oct28 Oct29 Oct29 Oct31 Nov06 Nov12 Nov13 Nov13 Nov23 Nov26 Nov27 Nov27 Nov28 Dec02 Dec11 Dec11 Dec17 Dec23 Dec24 Dec24 Dec24 Dec26 Dec29 Dec30 Jan03 Jan05 Jan12 Jan15 Jan15 Jan15 Jan17 Jan17 Jan18 Jan28 Feb02 Feb02 Feb05 Feb24 Feb25 Feb25 Wed Mon Fri Fri Fri Sat Sat Sat Mon Wed Sat Sun Sat Sat Mon Tue Tue Wed Wed Wed Wed Thu Fri Tue Fri Fri Sat Sat Mon Sun Sat Sun Sun Wed Sat Sun Sun Mon Fri Sun Sun Sat Fri Sat Sat Sat Mon Thu Fri Tue Thu Thu Sun Sun Sun Tue Tue Wed Sat Thu Thu P=18.4 d, i=.3, r=41.4 Rs, Phase=74 deg, LTST=4:56
~APO 15HY-3 Ascending Tethys Descending Titan Hyperion 15HY+3 ~APO
r=4.4 Rs r=3.0 Rs, Phase=106 deg outbound 33,295 km, v= 7.7 km/s, Phase=76 deg r=7.9 Rs outbound 910,272 km, v= 10.7 km/s, Phase=148 deg was H1; outbound 990 km, v= 5.6 km/s, Phase=45 deg
P=18.2 d, i=.3, r=41.2 Rs, Phase=74 deg, LTST=4:55 Duration = 35 days inbound 777,198 km, was D1; inbound 500 r=4.7 Rs r=3.0 Rs, Phase=106 outbound 42,635 km, r=7.1 Rs
16DI-3 Titan Dione Ascending Enceladus Descending 16DI+1
v= 9.7 km/s, Phase=65 deg km, v= 9.0 km/s, Phase=66 deg deg v= 6.6 km/s, Phase=75 deg
P=17.9 d, i=.4, r=40.6 Rs, Phase=75 deg, LTST=4:59
~APO 17TI-3 Titan Titan Ascending 17TI+3 Descending
Was T8; inbound 1,446 km, v= 5.9 km/s, Phase=105 deg Duration = 17 min r=4.7 Rs r=4.6 Rs, Phase=92 deg r=45.3 Rs Duration = 35 days P=28.5 d, i=.4, r=55.1 Rs, Phase=88 deg, LTST=5:53
~APO 18RH-3 Rhea Ascending 18RH+1 Descending
was R1; inbound 500 km, v= 7.3 km/s, Phase=87 deg r=4.8 Rs r=4.6 Rs, Phase=92 deg r=36.8 Rs P=27.4 d, i=.4, r=53.6 Rs, Phase=89 deg, LTST=5:54 Duration = 42 days r=4.8 Rs inbound 97,169 km, v= 6.9 km/s, Phase=133 deg r=4.6 Rs, Phase=91 deg Was T9; outbound 10,429 km, v= 5.6 km/s, Phase=67 deg r=37.2 Rs
~APO 19TI-3 Ascending Enceladus Titan Descending 19TI+3 ~APO
P=23.4 d, i=.4, r=48.3 Rs, Phase=94 deg, LTST=6:15 Was T10; inbound 2,042 km, v= 5.8 km/s, Phase=121 deg Duration = 14 min Duration = 13 min r=5.6 Rs r=5.6 Rs, Phase=73 deg Duration = 42 days r=66.9 Rs
20TI-3 Titan Titan Titan Ascending 20TI+3 ~APO Descending
21TI-3 Ascending
Sun P=39.2 d, i=.4, r=68.2 Rs, Phase=108 deg, LTST=7:10 Fri Sat r=5.6 Rs Sat r=5.6 Rs, Phase=72 deg
FOIA 10-JPL-F-00451
37 of 217
CASSINI Seq Rev S18 21 S18 21 S18 21 S18 S19 S19 S19 S19 S19 S19 S19 S19 S19 S19 S19 S19 S20 S20 S20 S20 S20 S20 S20 S20 S20 S20 S20 S20 S20 S20 S20 S20 S20 S20 S20 S21 S21 S21 S21 S21 S21 S21 S21 S21 S21 S21 S21 S21 S22 S22 S22 S22 S22 S22 S22 S22 S22 S22 S22 S22 S22 S22 S22 S22 S22 S22 S22 S23 22 22 22 22 22 22 22 22 22 22 22 22 23 23 23 23 23 23 23 23 23 23 23 24 24 24 24 24 24 24 24 24 24 24 25 25 25 25 25 25 25 25 25 25 26 26 26 26 26 26 26 26 26 26 27 27 27 27 27 27 27 27 27 27 27
TOUR EVENT SUMMARY Name Event 21TI (t) Titan OTM-053 21TI+3 OTM-054 ~APO Apoapse S19 Begins Ring CRX OTM-055 Sun OCC Earth OCC 22TI (t) Periapse Ring CRX 22RH (nt) OTM-056 OTM-057 Apoapse S20 Begins Ring CRX OTM-058 Periapse Ring CRX 23TI (t) Sun OCC Earth OCC OTM-059 OTM-060 Apoapse OTM-061 Ring CRX Sun OCC Earth OCC 24TI (t) Periapse Ring CRX OTM-062 S21 Begins OTM-063 Apoapse Ring CRX OTM-064 Periapse Ring CRX Sun OCC Earth OCC 25TI (t) OTM-065 OTM-066 Apoapse S22 Begins OTM-067 26TI (t) Ring CRX Periapse Ring CRX OTM-068 OTM-069 SEP=3 deg Apoapse SEP=2 deg SEP=1 deg SEP=1 deg SEP=2 deg SEP=3 deg Ring CRX Periapse Ring CRX 27TI (nt) S23 Begins
All times are in SCET. For events with nonzero duration, epoch given is start. Epoch (SCET) Date DOW Comment 2006-058T08:20 Feb27 Mon Was T11; outbound 1,812 km, v= 5.9 km/s, Phase=93 deg 2006-061T05:51 Mar02 Thu 2006-065T05:36 Mar06 Mon 2006-068T03:29 2006-070T00:35 2006-071T14:57 2006-075T04:50 2006-077T23:56 2006-077T23:58 2006-077T23:58 2006-079T19:56 2006-079T22:33 2006-080T07:01 2006-081T04:19 2006-096T03:32 2006-099T09:56 2006-112T05:15 2006-112T15:15 2006-118T01:59 2006-118T23:54 2006-119T02:38 2006-120T20:53 2006-120T21:00 2006-120T21:05 2006-124T01:28 2006-128T01:13 2006-130T16:26 2006-138T00:41 2006-140T04:50 2006-140T12:05 2006-140T12:06 2006-140T12:13 2006-142T08:55 2006-142T15:02 2006-143T16:41 2006-154T02:39 2006-158T23:24 2006-161T22:55 2006-179T13:21 2006-180T14:37 2006-181T12:55 2006-181T19:17 2006-183T09:10 2006-183T09:11 2006-183T09:12 2006-186T21:36 2006-190T21:21 Mar09 Mar11 Mar12 Mar16 Mar18 Mar18 Mar18 Mar20 Mar20 Mar21 Mar22 Apr06 Apr09 Apr22 Apr22 Apr28 Apr28 Apr29 Apr30 Apr30 Apr30 May04 May08 May10 May18 May20 May20 May20 May20 May22 May22 May23 Jun03 Jun07 Jun10 Jun28 Jun29 Jun30 Jun30 Jul02 Jul02 Jul02 Jul05 Jul09 Jul12 Jul15 Jul18 Jul22 Jul22 Jul23 Jul24 Jul24 Aug01 Aug03 Aug04 Aug05 Aug06 Aug08 Aug09 Aug11 Aug15 Aug16 Aug17 Aug18 Aug18 Thu Sat Sun Thu Sat Sat Sat Mon Mon Tue Wed Thu Sun Sat Sat Fri Fri Sat Sun Sun Sun Thu Mon Wed Thu Sat Sat Sat Sat Mon Mon Tue Sat Wed Sat Wed Thu Fri Fri Sun Sun Sun Wed Sun Wed Sat Tue Sat Sat Sun Mon Mon Tue Thu Fri Sat Sun Tue Wed Fri Tue Wed Thu Fri Fri P=23.3 d, i=.4, r=48.4 Rs, Phase=122 deg, LTST=8:07 Duration = 42 days r=45.5 Rs Duration = 15 min Duration = 14 min Was T12; inbound 1,947 km, v= 5.8 km/s, Phase=148 deg r=5.5 Rs, Phase=45 deg r=5.7 Rs outbound 85,935 km, v= 5.3 km/s, Phase=136 deg
Descending 22TI-3 Titan Titan Titan Ascending Rhea 22TI+3 ~APO
Descending 23TI-3 Ascending Titan Titan Titan 23TI+3 ~APO
P=39.2 d, i=.4, r=68.3 Rs, Phase=135 deg, LTST=9:01 Duration = 42 days r=45.2 Rs r=5.5 Rs, Phase=44 deg r=5.7 Rs Was T13; outbound 1,853 km, v= 5.8 km/s, Phase=121 deg Duration = 16 min Duration = 7 min
P=23.3 d, i=.4, r=48.4 Rs, Phase=148 deg, LTST=9:53 r=22.9 Rs Duration = 14 min Duration = 14 min Was T14; inbound 1,879 km, v= 5.8 km/s, Phase=163 deg r=5.5 Rs, Phase=21 deg r=6.5 Rs Duration = 42 days
24TI-3 Descending Titan Titan Titan Ascending 24TI+3 ~APO
Descending 25TI-3 Ascending Titan Titan Titan 25TI+3 ~APO
P=39.2 d, i=.4, r=68.3 Rs, Phase=159 deg, LTST=10:37 r=21.6 Rs r=5.4 Rs, Phase=20 deg r=6.6 Rs Duration = 15 min Duration = 15 min Was T15; outbound 1,911 km, v= 5.8 km/s, Phase=148 deg
2006-193T05:13 2006-196T00:06 26TI-3 2006-199T20:51 Titan 2006-203T00:25 Descending 2006-203T02:35 2006-204T21:49 Ascending 2006-205T01:17 26TI+3 2006-205T20:36 ~APO 2006-213T20:05 Conjunction 2006-215T23:59 2006-216T21:25 2006-217T06:46 2006-218T18:33 2006-220T05:41 2006-221T17:26 2006-223T00:08 2006-227T02:14 2006-228T20:53 2006-229T00:21 2006-230T17:48 2006-230T22:06
P=23.3 d, i=.4, r=48.4 Rs, Phase=164 deg, LTST=10:54 Duration = 35 days Was T16; inbound 950 km, v= 6.0 km/s, Phase=105 deg r=20.1 Rs r=4.2 Rs, Phase=8 deg r=4.8 Rs
SEP Decreasing, successful commanding not req. P=24.0 d, i=14.9, r=49.0 Rs, Phase=172 deg, LTST=12:31 SEP Decreasing, plan for RTE-1896, no SSR playback SEP Decreasing, schedule no DSN passes SEP Increasing, plan for RTE-1896, no SSR playback SEP Increasing, successful commanding not req. SEP Increasing r=20.0 Rs r=4.2 Rs, Phase=8 deg r=4.8 Rs outbound 339,190 km, v= 4.8 km/s, Phase=121 deg Duration = 39 days
Conjunction Conjunction Conjunction Conjunction Conjunction Descending Ascending Titan
FOIA 10-JPL-F-00451
38 of 217
CASSINI Seq Rev S23 28 S23 28 S23 28 S23 28 S23 28 S23 28 S23 28 S23 28 S23 28 S23 28 S23 28 S23 28 S23 28 S23 28 S23 S23 S23 S23 S23 S23 S23 S24 S24 S24 S24 S24 S24 S24 S24 S24 S24 S24 S24 S25 S25 S25 S25 S25 S25 S25 S25 S25 S25 S25 S25 S25 S25 S25 S25 S26 S26 S26 S26 S26 S26 S26 S26 S26 S26 S26 S26 S26 S26 S26 29 29 29 29 29 29 29 29 29 30 30 30 30 30 30 30 30 31 31 31 31 31 31 31 32 32 32 32 32 32 33 33 33 33 33 33 33 33 34 34 34 34 35 35 35 35 35 35 35 35
TOUR EVENT SUMMARY All times are in SCET. For events with nonzero duration, epoch given is start. Name Event Epoch (SCET) Date DOW Comment Apoapse 2006-240T19:13 Aug28 Mon P=23.8 d, i=14.9, r=48.8 Rs, Phase=172 deg, LTST=12:32 OTM-070 28TI-3 2006-247T18:21 Sep04 Mon 28TI (t) Titan 2006-250T20:12 Sep07 Thu Was T17; inbound 950 km, v= 6.0 km/s, Phase=45 deg Ring CRX Descending 2006-250T21:16 Sep07 Thu r=20.5 Rs Periapse 2006-252T17:38 Sep09 Sat r=2.9 Rs, Phase=7 deg Ring CRX Ascending 2006-252T19:02 Sep09 Sat r=3.2 Rs 28EN (nt) Enceladus 2006-252T20:00 Sep09 Sat outbound 39,842 km, v= 10.3 km/s, Phase=116 deg OTM-071 28TI+3 2006-253T17:52 Sep10 Sun OTM-072 ~APO 2006-257T10:07 Sep14 Thu Sun OCC Ring 2006-257T17:22 Sep14 Thu Duration = 1458 min. Sun OCC Saturn 2006-258T07:23 Sep15 Fri Duration = 936 min. Earth OCC Ring 2006-258T17:55 Sep15 Fri Duration = 604 min. Earth OCC Saturn 2006-259T05:17 Sep16 Sat Duration = 1175 min. Earth OCC Ring 2006-259T11:07 Sep16 Sat Duration = 602 min. Apoapse OTM-073 29TI (t) Ring CRX Periapse Ring CRX OTM-074 S24 Begins OTM-075 Apoapse OTM-076 30TI (t) Ring CRX Periapse Ring CRX OTM-077 OTM-078 Apoapse OTM-079 S25 Begins 31TI (t) Ring CRX Periapse Ring CRX Apoapse Ring CRX Periapse 32EN (nt) Ring CRX OTM-080 Apoapse Ring CRX Periapse Ring CRX 33DI (nt) S26 Begins 33TI (nt) OTM-081 Apoapse Ring CRX Periapse Ring CRX Apoapse OTM-082 35TI (t) Ring CRX Periapse Ring CRX OTM-083 OTM-084 2006-260T17:08 2006-263T17:22 2006-266T18:52 2006-266T19:48 2006-268T19:30 2006-268T22:05 2006-269T16:53 2006-269T19:53 2006-274T09:08 2006-276T18:51 2006-279T16:24 2006-282T17:23 2006-282T18:02 2006-284T22:49 2006-285T04:01 2006-285T16:10 2006-290T15:40 2006-292T22:06 2006-295T15:26 2006-295T18:26 2006-298T15:51 2006-298T16:13 2006-301T00:14 2006-301T03:17 2006-307T00:08 2006-310T15:46 2006-313T00:01 2006-313T01:48 2006-313T03:03 2006-313T14:28 2006-318T23:32 2006-322T15:00 2006-324T23:04 2006-325T02:06 2006-325T02:32 2006-328T16:30 2006-329T13:57 2006-330T13:15 2006-330T22:22 2006-334T13:36 2006-336T21:42 2006-337T00:44 2006-342T21:05 2006-343T12:32 2006-346T11:35 2006-346T12:03 2006-349T00:16 2006-349T11:10 2006-349T12:03 2006-354T11:48 Sep17 Sep20 Sep23 Sep23 Sep25 Sep25 Sep26 Sep26 Oct01 Oct03 Oct06 Oct09 Oct09 Oct11 Oct12 Oct12 Oct17 Oct19 Oct22 Oct22 Oct25 Oct25 Oct28 Oct28 Nov03 Nov06 Nov09 Nov09 Nov09 Nov09 Nov14 Nov18 Nov20 Nov21 Nov21 Nov24 Nov25 Nov26 Nov26 Nov30 Dec02 Dec03 Dec08 Dec09 Dec12 Dec12 Dec15 Dec15 Dec15 Dec20 Sun Wed Sat Sat Mon Mon Tue Tue Sun Tue Fri Mon Mon Wed Thu Thu Tue Thu Sun Sun Wed Wed Sat Sat Fri Mon Thu Thu Thu Thu Tue Sat Mon Tue Tue Fri Sat Sun Sun Thu Sat Sun Fri Sat Tue Tue Fri Fri Fri Wed P=15.9 d, i=24.7, r=37.6 Rs, Phase=173 deg, LTST=11:32 Was T18; inbound 950 km, v= 6.0 km/s, Phase=90 deg r=20.5 Rs r=4.0 Rs, Phase=7 deg r=4.3 Rs Duration = 26 days
29TI-3 Titan Descending Ascending 29TI+3 ~APO
P=15.9 d, i=37.7, r=36.5 Rs, Phase=173 deg, LTST=11:33 Was T19; inbound 950 km, v= 6.0 km/s, Phase=81 deg r=20.6 Rs r=5.5 Rs, Phase=14 deg r=6.2 Rs
P=15.9 d, i=46.8, r=35.0 Rs, Phase=166 deg, LTST=12:56 Duration = 33 days Was T20; inbound 950 km, v= 6.0 km/s, Phase=25 deg r=20.7 Rs r=4.7 Rs, Phase=16 deg r=5.0 Rs P=12.0 d, i=55.4, r=28.8 Rs, Phase=164 deg, LTST=10:56 r=20.7 Rs r=4.7 Rs, Phase=16 deg outbound 94,410 km, v= 14.1 km/s, Phase=27 deg r=5.0 Rs
31TI-3 Titan Descending Ascending
Descending Enceladus Ascending ~PERI
Descending Ascending Dione Titan ~APO
P=12.0 d, i=55.4, r=28.7 Rs, Phase=164 deg, LTST=10:56 r=20.7 Rs r=4.7 Rs, Phase=16 deg r=5.0 Rs outbound 72,293 km, v= 12.3 km/s, Phase=144 deg Duration = 42 days outbound 930,525 km, v= 4.5 km/s, Phase=114 deg
Descending Ascending
P=11.9 d, i=55.4, r=28.7 Rs, Phase=164 deg, LTST=10:57 r=20.7 Rs r=4.7 Rs, Phase=16 deg r=5.0 Rs P=11.9 d, i=55.4, r=28.7 Rs, Phase=165 deg, LTST=10:58 Was T21; inbound 950 km, v= 6.0 km/s, Phase=124 deg r=20.7 Rs r=7.7 Rs, Phase=24 deg r=8.9 Rs
S26 36 Apoapse S26 36 OTM-085 S26 36 36TI (t)
36TI-3 Titan
2006-356T23:25 Dec22 Fri P=15.9 d, i=53.3, r=32.8 Rs, Phase=156 deg, LTST=13:36 2006-359T11:34 Dec25 Mon 2006-362T10:00 Dec28 Thu Was T22; inbound 1,500 km, v= 5.9 km/s, Phase=62 deg
FOIA 10-JPL-F-00451
39 of 217
CASSINI Seq Rev S26 36 S26 36 S26 36 S26 36 S26 36 S27 36 S27 S27 S27 S27 S27 S27 S27 S27 S27 S27 S27 S27 S27 S27 S27 S27 S27 S27 S28 S28 S28 S28 S28 S28 S28 S28 S28 S28 S28 S28 S28 S28 S28 S28 S28 S28 S28 S28 S28 S28 S28 S28 S28 S28 S28 S28 S29 S29 S29 S29 S29 S29 S29 S29 S29 S29 S29 S29 S29 S29 S29 S29 37 37 37 37 37 37 37 37 38 38 38 38 38 38 38 38 39 39 39 39 39 39 39 39 39 39 40 40 40 40 40 40 40 40 40 40 41 41 41 41 41 41 41 41 41 41 41 42 42 42 42 42 42 42 42 42 42 43 43 43 43 43
TOUR EVENT SUMMARY All times are in SCET. For events with nonzero duration, epoch given is start. Name Event Epoch (SCET) Date DOW Comment Ring CRX Descending 2006-362T10:25 Dec28 Thu r=20.7 Rs Periapse 2006-365T05:14 Dec31 Sun r=9.8 Rs, Phase=31 deg OTM-086 36TI+3 2006-365T11:05 Dec31 Sun Ring CRX Ascending 2006-365T23:57 Dec31 Sun r=11.6 Rs OTM-087 ~APO 2007-005T10:50 Jan05 Fri S27 Begins 2007-005T13:50 Jan05 Fri Duration = 43 days Apoapse OTM-088 37TI (t) Ring CRX OTM-089 Periapse Ring CRX OTM-090 Apoapse OTM-091 38TI (t) Ring CRX OTM-092 Periapse Ring CRX OTM-093 Apoapse Ring CRX S28 Begins OTM-094 Periapse Sun OCC Earth OCC 39TI (t) Ring CRX OTM-095 Apoapse OTM-096 Ring CRX OTM-097 Periapse Sun OCC Earth OCC 40TI (t) Ring CRX OTM-098 Apoapse OTM-099 Ring CRX OTM-100 Periapse Sun OCC Earth OCC 41TI (t) Ring CRX OTM-101 S29 Begins Apoapse OTM-102 OTM-103 Ring CRX Periapse Sun OCC Earth OCC 42TI (t) Ring CRX OTM-104 Apoapse OTM-105 OTM-106 Earth OCC Sun OCC 2007-008T04:34 2007-010T10:20 2007-013T08:34 2007-013T08:53 2007-016T02:36 2007-016T13:06 2007-017T21:27 2007-021T09:36 2007-024T12:25 2007-026T09:21 2007-029T07:12 2007-029T07:34 2007-032T08:52 2007-032T09:53 2007-035T01:05 2007-038T08:37 2007-041T10:51 2007-047T09:44 2007-048T10:52 2007-050T07:37 2007-050T11:48 2007-053T03:00 2007-053T03:00 2007-053T03:10 2007-053T03:16 2007-056T07:22 2007-058T07:50 2007-061T06:51 2007-064T21:17 2007-066T06:36 2007-066T07:12 2007-069T01:35 2007-069T01:35 2007-069T01:47 2007-069T01:52 2007-072T06:06 2007-074T12:42 2007-077T05:50 2007-081T16:03 2007-081T21:50 2007-082T12:02 2007-085T00:06 2007-085T00:07 2007-085T00:21 2007-085T00:26 2007-088T05:04 2007-088T08:04 2007-090T17:10 2007-093T04:34 2007-097T20:48 2007-098T05:20 2007-098T16:31 2007-100T22:39 2007-100T22:40 2007-100T22:57 2007-100T23:00 2007-104T03:47 2007-106T20:52 2007-109T03:32 2007-114T03:16 2007-114T09:31 2007-114T10:14 Jan08 Jan10 Jan13 Jan13 Jan16 Jan16 Jan17 Jan21 Jan24 Jan26 Jan29 Jan29 Feb01 Feb01 Feb04 Feb07 Feb10 Feb16 Feb17 Feb19 Feb19 Feb22 Feb22 Feb22 Feb22 Feb25 Feb27 Mar02 Mar05 Mar07 Mar07 Mar10 Mar10 Mar10 Mar10 Mar13 Mar15 Mar18 Mar22 Mar22 Mar23 Mar26 Mar26 Mar26 Mar26 Mar29 Mar29 Mar31 Apr03 Apr07 Apr08 Apr08 Apr10 Apr10 Apr10 Apr10 Apr14 Apr16 Apr19 Apr24 Apr24 Apr24 Mon Wed Sat Sat Tue Tue Wed Sun Wed Fri Mon Mon Thu Thu Sun Wed Sat Fri Sat Mon Mon Thu Thu Thu Thu Sun Tue Fri Mon Wed Wed Sat Sat Sat Sat Tue Thu Sun Thu Thu Fri Mon Mon Mon Mon Thu Thu Sat Tue Sat Sun Sun Tue Tue Tue Tue Sat P=16.0 d, i=56.8, r=30.7 Rs, Phase=148 deg, LTST=14:06 Was T23; inbound 950 km, v= 6.0 km/s, Phase=53 deg r=20.7 Rs r=12.6 Rs, Phase=40 deg r=14.9 Rs
37TI-3 Titan Descending 37TI+3 Ascending ~APO
P=16.0 d, i=59.4, r=27.9 Rs, Phase=140 deg, LTST=14:40 Was T24; inbound 2,776 km, v= 5.8 km/s, Phase=73 deg r=20.7 Rs r=15.6 Rs, Phase=59 deg r=19.6 Rs
Descending 39TI-3 Titan Titan Titan Ascending 39TI+3
P=18.1 d, i=59.0, r=28.5 Rs, Phase=121 deg, LTST=15:56 r=20.7 Rs Duration = 40 days r=15.6 Rs, Phase=59 deg Duration = 16 min Duration = 16 min Was T25; outbound 953 km, v= 6.3 km/s, Phase=161 deg r=19.7 Rs
P=16.0 d, i=58.8, r=28.4 Rs, Phase=97 deg, LTST=17:33 r=15.0 Rs r=12.1 Rs, Phase=83 deg Duration = 16 min Duration = 15 min Was T26; outbound 956 km, v= 6.3 km/s, Phase=149 deg r=19.7 Rs
~APO Descending 40TI-3 Titan Titan Titan Ascending 40TI+3
P=15.9 d, i=56.2, r=30.8 Rs, Phase=88 deg, LTST=18:08 r=11.8 Rs r=9.7 Rs, Phase=92 deg Duration = 17 min Duration = 16 min Was T27; outbound 953 km, v= 6.3 km/s, Phase=144 deg r=19.7 Rs Duration = 37 days P=16.0 d, i=52.4, r=33.0 Rs, Phase=80 deg, LTST=18:39
~APO Descending 41TI-3 Titan Titan Titan Ascending 41TI+3
~APO 42TI-3 Descending Titan Titan Titan Ascending 42TI+3
r=8.9 Rs r=7.5 Rs, Phase=100 deg Duration = 20 min Duration = 19 min Was T28; outbound 951 km, v= 6.3 km/s, Phase=137 deg r=19.7 Rs
~APO 43TI-3 Ring Ring
Mon P=16.0 d, i=46.9, r=34.8 Rs, Phase=73 deg, LTST=19:08 Thu Tue Tue Duration = 85 min. Tue Duration = 100 min.
FOIA 10-JPL-F-00451
40 of 217
CASSINI Seq Rev S29 43 S29 43 S29 43 S29 43 S29 43 S29 43 S29 43 S29 S29 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S30 S31 S31 S31 S31 S31 S31 S31 S31 S31 S31 S31 S31 S31 S31 S31 S31 S31 S31 S31 S31 S31 S31 S31 S31 S31 S31 S31 44 44 44 44 44 44 44 44 44 44 44 44 44 44 44 44 44 45 45 45 45 45 45 45 45 45 45 45 45 45 45 45 45 45 46 46 46 46 46 46 46 46 46 46 46 46 46 46 46 46 46 47 47 47 47 47 47 47 47 47 47 47 47 47
TOUR EVENT SUMMARY All times are in SCET. For events with nonzero duration, epoch given is start. Name Event Epoch (SCET) Date DOW Comment Ring CRX Descending 2007-114T14:15 Apr24 Tue r=6.5 Rs Periapse 2007-114T20:14 Apr24 Tue r=5.7 Rs, Phase=107 deg Sun OCC Titan 2007-116T21:10 Apr26 Thu Duration = 23 min Earth OCC Titan 2007-116T21:11 Apr26 Thu Duration = 22 min 43TI (t) Titan 2007-116T21:32 Apr26 Thu Was T29; outbound 951 km, v= 6.3 km/s, Phase=130 deg Ring CRX Ascending 2007-116T21:35 Apr26 Thu r=19.7 Rs OTM-107 43TI+3 2007-120T02:45 Apr30 Mon Apoapse OTM-108 S30 Begins OTM-109 Earth OCC Earth OCC Sun OCC Sun OCC Earth OCC Sun OCC Ring CRX Periapse Sun OCC Earth OCC 44TI (t) Ring CRX OTM-110 Apoapse OTM-111 OTM-112 Earth OCC Earth OCC Sun OCC Sun OCC 45TE (nt) Earth OCC Sun OCC Ring CRX Periapse Sun OCC Earth OCC Ring CRX 45TI (t) OTM-113 Apoapse OTM-114 OTM-115 S31 Begins Earth OCC Sun OCC Earth OCC Sun OCC Earth OCC Sun OCC Ring CRX Periapse Earth OCC Sun OCC Ring CRX 46TI (t) OTM-116 Apoapse OTM-117 OTM-118 47TE (nt) Earth OCC Sun OCC 47MI (nt) Ring CRX Periapse 47EN (nt) 47TI (t) Ring CRX OTM-119 2007-122T23:34 2007-124T19:00 2007-124T22:00 2007-130T02:14 2007-130T14:55 2007-130T15:39 2007-130T15:43 2007-130T16:33 2007-130T17:13 2007-130T17:56 2007-130T19:46 2007-130T22:55 2007-132T19:40 2007-132T19:41 2007-132T20:08 2007-132T20:09 2007-136T01:43 2007-139T01:11 2007-141T01:27 2007-146T01:12 2007-146T18:59 2007-146T19:20 2007-146T19:51 2007-146T19:56 2007-146T20:57 2007-146T21:16 2007-146T21:38 2007-146T22:53 2007-147T00:37 2007-148T18:07 2007-148T18:09 2007-148T18:33 2007-148T18:51 2007-152T00:41 2007-155T01:21 2007-156T16:55 2007-162T00:10 2007-162T03:10 2007-162T19:35 2007-162T20:16 2007-162T20:56 2007-162T21:18 2007-162T21:48 2007-162T22:15 2007-162T23:38 2007-163T00:51 2007-164T17:02 2007-164T17:03 2007-164T17:43 2007-164T17:46 2007-167T23:39 2007-171T01:18 2007-172T23:23 2007-177T23:08 2007-178T19:53 2007-178T22:18 2007-178T22:24 2007-178T22:56 2007-179T00:14 2007-179T01:05 2007-179T01:15 2007-180T17:05 2007-183T16:20 2007-183T22:37 May02 May04 May04 May10 May10 May10 May10 May10 May10 May10 May10 May10 May12 May12 May12 May12 May16 May19 May21 May26 May26 May26 May26 May26 May26 May26 May26 May26 May27 May28 May28 May28 May28 Jun01 Jun04 Jun05 Jun11 Jun11 Jun11 Jun11 Jun11 Jun11 Jun11 Jun11 Jun11 Jun12 Jun13 Jun13 Jun13 Jun13 Jun16 Jun20 Jun21 Jun26 Jun27 Jun27 Jun27 Jun27 Jun28 Jun28 Jun28 Jun29 Jul02 Jul02 Wed Fri Fri Thu Thu Thu Thu Thu Thu Thu Thu Thu Sat Sat Sat Sat Wed Sat Mon Sat Sat Sat Sat Sat Sat Sat Sat Sat Sun Mon Mon Mon Mon Fri Mon Tue Mon Mon Mon Mon Mon Mon Mon Mon Mon Tue Wed Wed Wed Wed Sat Wed Thu Tue Wed Wed Wed Wed Thu Thu Thu Fri Mon Mon P=16.0 d, i=39.0, r=36.3 Rs, Phase=66 deg, LTST=19:34 Duration = 37 days Duration = 126 min. Duration = 60 min. Duration = 136 min. Duration = 40 min. Duration = 60 min. Duration = 40 min. r=4.7 Rs r=4.2 Rs, Phase=114 deg Duration = 27 min Duration = 26 min Was T30; outbound 950 km, v= 6.3 km/s, Phase=121 deg r=19.7 Rs
~APO 44TI-3 Saturn Ring Saturn Ring Ring Ring Descending Titan Titan Titan Ascending 44TI+3
P=16.0 d, i=28.0, r=37.3 Rs, Phase=61 deg, LTST=19:57
~APO 45TI-3 Ring Saturn Ring Saturn Tethys Ring Ring Descending Titan Titan Ascending Titan 45TI+3
Duration = 49 min. Duration = 144 min. Duration = 38 min. Duration = 136 min. inbound 97,131 km, v= 11.7 km/s, Phase=75 deg Duration = 49 min. Duration = 38 min. r=3.4 Rs r=3.2 Rs, Phase=119 deg Duration = 32 min Duration = 32 min r=19.6 Rs Was T31; outbound 2,425 km, v= 6.1 km/s, Phase=114 deg
~APO 46TI-3 Ring Ring Saturn Saturn Ring Ring Descending Titan Titan Ascending Titan 46TI+3
Duration = 33 days Duration = 74 min. Duration = 56 min. Duration = 122 min. Duration = 118 min. Duration = 76 min. Duration = 56 min. r=2.9 Rs r=2.7 Rs, Phase=123 deg Duration = 40 min Duration = 38 min r=19.7 Rs Was T32; outbound 950 km, v= 6.3 km/s, Phase=107 deg
~APO 47TI-3 Tethys Saturn Saturn Mimas Descending Enceladus Titan Ascending 47TI+3
inbound 16,166 km, v= 10.1 km/s, Phase=90 deg Duration = 80 min. Duration = 90 min. inbound 89,730 km, v= 16.2 km/s, Phase=110 deg r=2.5 Rs r=2.4 Rs, Phase=126 deg outbound 90,769 km, v= 9.4 km/s, Phase=55 deg Was T33; outbound 1,942 km, v= 6.2 km/s, Phase=96 deg r=35.9 Rs
FOIA 10-JPL-F-00451
41 of 217
CASSINI TOUR EVENT SUMMARY Name Event Seq Rev ~APO S31 47 OTM-120 S31 S32 S32 S32 S32 S32 S32 S32 S32 S32 S33 S33 S33 S33 S33 S33 S33 S33 S33 S33 S33 S33 S33 S33 S33 S33 S33 S33 S33 S34 S34 S34 S34 S34 S34 S34 S34 S34 S34 S34 S34 S34 S34 S34 S34 S34 S34 S34 S34 S35 S35 S35 S35 S35 S35 S35 S35 S35 S35 S35 S35 S35 S35 S35 S35 S35 S35 S35 48 48 48 48 48 48 48 48 48 49 49 49 49 49 49 49 49 49 49 49 49 49 49 49 49 49 49 50 50 50 50 50 50 50 50 50 50 50 50 50 51 51 51 51 51 51 51 51 51 51 52 52 52 52 52 52 52 52 52 52 53 53 53 53 53 53 53 53 Apoapse S32 Begins OTM-121 48TI (t) Ring CRX Periapse OTM-122 Ring CRX OTM-123
All times are in SCET. For events with nonzero duration, epoch given is start. Epoch (SCET) Date DOW Comment 2007-187T22:22 Jul06 Fri 2007-190T09:52 2007-195T01:06 2007-196T21:51 2007-200T00:39 2007-201T14:35 2007-201T19:53 2007-202T21:36 2007-204T04:54 2007-217T20:35 2007-221T16:29 2007-223T23:20 2007-230T13:46 2007-231T23:19 2007-233T20:36 2007-235T17:58 2007-237T03:40 2007-239T19:20 2007-241T07:40 2007-241T11:21 2007-241T13:09 2007-242T01:26 2007-243T06:34 2007-245T11:35 2007-248T18:50 2007-251T18:50 2007-253T12:33 2007-256T18:20 2007-257T11:43 2007-260T18:21 2007-265T20:51 2007-272T10:06 2007-273T06:27 2007-273T06:28 2007-273T07:28 2007-273T07:32 2007-273T10:53 2007-273T11:42 2007-274T22:59 2007-275T04:48 2007-275T15:19 2007-285T10:07 2007-295T00:47 2007-297T05:27 2007-297T05:36 2007-297T05:51 2007-297T08:15 2007-297T16:09 2007-299T10:34 2007-305T15:40 2007-305T18:40 2007-309T08:07 2007-320T14:41 2007-320T19:52 2007-321T05:17 2007-321T05:30 2007-321T05:38 2007-321T08:04 2007-323T00:52 2007-323T04:37 2007-326T06:57 2007-329T07:59 2007-331T06:43 2007-336T13:44 2007-337T05:01 2007-337T05:22 2007-337T05:28 2007-337T06:14 2007-337T06:25 Jul09 Jul14 Jul15 Jul19 Jul20 Jul20 Jul21 Jul23 Aug05 Aug09 Aug11 Aug18 Aug19 Aug21 Aug23 Aug25 Aug27 Aug29 Aug29 Aug29 Aug30 Aug31 Sep02 Sep05 Sep08 Sep10 Sep13 Sep14 Sep17 Sep22 Sep29 Sep30 Sep30 Sep30 Sep30 Sep30 Sep30 Oct01 Oct02 Oct02 Oct12 Oct22 Oct24 Oct24 Oct24 Oct24 Oct24 Oct26 Nov01 Nov01 Nov05 Nov16 Nov16 Nov17 Nov17 Nov17 Nov17 Nov19 Nov19 Nov22 Nov25 Nov27 Dec02 Dec03 Dec03 Dec03 Dec03 Dec03 Mon Sat Sun Thu Fri Fri Sat Mon Sun Thu Sat Sat Sun Tue Thu Sat Mon Wed Wed Wed Thu Fri Sun Wed Sat Mon Thu Fri Mon Sat Sat Sun Sun Sun Sun Sun Sun Mon Tue Tue Fri Mon Wed Wed Wed Wed Wed Fri Thu Thu Mon Fri Fri Sat Sat Sat Sat Mon Mon Thu Sun Tue Sun Mon Mon Mon Mon Mon P=22.8 d, i=.4, r=47.8 Rs, Phase=64 deg, LTST=19:45 Duration = 29 days Was T34; inbound 1,302 km, v= 6.2 km/s, Phase=34 deg r=6.2 Rs r=5.3 Rs, Phase=131 deg r=24.5 Rs
Apoapse S33 Begins SEP=3 deg Conjunction SEP=2 deg Conjunction SEP=1.24 deg Conjunction SEP=2 deg Conjunction SEP=3 deg Conjunction OTM-124 49TI-3 Ring CRX Descending 49TE (nt) Tethys Periapse 49RH (nt) Rhea 49TI (t) Titan OTM-125 49TI+2 OTM-126 49IA-5 OTM-127 49IA-2 49IA (t) Iapetus OTM-128 49IA+3 Apoapse OTM-129 S34 Begins OTM-130 50DI (nt) Ring CRX Earth OCC Sun OCC 50EN (nt) Periapse Ring CRX 50TI (t) Ring CRX Apoapse 51TI (nt) Sun OCC Earth OCC Ring CRX Periapse OTM-131 Ring CRX OTM-132 S35 Begins Apoapse OTM-133 52RH (nt) Sun OCC Earth OCC Ring CRX Periapse 52TI (t) Ring CRX OTM-134 Apoapse OTM-135 OTM-136 Sun OCC Earth OCC 53MI (nt) Sun OCC Earth OCC
P=39.7 d, i=.3, r=69.1 Rs, Phase=49 deg, LTST=20:45 Duration = 42 days SEP Decreasing, successful commanding not req. SEP Decreasing, plan for RTE-1896, no SSR playback SEP - Minimum Value (>1 deg) SEP Increasing, plan for RTE-1896, no SSR playback SEP Increasing, successful commanding not req. r=6.2 Rs inbound 48,324 km, v= 4.7 km/s, Phase=104 deg r=5.3 Rs, Phase=132 deg outbound 5,098 km, v= 6.7 km/s, Phase=46 deg Was T35; outbound 3,227 km, v= 6.1 km/s, Phase=87 deg
was I1; outbound 1,000 km, v= 2.4 km/s, Phase=65 deg
P=32.0 d, i=6.2, r=59.8 Rs, Phase=42 deg, LTST=21:13 Duration = 40 days inbound 56,523 km, v= 5.6 km/s, Phase=47 deg r=5.7 Rs Duration = 100 min. Duration = 59 min. inbound 88,174 km, v= 6.1 km/s, Phase=99 deg r=4.6 Rs, Phase=139 deg r=17.7 Rs Was T36; outbound 950 km, v= 6.3 km/s, Phase=67 deg r=22.9 Rs P=23.8 d, i=5.0, r=49.2 Rs, Phase=35 deg, LTST=21:39 inbound 455,697 km, v= 4.1 km/s, Phase=29 deg Duration = 74 min. Duration = 94 min. r=4.1 Rs r=3.8 Rs, Phase=145 deg r=22.6 Rs Duration = 42 days P=24.0 d, i=4.9, r=49.4 Rs, Phase=35 deg, LTST=21:41 inbound 78,360 km, v= 9.1 km/s, Phase=148 deg Duration = 78 min. Duration = 98 min. r=4.1 Rs r=3.8 Rs, Phase=146 deg Was T37; outbound 950 km, v= 6.3 km/s, Phase=51 deg r=20.8 Rs
49IA+7 50TI-3 Dione Ascending Saturn Saturn Enceladus Descending Titan Ascending
Titan Saturn Saturn Descending 50TI+P Ascending ~APO
52TI-3 Rhea Saturn Saturn Descending Titan Ascending 52TI+3
~APO 53TI-3 Ring Ring Mimas Saturn Saturn
Duration = 90 min. Duration = 74 min. inbound 79,272 km, v= 14.8 km/s, Phase=138 deg Duration = 83 min. Duration = 86 min.
FOIA 10-JPL-F-00451
42 of 217
CASSINI Seq Rev S35 53 S35 53 S35 53 S35 53 S35 53 S35 S35 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S36 S37 S37 S37 S37 S37 S37 S37 S37 S37 S37 S37 S37 S37 S37 S37 S37 S37 S37 S37 S37 S38 S38 S38 S38 S38 S38 S38 S38 S38 S38 54 54 54 54 54 54 54 54 54 54 54 54 54 55 55 55 55 55 55 55 55 55 56 56 56 56 56 56 56 56 56 56 57 57 57 57 57 57 57 57 57 58 58 58 58 58 58 58 58 58 59 59 59 59 59 59 59 59 59 59 59
TOUR EVENT SUMMARY All times are in SCET. For events with nonzero duration, epoch given is start. Name Event Epoch (SCET) Date DOW Comment Ring CRX Descending 2007-337T06:46 Dec03 Mon r=2.6 Rs Periapse 2007-337T07:43 Dec03 Mon r=2.5 Rs, Phase=155 deg 53TI (t) Titan 2007-339T00:06 Dec05 Wed Was T38; outbound 1,300 km, v= 6.3 km/s, Phase=70 deg Ring CRX Ascending 2007-339T02:16 Dec05 Wed r=20.3 Rs OTM-137 53TI+3 2007-342T06:00 Dec08 Sat Apoapse OTM-138 S36 Begins OTM-139 Sun OCC Earth OCC Sun OCC Earth OCC Ring CRX Periapse 54TI (t) Ring CRX OTM-140 Apoapse OTM-141 OTM-142 Sun OCC Earth OCC Ring CRX Periapse 55TI (t) Ring CRX Apoapse Sun OCC Earth OCC Sun OCC Earth OCC Ring CRX Periapse OTM-143 Ring CRX S37 Begins Apoapse 57TI (nt) Sun OCC Earth OCC Sun OCC Earth OCC Ring CRX Periapse Ring CRX Apoapse OTM-144 Sun OCC Earth OCC Sun OCC Earth OCC Ring CRX Periapse Ring CRX Apoapse S38 Begins OTM-145 Sun OCC Earth OCC Sun OCC Earth OCC Ring CRX Periapse 59TI (t) Ring CRX 2007-345T05:35 2007-347T13:15 2007-347T16:15 2007-352T05:16 2007-353T02:07 2007-353T02:33 2007-353T03:08 2007-353T03:25 2007-353T03:37 2007-353T05:05 2007-354T22:56 2007-355T00:13 2007-358T05:02 2007-361T01:27 2007-363T12:02 2008-003T04:18 2008-003T20:25 2008-003T20:52 2008-003T22:02 2008-004T00:44 2008-005T21:26 2008-005T22:16 2008-009T22:30 2008-015T19:16 2008-015T19:30 2008-015T19:50 2008-015T20:12 2008-015T20:20 2008-015T21:53 2008-016T03:34 2008-017T20:37 2008-021T13:35 2008-021T21:09 2008-022T21:06 2008-027T17:47 2008-027T17:58 2008-027T18:23 2008-027T18:40 2008-027T18:50 2008-027T20:23 2008-029T18:53 2008-033T19:55 2008-037T02:06 2008-039T16:35 2008-039T16:40 2008-039T17:05 2008-039T17:15 2008-039T17:36 2008-039T19:06 2008-041T18:36 2008-045T19:22 2008-047T11:51 2008-051T01:06 2008-051T17:07 2008-051T17:07 2008-051T17:39 2008-051T17:42 2008-051T18:06 2008-051T19:37 2008-053T17:39 2008-053T18:29 Dec11 Dec13 Dec13 Dec18 Dec19 Dec19 Dec19 Dec19 Dec19 Dec19 Dec20 Dec21 Dec24 Dec27 Dec29 Jan03 Jan03 Jan03 Jan03 Jan04 Jan05 Jan05 Jan09 Jan15 Jan15 Jan15 Jan15 Jan15 Jan15 Jan16 Jan17 Jan21 Jan21 Jan22 Jan27 Jan27 Jan27 Jan27 Jan27 Jan27 Jan29 Feb02 Feb06 Feb08 Feb08 Feb08 Feb08 Feb08 Feb08 Feb10 Feb14 Feb16 Feb20 Feb20 Feb20 Feb20 Feb20 Feb20 Feb20 Feb22 Feb22 Tue Thu Thu Tue Wed Wed Wed Wed Wed Wed Thu Fri Mon Thu Sat Thu Thu Thu Thu Fri Sat Sat Wed Tue Tue Tue Tue Tue Tue Wed Thu Mon Mon Tue Sun Sun Sun Sun Sun Sun Tue Sat Wed Fri Fri Fri Fri Fri Fri Sun Thu Sat Wed Wed Wed Wed Wed Wed Wed Fri Fri P=16.0 d, i=26.4, r=37.5 Rs, Phase=30 deg, LTST=21:59 Duration = 39 days Duration = 70 min. Duration = 50 min. Duration = 76 min. Duration = 76 min. r=3.2 Rs r=3.0 Rs, Phase=150 deg Was T39; outbound 953 km, v= 6.3 km/s, Phase=61 deg r=20.1 Rs
~APO 54TI-3 Ring Ring Saturn Saturn Descending Titan Ascending 54TI+3
~APO 55TI-3 Ring Ring Descending Titan Ascending
Duration = 57 min. Duration = 40 min. r=4.4 Rs r=4.0 Rs, Phase=143 deg Was T40; outbound 949 km, v= 6.3 km/s, Phase=37 deg r=19.9 Rs P=11.9 d, i=47.1, r=30.1 Rs, Phase=31 deg, LTST=21:55 Duration = 49 min. Duration = 38 min. Duration = 59 min. Duration = 41 min. r=3.5 Rs r=3.3 Rs, Phase=149 deg r=19.8 Rs Duration = 26 days P=11.9 d, i=47.1, r=30.1 Rs, Phase=31 deg, LTST=21:55 inbound 860,776 km, v= 4.5 km/s, Phase=70 deg Duration = 48 min. Duration = 40 min. Duration = 56 min. Duration = 41 min. r=3.5 Rs r=3.3 Rs, Phase=149 deg r=19.8 Rs P=12.0 d, i=47.0, r=30.2 Rs, Phase=31 deg, LTST=21:56 Duration = 47 min. Duration = 43 min. Duration = 61 min. Duration = 53 min. r=3.4 Rs r=3.2 Rs, Phase=149 deg r=20.1 Rs P=12.0 d, i=47.7, r=30.3 Rs, Phase=31 deg, LTST=21:58 Duration = 36 days Duration = 46 min. Duration = 45 min. Duration = 58 min. Duration = 55 min. r=3.4 Rs r=3.2 Rs, Phase=150 deg Was T41; outbound 959 km, v= 6.4 km/s, Phase=30 deg r=19.9 Rs
Ring Ring Saturn Saturn Descending 55TI+P Ascending
Titan Ring Ring Saturn Saturn Descending Ascending
~APO Ring Ring Saturn Saturn Descending Ascending
59TI-3 Ring Ring Saturn Saturn Descending Titan Ascending
S38 60 Apoapse S38 60 OTM-146
59TI+P
2008-056T22:23 Feb25 Mon P=10.6 d, i=56.8, r=27.1 Rs, Phase=32 deg, LTST=21:54 2008-062T00:06 Mar02 Sun
FOIA 10-JPL-F-00451
43 of 217
CASSINI Seq Rev S38 60 S38 60 S38 60 S38 60 S38 60 S38 60 S38 60 S38 60 S38 S38 S38 S38 S38 S38 S38 S38 S38 S38 S38 S38 S38 S38 S39 S39 S39 S39 S39 S39 S39 S39 S39 S39 S39 S39 S39 S39 S39 S39 S39 S39 S39 S39 S39 S39 S39 S40 S40 S40 S40 S40 S40 S40 S40 S40 S40 S40 S40 S40 S40 S40 S40 S40 S40 S40 S40 S40 S40 61 61 61 61 61 61 61 61 61 61 61 62 62 62 62 62 62 62 62 62 62 62 63 63 63 63 63 63 64 64 64 64 64 64 64 64 65 65 65 65 65 65 65 66 66 66 66 66 66 66 66 67 67 67 67 67 67 67 67
TOUR EVENT SUMMARY All times are in SCET. For events with nonzero duration, epoch given is start. Name Event Epoch (SCET) Date DOW Comment Earth OCC Ring 2008-062T02:37 Mar02 Sun Duration = 46 min. Sun OCC Ring 2008-062T02:41 Mar02 Sun Duration = 43 min. Earth OCC Saturn 2008-062T03:23 Mar02 Sun Duration = 22 min. Sun OCC Saturn 2008-062T03:31 Mar02 Sun Duration = 12 min. Ring CRX Descending 2008-062T03:42 Mar02 Sun r=3.9 Rs Periapse 2008-062T05:31 Mar02 Sun r=3.7 Rs, Phase=149 deg Ring CRX Ascending 2008-064T08:49 Mar04 Tue r=19.9 Rs OTM-147 ~APO 2008-067T07:21 Mar07 Fri Apoapse OTM-148 61TI (nt) Earth OCC Sun OCC Earth OCC Ring CRX 61EN (t) Periapse OTM-149 Ring CRX Apoapse OTM-150 OTM-151 S39 Begins Earth OCC Sun OCC Earth OCC Ring CRX Periapse 62TI (t) Ring CRX Apoapse Earth OCC Sun OCC Ring CRX Periapse Ring CRX Apoapse OTM-152 Earth OCC Sun OCC Ring CRX 64MI (nt) Periapse Ring CRX Apoapse S40 Begins Earth OCC Sun OCC Ring CRX Periapse Ring CRX Apoapse OTM-153 66TI (nt) Earth OCC Sun OCC Ring CRX Periapse Ring CRX Apoapse OTM-154 Earth OCC Sun OCC Ring CRX Periapse 67TI (t) Ring CRX 2008-067T13:13 2008-070T07:06 2008-070T19:15 2008-072T17:57 2008-072T18:06 2008-072T18:39 2008-072T19:05 2008-072T19:05 2008-072T20:55 2008-073T23:21 2008-075T00:07 2008-078T04:39 2008-078T06:35 2008-082T22:50 2008-083T01:50 2008-083T09:22 2008-083T09:36 2008-083T10:02 2008-083T10:33 2008-083T12:23 2008-085T14:35 2008-085T15:16 2008-088T01:36 2008-092T17:06 2008-092T17:25 2008-092T18:27 2008-092T20:34 2008-095T05:13 2008-097T15:37 2008-102T03:33 2008-102T07:09 2008-102T07:31 2008-102T08:32 2008-102T09:38 2008-102T10:40 2008-104T19:10 2008-107T05:19 2008-110T07:18 2008-111T20:27 2008-111T20:51 2008-111T21:50 2008-111T23:58 2008-114T08:24 2008-116T18:32 2008-117T03:47 2008-117T18:22 2008-121T09:32 2008-121T09:58 2008-121T10:56 2008-121T13:03 2008-123T21:29 2008-126T07:40 2008-130T03:00 2008-130T22:47 2008-130T23:14 2008-131T00:10 2008-131T02:18 2008-133T10:09 2008-133T10:38 Mar07 Mar10 Mar10 Mar12 Mar12 Mar12 Mar12 Mar12 Mar12 Mar13 Mar15 Mar18 Mar18 Mar22 Mar23 Mar23 Mar23 Mar23 Mar23 Mar23 Mar25 Mar25 Mar28 Apr01 Apr01 Apr01 Apr01 Apr04 Apr06 Apr11 Apr11 Apr11 Apr11 Apr11 Apr11 Apr13 Apr16 Apr19 Apr20 Apr20 Apr20 Apr20 Apr23 Apr25 Apr26 Apr26 Apr30 Apr30 Apr30 Apr30 May02 May05 May09 May09 May09 May10 May10 May12 May12 Fri Mon Mon Wed Wed Wed Wed Wed Wed Thu Sat Tue Tue Sat Sun Sun Sun Sun Sun Sun Tue Tue Fri Tue Tue Tue Tue Fri Sun Fri Fri Fri Fri Fri Fri Sun Wed Sat Sun Sun Sun Sun Wed Fri Sat Sat Wed Wed Wed Wed Fri Mon Fri Fri Fri Sat Sat Mon Mon P=10.6 d, i=56.8, r=27.2 Rs, Phase=31 deg, LTST=21:55 inbound 922,539 km, v= 6.3 km/s, Phase=123 deg Duration = 48 min. Duration = 41 min. Duration = 31 min. r=3.9 Rs was E3; inbound 995 km, v= 14.6 km/s, Phase=56 deg r=3.7 Rs, Phase=149 deg r=19.9 Rs P=10.6 d, i=56.8, r=27.2 Rs, Phase=31 deg, LTST=21:56
61EN-3 Titan Ring Ring Saturn Descending Enceladus 61EN+1 Ascending
~APO 62TI-3 Ring Ring Saturn Descending Titan Ascending
Duration = 27 days Duration = 50 min. Duration = 40 min. Duration = 38 min. r=3.9 Rs r=3.7 Rs, Phase=149 deg Was T42; outbound 950 km, v= 6.4 km/s, Phase=21 deg r=19.9 Rs P=9.6 d, i=63.7, r=24.5 Rs, Phase=31 deg, LTST=21:57 Duration = 51 min. Duration = 38 min. r=4.5 Rs r=4.3 Rs, Phase=149 deg r=19.9 Rs P=9.6 d, i=63.7, r=24.5 Rs, Phase=31 deg, LTST=21:57 Duration = 52 min. Duration = 37 min. r=4.5 Rs inbound 95,428 km, v= 16.9 km/s, Phase=137 deg r=4.3 Rs, Phase=149 deg r=19.8 Rs P=9.6 d, i=63.7, r=24.5 Rs, Phase=31 deg, LTST=21:58 Duration = 42 days Duration = 53 min. Duration = 36 min. r=4.5 Rs r=4.3 Rs, Phase=150 deg r=19.8 Rs P=9.5 d, i=63.7, r=24.5 Rs, Phase=30 deg, LTST=21:58 inbound 780,589 km, v= 5.5 km/s, Phase=94 deg Duration = 53 min. Duration = 35 min. r=4.5 Rs r=4.3 Rs, Phase=150 deg r=19.8 Rs P=9.6 d, i=63.7, r=24.5 Rs, Phase=30 deg, LTST=21:59 Duration = 53 min. Duration = 34 min. r=4.5 Rs r=4.3 Rs, Phase=150 deg Was T43; outbound 950 km, v= 6.4 km/s, Phase=35 deg r=19.8 Rs
Ring Ring Descending Ascending
62TI+P Ring Ring Descending Mimas Ascending
Ring Ring Descending Ascending
~APO Titan Ring Ring Descending Ascending
67TI-3 Ring Ring Descending Titan Ascending
FOIA 10-JPL-F-00451
44 of 217
CASSINI Seq Rev S40 68 S40 68 S40 68 S40 68 S40 68 S40 68 S40 68 S40 68 S40 68 S40 68 S40 S40 S40 S40 S40 S40 S40 S40 S40 S40 S40 S40 S40 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 S41 69 69 69 69 69 69 69 69 69 69 69 69 70 70 70 70 70 70 70 70 70 71 71 71 71 71 71 71 72 72 72 72 72 72 72 72 72 73 73 73 73 73 73 73 73 73 74 74 74 74 74 74 74 74 74
TOUR EVENT SUMMARY All times are in SCET. For events with nonzero duration, epoch given is start. Name Event Epoch (SCET) Date DOW Comment Apoapse 2008-135T00:13 May14 Wed P=8.0 d, i=70.1, r=22.3 Rs, Phase=25 deg, LTST=22:22 OTM-155 67TI+P 2008-138T18:44 May17 Sat Earth OCC Saturn 2008-138T22:00 May17 Sat Duration = 72 min. Earth OCC Ring 2008-138T22:01 May17 Sat Duration = 14 min. Earth OCC Ring 2008-138T22:32 May17 Sat Duration = 14 min. Sun OCC Saturn 2008-138T22:37 May17 Sat Duration = 28 min. Sun OCC Ring 2008-138T22:37 May17 Sat Duration = 12 min. Ring CRX Descending 2008-138T22:57 May17 Sat r=3.3 Rs Periapse 2008-138T23:49 May17 Sat r=3.3 Rs, Phase=155 deg Ring CRX Ascending 2008-141T09:54 May20 Tue r=19.8 Rs Apoapse OTM-156 OTM-157 Earth OCC Earth OCC Earth OCC Sun OCC Sun OCC Ring CRX Periapse 69TI (t) Ring CRX Apoapse S41 Begins Earth OCC Earth OCC Sun OCC Earth OCC Ring CRX Periapse Ring CRX Apoapse Earth OCC Sun OCC Sun OCC Ring CRX Periapse Ring CRX Apoapse 72TI (nt) Earth OCC Earth OCC Sun OCC Sun OCC Ring CRX Periapse Ring CRX Apoapse Earth OCC Earth OCC Sun OCC Sun OCC Earth OCC Ring CRX Periapse Ring CRX Apoapse Earth OCC Earth OCC Sun OCC Sun OCC Ring CRX 74EN (nt) Periapse 2008-142T23:24 2008-143T02:13 2008-146T17:58 2008-146T21:10 2008-146T21:11 2008-146T21:41 2008-146T21:46 2008-146T21:50 2008-146T22:06 2008-146T22:58 2008-149T08:33 2008-149T09:05 2008-150T08:58 2008-152T04:27 2008-153T20:57 2008-153T21:09 2008-153T21:17 2008-153T21:36 2008-153T21:51 2008-153T22:16 2008-156T11:59 2008-157T11:37 2008-160T23:41 2008-161T00:01 2008-161T00:23 2008-161T00:34 2008-161T00:58 2008-163T14:56 2008-164T14:16 2008-165T04:17 2008-168T02:15 2008-168T02:26 2008-168T02:34 2008-168T02:38 2008-168T03:06 2008-168T03:30 2008-170T17:36 2008-171T16:44 2008-175T04:47 2008-175T04:57 2008-175T05:05 2008-175T05:09 2008-175T05:22 2008-175T05:36 2008-175T05:59 2008-177T20:20 2008-178T19:12 2008-182T07:14 2008-182T07:24 2008-182T07:32 2008-182T07:35 2008-182T08:01 2008-182T08:07 2008-182T08:25 2008-183T00:00 May21 May22 May25 May25 May25 May25 May25 May25 May25 May25 May28 May28 May29 May31 Jun01 Jun01 Jun01 Jun01 Jun01 Jun01 Jun04 Jun05 Jun08 Jun09 Jun09 Jun09 Jun09 Jun11 Jun12 Jun13 Jun16 Jun16 Jun16 Jun16 Jun16 Jun16 Jun18 Jun19 Jun23 Jun23 Jun23 Jun23 Jun23 Jun23 Jun23 Jun25 Jun26 Jun30 Jun30 Jun30 Jun30 Jun30 Jun30 Jun30 Jul01 Wed Thu Sun Sun Sun Sun Sun Sun Sun Sun Wed Wed Thu Sat Sun Sun Sun Sun Sun Sun Wed Thu Sun Mon Mon Mon Mon Wed Thu Fri Mon Mon Mon Mon Mon Mon Wed Thu Mon Mon Mon Mon Mon Mon Mon Wed Thu Mon Mon Mon Mon Mon Mon Mon Tue P=8.0 d, i=70.1, r=22.2 Rs, Phase=24 deg, LTST=22:22
~APO 69TI-3 Saturn Ring Ring Ring Saturn Descending Titan Ascending
Duration = 70 min. Duration = 14 min. Duration = 14 min. Duration = 12 min. Duration = 21 min. r=3.3 Rs r=3.3 Rs, Phase=155 deg Was T44; outbound 1,316 km, v= 6.3 km/s, Phase=23 deg r=19.8 Rs P=7.1 d, i=75.6, r=20.9 Rs, Phase=22 deg, LTST=1:26 Duration = 35 days Duration = 75 min. Duration = 11 min. Duration = 55 min. Duration = 11 min. r=2.7 Rs r=2.7 Rs, Phase=158 deg r=19.8 Rs P=7.1 d, i=75.6, r=20.9 Rs, Phase=22 deg, LTST=1:26 Duration = 74 min. Duration = 53 min. Duration = 8 min. r=2.7 Rs r=2.7 Rs, Phase=158 deg r=19.9 Rs P=7.1 d, i=75.6, r=20.9 Rs, Phase=22 deg, LTST=1:26 inbound 372,240 km, v= 5.9 km/s, Phase=89 deg Duration = 72 min. Duration = 37 min. Duration = 52 min. Duration = 25 min. r=2.7 Rs r=2.7 Rs, Phase=158 deg r=19.9 Rs P=7.1 d, i=75.6, r=20.9 Rs, Phase=22 deg, LTST=1:27 Duration = 70 min. Duration = 11 min. Duration = 50 min. Duration = 25 min. Duration = 11 min. r=2.7 Rs r=2.7 Rs, Phase=158 deg r=19.9 Rs P=7.1 d, i=75.6, r=20.9 Rs, Phase=22 deg, LTST=1:27 Duration = 68 min. Duration = 10 min. Duration = 48 min. Duration = 24 min. r=2.7 Rs inbound 99,092 km, v= 21.6 km/s, Phase=66 deg r=2.7 Rs, Phase=158 deg End baseline tour
Saturn Ring Saturn Ring Descending Ascending
Saturn Saturn Ring Descending Ascending
Titan Saturn Ring Saturn Ring Descending Ascending
Saturn Ring Saturn Ring Ring Descending Ascending
Saturn Ring Saturn Ring Descending Enceladus End Tour
FOIA 10-JPL-F-00451
45 of 217
One-way Light Times for Science Cruise, Approach, and Tour

Light times are rounded to the nearest minute.
DOY range OWLT start-end (min) (hh:mm) 2002 121-123 66 01:06 124-132 67 01:07 133-143 68 01:08 144-157 69 01:09 158-216 70 01:10 217-231 69 01:09 232-243 68 01:08 244-253 67 01:07 254-262 66 01:06 263-271 65 01:05 272-280 64 01:04 281-289 63 01:03 290-298 62 01:02 299-308 61 01:01 309-319 60 01:00 320-336 59 00:59 337-365 58 00:58
DOY range OWLT start-end (min) (hh:mm) 2003 001-003 58 00:58 004-019 59 00:59 020-029 60 01:00 030-038 61 01:01 039-045 62 01:02 046-052 63 01:03 053-059 64 01:04 060-066 65 01:05 067-072 66 01:06 073-078 67 01:07 079-084 68 01:08 085-091 69 01:09 092-097 70 01:10 098-104 71 01:11 105-111 72 01:12 112-118 73 01:13 119-126 74 01:14 127-134 75 01:15 135-144 76 01:16 145-156 77 01:17 157-177 78 01:18 178-205 79 01:19 206-226 78 01:18 227-239 77 01:17 240-249 76 01:16 250-258 75 01:15 259-267 74 01:14 268-275 73 01:13 276-283 72 01:12 284-291 71 01:11 292-300 70 01:10 301-308 69 01:09 309-317 68 01:08 318-328 67 01:07 329-342 66 01:06 343-365 65 01:05
DOY range OWLT start-end (min) (hh:mm) 2004 001-020 65 01:05 021-034 66 01:06 035-044 67 01:07 045-052 68 01:08 053-060 69 01:09 061-067 70 01:10 068-074 71 01:11 075-081 72 01:12 082-087 73 01:13 088-094 74 01:14 095-100 75 01:15 101-107 76 01:16 108-114 77 01:17 115-122 78 01:18 123-130 79 01:19 131-138 80 01:20 139-148 81 01:21 149-161 82 01:22 162-180 83 01:23 181-204 84 01:24 205-225 83 01:23 226-238 82 01:22 239-248 81 01:21 249-257 80 01:20 258-266 79 01:19 267-273 78 01:18 274-281 77 01:17 282-288 76 01:16 289-295 75 01:15 296-304 74 01:14 305-311 73 01:13 312-318 72 01:12 319-326 71 01:11 327-335 70 01:10 336-346 69 01:09 347-362 68 01:08 363-366 67 01:07
DOY range OWLT start-end (min) (hh:mm) 2005 001-031 67 01:07 032-046 68 01:08 047-057 69 01:09 058-066 70 01:10 067-075 71 01:11 076-083 72 01:12 084-089 73 01:13 090-097 74 01:14 098-104 75 01:15 105-112 76 01:16 113-119 77 01:17 120-127 78 01:18 128-135 79 01:19 136-143 80 01:20 144-154 81 01:21 155-166 82 01:22 167-183 83 01:23 184-225 84 01:24 226-243 83 01:23 244-255 82 01:22 256-265 81 01:21 266-274 80 01:20 275-282 79 01:19 283-290 78 01:18 291-297 77 01:17 298-305 76 01:16 306-312 75 01:15 313-319 74 01:14 320-327 73 01:13 328-335 72 01:12 336-344 71 01:11 345-353 70 01:10 354-365 69 01:09
DOY range OWLT start-end (min) (hh:mm) 2006 001 69 01:09 002-054 68 01:08 055-065 69 01:09 066-076 70 01:10 077-084 71 01:11 085-092 72 01:12 093-099 73 01:13 100-107 74 01:14 108-115 75 01:15 116-122 76 01:16 123-129 77 01:17 130-137 78 01:18 138-144 79 01:19 145-152 80 01:20 153-161 81 01:21 162-172 82 01:22 173-185 83 01:23 186-209 84 01:24 210-227 85 01:25 228-251 84 01:24 252-266 83 01:23 267-276 82 01:22 277-284 81 01:21 285-294 80 01:20 295-301 79 01:19 302-309 78 01:18 310-316 77 01:17 317-323 76 01:16 324-331 75 01:15 332-338 74 01:14 339-346 73 01:13 347-355 72 01:12 356-363 71 01:11 364-365 70 01:10
DOY range OWLT start-end (min) (hh:mm) 2007 001-010 70 01:10 011-028 69 01:09 029-056 68 01:08 057-073 69 01:09 074-085 70 01:10 086-093 71 01:11 094-102 72 01:12 103-110 73 01:13 111-118 74 01:14 119-125 75 01:15 126-132 76 01:16 133-139 77 01:17 140-146 78 01:18 147-155 79 01:19 156-162 80 01:20 163-171 81 01:21 172-181 82 01:22 182-193 83 01:23 194-210 84 01:24 211-257 85 01:25 258-274 84 01:24 275-285 83 01:23 286-296 82 01:22 297-303 81 01:21 304-311 80 01:20 312-320 79 01:19 321-327 78 01:18 328-334 77 01:17 335-341 76 01:16 342-349 75 01:15 350-356 74 01:14 357-365 73 01:13
DOY range OWLT start-end (min) (hh:mm) 2008 001-008 72 01:12 009-019 71 01:11 020-033 70 01:10 034-077 69 01:09 078-090 70 01:10 091-101 71 01:11 102-110 72 01:12 111-118 73 01:13 119-126 74 01:14 127-133 75 01:15 134-141 76 01:16 142-148 77 01:17 149-155 78 01:18 156-163 79 01:19 164-170 80 01:20 171-179 81 01:21 180-183 82 01:22
FOIA 10-JPL-F-00451
46 of 217
2002
Jan 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 016 017 018 019 020 021 022 023 024 025 026 027 028 029 030 031 DOW Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Feb 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 DOY 032 033 034 035 036 037 038 039 040 041 042 043 044 045 046 047 048 049 050 051 052 053 054 055 056 057 058 059 DOW Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Mar 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 060 061 062 063 064 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079 080 081 082 083 084 085 086 087 088 089 090 DOW Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Apr 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 091 092 093 094 095 096 097 098 099 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 DOW Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue May 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 DOW Jun DOY Wed 01 152 Thu 02 153 Fri 03 154 Sat 04 155 Sun 05 156 Mon 06 157 Tue 07 158 Wed 08 159 Thu 09 160 Fri 10 161 Sat 11 162 Sun 12 163 Mon 13 164 Tue 14 165 Wed 15 166 Thu 16 167 Fri 17 168 Sat 18 169 Sun 19 170 Mon 20 171 Tue 21 172 Wed 22 173 Thu 23 174 Fri 24 175 Sat 25 176 Sun 26 177 Mon 27 178 Tue 28 179 Wed 29 180 Thu 30 181 Fri DOW Jul DOY Sat 01 182 Sun 02 183 Mon 03 184 Tue 04 185 Wed 05 186 Thu 06 187 Fri 07 188 Sat 08 189 Sun 09 190 Mon 10 191 Tue 11 192 Wed 12 193 Thu 13 194 Fri 14 195 Sat 15 196 Sun 16 197 Mon 17 198 Tue 18 199 Wed 19 200 Thu 20 201 Fri 21 202 Sat 22 203 Sun 23 204 Mon 24 205 Tue 25 206 Wed 26 207 Thu 27 208 Fri 28 209 Sat 29 210 Sun 30 211 31 212 DOW Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Aug 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 DOW Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sep 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 DOW Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Oct 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 DOW Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Nov 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 DOW Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Dec 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 DOW Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue
FOIA 10-JPL-F-00451
47 of 217
2003
Jan 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 016 017 018 019 020 021 022 023 024 025 026 027 028 029 030 031 DOW Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Feb 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 DOY 032 033 034 035 036 037 038 039 040 041 042 043 044 045 046 047 048 049 050 051 052 053 054 055 056 057 058 059 DOW Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Mar 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 060 061 062 063 064 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079 080 081 082 083 084 085 086 087 088 089 090 DOW Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Apr 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 091 092 093 094 095 096 097 098 099 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 DOW Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed May 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 DOW Jun DOY Thu 01 152 Fri 02 153 Sat 03 154 Sun 04 155 Mon 05 156 Tue 06 157 Wed 07 158 Thu 08 159 Fri 09 160 Sat 10 161 Sun 11 162 Mon 12 163 Tue 13 164 Wed 14 165 Thu 15 166 Fri 16 167 Sat 17 168 Sun 18 169 Mon 19 170 Tue 20 171 Wed 21 172 Thu 22 173 Fri 23 174 Sat 24 175 Sun 25 176 Mon 26 177 Tue 27 178 Wed 28 179 Thu 29 180 Fri 30 181 Sat DOW Jul DOY Sun 01 182 Mon 02 183 Tue 03 184 Wed 04 185 Thu 05 186 Fri 06 187 Sat 07 188 Sun 08 189 Mon 09 190 Tue 10 191 Wed 11 192 Thu 12 193 Fri 13 194 Sat 14 195 Sun 15 196 Mon 16 197 Tue 17 198 Wed 18 199 Thu 19 200 Fri 20 201 Sat 21 202 Sun 22 203 Mon 23 204 Tue 24 205 Wed 25 206 Thu 26 207 Fri 27 208 Sat 28 209 Sun 29 210 Mon 30 211 31 212 DOW Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Aug 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 DOW Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Sep 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 DOW Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Oct 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 DOW Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Nov 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 DOW Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Dec 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 DOW Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed
FOIA 10-JPL-F-00451
48 of 217
2004
Jan 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 016 017 018 019 020 021 022 023 024 025 026 027 028 029 030 031 DOW Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Feb 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 DOY 032 033 034 035 036 037 038 039 040 041 042 043 044 045 046 047 048 049 050 051 052 053 054 055 056 057 058 059 060 DOW Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mar 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 061 062 063 064 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079 080 081 082 083 084 085 086 087 088 089 090 091 DOW Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Apr 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 092 093 094 095 096 097 098 099 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 DOW Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri May 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 DOW Jun DOY Sat 01 153 Sun 02 154 Mon 03 155 Tue 04 156 Wed 05 157 Thu 06 158 Fri 07 159 Sat 08 160 Sun 09 161 Mon 10 162 Tue 11 163 Wed 12 164 Thu 13 165 Fri 14 166 Sat 15 167 Sun 16 168 Mon 17 169 Tue 18 170 Wed 19 171 Thu 20 172 Fri 21 173 Sat 22 174 Sun 23 175 Mon 24 176 Tue 25 177 Wed 26 178 Thu 27 179 Fri 28 180 Sat 29 181 Sun 30 182 Mon DOW Jul DOY Tue 01 183 Wed 02 184 Thu 03 185 Fri 04 186 Sat 05 187 Sun 06 188 Mon 07 189 Tue 08 190 Wed 09 191 Thu 10 192 Fri 11 193 Sat 12 194 Sun 13 195 Mon 14 196 Tue 15 197 Wed 16 198 Thu 17 199 Fri 18 200 Sat 19 201 Sun 20 202 Mon 21 203 Tue 22 204 Wed 23 205 Thu 24 206 Fri 25 207 Sat 26 208 Sun 27 209 Mon 28 210 Tue 29 211 Wed 30 212 31 213 DOW Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Aug 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 DOW Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Sep 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 DOW Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Oct 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 DOW Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Nov 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 DOW Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Dec 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 DOW Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri
FOIA 10-JPL-F-00451
49 of 217
2005
Jan 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 016 017 018 019 020 021 022 023 024 025 026 027 028 029 030 031 DOW Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Feb 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 DOY 032 033 034 035 036 037 038 039 040 041 042 043 044 045 046 047 048 049 050 051 052 053 054 055 056 057 058 059 DOW Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Mar 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 060 061 062 063 064 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079 080 081 082 083 084 085 086 087 088 089 090 DOW Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Apr 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 091 092 093 094 095 096 097 098 099 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 DOW Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat May 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 DOW Jun DOY Sun 01 152 Mon 02 153 Tue 03 154 Wed 04 155 Thu 05 156 Fri 06 157 Sat 07 158 Sun 08 159 Mon 09 160 Tue 10 161 Wed 11 162 Thu 12 163 Fri 13 164 Sat 14 165 Sun 15 166 Mon 16 167 Tue 17 168 Wed 18 169 Thu 19 170 Fri 20 171 Sat 21 172 Sun 22 173 Mon 23 174 Tue 24 175 Wed 25 176 Thu 26 177 Fri 27 178 Sat 28 179 Sun 29 180 Mon 30 181 Tue DOW Jul DOY Wed 01 182 Thu 02 183 Fri 03 184 Sat 04 185 Sun 05 186 Mon 06 187 Tue 07 188 Wed 08 189 Thu 09 190 Fri 10 191 Sat 11 192 Sun 12 193 Mon 13 194 Tue 14 195 Wed 15 196 Thu 16 197 Fri 17 198 Sat 18 199 Sun 19 200 Mon 20 201 Tue 21 202 Wed 22 203 Thu 23 204 Fri 24 205 Sat 25 206 Sun 26 207 Mon 27 208 Tue 28 209 Wed 29 210 Thu 30 211 31 212 DOW Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Aug 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 DOW Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Sep 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 DOW Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Oct 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 DOW Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Nov 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 DOW Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Dec 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 DOW Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat
FOIA 10-JPL-F-00451
50 of 217
2006
Jan 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 016 017 018 019 020 021 022 023 024 025 026 027 028 029 030 031 DOW Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Feb 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 DOY 032 033 034 035 036 037 038 039 040 041 042 043 044 045 046 047 048 049 050 051 052 053 054 055 056 057 058 059 DOW Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Mar 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 060 061 062 063 064 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079 080 081 082 083 084 085 086 087 088 089 090 DOW Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Apr 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 091 092 093 094 095 096 097 098 099 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 DOW Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun May 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 DOW Jun DOY Mon 01 152 Tue 02 153 Wed 03 154 Thu 04 155 Fri 05 156 Sat 06 157 Sun 07 158 Mon 08 159 Tue 09 160 Wed 10 161 Thu 11 162 Fri 12 163 Sat 13 164 Sun 14 165 Mon 15 166 Tue 16 167 Wed 17 168 Thu 18 169 Fri 19 170 Sat 20 171 Sun 21 172 Mon 22 173 Tue 23 174 Wed 24 175 Thu 25 176 Fri 26 177 Sat 27 178 Sun 28 179 Mon 29 180 Tue 30 181 Wed DOW Jul DOY Thu 01 182 Fri 02 183 Sat 03 184 Sun 04 185 Mon 05 186 Tue 06 187 Wed 07 188 Thu 08 189 Fri 09 190 Sat 10 191 Sun 11 192 Mon 12 193 Tue 13 194 Wed 14 195 Thu 15 196 Fri 16 197 Sat 17 198 Sun 18 199 Mon 19 200 Tue 20 201 Wed 21 202 Thu 22 203 Fri 23 204 Sat 24 205 Sun 25 206 Mon 26 207 Tue 27 208 Wed 28 209 Thu 29 210 Fri 30 211 31 212 DOW Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Aug 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 DOW Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Sep 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 DOW Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Oct 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 DOW Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Nov 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 DOW Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Dec 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 DOW Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun
FOIA 10-JPL-F-00451
51 of 217
2007
Jan 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 016 017 018 019 020 021 022 023 024 025 026 027 028 029 030 031 DOW Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Feb 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 DOY 032 033 034 035 036 037 038 039 040 041 042 043 044 045 046 047 048 049 050 051 052 053 054 055 056 057 058 059 DOW Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Mar 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 060 061 062 063 064 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079 080 081 082 083 084 085 086 087 088 089 090 DOW Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Apr 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 091 092 093 094 095 096 097 098 099 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 DOW Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon May 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 DOW Jun DOY Tue 01 152 Wed 02 153 Thu 03 154 Fri 04 155 Sat 05 156 Sun 06 157 Mon 07 158 Tue 08 159 Wed 09 160 Thu 10 161 Fri 11 162 Sat 12 163 Sun 13 164 Mon 14 165 Tue 15 166 Wed 16 167 Thu 17 168 Fri 18 169 Sat 19 170 Sun 20 171 Mon 21 172 Tue 22 173 Wed 23 174 Thu 24 175 Fri 25 176 Sat 26 177 Sun 27 178 Mon 28 179 Tue 29 180 Wed 30 181 Thu DOW Jul DOY Fri 01 182 Sat 02 183 Sun 03 184 Mon 04 185 Tue 05 186 Wed 06 187 Thu 07 188 Fri 08 189 Sat 09 190 Sun 10 191 Mon 11 192 Tue 12 193 Wed 13 194 Thu 14 195 Fri 15 196 Sat 16 197 Sun 17 198 Mon 18 199 Tue 19 200 Wed 20 201 Thu 21 202 Fri 22 203 Sat 23 204 Sun 24 205 Mon 25 206 Tue 26 207 Wed 27 208 Thu 28 209 Fri 29 210 Sat 30 211 31 212 DOW Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Aug 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 DOW Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sep 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 DOW Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Oct 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 DOW Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Nov 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 DOW Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Dec 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 DOW Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon
FOIA 10-JPL-F-00451
52 of 217
2008
Jan 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 016 017 018 019 020 021 022 023 024 025 026 027 028 029 030 031 DOW Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Feb 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 DOY 032 033 034 035 036 037 038 039 040 041 042 043 044 045 046 047 048 049 050 051 052 053 054 055 056 057 058 059 060 DOW Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Mar 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 061 062 063 064 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079 080 081 082 083 084 085 086 087 088 089 090 091 DOW Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Apr 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 092 093 094 095 096 097 098 099 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 DOW Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed May 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 DOW Jun DOY Thu 01 153 Fri 02 154 Sat 03 155 Sun 04 156 Mon 05 157 Tue 06 158 Wed 07 159 Thu 08 160 Fri 09 161 Sat 10 162 Sun 11 163 Mon 12 164 Tue 13 165 Wed 14 166 Thu 15 167 Fri 16 168 Sat 17 169 Sun 18 170 Mon 19 171 Tue 20 172 Wed 21 173 Thu 22 174 Fri 23 175 Sat 24 176 Sun 25 177 Mon 26 178 Tue 27 179 Wed 28 180 Thu 29 181 Fri 30 182 Sat DOW Jul DOY Sun 01 183 Mon 02 184 Tue 03 185 Wed 04 186 Thu 05 187 Fri 06 188 Sat 07 189 Sun 08 190 Mon 09 191 Tue 10 192 Wed 11 193 Thu 12 194 Fri 13 195 Sat 14 196 Sun 15 197 Mon 16 198 Tue 17 199 Wed 18 200 Thu 19 201 Fri 20 202 Sat 21 203 Sun 22 204 Mon 23 205 Tue 24 206 Wed 25 207 Thu 26 208 Fri 27 209 Sat 28 210 Sun 29 211 Mon 30 212 31 213 DOW Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Aug 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 DOW Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Sep 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 DOW Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Oct 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 DOW Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Nov 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 DOY 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 DOW Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Dec 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 DOY 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 DOW Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed
FOIA 10-JPL-F-00451
53 of 217
SECTION 3 SCIENCE OBJECTIVES 3.1 GENERAL OBJECTIVES The Cassini mission will accomplish a variety of scientific objectives on its way to Saturn and after arrival. The science investigation objectives are defined in the Project Policies and Requirements document, PD 699-004, and are summarized below. Pre-Saturn. One-time instrument checkouts (at Launch + 14 months), instrument maintenance, gravitational wave searches (during the three successive oppositions beginning Dec 2001), and instrument calibrations, limited cruise science, and Saturn approach science (after SOI minus 2 years) will be conducted. Saturnian System. The general scientific objectives of the Cassini mission are to investigate the physical, chemical, and temporal characteristics of Titan and of Saturn, its atmosphere, rings, icy satellites, and magnetosphere. 3.2 SPECIFIC OBJECTIVES BEFORE SATURN En Route Gravitational Wave Experiment. While en route to Saturn, Cassini shall perform gravitational wave experiments near at least three oppositions and for a time period of at least 40 days each. DSS-25 (X & Ka) required at Goldstone. DSS-45 (X) and DSS-65 (X) required at Canberra and Madrid. En Route Conjunction Experiment. While en route to Saturn, Cassini shall perform conjunction experiments near at least two solar conjunctions and for a time period of at least 30 days. DSS25 (X & Ka) requierd at Goldstone. DSS-45 (X & S) and DSS-65 (X & S) required at Canberra and Madrid. The objective of this experiment is to conduct tests of general relativity and study the solar corona. 3.3 SPECIFIC OBJECTIVES AT SATURN Saturn Objectives. Specific Cassini objectives for planetary science are to: Determine temperature field, cloud properties, and composition of the a) atmosphere of Saturn. b) Measure the global wind field, including wave and eddy components; observe synoptic cloud features and processes. c) Infer the internal structure and rotation of the deep atmosphere. d) Study the diurnal variations and magnetic control of the ionosphere of Saturn. e) Provide observational constraints (gas composition, isotope ratios, heat flux, etc.) on scenarios for the formation and the evolution of Saturn. f) Investigate the sources and the morphology of Saturn lightning (Saturn Electrostatic Discharges (SED), lightning whistlers). 3.4 SPECIFIC OBJECTIVES AT TITAN Titan Objectives. Specific Cassini objectives for Titan science are to: Determine abundance of atmospheric constituents (including any noble gases), a) establish isotope ratios for abundant elements, constrain scenarios of formation and evolution of Titan and its atmosphere. b) Observe vertical and horizontal distributions of trace gases, search for more complex organic molecules, investigate energy sources for atmospheric chemistry, and model the photochemistry of the stratosphere, study formation and composition of aerosols. c) Measure winds and global temperatures; investigate cloud physics, general circulation, and seasonal effects in Titan's atmosphere; search for lightning discharges. d) Determine the physical state, topography, and composition of the surface; infer the internal structure of the satellite. 3-1
54 of 217
e) 3.5
Investigate the upper atmosphere, its ionization, and its role as a source of neutral and ionized material for magnetosphere of Saturn. SPECIFIC OBJECTIVES AT THE RINGS
Ring Objectives. Specific Cassini objectives for Ring Science are to: Study configuration of the rings and dynamical processes (gravitational, viscous, a) erosional, and electromagnetic) responsible for ring structure. b) Map composition and size distribution of ring material. c) Investigate interrelation of rings and satellites, including imbedded satellites. d) Determine dust and meteoroid distribution in the vicinity of the rings. e) Study interactions between the rings and Saturn's magnetosphere, ionosphere, and atmosphere. 3.6 SPECIFIC OBJECTIVES AT THE ICY SATELLITES Icy Satellite Objectives. Specific Cassini objectives for Icy Satellite Science are to: Determine the general characteristics and geological histories of the satellites. a) b) Define the mechanisms of crustal and surface modifications, both external and internal. c) Investigate the compositions and distributions of surface materials, particularly dark, organic rich materials and low melting point condensed volatiles. d) Constrain models of the satellites' bulk compositions and internal structures. e) Investigate interactions with the magnetosphere and ring systems and possible gas injections into the magnetosphere. 3.7 SPECIFIC OBJECTIVES AT THE SATURN MAGNETOSPHERE Magnetosphere Objectives. Specific Cassini objectives for Magnetosphere Science are to: Determine the configuration of the nearly axially symmetric magnetic field and a) its relation to the modulation of Saturn Kilometric Radiation (SKR). b) Determine current systems, composition, sources, and sinks of magnetosphere charged particles. c) Investigate wave-particle interactions and dynamics of the dayside magnetosphere and the magnetotail of Saturn and their interactions with the solar wind, the satellites, and the rings. d) Study the effect of Titan's interaction with the solar wind and magnetospheric plasma. e) Investigate interactions of Titan's atmosphere and exosphere with the surrounding plasma. 3.8 ORBITER SCIENCE INSTRUMENTS There are 12 science instrument subsystems on the Cassini spacecraft. The science instruments are listed and their measurement objectives described in this section. Three of the instruments are capable of some limited motion (articulation) independent of the spacecraft pointing: CAPS, CDA, and MIMI/LEMMS. The science instrument subsystems are divided into three groups: Magnetosphere & Plasma Science (MAPS), Optical Remote Sensing (ORS), and microwave sensing. MAPS instruments include CAPS, CD, INMS, MAG, MIMI, and RPWS. The ORS instruments include CIRS, ISS, UVIS, and VIMS. Microwave sensing instruments are RADAR and RSS. 3.8.1 CASSINI PLASMA SPECTROMETER (CAPS) The CAPS instrument is designed to perform an in-situ study of plasma within and near Saturns magnetosphere. Specific science objectives for the Cassini mission are as follows. 1) Orbital Tour Observing Objectives: a) Near continuous survey. 3-2
55 of 217
b) c) d)
MAPS Campaigns. SOI, targeted Titan and icy satellite observations. CAPS Magnetospheric Survey.
2) Solar Wind/Aurora Campaign Objectives: a) Measure solar wind while ORS observes aurora. b) Unambiguous measurements of unperturbed solar wind, correlation with Earth based and RPW auroral data. 3) Study microphysical and rapidly varying processes near the bow shock and magnetopause. 4) Observe particle acceleration, particle injection, and dynamical events (e.g. substorms) in the magnetotail. 5) Measure vertical (field aligned) structure of plasma in the inner magnetosphere. 6) Observe the dynamics and microphysics of the auroral and Saturn Kilometric Radiation (SKR) source regions. 7) Study the Titan plasma torus and distant signatures of Titans interaction with the magnetosphere. 8) Study the distant signatures of satellites and ring interactions with the magnetosphere. 3.8.2 COSMIC DUST ANALYZER (CDA) The CDA instrument is designed to perform an in-situ study of dust grains in the Saturn system. Specific science objectives for the Cassini mission are as follows. 1) Study interplanetary and interstellar dust at Saturn. 2) Saturn Rings Objectives: a) Map size distribution. b) Search for particles in the clear zone (F/G ring). c) Determine orbits of particles to identify their possible parents. d) Study the interaction between E ring and Saturn's magnetosphere. e) Distinguish temporal and spatial effects. f) Analyze eccentricity and inclination of dust orbits independently. 3) Icy Satellites Objectives: a) Interaction with the ring system. b) Role of satellites as a source and sink for ring particles. c) Chemical composition of satellites (dust atmospheres). 3.8.3 COMPOSITE INFRARED SPECTROMETER (CIRS) The CIRS instrument is designed to perform spectral mapping to study temperature and composition of surfaces, atmospheres, and rings within the Saturn system. Specific science objectives for the Cassini mission are as follows. 1) Thermal Structure Objectives: a) Vertical profiles of atmospheric temperature. b) Maps of atmospheric and surface temperatures. c) Aerosol opacities. d) Thermal inertia of surfaces. e) Subsurface regolith structure. f) Ring particle sizes. g) Ring thermal structure. 2) Composition Objectives: a) Spatial distribution of atmospheric gases. b) Surfaces. 3-3
56 of 217
c)
Ring material.
3) Atmosphere Objectives: a) Circulation: Zonal jets, Meridional motion, vortices, wave, convection. b) Composition: Dis-equilibrium species, elemental and isotope abundances and distribution, ortho/para ratio, condensable gases, external sources (e.g., rings). c) Clouds/Aerosols: Composition, microphysical properties, spatial and temporal distribution. d) Atmospheric. Structure: Temperature, pressure, density, vertical distribution of major constituents. e) Internal Structure: He abundance, internal heat, gravity. f) Aurora, lighting, airglow: Spatial and temporal distribution, special properties. g) Titan: Aerosols and clouds, Titan winds. 4) Rings Objectives: a) Vertical structure and thermal gradient. b) Vertical Dynamics. c) Particle Surface Properties. d) Particle Composition. e) Radial Structure. 5) Non-Targeted Icy Satellites Objectives: a) Determine surface composition. b) Determine vertical thermal structure (Greenhouse). c) Determine thermophysical properties (Thermal Inertia). d) Search for active thermal sources (space and time). 3.8.4 ION AND NEUTRAL MASS SPECTROMETER (INMS) The INMS instrument is designed to perform an in-situ study of compositions of neutral and charged particles within the Saturn magnetosphere. Specific science objectives for the Cassini mission are as follows. 1) Outer Magnetosphere: Science Objectives: a) Neutral and ion composition of the magnetosphere. b) Composition of the Titan plasma torus. c) Additional low energy ion distribution function information to complement CAPS. 2) Inner Magnetosphere: Science Objectives: a) Studies of solar system formation. Plasma sources derived from the rings and icy satellites composition and isotopic ratio. b) Studies of plasma transport. Determination of plasma transport velocities and determination of momentum transfer from charge exchange chemistry water products. 3.8.5 IMAGING SCIENCE SUBSYSTEM (ISS) The ISS instrument is designed to perform multispectral imaging of Saturn, Titan, rings, and icy satellites to observe their properties. Specific science objectives for the Cassini mission are as follows. 1) Motions and Dynamics: a) Basic flow regime (Titan). b) Poleward flux of momentum (uv). c) Poleward flux of heat (with CIRS). d) Life cycles and small-scale dynamics of eddies. e) Radiative heating for dynamical studies. 3-4
57 of 217
2) Clouds and Aerosols: Could and haze stratigraphy (strongly couples with wind studies). a) b) Particle optical properties. c) Particle physical properties. d) Auroral processes and particle formation. e) Haze microphysical models. 3) Lightning (related to water clouds on Saturn, dont know what to expect for Titan). 4) Auroras (H and H2 emissions on Saturn, N and N2 emissions on Titan). 5) ISS High Priority Rings Goals: a) Ring Architecture/Evolution: Azimuthal, radial, temporal variations across tour. b) New satellites: orbits, masses/densities, effects on rings; complete inventory of Saturns inner moons. c) Search and characterize material potentially hazardous to Cassini: diffuse rings, arcs, Hills sphere material, etc. d) Orbit refinement of known satellites; temporal variations; resonant effects. e) Particle/Disk properties: vertical disk structure; particle physical properties and size distribution; variations across disk. f) Spokes: Formation timescales/process; periodic variations. g) Diffuse Rings (E, G): Structure, characterize particle properties. 3.8.5 MAGNETOMETER (MAG) The MAG instrument is designed to study Saturns magnetic field and interactions with the solar wind. Specific science objectives for the Cassini mission are as follows. 1) Intrinsic magnetic fields of Saturn and its moons: a) Determine the multiple moments of Saturns dynamo-driven magnetic field. b) Determine weather Titan has an internal field due to dynamo action, electromagnetic induction or even remnant magnetization in a dirty ice crust. c) Search for possible evidence of ancient dynamos and crustal remanance in the icy satellites. 2) Derive a 3-D global model of the magnetospheric magnetic field. 3) Establish the relative contributions to electromagnetic and mechanical stress balance. 4) Identify the energy source for dynamical processes (rotationally driven, solar wind driven, or other). 5) Characterize the phenomena of the distant dayside/flank planetary environment. 6) Survey satellite/dust/ring/torus electromagnetic interactions. 7) Determine tail structure and dynamic processes therein. 8) Establish nature and source of all ULF wave sources. 9) Magnetosphere/ionosphere coupling. 10) Titan: a) b) c) d) Determine the internal magnetic field sources of Titan as well as the sources external to I I thereby determining the interaction type. Determine all Titan-plasma flow interactions (magnetosphere, magnetosheath, solar wind). Determine the variation of the Titan-magnetosphere interaction with respect to Titan orbital phase. Determine the nature of the low frequency wave (ion cyclotron/hydromagnetic) spectrum of the near-Titan plasma environment. 3-5
58 of 217
11) Icy Satellites: Search for possible evidence of ancient dynamos and crustal remanence in the icy a) satellites b) Investigate icy satellite plasma environments. 3.8.6 RADIO SCIENCE SUBSYSTEM (RSS) The RSS is designed to study atmospheres and ionospheres of Saturn, Titan, rings, and gravity fields of Saturn and its satellites (also, search for gravitational waves during cruise). Specific science objectives for the Cassini mission are as follows. 1) Ring Occultations: a) To profile radial ring structure with resolution <= 100m; characterize structure variability with azimuth, wavelength, ring-opening-angle, and time. b) To determine the physical particle properties (size distribution, bulk density, surface density, thickness, viscosity). c) To study ring kinematics and dynamics (morphology, interaction with embedded and exterior satellites), and to investigate ring origin and evolution. 2) Atmospheric Occultations: a) To determine the global fields of temperature, pressure, and zonal winds in the stratosphere and troposphere of Saturn. b) To determine the small scale structure due to eddies and waves. c) To determine the latitudinal variations of NH3 abundance in Saturns atmosphere. d) To improve the knowledge of H2 /He ratio in Saturns troposphere (RSS+CIRS). 3) Ionospheric Occultations: a) To determine the vertical profiles of the electron density in Saturns terminator ionosphere, and its variability with latitude. b) To investigate interaction of the ionosphere with Saturns magnetosphere and Saturns rings. 4) Gravity Field of Saturn: a) To determine the mass of Saturn and zonal harmonic coefficients of its gravity field to at least degree 6 (J2 , J4 , J6 ). b) To constrain models of Saturns interior based on the results 5) Gravity Field and Occultation of Untargeted Satellites: a) To determine the masses of Mimas, Tethys, Dione, Hyperion, and Phoebe. b) To search for a possible tenuous ionosphere around any occulted satellites (a la Europa and Callisto). 3.8.7 ULTRAVIOLET IMAGING SPECTROGRAPH (UVIS) The UVIS instrument is designed to produce spatial UV maps, map ring radial structure, and to determine hydrogen/deuterium ratios. Specific science objectives for the Cassini mission are as follows. 1) Saturn System Scans: a) EUV and FUV low resolution spectra of magnetosphere neutral and ion emissions. b) System scans at every apoapsis. 2) Satellites: a) Latitude, longitude and phase coverage coordinated through SSWG. b) Distant stellar occultations to determine satellite orbits and Saturn reference frame. 3) Atmosphere: 3-6
59 of 217
a) b) c) d)
Vertical profiles of H, H2, hydrocarbons, temp in exo, thermosphere. Long integrations map of hydrocarbons, airglow. Map emissions with highest resolution at the limb. Auroral Map: H and H2 emissions over several rotations.
4) Ring Stellar Occultation Objectives: a) Highest Radial resolution (20m) structure of rings b) Discovery and precise characterization of dynamical features generated by ringsatellite interactions. - Density waves and bending waves. - Edge waves and ring shepherding. - Embedded moonlets and discovery of new moons from dynamical response in rings. c) Discovery and precise characterization of azimuthal structure in rings. - Eccentric rings. - Density waves and edge waves. - Small-scale self-gravitational clumping in rings. d) Measure temporal variability in ring structure. e) Simultaneously measure UV reflectance spectrum of rings. - Determine microstructure on particle surfaces. - Compositional information on ring particles. f) Measure size distribution of large particles through occultation statistics. g) Measure dust abundance in diffraction aureole. h) Simultaneously search for flashes from 0.1 m 1.0 m meteoroid impacts. 3.8.8 VISIBLE AND INFRARED MAPPING SPECTROMETER (VIMS) The VIMS instrument is designed to produce spectral mapping to study the composition and structure of surfaces, atmospheres, and rings. Specific science objectives for the Cassini mission are as follows. 1) Ring Observation: a) Determine ring composition and its spatial variations. b) Determine light scattering behavior of rings as a function of I, e, and . c) Constrain sizes and surface textures of ring particles. d) Establish optical depth profile of rings as a function of wavelength, incidence angle, and longitude. e) Characterize variable features such as non-circular ringlets, F ring, spokes, etc., and their evolution. f) Ring moon compositions. 2) Icy Satellite Observation: a) Measure UV and NIR spectra to: - Identify and map surface materials at the highest spatial resolution. - Determine microphysical surface properties. - Provide data on energy balance. 3.8.10 RADAR RADAR is designed for synthetic aperture RADAR (SAR) imaging, altimetry, and radiometry of Titans surface. Specific science objectives for the Cassini mission are as follows. 1) Rings: a) b) c) d) e) Determine scattering properties of rings. Determine ring global properties. Determine additional thermal and compositional properties of rings. Extended ring global properties: low-elevation measurements. Radial scans through optically thin rings (E, F and G). 3-7
60 of 217
f)
Identify thermal component.
2) Catalog of each satellites base radar/radiometric properties and their degree of global variation. 3.8.11 RADIO AND PLASMA WAVE SPECTROMETER (RPWS) The RPWS instrument is designed to study plasma waves, radio emissions, and dust in the Saturn system. Specific science objectives for the Cassini mission are as follows. 1) Aurora and SKR: Obtain radio and plasma wave data which provide information on the SKR source and plasma waves on auroral field lines. 2) Satellite and ring interactions: Measure dust flux, look for effects of selective absorption of electrons and ions near rings (thermal anisotropy), multi-ion wave particle interactions, satellite torii. 3) Inner Magnetosphere: Wave particle interactions via ULF waves; Stability of trapped electrons and relation to whistler-mode emissions; ECH (N+ _)fce waves trapped near the equatorial region and heating of cool electrons. 4) Titan Interactions: Multi-ion species wave-particle interactions; Evidence of Titan plumes/detached plasma blobs. 5) Magnetospheric Boundaries: Nature of the Saturnian Bow shock: Look for the signatures of waves accelerating electrons. 6) What is the nature of Saturns magetotail? Are there substorms or other dynamical processes there? 7) Observe lightning via SED and whistlers from Saturns atmosphere and possible Titans. 8) Determine the equatorial dust flux and scale height as a function of radial distance. 9) Provides for mapping and synoptic measurements required for the RPWS portion of the magnetospheric survey. 10) Search for electromagnetic phenomena which may be triggers of ring spokes. 3.8.12 MAGNETOSPHERIC IMAGING INSTRUMENT (MIMI) MIMI is designed for global magnetospheric imaging and in-situ measurements of Saturns magnetosphere and solar wind interactions. Specific science objectives for the Cassini mission are as follows. 1) MIMI Survey: a) What is the source of energetic particles in Saturn's magnetosphere and how are they energized? b) To what extent does the solar wind and rotation regulate the size, shape and dynamics of Saturn's magnetosphere; are there Earth-like storms and substorms? c) How does the interaction between the magnetospheric particle population and Saturn cause the aurora, and affect magnetospheric and upper atmospheric processes? d) How does the distribution of satellites affect global magnetospheric morphology and processes? 2) MIMI Campaigns: a) How do satellites and their exospheres affect local magnetospheric plasma flow and contribute to energetic particle populations? b) What particles (species, energy) cause Saturnian aurora; what processes accelerate them and what is the exospheric response? c) What unique role do Saturn's rings play in controlling the structure, composition, and transport of the inner magnetosphere? 3-8
61 of 217
3.9 HUYGENS PROBE INSTRUMENTS This section describes the Huygens Probe science objectives at Titan. 3.9.1 AEROSOL COLLECTOR PYROLYZER (ACP) The ACP is designed to perform in-situ study of clouds and aerosols in the Titan atmosphere. Specific science objectives for the Huygens Probe are as follows. 1) Determine the chemical makeup of the photochemical aerosol. 2) Obtain the relative abundance of condensed organics in a column average throughout the stratosphere. Compare with the abundance of constituent molecules in the aerosol nucleation sites. 3) Obtain the relative abundance of condensed organics in a column averaged over the upper troposphere. Compare with the abundance of constituent molecules in the aerosol nucleation sites. 3.9.2 GAS CHROMATOGRAPH AND MASS SPECTROMETER (GCMS) The GCMS is designed to perform in-situ measurement of the chemical composition of gases and aerosols in Titans atmosphere.Specific science objectives for the Huygens Probe are as follows. 1) Determine atmospheric composition of Titan including argon, isotopes and organic compounds. 2) Characterize conditions near the ground, especially to search for evidence of the vapor phases of possible surface condensates. 3) Surface Science a) If Huygens lands in a liquid: Mass spectra of evaporating liquid showing the relative abundance of nitrogen, ethane, methane, argon and other noble gases, simple hydrocarbons, nitriles and oxides. b) If Huygens lands in a deposit of aerosols: Determine the level of chemical complexity achieved by chemical synthesis in the atmosphere, as even rare aerosols may accumulate in measurable concentrations on the surface. c) If Huygens lands on exposed ice: Measurement of H2 O ice bedrock and search for condensed CO2 . 3.9.3 DESCENT IMAGER AND SPECTRAL RADIOMETER (DISR) The DISR is designed to measure aerosol and cloud optical properties and to perform spectroscopy measurements of Titans atmosphere and surface. Specific science objectives for the Huygens Probe are as follows. 1) Measure the solar heating rates vertical profile. 2) Measure distribution and properties of aerosol and cloud particles. 3) Determine the surfaces physical state (solid or liquid) near the impact site, and determine its fraction in each state. 4) Determine the composition of the atmosphere. 3.9.4 DOPPLER WIND EXPERIMENT (DWE) The DWE is designed to study winds from the effect it has on the Probe during Titan descent. Specific science objectives for the Huygens Probe are as follows. 1) Determining height profile of the wind velocity by measuring drift motions due to winds. 2) Measurement of Doppler fluctuations to determine the level and spectral index of turbulence and possible wave activity in Titans atmosphere. 3-9
62 of 217
3) Measurement of Doppler and signal level modulation to monitor Probe descent dynamics, including its rotation rate and phase, parachute swing and post-impact status. 3.9.5 HUYGENS ATMOSPHERIC STRUCTURE INSTRUMENT (HASI) The HASI is designed to perform in-situ study of Titan atmospheric physical and electrical properties. Specific science objectives for the Huygens Probe are as follows. 1) Determine the density, pressure, and temperature conditions of the atmospheres higher regions during entry. 2) Measure the stratospheric density, T and p profiles during the descent phase; identify the trace constituents that condense in this part of the atmosphere. 3) Measure the T and p condition in the lower troposphere and determine the existence and the extent of a convective zone. 4) Determine the nature of the surface. 5) Determine atmospheric electrical conductivity and investigate ionization processes, wave electric fields and atmospheric lightning. 6) Determine the surfaces large-scale and small-scale topography and the surfaces dielectric properties to distinguish, in particular, between a liquid and a solid surface before impact. 3.9.6 SURFACE SCIENCE PACKAGE (SSP) The SSP is designed to measure the physical properties of Titans surface and related atmospheric properties. Specific science objectives for the Huygens Probe are as follows. 1) Determine the physical nature and condition of Titans surface at the landing site. 2) Determine the abundance of major ocean constituents, placing bounds on atmospheric and ocean evolution. 3) Measure the thermal, optical, acoustic and electrical properties and density of any ocean, providing data to validate physical and chemical models. 4) Determine wave properties and ocean/atmospheric interactions. 5) Provide ground truth for interpreting the large-scale Orbiter Radar Mapper and other experimental data.
3-10
63 of 217
SECTION 4 FLIGHT SYSTEM DESCRIPTIONS This section contains a description of the Cassini Flight System. The Flight System consists of the launch vehicle & upper stage, the launch vehicle adapter, the Orbiter, and the Huygens Probe and Probe support equipment. 4.1 LAUNCH VEHICLE DESCRIPTION The Cassini spacecraft was injected into the interplanetary trajectory to Saturn by the Titan IV/SRMU/Centaur launch system. The launch was from the Cape Canaveral Air Station (CCAS) launch complex 40. The Titan IV flight vehicle is an integrated launch system consisting of a two-stage Titan IV core vehicle, two solid rocket motor upgrades, a Centaur upper stage and a 20 meter-long payload fairing. The Titan IV booster consisted of a core vehicle with Aerozine-50/N2 04 propellants and two 3segmented SRMUs as strap-ons, depicted in Table 4.1. Aerozine-50 is a 50/50 mix of unsymmetrical dimethylhydrazine and hydrazine. The upper stage wide body Centaur is a versatile high energy cryogenic upper stage with two Pratt and Whitney RL10A-3-3A multiple start engines. Table 4.1 Cassini Titan IV Launch System Description 1 2 3 4 5 6 7 8 Payload Fairing (McDonnell Douglas) Cassini Spacecraft (JPL) Guidance and Navigation (Honeywell) Centaur Upper Stage (Lockheed Martin) Titan IVB Lower Stage (US Air Force/Lockheed Martin) Liquid-Propellant Rockets: Stage I & II (Lockheed Martin) Stage I & II Engines (Aerojet) Solid-Propellant Rocket Motors (Alliant Techsystems)
The Titan IV/Centaur is a US Air Force launch system and was procured by the NASA Expendable Launch Vehicle Office for the Cassini mission. The NASA Lewis Research Center Launch Vehicle Project Office was responsible for overseeing the integration of the spacecraft with the launch vehicle. The Lockheed Martin Corporation was the USAF prime contractor for the launch system. The Titan IV/SRMU/Centaur performance for the Cassini mission was 4-1
64 of 217
tied to the USAF and MMC contractual agreement of placing 5760 kg payload in a geostationary orbit. 4.2 ORBITER DESCRIPTION The Cassini spacecraft is a three-axis-stabilized spacecraft, depicted in figure 4.1. The origin of the Orbiter coordinate system lies at the center of the field joint between the Bus and the Upper Equipment Module Upper Shell Structure Assembly. The Z-axis emanates from the origin and is perpendicular to a plane generated by the mating surfaces of the Bus. The +Z-axis is on the propulsion module side of the interface. The Z axis is aligned with the mechanical boresight fo the high gain antenna. The X-axis emanates from the origin The -X-axis points toward the Huygens Probe. The Y-axis is mutually perpendicular to the X and Z axes, with the +Y axis oriented along the magnetometer boom. The remote sensing pallet is mounted on the +X side of the spacecraft, the mag boom extends in the +Y direction, and the +Z axis completes the orthogonal body axes in the direction of the main engine. The primary remote sensing boresights view in the -Y direction, the probe will be ejected in the -X direction, the HGA boresight is in the -Z direction, the main engine exhaust is in the +Z direction with the thrust in the -Z direction. Two important directions to bear in mind are the HGA placement in the minus Z direction and the remote sensing instrument boresights along the minus Y direction. The rotational motion of the spacecraft about the coordinate system axes is commonly called simply a turn. The terms roll, pitch and yaw are generally discouraged because of possible ambiguity of the axis specified. However, roll, pitch and yaw are defined about the +Z, +Y, and +X directions respectively. The right-hand rule is used as to directions, e.g. during a positive roll while on Earth-line, the spacecraft will be spinning clockwise as seen from the Earth. (Point the right thumb along the +Z direction, i.e. along the main engines in this case away from the Earth. The fingers of the right hand indicate the direction of rotation as they curl closed in this case, clockwise looking from the Earth.) The main body of the spacecraft is formed by a stack consisting of the lower equipment module, the propulsion module, the upper equipment module, and the HGA. Attached to this stack are the remote sensing pallet, the fields and particles pallet, and the Huygens Probe system. The two equipment modules are also used for external mounting of the magnetometer boom and the three radioisotope thermoelectric generators (RTGs) which supply the spacecraft power. The spacecraft electronics bus is part of the upper equipment module and carries the electronics to support the spacecraft data handling, including the command and data subsystem and the radio frequency subsystem. The Spacecraft stands 6.8 meters (22.3 ft) high. Its maximum diameter, the diameter of the HGA, is 4 meters (13.1 ft). Therefore, the HGA can fully shield the rest of the spacecraft (except the deployed MAG boom and RPWS antennas) from sunlight when the HGA is pointed within 2.5 of the Sun. The dry mass of the spacecraft is 2523 kg, including the Huygens Probe system and the science instruments. The best estimate of the actual spacecraft mass at separation from the Centaur was 5573.8 kg. The spacecraft mass properties are listed in Table 4.2. 4.2.1 S/C ATTITUDE DEFINITION
The spacecraft orientation in inertial space is always defined with respect to the basebody attitude. All changes to the attitude are referenced with respect to the basebody attitude. The base attitude is specified by defining two pairs of vectors; two local vectors in the S/C body coordinate system and two inertial vectors in the J2000 inertial system. From each of these pairs, one of the vectors is termed the primary vector and the other is termed the secondary vector. 4-2
65 of 217
Mission phase BOM Before SOI Before Probe Release After Probe Release EOM
S/C Information
Table 4.2 Spacecraft Mass Properites Mass Xcm Ycm Zcm IXX
(kg) (m) (m) (m)
IYY
(kg-m 2)
IZZ
(kg-m 2)
(kg-m 2)
Huygens attached, Mag boom stowed, RPWS antennas stowed. Huygens attached, Mag boom deployed, 2 RPWS antennas deployed. Huygens attached, Mag boom deployed, 2 RPWS antennas deployed. Huygens released, Mag boom deployed, 2 RPWS antennas deployed. Huygens released, Mag boom deployed, all RPWS antennas deployed.
5573.8 4640.8 3306.8 2986.8 2452.8
-0.02 -0.03 -0.04 0.11 0.13
-0.01 0.02 0.03 0.03 0.06
1.33 1.36 1.30 1.27 1.14
8553.0 8758.9 7669.2 7505.5 6864.4
8846.8 8128.2 7045.0 6288.5 5719.5
3820.3 4650.9 4383.3 3665.9 3553.5
The base attitude shall be that attitude which satisfies the following two relationships: The primary body vector is pointing in the same direction as the primary inertial vector; The angle between the secondary body vector and the secondary inertial vector is minimized. Typically the primary body vector will be an instrument boresight and the primary inertial vector will be observation target. The secondary vectors are chosen to provide a preferertial attitude for satisfying (thermal) constraints or optimizing other aspects of the investigation. For example, the NAC boresight and the Z-axis could be the primary and secondary body vectors, respectively, while the S/C to Titan vector and the normal to the Titan flyby trajectory plane could be the primary and secondary inertial vectors, respectively. This would produce a continually changing attitude that points the NAC at Titan by rotating about the Z-axis. The "base" attitude is the spacecraft attitude that aligns one body vector with one inertial vector and places a second body vector as close as possible in alignment to a second inertial vector. The unit vectors XBASE, YBASE and ZBASE are fixed in the base coordinate frame. The spacecraft X, Y and Z axes are parallel to XBASE, YBASE and ZBASE, respectively, when the spacecraft is at the base attitude with zero offset. The user-selected body vectors must be members of the Body Vector Table (BVT). The user-selected inertial vectors must all be members of the Inertial Vector Table (IVT). If the chosen body vector does not exist in the BVT or the chosen inertial vector can not be constructed from entries in the IVT, the command to specify the base attitude is rejected. The base attitude is specified by the 7TARGET command. The 7TARGET command basically answers the question: "What do you want to point and where ?" 4.2.2 ATTITUDE COMMANDING Attitude offset shall be commanded by specifying a 'rotation' vector in base attitude coordinates or in the S/C basebody coordinates which determines the axis (vector direction) and angle (vector magnitude) of rotation necessary to achieve the offset. The commanded offset rotation axis may be specified in the base attitude or the body attitude coordinates. Attitude Commander allows for both types of offsets. Primary and secondary inertial vectors shall be selected by name from Inertial Vector Propagator entries. Commanded changes to the selection of basebody and/or inertial vectors (not the vector values) shall not be effective until the first subsequent offset rotation command. That offset command shall be with respect to the most recently selected basebody and inertial vectors. 4-3
66 of 217
The basebody commander shall accept absolute and relative turn commands. For absolute commands, the basebody commander shall generate the shortest vector turn between the current attitude and a newly commanded offset with respect to the base attitude such that conditions 1, 2, and 3 below are met during the transition. For relative commands, such as spin or turns that are larger than half a revolution, the basebody commander shall accept a turn (or spin) vector, consisting of a turn axis and a turn angle. It will then generate a turn profile between the current attitude and a newly computed offset (with respect to the base attitude) such that the following conditions during the turn are met: (1) The attitude offset with respect to the base attitude (not the attitude with respect to inertial space) rotates predictably about an axis relative to the base attitude; (2) The commanded attitude offset profile is composed of an acceleration phase, an optional constant rate coast phase (if coast rate is reached), and a deceleration phase; and (3) The offset rotation rate with respect to the base attitude reaches zero when the newly commanded offset is achieved. The peak acceleration/deceleration and coast rate of such a turn profile shall be commandable parameters and shall take effect only at the initiation of the next turn profile. Updates to basebody, inertial, and offset vectors, changes in the selections of basebody and inertial vectors, and changes in turn rate profile parameters shall be independently commandable. Other than the inertial and basebody vectors, all other updates shall take effect only at the initiation of the next turn profile. 4.2.3 INERTIAL VECTOR PROPAGATION The Inertial Vector Propagator (IVP) propagates relative inertial positions and velocities between two objects (which may be spacecraft or inertial), e.g. Sun and Earth, Earth and Moon, Sun and Saturn, Saturn and Titan, Titan and spacecraft etc. The propagated vectors are maintained in the Inertial Vector Table (IVT). This table can simultaneously maintain several inertial vectors, a subset of which is generally required to support science instrument pointing, antenna pointing, star tracker pointing, thrust vector pointing, constraint enforcement etc. Although there is no algorithmic restriction, the users (other AACS software objects) generally ask IVP for spacecraft-relative position and velocity vectors. The user may ask IVP for vectors between any two distinct objects propagated by IVP. The Inertial Vector Propagator will add or subtract the required relative vectors (components) to calculate the position and velocity vectors between the user-specified end points. The component vectors are propagated separately and one component may figure in several user requests. The component vectors form a tree, termed the inertial vector "tree". Three types of vector propagation are possible in IVP -- Fixed (time-invariant), Conic (timevarying) and Polynomial (time-varying). The determination of which type is suited best for a particular vector is based on fits carried out on the ground. The Inertial Vector Propagator must be provided with either fixed vectors or sets of propagation constants, each set describing the time-dependent motion of a single component vector. Component vectors need not all be based at the spacecraft. For instance, one set of propagation constants might specify the motion of Saturn with respect to the Sun while other defines the motion of Titan around Saturn. The Body Vector Table (BVT) resident in IVP stores various spacecraft boresights in the AACS body-fixed reference coordinate frame. Entries in the Body Vector Table are not propagated with respect to spacecraft time but are fixed according to user-specified command parameters. The Body Vector Table allows the user to explicitly accommodate in-flight identification of end-to-end structural and/or electrical misalignments. The vectors are stored as unit vectors. 4-4
67 of 217
FOIA 10-JPL-F-00451
68 of 217
4.2.4
STRUCTURE SUBSYSTEM
The STRUcture subsystem (STRU) provides mechanical support and alignment for all flight equipment including the Huygens Probe, attachment points for handling, and thermal conductivity. In addition it provides an equipotential container, an electrical grounding reference, RFI shielding, and protection from radiation and meteoroids. STRU consists of the Upper Equipment Module (UEM) which contains the 12-bay electronics bus assembly, the instrument pallets, and the MAG boom, and the Lower Equipment Module (LEM), plus all the brackets and structure for integrating the Huygens Probe, the HGA, LGAs, RTGs, reaction wheels, the main rocket engines, the four RCS thruster clusters, and other equipment. In addition, STRU includes the adapter which supports the spacecraft on the Centaur during launch. 4.2.5 RADIO FREQUENCY SUBSYSTEM The Radio Frequency Subsystem (RFS) provides the telecommunications facilities for the spacecraft and is used as part of the radio science instrument. For telecommunications, it produces an X-band carrier at 8.4 GHz, modulates it with data received from CDS, amplifies the X-band carrier power to produce 20 W from the Traveling Wave Tube Amplifiers (TWTA), and delivers it to the Antenna Subsystem (ANT). (The 20W is expected to degrade to about 19W by the start of the tour.) From ANT, RFS accepts X-band ground command/data signals at 7.2 GHz, demodulates them, and delivers the commands/data to CDS for storage and/or execution. The Ultra Stable Oscillator (USO), the Deep Space Transponder (DST), the X-band Traveling Wave Tube Amplifier (TWTA), and the X-band Diplexer are those elements of the RFS which are used as part of the radio science instrument. The DST can phase-lock to an X-band uplink and generate a coherent downlink carrier with a frequency translation adequate for transmission at X-, S-, or Ka-band. The DST has the capability of detecting a ranging modulation and of modulating the X-band downlink carrier with the detected ranging modulation. Differenced one-way ranging (DOR) tones can also be modulated onto the downlink. The DST can also accept the reference signal from the USO and generate a noncoherent downlink carrier. However, there are currently no plans to use the DOR tones for navigation. 4.2.6 POWER AND PYROTECHNICS SUBSYSTEM The Power and Pyrotechnics Subsystem (PPS) provides regulated electrical power from three RTGs on command from CDS to spacecraft users at 30 Volts DC, distributed over a power bus. In addition, PPS provides power to the various pyrotechnic devices on command from CDS. PPS also disposes of excess energy by heat radiation to space via a resistance shunt radiator. Initial measurements of the output of the radioisotope thermoelectric generators indicate a beginning-of-life power of 876 6 Watts and estimates of 740 Watts at SOI and 692 Watts at end of mission. These estimates are at least 30 Watts above pre-launch predictions. Modifications to the payload operational modes are being considered to best use this additional power, within required operating margins, and to include measured power consumption for each instrument. 4.2.7 COMMAND AND DATA SUBSYSTEM The CDS receives the uplink command stream via the RFS and decodes this stream which includes timing (immediate or sequence), routing, action, and parameter information. The CDS then distributes commands designated for other subsystems or instruments, executes those commands which are decoded as CDS commands, and stores sequence commands for later execution. The CDS has a capacity of 153,600 words. One CDS word equals 16 bits. The following table shows the allocation for the CDS words. 4-6
69 of 217
Table 4.3 CDS Words Allocations CDS Words Sequence Memory 10,240 On-board modules 130,240 Background sequence TCM 2,048 IVP Update 4,096 4,096 Mini-sequence IDAPs 1,856 1,024 Global Variables Total: 153,600 The Cassini spacecraft design includes two identical SSRs. Each CDS is attached to the two SSRs such that each CDS can communicate (read, write) with one SSR or the other SSR but not simultaneously. The Mission and Science Operations Office has the capability to control how the SSR attachments are configured via real-time command or a stored sequence. Under fault response conditions FSW can switch SSR attachment from CDS A to CDS B. The CDS receives data destined for the ground on the data bus from other on-board subsystems, processes it, formats it for telemetry and delivers it to RFS for transmission to Earth. Each subsystem interfaces with the data bus through a standard Bus Interface Unit (BIU) or a Remote Engineering Unit (REU). Data is collected in 8800 - bit frames, and ReedSoloman Encoded on downlink. A 32 framesync marker along with the encoding increases these frames to 10,112 bits. CDS software contains algorithms that provide protection for the spacecraft and the mission in the event of a fault. Fault protection software ensures that, in the case of a serious fault, the spacecraft will be placed into a safe, stable, commandable state (without ground intervention) for a period of at least two weeks to give the ground time to solve the problem and send the spacecraft a new command sequence. It also autonomously responds to a predefined set of faults needing immediate action. 4.2.7.1 ORBITER TELEMETRY MODES A set of telemetry modes has been defined to accommodate different engineering and science activities and the changing telecommunications capability during the Cassini mission. Eleven telemetry modes were implemented before launch to accommodate pre-launch and early postlaunch operations. The remaining modes are being developed and tested during cruise. Thirty modes can be stored on-board the spacecraft at any one time; more may exist on the ground, and various modes may be updated or replaced as the telemetry needs of the mission change. Refer to CAS-3-281 for more information on orbiter telemetry modes. Each telemetry mode represents a unique configuration of data sources, rates, and destinations for telemetry data gathered and distributed by the CDS. Data are routed either to the SSR for temporary storage or to the RFS for transmission to the ground or both. There are five sources of telemetry data: 1) Engineering data from the spacecraft subsystems is gathered in every telemetry mode and sent to the SSR for recording. Realtime engineering data are also included in the downlink data stream in most of the telemetry modes. For some of the telemetry modes used during the early part of the cruise phase, when the downlink data are transmitted via the LGAs, the engineering data rate could drop to 0 or 20 bps for SSR playback and 20 bps in real-time. Science housekeeping data are gathered from the instruments when they are operating and are either sent to the SSR or routed into the downlink data stream. The peak rate for science housekeeping data are predicted to not exceed 275 bps. 4-7
2)
70 of 217
3)
Scientific data from the instruments is always routed to the SSR in the telemetry modes that include science data collection. Data rates in these modes can be up to 410 kbps, however, the actual data rate into the SSR during science data collection in a given telemetry mode can vary up to this maximum. This is because there is insufficient storage and downlink data volume to collect data continuously at this rate, and some of the higher rate instruments will have to vary their data collection rates to fit within the available downlink data volume. Playback data from the SSR is routed into the downlink data stream to the RFS, at speeds depending on the downlink data rate. Probe data are included in two of the telemetry modes to allow for Probe checkout and Probe relay operations. These data will be collected at a rate of about 20 kbps.
4) 5)
Table 4.4 describes the telemetry modes, which have been grouped into eight functional categories, which are: Realtime Engineering (RTE) Playback plus Realtime Engineering (PB&RTE) Probe Checkout (PCHK) Probe Operations (PRLY) Science and Engineering Record (S&ER) Realtime Engineering plus Science Playback (RTE&SPB) SAF Instrument Checkout (SAF) Instrument Maintenance (IM) 4.2.8 ATTITUDE AND ARTICULATION CONTROL SUBSYSTEM The Attitude and Articulation Control Subsystem (AACS) provides dynamic control of the spacecraft in rotation and translation. It provides fixed-target staring for HGA and remote sensing pointing and performs target relative pointing using inertial vector propagation as well as repetitive subroutines such as scans and mosaics. Rotational motion during the Saturn tour that requires high pointing stability is normally controlled by the three main Reaction Wheel Assemblies (RWAs), although modes requiring faster rates or accelerations may use thrusters. The additional fourth reaction wheel can articulate to replace any single failed wheel. Each RWA has a mass of 14.53 kg. The largest reaction torque for each RWA is 0.13Nm. None of the three RWAs can absorb an angular momentum that is larger than 34Nms (approx. 2000 rpm). All RWAs have their spin axes at 54.7356o from the spacecraft Z-axis. Gyros are used primarily during the four year tour of the Saturnian system but will have some pre-Saturn use as well. If, upon evaluation after SOI, the IRUs show no signs of performance degradation, they will be used continuously for the full tour. The IRUs will be re-evaluated whenever a life limiting characteristic becomes evident. In the event of IRU failure or loss of performance, IRU use during the tour can be restricted to periods of high science activity. AACS contains a suite of sensors that includes redundant Sun Sensor Assemblies (SSA), redundant Stellar Reference Units (SRU, also called star trackers), a Z-axis accelerometer, and two 3-axis gyro Inertial Reference Units (IRU). Each IRU consists of four gyros, three orthogonal to each other and the fourth skewed equidistant to the other three. AACS also controls actuators for the main rocket engine gimbals. With two redundant MIL-STD-1750A AACS Flight Computers (AFC) running flight software programmed in Ada, AACS processes commands from CDS via the CDS data bus and produces commands to be delivered to AACS actuators and/or PMS ME and RCS valves for spacecraft attitude and V control. AACS provides heartbeat, telemetry and fault response information to the CDS. 4-8
71 of 217
TELEMETRY MODES - RECORD & REAL-TIME DOWNLINK

C A P S CIM DNA AMG S
SCIENCE MRCII IPISS MWRSS ISS
Telemetry Mode
CDS CDS V7 V9
S&ER-1 S&ER-2 S&ER-3 S&ER-4 S&ER-5 S&ER-5a S&ER-6 S&ER-7 S&ER-8 S&ER-9 S&ER-10 (prime)* S&ER-10 (online)* RTE-5 RTE-10 RTE-20 RTE-40 RTE-158 RTE-948 RTE-1896
U V I S
V I M S
R A D A
RECORD TO SSR HOUSEKEEPING PCCIMMRCIIUVRP SADNAIPISSVIAS APAMGMWRSSIMDA S S ISSnwSSR
ENG
Total rate (bps) (bps) 218 218 218 218 218 239 218 218 239 218 218 1623 1623 1623 1623 1623 1623 1623 1623 1623 1623 1623 1214
DOWNLINK ENG TOTAL
(bps)
1633 1633 1633 1633 1633 1633 1633 1633 1633 1633 1633 1633
Downlink (bps) 1896 1896 1896 1896 1896 1896 1896 1896 1896 1896 1896 1896
239 239 239 239 239 239 239

218
1623 1623 1623 1623 1623 1623 1623

1623 1623 1214
4 9 17 34 121 798 1633

1624 1633 1489
5 10 20 40 158 948 1896

24885 1896 1896
PCHK PRLY (prime) PRLY (online) * S&ER-10 is the telemetry mode used during SOI.
FOIA 10-JPL-F-00451
72 of 217
TELEMETRY MODES - PLAYBACK

C A P S CIM DNA AMG S
RECORD TO SSR SCIENCE MRCIIUVRP IPISSVIAS MWRSSIMDA ISSwnSSR
ENG (bps)
1623 1623 1623 1623 1623 1623 1623 1623 1623 1623 1623 1623 1623 1623
SSR CCIM Playback A D N A (bps) P A M G S S 10515 17382 22202 27012 29077 34235 39382 55882 70327 84762 94382 106422 121882 142512 121861 214681 214681 214681
214681 17 157 808
Telemetry Mode RTE&SPB-14220 RTE&SPB-22120 RTE&SPB-27650 RTE&SPB-33180 RTE&SPB-35550 RTE&SPB-41475 RTE&SPB-47400 RTE&SPB-66360 RTE&SPB-82950 RTE&SPB-99540 RTE&SPB-110600 RTE&SPB-124425 RTE&SPB-142200 RTE&SPB-165900 SAF-142.2 SAF-248.85 SAF-248.85(1) SAF-248.85(2) SAF-248.85(3) PB&RTE-40 PB&RTE-200 PB&RTE-948
CDS CDS V7 V9

PATCH
M I M I
DOWNLINK HOUSEKEEPING R C I I U V R P Total PISSVIAS rate W R S S I M D A (bps) SSwnSSR 218 218 218 218 218 218 218 218 218 218 218 218 218 218
ENG
TOTAL
R-T ENG Downlink (bps) (bps) 1626 1633 1626 1628 1626 1624 1633 1633 1626 1628 1633 1624 1633 1628 14220 22120 27650 33180 35550 41475 47400 66360 82950 99540 110600 124425 142200 165900
1623 1623 1623 1623

1623 1623 1623 1623

# # #
239 239 239 239

239
1633 1626 1626 1626

1626 17 17 17
142200 248850 248850 248850

248850 40 200 948
FOIA 10-JPL-F-00451
73 of 217
4.2.9
CABLING SUBSYSTEM
The cabling subsystem (CABL) consists of all power and data cabling on the spacecraft, except for coaxial cabling and waveguides. CABL conducts power from the three RTGs to the PPS and from the PPS out to the instruments, pyro devices, and power shunt radiator. CABL conducts data between CDS and the other subsystems and assemblies on the spacecraft. It also provides any access and breakouts that are needed during integration and testing prior to launch. 4.2.10 PROPULSION MODULE SUBSYSTEM The Propulsion Module Subsystem (PMS) provides thrust and torque to the spacecraft. Under command from AACS, the thrust and torque establish the spacecraft attitude, pointing, and the amount of velocity vector change. For attitude control, PMS has a Reaction Control Subsystem (RCS) consisting of four thruster clusters mounted off the PMS core structure adjacent to the LEM at the base of the spacecraft. Each of the clusters contain 4 hydrazine thrusters. The thrusters are oriented to provide thrust along the spacecraft Y and -Z axes. RCS thrusters also provide V for small maneuvers. The approximate ISP for the RCS is 180s for turns, 140s for RWA unloads, 120s for limit cycling, and the theoretical max is 217s. Table 4.5 Thruster Cluster Mass Properites Thruster Cluster # 1 2 3 4 Mass (kg) 5.91 5.91 5.91 5.91 Xcm (m) 1.24 -1.24 -1.24 1.24 Ycm (m) 1.59 1.59 -1.59 -1.59 Zcm (m) 2.88 2.88 2.88 2.88
For larger Vs, PMS has a primary and redundant pressure-regulated main rocket engine. Each engine is capable of a thrust of approximately 445 N when regulated. The bipropellant main engines burn nitrogen tetroxide (N2O4) and monomethylhydrazine (N2H3CH3) producing an expected specific impulse of up to 308s. These engines are gimbaled so that, under AACS control during burns, the thrust vector can be maintained through the shifting center of mass of the spacecraft. AACS-provided valve drivers for all the engines/thrusters operate in response to commands received from AACS via the CDS data bus. While the gimbals or the valve drive electronics are active -- be it during a burn or spacecraft checkout -there is some effect to the Radio and Plasma Wave Spectrometer due to electromagnetic interference. Since maneuvers and checkout occur so infrequently, and usually during periods where little or no science is collected, this is not a problem, but RPWS planning staff must be aware of this. During a main engine burn, RCS thrusters, controlled by AACS, maintain the spacecraft attitude about the roll axis. The main rocket engine performs most large maneuvers with the pressure regulated; however, it performs maneuvers in the blowdown mode during portions of the mission when the pressurization system is pyro-isolated. Only one of the two main engines is permitted to operate at a time, whether pressurized or in blowdown mode. Mounted below the main engines is a retractable cover which is used during cruise to protect the main engines from micrometeoroids. The thin coating on the inside of the engines is especially vulnerable to micrometeoroid damage, and if this coating is damaged it can lead to the loss of the engine. The main engine cover can be extended and retracted multiple times (at least 25 times), and has a pyro ejection mechanism to jettison the cover should there be a 4-11
74 of 217
mechanical problem with the cover that interferes with main engine operation. During cruise the cover will remain closed when the main engines are not in use. During ground testing, the main engines developed an oscillation, called chugging, when operated in lower pressure regimes. In order to minimize the potential loss of Isp and V due to chugging, it is recommended that the engine be operated at pressures above the point where chugging was observed. If engine operation is required at lower pressures, the total amount of time the engines operate in the chugging regime will be limited to 60 minutes. 4.2.10.1 HYDRAZINE The hydrazine tank will be fully loaded at launch to maximize the propellant available at the end of the tour and for any extended mission. 1% of the hydrazine is considered unusable because it may be left over in the tank/lines and loading uncertainty. The Cassini Consumables document, PD 699-523, details the expected hydrazine usage during tour. Advance planning and tracking of hydrazine usage should allow for a healthy margin to be maintained. The margin will be available for unexpected occurances during tour should they arise. Any unused hydrazine remaining after tour will be available for use in an extended mission. As propellant is used, the helium pressurant expands to fill the space used by the expended propellant, thereby decreasing the pressure in the tank. When the tank pressure reaches some minimum level, a second tank containing additional helium pressurant is connected to the hydrazine tank by firing a pyro valve. This effectively raises the pressure of the hydrazine tank. This one-time recharge will likely be used after the probe mission is complete to raise the thrust level for the tour portion of the mission. At launch, the initial pressure of the hydrazine tank is determined by the maximum allowable pressure and temperature of the tank and by the propellant load. The planned propellant load for the Cassini hydrazine tank is 132 kg, which is the maximum allowable load for the tank design. This value represents the maximum pressure at which the thruster is qualified to operate. The maximum flight allowable temperature of the hydrazine tank is 45C. With the current constraints, the maximum allowable initial pressure of the tank has been calculated to be 370 psia, at an initial tank pressure of 21C. The pressure after recharge can be calculated in a similar fashion as above. In this case, the propellant load can vary, depending on when in the mission the tank is re-pressurized. The blowdown curve in Figure 4.2 assumes that the recharge occurs when 100 kg of propellant remains in the tank. Given a 100 kg load, and the previous pressure and temperature constraints, the maximum recharge pressure is calculated to be 380 psia. The hydrazine tank pressure needs to be above 250 psia to maintain turn times in the thermally constrained environment inside one AU. The minimum pressure needed during low (950 km altitude) Titan flybys is also 250 psia. Figure 4.2 shows the hydrazine blowdown curve with the recharge after SOI, when approximately 100 kg of hydrazine remains. The range of fuel remaining for SOI and EOM are estimates based on expected values and 50% greater use (AACS) or allocation (Nav). The recharge point may be moved in time depending on whether hydrazine usage is more or less than expected and when higher turn performance is desired. However, there is a pressure which must be reached before the tank can safely be recharged. In the example shown in Figure 4.2, that pressure is 237 psia, based on a recharge with 100 kg of hydrazine in the tank. The maximum allowable pressure prior to recharge is a function of the recharge tank helium load and is fixed at PMS loading, months before launch. The tour will have a series of low Titan flybys. The majority of these low flybys will most likely occur late in the tour. As a result, the hydrazine tank pressure may be allowed to dip below 250 psia early in the tour if there are no Titan low flybys scheduled. However, if the 4-12
75 of 217
the tour has low Titan flybys scheduled early, the tank recharge may need to occur early after the probe mission.
Blowdown from initial load

Thrust=0.99 N
Blowdown from recharge at 250 psia

Thrust=1.02 N
Thrust=0.64 N Minimum Thruster Pressure
500.00 450.00 400.00 350.00 300.00 250.00 200.00 150.00 100.00 50.00 0.00 0
132 kg full load
SOI
140
120
100
80 60 Hydrazine Remaining, Kg
EOM
40
20
Figure 4.2 Hydrazine Blowdown With Recharge 4.2.10.2 MAIN ENGINE USAGE This subsection discusses main engine burn profiles for the Cassini mission set. d V estimates are expressed in terms of mean dV. The navigation staff recommends that suballocated d V estimates be used for statistical maneuvers on a maneuver-to-maneuver basis. The suballocations are computed so that when added together, the net budget is equal to a 50% confidence V estimate. However, this section considers the most realistic V budget as a whole and therefore uses current best estimates. The launch delay to the tenth day of the primary launch period resulted in a near-optimal launch date and reduced the d V requirements for reaching Saturn. Current estimates by the Navigation Team forecast the d V available for the tour as 520 m/s from the bipropellant engines and 37 m/s from the monopropellant thrusters with a 95% confidence. An additional 70 m/s is held as end-of-mission margin. 2.7% of the bipropellant is considered unusable because it will be left over in the tank/lines and loading uncertainty. 4.2.10.3 MEA OPERATION During testing, the MEA developed an oscillation (i.e., chugging) when operated below certain pressure levels. In order to minimize the possibility of damage to the MEA or the spacecraft, the amount of time that the MEA is allowed to operate in the chugging regime will be limited to a total of 60 minutes. Figure 4.3, from the Navigation Plan, shows the predicted progression of the mean values of the bipropellant fuel and oxidizer pressures for the interplanetary portion of the mission. The circles on the figure denote the coast periods between events. The figure begins with TCM-1 which was accomplished in blow-down mode after the pressurization of the fuel and oxidizer tanks. The pressures before and after TCM-1 were obtained from telemetry data. Following TCM-1 the pressures varied as a results of helium absorption and temperature changes. TCM-2 was accomplished using the RCS thrusters and, therefore, is not reflected in the bipropellant pressure history.
4-13
76 of 217
280
260
Chugging Boundary REA Operating Boundary DSM SOI
240
TCM 9
220
TCM 1
200
Post-TCM-1 He Absorption Earth Swingby Saturn Approach
180
160 160
180
200
220 Fuel Tank Pressure, psia
240
260
280
Figure 4.3 Biprop Tank Pressure History - Mean - Post-TCM-2 Trajectory Redesign The fuel and oxidizer tanks will be pressurized and regulated for the DSM. Following the DSM the oxidizer tank is isolated with a pyro valve and the fuel tank is isolated with a high pressure latch valve. Except for TCM-9, the plan is to remain isolated until just prior to SOI and accomplish all of the bipropellant maneuvers in "blow down mode. In order to preclude crossing the "chugging" boundary, it is necessary to pressurize the fuel tank during the execution of TCM-9. The history assumes that the fuel tank achieves the regulated pressure after the end of TCM-9 (the variations in the fuel pressure during the maneuver are not modeled). The figures assume that all maneuvers under 0.7 m/s are accomplished using the RCS system. (The actual value for choosing RCS or ME will be between 0.5 and 1.0 m/s). Additional information about best case and worst case predictions are discussed in the Navigation Plan. All cases remain within the operating and chugging boundaries. 4.2.11 TEMPERATURE CONTROL SUBSYSTEM The TEMPerature control subsystem (TEMP) permits operation over the expected solar ranges (0.61 to 10.1 AU) with some operational constraints discussed in each scenario. Temperatures of the various parts of the spacecraft are kept within allowable limits by a large number of local TEMP thermal control techniques, many of which are passive. The 12-bay electronics bus has automatically positioned reflective louvers. Radio Isotope Heater Units (RHU) are used where constant heat input rates are needed and where radiation is not a problem. Multilayer insulation blankets cover much of the spacecraft and its equipment. Electric heaters are used in different locations and are operated by CDS and instruments. Temperature sensors are located at many sites on the spacecraft, and their measurements are used by CDS to provide commands to TEMP's heaters. Shading is executed by pointing the 4-14
77 of 217
HGA (-Z axis) towards the sun; the HGA is large enough to provide shade for the entire spacecraft body including the Huygens Probe. 4.2.12 MECHANICAL DEVICES SUBSYSTEM The mechanical devices subsystem provides a pyrotechnic separation device that provides for separation of the spacecraft from the launch vehicle adapter. Springs provide the impulse to separate the spacecraft from the adapter. The mechanical devices subsystem also provides a self-deploying 10.5 meter coiled longeron mast stored in a canister for the two magnetometers, electrostatic discharge covers over inflight separation connectors, an articulation system for the backup reaction wheel assembly, a "pinpuller" for the RPWS Langmuir Probe, and louvers and variable RHUs for temperature control. The magnetometer boom and other spacecraft deployable elements are not deployed until well after the separation event. 4.2.13 ELECTRONIC PACKAGING SUBSYSTEM The Electronic Packaging Subsystem (EPS) consists of the electronics packaging for most of the spacecraft in the form of the 12-bay electronics bus. The bus is made up of bays containing standardized, dual-shear plate electronics modules. 4.2.14 SOLID STATE RECORDER SUBSYSTEM Cassinis two Solid State Recorders (SSRs) are the primary memory storage and retrieval devices for the orbiter. Each SSR contains 128 submodules, of which 8 are used for flight software and 120 are useable for telemetry. Each submodule has 16,777,200 bits for data, so the total data available for telemetry for each SSR is 2.013 Gbit. Expressed in terms of 8800-bit telemetry frames, this is 228,780 frames per SSR. Accounting for effects of solar and cosmic radiation, the end of mission capacity is expected to be no less than 1.800 Gbit per SSR. There are currently no bad blocks on either SSR, so the total start of mission capacity is still available. Spacecraft telemetry and AACS, CDS, and instrument memory loads can be stored in separate files, or partitions, on board the SSR routed through virtual channels. All data recorded to and played back from the SSR is handled by the CDS. A change has occurred since launch in the way engineering data is recorded to the SSR. Engineering will be recorded to a dedicated partition (Partition 6) starting in Version 9.0. In order to support science both the AACS prime packet and the RFS packet will be duplicated and recorded to Partition 4 for downlink to ground. There are three different SSR modes in which the SSR can function: Read-Write to End, Circular FIFO, and Ring Buffer. There is also a record pointer and a playback pointer, which mark the memory addresses at which the SSR will write or read, respectively. In Read-Write to End, there is a logical beginning and end to the SSR. Recording begins at this logical beginning and continues until either the SSR is reset (the record and playback pointers are returned to the logical beginning) or until the record pointer reaches the end. If the record pointer does reach the end, recording is halted until the SSR is reset. In Circular FIFO, there is no logical end to the SSR. The data is continuously recorded until the record pointer reaches the playback pointer. The Ring Buffer mode behaves exactly like Circular FIFO, with one exception. Recording will not stop if the record pointer reaches the playback pointer. 4.2.15 ANTENNA SUBSYSTEM The ANTenna subsystem (ANT) provides a directional high gain antenna (HGA) for X-, Ka-, Sand Ku-band for transmitting and receiving on all four bands. Because of its narrow halfpower beam width of 0.14 deg for Ka-band, it must be accurately pointed. The HGA, and the low gain antenna 1 (LGA1) located on the HGA feed structure, are provided by the Italian Space Agency. Another LGA (LGA2) is located below the Probe pointing in the -X direction (see Figure 4.1). During the inner solar system cruise, the HGA is Sun-pointed to provide 4-15
78 of 217
shade for the spacecraft. ANT provides two LGAs which allow one or the other to receive/transmit X-band from/to the Earth when the spacecraft is Sun-pointed. The LGAs also provide an emergency uplink/downlink capability while Cassini is at Saturn. The HGA downlink gain at X-band is 47dBi and the LGA1 peak downlink gain is 8.9 dBi. The X-band TWTA power is 20 watts. 4.2.16 SCIENCE INSTRUMENTS There are 12 science instrument subsystems grouped into three larger groups: Optical Remote Sensing, Fields/Particles/Waves and Microwave Remote Sensing. The Optical Remote Sensing instruments are mounted on the Remote Sensing Pallet (RSP) rigidly attached to the UEM, shown in Figure 4.4. The Fields, Particles, and Waves (FPW) instruments are mounted in several locations on the spacecraft. The MAG sensors are located on the extensible MAG boom, attached to the top of the UEM. A small pallet, also mounted on the UEM, carries INMS, MIMI LEMMS and CHEMS, and CAPS. MIMI INCA, CDA, and the RPWS antennas and Magnetic Search Coils (MSC) are attached elsewhere on the UEM. (Note that the MIMI INCA is a remote sensing instrument with the capability of imaging the charged particle population of Saturn's magnetosphere. Figures 4.4-5 depicts the Remote Sensing Pallet and Fields and Particles Pallet. There are two microwave sensing instruments: RADAR and the Radio Science Subsystem (RSS). The RADAR Flight Instrument System consists of the following subsystems: the Radio Frequency Electronics Subsystem (RFES), the Digital Subsystem (DSS), the Energy Storage Subsystem (ESS), and the Antenna Subsystem. DSS and ESS are located in one of the equipment bays below the HGA. RFES is in a penthouse-like attachment over the bay. The principal component of the Antenna Subsystem is the five-beam Ku-band HGA feed. RADAR shares the HGA with the RSS for both its active (Synthetic Aperture RADAR imaging and altimetry) and passive (radiometry) operations. The Radio Science instrument is composed of elements located in the DSN and onboard the spacecraft. The flight Radio Science instrument consists of the Radio Frequency Instrument Subsystem (RFIS) and elements of the RFS. The main assemblies of the RFIS are the Ka-band Exciter, the Ka-band TWTA, the Ka-band Translator, and the S-band transmitter. In addition, the HGA is used as part of the Radio Science Instrument to receive the X- and Ka-band signals and to transmit at X-, Ka-, and S-bands. 4.2.17 ORBITER CONSUMABLE BUDGETS Consumable budgets and usage reports are defined in the Cassini Consumables document, PD 699-523 which can be found on the Cassini Mission Planning Home Page, https://cassini.jpl.nasa.gov/mp/ 4.3 THE HUYGENS PROBE SYSTEM the Huygens Probe itself, which enters the Titan atmosphere near the beginning of the tour 22 days after separation from the Orbiter; and the Probe Support Equipment (PSE) consisting of those parts of the System which remain attached to the Orbiter in support of the Probe Mission. ENTRY SUBSYSTEM The Probe System consists of two elements:
Refer to Figure 4.8 for depictions of the components of the Huygens probe. 4.3.1 This subsystem functions only during the release of the Probe from the Orbiter and its subsequent entry into the Titan atmosphere. It consists of three main elements:
4-16
79 of 217
Figure 4.4 Remote Sensing Pallet
Figure 4.5 Fields & Particle Pallet 4-17

80 of 217
FIGURE 4.6 Fields of View for Cassini Science Instruments
4-18
81 of 217
PROJECTION ON SKY (ALONG Y-AXIS)

UVIS narrow (0.75 mrad by 61 mrad)
UVIS medium (1.5 mrad by 61 mrad)
UVIS wide (6 mrad by 61 mrad)
ISS NAC* (6.1 mrad)
ISS WAC (61.2 mrad)
CIRS (4.3 mrad, center offset from optical axis by 4 mrad)
CIRS (2 at 2.9 x 0.3 mrad, 0.67 mrad separation between inside edges)
*ISS NAC calibration shows offset by +0.822 mrad in X and -0.426 mrad from in Z from the -Y axis. Other instruments are shown in their nominal positions.
VIMS Visible & IR Frame (32 mrad)
+X
+Y
+Z Spacecraft Axes
Figure 4.8 Fields of view for the Optical Remote Sensing Instruments.
4-19
82 of 217
The Spin-Eject device, which by means of springs simultaneously propels the Probe away from the Orbiter with a relative velocity of 0.3 to 0.4 m/s and imparts to it a spin about its axis of greater than 5 rpm; A front shield, 2.7m in diameter, covered with a special thermal protection material, to protect the Probe from the enormous heat flux generated during entry; and An aft cover, covered in thermal protection materials to reflect away the heat radiated from the hot wake of the Probe.
Once the Probe has decelerated to about Mach 1.5, the aft cover is pulled off by a pilot parachute. An 8.3 m diameter main parachute is then deployed to ensure a slow and stable descent. The main parachute slows the Probe, and allows the decelerator to fall away when it is released. To limit the duration of the descent to a maximum of 2.5 hours, the main parachute is jettisoned at entry +900 seconds and replaced by a 3.0 m diameter drogue chute for the remainder of the descent. 4.3.2 INNER STRUCTURE SUBSYSTEM The inner structure of the Probe consists of two aluminum honeycomb platforms and an aluminum shell. It is linked by fiberglass struts and pyrotechnically operated release mechanisms to the front shield and aft cover. The central equipment platform carries, on both its upper and lower surfaces, the boxes containing the electrical subsystems and the experiments. The upper platform carries the parachute (when stowed) and the antennas for communication to the Orbiter. 4.3.3 THERMAL CONTROL SUBSYSTEM At different phases of the mission, the Probe will be subjected to extreme thermal environments requiring a variety of (passive) controls to maintain the required temperature conditions. During cruise, the solar heat input at perihelion (and during the Venus flybys) will be high, but the Probe will get some protection from its accommodation in the shade of the Orbiter's high-gain antenna. When the Orbiter is off Sun-point for maneuvers or communication, the Probe will be protected by multilayer insulation, which will later burn off during the atmospheric entry. Once the Orbiter leaves the inner solar system, the equilibrium temperature of the Probe will be much reduced. After separation from the Orbiter the Probe will be at its coldest. To ensure that none of the equipment falls below its storage-temperature limit the Probe carries 35 Radioisotope Heater Units, each generating 1 W. During entry the front shield may reach temperatures above 1500 C. Layers of insulation will ensure that the equipment inside stays below 50 C. Once the chute is deployed, the Probe instruments will be exposed to the cold Titan atmosphere at a temperature of 70K. The internal temperature will be kept within operating limits by thick foam insulation filling the Probe and by power dissipation in the experiments and subsystems. 4.3.4 ELECTRICAL POWER SUBSYSTEM During Probe checkout, the Probe will obtain power from the Orbiter via the umbilical cable. For all operations after separation, five lithium sulfur dioxide batteries, each with 26 cells, will be used. Their storage degradation during the long cruise will be compensated by depassivation (taking the surface charge off the active surfaces) during the pre-separation reconfiguration.
4-20
83 of 217
Figure 4.9 Huygens Probe Composition
4-21
84 of 217
Part of the battery power is used to power the timer for the 22 days of coast. The higher current needed for Probe mission operations is only necessary for the descent duration of 2.5 hours. 4.3.5 COMMAND AND DATA MANAGEMENT SUBSYSTEM to time the Coast phase and switch on the Probe just prior to entry; to control the activation of deployment mechanisms during descent; to distribute telecommands to the subsystems and experiments; to distribute to experiments a Descent Data Broadcast providing a timeline of conditions on which the instruments can base the scheduling of mode changes and other operations; to collect scientific and housekeeping data and forward them to the Orbiter, via the umbilical cable during the Cruise segment or via the PDRS during Descent. PROBE DATA RELAY SUBSYSTEM The functions of the command and data management subsystem are:
4.3.6
The Probe Data Relay Subsystem (PDRS) provides the one-way communications link between the Probe and the Orbiter and includes equipment installed in each part of the spacecraft. The elements that are part of the PSE are the Probe System Avionics (PSA) and the Radio Frequency Electronics (RFE) which includes an ultra-stable oscillator (USO) and a low-noise amplifier. For redundancy, the Probe carries two S-band transmitters, both transmitting during Probe descent, each with its own antenna. The telemetry in one link is delayed by about six seconds with respect to the other to avoid data loss if there are brief transmission outages. Reacquisition of the Probe signal would normally occur within this interval. 4.3.6.1 PROBE RELAY PROBLEM The receivers in the Huygens Probe support equipment on board the Cassini spacecraft have exhibited a performance anomaly under the conditions expected during the nominal Probe mission. There is sufficient margin to maintain both carrier and sub-carrier lock throughout the Probe mission. However, at the link levels expected, the digital circuitry which decodes the data from the sub-carrier does not have sufficient bandwidth to properly process the data from a sub-carrier which has been Doppler shifted by the nominal 5.6 km/s velocity difference between the Cassini orbiter and the Huygens Probe. The initial assessment of the affect of this anomaly is that it will lead to unacceptable data losses during the Probe descent to Titan. This anomaly was addressed by redesigning the orbiter trajectory at the time of the probe mission in order to minimize the Doppler on the received probe signal. In addition to this, it may be possible to preheat the probe transmitters for four hours before the probe mission to improve data performance and to insert zero packets into the probe data stream minimizing the expected cycle slips. However these latter two options are still being investigated. 4.3.7 4.3.7.1 HUYGENS SCIENCE INSTRUMENTATION HUYGENS ATMOSPHERIC STRUCTURE INSTRUMENT The huygens probe instruments were constructed as described below. This experiment comprises a suite of sensors that measure the physical properties of Titan's atmosphere. Accelerometers will measure forces in all three axes so that, knowing the aerodynamic properties of the Probe, the atmospheric density can be deduced and wind gusts detected. In the event of a landing on a liquid surface the Probe motion due to waves will be 4-22
85 of 217
measurable. Temperature and pressure sensors will enable the construction of a profile of the thermal structure of the atmosphere. The Permittivity and Electromagnetic Wave Analyzer will measure the ion and electron conductivities of the atmosphere and search for electromagnetic wave activity. On the surface, the conductivity and permittivity of the surface material will be measured. 4.3.7.2 DOPPLER WIND EXPERIMENT This experiment will use an ultra stable oscillator to give the Probe relay link a very stable carrier frequency. The Doppler shift calculated from the frequency measured at the Orbiter will be a measure of the Probe motion from which the component of the wind along the line of sight can be calculated. 4.3.7.3 DESCENT IMAGER/SPECTRAL RADIOMETER This instrument will make a range of imaging and spectral observations using several sensors and fields of view. By measuring the upward and downward flux of radiation, the radiative balance (or imbalance) of the thick Titan atmosphere will be deduced. Solar aureole sensors will measure the light intensity around the sun due to scattering by aerosols in the atmosphere. This will permit the calculation of the size and number density of the suspended particles. Two imagers (one visible, one infrared) will observe the surface during the latter stages of the descent and, as the Probe slowly spins, build up a mosaic of pictures around the landing site. There is also a side-looking visible imager looking horizontally to view the horizon and the underside of the cloud deck. For spectral measurements of the surface, the weak sunlight will be augmented by a lamp shortly before landing. 4.3.7.4 GAS CHROMATOGRAPH-MASS SPECTROMETER This gas analyzer will identify and quantify the abundances of the various atmospheric constituents, as well as measure the surface composition in the event of a safe landing. A mass spectrometer will construct a spectrum of the molecular masses of the gas driven into the instrument by the dynamic pressure of the Probe's descent. A more powerful separation of molecular and isotopic species will be accomplished by a chromatography column. Surface material investigation will be made possible by heating the GCMS inlets just prior to impact to vaporize the material on contact. During descent the GCMS will also analyze pyrolysis products passed to it from the ACP (see below). 4.3.7.5 AEROSOL COLLECTOR PYROLYZER Aerosol particles in the atmosphere will be drawn by a pump through filters to trap samples which are heated in ovens to vaporize volatiles and decompose the complex organic materials. The products will then be flushed along a pipe to the GCMS for analysis as described above. Samples will be taken down to 40km and again between 18-23km. 4.3.7.6 SURFACE SCIENCE PACKAGE The surface science package is comprised of a number of sensors to determine the properties of the surface, whether it be solid or liquid. An acoustic sounder, activated during the last kilometer of the descent, will determine continuously the distance to the surface from about 100m in altitude, measuring the rate of descent and the surface roughness (e.g. due to waves). On the (liquid) surface, the sounder will measure the speed of sound in the ocean, and possibly also the subsurface structure (depth). During descent, measurements of the speed of sound will give information on atmospheric composition and temperature. An accelerometer will accurately record the deceleration profile at impact, indicating the hardness and structure of the surface. A tilt sensor will indicate the Probe attitude after landing and will show any attitude motion due to waves. It will also measure any pendulum motion during descent. If the surface is liquid, other sensors will measure its density, temperature, refractive index, thermal conductivity, heat capacity and electrical permittivity. 4-23
86 of 217
FOIA 10-JPL-F-00451
87 of 217
SECTION 5 OPERATIONS STRATEGIES 5.1 OPERATIONS CONCEPTS Cassini's principal mission objective is to send a suite of instruments to Saturn to collect scientific data about Saturn, its rings, its satellites, its field and particle environments, and interactions between them. When considering how the mission should be run, the highest priority is placed upon the science that is gathered and returned during Cassinis 4-year tour. Consumables, resource budgets, and operations strategies are all focused on achieving the highest science return possible. 5.1.1 ON-BOARD OPERATIONS Control of the spacecraft is done, for the most part, from autonomous sequences stored onboard the spacecraft. Spacecraft sequencing uses a combination of centralized commands (for control of the system level resources) and instrument commands issued by the Command and Data Subsystem (CDS) and the instrument microprocessors to conduct activities and maintain the health and safety of the spacraft. Instrument data is formatted (including editing or compression) within the instrument microprocessor, and then collected on the spacecraft bus by the CDS on a schedule determined by the active telemetry mode. Packets from the engineering subsystems and instruments are assembled into frames and stored on the Solid State Recorder or inserted directly into the downlink telemetry stream. The spacecraft provides system level services for each of the twelve science investigations. These services include instrument command delivery, telemetry collection and transmission, spacecraft pointing and attitude stability, power, and thermal control. The spacecraft is flown with sufficient margins to allow the instruments to operate fairly independently from each other, and with a minimum of real-time ground intervention, but still allow for collaborative, synergistic collection of data. The Cassini spacecraft operates in a series of standard well-characterized configurations, referred to as "operational modes," and transitions between them use "fixed sequences." Since there is insufficient power to operate all instruments simultaneously, operational modes have been defined to balance the science return with the need to constrain operational complexity and cost in the planning and sequencing of science observations. Within an operational mode, any science and spacecraft activities are allowed that do not violate either the mode definition or other applicable constraints. The definition of each mode mirrors a common category of activities (such as maneuvers, or downlink to Earth) that are expected to be done often during the mission. Certain non-repetitive activities will be done with unique sequences of commands rather than operational modes. Non-variable but repetitive activities that are not done within an operational mode are called fixed sequences. These sequences are developed and validated once for use multiple times. Modules are the foundation on which a sequence is built, and they define the pointing of the spacecraft and the telemetry collection modes, both as a function of time. Sequence constructs during cruise consist primarily of engineering modules. During orbital operations, sequence constructs will consist primarily of science modules with some engineering activities to support the science objectives. Inherent in these operational definitions is that only one module can be executing at any time. Modules include "trigger" commands for those instruments with observations directly tied to the pointing design or telemetry mode timing. Instrument trigger commands do not necessarily need to be synchronized with module activity and may be issued independently. Modules generally have parameters that vary their behavior over a restricted range of possibilities (e.g. a mosaic size), but represent a single science observation or engineering activity. Each module operates within a single operational mode, which in turn constrains the design of the module depending on the pointing capabilities and telemetry collection bounds 5-1
88 of 217
for that operational mode. Some modules (e.g., Radio Science, MAG) can be executed with a selection of operational modes. However, there is no operational mode change within a module. Transition to the appropriate operational mode is performed before execution of the module. In order to simplify operations, timing within a module is completely self-contained, and the module is therefore relocatable in time with reasonable changes in its start time. Furthermore, modules do not require validation for their reuse--the design validation provides the necessary confidence to trust any instantiation of a module. Modules are designed to allow the addition of non-conflicting instrument triggers in parallel with the module execution for "ride-along" observations or instrument activities unrelated to the module's pointing profile, but allowed within the constraints of the modules operational mode. The constraints on the triggers are simply the instrument power states and telemetry collection bounds allowed in the operational mode. If any triggers are dependent on telemetry mode changes in the module (or any other specific times in the module), then they must be made part of the module design itself, again to simplify operations by allowing overlaid triggers to be independent of the module so as to not require an iterative design effort. 5.1.2 GROUND PLANNING & OPERATIONS Spacecraft operations will be centralized at JPL. The science teams are led using a distributed operations structure to allow scientists to operate their instruments from their home institutions with the minimum interaction necessary to collect their data. Specific functions provided centrally by JPL for the scientists include mission planning, sequence integration, sequence and command radiation, spacecraft telemetry data collection/processing (packet extraction)/storage, spacecraft monitoring and performance maintenance, Facility Instrument health and safety monitoring, and spacecraft navigation. The sequencing process is a hierarchical step-wise refinement process, starting with general goals, to high-level sequence components, and ends with low-level commanding. Sequence planning begins with long-range plans generated by the mission planners. Consumable allocations, margin policy, long-range DSN agreements, guidelines & constraints, and the operational strategies documented in this section guide the initial sequence design. The science planning team works with the mission planning, spacecraft and other offices to generate a conflict-free activity plan of integrated science and engineering activities. Both the distributed science teams and engineering subsystem representatives submit activity requests which are integrated by the science planning team. Conflicts between science activities are resolved within the science planning team, and conflicts between engineering activities are resolved within the spacecraft office, with help from the science planning team. Conflicts between science and engineering activities are resolved with participation from all element representatives, with the mission planning office as the liaison when necessary. Once the conflict-free activity plan is completed, with scheduled activities, DSN passes, instrument pointing, and data allocations, the sequence virtual team integrates the plan into a conflict-free sequence and generates, verifies and validates all related commands to be sent to the spacecraft, except for instrument internal commands. The sequence virtual team is also responsible for all system-level real-time commands associated with the sequence, and monitors the progress of the activities until the sequence is complete. During cruise, sequences largely make use of commands and scripts inherited from spacecraft testing during the Assembly, Test, and Launch Operations (ATLO) phase. Repeatable sequence components (i.e. modules) are developed slowly as experience is gained in operating the spacecraft. Some science is collected during cruise in order to gain experience with instrument operations and prepare the instrument and instrument teams for tour. During the later portions of cruise, the Science Operations Plan (SOP) is developed as the detailed plan of tour activities. The SOP is a conflict-free listing of all observations and engineering activities, a 5-2
89 of 217
constraint-checked pointing profile, and data volume allocations that would provide an acceptable level of science required to meet the primary mission objectives. As tour approaches, any high-level trade studies and changes in operations strategy are incorporated via an SOP aftermarket process, which is also used for further science optimization. In the few months before execution, the SOP sequences are refined as necessary via a short-term update process and final constraint checking, integration, validation, and command generation are performed. Figure 5.1 illustrates the processes for sequence generation for tour.
Figure 5.1 Planning Processes for Tour The flight team is sized for nominal operations, and anomaly staffing is done by augmentation with personnel (with spacecraft expertise) from the JPL technical divisions. Only a few specific contingency plans are developed (mostly dealing with launch and Earth flyby events). Identification and prioritization of these plans has been done as needed to reduce the risk to the mission within the cost constraints. This effort is documented in the Risk Management Plan. Updates to a sequence after it has been validated are limited. Changes to an instruments internal commands or instrument memory may be accomplished via the instrument-internal real-time command process and can range from the replacement of an entire block of instructions to the update of a few words in instrument memory. Updates to the tables which store the locations of various mission targets may also be uplinked if the spacecraft or target ephemeris has changed to refine pointing for planned observations. Tweaks to the stored sequence for other observation timing changes are also possible. These changes should be limited as much as possible, and must be approved by the sequence teams and/or the project manager. 5.1.3 DATA DISTRIBUTION Spacecraft and instrument housekeeping telemetry will be monitored in real-time for anomalies during all DSN tracks. Spacecraft and Facility Instrument health and safety are the responsibility of JPL and will be assessed in non-real-time. PI and Probe instrument health and safety are the responsibility of the personnel at the distributed operations sites and will be assessed by them in non-real-time. Science and engineering data packet is extracted from the downlink telemetry stream and stored in a centralized project data base at JPL. JPL is responsible for maintaining the integrity of the database contents and providing a catalog of everything on it. Personnel at the distributed operations sites query the database for data to be processed into higher level science products for analysis.
5-3
90 of 217
All public releases of data are coordinated through the Project Scientist or his designee. The Project Scientist ensures that JPL, NASA, ESA approval processes are initiated before data is released. Plans to release data on the web must also be approved by the Project Scientist. Public press conferences are planned to be held within a few days following quick-look analyses of data acquired during key events. At these press conferences, significant scientific results obtained from the near-real-time analysis of the data are presented. Science data is made available to the public one year after it is collected to allow time for the instrument teams to perform their own processing and analysis. 5.1.4 ACTIVITY OVERVIEW The mission design has a long (almost 7 year) cruise to get the spacecraft to Saturn and a 4 year tour in orbit around Saturn. During the cruise phase, the priority is placed on essential engineering, navigation, and science instrument maintenance, calibrations, and checkout. Some limited science collection is conducted, but is generally constrained to those activities required for tour readiness, or unique science opportunities that are in line with the program science objectives. A typical week in cruise would contain two downlink passes and have a handful of engineering activities as well as a low level of science observations. During early cruise, the spacecraft stays on Earth-point most of the time due to thermal constraints; in later cruise, the spacecraft may occasionally articlate to collect data from a particular target. Two years prior to Saturn Orbit Insertion, instrument activities and tour-related calibrations will increase in frequency. On a typical day in the Cassini tour, the spacecraft collects science data for 15 hours by orienting the spacecraft at a variety of targets. One instrument at a time controls the pointing of the spacecraft, and other instruments may ride along and collect data at the same time. Ride-alongs or collaborative data collection is often negotiated between the science teams. The remaining 9 hours is spent in one block on Earth-point, downlinking (or playing back) the data. During downlink since one axis of the spacecraft must be fixed to Earth - the spacecraft can only spin about the Z axis and collect fields, particles & waves data. This sweeping during playback allows three dimensional and temporal variations in the fields and particles environment to be measured. 5.2 TELECOMMUNICATIONS Telecommunications strategies are developed to use the three antennas (the HGA and two LGAs) to maximize science data return and visibility of the ground teams within the project and DSN constraints. Telecommunications with Cassini for the first 800-plus days of the mission is generally restricted to the spacecraft's low gain antennas (LGAs). During this time, it is necessary to use the high gain antenna (HGA) as a sunshade. Telemetry mode RTE-40 is used for most cruise downlink since it is generally the highest data rate achievable. Where advantageous, other modes such as PB&RTE-40, PB&RTE-200, RTE-948, RTE-158, or PB&RTE-948 are used when available and if Earth range and trajectory geometry permit. RTE-20 is the lowest data rate that the spacecraft will use for downlink in a non-emergency situation, whereas PB&RTE-40 is the lowest data rate available for playback of data from the SSR. The spacecraft transmits and receive through Low Gain Antenna 1 (LGA1) for the majority of the early cruise periods. LGA1 is preferred since the spacecraft does not have to be constrained in roll attitude as with LGA2, although the Earth-Spacecraft-Sun angle generally dictates which LGA is required. There is a 25 day period at launch plus 14 months when the EarthSpacecraft-Sun (EPS) angle is sufficiently small to allow use of the HGA for telecommunications. This is the first post-launch functional checkout of the science instruments. After the 25 days until early 2000, telecommunications must again use the LGAs at low rates (except very near Earth). 5-4
91 of 217
Following the switch to the HGA in February 2000, the telecommunications link capability is improved significantly and much higher rates are possible, allowing more data-intensive engineering and science activities throughout the rest of the mission. The normal DSN coverage for cruise is two passes per week, for spacecraft monitoring, data return and navigation. During the tour, when the Cassini telecommunications support requirement is one pass per day due to the high level of science activity expected. These basic coverages represent a general commitment of DSN loading. Specific requirements for DSN coverage are specified in the Project Service Level Agreement (PSLA). An estimate for Cassinis use of the DSN from 2001-2004 is shown in figure 2. 5.2.1 ANTENNA SWITCHES Antenna switch times are based on Earth range and on Earth-Spacecraft-Sun (EPS) geometry. If the EPS angle is greater than 44 degrees, LGA2 offers better downlink performance. However, if the EPS angle is less than 44 degrees, LGA1 should be used. LGA2 must not be used during probe checkouts due to its proximity to the probe and resulting interference. Table 5.1 defines the antenna usage periods for early cruise. Table 5.1 Antenna Usages (Year - Day Of Year) LGA1 Periods LGA2 Periods HGA Periods 97-290 to 97-299 97-300 to 98-174 98-362 to 99-021 98-175 to 98-361 99-063 to 99-230 00-032 to EOM 99-022 to 99-063 99-231 to 00-031 5.2.2 UPLINK During the encounter segment there is only one uplink data rate at 500 bps. The confidence level for uplink transmission is 99% or better. Generally speaking, the uplink signal is much stronger due to the much higher radiating power of the ground antenna. 5.2.3 BITS TO GROUND During cruise, telemetry is returned to the ground according to the (often limited) downlink capability, and is generally not heavily optimized due in part to a limited set of telemetry modes and tour capabilities which are still in development. During tour, however, much effort has been spent in selecting the data rates and DSN pass configurations to maximize the data return related to the projects primary science objectives.
5-5
92 of 217
User Loading Profile

Passes Per Week Week 1 2001 9 2 4 3 3 4 4 5 3 6 4 7 3 8 4 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 6 4 3 2 12 3
GWE test
5
SCE test
14
GWE test
7
SCO test
21
GWE
Jupiter Science wks 1-11 + TCM 17 in week 9
2002 15
GWE
12
21
15
21
GWE
TCM 18
Conjunction Exp
2003
21
GWE
21
21
21
18
AACS V A8 load & c/o
CDS V9 load & checkout
TCM 19
Conjunction Exp
GWE (moved earlier due to congestion)
2004
4
1/day @ S-3 mon
7 13
8 11 7
2005 7 16
Red is heavily contested. Blue is impacted.
FOIA 10-JPL-F-00451
93 of 217
Deep Space Network coverage of Cassini during the tour will consist of 1 pass per day from any one of the three main DSN stations (Goldstone, Canberra, or Madrid). Radio science measurements (e.g., occultations) will be accommodated on an occasional basis and will generally be added on top of the one pass per day schedule. The specific site used is chosen based on DSN workload, maximum downlink rate, conflicts with other missions, or other issues. Typically, however, the project will select Goldstone regularly since it has good downlink capability and using the same station allows for repeated activities (e.g. 15 hours collect, 9 hours downlink). Madrid also has good downlink rate and is desired by navigation to check for station-specific tracking biases. Canberra is undesirable due to its poor geometry and downlink rate. For the purposes of operational simplicity, the Tour DSN coverage has been classified into two categories: "high activity," presumably when the science opportunities are most intensive and require the most data to be collected, and "low activity," when the opportunities are more scarce or permit low data return. The science community has indicated that 1.0 Gbit per day for low activity periods and 4.0 Gbit per day for the high activity periods is adequate to achieve their science goals. To accomplish this, high activity periods are concentrated at targeted flybys and Saturn periapses, and take up about one quarter to one third of each orbit (refer to section 8). These passes are 9 hours in length and use a northern-hemisphere 70 meter station or 70/34 array. Communications is 2-way coherent at a 90% confidence level with ranging on. Low activity passes are also 9 hours in length and use northern hemishere 34 meter stations. Communications is also 2-way coherent at a 90% confidence level, ranging on. Furthermore, the project must work within the restrictions of the DSN and not overburden the network since coverage requests will come from other projects as well. Limited DSN station arrays may be used for the high activity periods and are available roughly 9 times per quarter. The specific placement of high and low activity passes is recommended by Science community as part of the Science Planning Process and is documented in the Science Operations Plan. During the tour, expected data rates for the spacecraft's HGA and 19W X-band transmitter are on the order of 14 kbps to 166 kbps. These rates vary due to the assumed telecom confidence level, the ground station configuration and the Earth's motion around the Sun, which affects the transmission range, and Saturn's motion around the Sun, which affects the declination of the spacecraft as seen from Earth. Earth's motion is by far the dominant geometric factor and is evident in the sinusoidal nature of the link performance. Since the link performance varies significantly with time, multiple data rates must be used as the performance changes or significant data return capability will be lost. In addition, the performance varies during a pass and multiple data rates per pass also increases telecom performance significantly (see figure 5.3).
Data Rate
Telemetry Pass
Ratio of 1/6 Time Used
2/3
1/6
Time
Figure 5.3 Multiple Data Rate Strategy Fourteen data rates compatible with the spacecraft information system have been chosen for the tour as listed in Table 5.2. These rates cover all expected ground apertures with a minimum of lost data return capability. 5-7
94 of 217
Table 5.2 Tour Data Rates (kb/s) 66.36 14.22 22.12 82.95 27.65 99.54 33.18 110.65 35.55 124.425 41.475 142.20 47.40 165.9 Higher rates of 199.08 and 248.85 kbps are available, but are not used because either they cannot be supported by the telecom link or because they are not needed to achieve the 4.0 Gbit daily return. Any slot that would be occupied by a high data rate would be better applied towards the lower data rate region to increase performance during low activity days. If a DSN pass is lost too late in the planning or execution process to alter the sequence safely, no steps will be taken to recover the data recorded on the SSR and the sequence is allowed to proceed as planned. The spacecraft continues operation as if the data are being received successfully, resulting in loss of these data as they are overwritten during the downlink period and the following observing period. Figures 5.4-5.6 show the downlink science data return in Gbit over the tour for Goldstone, Madrid, and Canberra (occasional Canberra passes may be required to resolve DSN conflicts). Nine hour passes are assumed, causing the jagged data returns, especially for arrayed antennas, since occasionally the top two data rates are not available for a full 9 hours, and occasionally the lower data rate is used less than the minimum of 45 minutes. In these cases, additional data return could be achieved by lengthening the duration of the pass beyond 9 hours, or reducing the time you collect data in the highest rate. Note that there are periods when 4 Gb of science is not achievable even at arrayed stations, ant there are periods of low activity when 1 Gb is not available from 34 m HEF antennas. 5.3 DATA STORAGE The principal purpose of the Solid State Recorders (SSRs) is to store science and engineering data during observation periods for playback during DSN passes, and to buffer FPW and engineering data during DSN passes for downlink during those same passes. The amount of data which can be recorded per period is primarily limited by the downlink capability of DSN stations. During most of cruise, only one SSR is needed primarily for engineering, but also to record maintenance, calibration, and checkout data, as well as limited cruise science. The other SSR may be turned off. During approach and tour, however, both SSRs may be on. Even though a majority of days during tour are expected to be low activity, requiring only one SSR, both SSRs are kept on to maintain a 4.0 Gbit storage and downlink capacity. Activity levels change several times per orbit, and cycling the SSRs on and off increases the ground workload and may impact the reliability of the SSRs. 5.3.1 PARTITIONING Table 5.3 shows the basic partition layout for the SSRs. Partitions 0-3 on each SSR are memory load partitions containing flight software. Each SSR can have up to 3 additional partitions used for telemetry. A CDS command edits partitions in the background sequence, enabling the number and size of telemetry partitions to be changed on a daily basis if needed. The minimum size of a partition in order for it to exist is one frame, or 8800 bits. The exception is the recording of Huygens data, which is duplicated on each SSR using a unique partitioning strategy. Refer to section 7 for details on the implementation of Huygens data recording. 5-8
95 of 217
Bits to Ground - Goldstone

5000
9 hour pass, optimum data rates
70ARR 4500
4000 70MET
3500
3000
2500
2000
1500 HEF 1000 BWG 500
0 2004-Jul
2004-Dec
2005-Jul
2006-Jan
2006-Jul
2007-Jan
2007-Jul
2008-Jan
2008-Jul
FOIA 10-JPL-F-00451
96 of 217
Bits to Ground - Madrid

5000
70ARR 4500
4000 70MET
3500
3000
2500
2000
1500 HEF 1000 BWG 500
0 2004-Jul
2004-Dec
2005-Jul
2006-Jan
2006-Jul
2007-Jan
2007-Jul
2008-Jan
2008-Jul
FOIA 10-JPL-F-00451
97 of 217
Bits to Ground - Canberra

3500
3000
2500
2000 70MET
1500
1000 HEF 500 BWG
0 2004-Jul
2004-Dec
2005-Jul
2006-Jan
2006-Jul
2007-Jan
2007-Jul
2008-Jan
2008-Jul
FOIA 10-JPL-F-00451
98 of 217
During cruise, typically one SSR with a single telemetry partition in circular FIFO mode is used to store and downlink all data collected, mixing engineering, housekeeping, maintenance, checkout and science data collected (see Figure 5.7). Engineering is recorded continuously at a rate of 1637 bps. At this rate, one SSR can store up to 14 days of data (assuming a capacity of 2.0 Gbit). During cruise, the least frequent DSN passes occur once per week. The SSR therefore would record up to 7 days of data between the least frequent downlinks, filling half of its capacity. During a DSN pass at greater than 20 bps downlink rate, along with real-time engineering, selected data from the SSR can be played back if desired. At 20 bps (the minimum planned downlink rate) only real-time engineering can be sent to Earth. At the end of the pass, the pointers are not reset and the SSR continues to record where it left off. P
up to 7 days' worth of engineering-only space remaining
Sci & Eng Partition

7 days (max time between DSN passes) of engineering recorded
R Figure 5.7 Cruise One-Partition SSR Management When a fault has occurred, at least 7 days (which is also the maximum time between passes) of data collection is guaranteed. This strategy allows time for the ground to make arrangements to receive fault protection data and engineering data before or after the fault to analyze the problem. If the spacecraft is not directed otherwise, it stops recording data once the record pointer hits the playback pointer. Certain variations to this basic cruise strategy are likely to be implemented. Preservation of data on some portion of the SSR for extended periods may be needed when the downlink data rate is too low to support normal operational procedures. This includes the second Probe Checkout, science activities for both Venus and Earth encounters, and maneuvers. However, during the HGA period at approximately launch + 14 months, the downlink data rates are high enough to return a significant portion of the SSR (if not all) on each pass. This allows more data-intensive operations such as probe checkout, instrument checkout and detailed engineering calibrations. During the later portion of cruise and tour, once the final flight software is uploaded, the SSRs are configured to use multiple partitions. Engineering data, optical navigation images, and/or high value science data can be routed to specific partitions and preserved separate from general science data for priority or multiple playbacks. For tour, partition 4 is used as the primary day-to-day telemetry partition (see Table 5.3), and is sized to 1788 Mbit. Engineering data stored during observation periods does not need to be downlinked every day, so it is routed to partition 6 at 1623 bps. Some engineering, however, is required to reconstruct pointing, etc., and this data is duplicated in partition 4 during observation periods at a lower rate of 718 bps. 5-12
99 of 217
Partition 6 is sized to hold 25,596 frames of engineering data (225 Mbit). This size guarantees that no engineering data is overwritten as long as there is one pass per day (at any complex). If passes are skipped, the duration of recording to any one SSR must not exceed 39.5 hours over two consecutive observations periods in order for engineering data to be preserved for fault diagnosis. For example, if both SSRs are filled at an even rate during a 48-hour observation period, each SSR is only used for 24 hours. If the subsequent observation period only uses one SSR, and the duration of that observation period exceeds 15.5 hours, some engineering data may be unrecoverable if a fault should occur during these two days. Note that the size of partitions 4 and 6 total 2013 Mbit, the total volume on each SSR usable for telemetry. Partition 5 is set aside for optical navigation. This data is routed via a telemetry mode overlay command. Once the OPNAV data is complete, an additional telemetry mode overlay command is sent to restore the data flow to its original form. New telemetry modes for each permutation of data routing are not required; the overlay command is sufficient to reroute specific instruments data to the appropriate partition. If partition 5 is used, its volume must be taken from partition4. OPNAVs are taken with the ISS NAC, using lossless compression and no encoding. ach NAC file is 1027 rows x 1036 columns x 16 bits (the first three rows, and the first 12 columns of all subsequent rows contain header data). Therefore, the maximum file size for these images is 17.0 Mbit. Recent in-flight performance of the lossless compressor on OPNAV-like images has been estimated at over 7:1. To size partition 5, 4:1 compression should be assumed, with each OPNAV occupying 4.26 Mbit or 484 SSR frames. Refer to the guidelines & constraints in section 8 for some details on how SSR management is implemented. # 0 1 2 3 4 5 6 Table 5.3 Tour SSR Partitioning FUNCTION SIZE DEFAULT MEM. LOAD 1 30 Mbit DEFAULT MEM. LOAD 2 30 Mbit NEW MEMORY LOAD 1 30 Mbit NEW MEMORY LOAD 2 30 Mbit TELEMETRY (SCIENCE & ENGINEERING) 1788 Mbit TELEMETRY (OPNAVS FOR TOUR ONLY) 0 unless needed (tour only) TELEMETRY (ENGINEERING FOR TOUR ONLY) 225 Mbit (tour only)
During downlink, all data recorded can only be written to the active partition being played back. This is required in order for the CDS to retrieve data from the SSR as quickly as possible (i.e. from only one partition at a time) to support the high downlink rates during playback. When more than one SSR is required (e.g. high activity day), data recording will switch from one SSR to the other only when partition 4 becomes full. The sizing of the other partitions, if used, should be done to ensure that they do not fill up before partition 4 (or data will be lost). Optimizing partition sizing should be avoided whenever possible to minimize operations complexity; instead, partitions should be sized the same on each SSR and with sufficient margin to allow for stochastic data collection. 5.3.2 DATA POLICING The limitations on downlink capability and SSR volume, as well as the non-deterministic nature of many of the instruments' data collection rates implies the need for control over the amount of data each instrument can place on the SSR. Data volume is set aside each day for OPNAVs, when needed, and engineering, and whatever remains of the downlink capability can be determined and allocated among the science instruments. The science office determines 5-13
100 of 217
the allocation process and assigns volume on a per-instrument basis as a function of time, including instrument housekeeping data. Once these allocations are uploaded to the spacecraft, they are activated in a background sequence when observations start, and are then enforced by CDS. The CDS is responsible for protection of instrument data and ceases to record data from an instrument which has exceeded its allocation. Navigation OPNAVs, when taken, are implemented as supplements to the ISS data allocation. The CDS has room for 90 data allocation tables, allowing for 44 days of SSR management with one uplink of these tables. (Separate tables are used for both observation and downlink periods, and two tables are set aside for support imaging and OPNAVs.) 5.3.3 CARRYOVER During low-activity periods, there will occasionally be a need to collect more data than can be downlinked in a single low-activity pass. This option is desirable during extended low-activity periods when prime science opportunities are unevenly spaced. The amount of data which can be taken during the observation period immediately preceding a given downlink period is usually assumed to be equal to the downlink capability of the pass minus the FPW and engineering data collected during the pass (after accounting for R-S encoding). However, if it is desirable to take more data during a particular observing period, this can be done by borrowing data from subsequent observing period(s). The total amount of data which can be taken over these multiple observing periods is still fixed, and limited to the total capability of the multiple downlink periods minus the FPW and engineering data collected during those downlink periods. 5.3.4 DSN LOCKUP DSN lockup during tour is theoretically predicted to be on the order of seconds; however, during cruise lockup has typically taken several minutes. In order to prevent data loss, the playback of data at the beginning of a pass (as well as during data rate or coherency changes) should be avoided. During cruise, the technique for preventing data loss is to snap and restore the pointer after 15 minutes of playback to the start of the partition. This duplicates the playback of the first 15 minutes of data and accommodates an equivalent lockup time. Once the tour flight software is loaded, however, a playback pause capability is implemented which halts SSR playback for a fixed amount of time whenever a new telemetry mode is activated. This time can be uploaded as a parameter and can be used to accommodate DSN lockup, data rate, or coherency changes. During playback pause, the transmitter still sends data to the ground at the expected rate, but only real-time engineering and fill frames; no data from the SSR is sent to the ground. Figures 5.8-10 illustrate the SSR recording and playback methods for tour. Data storage must meet two key requirements: data collected during observations periods must not exceed the volume that the SSR can store, and data collected during the observation + downlink period that is intended for playback must not exceed the downlink capability of the DSN pass (unless data is carried over). 5.4 ATTITUDE CONTROL Attitude control of the spacecraft is maintained through the use of the RCS thrusters and the reaction wheel assmblies (RWAs), while attitude determination is controlled through the star trackers, inertial reference units and sun sensors. Most of the attitude control resources are used merely to maintain a constant attitude, limit cycling between the bounds of the pointing requirements. External influences also require attitude control, and the two largest contributors are RTG radiation and solar radiation torques. 5-14
101 of 217
LOW ACTIVITY DAY (1 SSR) PR

PR
START EMPTY A4 = science partition with duplicated subset of engineering data (e.g. AACS, RFS) required for playback. Circular FIFO allows free recording up to data played back and is required if any data is to be held over to next pass.
CIRC FIFO
A4
A5
OP NAV
SCI + AACS
A6
CIRC FIFO
PR
A5 = OPNAV partition. Circular FIFO allows for MAPS data to use up OPNAV space after playback. Sized to volume of contents plus playback buffer for data recorded in A5 for each downlink. 4.26 Mb each OPNAV (484 frames) which assumes compression of 4:1 or better (>7:1 performance has been observed in flight on OPNAV-like images). A6 = engineering partition. Sized to hold 39.5 hours, needed for anomaly recovery. Ring buffer allows engineering to be recorded without pointer management. After safing, fault protection may route post-fault engineering to A4. RECORD All engineering in A6 at 1623 bps and science & a duplicated subset of engineering in A4 at 718 bps, plus HK at up to 239 bps. OPNAVs are routed to A5 by telemetry mode overlay command.
ENG RING BUFFER P
A4
A5
R
OP NAV
SCI + AACS
A6
ENG
A4
R P
A5
OP NAV
PLAYBACK In order as shown. A6 is never played back unless needed for anomaly diagnosis. All data collected during playback (including ENG at 1623 bps) must be recorded in active partition ONLY. Therefore, playback buffer in A5 must be bookkept for each downlink as illustrated to prevent data loss. Playback pointer is paused at start of downlink and at data rate changes for DSN lockup; record pointer is free to continue.
POST-PLAYBACK
ENG
R P
SCI + AACS
1 A6
P
2
R
Resize partitions if needed (and no carryover). Reset partition 4 and 5 pointers to start of partition.
D. Seal 10 May 2002
FOIA 10-JPL-F-00451
102 of 217
HIGH ACTIVITY DAY (2 SSRs) A4 PR A5

PR
B4
PR
B5
PR
START EMPTY Parition map for each SSR must always be identical in case of unexpected SSR swaps. Also, size partitions on each SSR to equal volumes whenever possible for ops simplicity. Stochastic compression or unforseen problems makes SSR swaps variable, so A5 or B5 must be able to contain entire volume of OPNAVs (plus playback buffers). Paying twice in storage capacity only limits science if SSRs would otherwise be completely filled; this is unlikely since OPNAVs will almost always be recorded on low activity days.
OP NAV
OP NAV
SCI + AACS
A6
PR
SCI + AACS
B6
PR
ENG
ENG
A4
RP
A5
B4
B5
RECORD SSR swap is triggered when one identified partition becomes full. This partition should always be A4/B4. If A5/B5 are sized to each contain the full volume of OPNAVs (plus playback buffers), they will never fill up before the swap. Otherwise, data will be discarded.
OP NAV
OP NAV
SCI + AACS
R A6
P R R ENG
SCI + AACS
B6
P R ENG
A4
PR
A5
OP NAV
B4 R P
B5
OP NAV
PLAYBACK In order as shown. If A5/B5 are not used, the record pointers and playback pointers will be at partition start and the partition will just be skipped. High-rate MAPS data collection must wait until after start of A4 playback so there will be SSR space for the data. Pause of playback pointer for DSN lockup occurs before playback order is asserted, so downlink starts on last partition B4 with room to record and only switches to filled A4 when playback resumes.
POST-PLAYBACK Resize partitions if needed (and no carryover). Reset partition 4 and 5 pointers to start of partition.
D. Seal 10 May 2002
SCI + AACS
1
PP R
A6
SCI + AACS
2 B6
P
P R
ENG
ENG
Note: the1-SSR strategy can be implemented identical to this one; some partitions would just not be used. Only day-to-day variations in OPNAV volume require special handling.
FOIA 10-JPL-F-00451
103 of 217
2 LOW ACTIVITY DAYS (1 SSR) WITH CARRYOVER A4 PR A5

PR
START EMPTY As usual: A4 = science + some engineering. A5 = OPNAVS. A6 = all engineering. R
A4
A5
OP NAV
POST-PLAYBACK
Usual is reset pointers in partitions 4 & 5. If carryover, do not reset any pointers. This is the only change in operations needed to acommodate carryover!
OP NAV
SCI + AACS
CIRC FIFO
A6
CIRC FIFO
PR
SCI + AACS
A6
PP
ENG RING BUFFER P
ENG
P
R
A4
A5
RECORD #1
As usual, record pointers move ahead.
A4
R
A5 R SCI + AACS
OP NAV P P
RECORD #2 As usual. Data carried over in A4 + new data recorded must not exceed partition capacity (of A4 + B4, really).
OP NAV
SCI + AACS
A6
R P
A6
R
ENG
ENG
P
R
A4 R SCI + AACS
A5
OP NAV R
PLAYBACK #1 As usual, in order shown, except data left on A4. Downlink capability must be adequate to downlink all of A5. All data recorded during downlink is stored in active partition as usual.
A4
R P
A5
OP NAV
PLAYBACK #2 As usual, in order shown. All data on A4 & A5 downlinked.
1
P P
A6
SCI + AACS
P R A6
R P
1
POST-PLAYBACK Resize partitions if needed. Reset partition 4 and 5 pointers to start of partition.
ENG
ENG
2
R
D. Seal 10 May 2002
FOIA 10-JPL-F-00451
104 of 217
5.4.1
SPACECRAFT ARTICULATION
Turns during cruise are typically done using the RCS system to save the reaction wheel lifetime for the tour period and to allow faster turns to minimize thermal exposure when turning off the Sun line. In situations where the fastest possible turns are required (e.g. for thermal constraints), sprint turns are available at higher rates with degraded pointing accuracy. Turns on thrusters generally take minutes, while turns on wheels can take up to an hour. Finer pointing control is possible with wheels, however, so the need for fast turn times and fine control must be balanced on a case by case basis. Care must be taken to ensure that orientations during turns do not violate thermal constraints or place the Sun, planets or satellites in the boresights of the star trackers and, in some cases, instrument fields of view. Spacecraft resources which are used for turns, mosaics, and target body motion are divided into two groups: torque, which determines the angular acceleration of the spacecraft; and momentum, which determines the maximum rate achievable by the spacecraft. Either resource can limit spacecraft capabilities. For the reaction wheels, the power allocated and some relative balance determines the maximum torque and momentum; for thrusters, the torque is a fixed quantity determined by the thrust provided by the RCS. Momentum (maximum rate) available on the thrusters is tied to the star tracker limits, and to a lesser extent, the propellant required to stabilize the spacecraft during its rotation. Reaction wheels require unloading due to external torques applied to the spacecraft by solar pressure, RTG pressure, etc. During unloads, the thrusters control the spacecraft attitude while the wheels are spun up or down to the desired rate. The reaction wheels must be unloaded (or re-biased) every 15 days, during a tracking pass so the activity can be monitored in real time and the resulting delta-vee measured via navigation tracking. In addition, a re-bias should be placed on the last pass of each sequence to set the wheel speeds properly for the next sequence. The time required to unload the reaction wheels is approximately 15 minutes. For the reaction wheels, mosaics typically use very small turns between frames that never reach the maximum spin rate of either the spacecraft or reaction wheels. Therefore, most of the power can be allocated to torque (i.e., acceleration) to minimize the time required for each mosaic. On the other hand, target turns (e.g. Saturn to Earth) usually spend a lot of time coasting at the maximum rate (determined by momentum). Reaction wheel capabilities are further complicated by variances between wheels, the fact that they are canted with respect to the body axes of the spacecraft, and they operate at various speeds depending on the orientation, biasing at the last reaction wheel unload, and external torques placed on the spacecraft. Each wheel has slight differences in its operating conditions; turns about different axes burden the wheels in different proportions; and the moment-tomoment spin rates of the reaction wheels which indicate how much authority each has available varies with time and the past conditions. For these reasons, articulation capabilities for planning must be selected carefully with an appropriate across-the board margin policy so that the science observations are not too limited, but the risk of not completing a turn is minimal. Typically, turns about the Z axis provide the best performance. This is due mainly to the fact that the spacecraft moment of inertia is lowest about Z. For reaction wheels, Z axis turns are shared equally between all three wheels which also provides some advantage. 5.4.2 TARGET MOTION COMPENSATION Target motion compensation is required for some of the highest value science near close flybys when satellites and features must be tracked as they move across the sky quickly. Without TMC, images would be smeared and data corrupted unacceptably. Naturally, the closest encounters can provide the highest potential resolution for images and the strongest 5-18
105 of 217
measurements of fields, particles and waves, but these flybys also have the highest target motion. During a flyby, each of the two available resources (torque and momentum) must be divided between TMC and any science articulation. As the satellite rate or acceleration increases, more momentum and torque must be devoted to TMC, and less is available for other science turns. If the maximum rate or acceleration limits are reached, no resources are left for science turns. If rate or acceleration limits are exceeded, the target body may move too fast for the science instruments to take advantage of the close encounter. When the spacecraft is engaged in target motion compensation, well-planned science turns can be oriented so they subtract rather than add to the target body rates. In other words, if the target motion should be used to turn from one position to another, rather than requiring the wheels to fight against the target motion. For example, a row of images starting on the leading edge (as seen from the spacecraft) and finishing at the trailing edge will allow the spacecraft to slew from frame to frame by simply compensating less for the target body motion. 5.4.3 TITAN ATMOSPHERIC MODEL Titan's atmosphere is primarily comprised of a handful of constituents, each of which can be modeled in a formula which approximates the atmospheric density as a function of height from the surface. This formula contains several terms, one for each main constituent, and is based on the PSG endorsed atmospheric model developed by Yelle in 1993-94. A relatively simple formula is possible because Titan's atmosphere is close to isothermic in the Yelle model at the altitudes of interest for this problem (i.e., 800 - 3000 km). At these altitudes of interest, Titan's atmosphere is comprised mainly of nitrogen, methane and argon. Therefore, there are three terms in the equation, as follows: (z) = 6.35x10
6
11400(z 76) 8030(z + 429) 15000(z 44) T(z +2575) + 5.13 x107 e T(z + 2575) + 7.35x105 e T(z +2575)
where (z) is the atmospheric density in g/cm3, z is the altitude in km, and T is the stratospheric temperature in Kelvin. Note that this formula is only valid for altitudes between 800km and 3000km. The formula is accurate to within 1% of the altitude in this region. The first term is for nitrogen, the second for methane, and the third for argon. The temperature variation arises only with different confidence levels; again, Titan's atmosphere is isothermic at these altitudes, but what temperature it is fixed at is uncertain. To determine the temperature, the formula T = 175 + 10 is used, where is the gaussian variable; i.e., = 1 equals a 1-sigma uncertainty (T = 165K or 185K). Gamma is greater than zero for denser atmospheres, and less than zero for sparse atmospheres. 5.4.4 MINIMUM FLYBY ALTITUDES Many of the low (< 4000 km) Titan flybys will be allocated to RADAR, when the thrusters will control the spacecraft attitude; most of the remainder will require reaction wheels, particularly for remote sensing. Both target motion compensation (TMC) and maintaining attitude under atmospheric torque must be possible for the flyby to be useful to the science investigations. Since target motion compensation is required for smear-free imaging of Titan, the reaction wheel or thruster capabilities must be split between atmospheric compensation and TMC. The minimum flyby altitude can therefore be constrained by either of two formulae: that for torque, which has contributions from both TMC and the atmosphere; and that for momentum, 5-19
106 of 217
which affects the spin rates of the wheels, and has a transient contribution from TMC and a lasting one from the atmosphere. RADAR passes currently use the reaction control thrusters which, compared with the reaction wheels, exerts a strong control over the spacecraft attitude and can rotate it rapidly. However, at the lowest planned altitudes ( 950 km) Titan's atmosphere becomes a significant source of spacecraft torque. Minimum altitude limits must be set based on the atmospheric model and thruster torque capability. Violating these altitudes will place the spacecraft in an environment where it cannot control its attitude to the desired target(s) for RADAR science. Significant deviations lower than the altitude limits will jeopardize the safety of the spacecraft. Titan's atmosphere, like any, is exponential in nature and has a scale height of about 70 km at the altitudes of interest (this is the altitude required to see a change in density of a factor of e, or 2.7x). Therefore, limit violations as low as tens of kilometers can require significantly higher control torques. One option, besides changing the ORS balance between torque and momentum, which might increase the available momentum is "biasing" the wheels. The momentum available is a vector and not a scalar value. In other words, any momentum limit is defined from 0 Nms in either direction. Since the momentum that the wheels will compensate for is predictable in direction it may be possible to "bias," or pre-spin the wheels in the opposite direction to compensate. This strategy could potentially double the available momentum. Official minimum altitudes: TBD (under active study by Mission Planning and AACS). 5.5 NAVIGATION The main objective of navigation is to maintain the spacecraft on the planned trajectory for the duration of the nominal mission. Secondary objectives of the navigation effort include minimizing the operational complexity of its related activities and the delta-vee required to maintain the correct trajectory. Unlike other missions, the trajectory design will not be reoptimized continuously. Every effort will be made to maintain that trajectory and not replan a new path. While Cassini is in the inner solar system, the focus is on achieving the three planetary flybys and satisfying the Earth swingby requirements. The Earth impact probability, required to be less than one in a million, is controlled by biasing the trajectory away from the Earth until the final pre-Earth maneuver. After the Earth flyby, the long Earth to Jupiter and Jupiter to Saturn legs are rather uneventful. During the Saturn approach phase, the nav team calibrates and understands the optical portion of the navigation system and places the spacecraft on the proper trajectory for the Phoebe encounter and SOI. In tour, the nav system controls the spacecraft trajectory on the nominal tour, and updates the tour trajectory only to account for expected variations in parameters such as satellite ephemerides and the Titan atmospheric density. Also during tour, the nav team is responsible for providing accurate predicted and reconstructed spacecraft and satellite ephemerides. 5.5.1 TRACKING REQUIREMENTS Navigation primarily uses DSN tracking during cruise and tour to collect two separate types of tracking data as follows. Ranging is derived from a modulation on the uplink which is processed by the spacecraft and remodulated onto the downlink carrier. The ranging channel competes with the telemetry channel for power and in intervals of low telecom performance, telemetry modulation must be turned off in order to achieve satisfactory ranging performance. Coherent Doppler requires a 2-way coherent X-band link and is a measure of the total frequency shift of the up- and downlink carriers. The spacecraft receives the carrier 5-20
107 of 217
from the ground and multiplies that frequency by a fixed ratio to derive the downlink carrier frequency. In addition to DSN tracking, optical navigation is used during approach and tour and provides a measurement of a satellite against a fixed stellar background. The images taken by the imaging cameras directly support the estimation of not only the Cassini spacecraft ephemeris but also the positions of the satellites, particularly early in the tour. OPNAVs complement the radiometric doppler and ranging measurements in orbit determination. Operational measurements begin during Saturn approach and continue throughout the duration of the mission, but are needed less often after the first year of the tour. Initially, between 4 and 8 images per day are taken for the first few Titan flybys with the number of images decreasing as the ephemerides converge. The number of images increase when approaching icy satellites for the first time. During the first two years of the mission, DSN tracking can always obtain the Doppler data, but obtaining the ranging data is complicated by a number of competing requirements. The spacecraft is normally sun pointed which requires that the communications be accomplished using the low gain antennas (LGAs). The performance characteristics of the LGAs create problems with the acquisition of range data. Navigation requires Doppler and ranging data from both northern and southern hemisphere tracking stations. The spacecraft analysis team requires telemetry at least once per week.
During this portion of early cruise, there are several periods where telemetry both types of tracking data are not achievable and must be accounted for. During later cruise, the spacecraft geometry is changing more slowly and HGA communication is possible. Tracking 1-2 times per week is sufficient to maintain acceptable knowledge of the spacecraft trajectory. On the long Jupiter-Saturn leg (the quiet and science cruise phases), orbit determination is only needed on a quarterly basis. During tour, most navigation tracking is tied to the schedule of close satellite encounters. Preencounter tracking in part supports the flyby targeting maneuver which places the spacecraft in the final flyby trajectory. Post-encounter maneuvers are required only for Titan as a result of its gravitational effect on the trajectory. Since the nominal DSN coverage is one pass per day during tour, tracking that rides along whenever these passes are desired by science may be acceptable. The tracking strategies as agreed to by SCO are as follows: 2-way doppler: 6 hours per day, in 2 hour time periods Ranging: on for all passes Complexes: 1 hour per day, on average, from an alternate DSN complex; tracking four times evenly spaced betweeen targeted encounters (e.g. Goldstone passes every day, with a 9-hour Madrid pass every 9 days on long periods between encounters) Maneuvers: 2 hours of 2-way doppler and range within 4 hours of maneuver, both before and after execution
For optical navigation during approach and tour, once the overall requirements for optical navigation are known, a super set of opportunities is generated that pass all of the pointing and timing constraints. Each opportunity is a unique image and specifies the time of the image, its target (typically a star) and the satellite also being imaged. The super set contains extra images (e.g. 25%) in order to allow flexibility in the science planning process. Requests for OPNAVs are submitted through the Cassini Information Management System (CIMS) as engineering activities. The narrow angle camera is the primary instrument for OPNAVs although the wide angle camera can also be used. 5-21
108 of 217
Navigation then participates in the planning process and is responsible for assuring that the images approved in the final sequence meet the nav requirements, and that the details of each observation start/end times, turns, camera parameters, etc. are properly included. Pointing constraints are checked and ride-alongs are coordinated. The real-time execution of the OPNAVs is monitored and the images are acquired at the beginning of the next downlink pass for processing. 5.5.2 MANEUVERS During the inner solar system cruise, typically three maneuvers are required between consecutive encounters; the first to clean up the dispersions caused by the first flyby, and the next two to assure accurate delivery to the next encounter. In the later portions of cruise, the trajectory requires very infrequent maneuvers. However, flushing maneuvers of at least 5 seconds in duration are required to flush the wet portion of the propellant valves of the main engine every 400 days. To maintain at least one maneuver every 400 days, several maneuvers have been added to the schedule and are accommodated in the navigation plan. These flushing maneuvers ensure that oxidization of iron alloys in the bipropellant feed system do not build up long enough to plug the small orifices of the valves. Maneuvers have two components of delta-vee: a deterministic (or pre-planned) component, and a statistical component required to clean up dispersions to maintain the correct trajectory. Cassini can execute maneuvers using either the main engines or the Reaction Control System (RCS) thrusters. Generally, delta-vees larger than a crossover point, currently at 0.7 m/s, are done with the main engine since the main engines have a higher thrust than the RCS thrusters and can impart higher V in a shorter period of time. The crossover point is selected within limits to share the delta-vee burden between the bipropellant and monopropellant systems. Ideally, Cassini should run out of each propellant at the same time in the extended mission (save for any hydrazine left over for continued attitude control). Since both main engine and RCS burns require RCS attitude control, all maneuvers require that the catalyst bed heaters be turned on prior to the start of the burn. Main engine maneuvers require REA heaters on for 12 hours before the burn. During each burn, the main engine nozzle gimbals control the engine to apply thrust as closely as possible in the direction of the center of mass of the spacecraft. The EGAs are stowed in the same position every time. For each main-engine maneuver, the MEA cover must also be opened before the maneuver and closed afterward in order to minimize micrometeoroid exposure of the sensitive engine nozzles. The maneuver will not proceed unless this is verified on the ground and a go command is sent to execute the maneuver block. The cover is closed after the engine burn, following an appropriate cooling period. The total open time is usually six to seven hours per main engine maneuver. Both types of burns must be at least one second in duration; the minimum resolution for a main engine burn is 8-12 cm/s. During cruise, all maneuvers have continuous coverage for three DSN passes centered on the burn. The SSR will record maneuver data during the time the spacecraft is off-Sun. During early cruise where HGA communication is not possible, up to seven passes at 40 bps downlink (20 bps SSR playback) are required to play back all recorded TCM data. As a result, only the off-Sun data is played back. Sprint turns may be used when they are necessary to meet the thermal constraints. A sprint turn to the burn attitude can take as long as 7 minutes each way. The total off-Sun time for a burn includes the turn to the burn attitude, a settling period of approximately 5 minutes, the actual burn time, a burn settling of 2 minutes, and the turn back to Sun-point. During cruise, maneuver backup dates are typically 14 days after the scheduled maneuver when time allows. The T18-5 tour selected for the Cassini mission places new and significant requirements on the execution of maneuvers. Control of the trajectory requires at least three maneuvers be scheduled between each targeted encounter of Titan or an icy satellite. The scheduled dates, as 5-22
109 of 217
follows, were chosen to balance the V budget with operational constraints on placing maneuvers close to flybys. Encounter Cleanup - scheduled at each targeted Titan encounter + 3 days . This maneuver corrects for most errors in the flyby and may provide some or all of the changes required to achieve the next flyby. Generally these are statistical maneuvers. Near Apoapsis - scheduled near apoapsis on the orbit between the targeted encounters. This maneuver sets up the trajectory to achieve the next targeted encounter. In many cases this maneuver has a significant deterministic component. Approach Targeting scheduled at each targeted encounter 3 days. This maneuver is usually statistical and cleans up any residual errors from the apoapsis maneuver in order to achieve an accurate delivery to the next encounter.
In order to maintain the spacecraft on the tour within the available propellant, it is necessary to execute both the cleanup maneuver and the near-apoapsis maneuver. The maneuvers may be delayed by a day or two with only a modest increase in the propellant cost, but skipping a maneuver could required a tour redesign due to propellant availability. The criticality of the approach targeting maneuvers depends upon the achieved accuracy of the near apoapsis maneuver. Also, the reference tour includes a significant number of 16 day orbits. With only 16 days between targeted encounters, a maneuver must be accomplished, on average, every 5.3 days. This maneuver frequency implies that maneuvers can occur on any day of the week and at any time of day. With only a few days between maneuvers, the time to evaluate the results of a maneuver, determine the post-maneuver trajectory and plan the next maneuver is at premium. With more than 150 TCMs planned for the tour, efficient and consistent planning and execution is necessary. All maneuvers will be executed during a single DSN tracking pass with the maneuver minisequence uplinked twice at the beginning of the pass. In case of a bad uplink or execution, there is insufficient time to retry the maneuver and the backup pass must be used. In this case, the OD solution will not be recalculated, but the maneuver will simply be replanned for the following day using the same trajectory. Two-way doppler tracking data is collected before and after the maneuver (in general 2-way tracking will be lost during the maneuver). The engineering telemetry recorded during the maneuver is played back immediately after the maneuver. For icy satellite flybys, targeting maneuvers before the flyby are also required but typically cleanup maneuvers after the encounter are not required, since the satellites gravitational effect on the trajectory is negligible. Occasionally there are maneuvers scheduled on the day after icy satellite flybys. These maneuvers are primarily deterministic and are implemented as canned maneuvers; no quick replanning of the maneuvers is conducted just after the flyby. The maneuver parameters and mini-sequence is automatically generated by a small 2 person subset of the navigation team. This team has the responsibility for generation of the final orbit determination solution, generation and validation of the mini-sequence and transmission of the command file to the ACE for uplink. The generation and validation of the input files necessary for the execution of the automatic maneuver generation software is accomplished by the individual SCO and ULO team members during standard working hours. A typical maneuver timeline is shown in Figure 5.11. Refer to section 2 for a list of all planned maneuvers during the mission. 5.5.3 ENCOUNTER REDESIGN The project has adopted a strategy for selecting a minimum altitude for Titan flybys and considering redesign of flyby aimpoints. This strategy is needed to assure efficient use of 5-23
110 of 217
propellant and to address the potential need to raise or lower the closest approach altitude at several flybys for spacecraft safety and/or INMS science. The design minimum Titan flyby altitude on thrusters is 950 km. This altitude is selected such that the chance of the atmosphere being too dense for the thrusters to maintain attitude control is 5%. If the atmospheric model is more dense than expected, and is refuted by in-situ measurement of the Titan atmosphere during early, higher flybys, then this altitude will have to be increased. For the first 950 km altitude flyby of Titan, two trajectories and sequence plans are developed in parallel, one at 950 km (the baseline) and one at a higher altitude of 1065 km guaranteed to be safe under any possible atmospheric conditions. Both trajectories and sequence plans are canned long before the encounter; after the atmospheric density is measured on the first Titan flyby, a decision is made on which plan is used. If the atmosphere is found to be less dense than expected, future encounters may be lowered to meet INMS science objectives. 5.6 ENVIRONMENTAL HAZARDS & CONTROL During the mission, the spacecraft is exposed to a variety of potentially hazardous environments. Careful planning is required to not only ensure that spacecraft health and safety is not compromised, but that creative solutions are developed to balance the risk from these hazards against the scientific objectives when they conflict. 5.6.1 RADIATION Radiation design for the Cassini spacecraft was created using the back-up mission trajectory (March 1999 VEEGA- Venus-Earth-Earth Gravity Assist), because the radiation environment for this mission is the most severe of any of the possible interplanetary trajectories. A radiation design margin of 2 for ionization dose, displacement damage and integrated peak flux was therefore used for all engineering subsystems, bus science electronics, imaging science instruments and the Huygens probe. Science instruments were required to operate with a radiation exposure of 100 krad. 5.6.2 THERMAL CONTROL AND SUN EXPOSURE There are several general pointing orientations which expose sensitive components of the spacecraft to undesirable thermal input. This radiative heating can potentially degrade performance or violate safety constraints. The primary source of thermal input at Saturn is the Sun; however, heating from Saturn and its rings, particularly when lit, and the satellites during close approaches are of concern as well. To maintain thermal control during cruise, the spacecraft HGA must remain Sun-pointed for virtually all of its travels in the inner solar system. Off-Sun orientations are possible for short periods of time, as listed in table 5.4, and these durations can be scaled with the square of the Sun range. For example, at 0.61 AU the spacecraft could withstand a transient off-Sun duration of 0.5 hours/day. At 0.8 AU, however, the spacecraft could turn 180 off-Sun for a scaled duration of about 0.9 hours once/day. For all these off-sun events, the roll angle is restricted so that the sun line lies in the -X (Probe) side of the X-Z plane. For more information about allowable off-Sun durations, consult CAS-3-210. Continuous off-Sun Sun Range 0.61-2.7 AU** 2.7-5.0 AU >5.0 AU Table 5.4 Thermal Capabilities Transient off-Sun exposure at range Range 0.61 AU 1.0 AU 1.0 AU Off-sun angle 180 180 <60 Duration 0.5 hours* 1/day 1.35 hours* 1/day 4.0 hours* 1/day
Off-sun angle 2.5 Earth point OK (unrestricted)
*Durations include turn times. **Earth-point OK for 25-day Instrument Checkout.
5-24
Example Nine Hour OTM Pass

Op Mode transition
Maneuver block*
6 hours
Op Mode transition
Spacecraft Event
DFWP-TCM, Spin
off-Earth
1:30 hr OWLT
DFWP-TCM No Spin
Earth Receive
BOT EOT
= Health & safety check + maneuver uplink = Two-way Doppler = Science downlink = Engineering downlink
A 9-hour OTM pass gives: A 9-hour OTM pass gives: > 1:41 hr for verifying s/c health & safety > 1:41 hr for verifying s/c health & safety and uplinking the maneuver and uplinking the maneuver > 7:33 hr science downlink > 7:33 hr science downlink 2:20 hr two-way Doppler before and after 2:20 hr two-way Doppler before and after maneuver maneuver 15 min OTM engineering data playback FOIA program 15 min OTM engineering data playback Posted Courtesy of the NASA
= assuming worst case (longest) maneuver block length of 2:44 hr.

FOIA 10-JPL-F-00451
24 Apr 02
112 of 217
During the later portions of cruise and tour, however, there are performance implications of sun exposure which must be considered. There are three major "exclusion zones" which thermal energy sources should be kept from: the SRU boresights (+X direction), the optical remote sensing instrument boresights (- Y direction), and the cryogenic instrument radiators hemisphere (also centered along +X). First, the SRU performance can be seriously degraded from thermal input within a 30 cone. A gyro-only mode, in which the spacecraft calculates its attitude without the SRU, may be available for short periods of time. Second, most of the remote sensing instruments report some performance degradation from thermal input within a ~15 cone. Third, the cryogenic instrument radiators have hemispherical fields of view and share their exclusion zone with the SRU boresight zone (actually encompassing it completely). Of course, the more vertical the thermal input, the greater the effect on the instruments. Drivers in this zone include VIMS IR and CIRS. Performance, not safety, is the primary concern. Overheating renders instrument data first degraded, then useless. Overheating for the VIMS IR instrument can be rapid ( tens of minutes with direct sunlight) and cooling very slow ( many hours). There is no absolute temperature threshold; "overheating" depends on the experiment in process. This problem is complicated by the fact that the vast majority of Titan flybys approach on the sunlit side and recede on the dark side of Titan. This is due to inbound and outbound flybys having been placed at consistent locations in Titans orbit. Unfortunately, the ram direction of INMS and other fields, particles & waves instruments is aligned directly opposite the radiators of the cryogenic instruments. Therefore, in order to point the INMS and other fields of view in the ram direction, the cryogenic instrument radiators must face the sun for many encounters. This problem can be avoided with one of two strategies: pointing the INMS in the anti-ram (instead of ram) direction, or turn the INMS to the ram direction only near closest approach, minimizing the amount of time the radiators are exposed to the sun. Unfortunately, the first strategy degrades data collection for some of the FPW instruments, and the second may use valuable reaction wheel or thruster resources that are needed for TMC or atmospheric compensation. Radiator exposure is still a concern even when the cryogenic instruments are not operating. Since the time constant for cooling is so slow, post-flyby science (even up to a day after exposure) can still be affected. This means that instrument teams that arent concerned with overheating will still have to constrain themselves in pointing design if cryogenic instrument teams are planning subsequent observations. 5.6.3 DEBRIS During its travels from the inner solar system to the Saturnian environment, Cassini flies through a large region of space which is known to contain debris at a variety of sizes and abundances. Care must be taken to determine the vulnerabilities of the spacecraft to debris impacts, and the likelihood of such impacts causing the loss of mission or a degradation in performance. For a complete description of Cassinis vulnerabilities to dust, and the protective strategies that have been adopted during the tour, refer to the Cassini Dust Protection Plan. 5.7 PERIODIC ACTIVITIES This section describes activities that are repeated often throughout the mission and are not specific to one particular subphase (as described in sections 6 and 7).
5-26
113 of 217
5.7.1
ENGINEERING MAINTENANCE
There are three activities to be completed in the Periodic Engineering Maintenance (PEM) sequence, which is executed approximately once every three months. The three activities are: Maintaining the BAIL EEPROM in AACS to protect the data from unrecoverable radiation damage. This activity lasts no more than 6 hours. Exercising the engine gimbal actuators (both prime and backup) through 25% of full stroke. This activity lasts one hour. Exercising all of the reaction wheels (including the backup) by rotating each at least 1/4 of a turn to spread the lubricant. This activity lasts for less than one hour. Note that this activity imparts a delta-V to the spacecraft and therefore should not be scheduled near a TCM (-3 weeks to +2 weeks).
In addition to the standard PEM activities, there are a number of other required engineering activities. SRU calibration must occur once every year. Maneuver related AACS parameter updates and AACS constraint monitor updates are also common. Also AACS cruise mode checkouts, RWA friction tests, NAC-to-SRU alignment, and HGA(X-band)-to-SRU alignment are expected. With the exception of the RWA friction test, all of these activities are planned to occur only once. The RWA friction test will occur as needed. Finally, SSR characterization is performed through analysis of the SSR single bit and double bit error information obtained from the internal SSR memory scrub function.. 5.7.2 HUYGENS PROBE CHECKOUTS Probe Checkouts are sequences which exercise the Probe systems to maintain their health during the long cruise period. Each Probe Checkout is up to a 4 hour test of the Probe mission sequence which records up to 303 Mbits of data (including engineering) to the SSR. The purpose of the cruise checkouts is to verify the capabilities of the Probe system to perform its mission at Titan. Therefore, the checkouts have been designed to simulate as closely as possible the sequence of activities to be performed during the Probe descent to Titan. Some experiment switch-on and pyro events excepted, the PCDU (Power Control Distribution Unit) and CDMS (Command & Data Management Subsystem) sequences are performed as during the normal mission, with simulation by telecommands of the changing DDB (Descent Data Broadcast) which will be transmitted to experiments. During checkout, the Probe/PSE link is conducted with a low power RF signal which essentially tests the whole transmitter except for the high power amplifiers. Due to the power allocation limits agreed to between JPL and ESA, not all of the Huygens instrumentation can be operated as it is in the mission descent sequence; therefore, checkout sequences have been developed to allow payload checkout in different groups, and such sequences have been used throughout ground testing activities. ESA will conduct Probe Checkout sequence reviews before each checkout to determine if the specific activities during any one Checkout need to be changed somewhat. Figure 5.12 illustrates a typical Probe Checkout. Checkouts must take into account the main constraints agreed to by JPL and ESA, namely: Power consumption never to exceed 262 Watts. 1 CDS telecommand per second per data chain. PSA and transmitters in mission mode at switch-on, i.e. the default frequency includes Doppler shift and the Ultra Stable Oscillators (RUSO/TUSO) are selected. Orbiter can be in any RTE mode, but Probe data must be recorded.
5-27
114 of 217
General USOs Xmit Instruments*
Power control / command & data management

PSA's (A+B) on A only
RUSO TUSO
A&B
A only
Probe
GCMS HASI ACP DISR SSP
Minutes from simulated probe entry
-30
30
60
90
120
150
* ACP = Aerosol Collector Pyrolyser, DISR = Descent Imager / Spectral Radiometer, GCMS = Gas Chromatograph / Mass Spectrometer, HASI = Huygens Atmosphere Structure Instrument, SSP = Surface Science Package Data modes are described in section 3.2.4: Orbital Telemetry Modes. The PCHK mode routes data to both the Reed-Solomon Encoder for high speed downlink (if the transmitter is on) and the Solid State Recorder for later transmission via LGAs at low rates; therefore, the PCHK mode can be used for all checkouts, regardless of the downlink strategy.
Figure 5.12 Sample Probe Checkout Timeline
FOIA 10-JPL-F-00451
115 of 217
LGA2 (which is mounted immediately below the probe) cannot be operating during a Probe Checkout (FR80C5). Several additional constraints exist that must be satisfied during each checkout are: For real-time playback, the link must support the Probe Checkout data rate of 24.885 kbps. If this is not possible, the link margin must support a data rate of at least 40 bps for SSR playback of Probe Checkout data (the lowest mode, 20 bps, is exclusively real-time engineering data with no SSR playback). DSN coverage sufficient to return Probe data must be in the Detailed Mission Request, which documents the antennas requested of the DSN by Cassini, and the MGSO User Loading Profile. Telemetry must not interfere with the navigation ranging required. During those periods where either ranging or telemetry is possible (but not both), a compromise must be reached that allows Probe Checkout data to be returned while still meeting navigation requirements. If Probe telemetry must be played back from the SSR, playback must be completed before being overwritten by later data (2.0 Gbit data capacity at the beginning of the mission - 303 Mbit of probe and engineering data leaves 1.7 Gbit of volume to record engineering at 1650 bps = 11.9 days worth of space). Any nonstandard activities which record additional data on the SSR would shorten this time period. DSN coverage following each Probe Checkout can be used to observe that the probe equipment temperature is falling back to its normal levels (i.e. that everything has been turned off properly). For real-time Probe Checkouts (i.e. those with DSN coverage supporting 24.8 kbps or higher rates), the Probe Checkouts have been placed at the beginning of a pass, leaving at least five hours after the Probe Checkout to study the probe temperature profile. For nonreal-time Probe Checkouts (checkouts 2 and 3), the Checkouts have been placed to end near the beginning of a DSN pass, so that ESA staff may observe the battery temperature over an entire pass (8 hours). If SSR playback is possible on this pass, the probe data return is initiated as well. In either case -- real-time or delayed data return -- it is expected that Probe battery temperature readings can be inserted into the Real-Time Engineering (RTE) portion of the telemetry at a granularity acceptable to ESA staff without overly limiting the standard engineering data. In all, there are five checkouts in the inner cruise period, and 11 more during outer cruise and after SOI (see table 5.9). No. 1 2 3 4 5 6 7 8 9 10 Table 5.9 Probe Checkout Dates Date Days w.r.t. Target Event 23 October, 1997 27 March, 1998 Launch + 8d near Launch + 6 months just before ICO Months since last Checkout N/A 5 9 9 5 6 8 6 6 6
FOIA 10-JPL-F-00451
22 December, 1998 15 September 1999 after Earth (at opposition) 2 February 2000 1-2 days after HGA on ~6 months later 28 July 2000 ~8 months later 22 March 2001 6 months later 24 July 2001 2 September 2001 6 months later 6 months later 16 April 2002 5-29
116 of 217
11 12 13 14 15 16 17 5.7.3
16 September 2002 21 April 2003 15 September 2003 15 March 2004 14 July 2004 14 September 2004 22 November 2004
6 months later 6 months later 6 months later 6 months later SOI + 14 days Periapsis Raise Probe Release 1 mon
6 6 6 6 4 2 2
PERIODIC INSTRUMENT MAINTENANCE
PIMs for pre-Jupiter cruise were done on IM40 telemetry mode and are described in previous mission plans (Rev. L and earlier). In post-Jupiter cruise, the instruments have the opportunity to perform limited maintenance sequences. These limited sequences are contained within the Periodic Instrument Maintenance (PIM) activity for the first few months after Jupiter. The main part of the sequence lasts approximately three and one quarter hours and is completed just prior to DSN coverage. The entire sequence lasts 19 hours and 15 minutes. Data is recorded on the SSR using the RTE 1896 telemetry mode. This mode allows the housekeeping data from all instruments in the PIM to be recorded to the SSR. It does not support the collection of science data. So for the duration of the PIM no science data is recorded. Maintenance activities for RADAR, ISS, VIMS, and CIRS are completed during the first 3 hours and 15 minutes of the PIM. ISS has a decontamination activity that extends for 16 hours after this time. Total time for the PIM is therefore 19 hours and 15 minutes. Starting in fall of 2001, however, each instrument performs instrument maintenance independently.
5-30
117 of 217
SECTION 6: LAUNCH AND CRUISE ACTIVITIES 6.1 LAUNCH PHASE The Launch Phase spans the time period between Launch (L) and L+30 days. During this time interval, the spacecraft goes through a relatively rapid series of transitions which take it from the launch pad on Earth to a Venus-targeted trajectory, which will eventually take it to Saturn. Because of the launch environment and the operation of the spacecraft for the first time, the events in the Launch Phase are geared primarily towards characterizing the spacecrafts behavior in the space environment, performing essential engineering checkouts and calibrations, and preparing the spacecraft for its first main engine maneuver, which occurs at L+25 days. The first thirty days of the mission were divided into two Subphases: the Launch Sequence Subphase and the TCM 1 Subphase. The Launch Sequence Subphase was autonomous, lasting two days, and covered the interaction between the spacecraft and launch vehicle through separation, the powering-on of select heaters, and the acquisition of the spacecraft by the DSN. The TCM 1 Subphase began at L+2 days and addressed the events that lead up to and surrounded the first Trajectory Correction Maneuver (TCM). Included among these events were those pertaining to spacecraft system health checks and a limited number of maintenance activities. 6.1.1 LAUNCH SEQUENCE SUBPHASE Cassini had a 30-day nominal launch window, extending between October 6 to November 4, 1997 that provided for an arrival date at Saturn of July 1, 2004. After November 4, the nominal arrival date was not achievable, but Cassini could still have launched into the primary trajectory until November 13 with an arrival date as late as June 25, 2005. After a first attempt was postponed on October 13, Cassini successfully lifted-off from the Cape Canaveral Air Station complex 40 on October 15, 1997 at 08:55 UTC. The solid rocket motors burned from liftoff to separation at 2 min 23 sec at an altitude of 224,000 feet. Stage 1 ignition began at 2 min 11 sec at an altitude of 192,000 feet, and Stage 2 ignition (and Stage 1 separation) occurred at 5 min 23 sec after liftoff at 549,000 feet. During the first three minutes and 27 seconds of flight, the payload fairing shrouded the spacecraft protecting it from direct solar illumination. The Centaur upper stage separated from the launch vehicle at 9 min 13 sec at 678,000 feet. The first Centaur burn began at 9 min 13 sec and lasted approximately two minutes. This burn placed the Cassini spacecraft into an elliptical, 170 km by 445km parking orbit with an inclination of about 30 degrees. This orbit was designed to provide an orbital lifetime of about 20 days in case the Centaur failed to have a successful second burn and injection. After 17 minutes in parking orbit, the Centaur fired again and launched Cassini toward Venus en route to Saturn. The injection C3 was 16.6 km2 /s2 . The first critical subsequence executed on board the spacecraft (TEMP) was initiated and completed during parking orbit coast and actually starts the onboard launch sequence in addition to turning on spacecraft heaters. The second critical subsequence (PREP), 30 seconds after the second Centaur burn, prepared the spacecraft for separation from the Centaur. PREP opened the prime thruster branch latch valve, turned on the pyro switching units, and turned on the spacecrafts X-band exciter and amplifiers for the low gain antenna for acquisition by the DSNs Canberra station. The third critical subsequence (SEP) was initiated following the worst-case completion time of PREP (6 minutes after the second Centaur burn). At this point the spacecraft was separated from the Centaur.
6-1
118 of 217
Launch Sequence Subphase
TEMP Start SRMU Separation Payload fairing Separation Stage 2 Separation Centaur Separation
MECO 1 MES 1 MES 2
PREP Prepare for SEP
SEP**
Warm up catbed heaters for thruster use
Titan IV
Launch
Centaur
Separation
MECO 2
MES = main engine start MECO = main engine cut-off C-CAM = collision & contamination avoidance maneuver
Orient S/C toward Sun

Discrete Signal start PREP Discrete Signal start SEP
C-CAM
Discrete Signal start TEMP
MAG replacement heaters on (auto. thermal control) Parking Orbit Short Coast
De-tumble Response to tip-off rates Get HGA Back to Sun AACS attitude reference Open prime thruster branch latch valve TWTAs warm-up Power on PSUs
Spacecraft
Events
Catbed heaters warming up Min. RTG Power Power on ISS NAC replacement heater
Orientation
Probe Sun-pointed (HGA Sun-pointed if coast > 23 min)
HGA orients/ points to Sun
HGA is Sun-pointed LGA2 until MECO2 + 40 minutes Real Time Engineering (Through S/C LGA) - 948bps
Data DSN Coverage Minutes Past

0
Real Time Engineering (Through Centaur) - 948bps TDRSS coverage of Centaur
early rise early rise latest
latest Canberra (Oct.9 launch) Canberra (Nov. 6 launch)
10
20
30
40
50
60
70
* Data modes are described in section 3.2.4: Orbital Telemetry Modes **Separation is shown at a representative time; actual time is under study.
Figure 6.1 Cassini Ascent Sequence Timeline

SEG 28 Oct 96
FOIA 10-JPL-F-00451
119 of 217
FOIA 10-JPL-F-00451
120 of 217
Immediately after separation, the spacecrafts AACS took control and pointed the HGA toward the Sun to achieve a thermally safe attitude. X-band uplink and downlink was established, the RPWS Langmuir Probe was deployed via pyro, instrument replacement heaters and main engine oxidizer valve heaters were turned on, and the SRU, ISS, and VIMS decontaminations were started. The Centaur, after separation from the spacecraft, executed a Collision and Contamination Avoidance Maneuver (C/CAM) which prevented it from impacting either Venus or the spacecraft. This burn occurred approximately 20 minutes after separation to allow the spacecraft and the Centaur to drift apart such that the plume from the Centaur RCS firing would not impact the spacecraft. Approximately eight minutes after C/CAM, the Centaur executed a blowdown maneuver to expel unused propellant and to further reduce the probability of impact with the spacecraft or Venus. About an hour after separation, the Centaur depleted its hydrazine from the RCS. The Centaur mission ended approximately 87 minutes after separation. Figure 6.1 illustrates the main events that executed during the launch sequence. Figure 6.2 shows the groundtrack from launch until one day after separation from the Centaur. 6.1.2 TCM 1 SUBPHASE The TCM 1 Subphase began on day 291 (18 October) and was comprised of four one-week sequences. During the beginning of the TCM1 subphase, the spacecraft was in a relatively quiescent state. Telemetry downlinked by the spacecraft was utilized to make an initial characterization of the spacecraft and to assess whether its various subsystems survived the launch environment. Deployment, decontamination, tank heating, and AACS checkout activities were started. Figure 6.3 summarizes the events during the TCM 1 Subphase. During most of the TCM 1 Subphase, the spacecraft remained Sun-pointed (i.e., with its HGA aimed at the Sun) and in a relatively quiescent state. The only event requiring the spacecraft to go off Sun-point was TCM 1. PMS Activities: Before the first TCM only, the fuel and oxidizer tanks were heated in order to avoid an irreversible overpressure in the propellant lines. If the tanks fully pressurize before the spacecraft passes through the peak temperature regime, then when the spacecraft does enter the maximum thermal environment, the tank pressure would climb without a way to bring it back down, possibly causing an overpressure. Each tank has one heater and one redundant backup heater. The oxidizer tank heater was turned on at approximately L+8 hours. Since the fuel tank requires less heating time, the fuel tank heater was turned on a few days later. The tank heating was interrupted for probe checkout and periodic instrument maintenance due to power constraints. Both heaters were turned off approximately 2 days before TCM 1. Venting, priming and pressurizing the bipropellant lines (REA-A only) occurred between one and two days before TCM 1. Venting removes the gas between the latch valves and the engines, creating a vacuum in the propellant lines. The main engine cover was opened prior to venting. Priming fills these lines with propellant. The tanks were then pressurized at a temperature higher than the peak temperature expected en route to Venus. Each step takes only seconds to complete. However, a real-time Go command was needed before moving on to the next, to ensure that the previous step was successful. After pressurizing, the valves were left open until approximately 2 days after TCM1. AACS Activities: There was a window to update AACS parameters in real-time at L+2 days. An IRU Characterization, EGA Exercise, and Accelerometer Calibration were scheduled during the TCM1 Subphase in order to ensure functionality before TCM1. TCM1 and Thermal Characterization: TCM 1 was an Earth injection clean-up maneuver placed at L+ 25 days. TCM 1 was executed with the main engine with a V magnitude of 2.8 6-4
121 of 217
m/s. The burn sequence included holding the spacecraft off-Sun after burn completion to allow the spacecraft heating to be characterized in a relatively benign environment. The Main Engine cover was opened 48 hours before the start of the burn, and closed during the TCM1 mini-sequence several hours after burn completion. Because of the high data rate capability at the beginning of the trajectory, it took less than one DSN pass to downlink the data from TCM 1 using the PB&RTE-948 data mode. Regulator Leak Problem: As the initial pressurization was being performed just prior to TCM1, an unexpectedly high leak rate, 1700 sccm (standard cubic centimeters per minute), was noticed from the primary regulator (PR1). The specified rate for leakage from this regulator was supposed to be 0.6 sccm. High pressure latch valve LV10 was closed in response. The incident was addressed in ISA Z44505. While regulator leakage is a well known phenomenon, the magnitude of this leak was surprising, especially given the leakage characteristics demonstrated by PR1 during ground testing. Analysis demonstrated that particulate contamination could very easily explain the observed regulator leakage, since the requisite particle size that causes a 1700 sccm leak is two orders of magnitude smaller than the filter capacity between pyro valve PV1 and PR1. That is, a particle that just fits and passes through the filter upstream of PR1 could actually cause a leak a hundred times larger than the leak observed at initial pressurization. Recommendation has been made to the project to continue to use PR1 unless the leakage reaches 20000sccm. The PR1 regulation function is considered excellent despite high leakage during DSM and TCM13, and procedures have been identified, specifically for the coordinated use of LV10, that can be employed at the next regulated maneuvers, Phoebe and SOI. Solid State Recorder: There were SSR pointer resets scheduled for L+18 and L+25 days. The primary SSR was switched from SSR A to SSR B at L+18 days, just before the scheduled pointer reset. At L+29 days, the redundant SSR was turned off. ISS & VIMS decontaminations: The spacecraft powered on decontamination heaters for these instruments in order to boil off any contaminants deposited on their optics or radiators as a result of the launch environment. VIMS and ISS (Level 1) decontaminations began during the Launch Sequence Subphase. ISS Decontamination was increased to Level 2 at the beginning of C1 (L+3 days). VIMS high power decontamination lasted 150 days. ISS Decontamination was reduced to Level 1 and the VIMS IR Optics Heaters were paused for Periodic Instrument Maintenance, Probe Checkout, and TCM1. The VIMS Visible Optics Heater were also paused for the Periodic Instrument Maintenance. Level 2 ISS decontamination concluded after the end of the TCM1 Subphase, when the decontamination had reached a cumulative 30 days. Many instrument cover deployments, antenna deployments, and latch releases were also done during the first 30 days after launch. These included MIMI Launch Latch Release, CAPS Launch Latch Release, CIRS Launch Latch Release, CDA Cover Jettison, MIMI Cover Releases, and UVIS Membrane Puncture. There was also a Periodic Instrument Maintenance scheduled for L+12 days. However, the Ka-TWTA Helix Current Maintenance could not occur before L + 4 months and was excluded from this first maintenance activity. The Huygens Probe had also requested that there be an early checkout shortly after launch in order to take advantage of the high downlink data rates. The first Probe Checkout was scheduled for L+8 days. This was the earliest time allowable considering post-launch cooldown inside the probe, while also allowing room for subsequent contingency actions that may have been necessary while the 24.885 kbps downlink rate is available (until approximately L+12 days). This checkout provided post-launch verification for all subsystems and experiments, and was of particular importance for the Gas Chromatograph and Mass Spectrometer (GCMS) by pumping out any launch-induced release of internal contaminants.
6-5
122 of 217
6.2
INNER CRUISE PHASE
The Inner Cruise Phase consisted of three subphases: Venus 1, Instrument Checkout, and Venus 2-Earth. Activities accomplished in each subphase are described in following subsections. The Inner Cruise Phase spanned the time period from 14 November 1997 through 7 November 1999. During most of this phase, the spacecrafts proximity to the Sun constrained the spacecraft to remain Sun-pointed, and therefore telecommunications used the low data rate Low Gain Antennas. The downlink capability of the LGAs at large spacecraft-Earth ranges was very limited. Figure 6.4 shows the timeline of events for the Inner Cruise Phase. Between L + 30 days and L + 150 days the downlink data rate varied between 20 and 948 bps. During this four-month period the spacecraft performed routine maintenance activities and engineering calibrations. These activities enabled the Mission and Science Operations office to progressively improve their understanding of the spacecrafts health and capabilities. "Routine" maintenance was limited to engineering subsystems and instrument maintenance. For some days during Inner Cruise, the downlink data rate capability dropped below 40 bps for a short period of time, even with ranging turned off. Due to the low downlink data rates, spacecraft activities generating large amounts of data were avoided during these periods. Beginning on 28 December, 1998, the spacecraft approached opposition and pointed the HGA towards Earth for a period of 25 days and kept the Probe equipment temperature within the required range. This provided a high data rate window in which checkout activities were accomplished. Off-Sun pointing greater than 2.5 degrees was permitted for this 25-day period. The DSN coverage shown in Figure 6.4 reflects the DSN tracking during the Inner Cruise period. A detailed description of the Projects request to the DSN can be found in the Program Service Level Agreement (PSLA). The number of passes requested per week was satisfies navigation radiometric data requirements provides telemetry visibility during periods of spacecraft activities requiring ground intervention such as maneuvers or planetary flybys. During the Inner Cruise Phase, Cassini utilized 34 meter DSN coverage. (The 70m DSN stations were not available to uplink X-band until the year 2000. X-band uplink is required for 2-way navigation tracking data). The transitions from LGA 1 to LGA 2 are based on which antenna has the highest gain for a particular geometry. These transitions occurred at Sun-Spacecraft-Earth (SPE) angles of approximately 44; when this angle was less than 44, LGA 1 had the higher gain, and when the angle was at least 44, LGA 2 provided the higher downlink capability. During most of the Inner Cruise Phase, the spacecraft remained Sun-pointed and downlinked telemetry via LGAs. The engineering activities onboard the spacecraft were geared towards maintenance and calibration of the various engineering subsystems and provided support for the TCMs and the DSM that were done during the phase.
6-6
123 of 217
Days Past Launch

Launch Sequence Subphase
0 1
3 4 5 6 C1
8 9
10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 C2 C3 C4
Aphelion 1.01AU
PMS Venting & Priming (R/T Go)
Milestones/ Maneuvers Engineering
AACS/CDS configuration for Cruise Main Engine Cover Close (R/T)
USO Turn-on, TLM coding, CDS FSW , SFP config.) IVP Update Window EGA Exercise, SRU Attitude Initialization IRUCharacterization, USO Accelerometer Calibration Enable SRU Decontamination Probe C/O Backup Window Oxidizer tank warm-up Fuel tank warm-up Oxidizer tank warm-up Fuel tank warm-up
S/C Configuration Activities (Incl. AACS Mode Block,
TCM -1
(Incl. Thermal Char. & ME Cover Close)

Pressurizing Biprop Isolation (R/T Go) (R/T Go)
Main Engine Cover Open**
Change Probe PCDU Temperature Limit back to 50 deg C (R/T cmd) CDA Cover Jettison
Science
CIRS Launch Latch Release Langmuir Probe Deployment
Probe C/O
Periodic Instrument Maintenance

RPWS Antenna Deployment ISS Decon Level 1 (First 8 hours of PIM) ISS Decon Level 2 (30 Days Cumulative Duration) VIMS Decon (High-Level for 150 Days Cumulative Duration) CDA Articulation and Launch Latch Release Cover Releases: MIMI INCA & CHEMS UVIS Membrane Puncture
Launch Latch Releases: MIMI & CAPS ISS Decon Level 1 and VIMS Decon (39 W) ISS Decon Level 2 ISS Decon Level 2
ISS Decon Level 1
ISS Decon Level 2
VIMS Decon (High Level)
Antenna Downlink Data Rate Data SSR DSN Coverage +

25k 14k 948 40 0
LGA 1
VIMS Decon Reduced for RADAR and VIMS Maint.
LGA 2
ISS Decon Off and VIMS Decon Reduced
PCHK-24.885k (1 Pass) RTE-948

C1 Seq
IM-40 (1 Pass)
PB&RTE-948 (1 pass for VPP P/B, 2 Passes for TCM P/B and 1 for MIMI/UVIS) RTE-948 RTE-948
Turn off SSR-A (R/T) C5 Seq
RTE&SPB-14.22k
C2 Seq
RTE&SPB-14.22k
PIM MiniSeq C3 Seq
Switch to SSR-B as Primary (R/T)
SSR Pointer Resets

C4 Seq
background sequence uplinks (Continuous Required, Waivers needed for any exceptions)
Quiet periods (for anomaly if needed)
* Data modes are described in section 4: Orbital Telemetry Modes. ** Main engine cover remains open for maneuvers only long enough to avoid violation of thermal and operational constraints. Ka-TWTA and CDA not included; implemented as mini-sequence to allow for anomalies or delays in deployment of CIRS and CAPS.
Figure 6.3 Cassini TCM1 Subphase Timeline

7 Oct 97
FOIA 10-JPL-F-00451
124 of 217
Date Trajectory Data Maneuvers Science Engineering

Periodic Engineering Maintenance (24 hours every 3 months)
1997
O N D J
Cassini1998 Early F Cruise Phase M A M J J A

C P Venus I
1999
S O N D J
A Aphelion Opposition 1.578AU
Test Maneuver DSM 5 TCM 6 TCM 7
2000
F M
F M A M J
Venus II
J A S O N D J
Earth Opposition Conjunction
Inferior Perihelion Conjunction 0.68 AU

TCM 2 TCM 3 TCM 4
TCM 8 TCM 10 TCM 12 TCM 13 TCM 9 TCM 11
Asteroid Belt
Venus-1 Science
Venus-2 Science
CDA Sci
Earth Science, Instr. Cals & Characterizations, Opposition science
SRU decontamination
Instrument
Periodic Instrument Maintenance (24 hours every 3 months)
* *
VIMS decontamination (5 months) MIMI decontamination (4 weeks)
* UVIS-Only Maintenance
Limited Data Return Probe Checkout
Probe Checkout
VIMS Cover Deploy/Jettison 25-Day Instr. Checkout LGA 1
MAG Boom Deployment Probe CIRS Cooler Checkout Cover Jettison LGA 1 HGA
Antenna Data Rate Capability

(Downlink in bps)
70M ant. 34M ant.
24885 14220
948 200 40 20
LGA 2
LGA 1
LGA 2
HGA
248.85k
Ranging mod index = 35 deg

20
DSN Coverage
(passes / wk)
MOSO User Loading Profile
15 10 5 0
Days Past Launch
60
120
180
240
300
360
420
480
540
600
660
720
780
840
900
Figure 6.4 Cassini Inner Cruise Phase
FOIA 10-JPL-F-00451
125 of 217
Probe checkouts (PCOs) are required about every 6 months to exercise the Probe internal systems to maintain their health. PCOs are usually accomplished with a 70 m for downlink to use their high-rate Probe Checkout telemetry mode, or when circumstances permit, the HGA. Probe Checkout #1 was done on 23 October 1997 when the spacecraft was still relatively close to Earth and was able to support the high data rate downlink on a 34 m antenna. Probe checkout 2 had no conveniently close high data rate period to allow for real-time downlink. ESA agreed to a compromise required downlink of about 40% of the data from this checkout. Fortunately, there was a period before the Venus 1 flyby where 70 meter coverage permitted the orbiter to transmit data using PB&RTE-948 data mode for periods at high elevation. PCO#2 was carried on 27 March 1998. PCO#3 was able to utilize the January 1999 opposition period to support the high downlink. This was enabled by the spacecraft being able to be earth pointed near opposition, so it could use the HGA. PCO#3 was carried out on 22 December 1998. However, since the spacecraft was Earth-pointed, and the Probe was receiving some thermal input from solar exposure, the Checkout occurred 6 days prior to the start of Earth-point to allow time for probe equipment to cool down after their Checkout. Therefore, Probe Checkout did not return the checkout data in real time. High data rates during the ICO period allowed rapid playback of the Probe data, so the full data set was returned during the first day of the ICO period. Probe checkout 4 was placed just after the Earth flyby, nine months after PCO#3, when the HGA was available for a limited period near opposition. This checkout occurred on 15 September 1999, after the flyby due to the extensive activities before and during the flyby related to the MAG boom deployment and calibration (see the Earth flyby description later in this section). 6.2.1 VENUS 1 FLYBY SUBPHASE The Venus 1 subphase started on 14 November 1997 and continued through 13 September 1998. The subphase encompassed sequences C5 through C9. The period included two executed TCMs (one other TCM was cancelled), one planetary swingbys, and three switches between LGA2 and LGA1. Most of the period was dedicated to engineering and instrument maintenance activities. The first Venus encounter occurred on 26 April 1998 (see Figure 6.5). The spacecraft approached Venus from a sunward direction, and closest approach occurred just after entering the Suns shadow for a period of about 15 minutes. At closest approach, the altitude was 284 km, with a velocity relative to Venus of 11.8 km/s. The spacecraft was occulted from the Earth for about 2 hours. The Earth occultation zone started about 15 minutes after the spacecraft left the Sun occultation zone. Flyby accuracy for the Venus flyby was maintained using two TCMs, 60 and 20 days before closest approach, and a clean-up maneuver 20 days after the flyby. DSN requirements for the Venus 1 flyby consisted of 1 pass per day on approach, beginning at Venus 1 - 90 days, followed by continuous coverage during the 5 days around the flyby. Coverage was reduced to 1 pass per day for the 5 days following the flyby. 6.2.2 INSTRUMENT CHECKOUT SUBPHASE The Instrument Checkout Subphase started on 14 September 1998 and continued through 14 March 1999. The subphase consisted of sequences C10-C13. This subphase is characterized by the opposition that occurred on 9 January 1999, and which allowed use of the HGA for downlink since the Earth and Sun are nearly aligned as seen from Cassini. So Earth pointing still allows shading from the Sun with the HGA. Beginning on 28 December, 1998, the spacecraft approached opposition and pointed the HGA towards Earth for a period of 25 days and kept the Probe equipment temperature within the
6-9
126 of 217
required range. This provided a high data rate window in which checkout activities were accomplished. Off-Sun pointing greater than 2.5 degrees was permitted for this 25-day period. All instruments scheduled checkout activities within a 25 day period centered on opposition. This was the first opportunity since launch to exercise most of the instruments and check status other than routine instrument maintenance. One test conducted was repeating the ATLO "Quiet Test". This test allowed the instruments to monitor other instruments as they turned on and off. This provided valuable insight into how to integrate science observations during the Saturn tour.
Figure 6.5 Venus 1 Flyby During the instrument checkout activities, the spacecraft autonomously went into a safe state due to a slow z-axis turn to keep the Sun in the -x-axis direction during opposition which caused star position errors. These errors caused AACS fault protection to call S/C Safing. Most of the instrument checkout activities were able to be rescheduled after a 10 day safing period. Those that were not completed were rescheduled for the ICO-2 subphase. 6.2.3 VENUS 2 - EARTH SUBPHASE The Venus 2 - Earth subphase started on 15 March 1999, or 45 days prior to the second Venus flyby, and continued through 7 November 1999, or Earth + 82 days. The subphase encompasses sequences C13 through C16. The period included seven scheduled TCMs, two planetary swingbys, and 25 science activities in addition to normal engineering activities. Figure 6.7 shows the Venus2-Earth timeline. At the beginning of the Venus 2 - Earth Subphase, the spacecraft was Sun-pointed and communicating through LGA2. The DSN coverage was 1 pass per day on approach to the Venus 2 flyby. TCM-7 was executed at Venus 2 - 37 days and TCM-8 at Venus - 14 days. The DSN coverage increased to 3 passes per day in support of the flyby. After perihelion, the spacecraft then executed the first Earth targeting maneuver (TCM-9) at Venus 2 + 12 days, and then three more pre-Earth maneuvers to ensure a successful Earth flyby. A post-Earth cleanup maneuver was executed at Earth + 13 days. After the Earth flyby, the DSN coverage demands decreased until the spacecraft was switched to the HGA in February, 2000. Opposition 6-10
127 of 217
occurred at E+26 days and this presented an opportunity to use the HGA for a four-day period when the spacecraft could be pointed to Earth and stay within 2.5 degrees of the Sun. Five instruments planned observations as Cassini passed through the Earth magnetotail. During this subphase, about two dozen activities involving maintenance, calibration, checkout, and science observations were carried out, using all of the Cassini instruments except INMS and CIRS. These activities are summarized in Table 6.1. The first flyby of this Subphase was the second flyby of Venus (see Figure 6.6). This flyby was an energy-increasing (with respect to the Sun) gravity assist which changes the trajectory to meet Earth only about 55 days later. This encounter, along with the Earth flyby, provide the spacecraft with the heliocentric energy to reach Jupiter in late 2000. A timeline for Venus 2 science activities is shown in 6.11. Closest approach occurred by the time the spacecraft left the Earth occultation zone. This occultation lasted approximately 15 min. At closest approach, the altitude was 603 km, with a Venus-relative velocity of 13.6 km/s. Targeting maneuvers took place 140, 37, and 14 days before closest approach, and a clean-up maneuver 12 days after the flyby. DSN requirements for the Venus 2 flyby consisted of one pass every two days beginning at Venus 2 - 90 days, plus one pass per day from Venus 2 - 50 days to Venus 2 - 3 days. Continuous coverage for the Venus 2 flyby was required between Venus 2 - 2 days and Venus 2 + 2 days.
Figure 6.6 Venus 2 Flyby
6-11
128 of 217
Figure 6.7 Cassini Venus 2Earth Subphase Timeline: C13 Through C16 Sequences
1999
Mar Apr
13 14 15 16 17 18
May
19 20 21 22 23
Jun
24 25 26 27
Jul
28 29 30 31
Aug
32 33 34 35 36
Sep
37 38 39 40
Oct
41 42 43
Nov
44
DSN Week of Year Sequence (with begin date)
11
12
15 Mar 99
C13
10 May 99
C14
Venus 2
12 Jul 99
C15
Inferior Conjunction
+ + TCM 11 TCM 12 (E-15d) (E-6.5d)
6 Sep 99
C16
Milestones TCMs (7-8 RCS, 9-13 ME, 12 contingency) Operational Mode (Cruise 2) and Fixed/Unique Sequences Engineering** Instruments and Probe
CAPS CDA ISS MAG MIMI RADAR RPWS RSS UVIS VIMS
PIM AACS Default IVP CMU* Vector Update CHM* CHM* CHM* PIM CDA-On + TCM 7 (V2-37d) RCS TCM CMU* +
Perihelion (0.72 AU)

+ + TCM 9 TCM 10 (V2+12d) (E-30d) CHM*
PIM
Earth
+ TCM 13 (E+13d)
Opposition
= Earth Swingby Critical Period

(E-45 days to E-4 hours)
PCO
TCM 8 (V2-14d) RCS TCM

PEM
PEM CHM* CHM*
ME TCM AACS Default IVP CMU* Vector Update CHM* CHM*
CHM* ME
PEM CMU* PEM CHM* CHM*
PIM
TCM
CHM*
CHM* CHM* CHM*
CHM* CHM*
CDA Dust Measurements
PIM CDA Dust Measurements Articulation Data record and/or downlink
CAPS,UVIS,MIMI , RPWS,CDA,MAG
PIM CDA Dust Measurements PCO
Post-Earth Science Observations
ISS Level 2 (last 16 hours of PIM)

ISS Decon Level 1 (or Level 2 as part of PIMs, and Off during TCMs)
Instruments in sleep mode during TCM13 and off before PCO. CDA & MAG on after PCO. MAG off on E+32d.
248 k 142 k 25 k 14 k (Laura Sakamotos 12/9/97 Mission Calendar) 948 200 158 40 20 0 (TBD, may track telemetry capability) 27 25 20 (proposed passes per week) 15 (Recommended DSN passes to satisfy the latest 10 requirements from ECR 82207) 5 Memory Load 0 Partition Repairs Resets Pointer
Antenna Telemetry Capability (bps)
LGA 2
LGA 1
HGA
LGA 1
Data Mode DSN Coverage SSR Management

(preliminary)
Day of Year
(Days past 15 Oct 97 = L + )
074 081 088 095 102 109 116 123 130 137 144 151 158 165
516 523 530 537 544 551 558 565 572 579 586 593 600 607
172 179 186 193

614 621 628 635
200 207 214 221 228 235 242 249 256 263 270 277 284 291 298 305 312
642 649 656 663 670 677 684 691 698 705 712 719 726 733 740 747 754
based on 00:00:00 UTC
* CMU : AACS Constraint Monitor Update. CHM : Clear Highwater Mark. + : Pre TCM parameter U/D ** Not shown are uplink Thursday before sequence start, detail activities around V2/Earth flyby, and VIMS decon. To obtain detail activities have been scheduled, please see individual sequence timeline.
WGS 15 December 98 (Rev.)
FOIA 10-JPL-F-00451
129 of 217
Table 6.1 Venus 2 - Earth Spacecraft Activities

Activity Instr. Description Observation Timing (duration usu. less than instrument-on time)
2 hrs near C/A 10 minutes near C/A 4 hrs centered on C/A 4 hrs centered on C/A at least 2 hrs, beginning 1hr+15 min. before C/A 30 min. near Venus 2 23 min., starting 20 min. prior to boresight viewing the Venus terminator continuously after Venus 2 to ESB >= 13 hrs between 3-10 Earth radii after Sun range > 0.97 AU (about 5 days before ESB) and before ESB from MAG activation for boom deployment until 14.22kps downlink no longer possible 10 hrs centered on C/A ~30 min of data acquisition, centered around Earth occultation of Sun, following C/A, maximized for ranges <=40,000 km >= 13 days + 2 hrs, beginning 2 hrs before C/A DSN tracking as continuously as possible from encounter - 10 hrs to encounter + 10 hrs after final TCM prior to ESB, prior to MAG boom deploy, and at > 2 days prior to last outbound Earth orbit crossing
Near Venus 2
CAPS Observations ISS Venus-2 Observations Venus-2 MAG Field MIMI Venus-2 RPWS Venus-2 Science UVIS Venus-2 Activity VIMS Observations Venus 2 - ESB CDA Activity Near ESB CAPS Calibration MAG Boom Deployment MAG Calibration CAPS ISS MAG MIMI RPWS UVIS VIMS characterize interaction of Venus with Solar Wind flat-field calib. for ISS WAC and NAC measure magnetic field science obs.; UV sensitivity calib. measure plasma waves and search for lightning measure Venus airglow; determine thermosphere time variation map tropospheric motion and night side of Venus continuous interplanetary dust measurements calibrate spectra and take data deploy MAG boom calibrate MAGs alignment
CDA CAPS MAG MAG
MIMI Earth Swingby RADAR Operation
MIMI RADAR
calibrate sensors and take data transmit and receive pulses for closed-loop test of RADAR
RPWS Validation and RPWS Testing Earth Flyby RSS Trajectory Determination VIMS Covers VIMS Jettison and Deployment Near ESB; using Moon ISS Lunar Calibration ISS UVIS Characterization VIMS Calibration After ESB CAPS Earth Observation CDA Dust Measurements MAG EarthExtended-Tail Operations MIMI Earth Magnetotail RPWS Magnetotail Observations UVIS Observations UVIS VIMS
validate capability to determine propagation characteristics of plasma waves; test directionfinding capability search for anomalous trajectory perturbation by determining pre- and post-flyby trajectory jettison of VIMS IR channel radiator cover; deployment of VIMS IR channel optics cover
image the Moon for several calibrations; study regional compositional differences on Moon characterize scattered light w/ EUV & FUV; characterize HDAC sensitivity calibrations and science data using the Moon
40 min near C/A to Moon, dictated by pointing restrictions 30 min, beginning when Moon enters the UVIS slit 1.5 hrs beginning ~2 hrs before C/A, and 2.0 hrs beginning ~1 hrs after C/A ~5-day HGA-to-Earth period centered on opposition 29 days, from ESB to HGA-to-Earth period* 29 days, from ESB to HGA-to-Earth period* 29 days, from ESB to HGA-to-Earth period* 29 days, from ESB to HGA-to-Earth period* 29 days, from ESB to HGA-to-Earth period*
CAPS CDA MAG
observe geomagnetic tail and interstellar particles continuous science dust measurements measurements of the magnetic field in Earths magnetotail calibrate LEMMS, CHEMS, and INCA; magnetotail measurements look for signatures of the distant geomagnetic tail UV measurements of the geocoronal H tail; measurements of Lyman , , and He 584
MIMI RPWS UVIS
* in sleep mode for TCM-13
6-13
130 of 217
Figure 6.8 Cassini Venus 2 Science Timeline (C14 Sequence), Time Frame = 16 hours
1999 DOY 175176(June 24-25)
10:00
11:00
-11:00
12:00
-10:00
13:00
-09:00
14:00
-08:00
15:00
-07:00
16:00
-06:00
17:00
-05:00
18:00
-04:00
19:00
-03:00
20:00
-02:00
21:00
-01:00
22:00
23:00
00:00
01:00
02:00 UTC
Relative to C/A
+00:00 +01:00
+02:00 +03:00
Venus 2
1999-175/21:50:11 UTC
Milestones
Estimated Bow Shock Crossings
CAPS MAG RPWS MIMI ISS VIMS UVIS

VIMS Power On 174/15:26
CAPS Science MAG Science RPWS Science MIMI Science ISS Science and Dark Frames VIMS Science UVIS Science
CAPS MAG RPWS MIMI ISS VIMS UVIS
FSO Keep-Out Times (V2 roll + verification)
APGEN 5-hour timeline Fields and Particles Instruments Remote Sensing Instruments
Power On
Observation
Power Off
Power On
Observation Power Off
FOIA 10-JPL-F-00451
131 of 217
Figure 6.9 Cassini Earth Swingby Science Timeline (C15 Sequence), Time Frame = 16 hours
1999 DOY 229230(August 17-18)
20:00
-08:00
21:00
-07:00
22:00
-06:00
23:00
-05:00
00:00
-04:00
01:00
-03:00
02:00
-02:00
03:00
-01:00
04:00
05:00
06:00
07:00
08:00
09:00
10:00
11:00
12:00 UTC
+00:00 +01:00
+02:00 +03:00
+04:00 +05:00 +06:00 +07:00 Relative to C/A
Blackout
Milestones
1999-230/02:47:40 UTC ORS Boresightat Moon Center
1999-230/04:02:33 UTC Earth Swingby CAPS Science CAPS to Sleep 243/03:55 MAG to Sleep 243/03:59 RPWS to Sleep 243/03:58 CDA to Sleep 243/03:55 MIMI to Sleep 243/03:57
CAPS MAG RPWS CDA MIMI ISS VIMS UVIS RADAR
CAPS Power On 229/16:00-20:52 SCAS 2 MAG Power On 225/16:00-16:15 RPWS Power On 225/17:00-17:07 CDA Power On 089/04:05 (C13) MIMI Power On 229/12:00-16:00
CAPS MAG RPWS CDA MIMI ISS VIMS
MAG Science/Calibration RPWS Science CDA Science MIMI Science/Calibration
ISS Science and Dark Frames VIMS Power On 227/20:0520:15 VIMS Science and Solar Port Observations UVIS Science RADAR Science RTE&SPB 14220 SAF 248850a S&ER3 SAF 248850a SAF 142200 S&ER3 SAF 248850a RTE&SPB 14220 UVIS to Sleep 243/03:56
UVIS RADAR
Telemetry Mode
APGEN 5-hour timeline Fields and Particles Instruments Remote Sensing Instruments
Power On
Observation
Power Off
Power On
SCAS Operation (MAG)
7 Dec 98 (SKS)
132 of 217
Figure 6.14 Cassini Science Timeline for HGA Period (C16 Sequence), Time Frame = 12 days
1999 DOY 248260(September 517)
248 249 250 251 252 253 254 255 256 257 258 259 DOY 260 UTC
-6 days -5 days -4 days -3 days -2 days -1 day +0 days +1 day +2 days +3 days +4 days +5 days +6 days relative to HGA transition
C15
C16 1999-256/09:38:25 UTC Opposition
Milestones
CAPS MAG RPWS CDA MIMI UVIS PROBE Antenna Telemetry Mode
CAPS at 267 bps MAG at 24 bps RPWS at 200 bps CDA at 524 bps MIMI at 467 bps UVIS at 242 bps UVIS Science CDA Science
CAPS Science MAG Science MAG at low rate
CAPS MAG RPWS CDA MIMI UVIS

Probe Checkout
RPWS Science CDA at low rate MIMI Science
PROBE
LGA 1
HGA
LGA 1
RTE&SPB 14220 SAF 248850a S&ER3
SAF 142200 SAF 248850a
PCHK
Fields and Particles Instruments
Remote Sensing Instruments
Power On
Observation
Power Off
Power On
7 Dec 98 (SKS)
133 of 217
Figure 6.11 Earth Flyby The Earth flyby occurred 55 days after the Venus 2 flyby on 18 August, 1999 (see Figure 6.11). The spacecraft approached the Earth approximately from the direction of the Sun. Closest approach occurred right after the spacecraft entered the Sun occultation zone. The occultation lasted approximately 30 minutes. The altitude at closest approach was 1175 km , with an Earth-relative velocity of 19.0 km/s. Trajectory correction maneuvers took place 43 (Venus 2 +12), 30, 15 and 6.5 days before closest approach, and a clean-up maneuver 13 days after the flyby. Continuous DSN coverage began at the Venus 2 Flyby and continued through the Earth flyby. DSN coverage dropped to 1 pass every 2 days at Earth + 1 week. A timeline for Earth science activities between Venus and Earth is shown in Figure 6.8. The post-Earth science activities through opposition are shown in Figure 6.9. 6.2.3.1 EARTH SWINGBY CONSIDERATIONS The Cassini project was required to assure that an inadvertent reentry of the spacecraft at Earth be next to impossible (mean probability less than one in a million). This resulted in constraints on all project elements, including the mission. For details on failure rates and protection, refer to the Project Policies and Requirements Document (699-004), Subsection 4.2. The mission constraints fell mostly in the Venus-2 to Earth leg. First, the trajectory design over the launch period was constrained to Earth swingby altitudes no lower than 800 km. Second, the bipropellant system needed to be in blowdown mode for the leg, with no pyro events or any other propulsion activities not needed for trajectory correction maneuvers or maintenance of a Sun-pointed attitude between maneuvers. Third, the orientation of the spacecraft was constrained during the leg to roll the Huygens probe to the ecliptic in the leading direction of the heliocentric trajectory (the High Gain Antenna remains Sun-pointed; see Section 8 constraint ESB-C4). This served to shield some parts of the spacecraft from micrometeoroids. This attitude was compatible with maintaining 6-17
134 of 217
communications with the spacecraft through LGA 2, which points in the same roll direction as the probe. Fourth, the spacecraft was required to be tracked continuously to rapidly detect any deviation from the desired course so that corrective actions could be taken if needed. Fifth, the magnitude and direction information (parameters) needed to perform the final maneuver before the Earth swingby were uplinked about 24 hours before the maneuver, and were zeroed out of the sequence immediately after the maneuver. This protected against an inadvertent repeat of the maneuver. The trajectory of this leg was biased away from the Earth aimpoint until the last 6.5 days. The most important effect of the biasing was to keep the V magnitude required to impact the Earth greater than 1.6 m/s over the entire leg, which nullified the effect of several small V failure modes. The biasing strategy is detailed in the Earth Swingby Plan and the Navigation Plan, and was crucial to meeting the Earth swingby requirement. The Venus 2 - Earth portion of cruise contained not only demanding navigation coverage, but some of the worst conditions for telemetry as well. Continuous DSN coverage was required throughout the Venus 2 - Earth leg. Continuous coverage was defined as no gaps greater than 8 hours (Earth Swingby (ESB) requirement 418-1D(k)in Project Policies document). From the beginning of the subphase through Earth closest approach, LGA2 was used. After the Earth flyby, the SPE angle dropped to low values again and LGA1 was used until the thermal constraints allowed the HGA to be used in February 2000. During the LGA coverage, uplink/ commanding of at least 31.25 bps was accomplished. Telemetry from each TCM and flyby was downlinked. Telemetry coverage for the Earth Magnetotail passage, leading up to opposition required several additional passes since the 14.22 kbps capability was no longer available. 6.2.3.2 MAG BOOM DEPLOYMENT AND EARTH FLYBY CALIBRATIONS Within the 24 hour period surrounding Earth flyby, the spacecraft passed in and out of the Earth's magnetosphere. This time was the most crucial for magnetometer alignment calibration to ensure that measurements at Saturn are accurate. Without the measurement of Earth's welldefined magnetic field, the measurement threshold of the instrument would be degraded enough to prevent the achievement of at least one major science goal (the measurement of Saturn's magnetic field orientation to an accuracy of 0.1). The Project also accepted activities for CAPS, MIMI, RPWS, Radio Science, and VIMS during the approach to Earth as well as ISS, UVIS, and VIMS observations using the Earths moon. RADAR observed the Earth just after Earth closest approach. Figure 6.12 shows the MAG boom deployment activities. Thermal restrictions limited the boom deployment to some time after the last outbound passage of 0.97 AU (which occurred 5 days prior to Earth). The MAG boom deployment was placed 44 hours prior to Earth. This location avoided the scheduled pre-Earth maneuver periods and gave the navigation team enough time to determine whether or not an Earth avoidance contingency maneuver (TCM-12a) was necessary. If the contingency maneuver would have been necessary, the MAG boom deployment and science calibrations would have been dropped from the sequence.
6-18
135 of 217
E-10d E-9d
E-8d
E-7d
E-6d
E-5d
E-4d
E-3d
E-2d
E-1d
ECA E+1d E+2d E+3d E+4d E+5d
Major Events
TCM 12
MAG boom deployment Earth Flyby (1160 km) 18 August 1999 TCM 12a* cruise ME TCM off cruise approx. 2 hr** approx. 1.5 hr off deployment off off Sun Occultation ~30 min cruise approx. 1.5 hr off cruise
Operational Modes
MAG calibration sequences
SCAS
on
MAG Activities
alignment determination off
v
SRU roll, moon viewing - E5hr
S/C Attitude
(except TCMs)
HGA to Sun/Huygens Probe to Velocity Vector-heliocentric
HGA to Sun/+Y to V-heliocentric***
DSN Coverage
(34m antenna)
continuous - 3 passes/day to E + 2 days

LGA 2 LGA 1
Antenna Days Past Launch

220 222 224
226
228
230
232
234
* Backup TCM (12a) at E - 3.5 days, if required for accurate Earth flyby targeting. ** MAG and SCAS should be warmed up before the boom is deployed. *** Pointing for MAG calibration from E - 4 hours to E + 24 hours is HGA to Sun and +Y axis to TBD (based on MAG sensor FOV). Sun occultation begins just before closest approach with duration ~30min.
Figure 6.12 MAG Boom Deployment and Alignment Determination Activities
FOIA 10-JPL-F-00451
136 of 217
The MAG Calibration sequence was planned to be in effect for a cumulative period of 6 days, broken up into two blocks. The MAG team used SCAS (Science Calibration Subsystem) for about five hours during near-Earth MAG operation: two hours while the MAG boom was being deployed, about one and one-half hour before entering the Earth's magnetosphere, and one and one half hour after exiting the Earth's magnetosphere. The purpose of SCAS is to create a known magnetic field for the magnetometer to measure. The HGA was constantly Sun-pointed throughout this time period, and Earth's magnetic field lay within the magnetometers 45 field of view, which is along the X axis. 6.2.3.3 POST-EARTH ACTIVITIES After Earth closest approach, there were are several other activities planned. The RADAR observation performed an end-to-end test of the RADAR system using Earth as a target. Several instruments finished up their Earth calibrations and science measurements and then remained on, except during TCM 13 (E+13days) when they were in sleep. The instruments came on again after the TCM and stayed on until just prior to the Probe Checkout at E+27 days, when they were turned off. The spacecraft turned the HGA toward Earth at E+24 days which allowed high data return on the HGA. The Probe Checkout 4 occurred just prior to the end of the HGA period. After four days on HGA, the spacecraft was turned back to Sun point, switched to LGA1, and turned MAG and CDA on. MAG was turned off four days later. CDA remained on throughout the rest of the sequence. 6.3 OUTER CRUISE PHASE The outer Cruise Phase consists of subphases for HGA Transition, ICO-2, Jupiter, and Quiet Cruise. This subsection provides an overview of the activities and plans in the outer cruise phase, which extends from 8 November 1999 (when the spacecraft reached a Sun range of 2.7 AU) to 7 July 2002 (about SOI - 2 years). At 2.7 AU, the HGA began continuous Earth-pointing, with the restriction that the Probe is used as a Sun shield for the rest of the spacecraft, without violating Probe thermal restrictions (PD 699-080, req #77606). A timeline for the Outer Cruise Phase and the Science Cruise Phase is shown in Figure 6.13. A second Instrument Checkout activity (ICO-2) was added for the summer of 2000 which required additional DSN passes to support science activities and reaction wheel unloading. The one planetary encounter in this phase was the flyby of Jupiter in December 2000. Extensive Jupiter science was accomplished which required additional DSN support. Science at Jupiter was an opportunity to test Saturn observation techniques. Data rates during this phase were much less tightly constrained than during most of the previous mission phases, because the final transition to exclusive use of the HGA, which was made on 1 February 2000. This fact made it much easier to perform cruise science and instrument checkout activities. The Outer Cruise navigation activities shown on the timeline include the seven TCMs between the Earth flyby until just after the Jupiter flyby. The DSN tracking coverage is also shown, and is driven in large measure by the navigation requirements for radiometric data to determine the spacecraft trajectory and plan the TCMs. Five of these TCMs, TCM-14 to TCM-18, occur in the Outer Cruise Phase. The DSN tracking for navigation data was typically 1 pass per week, with increased tracking around the maneuvers (TCM-21 to TCM+14) and the Jupiter flyby science observation period (1 October 2000-29 April 2001) . The engineering maintenance activities continuing from the Inner Cruise Phase including EGA Exercise, RWA Exercise, BAIL Maintenance, SRU Calibration, and PMS Flushing Maneuver. Additional new cruise engineering activities are listed in the Orbiter Cruise Activity Plan.
6-20
137 of 217
FOIA 10-JPL-F-00451
138 of 217
There are five scheduled Probe Checkouts in Outer Cruise. PCO 5 was performed 2 February 2000, one day after the spacecraft switched to the HGA. This PCO was the first time a Probe Checkout was performed with the Sun outside the HGA main beam. This provided a unique data set to investigate DWE performance in a noise-free environment. PCO 6 was performed 28 July 2000. This was moved earlier in time to allow science to use templates during the September timeframe. PCO 7 was performed on 22 March, at the end of the majority of Jupiter observations. PCO#8 was scheduled in September 2001, in C28. PCO #9 occurred approximately 6 month after PCO#8. 6.3.1 SPACECRAFT HGA CHECKOUT SUBPHASE The subphase occurred between the Venus 2-Earth and ICO 2 subphases, and incorporated sequences C17 to C19. Instrument activities during this subphase included the ISS and VIMS decontamination heaters being on, CDA dust calibrations, and MAPS observations after pointing the HGA to Earth . During the initial part of the subphase (C17 and part of C18), telecommunications were via LGA 1, and the spacecraft was at the farthest distance from Earth before transitioning to the HGA for regular use. Therefore, data rates were relatively low and activities were kept to a minimum. C17 included standard maintenance activities and one PEM. Sequence C17 also included the Y2K turnover, which did not cause any problems, although to be safe, all uplinks and critical activities were avoided for 3 days around the century change date. Activities during the LGA-1 portion of C18 included a PIM, ORS observations (by ISS, VIMS, and UVIS) of the asteroid Masursky near closest approach (1,634,000 km), and ISS dark frame calibration images directly following the ORS observations. The HGA was turned toward Earth for regular use on 1 Feb. 2000, during C18. Several activities took place during the rest of C18, using the greater telemetry capabilities available with the HGA: playback of the Masursky data and ISS dark frames, a Probe checkout, a Probe S-band Relay Test, a Telemetry-Ranging Interference Test, MAG calibrations, and a PEM. MAPS observations (by CAPS, CDA, MAG, MIMI, and RPWS) all began within a few days after transitioning to the HGA The first 6 weeks of C19 were used for a checkout of new Flight Software. The AACS version A7 software was uploaded near the beginning of this period, and the first 2 weeks were devoted to AACS tests. The next 4 weeks were originally scheduled for CDS tests of version V7.0. However, these tests were delayed to late July and August of 2000 to allow time for additional regression testing. During the AACS checkout period, MAPS activity ceased, although ISS and VIMS decontamination heaters remained on. Several activities took place during the last 3 weeks of C19: the MAPS observations resumed and continued throughout the sequence, three RSS activities (HGA pattern calibration, HGA boresight calibration, and USO characterization), the CIRS Cooler Cover release, and a PIM All activities were successful. A few days before the end of C19, the command loss timer setting was increased slightly, to account for the 10-day period at the beginning of C20 during which superior conjunction made commanding problematic. 6.3.2 INSTRUMENT CHECKOUT-2 SUBPHASE The second instrument checkout subphase was scheduled from 6 May 2000 to 5 November of 2000. This activity occurred after the spacecraft had begun using the HGA and the spacecraft office completed their engineering checkout activities. Communications were done on the HGA. Activities during ICO-2 included instrument checkout that required reaction wheel capability and any instrument checkouts that were not successfully completed during ICO#1. 6-22
139 of 217
In addition, pre-Jupiter science was requested during this subphase. The CDS Flight Software V7 uplink and checkout, which was delayed from March, was rescheduled to late July through early September 2000. This caused many of the ICO-2 activities to be rescheduled into a shorter and more dense period. Some activities were postponed until after the Jupiter observations were completed in 2001. The subphase began with a superior conjunction which precluded early science or engineering activities. MAPS instruments remained on to prevent cycling the instruments but data return was not assumed during conjunction. Two TCMs were scheduled for Jupiter targeting, in June and September. The later was moved out of October to allow for Jupiter science to begin using a repeatable template. Engineering activities included the continuous use of reaction wheels and beginning 1 October 2000, dual SSRs. There were no scheduled instrument PIMs done during ICO-2 since all instruments had other activities that accomplished this function. Other engineering activities included two RWA friction tests, two PEMs, and an SRU calibration. Science activities began with the MAPS instruments continuing from C19. New flight software was loaded for eight instruments in late May, and a CDA FSW update was done in September. New Quiet Tests while operating on reaction wheels, for most instruments were done in July, although the RSS Quiet Tests were done in September and RADAR related tests were done in late June. A Probe checkout occurred scheduled in late July. Spacecraft turns were done for RADAR observations of the Sun and Jupiter in June and again in September. The star Alpha Piscis Austrinus (Fomalhaut) was also be observed in September by VIMS with ISS and UVIS doing ride-along science. No other science turns were scheduled until October. October 1, science began using a repeating 5-day template to gather Jupiter science. This involved 11 turns in a 5 day period, including two downlinks. The turns in the 5day template involved 4 orientations: 6.3.3 ORS boresights to Jupiter, Z axis parallel to ecliptic HGA to Sun, rolling about Z axis Probe to Sun, rotating about X axis HGA to Earth, Probe offset from Sun for CDA , not rotating, downlink orientation JUPITER SUBPHASE
Additional instrument activities for calibration, checkout, and science were also scheduled. The Jupiter flyby occurred on 30 December, 2000 at an altitude of 9.7 million km with a velocity relative to Jupiter of about 10.4 km/s. This gravity assist rotated the trajectory 12 deg and increased the heliocentric velocity by 2 km/s. The Jupiter relative speed at closest approach was 11.6 km/s. At this distance, Jupiter filled the NAC field of view. Extensive Jupiter science was performed which required additional DSN support: templates using up to 2 passes every 5 days, and a maximum of 1 pass every 30 hours in the 10 days on either side of closest approach. Science at Jupiter was an opportunity to test how to build and execute viable Saturn sequences. The Jupiter subphase was from 6 November 2000 to 29 April 2001 and incorporated sequences C23 to C25. However Jupiter remote sensing observations actually begin on 1 October 2000, in C22. Figure 6.14 illustrates the flyby geometry for Cassini and for the previous Voyager missions. Although Cassini was not assumed to pass through the magnetopause, it actually recorded six crossings as well as 44 bowshock crossings during the Jupiter subphase. TCM17 occurred in the C24 sequence and was executed on 28 February 2001 to correct for Jupiter perturbation errors. RPWS calibrations were executed by small blocks of 10-hour duration during the Jupiter science observations repeating templates. The RPWS calibrations 6-23
140 of 217
were performed in the science repeating template 5 times before and 4 times after the Jupiter flyby.
100
Cassini Jupiter Cassini @ JCA

Voyager 1
0
2 days
-100
To Sun
Xo (Rj)
-200
Voyager 2
-300
V1-BS
-400
V2-BS V1-MP
-500
V2-MP
Trajectory Magnetopause (MP)

Bow Shock (BS)
-600 500 400

300
200
100
-100
-200
Yo (Rj) Figure 6.19 Cassini - Jupiter Magnetotail Passages

Engineering activities included the continuous use of reaction wheels and dual SSRs. There were no scheduled instrument PIMs done during the Jupiter subphase since all instruments had other activities that accomplished this function. Other engineering activities included: two PEMs, star ID extended bodies test, and RWA unloads. A Probe checkout occurred 22 March 2001 following a 5-day Probe Relay test in early February (in place of a 5-day science template). A RADAR radiometer calibration occurred at Jupiter flyby + 89 days. Beginning at Jupiter flyby 48 days, the spacecraft Ka-band was turned on for the rest of Jupiter subphase to perform the Ka-band upgrade task with DSS-25. Most of the RSS activities scheduled between the middle of March and the end of April 2001, were in preparation for the Gravitational Wave Experiment (GWE) test #1 that occurred at the beginning of May 2001. The preparation work for this GWE test included USO characterization, repeat of ICO Test E, 3-link test, HGA boresight calibration, Operational Interface Test (OIT) and its follow-up test, and HGA pattern calibration. There was also a successful in-flight test executed for the RTE&SPB 35.5 telemetry mode in C25, in preparation for using this new mode extensively in C26. Jupiter science observations were scheduled between Jupiter flyby 90 days and Jupiter flyby + 82 days. This period of Jupiter science observations was divided into A, B, C, D, E, F, and G 6-24
141 of 217
Jupiter science phases. Each of these science phases contained specific Jupiter science objectives and observations. Phase A occurred during the ICO-2 subphase. The Jupiter subphase science activities began with science phase B; the first ten days (Jupiter flyby 55 days to Jupiter flyby 45 days) contained two more instances of the late ICO-2 (phase A) 5-day science template. The C23 sequence incorporated phases B, C, D, and E, and covers from Jupiter flyby 55 days to Jupiter flyby + 15 days. The major science activities during these science phases, except for the science observations continued from the late ICO-2 5-day template, included 2x2 mosaics of Jupiter, ring movies, atmospheric and Europa opposition surge observations, north-south maps of Jupiter, Io eclipse observations, dust stream detection, coordinated Hubble Space Telescope (HST) and Cassini observations, and the observations of Callisto opposition surge and Himalia closest approach. When the spacecraft neared closest approach, resolution improved and the phase angle changed significantly, satellite and ring observations became more important. During this time frame, more atmospheric, ring, and satellite observations occurred, such as: the ORS boresights slewed slowly from north to south then stepped in a 1x3 mosaic from south to north; 3x2 mosaic was executed with full filter set and a 3x3 mosaic designed to obtain the best Jupiter picture; Io thermal studies and Io torus monitoring; and satellite eclipse observations. The coordinated Galileo and Cassini observations for Io dust stream and Io eclipses were performed during this closest approach time frame. The solar wind monitoring which began in Jupiter science phase A continued in C23. From Jupiter flyby to the end of C23, the most important science objectives include the coordinated HST and Cassini observations of Jupiters aurora and solar wind, phase angle coverage of Jupiters atmosphere and ring, coordinated Galileo ring and satellite observations, and the RADAR observation of Jupiters synchrotron emission. A problem with the RWAs occurred on 16 December 2000. Increased friction on one of the wheels caused the spacecraft to autonomously switch to the RCS for attitude control. With the switch to RCS, hydrazine usage increased. Two of the four joint CAPS-HST observations, a Jupiter North-South map, the Himalia "flyby", and a UVIS torus observation were all executed on RCS before the sequence was terminated on 19 December 2000. MAPS data continued to be recorded at a reduced rate. All other planned science activities were cancelled until 29 December, when they were resumed. RWA operation was resumed for attitude control on 22 December, with constraints imposed to avoid low RPM regions. This was accomplished by biasing the wheels. Continued testing by AACS personnel suggested the anomaly was a transient event so the sequence was restarted on December 29. Subsequent tests and studies eventually led to a Project directive to use the RCS system as primary control beginning with sequence C27. Observations lost due to the anomaly include four Jupiter North-South maps, two CAPS solar wind measurements, numerous Galilean satellite observations at various longitude and phase angles, Europa eclipse, numerous ring and Io torus measurements and Jupiter feature tracks. The science phases F and G were executed from Jupiter flyby + 15 days to Jupiter flyby + 82 days. Phase F occurred in the entire C24 sequence, and phase G occurred in the first 2 weeks of the C25 sequence. During this time frame, magnetospheric science was one of the most important science objectives since Cassini was in and out of the magnetosheath while Galileo was in the solar wind. This enabled the same type of science as inbound when Cassini was in the solar wind while Galileo was in the magnetosphere. Major science observations for science phases F and G included coordinated Cassini/HST for joint observations of Jupiters aurora, the outbound crescent movie, a search for lightning, and continuous monitoring of Ios torus emissions and dust streams. A slightly modified version of the tour ORS Operational Mode was used for all of the Jupiter science phases (A-G). RADAR activities were performed in SAF-142a and SAF 248 telemetry 6-25
142 of 217
modes, and all non-RADAR observation periods were performed in the S&ER-3 telemetry mode. 6.3.4 QUIET CRUISE SUBPHASE The Quiet Cruise Subphase is a 14 month period that started at the end of the Jupiter Subphase and ends at SOI - 2 years. During this subphase, routine maintenance, engineering, and navigation functions are carried out. One Gravitational Wave Experiment is planned for December 2001 and one Conjunction Experiment in June 2002. The Gravitational Wave Experiment preparation includes two one-week test periods starting in early May 2001 and August 2001. Many activities that were deferred from ICO-2, and were not accomplished during Jupiter activities are being scheduled during Quiet Cruise. In addition, newly proposed activities for both science and engineering activities are being considered for Quiet Cruise activities. Lists of all proposed science and engineering activities are documented in the "Post-Jupiter Final Scoping Package" which can be seen on the Mission Planning Home Page. The integration of science and engineering activities is done during the Science Planning Virtual Team activity which began in January 2001. Templates are again used to efficiently plan Science and engineering activities during Quiet Cruise. One change from the Jupiter Subphase is that data is recorded on only one SSR. A new telemetry mode of 35.5 kbps was implemented just prior to the Quiet Cruise subphase start to allow more efficient use of the downlink capability which is diminishing due to geometry. The Program Manager authorized increasing the requested DSN passes to 2 passes per week, minimum, to accommodate the increased science activity. Additional passes were also requested for GWE Tests, GWE, Conjunction experiment, and TCM 18. Other increases in DSN passes are expected to be requested for Radio Science activities, AACS activities, CDS new FSW, and Probe tests. All new requests are to be documented in the Project Service Level Agreement. All cruise activities beginning in May of 2000 assumed RWA for attitude control. Since the anomalous behavior in December 2000, tests and studies led to a Program decision to use RCS as the primary attitude control system. RWA is allowed for certain activities that require increased stability or pointing accuracy, e.g., GWE and RSS tests. This restriction was in force beginning with C27. Other requests for turns on thrusters required approval by the Program Manager. 6.3.4.1 GRAVITATIONAL WAVE EXPERIMENTS The project requirements call for support of Gravitational Wave Experiments (GWEs) while en route to Saturn near at least three oppositions, for periods of at least 40 days each, and with Ka-band tracking coverage from Goldstone of one pass per day. Additional tracking is requested using X-band links with DSN stations at Madrid and Canberra. These experiments have been scheduled during the three oppositions after the Jupiter flyby in December 2001, December 2002, and January 2004. (However, the 2004 GWE has been rescheduled to begin 20 October 2003 in order to relieve some of the DSN resource contention in January 2004 due to Mars missions and other projects.) The spacecraft will be configured into the RSS2/RWA operational mode with X-band and Ka-band uplinks, and X-band and Ka-band downlinks. The X-band downlink is required for engineering telemetry, including HGA inertial pointing. Attitude control will be on reaction wheels for these 40-day periods. The spacecraft may be rolled 180 about the Earth line when needed, in order to reduce the reaction wheels momentum buildup without having to use the thrusters. Since the RTG thermal torque and the magnetometer-boom solar torque are body fixed, the reaction wheel momentum change due to the X- and Y-axis torque reverses direction under the effect of the 180 roll. The Z-axis momentum continues to accumulate, but the rate is acceptably low. Keeping the turn rate 6-26
143 of 217
below 180 per four hours assures that the Doppler stability is not compromised. The turns are expected to be performed a few times during each Gravitational Wave Experiment. Within a month before each GWE, GWE Test, and Conjunction Experiment, there will be a HGA Electrical Boresight Peak Calibration. This calibration lasts 2 hours and includes X- and Ka-band for the GWEs and S-, X- and Ka- for the Conjunction Experiments. These calibrations require telemetry modulation be turned off. Note that GWEs and Conjunction Experiments extend into the Science Cruise Phase. For more details about this calibration, consult the Calibration & Maintenance Handbook (PD 699-280). 6.3.4.2 CONJUNCTION EXPERIMENTS The project requirements call for support of conjunction experiments whose purpose is to perform tests of general relativity and to study the solar corona. These experiments will be conducted while en route to Saturn, near at least two solar conjunctions, for periods of at least 30 days each, and with Ka-band tracking coverage from Goldstone of one pass per day. Additional tracking has been requested at S-band for the study of the solar corona. These experiments have been scheduled during the two conjunctions preceding SOI, from 6 June 2002 to 6 July 2002 and from 16 June 2003 to 16 July 2003. The spacecraft will be configured in the RSS2/RWA operational mode. For complete calibration of the plasma noise during the general relativity test, X-band and Ka-band uplinks and X-band and Ka-band downlinks will be used. The solar corona study requires X-band uplink and simultaneous X-band and S-band downlink (for SEP > 2) and X-band uplink and simultaneous X-band and Ka-band downlink (for SEP 2); Doppler and range (at X-band) data will be acquired throughout the conjunction experiment. Attitude control will be on reaction wheels during these 30-day periods. 6.4 SCIENCE CRUISE PHASE Cruise science and instrument calibrations continue during the Science Cruise Phase, which begins on 8 July 2002 and continues through 15 May 2004. Subphase activities include instrument calibrations, late cruise science, and preparation for Phoebe Flyby science, and Saturn approach science. Two subphases comprise this phase: Space Science and Approach Science. In the spring of 2003, new flight software will allow engineering data will be sent to a separate partition on the SSR so that not all engineering data need be downlinked on every pass. The impact of this is to increase the SSR data volume available for science data. Mission and Science Operations software for science pointing, timeline analysis, opportunity analysis (geometric observation models), resource allocation, science data records, etc. are all to be completed by January 2004 to support the Approach Science subphase. The Cassini Mission and Science Operations/Science Interface Requirements Document (GS/Sci IRD, 699-110) contains a complete list of Mission and Science Operations and Science deliverables. 6.4.1 SPACE SCIENCE SUBPHASE The Space Science subphase begins on 8 July 2002 and runs through 10 January 2004. TCMs 18 and 19 will occur during the Space Science Subphase. Activities during this period have been requested in the post-Jupiter Final Scoping Package, and the Space Science Scoping package. Two GWEs are scheduled during the Space Science Subphase. These occur in December 2002 and October 2003. The second Conjunction Experiment falls during the Space Science Subphase. It is scheduled for June 2003 to July 2003. There will be a SOI readiness test to simulate the activities associated with SOI. This will take place about one year prior to SOI. There will be a Probe Relay operational readiness test approximately November 2003. This will include orienting the Orbiter to point the HGA to a simulation of the Probe touch-down point on the rotating surface of Titan. 6-27
144 of 217
6.4.2
APPROACH SCIENCE SUBPHASE
The approach science subphase covers the period from 12 January 2004 through 15 May. At this point in the trajectory the spacecraft has long since left the Jovian system and is approaching Saturn at a rate of 5 kilometers per second. Most of the activities during this four month period will be Saturn science observations and preparation for the Phoebe flyby, SOI, and Tour operations. The reaction wheels will be turned on for continuous use about SOI - 6 months to provide a more stable viewing platform. At this point or earlier, the imaging instruments may begin atmospheric imaging, and making long-term atmospheric movies. CIRS will begin long integrations of Saturns disk. At SOI - 4 months, Saturn fills one third of the NAC field of view, and one half of the CIRS FIR field of view. The Saturn approach is made toward the morning terminator at a phase angle of about 75, and VIMS will gather data on the temperature difference across the terminator. UVIS scans of the Saturn System will begin at SOI - 3 to 4 months. Fields, particles, and waves instruments will also be collecting solar wind information and recording Saturn emissions as the spacecraft nears the planet. Science data gathered during this period will be stored on the SSR and transmitted back to Earth. Tracking coverage at the start of the subphase is increased to 3 passes per week, even though the first two months are heavily contested with other projects for DSN resources. Daily tracking coverage begins at SOI - 90 days.
6-28
145 of 217
SECTION 7: SATURN AND TOUR ACTIVITIES 7.1 SATURN APPROACH AND PHOEBE The first event of the tour (though it occurs before SOI) is a targeted encounter with Phoebe 20 days prior to the SOI burn. Among planetary satellites, Saturns outermost satellite is unusual. Phoebe has a rotation period of about 9.4 hours, an orbital period of 550 days, and a diameter of about 220 km. Its inclined, retrograde, chaotic orbit is strong evidence that the moon is a captured object. There is some evidence from albedo measurements that there may be craters on the surface. Determining whether or not Phoebe is asteroidal in character is an important scientific goal. Determining the density of Phoebe is important in meeting this goal. As this is the only possible encounter with Phoebe, the data acquisition opportunity is unique. The science operating modes used for this flyby are likely to be 1) the ORS mode to allow ISS, CIRS, UVIS, and VIMS observations as well as a more accurate determination of the Phoebe rotation period and 2) the RSS2/RWA mode to allow mass determination. The flyby of Phoebe occurs on 11 June, 2004, 19 days before SOI. The Phoebe closest approach is at 2,000 km altitude at 19:32 UTC, at a phase angle of 155. The imaging characteristics are shown in Figure 7.1. Beginning about 10 hours from Phoebe, the NAC FOV is rapidly filled. At closest approach the resolution of Phoebe will be about 12 meters/pixel. This resolution, which is 1500 times better than Voyager, is excellent for morphologic mapping, and for studying the geologic character of Phoebe, including mapping the surface. A complete map of Phoebe is desired with the range less than 160,000 km. During the approach to Saturn, there are three approach TCMs. TCM 20 is the final Phoebe targeting maneuver. TCM 20 is done with pressurized tanks and is accomplished by firing pyro valve 25 and opening latch valve 10. After TCM 20 is complete, LV 10 will be closed until 70 seconds before the SOI burn begins. TCM 21 ensures that the B-plane delivery error at the orbit insertion point is less than 130 km (one sigma). This maneuver needs to be done at least 14 days before SOI because the fault protection recovery period, based on Magellan and Voyager experience, can be as long as two weeks if the fault is difficult to diagnose and/or new software uplinks are required. There is another TCM opportunity at S-10 days which is available if needed. Two SSRs are used for recording science data beginning June 1, 2004. The Saturn approach and initial orbits are illustrated in section 2. 7.2 SATURN ORBIT INSERTION Saturn Orbit Insertion occurs on July 1, 2004 and is timed to allow a close approach to Phoebe at good phase angles. This arrival date also allows an opportunity for a non-targeted flyby of Titan about 31 hours after SOI at a distance of less than 340,000 km. This Titan-0 opportunity (revolution 0 is defined as the orbit segment from SOI until the initial apoapsis) may be used to confirm the Titan wind direction prior to the Probe delivery. 7.2.1 OVERVIEW Figure 7.2 shows the SOI Events Timeline. After the Phoebe flyby and clean-up TCMs, there is a Quiet Period that begins 8 days before the SOI burn. Approach DSN coverage is one pass per day, with continuous coverage on TCM days, and continuous coverage beginning S-2 days and continuing through S+1 day. Consideration is being given to extending the continuous coverage on both sides of the burn. Before the critical sequence begins, the spacecraft will turn off reaction wheel control and go to thruster attitude control. This will allow turns for safing, SOI burn orientation, and science viewing to be done faster than if on wheels. During the Quiet Period and burn itself, only Fields and Particle instruments will be on. Other instruments will be either in sleep or off. This is in order to keep high power margins for the critical burn event. Spacecraft vibrations during the main engine firing are likely to degrade remote sensing in any case. 7-1
146 of 217
FOIA 10-JPL-F-00451
147 of 217
After the burn is complete the spacecraft will turn to Earth briefly to determine whether safing has been entered during the critical sequence. At the end of the critical sequence, the background sequence will begin with post-burn science. Rev 0 science is unique in that it is the closest the spacecraft will be to Saturn and provides unique opportunities for environmental measurements as well as close images of Saturn and its ring system. Following the descending ring plane crossing, data from the critical sequence execution and post-burn science will be played back. An opportunity to observe Titan occurs on the day after SOI. The initial SOI clean-up TCM occurs two days after SOI. The Solar Conjunction (3 SEP) period begins on 3 July at 08:53 and continues until 12 July at 15:55. During Solar Conjunction, no pointing changes are allowed (rolls OK) and no downlinks are scheduled (except for Radio Science experiments). A final SOI clean-up maneuver is planned for SOI + 15 days. Table 7.1 summarizes the activities and states near SOI. Details of the SOI period are discussed in the following subsections. 7.2.2 SOI TRAJECTORY Figure 7.3 shows the SOI trajectory and SOI burn geometry. Figure 7.4 shows the SOI approach trajectory looking down on the ring plane from the North Saturn Pole. Occultation zones on the rings can be seen on this projection. Occultation zones on the trajectory are shown in Blue (Earth) and Yellow (Sun) .
SOI Events Timeline

Phoebe Targeting TCM bi-prop pressurization SOI-35 Phoebe Flyby SOI-19 d
Phoebe Saturn Clean-up Periapsis TCM Approach SOI-15 d Clean-up (if needed SOI-10 d) Activate Critical Sequence Start Quiet Period SOI initial SOI-8 d Clean-up SOI+2 d Critical Sequence Execution
pre-Quiet Period sequence S1 Day of Year (DOY) 145

Passes 3 2 per 1 day 0
Quiet Period CS post-Burn Period sequence S2
150
155
160
165
170
175
180
Solar Conjunction
SOI Final Clean-up SOI+15 d
185
190
195
200
Figure 7.2
7-3
148 of 217
SOI SUMMARY
Pre-Quiet Period Epoch Add start/stop times for each period Prior to QP (Day 175) Quiet Period ~S-8 day - Start Day 175 0:0:0/ ends at turn to safe attitude for ARPC 182 23:47:00 ARPC Start at turn to safe attitude Day 182 23:47:00, continue until SOI burn start 183 01:12:00 Open SOI Burn
start at burn start 183 01:12, ends at end of critical sequence 183 03:03
Post-Burn
Period
DRPC Start at safing turn for DRPC 183 ~04:21 ends at star of Downlink to Earth ~04:54
Downlink to Earth Start beginning of downlink ~04:54, end after D/L of critical sci and engr data ~ 22 hrs later.
Start at end of crit sequence 183 03:03, ends at turn to safe for DRPC ~04:21
ME Cover
Open since TCM 20 (S-35d)
Open for burn - Critical Sequence closes cover after burn ends
Closed
SSRs
Spacecraft Orientation
Two, beginning S1 SSR for QP and critical sequence. Ping-pong is disabled 8 weeks, or during critical sequence possibly earlier Defined by HGA Earth HGA to particle ME toward velocity Science, downlink pointed, RAM, SRU up, direction. Yaw daily secondary axis is Probe down steering, SRU up, ORS +X to Saturn toward Saturn, boom North Pole away from Saturn parallel to rings Any OK, TBD by science
Other SSR for post-burn science and engineering
HGA initially to Earth, HGA to particle followed by turn to RAM, Probe view rings and Saturn looking down, SRU up, boom parallel to rings
HGA Earth pointed, +X (SRU) up, turn to Earth to call home and D/L data
Instruments ON
Strawman has CAPS, CDA, MAG, MIMI, & RPWS with power ON, Any (except RADAR) others are in sleep CIRS, ISS (NAC), UVIS, & VIMS or OFF INMS, OK, TBD by science ISS(WAC), RADAR, RSS, SCAS, Probe (Science duration ~75 m) INMS cover jettison requested ASAP after burn
FPW + TBD
FPW
Science Attitude control mode Deadband
No RWA
Restricted*
Yes* RCS
Yes*
Normal Op Mode power restrictions RCS [2,2,20]
set to [2,2,2] 55 [2,2,20] when change from RWA minutes prior to to RCS in QP burn start
[2,2,2]
*Restrictions: no power, attitude, engineering configuration changes (except as needed for ARPC and SOI burn)
FOIA 10-JPL-F-00451
149 of 217
Pre-Quiet Period Turns Saturn viewing allowed, downlink dailyto Earth
Quiet Period None until 60 min prior to ARPC for safe s/c orientation
ARPC Turn to burn attitude 10 min after ARPC (wait for Star ID resumption) Turn duration 10 min
SOI Burn
Post-Burn
Period
DRPC
Downlink to Earth Turn to Earth after DRPC - Wait 10 minutes for resumption of Star ID
Yaw steering for burn. Background turns to Turn to safe attitude prior to Critical sequence also start science after DRPC initiates turn to Earth Turn to earth. Science turns prior to after burn ends DRPC are TBD
Turn Times (get exact times)
~ 12.3 minutes for ~ 13 minutes to burn attitude safing turn
Turn to Earth after burn ~4.3 min
~ 6 min to initial science orientation
DSN passes
vary daily
1 pass/day, then continuous continuous passes coverage but not from S-2 days Earth pointed through SOI day
continuous coverage but not Earth pointed until end of Burn, which is over Canberra
< 15 min for safing turn (depends on last sci orientation) continuous coverage but not Earth pointed
~13 minutes
Turn to Earth over Madrid
Critical Sequence
loaded 8 weeks Critical Sequence prior to periapsis Safing Status HGA to Sun Point Either Sun- or Earth-pointed, depending on type of Fault (HAS algorithm) Contingency Plans Autonomous FP in critical sequence
executing - ends with close ME cover and turn to Earth ME in burn direction, or HGA to RAM HGA Sun-Pointed direction during call home seqment Safing turn is in critical sequence
N/A TBD ( HGA to Sun or HGA to RAM)
Telemetry mode
varies
S&ER10
Downlink -
BWG 1896-22k
HEF 1896-27.6k
Call home after burn ME cover is closed ME burn in critical sequence, including ME confirms pointing swaping& burn restarts direction. If safing occurs, no science TWT disabled during S&ER10 burn, record at S&ER10 70m 35.5K-82K (70 m on SOI day in case of safing)
Other
PMS checkout done at S-35 days
Disable star ID for Tank pressurization RPC
Be aware of radiator Disable star ID for one-way LT is 83 exposure to Saturn RPC minutes. during ring plane obs.
*Restrictions: no power, attitude, engineering configuration changes (except as needed for ARPC and SOI burn)
FOIA 10-JPL-F-00451
150 of 217
Figure 7.3 SOI Geometry
Figure 7.4 SOI Arrival Geometry Even though Cassini is going through the rings in a location considered safe, there is still some chance that ring particles can strike the spacecraft. As Cassini approaches the ring plane, the 7-6
151 of 217
spacecraft will turn to place the HGA in the ring particle RAM direction. This turn will take place about 85 minutes prior to the start of the burn. From this time until the burn is completed, the spacecraft is out of communication with Earth. The spacecraft will turn to Earth briefly after the burn to confirm whether safing occurred during the critical sequence. The first downlink of SOI data is scheduled after the descending ring plane crossing, 95 minutes after pericrone. The main engine cover is open before the ARPC because there is not time to perform and confirm an open cycle between the ARPC and the burn start. The main engine cover will be closed for the DRPC. The spacecraft passes beneath the E ring from about 4.5 hours to 2.75 hours before periapsis. Sixty minutes prior to the initial ring plane crossing, the spacecraft breaks from Earth-point and assumes a safe attitude for the ascending ring plane crossing, which is between the F and G rings at 158,500 km from Saturn center. The debris hazard at the ring plane crossing location is expected to be small but significant. However, the risk to the main engine nozzles is nonzero, therefore it seems prudent to assume the safest possible attitude which will be HGA into ring particle RAM direction. The ascending ring plane crossing occurs 1 hour and 52 minutes before periapsis. After the ring plane crossing, the spacecraft is turned again to place the main engines in the correct attitude for the SOI burn. The X-band transmitter is turned off after the last downlink prior to ascending ring plane crossing and remains off until the burn is complete. The X-TWTA is turned on after the burn to allow signal acquisition. The spacecraft will turn to Earth after the critical sequence is complete to allow determination of the spacecraft state (whether in safing mode). The orbit insertion burn is designed to decrease the spacecraft's Saturn-relative energy to allow the spacecraft to be captured into Saturn orbit. The arrival trajectory, orbit insertion burn parameters, and Periapsis Raise Maneuver (PRM) have also been crafted to place the spacecraft on a trajectory that will bring it close enough to Titan to deliver the Huygens Probe into the Titan atmosphere several months after SOI. Because the arrival trajectory brings the spacecraft closer to Saturn and the inner rings than any time during the entire tour, the burn has been moved earlier than its optimal location (centered around periapsis) to begin shortly after ring plane crossing and end 10-15 minutes after periapsis. Immediately after the burn is complete, the spacecraft will turn to Earth so that it can be determined if the Spacecraft is in safe mode. After this short turn, the science instruments will conduct observations of the rings and near planet environment to take advantage of this unique opportunity. This early burn location also allows more time for a recovery should the burn fail to execute as planned. The trajectory will be occulted by Saturn from the Earth between 03:34 and 04:10. The trajectory will be occulted by Saturn from the Sun between 03:37 and 04:09. Clean-up TCMs are scheduled for S+2 days and S+15 days. The initial clean-up TCM will correct for insertion errors based on limited post-burn tracking. The final clean-up TCM will occur after the solar conjunction period. 7.2.3 SOI CRITICAL SEQUENCE OVERVIEW The Critical Sequence is loaded about 4 weeks before the Saturn closest approach. The Critical Sequence is activated 8 days before the burn, and the first critical command executes about 29 hours prior to the start of the burn. A Quiet Period is defined for the 8 days preceding SOI. During the Quiet Period, the spacecraft is Earth pointed. The purpose of this period is to have the spacecraft in a quiescent state that minimizes the chance for a spacecraft anomaly prior to the SOI burn. No turns or instrument articulations or power state changes are allowed, except to put the spacecraft into a safe orientation for the ascending ring plane crossing (ARPC) and to achieve the proper burn orientation after the ARPC. The critical sequence includes the turn for a safe attitude for the ARPC and turns to the burn attitude after the ARPC. The burn itself is the main focus of the critical sequence as this is one 7-7
152 of 217
of the most critical events (after launch) for a successful mission. Fault protection is customized to ensure the burn has every chance for successful completion. The critical sequence ends with a turn to Earth to allow determination of whether the spacecraft has gone into safing during the critical sequence. This information is important when later re-acquiring the spacecraft to downlink key engineering and science data. If the spacecraft goes into safing during the critical sequence, all scheduled background sequence events after the critical sequence will be cancelled. The main engine cover will be closed at the end of the critical sequence to afford additional protection for the descending ring plane crossing (DRPC). 7.2.4 SOI BURN The SOI maneuver is a 97-minute main engine burn with a total V of 632 m/s. The burn could take up to 5 minutes longer in the baseline case due to engine thrust variations, or hours longer if multiple faults or main engine swaps or engine restarts occur. The SOI maneuver places the spacecraft in an initial orbit with a periapsis radius of 1.3 Rs, apoapsis radius of 150.5 Rs, a period of 116 days, and an inclination of 16.8. An accelerometer will end the burn when the required velocity change is obtained. The SOI burn duration is also controlled by an energy based algorithm which will insure that the engine burns until the proper orbit is achieved. The spacecraft will be steered at a constant angular rate with the engine gimble actuators (EGAs) to keep the main engine pointed near the velocity vector during the burn. The spacecraft will turn approximately 45 degrees during the SOI burn to maximize the thrust efficiency. About 29 hours prior to the burn, the first critical sequence commands are executed. To insure proper power margin, the downlink transmitters must be turned off prior to the burn. The burn is done with pressurized tanks. Bi-prop tank pressurization was done for TCM 20. 70 seconds before burn start, LV 10 is opened to maintain pressurization. X and Y axis control is done by pointing the thrust vector slightly off the spacecraft center of mass to achieve the required torque about the X and Y axes. Full RCS control is regained once the burn is completed. RCS control is continued until the spacecraft descends through the rings, and regains Earth communications. The turn to regain the Earth line is done under RCS control. Both IRUs will be operating during the SOI burn. Star updates will be done during the SOI burn but vibrations set up by the main engine firings may cause smearing or other problems with star identification. Therefore, star updates during the SOI burn may not be available for attitude control. Good star tracking is expected up to one second before the start of the burn and within one second after the burn. Star updates will be suspended during the ring-plane crossings to minimize the chance of going into safing. Since the SOI burn must be made off Earth-line, no tracking coverage during the burn will be available. Therefore, final adjustments to the burn time will be based on tracking data and can only be sent at the latest on the day preceding the burn. Tracking data after that date will be used for trajectory reconstruction and planning the post-SOI clean-up maneuver. Tracking will also be degraded near solar conjunction, and the X-band tracking data is considered unreliable due to solar noise when the Earth is within 3 of the Sun. The Cassini spacecraft carries a redundant main engine in case the primary main engine fails. If the main engine experiences a fault during SOI, it will shut down, and a switch will be made to the redundant main engine after a minimum cooling period. The length of the required cooling period is a minimum of 10 minutes to an unused engine. Switching between engines that have already been used during SOI is done immediately. After the burn has ended the spacecraft will turn to Earth for a couple of minutes, and then turn to allow the ORS instruments to view the Saturn inner rings that are not in shadow. If the SOI burn completion is delayed due to a spacecraft anomaly, such as switching to the backup main engine, the postburn science background sequence will be deleted. After periapsis, the trajectory just grazes the occultation zones behind the planet with the Earth and Sun being occulted by Saturn. 7-8
153 of 217
7.2.5
ATTITUDE CONTROL STRATEGY
Beginning with the Critical Sequence start at S-8 days, the spacecraft will be on thruster control. Once the burn starts, control about the X and Y axes is done with the EGAs, while roll control is done by RCS. Post-burn science activities will be done on RCS. The change to RWA will likely be done during the first downlink following the DRPC. Star ID will be disabled 22 minutes before ARPC and re-enable 3 minutes after crossing the ring plane. For the DRPC, star ID is disabled 3 minutes prior and re-enabled 10 minutes after the ring plane. The differences in disable times are due to the direction the SRU is looking. For ARPC the SRU is pointed up, into the rings for approach; for DRPC, the SRU is pointed up, away from the ring plane on approach. Attitude control limits are [2,2,20] (S/C X,Y,Z uncertainty limits in mrad) during the Quiet Period until 55 minutes before burn start when it changes to [2,2,2]. The deadband limits are changed back to [2,2,20] at the end of the critical sequence. There are seven major turns that are part of the SOI period. Figure 7.5 summarizes the spacecraft pointing changes before, during, and after the SOI Burn. The main turns during this period are: - Earth point prior to ARPC, turn to HGA to RAM direction, SRU to Saturn North Pole - Turn to Burn orientation - Turn during burn (Yaw steering) to keep ME in proper orientation - Turn to Earth - Turn to view Saturn and Rings (post-burn science) - Turn for DRPC (HGA to RAM, SRU to Saturn North Pole - Turn to Earth for post-burn playback
Turn to Earth for few minutes ORS Radiators initially 26 min. exposed to Saturn, may need Yaw turn for protection INMS Roll to cover allow jettison ORS to view rings
Sc per ience iod view . ~ 74 ing min
SOI Burn Period

10 min Turn to burn attitude Complete 5 min prior to burn start
Ring Plan e Cr ossin g
(Yaw steer) Critical sequence includes burn, close ME covers, turn to Earth to confirm s/c status
Ring Plane Saturn

tion ing ec tion ss dir nta e croRAM e ori plan icle fe Sa ring part for A in HG
SRU SRU SRU ORS ARPC-60 min. SRU SRU ORS ORS
Ri ng
Pl
an eC
ro
ss
ing
1440 km Turn to P la regain sc ybac Earth lock en ience k gin P dat eer & a ing S ost- S cie a TBD nce turn
SRU ORS
ORS
97-102 Min SOI Burn
ORS
Turn to Safe Position
ARPC
Periapsis
Turn to DRPC Safe Position
SPACECRAFT ROLL ORIENTATION
Figure 7.5
7-9
R D oll to HGRPC saf eo Ai rie np nta art tio icle nf RA or M dir ec tio n
154 of 217
7.2.6
SSR STRATEGY
Recording in the SSR is done is partitions 4, 5, and 6. See subsection 5.3.1 for discussion of SSR partitioning. Partition 4 records science data and AACS and RFS engineering data. Partition 5 is for OPNAV data and will be resized to the default size for the critical sequence and postburn science period. Partition 6 is for a complete set of engineering data. Critical sequence science and engineering will be recorded on SSR-A while P4 engineering data will be recorded on both SSR-A and SSR-B. Post-burn engineering and science data will be recorded on SSR-B. Partitions 4 and 6 will be played back twice for each SSR, during the post-DRPC downlink. Prior to the Quiet Period, 2 SSRs are used to record approach science and downlink to Earth. Science recording and playback will be managed by the background sequence. Beginning with the Quiet Period, the ping pong option will be disabled and only 1 SSR (SSR-A) will be used during the Quiet Period and burn (all of the critical sequence). Engineering is recorded into P6 at 1623 bps and into P4 at 720 bps. The data on the SSR is considered critical engineering and will be preserved until it has been played back twice (over different DSN stations). Science data will consist of MAPS data and is considered critical after S-TBD minutes and will be played back twice. Data prior to that time need only be played back once. The partition sizes are shown in Table 7.2. Partition P4 P5 P6 Frames 203174 10 25596 Gigabits 1.788 0.000088 0.225 Table 7.2 SSR data volume during 36 hours of SOI events (from SOI burn 29 hrs to SOI burn + 7 hrs) is shown in table 7.3: Critical Sequence Partition P4 science P4 engineering P4 total P6 engineering SSR-A 1.709 0.079 1.788 0.179 SSR-B 0.0 0.006 0.006 0.0 Table 7.3 After the critical sequence ends, the SSR with critical sequence data will be preserved and the other SSR (SSR-B) will be used to record post-burn science and engineering. The post-burn science and engineering is also considered critical and will also be preserved until it has been played back twice. The first playback opportunity is after the DRPC. This pass is over Madrid and overlaps with a following Goldstone pass. These two stations will be used to playback the SSR data, with the critical sequence data being played back first. During the overlap between Madrid and Goldstone, both stations will receive the same SSR data which will shorten the time needed for the dual playback. 7.2.7 TELECOM STRATEGY Prior to the Quiet Period, DSN coverage and downlink strategy is one pass per day. This continues into the Quiet Period until S-2 days, when continuous coverage begins. The spacecraft is Earth pointed throughout the Quiet Period until the turn for ARPC. The telemetry 7-10
Engr rate bps 720 1623
Post-burn SSR-A 0.0 0.0 0.0 0.0 SSR-B 1.770 0.018 1.788 0.041
155 of 217
mode will switch between S&ER10 and a RT SPB mode during downlinks. At S-29 hrs, a switch to S&ER10 will be made and continue until the end in that record mode until after the DRPC. The turn from Earth line for the ARPC occurs 1 hr before ARPC, 1 hr 25 minutes before burn start. The spacecraft is out of communication until after the burn when the spacecraft turns to Earth to provide a carrier-only signal for a few minutes. This will establish whether the spacecraft has gone into safing during the critical sequence. Then the spacecraft turns from Earth to begin science viewing of Saturn and the Rings. Communication with Earth is re-established 5 to 30 minutes after the descending crossing, depending on the time needed to regain star tracking and lock up over Madrid. Except for the short carrier signal after the burn, the HGA will have been pointed off the Earth-line for a little over six hours. Once the post-burn downlink begins, the spacecraft will remain on Earth lock for about TBD (20) hours to play back recorded engineering and science data twice. 70 m passes will be used to playback the SOI data on the SSRs. 7.2.8 SCIENCE STRATEGY Science instrument operations are limited during the Quiet Period and SOI burn due to power limitations. Since no instrument change of state is allowed during the Quiet Period or burn, the SOI power limits affect which instruments can be operating. The Field, Particle, and Wave instruments (CAPS, CDA, MAG, MIMI, and RPWS) will be on during the Quiet Period so they can collect in situ data without requiring turns. MAG in particular needs to collect close-in field data. Other instruments are either in sleep or off, see Table 7.2. Table 7.4 SOI Quiet Period and SOI Burn Instrument Power States and Allocation
Instrument On Power W
21.0 11.7 46.0 26.6 26.2 19.4 13.4 19.0 85.3 16.9 83.0 24.0 13.0 27.3
Sleep Power W
15.8 12.0 29.0 16.6 22.3 16.4 10.0 16.9 0.0 3.15 0.0 0.0 6.6 12.9
Off Power W
16.5 11.25 9.8 4.0 9.0 5.0 3.4 2.3 0.0 0.0 0.0 0.0 3.5 7.6 0.0
Quiet Period/ Burn State

On On Sleep Sleep Sleep Off On On Off On Off Off Sleep Sleep Off Total Available
Quiet Period/ Burn Power

21.0 11.7 29.0 4.0 22.3 5.0 13.4 19.0 0.0 16.9 0.0 0.0 6.6 12.9 0.0 161.8 160.0
CAPS CDA (no art.) CIRS INMS ISS NAC ISS WAC MAG MIMI (special SOI config.) RADAR RPWS RSS SCAS UVIS VIMS Probe
Table 7.4 shows the SOI Quiet Period and SOI burn instrument power allocations. The slight overbudget total will be absorbed into the 70W margin being carried to protect against soft shorts. Note: There are several open issues that could cause the instrument power allocations to 7-11
156 of 217
increase or decrease. However, until those issues are resolved, the SOI science allocation during the Quiet Period and the burn is 160.0 w. After the critical sequence is completed, the stringent SOI power restrictions are lifted and normal Op Mode power limits apply. Instruments that were off or in sleep can come on. An attempt was made to allow instruments with long warm-up times to be in sleep during the critical sequence. Post-burn science is still in the design phase, but it is known that MAPS instruments will continue to collect data, ORS instruments will begin imaging Saturn and the rings, INMS will jettison its protective cover and begin collecting data above and through the ring passages. This subsection will be updated as soon as the science plans are firm. Specific science activities will try and get something for everyone who needs this unique closein data. Turns will be needed to protect radiators, and to give time to individual instruments. Details of the science design will be forthcoming after this Mission Plan is released. Post-burn science will be completed about 15 minutes before the DRPC to allow time to achieve a safe orientation. 7.3 INITIAL ORBIT After SOI there is a pair of cleanup maneuvers to correct for errors in the SOI burn. The first is immediately before the superior conjunction, at SOI+2 days, and the second is after conjunction at SOI+16 day. The initial clean-up will be based on only 1 day of tracking after the SOI burn is complete. The TCM cannot be delayed much further due to solar noise which degrades Doppler tracking around the conjunction period (5-12 July). Beginning with the Periapsis Raise Maneuver at SOI+53 days, a sequence of nine maneuvers is used to target the Probe and Orbiter trajectories for the proper entry and flyby conditions to accomplish the Probe measurements and the radio relay of the Probe data to the Orbiter. Three new Titan encounters: Ta, Tb, and Tc have been designed with a distant flyby during Probe delivery on Tc. These three initial Titan encounters replace the first two Titan encounters of the T18-5 tour. If the Probe cannot be delivered at the Tc flyby, a contingency trajectory exists that allows a second chance to deliver the Probe. This contingency retargets Tc to a lower altitude and introduces a new distant flyby, Td, for Probe delivery. However, this contingency causes Cassini to fall off of the tour and it doesn't return to the T18-5 tour until the 13TI (T6) flyby. The Periapsis TCM requires 392 m/s and the ODM requires 26 m/s. In addition to the TCMs, the initial orbit also contains three probe checkouts. The data from the last pre-separation checkout, along with Orbiter status, will determine whether or not to target to the Titan impact point at the Titan-1 flyby. DSN coverage after SOI is generally one pass per day. Additional coverage is required for unique events including maneuvers. Continuous coverage is required on maneuver days. Additional details on the Probe mission are given in the following subsection. 7.4 THE HUYGENS PROBE MISSION Figure 7.6 shows an overall timeline for the Huygens probe mission (supplied by ESA). The final checkout of the Probe will be made 31 days before its separation from the orbiter, and this supports a go/no-go decision to proceed with the Probe mission at the Titan-C encounter. Twenty-eight days before separation and 48 days before entry, a depassivation activity is scheduled for the Probe batteries to ensure that they are fully functional for entry and descent. The Probe targeting maneuver is then executed on December 18, 2004, two days before separation, and this places the spacecraft on an impacting trajectory with Titan. Final commands to the Probe are sent three days later to complete preparations for release, and this includes setting the Probe coast timer. 7-12
157 of 217
Nov04
Preliminary Probe Mission Timeline

Dec04
T M T W T F S S M T W 1 T 2 F 3 S 4 S 5 M 6 T 7 W 8 T 9 F S S M T W F S S M T W T F S S M T W T F S 1 S 2 M 3 T 4 W 5 T 6 F 7 S 8 S 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Post Ta Apoapsis Manoeuvre
Issue: 5.0
Jan05
M T W T F S S M
11 April, 2002 T W T F
Activity Name
11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
10 11 12 13 14 15 16 17 18 19 20 21
Major Milestones
Probe Critical Events Review
Tb
Tb approach PTM
Probe Release
ODM Iapetus C
Probe Entry Tc REV C
Rhea
2 Rev 3 Probe Activities 4 Probe Checkout 5 MTU Loading 6 Depassivation 7 MTU Loading Window 8 Probe Release Window 9 Probe Release/Entry 10 Coast 11 Probe Mission/Pback 12 Orbiter Activities 13 Manoeuvres 14 ODM Window 15 Earth Pointing 16 Probe Relay Seq Quiet 17 Active Period 18 Command Loss Timer 19 Uplink Probe Ops 20 UL Background Seq 21 UL Crit Sequence 22 Load Final Global Data 23
Go/No-go Decisions
REV A
REV B
Final Probe Checkout MTU Redundant Loading Battery Depassivation Battery status check MTU Loading
MTU Loading Window Probe Release Window

Probe Release Probe Entry
Coast
Post Ta Apoapsis Manoeuvre Tb approach
PTM
PTM Cleanup
ODM
Post Tc
ODM Window Earth Pointing Earth Pointing Probe Relay Seq Active Quiet Period
Variable CMD Loss Timer Command Loss Timer 11 days
24 25 Product Delivery 26 JPL File 27 ESA HGA Pointing File 28 Science Activities
Proposed Sequence 29 Boundaries Current Sequence 30 Boundaries DSN Passes
Go/No go for primary mission
Go/No-go for PTM
Go/No go for Delayed Release
Go/No-go for PTM cleanup
Go/No go for MTU loading
Go/No go for Separation Go/No go for ODM
Go/No go for Global data load
Go/No go for SSR release
Restricted Activities
Quicklook Reconstruction MAPS only
S5
S6 S5
S7 S6 S7
31
32 SFOF Freeze Level

11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
FOIA 10-JPL-F-00451
158 of 217
Separation of the Probe then occurs on December 24, 2004, which is 21 days before entry (E-21 days). The Probe Spin/Eject Device (SED) separates the Probe with a relative speed of 0.3 - 0.4 m/s and spins it up to a rate of > 5 rpm. At separation, the Probe axis is pointed to achieve a zero-angle-of-attack entry and such that the velocity increment provided by the SED springs provides the final targeting to the entry aimpoint. The last two maneuvers of the Orbiter before Probe entry provide its final targeting to the required aimpoint to achieve the radio relay link geometry and to obtain the required gravity assist from Titan for subsequent encounters in the orbital tour. The first of these is the Orbiter Deflection Maneuver (ODM), which is executed four days after separation or E-17 days. This maneuver of about 26 m/s targets the Orbiter for the planned flyby of Titan at an altitude of 60,000 km and delays the Orbiters closest approach to occur just over two hours after Probe entry. The relative position of the Orbiter with respect to Titan during probe entry and descent provides a view toward the Probe for approximately four and a half hours after entry. The Orbiter HGA will be pointed toward the predicted Probe landing site to capture the Probe telemetry during descent (maximum duration 150 minutes) and for approximately 2 hours after Probe touchdown. The spin-stabilized Probe will be targeted for a southern latitude landing site on the day side of Titan. In order to minimize trajectory dispersion and thus enhance data relay link performance, and to avoid Probe skip-out, the Probe entry angle into the atmosphere will be relatively steep at 64. The term entry generally refers to the arrival of the Probe at the interface altitude of 1270 km, which defines the interface point for Probe targeting requirements. The Probe does not experience significant atmospheric drag until a much lower altitude. The B-plane angle of the Probe aim point -190. This results in landing site at about 10.7 (.7) N and 160(13) E. The large East-West uncertainty in the landing site is driven by uncertainties in the Titan-relative ephemeris and in the magnitude and direction of zonal winds on Titan. No Earth or Sun occultations by Titan (as seen from either the Probe or Orbiter) occur during the probe-relay flyby. 7.4.1 PROBE SEPARATION Successful separation of the Huygens Probe from the Cassini Orbiter is defined as a separation that does not jeopardize the functional or structural integrity of the Probe or Orbiter and gives the Probe the required post-separation trajectory and attitude within allowable uncertainties. In order to accomplish this, the pre-separation state vector (position and velocity) and attitude must be such that, after the dynamics of separation have been applied, the Probe is left with the proper velocity to reach the aim point, and the proper attitude for atmospheric entry. The pre-separation attitude is achieved by rotating the combined spacecraft under AACS control to an attitude which will leave the Probe at the desired post-separation attitude. The Cassini Attitude Determination system provides an estimate of the spacecraft attitude and turning rates with respect to the J2000 coordinate system. The high accuracy Celestial-Inertial mode will be used for attitude determination in the period prior to the separation event. In this mode, the Stellar Reference Unit (SRU) and an on-board star catalog determine the spacecraft attitude in the J2000 reference frame. Attitude estimates are propagated by an Inertial Reference Unit (IRU) between SRU measurement updates. Reaction Control System (RCS) will be used to control the combined spacecraft attitude immediately prior to the separation event. RCS control algorithms maintain the spacecraft attitude and rate about all three spacecraft axes within a limit cycle whose angular size is commandable. The control is achieved using four Z-facing thrusters and another four Y-facing thrusters. It is assumed that, following the turn to the Probe separation orientation, sufficient time is allowed for the spacecraft to attain a quiescent state with rates below 0.01 deg/sec on all axes. However, the firing of the RCS thrusters will be inhibited 10 seconds prior to Probe separation, and the RCS thrusters will be re-enabled 60 seconds following the Probe separation event. 7-14
159 of 217
After the Probe has been positioned to its separation orientation the AACS continually monitors the spacecraft attitude. If the AACS determines that the Probe pointing direction has varied beyond a settable threshold, the Orbiter/Probe separation event will be aborted. Once the separation command is initiated, a sequence of dynamic events occur that result in separation of the Probe. These events include the firing of pyro bolts, engagement of the separation push-off springs, ramps and rollers and the separation of the electrical connectors, as well as motion of the Orbiter under the separation induced loads. All of the activity between the time of the separation command and the time at which the Orbiter and Probe are no longer in physical contact take place in approximately 0.15 seconds. The results obtained for the Probe separation analysis are shown in the table below for the expected propellant loading case. The Probe axial velocity (S/C -X axis direction) of 0.3367 m/s is within the ICD requirement of 0.3 to 0.4 m/s. The Probe lateral velocity, the vector sum of the y and z components, is 0.0039 m/s, well within the ICD requirement of <0.032 m/s. The Probe axial spin rate is 7.29 rpm, satisfying the requirement of >5 rpm. The maximum Orbiter angular rate (the maximum of x, y or z) is 0.974 deg/s (0.1624 rpm), satisfying the requirement of <7 deg/s. Probe/Orbiter Post-Separation Velocity State vx (m/s) vy (m/s) Probe Orbiter -0.3367 0.0471 0.0014 -0.0011 vz (m/s) 0.0036 -0.0006 wx (rpm) 7.2900 -0.1624 wy (rpm) -0.0049 0.1045 wz (rpm) -0.0700 0.018
The dynamics of the Probe and the Orbiter during the five minutes between the time of separation and the time the two bodies are 15 meters apart has been studied. The analysis results indicate that the overall minimum clearance obtained was found to occur between the Langmuir Probe and the Huygens Probe. The minimum clearance of 0.153 m occurred for the low propellant mass scenario. This value of minimum clearance is considered to be satisfactory. To assure that no unmodeled spacecraft motion occurs until the Probe has cleared the vicinity of the Orbiter, the AACS will inhibit the firing of the RCS thrusters until 60 seconds following the Probe separation event. The AACS will switch from the Celestial-Inertial mode to the Coast mode 10 seconds before Probe separation. In the Coast mode the RCS thrusters are inhibited from firing and the spacecraft attitude and rates are continuously sensed by the IRU. Sixty seconds after the separation event the AACS is switched to the detumble mode. In this mode the RCS thrusters are re-enabled and the spacecraft rates are reduced to low, commandable threshold values. When the Orbiter rates are within the prescribed threshold limits, the AACS is switched to the Celestial-Inertial mode and a turn is commenced to return the Orbiter to the attitude it had just prior to the Probe release event. Post-separation imaging of the Probe has been considered to improve the knowledge of its ephemeris and entry conditions at Titan. A preliminary feasibility study has been conducted (Feasibility of Imaging the Huygens Probe from the Cassini Orbiter, Claude Hildebrand, IOM 312.8-96-012, September 9,1996), but important issues remain on the ability to point the WAC and NAC accurately enough, given uncertainties in the Probe and Orbiter velocities after separation. If the pointing is sufficiently accurate, images could be obtained from shortly after separation with the WAC and to up to six days after separation with the NAC. While studies indicate that all Probe mission requirements can be met without post-separation imaging, this option could enhance the Probe relay pointing margins and provide diagnosis of certain Probe separation anomalies.
7-15
160 of 217
FOIA 10-JPL-F-00451
161 of 217
FOIA 10-JPL-F-00451
162 of 217
7.4.2
PROBE RELAY
Figure 7.11 shows a high level timeline for the Probe mission. This timeline is repeated in Section 8, and is under change control to define the basic strategy for the Probe mission sequence. A more detailed, prototype timeline for the day of the Probe mission, Friday January 14, 2005, is shown in Figure 7.12, which compares the timing of the Orbiter events to DSN viewperiods and the prime shifts for the operations centers at JPL and HPOC (European Space Operations Centre, Darmstadt, Germany). The Probe entry event will occur over the Goldstone tracking complex at about 0858 UTC (spacecraft event time, with a 67.7-minute oneway light time). This time is set by Probe trajectory requirements and cannot be adjusted to ground events. Because the Orbiter will be looking at Titan through most of the Goldstone tracking pass, DSN support on this day will be primarily through the 70-meter antennas at the Canberra and Madrid tracking complexes. On approach to Titan, the last downlink before Probe relay will be to the Madrid station (DSS 63). Following the playback of all data remaining on the solid state recorders, the Orbiter is turned nearly 180 degrees to point the HGA at the predicted Probe impact point. The Probe Support Avionics (PSA) are configured to receive data from the Probe. Some Orbiter instruments will be put in a low power state to allow power for the PSA. The data from the Probe are transmitted at S band in two separate data streams, and both are recorded on each SSR. SSR partitions 4, 5, and 6 will be resized as part of the probe-relay critical sequence. Figure 7.9 illustrates the relative sizes of each of these three partitions Following completion of the predicted descent, the Orbiter will continue to listen to the Probe for 30 minutes, in case the Probe transmissions continue after landing. The Orbiter is require to to stay pointed at the predicted Probe landing site for three hours, based on an earlier prediction of the longest descent time being 150 minutes, plus at least 60 minutes after landing. [Current ESA analysis gives an expected descent time of 141 +/- 15 minutes, with the principal uncertainties being the Titan atmospheric density, Titan topography, and uncertainties in the Probe parachute area and drag coefficients, including wind-induced oscillations.] To prevent any interference with reception of the Probe data, no transmissions from the Orbiter are allowed during Probe relay (FR80A4) at any frequency. Transmissions from the Orbiter HGA at X-band will be turned off by the Probe mission sequence shortly after the Orbiter turns away from the Earth to point the HGA at the predicted Probe landing site. Additional protection will be included in the Probe mission sequence and in the configuration of the Orbiter fault protection algorithms to ensure no violation of this flight rule; this protection may include periodic or cyclic commands to ensure that transmissions are kept off at S, X, Ka, and Ku frequencies. When the Probe data collection is complete, that data will be write protected on each SSR. The spacecraft will then turn to view Titan with optical remote sensing instruments, until about one hour after closest approach. A specific science profile has not been defined, but the best combination of remote sensing with fields, particles, and waves and INMS observations will be defined for the first close Titan flyby (Titan-1), within Orbiter operating constraints. Instrument data cannot overwrite the Probe data on the SSRs. Soon after closest approach, the Orbiter will turn the HGA towards Earth and begin transmitting the recorded Probe data. The complete, 4-fold redundant set of Probe data will be transmitted twice, and its receipt verified, before the write protection on that portion of the SSR is lifted by ground command, marking Probe mission completion. The first playback after Titan closest approach will be to the Canberra 70-meter antenna and will include all of the Probe data. The second playback including all of the Probe data and the Orbiter instrument observations will be returned over the subsequent Madrid 70-meter tracking pass, which is longer and at higher tracking elevations. 7-18
163 of 217
FOIA 10-JPL-F-00451
164 of 217
Trajectories referenced to Titan

Goldstone visibility Canberra visibility
Sun
Earth
Huygens
E-4 hr
E-4 hr
Sun-Earth separation = 0.05
E-3 hr
Orbiter
OWLT = 67m 6s
E-2 hr E-3 hr E-1 hr E-2 hr
Orbiter at Probe Entry (E)

E-1 hr
Huygens Probe Entry (h = 1270 km) E+1 hr Orbiter at periapse (h = 60000 km) Orbiter at Probe touchdown
E+2 hr
E+3 hr
Saturn
E+4 hr
Trajectories referenced to Saturn
Goldstone visibility Canberra visibility
Sun
Earth
Huygens
E-3 hr E-4 hr E-3 hr E-1 hr E-2 hr
Sun-Earth separation = 0.05
Orbiter
Titan at E+3 hr
Huygens Probe Entry (h = 1270 km)
E-2 hr E+1 hr E+2 hr
E-1 hr
Orbiter at Probe Entry (E)
Titan at probe entry
E+3 hr E+4 hr
Orbiter at periapse (h = 60000 km) Orbiter at Probe touchdown
Saturn
Figure 7.10 Probe and Orbiter Titan Approach Trajectories 7-20

165 of 217
HGA to Earth
HGA to probe
HGA to Earth
Earth, Sun
Probe at Entry
(interface altitude 1270 km)
Orbiter Probe Support
Turn HGA to Probe (~12 min) Change to PRLY tlm mode, PSAs ON
Turn HGA to Earth
Receive & Record Probe Data
(7.86 hrs req'd for both SSRs)
Probe Data Playback
SSRs write-protected
Orbiter Science
Quiet period* begins TCA-8 days All instrument data cleared from SSRs
All instruments OFF
Science resumes (at most) 2 days after playback

(Probe may request additional playbacks)
Probe Events
Coast Phase
Probe Entry
-2h 6m
Cassini-Titan range: 74689 km
*Quiet period restrictions: Spacecraft turns and rolls (S/C in RCS mode) Power state changes Engineering configuration changes AACS Mode Changes
Probe Link
(~4.5 hr) Orbiter Closest Approach Probe (TCA) Touchdown
Surface Science: S/C will continue to track probe for ~60 minutes (Probe battery life ~ 5 hrs)
Time from TCA

-4.0h
0
Cassini-Titan range @ TCA 60000 km
No quiet period restrictions on: SSR data playback MAPS data collection
Cassini/Huygens Probe Relay Timeline

166 of 217
FOIA 10-JPL-F-00451
167 of 217
A process for data exchanges between NASA/JPL Cassini operations and ESA/HPOC has been defined for all the data required to define Probe and Orbiter targeting and pointing. The operational interface for exchanging data on targeting of the Huygens Probe and pointing of the Orbiter HGA during the data relay will be between the ESA Huygens Probe operations center at ESOC (European Space Operations Center, Darmstadt, Germany) and the Cassini Navigation Team, which is part of the Flight System Operations element (FSO) of Cassini Mission and Science Operations (MSO) at JPL. The principal roles in this interface will be for Cassini Navigation to provide predictions of the Probe and Orbiter arrival conditions to the Titan encounter and for Huygens Probe operations to provide the predicted Probe landing site on Titan, which is the target point for Orbiter HGA pointing during the data relay. To provide for testing of this interface and for execution of the Probe mission, a series of data exchanges are planned according to the schedule shown in Table 7.5, which also shows the planned dates for Probe events for the primary mission. These dates are based on the baseline mission, which plans for the Probe mission occurring at the third Titan encounter, currently planned for January 14, 2005. Data exchanges after the periapsis raise maneuver could be shifted if the Probe mission is delayed to the second encounter. The data exchanges will be made by electronic files stored in the project central data base (CDB). The JPL data package will consist of the information shown in Table 7.6 to define the Probe and Orbiter arrival conditions at Titan and certain parameters used in the navigation analysis. The ESA data package will consist of the information shown in Table 7.7 to define the predicted Probe landing site and the time that the relay link is expected to begin. The ESA data also repeats the requirements on Probe and Orbiter targeting for the encounter as defined in the Cassini/Huygens Interface Requirements Document (PD-699-080, October 14, 1996). Coordinate systems used in the data packages are based on the definitions in the Cassini Physical Constants (PCK) file resident in the DOM. and the Cassini/Huygens Integrated Data Link Report Appendix A. Event times will be expressed in Ephemeris Time (ET).Two passes per day are required from Probe release-3 days to release+1 day, and for Probe entry 1 day. Table 7.5 Delivery Schedule for Probe Relay Planning Data
Event SOI - 1.5 years Saturn Orbit Insertion (SOI) SOI + 60 days Periapsis Raise Maneuver (OTM 002) OTM003 OTM004 Titan A OTM005 OTM006 OTM007 Titan B OTM008 OTM009 Set Probe Timer Probe Separation Orbiter Deflection Maneuver (OTM010) Entry - 15 days Entry - 12 days Last Orbiter OD Data for Probe Relay Last Uplink to Orbiter for Probe Relay Probe Entry/Relay Date 1 January 2003 1 July 2004 30 August 2004 23 August 2004 7 September 2004 23 October 2004 26 October 2004 29 October 2004 21 November 2004 9 December 2004 13 December 2004 17 December 2004 20 December 2004 21 December 2004 24 December2004 28 December 2004 31 December 2004 2 January 2005 Days from Entry -744 -197 -137 -144 -129 -83 -80 -77 -54 -36 -32 -28 -25 -24 -21 -17 -15 -12 -5 -3 0 JPL Data Package J J ESA Data Package D D
J D
14 January 2005
7-23
168 of 217
Table 7.6 JPL Data Package

The JPL data package is periodically produced by the Cassini Navigation Team and stored on the CDB. The Huygens Probe Operations Center is notified of the availability of the data package and retrieves the data from the CDB. Event times will be given in Ephemeris Time (ET). The contents of the JPL data package are: 1. Predicted Probe state, covariance, and time, t(interface), at the interface altitude (1270 km ). a. Coordinates and covariance in the Q frame 1. B-Plane 2. Cartesian 2. Predicted Orbiter Cartesian state and covariance at the predicted interface time, t(interface). a. Cartesian Coordinates and Covariance in the Q frame 3. Predicted Orbiter state, covariance, and time at Titan periapsis. a. Coordinates and covariance in the Q frame 1. B-Plane 2. Cartesian 4. Saturn mass (GM) used for the computation. a. Mean and 1 sigma uncertainty 5. Titan to Saturn vector at t(interface). a. Cartesian in the Q frame 6. Titan to Sun vector at t(interface). a. Cartesian in the Q frame 7. Direction of the predicted Probe Angular Momentum Vector. EME 2000 Coordinates Titan radius used in the computation. 8. 9. Titan mass (GM) used for the computation. a. Mean and 1 sigma uncertainty 10. Titan Pole Vector at 0:00 hours (ET) on the day of probe entry (currently November 27, 2004). EME 2000 Coordinates 11. Titan Prime Meridian Angle from the Q axis at 0:00 hours (ET) on the day of probe entry. 12. Titan Rotation Rate.
Table 7.7 ESA Data Package The ESA data package is periodically produced by Huygens Operations and stored on the CDB. The JPL Navigation Team is notified of the availability of the data package and retrieves the data from the CDB. Event times will be given in Ephemeris Time (ET). The contents of the Huygens data package are: 1. Probe Targeting Parameters in the Q frame. B-plane (B magnitude and angle from T axis) 2. Range of Allowable Orbiter Delay Time. 3. Range of the Magnitude of the probe asymptotic velocity at the interface altitude. 4. Orbiter Pointing Location during relay. a. Titan fixed latitude, longitude, radius 5. Start time of relay link (ET). Note: Items 1,2, and 3 are under change control in the Cassini/ Huygens Interface Requirements Document (PD-699-080), but will be repeated here for completeness. 7.5 OPTICAL REMOTE SENSING ENCOUNTERS Titan becomes a target of remote sensing instruments when Titan fills about 1/3 of the Narrow Angle Camera (NAC) Field of View (FOV). This occurs at a range of 2.5 million km. Remote sensing will usually alternate between viewing Saturn and Titan until Titan fills the NAC FOV. This will occur at about 850,000 km from Titan. On Titan flybys approaching Saturn, Titan will dominate the viewing during the approach and Saturn will become the main target of interest sometime after Titan, as the orbit periapsis is neared. Within ~16 hours of closest approach to Titan, Titan is exclusively the target of the ORS instruments. Optical remote sensing is desirable during Titan flybys which are dedicated to RADAR and Radio Science, before those instruments are turned on. Optical remote sensing investigations 7-24
169 of 217
will also require Titan flybys dedicated entirely to instruments which normally operate in the ORS mode. Only during dedicated optical remote sensing passes will the optical remote sensing instruments view Titan at closest approach. Dedicated optical remote sensing flybys will occur over a wide range of altitudes and on both the illuminated and dark side of the satellite. There is a general preference for more passes on the illuminated side to allow more opportunities to achieve science objectives which require an illuminated target. UVIS will observe solar occultations. Titan observation design is done by the Titan Orbiter Science Team (TOST). Icy satellite flyby observations is done by the Satellite Orbiter Science Team (SOST). Specific timelines can be obtained from those teams. 7.6 RADAR ENCOUNTERS RADAR flybys are generally tour flybys with the minimum altitude at Titan. These flybys are desirable for RADAR since the low altitudes offer the highest resolution, and generally undesirable to ORS since the altitudes are far too low for the reaction wheels to be used. High resolution RADAR imaging can occur when the altitude above Titan is less than about 1600 km. Figure 7.13 illustrates the geometry of a typical RADAR pass. During a complete RADAR pass, RADAR, the Ion and Neutral Mass Spectrometer (INMS), and the Cassini MAPS instruments will be operating. However, on most passes, RADAR will share time with other instruments and will often begin at closest approach or get only inbound or outbound portions of a Titan flyby. In order to set up for a complete RADAR pass, the spacecraft will have to make turns of up to 180 to go from pointing the HGA at Earth to pointing the RADAR at Titan. RADAR will also perform radiometry for one Saturn disk observation, a set of Saturn ring observations, and long range observations of the icy satellite observations. The RADAR system currently has 6 modes of operation: The two passive modes are warm-up and stand-alone radiometry. Cold-sky calibration periods which immediately precede- and follow the radiometry-only periods will use the stand-alone radiometry mode. The four active instrument modes are scatterometry, altimetry, low resolution imaging, and high resolution imaging. Radiometry data will automatically be obtained in an interleaved fashion during each of the four active modes. In general, radiometry warm-up time requires 3 hours, scatterometry requires 2 hours, and SAR or altimetry require 20 minutes warm-up. Since no pointing requirements are necessary, RADAR warm-up periods may be done simultaneously, in conjunction with other prime instruments activities. If an altimetry mode precedes the imaging mode, the imaging warm up time is included in the altimetry mode operating time. Every complete RADAR pass contains up to 10 hours of radiometry assuming radiometry data acquisition starts at 100,000 km. The radiometry mode uses the 0.35 degree, central beam 3, only. Radiometry observations at distances between 25,000- and 100,000 km should provide good opportunities for obtaining global coverage of Titan depending on the number of RADAR passes, the method for scanning the disk of Titan, and the geometry of the passes assigned to RADAR. RADAR personnel have identified as an open issue the possibility of performing radiometry during portions of optical remote sensing or radio science passes. This issue will be discussed by the PSG and will be evaluated in light of the increased operational complexity. The resolution of the radiometry is a function of the range to the surface. At 100,000 km, resolution is 611 km and at 10,000 km, resolution is 61 km. It is desired to obtain 10% coverage of Titan on a single pass at a resolution of 150 km or better. If adequate radiometry coverage cannot be achieved during the assigned RADAR passes, then there will be a strong desire to perform radiometry on non-RADAR passes as well. During the scatterometry mode, the RADAR will perform scans of the surface of Titan. RADAR does not expect to acquire 100% coverage of Titan during the scatterometry/ 7-25
170 of 217
radiometry period when distances are 25,000 km or less. The portion of Titans disk that can be mapped during this period is a function of the spacecrafts rotation rates and the spacecraft distance. At flyby altitudes greater than or equal to 1400 km, RADAR scans and spacecraft turns will be done using the Reaction Wheel Assemblies (RWAs). At altitudes less than 1400 km RADAR passes require turn rates of up to 0.4/s and therefore require the Reaction Control (thruster) System for attitude control. The transition between RWAs and RCS, and vice versa, will require a minimum of 20 minutes during which time no spacecraft maneuvers or RADAR scans can be done.
RADAR mode operation timeline during a nominal Titan flyby:
Radar Mode
SAR High-Res SAR Low-Res ALTIMETER SCATTEROMETER Calibration Rotation - 1
Time Relative To Closest Approach (min)

-6 to +6 -16 to -6 & +6 to +16 -30 to -16 & +16 to +30 -70 to -30 & +30 to +70 -300 to 290 & -78 to -70 +70 to +78 & +290 to +300
Min/Max Altitude (km)

1000 / 1600 1600 / 4000 4000 / 9000 9000 / 22,500 22,500 / 25,000
Radiometer Only - 2
-290 to -78 & +78 to +290
25,000 / 100,000
Notes: Calibration Rotation mode is actually the same as used for Radiometer Only. Radiometer data are acquired during all other active modes.
300 min Titan Disc Scan Radiometry Only 78 min Calibration (S/C rotate) 70 min Titan Disc Scan L-R Altimetry (Scatterometry), Radiometry 22500 km 30 min Nadir Pointing H-R Altimetry, Radiometry 9000 km 16 min 6 0 min min Side Looking Imaging, Radiometry
LO HI
REVERSE SEQUENCE
100000 km
25000 km
4000 km
1600 km 1000 km
TITAN
Figure 7.13 Cassini RADAR Operating Profile

Notes: 1 Spacecraft altitude at the closest approach is ~1000 km. 2. Another calibratin period should be shown preceding the Radiometry Only period. Both Calibration periods will be incorporated into the total time alloted for the Radiometry Only period, and the instrument mode will be the same.
During the high resolution altimetry mode, RADAR will be nadir-pointed, which requires target motion compensation as the spacecraft approaches/recedes from the planet. As an example, at the start of the imaging modes, SAR 1 and SAR 2, RADAR will turn off nadir. If the X axis is aligned with the direction of motion, the Ku antenna feeds can be aligned so the RADAR beam is oriented perpendicular to the direction of motion at closest approach.
7-26
171 of 217
Figure 7.14 Off Nadir Look Angle

Y-Axis
Titan
Off Nadir Ground Track Z-Axis Off Nadir Angle X -Axis out of page
Nadir Po inted
Nadir Ground Track
The RADAR will move slowly to other off nadir angles by the time of closest approach and then back to the initial angle by the end of the imaging modes. The exact algorithm for the off nadir angles is still being developed and will likely be a progression of incidence angles with time. The RADAR turns are performed to maintain a desired profile of incidence angle at the surface of Titan. All RADAR modes are repeated in reverse order as the spacecraft recedes from Titan. During the spotlight mode, the RADAR can illuminate a particular spot on the surface of Titan throughout the pass. This mode would be active during the time for imaging if previous passes have identified an area of particular interest (e.g. an ocean with waves). The spacecraft can perform turns at rates up to 0.4/s about the Y-axis to spotlight a feature. This mode is available but not currently planned for use during the baseline mission. During the RADAR pass, other instruments may also be operating, particularly MAPS and INMS. However data volume issues often preclude sharing passes with other instruments. INMS has two instrument modes, closed source and open source, to detect the widest range of ion species. The closed source has a half cone aperture of 90 and begins operation at a range of 5000 km from Titan, about 18.5 minutes before TCA. The open source has an half cone aperture of 8 to be aligned along the ram direction. Since INMS is mounted at 90 to the RADAR direction (facing -Y direction), the open source boresight is within 8 of the ram direction only when the spacecraft is near closest approach to Titan. The closed source will operate for about 140 seconds, centered about TCA. However, in general even INMS has a specific pointing profile that it desires that is inconsistent with RADAR profiles. Therefore, INMS and RADAR are often given control over different parts of the pass. Table 7.5: RADAR Operating Times and Data Rates for 950km Titan Flyby
Titan Flyby RADAR Operating Mode Stand-alone Radiometry Scatterometry and Radiometry High Resolution Altimetry and Radiometry Low Resolution Imaging and Radiometry High Resolution Imaging and Radiometry INMS, Close Source INMS, Open Source Data Rate (kbps) Times per Pass (minutes) 5* 0-480 30 80-90 30 30 191* 20 365 12-15 1.5 37 1.5 2.3
Note that the CDS pickup rate for RADAR remains at 365 kbps for all RADAR measurements.
7-27
172 of 217
7.7
RADIO SCIENCE ENCOUNTERS
There are two types of radio science observations during Tour: Earth occultations, and gravity field determinations. All three experiments require a 90-120 minute warm-up period for the RFIS bay to reach thermal stabilization. There are three separate occultation events that Radio Science will observe: Earth occultations by Saturn, by Titan, and by the rings. Each event requires the spacecraft to fly a trajectory behind the body of interest (as viewed from the Earth). The occultation experiment will determine characteristics of the Saturn or Titan atmosphere or of the rings by transmitting Sband, X-band, and potentially Ka-band signals through the atmosphere (or rings) toward the Earth. The Doppler-shifted frequencies will be received and analyzed to determine how much refraction and attenuation occurred during the passage through the atmosphere or the rings. Radio science prefers that limb-tracking maneuvers be performed using reaction wheels for the highest spacecraft stability when possible. For very fast Titan occultations, the thrusters must be used. 7.15 illustrates a typical radio science occultation flyby of Titan.
View from North Trajectory Pole
Earth
Sun
Saturn
2316 km Altitude Time tics each 6 minutes
Figure 7.15 Radio Science Occultation Occultation passes are not necessarily centered about Saturn or Titan CA. They may start after or end before CA. Occultation passes require a 5-20 minute baseline period where the oneway signal(s) travel through free-space (i.e., no atmosphere or ring particles) just before the occultation begins or right after the occultation ends. Flybys for gravity field determination are best served by flybys closer than 5000 km from the center of satellite of interest (usually Titan). They may occur on either the Earth side of the satellite or the occultation side as long as no Earth occultation zone is entered. For Titan, it is intended for the gravity field to be determined to degree and order 4. During gravity field passes, X and Ka signals will be transmitted toward Earth for a period of 2 hours on either side of CA (although this may vary as a result of negotiations with other Teams). Tracking coverage will be continuous throughout the pass. The gravity field passes will use the momentum wheels throughout the pass so there is no transition period requiring catalyst bed heaters. Also, Radio science prefers that gravity field data be taken from 2 hours before to 2 hours after any Earth occultation period. 7-28
173 of 217
SECTION 8: OPERATIONAL MODES, GUIDELINES AND CONSTRAINTS, AND CONTROLLED SCENARIO TIMELINES THIS SECTION IS UNDER PROGRAM CHANGE CONTROL. This section defines certain elements of the mission and system design for Cassini that are placed under project change control, because they are considered fundamental to the operational strategy for the mission and for constraining operational complexity. These elements include definitions of the operational modes, modules and templates, unique and fixed sequences, transitions, operational guidelines and constraints, and scenario timelines for certain key periods of the mission. 8.1 8.1.1 MISSION PLANNING FRAMEWORK OPERATIONAL MODE DEFINITION
An operational mode is a resource (power) envelope applied to the spacecraft subsystems and science instruments. The intent of defining operational modes is to maximize the collection of science within a mode (by balancing science and spacecraft power requirements), minimize operational complexity in sequence generation, and allow some flexibility for science instrument states to vary (within the limits of their resource envelopes). The operational mode also uniquely defines the beginning and ending spacecraft state(s) used to transition in and out of the mode. A fixed transition sequence will be defined for each allowed transition between operational modes. The current set of operational modes for the Cassini mission is listed in Table 8.1. Power analysis is one of the mission design primary considerations in verifying the functionality of the operational modes, and this work can be found in the current version of the Cassini Power Report (699-010). Some of the modes listed will only have sufficient power for a portion of the mission (e.g., to SOI+2 years). These modes will cease to be available if and when the power margin drops below the required operating margin. Calibration activities for all instruments, except MAG, are included within their normal operating modes. The MAG calibrations require additional power and separate fixed and/or unique sequences. 8.1.2 SEQUENCE CONSTRUCTS DEFINITION A module is a reusable sequence of commands whose relative timing and total duration may be variable. A module cannot extend across operational mode boundaries but may be used in more than one operational mode, provided its activities do not violate that operational mode. A module should define a pointing pattern but can be target and telemetry mode independent (provided its activities do not violate the active telemetry mode). A template is a science planning concept (not a sequence construct like a module) which allows convenient reuse of a sequential series of modules, fixed sequences, gaps, or other templates. Templates are used as a conceptual tool to assemble sets of activities that will typically be used in concert and may cross operational mode boundaries. A unique sequence is a sequence that has a specific purpose, is used once, and does not use modules. (If it did, it would not be a unique sequence, it would be a regular sequence.) Unique sequences can and should take advantage of operational modes in their design if possible, but violation of operational mode constraints is permitted. A fixed sequence is a fixed-duration sequence that is designed and validated once for multiple uses, and does not use operational modes, and admits a fixed list of parameters. Both unique and fixed sequence have no defined global constraints and can include any combination of states. Unique or fixed sequences are checked for constraint violations and must contain required state changes needed to transition into and out of specific predefined operational modes. Should the operational modes preceding and/or following the unique or 8-1
174 of 217
fixed sequence be different, appropriate transition sequences should be added before or after the sequence to ensure that no sequence redesign is required. Each unique or fixed sequence is checked for constraint violations and must contain required state changes needed to transition into and out of a specific predefined operational mode. Table 8.1 Cassini Operational Modes Mode Usage Type Optical Remote Sensing (ORS) Science Remote sensing pointing and FPW data acquisition Reaction Wheel Assembly Full (includes SCAS power) (RWAF) ORS Reaction Control Science Remote sensing pointing and FPW data acquisition during Subsystem (RCS) rare occasions when thruster control and speed are required (includes SCAS) Downlink/Fields, Particles, and Science FPW data return with or without S/C rotation during Waves (DFPW)-normal downlink DFPW-TCM Science FPW data return with or without S/C rotation when a TCM (ME or RCS) is to be done RADAR (RCS) Science RADAR and FPW data acquisition using thrusters RADAR (RWA) Science RADAR and FPW data acquisition with RWAF RADAR warmup/rad Science Same as ORS-RWAF, except RADAR warm-up and Radiometer are substituted for SCAS RSS warm-up Science Same as ORS-RWAF, but excludes SCAS, includes RSS warmup and limited RWA RSS3/RCS X+(S & Ka) Science Radio science, Titan atmospheric and Saturn atmospheric (Thruster control) and ring occultation measurements, includes ORS and FPW science (thruster control) RSS2/RWAF X+(S ) Science Radio science, Titan atmospheric and Saturn atmospheric (Wheel control) and ring occultations (no Ka-band, RWAF control) RSS3/RWAL X+(S+Ka) Science Same as RSS3/RCS, except no ORS and with RWAL (Wheel control) instead of thruster control RSS3 /RWAF X+(S+Ka) Science Same as RSS3/RWAL, except RWAF and w/o CDA art Fixed Sequences RWA Unload Engr. Same as ORS-RWAF, but excludes SCAS and includes RWA unload capability (fixed sequence not an Operational Mode) TCM (RCS) Engr. Thruster TCM burn (fixed sequence, not OpMode) TCM (Main Engine) Engr. Ignition transient and steady state main engine TCM burn (fixed sequence, not OpMode) Downlink FP-PEM Engr. Periodic engineering manitenance (spacecraft must stop spin during RWA exercise portion of sequence) Operational Mode A transition sequence is a fixed sequence that is used to shift between operational modes. A transition sequence is needed when the end state of a operational mode is not the same as the beginning state of the next mode. Operational modes instrument composition is shown in Table 8.2. Transition sequences are shown in Table 8.5. 8.1.3 REQUIREMENTS ON THE DESIGN OF OPERATIONAL MODES a) Each operational mode shallspecify a maximum power allocation for each instrument and each engineering function specified in the Operational Mode Tables. [Note: Telemetry modes included in Table 8.3 and 8.4 are merely suggestive, for guidance of the user]. The power and thermal envelopes shall be defined so that operations within those envelopes can be conducted safely without requiring power or thermal analysis by the ground. The 8-2
175 of 217
maximum power allocations for each science instrument and spacecraft subsystem are shown in Table 8.2. The maximum value is the peak power. b) Operational modes shall be designed so as to allow sequencing of system-level activities in the mode through the use of standard sequence components. c) Each operational mode shall have a defined spacecraft state for mode start and mode end. Each of the allowed transitions between end and start states of the different operational modes shall be via transition sequences using standard sequence components. d) Operational modes shall be designed so as to allow sequencing of system-level activities necessary to transition between modes. 8.1.4 REQUIREMENTS ON THE DESIGN OF MODULES The following rules for module construction and usage shall be followed: a) All modules shall be reusable without validation. As a consequence, the use of module parameters within a module expansion shall be limited to changing either command parameters or the number (greater than or equal to one) of repetitions of actions within the module. b) The module shall include target-relative pointing (but need not be target-specific), telemetry mode, and trigger commands which need to be time synchronized over the execution period of the module. c) Modules shall allow for instrument trigger commands (that are permitted within the operational mode) that are independent of spacecraft pointing, independent of the allowed telemetry mode choices, and that do not need to be synchronized with any other module actions to be executed in parallel with the module. d) Modules shall not cross operational mode boundaries. Modules need not assume a specific operational mode, provided their execution will not violate the conditions of the operational mode(s) in which they may be placed. e) Each command contained in a module shall execute at a time relative to a base time. These execution times may be parameters of the module. f) Module design shall not assume any telemetry mode is in effect at the beginning of the module. g) Only one module shall execute at a time and a module shall not initiate another module. h) The Prime Instrument shall define the pointing profile, telemetry mode changes, and module base time for each execution of a module.
Rationale: Defines what is meant by a module and what the constraints are. For a module to save costs, it must be trusted without validation. To make such a validation realizable, the use of parameters is limited to either changing the parameters of commands in the module expansion (e.g. timing), or changing the loop counts of repeated actions (e.g. scans or images or dimensions of a mosaic). This allows validation at the "edge of the envelope" of the possible module expansions. What is not permitted is a module with parameters that turn off some operations and turn on others, since then the amount of validation needed can grow exponentially to adequately cover all possible expansions. When that is needed, separate modules need to be written for different operations.
Modules must allow instrument operations that do not depend on the spacecraft orientation, or on which allowed data mode in that operational mode is active, to be placed anywhere in the time the module occupies. Modules are distinct from transition sequences used to change operational modes, and distinct from each other. While the module cannot cross operational mode boundaries, it must set one of the allowed data modes for that operational mode at the start, to avoid having to interface between modules. 8-3
176 of 217
Table 8.2 Operational Mode Composition

ORS (RWA) Margin Power Violations ORS CIRS ISS UVIS VIMS MAPS CAPS CDA INMS MAG MIMI RPWS SCAS RF RADAR RSS Instruments AACS Base AFC SRU SRU Supp Htr SRU Repl Htr Sun Sensor IRU RWA RCS VDECU MPD Thrusters Catbed Htrs Main Engine Accelerometer REA heaters REA valve REA OX htr EGA AACS PMS Press. Xdcrs Temp Control RSP R/Htr ATCs RFS X-TWTA DST TCU USO CDS CDS CDS EU PMS REU RSP REU REU delta SSR PPS Pwr Control Pwr Distrib. PPS REU SSPS Losses Cable Losses Rad. & Age Thermal Flux FP Margin Engineering (2) 21.6 7.4 0.9 1.8 1.9 26.0 90.4 2.1 1.7 0.0 18.4 0.0 0.0 0.0 4.4 0.0 176.6 5.8 0.0 12.0 10.7 9.8 6.0 2.7 26.4 6.2 6.2 6.2 7.5 16.4 7.4 12.4 6.6 2.5 26.0 2.0 6.0 20.0 375.4 (2) 21.6 7.4 0.9 1.8 1.9 26.0 0.0 2.1 1.7 17.0 9.2 0.0 0.0 0.0 4.4 0.0 94.0 5.8 0.0 12.0 10.7 9.8 6.0 2.7 26.4 6.2 6.2 6.2 7.5 16.4 7.4 12.4 6.6 2.5 26.0 2.0 0.0 20.0 286.8 (2) 21.6 7.4 0.9 1.8 1.9 26.0 90.4 2.1 1.7 0.0 18.4 0.0 0.0 0.0 4.4 0.0 176.6 5.8 0.0 12.0 51.6 9.8 6.0 2.7 26.4 6.2 6.2 6.2 7.5 16.4 7.4 12.4 6.6 2.5 26.0 2.0 6.0 20.0 416.3 (2) 21.6 7.4 0.9 1.8 1.9 26.0 90.4 2.1 1.7 0.0 18.4 0.0 34.0 0.0 4.4 0.0 210.6 5.8 21.2 12.0 51.6 9.8 6.0 2.7 26.4 6.2 6.2 6.2 7.5 16.4 7.4 12.4 6.6 2.5 26.0 2.0 6.0 20.0 471.5 (2) 21.6 7.4 0.9 1.8 1.9 26.0 90.4 2.1 1.7 8.7 13.8 0.0 0.0 0.0 4.4 0.0 180.7 5.8 0.0 12.0 51.6 9.8 6.0 2.7 26.4 6.2 6.2 6.2 7.5 16.4 7.4 12.4 6.6 2.5 26.0 2.0 6.0 20.0 420.4 (2) 21.6 7.4 0.9 1.8 1.9 26.0 90.4 2.1 1.7 0.0 18.4 0.0 0.0 0.0 4.4 0.0 176.6 5.8 0.0 12.0 10.7 9.8 6.0 2.7 26.4 6.2 6.2 6.2 7.5 16.4 7.4 12.4 6.6 2.5 26.0 2.0 6.0 20.0 375.4 669.0 ORS (RCS) 580.4 Downlink FP-normal 685.9 Downlink FP-TCM 680.6 RWA Unload 676.7 >EOM by 2.1 on on on on on on on on on on on off kat Total 46.0 45.6 13.0 27.3 21.0 25.0 26.6 13.4 25.9 16.9 24.0 0.0 8.9 293.6 on on on on on on on on on on on off kat Total 46.0 45.6 13.0 27.3 21.0 25.0 26.6 13.4 25.9 16.9 24.0 0.0 8.9 293.6 on on on on on on on on on on off off kat Total 46.0 45.6 13.0 27.3 21.0 25.0 26.6 13.4 25.9 16.9 0.0 0.0 8.9 269.6 sleep sleep on sleep on noart on on on on off off off Total 29.0 38.7 13.0 12.9 21.0 11.7 26.6 13.4 25.9 16.9 0.0 0.0 0.0 209.1 on on on on on noart on on on on off off kat Total 46.0 45.6 13.0 27.3 21.0 11.7 26.6 13.4 25.9 16.9 0.0 0.0 8.9 256.3 on on on on on on on on on on off wuRad off Total 46.0 45.6 13.0 27.3 21.0 25.0 26.6 13.4 25.9 16.9 0.0 53.0 0.0 313.7 RADAR wu/Rad 689.1
full on on off 8 off off off (2) off Subtotal (18) ORS on
off on on 4 4 off off off (2) off Subtotal (18) ORS on
full on on off 8 off on off (2) off Subtotal (18) ORS sleep
full on on 2 6 off off off (2) off Subtotal (18) ORS on
sleep
sleep
on
on
on
sleep
(2) (2) (2) (2) (2)
(2) (2) (2) (2) (2)
(2) (2) (2) (2) (2)
(2) (2) (2) (2) (2)
(2) (2) (2) (2) (2)
(2) (2) (2) (2) (2)
(2)
(2)
(2)
(2)
(2)
(2)
RWA on Total
RWA off Total
RWA on Total
RWA on Total
RWA on Total
RWA on Total
RTG@SOI margin
RTG@SOI+3 margin
729.0 60.0
699.0 30.0
729.0 148.6
699.0 118.6
729.0 43.1
699.0 13.1
729.0 48.4
699.0 18.4
729.0 52.3
699.0 22.3
729.0 39.9
699.0 9.9
RTG@EOM margin
687.0 18 0
687.0 106 6
687.0 11
687.0 64
687.0 10 3
687.0 -2 1
8-4
177 of 217
RADAR (RWA) Margin Power Violations ORS CIRS ISS UVIS VIMS MAPS CAPS CDA INMS MAG MIMI RPWS SCAS RF RADAR RSS Instruments AACS Base AFC SRU SRU Supp Htr SRU Repl Htr Sun Sensor IRU RWA RCS VDECU MPD Thrusters Catbed Htrs Main Engine Accelerometer REA heaters REA valve REA OX htr EGA AACS PMS Press. Xdcrs Temp Control RSP R/Htr ATCs RFS X-TWTA DST TCU USO CDS CDS CDS EU PMS REU RSP REU REU delta SSR PPS Pwr Control Pwr Distrib. PPS REU SSPS Losses Cable Losses Rad. & Age Thermal Flux FP Margin Engineering (2) 21.6 7.4 0.9 1.8 1.9 26.0 90.4 2.1 1.7 0.0 18.4 0.0 0.0 0.0 4.4 0.0 176.6 5.8 21.2 12.0 10.7 9.8 6.0 2.7 26.4 6.2 6.2 6.2 7.5 16.4 7.4 12.4 6.6 2.5 26.0 2.0 6.0 20.0 396.6 (2) 21.6 7.4 0.9 1.8 1.9 26.0 0.0 2.1 1.7 17.0 9.2 0.0 0.0 0.0 4.4 0.0 94.0 5.8 0.0 12.0 10.7 9.8 6.0 2.7 26.4 6.2 6.2 6.2 7.5 16.4 7.4 12.4 6.6 2.5 26.0 2.0 0.0 20.0 286.8 (2) 21.6 7.4 0.9 1.8 1.9 26.0 60.4 0.0 0.0 0.0 0.0 0.0 0.0 0.0 4.4 0.0 124.4 5.8 0.0 12.0 51.6 9.8 6.0 2.7 26.4 6.2 6.2 6.2 7.5 16.4 7.4 12.4 6.6 2.5 26.0 2.0 6.0 20.0 364.1 (2) 21.6 7.4 0.9 1.8 1.9 26.0 0.0 2.1 1.7 17.0 9.2 0.0 0.0 0.0 4.4 0.0 94.0 5.8 0.0 12.0 51.6 9.8 6.0 2.7 26.4 6.2 6.2 6.2 7.5 16.4 7.4 12.4 6.6 2.5 26.0 2.0 0.0 20.0 327.7 (2) 21.6 7.4 0.9 1.8 1.9 26.0 90.4 0.0 0.0 0.0 0.0 0.0 0.0 0.0 4.4 0.0 154.4 5.8 21.2 12.0 51.6 9.8 6.0 2.7 26.4 6.2 6.2 6.2 7.5 16.4 7.4 12.4 6.6 2.5 26.0 2.0 6.0 20.0 415.3 (2) 684.6 RADAR (RCS) 632.8 >EOM by 7.5 sleep sleep sleep sleep on noart on on on on off on off Total 29.0 38.7 6.6 12.9 21.0 11.7 26.6 13.4 25.9 16.9 0.0 85.3 0.0 288.0 on on on on on on on on on on off on off Total 46.0 45.6 13.0 27.3 21.0 25.0 26.6 13.4 25.9 16.9 0.0 85.3 0.0 346.0 on on on on on noart on on on on off off warmup Total 46.0 45.6 13.0 27.3 21.0 11.7 26.6 13.4 25.9 16.9 0.0 0.0 83.0 330.4 on on on on on on on on on on off off s/ka Total 46.0 45.6 13.0 27.3 21.0 25.0 26.6 13.4 25.9 16.9 0.0 0.0 83.0 343.7 sleep sleep sleep sleep on on on on on on off off s-only Total 29.0 38.7 6.6 12.9 21.0 25.0 26.6 13.4 25.9 16.9 0.0 0.0 48.8 264.8 sleep sleep sleep sleep on on on on on on off off s/ka Total RSS wu (RWAL) 694.5 RSS3 (RCS) 671.4 RSS2 (RWA) 680.1 RSS3 (RWAL)
full on on off 8 off off off (2) off Subtotal (18) ORS sleep
limited off off off off off off off (2) off Subtotal (18) ORS on
full off off off off off off off (2) off Subtotal (18) ORS sleep
limited off off off off off off off (2) off Subtotal (18) ORS sleep
sleep
sleep
on
on
on
on
(2) (2) (2) (2) (2)
(2) (2) (2) (2) (2)
(2) (2) (2) (2) (2)
(2) (2) (2) (2) (2)
(2) (2) (2) (2) (2)
(2) (2) (2) (2) (2)
(2)
(2)
(2)
(2)
(2)
(2)
RWA on Total
RWA off Total
RWA on Total
RWA off Total
RWA on Total
RWA on Total
RTG@SOI margin RTG@SOI+3 margin
729.0 44.4
699.0 14.4
729.0 96.2
699.0 66.2
729.0 34.5
699.0 4.5
729.0 57.6
699.0 27.6
729.0 48.9
699.0 18.9
RTG@EOM margin
687.0 2.4
687.0 54.2
687.0 -7.5
687.0 15.6
687.0 6.9
8-5
178 of 217
RSS3 (RWAF) Margin Power Violations ORS CIRS ISS UVIS VIMS MAPS CAPS CDA INMS MAG MIMI RPWS SCAS RF RADAR RSS Instruments AACS Base AFC SRU SRU Supp Htr SRU Repl Htr Sun Sensor IRU RWA RCS VDECU MPD Thrusters Catbed Htrs Main Engine Accelerometer REA heaters REA valve REA OX htr EGA AACS PMS Press. Xdcrs Temp Control RSP R/Htr ATCs RFS X-TWTA DST TCU USO CDS CDS CDS EU PMS REU RSP REU REU delta SSR PPS Pwr Control Pwr Distrib. PPS REU SSPS Losses Cable Losses Rad. & Age Thermal Flux FP Margin Engineering (2) 21.6 7.4 0.9 1.8 1.9 26.0 90.4 0.0 0.0 0.0 0.0 0.0 0.0 0.0 4.4 0.0 154.4 5.8 21.2 12.0 51.6 9.8 6.0 2.7 26.4 6.2 6.2 6.2 7.5 16.4 7.4 12.4 6.6 2.5 26.0 2.0 6.0 20.0 415.3 701.0 >SOI+3 by 2 sleep sleep sleep sleep on noart on on on on off off s/ka Total 29.0 38.7 6.6 12.9 21.0 11.7 26.6 13.4 25.9 16.9 0.0 0.0 83.0 285.7
TCM RCS 681.1
TCM ME 668.4
Downlink FP-PEM 684.5
sleep sleep on sleep on on on on on on off off kat Total
29.0 38.7 13.0 12.9 21.0 25.0 26.6 13.4 25.9 16.9 0.0 0.0 8.9 231.3
sleep sleep on sleep on noart sleep on on on off off off Total
29.0 38.7 13.0 12.9 21.0 11.7 16.6 13.4 25.9 16.9 0.0 0.0 0.0 199.1
sleep sleep sleep sleep on on on on on on off off off Total
29.0 38.7 6.6 12.9 21.0 25.0 26.6 13.4 25.9 16.9 0.0 0.0 0.0 216.0
(2)
full off off off off off off off (2) off Subtotal (18) ORS sleep
full on on 6 2 off off off (2) off Subtotal (18) ORS sleep
21.6 7.4 0.9 1.8 1.9 26.0 90.4 2.1 1.7 26.1 4.6 0.0 0.0 0.0 4.4 0.0 188.9 5.8 21.2 12.0 51.6 9.8 6.0 2.7 26.4 6.2 6.2 6.2 7.5 16.4 7.4 12.4 6.6 2.5 26.0 2.0 6.0 20.0 449.8
(2)
off on on 2 6 on off trans (2) on Subtotal (18) ORS sleep
21.6 7.4 0.9 1.8 1.9 26.0 0.0 2.1 1.7 8.7 13.8 3.1 0.0 90.0 4.4 31.0 214.4 5.8 21.2 12.0 51.6 9.8 6.0 2.7 26.4 6.2 6.2 6.2 7.5 16.4 7.4 12.4 6.6 2.5 26.0 2.0 0.0 20.0 469.3
(2)
full on on off 8 off off off (2) on Subtotal (18) ORS sleep
21.6 7.4 0.9 1.8 1.9 26.0 90.4 2.1 1.7 0.0 18.4 0.0 0.0 0.0 4.4 31.0 207.6 5.8 21.2 12.0 51.6 9.8 6.0 2.7 26.4 6.2 6.2 6.2 7.5 16.4 7.4 12.4 6.6 2.5 26.0 2.0 6.0 20.0 468.5
on
on
on
on
(2) (2) (2) (2) (2)
(2) (2) (2) (2) (2)
(2) (2) (2) (2) (2)
(2) (2) (2) (2) (2)
(2)
(2)
(2)
(2)
RWA on Total
RWA on Total
RWA off Total
RWA on Total
RTG@SOI margin RTG@SOI+3 margin RTG@EOM margin
729.0 28.0 699.0 -2.0 687.0 -14.0
729.0 47.9 699.0 17.9 687.0 5.9
729.0 60.6 699.0 30.6 687.0 18.6
729.0 44.5 699.0 14.5 687.0 2.5
8-6
179 of 217
Table 8.3 Cassini Peak Data Rate Guidelines by Operational Mode
Preferred Op Mode vs. Telemetry Mode Usage

S&ER-1 OP MODE ORS TYPES DL FPW or RWA Unload RADAR wu RADAR rad RADAR full RSS wu RSS/RCS RSS/RWA TCM x x x x x x x x x x x x x x x x x x x x x x x x x x S&ER-2 S&ER-3 S&ER-4 S&ER-5 S&ER-5a S&ER-6 S&ER-7 S&ER-8 x x x x x x x RTE & SPB
8-7
180 of 217
Table 8.4
S&ER-1 Stellar occultations ORS CIRS ISS UVIS VIMS MAPS CAPS CDA INMS MAG MIMI RPWS RADAR 4 121.856 32.096 182.784 16 0.524 1.498 1.976 8 60.928 0 Titan Saturn
Telemetry Mode Pickup rates

Icy Icy Icy Satellites Satellites Satellites & OpNav 4 365.568 5.032 18.432 4 0.524 1.498 1.976 4 30.464 0 4 304.64 5.032 18.432 4 0.524 1.498 1.976 4 60.928 7.6 4 243.712 5.032 94.208 8 4.192 1.498 1.976 8 60.928 0 FPW & INMS 0 0 0 0 16 0.524 1.498 1.976 8 365.568 0 RADAR/ INMS 0 0 0 0 16 0.524 1.498 1.976 8 30.464 364.8 DL FPW
S & E R - 2 S & E R - 3 S & E R - 4 S & E R - 5 S & E R - 5 a S & E R - 6 S & E R - 7 S & E R - 8 RTE & SPB Saturn
4 0 5.032 18.432 16 4.192 1.498 1.976 8
4 0 5.032 0 16 0.524 1.498 1.976 8 365.568 0
60.928 182.784 32.096 94.208 16 4.192 1.498 1.976 8 32.096 94.208 16 4.192 1.498 1.976 8
182.784 60.928 365.568 0 0 0
Notes: RADAR warmup is in S&ER-5A RADAR radiometry is in S&ER-5A or S&ER-8 RADAR full power is in S&ER-8
8-8
181 of 217
Table 8.5
9 RSS W/U (RWA) 6 RADAR Wu/Rad
3 DFPW (RWAF)
7 RADAR (RWA)
8 RADAR (RCS)
11 RSS2 (RWAF)
13 RSS3 (RWAF)
12 RSS3 (RWAL)
1 ORS (RWAF)
5 RWA Unload
4 DFPW -TCM
10 RSS3 (RCS)
To: From: 1 ORS (RWAF) 2 ORS (RCS) 3 DFPW (RWAF) 4 DFPW - TCM 5 RWA Unload 6 RADAR Wu/Rad 7 RADAR (RWA) 8 RADAR (RCS) 9 RSS W/U (RWA) 10 RSS3 (RCS) 11 RSS2 (RWAF) 12 RSS3 (RWAL) 13 RSS3 (RWAF) 14 TCM (RCS) 15 TCM (ME) 16 DFPW-PEM Code: Y W T Y2 Y9 L N N6 F
T W Y Y N Y Y W N W Y Y L N N Y T T N T T Y N Y T T L N N Y
Y W N F Y Y W N W Y Y L F N Y
Y W N N Y Y W N W Y Y L F F N
N N F N N N N N N N N N N N F
Y N6 W N6 Y N6
Y Y Y
Y Y2 Y9 Y9 Y9 N W Y Y9 Y9 Y9 N Y Y N Y Y W N N Y Y N N N Y Y2 Y9 Y9 Y9 F Y2 Y9 Y9 Y9 F N N N N N Y2 Y9 Y9 Y9 N Y2 Y9 Y9 Y9 N Y N N N N N Y9 Y9 Y9 N Y N N N Y Y N N N N Y9 Y9 N L L N N
N N N F N N N N N N N N N N N
Y Y Y N F Y Y Y N Y Y Y L N N
Y N6 Y N N N Y Y W N L N N Y Y Y L Y Y
W N6 Y N6 Y L N6 N6
N N N N N N Y N6 Y
N N N N N N N N N Y2 Y9 Y9 Y9 N
= yes, permitted transition = permitted, but must allow time for RWA spin-up = permitted, but must allow time for RWA spin-down = yes, permitted, but prefer to go via 2 ORS (RCS) = yes, permitted, but prefer to go via 9 RSS W/U = permitted, but insufficient (low) EoM power = no, transition not permitted or not required = not permitted w/o intermediate 6 RADAR Wu/Rad = permitted transition to/from a Fixed Sequence
8-9
16 DFPW-PEM
2 ORS (RCS)
14 TCM (RCS)
15 TCM (ME)
182 of 217
8.2
MISSION DESIGN GUIDELINES & CONSTRAINTS DEFINITION
The purpose of this subsection and Subsections 8.3 and 8.4 is to establish mission design guidelines and constraints that govern how the various Program systems and subsystems will be used to achieve science return, while providing assurance that the scenarios can be reliably developed with the available Program resources. These guidelines and constraints are intended to establish an envelope within which the mission scenarios are designed, developed, implemented, and executed. This minimizes unnecessary optimization and management turbulence. In general, these items are of a medium to long-range planning nature. Their purpose is to define and balance the interfaces between the Spacecraft Office, the Mission Support and Services Office, and the Science and Uplink Operations Office. The distinction between a guideline and a constraint is as follows. Each constraint is binding, necessitating formal waiver approval if it is to be violated. Guidelines have a solid level of support within the Program and should therefore be honored if they do not lead to appreciable science loss or increase in mission risk and cost. Guidelines & constraints have been organized by topic and labeled with NNNNN - G# for guidelines and NNNNN - C# for constraints. The 3-5 letter abbreviations NNNNN stand for the category of the guideline or constraint: OPS for Operational Modes and Sequence Constructs, SEQ for Sequence Development, POINT for Spacecraft Pointing, TEL for Telecommunications Strategies for Uplink & Downlink, DATA for Management of On-Board Data, PRESAT for Pre-Saturn Science Activities, ESB for Earth Swingby, MEO for main engine operations, and MISC for Miscellaneous. Numbering is done by category and restarted each new subsection. During the post-launch scenario development, the Mission Design Team has three principal areas of responsibility: a) Perform long-term studies to show feasibility of scenarios within consumable constraints and Program operating constraints; b) Develop and update appropriate mission design guidelines and constraints;
Coordinate scenario design with the science and uplink teams to ensure consistency with the guidelines and constraints.
8.3 8.3.1
MISSION DESIGN GUIDELINES AND CONSTRAINTS OPERATIONAL MODES AND SEQUENCE CONSTRUCTS
Constraint OPS-C1 Operational Mode Usage Each operational mode shall be defined in Subsection 8.1 and adhere to the design constraints in Subsection 8.1.3 and 8.1.4.
Rationale: See discussion in Subsection 8.1.1
Constraint OPS-C5 Transitions from Operational Mode to Unique Sequence The state transitions required from (to) any operational mode into (out of) a unique sequence shall be built into the unique sequence.
Rationale: Consolidates the unique sequence design activity into one effort.
Constraint OPS-C6 Allowed Instrument Commanding Instrument state changes within an operational mode shall not require any CDS controlled heater commands.
Rationale: This and the power allocations in Table 8.5 will ensure that remotely generated state change commands by the instruments do not require special integration into the spacecraft sequence.
Constraint OPS-C7 Operational Mode Transitions All spacecraft activities required to change from one mode to another mode shall be defined in a transition sequence. Standard transition sequences shall be used for the mode switches 8-10
183 of 217
indicated in Table 8.7 (see next page). The scenario design shall allow windows long enough and sufficient power margins for all transition activities. Science is permitted during a transition if an instrument is on in both the preceding and following mode. During the transition, however, the instrument has no flexibility for state changes other than those required during the transition.
Rationale: Defines transition rules, prevents arbitrary science interruptions.
8.3.2
SEQUENCE DEVELOPMENT
Constraint SEQ-C2 Scenario Development Margin The following margins shall be maintained when planning scenario activities, including engineering and science support activities. These margins are set aside to allow for later identified activities. These margins are reduced near the event time to reflect the maturity of the scenario design. Design Product SOP Sequence Memory (130,238 total words) Allocation Margin SSR Usage (2 SSRs) Allocation Margin 80 Mbit (2%) 80 Mbit (2%) 0 Mbit (0%) Downlink Margin 5% 5% 3%
110,702 words SOP Update 117,214 words Final upload 127,633 words
19,5356 3.92 Gbit words (15%) 13,023 3.92 Gbit words (10%) 2,605 words 4.00 Gbit (2%)
Rationale: Large early margins allow simpler modeling to check limits. CDS memory for sequence design is assumed to be 130,238 words. Sequence memory accounts for a total volume of 153,599 words, with 1024 words set aside for global variables, 1856 words for IDAPs, 4096 words for mini-sequences, 10240 words for modules, 2048 words for TCM sequence, and 4096 words for IVP updates (these last two are TBD) leaving a total of 130,2438 words for background sequences.
Constraint SEQ-C3 Scenario Development Activity Priority Windows shall be inserted during scenario development for the following activities, in the following priority: a) Propulsive Maneuvers and Supporting Activities
Rationale: Windows shall be set aside for spacecraft propulsive maneuvers and their corresponding turn times. OPNAV opportunity windows to support maneuver design shall be inserted. (Note that science activities are permitted if they do not conflict with the maneuver or supporting activities.)
b)
Reaction Wheel Unloads

Rationale: Reaction wheel unloads shall be scheduled periodically from SOI-6 months to EOM, when the predicted accumulated angular momentum reaches a SCO defined limit.
c)
Science Activities
Rationale: Windows shall be inserted for science activities and their related engineering support activities, including OPNAV images scheduled to enhance pointing performance, if necessary.
d)
Other Engineering Activities

Rationale: Windows shall be provided for engineering activities including performance tests and calibrations.
Constraint SEQ-C5 OP NAV Sequencing Spacecraft Operations (Navigation) personnel shall act as the Prime Instrument Team for the purpose of sequencing optical navigation images.
Rationale: Avoids an additional unique interface.
8-11
184 of 217
Constraint SEQ-C6 Late Update No more than one late update (change to sequence prior to uplink) per sequence during the Saturn tour shall be allowed to incorporate sequence changes due to navigation and spacecraft clock drift updates.
Rationale: Late updates allowed to meet accuracy requirements, primarily for targeted satellite flybys during the tour. Limit of one late update minimizes the Sequence Virtual Team workload. Late updates will only be changes to target vectors and module start times, and will be inserted into the sequence process as determined by the SVT. Should there be more than one tour targeted flyby in a sequence, pointing requirements may not be able to be met on all flybys unless multiple late updates to update pointing are approved by the Program.
Constraint SEQ-C7 Live Update No more than one sequence "live update" (change to sequence pointing and timing after it has been uplinked) per week shall be allowed. The live update capability shall be supported beginning with the Approach Science subphase, approximately SOI - 6 months.
Rationale: "Live updates" are needed to meet accuracy requirements. Limit of one "live update" per week limits the Sequence Virtual Team workload. "Live updates" will only be changes to IVP and movable block start times.
Constraint SEQ-C8 DSN Support for Real-time Commands Real-time commands shall not require additional DSN passes over those regularly scheduled, except to support spacecraft emergencies or critical events.
Rationale: DSN passes are a critical resource, and except for emergencies or critical events, it is prudent to limit real-time commanding to regularly scheduled passes. (Real-time commands may be sent during any pass scheduled for other purposes.)
Constraint SEQ-C9 On-board Distributed Sequence Timing Changes Once a distributed sequence has been loaded on-board, all timing changes (such as ephemeris changes, clock drifts, or movable blocks) that affect system-level commands and activities shall be implemented by changing CDS command execution times.
Rationale: Changes to internal instrument sequence timing could result in unexpected interactions. For example, no instrument commands that independently change the timing of microphonics are allowed.
Constraint SEQ-C10
Triggered Instrument Execution Time Definition
Instrument execution time in a trigger command shall be a relative time (as opposed to an absolute time) and is defined to be relative to the receipt of the trigger command by the instrument.
Rationale: Distributed sequencing does not mean independent sequencing--all instrument activities must be directly tied to the CDS sequence, and can be shifted or canceled by changing only the CDS sequence.
Constraint SEQ-C12
Huygens Probe Checkout Sequencing Constraint
No other spacecraft activities shall be sequenced during a Probe Checkout.

Rationale: MPVT/SPVT /SVT cannot verify that CDS command bandwidth would not be exceeded in the presence of other activities, since Probe telecommand frequency cannot be checked explicitly.
Constraint SEQ-C13
OPNAV Image Return (was a guideline, SEQ-G3)
Optical navigation images shall be returned at the next available downlink opportunity following exposure. All OPNAV images shall be compressed using lossless compression to reduce the total volume of OPNAV data downlinked.
Rationale: Time-critical navigation products require that OPNAVs be returned as soon as possible. Op Nav data volume shall be compressed to increase science data allocation.
8-12
185 of 217
Constraint SEQ-C15 Superior Conjunction Downlink Data Rate Downlink data rate shall be reduced to 1896 bps (RTE or S&ER) when the SEP angle falls to 2.0 or lower.
Rationale: X-band capability begins to be degraded when the SEP angle is low and degrades more as the angle decreases. 1896 bps is the minimum data rate which can record science data and provides higher reliability during down link than higher rates. The constraint does not forbid the recording of science data during the SEP<2 period.
Guideline SEQ-G2 OPNAV Image Scheduling Optical navigation images should be scheduled at a rate of no more than 8 per day during the tour. OPNAVs should only be scheduled when such data (including reasonable margin) significantly improve TCM design, near target pointing, satellite ephemerides, or trajectory reconstruction.
Rationale: Defines the maximum needed.
Guideline SEQ-G6 Superior Conjunctions Spacecraft activities should be limited when the SEP angle is 3.Spacecraft pointing changes should not be requested inside 3 (however, rolls about the Z-axis, with Z to Earth, are allowed) Planned activities should not require successful commanding inside 3, or successful playback inside 2. Downlinks should not be requested inside 1, except for cruise Radio Science Conjunction experiments.
Rationale: X-band capability begins to be degraded when the SEP angle is low and degrades more as the angle decreases. The minimum angle for communication depends on solar noise conditions. Limiting spacecraft activities during known periods of uncertain communication is prudent. Downlinks inside 1 SEP are unlikely to be successful.
Guideline SEQ-G7 Timing Control Ring or Saturn observations which need timing control better than 13 seconds (1 ) should be scheduled on orbits with no Titan inbound encounter.
Rationale: Titan perturbs the orbit and tight timing control may not be available at Saturn. Preliminary analysis indicates timing uncertainties following a Titan encounter range from about 2to 60 seconds (1 sigma), depending on the altitude of the flyby (the larger uncertainties from closer flybys).
Guideline SEQ-G8 Quiet Periods Development and Operations activities should allow for vacations and/or reduced workload during weekends and JPL observed holidays.
Rationale: Allows for time off to prevent staff overload. During these periods every attempt should be made to manage activities that require special preparation, analysis or monitoring.
Guideline SEQ-G10 First Time Event Scheduling First Time cruise events should not be scheduled in the same sequence time period as a key spacecraft event (e.g., probe activities, unique activities with a geometric constraint such as encounters or opposition experiments) in order to allow adequate time to recover from possible safing between the first time event and the key event.
Rationale: First time activities are unproven in flight and are more likely to induce safing than an activity that has been run before. Allowing sufficient time between first time activities and time critical events is prudent. Events such as PIM and PEM, which are repeated many times and are not geometry dependent are not considered key events since they can be rescheduled with minimal impact. Two to six weeks is a reasonable time before most events to recover from safing, perform fault analysis, and redesign and uplink the canceled sequence.
8-13
186 of 217
8.3.3
SPACECRAFT POINTING Spacecraft Articulation Margin Policy
Constraint POINT-C1
TBD. (This constraint will contain the Projects margin policy for turn rates and accelerations on reaction wheels and thrusters. Combined with AACS deliveries of the available raw articulation resources, this will provide all the necessary information for planners to design turns.) Constraint POINT-C4 Prime Instrument One science instrument shall be designated "prime" during science observing time in which the spacecraft pointing is not already determined. An instrument team will specify the spacecraft pointing for the interval in which it is prime.
Rationale: The purpose of this constraint is to avoid extra interfaces by defining that there shall be a single instrument that controls pointing during each observation period. The burden of any coupled pointing design rests solely on the instrument teams themselves.
Constraint POINT-C5 Prime Instrument Specified Attitude Prime instruments shall leave the spacecraft axes at: Science Planning-specified attitude at the end of their time as a prime instrument.
Rationale: The Science Planning Team is responsible for managing and defining the waypoint strategy used for Tour. A waypoint strategy will be adopted that minimizes any unnecessary spacecraft slewing.
Constraint POINT-C6 Turns to Targets The SPVT shall be responsible for spacecraft turns when both the target body and prime instrument change.
Rationale: Defines who has control of turns.
8.3.4
TELECOMMUNICATIONS
Constraint TEL-C1 Cruise DSN Coverage Cruise DSN coverage shall be requested consistent with that specified in the Project Service Level Agreement (PSLA)
Rationale: The PSLA is the controlling document for DSN coverage requests. DSN coverage is required for downlink spacecraft telemetry and uplink commands, and to provide navigation data for maneuvers, planetary encounters, conjunctions, instrument checkouts, cruise science, etc.
Constraint TEL-C2 Tour DSN Coverage (was a guideline, TEL-G3) An average of one downlink period per day (exclusive of Radio Science passes) shall be scheduled during the tour.
Rationale: Consistent with the 15 hour science recording/9 hour downlink operations concept. Provides flexibility in scheduling DSN resources while also constraining their average load. Occultation periods and gravity field flybys generally require two DSN stations for complete coverage of the event. Radio Science geometric experiments which require consecutive DSN passes shall be accommodated on an occasional basis (estimated at ~ one additional pass per month, averaged over the four years of the tour).
Constraint TEL-C9
High Activity Downlink
High activity data return shall be calculated assuming one of the following DSN and spacecraft configurations: 1) northern hemisphere 70 meter DSN pass, ranging off, 90% confidence; 2) northern hemisphere 70/34 meter arrayed pass, ranging off, 90% confidence. High Activity passes shall be requested up to 35% of the time. Actual data return shall be accomplished with equivalent performance DSN configurations.
Rationale: Specifies the expected data return configuration adequately for planning purposes. Northern hemisphere stations may have different performances (e.g. the Goldstone low noise feed upgrade); equivalent performance implies performance equivalent to whichever station is requested. High Activity days are capable of returning 4 Gbit per day.
8-14
187 of 217
Constraint TEL-C10
Low Activity Downlink
Low activity data return shall be calculated assuming a northern hemisphere 34 meter DSN pass, ranging on, 90% confidence. Actual data return shall be accomplished with equivalent performance DSN configurations.
Rationale: Specifies the expected data return configuration adequately for planning purposes. Low Activity days are capable of returning 1 Gbit per day.
Constraint TEL-C12
Telemetry Link Confidence Level
The Spacecraft Operations Office and the Science Planning Team shall design sequences such that the telemetry link provides the following probabilities of telemetry being successfully received by the ground during the following mission phases or activities: Mission Phase or Activity Saturn tour Cruise
Rationale: 004 requirement.
Probability Level 90 % * 85 %
*Dual playbacks shall be used for critical data and other data as specified in DATA-C4. Constraint TEL-C14 Data Rate Switches and DSN Lockup Data transmitted during initial DSN lockup, data rate switches, and unexpected outages (e.g., bad weather or station problems) shall be assumed to be lost.
Rationale: Operations staffs from Cassini and from other missions have indicated that strategies to recover data transmitted during DSN lockup (i.e. at frame sync) and data rate switches are expensive and complicated. DSN lockup is estimated to be ~ ten seconds at kilobit and higher data rates, and data rate switches are expected to take even less time. Due to the low amount of data lost, these strategies are not needed.
Constraint TEL-C15 Radio Science Occultation Pass Strategy During Radio Science Occultation experiments, telemetry modulation shall be turned off.
Rationale: Telemetry modulation is turned off to increase the signal-to-noise ratio during Radio Science occultation experiments.
Constraint TEL-C16 Command Uplink Background sequence design shall not require more than two command uploads per sequence. For each upload, time shall be set aside during the pass for two uplink attempts and one verification period during one pass.
Rationale: Breaking up detailed sequences into multiple pieces involves significant ground complications and coordination and should be minimized. Whenever possible, sequences should only require one command upload.
Guideline TEL-G2 Real-time Commands The use of real-time commands should be constrained to those activities which cannot be accomplished via the stored sequence.
Rationale: Real-time commands increase cost and risk.
Guideline TEL-G4 Ranging Data Navigation ranging data may be collected during all low activity period DSN passes, but should be excluded from high activity period DSN passes.
Rationale: Ranging off increases the downlink signal strength. Doppler signals alone are sufficient for navigation near Saturn or Titan.
8-15
188 of 217
Guideline TEL-G5 Length of Downlink Period Downlink periods should be 9 hours in length, unless a longer pass is required to return 4 Gbit on a high activity day or 1 Gbit on a low activity day.
Rationale: Restricts planners from overly burdening the DSN by regularly scheduling long passes.
8.3.5
MANAGEMENT OF ON-BOARD DATA
Constraint DATA-C5 Probe Data Protection Probe relay data shall be dual recorded (the same data recorded on each SSR) and kept stored on-board the orbiter until ground command is received by the orbiter authorizing deletion of the probe relay data. The ground command shall be issued after it has been verified that the correct data has been received at JPL (for data in non-protected partitions in SSR A and B) and at ESOC (for data in protected partitions in SSR A and B). Uplink window opportunities shall be provided after the transmission of probe data to allow data deletion or overwriting from the SSR. The windows shall be scheduled following a TBD (24) hour period on the ground during which data quality is verified.
Rationale: Prompt uplink windows following ground receipt of probe data can free up SSR space for post-flyby science collection by releasing the write protection flag.
Constraint DATA-C6 Engineering Data Engineering data shall be continuously recorded in all flight sequences.
Rationale: Allows the spacecraft health to be tracked and attitude to be reconstructed. Under normal conditions, it is not necessary that all engineering data be downlinked.
Constraint DATA-C7 SSR Partition During tour operations, each SSR shall be capable of storing telemetry in at least three partitions. The partition layout of these shall be the same on both SSRs.
Rationale: Typically partitions will be needed for engineering (except AACS), science (plus AACS), and OPNAVs and/or high-value science. Identical layouts minimize the chance of problems caused by an unexpected SSR swap. The partition sizes may vary between SSRs but the same partitions must exist. The minimum size for a partition is one frame, or 8800 bits.
Constraint DATA-C9 SSR Instrument Data Recording An instrument's data recording shall be monitored by CDS and stopped once the data volume equals the data volume allocation for that instrument.
Rationale: Data volumes must be policed to protect all engineering and instrument data allocations. CDS has been identified as the authority best suited to data volume policing. CDS performs data policing via data volume allocations uploaded from the ground with each sequence upload.
Constraint DATA-C10 Navigation SSR allocation The navigation data volume allocation for OPNAVs shall be maintained separately from the ISS data volume.
Rationale: Navigation data volume allocations will typically supplement the ISS data volume allocation just before the OPNAV is taken.
Constraint DATA-C11 SSR Priority Playback Only OPNAVs and probe mission data shall be allowed priority in the playback sequence during the tour, except for post-anomaly diagnostic data retrieval.
Rationale: Prioritized playback of specific instrument data is very difficult as all data are mixed within the science and engineering partition. Neither science nor engineering managers have requested prioritized playback of any specific data, unless a spacecraft fault has occurred.
8-16
189 of 217
Constraint DATA-C12 High-Value Data High-Value data as specified by a science team or SCO, shall be written into a separate partition on-onboard the spacecraft (but not write-protected).
Rationale: Provides additional protection, and permits a science team or SCO to use part of its data volume allocation to protect important data.
Constraint DATA-C13 High-Value Data Playback Data selected as high-value shall be played back over two separate DSN passes as executed by the on-board sequence. Thereafter, the data shall be released without the necessity of ground verification of receipt of the data. High value data playback shall be counted within the downlink data allocation of the relevant team for both playbacks.
Rationale: Provides additional protection of High-Value Science (or Engineering) Data from accidental loss of DSN coverage on one of two days, loss of all or part of relay from DSN to JPL, inclement weather, etc.
Guideline DATA-G3 SSR Playback During science operations at Saturn, all data recorded on the solid state recorders since the prior playback should be play back by the end of each DSN downlink pass.
Rationale: This simplifies SSR management
8.3.6
PRE-SATURN SCIENCE ACTIVITIES
Constraint PRESAT-C11 Quiet Spacecraft for Radio Science During Cruise During certain Radio Science cruise activities (Gravitational Wave Experiments, GWE Systems Tests, Solar Conjunction Experiments, HGA calibrations, and RSS ICO tests), a "quiet spacecraft" is required and shall be defined as follows: 1) S/C attitude controlled by RWAs and no firings of RCS thrusters or the main engine; 2) No motion imparted to spacecraft by any other instrument (i.e., no articulation, moving filter wheels, etc.); 3) No state changes (includes power changes or transients greater than 28 Watts) and with other disturbances (such as activating and deactivating heaters, transmitters, etc. minimized.
Rationale: Radio Science investigations are sensitive to all small forces imparting motion to the spacecraft, including other instruments' motions and state changes. From PRESAT-C6: Reduction of the reaction wheels momentum buildup can be accomplished without thruster use, for instance through 180 degree slow rolls about the Earth line every 10 days. This motion takes care of the momentum buildups for the X- and Y- axes. Calculations show that the Z momentum buildup is slow enough that it does not require unloading within the 40 days of the GWE. From PRESAT-C8: If 28 W of collimated (worst case) thermal radiation changes direction, it can result in a differential translational acceleration over the time scales of interest equal to the goal of 699-004 requirement 4213-1.
8.3.8
SATURN TOUR & SOI
Constraint TOUR-C1 Activities prior to SOI The following conditions shall apply while the SOI critical sequence is active: a) attitude shall be X-band to Earth, until the start of the turn for the ascending ring plane crossing preceding the SOI burn. The secondary axis shall be between +X to Saturn North Pole and +X to Saturn North Pole -40 degrees (roll about spacecraft Z with +X toward Saturn) no spacecraft attitude changes except to support ring plane crossing and the SOI burn. Instruments are quiescent(Quiescent means no power state changes, no s/w modifications) -instrument internal sequences, initiated prior to SOI critical sequence activation, may be executing. 8-17
b) c)
190 of 217
- instruments may lower their high voltage states prior to the SOI burn from an instrument internal sequence already executing d) e) f) no AACS control mode changes no real-time commands no sequenced bus commands except for engineering commands issued from the critical sequence. Exception: S/C telemetry mode changes (including corresponding subcarrier and mod-index changes) between any RTE&SPB telemetry mode and S&ER10 are allowed to execute from the background sequence until 12 hours before the first critical activity executes [about 29 hrs before the SOI burn]) during the critical sequence, only one SSR is available, due to the SSR ping-pong bit being disabled
Rationale: Defines a Quiet Period before SOI where safing is unlikely due to lack of activity, and allows time to recover from safing if needed.
g)
Constraint TOUR-C2 Titan Atmospheric Model Update The Science and Uplink Office shall investigate on the first Titan flyby the Titan atmospheric density and provide a Titan atmospheric model using that data by one month after the first Titan flyby.
Rationale: Allows adjustment of Titan flyby altitudes. It is expected that AACS will also conduct an analysis of the controlled response of the first Titan flyby in support of minimum Titan flyby altitude decision.
Constraint TOUR-C3 Probe Release at Late Dates Probe release shall not be attempted less than 9 days before Titan encounter.
Rationale: Provides sufficient time for emergency maneuvers on failure of Orbital Deflection Maneuver.
Guideline TOUR-G1 Post-Separation Imaging of the Probe Images of the Huygens probe should be acquired by both the NAC and the WAC during the time periods from probe separation to probe separation + 1 day and again from ODM to ODM + 3 days. Preferred observation times are probe separation + 1 day and ODM + 3 days.
Rationale: Images of the probe after separation can be used to estimate the probe trajectory and adjust the HGA pointing direction for the data relay. They can also be used to determine the probes approximate orientation for anomaly diagnosis. Images taken shortly after separation can also be used for public outreach.
8.3.10
MISCELLANEOUS Checkout of Redundant Hardware
Constraint MISC-C1 (formerly C-44)
Operating subsystems shall not be switched to standby redundant units for status or calibration unless: a) critical sequences require immediate unit switching in response to a failure in the primary operating unit, or b) the spacecraft has experienced a stressful environment (particle hits, etc.) and knowledge of the redundant unit status could substantially affect future plans, or c) one of the following allowed activities: 1) SRU Backup unit, which may undergo yearly performance characterizations. The unit shall not be set to Prime during the maintenance. 2) switching the AACS bus during the BAIL maintenance activity 3) switching the Probe Support Avionics (PSA) unit during Probe operational activities 8-18
191 of 217
4) switching to backup UVIS CPU2 during Instrument Checkout as done during ATLO tests 5) operating the backup EGA during periodic maintenance 6) operating the backup RWA during periodic maintenance 7) switching to backup MAG processor/power supply during Instrument Checkout as done during ATLO tests
Rationale: Checking redundant units does not save costs or increase mission reliability. Exceptions reflect activities where designed activities are an allowed in-flight repeat of ATLO tests during ICO, activities where SCO has adopted the prelaunch development design which reflects periodic use of the backup unit, and where the activity (BAIL maintenance) requires the use of a separate unit.
Constraint MISC-C2
In-Flight Use of Redundant Units
Prior to SOI plus 2 years, mission and sequence design shall be based upon the assumption that redundant spacecraft units are not available for the enhancement of mission return, with the exception noted below.. The exception is: redundant data storage devices shall be used to capture critical science data and engineering diagnostic data redundantly, and may be used to enhance mission return beginning with Phoebe approach science, 01 June 2004.
Rationale: Controls use of redundant units to a reasonable level.
8.4
CONTROLLED SCENARIO TIMELINES
The following scenario timelines are under change control: SOI and Probe Mission. The timelines are repeated on the following pages from the appropriate sections in this document. These timelines are not completely up to date, but are intended only to reflect the last scenario design that was reviewed across the project and subsequently approved via ECR.
8-19
192 of 217
SOI Events Timeline

Phoebe Targeting TCM bi-prop pressurization SOI-35 Phoebe Flyby SOI-19 d
Phoebe Saturn Clean-up Periapsis TCM Approach SOI-15 d Clean-up (if needed SOI-10 d) Activate Critical Sequence Start Quiet Period SOI-8 d SOI initial Clean-up SOI+2 d Critical Sequence Execution
Solar Conjunction
SOI Final Clean-up SOI+15 d
pre-Quiet Period sequence S1 Day of Year (DOY) 145

Passes per day 3 2 1 0
Quiet Period CS post-Burn Period sequence S2
150
155
160
165
170
175
180
}
185
190
195
200
FOIA 10-JPL-F-00451
193 of 217
HGA to Earth
HGA to probe
HGA to Earth
Earth, Sun
Probe at Entry
(interface altitude 1270 km)
Orbiter Probe Support
Turn HGA to Probe (~12 min) Change to PRLY tlm mode, PSAs ON
Turn HGA to Earth
Receive & Record Probe Data
(7.86 hrs req'd for both SSRs)
Probe Data Playback
SSRs write-protected
Orbiter Science
Quiet period* begins TCA-8 days All instrument data cleared from SSRs
All instruments OFF
Science resumes (at most) 2 days after playback

(Probe may request additional playbacks)
Probe Events
Coast Phase
Probe Entry
-2h 6m
Cassini-Titan range: 74689 km
*Quiet period restrictions: Spacecraft turns and rolls (S/C in RCS mode) Power state changes Engineering configuration changes AACS Mode Changes
Probe Link
(~4.5 hr) Orbiter Closest Approach Probe (TCA) Touchdown
Surface Science: S/C will continue to track probe for ~60 minutes (Probe battery life ~ 5 hrs)
Time from TCA

-4.0h
0
Cassini-Titan range @ TCA 60000 km
No quiet period restrictions on: SSR data playback MAPS data collection
Cassini/Huygens Probe Relay Timeline

194 of 217
Mission Plan Guidelines & Constraints History

OPERATIONAL MODES OPS-C1 ACTIVE OPS-C2 deleted by ECR 100413 OPS-C3 Changed to guideline G3 by ECR 100413 OPS-C4 deleted by ECR 100413 OPS-C5 ACTIVE OPS-C6 ACTIVE OPS-C7 ACTIVE OPS-C8 deleted by ECR 100413 OPS-C9 deleted by ECR 100413 OPS-C10 deleted by ECR 100413 OPS-G1 deleted by ECR 100413 OPS-G2 deleted by ECR 100413 OPS-G3 deleted by ECR 100930 SEQUENCING SEQ-C1 deleted by ECR 100413 SEQ-C2 ACTIVE SEQ-C3 ACTIVE SEQ-C4 deleted by ECR 100413 SEQ-C5 ACTIVE SEQ-C6 ACTIVE SEQ-C7 ACTIVE SEQ-C8 ACTIVE SEQ-C9 ACTIVE SEQ-C10 ACTIVE SEQ-C11 deleted by ECR 100413 SEQ-C12 ACTIVE SEQ-C13 ACTIVE, was SEQ-G3 SEQ-C14 deleted by ECR 100930 SEQ-C15 ACTIVE SEQ-G1 deleted by ECR 100413 SEQ-G2 ACTIVE SEQ-G3 changed to constraint by ECR 100413 SEQ-G4 deleted by ECR 100413 SEQ-G5 deleted by ECR 100413 SEQ-G6 ACTIVE SEQ-G7 ACTIVE SEQ-G8 ACTIVE SEQ-G9 changed to constraint by ECR 100413 SEQ-G10 ACTIVE POINTING POINT-C1 ACTIVE POINT-C2 deleted by ECR 81904 POINT-C3 deleted by ECR 100413 POINT-C4 ACTIVE POINT-C5 ACTIVE POINT-C6 ACTIVE TELECOMMUNICATIONS TEL-C1 ACTIVE TEL-C2 ACTIVE TEL-C3 deleted by ECR 100413 TEL-C4 deleted by ECR 100413 TEL-C5 deleted by ECR 100413 TEL-C6 deleted by ECR 100413 TEL-C7 deleted by ECR 100413 TEL-C8 deleted by ECR 100413 TEL-C9 ACTIVE TEL-C10 ACTIVE TEL-C11 deleted by ECR 100413 TEL-C12 ACTIVE TEL-C13 deleted by ECR 100413 TEL-C14 ACTIVE TEL-C15 ACTIVE TEL-C16 ACTIVE, was guideline TEL-G1 TEL-G1 changed to constraint by ECR 100413 TEL-G2 ACTIVE TEL-G3 deleted by ECR 100413 TEL-G4 ACTIVE TEL-G5 ACTIVE DATA MANAGEMENT DATA-C1 deleted by ECR 100413 DATA-C2 deleted by ECR 100413 DATA-C3 deleted by ECR 100413 DATA-C4 deleted by ECR 100413 DATA-C5 ACTIVE DATA-C6 ACTIVE DATA-C7 ACTIVE DATA-C8 deleted by ECR 100413 DATA-C9 ACTIVE DATA-C10 ACTIVE DATA-C11 ACTIVE DATA-C12 ACTIVE DATA-C13 ACTIVE DATA-G1 deleted by ECR 100413 DATA-G2 deleted by ECR 100413 DATA-G3 ACTIVE PRE-SATURN PRESAT-C1 deleted by ECR 100413 PRESAT-C2 deleted by ECR 100413 PRESAT-C3 deleted by ECR 100413 PRESAT-C4 deleted by ECR 100413 PRESAT-C5 deleted by ECR 100413 PRESAT-C6 deleted by ECR 82324 PRESAT-C7 deleted by ECR 100413 PRESAT-C8 deleted by ECR 82324 PRESAT-C9 deleted by ECR 100413 PRESAT-C10 deleted by ECR 100413 PRESAT-C11 ACTIVE PRESAT-G1 deleted by ECR 100413 PRESAT-G2 deleted by ECR 100413 PRESAT-G3 deleted by ECR 100413 EARTH SWINGBY ESB-C1 deleted by ECR 100413 ESB-C2 deleted by ECR 100413 ESB-C3 deleted by ECR 100413 ESB-C4 deleted by ECR 100413 ESB-C5 deleted by ECR 100413 ESB-C6 deleted by ECR 100413 ESB-C7 deleted by ECR 100413 ESB-C9 deleted by ECR 100413 ESB-C10 deleted by ECR 100413 ESB-C11 deleted by ECR 100413 ESB-C12 deleted by ECR 100413 ESB-C13 deleted by ECR 100413 ESB-C14 deleted by ECR 100413 ESB-C15 deleted by ECR 100413 ESB-C16 deleted by ECR 100413 ESB-C17 deleted by ECR 100413 ESB-C18 deleted by ECR 100413 ESB-C19 deleted by ECR 100413 TOUR TOUR-C1 ACTIVE TOUR-C2 ACTIVE TOUR-C3 ACTIVE TOUR-G1 ACTIVE TOUR-G2 deleted by ECR 101102 MAIN ENGINE OPERATION MEO-C1 deleted by ECR 100413 MEO-C2 deleted by ECR 100413 MEO-C3 superceded by MEO-C5, ECR 82287 MEO-C4 deleted by ECR 100413 MEO-C5 deleted by ECR 82287 MEO-C6 deleted by ECR 100413 MEO-G1 deleted by ECR 100413 MEO-G2 deleted by ECR 100413 MISCELLANEOUS MISC-C1 ACTIVE MISC-C2 ACTIVE MISC-C3 superceded by MEO-C6 per ECR 81999 MISC-G1 deleted by ECR 82227 MISC-G2 superceded by MEO-C6 per ECR 81999
FOIA 10-JPL-F-00451
195 of 217
MISSION PLAN ECR CHANGE LOG

ECR 101102 100867 100930 100947 100857 82356 82324 82394 82354 100133 100127 82355 82357 82358 82359 82392 82338 82210 82211 82321 82320 82319 82315 82306 82312 82314 82313 82311 82317 82316 82318 82224 82290 82298 82292 82287 82285 81932 SUBJECT SOI Constraints OpMode Changes Mission Plan Constraints Conjunction Restrictions Dual SSRs Tour Data Rate Selection Quiet S/C for Radio Science during Cruise Change to Definition of Critical Data Reusuable Sequence Constructs PSLA Update VIMS Stellar Calibration Tour Downlink Strategy Tour Downlink Durations Tour Arrayed Passes DSN PSLA update Deletion of Table 8.2 Change Timing of GWE Test Operational Mode Definitions Telemetry Mode Changes Revision to DSN Requirements for C17-C19 ORS Masursky Imaging MAPS Cruise Science MAG post-HGA Calibration USO Characterization Rfs Telemetry-Ranging Interference Test Radio Science Pattern Calibration Radio Science Boresight Calibration Probe relay S-Band Demo ISS Dark Frames CIRS Cover Release (80K) CDA Operations During C17 Through C19 Module and Template Definition Trajectory Biasing and Delivery during ESB Aimpoints and Execution Times before ESB Modification of ESB-C19 Test TCM Deletion Record/Playback OPNAVs VIMS Cruise Decontamination APPROVED 13 May 02 27 Mar 02 9 Jan 02 9 Jan 02 31 Oct 01 31 October 00 23 August 00 2 August 00 18 July 00 25 June 00 26 May 00 16 May 00 16 May 00 16 May 00 8 Feb 00 25 Jan 00 19 Jan 00 5 Aug 99 14 July 99 16 July 99 30 June 99 30 June 99 30 June 99 25 June 99 25 June 99 25 June 99 25 June 99 25 June 99 25 June 99 25 June 99 25 June 99 17 May 99 7 April 99 7 April 99 17 Feb 99 3 Feb 99 3 Feb 99 18 Dec 98 SECTIONS 8 8 8 8 8 8 8 8 8 Table J.2 5 (add to text) 8 8 8 Table J.2 Table 8.2 Section 5 Table 8.5 Table 8.6 Table J.2 5, Table 8.2 5, Table 8.2 5, Table 8.2 5, Table 8.2 5 5, Table 8.2 5, Table 8.2 5, Table 8.2 5, Table 8.2 5, Table 8.2 5, Table 8.2 8 8 8 8 8 8 8, Tables 8.4 & 8.5, Append. F. IMPLEMENTED May 2002 Rev N May 2002 Rev N May 2002 Rev N May 2002 Rev N May 2002 Rev N June 2001-Rev M June 2001-Rev M June 2001-Rev M June 2001-Rev M 10 July 2000-Rev L 10 July 2000-Rev L 10 July 2000-Rev L 10 July 2000-Rev L 10 July 2000-Rev L 26 Jan 2000-Rev K 26 Jan 2000-Rev K 26 Jan 2000-Rev K 26 Jan 2000-Rev K 26 Jan 2000-Rev K 16 July 1999 - Rev J 16 July 1999 - Rev J 16 July 1999 - Rev J 16 July 1999 - Rev J 16 July 1999 - Rev J 16 July 1999 - Rev J 16 July 1999 - Rev J 16 July 1999 - Rev J 16 July 1999 - Rev J 16 July 1999 - Rev J 16 July 1999 - Rev J 16 July 1999 - Rev J 16 July 1999 - Rev J 16 July 1999 - Rev J 16 July 1999 - Rev J 16 July 1999 - Rev J 16 July 1999 - Rev J 16 July 1999 - Rev J 16 July 1999 - Rev J
iii
196 of 217
FOIA 10-JPL-F-00451
197 of 217
APPENDIX A REQUIREMENTS COMPLIANCE
Table A.1 gives an assessment of compliance with the Project Policies and Require-ments Document (699-004), based on the current version of that document. References are given in the table to specific sections in the Mission Plan that discuss aspects of the mission design that contribute to compliance with each requirement.
FOIA 10-JPL-F-00451
198 of 217
Table A.1 Mission Plan Compliance with the Project Policies & Requirements Document
Reqt. No. Sec 2 22-1D Requirement Title Project Policies and Constraints Project Goal Achieved? Discussion The complete Mission Plan addresses this goal by demonstrating a mission design that balances mission success with complexity that could drive cost. A high probability of proper operation is addressed by such aspects of the mission design as (continues) maintaining margins in other consumable budgets, such as gyro and reaction wheel usage; slowly lowering the Titan flyby altitude during the tour; reducing ring plane crossing risk until later in the tour, etc. The complete Mission Plan addresses these priorities. While there are no major compromises in the design, examples of these considerations in the scenario development are: minimum payload activity in first year after launch, cautious (continues) approach for the Earth flyby scenario, probe deployment on the first Saturn orbit with a backup opportunity on the second orbit, carefully constrained payload operation near SOI, and so forth. 22-3B 22-4 22-5 22-6 23-1 Sec 3 31-1C 31-2 32-1B 32-2 321-1 321-2D 322-1B 323-1B 324-1B 325-1B 326-1B 331-1A Mission Set: primary, backup, and secondary launch opportunities Titan IV/Centaur Launch Vehicle Launch Readiness Date Cassini End of Mission and End of Project Inertial Reference Frame Science Investigation Objectives Pre-Saturn Saturnian System Orbiter Science Investigations Probe Science Investigations En Route Gravitational Wave Experiment En Route Solar Conjunction Experiment Titan Objectives Saturn Objectives Ring Objectives Icy Satellite Objectives Magnetosphere Objectives Reference Operational Modes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes The complete Mission Plan addresses the primary mission. Backup and secondary missions have been defined [2.2]. Baseline vehicle is Titan IV/Centaur [3.1, 4.3]. Primary mission baseline has earliest launch date on October 6, 1997 [4.3]. Mission design complies [2.1, 7.1.10] Mission design and navigation software uses J2000 as the primary reference frame. Scenarios for payload operations in the interplanetary mission and the Saturn approach phase support these objectives [5, 6]. Scenarios for Saturn system observations from pre-SOI through the tour support these objectives [6,7]. Scenarios for Saturn system observations from pre-SOI through the tour support these investigations [6,7]. Probe scenario supports these investigations [6.3]. Opportunities and plans for gravity wave experiments have been identified [5.5, 6.1]. Shown in Cruise timeline (Figure 2.1) and Mission Events Table (Table 2.1); DSN coverage may need to be added in DMR Plans for Saturn tour will provide many observational opportunities for these objectives [6.3, 7]. Conflicting instrument requirements, such as pointing, power, and data rate will require allocation of observations to certain Titan flybys. Plans for Saturn tour will provide observational opportunities for these objectives [6.1, 6.3, 7]. Plans for Saturn tour will provide observational opportunities for these objectives [6.2, 6.3, 7]. Plans for Saturn tour will provide observational opportunities for these objectives [6.1, 6.3, 7]. Plans for Saturn tour will provide observational opportunities for these objectives [6, 7]. Reference operational modes have been defined [8] and future scenario work will define the detailed implementation.
Yes
22-2D
Project Priorities
Yes
FOIA 10-JPL-F-00451
199 of 217
Reqt. No. 331-2B Sec 4 411-1 411-2 411-3 411-4 411-5B 411-6C 412-1 413-1 414-1 414-2B 414-3 414-4D 414-5D 415-1 415-2 415-3B 415-4B 415-5B 416-1 416-2 D 416-3 Requirement Title Jupiter Science (not precluded) Project Derived Requirements Launch Vehicle Resiliency Launch Vehicle/Spacecraft Separation Contingency Launch Period Launch Period Duration Probability of Impact Sufficiently High Parking Orbit Gravity Assist Near-SOI Science Probe Delivery Orbit Probe Data Acquisition Probe Approach Velocity Probe Delivery Tracking Probe Delivery Orbit Tour Duration Tour Geometry Requirements Titan Flyby Frequency Satellite Flyby Minimum Altitudes Attitude Control Monopropellant Allocation Mission Scenarios Mission Contingency Achieved? Yes Yes Yes Yes Yes Yes - Prelim Yes Yes Yes Yes Yes Yes Yes Yes Yes No (but mostly) Yes Yes Yes Yes - Prelim Yes Discussion Mission design can accommodate limited Jupiter science for the distant flyby, but no firm decision is made, pending better understanding of ground system capability [5.5.3]. Baseline vehicle is Titan IV/Centaur [3.1,4.3] with fallback mission for SRM [2.2,4.3]. Launch sequence shows no unnecessary delay in separation after the injection burn. Separation is planned 10 minutes after MECO-2 [4.4]. Eleven contingency launch dates have been defined for the primary mission [4.2, 4.3]. Baseline launch period for the primary mission is 30 days in duration. Launch periods for the secondary mission (35 days) and the backup mission (18 days) have also been defined. [2.2, 4.2, 4.3] Requirement on the Centaur collision/contamination avoidance maneuver to avoid impact with other planetary bodies will be defined in the Target Specification [4.4]. Parking orbit altitudes are defined to achieve minimum 10-day lifetime, and a preliminary SHO contingency strategy has been defined to simply the commanding of maneuvers to raise the orbit altitude [4.4]. Trajectory design complies [5.1]. SOI scenario provides near-SOI science observations with relatively small increase in sequence complexity [6.2]. Trajectory design provides for probe delivery on the first Saturn orbit, and a backup opportunity on the second orbit [6.3]. Probe relay scenario complies [6.3]. Trajectory design complies; baseline value is 5.75 km/sec [6.3]. Probe entry is planned far away from Solar conjunctions [6.3]. Probe entry is on an inbound Titan flyby [6.3]. Trajectory design complies [7.1]. The current reference tour exceeds or complies with most, but not all, of these criteria. Specific trade-offs between the achieve-able geometry and science objectives for the tour will be made in close consultation with the Project Science Group. Titan flybys as close as 16 days, but no closer, are planned according to agreed-upon ground system constraints and the TCM spacing is provided [7.1, 7.4]. Minimum planned Titan flyby altitude is 950 km. Studies of Titan atmospheric models are continuing. Minimum planned icy satellite flyby is 500 km [7.1, 7.2]. Current hydrazine budget for attitude control activities is 22.1 kg with 3-sigma AACS statistics and conservative mission assumptions [3.2.3]. Resource operating margins for spacecraft consumables have been allocated [3.2.3], payload operating constraints within the operating modes are preliminary [8.1], ground system margins are not yet worked in detail. The mission contingency mass is creatable from several potential mission trade-offs including Saturn arrival date, SOI burn delay, initial orbit period, average Titan flyby altitude, etc. The ring crossings before and after SOI through the F-G gap satisfy this probability based on the risk constraint equation documented in the MRRD [6.2, 7.2].
Ring Hazards Prior to Probe Delivery Yes - Prelim
FOIA 10-JPL-F-00451
200 of 217
Reqt. No. 416-4 416-5B 416-6 416-7B 416-8B 416-9B 417-1 418-1D 441-1 441-2D 441-4 441-6C 441-7 4421-4 4422-1B 4423-2B Sec 5 5412-3D 542-1 544-1 Requirement Title Achieved? Environmental Hazards After Probe Yes Delivery Uplink Windows Adequate Tracking and Communications Operability of Operational Modes Interface Simplicity Operational Power Margins Personnel Holidays Earth Swingby Requirements on Mission Design Space-to-Ground Telemetry Link BER Space-to-Ground Telemetry Link Confidence Level Ground-to-Space Command Link Error Rate Maximum Allowable Communications Outage Period Ground-to-Space Command Link Confidence Level Redundancy Policy Critical Events Earth Swingby Verification Sequence Validation Operational Scenario Capabilities Qualitative Risk Assessment Yes Yes - Prelim TBD Mission design will provide supporting scenarios for flight sequence testing and for definition of early cruise sequences. This verification will be the continuing role of the Scenarios Working Group, where representatives from science, flight system, and ground system review proposed scenarios. A qualitative risk assessment has not yet been performed for the mission design but, in general, the elements of mission risk are similar to Galileo: long cruise phase with multiple close planetary flybys, probe deploy/relay, orbit insertion maneuver, etc Yes - Prelim Yes Yes - Prelim Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes - Prelim Yes - Prelim Yes Discussion The tour design meets this requirement via gradual reduction of the Titan flyby altitude and the ring plane crossing strategy. The Mission Plan is not yet at this level of detail. A mission constraint for uplink windows is defined [8.3]. No important events planned within 5-deg SEP. The tour design specifically avoided targeted satellite encounters within 5-deg SEP [7.2]. A preliminary definition and operating strategy for the operational modes have been made, particularly to minimize power and thermal analysis, but only preliminary assessments of the overall operability of the mission have been made [8.1]. This guideline has been included in the mission design approach. The power analysis used for definition of the operational modes includes 20-Watt operating margin in all power modes with additional margin [8.3]. SOI and probe mission trajectory design complies [6.2, 6.3]. Earth swingby requirements have been included in Section 8. Telecom data used for mission design for all mission phases assumes BER no greater than 1.0E-6. 95% link confidence level used in telecom analysis for all cruise and emergency link calculations. 90% link confidence used for Saturn tour data return predictions. Greater than 95% confi-dence for critical science activities at Saturn will be achieved Uplink error rate of 1.0E-9 is achieved by 1.0E-5 telecom error rate and CDS error detection. Minimum tracking coverage frequency is once per week in cruise [5]. Telecom data used for mission design for all mission phases based on 99% uplink link confidence level. No current plans to use redundant units for mission enhance-ments, other than the SSR. Work on the critical sequences and fault protection is very preliminary. Mission design studies to support this requirement are documented in the Earth Swingby Plan (699-70-3).
FOIA 10-JPL-F-00451
201 of 217
Appendix B Saturnian System Description The following charts include geometric quantities that are commonly used when developing mission scenarios. They are provided for convenient reference. Table B.1 lists geometric quantities for Saturn, while tables B.2A and B.2B list quantities for the rings and satellites. In both tables the quantities are split into orbital quantities, concerning the geometry of the body with respect to its primary (the Sun for Saturn and Saturn for the rings and satellites), and planetary or satellite quantities, concerning the shape and characteristics (radius, rotation, temperature, etc.) of the body itself. The satellites' table has been split: table B.2A lists orbital quantities, while table B.2B lists satellite quantities. A comprehensive description of the Saturnian system, graphical images of Saturn and its satellites, and other geometric quantities is available via the World Wide Web at http://bang.lanl.gov/solarsys -- this resource is compiled by Calvin Hamilton of the Los Alamos National Laboratory.
FOIA 10-JPL-F-00451
202 of 217
Figure B.1 Saturns Satellites and Ring Structure
FOIA 10-JPL-F-00451
203 of 217
Table B.1: Saturn Geometric Quantities

Quantity Solar distance, mean Solar distance, min Orbital Quantities Solar distance, max Siderial orbit period Mean orbital velocity Orbital eccentricity Inclination to ecliptic Equatorial radius at 100 mbar =Rs Polar radius at 100 mbar Equatorial radius at 1 bar Polar radius at 1 bar J2 (unnormalized) Mass GM (planet centered) Volume Planetary Quantities Rotation period, kilometric Rotation period, equatorial Axial tilt Atmospheric temp. at 1 bar Effective temperature Visual geometric albedo Bolometric Bond albedo Mean density Mean gravity at 1 bar Constituent gases Magnetic dipole moment Field Quantities Magnetic dipole tilt Magnetic dipole offset Value 1430 9.56 1350 9.02 1510 10.09 10760 29.46 9.64 0.056 2.49 60330 54180 60268 54364 0.016298 5.69E+26 95.2 37931267.73 8.25E+23 764 10.66 10.17 26.73 134 95 0.47 0.34 0.688 10.46 1.07 0.218 4.70E+28 <1 0.04 Units million km AU million km AU million km AU days years km/s degrees km km km km kg Earth masses km^3/s^2 cubic meters Earth volumes hours hours degrees degrees Kelvin degrees Kelvin
g/cm3 m/s2 Earth gravities gauss Rs3 gauss cm3 degrees Rs
H2, He, CH4, NH3
FOIA 10-JPL-F-00451
204 of 217
Table B.2A: Saturnian Satellites - Orbital Geometry

Distance Satellite or Ring Name D RING (inner edge)
C RING (inner edge) (D ring outer edge)
Distance from Saturn (Saturn radii of 60330 km) 1.11 1.24 1.45 1.52 1.95 2.03 2.21 2.21 2.22 2.26 2.27 2.28 2.31 2.32 2.33 2.35 2.51 2.51 2.73 2.92 3.08 3.15 3.95 4.88 4.88 4.88 6.26 6.27 6.96 8.74 20.25
Orbital Period (days) 0.20 0.24 0.31 0.33 0.48 0.50 0.58 0.58 0.58 0.58 0.60 0.60 0.61 0.62 0.62 0.63 0.69 0.69 0.79 0.87 0.94 0.98 1.37 1.89 1.89 1.89 2.74 2.74 3.21 4.52 15.95
Mean Orbital Velocity (km/sec) 23.81 22.57 20.81 20.31 17.97 17.63 16.87 16.86 16.85 16.67 16.66 16.61 16.50 16.46 16.45 16.37 15.83 15.83 15.17 14.69 14.30 14.14 12.63 11.35 11.35 11.35 10.03 10.02 9.51 8.49 5.57
Orbital Inclination (degrees) 0 0 0 0 0 0 0 0 0 0 0 0.3 0 0 0 0.1 0.34 (var.) 0.14 (var.) 0 0 1.53 0 0.02 1.09 0 0 0.02 0.20 0.00 0.35 0.33
Orbital Eccentricity
from Saturn (km x 1000) 66.97 74.51 87.64 92.00 117.58 122.17 133.41 133.58 133.73 136.53 136.78 137.64 139.35 140.18 140.27 141.70 151.42 151.47 165.00 176.00 185.52 189.87 238.02 294.66 294.66 294.66 377.40 378.40 420.00 527.04 1221.90
0 0 0 0 0 0 0 0 0 0 0 0.0030 0.0024 0 0 0.0042 0.0090 0.0070 0 0 0.0202 0 0.0045 0 0 0 0.0022 0.0050 0 0.0010 0.0292
Maxwell Gap
B RING (inner edge) (C ring outer edge) CASSINI div. (inner edge) B ring (outer edge) A RING (inner edge) (Cassini div. outer edge)
Encke Division (inner edge) Pan Encke Division (outer edge) Keeler Gap (A ring outer edge) Atlas Prometheus F RING (inner edge) F RING (outer edge) Pandora Epimetheus Janus G RING (inner edge) G RING (outer edge) Mimas E RING (approximate inner edge) Enceladus Tethys Telesto Calypso Dione Helene (E ring approx. outer edge) Rhea Titan
Hyperion Iapetus Phoebe
1481.10 3561.30 12952.00
24.55 59.03 214.69
21.28 79.33 550.48
5.06 3.26 1.71
0.43 14.72 175.30
0.1042 0.0283 0.1633
FOIA 10-JPL-F-00451
205 of 217
Table B.2B: Saturnian Satellites - Body Characteristics

Mean Satellite or Ring Name D RING (inner edge)
C RING (inner edge) (D ring outer edge) Maxwell Gap B RING (inner edge) (C ring outer edge) CASSINI div. (inner edge) B ring (outer edge) A RING (inner edge) (Cassini div. outer edge)
Alternate GM (km^3/s^2) ---------------------0.00018 ---------0.00072 0.022 ------0.013 0.0357 0.1284 ------2.5 ---4.9 41.808 0.00048 0.00024 73.156 0.0017 ---154 8978.2 Density (g/cm3) ------------------------------------~0.70 ------~0.70 ~0.70 ~0.67 ------1.17 ---1.24 1.21 ------1.43 ------1.33 1.88 shepherd satellite to F ring with Prometheus irregular; may have been joined with Janus irregular; trades orbits with Epimetheus extremely tenuous & optically thin; seen best with forward-scattered light; has denser core extremely tenuous & optically thin; seen best with forward-scattered light; has denser core giant crater Herschel on leading hemisphere; icy surface; may be covered with water frost E: thought to be sustained by Enceladus; density peaks at Enceladus' orbit complex & varied geological evolution; craters; plains; crustal movements; may be E ring source almost pure ice; large trench Ithaca Chasma (4-5km deep); large 400km crater Odysseus co-orbital with Tethys, 60 ahead (L4) co-orbital with Tethys, 60 behind (L5) cratered leading hemisphere; wispy features on trailing hemisphere co-orbital with Dione 60 ahead (L4) ---largest icy satellite; dark trailing hemisphere; densely cratered equator largest of the satellites; N2, He atmosphere; aerosols, hydrocarbons; surface temp. = 92K; orangish disk; darker n. hemisphere; H2 torus irregular shape; long axis not pointed at Saturn (perhaps due to recent collision); dark surface; chaotic orbit MUCH darker leading hemisphere; ring of dark material near division retrograde orbit; only satellite not tidally locked; ~9hr rotation; dark surface; roughly spherical; may be captured body S5 S6 S2 S3
1980 S13 S13 1980 S25 S14 1980 S26 S15 1980 S3 S11 1980 S1 S10 D: very thin, not well defined; seen best in forwardscattered light C: very complicated grooved region; many ringlets Crepe ring of regular ordering
Radius* (km) 7540 17490 270 25580 4590 14610 325 10 ---35 ---18.5 x 17.2 x 13.5 74 x 50 x 34 90 ---55 x 44 x 31 69 x 55 x 55 97 x 95 x 77 11000 ---209 x 196 x 191 230130 256 x 247 x 245 536 x 528 x 526 15 x 12.5 x 7.5 15 x 8 x 8 560 16 ---764 2575
Observed Features
Names
Discovery
Pioneer 11 1979 C ring: W.C. & G.P Bond & C. W. Tuttle 1850 ---B ring: C. Huygens 1659* division: G. D. Cassini 1675 A ring: C. Huygens 1659*
B: brightest ring; highly complex; thousands of ringlets; ring spokes; redder particles Cassini division: most prominent gap; caused by half-period resonance with Mimas; faint ringlets A: many ringlets & minor gaps; darker & more transparent than B has faint ringlets ---1981 S13 S18
Encke Division (inner edge) Pan Encke Division (outer edge) Keeler Gap (A ring outer edge) Atlas Prometheus F RING (inner edge) F RING (outer edge) Pandora Epimetheus Janus G RING (inner edge) G RING (outer edge) Mimas E RING (approximate inner edge) Enceladus Tethys Telesto Calypso Dione Helene (E ring approx. outer edge) Rhea Titan
J. F. Encke 1837 Voyager 2 1981 (Showalter)
------elongated; may control A ring outer edge shepherd satellite to F ring with Pandora "braided" ring with separate strands; shepherded by Prometheus and Pandora
1980 S28 S17 1980 S27 S16
---Voyager 1 1980 (Terrile)

Voyager 1 1980 (Collins & Carlson)
Pioneer 11 1979
Voyager 1 1980 (Collins & Carlson) Fountain & Larson 1978 Fountain & Larson 1978
detected Pioneer 11 1979 confirmed Voyager 1 1980 detected Pioneer 11 1979 confirmed Voyager 1 1980
S1
Herschel 1789 Voyager 1 1980 Herschel 1789 G. D. Cassini 1684 Smith et al 1980 Smith et al 1980 G. D. Cassini 1684 Lacques & Lecacheaux 1980 ---Cassini 1672 Huygens 1655
S4 Dione B 1980S6 S12
Hyperion Iapetus Phoebe
180 x 140 x 113 718 115 x 110 x 105
0.99 106 0.48
1.40 1.21 0.70
S7 S8 S9
Bond 1848 G. D. Cassini 1671 Pickering 1898
*Some bodies list 3-axis radii when available corresponding to sub-Saturn equatorial radius, along orbit eq. radius, and polar radius. Ring values indicate width ( R) of ring.
FOIA 10-JPL-F-00451
206 of 217
APPENDIX K SATURN SYSTEM MYTHOLOGY Until the middle of the nineteenth century, the satellites of Saturn bore numerical designations only. In 1847, John Herschel proposed that the satellites be named after Saturns brothers and sisters, the Titans and Titanesses. Titans and Titanesses were brothers and sisters not of Saturn, but of Kronos, Saturns Greek counterpart. Hesiod, Homers younger contemporary, gives us the family history of the tribe of the Titans. Using some of Hesiods own words, here is an outline of the story. In the beginning, there was Chaos, and after him came Gaia (the Earth). Gaias first-born was Ouranos (the Sky), the one who matched her every dimension. Gaia lay with Ouranos, and bore him Okeanos, Koios, Krios, Hyperion, Iapetus, Theia, Rhea, Themis, Mnemosyne, Phoebe, and Tethys. Her youngest-born was the devious-devising Kronos, most terrible of her children. Hesiod assigned the name Titans to the enumerated twelve children. Kronos, upon urging from Gaia, attacked his father Ouranos with the sickle she provided. Following the attack, Kronos became the supreme ruler of the world. Kronos took Rhea as his wife. She bore him five children. Remembering the fate of his father, Kronos swallowed each child right after it was born. Zeus was the sixth-born. To save the baby, Rhea tricked her husband into swallowing a stone instead. At some later point, Kronos was made to regurgitate the stone and the five children he swallowed. (Hesiod does not say when and how.) With his siblings help, Zeus initiated a rebellion against Kronos and the Titans. The Titans suffered a defeat in a terrible battle during which all earth was boiling. Zeus imprisoned the defeated gods in Tartaros, a moldy place, at the uttermost edges of the monstrous earth and, along with his Olympian allies, assumed the lordship over the world. Although Kronos rule passed, it was long remembered as the Golden Age of mankind, when people lived as if they were gods, their hearts free from all sorrow, without hard work or pain. Saturn, a Latin deity perhaps associated with farming, received some of the attributes of Kronos. The Romans adopted also the legend of the golden age. In their version, Saturn was the king of Italy in the long forgotten days when, as in the age of Kronos, life was all play and no work. John Herschel gave the name Titan to the moon of Saturn which was discovered first and which happened to be the largest. The other four moons discovered in the seventeenth century he named Iapetus, Rhea, Dione, and Tethys. The minute inner satellites first observed by his father, John Herschel chose to name Enceladus and Mimas. Two satellites found in the nineteenth century received the names of Hyperion and Phoebe. The remaining satellites known at present were discovered in the twentieth century. They include Janus, Pan, Atlas, Prometheus, Pandora, Epimetheus, Telesto, Kalypso, and Helene. Of the eighteen named satellites, only Iapetus, Rhea, Tethys, Hyperion, and Phoebe bear the names of Saturns brothers and sisters, the Titans and Titanesses. A brief description of the meaning of the satellites names is given below. The satellites are listed in the order of the increasing distance from Saturn. Pan (pan) Half-goat, half-human, the Arcadian Pan was worshipped as the patron of shepherds and as the personification of nature. Atlas (AT-less)
FOIA 10-JPL-F-00451
207 of 217
Son of Iapetus. After the defeat of the Titans, Zeus ordered Atlas, at earths uttermost places, near the sweet-singing Hesperides to uphold the vault of the sky. Hesiod refers probably to the Pillars of Hercules, the edge of the world known to the ancient Greeks Prometheus (pro-MEE-thee-us) Hesiod presents Prometheus, son of Iapetus, as an immortal who sided with the mortals and as a prankster who liked to annoy his cousin Zeus. The ultimate annoyance was stealing the far-seen glory of weariless fire and giving it to mankind. For this, Zeus fastened Prometheus to a mountain in the Caucasus, and he let loose on hin the wing-spread eagle, and it was feeding on Prometheus imperishable liver, which by night would grow back to size from which the spread-winged bird had eaten in the daytime. Pandora (pan-DOR-ah) The worlds first woman. Creating Pandora was the punishment Zeus meted out to mankind for the Prometheus brazen acts of disobedience. Pandora arrived equipped with a jar that contained all the misfortunes, curses and plagues. Once the lid was lifted, the evil asserted itself in the world. Hope was the only spirit that stayed there, in the unbreakable closure of the jar, this was the will of the cloud-gathering Zeus. Epimetheus (epp-ee-MEE-thee-us) Son of Iapetus, brother of Prometheus, husband of Pandora. Pictured as weak-minded, he is the one who lifted the lid on the Pandorad jar. Janus (JANE-us) An exalted Roman god, a figure of great antiquity and obscure origin. Always represented as having two faces, one looking forwards, the other backwards, Janus presided over the past, present, and future, over gates, doorways, entrances, and beginnings in general, and over war and peace. At every sacrifice, in every prayer, he was the first god invoked, taking precedence before Jupiter. When war was declared, the portals to the sanctuary of Janus on the Forum were opened. They were shut again on the declaration of peace. During the entire history of Rome, this happened on a handful of occasions only. As the most ancient of kings, Janus is supposed to have given the exiled Kronos a warm welcome in Italy, and to have offered him a share of the royal duties. Mimas (MY-muss) One of the Giants, children of Gaia born of the blood of Ouranos.
Enceladus (n-SELL-uh-duss) One of the Giants, children of Gaia born of the blood of Ouranos. Giants, the last race of Hesiods monsters, were beings of enormous size and invincible strength. Later depictions show them as having hideous faces, bristling beards, hanging hair, skins of wild animals for garments, tree trunks for weapons, and twin serpents for legs. Tethys (TEE-thiss)
FOIA 10-JPL-F-00451
208 of 217
The youngest of Titanesses, Tethys married her brother Okeanos, and bore him three thousand Okeanides, the light-stepping sea-nymphs, and as many Rivers, the murmurously running sons. Telesto (tell-ESS-toe) A daughter of Tethys and Okeanos, an Okeanide. Calypso (kal-IP-so) A daughter of Tethys and Okeanos, an Okeanide. For Homer and other authors, she is a daughter of Atlas. In the course of the Odysseus tortuous return to Ithaca, his ship ran aground on the fabled island of Ogygia, the home of the lonely Kalypso. Odysseus kept her company for seven years, after which he departed on a jointed raft. Dione (die-OH-nee) Dione presents a problem in the genealogy of the Greek gods. To Hesiod, she is a daughter of Tethys and Okeanos, and thus an Okeanide. She is mentioned in a number of other incarnations; for instance as a daughter of Ouranos and Gaia (this would make her a Titaness), or as a daughter of Kronos, or of Atlas. In some localities she was also worshipped as the wife of Zeus (instead of Hera). Helene (heh-LEEN) The divinely beautiful wife of Menelaos, the king of Sparta, Helen (Helene) was abducted by Paris, the son of Priam, the king of Troy. Over Helen the Greeks fought the all-destructive Trojan War. Rhea (ree-uh) A Titaness, married to her brother Kronos. Titan (TIE-tan) Not a single deity, but a generic name for the children of Ouranos and Gaia. Hyperion (high-PEER-ee-on) The fourth-born Titan, Hyperion took for a wife his sister Theia. Theia brought forth great Helios and shining Selene, the Sun and Moon, and Eos the Dawn who lights all earthly creatures and the immortal gods who hold the white heaven. Solar and lunar deities, dominant in the affairs of other ancient civilizations, played a minor part in the religious life of ancient Greels. Iapetus (eye-AP-eh-tuss) Iapetus, a Titan, took Klymene, his niece, the light-stepping daughter of Okeanos, to be his wife. Their sons were Atlas, Prometheus, and Epimetheus. Phoebe (FEE-bee) Phoebe, a Titanness, bore to her brother Koios the goddess Leto, the gentlest of all who are on Olympus. Leto, who had lain in the arms of Zeus, bore Apollo and Artemis, children more delightful than all the other Olympians. In later antiquity, Phoebe was honored as the goddess of the Moon.
L. Roth, 8 Aug 96
FOIA 10-JPL-F-00451
209 of 217
FOIA 10-JPL-F-00451
210 of 217
APPENDIX L CASSINI AND HUYGENS, THE SCIENTISTS

The seventeenth century appears to us as an epoch of gallant manners, lavish costumes, comical wigs, and incomprehensible wars -- all without much relevance to the present. Yet the seventeenth century, despite its remoteness and extravagance, was a time of towering significance. Modern science was born in the seventeenth century and it was in the seventeenth century that mankind's view of the cosmos underwent the most drastic change since the beginning of recorded history. Giovanni Domenico Cassini (1625-1712) and Christiaan Huygens (1629-1695) were two of the learned men of that tumultuous period who, by showing to the incredulous public the new wonders of the sky, helped to usher in the age of science and alter our perception of the world. Both Cassini and Huygens came from well-to-do families -- one in Italy, the other in Holland, both received the best education available, both were extraordinarily industrious, and both did most of their lives' work in Paris, as members of the Royal Academy of Sciences established in 1666 by Louis XIV, the fabled Sun King. Huygens earned the invitation to join the Academy and the associated Royal Observatory as a result of having discovered Titan (the first of a number of moons of Saturn to be discovered subsequently) and the rings of Saturn. Before joining the Academy, Huygens also invented the pendulum clock, the first accurate timekeeping device. While still in Italy, Cassini gained fame by having measured the rotation periods of Jupiter and Mars, and by virtue of his extensive observations of the motions of the moons of Jupiter. (The moons of Jupiter were discovered by Galileo some fifty years earlier.) At Paris, Cassini extended his meticulously precise observations to Saturn, discovering four more moons -- Iapetus, Rhea, Dione, and Tethys, and also discovering a gap in the rings of Saturn, later named the Cassini Division. Towards the end of his life, Huygens returned to Holland where he continued to do pioneering work in mechanics and optics. Cassini stayed at the Paris Observatory where, in addition to conducting regular astronomical observations, he led the development of the new arts of geodesy and map-making.
FOIA 10-JPL-F-00451
211 of 217
Giovanni Domenico Cassini
Christiaan Huygens
FOIA 10-JPL-F-00451
212 of 217
APPENDIX O PENDING ACTIVITIES LISTED IN THE FINAL VERSION OF THE CASSINI ORBITER CRUISE ACTIVITY HANDBOOK (699-280) The purpose of this appendix was to list those activities which were in the final version of the Cassini Orbiter Cruise Activity Handbook (OCAH; Project ID 699-280; Rev. E, 11 Feb. 2000) and which had not been completed (i.e., were ongoing or not yet executed) as of the date of this Mission Plan. By the time Rev N was released, those activities consisted almost entirely of maintainance activities. Therefore this Appendix is no longer being maintained here. If descriptions of maintenance activities are desired, they can be found in the retired OCAH. Descriptions of new science or engineering activities for the Quiet Cruise and Space Science subphases, can be found in the Scoping Summaries for each subphase or Project Briefing packages for each sequence.
1
213 of 217
FOIA 10-JPL-F-00451
214 of 217
MISSION PLAN ACRONYM LIST

AACS ACP AFC AGC ANT ARIA ASE ATLO BER BIU BLF BWG C3 CABL CAPS CAR CCAS CCAM CDA CDB CDS CDU CHEMS CIRS COCAH CPF DDB DFPW DISR DMR DMWF DOR DOM DSM DSN DSS DST DWE EDR EEIS EFC EGA EGSE EOM EOP EPS EPS EPS ERT ESB ESS ETLA ETR EVEEGA Attitude and Articulation Control Subsystem Aerosol Collector and Pyrolyzer AACS Flight Computer RFS Automatic Gain Control ANTenna subsystem Advanced Range Instrumentation Aircraft Airborne Support Equipment Assembly, Test, and Launch Operations Bit Error Rate Bus Interface Unit Best Lock Frequency Beam Wave Guide Trajectory Energy parameter = twice the injection energy per unit mass = V2 CABLing subsystem Cassini Plasma Spectrometer Cruise Activity Request Cape Canaveral Air Station Collision and Contamination Avoidance Maneuver Cosmic Dust Analyzer Cassini Central Database Command and Data Subsystem Command Detector Unit Change-Energy-Mass Spectrometer Composite Infrared Spectrometer Cassini Orbiter Cruise Activity Handbook Command Packet File Descent Data Broadcast Downlink Fields, Particles and Waves Descent Imager/Spectral Radiometer Detailed Mission Requirements Desired Memory Word File Differenced One-way Ranging Distributed Object Manager Deep Space Maneuver Deep Space Network Digital Subsystem Deep Space Transponder Doppler Wind Experiment Engineering Data Record End-to-End Information System Engineering Flight Computer Engine Gimbal Actuator Probe Electrical Ground Support Equipment End of Mission End of Project Earth-Probe-Sun Earth-S/C-Sun Electronic Packaging Subsystem Earth Receive Time Earth Swingby Energy Storage Subsystem Extended Three-Letter Acronym Eastern Test Range Earth-Venus-Earth-Earth Gravity Assist iii
215 of 217
FGM FIFO FOV FPP FPW FSO GCMS GDS GSE HASI HEF HGA HPOC HSS IFR IIP INCA INMS IRD IRU ISS ITL IUS IVP JGA Ka-band L LEM LEMMS LeRC LGA LGA 1 MAG MAPS ME MECO MES MIMI MO&DA MOP MPVT MRR MRS MSC MSO NAC NAIF ODM ODR ODT OPNAV OPTG ORS PCDU PDB PDRS PEF PLF
Flux Gate Magnetometer First-In, First-Out Field of View Fields and Particles Pallet Fields, Particles, and Waves Flight System Operations Gas Chromatograph and Mass Spectrometer Ground Data System Ground Support Equipement Huygens Atmospheric Structure Instrument High Efficiency High Gain Antenna Huygens Probe Operations Centre High Speed Simulator In Flight Re-targetting Instantaneous Impact Point Ion and Neutral Camera Ion and Neutral Mass Spectrometer Interface Requirements Document Inertial Reference Unit Imaging Science Subsystem Integration and Test Laboratory Inertial Upper Stage Inertial Vector Propagator Jupiter Gravity Assist Radio frequencies between 26 Ghz and 40 GHz Launch Lower Equipment Module Low Energy Magnetosphere Measurement System Lewis Research Center Low Gain Antennas Low Gain Antenna 1 Magnetometer Magnetosphere, Atmosphere, Plasma Science Main Engines Main Engine Cut Off Main Engine Start Magnetosphere Imaging Instrument Mission Operations and Data Analysis Maximum Operating Pressure Mission Planning Virtual Team Mission Requirements Request Minimum Residual Shutdown Magnetic Search Coils Mission & Science Operations Narrow Angle Camera Navigation Ancillary Information Facility Orbit Deflection Maneuver Original Data Record Orbiter Delay Time Optical Navigation Orbit Propogation and Timing Geometry File Optical Remote Sensing Power Control Distribution Unit Project Data Base Probe Data Relay Subsystem Predicted Event File Payload Fairing iv
216 of 217
PMA PMC PMD PMS PPS PRM PSA PSE PSG PSU RCS REU RFE RFES RFI RFIS RFS RFSTLC RHU RJ RS ROM RPC RPWS RSP RSS RTG RUSO RWA S/C SAF SAMD SAR SASF S-band SCAS SCET SCLK SCO SED SEF SEQGEN SEQTRAN SFDU SHO SIS SIT SKR SNR SOE SOI SOPC SPC SPE SPICE SPK SRMU SRU
Propulsion Module Assembly Probe Mission Complete Propellant Management Device Propulsion Module Subsystem Power and Pyrotechnics Subsystem Probe Release Maneuver Probe Support Avionics Probe Support Equipment Project Science Group Pyro Switching Unit Reaction Control Subsystem Remote Engineering Unit Radio Frequency Electronics Radio Frequency Electronics Subsystem Radio Frequency Interference Radio Frequency Instrument Subsystem Radio Frequency Subsystem RFS Tracking Loop Capacitor RadioIsotope Heater Units Jupiter Radii Saturn Radii Read-Only-Memory Ring Plane Crossing Radio and Plasma Wave Science Remote Sensing Pallet Radio Science Subsystem Radioisotope Thermoelectric Generator Receiver Ultra Stable Oscillator Reaction Wheel Assembly Spacecraft Spacecraft Assembly Facility Science and Mission Design Synthetic Aperture Radar S/C Activity Sequence File Radio frequencies between 2 Ghz and 4 GHz Science Calibration Subsystem Spacecraft Event Time Spacecraft Clock Spacecraft Office (in the MSO) Saturn Electrostatic Discharges Spacecraft Events File Sequence Generator Sequence Translator Standard Format Data Unit Sufficiently High Orbit Software Interface Specification Science Integrated Timeline Saturn Kilometric Radiation Signal-to-Noise Ratio Sequence of Events Saturn Orbit Insertion Science Operations and Planning Computer Signal Processing Center Sun-Probe-Earth Angle Spacecraft, Planet, Instrument C-Matrix Ephemeris (Kernel) Spacecraft and Planet ephemeris data file (Kernel) Solid Rocket Motor Upgrade Stellar Reference Unit v
217 of 217
SSA SSD SSE SSEF SSP SSR STD STRU SWG TCA TCM TCP/IP TCS TDRSS TDS TEMP TIP TLA TLM TMC TOF TOL TP TPM TSS TTACS TUSO TV TWT TWTA UDMH UDT UEM ULO USAF USO UT1 UTC UVIS VEEGA VSHM VVEJGA VIMS VLBI V/S HM WAC X-band XMTR X-TWTA ZLP
Sun Sensor Assembly Solid State Detector Sun Sensor Electronics Spacecraft Significant Events File Surface Science Package Solid State Recorder Standard DSN Station STRUcture subsystem Scenarios Working Group Time of Closest Approach Trajectory Correction Maneuver Transmission Control Protocol / Internet Protocol Telecommunications Subsystem Tracking and Data Relay Satellite System Telemetry Delivery Subsystem Temperature Control Subsystem Target Interface Point Three-Letter Acronym Telemetry Target Motion Compensation Time Of Flight Time Ordered Listing Time of Periapsis Telemetry Propulsion Module Telecommunications Subsystem Telemetry, Test, and Command System Transmitter Ultra Stable Oscillator Thermal Vacuum Travelling Wave Tube Traveling Wave Tube Amplifier Unsymmetrical Di-Methyl Hydrazine Universal Daylight Time Upper Equipment Module Uplink Operations United States Air Force Ultra-Stable Oscillator Universal Time Universal Time Coordinated Ultraviolet Imaging Spectrograph Venus-Earth-Earth Gravity Assist Vector Scalar Helium Magnetometer Venus-Venus-Earth-Jupiter Gravity Assist Visible and Infrared Mapping Spectrometer Very Long Baseline Interferometry Vector/Scalar Helium Magnetmeter Wide Angle Camera Radio frequencies between 8 Ghz and 12 GHz Transmitter X-band Travelling Wave Tube Amplifier Zero Length Packet
vi

Cassine MissionPlan - RevN

Uploaded by

Copyright:

Available Formats

Cassine MissionPlan - RevN

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cassine MissionPlan - RevN

Uploaded by

Copyright:

Available Formats

1 of 217

Posted Courtesy of the NASA FOIA program

CASSINI PROJECT DOCUMENT CHANGE NOTICE

DOCUMENT CHANGE ID: Revision N PAGE 1 OF 1 DATE: 10 May 2002

[Include document approval authorities and document custodian]

list maintained by Mission Planning

Dave Seal, Mission Planning Lead Custodian: Jim Frautnick

Posted Courtesy of the NASA FOIA program

Posted Courtesy of the NASA FOIA program

1997 PHASES SUBPHASES

Launch Sequence TCM1 Venus 1

EVENTS MANEUVERS PERIHELION/ APHELION

DOWNLINK DATA RATE CAPABILITY

(log scale) 248 k 142 k 82 k 35 k 22 k

DSN COVERAGE REQUESTED (passes/week)

DAYS FROM LAUNCH

* Refer to Appendix J for more information about data rate capability.

Indicates actual instrument checkout window.

Figure 2.1: Cassini Cruise Segment Timeline

Posted Courtesy of the NASA FOIA program

Posted Courtesy of the NASA FOIA program

Posted Courtesy of the NASA FOIA program

Posted Courtesy of the NASA FOIA program

VENUS 2 FLYBY 24 JUN 1999

DEEP-SPACE MANEUVER DEC 1998 VENUS 1 FLYBY 26 APR 1998

EARTH FLYBY 18 AUG 1999

TICKS EVERY 30 DAYS

Figure 2.3 Cassini Cruise Trajectory

VENUS 1 SWINGBY 26 APR 1998 VENUS 2 SWINGBY 24 JUN 1999

SATURN ARRIVAL 1 JUL 2004

DEEP SPACE MANEUVER 3 DEC 1998 JUPITER FLYBY 30 DEC 2000

LAUNCH 15 OCT 1997 EARTH SWINGBY 18 AUG 1999

PERIHELIA 27 MAR 1998 0.67 AU 29 JUN 1999 0.72 AU

Figure 2.4 CASSINI CRUISE TRAJECTORY

Figure 2.6 Tour Petal Plot - Side View 2-10

Figure 2.7 Titan Ground Tracks

Posted Courtesy of the NASA FOIA program

DUSK LTST =18:00 = 6 PM

View From Saturn North Pole MIDNIGHT / TAIL LTST = 0:00 = 12 AM

Figure 2.8 Definition of Orbit Orientation

S/C Orbit Saturn

n complete Titan revs per m complete s/c revs where n, m = 1, 2, 3, ...

Titan at current encounter Titan at next encounter

Figure 2.9 Definition of Resonant Transfer

Titan at current encounter Sample Low Inclination Transfer

Table 2.3 Tour Segment Characteristics

Figure 2.12 Tour Segment SOI-Tc Side View

Figure 2.14 Tour Segment Tc-14TI (Tc-T7) Side View

Titan location first 9 inbound flybys i=25 , period=16 d i=15 , period= 24 d

180 Transfer Orb i=59

Posted Courtesy of the NASA FOIA program

Posted Courtesy of the NASA FOIA program

ATI-3 Titan Ascending Descending ATI+3

3TI-3 Titan Titan Titan Ascending Enceladus 3TI+3 Descending

Posted Courtesy of the NASA FOIA program

~APO 4EN-3 Enceladus Ascending Tethys 4EN+3 Descending

~APO 5TI-3 Enceladus Ascending Titan Descending 5TI+3

P=16.0 d, i=7.0, r=38.0 Rs, Phase=72 deg, LTST=4:50 Duration = 35 days

Ascending Ring Enceladus Ring Saturn Saturn Ring Ring Descending