Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Apollo project”

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 721 records · Page 40
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Going South: Warnings from the Largest Project Engineering Failure in Modern History

NASA’s successful conduct of the Apollo Program greatly enhanced the prestige of the United States and remains broadly accepted as America’s gift “for all Mankind.” NASA’s Artemis Program to return humanity to the Moon promises to again reveal America’s leadership in this field. In preparation for the initiation of Artemis and its predecessor project Constellation, NASA thoroughly examined space program precedents. There remains, however, another relevant precedent which has not been examined in this context. Though this project involved technology radically different from that managed by NASA, its scope and environment in many ways parallel NASA’s large programs. This project was initiated by a private sector team that had, ten years before, successfully completed an effort that, at a cost of $275 billion (in 2021 USD), had stimulated new technology, had brought economic growth, had established their country as the world leader in engineering innovation, and, though it was a commercial success, had been broadly accepted as their nation’s gift “to all Mankind.” The new project was inspired by popular belief that private capital could again be marshalled to enhance national prestige and make yet another major contribution to the progress of Humanity. This new effort was predicted to require eight years and $258 billion. However, after the passage of nine years, achievement of only 45% complete on the baseline design, and expenditures 96% beyond the baseline cost, the project collapsed amid bankruptcy, political scandal, and criminal prosecution. While the private sector team that carried out this project was exceptionally well educated and experienced in the field, their efforts resulted in what remains (in terms of the money wasted) the largest project engineering failure in modern history. This paper examines what went wrong.

Project Management↗
NASA NTRS1973

Magnetic measurements of the solar wind interaction with the moon

The magnetic signature of the interaction between the moon and the solar wind (as observed by the Apollo 15 subsatellite) is an enhanced field directly behind the moon, bounded on either side by two dips in the field strength. On occasion, compressions of the field strength are observed external to either one or sometimes both of these dips. Theories of the interaction postulate either that these compressions are a general feature of the solar wind-moon interaction modulated by changes in the solar wind parameters or that they are associated with the appearance of specific lunar regions at the limbs. The measurements of the lunar magnetic field with the Apollo 15 and 16 subsatellites, the mapping of projected source positions of limb compressions onto the lunar surface, and the study of the persistence of limb compressions supports the hypothesis that limb compressions are formed when regions of high magnetization are at the lunar limbs.

Lichtenstein, B. R.↗
NASA NTRS1972

Effects of geophysical extra-terrestrial and terrestrial physical stimuli on living organisms - Effects of gravity fields on living organisms

The biologic effects of greatly reduced gravity resulting from space flight are examined. Aspects of U.S. space biology during the period from 1960 to 1972 are discussed, giving attention to the Discoverer satellites, the Gemini series, the OV1-4 satellite, the biosatellite project, the orbiting frog otolith experiment, and the Apollo program. Other studies considered are related to the effects of galactic particles on nonproliferating cells, a recoverable tissue culture experiment, cell cycle maintenance in human lung cells, and effects of space flight on circadian rhythms. Viking will land on the planet Mars in 1975 in search for life forms.

Saunders, R. J. F.↗
NASA NTRS1995

Spaceflight revolution: NASA Langley Research Center from Sputnik to Apollo

As part of the transition to the broad research scope of the National Aeronautics and Space Administration (NASA) starting in the late 1950's, the Langley Research Center underwent many changes in program content, organization and management, and areas of personnel expertise. This book describes and evaluates the evolution and activities of the Langley Research Center during the seventeen-year period from 1958 to 1975. The book was based on the analysis of hundreds of written records, both published and unpublished, as well as numerous personal interviews with many of the key individuals involved in the transition of Langley. Some of the projects and research areas covered include Project Echo, magnetoplasmadynamics research, Scout Rocket Program, lunar-orbit rendezvous research, manned space laboratory development, and Apollo and the Lunar Orbiter Project.

Hansen, James R.↗
NASA NTRS1973

The Apollo/Soyuz test project

Consideration of the problems involved in the maneuvers executed by the Apollo Command and Service Module in docking with the Soyuz spacecraft. A detailed description is given of the Docking Module, which will serve as a kind of adaptor between the American and Soviet systems. Particular stress is placed on problems connected with the difference in atmosphere of the two vehicles and on the possibility of reducing this difference to the point where prebreathing of pure oxygen is not required when going from the Soviet vehicle with its air atmosphere to the American vehicle with its pure oxygen atmosphere. Also considered are problems connected with the use of different latching systems - an electromechanical attenuation system in the Soviet vehicle, and a hydraulic system in the Apollo Module.

Petrone, R. A.↗
NASA NTRS2016

Restoration of Apollo Data by the Lunar Data Project/PDS Lunar Data Node: An Update

The Apollo 11, 12, and 14 through 17 missions orbited and landed on the Moon, carrying scientific instruments that returned data from all phases of the missions, included long-lived Apollo Lunar Surface Experiments Packages (ALSEPs) deployed by the astronauts on the lunar surface. Much of these data were never archived, and some of the archived data were on media and in formats that are outmoded, or were deposited with little or no useful documentation to aid outside users. This is particularly true of the ALSEP data returned autonomously for many years after the Apollo missions ended. The purpose of the Lunar Data Project and the Planetary Data System (PDS) Lunar Data Node is to take data collections already archived at the NASA Space Science Data Coordinated Archive (NSSDCA) and prepare them for archiving through PDS, and to locate lunar data that were never archived, bring them into NSSDCA, and then archive them through PDS. Preparing these data for archiving involves reading the data from the original media, be it magnetic tape, microfilm, microfiche, or hard-copy document, converting the outmoded, often binary, formats when necessary, putting them into a standard digital form accepted by PDS, collecting the necessary ancillary data and documentation (metadata) to ensure that the data are usable and well-described, summarizing the metadata in documentation to be included in the data set, adding other information such as references, mission and instrument descriptions, contact information, and related documentation, and packaging the results in a PDS-compliant data set. The data set is then validated and reviewed by a group of external scientists as part of the PDS final archive process. We present a status report on some of the data sets that we are processing.

Lunar↗
NASA NTRS2010

Operational Lessons Learned from the Ares I-X Flight Test

The Ares I-X flight test, launched in 2009, is the first test of the Ares I crew launch vehicle. This development flight test evaluated the flight dynamics, roll control, and separation events, but also provided early insights into logistical, stacking, launch, and recovery operations for Ares I. Operational lessons will be especially important for NASA as the agency makes the transition from the Space Shuttle to the Constellation Program, which is designed to be less labor-intensive. The mission team itself comprised only 700 individuals over the life of the project compared to the thousands involved in Shuttle and Apollo missions; while missions to and beyond low-Earth orbit obviously will require additional personnel, this lean approach will serve as a model for future Constellation missions. To prepare for Ares I-X, vehicle stacking and launch infrastructure had to be modified at Kennedy Space Center's Vehicle Assembly Building (VAB) as well as Launch Complex (LC) 39B. In the VAB, several platforms and other structures designed for the Shuttle s configuration had to be removed to accommodate the in-line, much taller Ares I-X. Vehicle preparation activities resulted in delays, but also in lessons learned for ground operations personnel, including hardware deliveries, cable routing, transferred work and custodial paperwork. Ares I-X also proved to be a resource challenge, as individuals and ground service equipment (GSE) supporting the mission also were required for Shuttle or Atlas V operations at LC 40/41 at Cape Canaveral Air Force Station. At LC 39B, several Shuttle-specific access arms were removed and others were added to accommodate the in-line Ares vehicle. Ground command, control, and communication (GC3) hardware was incorporated into the Mobile Launcher Platform (MLP). The lightning protection system at LC 39B was replaced by a trio of 600-foot-tall towers connected by a catenary wire to account for the much greater height of the vehicle. Like Shuttle, Ares I-X will be stacked on a MLP and rolled out to the pad on a Saturn-era crawler-transporter. While Ares I-X was only held in place by the four hold-down posts on its aft skirt during rollout, a new vehicle stabilization system (VSS) attached to the vertical service structure kept the vehicle from undue swaying prior to launch at the pad, LC 39B. Following the launch, the flight test vehicle first stage was recovered with the aid of new parachutes resized to accommodate the five-segment-long first stage, which had a much greater length and mass than the Shuttle s reusable solid rocket boosters. After splashdown, recovery divers exercised extra care when handling the first stage to ensure that the flight data recorders in the fifth segment simulator were not damaged by exposure to sea water. The data recovered from the Ares I-X flight test will be very valuable in verifying the predicted environments and models used to design the vehicle. Lessons learned from Ares I-X will be shared with the Ares Projects through written and verbal reports and through integration of mission team members into the Project workforce.

Davis, Stephan R.↗
NASA NTRS1989

Systems interoperability approach Apollo/Soyuz test project

The aproach used to design and develop the hardware and to insure the compatibility of existing systems used for the Apollo/Soyuz test project mission, are described. This mission used slightly modified Apollo and Soyuz spacecraft, a new jointly designed docking system, a new docking module (used as an airlock), and many existing flight and ground systems. The working groups major responsibilities and the documentation to control the technical agreements and information exchange are summarized.

Wade, Donald C.↗
NASA NTRSDate not supplied

Content and Representation of Information Needed to Support Time-Constrained Problem Solving

NASA’s current mission-operations paradigm originated with Project Mercury and endured with minimum evolution through the Apollo Program, Space Shuttle Program, and ISS missions. At its foundation is a near-complete real-time dependence on a ground team to manage the combined state of the mission, vehicle, and crew. Utilizing many engineers and operators with broad and deep expertise; large, distributed datasets including extensive telemetry; and expansive analytical and computing power, this ground team has served as the safety net for crewed spaceflight missions over the past 60 years. This approach must change to address challenges associated with missions beyond low Earth orbit (BLEO), including infrequent resupply, reduced ability to evacuate, and delayed communications that prohibit real-time operational support. We anticipate that a necessary part of this change will be increased independence for the crew, as roles and responsibilities traditionally performed by ground teams move on board the vehicle. While many risks are associated with Earth-independent operations, one particular concern is ensuring that the crew will have adequate onboard support to perform urgent problem solving when communication with the ground is delayed or intermittent. A key resource that enables the ground team to respond to anomalies quickly and effectively is the extraordinary expertise and experience it possesses. It is comprised of 80+ experts on at any given time, with a combined 600+ years of system-specific experience across 22 unique console disciplines. A small crew will face the unprecedented challenge of independently responding to anomalies that have historically been handled by a team 20 times their size. Another important resource upon which the ground heavily relies to support procedure execution and anomaly response is data. The amount of telemetry data that each flight controller monitors is extensive. In addition, as the ground team works to further assess impacts, trouble shoot, identify workarounds, and oversee procedure execution, it accesses and synthesizes engineering and procedure information, as well as system build, test, and configuration documentation. It is not feasible nor useful to put all these data onboard as crews become more Earth independent. Each member of a small Mars mission small crew will have multiple roles beyond monitoring telemetry and data gathering, and multiple roles within anomaly resolution processes, thereby limiting their capacity for copious amounts of information. Moreover, while access is necessary, it alone is insufficient. Information will need to be compiled, refined, and represented appropriately to support the crew’s reduced attention and expertise. This work seeks to understand the content and representation of information needed to support time-constrained problem solving and decision making by the crew without real-time ground support. To build this understanding, we first surveyed the literature, focusing on how expert problem solvers construct and manipulate their mental models. Next, we interviewed expert problem solvers in spaceflight and analogous domains and surveyed industry solutions for data presentation. Finally, we analyzed current spaceflight operations by investigating flight controller anomaly resolution processes during ISS training simulations and real operational events. These methods led to creating a problem-solving framework that details common themes and features of attending to, assessing, analyzing, and acting on problems in complex, time-constrained domains. Using this framework and the results of our analysis, we identified conceptual data representations needed for crew-led problem-solving. Preliminary onboard user interface concepts to meet identified needs will be presented.

anomaly response↗
NASA NTRS2011

Apollo Lunar Sample Photographs: Digitizing the Moon Rock Collection

The Acquisition and Curation Office at JSC has undertaken a 4-year data restoration project effort for the lunar science community funded by the LASER program (Lunar Advanced Science and Exploration Research) to digitize photographs of the Apollo lunar rock samples and create high resolution digital images. These sample photographs are not easily accessible outside of JSC, and currently exist only on degradable film in the Curation Data Storage Facility

Lofgren, Gary E.↗
NASA NTRS2016

Preserving, Enhancing, and Continuing the Scientific Legacy of the Apollo Sample Suite

From 1969 to 1972, Apollo astronauts collected 382 kg of rocks, soils, and core samples from six geologically diverse locations on the Moon. In the nearly 50 years since the samples were collected, over 3000 different studies have been conducted using the nearly 2200 different Apollo samples. Despite the maturity of the sample collection, many new studies of lunar samples are undertaken each year, with an average of more than 55 requests and more than 600 distinct subsamples allocated annually over the past five years. The Apollo samples are a finite resource, however. Although new studies are encouraged, it is important that new studies do not duplicate previous studies, and where possible, leverage previous results to inform and enhance the current studies. This helps to preserve the samples and scientific funding, both of which are precious resources. We have initiated several new efforts to rescue some of the early analyses from these samples, including unpublished analytical data. We are actively scanning NASA documentation in paper form that is related to the Apollo missions and sample processing, and we are collaborating with IEDA to establish a geochemical data base called MoonDB. To populate this database, we are actively working with about a dozen prominent lunar PIs to organize and transcribe years of both published and unpublished data, making it available to all researchers. This effort will also take advantage of new online analytical tools like PetDB. There have already been tangible results from the MoonDB data rescue effort. A pilot project involving the rescue of geochemical data of John Delano on Apollo pyroclastic glasses has already been referenced in multiple Apollo sample requests, and in fact, the compiled data was used as part of one of the new studies. Similarly, scanned sample handling reports have been utilized to find previously analyzed samples that were appropriate to fulfill new sample requests. We have also begun to image the Apollo samples using (1) micro‐CT scanning to document the interior structure of samples, and (2) comprehensive high resolution photography of samples, enabling high resolution 3D reconstructions of the samples. Both efforts will provide comprehensive access to these samples and allow for more targeted requests, and thus better curation of the samples for decades to come.

Zeigler, Ryan↗
NASA NTRS2006

Survey of Dust Issues for Lunar Seals and the RESOLVE Project

Lunar dust poses a technical challenge for sealing applications on the moon. A survey of seals used in Apollo lunar missions is presented as well as lunar soil characteristics and a description of the lunar environment. Seal requirements and technical challenges for the volatiles characterization oven and hydrogen reduction reaction chamber of the RESOLVE project are discussed. The purpose of the RESOLVE project is to find water or ice in lunar soil and demonstrate the ability to produce water, and hence oxygen and hydrogen, from lunar regolith for life support and propellants.

Proctor, Margaret P.↗
NASA NTRS2011

Leveraging the Cloud for Robust and Efficient Lunar Image Processing

The Lunar Mapping and Modeling Project (LMMP) is tasked to aggregate lunar data, from the Apollo era to the latest instruments on the LRO spacecraft, into a central repository accessible by scientists and the general public. A critical function of this task is to provide users with the best solution for browsing the vast amounts of imagery available. The image files LMMP manages range from a few gigabytes to hundreds of gigabytes in size with new data arriving every day. Despite this ever-increasing amount of data, LMMP must make the data readily available in a timely manner for users to view and analyze. This is accomplished by tiling large images into smaller images using Hadoop, a distributed computing software platform implementation of the MapReduce framework, running on a small cluster of machines locally. Additionally, the software is implemented to use Amazon's Elastic Compute Cloud (EC2) facility. We also developed a hybrid solution to serve images to users by leveraging cloud storage using Amazon's Simple Storage Service (S3) for public data while keeping private information on our own data servers. By using Cloud Computing, we improve upon our local solution by reducing the need to manage our own hardware and computing infrastructure, thereby reducing costs. Further, by using a hybrid of local and cloud storage, we are able to provide data to our users more efficiently and securely. 12 This paper examines the use of a distributed approach with Hadoop to tile images, an approach that provides significant improvements in image processing time, from hours to minutes. This paper describes the constraints imposed on the solution and the resulting techniques developed for the hybrid solution of a customized Hadoop infrastructure over local and cloud resources in managing this ever-growing data set. It examines the performance trade-offs of using the more plentiful resources of the cloud, such as those provided by S3, against the bandwidth limitations such use encounters with remote resources. As part of this discussion this paper will outline some of the technologies employed, the reasons for their selection, the resulting performance metrics and the direction the project is headed based upon the demonstrated capabilities thus far.

Cloud Computing↗
NASA NTRS2009

Overview of the Altair Lunar Lander Thermal Control System Design

NASA's Constellation Program has been developed to successfully return humans to the Lunar surface prior to 2020. The Constellation Program includes several different project offices including Altair, which is the next generation Lunar Lander. The planned Altair missions are very different than the Lunar missions accomplished during the Apollo era. These differences have resulted in a significantly different thermal control system architecture. The Altair project has employed a rather unique development approach as compared with previous manned spacecraft programs. Altair started the design process by developing a single-string (no fault tolerance), minimum functionality design. This first design and analysis cycle resulted in the baseline design for the entire process. From this point of departure, Altair continued the development process by adding vehicle functionality for the purposes of minimizing the risk of Loss Of Crew (LOC) and Loss Of Mission (LOM). Through the subsequent design and analysis cycles, the project office compared the added mass associated with the reduction of LOC/LOM and selected the most mass efficient design solutions. The current paper will summarize the Altair mission profile, the operational phases, and the LOC/LOM decisions that were made during the various design cycles. The evolution of the thermal control system design through Lunar Design and Analysis Cycle 3 (LDAC-3) will also be described in this paper.

Stephan, Ryan A.↗
NASA NTRS1972

Astronomical photography. Part A: Gum nebula, galactic cluster, and zodiacal light photography

It is reported that the Apollo 16 command module astronomical photography was performed with the specific objective of capitalizing on the uniqueness of the double umbra as a vantage point to collect astronomical data that are obtainable only near our Moon. For this reason, these data will be compared directly to analogous photography performed from Earth orbit during Project Mercury and the Gemini Program as well as to the Apollo-duplicated photography taken from sites on the Earth surface. Comparison with Earth-based photography should yield direct information on the Earth airglow layer and on atmospheric scattering and extinction.

Mercer, R. D.↗