Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “SAFETY REPORTS”

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 145 records · Page 8

Mission safety evaluation report for STS-37, postflight edition

STS-37/Atlantis was launched on April 5, 1991 from Kennedy Space Center launch complex 39B at 9:23 a.m. Eastern Standard Time (EST). Launch was delayed 4 minutes 45 seconds because of safety concerns about the low cloud ceiling and the wind direction in the potential blast area. Based on the limited number and type of inflight anomalies encountered, the Space Shuttle operated satisfactorily throughout the STS-37 mission. A contingency EVA was performed by the crew on Flight Day (FD) 3 to free a sticky Gamma Ray Observatory (GRO) high gain antenna, after which the GRO primary payload was successfully deployed by the Orbiter's Remote Manipulator System. The GRO, which weighed just over 35,000 lbs, was the heaviest NASA science satellite ever deployed by the Space Shuttle into low Earth orbit. The scheduled entry/landing on FD 6 was waved off for one day due to high wind conditions at Edwards Air Force Base. Atlantis landed on FD 7, 11 April 1991 on Edwards AFB lakebed runway 33 at 9:55 a.m. Eastern Daylight Time.

Hill, William C.↗

Crew Factors in Flight Operations XIV: Alertness Management in Regional Flight Operations Education Module

Regional operations encompass a broad range of pilots and equipment. This module is intended to help all those involved in regional aviation, including pilots, schedulers, dispatchers, maintenance technicians, policy makers, and others, to understand the physiological factors underlying fatigue, how flight operations affect fatigue, and what can be done to counteract fatigue and maximize alertness and performance in their operations. The overall purpose of this module is to promote aviation safety, performance, and productivity. It is intended to meet three specific objectives: (1) to explain the current state of knowledge about the physiological mechanisms underlying fatigue; (2) to demonstrate how this knowledge can be applied to improving flight crew sleep, performance, and alertness; and (3) to offer strategies for alertness management. Aviation Safety Reporting System (ASRS) and National Transportation Safety Board (NISH) reports are used throughout this module to demonstrate that fatigue is a safety issue in the regional operations community. The appendices at the end of this module include the ASRS reports used for the examples contained in this publication, brief introductions to sleep disorders and relaxation techniques, summaries of relevant NASA publications, and a list of general readings on sleep, sleep disorders, and circadian rhythms.

Rosekind, Mark R.↗

Crew Factors in Flight Operations XV: Alertness Management in General Aviation Education Module

Regional operations encompass a broad range of pilots and equipment. This module is intended to help all those involved in regional aviation, including pilots, schedulers, dispatchers, maintenance technicians, policy makers, and others, to understand the physiological factors underlying fatigue, how flight operations affect fatigue, and what can be done to counteract fatigue and maximize alertness and performance in their operations. The overall purpose of this module is to promote aviation safety, performance, and productivity. It is intended to meet three specific objectives: (1) to explain the current state of knowledge about the physiological mechanisms underlying fatigue; (2) to demonstrate how this knowledge can be applied to improving flight crew sleep, performance, and alertness; and (3) to offer strategies for alertness management. Aviation Safety Reporting System (ASRS) and National Transportation Safety Board (NISH) reports are used throughout this module to demonstrate that fatigue is a safety issue in the regional operations community. The appendices at the end of this module include the ASRS reports used for the examples contained in this publication, brief introductions to sleep disorders and relaxation techniques, summaries of relevant NASA publications, and a list of general readings on sleep, sleep disorders, and circadian rhythms.

Rosekind, Mark R.↗

Safety Evaluation Report: Development of a Novel Efficient Solid-Oxide Hybrid for Co-generation of Hydrogen and Electricity Using Nearby Resources for Local Applications, Materials and Systems Research, Inc. (MSRI), Salt Lake City, UT, February 17, 2009

Following a telephone interview with Materials and Systems Research, Inc. (MSRI) by members of the Hydrogen Safety Panel on December 4, 2008, a safety review team was dispatched to Salt Lake City, UT to perform a site-visit review. The major topic of concern was the presence of a hydrogen storage and dispensing shed on the MSRI premises close to both its own laboratory/office building and to the adjoining property. The metal shed contains 36 cylinders (two 18-cylinder "pods") of hydrogen all connected to a common manifold and used to supply hydrogen to a U.S. Department of Energy (DOE) fuel cell project plus several other projects using an entire pod as a common supply. In busy times, MSRI uses and replaces one pod per week. As a result of the site visit, the safety review team has raised some concern with the shed’s location, design, use, and safety features as well as other components of the facility, including the laboratory area.

08 HYDROGEN↗

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↗

Who or what saved the day? A comparison of traditional and glass cockpits

This study examined incidents reported to NASAs Aviation Safety Reporting System from a different perspective: rather than focusing on the factors contributing to or causing incidents, this study concentrated on who and what (subsystems and information) enabled the recovery from an anomaly. Incident reports describing altitude deviations were classified as to cockpit type (glass or traditional), flight phase, agent restoring safety, and cockpit subsystems providing specific information that helped restore safety. The data revealed and quantified the agents, information, and factors that 'saved the day'. The flight crews used many sources of information to detect the altitude deviations: altimeter, outside scene, altitude alert, kinesthesia, attitude and communications monitoring. In the glass cockpits the crews also used the map display and autothrottles to detect deviations from assigned altitudes. There was an interaction between the person detecting the anomaly (controller/flight crew) and the type of cockpit. Glass cockpit flight crews detect proportionally more deviations than their counterparts in traditional cockpits, while controllers tend to detect more deviations involving traditional cockpits. There was no effect of cockpit position (captain/first officer). A model that details the flow of altitude information between air traffic control, flight crews, and cockpit subsystems, was developed and validated. This model identifies strengths and weaknesses in the flow of altitude information within the current ground/air system.

Degani, Asaf↗

Safety Evaluation Report: Development of Improved Composite Pressure Vessels for Hydrogen Storage, Lincoln Composites, Lincoln, NE, May 25, 2010

Lincoln Composites operates a facility for designing, testing, and manufacturing composite pressure vessels. Lincoln Composites also has a U.S. Department of Energy (DOE)-funded project to develop composite tanks for high-pressure hydrogen storage. The initial stage of this project involves testing the permeation of high-pressure hydrogen through polymer liners. The company recently moved and is constructing a dedicated research/testing laboratory at their new location. In the meantime, permeation tests are being performed in a corner of a large manufacturing facility. The safety review team visited the Lincoln Composites site on May 25, 2010. The project team presented an overview of the company and project and took the safety review team on a tour of the facility. The safety review team saw the entire process of winding a carbon fiber/resin tank on a liner, installing the boss and valves, and curing and painting the tank. The review team also saw the new laboratory that is being built for the DOE project and the temporary arrangement for the hydrogen permeation tests.

08 HYDROGEN↗

PAT-1 safety analysis report addendum author responses to request for additional information.

The Plutonium Air Transportable Package, Model PAT-1, is certified under Title 10, Code of Federal Regulations Part 71 by the U.S. Nuclear Regulatory Commission (NRC) per Certificate of Compliance (CoC) USA/0361B(U)F-96 (currently Revision 9). The National Nuclear Security Administration (NNSA) submitted SAND Report SAND2009-5822 to NRC that documented the incorporation of plutonium (Pu) metal as a new payload for the PAT-1 package. NRC responded with a Request for Additional Information (RAI), identifying information needed in connection with its review of the application. The purpose of this SAND report is to provide the authors responses to each RAI. SAND Report SAND2010-6106 containing the proposed changes to the Addendum is provided separately.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

Mission safety evaluation report for STS-48, postflight edition

Space Shuttle Discovery was launched into a 57 deg inclination orbit from the Kennedy Space Center (KSC) Launch Complex 39A at 7:11 p.m. EDT on 12 Sep. 1991. STS-48 was the second mission since return-to-flight to have KSC as the planned end-of-mission landing site, and the first mission to have a planned night landing at KSC. However, due to weather conditions at KSC, Discovery flew one extra orbit and landed at Edwards AFB, Calif. at 3:38 a.m. EDT on 18 Sep. 1991. Operation of all systems was generally satisfactory during the 5 day mission. On flight day 3, the Upper Atmospheric Research Satellite (UARS) was deployed from Discovery's payload bay 350 statute miles above Earth. This orbiting observatory will study mankind's effects on the planet's atmosphere and its shielding ozone layer. STS-48 safety risk factors are addressed that represent a change from previous flights, factors from previous flights that had an impact on this flight, and factors that are unique to this flight.

Clatterbuck, Guy E.↗

SMALL-SCALE SAFETY TEST REPORT FOR RDX (SECOND CALIBRATION)

RDX was provided by Indian Head and was dried at 60 C for 16 hours, cooled and kept in a desiccator before use. Please note that the impact testing was done on both pellets and loose powder which resulted in different data. The impact sensitivity on pressed pellets was 34 cm that is greater than that on loose powder, as expected. The impact test data on the loose powder was similar to what Indian Head and LANL got. Remarkable consistent results were observed for test results of loose powder RDX. The average impact sensitivyt (DH{sub 50}) was 21.8 cm and the average friction sensitivity (F{sub 50}) for loose powder was 24.9 kg, respectively. DSC charts showed that peak temperatures and onset temperatures for all 3 runs of RDX samples were almost identical. All electrostatic spark sensitivity was 0/10 at 1.0 J with a 510-ohm resistor in the discharge circuit.

37 INORGANIC, ORGANIC, PHYSICAL, AND ANALYTICAL CH↗

PAT-1 safety analysis report addendum.

The Plutonium Air Transportable Package, Model PAT-1, is certified under Title 10, Code of Federal Regulations Part 71 by the U.S. Nuclear Regulatory Commission (NRC) per Certificate of Compliance (CoC) USA/0361B(U)F-96 (currently Revision 9). The purpose of this SAR Addendum is to incorporate plutonium (Pu) metal as a new payload for the PAT-1 package. The Pu metal is packed in an inner container (designated the T-Ampoule) that replaces the PC-1 inner container. The documentation and results from analysis contained in this addendum demonstrate that the replacement of the PC-1 and associated packaging material with the T-Ampoule and associated packaging with the addition of the plutonium metal content are not significant with respect to the design, operating characteristics, or safe performance of the containment system and prevention of criticality when the package is subjected to the tests specified in 10 CFR 71.71, 71.73 and 71.74.

42 ENGINEERING↗

Safety Analysis Report for Packaging Model 9977, Addendum 3: Justification for Small Gram Quantity Contents (Revision 5)

This Addendum establishes a new family of content envelopes consisting of small quantities of radioactive materials. These content envelopes and specific packing configurations are shown to be subcritical. However, the dose rates of some payloads must be measured and shown to comply with applicable radiation limits. Authorization for shipment of the content envelop requires acceptance of this Addendum by the DOE-HQ certifying official as a supplement to the 9977 SARP Revision 2 and DOE-HQ's subsequent revision of the CoC Revision 10 (which is based on SARP Addendum 2 and SARP Addendum 4) to authorize the additional content envelope. The Small Gram Quantity Content Envelopes and packing configurations will be incorporated in the next revision of the 9977 SARP.

42 ENGINEERING↗

A review of in-flight emergencies in the ASRS data base

A series of 154 in-flight emergencies as reported to the Aviation Safety Reporting System are described. The various types of emergencies are examined and an attempt is made to determine the human errors and other factors associated with each incident, as well as the measures taken to resolve the emergency. It is concluded that nearly one half of those emergencies reported were related to failure or malfunction of aircraft subsystems. Of all the emergencies, nearly one quarter were associated with power plant failure. Other frequently encountered emergency types are associated with operation in instrument meteorological conditions without appropriate clearance or qualification, and with low fuel state situations. Human error is prominently featured in many of the incidents, appearing in the actions of pilots and air traffic controllers.

Porter, R. F.↗

Operational problems experienced by single pilots in instrument meteorological conditions

The development and implementation of a search strategy to extract pertinent reports from the Aviation Safety Reporting System-2 (ASRS-2) database are described. For any particular occurence to be pertinent to the study, it must have satisfied the following conditions: the aircraft must be of the type usually flown by a single pilot; operation on an IFR flight plan in instrument meteorological conditions; pilot experienced an operational problem. The occurances consist of reports by the pilot about his own performance, by the pilot about the system performance, or by an air traffic controller about a pilot's performance.

Weislogel, S.↗