Search NASA⌕ Search

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.

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

At least 325 records · Page 18
All sourcesNASA NTRSDOE OSTI
NASA NTRS1990

Rule-based mechanisms of learning for intelligent adaptive flight control

How certain aspects of human learning can be used to characterize learning in intelligent adaptive control systems is investigated. Reflexive and declarative memory and learning are described. It is shown that model-based systems-theoretic adaptive control methods exhibit attributes of reflexive learning, whereas the problem-solving capabilities of knowledge-based systems of artificial intelligence are naturally suited for implementing declarative learning. Issues related to learning in knowledge-based control systems are addressed, with particular attention given to rule-based systems. A mechanism for real-time rule-based knowledge acquisition is suggested, and utilization of this mechanism within the context of failure diagnosis for fault-tolerant flight control is demonstrated.

Handelman, David A.↗
NASA NTRS1987

Traditional versus rule-based programming techniques - Application to the control of optional flight information

A traditional programming technique for controlling the display of optional flight information in a civil transport cockpit is compared to a rule-based technique for the same function. This application required complex decision logic and a frequently modified rule base. The techniques are evaluated for execution efficiency and implementation ease; the criterion used to calculate the execution efficiency is the total number of steps required to isolate hypotheses that were true and the criteria used to evaluate the implementability are ease of modification and verification and explanation capability. It is observed that the traditional program is more efficient than the rule-based program; however, the rule-based programming technique is more applicable for improving programmer productivity.

Ricks, Wendell R.↗
NASA NTRS1990

Boeing flight deck design philosophy

Information relative to Boeing flight deck design philosophy is given in viewgraph form. Flight deck design rules, design considerations, functions allocated to the crew, redundancy and automation concerns, and examples of accident data that were reviewed are listed.

Stoll, Harty↗
NASA NTRS1990

A criterion for establishing life limits

The development of a rigorous statistical method that would utilize hardware-demonstrated reliability to evaluate hardware capability and provide ground rules for safe flight margin is discussed. A statistical-based method using the Weibull/Weibayes cumulative distribution function is described. Its advantages and inadequacies are pointed out. Another, more advanced procedure, Single Flight Reliability (SFR), determines a life limit which ensures that the reliability of any single flight is never less than a stipulated value at a stipulated confidence level. Application of the SFR method is illustrated.

Skopp, G. H.↗
NASA NTRS2005

Rover Sequencing and Visualization Program

The Rover Sequencing and Visualization Program (RSVP) is the software tool for use in the Mars Exploration Rover (MER) mission for planning rover operations and generating command sequences for accomplishing those operations. RSVP combines three-dimensional (3D) visualization for immersive exploration of the operations area, stereoscopic image display for high-resolution examination of the downlinked imagery, and a sophisticated command-sequence editing tool for analysis and completion of the sequences. RSVP is linked with actual flight-code modules for operations rehearsal to provide feedback on the expected behavior of the rover prior to committing to a particular sequence. Playback tools allow for review of both rehearsed rover behavior and downlinked results of actual rover operations. These can be displayed simultaneously for comparison of rehearsed and actual activities for verification. The primary inputs to RSVP are downlink data products from the Operations Storage Server (OSS) and activity plans generated by the science team. The activity plans are high-level goals for the next day s activities. The downlink data products include imagery, terrain models, and telemetered engineering data on rover activities and state. The Rover Sequence Editor (RoSE) component of RSVP performs activity expansion to command sequences, command creation and editing with setting of command parameters, and viewing and management of rover resources. The HyperDrive component of RSVP performs 2D and 3D visualization of the rover s environment, graphical and animated review of rover-predicted and telemetered state, and creation and editing of command sequences related to mobility and Instrument Deployment Device (IDD) operations. Additionally, RoSE and HyperDrive together evaluate command sequences for potential violations of flight and safety rules. The products of RSVP include command sequences for uplink that are stored in the Distributed Object Manager (DOM) and predicted rover state histories stored in the OSS for comparison and validation of downlinked telemetry. The majority of components comprising RSVP utilize the MER command and activity dictionaries to automatically customize the system for MER activities. Thus, RSVP, being highly data driven, may be tailored to other missions with minimal effort. In addition, RSVP uses a distributed, message-passing architecture to allow multitasking, and collaborative visualization and sequence development by scattered team members.

Cooper, Brian↗
NASA NTRS2005

Update on Rover Sequencing and Visualization Program

The Rover Sequencing and Visualization Program (RSVP) has been updated. RSVP was reported in Rover Sequencing and Visualization Program (NPO-30845), NASA Tech Briefs, Vol. 29, No. 4 (April 2005), page 38. To recapitulate: The Rover Sequencing and Visualization Program (RSVP) is the software tool to be used in the Mars Exploration Rover (MER) mission for planning rover operations and generating command sequences for accomplishing those operations. RSVP combines three-dimensional (3D) visualization for immersive exploration of the operations area, stereoscopic image display for high-resolution examination of the downlinked imagery, and a sophisticated command-sequence editing tool for analysis and completion of the sequences. RSVP is linked with actual flight code modules for operations rehearsal to provide feedback on the expected behavior of the rover prior to committing to a particular sequence. Playback tools allow for review of both rehearsed rover behavior and downlinked results of actual rover operations. These can be displayed simultaneously for comparison of rehearsed and actual activities for verification. The primary inputs to RSVP are downlink data products from the Operations Storage Server (OSS) and activity plans generated by the science team. The activity plans are high-level goals for the next day s activities. The downlink data products include imagery, terrain models, and telemetered engineering data on rover activities and state. The Rover Sequence Editor (RoSE) component of RSVP performs activity expansion to command sequences, command creation and editing with setting of command parameters, and viewing and management of rover resources. The HyperDrive component of RSVP performs 2D and 3D visualization of the rover s environment, graphical and animated review of rover predicted and telemetered state, and creation and editing of command sequences related to mobility and Instrument Deployment Device (robotic arm) operations. Additionally, RoSE and HyperDrive together evaluate command sequences for potential violations of flight and safety rules. The products of RSVP include command sequences for uplink that are stored in the Distributed Object Manager (DOM) and predicted rover state histories stored in the OSS for comparison and validation of downlinked telemetry. The majority of components comprising RSVP utilize the MER command and activity dictionaries to automatically customize the system for MER activities.

Cooper, Brian↗
NASA NTRS2011

Reducing NPR 7120.5D to Practice: Transitioning from Design Reviews to the SIR Hardware Review

The Gravity Recovery And Interior Laboratory (GRAIL) mission was the first Jet Propulsion Laboratory (JPL) project initiated under NASA's revised rules for space flight project management, NPR 7120.5D, "NASA Space Flight Program and Project Management Requirements." NASA selected GRAIL through a competitive Announcement of Opportunity process and funded its Phase B Preliminary Design effort. The team's first major milestone was a JPL institutional milestone, the Project Mission System Review (PMSR), which proved an excellent tune-up for the end-of-Phase-B NASA life-cycle review, the Preliminary Design Review (PDR). Building on JPL experience on the Prometheus and Juno projects, the team successfully organized for and conducted these reviews on an aggressive schedule. For the Project Critical Design Review (CDR), lessons learned from the PDR and updated Standing Review Board (SRB) practices from the Agency were factored into the review preparation effort. Additionally, the review was held at the Principal Investigator's institution, the Massachusetts Institute of Technology, rather than at the project management center (JPL), which necessitated additional cross-country coordination steps. The PMSR, PDR, and CDR were design reviews and largely paper-oriented. For the System Integration Review (SIR), the project needed to transition to a hardware review and deal with paper in a very different manner. While many of the practices employed for the design reviews were modified and retained (e.g., review preparation team, gate products management, pre-reviews, SRB coordination), the review agenda, presentation style, and slide templates were significantly changed. A key success factor concerned the handling of project open paper, which was succinctly and effectively communicated to the SRB in presentations.This paper provides a brief overview of the GRAIL mission and its project management challenges, provides a detailed description of project SIR preparation and execution activities, including positive and negative lessons learned and identifies recommendations for future NASA (and non- NASA) project teams.

NPR 7120.5D↗
NASA NTRS2013

Towards Real-time, On-board, Hardware-Supported Sensor and Software Health Management for Unmanned Aerial Systems

Unmanned aerial systems (UASs) can only be deployed if they can effectively complete their missions and respond to failures and uncertain environmental conditions while maintaining safety with respect to other aircraft as well as humans and property on the ground. In this paper, we design a real-time, on-board system health management (SHM) capability to continuously monitor sensors, software, and hardware components for detection and diagnosis of failures and violations of safety or performance rules during the flight of a UAS. Our approach to SHM is three-pronged, providing: (1) real-time monitoring of sensor and/or software signals; (2) signal analysis, preprocessing, and advanced on the- fly temporal and Bayesian probabilistic fault diagnosis; (3) an unobtrusive, lightweight, read-only, low-power realization using Field Programmable Gate Arrays (FPGAs) that avoids overburdening limited computing resources or costly re-certification of flight software due to instrumentation. Our implementation provides a novel approach of combining modular building blocks, integrating responsive runtime monitoring of temporal logic system safety requirements with model-based diagnosis and Bayesian network-based probabilistic analysis. We demonstrate this approach using actual data from the NASA Swift UAS, an experimental all-electric aircraft.

System & Software Health Management↗
NASA NTRS2015

Towards Real-Time, On-Board, Hardware-Supported Sensor and Software Health Management for Unmanned Aerial Systems

For unmanned aerial systems (UAS) to be successfully deployed and integrated within the national airspace, it is imperative that they possess the capability to effectively complete their missions without compromising the safety of other aircraft, as well as persons and property on the ground. This necessity creates a natural requirement for UAS that can respond to uncertain environmental conditions and emergent failures in real-time, with robustness and resilience close enough to those of manned systems. We introduce a system that meets this requirement with the design of a real-time onboard system health management (SHM) capability to continuously monitor sensors, software, and hardware components. This system can detect and diagnose failures and violations of safety or performance rules during the flight of a UAS. Our approach to SHM is three-pronged, providing: (1) real-time monitoring of sensor and software signals; (2) signal analysis, preprocessing, and advanced on-the-fly temporal and Bayesian probabilistic fault diagnosis; and (3) an unobtrusive, lightweight, read-only, low-power realization using Field Programmable Gate Arrays (FPGAs) that avoids overburdening limited computing resources or costly re-certification of flight software. We call this approach rt-R2U2, a name derived from its requirements. Our implementation provides a novel approach of combining modular building blocks, integrating responsive runtime monitoring of temporal logic system safety requirements with model-based diagnosis and Bayesian network-based probabilistic analysis. We demonstrate this approach using actual flight data from the NASA Swift UAS.

Unmanned Aerial System↗
NASA NTRS1987

Traditional versus rule-based programming techniques: Application to the control of optional flight information

To the software design community, the concern over the costs associated with a program's execution time and implementation is great. It is always desirable, and sometimes imperative, that the proper programming technique is chosen which minimizes all costs for a given application or type of application. A study is described that compared cost-related factors associated with traditional programming techniques to rule-based programming techniques for a specific application. The results of this study favored the traditional approach regarding execution efficiency, but favored the rule-based approach regarding programmer productivity (implementation ease). Although this study examined a specific application, the results should be widely applicable.

Ricks, Wendell R.↗
NASA NTRS1990

Ramifications of the recent FAA rule for windshear systems on the development of forward-looking systems

The recent Federal Aviation Administration (FAA) rule requiring windshear systems with flight guidance may have severe ramifications for the development of infrared and other forward-looking systems. The industry needs to have and can have a more cost effective option through the use of a forward-looking system with a reactive backup instead of a reactive system with flight guidance. However, because of the short time for compliance with the new FAA rule, it is possible that existing transport aircraft will be in full compliance before a comprehensive investigation of all forward-looking systems can be completed. If this occurs, it is possible that the market for forward-looking systems will be severely reduced, thereby eliminating the economic incentive to develop these much needed systems. Thus, to assure that this option is available for the airlines, it beehoves the industry to immediately support an in-service evaluation of all available forward-looking systems.

Adamson, H. Patrick↗
NASA NTRS2016

Computational Study of Flow Interactions in Coaxial Rotors

Although the first idea of coaxial rotors appeared more than 150 years ago, most helicopters have used single main-rotor/tail-rotor combination. Since reactive moments of coaxial rotors are canceled by contra-rotation, no tail rotor is required to counter the torque generated by the main rotor. Unlike the single main rotor design that distributes power to both main and tail rotors, all of the power for coaxial rotors is used for vertical thrust. Thus, no power is wasted for anti-torque or directional control. The saved power helps coaxial rotors reach a higher hover ceiling than single rotor helicopters. Another advantage of coaxial rotors is that the overall rotor diameter can be reduced for a given vehicle gross weight because each rotor provides a maximum contribution to vertical thrust to overcome vehicle weight. However, increased mechanical complexity of the hub has been one of the challenges for manufacturing coaxial rotorcraft. Only the Kamov Design Bureau of Russia had been notably successful in production of coaxial helicopters until Sikorsky built X2, an experimental compound helicopter. Recent developments in unmanned aircraft systems and high-speed rotorcraft have renewed interest in the coaxial configuration. Multi-rotors are frequently used for small electric unmanned rotorcraft partly due to mechanical simplicity. The use of multiple motors provides redundancy as well as cost-efficiency. The multi-rotor concept has rarely been used until recently because of its inherent stability and control problems. However, advances in inexpensive electronic flight control systems have opened the floodgates for small drones using multirotors. Coaxial rotors have started to appear in some multi-rotor configurations. Small coaxial rotors have often been designed using a hundred year old approach that is "sketch, build, fly, and iterate." In that approach, there is no systematic way to explore trade-offs or determine logical next steps. It is neither possible to account for multiple real-world constraints up front in design nor possible to know what performance is possible with a given design. Since unmanned vehicles are sized and optimized for the particular mission, a modern low-fidelity conceptual design and sizing tool that has been used for the design of large helicopters can be used for design of small coaxial rotorcraft. However, unlike most helicopters with single main rotor, the interactions between the upper and lower rotors emerge as an important factor to consider in design because an increase in performance of a multi-rotor system is not proportional to the number of rotors. Interference losses and differences in thrusts between the upper and lower rotors were investigated by theoretical methods as well as a computational fluid dynamics (CFD) method using the Reynolds-Averaged Navier-Stokes (RANS) equations. In this work, hybrid turbulence models are used to investigate the physics of interactions between coaxial rotors and a fuselage that are not well understood. Present study covers not only small-scale drones but also large-scale coaxial rotors for heavy-lifting missions. Considering the recently proposed FAA drone rules that require the flight only in visual line-of-sight, a large multirotor might be used as an airborne carrier for launch and recovery of unmanned aircraft systems with a human operator onboard. For applications to civil operations, their aerodynamic performance and noise levels need to be assessed. Noise is one of the largest limiting factors to rotorcraft operations in urban area. Since the high-frequency noise of multi-rotors may increase the annoyance, noise may turn out to be a key issue that must be addressed for market acceptability. One of the objectives of the present work is to study the effects of inter-rotor spacing and collectives on the performance, efficiency, and acoustics of coaxial rotor systems.

Study↗
NASA NTRS2016

SAFEGUARD: An Assured Safety Net Technology for UAS

As demands increase to use unmanned aircraft systems (UAS) for a broad spectrum of commercial applications, regulatory authorities are examining how to safely integrate them without loss of safety or major disruption to existing airspace operations. This work addresses the development of the Safeguard system as an assured safety net technology for UAS. The Safeguard system monitors and enforces conformance to a set of rules defined prior to flight (e.g., geospatial stay-out or stay-in regions, speed limits, altitude limits). Safeguard operates independently of the UAS autopilot and is strategically designed in a way that can be realized by a small set of verifiable functions to simplify compliance with regulatory standards for commercial aircraft. A framework is described that decouples the system from any other devices on the UAS as well as introduces complementary positioning source(s) for applications that require integrity and availability beyond what the Global Positioning System (GPS) can provide. Additionally, the high level logic embedded within the software is presented, as well as the steps being taken toward verification and validation (V&V) of proper functionality. Next, an initial prototype implementation of the described system is disclosed. Lastly, future work including development, testing, and system V&V is summarized.

Dill, Evan T.↗
NASA NTRS2017

Safeguard: Progress and Test Results for a Reliable Independent On-Board Safety Net for UAS

As demands increase to use unmanned aircraft systems (UAS) for a broad spectrum of commercial applications, regulatory authorities are examining how to safely integrate them without compromising safety or disrupting traditional airspace operations. For small UAS, several operational rules have been established; e.g., do not operate beyond visual line-of-sight, do not fly within five miles of a commercial airport, do not fly above 400 feet above ground level. Enforcing these rules is challenging for UAS, as evidenced by the number of incident reports received by the Federal Aviation Administration (FAA). This paper reviews the development of an onboard system - Safeguard - designed to monitor and enforce conformance to a set of operational rules defined prior to flight (e.g., geospatial stay-out or stay-in regions, speed limits, and altitude constraints). Unlike typical geofencing or geo-limitation functions, Safeguard operates independently of the off-the-shelf UAS autopilot and is designed in a way that can be realized by a small set of verifiable functions to simplify compliance with existing standards for safety-critical systems (e.g. for spacecraft and manned commercial transportation aircraft systems). A framework is described that decouples the system from any other devices on the UAS as well as introduces complementary positioning source(s) for applications that require integrity and availability beyond what can be provided by the Global Positioning System (GPS). This paper summarizes the progress and test results for Safeguard research and development since presentation of the design concept at the 35th Digital Avionics Systems Conference (DASC '16). Significant accomplishments include completion of software verification and validation in accordance with NASA standards for spacecraft systems (to Class B), development of improved hardware prototypes, development of a simulation platform that allows for hardware-in-the-loop testing and fast-time Monte Carlo evaluations, and flight testing on multiple air vehicles. Integration testing with NASA's UAS Traffic Management (UTM) service-oriented architecture was also demonstrated.

Young, Steven D.↗
NASA NTRS2008

Autonomous Flight Safety System - Phase III

The Autonomous Flight Safety System (AFSS) is a joint KSC and Wallops Flight Facility project that uses tracking and attitude data from onboard Global Positioning System (GPS) and inertial measurement unit (IMU) sensors and configurable rule-based algorithms to make flight termination decisions. AFSS objectives are to increase launch capabilities by permitting launches from locations without range safety infrastructure, reduce costs by eliminating some downrange tracking and communication assets, and reduce the reaction time for flight termination decisions.

Source record↗
NASA NTRS2006

Moving from Bilateral to Multilateral Medical Operations

When the ISS Integrated Medical Group moved to a multilateral configuration for the ASTROLAB mission, several challenges were encountered and overcome that allowed for a streamlined operational experience. Dating back to the early 1990s, the European Space Agency (ESA) has sent flight surgeon and Biomedical Engineering (BME) personnel to NASA-JSC and Russia to train for space flight operational support. This training was tailored towards the needs of particular Shuttle/Soyuz missions, and more generally for eventual ISS support. With the announcement of the ASTROLAB mission, NASA and ESA personnel worked together to develop a detailed training template for ESA BMEs to ensure successful support of the mission from the European Astronaut Center (EAC). This training included the deployment of ESA BMEs to JSC, as well as the development of a rotation of ISS-certified NASA BMEs to the EAC. In addition to training, NASA, ESA, and the Russian Federal Space Agency (FSA) worked together preflight to develop multilateral flight control support concepts and implementation plans. This resulted in flight control support schedules, operational rules of engagement, and the delineation of responsibilities. NASA also assisted ESA with the development and deployment of workstation displays to allow the ESA medical flight control team to monitor ISS telemetry from the EAC. The goal of this presentation is to provide details of the preflight preparation and in-flight support of the ASTROLAB mission by the ESA, NASA, and FSA medical support teams. In addition, it will identify lessons learned that will be implemented for future multilateral endeavors.

Roden, S.↗