Search NASA⌕ Search

SEARCH · Search NASA

Results for “report”

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 307 records · Page 17
All sourcesNASA NTRSDOE OSTI
NASA NTRS1997

Aviation Safety Reporting System: Process and Procedures

The Aviation Safety Reporting System (ASRS) was established in 1976 under an agreement between the Federal Aviation Administration (FAA) and the National Aeronautics and Space Administration (NASA). This cooperative safety program invites pilots, air traffic controllers, flight attendants, maintenance personnel, and others to voluntarily report to NASA any aviation incident or safety hazard. The FAA provides most of the program funding. NASA administers the program, sets its policies in consultation with the FAA and aviation community, and receives the reports submitted to the program. The FAA offers those who use the ASRS program two important reporting guarantees: confidentiality and limited immunity. Reports sent to ASRS are held in strict confidence. More than 350,000 reports have been submitted since the program's beginning without a single reporter's identity being revealed. ASRS removes all personal names and other potentially identifying information before entering reports into its database. This system is a very successful, proof-of-concept for gathering safety data in order to provide timely information about safety issues. The ASRS information is crucial to aviation safety efforts both nationally and internationally. It can be utilized as the first step in safety by providing the direction and content to informed policies, procedures, and research, especially human factors. The ASRS process and procedures will be presented as one model of safety reporting feedback systems.

Connell, Linda J.↗
NASA NTRS2006

TOPEX Radar Altimeter Engineering Assessment Report Final Update-Side B Turn-On to End-of-Mission on October 9, 2005

This is the thirteenth and final report in a series of TOPEX Radar Altimeter Engineering Assessment Reports. The initial TOPEX Radar Altimeter Engineering Assessment Report, in February 1994, presented performance results for the NASA Radar Altimeter on the TOPEX/POSEIDON spacecraft, from its launch in August 1992 to February 1994. Since the time of that initial report and prior to this report, there have been eleven interim supplemental Engineering Assessment Reports, issued in March 1995, May 1996, March 1997, June 1998, August 1999, September 2000, June 2001, March 2002, May 2003, April 2004 and September 2005. The sixth supplement in September 2000 was the first assessment report that addressed Side B performance, and presented the altimeter performance from Side B turn-on until the end of calendar year 1999. This report extends the performance assessment of Side B to the final collection of data on October 9, 2005, and includes the performance assessment of Jason-1, the TOPEX follow-on mission, launched on December 7, 2001. This report provides some comparisons of Side A and Side B performance.

Lockwood, Dennis W.↗
NASA NTRS2011

Space Shuttle Guidance, Navigation, and Rendezvous Knowledge Capture Reports

This document is a catalog and readers guide to lessons learned, experience, and technical history reports, as well as compilation volumes prepared by United Space Alliance personnel for the NASA/Johnson Space Center (JSC) Flight Dynamics Division.1 It is intended to make it easier for future generations of engineers to locate knowledge capture documentation from the Shuttle Program. The first chapter covers observations on documentation quality and research challenges encountered during the Space Shuttle and Orion programs. The second chapter covers the knowledge capture approach used to create many of the reports covered in this document. These chapters are intended to provide future flight programs with insight that could be used to formulate knowledge capture and management strategies. The following chapters contain descriptions of each knowledge capture report. The majority of the reports concern the Space Shuttle. Three are included that were written in support of the Orion Program. Most of the reports were written from the years 2001 to 2011. Lessons learned reports concern primarily the shuttle Global Positioning System (GPS) upgrade and the knowledge capture process. Experience reports on navigation and rendezvous provide examples of how challenges were overcome and how best practices were identified and applied. Some reports are of a more technical history nature covering navigation and rendezvous. They provide an overview of mission activities and the evolution of operations concepts and trajectory design. The lessons learned, experience, and history reports would be considered secondary sources by historians and archivists.

John L Goodman↗
NASA NTRS2012

2011 NASA Range Safety Annual Report

Welcome to the 2011 edition of the NASA Range Safety Annual Report. Funded by NASA Headquarters, this report provides a NASA Range Safety overview for current and potential range users. As is typical with odd year editions, this is an abbreviated Range Safety Annual Report providing updates and links to full articles from the previous year's report. It also provides more complete articles covering new subject areas, summaries of various NASA Range Safety Program activities conducted during the past year, and information on several projects that may have a profound impact on the way business will be done in the future. Specific topics discussed and updated in the 2011 NASA Range Safety Annual Report include a program overview and 2011 highlights; Range Safety Training; Range Safety Policy revision; Independent Assessments; Support to Program Operations at all ranges conducting NASA launch/flight operations; a continuing overview of emerging range safety-related technologies; and status reports from all of the NASA Centers that have Range Safety responsibilities. Every effort has been made to include the most current information available. We recommend this report be used only for guidance and that the validity and accuracy of all articles be verified for updates. Once again the web-based format was used to present the annual report. We continually receive positive feedback on the web-based edition and hope you enjoy this year's product as well. As is the case each year, contributors to this report are too numerous to mention, but we thank individuals from the NASA Centers, the Department of Defense, and civilian organizations for their contributions. In conclusion, it has been a busy and productive year. I'd like to extend a personal Thank You to everyone who contributed to make this year a successful one, and I look forward to working with all of you in the upcoming year.

Dumont, Alan G.↗
NASA NTRS2016

Pilot Critical Incident Reports as a Means to Identify Human Factors of Remotely Piloted Aircraft

It has been estimated that aviation accidents are typically preceded by numerous minor incidents arising from the same causal factors that ultimately produced the accident. Accident databases provide in-depth information on a relatively small number of occurrences, however incident databases have the potential to provide insights into the human factors of Remotely Piloted Aircraft System (RPAS) operations based on a larger volume of less-detailed reports. Currently, there is a lack of incident data dealing with the human factors of unmanned aircraft systems. An exploratory study is being conducted to examine the feasibility of collecting voluntary critical incident reports from RPAS pilots. Twenty-three experienced RPAS pilots volunteered to participate in focus groups in which they described critical incidents from their own experience. Participants were asked to recall (1) incidents that revealed a system flaw, or (2) highlighted a case where the human operator contributed to system resilience or mission success. Participants were asked to only report incidents that could be included in a public document. During each focus group session, a note taker produced a de-identified written record of the incident narratives. At the end of the session, participants reviewed each written incident report, and made edits and corrections as necessary. The incidents were later analyzed to identify contributing factors, with a focus on design issues that either hindered or assisted the pilot during the events. A total of 90 incidents were reported. Human factor issues included the impact of reduced sensory cues, traffic separation in the absence of an out-the-window view, control latencies, vigilance during monotonous and ultra-long endurance flights, control station design considerations, transfer of control between control stations, the management of lost link procedures, and decision-making during emergencies. Pilots participated willingly and enthusiastically in the study, and generally had little difficulty recalling critical incidents. The results suggest that pilot interviews can be a productive method of gathering information on incidents that might not otherwise be reported. Some of the issues described in the reports have received significant attention in the literature, or are analogous to human factors of manned aircraft. In other cases, incident reports involved human factors that are poorly understood, and have not yet been the subject of extensive study. Although many of the reported incidents were related to pilot error, the participants also provided examples of the positive contribution that humans make to the operation of highly-automated systems.

unmanned aircraft systems↗
NASA NTRS2017

Relationship Between Carbon Dioxide Levels and Reported Congestion and Headaches on the International Space Station

Congestion is commonly reported during spaceflight, and most crewmembers have reported using medications for congestion during International Space Station (ISS) missions. Although congestion has been attributed to fluid shifts during spaceflight, fluid status reaches equilibrium during the first week after launch while congestion continues to be reported throughout long duration missions. Congestion complaints have anecdotally been reported in relation to ISS CO2 levels; this evaluation was undertaken to determine whether or not an association exists. METHODS: Reported headaches, congestion symptoms, and CO2 levels were obtained for ISS expeditions 2-31, and time-weighted means and single-point maxima were determined for 24-hour (24hr) and 7-day (7d) periods prior to each weekly private medical conference. Multiple imputation addressed missing data, and logistic regression modeled the relationship between probability of reported event of congestion or headache and CO2 levels, adjusted for possible confounding covariates. The first seven days of spaceflight were not included to control for fluid shifts. Data were evaluated to determine the concentration of CO2 required to maintain the risk of congestion below 1% to allow for direct comparison with a previously published evaluation of CO2 concentrations and headache. RESULTS: This study confirmed a previously identified significant association between CO2 and headache and also found a significant association between CO2 and congestion. For each 1-mm Hg increase in CO2, the odds of a crew member reporting congestion doubled. The average 7-day CO2 would need to be maintained below 1.5 mmHg to keep the risk of congestion below 1%. The predicted probability curves of ISS headache and congestion curves appear parallel when plotted against ppCO2 levels with congestion occurring at approximately 1mmHg lower than a headache would be reported. DISCUSSION: While the cause of congestion is multifactorial, this study showed congestion is associated with CO2 levels on ISS. Data from additional expeditions could be incorporated to further assess this finding. CO2 levels are also associated with reports of headaches on ISS. While it may be expected for astronauts with congestion to also complain of headaches, these two symptoms are commonly mutually exclusive. Furthermore, it is unknown if a temporal CO2 relationship exists between congestion and headache on ISS. CO2 levels were time-weighted for 24hr and 7d, and thus the time course of congestion leading to headache was not assessed; however, congestion could be an early CO2-related symptom when compared to headache. Future studies evaluating the association of CO2-related congestion leading to headache would be difficult due to the relatively stable daily CO2 levels on ISS currently, but a systematic study could be implemented on-orbit if desired.

Cole, Robert↗
NASA NTRS2013

2013 NASA Range Safety Annual Report

Welcome to the 2013 edition of the NASA Range Safety Annual Report. Funded by NASA Headquarters, this report provides an Agency overview for current and potential range users. This report contains articles which cover a variety of subject areas, summaries of various activities performed during the past year, links to past reports, and information on several projects that may have a profound impact on the way business will be conducted in the future. Specific topics discussed in the 2013 NASA Range Safety Annual Report include a program overview and 2013 highlights, Range Safety Training, Independent Assessments, support to Program Operations at all ranges conducting NASA launch/flight operations, a continuing overview of emerging range safety-related technologies, and status reports from all of the NASA Centers that have Range Safety responsibilities. Every effort has been made to include the most current information available. We recommend this report be used only for guidance and that the validity and accuracy of all articles be verified for updates. As is the case each year, we had a wide variety of contributors to this report from across our NASA Centers and the national range safety community at large, and I wish to thank them all. On a sad note, we lost one of our close colleagues, Dr. Jim Simpson, due to his sudden passing in December. His work advancing the envelope of autonomous flight safety systems software/hardware development leaves a lasting impression on our community. Such systems are being flight tested today and may one day be considered routine in the range safety business. The NASA family has lost a pioneer in our field, and he will surely be missed. In conclusion, it has been a very busy and productive year, and I look forward to working with all of you in NASA Centers/Programs/Projects and with the national Range Safety community in making Flight/Space activities as safe as they can be in the upcoming year.

Center Status↗
DOE OSTI2025

Reported Energy and Cost Savings from the DOE ESPC IDIQ Program: FY 2024

Energy Savings Performance Contracts (ESPCs) are a contractual mechanism that allow a federal agency to procure energy savings and facility improvements without upfront capital costs to reduce costs and enhance mission resiliency. ESPCs are covered under FAR Part 23.2, and 42 USC § 8287. Section 8287(a)(2)(A) of Title 42 of the U.S. Code requires that each energy savings performance contract (ESPC) undergo an annual energy audit, resulting in a separate audit report for every project. The objective of the present report is to compile and analyze all annual ESPC audit reports issued between October 1, 2023, and September 30, 2024, for projects awarded under Generations 1, 2, and 3 of DOE’s ESPC IDIQ contracts. During this period, 205 measurement and verification (M&V) reports were produced for 200 projects; the total number of reports exceeds the number of projects because some projects generated more than one report (for example, a few projects measure savings twice per year and produce two audit reports annually, each covering a different six-month period). By aggregating the results from these individual audits, the report determines the portfolio-wide realization rate of energy and cost savings for all active ESPC projects awarded under DOE’s IDIQ program.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗
NASA NTRS1975

Apollo experience report: Mission evaluation team postflight documentation

The various postflight reports prepared by the mission evaluation team, including the final mission evaluation report, report supplements, anomaly reports, and the 5-day mission report, are described. The procedures for preparing each report from the inputs of the various disciplines are explained, and the general method of reporting postflight results is discussed. Recommendations for postflight documentation in future space programs are included. The official requirements for postflight documentation and a typical example of an anomaly report are provided as appendixes.

Dodson, J. W.↗
NASA NTRS1981

Marketing information: The technical report as product

Technical reports constitute a product, the primary means for communicating the results of research to the user. The Langley scientific and technical information (STI) review and evaluation project undertook a review of the technical report as an effective product for information communication. Style manuals describing theory and practice in technical report preparation; publication manuals covering such factors as design, layout, and type style; and copies of technical reports were obtained from industrial, academic, governmental, and research organizations. Based on an analysis of this material, criteria will be established for the report components, for the relationship of the components within the report context, and for the overall report organization. The criteria will be used as bench marks and compared with the publication standards currently used to prepare NASA technical reports.

Stoher, F. F.↗
NASA NTRS1982

Survey of reader preferences concerning the format of NASA technical reports

A survey was conducted to determine the opinions of readers concerning the format (organization) of NASA technical reports and usage of technical report components. A survey questionnaire was sent to 513 LaRC engineers and scientists and 600 engineers and scientists from three (3) professional/technical societies. The response rates were 74 and 85 percent, respectively. The questionnaire included the order in which users read report components, the components reviewed or read to determine whether to read a report, report components which could be deleted, the desirability of a table of contents, the desirability of both a summary and abstract, the location of the symbols list and glossary, the integration of illustrative material, the preferred format for reference citations, column layout and right margin treatment, and person/voice. The results of the reader preference survey indicated that the conclusion was the component most often ready by survey respondents. The summary, conclusion, abstract, title page, and introduction were the components used most frequently to determine if a report would actually be read. Respondents indicated that a summary as well as an abstract should be included, that the definition of symbols and glossary of terms should be located in the front of the report, and that illustrative material should be integrated with the text rather than grouped at the end of the report. Citation by number was the preferred format for references. A one-column, ragged right margin was preferred. Third person, passive voice was the style of writing preferred by the respondents.

Pinelli, T. E.↗
NASA NTRS1995

NASAwide electronic publishing system: Electronic printing and duplicating, stage-2 evaluation report (GSFC)

The NASA Scientific and Technical Information Office was assigned the responsibility to continue with the expansion of the NASAwide networked electronic duplicating effort by including the Goddard Space Flight Center (GSFC) as an additional node to the existing configuration of networked electronic duplicating systems within NASA. The subject of this report is the evaluation of a networked electronic duplicating system which meets the duplicating requirements and expands electronic publishing capabilities without increasing current operating costs. This report continues the evaluation reported in 'NASA Electronic Publishing System - Electronic Printing and Duplicating Evaluation Report' (NASA TM-106242) and 'NASA Electronic Publishing System - Stage 1 Evaluation Report' (NASA TM-106510). This report differs from the previous reports through the inclusion of an external networked desktop editing, archival, and publishing functionality which did not exist with the previous networked electronic duplicating system. Additionally, a two-phase approach to the evaluation was undertaken; the first was a paper study justifying a 90-day, on-site evaluation, and the second phase was to validate, during the 90-day evaluation, the cost benefits and productivity increases that could be achieved in an operational mode. A benchmark of the functionality of the networked electronic publishing system and external networked desktop editing, archival, and publishing system was performed under a simulated daily production environment. This report can be used to guide others in determining the most cost effective duplicating/publishing alternative through the use of cost/benefit analysis and return on investment techniques. A treatise on the use of these techniques can be found by referring to 'NASA Electronic Publishing System -Cost/Benefit Methodology' (NASA TM-106662).

Tuey, Richard C.↗
NASA NTRS1999

International VLBI Service for Geodesy and Astrometry: 1999 Annual Report

This volume of reports is the 1999 Annual Report of the International VLBI Service for Geodesy and Astrometry -IVS. The individual reports were contributed by VLBI groups in the international geodetic community who constitute the components of IVS. The 1999 Annual Report documents the work of the IVS components for the year ending March 1, 1999, the official inauguration date of IVS. As the newest of the space technique services, IVS decided to publish this Annual Report as a reference to our organization and its components. The entire contents of this Annual Report also appear on the IVS website at: http://ivscc.gsfc.nasa.gov/pub/arl999. The IVS 1999 Annual Report will be a valuable reference for information about IVS and its components. This Annual Report will serve as a baseline from which we can measure the anticipated progress of IVS in coming years.

Vandenberg, Nancy R.↗
NASA NTRS1996

Early Warning: Development of Confidential Incident Reporting Systems

Accidents hardly ever happen without warning. The combination, or sequence, of failures and mistakes that cause an accident may indeed be unique but the individual failures and mistakes rarely are. In the USA in 1974 the crews on two different aircraft misunderstood the same aeronautical chart and descended towards their destination dangerously early towards a mountain. The first crew were in good weather conditions and could see the mountain and resolved their misinterpretation of the chart. The second crew six weeks later were not so lucky. In cloud they had no clues to point out their mistake nor the presence of the mountain. The resulting crash and the ensuing inquiry, which brought to light the previous incident, shocked the country but gave it the impetus to instigate a safety reporting system. This system eventually became the NASA's Aviation Safety Reporting System (ASRS). The programme collects incident reports from pilots, controllers, mechanics, cabin attendants and many others involved in aviation operations. By disseminating this safety information the ASRS has helped enormously to give US airlines and airspace the highest safety standards. Accident prevention is a goal sought by everyone in the aviation industry and establishing effective incident reporting programmes can go a long way toward achieving that goal. This article will describe the steps and issues required to establish an incident reporting system. The authors summarize the lessons learned from the ASRS, now in its twentieth year of operation and from the Confidential Human Factors Reporting (HER) Programme run by British Airways, an airline that is a recognized world leader in safety reporting and analysis. The differences between government and airline operation of confidential safety reporting systems will be addressed.

OLeary, Mike J.↗
NASA NTRS2014

Challenges in Evaluating Relationships Between Quantitative Data (Carbon Dioxide) and Qualitative Data (Self-Reported Visual Changes)

Understanding the nuances in clinical data is critical in developing a successful data analysis plan. Carbon dioxide (CO2) data are collected on board the International Space Station (ISS) in a continuous stream. Clinical data on ISS are primarily collected via conversations between individual crewmembers and NASA Flight Surgeons during weekly Private Medical Conferences (PMC). Law, et.al, 20141 demonstrated a statistically significant association between weekly average CO2 levels on ISS and self-reported headaches over the reporting period from March 14, 2001 to May 31, 2012. The purpose of this analysis is to describe the evaluation of a possible association between visual changes and CO2 levels on ISS and to discuss challenges in developing an appropriate analysis plan. METHODS & PRELIMINARY RESULTS: A first analysis was conducted following the same study design as the published work on CO2 and self-reported headaches1; substituting self-reported changes in visual acuity in place of self-reported headaches. The analysis demonstrated no statistically significant association between visual impairment characterized by vision symptoms self-reported during PMCs and ISS average CO2 levels over ISS missions. Closer review of the PMC records showed that vision outcomes are not well-documented in terms of clinical severity, timing of onset, or timing of resolution, perhaps due to the incipient nature of vision changes. Vision has been monitored in ISS crewmembers, pre- and post-flight, using standard optometry evaluations. In-flight visual assessments were limited early in the ISS program, primarily consisting of self-perceived changes reported by crewmembers. Recently, on-orbit capabilities have greatly improved. Vision data ranges from self-reported post-flight changes in visual acuity, pre- to postflight changes identified during fundoscopic examination, and in-flight progression measured by advanced on-orbit clinical imaging capabilities at predetermined testing intervals. In contrast, CO2 data are recorded in a continuous stream over time; however, for the initial analysis this data was categorized into weekly averages.

Mendez, C. M.↗
NASA NTRS2020

Monitoring Water-Related Ecosystems with Earth Observation Data in Support of Sustainable Development Goal (SDG) 6 Reporting

Lack of national data on water-related ecosystems is a major challenge to achieving the Sustainable Development Goal (SDG) 6 targets by 2030. Monitoring surface water extent, wetlands, and water quality from space can be an important asset for many countries in support of SDG 6 reporting. We demonstrate the potential for Earth observation (EO) data to support country reporting for SDG Indicator 6.6.1, ‘Change in the extent of water-related ecosystems over time’ and identify important considerations for countries using these data for SDG reporting. The spatial extent of water-related ecosystems, and the partial quality of water within these ecosystems is investigated for seven countries. Data from the Moderate Resolution Imaging Spectroradiometer (MODIS) and Landsat 5, 7, and 8 with Shuttle Radar Topography Mission (SRTM) are used to measure surface water extent at 250 m and 30 m spatial resolution, respectively, in Cambodia, Jamaica, Peru, the Philippines, Senegal, Uganda, and Zambia. The extent of mangroves is mapped at 30 m spatial resolution using Landsat 8 Operational Land Imager (OLI), Sentinel-1, and SRTM data for Jamaica, Peru, and Senegal. Using Landsat 8 and Sentinel 2A imagery, total suspended solids and chlorophyll-a are mapped over time for a select number of large surface water bodies in Peru, Senegal, and Zambia. All of the EO datasets used are of global coverage and publicly available at no cost. The temporal consistency and long time-series of many of the datasets enable replicability over time, making reporting of change from baseline values consistent and systematic. We find that statistical comparisons between different surface water data products can help provide some degree of confidence for countries during their validation process and highlight the need for accuracy assessments when using EO-based land change data for SDG reporting. We also raise concern that EO data in the context of SDG Indicator 6.6.1 reporting may be more challenging for some countries, such as small island nations, than others to use in assessing the extent of water-related ecosystems due to scale limitations and climate variability. Country-driven validation of the EO data products remains a priority to ensure successful data integration in support of SDG Indicator 6.6.1 reporting. Multi-country studies such as this one can be valuable tools for helping to guide the evolution of SDG monitoring methodologies and provide a useful resource for countries reporting on water-related ecosystems. The EO data analyses and statistical methods used in this study can be easily replicated for country-driven validation of EO data products in the future.

water-related ecosystems; surface water extent; ma↗
NASA NTRS2023

Launch Complex 34, SWMU CCO542022 DNAPL Source Zone Operations, Maintenance, and Monitoring, Site-Wide Long-Term Monitoring, and Hot Spot 6 Air Sparge System Annual Performance Monitoring Report Cape Canaveral Space Force Station, Florida

This Annual Performance Monitoring Report (PMR) for the Dense Non-Aqueous Phase Liquid (DNAPL) Source Zone (DSZ), Site-Wide Long-Term Monitoring (LTM), and Hot Spot (HS) 6 Air Sparge (AS) System presents the results of Year 13 operation of the hydraulic containment (HC) Interim Measure (IM), the results of performance monitoring direct-push technology (DPT) sampling and monitoring well sampling conducted in the DSZ, results of the biennial site-wide LTM event, and the results of operations and performance sampling of the HS 6 AS IM at Launch Complex 34 (LC34), located at Cape Canaveral Space Force Station (CCSFS), Florida. This site has been designated Solid Waste Management Unit (SWMU) CC054 under the Kennedy Space Center (KSC) Resource Conservation and Recovery Act (RCRA) Corrective Action Program. For the site-wide biennial LTM event, a total of 55 monitoring wells were sampled for volatile organic compounds (VOCs) in February 2023 and one well was sampled for polychlorinated biphenyls (PCBs) in December 2022. One well planned for VOC sampling was found to be destroyed and could not be sampled (CW0002). The LTM wells are screened in two lithologic zones: Layer 1 (0 to 25 feet below land surface [bls]) and Layer 2 (25 to 30 ft bls), and are located in the outlying areas of LC34 to monitor groundwater conditions within the Low-Concentration Plume (LCP), defined as concentrations exceeding Groundwater Cleanup Target Levels (GCTLs), and the High-Concentration Plume (HCP), defined as concentrations exceeding Natural Attenuation Default Concentrations (NADCs). Results from the biennial sampling event indicated overall plume stability and delineation for the plume, which extends over 300 acres. The operational period for Year 13 of the HCS was from April 1, 2022 to March 31, 2023. Operational runtime for the system was 90 percent during Year 13, with downtime events attributed to planned maintenance, system repairs, and power outages. As of March 31, 2023, a total of 313,673,241 cumulative gallons of groundwater containing 88,337 pounds of VOCs have been removed by the HCS. Influent concentrations of trichloroethene (TCE) have decreased since startup from approximately 280,000 μg/L (January 2010) to 12,000 μg/L (March 2023). During the reporting period, all effluent concentrations from the HCS (aqueous and vapor) were below regulatory reporting limits, indicating the system continues to operate as intended. Performance monitoring was conducted in December 2022 within the DSZ to evaluate TCE contamination. Groundwater samples were collected via DPT at nine locations, consistent with previous events between 2017 and 2021. Full vertical profile sampling was completed at each DPT from 8 to 98 feet bls, at 5-foot intervals. The DPT performance monitoring results are summarized in this PMR. The results revealed TCE remains at concentrations greater than 11,000 μg/L in the DSZ (1-percent solubility, indicative of DNAPL) at eight of the nine DPT locations and at depths ranging from 8 to 98 feet bls. In addition to DPT sampling, groundwater samples were collected from deep monitoring wells in the DSZ area (Layers 7 and 8) in December 2022 to verify vertical delineation. Layer 7/8 monitoring well results were non-detect in December 2022, with exception of three wells (IW0162, IW043D2, and IW044D2), where TCE, cis-1,2-dichloroethene (cDCE), and/or vinyl chloride (VC) were detected above GCTLs. These wells are screened 105 to 115 feet bls, which is below the existing recovery well capture zone. TCE was first detected in IW0162 in December 2021 and has since been sampled at least monthly to monitor TCE concentrations. The maximum TCE concentration during this operational period was 15,000 μg/L at IW0162 in March 2023. Because of the increased TCE concentrations in this well, a new recovery well (RW21D), screened 86 to 106 feet bls, was installed in January 2023 and incorporated into existing HCS operations. The HS 6 AS IM was initiated in 2018 with 160 AS wells, and expanded in 2019 with an additional 140 AS wells. Quarterly performance monitoring was reduced to semi-annual in 2020. The HS 6 AS system remained operational during the reporting period covered under this report. The results of the HS 6 system operation and semi-annual performance monitoring are summarized in this report. Semi-annual monitoring results collected in April and October 2022 show concentrations of contaminants of concern (cDCE, trans-1,2-dichloroethene, and vinyl chloride) are generally decreasing and not impacting the surface water drainage canal, indicating the HS 6 IM is meeting objectives. A Phase Two Expansion of the HS 6 AS IM was recently completed. As of the date of this report, the expansion became operational in August 2023 and the first quarter of monitoring was conducted in November 2023. Details of the construction, start-up, and performance monitoring will be included in a future Annual PMR. Overall, the tasks associated with Year 13 operation of the HC IM, operation of the HS 6 AS IM, and biennial site-wide sampling were performed in accordance with recommendations included in the previous 2021 LC34 (Year 12) annual report. Evaluation of results from the HC IM and HS 6 IM show that these systems are operating as designed and meeting performance objectives. Results from the site-wide biennial LTM program also show that the overall network of monitoring wells is adequate to continue monitoring plume-wide conditions.

Complex 34↗
DOE OSTI2024

Submitting a Standard Compliance Annual Report: EPAct State and Alternative Fuel Provider Fleet Program User Guide

State government and alternative fuel provider fleets covered under the State and Alternative Fuel Provider Fleet Program (Program) established pursuant to the Energy Policy Act of 1992 (EPAct) may use the Compliance Reporting Tool to track and report on several compliance activities. These activities include, but are not limited to, completing Standard Compliance annual reports, Alternative Compliance notices of intent, and exemption requests. Covered fleets can access the Compliance Tool through the Program's website at https://epact.energy.gov/users/sign_in. Covered fleet points of contact should bookmark the Compliance Reporting Tool for future access. This user guide addresses how to complete and submit Standard Compliance annual reports, including getting started with reporting, submitting annual reports, submitting exemption requests, and viewing annual reports.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗