Search NASA⌕ Search

SEARCH · Search NASA

Results for “Automated Flight”

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 181 records · Page 10

Controlled breaks as a fatigue countermeasure on the flight deck

BACKGROUND: A major challenge for flight crews is the need to maintain vigilance during long, highly automated nighttime flights. No system currently exists to assist in managing alertness, and countermeasure options are limited. Surveys reveal many pilots use breaks as an in-flight countermeasure, but there have been no controlled studies of their effectiveness. HYPOTHESIS: We hypothesized that brief, regular breaks could improve alertness and performance during an overnight flight. METHOD: A 6-h, uneventful, nighttime flight in a Boeing 747-400 flight simulator was flown by fourteen two-man crews. The 14 subjects in the treatment group received 5 short breaks spaced hourly during cruise; the 14 subjects in the control group received 1 break in the middle of cruise. Continuous EEG/EOG, subjective sleepiness, and psychomotor vigilance performance data were collected. RESULTS: During the latter part of the night, the treatment group showed significant reductions for 15 min post-break in slow eye movements, theta-band activity, and unintended sleep episodes compared with the control group. The treatment group reported significantly greater subjective alertness for up to 25 min post-break, with strongest effects near the time of the circadian trough. There was no evidence of objective vigilance performance improvement at 15-25 min post-break, with expected performance deterioration occurring due to elevated sleep drive and circadian time. CONCLUSIONS: The physiological and subjective data indicate the breaks reduced nighttime sleepiness for at least 15 min post-break and may have masked sleepiness for up to 25 min, suggesting the potential usefulness of short-duration breaks as an in-flight fatigue countermeasure.

Non-NASA Center↗

Human factors in cockpit automation: A field study of flight crew transition

The factors which affected two groups of airline pilots in the transition from traditional airline cockpits to a highly automated version were studied. All pilots were highly experienced in traditional models of the McDonnell-Douglas DC-9 prior to their transition to the more automated DC-9-80. Specific features of the new aircraft, particularly the digital flight guidance system (DFGS) and other automatic features such as the autothrottle system (ATS), autobrake, and digital display were studied. Particular attention was paid to the first 200 hours of line flying experience in the new aircraft, and the difficulties that some pilots found in adapting to the new systems during this initial operating period. Efforts to prevent skill loss from automation, training methods, traditional human factors issues, and general views of the pilots toward cockpit automation are discussed.

Wiener, E. L.↗

Pilot Controls for a Hybrid Turbine-Electric 17 Engine Aircraft

NASA is exploring the development of a 180-passenger subsonic single engine aft turbine aircraft where the aft turbine provides electric power in a hybrid design to wing mounted electric engines. A pilot-in-the-loop study was conducted at Langley Research Center in Hampton, Virginia to explore the design of a flight deck for the hybrid electric aircraft with 16 wing fans and an aft mounted turbine engine. Current flight deck designs provide control inceptors for each propulsion engine and display of all engine parameters for all primary aircraft engines. Automation trends and increasing automation in flight controls and throttle controls indicate less controls instead of more. The design team researched state-of-the-art and recommended study of three, two, and one throttle levers. Engine displays were researched and two were recommended for initial evaluation. 16 airline pilots evaluated the three throttle configurations and two engine display options. Engine failures for known probable indications were evaluated against all throttle and display configurations. This included one, four symmetric, eight non-symmetric, and sixteen momentary electric engine failures with the loss of the aft turbine. The turbine engine was evaluated for complete and partial failure during critical phases of takeoff as well as enroute. This paper details the pilot study including pilot comments supporting the potential for increased automation and a single throttle control. Detailed recommendations are provided for a novel single throttle control and additional pilot controls to support selection of engines during start, shutdown, and engine troubleshooting procedures. This design deviates significantly from current practice of providing throttles for each propulsion engine. Engine display recommendations are provided based on pilot feedback during a guided post-evaluation interview. Recommendations for future study are documented with supporting research and current observations about upcoming flight deck certifications.

autothrottle↗

Pilot Controls for a Hybrid Turbine-Electric 17-Engine Aircraft

NASA is exploring the development of a 180-passenger subsonic single engine aft turbine aircraft where the aft turbine provides electric power in a hybrid design to wing mounted electric engines. A pilot-in-the-loop study was conducted at Langley Research Center in Hampton, Virginia to explore the design of a flight deck for the hybrid electric aircraft with 16 wing fans and an aft mounted turbine engine. Current flight deck designs provide control inceptors for each propulsion engine and display of all engine parameters for all primary aircraft engines. Automation trends and increasing automation in flight controls and throttle controls indicate less controls instead of more. The design team researched state-of-the-art and recommended study of three, two, and one throttle levers. Engine displays were researched and two were recommended for initial evaluation. 16 airline pilots evaluated the three throttle configurations and two engine display options. Engine failures for known probable indications were evaluated against all throttle and display configurations. This included one, four symmetric, eight non-symmetric, and sixteen momentary electric engine failures with the loss of the aft turbine. The turbine engine was evaluated for complete and partial failure during critical phases of takeoff as well as enroute. This presentation details the pilot study including pilot comments supporting the potential for increased automation and a single throttle control. Detailed recommendations are provided for a novel single throttle control and additional pilot controls to support selection of engines during start, shutdown, and engine troubleshooting procedures. This design deviates significantly from current practice of providing throttles for each propulsion engine. Engine display recommendations are provided based on pilot feedback during a guided post-evaluation interview. Recommendations for future study are documented with supporting research and current observations about upcoming flight deck certifications.

autothrottle↗

Apollo experience report: Guidance and control systems: Automated control system for unmanned mission AS-201

The Apollo command module heat shield and Apollo command and service module/Saturn launch vehicle structural integrity were evaluated in an unmanned test flight. An automated control system was developed to provide the mission event sequencing, the real-time ground control interface, and the backup attitude reference system for the unmanned flight. The required mission events, the design logic, the redundancy concept, and the ground-support-equipment concept are described and some development problem areas are discussed. The mission event time line and the real-time ground command list are included to provide an outline of the control system capabilities and requirements. The mission was accomplished with the automated control system, which functioned without flight anomalies.

Holloway, G. F.↗

Space power system automation approaches at the George C. Marshall Space Flight Center

This paper discusses the automation approaches employed in various electrical power system breadboards at the Marshall Space Flight Center. Of particular interest is the application of knowledge-based systems to fault management and dynamic payload scheduling. A description of each major breadboard and the automation approach taken for each is given.

Weeks, D. J.↗

Detect and Avoid and Collision Avoidance Flight Test Results with ACAS Xr

In October 2023, the National Aeronautics and Space Administration (NASA) completed its Integration of Automated Systems flight test series, conducted under NASA’s Advanced Air Mobility project and in partnership with Sikorsky and the Defense Advanced Research Projects Agency (DARPA). The flight test effort included two crewed rotorcraft platforms. The first, a modified S-76B helicopter, served as the “ownship” for the duration of the flight test. The second vehicle, a modified S-70, served as the intruder aircraft. One Sikorsky pilot and one NASA test pilot was onboard each aircraft for every test point, with the NASA test pilot responsible for interacting with the research systems under test. Approximately half of the flight test was devoted to assessing the Federal Aviation Administration’s (FAA) next-generation collision avoidance system, the Airborne Collision Avoidance System X for Rotorcraft (ACAS Xr). The two configurations available within ACAS Xr – the Collision Avoidance System (CAS) configuration and the Detect and Avoid (DAA) configuration – were flown with an onboard pilot under Visual Flight Rules in controlled airspace over the Long Island Sound (Connecticut, USA). A total of 33 flight test cards were flown with ACAS Xr active. The ownship was equipped with ACAS Xr and the intruder was equipped with Automatic Dependent Surveillance-Broadcast (ADS-B). The test points were blocked by ACAS Xr configuration, with individual encounters varying the ownship speed (90 knots or 20 knots), the intruder designation (en-route, terminal area, or structured airspace), and method of RA execution (automated or manually executed). Results showed that the ACAS Xr alerting and guidance was largely effective and rated positively by the NASA test pilots, exemplified by zero instances of the pilots overriding an ACAS Xr Resolution Advisory (RA). Key areas of improvement, however, were noted, particularly with regards to the lack of an aural alert indicating a need to accelerate when receiving an RA at low speed and the occurrence of multiple RAs that the pilots found to be unacceptable.

detect and avoid↗

Detect and Avoid and Collision Avoidance Flight Test Results with ACAS Xr

In October 2023, the National Aeronautics and Space Administration (NASA) completed its Integration of Automated Systems flight test series, conducted under NASA’s Advanced Air Mobility project and in partnership with Sikorsky and the Defense Advanced Research Projects Agency (DARPA). The flight test effort included two crewed rotorcraft platforms. The first, a modified S-76B helicopter, served as the “ownship” for the duration of the flight test. The second vehicle, a modified S-70, served as the intruder aircraft. One Sikorsky pilot and one NASA test pilot was onboard each aircraft for every test point, with the NASA test pilot responsible for interacting with the research systems under test. Approximately half of the flight test was devoted to assessing the Federal Aviation Administration’s (FAA) next-generation collision avoidance system, the Airborne Collision Avoidance System X for Rotorcraft (ACAS Xr). The two configurations available within ACAS Xr – the Collision Avoidance System (CAS) configuration and the Detect and Avoid (DAA) configuration – were flown with an onboard pilot under Visual Flight Rules in controlled airspace over the Long Island Sound (Connecticut, USA). A total of 33 flight test cards were flown with ACAS Xr active. The ownship was equipped with ACAS Xr and the intruder was equipped with Automatic Dependent Surveillance-Broadcast (ADS-B). The test points were blocked by ACAS Xr configuration, with individual encounters varying the ownship speed (90 knots or 20 knots), the intruder designation (en-route, terminal area, or structured airspace), and method of RA execution (automated or manually executed). Results showed that the ACAS Xr alerting and guidance was largely effective and rated positively by the NASA test pilots, exemplified by zero instances of the pilots overriding an ACAS Xr Resolution Advisory (RA). Key areas of improvement, however, were noted, particularly with regards to the lack of an aural alert indicating a need to accelerate when receiving an RA at low speed and the occurrence of multiple RAs that the pilots found to be unacceptable.

detect and avoid↗

Technologies for automating rotorcraft nap-of-the-earth flight

This paper discusses the technologies required for automating rotorcraft nap-of-the-earth flight, where the use of natural obstacles for masking from the enemy is intentional and the danger of undesirable obstacles such as enemy traps is real. Specifically, the automatic guidance structure is modeled by three decision-making levels: the far-field mission planning and the mid-field terrain-masking trajectory shaping are both driven by prestored terrain data, whereas the nearfield obstacle detection/avoidance is driven by real-time on-board sensor data. This paper summarizes the far-field and mid-field accomplishments, and reports on the status of the more-recent efforts in obstacle detection and avoidance development. Obstacle detection is based primarily on passive imaging sensors for the desirable properties of covertness and wide field of view, although active sensors are included in the structure to provide the much needed high resolution for thin-wire detection.

Cheng, Victor H. L.↗

Automated Commanding of the SMAP Spacecraft Enables Efficient, Reliable, and Responsive Operations

The Soil Moisture Active Passive (SMAP) mission developed and deployed a system to autonomously handle most routine commanding of the observatory. This system of ground software is able to build commands, validate them, and radiate the commands to the spacecraft, all without human interaction. In the case of an off -nominal scenario, the system will abort gracefully and notify the mission operations team of the problem. The system was phased into operations during the first three months of the SMAP mission and handles over 90% of the weekly commanding of the vehicle. The gradual introduction of the automation in flight, along with an extensive test campaign, was instrumental in the success of the software. The automation has enabled substantial efficiencies in operations team staffing and has improved reliability by removing the potential for human error. The system also allows the SMAP project to be more responsive which has shown significant benefits in areas of data latency and science accuracy.

automation↗

Onboard Autonomy and Ground Operations Automation for the Intelligent Payload Experiment (IPEX) CubeSat Mission

The Intelligent Payload Experiment (IPEX) is a cubesat manifested for launch in October 2013 that will flight validate autonomous operations for onboard instrument processing and product generation for the Intelligent Payload Module (IPM) of the Hyperspectral Infra-red Imager (HyspIRI) mission concept. We first describe the ground and flight operations concept for HyspIRI IPM operations. We then describe the ground and flight operations concept for the IPEX mission and how that will validate HyspIRI IPM operations. We then detail the current status of the mission and outline the schedule for future development.

project data planning↗

The NASA MERIT program - Developing new concepts for accurate flight planning

It is noted that the rising cost of aviation fuel has necessitated the development of a new approach to upper air forecasting for flight planning. It is shown that the spatial resolution of the present weather forecast models used in fully automated computer flight planning is an important accuracy-limiting factor, and it is proposed that man be put back into the system, although not in the way he has been used in the past. A new approach is proposed which uses the application of man-computer interactive display techniques to upper air forecasting to retain the fine scale features of the atmosphere inherent in the present data base in order to provide a more accurate and cost effective flight plan. It is pointed out that, as a result of NASA research, the hardware required for this approach already exists.

Steinberg, R.↗

Flight software issues in onboard automated planning: lessons learned on EO-1

This paper focuses on the onboard planner and scheduler CASPER, whose core planning engine is based on the ground system ASPEN. Given the challenges of developing flight software, we discuss several of the issues encountered in preparing the planner for flight, including reducing the code image size, determining what data to place within the engineering telemetry packet, and performing long term planning.

planning↗

Beyond the sterile cockpit

Consideration is given to some of the negative aspects of the trend toward increased automation of aircraft flight decks. The history of automated devices for navigation, communications and detection on board aircraft is reviewed. Instances of automatic system failure are identified which have led to accidents, and the events surrounding the downing of Korean Airlines Flight 747 are reexamined within the context of a computer-based system failure. Finally, new software and interactive systems to reduce navigational error due to inadequate computer-assisted flight instruction (CAI) are described, with emphasis given to speech processing and intelligent CAI systems.

Wiener, E. L.↗

Development of SCR Aircraft takeoff and landing procedures for community noise abatement and their impact on flight safety

Piloted simulator studies to determine takeoff and landing procedures for a supersonic cruise transport concept that result in predicted community noise levels which meet current Federal Aviation Administration (FAA) standards are discussed. The results indicate that with the use of advanced procedures, the subject simulated aircraft meets the FAA traded noise levels during takeoff and landing utilizing average flight crew skills. The advanced takeoff procedures developed involved violating three of the current Federal Aviation Regulations (FAR) noise test conditions. These were: (1) thrust cutbacks at altitudes below 214 meters (700 ft); (2) thrust cutback level below those presently allowed; and (3) configuration change, other than raising the landing gear. It was not necessary to violate any FAR noise test conditions during landing approach. It was determined that the advanced procedures developed do not compromise flight safety. Automation of some of the aircraft functions reduced pilot workload, and the development of a simple head-up display to assist in the takeoff flight mode proved to be adequate.

Grantham, W. D.↗

Analyzing Mode Confusion via Model Checking

Mode confusion is one of the most serious problems in aviation safety. Today's complex digital flight decks make it difficult for pilots to maintain awareness of the actual states, or modes, of the flight deck automation. NASA Langley leads an initiative to explore how formal techniques can be used to discover possible sources of mode confusion. As part of this initiative, a flight guidance system was previously specified as a finite Mealy automaton, and the theorem prover PVS was used to reason about it. The objective of the present paper is to investigate whether state-exploration techniques, especially model checking, are better able to achieve this task than theorem proving and also to compare several verification tools for the specific application. The flight guidance system is modeled and analyzed in Murphi, SMV, and Spin. The tools are compared regarding their system description language, their practicality for analyzing mode confusion, and their capabilities for error tracing and for animating diagnostic information. It turns out that their strengths are complementary.

Luettgen, Gerald↗