• 411 411

iHf- 20 AUG 1973

lbingaraa

1.4.3.406„,

PARTING GUIliANCE

FOR

SNP. LAUNCHES FROM VANDENBERG AFB

. . . .

riga% AI P,Ptirif • e • ewe. . •
SAFSP

REPORTING OF MISSILE LAUNCH ACTIVITY 

PURPOSE: 

This document provides guidance for reporting SAFSP launch activities

at Vandenberg AFB, CA.

REFERENCES: 

JCS Pub 6, Vol V, JRS

AFR 127-4

C. AFSCR 55-2

GENERAL: 

The Chief of Staff, USAF and appropriate Commanders at major and intermediate command levels must be informed when a . SAFSP system is launched or

involved in any unusual event. Notification is essential to permit their

knaaledgeable reply to inquiries from government officials or the general

public.

RESPONSIBILITIES: 

The Commander, 6595th Space Test Group (6595 STGp), is responsible for

implementing the reporting requirements set forth in this document.

5. REPORTING: 

LIMITATIONS: Prior to the release of any telephonic or telegraphic

reports, the Commander, 6595 STGp will notify and receive approval from the

Director of Special Projects, SAFSP, or his Deputy Director for the program

concerned.

REPORTS: Reporting requirements contained in references, paragraph

2 above, and public information reporting will be addressed in this section.

Reports required under both normal and accident conditions are listed in

relation to the launch phase activity, i.e., prelaunch and post launch.
(1) UORNAL Cr-nITIO4S:

PRELAUNCH: The D-5 Day Presto Report required by AFSCR

55-2, as supplemented, will be initiated by the 6595 STGp. Format will be

per report 1, ANNEX 1.

POST LAUNCH: 

The 6595 STGp will assure SAMTEC Range Operations (ROOC)

transmittal of the Range Post Launch Report (submitted NLT launch plus one

hour) adheres to the format and content of report 2, ANNEX 1.

A PRESTO QUICKLOOK Report, per AFSCR 55-2 will be

submitted (NLT launch plus 8 hours) by the 6595 STGp. Format and content

will be per report 3, ANNEX 1. Additionally, as applicable, a SAMTEC (00

public information message correlating with the content of report 3, ANNEX 1,

will also be approved (by 6595th ATW/CC) for release.

(2) ACCIDENT COUDITI?IS: • •

(a). PRELAUNCH: In the event of an on pad cataitrophe, the

6595 STGp will provide JCS Pub 6, Vol V, JRS, OPREP 3 telephonic report

data to Range Scheduling, per the format in report 4, ANNEX 1. Additionally,

a follow-up record report of the telephonic OPREP 3 transmission will be

submitted by the 6595th STGp via teletype; per the format of report 5,

ANNEX 1. A correlating public information message, prepared by SANTEC

(00, will also be approved (by 6595th ATW/CC) for release. Subsequent

reporting will be accomplished in accordance with the reporting schedule

and format requirements of AFR 127-4, attachments 4 and 8 respectively.

(b) POST LAUNCH: 

1. In the event a failure occurs prior to Satellite

Vehicle separation, Range Control, after coordination with 6595th STGp/CC,

will provide JCS Pub 6, Vol V, JRS OPREP 3 telephonic report data to Range

Scheduling; per format in report 4, ANNEX 1. Range Control, after coordination with 6595th STGp/CC, will submit a follow-up OPREP 3 Record Report via
teletype; per the form.. of report 5, AMEX 1. A corn. .tang public

information report, prepared by SAMTEC (01), will also be approved (by

6595th A714/CC) for release. Subsequent reporting will be accomplished in

accordance with the reporting schedule and format requirements of AFR 127-4,

attachments 4 and 8 respectively.

2. In the event a failure occurs after SV separation,

reporting, if required, will be accomplished by the cognizant SAFSP program

element.

. Atch

ANNEX 1
. . .

.em Iowa& WS el. II

•

ANNEX 1
REPORT NO. 1 

TYPE: D4 PRESTO REPORT (Submitted 5 work days prior to launch)

KODE OF SUBMISSION: Telegraphic

PRECEDENCE:. Routine

SECURITY CLASSIFICATION: SECRET (When message text is completed)

FROM: 6595th Space Test Group/CC

TO: AFSC/DOOW, Andrews AFB, ra

INFO: SAMSO/XOP, Los Angeles, CA

CINCNORAD/NCMC/NOSC-M, Ent AFB, CO

SUBJECT: D-5 Presto Report for (Operation Number)

TEXT: 1. (5) (Insert booster type and serial number), operation

number (list number), will be launched from Vandenberg AFB,

SLC (list number and pad) on (AA). Launch window is

(tigt)z to (time z. Launch azimuth (degrees) TRUE. Launch

will be conducted by the 6595th ASTWg.

(U) The purpose of this launch is to place a classified

payload in orbit.

(U) Radar optics and TM data will be collected from

Lompoc AFS and Vandenberg AFB through orbit injection.

4. (U) This message is classified SECRET because of the

association of the operation number, launch pad, launch

date and primary objectives.
REPORT NO. 2 

• •

TYPE: Range Post Launch Report (NLT launch plus 1 hour)

MODE OF SUBMISSION: Telegraphic

PRECEDENCE: Immediate

SECURITY CLASSIFICATION: SECRET (When message text is completed) •

FROM: SAMTEC Range Operations (ROOC)

•

TO: AFSC/Andrews Operation Center/AOC

SAMSO/Los Angeles AIS Operation Center/XOP

SAMSO/Det 3

SAMSO/SCD

SUBJECT: Range-Post Launch Report

TEXT: Five Paragraph Message as follows:

Para One: (a) Range Operation Number

(b) Liftoff Time•

(c) Missile Type (booster name)

Launch Pad

Launch Agency

(f) Launch Azimuth

Para Two: Mission objective (place a classified payload

in orbit).

Para Three: Identify any significant holds experienced

in the launch countdown.

Para pour: (a) Booster performance (booster performance 

appeared to be nominal); or,

Para Five:

(b) Range Destruct sent at (time). •

Contact (the Program Office) for additional

information.

•

con ilfrICIAL ME MI
REPORT 30. 3 

TYPE: PRESTO QUICKLOOK REPORT (Launch plus 8 hours)

MODE OF SUBMISSION: Telegraphic

PRECEDENCE: Immediate

SECURITY CLASSIFICATION: SECRET (When message text is comoleted)

FROM: 6595 ASTWg/CC

TO: CSAF

AFSC/000C/DOOW, Andrews AFB MD

INFO: SAMSO/X0P, Los Angeles, CA

CINCNORAD/NCMC/;OSC-M, Ent AFB, CO

SUBJECT: Presto Quicklook

TEXT: 1. (S) Operation (number), (type of booster) was launched

from Space Launch Complex (number and pad) on (kW, at (122).

Preliminary evaluation indicates that ascent traiectory and orbit

were (nominal or state the anomolies). Real time telemetry data

showed (no vehicle anomolies or state the anomolies).

2. (U) This message is classified (SECRET because of the

association of operation number, vehicle type and launch pad.
REPORT MO. 4 

•

TYPE: OPREP 3 Report

• MODE OF SUDMISSI04: Telephonic (A telegraphic record report will be

forwarded 1 hour after the telephonic;

see Report No..5)

PRECEDEUCE: • Immediate

SECURITY CLASSIFICATIOU: UNCLASSIFIED

FROM: Range Scheduling (ROOS)

TO: USAF, AFSC(Andrews Opn Ctr/AOC), SAmS0(Los Angeles APS

Opn Ctr/XOP)

TEXT: a. In the event of an on-oad catastrophe - A (booster type)

space launch vehicle was involved in an on-pad accident at

Vandenberg AFB, CA on (date), at (Limo. The vehicle was being

prepared for launch by the 6595th STGp (AFSC), VAFB, CA. There

were (indicate the number VIP military and civilian) casualties;

or state unknown. -Provide a brief description of damage to

government and/or private property, or state unknown. Provide

an estimate as to the public relations impact. A classified

record report will follow. 'Point of contact is (Haire

Commander, 6595th STGp (AFSC), Vandenberg AFB, CA.,(Autovon .

276-7048).

b. In the event of a failure orior to SV seoaration A

(booster type) space launch vehicle failed in flight on.(date),

at (time). The vehicle was launched from Vandenberg AFB, CA

by the 6595th STGp (AFSC), VAFB, CA. There were (indicate 

the number of VIP militaryor civilian) . casualties, or state

unknown. Provide a brief description of damage to government

and/or private property, or state unknown. Provide an estimate

as to the public relations impact. A classified record report

will follow. Point of contact is (name), Commander, 6595th

STGp, Vandenberg AFB, CA (Autovon 276-7048).
REPORT NO. 5 

TYPE: OPREP 3 Record Report

MODE OF SUBMISSION: Telegraphic •

PRECEDENCE: SECRET (When message text is completed)

SECURITY CLASSIFICATION: UNCLASSIFIED •

FROM: 6595th ASTWg/CC (Text a.) or Range Control/ROOC (Text b.)•

TO: CSAF

INFO: AFEOC, Ft Richie, rip

HQ USAF/ALT/Maxwell AFB, AL

HQ AFSC

HQ SAtSO

HQ SANTEC (Hail)

TEXT: a. In the event of an on-pad catastrophe - A (booster tvoe,

serial no. ) with a classified payload was involved in an

^ ad missile on-p accident at Space Launch Complex (number and 

ad), Vandenberg AFC, CA. The event occurred on (silk), at

• Itime). The vehicle was being prepared for launch by the

6595th STGp (AFSC), Vandenberg APB, CA. There were (indicate 

the number of VI!, military and civilian) casualties; or state

unknown. Provide a description of damage to government and/

or private property, or state unknown. Provide an estimate

of public relations impact. Point of contact is (name),

Commander, 6595th STGp (AFSC), Vandenberg AFB, CA (Autovon

276-7048).

b. In the event of a failure prior to SV separation - A

(booster, serial no. and type) space launch vehicle with a

classified payload failed in flight on (date), at (time).

The vehicle was launched from Space Launch Complex Fiber

and ad), Vandenberg AFB, CA by the 6595th STGp (AF5E),---

anden erg AFC, CA. Range safety destruct action (was or

was not) initiated. Missile and payload debris has imp acted

(on land, or water) and recovery actions (are or are not) in

progress. There were (indicate the number ofVIP, military 

and civilian) casualties; or state unknown. Provide a

description of damage to government and/or private property,

or state unknown. Provide an estimate of public relations

impact. Point of contact is (name), Commander, 6595th STGp

(AFSC), Vandenberg AFB, CA (Autovon 276-7048).
.11 Wall W•• saan .

PHONE LISTING

. .

FOR

REPORTING ORGANIZATIONS

HO imrEc 

LAUNCH OPERATIONS CONTROL CENTER 276-7840/7292

SPACE LAUNCH COMPLEX 4 275-4421

6595th AEROSPACE TEST WING 276-6444

6595th AEROSPACE TEST GROUP 276-7048

TITAN DIVISION 276-6957

RANGE OPERATIONS 276-3805

RANGE SCHEDULING • 276-8825

RANGE CONTROL 275-3091

1STRAD

BASE COVMANDER 276-4602

4392d CONTROL ROOM (Diaster Control) 276-6882/6411/6943

1STRAD SCHEDULING 276-5313

1STRAD COMMAND POST 276-9961
NEWS RELEASE GUIDANCE

•

FOR •

SAFSP LAUNCHES FROM VANDENBERG AFB

01 •

•
RELEASE AFTER VEHICLE IIAS BEEN

LAUNCHED, AND IS OUT OF SIGHT AND HEARING

•

et •

(satellite, space probe. etc.)

EMPLOYING A

COMBINATION WAS LAUNCHED FROM THE SPACE

AND MISSILE TEST CENTER, VANDENBERG AIR FORCE BASE, CA.,

•

TODAY AT

(date) (time)

. . .

PACIFIC STANDARD/DAYLIGHT TIME BY AN AIR FORCE AND INDUSTRY

TEAM (if applicable).

•

•
III I %re a wit um rubs vets. a

•

RELEASE IN EVENT OF EXPLOSION ON THE PAD:

•

•

"An • EXPLODED ON ITS LAUNCI I PAD

TODAY, AT THE SPACE AND MISSILE

TEST CENTER, VANDENBERG AFB, CALIFORNIA. AN INVESTIGATION

IS UNDER WAY TO DETERMINE THE CAUSE."

4.

41.
•

RELEASE IN EVENT OF DESTRUCT ACTION WITHIN SIGHT AND liEARING

OF GROUND OBSERVERS: .

.

WAS DESTROYED BY TILL SPACE AND MISSILE TEST CENTER RANCE

SAFETY OFFICER TODAY. AT VANDENBERG

MR FORCE BASE, CALIFORNIA WHEN A MALFUNCTION CAUSED A

DEVIATION IN ITS PLANNED FLIGHT PATH. AN INVESTIGATION IS

UNDER WAY TO DETERMINE THE CAUSE." •

•

•

• •

•

R

!.

.3
RELEASE IN EVENT OF IN-FLIGHT EXPLOSION WITHIN

HEARING AND SIGHT OF GROUND OBSERVERS:

•

"A

EXPLODED SECONDS AFTER IT WAS LAUNCHED AT

•• PDT/PST FROM THE SPACE AND MISSILE TEST CENTER, VANDENBERG

AIR FORCE BASE, CALIFORNIA. AN INVESTIGATION 1$ UNDERWAY

TO DETERMINE THE CAUSE."