SEARCH · Search NASA
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 STS-7 press briefing schedule, NASA select television schedule; launch preparations, countdown and liftoff; major countdown milestones; launch window; STS-7 flight sequence of events, landing timeline; STS-7 flight timeline; landing and post landing operations; flight objectives; Telesat's ANIK-C 2; PALAPA-B; STS-7 experiments; and spacecraft tracking and data network are presented.
The performance of the thermal protection system, field joint protection system, and systems tunnel components of Flight Set 360L006, are documented, as evaluated by postflight hardware inspection. The condition of both motors was similar to previous flights. Sixteen aft edge hits were noted on the ground environment instrumentation thermal protection system. Each hit left a clean substrate, indicating that the damage was caused by nozzle severance debris and/or water impact. No National Space and Transporation System debris criteria for missing thermal protection system were violated. One 5.0 by 1.0 in. unbond was observed on the left hand center field joint K5NA closeout and was elevated to an in-flight anomaly (STS-34-M-4) by the NASA Ice/Debris team. Aft edge damage to the K5NA and an associated black streak indicate that burning debris from the nozzle severance system was the likely cause of the damage. Minor divots caused by debris were seen on previous flights, but this is the first occurrence of a K5NA unbond. Since the unbond occurred after booster separation there is no impact on flight safety and no corrective actions was taken. The right hand center field joint primary heater failed the dielectric withstanding voltage test after joint closeout. The heater was then disabled by opening the circuit breaker, and the redundant heater was used. The redundant heater performed nominally during the launch countdown. A similar condition occurred on Flight 4 when a secondary joint heater failed the dielectric withstanding voltage test.
Lightning plays a pivotal role in the operation decision process for space and ballistic launches at Cape Canaveral Air Force Station and Kennedy Space Center. Lightning forecasts are the responsibility of Detachment 11, 4th Weather Wing's Cape Canaveral Forecast Facility. These forecasts are important to daily ground processing as well as launch countdown decisions. The methodology and equipment used to forecast lightning are discussed. Impact on a recent mission is summarized.
This paper is a consolidated report on ten major planning and scheduling systems that have been developed by the National Aeronautics and Space Administration (NASA). A description of each system, its components, and how it could be potentially used in private industry is provided in this paper. The planning and scheduling technology represented by the systems ranges from activity based scheduling employing artificial intelligence (AI) techniques to constraint based, iterative repair scheduling. The space related application domains in which the systems have been deployed vary from Space Shuttle monitoring during launch countdown to long term Hubble Space Telescope (HST) scheduling. This paper also describes any correlation that may exist between the work done on different planning and scheduling systems. Finally, this paper documents the lessons learned from the work and research performed in planning and scheduling technology and describes the areas where future work will be conducted.
NASA executives gathered together for an interview to discuss the 1998 Mars Mission. A simulated overview of the Lander Mission is presented. Also presented are views of pre-launch activities, countdown, and launch of the spacecraft, burnouts of the first, second, and third engines, and the probe separating from the spacecraft. During this mission the Lander performs in situ investigations that address the science theme "Volatiles and Climate History" on Mars. The purpose of this mission is to study the following: climate; life; water; carbon dioxide; and dust particles.
Dick Young, NASA Public Affairs, introduces Brewster Shaw, Deputy Program Manager Space Shuttle, Professor Heinz Stoewer, D-2 Program Manager German Space Agency, and Bob Sieck, Launch Director, Kennedy Space Center, who give an overview of the mission and the launch countdown. They then answer questions from the press.
The use of a quadrupole ion trap mass spectrometer for quantitative analysis of hydrogen and helium as well as other permanent gases is demonstrated. The customized instrument utilizes the mass selective instability mode of mass analysis as with commercial instruments; however, this instrument operates at a greater RF trapping frequency and without a buffer gas. With these differences, a useable mass range from 2 to over 50 Da is achieved, as required by NASA for monitoring the Space Shuttle during a launch countdown. The performance of the ion trap is evaluated using part-per-million concentrations of hydrogen, helium, oxygen and argon mixed into a nitrogen gas stream. Relative accuracy and precision when quantitating the four analytes were better than the NASA-required minimum of 10% error and 5% deviation, respectively. Limits of detection were below the NASA requirement of 25-ppm hydrogen and 100-ppm helium; those for oxygen and argon were slightly higher than the requirement. The instrument provided adequate performance at fast data recording rates, demonstrating the utility of an ion trap mass spectrometer as a real-time quantitative monitoring device for permanent gas analysis.
The Environments Group at the National Aeronautics and Space Administration's Marshall Space Flight Center monitors the winds aloft above Kennedy Space Center (KSC) in support of the Space Shuttle Program day-of-launch operations. Assessment of tropospheric winds is used to support the ascent phase of launch. Three systems at KSC are used to generate independent tropospheric wind profiles prior to launch; 1) high resolution jimsphere balloon system, 2) 50-MHz Doppler Radar Wind Profiler (DRWP) and 3) low resolution radiosonde system. All independent sources are compared against each other for accuracy. To assess spatial and temporal wind variability during launch countdown each jimsphere profile is compared against a design wind database to ensure wind change does not violate wind change criteria.
The NESC consultation team participated in real-time troubleshooting of the Main Propulsion System (MPS) Engine Cutoff (ECO) sensor system failures during STS-114 launch countdown. The team assisted with External Tank (ET) thermal and ECO Point Sensor Box (PSB) circuit analyses, and made real-time inputs to the Space Shuttle Program (SSP) problem resolution teams. Several long-term recommendations resulted. One recommendation was to conduct cryogenic tests of the ECO sensors to validate, or disprove, the theory that variations in circuit impedance due to cryogenic effects on swaged connections within the sensor were the root cause of STS-114 failures.
The purpose of this paper is to document the modeling considerations and performance metrics that were examined in the development of a large-scale Fault Detection, Isolation and Recovery (FDIR) system. The FDIR system is envisioned to perform health management functions for both a launch vehicle and the ground systems that support the vehicle during checkout and launch countdown by using suite of complimentary software tools that alert operators to anomalies and failures in real-time. The FDIR team members developed a set of operational requirements for the models that would be used for fault isolation and worked closely with the vendor of the software tools selected for fault isolation to ensure that the software was able to meet the requirements. Once the requirements were established, example models of sufficient complexity were used to test the performance of the software. The results of the performance testing demonstrated the need for enhancements to the software in order to meet the demands of the full-scale ground and vehicle FDIR system. The paper highlights the importance of the development of operational requirements and preliminary performance testing as a strategy for identifying deficiencies in highly scalable systems and rectifying those deficiencies before they imperil the success of the project
The purpose of this paper is to present the conventions, best practices, and processes that were established based on the prototype development of a Functional Fault Model (FFM) for a Cryogenic System that would be used for real-time Fault Isolation in a Fault Detection, Isolation, and Recovery (FDIR) system. The FDIR system is envisioned to perform health management functions for both a launch vehicle and the ground systems that support the vehicle during checkout and launch countdown by using a suite of complimentary software tools that alert operators to anomalies and failures in real-time. The FFMs were created offline but would eventually be used by a real-time reasoner to isolate faults in a Cryogenic System. Through their development and review, a set of modeling conventions and best practices were established. The prototype FFM development also provided a pathfinder for future FFM development processes. This paper documents the rationale and considerations for robust FFMs that can easily be transitioned to a real-time operating environment.
The SGOS executive and its subsystems have been an integral component of the Shuttle Launch Safety Program for almost thirty years. It is usable (via the LAN) by over 2000 NASA employees at the Kennedy Space Center and 11,000 contractors. SGOS supports over 800 models comprised of several hundred thousand lines of code and over 1,000 MCP procedures. Yet neither language has a for loop!! The simulation software described in this paper is used to train ground controllers and to certify launch countdown readiness.
During launch countdown, at approximately T-7 seconds, the Space Shuttle Main Engines (SSMEs) roar to life. When the controllers indicate normal operation, the solid rocket boosters ignite and the shuttle blasts off. Initially, the SSMEs throttle down to reduce stress during the period of maximum dynamic pressure, but soon after, they throttle up to propel the orbiter to 17,500 miles per hour. In just under 9 minutes, the three SSMEs burn over 1.6 million pounds of propellant, and temperatures inside the main combustion chamber reach 6,000 F. To cool the engines, liquid hydrogen circulates through miles of tubing at -423 F. From 1981to 2011, the Space Shuttle fleet carried crew and cargo into orbit to perform a myriad of unprecedented tasks. After 30 years and 135 missions, the feat of engineering known as the SSME boasted a 100-percent flight success rate.
NASA's future human space exploration strategy includes single and multi-launch missions to various destinations including cis-lunar space, near Earth objects such as asteroids, and ultimately Mars. Each campaign is being defined by Design Reference Missions (DRMs). Many of these missions are complex, requiring multiple launches and assembly of vehicles in orbit. Certain missions also have constrained departure windows to the destination. These factors raise concerns regarding the reliability of launching and assembling all required elements in time to support planned departure. This paper describes an integrated methodology for analyzing launch and assembly reliability in any single DRM or set of DRMs starting with flight hardware manufacturing and ending with final departure to the destination. A discrete event simulation is built for each DRM that includes the pertinent risk factors including, but not limited to: manufacturing completion; ground transportation; ground processing; launch countdown; ascent; rendezvous and docking, assembly, and orbital operations leading up to trans-destination-injection. Each reliability factor can be selectively activated or deactivated so that the most critical risk factors can be identified. This enables NASA to prioritize mitigation actions so as to improve mission success.
The SGOS executive and its subsystems have been an integral component of the Shuttle Launch Safety Program for almost thirty years. it is usable (via the LAN) by over 2000 NASA employees at the Kennedy Space Center and 11,000 contractors. SGOS supports over 800 models comprised of several hundred thousand lines of code and over 1,00 MCP procedures. Yet neither language has a for loop!! The simulation software described in this paper is used to train ground controllers and to certify launch countdown readiness.
On the day-of-launch, the 45th Weather Squadron (45 WS) Launch Weather Officers (LWOs) monitor the upper-level winds for their launch customers to include NASA's Launch Services Program and NASA's Ground Systems Development and Operations Program. They currently do not have the capability to display and overlay profiles of upper-level observations and numerical weather prediction model forecasts. The LWOs requested the Applied Meteorology Unit (AMU) develop a tool in the form of a graphical user interface (GUI) that will allow them to plot upper-level wind speed and direction observations from the Kennedy Space Center (KSC) 50 MHz tropospheric wind profiling radar, KSC Shuttle Landing Facility 915 MHz boundary layer wind profiling radar and Cape Canaveral Air Force Station (CCAFS) Automated Meteorological Processing System (AMPS) radiosondes, and then overlay forecast wind profiles from the model point data including the North American Mesoscale (NAM) model, Rapid Refresh (RAP) model and Global Forecast System (GFS) model to assess the performance of these models. The AMU developed an Excel-based tool that provides an objective method for the LWOs to compare the model-forecast upper-level winds to the KSC wind profiling radars and CCAFS AMPS observations to assess the model potential to accurately forecast changes in the upperlevel profile through the launch count. The AMU wrote Excel Visual Basic for Applications (VBA) scripts to automatically retrieve model point data for CCAFS (XMR) from the Iowa State University Archive Data Server (http://mtarchive.qeol.iastate.edu) and the 50 MHz, 915 MHz and AMPS observations from the NASA/KSC Spaceport Weather Data Archive web site (http://trmm.ksc.nasa.gov). The AMU then developed code in Excel VBA to automatically ingest and format the observations and model point data in Excel to ready the data for generating Excel charts for the LWO's. The resulting charts allow the LWOs to independently initialize the three models 0-hour forecasts against the observations to determine which is the best performing model and then overlay the model forecasts on time-matched observations during the launch countdown to further assess the model performance and forecasts. This paper will demonstrate integration of observed and predicted atmospheric conditions into a decision support tool and demonstrate how the GUI is implemented in operations.
This paper presents the process used by the Marshall Space Flight Center Natural Environments Branch (EV44) to quality control (QC) data from the Kennedy Space Center's 50-MHz Doppler Radar Wind Profiler for use in vehicle wind loads and steering commands. The database has been built to mitigate limitations of using the currently archived databases from weather balloons. The DRWP database contains wind measurements from approximately 2.7-18.6 km altitude at roughly five minute intervals for the August 1997 to December 2009 period of record, and the extensive QC process was designed to remove spurious data from various forms of atmospheric and non-atmospheric artifacts. The QC process is largely based on DRWP literature, but two new algorithms have been developed to remove data contaminated by convection and excessive first guess propagations from the Median Filter First Guess Algorithm. In addition to describing the automated and manual QC process in detail, this paper describes the extent of the data retained. Roughly 58% of all possible wind observations exist in the database, with approximately 100 times as many complete profile sets existing relative to the EV44 balloon databases. This increased sample of near-continuous wind profile measurements may help increase launch availability by reducing the uncertainty of wind changes during launch countdown
The Orion flight software’s parity algorithm runs onboard to verify all three OIMUs (Orion Inertial Measurement Units) are sensing relatively uniform rate and acceleration and to quickly identify any unit which is in significant disagreement with the other two units. During the Artemis-I Wet Dress Rehearsal tests and Launch Countdowns, one of the three OIMUs regularly reported an anomalous parity signature for a brief period of time during sensor warm up. This paper will review this anomalous performance on the pad and review flight data with the intent to supplement the findings of the initial root cause investigation. Outside of this start up behavior, initial investigation into Artemis I flight data did not reveal any behavior of the OIMUs outside of preflight expectations. Flight data from any significant parity events and relevant IMU calibrations will be presented. A brief discussion of impacts to future Artemis mission operations strategy will be provided.