SEARCH · Search NASA

Results for “lessons learned process”

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 199 records · Page 11

All sources NASA NTRS DOE OSTI

NASA NTRSDate not supplied

Risk Reduction through Early Software Prototyping for the Mars Ascent Vehicle

Despite the critical nature flight software plays in the development of spacecraft, software development teams are often brought on to the project after initial requirements definition and design efforts have started, and well after the conceptual design phase has completed. The flight software development team for the Mars Ascent Vehicle has supported the project from project formulation and conceptual design into the formal design and development. This approach has allowed for the development of a robust software prototype that supported risk reduction in numerous areas for the project. Early software prototyping supported decision making in the areas of hardware selection and considerations, software architecture, and simulation requirements. The prototype software actively supported ongoing trade studies and analyses for the project and enable valuable collaboration across multiple subsystems as well as between MSFC and the Jet Propulsion Laboratory. This early development also allowed the team to leverage past projects’ lessons learned to make valuable process improvements.

Stefanie Justice↗

DOE OSTI2024

Practical challenges of model predictive control (MPC) for grid interactive small and medium commercial buildings

To the urgent call for mitigating climate change, substantial initiatives have been undertaken to deploy grid-interactive heating, ventilation, and air-conditioning (HVAC) controls, such as model predictive control (MPC) for buildings. These efforts typically aim to curtail peak energy demand, shift load and enhance overall energy efficiency. With the recent development of low-cost MPC technologies that don’t require extensive instrumentation or manual modeling, small and medium commercial buildings (SMCBs), which rarely utilize advanced HVAC control systems, have become candidates for grid-interactive efficient buildings (GEBs). However, despite the potential benefits and maturity of the technology itself, several practical challenges remain in real-world implementation. In this paper, we share the practical challenges that we have encountered in implementing and testing three types of MPC solutions (ON/OFF unit, dualfuel, and VRF systems) on multiple SMCB sites. We describe the MPC deployment process and discuss the lessons learned. The site selection, eligibility, and retrofit availability (e.g., utility price structure, thermostat communications, etc.) are the main discussion points at the beginning of the project. Also, the modeling automation and the best practices for interacting with endusers and handling erroneous situations are presented for successful operations.

woo Ham, Sang↗

NASA NTRS2006

Techniques for Embedding Instrumentation in Pressure Vessel Test Articles

Many interesting structural and thermal events occur in materials that are housed within a surrounding pressure vessel. In order to measure the environment during these events and explore their causes instrumentation must be installed on or in the material. Transducers can be selected that are small enough to be embedded within the test material but these instruments must interface with an external system in order to apply excitation voltages and output the desired data. The methods for installing the instrumentation and creating an interface are complicated when the material is located in a case or housing containing high pressures and hot gases. Installation techniques for overcoming some of these difficulties were developed while testing a series of small-scale solid propellant and hybrid rocket motors at Marshall Space Flight Center. These techniques have potential applications in other test articles where data are acquired from materials that require containment due to the severe environment encountered during the test process. This severe environment could include high pressure, hot gases, or ionized atmospheres. The development of these techniques, problems encountered, and the lessons learned from the ongoing testing process are summarized.

Cornelius, Michael↗

NASA NTRS2009

Spacecraft Electrical Connector Selection and Application Processes

This assessment was initiated by the NASA Engineering & Safety Center (NESC) after a number of recent "high profile" connector problems, the most visible and publicized of these being the problem with the Space Shuttle's Engine Cut-Off System cryogenic feed-thru connector. The NESC commissioned a review of NASA's connector selection and application processes for space flight applications, including how lessons learned and past problem records are fed back into the processes to avoid recurring issues. Team members were primarily from the various NASA Centers and included connector and electrical parts specialists. The commissioned study was conducted on spacecraft connector selection and application processes at NASA Centers. The team also compared the NASA spacecraft connector selection and application process to the military process, identified recent high profile connector failures, and analyzed problem report data looking for trends and common occurrences. The team characterized NASA's connector problem experience into a list of top connector issues based on anecdotal evidence of a system's impact and commonality between Centers. These top issues are as follows, in no particular rank order: electrically shorted, bent and/or recessed contact pins, contact pin/socket contamination leading to electrically open or intermittencies, connector plating corrosion or corrosion of connector components, low or inadequate contact pin retention forces, contact crimp failures, unmated connectors and mis-wiring due to workmanship errors during installation or maintenance, loose connectors due to manufacturing defects such as wavy washer and worn bayonet retention, damaged connector elastomeric seals and cryogenic connector failure. A survey was also conducted of SAE Connector AE-8C1 committee members regarding their experience relative to the NASA concerns on connectors. The most common responses in order of occurrence were contact retention, plating issues, worn-out or damaged coupling mechanisms, bent pins, contact crimp barrel cracking and torn seals. In addition to these common themes, responses included issues with markings, dimensional errors on the build, contact/socket damage (handling), manufacturing defects and customer misapplication and mishandling. The NESC team concluded that considering the large quantity and wide variety of connectors successfully flown on human and robotic space applications, the number of failures is quite low. However, "high profile" failures with significant cost, schedule, safety, and/or mission success impacts continue to occur. It was also concluded that connector failures occur throughout a system's life-cycle with the majority of connector issues application related. A number of recommendations were identified for improving NASA connector selection processes and overall space connector reliability and performance.

Iannello, Chris↗

NASA NTRS2002

Integrating Theory and Practice: Applying the Quality Improvement Paradigm to Product Line Engineering

My assertion is that not only are product lines a relevant research topic, but that the tools used by empirical software engineering researchers can address observed practical problems. Our experience at NASA has been there are often externally proposed solutions available, but that we have had difficulties applying them in our particular context. We have also focused on return on investment issues when evaluating product lines, and while these are important, one can not attain objective data on success or failure until several applications from a product family have been deployed. The use of the Quality Improvement Paradigm (QIP) can address these issues: (1) Planning an adoption path from an organization's current state to a product line approach; (2) Constructing a development process to fit the organization's adoption path; (3) Evaluation of product line development processes as the project is being developed. The QIP consists of the following six steps: (1) Characterize the project and its environment; (2) Set quantifiable goals for successful project performance; (3) Choose the appropriate process models, supporting methods, and tools for the project; (4) Execute the process, analyze interim results, and provide real-time feedback for corrective action; (5) Analyze the results of completed projects and recommend improvements; and (6) Package the lessons learned as updated and refined process models. A figure shows the QIP in detail. The iterative nature of the QIP supports an incremental development approach to product lines, and the project learning and feedback provide the necessary early evaluations.

Stark, Michael↗

NASA NTRS1996

Software Engineering Program: Software Process Improvement Guidebook

The purpose of this document is to provide experience-based guidance in implementing a software process improvement program in any NASA software development or maintenance community. This guidebook details how to define, operate, and implement a working software process improvement program. It describes the concept of the software process improvement program and its basic organizational components. It then describes the structure, organization, and operation of the software process improvement program, illustrating all these concepts with specific NASA examples. The information presented in the document is derived from the experiences of several NASA software organizations, including the SEL, the SEAL, and the SORCE. Their experiences reflect many of the elements of software process improvement within NASA. This guidebook presents lessons learned in a form usable by anyone considering establishing a software process improvement program within his or her own environment. This guidebook attempts to balance general and detailed information. It provides material general enough to be usable by NASA organizations whose characteristics do not directly match those of the sources of the information and models presented herein. It also keeps the ideas sufficiently close to the sources of the practical experiences that have generated the models and information.

Source record↗

NASA NTRS2017

Lessons Learned from Applying Design Thinking in a NASA Rapid Design Study in Aeronautics

In late 2015, NASA's Aeronautics Research Mission Directorate (ARMD) funded an experiment in rapid design and rapid teaming to explore new approaches to solving challenging design problems in aeronautics in an effort to cultivate and foster innovation. This report summarizes several lessons learned from the rapid design portion of the study. This effort entailed learning and applying design thinking, a human-centered design approach, to complete the conceptual design for an open-ended design challenge within six months. The design challenge focused on creating a capability to advance experimental testing of autonomous aeronautics systems, an area of great interest to NASA, the US government as a whole, and an entire ecosystem of users and developers around the globe. A team of nine civil servant researchers from three of NASA's aeronautics field centers with backgrounds in several disciplines was assembled and rapidly trained in design thinking under the guidance of the innovation and design firm IDEO. The design thinking process, while used extensively outside the aerospace industry, is less common and even counter to many practices within the aerospace industry. In this report, several contrasts between common aerospace research and development practices and design thinking are discussed, drawing upon the lessons learned from the NASA rapid design study. The lessons discussed included working towards a design solution without a set of detailed design requirements, which may not be practical or even feasible for management to ascertain for complex, challenging problems. This approach allowed for the possibility of redesigning the original problem statement to better meet the needs of the users. Another lesson learned was to approach problems holistically from the perspective of the needs of individuals that may be affected by advances in topic area instead of purely from a technological feasibility viewpoint. The interdisciplinary nature of the design team also provided valuable experience by allowing team members from different technological backgrounds to work side-by-side instead of dividing into smaller teams, as is frequently done in traditional multidisciplinary design. The team also learned how to work with qualitative data obtained primarily through the 70-plus interviews that were conducted over the course of this project, which was a sharp contrast to using quantitative data with regards to identifying, capturing, analyzing, storing, and recalling the data. When identifying potential interviewees who may have useful contributions to the design subject area, the team found great value in talking to non-traditional users and potential beneficiaries of autonomous aeronautics systems whose impact on the aeronautics autonomy ecosystem is growing swiftly. Finally, the team benefitted from using "sacrificial prototyping," which is a method of rapidly prototyping draft concepts and ideas with the intent of enabling potential users to provide significant feedback early in the design process. This contrasts the more common approach of using expensive prototypes that focus on demonstrating technical feasibility. The unique design approach and lessons learned by the team throughout this process culminated in a final design concept that was quite different than what the team originally assumed would be the design concept initially. A summary of the more usercentered final design concept is also provided.

McGowan, Anna-Maria↗

NASA NTRS2005

Engineering Lessons Learned and Systems Engineering Applications

Systems Engineering is fundamental to good engineering, which in turn depends on the integration and application of engineering lessons learned. Thus, good Systems Engineering also depends on systems engineering lessons learned from within the aerospace industry being documented and applied. About ten percent of the engineering lessons learned documented in the NASA Lessons Learned Information System are directly related to Systems Engineering. A key issue associated with lessons learned datasets is the communication and incorporation of this information into engineering processes. As part of the NASA Technical Standards Program activities, engineering lessons learned datasets have been identified from a number of sources. These are being searched and screened for those having a relation to Technical Standards. This paper will address some of these Systems Engineering Lessons Learned and how they are being related to Technical Standards within the NASA Technical Standards Program, including linking to the Agency's Interactive Engineering Discipline Training Courses and the life cycle for a flight vehicle development program.

Gill, Paul S.↗

DOE OSTI2026

Elevating Engagement: Insights for Energy Infrastructure Siting from Oregon Literature

Our study conducts a meta-synthesis of existing Oregon-based literature on stakeholder and community engagement methods across a variety of contexts to identify best practices and lessons learned to inform future engagement processes for Oregon’s energy siting. We analyze and synthesize these strategies to understand what has worked well across engagement practices and how we can integrate and learn from a variety of methods to develop more effective practices for engagement moving forward. We look at the successes and challenges for each method, applying lessons learned to the pre-permitting phase of energy development and infrastructure planning in Oregon. Our results synthesize key recommendations for engagement in the pre-permitting phase for energy infrastructure siting in Oregon, such as consensus and relationship building, local partnerships, and background research to understand community context.

energy infrastructure↗

NASA NTRS1982

Lessons learned - Americans in space

Milestones in the learning process during development of spaceflight capability for different NASA missions are traced from the initial launch of the Mercury escape rocket to the advent of the Shuttle. A detached heat shield on the first manned Mercury orbital flight led to a decision for reentry with retrorockets attached, a situation which demonstrated a need for on-line communications with the spacecraft construction engineers. The Gemini program served to develop EVA techniques and docking procedures essential for the Apollo missions. Apollo 8 circled the moon after only one manned test flight of the equipment due to the success of the first flight. Lunar landing simulation training exposed the astronauts to situations beyond the human ability to respond. The training was justified when computer overload required the pilot to retake manual control of some spacecraft functions during the successful first lunar landing. All lessons previously learned were used to safely return the damaged Apollo 13 to earth. The Skylab missions provided an opportunity to maintain rotating teams of flight controllers on a 24-hr/day basis for periods of months. Finally, the six-year hiatus of U.S. manned space activities between the end of the Skylab missions and the first Shuttle flight provided time for incorporating previous lessons into new procedures, training strategies, and data resources.

Kranz, E.↗

NASA NTRSDate not supplied

Having a Come-Apart: Lessons Learned from Additively Manufactured Hardware Failures

NASA has been engaged with additively manufactured (AM) process and component development since the 2000’s. AM offers various technical advantages, such as enhanced hardware design complexity, part consolidation, and processing of novel alloys in addition to programmatic advantages for reduction in processing time and cost. The focus of much of the AM development at NASA has been to mature the various processes, characterize material properties, develop standards, produce demonstrator parts, and integrate AM hardware in liquid rocket engines. These aspects have been demonstrated through process and design iterations using a methodical characterization, test-fail-fix cycles, as well as application and dissemination of lessons learned. In addition to these fundamental demonstrations of the AM process and hardware development, alloys that provide performance advantages in the high temperature and high-pressure environments have been matured for use in rocket engines. These environments are challenging for any alloy and any design, and the AM process is required to fully meet the intended design requirements. The importance of proper AM process was made evident in the failure of a Laser Powder Bed Fusion (L-PBF) copper-alloy combustion chamber during a hot-fire test due to a degraded material quality resulted from an AM process issue. The hot-fire test aimed to demonstrate high duty cycle under a risk-tolerant development project, where consequences of component failure would be minimal. However, the unintentional component failure emphasized the necessity of robust material characterization and rigorous process control procedures for the safe use of AM components in critical applications. In part, such concerns motivate the AM certification approach that NASA has recently adopted in NASA-STD-6030 “Additive Manufacturing Requirements for Spaceflight Systems”. This presentation provides an overview of the previously mentioned failure, a discussion on the evaluation of the failed chamber and supplemental chambers produced at the same time, a representative material samples that included intentional build witness lines, and a summary of the key results and recommendations from the evaluations. NASA continues to approach AM processes and designs with a level of risk and acceptance of failures that is appropriate for the project objectives, with the overall goal of safe implementation of AM technology and transferring AM technology into commercial space applications. The objective of this presentation is to provide awareness to the community working critical and non-critical AM components and the lessons learned on proper implementation of AM.

Additive Manufacturing↗

DOE OSTI2026

Mark-18A Target Material Recovery Program: Initial Hot Startup

The Savannah River National Laboratory (SRNL) has been tasked by the National Nuclear Security Administration to recover highly valued isotopes from irradiated Mark-18A (Mk-18A) targets. The Savannah River Site (SRS) has sixty-five Mk-18A targets available for the recovery of the high valued materials. The Mk-18A targets were manufactured with Pu-242 then irradiated under high neutron flux in K-Reactor at the SRS from 1968 to 1978. The sixty-five Mk-18A targets are currently stored in the SRS L-Area Basin and will be removed one at a time and individually transported to SRNL. Upon receipt at SRNL, the Mk-18A target material will be removed from the confinement, dissolved, chemically separated, and calcined to a stable oxide. The flowsheet is designed to recover the plutonium as well as the trivalent actinides. The original targets were manufactured with varying quantities of Pu-242, ranging from 5.2 grams to 121.5 grams. Taking a graded approach to process start up, the lowest loaded target (FT-80-03) was selected as the first target to be received and processed at SRNL. As operational experience and knowledge is gained from processing targets, higher loaded targets will be selected for processing to increase the quantities of valuable isotopes recovered. Due to dose concerns, the receipt and processing of the Mk-18A targets is performed in the SRNL Shielded Cells Facility. The targets are stored in a double J-can confinement in the L-Area Basin. A specially designed cask was procured for transport of the targets from L-Area to SRNL. Once received at SRNL, the targets are loaded into the back of Cell 7 and resized as they enter the cell. The resized targets (1/4 length) are then processed one at a time through the following processes: caustic dissolution and filtration, acidic dissolution and filtration, elutable Reillex anion exchange, diglycolamide (DGA) resin extraction, and DGA calcination. This processing results in two product streams. The first is an aqueous plutonium solution which is removed from the shielded cells and taken to a glovebox for further purification and conversion to an oxide. The second is a calcined oxide product containing the Am and Cm as well as other lanthanide fission products which is removed from the shielded cells using a bagless transfer system. Both materials are packaged for shipment to Oak Ridge National Laboratory (ORNL). This paper will discuss the operating experience, lessons learned, and results from initial process hot startup.

Armstrong, Christopher [Savannah River National La↗

NASA NTRS2017

Development of Reliable Life Support Systems

The life support systems on the International Space Station (ISS) are the culmination of an extensive effort encompassing development, design, and test to provide the highest possible confidence in their operation on ISS. Many years of development testing are initially performed to identify the optimum technology and the optimum operational approach. The success of this development program depends on the accuracy of the system interfaces. The critical interfaces include the specific operational environment, the composition of the waste stream to be processed and the quality of the product. Once the development program is complete, a detailed system schematic is built based on the specific design requirements, followed by component procurement, assembly, and acceptance testing. A successful acceptance test again depends on accurately simulating the anticipated environment on ISS. The ISS Water Recovery System (WRS) provides an excellent example of where this process worked, as well as lessons learned that can be applied to the success of future missions. More importantly, ISS has provided a test bed to identify these design issues. Mechanical design issues have included an unreliable harmonic drive train in the Urine Processor's fluids pump, and seals in the Water Processor's Catalytic Reactor with insufficient life at the operational temperature. Systems issues have included elevated calcium in crew urine (due to microgravity effect) that resulted in precipitation at the desired water recovery rate, and the presence of an organosilicon compound (dimethylsilanediol) in the condensate that is not well removed by the water treatment process. Modifications to the WRS to address these issues are either complete (and now being evaluated on ISS) or are currently in work to insure the WRS has the required reliability before embarking on a mission to Mars.

Carter, Layne↗

NASA NTRS2017

Development of Reliable Life Support Systems

Carter, Layne↗

NASA NTRS2011

A Framework for Successful Research Experiences in the Classroom: Combining the Power of Technology and Mentors

Authentic research opportunities in the classroom are most impactful when they are student-driven and inquiry-based. These experiences are even more powerful when they involve technology and meaningful connections with scientists. In today's classrooms, activities are driven by state required skills, education standards, and state mandated testing. Therefore, programs that incorporate authentic research must address the needs of teachers. NASA's Expedition Earth and Beyond (EEAB) Program has developed a framework that addresses teacher needs and incorporates the use of technology and access to mentors to promote and enhance authentic research in the classroom. EEAB is a student involvement program that facilitates student investigations of Earth or planetary comparisons using NASA data. To promote student-led research, EEAB provides standards-aligned, inquiry-based curricular resources, an implementation structure to facilitate research, educator professional development, and ongoing support. This framework also provides teachers with the option to incorporate the use of technology and connect students with a mentor, both of which can enrich student research experiences. The framework is structured by a modeled 9-step process of science which helps students organize their research. With more schools gaining increased access to technology, EEAB has created an option to help schools take advantage of students' interest and comfort with technology by leveraging the use of available technologies to enhance student research. The use of technology not only allows students to collaborate and share their research, it also provides a mechanism for them to work with a mentor. This framework was tested during the 2010/2011 school year. Team workspaces hosted on Wikispaces for Educators allow students to initiate their research and refine their research question initially without external input. This allows teams to work independently and rely on the skills and interests of team members. Once teams finalize their research question, they are assigned a mentor. The mentor introduces himself/herself, acknowledges the initial work the team has conducted, and asks a focused question to help open the lines of communication. Students continue to communicate with their mentor throughout their research. As research is completed, teams can share their investigation during a virtual presentation. These live presentations allow students to share their research with their mentor, other scientists, other students, parents, and school administrators. After the initial year of testing this authentic research process, EEAB is working to address the many lessons learned. This will allow the program to refine and improve the overall process in an effort to maximize the benefits. Combined, these powerful strategies provide a successful framework to help teachers enhance the skills and motivation of their students, preparing them to become the next generation of scientists, explorers, and STEM-literate citizens of our nation.

Graff, Paige Valderrama↗

NASA NTRS2011

Habitat Demonstration Unit (HDU) Pressurized Excursion Module (PEM) Systems Integration Strategy

The Habitat Demonstration Unit (HDU) project team constructed an analog prototype lunar surface laboratory called the Pressurized Excursion Module (PEM). The prototype unit subsystems were integrated in a short amount of time, utilizing a rapid prototyping approach that brought together over 20 habitation-related technologies from a variety of NASA centers. This paper describes the system integration strategies and lessons learned, that allowed the PEM to be brought from paper design to working field prototype using a multi-center team. The system integration process was based on a rapid prototyping approach. Tailored design review and test and integration processes facilitated that approach. The use of collaboration tools including electronic tools as well as documentation enabled a geographically distributed team take a paper concept to an operational prototype in approximately one year. One of the major tools used in the integration strategy was a coordinated effort to accurately model all the subsystems using computer aided design (CAD), so conflicts were identified before physical components came together. A deliberate effort was made following the deployment of the HDU PEM for field operations to collect lessons learned to facilitate process improvement and inform the design of future flight or analog versions of habitat systems. Significant items within those lessons learned were limitations with the CAD integration approach and the impact of shell design on flexibility of placing systems within the HDU shell.

Gill, Tracy↗

NASA NTRSDate not supplied

Gateway Program Safety and Mission Assurance Integration - the Future of Safe Deep Space Human Exploration

As a foundational element of the National Aeronautics and Space Administration (NASA) Artemis Campaign, the Gateway is an incrementally built cislunar spacecraft that will serve as a platform for deep space human exploration, science, and technology demonstration. The Gateway will be a unifying catalyst for international partners around the world to establish sustained deep space scientific investigations, lunar surface access, and missions to Mars. As human exploration moves farther away from Earth, spacecraft designs must prioritize and optimize mass and volume allocations, while minimizing human and spacecraft risk. To accomplish this objective, the Gateway Program Safety and Mission Assurance functions develop, implement, and ensure compliance with requirements, in concert with the accurate characterization and transparent communication of residual hazard risks, for integrated safety, reliability and maintainability and quality assurance. Safety and Mission Assurance was a key contributor during Gateway program pre-formulation and formulation activities where safety and reliability analysis was embedded in the Gateway Systems Engineering and Integration team. During these early program stages, a preliminary Gateway Integrated Hazard Analysis and Preliminary Gateway Probabilistic Risk Assessment assisted in Gateway architectural and operational definition as part of a risk-informed design process. As the deep space architecture has matured, the integrated Safety and Mission Assurance analyses have matured, new safety review processes have been developed, and requirements have been refined to ensure compliance with integrated safety and mission assurance objectives. The Gateway Program is currently concluding the preliminary design review informed milestone, where the primary objectives included: - Ensured completeness and consistency of the preliminary design, including the meeting of all requirements within appropriate margins and acceptable risk posture. - Identification of any major issues moving forward to the Critical Design phase. At this milestone, Safety and Mission Assurance provided numerous products, including Gateway Top Risks and Risk Mitigation Plans, updated integrated hazard analyses, updated probabilistic risk assessment, Crew Survival Analysis Report, and updated Safety and Mission Assurance Requirements and Plans. These products provide a many-faceted perspective on the inherent risk and available mitigations involved in flying the current proposed vehicle design and anticipated stack configurations. In addition, Safety and Mission Assurance identified top technical, process and workforce concerns to be addressed as the program progresses toward the critical design phase. This paper will detail the evolution of the Gateway Program Safety and Mission Assurance integration functions, provide its current status and lessons learned for future human spaceflight programs. Throughout this paper the key tenets of the Gateway Program Safety and Mission Assurance will be discussed: - Application of a risk-informed approach to identify and mitigate areas of highest risk. - Leverage of valuable processes and lessons learned from earlier spaceflight programs. - Development of Safety and Mission Assurance products to inform design risk trades. - Utilization of common Safety and Mission Assurance practices to identify safety risks for multiple perspectives: top-down, bottom-up, and across lines of integration. - Approval of safety hazards at the appropriate level of authority, keeping most deliberation closest to design expertise and elevating risks of greatest concern for program-level consideration. - Championing of Safety and Mission Assurance processes and forums to foster a pervasive safety culture that is transparent, inclusive, and collaborative between all partners. These tenets have allowed the Gateway Safety and Mission Assurance function to play a key role in optimized vehicle design evolution, and early identification and mitigation of Gateway program and Artemis mission risk.

Helen Vaccaro↗

NASA NTRS2002

Stellar Occultation Studies of Pluto, Triton, Charon, and Chiron

Bodies inhabiting the outer solar system are of interest because, due to the colder conditions, they exhibit unique physical processes. Also, some of the lessons learned from them can be applied to understanding what occurred in the outer solar system during its formation and early evolution. The thin atmospheres of Pluto and Triton have structure that is not yet understood, and they have been predicted to undergo cataclysmic seasonal changes. Charon may have an atmosphere - we don't know. Chiron exhibits cometary activity so far from the sun (much further than most comets), so that H2O sublimation cannot be the driving mechanism. Probing these bodies from Earth with a spatial resolution of a few kilometers can be accomplished only with the stellar occultation technique. In this program we find and predict stellar occultation events by small outer-solar system bodies and then attempt observations of the ones that can potentially answer interesting questions. We also develop new methods of data analysis for occultations and secure other observations that are necessary for interpretation of the occultation data.

Elliot, James L.↗