Search NASA⌕ Search

SEARCH · Search NASA

Results for “separation assurance”

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 253 records · Page 14

Evaluation of available analytical techniques for monitoring the quality of space station potable water

To assure the quality of potable water (PW) on the Space Station (SS) a number of chemical and physical tests must be conducted routinely. After reviewing the requirements for potable water, both direct and indirect analytical methods are evaluated that could make the required tests and improvements compatible with the Space Station operation. A variety of suggestions are made to improve the analytical techniques for SS operation. The most important recommendations are: (1) the silver/silver chloride electrode (SB) method of removing I sub 2/I (-) biocide from the water, since it may interfere with analytical procedures for PW and also its end uses; (2) the orbital reactor (OR) method of carrying out chemistry and electrochemistry in microgravity by using a disk shaped reactor on an orbital table to impart artificial G force to the contents, allowing solution mixing and separation of gases and liquids; and (3) a simple ultra low volume highly sensitive electrochemical/conductivity detector for use with a capillary zone electrophoresis apparatus. It is also recommended, since several different conductivity and resistance measurements are made during the analysis of PW, that the bipolar pulse measuring circuit be used in all these applications for maximum compatibility and redundancy of equipment.

Geer, Richard D.↗

Far Ultraviolet Imaging from the Image Spacecraft: System Design - 1

Direct imaging of the magnetosphere by the IMAGE spacecraft A,ill be supplemented by observation of the global aurora, the footprint of magnetospheric regions. To assure the simultaneity of these observations and tile measurement of the magnetospheric back-round neutral gas density, the IMAGE satellite instrument complement includes three Far Ultraviolet (FUV) instruments. In tile wavelength region 120-1 90 nm. a downward-viewing aurora imager is only minimally contaminated sunlight, scattered from clouds and ground, and radiance of the aurora observed in a nadir viewing geometry can be observed in the presence of the high-latitude day-low. Tile Wideband Imaging Camera (WIC) will provide broadband ultraviolet images of the aurora for maximum spatial and temporal resolution by imaging the LBH N2 bands of the aurora. The Spectrographic Imager (SI), a monochromatic imager, will image different types of aurora, filtered by wavelength. By measuring the Doppler-shifted Lyman-alpha, the proton-induced component of the aurora will be imaged separately. Finally, the GEO instrument will observe the distribution of the geocoronal emission, which is a measure of the neutral background density source of the charge exchange in the magnetosphere. The FUV instrument complement looks radially outward from the rotating IMAGE satellite and, therefore, it spends only a short time observing tile aurora and the Earth during, each spin. Detailed descriptions of the WIC, Si, GEO, and their individual performance validations are discussed in companion papers. This paper summarizes the system requirements and system design approach taken to satisfy the science requirements. One primary requirement is to maximize photon collection efficiency and use efficiently tile short time available foe exposures. The FUV auroral imagers WIC and SI both have wide fields of view and take data continuously as the auroral region proceeds through the field of view. To minimize data volume, multiple images are taken and electronically co-added by suitably shifting each image to compensate for the spacecraft rotation. In order to minimize resolution loss, the images have to be distortion-corrected in real time foe both WIC and Si prior to co-adding. The distortion correction is accomplished using high-speed look Lip tables that are pre-generated by least square fitting to polynomial functions by the on-orbit processor. The instruments were calibrated individually while on stationary platforms, mostly in vacuum chambers as described in the companion papers. Extensive -round-based testing was performed with visible and near UV simulators mounted oil a rotating platform to estimate their on-orbit performance. The predicted instrument system performance is summarized and some of the preliminary data formats are shown.

Mende, S. B.↗

Postlanding optimum designs for the assured crew return vehicle

The optimized preliminary engineering design concepts for postlanding operations of a water-landing Assured Crew Return Vehicle (ACRV) during a medical rescue mission are presented. Two ACRVs will be permanently docked to Space Station Freedom, fulfilling NASA's commitment to Assured Crew Return Capability in the event of an accident or illness. The optimized configuration of the ACRV is based on an Apollo command module (ACM) derivative. The scenario assumes landing a sick or injured crewmember on water with the possibility of a delayed rescue. Design emphasis is placed on four major areas. First is the design of a mechanism that provides a safe and time-critical means of removing the sick or injured crewmember from the ACRV. Support to the assisting rescue personnel is also provided. Second is the design of a system that orients and stabilizes the craft after landing so as to cause no further injury or discomfort to the already ill or injured crewmember. Third is the design of a system that provides full medical support to a sick or injured crewmember aboard the ACRV from the time of separation from the space station to rescue by recovery forces. Last is the design of a system that provides for the comfort and safety of the entire crew after splashdown up to the point of rescue. The four systems are conceptually integrated into the ACRV.

Hosterman, Kenneth C.↗

Integrating Formal Methods and Testing 2002

Traditionally, qualitative program verification methodologies and program testing are studied in separate research communities. None of them alone is powerful and practical enough to provide sufficient confidence in ultra-high reliability assessment when used exclusively. Significant advances can be made by accounting not only tho formal verification and program testing. but also the impact of many other standard V&V techniques, in a unified software reliability assessment framework. The first year of this research resulted in the statistical framework that, given the assumptions on the success of the qualitative V&V and QA procedures, significantly reduces the amount of testing needed to confidently assess reliability at so-called high and ultra-high levels (10-4 or higher). The coming years shall address the methodologies to realistically estimate the impacts of various V&V techniques to system reliability and include the impact of operational risk to reliability assessment. Combine formal correctness verification, process and product metrics, and other standard qualitative software assurance methods with statistical testing with the aim of gaining higher confidence in software reliability assessment for high-assurance applications. B) Quantify the impact of these methods on software reliability. C) Demonstrate that accounting for the effectiveness of these methods reduces the number of tests needed to attain certain confidence level. D) Quantify and justify the reliability estimate for systems developed using various methods.

Cukic, Bojan↗

Technology Infusion of CodeSonar into the Space Network Ground Segment (RII07): Software Assurance Symposium Technical Summary

Presents a source code analysis tool (CodeSonar) for use in the Space Network Ground Segment. The Space Network requires 99.9% proficiency and 97.0% availability of systems. Software has historically accounted for an annual average of 28% of the Space Network loss of availability and proficiency. CSCI A and CSCI B account for 42% of the previous eight months of software data loss. The technology infusion of CodeSonar into the Space Network Ground segment is meant to aid in determining the impact of the technology on the project both in the expenditure of effort and the technical results of the technology. Running a CodeSonar analysis and performing a preliminary review of the results averaged 3.5 minutes per finding (approximately 20 hours total). An additional 40 hours is estimated to analyze the 37 findings deemed too complex for the initial review. Using CodeSonar's tools to suppress known non-problems, delta tool runs will not repeat findings that have been marked as non-problems, further reducing the time needed for review. The 'non-interesting' finding rate of 70% is a large number, but filtering, search, and detailed contextual features of CodeSonar reduce the time per finding. Integration of the tool into the build process may also provide further savings by preventing developers from having to configure and operate the tool separately. These preliminary results show the tool to be easy to use and incorporate into the engineering process. These findings also provide significant potential improvements in proficiency and availability on the part of the software. As time-to-fix data become available a better cost trade can be made on person hours saved versus tool cost. Selective factors may be necessary to determine where best to apply CodeSonar to balance cost and benefits.

Benson, Markland J.↗

Urban Air Mobility Airspace Dynamic Density

Airspace safety must be assured for Urban Air Mobility (UAM) to become reality. Emerging operations need to safely integrate with existing and future air traffic. UAM is anticipated to evolve in stages. Early stages, characterized by low-density operations, may be accommodated by traditional air traffic management approaches. However, to enable the scale of UAM operations necessary to reach ubiquitous integration into daily life, new paradigms that utilize collaborative and automated systems are being considered. Correspondingly, traditional approaches for determining a safe number of simultaneous operations in an airspace must be adapted to suit evolving traffic management paradigms. In this paper, we examine dynamic density as an approach to determine when an airspace is excessively populated, and safety may become compromised. We review previous work on dynamic density as it relates to air traffic controller workload and propose factors that may be more fitting for UAMs. Rather than considering controller workload, we propose factors that suggest increased likelihood of loss of separation and may lead to conflicts that require tactical avoidance maneuvers. In addition to monitoring dynamic density for tactical decision making, we endeavor to predict airspace dynamic density with adequate look-ahead to allow for strategic route selection.

UAM↗

Station Program Note Pull Automation

Upon commencement of my internship, I was in charge of maintaining the CoFR (Certificate of Flight Readiness) Tool. The tool acquires data from existing Excel workbooks on NASA's and Boeing's databases to create a new spreadsheet listing out all the potential safety concerns for upcoming flights and software transitions. Since the application was written in Visual Basic, I had to learn a new programming language and prepare to handle any malfunctions within the program. Shortly afterwards, I was given the assignment to automate the Station Program Note (SPN) Pull process. I developed an application, in Python, that generated a GUI (Graphical User Interface) that will be used by the International Space Station Safety & Mission Assurance team here at Johnson Space Center. The application will allow its users to download online files with the click of a button, import SPN's based on three different pulls, instantly manipulate and filter spreadsheets, and compare the three sources to determine which active SPN's (Station Program Notes) must be reviewed for any upcoming flights, missions, and/or software transitions. Initially, to perform the NASA SPN pull (one of three), I had created the program to allow the user to login to a secure webpage that stores data, input specific parameters, and retrieve the desired SPN's based on their inputs. However, to avoid any conflicts with sustainment, I altered it so that the user may login and download the NASA file independently. After the user has downloaded the file with the click of a button, I defined the program to check for any outdated or pre-existing files, for successful downloads, to acquire the spreadsheet, convert it from a text file to a comma separated file and finally into an Excel spreadsheet to be filtered and later scrutinized for specific SPN numbers. Once this file has been automatically manipulated to provide only the SPN numbers that are desired, they are stored in a global variable, shown on the GUI, and transferred over to a new Excel worksheet for comparison. I managed to get my application to acquire the CSWG (Computer Safety Working Group) and the SPNWG (Space Station Working Group) SPN's with just two mouse clicks for each pull, as opposed to several from the original process. When all three pulls are performed, an Excel sheet containing all three different results will be generated for the user to compare and determine which SPN's will be presented or reviewed the following month. The experience from this internship has been spectacular. As a high school senior who will begin attending college in the fall, this internship has been both educationally and occupationally beneficial. The internship has allowed me the opportunities to learn new programming languages, effectively network with NASA personnel from a variety of departments at JSC, and allowed me to learn new professional skills and etiquette. My internship at NASA's Johnson Space Center has further motivated me to pursue a Master's degree in Software Engineering and strive for a prosperous career with NASA as a civil servant.

Delgado, Ivan↗

Advanced Modular Power Approach to Affordable, Supportable Space Systems

Recent studies of missions to the Moon, Mars and Near Earth Asteroids (NEA) indicate that these missions often involve several distinct separately launched vehicles that must ultimately be integrated together in-flight and operate as one unit. Therefore, it is important to see these vehicles as elements of a larger segmented spacecraft rather than separate spacecraft flying in formation. The evolution of large multi-vehicle exploration architecture creates the need (and opportunity) to establish a global power architecture that is common across all vehicles. The Advanced Exploration Systems (AES) Modular Power System (AMPS) project managed by NASA Glenn Research Center (GRC) is aimed at establishing the modular power system architecture that will enable power systems to be built from a common set of modular building blocks. The project is developing, demonstrating and evaluating key modular power technologies that are expected to minimize non-recurring development costs, reduce recurring integration costs, as well as, mission operational and support costs. Further, modular power is expected to enhance mission flexibility, vehicle reliability, scalability and overall mission supportability. The AMPS project not only supports multi-vehicle architectures but should enable multi-mission capability as well. The AMPS technology development involves near term demonstrations involving developmental prototype vehicles and field demonstrations. These operational demonstrations not only serve as a means of evaluating modular technology but also provide feedback to developers that assure that they progress toward truly flexible and operationally supportable modular power architecture.

Oeftering, Richard C.↗

Decoupling the Effects of Anthropogenic Emission Reductions from the Meteorology and Natural Emissions in TROPOMI NO 2 Retrievals During the 2020 COVID-19 Lockdowns

Satellite measurements during the COVID-19 lockdowns that began in 2020 revealed unprecedented reductions in NO 2 tropospheric vertical column densities (VCD). These reductions have largely been attributed to reduced anthropogenic emissions associated with abrupt decreases in road traffic and other power consuming business activities. Although decreased emissions tended to be the main contributor to the observed NO 2 VCD reduction, meteorological variability also played a role. Whereas the observed VCD changes were predominantly negative in places where public health policies were strictly enforced, meteorology had both positive and negative effects over short time intervals. Here, we present results from a global study of the NO 2 reductions aimed at disentangling the meteorological and natural emission variability from the anthropogenic emissions over the world’s most populated megacities. For this study, NASA’s TROPOMI NO 2 algorithm was used in conjunction with the Global Modeling Initiative (GMI) chemical transport model to separate the contributions due emissions and meteorology. A priori NO 2 profiles were generated from two GMI simulations performed for 2020 at a resolution of 0.25° longitude x 0.25° latitude. The first simulation used updated, COVID-impacted NOX emissions based on Forster et al. (2020), while the second simulation used the 2019 emissions with the 2020 meteorology, referred to here as 2020BAU. The 2020BAU data set allowed for the decoupling of the emission component from the meteorology. When compared to the same period in 2019, NO 2 column amounts during the lockdowns were reduced in 35 out of 36 cities. While reduced emissions contributed most to the observed total change in NO 2 during the lockdowns, the effects of meteorology were significant, ranging between 40% (Chennai) and 15% (Beijing). In China, an increase in NO 2 levels due to meteorology were observed in five out of the seven cities considered in the study. Use of different a-priori NO 2 profiles from the two simulations in our TROPOMI retrievals allowed for a determination of retrieval errors that ranged from -1.7% to -11.0%. We used the quality assurance flag > 0.75 to select the highest quality scenes in the study period. Using the GMI, we estimated the sampling biases to be in the range -11% to 10% of the total change for the cities in our study.

Brad Fisher↗

Mock Certification Basis for an Unmanned Rotorcraft for Precision Agricultural Spraying

This technical report presents the results of a case study using a hazard-based approach to develop preliminary design and performance criteria for an unmanned agricultural rotorcraft requiring airworthiness certification. This case study is one of the first in the public domain to examine design and performance criteria for an unmanned aircraft system (UAS) in tandem with its concept of operations. The case study results are intended to support development of airworthiness standards that could form a minimum safety baseline for midsize unmanned rotorcraft performing precision agricultural spraying operations under beyond visual line-of-sight conditions in a rural environment. This study investigates the applicability of current methods, processes, and standards for assuring airworthiness of conventionally piloted (manned) aircraft to assuring the airworthiness of UAS. The study started with the development of a detailed concept of operations for precision agricultural spraying with an unmanned rotorcraft (pp. 5-18). The concept of operations in conjunction with a specimen unmanned rotorcraft were used to develop an operational context and a list of relevant hazards (p. 22). Minimum design and performance requirements necessary to mitigate the hazards provide the foundation of a proposed (or mock) type certification basis. A type certification basis specifies the applicable standards an applicant must show compliance with to receive regulatory approval. A detailed analysis of the current airworthiness regulations for normal-category rotorcraft (14 Code of Federal Regulations, Part 27) was performed. Each Part 27 regulation was evaluated to determine whether it mitigated one of the relevant hazards for the specimen UAS. Those regulations that did were included in the initial core of the type certification basis (pp. 26-31) as written or with some simple modifications. Those regulations that did not mitigate a recognized hazard were excluded from the certification basis. The remaining regulations were applicable in intent, but the text could not be easily tailored. Those regulations were addressed in separate issue papers. Exploiting established regulations avoids the difficult task of generating and interpreting novel requirements, through the use of acceptable, standardized language. The rationale for the disposition of the regulations was assessed and captured (pp. 58-115). The core basis was then augmented by generating additional requirements (pp. 38-47) to mitigate hazards for an unmanned sprayer that are not covered in Part 27.

Hayhurst, Kelly J.↗

Steady-State Vacuum Ultraviolet Exposure Facility With Automated Lamp Calibration and Sample Positioning Fabricated

The Next Generation Space Telescope (NGST) will be placed in an orbit that will subject it to constant solar radiation during its planned 10-year mission. A sunshield will be necessary to passively cool the telescope, protecting it from the Sun s energy and assuring proper operating temperatures for the telescope s instruments. This sunshield will be composed of metalized polymer multilayer insulation with an outer polymer membrane (12 to 25 mm in thickness) that will be metalized on the back to assure maximum reflectance of sunlight. The sunshield must maintain mechanical integrity and optical properties for the full 10 years. This durability requirement is most challenging for the outermost, constantly solar-facing polymer membrane of the sunshield. One of the potential threats to the membrane material s durability is from vacuum ultraviolet (VUV) radiation in wavelengths below 200 nm. Such radiation can be absorbed in the bulk of these thin polymer membrane materials and degrade the polymer s optical and mechanical properties. So that a suitable membrane material can be selected that demonstrates durability to solar VUV radiation, ground-based testing of candidate materials must be conducted to simulate the total 10- year VUV exposure expected during the Next Generation Space Telescope mission. The Steady State Vacuum Ultraviolet exposure facility was designed and fabricated at the NASA Glenn Research Center at Lewis Field to provide unattended 24-hr exposure of candidate materials to VUV radiation of 3 to 5 times the Sun s intensity in the wavelength range of 115 to 200 nm. The facility s chamber, which maintains a pressure of approximately 5 10(exp -6) torr, is divided into three individual exposure cells, each with a separate VUV source and sample-positioning mechanism. The three test cells are separated by a water-cooled copper shield plate assembly to minimize thermal effects from adjacent test cells. Part of the interior sample positioning mechanism of one test cell is shown in the illustration. Of primary concern in VUV exposure is the maintenance of constant measured radiation intensity so that the sample s total exposure can be determined in equivalent Sun hours. This is complicated by the fact that a VUV lamp s intensity degrades over time, necessitating a decrease in the distance between the test samples and the lamp. The facility overcomes this challenge by periodically measuring the lamp s intensity with a cesium-iodide phototube and adjusting the sample distance as required to maintain constant exposure intensity. Sample positioning and periodic phototube location under the lamp are both achieved by a single lead-screw assembly. The lamps can be isolated from the main vacuum chamber for cleaning or replacement so that samples are not exposed to the atmosphere during a test.

Sechkar, Edward A.↗

Separation of Lift-Generated Vortex Wakes Into Two Diverging Parts

As part of an ongoing study of the spreading rate of lift-generated vortex wakes, the present investigation considers possible reasons as to why segments of lift-generated wakes sometimes depart from the main part of the wake to move rapidly in either an upward or downward direction. It is assumed that deficiencies or enhancements of the lift carry over across the fuselage-shrouded wing are the driving mechanism for departures of wake-segments. The computations presented first indicate that upwardly departing wake segments that were observed and photographed could have been produced by a deficiency in lift carryover across the fuselage-shrouded part of the wing. Computations made of idealized vortex wakes indicate that upward departure of a wake segment requires a centerline reduction in the span loading of 70% or more, whether the engines are at idle or robust thrust. Similarly, it was found that downward departure of wake segments is produced when the lift over the center part of the wing is enhanced. However, it was also found that downward departures do not occur without the presence of robust engine-exhaust streams (i.e., engines must NOT be at idle). In those cases, downward departures of a wake segment occurs when the centerline value of the loading is enhanced by any amount between about 10% to 100%. Observations of condensation trails indicate that downward departure of wake segments is rare. Upward departures of wake segments appears to be more common but still rare. A study to determine the part of the aircraft that causes wake departures has not been carried out. However, even though departures of wake segments rarely occur, some aircraft do regularly shed these wake structures. If aircraft safety is to be assured to a high degree of reliability, and a solution for eliminating them is not implemented, existing guidelines for the avoidance of vortex wakes [1,3] may need to be broadened to include possible increases in wake sizes caused by vertical departures of wake segments. Further study may indicate that it is not possible to modify existing aircraft enough to prevent wake departures. Wake-avoidance guidelines must then be adjusted to provide the desired degree of safety. It appears that steps to avoid upwardly moving wake segments have already been incorporated into the avoidance procedures used for aircraft on approach to runways at the Frankfurt Airport [6,7]. The uncertainty in the prospects for compromises in flight safety caused by rapidly upwardly or downwardly moving wake segments suggest that it be specified that aircraft do not fly above or below each other during operations in the airport vicinity where aircraft are likely to be closely spaced [20].

Rossow, Vernon J.↗

Exploration of the Trade Space Between Unmanned Aircraft Systems Descent Maneuver Performance and Sense-and-Avoid System Performance Requirements

A need exists to safely integrate Unmanned Aircraft Systems (UAS) into the United States' National Airspace System. Replacing manned aircraft's see-and-avoid capability in the absence of an onboard pilot is one of the key challenges associated with safe integration. Sense-and-avoid (SAA) systems will have to achieve yet-to-be-determined required separation distances for a wide range of encounters. They will also need to account for the maneuver performance of the UAS they are paired with. The work described in this paper is aimed at developing an understanding of the trade space between UAS maneuver performance and SAA system performance requirements, focusing on a descent avoidance maneuver. An assessment of current manned and unmanned aircraft performance was used to establish potential UAS performance test matrix bounds. Then, near-term UAS integration work was used to narrow down the scope. A simulator was developed with sufficient fidelity to assess SAA system performance requirements. The simulator generates closest-point-of-approach (CPA) data from the wide range of UAS performance models maneuvering against a single intruder with various encounter geometries. Initial attempts to model the results made it clear that developing maneuver performance groups is required. Discussion of the performance groups developed and how to know in which group an aircraft belongs for a given flight condition and encounter is included. The groups are airplane, flight condition, and encounter specific, rather than airplane-only specific. Results and methodology for developing UAS maneuver performance requirements are presented for a descent avoidance maneuver. Results for the descent maneuver indicate that a minimum specific excess power magnitude can assure a minimum CPA for a given time-to-go prediction. However, smaller amounts of specific excess power may achieve or exceed the same CPA if the UAS has sufficient speed to trade for altitude. The results of this study will support UAS maneuver performance requirements development for integrating UAS in the NAS. The methods described are being used to help RTCA Special Committee 228 develop requirements.

Jack, Devin P.↗

Employee Assistance Program Issues

Employee Assistance Program (EAP) officers, as well as personnel in other disciplines from eight NASA Centers, attended this breakout session. Ms. Brenda Blair, MA, CEAP, a guest speaker at the conference, also attended as a consultant. Representatives from the NASA Centers introduced themselves and spoke briefly about their programs. In a discussion related to the conference theme on benchmarking, quality control issues within the EAP community and adequate documentation of cases were addressed. Disposition and provision for quality assurance checks for EAP providers in single person offices were also discussed. Ms. Blair presented methods for consulting with other NASA personnel in single person EAP offices as a quality control measure. EAP intervention in critical incidents was discussed. The question of whether EAP assistance is an asset or a potential liability in those situations was addressed. Suggestions were made of topics for future EAP video-teleconference topics. A program on EAP ethics was planned for a September video teleconference. Each person was asked to provide intake forms they use to Mr. Gettleman or Ms. Blair. Ms. Blair said she would review the forms to ensure that adequate notification is provided to the client for confidentiality. She would also review them to ensure they have adequate limits of confidentiality--a topic for future video teleconferencing. Mr. Gettleman described the NASA initiative to reduce stresses in the workplace, and the activities of an ad-hoc EAP group that will make recommendations to NASA senior management. Alternative training methods were discussed for reaching target audiences such as employees at risk, supervisors, and others. Pfc. David A. Pendleton, Victim Assistance Coordinator, U.S. Capitol Police. U.S. House of Representatives made a special presentation. Pfc. Pendleton was on duty during the tragic shooting of two Federal guards at the U.S. Capitol. He related the events immediately after the incident. He described the nature and structure of the EAP's and the separate nature of the House and Senate programs. This episode was a particularly difficult situation as large numbers of tourists were involved. William S. Barry, MD, the new Manager of the NASA Occupational Health Program Office was introduced to those attending the breakout session.

Gettleman, Alan G.↗

Analysis of Launch Vehicle Liftoff Debris: Historical Perspective from Space Shuttle and Application to Artemis I

Human exploration-class launch vehicles are inherently prone to debris due to the extreme environments generated during pre-launch operations, liftoff, and flight. The use of cryogenic propellants often requires thermal protection system (TPS) coatings, typically foam, to maintain the propellant conditions in the tank and prevent an accumulation ice on the external surface of the vehicle. Some ice growth is to be expected at umbilical interfaces, vents, flanges, or brackets where it is difficult to apply TPS. This ice may come loose at any time due to wind on the launch pad, structural vibration and acoustics after rocket ignition, or aerodynamic forces during flight. This phenomena is especially apparent on vehicles with no TPS, such as the Saturn V rockets used in the Apollo Program, see Figure 1. During propellant tanking, the thermal contraction of the underlying substrate may generate cracks in the TPS (Figure 1). Chunks of TPS can release due to the expansion of ingested gas from cryopumping or from aerodynamic forces if the crack creates an offset surface. Most foams will also have a certain amount of “popcorning” where small pieces of foam will pop off during flight because of the differential between the static surface pressure and the pressure of the gas trapped in the foam cell structure. There are a number of other coating or closeout materials that may be shed from the vehicle and become debris. During pre-launch operations and liftoff, the vehicle may also be exposed to debris originating from the launch pad or ground support equipment. This debris is separate from foreign object debris, or FOD, which is not intended to be present and is strictly controlled through operations and maintenance procedures. In this case, debris is generated from hardware and materials that are necessary for launch and are subject to the intense vibration, acoustics, and direct plume impingement of the launch environment. Examples include ice from umbilicals, tape and tie wraps that protect cables, and rust or corrosion from the launch platform. While NASA has historically been aware of debris as a potential issue that could cause a failure resulting in loss of mission, loss of vehicle, or loss of crew, the likelihood and severity of that risk was not always well understood or given sufficient weight in program and flight decisions. After the Space Shuttle Columbia accident (STS-107), the investigation found that foam TPS debris shed from the external tank was the proximate cause of the damage to the orbiter wing. Six previous observations of debris released from the foam ramp that covered the bipod connecting the forward end of the orbiter to the external tank resulted in minor changes or were determined to be accepted flight risks. Two occurrences of bipod ramp foam loss were not identified until the STS-107 investigation. Despite the damage inflicted by these debris strikes, the Shuttle Program Requirements Control Board deemed the vehicle safe to fly. During the Return to Flight effort following the Columbia disaster, NASA Engineering developed a process for the assessment of debris transport, impact, and damage tolerance to support independent assessments of risk by NASA Safety and Mission Assurance (S&MA). Under this system, each element (vehicle or ground system) defines a catalog of all expected debris based on launch history, component testing, or analysis. Debris transport analysis (DTA) is conducted using the debris catalog characteristics and potential flow transport mechanisms (e.g., vehicle aerodynamics, gravity, wind, plume-driven). The predicted debris impact locations and velocities are provided to the hardware owners, who use available test data and analysis to determine whether each component can withstand the impacts. In cases where the element hardware may be severely damaged or fail, the options are to mitigate the debris source through some change in design or operation, or to work with S&MA to try to characterize the probability of the impact and damage for program risk acceptance. Because of the differences in debris characteristics and transport, the DTA has been divided between the Liftoff and Ascent regimes. The development and application of Liftoff DTA methodology from the Shuttle Program to the current Artemis Program is the subject of this paper. Liftoff DTA covers the time from the start of pre-launch operations at the launch pad, up until the vehicle clears the launch tower and there is no longer any interaction with ground systems. Debris transport during this period is broadly classified as either gravity, wind, and plume-entrained (GWPE) or plume driven (PD). GWPE debris is generally lower speed, travelling in a forward-to-aft direction. PD transport includes flow features from the rocket ignition transient, as well as plume impingement and recirculation that occur as the vehicle lifts off the launch platform. In these cases, the debris typically moves in an aft-to-forward direction at higher speeds. The applicable transport mechanisms must be considered for each piece of debris depending on the material, and release location and time. For example, rust or metallic debris from the tower could fall (GWPE) and impact the vehicle before landing on the launch platform deck where it could be also be transported by plume impingement (PD). However, falling ice (GWPE) from an umbilical is unlikely to survive impact with the vehicle or launch platform and be available for PD transport. Modeling of debris transport is accomplished using a set of DTA tools which simulate debris trajectories subject to a reference frame acceleration (i.e., gravity) and aerodynamic drag. Where the trajectory encounters a solid surface, the debris is allowed to rebound with a specified coefficient of restitution. The drag is calculated by interpolating the fluid state at each point in the debris trajectory from high-fidelity computational fluid dynamics (CFD) simulations of the launch vehicle and pad. The CFD data may either be static (steady state or time averaged), typically for GWPE transport, or dynamic (time-accurate) for PD flow features like the ignition transient. Examples of the CFD flow field solutions for the Space Launch System (SLS) rocket and launch pad are shown in Figure 2. Typical SLS debris trajectory predictions from DTA are illustrated in Figure 3. The final version of this paper will include a more detailed examination of the Liftoff DTA process developed during the Shuttle Program, and how it has been augmented and applied to the SLS rocket under the Artemis Program. Comparisons with debris observations from the Artemis I launch will demonstrate validation of the tools and methodology.

Debris↗

Genesis Solar Wind – Capture, Return, Curate and Analyze: Looking Backward and Creating a Timeline

Introduction: In 1997 NASA’S Discovery Program selected the Genesis mission proposal to return solar wind samples to Earth for laboratory analyses. Principal Investigator Donald S. Burnett and the science team defined the purity of collector materials and ability to analyze solar wind composition to the precision required for planetary science. As a small mission, focused on a well-defined science goal, yet needing careful attention to engineering details, the communication among scientists and engineers, nurtured by Don Burnett, was exceptional. Genesis Mission and Curation Legacy: Genesis, as the first U. S. spacecraft to return astromaterial samples since Apollo, not only integrated the mission planning and flight teams, but also the science and sample curation teams during the mission development period. Since Genesis is a sample return mission, the Science Team was essential in certifying the collectors (sample containers for solar atoms). From inception, Genesis established mission funding for returned sample curation. JSC was lead in contamination control during mission preparation, including establishment of an ISO 4 cleanroom facility and use of ultrapure water (UPW) for cleaning flight hardware (and, as it turned out, for cleaning collectors after the mishap). Reliable, fast communication among scientists, engineers and curators at the hands-on level established deep respect among team members and efficient decision-making. JSC’s 50-years of astromaterial sample curation provided experienced sample processors onsite during recovery in Utah (a deep bench for emergency response). Post-recovery curation included iterative collaboration with science sample users to clean or verify cleanliness of samples. The science legacy from Genesis is addressed by Burnett and Jurewicz, this volume. In The Beginning: After Apollo sample return, Burnett and Marcia Neugebauer at JPL began discussing a solar wind sample return, with Neugebauer arguing that separate collection of solar wind regimes was essential science. By 1992 a solar wind sample return mission was presented at a workshop, and by 1994 a mission was proposed named Suess-Urey. The mission was re-proposed under a new name GENESIS and selected in 1997. Susan Niebur captured the Genesis mission history and stories, from high level management documents and from many interviews with participants [2]. Her account lets readers glimpse personality of participants in quotations from interviews. Need and Scope for Detailed Technical Timeline: A timeline constructed from lower level task documents has been initiated to document the resources and skills actually used, as well as task sequence or concurrency. Timelines for high level mission events are captured in two documents [1] [2] and for detailed re-entry events in [3]. A detailed technical timeline for Genesis mission and curation activities will provide data points for lower level tasks, such as ISO 4 curation facility construction time, preparation for nominal sample field recovery, mishap recovery, and UPW expansion. Changes in technology context 1990-2024: Semiconductor technologies were easily accessible in the U.S.A. (1990-1999), and the Genesis team used those resources for cleanroom design and UPW system expansion. Image documentation was changing from film to digital during cleanroom construction and payload cleaning (1997-2001). Engineering design was done using computer aided design proprietary software, making more difficult the archiving of payload configuration and materials. Email of documents, tracked delivery service and virtual meeting capability greatly improved communication efficiency. Information sources – Pre-launch mission preparation: Examples of mission science, engineering and contamination control are collector purity testing, payload design/fabrication and ISO 4 cleanroom construction. Information on timing of these activities comes from facility readiness reviews, management reviews, shipping documents, procurement documents, test reports, travel documents, laboratory logs, Quality Assurance documents, dates on images, participant notebooks and emails. Information sources – Sample return re-entry and field recovery activities: Information comes from event timelines produced by Mid-Air Recovery team, Lockheed team lead notes and from chase video, JPL Quality Assurance. Information also comes from images and logbooks from UTTR cleanroom operations and from curatorial documents. Information sources – Resulting science and sample cleaning processes: Agendas from the annual gatherings of the science team initially trace testing for collector purity/cleanliness, and after sample recovery, include collector cleaning and cleanliness assessment. Post-recovery documents include curatorial orders and procedures, sample allocation documents and LPSC abstracts. Timeline Objectives: A simple spreadsheet timeline with headers DATE, EVENT, PEOPLE, COMMENT, INFORMATION SOURCE has been initiated and currently has over 90 entries. While this is not definitive historical research, it is a quick look at the evolution of Genesis curation with pointers to documents or people with information. Engineers for future missions may find useful points of comparison for development of facilities. References:[1] Genesis Mission Reference Document, (2011) JPL D-62382.[2] Niebur S. M., edited by Brown D. W. (2023) NASA’s Discovery Program: The First 20 Years of Competitive Planetary Exploration, NASA-SP-2023-4238.[3] Genesis Mishap Investigation Board Report, Vol. 1 (July 2005).

solar wind↗

Stardust Navigation Covariance Analysis

The Stardust spacecraft was launched on February 7, 1999 aboard a Boeing Delta-II rocket. Mission participants include the National Aeronautics and Space Administration (NASA), the Jet Propulsion Laboratory (JPL), Lockheed Martin Astronautics (LMA) and the University of Washington. The primary objective of the mission is to collect in-situ samples of the coma of comet Wild-2 and return those samples to the Earth for analysis. Mission design and operational navigation for Stardust is performed by the Jet Propulsion Laboratory (JPL). This paper will describe the extensive JPL effort in support of the Stardust pre-launch analysis of the orbit determination component of the mission covariance study. A description of the mission and it's trajectory will be provided first, followed by a discussion of the covariance procedure and models. Predicted accuracy's will be examined as they relate to navigation delivery requirements for specific critical events during the mission. Stardust was launched into a heliocentric trajectory in early 1999. It will perform an Earth Gravity Assist (EGA) on January 15, 2001 to acquire an orbit for the eventual rendezvous with comet Wild-2. The spacecraft will fly through the coma (atmosphere) on the dayside of Wild-2 on January 2, 2004. At that time samples will be obtained using an aerogel collector. After the comet encounter Stardust will return to Earth when the Sample Return Capsule (SRC) will separate and land at the Utah Test Site (UTTR) on January 15, 2006. The spacecraft will however be deflected off into a heliocentric orbit. The mission is divided into three phases for the covariance analysis. They are 1) Launch to EGA, 2) EGA to Wild-2 encounter and 3) Wild-2 encounter to Earth reentry. Orbit determination assumptions for each phase are provided. These include estimated and consider parameters and their associated a-priori uncertainties. Major perturbations to the trajectory include 19 deterministic and statistical maneuvers planned for the mission. The spacecraft is three axis stabilized and has unbalanced thrusters for attitude control. Accelerations due to the attitude control system are treated stochastically. The tracking scenario for the study is patterned after the actual schedule employed during the different phases of the mission. Conventional X-band two-way Doppler and SRA range data was simulated and the standard accuracy for these data types was assumed throughout most of the mission. However, a deweighting scheme was used for the Doppler data during times of low Sun-Earth-Probe angles, especially in the case of the DSM. Optical data is assumed to be available starting at 50 days prior to the comet encounter. The optical data will be used to improve the ephemeris of Wild-2, which is considered crucial to properly target the comet flyby. Results of the covariance analysis are presented for all mission phases. Navigation capability will be discussed in terms of the uncertainty in the encounter B-Plane (B.R and B.T) and linearized time of flight. Delivery errors based on the final maneuver prior to the comet encounter will be presented. The most stringent navigation requirement is for the Earth reentry. The uncertainty in the flight path angle must be less than 0.02 degree (orbit determination and maneuver performance) to assure successful recovery of the SRC. Results presented show that this requirement can be met.

Menon, Premkumar R.↗

Altitude Testing of Large Liquid Propellant Engines

The National Aeronautics and Space Administration entered a new age on January 14, 2004 with President Bush s announcement of the creation the Vision for Space Exploration that will take mankind back to the Moon and on beyond to Mars. In January, 2006, after two years of hard, dedicated labor, engineers within NASA and its contractor workforce decided that the J2X rocket, based on the heritage of the Apollo J2 engine, would be the new engine for the NASA Constellation Ares upper stage vehicle. This engine and vehicle combination would provide assured access to the International Space Station to replace that role played by the Space Shuttle and additionally, would serve as the Earth Departure Stage, to push the Crew Excursion Vehicle out of Earth Orbit and head it on a path for rendezvous with the Moon. Test as you fly, fly as you test was chosen to be the guiding philosophy and a pre-requisite for the engine design, development, test and evaluation program. An exhaustive survey of national test facility assets proved the required capability to test the J2X engine at high altitude for long durations did not exist so therefore, a high altitude/near space environment testing capability would have to be developed. After several agency concepts the A3 High Altitude Testing Facility proposal was selected by the J2X engine program on March 2, 2007 and later confirmed by a broad panel of NASA senior leadership in May 2007. This facility is to be built at NASA s John C. Stennis Space Center located near Gulfport, Mississippi. 30 plus years of Space Shuttle Main Engine development and flight certification testing makes Stennis uniquely suited to support the Vision For Space Exploration Return to the Moon. Propellant handling infrastructure, engine assembly facilities, a trained and dedicated workforce and a broad and varied technical support base will all ensure that the A3 facility will be built on time to support the schedule needs of the J2X engine and the ultimate flight of the first Ares I vehicle. The A3 facility will be able to simulate pre-ignition altitude from sea-level to 100,000 feet and maintain it up to 650 seconds. Additionally the facility will be able to accommodate initial ignition, shutdown and then restart test profiles. A3 will produce up to 5000 lbm/sec of superheated steam utilizing a Chemical Steam generation system. Two separate inline steam ejectors will be used to produce a test cell vacuum to simulate the 100,000 ft required altitude. Operational capability will ensure that the facility can start up and shutdown without producing adverse pressure gradients across the J2X nozzle. The facility will have a modern thrust measurement system for accurate determination of engine performance. The latest advances in data acquisition and control will be incorporated to measure performance parameters during hotfire testing. Provisions are being made in the initial design of the new altitude facility to allow for testing of other, larger engines and potential upper stage launch vehicles that might require vacuum start testing of the engines. The new facility at Stennis Space Center will be complete and ready for hotfire operations in late 2010.

Maynard, Bryon T.↗