Search NASA⌕ Search

SEARCH · Search NASA

Results for “mission trajectory”

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 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Automated Software for Manned Spacecraft - Bridging the Gap from Sci Fi to Reality

With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies. One goal of advanced spacecraft automation is the ability to reduce both the crew workload and the ground control footprint while at the same time increasing spacecraft and mission flexibility. Historically, crewed spacecraft required a large number of operators on the ground to use a plethora of tools to compute nominal and contingency mission trajectories. Moving those sophisticated software tools to being onboard the vehicle can reduce the need for such complex ground support. Given that today’s spacecraft software is not yet as capable or as flexible in all circumstances as the computers depicted in movies, there is usually a trade-off between software automation cost and the flexibility of that software resulting in a trade-off between what is performed on the spacecraft and what is left to onboard crew or ground control. For missions that go beyond the Moon, software that autonomously controls nearly every aspect of a crewed mission will become a necessity given the long time delays between the spacecraft and Earth’s ground control teams. The lessons learned by Boeing and its Mission Operations team, through the design and implementation of Starliner’s hardware and software automation, will be able to inform future public and private spacecraft design. As the technologies and capabilities evolve, incorporating lessons learned in successful low Earth orbit commercial crew vehicle missions, spacecraft designs will continue to improve and be able to better enable safe execution of human missions to the Moon and beyond.

Robert C Dempsey↗
NASA NTRSDate not supplied

Automated Software for Manned Spacecraft - Bridging the Gap from Sci Fi to Reality

With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies. One goal of advanced spacecraft automation is the ability to reduce both the crew workload and the ground control footprint while at the same time increasing spacecraft and mission flexibility. Historically, crewed spacecraft required a large number of operators on the ground to use a plethora of tools to compute nominal and contingency mission trajectories. Moving those sophisticated software tools to being onboard the vehicle can reduce the need for such complex ground support. Given that today’s spacecraft software is not yet as capable or as flexible in all circumstances as the computers depicted in movies, there is usually a trade-off between software automation cost and the flexibility of that software resulting in a trade-off between what is performed on the spacecraft and what is left to onboard crew or ground control. For missions that go beyond the Moon, software that autonomously controls nearly every aspect of a crewed mission will become a necessity given the long time delays between the spacecraft and Earth’s ground control teams. The lessons learned by Boeing and its Mission Operations team, through the design and implementation of Starliner’s hardware and software automation, will be able to inform future public and private spacecraft design. As the technologies and capabilities evolve, incorporating lessons learned in successful low Earth orbit commercial crew vehicle missions, spacecraft designs will continue to improve and be able to better enable safe execution of human missions to the Moon and beyond.

Robert C. Dempsey↗
NASA NTRSDate not supplied

Automated Software for Crewed Spacecraft - Bridging the Gap from Sci Fi to Reality

With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies. One goal of advanced spacecraft automation is the ability to reduce both the crew workload and the ground control footprint while at the same time increasing spacecraft and mission flexibility. Historically, crewed spacecraft required a large number of operators on the ground to use a plethora of tools to compute nominal and contingency mission trajectories. Moving those sophisticated software tools to being onboard the vehicle can reduce the need for such complex ground support. Given that today’s spacecraft software is not yet as capable or as flexible in all circumstances as the computers depicted in movies, there is usually a trade-off between software automation cost and the flexibility of that software resulting in a trade-off between what is performed on the spacecraft and what is left to onboard crew or ground control. For missions that go beyond the Moon, software that autonomously controls nearly every aspect of a crewed mission will become a necessity given the long time delays between the spacecraft and Earth’s ground control teams. The lessons learned by Boeing and its Mission Operations team, through the design and implementation of Starliner’s hardware and software automation, will be able to inform future public and private spacecraft design. As the technologies and capabilities evolve, incorporating lessons learned in successful low Earth orbit commercial crew vehicle missions, spacecraft designs will continue to improve and be able to better enable safe execution of human missions to the Moon and beyond.

Robert C Dempsey↗
NASA NTRS2008

Return to Mercury: A Comparison of Solar Simulation and Flight Data for the MESSENGER Spacecraft

The MErcury, Surface, Space, ENvironment GEochemistry and Ranging (MESSENGER) spacecraft is a NASA Discovery Mission spacecraft developed and operated by the Johns Hopkins University Applied Physics Laboratory. It was launched on August 3, 2004 and is currently on a course for Mercury orbit insertion in March 2011. To date the mission trajectory has taken the spacecraft to minimum solar distances of 0.332 and 0.313 AU and on January 14, 2008 the first flyby of Mercury in 33 years. From launch through the latest perihelion passage temperature performance data has been collected for the sun facing Digital Sun Sensors (DSS), the sun facing phased array and low gain (omni) antennas, the solar arrays, the sunshade and the two sun facing attitude control 4.4 N thrusters. Prior to launch, extensive solar simulation testing was conducted at the Glenn Research Center, Tank 6 solar simulation facility in Cleveland Ohio. Flight hardware qualification units representing these Sun exposed components were tested in solar environments that represented near mission minimum solar distance as to verify the thermal designs and the material used in fabrication. The paper will review the thermal designs of these components and their thermal performance to date as compared to the solar simulation testing.

Ercol, Carl J.↗
NASA NTRS1995

Robotic Planetary Science Missions Enabled with Small NTR Engine/Stage Technologies

The high specific impulse (Isp) and engine thrust-to-weight ratio of liquid hydrogen (LH2)-cooled nuclear thermal rocket (NTR) engines makes them ideal for upper stage applications to difficult robotic planetary science missions. A small 15 thousand pound force (klbf) NTR engine using a uranium-zirconium-niobium 'ternary carbide' fuel (Isp approximately 960 seconds at approximately 3025K) developed in the Commonwealth of Independent States (CIS) is examined and its use on an expendable injection stage is shown to provide major increases in payload delivered to the outer planets (Saturn, Uranus, Neptune and Pluto). Using a single 'Titan IV-class' launch vehicle, with a lift capability to low Earth orbit (LEO) of approximately 20 metric tons (t), an expendable NTR upper stage can inject two Pluto 'Fast Flyby' spacecraft (PFF/SC) plus support equipment-combined mass of approximately 508 kg--on high energy, '6.5-9.2 year' direct trajectory missions to Pluto. A conventional chemical propulsion mission would use a liquid oxygen (LOX)/LH2 'Centaur' upper stage and two solid rocket 'kick motors' to inject a single PFF/SC on the same Titan IV launch vehicle. For follow on Pluto missions, the NTR injection stage would utilize a Jupiter 'gravity assist' (JGA) maneuver to launch a LOX/liquid methane (CH4) capture stage (Isp approximately 375 seconds) and a Pluto 'orbiter' spacecraft weighing between approximately 167-312 kg. With chemical propulsion, a Pluto orbiter mission is not a viable option because c inadequate delivered mass. Using a 'standardized' NTR injection stage and the same single Titan IV launch scenario, 'direct flight' (no gravity assist) orbiter missions to Saturn, Uranus and Neptune are also enabled with transit times of 2.3, 6.6, and 12.6 years, respectively. Injected mass includes a storable, nitrogen tetroxide/monomethyl hydrazine (N2O4/MMH) capture stage (Isp approximately 330 seconds) and orbiter payloads 340 to 820% larger than that achievable using a LOX/LH2-fueled injection stage. The paper discusses NTR technology and mission characteristics, shows NTR stage and payload accommodations within the 26.2 m long Titan IV payload fairing, and discusses NTR stage performance as a function of assumed cryogenic tank technology.

Borowski, Stanley K.↗
NASA NTRS2001

Development of a Space Radiation Monte-Carlo Computer Simulation Based on the FLUKE and Root Codes

The radiation environment in space is a complex problem to model. Trying to extrapolate the projections of that environment into all areas of the internal spacecraft geometry is even more daunting. With the support of our CERN colleagues, our research group in Houston is embarking on a project to develop a radiation transport tool that is tailored to the problem of taking the external radiation flux incident on any particular spacecraft and simulating the evolution of that flux through a geometrically accurate model of the spacecraft material. The output will be a prediction of the detailed nature of the resulting internal radiation environment within the spacecraft as well as its secondary albedo. Beyond doing the physics transport of the incident flux, the software tool we are developing will provide a self-contained stand-alone object-oriented analysis and visualization infrastructure. It will also include a graphical user interface and a set of input tools to facilitate the simulation of space missions in terms of nominal radiation models and mission trajectory profiles. The goal of this project is to produce a code that is considerably more accurate and user-friendly than existing Monte-Carlo-based tools for the evaluation of the space radiation environment. Furthermore, the code will be an essential complement to the currently existing analytic codes in the BRYNTRN/HZETRN family for the evaluation of radiation shielding. The code will be directly applicable to the simulation of environments in low earth orbit, on the lunar surface, on planetary surfaces (including the Earth) and in the interplanetary medium such as on a transit to Mars (and even in the interstellar medium). The software will include modules whose underlying physics base can continue to be enhanced and updated for physics content, as future data become available beyond the timeframe of the initial development now foreseen. This future maintenance will be available from the authors of FLUKA as part of their continuing efforts to support the users of the FLUKA code within the particle physics community. In keeping with the spirit of developing an evolving physics code, we are planning as part of this project, to participate in the efforts to validate the core FLUKA physics in ground-based accelerator test runs. The emphasis of these test runs will be the physics of greatest interest in the simulation of the space radiation environment. Such a tool will be of great value to planners, designers and operators of future space missions, as well as for the design of the vehicles and habitats to be used on such missions. It will also be of aid to future experiments of various kinds that may be affected at some level by the ambient radiation environment, or in the analysis of hybrid experiment designs that have been discussed for space-based astronomy and astrophysics. The tool will be of value to the Life Sciences personnel involved in the prediction and measurement of radiation doses experienced by the crewmembers on such missions. In addition, the tool will be of great use to the planners of experiments to measure and evaluate the space radiation environment itself. It can likewise be useful in the analysis of safe havens, hazard migration plans, and NASA's call for new research in composites and to NASA engineers modeling the radiation exposure of electronic circuits. This code will provide an important complimentary check on the predictions of analytic codes such as BRYNTRN/HZETRN that are presently used for many similar applications, and which have shortcomings that are more easily overcome with Monte Carlo type simulations. Finally, it is acknowledged that there are similar efforts based around the use of the GEANT4 Monte-Carlo transport code currently under development at CERN. It is our intention to make our software modular and sufficiently flexible to allow the parallel use of either FLUKA or GEANT4 as the physics transport engine.

Pinsky, L. S.↗
NASA NTRS2011

Why Atens Enjoy Enhanced Accessibility For Human Space Flight

In the context of human space flight (HSF), the concept of near-Earth object (NEO) accessibility is highly subjective. Whether or not a particular NEO is accessible critically depends on mass, performance, and reliability of interplanetary HSF systems yet to be designed. Such systems would certainly include propulsion and crew life support with adequate shielding from both solar flares and galactic cosmic radiation. Equally critical architecture options are relevant to NEO accessibility. These options are also far from being determined and include the number of launches supporting an HSF mission, together with whether or not consumables are to be pre-emplaced at the destination. Until the unknowns of HSF to NEOs come into clearer focus, the notion of relative accessibility is of great utility. Imagine a group of NEOs, each with nearly equal HSF merit determined from their individual characteristics relating to crew safety, scientific return, resource utilization, and planetary defense. The more accessible members of this group are more likely to be explored first. A highly accessible NEO could conceivably be deferred in favor of a less accessible HSF destination because the latter is more accessible during a programmatically desirable launch compliant mission trajectory solutions detected in association with a specific NEO. The known NEO population is then surveyed to illustrate in which regions of heliocentric semi-major axis, eccentricity, and inclination (a, e, i) space NEOs with large n values are mapped. The (a, e, i) mapping is also formatted such that membership in each of four NEO orbit classifications, as defined below, is evident. Amors have orbits everywhere superior to (outside of) Earth's. An Amor is therefore defined to have perihelion between 1.017 astronomical units (AU) and the maximum NEO value of 1.3 AU. As of 0 hrs Universal Time on 1 January 2011 (UT epoch 2011.0), Amors numbered 2855 in the Jet Propulsion Laboratory (JPL) Small-Body Database (SBDB), comprising 37.7% of known NEOs. Apollos have orbits crossing Earth's with periods greater than Earth's. An Apollo is therefore defined to have perihelion less than 1.017 AU and a greater than 1.0 AU. As of 2011.0 UT, Apollos numbered 4080 in the SBDB, comprising 53.9% of known NEOs. Atens have orbits crossing Earth's with periods less than Earth's. An Aten is therefore defined to have aphelion greater than 0.983 AU and a less than 1.0 AU. As of 2011.0 UT, Atens numbered 618 in the SBDB, comprising 8.2% of known NEOs. Atiras have orbits everywhere inferior to (inside of) Earth's. An Atira is therefore defined to have aphelion less than 0.983 AU. As of 2011.0 UT, Atiras numbered 11 in the SBDB, comprising 0.1% of known NEOs. It is no surprise that the largest n values are chiefly associated with Apollos and Atens. Because these orbits cross Earth's, distance to be covered in a given round trip mission time delta-t can be far less than is possible for Amors or Atiras . This delta-t or the sum of mission propulsive impulse magnitudes delta-v can more frequently be minimized to enhance NHATS compliance for Apollos and Atens than is generally the case for Amors and Atiras. A less intuitive trend in NHATS results is that Atens nearly outnumber the more numerous Apollos among the most compliant NEOs as measured by n. This trend is completely out of proportion to the degree Atens are represented among the known NEO population. A theory based on geocentric NEO dynamics is presented by this paper to explain why Atens enjoy inherently greater accessibility than do Apollos. Another trend evident from mapping into (a, e, i) space is the dearth of known NEOs at low e when a < 1 AU. Underrepresentation of Atens and Atiras in the NEO catalog is at least in part attributable to observing exclusively from a perspective near Earth. Generally inferior Aten and Atira orbits are rarely, if ever, in Earth's night sky. Until a comprehensive NEO survey is conducted from an appropriateegion remote from Earth, the theory developed in this paper indicates a substantial fraction of the most accessible NEOs will remain unknown. season. Such a season is really yet another undetermined HSF architecture option. A launch season's duration will likely be measured in weeks, and it will be utilized at an indeterminate point almost certainly more than a decade in the future when HSF programmatic maturity is sufficient. Furthermore, current knowledge of the NEO population relevant to HSF is far from complete. In the 100-m-diameter class of greatest interest, only a few percent of the estimated NEO population is known [2, Figure 2.4]. Therefore, any known, lost, or fictitious NEO in a highly accessible orbit is a potential HSF destination of merit. Even if lost, fictitious, small, or hazardous, such a potential target (or another in a similar orbit) may ultimately prove to be an early HSF destination when the pertinent NEO population is more thoroughly catalogued and NEO orbits are more thoroughly maintained at high accuracy. This paper first reviews methodology and pertinent results from NASA-sponsored research performed in late 2010 and dubbed NEO HSF Accessible Targets Study (NHATS, pronounced as "gnats"). A useful accessibility metric developed during this study is n, the tally of NHATS-

Barbee, Brent↗
NASA NTRSDate not supplied

Integrated Crewed Mars Mission Analysis, Part II: The Trajectory Strikes Back

Crewed missions to Mars present a challenging problem involving strong interactions between a variety of spacecraft systems. Design and architecture decisions made by one system can have powerful implications for another. Siloed subsystem development and optimization efforts are unlikely to generate optimal results for the integrated system and may lead to counterproductive investments at the mission and system level. Mismatched assumptions between different subsystems can also negatively impact the final result. Integrated systems analysis, trade studies, and sensitivity analysis are a critical element of successful Mars mission design. Previous work examined the linkages between Environmental Control and Life Support System (ECLSS) loop closure, food water content, spares Probability of Sufficiency (POS), and other factors by performing an integrated mass and cost assessment of a variety of Mars habitat and transportation system designs. This paper expands upon that work by evaluating the impact of mission duration, trajectory, and propulsion technology alongside key habitat variables. Transportation system and trajectory design decisions have enormous impacts on overall system mass, and the impacts of those decisions are themselves sensitive to the mass of the habitat that is being transported. This paper examines a variety of mission cases and evaluates total departure mass for each case. An estimate of relative costs for specific cases is also provided. The results are discussed, with an emphasis on the sensitivity of mass, cost, and other figures of merit to key parameters. Interactions and dependencies between various decisions, particularly those that relate to technology investments, are also highlighted. Overall, the various elements, systems, and subsystems required to support human spaceflight should not be optimized and evaluated in isolation, but instead should be analyzed as part of an integrated system. This paper demonstrates how integrated analysis can improve system understanding and lead to more optimal and effective crewed exploration systems.

Human Spaceflight↗
NASA NTRSDate not supplied

Integrated Crewed Mars Mission Analysis, Part II: The Trajectory Strikes Back

Crewed missions to Mars present a challenging problem involving strong interactions between a variety of spacecraft systems. Design and architecture decisions made by one system can have powerful implications for another. Siloed subsystem development and optimization efforts are unlikely to generate optimal results for the integrated system and may lead to counterproductive investments at the mission and system level. Mismatched assumptions between different subsystems can also negatively impact the final result. Integrated systems analysis, trade studies, and sensitivity analysis are a critical element of successful Mars mission design. Previous work examined the linkages between Environmental Control and Life Support System (ECLSS) loop closure, food water content, spares Probability of Sufficiency (POS), and other factors by performing an integrated mass and cost assessment of a variety of Mars habitat and transportation system designs. This paper expands upon that work by evaluating the impact of mission duration, trajectory, and propulsion technology alongside key habitat variables. Transportation system and trajectory design decisions have enormous impacts on overall system mass, and the impacts of those decisions are themselves sensitive to the mass of the habitat that is being transported. This paper examines a variety of mission cases and evaluates total departure mass for each case. An estimate of relative costs for specific cases is also provided. The results are discussed, with an emphasis on the sensitivity of mass, cost, and other figures of merit to key parameters. Interactions and dependencies between various decisions, particularly those that relate to technology investments, are also highlighted. Overall, the various elements, systems, and subsystems required to support human spaceflight should not be optimized and evaluated in isolation, but instead should be analyzed as part of an integrated system. This paper demonstrates how integrated analysis can improve system understanding and lead to more optimal and effective crewed exploration systems.

Human Spaceflight↗
NASA NTRS1972

Early missions to comets

Two specific early missions to the comets Grigg-Skjellerup in 1977 and Encke in 1980 are proposed as precusor missions to Encke rendezvous and Halley intercept in 1986. The mission guidelines and principal objectives are presented. The spacecraft IMP was chosen for the flythrough mission for Grigg-Skjellerup in 1977, and the Helios spacecraft for the Encke mission in 1980. The mission trajectories are summarized in graphs.

Farquhar, R. W.↗
NASA NTRS1971

JOSE, Jupiter orbiting spacecraft: A systems study, volume 1

A brief summary of the mechanical properties of Jupiter is presented along with an organizational outline of the entire JOSE program. Other aspects of the program described include: spacecraft design, mission trajectories, altitude control, propulsion subsystem, on-board power supply, spacecraft structures and environmental design considerations, and telemetry.

Source record↗
NASA NTRS1972

First generation atmospheric probes (10-BARS) for Uranus and Neptune

The feasibility of atmospheric entry probe missions to Uranus and Neptune is studied, and preliminary estimates of missions parameters are presented. Most of the study results are applicable, with only minor modifications, to Uranus-Neptune entry probes included on any type of outer planet mission. Trajectory dynamics is discussed first because it imposes some important constraints upon the total time available for data transmission, which in turn determines the descent rate. This last quantity provides important information for the design of the scientific payload.

Sullivan, R. J.↗
NASA NTRS1973

Apollo/Soyuz test project operational data book. Volume 2: ASTP mass properties data book

Spacecraft mass properties data are provided for use in mission planning, trajectory documentation, mission simulations, and consumable loading. Spacecraft for use in determining locations of spacecraft components and the relationship to coordinate systems in the launch and docked configuration. Mass properties and consumable loading data for the ASTP mission are included along with consumables mass property data and mission independent consumable loading information for the CSM and DM.

Source record↗
NASA NTRS1972

Data report of six free-drifting buoys tracked by the Eole satellite in the western North Atlantic Ocean in the autumn of 1972

The buoys were deployed on the Continental Shelf east of the Chesapeake Light and were tracked by the French EOLE satellite. Two buoys drifted for 11 days during the first mission and four buoys drifted for 14 days during the second mission. Trajectory and water temperature data are presented in tabular and graphical from with a discussion of the accuracy.

Usry, J. W.↗
NASA NTRS1982

Computer modeling of thermoelectric generator performance

Features of the DEGRA 2 computer code for simulating the operations of a spacecraft thermoelectric generator are described. The code models the physical processes occurring during operation. Input variables include the thermoelectric couple geometry and composition, the thermoelectric materials' properties, interfaces and insulation in the thermopile, the heat source characteristics, mission trajectory, and generator electrical requirements. Time steps can be specified and sublimation of the leg and hot shoe is accounted for, as are shorts between legs. Calculations are performed for conduction, Peltier, Thomson, and Joule heating, the cold junction can be adjusted for solar radition, and the legs of the thermoelectric couple are segmented to enhance the approximation accuracy. A trial run covering 18 couple modules yielded data with 0.3% accuracy with regard to test data. The model has been successful with selenide materials, SiGe, and SiN4, with output of all critical operational variables.

Chmielewski, A. B.↗