Search NASA⌕ Search

SEARCH · Search NASA

Results for “Shuttle Constellation”

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 199 records · Page 11
All sourcesNASA NTRSDOE OSTI
NASA NTRS2011

Extravehicular Activity Technology Development Status and Forecast

The goal of NASA s current EVA technology effort is to further develop technologies that will be used to demonstrate a robust EVA system that has application for a variety of future missions including microgravity and surface EVA. Overall the objectives will be to reduce system mass, reduce consumables and maintenance, increase EVA hardware robustness and life, increase crew member efficiency and autonomy, and enable rapid vehicle egress and ingress. Over the past several years, NASA realized a tremendous increase in EVA system development as part of the Exploration Technology Development Program and the Constellation Program. The evident demand for efficient and reliable EVA technologies, particularly regenerable technologies was apparent under these former programs and will continue to be needed as future mission opportunities arise. The technological need for EVA in space has been realized over the last several decades by the Gemini, Apollo, Skylab, Space Shuttle, and the International Space Station (ISS) programs. EVAs were critical to the success of these programs. Now with the ISS extension to 2028 in conjunction with a current forecasted need of at least eight EVAs per year, the EVA hardware life and limited availability of the Extravehicular Mobility Units (EMUs) will eventually become a critical issue. The current EMU has successfully served EVA demands by performing critical operations to assemble the ISS and provide repairs of satellites such as the Hubble Space Telescope. However, as the life of ISS and the vision for future mission opportunities are realized, a new EVA systems capability will be needed and the current architectures and technologies under development offer significant improvements over the current flight systems. In addition to ISS, potential mission applications include EVAs for missions to Near Earth Objects (NEO), Phobos, or future surface missions. Surface missions could include either exploration of the Moon or Mars. Providing an EVA capability for these types of missions enables in-space construction of complex vehicles or satellites, hands on exploration of new parts of our solar system, and engages the public through the inspiration of knowing that humans are exploring places that they have never been before. This paper offers insight into what is currently being developed and what the potential opportunities are in the forecast.

Chullen, Cinda↗
NASA NTRS2008

Ares Launch Vehicles Development Awakens Historic Test Stands at NASA's Marshall Space Flight Center

This paper chronicles the rebirth of two national rocket testing assets located at NASA's Marshall Space Flight Center: the Dynamic Test Stand (also known as the Ground Vibration Test Stand) and the Static Test Stand (also known as the Main Propulsion Test Stand). It will touch on the historical significance of these special facilities, while introducing the requirements driving modifications for testing a new generation space transportation system, which is set to come on line after the Space Shuttle is retired in 2010. In many ways, America's journey to explore the Moon begins at the Marshall Center, which is developing the Ares I crew launch vehicle and the Ares V cargo launch vehicle, along with managing the Lunar Precursor Robotic Program and leading the Lunar Lander descent stage work, among other Constellation Program assignments. An important component of this work is housed in Marshall's Engineering Directorate, which manages more than 40 facilities capable of a full spectrum of rocket and space transportation technology testing - from small components to full-up engine systems. The engineers and technicians who operate these test facilities have more than a thousand years of combined experience in this highly specialized field. Marshall has one of the few government test groups in the United States with responsibility for the overall performance of a test program from conception to completion. The Test Laboratory has facilities dating back to the early 1960s, when the test stands needed for the Apollo Program and other scientific endeavors were commissioned and built along the Marshall Center's southern boundary, with logistics access by air, railroad, and barge or boat on the Tennessee River. NASA and its industry partners are designing and developing a new human-rated system based on the requirements for safe, reliable, and cost-effective transportation solutions. Given below are summaries of the Dynamic Test Stand and the Static Test Stand capabilities, along with an introduction to the new missions that these sleeping giants will be fulfilling as NASA readies the Ares I for service in the 2015 timeframe, and plans the development work for fielding the Ares V late next decade (fig. 1). Validating modern computer design models and techniques requires the sorts of data that can only be generated by these one-of-a-kind facilities.

Dumbacher, Daniel L.↗
NASA NTRS2009

Ares I Avionics Introduction

The Ares I is the next generation human-rated launcher for the United States Constellation program. This system is required to provide single fault tolerance within defined crew safety and mission reliability limits. As part of the effort to achieve those safety goals, Ares I includes an avionics subsystem built as a multistring, voting architecture. The avionics design draws upon experience gained from building fly-by-wire systems for Shuttle, X- 38, and Seawolf. Architectural drivers for the avionics design include using proven technologies with existing suppliers of space rated parts for critical functions (to reduce overall development risk), easing the software development effort by using an off-theshelf, DO-178B certifiable, ARINC-653 operating system in the main flight computers, minimizing mutual data and power connections that might lead to a common-mode hardware failure of the redundant avionics strings, and centralizing overall Ares I command & control within the Upper Stage.

Marchant, Christopher C.↗
NASA NTRS2008

Lessons Learned From The EMU Fire and How It Impacts CxP Suit Element Development and Testing

During testing a Space Shuttle Extravehicular Mobility Unit (EMU) pressure garment and life-support backpack was destroyed in a flash fire in the Johnson Space Center's Crew systems laboratory. This slide presentation reviews the accident, probable causes, the lessons learned and the effect this has on the testing and the environment for testing of the Space Suit for the Constellation Program.

Metts, Jonathan↗
NASA NTRS2010

2010 JANNAF Abstract Propulsion System Status: Ares First Stage

In November 2005, NASA created the Constellation Program to develop an entirely new fleet of spacecraft to include the Ares I Crew Launch Vehicle and the Ares V Cargo Launch vehicles. The Ares I First Stage Team has made significant progress on the design of a propulsion system capable of lofting that new fleet. To minimize technical risks and development costs, the Solid Rocket Boosters (SRBs) of Shuttle served as a starting point in the design of a new motor that would meet the requirements of those new vehicles. By bringing in a fifth segment, this new propulsive element will provide greater total impulse to loft a safer, more powerful fleet of space flight vehicles. Additional modifications include the use of composite structures, new metallic forward structures, new parachutes, a new propellant grain design, and a new nozzle. Although still ongoing and in process, significant design, development and concept testing has already been conducted. This includes a full-scale motor firing, deceleration subsystem testing, and testing of several complete avionics line replaceable units. The suborbital development flight, Ares I-X, provided the opportunity to gather critical data about the flight dynamics of the integrated launch vehicle stack. The Ares I-X test flight has also informed our Ares First Stage design. It brought a more comprehensive understanding in a number of areas, which are now being analyzed. This paper will provide an overview of the design, development, challenges, and progress on the production of the new Ares First Stage propulsion system. Challenges and mitigation strategies will be addressed. An overview will also be included of testing to date.

Tiller, Bruce K.↗
NASA NTRS2011

Launch Control Systems: Moving Towards a Scalable, Universal Platform for Future Space Endeavors

The redirection of NASA away from the Constellation program calls for heavy reliance on commercial launch vehicles for the near future in order to reduce costs and shift focus to research and long term space exploration. To support them, NASA will renovate Kennedy Space Center's launch facilities and make them available for commercial use. However, NASA's current launch software is deeply connected with the now-retired Space Shuttle and is otherwise not massively compatible. Therefore, a new Launch Control System must be designed that is adaptable to a variety of different launch protocols and vehicles. This paper exposits some of the features and advantages of the new system both from the perspective of the software developers and the launch engineers.

Sun, Jonathan↗
NASA NTRS2006

Effects of Hydrogen on GRCop-84

This report is a section of the final report on the GRCop-84 task of the Constellation Program and incorporates the results obtained between October 2000 and September 2005 when the program ended. GRCop-84 contains approximately 5.5 wt% Nb. Nb can react with H and embrittle easily. Previous work had indicated the thermodynamic possibility that Cr 2 Nb could react with H and form niobium hydrides in the presence of high pressure H such as seen in the Space Shuttle Main Engine. In this study, samples were charged with H and then tested in both high pressure H and He environments to determine if measurable differences existed which indicate that hydrogen embrittlement occurs in GRCop-84. Tensile, notched tensile, stress rupture and low cycle fatigue properties were surveyed. High pressure H environment stress rupture testing resulted in a lower reduction in area than a high pressure He environment, and the LCF lives at high strain ranges fall below the lower 95 percent confidence interval for the baseline data, but in general no significant differences were noted either between H and He environment tests or between hydrogen charged materials and the baseline, uncharged extruded GRCop-84 data sets. There was also no discernable evidence of the formation of hydrides or changes in fracture morphology indicating hydrogen embrittlement occurred.

Ellis, David L.↗
NASA NTRS2010

Ares I-X Flight Test Development Challenges and Success Factors

The NASA Constellation Program's Ares I-X rocket launched successfully on October 28, 2009 collecting valuable data and providing risk reduction for the Ares I project. The Ares I-X mission was formulated and implemented in less than four years commencing with the Exploration Systems Architecture Study in 2005. The test configuration was founded upon assets and processes from other rocket programs including Space Shuttle, Atlas, and Peacekeeper. For example, the test vehicle's propulsion element was a Shuttle Solid Rocket Motor. The Ares I-X rocket comprised a motor assembly, mass and outer mold line simulators of the Ares I Upper Stage, Orion Spacecraft and Launch Abort System, a roll control system, avionics, and other miscellaneous components. The vehicle was 327 feet tall and weighed approximately 1,800,000 pounds. During flight the rocket reached a maximum speed of Mach 4.8 and an altitude of 150,000 feet. The vehicle demonstrated staging at 130,000 feet, tested parachutes for recovery of the motor, and utilized approximately 900 sensors for data collection. Developing a new launch system and preparing for a safe flight presented many challenges. Specific challenges included designing a system to withstand the environments, manufacturing large structures, and re-qualifying heritage hardware. These and other challenges, if not mitigated, may have resulted in test cancellation. Ares I-X succeeded because the mission was founded on carefully derived objectives, led by decisive and flexible management, implemented by an exceptionally talented and dedicated workforce, and supported by a thorough independent review team. Other major success factors include the use of proven heritage hardware, a robust System Integration Laboratory, multi-NASA center and contractor team, concurrent operations, efficient vehicle assembly, effective risk management, and decentralized element development with a centralized control board. Ares I-X was a technically complex test that required creative thinking, risk taking, and a passion to succeed.

Askins, Bruce↗
NASA NTRS2006

The NASA Constellation University Institutes Project: Thrust Chamber Assembly Virtual Institute

This paper documents key aspects of the Constellation University Institutes Project (CUIP) Thrust Chamber Assembly (TCA) Virtual Institute (VI). Specifically, the paper details the TCA VI organizational and functional aspects relative to providing support for Constellation Systems. The TCA VI vision is put forth and discussed in detail. The vision provides the objective and approach for improving thrust chamber assembly design methodologies by replacing the current empirical tools with verified and validated CFD codes. The vision also sets out ignition, performance, thermal environments and combustion stability as focus areas where application of these improved tools is required. Flow physics and a study of the Space Shuttle Main Engine development program are used to conclude that the injector is the key to robust TCA design. Requirements are set out in terms of fidelity, robustness and demonstrated accuracy of the design tool. Lack of demonstrated accuracy is noted as the most significant obstacle to realizing the potential of CFD to be widely used as an injector design tool. A hierarchical decomposition process is outlined to facilitate the validation process. A simulation readiness level tool used to gauge progress toward the goal is described. Finally, there is a description of the current efforts in each focus area. The background of each focus area is discussed. The state of the art in each focus area is noted along with the TCA VI research focus in the area. Brief highlights of work in the area are also included.

Tucker, P. Kevin↗
NASA NTRS2008

Functional Mobility Testing: A Novel Method to Establish Human System Interface Design Requirements

Across all fields of human-system interface design it is vital to posses a sound methodology dictating the constraints on the system based on the capabilities of the human user. These limitations may be based on strength, mobility, dexterity, cognitive ability, etc. and combinations thereof. Data collected in an isolated environment to determine, for example, maximal strength or maximal range of motion would indeed be adequate for establishing not-to-exceed type design limitations, however these restraints on the system may be excessive over what is basally needed. Resources may potentially be saved by having a technique to determine the minimum measurements a system must accommodate. This paper specifically deals with the creation of a novel methodology for establishing mobility requirements for a new generation of space suit design concepts. Historically, the Space Shuttle and the International Space Station vehicle and space hardware design requirements documents such as the Man-Systems Integration Standards and International Space Station Flight Crew Integration Standard explicitly stated that the designers should strive to provide the maximum joint range of motion capabilities exhibited by a minimally clothed human subject. In the course of developing the Human-Systems Integration Requirements (HSIR) for the new space exploration initiative (Constellation), an effort was made to redefine the mobility requirements in the interest of safety and cost. Systems designed for manned space exploration can receive compounded gains from simplified designs that are both initially less expensive to produce and lighter, thereby, cheaper to launch.

England, Scott A.↗
NASA NTRS2006

A Case for Developing a Ground Based Replication of the Earth, Moon and Mars Spaceflight Infrastructure

When the systems are developed and in place to provide the services needed to operate en route and on the Lunar and Martian surfaces, an Earth based replication will need to be in place for the safety and protection of mission success. The replication will entail all aspects of the flight configuration end to end but will not include any closed loop systems. This would replicate the infrastructure from Lunar and Martian robots, manned surface excursions, through man and unmanned terrestrial bases, through the various types of communication systems and technologies, manned and un-manned space vehicles (large and small), to Earth based systems and control centers. An Earth based replicated infrastructure will enable checkout and test of new technologies, hardware, software updates and upgrades and procedures without putting humans and missions at risk. Analysis of events, what ifs and trouble resolution could be played out on the ground to remove as much risk as possible from any type of proposed change to flight operational systems. With adequate detail, it is possible that failures could be predicted with a high probability and action taken to eliminate failures. A major factor in any mission to the Moon and to Mars is the complexity of systems, interfaces, processes, their limitations, associated risks and the factor of the unknown including the development by many contractors and NASA centers. The need to be able to introduce new technologies over the life of the program requires an end to end test bed to analyze and evaluate these technologies and what will happen when they are introduced into the flight system. The ability to analyze system behaviors end to end under varying conditions would enhance safety e.g. fault tolerances. This analysis along with the ability to mine data from the development environment (e.g. test data), flight ops and modeling/simulations data would provide a level of information not currently available to operations and astronauts. In this paper we will analyze the beginnings of such a replication and what it could do in terms of reducing risk in the near term for development. We will analyze the Space Shuttle Main Engine (SSME) test lab which has to a large extent accomplished this replication for the SSME and has been highly successful in analyzing hardware and software problems and changes. The cost of replicating the flight system as proposed here could be very high if attempted as an afterthought. We will describe the initial steps for the development of a replication of this infrastructure starting with the communication infrastructure. The Constellation of Labs (CofL) under the Command, Control, Communication and Information (C3I) project for the NASA Exploration Initiative will provide the initial foundation upon which to base this replication. Simply put, there is very little margin for error in high latency situations e.g. en-route to/from Mars or in an autonomous process on the Lunar far side. Any thought out approach to reduce risk and increase safety needs to be accomplished end to end with the actual systems configuration.

Bradford, Robert N.↗
NASA NTRS2010

Waterhammer Testing and Modeling of the Ares I Upper Stage Reaction Control System

NASA's Ares I rocket is the agency's first step in completing the goals of the Constellation Program, which plans to deliver a new generation of space explorers into low earth orbit for future missions to the International Space Station, the moon, and other destinations within the solar system. Ares I is a two-stage rocket topped by the Orion crew capsule and its service module. The launch vehicle's First Stage is a single, five-segment reusable solid rocket booster (RSRB), derived from the Space Shuttle Program's four segment RSRB. The vehicle's Upper Stage, being designed at Marshall Space Flight Center (MSFC), is propelled by a single J-2X Main Engine fueled with liquid oxygen and liquid hydrogen. During active Upper Stage flight of the Ares I launch vehicle, the Upper Stage Reaction Control System (US ReCS) will perform attitude control operations for the vehicle. The US ReCS will provide three-axis attitude control capability (roll, pitch, and yaw) for the Upper Stage while the J-2X is not firing and roll control capability while the engine is firing. Because of the requirements imposed upon the system, the design must accommodate rapid pulsing of multiple thrusters simultaneously to maintain attitude control. In support of these design activities and in preparation for Critical Design Review, analytical models of the US ReCS propellant feed system have been developed using the Thermal Hydraulic Library of MSC.EASY5 v.2008, herein referred to as EASY5. EASY5 is a commercially available fluid system modeling package with significant history of modeling space propulsion systems. In Fall 2009, a series of development tests were conducted at MSFC on a cold-flow test article for the US ReCS, herein referred to as System Development Test Article (SDTA). A subset of those tests performed were aimed at examining the effects of waterhammer on a flight-representative system and to ensure that those effects could be quantified with analytical models and incorporated into the design of the flight system. This paper presents an overview of the test article and the test approach, along with a discussion of the analytical modeling methodology. In addition, the results of that subset of development tests, along with analytical model pre-test predictions and post-test model correlations, will also be discussed in detail.

Williams, J. Hunter↗
NASA NTRS2006

Development of the J-2X Engine for the Ares I Crew Launch Vehicle and the Ares V Cargo Launch Vehicle: Building on the Apollo Program for Lunar Return Missions

The United States (U.S.) Vision for Space Exploration directs NASA to develop two new launch vehicles for sending humans to the Moon, Mars, and beyond. In January 2006, NASA streamlined its hardware development approach for replacing the Space Shuttle after it is retired in 2010. Benefits of this approach include reduced programmatic and technical risks and the potential to return to the Moon by 2020, by developing the Ares I Crew Launch Vehicle (CLV) propulsion elements now, with full extensibility to future Ares V Cargo Launch Vehicle (CaLV) lunar systems. This decision was reached after the Exploration Launch Projects Office performed a variety of risk analyses, commonality assessments, and trade studies. The Constellation Program selected the Pratt & Whitney Rocketdyne J-2X engine to power the Ares I Upper Stage Element and the Ares V Earth Departure Stage. This paper narrates the evolution of that decision; describes the performance capabilities expected of the J-2X design, including potential commonality challenges and opportunities between the Ares I and Ares V launch vehicles; and provides a current status of J-2X design, development, and hardware testing activities. This paper also explains how the J-2X engine effort mitigates risk by building on the Apollo Program and other lessons lived to deliver a human-rated engine that is on an aggressive development schedule, with its first demonstration flight in 2012.

Snoddy, Jim↗
NASA NTRS2010

Performance Analysis of Apollo Navigational Starter Routine

The focus of this project is to recreate and analyze the effectiveness of the original Apollo Starter Routine (ASR) which was used to generate the state vector of the Apollo spacecraft based on a series of radiometric observations. The original Apollo navigation software is unavailable in a modern programming language and the original coding has not been preserved. This necessitates its recreation using the original software documentation. Space Shuttle navigation software does not typically use the ASR or an algorithm like it since the Shuttle s state vector is easily deduced from GPS information or other sources. However, this tactic will be ineffective when trying to determine the state vector of a craft approaching, departing or in orbit around the Moon since the GPS network faces the surface of the Earth, not outer space. The recreation of the ASR from the original documentation is therefore vital as a simulation baseline for the navigation software under development for the Constellation program. The algorithms that make up the ASR will be extracted from the original documentation and adapted for and then implemented in a modern programming language; the majority of it will be coded in Matlab. The ASR s effectiveness will then be tested using simulated tracking data. The ability of the ASR to handle realistically noisy data and the accuracy with which it generates state vectors were analyzed. The ASR proved to be robust enough to process data with range and angle noise as large as 10,000 meters and 10(exp -6) radians together and 300,000 meters and 5x10(exp -4) radians separately at Lunar distances. The ASR was able to handle marginally more noise at distances closer to the Earth where the angle noise was less significant. The ASR is capable of effectively processing 40-80 data points gathered at a rate of one per 20 seconds at close Earth orbit and up to 28-40 data points gathered at a rate of one per minute at distant Earth orbit and Lunar orbit.

Ivanov, Stoyan I.↗
NASA NTRS2011

Ground Processing Affordability for Space Vehicles

Launch vehicles and most of their payloads spend the majority of their time on the ground. The cost of ground operations is very high. So, why so often is so little attention given to ground processing during development? The current global space industry and economic environment are driving more need for efficiencies to save time and money. Affordability and sustainability are more important now than ever. We can not continue to treat space vehicles as mere science projects. More RLV's (Reusable Launch Vehicles) are being developed for the gains of reusability which are not available for ELV's (Expendable Launch Vehicles). More human-rated vehicles are being developed, with the retirement of the Space Shuttles, and for a new global space race, yet these cost more than the many unmanned vehicles of today. We can learn many lessons on affordability from RLV's. DFO (Design for Operations) considers ground operations during design, development, and manufacturing-before the first flight. This is often minimized for space vehicles, but is very important. Vehicles are designed for launch and mission operations. You will not be able to do it again if it is too slow or costly to get there. Many times, technology changes faster than space products such that what is launched includes outdated features, thus reducing competitiveness. Ground operations must be considered for the full product Lifecycle, from concept to retirement. Once manufactured, launch vehicles along with their payloads and launch systems require a long path of processing before launch. Initial assembly and testing always discover problems to address. A solid integration program is essential to minimize these impacts, as was seen in the Constellation Ares I-X test rocket. For RLV's, landing/recovery and post-flight turnaround activities are performed. Multi-use vehicles require reconfiguration. MRO (Maintenance, Repair, and Overhaul) must be well-planned--- even for the unplanned problems. Defect limits and standard repairs need to be in-place as well as easily added. Many routine inspections and maintenance can be like an aircraft overhaul. Modifications and technology upgrades should be expected. Another factor affecting ground operations efficiency is trending. It is essential for RLV's, and also useful for ELV's which fly the same or similar models again. Good data analysis of technical and processing performance will determine fixes and improvements needed for safety, design, and future processing. Collecting such data on new or low-frequency vehicles is a challenge. Lessons can be learned from the Space Shuttle, or even the Concorde aircraft. For all of the above topics, efficient business systems must be established for comprehensive program management and good throughput. Drawings, specifications, and manuals for an entire launch vehicle are often in different formats from multiple vendors, plus they have proprietary constraints. Nonetheless, the integration team must ensure that all data needed is compatible and visible to each appropriate team member. Ground processing systems for scheduling, tracking, problem resolution, etc. must be well laid-out. The balance between COTS (commercial off the shelf) and custom software is difficult. Multiple customers, vendors, launch sites, and landing sites add to the complexity of efficient IT (Information Technology) tools.

Ingalls, John↗
NASA NTRS2010

Lessons Learned in Launching Ares I-X

The Ares I-X flight test, scheduled for 2009, is the first opportunity for the Constellation Program and Ares Projects to obtain important data on the in-flight loads, first stage recovery, and ground-handling characteristics of the Ares I crew launch vehicle. The flight test vehicle will incorporate a mix of flight and mockup hardware, reflecting an acceptable representation of the mass and outer mold line characteristics of the operational Ares I vehicle. It will be powered by a four-segment solid rocket motor from the Space Shuttle inventory and will include a fifth, inert spacer segment and new forward structures to make it the same shape as the Ares I first stage. The vehicle also includes mass simulators for the upper stage, Orion crew module, and launch abort system to match the outer mold line of Ares I; an active roll control system; and avionics derived from Shuttle and Atlas hardware. This suborbital mission will take the flight test vehicle from stacking in the Vehicle Assembly Building (VAB) at Kennedy Space Center (KSC) through liftoff, maximum dynamic pressure, first stage separation, and recovery. Ares I-X presented NASA with unique project management challenges. This presentation will address those unique challenges, including managing a virtual nationwide team under a constrained timeline; designing and building the launch vehicle and ground systems; working concurrently with Space Shuttle activities; and integrating technical and management functions. It also will identify key data collected and lessons learned from the flight that will be applied to future exploration missions.

Davis, Stephan R.↗
NASA NTRS2008

An Alternative Method Of Specifying Shock Test Criteria

Shock testing of aerospace vehicle hardware has presented many challenges over the years due to the high magnitude and short duration of the specifications. Recently, component structural failures have occurred during testing that have not manifested themselves on over 200 Space Shuttle solid rocket booster (SRB) flights (two boosters per flight). It is suspected that the method of specifying shock test criteria may be leaving important information out of the test process. The traditional test criteria specification, the shock response spectrum, can be duplicated by any number of waveforms that may not resemble the actual flight test recorded time history. One method of overcoming this limitation is described herein, which may prove useful for qualifying hardware for the upcoming Constellation Program.

Ferebee, R. C.↗
NASA NTRS2010

Seal Analysis for the Ares-I Upper Stage Fuel Tank Manhole Cover

Techniques for studying the performance of Naflex pressure-assisted seals in the Ares-I Upper Stage liquid hydrogen tank manhole cover seal joint are explored. To assess the feasibility of using the identical seal design for the Upper Stage as was used for the Space Shuttle External Tank manhole covers, a preliminary seal deflection analysis using the ABAQUS commercial finite element software is employed. The ABAQUS analyses are performed using three-dimensional symmetric wedge finite element models. This analysis technique is validated by first modeling a heritage External Tank liquid hydrogen tank manhole cover joint and correlating the results to heritage test data. Once the technique is validated, the Upper Stage configuration is modeled. The Upper Stage analyses are performed at 1.4 times the expected pressure to comply with the Constellation Program factor of safety requirement on joint separation. Results from the analyses performed with the External Tank and Upper Stage models demonstrate the effects of several modeling assumptions on the seal deflection. The analyses for Upper Stage show that the integrity of the seal is successfully maintained.

Phillips, Dawn R.↗