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.
Contingency management is essential to the robust operation of complex systems such as spacecraft and Unpiloted Aerial Vehicles (UAVs). Automatic contingency handling allows a faster response to unsafe scenarios with reduced human intervention on low-cost and extended missions. Results, applied to the Autonomous Rotorcraft Project and Mars Science Lab, pave the way to more resilient autonomous systems.
The NASA Unmanned Aircraft Systems (UAS) Traffic Management (UTM) Project executed the fourth and final UTM Technical Capability Level demonstration between May and August 2019. Two Federal Aviation Administration (FAA)-designated UAS test sites managed the range, partners, and operations to meet the requirements set forth by the UTM Project. All stakeholders supported the execution of the flight testing through close collaboration. Results of the demonstration indicate the viability of the UTM concept to manage large scale operations and contingencies in an urban environment. The demonstration also provided insight into key technological gaps that must be addressed before such operations are routine, safe, and efficient. Standardization efforts related to UTM and the industry participants of those efforts can leverage the results and experiences of this flight activity to accelerate and more firmly ground forthcoming standards. The FAA and other regulators will be able to leverage results to inform future rule-making and identify additional gaps that require further analysis.
Technical writers role in communicating NASA generated information to public
This document is a product of the joint NASA and FAA Research Transition Team's (RTT) Concept Working Group (CWG) as part of the UAS Traffic Management (UTM) project. The scope of the document covers Technical Capability Level (TCL) 3 of the UTM research path and presents the 1) Terms and Definitions, 2) Foundational Principles, 3) Concept Narratives, 4) Use Cases, 5) Operational Views (OVs), and 6) Roles and Responsibilities of actors interacting within a TCL3 environment. The document includes additional use cases to accompany the RTT CWG Package #2 document.
NASA's UAS Traffic Management (UTM) project concluded its second flight demonstration activity in late October 2016. This activity demonstrated the capabilities and functionality incorporated into its Technical Capability Level 2 (TCL2) concept, which envisions future operations that are low density, capable of being performed over sparsely populated areas, and allow for a concurrent mix of longer duration, beyond visual-line-of-sight flights and shorter flights within visual-line-of-sight (VLOS). To incorporate these features into a flight demonstration, a scenario-based approach was taken to address different aspects of the TCL2 environment and to meet defined objectives. This paper will describe elements of how the flight activity was conducted and present analyses regarding UTM operations, system messages, and alerting as they pertained to meeting the demonstration objectives and shedding light on research questions and lessons learned.NASA was able to successfully demonstrate complex UTMoperations in a TCL 2 environment in collaboration withindustry partners and the Reno-Stead Airport UAS test range.A scenario-based approach to the demonstration provided arelevant means through which the key elements and objectivesof the test could be captured. Although issues were identifiedthrough the testing and feedback of test participants, theoverall results were in line with the overall UTM objective ofsafely enabling large-scale UAS operations in low altitudeairspace.
NASA's UTM project is conducting research on a traffic management concept for small unmanned aircraft systems (UAS) flying in low altitude, uncontrolled airspace. The project started in 2015 and is developing prototype UTM systems of successively complex technical capability levels (TCL) that are tested in the field. To date TCL levels 1-3 have been tested and TCL 4 will be tested in the summer of 2019. Project results are transferred to the FAA and industry to advance the adoption, implementation, and design standards of future UTM systems.
NASA's UAS Traffic Management (UTM) Project has been tasked with developing concepts and initial implementations for integrating and managing small unmanned aircraft systems (UAS) into the low altitude airspace. To accomplish this task, the Project planned a phased approach based on four Technical Capability Levels (TCLs). As of this writing, TCL4 is currently in development for a late Spring 2019 flight demonstration. This TCL is focused on operations in an urban environment and includes the handling of high density and large-scale off-nominal conditions, vehicle-to-vehicle communications, detect-and-avoid technologies, communication requirements, public safety operations, airspace restrictions, and other related goals. Through research and testing to date, NASA has developed an architecture for UTM that depends on commercial entities collaboratively providing services that are traditionally provided by the Air Navigation Service Provider(ANSP) in manned aviation. A key component of this architecture is the UAS Service Supplier (USS), which acts as a communications bridge between UAS operators and the ANSP when necessary. In addition, the collection of USSs form a USS Network to collaboratively manage the airspace through the sharing of data and the adherence to a standard or set of standards required to participate in this USS Network. This document provides a record of the first step in the development of interoperable USSs that will ultimately support TCL4 flight testing and formalization of the overall UTM concept. To develop these USSs and the underlying specifications for them, NASA has planned a series of "Sprints" to work with industry partners in implementing the features and proposed specifications for USSs to participate in TCL4. This report describes Sprint One. In this Sprint, the focus was on establishing a baseline for the Application Programming Interfaces (APIs) and their associated data models. In addition, the concept of UAS Volume Reservations (UVR) (areas that impose restrictions on sUAS that are allowed to operate) was tested. NASA provided the specifications and iterated on them with partners while implementers developed to those specifications. NASA then tested each partner's implementation to ensure compatibility with all other implementers. This process helped all stakeholders gain confidence that the foundation for future Sprints was solid.
NASA's UAS Traffic Management (UTM) Project has been tasked with developing concepts and initial implementations for integrating and managing small unmanned aircraft systems (UAS) into the low altitude airspace. To accomplish this task, the UTM Project planned a phased approach based on four Technical Capability Levels (TCLs). As of this writing, TCL4 is currently in development for a late Spring 2019 flight demonstration. This TCL is focused on operations in an urban environment and includes the handling of high density environments, large-scale off-nominal conditions, vehicle-to-vehicle communications, detect-and-avoid technologies, communication requirements, public safety operations, airspace restrictions, and other related goals. Through research and testing to date, NASA has developed an architecture for UTM that depends on commercial entities collaboratively providing services that are traditionally provided by the Air Navigation Service Provider (ANSP) in manned aviation. A key component of this architecture is the UAS Service Supplier (USS), which acts as a communications bridge between UAS operators and the ANSP when necessary. In addition, the collection of USSs form a USS Network to collaboratively manage the airspace through the sharing of data and the adherence to a standard or set of standards required to participate in this USS Network. This document provides a record of the second of four planned steps in the development of interoperable USSs that will ultimately support TCL4 flight testing and formalization of the overall UTM concept. To develop these USSs and their underlying specifications, NASA has planned a series of "Sprints" to work with industry partners in implementing the features and develop proposed specifications for USSs in order to to participate in TCL4. This report describes Sprint Two. In this Sprint, there was a major theme with four goals. The theme was the development and testing of a new USS discovery system, to better enable USSs to find and communicate with each other. The goals supporting this theme were: participants needed to implement and exercise the discovery service for USS-USS communications; USSs needed to demonstrate strategic deconfliction through operation sharing; the systems were to use discovery to aid in handling off-nominal operations; and finally, there was an investigation of an initial off-nominal reporting capability.
The goal of the Unmanned Aircraft System (UAS) Traffic Management (UTM) effort at NASA is to enable access to low-altitude airspace for small UAS. This goal is being achieved partly through partnerships that NASA has developed with the FAA, other government agencies, the UAS stakeholder community, and the designated FAA UAS Test Sites. This paper reports the technical and operational capabilities demonstrated during the UTM flight demonstration, March 6 through May 30, 2018. The demonstration featured geographically diverse operations, involving FAA UAS Test Sites in Alaska, Nevada, New York, North Dakota, Texas and Virginia. The demonstration leveraged the contributions of 30 partner organizations serving as UAS service suppliers, UAS operators, and/or providers of sensors, surveillance, connectivity, and management roles. Utilizing the UTM architecture developed at NASA, the demonstration explored 11 use cases for small UAS operations to highlight UTM capabilities at what NASA calls “Technical Capability Level (TCL) 3.” TCL 3 is characterized by multiple small UAS safely operating in moderately populated areas and beyond the visual line of sight of their operators. The TCL 3 flights demonstrated the basic feasibility of such operations in the UTM environment, including USS exchanges; communication, navigation and surveillance functions; sense and avoid capabilities; and technologies and procedures to enable them.
Unmanned Aircraft System (UAS) Traffic Management (UTM) refers to the service-based, cooperative approach to the management of small UAS in the National Airspace System that is safe, scalable, and fair. UTM provides the means to manage the airspace in a complementary manner that does not burden the current air traffic control workforce or infrastructure but allows the Air Navigation Service Provider to maintain its regulatory and operational authority of the airspace. A key feature of UTM is the ability to provide operators the means to strategically deconflict operations from others in the airspace through the digital exchange of information via supporting services. Through this approach, the four-dimensional operation volumes that encompass the intent of operators in a given area are discoverable and can be used for airspace awareness as well as planning conflict free operations that account for and avoid other operations. In certain cases, it is also possible to negotiate volume intersections for shared airspace use without the need to re-plan. In the NASA UTM concept, strategic deconfliction is the first layer of three in the overall conflict management model. The three layers of the conflict management model, which follow the International Civil Aviation Organization’s scheme [ICAO 2005] are: strategic conflict management, separate provision, and collision avoidance. In UTM, the strategic layer mostly occurs prior to departure, but is applicable to en route operations with sufficient planning horizon. The initial requirements for a strategic deconfliction capability within UTM are defined in a NASA publication [Rios 2018]. Within the concept and implementation of service-provided strategic deconfliction is the notion of priority. It is understood that there are instances in which an operation requires a priority designation within the UTM system and special handling accordingly to provide situation awareness and facilitate appropriate responses from other airspace users. Examples of situations requiring priority designation include: when an operator declares an emergency due to problems with the vehicle or its immediate surroundings; operations that are in support of certain organizations (e.g., public safety and first responders); or special missions that also require priority use of airspace (e.g., emergency medical deliveries). UAS Volume Reservations (UVRs) also relate to the topic of priority in the sense that the airspace that the volume encompasses has a different status or classification in which unassociated operations must vacate if inside, or avoid if outside, through strategic deconfliction with the volume. Operations that are specially permitted to access the UVR area are typically assigned priority status given the nature of their mission and their associated credentials. The ability to perform strategic deconfliction, handle certain operations with a priority distinction, and establish UVRs that are communicated throughout the UTM system, is predicated on an architecture that has been established through an evolutionary process in response to close collaboration with stakeholders from government and industry. Another important and influential aspect of these capabilities and architecture is the live, distributed flight tests that have been conducted across the Technical Capability Levels (TCLs) that culminated with a set of complex tests performed as part of TCL4 [Rios 2020]. The TCL4 flight test involved two FAA-designated UAS test sites building teams to collaborate with NASA’s UTM Project on the execution of several detailed, small UAS scenarios in urban environments.
NASA performed research and development of technologies and requirements for traffic management of small Unmanned Aircraft Systems (UAS). In this effort, a small UAS off-nominal situation reporting system was developed to capture information from off-nominal situations to understand their nature and reduce occurrences. This Technical Memorandum (TM) describes the reporting system and analysis of 116 off-nominal situation reports from 352 small UAS operations, which were conducted at two flight test ranges in Summer 2019.
No abstract available
Explore the source record for details and available documents.
This paper provides a description of a recent comprehensive Analysis of Alternatives (AoA) for icing research. A team of NASA icing subject matter experts (SMEs) was assembled from NASA’s Glenn and Langley Research Centers, which began by gathering inputs from icing stakeholders in industry, Government, and academia. Those inputs, which were grouped into a number of themes, were used by the SMEs to identify needed icing technical elements. Each of these high-level technical elements included the icing physics, modeling capabilities, and experimental capabilities needed to address a particular element. A multivariable analysis technique called TOPSIS (Technique for Order Preference by Similarity to Ideal Solutions) was then applied to prioritize the technical elements for several potential future realities. A large number of icing research needs were identified and analyzed to determine the highest priorities for NASA key focus areas and those that will endure into the future. The primary outcome of the AoA is the identification of legacy and newly identified capability areas in priority order to guide future investment.
This paper provides a description of a recent comprehensive Analysis of Alternatives (AoA) for icing research. A team of NASA icing subject matter experts (SMEs) was assembled from NASA’s Glenn and Langley Research Centers, which began by gathering inputs from icing stakeholders in industry, Government, and academia. Those inputs, which were grouped into a number of themes, were used by the SMEs to identify needed icing technical elements. Each of these high-level technical elements included the icing physics, modeling capabilities, and experimental capabilities needed to address a particular element. A multivariable analysis technique called TOPSIS (Technique for Order Preference by Similarity to Ideal Solutions) was then applied to prioritize the technical elements for several potential future realities. A large number of icing research needs were identified and analyzed to determine the highest priorities for NASA key focus areas and those that will endure into the future. The primary outcome of the AoA is the identification of legacy and newly identified capability areas in priority order to guide future investment
General background details in the development of a university level technical writing program, based upon the writing tasks of the student's occupations, are summarized. Objectives and methods for unifying the courses of study with the needs of industry are discussed. Four academic course divisions, Industries Technologies, in which preparation and training are offered are: Animal, Horticulture, Agriculture, and Agricultural Business. Occupational competence is cited as the main goal for these programs in which technical writing is to be practically unified through industry. Course descriptions are also provided.
The end-to-end verification of a spacecraft photovoltaic power generation system requires light! Specifically, the standard practice for doing so is the Large Area Pulsed Solar Simulation (LAPSS). A LAPSS test can characterize a photovoltaic system's efficiency via its response to rapidly applied impulses of simulated sunlight. However, a Class D program on a constrained budget and schedule may not have the resources to ship an entire satellite for a LAPSS test alone. Such was the case with the Lunar Atmospheric and Dust Environment Explorer (LADEE) program, which was also averse to the risk of hardware damage during shipment. When the Electrical Power System (EPS) team was denied a spacecraft-level LAPSS test, the lack of an end-to-end power generation test elevated to a project-level technical risk. The team pulled together very limited resources to not only eliminate the risk, but build a process to monitor the health of the system through mission operations. We discuss a process for performing a low-cost, end-to-end test of the LADEE photovoltaic system. The approach combines system-level functional test, panel-level performance results, and periodic inspection (and repair) up until launch. Following launch, mission operations tools are utilized to assess system performance based on a scant amount of data. The process starts in manufacturing at the subcontractor. The panel manufacturer provides functional test and LAPSS data on each individual panel. We apply an initial assumption that the per-panel performance is sufficient to meet the power generation requirements. The manufacturer's data is also carried as the performance allocation for each panel during EPS system modeling and initial mission operations. During integration and test, a high-power, professional theater lamp system provides simulated sunlight to each panel on the spacecraft, thereby permitting a true end-to-end system test. A passing test results in a step response to nearly full-rated current at the appropriate solar array switch in the power system. A metal-halide bulb, infrared imagers, and onboard spacecraft measurements are utilized to minimize risk of thermal damage during test. Data is provided to support test results for both passing and marginal panels. Prior to encapsulation in the launch vehicle, each panel is inspected for damage by the panel manufacturer. Cracked cells or other damage is amended on-site. Because the photovoltaic test system is inexpensive and portable, each repaired panel can be re-verified immediately. Post-launch, the photovoltaic system is again characterized for per-panel deviations from the manufacturer's performance test. This proved especially tricky as the LADEE spacecraft performs only one current measurement on the entire array. The algorithm for Matlab tools to assess panel performance based on spacecraft attitude is discussed. While not as precise and comprehensive as LAPSS, the LADEE approach leverages minimal resources into an ongoing assessment program that can be applied through numerous stages of the mission. The project takes a true Class D approach in assessing the technical value of a spacecraft level performance test versus the programmatic risk of shipping the spacecraft to another facility. The resources required are a fraction of that for a LAPSS test, and is easy to repeat. Further, the test equipment can be handed down to future projects without building an on-site facility.