Search NASA⌕ Search

SEARCH · Search NASA

Results for “NASA perspective”

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 199 records · Page 11

Thermal Challenges from GSFC Planetary Missions

Planetary science missions introduce many thermal challenges based on their varied thermal environment. Additionally planetary missions often include specific payloads that introduce further thermal design challenges. This presentation provides an overview of those challenges through the perspective of NASA planetary science missions that GSFC has been involved with. It also presents a look ahead at how these challenges will be expanded with the proposed mission concepts in the 2022 Planetary decadal survey.

Thermal Control Planetary Probe↗

NASA's Impact in Florida: A Tech Transfer Perspective

The Innovative Partnerships Program (IPP) Office at NASA's Kennedy Space Center is dedicated to forming partnerships that can positively contribute to -- and benefit from -- NASA's research and development (R&D) and technology innovations. This document discusses the IPP-driven impacts of NASA in Florida.

Dunn, Carol↗

Technology transfer program: Perspective

Most of NASA's technology transfer activities are in the area of land use (development, suitability, and planning); forestry (including wildlife and range and vegetation inventories) agriculture related activities; and water resources. The technology dissemination function is exercised through three regional applications centers which are involved in 91 applications projects within 22 states. In addition there are approximately eight application system verification transfer (ASVT) projects, 21 university applications branches, institutionalized liason activities with public interest groups, and user requirements activities. As the result of budget cuts, the ASVT and user requirements and awareness programs are to be phased out at the end of FY81. The university applications programs are to be phased down and terminated by 1985. NASA will continue to work with the user more in an R & D and an applications development capacity, and not in a national scale or administrative way.

Toyshov, A. J.↗

Cratering on Titan: A Pre-Cassini Perspective

The NASA-ESA Cassini mission, comprising a formidably instrumented orbiter and parachute-borne probe to be launched this October, promises to reveal a crater population on Titan that has been heretofore hidden by atmospheric haze. This population on the largest remaining unexplored surface in the solar system will be invaluable in comparative planetological studies, since it introduces evidence of the atmospheric effects of cratering on an icy satellite. Here, I highlight some impact features we may hope to find and could devote some modeling effort toward. Titan in a Nutshell: Radius= 2575 km. Density= 1880 kg/cubic m consistent with rock-ice composition. Surface pressure = 1.5 bar. Surface gravity = 1.35 m/square s Atmosphere -94% N2 6% CH, Surface temperature = 94K Tropopause temperature = 70K at 40 km alt. Probable liquid hydrocarbon deposits exist on or near the surface.Titan in a Nutshell: Radius= 2575 km. Density= 1880 kg/cubic m consistent with rock-ice composition. Surface pressure = 1.5 bar. Surface gravity = 1.35 m/square s; Atmosphere about 94% N2 6% CH, Surface temperature = 94K Tropopause temperature = 70K at 40 km alt. Probable liquid hydrocarbon deposits exist on or near the surface. Titan is comparable to Callisto and Ganymede for strength/gravity, Mars/Earth/Venus for atmospheric interaction, and Hyperion, Rhea, and Iapetus for impactor distribution. The leading/trailing asymmetry of crater density from heliocentric impactors is expected to be about 5-6, in the absence of resurfacing. Any Saturnocentric impactor population is likely to alter this. In particular the impact disruption of Hyperion is noted; because of the 3:4 orbital resonance with Titan, fragments from the proto-Hyperion breakup would have rapidly accreted onto Titan. Titan's resurfacing history is of course unknown. The disruption of impactors into fragments that individually create small craters is expected to occur. A crude estimate suggests a maximum separation of about 2 km (compared with 4 km on Venus, or 0.5 km on Earth). Crater chains are unlikely on Titan, since impactors must pass close enough to Saturn to be tidally disrupted; as a result, they would suffer aerodynamic disruption. Crater counting on adjacent satellites gives densities of about 200 per 10 (exp 6) square km for 20-km-diameter craters. However, the presence of a thick atmosphere leads to atmospheric shielding, depleting the relative abundance of small craters. This has been evaluated by models, and the relative abundance of small craters may be due to a diagnostic atmospheric collapse. A number of radar-dark "splotches" have been detected on Venus; these have been attributed to the interaction of the surface with the atmospheric shockwave produced by the Tunguska-like explosion of a bolide in the atmosphere. Simple analogy suggests that similar features might occur on Titan, but the shocked mass density (which controls the momentum coupling between the surface and the shockwave) of Titan's cold N2 atmosphere is about 20x smaller than that of Venus's hot CO2 atmosphere. Unless ice is much more easily turned to rubble than is rock, such features seem less probable on Titan. When the energy deposited by an impact forms a fireball with an equilibrate greater than one scale height, the fireball expands upward and can distribute ejecta. on ballistic exoatmospheric trajectories. On Venus this process is believed to be responsible for the parabolic features; the interaction of various-sized particles falling through the atmosphere with the zonal wind field winnows the particles to form a parabolic deposit. Although such a process is possible on Titan, the large scale height at higher altitudes would make it more difficult. Comparison with craters on other icy satellites suggests that craters on Titan will be fairly shallow (depth/diameter about 0.1) and craters greater than 10 km in diameter will have central peaks or domed bases, perhaps with central pits. The formation of ejecta. blankets may involve the atmosphere in a significant way, both by restraining the expansion of the ejecta cloud and by influencing the thermal history of the ejecta. Compared with Venus, Titan's atmosphere will chill an impact melt somewhat quickly, so the long ejecta flows seen on Venus seem less likely, detailed modeling needs to be performed to determine the impact melt production. Crater topography on Titan may be highlighted by the influence of liquids forming crater lakes. Craters with central peaks will typically form ring-shaped lakes, although horseshoe-shaped takes may be common; domed craters with central pits may even form bullseye lakes with islands with central ponds. If liquids have covered a substantial part of Titan's surface for a substantial period, hydroblemes and tsunami deposits may be common.

Lorenz, R. D.↗

Space Interferometry Mission: A Systems Perspective

In 2006, NASA's Origins Program will launch the Space Interferometry Mission (SIM), a 10 meter baseline optical interferometry instrument, into a Earth trailing orbit.

SIM interferometry Space Interferometry Mission JP↗

The X-15 3-65 Accident: An Aircraft Systems and Flight Control Perspective

Despite the NASA X-15 program's outstanding success in developing and operating the first manned hypersonic research platform, the program suffered a fatal accident on November 15, 1967, when X-15-3, the only aircraft outfitted with advanced pilot displays and an adaptive flight control system, was lost after entering uncontrolled flight at an altitude of 230,000 feet and a velocity near Mach 5. The pilot, Major Michael J. Adams, was incapacitated by the aircraft accelerations and was killed either during the ensuing breakup or upon ground impact. In light of mitigating risk to current and emerging manned aerospace vehicles, a comprehensive systems level analysis of the accident is presented with a focus on the electrical power, flight control, and instrumentation failures that affected not only the vehicle dynamics but substantially impacted the pilot decisions that led to an inevitable loss of control. Insights based on reconstructed flight data as well as analysis and simulation of the X-15's unique adaptive control system, yield new conclusions about the reasons for the control systems anomalous behavior and the system-level interactions and human-machine interface design oversights that led to the accident.

Accident Investigation↗

ASK Magazine

Not everyone looks forward to reviews. Dog and pony shows I've heard them called. Exercises in putting together Power Point charts. Other less tasteful descriptions abound, but I won't bother to summarize these. This is a tasteful magazine after all. In this issue, we've assembled a number of articles on the subject of reviews, particularly as they occur in the NASA project world (although we cover the subject from other perspectives too). Veteran NASA Project Manager Marty Davis, in his article Tangled Up in Reviews, writes, "Many people regard reviews as something onerous, but if we can tailor them so that they're not as bad as they have to be, it can be a great benefit to a project manager." Great benefits to the project manager is what you'll find in Marty's story as he describes not only tailoring a single review but the entire lifecycle of reviews in his project. In Jo Gunderson's story, Calling Down the Fire on Yourself, she describes a young NASA Project Manager who does just that because, as he tells her, I needed to know if there was anything that I had overlooked." How he brings fire down on himself at his project review will inspire other young Project Managers, seasoned managers, and anyone else who reads this powerful story. Leave Your Ego at the Door, by Jenny Baer-Reidhart and Ray Morgan, uses reviews to highlight the creative collaboration that existed between NASA and one of its industry partners. The protagonist of this story is a company who took advantage of NASAs expert advice during reviews and accomplished amazing feats as a result. The story also examines how disasters might well have been avoided by two other NASA partners had they been as open-minded as the first company during their reviews. In Roy Malone's story, Standing Offer, a NASA Project Manager describes how he used a crack review team to help him pass a critical certification inspection while he was a Combat Systems Officer in the Navy. Malone invited the reviewers to come back several times so that they would be able to focus in detail on the many areas of the program that would be scrutinized during the certification inspection. These are just a sampling of some of the articles you'll find in this issue of ASK. We believe this issue offers ample evidence that talented Project Managers know how to use reviews to the great benefit of their projects. A talented Project Manager will typically figure out a way to turn any onerous task into a useful learning exercise. These Project Managers demonstrate that the real value of reviews is that they provide a chance to learn something. No dog and pony shows here.

Laufer, Alexander↗

Development of X-33/X-34 Aerothermodynamic Data Bases: Lessons Learned and Future Enhancements

A synoptic of programmatic and technical lessons learned in the development of aerothermodynamic data bases for the X-33 and X-34 programs is presented in general terms and from the perspective of the NASA Langley Research Center Aerothermodynamics Branch. The format used is that of the "aerothermodynamic chain," the links of which are personnel, facilities, models/test articles, instrumentation, test techniques, and computational fluid dynamics (CFD). Because the aerodynamic data bases upon which the X-33 and X-34 vehicles will fly are almost exclusively from wind tunnel testing, as opposed to CFD, the primary focus of the lessons learned is on ground-based testing. The period corresponding to the development of X-33 and X-34 aerothermodynamic data bases was challenging, since a number of other such programs (e.g., X-38, X-43) competed for resources at a time of downsizing of personnel, facilities, etc., outsourcing, and role changes as NASA Centers served as subcontractors to industry. The impact of this changing environment is embedded in the lessons learned. From a technical perspective, the relatively long times to design and fabricate metallic force and moment models, delays in delivery of models, and a lack of quality assurance to determine the fidelity of model outer mold lines (OML) prior to wind tunnel testing had a major negative impact on the programs. On the positive side, the application of phosphor thermography to obtain global, quantitative heating distributions on rapidly fabricated ceramic models revolutionized the aerothermodynamic optimization of vehicle OMLs, control surfaces, etc. Vehicle designers were provided with aeroheating information prior to, or in conjunction with, aerodynamic information early in the program, thereby allowing trades to be made with both sets of input; in the past only aerodynamic data were available as input. Programmatically, failure to include transonic aerodynamic wind tunnel tests early in the assessment phase led to delays in the optimization phase, as OMLs required modification to provide adequate transonic aerodynamic performance without sacrificing subsonic and hypersonic performance. Funding schedules for industry, based on technical milestones, also presented challenges to aerothermodynamics seeking optimum flying characteristics across the subsonic to hypersonic speed regimes and minimum aeroheating. This paper is concluded with a brief discussion of enhancements in ground-based testing/CFD capabilities necessary to partially/fully satisfy future requirements.

Miller, C. G.↗

NASA Systems Engineering Handbook

This handbook is intended to provide general guidance and information on systems engineering that will be useful to the NASA community. It provides a generic description of Systems Engineering (SE) as it should be applied throughout NASA. A goal of the handbook is to increase awareness and consistency across the Agency and advance the practice of SE. This handbook provides perspectives relevant to NASA and data particular to NASA. The coverage in this handbook is limited to general concepts and generic descriptions of processes, tools, and techniques. It provides information on systems engineering best practices and pitfalls to avoid. There are many Center-specific handbooks and directives as well as textbooks that can be consulted for in-depth tutorials. This handbook describes systems engineering as it should be applied to the development and implementation of large and small NASA programs and projects. NASA has defined different life cycles that specifically address the major project categories, or product lines, which are: Flight Systems and Ground Support (FS&GS), Research and Technology (R&T), Construction of Facilities (CoF), and Environmental Compliance and Restoration (ECR). The technical content of the handbook provides systems engineering best practices that should be incorporated into all NASA product lines. (Check the NASA On-Line Directives Information System (NODIS) electronic document library for applicable NASA directives on topics such as product lines.) For simplicity this handbook uses the FS&GS product line as an example. The specifics of FS&GS can be seen in the description of the life cycle and the details of the milestone reviews. Each product line will vary in these two areas; therefore, the reader should refer to the applicable NASA procedural requirements for the specific requirements for their life cycle and reviews. The engineering of NASA systems requires a systematic and disciplined set of processes that are applied recursively and iteratively for the design, development, operation, maintenance, and closeout of systems throughout the life cycle of the programs and projects.

Source record↗

Applying Spatial Audio to Human Interfaces: 25 Years of NASA Experience

From the perspective of human factors engineering, the inclusion of spatial audio within a human-machine interface is advantageous from several perspectives. Demonstrated benefits include the ability to monitor multiple streams of speech and non-speech warning tones using a cocktail party advantage, and for aurally-guided visual search. Other potential benefits include the spatial coordination and interaction of multimodal events, and evaluation of new communication technologies and alerting systems using virtual simulation. Many of these technologies were developed at NASA Ames Research Center, beginning in 1985. This paper reviews examples and describes the advantages of spatial sound in NASA-related technologies, including space operations, aeronautics, and search and rescue. The work has involved hardware and software development as well as basic and applied research.

Begault, Durand R.↗

Expanded Guidance for NASA Systems Engineering. Volume 1: Systems Engineering Practices

This document is intended to provide general guidance and information on systems engineering that will be useful to the NASA community. It provides a generic description of Systems Engineering (SE) as it should be applied throughout NASA. A goal of the expanded guidance is to increase awareness and consistency across the Agency and advance the practice of SE. This guidance provides perspectives relevant to NASA and data particular to NASA. This expanded guidance should be used as a companion for implementing NPR 7123.1, Systems Engineering Processes and Requirements, the Rev 2 version of SP-6105, and the Center-specific handbooks and directives developed for implementing systems engineering at NASA. It provides a companion reference book for the various systems engineering-related training being offered under NASA's auspices.

Steven R Hirshorn↗

A GNC Perspective of the Launch and Commissioning of NASA's SMAP (Soil Moisture Active Passive) Spacecraft

The NASA Soil Moisture Active Passive (SMAP) spacecraft was designed to use radar and radiometer measurements to produce global soil moisture measurements every 2-3 days. The SMAP spacecraft is a complicated dual-spinning design with a large 6 meter deployable mesh reflector mounted on a platform that spins at 14.6 rpm while the Guidance Navigation and Control algorithms maintain precise nadir pointing for the de-spun portion of the spacecraft. After launching in early 2015, the Guidance Navigation and Control software and hardware aboard the SMAP spacecraft underwent an intensive spacecraft checkout and commissioning period. This paper describes the activities performed by the Guidance Navigation and Control team to confirm the health and phasing of subsystem hardware and the functionality of the guidance and control modes and algorithms. The operations tasks performed, as well as anomalies that were encountered during the commissioning, are explained and results are summarized.

Brown, Todd S.↗