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 433 records · Page 24
All sourcesNASA NTRSDOE OSTI
NASA NTRS2007

X-31 Mishap: Lessons Learned

The experimental X-31 High Angle of Attack Research Aircraft crashed during a 1995 test mission flight conducted by NASA at Edwards Air Force Base, California. The pilot lost control of the airplane and was forced to eject, sustaining a permanent back injury that ended his flying career. Prior to this incident the airplane had a perfect record of several hundred non-eventful flights supported by an experienced team. During the subsequent investigation by a mishap committee it was discovered that a series of cascading events contributed to this accident. Some of the identified contributing factors that resulted in this mishap are common to aircraft design and to flight-test in general. The mistakes and the solutions are presented here so that the flight-test community may consider and learn from them. The primary cause of the crash was icing and, ultimately, a complete blockage of the pitot-static nose probe. The icing was caused by a freak weather phenomenon that was neither expected nor known to exist on the day of the mishap. The normal probe had been replaced with a special Kiel probe to allow total pressure measurements of up to 70 degrees angle of attack for flight-test purposes. The Kiel probe did not include a heater, because it was assumed that the airplane would not be flown in the clouds or in conditions conducive to icing. This assumption was later proven to be incorrect. The iced Kiel probe caused incorrect gain scheduling in the flight control system, resulting in an unstable aircraft. This failure was essentially undetected because of a faulty design in the flight control system architecture. There were, however, also a number of other issues that lead up to this situation that never should have happened. This presentation discusses what the issues were that contributed to the incident. After the incident was investigated, some of these issues were addressed and some changes were made. The second X-31 aircraft flew the remainder of the flight tests, and the program was successfully completed without incident. This presentation also shows a video of the mishap including lessons learned, and the changes that were made to resume the flight-test program are presented.

Larson, Richard R.↗
NASA NTRS2004

Development of a State Machine Sequencer for the Keck Interferometer: Evolution, Development and Lessons Learned using a CASE Tool Approach

This paper presents a discussion of the evolution of a sequencer from a simple EPICS (Experimental Physics and Industrial Control System) based sequencer into a complex implementation designed utilizing UML (Unified Modeling Language) methodologies and a CASE (Computer Aided Software Engineering) tool approach. The main purpose of the sequencer (called the IF Sequencer) is to provide overall control of the Keck Interferometer to enable science operations be carried out by a single operator (and/or observer). The interferometer links the two 10m telescopes of the W. M. Keck Observatory at Mauna Kea, Hawaii. The IF Sequencer is a high-level, multi-threaded, Hare1 finite state machine, software program designed to orchestrate several lower-level hardware and software hard real time subsystems that must perform their work in a specific and sequential order. The sequencing need not be done in hard real-time. Each state machine thread commands either a high-speed real-time multiple mode embedded controller via CORB A, or slower controllers via EPICS Channel Access interfaces. The overall operation of the system is simplified by the automation. The UML is discussed and our use of it to implement the sequencer is presented. The decision to use the Rhapsody product as our CASE tool is explained and reflected upon. Most importantly, a section on lessons learned is presented and the difficulty of integrating CASE tool automatically generated C++ code into a large control system consisting of multiple infrastructures is presented.

interferometer↗
NASA NTRS2007

Lessons Learned from the Wide Field Camera 3 TV1 Test Campaign and Correlation Effort

In January 2004, shortly after the Columbia accident, future servicing missions to the Hubble Space Telescope (HST) were cancelled. In response to this, further work on the Wide Field Camera 3 instrument was ceased. Given the maturity level of the design, a characterization thermal test (TV1) was completed in case the mission was re-instated or an alternate mission found on which to fly the instrument. This thermal test yielded some valuable lessons learned with respect to testing configurations and modeling/correlation practices, including: 1. Ensure that the thermal design can be tested 2. Ensure that the model has sufficient detail for accurate predictions 3. Ensure that the power associated with all active control devices is predicted 4. Avoid unit changes for existing models. This paper documents the difficulties presented when these recommendations were not followed.

Peabody, Hume↗
NASA NTRS2007

Lessons Learned from Deploying an Analytical Task Management Database

Defining requirements, missions, technologies, and concepts for space exploration involves multiple levels of organizations, teams of people with complementary skills, and analytical models and simulations. Analytical activities range from filling a To-Be-Determined (TBD) in a requirement to creating animations and simulations of exploration missions. In a program as large as returning to the Moon, there are hundreds of simultaneous analysis activities. A way to manage and integrate efforts of this magnitude is to deploy a centralized database that provides the capability to define tasks, identify resources, describe products, schedule deliveries, and generate a variety of reports. This paper describes a web-accessible task management system and explains the lessons learned during the development and deployment of the database. Through the database, managers and team leaders can define tasks, establish review schedules, assign teams, link tasks to specific requirements, identify products, and link the task data records to external repositories that contain the products. Data filters and spreadsheet export utilities provide a powerful capability to create custom reports. Import utilities provide a means to populate the database from previously filled form files. Within a four month period, a small team analyzed requirements, developed a prototype, conducted multiple system demonstrations, and deployed a working system supporting hundreds of users across the aeros pace community. Open-source technologies and agile software development techniques, applied by a skilled team enabled this impressive achievement. Topics in the paper cover the web application technologies, agile software development, an overview of the system's functions and features, dealing with increasing scope, and deploying new versions of the system.

O'Neil, Daniel A.↗
NASA NTRS2008

NASA's In Space Propulsion Technology Program Accomplishments and Lessons Learned

NASA's In-Space Propulsion Technology (ISPT) Program was managed for 5 years at the NASA MSFC and significant strides were made in the advancement of key transportation technologies that will enable or enhance future robotic science and deep space exploration missions. At the program's inception, a set of technology investment priorities were established using an NASA-wide, mission-driven prioritization process and, for the most part, these priorities changed little - thus allowing a consistent framework in which to fund and manage technology development. Technologies in the portfolio included aerocapture, advanced chemical propulsion, solar electric propulsion, solar sail propulsion, electrodynamic and momentum transfer tethers, and various very advanced propulsion technologies with significantly lower technology readiness. The program invested in technologies that have the potential to revolutionize the robotic exploration of deep space. For robotic exploration and science missions, increased efficiencies of future propulsion systems are critical to reduce overall life-cycle costs and, in some cases, enable missions previously considered impossible. Continued reliance on conventional chemical propulsion alone will not enable the robust exploration of deep space - the maximum theoretical efficiencies have almost been reached and they are insufficient to meet needs for many ambitious science missions currently being considered. By developing the capability to support mid-term robotic mission needs, the program was to lay the technological foundation for travel to nearby interstellar space. The ambitious goals of the program at its inception included supporting the development of technologies that could support all of NASA's missions, both human and robotic. As time went on and budgets were never as high as planned, the scope of the program was reduced almost every year, forcing the elimination of not only the broader goals of the initial program, but also of funding for over half of the technologies in the original portfolio. In addition, the frequency at which the application requirements for the program changed exceeded the development time required to mature technologies: forcing sometimes radical rescoping of research efforts already halfway (or more) to completion. At the end of its fifth year, both the scope and funding of the program were at a minimum despite the program successfully meeting all of it's initial high priority objectives. This paper will describe the program, its requirements, technology portfolio, and technology maturation processes. Also discussed will be the major technology milestones achieved and the lessons learned from managing a $100M+ technology program.

Johnson, Les C.↗
NASA NTRS2006

Fluid Quick Disconnects - ISS Lessons Learned

The International Space Station has many fluid systems on the United States On-orbit Segment supporting thermal control, life support, extravehicular activities and payloads. To facilitate assembly and maintenance, fluid quick disconnect (QD) fittings are used throughout these systems for both internal pressurized modules and for external systems exposed to space. In the years since full scale development began on these QDs, a number of design and performance issues have surfaced and required substantial program funds and activity to rectify. This paper is intended to describe the most significant of these issues, their resolutions, and the lessons learned from the ISS experience.

Bond, Timothy A.↗
NASA NTRS2005

Aeromedical Lessons from the Space Shuttle Columbia Accident Investigation

This paper presents the aeromedical lessons learned from the Space Shuttle Columbia Accident Investigation. The contents include: 1) Introduction and Mission Response Team (MRT); 2) Primary Disaster Field Office (DFO); 3) Mishap Investigation Team (MIT); 4) Kennedy Space Center (KSC) Mishap Response Plan; 5) Armed Forces Institute of Pathology (AFIP); and 6) STS-107 Crew Surgeon.

Pool, Sam L.↗
NASA NTRS2008

Lessons Learned from Previous Space-Borne Sounders as a Guide to Future Sounder Development

Space-borne radio sounding is considered to be the gold standard for electron-density (N(sub e)) measurements compared to other techniques even under low-density conditions, such as N(sub e) < 1/cu cm, when other techniques are known to experience difficulties. These reliable measurements are not restricted to in-situ N(sub e) determinations since a spaceborne sounder can provide vertical N(sub e) profiles (N(sub e)(h)) from the spacecraft altitude to the altitude of maximum N(sub e). Near-conjunction studies involving the International Satellites for Ionospheric Studies (ISIS) satellites in the topside ionosphere and Dynamics Explorer 2 (DE 2) near the altitude of the F-region peak density have verified that, even at the greatest distance from the sounder, the ISIS-derived N(sub e)(h) profiles agree with the DE-2 Langmuir-probe measurements to within about 30% over a density range of more than two decades. Space-borne sounders can also provide N(sub e) profiles along the magnetic-field B, by inverting echoes that are ducted along field-aligned irregularities (FAI), and can provide information about the terrain beneath the satellite by examining surface reflections in the frequency range above the ionospheric penetration frequency. Many nations have launched rocket and satellite radio sounders in geospace over more than 4 decades and there have been sounders on space-probes and in orbit around other planets. Here we will summarize some of the lessons learned from these accomplishments by analyzing data from radio sounders on the Alouette and ISIS satellites and the OEDIPUS and other rockets in the terrestrial ionosphere, the IMAGE satellite in the terrestrial magnetosphere, the Ulysses space probe in Jupiter's 10 plasma torus and the MARSIS satellite in orbit around Mars. The emphasis will be on information deduced concerning (1) fundamental plasma processes and gradients in N, and B in the vicinity of the sounders from sounder-stimulated plasma resonances and short-range echoes involving ion as well as electron motions, (2) the importance of the antenna orientation relative to B for the detection of different plasma resonances, (3) sounder-stimulated plasma phenomena, including FAI, when special plasma conditions are satisfied, (4) the minimum power required for long-range echoes, as indicated by echoes from frequency components of the transmitted pulse and by multiple ducted echoes, and (5) the terrain beneath the satellite from surface reflections. Knowledge of these results should enable the optimum design of a future sounder to satisfy specific science requirements with minimal spacecraft resources.

Benson, Robert F.↗
NASA NTRS2008

Building a GPS Receiver for Space Lessons Learned

Over the past 4 years the Component Systems and Hardware branch at NASA GSFC has pursued an inhouse effort to build a unique space-flight GPS receiver. This effort has resulted in the Navigator GPS receiver. Navigator's first flight opportunity will come with the STS-125 HST-SM4 mission in August 2008. This paper covers the overall hardware design for the receiver and the difficulties encountered during the transition from the breadboard design to the final flight hardware design. Among the different lessons learned, the paper stresses the importance of selecting and verifying parts that are appropriate for space applications, as well as what happens when these parts are not accurately characterized by their datasheets. Additionally, the paper discusses what analysis needs to be performed when deciding system frequencies and filters. The presentation also covers how to prepare for thermal vacuum testing, and problems that may arise during vibration testing. It also contains what criteria should be considered when determining which portions of a design to create in-house, and which portions to license from a third party. Finally, the paper shows techniques which have proven to be extraordinarily helpful in debugging and analysis.

Sirotzky, Steve↗
NASA NTRS2007

Qualification and Lessons Learned with Space Flight Fiber Optic Components

This presentation covers lessons learned during the design, development, manufacturing and qualification of space flight fiber optic components. Changes at NASA, including short-term projects and decreased budgets have brought about changes to vendors and parts. Most photonics for NASA needs are now commercial off the shelf (COTS) products. The COTS Tecnology Assurance approach for space flight and qualification plans are outlined.

Ott, Melanie↗
NASA NTRS2008

Acting on Lessons Learned: A NASA Glenn Acoustics Branch Perspective

Lessons learned from the International Space Station have indicated that early attention to acoustics will be key to achieving safer, more productive environments for new long duration missions. Fans are known to be dominant noise sources, and reducing fan noise poses challenges for fan manufacturers and systems engineers. The NASA Glenn Acoustics Branch has considered ways in which expertise and capabilities traditionally used to understand and mitigate aircraft engine noise can be used to address small fan noise issues in Exploration and Information Technology applications. Many could benefit if NASA can capture what is known about small fan aero and acoustic performance in a "Guide for the Design, Selection, and Installation of Fans for Spaceflight Applications." A draft outline for this document will be offered as a useful starting point for brainstorming ideas for the various smaller, near-term research projects that would need to be addressed first.

Koch, L. Danielle↗
NASA NTRS2009

Suit Port Aft Bulkhead Mockup Test Results and Lessons Learned

The Small Pressurized Rover (SPR) is currently being carried as an integral part of the current Lunar Surface Architectures under consideration in the Constellation program. One element of the SPR is the suit port, the means by which the crew performs Extravehicular Activities (EVAs). Two suit port deliverables were produced in fiscal year 2008: an aft bulkhead mockup for functional integrated testing with the 1-G SPR mockup and a functional and pressurizable engineering unit. This paper focuses on the test results and lessons learned on the aft bulkhead mockup. The suit port aft bulkhead mockup was integrated with the mockup of the SPR cabin and chassis. It is located on the aft bulkhead of the SPR cabin structure and includes hatches, a locking mechanism, seals, interior and exterior suit don/doff aids, and exterior platforms to accommodate different crewmember heights. A lightweight mockup of the Mark III suit was tested with the suit port aft bulkhead mockup. There are several limitations to the suit port and mockup suits, and results of the suit port evaluation are presented and interpreted within the context of the limitations.

Romig, Barbara A.↗
NASA NTRS2005

Lessons Learned from Autonomous Sciencecraft Experiment

An Autonomous Science Agent has been flying onboard the Earth Observing One Spacecraft since 2003. This software enables the spacecraft to autonomously detect and responds to science events occurring on the Earth such as volcanoes, flooding, and snow melt. The package includes AI-based software systems that perform science data analysis, deliberative planning, and run-time robust execution. This software is in routine use to fly the EO-l mission. In this paper we briefly review the agent architecture and discuss lessons learned from this multi-year flight effort pertinent to deployment of software agents to critical applications.

Autonomous Sciencecraft Experiment (ASE)↗
NASA NTRS2009

Apollo CSM Power Generation System Design Considerations, Failure Modes and Lessons Learned

The objectives of this slide presentation are to: review the basic design criteria for fuel cells (FC's), review design considerations during developmental phase that affected Block I and Block II vehicles, summarize the conditions that led to the failure of components in the FC's, and state the solution implemented for each failure. It reviews the location of the fuel cells, the fuel cell theory the design criteria going into development phase and coming from the development phase, failures and solutions of Block I and II, and the lessons learned.

Interbartolo, Michael↗