Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “endurance”

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,153 records · Page 64

Emergency Response Fire-Imaging UAS Missions over the Southern California Wildfire Disaster

Objectives include: Demonstrate capabilities of UAS to overfly and collect sensor data on widespread fires throughout Western US. Demonstrate long-endurance mission capabilities (20-hours+). Image multiple fires (greater than 4 fires per mission), to showcase extendable mission configuration and ability to either linger over key fires or station over disparate regional fires. Demonstrate new UAV-compatible, autonomous sensor for improved thermal characterization of fires. Provide automated, on-board, terrain and geo-rectified sensor imagery over OTH satcom links to national fire personnel and Incident commanders. Deliver real-time imagery (within 10-minutes of acquisition). Demonstrate capabilities of OTS technologies (GoogleEarth) to serve and display mission-critical sensor data, coincident with other pertinent data elements to facilitate information processing (WX data, ground asset data, other satellite data, R/T video, flight track info, etc).

Cobleigh, Brent R.↗

Solar Airplanes and Regenerative Fuel Cells

A solar electric aircraft with the potential to "fly forever" has captured NASA's interest, and the concept for such an aircraft was pursued under Aeronautics Environmental Research Aircraft and Sensor Technology (ERAST) project. Feasibility of this aircraft happens to depend on the successful development of solar power technologies critical to NASA's Exploration Initiatives; hence, there was widespread interest throughout NASA to bring these technologies to a flight demonstration. The most critical is an energy storage system to sustain mission power during night periods. For the solar airplane, whose flight capability is already limited by the diffuse nature of solar flux and subject to latitude and time of year constraints, the feasibility of long endurance flight depends on a storage density figure of merit better than 400-600 watt-hr per kilogram. This figure of merit is beyond the capability of present day storage technologies (other than nuclear) but may be achievable in the hydrogen-oxygen regenerative fuel cell (RFC). This potential has led NASA to undertake the practical development of a hydrogen-oxygen regenerative fuel cell, initially as solar energy storage for a high altitude UAV science platform but eventually to serve as the primary power source for NASAs lunar base and other planet surface installations. Potentially the highest storage capacity and lowest weight of any non-nuclear device, a flight-weight RFC aboard a solar-electric aircraft that is flown continuously through several successive day-night cycles will provide the most convincing demonstration that this technology's widespread potential has been realized. In 1998 NASA began development of a closed cycle hydrogen oxygen PEM RFC under the Aeronautics Environmental Research Aircraft and Sensor Technology (ERAST) project and continued its development, originally for a solar electric airplane flight, through FY2005 under the Low Emissions Alternative Power (LEAP) project. Construction of the closed loop system began in 2002 at the NASA Glenn Research Center in Cleveland, Ohio. System checkout was completed, and testing began, in July of 2003. The initial test sequences were done with only a fuel cell or electrolyzer in the test rig. Those tests were used to verify the test apparatus, procedures, and software. The first complete cycles of the fully closed loop, regenerative fuel cell system were successfully completed in the following September. Following some hardware upgrades to increase reactant recirculation flow, the test rig was operated at full power in December 2003 and again in January 2004. In March 2004 a newer generation of fuel cell and electrolyzer stacks was substituted for the original hardware and these stacks were successfully tested at full power under cyclic operation in June of 2004.

Bents, David J.↗

High temperature ceramic/metal joint structure

A high temperature turbine engine includes a hybrid ceramic/metallic rotor member having ceramic/metal joint structure. The disclosed joint is able to endure higher temperatures than previously possible, and aids in controlling heat transfer in the rotor member.

Boyd, Gary L.↗

The Columbia Debris Loan Program; Examples of Microscopic Analysis

Following the tragic loss of the Space Shuttle Columbia NASA formed The Columbia Recovery Office (CRO). The CRO was initially formed at the Johnson Space Center after the conclusion of recovery operations on May 1,2003 and then transferred .to the Kennedy Space Center on October 6,2003 and renamed The Columbia Recovery Office and Preservation. An integral part of the preservation project was the development of a process to loan Columbia debris to qualified researchers and technical educators. The purposes of this program include aiding in the advancement of advanced spacecraft design and flight safety development, the advancement of the study of hypersonic re-entry to enhance ground safety, to train and instruct accident investigators and to establish an enduring legacy for Space Shuttle Columbia and her crew. Along with a summary of the debris loan process examples of microscopic analysis of Columbia debris items will be presented. The first example will be from the reconstruction following the STS- 107 accident and how the Materials and Pro~es~steesa m used microscopic analysis to confirm the accident scenario. Additionally, three examples of microstructural results from the debris loan process from NASA internal, academia and private industry will be presented.

Russell, Rick↗

NASA Dryden's UAS Service Capabilities

The vision of NASA s Dryden Flight Research Center is to "fly what others only imagine." Its mission is to advance technology and science through flight. Objectives supporting the mission include performing flight research and technology integration to revolutionize aviation and pioneer aerospace technology, validating space exploration concepts, conducting airborne remote sensing and science missions, and supporting operations of the Space Shuttle and the International Space Station. A significant focus of effort in recent years has been on Unmanned Aircraft Systems (UAS), both in support of the Airborne Science Program and as research vehicles to advance the state of the art in UAS. Additionally, the Center has used its piloted aircraft in support of UAS technology development. In order to facilitate greater access to the UAS expertise that exists at the Center, that expertise has been organized around three major capabilities. The first is access to high-altitude, long-endurance UAS. The second is the establishment of a test range for small UAS. The third is safety case assessment support.

Bauer, Jeff↗

High temperature turbine engine structure

A high temperature turbine engine includes a hybrid ceramic/metallic rotor member having ceramic/metal joint structure. The disclosed joint is able to endure higher temperatures than previously possible, and aids in controlling heat transfer in the rotor member.

Boyd, Gary L.↗

NASA 2007 Western States Fire Missions (WSFM)

This viewgraph presentation describes the Western states Fire Missions (WSFM) that occurred in 2007. The objectives of this mission are: (1) Demonstrate capabilities of UAS to overfly and collect sensor data on widespread fires throughout Western US. (1) Demonstrate long-endurance mission capabilities (20-hours+). (2) Image multiple fires (greater than 4 fires per mission), to showcase extendable mission configuration and ability to either linger over key fires or station over disparate regional fires. (3) Demonstrate new UAV-compatible, autonomous sensor for improved thermal characterization of fires. (4) Provide automated, on-board, terrain and geo-rectified sensor imagery over OTH satcom links to national fire personnel and Incident commanders. (5) Deliver real-time imagery to (within 10-minutes of acquisition). (6) Demonstrate capabilities of OTS technologies (GoogleEarth) to serve and display mission-critical sensor data, coincident with other pertinent data elements to facilitate information processing (WX data, ground asset data, other satellite data, R/T video, flight track info, etc).

Buoni, Greg↗

Chemostratigraphy and Fe Mineralogy of the Victoria Crater Duck Bay Section: Opportunity APXS and Moessbauer Results

Meridiani Planum is a vast plain of approximately horizontally bedded sedimentary rocks composed of mixed and reworked basaltic and evaporitic sands containing secondary, diagenetic minerals [e.g., 1-5]. Because bedding planes are subparallel to topography, investigation of contiguous stratigraphy requires examining exposures in impact craters. Early in the mission (sols 130-317), Opportunity was commanded to do detailed study of exposed outcrops in Endurance crater, including the contiguous Karatepe section at the point of ingress. Just over 1000 sols later and roughly 7 km to the south, the rover is being commanded to do a similar study of the Duck Bay section of Victoria crater. Here we report on the preliminary results from the Alpha Particle X-ray Spectrometer (APXS) and Moessbauer instruments.

Mittlefehldt, D. W.↗

A Freezable Heat Exchanger for Space Suit Radiator Systems

During an ExtraVehicular Activity (EVA), both the heat generated by the astronaut s metabolism and that produced by the Portable Life Support System (PLSS) must be rejected to space. The heat sources include the heat of adsorption of metabolic CO2, the heat of condensation of water, the heat removed from the body by the liquid cooling garment and the load from the electrical components. Although the sublimator hardware to reject this load weighs only 1.58 kg (3.48 lbm), an additional 3.6 kg (8 lbm) of water are loaded into the unit, most of which is sublimated and lost to space, thus becoming the single largest expendable during an eight-hour EVA. Using a radiator to reject heat from the astronaut during an EVA can reduce the amount of expendable water consumed in the sublimator. Radiators have no moving parts and are thus highly reliable. Past freezable radiators have been too heavy, but the weight can be greatly reduced by placing a small and freeze tolerant heat exchanger between the astronaut and radiator, instead of making the very large radiator freeze tolerant. Therefore, the key technological innovation to improve space suit radiator performance was the development of a lightweight and freezable heat exchanger that accommodates the variable heat load generated by the astronaut. Herein, we present the heat transfer performance of a newly designed heat exchanger that endured several freeze / thaw cycles without any apparent damage. The heat exchanger was also able to continuously turn down or turn up the heat rejection to follow the variable load.

Nabity, James A.↗

Contingency Management Requirements Document: Preliminary Version. Revision F

This is the High Altitude, Long Endurance (HALE) Remotely Operated Aircraft (ROA) Contingency Management (CM) Functional Requirements document. This document applies to HALE ROA operating within the National Airspace System (NAS) limited at this time to enroute operations above 43,000 feet (defined as Step 1 of the Access 5 project, sponsored by the National Aeronautics and Space Administration). A contingency is an unforeseen event requiring a response. The unforeseen event may be an emergency, an incident, a deviation, or an observation. Contingency Management (CM) is the process of evaluating the event, deciding on the proper course of action (a plan), and successfully executing the plan.

Source record↗

Collision Avoidance Functional Requirements for Step 1. Revision 6

This Functional Requirements Document (FRD) describes the flow of requirements from the high level operational objectives down to the functional requirements specific to cooperative collision avoidance for high altitude, long endurance unmanned aircraft systems. These are further decomposed into performance and safety guidelines that are backed up by analysis or references to various documents or research findings. The FRD should be considered when establishing future policies, procedures, and standards pertaining to cooperative collision avoidance.

Source record↗

HALE UAS Concept of Operations. Version 3.0

This document is a system level Concept of Operations (CONOPS) from the perspective of future High Altitude Long Endurance (HALE) Unmanned Aircraft Systems (UAS) service providers and National Airspace System (NAS) users. It describes current systems (existing UAS), describes HALE UAS functions and operations to be performed (via sample missions), and offers insight into the user s environment (i.e., the UAS as a system of systems). It is intended to be a source document for NAS UAS operational requirements, and provides a construct for government agencies to use in guiding their regulatory decisions, architecture requirements, and investment strategies. Although it does not describe the technical capabilities of a specific HALE UAS system (which do, and will vary widely), it is intended to aid in requirements capture and to be used as input to the functional requirements and analysis process. The document provides a basis for development of functional requirements and operational guidelines to achieve unrestricted access into the NAS. This document is an FY06 update to the FY05 Access 5 Project-approved Concept of Operations document previously published in the Public Domain on the Access 5 open website. This version is recommended to be approved for public release also. The updates are a reorganization of materials from the previous version with the addition of an updated set of operational requirements, inclusion of sample mission scenarios, and identification of roles and responsibilities of interfaces within flight phases.

Source record↗

Preliminary C3 Loading Analysis for Future High-Altitude Unmanned Aircraft in the NAS

This document provides a preliminary assessment and summary of the command, control, and communications (C(sup 3)) loading requirements of a generic future high-altitude, long-endurance unmanned aircraft (UA) operating at in the National Airspace System. Two principal types of C(sup 3) traffic are considered in our analysis: communications links providing air traffic services (ATS) to the UA and its human pilot, and the command and control data links enabling the pilot to operate the UA remotely. we have quantified the loading requirements of both types of traffic for two different assumed levels of UA autonomy. Our results indicate that the potential use of UA-borne relays for the ATS links, and the degree of autonomy exercised by the UA during the departure and arrival phases of its flight, will be among the key drivers of C(sup 3) loading and bandwidth requirements.

Ho, Yan-Shek↗

Access 5 - Step 1: Human Systems Integration Program Plan (HSIPP)

This report describes the Human System Interface (HSI) analysis, design and test activities that will be performed to support the development of requirements and design guidelines to facilitate the incorporation of High Altitude Long Endurance (HALE) Remotely Operated Aircraft (ROA) at or above FL400 in the National Airspace System (NAS). These activities are required to support the design and development of safe, effective and reliable ROA operator and ATC interfaces. This plan focuses on the activities to be completed for Step 1 of the ACCESS 5 program. Updates to this document will be made for each of the four ACCESS 5 program steps.

Source record↗

Work Package 5: Contingency Management. Mission Planning Requirements Document: Preliminary Version. Revision A

The purpose of this document is to identify the general flight/mission planning requirements for same-day file-and-fly access to the NAS for both civil and military High-Altitude Long Endurance (HALE) Unmanned Aircraft System (UAS). Currently the scope of this document is limited to Step 1, operations above flight level 43,000 feet (FL430). This document describes the current applicable mission planning requirements and procedures for both manned and unmanned aircraft and addresses HALE UAS flight planning considerations in the future National Airspace System (NAS). It also discusses the unique performance and operational capabilities of HALE UAS associated with the Access 5 Project, presents some of the projected performance characteristics and conceptual missions for future systems, and provides detailed analysis of the recommended mission planning elements for operating HALE UAS in the NAS.

Source record↗

Step 1: Human System Interface (HSI) Functional Requirements Document (FRD). Version 2

This Functional Requirements Document (FRD) establishes a minimum set of Human System Interface (HSI) functional requirements 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)". Basically, it provides what functions are necessary to fly UAS in the NAS. The framework used to identify the appropriate functions was the "Aviate, Navigate, Communicate, and Avoid Hazards" structure identified in the Access 5 FRD. As a result, fifteen high-level functional requirements were developed. In addition, several of them have been decomposed into low-level functional requirements to provide more detail.

Source record↗

HALE UAS Command and Control Communications: Step 1 - Functional Requirements Document. Version 4.0

The High Altitude Long Endurance (HALE) unmanned aircraft system (UAS) communicates with an off-board pilot-in-command in all flight phases via the C2 data link, making it a critical component for the UA to fly in the NAS safely and routinely. This is a new requirement in current FAA communications planning and monitoring processes. This document provides a set of comprehensive C2 communications functional requirements and performance guidelines to help facilitate the future FAA certification process for civil UAS to operate in the NAS. The objective of the guidelines is to provide the ability to validate the functional requirements and in future be used to develop performance-level requirements.

Source record↗

Functional Requirements Document for HALE UAS Operations in the NAS: Step 1. Version 3

The purpose of this Functional Requirements Document (FRD) is to compile the 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. These functional requirements could support the development of a minimum set of policies, procedures and standards by the Federal Aviation Administration (FAA) and various standards organizations. It is envisioned that this comprehensive body of work will enable the FAA to establish and approve regulations to govern safe operation of UAS in the NAS on a routine or daily "file and fly" basis. The approach used to derive the functional requirements found within this FRD was to decompose the operational requirements and objectives identified within the Access 5 Concept of Operations (CONOPS) into the functions needed to routinely and safely operate a HALE UAS in the NAS. As a result, four major functional areas evolved to enable routine and safe UAS operations for an on-demand basis in the NAS. These four major functions are: Aviate, Navigate, Communicate, and Avoid Hazards. All of the functional requirements within this document can be directly traceable to one of these four major functions. Some functions, however, are traceable to several, or even all, of these four major functions. These cross-cutting functional requirements support the "Command / Control: function as well as the "Manage Contingencies" function. The requirements associated to these high-level functions and all of their supporting low-level functions are addressed in subsequent sections of this document.

Source record↗