Search NASA⌕ Search

SEARCH · Search NASA

Results for “appendix”

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 1,297 records · Page 72

Columbia Accident Investigation Board

The CAIB requested these data be included in this Appendix. This Appendix is a summary of present and past efforts that were initiated to characterize the moisture absorption capability of sprayed-on-foam-insulation (SOFI) and specifically, BX-250.

White, Donald J.↗

[New Retrieval Algorithms for Geophysical Products from GLI and MODIS Data]

Below is the 1st year progress report for NAG5-13435 "New Retrieval Algorithms for Geophysical Products from GLI and MODIS Data". Activity on this project has been coordinated with our NASA DB project NAG5-9604. For your convenience, this report has six sections and an Appendix. Sections I - III discuss specific activities undertaken during the past year to analyze/use MODIS data. Section IV formally states our intention to no longer pursue any research using JAXA's (formerly NASDA's) GLI instrument which catastrophically failed very early after launch (also see the Appendix). Section V provides some indications of directions for second year activities based on our January 2004 telephone discussions and email exchanges. A brief summary is given in Section VI.

Dodge, James C.↗

Photon Sail History, Engineering, and Mission Analysis

This Appendix summarizes the results of a Teledyne Brown Engineering, Inc. report to the In-Space propulsion research group of the NASA Marshall Space Flight Center (MSFC) that was authored by Taylor et al. in 2003. The subject of this report is the technological maturity, readiness, and capability of the photon solar sail to support space-exploration missions. Technological maturity for solar photon sail concepts is extremely high high for rectangular (or square) solar sail configurations due to the historical development of the rectangular design by the NASA Jet Propulsion Laboratory (JPL). L'Garde Inc., ILC Dover Inc., DLR, and many other corporations and agencies. However, future missions and mission analysis may prove that the rectangular sail design is not the best architecture for achieving mission goals. Due to the historical focus on rectangular solar sail spacecraft designs, the maturity of other architectures such as hoop-supported disks, multiple small disk arrays, parachute sails, heliogyro sails, perforated sails, multiple vane sails (such as the Planetary Society's Cosmos 1), inflated pillow sails, etc., have not reached a high level of technological readiness. (Some sail architectures are shown in Fig. A.1.) The possibilities of different sail architectures and some possible mission concepts are discussed in this Appendix.

Matloff, Gregory L.↗

Additional Results of Ice-Accretion Scaling at SLD Conditions

To determine scale velocity an additional similarity parameter is needed to supplement the Ruff scaling method. A Weber number based on water droplet MVD has been included in several studies because the effect of droplet splashing on ice accretion was believed to be important, particularly for SLD conditions. In the present study, ice shapes recorded at Appendix-C conditions and recent results at SLD conditions are reviewed to show that droplet diameter cannot be important to main ice shape, and for low airspeeds splashing does not appear to affect SLD ice shapes. Evidence is presented to show that while a supplementary similarity parameter probably has the form of a Weber number, it must be based on a length proportional to model size rather than MVD. Scaling comparisons were made between SLD reference conditions and Appendix-C scale conditions using this Weber number. Scale-to-reference model size ratios were 1:1.7 and 1:3.4. The reference tests used a 91-cm-chord NACA 0012 model with a velocity of approximately 50 m/s and an MVD of 160 m. Freezing fractions of 0.3, 0.4, and 0.5 were included in the study.

Bond, Thomas H.↗

Initial Experimental Airworthiness Certification Guidance for UAS. UAS Experimental Certification Process and Guidance

This paper addresses the regulatory processes and requirements already in place by which an applicant might obtain experimental airworthiness certification for a civil Unmanned Aircraft System (UAS). It is more extensive and subsequent to an earlier, similar deliverable, PD007, which was an interim study of the same topic. Since few regulatory airworthiness and operating standards exist for UAS like those for traditional manned aircraft and since most UAS have historically been developed and operated under military auspices, civil use of UAS in the NAS is a new and unfamiliar challenge requiring specific and unique considerations. Experimental certification is the most basic level of FAA approval toward routine UAS operation in the NAS. The paper reviews and explains existing FAA requirements for an applicant seeking experimental airworthiness approval and details the process for submission of necessary information. It summarizes the limited purposes for which experimental aircraft may be used and addresses pertinent aspects of UAS design, construction and operation in the NAS in harmony with traditional manned aircraft. Policy IPT position is that UAS, while different from manned aircraft, can use the same initial processes to gain civil operating experience under the experimental approval. Particular note is taken of those UAS-unique characteristics which require extra attention to assure equivalent safety of operation, such as the UAS control station and sense-and-avoid. The paper also provides "best practices" guidance for UAS manufacturers and FAA personnel in two appendices. The material in Appendix A is intended to provide guidance on assuring UAS safety to FAA, and provides FAA personnel with a suggested list of items to review, with a focus on UAS unique factors, prior to issuance of an experimental airworthiness certificate. Appendix B provides an outline for a program letter which a manufacturer could use in preparing the application for an UAS experimental airworthiness certificate.

Source record↗

Weather Requirements and Procedures for Step 1: High Altitude Long Endurance (HALE) Unmanned Aircraft System (UAS) Flight Operations in the National Air Space (NAS)

This cover sheet is for version 2 of the weather requirements document along with Appendix A. The purpose of the requirements document was to identify and to list the weather functional requirements needed to achieve the Access 5 vision of "operating High Altitude, Long Endurance (HALE) Unmanned Aircraft Systems (UAS) routinely, safely, and reliably in the National Airspace System (NAS) for Step 1." A discussion of the Federal Aviation Administration (FAA) references and related policies, procedures, and standards is provided as basis for the recommendations supported within this document. Additional procedures and reference documentation related to weather functional requirements is also provided for background. The functional requirements and related information are to be proposed to the FAA and various standards organizations for consideration and approval. The appendix was designed to show that sources of flight weather information are readily available to UAS pilots conducting missions in the NAS. All weather information for this presentation was obtained from the public internet.

Source record↗

An Overview of Autogyros and The McDonnell XV-1 Convertiplane

This report and its lengthy appendix first reviews early autogyro history. The period from Juan de la Cierva's invention in the early1920s through to the U. S. Army Air Corps' choice, in 1943, of the helicopter instead of the more fully developed autogyro, is examined from a technical point of view. With this historical background in hand, simple aerodynamic technology for rotors, wings, propeller, and fuselages is provided for reference. The McDonnell XV-1 convertiplane development and its program are discussed in detail, with particular emphasis on the wind tunnel and flight testing that was accomplished with two prototype aircraft in the early 1950s. The tip drive rotor system with its ingeniously designed hub was well suited to high speed rotorcraft. The configuration was conceived by Kurt Hohenemser and Fred Dubloff. Many photographs taken of the XV-1 stored at Fort Rucker are included in this report's appendix.

Harris, Franklin D.↗

Ice Shape Scaling for Aircraft in SLD Conditions

This paper has summarized recent NASA research into scaling of SLD conditions with data from both SLD and Appendix C tests. Scaling results obtained by applying existing scaling methods for size and test-condition scaling will be reviewed. Large feather growth issues, including scaling approaches, will be discussed briefly. The material included applies only to unprotected, unswept geometries. Within the limits of the conditions tested to date, the results show that the similarity parameters needed for Appendix C scaling also can be used for SLD scaling, and no additional parameters are required. These results were based on visual comparisons of reference and scale ice shapes. Nearly all of the experimental results presented have been obtained in sea-level tunnels. The currently recommended methods to scale model size, icing limit and test conditions are described.

Anderson, David N.↗

Wake Vortex Inverse Model User's Guide

NorthWest Research Associates (NWRA) has developed an inverse model for inverting landing aircraft vortex data. The data used for the inversion are the time evolution of the lateral transport position and vertical position of both the port and starboard vortices. The inverse model performs iterative forward model runs using various estimates of vortex parameters, vertical crosswind profiles, and vortex circulation as a function of wake age. Forward model predictions of lateral transport and altitude are then compared with the observed data. Differences between the data and model predictions guide the choice of vortex parameter values, crosswind profile and circulation evolution in the next iteration. Iterations are performed until a user-defined criterion is satisfied. Currently, the inverse model is set to stop when the improvement in the rms deviation between the data and model predictions is less than 1 percent for two consecutive iterations. The forward model used in this inverse model is a modified version of the Shear-APA model. A detailed description of this forward model, the inverse model, and its validation are presented in a different report (Lai, Mellman, Robins, and Delisi, 2007). This document is a User's Guide for the Wake Vortex Inverse Model. Section 2 presents an overview of the inverse model program. Execution of the inverse model is described in Section 3. When executing the inverse model, a user is requested to provide the name of an input file which contains the inverse model parameters, the various datasets, and directories needed for the inversion. A detailed description of the list of parameters in the inversion input file is presented in Section 4. A user has an option to save the inversion results of each lidar track in a mat-file (a condensed data file in Matlab format). These saved mat-files can be used for post-inversion analysis. A description of the contents of the saved files is given in Section 5. An example of an inversion input file, with preferred parameters values, is given in Appendix A. An example of the plot generated at a normal completion of the inversion is shown in Appendix B.

Lai, David↗

Rocketdyne - Lunar Ascent Engine

The ascent engine was the last one from the moon, and I want to focus on the idea of redundancy and teams in regard to the engine. By teams, I mean teamwork - not just within Rocketdyne. It was teamwork within Rocketdyne; it was teamwork within Grumman; it was teamwork within NASA. These were all important elements leading to the successful development of the lunar excursion module (LEM) engine. Communication, rapid response, and cooperation were all important. Another aspect that went into the development of the ascent engine was the integration of technology and of lessons learned. We pushed all the above, plus technology and lessons learned, into a program, and that led to a successful result. One of the things that I like to think about - again in retrospect - is how it is very "in" now to have integrated product and process teams. These are buzzwords for teamwork in all program phases. That s where you combine a lot of groups into a single organization to get a job done. The ascent engine program epitomized that kind of integration and focus, and because this was the mid- to late-1960s; this was new ground for Rocketdyne, Grumman, and NASA. Redundancy was really a major hallmark of the Apollo Program. Everything was redundant. Once you got the rocket going, you could even lose one of the big F-1 engines, and it would still make it to orbit. And once the first stage separated from the rest of the vehicle, the second stage could do without an engine and still make a mission. This redundancy was demonstrated when an early Apollo launch shut down a J-2 second-stage engine. Actually, they shut down two J-2 engines on that flight. Even the third stage, with its single J-2 engine, was backed up because the first two stages could toss it into a recoverable orbit. If the third stage didn't work, you were circling the earth, and you had time to recover the command module and crew. Remember how on the Apollo 13 flight, there was sufficient system redundancy even when we lost the service module. That was a magnificent effort. TRW Inc. really ought to be proud of their engine for that. (See Slide 2, Appendix I) We had planned for redundancy; we had landed on the moon. However, weight restrictions in the architecture said, "You can t have redundancy for ascent from the moon. You've got one engine. It s got to work. There is no second chance. If that ascent engine doesn't work, you re stuck there." It would not have looked good for NASA. It wouldn't have looked good for the country. There was a letter written that President Richard Nixon would read if the astronauts got stuck on the moon, expressing how sorry we were and so forth. It was a scary letter, really. The ascent engine was an engine that had to work. (See Slide 3, Appendix I).

Harmon, Tim↗

Design and Testing of a Prototype Lunar or Planetary Surface Landing Research Vehicle (LPSLRV)

This handbook describes a two-semester senior design course sponsored by the NASA Office of Education, the Exploration Systems Mission Directorate (ESMD), and the NASA Space Grant Consortium. The course was developed and implemented by the Mechanical and Aerospace Engineering Department (MAE) at Utah State University. The course final outcome is a packaged senior design course that can be readily incorporated into the instructional curriculum at universities across the country. The course materials adhere to the standards of the Accreditation Board for Engineering and Technology (ABET), and is constructed to be relevant to key research areas identified by ESMD. The design project challenged students to apply systems engineering concepts to define research and training requirements for a terrestrial-based lunar landing simulator. This project developed a flying prototype for a Lunar or Planetary Surface Landing Research Vehicle (LPSRV). Per NASA specifications the concept accounts for reduced lunar gravity, and allows the terminal stage of lunar descent to be flown either by remote pilot or autonomously. This free-flying platform was designed to be sufficiently-flexible to allow both sensor evaluation and pilot training. This handbook outlines the course materials, describes the systems engineering processes developed to facilitate design fabrication, integration, and testing. This handbook presents sufficient details of the final design configuration to allow an independent group to reproduce the design. The design evolution and details regarding the verification testing used to characterize the system are presented in a separate project final design report. Details of the experimental apparatus used for system characterization may be found in Appendix F, G, and I of that report. A brief summary of the ground testing and systems verification is also included in Appendix A of this report. Details of the flight tests will be documented in a separate flight test report. This flight test report serves as a complement to the course handbook presented here. This project was extremely ambitious, and achieving all of the design and test objectives was a daunting task. The schedule ran slightly longer than a single academic year with the complete design closure not occurring until early April. Integration and verification testing spilled over into late May and the first flight did not occur until mid to late June. The academic year at Utah State University ended on May 8, 2010. Following the end of the academic year, testing and integration was performed by the faculty advisor, paid research assistants, and volunteer student help

Murphy, Gloria A.↗

Consolidated Development Objectives Document (CDOD) For MB-60

This document defines the objectives related to liquid rocket engine system development to be undertaken by JAXA in support of the Space Launch System (SLS) Program managed out of the NASA Marshall Space Flight Center (MSFC). These objectives include furnishing the necessary management, labor, facilities, tools, equipment, and materials required to execute the specified activities. 1.1 Project Scope: The scope of this effort is to develop a rocket engine and associated products per the objectives and technical requirements established in this document. This engine, minus the engine controller, designated here as MB ]60, is to be developed through to a prequalification point of maturity. It is assumed that should JCNE ]1 development proceed beyond this maturity point towards actual flight qualification, the engine controller will be supplied and integrated by NASA. 1.2 Document Structure: The structure of this Consolidated Development Objectives Document (CDOD) includes a traditional description of objectives in a SOO, plus the associated Data Products Document (DPD) in an attached appendix, and then Engine Requirements Document (ERD) as another attached appendix. It is the intent that this document, in conjunction with the cited applicable documents, should constitute a complete programmatic and technical description of the development effort to be pursued.

Greene, William D.↗

NASA Glenn Icing Research Tunnel: 2014 Cloud Calibration Procedure and Results

The results of the December 2013 to February 2014 Icing Research Tunnel full icing cloud calibration are presented. The calibration steps included establishing a uniform cloud and conducting drop size and liquid water content calibrations. The goal of the calibration was to develop a uniform cloud, and to generate a transfer function from the inputs of air speed, spray bar atomizing air pressure and water pressure to the outputs of median volumetric drop diameter and liquid water content. This was done for both 14 CFR Parts 25 and 29, Appendix C ('typical' icing) and soon-to-be released Appendix O (supercooled large drop) conditions.

liquid water content↗

NASA Glenn Icing Research Tunnel: 2014 Cloud Calibration

The results of the December 2013 to February 2014 Icing Research Tunnel full icing cloud calibration are being presented to the SAE AC-9C committee, as represented in the 2014 cloud calibration report. The calibration steps included establishing a uniform cloud and conducting drop size and liquid water content calibrations. The goal of the calibration was to develop a uniform cloud, and to generate a transfer function from the inputs of air speed, spray bar atomizing air pressure and water pressure to the outputs of median volumetric drop diameter and liquid water content. This was done for both 14 CFR Parts 25 and 29, Appendix C (typical icing) and soon-to-be released Appendix O (supercooled large drop) conditions.

drop size↗

File Specification for the 7-km GEOS-5 Nature Run, Ganymed Release Non-Hydrostatic 7-km Global Mesoscale Simulation

This document describes the gridded output files produced by a two-year global, non-hydrostatic mesoscale simulation for the period 2005-2006 produced with the non-hydrostatic version of GEOS-5 Atmospheric Global Climate Model (AGCM). In addition to standard meteorological parameters (wind, temperature, moisture, surface pressure), this simulation includes 15 aerosol tracers (dust, sea-salt, sulfate, black and organic carbon), O3, CO and CO2. This model simulation is driven by prescribed sea-surface temperature and sea-ice, daily volcanic and biomass burning emissions, as well as high-resolution inventories of anthropogenic sources. A description of the GEOS-5 model configuration used for this simulation can be found in Putman et al. (2014). The simulation is performed at a horizontal resolution of 7 km using a cubed-sphere horizontal grid with 72 vertical levels, extending up to to 0.01 hPa (approximately 80 km). For user convenience, all data products are generated on two logically rectangular longitude-latitude grids: a full-resolution 0.0625 deg grid that approximately matches the native cubed-sphere resolution, and another 0.5 deg reduced-resolution grid. The majority of the full-resolution data products are instantaneous with some fields being time-averaged. The reduced-resolution datasets are mostly time-averaged, with some fields being instantaneous. Hourly data intervals are used for the reduced-resolution datasets, while 30-minute intervals are used for the full-resolution products. All full-resolution output is on the model's native 72-layer hybrid sigma-pressure vertical grid, while the reduced-resolution output is given on native vertical levels and on 48 pressure surfaces extending up to 0.02 hPa. Section 4 presents additional details on horizontal and vertical grids. Information of the model surface representation can be found in Appendix B. The GEOS-5 product is organized into file collections that are described in detail in Appendix C. Additional details about variables listed in this file specification can be found in a separate document, the GEOS-5 File Specification Variable Definition Glossary. Documentation about the current access methods for products described in this document can be found on the GEOS-5 Nature Run portal: http://gmao.gsfc.nasa.gov/projects/G5NR. Information on the scientific quality of this simulation will appear in a forthcoming NASA Technical Report Series on Global Modeling and Data Assimilation to be available from http://gmao.gsfc.nasa.gov/pubs/tm/.

GEOS-5↗

Ice Roughness in Short Duration SLD Icing Events

Ice accretion codes depend on models of roughness parameters to account for the enhanced heat transfer during the ice accretion process. While mitigating supercooled large droplet (SLD or Appendix O) icing is a significant concern for manufacturers seeking future vehicle certification due to the pending regulation, historical ice roughness studies have been performed using Appendix C icing clouds which exhibit mean volumetric diameters (MVD) much smaller than SLD clouds. Further, the historical studies of roughness focused on extracting parametric representations of ice roughness using multiple images of roughness elements. In this study, the ice roughness developed on a 21-in. NACA 0012 at 0deg angle of attack exposed to short duration SLD icing events was measured in the Icing Research Tunnel at the NASA Glenn Research Center. The MVD's used in the study ranged from 100 micrometer to 200 micrometers, in a 67 m/s flow, with liquid water contents of either 0.6 gm/cubic meters or 0.75 gm/cubic meters. The ice surfaces were measured using a Romer Absolute Arm laser scanning system. The roughness associated with each surface point cloud was measured using the two-dimensional self-organizing map approach developed by McClain and Kreeger (2013) resulting in statistical descriptions of the ice roughness.

Icing↗

Marshall Space Flight Center Faculty Fellowship Program

The Faculty Fellowship program was revived in the summer of 2015 at NASA Marshall Space Flight Center, following a period of diminished faculty research activity here since 2006 when budget cuts in the Headquarters' Education Office required realignment. Several senior Marshall managers recognized the need to involve the Nation's academic research talent in NASA's missions and projects to the benefit of both entities. These managers invested their funds required to establish the renewed Faculty Fellowship program in 2015, a 10-week residential research involvement of 16 faculty in the laboratories and offices at Marshall. These faculty engineers and scientists worked with NASA collaborators on NASA projects, bringing new perspectives and solutions to bear. This Technical Memorandum is a compilation of the research reports of the 2015 Marshall Faculty Fellowship program, along with the Program Announcement (appendix A) and the Program Description (appendix B). The research touched on seven areas-propulsion, materials, instrumentation, fluid dynamics, human factors, control systems, and astrophysics. The propulsion studies included green propellants, gas bubble dynamics, and simulations of fluid and thermal transients. The materials investigations involved sandwich structures in composites, plug and friction stir welding, and additive manufacturing, including both strength characterization and thermosets curing in space. The instrumentation projects involved spectral interfero- metry, emissivity, and strain sensing in structures. The fluid dynamics project studied the water hammer effect. The human factors project investigated the requirements for close proximity operations in confined spaces. Another team proposed a controls system for small launch vehicles, while in astrophysics, one faculty researcher estimated the practicality of weather modification by blocking the Sun's insolation, and another found evidence in satellite data of the detection of a warm-hot intergalactic medium filament. Our goal is to continue the Faculty Fellowship effort with Center funds in succeeding summers.

Six, N. F.↗

Lessons Learned Study Final Report for the Exploration Systems Mission Directorate

This report is the final product of a 90-day study performed for the Exploration Systems Mission Directorate. The study was to assemble lessons NASA has learned from previous programs that could help the Exploration Systems Mission Directorate pursue the Exploration vision. It focuses on those lessons that should have the greatest significance to the Directorate during the formulation of program and mission plans. The study team reviewed a large number of lessons learned reports and data bases, including the Columbia Accident Investigation Board and Rogers Commission reports on the Shuttle accidents, accident reports from robotic space flight systems, and a number of management reviews by the Defense Sciences Board, Government Accountability Office, and others. The consistency of the lessons, findings, and recommendations validate the adequacy of the data set. In addition to reviewing existing databases, a series of workshops was held at each of the NASA centers and headquarters that included senior managers from the current workforce as well as retirees. The full text of the workshop reports is included in Appendix A. A lessons learned website was opened up to permit current and retired NASA personnel and on-site contractors to input additional lessons as they arise. These new lessons, when of appropriate quality and relevance, will be brought to the attention of managers. The report consists of four parts: Part 1 provides a small set of lessons, called the Executive Lessons Learned, that represent critical lessons that the Exploration Systems Mission Directorate should act on immediately. This set of Executive Lessons and their supporting rationale have been reviewed at length and fully endorsed by a team of distinguished NASA alumni; Part 2 contains a larger set of lessons, called the Selected Lessons Learned, which have been chosen from the lessons database and center workshop reports on the basis of their specific significance and relevance to the near-term work of the Exploration Directorate. These lessons frequently support the Executive lessons but are more general in nature; Part 3 consists of the reports of the center workshops that were conducted as part of this activity. These reports are included in their entirety (approximately 200 pages) in Appendix G and have significance for specific managers; Part 4 consists of the remainder of the lessons that have been selected by this effort and assembled into a database for the use of the Explorations Directorate. The database is archived and hosted in the Lessons Learned Knowledge Network, which provides a flexible search capability using a wide variety of search terms. Finally, a spreadsheet lists databases searched and a bibliography identifies reports that have been reviewed as sources of lessons for this task. NASA has been presented with many learning opportunities. We have conducted numerous programs, some extremely successful and others total failures. Most have been documented with a formal lessons learned activity, but we have not always incorporated these learning opportunities into our normal modes of business. For example, the Robbins Report of 2001 clearly indicates that many project failures of the past two decades were the result of violating well documented best practices, often in direct violation of management instructions and directives. An overarching lesson emerges: that disciplined execution in accordance with proven best practices is the greatest single contributor to a successful program. The Lessons Learned task team offers a sincere hope that the lessons presented herein will be helpful to the Exploration Systems Directorate in charting and executing their course. The success of the Directorate and of NASA in general depends on our collective ability to move forward without having to relearn the lessons of those who have gone before.

Van Laak, Jim↗