SEARCH · Engineering Papers

Results for “reporting”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 559 records · Page 31

All sources NASA NTRS DOE OSTI

DOE OSTI2026

United States Nuclear Data Program Annual Report for Fiscal Year 2025

The US Nuclear Data Program (USNDP) Annual Report for Fiscal Year 2025 summarizes the work of USNDP for the period of October 1, 2024 through September 30, 2025, with respect to the Work Plan for FY 2025 that was prepared in 2024. The Work Plan and Final Report for USNDP are prepared for the DOE Office of Science, Office of Nuclear Physics. The support for the nuclear data activity from sources outside the US Nuclear Data Program is summarized in the staffing table and Appendix A. This leverage amounts to about 22.8 FTE scientific, to be compared with 21.9 FTEs at USNDP units funded by the DOE Office of Science, Office of Nuclear Physics. Since it is often difficult to separate accomplishments funded by various sources, some of the work reported in the present report was accomplished with nuclear data program support leveraged by other funding. FY 2025 was the 25th year in which the USNDP has operated under a Work Plan developed by the program participants. The program continued to carry out important work in support of the DOE mission. The work balances the ongoing collecting, analyzing, and archiving of nuclear physics information critical to basic nuclear research and to the development and improvement of nuclear technologies with the electronic distribution of this information to users in a timely and easily accessible manner. The present section of the report consists of activity summaries for the major components of the USNDP. This is followed by an updated staff level assignment table that reflects the final distribution of effort among the tasks carried out during FY 2025. Then, we continue with the detailed status of work performed during FY 2025.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

DOE OSTI2022

Precursor Analysis Report: Cyber Attack on Thyssenkrupp Blast Furnace 2014

The Cyber Attack on Thyssenkrupp Blast Furnace 2014 Precursor Analysis Report leverages publicly available information about the Thyssenkrupp Steel Mill cyber attack and catalogs anomalous observables for each technique employed in the attack. This analysis is based upon the methodology of the Cybersecurity for the Operational Technology Environment (CyOTE) program. In December 2014, the German Government’s Federal Office for Information Security (BSI) released a report detailing a cyber attack on a German steel mill that occurred earlier that year, though exact dates and details of the attack were not revealed. While the report did not specify the name of the company, multiple sources identified the victim as one of Europe’s largest steel manufacturers, Thyssenkrupp AG. Further, Thyssenkrupp announced on 16 May of that year that Europe’s largest blast furnace, “Schwelgern 2,” located at its facility in Duisburg, Germany, would be offline for several weeks for repairs and upgrades, suggesting Schwelgern 2 was likely the target of the attack. The attack began in early 2014, when adversaries infiltrated the victim steel mill’s Information Technology (IT) network via a spearphishing campaign, then worked their way into the Operational Technology (OT) environment, where they executed software that caused denial of service, denial of control, and eventually a loss of control. This led to the blast furnace shutting down without proper safety procedures, resulting in catastrophic physical damage. No lives were lost in the incident, but ThyssenKrupp suffered $4 million in damage to the blast furnace and an additional $6 million in lost revenue. The adversaries required specialized knowledge and expertise in steel production, which enabled them to compromise a variety of internal systems and components across both IT and OT networks. The attack also demonstrated detailed knowledge of the industrial control systems (ICS) and production processes being used. This combination resulted in one of the earliest known publicly reported cybersecurity incidents resulting in physical damage to ICS equipment. Researchers and analysts identified 19 unique techniques (used in a sequence of 20 steps) utilized during the attack with a total of 454 observables using MITRE ATT&CK® for Industrial Control Systems. The CyOTE program assesses observables accompanying techniques used prior to the triggering event to identify opportunities to detect malicious activity. If observables accompanying the attack techniques are perceived and investigated prior to the triggering event, earlier comprehension of malicious activity can take place. Fifteen of the identified techniques used during the Thyssenkrupp cyber attack were precursors to the triggering event. Analysis identified 369 observables associated with these precursor techniques, 316 of which were assessed to have an increased likelihood of being perceived in the 120 days preceding the triggering event. The response and comprehension time could have been reduced if the observables had been identified earlier. The information gathered in this report contributes to a library of observables tied to a repository of artifacts, data sources, and technique detection references for practitioners and developers to support the comprehension of indicators of attack. Asset owners and operators can use these products if they experience similar observables or to prepare for comparable scenarios.

45 MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEF↗

DOE OSTI2026

Chemically Enabled CO 2 -Enhanced Oil Recovery in Multi-Porosity, Hydrothermally Altered Carbonates in the Southern Michigan Basin (Final Technical Report)

This is the Final Technical Report for the project "Chemically Enabled CO 2 -Enhanced Oil Recovery in Multi-Porosity, Hydrothermally Altered Carbonates in the Southern Michigan Basin." Over the course of six years of collaboration between Battelle and project partners, all stated objectives of the program have been completed, including full geological characterization of the TBR trend (See companion report for Task2), laboratory and modeling experiments to determine the optimum composition and design of CO 2 -EOR operations in the TBR trend, execution of a field test of chemically-enhanced CO 2 in a TBR well, and integration of the data and learnings gathered during these efforts into a full-trend development plan. Detailed reporting on these activities, their outcomes, and implications for trend-wide development is provided in the report. This report and encompassed data will provide TBR field operators with detailed information on what worked, what did not work, and how to proceed with production optimization of their TBR assets using chemically-enhanced CO 2 -EOR. CO 2 -EOR is a relatively well understood and broadly implemented strategy for increasing incremental production across the oil and gas industry, but its application has been primarily focused on reservoirs with limited heterogeneity. The intention of this project was show first that the same physical mechanisms that improve recovery factors in homogeneous reservoirs (namely wettability alteration, viscosity alteration, oil swelling, and mobility control) are at play in heterogeneous reservoirs. This was proven by the project’s laboratory studies and dynamic simulations, with the potential exception of mobility control, which needs further study. The second intention was to demonstrate via direct field testing that CO 2 -EOR can work in a strongly heterogeneous reservoir. While the field test strategy implemented during this project did not succeed in producing oil, data gathered during the test sheds light on what may work for field operators who try chemically-enhanced CO 2 -EOR within their own reservoirs, significantly reducing the level of uncertainty carried by first-of-a-kind commercial efforts that could (and should) follow this test. Simultaneously, the project has identified several large-volume ethanol plants and other sources of CO 2 emissions in the region and provided a handrail that CO 2 emitters and field operators can leverage to capture, transport, and inject that CO 2 into their fields. This project has also shown that, in many cases, the economics of CO 2 -EOR in the TBR are attractive. And finally, by completing a project of this scope in the southern Michigan Basin, the project has contributed to the knowledge base and operational experience of field operators, state regulatory agencies, local service companies, and state universities, with CO 2 -EOR projects which should allow follow-on projects to proceed safely and efficiently.

02 PETROLEUM↗

NASA NTRS1970

Apollo 12 Mission Report

The Apollo 12 mission was the twelfth in a series of flights using Apollo flight hardware and was the second lunar landing. The purpose of the mission was to perform a precise lunar landing and to conduct a specific scientific exploration of a designated landing site in the Ocean of Storms. Since the performance of the entire spacecraft was excellent, this report discusses only the systems performance that significantly differed from that of previous missions. Because they were unique to Apollo 12, the lunar surface experiments, the precision landing operation, and lunar dust contamination are reported in sections 3, 4, and 6, respectively. A complete analysis of all flight data is not possible within the time allowed for preparation of this report. Therefore, report supplements will be published for certain Apollo 12 systems analyses, as shown in appendix E. This appendix also lists the current status of all Apollo mission supplements, either published or in preparation. Other supplements will be published as the need is identified. In this report, all actual times prior to earth landing are elapsed time from range zero, established as the integral second before lift-off. Range zero for this mission was 16:22:00 G.m.t., November 14, 1969. Greenwich mean time is used for all times after earth landing as well as for the discussions of the experiments left on the lunar surface. All references to mileage distance are in nautical miles.

Source record↗

NASA NTRS1983

The NASA Aviation Safety Reporting System

This is the fourteenth in a series of reports based on safety-related incidents submitted to the NASA Aviation Safety Reporting System by pilots, controllers, and, occasionally, other participants in the National Aviation System (refs. 1-13). ASRS operates under a memorandum of agreement between the National Aviation and Space Administration and the Federal Aviation Administration. The report contains, first, a special study prepared by the ASRS Office Staff, of pilot- and controller-submitted reports related to the perceived operation of the ATC system since the 1981 walkout of the controllers' labor organization. Next is a research paper analyzing incidents occurring while single-pilot crews were conducting IFR flights. A third section presents a selection of Alert Bulletins issued by ASRS, with the responses they have elicited from FAA and others concerned. Finally, the report contains a list of publications produced by ASRS with instructions for obtaining them.

Source record↗

NASA NTRS1983

Analysis of general aviation single-pilot IFR incident data obtained from the NASA Aviation Safety Reporting System

An analysis of incident data obtained from the NASA Aviation Safety Reporting System (ASRS) has been made to determine the problem areas in general aviation single-pilot IFR (SPIFR) operations. The Aviation Safety Reporting System data base is a compilation of voluntary reports of incidents from any person who has observed or been involved in an occurrence which was believed to have posed a threat to flight safety. This paper examines only those reported incidents specifically related to general aviation single-pilot IFR operations. The frequency of occurrence of factors related to the incidents was the criterion used to define significant problem areas and, hence, to suggest where research is needed. The data was cataloged into one of five major problem areas: (1) controller judgment and response problems, (2) pilot judgment and response problems, (3) air traffic control (ATC) intrafacility and interfacility conflicts, (4) ATC and pilot communication problems, and (5) IFR-VFR conflicts. In addition, several points common to all or most of the problems were observed and reported. These included human error, communications, procedures and rules, and work load.

Bergeron, H. P.↗

NASA NTRS1992

The Telecommunications and Data Acquisition Report

Archival reports on developments in programs managed by the Jet Propulsion Laboratory's (JPL's) Office of Telecommunications and Data Acquisition (TDA) are published in the TDA Progress Report. In the search for extraterrestrial intelligence (SETI), the TDA Progress Report reports on implementation and operations for searching the microwave spectrum. In solar system radar, it reports on the uses of the Goldstone Solar System Radar for scientific exploration of the planets, their rings and satellites, asteroids, and comets. In radio astronomy, the areas of support include spectroscopy, very long baseline interferometry, and astrometry. These three programs are performed for NASA's Office of Space Science and Applications (OSSA), with the Office of Space Operations funding DSN operational support.

Posner, Edward C.↗

NASA NTRS1992

NASA/DOD Aerospace Knowledge Diffusion Research Project. Report 13: Source selection and information use by US aerospace engineers and scientists: Results of a telephone survey

A telephone survey of U.S. aerospace engineers and scientists belonging to the Society of Automotive Engineers (SAE) was conducted between December 4, 1991 and January 5, 1992. The survey was undertaken to (1) validate the telephone survey as an appropriate technique for collecting data from U.S. aerospace engineers and scientists; (2) collect information about how the results of NASA/DoD aerospace research are used in the R&D process; (3) identify those selection criteria which affect the use of federally-funded aerospace R&D; and (4) obtain information that could be used to develop a self-administered mail questionnaire for use with the same population. The average rating of importance of U.S. government technical reports was 2.5 (on a 4-point scale); The mean/median number of times U.S. government technical reports were used per 6 months was 8/2. Factors scoring highest for U.S. government technical reports were technical accuracy (2.9), reliable data and technical information (2.8), and contains comprehensive data and information (2.7) on a 4-point system. The factors scoring highest for influencing the use of U.S. government technical reports were relevance (3.1), technical accuracy (3.06), and reliable data/information (3.02). Ease of use, familiarity, technical accuracy, and relevance correlated with use of U.S. government technical reports. Survey demographics, survey questionnaire, and the NASA/DoD Aerospace Knowledge Diffusion Research Project publications list are included.

Pinelli, Thomas E.↗

NASA NTRS1992

Monthly progress report

This report is the mid-year report intended for the design concepts for the communication network for the Advanced Solid Rocket Motor (ASRM) facility being built at Yellow Creek near Iuka, MS. The overall network is to include heterogeneous computers, to use various protocols, and to have different bandwidths. Performance consideration must be given to the potential network applications in the network environment. The performance evaluation of X window applications was given the major emphasis in this report. A simulation study using Bones will be included later. This mid-year report has three parts: Part 1 is an investigation of X window traffic using TCP/IP over Ethernet networks; part 2 is a survey study of performance concepts of X window applications with Macintosh computers; and the last part is a tutorial on DECnet protocols. The results of this report should be useful in the design and operation of the ASRM communication network.

Moorhead, Robert J., II↗

NASA NTRS1993

The Telecommunications and Data Acquisition Report

This quarterly publication provides archival reports on developments in programs managed by JPL's Office of Telecommunications and Data Acquisition (TDA). In space communications, radio navigation, radio science, and ground-based radio and radar astronomy, it reports on activities of the Deep Space Network (DSN) in planning, supporting research and technology, implementation, and operations. Also included are standards activity at JPL for space data and information systems and reimbursable DSN work performed for other space agencies through NASA. The preceding work is all performed for NASA's Office of Space Communications (OSC). The TDA Office also performs work funded by another NASA program office through and with the cooperation of OSC. This is the Orbital Debris Radar Program with tile Office of Space Systems Development. The TDA Office is directly involved in several tasks that directly support the Office of Space Science (OSS), with OSC funding DSN operational support. In radio science, The TDA Progress Report describes the spacecraft radio science program conducted using tile DSN. For the High-Resolution Microwave Survey (HRMS), the report covers implementation and operations for searching the microwave spectrum. In solar system radar, it reports on the uses of the Goldstone Solar System Radar for scientific exploration of the planets, their rings and satellites, asteroids, and comets. In radio astronomy, the areas off support include spectroscopy, very long baseline interferometry, and astrometry.

Edward C Posner↗

NASA NTRS1993

The atmospheric effects of stratospheric aircraft: A third program report

A third report from the Atmospheric Effects of Stratospheric Aircraft (AESA) component of NASA's High-Speed Research Program (HSRP) is presented. Market and technology considerations continue to provide an impetus for high-speed civil transport research. A recent United Nations Environment Program scientific assessment showed that considerable uncertainty still exists about the possible impact of aircraft on the atmosphere. The AESA was designed to develop the body of scientific knowledge necessary for the evaluation of the impact of stratospheric aircraft on the atmosphere. The first Program report presented the basic objectives and plans for AESA. This third report marks the midpoint of the program and presents the status of the ongoing research on the impact of stratospheric aircraft on the atmosphere as reported at the third annual AESA Program meeting in June 1993. The focus of the program is on predicted atmospheric changes resulting from projected HSCT emissions. Topics reported on cover how high-speed civil transports (HSCT) might affect stratospheric ozone, emissions scenarios and databases to assess potential atmospheric effects from HSCT's, calculated results from 2-D zonal mean models using emissions data, engine trace constituent measurements, and exhaust plume/aircraft wake vortex interactions.

Stolarski, Richard S.↗

NASA NTRS1991

The Telecommunications and Data Acquisition Report

Posner, Edward C.↗

NASA NTRS1994

NASA/DOD Aerospace Knowledge Diffusion Research Project. Report 31: The technical communications practices of US aerospace engineers and scientists: Results of the phase 1 SME mail survey

The U.S. government technical report is a primary means by which the results of federally funded research and development (R&D) are transferred to the U.S. aerospace industry. However, little is known about this information product in terms of its actual use, importance, and value in the transfer of federally funded R&D. To help establish a body of knowledge, the U.S. government technical report is being investigated as part of the NASA/DOD Aerospace Knowledge Diffusion Research Project. In this report, we summarize the literature on technical reports and provide a model that depicts the transfer of federally funded aerospace R&D via the U.S. government technical report. We present results from our investigation of aerospace knowledge diffusion vis-a-vis the U.S. government technical communications practices of U.S. aerospace engineers and scientists affiliated with, not necessarily belonging to, the Society of Manufacturing Engineers (SME).

Pinelli, Thomas E.↗

NASA NTRS1996

NASA/DOD Aerospace Knowledge Diffusion Research Project: The Technical Communications Practices of US Aerospace Engineers and Scientists: Results of the Phase 3 US Aerospace Engineering Educators Survey - Report 45

The U.S. government technical report is a primary means by which the results of federally funded research and development (R&D) are transferred to the U.S. aerospace industry. However, little is known about this information product in terms of its actual use, importance, and value in the transfer of federally funded R&D. Little is also known about the intermediary-based system that is used to transfer the results of federally funded R&D to the U.S. aerospace industry. To help establish a body of knowledge, the U.S. government technical report is being investigated as part of the NASA/DOD Aerospace Knowledge Diffusion Research Project. In this report, we summarize the literature on technical reports, present a model that depicts the transfer of federally funded aerospace R&D via the U.S. government technical report, and present the results of research that investigated aerospace knowledge diffusion vis-a-vis the technical communication practices of U.S. aerospace engineers and scientists who were members of the American Institute of Aeronautics and Astronautics (AIAA) and identified themselves as educators.

Pinelli, Thomas E.↗

NASA NTRS1996

Research Projects, Technical Reports and Publications

The Research Institute for Advanced Computer Science (RIACS) was established by the Universities Space Research Association (USRA) at the NASA Ames Research Center (ARC) on June 6, 1983. RIACS is privately operated by USRA, a consortium of universities with research programs in the aerospace sciences, under contract with NASA. The primary mission of RIACS is to provide research and expertise in computer science and scientific computing to support the scientific missions of NASA ARC. The research carried out at RIACS must change its emphasis from year to year in response to NASA ARC's changing needs and technological opportunities. A flexible scientific staff is provided through a university faculty visitor program, a post doctoral program, and a student visitor program. Not only does this provide appropriate expertise but it also introduces scientists outside of NASA to NASA problems. A small group of core RIACS staff provides continuity and interacts with an ARC technical monitor and scientific advisory group to determine the RIACS mission. RIACS activities are reviewed and monitored by a USRA advisory council and ARC technical monitor. Research at RIACS is currently being done in the following areas: Advanced Methods for Scientific Computing High Performance Networks During this report pefiod Professor Antony Jameson of Princeton University, Professor Wei-Pai Tang of the University of Waterloo, Professor Marsha Berger of New York University, Professor Tony Chan of UCLA, Associate Professor David Zingg of University of Toronto, Canada and Assistant Professor Andrew Sohn of New Jersey Institute of Technology have been visiting RIACS. January 1, 1996 through September 30, 1996 RIACS had three staff scientists, four visiting scientists, one post-doctoral scientist, three consultants, two research associates and one research assistant. RIACS held a joint workshop with Code 1 29-30 July 1996. The workshop was held to discuss needs and opportunities in basic research in computer science in and for NASA applications. There were 14 talks given by NASA, industry and university scientists and three open discussion sessions. There were approximately fifty participants. A proceedings is being prepared. It is planned to have similar workshops on an annual basis. RIACS technical reports are usually preprints of manuscripts that have been submitted to research 'ournals or conference proceedings. A list of these reports for the period January i 1, 1996 through September 30, 1996 is in the Reports and Abstracts section of this report.

Oliger, Joseph↗

NASA NTRS1994

Third Report of the Task Force on the Shuttle-Mir Rendezvous and Docking Missions

In May 1994, the Task Force on the Shuttle-Mir Rendezvous and Docking Missions was established by the NASA Advisory Council. Its purpose is to review Phase 1 (Shuttle-Mir) planning, training, operations, rendezvous and docking, and management and to provide interim reports containing specific recommendations to the Advisory Council. Phase 1 represents the building block to create the experience and technical expertise for an International Space Station. The Phase 1 program brings together the United States and Russia in a major cooperative and contractual program that takes advantage of both countries' capabilities. The content of the Phase 1 program consists of the following elements as defined by the Phase 1 Program Management Plan, dated October 6, 1994: Shuttle-Mir rendezvous and docking missions; astronaut long duration presence on Mir Requirements for Mir support of Phase 1 when astronauts are not on board; outfitting Spektr and Priroda modules with NASA science, research, and risk mitigation equipment Related ground support requirements of NASA and the Russian Space Agency (RSA) to support Phase 1 Integrated NASA and RSA launch schedules and manifests The first meeting of the Task Force was held at the Johnson Space Center (JSC) on May 24 and 25, 1994 with a preliminary report submitted to the NASA Advisory Council on June 6, 1994. The second meeting of the Task Force was held at JSC on July 12 and 13, 1994 and a detailed report containing a series of specific recommendations was submitted on July 29, 1994. This report reflects the results of the third Task Force meeting which was held at JSC on 11 and 12 October, 1994. The briefings presented at that meeting reviewed NASA's response to the Task Force recommendations made to date and provided background data and current status on several critical areas which the Task Force had not addressed in its previous reports.

Source record↗

NASA NTRS1996

STS-77 Space Shuttle Mission Report

The STS-77 Space Shuttle Program Mission Report summarizes the Payload activities as well as the: Orbiter, External Tank (ET), Solid Rocket Booster (SRB), Reusable Solid Rocket Motor (RSRM), and the Space Shuttle Main Engine (SSME) systems performance during the seventy-seventh flight of the Space Shuttle Program, the fifty-second flight since the return-to-flight, and the eleventh flight of the Orbiter Endeavour (OV-105). STS-77 was also the last flight of OV-105 prior to the vehicle being placed in the Orbiter Maintenance Down Period (OMDP). In addition to the Orbiter, the flight vehicle consisted of an ET that was designated ET-78; three SSME's that were designated as serial numbers 2037, 2040, and 2038 in positions 1, 2, and 3, respectively; and two SRB's that were designated BI-080. The RSRM's, designated RSRM-47, were installed in each SRB and the individual RSRM's were designated as 360TO47A for the left SRB, and 360TO47B for the right SRB. The STS-77 Space Shuttle Program Mission Report fulfills the Space Shuttle Program requirement as documented in NSTS 07700, Volume VII, Appendix E. The requirement stated in that document is that each organizational element supporting the Program will report the results of their hardware (and software) evaluation and mission performance plus identify all related in-flight anomalies. The primary objectives of this flight were to successfully perform the operations necessary to fulfill the requirements of Spacehab-4, the SPARTAN 207/inflatable Antenna Experiment (IAE), and the Technology Experiments Advancing Missions in Space (TEAMS) payload. Secondary objectives of this flight were to perform the experiments of the Aquatic Research Facility (ARF), Brilliant Eyes Ten-Kelvin Sorption Cryocooler Experiment (BETSCE), Biological Research in Canisters (BRIC), Get-Away-Special (GAS), and GAS Bridge Assembly (GBA). The STS-77 mission was planned as a 9-day flight plus 1 day, plus 2 contingency days, which were available for weather avoidance or Orbiter contingency operations. The sequence of events for the STS-77 mission is shown in Table 1, and the Space Shuttle Vehicle Management Office Problem Tracking List is shown in Table 11. The Government Fumished Equipment/Flight Crew Equipment (GFE/FCE) Problem Tracking List is shown in Table II. Appendix A lists the sources of data, both formal and informal, that were used to prepare this report. Appendix B provides the definition of acronyms and abbreviations used throughout the report. All times during the flight are given in Greenwich mean time (G.m.t.) and mission elapsed time (MET). The six-person crew for STS-77 consisted of John H. Casper, Col., U. S. Air Force, Commander; Curtis L. Brown, Jr., Lt. Col., U. S. Air Force, Pilot; Andrew S. W. Thomas, Civilian, Ph.D., Mission Specialist 1; Daniel W. Bursch, CDR., U. S. Navy, Mission Specialist 2; Mario Runco, Jr., Civilian, Mission Specialist 3; and Marc Gameau, Civilian, PhD, Mission Specialist 4.

Fricke, Robert W., Jr.↗

NASA NTRS1996

STS-78 Space Shuttle Mission Report

The STS-78 Space Shuttle Program Mission Report summarizes the Payload activities as well as the Orbiter, External Tank (ET), Solid Rocket Booster (SRB), Reusable Solid Rocket Motor (RSRM), and the Space Shuttle main engine (SSME) systems performance during the seventy-eighth flight of the Space Shuttle Program, the fifty-third flight since the return-to-flight, and the twentieth flight of the Orbiter Columbia (OV-102). In addition to the Orbiter, the flight vehicle consisted of an ET that was designated ET-79; three SSME's that were designated as serial numbers 2041, 2039, and 2036 in positions 1, 2, and 3, respectively; and two SRB's that were designated BI-081. The RSRM's, designated RSRM-55, were installed in each SRB and the individual RSRM's were designated as 360L055A for the left SRB, and 360L055B for the right SRB. The STS-78 Space Shuttle Program Mission Report fulfills the Space Shuttle Program requirement as documented in NSTS 07700, Volume 7, Appendix E. The requirement stated in that document is that each organizational element supporting the Program will report the results of their hardware (and software) evaluation and mission performance plus identify all related in-flight anomalies. The primary objective of this flight was to successfully perform the planned operations of the Life and Microgravity Spacelab experiments. The secondary objectives of this flight were to complete the operations of the Orbital Acceleration Research Experiment (OARE), Biological Research in Canister Unit-Block II (BRIC), and the Shuttle Amateur Radio Experiment II-Configuration C (SAREX-II). The STS-78 mission was planned as a 16-day, plus one day flight plus two contingency days, which were available for weather avoidance or Orbiter contingency operations. The sequence of events for the STS-78 mission is shown in Table 1, and the Space Shuttle Vehicle Management Office Problem Tracking List is shown in Table 2. The Government Furnished Equipment/Flight Crew Equipment (GFE/FCE) Problem Tracking List is shown in Table 3. The Marshall Space Flight Center (MSFC) Problem Tracking List is shown in Table 4. Appendix A lists the sources of data, both formal and informal, that were used to prepare this report. Appendix B provides the definition of acronyms and abbreviations used throughout the report. All times during the flight are given in Greenwich mean time (G.m.t.) and mission elapsed time (MET).

Fricke, Robert W., Jr.↗