SEARCH · Search NASA

Results for “The Concept of Operations (ConOps)”

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 55 records · Page 3

All sources NASA NTRS DOE OSTI

NASA NTRSDate not supplied

Assessing the Relocation of Artemis Foundational Lunar Surface Concepts

The National Aeronautics and Space Administration (NASA) has defined a functionally based Moon to Mars (M2M) architecture consisting of four key human exploration segments: human lunar return (HLR), foundational exploration (FE), sustained lunar evolution (SLE), and humans to Mars (H2M). These segments are portions of the architecture which represent a stepwise increase in complexity and achievement of M2M objectives [1]. As systems are deployed during the FE segment, it may be desired or even necessary to relocate these elements on the lunar surface as the architecture transitions into the SLE segment. While some Artemis elements under development, such as rovers, are being designed for mobility during both crewed and uncrewed/dormant periods, other architectural concepts do not currently carry a mobility capability. In preparation for the Agency’s 2023 Architecture Concept Review (ACR), a team was assembled to establish a methodology for assessing the relocation feasibility of normally stationary elements. Such a capability could be applied locally or regionally, and might allow for re-purposing previously occupied terrain, expansion of exploration range, aggregation of habitation elements, or retiring systems at the end of their useful service life. The assembled NASA team investigated the relocation trade space through defining a representative concept of operations (ConOps) and assessing possible system impacts. The team focused predominately on the relocation of medium and large surface habitat architectural concepts through surface-based traverses utilizing separable mobility platforms (SMP). A representative mobility platform model was placed through simulation to analyze the possible energy requirements and dynamic illumination impacts. Preliminary assessment indicated that element relocation might be achievable, however significant system and architectural-level risks still need to be quantified. Future analysis will assist in determining what degree of element relocation provides the greatest benefit to achieving a sustained lunar presence. [1] NASA. (2022). Moon to Mars Objectives. Retrieved from: https://www.nasa.gov/sites/default/files/atoms/files/m2m-objectives-exec-summary.pdf

Artemis↗

NASA NTRS2015

A Validated Task Analysis of the Single Pilot Operations Concept

The current day flight deck operational environment consists of a two-person Captain/First Officer crew. A concept of operations (ConOps) to reduce the commercial cockpit to a single pilot from the current two pilot crew is termed Single Pilot Operations (SPO). This concept has been under study by researchers in the Flight Deck Display Research Laboratory (FDDRL) at the National Aeronautics and Space Administration's (NASA) Ames (Johnson, Comerford, Lachter, Battiste, Feary, and Mogford, 2012) and researchers from Langley Research Centers (Schutte et al., 2007). Transitioning from a two pilot crew to a single pilot crew will undoubtedly require changes in operational procedures, crew coordination, use of automation, and in how the roles and responsibilities of the flight deck and ATC are conceptualized in order to maintain the high levels of safety expected of the US National Airspace System. These modifications will affect the roles and the subsequent tasks that are required of the various operators in the NextGen environment. The current report outlines the process taken to identify and document the tasks required by the crew according to a number of operational scenarios studied by the FDDRL between the years 2012-2014. A baseline task decomposition has been refined to represent the tasks consistent with a new set of entities, tasks, roles, and responsibilities being explored by the FDDRL as the move is made towards SPO. Information from Subject Matter Expert interviews, participation in FDDRL experimental design meetings, and study observation was used to populate and refine task sets that were developed as part of the SPO task analyses. The task analysis is based upon the proposed ConOps for the third FDDRL SPO study. This experiment possessed nine different entities operating in six scenarios using a variety of SPO-related automation and procedural activities required to guide safe and efficient aircraft operations. The task analysis presents the roles and responsibilities in a manner that can facilitate testing future scenarios. Measures of task count and workload were defined and analyzed to assess the impact of transitioning to a SPO environment.

task analysis↗

NASA NTRSDate not supplied

Corridor Design and Analysis for UAM Operations

The Urban Air Mobility (UAM) concept is a part of Advanced Air Mobility (AAM), a joint initiative between the Federal Aviation Administration (FAA), NASA, and industry to develop an air transportation system that uses new electric (i.e., green) air vehicles in geographical areas previously underserved by traditional aviation. Market forecast studies predict that there will be demand for alternate modes of air transportation using electric Vertical Take-off and Landing aircraft. UAM expands transportation networks by introducing short flights to move people and goods around metropolitan areas. UAM is expected to improve mobility for the public, decongest road traffic, reduce trip time, and decrease strain on existing public transportation networks. Various challenges exist to make the introduction of UAM operations successful in the U.S. National Airspace System (NAS). These include but are not limited to integration with existing airports and airspace, provision of air traffic services (e.g., separation), vehicle design and certification, and community acceptance. The focus of this paper is on integration of UAM operations into the NAS via introduction of new airspace structures. UAM will operate within a regulatory, operational, and technical environment that is incorporated into the NAS. As per the UAM Concept of Operations (ConOps), the FAA retains regulatory authority and is responsible for establishing operational parameters and maintaining oversight. The FAA’s UAM ConOps describes flights at low altitudes (below 5,000 ft) with minimal disruption to established conventional aircraft traffic and limited voice interactions with the Air Traffic Control (ATC). Early stages of UAM may use existing procedures to safely integrate UAM with conventional flights. This would involve flying under Part 91 Visual Flight Rules (VFR) and using voice for communications. The initial UAM ecosystem will utilize the current infrastructure such as routes, helipads, and ATC services, where practicable. A NASA study explored the use of existing helicopter routes in Dallas Fort Worth (DFW) airspace for initial UAM operations with a Letter of Agreement (LOA) that included procedures to request a Class B (controlled airspace) clearance. The research showed that the chosen approach was feasible for near-term, low-demand UAM traffic, but was not scalable. The growth of operations in today’s aviation system has resulted in airspace reorganization and procedures to ensure safety and efficiency as traffic rates increase. One proposed operating innovation that can help with the scalability of UAM is establishing routes and corridors. This may look similar to the Area Navigation (RNAV) procedures used today to streamline operations into busy airports. However, instead of FAA automation systems and ATC managing the flow of traffic, some UAM concepts envision a third-party service provider performing this role as part of the Provider of Services for UAM (PSU) network. The FAA’s UAM ConOps posits that new airspace structures such as UAM corridors include the following design criteria: 1) Minimal impact on existing NAS operations, 2) no or minimal additional ATC services, 3) public interest considerations such as noise, safety, and security, and 4) customer needs. The airspace available in urban environments is limited by the height of buildings, the effect of weather including wind gusts, privacy needs, and a clearance envelope. The new airspace structure would need to be designed around large airports and urban areas where the initial market demand is likely to exist. NASA has started evaluating airspace in the Dallas Fort Worth area to design new airspace structures, keeping the first two design criteria in mind. It is assumed that there will be an on-board pilot-in-command, and the flights will operate under VFR in Visual Meteorological Conditions. Corridors will be required in controlled airspace, whereas UAM operations can fly in uncontrolled Class G and E airspace using current day rules. Keeler et. al identified factors and heuristics for development of routes for UAM operations for integration with airspace close to large airports such as Dallas Fort Worth and Dallas Love Field. This paper describes the heuristics applied to define the corridors, analyzes them with respect to legacy traffic and presents key results.

Urban Air Mobility↗

NASA NTRS2026

Moon Base Transportation - Deliveries to the Lunar Surface

Development of the Moon Base will enable a home away from home for astronauts who will live and work at humanity’s first lunar outpost. In this effort, NASA’s Moon Transportation Office is responsible for enabling the transformational missions required to deliver habitats, supplies, science payloads, and all other elements needed to cultivate a permanent presence on the Lunar Surface. The Mission Concept (MC) is characterized through evaluation of an end-to-end architecture that can successfully deliver a generalized heavy large-volume payload, in excess of 4000 kg, to a precision landing and touchdown on the lunar surface. The mission architecture utilizes a single launch configuration of a Lunar Lander (LL) with a unique propellant system. The LL has an integral orbital transfer capability and features jettisonable elements. The design circumvents the need for prop transfer on orbit and multiple launch configurations. The launch vehicle (LV) for this work will assume the capability to deliver a payload in excess of 40,000 kg to orbit, affording multiple LV solutions. Considerations for the LL and payload deployment from the fairing are assumed to be handled through compliance with a launch providers’ Interface Requirements Document (IRD). The MC will span from launch at Kennedy Space Center (KSC) to terminal descent and touchdown on the lunar surface, requiring a total ΔV on the order of 6 km/s beyond what is required to get the vehicle stack to a 200 km circular Low Earth Orbit (LEO). Major mission phases include: launch and launch vehicle separation, transfer operations, pre-landing navigation, and lunar descent and touchdown. A Concept of Operations (ConOps) is used as the primary design driver for defining architecture of the vehicles necessary to achieve final payload delivery. Numerous ground rules and assumptions will be provided for each phase of the mission. Concept designs for the LL is presented. An emphasis of the design maximizes a feasible path for maturation, manufacturing, and operation. A self-imposed practical consideration for this effort is the incorporation of legacy designed hardware to minimize expensive, time-intensive, and high-risk hardware development cycles. The propulsion system of the LL adopts a conventional storable bipropellant configuration of monomethyl hydrazine (MMH) and mixed oxides of nitrogen (MON3). This effort will showcase a unique propellant delivery system to minimize the reliance on propellant management devices (PMDs) during descent. Numerous key constraints have been considered, across the multiple segments of the mission. These include the unique aspects of center of gravity (CG) management, thruster plume effects including self-impingement, propulsion system hardware limitations, navigation during multiple mission phases, and landing gear geometry for uneven terrain. These constraints shape the trades necessary for precision landing of heavy cargo and ensure compatibility with broader Moon Base Transportation concepts. The resulting insights inform future transportation strategies for the Moon and beyond; directly contributing to the development of cargo‑delivery standards that will support the long‑term buildup of a sustainable, continuously inhabited Moon Base.

Lunar Habitat↗

NASA NTRS2016

A Tailored Concept of Operations for NASA LSP Integrated Operations

An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this project is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services.

Systems↗

NASA NTRS2003

Concept of Operations for the NASA Weather Accident Prevention (WxAP) Project

The Weather Accident Prevention Concept of Operations (CONOPS) serves as a decision-making framework for research and technology development planning. It is intended for use by the WxAP members and other related programs in NASA and the FAA that support aircraft accident reduction initiatives. The concept outlines the project overview for program level 3 elements-such as AWIN, WINCOMM, and TPAWS (Turbulence)-that develop the technologies and operating capabilities to form the building blocks for WxAP. Those building blocks include both retrofit of equipment and systems and development of new aircraft, training technologies, and operating infrastructure systems and capabilities. This Concept of operations document provides the basis for the WxAP project to develop requirements based on the operational needs ofthe system users. It provides the scenarios that the flight crews, airline operations centers (AOCs), air traffic control (ATC), and flight service stations (FSS) utilize to reduce weather related accidents. The provision to the flight crew of timely weather information provides awareness of weather situations that allows replanning to avoid weather hazards. The ability of the flight crew to locate and avoid weather hazards, such as turbulence and hail, contributes to safer flight practices.

Green, Walter S.↗

NASA NTRS2008

Concept of Operations Visualization in Support of Ares I Production

Boeing was selected in 2007 to manufacture Ares I Upper Stage and Instrument Unit according to NASA's design which would require the use of the latest manufacturing and integration processes to meet NASA budget and schedule targets. Past production experience has established that the majority of the life cycle cost is established during the initial design process. Concept of Operations (CONOPs) visualizations/simulations help to reduce life cycle cost during the early design stage. Production and operation visualizations can reduce tooling, factory capacity, safety, and build process risks while spreading program support across government, academic, media and public constituencies. The NASA/Boeing production visualization (DELMIA; Digital Enterprise Lean Manufacturing Interactive Application) promotes timely, concurrent and collaborative producibility analysis (Boeing)while supporting Upper Stage Design Cycles (NASA). The DELMIA CONOPs visualization reduced overall Upper Stage production flow time at the manufacturing facility by over 100 man-days to 312.5 man-days and helped to identify technical access issues. The NASA/Boeing Interactive Concept of Operations (ICON) provides interactive access to Ares using real mission parameters, allows users to configure the mission which encourages ownership and identifies areas for improvement, allows mission operations or spacecraft detail to be added as needed, and provides an effective, low coast advocacy, outreach and education tool.

Chilton, James H.↗

NASA NTRS2022

National Campaign (NC)-1 Strategic Conflict Management Simulation (X4) Final Report

Urban Air Mobility (UAM) enables highly automated, cooperative, passenger or cargo-carrying air transportation services in and around urban areas. UAM is a subset of the Advanced Air Mobility (AAM) concept under development by the National Aeronautics and Space Administration (NASA), the Federal Aviation Administration (FAA), and industry. The Strategic Conflict Management (SCM) Simulation, dubbed “X4”, was conducted between July 2021 and June 2022 by NASA with the FAA and industry to evolve the Provider of Services for UAM (PSU) that will be needed to ensure initial UAM operations can scale in the National Airspace System (NAS). The FAA UAM Concept of Operations (ConOps) v1 [1] served as an initial guiding document for the X4 airspace management system design to ensure the architecture supports testing of services provided by third-party service providers. To that end, the X4 architecture leveraged concepts and technologies developed for Unmanned Aircraft System (UAS) Traffic Management (UTM) while also developing and testing new capabilities and services needed for UAM. The architecture included an initial prototype of the FAA-Industry Exchange Protocol (FIDXP), third-party services such as the PSUs, and Discovery and Synchronization Service (DSS), and other new services such as Demand-Capacity Balancing (DCB) to facilitate UAM strategic conflict management. During X4, NASA led discussions and collaborated with seven industry airspace partners to develop initial airspace management concepts for UAM that drove what would be tested and evaluated during the simulations. The initial capabilities defined for PSU leveraged UTM UAS Service Supplier (USS) as a starting point and evolved to meet UAM requirements. These discussions were also an opportunity for NASA to collaborate with industry to develop a set of initial Community-Based Rules (CBRs). These CBRs enabled how UAM traffic would be cooperatively managed among UAM operators. The collaborative, iterative process of developing CBRs with industry during X4 provided insight into the challenges involved and identified the need for a suitable and effective forum for future CBR development. In parallel with these discussions, NASA conducted a series of seven software sprints and two collaborative simulations with the airspace partners that built up in complexity. Over the course of the year, all seven partners successfully completed all the sprints by demonstrating the required capabilities. They also participated in the two collaborative simulations to demonstrate how multiple PSUs could work together in a collaborative, more complex environment with higher traffic density. The X4 simulation accomplished NASA's objectives and helped advance the development of the seven participating PSUs. The lessons learned provided insight into key elements of the UAM Notional Architecture from the FAA ConOps v1 [1] and UTM technologies when applied to UAM: - Having a Concept of Use (ConUse) defined prior to the activity would accelerate the time and effort from concept development to testing. - While the UAM Notional Architecture provided a starting point for a federated architecture that support services provided by third-party providers, the USS and PSU differed in their capability definitions for operational intent submission and sharing, conformance monitoring, airspace authorization, strategic conflict management, airspace constraints and dynamic replanning. - While existing DSS developed for UTM provided a way for PSU and other UAM services (such as DCB) to discover relevant operations from each other, additional complexity and challenges were found during X4 testing and illuminated the need for a more suitable solution for UAM. Industry can leverage the results of this demonstration to accelerate UAM requirements, CBRs, and standards development. The FAA and other government municipalities and agencies will be able to leverage results to inform future policies and identify additional gaps that require further analysis, moving toward operationalization of UAM.

Urban Air Mobility↗

NASA NTRSDate not supplied

TriTruss Packaging and Deployment Trade Study

An architecture and feasibility study of next generation In-Space Assembled Telescopes (iSAT) concluded that robotic in-space assembly of modular components is necessary to enable large (>15-meter diameter) primary apertures. The iSAT study recommended that the foundational structure be assembled from modular TriTruss modules that are packaged for launch, deployed on-orbit and robotically assembled into the final configuration. This paper will describe and summarize the results of a trade study that investigated viable concept of operations (ConOps) for the packaging and deployment (P&D) of individual planar TriTruss modules that could be assembled to form a large aperture iSAT. The ideal TriTruss P&D concept is defined as one that: allows for efficient packaging; has sufficient geometric versatility to be launch vehicle independent; provides a stiff and lightweight structure; has low mechanical complexity; and has component modularity. The P&D concept should allow for prelaunch subsystem or utility integration if required. The concept would be kinematically simple and be robotically deployed using a minimum number of specialized tools. In this first phase of an ongoing more comprehensive trade study, concepts were proposed and then evaluated based on initial metrics representing features of an ideal P&D concept. The P&D concepts evaluated are categorized as: core collapse, face collapse, and erectable structures. Sub-scale models were constructed to help understand the kinematics and mechanical complexity required to enable P&D. Based on a weighting scale, the most promising candidate P&D concepts have selected and will undergo more rigorous structural design, analysis, and testing in the study’s next phase. The ultimate goal of the comprehensive trade study will be to recommend a single TriTruss design and associated P&D concept that will be built and evaluated at NASA Langley Research Center’s In-Space Assembly Laboratory.

in-space assembly (ISA)↗

NASA NTRSDate not supplied

Developing a Medical System Concept of Operations for Level of Care IV: Long-Duration Lunar Orbital and Surface Operations

A goal of the Human Research Program (HRP) Exploration Medical Capability (ExMC) Element Systems Engineering (SE) team is to define the technical system needed to support crew medical system capabilities for future exploration missions, including a mission with lunar orbital and long duration surface operations. The medical system concept of operations (ConOps) is the starting point of creating a foundation for a medical system that meets Level of Care IV requirements, as defined by NASA’s space flight human-system standards. This ConOps illustrates how NASA can provide a Level of Care IV medical system for crews within the various cis-lunar orbit and lunar surface habitat environments. The use case scenarios included in this ConOps illustrate required medical system capabilities for Level of Care IV and enable the ExMC SE team to develop integrated medical system requirements and identify capabilities required to meet those requirements. This discussion will focus on how this concept of operations was constructed – by utilizing the lessons learned from ExMC’s existing Short-Duration Lunar Orbit Medical System Concept of Operations, by employing Model-Based Systems Engineering, and by collaborating with stakeholders in order to ensure the necessary assumptions were made.

M. Kaetzer↗

NASA NTRS2005

Analysis of Wake VAS Benefits Using ACES Build 3.2.1: VAMS Type 1 Assessment

The FAA and NASA are currently engaged in a Wake Turbulence Research Program to revise wake turbulence separation standards, procedures, and criteria to increase airport capacity while maintaining or increasing safety. The research program is divided into three phases: Phase I near term procedural enhancements; Phase II wind dependent Wake Vortex Advisory System (WakeVAS) Concepts of Operations (ConOps); and Phase III farther term ConOps based on wake prediction and sensing. The Phase III Wake VAS ConOps is one element of the Virtual Airspace Modelling and Simulation (VAMS) program blended concepts for enhancing the total system wide capacity of the National Airspace System (NAS). This report contains a VAMS Program Type 1 (stand-alone) assessment of the expected capacity benefits of Wake VAS at the 35 FAA Benchmark Airports and determines the consequent reduction in delay using the Airspace Concepts Evaluation System (ACES) Build 3.2.1 simulator.

Smith, Jeremy C.↗

NASA NTRS2006

Tools to Support Human Factors and Systems Engineering Interactions During Early Analysis

We describe an approach and existing software tool support for effective interactions between human factors engineers and systems engineers in early analysis activities during system acquisition. We examine the tasks performed during this stage, emphasizing those tasks where system engineers and human engineers interact. The Concept of Operations (ConOps) document is an important product during this phase, and particular attention is paid to its influences on subsequent acquisition activities. Understanding this influence helps ConOps authors describe a complete system concept that guides subsequent acquisition activities. We identify commonly used system engineering and human engineering tools and examine how they can support the specific tasks associated with system definition. We identify possible gaps in the support of these tasks, the largest of which appears to be creating the ConOps document itself. Finally, we outline the goals of our future empirical investigations of tools to support system concept definition.

Thronesbery, Carroll↗

NASA NTRS2005

Tools to Support Human Factors and Systems Engineering Interactions During Early Analysis

Thronesbery, Carroll↗

NASA NTRS2017

U.S. Exploration EVA: ConOps, Interfaces and Test Objectives for Airlocks

NASA is moving forward on defining the xEVA System Architecture and its implications to the spacecraft that host exploration EVA systems. This presentation provides an overview of the latest information for NASA's Concept of Operations (ConOps), Interfaces and corresponding Test Objectives for Airlocks hosting the xEVA System.

Buffington, J.↗

NASA NTRS2016

Human-in-the-Loop Assessment of Alternative Clearances in Interval Management Arrival Operations

Interval Management Alternative Clearances (IMAC) was a human-in-the-loop simulation experiment conducted to explore the Air Traffic Management (ATM) Technology Demonstration (ATD-1) Concept of Operations (ConOps), which combines advanced arrival scheduling, controller decision support tools, and aircraft avionics to enable multiple time deconflicted, efficient arrival streams into a high-density terminal airspace. Interval Management (IM) is designed to support the ATD-1 concept by having an "Ownship" (IM-capable) aircraft achieve or maintain a specific time or distance behind a "Target" (preceding) aircraft. The IM software uses IM clearance information and the Ownship data (route of flight, current location, and wind) entered by the flight crew, and the Target aircraft's Automatic Dependent Surveillance-Broadcast state data, to calculate the airspeed necessary for the IM-equipped aircraft to achieve or maintain the assigned spacing goal.

Baxley, Brian T.↗

NASA NTRSDate not supplied

ETM: Upper Class E Traffic Management

The FAA, along with input from the National Aeronautics and Space Administration (NASA) and industry partners, published an initial Concept of Operations (ConOps) for Upper Class E Traffic Management (ETM). To support the next iteration of the ConOps, NASA Ames Research Center has been investigating several technologies and operating principles that will help enable industry in the system development of a cooperative operating environment. Following in the footsteps of the established Unmanned Aircraft Systems Traffic Management (UTM) concept, ETM will utilize some of the basic system architecture and the community-based theories of cooperation and coordination. The main considerations for ETM as compared to UTM, are the diversity of the vehicle types with varying speed and maneuverability capabilities, the severe stratospheric atmosphere conditions, the potential longevity of the missions, and the assorted operating modes (e.g., transit, loitering, or hovering). TM oriented technologies and proposed operating principles are being tested and assessed in a collaborative evaluation of an initial ETM system in spring of 2024. These slides will be presented to a group of stratospheric operators, informing them on some past work and the next steps in the ETM research.

Upper Class-E Traffic Management (ETM)↗

NASA NTRS2013

Modeling and Evaluating Pilot Performance in NextGen: Review of and Recommendations Regarding Pilot Modeling Efforts, Architectures, and Validation Studies

NextGen operations are associated with a variety of changes to the national airspace system (NAS) including changes to the allocation of roles and responsibilities among operators and automation, the use of new technologies and automation, additional information presented on the flight deck, and the entire concept of operations (ConOps). In the transition to NextGen airspace, aviation and air operations designers need to consider the implications of design or system changes on human performance and the potential for error. To ensure continued safety of the NAS, it will be necessary for researchers to evaluate design concepts and potential NextGen scenarios well before implementation. One approach for such evaluations is through human performance modeling. Human performance models (HPMs) provide effective tools for predicting and evaluating operator performance in systems. HPMs offer significant advantages over empirical, human-in-the-loop testing in that (1) they allow detailed analyses of systems that have not yet been built, (2) they offer great flexibility for extensive data collection, (3) they do not require experimental participants, and thus can offer cost and time savings. HPMs differ in their ability to predict performance and safety with NextGen procedures, equipment and ConOps. Models also vary in terms of how they approach human performance (e.g., some focus on cognitive processing, others focus on discrete tasks performed by a human, while others consider perceptual processes), and in terms of their associated validation efforts. The objectives of this research effort were to support the Federal Aviation Administration (FAA) in identifying HPMs that are appropriate for predicting pilot performance in NextGen operations, to provide guidance on how to evaluate the quality of different models, and to identify gaps in pilot performance modeling research, that could guide future research opportunities. This research effort is intended to help the FAA evaluate pilot modeling efforts and select the appropriate tools for future modeling efforts to predict pilot performance in NextGen operations.

pilot human performance models↗

NASA NTRS2019

Space Traffic Management with a NASA UAS Traffic Management (UTM) Inspired Architecture

Space is becoming increasingly congested as the number of on-orbit satellites and debris objects continues to grow. Space traffic management (STM) is critical for ensuring that the expanding orbital population operates safely and efficiently, avoiding collisions and radio-frequency interference while still facilitating widespread space operations. Recent events such as the FCC approval of SpaceX’s ~12,000 satellite constellation, the signing of Space Policy Directive 3 (which moves Space Situational Awareness responsibilities away from the Department of Defense and to a civil agency), and the growth in rideshare and small launch vehicles illustrate the rapidly changing nature of this domain. This paper will describe the concept of operations (ConOps) for a civilian STM research initiative, which has been developed from previous NASA work to enable safe operation of small unmanned aircraft systems. The STM ConOps proposes an architecture to enable efficient data sharing and coordination between participants to facilitate safe spaceflight operations. It is designed to utilize and promote the emerging field of commercial STM services, as a complement to existing government-provided STM services. The concept envisions a phased evolution that would gradually integrate additional capabilities, proposing a first phase architecture and tentative plans for a broader system. Work towards developing an STM research and prototyping platform is also discussed.

UTM↗