SEARCH · Search NASA

Results for “launch software”

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 505 records · Page 28

All sources NASA NTRS DOE OSTI

NASA NTRS1984

Space Shuttle development update

The development efforts, since the STS-4 flight, in the Space Shuttle (SS) program are presented. The SS improvements introduced in the last two years include lower-weight loads, communication through the Tracking and Data Relay Satellite, expanded extravehicular activity capability, a maneuvering backpack and the manipulator foot restraint, the improvements in thermal projection system, the 'optional terminal area management targeting' guidance software, a rendezvous system with radar and star tracker sensors, and improved on-orbit living conditions. The flight demonstrations include advanced launch techniques (e.g., night launch and direct insertion to orbit); the on-orbit demonstrations; and added entry and launching capabilities. The entry aerodynamic analysis and entry flight control fine tuning are described. Reusability, improved ascent performance, intact abort and landing flexibility, rollout control, and 'smart speedbrakes' are among the many improvements planned for the future.

Brand, V.↗

NASA NTRS1989

Space Station Freedom Safety Program

The renewed emphasis within NASA on the incorporation of firmly established safety design requirements and evolving new safety analysis techniques, including quantitative safety risk assessment methods, is discussed with particular reference to the Space Station Freedom Safety Program. The program provides for integration of the partial safety analysis performed by numerous NASA Centers and International Partners into a Programmatic Safety Assessment for each of the launch increments and the complete Space Station Freedom on orbit. Communication in the safety program will utilize state-of-the-art software and computers, which will provide broad accessibility to safety information among the NASA and International Partners.

Griggs, John G., III↗

NASA NTRS1998

In-Flight Calibration of the Energetic Gamma-Ray Experiment Telescope (EGRET) on the Compton Gamma-Ray Observatory

The Energetic Gamma-Ray Experiment Telescope (EGRET) on the Compton Gamma-Ray Observatory has been operating for over seven years since its launch in 1991 April. This span of time far exceeds the design lifetime of two years. As the instrument has aged, several changes have occurred due to spark chamber gas exchanges as well as some hardware degradation and failures, all of which have an influence on the instrument sensitivity. This paper describes post-launch measurements and analysis that are done to calibrate the instrument response functions. The updated instrument characteristics are incorporated into the analysis software.

Esposito, J. A.↗

NASA NTRS2010

Range Safety for an Autonomous Flight Safety System

The Range Safety Algorithm software encapsulates the various constructs and algorithms required to accomplish Time Space Position Information (TSPI) data management from multiple tracking sources, autonomous mission mode detection and management, and flight-termination mission rule evaluation. The software evaluates various user-configurable rule sets that govern the qualification of TSPI data sources, provides a prelaunch autonomous hold-launch function, performs the flight-monitoring-and-termination functions, and performs end-of-mission safing

Lanzi, Raymond J.↗

NASA NTRS2010

Autonomous Flight Safety System

The Autonomous Flight Safety System (AFSS) is an independent self-contained subsystem mounted onboard a launch vehicle. AFSS has been developed by and is owned by the US Government. Autonomously makes flight termination/destruct decisions using configurable software-based rules implemented on redundant flight processors using data from redundant GPS/IMU navigation sensors. AFSS implements rules determined by the appropriate Range Safety officials.

Simpson, James↗

NASA NTRS2006

Flight Operations Analysis Tool

Flight Operations Analysis Tool (FLOAT) is a computer program that partly automates the process of assessing the benefits of planning spacecraft missions to incorporate various combinations of launch vehicles and payloads. Designed primarily for use by an experienced systems engineer, FLOAT makes it possible to perform a preliminary analysis of trade-offs and costs of a proposed mission in days, whereas previously, such an analysis typically lasted months. FLOAT surveys a variety of prior missions by querying data from authoritative NASA sources pertaining to 20 to 30 mission and interface parameters that define space missions. FLOAT provides automated, flexible means for comparing the parameters to determine compatibility or the lack thereof among payloads, spacecraft, and launch vehicles, and for displaying the results of such comparisons. Sparseness, typical of the data available for analysis, does not confound this software. FLOAT effects an iterative process that identifies modifications of parameters that could render compatible an otherwise incompatible mission set.

Easter, Robert↗

NASA NTRS2013

Orion GN and C Mitigation Efforts for Van Allen Radiation

The Orion Crew Module (CM) is NASA's next generation manned space vehicle, scheduled to return humans to lunar orbit in the coming decade. The Orion avionics and GN&C architectures have progressed through a number of project phases and are nearing completion of a major milestone. The first unmanned test mission, dubbed "Exploration Flight Test One" (EFT-1) is scheduled to launch from NASA Kennedy Space Center late next year and provides the first integrated test of all the vehicle systems, avionics and software.

King, Ellis T.↗

NASA NTRS2015

Standardized Modular Power Interfaces for Future Space Explorations Missions

Earlier studies show that future human explorations missions are composed of multi-vehicle assemblies with interconnected electric power systems. Some vehicles are often intended to serve as flexible multi-purpose or multi-mission platforms. This drives the need for power architectures that can be reconfigured to support this level of flexibility. Power system developmental costs can be reduced, program wide, by utilizing a common set of modular building blocks. Further, there are mission operational and logistics cost benefits of using a common set of modular spares. These benefits are the goals of the Advanced Exploration Systems (AES) Modular Power System (AMPS) project. A common set of modular blocks requires a substantial level of standardization in terms of the Electrical, Data System, and Mechanical interfaces. The AMPS project is developing a set of proposed interface standards that will provide useful guidance for modular hardware developers but not needlessly constrain technology options, or limit future growth in capability. In 2015 the AMPS project focused on standardizing the interfaces between the elements of spacecraft power distribution and energy storage. The development of the modular power standard starts with establishing mission assumptions and ground rules to define design application space. The standards are defined in terms of AMPS objectives including Commonality, Reliability-Availability, Flexibility-Configurability and Supportability-Reusability. The proposed standards are aimed at assembly and sub-assembly level building blocks. AMPS plans to adopt existing standards for spacecraft command and data, software, network interfaces, and electrical power interfaces where applicable. Other standards including structural encapsulation, heat transfer, and fluid transfer, are governed by launch and spacecraft environments and bound by practical limitations of weight and volume. Developing these mechanical interface standards is more difficult but an essential part of defining physical building blocks of modular power. This presentation describes the AMPS projects progress towards standardized modular power interfaces.

Spacecraft Power↗

NASA NTRS2015

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASA's Space Launch System

The engineering development of the new Space Launch System (SLS) launch vehicle requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The characteristics of these spacecraft systems must be matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large and complex system engineering challenge, which is being addressed in part by focusing on the specific subsystems involved in the handling of off-nominal mission and fault tolerance with response management. Using traditional model based system and software engineering design principles from the Unified Modeling Language (UML) and Systems Modeling Language (SysML), the Mission and Fault Management (M&FM) algorithms for the vehicle are crafted and vetted in specialized Integrated Development Teams (IDTs) composed of multiple development disciplines such as Systems Engineering (SE), Flight Software (FSW), Safety and Mission Assurance (S&MA) and the major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GNC), Thrust Vector Control (TVC), and liquid engines. These model based algorithms and their development lifecycle from inception through Flight Software certification are an important focus of this development effort to further insure reliable detection and response to off-nominal vehicle states during all phases of vehicle operation from pre-launch through end of flight. NASA formed a dedicated M&FM team for addressing fault management early in the development lifecycle for the SLS initiative. As part of the development of the M&FM capabilities, this team has developed a dedicated testbed that integrates specific M&FM algorithms, specialized nominal and off-nominal test cases, and vendor-supplied physics-based launch vehicle subsystem models. Additionally, the team has developed processes for implementing and validating these algorithms for concept validation and risk reduction for the SLS program. The flexibility of the Vehicle Management End-to-end Testbed (VMET) enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the developed algorithms utilizing actual subsystem models such as MPS. The intent of VMET is to validate the M&FM algorithms and substantiate them with performance baselines for each of the target vehicle subsystems in an independent platform exterior to the flight software development infrastructure and its related testing entities. In any software development process there is inherent risk in the interpretation and implementation of concepts into software through requirements and test cases into flight software compounded with potential human errors throughout the development lifecycle. Risk reduction is addressed by the M&FM analysis group working with other organizations such as S&MA, Structures and Environments, GNC, Orion, the Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission and Loss of Crew probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and associated detection and responses that can be tested in VMET to ensure that failures can be detected, and confirm that responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - ARINC 653 partitioned OS, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM such as telemetry packing and processing. The baseline plan for use of VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by Flight Software. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure the effectiveness of M&FM algorithms performance in the FSW development and test processes.

Trevino, Luis↗

NASA NTRS2005

Vehicle Integrated Performance Analysis, the VIPA Experience: Reconnecting with Technical Integration

Today's NASA is facing significant challenges and changes. The Exploration initiative indicates a large increase in projects with limited increase in budget. The Columbia report has criticized NASA for its lack of insight and technical integration impacting its ability to provide safety. The Aldridge report is advocating NASA find new ways of doing business. Very early in the Space Launch Initiative (SLI) program a small team of engineers at MSFC were asked to propose a process for performing a system level assessment of a launch vehicle. The request was aimed primarily at providing insight and making NASA a "smart buyer." Out of this effort the VIPA team was created. The difference between the VIPA effort and many integration attempts is that VIPA focuses on using experienced people from various disciplines and a process which focuses them on a technically integrated assessment. Most previous attempts have focused on developing an all encompassing software tool. In addition, VIPA anchored its process formulation in the experience of its members and in early developmental Space Shuttle experience. The primary reference for this is NASA-TP-2001-210092, "Launch Vehicle Design Process: Characterization, Technical Integration, and Lessons Learned," and discussions with its authors. The foundations of VIPA's process are described. The VIPA team also recognized the need to drive detailed analysis earlier in the design process. Analyses and techniques typically done in later design phases, are brought forward using improved computing technology. The intent is to allow the identification of significant sensitivities, trades, and design issues much earlier in the program. This process is driven by the T-model for Technical Integration described in the aforementioned reference. VIPA's approach to performing system level technical integration is discussed in detail. Proposed definitions are offered to clarify this discussion and the general systems integration dialog. VIPA's capabilities and process can now be used to significantly enhance the development and monitoring of realizable project requirements. This is done through the use of VIPA's V-model. Starting with a given concept, VIPA's assessment validates the concept's stated performance, identifies significant issues either with the concept or the requirements, and then re-integrates these issues to determine impacts. This process is discussed along with a description of how it may be integrated into a program's insight and review process. The VIPA process has been employed successfully on several projects including SLI, Orbital Space Plane (OSP), and several heavy lift concepts for Exploration. It has also been proposed for use on the Jupiter Icy Moon (JIMO) spacecraft. The VIPA process has gained favor with both engineering and project organizations for being responsive and insightful. Selected results from these assessments will be presented.

McGhee, David S.↗

NASA NTRS1995

Weaves as an Interconnection Fabric for ASIM's and Nanosatellites

Many of the micromachines under consideration require computer support, indeed, one of the appeals of this technology is the ability to intermix mechanical, optical, analog, and digital devices on the same substrate. The amount of computer power is rarely an issue, the sticking point is the complexity of the software required to make effective use of these devices. Micromachines are the nano-technologist's equivalent of 'golden screws'. In other words, they will be piece parts in larger assemblages. For example, a nano-satellite may be composed of stacked silicon wafers where each wafer contains hundreds to thousands of micromachines, digital controllers, general purpose computers, memories, and high-speed bus interconnects. Comparatively few of these devices will be custom designed, most will be stock parts selected from libraries and catalogs. The novelty will lie in the interconnections. For example, a digital accelerometer may be a component part in an adaptive suspension, a monitoring element embedded in the wrapper of a package, or a portion of the smart skin of a launch vehicle. In each case, this device must inter-operate with other devices and probes for the purposes of command, control, and communication. We propose a software technology called 'weaves' that will permit large collections of micromachines and their attendant computers to freely intercommunicate while preserving modularity, transparency, and flexibility. Weaves are composed of networks of communicating software components. The network, and the components comprising it, may be changed even while the software, and the devices it controls, are executing. This unusual degree of software plasticity permits micromachines to dynamically adapt the software to changing conditions and allows system engineers to rapidly and inexpensively develop special purpose software by assembling stock software components in custom configurations.

Gorlick, Michael M.↗

NASA NTRS2015

Orion Launch Abort System Performance on Exploration Flight Test 1

This paper will present an overview of the flight test objectives and performance of the Orion Launch Abort System during Exploration Flight Test-1. Exploration Flight Test-1, the first flight test of the Orion spacecraft, was managed and led by the Orion prime contractor, Lockheed Martin, and launched atop a United Launch Alliance Delta IV Heavy rocket. This flight test was a two-orbit, high-apogee, high-energy entry, low-inclination test mission used to validate and test systems critical to crew safety. This test included the first flight test of the Launch Abort System preforming Orion nominal flight mission critical objectives. NASA is currently designing and testing the Orion Multi-Purpose Crew Vehicle (MPCV). Orion will serve as NASA's new exploration vehicle to carry astronauts to deep space destinations and safely return them to earth. The Orion spacecraft is composed of four main elements: the Launch Abort System, the Crew Module, the Service Module, and the Spacecraft Adapter (Fig. 1). The Launch Abort System (LAS) provides two functions; during nominal launches, the LAS provides protection for the Crew Module from atmospheric loads and heating during first stage flight and during emergencies provides a reliable abort capability for aborts that occur within the atmosphere. The Orion Launch Abort System (LAS) consists of an Abort Motor to provide the abort separation from the Launch Vehicle, an Attitude Control Motor to provide attitude and rate control, and a Jettison Motor for crew module to LAS separation (Fig. 2). The jettison motor is used during a nominal launch to separate the LAS from the Launch Vehicle (LV) early in the flight of the second stage when it is no longer needed for aborts and at the end of an LAS abort sequence to enable deployment of the crew module's Landing Recovery System. The LAS also provides a Boost Protective Cover fairing that shields the crew module from debris and the aero-thermal environment during ascent. Although the Orion Program has tested a number of the critical systems of the Orion spacecraft on the ground, the launch environment cannot be replicated completely on Earth. A number of flight tests have been conducted and are planned to demonstrate the performance and enable certification of the Orion Spacecraft. Exploration Flight Test 1, the first flight test of the Orion spacecraft, was successfully flown on December 5, 2014 from Cape Canaveral Air Force Station's Space Launch Complex 37. Orion's first flight was a two-orbit, high-apogee, high-energy entry, low-inclination test mission used to validate and test systems critical to crew safety, such as heat shield performance, separation events, avionics and software performance, attitude control and guidance, parachute deployment and recovery operations. One of the key separation events tested during this flight was the nominal jettison of the LAS. Data from this flight will be used to verify the function of the jettison motor to separate the Launch Abort System from the crew module so it can continue on with the mission. The LAS nominal jettison event on Exploration Flight Test 1 occurred at six minutes and twenty seconds after liftoff (See Fig. 3). The abort motor and attitude control motors were inert for Exploration Flight Test 1, since the mission did not require abort capabilities. A suite of developmental flight instrumentation was included on the flight test to provide data on spacecraft subsystems and separation events. This paper will focus on the flight test objectives and performance of the LAS during ascent and nominal jettison. Selected LAS subsystem flight test data will be presented and discussed in the paper. Exploration Flight Test -1 will provide critical data that will enable engineering to improve Orion's design and reduce risk for the astronauts it will protect as NASA continues to move forward on its human journey to Mars. The lessons learned from Exploration Flight Test 1 and the other Flight Test Vehicles will certainly contribute to the vehicle architecture of a human-rated space launch vehicle.

McCauley, R.↗

NASA NTRS2013

Integration of Mirror Design with Suspension System using NASA's New Mirror Modeling Software

Advances in mirror fabrication is making very large space based telescopes possible. In the many applications, only monolithic mirrors meet the performance requirements. The existing and near-term planned heavy launch vehicles place a premium on lowest possible mass. Again, available and planned payload shroud size limits near term designs to 4 meter class mirror. Practical 8 meter and beyond designs could encourage planners to include larger shrouds if it can be proven that such mirrors can be manufactured. These two factors lower mass and larger mirrors, presents the classic optimization problem. There is a practical upper limit to how large a mirror can be supported by a purely kinematic mount system and be launched. This paper shows how the design of the suspension system and mirror blank needs to be designed simultaneously. We will also explore the concepts of auxiliary support systems, which act only during launch and disengage on orbit. We will define required characteristics of these systems and show how they can substantially reduce the mirror mass. The AMTD project is developing and maturing the processes for future replacements for HUBBLE, creating the design tools, validating the methods and techniques necessary to manufacture, test and launch extremely large optical missions. This paper will use the AMTD 4 meter "design point" as an illustration of the typical use of the modeler in generating the multiple models of mirror and suspension systems used during the conceptual design phase of most projects. The influence of Hexapod geometry, mirror depth, cell size and construction techniques (Exelsis Deep Core Low Temperature Fusion (c) versus Corning Frit Bonded (c) versus Schott Pocket Milled Zerodur (c) in this particular study) are being evaluated. Due to space and time consideration we will only be able to present snippets of the study in this paper. The advances in manufacturing techniques for lightweight mirrors, such as EXELSIS deep core low temperature fusion, Corning's continued improvements in the Frit bonding process and the ability to cast large complex designs, combined with water-jet and conventional diamond.

Arnold, William↗

NASA NTRS2013

Integration of Mirror Design with Suspension System Using NASA's New Mirror Modeling Software

Advances in mirror fabrication are making very large space based telescopes possible. In many applications, only monolithic mirrors can meet the performance requirements. The existing and near-term planned heavy launch vehicles place a premium on lowest possible mass, and then available payload shroud sizes limit near term designs to 4 meter class mirrors. Practical 8 meter class and beyond designs could encourage planners to include larger shrouds, if it can be proven that such mirrors can be manufactured. These two factors, lower mass and larger mirrors, present the classic optimization problem. There is a practical upper limit to how large of a mirror can be supported by a purely kinematic mount system handling both operational and launch loads. This paper shows how the suspension system and mirror blank need to be designed simultaneously. We will also explore the concepts of auxiliary support systems which act only during launch and disengage on orbit. We will define required characteristics of these systems and show how they can substantially reduce the mirror mass.

Arnold, William R., Sr.↗

NASA NTRS2013

Integration of Mirror Design with Suspension System using NASA's New Mirror Modeling Software

Arnold,William R., Sr.↗

NASA NTRS2011

First Stage Solid Propellant Multiply Debris Thermal Analysis

Destruction of a solid rocket stage of a launch vehicle can create a thermal radiation hazard for an aborting crew module. This hazard was assessed for the Constellation Program (Cx) crew and launch vehicle concept. For this concept, if an abort was initiated in first stage flight, the Crew Module (CM) will separate and be pulled away from the malfunctioning launch vehicle via a Launch Abort System (LAS). Having aborted the mission, the launch vehicle will likely be destroyed via a Flight Termination System (FTS) in order to prevent it from errantly traversing back over land and posing a risk to the public. The resulting launch vehicle debris field, composed primarily of first stage solid propellant, poses a threat to the CM. The harsh radiative thermal environment, caused by surrounding burning propellant debris, may lead to CM parachute failure. A methodology, detailed herein, has been developed to address this concern and to quantify the risk of first stage propellant debris leading to the thermal demise of the CM parachutes. Utilizing basic thermal radiation principles, a software program was developed to calculate parachute temperature as a function of time for a given abort trajectory and debris piece trajectory set. Two test cases, considered worst case aborts with regard to launch vehicle debris environments, were analyzed using the simulation: an abort declared at Mach 1 and an abort declared at maximum dynamic pressure (Max Q). For both cases, the resulting temperature profiles indicated that thermal limits for the parachutes were not exceeded. However, short duration close encounters by single debris pieces did have a significant effect on parachute temperature. Therefore while these two test cases did not indicate exceedance of thermal limits, in order to quantify the risk of parachute failure due to radiative effects from the abort environment, a more thorough probability-based analysis using the methodology demonstrated herein must be performed.

Toleman, Benjamin M.↗

NASA NTRS2010

Lessons Learned on Implementing Fault Detection, Isolation, and Recovery (FDIR) in a Ground Launch Environment

This paper's main purpose is to detail issues and lessons learned regarding designing, integrating, and implementing Fault Detection Isolation and Recovery (FDIR) for Constellation Exploration Program (CxP) Ground Operations at Kennedy Space Center (KSC). Part of the0 overall implementation of National Aeronautics and Space Administration's (NASA's) CxP, FDIR is being implemented in three main components of the program (Ares, Orion, and Ground Operations/Processing). While not initially part of the design baseline for the CxP Ground Operations, NASA felt that FDIR is important enough to develop, that NASA's Exploration Systems Mission Directorate's (ESMD's) Exploration Technology Development Program (ETDP) initiated a task for it under their Integrated System Health Management (ISHM) research area. This task, referred to as the FDIIR project, is a multi-year multi-center effort. The primary purpose of the FDIR project is to develop a prototype and pathway upon which Fault Detection and Isolation (FDI) may be transitioned into the Ground Operations baseline. Currently, Qualtech Systems Inc (QSI) Commercial Off The Shelf (COTS) software products Testability Engineering and Maintenance System (TEAMS) Designer and TEAMS RDS/RT are being utilized in the implementation of FDI within the FDIR project. The TEAMS Designer COTS software product is being utilized to model the system with Functional Fault Models (FFMs). A limited set of systems in Ground Operations are being modeled by the FDIR project, and the entire Ares Launch Vehicle is being modeled under the Functional Fault Analysis (FFA) project at Marshall Space Flight Center (MSFC). Integration of the Ares FFMs and the Ground Processing FFMs is being done under the FDIR project also utilizing the TEAMS Designer COTS software product. One of the most significant challenges related to integration is to ensure that FFMs developed by different organizations can be integrated easily and without errors. Software Interface Control Documents (ICDs) for the FFMs and their usage will be addressed as the solution to this issue. In particular, the advantages and disadvantages of these ICDs across physically separate development groups will be delineated.

Ferrell, Bob A.↗

NASA NTRS2011

First Stage Solid Propellant Multi Debris Thermal Analysis

The crew launch vehicle considered for the Constellation (Cx) Program utilizes a first stage solid rocket motor. If an abort is initiated in first stage flight the Crew Module (CM) will separate and be pulled away from the launch vehicle via a Launch Abort System (LAS) in order to safely and quickly carry the crew away from the malfunction launch vehicle. Having aborted the mission, the launch vehicle will likely be destroyed via a Flight Termination System (FTS) in order to prevent it from errantly traversing back over land and posing a risk to the public. The resulting launch vehicle debris field, composed primarily of first stage solid propellant, poses a threat to the CM. The harsh radiative thermal environment induced by surrounding burning propellant debris may lead to CM parachute failure. A methodology, detailed herein, has been developed to address this concern and quantify the risk of first stage propellant debris leading to radiative thermal demise of the CM parachutes. Utilizing basic thermal radiation principles, a software program was developed to calculate parachute temperature as a function of time for a given abort trajectory and debris piece trajectory set. Two test cases, considered worst-case aborts with regard to launch vehicle debris environments, were analyzed using the simulation: an abort declared at Mach 1 and an abort declared at maximum dynamic pressure (Max Q). For both cases, the resulting temperature profiles indicated that thermal limits for the parachutes were not exceeded. However, short duration close encounters by single debris pieces did have a significant effect on parachute temperature, with magnitudes on the order of 10 s of degrees Fahrenheit. Therefore while these two test cases did not indicate exceedance of thermal limits, in order to quantify the risk of parachute failure due to radiative effects from the abort environment, a more thorough probability-based analysis using the methodology demonstrated herein must be performed.

Toleman, Benjamin M.↗