DI-SAFT-81300C

Mishap Risk Assessment Report (MRAR)

The Mishap Risk Assessment Report (MRAR) provides a comprehensive identification and evaluation of the mishap risks assumed during the processing and operation of a system throughout its life cycle.

Approval DateSeptember 11, 2025

AMSC NumberF10600

Preparing Activity40 (AFMC/SE)

Project NumberSAFT-2025-008

OPR—

DTIC ApplicableNo

GIDEP ApplicableNo

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantYes

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Supersedes

DI-SAFT-81300B

DI-SAFT-80101DI-SAFT-80102DI-SAFT-80103DI-SAFT-80104DI-SAFT-80105DI-SAFT-80106

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The Mishap Risk Assessment Report (MRAR) provides a comprehensive identification and evaluation of the mishap risks assumed during the processing and operation of a system(s) throughout its life cycle. It provides a means of confirming the compliance with program safety requirements. It summarizes all system safety analyses and testing performed on each system. The results of this assessment identify design and operation limits to be imposed upon system elements to preclude or minimize mishaps which could cause injury or damage.

It will be used for the life of the program as a baseline for safety decisions involving changes to the system, operational concepts and procedures.

a. This Data Item Description (DID) contains the content and format preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

b. This DID is applicable to all space, missile, and associated activities that include direct contractor support or management of system design, integration, test or operations.

c. This DID is related to DI-SAFT-80101, System Safety Hazard Analysis Report (SSHAR); DI-SAFT-80102, Safety Assessment Report (SAR); DI-SAFT-80103, Engineering Change Proposal System Safety Report (ECPSSR); DI-SAFT-80104, Waiver or Deviation System Safety Report (WDSSR); DI-SAFT-80105, System Safety Program Progress Report (SSPPR); and DI-SAFT-80106, Health Hazard Assessment Report (HHAR).

(Copies of these DIDs are available online at https://quicksearch.dla.mil.)

d. This DID supersedes DI-SAFT-81300B.

Preparation Instructions

1Reference documentsThe applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.

2FormatThe MRAR shall be in the contractor's format.

3ContentThe MRAR shall include the following information:

3.1General preparation instructions

3.1.1The level of detail for each submittal of the MRARThe level of detail for each submittal of the MRAR shall be commensurate with the level of design effort and safety analysis performed to date.

3.1.2Changes to the MRARChanges to the MRAR shall be identified by change bars or other means acceptable to the approving agency. Existing change bars shall be removed upon subsequent submittals and new change bars inserted, as necessary.

3.1.3All data pertaining to a particular subject matterAll data pertaining to a particular subject matter shall be consolidated or cross referenced.

3.1.4All pages of the MRARAll pages of the MRAR shall be numbered. Each page of each hazard report shall be labeled with the hazard report number.

3.1.5The MRAR shall be signedThe MRAR shall be signed by the contractor program manager and the contractor system safety engineer.

3.2Table of contents

3.3List of tables and figures

3.4List of system unique acronyms and definitions

3.5Introduction

3.5.1PurposeThis section is used to identify compliance documents being satisfied by the submittal of an MRAR; identify safety related compliance documents applicable to system design, test, processing, and operation; and certify that an evaluation of compliance with test documents has been made.

3.5.2ScopeThis section identifies the primary system, support systems, operational interfaces and facilities. It also identifies major similarities and differences with previous versions of the primary system.

3.6Safety certificationThis section shall state that management approval and submittal of the MRAR constitutes certification of the MRAR's completeness (commensurate with the program phase), accuracy and validity by a qualified system safety engineer. It states that the system complies with contractual safety requirements and can be safely operated within the parameters specified.

3.7Program safety status summaryThis is an executive summary of the program safety status. At final approval of the MRAR, this section shall reflect resolution of all previously identified safety concerns and noncompliance items, and summarize all risks deemed "acceptable" by the approving agency and the corresponding contractor position.

3.8Non-compliant itemsThis section shall include all waivers and deviations with a discussion of their disposition. Supporting documentation is not required in the MRAR if it is adequately summarized and referenced. Reference to technical agreements and understandings shall either identify the approved minutes of a meeting or include a copy of the approving correspondence.

3.9General system descriptionThis section includes:

3.9.1A brief description of the primary systemA brief description of the primary system in terms of its significant characteristics and the functions performed.

3.9.2Illustrations of the primary systemIllustrations of the primary system in all major configurations.

3.9.3A description of the primary system and support systemsA description of the primary system and support systems in terms of their hazardous subsystems.

3.10Ground operationsThis section includes:

3.10.1A brief description of the in-line and off-line sequencingA brief description of the in-line and off-line sequencing of ground processing tasks to include transport, receipt, assembly, test/checkout and ultimate usage.

3.10.2A condensed flow chart of the integrated ground flowA condensed flow chart of the integrated ground flow showing movement of systems/elements/components through government facilities.

3.11Flight operationsThis section includes:

3.11.1A brief description of the sequence of events for flight operationsA brief description of the sequence of events for flight operations with an emphasis on hazardous operations.

3.11.2Ascent, on-orbit, deployment through safe distance, retrieval, and landing or disposal operationsAscent, on-orbit, deployment through safe distance, retrieval, and landing or disposal operations, including abort for manned payload elements.

3.12Summary system descriptionA separate section shall be provided in the MRAR for the primary and its support systems (i.e., primary system, flight and ground support equipment and facilities). Within each of these sections, the following subsections shall be established as applicable:

3.12.1Structural/mechanical subsystems

3.12.2Ordnance subsystems

3.12.3Pressurized subsystems

3.12.4Propulsion and propellant subsystems

3.12.5Ionizing radiation producing subsystems

3.12.6Non-ionizing radiation - RF and command subsystems

3.12.7Non-ionizing radiation - optical and laser subsystems

3.12.8Electrical/electronic subsystems

3.12.9Software

3.13Subsystems design, operating characteristics and safety analysisThis section briefly describes each subsystem and summarizes the hazard analyses that were conducted for each subsystem. A lead-in paragraph for each subsystem lists all major elements. Information required for major elements include:

3.13.1A brief description of the element(s) and its function

3.13.2A sketch of the major element(s)A sketch of the major element(s) which shows its physical location in the system. A single sketch can be used to show all major elements.

3.13.3A mechanical and electrical schematic of the major element(s)A mechanical and electrical schematic of the major element(s) with its major components identified as appropriate.

3.13.4An electrical schematic of the control circuitryAn electrical schematic of the control circuitry for the major element(s)

3.13.5A flow chart or block diagram of the critical software componentsA flow chart or block diagram of the critical software components (CSCs) in the subsystem or element.

3.13.6How the major element(s) is controlled/powered and how it operatesHow the major element(s) is controlled/powered and how it operates, using the provided schematics.

3.13.7A description of the safety critical design and operation parametersA description of the safety critical design and operation parameters of the major element(s).

3.13.8When necessary to fully describe a major elementWhen necessary to fully describe a major element (for example, a helium pressure unit), its major components (for example, regulators, valves, etc.) shall be identified and described, including their safety critical design and operating parameters.

3.13.9A summary of the hazard analyses for the major elementsA summary of the hazard analyses for the major elements. Use sketches and schematics showing hazardous operations and/or interfaces to support the analyses.

3.13.10A description of the sequence of major tasksA description of the sequence of major tasks involving each major element, subsequent to arrival on government property. These tasks shall be traceable to the flow chart required in the procedures paragraph.

3.14Hazardous materialsThis section shall contain a listing of all materials used in primary systems, support systems, and facilities, which in themselves or in how they are used, are hazardous. An assessment shall be made of their safe usage with regard to flammability, odor, out-gassing, toxicity, asphyxiant properties, static electricity bleed capability, propellant compatibility, quantities, controls, etc. Test results and supporting analyses shall be referenced and available upon request.

3.14.1Personnel protective equipmentThis section shall include the identification of all tasks requiring personnel protective equipment, and the identification of that equipment by manufacturer/supplier and performance characteristics. Include test data supporting performance characteristics if not verifiable by the approving agency.

3.14.2Hazard report sheetsThis section shall include hazard report sheets as an integral part of the MRAR that are generated for hazardous events identified in the analyses. Related hazard report sheets shall be cross referenced. Supporting data shall be included with the hazard report sheet or summarized and cross referenced to information in 3.10.1. Contractor format acceptable for the supporting data. Each hazard report sheet shall include:

3.14.2.1Information on how the hazardous condition can propagate into an accident

3.14.2.2The potential effects

3.14.2.3Whether any established safety requirement has been violated

3.14.2.4Recommended corrective action initiated or to be initiated

3.14.2.5Illustrations with critical paths or pertinent areas identified

3.14.2.6Status of actions taken

3.15ProceduresThis section shall contain the title and numerical designations of all planned and contingency/emergency ground and flight operations procedures. Each procedure is listed with a summary of major tasks sufficient to assess hazard potential. Include a flow chart which shows the integration of the major tasks. Hazardous procedures and tasks are identified.

3.16Failure/mishap recordThis section shall contain a record of all safety related failures or mishaps related to program hardware or software acceptance, installation, test and checkout. This section also includes an assessment of the impact on flight and ground safety, and those action(s) taken to prevent recurrence of the failure/mishap.

3.17ReferencesThis section includes a list of all pertinent references, such as test reports, meeting minutes, agreements, etc.

References

Copies of these DIDs are available online https://quicksearch.dla.mil

Schema v3.0Community-maintained · Verify against ASSIST

Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer