Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Lessons learned”

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 1,387 records · Page 77

NASA's Professional DEVELOPment - Evaluating 10 Weeks of Capacity Building

Under NASA’s Applied Sciences, the NASA DEVELOP Program is centered on dual capacity building. Projects bring together partners and participants to learn how Earth observation data can enhance environmental decision-making practices and inform action. During their time with DEVELOP, participants build technical skills around remotely sensed data and professional skills through interactions with team members, science advisors, and partners. To further refine the participant experience, DEVELOP explores which technical and professional skills individuals report improving during the 10-week program. An analysis of self-reported assessments from 2018 to 2021 included projects that were conducted in-person and virtually. Participants consistently indicated a strong improvement in technical and professional skills yet there was clear variation between in-person and virtual opportunities. When comparing between 2019 and 2021, self-reporting showed a higher percentage of participants reporting an increase in networking in the virtual environment and an increase in building professional relationships with project partners virtually. This analysis suggests that professional opportunities available in the virtual environment may in fact bolster early career scientists’ networking abilities. This presentation will identify DEVELOP’s approach to monitoring and evaluation, highlight interesting trends introduced by the pandemic, and lessons learned.

Sarah Payne↗

Project KEWL: Kinect Engineering With Learning

Project KEWL is a joint project between NASA/JPL and NASA/JSC to stimulate interest of children in Science, Technology, Engineering and Math (STEM) and bring the NASA space exploration experience to the classroom, museum and ultimately the living room. Using the Kinect game controller KEWL allows children to engage in NASA s missions in a fundamentally new way. KEWL allows children to experiment with gravity on Mars and the Moon; navigate through the International Space Station; fix a torn solar array on the ISS; drive a robot on Mars; visit an Asteroid; learn about the differences in gravity on different planets and control Robonaut 2 using their body as the input device. Project KEWL complements NASA s outreach investments in television, mobile platforms and the web by engaging the public through the rapidly expanding medium of console gaming. In 2008, 97% of teenagers played video games and 86% played on a home gaming console. (source: http://pewresearch.org/pubs/953/) As of March 2011, there have been more than 10 million Kinects sold. (source: http://www.itproportal.com/2011/03/10/kinect-record-breaking-sales-figures-top-10-million/) Project KEWL interacts with children on a platform on which they spend much of their time and teaches them information about NASA while they are having fun. Project KEWL progressed from completely custom C++ code written in house to using a commercial game engine. The art work and 3D geometry models come from existing engineering work or are created by the KEWL development team. Six different KEWL applications have been demonstrated at nine different venues including schools, museums, conferences, and NASA outreach events. These demonstrations have allowed the developers the chance to interact with players and observe the gameplay mechanics in action. The lessons learned were then incorporated into the subsequent versions of the applications.

Norris, Jeff↗

Hubble Space Telescope Fine Guidance Sensor Post-Flight Bearing Inspection

Aerospace mechanism engineering success stories often, if not always, consist of overcoming developmental, test and flight anomalies. Many times it is these anomalies that stimulate technology growth and more reliable future systems. However, one must learn from these to achieve an ultimately successful mission. It is not often that a spacecraft engineer is able to inspect hardware that has flown in orbit for several years. However, in February 1997, the Fine Guidance Sensor-1 (FGS-1) was removed from the Hubble Space Telescope (HST) and returned to NASA Goddard Space Flight Center (GSFC) during the second Servicing Mission (SM2). At the time of removal, FGS-1 had nearly 7 years of service and the bearings in the Star Selector Servos (SSS) had accumulated approximately 25 million Coarse Track (CT) cycles. The main reason for its replacement was due to a bearing torque anomaly leading to stalling of the B Star Selector Servo (SSS-B) when reversing direction during a vehicle offset maneuver, referred to herein as a Reversal Bump (RB). The returned HST FGS SSS bearings were disassembled for post-service condition assessment to better understand the actual cause of the torque spikes, identify potential process/design improvements, and provide information for remedial on-orbit operation modifications. The methods and technology utilized for this inspection are not unique to this system and can be adapted to most investigations at varying stages of the mechanism life from development, through testing, to post flight evaluation. The systematic methods used for the HST Fine Guidance Sensor (FGS) SSS and specific findings are the subjects presented in this paper. The lessons learned include the importance of cleanliness and handling for precision instrument bearings and the potential effects from contamination. The paper describes in detail, the analytical techniques used for the SSS and their importance in this investigation. Inspection analytical data and photographs are included throughout the paper.

Pellicciotti, J.↗

Hubble Space Telescope Fine Guidance Sensor Post-Flight Bearing Inspection

Aerospace mechanism engineering success stories often, if not always, consist of overcoming developmental, test and flight anomalies. Many times it is these anomalies that stimulate technology growth and more reliable future systems. However, one must learn from these to achieve an ultimately successful mission. It is not often that a spacecraft engineer is able to inspect hardware that has flown in orbit for several years. However, in February 1997, the Fine Guidance Sensor-I (FGS-1) was removed from the Hubble Space Telescope (HST) and returned to NASA Goddard Space Flight Center (GSFC) during the second Servicing Mission (SM2). At the time of removal, FGS-1 had nearly 7 years of service and the bearings in the Star Selector Servos (SSS) had accumulated approximately 25 million Coarse Track (CT) cycles. The main reason for its replacement was due to a bearing torque anomaly leading to stalling of the B Star Selector Servo (SSS-B) when reversing direction during a vehicle offset maneuver, referred to herein as a Reversal Bump (RB). The returned HST FGS SSS bearings were disassembled for post-service condition assessment to better understand the actual cause of the torque spikes, identify potential process/design improvements, and provide information for remedial on-orbit operation modifications. The methods and technology utilized for this inspection are not unique to this system and can be adapted to most investigation ai varying stages of the mechanism life from development, through testing, io post night evaluation. The systematic methods used for the HST Fine Guidance Sensor (FGS) SSS and specific findings are the subjects presented in this paper. The lessons learned include the importance of cleanliness and handling for precision instrument bearings and the potential effects from contamination. The paper describes in detail, the analytical techniques used for the SSS and their importance in this investigation. Inspection analytical data and photographs are included throughout the paper.

Pellicciotti, Joseph↗

NASA's Space Launch System Progress Report

Exploration beyond Earth will be an enduring legacy for future generations, confirming America's commitment to explore, learn, and progress. NASA's Space Launch System (SLS) Program, managed at the Marshall Space Flight Center, is responsible for designing and developing the first exploration-class rocket since the Apollo Program's Saturn V that sent Americans to the Moon. The SLS offers a flexible design that may be configured for the MultiPurpose Crew Vehicle and associated equipment, or may be outfitted with a payload fairing that will accommodate flagship science instruments and a variety of high-priority experiments. Both options support a national capability that will pay dividends for future generations. Building on legacy systems, facilities, and expertise, the SLS will have an initial lift capability of 70 metric tons (mT) and will be evolvable to 130 mT. While commercial launch vehicle providers service the International Space Station market, this capability will surpass all vehicles, past and present, providing the means to do entirely new missions, such as human exploration of asteroids and Mars. With its superior lift capability, the SLS can expand the interplanetary highway to many possible destinations, conducting revolutionary missions that will change the way we view ourselves, our planet and its place in the cosmos. To perform missions such as these, the SLS will be the largest launch vehicle ever built. It is being designed for safety and affordability - to sustain our journey into the space age. Current plans include launching the first flight, without crew, later this decade, with crewed flights beginning early next decade. Development work now in progress is based on heritage space systems and working knowledge, allowing for a relatively quick start and for maturing the SLS rocket as future technologies become available. Together, NASA and the U.S. aerospace industry are partnering to develop this one-of-a-kind asset. Many of NASA's space centers across the country will provide their unique expertise to the Space Launch System endeavor. Unique infrastructure to be used includes the Michoud Assembly Facility for tank manufacturing, Stennis Space Center for engine testing, and Kennedy Space Center for processing and launch. As this panel will discuss, the SLS team is dedicated to doing things differently-from applying lean oversight/insight models to smartly using legacy hardware and existing facilities. Building on the foundation laid by over 50 years of human and scientific space flight--and on the lessons learned from the Apollo, Space Shuttle, and Constellation Programs-the SLS team has delivered both technical trade studies and business case analyses to ensure that the SLS architecture will be safe, affordable, reliable, and sustainable.

Singer, Joan A.↗

Evaluating Failures and Near Misses in Human Spaceflight History for Lessons for Future Human Spaceflight

There have been a number of studies done in the past drawn on lessons learned with regard to human loss-of-life events. Generally, the systemic causes and proximate causes for fatal events have both been examined in considerable detail. However, an examination of near-fatal accidents and failures that narrowly missed being fatal could be equally useful, not only in detecting causes, both proximate and systemic, but also for determining what factors averted disaster, what design decisions and/or operator actions prevented catastrophe. Additionally, review of risk factors for upcoming or future programs will often look at trending statistics, generally focusing on failure/success statistics. Unfortunately, doing so can give a skewed or misleading view of past reliability or a reliability that cannot be presumed to apply to a new program. One reason for this might be that failure/success criteria aren't the same across programs, but also that apparent success can hide systemic faults that, under other circumstances, can be fatal to a program with different parameters. A program with a number of near misses can look more reliable than a consistently healthy program with a single out-of-family failure and provide very misleading data if it is not examined in detail. This is particularly true for a manned space program where failure/success includes more than making a particular orbit. Augmenting reliability evaluations with this near miss data can provide insight and expand on the limitations of a strictly pass/fail evaluation. Even more importantly, a thorough understanding of these near miss events can identify conditions that prevented fatalities. Those conditions may be key to a programs reliability, but, without insight to the repercussions if such conditions were not in place, their importance may not be readily clear. As programs mature and political and fiscal responsibilities come to the fore, often there is considerable incentive to eliminate unnecessary conservatism, design margin, redundancy, operational support, testing, training, or safety oversight. An evaluation that demonstrates how these features and capabilities averted disaster can ensure processes that saved lives or missions are not discarded without appropriate review and understanding. Close examination of accidents that almost were can also highlight differences in design from one program to another, either justifying reliability comparisons or negating them. It can also provide considerable insight into how those saving factors were developed and implemented so that similar methods can be used to ensure appropriate life-saving and mission saving factors can be developed, even for a dissimilar space program. The lessons are appropriate for seasoned manned space programs and agencies, but crucial for untried agencies and organizations that are interested in sending man into space. The large body of publicly available near miss and accident data available provide invaluable insight into programmatic, technical, and even political issues that can be addressed before they impact safety. In this paper, we examine a number of these near misses and accidents and steps a program, agency, or potential spacefaring company might take to improve their chances of success and avoid mission or safety disasters using this data.

Barr, Stephanie↗

2024 Nasa Lunabotics University Competition: Site Preparation With Bulk Regolith

Introduction: Lunabotics provides accredited institutions of higher learning students (vocational-technical, college, university) an opportunity to apply the NASA systems engineering process to design and build a prototype robot. This robot would be capable of performing the proposed operations on the Lunar surface in support of future Artemis mission goals. Lunabotics features a systems engineering design challenge to engage students in the next phase of hu-man space exploration supporting the Artemis missions. This two-semester event encourages students to design and build an autonomous or telerobotic robot designed to traverse the simulated Lunar surface and complete the assigned construction tasks. The number of teams accepted into this challenge is not predetermined but is based on the scores and overall quality of the Project Management Plans received and other factors. The culmination of the Lunabotics virtual challenge will be the design, build and operation of a functional prototype Lunar robot. Teams are required to submit the following: (1) Project Management Plan, (2) Systems Engineering Paper, a (3) STEM Engage-ment Report, and a (4) Proof of Life Video. This is an optional item, but to qualify for the grand prize a team must also submit a: (5) Presentation and Demonstration. Background: The NASA Lunabotics University Competition was first held in 2010 as a follow on to the NASA Regolith Excavation Challenge [1]. The high level of interest and participation from over 50 universities each year has led to a sustained annual competi-ion cadence: it has been held every May for the past 14 years [2,3]. Over 6,000 students have participated and been inspired to pursue Science, Technology, En-gineering and Mathematics careers (STEM). 2024 Competition: The necessary lunar surface tasks are evolving to meet the NASA Artemis Mission requirements. In the past Lunabotics challenges we gathered data to support Lunar mining for consuma-bles in the Lunar regolith. Now, in 2024, the task is to gather data on Lunar site preparation and construction by designing and building a robot that will traverse the chaotic Lunar terrain and construct a regolith-based berm. The goal is to build a berm structure which would be useful to the Artemis Mission for blast and ejecta protection during lunar landings and launches, shading cryogenic propellant tank farms, providing radiation protection around a nuclear power plant and other mission critical uses. Lunabotics will consist of three separate events this year. The first event is NASA’s Lunabotics Project Development Challenge, where teams submit various deliverables to be scored by judges. The second event will be the University of Central Florida (UCF) Lunabotics Qualification challenge, in the Exolith laboratory, where teams will put their de-signs to the test. The top ten scoring teams from the Qualification challenge are then invited to the third and final event, NASA’s Lunabotics On-Site Challenge at Kennedy Space Center in Florida. This presentation will summarize the results and lessons learned from the NASA Lunabotics University Competition held in May 2024.

Lunabotics↗

NASA's Earth Science Flight Program Meets the Challenges of Today and Tomorrow

NASA's Earth science flight program is a dynamic undertaking that consists of a large fleet of operating satellites, an array of satellite and instrument projects in various stages of development, a robust airborne science program, and a massive data archiving and distribution system. Each element of the flight program is complex and present unique challenges. NASA builds upon its successes and learns from its setbacks to manage this evolving portfolio to meet NASA's Earth science objectives. NASA fleet of 16 operating missions provide a wide range of scientific measurements made from dedicated Earth science satellites and from instruments mounted to the International Space Station. For operational missions, the program must address issues such as an aging satellites operating well beyond their prime mission, constellation flying, and collision avoidance with other spacecraft and orbital debris. Projects in development are divided into two broad categories: systematic missions and pathfinders. The Earth Systematic Missions (ESM) include a broad range of multi-disciplinary Earth-observing research satellite missions aimed at understanding the Earth system and its response to natural and human-induced forces and changes. Understanding these forces will help determine how to predict future changes, and how to mitigate or adapt to these changes. The Earth System Science Pathfinder (ESSP) program provides frequent, regular, competitively selected Earth science research opportunities that accommodate new and emerging scientific priorities and measurement capabilities. This results in a series of relatively low-cost, small-sized investigations and missions. Principal investigators whose scientific objectives support a variety of studies lead these missions, including studies of the atmosphere, oceans, land surface, polar ice regions, or solid Earth. This portfolio of missions and investigations provides opportunity for investment in innovative Earth science that enhances NASA's capability for better understanding the current state of the Earth system. ESM and ESSP projects often involve partnerships with other US agencies and/or international organizations. This adds to the complexity of mission development, but allows for a greater scientific return on NASA's investments. The Earth Science Airborne Science Program provides manned and unmanned aircraft systems that further science and advance the use of satellite data. NASA uses these assets worldwide in campaigns to investigate extreme weather events, observe Earth system processes, obtain data for Earth science modeling activities, and calibrate instruments flying aboard Earth science spacecraft. The Airborne Science Program has six dedicated aircraft and access to many other platforms. The Earth Science Multi-Mission Operations program acquires, preserves, and distributes observational data from operating spacecraft to support Earth Science research focus areas. The Earth Observing System Data and Information System (EOSDIS), which has been in operations since 1994, primarily accomplishes this. EOSDIS acquires, processes, archives, and distributes Earth Science data and information products. The archiving of NASA Earth Science information happens at eight Distributed Active Archive Centers (DAACs) and four disciplinary data centers located across the United States. The DAACs specialize by topic area, and make their data available to researchers around the world. The DAACs currently house over 9 petabytes of data, growing at a rate of 6.4 terabytes per day. NASA's current Earth Science portfolio is responsive to the National Research Council (NRC) 2007 Earth Science Decadal Survey and well as the 2010 NASA Response to President Obama's Climate Plan. As the program evolves into the future it will leverage the lessons learned from the current missions in operations and development, and plan for adjustments to future objectives in response to the anticipated 2017 NRC Decadal Survey.

Flight Program↗

Formulation of an effective safety design review for the Skylab Program.

The Skylab Program is presenting a unique set of requirements by extending the capabilities of both men and equipment to withstand extended periods of time in space. The progression of space programs which preceded Skylab have provided a set of building blocks of knowledge and experience coupled with an extensive ground test program which makes it possible to plan its flight program without earlier, unmanned test flights. This approach, however, makes it mandatory that to the maximum extent possible, we factor into the design review process all the 'lessons learned' which are applicable. It is this conscious review of the Skylab design, based on checklists prepared from design criteria, gleaned from a variety of sources and experiences, which is the subject of this paper. A brief description of the Skylab Program, its objectives, and the missions planned for it are presented briefly to better understand the degree of extrapolation of hardware development from previous programs.

Cohen, H.↗

Spiritual impacts of the space program on the world

The lessons learned from the space program in showing how fragile the environment is on earth are discussed. Examples are cited of the reactions of the astronauts to the unique features of earth. The reactions of the populace in seeking better living conditions and their concern with improving the environment are given as two outgrowths of the program.

Esch, M.↗

Mechanism problems

It is pointed out that too frequently during the design and development of mechanisms, problems occur that could have been avoided if the right question had been asked before, rather than after, the fact. Several typical problems, drawn from actual experience, are discussed and analyzed. The lessons learned are used to generate various suggestions for minimizing mistakes in mechanism design.

Riedel, J. K.↗

Manned Space Programs Accident/Incident Summaries (1970 - 1971)

A compilation of 223 mishaps assembled from company and NASA records covering the Accident/Incident experience in 1970-1971 in the Manned Space Flight Programs is presented. It is the companion volume to NASA-CR-120998 which covered the years 1963-1969. The objectives of this summary is to make available to Government agencies and industrial firms the lessons learned from these mishaps. Each accident/incident summary has been reviewed by description, cause and recommended preventive action. The summaries have been categorized by the following ten systems: (1) Cryogenic; (2) Electrical; (3) Facility/GSE; (4) Fuel and Propellant; (5) Life Support; (6) Ordnance; (7) Pressure; (8) Propulsion; (9) Structural; and (10) Transport/Handling.

Source record↗

Apollo 16 Site Selection

The selection is discussed of the Descartes landing site for the Apollo 16 flight for direct sampling of highland materials that would be compositionally different from previous samples. The lessons learned in this site selection that should be considered in future site selection are listed.

Hinners, N. W.↗

MSFC Skylab Multiple Docking Adapter, Volume 1

The history is presented of the development of the Skylab Multiple Docking Adapter from initial concept through its final design, related test programs, mission performance, and lessons learned.

Source record↗

Cluster man/system design requirements and verification

Discussion of the procedures employed for determining the man/system requirements that guided Skylab design, and review of the techniques used for implementing the man/system design verification. The foremost lesson learned from the design need anticipation and design verification experience is the necessity to allow for human capabilities of in-flight maintenance and repair. It is now known that the entire program was salvaged by a series of unplanned maintenance and repair events which were implemented in spite of poor design provisions for maintenance.

Orbital workers↗

Flightcrew observations of spacecraft systems

A brief overview of the various Skylab systems is presented. Particular emphasis is placed on unique points of system design that were either new to space flight or had an effect on crew operations significantly different from that experienced during the Mercury, Gemini, and Apollo missions. A summary of the opinions and experience of the three Skylab flightcrews in using these Skylab-unique systems is given. The designs that the crews considered completely successful as compared to the preflight expectations and those designs that turned out to be unsuitable and that should be approached differently in future missions are discussed. Differences in crew opinions about the same system are noted where appropriate, and spacecraft lessons learned by the flightcrews are summarized.

Crippen, R. L.↗

Experimenters' reference based upon Skylab experiment management

The methods and techniques for experiment development and integration that evolved during the Skylab Program are described to facilitate transferring this experience to experimenters in future manned space programs. Management responsibilities and the sequential process of experiment evolution from initial concept through definition, development, integration, operation and postflight analysis are outlined and amplified, as appropriate. Emphasis is placed on specific lessons learned on Skylab that are worthy of consideration by future programs.

Source record↗