Energetic Oxygen and Sulfur Charge States in the Outer Jovian Magnetosphere: Insights From the Cassini Jupiter Flyby
Explore the source record for details and available documents.
R. C. Allen↗
SEARCH · Search NASA
Results for “Flybys”
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.
The second-degree gravity coefficients of Phobos from two Mars Express flybys
Explore the source record for details and available documents.
X Yang↗
Titan's Variable Ionosphere During the T118 and T119 Cassini Flybys
Explore the source record for details and available documents.
N. J. T. Edberg↗
Secular dynamics of hierarchical multiple systems composed of nested binaries, with an arbitrary number of bodies and arbitrary hierarchical structure – II. External perturbations: flybys and supernovae
Explore the source record for details and available documents.
Adrian S Hamers↗
Using Gravity Assists in the Earth-moon System as a Gateway to the Solar System
For spacecraft departing the Earth - Moon system, lunar flybys can significantly increase the hype rbolic escape energy (C3, in km 2 /sec 2 ) for a modest increase in flight time. Within ~2 months, lunar flybys can produce a C3 of ~2. Over 4 - 6 months, lunar flybys alone can increase the C3 to ~4.5, or they can provide for additional periapsis burns to increase the C3 from ~2 -3 to 10 or more, suitable for planetary missions. A lunar flyby departure can be followed by additional ∆ -V (such as that efficiently provided by a low thrust system, eg. Solar Electric Propulsion (SEP)) to raise the Earth - relative velocity (at a ratio of more than 2:1) before a subsequent Earth flyby, which redirects that velocity to a more di stant target, all within not much more than a year. This paper describes the applicability of lunar flybys for different flight times and propulsi on systems, and illustrates this with instances of past usage and future possibilities. Examples discussed i nclude ISEE - 3, Nozomi, STEREO, 2018 Mars studies (which showed an 8% payload increase), and missions to Near Earth Objects (NEOs). In addition, the options for the achieving the initial lunar flyby are systematically discussed, with a view towards their p ractical use with in a compact launch period. In particular, we show that launches to geosynchronous transfer orbit (GTO) as a secondary payload provide a feasible means of obtaining a lunar flyby for an acceptable cost, even for SEP systems that cannot ea sily deliver large ∆ - Vs at periapsis. Taken together, these results comprise a myriad of options for increasing the mission performance, by the efficient use of lunar flybys within an acceptable extension of the flight time.
lunar fly-bys↗
Using Gravity Assists in the Earth-moon System as a Gateway to the Solar System
For spacecraft departing the Earth - Moon system, lunar flybys can significantly increase the hyperbolic escape energy (C3, in km (exp 2) /sec (exp 2) ) for a modest increase in flight time. Within approx 2 months, lunar flybys can produce a C3 of approx 2. Over 4 - 6 months, lunar flybys alone can increase the C3 to approx 4.5, or they can provide for additional periapsis burns to increase the C3 from approx 2 -3 to 10 or more, suitable for planetary missions. A lunar flyby departure can be followed by additional delta -V (such as that efficiently provided by a low thrust system, eg. Solar Electric Propulsion (SEP)) to raise the Earth - relative velocity (at a ratio of more than 2:1) before a subsequent Earth flyby, which redirects that velocity to a more distant target, all within not more than a year. This paper describes the applicability of lunar flybys for different flight times and propulsion systems, and illustrates this with instances of past usage and future possibilities. Examples discussed include ISEE-3, Nozomi, STEREO, 2018 Mars studies (which showed an 8% payload increase), and missions to Near Earth Objects (NEOs). In addition, the options for the achieving the initial lunar flyby are systematically discussed, with a view towards their practical use within a compact launch period. In particular, we show that launches to geosynchronous transfer orbit (GTO) as a secondary payload provide a feasible means of obtaining a lunar flyby for an acceptable cost, even for SEP systems that cannot easily deliver large delta-Vs at periapsis. Taken together, these results comprise a myriad of options for increasing the mission performance, by the efficient use of lunar flybys within an acceptable extension of the flight time.
Solar Electric Propulsion (SEP)↗
Resolution of Orbit Determination Prediction Instabilities at Titan During Cassini's Solstice Mission
The Cassini spacecraft has been in orbit about Saturn since 2004. Exploration of the Saturn system is driven by gravitational flybys of the moon Titan which alter the spacecraft trajectory. The Cassini Navigation Team receives regular updates to the Saturn satellites ephemeris from JPL's Solar System Dynamics group. The difference between subsequent ephemeris deliveries can be hundreds of meters in the position of Titan at the time of a flyby. Errors in Titan's position propagate downstream to the next flyby through the estimated spacecraft trajectory. Prior to 2013, the Cassini Orbit Determination Team estimated the Saturn satellite ephemeris parameters and used the a posteriori states and covariance of an operations arc as a priori inputs to subsequent estimation arcs. Since 2013, the OD Team has only been considering errors in the ephemeris and not estimating a correction to the satellite positions. The T119 Titan flyby exhibited a 3D miss distance of 2.44 km and the following T120 flyby yielded a smaller miss of 1.06 km at the 2.9s error level. These discrepancies between pre-flyby prediction and post-flyby trajectory reconstruction were due to errors in the Titan ephemeris. In order to improve the targeting of Titan in future flybys, the team restarted the satellite ephemeris estimation process for orbit determination solutions. Subsequent flybys had target misses of less than 1 km at the sub-3 error level. This paper describes the method of scaling the a priori satellite ephemeris covariance in the orbit determination process to allow larger corrections to the satellite system and improve the prediction of the spacecraft’s Titan-relative position at the time of encounters.
Boone, Dylan↗
Science Benefits of Onboard Spacecraft Navigation
Primitive bodies (asteroids and comets), which have remained relatively unaltered since their formation, are important targets for scientific missions that seek to understand the evolution of the solar system. Often the first step is to fly by these bodies with robotic spacecraft. The key to maximizing data returns from these flybys is to determine the spacecraft trajectory relative to the target body-in short, navigate the spacecraft- with sufficient accuracy so that the target is guaranteed to be in the instruments' field of view. The most powerful navigation data in these scenarios are images taken by the spacecraft of the target against a known star field (onboard astrometry). Traditionally, the relative trajectory of the spacecraft must be estimated hours to days in advance using images collected by the spacecraft. This is because of (1)!the long round-trip light times between the spacecraft and the Earth and (2)!the time needed to downlink and process navigation data on the ground, make decisions based on the result, and build and uplink instrument pointing sequences from the results. The light time and processing time compromise navigation accuracy considerably, because there is not enough time to use more accurate data collected closer to the target-such data are more accurate because the angular capability of the onboard astrometry is essentially constant as the distance to the target decreases, resulting in better "plane-of- sky" knowledge of the target. Excellent examples of these timing limitations are high-speed comet encounters. Comets are difficult to observe up close; their orbits often limit scientists to brief, rapid flybys, and their coma further restricts viewers from seeing the nucleus in any detail, unless they can view the nucleus at close range. Comet nuclei details are typically discernable for much shorter durations than the roundtrip light time to Earth, so robotic spacecraft must be able to perform onboard navigation. This onboard navigation can be accomplished through a self- contained system that by eliminating light time restrictions dramatically improves the relative trajectory knowledge and control and subsequently increases the amount of quality data collected. Flybys are one-time events, so the system's underlying algorithms and software must be extremely robust. The autonomous software must also be able to cope with the unknown size, shape, and orientation of the previously unseen comet nucleus. Furthermore, algorithms must be reliable in the presence of imperfections and/or damage to onboard cameras accrued after many years of deep-space operations. The AutoNav operational flight software packages, developed by scientists at the Jet Propulsion Laboratory (JPL) under contract with NASA, meet all these requirements. They have been directly responsible for the successful encounters on all of NASA's close-up comet-imaging missions (see Figure !1). AutoNav is the only system to date that has autonomously tracked comet nuclei during encounters and performed autonomous interplanetary navigation. AutoNav has enabled five cometary flyby missions (Table!1) residing on four NASA spacecraft provided by three different spacecraft builders. Using this software, missions were able to process a combined total of nearly 1000 images previously unseen by humans. By eliminating the need to navigate spacecraft from Earth, the accuracy gained by AutoNav during flybys compared to ground-based navigation is about 1!order of magnitude in targeting and 2!orders of magnitude in time of flight. These benefits ensure that pointing errors do not compromise data gathered during flybys. In addition, these benefits can be applied to flybys of other solar system objects, flybys at much slower relative velocities, mosaic imaging campaigns, and other proximity activities (e.g., orbiting, hovering, and descent/ascent).
Autonomy↗
Material capture by double lunar gravity assist
The equations yielding the performance of a single lunar flyby in removing incoming hyperbolic excess velocity to capture payloads on interplanetary trajectories are briefly derived. The impossibility of using a single lunar flyby to capture a body entering the earth-moon system with a hyperbolic velocity in excess of about 1.9 km/s is discussed, and a method of using a double flyby of the moon to significantly improve this performance is developed. The equations for achieving a double lunar flyby are derived by solving the orbital equations and Lambert's problem both for the incoming trajectory in the plane of the moon's orbit and for arbitrary declination. For the in-plane case it is shown that the maximum removable hyperbolic excess velocity is 2.2687 km/s. For the inclined case, it is shown that the use of a double lunar flyby allows capture for declinations in excess of 54 degrees, and that for declinations less than 38 degrees the double lunar flyby offers better performance than the single lunar flyby.
Ross, D. J.↗
Cassini Titan Science Integration: Getting a 'Jumpstart' on the Process
The Cassini spacecraft has been in orbit for five years, returning a wealth of scientific data from Titan and the Saturn system. The mission is a cooperative undertaking between NASA, ESA and the Italian Space Agency and the project is currently planning for a second extension of the mission. The Cassini Solstice Mission (CSM) will extend the mission's lifetime until Saturn's northern summer solstice in 2017. The Titan Orbiter Science Team (TOST) has the task of integrating the science observations for all 126 targeted Titan flybys (44 in the Prime Mission, 26 in the first extension (Equinox Mission), and 56 in the second extension (Solstice Mission)) contained in the chosen trajectory. Cassini science instruments are body-fixed with limited ability to articulate; thus, the spacecraft pointing during the flybys must be allocated among the instruments to accomplish the mission's science goals. The science that can be accomplished on each Titan flyby also critically depends on the closest approach altitude, which is in turn determined by the attitude, but changing the altitude impacts the overall trajectory for the Solstice Mission. During the Prime and Extended missions, TOST has learned that the best way to achieve Cassini's Titan science goals is via a 'jumpstart' process prior to final delivery of the trajectory. The jumpstart is driven by the desire to balance Titan science across the entire set of flybys during the CSM, and to influence any changes (tweaks) to the flyby altitudes. By the end of the jumpstart, TOST produces Master Timelines for each flyby, identifying each flyby's prime science observations and allocating control of the spacecraft attitude to specific instrument teams. In addition, developing timelines early, while the science and operations teams are still fully funded, decreases the future workload in integration and implementation.
Steadman, Kimberly B.↗
Estimation and Modeling of Enceladus Plume Jet Density Using Reaction Wheel Control Data
The Cassini spacecraft was launched on October 15, 1997 by a Titan 4B launch vehicle. After an interplanetary cruise of almost seven years, it arrived at Saturn on June 30, 2004. In 2005, Cassini completed three flybys of Enceladus, a small, icy satellite of Saturn. Observations made during these flybys confirmed the existence of a water vapor plume in the south polar region of Enceladus. Five additional low-altitude flybys of Enceladus were successfully executed in 2008-9 to better characterize these watery plumes. The first of these flybys was the 50-km Enceladus-3 (E3) flyby executed on March 12, 2008. During the E3 flyby, the spacecraft attitude was controlled by a set of three reaction wheels. During the flyby, multiple plume jets imparted disturbance torque on the spacecraft resulting in small but visible attitude control errors. Using the known and unique transfer function between the disturbance torque and the attitude control error, the collected attitude control error telemetry could be used to estimate the disturbance torque. The effectiveness of this methodology is confirmed using the E3 telemetry data. Given good estimates of spacecraft's projected area, center of pressure location, and spacecraft velocity, the time history of the Enceladus plume density is reconstructed accordingly. The 1 sigma uncertainty of the estimated density is 7.7%. Next, we modeled the density due to each plume jet as a function of both the radial and angular distances of the spacecraft from the plume source. We also conjecture that the total plume density experienced by the spacecraft is the sum of the component plume densities. By comparing the time history of the reconstructed E3 plume density with that predicted by the plume model, values of the plume model parameters are determined. Results obtained are compared with those determined by other Cassini science instruments.
Lee, Allan Y.↗
Estimation and Modeling of Enceladus Plume Jet Density Using Reaction Wheel Control Data
The Cassini spacecraft was launched on October 15, 1997 by a Titan 4B launch vehicle. After an interplanetary cruise of almost seven years, it arrived at Saturn on June 30, 2004. In 2005, Cassini completed three flybys of Enceladus, a small, icy satellite of Saturn. Observations made during these flybys confirmed the existence of a water vapor plume in the south polar region of Enceladus. Five additional low-altitude flybys of Enceladus were successfully executed in 2008-9 to better characterize these watery plumes. The first of these flybys was the 50-km Enceladus-3 (E3) flyby executed on March 12, 2008. During the E3 flyby, the spacecraft attitude was controlled by a set of three reaction wheels. During the flyby, multiple plume jets imparted disturbance torque on the spacecraft resulting in small but visible attitude control errors. Using the known and unique transfer function between the disturbance torque and the attitude control error, the collected attitude control error telemetry could be used to estimate the disturbance torque. The effectiveness of this methodology is confirmed using the E3 telemetry data. Given good estimates of spacecraft's projected area, center of pressure location, and spacecraft velocity, the time history of the Enceladus plume density is reconstructed accordingly. The 1-sigma uncertainty of the estimated density is 7.7%. Next, we modeled the density due to each plume jet as a function of both the radial and angular distances of the spacecraft from the plume source. We also conjecture that the total plume density experienced by the spacecraft is the sum of the component plume densities. By comparing the time history of the reconstructed E3 plume density with that predicted by the plume model, values of the plume model parameters are determined. Results obtained are compared with those determined by other Cassini science instruments.
Lee, Allan Y.↗
Asteroid/comet encounter opportunities for the Galileo VEEGA mission
The opportunity for the Galileo spacecraft to perform a close flyby of an asteroid or distant observation of a comet while on the Venus-Earth-Earth-Gravity-Assist (VEEGA) mission to Jupiter is discussed. More than 120 nominal trajectories were used in a scan program to identify asteroids passing within 30 million km of the spacecraft. A total of 47 asteroids were examined to determine the propellant cost of a close flyby. The possible flybys include a double asteroid flyby with No. 951 in October, 1991, with a flyby of No. 243 in August 1993. The factors considered in the selection of an asteroid include the propellant margin cost of modifying a nominal trajectory to include a close flyby, the size and type of asteroid, and the Jupiter arrival date.
Johannesen, Jennie R.↗
The Determination of Titan Gravity Field from Doppler Tracking of the Cassini Spacecraft
In its tour of the Saturnian system, the spacecraft Cassini is carrying out measurements of the gravity field of Titan, whose knowledge is crucial for constraining the internal structure of the satellite. In the five flybys devoted to gravity science, the spacecraft is tracked in X (8.4 GHz) and Ka band (32.5 GHz) from the antennas of NASA's Deep Space Network. The use of a dual frequency downlink is used to mitigate the effects of interplanetary plasma, the largest noise source affecting Doppler measurements. Variations in the wet path delay are effectively compensated by means of advanced water vapor radiometers placed close to the ground antennas. The first three flybys occurred on February 27, 2006, December 28, 2006, and June 29, 2007. Two additional flybys are planned in July 2008 and May 2010. This paper presents the estimation of the mass and quadrupole field of Titan from the first two flybys, carried out by the Cassini Radio Science Team using a short arc orbit determination. The data from the two flybys are first independently fit using a dynamical model of the spacecraft and the bodies of the Saturnian system, and then combined in a multi-arc solution. Under the assumption that the higher degree harmonics are negligible, the estimated values of the gravity parameters from the combined, multi-arc solution are GM = 8978.1337 +/- 0.0025 km(exp 3) / s(exp 2), J (sub 2) = (2.7221 +/- 0.0185) 10 (exp -5) and C (sub 22) = (1.1159 +/- 0.0040) 10 (exp -5) The excellent agreement (within 1.7 sigma) of the results from the two flybys further increases the confidence in the solution and provides an a posteriori validation of the dynamical model.
Iess, L.↗
Enceladus Plume Density Modeling and Reconstruction for Cassini Attitude Control System
In 2005, Cassini detected jets composed mostly of water, spouting from a set of nearly parallel rifts in the crust of Enceladus, an icy moon of Saturn. During an Enceladus flyby, either reaction wheels or attitude control thrusters on the Cassini spacecraft are used to overcome the external torque imparted on Cassini due to Enceladus plume or jets, as well as to slew the spacecraft in order to meet the pointing needs of the on-board science instruments. If the estimated imparted torque is larger than it can be controlled by the reaction wheel control system, thrusters are used to control the spacecraft. Having an engineering model that can predict and simulate the external torque imparted on Cassini spacecraft due to the plume density during all projected low-altitude Enceladus flybys is important. Equally important is being able to reconstruct the plume density after each flyby in order to calibrate the model. This paper describes an engineering model of the Enceladus plume density, as a function of the flyby altitude, developed for the Cassini Attitude and Articulation Control Subsystem, and novel methodologies that use guidance, navigation, and control data to estimate the external torque imparted on the spacecraft due to the Enceladus plume and jets. The plume density is determined accordingly. The methodologies described have already been used to reconstruct the plume density for three low-altitude Enceladus flybys of Cassini in 2008 and will continue to be used on all remaining low-altitude Enceladus flybys in Cassini's extended missions.
Sarani, Siamak↗
Multi-asteroid comet missions using solar electric propulsion.
Multitarget flyby missions to asteroids and comets are attractive candidates for solar electric propulsion (SEP) application because SEP can efficiently provide the thrust required for carefully chosen sequences of encounters. In this paper, techniques for finding encounter sequences for these missions are described, and examples involving flyby and rendezvous missions to P/Encke, P/Kopff and 20/Massalia are presented. In addition, examples of four asteroid flyby sequences are given. Encounters typically have flyby speeds on the order of 5-10 km/sec and are limited only by navigational capability as regards flyby distance, which is taken as zero in the study. Flights traversing the asteroid belt can be modified by SEP to pass one or more asteroids, and the performance penalty is small if the encounters are properly spaced.
Bender, D. F.↗
Out of ecliptic missions using Venus or earth gravity assists
Multiple Venus or earth gravity-assist flybys are investigated as a means of producing trajectories that are inclined to the solar equator at low cost in total delta V. There are three phases to such trajectories: (1) production of a high flyby speed at the planet encounter, (2) attainment of one-to-one resonance by orbit pumping, and (3) deflection to high inclination by orbit cranking. Flybys are restricted to occur at the node of the planet orbit and the solar equator so as to take advantage of the natural inclination of the solar equator. For Venus flybys, the high approach speed is inherent in the earth to Venus trajectory. For earth flybys, the production of high approach speed can be accomplished by a VEGA (Venus-earth-gravity assist) trajectory or by a delta V-EGA trajectory. The general result is that moderate inclinations to the solar equator can be obtained at moderate total delta V cost, but at flight times which rise to five years for an inclination of 37 deg and to 13 years for an inclination of 54 deg.
Bender, D. F.↗
Galileo trajectory design
The trajectory design of the Galileo spacecraft is examined. The Galileo spacecraft was launched on a six-year long trip to Jupiter in October 1989. A new Venus-Earth-Earth-Gravity Assist (VEEGA) trajectory mode is being used for the transfer to Jupiter and involves two phasing orbits around the sun and gravity-assist flybys with Venus. The aggregate delta V acquired from these flybys is 18.3 km/s. The interplanetary trajectory includes a close flyby of asteroid 951-Gaspra in October 1991 and a possible flyby of 243-Ida in August 1993. After arrival at Jupiter in December 1995, the previously released Galileo atmospheric probe will relay data to earth via the Galileo Orbiter. The orbital phase of the mission will involve 10 orbits of Jupiter over a 22 month period. In this phase the Orbiter will use repeated gravity-assisted flybys of Europa, Ganymede and Callisto during which Jupiter, its magnetosphere and the Galilean satellites will be investigated. The mission is scheduled to end in October 1997.
D'Amario, Louis A.↗