ATTACHMENT_E-_nasa-std-8719.24_annex.pdf

NASA TECHNICAL

STANDARD

ANNEX Revision A to

NASA-STD 8719.24

National Aeronautics and Space Administration Washington, DC 20546

Approved: 2015-09-30 Superseding: NASA-STD-8719.24 Annex with Change 2

ANNEX TO NASA-STD 8719.24

NASA EXPENDABLE LAUNCH VEHICLE

PAYLOAD SAFETY REQUIREMENTS:

REQUIREMENTS TABLE

Measurement System Identification:

Metric (English)

Annex Rev. A to NASA-STD-8719.24

DOCUMENT HISTORY LOG

Status Document Revision Approval Date Description

Baseline 2011-08-26 Initial Release

(JWL4)

Change 1 2012-01-26

- Page 3: Corrected PSWG Chair signature block;

- Pages 187 Vol 3, para13.1.1.1 and Vol 7, removed revision from ST/SG/AC.10.1;

- Vol 7 page 404, bolded “hazardous materials” definition header

(JWL4)

Change 2 2012-06-19 Throughout document: Corrected 18 typographical errors (Administrative Change)

(JWL4)

Revision A 2015-09-30

Added Attachment 5 to Volume 1 on Payload Safety Introduction Briefing (PSIB) and related information that is to be presented at the PSIB.

Added NASA electric forms NF 1825, NASA ELV Payload Safety Hazard Report Form; NF 1826, NASA ELV Payload Safety Post-Tailoring Equivalent Level of Safety Request; and NF 1827, NASA ELV Payload Safety Waiver Request.

Added requirements addressing pyrovalves (Vol. 3, Section12.1.2.6) and payload recovery missions involving sample or payload returns. Added some additional requirements for Composite Overwrapped Pressure Vessels (COPVs) and a COPV Mechanical Damage Control Plan (Vol. 3, Section 12.2.5). Revised definition for “catastrophic.” Numerous improvements to requirements to improved clarity and correctness.

(SH)

TAILORED REQUIREMENTS FOR PROJECT Name

From: NASA-STD-8719.24 Annex Rev. A

Logo

PROJECT NAME

XXX

XX Month 201X Revision: X

PROJECT NAME SAFETY REQUIREMENTS

Prepared for: NASA Center Under contract: Contract Number

Prepared by:

Company’s Name Company’s Address Company’s Phone Number

Prepared by (Name) Name

Preparer Title Project Manager

Organization NASA Center

Date: _________________ Date: ________________

Name Name

Project SMA Technical Authority Launch Services Program SMA Technical Authority

NASA Center NASA Center

Date: _________________ Date: _________________

Name Name

Range Safety Authority Payload Safety Working Group Chairperson

Organization NASA Center

Date: _________________ Date: _________________

From: NASA-STD-8719.24 Annex Rev. A

FOREWORD

The Original Text column of the following requirements matrix contains the NASA Expendable Launch Vehicle (ELV) payload safety requirements that are to be tailored for each NASA ELV payload project, as required by NPR 8715.7, “Expendable Launch Vehicle Payload Safety Program.” The NASA ELV payload safety requirements are the result of a joint effort by NASA and U.S. Air Force Range Safety representatives (30th and 45th Space Wings) to establish an approved baseline from AFSPCMAN 91-710, “Range Safety User Requirements,” and applicable NASA safety requirements and also address unique issues associated with NASA payload safety design and operations. The NASA ELV payload safety requirements apply to all NASA ELV payload projects launched from an Air Force, NASA, or other range/launch site.

The NASA ELV payload safety requirements supplement NPR 8715.7 and satisfy AFSPCMAN 91-710 when applied to NASA ELV launches from Air Force launch ranges. As such, they provide a streamlined starting point for the safety requirements tailoring process that is required for each NASA ELV payload project per NPR 8715.7.

The NASA ELV payload safety requirements (as tailored for each specific project) are mandatory for each NASA ELV payload project and are to be applied to associated contracts and/or agreements. Additional requirements may be imposed by other organizations, including other launch ranges, commercial payload processing facility operators, or launch vehicle contractors. This document does not alter or otherwise modify the authority or roles and responsibilities delineated by statute or policy applicable to the Air Force, NASA, or other organizations participating in a NASA ELV payload project. As outlined in ASPCMAN 91-710, the Space Wing Commanders have overall launch authority and responsibility for public safety at Air Force ranges. The Director, NASA Wallops Flight Facility has similar authority and responsibility for launches originating from Wallops Flight Facility.

AFSPCMAN 91-710 requirements not applicable to NASA ELV payloads were eliminated from the following NASA ELV payload safety requirements tailoring matrix. This results in irregular numbering of paragraphs where certain paragraph(s) may appear to be skipped or missing because they were not applicable.

Additionally, in some cases entire inapplicable volumes or chapters may be missing and are not included in the tailoring matrix. The absence of these requirements does not alter the Air Force Range Safety authority. The project may add back any AFSPCMAN 91-710 requirements that are pertinent to their project upon agreement by the project’s Payload Safety Working Group (PSWG) and Range Safety representatives. Questions pertaining to the requirements in this document and applicable local safety requirements should be brought to the attention of the payload project’s PSWG. Per NPR 8715.7, Payload Project Offices will contact the NASA ELV Payload Safety Manager as early as practical in the project’s Concept and Technology Development, Phase A, to establish the project’s PSWG and initiate the payload safety review and approval process, which includes the requirements tailoring process.

The NASA ELV Payload Safety Manager is responsible for maintaining and keeping the NASA ELV payload safety requirements current and coordinating all changes with the NASA ELV Payload Safety Agency Team and the Air Force Range Safety 30th and 45th Space Wing Safety Offices. The NASA ELV Payload Safety Manager contact information and the NASA ELV payload safety requirements tailoring matrix are available on the NASA ELV Payload Safety Program website at: http://kscsma.ksc.nasa.gov/ELVPayloadSafety/Default.html.

Note: This Foreword provides background information that is applicable to all NASA ELV payload projects.

It is not to be tailored and shall remain as part of each final project-specific safety requirements document.

From: NASA-STD-8719.24

TABLE OF CONTENTS 1

VOLUME 1: POLICIES AND PROCEDURES

CHAPTER 1 INTRODUCTION

1.1 Objective

1.2 Applicability

1.3 Basis for the Requirements

CHAPTER 2 RESPONSIBILITIES AND AUTHORITIES

2.1 General

2.2 Headquarters Air Force Space Command Responsibilities

2.3 Space Wing Responsibilities

2.4 Federal Aviation Administration Responsibilities

2.5 Payload Project Responsibilities

CHAPTER 3 RANGE SAFETY POLICY

3.1 General

3.2 Prelaunch and Launch Operations:

3.3 Launch Area Safety

3.4 Launch Complex Safety

CHAPTER 4 PSWG and RANGE SAFETY PROCESSES

4.1 Range Safety and Payload Projects Interface Process

4.6 Equivalent Level of Safety (ELS) Determinations and Waivers

CHAPTER 5 SAFETY AUTHORIZATIONS, SAFETY APPROVALS, AND

DOCUMENTATION

5.1 General

CHAPTER 6 INVESTIGATING AND REPORTING MISHAPS AND I NCIDENTS

6.1 Mishaps and Incidents Involving Air Force Personnel and Resources

6.2 Non-Air Force Personnel and Resources on Air Force Property

6.3 Reporting Space Launch System Anomalies

CHAPTER 7 CHANGES TO THIS PUBLICATION

ATTACHMENT 1 THE NASA ELV PAYLOAD SAFETY REQUIREMENTS

TAILORING PROCESS

A1.1 Introduction:

A1.2 Tailoring Process

1 This document follows the paragraph numbering used in AFSPCMAN 91-710 for applicable payload requirements. AFSPCMAN 91-710 requirements that are not applicable to NASA ELV payloads were eliminated, which resulted in an irregular numbering of paragraphs. In some cases, entire inapplicable volumes or chapters were not included in this document.

From: NASA-STD-8719.24 Annex Rev. A

ATTACHMENT 2 SYSTEM SAFETY PROGRAM REQUIREMENTS

A2.1 Introduction

A2.2 System Safety Program Tasks

ATTACHMENT 3 SUBMITTING NONCOMPLIANCE REQUESTS

A3.1 Introduction

A3.2 Submitting Noncompliance Requests

ATTACHMENT 4 ACCEPTABLE RISK CRITERIA

A4.1 Introduction

ATTACHMENT 5 PAYLOAD SAFETY INTRODUCTION BRIEFING

A5.1 Introduction

A5.2 Payload safety introduction briefing (PSIB)

VOLUME 3: PAYLOADS AND GROUND SYSTEMS REQUIREMENTS

CHAPTER 1 INTRODUCTION

1.1 General

1.2 Organization of the Volume

CHAPTER 2 RESPONSIBILITIES AND AUTHORITIES

2.1 Payload Safety Working Group (PSWG)

2.2 Payload Project Responsibilities

CHAPTER 3 GENERAL DESIGN POLICY

3.1 General

3.2 Systems Without Specific Design Criteria

CHAPTER 4 DOCUMENTATION REQUIREMENTS

4.1 System Safety Plan Hazard Analyses

4.2 Safety Data Package (SDP) (MSPSP)

4.3 SDP Associated Test Plans and Test Results

4.4 Nondestructive Examination Plans

CHAPTER 6 MATERIAL HANDLING EQUIPMENT AND PERSONNEL WORK

PLATFORMS

6.1 Material Handling Equipment

6.3 Removable, Extendible, and/or Hinged Personnel Work Platforms

6.4 Lifting Personnel with a Crane

6.5 Flight Hardware Used to Lift Critical Loads and Clampbands

CHAPTER 7 ACOUSTIC HAZARDS

7.1 Acoustic Design Standards

7.2 Acoustic Data Requirements

CHAPTER 8 NON-IONIZING RADIATION SOURCES

8.1 Radio Frequency Emitters

From: NASA-STD-8719.24 Annex Rev. A

8.2 Laser Systems

CHAPTER 9 RADIOACTIVE (IONIZING) RADIATION SOURCES

9.1 Radioactive Source Design Standards and Controls

9.2 Radioactive Sources Carried on Payloads

CHAPTER 10 HAZARDOUS MATERIALS

10.1 Hazardous Materials Selection Criteria

10.2 Hazardous Materials Test Requirements

10.3 Hazardous Materials Environmental Requirements

10.4 Hazardous Materials Data Requirements

10.5 Process Safety Management and Risk Management Plan

CHAPTER 11 GROUND SUPPORT PRESSURE, VACUUM, AND HAZARDOUS

STORAGE SYSTEMS

11.1 Ground Support Pressure Vacuum and Storage Systems Requirements

11.2 Ground Support Pressure Systems Requirements

11.3 Ground Support Pressure Systems Certification and Recertification

CHAPTER 12 FLIGHT HARDWARE PRESSURE SYSTEMS AND PRESSURIZED

STRUCTURES

12.1 Flight Hardware Pressure System and Pressurized Structure General Requirements

12.2 Flight Hardware Pressure Vessel Design, Analysis, and Test Requirements

12.4 Flight Hardware Special Pressurized Equipment Design, Analysis, and Test Requirements

12.5 Flight Hardware Pressure System Component Design and Test Requirements

12.6 Flight Hardware Pneumatic System Design Requirements

12.7 Flight Hardware Hydraulic System Design and Test Requirements

12.8 Flight Hardware Hypergolic Propellant System Design and Test Requirements

12.9 Flight Hardware Cryogenic Systems Design and Test Requirements

12.10 Flight Hardware Pressure Systems Data Requirements

CHAPTER 13 ORDNANCE SYSTEMS

13.1 Ordnance Hazard Classification

13.2 Ordnance System General Requirements

13.3 Ordnance Electrical Circuits

13.4 Initiator Electrical Circuits

13.5 Ordnance Safety Devices

13.6 Ordnance Initiating Devices

13.7 Explosive Transfer Systems and Receptor Ordnance

13.8 Ordnance Test Equipment

13.9 Ordnance and Non-Explosive Initiator Data Requirements

CHAPTER 14 ELECTRICAL AND ELECTRONIC EQUIPMENT

14.1 Electrical and Electronic Ground Support Equipment and Flight Hardware General Design Requirements and Standards

14.2 EGSE Design Requirements

14.3 Electrical and Electronic Flight Hardware

From: NASA-STD-8719.24 Annex Rev. A

CHAPTER 15 MOTOR VEHICLES

15.1 General

15.2 Motor Vehicles Other Than Lift Trucks

15.3 Lift Trucks

CHAPTER 16 COMPUTER SYSTEMS AND SOFTWARE

16.1 General

16.2 Determination of Safety Critical Computer System Functions

16.3 Hardware and Software Safety Design Requirements

16.4 Software Requirements

16.5 Computer System and Software Data Requirements

CHAPTER 17 WESTERN RANGE SEISMIC DESIGN

17.1 Applicability of Design and/or Anchorage or Restraint Requirements

17.2 Basis for Design

17.3 WR Seismic Data Requirements

17.4 Earthquake Emergency Planning and Post Recovery Response

CHAPTER 18 SOLID ROCKET MOTORS, ROCKET MOTOR SEGMEN TS, AND

ROCKET MOTOR COMPONENTS

18.1 General

18.2 Failure Modes, Effects, and Criticality Analysis (FMECA) and Operational Hazards Analysis

(OHA)

18.3 Lightning Effects Hazard Analysis

18.4 Solid Rocket Motor and Motor Segment Data Requirements

ATTACHMENT 1 SAFETY DATA PACKAGE (MISSILE SYSTEM PRELAUNCH

SAFETY PACKAGE)

A1.1 Introduction

A1.2 Preparation Instructions

A1.4 Modifications to the Safety DATA PACKAGE (SDP)

ATTACHMENT 2 HANDLING STRUCTURES INITIAL AND PERIODIC TEST

REQUIREMENT FLOW PATH

ATTACHMENT 3 HAZARD AREA CLASSIFICATION

VOLUME 6: GROUND AND LAUNCH PERSONNEL, EQUIPMENT, SYSTEMS, AND

MATERIAL OPERATIONS SAFETY REQUIREMENTS

CHAPTER 1 INTRODUCTION

1.1 Applicability

1.2 Organization of the Volume

1.3 Compliance Documents

CHAPTER 2 RESPONSIBILITIES AND AUTHORITIES

2.1 Payload Safety Working Group

2.2 Payload Project Responsibilities

From: NASA-STD-8719.24 Annex Rev. A

CHAPTER 3 GROUND OPERATIONS POLICIES

3.1 Personnel Safety

3.2 Stopping Unsafe Operations

CHAPTER 4 DOCUMENTATION REQUIREMENTS

4.1 Ground Operations Plans

4.2 Test and Inspection Plans

4.3 Safety and Emergency Plans

4.4 Procedures

4.5 Range User Training Plan

4.6 Mishap Reporting

4.7 Safety For Return-to Earth Payloads or Sample Returns

CHAPTER 5 GROUND OPERATIONS SAFETY REQUIREMENTS

5.1 Ground Operations Personnel Requirements

5.2 Hazardous Ground Operations General Requirements

5.3 Personal Protective Equipment

5.4 Fall Protection

5.5 Smoking Areas

5.6 Operating Restrictions Due to Adverse Weather

5.7 Operating Restrictions Due to High Winds

5.8 Facility Use

5.9 Hazardous Operation Support Requirements

CHAPTER 6 MATERIAL HANDLING EQUIPMENT, CRANE AND HO IST,

PERSONNEL PLATFORM, POWERED INDUSTRIAL TRUCK,

AND ELEVATOR OPERATIONS

6.1 Material Handling Equipment Operations

6.2 Crane and Hoist Operations

6.3 Personnel Work Platform Operations

6.4 Powered Industrial Trucks

6.5 Elevator Usage

CHAPTER 7 ACOUSTIC HAZARD OPERATIONS

7.1 Acoustic Hazard Operating Standards

7.2 Acoustic Hazard Operations Personnel Protection Requirements

7.3 Acoustic Operations

CHAPTER 8 NON-IONIZING RADIATION OPERATIONS

8.1 Non-Ionizing Radiation Operating Standards

8.2 Radio Frequency Procedures

8.3 RF Operations

8.4 Optical/Laser Operations

CHAPTER 9 RADIOACTIVE (IONIZING) RADIATION SOURCES OPERATIONS

CHAPTER 10 HAZARDOUS MATERIALS OPERATIONS

10.1 Hazardous Materials Operating Standards

10.2 Hazardous Materials Operations Personal Protective Equipment (PPE)

From: NASA-STD-8719.24 Annex Rev. A

10.3 Hazardous Materials Procedures

10.4 Hazardous Materials Operations

10.5 Restrictions on the Use of Plastic Films, Foams, and Adhesive Tapes (PFAs) and other Static- Producing and Flammable Materials

10.6 Hazardous Commodity Lockers

10.7 Disposal of Contaminated Liquid Propellant, Gas, or Other Regulated Wastes

CHAPTER 11 GROUND SUPPORT AND FLIGHT HARDWARE PRESSURE SYSTEMS

OPERATIONS

11.1 Pressure Systems Operating Standards

11.2 Pressure Systems Personnel Requirements

11.3 Pressure Systems Procedures

11.4 Pressure Systems Test, Inspection, and Maintenance Requirements

11.5 Pressure Systems Operating Requirements

CHAPTER 12 RESERVED

CHAPTER 13 ORDNANCE OPERATIONS

13.1 Ordnance Operations Procedure Requirements

13.2 Ordnance Transportation, Receipt, and Storage

13.3 Ordnance Systems Grounding

13.4 Ordnance Operations

13.5 Explosive Ordnance Disposal

13.6 Ordnance Facilities Operations

CHAPTER 14 ELECTRICAL SYSTEMS OPERATIONS

14.1 Electrical Systems Operating Standards and Definitions

14.2 Electrical Systems Operations Personnel and Special Insulated Equipment

14.3 Electrical Systems Procedures

14.4 Electrical Equipment and Systems Test, Inspection, and Maintenance Requirements

14.5 Electrical Systems Operating Requirements

14.6 Battery Operations

CHAPTER 15 MOTOR VEHICLE OPERATIONS

15.1 Motor Vehicle Operating Standards

15.2 Motor Vehicle Operating Requirements

CHAPTER 16 CONVOY OPERATIONS

16.1 General

16.2 Convoy Operations Procedures

16.3 Convoy Operations Requirements

CHAPTER 17 LAUNCH OPERATIONS

CHAPTER 18 SOLID ROCKET MOTORS AND ROCKET, ROCKET M OTOR

SEGMENTS, AND ROCKET MOTOR OPERATIONS

18.1 Solid Rocket Motors And Rocket Motor Segments Operations General Requirements

18.2 Solid Rocket Motor and Rocket Motor Segment Transportation

18.3 Solid Rocket Motor and Rocket Motor Segment Inspections

From: NASA-STD-8719.24 Annex Rev. A

18.4 Solid Rocket Motor and Rocket Motor Segment Processing and Handling

ATTACHMENT 1 GROUND OPERATIONS PLANS

A1.1 Introduction

A1.2 Preparation Instructions

ATTACHMENT 2 HAZARDOUS AND SAFETY CRITICAL PROCEDURES

A2.1 Introduction

A2.2 Preparation Instructions

A2.3 Examples of Hazardous Procedures

A2.4 Changes

ATTACHMENT 3 INDEX OF OPERATIONS/AREAS SAFETY PLANS

ATTACHMENT 4 INDEX OF EXPLOSIVE (OPERATING AND AREA) SAFETY

PLANS

ATTACHMENT 5 MISCELLANEOUS SAFETY PLANS

ATTACHMENT 7 LAUNCH COMMIT CRITERIA

VOLUME 7: GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION ... 401

Volume 1: TAILORED REQUIREMENTS FOR PROJECT Name

I – Information/Title N/A – Not Applicable C – Compliant T – Tailored NC – Noncompliant

VOLUME 1: POLICIES AND PROCEDURES

ORIGINAL TEXT STATUS

TAILORED

TEXT

RATIONALE/

COMMENTS

CHAPTER 1 INTRODUCTION I

1.1 OBJECTIVE

The objective of this publication is to establish and enforce NASA ELV payload project requirements to ensure the safety of the public, launch area, payload processing facility, and launch complex personnel and resources and to ensure that all aspects of prelaunch and launch operations adhere to applicable public laws. These safety requirements safeguard people and resources (including flight hardware, ground support equipment (GSE) and facilities) from hazards associated with payloads that will fly on unmanned Expendable Launch Vehicles (ELVs) (i.e. ELV payloads), including hazards associated with payload related GSE. This document is a baseline and shall be tailored for each NASA payload project (mission). The contents of this publication are to be used in conjunction with NASA Procedural Requirements (NPR) 8715.7, Expendable Launch Vehicle Payload Safety Program by the payload project to develop and process their payloads safely throughout the project’s life cycle. The requirements of this document comply with the requirements of AFSPCMAN 91-710 and are acceptable to NASA and the Air Force ranges. The Payload Safety Working Group (PSWG) is the payload project’s primary interface for the safety review and approval process, where all documentation required by this publication and safety concerns or issues start. The PSWG members represent their respective organizations and are responsible for coordinating, as necessary, with their organization to ensure payload project compliance with their organization’s safety policies, processes, and requirements whenever the payload is being processed on their organizations property or in their jurisdiction. The PSWG shall include the NASA (or JPL) Payload Project System Safety Engineer, the payload contractor safety representative(s), the NASA Kennedy Space Center (KSC) Launch Services Division Safety Engineer (or equivalent) who typically chairs the PSWG, the launch vehicle contractor safety engineer, the launch site range safety engineer, the payload processing facility safety engineer, and other invitees such as the mission’s Launch Site Integration Manager (LSIM) and subject matter experts (see Volume 3, Paragraph 2.1) and payload or sample recovery organization safety representative as needed.

PSWG activities typically conclude with the signing of the Certificate of ELV Payload Safety Compliance. If there are any open action items, the payload project will provide the appropriate local safety authorities and mission officials with updates and complete the Safety Verification Tracking Log (SVTL). NPR 8715.7, this publication, and the PSWG safety review and approval process upholds and does not remove or alter the safety responsibility and authority of any organization having safety authority jurisdiction where the payload project is processed. The paragraph numbers of this document follow the same paragraph numbering of AFSPCMAN 91-710. The mutual goal of NASA, the payload project, and Range Safety shall be to conduct their missions safely, with a strong commitment to public safety.

Note: Range Safety is a member of the PSWG working as a PSWG member in the project’s safety review and approval process. All correspondence (safety submittals, review comments, etc.) is processed and coordinated through the PSWG.

The phrase “PSWG and Range Safety” is used throughout this document not to imply that Range Safety is separate from the PSWG but to emphasize Range Safety’s role, authority, and responsibility in public safety and launch site safety.

C

TEXT

RATIONALE/

COMMENTS

1.2 APPLICABILITY I

1.2.1. Payload Projects. The requirements, policies, processes, procedures, and approvals defined in this publication and NPR

8715.7 shall be applicable to all NASA ELV payload projects. The requirements in this document apply to each payload project and its design, fabrication, launch area testing, vehicle integration, launch processing, launch, ascent flight phase through payload separation, and planned recovery; payload-provided upper stages; interface hardware that is flown as part of a payload; and GSE (Ground Support Equipment) used to support payload-related operations. Post launch ascent flight phase through payload separation the requirements of this document apply only to the extent that a hazard could credibly result in a mishap causing a fatal injury or loss of the flight termination system. This document does not address in-flight spacecraft operational safety. This document applies to payload processing facilities and the launch site area and does not apply to payload integration, operations and testing performed at NASA Centers, JPL and other contractor facilities that take place prior to payload shipment to the launch site area. Center payload activities fall under NPR 8715.3 NASA General Safety Program Requirements and their local safety requirements. The mission success and any scientific objectives of the payload are the responsibility of the Payload Project Office and are beyond the scope of this document. When conflicting safety requirements are encountered, the most stringent shall be applied. When additional safety requirements are needed, NPR 8715.7, AFSPCMAN 91-710, and local safety requirements shall be applied as determined by the PSWG and Range Safety.

1.2.2. Tailoring: I

1.2.2.1. This document is a template for developing a specific payload project's safety requirements document. The tailored edition shall be placed on contract, other agreement, or effected through the applicable range Universal Documentation System.

Requirements were identified to address the safe design and operational concerns encountered in a 'typical' spacecraft. Every attempt was made to capture the intent of all original requirements from applicable baseline requirements (e.g., AFSPCMAN 91-710). The contents of this publication provide additional clarification, remove non-applicable requirements, and reflect current practices and procedures of Ranges, Launch Vehicle Contractors, Payload Processing Facility Contractors, etc. The PSWG and Range Safety reserves the right to identify applicable requirements not addressed, and any oversights, omissions, or inaccuracies during the tailoring process with the payload project office. See Attachment 1 of this volume, for further tailoring instructions. See NPR

8715.7 for the overall tailoring process.

I

1.2.2.2. Developing a tailored edition of this document. The tailored edition should look like this document with the following exceptions: C

1.2.2.2.1. The tailored edition shall be constructed in the following manner: C

1.2.2.2.1.1. Insert a document heading/title that reads, "NASA ELV Payload Safety Requirements" for Project Name, date of the applicable contract/agreement/ etc.", centered at the top of each page. C

1.2.2.2.1.2. Date of tailored edition. C

1.2.2.2.1.3. Insert "PROPRIETARY" at the top, centered directly over heading material, and at the bottom of each page (if requested by the payload project). C

TEXT

RATIONALE/

COMMENTS

1.2.2.2.2. Remaining heading information shall be left justified. C

1.2.3. New Programs. This publication and NPR 8715.7 are applicable to all NASA ELV payload projects under all new programs. C

1.2.4. Previous Approvals. All new NASA ELV payload projects must comply with the requirements in this document. However, similar previously approved projects, systems or operations and related noncompliances may be updated and submitted for consideration by the PSWG in assessing the safety of the new payload project. Existing projects and noncompliance approvals approved before the initial publication of this document shall be updated to reflect any changes since last approval and resubmitted to the PSWG for PSWG and Range Safety assessment.

1.3 BASIS FOR THE REQUIREMENTS

This publication is based on, but not limited to, the responsibilities or standards contained in or applied by NPR 8715.7 Preface and AFSPCMAN 91-710 Volume 1 Section1.3.

TEXT

RATIONALE/

COMMENTS

CHAPTER 2 RESPONSIBILITIES AND AUTHORITIES I

2.1 GENERAL

The roles, responsibilities, and authorities for ensuring safety for NASA ELV payload projects are provided in NPR 8715.7, AFSPCMAN 91-710, and below. For NASA ELV payload safety roles, responsibilities and safety review and approval processes, see NPR 8715.7. For Air Force Range Safety roles, responsibilities, and safety review and approval processes, see AFSPCMAN 91- 710.

2.2 HEADQUARTERS AIR FORCE SPACE COMMAND RESPONSIBILITI ES

The Headquarters Air Force Space Command (HQ AFSPC) operates the AFSPC ranges, including providing base support, personnel, and other government assets. The AFSPC Commander (AFSPC/CC) is responsible for establishing range safety policy for AFSPC ranges as outlined in AFSPCI91-701, Range Safety Program Policy and Requirements. HQ AFSPC is also responsible for establishing common range safety user requirements as outlined in this publication for the AFSPC space wings to implement and enforce.

2.3 SPACE WING RESPONSIBILITIES I

2.3.1. Commanders, 30th Space Wing and 45th Space Wing: I

2.3.1.1. The Space Wing Commanders (SW/CCs) have overall authority and responsibility for public safety at AFSPC ranges as directed by the AFSPC/CC. This delegation is provided via the MAJCOM chain of command and AFI 91-202, as supplemented. I

2.3.5. Range Safety Offices. Unless otherwise noted, the use of the term Range Safety in this publication refers to 30 SW/SE, 45 SW/SE, or other local range safety organization. I

2.3.5.1. Enforcing safety requirements to ensure that public safety, launch area safety, and launch complex safety are adequately provided by and for all programs using the ranges. I

2.3.5.3. Providing oversight, review, approval, and monitoring for all public safety and launch area safety concerns during prelaunch operations at the launch complex and launch vehicle or AF payload processing facilities. I

2.3.5.5. Reviewing and approving flight plans, design, inspection, procedures, testing, and documentation of all hazardous and safety critical launch vehicles, payloads, and ground support equipment, systems, subsystems, facilities, and material to be used at the ER and WR.

TEXT

RATIONALE/

COMMENTS

2.4 FEDERAL AVIATION ADMINISTRATION RESPONSIBILITIES

In accordance with 49 U.S.C., Subtitle IX, Commercial Space Transportation, Chapter 701, Commercial Space Launch Activities, U.S.C. §§ 70101 - 70121, the FAA has responsibility for public safety of licensed launches. The Range Safety requirements in this publication have been written with the intent of achieving commonality with the FAA requirements. The FAA performed launch site safety assessments of the two AFSPC national launch ranges and determined the level of safety obtained by the existing range safety process to be adequate. The FAA will not require a license applicant to demonstrate the adequacy of the range services it proposes to use if the applicable launch site safety assessment included those services and if those services remain adequate. SW Commander discretion to accept higher risk for the launch of government payloads does not apply to licensed launches without a Range User obtaining relief from the FAA. (“Memorandum of Agreement between the Department of the Air Force and Federal Aviation Administration on Safety for Space Transportation and Range Activities,” dated 16 January 2001). FAA documents can be found on the FAA/AST web site at http://www.faa.gov/about/office_org/headquarters_offices/ast/.

2.5 PAYLOAD PROJECT RESPONSIBILITIES

Projects are responsible for complying with NPR 8715.7 and the requirements identified in this publication.

2.5.2. System Safety Program. The payload Project Manager (PM) shall be responsible for payload project safety and for developing and maintaining a safety management program encompassing all applicable safety requirements, identifying a qualified key system safety person with authority for resolution of identified hazards and direct access to the PM, and establishing and funding a supporting system safety organization/function with direct interfaces and access to other functional elements of the project. Once assigned a project the PM shall notify the NASA ELV Payload Safety Manager of the new project as early as possible, obtain a Payload Project System Safety Engineer, help coordinate the establishment of the PSWG, and ensure compliance with their responsibilities and the safety review and approval process listed in NPR 8715.7. The payload project shall provide a System Safety Plan (SSP), detailing the safety program, for review and approval in accordance with Attachment 2 of this volume.

2.5.3. Design, Test, and Inspection Requirements. Payload projects shall be responsible for the design, inspection, and testing of all hazardous and safety critical payload, project provided ground support equipment, systems, subsystems, facilities, and materials to be used in accordance with the requirements of this publication and applicable local safety requirements. Payload project requests to eliminate or reduce testing shall be justified with clear and convincing evidence presented to Range Safety and the PSWG for approval. Payload project responsibilities include the following:

2.5.3.1. Providing safe systems, equipment, facilities, and materials in accordance with this publication. C

2.5.3.2. Developing and obtaining PSWG and Range Safety review and approval for all required data and/or documents necessary for their planned operations. The submittal, review, and approval of data are defined by this document and NPR 8715.7. C

2.5.3.5. Performing risk analyses and implementing design and mission plans consistent with acceptable risk to the general public for deorbiting spacecraft in accordance with NASA-STD-8719.14 Process for Limiting Orbital Debris. C

TEXT

RATIONALE/

COMMENTS

2.5.3.6. Coordinating their safety programs with the PSWG in conjunction with Range Safety and any additional safety authorities needed to ensure their activities meet national policy goals and provide for public, payload processing facility and launch site safety and resource protection while minimizing impact on mission requirements.

2.5.3.8. Verifying compliance with this publication. The use of subcontractors does not relieve the payload project of responsibility.

The payload project shall provide adequate contractual direction and monitor subcontractor performance to verify compliance. C

2.5.3.9. As applicable, when involved in joint projects, interfacing and integrating with other payload projects or associated contractors in their safety programs. C

2.5.4. Radioactive Material Launches. Payload projects shall be responsible for notifying the PSWG and Range Safety and ensuring compliance with PD/NSC 25 as outlined in DoD 3100.10, with implementation through AFI 91-110 and any Space Wing supplements and providing certification as detailed in AFSPCMAN 91-710, NPR 1800.1, Chapter 4, NPR 8715.3 Chapter 6, and local requirements.

2.5.5. Conduct of Operations. Payload projects shall be responsible for the conduct of operations as outlined below and in Volume 6 and its attachments: C

2.5.5.1. Conducting their operations in a safe manner. C

2.5.5.2. Planning and conducting hazardous and safety critical operations only in accordance with approved procedures and the current edition of the applicable operations safety plan (OSP). C

2.5.5.3. Observing, evaluating, and enforcing compliance with safety requirements. C

2.5.7. Occupational Safety and Health: I

2.5.7.1. Payload projects are fully responsible for the safety and health of their employees in accordance with OSHA regulations/standards, NPR 1800.1, NASA Occupational Health Program Procedures, NPR 8715.1, NASA Occupational Safety And Health Programs, and other federal and state safety and health regulations. Further, they have an inherent responsibility to protect any government employees and property when such are involved in contractor operations or on contractor-leased facilities. Air Force Range Safety shall assume no liability for payload project or contractor compliance or noncompliance with OSHA requirements.

2.5.8. Resource Safety. Payload projects are responsible for resource safety of their owned or leased facilities, equipment, and flight hardware. C

TEXT

RATIONALE/

COMMENTS

CHAPTER 3 RANGE SAFETY POLICY I

3.1 GENERAL I

3.1.1. Each project shall have a risk management plan consistent with AFSPC range launch risk guidance. The payload project shall demonstrate an acceptable level of mishap risk to the PSWG through the completion of the system safety hazard analyses and risk assessments described in Attachment 2.

3.2 PRELAUNCH AND LAUNCH OPERATIONS: I

3.2.1.1. Range Safety shall review, approve, and through Pad Safety, monitor, and impose safety holds, when necessary, on all prelaunch and launch operations conducted on the ranges. These actions are required to ensure that the hazards associated with propellants, ordnance, radioactive material, and other hazardous systems do not expose the public, launch area, or launch complex to risks greater than those considered acceptable by public law and state documents. These documents include but are not limited to PL 99-499 42 U.S.C. 11001-11050, Superfund Amendments and Reauthorization Act (SARA), Title III: Emergency Planning and Community Right-to-Know Act (CPRCA); 29 CFR 1910.119, Process Safety Management of Highly Hazardous Chemicals; 40 CFR 355, Emergency Planning and Notification; 40 CFR 68, Chemical Accident Prevention Provisions, subpart G, Risk Management Plan; Executive Order 12856, Federal Compliance with Right-to-Know Laws and Pollution Prevention Requirements;

and California Occupational Safety and Health Administration (CAL-OSHA).

3.2.1.2. Range Safety shall conduct and oversee launch vehicle, payload, mission flight control, and Range Safety launch support operations to ensure that risks to the public, launch area, and launch complex do not exceed acceptable limits consistent with mission and national needs.

3.3 LAUNCH AREA SAFETY

The following requirements are in addition to those specifically identified for launch area safety in 3.2.1 of this volume. (See Attachment 4 of this volume and Volume 7 of this publication for the definitions of terms related to risk.)

3.3.1. The ranges shall ensure that all personnel and USAF or third party resources located on any AFSPC range, including CCAFS or VAFB or on any supporting site within the ER or WR, are provided an acceptable degree of protection from the hazards associated with range operations.

3.3.2. Figure 3.2 shows nominal launch area and launch complex hazard consequence and probability categories correlated to different levels of acceptability for prelaunch hazards not associated with launch or Range Safety launch commit criteria. Numbers provided in Figure 3.2 are guides only and are not necessarily hard limits. NASA safety risks assessment often do not address specific monetary values or downtime. NASA safety risks focus more on credible scenarios that may result in loss of life, personal injury, illness, mission loss, or system loss or damage.

TEXT

RATIONALE/

COMMENTS

Figure 3.2: Acceptability Guidelines for Prelaunch Launch Area/Launch Complex Hazard Consequences and Probability Categories

TEXT

RATIONALE/

*Probability refers to the probability that the potential consequence will occur in the life cycle of the system (test/activity/operation).

Use the following list to determine the appropriate Risk Level.

DESCRIPTION**

THRESHOLD

LEVEL

PROBABILITY

VALUE

SPECIFIC INDIVIDUAL ITEM

FLEET OR INVENTORY***

A Frequent 3X10-1 Likely to occur repeatedly Continuously experienced ----------------------- 8X10-2 -----------------------------------------------------------------------------------------------------------------------------

B Reasonably probable

3X10-2 Likely to occur several times Will occur frequently

----------------------- 8X10-3 ----------------------------------------------------------------------------------------------------------------------------- C Occasional 3X10-3 Likely to occur sometime Will occur several times

----------------------- 8X10-4 ----------------------------------------------------------------------------------------------------------------------------- D Remote 3X10-4 Unlikely to occur, but possible Unlikely, but can reasonably be expected to occur

----------------------- 8X10-5 ----------------------------------------------------------------------------------------------------------------------------- E Extremely

Improbable 3X10-5 The probability of occurrence cannot be distinguished from zero.

Unlikely to occur, but possible

** Definitions of descriptive words may have to be modified based on quantity involved.

*** The size of the fleet or inventory and system life cycle should be defined.

Figure 3.2 (Continued): Acceptability Guidelines for Prelaunch Launch Area/Launch Complex Hazard Consequences and Probability Categories

3.3.7. Range Safety shall evaluate all launch vehicle, payload, ground support, and facility systems used on the ranges to test, checkout, assemble, handle, support, or launch space launch vehicles or payloads with regard to their hazard potential and ensure they are designed to minimize risks to personnel and fall within acceptable exposure levels for launch area and launch complex safety.

3.4 LAUNCH COMPLEX SAFETY

The following requirements are in addition to those also specifically identified for launch complex safety in 3.2.1 and 3.3 of this volume.

3.4.4. When hazards extend to range assets or the general public, the SW Commander has the ultimate responsibility to ensure proper safety through an appropriate level of oversight into payload project operations. I

TEXT

RATIONALE/

CHAPTER 4 PSWG AND RANGE SAFETY PROCESSES I

4.1 RANGE SAFETY AND PAYLOAD PROJECTS INTERFACE PROCESS

The safety review and approval process is covered in the NPR 8715.7 and allows for Range Safety approval processes. A Payload Safety Introduction Briefing (PSIB) is typically the first meeting of the PSWG followed by other meetings to complete Safety Review I, II, and III in accordance with NPR 8715.7. The PSIB shall cover the listed information in Attachment 5 of this Volume.

4.6 EQUIVALENT LEVEL OF SAFETY (ELS) DETERMINATIONS AND WAIVERS I

4.6.1. General. Payload projects shall identify the need for any potential Equivalent Level of Safety (ELS) determination and/or waiver regarding requirements in this publication to PSWG and Range Safety for resolution. Potential ELS determinations or waivers shall be identified and presented to the PSWG and Range Safety approval authority at the earliest possible time. Details and requirements for submitting non-compliance requests can be found in Attachment 3 of this volume.

4.6.2. ELS Determination. The phrase “ELS” means an approximately equal level of safety. An ELS may involve a change to the level of expected risk that is not statistically or mathematically significant as determined by qualitative or quantitative risk analysis.

ELS determination made by NASA and AFSPC ranges have been referred to in the past as meets intent certifications. ELS determinations are normally incorporated during the tailoring process.

4.6.3. Waivers: I

4.6.3.1. The term “waiver” refers to a decision that allows a payload project to continue with a launch, including launch process, even though the payload project does not satisfy a specific safety requirement and is not able to demonstrate an ELS. A waiver applies where a failure to satisfy a safety requirement involves a statistically or mathematically significant increase in expected risk as determined through quantitative or qualitative risk analysis, and the activity may or may not exceed the public risk criteria.

4.6.3.2. It is the policy of the NASA and the ranges to avoid the use of waivers. Waivers to the requirements shall be granted only in extremely unique or compelling circumstances and only when the mission objectives of the payload project cannot otherwise be achieved. PSWG, Range Safety, and the payload project shall jointly endeavor to ensure that all requirements of this publication are met as early in the design and operation process as possible to limit the number of required waivers to an absolute minimum.

4.6.3.3. Waivers shall always have the effectivity designated. A "get-well" plan shall be required except for those with lifetime effectivity. C

4.6.3.4. The FAA shall be included in the waiver process for licensed programs at AFSPC ranges per the memorandum of agreement between HQ AFSPC and FAA/AST on Resolving Requests for Relief from Common Launch Safety Requirements. C

TEXT

RATIONALE/

COMMENTS

4.6.3.5. The SW Commanders shall approve or disapprove all waivers affecting public safety as defined in Figure 3.1 and Figure 3.2 of AFSPCMAN 91-710 for a specific mission based on national or mission needs. When the specific mission risks are greater than an expected casualty (Ec) of 300 x 10-6, the SW Commanders shall advise the 14 AF/CC. Refer to AFSPCI 91-701 for risk approval levels. The latest prescribed Air Force Noncompliance Request format shall be used.

4.6.3.6. The Chiefs of Safety or their designated representatives shall approve or disapprove all Air Force waivers other than those affecting public safety. C

4.6.4. Submittal. The payload project shall submit all waiver requests for review and approval separately. ELS determinations shall normally be documented as part of the tailoring process. All approved waivers and ELS determinations shall be included in the appropriate safety data package.

4.6.5. Every applicable waiver shall be reviewed for validity prior to each launch or launch cycle. The payload project shall present a synopsis of each applicable waiver with the rationale concerning its viability for review and approval by Range Safety and the

PSWG.

TEXT

RATIONALE/

COMMENTS

CHAPTER 5 SAFETY AUTHORIZATIONS, SAFETY APPROVALS, AND

DOCUMENTATION

5.1 GENERAL

The overall safety review and approval process for NASA ELV payloads is contained in NPR 8715.7.

TEXT

RATIONALE/

COMMENTS

CHAPTER 6 INVESTIGATING AND REPORTING MISHAPS AND INCIDENTS I

6.1 MISHAPS AND INCIDENTS INVOLVING AIR FORCE PERSONNEL AND RESOURCES

NPR 8621.1, NASA Procedural Requirements for Mishap and Close Call Reporting, Investigating, and Recordkeeping, applies to all NASA mishaps and close calls. For mishaps and incidents occurring on an Air Force range AFI 91-204, Safety Investigations and Reports, also applies and the ranges shall investigate and report all mishaps and incidents involving USAF personnel and resources.

6.2 NON-AIR FORCE PERSONNEL AND RESOURCES ON AIR FORCE PROPERTY I

6.2.1. The AFSPC ranges shall not report or investigate non-Air Force mishaps under AFI 91-204 auspices. However, Range Safety shall assist and participate in non-Air Force mishap investigations that affect or could affect public safety, launch area safety, or Air Force resources and may assist in non-Air Force mishap investigations that affect or could affect launch complex safety or non-Air Force third party resources.

6.2.2. The PSWG and Range Safety shall be provided with the investigation results of any mishaps or incidents occurring on the ranges. C

6.2.3. Regardless of the payload project or Range User, the SW Commander may conduct formal investigations into any mishap and incident on Air Force property that affects or could affect public safety, launch area safety, or launch complex safety. However, the scope of such an investigation into contractor mishaps is limited to the protection of the public, other Range Users, and Air Force personnel and resources.

6.3 REPORTING SPACE LAUNCH SYSTEM ANOMALIES

Any anomaly with potential safety implications and close calls shall be reported in accordance with NPR 8621.21, NASA Procedural Requirements for Mishap and Close Call Reporting Investigating, and Recordkeeping. Any anomaly with potential safety implications occurring in a system during prelaunch processing, launch, flight, or post-launch processing shall be promptly reported to the PSWG and Range Safety for review. Anomalies occurring during launch, flight, or post-launch shall be promptly reported to Range Safety and local safety authorities. Payload projects shall notify the PSWG and Range Safety office of all anomaly reviews/meetings prior to the review/meeting and shall provide copies of the briefings, reports, meeting minutes, and actions identified and taken to address the anomalies.

TEXT

RATIONALE/

COMMENTS

CHAPTER 7 CHANGES TO THIS PUBLICATION I

7.1. This publication shall be updated as needed to coincide with updates to AFSPCMAN 91-710 and NASA requirements and to incorporate document improvements. The latest version with any changes shall be provided on the NASA ELV Payload Safety Program website at http://kscsma.ksc.nasa.gov/ELVPayloadSafety/Default.html.

7.2. Recommended changes to this document shall be sent to the NASA ELV Payload Safety Manager. C

7.4. All changes to this publication shall first be coordinated jointly among the NASA ELV Payload Safety Agency Team and the Air Force Space Command Ranges (30th and 45th Space Wing Safety Offices). All affected NASA payload projects shall be informed of any changes to this publication. The NASA ELV Payload Safety Manager is responsible for keeping this document current and incorporating changes.

TEXT

RATIONALE/

COMMENTS

ATTACHMENT 1 THE NASA ELV PAYLOAD SAFETY REQUIREMENTS

TAILORING PROCESS

A1.1 INTRODUCTION: I

A1.1.1. Purpose. The tailoring approval process is provided in NPR 8715.7. Tailoring provides a means for formulating a specific edition of this publication, incorporating only those requirements that apply to a particular project. Additionally, tailoring allows for the project to propose whether or not they will meet the requirements as written or achieve an ELS through an acceptable alternative.

A tailored version of the publication is denoted by the project’s name in the title. Departures from this policy shall be approved by the PSWG and Range Safety. Tailoring refers to the process used of assessing the applicability of requirements and evaluating the project’s potential implementation in order to generate a set of specific requirements for the project. The tailored edition shall be placed on the payload project’s contract, grants, cooperative agreements or other agreements.

A1.1.2. Content. This attachment describes the rationale for tailoring, the tailoring process, and the requirements for documenting tailored editions of the publication. This NASA ELV Payload Safety Requirements tailoring matrix baseline document may be found on the NASA ELV Payload Safety Program website at http://kscsma.ksc.nasa.gov/ELVPayloadSafety/ Default.html.

A1.1.3. Applicability. The tailoring process is applicable to all NASA ELV payload projects. C

A1.1.4. Formation of a Payload Safety Working Group. A PSWG shall be formed to assist the project as needed in tailoring per this publication. C

A1.1.5. Tailoring Rationale. Tailoring shall be accomplished based on the following rationale described below. Alternative means of identifying deletions, changes, additions, and payload project information are allowable provided that they are distinguishable from the original text and each other and are mutually agreed to by the payload project, PSWG, and Range Safety.

A1.1.5.1. Deletion of a Requirement: I

A1.1.5.1.1. When a requirement is going to be complied with and is applicable to the project, a “C” shall remain in the STATUS column of the tailored document. When a requirement is not applicable to a specific payload project, then a “N/A” shall be placed in the STATUS column and rationale provided under the RATIONALE/COMMENTS column.

A1.1.5.1.2. The original paragraph number and headings shall remain, but the non-applicable text shall be identified with the abbreviation N/A in the STATUS column with rationale provided in RATIONALE/COMMENTS column. C

A1.1.5.2. Change to a Requirement: I

A1.1.5.2.1. ELS determinations may be provided and approved by the PSWG and Range Safety through the change process. I

TEXT

RATIONALE/

COMMENTS

A1.1.5.2.2. A change is allowed to tailor the requirement to a particular system as long as the intent of the requirement is met and the ELS is maintained. An “NC” for noncompliance shall be placed in the tailored STATUS column and sufficient rationale is provided in the RATIONALE/COMMENTS column to allow for PSWG and Range Safety assessment.

A1.1.5.2.3. The change shall be fully captured by showing the entire new paragraph with the change in the TAILORED TEXT column of the tailored document. When the change is an Equivalent Level of Safety the abbreviation “NC” shall be placed in the STATUS column of the tailored document following the paragraph number. The new paragraph with the change shall be provided under the TAILORED TEXT column with sufficient rationale provided under the RATIONALE/COMMENTS column for PSWG and Range Safety assessment. If additional space is needed for the rationale (i.e. to show analysis or data, or to provide lengthy rationale) then an addendum to the tailored document should be used referencing the paragraph number.