Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Lessons learned”

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 811 records · Page 45
All sourcesNASA NTRSDOE OSTI
NASA NTRS1983

Shuttle Performance: Lessons Learned, part 1

Beginning with the first orbital flight of the Space Shuttle, a great wealth of flight data became available to the aerospace community. These data were immediately subjected to analyses by several different groups with different viewpoints and motivations. The results were collected and presented in several papers in the subject areas of ascent and entry aerodynaics; guidance, navigation, and control; aerothermal environment prediction; thermal protection systems; and measurement techniques.

James P Arrington↗
NASA NTRS1983

Space Shuttle Orbiter Venting: Lessons Learned

The orbiter vent system provides dedicated vent areas to permit the gases trapped inside the vehicle to escape during accent. The same vent system also repressurizes the vehicle during entry. The vent system is one of six systems that constitutes the purge, vent and drain subsystem. The orbiter active vent system has been very adaptable to the changing requirements that have occurred during the development of the Space Shuttle orbiter. Good correlation has been obtained between predicted and measured compartment pressures during the orbital flight test (OFT) program. An investigation of the flight data showed that the difference between preflight prediction and the measured values were primarily due to the difference between the baseline external pressures, which was based on subscale wind tunnel test data, and the actual vehicle local external pressures measured during the flight. The current predictions are based on flight derived vent port pressure coefficients since the wind tunnel data does not adequately define the orbiter ascent pressure environment.

H S Lutfi↗
NASA NTRS1983

Explanation of the hypersonic longitudinal stability problem: Lessons learned

Inviscid and viscous CFD codes have been applied to a modified Space Shuttle orbiter geometry to investigate differences between preflight aerodynamic predictions and aerodynamic data from hypersonic reentry flight. Flow field solutions were obtained for wind tunnel conditions and flight conditions to assess Mach number, real-gas, and viscous effects on the reentry aerodynamics of the orbiter. Based on the CFD studies, a methodology model has been developed to (1) extrapolate wind tunnel data to flight conditions and (2) calculate a DCM for use with the Aerodynamic Design Data Book. Comparisons are made with selected flight data. Results of the study indicate that the differences between flight and pre-STS-1 predictions of hypersonic pitching moment are primarily due the to Mach number and real-gas effects.

Griffith, B. J.↗
NASA NTRS1983

Aerodynamic coefficient identification package dynamic data accuracy determinations: Lessons learned

The errors in the dynamic data output from the Aerodynamic Coefficient Identification Packages (ACIP) flown on Shuttle flights 1, 3, 4, and 5 were determined using the output from the Inertial Measurement Units (IMU). A weighted least-squares batch algorithm was empolyed. Using an averaging technique, signal detection was enhanced; this allowed improved calibration solutions. Global errors as large as 0.04 deg/sec for the ACIP gyros, 30 mg for linear accelerometers, and 0.5 deg/sec squared in the angular accelerometer channels were detected and removed with a combination is bias, scale factor, misalignment, and g-sensitive calibration constants. No attempt was made to minimize local ACIP dynamic data deviations representing sensed high-frequency vibration or instrument noise. Resulting 1sigma calibrated ACIP global accuracies were within 0.003 eg/sec, 1.0 mg, and 0.05 deg/sec squared for the gyros, linear accelerometers, and angular accelerometers, respectively.

Heck, M. L.↗
NASA NTRS1983

Shuttle Performance: Lessons Learned, Part 2

Several areas of Space Shuttle technology were addressed including aerothermal environment, thermal protection, measurement and analysis, Shuttle carrier aerodynamics, entry analysis of the STS-3, and an overview of each section.

Arrington, J. P.↗
NASA NTRS1983

Orbiter Entry Heating Lessons Learned from Development Flight Test Program

The Space Shuttle orbiter's thermal protection system (TPS), designed mainly on the basis of wind tunnel test data, has successfully completed its design, development, and flight test program. The flight test data provide an exceptional opportunity to evaluate the use of wind tunnel test data for the design of TPS for reentry vehicles. Comparisons of flight test data against wind tunnel data used to design the orbiter's TPS were developed. These flight data, though still in the preliminary analysis phases, generally support the use of wind tunnel test data in the design of TPS for hypersonic reentry vehicles.

Haney, J. W., Jr.↗
NASA NTRS1984

Lessons learned during the first year of the TDRSS

The Tracking and Data Relay Satellite System (TDRSS) is the National Aeronautics and Space Administration's (NASA) newest capability for tracking and communicating with NASA's low-earth orbiting scientific and operational satellites. This support will eventually be provided through three identical satellites in geosynchronous orbit. They will relay data through a single ground station located in New Mexico. This paper discusses both the overall TDRSS concept and NASA's experience to date with the first of the three relay satellites on station.

Aller, R. O.↗
NASA NTRS1985

Software management tools: Lessons learned from use

Experience in inserting software project planning tools into more than 100 projects producing mission critical software are discussed. The problems the software project manager faces are listed along with methods and tools available to handle them. Experience is reported with the Project Manager's Workstation (PMW) and the SoftCost-R cost estimating package. Finally, the results of a survey, which looked at what could be done in the future to overcome the problems experienced and build a set of truly useful tools, are presented.

Reifer, D. J.↗
NASA NTRS1986

Some lessons learned with wind tunnels

An historical evaluation is made of the most significant developments in the use of wind tunnels for the development and analysis of missiles and aircraft since the 1940s. In addition to being instrumental in the discovery of unknown aerodynamic, aeroelastic and aerothermodynamic phenomena, wind tunnels have helped in the explanation of numerous effects, the development of new configurations and systems, and the furnishing of critical initial performance evaluations for a broad spectrum of aircraft and missiles. Attention is given to low speed planform tests, body-wing-tail studies, variable sweep wing investigations, transonic characteristics and problems, supersonic trim drag, and supersonic pitch-up, area ruling, and inlet effects.

Spearman, M. L.↗
NASA NTRS1987

Shuttle middeck fluid transfer experiment: Lessons learned

This presentation is based on the experience gained from having integrated and flown a shuttle middeck experiment. The experiment, which demonstrated filling, expulsion, and fluid behavior of a liquid storage system under low-gravity conditions, is briefly described. The advantages and disadvantages of middeck payloads compared to other shuttle payload provisions are discussed. A general approach to the integration process is described. The requirements for the shuttle interfaces--such as structures, pressurized systems, materials, instrumentation, and electrical power--are defined and the approach that was used to satisfy these requirements is presented. Currently the middeck experiment is being used as a test bed for the development of various space fluid system components.

Tegart, James↗
NASA NTRS1986

Lessons learned from the DC-10 carbon-epoxy rudder program

With the DC-10 carbon-epoxy rudder, the Douglas Aircraft Company achieved one of the greatest percentage weight savings associated with composite structures. Apart from minor damage from lightning strikes, the 15 rudders put into service have experienced virtually trouble-free operation for about a decade. This paper explains why a multirib, postbuckled skin design was used for the DC-10 composite rudder, how it was justified, and how it would have compared with more conventional sandwich design concepts. Special attention is devoted to the reasons why, for such postbuckled designs, it is better to allow the skin to wrinkle and unload itself than to reinforce it and make it resist buckling until some higher load level is attained. With minor changes in the manufacturing technique, this design concept is ideal for the control surfaces on many aircraft. The paper includes suggestions on how to make even better composite control surfaces in the future.

Hart-Smith, L. J.↗
NASA NTRS1987

Fallible humans and vulnerable systems - Lessons learned from aviation

It is suggested that the problems being experienced in complex automatic systems are essentially due to the failure of information management and communication. The failure covers the entire spectrum: display devices and techniques, coding information so as to reduce human error, and information economy, i.e., resisting the temptation to bombard the operator with unlimited information simply because the system possesses the capability to do so. Since there has been great progress in hardware engineering, it is suggested that further attention is needed in the 'soft' side of systems. The approach should focus on (1) preventing human cognitive slips and (2) making the systems less vulnerable to such slips when they do occur. Most of the examples are taken from studies of cockpit automation.

Wiener, Earl L.↗
NASA NTRS1988

Lessons learned in ground processing scientific and applications payloads at Kennedy Space Center

The payload ground processing of experiments which flew on the Shuttle is examined, including studies of atmosphere and earth observation, life science, advance technology, materials science, plasma physics, astrophysics and solar physics, astronomy, navigation and communication, and fluid mechanics. The process of designing and development payloads, the integration of instruments, carrier interface verification, and late servicing at the launch pad are discussed. The problems of cost, red tape, contamination, safety, and propriety protection are considered.

Elfrey, Priscilla↗
NASA NTRS1989

Lessons learned in the transition to ADA from FORTRAN at NASA/Goddard

A case study was done at Goddard Space Flight Center, in which two dynamics satellite simulators are developed from the same requirements, one in Ada and the other in FORTRAN. The purpose of the research was to find out how well the prescriptive Ada development model worked to develop the Ada simulator. The FORTRAN simulator development, as well as past FORTRAN developments, provided a baseline for comparison. Since this was the first simulator developed here, the prescriptive Ada development model had many similarities to the usual FORTRAN development model. However, it was modified to include longer design and shorter testing phases, which is generally expected with Ada development. One surprising result was that the percentage of time the Ada project spent in the various development activities was very similar to the percentage of time spent in these activities when doing a FORTRAN project. Another surprising finding was the difficulty the Ada team had with unit testing as well as with integration. In retrospect it is realized that adding additional steps to the design phase, such as an abstract data type analysis, and certain guidelines to the implementation phase, such as to use primarily library units and nest sparingly, would have made development much easier.

Brophy, Carolyn Elizabeth↗
NASA NTRS1989

Lessons learned in the transition to Ada from FORTRAN at NASA/Goddard

Two dynamics satellite simulators are developed from the same requirements, one in Ada and the other in FORTRAN. The purpose of the research was to find out how well the prescriptive Ada development model worked to develop the Ada simulator. The FORTRAN simulator development, as well as past FORTRAN developments, provided a baseline for comparison. Since this was the first simulator developed, the prescriptive Ada development model had many similarities to the usual FORTRAN development model. However, it was modified to include longer design and shorter testing phases, which is generally expected with Ada developments. One result was that the percentage of time the Ada project spent in the various development activities was very similar to the percentage of time spent in these activities when doing a FORTRAN project. Another finding was the difficulty the Ada team had with unit testing as well as with integration. It was realized that adding additional steps to the design phase, such as an abstract data type analysis, and certain guidelines to the implementation phase, such as to use primarily library units and nest sparingly, would have made development easier. These are among the recommendations made to be incorporated in a new Ada development model next time.

Brophy, Carolyn Elizabeth↗
NASA NTRS1989

Development of the XV-15 tiltrotor research aircraft - Lessons learned

The initial ground rules that guided the decision process during the initial stages of the XV-15 tiltrotor aircraft development are reviewed and reevaluated. A full flight-envelope nonlinear simulation mathematical model is outlined, along with the advantages of a multiaircraft program. Direct involvement of government engineers in all aspects of the program is considered to be beneficial, while the ejection-seat test requirement is not. Utilization of existing components - a rotor, transmissions, and engines - is analyzed, and emphasis is placed on integrated system test plans responsible for producing two reliable aircraft through a complete checkout of the aircraft subsystems before the start of the fligth program. Wind-tunnel and fatigue test requirements are presented, and the decision to go with an all mechanical control system design is addressed.

Schroers, Laurel G.↗
NASA NTRS1986

An expert system prototype for aiding in the development of software functional requirements for NASA Goddard's command management system: A case study and lessons learned

At NASA Goddard, the role of the command management system (CMS) is to transform general requests for spacecraft opeerations into detailed operational plans to be uplinked to the spacecraft. The CMS is part of the NASA Data System which entails the downlink of science and engineering data from NASA near-earth satellites to the user, and the uplink of command and control data to the spacecraft. Presently, it takes one to three years, with meetings once or twice a week, to determine functional requirements for CMS software design. As an alternative approach to the present technique of developing CMS software functional requirements, an expert system prototype was developed to aid in this function. Specifically, the knowledge base was formulated through interactions with domain experts, and was then linked to an existing expert system application generator called 'Knowledge Engineering System (Version 1.3).' Knowledge base development focused on four major steps: (1) develop the problem-oriented attribute hierachy; (2) determine the knowledge management approach; (3) encode the knowledge base; and (4) validate, test, certify, and evaluate the knowledge base and the expert system prototype as a whole. Backcasting was accomplished for validating and testing the expert system prototype. Knowledge refinement, evaluation, and implementation procedures of the expert system prototype were then transacted.

Liebowitz, Jay↗