SEARCH · Search NASA

Results for “flight rules.”

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 451 records · Page 25

All sources NASA NTRS DOE OSTI

NASA NTRS2014

Combustion Stability Assessments of the Black Brant Solid Rocket Motor

The Black Brant variation of the Standard Brant developed in the 1960's has been a workhorse motor of the NASA Sounding Rocket Project Office (SRPO) since the 1970's. In March 2012, the Black Brant Mk1 used on mission 36.277 experienced combustion instability during a flight at White Sands Missile Range, the third event in the last four years, the first occurring in November, 2009, the second in April 2010. After the 2010 event the program has been increasing the motor's throat diameter post-delivery with the goal of lowering the chamber pressure and increasing the margin against combustion instability. During the most recent combustion instability event, the vibrations exceeded the qualification levels for the Flight Termination System. The present study utilizes data generated from T-burner testing of multiple Black Brant propellants at the Naval Air Warfare Center at China Lake, to improve the combustion stability predictions for the Black Brant Mk1 and to generate new predictions for the Mk2. Three unique one dimensional (1-D) stability models were generated, representing distinct Black Brant flights, two of which experienced instabilities. The individual models allowed for comparison of stability characteristics between various nozzle configurations. A long standing "rule of thumb" states that increased stability margin is gained by increasing the throat diameter. In contradiction to this experience based rule, the analysis shows that little or no margin is gained from a larger throat diameter. The present analysis demonstrates competing effects resulting from an increased throat diameter accompanying a large response function. As is expected, more acoustic energy was expelled through the nozzle, but conversely more acoustic energy was generated due to larger gas velocities near the propellant surfaces.

Fischbach, Sean↗

NASA NTRS2014

Weather Avoidance Guidelines for NASA Global Hawk High-Altitude UAS

NASA operates two Global Hawk unmanned aircraft systems for Earth Science research projects. In particular, they are used in the Hurricane and Severe Storm Sentinel (HS3) project during 2012, 2013, and 2014 to take measurements from the environment around tropical cyclones, and from directly above tropical cyclones. There is concern that strict adherence to the weather avoidance rules used in 2012 may sacrifice the ability to observe important science targets. We have proposed modifications to these weather avoidance rules that we believe will improve the ability to observe science targets without compromising aircraft safety. The previous guidelines, used in 2012, specified: Do not approach thunderstorms within 25 nm during flight at FL500 or below. When flying above FL500: Do not approach reported lightning within 25NM in areas where cloud tops are reported at FL500 or higher. Aircraft should maintain at least 10000 ft vertical separation from reported lightning if cloud tops are below FL500. No over-flight of cumulus tops higher than FL500. No flight into forecast or reported icing conditions. No flight into forecast or reported moderate or severe turbulence Based on past experience with high-altitude flights over tropical cyclones, we have recommended changing this guidance to: Do not approach thunderstorms within 25 nm during flight at FL500 or below. Aircraft should maintain at least 5000 ft vertical separation from significant convective cloud tops except: a) When cloud tops above FL500: In the event of reported significant lightning activity or indicators of significant overshooting tops, do not approach within 10-25 nm, depending on pilot discretion and advice from Mission Scientist. b) When cloud tops are below FL500, maintain 10000 ft separation from reported significant lightning or indicators of significant overshooting tops. No flight into forecasted or reported icing conditions. No flight into forecasted or reported moderate or severe turbulence The key changes have to do with overflight of high convective cloud tops and those producing lightning. Experience shows that most tropical oceanic convection (including that in tropical cyclones) is relatively gentle even if the cloud tops are quite high, and can be safely overflown. Exceptions are convective elements producing elevated lightning flash rates (more than just the occasional flash, which would trigger avoidance under the previous rules) and significant overshooting cloud tops.

Cecil, Daniel J.↗

NASA NTRS1977

F-8 supercritical wing flight pressure, Boundary layer, and wake measurements and comparisons with wind tunnel data

Data for speeds from Mach 0.50 to Mach 0.99 are presented for configurations with and without fuselage area-rule additions, with and without leading-edge vortex generators, and with and without boundary-layer trips on the wing. The wing pressure coefficients are tabulated. Comparisons between the airplane and model data show that higher second velocity peaks occurred on the airplane wing than on the model wing. The differences were attributed to wind tunnel wall interference effects that caused too much rear camber to be designed into the wing. Optimum flow conditions on the outboard wing section occurred at Mach 0.98 at an angle of attack near 4 deg. The measured differences in section drag with and without boundary-layer trips on the wing suggested that a region of laminar flow existed on the outboard wing without trips.

Montoya, L. C.↗

NASA NTRS1999

A Cooperative Human-Adaptive Traffic Simulation (CHATS)

NASA is considering the development of a Cooperative Human-Adaptive Traffic Simulation (CHATS), to examine and evaluate performance of the National Airspace System (NAS) as the aviation community moves toward free flight. CHATS will be specifically oriented toward simulating strategic decision-making by airspace users and by the service provider s traffic management personnel, within the context of different airspace and rules assumptions. It will use human teams to represent these interests and make decisions, and will rely on computer modeling and simulation to calculate the impacts of these decisions. The simulation objectives will be to examine: 1. evolution of airspace users and the service provider s strategies, through adaptation to new operational environments; 2. air carriers competitive and cooperative behavior; 3. expected benefits to airspace users and the service provider as compared to the current NAS; 4. operational limitations of free flight concepts due to congestion and safety concerns. This paper describes an operational concept for CHATS, and presents a high-level functional design which would utilize a combination of existing and new models and simulation capabilities.

Phillips, Charles T.↗

NASA NTRS2012

Virtual Machine Language 2.1

VML (Virtual Machine Language) is an advanced computing environment that allows spacecraft to operate using mechanisms ranging from simple, time-oriented sequencing to advanced, multicomponent reactive systems. VML has developed in four evolutionary stages. VML 0 is a core execution capability providing multi-threaded command execution, integer data types, and rudimentary branching. VML 1 added named parameterized procedures, extensive polymorphism, data typing, branching, looping issuance of commands using run-time parameters, and named global variables. VML 2 added for loops, data verification, telemetry reaction, and an open flight adaptation architecture. VML 2.1 contains major advances in control flow capabilities for executable state machines. On the resource requirements front, VML 2.1 features a reduced memory footprint in order to fit more capability into modestly sized flight processors, and endian-neutral data access for compatibility with Intel little-endian processors. Sequence packaging has been improved with object-oriented programming constructs and the use of implicit (rather than explicit) time tags on statements. Sequence event detection has been significantly enhanced with multi-variable waiting, which allows a sequence to detect and react to conditions defined by complex expressions with multiple global variables. This multi-variable waiting serves as the basis for implementing parallel rule checking, which in turn, makes possible executable state machines. The new state machine feature in VML 2.1 allows the creation of sophisticated autonomous reactive systems without the need to develop expensive flight software. Users specify named states and transitions, along with the truth conditions required, before taking transitions. Transitions with the same signal name allow separate state machines to coordinate actions: the conditions distributed across all state machines necessary to arm a particular signal are evaluated, and once found true, that signal is raised. The selected signal then causes all identically named transitions in all present state machines to be taken simultaneously. VML 2.1 has relevance to all potential space missions, both manned and unmanned. It was under consideration for use on Orion.

Riedel, Joseph E.↗

NASA NTRS1991

Onboard navigation rendezvous expert system

The Onboard Navigation rendezvous expert system is designed to aid the ground flight controller in monitoring the shuttle onboard navigation system. The system is designed to keep track of the navigation sensors and relative state vectors. In addition, the system also keeps an event log and fills out forms usually handled by the flight controller. This expert system is one of the few rendezvous specific systems being developed for the Mission Control Center. The expert system has been in development for six years. Through these years the system has seen hardware, software, and personnel changes. Initial development was done by the Information Systems Directorate (ISD) and Mission Operations Directorate (MOD) at Johnson Space Center. As of October 1, 1991 the system has been turned over to MOD. The system is completely developed except for some minor adjustments to the user interface. The rule base is in the verification stage with total certification of the system due to be completed by May 1992. Test cases for verification are obtained by saving data used for flight controller integrated simulations. The actual data comes from both the shuttle mission simulator and the Mission Control Center Computer. So far no actual flight data has been available. This paper covers all aspects of the system from the development history to the current hardware, software, and use of the system.

Kocen, Michelle↗

NASA NTRS1976

Choosing reliability level for Shuttle-carried payloads

The paramount importance of high payload reliability is questioned in the light of payload recoverability in Spacelab and Space Shuttle experiments, and cost effectiveness through less stringent reliability requirements backed up by recovery and reflight of the experiment if necessary is considered. Ground rules and parameters for assessing reliability and recoverability in relation to mission cost effectiveness are advanced. Mission success probability (for one or several flights), experiment hardware cost, design reliability, cost of orbiting the experiment, support system reliability, and other relevant parameters are identified and discussed, and graphs of experimental total cost envelope are plotted. It is proposed that reliability and quality assurance standards be weighed against failure costs and penalties in the case of recoverable space systems.

Campbell, J. W.↗

NASA NTRS1998

Next Generation User Support Tools

One of the manually intensive efforts of Hubble Space Telescope (HST) observing is the specification and validation of the detailed proposals for scientists observing with the telescope. In order to meet the operational cost objectives for the Next Generation Space Telescope (NGST), this process needs to be dramatically less time consuming and less costly. We have prototyped a new proposal development system, the Scientist's Expert Assistant (SEA), using a combination of artificial intelligence and user interface techniques to reduce the time and effort involved for both scientists and the telescope operations staff. The Advanced Architectures and Automation Branch of NASA's Goddard Space Flight Center is working with the Space Telescope Science Institute (ST ScI) to explore SEA alternatives. We are testing the usefulness of rule-based expert systems to painlessly guide a scientist to his or her desired observation specification. We are also examining several potential user interface paradigms and exploring data visualization schemes to see which techniques are more intuitive. Our prototypes will be validated using HST's Advanced Camera for Surveys (ACS) instrument (scheduled for installation in 1999) as a live test instrument. Having an operational test-bed will ensure the most realistic feedback possible for the prototyping cycle. In addition, once the NGST instruments are better defined, the SEA will already be a proven platform that simply needs adapting to NGST-specific instruments.

Jones, Jeremy E.↗

NASA NTRS2001

Robust Strategy for Rocket Engine Health Monitoring

Monitoring the health of rocket engine systems is essentially a two-phase process. The acquisition phase involves sensing physical conditions at selected locations, converting physical inputs to electrical signals, conditioning the signals as appropriate to establish scale or filter interference, and recording results in a form that is easy to interpret. The inference phase involves analysis of results from the acquisition phase, comparison of analysis results to established health measures, and assessment of health indications. A variety of analytical tools may be employed in the inference phase of health monitoring. These tools can be separated into three broad categories: statistical, rule based, and model based. Statistical methods can provide excellent comparative measures of engine operating health. They require well-characterized data from an ensemble of "typical" engines, or "golden" data from a specific test assumed to define the operating norm in order to establish reliable comparative measures. Statistical methods are generally suitable for real-time health monitoring because they do not deal with the physical complexities of engine operation. The utility of statistical methods in rocket engine health monitoring is hindered by practical limits on the quantity and quality of available data. This is due to the difficulty and high cost of data acquisition, the limited number of available test engines, and the problem of simulating flight conditions in ground test facilities. In addition, statistical methods incur a penalty for disregarding flow complexity and are therefore limited in their ability to define performance shift causality. Rule based methods infer the health state of the engine system based on comparison of individual measurements or combinations of measurements with defined health norms or rules. This does not mean that rule based methods are necessarily simple. Although binary yes-no health assessment can sometimes be established by relatively simple rules, the causality assignment needed for refined health monitoring often requires an exceptionally complex rule base involving complicated logical maps. Structuring the rule system to be clear and unambiguous can be difficult, and the expert input required to maintain a large logic network and associated rule base can be prohibitive.

Santi, L. Michael↗

NASA NTRS2006

Validation of Ultrasound Imaging to Rule-out Thoracic Trauma on the International Space Station

Introduction: Aboard the International Space Station (ISS) an intra-thoracic injury may be disastrous to the crew member if the diagnosis is missed or even delayed. Pneumothorax and hemothorax commonly seen in trauma patients; the diagnosis is usually confirmed by chest X-ray or computed tomography. In this study, the ability of ultrasound to rule out pneumothorax by the presence "lung sliding" and hemothorax by the absence of pleural fluid was validated. Methods: The research activities were approved by the NASA Johnson Space Center Committee for the Protection of Human Subjects, and the participating crewmembers signed informed consent prior to the activity. ISS crewmembers received 2-hours of "hands on" ultrasound training 8 months prior to the on-orbit ultrasound exam. Baseline ultrasound images of the thorax were acquired on the crewmebers of Increment 8 and 9 prior to launch from Bakonur, Russia. Ultrasound examination of the thorax were performed on crewmembers at 30 day intervals (n=??) throughout their flight. Post flight images were acquired on or about landing day 10. Ultrasound images were acquired using the ISS Health Research Facility ultrasound system and examined by experts on the ground to rule out the presence of pneumothorax and hemothorax. Results: The presence of "lung sliding" which excludes pneumothorax, was seen in all subjects. The absence of pleural fluid, which excludes hemothorax was seen in all subjects. The optimal position between sonographer and patient under microgravity conditions and the amount and type of training for a non-physician crew medical officer for these procedures was also established for this procedure. Conclusion: Ultrasound can be performed on orbit under microgravity condition to rule thoracic trauma, such as pneumothorax and hemothorax.

Hamilton, Douglas R.↗

NASA NTRS2011

Lessons Learned from the Space Shuttle Engine Hydrogen Flow Control Valve Poppet Breakage

The Main Propulsion System (MPS) uses three Flow Control Valves (FCV) to modulate the flow of pressurant hydrogen gas from the Space Shuttle Main Engines (SSME) to the hydrogen External Tank (ET). This maintains pressure in the ullage volume as the liquid level drops, preserving ET structural integrity and assuring the engines receive a sufficient amount of head pressure. On Space Transportation System (STS)-126 (2009), with only a handful of International Space Station (ISS) assembly flights from the end of the Shuttle program, a portion of a single FCV?s poppet head broke off at about a minute and a half after liftoff. The risk of the poppet head failure is that the increased flow area through the FCV could result in excessive gaseous hydrogen flow back to the external tank, which could result in overboard venting of hydrogen ullage pressure. If the hydrogen venting were to occur in first stage (i.e., lower atmosphere), a flammability hazard exists that could lead to catastrophic loss of crew and vehicle. Other failure risks included particle impact damage to MPS downstream hardware. Although the FCV design had been plagued by contamination-related sluggish valve response problems prior to a redesign at STS-80 (1996), contamination was ruled out as the cause of the STS-126 failure. Employing a combination of enhanced hardware inspection and a better understanding of the consequences of a poppet failure, safe flight rationale for subsequent flights (STS-119 and later) was achieved. This paper deals with the technical lessons learned during the investigation and mitigation of this problem at a time when assembly flights were each in the critical path to Space Station success.

Martinez, Hugo E.↗

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 NTRS2021

GA-ASI Final Report and Program Wrap-up for NASA System Integration and Operationalization (SIO)

The NASA SIO demonstration flight of April 3, 2020 represents a successful culmination of 18 months of coordinated effort between GA-ASI, NASA, the FAA, Collins Aerospace, and Honeywell Aerospace to operate a Medium Altitude, Long Endurance (MALE) Unmanned Aircraft System (UAS) safely in the National Airspace System (NAS) using industry leading prototype technologies. The GA-ASI team consisted of technical experts, program managers, engineers, mechanics, flight technicians, flight crews, and numerous other subject matter experts. This final report describes the most significant and potentially impactful aspects of the planning, integration, test, and flight aspects of this effort. GA-ASI successfully integrated the key technologies needed for UAS to fly in the NAS onto our prototype SkyGuardian UAS, which was designed to meet the most stringent airworthiness standards applicable to an aircraft of its size category. A proven Detect and Avoid (DAA) system, developed by GA-ASI and utilizing Honeywell Aerospace technology was integrated onto SkyGuardian for the first time, along with datalink radios from Collins Aerospace that meet the new civil standard for Control and Non-Payload Communication (CNPC) links. GA-ASI also obtained approvals from the FAA and FCC to operate the reconfigured UAS. The SIO demonstration flight represented a commercial aerial surveying operation conducted at medium altitude (>10,000ft above mean sea level). The aircraft’s onboard sensors were used to capture photographic, infrared and radar imagery of public and commercial infrastructure and land, and to subsequently produce the types of data products that would provide business value to potential customers. These survey services would supplement or replace services currently provided by manned airplanes and helicopters, small drones or satellites. A “virtual” mission was also planned, to show what additional survey data could have been captured during the flight if additional sensors had been installed on the aircraft’s external hardpoints. This revision of the final report focuses on information of value to the wider UAS community, and avoids propriety data to facilitate broad dissemination. It also includes a description of GA-ASI’s engagement with the FAA following the SIO flight, which led to the award of an updated Special Airworthiness Certificate in the Experimental Category (SAC-EC) and a Certificate of Waiver or Authorization (COA) allowing operation of the SkyGuardian UAS using its DAA system to satisfy right-of-way rules, instead of a chase plane. The associated operational limitations are described to illustrate the further steps that would be needed to remove those limitations for unhindered commercial operations.

Flight demonstration↗

NASA NTRS1975

Verbal Workload in Distributed Air Traffic Management

The effects of alternative traffic management possibilities on task performance and pilot controller verbal workloads were studied. Two new rule structures - sequencing and advisory - in addition to vectoring were studied in conjunction with CRT pilot displays incorporating traffic situation displays with and without aircraft flight path predictors. The sequencing and advisory systems gave increasing control responsibility to the pilots. It was concluded that distributed management systems could in practice significantly reduce controller verbal workload without reducing system performance. Implications of this conclusion suggest that distributed management would allow controllers to handle a larger volume of traffic safely either as a normal operating procedure or as a failure mode alternative in a highly automated ground centered system.

Kreifeldt, J. G.↗

NASA NTRS1986

A prototype expert system in OPS5 for data error detection

A prototype expert system has been developed in the OPS5 language to perform error checking on data which spacecraft builders/users supply to the NASA Goddard Space Flight Center for processing on the Communications Link Analysis and Simulation System (CLASS) computer. This prototype expert system, called Trajectory Preprocessing System (TRAPS), contains 49 rules. In its operational phase, TRAPS will run in the Oak Ridge Production Language (ORPL) on the CLASS computer. ORPL, an implementation of OPS5 in MULTIFORTH on a desktop computer, is now being ported to SS-FORTH on the CLASS computer. This paper discusses the expert system problem domain, development approch, tools, results, and future plans stemming from the TRAPS project.

Rash, James↗

NASA NTRS1991

Valve- And Switch-Monitoring Computer Program

Human operators freed from tedious, repetitive monitoring tasks. Computer program applies techniques of artificial intelligence to monitoring positions of many switches and valves. Uses combination of procedural and declarative programming techniques. NASA's C Language Integrated Production System (CLIPS) provides rule-processing capabilities. Host program, written in C, acquires necessary data and applies valuation algorithm to generate knowledge-based propositions. Written to assist human flight controllers in comparing actual with expected configuration of switches and valves in Space Shuttle; underlying programming concept applicable to other complicated systems as chemical-processing plants, power-plants, and automated assembly lines. Program works with present monitoring equipment and computers.

Barry, Matthew R.↗

NASA NTRS2011

Lessons Learned from the Space Shuttle Engine Cutoff System (ECO) Anomalies

The Space Shuttle Orbiter's main engine cutoff (ECO) system first failed ground checkout in April, 2005 during a first tanking test prior to Return-to-Flight. Despite significant troubleshooting and investigative efforts that followed, the root cause could not be found and intermittent anomalies continued to plague the Program. By implementing hardware upgrades, enhancing monitoring capability, and relaxing the launch rules, the Shuttle fleet was allowed to continue flying in spite of these unexplained failures. Root cause was finally determined following the launch attempts of STS-122 in December, 2007 when the anomalies repeated, which allowed drag-on instrumentation to pinpoint the fault (the ET feedthrough connector). The suspect hardware was removed and provided additional evidence towards root cause determination. Corrective action was implemented and the system has performed successfully since then. This white paper presents the lessons learned from the entire experience, beginning with the anomalies since Return-to-Flight through discovery and correction of the problem. To put these lessons in better perspective for the reader, an overview of the ECO system is presented first. Next, a chronological account of the failures and associated investigation activities is discussed. Root cause and corrective action are summarized, followed by the lessons learned.

Martinez, Hugo E.↗

NASA NTRS1992

Manned testing in a simulated space environment

A view of the facility and operational requirements involved in performing a manned thermal vacuum test is presented. The requirements fall into two major categories. The first category deals with placing the suited crewmen in a hazardous environment and assuring their safety. The second category deals with the constraints and special requirements involved with a suited crewman operating flight hardware in a 1-G environment. Design areas that deal with man rating a chamber, including fire suppression, emergency repress, emergency power, backups, reliable instrumentation and data systems, communications, television monitoring, biomedical monitoring, material compatibilities, and equipment supporting the Extravehicular Mobility Unit (EMU) are discussed. The operational issues that are peculiar to manned testing such as test rules, test procedures, test protocol, emergency drills, availability of hyperbaric facilities, test team training and certification engineering concerns for a safe mechanical and instrumentation buildup, hazard analysis, and Failure Modes and Effects Analysis are discussed. The constraints and special requirements involved with a suited crewman operating flight hardware in a 1-G environment are addressed.

Fender, Donna L.↗