Search NASA⌕ Search

SEARCH · Search NASA

Results for “Apollo Docking”

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.

128 records · Page 8

Ares V: Game Changer for National Security Launch

NASA is designing the Ares V cargo launch vehicle to vastly expand exploration of the Moon begun in the Apollo program and enable the exploration of Mars and beyond. As the largest launcher in history, Ares V also represents a national asset offering unprecedented opportunities for new science, national security, and commercial missions of unmatched size and scope. The Ares V is the heavy-lift component of NASA's dual-launch architecture that will replace the current space shuttle fleet, complete the International Space Station, and establish a permanent human presence on the Moon as a stepping-stone to destinations beyond. During extensive independent and internal architecture and vehicle trade studies as part of the Exploration Systems Architecture Study (ESAS), NASA selected the Ares I crew launch vehicle and the Ares V to support future exploration. The smaller Ares I will launch the Orion crew exploration vehicle with four to six astronauts into orbit. The Ares V is designed to carry the Altair lunar lander into orbit, rendezvous with Orion, and send the mated spacecraft toward lunar orbit. The Ares V will be the largest and most powerful launch vehicle in history, providing unprecedented payload mass and volume to establish a permanent lunar outpost and explore significantly more of the lunar surface than was done during the Apollo missions. The Ares V consists of a Core Stage, two Reusable Solid Rocket Boosters (RSRBs), Earth Departure Stage (EDS), and a payload shroud. For lunar missions, the shroud would cover the Lunar Surface Access Module (LSAM). The Ares V Core Stage is 33 feet in diameter and 212 feet in length, making it the largest rocket stage ever built. It is the same diameter as the Saturn V first stage, the S-IC. However, its length is about the same as the combined length of the Saturn V first and second stages. The Core Stage uses a cluster of five Pratt & Whitney Rocketdyne RS-68B rocket engines, each supplying about 700,000 pounds of thrust. Its propellants are liquid hydrogen and liquid oxygen. The two solid rocket boosters provide about 3.5 million pounds of thrust at liftoff. These 5.5-segment boosters are derived from the 4-segment boosters now used on the Space Shuttle, and are similar to those used in the Ares I first stage. The EDS is powered by one J-2X engine. The J-2X, which has roughly 294,000 pounds of thrust, also powers the Ares I Upper Stage. It is derived from the J-2 that powered the Saturn V second and third stages. The EDS performs two functions. Its initial suborbital burns will place the lunar lander into a stable Earth orbit. After the Orion crew vehicle, launched separately on an Ares I, docks with the lander/EDS stack, EDS will ignite a second time to put the combined 65-metric ton vehicle into a lunar transfer orbit. When it stands on the launch pad at Kennedy Space Center late in the next decade, the Ares V stack will be approximately 381 feet tall and have a gross liftoff mass of 8.1 million pounds. The current point-of-departure design exceeds Saturn V s mass capability by approximately 40 percent. Using the current payload shroud design, Ares V can carry 315,000 pounds to 29-degree low Earth orbit (LEO) or 77,000 pounds to a geosynchronous orbit. Another unique aspect of the Ares V is the 33-foot-diameter payload shroud, which encloses approximately 30,400 cubic feet of usable volume. A larger hypothetical shroud for encapsulating larger payloads has been studied. While Ares V makes possible larger payload masses and volumes, it may alternately make possible more cost-effective mission design if the relevant payload communities are willing to consider an alternative to the existing approach that has driven them to employ complexity to solve current launch vehicle mass and volume constraints. By using Ares V s mass and volume capabilities as margin, payload designers stand to reduce development risk and cost. Significant progress has been made on the Ares V to support a plaed fiscal 2011 authority-to-proceed (ATP) milestone. The Ares V team is actively reaching out to external organizations during this early concept phase to ensure that the Ares V vehicle can be leveraged for national security, science, and commercial development needs. This presentation will discuss Ares V vehicle configuration, the path to the current concept, accomplishments to date, and potential payload utilization opportunities.

Sumrall, Phil↗

A Comparison Between Orion Automated and Space Shuttle Rendezvous Techniques

The Orion spacecraft will replace the space shuttle and will be the first human spacecraft since the Apollo program to leave low earth orbit. This vehicle will serve as the cornerstone of a complete space transportation system with a myriad of mission requirements necessitating rendezvous to multiple vehicles in earth orbit, around the moon and eventually beyond . These goals will require a complex and robust vehicle that is, significantly different from both the space shuttle and the command module of the Apollo program. Historically, orbit operations have been accomplished with heavy reliance on ground support and manual crew reconfiguration and monitoring. One major difference with Orion is that automation will be incorporated as a key element of the man-vehicle system. The automated system will consist of software devoted to transitioning between events based on a master timeline. This effectively adds a layer of high level sequencing that moves control of the vehicle from one phase to the next. This type of automated control is not entirely new to spacecraft since the shuttle uses a version of this during ascent and entry operations. During shuttle orbit operations however many of the software modes and hardware switches must be manually configured through the use of printed procedures and instructions voiced from the ground. The goal of the automation scheme on Orion is to extend high level automation to all flight phases. The move towards automation represents a large shift from current space shuttle operations, and so these new systems will be adopted gradually via various safeguards. These include features such as authority-to-proceed, manual down modes, and functional inhibits. This paper describes the contrast between the manual and ground approach of the space shuttle and the proposed automation of the Orion vehicle. I will introduce typical orbit operations that are common to all rendezvous missions and go on to describe the current Orion automation architecture and contrast it with shuttle rendezvous techniques and circumstances. The shuttle rendezvous profile is timed to take approximately 3 days from orbit insertion to docking at the International Space Station (ISS). This process can be divided into 3 phases: far-field, mid-field and proximity operations. The far-field stage is characterized as the most quiescent phase. The spacecraft is usually too far to navigate using relative sensors and uses the Inertial Measurement Units (IMU s) to numerically solve for its position. The maneuvers are infrequent, roughly twice per day, and are larger than other burns in the profile. The shuttle uses this opportunity to take extensive ground based radar updates and keep high fidelity orbit states on the ground. This state is then periodically uplinked to the shuttle computers. The targeting solutions for burn maneuvers are also computed on the ground and uplinked. During the burn the crew is responsible for setting the shuttle attitude and configuring the propulsion system for ignition. Again this entire process is manually driven by both crew and ground activity. The only automatic processes that occur are associated with the real-time execution of the burn. The Orion automated functionality will seek to relieve the workload of both the crew and ground during this phase

Ruiz, Jose O,↗