I
|
|
| Personnel Safety
All personnel shall be protected during the performance of operations.
|
C
|
|
|
Stopping Unsafe Operations |
I
|
|
|
3.2.1. All personnel shall have authority to stop immediately operations or practices that, if allowed to continue, could reasonably be expected to result in death or serious physical harm to personnel or major system damage.
|
C
|
|
|
3.2.2. All personnel are authorized to stop operations or practices when imminent danger cannot be eliminated through regular channels. Personnel observing an unsafe operation or practice shall report their observations to a safety representative, an operational supervisor, or any other appropriate authority.
|
C
|
|
|
3.2.3. Notification of Action. Any action taken to stop an unsafe operation where imminent danger is involved shall be followed by direct verbal, telephone, or radio communication and notification to the appropriate safety authority. For Air Force Ranges notifications, include Pad Safety at the ER and Range Safety at the WR, the Squadron Commander, the Group Commander, or their designated representative.
|
C
|
|
|
3.2.4. Notification of Work Stoppage. The Contracting Officer or Administrator for an Air Force Construction Contract shall be immediately notified of any work stoppage of their respective construction contract.
|
C
|
|
|
DOCUMENTATION REQUIREMENTS |
I
|
|
|
Ground Operations Plans
GOPs shall be developed in accordance with the requirements in Attachment 1 of this volume and submitted to the PSWG for PSWG and Range Safety review and approval.
|
C
|
|
|
4.1.1. The GOP provides a detailed description of hazardous and safety critical operations for processing aerospace systems and their associated ground support equipment (GSE). Along with the Safety Data Package (Missile System Prelaunch Safety Package (MSPSP)), the GOP is the medium from which payload safety approval is obtained.
|
C
|
|
|
4.1.2. A high level Ground Operations Flow Overview shall be provided at the Payload Safety Introduction Briefing. The preliminary Draft GOP is due 30 days prior to project’s mission CDR for Safety Review II per NPR 8715.7. The Final GOP shall be submitted 90 days prior to the payload shipment to the processing site per NPR 8715.7. The information from a GOP may be part of the respective Safety Data Packages as an inclusion or may be a separate document. The level of detail provided in the GOP data shall be commensurate with the level of data available at the time of submission.
|
C
|
|
|
4.1.3. The final GOP shall be submitted no later than 60 days prior to the Safety Review III meeting and at least 90 days prior to intended shipment of hardware to the prelaunch payload processing site per NPR 8715.7.
|
C
|
|
|
4.1.4. The GOP shall be approved before the start of any hazardous operations.
|
C
|
|
|
Test and inspection plans shall be developed to document the initial and recurring validation of component compliance and assessment of hazards. Test and inspection plans shall be developed for the following items that include, but are not limited to, material handling equipment, ground support pressure vessels, and ground support propellant systems. Specific requirements for each of these systems are discussed in this volume.
|
C
|
|
|
4.2.1. Equipment and System Logs and Test Records.
|
I
|
|
|
4.2.1.1. Unless otherwise specified in a separate part of this volume that addresses a particular class of system or equipment, logs and test records shall be maintained on critical ground support systems and major fixed equipment. Logs and test records shall comply with the following:
|
C
|
|
|
4.2.1.1.1. Logs and test records shall contain chronological entries including:
|
C
|
|
|
4.2.1.1.1.1. Records of use or running time.
|
C
|
|
|
4.2.1.1.1.2. Maintenance.
|
C
|
|
|
4.2.1.1.1.3. Modifications.
|
C
|
|
|
4.2.1.1.1.4. Tests, inspections, acceptable parameters, and results.
|
C
|
|
|
4.2.1.1.2. Discrepancies and out of specification results shall be clearly identified.
|
C
|
|
|
4.2.1.1.3. Resolution of discrepancies and out of specification results shall be noted.
|
C
|
|
|
4.2.1.2. Logs and test records shall be maintained for the life of the system/equipment.
|
C
|
|
|
4.2.1.3. Logs and test records shall be available to the PSWG and Range Safety upon request.
|
C
|
|
|
| |
