SEARCH · Search NASA

Results for “flight data system”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 487 records · Page 27

All sources NASA NTRS DOE OSTI

NASA NTRS2018

Use of Open Networks and Delay-Tolerant Protocol to Decrease WAN Latency of EOS near Real-Time Data

Since 1999, NASA's Earth Observing System Data Operations System (EDOS) project at Goddard Space Flight Center (GSFC) has provided high-rate data capture, level zero processing, and product distribution services for a majority of NASA's EOS (Earth Observing System) high-rate missions, including Terra, Aqua, Aura, ICESat, EO-1, SMAP, and OCO-2. EDOS high-rate science and engineering (150-300 Mbps) data-driven capture systems are deployed at 7 worldwide ground stations which are connected via both private (closed) and public (open) wide area networks (WANs) to the centralized EDOS Level Zero Processing Facility (LZPF) located at GSFC, where the data is processed and Level 0 products are distributed to users worldwide. All data transferred over the open networks to GSFC traverse an IPSec tunnel, providing the same level of security as a VPN connection. EDOS produces both time-based and near real-time products (session-based). Near real-time data products are produced from a single ground station contact; time-based products are produced from multiple ground station contacts. EDOS is the primary supplier of EOS Level 0 data to the NASA near real-time user community known as the Land, Atmosphere Near real-time Capability for EOS (LANCE). For the past few years, EDOS has streamlined its systems to reduce WAN latency for near real-time data delivery, including implementing Quality of Service (QoS), expanding closed network bandwidth, adding open network connections with more bandwidth, and implementing a delay-tolerant protocol to mitigate long round-trip times to remote ground stations.

Delay-Tolerant Protocol↗

NASA NTRS2019

Medical Data Architecture (MDA) Project Status

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically-relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm. The medical system requirements are being developed in parallel with the exploration mission architecture and vehicle design. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products supported by current prototype development will directly inform exploration medical system requirements.In fiscal year 2018, the MDA project developed Test Bed 2, the second iteration in a series of prototypes with functionality focused on data security through role-based access control and encryption, integration with One Portal exercise software and ingestion of an ultrasound Digital Imaging and Communications in Medicine (DICOM) file and image display. Test Bed 2 advances the medical data system architecture framework by providing these functionalities in a scalable system that maintained a layered, modular design. The architecture framework uses a data services approach with role-based access to data in a customized medical record system suitable for space exploration. These functionalities were demonstrated as part of the Next Space Technologies for Exploration Partnerships (NextSTEP) ground test demonstrated at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Interfacing to a Core Flight Software (CFS) system, the MDA system, using Consultative Committee for Space Data Systems (CCSDS) protocol, transferred an exercise file from the simulated flight MDA system to a mirrored MDA system on the ground through the CFS system. The selection of data sources and demonstrations enabled the team to address stakeholder concerns throughout the development process. In the next iteration, the MDA team will work with stakeholders to identify additional relevant functionalities to further advance system data models, standards and principles that will inform the medical system requirements development.

medical data architecture↗

NASA NTRS1989

An American knowledge base in England - Alternate implementations of an expert system flight status monitor

A joint activity between the Dryden Flight Research Facility of the NASA Ames Research Center (Ames-Dryden) and the Royal Aerospace Establishment (RAE) on knowledge-based systems has been agreed. Under the agreement, a flight status monitor knowledge base developed at Ames-Dryden has been implemented using the real-time AI (artificial intelligence) toolkit MUSE, which was developed in the UK. Here, the background to the cooperation is described and the details of the flight status monitor and a prototype MUSE implementation are presented. It is noted that the capabilities of the expert-system flight status monitor to monitor data downlinked from the flight test aircraft and to generate information on the state and health of the system for the test engineers provides increased safety during flight testing of new systems. Furthermore, the expert-system flight status monitor provides the systems engineers with ready access to the large amount of information required to describe a complex aircraft system.

Butler, G. F.↗

NASA NTRS1994

Basic principles of flight test instrumentation engineering, volume 1, issue 2

Volume 1 of the AG 300 series on ´Flight Test Instrumentation´ gives a general introduction to the basic principles of flight test instrumentation. The other volumes in the series provide more detailed treatments of selected topics on flight test instrumentation. Volume 1, first published in 1974, has been used extensively as an introduction for instrumentation courses and symposia, as well as being a reference work on the desk of most flight test and instrumentation engineers. It is hoped that this second edition, fully revised, will be used with as much enthusiasm as the first edition. In this edition a flight test system is considered to include both the data collection and data processing systems. In order to obtain an optimal data flow, the overall design of these two subsystems must be carefully matched; the detail development and the operation may have to be done by separate groups of specialists. The main emphasis is on the large automated instrumentation systems used for the initial flight testing of modern military and civil aircraft. This is done because there, many of the problems, which are discussed here, are more critical. It does not imply, however, that smaller systems with manual data processing are no longer used. In general, the systems should be designed to provide the required results at the lowest possible cost. For many tests which require only a few parameters, relatively simple systems are justified, especially if no complex equipment is available to the user. Although many of the aspects discussed in this volume apply to both small and large systems, aspects of the smaller systems are mentioned only when they are of special interest. The volume has been divided into three main parts. Part 1 defines the main starting points for the design of a flight test instrumentation system, as seen from the points of view of the flight test engineer and the instrumentation engineer. In Part 2 the discussion is concentrated on those aspects which apply to each individual measuring channel, and in Part 3 the main emphasis is on the integration of the individual data channels into one data collection system and on those aspects of the data processing which apply to the complete system.

channels (data transmission)↗

NASA NTRS1991

Rotor and control system loads analysis of the XV-15 with the advanced technology blades

An analysis of the rotor and control system loads of the XV-15 with the Advanced Technology Blades (XV-15/ATB) was conducted to study the effects of modifications designed to alleviate high collective actuator loads encountered during initial flight tests. Rotor loads predictions were correlated with flight data to establish accuracies of the methodology used in the analysis. Control system loads predictions were then examined and were also correlated with flight data. The results showed a significant reduction in 3/rev collective actuator loads of the XV-15/ATB when the control system stiffness was increased and the rotor blade chord balance and tip twist were modified.

Totah, Joseph J.↗

NASA NTRS1990

Rotor and control system loads analysis of the XV-15 with the advanced technology blades

An analysis of the rotor and control system loads of the XV-15 with the Advanced Technology Blades (XV-15/ATB) was conducted to investigate the effects of modifications designed to alleviate high collective actuator loads encountered during initial flight tests. Rotor loads predictions were correlated with flight data to establish accuracies of the methodology used in the analysis. Control system loads predictions were then examined and were also correlated with flight data. The results showed a significant reduction in 3/rev collective actuator loads of the XV-15/ATB when the control system stiffness was increased and the rotor blade chord balance and tip twist were modified.

Totah, Joseph J.↗

NASA NTRS1982

Beta experiment

A focused laser doppler velocimeter (LDV) system was developed for the measurement of atmospheric backscatter (beta) from aerosols at infrared wavelengths. A Doppler signal generator was used in mapping the coherent sensitive focal volume of a focused LDV system. System calibration data was analyzed during the flight test activity scheduled for the Beta system. These analyses were performed to determine the acceptability of the Beta measurement system's performance.

Source record↗

NASA NTRS2006

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challange

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), responsible for project management and flight operations; Orbital Sciences Corporation (OSC), spacecraft builder and responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), responsible for science planning and operations. As a cost-capped mission, one of Dawn s implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL s ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL s GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project s commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to an overall systems engineering process and fundamental systems engineering practices: decomposition of the project request into manageable requirements; definition of a structured yet flexible development process; integration of multiple ground disciplines and experts into a focused team effort; in-process risk management; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

systems engineering↗

NASA NTRS1992

Engine systems analysis results of the Space Shuttle Main Engine redesigned powerhead initial engine level testing

Engineers regularly analyze SSME ground test and flight data with respect to engine systems performance. Recently, a redesigned SSME powerhead was introduced to engine-level testing in part to increase engine operational margins through optimization of the engine internal environment. This paper presents an overview of the MSFC personnel engine systems analysis results and conclusions reached from initial engine level testing of the redesigned powerhead, and further redesigns incorporated to eliminate accelerated main injector baffle and main combustion chamber hot gas wall degradation. The conclusions are drawn from instrumented engine ground test data and hardware integrity analysis reports and address initial engine test results with respect to the apparent design change effects on engine system and component operation.

Sander, Erik J.↗

NASA NTRS2015

A Preliminary Evaluation of Supersonic Transport Category Vehicle Operations in the National Airspace System

Several public sector businesses and government agencies, including the National Aeronautics and Space Administration are currently working on solving key technological barriers that must be overcome in order to realize the vision of low-boom supersonic flights conducted over land. However, once these challenges are met, the manner in which this class of aircraft is integrated in the National Airspace System may become a potential constraint due to the significant environmental, efficiency, and economic repercussions that their integration may cause. Background research was performed on historic supersonic operations in the National Airspace System, including both flight deck procedures and air traffic controller procedures. Using this information, an experiment was created to test some of these historic procedures in a current-day, emerging Next Generation Air Transportation System (NextGen) environment and observe the interactions between commercial supersonic transport aircraft and modern-day air traffic. Data was gathered through batch simulations of supersonic commercial transport category aircraft operating in present-day traffic scenarios as a base-lining study to identify the magnitude of the integration problems and begin the exploration of new air traffic management technologies and architectures which will be needed to seamlessly integrate subsonic and supersonic transport aircraft operations. The data gathered include information about encounters between subsonic and supersonic aircraft that may occur when supersonic commercial transport aircraft are integrated into the National Airspace System, as well as flight time data. This initial investigation is being used to inform the creation and refinement of a preliminary Concept of Operations and for the subsequent development of technologies that will enable overland supersonic flight.

Underwood, Matthew C.↗

NASA NTRS2006

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

Ground Data System (GDS)↗

NASA NTRS1972

Balloon launched decelerator test program: Post-flight test report, BLDT vehicle AV-2, Viking 1975 project

The pertinent events concerned with the launch, float, and flight of balloon launched decelerator test vehicle AV-2 are discussed. The performance of the decelerator system is analyzed. Data on the flight trajectory and decelerator test points at the time of decelerator deployment are provided. A description of the time history of vehicle events and anomalies encounters during the mission is included.

Dickinson, D.↗

NASA NTRS1973

Balloon launched decelerator test program: Post-flight test report, BLDT vehicle AV-3, Viking 1975 project

The pertinent events concerned with the launch, float, and flight of balloon launched decelerator test vehicle AV-3 are discussed. The performance of the decelerator system is analyzed. Data on the flight trajectory and decelerator test points at the time of decelerator deployment are provided. A description of the time history of vehicle events and anaomalies encounters during the mission is included.

Dickinson, D.↗

NASA NTRS1986

An overview of the NSCAT/N-ROSS program

The NASA Scatterometer (NSCAT) to fly on the U.S. Navy Remote Ocean Sensing System (N-ROSS) mission is presented. The overall N-ROSS mission, the NSCAT flight instrument and groundbased data processing/distribution system, and NASA-supported science and verification activities are described. The N-ROSS system is designed to provide measurements of near-surface wind, ocean topography, wave height, sea-surface temperature, and atmospheric water content over the global oceans. The NSCAT is an improved version of the Seasat scatterometer. It will measure near surface vector winds.

Martin, B. D.↗

NASA NTRS2011

Freeing Space for NASA: Incorporating a Lossless Compression Algorithm into NASA's FOSS System

NASA's Fiber Optic Strain Sensing (FOSS) system can gather and store up to 1,536,000 bytes (1.46 megabytes) per second. Since the FOSS system typically acquires hours - or even days - of data, the system can gather hundreds of gigabytes of data for a given test event. To store such large quantities of data more effectively, NASA is modifying a Lempel-Ziv-Oberhumer (LZO) lossless data compression program to compress data as it is being acquired in real time. After proving that the algorithm is capable of compressing the data from the FOSS system, the LZO program will be modified and incorporated into the FOSS system. Implementing an LZO compression algorithm will instantly free up memory space without compromising any data obtained. With the availability of memory space, the FOSS system can be used more efficiently on test specimens, such as Unmanned Aerial Vehicles (UAVs) that can be in flight for days. By integrating the compression algorithm, the FOSS system can continue gathering data, even on longer flights.

Fiechtner, Kaitlyn↗

NASA NTRS1984

Practical aspects of modeling aircraft dynamics from flight data

The purpose of parameter estimation, a subset of system identification, is to estimate the coefficients (such as stability and control derivatives) of the aircraft differential equations of motion from sampled measured dynamic responses. In the past, the primary reason for estimating stability and control derivatives from flight tests was to make comparisons with wind tunnel estimates. As aircraft became more complex, and as flight envelopes were expanded to include flight regimes that were not well understood, new requirements for the derivative estimates evolved. For many years, the flight determined derivatives were used in simulations to aid in flight planning and in pilot training. The simulations were particularly important in research flight test programs in which an envelope expansion into new flight regimes was required. Parameter estimation techniques for estimating stability and control derivatives from flight data became more sophisticated to support the flight test programs. As knowledge of these new flight regimes increased, more complex aircraft were flown. Much of this increased complexity was in sophisticated flight control systems. The design and refinement of the control system required higher fidelity simulations than were previously required.

Iliff, K. W.↗

NASA NTRSDate not supplied

Usability of Pre-Flight Planning Interfaces for Supplemental Data Service Provider Tools to Support Uncrewed Aircraft System Traffic Management

Small uncrewed aircraft systems (sUASs) operate in low-altitude, uncontrolled airspace – where support services for their operators (UASOs) are not currently provided. NASA’s System-Wide Safety (SWS) project is identifying the potential risks and hazards to sUAS operations to provide, inform, and improve the designs of In-time Aviation Safety Management Systems (IASMS). The IASMS will include a suite of data-driven tools that compile and analyze data collected from aviation systems and environmental sources to predict hazards, and provide information to allow operators to mitigate these risks (Young et al., 2020). These risk and hazard services can be run and displayed to operators on graphical user interfaces (GUIs), as they relate to a vehicle(s)’ route of flight. These interfaces offer both a means to present hazard service output and offer an opportunity to test user understanding of the information, user decision making, and the best ways to present such data to an operator. Based on these future technologies and intended missions, it is important to investigate interface requirements and evaluate how operators might use these tools. Presenting salient and meaningful risk assessment information to operators is necessary to increase situation awareness and ultimately safety. Building on previous research (Feldman et al., 2022), a usability study comparing two GUIs was conducted to explore how individuals interacted with different styles of information displays. A series of pre-flight hazard and risk-assessment tasks were developed to evaluate participant performance using the Supplemental Data Service Provider Consolidated Dashboard and the Human Automation Team Interface System interfaces. Participants were trained to use both GUIs and their performance was analysed across different scenarios involving multiple sUASs. Performance on simple tasks and the System Usability Scale scores were reported by Feldman et al., 2023. Additional analyses and evaluations on more complex tasks (e.g., risk assessment, prioritization), workload and response times are examined in this paper.

sUAV interfaces↗

NASA NTRSDate not supplied

Usability of Pre-flight Planning Interfaces for Supplemental Data Service Provider Tools to Support Uncrewed Aircraft System Traffic Management

sUAV interfaces↗