Search NASASearch

SEARCH · Search NASA

Results for “incident command post”

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.

Mobile satellite communications in the Forest Service

There are usually some places within a forest that do not have adequate communication coverage due to line-of-sight or other reasons. These areas are generally known by the foresters and radio technicians and allowances are made for that when working or traveling in those areas. However, when wildfire or other emergencies occur, communications are vital because wildfires can require hundreds of firefighters and cover thousands of acres. During these emergency operations, the existing communications are not adequate and complete radio systems are moved into the area for the conduct of fire communications. Incident command posts (ICPs) and fire camps are set up in remote locations and there is constant need for communications in the fire area and to agency headquarters and dispatch offices. Mobile satellite communications would be an ideal supplement to the Forest Service's current communications system in aiding forest fire control activities.

Warren, John R.

Open Data Integration (ODIN): A Concurrent, Distributed Message-Based Architecture and Framework for Disaster Response

The Runtime for Airspace Concept Evaluation (RACE) is an open-source software architecture and framework to build configurable, highly concurrent and distributed message-based systems that offer scalable, low-latency performance on commodity hardware. RACE was used in commercial aviation applications to rapidly build systems that span several machines (including synchronized displays), interface existing hardware simulators and other live data feeds, and incorporate sophisticated visualization components such as NASA WorldWind. These RACE applications validated elements of the FAA’s System Wide Information Management (SWIM) Program, handling up to 1000 messages/sec from diverse sources (SFDPS, TFM-DATA, TAIS, ASDE-X, ITWS and local ADS) for 4,500 simultaneous flights tracked in the next-generation air transportation system’s digital backbone. We have since generalized RACE to support Open Data Integration (ODIN) applications outside aviation. Systems built with RACE/ODIN can be deployed in the field, on commodity hardware, and operate with limited or intermittent connectivity to the outside world. Our primary use case is a web-server with local/persistent data storage that runs within and only serves the stakeholder network (e.g. an incident command post). We are tailoring the RACE/ODIN system to support wildland fire management for the upcoming NASA Wildland Fire Safety Demonstration Series. RACE-ODIN is under consideration for application in the Scalable Traffic Management for Emergency Response Operations project, or STEReO, which aims to create a system that can be deployed during emergencies, to coordinate multiple elements of disaster response. Such data sources predominantly come from existing services on the internet (e.g. weather and satellite data, imported from so called "edge servers") but can also include dynamic (real-time) data from computer simulations and within the stakeholder network (such as aircraft and personnel tracking information). We will present the architecture and ODIN system demonstration incorporating local data from instrumented power-line towers, interpolated weather data and geospatial data from space-based platforms.

Joseph C Coughlan

Open Data Integration (ODIN): A Concurrent, Distributed Message-Based Architecture and Framework for Disaster Response

The Runtime for Airspace Concept Evaluation (RACE) is an open-source software architecture and framework to build configurable, highly concurrent and distributed message-based systems that offer scalable, low-latency performance on commodity hardware. RACE was used in commercial aviation applications to rapidly build systems that span several machines (including synchronized displays), interface existing hardware simulators and other live data feeds, and incorporate sophisticated visualization components such as NASA WorldWind. These RACE applications validated elements of the FAA’s System Wide Information Management (SWIM) Program, handling up to 1000 messages/sec from diverse sources (SFDPS, TFM-DATA, TAIS, ASDE-X, ITWS and local ADS) for 4,500 simultaneous flights tracked in the next-generation air transportation system’s digital backbone. We have since generalized RACE to support Open Data Integration (ODIN) applications outside aviation. Systems built with RACE/ODIN can be deployed in the field, on commodity hardware, and operate with limited or intermittent connectivity to the outside world. Our primary use case is a web-server with local/persistent data storage that runs within and only serves the stakeholder network (e.g. an incident command post). We are tailoring the RACE/ODIN system to support wildland fire management for the upcoming NASA Wildland Fire Safety Demonstration Series. RACE-ODIN is under consideration for application in the Scalable Traffic Management for Emergency Response Operations project, or STEReO, which aims to create a system that can be deployed during emergencies, to coordinate multiple elements of disaster response. Such data sources predominantly come from existing services on the internet (e.g. weather and satellite data, imported from so called "edge servers") but can also include dynamic (real-time) data from computer simulations and within the stakeholder network (such as aircraft and personnel tracking information). We will present the architecture and ODIN system demonstration incorporating local data from instrumented power-line towers, interpolated weather data and geospatial data from space-based platforms.

Guillaume P Brat

(ODIN): An Open Source, Low-Latency Data Integration & Visualization Framework for the NASA System Wide Safety Project's Disaster Response Safety Demonstration Series

The Open Data Integration Framework (ODIN) is an open source, low latency data integration and visualization framework (https://github.com/NASARace/race-odin) developed under NASA’s System WideSafety Program to demonstrate new safety capabilities designed to improve US airspace operations. Safety demonstrations are a set of increasingly complex (from public safety perspective) disaster response scenarios under which air systems must operate with increased capacity and include: 1) Wildland fire response, 2) Hurricane relief and recovery, 4) Emergency medical delivery via UAS and 4) Urban disaster relief. To accommodate disaster response, ODIN is field deployable and can scale on one or more multi-core, commodity laptops operating with full to limited or intermittent internet connectivity, conditions likely encountered during operations. ODIN runs as webserver with local, persistent data storage to serve either public or a secured, ad hoc network (e.g., an incident command post). The current released ODIN, ODIN-Fire is tailored for wildland fire management incorporating information on satellite overpasses with links to the near real-time data and imagery from the respective agencies. Included are winds data, an important variable for emergency responders and airspace operations, and high-resolution wind forecasts generated by super-computing resources and ingested into ODIN. As an open-source project, ODIN has attracted interest from multiple entities. We will show how 1) a commercial field instrument and data provider uses ODIN to help users visualize, publish and integrate their in-situ sensor network data and 2) ODIN’s capabilities to ingest, integrate and display near-real time satellite data with air traffic and a USFS winds forecast model used in fire response and post-fire assessment. Within NASA ODIN demonstrated novel, near terminal airspace safety capabilities for a project close-out event and previously it monitored the national airspace in real-time to meet an agency milestone. ODIN is presently under development for the anticipated hurricane relief and response demonstration notionally scheduled for the 2025-27 time frame and is available from NASA's github at the above link.

Aeronautics

Hybrid Powered Command Trailers Cost-Benefit Analysis Tool: User Guide and Examples

U.S. Forest Service (USFS) wildfire base camps use portable power for electrical needs, including yurts and trailers from which logistics staff work during the incident. These yurts and trailers are conventionally powered by portable diesel generators. Hybrid portable power systems consisting of a combination of solar photovoltaics (PV), battery energy storage systems (BESS), and/or backup diesel generators have been used in recent years and were piloted by the National Technology and Development Program (NTDP) on incidents in fall 2024 as part of NTDP's Portable Power Project. As part of that project, this work included the development of two Excel-based tools and two reports explaining the tools. The first tool, the Incident Energy Systems Model, is an Excel-based tool that models the power output of hybrid portable power systems powering yurts and/or trailers at fire camps over a typical day. The associated report (published separately) outlines a user guide for the model and walks through two scenarios. The two scenarios are 1) trailers powered by rooftop solar PV, batteries, and a back-up diesel generator, and 2) trailers powered by ground mount solar PV, batteries, and a back-up diesel generator. The second tool is a high-level cost-benefit analysis of the same two types of portable power systems, and is location independent.

14 SOLAR ENERGY

Incident Energy Systems Model: User Guide and Examples

U.S. Forest Service (USFS) wildfire base camps use portable power for electrical needs, including yurts and trailers from which logistics staff work during the incident. These yurts and trailers are conventionally powered by portable diesel generators. Hybrid portable power systems consisting of a combination of solar photovoltaics (PV), battery energy storage systems (BESS), and/or backup diesel generators have been used in recent years and were piloted by the National Technology and Development Program (NTDP) on incidents in fall 2024 as part of NTDP's Portable Power Project. As part of that project, this work included the development of two Excel-based tools and two reports explaining the tools. The first tool, the Incident Energy Systems Model, is an Excel-based tool that models the power output of hybrid portable power systems powering yurts and/or trailers at fire camps over a typical day.

14 SOLAR ENERGY

Development of a Rover Simulation to Assess Operational Proficiency Following Long Duration Spaceflights

Following long-duration space transits, adaptive changes in sensorimotor and cognitive function may impair the crew s ability to safely control pressurized rovers designed to explore the new environment. We describe a rover simulation developed to quantify post-flight decrements in operational proficiency following International Space Station expeditions. The rover simulation consists of a serial presentation of discrete tasks to be completed as quickly and accurately as possible. Each task consists of 1) perspective taking using a map that defines a docking target, 2) navigation toward the target around a Martian outpost, and 3) docking a side hatch of the rover to a visually guided target. The simulator utilizes a Stewart-type motion base (CKAS, Australia), single seat cabin with triple scene projection covering approximately 150 horizontal by 40 vertical, and joystick controller. The software was implemented using Unity3 with next-gen PhysX engine to tightly synchronize simulation and motion platform commands. Separate C# applications allow investigators to customize session sequences with different lighting and gravitational conditions, and then execute tasks to be performed as well as record performance data. Preliminary tests resulted in low incidence of motion sickness (<15% unable to complete first session), with only negligible after effects and symptoms after familiarization sessions. Functionally relevant testing early post-flight will develop evidence regarding the limitations to early surface operations and what countermeasures are needed. This approach can be easily adapted to other vehicle designs to provide a platform to safely assess how sensorimotor and cognitive function impact manual control performance.

DeDios, Y. E.

Space Shuttle Program (SSP) Orbiter Main Propulsion System (MPS) Gaseous Hydrogen (GH2) Flow Control Valve (FCV) Poppet Eddy Current (EC) Inspection Probability of Detection (POD) Study

The Director of the NASA Engineering and Safety Center (NESC), requested an independent assessment of the anomalous gaseous hydrogen (GH2) flow incident on the Space Shuttle Program (SSP) Orbiter Vehicle (OV)-105 during the Space Transportation System (STS)-126 mission. The main propulsion system (MPS) engine #2 GH2 flow control valve (FCV) LV-57 transition from low towards high flow position without being commanded. Post-flight examination revealed that the FCV LV-57 poppet had experienced a fatigue failure that liberated a section of the poppet flange. The NESC assessment provided a peer review of the computational fluid dynamics (CFD), stress analysis, and impact testing. A probability of detection (POD) study was requested by the SSP Orbiter Project for the eddy current (EC) nondestructive evaluation (NDE) techniques that were developed to inspect the flight FCV poppets. This report contains the findings and recommendations from the NESC assessment.

Piascik, Robert S.

Space Shuttle Program (SSP) Orbiter Main Propulsion System (MPS) Gaseous Hydrogen (GH2) Flow Control Valve (FCV) Poppet Eddy Current (EC) Inspection Probability of Detection (POD) Study: Appendices - Volume 2

The Director of the NASA Engineering and Safety Center (NESC), requested an independent assessment of the anomalous gaseous hydrogen (GH2) flow incident on the Space Shuttle Program (SSP) Orbiter Vehicle (OV)-105 during the Space Transportation System (STS)-126 mission. The main propulsion system (MPS) engine #2 GH2 flow control valve (FCV) LV-57 transition from low towards high flow position without being commanded. Post-flight examination revealed that the FCV LV-57 poppet had experienced a fatigue failure that liberated a section of the poppet flange. The NESC assessment provided a peer review of the computational fluid dynamics (CFD), stress analysis, and impact testing. A probability of detection (POD) study was requested by the SSP Orbiter Project for the eddy current (EC) nondestructive evaluation (NDE) techniques that were developed to inspect the flight FCV poppets. This report contains the Appendices to the main report.

Piascik, Robert S.

2007 Ikhana Western States and Southern California Emergency UAS Fire Missions

Four demonstration and four emergency fire imaging missions completed: a) Thermal infrared imagery delivered in near real-time (5 to 15 minutes) to: 1) SoCal Emergency: FEMA, NIFC, NorthCom, California EOC; 2) Demo Flights: NIFC, Individual Fire Incident Commands. Imagery used for tactical and strategic decision making. Air Traffic Control gave excellent support. Mission plans flown in reverse. Real time requests for revisits of active fires. Added new fire during mission. Moved fire loiter points as fires moved. Real-time reroute around thunderstorm activity. Pre & Post flight telecons with FAA were held to review mission and discuss operational improvements. No issues with air traffic control during the 8 fire missions flown.

Cobleigh, Brent

Infrared Sensor on Unmanned Aircraft Transmits Time-Critical Wildfire Data

Since 2006, NASA fs Dryden Flight Research Center (DFRC) and Ames Research Center have been perfecting and demonstrating a new capability for geolocation of wildfires and the real-time delivery of data to firefighters. Managed for the Western States Fire Mission, the Ames-developed Autonomous Modular Scanner (AMS), mounted beneath a wing of DFRC fs MQ-9 Ikhana remotely piloted aircraft, contains an infrared sensor capable of discriminating temperatures within 0.5 F (approx. = 0.3 C), up to 1,000 F (approx. = 540 C). The AMS operates like a digital camera with specialized filters to detect light energy at visible, infrared, and thermal wavelengths. By placing the AMS aboard unmanned aircraft, one can gather information and imaging for thousands of square miles, and provide critical information about the location, size, and terrain around fires to commanders in the field. In the hands of operational agencies, the benefits of this NASA research and development effort can support nationwide wildfire fighting efforts. The sensor also provides data for post-burn and vegetation regrowth analyses. The MQ-9 Unmanned Aircraft System (UAS), a version of the Predator-B, can operate over long distances, staying aloft for over 24 hours, and controlled via a satellite-linked command and control system. This same link is used to deliver the fire location data directly to fire incident commanders, in less than 10 minutes from the time of overflight. In the current method, similarly equipped short-duration manned aircraft, with limited endurance and range, must land, hand-carry, and process data, and then deliver information to the firefighters, sometimes taking several hours in the process. Meanwhile, many fires would have moved over great distances and changed direction. Speed is critical. The fire incident commanders must assess a very dynamic situation, and task resources such as people, ground equipment, and retardant-dropping aircraft, often in mountainous terrain obscured by dense smoke.

Pestana, Mark

Artemis Sustained Translational Acceleration Limits: Human Tolerance Evidence from Apollo to ISS

The designers of the next generation of lunar landers may adopt novel, crew-body orientations outside of our flight history or applied to flight durations and environments outside of our experience. Current sustained translational acceleration requirements in NASA-STD-3001 are applicable only to crewmembers in a seated posture and are thus inadequate to address human tolerance in non-seated configurations. Initial designs for the Apollo Lunar Module (LM) included seats for both commander and pilot; however, these were subsequently removed from the vehicle due to mass constraints and a willingness to accept the unknown risks for short-duration missions given the limited human physiologic data at the time. In the years since Apollo, our evidence base has grown immensely. Initial Artemis mission timelines under consideration will be longer than the longest Apollo mission, by a significant margin, with timeframes more analogous to longer Space Shuttle missions. Given the incidence of postflight orthostatic intolerance following shuttle missions, a significant risk may exist for lander design(s) pursuing a standing crew configuration similar to Apollo LM. New sustained translational acceleration limits developed to address this risk are presented herein. These limits were derived from evaluations of Apollo biomedical and flight profile data during lunar descent and ascent operations, Soyuz and Space Shuttle flight profile and post-landing biomedical data, and analogue bed rest post-exposure data on orthostatic intolerance.

James M. Pattarini

Airborne Antenna System for Minimum-Cycle-Slip GPS Reception

A system that includes a Global Positioning System (GPS) antenna and associated apparatus for keeping the antenna aimed upward has been developed for use aboard a remote-sensing-survey airplane. The purpose served by the system is to enable minimum- cycle-slip reception of GPS signals used in precise computation of the trajectory of the airplane, without having to restrict the airplane to maneuvers that increase the flight time needed to perform a survey. Cycle slip signifies loss of continuous track of the phase of a signal. Minimum-cycle-slip reception is desirable because maintaining constant track of the phase of the carrier signal from each available GPS satellite is necessary for surveying to centimeter or subcentimeter precision. Even a loss of signal for as short a time as a nanosecond can cause cycle slip. Cycle slips degrade the quality and precision of survey data acquired during a flight. The two principal causes of cycle slip are weakness of signals and multipath propagation. Heretofore, it has been standard practice to mount a GPS antenna rigidly on top of an airplane, and the radiation pattern of the antenna is typically hemispherical, so that all GPS satellites above the horizon are viewed by the antenna during level flight. When the airplane must be banked for a turn or other maneuver, the reception hemisphere becomes correspondingly tilted; hence, the antenna no longer views satellites that may still be above the Earth horizon but are now below the equatorial plane of the tilted reception hemisphere. Moreover, part of the reception hemisphere (typically, on the inside of a turn) becomes pointed toward ground, with a consequent increase in received noise and, therefore, degradation of GPS measurements. To minimize the likelihood of loss of signal and cycle slip, bank angles of remote-sensing survey airplanes have generally been limited to 10 or less, resulting in skidding or slipping uncoordinated turns. An airplane must be banked in order to make a coordinated turn. For small-radius, short-time coordinated turns, it is necessary to employ banks as steep as 45 , and turns involving such banks are times and for confining airplanes as closely as possible to areas to be surveyed. The idea underlying the design is that if the antenna can be kept properly aimed, then the incidence of cycle slips caused by loss or weakness of signals can be minimized. The system includes an articulating GPS antenna and associated electronic circuitry mounted under a radome atop an airplane. The electronic circuitry includes a microprocessor-based interface-circuit-and-data-translation module. The system receives data on the current attitude of the airplane from the inertial navigation system of the airplane. The microprocessor decodes the attitude data and uses them to compute commands for the GPS-antenna-articulating mechanism to tilt the antenna, relative to the airplane, in opposition to the roll or bank of the airplane to keep the antenna pointed toward the zenith. The system was tested aboard the hurricane- hunting airplane of the National Oceanic and Atmospheric Administration (NOAA) [see figure] during an 11-hour flight to observe the landfall of Hurricane Bret in late summer of 1999. No bank-angle restrictions were imposed during the flight. Post-flight analysis of the GPS trajectory data revealed that no cycle slip had occurred.considered normal maneuvers. These steep banks are highly desirable for minimizing flight

Wright, C. Wayne

Titan/Centaur T/C-1 post flight evaluation report

The first Titan/Centaur launch vehicle, TC-1, was launched from the Eastern Test Range Complex 41 at 09:48:01.46 hours Eastern Daylight Time on February 11, 1974. The vehicle carried a dynamic mass model of the Viking spacecraft and a SPHINX spacecraft, intended to study high voltage interactions in space. This launch was a Proof Flight of a vehicle con- figuration integrating the Air Force Titan booster and the NASA Centaur upper stage. It also was the first flight of the Centaur Standard Shroud developed for the Titan/Centaur. The countdown for the launch proceeded normally except for an additional 45 minute hold which was required to resolve a question concerning interpretation of booster hydraulic system data. The launch window opened at 09:03:00 hours Eastern Daylight Time. The vehicle was launched o on a flight azimuth of 105°. The Titan boost phase of flight was satisfactory. Solid Motor operation, Stage I and Stage II operation were normal. Venting of the Centaur Standard Shroud during ascent was successful and shroud separation and jettison was accomplished without incident. At the completion of the Titan Stage II burn, the Centaur successfully separated from the Titan. At this time, the Centaur main engines were sequenced through the first planned starting cycle but failed to achieve steady state operation. The vehicle flight control system, not sensing vehicle acceleration, commanded engine shutdown, and recycled, as programmed, through a back-up engine start attempt. The second engine start attempt was also unsuccessful. The flight control system then placed the vehicle in a coast-phase mode and the vehicle continued downrange in free fall. The vehicle was destroyed by Range Safety when the impact point was approximately 2200 nautical miles downrange, 12 minutes, 28.5 seconds after liftoff.

S. V. Szabo, Jr.

Informing New Concepts for UAS and Autonomous System Safety Management using Disaster Management and First Responder Scenarios

As emerging flight operations become more prevalent and increasingly automated and distributed, the capabilities for managing safety of vehicles and operations will also need to evolve. To address this challenge, the National Academies has envisioned an In-Time Aviation Safety Management System (IASMS) capability for a wide range of aviation operations including current commercial operations as well as new entrants envisioned with advanced air mobility (AAM). The suite of IASMS services, functions, and capabilities (SFCs) would be implemented in a federated approach and would address trends as well as individual operations. Through predictive modeling and data analysis, IASMS is envisioned to identify arising risks so that they can be mitigated, in-time, before a safety incident occurs. IASMS and its requisite set of SFCs must leverage a wide range of information to perform. To better understand these new needs, FSF worked with the aviation and humanitarian communities to develop and validate scenarios that include traditional aviation operations and UAS operations intermingled as they are deployed for disaster management and first responder (DMFR) situations. The three scenarios developed include: • Post Natural disaster response, such as a hurricane, involving multiple parties utilizing traditional aviation and UAS to support rescue operations, surveil damage, and locate survivors needing assistance. • Wildfire fighting in remote locations with traditional aircraft for transport and fire-retardant delivery combined with UAS for surveillance of fire locations as well as to track individual firefighter locations. • Medical Operations and AAM in Urban Environments including passenger-carrying helicopters and AAM vehicles, medical missions (such as transport of radio-pharmaceuticals), and other UAS delivery operations (such as the delivery of defibrillators). Each scenario was developed and validated by representatives with expertise in humanitarian operations, urban and rural emergency response, air traffic management, UAS operations, and traditional flight operations. The scenario definitions address roles and responsibilities of individual actors, the appropriate utilization of UAS, and the actions taken by those actors to appropriately manage risks associated with the mission and environment. The risks to aviation traffic and to people on the ground explored included potential risks arising from incompatibilities in calculating reference altitudes (eg, differing uses of AGL, MSL, barometric, or GPS-derived values), loss of command and control (C2) communications, rapid changes in weather and winds, and physical interference. For each risk, IASMS SFCs were postulated in the context of monitoring services, risk assessment capabilities, and identifying appropriate mitigation strategies. The identified SFC capabilities were envisioned from known services postulated for IASMS and for UTM. For these unique environments, IASMS SFCs are needed to address conditions such as hazardous payloads, micro-climates and urban canyons, and the need to keep uninvolved air traffic out of the area where DMFR operations are being conducted. The second phase of analysis focused on inferring the specific information needs and the SFCs for IASMS, utilizing a structure of 16 information classes to organize requirements. For each of the risks identified in the workshops, it was postulated what data sources would be necessary to monitor critical aspects of the risk (eg, surrounding air traffic, ground population, terrain, etc). to be directly measured as well as data that would be derived, which implies additional SFCs for different actors to understand what information would likely be exchanged between parties. For an IASMS to be effective, additional research is needed to develop the advanced algorithms that can address the increasingly autonomous and complex operations in differing environments and to develop means of identifying unknown risks. Looking at these scenarios highlighted a number of research issues. These include the ability to quickly "cordon off" airspace thru temporary flight restrictions (TFRs) or other means, developing clear definitions to enable automation-based algorithms for prioritizing operations, defining airspace density metrics, standardization of altitude reporting, and establishing a basis for safety data metrics definition and collection. This paper seeks to outline the development of an IASMS in the context of the DMFR scenarios and resulting demonstrations. Utilizing this contextual approach, NASA will generate recommendations for an assured safety framework for AAM operations that enables AAM operations to safely access the NAS.

In Time Aviation Safety Management System

Testing of Advanced Capabilities to Enable In-time Safety Management and Assurance for Future Flight Operations

In order to refine an initial Concept of Operations, explore Concepts of Use, and expose/validate requirements for future In-Time Aviation Safety Management Systems (IASMS), testing architectures were created, along with a set of capabilities and underlying information exchange protocols. These systems were conceived and developed based on hazards associated with two envisioned urban area flight domains: (1) highly autonomous small uncrewed aerial systems (sUAS) operating at low altitudes, and (2) highly autonomous air taxis. The initial scope of this development is described in [1]; this report provides an update, focusing on the subsequent developments and test activities. As stated in [1], it is important to note that there are many capabilities already in use by the industry (or soon to be in use) that will play critical roles in future IASMS designs. Those reported here were developed to address a gap in the current state-of-the-art regarding specific hazards/risks, and/or to allow for investigation of the interplay between and across hazard types — particularly regarding how overall safety risk can be reduced or managed effectively. Results of testing and development activities are organized by the operational phase wherein a particular capability would be employed (i.e., preflight, in-flight, and post-flight/off-line). Pre-flight: A set of capabilities were developed to help mitigate safety risk prior to flight (e.g., during flight and mission planning). Results of testing summarize (1) validation activities to raise the Technology Readiness Level (TRL) and (2) evaluation activities where the capabilities were applied to flight/mission planning procedures and used by operators/pilots. For the latter, flight plans were automatically assessed, and operators/pilots were notified of hazardous flight segments so as to enable adjustment of the flight plan and re-evaluation, and/or to better inform go/no-go decisions. Capabilities addressed hazards associated with power consumption, third-party risk, wind, navigation system performance, radiofrequency interference, and proximity to geo-spatial threats (e.g., buildings, trees, and no-fly zones). In-flight: Flight experiments tested capabilities that detect and respond to hazards encountered during flight. In the first series, safety hazards were monitored and assessed onboard, and system-generated mitigation maneuvers were recorded (but not acted upon by the vehicle). In the second series, mitigation maneuver commands directed the aircraft in response to safety hazards (i.e., auto-mitigation). The sUAS used for testing is described in full, as is the test architecture, which included commercial avionics, research avionics, and onboard software designed to detect, assess, and respond to hazards. The onboard system was designed as a run-time assurance framework, consistent with [2] and supportive of both supervisory and automated modes. The primary functions included: real-time risk assessment (RTRA), auto-pilot monitoring, constraint monitoring, and contingency select/triggering. RTRA performs integrated risk assessment considering data from several hazard-related monitors (e.g., battery, motors, navigation, communications, population density, and loss-of-control). Post-flight/off-line: Data monitored and recorded during flights can enable IASMS capabilities that execute after flights have completed (or “off-line”). These include: (1) the ability to identify anomalies and trends that may only be observable when comparing data spanning a number of similar flights; (2) the ability to update and validate pre-flight and in-flight capabilities and any underlying models to improve their performance; (3) the ability to report anomalies/off-nominals that may indicate design changes or maintenance actions are needed; and (4) the ability for humans involved in operations to report safety-relevant observations to help in understanding the flight data and/or the operational context of a flight. Progress on three such capabilities is summarized; the first investigates anomaly detection given a limited set of flight logs and applies an approach previously used for space operations. The second explores what could be identified using a larger set of flight logs, including from web-based forums where flight logs are posted by sUAS autopilot users. The third creates a new means of collecting information on UAS incidents and accidents via the Aviation Safety Reporting System (ASRS).

sUAS