Search NASA⌕ Search

SEARCH · Search NASA

Results for “Lessons”

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 397 records · Page 22

Lessons Learned with Metallized Gelled Propellants

During testing of metallized gelled propellants in a rocket engine, many changes had to be made to the normal test program for traditional liquid propellants. The lessons learned during the testing and the solutions for many of the new operational conditions posed with gelled fuels will help future programs run more smoothly. The major factors that influenced the success of the testing were propellant settling, piston-cylinder tank operation, control of self pressurization, capture of metal oxide particles, and a gelled-fuel protective layer. In these ongoing rocket combustion experiments at the NASA Lewis Research Center, metallized, gelled liquid propellants are used in a small modular engine that produces 30 to 40 lb of thrust. Traditional liquid RP-1 and gelled RP-1 with 0-, 5-, and 55-wt% loadings of aluminum are used with gaseous oxygen as the oxidizer. The figure compares the thrust chamber efficiencies of different engines.

Source record↗

Overview With Results and Lessons Learned of the X-43A Mach 10 Flight

This paper provides an overview of the final flight of the NASA X-43A project. The project consisted of three flights, two planned for Mach 7 and one for Mach 10. The third and final flight, November 16, 2004, was the first Mach 10 flight demonstration of an airframe-integrated, scramjet-powered, hypersonic vehicle. The goals and objectives for the project as well as those for the third flight are presented. The configuration of the Hyper-X stack including the X-43A, Hyper-X launch vehicle, and Hyper-X research vehicle adapter is discussed. The second flight of the X-43A was successfully conducted on March 27, 2004. Mission differences, vehicle modifications and lessons learned from the second flight as they applied to the third flight are also discussed. An overview of flight 3 results is presented.

Marshall, Laurie A.↗

Space Mechanisms Lessons Learned and Accelerated Testing Studies

A number of mechanism (mechanical moving component) failures and anomalies have recently occurred on satellites. In addition, more demanding operating and life requirements have caused mechanism failures or anomalies to occur even before some satellites were launched (e.g., during the qualification testing of GOES-NEXT, CERES, and the Space Station Freedom Beta Joint Gimbal). For these reasons, it is imperative to determine which mechanisms worked in the past and which have failed so that the best selection of mechanically moving components can be made for future satellites. It is also important to know where the problem areas are so that timely decisions can be made on the initiation of research to develop future needed technology. To chronicle the life and performance characteristics of mechanisms operating in a space environment, a Space Mechanisms Lessons Learned Study was conducted. The work was conducted by the NASA Lewis Research Center and by Mechanical Technologies Inc. (MTI) under contract NAS3-27086. The expectation of the study was to capture and retrieve information relating to the life and performance of mechanisms operating in the space environment to determine what components had operated successfully and what components had produced anomalies.

Fusaro, Robert L.↗

X-43A Fluid and Environmental Systems: Ground and Flight Operation and Lessons Learned

The X-43A Hyper-X program demonstrated the first successful flights of an airframe integrated scramjet powered hypersonic vehicle. The X-43A vehicles established successive world records for jet-powered vehicles at speeds of Mach 7 and Mach 10. The X-43A vehicle is a subscale version of proposed hypersonic reconnaissance strike aircraft. Scaled down to a length of 12 ft (3.66 m), the lifting body design with high fineness ratio resulted in very small internal space available for fluid systems and their corresponding environmental conditioning systems. Safe testing and operation of the X-43A fluid and environmental systems was critical for mission success, not only for the safety of the flight crew in the NASA B-52B carrier aircraft, but also to maintain the reliability of vehicle systems while exposed to dynamics and hostile conditions encountered during the boost trajectory. The X-43A fluid and environmental systems successfully managed explosive, pyrophoric, inert, and very high pressure gases without incident. This report presents a summary of the checkout and flight validation of the X-43A fluid systems. The testing used for mission assurance is summarized. System performance during captive carry and launch flights is presented. The lessons learned are also discussed.

Vachon, Michael Jacob↗

NASA Space Mechanisms Handbook: Lessons Learned Documented

The need to improve space mechanism reliability is underscored by a long history of flight failures and anomalies caused by malfunctioning mechanisms on spacecraft and launch vehicles. Some examples of these failures are listed in a table. Because much experience has been gained over the years, many specialized design practices have evolved and many unsatisfactory design approaches have been identified.NASA and the NASA Lewis Research Center conducted a Lessons Learned Study (refs. 1 and 2) and wrote a handbook to document what has been learned in the past. The primary goals of the handbook were to identify desirable and undesirable design practices for space mechanisms and to reduce the number of failures caused by the repetition of past design errors. Another goal was to identify a variety of design approaches for specific applications and to provide the associated considerations and caveats for each approach in an effort to help designers choose the approach most suitable for each application. This technical summary outlines the goals and objectives of the handbook and study as well as the contents of the handbook.

Fusaro, Robert L.↗

Welding in Space: Lessons Learned for Future In Space Repair Development

Welds have been made in the harsh environment of space only twice in the history of manned space flight. The United States conducted the M5 12 experiment on Skylab and the former Soviet Union conducted an Extravehicular Activity. Both experiments demonstrated electron beam welding. A third attempt to demonstrate and advance space welding was made by the Marshall Space Flight Center in the 90's but the experiment was demanifested as a Space Shuttle payload. This presentation summarizes the lessons learned from these three historical experiences in the areas of safety, design, operations and implementation so that welding in space can become an option for in space repair applications.

Russell, C. K.↗

An Overview of the Annual NASA Tire/Runway Friction Workshop and Lessons Learned

This paper summarizes the organization efforts, objectives, scope, agenda, test procedures and results from eleven years of conducting the NASA Tire/Runway Friction Workshop. The paper will also summarize the lessons learned between 1994 and 2004. A description of the various friction, texture and roughness equipment used during these workshops at NASA Wallops Flight Facility on the eastern shore of Virginia will be provided together with the range of test surfaces available for evaluation. The need for friction measuring equipment calibration centers is discussed and plans for future workshops are identified.

Yager, Thomas J.↗

Flying SATS Higher Volume Operations: Training, Lessons Learned, and Pilots' Experiences

Developments in aviation, including new surveillance technologies and quicker, more economical small aircraft, have been identified as driving factors in a potential expansion of the use of non-towered, non-radar airports. The Small Aircraft Transportation System (SATS) project has developed the Higher Volume Operations (HVO) concept that enables pilots to safely arrive and depart these airports in instrument conditions at an increased rate as compared to today's procedures. This is achieved by transferring some traffic management tasks to centralized, ground-based automation, while assigning others to participating pilots aided by on-board tools. This paper describes strategies and lessons learned while training pilots to fly these innovative operations. Pilot approaches to using the experimental displays and dynamic altering systems during training are discussed. Potential operational benefits as well as pit-falls and frustrations expressed by subjects while learning to fly these new procedures are presented. Generally, pilots were comfortable with the procedures and the training process, and expressed interest in its near-term implementation.

Conway, Sheila↗

Lessons Learned Implementing DOORS in a Citrix Environment

NASA's James Web Space Telescope (JWST) Project is a large multi-national project with geographically dispersed contractors that all need access to the Projects requirement database. Initially, the project utilized multiple DOORS databases with the built-in partitions feature to exchange modules amongst the various contractor sites. As the requirements databases matured the use of partitions became extremely difficult. There have been many issues such as incompatible versions of DOORS, inefficient mechanism for sharing modules, security concerns, performance issues, and inconsistent document import and export formats. Deployment of the client software with limited IT resources available was also an issue. The solution chosen by JWST was to integrate the use of a Citrix environment with the DOORS database to address most of the project concerns. The use of the Citrix solution allowed a single Requirements database in a secure environment via a web interface. The Citrix environment allows JWST to upgrade to the most current version of DOORS without having to coordinate multiple sites and user upgrades. The single requirements database eliminates a multitude of Configuration Management concerns and facilitated the standardization of documentation formats. This paper discusses the obstacles and the lessons learned throughout the installation, implementation, usage and deployment process of a centralized DOORS database solution.

Bussman, Marie↗

Lessons Learned From Developing Three Generations of Remote Sensing Science Data Processing Systems

The Biospheric Information Systems Branch at NASA s Goddard Space Flight Center has developed three generations of Science Investigator-led Processing Systems for use with various remote sensing instruments. The first system is used for data from the MODIS instruments flown on NASA s Earth Observing Systems @OS) Terra and Aqua Spacecraft launched in 1999 and 2002 respectively. The second generation is for the Ozone Measuring Instrument flying on the EOS Aura spacecraft launched in 2004. We are now developing a third generation of the system for evaluation science data processing for the Ozone Mapping and Profiler Suite (OMPS) to be flown by the NPOESS Preparatory Project (NPP) in 2006. The initial system was based on large scale proprietary hardware, operating and database systems. The current OMI system and the OMPS system being developed are based on commodity hardware, the LINUX Operating System and on PostgreSQL, an Open Source RDBMS. The new system distributes its data archive across multiple server hosts and processes jobs on multiple processor boxes. We have created several instances of this system, including one for operational processing, one for testing and reprocessing and one for applications development and scientific analysis. Prior to receiving the first data from OMI we applied the system to reprocessing information from the Solar Backscatter Ultraviolet (SBUV) and Total Ozone Mapping Spectrometer (TOMS) instruments flown from 1978 until now. The system was able to process 25 years (108,000 orbits) of data and produce 800,000 files (400 GiB) of level 2 and level 3 products in less than a week. We will describe the lessons we have learned and tradeoffs between system design, hardware, operating systems, operational staffing, user support and operational procedures. During each generational phase, the system has become more generic and reusable. While the system is not currently shrink wrapped we believe it is to the point where it could be readily adopted, with substantial cost savings, for other similar tasks.

Tilmes, Curt↗

Lessons Learned in the Livingstone 2 on Earth Observing One Flight Experiment

The Livingstone 2 (L2) model-based diagnosis software is a reusable diagnostic tool for monitoring complex systems. In 2004, L2 was integrated with the JPL Autonomous Sciencecraft Experiment (ASE) and deployed on-board Goddard's Earth Observing One (EO-1) remote sensing satellite, to monitor and diagnose the EO-1 space science instruments and imaging sequence. This paper reports on lessons learned from this flight experiment. The goals for this experiment, including validation of minimum success criteria and of a series of diagnostic scenarios, have all been successfully net. Long-term operations in space are on-going, as a test of the maturity of the system, with L2 performance remaining flawless. L2 has demonstrated the ability to track the state of the system during nominal operations, detect simulated abnormalities in operations and isolate failures to their root cause fault. Specific advances demonstrated include diagnosis of ambiguity groups rather than a single fault candidate; hypothesis revision given new sensor evidence about the state of the system; and the capability to check for faults in a dynamic system without having to wait until the system is quiescent. The major benefits of this advanced health management technology are to increase mission duration and reliability through intelligent fault protection, and robust autonomous operations with reduced dependency on supervisory operations from Earth. The work-load for operators will be reduced by telemetry of processed state-of-health information rather than raw data. The long-term vision is that of making diagnosis available to the onboard planner or executive, allowing autonomy software to re-plan in order to work around known component failures. For a system that is expected to evolve substantially over its lifetime, as for the International Space Station, the model-based approach has definite advantages over rule-based expert systems and limit-checking fault protection systems, as these do not scale well. The model-based approach facilitates reuse of the L2 diagnostic software; only the model of the system to be diagnosed and telemetry monitoring software has to be rebuilt for a new system or expanded for a growing system. The hierarchical L2 model supports modularity and expendability, and as such is suitable solution for integrated system health management as envisioned for systems-of-systems.

Hayden, Sandra C.↗

Constellation Operations: Lessons Learned For Future Exploration

The Earth science community has long advocated placing numerous instruments in space to study the Earth and its environment. Space agencies from many countries have responded to this call with a wide range of orbiting satellites. Scientists also envisioned placing some satellites in constellations, to enable diverse remote sensing instruments to observe the same part of the Earth (or its atmosphere) at about the same time, thereby increasing the opportunities for coincident science observations. The Earth Science Afternoon Constellation is answering this call, but there have been unique challenges on the way to its deployment. Currently, the Afternoon Constellation is to comprise six satellites. Three are currently on orbit: NASA's Earth Observing System (EOS)-Aqua (2002) and EOS-Aura (2004), and CNES's Polarization & Anisotropy of Reflectances for Atmospheric Sciences coupled with Observations from a Lidar (PARASOL) (2004). Two more satellites, the Cloud-Aerosol Lidar and Infrared Pathfinder Satellite Observation (CALIPSO) and Cloudsat, are to be jointly launched in late 2005, followed by the Orbiting Carbon Observatory (OCO) in 2008. The Afternoon Constellation is unlike most satellite constellations in that: 1) It is not a homogenous mix of identical satellites; rather it comprises several satellites with complementary observational capabilities; 2) The satellites are not spaced around the Earth to provide instantaneous, global coverage (as for a communications satellite constellation); rather they orbit in close proximity so observations occur at about the same time over approximately the same region; and 3) Lastly, the satellites are not managed and controlled by one organization; rather the list of organizations is diverse: CNES in France, NASA Centers at Goddard, Langley, and the Jet Propulsion Laboratory, and the US Air Force facility in New Mexico. The PARASOL launch and early orbit (L&EO) phase proved to be a learning experience for constellation members (including Constellation management). Prior to launch, all members signed an operations coordination document that spelled out basic requirements for keeping the constellation safe and resolving non-nominal events. Once PARASOL reached orbit and the mission teams gained experience using the newly-developed constellation monitoring tools, it became clear that some of the guidelines in the signed agreements had to be adjusted. This paper presents the L&EO lessons learned and how they were used to prepare for the next phase - the period following the CloudSat/CALIPSO launch.

Kelly, Angelita C.↗

Lessons Learned from Engineering a Multi-Mission Satellite Operations Center

NASA's Small Explorers (SMEX) satellites have surpassed their designed science-lifetimes and their flight operations teams are now facing the challenge of continuing operations with reduced funding. At present, these missions are being reengineered into a fleet-oriented ground system at Goddard Space Flight Center (GSFC). When completed, this ground system will provide command and control of four SMEX missions and will demonstrate fleet automation and control concepts. As a path-finder for future mission consolidation efforts, this ground system will also demonstrate new ground-based technologies that show promise of supporting longer mission lifecycles and simplifying component integration. One of the core technologies being demonstrated in the SMEiX Mission Operations Center is the GSFC Mission Services Evolution Center (GMSEC) architecture. The GMSEC architecture uses commercial Message Oriented Middleware with a common messaging standard to realize a higher level of component interoperability, allowing for interchangeable components in ground systems. Moreover, automation technologies utilizing the GMSEC architecture are being evaluated and implemented to provide extended lights-out operations. This mode of operation will provide routine monitoring and control of the heterogeneous spacecraft fleet. The operational concepts being developed will reduce the need for staffed contacts and is seen as a necessity for fleet management. This paper will describe the experiences of the integration team throughout the reengineering effort of the SMEX ground system. Additionally, lessons learned will be presented based on the team s experiences with integrating multiple missions into a fleet-based automated ground system.

Madden, Maureen↗

NASA Crew and Cargo Launch Vehicle Development Approach Builds on Lessons from Past and Present Missions

The United States (US) Vision for Space Exploration, announced in January 2004, outlines the National Aeronautics and Space Administration's (NASA) strategic goals and objectives, including retiring the Space Shuttle and replacing it with new space transportation systems for missions to the Moon, Mars, and beyond. The Crew Exploration Vehicle (CEV) that the new human-rated Crew Launch Vehicle (CLV) lofts into space early next decade will initially ferry astronauts to the International Space Station (ISS) Toward the end of the next decade, a heavy-lift Cargo Launch Vehicle (CaLV) will deliver the Earth Departure Stage (EDS) carrying the Lunar Surface Access Module (LSAM) to low-Earth orbit (LEO), where it will rendezvous with the CEV launched on the CLV and return astronauts to the Moon for the first time in over 30 years. This paper outlines how NASA is building these new space transportation systems on a foundation of legacy technical and management knowledge, using extensive experience gained from past and ongoing launch vehicle programs to maximize its design and development approach, with the objective of reducing total life cycle costs through operational efficiencies such as hardware commonality. For example, the CLV in-line configuration is composed of a 5-segment Reusable Solid Rocket Booster (RSRB), which is an upgrade of the current Space Shuttle 4- segment RSRB, and a new upper stage powered by the liquid oxygen/liquid hydrogen (LOX/LH2) J-2X engine, which is an evolution of the J-2 engine that powered the Apollo Program s Saturn V second and third stages in the 1960s and 1970s. The CaLV configuration consists of a propulsion system composed of two 5-segment RSRBs and a 33- foot core stage that will provide the LOX/LED needed for five commercially available RS-68 main engines. The J-2X also will power the EDS. The Exploration Launch Projects, managed by the Exploration Launch Office located at NASA's Marshall Space Flight Center, is leading the design, development, testing, and operations planning for these new space transportation systems. Utilizing a foundation of heritage hardware and management lessons learned mitigates both technical and programmatic risk. Project engineers and managers work closely with the Space Shuttle Program to transition hardware, infrastructure, and workforce assets to the new launch systems, leveraging a wealth of knowledge from Shuffle operations. In addition, NASA and its industry partners have tapped into valuable Apollo databases and are applying corporate wisdom conveyed firsthand by Apollo-era veterans of America s original Moon missions. Learning from its successes and failures, NASA employs rigorous systems engineering and systems management processes and principles in a disciplined, integrated fashion to further improve the probability of mission success.

Dumbacher, Daniel L.↗

Lessons Learned from Engineering a Multi-Mission Satellite Operations Center

NASA's Small Explorers (SMEX) satellites have surpassed their designed science-lifetimes and their flight operations teams are now facing the challenge of continuing operations with reduced funding. At present, these missions are being re-engineered into a fleet-oriented ground system at Goddard Space Flight Center (GSFC). When completed, this ground system will provide command and control of four SMEX missions and will demonstrate fleet automation and control concepts. As a path-finder for future mission consolidation efforts, this ground system will also demonstrate new ground-based technologies that show promise of supporting longer mission lifecycles and simplifying component integration. One of the core technologies being demonstrated in the SMEX Mission Operations Center is the GSFC Mission Services Evolution Center (GMSEC) architecture. The GMSEC architecture uses commercial Message Oriented Middleware with a common messaging standard to realize a higher level of component interoperability, allowing for interchangeable components in ground systems. Moreover, automation technologies utilizing the GMSEC architecture are being evaluated and implemented to provide extended lights-out operations. This mode of operation will provide routine monitoring and control of the heterogeneous spacecraft fleet. The operational concepts being developed will reduce the need for staffed contacts and is seen as a necessity for fleet management. This paper will describe the experiences of the integration team throughout the re-enginering effort of the SMEX ground system. Additionally, lessons learned will be presented based on the team's experiences with integrating multiple missions into a fleet-automated ground system.

Madden, Maureen↗

Mars Exploration Rover Potentiometer Problems, Failures and Lessons Learned

During qualification testing of three types of non-wire-wound precision potentiometers for the Mars Exploration Rover, a variety of problems and failures were encountered. This paper will describe some of the more interesting problems, detail their investigations and present their final solutions. The failures were found to be caused by design errors, manufacturing errors, improper handling, test errors, and carelessness. A trend of decreasing total resistance was noted, and a resistance histogram was used to identify an outlier. A gang fixture is described for simultaneously testing multiple pots, and real time X-ray imaging was used extensively to assist in the failure analyses. Lessons learned are provided.

Balzer, Mark↗

Lessons learned from SIR-C calibration

In this paper, lessons learned through the calibration of SIR-C data will be reviewed in the context of upcoming spaceborne, polarimetric SAR missions planned for launch later in this decade.

Synthetic Aperture Radar SAR polarimetry calibrati↗