Search NASA⌕ Search

SEARCH · Search NASA

Results for “reporting and analysis of anomalies”

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.

At least 163 records · Page 9
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

An Approach for Defining IASMS Services, Functions, and Capabilities

Assuring safety in the NAS with the inclusion of new entrants, such as Advanced Air Mobility (AAM), will require overcoming unique safety challenges that result from combining innovative technologies with novel airspace concepts for moving people and cargo using autonomous vehicles. The focus of the In-time Aviation Safety Management System (IASMS) is to overcome AAM’s safety assurance challenges. The IASMS Concept of Operations (ConOps) describes an interconnected set of services, functions, and capabilities (SFCs) designed to manage operational risks, identify unknown risks, and inform system designs. This paper describes an approach for defining SFCs based on technology trends in research, assessment of known and unknown risks in voluntary safety reports, and causal and contributing factors in aviation accidents and incidents. This approach would identify potential SFCs that further expand the Monitor, Assess, and Mitigate (M-A-M) functionality that represents the enabling framework of the IASMS. Safety implications that will result from integration of AAM in the transformation of the National Airspace System (NAS) were addressed in National Academies committees reports on AAM and IASMS. Development of a ConOps for IASMS was a top recommendation and can be represented as a reframing of safety assurance that builds on real-time alerting such as the Traffic Alert and Collision Avoidance System, and adds the more encompassing in-time temporal parameter in recognition of the different timelines for collecting and assessing safety data for risk mitigations. For example, mining for safety trends from data sources such as the Aviation Safety Information Analysis and Sharing system occurs over a longer time period. Research on AAM operations poses that SFCs can be designed to monitor the safety margin appropriate for AAM including with regards to the distance between current flight parameters and nominal ideal conditions. These in-time comparisons will become more complex as the density of operations increases at least in certain areas and can include planned and actual 4D trajectory, and in-time comparisons having implications on conflict modeling and prediction including expected and actual departure time, fix/waypoint crossing times, and arrival time. These comparisons would be integrated as part of SFCs that redefine and inform new safety margin. An increased safety margin improves management of operational risks while reducing the potential for anomalies. An increased safety margin also has implications for operator confidence in the certainty of its operations and trust in automation. Technology trends in research could be used to refine existing SFCs and define needs for additional SFCs that provide safety improvements to the design and operation of vehicles, airspace design, and operator performance requirements. NASA is developing innovative approaches to safeguard against major accidents and incidents that have occurred in the NAS and those anticipated with the inclusion of envisioned AAM operations. The innovations use operational performance data to monitor, detect, and predict flight variations exceeding safe nominal patterns, such as would be caused by navigational error, severe weather complications, or hijacking of UAS controls. These innovative approaches have high potential to prevent accidents and incidents in the new AAM era. It is anticipated that elements of the innovations will evolve into SFCs for the IASMS. Voluntary safety reports can be monitored to identify anomalies related to design or operational performance risks. Reports could be periodically monitored and assessed for specific topics. Reports might serve as weak signals or precursors indicative of emergent risk such as when combined with other safety information. The architecture could include SFCs that are based on voluntary safety reports recognizing the periodic temporal nature of data analysis. As previously mentioned, aviation accidents with their causal and contributing precursors can inform the need for SFCs in the IASMS. Accidents and incidents at San Francisco International Airport such as Asiana 214 and Air Canada 759 illustrate how combinations of different factors lead to increased risk. These types of precursors and different factors have implications on the types of SFCs that could be needed to monitor and manage different sources and types of design and operational risk. Continuing to assure the safety of AAM as designs and operations gain in complexity can be accompanied by defining SFCs that also increase in complexity. These SFCs can leverage information from findings and recommendations synthesized across on-going research, voluntary safety reports, and accident and incident reports. These SFCs can serve to refine accuracy of algorithms and resolve limitations with current practices. The IASMS architecture represents the framework for the SFCs and their critical role in safety assurance.

In-Time Aviation Safety Management System↗
DOE OSTI2022

Facilitating Machine Learning Collaborations Between Labs, Universities, And Industry

It is clear from numerous recent community reports, papers, and proposals that machine learning is of tremendous interest for particle accelerator applications. The quickly evolving landscape continues to grow in both the breadth and depth of applications including physics modeling, anomaly detection, controls, diagnostics, and analysis. Consequently, laboratories, universities, and companies across the globe have established dedicated machine learning (ML) and data science efforts aiming to make use of these new state-of-the-art tools. The current funding environment in the U.S. is structured in a way that supports specific application spaces rather than larger collaboration on community software. Here, we discuss the existing collaboration bottlenecks and how a shift in the funding environment, and how we develop collaborative tools, can help fuel the next wave of ML advancements for particle accelerators.

Edelen, J.P.↗
DOE OSTI2021

Review of Intrusion Detection Methods and Tools for Distributed Energy Resources

Recent trends in the growth of distributed energy resources (DER) in the electric grid and newfound malware frameworks that target internet of things (IoT) devices is driving an urgent need for more reliable and effective methods for intrusion detection and prevention. Cybersecurity intrusion detection systems (IDSs) are responsible for detecting threats by monitoring and analyzing network data, which can originate either from networking equipment or end-devices. Creating intrusion detection systems for PV/DER networks is a challenging undertaking because of the diversity of the attack types and intermittency and variability in the data. Distinguishing malicious events from other sources of anomalies or system faults is particularly difficult. New approaches are needed that not only sense anomalies in the power system but also determine causational factors for the detected events. In this report, a range of IDS approaches were summarized along with their pros and cons. Using the review of IDS approaches and subsequent gap analysis for application to DER systems, a preliminary hybrid IDS approach to protect PV/DER communications is formed in the conclusion of this report to inform ongoing and future research regarding the cybersecurity and resilience enhancement of DER systems.

45 MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEF↗
NASA NTRS1975

Man-rated flight software for the F-8 DFBW program

The design, implementation, and verification of the flight control software used in the F-8 DFBW program are discussed. Since the DFBW utilizes an Apollo computer and hardware, the procedures, controls, and basic management techniques employed are based on those developed for the Apollo software system. Program Assembly Control, simulator configuration control, erasable-memory load generation, change procedures and anomaly reporting are discussed. The primary verification tools--the all-digital simulator, the hybrid simulator, and the Iron Bird simulator--are described, as well as the program test plans and their implementation on the various simulators. Failure-effects analysis and the creation of special failure-generating software for testing purposes are described. The quality of the end product is evidenced by the F-8 DFBW flight test program in which 42 flights, totaling 58 hours of flight time, were successfully made without any DFCS inflight software, or hardware, failures.

Bairnsfather, R. R.↗
NASA NTRS1974

Investigation of the Kramers-Kronig analysis - Revised optical constants of AgCl

White and Straley (1968) have reported room-temperature optical constants for AgCl that exhibit negative, unphysical dips at the band edge. Because Morrison (1961) also obtained such behavior for InAs, InSb, and GaAs, a study is made of the possible sources of this anomaly. An artifact of the experimental reflectance data near this energy is found to be responsible. No defect in the Kramers-Kronig transform or its use is implied, contrary to some suggestions. The corrected optical constants of AgCl were modified by about 10% up to 5 eV, whereas at higher energies they were barely affected. Thus Kramers-Kronig-deduced optical constants that exhibit unusual structure are not affected by this structure at other energies. The new AgCl results are presented, and assignments are briefly discussed.

Bauer, R. S.↗
NASA NTRS1997

Scientific and Technical Support for the Galileo Net Flux Radiometer Experiment

This report describes work in support of the Galileo Net Flux Radiometer (NFR), an instrument mounted on the Galileo probe, a spacecraft designed for entry into and direct measurements of Jupiter's atmosphere. Tasks originally proposed for the post launch period covered by NCC 2-854 are briefly as follows: attend and support PSG (Project Science Group) and other project science meetings; support in-flight checkouts; maintain and keep safe the spare instrument and GSE (Ground Support Equipment); organize and maintain documentation; finish NFR calibration measurements, documentation, and analysis; characterize and diagnose instrument anomalies; develop descent data analysis tools; and science data analysis and publication. Because we had the capability to satisfy a project support need we also subsequently proposed and were funded to make ground-based observations of Jupiter during the period surrounding the Galileo arrival at Jupiter, using the Swedish Solar Telescope at La Palma, Canary Islands. The following section provides background information on the NFR instrument. Section 3 contains the final report of work done.

Sromovsky, Lawrence A.↗
NASA NTRS1979

Design review of a liquid solar collector

Report documents procedures, results, and recommendations for in-depth analysis of problems with liquid-filled version of concentric-tube solar collector. Problems are related to loss of vacuum and/or violent fracture of collector elements, fluid leakage, freezing, flow anomalies, manifold damage, and other component failures.

Wiesewmaier, B. L.↗
NASA NTRS1994

A Cost and Performance System (CAPS) in a Federal agency

Cost and Performance System (CAPS) is an automated system used from the planning phase through implementation to analysis and documentation. Data is retrievable or available for analysis of cost versus performance anomalies. CAPS provides a uniform system across intra- and international elements. A common system is recommended throughout an entire cost or profit center. Data can be easily accumulated and aggregated into higher levels of tracking and reporting of cost and performance.The level and quality of performance or productivity is indicated in the CAPS model and its process. The CAPS model provides the necessary decision information and insight to the principal investigator/project engineer for a successful project management experience. CAPS provides all levels of management with the appropriate detailed level of data.

Huseonia, W. F.↗
NASA NTRS2014

Clearance Analysis of Node 3 Aft CBM to the Stowed FGB Solar Array

In early 2011, the ISS Vehicle Configuration Office began considering the relocation of the Permanent Multipurpose Module (PMM) to the aft facing Common Berthing Mechanism (CBM) on Node 3 to open a berthing location for visiting vehicles on the Node 1 nadir CBM. In this position, computer-aided design (CAD) models indicated that the aft end of the PMM would be only a few inches from the stowed Functional Cargo Block (FGB) port solar array. To validate the CAD model clearance analysis, in the late summer of 2011 the Image Science and Analysis Group (ISAG) was asked to determine the true geometric relationship between the on-orbit aft facing Node 3 CBM and the FGB port solar array. The desired measurements could be computed easily by photogrammetric analysis if current imagery of the ISS hardware were obtained. Beginning in the fall of 2011, ISAG used the Dynamic Onboard Ubiquitous Graphics (DOUG) program to design a way to acquire imagery of the aft face of Node 3, the aft end-cone of Node 1, the port side of pressurized mating adapter 1 (PMA1), and the port side of the FGB out to the tip of the port solar array using cameras on the Space Station Remote Manipulator System (SSRMS). This was complicated by the need to thread the SSRMS under the truss, past Node 3 and the Cupola, and into the space between the aft side of Node 3 and the FGB solar array to acquire more than 100 images from multiple positions. To minimize the number of SSRMS movements, the Special Purpose Dexterous Manipulator (SPDM) would be attached to the SSRMS. This would make it possible to park the SPDM in one position and acquire multiple images by changing the viewing orientation of the SPDM body cameras using the pan/tilt units on which the cameras are mounted. Using this implementation concept, ISAG identified four SSRMS/SPDM positions from which all of the needed imagery could be acquired. Based on a photogrammetric simulation, it was estimated that the location of the FGB solar array could be measured within an accuracy of about 1 in. in each axis relative to the ISS Analysis Coordinate System (ISSACS). In October 2011, a proposed image-acquisition plan was drafted by ISAG and released for review. The ISS Robotics flight control team (ROBO) proposed minor changes to SPDM positions 1 and 4 to meet ISS proximity requirements. The updated image acquisition plan and draft chit were presented to and approved by the Systems Working Group (SWG) November 18 and were sent to the Vehicle Configuration Board (VCB) in early December 2011. Working with ROBO on 3 successive days (February 21, 22, and 23), ISAG collected 161 images of the ISS. Approximately 40 images were collected from each of the four different SSRMS/SPDM positions, with each set mapping the region from the Node 3 end cone, across Node 1, along the forward port side portion of the FGB, and out the port side FGB solar arrays. From this imagery, the best 80 images were selected for use in the analysis. The images were radiometrically enhanced to improve color and contrast and loaded into the FotoG analysis software along with the camera parameters and control data, which consisted of the coordinates for 54 handrail attachment bolts on the aft face of Node 3, in the ISSACS coordinate system. The results of this analysis produced the measured coordinates of 116 points distributed across the face of the FGB solar array panels (see figure 3) along with propagated uncertainty estimates in each coordinate axis. These results were sent to the ISS Vehicle Configuration Office, which sent them to the Configuration Analysis Modeling and Mass Properties (CAMMP) team for comparison with the Russian-provided CAD model for the retracted FGB solar arrays. The CAMMP analysis unexpectedly showed that the measured location of the port FGB solar array was up to 41-in. further outboard than the design and was slightly twisted about its rotational axis. The unexpected comparison results produced some initial concern regarding the accuracy of the photogrammetric measurements. To verify the measured results, ISAG personnel conducted a second analysis using just the imagery of the solar arrays in an arbitrary coordinate system defined by the three corner points of the inboard-most panel, with the design distance between points A1 and A10 as the only scale. The new measurements agreed with the original results to within less than 1 in. RMS in each axis, confirming the original solar array measurements. ISAG produced a final report for the ISS Vehicle Configuration Office documenting an apparent anomaly in the retracted configuration of the port FGB solar arrays. A copy of the measurement report was translated and sent to the Russian Space Agency. During a Vehicle Integrated Performance and Resources (VIPeR) teleconference September 24, 2012, the Russians acknowledged receipt of a translated copy of the ISAG report. The Russian representative stated that the head of the solar array design team claimed that the measured configuration was impossible unless the structure was physically broken. The Russians acknowledged that they had no expertise in photogrammetry, so the analysis technique employed was a "black box" to them, and they did not know how to use the ISAG results. They asked for a single image in which the overextension of the port solar array could be obviously seen. On November 10, 2012, during a face-to-face meeting with their Russian counterparts at JSC, ISAG presented nadir-view imagery of the FGB acquired during Space Shuttle rendezvous. Using the known width of the pressurized portion of the FGB as a scale, this analysis clearly showed that the port FGB solar array was extended outboard further than the Russian design for the retracted solar array.

Liddle, Donn↗
NASA NTRS1972

Apollo 16 mission Report. Supplement 1: Apollo 16 guidance, navigation, and control system performance analysis report

The results are reported of additional studies which were conducted to supplement conclusions drawn in the MSC Mission Report and analyses which were not completed in time to meet the Mission Report dealine. A detailed evaluation of the Abort Guidance System sensor assembly and results from the investigation of the X gyro loop anomaly are included. Further evidence is presented substantiating the excellent LM IMU performance obtained from preliminary indications. A detailed study is presented of the procedural changes implemented on Apollo 16 to diminish the number and duration of interruptions to the CSM DAP attitude maneuver during P20 Option 5 operations.

Source record↗
NASA NTRS2016

The Matsu Wheel: A Cloud-Based Framework for Efficient Analysis and Reanalysis of Earth Satellite Imagery

Project Matsu is a collaboration between the Open Commons Consortium and NASA focused on developing open source technology for cloud-based processing of Earth satellite imagery with practical applications to aid in natural disaster detection and relief. Project Matsu has developed an open source cloud-based infrastructure to process, analyze, and reanalyze large collections of hyperspectral satellite image data using OpenStack, Hadoop, MapReduce and related technologies. We describe a framework for efficient analysis of large amounts of data called the Matsu "Wheel." The Matsu Wheel is currently used to process incoming hyperspectral satellite data produced daily by NASA's Earth Observing-1 (EO-1) satellite. The framework allows batches of analytics, scanning for new data, to be applied to data as it flows in. In the Matsu Wheel, the data only need to be accessed and preprocessed once, regardless of the number or types of analytics, which can easily be slotted into the existing framework. The Matsu Wheel system provides a significantly more efficient use of computational resources over alternative methods when the data are large, have high-volume throughput, may require heavy preprocessing, and are typically used for many types of analysis. We also describe our preliminary Wheel analytics, including an anomaly detector for rare spectral signatures or thermal anomalies in hyperspectral data and a land cover classifier that can be used for water and flood detection. Each of these analytics can generate visual reports accessible via the web for the public and interested decision makers. The result products of the analytics are also made accessible through an Open Geospatial Compliant (OGC)-compliant Web Map Service (WMS) for further distribution. The Matsu Wheel allows many shared data services to be performed together to efficiently use resources for processing hyperspectral satellite image data and other, e.g., large environmental datasets that may be analyzed for many purposes.

0↗
NASA NTRS2014

Analysis of Aviation Safety Reporting System Incident Data Associated with the Technical Challenges of the Atmospheric Environment Safety Technology Project

This study analyzed aircraft incidents in the NASA Aviation Safety Reporting System (ASRS) that apply to two of the three technical challenges (TCs) in NASA's Aviation Safety Program's Atmospheric Environment Safety Technology Project. The aircraft incidents are related to airframe icing and atmospheric hazards TCs. The study reviewed incidents that listed their primary problem as weather or environment-nonweather between 1994 and 2011 for aircraft defined by Federal Aviation Regulations (FAR) Parts 121, 135, and 91. The study investigated the phases of flight, a variety of anomalies, flight conditions, and incidents by FAR part, along with other categories. The first part of the analysis focused on airframe-icing-related incidents and found 275 incidents out of 3526 weather-related incidents over the 18-yr period. The second portion of the study focused on atmospheric hazards and found 4647 incidents over the same time period. Atmospheric hazards-related incidents included a range of conditions from clear air turbulence and wake vortex, to controlled flight toward terrain, ground encounters, and incursions.

Withrow, Colleen A.↗
DOE OSTI2025

Utah FORGE: Seismic DAS and Geophone Borehole Data Processing and 3D Imaging of Vp/Vs Ratio in the 2024 Stimulated Reservoir

This dataset includes a final report and a 3D velocity model derived from seismic DAS and geophone borehole data collected during the April 2024 stimulation of the reservoir at Utah FORGE. The report details the processing of over 50,000 P- and S-wave travel times used in a tomographic inversion to estimate the Vp/Vs ratio, revealing anomalies adjacent to wells 16A and 16B that may be associated with injected fracturing fluids. Additionally, Wadati analysis of more than 27,000 pairs of differential P- and S-wave travel times supports this interpretation with a high Vp/Vs estimate of 1.86, averaged over the dimensions of the earthquake cluster. The accompanying data file provides a 3D model of P- and S-wave velocities and Vp/Vs ratios, structured with spatial coordinates and velocity values.

15 GEOTHERMAL ENERGY↗
NASA NTRS2003

Time-Variable Gravity Signal due to Extratropic Pacific Water Mass Redistribution

Using the satellite-laser-ranging (SLR) data, Cox and Chao [2002] reported the detection of a large post-1998 anomaly (in the form of a positive jump) in the time series of Earth s lowest-degree gravity harmonic 52, or the dynamic oblateness. Among several groups now examining the mass redistribution in the global geophysical fluids in search of the cause(s), we report here a temporally coinciding anomalies found in the extratropic north + south Pacific basins. Clearly seen in the leading EOFPC mode for extratropic Pacific, these anomalies occurred in sea-surface height, sea-surface temperature, and temperature- and salinity-depth profiles. We based our analysis on two different data sources: TOPEX/Poseidon altimetry, and the ECCO ocean general circulation model output assimilating T/P data. The magnitude of these changes, when converted to equivalent J2 change, appears to be a few times too small to explain the observed J2 directly. These findings, and the fact that the anomalies occurred following the strong 1997-98 El Nino, suggest strong geophysical connection of the interannual-to-decadal variation of 52 with the Pacific Decadal Oscillation (PDO) and the ultimate global-change processes that cause PDO. More work is underway, and additional independent data sources are examined, paying close attention to the fact that the J2 anomaly has been reversing back to normal since 2001. These include: (1) cryospheric contributions (melting of glaciers and ice sheets); (2) land hydrological contributions; (3) polar sea influences ( e g , via deep flow); (4) fluid flow in Earth's core; (5) time-variable gravity signals from SLR in higher harmonic degree/order, including J3,J4, (2,1), and (2,2) coefficients, considering their lower signal-to-noise ratios; (6) Earth rotation data in terms of length-of-day and polar motion.

Chao, B. F.↗
NASA NTRS1981

Analysis of DSN software anomalies

A categorized data base of software errors which were discovered during the various stages of development and operational use of the Deep Space Network DSN/Mark 3 System was developed. A study team identified several existing error classification schemes (taxonomies), prepared a detailed annotated bibliography of the error taxonomy literature, and produced a new classification scheme which was tuned to the DSN anomaly reporting system and encapsulated the work of others. Based upon the DSN/RCI error taxonomy, error data on approximately 1000 reported DSN/Mark 3 anomalies were analyzed, interpreted and classified. Next, error data are summarized and histograms were produced highlighting key tendencies.

Galorath, D. D.↗
NASA NTRS2005

Fault-Detection Tool Has Companies 'Mining' Own Business

A successful launching of NASA's Space Shuttle hinges heavily on the three Space Shuttle Main Engines (SSME) that power the orbiter. These critical components must be monitored in real time, with sensors, and compared against expected behaviors that could scrub a launch or, even worse, cause in- flight hazards. Since 1981, SSME faults have caused 23 scrubbed launches and 29 percent of total Space Shuttle downtime, according to a compilation of analysis reports. The most serious cases typically occur in the last few seconds before ignition; a launch scrub that late in the countdown usually means a period of investigation of a month or more. For example, during the launch attempt of STS-41D in 1984, an anomaly was detected in the number three engine, causing the mission to be scrubbed at T-4 seconds. This not only affected STS-41D, but forced the cancellation of another mission and caused a 2-month flight delay. In 2002, NASA s Kennedy Space Center, the Florida Institute of Technology, and Interface & Control Systems, Inc., worked together to attack this problem by creating a system that could automate the detection of mechanical failures in the SSMEs fuel control valves.

Source record↗
NASA NTRS2007

Lessons Learned from Seven Space Shuttle Missions

Much can be learned from well-written descriptions of the technical and organizational factors that lead to an accident. Subsequent analysis by third parties of investigation reports and associated evidence collected during the investigations can lead to additional insight. Much can also be learned from documented close calls that do not result in loss of life or a spacecraft, such as the Mars Exploration Rover Spirit software anomaly, the SOHO mission interruption, and the NEAR burn anomaly. Seven space shuttle incidents fall into the latter category: Rendezvous Target Failure On STS-41B; Rendezvous Radar Anomaly and Trajectory Dispersion-STS-32 ;Rendezvous Lambert Targeting Anomaly-STS-49; Rendezvous Lambert Targeting Anomaly-STS-51; Zero Doppler Steering Maneuver Anomaly-STS-59; Excessive Propellant Consumption During Rendezvous-STS-69; Global Positioning System Receiver and Associated Shuttle Flight Software Anomalies-STS-91 Procedural work-arounds or software changes prevented them from threatening mission success. Extensive investigations, which included the independent recreation of the anomalies by multiple Shuttle Program organizations, were the key to determining the cause, accurately assessing risk, and identifying software and software process improvements. Lessons learned from these incidents not only validated long-standing operational best practices, but serve to promote discussion and mentoring among Program personnel and are applicable to future space flight programs.

Goodman, John↗
NASA NTRS2013

Determining Component Probability using Problem Report Data for Ground Systems used in Manned Space Flight

During the shuttle era NASA utilized a failure reporting system called the Problem Reporting and Corrective Action (PRACA) it purpose was to identify and track system non-conformance. The PRACA system over the years evolved from a relatively nominal way to identify system problems to a very complex tracking and report generating data base. The PRACA system became the primary method to categorize any and all anomalies from corrosion to catastrophic failure. The systems documented in the PRACA system range from flight hardware to ground or facility support equipment. While the PRACA system is complex, it does possess all the failure modes, times of occurrence, length of system delay, parts repaired or replaced, and corrective action performed. The difficulty is mining the data then to utilize that data in order to estimate component, Line Replaceable Unit (LRU), and system reliability analysis metrics. In this paper, we identify a methodology to categorize qualitative data from the ground system PRACA data base for common ground or facility support equipment. Then utilizing a heuristic developed for review of the PRACA data determine what reports identify a credible failure. These data are the used to determine inter-arrival times to perform an estimation of a metric for repairable component-or LRU reliability. This analysis is used to determine failure modes of the equipment, determine the probability of the component failure mode, and support various quantitative differing techniques for performing repairable system analysis. The result is that an effective and concise estimate of components used in manned space flight operations. The advantage is the components or LRU's are evaluated in the same environment and condition that occurs during the launch process.

Monaghan, Mark W.↗