eastern range safety policies and...

1 CHAPTER 1

Published by the Range Safety OfficePatrick Air Force BaseFlorida 32925-3238

Eastern and Western Range 127-1 31 December 199 (Change 1 to the 1997 Edition)

CONTENTS

1-iv

Glossary of Abbreviations, Acronymns, and Definitions ..............................................................................................1-vReferenced Documents.............................................................................................................................................. 1-xi

1.1 INTRODUCTION...................................................................................................................................................1-11.1.1 Purpose of the Chapter..............................................................................................................................1-11.1.2 Applicability................................................................................................................................................1-1

1.1.2.1 The Eastern and Western Ranges .................................................................................................1-11.1.2.2 Range Users ..................................................................................................................................1-3

1.2 RANGE SAFETY PROGRAM...............................................................................................................................1-41.2.1 Objective of the Program...........................................................................................................................1-51.2.2 Purpose of the Requirements ....................................................................................................................1-51.2.3 Rationale for the Requirements .................................................................................................................1-51.2.4 Applicability of the 1997 Edition of EWR 127-1..........................................................................................1-6

1.2.4.1 Status of Previously Approved Programs..........................................................................................1-61.2.4.2 Implementation of Required Changes............................................................................................1-7

1.3 RESPONSIBILITIES AND AUTHORITIES............................................................................................................1-71.3.1 Commanders, 45th Space Wing and 30th Space Wing.............................................................................1-71.3.2 Chiefs of Safety, 45th Space Wing and 30th Space Wing .........................................................................1-71.3.3 Commanders, 45th Operations Group and 30th Operations Group...........................................................1-71.3.4 Commander, 45th Logistics Group ............................................................................................................1-71.3.5 Commanders, 45th Support Group and 30th Support Group.....................................................................1-81.3.6 Commanders, 45th Medical Group and 30th Medical Group.....................................................................1-81.3.7 Offices of the Chiefs of Safety, 45th Space Wing and 30th Space Wing ...................................................1-8

1.3.7.1 Air Force Ground Safety, 45th Space Wing and Ground Safety, 30th Space Wing .......................1-81.3.7.2 Mission Flight Control, 45th Space Wing and 30th Space Wing ....................................................1-81.3.7.3 Systems Safety, 45th Space Wing and 30th Space Wing ..............................................................1-91.3.7.4 Operations Support and Analysis, 45th Space Wing, and Flight Analysis, 30th Space Wing..........................................................................................1-101.3.7.5 Relationship with Range Users ....................................................................................................1-10

1.3.8 Range Users and Supporting Agencies...................................................................................................1-10

1.4 RANGE SAFETY POLICY ..................................................................................................................................1-111.4.1 Public Safety............................................................................................................................................1-11

1.4.1.1 Prelaunch and Launch Operations...............................................................................................1-111.4.1.2 Range Safety Critical Systems.....................................................................................................1-121.4.1.3 Control of Errant Vehicle Flight ....................................................................................................1-13

1.4.2 Launch Area Safety .................................................................................................................................1-131.4.3 Launch Complex Safety...........................................................................................................................1-14

1.4.3.1 General Requirements .................................................................................................................1-151.4.3.2 Launch Complex Safety Responsibility ........................................................................................1-151.4.3.3 Launch Complex Safety Training and Certification Requirements ...............................................1-16

1.5 SAFETY AUTHORIZATIONS, COMPLIANCES, AND DOCUMENTATION .......................................................1-161.5.1 Purpose of Obtaining Safety Approvals......................................................................................................1-161.5.2 Authorizations..........................................................................................................................................1-16

1.5.2.1 Safety Approvals Authorized by the Wing Commanders..............................................................1-161.5.2.2 Safety Approvals Authorized by the Chief of Safety or a Designated Representative........................1-171.5.2.3 Launch Complex Safety Approvals Authorized by Control Authorities .........................................1-171.5.2.4 Safety Approvals Authorized by the DoD Explosive Safety Board ...............................................1-17

1.5.3 Radioactive Material Launches................................................................................................................1-171.5.3.1 National Aeronautics and Space Council Compliance .................................................................1-171.5.3.2 Presidential Directive/National Security Council 25 Compliance ..................................................1-171.5.3.3 Radioactive Material Launch Approval .........................................................................................1-17

1.5.4 Documentation and Activity Requirements ..............................................................................................1-171.5.4.1 Tailored EWR 127-1, System Safety Program Plan, Noncompliance Requests, and Launch Complex Safety Training and Certification Plan .......................................................1-171.5.4.2 Flight Data Packages, Intended Support Plans, and Directed Energy Plans ...............................1-181.5.4.3 Missile System Prelaunch Safety Package ..................................................................................1-18

1.5.4.4 Airborne Range Safety System Report ........................................................................................1-181.5.4.5 Ground Operations Plan and Hazardous and Safety Critical Procedures ....................................1-181.5.4.6 Facilities Safety Data Package.....................................................................................................1-181.5.4.7 Launch Operations Approval........................................................................................................1-181.5.4.8 Final Range Safety Approval to Launch.......................................................................................1-18

1.6 RANGE SAFETY AND RANGE USER INTERFACE PROCESS ........................................................................1-181.6.1 Range Safety Funding .............................................................................................................................1-191.6.2 Initial Range Safety and Range User Technical Interchange Meeting.....................................................1-191.6.3 Tailoring Process.....................................................................................................................................1-191.6.4 Other Range Safety and Range User Technical Interchange Meetings and Reviews .............................1-191.6.5 Noncompliance With the Requirements...................................................................................................1-20

1.6.5.1 Meets Intent Certification .............................................................................................................1-201.6.5.2 Deviations and Waivers ...............................................................................................................1-20

1.6.6 System Safety Program Requirements....................................................................................................1-20

1.7 RANGE SAFETY CONCEPT TO LAUNCH PROCESS......................................................................................1-201.7.1 Range Safety Milestones.........................................................................................................................1-201.7.2 Time Frames and Schedules...................................................................................................................1-21

1.8 CHANGES TO APPROVED GENERIC SYSTEMS ............................................................................................1-21

1.9 CHANGES TO EWR 127-1.................................................................................................................................1-21

1.10 INVESTIGATING AND REPORTING MISHAPS AND INCIDENTS...................................................................1-221.10.1 Mishaps and Incidents Involving Air Force Personnel and Resources...................................................1-221.10.2 Non-Air Force Personnel and Resources ..............................................................................................1-22

1.11 RANGE SAFETY RANGE USER HANDBOOK ................................................................................................1-22

1.12 RANGE SAFETY WEB SITE ...........................................................................................................................1-22

APPENDIX 1A: THE EWR 127-1 TAILORING PROCESS ...................................................................................................1-23APPENDIX 1B: SYSTEM SAFETY PROGRAM REQUIREMENTS......................................................................................1-26APPENDIX 1C: SUBMITTING EWR 127-1 NONCOMPLIANCE REQUESTS......................................................................1-36APPENDIX 1D: EWR 127-1 ACCEPTABLE RISK CRITERIA ..............................................................................................1-39APPENDIX 1E: MAKING CHANGES TO EWR 127-1 .........................................................................................................1-40APPENDIX 1F: GENERIC PAYLOAD POLICY AND APPROVAL PROCESS .....................................................................1-41APPENDIX 1G: LAUNCH COMPLEX SAFETY TRAINING AND CERTIFICATION .................................................................1-

Chapter 1: Eastern and Western Range Safety Policies and Processes 31 December 199 (Change 1 to the 1997 Edition

CONTENTS

1-iii

Eastern and Western Range 127-1 31 December 199 (Change 1 to the 1997 Edition

GLOSSARY OF ABBREVIATIONS, ACRONYMS, AND DEFINITIONS

1-iv

30 SW/SEGP - 30th Space Wing, OperationsSafety

30 SW/SEO - 30th Space Wing, Mission FlightControl

30 SW/SEY - 30th Space Wing, Flight Analysis

45 SW/SEO - 45th Space Wing, Mission FlightControl and Analysis

45 SW/SEOE - 45th Space Wing, ExpendableLaunch Vehicle Operations Support and Analysis

45 SW/SEOO - 45th Space Wing, Mission FlightControl

45 SW/SEOS - 45th Space Wing, Space Trans-portation System Operations Support and Analysis

45 and 30 LG - 45th and 30th Logistics Group

45 and 30 MDG - 45th and 30th Medical Group

45 and 30 OG - 45th and 30th Operations Group

45 and 30 SPTG - 45th and 30th Support Group

45 and 30 SW/SE - 45th and 30th Space Wing,Office of the Chief of Safety; see also Office of theChief of Safety

45 and 30 SW/SEG - 45th and 30th Space Wing,Ground Safety

45 and 30 SW/SES - 45th and 30th Space Wing,Systems Safety

approval - Range Safety approval is the final ap-proval necessary for data packages such as thePreliminary Flight Data Package, the Final FlightData Package, the Missile System PrelaunchSafety Package, the Range Safety System Report,the Ground Operations Plan, and the FacilitySafety Data Package. In addition, Range Safetyapproval is required for hazardous and safety criti-cal procedures prior to the procedure being per-formed; however, Range Safety approval does notconstitute final approval for hazardous and safetycritical procedures since Range Users normallyhave additional approval requirements prior to theprocedure being performed.

AF - Air Force

AFETR - Air Force Eastern Test Range

AFI - Air Force Instruction

BDA - Blast Danger Area

Blast Danger Area - a hazardous clear area;clearance prior to establishment of a major explo-sive hazard such as vehicle fuel/oxidizer load andpressurization; the area subject to fragment anddirect overpressure resulting from the explosion ofthe booster/payload

CAL-OSHA - California Occupational Safety andHealth Act

CCAS - Cape Canaveral Air Station

cDR - Conceptual Design Review

CDR - Critical Design Review; Command De-struct Receiver

CFR - Code of Federal Regulations

COLA - Collision Avoidance

collective risk - the total risk to an exposed popu-lation; the expected (average, mean) number ofindividuals who will be casualties

commercial user - a non-federal government or-ganization that provides launch operations services

Control Area Clears - a hazardous clear area;clearance of defined areas to protect personnelfrom hazardous operations

control authority - a single commercial user on-site director and/or manager, a full time govern-ment tenant director and/or commander, or UnitedStates Air Force squadron/detachment commanderresponsible for the implementation of launch com-plex safety requirements

deviation - a designation used when a design non-compliance is known to exist prior to hardwareproduction or an operational noncompliance isknown to exist prior to beginning operations atCCAS and Vandenberg Air Force Base

DDESB - Department of Defense ExplosiveSafety Board

DEP - Directed Energy Plan

DoD - Department of Defense

DoDD - Department of Defense Directive

DOT - Department of Transportation



1-v

ECP - Engineering Change Proposal

ER - Eastern Range

ERR - Eastern Range Regulation

ESMCR - Eastern Space and Missile CenterRegulation

errant launch vehicle -a launch vehicle that,during flight, violates established flight safety cri-teria and/or operates erratically in a manner incon-sistent with its intended flight performance. Con-tinued flight of an errant launch vehicle maygrossly deviate from planned flight, with the pos-sibility of increasing public risk to unacceptablelimits.

explosive warhead launch approval - the man-datory prior written approval given by the Easternor Western Range Commanders to Range Userswho launch launch vehicles carrying explosivewarheads

explosive quantity distance site plans - a formalplan for explosives facilities and areas required inaccordance with AFM 91-201 and DoD 6055.9-STD detailing explosives quantity operating andstorage limits and restrictions and resultant dis-tance clearance requirements

FAA/AST - Federal Aviation Administra-tion/Associate Administrator for CommercialSpace Transportation

FCA - Flight Caution Area

FDR - Final Design Review

FFDP - Final Flight Data Package

FFPA - Final Flight Plan Approval

Flight Caution Area - a Hazardous Launch Area;the controlled surface area and airspace outside theFlight Hazard Area (FHA) where individual riskfrom a launch vehicle malfunction during the earlyphase of flight exceeds 1 x 10-6. When activated,only personnel essential to the launch operation(mission-essential) with adequate breathing pro-tection are permitted in this area; see also FlightHazard Area, mission-essential personnel

FHA - Flight Hazard Area

Flight Hazard Area - a Hazardous Launch Area;the controlled surface area and airspace about thelaunch pad and flight azimuth where individualrisk from a malfunction during the early phase of

flight exceeds 1 x 10-5. Because the risk of seriousinjury or death from blast overpressure or debris isso significant, only mission-essential personnel inapproved blast-hardened structures with adequatebreathing protection are permitted in this areaduring launch.

FSDP - Facility Safety Data Package

FTS - Flight Termination System

GOP - Ground Operations Plan

GPS - Global Positioning System

h - hour, hours

Hazardous Clear Areas - Safety Clearance Zonesfor ground processing that are defined in the Op-erations Safety Plans for each operating facility;include BDA, Control Area Clears, and ToxicHazard Corridor

Hazardous Launch Area Clearance - requiredclearances; concurrence from the Chief of Safetymust be obtained for all personnel required or re-questing to be in a Hazardous Launch Area duringa launch operation; mission-essential personnelmay be permitted within the Impact Limit Linesand the FCA, but only within the FHA if locatedin approved blast-hardened structures with ade-quate breathing apparatus; Wing-essential person-nel located at required work areas and non-essential personnel may be permitted inside theimpact limit lines with Wing Commander ap-proval; see also FCA, FHA, impact limit lines,mission-essential personnel

Hazardous Launch Areas - Safety ClearanceZones during launch operations, including theFCA, FHA, Vessel Exclusion Area, and impactlimit lines

HCA - Hazardous Clear Areas

HLA - Hazardous Launch Areas

HPWT - High Performance Work Team

ILL - impact limit line

imminent danger - any condition, operation, orsituation that occurs on the Range where a dangerexists that could reasonably be expected to causedeath or serious physical harm, immediately orbefore the imminence of such danger can beeliminated through control procedures; thesesituations also include health hazards where it is



1-vi

reasonably expected that exposure to a toxic sub-stance or other hazard will occur that will causeharm to such a degree as to shorten life or cause asubstantial reduction in physical or mental effi-ciency even though the resulting harm may notmanifest itself immediately

impact limit line - a Hazardous Launch Area; theboundary within which trajectory constraints andFTSs are used to contain an errant launch vehicleand vehicle debris. Mission-essential and Wing-essential personnel are permitted within the ILLs;with Wing Commander approval, non-essentialpersonnel may be permitted within this area. How-ever, the collective risk will not exceed acceptablestandards for non-essential personnel; see alsomission-essential personnel, non-essential person-nel

individual risk - the risk to a randomly exposedindividual; the probability that the individual willbe a casualty

ISP - Intended Support Plan

KMR - Kwajalein Missile Range

KSC - Kennedy Space Center

launch area safety - safety requirements involv-ing risks limited to personnel and/or property onCCAS and may be extended to KSC or VAFB;involves multiple commercial users, governmenttenants, or United State Air Force squadron com-manders

launch area - the facility, in this case, CCAS andKSC or Vandenberg Air Force Base, where launchvehicles and payloads are launched; includes anysupporting sites on the Eastern or Western Range;also known as launch head

launch complex - a defined area that supportslaunch vehicle or payload operations or storage;includes launch pads and/or associated facilities

launch complex safety - safety requirements in-volving risk that is limited to personnel and/orproperty located within the well defined confinesof a launch complex, facility, or group of facilities;for example, within the fence line; involves riskonly to those personnel and/or property under thecontrol of the control authority for the launchcomplex, facility, or group of facilities

launch head - see launch area

launch vehicle - a vehicle that carries and/or de-livers a payload to a desired location; this is a ge-neric term that applies to all vehicles that may belaunched from the Eastern and Western Ranges,including but not limited to airplanes; all types ofspace launch vehicles, manned space vehicles,missiles, and rockets and their stages; probes;aerostats and balloons; drones; remotely pilotedvehicles; projectiles, torpedoes and air-droppedbodies

lead time - the time between the beginning of aprocess or project and the appearance of its results

LDCG - Launch Disaster Control Group; ER andWR teams responsible for responding to launchemergencies

LRR - Launch Readiness Review

MIC - meets intent certification; a noncompliancedesignation used to indicate that an equivalentlevel of safety is maintained despite not meetingthe exact requirements stated in this Regulation

MIL-SPEC - military specification

MIL-STD - military standard

mission-essential personnel - those persons nec-essary to successfully and safely complete a haz-ardous or launch operation and whose absencewould jeopardize the completion of the operation;includes persons required to perform emergencyactions according to authorized directives, personsspecifically authorized by the Wing Commanderto perform scheduled activities, and person intraining; the number of mission-essential person-nel allowed within Safety Clearance Zones orHazardous Launch Areas is determined by theWing Commander and the Range User with RangeSafety concurrence

MSPSP - Missile System Prelaunch Safety Pack-age

NASA - National Aeronautics and Space Admini-stration

NASC - National Aeronautics and Space Council

NAWC - Naval Air Warfare Center

NSC - National Security Council

noncompliance - a noticeable or marked departurefrom Regulation standards or procedures; includes



1-vii

deviations, meets intent certifications, and waivers

non-essential personnel - those persons notdeemed mission-essential or Wing-essential; in-cludes the general public, visitors, the media, andany persons who can be excluded from SafetyClearance Zones with no effect on the operation orparallel operations

O&SHA - Operating and Support Hazard Analy-sis

OSHA - Occupational Safety and Health Act

Office of the Chief of Safety - the Range officeheaded by the Chief of Safety; this office ensuresthat the Range Safety Program meets Range andRange User needs and does not impose undue oroverly restrictive requirements on a program

OCST - Office of Commercial Space Transporta-tion, DOT

PAFB - Patrick Air Force Base located in Florida

PMRF - Pacific Missile Range Facility

payload - the object(s) within a payload fairingcarried or delivered by a launch vehicle to a de-sired location or orbit; a generic term that appliesto all payloads that may be delivered to or fromthe Eastern or Western Ranges; includes but is notlimited to satellites, other spacecraft, experimentalpackages, bomb loads, warheads, reentry vehicles,dummy loads, cargo, and any motors attached tothem in the payload fairing

PD - presidential directive

PDR - Preliminary Design Review

PFDP - Preliminary Flight Data Package

PHA - Preliminary Hazard Analysis

PL - public law

program - the coordinated group of tasks associ-ated with the concept, design, manufacture, prepa-ration, checkout, and launch of a launch vehicleand/or payload to or from, or otherwise supportedby the Eastern or Western Ranges and the associ-ated ground support equipment and facilities

PTR - Program Trouble Report

public safety - safety involving risks to the gen-eral public of the United States or foreign coun-tries and/or their property

radioactive material launch approval - approvalgranted by Range Safety to Range Users intendingto launch radioactive materials

Range Commander - Commander of the Easternand Western Range in accordance with DoDD3200.11; sometimes called Range Director, wheninterfacing with commercial Range Users.NOTE: Currently, the 45 SW and 30 SW Com-manders are also the Range Commanders andRange Directors

Range Safety Launch Commit Criteria - haz-ardous or safety critical parameters, including, butnot limited to, those associated with the launchvehicle, payload, ground support equipment,Range Safety System, hazardous area clearancerequirements, and meteorological conditions thatmust be within defined limits to ensure that public,launch area, and launch complex safety can bemaintained during a launch operation

Range Safety Program - a program implementedto ensure that launch and flight of launch vehiclesand payloads present no greater risk to the generalpublic than that imposed by the overflight of con-ventional aircraft; such a program also includeslaunch complex and launch area safety and pro-tection of national resources

Range Safety System - the system consisting ofthe airborne and ground flight termination sys-tems, airborne and ground tracking system, andthe airborne and ground telemetry data transmis-sion systems

Range Users - clients of the Cape Canaveral AirStation and Vandenberg Air Force Base, such asthe Department of Defense, non-Department ofDefense US government agencies, civilian com-mercial companies, and foreign government agen-cies that use Eastern or Western Range facilitiesand test equipment; conduct prelaunch, launch,and impact operations; or require on-orbit support



1-viii

Ranges - in this document, Ranges refers to theEastern Range at CCAS, KSC, and PAFB, and theWestern Range at Vandenberg Air Force Base

risk - a measure that takes into consideration boththe probability of occurrence and the consequenceof a hazard to a population or installation. Risk ismeasured in the same units as the consequencesuch as number of injuries, fatalities, or dollarloss. For Range Safety, risk is expressed as casu-alty expectation or shown in a risk profile; see alsocollective risk and individual risk.

risk analysis - a study of potential risk

risk-cost benefit concept - the concept used todetermine the granting of waivers, deviations, ormeets intent certifications to Eastern and WesternRange 127-1 requirements by comparing the costs,risks, and benefits of the mission. If the applica-tion of an EWR 127-1 requirement results in asignificant reduction of risk at an acceptable levelof cost, it may be judged by Range Safety to besufficient to impose a requirement; however, if thebenefit is insignificant and/or the cost is high, therequirement may be deviated from, waived, or de-termined to meet the intent, all with considerationto public safety. The risk of concern may be themean or average risk, or it may be a risk corre-sponding to a high consequence at a low probabil-ity (a catastrophic risk). The assurance of a verylow probability may be required for a very highconsequence even if a high cost may be entailed.

RSBBS - Range Safety Bulletin Board System

RSLCC - Range Safety Launch Commit Criteria

RSSR - Airborne Range Safety System Report

RTS - Range Tracking System

safety holds - the holdfire capability, emergencyvoice procedures, or light indication system ofeach launch system used to prevent launches in theevent of loss of Range Safety critical systems orviolations of mandatory Range Safety launchcommit criteria

Safety Clearance Zones - restricted areas desig-nated for day-to-day prelaunch processing andlaunch operations to protect the public, launcharea, and launch complex personnel; these zonesare established for each launch vehicle and pay-load at specific processing facilities, including

launch complexes; includes HCA and HLA

safety margins (destruct) - margins used to avoidoverly restrictive flight termination limits; nor-mally based on launch vehicle three-sigma per-formance characteristics

SCN - Specification Change Notice

SHA - System Hazard Analysis

space safety professional - a safety professionalwho has been trained and formally certified tomeet the criteria outlined in the Launch ComplexSafety Training and Certification Program Docu-ment

SPR - Software Problem Report

SSHA - Subsystem Hazard Analysis

SSPP - System Safety Program Plan

STR - Software Trouble Report

STS - Space Transportation System

SWI - space wing instruction

TDTS - Telemetry Data Transmitting System

THC - Toxic Hazard Corridor

TIM - Technical Interchange Meeting

Toxic Hazard Corridor - a Hazardous ClearArea; clearance of a sector in which toxic materialmay reach predetermined concentration levels

TPS - Telemetry Processing Station

US - United States

USAF - United States Air Force

USC - United States Code

VEA - Vessel Exclusion Area

Vessel Exclusion Area - a combination of the seasurface area and airspace measured from thelaunch point and extending downrange along theintended flight azimuth; the size of the VEA isbased on hazard containment or a combination ofacceptable impact probability and personnel risk

WCOOA - West Coast Offshore Operating Area

waiver - a designation used when, through an errorin the manufacturing process or for other reasons, ahardware noncompliance is discovered after hard-ware production, or an operational noncompliance



1-ix

is discovered after operations have begun at theEastern or Western Range

Wing Commander - see Range Commander

WSMCR Western Space and Missile CenterRegulation

VAFB - Vandenberg Air Force Base; located inCalifornia

WR - Western Range

WRR - Western Range Regulation


REFERENCED DOCUMENTS

1-x

29 CFR 1910.119, Process Safety Management ofHighly Hazardous Chemicals

40 CFR 355, Emergency Planning and Notifica-tion

40 CFR 68, Risk Management Program

45 SWI 99-101, 45th Space Wing Mission Pro-gram Documents

AFI 91-204, Safety Investigations and Reports

AFI 91-110, Nuclear Safety Review and LaunchApproval for Space or Missile Use of RadioactiveMaterial and Nuclear Systems

AFI 99-101, Developmental Test and Evaluation

AFI 99-102, Operational Test and Evaluation

AFI 99-113, Space Systems Test and EvaluationProcess Direction and Methodology for SpaceSystems Testing

AFMAN 91-201, Explosive Safety Standards

AFMAN 99-110, Airframe Propulsion-AvionicsTest and Evaluation Process

CERCLA, Comprehensive Environmental Re-sponse, Compensation, and Liability Act of 1980

Department of Defense Directive 3200.11, MajorRange and Test Facility Base

Department of Defense Directive 3230.3, DoDSupport for Commercial Space Launch Activities

DoD 6055.9-STD, DoD Ammunition and Explo-sives Safety Standards

DOT OCST 14 CFR, Chapter III, “CommercialSpace Transportation; Licensing Process forCommercial Space Launch Activities”

Executive Order 12856, “Federal Compliance withRight-to-Know Laws and Pollution PreventionRequirements”

MIL-STD-498, Software Development and Docu-mentation

National Aeronautics and Space Council, NuclearSafety Review and Approval Procedures for MinorRadioactive Sources in Space Operations

Presidential Directive/National Security Council25, Scientific or Technological Experiments withPossible Large-Scale Adverse Environmental Ef-fects and Launch of Nuclear Systems into Space

Public Law 10, 10 USC Section 172, AmmunitionStorage Board

Public Law 91-596, 29 USC 651-678, Occupa-tional Health and Safety Act

Public Law 60, 81st Congress, 1st Session, GuidedMissiles Joint Long Range Proving Ground

Public Law 98-575, 49 USC 2601-2623, TheCommercial Space Launch Act of 1984, AsAmended

Public Law 99-499, 42 USC 11001-11050, Su-perfund Amendments and Reauthorization Act(SARA), Title III: Emergency Planning and Com-munity Right-to-Know Act (EPCRA)

CHAPTER 1EASTERN AND WESTERN RANGE

SAFETY POLICIES AND PROCESSES

1-1

1.1 INTRODUCTION1.1.1 Purpose of the ChapterChapter 1 describes the Range Safety Program;defines responsibilities and authorities; and de-lineates policies, processes, and approvals for allactivities from design concept through test, check-out, assembly, and launch of launch vehicles andpayloads to orbital insertion or impact from oronto the Eastern Range (ER) or Western Range(WR). The following major topics are addressed:

1.2 Range Safety Program1.3 Responsibilities and Authorities1.4 Range Safety Policy1.5 Safety Authorizations, Compliances, and

Documentation1.6 Range Safety and Range User Interface

Process1.7 Range Safety "Concept to Launch" Process1.8 Changes to Approved Generic Systems1.9 Changes to the Document1.10 Investigating and Reporting Mishaps and

Incidents1.11 Range Safety Range User Handbook1.12 Range Safety Bulletin Board System

1.1.2 ApplicabilityThe policies, requirements, processes, procedures,and approvals defined in this Chapter and the otherchapters in this document are applicable to all or-ganizations, agencies, companies, and programsconducting or supporting operations on the ER andWR. NOTE: When used in this document, theterms Range or Ranges refer to both the Eastern

Range and the Western Range.

1.1.2.1 The Eastern and Western Ranges

1.1.2.1.1 The Eastern Range.a. The ER is the launch head at Cape Canaveral

Air Station (CCAS); owned or leased facilities ondownrange sites such as Antigua and Ascension;and in the context of launch operations, the AtlanticOcean, including all surrounding land, sea, and airspace within the reach of any launch vehicle ex-tending eastward into the Indian and PacificOceans. Figure 1-1 shows the typical launch sectorfor launches from the ER; Figure 1-2 shows ownedor leased facilities on sites downrange from the ER.

b. Range management activities are concen-trated at Patrick Air Force Base (PAFB), Florida.

c. Launch vehicle and payload prelaunch andlaunch activities are concentrated at CCAS, Ken-nedy Space Center (KSC), and miscellaneousoutlying support locations. d. Launch activities conducted by ER person-nel operating outside the geographical limits de-scribed above may occur under Department of De-fense (DoD) or United States Air Force (USAF)direction or under the auspices of agreementsmade by those agencies. In such cases, the termEastern Range or ER is expanded to include thesesituations and apply, as required, for the specificmission, launch, launch area, and impact area.

Eastern and Western Range 127-1 31 December 1999 Change to 1997 EWR

1-2

Figure 1-1Typical Launch Sector for Launches From the Eastern Range

Chapter 1: Eastern and Western Range Safety Policies and Processes 31 December 1999 Change to 1997 EWR

1-3

1.1.2.1.2 The Western Range.a. The WR is the launch head at Vandenberg

Air Force Base (VAFB) and extends along theWest Coast of the continental United States (US)westward through the Pacific and Indian Oceans.Figure 1-3 shows the typical launch sector forlaunches from the WR; Figure 1-4 shows ownedor leased facilities on sites uprange along the Pa-cific Coast, including US Navy facilities at PointMugu, and downrange from the WR.

b. Range management activities as well aslaunch and prelaunch processing activities areconcentrated at VAFB in California.

c. Launch activities conducted by WR personneloperating outside the geographical limits describedabove may occur under DoD or USAF direction orunder the auspices of agreements made by thoseagencies. In such cases, the term Western Range orWR is expanded to include these situations andapply, as required, to the specific mission, launch,launch area, and impact area.

1.1.2.1.3 Eastern and Western Range Dif-ferences. The ER and WR have some differencesin their Range Safety requirements. These differ-ences are caused by geographical differences thatchange risk levels for launch operations, organiza-tional variations, and different Range User re-quirements such as those associated with mannedspace flights at the ER and ballistic launches intothe Kwajalein Atoll and aircraft tests at the WR.At present, where a requirement differs, the RangeUser may standardize to the more stringent re-quirement or meet the requirements of eachRange, whichever option is technically or eco-nomically more desirable. Specific ER and WRdifferences are noted throughout this document.

1.1.2.2 Range Users

Range Users include the DoD, non-DoD US gov-ernment agencies, civilian commercial companies,and foreign government agencies that use ER andWR facilities and test equipment; conduct prelaunch,

Figure 1-2Owned or Leased Facilities on Sites Downrange from the Eastern Range


1-4

launch operations, and impact; or require on-orbit orother related support.

a. Commercial users intending to providelaunch services from one of the Ranges shall besponsored and have a license from the Departmentof Transportation (DOT) or have a DoD sponsor-ship and be accepted by the DoD to use the ER orWR.

b. Foreign government organizations or compa-nies shall be sponsored by an appropriate US gov-ernment organization or be a customer of a com-mercial Range User.

1.2 RANGE SAFETY PROGRAMThe national range system, established by PublicLaw 60, was originally sited based on two primaryconcerns: location and public safety. Thus, RangeSafety, in the context of national range activities,is rooted in PL 60.

To provide for the public safety, the Ranges, usinga Range Safety Program, shall ensure that thelaunch and flight of launch vehicles and payloadspresent no greater risk to the general public thanthat imposed by the overflight of conventionalaircraft. In addition to public protection, safety ona national range includes launch area safety,launch complex safety, and the protection of na-tional resources.

Range Safety is intrinsic to the range mission ofproviding Range Users the facilities, instrumenta-tion, and infrastructure to support launch vehiclesand payloads during prelaunch and launch opera-tions. Significant hazards and risks are inherent tolaunch vehicle and payload tests and operations;therefore, all reasonable precautions shall be takento minimize these risks with respect to life, health,

Figure 1-3Typical Launch Sector For Launches From the Western Range


1-5

and property.

1.2.1 Objective of the ProgramThe objective of the Range Safety Program is toensure that the general public, launch area person-nel, foreign land masses, and launch area resourcesare provided an acceptable level of safety and thatall aspects of prelaunch and launch operations ad-here to public laws and national needs. The mutualgoal of the Ranges and Range Users shall be tolaunch launch vehicles and payloads safely andeffectively with commitment to public safety.

1.2.2 Purpose of the RequirementsThrough these requirements, the ER and WRSafety Programs implement and carry out the re-sponsibilities or standards contained in or appliedby the following laws and directives:

a. Public Law 60, Legislative History, 81st Con-gress

b. Public Law 10, 10 USC, Section 172c. Public Law 91-596, 29 USC. NOTE: Con-

tractors are solely responsible for compliance withOSHA standards and the protection of their em-ployees.

d. Public Law 98-575, 49 USCe. Presidential Directive (PD)/National Security

Council (NSC) 25f. Department of Defense Directive 3200.11g. Department of Defense Directive 3230.3

1.2.3 Rationale for the RequirementsThis document provides a baseline generic ap-proach for Range Users and Range organizationsthat use the ER or WR to handle, store, assemble,checkout, and launch launch vehicles and theirassociated payloads. The document is written tocover a multitude of programs and Range Users. Itspans a wide range of complex systems from thelaunch of the manned space shuttle to loading war-

Figure 1-4Owned or Leased Facilities On Sites Uprange Along the Pacific Coast Including US Navy

Facilities at Point Mugu and Downrange From the Western Range


1-6

shot torpedoes on submarines. The document hasbeen developed as a baseline document for thefollowing reasons:

a. Past experience and input from Range Usersregarding concerns about referenced documents,particularly military standards and military speci-fications, causing a tiering effect with the resultthat designers have difficulty understanding whichspecific requirements apply to a given design

b. Standardized design and safety requirementsfor many aerospace hazardous systems that do notexist except in this document

c. The need for a set of standards that, throughexperience, ensures a prudent level of public safe-ty protection is provided during prelaunch andlaunch operations

d. The need for a set of minimum criteria andrequirements to ensure launch area safety sincecommercial users are not required to directly usemilitary standards or military specifications in thedesign of their hazardous systems except for flighttermination systems required by the Ranges.Therefore, to ensure each Range User is protectedfrom the activities of others, this baseline docu-ment provides a set of minimum criteria and re-quirements to ensure launch area safety.

e. Wherever possible, military standards (MIL-STDs) and military specifications (MIL-SPECs)will be replaced with equivalent commercial stan-dards. Anywhere a MIL-STD or MIL-SPEC isreferenced in this document, an equivalent com-mercial standard may be used. However, both 45SW/SE and 30 SW/SE shall recognize and ap-prove the equivalency of the commercial standardprior to its use. As commercial standards andspecifications are developed and approved, thisdocument will be updated to list and/or incorpo-rate them.

1.2.4 Applicability of the 1997 Edition ofEWR 127-1

This edition of EWR 127-1 is applicable to all newprograms with Program Introduction submittalsdated after 31 October 1997. NOTE: Programsthat have begun significant design prior to thisdate and with Program Introductions occurring at alater date may submit a program milestone sched-ule (cDR, PDR, CDR, PI, document submittals,and other items) and request Range Safety concur-rence that the edition/revision of 127-1 at the timeof design commencement is acceptable. However,all Range Users are encouraged to perform Pro-

gram Introductions at the earliest possible time inthe program.

1.2.4.1 Status of Previously Approved Programs

Existing program approval and compliance agree-ments on Range User flight hardware systems andsubsystems and ground support equipment, facili-ties, operations, and procedures, including all de-viations, waivers, and meets intent certifications,approved prior to 31 October 1997 shall be honoredand do not have to meet the requirements in thisdocument unless it is determined by the Chief ofSafety or the Range User that one or more of thesituations listed in a through g below exist. NOTE:The exceptions also apply to programs that are ap-proved in accordance with this document, whenapplication of previously non-enforced require-ments of this document are contemplated.

a. Existing programs make major modifications orinclude the use of currently approved components,systems, or subsystems in new applications. EX-CEPTION: Previously approved existing components,systems, or subsystems that do not increase the risks,do not degrade safety, or can survive new environ-ments or the new environments are equivalent to orlower than the originally approved qualification levelsshall be honored and do not have to meet new re-quirements as long as data and analyses submitted toand approved by Range Safety show that the criteriahave been met.

b. The Range User has determined that it is eco-nomically and technically feasible and desirable toincorporate new requirements into the system.

c. The system has been or will be modified to theextent that it is considered a new program or thatexisting safety approvals no longer apply. NOTE:Risk and hazard analyses in accordance with Ap-pendix 1B and developed jointly by Range Safetyand the Range User shall be used by Range Safety todetermine applicability of the safety approvals.

d. A previously unforeseen or newly discoveredsafety hazard exists that is deemed by either RangeSafety or by the Range User to be significantenough to warrant the change.

e. The system does not meet the requirementsexisting when the system was originally accepted.NOTE: This category includes systems that werepreviously approved, but when obtaining the ap-proval, noncompliances to the original requirementwere not identified.

f. A system or procedure is modified and a newrequirement reveals that a significant risk exists.


1-7

g. Mishap and incident investigations and re-ports may dictate compliance with this edition ofthe document.

1.2.4.2 Implementation of Required Changes

All program hardware and operational changesrequired by the imposition of a new Range Safetyrequirement shall be implemented in a manner andon a schedule that minimizes the impact on theprogram and that is agreed to by both the RangeUser and Range Safety.

1.3 RESPONSIBILITIES ANDAUTHORITIES

PL 10, PL 60, PL 98-575, and PD/NSC 25, as im-plemented by DoDDs 3200.11 and 3230.3, definepublic, international, launch area, and launchcomplex safety requirements and establish the re-sponsibility for safety on the Range.

1.3.1 Commanders, 45th Space Wing and30th Space Wing

a. Final authority and responsibility for safety atthe ER and WR rests with the Space Wing Com-manders (Range Commanders). The Range Com-mander or a designated representative is responsiblefor carrying out the Range Safety Program describedin this document.

b. The Wing Commanders shall implement, han-dle noncompliances, and/or disposition the require-ments of this document as it applies to Range Userprograms on their Range.

c. Where feasible, the Wing Commanders shallcoordinate all actions between the Ranges to en-sure that consistent and standard Range Safetyrequirements and approvals are levied on allRange Users.

1.3.2 Chiefs of Safety, 45th Space Wingand 30th Space Wing

The Chiefs of Safety, the designated representa-tives of the Wing Commanders/Range Command-ers, are responsible for establishing, complyingwith, implementing, and directing the Range

Safety Program. The Chiefs of Safety responsi-bilities include the following:

a. Enforcing public safety requirements; defin-ing launch area safety and launch complex safetyrequirements for mission flight control and otherRange Safety launch support operations

b. Reviewing and coordinating changes with theRange User and providing Range Safety approvalfor operational procedures along with oversight forall prelaunch operations at the launch complex andlaunch vehicle or payload processing facilities forpublic safety and launch area safety concerns

c. Reviewing, providing Range Safety approval,and auditing operations at a launch complex andassociated support facilities for launch complexsafety concerns in accordance with a jointly ac-cepted Launch Complex Safety Training and Cer-tification program. NOTE: If the Range Usercontrol authority decides not to implement theplan then Range Safety will assume completesafety responsibility per subparagraph b above.

1.3.3 Commanders, 45th Operations Groupand 30th Operations Group

The Commanders, 45th Operations Group (45OG) and 30th Operations Group (30 OG), are re-sponsible for:

a. Complying with, implementing, and enforc-ing the Range Safety Program

b. Reviewing and accepting all prelaunch andlaunch operations procedures at CCAS and VAFBfor Air Force Programs, including hazardous andsafety critical procedures that may affect publicsafety or launch area safety, after insuring theyhave been approved by Range Safety

c. As a control authority, in accordance with theLaunch Complex Safety Training and CertificationPlan, reviewing and approving prelaunch andlaunch operations procedures for Air Force pro-grams that are limited to launch complex safetyconcerns

d. Providing 45 SW/SE and 30 SW/SE with theinstrumentation, computers, communications,command transmitter systems, weather support,and Range Safety display systems necessary tocarry out prelaunch and flight safety functions.Range Safety shall provide the Operations Groupswith mandatory support requirements, and the Op-erations Groups shall ensure that these require-ments are met.


1-8

1.3.4 Commander, 45th Logistics GroupThe Commander, 45th Logistics Group (45 LG)and 30thLogistics Group (30 LG), are responsiblefor complying with, implementing, and directingthe Range Safety Program and ensuring that allrequired instrumentation, computers, communica-tions, command systems, and display systems nec-essary for Range Safety to carry out its functionsperform to the prescribed level of reliability andmeet specified design requirements.

1.3.5 Commanders, 45th Support Groupand 30th Support Group

The Commanders, 45th Support Group (45 SPTG)and 30th Support Group (30 SPTG), are responsi-ble for complying with, implementing, and di-recting the Range Safety Program and determin-ing, coordinating, and enforcing fire safety, envi-ronmental engineering, and explosive ordnancedisposal requirements. The Fire Department, Envi-ronmental Engineering, and Explosive OrdnanceDisposal are responsible for establishing and im-plementing their programs in coordination with theOffice of the Chief of Safety.

1.3.6 Commanders, 45th Medical Groupand 30th Medical Group

The Commanders, 45th Medical Group (45 MDG)and 30th Medical Group (30 MDG), are responsi-ble for complying with, implementing, and di-recting the Range Safety Program and determin-ing, coordinating, and enforcing medical, biologi-cal, and radiological health requirements. Radia-tion Protection Officers and BioenvironmentalEngineering are responsible for establishing andimplementing their programs in coordination withthe Office of the Chief of Safety.

1.3.7 Offices of the Chiefs of Safety, 45thSpace Wing and 30th Space Wing

The Offices of the Chiefs of Safety, 45th SpaceWing (45 SW/SE) and 30th Space Wing (30SW/SE) ensure that the Range Safety Programcomplies with public law and DoD directives asnoted in the Purpose of the Requirement sectionof this Chapter, meets the needs of the Ranges andRange Users, and does not impose undue or overlyrestrictive requirements on Range User programs.NOTE: Unless otherwise noted, the use of theterm Range Safety in this Chapter refers to 45SW/SE and 30 SW/SE. The Safety Offices provideoperational, engineering, scientific, and mathe-

matical expertise to accomplish flight analysis,system safety, mission flight control, and AirForce ground safety. Figures 1-5a and b providecharts representative of both of the Eastern andWestern Range Safety Organizations. The respon-sibilities of these sections are slightly different andare described below:

1.3.7.1 Air Force Ground Safety, 45th SpaceWing and 30th Space Wing and OperationsSafety, 30th Space Wing

1.3.7.1.1 Air Force Ground Safety, 45thSpace Wing and 30th Space Wing. Air ForceGround Safety, 45th Space Wing (45 SW/SEG)and 30th Space Wing (30 SW/SEG), are responsi-ble for developing and implementing a ground andindustrial safety program for Air Force personneland Air Force resources.

1.3.7.1.2 Operations Safety, 30th SpaceWing. Operations Safety, 30th Space Wing (30SW/SEGP) is responsible for the following. NOTE:30 SW/SEGP is similar to the ER OperationsSafety, a government contractor.

a. Reviewing, coordinating, and approving pro-cedures for prelaunch processing

b. Monitoring selected activities at the launchhead

c. Providing prelaunch and countdown LaunchDisaster Control Groups

d. Defining Safety Clearance Zones and provid-ing advice for the control of access to Safety Clear-ance Zones within the confines of the launch head

e. Providing emergency response support and/orassistance in the event of failures and mishaps dur-ing ground operations

f. Advising the on-site commander on disasterpreparedness and responsiveness

1.3.7.2 Mission Flight Control, 45th SpaceWing and 30th Space Wing

Mission Flight Control, 45th Space Wing (45SW/SEOO) and 30th Space Wing (30 SW/SEO)are responsible for protecting the general public,the launch area, and US and foreign land massesfrom errant launch vehicle flight. In conjunctionwith Operations Support and Analysis (30SW/SEY and 45 SW/SEOE and SEOS) and Sys-tems Safety (SES), Mission Flight Control usesflight safety analysis and systems safety engi-neering products to develop and implement real-time mission rules and flight termination criteria tocontrol errant launch vehicle flight from launch to


1-9

impact of vehicles with suborbital trajectories or toorbital insertion for space launch vehicles.

1.3.7.3 Systems Safety, 45th Space Wing and30th Space Wing

Systems Safety, 45th Space Wing (45 SW/SES) and30th Space Wing (30 SW/SES) are responsible forensuring that public, launch area and launch com-plex safety and resource protection are adequatelyprovided by and for all programs using the Ranges.Responsibilities include:

a. Developing safety critical design and operatingcriteria and requirements

b. Reviewing and approving design, test, anddocumentation for airborne range safety systems.

c. Developing, enforcing, reviewing and approv-ing engineering design, test, and documentation forhazardous launch vehicle, payload, ground support

equipment, and facility systemsd. Reviewing, approving, monitoring, and classi-

fying (as public launch area or launch complexsafety) hazardous and safety critical operations

e. Providing safety engineering and developingprocesses and procedures to mitigate risks in-volved in prelaunch and launch operations for boththe general public and launch area

f. At the ER, overseeing Operations Safety andensuring they meet contract requirements

g. Operations Safety, a government contractorfor 45 SW/SES is responsible for reviewing for,monitoring for, and enforcing compliance throughRange Safety and/or the appropriate launch com-plex control authority, with this document andother Range Safety requirements by all personneloperating as Range Users or Support Agencies onthe ER, primarily during hazardous and safety

COMMANDER45TH SPACE WING(Range Commander)

RANGE SAFETY (SE)CHIEF OF SAFETY

GROUND SAFETY(SEG)

SYSTEMS SAFETY(SES)

MISSION FLIGHTCONTROL AND

ANALYSIS (SEO)

MISSION FLIGHTCONTROL (SEOO)

STS OPERATIONSSUPPORT AND

ANALYSIS (SEOS)

ELV OPERATIONSSUPPORT AND ANALYSIS

(SEOE)

Figure 1-5aEastern Range Safety Organization

COMMANDER30TH SPACE WING(Range Commander)

RANGE SAFETY (SE)CHIEF OF SAFETY

GROUND SAFETY(SEG)

SYSTEMS SAFETY(SES)

MISSION FLIGHTCONTROL (SEO)

FLIGHT ANALYSIS(SEY)

Figure 1-5bWestern Range Safety Organization


1-10

critical operations. The operations and responsi-bilities of this organization are similar to thoseperformed by 30 SW/SEGP on the WR.

1.3.7.4 Operations Support and Analysis, 45thSpace Wing, and Flight Analysis, 30th SpaceWing

Operations Support and Analysis, 45th Space Wing(45 SW/SEOE and SEOS) and Flight Analysis, 30thSpace Wing (30 SW/SEY) are responsible for de-veloping criteria for the control of errant vehicleflight to provide public safety. Responsibilities in-clude:

a. Approving all launch vehicle and payloadflight plans

b. Determining the need for flight terminationsystems

c. Establishing mission rules in conjunction with45 SW/SEOO and 30 SW/SEO and Range Users

d. Determining criteria for flight termination ac-tion

e. Assessing risks to protect the general public,launch area, and launch complex personnel andproperty

f. Identifying and evaluating risk reduction ac-tions such as evacuation, sheltering, and safetyholds for suitable meteorological conditions

g. Developing mathematical models to increasethe effectiveness of errant vehicle control whileminimizing restrictions on launch vehicle flight

h. In conjunction with Mission Flight Control,ensuring that Mission Flight Control Officers aretrained to perform errant launch vehicle control

i. Determining collision avoidance (COLA) re-quirements for mannable objects

1.3.7.5 Relationship with Range Users

Each of the Safety Office sections is responsiblefor initiating, establishing, and implementingRange User interface processes to ensure that therequirements of this document are met and, if de-sired, tailored to meet individual Range User pro-gram requirements. The interface process is de-scribed in the Range Safety and Range User In-terface Processes section of this Chapter.

1.3.8 Range Users and Supporting Agen-cies

Range Users and supporting agencies are responsi-ble for the following:

a. Providing safe systems, equipment, facilities,and materials in accordance with this document

b. Conducting their operations in a safe manner

that complies with and implements those portions ofthe Range Safety Program that are applicable totheir programs

c. Obtaining review and approval for the followingdocuments:

1. Tailored versions of EWR 127-1, as desired,System Safety Program Plans (SSPP), noncompli-ance requests, and Launch Complex Safety Trainingand Certification Plans (See Appendixes 1A, 1B,and 1C of this Chapter.)

2. Preliminary and Final Flight Data Packages(PFDP and FFDP), Aircraft and Ship Intended Sup-port Plans (ISPs), and Directed Energy Plans(DEPs) (See Chapter 2.)

3. Missile System Prelaunch Safety Package(MSPSP) (See Chapter 3 and Appendix 3A.)

4. Airborne Range Safety System Report(RSSR) (See Chapter 4 and Appendix 4A.)

5. Facility Safety Data Packages (FSDP) as re-quired for all critical facilities and launch com-plexes (See Chapter 5 and Appendix 5A.) and ex-plosive quantity distance site plans

6. Ground Operations Plans (GOP) and Haz-ardous and Safety Critical Procedures (See Chapter6 and Appendixes 6A and 6B.)

d. Submitting data for flight control operations,obtaining a Range Safety Launch Operations Ap-proval Letter or verbal approval at the LaunchReadiness Review, and participating in safety criti-cal operations (See Chapter 7.)

e. As applicable, ensuring compliance with theNational Aeronautics and Space Council documentNuclear Safety Review and Approval Procedure forMinor Radioactive Sources in Space Operations

f. As applicable, ensuring compliance withPresidential Directive/NSC 25 as outlined in DoDD3200.11 and AFI 91-110

g. As applicable, ensuring that the requirementsof PL 98-575 and DOT Office of CommercialSpace Transportation (OCST) 14 CFR, Chapter IIIare met


1-11

h. Performing risk analyses and implementingcontingency plans to protect the general public in theevent of a threat from de-orbiting launch vehicles.NOTE: DOT commercial licenses normally addressthese analyses for commercial programs.

i. Coordinating their safety programs with RangeSafety to ensure the activities of both organizationsmeet national policy goals and provide for publicand launch site safety and resource protection whileminimizing impact on mission requirements

j. Providing for crew safety in manned spacelaunch systems and coordinating crew safety policy,procedures, and activities with the Office of theChief of Safety

k. Verifying compliance with this document.NOTE: The use of subcontractors does not relievethe Range User of responsibility. The Range Usershall provide adequate contractual direction andmonitor subcontractor performance to verify com-pliance.

l. As applicable, when involved in joint proj-ects, interfacing and integrating with other RangeUsers or associated contractors in their safety pro-grams

1.4 RANGE SAFETY POLICYa. It is the policy of the Ranges to ensure that

the risk to the public, to personnel at the launcharea, and to national resources is minimized to thegreatest degree possible. This policy shall be im-plemented by employing risk management in threecategories of safety: Public Safety, Launch AreaSafety, and Launch Complex Safety.

b. The Range User shall endeavor to maintainthe lowest risk possible, consistent with missionrequirements, and in consonance with ER and WRlaunch risk guidance. NOTE: Individual hazard-ous activities may exceed guidance based on na-tional need after implementation of available cost-effective mitigation. The Launch Area Safetysection of this Chapter includes formulations forevaluating cost-effectiveness.

c. The Wing Commanders may vary from thiscriteria for particular programs or missions basedon geography, weather, and national need; how-ever, the basic standard is no more than that vol-untarily accepted by the general public in normalday-to-day activities.

d. Launch risk guidance has been establishedbased on a standard of a collective risk level of notmore than 30 casualties in 1 million (30 x 10-6) forthe general public and not more than 300 casual-

ties in 1 million (300 x 10-6) for essential launcharea personnel. The basic standard for the generalpublic is not more than the risk voluntarily ac-cepted in normal day-to-day activities. Furtherinformation on acceptable risk criteria may befound in Appendix 1D.

e. Imminent danger situations are subject to thefollowing:

1. Immediate action shall be taken by the su-pervisor or individual responsible for the immedi-ate area to correct the situation, apply interimcontrol measures, stop the operation, and evacuateall personnel.

2. Any operation, condition, or procedure thatpresents imminent danger shall be brought to theimmediate attention of the supervisor or individualresponsible for the immediate area.

3. All imminent danger situations shall be re-ported to Range Safety not later than 1 h from thetime the situation is identified.

4. Personnel may decline to perform assignedtasks because of a reasonable belief that, under thecircumstances, the task presents imminent danger,coupled with a reasonable belief that there is insuf-ficient time through normal reporting for abate-ment procedures to correct the situation.

1.4.1 Public SafetyThe Ranges shall strive to ensure that the risk tothe general public and foreign countries fromRange operations meets the criteria established inPL 60, Legislative History. Figure 1-6 shows therisk management criteria guidance to be used fordetermining acceptable risk for individuallaunches. The figure of 30 x 10-6 shall be used byboth Ranges as a level defining “acceptable launchrisk without high management (Range Com-mander) review.” Based on national need and theapproval of the Range Commander/Wing Com-manders, launches may be permitted using a pre-dicted risk above 30 x 10-6.

1.4.1.1 Prelaunch and Launch Operations

a. Range Safety shall review, approve, andthrough Operations Safety, monitor, and imposesafety holds when necessary, on all prelaunch andlaunch operations conducted on the Ranges to en-sure that the hazards associated with propellants,ordnance, radioactive material, and other hazardoussystems do not expose the general public to risksgreater than those considered acceptable by publiclaw and state documents, such as PL 99-499, 29


1-12

CFR 1910.119, 40 CFR 355, 40 CFR 68, ExecutiveOrder 12856, and CAL-OSHA.

b. Range Safety shall conduct and oversee launchvehicle, payload, mission flight control, and RangeSafety launch support operations to ensure that risksto the general public and foreign countries and theirproperty do not exceed acceptable limits consistentwith mission and national needs.

c. Range Safety shall ensure that each Range Userprovides each launch system with a capability thatallows Range Safety to initiate a hold-fire that pre-vents launch in the event of loss of Range Safetycritical systems or violation of mandatory RangeSafety launch commit criteria (Appendix 7A).

1. Safety holds shall be initiated to prevent thestart of a launch operation or to stop a launch op-eration that is already underway if it violates public,launch area, or launch complex safety or launchcommit criteria.

2. Safety holds may be called if Range Safetylaunch commit criteria are violated or if adequatesafety cannot be ensured or verified when personnelor resources are jeopardized.

3. Safety holds may be initiated by the Mis-sion Flight Control Officers, Operations SafetyManager, Range Control Officers, Range Opera-tions Commander (WR), Aerospace Control Offi-

cer (WR), Range User, or any responsible supervi-sor in charge of a launch operation.

1.4.1.2 Range Safety Critical Systems

Range Safety critical systems include all airborneand ground subsystems of the Range Safety System.The Range Safety System consists of airborne andground flight termination systems (FTSs), airborneand ground Range Tracking Systems (RTSs), andthe Telemetry Data Transmitting System (TDTS).

a. All Range Safety critical systems shall be de-signed to ensure that no single point of failure, in-cluding software, will deny the capability to moni-tor and terminate or result in the inadvertent termi-nation of a launch vehicle or payload, as applicable.

b. The reliability requirements of the RangeSafety System are as follows:

1. The overall airborne and ground FTS reli-ability goal is 0.9981 at the 95 percent confidencelevel.

(a) The airborne FTS reliability goal shall bea minimum of 0.999 at the 95 percent level. Thisgoal shall be met by combining the design approachand testing requirements of Chapter 4 of this docu-ment.

(b) The ground FTS shall have a reliability of0.999 at the 95 percent confidence level for a 4 h

(“From a Safety Standpoint they [missiles] will be no more dangerous than conventional airplanes flying over-head.” Legislative History, 81st Congress, pg. 1235)

Figure 1-6Acceptable Public Exposure Launch Operation Risk Guidance


1-13

duration, as required.2. The overall airborne and ground Range

Tracking System (RTS) reliability is a function ofthe following requirements:

(a) The airborne RTS reliability shall be0.995 at the 95 percent confidence level for trans-ponder systems and 0.999 at the 95 percent confi-dence level for global positioning systems. Thesegoals shall be met by combining the design ap-proach and testing requirements of Chapter 4 of thisdocument.

(b) The ground RTS reliability shall be 0.999at the 95 percent confidence level for a 1 h duration,as required.

3. There are no reliability requirements for theTDTS.

c. When possible, Range Safety critical systemsshall be designed to allow single failures in hard-ware and software and still provide overall systemredundancy.

d. Other systems determined to be Range Safetycritical shall have a design reliability of 0.999 atthe 95 percent confidence level.

1.4.1.3 Control of Errant Vehicle Flight

a. Range Safety shall verify that all launch vehi-cles launched from or onto the Ranges have apositive, range-approved method of controlling er-rant vehicle flight to meet the objective of mini-mizing risks to the general public and foreign coun-tries. NOTE: Normally, control systems on launchvehicles using the Ranges shall consist of an air-borne Range Safety System that shall meet all therequirements of Chapters 2, 4, and 7 of this docu-ment. A thrust termination system may be consid-ered as an alternative to a Range Safety System;however, quantification of risks must be deter-mined, and the requirements in Chapter 2 shall bemet. The alternative thrust termination concept anddesign shall be approved by the Range Commander.

b. Range Safety shall establish flight terminationcriteria and Range Safety mission flight rules toensure that operations do not exceed acceptablepublic safety limits.

c. Range Safety shall establish and control Haz-ardous Launch Areas and procedures to protect thepublic on land, on the sea, and in the air for eachlaunch and launch vehicle using the Ranges and toensure the following criteria are met:

1. No intact launch vehicle, scheduled debris, orpayload, or launch vehicle and payload subsystemsshall be allowed to intentionally impact on land ex-

cept in the launch area inside the impact limit lines.2. Flight paths and trajectories shall be designed

so that normal impact dispersion areas do not en-compass land.

3. Safety margins shall be used to avoid overlyrestrictive flight termination (destruct) limits.

d. Range Safety may allow errant launch vehi-cles to fly to obtain maximum data until theywould present an unacceptable risk to the public oruntil Range Safety can no longer control thelaunch vehicle.

1.4.2 Launch Area SafetyThe Ranges shall ensure that all personnel locatedon CCAS or VAFB or on any supporting site withinthe ER or WR are provided protection from thehazards associated with Range operations.

a. Table 1-1 shows nominal launch area andlaunch complex hazard consequence and probabilitycategories correlated to different levels of accept-ability for prelaunch hazards not associated withlaunch or Range Safety launch commit criteria.Numbers provided in Table 1-1 are guides only andare not necessarily hard limits.

b. Range Safety shall provide errant launch vehi-cle control protection for the launch area, includingCCAS, KSC, and VAFB.

c. Range Safety shall conduct risk studies andanalyses to determine the risk levels, define accept-able risk levels, and develop exposure criteria.

d. Range Safety shall establish design criteria andcontrols, procedures, and processes to minimizepersonnel risks and ensure acceptable launcharea/complex risk levels are not exceeded.

e. Range Safety shall evaluate all launch vehicle,payload, ground support, and facility systems usedon the Ranges to test, checkout, assemble, handle,support, or launch launch vehicles or payloads withregard to their hazard potential and ensure they aredesigned to minimize risks to personnel and fallwithin acceptable exposure levels.

f. Range Safety shall ensure that all hazardous op-erations affecting launch area safety are identifiedand conducted using Range Safety approved formalwritten procedures. Through Operations Safety,Range Safety shall ensure launch area safety is pro-vided in accordance with this document and ap-proved Operations Safety Plans.

g. Range Safety shall define the threat envelopeof all hazardous operations affecting launch areasafety and establish Safety Clearance Zones to pro-tect personnel and resources. NOTE: A minimum


1-14

number of personnel shall be exposed to the mini-mum hazard level consistent with efficient task ac-complishment.

h. Range Safety shall ensure all personnel per-forming hazardous operations that may impactlaunch area safety are provided adequate training toensure proper conduct of their jobs and tasks by

reviewing Range User training plans.i. Launch Area Resource Protection

1.The Ranges shall ensure that launch areaphysical resources are provided an acceptable de-gree of protection based on federal law and nationalstandards.

2. Procedures and policies that are applied forpublic and launch area safety shall be used to reducerisks to launch area physical resources to acceptablelevels.

3. Siting, design, and use of physical resourcesshall consider potential hazards and threat enve-lopes to ensure that damage exposure is limited toacceptable levels as defined by federal law andnational consensus standards.

Table 1-1Acceptability Guidelines for Prelaunch Launch Area/Launch Complex Hazard Consequences

and Probability CategoriesHAZARD SEVERITY POTENTIAL CONSEQUENCES PROBABILITY*

CategoryPersonnel

Illness/InjuryEquipment

Loss($)Unit

DowntimeData

Compromise A B C D EI Catastrophic May cause death. > 1,000,000 > 4 months Data is never recoverable or

primary program objectives arelost.

��

��

��

��

��

II Critical May cause severeinjury or severe occu-pational illness.

200,000to

1,000,000

2 weeksto

4 months

May cause repeat of test pro-gram.

��

��

��

��

III Marginal May cause minorinjury or minor occu-pational illness.

10,000to

200,000

1 Dayto

2 Weeks

May cause repeat of test pe-riod.

��

��

��

IV Negligible Will not result in injuryor occupational illness.

< 10,000 < 1 Day May cause repeat of data point,or data may require minor ma-nipulation or computer rerun.

RISK PRIORITY:

�� Unacceptable

�� Waiver or deviation required Operation permissible

*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

LEVELPROBABILITY

VALUE SPECIFIC INDIVIDUAL ITEM FLEET OR INVENTORY***A Frequent 3X10-1 Likely to occur repeatedly Continuously experienced----------------------- 8X10-2 -----------------------------------------------------------------------------------------------------------------------------B Reasonably

probable3X10-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 Im-

probable3X10-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.


1-15

1.4.3 Launch Complex SafetyThe single commercial user, full-time governmenttenant organization or USAF squadron/detachmentcommander, as the control authority has the re-sponsibility for launch complex safety and willexercise the function in accordance with theLaunch Complex Safety Training and Certificationrequirements. The control authority has the optionof delegating this responsibility to the Chiefs ofSafety. NOTE: The control authority for safety asdefined in this document includes areas within acomplete launch complex (or missile silo) and ad-jacent facilities used by each agency for launchvehicle and/or payload processing. In all cases, theChiefs of Safety shall review and approve all haz-ardous operating procedures and any other proce-dures that Range Safety may review to insure suchoperations do not pose or create a hazardous con-dition.

1.4.3.1 General Requirements

a. Regardless of whether the control authority orRange Safety takes responsibility for launch com-plex safety, the following general requirementsapply:

1. Range Safety shall provide errant launchvehicle control protection for the launch area, in-cluding CCAS, KSC, and VAFB and all launchcomplex locations therein.

2. Range Safety shall conduct risk studies andanalyses to determine and define launch complexacceptable risk levels and develop exposure crite-ria.

3. Range Safety shall establish design criteriaand controls, procedures, and processes to mini-mize launch area and launch complex personnelrisks and ensure acceptable risk levels are not ex-ceeded.

4. Range Safety shall evaluate all launch ve-hicles, payloads, ground support, and facility sys-tems used on the Ranges to test, checkout, assem-ble, handle, support, or launch vehicles or pay-loads with regard to their hazard potential and en-sure they are designed, tested, and maintained tominimize risks to launch complex personnel andfall within acceptable exposure levels.

b. If the control authority assumes responsibilityfor launch complex safety, the following generalrequirements apply:

1. As requested, Range Safety shall providetechnical advice, requirements interpretation, andsafety guidance to the control authority for launch

complex safety issues.2. Range Safety shall audit launch complex

hazardous and safety critical procedures to ensurecompliance with this document.

1.4.3.2 Launch Complex Safety Responsibility

The organization responsible for launch complexsafety, either Range Safety or the launch complexcontrol authority (AF Squadron Commanders forAF programs), is subject to the following require-ments:

a. Hazardous Operations1. If requested by the control authority,

Range Safety shall ensure that all hazardous op-erations affecting launch complex safety are con-ducted using Range Safety approved formal writ-ten procedures. Through Operations Safety, RangeSafety shall ensure launch complex safety is pro-vided in accordance with this document and ap-proved Operations Safety Plans.

2. If assuming responsibility, the controlauthority shall ensure that all hazardous operationsaffecting launch complex safety are conductedusing formal written procedures approved by aspace safety professional. In accordance withLaunch Complex Safety Training and CertificationRequirements, the control authority shall ensurelaunch complex safety is provided in accordancewith this document and approved OperationsSafety Plans.

b. Either the control authority or Range Safety,if requested, shall define the threat envelope of allhazardous operations affecting launch complexsafety and establish Safety Clearance Zones toprotect launch complex personnel and resources.NOTE: A minimum number of personnel shall beexposed to the minimum hazard level consistentwith efficient task accomplishment.

c. Either the control authority or Range Safety,if requested, shall ensure all personnel performinghazardous operations that may impact launchcomplex safety are adequately trained to performtheir jobs and tasks.

d. Either the control authority or Range Safety,if requested, shall ensure that adequate personalprotective equipment is provided as defined bythis document and approved Operations SafetyPlans.

e. The areas and facilities for which the controlauthority has responsibility for launch complexsafety are available from the Range Safety Offices.

f. Launch Complex Resource Protection


1-16

1. The Ranges and control authorities shallensure that launch complex physical resources areprovided an acceptable degree of protection basedon federal law and national consensus standards.

2. Procedures and policies that are applied forpublic, launch area, and launch complex safetyshall be used to reduce risks to launch complexphysical resources to acceptable levels.

3. Siting, design, and use of physical re-sources shall consider potential hazards and threatenvelopes to ensure that damage exposure is lim-ited to acceptable levels as defined by federal lawand national consensus standards.

4. Launch complex resource protection issuesshall be coordinated between Range Safety and theaffected Range Users.

(a) USAF squadron or detachment Com-manders shall be responsible for implementingresource protection requirements for all DoD flighthardware, ground support equipment, and facilitieswithin their assigned areas.

(b) US Navy, NASA, and other governmenttenant organizations shall be responsible for alltenant-occupied facilities and tenant-ownedequipment.

(c) The CCAS Commander shall be respon-sible for implementing of resource protection re-quirements for an area on CCAS not assigned to aspecific USAF squadron or detachment com-mander or other Range User.

(d) Commercial Range Users shall be re-sponsible for commercially owned, leased, or li-censed physical resources

1.4.3.3 Launch Complex Safety Training andCertification Requirements

The control authority shall implement a LaunchComplex Safety Training and Certification Plan inaccordance with the Launch Complex SafetyTraining and Certification Requirements availablefrom the Range Safety Offices. This process in-cludes the following steps:

a. Range Safety and the control authorityjointly tailor the subject document.

b. The control authority submits a plan to com-ply with the subject document.

c. Range Safety reviews and approves the plan.d. The complex control authority safety plan

shall include qualification and certification docu-mentation of personnel performing the safetyfunction for review and approval by the Chiefs ofSafety.

e. Range Safety shall audit launch complexsafety procedures and processes as necessary.

1.5 SAFETY AUTHORIZATIONS,COMPLIANCES, AND

DOCUMENTATION1.5.1 Purpose of Obtaining Safety Approvals

a. To operate, use, and launch launch vehiclesand payloads from or onto the Ranges, specificmandatory safety approvals shall be obtained toshow compliance with and meet the requirementsof the Ranges.

b. Commercial users providing launch servicesshall have a license approved by the Federal Avia-tion Administration/Associate Administrator forCommercial Space Transportation (FAA/AST) inaccordance with 14 CFR Chapter III and meet therequirements of PL 98-575.

1.5.2 Authorizationsa. Programs launching from only the ER or WR

shall obtain authorizations from the appropriate 45SW or 30 SW authority.

b. Programs launching from both the ER and WRshall obtain authorizations for common require-ments from appropriate 45 SW and 30 SW authori-ties.

c. Unique requirements shall require authoriza-tions from the appropriate 45 SW or 30 SW author-ity.

d. In general, if a program is approved at the ERor WR, it will be approved at the other withoutfurther review with the exception of ER or WRspecific requirements identified in this document,design or operational changes to the program dueto the change of processing location (a new GOPand hazardous procedures are normally alwaysrequired), and the exceptions identified in items athrough g of the Status of Previously ApprovedPrograms section of this Chapter.

1.5.2.1 Safety Approvals Authorized by theWing Commanders

The following safety approvals shall be authorizedby the Wing Commanders:

a. Tailored versions of EWR 127-1 affectingpublic safety

b. Range Safety mission flight rules, includingtermination (errant vehicle control) criteria for alllaunch vehicles

c. Range Safety launch commit criteria for alllaunch vehicles


1-17

d. The launch of launch vehicles containing ex-plosive warheads

e. The launch of nuclear payloadsf. Noncompliances affecting public safety

1.5.2.2 Safety Approvals Authorized by theChief of Safety or a Designated Representative

The following safety approvals shall be authorizedby the Chief of Safety or a designated representa-tive:

a. Tailored versions of EWR 127-1 not affectingpublic safety

b. Noncompliances not affecting public safetyc. System Safety Program Pland. Launch Complex Safety Training and Certifi-

cation Plane. Preliminary and Final Flight Data Packagesf. Aircraft and Ship Intended Support Plansg. Directed Energy Plansh. Missile System Prelaunch Safety Packagei. Airborne Range Safety System Reportj. Hazardous and Safety Critical Proceduresk. Facilities Safety Data Packagel. Range Safety Launch Operations Approval

Letterm. Final Range Safety Approval for Launchn. Range Safety instrumentation, tracking, data,

and display requirements for all launch vehicleso. Range Safety Operations Requirements

1.5.2.3 Launch Complex Safety ApprovalsAuthorized by Control Authorities

Control authorities may approve hazardous andsafety critical procedures associated with launchcomplex safety in accordance with Launch Com-plex Safety Training and Certification Require-ments.

1.5.2.4 Safety Approvals Authorized by theDoD Explosive Safety Board

Explosive site plans require the signature of amember of the DoD Explosive Safety Board(DDESB).

1.5.3 Radioactive Material LaunchesAll Range Users shall notify Range Safety of anyintended launch of radioactive materials during theconcept phase of the program.

1.5.3.1 National Aeronautics and Space Coun-cil Compliance

As applicable, all Range Users shall certify com-pliance with the National Aeronautics and Space

Council (NASC) document, Nuclear Safety Re-view and Approval Procedures for Minor Radio-active sources in Space Operations, dated 16 June1970. Range Users may use their own agencyequivalent document if it meets the requirementsof the NASC document. Detailed information andprocedures are in Chapter 3.

1.5.3.2 Presidential Directive/National SecurityCouncil 25 Compliance

As applicable, all Range Users contemplatinglaunch of a major radioactive source shall complywith PD/NSC 25 as outlined in DoDD 3200.11and AFI 91-110. Detailed information and proce-dures are in Chapters 2 and 3.

1.5.3.3 Radioactive Material Launch Approval

All Range Users shall certify and show proof toRange Safety that they have obtained launch ap-proval for radioactive materials. Detailed informa-tion and procedures are in Chapters 2 and 3.

1.5.4 Documentation and Activity Require-ments

Chapters 2 through 7 of this document haveDocumentation Requirements sections. Thesesections describe the documents that shall be sub-mitted and the processes that shall be used to ob-tain the necessary approvals to launch from theRanges. In addition, appendixes in Chapters 2, 3,4, 5, and 6 provide detailed document content re-quirements that shall be met for some, but not allrequired documents. All other documentationnoted in the specific chapters shall also be ap-proved as indicated in the respective chapters.NOTE 1: While developing the documentationrequirements, Range Users are encouraged to workclosely with Range Safety to facilitate the ap-proval process. NOTE 2: The Range User Hand-book provides additional helpful information re-garding documentation requirements.

1.5.4.1 Tailored EWR 127-1, System SafetyProgram Plan, Noncompliance Requests, andLaunch Complex Safety Training and Certifica-tion Plan

a. If desired, a Range User and Range Safetyjointly tailored EWR 127-1 may be developed.(See Appendix 1A for further information.)

b. A Systems Safety Program Plan (SSPP) shallbe approved within 45 days of any program cDR.(See Appendix 1B for further information.)

c. Noncompliance requests shall be submitted


1-18

for all identified noncompliances to this document.(See Appendix 1C for further information.)

d. If a control authority desires to assume launchcomplex safety responsibility, a Launch ComplexSafety Training and Certification Plan shall beapproved prior to assumption of this responsibil-ity.

1.5.4.2 Flight Data Packages, Intended Sup-port Plans, and Directed Energy Plans

a. The PFDP and FFDP shall be approved priorto support final Launch Readiness Reviews (LRRs).

b. ISPs shall be approved prior to the LRR.c. DEPs shall be approved prior to the LRR.d. PFDP, FFDP, ISP, and DEP content require-

ments may be found in Chapter 2.

1.5.4.3 Missile System Prelaunch SafetyPackage

a. The MSPSP including design documentation,initial test plans and test reports, and recertificationrequirements for all hazardous and safety criticallaunch vehicle and payload systems, ground supportequipment, facilities, their interfaces, and operationsshall be approved prior to hardware arrival and/oruse at the Ranges. NOTE: The National Aeronauticsand Space Administration (NASA) is responsible forproviding review and approval for potential hazard-ous systems and activities on KSC, except for launchvehicle flight safety, which is the responsibility ofthe ER.

b. Content and submittal requirements for theMSPSP can be found in Chapter 3 and Appendix3A.

1.5.4.4 Airborne Range Safety System Report

a. The airborne RSSR, including all designdocumentation and test plans and test reports forthe FTS, RTS, and TDTS shall be approvedprior to launch.

b. Content and submittal requirements can befound in Chapter 4 and Appendix 4A.

1.5.4.5 Ground Operations Plan and Hazard-ous and Safety Critical Procedures

a. The GOP shall be approved prior to the startof operations at the Ranges.

b. Content and submittal requirements for theGOP can be found in Chapter 6 and Appendix 6A.

c. Hazardous and safety critical procedures shallbe approved by Range Safety prior to their use atthe Ranges.

d. Content and submittal requirements for Haz-

ardous and Safety Critical Procedures may befound in Chapter 6 and Appendix 6B.

1.5.4.6 Facilities Safety Data Package

a. The FSDP shall be approved prior to facilityuse.

b. Content and submittal requirements for theFSDP may be found in Chapter 5 and Appendix5A.

1.5.4.7 Launch Operations Approval

a. WR. A Range Safety Launch Operations Ap-proval Letter to launch from or onto the WR shallbe provided to the Range User no later than thescheduled LRR conducted prior to a plannedlaunch operation. Receipt of this letter depends onthe Range User having obtained the previouslyrequired approvals described in this Chapter.

b. ER. Launch Operations Approval Letters arenot normally used on the ER. Wing Safety’s GO atthe LRR constitutes approval to launch and iscontingent upon the Range User having obtainedthe required approvals identified in this Chapter.However, a Range Safety Launch Operations Ap-proval Letter can be provided, if requested.

c. Lack of Launch Operations Approval may re-sult in the launch being withdrawn from the Rangeschedule.

1.5.4.8 Final Range Safety Approval to Launch

a. Holdfire checks, Range Safety System checks,and other safety critical checks shall be performedsatisfactorily; environmental conditions shall bemet; and all Range Safety launch commit criteriashall be “green” prior to final approval to launch.

b. Given that holdfire checks, Range SafetySystem checks, other safety critical checks, and


1-19

environmental conditions are satisfactory and allRange Safety launch commit criteria are “green,”Range Safety shall provide a final approval tolaunch as follows: At the ER, the Chief of Safetyprovides approval by relaying the MFCO,“CLEAR TO LAUNCH.” At the WR, the MFCOissues a GREEN to go electronically and a verbalcall “Safety is sending a green.”

1.6 RANGE SAFETY AND RANGEUSER INTERFACE PROCESS

The complexity of present space programs and theinevitable cost of changes in hardware and impacton time schedules can be reduced by joint RangeSafety and Range User planning. The goal of theinterface process is to provide final Range Safetyapprovals for launch as early as possible. RangeUsers are strongly encouraged to solicit RangeSafety participation in the development of Re-quests for Proposals, source selection processes,and development of contract documents such asStatements of Work and Contract Data Require-ments Lists.

It is not the intent of this document or the interfaceprocess to stifle ingenuity, new technology, state-of-the-art development, or unique solutions tosafety problems. Instead, the interface process en-sures that both Range Safety and Range Users un-derstand the requirements of this document andreach mutual agreement on compliance methodsearly in the program.

1.6.1 Range Safety FundingRange Users and supporting agencies are respon-sible for full funding of activities associated withRange Safety support early in and throughout theprogram in accordance with funding requirementsof DoDD 3200.11, AFR 80-29, AFI 99-110 at theER and WR and 45 SWI 99-101 at the ER with thefollow-on funding for each fiscal year to be re-ceived at the start of each fiscal year. Programsintending to perform launch operations at both theER and WR shall fund both Ranges.

At the ER, Range Safety will provide cost esti-mates in accordance with 45 SWI 99-101 to helpRange Users estimate funding requirements.

1.6.2 Initial Range Safety and Range UserTechnical Interchange Meeting

Range Users shall contact Range Safety to arrangean initial Technical Interchange Meeting (TIM)during the concept phase of a program. The pur-

pose of this meeting is to present program con-cepts regarding flight plans; launch complex se-lection; launch vehicle, payload, and ground sup-port equipment; range safety system; and facilitydesign, operations, and launch complex safety re-sponsibility to determine if there are any majorsafety concerns that could impact the program.

This TIM may occur at anytime but should be nolater than the formal Program Introduction in ac-cordance with the Universal Documentation Sys-tem and, at the ER, 45 SWI 99-101. The cost of theinitial interface meetings will not be charged to theRange User as long as the workload associated withthis activity is insignificant in scope.

1.6.3 Tailoring ProcessIf desired by the Range User, Range Safety and theRange User shall jointly develop a tailored editionof this document for the program. The purpose oftailoring the document is to ensure that only appli-cable or alternative Range User requested equiva-lent requirements are levied upon the program andthat Range Safety requirements are levied in themost efficient manner possible.

a. Requirements in this document are subject totailoring within limits, including detailed design,operating, and documentation submission require-ments. Details of the tailoring process can be foundin Appendix 1A.

b. Tailoring, if desired, should begin at the earli-est opportunity and finish no later than the criticaldesign review.

1.6.4 Other Range Safety and Range UserTechnical Interchange Meetings andReviews

Range Users and Range Safety shall jointly agree toarrange the following TIMs and reviews as neces-sary:

a. Flight Safety TIMs (PFDP-, FFDP-related,Chapter 2)


1-20

b. As required, combined or independent safetyreviews in association with the Concept Design Re-view (cDR), Preliminary Design Review (PDR),and Critical Design Review (CDR) for launch vehi-cle, payload, and associated ground support equip-ment design (MSPSP-related, Chapter 3), airborneRange Safety System and associated ground supportequipment design (RSSR-related, Chapter 4), criti-cal facility design (FSDP-related, Chapter 5), andground operations plans (GOP-related, Chapter 6)

1. cDRs shall provide design and operationsdetail to at least the system level.

2. PDRs shall provide design and operationsdetail to at least the subsytem and box level.

3. CDRs shall provide design and operatingdetail to the component and piece part level.

c. Hazardous and Safety Critical ProceduresTIMs (Chapter 6)

d. Other TIMs, reviews, and meetings as neces-sary

1.6.5 Noncompliance With the Require-ments

Range Users are responsible for identifying allnoncompliances with this document to RangeSafety for resolution. The three types of noncom-pliances are meets intent certifications (MICs),deviations, and waivers. Details and requirementsfor submitting noncompliance requests can befound in Appendix 1C.

1.6.5.1 Meets Intent Certification

MICs are used when Range Users do not meet ex-act EWR 127-1 requirements but do meet the in-tent of the requirements. Rationale for equivalentsafety shall be provided. NOTE: MICs are nor-mally incorporated during the tailoring process.

1.6.5.2 Deviations and Waivers

Deviations and waivers to the requirements of thisdocument are used when the mission objectives ofthe Range User cannot otherwise be achieved.NOTE 1: Many previously approved waiverswould be classified as deviations based on thedefinition below. NOTE 2: Programs using earliereditions of the document will continue to holdwaiver approvals; new documentation is not re-quired.

1.6.5.2.1 Deviations. Deviations are used whena design noncompliance is known to exist prior tohardware production or an operational noncompli-ance is known to exist prior to beginning opera-

tions at the Ranges.

1.6.5.2.2 Waivers. Waivers are used when,through an error in the manufacturing process orfor other reasons, a hardware noncompliance isdiscovered after hardware production, or an op-erational noncompliance is discovered after opera-tions have begun at the Ranges.

1.6.5.2.3 Deviation and Waiver Policy.a. It is the policy of the Ranges to avoid the use

of deviations and waivers except in extremely raresituations, and they are granted only under uniqueand compelling circumstances. Range Safety andthe Range User shall jointly endeavor to ensure thatall requirements of this document are met as early inthe design process as possible to limit the number ofrequired deviations and waivers to an absoluteminimum.

b. Individually, the Range Commanders havethe authority to change, deviate from, or waive anyrequirement in this document for a specific programor mission operating at the respective launch area.Each Range Commander has the authority to acceptrisks that exceed those defined in Table 1-1 for aspecific mission based on national or mission need.

1. Rationale for national need or mission re-quirements shall be explained.

2. Acceptable risk mitigation and "get well"plans shall be provided since they are an integralpart of the basis for approval.

c. When granted, deviations and waivers arenormally given for a defined period of time or agiven number of missions until a design or opera-tional change can be implemented.

1.6.6 System Safety Program Require-ments

Range Users shall develop and maintain a SystemSafety Program in accordance with Appendix 1Bof this Chapter. An SSPP shall be submitted toRange Safety for review and approval.

1.7 RANGE SAFETY CONCEPT TOLAUNCH PROCESS

The overall Range Safety process from "concept tolaunch" for new launch vehicles is shown in Figure1-7. This process is tailorable to apply to payloads,ground support equipment, critical facilities, and/orhazardous and safety critical operations. The toprow of boxes represents the subprocesses for estab-lishing the program concept and applicable RangeSafety requirements per this Chapter. The second


1-21

row of boxes represents the subprocesses for analy-sis, design and test for the program per Chapters 2-5of this document. The third row of boxes representsthe subprocesses for operations and launch at theRanges per Chapters 6 and 7 of this document. De-tails of the steps of this process can be found in thisChapter and Chapters 2 through 7 of this documentas indicated. In addition, the Range User Handbookdescribes this process in greater detail. NOTE: Ap-pendix 1F contains a detailed tailored version ofthis process specifically developed for genericpayloads and payload buses.

1.7.1 Range Safety MilestonesRange Safety milestones are those events that shalloccur for Range Safety to approve a program dur-ing the "concept to launch" cycle. The contents ofthe document, 45 SW/SE and 30 SW/SE responsi-bilities and authorities, required meetings and ac-tivities, documentation, and approvals, have beenaddressed earlier in this Chapter.

1.7.2 Time Frames and SchedulesTime frames and event schedules vary dependingupon the complexity of the program. Figure 1-7time frames provide a general schedule of eventsas guidance for new, major launch vehicle pro-

grams. For smaller vehicles and payloads, thesetime frames can be compressed to a year or less.Time frame requirements for Range Safety and theRange Users throughout the document are base-lines for all programs; however, they may be al-tered during the tailoring process.

1.8 CHANGES TO APPROVEDGENERIC SYSTEMS

a. Once baseline or generic launch systems, in-cluding launch vehicles, payloads, ground supportequipment, RSSs, and critical facilities have beenapproved, only those systems and subsystems thatchange shall be submitted to Range Safety for re-view and approval. NOTE 1: The approval proc-ess remains the same as described above and issubject to the requirements in the Situations Re-quiring Reevaluation of Previously ApprovedPrograms section of this Chapter. NOTE 2: Ap-

Figure 1-7Range Safety “Concept to Launch” Process


1-22

pendix 1F provides a tailored process for the ap-proval of generic payloads.

b. Documentation shall be marked or labeled as"Mission Unique," "Upgrade," "Change," or“Other” to the previously approved system andshall be prepared in such a manner to allow easyreference to previously approved submittals.

1.9 CHANGES TO EWR 127-1This document shall normally be updated at leastonce every four years; however, it may be updatedonce a year. If circumstances warrant, revisions maybe made on a chapter-by-chapter basis within thesetime constraints.

a. Permanent changes to EWR 127-1 shall beperformed in accordance with the requirements inAppendix 1E.

b. Changes requiring immediate attention, such asthose based on a previously unknown risk or safetycompromise, shall be made as necessary and dis-tributed as EWR 127-1 Change Notices.

c. Change Notices shall be coordinated betweenthe ER and WR, and all affected Range Users shallbe notified.

1.10 INVESTIGATING ANDREPORTING MISHAPS AND INCIDENTS

1.10.1 Mishaps and Incidents Involving AirForce Personnel and Resources

In accordance with AFI 91-204, the Ranges shallinvestigate and report all mishaps involving AirForce personnel and resources.

1.10.2 Non-Air Force Personnel and Re-sources

a. The ER and the WR will not report or investi-gate non-Air Force mishaps under AFI 91-204 aus-

pices. However, Range Safety may assist and par-ticipate in non-Air Force mishap investigations thataffect or could affect operations on the Range, pub-lic safety, launch area safety, launch complexsafety, or resource protection.

b. Range Safety shall be provided with the in-vestigation results of any mishaps or incidents oc-curring on the Ranges.

c. Regardless of the Range User, the RangeCommander may conduct formal investigationsinto any mishap and incident that affects or couldaffect public, launch area safety, or launch com-plex safety.

1.11 RANGE SAFETY RANGE USERHANDBOOK

A Range Safety Range User Handbook is avail-able to all Range Users. This handbook providesinformational tools to help Range Users achievethe Range Safety “concept to launch” process inthe most efficient manner possible. Contact theRange Safety Office to obtain a copy or downloadthe handbook from the Range Safety web site.

1.12 RANGE SAFETY WEB SITE

The Range Safety web site is a tool for noti-fying the Range User community of issuespertaining to Safety, including changes toEWR 127-1, and for distributing the variouseditions of 127-1. The 1997 and subsequenteditions will be distributed primarily via theweb site. The address (subject to change) is asfollows:http://www.patrick.af.mil/45sw/rangesafety

/45swse.htmAccessing through the 45th Space Wing HomePage (http://www.patrick.af.mil/) requires click-ing on “Wing Staff,” then selecting “RangeSafety” (subject to change). Questions and com-ments can be sent via e-mail [email protected].

Chapter 1: Eastern and Western Range Safety Policies and Processes 31 December 1999 Change to 1997 EWRAPPENDIX 1A

1.2 1.2 THE EWR 127-1 TAILORING PROCESS

1-23

1A.1 INTRODUCTION1A.1.1 PurposeTailoring provides a means for formulating a spe-cific edition of the document incorporating onlythose requirements that apply to a particular RangeUser program. A tailored version of the document isdenoted as EWR 127-1 [T]. Programs that launchfrom only the ER or WR shall be tailored by theappropriate 45 SW/SE or 30 SW/SE section. Pro-grams that intend to launch from both Ranges shallbe tailored by a combined 45 SW/SE and 30SW/SE team.

1A.1.2 ContentThis Appendix describes the rationale for tailoring,the tailoring process, and the requirements fordocumenting tailored editions of the document.

1A.1.3 ApplicabilityThe tailoring process is applicable to all programs(boosters, solid rocket motors, upper stages, pay-loads, associated ground support equipment andfacilities). The tailoring process is optional for newprograms, and existing programs where RangeSafety and the Range User agree this processwould be effective.

1A.1.4 Formation of a High PerformanceWork Team

A high performance work team (HPWT) shall beformed to perform tailoring during Technical Inter-change Meetings (TIMs). HPWT Membershipshall include Range User and Range Safety per-sonnel who have specific tailoring authority.

1A.1.5 Tailoring RationaleTailoring shall be accomplished based on the fol-lowing rationale:

1A.1.5.1 Deletion of a Requirement

a. When a requirement is not applicable to aRange User Program, the requirement shall be de-leted.

b. The original paragraph number and headingsshall remain, but the non-applicable text shall beremoved and replaced with the abbreviation N/A.

1A.1.5.2 Change to a Requirement.a. MICs may be provided by the High Perform-

ance Work Team through the change process; how-ever, the High Performance Work Team cannotprovide deviation or waivers.

b. A change is allowed to tailor the requirementto a particular system as long as the intent of therequirement is met and the equivalent level ofsafety is maintained.

c. The change shall be written in the place of theoriginal requirement.

d. The existing numbering system shall remainthe same to the maximum extent possible.

e. Additional paragraphs may be added; however,using the remaining unaffected paragraph numbersis not allowed.

f. All changes shall be highlighted in bold.

1A.1.5.3 Addition to a Requirement

a. An addition to a requirement is allowed whenthere are no existing requirements addressing newtechnology, when unforeseen hazards are discov-ered, when federal or industry standards change,and for similar reasons.

b. An addition shall be added with new paragraphnumbers in the section for which it is appropriate orin a new section if no other section applies.

c. All additions shall be highlighted by under-line.

1A.1.5.4 Range User Information Only

a. Requirements having only an indirect effect onthe Range User but which are still required of theprogram as a whole shall remain in the tailoreddocument as information only. Examples of suchrequirements include Operations Safety responsi-bilities, other Range Contractor responsibilities, andRange User facilities manager responsibilities.

b. All "Range User Information Only" require-ments shall be highlighted with an asterisk prior tothe affected paragraph number.

1A.1.5.5 Deviations and Waivers

Deviations and waivers are not rationale for thedeletion of requirements. The requirements shall


APPENDIX 1A1.1 1.1 THE EWR 127-1 TAILORING PROCESS

1-24

remain in the EWR 127-1 [T] and the deviationand waiver process shall be used for the dispositionof the requirement.

1A.1.5.6 Risk-Cost Benefit Analysis

a. Technical issues regarding such items as appli-cable requirements, policy, criteria, or data may beevaluated on a risk-cost benefit basis to determine ifthe risk is acceptable to deviate from or waive therequirements.

b. A risk-cost benefit analysis, based on the crite-ria defined in Figure 1-6 and Table 1-1 of thisChapter shall be submitted to Range Safety.

c. Based on risk-cost benefit analysis data, RangeSafety and the Range User shall reach agreement onthe disposition of the requirement in question.

d. If the application of an EWR 127-1 require-ment results in significant reduction of risk at asignificant cost benefit, it may be judged by RangeSafety to be sufficient to impose the requirement;however, if the benefit is insignificant and/or thecost is high, the requirement may be deviated from,waived, or determined to meet the intent, all withconsideration for public safety.

1A.1.6 Scheduling Technical InterchangeMeetings

a. TIMs are required for Range Users to presenttheir systems to Range Safety and to participate inthe active tailoring of the document.

b. TIMs shall be scheduled as early in the programas possible when program definition is sufficient tomake the meetings worthwhile and structured so thattechnical tailoring is completed before contractual tai-loring (word smithing) is started.

c. EWR 127-1 [T] TIM data shall be provided toRange Safety at least 30 days prior to scheduledTIMs.

1A.2 TAILORING PROCESS1A.2.1 Preparation of an Optional Draft Edi-

tion of EWR 127-1a. If desired, the Range User and/or Range Safety

may produce an optional draft edition of EWR 127-1 Tailored [T] based on conceptual data and meet-ings.

b. The purpose of a draft EWR 127-1 [T] is toeliminate all non-applicable requirements, leavingonly applicable requirements from which detailedtailoring can be performed.

c. The draft EWR 127-1 [T] shall be delivered as

soon as possible and is negotiable.

1A.2.2 Generation of Tailoring Requestsa. EWR 127-1 [T] Tailoring Requests shall be

used to document proposed EWR 127-1 [T] dele-tions, changes, and additions.

b. Tailoring Requests should be completed priorto scheduled TIMs and submitted to Range Safetyfor review or they may be completed during TIMs.NOTE: An example is in the Range User RangeSafety Handbook.

c. The forms for submitting Tailoring Requestsmay be found in the Range User Handbook.

d. A matrix-type format, containing the sameinformation as the Tailoring Request form, may beused as an alternative if mutually agreeable to theRange User and Range Safety.

1A.2.2.1 Completing Tailoring Requests

a. The original EWR 127-1 paragraph number,original (or summarized, if sufficiently detailed)text, tailored paragraph number, proposed text, andthe rationale for the change shall be included.

b. Deletions of requirements that are non-applicable and need no formal explanation may allbe listed on one or more Tailoring Request forms.

c. Tailoring Requests dealing with similar orrelated requirements and rationale may all becombined on the same Tailoring Request form.

1A.2.2.2 Disposition of Tailoring Requests

a. If necessary, Range Safety will comment onthe proposed change and dispose of it as "approvedas written," "approved with provided comments,"or "disapproved."

b. When agreement is reached and a TailoringRequest approved, Range Safety and Range Userrepresentatives shall sign and date the form.

1A.2.3 Publication of EWR 127-1 [T]1A.2.3.1 Final Publication

a. The goal for final publication of an EWR 127-1 [T] is as soon as possible, but should be no laterthan 30 days after the PDR.

b. In some cases, it may be necessary to com-plete the EWR 127-1 [T] as part of the contractingprocess or at some other point prior to the PDR. Inthese cases, Range Safety will work with theRange User to establish and meet a completiondate for EWR 127-1 [T] publication.


APPENDIX 1A1.3 1.3 THE EWR 127-1 TAILORING PROCESS

1-25

1A.2.3.2 Identification of EWR 127-1 [T]

a. Each EWR 127-1 [T] shall be given a uniquetitle and each header of each page of the EWR 127-1[T] shall indicate the edition is a tailored edition ofEWR 127-1.

b. Even page headers shall incorporate the title ofthe program, the edition number, and the date (EWR127-1 Tailored for XXX Program, Edition X, Date).

c. Odd page headers shall incorporate thetitle of the chapter and the chapter number (East-ern and Western Range Policies and Processes,Chapter 1 [T].

1A.2.3.3 Effectivity of EWR 127-1 [T]

a. Each EWR 127-1 [T] shall contain a prefaceparagraph detailing its effectivity.

b. At a minimum, the types of vehicles, the timeperiod, and the number of vehicles to which theEWR 127-1 [T] applies shall be addressed.

1A.2.3.4 Assumptions

a. Each EWR 127-1 [T] shall contain a prefaceparagraph detailing the critical assumptions thatwere made in writing the tailored edition.

b. The nature of the assumptions shall be such thata change may invalidate the EWR 127-1 [T] or re-quire a change or update. An example of such a criti-cal assumption is that the design of any hazardoussystem does not change from that presented prior topublication of the EWR 127-1 [T].

1A.2.3.5 Management Summaries

a. Since management will be unable to review allcomplete editions of EWR 127-1 [T], managementsummaries shall be prepared to specifically identifyEWR 127-1 [T] deletions, changes, and additions.

b. The management summary shall consist of allsigned EWR 127-1 [T] Tailoring Requests and alist of all HPWT members.

c. A copy of the management summary and thefinal EWR 127-1 [T] ready for signature shall beprovided to the Range Commander and the Chiefof Safety for their signature.

1A.2.4 Approvalsa. Each significant addition, change, or deletion

shall be signed off by the Range Safety Programmanager and the appropriate Range User represen-tative on the Tailoring Request form.

b. Tailored chapters affecting public safety (nor-mally Chapters 1, 2, 4, and 7) shall be approvedand signed by the Chief of Safety or a designatedrepresentative and the appropriate Range User rep-resentative on the Preface page of the EWR 127-1[T].

c. Tailored chapters not affecting public safety(normally Chapters 3, 5, and 6) shall be approvedand signed by the appropriate Range Safety sectionchief or a designated representative and the appro-priate Range User representative.

d. Each complete, final EWR 127-1 [T] affect-ing public safety shall be approved and signed bythe Wing Commander or a designated representa-tive and the appropriate Range User representa-tive.

1A.2.5 Revisions to EWR 127-1 [T]a. Any revision to the document shall be eval-

uated against each program EWR 127-1 [T] todetermine applicability.

b. Any revisions to EWR 127-1 [T] shall be madein accordance with the EWR 127-1 change process.

Eastern and Western Range 127-1 31 December 1999 Change to 1997 EWRAPPENDIX 1B

SYSTEM SAFETY PROGRAM REQUIREMENTS

1-26

1B.1 GENERAL SYSTEM SAFETY PROGRAMREQUIREMENTS

1B.1.1 System Safety ProgramThe Range User shall establish and maintain asystem safety program to support efficient andeffective achievement of overall system safetyobjectives.

1B.1.1.1 Management System

The Range User shall establish a safety man-agement system to implement provisions of thisdocument. A Range User program manager shallbe responsible for the following:

a. Establishing, controlling, incorporating, di-recting, and implementing the system safety pro-gram policies

b. Ensuring that mishap risk is identified andeliminated or controlled within established pro-gram risk acceptability parameters.

c. Establishing internal reporting systems andprocedures for investigation and disposition ofsystem related mishaps and safety incidents, in-cluding potentially hazardous conditions not yetinvolved in a mishap or incident and reportingsuch matters to Range Safety

d. Reviewing and approving safety analyses,reports, and documentation submitted to RangeSafety to establish knowledge and acceptance ofresidual risks.

1B.1.1.2 Key System Safety Personnel

The Range User shall establish and maintain a keysystem safety position for each program. The indi-vidual in this position shall be directly responsibleto the Range User program manager for safetymatters. At a minimum, Range User safety per-sonnel shall be responsible for the following:

a. Reviewing and approving safety analyses,reports, and documentation submitted to RangeSafety.

b. Reviewing and approving all hazardous andsafety critical test plans and procedures conductedat the Ranges and verifying that all safety re-quirements are incorporated.

1B.1.1.3 Compliance

Compliance with all contractually imposed re-quirements of this document is mandatory. When arequested system safety program plan is approvedby Range Safety, it provides a basis of under-standing between the Range User and Range

Safety as to how the system safety program will beaccomplished. Any noncompliance must be re-quested by the Range User and approved byRange Safety.

1B.1.1.4 Conflicting Requirements

When conflicting requirements or deficiencies areidentified in system safety program requirementsor with other program requirements, the RangeUser shall submit notification, with proposed so-lutions or alternatives and supporting rationale, toRange Safety for resolution.

1B.1.1.5 System Safety Precedence

The order of precedence for satisfying systemsafety requirements and resolving identified haz-ards shall be as follows:

a. Design for minimum risk. From the first, de-sign to eliminate hazards. If an identified hazardcannot be eliminated, reduce the associated risk toan acceptable level, as defined by Range Safety,through design selection.

b. Incorporate safety devices. If identified haz-ards cannot be eliminated or their associated riskadequately reduced through design selection, thatrisk shall be reduced to a level acceptable toRange Safety through the use of fixed, automatic,or other protective safety design features or de-vices. Provisions shall be made for periodic func-tional checks of safety devices when applicable.

c. Provide warning devices. When neither de-sign nor safety devices can effectively eliminateidentified hazards or adequately reduce associatedrisk, devices shall be used to detect the conditionand to produce an adequate warning signal to alertpersonnel of the hazard. Warning signals and theirapplication shall be designed to minimize theprobability of incorrect personnel reaction to thesignals and shall be standardized within like typesof systems.

d. Develop procedures and training. Where it isimpractical to eliminate hazards through designselection or adequately reduce the associated riskwith safety and warning devices, procedures andtraining shall be used. However, without a specificdeviation or waiver from Range Safety, no warn-ing, caution, or other form of written advisoryshall be used as the only risk reduction method forCategory I or II hazards (per Chapter 1 Table 1-1).Procedures may include the use of personal pro-tective equipment. Precautionary notations shall bestandardized as specified by Range Safety. Tasks

Chapter 1: Eastern and Western Range Safety Policies and Processes 31 December 1999 Change to 1997 EWRAPPENDIX 1B

1.4 1.4 SYSTEM SAFETY PROGRAM REQUIREMENTS

1-27

and activities judged to be safety critical by RangeSafety require certification of personnel profi-ciency.

1B.1.1.6 Risk Assessment

Decisions regarding resolution of identified haz-ards shall be based on assessment of the risk in-volved. To aid the achievement of the objectives ofsystem safety, hazards shall be characterized as tohazard severity categories and hazard probabilitylevels, when possible. Since the priority for systemsafety is eliminating hazards by design, a risk as-sessment procedure considering only hazard se-verity, will generally suffice during the early de-sign phase to minimize risk. When hazards are noteliminated during the early design phase, a riskassessment procedure based upon the hazard prob-ability, hazard severity, as well as risk impact,shall be used to establish priorities for correctiveaction and resolution of identified hazards.

1B.1.2 Task 1: Establish a System SafetyProgram

The purpose of this task is to establish the founda-tion for a system safety program. The require-ments for Task 1 are as follows:

a. Establish and execute a system safety pro-gram that meets the tailored requirements of thisdocument.

b. Develop a planned approach for safety taskaccomplishment, provide qualified people to ac-complish the tasks, establish the authority for im-plementing the safety tasks through all levels ofmanagement, and allocate appropriate resources,both manning and funding, to ensure the safetytasks are completed.

c. Establish a system safety organization orfunction and lines of communication within theprogram organization and with associated organi-zations (government and contractor).

d. Establish interfaces between system safetyand other functional elements of the program, aswell as between other safety disciplines such asnuclear, range, explosive, chemical, and biologi-cal.

e. Designate the organizational unit responsiblefor executing each safety task.

f. Establish the authority for resolution of iden-tified hazards.

g. Define system safety program milestones andrelate these to major program milestones, programelement responsibility, and required inputs and

outputs.h. Establish an incident alert and notification,

investigation and reporting process, to include no-tification of Range Safety.

1B.1.3 Task 2: Develop a System Safety Pro-gram Plan

The purpose of this task is to develop a SystemSafety Program Plan (SSPP). The SSPP shall de-scribe in detail tasks and activities of system safe-ty management and system safety engineering re-quired to identify, evaluate, and eliminate andcontrol hazards, or reduce the associated risk to alevel acceptable to Range Safety throughout thesystem life cycle. The approved plan provides aformal basis of understanding between the RangeUser and Range Safety on how the SSPP will beconducted to meet the requirements of EWR 127-1, including general and specific provisions. Theapproved plan shall account for all contractuallyrequired tasks and responsibilities on an item-by-item basis. The Range User shall submit a draftSSPP to Range Safety for review and approvalwithin 45 days of contract award and a final atleast 45 days prior to any program cDR. The SSPPshall include the following information:1B.1.3.1 System Safety OrganizationThe System Safety Organization section shall de-scribe the following:

a. The system safety organization or functionwithin the organization of the total program usingcharts to show the organizational and functionalrelationships and lines of communication

b. The organizational relationship between oth-er functional elements having responsibility fortasks with system safety impacts and the systemsafety management and engineering organization

c. Review and approval authority of applicabletasks by system safety

d. The responsibility and authority of systemsafety personnel, other Range User organizationalelements involved in the system safety effort,contractors, and system safety groups

e. A description of the methods by which safetypersonnel may raise issues of concern directly tothe program manager or the program manager'ssupervisor within the organization

f. Identification of the organizational unit re-sponsible for executing each task

g. Identification of the authority in regard toresolution of all identified hazards



1-28

h. The staffing of the system safety organizationfor the duration of the program to include person-nel loading and a summary of the qualifications ofkey system safety personnel assigned to the effort,including those who possess coordination and ap-proval authority for Range User prepared docu-mentation

i. The process by which Range User manage-ment decisions will be made, including such deci-sions as timely notification of unacceptable risks,necessary action, incidents, or malfunctions, waiv-ers to safety requirements, program deviations

j. Details of how resolution and action relativeto system safety will be accomplished at the pro-gram management level possessing resolutionauthority

1B.1.3.2 System Safety Program MilestonesThe SSPP shall:

a. Define system safety program milestones andrelate these to major program milestones, programelement responsibility, and required inputs andoutputs

b. Provide a program schedule of safety tasks,including start and completion dates, reports, andreviews

c. Identify subsystem, component, softwaresafety activities as well as integrated system levelactivities such as design analyses, tests, and dem-onstrations applicable to the system safety pro-gram but specified in other engineering studiesand development efforts to preclude duplication

1B.1.3.3 System Safety DataThe SSPP shall:

a. Identify deliverable data by title, number, andmeans of delivery such as hard copy, electronic

b. Identify non-deliverable system safety dataand describe the procedures for accessibility byRange Safety and retention of data of historicalvalue

1B.1.3.4 System Safety Interfaces

The SSPP shall identify, in detail:a. The interface between system safety and all

other applicable safety disciplines such as: nuclearsafety, Range Safety, explosive and ordnancesafety, chemical and biological safety, laser safe-ty, and any others

b. The interface between system safety, systemsengineering, and all other support disciplines suchas maintainability, quality control, reliability,

software development, human factors engineering,medical support (health hazard assessments), andany others

c. The interface between system safety and allsystem integration and test disciplines

1B.1.4 Task 3: Establish System Safety Pro-gram Reviews and Audits

The purpose of this task is to establish a systemsafety program review and audit program as speci-fied by Range Safety. This task is also used to ac-quire support for special requirements such as cer-tifications and test and flight readiness reviews.The following tasks shall be performed:

a. Conduct, document, and make documentationavailable to Range Safety upon request the fol-lowing reviews and audits:

1. The Range User system safety program2. Associate contractor system safety pro-

grams3. Support contractor system safety programs4. Subcontractor system safety programs

b. Provide the support for the following:1. Safety reviews and audits performed by

representatives of Range Safety2. Presentations to government certifying ac-

tivities such as phase safety reviews, munitionssafety boards, nuclear safety boards, or flightsafety review boards to the extent specified by thisdocument. NOTE: These may also include specialreviews such as flight and article readiness reviewsor pre-construction briefings.

3. Safety reviews shall be held in associationwith program cDR, PDR, and CDRs. Generally,the safety reviews shall address the following:

a) Program systems and operations overviewb) Presentation of Range Safety required

documentationc) EWR 127-1 Noncompliancesd) Open safety issues

1B.1.5 Task 4: Track Hazards and RiskResolution

The purpose of this task is to establish a singleclosed-loop hazard tracking system by develop-ment of a method or procedure to document andtrack hazards and their controls, providing an audittrail of hazard resolutions. A centralized file, com-puter database, or document called a Hazard Logshall be maintained and made available to RangeSafety upon request. At a minimum, the HazardLog shall contain the following information:



1-29

a. Description of each hazard, including an as-sociated hazard risk index

b. Status of each hazard and controlc. Traceability of resolution on each Hazard Log

item from the time the hazard was identified to thetime the risk associated with the hazard was re-duced to a level acceptable to Range Safety

d. Identification of residual riske. Action persons and organizational elementf. The recommended controls to reduce the haz-

ard to a level of risk acceptable to Range Safetyg. The signature of Range Safety accepting the

risk effecting closure of the Hazard Log item

1B.2 HAZARD ANALYSIS ANDRISK RESOLUTION

NOTE: The Range User shall perform all of therequired Preliminary Hazard Analyses (PHAs),Subsystem Hazard Analyses (SSHAs), SystemHazard Analyses (SHAs), Operating and SupportHazard Analyses (O&SHAs) and Safety Assess-ments per Tasks 1 through 8 that follow; however,the Range User shall submit to Range Safety onlythose Hazard Analyses and Safety Assessments asspecifically required per the Data Requirementssections of Chapters 3, 4, 5, and 6 of this docu-ment.

1B.2.1 Task 1: Perform and Document A Pre-liminary Hazard Analysis

The purpose of this task is to perform and docu-ment a Preliminary Hazard Analysis (PHA) toidentify safety critical areas, to provide an initialassessment of hazards, and to identify requisitehazard controls and follow-on actions. The RangeUser shall perform and document a PHA to obtainan initial risk assessment of a concept or system.Based on the best available data, including mishapdata from similar systems and other lessonslearned, hazards associated with the proposed de-sign or function shall be evaluated for hazard se-verity, hazard probability, and operational con-straint. Safety provisions and alternatives neededto eliminate hazards or reduce their associated riskto a level acceptable to Range Safety shall be in-cluded. At a minimum, the PHA shall consider thefollowing for identification and evaluation of haz-ards:

a. Hazardous components such as fuels, propel-lants, lasers, explosives, toxic substances, hazard-ous construction materials, pressure systems, andother energy sources

b. Safety related interface considerations amongvarious elements of the system such as materialcompatibility, electromagnetic interference, inad-vertent activation, fire and explosive initiation andpropagation, and hardware and software controls.NOTE: This shall include consideration of thepotential contribution by software, including soft-ware developed by other contractors and sour-ces,to subsystem and system mishaps.

c. Safety design criteria to control safety-criticalsoftware commands and responses such as inad-vertent command, failure to command, untimelycommand or responses, inappropriate magnitude,or designated undesired events shall be identifiedand appropriate action taken to incorporate themin the software and related hardware specifica-tions.

d. Environmental constraints including the oper-ating environments such as drop, shock, vibration,extreme temperatures, humidity, noise, exposureto toxic substances, health hazards, fire, electro-static discharge, lightning, electromagnetic envi-ronmental effects, ionizing and non-ionizing ra-diation including laser radiation

e. Operating, test, maintenance, built-in-tests,diagnostics, and emergency procedures (humanfactors engineering, human error analysis of op-erator functions, tasks, and requirements; effect offactors such as equipment layout, lighting re-quirements, potential exposures to toxic materials,effects of noise or radiation on human perform-ance; explosive ordnance render safe and emer-gency disposal procedures; life support require-ments and their safety implications in mannedsystems, crash safety, egress, rescue, survival, andsalvage)

f. Those test unique hazards that will be a di-rect result of the test and evaluation of the articleor vehicle

g. Facilities, real property installed equipment,support equipment such as provisions for storage,assembly, checkout, Proof testing of hazardoussystems and assemblies that may involve toxic,flammable, explosive, corrosive or cryogenic ma-terials and wastes; radiation or noise emitters;electrical power sources

h. Training and certification pertaining to haz-ardous and safety critical operations and mainte-nance of hazardous and safety critical systems

i. Safety related equipment, safeguards, andpossible alternate approaches such as interlocks;system redundancy; fail safe design considerations



1-30

using hardware or software controls; subsystemprotection; fire detection and suppression systems;personal protective equipment; heating, ventila-tion, and air-conditioning; and noise or radiationbarriers

j. Malfunctions to the system, subsystems, orsoftware. NOTE: Each malfunction shall be speci-fied, the cause and resulting sequence of eventsdetermined, the degree of hazard determined, andappropriate specification and/or design changesdeveloped.

1B.2.2 Task 2: Perform and Document Sub-system Hazard Analyses

The purpose of this task is to perform and docu-ment a Subsystem Hazard Analysis (SSHA) toverify subsystem compliance with safety require-ments contained in subsystem specifications andother applicable documents; identify previouslyunidentified hazards associated with the design of

subsystems including component failure modes,critical human error inputs, and hazards resultingfrom functional relationships between componentsand equipment comprising each subsystem; andrecommend actions necessary to eliminate identi-fied hazards or control their associated risk to ac-ceptable levels. The Range User shall perform anddocument an SSHA to identify all components andequipment that could result in a hazard or whosedesign does not satisfy contractual safety require-ments. This will include government furnishedequipment, non-developmental items, and soft-ware. Areas to consider are performance, perform-ance degradation, functional failures, timing er-rors, design errors or defects, or inadvertent func-tioning. The human shall be considered a compo-nent within a subsystem, receiving both inputs andinitiating outputs, during the conduct of this analy-sis. The analysis shall include a determination ofthe following:

a. The modes of failure including reasonablehuman errors as well as single point and commonmode failures, and the effects on safety when fail-ures occur in subsystem components

b. The potential contribution of hardware andsoftware, including that which is developed byother contractors and sources, events, faults, andoccurrences such as improper timing on the safetyof the subsystem

c. That the safety design criteria in the hard-ware, software, and facilities specifications havebeen satisfied

d. That the method of implementation of hard-ware, software, and facilities design requirementsand corrective actions has not impaired or de-creased the safety of the subsystem nor has it in-troduced any new hazards or risks

e. The implementation of safety design re-quirements from top level specifications to de-tailed design specifications for the subsystem.NOTE: The implementation of safety design re-quirements developed as part of the PHA shall beanalyzed to ensure that it satisfies the intent of therequirements.

f. Test plan and procedure recommendations tointegrate safety testing into the hardware andsoftware test programs



1-31

g. That system level hazards attributed to thesubsystem are analyzed and that adequate controlof the potential hazard is implemented in the de-sign

1B.2.2.1 SSHA Analysis Techniques

If no specific analysis techniques are directed or ifRange User recommends that a different techniquethan specified by Range Safety should be used, theRange User shall obtain approval of techniques tobe used prior to performing the analysis.

1B.2.2.2 SSHA Software

a. When software to be used in conjunction withthe subsystem is being developed under MIL-STD-498 or MIL-STD-1679 or other developmentdocuments; the Range User performing the SSHAshall monitor, obtain, and use the output of eachphase of the formal software development processin evaluating the software contribution to theSSHA.

b. Problems identified that require the reactionof the software developer shall be reported toRange Safety in time to support the ongoing phaseof the software development process.

1B.2.2.3 Updating the SSHA

The Range User shall update the SSHA as a resultof any system design changes, including softwaredesign changes, that affect system safety.

1B.2.3 Task 3: Perform and Document Sys-tem Hazard Analyses

The purpose of this task is to perform and docu-ment a System Hazard Analysis (SHA) to verifysystem compliance with safety requirements con-tained in system specifications and other applica-ble documents; identify previously unidentifiedhazards associated with the subsystem interfacesand system functional faults; assess the risk asso-ciated with the total system design, includingsoftware, and specifically of the subsystem inter-faces; and recommend actions necessary to elimi-nate identified hazards and/or control their associ-ated risk to acceptable levels.

The Range User shall perform and document asystem hazard analysis to identify hazards and as-sess the risk of the total system design, includingsoftware, and specifically of the subsystem inter-faces. This analysis shall include a review of sub-system interrelationships to determine the follow-ing:

a. Compliance with specified safety design cri-teria

b. Possible independent, dependent, and simul-taneous hazardous events including system fail-ures; failures of safety devices; common causefailures and events; and system interactions thatcould create a hazard or result in an increase inmishap risk

c. Degradation in the safety of a subsystem orthe total system from normal operation of anothersubsystem

d. Design changes that affect subsystemse. Effects of reasonable human errorsf. Potential contribution of hardware and soft-

ware, including that which is developed by otherRange Users and other sources or commercial off-the-shelf hardware or software, events, faults andoccurrences such as improper timing on the safetyof the system.

g. That the safety design criteria in the hard-ware, software, and facilities specifications havebeen satisfied

h. That the method of implementation of thehardware, software, and facilities design require-ments and corrective actions has not impaired ordegraded the safety of the system nor has intro-duced any new hazards

1B.2.3.1 SHA Analysis Techniques

If no specific analysis techniques are directed or ifRange User recommends that a different techniquethan specified by Range Safety should be used, theRange User shall obtain approval of techniques tobe used prior to performing the analysis. The SHAmay be combined with and/or performed usingsimilar techniques to those used for the SSHA.

1B.2.3.2 SHA Software

a. When software to be used in conjunction withthe system is being developed under DoD-STD-2167 and DoD-STD-2168; or MIL-STD-1679 orother development documents; the Range Userperforming the SHA shall monitor, obtain, and usethe output of each phase of the formal softwaredevelopment process in evaluating the softwarecontribution to the SSHA.

b. Problems identified that require the reactionof the software developer shall be reported toRange Safety in time to support the ongoing phaseof the software development process.



1-32

1B.2.3.3 Updating the SHA

The Range User shall update the SHA as a resultof any system design changes, including softwaredesign changes, that affect system safety.

1B.2.4 Task 4: Perform and Document Oper-ating and Support Hazard Analyses

The purpose of this task is to perform and docu-ment Operating and Support Hazard Analysis(O&SHA) to evaluate activities for hazards orrisks introduced into the system by operational andsupport procedures and to evaluate adequacy ofoperational and support procedures used to elimi-nate, control, or abate identified hazards or risks.

The Range User shall perform and document anO&SHA to examine procedurally controlled ac-tivities. The O&SHA identifies and evaluates haz-ards resulting from the implementation of opera-tions or tasks performed by persons, consideringthe following criteria: the planned system configu-ration and/or state at each phase of activity; thefacility interfaces; the planned environments or theranges thereof; the supporting tools or otherequipment, including software controlled auto-matic test equipment, specified for use; operationaland/or task sequence, concurrent task effects andlimitations; biotechnological factors, regulatory orcontractually specified personnel safety and healthrequirements; and the potential for unplannedevents including hazards introduced by humanerrors. The human shall be considered an elementof the total system, receiving both inputs and initi-ating outputs during the conduct of this analysis.

The O&SHA shall identify the safety requirementsor alternatives needed to eliminate or controlidentified hazards or to reduce the associated

risk to a level that is acceptable under either regu-latory or Range Safety specified criteria. Theanalysis shall identify the following:

a. Activities that occur under hazardous condi-tions, their time periods, and the actions requiredto minimize risk during these activities and timeperiods

b. Changes needed in functional or design re-quirements for system hardware and software, fa-cilities, tooling, or support and test equipment toeliminate or control hazards or reduce associatedrisks

c. Requirements for safety devices and equip-ment, including personnel safety and life supportequipment

d. Warnings, cautions, and special emergencyprocedures such as egress, rescue, escape, rendersafe, explosive ordnance disposal, and back-out,including those necessitated by failure of a com-puter software-controlled operation to produce theexpected and required safe result or indication

e. Requirements for packaging, handling, stor-age, transportation, maintenance, and disposal ofhazardous materials

f. Requirements for safety training and person-nel certification

g. Effects of non-developmental hardware andsoftware across the interface with other systemcomponents or subsystems

h. Potentially hazardous system states underoperator control

1B.2.4.1 Assessment of Procedures

The O&SHA shall document system safety as-sessment of procedures involved in: system pro-duction, deployment, installation, assembly, test,operation, maintenance, servicing, transportation,storage, modification, demilitarization, and dis-posal.

1B.2.4.2 O&SHA Analysis Techniques

If no specific analysis techniques are directed or ifthe Range User recommends that a different tech-nique than specified by Range Safety should beused, the Range User shall obtain approval oftechniques to be used prior to performing theanalysis.

1B.2.4.3 Updating the O&SHA

The Range User shall update the O&SHA as a re-sult of any system design or operational changes.

1B.2.5 Task 5: Perform and Document Safety



1-33

AssessmentsThe purpose of this task is to perform and docu-ment a comprehensive evaluation of the mishaprisk being assumed prior to test or operation of asystem. The Range User shall perform and docu-ment a safety assessment to identify all safetyfeatures of the hardware, software, and systemdesign and to identify procedural, hardware andsoftware related hazards that may be present in thesystem being acquired including specific proce-dural controls and precautions that should be fol-lowed. The safety assessment shall summarize thefollowing information:

a. The safety criteria and methodology used toclassify and rank hazards, plus any assumptions onwhich the criteria or methodologies were based orderived including the definition of acceptable riskas specified by Range Safety

b. The results of analyses and tests performed toidentify hazards inherent in the system, including:

1. Those hazards that still have a residual riskand the actions that have been taken to reduce theassociated risk to a level contractually specified asacceptable

2. Results of tests conducted to validate safetycriteria, requirements and analyses

c. The results of the safety program efforts., in-cluding a list of all significant hazards along withspecific safety recommendations or precautionsrequired to ensure safety of personnel, property, orthe environment. NOTE: The list shall be catego-rized as to whether or not the risks may be ex-pected under normal or abnormal operating condi-tions.

d. Any hazardous materials generated by or usedin the system

e. Conclusion with a signed statement that allidentified hazards have been eliminated or theirassociated risks controlled to levels contractually

specified as acceptable, and that the system isready to test or operate or proceed to the next ac-quisition phase

f. Recommendations applicable to hazards atthe interface of Range User systems with othersystems, as required

1B.2.6 Task 6: Perform and Document Engi-neering Change Proposals, Specifica-tion Change Notices, Software Prob-lem Reports, Program or SoftwareTrouble Reports, and Requests

The purpose of this task is to perform and docu-ment analyses of Engineering Change Proposals(ECPs), Specification Change Notices (SCNs),Software Problem Reports (SPRs), program orsoftware trouble reports (PTRs, STRs), and re-quests for deviation or waiver to determine thesafety impact on the system.

1B.2.6.1 Engineering Change Proposals

As specified by Range Safety, the Range Usershall analyze each ECP to determine the hazardsassociated with it, assess the associated risk, andpredict the safety impact of the ECP on the exist-ing system. The Range User shall notify RangeSafety when an ECP changes the level of safety ofthe existing system.

1B.2.6.2 Specification Change Notices

The Range User shall analyze each SCN to deter-mine the potential effect on safety critical compo-nents or subsystems. The Range User shall notifyRange Safety if the level of safety of the systemchanges.

1B.2.6.3 Software Problem Reports

The Range User shall review each SPR to deter-mine the potential safety implications. If safetyimpacts are identified, the Range User shall notifyRange Safety of a decrease in the level of safety ofthe system.

1B.2.6.4 Program or Software Trouble Reports

The Range User shall review each PTR and STRto determine the potential safety implications. If



1-34

safety impacts are identified, the Range User shallnotify Range Safety of a decrease in the level ofsafety of the system.

1B.2.7 Task 7: Perform and Document Com-pliance With Safety Requirements

The purpose of this task is to define and performtests and demonstrations or use other verificationmethods on safety critical hardware, software, andprocedures to verify compliance with safety re-quirements.

The Range User shall define and perform tests,demonstrations, develop models, and otherwiseverify the compliance of the system with safetyrequirements on safety critical hardware, software,and procedures. Induced or simulated failures shallbe considered to demonstrate the acceptable safetyperformance of the equipment and software.

Where hazards are identified during the develop-ment efforts and analysis or inspection cannot de-termine the adequacy of actions taken to reducethe risk, safety tests shall be specified and con-ducted to evaluate the overall effectiveness of theactions taken. SSPPs and test plan and proceduredocuments shall be revised to include these tests.

Where costs for safety testing would be prohibi-tive, safety characteristics or procedures may beverified by engineering analyses, analogy, labora-tory test, functional mockups, or models andsimulations when approved by Range Safety. Spe-cific safety tests shall be integrated into appropri-ate system test and demonstration plans, includingverification and validation plans, to maximum ex-tent possible.

Test plans, test procedures, and the results of alltests including design verification, technical op-erational evaluation, technical data and require-ments validation and verification, production ac-ceptance, and shelf-life validation shall be re-viewed to ensure:

a. Safety of the design, including operating andmaintenance procedures, is adequately demon-strated, including verification of such items assafety devices and warning devices for all cata-strophic hazards not eliminated by design. Critical,marginal, and negligible hazards shall also be ad-dressed as required by Range Safety.

b. Results of safety evaluations of the systemare included in the test and evaluation reports onhardware or software.

1B.2.8 Task 8: Perform and Document Com-pliance with Applicable Codes

The purpose of this task is to perform and docu-ment an assessment to identify and verify compli-ance with military, federal, national, international,and industry codes to ensure safe design of a sys-tem, and to comprehensively evaluate the safetyrisk being assumed prior to test or operation of asystem or at contract completion.

The Range User shall perform and document asafety compliance assessment to identify anddocument compliance with appropriate design andoperational safety requirements. The assessmentidentifies the contractually imposed standards,specifications, and codes appropriate to the safetyof the system and documents compliance withthese requirements.

The assessment includes necessary hazard analy-sis, design drawing and procedural reviews, andequipment inspections. The assessment shall in-corporate the scope and techniques of the PHA,SSHA, SHA, and O&SHA to the extent necessaryto ensure the safe design, operation, maintenance,and support of the system. A safety complianceassessment shall include the following:

a. Identification of military, federal, national,international, and industry safety specifications,standards, and codes applicable to the system anddocumentation of compliance of the design andprocedures with these requirements

b. Identification of other military, federal, na-tional, international, and industry safety specifica-tions, standards, and codes applicable to the sys-tem, that are required by law or the use thereof isconsidered good engineering practice, and docu-mentation of compliance of the design and proce-dures with these requirements

c. Identification and evaluation of residual haz-ards inherent in the system or that arise from sys-tem unique interfaces, installation, test, operation,maintenance, or support

d. Identification of necessary specialized safetydesign features, devices, procedures, skills, train-ing, facilities, support requirements, and personnelprotective equipment

e. Identification of hazardous materials and jus-tification for using such a material instead of a lessor non-hazardous material and the precautions andprocedures necessary for safe storage, hand-ling,transport, use, and disposal of material.


APPENDIX 1C1.5 1.5 SUBMITTING EWR 127-1 NONCOMPLIANCE REQUESTS

1-35

1C.1 INTRODUCTION1C.1.1 PurposeMeets intent certifications (MICs), deviations, andwaivers are used when Range Users can not meetor feel that they can meet equivalent, though notthe exact requirements of the document.

1C.1.2 ContentThis Appendix describes the noncompliance cate-gories and the process for submitting MICs, de-viations, and waivers.

1C.1.3 Applicabilitya. The noncompliance process is applicable to

all programs including boosters, solid rocket mo-tors, upper stages, payloads, ground supportequipment, facilities, and others that operate at theRanges or elsewhere if governed under Range per-sonnel unless grandfathered in accordance with thecriteria stated below. b. The noncompliance proc-ess is also applicable to all programs regardless ofwhich version of the old Range Safety Standards(such as AFETR 127-1, ESMCR 127-1, ERR 127-1, WSMCR 127-1, and WRR 127-1) is undercontract. c. The flight plan approval process doesnot fall within the intent of this Appendix exceptwhen it involves launch vehicle and/or payloadhardware.

1C.1.4 Grandfathering Criteria:Previously approved systems with or withoutgranted MICs, deviations, and waivers will begrandfathered and maintain approval and need notbe resubmitted unless it is determined by the Chiefof Safety and/or the Range User that one of thefollowing situations exists: a. Existing programsmake major modifications or include the use ofcurrently approved com-ponents, systems, orsubsystems in new application (through tailoring ifdesire) Exception: Previously approved existingcomponents, systems, or sub-systems that do notincrease the risks, do not degrade safety, or cansurvive new environments are equivalent to orlower than the originally approved qualificationlevels shall be honored and do not have to meet newrequirements as long as data and analyses showthat the criteria have been met.

b. The Range User has determined that it iseconomically and technically feasible to incor-porate new requirements into the system.

c. The system has been or will be modified to theextent that it is considered a new program or thatexisting safety approvals no longer apply. NOTE:Risk and hazard analyses developed jointly byRange Safety and the Range User shall be used todetermine applicability of the safety approvals.

d. A previously unforeseen or newly discoveredsafety hazard exists that is deemed by either RangeSafety or the Range User to be significant enough towarrant the change.

e. The system does not meet the requirementsexisting when the system was originally accepted.NOTE: This category includes systems that werepreviously approved, but when obtaining theapproval, the noncompliances to the originalrequirement were not identified.

f. A system or procedure is modified and a newrequirement reveals that a significant risk exists.

g. Accident and incident investigations and re-ports may dictate compliance with the document.

1C.1.5 Noncompliance Categories1C.1.5.1 Public Safety

Public safety noncompliance deals with safety re-quirements involving risks to the general public ofthe US or foreign countries and/or their property.

1C.1.5.2 Launch Area Safety

Launch area safety noncompliances deal withsafety requirements involving risks that are limitedto personnel and/or property on VAFB and CCAS,and may be extended to KSC. Launch area safetyinvolves multiple commercial users, governmenttenants, and/or squadrons.

1C.1.5.3 Launch Complex Safety

Launch complex safety noncompliances deal withsafety requirements involving risk that is limitedto the personnel and/or property under the controlof a single commercial user, full time governmenttenant organization, or USAF squadron/detach-ment commander (control authority). Launchcomplex safety is limited to risks confined to a


APPENDIX 1CSUBMITTING EWR 127-1 NONCOMPLIANCE REQUESTS

1-36

physical space for which the single controlauthority is responsible.

1C.1.6 Effectivity of Noncompliances1C.1.6.1 Lifetime

a. Lifetime deviations and waivers are unde-sirable and shall be limited to those situations whereit is virtually impossible to meet the requirement ormeet the intent of the requirement.

b. Lifetime MICs are allowed provided equiva-lent safety is maintained.

1C.1.6.2 Time Limited

a. Time limited deviations and waivers are set fora limited period of time or a limited number oflaunches. The time constraint is normallydetermined as a function of cost, impact onschedule, and the minimum time needed tosatisfactorily modify or replace the non-compliantsystem or to modify the non-compliant operation.

b. MICs may be time limited depending on themethod by which equivalent safety is accom-plished. If excessive procedural controls, person-nel, material, or costs are required to maintainequivalent safety, the MIC should be time limited.

1C.1.7 Conditions for Issuance of Deviations,MICs, and Waivers

a. Hazard Mitigation. All reasonable steps shallbe taken to meet the intent of the documentrequirements and mitigate associated hazards toacceptable levels, including design and operationalmethods.

b. Get Well Plans. All deviations, MICs, andwaivers that are not granted for the life of a pro-gram shall have a plan to meet the requirements inquestion by the time the approved effectivity ex-pires.

1C.1.8 Risk-Cost Benefit Analysisa. Technical disagreements regarding such items

as applicable requirements, policy, criteria, or datamay be evaluated on a risk-cost benefit basis todetermine if the risk is acceptable to delete, modify,deviate from, or waive the requirements.

b. Risk-cost benefit analyses based on the criteriadefined in Tables 1-1 and 1-2 of this Chapter shallbe submitted to Range Safety.

c. Based on risk-cost benefit analysis data, RangeSafety and the Range User shall reach agreement on

the disposition of the requirement in question.d. If the application of an EWR 127-1 require-

ment results in a significant reduction of risk at asignificant cost benefit, it may be judged by RangeSafety to be sufficient to impose the requirement;however, if the benefit is insignificant and/or thecost is high, the requirement may be deviatedfrom, waived, or determined to meet the intent, allwith consideration for public safety.

1C.2 SUBMITTING NONCOMPLIANCES1C.2.1 FormatAll noncompliances shall be submitted in writingin letter or memorandum format or the equivalent.An example format may be found in the RangeUser Handbook. As an alternative, a matrix-typeformat, containing the same information as thenon-compliance request form, may be used if mu-tually agreeable to the Range User, Range Safety,and the appropriate approving official.

1C.2.2 ContentThe following items shall be included in the letter ormemorandum:

a. Title: MIC, Deviation, Waiver of (require-ment a) for (requirement b)

b. Descriptive Title of MIC, Deviation, Waiverrequest

c. MIC, Deviation, Waiver categoryd. MIC, Deviation, Waiver effectivitye. Background

1. Summary of Range Safety requirement2. Statement of the noncompliance3. Reason for request

f. Conditions for MIC, Deviation, Waiver1. Hazard mitigation2. Get Well Plan

1C.2.3 Processa. Requests for MICs, deviations, and waivers

shall be submitted to the Office of the Chief ofSafety as early as they are known to be necessary.

b. Public safety MICs, deviations, and waiverssuch as those including flight plan approval, flighttermination system design, and toxic propellantstorage normally require extensive risk analyses thatcan take one to two years to perform; therefore,these deviations, MICs, and waivers shall beinitiated during the planning phase and be closedout by Wing Commander approval or design


APPENDIX 1C1.5 1.5 SUBMITTING EWR 127-1 NONCOMPLIANCE REQUESTS

1-37

change prior to manufacture of the booster,spacecraft, flight termination system or othersystem in question.

c. Launch site safety and launch complex safetyMICs, deviations, and waivers normally requiretwo weeks to two months to process depending onthe nature of the noncompliance and the requestedeffectivity.

1C.2.4 Approvalsa. Programs launching from only the ER or WR

require only the appropriate 45 SW/SE or 30SW/SE approvals.

b. Programs launching from both Ranges requireapprovals from 45 SW/SE and 30 SW/SE.

c. Waivers and deviations dealing with public sa-fety shall be approved by the Wing Commanders ortheir designated representatives.

d. Waivers and deviations other than public sa-fety shall be approved by the Chiefs of Safety ortheir designated representatives.

e. MICs shall be approved by appropriate 45SW/SE or 30 SW/SE section chiefs or their desig-nated representatives.

Chapter 1: Eastern and Western Range Safety Policies and Processes 31 December 1999 Change to 1997 EWRAPPENDIX 1D

1.6 EWR 127-1 ACCEPTABLE RISK CRITERIA

1-38

1D.1 INTRODUCTIONa. The criteria defined in this Appendix is for-

mulated to meet the requirements of PL 60 andapply to all programs and missions operating at theRanges.

b. All programs and missions are subject toGO/NO-GO decisions based on risk acceptance.The overall risk levels may or may not be an addi-tive value that includes risks resulting from debris,toxic, and blast overpressure exposures. Riskguidance levels in the Launch Area Safety andLaunch Complex Safety sections of this Chapterare derived from the criteria shown in Table 1D-1.

c. These risk guidance levels are provided asguidance for the Wing Commanders and as plan-ning information for Range Users.

d. Range Users should use this guidance to de-velop their program or mission plans to minimizerisk levels.

1D.2 DESCRIPTION OF RISK CRITERIAa. As shown in Table 1D-1, comparing normally

accepted public, day-to-day accident risk exposureto normal launch vehicle and payload launch oper-ating risks indicates that, under any circumstances,the annual collective risk for launch operations issmall.

b. A ratio of 1 x 10-3/1.8 x 104 = 5.7 x 10-8 isobtained between the maximum annual launchrisks accepted under the guidance limits and thetotal annual launch risk. Therefore, launch opera-tions risks are only this fraction of the normallyaccepted risk levels defined in the Public Safetysection of this document.

c. Individual hazardous activities may exceedguidance levels based on national need or missionrequirements. Deviations, meets intent certifica-tions, or waiver requests are required.

Table 1D-1Comparison of Various Normally Accepted Public Ambient Collective Accident Risks

with Collective ER and WR Launch Risk Guides

Hazardous EventsAverage US IndividualCasualty Risk per Year

Collective Casualty Riskper Year for Population in

ER and WR Launch Area a

Equivalent LaunchCollective Casualty

Risk per Year

Launch Guidance Lim-its: Collective Casualty

Risks per LaunchAll Accidents 7.2 X 10 -2 b 1.8 X 104

Motor Vehicle Accidents 8.0 X 10-3 b 2.0 X 103

Air Travel Accidents 6.4 X 10-4 c 1.6 X 102

Natural Hazards d 2.6 X 10-4 e 6.5 X 101

Hypothetical Nuclear Plant Accident 4.0 X 10-6 e 1.0Aviation Over flight Accidents 1.8 x 10-2 f

Maximum Risk Acceptableg for Acci-dent in One-Time National NeedLaunch

1 x 10-2 3 X 10-4 h

Maximum Risk Acceptable g for Ac-cidents in Launches Unless HighManagement Review

1 X 10-3 3 X 10-5 i

Notes: a Total population of 2.5 X 105 assumed exposed to ER or WR launch area Accidents.b From total numbers of casualties (at least one-day disability) in Accident Facts, 1994, a publication of the National Safety Coun-

cil, divided by US population of 2.5 X 108

c From number of fatalities in Accident Facts, 1994, multiplied by 200, approximately the average number f causalities (at leastone-day disability) experienced in the US for each accident fatality experienced.

d Lightning, tornadoes, hurricane (earthquake negligible)e From Reactor Safety Study, WASH-1400/NUREG-75/014, 1975.f From Philipson, Lloyd L., Refined Estimate of the Risk from Aviation Accidents to the Population in the CCAS Area of Concern,

ACTA Inc., Report No. 94-297/46-01, September 1994. (Estimates derived for the ER; assumed to be applicable to the WR aswell)

g Waiver or Deviation Required.h At most one such launch per year assumed.i From Risk Commonality/Acceptability Workshop, August 1990.


APPENDIX 1E1.8 MAKING CHANGES TO EWR 127-1

1-39

1E.1 INTRODUCTION1E.1.1 PurposeChanging the document provides a means forkeeping the document current with new technol-ogy and processes and allowing for internal andexternal technical reviews.

1E.1.2 ContentThis Appendix describes the process for submit-ting changes to the document. These changes areglobal in nature and do not address technicalchanges that are related to specific and uniqueprogram issues.

1E.1.3 ApplicabilityThe document change process is applicable to allRange Users and Range organizations that are re-sponsible for applying the document on contractand monitoring the compliance and implementa-tion of the requirements.

1E.2 CHANGE PROCESSChanges to EWR 127-1 shall be submitted usingthe Change Request form. Only one change is al-lowed per Change Request form and that change isrequired to stand alone regarding specific subjectmatter and alphanumeric paragraph number.NOTE: A sample of this form may be found in theRange Safety Range User Handbook.

1E.2.1 Completing Change RequestsChange Requests shall include the following infor-mation:

a. Date of requestb. Name of originatorc. Name of company or agencyd. Address of company or agencye. Telephone and Fax numbers as applicable

f. The alphanumeric designation of the affectedparagraph

g. The text for the suggested changeh. The rationale for the suggested change

1E.2.2 Submitting Change RequestsCompleted Change Requests shall be submitted tothe 45 SW/SE Office of the Chief of Safety, Sys-tems Safety Engineering Support, 1201 Edward H.White II Street, Patrick Air Force Base, Florida32925-3238. Change Requests can also be sub-mitted electronically via the following RangeSafety e-mail address:

[email protected]

1E.2.3 Range User ReviewDepending upon the impact of a proposed change,Change Requests may be sent out to Range Usersfor review and comment prior to final resolution.

In addition, if the proposed change is complex,meetings may be arranged with Range Users asrequired.

1E.2.4 Disposition of Change Requestsa. 45 SW/SE is the office of primary responsibil-

ity and 30 SW/SE will be the office of coordinatingresponsibility for all EWR 127-1 changes.

b. The disposition of Change Requests falls intothe following three categories:

1. Concur As Written2. Concur With The Intent. In such cases, the

Change Request will be rewritten.3. Do Not Concur. Rationale for not accepting

the proposed change will be provided.

1E.2.5 Range User NotificationApproved changes to the document shall be pub-lished annually. Changes requiring immediateRange User attention shall be published as requiredas official document Change Notices. A sampleChange Notice is included in the Range User Hand-book.


APPENDIX 1F1.10 1.7 GENERIC PAYLOAD POLICY AND APPROVAL REQUIREMENTS

1-40

1F.1 GENERIC PAYLOAD POLICYThe interactive process between Range Safety,payload manufacturers, and launch vehicle com-panies or government agencies described in thissection will ensure minimum impact to payloadprograms and reduce the cost and time required forthe approval process.

Many payload systems are generic, meaning theyare built to a common bus structure, using a com-mon launch vehicle, and common Range process-ing prelaunch and launch procedures. As a result,these generic payloads contain few changes to thebaseline system; and the safety data can remain thesame from one mission to the next.

To take advantage of previously approved payloadsystems and generic safety data, the policy de-scribed below shall be followed; however, they maybe modified to meet individual program require-ments:

a. Range Safety and the payload manufacturer inconjunction with the launch vehicle company orgovernment agency shall conduct initial planningmeetings to establish a generic payload approvalprocess.

b. Once a baseline system has been approved,Range Safety efforts will focus on specific changesfor each new program or mission. NOTE: Existingand ongoing previously approved components,systems, and subsystems need not be resubmitted aspart of data packages for review and approval.

c. Range Safety, the payload manufacturer, andlaunch vehicle company, or government agency,shall conduct a safety assessment of each new pro-gram or mission to define changes and/or additionsthat create new, uncontrolled hazards or that in-crease risks significantly.

d. Based on the joint safety assessment, the par-ties shall agree on the minimum required documen-tation to be submitted to Range Safety for reviewand approval.

e. Data submittal and Range Safety responsetimes shall be established based on the joint safetyassessment and modified only upon agreement ofall parties.

f. The goal of the generic payload approval pro-cess is to achieve final Range Safety approval atleast 60 calendar days prior to payload arrival onthe launch complex.

1F.2 APPROVAL PROCESS FOREXISTING PAYLOAD BUSES

For currently existing payload buses, the goal is togrant baseline approvals for generic buses duringthe first mission after implementation of this ap-proach. Subsequent flights would use the joint as-sessment process to review and approve changesto the generic bus and/or payload additions forspecific missions. Key to the approach is thesafety assessment that is used to determinewhether changes or additions have created anynew uncontrolled hazards or increased the riskssignificantly. The assessment results will be util-ized to determine data required and review andapproval requirements.

The approval process for existing payload buses isshown in Figure 1F-1 and described below:

1F.2.1 Launch Services and Mission Orienta-tion Briefing

a. A launch services and mission orientationsafety briefing shall be conducted for Range Safetyapproximately 45 days after contract award for themission. The briefing shall cover the followingtopics:

1. Changes to the launch vehicle2. Changes to the payload bus3. Planned payload additions for the mission4. Changes to hazardous systems and opera-

tions (the focus of this review)b. Range Safety concurrence for both the mis-

sion concept and schedule for the remainingRange Safety milestones shall be provided duringthe mission orientation safety briefing or within 14calendar days after the briefing.

1F.2.2 Data Review and Approval1F.2.2.1 Mission Unique Missile SystemPrelaunch Safety Package

a. A Missile System Prelaunch Safety Package(MSPSP) shall be delivered approximately 12months prior to launch and contain the data re-quirements identified during the mission orientationsafety briefing on the changes to launch vehicle andpayload unique for the mission and identified in theinitial operation's concept review.

Chapter 1: Eastern and Western Range Policies and Processes 31 December 1999 Change to 1997 EWR


1-41

b. Range Safety shall provide responses 45calendar days after receipt of the data package.

1F.2.2.2 Ground Operations Plan (GOP) andHazardous and Safety Critical Procedures

a. A GOP supplement describing changes to ap-proved operations and/or new or modified safetycritical or hazardous procedures shall be deliveredto Range Safety approximately 120 days prior topayload arrival on the Range. NOTE: This supple-ment is required only if changes have been made tooperations and procedures that affect hazardous lev-els or risks.

b. Range Safety shall provide responses 45 cal-endar days after receipt of the data.

1F.2.3 Mission Approval Safety Reviewa. A mission approval safety review shall be con-

ducted approximately L - 120 days to obtain RangeSafety approval for launch vehicle and payloadprocessing, transport to the payload launch pad,payload launch vehicle mating, and launch padpayload processing.

b. Unless there are significant issues, RangeSafety shall provide mission safety approval 14calendar days after the safety review.

1F.2.4 Final Launch Approvala. Final approval to proceed with launch vehicle

and payload processing up to beginning the finalcountdown shall be provided by Range Safety atleast 60 days prior to payload arrival at the launchcomplex. NOTE: Flight plan approval for a mis-sion that involves public safety may not be granted

until just prior to the Launch Readiness Review(LRR) depending on the complexity of the publicsafety issue encountered. For example, typically,at the ER, easterly launch azimuths can be ap-proved at least 120 days prior to launch; on theother hand, high inclination launches may requireextensive risk analyses that can delay final flightplan approval until just prior to the LRR.

1F.3 APPROVAL PROCESS FOR NEW PAYLOAD BUSES

For new payload buses, the goal is to grant base-line approvals for generic buses during the firstmission after implementation of this approach.Subsequent flights would use the joint assessmentprocess to review and approve changes to the ge-neric bus and/or payload additions for specificmissions. Key to the approach is the safety as-sessment that is used to determine whetherchanges or additions have created any new uncon-trolled hazards or increased the risks significantly.The assessment results will be used to determinedata required and review and approval require-ments.

The approval process for new payload buses isshown in Figure 1F-2 and described below:

1F.3.1 Concept Orientation Briefing andSafety Review

a. A concept orientation briefing shall be pro-vided to Range Safety early in (no later than 45days from) the conceptual phase of the development(cDR).

Figure 1F-1Approval Process for Existing Payload Buses

MSPSP CHANGESL-12 MONTHS

SAFETY OPERATIONALSUPPLEMENT CHANGESPAYLOAD ARRIVAL ATCCAS/VAFB -120 DAYS

MISSION ORIENTATION BRIEFINGCONTRACT AWARD +45 DAYS

RANGE SAFETY APPROVALMISSION ORIENTATIONBRIEFING +14 DAYS

RANGE SAFETY APPROVALMSPSP CHANGES RECEIPT +45DAYS

RANGE SAFETY APPROVALSAFETY OPERATIONALSUPPLEMENT CHANGESRECEIPT +45 DAYS

MISSION APPROVAL SAFETYREVIEWL-120 DAYS

RANGE SAFETY APPROVALMISSION APPROVAL SAFETYREVIEW +14 DAYS

FINAL RANGE SAFETY LAUNCHAPPROVALPAYLOAD ARRIVAL AT LAUNCHCOMPLEX -60 DAYS



1-42

b. The generic approval process shall be docu-mented and concept approvals granted so that anaudit trail can be established.

c. A concept orientation safety review shall beheld in conjunction with this briefing and approvalof design concepts, schedule of safety submittals,and Range Safety responses shall be documented.

d. Range Safety concept approvals not grantedat this meeting shall be provided within 14 calen-dar days.

1F.3.2 Preliminary Design Reviewa. A preliminary design review (PDR) shall be

held at least 12 months prior to scheduled launchand will to provide necessary MSPSP data for initialRange Safety approval before the final payload de-sign and prelaunch processing is initiated.

b. Range Safety shall provide approvals within45 calendar days after the meeting.

1F.3.3 Critical Design and Data Reviewa. Prior to initiating hardware manufacture, a

critical design review (CDR) shall be held to pro-vide Range Safety the necessary MSPSP data togrant final design approval and prelaunch process-ing initial procedure review.

b. Range Safety shall provide a response in 45calendar days after meeting.

c. A Ground Operations Plan describing opera-tions and containing safety critical and hazardousprocedures shall be delivered to Range Safety ap-proximately 120 days prior to payload arrival on theRange.

d. Range Safety shall provide responses within45 calendar days.

1F.3.4 Mission Approval Safety Reviewa. A mission approval safety review shall be con-

ducted approximately L - 120 days to obtain RangeSafety approval for launch vehicle and payloadprocessing, transport to the payload launch pad,payload launch vehicle mating, and launch padpayload processing.

b. Unless there are significant issues, Range Sa-fety shall provide mission safety approval 14 cal-endar days after the safety review.

Figure 1F-2Approval Process for New Payload Buses

CDRPRIOR TO INITIATINGHARDWAREMANUFACTURE

CONCEPT ORIENTATIONBRIEFINGEARLY IN CONCEPT PHASE

RANGE SAFETY CONCEPTAPPROVALCONCEPT ORIENTATIONBRIEFING +14 DAYS

RANGE SAFETY APPROVALCDR +45 DAYS

MISSION APPROVALSAFETY REVIEWL -120 DAYS

RANGE SAFETY APPROVALMISSION APPROVALSAFETY REVIEW +14 DAYS

FINAL RANGE SAFETYLAUNCH APPROVALPAYLOAD ARRIVAL ATLAUNCH COMPLEX -60DAYS

PDRL-12 MONTHS

RANGE SAFETY APPROVALPDR +45 DAYS

SAFETY OPERATIONSSUPPLEMENTPAYLOAD ARRIVAL ATCCAS/VAFB -120 DAYS

RANGE SAFETY APPROVALSAFETY OPERATIONSSUPPLEMENT RECEIPT +45DAYS



1-43

1F.3.5 Final Launch ApprovalFinal approval to proceed with launch vehicle andpayload processing up to beginning the finalcountdown shall be provided by Range Safety atleast 60 days prior to payload arrival at the launchcomplex. NOTE: Flight plan approval for a mis-sion that involves public safety may not be grant-ed until just prior to the LRR, depending on thecomplexity of the public safety issue encountered.Typically, easterly launch azimuths can be ap-proved at least 120 days prior to launch. On theother hand, high inclination launches may requireextensive risk analyses that can delay final flight

plan approval until just prior to the LRR.

1F.4 INCIDENTAL RANGESAFETY ISSUES

Incidental Range Safety issues such as componentfailures, test failures, and the discovery of unfore-seen hazards occurring after baseline approvalsshall be worked in real time as part of the finalapproval process for an individual launch. Typi-cally these issues involve the launch vehicle, notthe payload.


APPENDIX 1G1.12 1.9 LAUNCH COMPLEX SAFETY TRAINING AND CERTIFICATION

1-44

1G.1 INTRODUCTION1G.1.1 PurposeThis appendix provides 45 SW/SE and 30 SW/SEoperational safety training and certification re-quirements for launch complex safety. These re-quirements shall be used by Range Users whowish to assume control authority for launch com-plex safety. NOTE: These requirements may bejointly tailored by the Range User and RangeSafety to meet special or unique program require-ments in accordance with Appendix 1A. Minimumstandards, roles, and responsibilities for a launchcomplex safety program are defined in this appen-dix.

1G.1.2 ApplicabilityThe requirements in this appendix apply to all full-time government tenant organizations, singlecommercial users, or USAF squadron/detachmentcommanders who assume control authority andresponsibility for hazardous procedures identifiedby Range Safety as launch complex safety opera-tions. Responsibilities and authorities are definedin Chapters 1 and 6 of EWR 127-1.

1G.2 LAUNCH COMPLEX OPERATIONSSAFETY PROGRAM GENERAL

REQUIREMENTSa. The Range User shall establish and maintain a

launch complex operations safety program to sup-port efficient and effective achievement of overalloperations safety objectives. NOTE: The safetytraining and certification program shall be referredto as the launch complex operations safety pro-gram.

b. The Range User shall implement the require-ments defined in this appendix using a RangeUser-prepared operations safety training and certi-fication plan.

1G.2.1 Safety Management SystemThe Range User shall establish a safety manage-ment system to implement provisions of this ap-pendix. The launch complex safety controlauthority shall be responsible for the following: a. Establishing, controlling, incorporating, di-recting, and implementing the launch complex

operations safety program policies b. Establishing internal reporting systems andprocedures for investigation and disposition oflaunch complex safety operations mishaps andincidents, including potentially hazardous condi-tions not yet involved in a mishap or incident andreporting such matters to Range Safety c. Reviewing and approving launch complexsafety hazardous procedures

1G.2.2 Launch Complex Operations SafetyPersonnel Responsibilities and Quali-fications

1G.2.2.1 Safety Manager

1G.2.2.1.1 Safety Manager Responsibilities.The Range User shall establish and maintain alaunch complex operations safety manager directlyresponsible to the launch complex safety controlauthority. At a minimum, the Range User safetymanger shall be responsible for the following:

a. Approving all launch complex safety op-erations analyses, reports, and documentation

b. Approving all launch complex safetyhazardous procedures and verifying they complywith OSHA/EPA operation requirements and therequirements of EWR 127-1, particularly thosedefined in Chapter 6.

1G.2.2.1.2 Safety Manager Qualifications.The launch complex safety operations safety man-ager shall have a minimum of 10 years of applica-ble managerial or supervisory experience includ-ing at least seven years experience in three of thefour functional areas listed below. A Bachelor ofScience in Engineering and a CSP are also re-quired.

a. Large missile, space vehicle, rocket, tor-pedo, pre-launch, launch, post-launch operationsand/or recovery operations

b. System safety hazard analysis and designor research and development testing of ordnance,explosives, other types of munitions, pyrotechnics,cryogenic, toxic/hypergolic propellants, high pres-sure gases, radioactive materials, or other hazard-ous systems/components

c. Nuclear safety and/or ionizing/non-ionizing radiation

d. Preparation and/or review and approval ofhazardous operating procedures for missile andweapons systems


APPENDIX 1GLAUNCH COMPLEX SAFETY TRAINING AND CERTIFICATION

1-45

1G.2.2.2 Safety Personnel

1G.2.2.2.1 Safety Personnel Responsibilities.Safety personnel shall be directly responsible tothe launch complex safety operations safety man-ager. At a minimum, Range User launch complexsafety personnel shall be responsible for the fol-lowing

a. Reviewing launch complex safety opera-tions analyses, reports, and documentation

b. Performing a detailed safety engineeringreview of launch complex safety hazardous proce-dures to ensure compliance with federal, state, lo-cal OSHA/EPA operation requirements and therequirements in EWR 127-1, particularly thosedefined in Chapter 6.

c. Performing safety, surveillance, and moni-toring of all launch complex safety hazardous op-erations

1G.2.2.2.2 Safety Personnel Qualifications.Launch complex safety personnel shall meet rigidqualification standards and shall be fully experi-enced, trained, and certified to perform launchcomplex safety duties.

a. All safety personnel shall have at least fouryears of applicable experience in at least three ofthe four functional areas identified in 1G.2.2.1.2.

b. Personnel who provide detailed safety en-gineer review of launch complex safety analyses,reports, documentation, and hazardous proceduresshall have a Bachelor of Science degree in Engi-neering and a CSP.

c. The launch complex safety work force shallbe composed of the following levels of experience.NOTE: An Engineering degree may be used tosatisfy three years of the required experience, oran equivalent combination of education, experi-ence, and training may be deemed acceptable by45 SW/SE.

1. At least 30 percent shall have more thaneight years of applicable experience in at leastthree of the four functional areas identified in1G.2.2.1.2.

2. An additional 50 percent shall have atleast six years applicable experience in at leastthree of the four functional areas identified in1G.2.2.1.2.

3. An additional 10 percent shall have atleast four years applicable experience in at least

three of the four functional areas identified in1G.2.2.1.2.

4. The remaining 10 percent may be train-ees.

1G.2.3 Launch Complex Operations SafetyPersonnel Training Requirements

The launch complex safety operations safety man-ager and safety personnel shall have initial andrefresher training in the following areas everythree years:

a. Recognition of launch complex safety haz-ards including:

1. Overhead and mobile crane and hoists2. Sling assemblies3. Handling structures4. Personnel work platforms5. Acoustic hazards6. Non-ionizing radiation7. Laser systems8. Ionizing radiation sources9. Hazardous materials10. Airborne and ground pressure systems11. Airborne and ground cryogenic systems12. Airborne and ground hypergolic systems13. Airborne and ground ordnance systems14. Solid propellants15. Airborne and ground electrical and

electronic equipment.16. Motor vehicles17. Forklifts18. Computer controlled systems such as

cranes and robots19. Facilities

b. Failure modes for launch complex systems in-cluding cause and effect

c. Preventive and control measures for launchcomplex safety hazards

d. Safety devices for launch complex systemse. Protective equipmentf. Monitoring and warning devices for launch

complexesg. Operations hazards analysis techniquesh. Human engineering principlesi. Emergency proceduresj. Hazardous procedures approval and deviation

processk. Preparation and hazards of hazardous materi-

als



1-46

l. Federal (OSHA/EPA), state, local, and AirForce (EWR 127-1, particularly those in Chapter6) hazardous operations requirements

m. Accident investigationsn. Non-destructive examination techniqueso. Single failure point analysis

1G.2.4 ComplianceCompliance with all launch complex safety opera-tions requirements of federal, state, and localregulations, EWR 127-1 (particularly those de-fined in Chapter 6) is mandatory. When the RangeUser launch complex safety operations safety pro-gram plan is approved by Range Safety, it pro-vides a basis of understanding between the RangeUser and Range Safety as to how the launch com-plex operations safety program will be accom-plished.

1G.2.5 Conflicting RequirementsWhen conflicting requirements or deficiencies areidentified in launch complex operations safetyprogram requirements or with other program re-quirements, the Range User shall submit notifica-tion with proposed solutions or alternatives andsupporting rationale to Range Safety for resolu-tion.

1G.3 FOUNDATION OF LAUNCH COMPLEXOPERATIONS SAFETY PROGRAM

This section describes the foundation of a launchcomplex operations safety program. The require-ments are as follows:

a. Establishing and executing a launch complexoperations safety program which meets the tai-lored requirements of this appendix

b. Developing a planned approach for safetytask accomplishment, providing qualified peopleto accomplish the tasks, establishing the authorityfor implementing the safety tasks through all lev-els of management, and allocating appropriate re-sources, both manning and funding, to ensure thesafety tasks are completed

c. Establishing a launch complex operationssafety organization with function and lines ofcommunication within the program organizationand with associated organizations (governmentand contractor)

d. Establishing interfaces between launch com-plex operations safety and other functional ele-ments of the program

e. Designating the organizational unit responsi-ble for executing each safety task

f. Establishing the authority for resolution ofidentified launch complex operational hazards.

g. Defining launch complex operational safetyprogram milestones and relate these to major pro-gram milestones, program element responsibility,and required inputs and outputs.

h. Establishing an incident alert and notification,investigation and reporting process, to include no-tification of Range Safety.

i. Establishing and executing a launch complexsafety operations safety program that complieswith the following:

1. Launch complex safety operation require-ments in EWR 127-1, particularly those definedin Chapter 6

2. OSHA 1910.119 (c): Employee participa-tion

3. OSHA 1910.119(d)(1)(2): Process safetyinformation

4. OSHA 1910.119(f): Operating procedures5. OSHA 1910.119(g): Training6. OSHA 1910.119(h): Contractors7. OSHA 1910.110(I): Pre-startup safety8. OSHA 1910.119(j)(2)(3)(4)(5): Mechanical

Integrity9. OSHA 1910.119(k): Hot work permit10. OSHA 1910.119(l): Management of

Change11. OSHA 1910.119(m): Incident investiga-

tion12. OSHA 1910.119 (n): Emergency planning

and response13. OSHA 1910.119(o): Compliance Audits14. OSHA 1910.119(p): Trade secrets15. Air Force Occupational and Environ-

mental Instruction, AFI 91-301

1G.4 LAUNCH COMPLEX OPERATIONSSAFETY PROGRAM PLAN

a. The Range User shall develop a launchcomplex operations safety program plan(LCOSPP) that describes the tasks and activities oflaunch complex safety operations safety manage-ment and safety personnel required to identify,



1-47

evaluate, eliminate, and control launch complexoperations hazards.

b. The approved plan shall account for all EWR127-1 (particularly those in Chapter 6) and federal,state, and local regulations pertaining to launchcomplex safety operations on an item-by-item ba-sis. c. The Range User shall submit a draft LCOSSPto Range Safety for review and approval within 90days of the date the Range User wishes to assumecontrol authority for launch complex safety opera-tions.

d. The LCOSPP shall include the following sec-tions:

1G.4.1 Launch Complex Operations SafetyOrganizationThe Organization section shall describe the fol-lowing:

a. The launch complex operations safety organi-zation using charts to show the organizational andfunctional relationships and lines of communica-tion

b. The organizational relationship between otherfunctional elements having responsibility for taskswith launch complex safety operations impactsand the launch complex operations safety organi-zation

c. Review and approval authority of applicabletasks by launch complex operations safety

d. The responsibility and authority of launchcomplex operations safety personnel, other RangeUser organizational elements involved in the sys-tem safety effort, contractors, and system safetygroups

e. A description of the methods by which safetypersonnel may raise issues of concern directly tothe program manager or the program manager’ssupervisor within the organization

f. Identification of the organizational unit re-sponsible for performing each task

g. Identification of the authority responsible forresolving launch complex safety operations haz-ards

h. The staffing of the launch complex operationssafety organization for the duration of the programincluding personnel loading and a summary of thequalifications of safety personnel assigned to theeffort, including those who possess coordinationand approval authority

i. The process by which Range User manage-ment decisions are made, including such decisionsas timely notification of unacceptable risks, neces-sary action, incidents or malfunctions, and waiversto operations safety requirements

j. Details of how resolution and action relativeto launch complex operations safety will be ac-complished at the program management level pos-sessing resolution authority.NOTE: See Appendix 1B.1.3.1 for additionalguidance.

1G.4.2 Launch Complex Operations SafetyProgram MilestonesThe LCOSPP shall:

a. Provide a program schedule of safety tasks,including start and completion dates, reports, andreviews

b. Identify subsystem, component, and softwaresafety activities as well as integrated system levelactivities such as design analyses, tests, and dem-onstrations applicable to the launch complex op-erations safety program but specified elsewhere toavoid duplication.NOTE: See Appendix 1B.1.3.2 for additionalguidance.

1G.4.3 LCOSPP DataThe LCOSPP shall provide the following data:

a. A list of all analyses, reports, and documenta-tion used by safety personnel to review and ap-prove hazardous launch complex safety proce-dures and execute the safety program

b. A list of all hazardous procedures categorizedas launch complex safety procedures by RangeSafety

c. The procedures for accessibility of the data byRange Safety and for retention of the data for his-torical and legal requirements

1G.4.4 InterfacesThe LCOSPP shall identify the following inter-faces in detail:

a. The interface between launch complex opera-tions safety and all other applicable safety disci-plines such as nuclear safety, Range Safety, explo-sive and ordnance safety, chemical and biologicalsafety, and laser safety

b. The interface between launch complex opera-tions safety, systems engineering, systems safety



1-48

engineering, and all other support disciplines suchas maintainability, quality control, reliability,software development, human factors engineering,and medical support (health hazards assessments)

c. The interface between launch complex opera-tions safety and all system integration and test dis-ciplinesNOTE: See Appendix 1B.1.3.4 for additionalguidance.

1G.4.5 Internal Reviews and AuditsThe LCOSPP shall describe the procedures foraccomplishing the following:

a. Annual review of the launch complex opera-tions safety program to verify compliance, rele-vancy, adequacy, and ensure documentation iscurrent

b. Launch complex safety management and op-erational reviews (self-audits) to identify programdeficiencies and ensure safety program effective-ness

1G.5 LAUNCH COMPLEX OPERATIONSSAFETY HAZARDS ANALYSIS

The Range User shall perform and document thefollowing safety hazard analyses in accordancewith the requirements specified in referenced sec-tions of Appendix 1B:

a. A Launch Complex Safety Operating andSupport Hazard Analysis (O&SHA) in accordancewith the requirements in Appendix 1B.2.4, Task 4

b. Safety analyses of Engineering Change Pro-posals (ECPs), Specification Change Notices(SCNs), Software Problem Reports (SPRs), Pro-gram or Software Trouble Reports (PTRs, STRs),and requests for EWR 127-1 (Chapter 6) deviationor waiver to determine the launch complex safetyimpact on the system in accordance with the re-quirements in Appendix 1B.2.6, Task 6

c. A safety compliance assessment to identifyand verify compliance with Air Force, federal,state, local, and industry codes to ensure that thehazardous systems are being operated properly inaccordance with the requirements in accordancewith Appendix 1B.2.8

1G.6 RANGE SAFETY AUDITSa. Launch complex safety audits shall be con-

ducted by Range Safety on a periodic basis.

b. The audit shall measure the status of eachsafety task, interrelationship between safety andother program disciplines, identification and im-plementation of safety requirements/criteria, anddocumented evidence which reflects planned vs.actual safety accomplishment.

c. Each audit shall evaluate program milestones,safety program milestones and incompatibilitiesthat require remedial corrective action.

d. The Range User shall initiate positive correc-tive actions where deficiencies are revealed by theaudits.

e. Components, equipment, conditions, designs,or procedures that provide unusual safety prob-lems, shall be audited.

f. Audits shall include verification or correctiveaction on problems revealed by previous audits.

g. The Range User shall support these RangeSafety audits by providing access to documenta-tion that substantiates compliance with federal,state, local, and EWR 127-1 (particularly Chapter6) launch complex operations safety requirements.

1G.7 45 SW/30 SW SAFETY PROGRAMAPPROVAL

The Range User launch complex operations safetyprogram shall be approved by the 45 SW/CC or 30SW/CC, as appropriate, once the following taskshave been accomplished:

a. The Range User shall submit a letter to the 45SW/30 SW Commander stating that they wish toexercise control authority over launch complexsafety operations, and the commander has agreed.

b. The Range User shall identify those launchcomplex safety operations/procedures they wish tohave control authority for, and provides this list toRange Safety.

c. Range Safety will identify those opera-tions/procedures that can be classified as launchcomplex safety operations

d. The Range User and Range Safety will jointlytailor this appendix and Chapter 6 of EWR 127-1.

e. The Range User shall prepare the launchcomplex operations safety program plan andsubmit to Range Safety for review and approval.f. The Range User shall prepare operating haz-ards analysis (as required) and submit to RangeSafety for review and approval.g. The Range User control authority for launchcomplex safety shall submit a certification of



1-49

compliance and substantiating data to RangeSafety for review and approval.

1G.8 SAFETY PROGRAM DECERTIFICATION

a. As appropriate, the Range User launch com-plex operations safety program can be decertifiedby the 45 SW/CC or 30 SW/CC for the followingreasons:

1. The safety program, as implemented, does

not comply with the Range approved launch com-plex operations safety program requirements

2. Internal audits or Range Safety of safetyprogram indicate serious deficiencies that are notbeing corrected in a time frame acceptable toRange Safety

3. Numerous anomalies and/or accidentscaused by operational deficiencies in the safetyprogram

b. Possible 45 SW/CC, 30 SW/CC actions fol-lowing safety program decertification include:

1. Range Safety and its operations safety con-tractor will assume control of launch complexsafety operations

2. Launch complex safety operations will beterminated until the safety program is approved by45 SW/CC or 30 SW/CC, as appropriate.