Skip to content
SF-2026-001089UnverifiedDeep State & Intel Agencies

SUN STREAK Operational Project Protocols (1990)

This 17-page Defense Intelligence Agency (DIA) document, titled 'Operational Project Protocols,' was prepared by the Technology Assessment and Support Office within the Directorate for Scientific and Technical Intelligence and dated 27 November 1990. Classified as a Special Access Program to be handled only via SUN STREAK security channels, it establishes the standard procedures for conducting operational remote viewing tasks. The document details the tasking and reporting flow — from an initial customer request routed through DIA/DT to a Unit Manager, Operations Officer, Project Officer, Monitor, and finally Remote Viewers — and specifies the discrete responsibilities of each role. Procedures include assigning encrypted (random-number) coordinates to represent targets, scheduling viewer sessions, preparing Operations Reports and Summary Reports, maintaining central files, and collecting written customer evaluations of the utility of the data provided. Appendices provide standardized forms: a Task Record Sheet (Appendix A), a Project Summary Record Sheet (Appendix B), and an Operations Report format (Appendix C). The file was approved for release by the CIA on 8 August 2000 and is hosted in the CIA's online Reading Room. SUN STREAK was a code name for the U.S. government's psychic/remote-viewing intelligence effort.

cia.govIncident Nov 27, 1990Released Aug 8, 2000Discovered Jul 4, 2026491.7 KBdocument
sha256:2b3a16407c634cbc32db

Focus

Highlighted excerpt from SUN STREAK Operational Project Protocols (1990)

Archive-highlighted excerpt · page 3 · Jul 6, 2026

Description

A Defense Intelligence Agency Special Access Program document dated 27 November 1990 defining the operational protocols, tasking flow, and individual responsibilities for conducting remote viewing sessions under Project SUN STREAK.

Claims

  • The DIA operated a remote viewing program called SUN STREAK with formal operational protocols for tasking psychic 'viewers' against intelligence targets.

    92%
  • The Defense Intelligence Agency operated a Special Access Program called SUN STREAK for conducting operational remote viewing tasks.

    90%
  • Remote viewing targets were represented to viewers by computer-generated encrypted coordinates (random numbers).

    90%
  • Remote viewers usually viewed once a day, no more than three times a day, submitting session summaries with conceptual sketches.

    90%
  • Remote viewers were tasked using computer-generated encrypted coordinates (random numbers) to represent targets.

    90%
  • Remote viewers usually viewed once a day but no more than three times a day.

    90%
  • Customers were required to provide written evaluations describing how the remote viewing data was used or of utility.

    85%

Events

  1. Nov 26, 1990

    Publication of SUN STREAK Operational Project Protocols

    DIA Technology Assessment and Support Office issued the operational project protocols document.

  2. Aug 7, 2000

    CIA approval for release

    Document approved for public release under the CIA Reading Room declassification.

  3. Aug 7, 2000

    CIA release/declassification

    Document approved for release under the CIA Reading Room.

Dates mentioned

1990-11-272000-08-08

Keywords

Entities

Extracted text (OCR)
—,

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3

SPECIAL ACCESS PROGHAM
OT-5- 1006-SS

DEFENSE
INTELLIGENCE
AGENCY |

OPERATIONAL PROJECT PROTOCOLS (u)

27 Tlovember, 1990

| NORORN
SPECIAL ACCESS:PROGRAM  : ee
Handle Via SUN STREAK Security Channels Only

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3

SPECIAL ACCESS PROGRAM
atta

Date of Publication

27 November 1990

This is a Department of Defense Intelligence Document
prepared by the Technology Assessment and Support Office,
Directorate for Scientific and Technical Intelligence
Defense Intelligence Agency.

PREPARED BY

Technology Assessment and Support Office (DT-SY

NOT RELEASABLE TO FOREIGN NATIONALS

Classified By: DIA/DT
Declassify On: OADR

WARNING NOTICE: THIS MATERIAL IS RESTRICTED TO THOSE WITH

VERIFIED ACCESS TO SUN STREAK LEVEL 2 (S5-2).

eT?
SPECIAL ACCESS PROGRAM
Handle Via SUN STREAK Security Channels Only

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3

Oe a

TABLE OF CONTENTS

Page
I. PURPOSE 1
II. OPERATIONAL PROJECT PROTOCOLS 1
A. TASKING AND REPORTING FLOW SUMMARY 3

B. INDIVIDUAL RESPONSIBILITIES AND PROCEDURES

a. UNIT MANAGER

b. OPERATIONS OFFICER
c. PROJECT OFFICER

d. MONITOR

e. REMOTE VIEWER

OOD LW

APPENDIX A: TASK RECORD SHEET
APPENDIX B: PROJECT SUMMARY RECORD SHEET

APPENDIX C: OPERATIONS REPORT FORMAT

aatiuimG@uiaiimiie / NOFORN
Handle Via SUN STREAK Security Channels Only

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3
atu

I. (U) PURPOSE:

(S/NF) To document the basic protocols and

procedures for the conduct of operational tasks.

Il. (U) OPERATIONAL PROJECT PROTOCOLS:

(U) <A general description of operational project
procedures, along with specific individual responsibilities
are included on the following pages. Detailed protocols
will also be prepared to provide additional details and to

reflect requirements for unique activities as needs arise.
t

CLASSIFIED BY: DIA/DT
DECLASSIFY ON: OADR

aime / NOFORN
Approved: Fox Release 2000/08/96 k EMC ROP 9G 007 §9RINZAAQI7H00h By

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3
jue

A. (S/NF/SS-2) TASKING AND REPORTING FLOW SUMMARY

1. Customer request for information initiated and sent to
the Defense Intelligence Agency (DIA), Directorate for
Scientific and Technical Intelligence (DT).

2. ODT forwards request to Unit Manager.

3. Unit Manager reviews mission requirements and levies
tasking on Operations Officer.

4. Operations Officer identifies Essential Elements of
Information (EEI) to be satisfied, and designated a Project
Officer.

5. Project Officer tasks individual Remote Viewers.

6. Remote Viewers conduct sessions and submit session
summaries with conceptual sketches to Project Officer.

7. Project Officer submits Operations Report with each
viewers summary and sketches to Operations Officer.

8. Operations Officer reviews results and provides a
Summary Report of project findings to Unit Manager.

9. Unit Manager reviews results and forwards completed
project to DT.

10. DT forwards project results to customer.

11. Customer provides written evaluation of data provided
for that project and, where possible, identifies in what
way the data was used or was of utility.

12. Customer evaluations are received through DT by Unit
Manager. Unit Manager forwards evaluations to Operations
Officer who ensures they are posted and given to viewers
for feedback.

13. General steps as discussed above are shown in
Figure 1.

2

atui@uisiiiie / NOFORN
Approved Fog Release 2Q0Q(08/ OR & RIA BBP AED FE IRALAAAGY 0001-3

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3

ae

TASKING AND REPORTING

CUSTOMER

*

LEGEND

L Tasking Unit
ft Reporting Tanager

Operations Ff
Officer §

pity
fdle Ect ae daiat TF

ask vp iat

| Project § Project § Project &

Officer & Officer : Officer :

Viewers fa

Viewers &

Viewers : |

Figure 1
afeeee/ TOF ORT!

Handle Via SUN STREAK Security Channels Only

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3
exGunieGenienie

sage”

B. (S/NF/SS-2) INDIVIDUAL RESPONSIBILITIES AND PROCEDURES

t. Obtains tasking from customer via the Defense
Intelligence Agency (DIA), Directorate for Scientific and
Technical Intelligence (DT).

2. Ensures tasking is valid and applicable.
3. Determines suspense date and timelines.
4. Forwards tasking on Task Record Sheet, see appendix A,

to Operations Officer.

5. Reviews and approves key aspects of all operational
task procedures (e.g. personnel mix, timing, priorities)
developed by the Operations Officer.

¥*¥*CONDUCT OF OPERATION**X
6. Receives completed project from Operations Officer.
7. Determines, in conjunction with customer, if additional
follow-up tasking is required for data clarification or for
pursuit of new and/or different unknowns.
8 Completed project is sent to customer via DIA/DT.
9. Ensures, after data review, that the customer provides
a written evaluation of the data provided for that project,
and where possible, identifies in what way the data was
used or was of utility.
10. Ensures that the entire tasking process, implementing

steps, session details and other information will be
maintained in the program central files.

3

/ NOFORN
Approved For Release TOMO e PRE Re SULA DUFEeRANZAON07 00R1-9

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3

b. OPERATIONS OFFICER

1. Receives tasking from the Unit Manager; examines the
tasking requirements to determine applicability and verify
the key questions or Essential Elements of Information
(EEI’s) desired.

2. Assigns each project a project number.

3. Prepares a mission statement as given by the
requestor/customer; prepares a tasking package, in
conjunction with the Unit Manager, with the specific
targeting method or methods that will be made available to
the viewer:

a. Develops/assigns computer generated encrypted
coordinates (i.e. random numbers) to represent the

target.

b. Develops in conjunction with the Unit Manager, any
additional requirements that may be presented to the
viewer (e.g. scope of task, general type of
information desired).

c. Develops, in conjunction with the Unit Manager, if
any target-related information (e.g. sealed photo,
name of missing person/ship, maps, etc.) are to be
made available to the viewer.

d. Recommends to the Unit Manager the anticipated
personnel mix (Project Officer, Monitor, Viewer)
required to accomplish the task.

4. Provides Project Officer with refined tasking package
to include:

a. Information identified in paragraph 3.
b. List of available viewers.

c. Assigns suspense dates and specific time windows
for accomplishment of the project.

¥*¥*CONDUCT OF THE OPERATIONX**

5. Receives Operations Report and viewer session summaries
from Project Officer.

4

ame / NOK ORN
Approved Fed Relekée 2600/0808 Eblh-Repy6-b6789R0029G007 0801-3

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3

aqua
6. Reviews project results to ensure all questions have
been answered and project is complete. Determines if

additional sessions are required.

7. Writes a formal Summary Report of each project with
appropriate addenda such as viewer summaries and sketches,
completes Task Record Sheet, see appendix A, and forwards
it to the Unit Manager.

8. Maintains a copy of all data obtained from each session
in unit’s central files.

9. Maintains a detailed summary of project information
(see appendix B).

10. Ensures evaluations are posted upon receipt from the
customer and made available to viewers for feedback.

5

Approved For Release 20000 She
Handle Via SUN Sit 96 cUPESRUbzanna7p00%31 y

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3
od

c. © PROJECT OFFICER

1. Receives the project from the Operations Officer and
determines the actual number of sessions required in
conjunction with the Operations Officer.

2. Responsible for accomplishing the entire project;
ensures all questions are answered.

3. Responsible for the preparation of individual tasks
reflecting specific EEI for the viewer to answer.

4. Manages, directs, and provides guidance for the remote
viewing activity.

a. Obtains required materials for sessions, e.g.
appropriate maps for a search problem, photos, etc.
b. Identifies and schedules specific viewers and
monitors (if needed).

c. Will not normally serve as a viewer for the
project he is managing but may act in the capacity of
monitor as circumstances warrant.

¥*¥XCONDUCT OF OPERATIONKX®X

d. Receives and reviews viewer session summaries for
submission to the Operations Officer.

e. As required, discusses each viewer’s summary with
individual viewer to ensure all concepts of the
session are complete and clearly stated in the
summary. Ensures all necessary sketches are provided.
f. Determines if viewer will have to conduct another
session, depending on whether viewer has answered all
questions, the nature of the task, and the results
achieved per session.

g. At the conclusion of the sessions, provides
viewers with known operational information as
available. Nature and type of feedback will be
recorded in the session records. Project Officer must
also be aware that follow-up tasking for the same
project may occur depending on customer/program
manager requirements after review of project results.

quiunimieieninis / NOFORN
Approved Far relegge, 20000 8ia82 EAie- RAR W-9 O78 ROA AIOE OGHE 3

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3

extents

5. Responsible for preparing and submitting a written
Operations Report that serves as a cover to the Remote
Viewer’s summary. The Operations Report will contain the
following: Project number, session number, date of
session, date of report, start time, end time, methodology
used, viewer identifier number, missions, viewer tasking,
comments and inclemencies noted, (see sample of report at
appendix C). Evaluation paragraph will be left blank for
customer/program manager.

6. The Project Officer will also report, on appendix B
“COMMENTS”, any information that may relate to viewer
disposition (e.g. state of health, distractions, etc.)
The Project Officer will also record any deviation from
standard protocols that may have occurred.

7. Completed project with viewers summaries and operations
reports will be given to the Operations Officer. All data

obtained from each session will be recorded and stored in a
file under the control of the Operations Officer.

8. The Project Officer will not communicate results to
anyone other than the Operations Officer and/or Unit
Manager. During and following the operational task
activity, the Project Officer will ensure that file
integrity is maintained and that the project will not be
discussed among viewers until the Unit Manager has given
approval.

7

pproved Wiandle Via SUN ST ge SUB YRBGZANNDEROG A y

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3
agua

d. MONITO

1. Receives tasking to be a monitor/interviewer from
Operations Officer through Project Officer.

2. Receives project questions to be answered and EEI from
Project Officer.

3. Ensures he has appropriate materials required for the
session, such as maps or photos if available.

4. Discusses with viewer designated time window and
conducts the session.

5. Ensures viewer has answered all questions during the
session or after numerous sessions.

6. Does not discuss session results with anyone other than
the Project Officer, Operations Officer, or the Unit

Manager.

7. Will not monitor a project he has served as a viewer.

equindinGeie / NOFORN
Approved For Release 2000/08/08 R CAK-RDAIG 007 §9R002906020001-by

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3
anita,»

e. REMOTE VIEWER

1. Receives tasking from Operations Officer through
Project Officer.

2. Usually views once a day but no more than three times a
day.

3. Provides a summary of information obtained per session
to the Project Officer. Summary will contain at least the
following: Project number, date, start time, end time,
viewer identification number, session number, physical
inclemencies noted, summary of information from session,
sketches and appropriate classification markings.

4. Does not discuss session results with other viewers.

5. May be selected to act as trainer/teacher for a new
member of the unit.

6. Should the Remote Viewer serve as Monitor or Project

Officer, he/she will not perform remote viewing activities
on those Monitor or Project Officer tasks.

9

agua=memnee / NOFORN
ApprovediBerRejeasrs2 090M 8H)BR LAK-RDR9600789R0G29000 70007 lay

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3
nina,

TASK RECORDS

1. DATE TASK PROVIDED TO PROJECT:
2. PROJECT NUMBER:
3. REQUESTOR:

4. INFORMATION DESIRED:

5. BACKGROUND INFORMATION PROVIDED TO PROJECT:

6. ENCRYPTED COORDINATES:

7. SESSION SCHEDULING:

DATE SOURCE SESSION METHODOLOGY REMARKS

8. TASK MILESTONES (e.g. task reporting, feedback):

APPENDIX A

Approved For Release 2000/08/08 pela P96) 007 89R002900070001-3

Handle Via SUN STREAK Security Channels Only

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3

yieiz by vis c

NOISSAS | NOISS3S . SNOISSHS f

| Had JO ON
Bad | GOHLAW ft ssaounosl :
HOLINON =} ONILZOYVL :

MREMERERE WS WORE RE SUE Ws Ee EE i we FER. §

SOLWAOIN ik a cl

APPENDIX B

equampunaneb / NOFORN

Approved For Relaast 200008708 :SCHRERDP96100789 00296667 0661-3


Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3

Ce

ne
= O
ee
ii] ©
Csi | “Oat
<t | P2290
Ot f= AD P
: err)
© Are uw

: j— Ps io

(= SF Ia
> 1" Z2

, 7G} -
maa

iO E +
_ae

PZ) peers
PE ZE
pr) |=53

O} |e 22]
ir rox

=

i= :
ean:
gan a
wal Fa)
‘ae H
+ 3
S| x 2

agunuGunmiiaie / NOFORN
Handle Via SUN STREAK Security Channels Only

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3


Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3

. ;

PROJECT SUN STREAK

WARNING NOTICE: INTELLIGENCE SOURCES AND METHODS INVOLVED

PROJECT NUMBER: SESSION NUMBER:
DATE OF SESSION: DATE OF REPORT:
START TIME: END TIME:
METHODOLOGY: SOURCE IDENTIFIER:

1. (S/NF) MISSIONS:

2. (S/NF) VIEWER TASKING:
3. (S/NF) COMMENTS:

4. (S/NF) EVALUATION:

5. (S/NF) SEARCH EVALUATION:

CLASSIFIED BY: DIA
DECLASSIFY ON: OADR

APPENDIX C

quae = NN OF ORN
Handle Via SUN STREAK Security Channels Only

Approved For Release 2000/08/08 : CIA-RDP96-00789R002900070001-3

Related files

Connected through the network