Search NASA⌕ Search

NASA NTRS · 20170007262

Concept of Operations for RCO SPO

Abstract

Reduced crew operations (RCO) refers to the reduction of crew members flying long-haul or military operations with more than one pilot onboard. Single pilot operations (SPO) refers to flying a commercial transport aircraft with only one pilot on board the aircraft, assisted by advanced onboard automation andor ground operators providing piloting support services. Properly implemented, RCO/SPO could provide operating cost savings while maintaining a level of safety no less than conventional two-pilot commercial operations. A concept of operations (ConOps) for any paradigm describes the characteristics of its various components and their integration in a multi-dimensional design space. This paper presents key options for humanautomation function allocation being considered by NASA in its ongoing development of RCO/SPO ConOps.

Explore related subjects

Keep this discovery

Explore connections, maps & timelines

BibTeXRIS

Matessa, Michael, Strybel, Thomas, Vu, Kim, Battiste, Vernol, Schnell, Thomas. 2017-07-10. Concept of Operations for RCO SPO. https://ntrs.nasa.gov/citations/20170007262

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related reports

Concept of Operations for Management by Trajectory

This document describes Management by Trajectory (MBT), a concept for future air traffic management (ATM) in which every flight operates in accordance with a four-dimensional trajectory (4DT) that is negotiated between the airspace user and the Federal Aviation Administration (FAA) to respect the airspace user's goals while complying with National Airspace System (NAS) constraints. In the present-day NAS, the ATM system attempts to predict the trajectory for each flight based on the approved flight plan and scheduled or controlled departure time. However, once the aircraft starts to move, controllers tactically manage the aircraft to implement traffic management restrictions, separate otherwise conflicting aircraft, and address arising NAS constraints. Tactical controller actions are not directly communicated to the automation systems or other stakeholders. Furthermore, the initial trajectory prediction does not anticipate these disruptions or how they will impact the flight. Consequently, and compounded by gaps in required data and models, trajectory predictions are less accurate than possible, which affects Traffic Flow Management (TFM) performance. A cornerstone of the MBT concept is that all air vehicles have, at all times, an assigned 4DT from their current state to their destination. These assigned trajectories consist of trajectory constraints and descriptions. Pilots and air traffic controllers, with the aid of automation, operate the aircraft to comply with the assigned trajectory, unless first negotiating a revision. Equipped aircraft have substantial responsibility for complying with the assigned trajectory without controller intervention. To maximize the operational flexibility available to the airspace user, the assigned trajectory only imposes trajectory constraints as required to achieve the ATM goals of NAS constraint compliance and aircraft separation. Trajectory descriptions are added to the assigned trajectory to ensure sufficient predictability. To further improve trajectory prediction accuracy, airspace users supplement the assigned trajectory by broadcasting intent information and updating it as necessary. Air vehicle intent is a more detailed description of the airspace user's plan for how the flight will fly the assigned trajectory. Air vehicle intent can change freely, without negotiation, as long as it remains in compliance with the assigned trajectory. Aircraft assigned trajectories, air vehicle intent, and predicted trajectories are shared, creating a common view among stakeholders. A NAS Constraint Service gathers and publishes information about all known NAS constraints, enabling airspace users to be informed participants in trajectory negotiation. Trajectory constraints in the assigned trajectory are mapped to NAS constraints to facilitate identifying which aircraft are affected when NAS constraints change. To support efficient trajectory negotiation, all aircraft provide current information about air vehicle capabilities. Assigned trajectories are constructed to satisfy all known NAS constraints, improving trajectory stability and predictability. Uncertainty and disruptions are handled by modifying the assigned trajectory as far in advance as possible. By proactively negotiating changes to the assigned trajectory, rather than relying on controller-selected tactical actions such as vectors to resolve traffic conflicts or implement miles-in-trail restrictions, MBT keeps aircraft on closed trajectories that are fully known to all stakeholders. Since reactive air traffic control actions cannot be predicted in advance, the downstream trajectory cannot be accurately predicted until they happen. Reliable trajectory predictions allow the system to identify needed modifications to trajectories further in advance, where they can be negotiated and communicated as amendments (i.e., additional or altered trajectory constraints) to the assigned trajectory. Decision Support Tools (DSTs) aid controllers in rapidly defining and communicating closed trajectories to the aircraft and support all stakeholders in trajectory negotiation. Anticipated MBT benefit mechanisms include more accurate trajectory predictions, improved ATM performance and robustness to off-nominal conditions, increased flexibility and operational efficiency, reduced impediments to emerging classes of airspace users accessing NAS resources, reduced environmental impacts, and enhanced safety.

ConOps↗

Air Traffic Management Technology Demonstration - 3 (ATD-3): Operational Concept for the Integration of ATD-3 Capabilities Version 1.0

ATD-3 has developed four capabilities to address its goal and objectives. The four ATD-3 capabilities include: Dynamic Weather Routes (DWR), Multi-Flight Common Routes (MFCR), Traffic Aware Strategic Aircrew Requests (TASAR), and Dynamic Routes for Arrivals in Weather (DRAW). This document describes the long-term, mature vision for the use and incorporation of the ATD-3 capabilities into the National Airspace System (NAS). This vision describes their complementary interaction and the benefit capture that accrues from use. Recognizing that all capabilities are unlikely to be implemented in unison, each of the capabilities is designed and able to be implemented independently. As discrete portions of the integrated capabilities are planned, additional integration efforts should be undertaken to validate the complementary interactions and benefit pool are realized from the selected subset.

ConOps↗

SysML Success Tree for DAVINCI In-Situ Campaign Requirements Validation and Redundancy Assessment

The DAVINCI mission will scientifically study the Venusian atmosphere to better understand the current state of the planet and its evolutionary history. This will be accomplished by deploying a descent probe to collect in-situ atmospheric dynamic and spectroscopic measurements, characterize ambient temperatures and pressures during descent, and surface imaging below the cloud layer. To better characterize the DAVINCI In-Situ Campaign, a success tree, developed in the SysML tool, MagicDraw, was created to define the events necessary to have a successful in-situ campaign, for each phase of the campaign. This success tree was also used to validate DAVINCI Program, Mission, and Element level requirements. In addition, because DAVINCI is a single-string mission, the success tree was also used to identify areas of redundancy and resiliency throughout the campaign. The initial redundancy assessment recommended further on-orbit evaluation of the probe’s communication system, as well as further evaluation of the ability of the mass spectrometer turbo-molecular pump to handle the expected decent environment. During the integration and test phase of the overall mission, the success tree will be used to guide the mission validation process, helping to ensure that the in-situ mission elements can perform in accordance with the DAVINCI In-Situ Concept of Operations document.

ConOps↗