Engineering PapersSearch

Engineering topics

Goodman, John L.

Publications and source records attributed to Goodman, John L..

History and Archives Contribute to the Success of Space Flight Programs

Final Paper, not the Abstract, is attached: This report discusses how history can be used by management, engineering, and operations personnel within space flight programs. Works by professional historians and sociologists inform key decision makers and policy specialists on lessons learned from space flight program management successes and failures, as well as from legislative affairs, policy making, and commercial space efforts. Vehicle engineering history written by engineers for an engineering or operations audience informs project management and technical personnel on lessons learned, best practices, and the rationale behind the design and operation of flight vehicles and supporting ground systems. Archives play a critical role in supporting the efforts of both professional historians and flight program personnel. Suggestions are made concerning how professional historians could leverage the interests and knowledge of flight program personnel to obtain more insight that is needed to support historical research efforts.

Archive

Orion Burn Management, Nominal and Response to Failures

An approach for managing Orion on-orbit burn execution is described for nominal and failure response scenarios. The burn management strategy for Orion takes into account per-burn variations in targeting, timing, and execution; crew and ground operator intervention and overrides; defined burn failure triggers and responses; and corresponding on-board software sequencing functionality. Burn-to- burn variations are managed through the identification of specific parameters that may be updated for each progressive burn. Failure triggers and automatic responses during the burn timeframe are defined to provide safety for the crew in the case of vehicle failures, along with override capabilities to ensure operational control of the vehicle. On-board sequencing software provides the timeline coordination for performing the required activities related to targeting, burn execution, and responding to burn failures.

Odegard, Ryan

Encke-Beta Predictor for Orion Burn Targeting and Guidance

The state vector prediction algorithm selected for Orion on-board targeting and guidance is known as the Encke-Beta method. Encke-Beta uses a universal anomaly (beta) as the independent variable, valid for circular, elliptical, parabolic, and hyperbolic orbits. The variable, related to the change in eccentric anomaly, results in integration steps that cover smaller arcs of the trajectory at or near perigee, when velocity is higher. Some burns in the EM-1 and EM-2 mission plans are much longer than burns executed with the Apollo and Space Shuttle vehicles. Burn length, as well as hyperbolic trajectories, has driven the use of the Encke-Beta numerical predictor by the predictor/corrector guidance algorithm in place of legacy analytic thrust and gravity integrals.

Robinson, Shane

History of Space Shuttle Rendezvous

This technical history is intended to provide a technical audience with an introduction to the rendezvous and proximity operations history of the Space Shuttle Program. It details the programmatic constraints and technical challenges encountered during shuttle development in the 1970s and over thirty years of shuttle missions. An overview of rendezvous and proximity operations on many shuttle missions is provided, as well as how some shuttle rendezvous and proximity operations systems and flight techniques evolved to meet new programmatic objectives. This revised edition provides additional information on Mercury, Gemini, Apollo, Skylab, and Apollo/Soyuz. Some chapters on the Space Shuttle have been updated and expanded. Four special focus chapters have been added to provide more detailed information on shuttle rendezvous. A chapter on the STS-39 mission of April/May 1991 describes the most complex deploy/retrieve mission flown by the shuttle. Another chapter focuses on the Hubble Space Telescope servicing missions. A third chapter gives the reader a detailed look at the February 2010 STS-130 mission to the International Space Station. The fourth chapter answers the question why rendezvous was not completely automated on the Gemini, Apollo, and Space Shuttle vehicles.

Goodman, John L.

Hubble Servicing Challenges Drive Innovation of Shuttle Rendezvous Techniques

Hubble Space Telescope (HST) servicing, performed by Space Shuttle crews, has contributed to what is arguably one of the most successful astronomy missions ever flown. Both nominal and contingency proximity operations techniques were developed to enable successful servicing, while lowering the risk of damage to HST systems, and improve crew safety. Influencing the development of these techniques were the challenges presented by plume impingement and HST performance anomalies. The design of both the HST and the Space Shuttle was completed before the potential of HST contamination and structural damage by shuttle RCS jet plume impingement was fully understood. Relative navigation during proximity operations has been challenging, as HST was not equipped with relative navigation aids. Since HST reached orbit in 1990, proximity operations design for servicing missions has evolved as insight into plume contamination and dynamic pressure has improved and new relative navigation tools have become available. Servicing missions have provided NASA with opportunities to gain insight into servicing mission design and development of nominal and contingency procedures. The HST servicing experiences and lessons learned are applicable to other programs that perform on-orbit servicing and rendezvous, both human and robotic.

Goodman, John L.

Rendezvous Integration Complexities of NASA Human Flight Vehicles

Propellant-optimal trajectories, relative sensors and navigation, and docking/capture mechanisms are rendezvous disciplines that receive much attention in the technical literature. However, other areas must be considered. These include absolute navigation, maneuver targeting, attitude control, power generation, software development and verification, redundancy management, thermal control, avionics integration, robotics, communications, lighting, human factors, crew timeline, procedure development, orbital debris risk mitigation, structures, plume impingement, logistics, and in some cases extravehicular activity. While current and future spaceflight programs will introduce new technologies and operations concepts, the complexity of integrating multiple systems on multiple spacecraft will remain. The systems integration task may become more difficult as increasingly complex software is used to meet current and future automation, autonomy, and robotic operation requirements.

Brazzel, Jack P.

Apollo 13 Guidance, Navigation, and Control Challenges

Combustion and rupture of a liquid oxygen tank during the Apollo 13 mission provides lessons and insights for future spacecraft designers and operations personnel who may never, during their careers, have participated in saving a vehicle and crew during a spacecraft emergency. Guidance, Navigation, and Control (GNC) challenges were the reestablishment of attitude control after the oxygen tank incident, re-establishment of a free return trajectory, resolution of a ground tracking conflict between the LM and the Saturn V S-IVB stage, Inertial Measurement Unit (IMU) alignments, maneuvering to burn attitudes, attitude control during burns, and performing manual GNC tasks with most vehicle systems powered down. Debris illuminated by the Sun and gaseous venting from the Service Module (SM) complicated crew attempts to identify stars and prevented execution of nominal IMU alignment procedures. Sightings on the Sun, Moon, and Earth were used instead. Near continuous communications with Mission Control enabled the crew to quickly perform time critical procedures. Overcoming these challenges required the modification of existing contingency procedures.

Goodman, John L.

Best Practices for Researching and Documenting Lessons Learned

Identification, resolution, and avoidance of technical and programmatic issues are important for ensuring safe and successful space missions. Although the importance of applying lessons learned to reduce risk is frequently stressed, there is little material available to help technical and management personnel research and document lessons learned. Collecting, researching, identifying, and documenting lessons learned that will be useful to current and future management and engineering personnel is not always a straightforward task. This white paper presents lessons learned and best practices concerning the research and documentation of technical and organizational lessons learned. It is intended to enable organizations to initiate or improve lessons learned research and documentation efforts. The content of this white paper is based on four technical lessons learned projects conducted by the United Space Alliance (USA) Flight Design and Dynamics Department, in support of the NASA/Johnson Space Center (JSC) Flight Design and Dynamics Division. Each project published a report, titled as follows: (1) GPS Lessons Learned From the ISS, Space Shuttle and X-38; (2) Lessons Learned From Seven Space Shuttle Missions; (3) Space Shuttle Rendezvous and Proximity Operations Experience Report; and (4) Navigation Technical History with Lessons Learned. The four projects were different in availability of subject matter experts and primary source material, subject scope, and the level of effort required to produce the final report. However, generic lessons can be drawn from all of them. The best practices will be discussed by the phases of report research and development: (1) Defining Report Requirements, Project Organization, and Schedule; (2) Collection and Analysis of Source Material; (3) Writing and Integrating the Report; and (4) Review and Revision of the Report.

Goodman, John L.

Operational Use of GPS Navigation for Space Shuttle Entry

The STS-118 flight of the Space Shuttle Endeavour was the first shuttle mission flown with three Global Positioning System (GPS) receivers in place of the three legacy Tactical Air Navigation (TACAN) units. This marked the conclusion of a 15 year effort involving procurement, missionization, integration, and flight testing of a GPS receiver and a parallel effort to formulate and implement shuttle computer software changes to support GPS. The use of GPS data from a single receiver in parallel with TACAN during entry was successfully demonstrated by the orbiters Discovery and Atlantis during four shuttle missions in 2006 and 2007. This provided the confidence needed before flying the first all GPS, no TACAN flight with Endeavour. A significant number of lessons were learned concerning the integration of a software intensive navigation unit into a legacy avionics system. These lessons have been taken into consideration during vehicle design by other flight programs, including the vehicle that will replace the Space Shuttle, Orion.

Goodman, John L.

GPS Lessons Learned from the International Space Station, Space Shuttle and X-38

This document is a collection of writings concerning the application of Global Positioning System (GPS) technology to the International Space Station (ISS), Space Shuttle, and X-38 vehicles. An overview of how GPS technology was applied is given for each vehicle, including rationale behind the integration architecture, and rationale governing the use (or non-use) of GPS data during flight.

Goodman, John L.

Knowledge Capture and Management for Space Flight Systems

The incorporation of knowledge capture and knowledge management strategies early in the development phase of an exploration program is necessary for safe and successful missions of human and robotic exploration vehicles over the life of a program. Following the transition from the development to the flight phase, loss of underlying theory and rationale governing design and requirements occur through a number of mechanisms. This degrades the quality of engineering work resulting in increased life cycle costs and risk to mission success and safety of flight. Due to budget constraints, concerned personnel in legacy programs often have to improvise methods for knowledge capture and management using existing, but often sub-optimal, information technology and archival resources. Application of advanced information technology to perform knowledge capture and management would be most effective if program wide requirements are defined at the beginning of a program.

Goodman, John L.

Rendezvous and Proximity Operations of the Space Shuttle

Space Shuttle rendezous missions presented unique challenges that were not fully recognized when the Shuttle was designed. Rendezvous targets could be passive (i.e., no lights or transponders), and not designed to facilitate Shuttle rendezvous, proximity operations and retrieval. Shuttle reaction control system jet plume impingement on target spacecraft presented induced dynamics, structural loading and contamination concerns. These issues, along with limited forward reaction control system propellant, drove a change from the Gemimi/Apollo coelliptic profile heritage to a stable orbit profile, and the development of new proximity operations techniques. Multiple scientific and on-orbit servicing missions and crew exchange, assembly and replinishment flights to Mir and to the International Space Station drove further profile and piloting technique changes, including new relative navigation sensors and new computer generated piloting cues.

Goodman, John L.

Rendezvous and Proximity Operations of the Space Shuttle

Space Shuttle rendezvous missions present unique challenges that were not fully recognized when the Shuttle was designed. Rendezvous targets could be passive (i.e., no lights or transponders), and not designed to facilitate Shuttle rendezvous, proximity operations, and retrieval. Shuttle reaction control system jet plume impingement on target spacecraft presented induced dynamics, structural loading, and contamination concerns. These issues, along with limited reaction control system propellant in the Shuttle nose, drove a change from the legacy Gemini/Apollo coelliptic profile to a stable orbit profile, and the development of new proximity operations techniques. Multiple scientific and on-orbit servicing missions, and crew exchange, assembly and replenishment flights to Mir and to the International Space Station drove further profile and piloting technique changes. These changes included new proximity operations, relative navigation sensors, and new computer generated piloting cues. However, the Shuttle's baseline rendezvous navigation system has not required modification to place the Shuttle at the proximity operations initiation point for all rendezvous missions flown.

Goodman, John L.

Advanced GPS Technology For Automated/Autonomous Shuttle Missions

Test flights of a GPS receiver to replace TACAN began in 1996. Each orbiter has one GPS receiver. After RTF, ramp-up to single string GPS use will commence. Endeavour is undergoing TACAN removal and upgrade to three string GPS. GPS is not used for ascent and is powered on prelaunch to support an emergency landing. GPS has limited use for orbital operations and is not used for Rendezvous and docking. GPS will supplement or replace TACAN, but cannot be used as an MLS replacement. GPS enhances Shuttle navigation and improves safety. State-of-the-art GPS receivers have capabilities that would be useful in supporting automated/autonomous missions.

Goodman, John L.

Global Scale Observations of Ionospheric Instabilities from GPS in Low Earth Orbit

The GPS receiver used for navigation on the Space Shuttle exhibits range rate noise which appears to result from scintillation of the satellite signals by irregularities in ionospheric plasma. The noise events cluster in geographic regions previously identified as susceptible to instability and disturbed ionospheric conditions. These mechanisms are reviewed in the context of the GPS observations. Range rate data continuously monitored during the free orbiting phase of several space shuttle missions reveals global scale distribution of ionospheric irregularities. Equatorial events cluster +/- 20 degrees about the magnetic equator and polar events exhibit hemispheric asymmetry suggesting influence of off axis geomagnetic polar oval system. The diurnal, seasonal and geographic distribution is compared to previous work concerning equatorial spread F, Appleton anomaly and polar oval. The observations provide a succinct demonstration of the utility of space based ionospheric monitoring using GPS. The susceptability of GPS receivers to scintillation represents 'an unanticipated technical risk not factored into the selection of receivers for the United States space program.

Kramer, Leonard

Space Shuttle Navigation in the GPS Era

The Space Shuttle navigation architecture was originally designed in the 1970s. A variety of on-board and ground based navigation sensors and computers are used during the ascent, orbit coast, rendezvous, (including proximity operations and docking) and entry flight phases. With the advent of GPS navigation and tightly coupled GPS/INS Units employing strapdown sensors, opportunities to improve and streamline the Shuttle navigation process are being pursued. These improvements can potentially result in increased safety, reliability, and cost savings in maintenance through the replacement of older technologies and elimination of ground support systems (such as Tactical Air Control and Navigation (TACAN), Microwave Landing System (MLS) and ground radar). Selection and missionization of "off the shelf" GPS and GPS/INS units pose a unique challenge since the units in question were not originally designed for the Space Shuttle application. Various options for integrating GPS and GPS/INS units with the existing orbiter avionics system were considered in light of budget constraints, software quality concerns, and schedule limitations. An overview of Shuttle navigation methodology from 1981 to the present is given, along with how GPS and GPS/INS technology will change, or not change, the way Space Shuttle navigation is performed in the 21 5 century.

Goodman, John L.

Scintillation Effects on Space Shuttle GPS Data

Irregularities in ionospheric electron density result in variation in amplitude and phase of Global Positioning System (GPS) signals, or scintillation. GPS receivers tracking scintillated signals may lose carrier phase or frequency lock in the case of phase sc intillation. Amplitude scintillation can cause "enhancement" or "fading" of GPS signals and result in loss of lock. Scintillation can occur over the equatorial and polar regions and is a function of location, time of day, season, and solar and geomagnetic activity. Mid latitude regions are affected only very rarely, resulting from highly disturbed auroral events. In the spring of 1998, due to increasing concern about scintillation of GPS signals during the upcoming solar maximum, the Space Shuttle Program began to assess the impact of scintillation on Collins Miniaturized Airborne GPS Receiver (MAGR) units that are to replace Tactical Air Control and Navigation (TACAN) units on the Space Shuttle orbiters. The Shuttle Program must determine if scintillation effects pose a threat to safety of flight and mission success or require procedural and flight rule changes. Flight controllers in Mission Control must understand scintillation effects on GPS to properly diagnose "off nominal" GPS receiver performance. GPS data from recent Space Shuttle missions indicate that the signals tracked by the Shuttle MAGR manifest scintillation. Scintillation is observed as anomalous noise in velocity measurements lasting for up to 20 minutes on Shuttle orbit passes and are not accounted for in the error budget of the MAGR accuracy parameters. These events are typically coincident with latitude and local time occurrence of previously identified equatorial spread F within about 20 degrees of the magnetic equator. The geographic and seasonal history of these events from ground-based observations and a simple theoretical model, which have potential for predicting events for operational purposes, are reviewed.

Goodman, John L.