Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “spacecraft anomalies”

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 91 records · Page 5
All sourcesNASA NTRSDOE OSTI
NASA NTRS1996

Orbital Anomalies in Goddard Spacecraft for Calendar Year 1994

This report summarizes and updates the annual on-orbit performance between January I and December 31, 1994, for spacecraft built by or managed by the Goddard Space Flight Center (GSFC). During 1994, GSFC had 27 active orbiting satellites and I Shuttle-launched and retrieved 'free flyer.' There were 310 reported anomalies among 21 satellites and one GSFC instrument (TOMS). GOES-8 accounted for 66 anomalies, and SAMPES reported 155 'anomalies'. Of the 155 anomalies reported for all but SAMPEX, only 4 affected the spacecraft missions 'substantially' or greater, that is, presented a loss of more than 33% of the total missions. The most frequent subsystem anomalies were Instrument/Payload(44), Timing Command and Control(40), and Attitude Control Systems(33). Of the non-SAMPEX anomalies, 29% had no effect on the missions and 28% caused subsystem or instrument degradation and, for another 28%, no anomaly effect on the mission could be determined. Fifty-three percent of non-SAMPEX anomalies could not be classified according to 'type'; the other most common types were 'systemic'(35), 'random'(19), and 'normal or expected operation'(15). Forty percent of the anomalies were not classified according to failure category; the remaining most frequent occurrences were 'design problems'(50) and 'other known problems'(35).

Thomas, Walter B.↗
NASA NTRS1985

Experiments in charge control at geosynchronous orbit - ATS-5 and ATS-6

In connection with existing theoretical concepts, it was difficult to explain the negative potentials found in sunlight, first on Applied Technology Satellite-5 (ATS-5) and then on ATS-6. The problem became important when an association between spacecraft charging and anomalies in spacecraft behavior was observed. A study of daylight charging phenomena on ATS-6 was conducted, and an investigation was performed with the objective to determine effective methods of charge control, taking into account the feasibility to utilize the ATS-5 and ATS-6 ion engines as current sources. In the present paper, data and analysis for the ion engine experiments on ATS-5 and ATS-6 are presented. It is shown that electron emission from a satellite with insulating surfaces is not an effective method of charge control because the increase in differential charging which results limits the effectiveness of electron emitters and increases the possibility of electrostatic discharges between surfaces at different potentials.

Olsen, R. C.↗
NASA NTRS1983

Analysis of spacecraft on-orbit anomalies and lifetimes

Analyses of the on-orbit performance of forty-four unmanned NASA spacecraft are presented. Included are detailed descriptions and classifications of over 600 anomalies; each anomalous incident represents one reported deviation from expected spacecraft performance. Charts depicting satellite lifetimes and the performance of their major subsystems are included. Engineering analyses to further investigate the kinds and frequencies of various classes of anomalies have been conducted. An improved method for charting spacecraft capability as a function of time on orbit is explored.

Bloomquist, C.↗
NASA NTRS1996

Spacecraft System Failures and Anomalies Attributed to the Natural Space Environment

The natural space environment is characterized by many complex and subtle phenomena hostile to spacecraft. The effects of these phenomena impact spacecraft design, development, and operations. Space systems become increasingly susceptible to the space environment as use of composite materials and smaller, faster electronics increases. This trend makes an understanding of the natural space environment essential to accomplish overall mission objectives, especially in the current climate of better/cheaper/faster. This primer provides a brief overview of the natural space environment - definition, related programmatic issues, and effects on various spacecraft subsystems. The primary focus, however, is to catalog, through representative case histories, spacecraft failures and anomalies attributed to the natural space environment. This primer is one in a series of NASA Reference Publications currently being developed by the Electromagnetics and Aerospace Environments Branch, Systems Analysis and Integration Laboratory, Marshall Space Flight Center (MSFC), National Aeronautics and Space Administration (NASA).

Bedingfield, Keith, L.↗
NASA NTRS1979

Viking adaptive mission sequence and control operations

Viking mission operations were required to provide an adaptive sequencing capability in which future observations could be influenced by the latest information about Mars as it was obtained and analyzed. The mission operations strategy that was developed met this requirement and provided the capability to respond smoothly and efficiently to spacecraft subsystem anomalies with minimum impact on the science data gathering process. A description of the major elements of this adaptive man-in-the-loop control system is provided. Specific cases showing how it was utilized to enhance scientific return and to respond to spacecraft anomalies are also provided.

Larman, B. T.↗
DOE OSTI2020

Hypervelocity impact flash expansion geometry under various spacecraft surface electrical conditions

A more congested space environment due to increasing space activities introduces new threats to spacecraft operators. Among these threats include hypervelocity impacts from microparticles (< 1 µg) in the form of meteoroids and space debris. These microparticles travel at speeds between 11.2 and 72.8 km/s with respect to the Earth and can impact spacecraft forming a small (~1 µm) and dense (~ 10 26 m -3 ) plasma. This plasma can generate a strong optical emission (impact flash) and a radio frequency (RF) emission. These emissions can lead to spacecraft electrical anomalies when the impacted spacecraft surface (target) carries high electrical potential due to various space weather effects. To understand the microparticle hypervelocity impact plasma and its associated threat to spacecraft electronics, we studied the hypervelocity impact flash expansion geometry under various spacecraft surface electrical conditions. Three high-speed broadband photomultiplier tubes (PMT) are used to capture the temporal evolution of the impact flash and the temporal evolution of the angular distribution of the impact flash expansion geometry in a 3 MV electrostatic dust accelerator during a ground-based experiment. Overall, results indicate that the impact surface electrical condition has a statistically significant influence on the impact flash geometry, and a strong similarity between the impact plasma and flash expansion geometry. Thus, this paper provides new experimental support for the impact flash origin from and connection with the impact plasma, and serves as the first impact flash expansion geometry characterization under various impact surface electrical conditions in a collisionless environment (< 10 -5 Torr).

42 ENGINEERING↗
NASA NTRS2006

Evolution of the Hubble Space Telescope Safing Systems

The Hubble Space Telescope (HST) was launched on April 24 1990, with an expected lifespan of 15 years. Central to the spacecraft design was the concept of a series of on-orbit shuttle servicing missions permitting astronauts to replace failed equipment, update the scientific instruments and keep the HST at the forefront of astronomical discoveries. One key to the success of the Hubble mission has been the robust Safing systems designed to monitor the performance of the observatory and to react to keep the spacecraft safe in the event of equipment anomaly. The spacecraft Safing System consists of a range of software tests in the primary flight computer that evaluate the performance of mission critical hardware, safe modes that are activated when the primary control mode is deemed inadequate for protecting the vehicle, and special actions that the computer can take to autonomously reconfigure critical hardware. The HST Safing System was structured to autonomously detect electrical power system, data management system, and pointing control system malfunctions and to configure the vehicle to ensure safe operation without ground intervention for up to 72 hours. There is also a dedicated safe mode computer that constantly monitors a keep-alive signal from the primary computer. If this signal stops, the safe mode computer shuts down the primary computer and takes over control of the vehicle, putting it into a safe, low-power configuration. The HST Safing system has continued to evolve as equipment has aged, as new hardware has been installed on the vehicle, and as the operation modes have matured during the mission. Along with the continual refinement of the limits used in the safing tests, several new tests have been added to the monitoring system, and new safe modes have been added to the flight software. This paper will focus on the evolution of the HST Safing System and Safing tests, and the importance of this evolution to prolonging the science operations of the telescope.

Pepe, Joyce↗
NASA NTRS2015

Benefits of Spacecraft Level Vibration Testing

NASA-HDBK-7008 Spacecraft Level Dynamic Environments Testing discusses the approaches, benefits, dangers, and recommended practices for spacecraft level dynamic environments testing, including vibration testing. This paper discusses in additional detail the benefits and actual experiences of vibration testing spacecraft for NASA Goddard Space Flight Center (GSFC) and Jet Propulsion Laboratory (JPL) flight projects. JPL and GSFC have both similarities and differences in their spacecraft level vibration test approach: JPL uses a random vibration input and a frequency range usually starting at 5 Hz and extending to as high as 250 Hz. GSFC uses a sine sweep vibration input and a frequency range usually starting at 5 Hz and extending only to the limits of the coupled loads analysis (typically 50 to 60 Hz). However, both JPL and GSFC use force limiting to realistically notch spacecraft resonances and response (acceleration) limiting as necessary to protect spacecraft structure and hardware from exceeding design strength capabilities. Despite GSFC and JPL differences in spacecraft level vibration test approaches, both have uncovered a significant number of spacecraft design and workmanship anomalies in vibration tests. This paper will give an overview of JPL and GSFC spacecraft vibration testing approaches and provide a detailed description of spacecraft anomalies revealed.

Spacecraft Vibration Test↗
NASA NTRS1980

Spacecraft utility and the development of confidence intervals for criticality of anomalies

The concept of spacecraft utility, a measure of its performance in orbit, is discussed and its formulation is described. Performance is defined in terms of the malfunctions that occur and the criticality to the mission of these malfunctions. Different approaches to establishing average or expected values of criticality are discussed and confidence intervals are developed for parameters used in the computation of utility.

Williams, R. E.↗
NASA NTRS1977

Apollo-Soyuz pamphlet no. 4: Gravitational field

Two Apollo Soyuz experiments designed to detect gravity anomalies from spacecraft motion are described. The geodynamics experiment (MA-128) measured large-scale gravity anomalies by detecting small accelerations of Apollo in the 222 km orbit, using Doppler tracking from the ATS-6 satellite. Experiment MA-089 measured 300 km anomalies on the earth's surface by detecting minute changes in the separation between Apollo and the docking module. Topics discussed in relation to these experiments include the Doppler effect, gravimeters, and the discovery of mascons on the moon.

Page, L. W.↗
NASA NTRS2018

Lessons Learned During the Transition of SORCE Science Operations to Daylight Only Operations

In July 2013, NASA's Solar Radiation and Climate Experiment experienced a battery anomaly which placed it into safemode halting all science observations. Initial attempts to recover the spacecraft to an operational configuration failed due to the reduced capacity of the battery. As the keystone mission for measuring total solar irradiance, and the cornerstone mission for measuring the solar spectral irradiance there was a strong motivation for developing a new operations concept that would allow SORCE to resume daily measurements of the Sun. The operations team faced many challenges over the next several months. For a five-day period in late 2013 the operations team was able resume science observations to cross-calibrate SORCE data with a new instrument launched in November 2013. After the cross-calibration campaign was completed a new operations concept was deployed which allowed SORCE to perform daylight only operations. In this mode of operations all non-essential components are powered off at each eclipse entry and then turned back on at sunrise. In March 2014 SORCE resumed making daily measurements of the Sun. This paper will review the events and lessons learned from the six-month recovery effort.

Spacecraft Anomaly↗
NASA NTRS2014

MSFC/EV44 Natural Environment Capabilities

The Natural Environments Branch at Marshall Space Flight Center is an integral part of many NASA satellite and launch vehicle programs, providing analyses of the space and terrestrial environments that are used for program development efforts, operational support, and anomaly investigations. These capabilities include model development, instrument build and testing, analysis of space and terrestrial related data, spacecraft charging anomaly investigations, surface and internal charging modeling, space environment definition, and radiation assessments for electronic parts. All aspects of space and terrestrial design are implemented with the goal of devising missions that are successful from launch to operations in the space environment of LEO, polar, GEO, and interplanetary orbits.

NeergaardParker, Linda↗
NASA NTRS2014

MSFC/EV44 Natural Environment Capabilities

The Natural Environments Branch at Marshall Space Flight Center is an integral part of many NASA satellite and launch vehicle programs, providing analyses of the space and terrestrial environments that are used for program development efforts, operational support, and anomaly investigations. The space environment capabilities of the Natural Environments Branch at MSFC will be presented. These capabilities include model development, analysis of space and terrestrial related data, spacecraft charging anomaly investigations, surface charging modeling (e.g., Nascap-2k), space environment definition and radiation assessments for electronic parts. All aspects of space and terrestrial design are implemented with the goal of devising missions that are successful from launch to operations in the space environment of LEO, polar, GEO, and interplanetary orbits. We will show examples of recent applications of branch capabilities to NASA missions.

Parker, L. Neergaard↗
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↗