SEARCH · Engineering Papers

Results for “ENGINE STARTING”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 433 records · Page 24

All sources NASA NTRS DOE OSTI

NASA NTRS2015

Software Development: 3D Animations and Creating User Interfaces for Realistic Simulations

My fall 2015 semester was spent at the Lyndon B. Johnson Space Center working in the Integrated Graphics, Operations, and Analysis Laboratory (IGOAL). My first project was to create a video animation that could tell the story of OMICS. OMICS is a term being used in the field of biomedical science to describe the collective technologies that study biological systems, such as what makes up a cell and how it functions with other systems. In the IGOAL I used a large 23 inch Wacom monitor to draw storyboards, graphics, and line art animations. I used Blender as the 3D environment to sculpt, shape, cut or modify the several scenes and models for the video. A challenge creating this video was to take a term used in biomedical science and describe it in such a way that an 8th grade student can understand. I used a line art style because it would visually set the tone for what we thought was an educational style. In order to get a handle on the perspective and overall feel for the animation without overloading my workspace, I split up the 2 minute animation into several scenes. I used Blender's python scripting capabilities which allowed for the addition of plugins to add or modify tools. The scripts can also directly interact with the objects to create naturalistic patterns or movements. After collecting the rendered scenes, I used Blender's built-in video editing workspace to output the animation. My second project was to write software that emulates a physical system's interface. The interface was to simulate a boat, ROV, and winch system. Simulations are a time and cost effective way to test complicated data and provide training for operators without having to use expensive hardware. We created the virtual controls with 3-D Blender models and 2-D graphics, and then add functionality in C# using the Unity game engine. The Unity engine provides several essential behaviors of a simulator, such as the start and update functions. A framework for Unity, which was developed in the lab, provided a way to place the different widgets on the virtual console dock and have them resize correctly based on the window dimensions.. My task in this project was to create the controls and visualizations for the data coming in from the simulator for the boat portion of the project. I wrote a class for each control window to handle the functionality of that widget. I implemented 11 widgets that make up the ship portion of the simulator. The members of the lab were each masters of their craft and I'm glad I had the opportunity to learn from them. I learned to plan strategically so I could finish this project on time. I allotted time for storyboarding, development, and refinement. In regards to animating I learned to use modifiers like lattice, boolean and build deformers. I also learned how to animate with drivers, how to use the dope sheet, and how to use the graph editor. In coding I learned to limit the chances for bugs by privatizing functions that should be exclusive to their class. I learned how to use the GIT repository to commit, stash and pull the latest build. I learned a bit of everything because I had the chance to see the entire application development process from the artwork, to the implementation.

Gordillo, Orlando Enrique↗

NASA NTRS2017

Mission Use of the SpaceCube Hybrid Data Processing System

The award-winning SpaceCube v2.0 system is a high performance, reconfigurable, hybrid data processing system that can be used in a multitude of applications including those that require a radiation hardened and reliable solution. This presentation provides an overview of the design architecture, flexibility, and the advantages of the modular SpaceCube v2.0 high performance data processing system for space applications. The current state of the proven SpaceCube technology is based on 11 years of engineering and operations. Eight systems have been successfully operated in space starting in 2008 with eight more to be delivered for payload integration in 2018 in support of various missions. This presentation will highlight how this multipurpose system is currently being used to solve design challenges of a variety of independent applications. The SpaceCube hardware adapts to new system requirements by allowing for application-unique interface cards that are utilized by reconfiguring the underlying programmable elements on the core processor card. We will show how this system is being used to improve on a heritage NASA GPS technology, enable a cutting-edge LiDAR instrument, and serve as a typical command and data handling (CDH) computer for a space robotics technology demonstration.Finally, this presentation will highlight the use of the SpaceCube v2.0 system on the Restore-L robotic satellite servicing mission. SpaceCube v2.0 is the central avionics responsible for the real-time vision system and autonomous robotic control necessary to find, capture, and service a national asset weather satellite.

Petrick, Dave↗

NASA NTRSDate not supplied

The Habitable Worlds Observatory Engineering View: Status, Plans and Opportunities

The NASA has begun the Great Observatory Maturation Program (GOMAP) with the goal of studying and advancing the Habitable Worlds Observatory (HWO), a large ultraviolet, optical, infrared space telescope recommended by the Astro 2020 Decadal Survey. Among its many goals, HWO will obtain spectra of at least 25 exo-Earth candidates to search for signs of life and conduct transformative astrophysics at ultraviolet, optical, and near-infrared wavelengths. The observatory, like HST and JWST, will be a powerful general class observatory. This past Fall the GOMAP program stood up two study groups, the Science Technology Architecture Review Team (START) and the Technical Assessment Group (TAG) aimed at helping to study the science, technology and architecture options for this new flagship mission. This talk will discuss the engineering activities associated with these studies including the team and organization, the study plan and the use of the Concept Maturity Level (CML) approach. In addition, the talk will discuss the key initial engineering efforts, the key technology gaps, and overall engineering plans.

HWO↗

NASA NTRS2001

Time-Dependent Simulations of Turbopump Flows

The objective of the current effort is to provide a computational framework for design and analysis of the entire fuel supply system of a liquid rocket engine, including high-fidelity unsteady turbopump flow analysis. This capability is needed to support the design of pump sub-systems for advanced space transportation vehicles that are likely to involve liquid propulsion systems. To date, computational tools for design/analysis of turbopump flows are based on relatively lower fidelity methods. An unsteady, three-dimensional viscous flow analysis tool involving stationary and rotational components for the entire turbopump assembly has not been available for real-world engineering applications. The present effort will provide developers with information such as transient flow phenomena at start up, impact of non-uniform inflows, system vibration and impact on the structure. In the proposed paper, the progress toward the capability of complete simulation of the turbo-pump for a liquid rocket engine is reported. The Space Shuttle Main Engine (SSME) turbo-pump is used as a test case for evaluation of the hybrid MPI/Open-MP and MLP versions of the INS3D code. The relative motion of the grid systems for the rotor-stator interaction was obtained using overset grid techniques. Time-accuracy of the scheme has been evaluated with simple test cases. Unsteady computations for the SSME turbo-pump, which contains 114 zones with 34.5 million grid points, are carried out on Origin 2000 systems at NASA Ames Research Center. Results from these time-accurate simulations with moving boundary capability will be presented along with the performance of parallel versions of the code.

Kris, Cetin C.↗

NASA NTRS2012

Getting a Cohesive Answer from a Common Start: Scalable Multidisciplinary Analysis through Transformation of a Systems Model

One of the challenges of systems engineering is in working multidisciplinary problems in a cohesive manner. When planning analysis of these problems, system engineers must trade between time and cost for analysis quality and quantity. The quality often correlates with greater run time in multidisciplinary models and the quantity is associated with the number of alternatives that can be analyzed. The trade-off is due to the resource intensive process of creating a cohesive multidisciplinary systems model and analysis. Furthermore, reuse or extension of the models used in one stage of a product life cycle for another is a major challenge. Recent developments have enabled a much less resource-intensive and more rigorous approach than hand-written translation scripts between multi-disciplinary models and their analyses. The key is to work from a core systems model defined in a MOF-based language such as SysML and in leveraging the emerging tool ecosystem, such as Query/View/Transformation (QVT), from the OMG community. SysML was designed to model multidisciplinary systems. The QVT standard was designed to transform SysML models into other models, including those leveraged by engineering analyses. The Europa Habitability Mission (EHM) team has begun to exploit these capabilities. In one case, a Matlab/Simulink model is generated on the fly from a system description for power analysis written in SysML. In a more general case, symbolic analysis (supported by Wolfram Mathematica) is coordinated by data objects transformed from the systems model, enabling extremely flexible and powerful design exploration and analytical investigations of expected system performance.

Operational QVT↗

NASA NTRS2012

Getting a Cohesive Answer from a Common Start: Scalable Multidisciplinary Analysis through Transformation of a System Model

One of the challenges of systems engineering is in working multidisciplinary problems in a cohesive manner. When planning analysis of these problems, system engineers must tradeoff time and cost for analysis quality and quantity. The quality is associated with the fidelity of the multidisciplinary models and the quantity is associated with the design space that can be analyzed. The tradeoff is due to the resource intensive process of creating a cohesive multidisciplinary system model and analysis. Furthermore, reuse or extension of the models used in one stage of a product life cycle for another is a major challenge. Recent developments have enabled a much less resource-intensive and more rigorous approach than handwritten translation scripts or codes of multidisciplinary models and their analyses. The key is to work from a core system model defined in a MOF-based language such as SysML and in leveraging the emerging tool ecosystem, such as Query-View- Transform (QVT), from the OMG community. SysML was designed to model multidisciplinary systems and analyses. The QVT standard was designed to transform SysML models. The Europa Hability Mission (EHM) team has begun to exploit these capabilities. In one case, a Matlab/Simulink model is generated on the fly from a system description for power analysis written in SysML. In a more general case, a symbolic mathematical framework (supported by Wolfram Mathematica) is coordinated by data objects transformed from the system model, enabling extremely flexible and powerful tradespace exploration and analytical investigations of expected system performance.

Cole, Bjorn↗

NASA NTRS2014

Raising Nuclear Thermal Propulsion (NTP) Technology Readiness Above 3

NTP development is currently supported by the NASA program office "Advanced Exploration Systems". The concept is a main propulsion option being considered for human missions to Mars in the 2030's. Major NTP development took place in the 1960's and 1970's under the Rover/NERVA program. The technology had matured to TRL 6 and was preparing to go to TRL 7 with a prototype flight engine before the program was cancelled. Over the last 40 years, a variety of continuations started, but only lasted a few years each. The Rover/NERVA infrastructure is almost all gone. The only remains are a few pieces of hardware, final reports and a few who worked the Rover/NERVA. Two types of nuclear fuel are being investigated to meet the current engine design specific impulse of 900 seconds compared to approximately 850 seconds demonstrated during Rover/NERVA. One is a continuation of composite fuel with new coatings to better control mid-band corrosion. The other type is a CERMET fuel made of Tungsten and UO2. Both fuels are being made from Rover/NERVA lessons learned, but with slightly different recipes to increase fuel endurance at higher operating temperatures. The technology readiness level (TRL) of these current modified reactor fuels is approximately TRL 3. To keep the development cost low and help mature the TRL level past 4 quickly, a few special non-nuclear test facilities have been made to test surrogate fuel, with depleted uranium, as coupons and full length elements. Both facilities utilize inductive heating and are licensed to handle depleted uranium. TRL 5 requires exposing the fuel to a nuclear environment and TRL 6 requires a prototype ground or flight engine system test. Currently, three different NTP ground test facility options are being investigated: exhaust scrubber, bore hole, and total exhaust containment. In parallel, a prototype flight demonstration test is also being studied. The first human mission to Mars in the 2030's is currently 2033. For an advanced propulsion concept to be seriously considered for use, the engine development plans need to show it is feasible and affordable to reach TRL 8 by 2027 and can be qualified for human mission use.

Gerrish, Harold P., Jr.↗

NASA NTRS1993

Liquid hydrogen and liquid oxygen feedline passive recirculation analysis

The primary goal of the National Launch System (NLS) program was to design an operationally efficient, highly reliable vehicle with minimal recurring launch costs. To achieve this goal, trade studies of key main propulsion subsystems were performed to specify vehicle design requirements. These requirements include the use of passive recirculation to thermally condition the liquid hydrogen (LH2) and liquid oxygen (LO2) propellant feed systems and Space Transportation Main Engine (STME) fuel pumps. Rockwell International (RI) proposed a joint independent research and development (JIRAD) program with Marshall Space Flight Center (MSFC) to study the LH2 feed system passive recirculation concept. The testing was started in July 1992 and completed in November 1992. Vertical and sloped feedline designs were used. An engine simulator was attached at the bottom of the feedline. This simulator had strip heaters that were set to equal the corresponding heat input from different engines. A computer program is currently being used to analyze the passive recirculation concept in the LH2 vertical feedline tests. Four tests, where the heater setting is the independent variable, were chosen. While the JIRAD with RI was underway, General Dynamics Space Systems (GDSS) proposed a JIRAD with MSFC to explore passive recirculation in the LO2 feed system. Liquid nitrogen (LN2) is being used instead of LO2 for safety and economic concerns. To date, three sets of calibration tests have been completed on the sloped LN2 test article. The environmental heat was calculated from the calibration tests in which the strip heaters were turned off. During the LH2 testing, the environmental heat was assumed to be constant. Therefore, the total heat was equal to the environmental heat flux plus the heater input. However, the first two sets of LN2 calibration tests have shown that the environmental heat flux varies with heater input. A Systems Improved Numerical Differencing Analyzer and Fluid Integrator (SINDA/FLUINT) model is currently being built to determine if this variation in environmental heat is due to a change in the wall temperature. During the third set of calibration tests, a faulty reference junction was found. Based on this anomaly with the reference junction, the heat flux calculations from the first two calibration sets are now considered questionable.

Holt, Kimberly Ann↗

NASA NTRS2003

Development and Engineering Design in Support of "Rover Ranch": A K-12 Outreach Software Project

A continuation of the initial development started in the summer of 1999, the body of work performed in support of 'ROVer Ranch' Project during the present fellowship dealt with the concrete concept implementation and resolution of the related issues. The original work performed last summer focused on the initial examination and articulation of the concept treatment strategy, audience and market analysis for the learning technologies software. The presented work focused on finalizing the set of parts to be made available for building an AERCam Sprint type robot and on defining, testing and implementing process necessary to convert the design engineering files to VRML files. Through reverse engineering, an initial set of mission critical systems was designed for beta testing in schools. The files were created in ProEngineer, exported to VRML 1.0 and converted to VRML 97 (VRML 2.0) for final integration in the software. Attributes for each part were assigned using an in-house developed JAVA based program. The final set of attributes for each system, their mutual interaction and the identification of the relevant ones to be tracked, still remain to be decided.

Pascali, Raresh↗

NASA NTRS1982

Support and power plant documentation for the gas turbine powered bus demonstration program

The operational experience obtained for the GT404-4 gas turbine engines in the intercity and intracity Bus Demonstration Programs is described for the period January 1980 through September 1981. Support for the engines and automatic transmissions involved in this program provided engineering and field service, spare parts and tools, training, and factory overhauls. the Greyhound (intercity) coaches accumulated 183,054 mi (294,595 km) and 5154 hr of total operation. The Baltimore Transit (intracity) coaches accumulated 40,567 mi (65,285 km) and 1840 hr of total operation. In service, the turbine powered Greyhound and Transit coaches achieved approximately 25% and 40% lower fuel mileage, respectively, than did the production diesel powered coaches. The gas turbine engine will require the advanced ceramic development currently being sponsored by the DOE and NASA to achieve fuel economy equivalent not only to that of today's diesel engines but also to the projected fuel economy of the advanced diesel engines of the 1990s. Sufficient experience was not achieved with the coaches prior to the start of service to identify and eliminate many of the problems associated with the startup of new equipment. Because of these problems, the mean miles between incident were unacceptably low. The future gas turbine system should be developed sufficiently to establish satisfactory durability prior to evaluation in revenue service. Commercialization of the gas turbine bus engine remains a viable goal for the future.

Nigro, D. N.↗

NASA NTRS1973

A study of ingestion and dispersion of engine exhaust products in trailing vortex systems

Analysis has been made of the ingestion and dispersion of engine exhaust products into the trailing vortex system of supersonic aircraft flying in the stratosphere. The rate of mixing between the supersonic jet and the co-flowing supersonic stream was found to be an order of magnitude less than would be expected on the basis of subsonic eddy-viscosity results. The length of the potential core was 66 nozzle exit radii so that the exhaust gases remain at elevated temperatures and concentrations over much longer distances than previsously estimated. Ingestion started at the end of the potential core and all hot gas from the engine was ingested into the trailing vortex within two core lengths. Comparison between the buoyancy calculations for the supersonic case with nondimensionalized subsonic aircraft contrail data on wake spreading showed good agreement. Velocity and temperature profiles have been specified at various stages of the wake, and the analysis in this report can be used to predict variations of concentrations of species such as nitrogen oxides under conditions of chemical reaction.

Nielsen, J. N.↗

NASA NTRS1979

Hydrogen-fueled diesel engine without timed ignition

Experiments were carried out to investigate the feasibility of converting a diesel engine to hydrogen-fueled operation without providing a timed ignition system. Use was made of a glow plug and a multiple-strike spark plug. The glow plug was found to provide reliable ignition and smooth engine operation. It caused the hydrogen to ignite almost immediately upon the start of injection. Indicated mean effective pressures were on the order of 1.3 MPa for equivalence ratios between 0.1 and 0.4 at a compression ratio of 18. This is significantly higher than the corresponding result obtained with diesel oil (about 0.6 MPa for equivalence ratios between 0.3 and 0.9). Indicated thermal efficiencies were on the order of 0.4 for hydrogen and 0.20-0.25 for diesel oil. Operation with the multiple-strike spark system yielded similar values for IMEP and efficiency, but gave rise to large cycle-to-cycle variations in the delay between the beginning of injection and ignition. Large ignition delays were associated with large amplitude pressure waves in the combustion chamber. The measured NO(x) concentrations in the exhaust gas were of the order of 50-100 ppm. This is significantly higher than the corresponding results obtained with premixed hydrogen and air at low equivalence ratios. Compression ignition could not be achieved even at a compression ratio of 29.

Homan, H. S.↗

NASA NTRS1980

Investigation of the fuel feed line failures on the Space Shuttle main engine

The Space Shuttle Main Engine (SSME) development program experienced two similar appearing fuel feed line failures during the shutdown portion of two engine tests. Failure investigations into each incident showed that a few cycles of high-amplitude transient strain occurring during the start and cutoff portions of each test could have either accumulated damage and led to a fatigue failure after 46 tests, or caused rupture in a low-strength weld joint. The cause of the high strain was traced to a period of unsteady flow separation during the start and cutoff of each test coincident with the oblique shock approaching the nozzle exit. Since elimination of the flow separation was impractical, the steps taken to allow engine development and flight preparations to continue were: (1) establish the safe operating life of the nozzle, (2) reinforce all low-strength welds, and (3) eliminate the use of thin-wall fuel feed lines. In parallel, the feed line was redesigned and fabrication was initiated on units to be incorporated into the development program.

Larson, E. W.↗

NASA NTRS1992

NASA Johnson Space Center: Total quality partnership

The development of and benefits realized from a joint NASA, support contractor continuous improvement process at the Johnson Space Center (JSC) is traced. The joint effort described is the Safety, Reliability, and Quality Assurance Directorate relationship with its three support contractors which began in early 1990. The Continuous Improvement effort started in early 1990 with an initiative to document and simplify numerous engineering change evaluation processes. This effort quickly grew in scope and intensity to include process improvement teams, improvement methodologies, awareness, and training. By early 1991, the support contractor had teams in place and functioning, program goals established and a cultural change effort underway. In mid-l991 it became apparent that a major redirection was needed to counter a growing sense of frustration and dissatisfaction from teams and managers. Sources of frustration were isolated to insufficient joint participation on teams, and to a poorly defined vision. Over the next year, the effort was transformed to a truly joint process. The presentation covers the steps taken to define vision, values, goals, and priorities and to form a joint Steering Committee and joint process improvement teams. The most recent assessment against the President's award criteria is presented as a summary of progress. Small, but important improvement results have already demonstrated the value of the joint effort.

Harlan, Charlie↗

NASA NTRS2006

Applying Registry Services to Spaceflight Technologies to Aid in the Assignment of Assigned Numbers to Disparate Systems and Their Technologies to Further Enable Interoperability

To date very little effort has been made to provide interoperability between various space agency projects. To effectively get to the Moon and beyond systems must interoperate. To provide interoperability, standardization and registries of various technologies will be required. These registries will be created as they relate to space flight. With the new NASA Moon/Mars initiative a requirement to standardize and control the naming conventions of very disparate systems and technologies are emerging. The need to provide numbering to the many processes, schemas, vehicles, robots, space suits and technologies (e.g. versions), to name a few, in the highly complex Constellation Initiative is imperative. The number of corporations, developer personnel, system interfaces, people interfaces will require standardization and registries on a scale not currently envisioned. It would only take one exception (stove piped system development) to weaken, if not, destroy interoperability. To start, a standardized registry process must be defined that allows many differing engineers, organizations and operators the ability to easily access disparate registry information across numerous technological and scientific disciplines. Once registries are standardized the need to provide registry support in terms of setup and operations, resolution of conflicts between registries and other issues will need to be addressed. Registries should not be confused with repositories. No end user data is "stored" in a registry nor is it a configuration control system. Once a registry standard is created and approved, the technologies that should be registered must be identified and prioritized. In this paper, we will identify and define a registry process that is compatible with the Constellation Initiative and other non related space activities and organizations. We will then identify and define the various technologies that should use a registry to provide interoperability. The first set of technologies will be those that are currently in need of expansion namely the assignment of satellite designations and the process which controls assignments. Second, we will analyze the technologies currently standardized under the Consultative Committee for Space Data Systems (CCSDS) banner. Third, we will analyze the current CCSDS working group and birds of a feather activities to ascertain registry requirements. Lastly, we will identify technologies that are either currently under the auspices of another

Bradford, Robert N.↗

NASA NTRS2006

Applying Registry Services to Spaceflight Technologies to Aid in the Assignment of Assigned Numbers to Disparate Systems and their Technologies to Further Enable Interoperability

To date very little effort has been made to provide interoperability between various space agency projects. To effectively get to the Moon and beyond systems must interoperate. To provide interoperability, standardization and registries of various technologies will be required. These registries will be created as they relate to space flight. With the new NASA Moon/Mars initiative, a requirement to standardize and control the naming conventions of very disparate systems and technologies is emerging. The need to provide numbering to the many processes, schemas, vehicles, robots, space suits and technologies (e.g. versions), to name a few, in the highly complex Constellation initiative is imperative. The number of corporations, developer personnel, system interfaces, people interfaces will require standardization and registries on a scale not currently envisioned. It would only take one exception (stove piped system development) to weaken, if not, destroy interoperability. To start, a standardized registry process must be defined that allows many differing engineers, organizations and operators the ability to easily access disparate registry information across numerous technological and scientific disciplines. Once registries are standardized the need to provide registry support in terms of setup and operations, resolution of conflicts between registries and other issues will need to be addressed. Registries should not be confused with repositories. No end user data is "stored" in a registry nor is it a configuration control system. Once a registry standard is created and approved, the technologies that should be registered must be identified and prioritized. In this paper, we will identify and define a registry process that is compatible with the Constellation initiative and other non related space activities and organizations. We will then identify and define the various technologies that should use a registry to provide interoperability. The first set of technologies will be those that are currently in need of expansion namely the assignment of satellite designations and the process which controls assignments. Second, we will analyze the technologies currently standardized under the Consultative Committee for Space Data Systems (CCSDS) banner. Third, we will analyze the current CCSDS working group and Birds of a Feather (BoF) activities to ascertain registry requirements. Lastly, we will identify technologies that are either currently under the auspices of another standards body or technologies that are currently not standardized. For activities one through three, we will provide the analysis by either discipline or technology with rationale, identification and brief description of requirements and precedence. For activity four, we will provide a list of current standards bodies e.g. IETF and a list of potential candidates.

Bradford, Robert N.↗

NASA NTRS2008

Solar Power System Design for the Solar Probe+ Mission

Solar Probe+ is an ambitious mission proposed to the solar corona, designed to make a perihelion approach of 9 solar radii from the surface of the sun. The high temperature, high solar flux environment makes this mission a significant challenge for power system design. This paper summarizes the power system conceptual design for the solar probe mission. Power supplies considered included nuclear, solar thermoelectric generation, solar dynamic generation using Stirling engines, and solar photovoltaic generation. The solar probe mission ranges from a starting distance from the sun of 1 AU, to a minimum distance of about 9.5 solar radii, or 0.044 AU, from the center of the sun. During the mission, the solar intensity ranges from one to about 510 times AM0. This requires power systems that can operate over nearly three orders of magnitude of incident intensity.

Landis, Geoffrey A.↗

NASA NTRS2011

Shuttle Program Loads Integration: Going From Concept to Operations and Staying Successful

From the beginning of the Shuttle Program to its end, integrated loads and dynamics analyses and tests have been critical in shaping the vehicle design and operational decisions for NASA and its customers. Starting with scaled models and simple mathematical simulations of the structural dynamics, engineers defined the required structural stiffness and predicted the limit loads for each element of the system. Early structural tests provided reasonable confidence that the models and predictions were good. The first launch of the Space Shuttle brought surprises, though, when the ignition overpressure event caused a forward fuel tank support strut to buckle, among several unexpected effects. The launch pad and other ground equipment became an integral part of the system integration, especially where the acoustic and pressure environments of ignition and lift-off were concerned. Following the Challenger accident, operating limits were changed in response to new understandings of how the integrated system performed. Controlling loads while maximizing performance was a key tenet of the Performance Enhancement design process, which enabled construction of the International Space Station. During the return to flight after the Columbia accident, engineers grew to understand that loads during the roll maneuver were also important to the vehicle s structural margin and life. At this point the crawler transport from the Vehicle Assembly Building to the launch pad also became a part of the integrated loads analysis. Even in the last years of the Space Shuttle Program, new data still provided interesting insights into this complicated and fascinating spaceship. This paper will present some examples of the important findings by the team of specialists that supported the Integrated Loads and Dynamics Panel for the Space Shuttle Program.

Bernstein, Karen↗