SEARCH · Search NASA
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.
This paper presents viewgraphs on the development of the Weather Accident Prevention (WxAP) System architecture and Concept of Operation (CONOPS) activities. The topics include: 1) Background Information on System Architecture/CONOPS Activity; 2) Activity Work in Progress; and 3) Anticipated By-Products.
In order to accomplish NASA's Vision for Exploration, while assuring crew safety and productivity, human performance issues must be well integrated into system design from mission conception. To that end, a two-year Technology Development Project (TDP) was funded by NASA Headquarters to develop a systematic method for including the human as a system in NASA's Vision for Exploration. The specific goals of this project are to review current Human Systems Integration (HSI) standards (i.e., industry, military, NASA) and tailor them to selected NASA Exploration activities. Once the methods are proven in the selected domains, a plan will be developed to expand the effort to a wider scope of Exploration activities. The methods will be documented for inclusion in NASA-specific documents (such as the Human Systems Integration Standards, NASA-STD-3000) to be used in future space systems. The current project builds on a previous TDP dealing with Human Factors Engineering processes. That project identified the key phases of the current NASA design lifecycle, and outlined the recommended HFE activities that should be incorporated at each phase. The project also resulted in a prototype of a webbased HFE process tool that could be used to support an ideal HFE development process at NASA. This will help to augment the limited human factors resources available by providing a web-based tool that explains the importance of human factors, teaches a recommended process, and then provides the instructions, templates and examples to carry out the process steps. The HFE activities identified by the previous TDP are being tested in situ for the current effort through support to a specific NASA Exploration activity. Currently, HFE personnel are working with systems engineering personnel to identify HSI impacts for lunar exploration by facilitating the generation of system-level Concepts of Operations (ConOps). For example, medical operations scenarios have been generated for lunar habitation in order to identify HSI requirements for the lunar communications architecture. Throughout these ConOps exercises, HFE personnel are testing various tools and methodologies that have been identified in the literature. A key part of the effort is the identification of optimal processes, methods, and tools for these early development phase activities, such as ConOps, requirements development, and early conceptual design. An overview of the activities completed thus far, as well as the tools and methods investigated will be presented.
This viewgraph presentation reviews issues of health care in space. Some of the issues reviewed are: (1) Physiological adaptation to microgravity, partial gravity, (2) Medical events during spaceflight, (3) Space Vehicle and Environmental and Surface Health Risks, (4) Medical Concept of Operations (CONOPS), (4a) Current CONOPS & Medical Hardware for Shuttle (STS) and ISS, (4b) Planned Exploration Medical CONOPS & Hardware needs, (5) Exploration Plans for Lunar Return Mission & Mars, and (6) Developing Medical Support Systems.
The purpose of this Functional Requirements Document (FRD) is to compile the functional requirements needed to achieve the Access 5 Vision of "operating High Altitude, Long Endurance (HALE) Unmanned Aircraft Systems (UAS) routinely, safely, and reliably in the national airspace system (NAS)" for Step 1. These functional requirements could support the development of a minimum set of policies, procedures and standards by the Federal Aviation Administration (FAA) and various standards organizations. It is envisioned that this comprehensive body of work will enable the FAA to establish and approve regulations to govern safe operation of UAS in the NAS on a routine or daily "file and fly" basis. The approach used to derive the functional requirements found within this FRD was to decompose the operational requirements and objectives identified within the Access 5 Concept of Operations (CONOPS) into the functions needed to routinely and safely operate a HALE UAS in the NAS. As a result, four major functional areas evolved to enable routine and safe UAS operations for an on-demand basis in the NAS. These four major functions are: Aviate, Navigate, Communicate, and Avoid Hazards. All of the functional requirements within this document can be directly traceable to one of these four major functions. Some functions, however, are traceable to several, or even all, of these four major functions. These cross-cutting functional requirements support the "Command / Control: function as well as the "Manage Contingencies" function. The requirements associated to these high-level functions and all of their supporting low-level functions are addressed in subsequent sections of this document.
Based on a previous Civil Tiltrotor (CTR) National Airspace System (NAS) performance analysis study, CTR operations were evaluated over selected routes and terminal airspace configurations assuming noninterference operations (NIO) and runway-independent operations (RIO). This assessment aims to further identify issues associated with these concepts of operations (ConOps), and their dependency on the airspace configuration and interaction with conventional fixed-wing traffic. Safety analysis following a traditional Safety Management System (SMS) methodology was applied to CTR-unique departure and arrival failures in the selected airspace to identify any operational and certification issues. Additional CTR operational cases were then developed to get a broader understanding of issues and gaps that will need to be addressed in future CTR operational studies. Finally, needed enhancements to National Airspace System performance analysis tools were reviewed, and recommendations were made on improvements in these tools that are likely to be required to support future progress toward CTR fleet operations in the Next Generation Air Transportation System (NextGen).
Reacting to potential on-orbit collision risk in an operational environment requires timely and accurate communication and exchange of data, information, and analysis to ensure informed decision-making for safety of flight and responsible use of the shared space environment. To accomplish this mission, it is imperative that all stakeholders effectively manage resources: devoting necessary and potentially intensive resource commitment to responding to high-risk conjunction events and preventing unnecessary expenditure of resources on events of low collision risk. After 10 years of operational experience, the NASA Robotic Conjunction Assessment Risk Analysis (CARA) is modifying its Concept of Operations (CONOPS) to ensure this alignment of collision risk and resource management. This evolution manifests itself in the approach to characterizing, reporting, and refining of collision risk. Implementation of this updated CONOPS is expected to have a demonstrated improvement on the efficacy of JSpOC, CARA, and owner/operator resources.
The runway is a critical resource of any air transport system. It is used for arrivals, departures, and for taxiing aircraft and is universally acknowledged as a constraining factor to capacity for both surface and airspace operations. It follows that investigation of the effective use of runways, both in terms of selection and assignment as well as the timing and sequencing of the traffic is paramount to the efficient traffic flows. Both the German Aerospace Center (DLR) and NASA have developed concepts and tools to improve atomic aspects of coordinated arrival/departure/surface management operations and runway configuration management. In December 2012, NASA entered into a Collaborative Agreement with DLR. Four collaborative work areas were identified, one of which is called "Runway Management." As part of collaborative research in the "Runway Management" area, which is conducted with the DLR Institute of Flight Guidance, located in Braunschweig, the goal is to develop an integrated system comprised of the three DLR tools - arrival, departure, and surface management (collectively referred to as A/D/S-MAN) - and NASA's tactical runway configuration management (TRCM) tool. To achieve this goal, it is critical to prepare a concept of operations (ConOps) detailing how the NASA runway management and DLR arrival, departure, and surface management tools will function together to the benefit of each. To assist with the preparation of the ConOps, the integrated NASA and DLR tools are assessed through a functional analysis method described in this report. The report first provides the highlevel operational environments for air traffic management (ATM) in Germany and in the U.S., and the descriptions of the DLR's A/D/S-MAN and NASA's TRCM tools at the level of details necessary to compliment the purpose of the study. Functional analyses of each tool and a completed functional analysis of an integrated system design are presented next in the report. Future efforts to fully develop the ConOps will include: developing scenarios to fully test environmental, procedural, and data availability assumptions; executing the analysis by a walk-through of the integrated system using these scenarios; defining the appropriate role of operators in terms of their monitoring requirements and decision authority; executing the analysis by a walk-through of the integrated system with operator involvement; characterizing the environmental, system data requirements, and operator role assumptions for the ConOps.
NASA is studying conceptual architectures for a "Proving Ground" near the Moon or in high lunar orbit to conduct human space exploration missions that bridge the gap between today's operations with the International Space Station (ISS) and future human exploration of Mars beginning in the 2030s. This paper describes the framework of a concept of operations ("Conops") for candidate activities in the Proving Ground. The Conops discusses broad goals that the Proving Ground might address, such as participation from commercial entities, support for human landings on the Moon, use of mature technologies, and growth of capability through a steady cadence of increasingly ambitious piloted missions. Additional Proving Ground objectives are outlined in a companion paper. Key elements in the Conops include the Orion spacecraft (with mission kits for docking and other specialized operations) and the Space Launch System (SLS) heavy-lift rocket. Potential additions include a new space suit, commercial launch vehicles and logistics carriers, Solar Electric Propulsion (SEP) stages to move elements between different orbits and eventually take them on excursions to deep space, a core module with multiple docking ports, a habitation block, and robotic and piloted lunar landers. The landers might include reusable ascent modules which could remain docked to in-space elements between lunar sorties. A module providing advanced regenerative life support functions could launch to the ISS, and later move to the Proving Ground. The architecture will include infrastructure for launch preparation, communication, mission control, and range safety. The Conops describes notional missions chosen to guide the design of the architecture and its elements. One such mission might be the delivery of a approximately 10-t Transit Habitat element, comanifested with Orion on a Block 1B SLS launcher, to the Proving Ground. In another mission, the architecture might participate in direct human exploration of an asteroidal boulder brought to high lunar orbit by the Asteroid Redirect Mission. The Proving Ground stack could serve as a staging point and tele-operation center for robotic and piloted Moon landings. With the addition of a SEP stage, the architecture could support months-long excursions within and beyond the Earth's sphere of influence, possibly culminating in a year-long mission to land humans on a near-Earth asteroid. In the last case, after returning to near-lunar space, two of the asteroid explorers could join two crewmembers freshly arrived from Earth for a Moon landing, helping to quantify the risk of landing deconditioned crews on Mars. In a conceptual mission particularly stressing to system design, Proving Ground elements could transit to Mars orbit. Other possible design-driving operations include relocation of the stack with no crew on board, the unpiloted journey of the advanced life support module from ISS to the lunar vicinity, excursions to other destinations in near-Earth space, and additional support for Mars exploration in conjunction with the Evolvable Mars Campaign. The Proving Ground Conops concludes with a discussion of aborts and contingency operations
NASA is studying a "Proving Ground" near the Moon to conduct human space exploration missions in preparation for future flights to Mars. This paper describes a concept of operations ("conops") for activities in the Proving Ground, focusing on the construction and use of a mobile Cislunar Transit Habitat capable of months-long excursions within and beyond the Earth-Moon system. Key elements in the conops include the Orion spacecraft (with mission kits for docking and other specialized operations) and the Space Launch System heavy-lift rocket. Potential additions include commercial launch vehicles and logistics carriers, solar electric propulsion stages to move elements between different orbits and eventually take them on excursions to deep space, a node module with multiple docking ports, habitation and life support blocks, and international robotic and piloted lunar landers. The landers might include reusable ascent modules which could remain docked to in-space elements between lunar sorties. The architecture will include infrastructure for launch preparation, communication, mission control, and range safety. The conops describes "case studies" of notional missions chosen to guide the design of the architecture and its elements. One such mission is the delivery of a ~10-ton pressurized element, co-manifested with an Orion on a Block 1B Space Launch System rocket, to the Proving Ground. With a large solar electric propulsion stage, the architecture could enable a year-long mission to land humans on a near-Earth asteroid. In the last case, after returning to near-lunar space, two of the asteroid explorers could join two crewmembers freshly arrived from Earth for a Moon landing, helping to safely quantify the risk of landing deconditioned crews on Mars. The conops also discusses aborts and contingency operations. Early return to Earth may be difficult, especially during later Proving Ground missions. While adding risk, limited-abort conditions provide needed practice for Mars, from which early return is likely to be impossible.
The FINESSE (Field Investigations to Enable Solar System Science and Exploration) team is focused on a science and exploration field-based research program aimed at generating strategic knowledge in preparation for the human and robotic exploration of the Moon, near-Earth asteroids (NEAs) and Phobos and Deimos. We follow the philosophy that "science enables exploration and exploration enables science." 1) FINESSE Science: Understand the effects of volcanism and impacts as dominant planetary processes on the Moon, NEAs, and Phobos & Deimos. 2) FINESSE Exploration: Understand which exploration concepts of operations (ConOps) and capabilities enable and enhance scientific return. To accomplish these objectives, we are conducting an integrated research program focused on scientifically-driven field exploration at Craters of the Moon National Monument and Preserve in Idaho and at the West Clearwater Lake Impact Structure in northern Canada. Field deployments aimed at reconnaissance geology and data acquisition were conducted in 2014 at Craters of the Moon National Monument and Preserve. Targets for data acquisition included selected sites at Kings Bowl eruptive fissure, lava field and blowout crater, Inferno Chasm vent and outflow channel, North Crater lava flow and Highway lava flow. Field investigation included (1) differential GPS (dGPS) measurements of lava flows, channels (and ejecta block at Kings Bowl); (2) LiDAR imaging of lava flow margins, surfaces and other selected features; (3) digital photographic documentation; (4) sampling for geochemical and petrographic analysis; (5) UAV aerial imagery of Kings Bowl and Inferno Chasm features; and (6) geologic assessment of targets and potential new targets. Over the course of the 5-week field FINESSE campaign to the West Clearwater Impact Structure (WCIS) in 2014, the team focused on several WCIS research topics, including impactites, central uplift formation, the impact-generated hydrothermal system, multichronometer dating of impact products, and using WCIS as an analog test site for crew studies of sampling protocols. The FINESSE team visited and mapped all of the major islands within West Clearwater Lake. Excellent cliff exposures around the coasts of many of the islands allowed a general stratigraphy of impactites to be defined. Notable differences to previous work includes the discovery of a monomict lithic breccia and a medium to coarse grained impact melt rock. In addition, ample rock samples were returned from West Clearwater for geochronology study. Geochronology work centers around laboratory analyses of these samples (and samples collected in the future or obtained from archives housed at the Canadian Geological Survey). Samples returned from the FINESSE field season have been evaluated for suitability for geochronologic analysis, and selected samples have been crushed for mineral separation and/or sawed for the preparation of polished petrologic thin sections. Heavy minerals (e.g., zircon, titanite, and apatite) will be separated from the crushed material for (U-Th)/He geochronology. The sections will be used for laser ablation 40Ar/39Ar research after neutron irradiation. This presentation will highlight the exciting science and exploration work conducted by FINESSE, as well as future plans for continued research.
This document is derived from the former National Aeronautics and Space Administration (NASA) Constellation Program (CxP) document CxP 70023, titled "The Design Specification for Natural Environments (DSNE), Revision C." The original document has been modified to represent updated Design Reference Missions (DRMs) for the NASA Exploration Systems Development (ESD) Programs. The DSNE completes environment-related specifications for architecture, system-level, and lower-tier documents by specifying the ranges of environmental conditions that must be accounted for by NASA ESD Programs. To assure clarity and consistency, and to prevent requirements documents from becoming cluttered with extensive amounts of technical material, natural environment specifications have been compiled into this document. The intent is to keep a unified specification for natural environments that each Program calls out for appropriate application. This document defines the natural environments parameter limits (maximum and minimum values, energy spectra, or precise model inputs, assumptions, model options, etc.), for all ESD Programs. These environments are developed by the NASA Marshall Space Flight Center (MSFC) Natural Environments Branch (MSFC organization code: EV44). Many of the parameter limits are based on experience with previous programs, such as the Space Shuttle Program. The parameter limits contain no margin and are meant to be evaluated individually to ensure they are reasonable (i.e., do not apply unrealistic extreme-on-extreme conditions). The natural environments specifications in this document should be accounted for by robust design of the flight vehicle and support systems. However, it is understood that in some cases the Programs will find it more effective to account for portions of the environment ranges by operational mitigation or acceptance of risk in accordance with an appropriate program risk management plan and/or hazard analysis process. The DSNE is not intended as a definition of operational models or operational constraints, nor is it adequate, alone, for ground facilities which may have additional requirements (for example, building codes and local environmental constraints). "Natural environments," as the term is used here, refers to the environments that are not the result of intended human activity or intervention. It consists of a variety of external environmental factors (most of natural origin and a few of human origin) which impose restrictions or otherwise impact the development or operation of flight vehicles and destination surface systems. These natural environments include the following types of environments: Terrestrial environments at launch, abort, and normal landing sites (winds, temperatures, pressures, surface roughness, sea conditions, etc.); Space environments (ionizing radiation, orbital debris, meteoroids, thermosphere density, plasma, solar, Earth, and lunar-emitted thermal radiation, etc.); Destination environments (Lunar surface and orbital, Mars atmosphere and surface, near Earth asteroids, etc.). Many of the environmental specifications in this document are based on models, data, and environment descriptions contained in the CxP 70044, Constellation Program Natural Environment Definition for Design (NEDD). The NEDD provides additional detailed environment data and model descriptions to support analytical studies for ESD Programs. For background information on specific environments and their effects on spacecraft design and operations, the environment models, and the data used to generate the specifications contained in the DSNE, the reader is referred to the NEDD paragraphs listed in each section of the DSNE. Also, most of the environmental specifications in this document are tied specifically to the ESD DRMs in ESD-10012, Revision B, Exploration Systems Development Concept of Operations (ConOps). Coordination between these environment specifications and the DRMs must be maintained. This document should be compatible with the current ESD DRMs, but updates to the mission definitions and variations in interpretation may require adjustments to the environment specifications.
For the first time since the Apollo era, NASA is planning on sending astronauts on flights beyond LEO. The Human Space Flight (HSF) program started with a successful initial flight in Earth orbit, in December 2014. The program will continue with two Exploration Missions (EM): EM-1 will be unmanned and EM-2, carrying astronauts, will follow. NASA established a multi-center team to address the communications, and related tacking/navigation needs. This paper will focus on the lessons learned by the team designing the architecture and operations for the missions. Many of these Beyond Earth Orbit lessons had to be re-learned, as the HSF program has operated for many years in Earth orbit. Unlike the Apollo missions that were largely tracked by a dedicated ground network, the HSF planned missions will be tracked (at distances beyond GEO) by the DSN, a network that mostly serves robotic missions. There have been surprising challenges to the DSN as unique modern human spaceflight needs stretch the experience base beyond that of tracking robotic missions in deep space. Close interaction between the DSN and the HSF community to understand the unique needs (e.g. 2-way voice) resulted in a Concept of Operations (ConOps) that leverages both the deep space robotic and the Human LEO experiences. Several examples will be used to highlight the unique challenges the team faced in establishing the communications and tracking capabilities for HSF missions beyond Earth Orbit, including: Navigation. At LEO, HSF missions can rely on GPS devices for orbit determination. For Lunar-and-beyond HSF missions, techniques such as precision 2-way and 3-way Doppler and ranging, Delta-Difference-of-range, and eventually possibly on-board navigation will be used. At the same time, HSF presents a challenge to navigators, beyond those presented by robotic missions - navigating a dynamic/"noisy" spacecraft. Impact of latency - the delay associated with Round-Trip-Light-Time (RTLT). Imagine trying to have a 2-way discussion (audio or video) with an astronaut, with a 2-3 sec or more delay inserted (for lunar distances) or 20 minutes delay (for Mars distances). Balanced communications link. For robotic missions, there has been a heavy emphasis on higher downlink data rates, e.g. bringing back science data. Higher uplink data rates were of secondary importance, as uplink was used only to send commands (and occasionally small files) to the spacecraft. The ratio of downlink-to-uplink data rates was often 10:1 or more. For HSF, a continuous forward link is established and rates for uplink and downlink are more similar.
This paper describes the results of a set of experiments and analyses conducted to evaluate the capability of small unmanned aircraft systems (sUAS) to spot nascent fires in the Great Dismal Swamp (GDS) National Wildlife Refuge. This work is the result of a partnership between the National Aeronautics and Space Administration and the US Fish and Wildlife service specifically to investigate sUAS usage for fire-spotting. The objectives of the current effort were to: 1) Determine suitability and utility of low-cost Small Unmanned Aircraft Systems (sUAS) to detect nascent fires at GDS; 2) Identify and assess the necessary National Airspace System (NAS) integration issues; and 3) Provide information to GDS and the community on system requirements and concepts-of-operation (CONOPS) for conducting fire detection/support mission in the National Airspace and (4) Identify potential applications of intelligent autonomy that would enable or benefit this high-value mission. In addition, data on the ability of various low-cost sensors to detect smoke plumes and fire hot spots was generated during the experiments as well as identifying a path towards a future practical mission utility by using sUAS in beyond visual-line-of-sight operation in the National Airspace System (NAS).
The Biologic Analog Science Associated with Lava Terrains (BASALT) project is a multi-year program dedicated to iteratively develop, implement, and evaluate concepts of operations (ConOps) and supporting capabilities intended to enable and enhance human scientific exploration of Mars. This pa-per describes the planning, execution, and initial results from the first field deployment, referred to as BASALT-1, which consisted of a series of 10 simulated extravehicular activities (EVAs) on volcanic flows in Idaho's Craters of the Moon (COTM) National Monument. The ConOps and capabilities deployed and tested during BASALT-1 were based on previous NASA trade studies and analog testing. Our primary research question was whether those ConOps and capabilities work acceptably when performing real (non-simulated) biological and geological scientific exploration under 4 different Mars-to-Earth communication conditions: 5 and 15 min one-way light time (OWLT) communication latencies and low (0.512 Mb/s uplink, 1.54 Mb/s downlink) and high (5.0 Mb/s uplink, 10.0 Mb/s downlink) bandwidth conditions representing the lower and higher limits of technical communication capabilities currently proposed for future human exploration missions. The synthesized results of BASALT-1 with respect to the ConOps and capabilities assessment were derived from a variety of sources, including EVA task timing data, network analytic data, and subjective ratings and comments regarding the scientific and operational acceptability of the ConOp and the extent to which specific capabilities were enabling and enhancing, and are presented here. BASALT-1 established preliminary findings that baseline ConOp, software systems, and communication protocols were scientifically and operationally acceptable with minor improvements desired by the "Mars" extravehicular (EV) and intravehicular (IV) crewmembers, but unacceptable with improvements required by the "Earth" Mission Support Center. These data will provide a basis for guiding and prioritizing capability development for future BASALT deployments and, ultimately, future human exploration missions.
The Biologic Analog Science Associated with Lava Terrains (BASALT) project is a four-year program dedicated to iteratively designing, implementing, and evaluating concepts of operations (ConOps) and supporting capabilities to enable and enhance scientific exploration for future human Mars missions. The BASALT project has incorporated three field deployments during which real (non-simulated) biological and geochemical field science have been conducted at two high-fidelity Mars analog locations under simulated Mars mission conditions, including communication delays and data transmission limitations. BASALT's primary Science objective has been to extract basaltic samples for the purpose of investigating how microbial communities and habitability correlate with the physical and geochemical characteristics of chemically altered basalt environments. Field sites include the active East Rift Zone on the Big Island of Hawai'i, reminiscent of early Mars when basaltic volcanism and interaction with water were widespread, and the dormant eastern Snake River Plain in Idaho, similar to present-day Mars where basaltic volcanism is rare and most evidence for volcano-driven hydrothermal activity is relict. BASALT's primary Science Operations objective has been to investigate exploration ConOps and capabilities that facilitate scientific return during human-robotic exploration under Mars mission constraints. Each field deployment has consisted of ten extravehicular activities (EVAs) on the volcanic flows in which crews of two extravehicular and two intravehicular crewmembers conducted the field science while communicating across time delay and under bandwidth constraints with an Earth-based Mission Support Center (MSC) comprised of expert scientists and operators. Communication latencies of 5 and 15 min one-way light time and low (0.512 Mb/s uplink, 1.54 Mb/s downlink) and high (5.0 Mb/s uplink, 10.0 Mb/s downlink) bandwidth conditions were evaluated. EVA crewmembers communicated with the MSC via voice and text messaging. They also provided scientific instrument data, still imagery, video streams from chest-mounted cameras, GPS location tracking information. The MSC monitored and reviewed incoming data from the field across delay and provided recommendations for pre-sampling and sampling tasks based on their collective expertise. The scientists used dynamic priority ranking lists, referred to as dynamic leaderboards, to track and rank candidate samples relative to one another and against the science objectives for the current EVA and the overall mission. Updates to the dynamic leaderboards throughout the EVA were relayed regularly to the IV crewmembers. The use of these leaderboards enabled the crew to track the dynamic nature of the MSC recommendations and helped minimize crew idle time (defined as time spent waiting for input from Earth during which no other productive tasks are being performed). EVA timelines were strategically designed to enable continuous (delayed) feedback from an Earth-based Science Team while simultaneously minimizing crew idle time. Such timelines are operationally advantageous, reducing transport costs by eliminating the need for crews to return to the same locations on multiple EVAs while still providing opportunities for recommendations from science experts on Earth, and scientifically advantageous by minimizing the potential for cross-contamination across sites. This paper will highlight the space-to-ground interaction results from the three BASALT field deployments, including planned versus actual EVA timeline data, ground assimilation times (defined as the amount of time available to the MSC to provide input to the crew), and idle time. Furthermore, we describe how these results vary under the different communication latency and bandwidth conditions. Together, these data will provide a basis for guiding and prioritizing capability development for future human exploration missions.
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.
An economic impact market analysis was conducted for 16 leading sectors of commercial Unmanned Aerial System (UAS) applications predicted to be enabled by 2020 through the NASA UAS Traffic Management (UTM) program. Subject matter experts from seven industries were interviewed to validate concept of operations (ConOps) and market adoption assumptions for each sector. The market analysis was used to estimate direct economic impacts for each sector including serviceable addressable market, capital investment, revenue recovery potential, and operations cost savings. The resultant economic picture distinguishes the agricultural, pipeline and railroad inspection, construction, and maritime sectors of the nascent commercial UAS industry as providing the highest potential economic value in the United States. Sensitivity studies characterized the variability of select UAS sectors economic value to key regulatory or UTM ConOps requirements such as weight, altitude, and flight over populated area constraints. Takeaways from the analysis inform the validation of UTM requirements, technologies and timetables from a commercial market need and value viewpoint. This work concluded in August 2015 and reflects the state of the UAS industry and market projections at that time.
This paper will discuss a different approach to the typical notional small package delivery drone concept. Most delivery drone concepts employ a point-to-point aerial delivery CONOPS (Concept of Operations) from a warehouse directly to the front or back yards of a customers residence or a commercial office space. Instead, the proposed approach is somewhat analogous to current postal deliveries: a small aerial vehicle flies from a warehouse to designated neighborhood VTOL (Vertical Take-Off and Landing) landing spots where the aerial vehicle then converts to a "roadable" (ground-mobility) vehicle that then transits on sidewalks and/or bicycle paths till it arrives to the residence/office drop-off points. This concept and associated platform or vehicle will be referred in this paper as MICHAEL (Multimodal Intra-City Hauling and Aerial-Effected Logistics) concept. It is suggested that the MICHAEL concept potentially results in a more community friendly "delivery drone" approach.