SEARCH · Engineering Papers
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.
The Structures Flight from 412 Test Wing and the Aerostructures Branch at NASA Armstrong Flight Research Center at Edwards Air Force Base have developed a set of best practices for training a structures flight test engineer. These practices represent the hard-won lessons learned and best practices from training generations of engineers to perform high risk envelope expansion and developmental flight test.
This presentation describes aerostructures lessons learned and best practices developed over the years at AFRC.
This paper proposes the formation of an international panel of space related public/private partnerships for the purposes of sharing best practices among members. The exploration and development of space is too costly to be conducted by governments alone. Private industry has a significant role in creating needed technologies, and developing commercial space infrastructure, thereby allowing sustainable exploration to take place. Public/private partnerships between government and industry are key to fostering industrial participation in space. The spacefaring nations have, or are developing these partnerships. Those organizations forming these partnerships can benefit from sharing among each other best practices and lessons learned. In this way the common goal of space exploration and development can be more effectively pursued.
This presentation describes aerodynamics and performance X-plane airworthiness guidelines and best practices.
During the development of the CMR (Common Metadata Repository) (CMR) for the Earth Observing System Data and Information System (EOSDIS), CSW (Catalog Service for the Web) a number of best practices came to light. Given that the ESIP (Earth Science Information Partners) Discovery Cluster is committed to interoperability and standards in earth data discovery this seemed like a convenient moment to provide Best Practices to the organization in the same way we did for OpenSearch for this widely-used standard.
The NASA Engineering and Safety Center (NESC) recently completed an in-depth assessment to identify a comprehensive set of engineering considerations for the Design, Development, Test and Evaluation (DDT&E) of safe and reliable human-rated spacecraft systems. Reliability subject matter experts, discipline experts, and systems engineering experts were brought together to synthesize the current "best practices" both at the spacecraft system and subsystems levels. The objective of this paper is to summarize, for the larger Community of Practice, the initial set of Guidance, Navigation and Control (GN&C) engineering Best Practices as identified by this NESC assessment process.
The NASA Engineering and Safety Center (NESC) recently completed an in-depth assessment to identify a comprehensive set of engineering considerations for the Design, Development, Test and Evaluation (DDT&E) of safe and reliable human-rated spacecraft systems. Reliability subject matter experts, discipline experts, and systems engineering experts were brought together to synthesize the current "best practices" both at the spacecraft system and subsystems levels. The objective of this paper is to summarize, for the larger Community of Practice, the initial set of Guidance, Navigation and Control (GN&C) engineering Best Practices as identified by this NESC assessment process.
The NASA Engineering and Safety Center (NESC) recently completed an in-depth assessment to identify a comprehensive set of engineering considerations for the Design, Development, Test and Evaluation (DDT&E) of safe and reliable human-rated spacecraft systems. Reliability subject matter experts, discipline experts, and systems engineering experts were brought together to synthesize the current "best practices" both at the spacecraft system and subsystems levels. The objective of this paper is to summarize, for the larger Community of Practice, the initial set of Guidance, Navigation and Control (GN&C) engineering Best Practices as identified by this NESC assessment process.
Aviation safety can be greatly enhanced by the expeditious use of computer simulations of crash impact. Unlike automotive impact testing, which is now routine, experimental crash tests of even small aircraft are expensive and complex due to the high cost of the aircraft and the myriad of crash impact conditions that must be considered. Ultimately, the goal is to utilize full-scale crash simulations of aircraft for design evaluation and certification. The objective of this publication is to describe "best practices" for modeling aircraft impact using explicit nonlinear dynamic finite element codes such as LS-DYNA, DYNA3D, and MSC.Dytran. Although "best practices" is somewhat relative, it is hoped that the authors' experience will help others to avoid some of the common pitfalls in modeling that are not documented in one single publication. In addition, a discussion of experimental data analysis, digital filtering, and test-analysis correlation is provided. Finally, some examples of aircraft crash simulations are described in several appendices following the main report.
The X-57 Maxwell is NASA’s latest electric airplane concept that has been simulated for aerodynamic performance using the structured overset and unstructured grid solvers within the Launch Ascent and Vehicle Aerodynamics (LAVA) solver framework as well as the unstructured polyhedral grid solver in Star-CCM+ for code-to-code comparison. In order to validate the predictions, comparisons were made between the CFD solutions and experimental data collected in the 12-foot Low-Speed Wind Tunnel at NASA Langley Research Center. The simulations are in preparation for the development of a comprehensive aerodynamic database which will assess aircraft performance at a variety of conditions. The findings from these simulations will establish the best practices for mesh resolution, numerical discretization, and turbulence modeling to be used for this database. Preliminary database results have shown that best-practices learned from the initial validation simulations will potentially reduce error in X-57 aerodynamic loads and moments relative to experiment by up to 14%.
To facilitate the development of the Urban Air Mobility (UAM) market, the NASA Revolutionary Vertical Lift Technology Project has created the Conceptual Design Toolchain, a suite of tools developed and/or selected to assist rotorcraft designers in all stages of rotorcraft design. Of particular interest to the UAM noise community are the following two steps in this toolchain: comprehensive analysis and acoustic prediction. Since the UAM application is relatively new, there is a need for a systematic study on how best to utilize these codes. To this end, the current study documents best practices for using the comprehensive analysis codes, CAMRAD II and CHARM, along with the acoustic code AARON. Two single rotors are considered: i) a simple rotor and ii) a rotor that is more exemplary of what UAM designers might use. Best practices are presented for the prediction of both tonal and broadband self-noise, along with the corresponding results. The goal is to provide conceptual designers the tools to conduct accurate noise prediction using the RVLT Conceptual Design Toolchain.
This presentation discusses Best Practices for Power Quality and Integrated Testing at JSC in regards to electrical systems. These high-level charts include mostly generic information; however, a specific issue is discussed involving flight hardware that could have been discovered prior to flight with an integrated test.
Identification, resolution, and avoidance of technical and programmatic issues are important for ensuring safe and successful space missions. Although the importance of applying lessons learned to reduce risk is frequently stressed, there is little material available to help technical and management personnel research and document lessons learned. Collecting, researching, identifying, and documenting lessons learned that will be useful to current and future management and engineering personnel is not always a straightforward task. This white paper presents lessons learned and best practices concerning the research and documentation of technical and organizational lessons learned. It is intended to enable organizations to initiate or improve lessons learned research and documentation efforts. The content of this white paper is based on four technical lessons learned projects conducted by the United Space Alliance (USA) Flight Design and Dynamics Department, in support of the NASA/Johnson Space Center (JSC) Flight Design and Dynamics Division. Each project published a report, titled as follows: (1) GPS Lessons Learned From the ISS, Space Shuttle and X-38; (2) Lessons Learned From Seven Space Shuttle Missions; (3) Space Shuttle Rendezvous and Proximity Operations Experience Report; and (4) Navigation Technical History with Lessons Learned. The four projects were different in availability of subject matter experts and primary source material, subject scope, and the level of effort required to produce the final report. However, generic lessons can be drawn from all of them. The best practices will be discussed by the phases of report research and development: (1) Defining Report Requirements, Project Organization, and Schedule; (2) Collection and Analysis of Source Material; (3) Writing and Integrating the Report; and (4) Review and Revision of the Report.
Sine Burst (SB) Testing is used for strength testing of aerospace hardware as an alternate to static pull and centrifuge tests. The main advantage is that testing can be implemented while hardware is on the shaker for other tests. It also imposes a lower number of cycles on the hardware compared with a sine dwell or sweep, and is particularly suitable for relatively stiff components or electronics boxes, instruments, or spacecraft. Identified risks can be mitigated by best practices.
The NASA Ames Life Sciences Institutional Scientific Collection (ISC), which is composed of the Ames Life Sciences Data Archive (ALSDA) and the Biospecimen Storage Facility (BSF), is managed by the Space Biosciences Division and has been operational since 1993. The ALSDA is responsible for archiving information and animal biospecimens collected from life science spaceflight experiments and matching ground control experiments. Both fixed and frozen spaceflight and ground tissues are stored in the BSF within the ISC. The ALSDA also manages a Biospecimen Sharing Program, performs curation and long-term storage operations, and makes biospecimens available to the scientific community for research purposes via the Life Science Data Archive public website (https:lsda.jsc.nasa.gov). As part of our best practices, a viability testing plan has been developed for the ISC, which will assess the quality of archived samples. We expect that results from the viability testing will catalyze sample use, enable broader science community interest, and improve operational efficiency of the ISC. The current viability test plan focuses on generating disposition recommendations and is based on using ribonucleic acid (RNA) integrity number (RIN) scores as a criteria for measurement of biospecimen viablity for downstream functional analysis. The plan includes (1) sorting and identification of candidate samples, (2) conducting a statiscally-based power analysis to generate representaive cohorts from the population of stored biospecimens, (3) completion of RIN analysis on select samples, and (4) development of disposition recommendations based on the RIN scores. Results of this work will also support NASA open science initiatives and guides development of the NASA Scientific Collections Directive (a policy on best practices for curation of biological collections). Our RIN-based methodology for characterizing the quality of tissues stored in the ISC since the 1980s also creates unique scientific opportunities for temporal assessment across historical missions. Support from the NASA Space Biology Program and the NASA Human Research Program is gratefully acknowledged.
Sine Vibration (SV) Testing involves subjecting the test article to a swept sine input over a frequency range (typically 5-100 Hz) to replicate the low-frequency launch environment. This test method is used for various purposes on a structural model but mainly on flight articles. The SV levels are derived from measured flight data or based on interface acceleration levels from coupled loads analysis (CLA). A logarithmic sweep rate is typically used to excite a constant time interval per bandwidth for the test (e.g., 2 or 4 octave/min), which is intended to simulate sustained sine and transient events that occur during launch. Risks can be mitigated through best practices.
On April 15, 2010 President Barak Obama made the official announcement that the Constellation Program, which included the Ares I launch vehicle, would be canceled. NASA s Ares I launch vehicle was being designed to launch the Orion Crew Exploration Vehicle, returning humans to the moon, Mars, and beyond. It consisted of a First Stage (FS) five segment solid rocket booster and a liquid J-2X Upper Stage (US) engine. Roll control for the FS was planned to be handled by a dedicated Roll Control System (RoCS), located on the connecting interstage. Induced yaw or pitch moments experienced during FS ascent would have been handled by vectoring of the booster nozzle. After FS booster separation, the US Reaction Control System (ReCS) would have provided the US Element with three degrees of freedom control as needed. The best practices documented in this paper will be focused on the technical designs and producibility of both systems along with the partnership between NASA and Boeing, who was on contract to build the Ares I US Element, which included the FS RoCS and US ReCS. In regards to partnership, focus will be placed on integration along with technical work accomplished by Boeing. This will include detailed emphasis on task orders developed between NASA and Boeing that were used to direct specific work that needed to be accomplished. In summary, this paper attempts to capture key best practices that should be helpful in the development of future launch vehicle and spacecraft RCS designs.
Formal international standards as well as promotion of community or recommended practices have their place in ensuring "FAIRness" of data. Data management in NASA's Earth Observation System Data and Information System (EOSDIS) has benefited from both of these avenues to a significant extent. The purpose of this paper is to present one example of each of these, which promote (re)usability. The first is an ISO standard for specifying preservation content from Earth observation missions. The work on this started in 2011, informally within the Earth Science Information Partners (ESIP) in the US, while the European Space Agency (ESA) was leading an effort on Long-Term Data Preservation (LTDP). Resulting from the ESIP discussions was NASA's Preservation Content Specification, which was applied in 2012 as a requirement for NASA's new missions. ESA's Preserved Data Set Content (PDSC) document was codified into a document adopted by the Committee on Earth Observation Satellites (CEOS). It was recognized that it would be useful to combine PCS and PDSC into an ISO standard to ensure consistency in data preservation on a broader international scale. This standard, numbered ISO 19165-2 has been under development since mid-2017. The second is an example of developing recommendations for "best practices" within more limited (still fairly broad) communities. A Data Product Developers' Guide (DPDG) is currently being developed by one of NASA's Earth Science Data System Working Groups (ESDSWGs). It is for use by developers of products to be derived from Earth observation data to improve product (re)usability. One of the challenges in developing the guide is the fact that there are already many applicable standards and guides. The relevant information needs to be selected and expressed in a succinct manner, with appropriate pointers to references. The DPDG aims to compile the most applicable parts of earlier guides into a single document outlining the typical development process for Earth Science data products. Standards and best practices formally endorsed by the Earth Science Data and Information System (ESDIS) Standards Office (ESO), outputs from ESDSWGs (e.g., Dataset Interoperability Working Group, and Data Quality Working Group), and recommendations from Distributed Active Archive Centers and data producers are emphasized.