Engineering Papers⌕ Search

SEARCH · Engineering Papers

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.

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

At least 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRS1995

Viscous-flow analysis of a subsonic transport aircraft high-lift system and correlation with flight data

High-lift system aerodynamics has been gaining attention in recent years. In an effort to improve aircraft performance, comprehensive studies of multi-element airfoil systems are being undertaken in wind-tunnel and flight experiments. Recent developments in Computational Fluid Dynamics (CFD) offer a relatively inexpensive alternative for studying complex viscous flows by numerically solving the Navier-Stokes (N-S) equations. Current limitations in computer resources restrict practical high-lift N-S computations to two dimensions, but CFD predictions can yield tremendous insight into flow structure, interactions between airfoil elements, and effects of changes in airfoil geometry or free-stream conditions. These codes are very accurate when compared to strictly 2D data provided by wind-tunnel testing, as will be shown here. Yet, additional challenges must be faced in the analysis of a production aircraft wing section, such as that of the NASA Langley Transport Systems Research Vehicle (TSRV). A primary issue is the sweep theory used to correlate 2D predictions with 3D flight results, accounting for sweep, taper, and finite wing effects. Other computational issues addressed here include the effects of surface roughness of the geometry, cove shape modeling, grid topology, and transition specification. The sensitivity of the flow to changing free-stream conditions is investigated. In addition, the effects of Gurney flaps on the aerodynamic characteristics of the airfoil system are predicted.

Potter, R. C.↗
NASA NTRS1993

The rhesus measurement system: A new instrument for space research

The Rhesus Research Facility (RRF) is a research environment designed to study the effects of microgravity using rhesus primates as human surrogates. This experimental model allows investigators to study numerous aspects of microgravity exposure without compromising crew member activities. Currently, the RRF is slated for two missions to collect its data, the first mission is SLS-3, due to fly in late 1995. The RRF is a joint effort between the United States and France. The science and hardware portions of the project are being shared between the National Aeronautics and Space Administration (NASA) and France's Centre National D'Etudes Spatiales (CNES). The RRF is composed of many different subsystems in order to acquire data, provide life support, environmental enrichment, computer facilities and measurement capabilities for two rhesus primates aboard a nominal sixteen day mission. One of these subsystems is the Rhesus Measurement System (RMS). The RMS is designed to obtain in-flight physiological measurements from sensors interfaced with the subject. The RMS will acquire, preprocess, and transfer the physiologic data to the Flight Data System (FDS) for relay to the ground during flight. The measurements which will be taken by the RMS during the first flight will be respiration, measured at two different sites; electromyogram (EMG) at three different sites; electroencephalogram (EEG); electrocardiogram (ECG); and body temperature. These measurements taken by the RMS will assist the research team in meeting the science objectives of the RRF project.

Schonfeld, Julie E.↗
NASA NTRS1973

Development of AIFTDS-4000, a flight-qualified, flexible, high-speed data acquisition system

The NASA flight research center has developed a prototype data acquisition system which integrates an airborne computer with a high-speed pulse code modulation system. The design of the airborne integrated flight test data system (AIFTDS) is the result of experience with airborne pulse code modulation data systems. The AIFTDS-4000 has proved the premise on which it was designed: that the needs and requirements of data acquisition system users can be integrated to produce a highly flexible system that will be more useful than existing systems.

Borek, R. W.↗
NASA NTRS1977

Description of a Computer Program Written for Approach and Landing Test Post Flight Data Extraction of Proximity Separation Aerodynamic Coefficients and Aerodynamic Data Base Verification

A computer program written to calculate the proximity aerodynamic force and moment coefficients of the Orbiter/Shuttle Carrier Aircraft (SCA) vehicles based on flight instrumentation is described. The ground reduced aerodynamic coefficients and instrumentation errors (GRACIE) program was developed as a tool to aid in flight test verification of the Orbiter/SCA separation aerodynamic data base. The program calculates the force and moment coefficients of each vehicle in proximity to the other, using the load measurement system data, flight instrumentation data and the vehicle mass properties. The uncertainty in each coefficient is determined, based on the quoted instrumentation accuracies. A subroutine manipulates the Orbiter/747 Carrier Separation Aerodynamic Data Book to calculate a comparable set of predicted coefficients for comparison to the calculated flight test data.

Homan, D. J.↗
NASA NTRS2008

Advancing NASA's Satellite Control Capabilities: More than Just Better Technology

This viewgraph presentation reviews the work of the Goddard Mission Services Evolution Center (GMSEC) in the development of the NASA's satellite control capabilities. The purpose of the presentation is to provide a quick overview of NASA's Goddard Space Flight Center and our approach to coordinating the ground system resources and development activities across many different missions. NASA Goddard's work in developing and managing the current and future space exploration missions is highlighted. The GMSEC, was established to to coordinate ground and flight data systems development and services, to create a new standard ground system for many missions and to reflect the reality that business reengineering and mindset were just as important.

Smith, Danford↗
NASA NTRS1988

The evolution of AAOE observed constituents with the polar vortex

One of the difficulties in determining constituent trends from the ER-2 flight data is the large amount of day to day variability generated by the motion of the polar vortex. To reduce this variability, the observations have been transformed into the conservative (Lagrangian) reference frames consisting of the coordinate pairs, potential temperature (PT) and potential vorticity (PV), or PT and N2O. The requirement of only two independent coordinates rests on the assumption that constituent distributions and their chemical processes are nearly zonal in that coordinate system. Flight data is used everywhere for these transformation except for potential vorticity. Potential vorticity is determined from level flight segments, and NMC PV values during flight dives and takeoffs are combined with flight data in a smooth fashion.

Schoeberl, Mark R.↗
NASA NTRS2000

An Evaluation Technique for an F/A-18 Aircraft Loads Model Using F/A-18 Systems Research Aircraft Flight Data

A limited evaluation of the F/A-18 baseline loads model was performed on the Systems Research Aircraft at NASA Dryden Flight Research Center (Edwards, California). Boeing developed the F/A-18 loads model using a linear aeroelastic analysis in conjunction with a flight simulator to determine loads at discrete locations on the aircraft. This experiment was designed so that analysis of doublets could be used to establish aircraft aerodynamic and loads response at 20 flight conditions. Instrumentation on the right outboard leading edge flap, left aileron, and left stabilator measured the hinge moment so that comparisons could be made between in-flight-measured hinge moments and loads model-predicted values at these locations. Comparisons showed that the difference between the loads model-predicted and in-flight-measured hinge moments was up to 130 percent of the flight limit load. A stepwise regression technique was used to determine new loads derivatives. These derivatives were placed in the loads model, which reduced the error to within 10 percent of the flight limit load. This paper discusses the flight test methodology, a process for determining loads coefficients, and the direct comparisons of predicted and measured hinge moments and loads coefficients.

Olney, Candida D.↗
NASA NTRS1973

Ground and flight experience with a strapdown inertial measuring unit and a general purpose airborne digital computer

Ground and flight tests were conducted to investigate the problems associated with using a strapdown inertial flight data system. The objectives of this investigation were to develop a three axis inertial attitude reference system, to evaluate a self-alignment technique, and to examine the problem of time-sharing a general purpose computer for the several tasks required of it. The performance of the strapdown platform/computer system that was developed was sufficiently accurate for the tasks attempted. For flights on the order of 45 minutes duration, attitude angle errors of + or -.035 radian (+ or -2 deg) in all axes were observed. Laboratory tests of the self-alignment technique gave accuracies of + or -.00075 radian in pitch and roll axes and + or -0.0045 radian in the yaw axis. Self-alignment flight results were inconsistent, since a stable solution was not obtained on windy days because of aircraft rocking motions.

Wolf, T. D.↗
NASA NTRS1988

Assessment of the hydrogen external tank pressure decay anomaly on Space Transportation System (STS) 51-L

Following the Challenger tragedy, an evaluation of the integrated main propulsion system flight data revealed a premature decay in the hydrogen external tank ullage pressure. A reconstruction of predicted ullage pressure versus time indicated an inconsistency between predicted and measured ullage pressure starting at approximately 65.5 seconds into the flight and reaching a maximum value between 72 and 72.9 seconds. This discrepancy could have been caused by a hydrogen gas leak or by a liquied hydrogen leak that occurred either in the pressurization system or in the external tank. The corresponding leak rates over the time interval from 65.5 to 72.9 seconds were estimated to range from 0.28 kg/s (0.62 lbm/s) + or - 41 percent to between 0.43 and 0.51kg/s (0.94 and 1.12lbs/s) + or - 1 percent for a gas leak and from 72.9 kg/s (160.5 lbs/s) + or - 41 percent to between 111.6 and 133.2 kg/s (245.8 and 293.3 lbs/s) + or - 1 percent for a liquid leak. No speculation is made to ascertain whether the leak is liquid or gas, as this cannot be determined from the analysis performed. Four structural failures in the hydrogen external tank were considered to explain the leak rates. A break in the 5-cm (2 in) pressurization line, in the 13-cm (5 in) vent line, or in the 43-cm (17 in) feedline is not likely. A break in the 10-cm (4 in) recirculation line with a larger structural failure occurring in the 72 to 73-second time period, the time of the visibly identified premature pressure decay, does seem plausible and the most likely of the four modes considered. These modes are not all-inclusive and do not preclude the possibility of a leak elsewhere in the tank.

Buckley, Theresa M.↗
NASA NTRS1976

Titan/Centaur D-1T TC-3 Viking B Flight Data Report

Titan/Centaur TC-3 was launched from the Eastern Test Range, Complex 41, at 02:34 PM EDT on Tuesday, September 9, 1975. This was the third operational flight of the newest NASA unmanned launch vehicle. The spacecraft was the Viking B, the second of two orbiting and landing missions to Mars planned for the 1975 Martian launch opportunity. The objective of the launch phase of the mission, to inject the Viking spacecraft onto the planned transfer orbit to Mars, was successfully accomplished. A review of the launch vehicle system flight data is presented.

Source record↗
NASA NTRS1976

Titian/Centaur D-1TTC-4 Viking A flight data report

Titan/Centaur TC-4 was launched from the Eastern Test Range, Complex 41, at 05:22 PM EDT on Wednesday, August 20, 1975. This was the second operational flight of the newest NASA unmanned launch vehicle. The spacecraft was the Viking A, the first of two orbiting and landing missions to Mars planned for the 1975 Martian launch opportunity. The objective of the launch phase of the mission, to inject the Viking spacecraft onto the planned transfer orbit to Mars, was successfully accomplished. This report presents a review of the launch vehicle system flight data.

Source record↗
NASA NTRS1993

Space Station Freedom (SSF) Data Management System (DMS) performance model data base

The purpose of this document was originally to be a working document summarizing Space Station Freedom (SSF) Data Management System (DMS) hardware and software design, configuration, performance and estimated loading data from a myriad of source documents such that the parameters provided could be used to build a dynamic performance model of the DMS. The document is published at this time as a close-out of the DMS performance modeling effort resulting from the Clinton Administration mandated Space Station Redesign. The DMS as documented in this report is no longer a part of the redesigned Space Station. The performance modeling effort was a joint undertaking between the National Aeronautics and Space Administration (NASA) Johnson Space Center (JSC) Flight Data Systems Division (FDSD) and the NASA Ames Research Center (ARC) Spacecraft Data Systems Research Branch. The scope of this document is limited to the DMS core network through the Man Tended Configuration (MTC) as it existed prior to the 1993 Clinton Administration mandated Space Station Redesign. Data is provided for the Standard Data Processors (SDP's), Multiplexer/Demultiplexers (MDM's) and Mass Storage Units (MSU's). Planned future releases would have added the additional hardware and software descriptions needed to describe the complete DMS. Performance and loading data through the Permanent Manned Configuration (PMC) was to have been included as it became available. No future releases of this document are presently planned pending completion of the present Space Station Redesign activities and task reassessment.

Stovall, John R.↗
NASA NTRS1991

NASA/Ames Research Center DC-8 data system

In-flight facility data acquisition, distribution, and recording on the NASA Ames Research Center (ARC) DC-8 are performed by the Data Acquisition and Distribution System (DADS). Navigational and environmental data collected by the DADS are converted to engineering units and distributed real-time to investigator stations once per second. Selected engineering units data are printed and displayed on closed circuit television monitors throughout flights. An in-flight graphical display of the DC-8 flight track (with barbs indicating wind direction and magnitude) has recently been added to the DADS capabilities. Logging of data run starts/stops and commentary from the mission director are also provided. All data are recorded to hard disk in-flight and archived to tape medium post-flight. Post-flight, hard copies of the track map and mission director's log are created by the DADS. The DADS is a distributed system consisting of a data subsystem, an Avionic Serial Data-to-VMEbus (ASD2VME) subsystem, and a host subsystem. Each subsystem has a dedicated central processing unit (CPU) and is capable of stand-alone operation. All three subsystems are housed in a single 20-slot VME chassis and communicate with each other over the VMEbus. The data and host subsystems are briefly discussed, and the DC-8 DADS internal configuration and system block diagram are presented.

Cherniss, S. C.↗
NASA NTRS1984

Data management

The following tasks were prioritized: software acquisition management plan; space station flight data system architectural study; space station user data system interface; automation of software development process; automation of software testing; distributed data base management; ADA (automated data acquisition) evaluation and transition and planning; network operating system software; fault tolerant computer validation methodology for onboard data management system; systems integration; artificial intelligence/expert systems; space station data network concept; space station standard interface protocols; space station data networks systems; integrated software development facility; and language trade studies.

Love, G.↗
NASA NTRS1988

Fast Data Acquisition For Mass Spectrometer

New equipment has speed and capacity to process time-of-flight data. System relies on fast, compact waveform digitizer with 32-k memory coupled to personal computer. With digitizer, system captures all mass peaks on each 25- to 35-microseconds cycle of spectrometer.

Lincoln, K. A.↗
NASA NTRS1987

Spacecraft on-board SAR processing technology

This paper provides an assessment of the on-board SAR processing technology for Eos-type missions. The proposed Eos SAR sensor and flight data system are introduced, and the SAR processing requirements are described. The SAR on-board SAR processor architecture selection is discussed, and a baseline processor architecture using a frequency-domain processor for range correlation and a modular fault-tolerant VLSI time-domain parallel array for azimuth correlation are described. The mass storage and VLSI technologies needed for implementing the proposed SAR processing are assessed. It is shown that acceptable processor power and mass characteristics should be feasible for Eos-type applications. A proposed development strategy for the on-board SAR processor is presented.

Liu, K. Y.↗
NASA NTRS1990

Perspectives on NASA flight software development - Apollo, Shuttle, Space Station

Flight data systems' software development is chronicled for the period encompassing NASA's Apollo, Space Shuttle, and (ongoing) Space Station Freedom programs, with attention to the methodologies and 'development tools' employed in each case and their mutual relationships. A dominant concern in all three programs has been the accommodation of software change; it has also been noted that any such long-term program carries the additional challenge of identifying which elements of its software-related 'institutional memory' are most critical, in order to preclude their loss through the retirement, promotion, or transfer of its 'last expert'.

Garman, John R.↗
NASA NTRS1993

Mongoose: Creation of a Rad-Hard MIPS R3000

This paper describes the development of a 32 Bit, full MIPS R3000 code-compatible Rad-Hard CPU, code named Mongoose. Mongoose progressed from contract award, through the design cycle, to operational silicon in 12 months to meet a space mission for NASA. The goal was the creation of a fully static device capable of operation to the maximum Mil-883 derated speed, worst-case post-rad exposure with full operational integrity. This included consideration of features for functional enhancements relating to mission compatibility and removal of commercial practices not supported by Rad-Hard technology. 'Mongoose' developed from an evolution of LSI Logic's MIPS-I embedded processor, LR33000, code named Cobra, to its Rad-Hard 'equivalent', Mongoose. The term 'equivalent' is used to infer that the core of the processor is functionally identical, allowing the same use and optimizations of the MIPS-I Instruction Set software tool suite for compilation, software program trace, etc. This activity was started in September of 1991 under a contract from NASA-Goddard Space Flight Center (GSFC)-Flight Data Systems. The approach affected a teaming of NASA-GSFC for program development, LSI Logic for system and ASIC design coupled with the Rad-Hard process technology, and Harris (GASD) for Rad-Hard microprocessor design expertise. The program culminated with the generation of Rad-Hard Mongoose prototypes one year later.

Lincoln, Dan↗