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 activities and results of the test and operations program performed on the three orbiter spacecraft (VO-1, VO-2, and VO-3) are described. The period from receipt of orbiter hardware at the Spacecraft Assembly Facility at JPL through shipment of the orbiter systems and support equipment to the Air Force Eastern Test Range is covered.
All manpower numbers, number of heads (by skill), serial time and manhours have been accumulated and compiled on a per subtask basis in spreadsheet format for both the ground based and the space based data flows. To aid in identifying the facility resources required to process the Ground Based Orbital Transfer Vehicle (GBOTV) and/or the space based orbital transfer vehicle (SBOTV) through the ground facilities at Kennedy Space Center (KSC), a software application package was developed using a general purpose data base management system known as Data Flex. The facility requirements are used as the basic input to this software application. The resources of the KSC facility that could be used by orbital transfer vehicle program were digitized in the same format used to identify facility requirements. The facility capabilities were digitized in this format for subsequent, automated comparative analyses. Composite facility requirements are compared to each of the baseline facility capabilities and the system generates a relative score that indicates how each facility weighs against the composite requirements in relation to the other facilities in the set.
A simplified retrieval strategy for compiling automation-related bibliographies from NASA/RECON is presented. Two subsets of NASA Thesaurus subject terms were extracted: a primary list, which is used to obtain an initial set of citations; and a secondary list, which is used to limit or further specify a large initial set of citations. These subject term lists are presented in Appendix A as the Automated Technology Knowledge Base (ATKB) Thesaurus.
Kennedy Space Center (KSC) is developing knowledge-based systems to automate critical operations functions for the space shuttle fleet. Intelligent systems will monitor vehicle and ground support subsystems for anomalies, assist in isolating and managing faults, and plan and schedule shuttle operations activities. These applications are being developed independently of one another, using different representation schemes, reasoning and control models, and hardware platforms. KSC has recently initiated the EXODUS project to integrate these stand alone applications into a unified, coordinated intelligent operations support system. EXODUS will be constructed using SOCIAL, a tool for developing distributed intelligent systems. EXODUS, SOCIAL, and initial prototyping efforts using SOCIAL to integrate and coordinate selected EXODUS applications are described.
No abstract available
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Launch site impacts and integration planning issues are presented to support launch operations for a mixed vehicle fleet (manned and cargo). Proposed ground systems and launch site configurations are described. Prelaunch processing scenarios and schedules are developed for candidate launch vehicles. Earth-to-orbit (ETO) vehicle architectures are presented to meet future launch requirements, including the Space Exploration Initiative (SEI). Flight vehicle design recommendations to enhance launch processing are discussed. The significance of operational designs for future launch vehicles is shown to be a critical factor in planning for mixed fleet launch site operations.
Topics dealing with nuclear safety are addressed which include the following: general safety requirements; safety design requirements; terrestrial safety; SP-100 Flight System key safety requirements; potential mission accidents and hazards; key safety features; ground operations; launch operations; flight operations; disposal; safety concerns; licensing; the nuclear engine for rocket vehicle application (NERVA) design philosophy; the NERVA flight safety program; and the NERVA safety plan.
The Aerospace industry has a long history of using low density polyurethane and polyurethane-modified isocyanurate foam systems as lightweight, low cost, easily processed cryogenic Thermal Protection Systems (TPS) for ascent vehicles. The Thermal Protection System of the Space Shuttle External Tank (ET) is required so that quality liquid cryogenic propellant can be supplied to the Orbiter main engines and to protect the metal structure of the tanks from becoming too hot from aerodynamic heating, hence preventing premature break-up of the tank. These foams are all blown with CFC-1 I blowing agent which has been identified by the Environmental Protection Agency (EPA) as an ozone depleting substance. CFCs will not be manufactured after 1995, Consequently, alternate blowing agent substances must be identified and implemented to assure continued ET manufacture and delivery. This paper describes the various testing performed to select and qualify HCFC-1 41 b as a near term drop-in replacement for CFC-11. Although originally intended to be a one for one substitution in the formulation, several technical issues were identified regarding material performance and processability which required both formulation changes and special processing considerations to overcome. In order to evaluate these material changes, each material was subjected to various tests to qualify them to meet the various loads imposed on them during long term storage, pre-launch operations, launch, separation and re-entry. Each material was tested for structural, thermal, aeroshear, and stress/strain loads for the various flight environments each encounters. Details of the development and qualification program and the resolution of specific problems are discussed in this paper.
This video of a briefing to representatives from the national media took the form of a slide show presentation by Jon Cowart, Manager of the Resident Office at Johnson Space Center. The presentation was an overview of ground maintainance facilities and procedures at Kennedy Space Center used to support Space Shuttle operations. The photographs in the slide show: Shuttle ground transport, maintenance, computers, and payloads, the Vehicle Assembly Building, ground operations, launch operations, crew boarding, liftoff, Pad A and Pad B, Solid Rocket Motor retrieval, crew procedures on-orbit, and landing. After the presentation is a brief question and answer session, in which reporters ask Cowart about Shuttle readiness, changes in Shuttle operations made for the Return to Flight, and how weather affects Shuttle operations.
Outline: Selected Historic Shuttle Operations Data; Shuttle Lessons Learned Recommendations for Lower Cost, Operationally Efficient Launch Vehicle Systems; Selected Expendable launch vehicle experiences; Past NASA Launch Vehicle Development Programs, Studies (1985 to present); Discussion: Suggested applications of NASA Lessons Learned to already-baselined contractor XS-1 Phase I concepts.
Launch vehicle operational flight trajectory for Saturn IB vehicle AS-202
Operational experience of Saturn/Apollo space vehicle checkout and launch
Spitzer Space Telescope was launched on 25 August 2003 into an Earth-trailing solar orbit to acquire infrared observations from space. Development of the Mission Operations System (MOS) portion prior to launch was very different from planetary missions from the stand point that the MOS teams and Ground Data System had to be ready to support all aspects of the mission at launch (i.e., no cruise period for finalizing the implementation). For Spitzer, all mission-critical events post launch happen in hours or days rather than months or years, as is traditional with deep space missions. At the end of 2000 the Project was dealt a major blow when the Mission Operations System (MOS) had an unsuccessful Critical Design Review (CDR). The project made major changes at the beginning of 2001 in an effort to get the MOS (and Project) back on track. The result for the Spitzer Space Telescope was a successful launch of the observatory followed by an extremely successful In Orbit Checkout (IOC) and operations phase. This paper describes how the project was able to recover the MOS to a successful Delta (CDR) by mid 2001, and what changes in philosophies, experiences, and lessons learned followed. It describes how projects must invest early or else invest heavily later in the development phase to achieve a successful operations phase.
The 12-km resolution North American Mesoscale (NAM) model (MesoNAM) is used by the 45th Weather Squadron (45 WS) Launch Weather Officers at Kennedy Space Center (KSC) and Cape Canaveral Air Force Station (CCAFS) to support space launch weather operations. The 45 WS tasked the Applied Meteorology Unit to conduct an objective statistics-based analysis of MesoNAM output compared to wind tower mesonet observations and then develop a an operational tool to display the results. The National Centers for Environmental Prediction began running the current version of the MesoNAM in mid-August 2006. The period of record for the dataset was 1 September 2006 - 31 January 2010. The AMU evaluated MesoNAM hourly forecasts from 0 to 84 hours based on model initialization times of 00, 06, 12 and 18 UTC. The MesoNAM forecast winds, temperature and dew point were compared to the observed values of these parameters from the sensors in the KSC/CCAFS wind tower network. The data sets were stratified by model initialization time, month and onshore/offshore flow for each wind tower. Statistics computed included bias (mean difference), standard deviation of the bias, root mean square error (RMSE) and a hypothesis test for bias = O. Twelve wind towers located in close proximity to key launch complexes were used for the statistical analysis with the sensors on the towers positioned at varying heights to include 6 ft, 30 ft, 54 ft, 60 ft, 90 ft, 162 ft, 204 ft and 230 ft depending on the launch vehicle and associated weather launch commit criteria being evaluated. These twelve wind towers support activities for the Space Shuttle (launch and landing), Delta IV, Atlas V and Falcon 9 launch vehicles. For all twelve towers, the results indicate a diurnal signal in the bias of temperature (T) and weaker but discernable diurnal signal in the bias of dewpoint temperature (T(sub d)) in the MesoNAM forecasts. Also, the standard deviation of the bias and RMSE of T, T(sub d), wind speed and wind direction indicated the model error increased with the forecast period all four parameters. The hypothesis testing uses statistics to determine the probability that a given hypothesis is true. The goal of using the hypothesis test was to determine if the model bias of any of the parameters assessed throughout the model forecast period was statistically zero. For th is dataset, if this test produced a value >= -1 .96 or <= 1.96 for a data point, then the bias at that point was effectively zero and the model forecast for that point was considered to have no error. A graphical user interface (GUI) was developed so the 45 WS would have an operational tool at their disposal that would be easy to navigate among the multiple stratifications of information to include tower locations, month, model initialization times, sensor heights and onshore/offshore flow. The AMU developed the GUI using HyperText Markup Language (HTML) so the tool could be used in most popular web browsers with computers running different operating systems such as Microsoft Windows and Linux.
The Saturn Launch Vehicle Operations Simulator (LVOS) was developed for NASA at Kennedy Space Center. LVOS simulates the Saturn launch vehicle and its ground support equipment. The simulator was intended primarily to be used as a launch crew trainer but it is also being used for test procedure and software validation. A NASA/contractor team of engineers and programmers implemented the simulator after the Apollo XI lunar landing during the low activity periods between launches.