Search NASA⌕ Search

SEARCH · Search NASA

Results for “Cassini Huygens Saturn”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS2002

The Cassini/Huygens Mission to Saturn and Titan

The Cassini/Huygens mission is a joint endeavor between NASA, the EuropeanSpace Agency, and the Italian Space Agency to send a spacecraft to perform an extensive exploration of the Saturnian system, including an atmospheric probe to go to the surface of Titan. The spacecraft was launched on October 15, 1997, and now has completed five years of its nearly seven year journey to Saturn. The cruise period has been a relatively passive time for the spacecraft, but an intensely busy one for the flight team. There is now less than two years to go until arrival at Saturn, and a significant portion of the effort deliberately planned for the post-launch period remains to be completed. Ground activities include the development of flight software, ground software, and science observation plans in order to be prepared to operate the mission after arrival at Saturn. This paper provides an update to the mission status and progress over the past year.

Cassini Huygens Saturn Titan↗
NASA NTRS2000

The Cassini/Huyegens Mission to Saturn and Titan

This paper summarizes the principal accomplishments of the Cassini/Huygens mission over the past year, which include a complete reload of the flight software on the spacecraft, including that of most of the orbiter science instruments, the final definition of the exact orbital tour to be flown at Saturn, and considerable progress in designing the sequence of science observations to be made in the tour.

Cassini Huygens Saturn Titan↗
NASA NTRS1999

The Cassini/Huygens Mission to Saturn

This paper characterizes the performance of the Cassini/Huygens spacecraft during its first two years of flight, up through the Earth flyby.

Cassini↗
NASA NTRS2005

Cassini orbit determination performance during the first eight orbits of the Saturn satellite tour

From June 2004 through July 2005, the Cassini/Huygens spacecraft has executed nine successful close-targeted encounters by three major satellites of the Saturnian system. Current results show that orbit determination has met design requirements for targeting encounters, Hugens descent, and predicting science instrument pointing for targetd satellite encounters. This paper compares actual target dispersion against, the predicte tour covariance analyses.

navigation↗
NASA NTRS2003

The Cassini/Huygens mission to Saturn

This paper provides an overview of the mission but focuses primarily on the activities over the past year in preparation for Saturn arrival and beginning the scientific observations to be made in orbit. Details are provided on the completion, validation, and uplink of new on-board flight software, development and testing of the sequences to be used for orbit insertion and relay of the data stream from the Huygens probe as it descends through the atmosphere of Titan, and design and preparation of the science sequences to be performed by the orbiter.

Huygens↗
NASA NTRS2017

The Saturn System Through the Eyes of Cassini

More than 400 years ago, Galileo Galilei trained his homemade telescope on the night sky and observed that Saturn had two objects closely related to the planet extending on either side. At the time, in 1610, Galileo declared them to be moons. A few decades later, Saturn moon science accelerated at a dizzying pace. Christiaan Huygens first observed Saturn's largest moon Titan in 1655 and was the first to describe the extended moon-like features at Saturn as a disk of material sounding the planet. From 1671 to 1674, Giovanni Cassini discovered the moons lapetus, Rhea, Dione and Tethys. In 1675, Cassini discovered the gap in Saturn's rings that we now know as the Cassini Division. In the space age, before the Cassini-Huygens mission, we had only hints of the discoveries awaiting us at Saturn. Pioneer 11 and Voyagers 1 and 2 conducted flybys decades ago. But these quick encounters didn't allow time for more extensive research. NASA and the European Space Agency created a partnership to orbit a Saturn orbiter (Cassini) and a lander (Huygens) on Titan. Like its namesakes, the Cassini-Huygens mission not only discovered previously unknown moons, but it also helped us understand the science behind their formation, their interactions with the rings, and how truly diverse they are. The Cassini-Huygens mission revolutionized what we know about the Saturn system. The rings of Saturn, the moons, and the planet itself offer irresistible and inexhaustible subjects for intense study, and Cassini-Huygens did not disappoint. The Saturnian system proved to be a rich ground for science exploration and discoveries, and Cassini has been nothing short of a discovery machine. At the time Cassini plunged into Saturn at the end of its mission, it had observed the planet for a little less than half of a Saturn year. But it also orbited the gas giant 293 times, forever changing our understanding of the Saturn system and yielding tremendous insight for understanding the entire Solar System.

Green, James↗
NASA NTRS2006

Cassini-Huygens maneuver automation for navigation

Many times during the Cassini-Huygens mission to Saturn, propulsive maneuvers must be spaced so closely together that there isn't enough time or workforce to execute the maneuver-related software manually, one subsystem at a time. Automation is required. Automating the maneuver design process has involved close cooperation between teams. We present the contribution from the Navigation system. In scope, this includes trajectory propagation and search, generation of ephemerides, general tasks such as email notification and file transfer, and presentation materials. The software has been used to help understand maneuver optimization results, Huygens probe delivery statistics, and Saturn ring-plane crossing geometry. The Maneuver Automation Software (MAS), developed for the Cassini-Huygens program enables frequent maneuvers by handling mundane tasks such as creation of deliverable files, file delivery, generation and transmission of email announcements, generation of presentation material and other supporting documentation. By hand, these tasks took up hours, if not days, of work for each maneuver. Automated, these tasks may be completed in under an hour. During the cruise trajectory the spacing of maneuvers was such that development of a maneuver design could span about a month, involving several other processes in addition to that described, above. Often, about the last five days of this process covered the generation of a final design using an updated orbit-determination estimate. To support the tour trajectory, the orbit determination data cut-off of five days before the maneuver needed to be reduced to approximately one day and the whole maneuver development process needed to be reduced to less than a week..

propulsion maneuvers↗
NASA NTRS1996

Cassini / Huygens Science Instruments

The Cassini spacecraft will bring eighteen scientific instruments to Saturn. After it is inserted into Saturn orbit, it will seperate into a Saturn Orbiter and an atmospheric probe, called Huygens, which will descend to the surface of Titan.

Cassini↗
NASA NTRS2008

Preparing Cassini Uplink Operations for Extended Mission

The Cassini-Huygens Mission to Saturn and Titan, a joint venture between the National Aeronautics and Space Administration, the European Space Agency, and the Italian Space Agency, is conducting a four-year, prime mission exploring the Saturnian system, including its atmosphere, rings, magnetosphere, moons and icy satellites. Launched in 1997, Cassini began its prime mission in 2004. Cassini is now preparing for a new era, a two-year extended mission to revisit many of the highlights and new discoveries made during the prime mission. Because of the light time delay from Earth to Saturn, and the time needed to coordinate the complicated science and engineering activities that take place on the spacecraft, commanding on Cassini is done in approximately 40-day intervals known as sequences. The Cassini Uplink Operations team is responsible for the final development and validation of the pointing profile and instrument and spacecraft commands that are contained in a sequence. During this final analysis prior to uplink to the spacecraft, thorough and exact evaluation is necessary to ensure there are no mistakes during commanding. In order to perform this evaluation, complete and refined processes and procedures are fundamental. The Uplink Operations team is also responsible for anomaly response during sequence execution, a process in which critical decisions often are made in real-time. Recent anomalies on other spacecraft missions have highlighted two major risks in the operations process: (1) personnel turnover and the retirement of critical knowledge and (2) aging, outdated operations procedures. If other missions are a good barometer, the Cassini extended mission will be presented with a high personnel turnover of the Cassini flight team, which could lead to a loss of expertise that has been essential to the success of the prime mission. In order to prepare the Cassini Uplink Operations Team for this possibility and to continue to develop and operate safe science and engineering sequences, a review and major update of the current documentation and operations procedures was needed. This paper will address the changes made to extended mission sequence generation processes primarily due to new restrictions in spacecraft operating capability and lessons learned from prime mission. In addition, it will address the state of the prime mission operations procedures, the philosophy changes and updates that were made to those procedures in response to process improvement, and the validation of those new procedures through the training of current and new personnel. And lastly, it will address the lessons learned throughout prime mission and how the Uplink Operations team chose to incorporate those lessons into the working documentation and team knowledge. This incorporation was necessary to facilitate the success of the extended mission with potentially all new personnel at some point prior to the end of the mission.

Maxwell, Jennifer L.↗