Search NASA⌕ Search

SEARCH · Search NASA

Results for “Outage prediction”

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.

41 records · Page 3

Dual-Doppler Feasibility Study

When two or more Doppler weather radar systems are monitoring the same region, the Doppler velocities can be combined to form a three-dimensional (3-D) wind vector field thus providing for a more intuitive analysis of the wind field. A real-time display of the 3-D winds can assist forecasters in predicting the onset of convection and severe weather. The data can also be used to initialize local numerical weather prediction models. Two operational Doppler Radar systems are in the vicinity of Kennedy Space Center (KSC) and Cape Canaveral Air Force Station (CCAFS); these systems are operated by the 45th Space Wing (45 SW) and the National Weather Service Melbourne, Fla. (NWS MLB). Dual-Doppler applications were considered by the 45 SW in choosing the site for the new radar. Accordingly, the 45th Weather Squadron (45 WS), NWS MLB and the National Aeronautics and Space Administration tasked the Applied Meteorology Unit (AMU) to investigate the feasibility of establishing dual-Doppler capability using the two existing systems. This study investigated technical, hardware, and software requirements necessary to enable the establishment of a dual-Doppler capability. Review of the available literature pertaining to the dual-Doppler technique and consultation with experts revealed that the physical locations and resulting beam crossing angles of the 45 SW and NWS MLB radars make them ideally suited for a dual-Doppler capability. The dual-Doppler equations were derived to facilitate complete understanding of dual-Doppler synthesis; to determine the technical information requirements; and to determine the components of wind velocity from the equation of continuity and radial velocity data collected by the two Doppler radars. Analysis confirmed the suitability of the existing systems to provide the desired capability. In addition, it is possible that both 45 SW radar data and Terminal Doppler Weather Radar data from Orlando International Airport could be used to alleviate any radar geometry issues at the NWS MLB radar, such as the "cone of silence" or beam blockage. In the event of a radar outage at one of the sites, the multi-radar algorithms would provide continuing coverage of the area through use of the data from the remaining operational radar sites. There are several options to collect, edit, synthesize and display dual-Doppler data sets. These options include commercial packages available for purchase and a variety of freeware packages available from the National Center for Atmospheric Research (NCAR) for processing raw radar data. However, evaluation of the freeware packages revealed that they do not have sufficient documentation and configuration control to be certified for 45 SW use. Additionally, a TI data line must be installed/leased from the NWS MLB office and CCAFS to enable the receipt of NWS MLB raw radar data to use in the dual-Doppler synthesis. Integration of the TI data line into the Eastern Range infrastructure that will meet the security requirements necessary for 45 SW use is time-consuming and costly. Overall evaluation indicates that establishment of the dual-Doppler capability using the existing operational radar systems is desirable and feasible with no technical concerns. Installation of such a system represents a significant enhancement to forecasting capabilities at the 45 WS and at NWS MLB. However, data security and cost considerations must be evaluated in light of current budgetary constraints. In any case, gaining the dual-Doppler capability will provide opportunities for better visualization of the wind field and better forecasting of the onset of convection and severe weather events to support space launch operations at KSC and CCAFS.

Huddleston, Lisa L.↗

Combined Global Navigation Satellite Systems in the Space Service Volume

Besides providing position, velocity, and timing (PVT) for terrestrial users, the Global Positioning System (GPS) is also being used to provide PVT information for earth orbiting satellites. In 2006, F. H. Bauer, et. al., defined the Space Service Volume in the paper GPS in the Space Service Volume , presented at ION s 19th international Technical Meeting of the Satellite Division, and looked at GPS coverage for orbiting satellites. With GLONASS already operational, and the first satellites of the Galileo and Beidou/COMPASS constellations already in orbit, it is time to look at the use of the new Global Navigation Satellite Systems (GNSS) coming into service to provide PVT information for earth orbiting satellites. This presentation extends GPS in the Space Service Volume by examining the coverage capability of combinations of the new constellations with GPS GPS was first explored as a system for refining the position, velocity, and timing of other spacecraft equipped with GPS receivers in the early eighties. Because of this, a new GPS utility developed beyond the original purpose of providing position, velocity, and timing services for land, maritime, and aerial applications. GPS signals are now received and processed by spacecraft both above and below the GPS constellation, including signals that spill over the limb of the earth. Support of GPS space applications is now part of the system plan for GPS, and support of the Space Service Volume by other GNSS providers has been proposed to the UN International Committee on GNSS (ICG). GPS has been demonstrated to provide decimeter level position accuracy in real-time for satellites in low Earth orbit (centimeter level in non-real-time applications). GPS has been proven useful for satellites in geosynchronous orbit, and also for satellites in highly elliptical orbits. Depending on how many satellites are in view, one can keep time locked to the GNSS standard, and through that to Universal Time as long as at least one satellite is in view (the longest duration with no satellites in view is important in determining the maximum clock drift from GNSS time). Instantaneous position requires four satellites in view, but because orbital motion is predictable, it is possible to build up knowledge of the orbital position gradually through time without a need for constant four satellite coverage. However, it is desirable to have four satellite coverage when performing satellite maneuvers, since there can be significant changes in velocity, leading to large changes in orbit parameter, causing substantial divergence in position over time. The Space Service Volume has been defined as the volume between three thousand km altitude and geosynchronous altitude, and can be divided into medium orbit services between three thousand km altitude and eight thousand km altitude, and high orbit services above eight thousand km. The Terrestrial Service Volume includes the Earth s surface, the atmosphere, and space below the altitude of three thousand km. The Terrestrial Service Volume is the volume within which the GNSS systems will have very similar performance to the Earth surface, and satellites need only use the signals specified to provide terrestrial performance. Above three thousand km the use of signals passing by the Earth s limb becomes important, so it is desirable to have additional information on signal strength, phase delay, and group delay covering wider beam angles than are needed for terrestrial service (and which can be obtained by monitoring GNSS signals from the Earth s surface). This presentation will look at each of the new GNSS constellations in combination with GPS (GLONASS with GPS, Galileo with GPS, Beidou/COMPASS with GPS), and also at the combination of all four GNSS systems. The presentation will largely follow the format of GPS in the Space Service Volume , presenting data on the availability of one, two, three, or four of the various combinations of GNSS constellation satelles at approximately two thousand grid points evenly spaced and fixed in longitude and latitude, the duration of the longest single-fold outages (intervals when no satellites are available), and the duration of the longest four-fold outages (intervals when fewer than four satellites are available) at several altitudes. Following the original paper, we will use the altitudes of three hundred km (typical LEO satellite, and within the Terrestrial Service Volume), at three thousand km (border between Terrestrial Service Volume and Space Service Volume), at eight thousand km (the border between medium and high orbit service within the Space Service Volume), at fifteen thousand km (just below the GNSS constellations), at twenty five thousand km (just above the GNSS constellations), at thirty six thousand, five hundred km (limit of Space Service Volume definition, geosynchronous altitude), and at seventy thousand km (to show the potential usefulness of GNSS beyond geosynchronous altitude).

Force, Dale A.↗

Science CONOPS for Application of Sport Mission Data to Study Large (~1000KM) Ionospheric Plasma Depletions

The Scintillation Prediction Observations Research Task (SPORT) mission is a single 6U CubeSat space weather satellite planned for an October 2022 launch into an ISS-like orbit. The primary purpose of the SPORT mission is to determine the longitudinal effects on equatorial plasma bubble (EPB) growth resulting from the offset dipole magnetic field of the Earth. By combining field and plasma measurements from SPORT with other low-altitude (i.e., alt < 1000 km) spacecraft, it is possible to investigate large-scale (> 1000 km) EPB structures. The types of investigation made possible by measurements from SPORT and other contemporaneous missions include 1) dynamics of depleted magnetic flux tubes; 2) dynamics of field-aligned EPB expansion versus propagation speed; 3) EPB vertical extent; and 4) EPB temporal evolution. To support these investigation types, the respective modes of conjunctions are: 1) simultaneous intersection of a magnetic flux tube; 2) intersection of magnetic flux tube separated in time; 3) Simultaneous Latitude/Longitude position conjunction; and 4) Non-simultaneous latitude/longitude position conjunction. This paper will summarize the SPORT satellite and data used for Science CONOPS to accomplish these objectives.

Ionospheres↗

Land and Atmosphere Near-Real-Time Capability for Earth Observing System

The past decade has seen a rapid increase in availability and usage of near-real-time data from satellite sensors. The EOSDIS (Earth Observing System Data and Information System) was not originally designed to provide data with sufficiently low latency to satisfy the requirements for near-real-time users. The EOS (Earth Observing System) instruments aboard the Terra, Aqua and Aura satellites make global measurements daily, which are processed into higher-level 'standard' products within 8-40 hours of observation and then made available to users, primarily earth science researchers. However, applications users, operational agencies, and even researchers desire EOS products in near-real-time to support research and applications, including numerical weather and climate prediction and forecasting, monitoring of natural hazards, ecological/invasive species, agriculture, air quality, disaster relief and homeland security. These users often need data much sooner than routine science processing allows, usually within 3 hours, and are willing to trade science product quality for timely access. While Direct Broadcast provides more timely access to data, it does not provide global coverage. In 2002, a joint initiative between NASA (National Aeronautics and Space Administration), NOAA (National Oceanic and Atmospheric Administration), and the DOD (Department of Defense) was undertaken to provide data from EOS instruments in near-real-time. The NRTPE (Near Real Time Processing Effort) provided products within 3 hours of observation on a best-effort basis. As the popularity of these near-real-time products and applications grew, multiple near-real-time systems began to spring up such as the Rapid Response System. In recognizing the dependence of customers on this data and the need for highly reliable and timely data access, NASA's Earth Science Division sponsored the Earth Science Data and Information System Project (ESDIS)-led development of a new near-real-time system called LANCE (Land, Atmosphere Near-Real-Time Capability for EOS) in 2009. LANCE consists of special processing elements, co-located with selected EOSDIS data centers and processing facilities. A primary goal of LANCE is to bring multiple near-real-time systems under one umbrella, offering commonality in data access, quality control, and latency. LANCE now processes and distributes data from the Moderate Resolution Imaging Spectroradiometer (MODIS), Atmospheric Infrared Sounder (AIRS), Advanced Microwave Scanning Radiometer Earth Observing System (AMSR-E), Microwave Limb Sounder (MLS) and Ozone Monitoring Instrument (OMI) instruments within 3 hours of satellite observation. The Rapid Response System and the Fire Information for Resource Management System (FIRMS) capabilities will be incorporated into LANCE in 2011. LANCE maintains a central website to facilitate easy access to data and user services. LANCE products are extensively tested and compared with science products before being made available to users. Each element also plans to implement redundant network, power and server infrastructure to ensure high availability of data and services. Through the user registration system, users are informed of any data outages and when new products or services will be available for access. Building on a significant investment by NASA in developing science algorithms and products, LANCE creates products that have a demonstrated utility for applications requiring near-real-time data. From lower level data products such as calibrated geolocated radiances to higher-level products such as sea ice extent, snow cover, and cloud cover, users have integrated LANCE data into forecast models and decision support systems. The table above shows the current near-real-time product categories by instrument. The ESDIS Project continues to improve the LANCE system and use the experience gained through practice to seek adjustments to improve the quality and performance of the system. For example, anGC-compliant Web Map Service (WMS) will be added shortly that will allow users to download geo-referenced MODIS images for arbitrary bounding boxes. Further, an OGC-compliant Web Coverage Service (WCS) will be added later this year that will expedite user access to arbitrary data subsets or re-formatted products. AIRS images are now served through WMS and available in multiple formats (PNG, GeoTIFF, KMZ). NASA has established a LANCE User Working Group to steer the development of the system and create a forum for sharing ideas and experiences that are expected to further improve the LANCE capabilities. The LANCE system has proved a success by satisfying the growing needs of the applications and operational communities for land and atmosphere data in near-real-time. NASA's Earth Sciences Division was able to leverage existing science research capabilities to provide the near-real-time community with products and imagery that support monitoring of disasters in a timely manner.

Murphy, Kevin J.↗

Monitoring Airspace Complexity and Determining Contributing Factors

The national airspace has evolved over many years to accommodate increased traffic demand [1] while simultaneously maintaining one of the safest forms of transportation [2], [3]. One of the reasons for this success is the ability of the system and the operators to adapt and accommodate to situations that routinely disrupt optimal operations. These situations may include: adverse weather, delays, early arrivals, equipment outages, and other factors that are outside the operators ability to control. These factors can lead to states where automation is unable to properly handle these issues and therefore air traffic controllers and pilots have to intervene, ultimately increasing communication between operators resulting in higher workload. As controller workload increases to handle sub-optimal operating conditions this can be viewed as an increase in complexity. The reasoning for this is because humans are now required to make tactical decisions in response to external factors, resulting in a departure from the strategic plan where operations would be more efficiently managed. Human operators control airspace complexity under rigid regulations that are constantly changing. The airspace is divided into sectors and the number of aircraft assigned to each controller is limited for safe handling. There has been past work that devised airspace complexity metrics in commercial aviation and related these metrics to controller workload (e.g., [4],[5]). The upper bounds on the system load are pre-determined. Such bounds on complexity make for a safe system, but the system cannot scale and adapt to autonomous, dense, and heterogeneous traffic, including the many types of Unmanned Aerial Vehicles (UAVs) envisioned to be added to the operations. We hypothesize that, as traffic density and heterogeneity grow, and other key metrics change, there will be phase transitions at which the way traffic should be managed changes significantly [6]. We offer a method for in-time detection of contributing factors that lead to phase transitions, characterized by increased complexity. To the best of our knowledge, there is no tool similar to our proposed effort that identifies such contributing factors or precursor patterns. To define the scope we are proposing to measure complexity from the viewpoint of the Terminal Radar Approach Control Facilities (TRACON) controller’s perspective. In particular we are analyzing arrivals into KSFO. With safety as the top concern for airspace operators, it is important to recognize that as density and heterogeneity grow, the focus of the system will change. Times of the day when the airspace has low density and heterogeneity, the flights will follow more efficient paths where the aircraft move on established routes that are more or less directly to the destination. However, when density and heterogeneity increases, the system will begin changing focus to avoiding conflicts and collisions and route the flights in a more flexible way. Higher flexibility requires more communication and coordination between controllers and pilots which the current automation is unable to handle. This paper proposes a novel approach that monitors airspace complexity at multiple scales, uses a Machine Learning-based tool that predicts when operations will transition to a regime of greater complexity, and identifies actions that can reduce the complexity while still maintaining efficient and safe operations. We demonstrate our proposed approach using data from multiple complementary sources. This includes, but is not limited to: historical aircraft surveillance data from NASA’s Sherlock Data Warehouse [7], METAR weather data, and airport configuration data from Aviation System Performance Metrics (ASPM). The surveillance data flight paths are sampled at a variable sample rate — increasing as the aircraft approaches the airport. This is due to how Sherlock manages flight track stitching between different radar facilities which have different sampling rates. The weather and performance data are logged at defined intervals throughout the day at a courser refresh rate. In addition to the logged data and metrics, we leverage pre-defined Standard Terminal Arrival Routes (STARs) procedures to characterize the path of each flight. Each flight files for one of these routes in the flight plan well before entering the terminal airspace, and approximately follows the route until it leaves the STAR, typically on the final fix of a runway transition. However, most flights do not always fly the full STAR procedure to completion [8], but the majority do adhere to the fixes within the common route of the procedure. Our approach leverages fixes in the common route of each of the STARs to build a reference path to the airport. This allows us to characterize the flight paths in what we are defining as the “maneuvering area” (the airspace between the STAR and before the flight is lined up on the runway’s final approach) to determine how off nominal the flights are to calculate its complexity score. Determining airspace complexity is a concept that does not have a concrete answer. In designing this metric, we consider what increases the workload for the air traffic controllers. Consequently more specialized vectoring maneuvers results in higher workload. Accordingly, we start with a theory: each flight has a direct path it takes from the STAR’s common route to the final approach’s outer marker fix for the flight’s landing runway. It is important to note that the direct path is only used as a reference. If the majority of the flights have a large consistent offset as compared to other routes it does not necessarily mean that those flights have higher complexity. We are merely building a distribution based on this direct path for that particular STAR and runway pair to determine the normal mode of operations for that route. Flights that are in the upper tail of these distributions will result in higher complexity scores and flights that fly in the median will represent the normal mode of operations and therefore will have lower complexity scores. Since flights following each STAR route take different paths to the airport, we have a different distribution for each STAR route and therefore can model these distributions to compute a complexity score from their respective normalized distributions. To evaluate the effectiveness of our proposed airspace complexity metric we will compare against an established approach based on trajectory clustering [9]. This unsupervised learning technique consists of the following steps: (1) identify the general maneuvering areas (waypoints) by performing $\kappa$-means or DBSCAN clustering on locations where aircraft frequently turn based on the surveillance radar track data, (2) map flight trajectories onto sequences of waypoints, and (3) cluster the sequences based on their common subsequences. From a high-level perspective, this baseline model learns nominal operations in the airspace through the sequence of waypoints that are representative of where aircraft change direction and defines deviations from the nominal operations as “complex.” Therefore, more deviations from the nominal operations correspond to higher complexity values. For our validation, we re-implemented this technique and tune model hyper-parameters to correctly detect waypoints for the arrival traffic into the San Francisco bay area. We will compute the complexity measure over a one-year period using our proposed technique as well as the baseline. Our validation will be based on each technique’s ability to detect a set of undesirable outcomes (e.g., go-arounds, holding patterns, average time in the airspace, etc.). Since our current complexity metric is derived from the offset from the direct reference path, it’s important to understand what causes these offsets. In many of the flights with high offset distance, flights performing holding patterns and S turns can be observed. These maneuvering tactics are utilized to add distance between the aircraft and the destination runway to prevent multiple flights from having conflicting arrival times. In order to predict a rise in complexity (or the precursor to complexity), it’s necessary to be able to identify these potential conflicts (which in turn, result in higher offsets). To do this, we define a “representative flight” for each STAR route and runway pair. This flight is approximately the path the flight would take if there was a clear path with no other flights in the airspace — including the time remaining to the airport. We first identify the flights for a given STAR runway pair using the offset to the reference path distributions that fall between the 44-55 percentiles. This yields the flights that conform to the most normal mode of operation. Each of these flights is partitioned based on the percent complete from the entry point into the maneuvering areas from 0\% – 100\% complete. Then for each percent “bin”, we take the median value of the flight’s latitude/longitude coordinates, airspeed, and (non causal) time remaining to the airport to construct a lookup table for each percent complete bin on a given route. As a flight enters the maneuvering area, we can find the estimated arrival time of a flight to the airport by finding the closest point to the representative path’s percent complete bin (relative to the flight’s current position at any snapshot in the airspace) and therefore retrieve the corresponding remaining time left on the “representative path”. We assume that the flight will follow the representative path to completion when deriving these estimates. We can then compare these estimated arrival times against other flights for the same snapshot in time to identify potential conflicts. If more flights are estimated to arrive within a tolerance window than there are runways available, then we have a potential conflict. We can use this derived measure along with other factors expected to add disruption to the operation such as weather and runway configuration changes as an input to machine learning tools to detect precursors that increases in our complexity measure. This novel method will assist in uncovering insights into the contributing factors that lead to increased complexity that may allow for in-time responses to avoid reaching a high complexity state in the airspace.

complexity↗